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?

Thanks,
Brian
_______________________________________________
64studio-users mailing list
64studio-users@lists.64studio.com
http://lists.64studio.com/mailman/listinfo/64studio-users

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?
>
> Thanks,
> Brian

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.

*?*
Ralf
_______________________________________________
64studio-users mailing list
64studio-users@lists.64studio.com
http://lists.64studio.com/mailman/listinfo/64studio-users

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.

Cheers,
Brian

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?
>>
>> Thanks,
>> Brian
>>
> 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.
>
> *?*
> Ralf
> _______________________________________________
> 64studio-users mailing list
> 64studio-users@lists.64studio.com
> http://lists.64studio.com/mailman/listinfo/64studio-users
>
_______________________________________________
64studio-users mailing list
64studio-users@lists.64studio.com
http://lists.64studio.com/mailman/listinfo/64studio-users

Brian Bergstrom wrote:
> WICD

I don't know WICD. Anyway, we do a shutdown to enable that all running
processes can store useful data and settings. It's conceivably that a
network manager needs to manage and store a lot on shutdown.
If you like this network manager you should contact the coder(s). Maybe
this is a solvable issue.

I remember my C64 and Atari ST. No shutdown, just a switch to turn it
off .

IMO killing WICD before the shutdown seems not to be a good solution, as
long as the reason for the stall is unknown.

Ralf
_______________________________________________
64studio-users mailing list
64studio-users@lists.64studio.com
http://lists.64studio.com/mailman/listinfo/64studio-users

Brian Bergstrom wrote:
> I use the internet on it pretty rarely so I'll just remove that from the startup list.
>

You used it just for the internet? Depending to the kind of connection,
there should be an alternative application able to do the same job.
Maybe WICD stalled, because it tries to detect, if there are any other
network connections done by other applications that need the information
that they have to log out.
_______________________________________________
64studio-users mailing list
64studio-users@lists.64studio.com
http://lists.64studio.com/mailman/listinfo/64studio-users

I think I got a bit excited. It turns out that after the first attempt
to get the shutdown dialog, it pops up instantly after that. WICD was
the first thing I killed, so I thought it was the culprit. I removed it
from startup and uninstalled it from the system, but the shutdown delay
still happens. Herm, back to step one.

On 2/9/10 5:51 AM, Ralf Mardorf wrote:
> Brian Bergstrom wrote:
>
>> WICD
>>
> I don't know WICD. Anyway, we do a shutdown to enable that all running
> processes can store useful data and settings. It's conceivably that a
> network manager needs to manage and store a lot on shutdown.
> If you like this network manager you should contact the coder(s). Maybe
> this is a solvable issue.
>
> I remember my C64 and Atari ST. No shutdown, just a switch to turn it
> off .
>
> IMO killing WICD before the shutdown seems not to be a good solution, as
> long as the reason for the stall is unknown.
>
> Ralf
> _______________________________________________
> 64studio-users mailing list
> 64studio-users@lists.64studio.com
> http://lists.64studio.com/mailman/listinfo/64studio-users
>
_______________________________________________
64studio-users mailing list
64studio-users@lists.64studio.com
http://lists.64studio.com/mailman/listinfo/64studio-users

Hi Brian,

> I think I got a bit excited. It turns out that after the first attempt
> to get the shutdown dialog, it pops up instantly after that. WICD was
> the first thing I killed, so I thought it was the culprit. I removed it
> from startup and uninstalled it from the system, but the shutdown delay
> still happens.

I've seen something similar on 3.0 beta3, only for certain users of the
system though. Hopefully this will have been fixed upstream by the time
of our next beta.

Cheers!

Daniel
_______________________________________________
64studio-users mailing list
64studio-users@lists.64studio.com
http://lists.64studio.com/mailman/listinfo/64studio-users

Greetings,

From notes made during my last Ubuntu install (Karmic) :

Shutdown didn't work properly until i fixed /etc/init.d/umountfs :

this line:
fstab-decode umount -f -r -d $WEAK_MTPTS
becomes:
fstab-decode umount -r -d $WEAK_MTPTS

and this line:
fstab-decode umount -f -v -r -d $WEAK_MTPTS
becomes:
fstab-decode umount -v -r -d $WEAK_MTPTS

These changes fixed the shutdown problem on my laptop, an HP G60
notebook. YMMV.

Best,

dp




_______________________________________________
64studio-users mailing list
64studio-users@lists.64studio.com
http://lists.64studio.com/mailman/listinfo/64studio-users

Dave Phillips wrote:
> Greetings,
>
> From notes made during my last Ubuntu install (Karmic) :
>
> Shutdown didn't work properly until i fixed /etc/init.d/umountfs :
>
> this line:
> fstab-decode umount -f -r -d $WEAK_MTPTS
> becomes:
> fstab-decode umount -r -d $WEAK_MTPTS
>
> and this line:
> fstab-decode umount -f -v -r -d $WEAK_MTPTS
> becomes:
> fstab-decode umount -v -r -d $WEAK_MTPTS
>
> These changes fixed the shutdown problem on my laptop, an HP G60
> notebook. YMMV.
>
> Best,
>
> dp

I fear this won't solve his problem, because for 3.0-beta3 there aren't
those lines. /etc/init.d/umountfs is from my 64 Studio 3.0-beta3
installation and /media/disk/etc/init.d/umountfs is from my Karmic
(openArtist) installation.

spinymouse-sudo@64studio:~$ cat /etc/init.d/umountfs | grep fstab-decode
spinymouse-sudo@64studio:~$ cat /media/disk/etc/init.d/umountfs | grep
fstab-decode
fstab-decode umount $TMPFS_MTPTS
fstab-decode umount -v $TMPFS_MTPTS
fstab-decode umount -r -d $WEAK_MTPTS
fstab-decode umount -v -r -d $WEAK_MTPTS
fstab-decode umount -f -r -d $REG_MTPTS
fstab-decode umount -f -v -r -d $REG_MTPTS

But for 3.0-beta3 there are the lines ...

if echo "$WEAK_MTPTS" | grep -qs " $MTPT "; then
FORCE=""
else
FORCE="-f"
fi

Perhaps he could test what happens if he comment out anything, but FORCE="".

#if echo "$WEAK_MTPTS" | grep -qs " $MTPT "; then
FORCE=""
#else
#FORCE="-f"
#fi


Btw. I need to read the man page: "-f Force unmount (in case of an
unreachable NFS system)."
_______________________________________________
64studio-users mailing list
64studio-users@lists.64studio.com
http://lists.64studio.com/mailman/listinfo/64studio-users

Hello, Brian,

2010/2/9 Brian Bergstrom <boilingbergstrom@gmail.com>:
> I think I got a bit excited. Â*It turns out that after the first attempt
> to get the shutdown dialog, it pops up instantly after that. Â*WICD was
> the first thing I killed, so I thought it was the culprit. Â*I removed it
> from startup and uninstalled it from the system, but the shutdown delay
> still happens. Â*Herm, back to step one.

Do you have Power manager process running?
Once I had such issue when I removed gnome-power-manager as
"unnecessary" for desktop PC.
But you mentioned a laptop, so my guess could be wrong.


Antanas Budriūnas
_______________________________________________
64studio-users mailing list
64studio-users@lists.64studio.com
http://lists.64studio.com/mailman/listinfo/64studio-users