Dolphin crashes when path contains two slashes behind each other

Bug #290717 reported by S. Young
12
Affects Status Importance Assigned to Milestone
KDE Base
Fix Released
High
kde4libs (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

Binary package hint: dolphin

I'm using Kubuntu 8.10 RC. Dolphin crashes when I enter an address in the address bar like /home//username, in stead of /home/username. The package version of dolphin is 4:4.1.2-0ubuntu4

Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Could you get a backtrace? It doesn't crash for me.

Changed in dolphin:
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
S. Young (stkyoung) wrote :

This is the backtrace:

Programma: Dolphin (dolphin), signaal SIGABRT
(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)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb5ea86c0 (LWP 5790)]
(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)
[KCrash handler]
#6 0xb7fbe430 in __kernel_vsyscall ()
#7 0xb6736880 in raise () from /lib/tls/i686/cmov/libc.so.6
#8 0xb6738248 in abort () from /lib/tls/i686/cmov/libc.so.6
#9 0xb7516795 in qt_message_output () from /usr/lib/libQtCore.so.4
#10 0xb7516872 in qFatal () from /usr/lib/libQtCore.so.4
#11 0xb7516915 in qt_assert () from /usr/lib/libQtCore.so.4
#12 0xb7d74f68 in ?? () from /usr/lib/libkio.so.5
#13 0xb7d78de7 in KDirModel::indexForUrl () from /usr/lib/libkio.so.5
#14 0x0808cef9 in _start ()
#0 0xb7fbe430 in __kernel_vsyscall ()

Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Oh, sorry. Could you install kdebase-dbg and get a backtrace? Without the debug symbols the backtrace isn't of much use. Thanks.

Revision history for this message
Roderick B. Greening (roderick-greening) wrote :

I cannot duplicate this.

Is this reproducible every time? Can you create a brand new user and try launching dolphin under that user and test again? Also, you may want to install the kdebase-dbg package so you get complete backtraces for us.

Revision history for this message
S. Young (stkyoung) wrote :

I'm sorry: I didn't know about the kdebase-dbg package. You can find the backtrace as attachment. I have created another user and I logged in using the new user account: This solved the problem. After that, I removed my .kde folder from my old user account and now I do not have this problem anymore.

Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Ok, since it was fixed by setting the config back to default I don't think we should worry about this, especially since we don't know the root cause of the configuration error.
Thanks for the bug report.

Changed in kdebase:
status: Incomplete → Invalid
Revision history for this message
S. Young (stkyoung) wrote :

I got the problem again, after adding the "folders" panel to dolphin.

Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Ok, now I can reproduce the crash. Thanks for tracking this down.

Changed in kdebase:
status: Invalid → Confirmed
Changed in kdebase:
status: Confirmed → Triaged
Changed in kdebase:
status: Unknown → Confirmed
Changed in kdebase:
status: Confirmed → Fix Released
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Fix committed for KDE 4.1.4

Changed in kdebase:
status: Triaged → Fix Committed
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Fix released in the KDE 4.2 packages for Jaunty and the "unofficia official" ones for Intrepid.

Changed in kde4libs:
status: Fix Committed → Fix Released
Changed in kdebase:
importance: Unknown → High
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.