Bug 565387 - [abrt] crash in xarchiver-0.5.2-5.fc12
Summary: [abrt] crash in xarchiver-0.5.2-5.fc12
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: xarchiver
Version: 12
Hardware: ppc
OS: Linux
low
medium
Target Milestone: ---
Assignee: Christoph Wickert
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:bb64a24460bab7cd463a5bd63e0...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-02-15 06:03 UTC by Alexey Kuznetsov
Modified: 2010-02-22 06:30 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-02-15 21:41:34 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (9.33 KB, text/plain)
2010-02-15 06:03 UTC, Alexey Kuznetsov
no flags Details

Description Alexey Kuznetsov 2010-02-15 06:03:11 UTC
abrt 1.0.6 detected a crash.

architecture: ppc
Attached file: backtrace
cmdline: xarchiver '/home/axet/.gvfs/local-rw /h /home/axet/.gvfs/loc\xd0\x9f\xd0\xb0\xd0\xba\xd0\xb5\xd1\x82 /home'
component: xarchiver
executable: /usr/bin/xarchiver
kernel: 2.6.31.12-174.2.3.fc12.ppc
package: xarchiver-0.5.2-5.fc12
rating: 3
reason: Process was terminated by signal 6 (Aborted)
release: Fedora release 12 (Constantine)

Comment 1 Alexey Kuznetsov 2010-02-15 06:03:18 UTC
Created attachment 394259 [details]
File: backtrace

Comment 2 Christoph Wickert 2010-02-15 09:49:15 UTC
Thanks for your bug report. Can you provide some info on how to reproduce this bug? Is it reproducible or does it happen only randomly? How did you mount the gvfs share? What kind of share was it? And what are these strange escaped letters in the filename? What locale are you using? And why did you try to extract something to /home? I doubt you have write permissions there.

The backtrace is bad as it contains no debuginfo. This is a bug in abrt that should be fixed in 1.0.6, but obviously it's not. If you can reproduce the bug, you can manually install the debug packages with

debuginfo-install xarchiver

and then submit a new backtrace please.

Comment 3 Alexey Kuznetsov 2010-02-15 14:07:51 UTC
many questions i dont have answers sorry.

but it was:
 - unable to reproduce. just first report on it.
 - happens once
 - it is my ppc machine
 - samba server on same machine (aka loopback connection)
 - read/write samba share
 - cyrillic names with spaces (escaped letters?) (russan + utf-8)
 - mounted by double click on desktop link to (smb://mini.local/local-rw)
 - archive was 7zip, i did create archive, maybe cancel it, may be create it again on same name... not sure, sorry. or... hmm.. it was probably out of space problem...

Comment 4 Christoph Wickert 2010-02-15 21:41:34 UTC
Ok, thanks a lot for all these infos. There are a lot of problems, but none of them should make xarchiver crash. Unfortunately with this backtrace, I cannot help you. This is the worst backtrace I have ever seen. Please don't take this personally, it's a bug in the abrt tool.

I suggest to install the debuginfo manually and if xarchiver crashes again, just submit a new report. I'll close this one now because I really can't do anything for you.

Comment 5 Christoph Wickert 2010-02-21 16:52:02 UTC
Alexey, can you please provide the coredump file?

Comment 6 Alexey Kuznetsov 2010-02-22 06:30:31 UTC
sorry, i already wipe report from abrt.


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