Bug 459345 - k9copy crashes instantly when a file is opened
Summary: k9copy crashes instantly when a file is opened
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: kdelibs
Version: 9
Hardware: i386
OS: Linux
medium
high
Target Milestone: ---
Assignee: Than Ngo
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-08-17 04:26 UTC by Mick Mearns
Modified: 2008-09-06 22:05 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2008-09-06 21:22:48 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
backtrace output, and xterm output. (8.51 KB, text/plain)
2008-08-17 04:26 UTC, Mick Mearns
no flags Details
backtrace with debug info (6.37 KB, text/plain)
2008-08-17 19:35 UTC, Mick Mearns
no flags Details
backtrace with debug info (6.37 KB, text/plain)
2008-08-17 19:39 UTC, Mick Mearns
no flags Details
valgrind k9copy (34.18 KB, text/plain)
2008-08-18 05:16 UTC, Mick Mearns
no flags Details
backtrace from k9copy crash (2.71 KB, text/plain)
2008-09-06 21:10 UTC, Mick Mearns
no flags Details
valgrind k9copy (10.51 KB, text/plain)
2008-09-06 21:15 UTC, Mick Mearns
no flags Details

Description Mick Mearns 2008-08-17 04:26:36 UTC
Created attachment 314439 [details]
backtrace output, and xterm output.

Description of problem:
k9copy dies instantly when a disk is selected.
It only does this when there is a disk in the drive.


Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1.k9copy (menu or xterm)
2.click "open" - dies.
3.
  
Actual results:
"caused the signal 6 SIGABRT"

Expected results:
next menu

Additional info:
[root@localhost ~]# rpm -q k9copy qt kdelibs
k9copy-2.0.2-1.lvn9.i386
qt-4.3.5-2.fc9.i386
kdelibs-4.0.5-5.fc9.i386

Comment 1 Kevin Kofler 2008-08-17 08:05:57 UTC
I'm reassigning this to Qt for now, because that's what the backtrace points to, but I suspect some bug in k9copy (which is a Livna package).

Can you please install qt-debuginfo and k9copy-debuginfo and produce a backtrace with that debugging info? (If you're not sure how to install the appropriate -debuginfo packages directly, try: su -c "debuginfo-install k9copy".)

Comment 2 Rex Dieter 2008-08-17 12:17:42 UTC
fwiw, k9copy isn't from fedora (but livna or elsewhere).

Comment 3 Mick Mearns 2008-08-17 19:35:06 UTC
Created attachment 314451 [details]
backtrace with debug info

Comment 4 Mick Mearns 2008-08-17 19:39:36 UTC
Created attachment 314452 [details]
backtrace with debug info

Comment 5 Kevin Kofler 2008-08-17 19:49:25 UTC
Thanks, that tells us a lot more, but unfortunately still not the whole story. Any chance you can run k9copy in Valgrind and upload that output too?

Comment 6 Rex Dieter 2008-08-17 19:52:11 UTC
I cannot reproduce locally (with kde-4.1.0/qt-4.4.1)

Comment 7 Kevin Kofler 2008-08-17 19:58:39 UTC
The backtrace with debugging info puts the blame rather on kdelibs than Qt in any case.

I suspect that your KDE icon/pixmap cache went corrupt. In your ~/.kde/cache-hostname directory (normally a symlink to /var/tmp/kdecache-username), there is a subdirectory called kpc (short for KDE Pixmap Cache), try deleting that kpc directory and all the files it contains.

Comment 8 Mick Mearns 2008-08-18 05:16:58 UTC
Created attachment 314462 [details]
valgrind k9copy

I have a DVD-rom (sr1), and a DVD-rw (sr0).
The disc was in sr1.

Comment 9 Rex Dieter 2008-09-06 17:24:42 UTC
As Kevin suggests in Comment #7, try deleting your kpc cache
rm -rf /var/tmp/kdecache-<username>/kpc

Comment 10 Mick Mearns 2008-09-06 21:10:31 UTC
Created attachment 315957 [details]
backtrace from k9copy crash

Comment 11 Kevin Kofler 2008-09-06 21:15:09 UTC
Interesting, this backtrace looks a bit different, and might point to an actual k9copy bug (which would make this a Livna issue).

Comment 12 Mick Mearns 2008-09-06 21:15:49 UTC
Created attachment 315958 [details]
valgrind k9copy

did a 'valgrind k9copy'

As an aside I have two F9 boxes.
Both are fully updated.
One is Athlon one is Athlon X64.

Both crash k9copy.

(it used to work on them both under F9)

Mick

Comment 13 Kevin Kofler 2008-09-06 21:22:48 UTC
Ouch, this points out quite some bugs with k9copy: an invalid free, garbage data in fields of a structure which should be zero and a probably related bug with that same structure (a constraint is violated), a buffer overflow.

Closing as not a Fedora bug, please file this at bugzilla.livna.org against k9copy.

Comment 14 Rex Dieter 2008-09-06 21:46:18 UTC
It would be preferable to notify k9copy upstream of these issues.  I'll see if I can dig up some pointers or references to do that.

Comment 15 Kevin Kofler 2008-09-06 22:05:18 UTC
You're right, the upstream k9copy project is of course the best place to report this kind of bugs.


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