Bug 233184 - evo can't attach "zero length" files
evo can't attach "zero length" files
Status: CLOSED UPSTREAM
Product: Fedora
Classification: Fedora
Component: evolution-data-server (Show other bugs)
rawhide
All Linux
low Severity medium
: ---
: ---
Assigned To: Milan Crha
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2007-03-20 16:00 EDT by Adam Jackson
Modified: 2007-11-30 17:11 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2007-05-24 07:13:49 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
GNOME Desktop 440919 None None None Never

  None (edit)
Description Adam Jackson 2007-03-20 16:00:10 EDT
Description of problem:

Trying to send /proc/bus/usb/devices as an attachment eventually times out with
a rather hilarious error message:

Cannot append message to mbox file: /home/ajax/.evolution/mail/local/Outbox:
Connection timed out

However, copying the file aside and attaching the copy works just fine. 
/prov/bus/usb/devices is listed as 0 bytes long in ls, so it's probably just evo
getting stuck waiting for zero bytes forever.

Version-Release number of selected component (if applicable):

evolution-2.9.92-1.fc7
Comment 1 Matthew Barnes 2007-03-23 18:13:43 EDT
Likely a problem in Camel, so changing the component to Evolution-Data-Server.

My guess is it's one of the CamelStream subclasses; CamelStreamFs perhaps.
Comment 2 Christopher Aillon 2007-04-17 15:38:50 EDT
Wanna upstream this Matt?
Comment 3 Milan Crha 2007-05-24 06:05:15 EDT
I'm not sure what I could do with this. Based on my observations, at
evolution-data-server/camel/camel-file-utils.c is in function camel_read used
function select, which waits for max 4 minutes on response from device, and if
it will fail (timeout), then the result is an error message mentioned above.

I think we could rather move this upstream and discuss with them how to solve it
properly.
Comment 4 Matthew Barnes 2007-05-24 06:50:37 EDT
Milan, yes please move this upstream.
Comment 5 Milan Crha 2007-05-24 07:13:49 EDT
Moving this upstream where we will continue to track the problem.
Please see [1] for further updates.

[1] http://bugzilla.gnome.org/show_bug.cgi?id=440919

Note You need to log in before you can comment on or make changes to this bug.