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 719573 - BatMatch X window error when launching
BatMatch X window error when launching
Status: RESOLVED FIXED
Product: mutter
Classification: Core
Component: general
3.10.x
Other Linux
: Normal normal
: ---
Assigned To: mutter-maint
mutter-maint
Depends on:
Blocks:
 
 
Reported: 2013-11-29 18:25 UTC by Travis Glenn Hansen
Modified: 2014-12-30 04:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Xorg log (52.40 KB, text/x-log)
2013-11-29 18:28 UTC, Travis Glenn Hansen
Details
backtrace (3.15 KB, text/plain)
2013-11-29 18:28 UTC, Travis Glenn Hansen
Details
backtrace (2.75 KB, text/x-log)
2013-12-06 06:49 UTC, Travis Glenn Hansen
Details

Description Travis Glenn Hansen 2013-11-29 18:25:26 UTC
I have dell xps 15 (latest model with 3200x1800 resolution touch screen) with optimus setup.  When running with strictly the intel chip all works fine.  When running with the binary nvidia drivers (modesetting for intel etc) I can launch X fine but attempting to start mutter results in:

# mutter-nvidia-fail.txt [plain_text]
Window manager warning: Log level 6: The program 'mutter' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadMatch (invalid parameter attributes)'.
  (Details: serial 348 error_code 8 request_code 140 minor_code 30)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the GDK_SYNCHRONIZE environment
   variable to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
Comment 1 Travis Glenn Hansen 2013-11-29 18:28:05 UTC
Created attachment 263152 [details]
Xorg log
Comment 2 Travis Glenn Hansen 2013-11-29 18:28:48 UTC
Created attachment 263153 [details]
backtrace
Comment 3 Travis Glenn Hansen 2013-11-29 18:30:05 UTC
thansen@libertas ~ $ xrandr --listproviders
Providers: number : 2
Provider 0: id: 0x2bb cap: 0x1, Source Output crtcs: 0 outputs: 0 associated providers: 1 name:NVIDIA-0
Provider 1: id: 0x48 cap: 0x2, Sink Output crtcs: 3 outputs: 6 associated providers: 1 name:modesetting

thansen@libertas ~ $ xrandr -q
Screen 0: minimum 8 x 8, current 3200 x 1800, maximum 16384 x 16384
eDP-0 connected 3200x1800+0+0 (normal left inverted right x axis y axis) 346mm x 194mm
   3200x1800      60.0*+
   2048x1536      60.0  
   1920x1440      60.0  
   1856x1392      60.0  
   1792x1344      60.0  
   1600x1200      60.0  
   1400x1050      60.0  
   1280x1024      60.0  
   1280x960       60.0  
   1024x768       60.0     60.0  
   960x720        60.0  
   928x696        60.1  
   896x672        60.0  
   800x600        60.0     60.3     56.2  
   700x525        60.0  
   640x512        60.0  
   640x480        60.0     59.9  
   512x384        60.0  
   400x300        60.3     56.3  
   320x240        60.1  
VGA-0 disconnected (normal left inverted right x axis y axis)
DisplayPort-0 disconnected (normal left inverted right x axis y axis)
HDMI-0 disconnected (normal left inverted right x axis y axis)
DisplayPort-1 disconnected (normal left inverted right x axis y axis)
HDMI-1 disconnected (normal left inverted right x axis y axis)
Comment 4 Owen Taylor 2013-12-01 13:47:49 UTC
Is it possible for you to install debug symbols? (The details of how to do this will be specific to your distribution.) The backtrace you provided here without debug symbols is unfortunately not very useful in figuring out what is going wrong.
Comment 5 Travis Glenn Hansen 2013-12-01 15:19:10 UTC
Owen

What additional packages need debug symbols?  I built mutter with them (on arch currently) but can certainly look into the others..
Comment 6 Owen Taylor 2013-12-02 14:02:24 UTC
(In reply to comment #5)
> Owen
> 
> What additional packages need debug symbols?  I built mutter with them (on arch
> currently) but can certainly look into the others..

The backtrace shows missing symbols from:

 glib
 GTK+
 libX11
 libXrandr

Can you also provide the output of xdpyinfo -ext all?
Comment 7 Travis Glenn Hansen 2013-12-06 06:49:40 UTC
Created attachment 263636 [details]
backtrace
Comment 8 Travis Glenn Hansen 2013-12-06 06:51:28 UTC
Owen in working with Jasper I have additionally applied the patch available here: https://bugzilla.gnome.org/show_bug.cgi?id=719790 which seems to have resolved the issue.  I haven't replaced my system binary yet for a complete test, but it appears to have resolved the issue on the surface anyhow.
Comment 9 Travis Glenn Hansen 2013-12-10 21:44:22 UTC
With the above patch applied I get a working solution.  However CPU usage is very high for gnome-shell.  shell sits around 30% cpu and spikes to 100% when going in and out of overview mode (neither of which happen when not using binary nvidia drivers).

perf top -p `pidof gnome-shell`

produces

14.47% libglib
8.66% libnvidia-glcore
8.53 libGL
...

Additionally an strace shows unfinite calls to:

clock_gettime(CLOCK_MONOTONIC, {39326, 194407727}) = 0

Which also do not appear when binary drivers are out of the mix.
Comment 10 Jan Alexander Steffens (heftig) 2014-01-25 20:24:33 UTC
Should that patch be backported to 3.10?

(arch downstream bug: https://bugs.archlinux.org/task/38035 )
Comment 11 Jasper St. Pierre (not reading bugmail) 2014-12-30 03:09:58 UTC
Fixed when the other bug was fixed.
Comment 12 Travis Glenn Hansen 2014-12-30 04:27:57 UTC
Fairly certain this has not been fixed.  I tried again with 3.14 and got the same error.
Comment 13 Jasper St. Pierre (not reading bugmail) 2014-12-30 04:47:18 UTC
Can you re-test with git master and get a new backtrace for me?