Ubuntu
libproxy package

pxgsettings crashed with SIGSEGV in main()

Bug #1182043 reported by Lockal
28
This bug affects 4 people
Affects Status Importance Assigned to Milestone
libproxy
Unknown
Unknown
libproxy (Ubuntu)
Fix Released
High
Unassigned

Bug Description

After recent upgrade pxgsettings crashes after system startup.

Not sure how to reproduce, but the stack trace may indicate in which circumstances it crashed.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: libproxy1-plugin-gsettings 0.4.11-0ubuntu1
ProcVersionSignature: Ubuntu 3.9.0-2.6-generic 3.9.2
Uname: Linux 3.9.0-2-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.10.1-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Mon May 20 20:26:33 2013
ExecutablePath: /usr/lib/x86_64-linux-gnu/libproxy/0.4.7/pxgsettings
InstallationDate: Installed on 2012-02-05 (469 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120201.1)
MarkForUpload: True
ProcCmdline: /usr/lib/x86_64-linux-gnu/libproxy/0.4.7/pxgsettings org.gnome.system.proxy org.gnome.system.proxy.http org.gnome.system.proxy.https org.gnome.system.proxy.ftp org.gnome.system.proxy.socks
SegvAnalysis:
 Segfault happened at: 0x4014fa: cmpq $0x50,(%rax)
 PC (0x004014fa) ok
 source "$0x50" ok
 destination "(%rax)" (0xaaaaaaaaaaaaaaaa) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: libproxy
StacktraceTop:
 ?? ()
 __libc_start_main (main=0x4012b0, argc=6, ubp_av=0x7fffda68cb48, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fffda68cb38) at libc-start.c:260
 _start ()
Title: pxgsettings crashed with SIGSEGV in __libc_start_main()
UpgradeStatus: Upgraded to saucy on 2013-05-19 (1 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Lockal (lockal) wrote :
information type: Private → Public
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in libproxy (Ubuntu):
status: New → Confirmed
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop: main (argc=6, argv=0x7fffda68cb48) at /build/buildd/libproxy-0.4.11/libproxy/modules/pxgsettings.cpp:160

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in libproxy (Ubuntu):
importance: Undecided → Medium
summary: - pxgsettings crashed with SIGSEGV in __libc_start_main()
+ pxgsettings crashed with SIGSEGV in main()
tags: removed: need-amd64-retrace
Revision history for this message
Iain Lane (laney) wrote :

Thanks - I have a handle on this problem. I reported it upstream and am waiting for their response/advice.

Changed in libproxy (Ubuntu):
importance: Medium → High
status: Confirmed → Triaged
Revision history for this message
Iain Lane (laney) wrote :

I can't link to the bug properly, but it is http://code.google.com/p/libproxy/issues/detail?id=192

Apport retracing service (apport)
tags: added: need-amd64-retrace
Apport retracing service (apport)
tags: removed: need-amd64-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package libproxy - 0.4.11-0ubuntu2

---------------
libproxy (0.4.11-0ubuntu2) saucy; urgency=low

  * debian/patches/dont_segfault_on_exit.patch:
    - drop buggy unref calls to fix a segfault (lp: #1182043)
 -- Sebastien Bacher <email address hidden> Thu, 30 May 2013 13:20:43 +0200

Changed in libproxy (Ubuntu):
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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