Version-Release number of selected component:
cmdline: /usr/bin/gnome-shell --wayland --display-server
runlevel: N 5
Thread no. 1 (10 frames)
#4 meta_frame_left_click_event at ui/frames.c:1057
#5 handle_button_press_event at ui/frames.c:1107
#6 meta_ui_frame_handle_event at ui/frames.c:1580
#7 meta_window_handle_ungrabbed_event at core/window.c:7771
#8 meta_display_handle_event at core/events.c:268
#9 event_callback at core/events.c:333
#10 _clutter_event_process_filters at clutter-event.c:1768
#11 emit_pointer_event at clutter-main.c:2022
#12 _clutter_process_event_details at clutter-main.c:2377
#13 _clutter_process_event at clutter-main.c:2537
Created attachment 1011039 [details]
Created attachment 1011040 [details]
Created attachment 1011041 [details]
Created attachment 1011042 [details]
Created attachment 1011043 [details]
Created attachment 1011044 [details]
Created attachment 1011045 [details]
Created attachment 1011046 [details]
Created attachment 1011047 [details]
Created attachment 1011048 [details]
Created attachment 1011049 [details]
Created attachment 1011050 [details]
I hit this when I dragged a virt-manager window from one monitor to another.
this happens when get_control returns META_FRAME_CONTROL_NONE
Fairly sure it's reproducible, but don't know exactly how; it's some weird specific series of inputs.
For me this happens when i do copy paste. If i highlight some text in a terminal or gvim window using the mouse and then switch to a different window or even a different desktop, it crashes.
This also happens when i change desktops quickly after typing in a thunderbird window.
Sorry but not reliably. I want to give as many scenarios as possible so that the cause can be narrowed down. The most reliable case for me is when i highlight something in a terminal or gvim window and switch to another window quickly.
Google'ing the first interesting frame of a backtrace got me here. For some reason abrt-cli report doesn't seem to work lately (just takes forever). I was just using the computer like I normally do, clicking/switching firefox windows and stuff, then suddenly gnom-shell restarted. This is non-wayland, and also under a classic session. I have had the same backtrace onece of twice before, but as I said, abrt-cli report took forever so I gave up then.
# abrt-cli list
reason: gnome-shell killed by SIGABRT
time: Tue 09 Jun 2015 20:05:59 BST
uid: 1000 (Hin-Tak)
#0 0x00000034e2434a98 in raise () at /lib64/libc.so.6
#1 0x00000034e243672a in abort () at /lib64/libc.so.6
#2 0x00000034e4c702a5 in g_assertion_message () at /lib64/libglib-2.0.so.0
#3 0x00000034e4c7033a in g_assertion_message_expr () at /lib64/libglib-2.0.so.0
#4 0x0000003b37e8aa02 in meta_frame_left_click_event () at /lib64/libmutter.so.0
#5 0x0000003b37e87776 in meta_window_handle_ungrabbed_event () at /lib64/libmutter.so.0
#6 0x0000003b37e6a896 in event_callback () at /lib64/libmutter.so.0
#7 0x0000003b3868149d in _clutter_event_process_filters () at /lib64/libclutter-1.0.so.0
#8 0x0000003b386942cb in _clutter_process_event () at /lib64/libclutter-1.0.so.0
#9 0x0000003b386ae309 in _clutter_stage_process_queued_events () at /lib64/libclutter-1.0.so.0
#10 0x0000003b38696539 in clutter_clock_dispatch () at /lib64/libclutter-1.0.so.0
#11 0x00000034e4c49a8a in g_main_context_dispatch () at /lib64/libglib-2.0.so.0
#12 0x00000034e4c49e20 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0
#13 0x00000034e4c4a142 in g_main_loop_run () at /lib64/libglib-2.0.so.0
#14 0x0000003b37e71356 in meta_run () at /lib64/libmutter.so.0
#15 0x00000000004023fd in main ()
*** Bug 1227391 has been marked as a duplicate of this bug. ***
I got sent here.
I can do the gnome-shell crash when using clearlooks-phenix theme.
This theme was adapted for Gnome 3.14.
And it makes gnome-shell crash when I click at the right hand edge of the creen in firefox. Also at the left hand side and bottom but I did less testing there.
Default theme does not show this behaviour. See https://bugzilla.redhat.com/show_bug.cgi?id=1227391 to confirm this is the same issue.
My way of reproducing this issue is very reliable.
I have experienced this issue when using GfxTablet, together with https://bugzilla.redhat.com/show_bug.cgi?id=1215320
Is there anything how I can help to identify and fix it?
(In reply to udo from comment #22)
> My way of reproducing this issue is very reliable.
See https://bugzilla.redhat.com/show_bug.cgi?id=1230326 for details.
gnome-shell sometimes doesn't restart automatically, leaving you with a practically unusable session
FWIW when that happens, go to a tty (ctrl-alt-f2), log in, and run 'DISPLAY=:0 gnome-shell --replace &', and it should start the Shell up again.
obviously that's just a workaround, but handy to know if it tends to happen to you.
Usually have a terminal open I can run --replace from, but i don't think it's fair to expect an average user to do that.
Has this been reported upstream yet?
Don't know offhand, but more or less the same people should see it in both places. Can't hurt to have an upstream report if it hasn't happened yet, though.
(In reply to mchalupa from comment #29)
> Upstream bug:
So we have a patch.
Please verify and push RPMs please.
Also see https://bugzilla.redhat.com/show_bug.cgi?id=1230326 as this clearlook-phenix is not intended from this Gnome release....
mutter-3.16.3-2.fc22 has been submitted as an update for Fedora 22.
* should fix your issue,
* was pushed to the Fedora 22 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing mutter-3.16.3-2.fc22'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
mutter-3.16.3-2.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.