After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 686011 - gnome-shell 3.6 crashes when creating a new virtual desktop
gnome-shell 3.6 crashes when creating a new virtual desktop
Status: RESOLVED DUPLICATE of bug 681399
Product: gnome-shell
Classification: Core
Component: general
3.6.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2012-10-12 07:47 UTC by Canek Peláez Valdés
Modified: 2012-10-12 07:53 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Canek Peláez Valdés 2012-10-12 07:47:18 UTC 
I'm getting a reproducible crash when creating a new virtual desktop by dragging an application between two existing virtual desktops (or to the top of all the existing ones). It's easier to reproduce if several applications are opened; five or six are enough. Put one application in its own virtual desktop, and then from the overview drag the bottom one to the top, creating a new virtual desktop for it. After two or three times of doing this, gnome-shell will segfault.

I'm running Gentoo, with the following component versions:

glib-2.34.0
clutter-1.12.0
mutter-3.6.0
gnome-shell-3.6.0

I don't think any other package is related, since  I only had to rebuild those packages with debug symbols to get the following backtrace:

Program received signal SIGSEGV, Segmentation fault.
0x00007ffff71e5d36 in g_action_group_query_action (action_group=0x0, action_name=0x254ce80 "bookmarks", enabled=0x7fffffffc8ec, parameter_type=0x7fffffffc8f0, state_type=0x0, state_hint=0x0, 
    state=0x7fffffffc8e0) at gactiongroup.c:748
748     gactiongroup.c: No such file or directory.
        in gactiongroup.c
(gdb) bt

+ Trace 231019

  • #0 g_action_group_query_action
    at gactiongroup.c line 748
  • #1 g_action_muxer_action_added
    at gactionmuxer.c line 195
  • #2 g_cclosure_marshal_VOID__STRING
    at gmarshal.c line 964
  • #3 g_closure_invoke
    at gclosure.c line 777
  • #4 signal_emit_unlocked_R
    at gsignal.c line 3551
  • #5 g_signal_emit_valist
    at gsignal.c line 3300
  • #6 g_signal_emit
    at gsignal.c line 3356
  • #7 g_action_group_action_added
    at gactiongroup.c line 611
  • #8 g_dbus_action_group_describe_all_done
    at gdbusactiongroup.c line 266
  • #9 g_simple_async_result_complete
    at gsimpleasyncresult.c line 775
  • #10 g_dbus_connection_call_done
    at gdbusconnection.c line 5339
  • #11 g_simple_async_result_complete
    at gsimpleasyncresult.c line 775
  • #12 complete_in_idle_cb
    at gsimpleasyncresult.c line 787
  • #13 g_idle_dispatch
    at gmain.c line 4806
  • #14 g_main_dispatch
    at gmain.c line 2715
  • #15 g_main_context_dispatch
    at gmain.c line 3219
  • #16 g_main_context_iterate
    at gmain.c line 3290
  • #17 g_main_loop_run
    at gmain.c line 3484
  • #18 meta_run
    at core/main.c line 545
  • #19 main
    at main.c line 414 

Any other information you need, please tell me and I will try to proportionate it.
Comment 1 Florian Müllner 2012-10-12 07:53:53 UTC 
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 681399 ***