Success! I started killing items in htop and requesting the shutdown
menu until I got the culprit. WICD. I am not sure why, but that daemon
was causing the minute delay. I use the internet on it pretty rarely so
I'll just remove that from the startup list.
I am usually a patient person and would deal with this, but I use this
laptop on stage and and when the sound dude and next act wants to setup,
I usually like to expidite my equipment takedown. Also, there was no
delay when I ran 64 Studio 2.1 on this same machine which gave me hope
for solving it.
Thanks for the shove in the right direction Ralf.
On 2/8/10 8:58 PM, Ralf Mardorf wrote:
> Brian Bergstrom wrote:
>> I recently install 64 Studio 3.0b3 on my Thinkpad T22. Everything works
>> great except for shutting down. I click the menu and select the item to
>> shutdown/logout/reboot and it just sits there for 30-60 seconds. It
>> isn't frozen as I can't still manipulate the gui. Then finally the
>> dialog pops up for me to choose logout/shutdown/reboot.
>> I didn't see anything in the log that was causing this.
>> How would I go about debugging this to find out what is causing the stall?
> Phew, did you try a stacktrace? It's weird, but OTOH, if there are no
> additional issues, it might be something acceptable.
> Did you compile a lot of applications without adding those applications
> to the package management, so that the package management is detecting
> putatively unneeded packages (dependencies for the installed
> applications, that were installed, but not by a package)? I'm able to
> imagine that detecting issues similar to putatively unneeded packages
> could take some time.
> Another thought, when you end a session, will it store running
> applications and restore them for the next session? Perhaps there will
> be 100 instances of jackd, that needs to be killed for each shut down.
> It might be something very simple. Did you run top to see if there are
> unwanted threads etc.?
> If everything is fine, but just logout, shutdown and reboot is delayed
> for less than 2 minutes (but unfortunately for a minute), I also would
> ask the list, but accept it, if nobody should know how to fix this
> unusual behaviour.
> Does this appear since you installed 64 Studio, or was 64 Studio ok for
> a while and does it appear after using 64 Studio for a while?
> I guess a stacktrace would be impossible, because your system seems to
> be ok, but just annoying, when you end a session.
> 64studio-users mailing list
64studio-users mailing list