gwibber-bugs team mailing list archive

[Bilal Shahid <s9iper1@xxxxxxxxx>]

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

** Changed in: gwibber
   Importance: High => Undecided

** Changed in: gwibber (Ubuntu)
       Status: New => Incomplete

-- 
You received this bug notification because you are a member of Gwibber
Bug Heros, which is subscribed to Gwibber.
https://bugs.launchpad.net/bugs/932454

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

Status in Gwibber:
  Incomplete
Status in “gwibber” package in Ubuntu:
  Incomplete

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/gwibber/+bug/932454/+subscriptions