Bug 675525 - [abrt] xfburn-0.4.3-2.fc14: gtk_tree_store_get_path: Process /usr/bin/xfburn was killed by signal 6 (SIGABRT)
Summary: [abrt] xfburn-0.4.3-2.fc14: gtk_tree_store_get_path: Process /usr/bin/xfburn ...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: xfburn
Version: 14
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Christoph Wickert
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:2ea40e0edc982746817b25a8fdf...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-06 10:29 UTC by Sergei
Modified: 2012-01-10 02:58 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-01-10 02:58:50 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (21.50 KB, text/plain)
2011-02-06 10:30 UTC, Sergei 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Sergei 2011-02-06 10:29:53 UTC 
abrt version: 1.1.14
architecture: i686
Attached file: backtrace
cmdline: xfburn
comment: Xfburn
component: xfburn
crash_function: gtk_tree_store_get_path
executable: /usr/bin/xfburn
kernel: 2.6.35.10-74.fc14.i686
package: xfburn-0.4.3-2.fc14
rating: 4
reason: Process /usr/bin/xfburn was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1296987525
uid: 501

How to reproduce
-----
1. Xfburn
2.
3.
Comment 1 Sergei 2011-02-06 10:30:05 UTC 
Created attachment 477279 [details]
File: backtrace
Comment 2 Christoph Wickert 2011-02-20 23:06:46 UTC 
Thanks for submitting this crash report. Can you give me more info about the crash? What did you do when xfburn crashed? Can you reproduce the crash when you repeat the same steps again?
Comment 3 Christoph Wickert 2011-05-16 17:16:35 UTC 
Sergei, are there any news? Can you please reply to my questions?
Comment 4 Christoph Wickert 2012-01-10 02:58:50 UTC 
No feedback from reporter, bad backtrace, not much I can do.
Note You need to log in before you can comment on or make changes to this bug.