Bug 297631 - Beagle causing Evolution to hang when adding attachments
Beagle causing Evolution to hang when adding attachments
Product: Fedora
Classification: Fedora
Component: beagle (Show other bugs)
All Linux
low Severity medium
: ---
: ---
Assigned To: David Nielsen
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2007-09-20 06:10 EDT by Adam Huffman
Modified: 2008-05-02 23:29 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-05-02 23:29:00 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
gdb backtrace (5.07 KB, text/plain)
2007-09-20 06:10 EDT, Adam Huffman
no flags Details

  None (edit)
Description Adam Huffman 2007-09-20 06:10:06 EDT
Description of problem:
After applying a big batch of updates to an FC6 machine, the user reported to me
that Evolution hung when she tried to add an attachment to a mail.

I installed the debuginfo package, ran gdb and saw that it was waiting on a
Beagle-related process.  If I killed beagled, Evolution became responsive again
and I was able to send the message, with the attachment.

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

How reproducible:
Every time

Steps to Reproduce:
1. Compose a new mail in Evolution
2. Add an attachment
3 [details].
Actual results:
Evolution hangs, waiting for the Beagle process to complete

Expected results:
Should be able to add attachment normally

Additional info:
Comment 1 Adam Huffman 2007-09-20 06:10:06 EDT
Created attachment 200641 [details]
gdb backtrace
Comment 2 Bug Zapper 2008-04-04 03:35:13 EDT
Fedora apologizes that these issues have not been resolved yet. We're
sorry it's taken so long for your bug to be properly triaged and acted
on. We appreciate the time you took to report this issue and want to
make sure no important bugs slip through the cracks.

If you're currently running a version of Fedora Core between 1 and 6,
please note that Fedora no longer maintains these releases. We strongly
encourage you to upgrade to a current Fedora release. In order to
refocus our efforts as a project we are flagging all of the open bugs
for releases which are no longer maintained and closing them.

If this bug is still open against Fedora Core 1 through 6, thirty days
from now, it will be closed 'WONTFIX'. If you can reporduce this bug in
the latest Fedora version, please change to the respective version. If
you are unable to do this, please add a comment to this bug requesting
the change.

Thanks for your help, and we apologize again that we haven't handled
these issues to this point.

The process we are following is outlined here:

We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.

And if you'd like to join the bug triage team to help make things
better, check out http://fedoraproject.org/wiki/BugZappers
Comment 3 Adam Huffman 2008-04-23 12:03:21 EDT
Not using Beagle anymore so I can't reproduce this on the relevant systems,
which have all been upgraded.

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