There seems to be some hostility to the idea of this being a GNOME or Evolution problem:
Bug 542280 – Refuses to report bugs because gnome 2.16.x is too old View Bug Activity Product: bug-buddy Component: general Version: 2.16.x Status: RESOLVED Resolution: WONTFIX Opened by Mark Hull-Richter (reporter, points: 3) 2008-07-09 23:40 UTC [reply]
On CentOS 5.2 (and 5.1 and 5.0, and Red Hat Enterprise Linux of the same versions, which happen to be the most current ones available), the bug buddy "tool" consistently refuses to report any bugs because it claims that the version of Gnome is too old.
This is unacceptable - Gnome 2.16.x is the /standard/ release with RHEL and CentOS distributions of Linux/Gnome. There are too many issues that can (and do) come up for the tool simply to refuse to report a bug for this reason.
Comment #1 from Cosimo Cecchi (points: 22) 2008-07-14 20:29 UTC [reply]
This is intentional and isn't a bug-buddy issue. Bugzilla only accepts crashers from the two most recent stable releases (e.g. now that 2.22 is the current stable, it rejects everything <= 2.19.99). This is because we can't support every stable branch, as the codebases evolve and backporting fixes would be nearly impossible. If you need a specific fix, please backport it yourself in your distribution (like RHEL does I think) or just use newer releases. I'm closing this as WONTFIX, please file a bug under bugzilla.gnome.org component if you need more explanations, thanks.
Comment #2 from Andre Klapper (points: 28) 2008-07-14 20:46 UTC [reply]
It's not our problem that CentOS and RHEL ship ancient software. Ask them to patch bug-buddy to report against their distribution bug tracker instead of GNOME Bugzilla. We are definitely not interested in bugs that probably have been fixed for ages and 95% of those ancient reports are dups anyway. If you volunteer to triage all that useless incoming stuff, okay. We definitely don't want to, we got better stuff to spend our time on than 2.16 that in fact nobody works on, except for two LTS distros.
LTS? Long Term Support?
So much for that effort.
Any chance of CentOS (or RHEL) patching bug-buddy as suggested in #2, above? Just curious....
Thanks, all.
mhr
MHR wrote:
There seems to be some hostility to the idea of this being a GNOME or Evolution problem:
Bug 542280 – Refuses to report bugs because gnome 2.16.x is too old View Bug Activity Product: bug-buddy Component: general Version: 2.16.x Status: RESOLVED Resolution: WONTFIX Opened by Mark Hull-Richter (reporter, points: 3) 2008-07-09 23:40 UTC [reply]
On CentOS 5.2 (and 5.1 and 5.0, and Red Hat Enterprise Linux of the same versions, which happen to be the most current ones available), the bug buddy "tool" consistently refuses to report any bugs because it claims that the version of Gnome is too old.
This is unacceptable - Gnome 2.16.x is the /standard/ release with RHEL and CentOS distributions of Linux/Gnome. There are too many issues that can (and do) come up for the tool simply to refuse to report a bug for this reason.
Comment #1 from Cosimo Cecchi (points: 22) 2008-07-14 20:29 UTC [reply]
This is intentional and isn't a bug-buddy issue. Bugzilla only accepts crashers from the two most recent stable releases (e.g. now that 2.22 is the current stable, it rejects everything <= 2.19.99). This is because we can't support every stable branch, as the codebases evolve and backporting fixes would be nearly impossible. If you need a specific fix, please backport it yourself in your distribution (like RHEL does I think) or just use newer releases. I'm closing this as WONTFIX, please file a bug under bugzilla.gnome.org component if you need more explanations, thanks.
Comment #2 from Andre Klapper (points: 28) 2008-07-14 20:46 UTC [reply]
It's not our problem that CentOS and RHEL ship ancient software. Ask them to patch bug-buddy to report against their distribution bug tracker instead of GNOME Bugzilla. We are definitely not interested in bugs that probably have been fixed for ages and 95% of those ancient reports are dups anyway. If you volunteer to triage all that useless incoming stuff, okay. We definitely don't want to, we got better stuff to spend our time on than 2.16 that in fact nobody works on, except for two LTS distros.
LTS? Long Term Support?
So much for that effort.
Any chance of CentOS (or RHEL) patching bug-buddy as suggested in #2, above? Just curious....
Well ... we will do whatever upstream does.
I can see why the GNOME project could care less though.
However, the fact is that bug buddy is NOT required to make bugzilla entries for RHEL. If you have a bug, file a bug against the component that is the problem. The fact that bug buddy does not file it directly to gnome is really irrelevant as they are no longer providing any support for 2.16.x.
So, when you have a problem (ignoring bug buddy, which is to gnome and not to RH), then just file the bug against the thing that is broken.
On Mon, Jul 14, 2008 at 7:20 PM, Johnny Hughes johnny@centos.org wrote:
However, the fact is that bug buddy is NOT required to make bugzilla entries for RHEL. If you have a bug, file a bug against the component that is the problem. The fact that bug buddy does not file it directly to gnome is really irrelevant as they are no longer providing any support for 2.16.x.
So, when you have a problem (ignoring bug buddy, which is to gnome and not to RH), then just file the bug against the thing that is broken.
The place where I see this most frequently is when exiting Evolution. I use Evo strictly for email, and it is almost always the Calendar that crashes (why? beats me!). So I /can/ go and file the bug against Evolution (which I will do next time it comes up).
However, isn't Evolution just part of the GNOME distro?
(FTR, I can't remember if this was happening when I was running FC8, so - does anyone else know if this might have been fixed already?)
Thanks.
mhr
On Mon, Jul 14, 2008 at 9:20 PM, Johnny Hughes johnny@centos.org wrote: <snip>
On CentOS 5.2 (and 5.1 and 5.0, and Red Hat Enterprise Linux of the same versions, which happen to be the most current ones available), the bug buddy "tool" consistently refuses to report any bugs because it claims that the version of Gnome is too old.
I've run into is, multiple times, when the Evolution Calendar (which I never use) crashed, when I closed Evolution.
<snip>
Well ... we will do whatever upstream does.
I can see why the GNOME project could care less though.
However, the fact is that bug buddy is NOT required to make bugzilla entries for RHEL. If you have a bug, file a bug against the component that is the problem. The fact that bug buddy does not file it directly to gnome is really irrelevant as they are no longer providing any support for 2.16.x.
So, when you have a problem (ignoring bug buddy, which is to gnome and not to RH), then just file the bug against the thing that is broken.
The next time Evolution Calendar crashes on me, I will write it up in CentOS Bugzilla.
Lanny Marcus wrote:
On Mon, Jul 14, 2008 at 9:20 PM, Johnny Hughes johnny@centos.org wrote:
<snip> >> On CentOS 5.2 (and 5.1 and 5.0, and Red Hat Enterprise Linux of the >> same versions, which happen to be the most current ones available), >> the bug buddy "tool" consistently refuses to report any bugs because >> it claims that the version of Gnome is too old.
I've run into is, multiple times, when the Evolution Calendar (which I never use) crashed, when I closed Evolution.
<snip> > Well ... we will do whatever upstream does. > > I can see why the GNOME project could care less though. > > However, the fact is that bug buddy is NOT required to make bugzilla entries > for RHEL. If you have a bug, file a bug against the component that is the > problem. The fact that bug buddy does not file it directly to gnome is > really irrelevant as they are no longer providing any support for 2.16.x. > > So, when you have a problem (ignoring bug buddy, which is to gnome and not > to RH), then just file the bug against the thing that is broken. > The next time Evolution Calendar crashes on me, I will write it up in CentOS Bugzilla.
I am currently using thunderbird for my e-mail ... but I have setup a test evolution instance and it is not failing here when I exit.
But there is not a whole lot of mail there, so that might be part of it.
Lots of details will also be good if they are provided by the crash.
On Tue, Jul 15, 2008 at 10:44 AM, Johnny Hughes johnny@centos.org wrote:
I am currently using thunderbird for my e-mail ... but I have setup a test evolution instance and it is not failing here when I exit.
But there is not a whole lot of mail there, so that might be part of it.
Could be that or time up - I rarely log out, and I have evo up all the time. I exit all my windows before a log out, and the longer I've been up, the more likely it seems that a crash will occur, although that might not be directly related. I do have a fair amount of email there, too....
Lots of details will also be good if they are provided by the crash.
Yeah, if only I could get them - any idea where Evo stashes its data when it crashes _and_ if it saves it even after a bug-buddy attempt? When I was having problems with SeaMonkey crashes, if the report got sent, the data disappeared.... Of course, I can just tell bug-buddy to abort when it asks what I was doing, but I still need to know where the data lives.
Thanks.
mhr
On Tue, 2008-07-15 at 10:57 -0700, MHR wrote:
On Tue, Jul 15, 2008 at 10:44 AM, Johnny Hughes johnny@centos.org wrote:
I am currently using thunderbird for my e-mail ... but I have setup a test evolution instance and it is not failing here when I exit.
But there is not a whole lot of mail there, so that might be part of it.
Could be that or time up - I rarely log out, and I have evo up all the time. I exit all my windows before a log out, and the longer I've been up, the more likely it seems that a crash will occur, although that might not be directly related. I do have a fair amount of email there, too....
JIC it useful: I've been using evo from 4.x up to now 5.2. Never had this problem. But I did have one that might be involved. I used to get an evo crap out that spawned a bug buddy instance. Eventually saw enough detail to identify it as being related to spell checking. Something to do with dictionaries. Over time, I added/upgraded dictionaries and haven't seen the problem for a long time now.
It never crashed calendar on me - I also do not* use it.
I did have the advantage that the bug buddy did aprove of the gnome version at the time, so I was able to see the issues when I filled out the submission form. You don't have that advantage. The only thing I can think of might be to see if there is anything in the /var/log/gdm/* logs, although it would surprise me if there was something.
<snip>
mhr
<snip sig stuff>
On Tue, Jul 15, 2008 at 12:44 PM, Johnny Hughes johnny@centos.org wrote: <snip>.
Lanny: I've run into is, multiple times, when the Evolution Calendar (which I never use) crashed, when I closed Evolution.
<snip> The next time Evolution Calendar crashes on me, I will write it up in CentOS Bugzilla.
I am currently using thunderbird for my e-mail ... but I have setup a test evolution instance and it is not failing here when I exit.
But there is not a whole lot of mail there, so that might be part of it.
Lots of details will also be good if they are provided by the crash.
Johnny: It is an intermittent thing. Strangely, it seemed to happen more frequently, after I updated from CentOS 5.1 to 5.2, than it does now. Possibly one of the 15-20 updates I've gotten since then has decreased the frequency of the crashes. The next time Evolution Calendar crashes, I will provide as much information as I can. I never use Evolution Calendar, but I do use Evolution for email and when I shut Evolution down, then, sometimes, Evolution Calendar crashes. Lanny
-
Johnny Hughes -
Lanny Marcus -
MHR -
William L. Maltby