Ubuntu
gwibber package

unity-gwibber-daemon crashed with SIGSEGV in _start()

Bug #932454 reported by Jason Warner on 2012-02-15

10

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	Gwibber	Expired	Undecided	Unassigned
	gwibber (Ubuntu)	Expired	Medium	Unassigned

Bug Description

Just installed gwibber lens in precise and got this when trying to use it.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: unity-lens-gwibber 3.3.3-0ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-16.25-generic 3.2.6
Uname: Linux 3.2.0-16-generic x86_64
NonfreeKernelModules: wl nvidia
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
Date: Wed Feb 15 10:53:30 2012
ExecutablePath: /usr/lib/gwibber/unity-gwibber-daemon
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
ProcCmdline: /usr/lib/gwibber/unity-gwibber-daemon
SegvAnalysis:
Segfault happened at: 0x40375b <_start+1515>: mov 0x28(%r12),%rbp
PC (0x0040375b) ok
source "0x28(%r12)" (0x00000028) not located in a known VMA region (needed readable region)!
destination "%rbp" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gwibber
Stacktrace:
#0 0x000000000040375b in _start ()
No symbol table info available.
StacktraceTop: _start ()
Title: unity-gwibber-daemon crashed with SIGSEGV in _start()
UpgradeStatus: Upgraded to precise on 2012-02-01 (13 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Tags:

Revision history for this message

Jason Warner (jasoncwarner) wrote on 2012-02-15:

#1

Dependencies.txt Edit (3.7 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (810 bytes, text/plain; charset="utf-8")
ProcEnviron.txt Edit (141 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (17.5 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (817 bytes, text/plain; charset="utf-8")
Registers.txt Edit (722 bytes, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (997 bytes, text/plain; charset="utf-8")

visibility:

private → public

Revision history for this message

Apport retracing service (apport) wrote on 2012-02-15:

#2

Stacktrace:
#0 0x000000000040375b in _start ()
No symbol table info available.
StacktraceTop: _start ()

Revision history for this message

Apport retracing service (apport) wrote on 2012-02-15: ThreadStacktrace.txt

#3

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

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

Bilal Shahid (s9iper1) on 2012-02-18

Changed in gwibber:
importance:	Undecided → High

Revision history for this message

Bilal Shahid (s9iper1) wrote on 2012-03-12:

#4

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:

* Is this reproducible now ?
* If so, what specific steps should we take to recreate this bug?

This will help us to find and resolve the problem.

Changed in gwibber:
status:	New → Incomplete
importance:	High → Undecided
Changed in gwibber (Ubuntu):
status:	New → Incomplete

Revision history for this message

Launchpad Janitor (janitor) wrote on 2012-05-12:

#5

[Expired for Gwibber because there has been no activity for 60 days.]

Changed in gwibber:
status:	Incomplete → Expired

Revision history for this message

Launchpad Janitor (janitor) wrote on 2012-05-12:

#6

[Expired for gwibber (Ubuntu) because there has been no activity for 60 days.]

Changed in gwibber (Ubuntu):
status:	Incomplete → Expired

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

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