wicd-daemon.py crashed with SIGSEGV

Bug #515368 reported by alexelprogramador
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
wicd (Ubuntu)
New
Medium
Unassigned

Bug Description

Binary package hint: wicd

Sudenly crashes.

No reasons about it.

I have many different configurations saved in wicd, but till now, it was working

thanks for your job ;)

ProblemType: Crash
Architecture: amd64
Date: Mon Feb 1 03:04:14 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/share/wicd/wicd-daemon.py
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20100113)
InterpreterPath: /usr/bin/python2.6
NonfreeKernelModules: nvidia
Package: wicd 1.6.2.2-4
PackageArchitecture: all
ProcAttrCurrent: unconfined (enforce)
ProcCmdline: python /usr/share/wicd/wicd-daemon.py
ProcEnviron: PATH=(custom, no user)
ProcVersionSignature: Ubuntu 2.6.32-12.16-generic
SegvAnalysis:
 Segfault happened at: 0x7f7dd45111e0: mov 0x34(%rdi),%eax
 PC (0x7f7dd45111e0) ok
 source "0x34(%rdi)" (0x00000034) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: wicd
StacktraceTop:
 ?? () from /lib/libdbus-1.so.3
 ?? () from /lib/libdbus-1.so.3
 ?? () from /lib/libdbus-1.so.3
 ?? () from /lib/libdbus-1.so.3
 ?? ()
Title: wicd-daemon.py crashed with SIGSEGV
Uname: Linux 2.6.32-12-generic x86_64
UserGroups:

Revision history for this message
alexelprogramador (alexvideos) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 _dbus_hash_table_get_n_entries (table=0x0) at dbus-hash.c:1702
 _dbus_connection_get_dispatch_status_unlocked (
 _dbus_connection_send_preallocated_and_unlock (
 _dbus_connection_send_and_unlock (
 ?? ()

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 wicd (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Steve Beattie (sbeattie)
information type: Private → Public
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.