Re: Cannot shutown from plasma or sddm
Thank you for your hints Christian, as I don't have any critical service on my laptop (it's basically my daily desktop computer), i've tried starting it with systemd following the instructions on https://wiki.debian.org/systemd (section "configured for testing"), editing the entry on grub to add init=/bin/systemd Doing this the computer started correctly and I had been able to shutdown and restarting it. Also fixed a permissions problem with muon-updater (which wasn't critical, because normally I use apt-get). After testing the computer for a while I've decided to switch to systemd, following the instructions on the wiki page mentioned before, and now everything is working as expected. Seems that what you told about sddm and systemd-logind was right and it's not working properly on sysvinit. Regards -- Marc Bres 2015-11-03 14:44 GMT+01:00 Christian Hilberg : > Hi Marc, > > Am Dienstag 03 November 2015, 12:05:04 schrieb Marc Bres Gil: > > Hello Christian, > > > > I'm using sysvinit, I installed the system when jessie was the "testing" > > version, and now i'm on stretch. > > I thought it will have changed to systemd when the upgrade was done, but > > checking it now i've found it is sysvinit the system in use. > > For fresh installs, systemd will be the default. When upgrading, I don't > think the installer will automatically change the previously-used init. > At least, the installer can be prevented from attempting this. > > I've also updated from a sysvinit Jessie to Stretch, keeping sysvinit as > init-System. I've casually searched the web for hints, but so far, no luck. > Some posts point into the PAM direction, i.e. systemd-logind not doing the > entire PAM dance. But so far, that's guessing only. > > > How can I check if systemd-logind is in use? I see that the systemd > package > > is installed. > > AFAIK, sddm relies in systemd-logind, i.e., when sddm is being used, so > is systemd-logind. At least, that is the default. > > Regards, > > Christian > > > Thanks > > Marc Bres > > [...] > > -- > kernel concepts GmbH Tel: +49-271-771091-11 > Sieghuetter Hauptweg 48 > D-57072 Siegen > http://www.kernelconcepts.de/ > -- Marc Bres Gil m...@bres.cat marc.b...@gmail.com
Re: Cannot shutown from plasma or sddm
Hi Marc, Am Dienstag 03 November 2015, 12:05:04 schrieb Marc Bres Gil: > Hello Christian, > > I'm using sysvinit, I installed the system when jessie was the "testing" > version, and now i'm on stretch. > I thought it will have changed to systemd when the upgrade was done, but > checking it now i've found it is sysvinit the system in use. For fresh installs, systemd will be the default. When upgrading, I don't think the installer will automatically change the previously-used init. At least, the installer can be prevented from attempting this. I've also updated from a sysvinit Jessie to Stretch, keeping sysvinit as init-System. I've casually searched the web for hints, but so far, no luck. Some posts point into the PAM direction, i.e. systemd-logind not doing the entire PAM dance. But so far, that's guessing only. > How can I check if systemd-logind is in use? I see that the systemd package > is installed. AFAIK, sddm relies in systemd-logind, i.e., when sddm is being used, so is systemd-logind. At least, that is the default. Regards, Christian > Thanks > Marc Bres > [...] -- kernel concepts GmbH Tel: +49-271-771091-11 Sieghuetter Hauptweg 48 D-57072 Siegen http://www.kernelconcepts.de/ signature.asc Description: This is a digitally signed message part.
Re: Cannot shutown from plasma or sddm
Hello Christian, I'm using sysvinit, I installed the system when jessie was the "testing" version, and now i'm on stretch. I thought it will have changed to systemd when the upgrade was done, but checking it now i've found it is sysvinit the system in use. How can I check if systemd-logind is in use? I see that the systemd package is installed. Thanks Marc Bres 2015-11-03 10:33 GMT+01:00 Christian Hilberg : > Hi Marc, > > Am Dienstag 03 November 2015, 09:13:12 schrieb Marc Bres Gil: > > Hello > > > > since some update made by half september, I cannot shutdown my computer > > from the kmenu on plasma. When I choose the shutdown option, only logs > off > > and shows me the sddm. > > When I try to shutdown from sddm it starts the countdown, but when > reaches > > zero, continues counting with negative numbers. > > The /var/log/syslog shows the following: > > > > Nov 3 09:02:01 fangorn dbus[2715]: [system] Activating service > > name='org.freedesktop.systemd1' (using servicehelper) > > Nov 3 09:02:01 fangorn kernel: [ 3618.266611] kactivitymanage[4103]: > > segfault at 7f8919e4acd0 ip 7f8919df4291 sp 7ffccd097278 error 4 > in > > libQt5Sql.so.5.5.1[7f8919de+3f000] > > Nov 3 09:02:01 fangorn dbus[2715]: [system] Successfully activated > service > > 'org.freedesktop.systemd1' > > Nov 3 09:02:01 fangorn acpid: client 2916[0:0] has disconnected > > Nov 3 09:02:01 fangorn acpid: client connected from 7791[0:0] > > Nov 3 09:02:01 fangorn acpid: 1 client rule loaded > > Nov 3 09:02:21 fangorn dbus[2715]: [system] Activating service > > name='org.freedesktop.systemd1' (using servicehelper) > > Nov 3 09:02:21 fangorn dbus[2715]: [system] Successfully activated > service > > 'org.freedesktop.systemd1' > > > > Previously to the last update, the segfault was given at > > libQt5Sql.so.5.4.2, i thought that with next update of this library it > will > > be solved, but it is still giving the error. > > > > Anybody else is having this problem? > > I'm experiencing this since end of August, see [0]. Back then, only > SDDM would not reboot or shutdown, while both was possible from within > Plasma. > > With the latest updates in stretch, though, shutting down the system > from within Plasma also does not work for me. Plasma throws me back to > SDDM, but no shutdown/reboot. > > May I ask, which init system do you use? For me, it is sysvinit (but > with systemd-logind installed), maybe this is creating an issue here. > > > Regards, > > Christian > > > [0] https://lists.debian.org/debian-kde/2015/08/msg00166.html > > -- > kernel concepts GmbH Tel: +49-271-771091-11 > Sieghuetter Hauptweg 48 > D-57072 Siegen > http://www.kernelconcepts.de/ > -- Marc Bres Gil m...@bres.cat marc.b...@gmail.com
Re: Cannot shutown from plasma or sddm
Hi Marc, Am Dienstag 03 November 2015, 09:13:12 schrieb Marc Bres Gil: > Hello > > since some update made by half september, I cannot shutdown my computer > from the kmenu on plasma. When I choose the shutdown option, only logs off > and shows me the sddm. > When I try to shutdown from sddm it starts the countdown, but when reaches > zero, continues counting with negative numbers. > The /var/log/syslog shows the following: > > Nov 3 09:02:01 fangorn dbus[2715]: [system] Activating service > name='org.freedesktop.systemd1' (using servicehelper) > Nov 3 09:02:01 fangorn kernel: [ 3618.266611] kactivitymanage[4103]: > segfault at 7f8919e4acd0 ip 7f8919df4291 sp 7ffccd097278 error 4 in > libQt5Sql.so.5.5.1[7f8919de+3f000] > Nov 3 09:02:01 fangorn dbus[2715]: [system] Successfully activated service > 'org.freedesktop.systemd1' > Nov 3 09:02:01 fangorn acpid: client 2916[0:0] has disconnected > Nov 3 09:02:01 fangorn acpid: client connected from 7791[0:0] > Nov 3 09:02:01 fangorn acpid: 1 client rule loaded > Nov 3 09:02:21 fangorn dbus[2715]: [system] Activating service > name='org.freedesktop.systemd1' (using servicehelper) > Nov 3 09:02:21 fangorn dbus[2715]: [system] Successfully activated service > 'org.freedesktop.systemd1' > > Previously to the last update, the segfault was given at > libQt5Sql.so.5.4.2, i thought that with next update of this library it will > be solved, but it is still giving the error. > > Anybody else is having this problem? I'm experiencing this since end of August, see [0]. Back then, only SDDM would not reboot or shutdown, while both was possible from within Plasma. With the latest updates in stretch, though, shutting down the system from within Plasma also does not work for me. Plasma throws me back to SDDM, but no shutdown/reboot. May I ask, which init system do you use? For me, it is sysvinit (but with systemd-logind installed), maybe this is creating an issue here. Regards, Christian [0] https://lists.debian.org/debian-kde/2015/08/msg00166.html -- kernel concepts GmbH Tel: +49-271-771091-11 Sieghuetter Hauptweg 48 D-57072 Siegen http://www.kernelconcepts.de/ signature.asc Description: This is a digitally signed message part.
Cannot shutown from plasma or sddm
Hello since some update made by half september, I cannot shutdown my computer from the kmenu on plasma. When I choose the shutdown option, only logs off and shows me the sddm. When I try to shutdown from sddm it starts the countdown, but when reaches zero, continues counting with negative numbers. The /var/log/syslog shows the following: Nov 3 09:02:01 fangorn dbus[2715]: [system] Activating service name='org.freedesktop.systemd1' (using servicehelper) Nov 3 09:02:01 fangorn kernel: [ 3618.266611] kactivitymanage[4103]: segfault at 7f8919e4acd0 ip 7f8919df4291 sp 7ffccd097278 error 4 in libQt5Sql.so.5.5.1[7f8919de+3f000] Nov 3 09:02:01 fangorn dbus[2715]: [system] Successfully activated service 'org.freedesktop.systemd1' Nov 3 09:02:01 fangorn acpid: client 2916[0:0] has disconnected Nov 3 09:02:01 fangorn acpid: client connected from 7791[0:0] Nov 3 09:02:01 fangorn acpid: 1 client rule loaded Nov 3 09:02:21 fangorn dbus[2715]: [system] Activating service name='org.freedesktop.systemd1' (using servicehelper) Nov 3 09:02:21 fangorn dbus[2715]: [system] Successfully activated service 'org.freedesktop.systemd1' Previously to the last update, the segfault was given at libQt5Sql.so.5.4.2, i thought that with next update of this library it will be solved, but it is still giving the error. Anybody else is having this problem? Thanks -- Marc Bres Gil
