Hide Forgot
Description of problem: I have the following multi-monitor setup: * two screens, one primary, one secondary * virtual workspaces only on the primary monitor (the default) This morning, I launched Liferea, and it opened on the secondary monitor. Note: There was only one virtual workspace at the time (plus the empty one that is always present) I tried moving it: * to the primary monitor * to a new workspace, by dragging and dropping the Liferea window thumbnail directly above the current/first workspace The important point (I guess) is that I tried to do the above two points in only one drag and drop. That seems to have confused GNOME Shell, and it crashed. Version-Release number of selected component: gnome-shell-3.10.2-2.fc20 Additional info: reporter: libreport-2.1.9 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: meta_bug executable: /usr/bin/gnome-shell kernel: 3.11.8-300.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #2 meta_bug at core/util.c:422 #3 meta_workspace_index at core/workspace.c:710 #4 meta_workspace_activate_with_focus at core/workspace.c:553 #5 ffi_call_unix64 at ../src/x86/unix64.S:76 #6 ffi_call at ../src/x86/ffi64.c:522 #7 gjs_invoke_c_function at gi/function.c:894 #8 function_call at gi/function.c:1203 #9 CallJSNative at /usr/src/debug/mozjs17.0.0/js/src/jscntxtinlines.h:372 #10 js::InvokeKernel at /usr/src/debug/mozjs17.0.0/js/src/jsinterp.cpp:345 #11 js::Interpret at /usr/src/debug/mozjs17.0.0/js/src/jsinterp.cpp:2414 Potential duplicate: bug 912556
Created attachment 828500 [details] File: backtrace
Created attachment 828501 [details] File: cgroup
Created attachment 828502 [details] File: core_backtrace
Created attachment 828503 [details] File: dso_list
Created attachment 828504 [details] File: environ
Created attachment 828505 [details] File: limits
Created attachment 828506 [details] File: maps
Created attachment 828507 [details] File: open_fds
Created attachment 828508 [details] File: proc_pid_status
Created attachment 828509 [details] File: var_log_messages
Another user experienced a similar problem: I was moving an application window to another workspace in the overview mode. reporter: libreport-2.1.10 backtrace_rating: 4 cmdline: gnome-shell --sm-client-id 1075c25a04c2ef8df4137787943798685900000014510000 crash_function: meta_bug executable: /usr/bin/gnome-shell kernel: 3.12.6-300.fc20.x86_64 package: gnome-shell-3.10.2.1-3.fc20 reason: gnome-shell killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: I have a two-screen resolution, I was was moving windows from my secondary screen to one of the panels on the right side of the primary screen. reporter: libreport-2.1.11 backtrace_rating: 3 cmdline: /usr/bin/gnome-shell crash_function: meta_bug executable: /usr/bin/gnome-shell kernel: 3.12.8-300.fc20.x86_64 package: gnome-shell-3.10.2.1-3.fc20 reason: gnome-shell killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: When I want to open Terminal screen just flash - Terminal opens for a few miliseconds and then shuts down. Mabe it's because of my playing with Terminal settings when I changed starting command to this -> echo "Hello!" but I don't think so... reporter: libreport-2.1.11 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: meta_bug executable: /usr/bin/gnome-shell kernel: 3.12.8-300.fc20.x86_64 package: gnome-shell-3.10.3-2.fc20 reason: gnome-shell killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: Gnome shell crashed during window dragging through the screen. reporter: libreport-2.1.12 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: meta_bug executable: /usr/bin/gnome-shell kernel: 3.13.5-200.fc20.x86_64 package: gnome-shell-3.10.4-1.fc20 reason: gnome-shell killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: Crashed when I moved a window from secondary screen to a different desktop then I was looking on on primary screen. I was moving the window preview in the overview. Usualy it just bounces the window back to secondary screen but this time it surprisingly crashed. reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: meta_bug executable: /usr/bin/gnome-shell kernel: 3.16.6-200.fc20.x86_64 package: gnome-shell-3.10.4-9.fc20 reason: gnome-shell killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 EOL if it remains open with a Fedora 'version' of '20'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 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 change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. 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.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.