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 744708 - 3.15.4: segfaults inside gnome-boxes
3.15.4: segfaults inside gnome-boxes
Status: RESOLVED DUPLICATE of bug 743412
Product: gnome-shell
Classification: Core
Component: general
3.15.x
Other Linux
: Normal major
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2015-02-18 13:47 UTC by Dominique Leuenberger
Modified: 2015-02-18 14:19 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Dominique Leuenberger 2015-02-18 13:47:38 UTC 
So far I rebuilt a new live Image based on GNOME 3.15.90 (what has been released so far); which still means gnome-shell 3.15.4.

When starting the imagae inside a gnome-boxes VM, gnome-shell segfaults:

GNU gdb (GDB; openSUSE Factory) 7.8.1
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-suse-linux".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://bugs.opensuse.org/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/bin/gnome-shell...Reading symbols from /usr/lib/debug/usr/bin/gnome-shell.debug...done.
done.
[New LWP 1489]
[New LWP 1492]
[New LWP 1490]
[New LWP 1491]
[New LWP 1495]
[New LWP 1493]
[New LWP 1494]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Core was generated by `/usr/bin/gnome-shell'.
Program terminated with signal SIGSEGV, Segmentation fault.

+ Trace 234664

  • #0 g_str_hash
    at ghash.c line 1859
  • #0 g_str_hash
    at ghash.c line 1859
  • #1 output_key_hash
    at backends/meta-monitor-config.c line 157
  • #2 config_hash
    at backends/meta-monitor-config.c line 187
  • #3 g_hash_table_lookup_node
    at ghash.c line 375
  • #4 g_hash_table_lookup
    at ghash.c line 1147
  • #5 meta_monitor_config_get_stored
    at backends/meta-monitor-config.c line 846
  • #6 meta_monitor_config_apply_stored
    at backends/meta-monitor-config.c line 1045
  • #7 meta_monitor_manager_constructed
    at backends/meta-monitor-manager.c line 208
  • #8 g_object_new_internal
    at gobject.c line 1814
  • #9 g_object_newv
    at gobject.c line 1922
  • #10 g_object_new
    at gobject.c line 1614
  • #11 meta_backend_real_post_init
    at backends/meta-backend.c line 157
  • #12 meta_backend_x11_post_init
    at backends/x11/meta-backend-x11.c line 421
  • #13 meta_init
    at core/main.c line 358
  • #14 main
    at main.c line 429
  • #0 g_str_hash
    at ghash.c line 1859
  • #1 output_key_hash
    at backends/meta-monitor-config.c line 157
  • #2 config_hash
    at backends/meta-monitor-config.c line 187
  • #3 g_hash_table_lookup_node
    at ghash.c line 375
  • #4 g_hash_table_lookup
    at ghash.c line 1147
  • #5 meta_monitor_config_get_stored
    at backends/meta-monitor-config.c line 846
  • #6 meta_monitor_config_apply_stored
    at backends/meta-monitor-config.c line 1045
  • #7 meta_monitor_manager_constructed
    at backends/meta-monitor-manager.c line 208
  • #8 g_object_new_internal
    at gobject.c line 1814
  • #9 g_object_newv
    at gobject.c line 1922
  • #10 g_object_new
    at gobject.c line 1614
  • #11 meta_backend_real_post_init
    at backends/meta-backend.c line 157
  • #12 meta_backend_x11_post_init
    at backends/x11/meta-backend-x11.c line 421
  • #13 meta_init
    at core/main.c line 358
  • #14 main
    at main.c line 429
  • #0 g_str_hash
    at ghash.c line 1859
  • #1 output_key_hash
    at backends/meta-monitor-config.c line 157
  • #2 config_hash
    at backends/meta-monitor-config.c line 187
  • #3 g_hash_table_lookup_node
    at ghash.c line 375
  • #4 g_hash_table_lookup
    at ghash.c line 1147
  • #5 meta_monitor_config_get_stored
    at backends/meta-monitor-config.c line 846
  • #6 meta_monitor_config_apply_stored
    at backends/meta-monitor-config.c line 1045
  • #7 meta_monitor_manager_constructed
    at backends/meta-monitor-manager.c line 208
  • #8 g_object_new_internal
    at gobject.c line 1814
  • #9 g_object_newv
    at gobject.c line 1922
  • #10 g_object_new
    at gobject.c line 1614
  • #11 meta_backend_real_post_init
    at backends/meta-backend.c line 157
  • #12 meta_backend_x11_post_init
    at backends/x11/meta-backend-x11.c line 421
  • #13 meta_init
    at core/main.c line 358
  • #14 main
    at main.c line 429 


I seem not to have such issues on my physical machine running the same packages though.
Comment 1 Dominique Leuenberger 2015-02-18 13:56:56 UTC 
Supposedly a DUP of bug 743412; just added that patch to my pkg and will test shortly.
Comment 2 Dominique Leuenberger 2015-02-18 14:19:20 UTC 
DUP confirmed - added patch to mutter and all is fine; closing.

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