Attachment 101925 Details for Bug 80629 – runlevel 3 kdm.log

runlevel 3 kdm.log

rl3_kdm.log (text/plain), 1.47 KB, created by pdi on 2014-06-28 14:14:35 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: pdi

Created: 2014-06-28 14:14:35 UTC

Size: 1.47 KB

patch

obsolete

>Initializing built-in extension Generic Event Extension
>Initializing built-in extension SHAPE
>Initializing built-in extension MIT-SHM
>Initializing built-in extension XInputExtension
>Initializing built-in extension XTEST
>Initializing built-in extension BIG-REQUESTS
>Initializing built-in extension SYNC
>Initializing built-in extension XKEYBOARD
>Initializing built-in extension XC-MISC
>Initializing built-in extension XINERAMA
>Initializing built-in extension XFIXES
>Initializing built-in extension RENDER
>Initializing built-in extension RANDR
>Initializing built-in extension COMPOSITE
>Initializing built-in extension DAMAGE
>Initializing built-in extension MIT-SCREEN-SAVER
>Initializing built-in extension DOUBLE-BUFFER
>Initializing built-in extension RECORD
>Initializing built-in extension DPMS
>Initializing built-in extension X-Resource
>Initializing built-in extension XVideo
>Initializing built-in extension XVideo-MotionCompensation
>Initializing built-in extension XFree86-VidModeExtension
>Initializing built-in extension XFree86-DGA
>Initializing built-in extension XFree86-DRI
>Initializing built-in extension DRI2
>Loading extension GLX
>klauncher(1010) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
>kdeinit4: Communication error with launcher. Exiting!
>kdmgreet(1004)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed:  "Not connected to D-Bus server"
>
>kdmgreet(1004)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
>

Actions: View

Attachments on bug 80629: 101917 | 101918 | 101919 | 101920 | 101921 | 101922 | 101923 | 101924 | 101925 | 102121 | 102123 | 102267

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.