View previous topic :: View next topic |
Author |
Message |
jody l33t
Joined: 16 Oct 2007 Posts: 668 Location: Switzerland
|
Posted: Tue Dec 10, 2013 11:03 am Post subject: [SOLVED]systemd:gnome doesn't start properly (black screen) |
|
|
Hi
I have moved from openRC to systemd and have problems starting gnome.
At the same time i also updated from gnome 2.3.2 to Gnome 3.8.6
When i want to start gnome with
systemctl start gdm
the nivida logo appears for a fraction of a second and then there is only a black screen.
Below are all the messages from the moment i started gdm as shown by journalctl.
There are several warnings, but i have no idea which of these are relevant to the problem...
i suspect this is important, but i am not sure Code: | Dec 10 11:29:47 localhost /usr/bin/dbus-launch[16967]: gnome-session[16967]: WARNING: Could not connect to ConsoleKit: Unable to lookup session information for process '16967'
Dec 10 11:29:47 localhost gnome-session[16967]: WARNING: Could not connect to ConsoleKit: Unable to lookup session information for process '16967'
|
If it is what could be the problem?
I have this installed Code: | [I] sys-auth/consolekit
Available versions: 0.4.5_p20120320-r1 ~0.4.5_p20120320-r2 0.4.6 {acl debug doc pam policykit selinux systemd-units test KERNEL="linux"}
Installed versions: 0.4.6(10:23:15 09/09/13)(acl pam policykit -debug -doc -selinux -systemd-units -test KERNEL="linux")
Homepage: http://www.freedesktop.org/wiki/Software/ConsoleKit
Description: Framework for defining and tracking users, login sessions and seats.
|
Here is the entire journalctl-output created during gnome's start:
Code: | Dec 10 11:29:41 localhost systemd[1]: Starting GNOME Display Manager...
-- Subject: Unit gdm.service has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit gdm.service has begun starting up.
Dec 10 11:29:41 localhost systemd[1]: Started GNOME Display Manager.
-- Subject: Unit gdm.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit gdm.service has finished starting up.
--
-- The start-up result is done.
Dec 10 11:29:41 localhost dbus-daemon[16729]: dbus[16729]: [system] Rejected send message, 1 matched rules; type="method_call", sender=":1.8" (uid=0 pid=16936 comm="/usr/sbin/gdm ") interface="org.freedesktop.DBus.Properties" member="GetAll" error name="(unset)" requested_repl
y="0" destination=":1.9" (uid=0 pid=16939 comm="/usr/libexec/gdm-simple-slave --display-id /org/gn")
Dec 10 11:29:41 localhost dbus[16729]: [system] Rejected send message, 1 matched rules; type="method_call", sender=":1.8" (uid=0 pid=16936 comm="/usr/sbin/gdm ") interface="org.freedesktop.DBus.Properties" member="GetAll" error name="(unset)" requested_reply="0" destination=":
1.9" (uid=0 pid=16939 comm="/usr/libexec/gdm-simple-slave --display-id /org/gn")
Dec 10 11:29:41 localhost dbus-daemon[16729]: dbus[16729]: [system] Activating via systemd: service name='org.freedesktop.Accounts' unit='accounts-daemon.service'
Dec 10 11:29:41 localhost dbus[16729]: [system] Activating via systemd: service name='org.freedesktop.Accounts' unit='accounts-daemon.service'
Dec 10 11:29:41 localhost systemd[1]: Starting Accounts Service...
-- Subject: Unit accounts-daemon.service has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit accounts-daemon.service has begun starting up.
Dec 10 11:29:41 localhost accounts-daemon[16944]: started daemon version 0.6.34
Dec 10 11:29:41 localhost dbus-daemon[16729]: dbus[16729]: [system] Successfully activated service 'org.freedesktop.Accounts'
Dec 10 11:29:41 localhost dbus[16729]: [system] Successfully activated service 'org.freedesktop.Accounts'
Dec 10 11:29:41 localhost systemd[1]: Started Accounts Service.
-- Subject: Unit accounts-daemon.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit accounts-daemon.service has finished starting up.
--
-- The start-up result is done.
Dec 10 11:29:41 localhost accounts-daemon[16944]: ** (accounts-daemon:16944): CRITICAL **: error exporting user object: An object is already exported for the interface org.freedesktop.Accounts.User at /org/freedesktop/Accounts/User1011
Dec 10 11:29:42 localhost kernel: nvidia 0000:02:00.0: irq 58 for MSI/MSI-X
Dec 10 11:29:44 localhost gdm[16936]: Failed to give slave programs access to the display. Trying to proceed.
Dec 10 11:29:45 localhost gdm-launch-environment][16962]: pam_systemd(gdm-launch-environment:session): Unknown parameter 'kill-session-processes=1', ignoring
Dec 10 11:29:45 localhost systemd[1]: Starting user-105.slice.
-- Subject: Unit user-105.slice has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit user-105.slice has begun starting up.
Dec 10 11:29:45 localhost systemd[1]: Created slice user-105.slice.
-- Subject: Unit user-105.slice has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit user-105.slice has finished starting up.
--
-- The start-up result is done.
Dec 10 11:29:45 localhost systemd[1]: Starting User Manager for 105...
-- Subject: Unit user@105.service has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit user@105.service has begun starting up.
Dec 10 11:29:45 localhost systemd[1]: Starting Session c1 of user gdm.
-- Subject: Unit session-c1.scope has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit session-c1.scope has begun starting up.
Dec 10 11:29:45 localhost systemd-logind[16732]: New session c1 of user gdm.
-- Subject: A new session c1 has been created for user gdm
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: http://www.freedesktop.org/wiki/Software/systemd/multiseat
--
-- A new session with the ID c1 has been created for the user gdm.
--
-- The leading process of the session is 16962.
Dec 10 11:29:45 localhost systemd-logind[16732]: Linked /tmp/.X11-unix/X0 to /run/user/105/X11-display.
Dec 10 11:29:45 localhost systemd[1]: Started Session c1 of user gdm.
-- Subject: Unit session-c1.scope has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit session-c1.scope has finished starting up.
--
-- The start-up result is done.
Dec 10 11:29:45 localhost systemd[16965]: pam_unix(systemd-user:session): session opened for user gdm by (uid=0)
Dec 10 11:29:45 localhost systemd[16965]: Failed to open private bus connection: Failed to connect to socket /run/user/105/dbus/user_bus_socket: No such file or directory
Dec 10 11:29:45 localhost systemd[16965]: Mounted /sys/kernel/config.
-- Subject: Unit UNIT has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit UNIT has finished starting up.
--
-- The start-up result is done.
Dec 10 11:29:45 localhost systemd[16965]: Mounted /sys/fs/fuse/connections.
-- Subject: Unit UNIT has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit UNIT has finished starting up.
--
-- The start-up result is done.
Dec 10 11:29:45 localhost systemd[16965]: Stopped target Sound Card.
-- Subject: Unit UNIT has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: http://www.freedesktop.org/wiki/Software/systemd/catalog/9d1aaa27d60140bd96365438aad20286
--
-- Unit UNIT has finished shutting down.
Dec 10 11:29:45 localhost systemd[16965]: Starting Default.
-- Subject: Unit UNIT has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit UNIT has begun starting up.
Dec 10 11:29:45 localhost systemd[16965]: Reached target Default.
-- Subject: Unit UNIT has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit UNIT has finished starting up.
--
-- The start-up result is done.
Dec 10 11:29:45 localhost systemd[16965]: Startup finished in 54ms.
-- Subject: System start-up is now complete
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- All system services necessary queued for starting at boot have been
-- successfully started. Note that this does not mean that the machine is
-- now idle as services might still be busy with completing start-up.
--
-- Kernel start-up required KERNEL_USEC microseconds.
--
-- Initial RAM disk start-up required INITRD_USEC microseconds.
--
-- Userspace start-up required 54772 microseconds.
Dec 10 11:29:45 localhost systemd[1]: Started User Manager for 105.
-- Subject: Unit user@105.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit user@105.service has finished starting up.
--
-- The start-up result is done.
Dec 10 11:29:47 localhost /usr/bin/dbus-launch[16967]: gnome-session[16967]: WARNING: Could not connect to ConsoleKit: Unable to lookup session information for process '16967'
Dec 10 11:29:47 localhost gnome-session[16967]: WARNING: Could not connect to ConsoleKit: Unable to lookup session information for process '16967'
Dec 10 11:29:47 localhost /usr/bin/dbus-launch[16967]: gnome-session[16967]: WARNING: Could not connect to ConsoleKit: Unable to lookup session information for process '16967'
Dec 10 11:29:47 localhost gnome-session[16967]: WARNING: Could not connect to ConsoleKit: Unable to lookup session information for process '16967'
Dec 10 11:29:47 localhost /usr/bin/dbus-launch[16967]: gnome-session[16967]: WARNING: Could not parse desktop file orca-autostart.desktop or it references a not found TryExec binary
Dec 10 11:29:47 localhost gnome-session[16967]: WARNING: Could not parse desktop file orca-autostart.desktop or it references a not found TryExec binary
Dec 10 11:29:48 localhost dbus-daemon[16729]: dbus[16729]: [system] Activating via systemd: service name='org.freedesktop.UPower' unit='upower.service'
Dec 10 11:29:48 localhost dbus[16729]: [system] Activating via systemd: service name='org.freedesktop.UPower' unit='upower.service'
Dec 10 11:29:48 localhost systemd[1]: Starting Daemon for power management...
-- Subject: Unit upower.service has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit upower.service has begun starting up.
Dec 10 11:29:48 localhost dbus-daemon[16729]: dbus[16729]: [system] Successfully activated service 'org.freedesktop.UPower'
Dec 10 11:29:48 localhost dbus[16729]: [system] Successfully activated service 'org.freedesktop.UPower'
Dec 10 11:29:48 localhost systemd[1]: Started Daemon for power management.
-- Subject: Unit upower.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit upower.service has finished starting up.
--
-- The start-up result is done.
Dec 10 11:29:48 localhost upowerd[16995]: (upowerd:16995): UPower-WARNING **: failed to get directory: Error opening directory '/sys/class/leds': No such file or directory
Dec 10 11:29:49 localhost /usr/bin/dbus-launch[16967]: (gnome-settings-daemon:16987): power-plugin-WARNING **: Unable to inhibit lid switch: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: Operation not permitted
Dec 10 11:29:49 localhost /usr/bin/dbus-launch[16967]: (gnome-settings-daemon:16987): media-keys-plugin-WARNING **: Unable to inhibit keypresses: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: Operation not permitted
Dec 10 11:29:49 localhost dbus-daemon[16729]: dbus[16729]: [system] Activating via systemd: service name='org.freedesktop.ColorManager' unit='colord.service'
Dec 10 11:29:49 localhost dbus[16729]: [system] Activating via systemd: service name='org.freedesktop.ColorManager' unit='colord.service'
Dec 10 11:29:49 localhost systemd[1]: Starting Manage, Install and Generate Color Profiles...
-- Subject: Unit colord.service has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit colord.service has begun starting up.
Dec 10 11:29:50 localhost colord[17052]: Using config file /etc/colord.conf
Dec 10 11:29:50 localhost colord[17052]: Using mapping database file /var/lib/colord/mapping.db
Dec 10 11:29:50 localhost colord[17052]: Using device database file /var/lib/colord/storage.db
Dec 10 11:29:50 localhost colord[17052]: loaded plugin libcd_plugin_camera.so
Dec 10 11:29:50 localhost colord[17052]: loaded plugin libcd_plugin_scanner.so
Dec 10 11:29:50 localhost colord[17052]: Daemon ready for requests
Dec 10 11:29:50 localhost dbus-daemon[16729]: dbus[16729]: [system] Successfully activated service 'org.freedesktop.ColorManager'
Dec 10 11:29:50 localhost dbus[16729]: [system] Successfully activated service 'org.freedesktop.ColorManager'
Dec 10 11:29:50 localhost systemd[1]: Started Manage, Install and Generate Color Profiles.
-- Subject: Unit colord.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit colord.service has finished starting up.
--
-- The start-up result is done.
Dec 10 11:29:50 localhost colord[17052]: Profile added: icc-5b605be32b278d8e91dcdb94462ac27f
Dec 10 11:29:50 localhost colord[17052]: Profile added: icc-83c9227cee43e657a58674804fe00278
Dec 10 11:29:50 localhost colord[17052]: Profile added: icc-fdfdf1022b23440abcd5b7331cf02a55
Dec 10 11:29:50 localhost colord[17052]: Profile added: icc-a5f10846975eeb751fd90b1d6512e852
Dec 10 11:29:50 localhost colord[17052]: Profile added: icc-5e053c78d65e0366aefcb55db0d57f5a
Dec 10 11:29:50 localhost colord[17052]: Profile added: icc-029985d49a051c5fa2388d4edd69656b
Dec 10 11:29:50 localhost colord[17052]: (colord:17052): libcolord-WARNING **: lcms2(profile): Failed with error: Bad dictionary Name/Value [12]
Dec 10 11:29:50 localhost colord[17052]: (colord:17052): libcolord-WARNING **: lcms2(profile): Failed with error: Corrupted tag 'meta' [12]
Dec 10 11:29:50 localhost colord[17052]: Profile added: icc-1fd0ece7a843c5590592ad274c2597fa
Dec 10 11:29:50 localhost colord[17052]: (colord:17052): libcolord-WARNING **: lcms2(profile): Failed with error: Bad dictionary Name/Value [12]
Dec 10 11:29:50 localhost colord[17052]: (colord:17052): libcolord-WARNING **: lcms2(profile): Failed with error: Corrupted tag 'meta' [12]
Dec 10 11:29:50 localhost colord[17052]: Profile added: icc-4b91a64d8e7936279e0c664ccf289446
Dec 10 11:29:50 localhost colord[17052]: Profile added: icc-2db96e3be58bf616617d29438773d1e9
Dec 10 11:29:50 localhost colord[17052]: Profile added: icc-0948af7e067817c24555e1b061718b44
Dec 10 11:29:50 localhost colord[17052]: (colord:17052): libcolord-WARNING **: lcms2(profile): Failed with error: Bad dictionary Name/Value [12]
Dec 10 11:29:50 localhost colord[17052]: (colord:17052): libcolord-WARNING **: lcms2(profile): Failed with error: Corrupted tag 'meta' [12]
Dec 10 11:29:50 localhost colord[17052]: Profile added: icc-dba1a7ff94a3ab9309b7b9833d5d68a9
Dec 10 11:29:50 localhost colord[17052]: Profile added: icc-87b7d9b72bc12ef5d18e9e00e4de00a4
Dec 10 11:29:50 localhost colord[17052]: Profile added: icc-1addcb1ff317681fb7c2e763dcf15caf
Dec 10 11:29:50 localhost colord[17052]: Profile added: icc-1f45c3fed247b0713c7afa57c09e8f84
Dec 10 11:29:50 localhost colord[17052]: Profile added: icc-5fe73ea8e1711173ecf046a414b358b0
Dec 10 11:29:50 localhost colord[17052]: Profile added: icc-5f7e866cba7bf4285b1bd881eb480a13
Dec 10 11:29:50 localhost colord[17052]: Profile added: icc-74f1646a87c428762276e5611bcbc272
Dec 10 11:29:50 localhost colord[17052]: Profile added: icc-401e3f1b41eddb1dd67f8036a6d23f9b
Dec 10 11:29:50 localhost colord[17052]: Profile added: icc-955ffdfc2d370c411b62cbfc653ad7a5
Dec 10 11:29:50 localhost colord[17052]: Profile added: icc-8f16b44396463023b03ab98837be1b06
Dec 10 11:29:50 localhost colord[17052]: Profile added: icc-7c840f5d113af75c9b2544f95cf94728
Dec 10 11:29:50 localhost colord[17052]: Profile added: icc-0a91d97691639c980c16364f630f9c1f
Dec 10 11:29:50 localhost colord[17052]: Profile added: icc-a57b148310aa4ae07da22b13571fe558
Dec 10 11:29:50 localhost colord[17052]: Profile added: icc-52385f9e22129f38e27d4a5f0d45983a
Dec 10 11:29:53 localhost dbus-daemon[16729]: dbus[16729]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service'
Dec 10 11:29:53 localhost dbus-daemon[16729]: dbus[16729]: [system] Activation via systemd failed for unit 'dbus-org.bluez.service': Unit dbus-org.bluez.service failed to load: No such file or directory.
Dec 10 11:29:53 localhost dbus[16729]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service'
Dec 10 11:29:53 localhost dbus[16729]: [system] Activation via systemd failed for unit 'dbus-org.bluez.service': Unit dbus-org.bluez.service failed to load: No such file or directory.
Dec 10 11:29:54 localhost pulseaudio[17055]: [pulseaudio] bluetooth-util.c: org.bluez.Manager.GetProperties() failed: org.freedesktop.systemd1.LoadFailed: Unit dbus-org.bluez.service failed to load: No such file or directory.
Dec 10 11:29:54 localhost pulseaudio[17079]: [pulseaudio] pid.c: Daemon already running.
Dec 10 11:29:54 localhost dbus-daemon[16729]: dbus[16729]: [system] Activating via systemd: service name='org.freedesktop.locale1' unit='dbus-org.freedesktop.locale1.service'
Dec 10 11:29:54 localhost dbus[16729]: [system] Activating via systemd: service name='org.freedesktop.locale1' unit='dbus-org.freedesktop.locale1.service'
Dec 10 11:29:54 localhost systemd[1]: Starting Locale Service...
-- Subject: Unit systemd-localed.service has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit systemd-localed.service has begun starting up.
Dec 10 11:29:54 localhost dbus-daemon[16729]: dbus[16729]: [system] Successfully activated service 'org.freedesktop.locale1'
Dec 10 11:29:54 localhost dbus[16729]: [system] Successfully activated service 'org.freedesktop.locale1'
Dec 10 11:29:54 localhost systemd[1]: Started Locale Service.
-- Subject: Unit systemd-localed.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit systemd-localed.service has finished starting up.
--
-- The start-up result is done.
Dec 10 11:29:54 localhost /usr/bin/dbus-launch[16967]: (gnome-settings-daemon:16987): color-plugin-WARNING **: failed to create device: failed to obtain org.freedesktop.color-manager.create-device auth
Dec 10 11:29:54 localhost /usr/bin/dbus-launch[16967]: (gnome-settings-daemon:16987): color-plugin-WARNING **: failed to create device: failed to obtain org.freedesktop.color-manager.create-device auth
Dec 10 11:29:55 localhost /usr/bin/dbus-launch[16967]: JS ERROR: !!! Exception was: Error: Requiring Shell, version none: Typelib file for namespace 'NetworkManager', version '1.0' not found
Dec 10 11:29:55 localhost /usr/bin/dbus-launch[16967]: JS ERROR: !!! message = '"Requiring Shell, version none: Typelib file for namespace 'NetworkManager', version '1.0' not found"'
Dec 10 11:29:55 localhost /usr/bin/dbus-launch[16967]: JS ERROR: !!! fileName = '"/usr/share/gnome-shell/js/ui/environment.js"'
Dec 10 11:29:55 localhost /usr/bin/dbus-launch[16967]: JS ERROR: !!! lineNumber = '13'
Dec 10 11:29:55 localhost /usr/bin/dbus-launch[16967]: JS ERROR: !!! stack = '"@/usr/share/gnome-shell/js/ui/environment.js:13
Dec 10 11:29:55 localhost /usr/bin/dbus-launch[16967]: "'
Dec 10 11:29:55 localhost /usr/bin/dbus-launch[16967]: JS ERROR: !!! Exception was: Error: Requiring Shell, version none: Typelib file for namespace 'NetworkManager', version '1.0' not found
Dec 10 11:29:55 localhost /usr/bin/dbus-launch[16967]: JS ERROR: !!! message = '"Requiring Shell, version none: Typelib file for namespace 'NetworkManager', version '1.0' not found"'
Dec 10 11:29:55 localhost /usr/bin/dbus-launch[16967]: JS ERROR: !!! fileName = '"/usr/share/gnome-shell/js/ui/environment.js"'
Dec 10 11:29:55 localhost /usr/bin/dbus-launch[16967]: JS ERROR: !!! lineNumber = '13'
Dec 10 11:29:55 localhost /usr/bin/dbus-launch[16967]: JS ERROR: !!! stack = '"@/usr/share/gnome-shell/js/ui/environment.js:13
Dec 10 11:29:55 localhost /usr/bin/dbus-launch[16967]: "'
Dec 10 11:29:55 localhost /usr/bin/dbus-launch[16967]: Window manager warning: Log level 32: Execution of main.js threw exception: Error: Requiring Shell, version none: Typelib file for namespace 'NetworkManager', version '1.0' not found
Dec 10 11:29:55 localhost /usr/bin/dbus-launch[16967]: (gnome-settings-daemon:16987): GLib-GIO-CRITICAL **: g_dbus_proxy_call_internal: assertion `G_IS_DBUS_PROXY (proxy)' failed
|
this is /usr/lib/systemd/system/gdm.service Code: | [Unit]
Description=GNOME Display Manager
Conflicts=getty@tty7.service plymouth-quit.service
After=systemd-user-sessions.service getty@tty7.service plymouth-quit.service
[Service]
ExecStart=/usr/sbin/gdm
Restart=always
IgnoreSIGPIPE=no
BusName=org.gnome.DisplayManager
StandardOutput=syslog
StandardError=inherit
[Install]
Alias=display-manager.service
|
Can anybody help me getting gnome running?
Thank You
Jody
Last edited by jody on Mon Dec 16, 2013 8:23 am; edited 1 time in total |
|
Back to top |
|
|
jody l33t
Joined: 16 Oct 2007 Posts: 668 Location: Switzerland
|
Posted: Thu Dec 12, 2013 9:08 am Post subject: |
|
|
additional info
- it is not an X problem or an nvidia problem: i can start twm and it works, and i can start glxgears and it works
Any ideas what could be wrong here?
thanks
Jody |
|
Back to top |
|
|
jonnevers Veteran
Joined: 02 Jan 2003 Posts: 1594 Location: Gentoo64 land
|
Posted: Thu Dec 12, 2013 2:15 pm Post subject: |
|
|
ConsoleKit should be disabled via the systemd USE flag.
are you using the 'default/linux/amd64/13.0/desktop/gnome/systemd' profile?
The systemd ( nor gnome 3.8 ) upgrade guide doesn't say to explicitly remove the standalone ConsoleKit, just to disable it via the systemd use flag. |
|
Back to top |
|
|
jody l33t
Joined: 16 Oct 2007 Posts: 668 Location: Switzerland
|
Posted: Thu Dec 12, 2013 3:10 pm Post subject: |
|
|
I indeed had the consolekit flag active, and apparently my profile is 'default/linux/amd64/13.0/desktop/gnome' /which is strange because i remember setting it to systemd).
Anyway, I now removed the flag and set my profile to 'default/linux/amd64/13.0/desktop/gnome/systemd'.
I do a complete reemerge and see what happens.
Thanks
Jody |
|
Back to top |
|
|
jody l33t
Joined: 16 Oct 2007 Posts: 668 Location: Switzerland
|
Posted: Thu Dec 12, 2013 3:25 pm Post subject: |
|
|
It was enough to reemerge gdm-session.
After this gniome started correctly.
Thanks again!
Jody |
|
Back to top |
|
|
198728 l33t
Joined: 08 Apr 2009 Posts: 693
|
Posted: Thu Dec 12, 2013 9:46 pm Post subject: |
|
|
jonnevers wrote: | ConsoleKit should be disabled via the systemd USE flag.
are you using the 'default/linux/amd64/13.0/desktop/gnome/systemd' profile?
The systemd ( nor gnome 3.8 ) upgrade guide doesn't say to explicitly remove the standalone ConsoleKit, just to disable it via the systemd use flag. |
Globally disabled in the make.conf or simply unmerge it?
Which is the most complete guide to systemd migration? |
|
Back to top |
|
|
jonnevers Veteran
Joined: 02 Jan 2003 Posts: 1594 Location: Gentoo64 land
|
|
Back to top |
|
|
|