By default, Bugzilla does not search the list of RESOLVED bugs.
You can force it to do so by putting the upper-case word ALL in front of your search query, e.g.: ALL tdelibs
We recommend searching for bugs this way, as you may discover that your bug has already been resolved and fixed in a later release.
Bug 1209 - Shutdown won't complete if TDM is/was running
Summary: Shutdown won't complete if TDM is/was running
Status: RESOLVED DUPLICATE of bug 1233
Alias: None
Product: TDE
Classification: Unclassified
Component: tdebase (show other bugs)
Version: R14.0.0 [Trinity]
Hardware: i386 Debian Squeeze
: P5 major
Assignee: Timothy Pearson
URL:
Depends on:
Blocks:
 
Reported: 2012-09-13 13:10 CDT by Kris
Modified: 2013-04-22 13:28 CDT (History)
3 users (show)

See Also:
Compiler Version:
TDE Version String:
Application Version:
Application Name:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Kris 2012-09-13 13:10:06 CDT
When my system boots into TDM, if I tell it to shutdown (either while logged in or from TDM menu), it will go through the normal process of shutting down processes, but will end with a message similar to:

"init: no more processes left in this level"

Even if I switch to a VT, do a "service tdm-trinity stop && shutdown -hP now", I get the same error.

I managed to fix this issue by going into "Control Center -> System Admin -> Login Manager -> Shutdown" and changing both the halt and reboot options.

Originally, halt pointed to "/sbin/poweroff", but I changed it to "/sbin/shutdown -hP now" (without quotes, of course).

Reboot now points to "/sbin/shutdown -r now" (without quotes).

This issue no longer affects my system, but should be included in the vanilla packaging.

Since distro hopping has shown that some distros handle the poweroff/reboot commands slightly differently, I filed this specifically against Debian (my current distro), though I would recommend this fix for all of TDE.
Comment 1 Slávek Banko 2013-04-22 13:28:57 CDT
Bug 1233 contain more informations about this issue. Therefore I close this as a duplicate, even though it was reported earlier,

*** This bug has been marked as a duplicate of bug 1233 ***