Evolution slow to display window for composing new message/reply.

Bug #159153 reported by DavidS
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
evolution (Ubuntu)
Invalid
Low
Ubuntu Desktop Bugs

Bug Description

Binary package hint: evolution

After clicking on "Reply" or "New" to compose a message, there is a delay of about 6 seconds before the new window appears, running Ubuntu 7.10 on a PC with Pentium 4 1.5GHz. This is not a new problem - it has been there since I started using Ubuntu and Evolution about 18 months ago. I consider this to be a bug - minor, perhaps, but extremely irritating.

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for your bug report. Do you have high CPU usage during this delay? Could you try using a stock configuration if you have the same issue there?

Changed in evolution:
assignee: nobody → desktop-bugs
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
DavidS (david-aeolia) wrote :

Using 'top', I see CPU usage shoot up from around 0-5% to about 90% during the delay. I'm afraid I don't understand your second question.

Revision history for this message
Sebastien Bacher (seb128) wrote :

Could you try with an another user and a new configuration?

Revision history for this message
DavidS (david-aeolia) wrote : Re: [Bug 159153] Re: Evolution slow to display window for composing new message/reply.

On Fri, 2008-02-08 at 14:03 +0000, Sebastien Bacher wrote:
> Could you try with an another user and a new configuration?

I have now tried with a new user - so everything was set up pretty much
"out of the box". Same result - about 6 seconds for a new message
window to appear.

Revision history for this message
Sebastien Bacher (seb128) wrote :

there is no enough informations to work on the issue there, could be due to a network configuraton issue. Could you try to get stacktrace when it's hanging?

Revision history for this message
Pedro Villavicencio (pedro) wrote :

Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!.

Changed in evolution:
status: Incomplete → Invalid
Revision history for this message
Chris Hutt (chrishutt) wrote :

I have the same problem and would be happy to provide the stacktrace but I'm not sure how. If someone could explain how to then I'll do it.

I have attached the output from running evolution --debug and clicking reply

Note. The following line is repeated as soon as I click reply or new.

(evolution:15779): Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated

Don't know if it helps.

Chris Hutt (chrishutt)
Changed in evolution:
status: Invalid → Confirmed
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Instructions on how to get a backtrace are here: http://wiki.ubuntu.com/DebuggingProgramCrash please attach the resulting file to the report, if you have any question just ask us, thanks.

Changed in evolution:
status: Confirmed → Incomplete
Revision history for this message
Tessa Lau (tlau) wrote :

I am seeing this now with Evolution 2.24.1-0ubuntu2 on Ubuntu Ibex. Replying to a message or composing a new message causes a delay of about 2 minutes before the compose window pops up. During that time, the entire application is frozen and does not repaint. CPU usage is minimal.

Backtrace is attached.

I suspect this might be related to some kind of network problem. I first started seeing this problem after upgrading from hardy to ibex. I believe the cause was related to network-manager reporting that the system was offline; see bug https://bugs.edge.launchpad.net/ubuntu/+source/network-manager/+bug/82335. Uninstalling network-manager made most of the problems (including this Evolution bug) go away. However, after a dist-upgrade yesterday, I suddenly started seeing this problem again, making Evolution fairly unusable.

Revision history for this message
Tessa Lau (tlau) wrote :

Here's a more complete backtrace with the debug versions of libdbus and libtrackerclient included. It looks like it's hanging while trying to get the tracker version. That isn't normal, is it?

Uninstalling libtrackerclient0 and all its dependencies does fix the problem for me.

Revision history for this message
Sebastien Bacher (seb128) wrote :

the new comments are a tracker issue and not an evolution one, not sure if the bug submitter has the same issue though

Revision history for this message
Chris Hutt (chrishutt) wrote : Re: [Bug 159153] Re: Evolution slow to display window for composing new message/reply.

Thanks, doing it now.

On Thu, 2008-11-20 at 17:25 +0000, Pedro Villavicencio wrote:

> Instructions on how to get a backtrace are here:
> http://wiki.ubuntu.com/DebuggingProgramCrash please attach the resulting
> file to the report, if you have any question just ask us, thanks.
>
> ** Changed in: evolution (Ubuntu)
> Status: Confirmed => Incomplete
>

Revision history for this message
Chris Hutt (chrishutt) wrote :

I dont't think it worked properly but here it is anyway.

Revision history for this message
Pedro Villavicencio (pedro) wrote :

there's nothing on the log you attached, please try again, thanks.

Revision history for this message
Tessa Lau (tlau) wrote :

Agreed, my issue was related to tracker, not evolution.

If anyone else is following my path, here's the more relevant bug report (ignore the misleading title, it's not about nfs): https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/218230

Revision history for this message
Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in evolution:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.