--- Begin Message ---
Package: kdebase-kio-plugins
Version: 4:3.5.7-1
Severity: important
--- Please enter the report below this line. ---
Since a few days the fish:// protocol dies unexpectedly with any address I try
and everytime I use it. The error message that is reported by Konqueror is,
unfortunately, not very informative:
An error occurred while loading fish://<user>@<address>:
The process for the fish://<address> protocol died unexpectedly.
I tried to find out what happens using gdb, this is the output:
alex@dustpuppy:~$ gdb konqueror
GNU gdb 6.6-debian
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu"...
Using host libthread_db library "/lib/libthread_db.so.1".
(gdb) run fish://<user>@<address>
Starting program: /usr/bin/konqueror
fish://<user>@<address>
[Thread debugging using libthread_db enabled]
[New Thread 47330262517744 (LWP 7076)]
Qt: gdb: -nograb added to command-line options.
Use the -dograb option to enforce grabbing.
ASSERT: "!icon.isEmpty()"
in /build/buildd/kdebase-3.5.7/./libkonq/konq_pixmapprovider.cc (81)
ASSERT: "!icon.isEmpty()"
in /build/buildd/kdebase-3.5.7/./libkonq/konq_pixmapprovider.cc (81)
ASSERT: "!icon.isEmpty()"
in /build/buildd/kdebase-3.5.7/./libkonq/konq_pixmapprovider.cc (81)
ASSERT: "!icon.isEmpty()"
in /build/buildd/kdebase-3.5.7/./libkonq/konq_pixmapprovider.cc (81)
Program exited normally.
(gdb) quit
The only odd things I can see here, are the ASSERT statements, that appear
right before the above error message is show. But since those are also shown
with other protocols, that do work, I do not know whether this is the cause
of the problem.
To exclude that this is a Konqueror problem, I tried uploading my home page
project with Quanta and kio_fish. The result is the same: The protocol dies
here, too.
I also check that the problem is not caused by a bad configuration: I created
a new user and performed the tests with this new account. Same result.
If I can help tracking down the problem, please let me know.
--- System information. ---
Architecture: amd64
Kernel: Linux 2.6.21-1-amd64
Debian Release: lenny/sid
500 unstable ftp.gwdg.de
500 unstable ftp.de.debian.org
--- Package information. ---
Depends (Version) | Installed
===========================================-+-=======================
kdelibs4c2a (>= 4:3.5.7-1) | 4:3.5.7.dfsg.1-1
libc6 (>= 2.5-5) | 2.5-9
libdbus-1-3 (>= 0.94) | 1.0.2-5
libdbus-qt-1-1c2 (>= 0.62.git.20060814) | 0.62.git.20060814-2
libgcc1 (>= 1:4.2-20070516) | 1:4.2-20070528-1
libhal-storage1 (>= 0.5.9) | 0.5.9-3
libhal1 (>= 0.5.9) | 0.5.9-3
libldap2 (>= 2.1.17-1) | 2.1.30-13.4
libopenexr2c2a (>= 1.2.2) | 1.2.2-4.3
libqt3-mt (>= 3:3.3.7) | 3:3.3.7-4+b1
libsasl2-2 | 2.1.22.dfsg1-10
libsmbclient (>= 3.0.2a-1) | 3.0.25a-1
libstdc++6 (>= 4.2-20070516) | 4.2-20070528-1
libxcursor1 (>> 1.1.2) | 1:1.1.8-2
zlib1g (>= 1:1.2.1) | 1:1.2.3-15
kdesktop | 4:3.5.7-1
libsasl2-modules | 2.1.22.dfsg1-10
psmisc | 22.5-1
--- End Message ---