I have two programs which cause a segfault on exit. The first is Aisleriot only if you win the game and select quit for exit. https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=221046 Upstream thought that the problem is actually caused by the guile package.
The most recent problem is with system-config-lvm. If you exit the program I end up getting bug buddy collecting information for a bug report. https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=221739
Anyway, another question is for s-c-lvm, there is no debuginfo package when I tried to install the package for debugging purposes. Is there a package for this program?
Jim
On Sat, 06 Jan 2007 22:40:51 -0500, Jim Cornette wrote:
I have two programs which cause a segfault on exit. The first is Aisleriot only if you win the game and select quit for exit. https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=221046 Upstream thought that the problem is actually caused by the guile package.
The most recent problem is with system-config-lvm. If you exit the program I end up getting bug buddy collecting information for a bug report. https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=221739
Anyway, another question is for s-c-lvm, there is no debuginfo package when I tried to install the package for debugging purposes. Is there a package for this program?
I'm seeing this with gnucash, which triggers bug-buddy which segfaults when it too exits.
I'm current up-to-date with fedora development. Rolling back gnucash to 2.0.1 doesn't change the segfaults.
-Paul
Paul Dickson wrote:
On Sat, 06 Jan 2007 22:40:51 -0500, Jim Cornette wrote:
I have two programs which cause a segfault on exit. The first is Aisleriot only if you win the game and select quit for exit. https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=221046 Upstream thought that the problem is actually caused by the guile package.
The most recent problem is with system-config-lvm. If you exit the program I end up getting bug buddy collecting information for a bug report. https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=221739
Anyway, another question is for s-c-lvm, there is no debuginfo package when I tried to install the package for debugging purposes. Is there a package for this program?
I'm seeing this with gnucash, which triggers bug-buddy which segfaults when it too exits.
I'm current up-to-date with fedora development. Rolling back gnucash to 2.0.1 doesn't change the segfaults.
-Paul
Thanks for the info. Bug buddy exiting also might be a big problem if it also exits without gathering information for the bug report. Bug Buddy woks fine and gathers information for the two failures that I'm getting. I'll try gnucash later to see if it crashes on exit for me and if bug buddy can grab any information without crashing.
Jim
On Sat, Jan 06, 2007 at 10:40:51PM -0500, Jim Cornette wrote:
The most recent problem is with system-config-lvm. If you exit the program I end up getting bug buddy collecting information for a bug report. https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=221739
That one happens to be a duplicate of https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=221539 but you definitely got much more interesting traces from bug-buddy. I will leave to Jim Parsons which of these two he wants to track.
Anyway, another question is for s-c-lvm, there is no debuginfo package when I tried to install the package for debugging purposes. Is there a package for this program?
s-c-lvm is really a pile of Python scripts so this package is its own source :-) and there is no other symbolic information which debuggers could use. All the info you need and can get you already installed.
Michal
On 1/7/07, Michal Jaegermann michal@harddata.com wrote:
On Sat, Jan 06, 2007 at 10:40:51PM -0500, Jim Cornette wrote:
The most recent problem is with system-config-lvm. If you exit the program I end up getting bug buddy collecting information for a bug report. https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=221739
That one happens to be a duplicate of https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=221539 but you definitely got much more interesting traces from bug-buddy. I will leave to Jim Parsons which of these two he wants to track.
Anyway, another question is for s-c-lvm, there is no debuginfo package when I tried to install the package for debugging purposes. Is there a package for this program?
s-c-lvm is really a pile of Python scripts so this package is its own source :-) and there is no other symbolic information which debuggers could use. All the info you need and can get you already installed.
Michal
I seem to have 'worked around' some similar 'bug buddy reports' by reverting ORBit2 and ORBit2-devel to 2.14.3-4.fc7.
Does that work?
tom
Tom London wrote:
On 1/7/07, Michal Jaegermann michal@harddata.com wrote:
On Sat, Jan 06, 2007 at 10:40:51PM -0500, Jim Cornette wrote:
I seem to have 'worked around' some similar 'bug buddy reports' by reverting ORBit2 and ORBit2-devel to 2.14.3-4.fc7.
Does that work?
If you upgraded ORBit2 up to the latest version, do the crashes start up again? Did you make a report against ORBit2?
All packages are current as to what is available in rawhide.
Jim
tom
On 1/7/07, Jim Cornette fct-cornette@insight.rr.com wrote:
Tom London wrote:
On 1/7/07, Michal Jaegermann michal@harddata.com wrote:
On Sat, Jan 06, 2007 at 10:40:51PM -0500, Jim Cornette wrote:
I seem to have 'worked around' some similar 'bug buddy reports' by reverting ORBit2 and ORBit2-devel to 2.14.3-4.fc7.
Does that work?
If you upgraded ORBit2 up to the latest version, do the crashes start up again? Did you make a report against ORBit2?
All packages are current as to what is available in rawhide.
Jim
I filed several reports upstream.
At least one issue (with at-spi) has a patch listed at bugzilla.gnome.org, so I figured a downstream fix was in the works.
Yes, if I upgrade to latest ORBit2 packages, I start seeing failures again (I tried this morning and got a failure with at-spi). [Original BZ reported here: http://bugzilla.gnome.org/show_bug.cgi?id=390362 ]. Reverting to older ORBit2 packages 'cures'.
BZ'd locally here: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=221778
tom Tom London
Tom London wrote:
On 1/7/07, Jim Cornette fct-cornette@insight.rr.com wrote:
Tom London wrote:
On 1/7/07, Michal Jaegermann michal@harddata.com wrote:
On Sat, Jan 06, 2007 at 10:40:51PM -0500, Jim Cornette wrote:
I seem to have 'worked around' some similar 'bug buddy reports' by reverting ORBit2 and ORBit2-devel to 2.14.3-4.fc7.
Does that work?
If you upgraded ORBit2 up to the latest version, do the crashes start up again? Did you make a report against ORBit2?
I filed several reports upstream.
At least one issue (with at-spi) has a patch listed at bugzilla.gnome.org, so I figured a downstream fix was in the works.
Yes, if I upgrade to latest ORBit2 packages, I start seeing failures again (I tried this morning and got a failure with at-spi). [Original BZ reported here: http://bugzilla.gnome.org/show_bug.cgi?id=390362 ]. Reverting to older ORBit2 packages 'cures'.
BZ'd locally here: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=221778
tom Tom London
Thanks for the leads. I was wondering if the other reports filed should reference depending upon ORBit2 and this bug number if downgrading ORBits2 stops the crashing?
Jim
On 1/7/07, Jim Cornette fct-cornette@insight.rr.com wrote:
Thanks for the leads. I was wondering if the other reports filed should reference depending upon ORBit2 and this bug number if downgrading ORBits2 stops the crashing?
Jim
I would think so.... couldn't hurt.
I'm not sure there is actually a problem with ORBit2 or if the API changed a bit between versions (requiring changes to calling apps) or if ...
The 'marker' for me was that ORBit2 routines were always a few calls down from the the top of the bug buddy stack trace.
tom
On Sun, Jan 07, 2007 at 09:27:57PM -0500, Jim Cornette wrote:
Thanks for the leads. I was wondering if the other reports filed should reference depending upon ORBit2 and this bug number if downgrading ORBits2 stops the crashing?
I bumped in another application with a consistent "crash-on-exit" behaviour. Try to adjust keyboard properties from a GUI in "Preferences" menu entry and see for yourself.
I do not know at this moment of backing out ORBit2 version helps here. I guess that I will wait for updates before filing any new bug reports.
Michal
Michal Jaegermann wrote:
On Sun, Jan 07, 2007 at 09:27:57PM -0500, Jim Cornette wrote:
Thanks for the leads. I was wondering if the other reports filed should reference depending upon ORBit2 and this bug number if downgrading ORBits2 stops the crashing?
I bumped in another application with a consistent "crash-on-exit" behaviour. Try to adjust keyboard properties from a GUI in "Preferences" menu entry and see for yourself.
I do not know at this moment of backing out ORBit2 version helps here. I guess that I will wait for updates before filing any new bug reports.
Michal
It sure enough does crash!
http://bugzilla.gnome.org/show_bug.cgi?id=394443
With bug buddy, filing the report is too easy to post.
I'll refrain from going too far to the extreme, but this should at least get orbit2 some tlc from reassigning the reports to the ORBit2 component.
Jim
On 1/8/07, Jim Cornette fct-cornette@insight.rr.com wrote:
It sure enough does crash!
http://bugzilla.gnome.org/show_bug.cgi?id=394443
With bug buddy, filing the report is too easy to post.
I'll refrain from going too far to the extreme, but this should at least get orbit2 some tlc from reassigning the reports to the ORBit2 component.
Jim
This does not crash for me running ORBit2-2.14.3-4.fc7.....
tom
On Mon, Jan 08, 2007 at 05:50:23PM -0500, Jim Cornette wrote:
It sure enough does crash!
http://bugzilla.gnome.org/show_bug.cgi?id=394443
With bug buddy, filing the report is too easy to post.
Apparently "too easy" is right. :-) It is already closed as a duplicate of http://bugzilla.gnome.org/show_bug.cgi?id=364839 and that one list forty four, or something in that range, duplicates. For more fun 364839 is closed as resolved.
Michal
Michal Jaegermann wrote:
On Mon, Jan 08, 2007 at 05:50:23PM -0500, Jim Cornette wrote:
It sure enough does crash!
http://bugzilla.gnome.org/show_bug.cgi?id=394443
With bug buddy, filing the report is too easy to post.
Apparently "too easy" is right. :-) It is already closed as a duplicate of http://bugzilla.gnome.org/show_bug.cgi?id=364839 and that one list forty four, or something in that range, duplicates. For more fun 364839 is closed as resolved.
Michal
But what was fixed? One other thing puzzles me as to why they show all of the endless scrolling through bug marked as duplicate instead of having a way to tally all of the duplicates within a separate area for duplicates , depends on or similar fields.
Still waiting on ORBit2 to be repaired either upstream or locally.
Jim
Michal Jaegermann wrote:
On Sat, Jan 06, 2007 at 10:40:51PM -0500, Jim Cornette wrote:
The most recent problem is with system-config-lvm. If you exit the program I end up getting bug buddy collecting information for a bug report. https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=221739
That one happens to be a duplicate of https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=221539 but you definitely got much more interesting traces from bug-buddy. I will leave to Jim Parsons which of these two he wants to track.
I'll check out the reference for comparison.
Anyway, another question is for s-c-lvm, there is no debuginfo package when I tried to install the package for debugging purposes. Is there a package for this program?
s-c-lvm is really a pile of Python scripts so this package is its own source :-) and there is no other symbolic information which debuggers could use. All the info you need and can get you already installed.
Michal
Alright, I'll just make due with the information that I was able to collect. If there are only scripts, it should be up to the developer to decypher.
Related to the problem with gnucash, I tried out exiting the program and bug buddy mailed this bug report upstream. At least this problem is easier to resolve than having to win a game in order to reproduce the bug. Here is the link to the new bug report for gnucash..
http://bugzilla.gnome.org/show_bug.cgi?id=394024
Jim