Ubuntu
evolution package

Evolution hangs with soup_connection_reserve and soup_connection_send_request errors

Bug #128985 reported by Aaron C. de Bruyn
2
Affects Status Importance Assigned to Milestone
evolution (Ubuntu)
Invalid
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: evolution

I start evolution from the command-line and get the following until I hit CTRL+C:

$ evolution
CalDAV Eplugin starting up ...

(evolution-2.10:6734): libsoup-CRITICAL **: soup_connection_reserve: assertion `SOUP_IS_CONNECTION (conn)' failed

(evolution-2.10:6734): libsoup-CRITICAL **: soup_connection_send_request: assertion `SOUP_IS_CONNECTION (conn)' failed

(evolution-2.10:6734): libsoup-CRITICAL **: soup_connection_reserve: assertion `SOUP_IS_CONNECTION (conn)' failed

(evolution-2.10:6734): libsoup-CRITICAL **: soup_connection_send_request: assertion `SOUP_IS_CONNECTION (conn)' failed

<CTRL+C>

My copy of evolution is setup with two connections. One IMAP and one to an exchange server.

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

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

Changed in evolution:
assignee: nobody → desktop-bugs
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Aaron C. de Bruyn (darkpixel2k) wrote :

I usually run into this once or twice a month.
As soon as it pops up, I'll get it to you.

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
Aaron C. de Bruyn (darkpixel2k) wrote :

It is difficult to reproduce, but I believe I have tracked down the core issue.
The problem stopped happening very shortly after I posted the bug.
One of the network techs at the office said someone made a bad cable and they were getting a lot of packet loss between one machine and the switch.
As soon as the cable was replaced, I stopped having the issue.

I'm assuming the packet loss caused the error.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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