I upgrade my cauldron install a few days ago for using Gnome3 Install work well and gnome3 launch but every time I try to launch a application (no matter wich one), the system crash and tell me he is sorry before bring me back to GDM
CC: (none) => marianne
Created attachment 577 [details] Backtrace of gnome-shell Attached is a backtrace of the crash of gnome-shell few seconds after the gnome-session start. Relaunched from tty gnome-shell (via a DISPLAY=:0 gnome-shell) does not crash anymore.
Blino on irc is pointing to this commit http://git.gnome.org/browse/gnome-shell/commit/src/shell-xfixes-cursor.c?id=88de26138a8b79d89884ff2eb6471c5a8e3b39ca
CC: (none) => balcaen.john, dmorganec
Marianne do you have the same backtrace ?
for comment #3, unfortunately the git commit is already on our version of gnome shell.
is adwaita-cursor-theme installed for you ?
Created attachment 582 [details] bt full Another bt with bt full now :)
(In reply to comment #5) > is adwaita-cursor-theme installed for you ? it is.
(In reply to comment #7) > (In reply to comment #5) > > is adwaita-cursor-theme installed for you ? > > it is. Same for me
Marianne can you provide me the backtrace too please ?
GNOME 3 crashes here after I: 1. Start it using "startx". 2. Start a terminal using "Activities -> Applications". 3. Move it for a while. My system's specs are: Pentium 4, 2.4 GHz CPU. 2.5 GB of RAM. An ATI Radeon HD 2600 card. One 160 GB Hard-disk and two smaller ones of 80 GB or so. A 19×´ LCD Screen by ViewSonic. A standard built-in ACâ97 sound-card.
CC: (none) => shlomif
(In reply to comment #10) > GNOME 3 crashes here after I: > Could you attach the backtrace please ?
(In reply to comment #11) > (In reply to comment #10) > > GNOME 3 crashes here after I: > > > Could you attach the backtrace please ? 1. Well, what happens is that GNOME informs me that it closed. 2. How do I generate the backtrace? Regards, -- Shlomi Fish
(In reply to comment #12) > > 1. Well, what happens is that GNOME informs me that it closed. That gnome-shell crash or something was wrong ? > 2. How do I generate the backtrace? By attaching gdb to gnome-shell pid from a tty switch to a tty (tty1 for example) gdb --pid `pidof gnome-shell` set logging on set logging file /home/fish/gdb.txt continue switch back to gnome (tty7 or tty8) & when the crash occurs switch back to tty1 tape bt bt full to get all the backtrace in /home/fish/gdb.txt
(In reply to comment #13) > (In reply to comment #12) > > > > 1. Well, what happens is that GNOME informs me that it closed. > That gnome-shell crash or something was wrong ? > Apparently gnome-shell did not crash. What I am getting is this dialogue: [QUOTE] Oh No! Something has gone wrong. A problem has occured and the system can't recover. Please log out and try again. [ Log Out ] [/QUOTE] > > 2. How do I generate the backtrace? > > By attaching gdb to gnome-shell pid from a tty > switch to a tty (tty1 for example) > > gdb --pid `pidof gnome-shell` > set logging on > set logging file /home/fish/gdb.txt > continue > > switch back to gnome (tty7 or tty8) > > & when the crash occurs switch back to tty1 > tape > bt > bt full > to get all the backtrace in /home/fish/gdb.txt Apparently, it's not gnome-shell that crashed: [QUOTE] Loaded symbols for /lib/libplds4.so 0xffffe430 in __kernel_vsyscall () (gdb) set logging on Copying output to gdb.txt. (gdb) set logging file /home/fish/gdb.txt (gdb) set logging file /home/shlomif/gdb.txt (gdb) continue Continuing. [New Thread 0xad3ffb70 (LWP 26374)] [Thread 0xad3ffb70 (LWP 26374) exited] [New Thread 0xad3ffb70 (LWP 26397)] [New Thread 0xa39e9b70 (LWP 26398)] [New Thread 0xa41eab70 (LWP 26399)] Program received signal SIGHUP, Hangup. 0xffffe430 in __kernel_vsyscall () (gdb) Continuing. [Thread 0xad3ffb70 (LWP 26397) exited] [Thread 0xa41eab70 (LWP 26399) exited] [Thread 0xa39e9b70 (LWP 26398) exited] [Thread 0xb38ffb70 (LWP 26280) exited] [Thread 0xae4ffb70 (LWP 26282) exited] [Thread 0xaeefeb70 (LWP 26281) exited] [Thread 0xb42cdb70 (LWP 26279) exited] Program terminated with signal SIGHUP, Hangup. The program no longer exists. (gdb) The program is not being run. (gdb) [/QUOTE]
(In reply to comment #14) > (In reply to comment #13) > > (In reply to comment #12) > > > > > > 1. Well, what happens is that GNOME informs me that it closed. > > That gnome-shell crash or something was wrong ? > > > > Apparently gnome-shell did not crash. What I am getting is this dialogue: ok. so you can probably simply close the window « something is wrong » with a ALT+F4. We're trying in fact to figure which program is crashing @ the start of the session. When closing this windows you'll be able to use gnome3 without problem.
(In reply to comment #15) > (In reply to comment #14) > > (In reply to comment #13) > > > (In reply to comment #12) > > > > > > > > 1. Well, what happens is that GNOME informs me that it closed. > > > That gnome-shell crash or something was wrong ? > > > > > > > Apparently gnome-shell did not crash. What I am getting is this dialogue: > > > ok. > so you can probably simply close the window « something is wrong » with a > ALT+F4. > We're trying in fact to figure which program is crashing @ the start of the > session. > When closing this windows you'll be able to use gnome3 without problem. I see. Yes, I guess you're right. It's still very misleading. Regards, -- Shlomi Fish
(In reply to comment #15) > (In reply to comment #14) > > (In reply to comment #13) > > > (In reply to comment #12) > > > > > > > > 1. Well, what happens is that GNOME informs me that it closed. > > > That gnome-shell crash or something was wrong ? > > > > > > > Apparently gnome-shell did not crash. What I am getting is this dialogue: > > > ok. > so you can probably simply close the window « something is wrong » with a > ALT+F4. > We're trying in fact to figure which program is crashing @ the start of the > session. > When closing this windows you'll be able to use gnome3 without problem. Maybe it's a missing gnome-shell.desktop file. Create a gnome-shell.desktop file with the following content: [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= Store it in /usr/share/gnome/autostart/ Works here on Cauldron i586 See also: https://forums.mageia.org/en/viewtopic.php?f=15&t=695&start=30 chhers, Bernd
CC: (none) => bernd.deinzer
Everything is back to normal since a few days. Looks like the last gnome-shell update has solved the problem
thanks, then i close the bugreport. Reopen it if the bug reappear.
Status: NEW => RESOLVEDResolution: (none) => FIXED