Bug 664453
| Summary: | Evolution freezes when displaying my own contact info | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | John Keller <bugs> | ||||||||||
| Component: | evolution | Assignee: | Matthew Barnes <mbarnes> | ||||||||||
| Status: | CLOSED UPSTREAM | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||
| Severity: | medium | Docs Contact: | |||||||||||
| Priority: | low | ||||||||||||
| Version: | 14 | CC: | lucilanga, mbarnes, mcrha | ||||||||||
| Target Milestone: | --- | ||||||||||||
| Target Release: | --- | ||||||||||||
| Hardware: | x86_64 | ||||||||||||
| OS: | Linux | ||||||||||||
| Whiteboard: | |||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||
| Doc Text: | Story Points: | --- | |||||||||||
| Clone Of: | Environment: | ||||||||||||
| Last Closed: | 2011-01-05 14:33:31 UTC | Type: | --- | ||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||
| Documentation: | --- | CRM: | |||||||||||
| Verified Versions: | Category: | --- | |||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||
| Embargoed: | |||||||||||||
| Attachments: |
|
||||||||||||
|
Description
John Keller
2010-12-20 13:46:16 UTC
Thanks for a bug report. What was the image type you assigned to your contact, please? (jpeg, png, ...) The reason why the mouse stops responding is that the double click locks it (and I think it locks it because it thinks you would want to drag&drop, not only double click, but anyway). You can alternatively right click above the contact and choose "Open". Could you get a backtrace of a frozen evolution, please? You can do that by this command: $ gdb --batch --ex "t a a bt" -pid=PID &>evo.txt where PID is a process ID of the running evolution. The evo.txt file will contain the captured backtrace. Please make sure you'll have installed debug info packages for evolution-data-server, evolution and gtkhtml3. Thanks in advance. Hi, Milan. Thanks for the fast reply! Answering your questions in order... The image is just one from the standard Gnome selection, a JEPG image: /usr/share/pixmaps/faces/lightning.jpg I'm not sure that the mouse stops because of a double-click capture. Even a single click gave me the same result (and I confirmed again today). Right clicking gives the same result, but even worse: because the menu appears, but the system no longer recognizes the mouse clicks, I can't click to dismiss the menu. Nor could I use Ctrl-Alt-arrow to go to another workspace, or use Ctrl-Alt-Fx to go to a text console. And since I leave Ctrl-Alt-Backspace disabled, I had to do a hard reset on my computer to reboot... I'll attach the backtrace next. I installed evolution-data-server-debuginfo, evolution-debuginfo, and gtkhtml3-debuginfo - all version 2.32.1-1.fc14, the same as the normal packages. There still seem to be some undefined symbols (if that's the right term, I only know enough to be dangerous), so please let me know if you'd like me to install any other debuginfo packages and do another backtrace. Note that I'm actually going to attach two backtraces: one reight before, and one right after the freeze. The only difference is that I clicked on my own contact between the two. Created attachment 469996 [details]
backtrace with functional Evolution
At the moment of this backtrace, I was viewing the contact list and the contact immediately above mine was selected. Evo was responsive and usable.
Created attachment 469997 [details]
backtrace with frozen Evolution
Right after the previous backtrace, I clicked on my contact info within the contact list. Evo duly froze, I went to another workspace so I could click with my mouse again, and made this backtrace.
(In reply to comment #2) > The image is just one from the standard Gnome selection, a JEPG image: > /usr/share/pixmaps/faces/lightning.jpg Bah, I mean "a JPEG image". But maybe Evo froze because it expected a JEPG image. :-D I've just been able to reproduce the same freeze with another contact, only this time there isn't an image involved. At least, there shouldn't be (I don't use images for any contacts other than my own, and that's only a side effect of my having picked one in the Gnome "About Me" capplet). However, looking at the diff between the "good" and "frozen" backtraces for this contact, there seems to be the same problem as with my own contact info: image functions (for example, one in libgdk_pixbuf) are being called. Strange, considering as I mentioned that this contact doesn't have an associated image... Created attachment 470174 [details]
backtrace with functional Evolution
As before, this is the first of a pair of backtraces. Here, I've filtered the contact list to include only the contact that causes the freeze and two other contacts with the same last name.
Created attachment 470175 [details]
backtrace with frozen Evolution (second set)
As before, this is the second of a pair of backtraces. Here, I've clicked on a contact in a filtered list of three. Just as with my own contact info, clicking on this item immediately causes a freeze (before the list item is even displayed as selected).
Eureka! Well, at least I think so...
Going through addresses for holiday cards, I ran into a few other contacts where selecting them in the contact list would freeze Evolution. And they're disparate - contacts from my wife to friends with essentially full vcards to friends with minimal info. There didn't seem to be a pattern.
Except... I use Pidgin and the Evolution Integration plugin. For every contact I have in Pidgin from a random selection (i.e. I didn't test everyone), selecting their info in the Evo contact list will freeze Evo.
This would explain the crash when selecting my own contact, too: I store my own chat IDs in Evo contact fields, and have a test MSN account besides my main MSN account. The test account refers to my main MSN account and vice-versa (so that I can see my presence in account "A" from account "B", and the other way around).
Neither disabling (via Pidgin) nor removing (the RPM, via yum) the Pidgin Evolution plugin made a difference within Evolution. I'm guessing that some information was written back into the EDS data store that is persistent. That makes sense, since Evo crashed in the earlier tests even when I wasn't running Pidgin.
I'm guessing that Pidgin has written the chat avatar image to the EDS data store, or at least some flag which indicates that there's an image even if one isn't saved. That would make sense, since the two pairs of backtraces I attached both indicate a freeze in getting some graphic info.
Please let me know if there are any tests I could do that would help you zero in on the source, so that we know if it's a bug that needs to be fixed in Evolution ("strict in what you write, flexible in what you read"?) or in Pidgin ("stop writing unexpected values"), or both...
Thanks for the update. I believe it's the same issue as the upstream bug [1]. Please CC yourself there, maybe the developers will ask for a backtrace of evolution with gtk2, glib2 and gdk-pixbuf debug-info packages installed. It'll be great if you could write there your versions of these packages too. Thanks in advance. [1] https://bugzilla.gnome.org/show_bug.cgi?id=473862 |