Ubuntu
whoopsie-preferences package

whoopsie-preferences crashed with SIGSEGV in _IO_new_fclose()

Bug #1289097 reported by archfoe on 2014-03-07

32

This bug affects 3 people

Affects		Status	Importance	Assigned to	Milestone
	whoopsie-preferences (Ubuntu)	Fix Released	High	Unassigned

Bug Description

in Diagnostics - System Settings
When selecting "Send a report automatically if a problem prevents login" and hit Apply it crashes.

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: whoopsie-preferences 0.10
ProcVersionSignature: Ubuntu 3.13.0-15.35-generic 3.13.5
Uname: Linux 3.13.0-15-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.13.2-0ubuntu5
Architecture: amd64
Date: Thu Mar 6 20:25:30 2014
ExecutablePath: /usr/bin/whoopsie-preferences
InstallationDate: Installed on 2012-10-28 (494 days ago)
InstallationMedia: Ubuntu-Server 12.10 "Quantal Quetzal" - Release amd64 (20121017.2)
ProcCmdline: /usr/bin/whoopsie-preferences
ProcEnviron:

SegvAnalysis:
Segfault happened at: 0x7ff487a37764 <_IO_new_fclose+4>: mov (%rdi),%edx
PC (0x7ff487a37764) ok
source "(%rdi)" (0x00000000) not located in a known VMA region (needed readable region)!
destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: whoopsie-preferences
StacktraceTop:
_IO_new_fclose (fp=0x0) at iofclose.c:54
?? ()
g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: whoopsie-preferences crashed with SIGSEGV in _IO_new_fclose()
UpgradeStatus: Upgraded to trusty on 2014-03-05 (1 days ago)
UserGroups:

Tags:

Related branches

lp:~laney/whoopsie-preferences/mkdir

Merged into lp:whoopsie-preferences at revision 49

Evan (community): Approve on 2014-04-01

Daisy Pluckers: Pending requested 2014-04-01

lp:ubuntu/trusty/whoopsie-preferences

Revision history for this message

archfoe (vanio-p) wrote on 2014-03-07:

#1

Dependencies.txt Edit (701 bytes, text/plain; charset="utf-8")
Disassembly.txt Edit (1.1 KiB, text/plain; charset="utf-8")
ProcMaps.txt Edit (12.7 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (785 bytes, text/plain; charset="utf-8")
Registers.txt Edit (770 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (3.1 KiB, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (8.5 KiB, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2014-03-07: Possible regression detected

#2

This crash has the same stack trace characteristics as bug #1239811. However, the latter was already fixed in an earlier package version than the one in this report. This might be a regression or because the problem is in a dependent package.

tags:

added: regression-retracer

Revision history for this message

Apport retracing service (apport) wrote on 2014-03-07:

#3

StacktraceTop:
_IO_new_fclose (fp=0x0) at iofclose.c:54
whoopsie_automatic_reporting_changed (object=0x651270, pspec=<optimized out>, user_data=<optimized out>) at whoopsie-preferences.c:195
g_closure_invoke (closure=0x65b6b0, return_value=0x0, n_param_values=2, param_values=0x7fff2745b170, invocation_hint=0x7fff2745b110) at /build/buildd/glib2.0-2.39.91/./gobject/gclosure.c:768
signal_emit_unlocked_R (node=node@entry=0x64cdf0, detail=detail@entry=178, instance=instance@entry=0x651270, emission_return=emission_return@entry=0x0, instance_and_params=instance_and_params@entry=0x7fff2745b170) at /build/buildd/glib2.0-2.39.91/./gobject/gsignal.c:3551
g_signal_emit_valist (instance=<optimized out>, signal_id=<optimized out>, detail=<optimized out>, var_args=var_args@entry=0x7fff2745b308) at /build/buildd/glib2.0-2.39.91/./gobject/gsignal.c:3307

Revision history for this message

Apport retracing service (apport) wrote on 2014-03-07: Stacktrace.txt

#4

Stacktrace.txt Edit (10.1 KiB, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2014-03-07: StacktraceSource.txt

#5

StacktraceSource.txt Edit (8.1 KiB, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2014-03-07: ThreadStacktrace.txt

#6

ThreadStacktrace.txt Edit (19.1 KiB, text/plain)

Changed in whoopsie-preferences (Ubuntu):
importance:	Undecided → Medium
tags:	removed: need-amd64-retrace

Revision history for this message

Launchpad Janitor (janitor) wrote on 2014-03-27:

#7

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

Changed in whoopsie-preferences (Ubuntu):
status:	New → Confirmed

Iain Lane (laney) on 2014-04-01

information type:	Private → Public
Changed in whoopsie-preferences (Ubuntu):
status:	Confirmed → Triaged
importance:	Medium → High

Revision history for this message

Launchpad Janitor (janitor) wrote on 2014-04-02:

#8

This bug was fixed in the package whoopsie-preferences - 0.11

---------------
whoopsie-preferences (0.11) trusty; urgency=low

  [ Evan Dandrea ]
  * Signal to policykit that we'd like a password dialog, if one is
    needed.

  [ Iain Lane ]
  * Try to create /var/lib/apport/ to avoid crashing when we attempt to access
    a file in there. (LP: #1289097)
-- Iain Lane <email address hidden> Wed, 02 Apr 2014 10:50:18 +0100

Changed in whoopsie-preferences (Ubuntu):
status:	Triaged → Fix Released

Report a bug

This report contains Public information

Everyone can see this information.

Duplicates of this bug

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

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