Envirionment: Plasma 5
Symptoms: Choosing restart option from right click on Desktop
Result: System appears to be correctly beginning its sequence; Drops to black screen where it shows the log in prompt;
Expected outcome: should turn to black and continue until grub screen appears for boot choices
What actually happens: Screen turns to black and appears to my ears (I can hear the birds tweeting in the trees outside) to have completely closed down. At the end of 30 seconds (counted it on last delayed restart); system then seems to wake up and continue restarting.
Any logs I could look at? And what would I be looking for?
Anyway to see output during restart? e.g. [Esc] except that [Esc] doesn’t work. Maybe my timing is out on the escape keypress
I’m pretty sure this has only just started happening. I remember now it did happen once before, might been after the first restart on the Plasma install. The second restart would have been fine also then the third one wasn’t. Then the fourth restart was also OK. (This is a guesswork type of memory trying to display a rough sequence of events - I’ve no idea how many times I have restarted). The one itme it did restart successfully in the aftermath of not restarting properly led me to think it was a minor glitch after an update. Now it is a consistent repeatable delay.
I originally installed Gnome from the network ISO and decided a couple of days ago to install plasma. I did this from Yast2.
Result was a fully functioning Plasma desktop which is performing beautifully and continues to do so - except of course for the extended restart.
I haven’t logged into a Gnome session since I installed plasma
Just on the off chance there was a borked something or other, I downloaded the DVD and installed only KDE on a separate partition.
First two reboots were fine. Third restart is behaving exactly like the installation described above.
Things that I did on the new install:
zypper lu and zypper up.
Added the nvidia repository and installed the Nvidia proprietary for my card -x11-video-G03 and all the accompanying bits and pieces to a total of 95 MB - as the nouveau/gallium was having difficulties displaying the Desktop on login - otherwise I would have let it run for a while - benefit of the doubt and anxious to encourage FOSS development.
added pavucontrol
system setting and turned off power management stuff; display and monitor set to please don’t dim go black or do anything I don’t want you to do.
configured Dolphin - hardly system threatening behaviour.
mounted a couple of internal drives from Dolphin>Places to retrieve a couple of files. Umounted them using right-click menu in Dolphin>Places
So after a happy hour or so of playing I am back with a weird restart/reboot delay.
Any thoughts suggestions? I did notice while I was in System Settings that there was an advanced tab with a place to put halt or restart commands.
I’d never seen that area before - so therefore I figure I don’t need it. Why is it there? Who would use or benefit from it?
I can embed a short account of the moments leading up to finally restarting:
# journalctl --list-boot
-4 fa071f58ef7b4367b804dee520939457 Sun 2015-11-08 15:49:14 NZDT—Sun 2015-11-08 16:02:39 NZDT
-3 cb6d6a6fe47c43cc8617641f557da8cb Sun 2015-11-08 16:03:13 NZDT—Sun 2015-11-08 16:31:35 NZDT
-2 105680763a87454d9b56058d34c77425 Sun 2015-11-08 16:33:45 NZDT—Sun 2015-11-08 16:56:11 NZDT
-1 a4d99c3d883447b0ac3ae414f365d615 Sun 2015-11-08 20:44:37 NZDT—Sun 2015-11-08 21:13:23 NZDT
0 770384e6b2514726b8c86c55403a772f Sun 2015-11-08 21:13:49 NZDT—Sun 2015-11-08 21:15:22 NZDT
# journalctl -b a4d99c3d883447b0ac3ae414f365d615 -r
-- Logs begin at Sun 2015-11-08 15:49:14 NZDT, end at Sun 2015-11-08 21:15:22 NZDT. --
Nov 08 21:13:23 linux-lgum systemd-journal[364]: Journal stopped
Nov 08 21:13:23 linux-lgum kernel: watchdog watchdog0: watchdog did not stop!
Nov 08 21:13:23 linux-lgum kernel: audit: type=1130 audit(1446970403.346:221): pid=1 uid=0 auid=4294967295 ses=4294967295 msg=' comm="halt-local" exe="/usr/l
Nov 08 21:13:23 linux-lgum kernel: audit: type=1131 audit(1446970403.334:220): pid=1 uid=0 auid=4294967295 ses=4294967295 msg=' comm="systemd-readahead-colle
Nov 08 21:13:23 linux-lgum kernel: audit: type=1131 audit(1446970403.334:219): pid=1 uid=0 auid=4294967295 ses=4294967295 msg=' comm="systemd-readahead-repla
Nov 08 21:13:23 linux-lgum kernel: audit: type=1131 audit(1446970403.334:218): pid=1 uid=0 auid=4294967295 ses=4294967295 msg=' comm="systemd-remount-fs" exe
Nov 08 21:13:23 linux-lgum kernel: audit: type=1130 audit(1446970403.326:217): pid=1 uid=0 auid=4294967295 ses=4294967295 msg=' comm="plymouth-reboot" exe="/
Nov 08 21:13:23 linux-lgum kernel: audit: type=1131 audit(1446970403.290:216): pid=1 uid=0 auid=4294967295 ses=4294967295 msg=' comm="auditd" exe="/usr/lib/s
Nov 08 21:13:23 linux-lgum kernel: audit: type=1305 audit(1446970403.286:215): audit_pid=0 old=444 auid=4294967295 ses=4294967295 res=1
Nov 08 21:13:23 linux-lgum auditd[444]: The audit daemon is exiting.
Nov 08 21:13:23 linux-lgum boot.apparmor[2420]: Unloading AppArmor profiles ..done
Nov 08 21:13:23 linux-lgum sddm[1160]: QProcess: Destroyed while process ("/usr/lib/sddm/sddm-helper") is still running.
Nov 08 21:13:23 linux-lgum sddm[1160]: Running display stop script "/usr/share/sddm/scripts/Xstop"
Nov 08 21:13:23 linux-lgum sddm[1160]: Display server stopped.
Nov 08 21:13:22 linux-lgum sddm-helper[2409]: [PAM] returning.
Nov 08 21:13:22 linux-lgum sddm-helper[2409]: [PAM] Authenticating...
Nov 08 21:13:22 linux-lgum sddm-helper[2409]: [PAM] Starting...
Nov 08 21:13:22 linux-lgum sddm[1160]: Display server stopping...
Nov 08 21:13:22 linux-lgum sddm[1160]: Socket server stopped.
Nov 08 21:13:22 linux-lgum sddm[1160]: Socket server stopping...
Nov 08 21:13:22 linux-lgum sddm[1160]: Signal received: SIGTERM
Nov 08 21:13:22 linux-lgum sddm[1160]: Adding cookie to "/run/sddm/{7cd257a1-7472-45a5-a97a-207994fb0c5a}"
Nov 08 21:13:22 linux-lgum sddm[1160]: Greeter starting...
Nov 08 21:13:22 linux-lgum sddm[1160]: Socket server started.
Nov 08 21:13:22 linux-lgum sddm[1160]: Socket server starting...
Nov 08 21:12:56 linux-lgum display-manager[2182]: Shutting down service sddm..done
Nov 08 21:12:52 linux-lgum sddm[1160]: Running display setup script "/etc/X11/xdm/Xsetup"
Nov 08 21:12:52 linux-lgum wicked[2237]: eth0 device-ready
Nov 08 21:12:52 linux-lgum wickedd-dhcp6[839]: eth0: no lease set
Nov 08 21:12:51 linux-lgum sddm[1160]: Running: /usr/bin/X -nolisten tcp -auth /run/sddm/{7cd257a1-7472-45a5-a97a-207994fb0c5a} -background none -noreset -di
Nov 08 21:12:51 linux-lgum sddm[1160]: Display server starting...
Nov 08 21:12:51 linux-lgum sddm[1160]: Adding new display on vt 7 ...
Nov 08 21:12:51 linux-lgum sddm[1160]: Removing display ":0" ...
Nov 08 21:12:51 linux-lgum sddm[1160]: Running display stop script "/usr/share/sddm/scripts/Xstop"
Nov 08 21:12:51 linux-lgum wickedd-dhcp4[840]: eth0: Request to release DHCPv4 lease with UUID 70fd3e56-c879-0000-4a03-000005000000
Nov 08 21:12:51 linux-lgum postfix/master[1744]: terminating on signal 15
Nov 08 21:12:51 linux-lgum SuSEfirewall2[2218]: Not unloading firewall rules at system shutdown
Nov 08 21:12:51 linux-lgum postfix/postfix-script[2214]: stopping the Postfix mail system
Nov 08 21:12:51 linux-lgum bluetoothd[1565]: Exit
Nov 08 21:12:51 linux-lgum bluetoothd[1565]: Stopping SDP server
Nov 08 21:12:51 linux-lgum bluetoothd[1565]: Terminating
Nov 08 21:12:51 linux-lgum iscsiadm[2174]: iscsiadm: No matching sessions found
Nov 08 21:12:51 linux-lgum ca.desrt.dconf[1396]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an
Nov 08 21:12:51 linux-lgum org.kde.kglobalaccel[1396]: after 380 requests (378 known processed) with 0 events remaining.
Nov 08 21:12:51 linux-lgum org.kde.kglobalaccel[1396]: XIO: fatal IO error 6 (No such device or address) on X server ":0"
Nov 08 21:12:51 linux-lgum org.kde.kglobalaccel[1396]: The X11 connection broke: I/O error (code 1)
Nov 08 21:12:51 linux-lgum avahi-daemon[742]: avahi-daemon 0.6.31 exiting.
Nov 08 21:12:51 linux-lgum avahi-daemon[742]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.0.2.
Nov 08 21:12:51 linux-lgum avahi-daemon[742]: Leaving mDNS multicast group on interface eth0.IPv6 with address fe80::225:64ff:fe8b:4cbf.
Nov 08 21:12:51 linux-lgum systemd[1347]: pam_unix(systemd-user:session): session closed for user hugh
Nov 08 21:12:51 linux-lgum ModemManager[748]: <info> ModemManager is shut down
Nov 08 21:12:51 linux-lgum ModemManager[748]: <info> Caught signal, shutting down...
Nov 08 21:12:51 linux-lgum smartd[745]: smartd is exiting (exit status 0)
Nov 08 21:12:51 linux-lgum smartd[745]: Device: /dev/sdb [SAT], state written to /var/lib/smartmontools/smartd.WDC_WD10EAVS_32D7B1-WD_WCAU48420094.ata.state
Nov 08 21:12:51 linux-lgum smartd[745]: Device: /dev/sda [SAT], state written to /var/lib/smartmontools/smartd.WDC_WD1001FAES_75W7A0-WD_WCATR1943769.ata.stat
Nov 08 21:12:51 linux-lgum smartd[745]: smartd received signal 15: Terminated
Nov 08 21:12:51 linux-lgum avahi-daemon[742]: Got SIGTERM, quitting.
Nov 08 21:12:51 linux-lgum kernel: SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC= SRC=fe80:0000:0000:0000:0225:64ff:fe8b:4cbf DST=ff02:0000:0000:0000:0000:0000:0000
Nov 08 21:12:51 linux-lgum systemd[1]: Cannot find unit for notify message of PID 742.
Nov 08 21:12:51 linux-lgum sddm[1160]: Display server stopping...
Nov 08 21:12:51 linux-lgum sddm[1160]: Auth: sddm-helper exited with 15
Nov 08 21:12:51 linux-lgum sddm[1160]: Authentication error: "Process crashed"
Nov 08 21:12:51 linux-lgum sddm[1160]: Auth: sddm-helper crashed (exit code 15)
Nov 08 21:12:50 linux-lgum polkitd[759]: Unregistered Authentication Agent for unix-session:1 (system bus name :1.33, object path /org/kde/PolicyKit1/Authent
personally speaking I am very little the wiser. However sddm features quite a bit in the narrative.
eth0: no lease set
was marked in red as was watchdog didn’t stop. But I pay no mind to watchdog not stopping - i’ve seen that in Arch as well.
Me too… My Leap 42.1 install on my overclocked x-99 viper went well (except it doesn’t boot windows) including all zypper dups. I added the nvidia repros & it allowed me to configure my 4 displays – running great. I have not shut it down until now and “thought” it was not responding; did a hard shutdown with the off button.
I was able to reboot into multiboot 13.2 & then rebooted into Leap 42,1
This time it shutdown – just took forever.
I’m thinking the Nvidia install is the issue in my case.
I’ll reinstall the 13.2 bootloader & that will get back my full multi-boot capability.
I saw it in plasma when I tried it, even login takes longer than when I boot the system.
I am using xfce, enlightenment and gnome and this three looks good.
Come to think of it I didn’t test reboot with xfce, will do later as I have a laptop running Leap with xfce
@Snakedriver
I had slow reboot without nvidia (which in itself brought other issues with freezing), nvidia solved the freezing though.
Nevertheless, one of the first apps I tried ‘devede’ didn’t work in plasma 5
I installed gnome and switched completely to it. And it worked fine.
VLC is completely messed up not just in kde
So for now, it’s just one of my Laptops running xfce with Leap 42.1
I have now installed lightdm and set it up in /etc/sysconfig via the display manager component in Yast.
My Leap install restarted in a sensible time frame when - after rebooting to allow the newly installed display manager to take over.
I find incidences of problems recorded all over the web with plasma, sddm and nvidia occurring in the same sentences. I don’t know about Gnome (haven’t rebooted while sddm was in the display driving seat) but I do know that when I installed Plasma side by side with Gnome and found that sddm was now the display manager, that’s when the lengthy restarts began.
Obviously my reaserach will be scattered and patchy but there does seem to be a link with nvidia, plasma, sddm - and it’s not a healthy one or cause for great cheer.
When Wayland gets up and running (whenever that might be) surely us Plasma 5 users we will need sddm to ease our passage into the new world of video management?
I have an notebook with an older nvidia and two installs on SSD with nvidia closed driver and on HDD with noveau. In both cases starting restarts takes about 2minutes :-(((