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 725802 - gdm greeter fails to start on nvidia prime laptop
gdm greeter fails to start on nvidia prime laptop
Status: RESOLVED FIXED
Product: mutter
Classification: Core
Component: general
3.10.x
Other Linux
: Normal normal
: ---
Assigned To: mutter-maint
mutter-maint
: 728554 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2014-03-06 08:00 UTC by darkxst
Modified: 2014-04-22 09:14 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description darkxst 2014-03-06 08:00:42 UTC
From downstream launchpad bug.
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1288572

JS ERROR: Exception in callback for signal: sessions-loaded: TypeError: this.primaryMonitor is undefined
LayoutManager<._updateBoxes@/usr/share/gnome-shell/js/ui/layout.js:410
wrapper@resource:///org/gnome/gjs/modules/lang.js:169
LayoutManager<._monitorsChanged@/usr/share/gnome-shell/js/ui/layout.js:489
wrapper@resource:///org/gnome/gjs/modules/lang.js:169 
LayoutManager<._init@/usr/share/gnome-shell/js/ui/layout.js:239
wrapper@resource:///org/gnome/gjs/modules/lang.js:169 
_Base.prototype._construct@resource:///org/gnome/gjs/modules/lang.js:110
Class.prototype._construct/newClass@resource:///org/gnome/gjs/modules/lang.js:204
_initializeUI@/usr/share/gnome-shell/js/ui/main.js:156
_sessionsLoaded@/usr/share/gnome-shell/js/ui/main.js:122
_emit@resource:///org/gnome/gjs/modules/signals.js:124
SessionMode<.init/<@/usr/share/gnome-shell/js/ui/sessionMode.js:161
done@/usr/share/gnome-shell/js/misc/fileUtils.js:33 
 _collectFromDirectoryAsync/
Comment 1 Giovanni Campagna 2014-03-06 12:29:43 UTC
Seems we don't have a primary monitor.

Would be useful to see the output of xrandr in that configuration.
Comment 2 darkxst 2014-03-11 04:49:51 UTC
under gdm/gnome-shell xrandr does not display any outputs, presumably because xrandr --setoutputprovidersource is not completely configured.

under a unity session:
Screen 0: minimum 8 x 8, current 1366 x 768, maximum 8192 x 8192
LVDS-1-0 connected 1366x768+0+0 (normal left inverted right x axis y axis) 293mm x 165mm
   1366x768 60.0*+
   1360x768 59.8 60.0
   1024x768 60.0 60.0
   960x720 60.0
   928x696 60.1
   896x672 60.0
   960x600 60.0
   960x540 60.0
   800x600 60.0 60.3 56.2
   840x525 60.0 59.9
   800x512 60.2
   700x525 60.0
   640x512 60.0
   720x450 59.9
   640x480 60.0 59.9
   680x384 59.8 60.0
   576x432 60.1
   512x384 60.0
   400x300 60.3 56.3
   320x240 60.1
VGA-1-0 disconnected (normal left inverted right x axis y axis)
HDMI-1-0 disconnected (normal left inverted right x axis y axis)
DisplayPort-1-0 disconnected (normal left inverted right x axis y axis)

gnome-shell --replace (from Unity session) crashes reading DPMSCapable

  • #0 g_logv
    at /build/buildd/glib2.0-2.39.91/./glib/gmessages.c line 1038
  • #1 g_log
    at /build/buildd/glib2.0-2.39.91/./glib/gmessages.c line 1071
  • #2 _gdk_x11_display_error_event
    at /build/buildd/gtk+3.0-3.10.7/./gdk/x11/gdkdisplay-x11.c line 2533
  • #3 gdk_x_error
    at /build/buildd/gtk+3.0-3.10.7/./gdk/x11/gdkmain-x11.c line 303
  • #4 _XError
    at ../../src/XlibInt.c line 1463
  • #5 handle_error
    at ../../src/xcb_io.c line 213
  • #6 handle_response
    at ../../src/xcb_io.c line 325
  • #7 _XReply
    at ../../src/xcb_io.c line 627
  • #8 DPMSCapable
    at ../../src/DPMS.c line 137
  • #9 meta_monitor_manager_xrandr_read_current
    at core/monitor-xrandr.c line 355
  • #10 read_current_config
    at core/monitor.c line 376
  • #11 meta_monitor_manager_constructed
    at core/monitor.c line 525
  • #12 g_object_new_internal
    at /build/buildd/glib2.0-2.39.91/./gobject/gobject.c line 1763
  • #13 g_object_newv
    at /build/buildd/glib2.0-2.39.91/./gobject/gobject.c line 1868
  • #14 g_object_new
    at /build/buildd/glib2.0-2.39.91/./gobject/gobject.c line 1568
  • #15 meta_monitor_manager_new
    at core/monitor.c line 489
  • #16 meta_monitor_manager_initialize
    at core/monitor.c line 1405
  • #17 meta_screen_new
    at core/screen.c line 678
  • #18 meta_display_open
    at core/display.c line 910
  • #19 meta_run
    at core/main.c line 553
  • #20 main
    at main.c line 439
  • #0 g_logv
  • #1 g_log
    at /build/buildd/glib2.0-2.39.91/./glib/gmessages.c line 1071
  • #2 _gdk_x11_display_error_event
    at /build/buildd/gtk+3.0-3.10.7/./gdk/x11/gdkdisplay-x11.c line 2533
  • #3 gdk_x_error
    at /build/buildd/gtk+3.0-3.10.7/./gdk/x11/gdkmain-x11.c line 303
  • #4 _XError
    at ../../src/XlibInt.c line 1463
  • #5 handle_error
    at ../../src/xcb_io.c line 213
  • #6 handle_response
    at ../../src/xcb_io.c line 325
  • #7 _XReply
    at ../../src/xcb_io.c line 627
  • #8 DPMSCapable
    at ../../src/DPMS.c line 137
  • #9 meta_monitor_manager_xrandr_read_current
    at core/monitor-xrandr.c line 355
  • #10 read_current_config
    at core/monitor.c line 376
  • #11 meta_monitor_manager_constructed
    at core/monitor.c line 525
  • #12 g_object_new_internal
    at /build/buildd/glib2.0-2.39.91/./gobject/gobject.c line 1763
  • #13 g_object_newv
    at /build/buildd/glib2.0-2.39.91/./gobject/gobject.c line 1868
  • #14 g_object_new
    at /build/buildd/glib2.0-2.39.91/./gobject/gobject.c line 1568
  • #15 meta_monitor_manager_new
    at core/monitor.c line 489
  • #16 meta_monitor_manager_initialize
    at core/monitor.c line 1405
  • #17 meta_screen_new
    at core/screen.c line 678
  • #18 meta_display_open
    at core/display.c line 910
  • #19 meta_run
    at core/main.c line 553
  • #20 main
    at main.c line 439

