Your message dated Sun, 15 Feb 2015 22:54:13 +0100
with message-id <[email protected]>
and subject line Re: Bug#778362: Periodic (90s) restart of KDM by systemd on
jessie
has caused the Debian Bug report #778362,
regarding Periodic (90s) restart of KDM by systemd on jessie
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
778362: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778362
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: systemd
Version: 215-10
Platform -- Dell M3800 (XPS-15 alike) laptop, dm-crypt rootfs, jessie
with main/contrib/non-free, nVidia binary drivers (dkms). *Mostly* a
vanilla Jessie install (dm-crypt'd / is the obvious out of the
ordinary config item). Note - NOT an upgraded Debian installation -
wheezy (ISO) then dist-upgrade. One hiccup during dist-upgrade
relating to cryptsetup not being put into initrd - subsequently
resolved. Jessie linux-image: Linux shpongle 3.18.0-trunk-amd64 #1
SMP Debian 3.18.3-1~exp1 (2015-01-18) x86_64 GNU/Linux
Problem -- on boot, KDM starts fine. Whether I log in or not, KDM
restarts precisely every 90 seconds. (The problem is exacerbated by
my profound lack of systemd-fu.)
journalctl produces notice that kdm.service failed, and restarts it,
but I can't find where to determine why it failed.
Unedited output of "journalctl -f" follows here, including
subsequent systemctl (below) period:
shpongle:~# journalctl -f
-- Logs begin at Sat 2015-02-14 12:02:45 AEDT. --
Feb 14 12:03:31 shpongle console-kit-daemon[1318]: (process:1596):
GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0'
failed
Feb 14 12:03:31 shpongle console-kit-daemon[1318]: (process:1597):
GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0'
failed
Feb 14 12:03:31 shpongle console-kit-daemon[1318]: (process:1598):
GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0'
failed
Feb 14 12:03:55 shpongle sshd[1602]: Accepted publickey for root from
192.168.1.10 port 58966 ssh2: RSA
f4:17:b4:a7:20:eb:ec:4b:e4:e8:ef:63:88:f6:a5:89
Feb 14 12:03:55 shpongle sshd[1602]: pam_unix(sshd:session): session
opened for user root by (uid=0)
Feb 14 12:03:55 shpongle systemd-logind[796]: New session 3 of user root.
Feb 14 12:03:55 shpongle console-kit-daemon[1318]: (process:1606):
GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0'
failed
Feb 14 12:03:55 shpongle console-kit-daemon[1318]: (process:1607):
GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0'
failed
Feb 14 12:03:55 shpongle console-kit-daemon[1318]: (process:1608):
GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0'
failed
Feb 14 12:03:55 shpongle console-kit-daemon[1318]: missing action
Feb 14 12:04:17 shpongle systemd[1]: kdm.service start operation timed
out. Terminating.
Feb 14 12:04:17 shpongle systemd[1]: Failed to start KDE Display Manager.
Feb 14 12:04:17 shpongle systemd[1]: Dependency failed for X11 Display Manager.
Feb 14 12:04:17 shpongle systemd[1]: Unit kdm.service entered failed state.
Feb 14 12:04:18 shpongle console-kit-daemon[1318]: (process:1636):
GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0'
failed
Feb 14 12:04:18 shpongle console-kit-daemon[1318]: (process:1637):
GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0'
failed
Feb 14 12:04:18 shpongle console-kit-daemon[1318]: (process:1638):
GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0'
failed
Feb 14 12:04:41 shpongle sshd[1650]: Accepted publickey for root from
192.168.1.10 port 58980 ssh2: RSA
f4:17:b4:a7:20:eb:ec:4b:e4:e8:ef:63:88:f6:a5:89
Feb 14 12:04:41 shpongle sshd[1650]: pam_unix(sshd:session): session
opened for user root by (uid=0)
Feb 14 12:04:41 shpongle systemd-logind[796]: New session 4 of user root.
Feb 14 12:04:41 shpongle console-kit-daemon[1318]: (process:1654):
GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0'
failed
Feb 14 12:04:41 shpongle console-kit-daemon[1318]: (process:1655):
GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0'
failed
Feb 14 12:04:41 shpongle console-kit-daemon[1318]: (process:1656):
GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0'
failed
Feb 14 12:04:41 shpongle console-kit-daemon[1318]: missing action
Feb 14 12:05:01 shpongle CRON[1672]: pam_unix(cron:session): session
opened for user root by (uid=0)
Feb 14 12:05:01 shpongle CRON[1673]: (root) CMD (command -v debian-sa1
> /dev/null && debian-sa1 1 1)
Feb 14 12:05:01 shpongle CRON[1672]: pam_unix(cron:session): session
closed for user root
Feb 14 12:05:41 shpongle console-kit-daemon[1318]: (process:1677):
GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0'
failed
Feb 14 12:05:41 shpongle console-kit-daemon[1318]: (process:1678):
GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0'
failed
Feb 14 12:05:41 shpongle console-kit-daemon[1318]: (process:1679):
GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0'
failed
Feb 14 12:05:48 shpongle systemd[1]: kdm.service start operation timed
out. Terminating.
Feb 14 12:05:48 shpongle console-kit-daemon[1318]: (process:1685):
GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0'
failed
Feb 14 12:05:48 shpongle console-kit-daemon[1318]: (process:1686):
GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0'
failed
Feb 14 12:05:48 shpongle console-kit-daemon[1318]: (process:1687):
GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0'
failed
Feb 14 12:05:48 shpongle systemd[1]: Failed to start KDE Display Manager.
Feb 14 12:05:48 shpongle systemd[1]: Dependency failed for X11 Display Manager.
Feb 14 12:05:48 shpongle systemd[1]: Unit kdm.service entered failed state.
Feb 14 12:05:48 shpongle console-kit-daemon[1318]: (process:1698):
GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0'
failed
Feb 14 12:05:48 shpongle console-kit-daemon[1318]: (process:1699):
GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0'
failed
Feb 14 12:05:48 shpongle console-kit-daemon[1318]: (process:1700):
GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0'
failed
Feb 14 12:07:18 shpongle systemd[1]: kdm.service start operation timed
out. Terminating.
Feb 14 12:07:20 shpongle console-kit-daemon[1318]: (process:1717):
GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0'
failed
Feb 14 12:07:20 shpongle systemd[1]: Failed to start KDE Display Manager.
Feb 14 12:07:20 shpongle systemd[1]: Dependency failed for X11 Display Manager.
Feb 14 12:07:20 shpongle systemd[1]: Unit kdm.service entered failed state.
Feb 14 12:07:20 shpongle console-kit-daemon[1318]: (process:1718):
GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0'
failed
Feb 14 12:07:20 shpongle console-kit-daemon[1318]: (process:1722):
GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0'
failed
Feb 14 12:07:20 shpongle console-kit-daemon[1318]: (process:1732):
GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0'
failed
Feb 14 12:07:20 shpongle console-kit-daemon[1318]: (process:1733):
GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0'
failed
Feb 14 12:07:20 shpongle console-kit-daemon[1318]: (process:1734):
GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0'
failed
I've taken systemctl status dumps (below) before and after that one
particular KDM restart.
shpongle:~# systemctl status kdm.service
● kdm.service - KDE Display Manager
Loaded: loaded (/lib/systemd/system/kdm.service; enabled)
Drop-In: /run/systemd/generator/kdm.service.d
└─50-kdm-$x-display-manager.conf
Active: activating (start) since Sat 2015-02-14 12:04:17 AEDT; 41s ago
Docs: man:kdm(1)
Process: 1628 ExecStartPre=/bin/sh -c [ "$(cat
/etc/X11/default-display-manager 2>/dev/null)" = "/usr/bin/kdm" ]
(code=exited, status=0/SUCCESS)
Control: 1631 (kdm)
CGroup: /system.slice/kdm.service
├─1631 /usr/bin/kdm
├─1633 /usr/bin/X :0 vt7 -br -nolisten tcp -auth
/var/run/xauth/A:0-5nfVMb
├─1641 -:0
└─1642 /usr/lib/kde4/libexec/kdm_greet
shpongle:~# systemctl status kdm.service
● kdm.service - KDE Display Manager
Loaded: loaded (/lib/systemd/system/kdm.service; enabled)
Drop-In: /run/systemd/generator/kdm.service.d
└─50-kdm-$x-display-manager.conf
Active: activating (start) since Sat 2015-02-14 12:05:48 AEDT; 3s ago
Docs: man:kdm(1)
Process: 1690 ExecStartPre=/bin/sh -c [ "$(cat
/etc/X11/default-display-manager 2>/dev/null)" = "/usr/bin/kdm" ]
(code=exited, status=0/SUCCESS)
Control: 1693 (kdm)
CGroup: /system.slice/kdm.service
├─1693 /usr/bin/kdm
├─1695 /usr/bin/X :0 vt7 -br -nolisten tcp -auth
/var/run/xauth/A:0-1o2gGb
├─1703 -:0
└─1704 /usr/lib/kde4/libexec/kdm_greet
Of course, very happy to provide dumps, info, config files, logs, etc.
--- End Message ---
--- Begin Message ---
Am 14.02.2015 um 08:46 schrieb Jedd Rashbrooke:
>> You should consider removing the console-kit-daemon package.
>> It's not really useful anymore nowadays.
>
> I have now removed the consolekit package - thanks for the suggestion.
>
> I noted that it resulted in the removal of the mdadm package (along
> with a bunch of init.d/*mdadm scripts) even though that wasn't listed
> as a dependency. I'm using apt-get with -u, so actions involving
> other packages tend to stand out. I'm not using any mdadm volumes, so
> no biggy, but I did note before when trawling around systemadm GUI
> that mdadm.service and mdadm-raid.service were highlighted in red on
> the 'graphical.target', but so were acpi-support-service,
> sysstat.service, and nvidia-kernel.service, and those three still are.
>
>
>> That's a bug in the kdm.service unit resp. kdm. It never signals
>> systemd, that it started successfully. Most likely, this is due to the
>> use of the wrong Type= in kdm.service.
>>
>> Curious though, the kdm package in Debian doesn't ship
>> /lib/systemd/system/kdm.service. Where is this file coming from? Have
>> you created/installed that on your own?
>
> Ah, yes, I think I got that suggestion from bug #755359, and failed
> to mention it in the original report. Apologies for that oversight.
>
>
> After removing consolekit, I removed /lib/systemd/system/kdm.service
> file AND the symlink that had been recommended
> (/etc/systemd/system/display-manager.service ->
> /lib/systemd/system/display-manager.service )
>
>
> As an aside, the contents of the kdm.service file I'd used follows:
>
>
> [Unit]
> Description=KDE Display Manager
> Documentation=man:kdm(1)
> After=systemd-user-sessions.service
>
> [Service]
> ExecStartPre=/bin/sh -c '[ "$(cat /etc/X11/default-display-manager
> 2>/dev/null)" = "/usr/bin/kdm" ]'
> # ExecStart=/usr/bin/kdm -debug 0x08F vt1
> Type=forking
> ExecStart=/usr/bin/kdm
> Restart=always
> BusName=org.freedesktop.DisplayManager
>
>
>
> I then restarted the laptop, and KDM starts normally, and then stays
> up properly. So, this problem is fixed, but I'm still a smidge
> bewildered, as I put that kdm.service file in place, and the symlink,
> after following some other suggestions to fix the problem that was
> occurring *before* I made those changes. Oh well.
Ok, closing the bug, since it's not a bug in the systemd package.
As a small hint: If you add unit/service file locally, add them to
/etc/systemd/system. The /lib/systemd/system directory is reserved for
the package manager.
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
--- End Message ---
