Red Hat Bugzilla – Bug 626349
[abrt] gwget-1.0.4-2.fc13: find_root: Process /usr/bin/gwget was killed by signal 11 (SIGSEGV)
Last modified: 2010-11-28 04:53:09 EST
abrt version: 1.1.13
Attached file: backtrace
reason: Process /usr/bin/gwget was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
Created an attachment (id=440347)
What did you do when gwget crashed? Can you reproduce the crash reliably? If
Any news on this bug? Can you please provide the info I asked for?
Sorry for the delay!
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:
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 **:
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.
(In reply to comment #4)
> Sorry for the delay!
Same here. :( This has dropped off my radar, sorry.
> (gwget:2869): Gtk-CRITICAL **:
> assertion 'VALID_ITER(iter,list_stor)' failed
Save to ignore, this is not the root of the crash.
> I argue that this error should reproduce on any system with any download.
I just tried to reproduce it with the URL you provided. Adding a download from the commandline does not work correctly (it wont show up and on the second attempt gwget complains that the download had already been added), but it does not crash, no matter what I do. I am using gwget quite frequently and I have never seen this crash.
I have to admit that I'm clueless about this one, so I have forwarded it to the upstrem developer for further investigation (in fact all ABRT reports should go to the developers directly). From now on, new comments shoud be added at
I will get back to you if I need info and inform you once the issue has been resolved in Fedora. Thanks for reporting this bug.
*** This bug has been marked as a duplicate of bug 542393 ***