Comment 3 Giovanni Campagna 2014-03-13 13:20:34 UTC
Is that trace with GDK_SYNCHRONIZE=1?
DPMSCapable is not documented to generate any X error, so this would be a driver bug in nvidia (but one we can easily work around with an error trap)
Comment 4 darkxst 2014-03-14 06:24:27 UTC
checked with the OP, apparently not.

Here is the real trace with GDK_SYNCHRONIZE=1

  • #0 g_logv
    at /build/buildd/glib2.0-2.39.91/./glib/gmessages.c line 1038
  • #1 g_log
    at /build/buildd/glib2.0-2.39.91/./glib/gmessages.c line 1071
  • #2 _gdk_x11_display_error_event
    at /build/buildd/gtk+3.0-3.10.7/./gdk/x11/gdkdisplay-x11.c line 2533
  • #3 gdk_x_error
    at /build/buildd/gtk+3.0-3.10.7/./gdk/x11/gdkmain-x11.c line 303
  • #4 _XError
    at ../../src/XlibInt.c line 1463
  • #5 handle_error
    at ../../src/xcb_io.c line 213
  • #6 handle_response
    at ../../src/xcb_io.c line 325
  • #7 _XReply
    at ../../src/xcb_io.c line 627
  • #8 XSync
    at ../../src/Sync.c line 44
  • #9 _XSyncFunction
    at ../../src/Synchro.c line 35
  • #10 XRRSetOutputPrimary
    at ../../src/XrrOutput.c line 160
  • #11 meta_monitor_manager_xrandr_apply_configuration
    at core/monitor-xrandr.c line 903
  • #12 apply_configuration
    at core/monitor-config.c line 874
  • #13 meta_monitor_config_make_default
    at core/monitor-config.c line 1272
  • #14 meta_monitor_manager_constructed
    at core/monitor.c line 504
  • #15 g_object_new_internal
    at /build/buildd/glib2.0-2.39.91/./gobject/gobject.c line 1763
  • #16 g_object_newv
    at /build/buildd/glib2.0-2.39.91/./gobject/gobject.c line 1868
  • #17 g_object_new
    at /build/buildd/glib2.0-2.39.91/./gobject/gobject.c line 1568
  • #18 meta_monitor_manager_new
    at core/monitor.c line 489
  • #19 meta_monitor_manager_initialize
    at core/monitor.c line 1405
  • #20 meta_screen_new
    at core/screen.c line 678
  • #21 meta_display_open
    at core/display.c line 910
  • #22 meta_run
    at core/main.c line 553
  • #23 main
    at main.c line 439

Comment 5 Matthias Clasen 2014-03-18 18:12:27 UTC
Which version of mutter / gnome-shell is this with ?

Looks like the call to XRRSetOutputPrimary in monitor-xrandr.c:903 has been wrapped in an error trap since last December, so this should not happen anymore
Comment 6 darkxst 2014-03-18 21:16:07 UTC
3.10.4

I see it should be fixed by 55180f5bb3063a491487bedc58550a3571cbdcbd, can this be cherry-picked to 3.10 branch
Comment 7 Rui Matos 2014-04-22 09:02:39 UTC
*** Bug 728554 has been marked as a duplicate of this bug. ***
Comment 8 Rui Matos 2014-04-22 09:14:23 UTC
(In reply to comment #6)
> I see it should be fixed by 55180f5bb3063a491487bedc58550a3571cbdcbd, can this
> be cherry-picked to 3.10 branch

Pushed to gnome-3-10. I don't think there's going to be another release of that branch at this point though.