gwibber-daemon crashed with SIGSEGV in fwrite()

Bug #516163 reported by Omer Akram
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gwibber (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Binary package hint: gwibber

gwibber's daemon crashes very often so the gui is there and the status icon is spinning and it wont stop unless gwibber is resatarted.

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Tue Feb 2 22:43:19 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/gwibber-daemon
InstallationMedia: Ubuntu-Netbook 10.04 "Lucid Lynx" - Alpha i386 (20100128)
InterpreterPath: /usr/bin/python2.6
Package: gwibber 2.0.0~bzr476-0ubuntu3
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/gwibber-daemon
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.utf8
ProcVersionSignature: Ubuntu 2.6.32-12.16-generic
SegvAnalysis:
 Segfault happened at: 0x16ce3c <fwrite+44>: cmpw $0x0,(%esi)
 PC (0x0016ce3c) ok
 source "$0x0" ok
 destination "(%esi)" (0x69746e75) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: gwibber
StacktraceTop:
 fwrite () from /lib/tls/i686/cmov/libc.so.6
 ?? () from /usr/lib/libcurl-gnutls.so.4
 ?? () from /usr/lib/libcurl-gnutls.so.4
 ?? () from /usr/lib/libcurl-gnutls.so.4
 ?? () from /usr/lib/libcurl-gnutls.so.4
Title: gwibber-daemon crashed with SIGSEGV in fwrite()
Uname: Linux 2.6.32-12-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Omer Akram (om26er) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 _IO_fwrite (buf=0x12b5187, size=2, count=1, fp=0x69746e75)
 showit () from /usr/lib/libcurl-gnutls.so.4
 Curl_debug () from /usr/lib/libcurl-gnutls.so.4
 Curl_failf () from /usr/lib/libcurl-gnutls.so.4
 Curl_resolv_timeout () from /usr/lib/libcurl-gnutls.so.4

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-i386-retrace
Revision history for this message
Omer Akram (om26er) wrote :

I don't face this in gwibber 2.29.1

visibility: private → public
Changed in gwibber (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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