Mageia forum

Oh no! something went wrong. It is impossible to correct a problem ending the session and try again

i use fglrx catalys 11.6 ati

What is the problem you are talking about?

Are you still using Cauldron despite all the warnings you received?

yes i use cauldron but why gnome3 give me this error session i use fglrx

PietroTux88 wrote:Oh no! something went wrong. It is impossible to correct a problem ending the session and try again

My my my... how in the world are we supposed to help you with a message like that?

"Something is broken. Help!"

Try to be constructive and to give useful input. And switch to Mageia 1, because Cauldron seems not to be the best fit for you.

You have not given anywhere near enough information for anyone to help.

Why do you think the video driver is at fault?
Have you checked the log files for relevant errors?
At what point does this message appear?
Have you tried launching X manually?
Have you tried using an alternative DE?
etc, etc.

Those who run cauldron, at this stage of the development cycle, should be able to perform at least some of the basic initial trouble-shooting without help.

Cauldron does not exist so that you can have the latest version of software. It's main purpose is testing and bug resolution. Hence it should be used only by those who have the knowledge to participate in that process.

Jim

kde 4.6.90 work and xfce work and fluxbox work and e17 work but gnome 3 fail but gnome 2.32.1 work 100% with fglrx 8.861 ati radeon catalyst 11.6 gnome-shell fail and come to gnome-classic mode

It seems that there a several possible reasons for that error message. If you Google for:

Gnome "Oh no! Something has gone wrong. A problem has occurred and the system can't recover. Please log out and try again"

you'll find several reports. Since only you know what packages you have installed, what configuration changes you have made and what you did in the session immediately prior to this failure, only you can know if any of those reports are relevant to your situation. (~.xsession-errors may provide a clue.)

Jim

Ok, I tried this with my Cauldron-installation ...

This seems to be a graphics-problem (x - mutter?). It occurs here with Nvidia too.

It occurs, when I want to expand a window to fullscreen, or when I move the mouse-pointer to the upper left region of the screen. A problem with the 3d functionality?
Sometimes, the screen flickers after the oh-no-message, and there is a changing between the message screen and the fullscreen window (for example full screen firefox).
I guess the system works, but something provokes the message ...

Btw, deleting ./gconf /gconfd and ./gnome2 doesnt have any effect ...


Cheers,
Bernd

edit: Gnome-classic works without problems ...

winstonteacox wrote:This seems to be a graphics-problem (x - mutter?). It occurs here with Nvidia too.

It occurs, when I want to expand a window to fullscreen, or when I move the mouse-pointer to the upper left region of the screen. A problem with the 3d functionality?

Maybe a similar problem like the nvidia-resize bug with KDE4 and X-server 1.10?
viewtopic.php?f=15&t=567

I have the newest driver and Pietro uses ATI ... so this is no driver problem this time, I guess.

EDIT: Same symptoms on an Asus eeepc 901 with Intel-graphics ...


The Mageia Devs know about the problem:

https://www.mageia.org/pipermail/mageia ... 05238.html

and following ...

It seems, they want to wait for the update to 3.2 and check the situation then ...

Cheers,
Bernd

I guess I have a interim solution:

In the folder

Code: Select all

/home/YOURUSER/.config/autostart/

create a file

Code: Select all

gnome-shell.desktop


It should have the following content:

Code: Select all

[Desktop Entry]
Type=Application
Exec=gnome-shell --replace
Hidden=false
NoDisplay=false
X-GNOME-Autostart-enabled=true
Name[en_US]=Gnome Shell
Name=Gnome Shell
Comment[en_US]=
Comment=

This seems to work. (At least it worked now for 20 minutes ... )

cheers,
Bernd


edit: the X-GNOME ... line was neccessary

This "Oh no!" message comes after each start of the gnome-shell. Workaround:

DO NOT click on "ok" in the message box!
Just punch Alt+F4 and the message box will go away. After that the gnome shell works as it should.

This has been discussed in the -dev list some time ago.

Thanks wobo. I thought that I had seen a reference to that message before, but I couldn't remember where. There's also a bug report with the solution (just a couple of days ago) which I probably read:

https://bugs.mageia.org/show_bug.cgi?id=1815#c15

(It's really frustrating when one's memory starts to go.)

This experience confirms that anyone running cauldron should be subscribed to the dev and bugs lists, or at least be willing to search bugzilla and the ml archive before asking for help.

Jim

jkerr82508 wrote:This experience confirms that anyone running cauldron should be subscribed to the dev and bugs lists, or at least be willing to search bugzilla and the ml archive before asking for help.

Amen!!

winstonteacox wrote:This seems to work. (At least it worked now for 20 minutes ... )

clarification:
It works, since yesterday evening no single crash. And without a single error-message (not to click away) after login.

winstonteacox wrote:It works, since yesterday evening no single crash. And without a single error-message (not to click away) after login.

Great!
I posted the solution for the "not to click away" error message earlier this morning here.

Yes, I have not been sure if it really works, but it seems so.

I found the solution with gnome-shell.desktop considerably fast ...
The Exec-line restarts the shell after login.

But the panel didn't start.

So the X-GNOME line was necessary to start the panel ... This i found in another forum ...


Cheers,

Bernd

the solution for gnome3 ?how to fix this fail

winstonteacox wrote:In the folder

Code: Select all

/home/YOURUSER/.config/autostart/

create a file

Code: Select all

gnome-shell.desktop


It should have the following content:

Code: Select all

[Desktop Entry]
Type=Application
Exec=gnome-shell --replace
Hidden=false
NoDisplay=false
X-GNOME-Autostart-enabled=true
Name[en_US]=Gnome Shell
Name=Gnome Shell
Comment[en_US]=
Comment=

With this solution I have a working GNOME3 (not Gnome-Classic) without any error-messages.

i haven't a folder autostart in my .config ?and how to create new file you say new file document?

PietroTux88 wrote:i haven't a folder autostart in my .config ?and how to create new file you say new file document?

You're running Cauldron. And you don't even know how to create a folder and a file?

Code: Select all

man mkdir
man touch

now not working gnome3 i have make gnome-shell.desktop and create folder autostart on ./config my user gnome fall back is blue screen with screenshot striped gnome3
this is photo my problem i link down
http://gnupress.files.wordpress.com/2010/12/stripes.jpg this is my photo problem

You haven't said whether or not hitting Alt-F4 to close the message dialogue works for you or not. If it does, then revert the changes that you made to your /.config and wait for the bug(s) to be fixed.

Jim

is possible mageia cauldron can have gnome 3 stable please before upload to mirrors mageia must check very well before upload package if before to upload to caulron