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 744156 - gdm greeter fails to load due to XRANDR error on NVIDIA
gdm greeter fails to load due to XRANDR error on NVIDIA
Status: RESOLVED OBSOLETE
Product: mutter
Classification: Core
Component: general
3.15.x
Other Linux
: Normal normal
: ---
Assigned To: mutter-maint
mutter-maint
Depends on:
Blocks:
 
 
Reported: 2015-02-08 03:44 UTC by darkxst
Modified: 2021-07-05 13:47 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
gdm greeter log (14.18 KB, text/x-log)
2015-02-08 03:44 UTC, darkxst 		Details

Description darkxst 2015-02-08 03:44:12 UTC 
Created attachment 296362 [details]
gdm greeter log

On my system with Nvidia Blob, can't seem to get the gdm greeter started seems to be an XRANDR error. 

(gnome-settings-daemon:5734): AccountsService-WARNING **: SetInputSources call failed: GDBus.Error:org.freedesktop.Accounts.Error.PermissionDenied: Authentication is required
X Error of failed request:  BadMatch (invalid parameter attributes)
  Major opcode of failed request:  140 (RANDR)
  Minor opcode of failed request:  7 (RRSetScreenSize)
  Serial number of failed request:  198
  Current serial number in output stream:  199
Comment 1 darkxst 2015-02-09 07:47:36 UTC 
Booting with only a single monitor seems to avoid the BadMatch error above, however then I get another crash ;( 

n_crtcs is clearly bogus in f #9

+ Trace 234633

Thread 1 (Thread 0x7f41c1cc0a40 (LWP 5800))

  • #0 strchrnul
    at ../sysdeps/x86_64/strchr.S line 32
  • #1 _IO_vfprintf_internal
    at printf-parse.h line 108
  • #2 _IO_vfprintf_internal
    at vfprintf.c line 1315
  • #3 __GI___vasprintf_chk
    at vasprintf_chk.c line 66
  • #4 g_vasprintf
    at /usr/include/x86_64-linux-gnu/bits/stdio2.h line 210
  • #5 g_vasprintf
    at /build/buildd/glib2.0-2.43.4~20150205.r1+git7417198/./glib/gprintf.c line 316
  • #6 g_strdup_vprintf
    at /build/buildd/glib2.0-2.43.4~20150205.r1+git7417198/./glib/gstrfuncs.c line 507
  • #7 g_logv
    at /build/buildd/glib2.0-2.43.4~20150205.r1+git7417198/./glib/gmessages.c line 948
  • #8 g_log
    at /build/buildd/glib2.0-2.43.4~20150205.r1+git7417198/./glib/gmessages.c line 1079
  • #9 meta_monitor_manager_xrandr_apply_configuration
    at backends/x11/meta-monitor-manager-xrandr.c line 984
  • #10 apply_configuration
    at backends/meta-monitor-config.c line 875
  • #11 meta_monitor_config_make_default
    at backends/meta-monitor-config.c line 1385
  • #12 meta_monitor_manager_constructed
    at backends/meta-monitor-manager.c line 209
  • #13 g_object_new_internal
    at /build/buildd/glib2.0-2.43.4~20150205.r1+git7417198/./gobject/gobject.c line 1814
  • #14 g_object_newv
    at /build/buildd/glib2.0-2.43.4~20150205.r1+git7417198/./gobject/gobject.c line 1922
  • #15 g_object_new
    at /build/buildd/glib2.0-2.43.4~20150205.r1+git7417198/./gobject/gobject.c line 1614
  • #16 meta_backend_real_post_init
    at backends/meta-backend.c line 157
  • #17 meta_backend_x11_post_init
    at backends/x11/meta-backend-x11.c line 421
  • #18 meta_init
    at core/main.c line 358
  • #19 0x0000000000401dbb in
  • #20 __libc_start_main
    at libc-start.c line 287
  • #21 0x0000000000402175 in 






Comment 2


Jasper St. Pierre (not reading bugmail)





          2015-02-09 23:33:46 UTC
        



Why are you getting bogus values?






Comment 3


darkxst





          2015-02-10 01:08:16 UTC
        



ignore that trace, it was caused by a bad patch trying to track down the BadMatch error... 

gtk 3.15.x with mutter 3.14 will boot to greeter with a single monitor only
gtk 3.15 with mutter 3.15 seems to get the Randr errors 99% of the time, have got to the greeter once or twice though.

Can also reproduce on login, but not when starting gnome-shell within a running session :(






Comment 4


darkxst





          2015-03-06 01:46:52 UTC
        



I am still seeing this issue with 3.15.91. gdm consistently fails with XRANDR error whenever I try to boot with more than one monitor attached. Everything is working fine now though with single monitor only.






Comment 5


GNOME Infrastructure Team





          2021-07-05 13:47:47 UTC
        



GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org.
As part of that, we are mass-closing older open tickets in bugzilla.gnome.org
which have not seen updates for a longer time (resources are unfortunately
quite limited so not every ticket can get handled).

If you can still reproduce the situation described in this ticket in a recent
and supported software version, then please follow
  https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines
and create a new ticket at
  https://gitlab.gnome.org/GNOME/mutter/-/issues/

Thank you for your understanding and your help.