After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 566438 - Brasero 0.8.0 & 0.8.4 crash on Banshee Drag&Drop Audio files
Brasero 0.8.0 & 0.8.4 crash on Banshee Drag&Drop Audio files
Status: RESOLVED DUPLICATE of bug 588323
Product: brasero
Classification: Applications
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Brasero maintainer(s)
Brasero maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2009-01-03 19:36 UTC by Mike
Modified: 2009-11-04 08:23 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24

Attachments
GDb (5.89 KB, application/octet-stream)
2009-01-07 16:44 UTC, Mike 		Details
valgrind (82.31 KB, text/x-log)
2009-01-07 16:44 UTC, Mike 		Details

Description Mike 2009-01-03 19:36:08 UTC 
Steps to reproduce:
1.Runing Banshee 1.4.1 and when I try to drag&drop files to Brasero audio project i get application crash
2.In teminal brasero on crash produce : Segmentation fault
3.


Stack trace:


Other information:
Comment 1 palfrey 2009-01-03 20:29:05 UTC 
Thanks for taking the time to report this bug.
Without a stack trace from the crash it's very hard to determine what caused it.
Can you get us a stack trace? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Comment 2 Mike 2009-01-07 16:44:05 UTC 
Created attachment 125943 [details]
GDb
Comment 3 Mike 2009-01-07 16:44:53 UTC 
Created attachment 125944 [details]
valgrind
Comment 4 palfrey 2009-01-07 16:52:51 UTC 
We're going to need more output of gdb than that (see http://live.gnome.org/GettingTraces/Details#gdb-not-yet-running for details), and also you'll need to install the debugging symbols for brasero and gtk (see http://live.gnome.org/GettingTraces/DistroSpecificInstructions), as there isn't enough data in that gdb output yet.
Comment 5 Tobias Mueller 2009-06-18 08:58:06 UTC 
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!
Comment 6 Philippe Rouquier 2009-11-04 08:23:52 UTC 
This bug has been fixed. Thanks for reporting.

*** This bug has been marked as a duplicate of bug 588323 ***