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 727457 - Crash in real_assign_crtcs()
Crash in real_assign_crtcs()
Status: RESOLVED DUPLICATE of bug 725637
Product: gnome-shell
Classification: Core
Component: general
3.10.x
Other Linux
: Normal critical
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2014-04-01 20:04 UTC by Milan Bouchet-Valat
Modified: 2014-05-15 19:38 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Milan Bouchet-Valat 2014-04-01 20:04:12 UTC 
This bug was reported several times in Fedora 20 with gnome-shell 3.10.2. It seems to happen under quite varied conditions. I experienced it myself when resuming from suspend; the unusal detail was that before suspending (or a few seconds before that) I was using a video projector.


https://bugzilla.redhat.com/show_bug.cgi?id=1037138

Core was generated by `/usr/bin/gnome-shell'.
Program terminated with signal SIGSEGV, Segmentation fault.

+ Trace 233425

Thread 1 (Thread 0x7f4793c23a40 (LWP 25540))

  • #0 real_assign_crtcs
    at core/monitor-config.c line 1602
  • #1 real_assign_crtcs
    at core/monitor-config.c line 1770
  • #2 meta_monitor_config_assign_crtcs
    at core/monitor-config.c line 1805
  • #3 apply_configuration
    at core/monitor-config.c line 864
  • #4 _g_closure_invoke_va
    from /lib64/libgobject-2.0.so.0
  • #5 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #6 g_signal_emit
    from /lib64/libgobject-2.0.so.0
  • #7 marshal_dbus_message_to_g_marshaller
    at dbus-gproxy.c line 1736
  • #8 g_closure_invoke
    from /lib64/libgobject-2.0.so.0
  • #9 signal_emit_unlocked_R
    from /lib64/libgobject-2.0.so.0
  • #10 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #11 g_signal_emit
    from /lib64/libgobject-2.0.so.0
  • #12 dbus_g_proxy_emit_remote_signal
    at dbus-gproxy.c line 1789
  • #13 dbus_g_proxy_manager_filter
    at dbus-gproxy.c line 1356
  • #14 dbus_connection_dispatch
    at dbus-connection.c line 4631
  • #15 message_queue_dispatch
    at dbus-gmain.c line 90
  • #16 g_main_context_dispatch
    from /lib64/libglib-2.0.so.0
  • #17 g_main_context_iterate.isra.24
    from /lib64/libglib-2.0.so.0
  • #18 g_main_loop_run
    from /lib64/libglib-2.0.so.0
  • #19 meta_run
    at core/main.c line 556
  • #20 main
    at main.c line 439 






Comment 1


Giovanni Campagna





          2014-05-15 19:38:47 UTC
        



Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.

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