Red Hat Bugzilla – Bug 227442
gnome-cd crashes when run
Last modified: 2008-08-02 19:40:34 EDT
Description of problem:
when: gnome-cd --unique --play --device /dev/hdc
is run it produces a segmentation fault
Note: may be related to bug: 187602
If gnome-cd /dv/hdc is run it reports it cannot find the CD but does not
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.gnome-cd --unique --play --device /dev/hdc is run
plays the CD
Created attachment 147411 [details]
log of strace run on execution line above
Could you please gather a backtrace of the crash, following the instructions at:
A stack trace of the execution was included as an attachment in this bug report.
(In reply to comment #3)
> A stack trace of the execution was included as an attachment in this bug report.
No, it's not a stack trace (or backtrace), it's the output of strace. See the
page mentioned above, you need to use gdb to capture a stack trace.
Created attachment 154656 [details]
gdb stack trace of the failed run of gnome-cd
We are no faced with an argument I have with Rahul. I was convinced that
bugzillas were essential to giving the developers feedback. But this bugzilla
has maintained my perfect record of never getting any results to help me
understand the problem.
I supplied the gdb stacktrace and received bubkas (really nothing) in return. Do
bugzillas actually lead to progress on problems since I have never had that
(In reply to comment #6)
> I supplied the gdb stacktrace and received bubkas (really nothing) in return. Do
> bugzillas actually lead to progress on problems since I have never had that
Certainly not going to be fixed if you keep the bug in NEEDINFO once you've
provided the information.
The backtrace you provided isn't full, and you don't have the debuginfo packages
for the package installed (so no filenames, or line numbers).
Please install the -debuginfo package necessary until you see all file names and
line numbers for all the calls on the line (how to install the debuginfo
packages is explained in the StackTraces page mentioned above), and make sure
you include the _full_ gdb output.
I haven't a clue what you are talking about. I followed your instructions on
producing the backtrace. The fact that yo need to changes the status of the
bugzilla from NEEDINFO was never exp[lained to me. I have not the slightest idea
what you are claiming is wrong with the backtrace I sent you since I followed
the instructions you pointed to exactly.
This is why so many users are turned off on Bugzilla. As far as I can see it is
next to impossible to use properly and again I have never got a sucessful
resolution of any bugzilla problem using this tool.
Again I did follow the instructions and sent you all the output I produced. I am
at a loss to see what you are complaining about.
(In reply to comment #8)
> I haven't a clue what you are talking about. I followed your instructions on
> producing the backtrace. The fact that yo need to changes the status of the
> bugzilla from NEEDINFO was never exp[lained to me.
That's how all bugzillas work.
> I have not the slightest idea
> what you are claiming is wrong with the backtrace I sent you since I followed
> the instructions you pointed to exactly.
You didn't install the debuginfo packages for the libraries present in the
backtrace, or they don't match the versions of the packages you have installed.
These are the explanations on what a debuginfo package is, and how to install it:
Also make sure that the version of the debuginfo package installed matches
exactly the version of the packages installed on your system.
If you paste the full output of gdb (from the moment you start it), it'll show
whether it could load the debugging symbols or not.
> This is why so many users are turned off on Bugzilla. As far as I can see it is
> next to impossible to use properly and again I have never got a sucessful
> resolution of any bugzilla problem using this tool.
That's funny, I got plenty. The bug reporting tool might not be the easiest to
use, but a good backtrace will lead to the bug being fixed. I can't do it otherwise.
Fedora apologizes that these issues have not been resolved yet. We're
sorry it's taken so long for your bug to be properly triaged and acted
on. We appreciate the time you took to report this issue and want to
make sure no important bugs slip through the cracks.
If you're currently running a version of Fedora Core between 1 and 6,
please note that Fedora no longer maintains these releases. We strongly
encourage you to upgrade to a current Fedora release. In order to
refocus our efforts as a project we are flagging all of the open bugs
for releases which are no longer maintained and closing them.
If this bug is still open against Fedora Core 1 through 6, thirty days
from now, it will be closed 'WONTFIX'. If you can reporduce this bug in
the latest Fedora version, please change to the respective version. If
you are unable to do this, please add a comment to this bug requesting
Thanks for your help, and we apologize again that we haven't handled
these issues to this point.
The process we are following is outlined here:
We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.
And if you'd like to join the bug triage team to help make things
better, check out http://fedoraproject.org/wiki/BugZappers
This bug is open for a Fedora version that is no longer maintained and
will not be fixed by Fedora. Therefore we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen thus bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.