Arch Linux

mreff555

Member

Registered: 2015-02-13

Posts: 24

KDM crashing on boot

I just recently installed arch, so not a whole lot of changes have been made since I got it up and running
After a recent update I am now having issues when I reboot. KDM hangs (black screen). I can switch tty's and restart kdm and everything works fine.
I'm struggling to get wgetpaste working, and I'll spare you my entire KDM log, but I have more than one of these in there.
could it be that KDM is starting before dbus? I've never used systemd and have no idea how to diagnose or repair.

thanks,

kdmgreet(268)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned 
QThread::wait: Thread tried to wait on itself
QThread: Destroyed while thread is still running
KCrash: Application 'kdmgreet' crashing...
(II) Server terminated successfully (0). Closing log file.
klauncher(508) kdemain: No DBUS session-bus found. Check if you have started the DBUS server. 
kdeinit4: Communication error with launcher. Exiting!
kdmgreet(502)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed:  "Not connected to D-Bus server" 

kdmgreet(502)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned 
(II) Server terminated successfully (0). Closing log file.
klauncher(297) kdemain: No DBUS session-bus found. Check if you have started the DBUS server. 
kdeinit4: Communication error with launcher. Exiting!
kdmgreet(267)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed:  "Not connected to D-Bus server" 

