gwibber-service crashed with SIGSEGV in free()

Bug #631147 reported by Brett Alton
662
This bug affects 97 people
Affects Status Importance Assigned to Milestone
gwibber (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Binary package hint: gwibber

Gwibber was running in the background and all of a sudden crashed.

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: gwibber-service 2.31.91-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.35-19.28-generic 2.6.35.3
Uname: Linux 2.6.35-19-generic x86_64
Architecture: amd64
Date: Sun Sep 5 13:47:45 2010
ExecutablePath: /usr/bin/gwibber-service
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta amd64 (20100901.1)
InterpreterPath: /usr/bin/python2.6
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/gwibber-service
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.utf8
SegvAnalysis:
 Segfault happened at: 0x7ffaf8306c2d <free+29>: mov -0x8(%rdi),%rsi
 PC (0x7ffaf8306c2d) ok
 source "-0x8(%rdi)" (0xe000afe8) not located in a known VMA region (needed readable region)!
 destination "%rsi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gwibber
StacktraceTop:
 free () from /lib/libc.so.6
 ffi_call_unix64 ()
 ffi_call ()
 _CallProc ()
 ?? () from /usr/lib/python2.6/lib-dynload/_ctypes.so
Title: gwibber-service crashed with SIGSEGV in free()
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev sambashare tape video

Revision history for this message
Brett Alton (brett-alton-deactivatedaccount) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 free () from /lib/libc.so.6
 ffi_call_unix64 ()
 ffi_call ()
 _CallProc (pProc=<value optimized out>,
 CFuncPtr_call (self=0x30db460, inargs=0x30de5d0,

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 gwibber (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Victor Vargas (kamus) wrote :

@Brett, Please could you run under latest version of gwibber: "gwibber --debug" and attach all resulted output to a textfile (following your steps to reproduce this issue), Thanks!

Changed in gwibber (Ubuntu):
status: New → Incomplete
visibility: private → public
Revision history for this message
dox187 (dox187) wrote :

gwibber --debug
Gtk-Message: (for origin information, set GTK_DEBUG): failed to retrieve property `gtk-enable-event-sounds' of type `gboolean' from rc file value "((GString*) 0x29563a0)" of type `gboolean'
Gtk-Message: (for origin information, set GTK_DEBUG): failed to retrieve property `gtk-enable-input-feedback-sounds' of type `gboolean' from rc file value "((GString*) 0x27410e0)" of type `gboolean'
Gtk-Message: (for origin information, set GTK_DEBUG): failed to retrieve property `gtk-button-images' of type `gboolean' from rc file value "((GString*) 0x295cae0)" of type `gboolean'

** (gwibber:10122): WARNING **: Trying to register gtype 'WnckWindowState' as enum when in fact it is of type 'GFlags'

** (gwibber:10122): WARNING **: Trying to register gtype 'WnckWindowActions' as enum when in fact it is of type 'GFlags'

** (gwibber:10122): WARNING **: Trying to register gtype 'WnckWindowMoveResizeMask' as enum when in fact it is of type 'GFlags'
ERROR:dbus.proxies:Introspect error on com.Gwibber.Service:/com/gwibber/Service: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Traceback (most recent call last):
  File "/usr/bin/gwibber", line 72, in <module>
    client.Client()
  File "/usr/lib/python2.6/dist-packages/gwibber/client.py", line 536, in __init__
    self.w = GwibberClient()
  File "/usr/lib/python2.6/dist-packages/gwibber/client.py", line 34, in __init__
    self.model = gwui.Model()
  File "/usr/lib/python2.6/dist-packages/gwibber/gwui.py", line 42, in __init__
    self.services = json.loads(self.daemon.GetServices())
  File "/usr/lib/pymodules/python2.6/dbus/proxies.py", line 68, in __call__
    return self._proxy_method(*args, **keywords)
  File "/usr/lib/pymodules/python2.6/dbus/proxies.py", line 140, in __call__
    **keywords)
  File "/usr/lib/pymodules/python2.6/dbus/connection.py", line 620, in call_blocking
    message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

Revision history for this message
Victor Vargas (kamus) wrote :

Please Ken or something can you take a look to this problem.

Changed in gwibber (Ubuntu):
status: Incomplete → New
Revision history for this message
Omer Akram (om26er) wrote :

dox you are facing bug 635571 and not this one.

Revision history for this message
Victor Vargas (kamus) wrote :

Please try to obtain a valgrind log following the instructions at https://wiki.ubuntu.com/Valgrind and attach the file to the bug report. Thanks!

Revision history for this message
Tomas Vaculin (tvaculin) wrote :

here is the log from Valgrind...
I hope that it will help

Revision history for this message
Brad Heap (nzv8fan) wrote :

After adding a new twitter account and returning to the main gui screen this error popped up.

Revision history for this message
martincasc (martincasco) wrote :

Same problem here... but I'm running a live Session trying to find out if my maverick installation has any problem...

So, on live session have this issue; on installed session Gwibber doesn't update my twitts

Revision history for this message
Shane Rice (shane2peru) wrote :

Just setting here working on other stuff and Gwibber crashed. Odd.

Revision history for this message
Victor Vargas (kamus) wrote :

Shane, please do not submit .crash files into reports. by the way, any news about this issue?

Revision history for this message
Victor Vargas (kamus) wrote :

Brett, are you still facing this issue or has been fixed with newer releases?

Revision history for this message
Victor Vargas (kamus) wrote :

Since this issue has a long time without activity and seems like is solved I will close this report now. Thanks

Changed in gwibber (Ubuntu):
status: New → Fix Released
Bilal Shahid (s9iper1)
no longer affects: gwibber
To post a comment you must log in.