[apport] gwget crashed with SIGSEGV

Bug #97455 reported by Clark Endrizzi
This bug report is a duplicate of:  Bug #381443: Drag & Drop locks up Gwget. Edit Remove
6
Affects Status Importance Assigned to Milestone
gwget2 (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Binary package hint: gwget2

Really all I did was reordered (drag and drop) some download items and it crashed.

ProblemType: Crash
Architecture: i386
Date: Wed Mar 28 09:15:14 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/bin/gwget
Package: gwget 0.98.1-2ubuntu1
PackageArchitecture: i386
ProcCmdline: gwget --force-tray-only
ProcCwd: /home/cendrizzi
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: gwget2
Stacktrace:
 #0 0xb7a6d88d in ?? () from /usr/lib/libgtk-x11-2.0.so.0
 #1 0x00000000 in ?? ()
StacktraceTop:
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
 ?? ()
ThreadStacktrace:
 .
 Thread 1 (process 5720):
 #0 0xb7a6d88d in ?? () from /usr/lib/libgtk-x11-2.0.so.0
 #1 0x00000000 in ?? ()
Uname: Linux cendrizzi-laptop 2.6.20-13-generic #2 SMP Sun Mar 25 00:21:25 UTC 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

Revision history for this message
Clark Endrizzi (cendrizzi) wrote :
Revision history for this message
Martin Pitt (pitti) wrote : Symbolic stack trace

StacktraceTop:splay (node=0x8117f10) at gtksequence.c:674
_gtk_sequence_node_get_pos (node=0x8118cc8) at gtksequence.c:801
gtk_list_store_get_path (tree_model=0x8089300, iter=0x82bd540) at gtkliststore.c:446
IA__gtk_list_store_set_valist (list_store=0x8089300, iter=0x82bd540, var_args=0xbfdcc718 "\r") at gtkliststore.c:804

Revision history for this message
Martin Pitt (pitti) wrote : Symbolic threaded stack trace
Changed in gwget2:
importance: Undecided → Medium
status: Unconfirmed → Confirmed
Revision history for this message
Artur Rona (ari-tczew) wrote :

Bug still alive? 7.04 is old distro.

Revision history for this message
Artur Rona (ari-tczew) wrote :

I've tested this bug and I can confirm, bug still alive in 1.0.1.

Revision history for this message
Artur Rona (ari-tczew) wrote :
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.