[background]: gnome-control-center crashed with SIGSEGV in cc_background_xml_load_xml_internal()

Bug #1044100 reported by Fred
24
This bug affects 3 people
Affects Status Importance Assigned to Milestone
gnome-control-center (Ubuntu)
Invalid
Low
Unassigned

Bug Description

I was looking at the Change Desktop Background dialog while updating ubuntu-wallpaper package.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: gnome-control-center 1:3.4.2-0ubuntu13
ProcVersionSignature: Ubuntu 3.5.0-13.14-generic 3.5.3
Uname: Linux 3.5.0-13-generic x86_64
ApportVersion: 2.5.1-0ubuntu4
Architecture: amd64
CrashCounter: 1
Date: Fri Aug 31 00:36:13 2012
ExecutablePath: /usr/bin/gnome-control-center
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
ProcCmdline: gnome-control-center background
SegvAnalysis:
 Segfault happened at: 0x7f66bb2d6222: mov (%rax),%rdi
 PC (0x7f66bb2d6222) ok
 source "(%rax)" (0xaaaaaaaaaaaaaaaa) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gnome-control-center
StacktraceTop:
 ?? () from /usr/lib/control-center-1/panels/libbackground.so
 ?? () from /usr/lib/control-center-1/panels/libbackground.so
 ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
 g_cclosure_marshal_generic_va () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: [background]: gnome-control-center crashed with SIGSEGV in ffi_call_unix64()
UpgradeStatus: Upgraded to quantal on 2012-07-25 (35 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
usr_lib_gnome-control-center:
 activity-log-manager-control-center 0.9.4-0ubuntu3
 deja-dup 23.90-0ubuntu1
 gnome-control-center-signon 0.0.13-0ubuntu1
 indicator-datetime 12.10.0-0ubuntu1

Revision history for this message
Fred (eldmannen+launchpad) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 cc_background_xml_load_xml_internal (xml=0x7f66dc8ca640, filename=filename@entry=0x7f66dc5e11e0 "/usr/share/gnome-background-properties/quantal-wallpapers.xml", in_thread=in_thread@entry=0) at cc-background-xml.c:304
 gnome_wp_file_changed (data=<optimized out>, file=<optimized out>, monitor=<optimized out>, other_file=<optimized out>, event_type=<optimized out>) at cc-background-xml.c:338
 gnome_wp_file_changed (monitor=<optimized out>, file=<optimized out>, other_file=<optimized out>, event_type=<optimized out>, data=<optimized out>) at cc-background-xml.c:326
 ffi_call_unix64 () at ../src/x86/unix64.S:75
 ffi_call (cif=cif@entry=0x7fff4d5aca30, fn=fn@entry=0x7f66bb2d6670 <gnome_wp_file_changed>, rvalue=0x7fff4d5ac960, avalue=avalue@entry=0x7fff4d5ac8e0) at ../src/x86/ffi64.c:492

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in gnome-control-center (Ubuntu):
importance: Undecided → Medium
summary: [background]: gnome-control-center crashed with SIGSEGV in
- ffi_call_unix64()
+ cc_background_xml_load_xml_internal()
tags: removed: need-amd64-retrace
tags: added: running-unity
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gnome-control-center (Ubuntu):
status: New → Confirmed
information type: Private → Public
Changed in gnome-control-center (Ubuntu):
importance: Medium → Low
Revision history for this message
Sebastien Bacher (seb128) wrote :

The bug hasn't seen any activity in years and there has been no recent similar reports, the code also changed quite a lot since and it's likely the issue doesn't exist anymore. Closing, feel free to open a new report if you still get problems in recent Ubuntu versions

Changed in gnome-control-center (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
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.