Mailinglist Archive: opensuse-bugs (3178 mails)

< Previous Next >
[Bug 760433] New: Can't cancel image retrieval in Evolution
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Thu, 3 May 2012 04:48:15 +0000
  • Message-id: <bug-760433-21960@http.bugzilla.novell.com/>

https://bugzilla.novell.com/show_bug.cgi?id=760433

https://bugzilla.novell.com/show_bug.cgi?id=760433#c0


Summary: Can't cancel image retrieval in Evolution
Classification: openSUSE
Product: openSUSE 12.1
Version: Final
Platform: x86-64
OS/Version: openSUSE 12.1
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Evolution
AssignedTo: bnc-team-evolution@xxxxxxxxxxxxxxxxxxxxxx
ReportedBy: dhwprof@xxxxxxxxx
QAContact: lakhil@xxxxxxxxxx
Found By: ---
Blocker: ---


User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20100101
Firefox/12.0

It doesn't seem to be possible to cancel the retrieval of an image when a
message is being displayed. If, for whatever reason, an image retrieval takes
a very long time, It's not possible switch to another message. Clicking on the
little red "cancel" button in the status bar changes the status to say it's
being canceled, but the canceling process never finishes. Exiting from
Evolution doesn't work, either. I have to use "evolution --force-shutdown" to
cause Evolution to exit.

Reproducible: Sometimes

Steps to Reproduce:
Unfortunately, this is hard to reproduce on demand. You need a message that
includes an image that's stored on a server that's very slow or never completes
the transfer. (I've found that Radio Shack ads are often culprits.) Once you
find one, then click on the red cancel button in the status bar.
Actual Results:
Evolution hangs waiting for an image retrieval to complete (or cancel).

Expected Results:
The image retrieval should time out within a reasonable period of time, and
canceling it should occur immediately. Exiting from Evolution should never
hang.

--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

< Previous Next >
This Thread
  • No further messages