brasero crashed with SIGABRT in __kernel_vsyscall()

Bug #761831 reported by Ruslanm on 2011-04-15
78
This bug affects 14 people
Affects Status Importance Assigned to Milestone
Brasero
Expired
Critical
brasero (Ubuntu)
Medium
Unassigned

Bug Description

Binary package hint: brasero

Description: Ubuntu Natty (development branch)
Release: 11.04

brasero:
  Установлен: 2.32.1-0ubuntu2
  Кандидат: 2.32.1-0ubuntu2
  Таблица версий:
 *** 2.32.1-0ubuntu2 0
        500 http://ru.archive.ubuntu.com/ubuntu/ natty/main i386 Packages
        100 /var/lib/dpkg/status

Everything was simple. I inserted a CD and wanted to write an ISO image. I presses button 'burn', the process begun..
And after some time bug report appeared. CD looks like clear. Hope it is :)

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: brasero 2.32.1-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.38-7.39-generic-pae 2.6.38
Uname: Linux 2.6.38-7-generic-pae i686
Architecture: i386
CheckboxSubmission: 98ab0d5af71f90633937e5fcdc3884bb
CheckboxSystem: b8f3ec504801f13fc208edb5c785b099
Date: Fri Apr 15 18:34:11 2011
ExecutablePath: /usr/bin/brasero
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
ProcCmdline: brasero
ProcEnviron:
 LANGUAGE=ru_RU:en
 PATH=(custom, user)
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
Signal: 6
SourcePackage: brasero
StacktraceTop:
 __kernel_vsyscall ()
 raise () from /lib/i386-linux-gnu/libc.so.6
 abort () from /lib/i386-linux-gnu/libc.so.6
 g_assertion_message () from /lib/i386-linux-gnu/libglib-2.0.so.0
 g_assertion_message_expr () from /lib/i386-linux-gnu/libglib-2.0.so.0
Title: brasero crashed with SIGABRT in __kernel_vsyscall()
UpgradeStatus: Upgraded to natty on 2011-04-02 (12 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Ruslanm (mist-r) wrote :

StacktraceTop:
 __kernel_vsyscall ()
 raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
 abort () at abort.c:92
 g_assertion_message (domain=0x0, file=0x80a5fa6 "brasero-drive-settings.c", line=83, func=0x80a5fc0 "brasero_drive_settings_get_mapping_speed", message=<value optimized out>) at /build/buildd/glib2.0-2.28.5/./glib/gtestutils.c:1358
 g_assertion_message_expr (domain=0x0, file=0x80a5fa6 "brasero-drive-settings.c", line=83, func=0x80a5fc0 "brasero_drive_settings_get_mapping_speed", expr=0x80a5f97 "medium != NULL") at /build/buildd/glib2.0-2.28.5/./glib/gtestutils.c:1369

Changed in brasero (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Ruslanm (mist-r) wrote :

Solution:
 Used "cdrecord -v speed=4 dev=/dev/cdrom file.iso" instead of brasero :))

visibility: private → public
Pedro Villavicencio (pedro) wrote :

Thank you for your bug report. This bug has been reported to the developers of the software. You can track it and make comments at:
 https://bugzilla.gnome.org/show_bug.cgi?id=648301

Changed in brasero (Ubuntu):
status: New → Triaged
Changed in brasero:
importance: Unknown → Critical
status: Unknown → New
Charles H.Scott (chscott) wrote :

The problem happened in brasero and nautilus. While burning iso all's well until the last few seconds.

Brasero quit near end of burning process with an unexpected error.

Bruce R (bm007a0030) wrote :

Also occurred when using Ubuntu 11.10 Oneiric Alpha 3 release.

Pedro Villavicencio (pedro) wrote :

Could you please use the 'affect me too' button at the top of the page instead of commenting if you have the bug with a new release? thanks in advance.

I thought that's what I did, but was then prompted to also offer comment,
whilst in your requested response to #493865, I commented about this
crash report.
  ----- Original Message -----
  From: Pedro Villavicencio
  To: <email address hidden>
  Sent: Tuesday, August 16, 2011 9:21 AM
  Subject: [Bug 761831] Re: brasero crashed with SIGABRT in __kernel_vsyscall()

  Could you please use the 'affect me too' button at the top of the page
  instead of commenting if you have the bug with a new release? thanks in
  advance.

Changed in brasero:
status: New → 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.