[opensuse] fish protocol and > 2.6.20 kernel problem fixed in 10.3 beta?
Can anyone please check and see if fish protocol is working in the 10.3 betas. In 10.2 IIRC it does not work properly with a kernel greater than 2.6.20 or so. It seems to be some interaction between fish in the kernel, as the original kernel works fine, and it is not limited to openSUSE, see http://bugs.kde.org/show_bug.cgi?id=145123 for more info. Since I use fish quite a bit, I have went back to the 2.6.18 series kernel (i.e. latest updated 10.2 kernel) where it still works. -- Joe Morris Registered Linux user 231871 running openSUSE 10.2 x86_64 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Aug 12 2007 08:14, Joe Morris (NTM) wrote:
Can anyone please check and see if fish protocol is working in the 10.3 betas. In 10.2 IIRC it does not work properly with a kernel greater than 2.6.20 or so. It seems to be some interaction between fish in the kernel,
ERROR. fish is a userspace-only filesystem, and does not even use FUSE. It uses bash only.
as the original kernel works fine, and it is not limited to openSUSE, see http://bugs.kde.org/show_bug.cgi?id=145123 for more info. Since I use fish quite a bit, I have went back to the 2.6.18 series kernel (i.e. latest updated 10.2 kernel) where it still works.
Jan -- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Aug 12 2007 08:14, Joe Morris (NTM) wrote:
Can anyone please check and see if fish protocol is working in the 10.3 betas. In 10.2 IIRC it does not work properly with a kernel greater than 2.6.20 or so. It seems to be some interaction between fish in the kernel,
ERROR. fish is a userspace-only filesystem, and does not even use FUSE. It uses bash only.
as the original kernel works fine, and it is not limited to openSUSE, see http://bugs.kde.org/show_bug.cgi?id=145123 for more info. Since I use fish quite a bit, I have went back to the 2.6.18 series kernel (i.e. latest updated 10.2 kernel) where it still works.
Did you check out the bug report? I know for certain, with all the same kde files, that it will not work normally with 2.6.22 (factory kernel) but works fine with 2.6.18.8-0.5. I downgraded to double check. If you can help track it down, please do. If you run 10.3 b1, does it work with it, and what kernel is it? What changed in the kernel to cause
On 08/12/2007 07:20 PM, Jan Engelhardt wrote: this I wished I knew. I'm sure the developer would too. -- Joe Morris Registered Linux user 231871 running openSUSE 10.2 x86_64 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Aug 12 2007 20:26, Joe Morris (NTM) wrote:
On 08/12/2007 07:20 PM, Jan Engelhardt wrote:
On Aug 12 2007 08:14, Joe Morris (NTM) wrote:
Can anyone please check and see if fish protocol is working in the 10.3 betas. In 10.2 IIRC it does not work properly with a kernel greater than 2.6.20 or so. It seems to be some interaction between fish in the kernel,
ERROR. fish is a userspace-only filesystem, and does not even use FUSE. It uses bash only.
as the original kernel works fine, and it is not limited to openSUSE, see http://bugs.kde.org/show_bug.cgi?id=145123 for more info. Since I use fish quite a bit, I have went back to the 2.6.18 series kernel (i.e. latest updated 10.2 kernel) where it still works.
Did you check out the bug report? I know for certain, with all the same kde files, that it will not work normally with 2.6.22 (factory kernel) but works fine with 2.6.18.8-0.5.
I am running 2.6.22.2 (in 10.2), and mc has no problems creating a "Shell Link" - which is fish[1] - on both i586 and x86_64, to 'another' 2.6.22.2 machine (localhost). [1] http://en.wikipedia.org/wiki/Files_transferred_over_shell_protocol Hence I believe this is not a kernel bug. Especially since
between fish in the kernel,
there is no in-kernel fish code. I do not think it's a socket issue either, because that would render mc unusable too. Run KDE/GNOME from a console, wonder about all those assertion failed messages, and then look for pointers. I get ####### CRASH ####### protocol = fish pid = 12345 signal = 29. 29? SIGIO. ("Your Input Is Ready.") I do not have much joy going deeper than this. But fish://127.0.0.1 works, so I suspect your asynchronous DNS handling is borked. It is really hard to track thanks to all the processes a simple konqueror in twm spawns. Jan -- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (2)
-
Jan Engelhardt -
Joe Morris (NTM)