gwibber-daemon crashed with SIGSEGV in __libc_res_nquerydomain()

[kone4040]

Binary package hint: gwibber

don't exactly know what happend. Had a lot of downloading going on using 3G internet connection.

ProblemType: Crash
Architecture: i386
Date: Mon Nov 2 21:06:55 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/gwibber-daemon
InterpreterPath: /usr/bin/python2.6
NonfreeKernelModules: nvidia
Package: gwibber 2.0.0~bzr476-0ubuntu3
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/gwibber-daemon
ProcEnviron:
 SHELL=/bin/bash
 LANGUAGE=de_AT.UTF-8
 LANG=de_AT.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SegvAnalysis:
 Segfault happened at: 0x376ef5 <__libc_res_nquerydomain+197>: ret
 PC (0x00376ef5) ok
 Reason could not be automatically determined.
Signal: 11
SourcePackage: gwibber
Stacktrace:
 #0 0x00376ef5 in __libc_res_nquerydomain (statp=<value optimized out>,
     name=<value optimized out>, domain=Cannot access memory at address 0x2f
 ) at res_query.c:579
         nbuf = Cannot access memory at address 0xfffffc1a
StacktraceTop: __libc_res_nquerydomain (statp=<value optimized out>,
Title: gwibber-daemon crashed with SIGSEGV in __libc_res_nquerydomain()
Uname: Linux 2.6.31-14-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers

[Victor Vargas (kamus)]

Since this report have a long time without activity, please could you check (if is possible) in latest version included in Karmic if this issue is still affecting you? Thanks in advance.

[Victor Vargas (kamus)]

We are closing this bug report because it lacks the information we need to investigate the problem. Please reopen it if you encounter that this issue is still occurring or even better if you can check in latest Ubuntu version. To reopen the bug report you can click under the Status column, and change the Status back to "New". Thanks again!