[apport] brasero crashed with SIGSEGV in g_str_hash()

Bug #105425 reported by Marco Raccagni on 2007-04-11
Affects Status Importance Assigned to Milestone
brasero (Ubuntu)
Mario Đanić

Bug Description

Binary package hint: brasero

brasero crashes during setting the drive

ProblemType: Crash
Architecture: i386
Date: Wed Apr 11 09:02:45 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/bin/brasero
Package: brasero 0.5.2-0ubuntu1
PackageArchitecture: i386
ProcCmdline: brasero
ProcCwd: /home/marco
Signal: 11
SourcePackage: brasero
 #0 0xb725e3c7 in g_str_hash () from /usr/lib/libglib-2.0.so.0
 #1 0xb7236537 in g_hash_table_lookup () from /usr/lib/libglib-2.0.so.0
 #2 0x08068377 in ?? ()
 #3 0x084e2ce0 in ?? ()
 #4 0x00000000 in ?? ()
 g_str_hash () from /usr/lib/libglib-2.0.so.0
 g_hash_table_lookup () from /usr/lib/libglib-2.0.so.0
 ?? ()
 ?? ()
 ?? ()
Uname: Linux ubuntu704 2.6.20-14-generic #2 SMP Mon Apr 2 20:37:49 UTC 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin plugdev scanner video

Marco Raccagni (markk1981) wrote :
Lionel Le Folgoc (mrpouit) wrote :

Thanks for your bug report.

Changed in brasero:
assignee: nobody → mrpouit
status: Unconfirmed → Needs Info

StacktraceTop:IA__g_hash_table_lookup (hash_table=0x84e2ce0, key=0x0) at ghash.c:231
brasero_recorder_selection_button_cb (button=0x8331a60, selection=0x84bd810) at recorder-selection.c:861
IA__g_cclosure_marshal_VOID__VOID (closure=0x84f67b0, return_value=0x0, n_param_values=1, param_values=0xbfe827ec, invocation_hint=0xbfe826fc,
IA__g_closure_invoke (closure=0x84f67b0, return_value=0x0, n_param_values=1, param_values=0xbfe827ec, invocation_hint=0xbfe826fc) at gclosure.c:490

Lionel Le Folgoc (mrpouit) wrote :


I would like to forward the bug to upstream, but as I wasn't able to reproduce the crash, I have a few questions:
- does this crash always happen?
- when exactly (when setting the drive just before burning?)
- some infos on your drive.


Marco Raccagni (markk1981) wrote :

-yes, this always happens
-when I try to burn an ISO image, I click on "Config" (I don't know if in the English version is so called...) and Brasero closed
-the drive is an LG model HL-DT-ST DVDRAM GSA-H10N


Changed in brasero:
status: Unknown → Unconfirmed
Changed in brasero:
status: Needs Info → Unconfirmed
Changed in brasero:
assignee: mrpouit → nobody
status: Unconfirmed → Confirmed
Mario Đanić (mario-danic) wrote :

Would you please be so kind to try reproducing bug with Brasero 0.5.90 that landed in Gutsy?

Changed in brasero:
assignee: nobody → mario-danic
Marco Raccagni (markk1981) wrote :

Yes, there is the same problem...

Changed in brasero:
status: New → Incomplete
MarkusBernhard (salvia44) wrote :

same problem here. Gutsy Tribe 3, Brasero 0.6.0. When i start to burn an ISO Image, the drive is not detected and when i start to burne i get this crash report.

Changed in brasero:
status: Incomplete → Invalid
Luis Medinas (lmedinas) wrote :

Brasero 0.6.1 is the release on Gutsy can you try to reproduce it ? I'm almost sure this bug is fixed somewhere.

Launchpad Janitor (janitor) wrote :

This bug was fixed in the package brasero - 0.7.0-0ubuntu1

brasero (0.7.0-0ubuntu1) hardy; urgency=low

  * New Upstream version.
  * Update standarts to 3.7.3
  * debian/patches:
    - drop 004_fix-windows-size.patch: Fixed Upstream.
    - drop 005-fix-tooltips-gtk-2.11.6.patch: Fixed Upstream.
    - drop 001_use-sys-inotify.h.patch: Unneeded patch.
  * Modified 006-fix-libdvdcss.patch: Accommodating new release
  * Bugs fixed in the new release:
    - LP: #159937: time / size mapping is incorrect for Audio CD
    - LP: #157478: Brasero reports incorrect medium size & status
    - LP: #105425: [apport] brasero crashed with SIGSEGV in g_str_hash()
    - LP: #120322: Add functionality to make multiple copies of a disk
    - LP: #153523: Brasero doesn't load image after right click (nautilus) -> Open with Brasero
    - LP: #159607: "Increase compatibility with Windows systems" doesn't work

 -- Luis Medinas <email address hidden> Mon, 26 Dec 2007 20:39:42 +0000

Changed in brasero:
status: Confirmed → Fix Released
Changed in brasero:
importance: Unknown → Critical
status: Invalid → Expired
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.