Bug 74115

Summary:	crash when trying to add an existing file to a project via "copy or link?"
Product:	[Applications] kdevelop	Reporter:	Wim Glassee <wim.glassee>
Component:	Build tools: Automake	Assignee:	KDevelop Developers <kdevelop-devel>
Status:	RESOLVED NOT A BUG
Severity:	crash
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	RedHat Enterprise Linux
OS:	Linux
Latest Commit:		Version Fixed In:

Description Wim Glassee 2004-02-04 10:18:07 UTC

Version:           3.0.0.0.1 (using KDE KDE 3.2.0)
Installed from:    RedHat RPMs
Compiler:          3.3.2-1 
OS:          Linux

First of all, I used the Fedora rpm packages but Fedora wasn't in the list I could choose from when filing this bug report.

I get

QMetaObject::findSignal:KFileDetailView: Conflict with QListView::doubleClicked(QListViewItem*,const QPoint&,int)

when trying to add an existing file to a project by using the automake manager. It asks me if I want to copy the file or just link to it. When I make a decision, it crashes.

I just upgraded to kde3.2, but I had the same error a few days ago as well with kde3.1.95

Any ideas?

Wim

Backtrace won't do much good without debug info, but hey...

(no debugging symbols found)...Using host libthread_db library "/lib/tls/libthread_db.so.1".
(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...[Thread debugging using libthread_db enabled]
[New Thread -1084850048 (LWP 28775)]
[New Thread 33119152 (LWP 28825)]

(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
0x002e5c32 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
#0  0x002e5c32 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
#1  0x0073eb2b in __waitpid_nocancel () from /lib/tls/libpthread.so.0
#2  0x00c2b791 in KCrash::defaultCrashHandler(int) ()
   from /usr/lib/libkdecore.so.4

Comment 1 Jens Dagerbo 2004-02-07 10:02:18 UTC

Does the crash happen under the same conditions as bug #55214? (That is, it crashes if you add files twice.)

The console output about "QListView::doubleClicked Conflict" is  in all likelyhood unrelated, btw.

Comment 2 Jens Dagerbo 2004-03-22 05:04:40 UTC

Renaming and setting component.

Comment 3 Jens Dagerbo 2004-09-25 01:06:07 UTC

Unreproducible, no answer for 6+ months. Closing.