Bug 640350 - [abrt] gnome-commander-2:1.2.8.8-2.fc13: Process /usr/libexec/gnome-commander/gnome-commander was killed by signal 11 (SIGSEGV)
Summary: [abrt] gnome-commander-2:1.2.8.8-2.fc13: Process /usr/libexec/gnome-commander...
Keywords:
Status: CLOSED DUPLICATE of bug 622853
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-commander
Version: 13
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Mamoru TASAKA
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:4bd3f3622d2bfc2eee158b4d151...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-10-05 16:03 UTC by Daniel Stripes
Modified: 2010-11-09 13:29 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-09 13:29:02 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (37.01 KB, text/plain)
2010-10-05 16:03 UTC, Daniel Stripes 		no flags Details
View All

Description Daniel Stripes 2010-10-05 16:03:33 UTC 
abrt version: 1.1.13
architecture: x86_64
Attached file: backtrace
cmdline: gnome-commander
comment: Attempted to connect to shared volume (smb://) connected to USB port of Buffalo Technologies WZR-HP-G300NH.
component: gnome-commander
crash_function: IA__gdk_window_set_geometry_hints
executable: /usr/libexec/gnome-commander/gnome-commander
kernel: 2.6.34.7-56.fc13.x86_64
package: gnome-commander-2:1.2.8.8-2.fc13
rating: 4
reason: Process /usr/libexec/gnome-commander/gnome-commander was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
time: 1286294201
uid: 500
Comment 1 Daniel Stripes 2010-10-05 16:03:35 UTC 
Created attachment 451713 [details]
File: backtrace
Comment 2 Karel Klíč 2010-11-09 13:29:02 UTC 

*** This bug has been marked as a duplicate of bug 622853 ***
Comment 3 Karel Klíč 2010-11-09 13:29:02 UTC 
This bug appears to have been filled using a buggy version of ABRT, because
it contains a backtrace which is a duplicate of backtrace from bug #622853.

Sorry for the inconvenience.
Note You need to log in before you can comment on or make changes to this bug.