[apport] d4x crashed with SIGSEGV on close

Bug #89625 reported by ChristofferS
4
Affects Status Importance Assigned to Milestone
d4x (Ubuntu)
Invalid
Medium
MOTU

Bug Description

Binary package hint: d4x

I downloaded something through d4x.

When I quit the program after successfully downloading it crashed.

ProblemType: Crash
Architecture: i386
Date: Sun Mar 4 10:14:56 2007
Disassembly: 0x0:
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/bin/d4x
InterpreterPath: /usr/bin/nt
Package: d4x 2.5.7.1-4
ProcCmdline: d4x
ProcCwd: /home/cs
ProcEnviron:
 SHELL=/bin/bash
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games
 LANG=en_DK.UTF-8
Signal: 11
SourcePackage: d4x
Stacktrace:
 #0 0x00000000 in ?? ()
 #1 0x0808a54e in ?? ()
 #2 0x080c75bd in ?? ()
 #3 0xb7f3a216 in ?? () from /usr/lib/libglib-2.0.so.0
 #4 0x00000000 in ?? ()
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? () from /usr/lib/libglib-2.0.so.0
 ?? ()
Uname: Linux t23 2.6.20-8-generic #2 SMP Tue Feb 13 05:18:42 UTC 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin plugdev scanner video

Revision history for this message
ChristofferS (ubuntu-curo) wrote :
Revision history for this message
Daniel Holbach (dholbach) wrote :

Thanks for your bug report.

Changed in d4x:
assignee: nobody → motu
importance: Undecided → Medium
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:?? ()
tMain::redraw_logs ()
time_for_logs_refresh ()
IA__g_get_current_time (result=0x0) at gmain.c:1698
g_source_destroy_internal (source=0xbfd99498, context=0x8409f78, have_lock=0) at gmain.c:938

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Changed in d4x:
status: Unconfirmed → Confirmed
Revision history for this message
Adam Niedling (krychek) wrote :

Feisty is not supported anymore and there is a newer version of d4x. Please open a new bug if you still get a crash in a later version of Ubuntu.

Changed in d4x:
status: Confirmed → Invalid
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.