The problem did not occur anymore, so I set this bug report to fixed. I don't know, which updates have solved this problem, but there were many updates regarding systemd, upstart, kernel updates, udev, etc .
** Changed in: kde-workspace (Ubuntu) Status: New => Fix Released ** Changed in: upstart (Ubuntu) Status: New => Fix Released ** Changed in: acpid (Ubuntu) Status: New => Fix Released ** Changed in: upstart (Ubuntu) Assignee: (unassigned) => Bernhard (baumber) ** Changed in: kde-workspace (Ubuntu) Assignee: (unassigned) => Bernhard (baumber) ** Changed in: acpid (Ubuntu) Assignee: (unassigned) => Bernhard (baumber) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1421429 Title: [trusty] Frequently no clean shutdown or reboot Status in acpid package in Ubuntu: Fix Released Status in kde-workspace package in Ubuntu: Fix Released Status in upstart package in Ubuntu: Fix Released Bug description: Hello, on all of my installations of Kubuntu 14.04.x (3 PCs), frequently on a shutdown or reboot the PC powers off or reboots without umounting the filesystems and terminating the processes. There is no message like "Terminating or killing all processes within x seconds, umounting filesystems, etc", but immediately the shutdown (power off) or reboot of the system, all via KDE. => No clean shutdown. (No network shares are mounted.) Next boot the fsck is recovering the filesystem/journal, etc This behaviour occurred after the upgrade from 12.04.x to 14.04.x , this was not in 12.04. Maybe it is a bug in upstart/systemd init scripts at reboot/shutdown. - Reproducible with: Download the iso image kubuntu-14.04.2-desktop-amd64.iso and install it, for instance as a Virtual Machine. There logon in KDE and use the keyboard shortcut "ctl+alt+shift+pageup" (=Reboot) to reboot the machine several times until you can see that on the reboot/shutdown process there is no clean reboot, but an immediate reboot. On the next boot you will see that fsck is recovering the journal (inodes cleared/recovered), etc. Thank you for your support! Best regards, Bernhard ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: upstart 1.12.1-0ubuntu4.2 ProcVersionSignature: Ubuntu 3.16.0-31.41~14.04.1-generic 3.16.7-ckt5 Uname: Linux 3.16.0-31-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 CurrentDesktop: KDE Date: Thu Feb 12 22:40:45 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2010-06-02 (1716 days ago) InstallationMedia: Kubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100427) SourcePackage: upstart UpgradeStatus: Upgraded to trusty on 2015-01-18 (25 days ago) UpstartBugCategory: Session UpstartRunningSessionCount: 1 UpstartRunningSessionVersion: init (upstart 1.12.1) UpstartRunningSystemVersion: init (upstart 1.12.1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpid/+bug/1421429/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp