[Bug 74115] New: QListView::doubleClicked Conflict in KFileDetailView

Wim Glassee wim.glassee at ua.ac.be
Wed Feb 4 10:23:05 UTC 2004


------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
      
http://bugs.kde.org/show_bug.cgi?id=74115      
           Summary: QListView::doubleClicked Conflict in KFileDetailView
           Product: kdevelop
           Version: unspecified
          Platform: RedHat RPMs
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: crash
          Priority: NOR
         Component: general
        AssignedTo: kdevelop-devel at kdevelop.org
        ReportedBy: wim.glassee at ua.ac.be


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




More information about the KDevelop-devel mailing list