Hide Forgot
Description of problem: gnome-shell crashes every time I move a window of a graphical application running from terminal to another workspace Version-Release number of selected component (if applicable): GNOME Shell 3.2.1 Steps to Reproduce: 1. Run any graphical application from gnome-terminal 2. Move the window of the application to another workspace (both through the window context menu or by dragging it in "gnome-shell overview") 3. gnome-shell crashes and restarts; requires logout if repeated
Can you get a backtrace? ABRT will do this automatically if enabled
ABRT for some reason does not track the bug (I guess it never happened to me that ABRT tracked a shell restart). Can you advice me how to generate it manually?
Hmm, ABRT generally seems to work fine to send us lots of gnome-shell backtraces, not sure why it wouldn't work for you. Manually: As root: debuginfo install gdb From a virtual terminal gdb -p `/sbin/pidof gnome-shell` (gdb) continue Switch back to the desktop, reproduce the bug - things will hang - switch back to the virtual terminal (gdb) set logging on (gdb) backtrace (gdb) quit Then attach the resulting gdb.txt here
Created attachment 552035 [details] Manually generated backtrace
> As root: > > debuginfo install gdb I'm sorry - I meant to say 'debuginfo install gnome-shell' - if you can repeat after doing that that would be appreciated! > 1. Run any graphical application from gnome-terminal Are you sure it's any application, or is it specific applications? As far as I can tell from the partial backtrace without debug symbols, it seems like it might be hitting a crash that only occurs for windows that aren't associated with an application and .desktop file.
Created attachment 552383 [details] broken "backtrace" after debuginfos installed Uf, the behaviour is quite sneaky now. I didn't install all the debuginfos because it would take over 500MB, so I installed only these: 'yum --enablerepo fedora-debuginfo,updates-debuginfo install gnome-shell-debuginfo gnome-menus-debuginfo gnome-desktop3-debuginfo' Maybe that was the mistake but I don't really know. As I said, after this the behaviour is quite strange. Firstly, when I run an application from terminal (my own qt application './t6' here), I can't change the workspace using the window context menu anymore. It simply does NOTHING. When I drag it to another workspace at the "shell overview", gnome-shell crashes as intended. The new attachment comes from this. But for some reason, it does not contain anything (?!). I should maybe say that after I started gdb using 'gdb -p `/sbin/pidof gnome-shell`', there was (among others) a line '/usr/bin/gnome-shell (deleted): No such file or directory.' Another strange behaviour is that before I installed debuginfos, gnome-shell kept crashing in case of e.g. 'gedit' as well. Now it does not crash. It still is not possible to change the ORIGINAL workspace using the context menu. But when I change the workspace using the "overview" (as I said, for gedit it does not crash anymore), the context menu suddenly starts working properly so I can move the window elsewhere using it. Unless I move it to the original workspace where it stops working again. So do I really need to install all the debuginfos or what to do now?
A line '/usr/bin/gnome-shell (deleted)' usually means that prelink ran on your system between the time that gnome-shell was started and the time that the crash occurred. I'd certainly appreciated it if you can install all debuginfos - it would keep me from having to ask for more if there are more ones missing, but if you are really tight on disk space, if you can just add mutter-debuginfo gtk3-debuginfo gjs-debuginfo to the ones above, that's probably enough. (Even just gnome-shell debuginfo would be enough... that's not your problem) In terms of whether changing the workspace from the context menu - note the behavior in the overview: - Empty workspaces are deleted, except for the last one - If you move a window to the last empty workspace, a new one is added This also applies via the context menu - maybe that's affecting your testing? E.g. Workspace 1: window A Workspace 2: window B Workspace 3: Empty And I move window B to workspace 3, I'll end up with Workspace 1: window A Workspace 2: Empty Workspace 3: window B Which is then changed to Workspace 1: window A Workspace 2: window B Workspace 3: Empty by the above rules.
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '16'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.