After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 635954 - gwget-1.0.4-2.fc13: find_root: Process /usr/bin/gwget was killed by signal 11
gwget-1.0.4-2.fc13: find_root: Process /usr/bin/gwget was killed by signal 11
Status: RESOLVED DUPLICATE of bug 603313
Product: gwget
Classification: Deprecated
Component: general
unspecified
Other Linux
: Normal critical
: ---
Assigned To: David Sedeño Fernández
David Sedeño Fernández
Depends on:
Blocks:
 
 
Reported: 2010-11-27 21:45 UTC by Christoph Wickert
Modified: 2010-11-28 01:38 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
backtrace of the crash (13.48 KB, text/plain)
2010-11-27 21:45 UTC, Christoph Wickert
Details

Description Christoph Wickert 2010-11-27 21:45:20 UTC
Created attachment 175386 [details]
backtrace of the crash

Original bug report at https://bugzilla.redhat.com/show_bug.cgi?id=626349

abrt version: 1.1.13
architecture: x86_64
Attached file: backtrace
cmdline: gwget
component: gwget
crash_function: find_root
executable: /usr/bin/gwget
kernel: 2.6.33.6-147.2.4.fc13.x86_64
package: gwget-1.0.4-2.fc13
rating: 4
reason: Process /usr/bin/gwget was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
time: 1282555573
uid: 500

How to reproduce
1. Call gwget with an URL, e.g.

$ gwget http://downlaod.fedoraproject.org/pub/fedora/linux/releases/13/Live/1686/fedora-13-i686-Live.iso

Comment from bug original reporter:
I cannot remember exactly what I did, but I just tried to download something.
The error is reproducible ALWAYS with ANY DOWNLOAD. So I did another try
actually with a downloadd of fedora 13:
gwget 
http://downlaod.fedoraproject.org/pub/fedora/linux/releases/13/Live/1686/fedora-13-i686-Live.iso

I get some equal lines of (german) messages in the console window:
Fehler unbekannter Fehler 73950K ... etc
(The german word Fehler translates to error, so in an US or Uk ysstem the
message should probably read as follows: error unknown error ..etc) 
Than the download stops, say freezes, the OS is still usable. 

That bug, or whatever that is only concerns gwget, wget works well. So one
might aergue that there is something wrong with GTK. The error message suggests
that assumption:
(gwget:2869): Gtk-CRITICAL **:
gtk_list_store_set_valid:
assertion 'VALID_ITER(iter,list_stor)' failed

I argue that this error should reproduce on any system with any download. 

If you think the trigger is some uncommon costellation of my hardware (DELL
inspirion), let me know the infos you need.


Note
I (Christoph) the person who opened this bug, cannot confirm the observation of the bug reporter of the downstream bug

Additional info:
Could be related
Comment 1 Fabio Durán Verdugo 2010-11-28 01:36:56 UTC
paste here the attach backtrace


Core was generated by `gwget'.
Program terminated with signal 11, Segmentation fault.

Thread 1 (Thread 5731)

  • #0 find_root
    at gsequence.c line 1410
  • #1 node_get_last
    at gsequence.c line 1444
  • #2 get_sequence
    at gsequence.c line 172
  • #3 IA__g_sequence_iter_get_sequence
    at gsequence.c line 1025
  • #4 IA__gtk_list_store_set_valist
    at gtkliststore.c line 897
  • #5 IA__gtk_list_store_set
    at gtkliststore.c line 939
  • #6 gwget_data_update_statistics
    at gwget_data.c line 98
  • #7 wget_log_process
    at wget-log.c line 438
  • #8 gwget_data_process_information
    at gwget_data.c line 274
  • #9 g_timeout_dispatch
    at gmain.c line 3396
  • #10 g_main_dispatch
    at gmain.c line 1960
  • #11 IA__g_main_context_dispatch
    at gmain.c line 2513
  • #12 g_main_context_iterate
    at gmain.c line 2591
  • #13 IA__g_main_loop_run
    at gmain.c line 2799
  • #14 IA__gtk_main
    at gtkmain.c line 1219
  • #15 main
    at main.c line 244

Comment 2 Fabio Durán Verdugo 2010-11-28 01:38:12 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 603313 ***