Bug 213679 - summary popup crashes mail-notification
Summary: summary popup crashes mail-notification
Status: CLOSED DEFERRED
Alias: None
Product: Fedora
Classification: Fedora
Component: mail-notification
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Thorsten Leemhuis
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-11-02 15:16 UTC by Matthias Clasen
Modified: 2007-11-30 22:11 UTC (History)
1 user (show)

(edit)
Clone Of:
(edit)
Last Closed: 2006-11-10 21:03:29 UTC


Attachments (Terms of Use)

Description Matthias Clasen 2006-11-02 15:16:39 UTC
once I learned to install the evolution plugin, I was able to configure
mail-notification to look at my evolution inbox. Unfortunately, it crashed
immediately, when trying to display a summary popup of the ~500 unread messages 
in that folder. The crash was due to some X error, so I assume it is just trying
to create a humongous window to show all the messages. 

As a rule of thumb, never make popups larger than the screen. And displaying
a summary of 100s of messages is probably not very helpful in the first place.
So maybe restricting the popup to a most screen height and at most the first, 
say, 10 messages might make this tool a lot more useful.

Comment 1 Thorsten Leemhuis 2006-11-04 13:08:14 UTC
reported upstream
https://savannah.nongnu.org/bugs/?18196

Comment 2 Thorsten Leemhuis 2006-11-10 21:03:29 UTC
Answer from upstream deeloper:
---
It's X's job to not crash when displaying a huge window. Anyway, that popup code
is gone in what will become the next version (libnotify is now used).

For now you should simply refrain from monitoring mailboxes which contain that
many unread mails (I see no point in doing so anyway). If you can no longer use
MN because it crashes at startup while trying to display the huge popup, just
remove the offending mailbox from ~/.gnome2/mail-notification/mailboxes.xml
manually.
---

So a fix will be in the next version. Sorry, that solution is far from perfect,
but I don't hae the manpower to fix that on my own.


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