Bug 625643 - [abrt] crash in gwget-1.0.4-2.fc13: raise: Process /usr/bin/gwget was killed by signal 6 (SIGABRT)
Summary: [abrt] crash in gwget-1.0.4-2.fc13: raise: Process /usr/bin/gwget was killed ...
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: gwget
Version: 13
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Christoph Wickert
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:26091d033c407479da17f9876fc...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-08-20 02:12 UTC by Kaiser Dias Schwarcz
Modified: 2010-09-27 20:37 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-09-27 20:37:37 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (17.92 KB, text/plain)
2010-08-20 02:13 UTC, Kaiser Dias Schwarcz 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
GNOME Bugzilla 630761 0 None None None Never

Description Kaiser Dias Schwarcz 2010-08-20 02:12:50 UTC 
abrt 1.1.1 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: gwget
component: gwget
crash_function: raise
executable: /usr/bin/gwget
global_uuid: 26091d033c407479da17f9876fcf8b69303f1301
kernel: 2.6.33.5-124.fc13.i686.PAE
package: gwget-1.0.4-2.fc13
rating: 4
reason: Process /usr/bin/gwget was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)
Comment 1 Kaiser Dias Schwarcz 2010-08-20 02:13:24 UTC 
Created an attachment (id=439837)
File: backtrace
Comment 2 Christoph Wickert 2010-08-20 07:19:52 UTC 
What did you do when gwget crashed? Can you reproduce the crash reliably? If so, how?
Comment 3 Kaiser Dias Schwarcz 2010-08-20 10:51:04 UTC 
I was downloading a video from newspaper site. 
I was unable to reproduce the crash.
Comment 4 Christoph Wickert 2010-09-27 20:37:37 UTC 
Thanks for your reply. I have forwarded your bug to the developers at
https://bugzilla.gnome.org/show_bug.cgi?id=630761

I am now closing this bug report because all further investigation should take place upstream. Feel free to subscribe to the upstream bug report in order to be notified about any changes. I will inform you once this bug is resolved in Fedora. If I need more info, I will get back to you.
Note You need to log in before you can comment on or make changes to this bug.