Reliably crashes (segmentation fault) when opening "User Accounts"

Bug #892585 reported by Matthew Paul Thomas
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
gnome-control-center (Ubuntu)
Confirmed
Low
Unassigned

Bug Description

gnome-control-center 1:3.2.1-0ubuntu1, Ubuntu 11.10

1. At a terminal, enter "gnome-control-center".
2. When it launches, click "User Accounts".

What happens:
* System Settings crashes.
* The terminal says "Segmentation fault".

Revision history for this message
Walter Garcia-Fontes (walter-garcia) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command, as it will automatically gather debugging information, in a terminal:
apport-collect 892585
When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

Changed in gnome-control-center (Ubuntu):
status: New → Incomplete
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, your crash report is either missing or challenging to deal with as a ".crash" file. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer.

If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.

Now open your file manager, navigate to your /var/crash directory and open the crash report you wish to submit.
If this fails you will have to open a terminal and file your report with 'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash is the crash you would like to report. If you get an error that you aren't allowed to access this report you will have to file it with 'sudo ubuntu-bug /var/crash/_my_crash_report.crash'.

I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thanks in advance for your cooperation and understanding.

Changed in gnome-control-center (Ubuntu):
importance: Undecided → Low
status: Incomplete → Invalid
Revision history for this message
Matthew Paul Thomas (mpt) wrote :

Thanks for those instructions. Unfortunately, they don't work. Apport does run, and produces the crash report. But the crash report is 114.4 MB, and ubuntu-bug gets about 90% of the way through uploading it before it reports "Cannot connect to crash database, please check your Internet connection. HTTP Error 503: Service Unavailable". (I've tested this several times, and meanwhile the rest of Launchpad is working fine.) Martin Pitt thinks perhaps Launchpad is setting an upper limit on the size of uploaded crash reports.

So is there anything else I can do to help get the bug fixed?

Changed in gnome-control-center (Ubuntu):
status: Invalid → New
Revision history for this message
Sebastien Bacher (seb128) wrote :

Could you clean your current .crash, install gnome-control-center-dbgsym (you need a ddeb source in your apt sources as explained on https://wiki.ubuntu.com/DebuggingProgramCrash), trigger the bug again and tell apport to send the "small" version of the report? Those can't be retraced but it should contain a stacktrace from your local installation, with the dbgsym installed it should be useful enough (we might do another iteration with some extra ddebs installed once we get the first stacktrace)

Revision history for this message
Matthew Paul Thomas (mpt) wrote :

Thanks Sebastien. Following those instructions, the "Complete report" shrank to only 23 MB (only 2 MB larger than the "Reduced report"), so I sent the complete one.

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
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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