You are not logged in.

Dear visitor, welcome to KDE-Forum.org. If this is your first visit here, please read the Help. It explains in detail how this page works. To use all features of this page, you should consider registering. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.

kriko

Trainee

  • "kriko" started this thread

Posts: 127

Location: Slovenia

  • Send private message

1

Sunday, May 6th 2007, 7:57pm

Fish dies unexpectedly

I just got up and running suse 10.2 x64 and I have problem with fish protocol.

Source code

1
The process for the fish://192.168.0.16 protocol died unexpectedly.


The second computer is up and running, no changes there, however If I login as other user under my account:

Source code

1
sux anotheruser

and launch konqueror it works! It works also vice versa (logged in as anotheruser, sux myname, launch konqueror). Why is this happening?

kriko

Trainee

  • "kriko" started this thread

Posts: 127

Location: Slovenia

  • Send private message

2

Sunday, May 6th 2007, 8:15pm

I took some steps:

Source code

1
2
3
export KDE_DEBUG=yes
kdeinit
kfmexec openURL fish:/192.168.0.16


and got:

Source code

1
2
kio (KIOConnection): ERROR: Header read failed, errno=104
kio (KIOConnection): ERROR: Header has invalid size (-1)

3

Monday, May 7th 2007, 12:11am

Gentoo x64 build has the same problem (someone on irc pointed me once to the gentoo bug tracker about this problem)
So, i guess something is wrong with the 64 bit build of kdebase 3.5.x
Help mee om KDE 3.5.5 in het Nederlands te vertalen

kriko

Trainee

  • "kriko" started this thread

Posts: 127

Location: Slovenia

  • Send private message

4

Monday, May 7th 2007, 12:16am

Thanks, I think I'll report to bugs.kde.org.

kriko

Trainee

  • "kriko" started this thread

Posts: 127

Location: Slovenia

  • Send private message

5

Wednesday, May 23rd 2007, 5:34pm

This problem exists if I use newer kernel, as reported elsewere this issue is not present if you use 2.6.19 or lower.