Evolution hangs after resuming from suspend

[Mackenzie Morgan]

Binary package hint: evolution

Ubuntu: 8.04.1
Evolution: 2.22.3.1-0ubuntu1

Steps to reproduce:
1. Have evolution running
2. Suspend
3. Resume
4. Connect to network
5. Wait
6. Keep waiting

What happens:
1. "Filtering Messages (0%)" shows in the statusbar until, as far as I can tell, forever.
2. File -> Quit might make Evolution stop redrawing, but it stays there
3. Forcibly closing the window (alt+f4 on metacity, mod+shift+c on xmonad, hitting the X) brings up the Force Quit dialog. Force Quitting kills the GUI. Something stays running in the background, though, so that trying to start evolution up again does not bring up a GUI and just results in the CPU doing a lot of extra work.
4. "pkill evolution" is the only way to fully kill it so a new session can be started

What should happen:
Evolution gets back online, downloads email data properly, and keeps responding. Or if not that, it can at least be exited properly so restarting it is easy.

[Sebastien Bacher (seb128)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

[Mackenzie Morgan (maco.m)]

It doesn't crash, it just gets kind of stuck. I can still search the cached mails (that's how I found the bug number to get here). Anyway, I just tried attaching strace to it, and I'm attaching the output. I didn't kill it yet, but you can maybe see what it's doing while it says "filtering 0%"

[Sebastien Bacher (seb128)]

right, you can attach gdb to running programs, that's explained on the wiki and get a stacktrace, it will tell us where it's hanging

[Sebastien Bacher (seb128)]

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and don't hesitate to submit bug reports in the future.

[Mackenzie Morgan (maco.m)]

GDB doesn't show any information whatsoever. It's totally blank. I tell it to "continue" once and then it gives a thread error. There is no crash to get a backtrace from, but if you look at the strace output, you'll see that it's polling and getting a socket error.

[Christian Doczkal (thyrus)]

I have the same/a similar problem on current Ubuntu 8.04. Evolution hangs reproducibly when trying to close the program after a suspend/resume cycle. I remember older versions of evolution hanging on every sort of network anomaly. So it looks like there is some check for error condititions missing.

There ssems to be a connection to:
http://bugzilla.gnome.org/show_bug.cgi?id=551788

Their bottom line is:
------------------------------------------------
> In addition choosing File->Quit does nothing until it finally quits
> evolution about 10 minutes later.
Disconnect from the network in nm-applet and reconnect fixes this for me, but
it's annoying.
-----------------------------------------------

So it appears to be improper handling of changing networks/invalid sockets when doing suspend.

[Sebastien Bacher (seb128)]

could you copy the gdb to the log and describe what you are doing exactly?

[Sebastien Bacher (seb128)]

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and don't hesitate to submit bug reports in the future.