kdmgreet(267)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned 
KCrash: Application 'kdmgreet' crashing...
KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi directly
QThread::wait: Thread tried to wait on itself
QThread: Destroyed while thread is still running
*** Error in `/usr/lib/kde4/libexec/kdm_greet': corrupted double-linked list: 0x00000000009cb630 ***
======= Backtrace: =========
/usr/lib/libc.so.6(+0x7198e)[0x7f721b46998e]
/usr/lib/libc.so.6(+0x76dee)[0x7f721b46edee]
/usr/lib/libc.so.6(+0x77dc3)[0x7f721b46fdc3]
/usr/lib/libQtCore.so.4(+0xae52c)[0x7f721cfc152c]
/usr/lib/libQtCore.so.4(+0xbceb9)[0x7f721cfcfeb9]
/usr/lib/libc.so.6(+0x35db2)[0x7f721b42ddb2]
/usr/lib/libc.so.6(+0x35e05)[0x7f721b42de05]
/usr/lib/kde4/libexec/kdm_greet[0x430d0e]
/usr/lib/libc.so.6(+0x33540)[0x7f721b42b540]
/usr/lib/libc.so.6(__select+0x33)[0x7f721b4d91b3]
/usr/lib/libQtCore.so.4(+0x161e31)[0x7f721d074e31]
/usr/lib/libQtCore.so.4(+0x7c05f)[0x7f721cf8f05f]
/usr/lib/libpthread.so.0(+0x7374)[0x7f721ccfd374]
/usr/lib/libc.so.6(clone+0x6d)[0x7f721b4e027d]

cfr

Member

From: Cymru

Registered: 2011-11-27

Posts: 7,140

Re: KDM crashing on boot

How are you starting KDM exactly?

---

CLI Paste | How To Ask Questions

Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Wireless 8265/8275 | US keyboard w/ Euro | 512G NVMe INTEL SSDPEKKF512G7L

mreff555

Member

Registered: 2015-02-13

Posts: 24

Re: KDM crashing on boot

How are you starting KDM exactly?

I have the service enabled through systemd

Hopefully this is the answer you are looking for.

cfr

Member

From: Cymru

Registered: 2011-11-27

Posts: 7,140

Re: KDM crashing on boot

Did you follow https://wiki.archlinux.org/index.php/KDM? If you boot to the command line, can you start the systemd service without it crashing? Does the journal say anything useful? (journalctl) Have you edited the default configuration file for KDM?

---

CLI Paste | How To Ask Questions

Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Wireless 8265/8275 | US keyboard w/ Euro | 512G NVMe INTEL SSDPEKKF512G7L

mreff555

Member

Registered: 2015-02-13

Posts: 24

Re: KDM crashing on boot

cfr,

Yes I followed it verbatim. It worked flawlessly for a few days and then stopped working.
As I said before, if I switch tty's and restart kdm it loads without indecent. I have not edited the default config, but I do not think that is the problem since it worked before.

below is my journalctl output. I'm not familiar with this log, whats interesting is that I've rebooted a dozen times since that time stamp. That was probably the last successful boot to to the DM without me having to intervene.

-- Logs begin at Wed 2015-02-11 20:05:31 EST, end at Thu 2015-02-19 20:29:15 EST. --
Feb 11 20:05:31 mojo systemd-journal[136]: Runtime journal is using 8.0M (max allowed 193.3M, trying to leave 290.0M free of 1.8G available <E2><86><92> current limit 193.3
Feb 11 20:05:31 mojo systemd-journal[136]: Permanent journal is using 8.0M (max allowed 4.0G, trying to leave 4.0G free of 142.5G available <E2><86><92> current limit 4.0G)
Feb 11 20:05:31 mojo systemd-journal[136]: Time spent on flushing to /var is 1.327ms for 2 entries.
Feb 11 20:05:31 mojo kernel: Initializing cgroup subsys cpuset
Feb 11 20:05:31 mojo kernel: Initializing cgroup subsys cpu
Feb 11 20:05:31 mojo kernel: Initializing cgroup subsys cpuacct
Feb 11 20:05:31 mojo kernel: Linux version 3.18.6-1-ARCH (builduser@tobias) (gcc version 4.9.2 20141224 (prerelease) (GCC) ) #1 SMP PREEMPT Sat Feb 7 08:44:05 CET 2015
Feb 11 20:05:31 mojo kernel: Command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=adee7d41-afda-4973-a77f-fce2c42cd2ef rw quiet
Feb 11 20:05:31 mojo kernel: e820: BIOS-provided physical RAM map:
Feb 11 20:05:31 mojo kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009e7ff] usable
Feb 11 20:05:31 mojo kernel: BIOS-e820: [mem 0x000000000009e800-0x000000000009ffff] reserved
Feb 11 20:05:31 mojo kernel: BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Feb 11 20:05:31 mojo kernel: BIOS-e820: [mem 0x0000000000100000-0x000000001fffffff] usable
Feb 11 20:05:31 mojo kernel: BIOS-e820: [mem 0x0000000020000000-0x00000000201fffff] reserved
Feb 11 20:05:31 mojo kernel: BIOS-e820: [mem 0x0000000020200000-0x000000003fffffff] usable
Feb 11 20:05:31 mojo kernel: BIOS-e820: [mem 0x0000000040000000-0x00000000401fffff] reserved
Feb 11 20:05:31 mojo kernel: BIOS-e820: [mem 0x0000000040200000-0x00000000aad21fff] usable
Feb 11 20:05:31 mojo kernel: BIOS-e820: [mem 0x00000000aad22000-0x00000000aad8dfff] reserved
Feb 11 20:05:31 mojo kernel: BIOS-e820: [mem 0x00000000aad8e000-0x00000000aad94fff] usable
Feb 11 20:05:31 mojo kernel: BIOS-e820: [mem 0x00000000aad95000-0x00000000aad95fff] reserved
Feb 11 20:05:31 mojo kernel: BIOS-e820: [mem 0x00000000aad96000-0x00000000aad96fff] usable

Alad

Wiki Admin/IRC Op

From: Bagelstan

Registered: 2014-05-04

Posts: 2,413

Website

Re: KDM crashing on boot

Is that all your log says? oO

---

Mods are just community members who have the occasionally necessary option to move threads around and edit posts. -- Trilby

mreff555

Member

Registered: 2015-02-13

Posts: 24

Re: KDM crashing on boot

yes, It appears to have stopped recording around the time I began having this issue.