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 742372 - Mutter 3.14.3 hangs on nvidia 346.22
Mutter 3.14.3 hangs on nvidia 346.22
Status: RESOLVED OBSOLETE
Product: mutter
Classification: Core
Component: general
3.14.x
Other Linux
: Normal major
: ---
Assigned To: mutter-maint
mutter-maint
Depends on:
Blocks:
 
 
Reported: 2015-01-05 12:07 UTC by Mariusz Ceier
Modified: 2015-03-07 11:35 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Xorg configuration (1.29 KB, application/octet-stream)
2015-01-05 12:07 UTC, Mariusz Ceier 		Details

Description Mariusz Ceier 2015-01-05 12:07:23 UTC 
Created attachment 293809 [details]
Xorg configuration

On laptop with hybrid intel+nvidia graphics, mutter hangs:

# gdb mutter
(gdb) run --replace
Starting program: /usr/bin/mutter --replace
warning: Could not load shared library symbols for linux-vdso.so.1.
Do you need "set solib-search-path" or "set sysroot"?
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
[New Thread 0x7fffe7c34700 (LWP 3667)]
[New Thread 0x7fffe5f07700 (LWP 3668)]
X Error of failed request:  BadMatch (invalid parameter attributes)
  Major opcode of failed request:  139 (RANDR)
  Minor opcode of failed request:  30 (RRSetOutputPrimary)
  Serial number of failed request:  167
  Current serial number in output stream:  170
^C
Program received signal SIGINT, Interrupt.
0x00007ffff1014f0b in _XReply (dpy=0x667d80, rep=0x7fffffffadd0, extra=0, discard=0) at /var/tmp/portage/x11-libs/libX11-1.6.2/work/libX11-1.6.2/src/xcb_io.c:596
596 /var/tmp/portage/x11-libs/libX11-1.6.2/work/libX11-1.6.2/src/xcb_io.c: Nie ma takiego pliku ani katalogu.
(gdb) bt

+ Trace 234498

  • #0 _XReply
    at /var/tmp/portage/x11-libs/libX11-1.6.2/work/libX11-1.6.2/src/xcb_io.c line 596
  • #1 ??
    from /usr/lib64/opengl/nvidia/lib/libGL.so.1
  • #2 ??
    from /usr/lib64/opengl/nvidia/lib/libGL.so.1
  • #3 ??
    from /usr/lib64/opengl/nvidia/lib/libGL.so.1
  • #4 ??
    from /usr/lib64/opengl/nvidia/lib/libGL.so.1
  • #5 ??
    from /usr/lib64/libnvidia-glcore.so.346.22
  • #6 ??
    from /usr/lib64/libnvidia-glcore.so.346.22
  • #7 ??
    from /usr/lib64/libnvidia-glcore.so.346.22
  • #8 ??
    from /usr/lib64/libnvidia-glcore.so.346.22
  • #9 ??
    from /usr/lib64/libnvidia-glcore.so.346.22
  • #10 ??
    from /usr/lib64/libnvidia-glcore.so.346.22
  • #11 ??
    from /usr/lib64/libnvidia-glcore.so.346.22
  • #12 ??
    from /usr/lib64/libnvidia-glcore.so.346.22
  • #13 ??
    from /usr/lib64/libnvidia-glcore.so.346.22
  • #14 ??
    from /usr/lib64/libnvidia-glcore.so.346.22
  • #15 ??
    from /usr/lib64/opengl/nvidia/lib/libGL.so.1
  • #16 _dl_fini
    at dl-fini.c line 257
  • #17 __run_exit_handlers
    at exit.c line 82
  • #18 __GI_exit
    at exit.c line 104
  • #19 _XDefaultError
    at /var/tmp/portage/x11-libs/libX11-1.6.2/work/libX11-1.6.2/src/XlibInt.c line 1414
  • #20 _XError
    at /var/tmp/portage/x11-libs/libX11-1.6.2/work/libX11-1.6.2/src/XlibInt.c line 1463
  • #21 handle_error
    at /var/tmp/portage/x11-libs/libX11-1.6.2/work/libX11-1.6.2/src/xcb_io.c line 213
  • #22 handle_response
    at /var/tmp/portage/x11-libs/libX11-1.6.2/work/libX11-1.6.2/src/xcb_io.c line 325
  • #23 _XReply
    at /var/tmp/portage/x11-libs/libX11-1.6.2/work/libX11-1.6.2/src/xcb_io.c line 627
  • #24 DPMSCapable
    at /var/tmp/portage/x11-libs/libXext-1.3.3/work/libXext-1.3.3/src/DPMS.c line 137
  • #25 meta_monitor_manager_xrandr_read_current
    at backends/x11/meta-monitor-manager-xrandr.c line 392
  • #26 read_current_config
    at backends/meta-monitor-manager.c line 66
  • #27 meta_monitor_manager_constructed
    at backends/meta-monitor-manager.c line 226
  • #28 g_object_new_internal
    at /var/tmp/portage/dev-libs/glib-2.42.1/work/glib-2.42.1/gobject/gobject.c line 1814
  • #29 g_object_newv
    at /var/tmp/portage/dev-libs/glib-2.42.1/work/glib-2.42.1/gobject/gobject.c line 1922
  • #30 g_object_new
    at /var/tmp/portage/dev-libs/glib-2.42.1/work/glib-2.42.1/gobject/gobject.c line 1614
  • #31 meta_backend_real_post_init
    at backends/meta-backend.c line 165
  • #32 meta_backend_x11_post_init
    at backends/x11/meta-backend-x11.c line 398
  • #33 meta_init
    at core/main.c line 358
  • #34 main
    at core/mutter.c line 83 

It's regression - since mutter 3.12.2 didn't hang and didn't crash with the same drivers.
I think commit https://git.gnome.org/browse/mutter/commit/?id=3d1d155 has been reverted.

Attaching xorg.conf.
Comment 1 Matheus C. Santos 2015-01-05 13:39:00 UTC 
Exact same problem here.
Comment 2 Mariusz Ceier 2015-01-09 10:58:57 UTC 
Found the commit which removed calls to meta_error_trap_* functions:

https://git.gnome.org/browse/mutter/commit/src/backends/x11/meta-monitor-manager-xrandr.c?id=6c743dad8867eb4fafb664a783d26ec875e72957
Comment 3 Nocturne 2015-01-22 17:22:11 UTC 
Seeing the same issue here.  Seems like is should be an easy fix since it's just a regression.  Wish I had the knowledge to fix it!
Comment 4 Mariusz Ceier 2015-03-07 11:35:39 UTC 
Mutter started working again with nvidia drivers 346.47. Marking this bug as obsolete (I hope you dont mind).