gnome crashes when system suspends with smb shares still mounted

Thanks for your bug report. Please try to obtain a backtrace http://wiki.ubuntu.com/DebuggingProgramCrash or get the crash report from /var/crash and attach the file to the bug report. This will greatly help us in tracking down your problem.

Here's the crash report

and the backtrace

Upgraded from edgy to feisty -- same problem.

Decided to live dangerously and perm mounted the smb shares with fstab on feisty -- mounting works fine but if the laptop gets disconnected from the network whilst nautilus is running, nautilus crashes taking not only GNOME but the whole system with it.

This isn't related to suspend -- suspend is so flakey in feisty I've given up on it. It happens if the laptop can't connect to the shares either because the network has dropped or the host has been booted down.

I posted the info requested -- is there more info you need?

On Tue, 2007-05-15 at 12:48 +0000, Sebastien Bacher wrote:

> ** Changed in: nautilus (Ubuntu)
> Status: Needs Info => Unconfirmed
>

not for now, what we need is extra people to deal with the huge number of bugs we get, I've marked this one unconfirmed so maybe somebody else can pick on it

OK, thanks :)

On Wed, 2007-05-16 at 17:38 +0000, Sebastien Bacher wrote:

> not for now, what we need is extra people to deal with the huge number
> of bugs we get, I've marked this one unconfirmed so maybe somebody else
> can pick on it
>

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? May you try to reproduce it with a newer version of Ubuntu like Gutsy? Thanks in advance.

Yes, still having exactly the same problem with nautilus in Feisty,
probably related to more general problems with fstab and mount
commands. If I unmount the drive on the commandline, it doesn't
actually unmount.

if I comment out the line in fstab which mounts the smb shares and
do a mount -a command then mount, it's gone from the list -- but if
I mount it again, Feisty tries to mount it twice (I imagine it never
was unmounted). I have to reboot to get Feisty to recognise that the
line is commented out in fstab.

I haven't tried to do it for a while (I just work around it), I'll
try to find time over the next week to play with it systematically
and let you know exactly what it's doing.

The most annoying aspect is that since I can't even unmount the
drive manually, I actually have to reboot my entire system when I
change from wired to wireless connection -- it's a serious nuisance.

Paula

Pedro Villavicencio wrote:
> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. You reported this bug a while ago and there hasn't been
> any activity in it recently. We were wondering is this still an issue
> for you? May you try to reproduce it with a newer version of Ubuntu like
> Gutsy? Thanks in advance.
>
> ** Changed in: nautilus (Ubuntu)
> Status: New => Incomplete
>

could you try to get a backtrace of nautilus when it's hanging? the one you attached was a normal exit of the program, not a hang or crash

Just repeated the backtrace, nautilus is exiting normally. Sorry to
waste your time, I haven't really tried it properly on Feisty before.

On dapper, it was crashing cataclysmically -- but I didn't know I
needed to install debug symbols before doing the backtrace then so
the log was probably useless.

Thanks! It seems to be working fine now -- I've put the mounts back
into fstab (and now I've got the hang of backtracing properly so it
wasn't a total waste of time for me).

Sorry and thanks!

Paula

Sebastien Bacher wrote:
> could you try to get a backtrace of nautilus when it's hanging? the one
> you attached was a normal exit of the program, not a hang or crash
>

closing if that's working correctly now, you can reopen if you get the issue again though

Thanks!

Sebastien Bacher wrote:
> closing if that's working correctly now, you can reopen if you get the
> issue again though
>
> ** Changed in: nautilus (Ubuntu)
> Status: Incomplete => Invalid
>