Bug 993 - Brasero stops when selecting image to burn
Summary: Brasero stops when selecting image to burn
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-26 08:58 CEST by Stephen Pettin
Modified: 2011-10-11 06:49 CEST (History)
4 users (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments
Brasero Debug Info (4.45 KB, text/plain)
2011-04-26 21:10 CEST, Stephen Pettin
Details
(gdb) brasero and (gdb) run brasero (6.17 KB, text/plain)
2011-06-02 05:22 CEST, Palm Pre
Details

Description Stephen Pettin 2011-04-26 08:58:05 CEST
When running Brasero it opens but once I select an ISO image to burn, it stops and crashes. I noticed this running from the menu and when I ran it from a terminal, I got these messages:

$ GLib-GIO-Message: Using the 'memory' GSettings backend.  Your settings will not be saved or shared with other applications.



** (brasero:12828): WARNING **: ERROR loading background pix : Failed to open file '/usr/share/brasero/logo.png': No such file or directory





(brasero:12828): GLib-CRITICAL **: g_variant_builder_end: assertion `is_valid_builder (builder)' failed



(brasero:12828): GLib-CRITICAL **: g_variant_get_type: assertion `value != NULL' failed



(brasero:12828): GLib-CRITICAL **: g_variant_type_is_array: assertion `g_variant_type_check (type)' failed



(brasero:12828): GLib-CRITICAL **: g_variant_get_type_string: assertion `value != NULL' failed



GLib-ERROR **: g_variant_new: expected array GVariantBuilder but the built value has type `(null)'


aborting...



I haven't tried it with any other files to burn.

Thnx.
Comment 1 D Morgan 2011-04-26 09:02:09 CEST
can you please run  brasero inside gdb ? ( this will help to provide a good backtrace )

CC: (none) => dmorganec

Comment 2 Stephen Pettin 2011-04-26 09:39:16 CEST
When I run it inside gdb, I get this:

This GDB was configured as "x86_64-mageia-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /usr/bin/brasero...(no debugging symbols found)...done.
Missing debug package(s), you should install: brasero-debug-2.32.1-2.mga1.x86_64
(gdb)


When I tried to install brasero-debug & brasero-debug-2.32.1-2.mga1.x86_64, I got no package found message.

Thnx.
Comment 3 Frank Griffin 2011-04-26 12:39:21 CEST
You need to enable the debug repositories in MCC Manage Software.

CC: (none) => ftg

Comment 4 Stephen Pettin 2011-04-26 21:10:55 CEST
Created attachment 294 [details]
Brasero Debug Info
Comment 5 Stephen Pettin 2011-04-26 21:14:36 CEST
Comment on attachment 294 [details]
Brasero Debug Info

I'm not sure how the gdb command works. It seems I need to add more debug files before it fully works. Is this the case? I've listed part of the debug info in an attachment.
Comment 6 Ahmad Samir 2011-04-26 23:46:47 CEST
For gdb to work it needs all the -debug packages it listed (http://wiki.mandriva.com/en/Development/Howto/Software_Crash).
Comment 7 Palm Pre 2011-06-02 05:19:57 CEST
I have something very simular: pressing Burn botton just stops Brasero. 

Debugging with gdb is in attachement

CC: (none) => palm_pre_stl

Comment 8 Palm Pre 2011-06-02 05:22:03 CEST
Created attachment 501 [details]
(gdb) brasero and (gdb) run brasero
Comment 9 Marja Van Waes 2011-10-10 20:39:22 CEST
@ Stephen
@ Palm

Is this still an issue in current cauldron?

Keywords: (none) => NEEDINFO
CC: (none) => marja11

Comment 10 Palm Pre 2011-10-11 05:16:48 CEST
I'm using Mageia1. 

There is no problem here like it used to be.
Comment 11 Marja Van Waes 2011-10-11 06:49:05 CEST
(In reply to comment #10)
> I'm using Mageia1. 
> 
> There is no problem here like it used to be.

Well, if the fix found its way to Mageia 1, it found its way to cauldron, too, and probably even earlier

@ Stephen
Feel free to reopen if you don't think this bug is fixed

Keywords: NEEDINFO => (none)
Status: NEW => RESOLVED
Resolution: (none) => FIXED


Note You need to log in before you can comment on or make changes to this bug.