Brasero

nautilus crashed with SIGSEGV in g_settings_binding_key_changed()

Bug #811204 reported by Linus Hoppe on 2011-07-15

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	Brasero	New	Undecided	Unassigned
	brasero (Ubuntu)	Expired	Medium	Unassigned

Bug Description

When clicking on the "Write on Disk"-button (marked in Screenshot) in nautilus (brasero) (adress: burn://) with several files and folders dropped, nautilus crashed.

Adding the core dump was not possible because of a problem in apport (error in network-conection), I'll try again later.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: brasero 2.32.1-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.38-10.46-generic-pae 2.6.38.7
Uname: Linux 2.6.38-10-generic-pae i686
NonfreeKernelModules: wl fglrx
Architecture: i386
Date: Fri Jul 15 17:14:00 2011
ExecutablePath: /usr/bin/nautilus
ProcCmdline: nautilus
ProcCwd: /home/linus
ProcEnviron:
LANGUAGE=de_DE:en
LANG=de_DE.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0xb17e7ff7: mov 0x14(%edi),%eax
PC (0xb17e7ff7) ok
source "0x14(%edi)" (0x00000014) not located in a known VMA region (needed readable region)!
destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: brasero
StacktraceTop:
?? () from /usr/lib/nautilus/extensions-2.0/libnautilus-brasero-extension.so
g_settings_binding_key_changed (settings=0x8ced0f0, key=0xb727b71f "flags", user_data=0x8d4df20) at /build/buildd/glib2.0-2.28.6/./gio/gsettings.c:2491
g_cclosure_marshal_VOID__STRING (closure=0xcb14a68, return_value=0x0, n_param_values=2, param_values=0x8e2c5b8, invocation_hint=0xbf9647c0, marshal_data=0x0) at /build/buildd/glib2.0-2.28.6/./gobject/gmarshal.c:498
g_closure_invoke (closure=0xcb14a68, return_value=0x0, n_param_values=2, param_values=0x8e2c5b8, invocation_hint=0xbf9647c0) at /build/buildd/glib2.0-2.28.6/./gobject/gclosure.c:767
signal_emit_unlocked_R (node=0xc9136c8, detail=752, instance=0x8ced0f0, emission_return=0x0, instance_and_params=0x8e2c5b8) at /build/buildd/glib2.0-2.28.6/./gobject/gsignal.c:3252
Title: nautilus crashed with SIGSEGV in g_settings_binding_key_changed()
UpgradeStatus: Upgraded to natty on 2011-05-24 (51 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers

Tags:

Revision history for this message

Linus Hoppe (linus-hoppe-deactivatedaccount) wrote on 2011-07-15:

the button I clicked Edit (11.3 KiB, image/png)
Dependencies.txt Edit (5.9 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (637 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (76.1 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (788 bytes, text/plain; charset="utf-8")
Registers.txt Edit (446 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (35.6 KiB, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (43.4 KiB, text/plain; charset="utf-8")
XsessionErrors.txt Edit (3.2 KiB, text/plain; charset="utf-8")

Revision history for this message

Pedro Villavicencio (pedro) wrote on 2011-07-19:

Thank you taking the time to report this bug and helping to make Ubuntu better. However, processing the crash report to get detailed information for the developers failed as the retracer did not generate a useful symbolic stack trace.
Please try to obtain a backtrace manually following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem. Before doing that please install brasero-dbgsym since those are the missing symbols, thanks.

Changed in brasero (Ubuntu):
importance:	Undecided → Medium
status:	New → Incomplete

Revision history for this message

Pedro Villavicencio (pedro) wrote on 2011-08-30:

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!