| Summary: | Incorrect message counts in all my Maildir "folders" | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Gene Alexander <subs> |
| Component: | RPM Packages | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | dmorganec, fundawang, marja11 |
| Version: | 1 | Keywords: | UPSTREAM |
| Target Milestone: | --- | ||
| Hardware: | i586 | ||
| OS: | Linux | ||
| URL: | http://www.eracc.com/other/screen-shots/Evolution_bad_msg_count_001.jpeg | ||
| Whiteboard: | |||
| Source RPM: | evolution-2.32.2-2.mga1.src.rpm | CVE: | |
| Status comment: | |||
| Bug Depends on: | 2721 | ||
| Bug Blocks: | |||
| Attachments: |
CAMEL_DEBUG=all evolution >& evolution_debug_1.log
gdb backtrace from trying to create a folder in evolution |
||
|
Description
Gene Alexander
2011-09-06 19:40:51 CEST
Do you have the link of your upstream bug ? I think they don't want support the old version 2.32, we have the last version in cauldron 3.9x. But we can do nothing for that. :/ https://bugzilla.gnome.org/show_bug.cgi?id=658290 Note the refusal states: "Ermm, no... This report lists several issues. Please file separate reports for each issue, and if possible query first as some issues have been fixed in the meantime for 3.0 already. Currently this report is impossible to handle with all its different issues. Closing as INVALID." Since I was not sure WHAT caused my problem I was reporting everything I saw. Apparently, that was "wrong". :/ I understand the gnome opinion. For next time, to report some backtrace, it's better to attach the logs and not to add them in one command. ;) I will remember that ... I hope. ;) so I close Status:
NEW =>
RESOLVED Why close this? Nothing was resolved! The message counts in my Maildir "folders" still become incorrect during use. The screen capture in the URL attached to the original report shows this. What do you need from me to help you to resolve this? Status:
RESOLVED =>
REOPENED Created attachment 770 [details]
CAMEL_DEBUG=all evolution >& evolution_debug_1.log
Here is a log from running Evolution overnight. It is also attached to another bug report about Evolution crashing. I have no idea if this contains anything you can use, but at least look at it and see if anything suggests to you why Evolution is having a problem with Maildir message counts on /my/ system.
that is an upstream bug... So, this means I am just stuck? Since they reject it and you say it is "upstream" how does this get fixed? You want to know what is really weird? I am running Evolution with gdb and trying to MAKE it crash, and it will not crash. Hmm, maybe I can try to make a new "folder" ... these problems with Maildir "folders" may be related. Created attachment 772 [details]
gdb backtrace from trying to create a folder in evolution
Marja Van Waes
2011-11-25 14:11:25 CET
CC:
(none) =>
marja11
Marja Van Waes
2011-11-25 14:20:36 CET
Depends on:
(none) =>
2721 No maintainer for evolution cc'ing two committers Keywords:
(none) =>
UPSTREAM cc'ing one more committer CC:
(none) =>
jani.valimaa
Jani Välimaa
2012-04-28 10:04:49 CEST
CC:
jani.valimaa =>
(none) This message is a reminder that Mageia 1 is nearing its end of life. In approximately 25 days from now, Mageia will stop maintaining and issuing updates for Mageia 1. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '1'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 1's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 1 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. -- Mageia Bugsquad Mageia 1 changed to end-of-life (EOL) status on ''1st December''. Mageia 1 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Mageia please feel free to click on "Version" change it against that version of Mageia and reopen this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- Mageia Bugsquad Status:
REOPENED =>
RESOLVED |
