[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#358606: Bug#392607: krusader is horribly unstable in network connections



On 10/12/06, Frank Schoolmeesters <frank_schoolmeesters@yahoo.com> wrote:
On 10/12/06, Rafal Maj <rafal@raf256.org> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Package: krusader
> Version: 1.70.0-1
> Severity: major
>
> ii  krusader                          1.70.0-1
>
> Krusader is almos unusable in network connections mode - it crashes all
> the time.
>
>
> - --
> Rafał Maj
> www.Raf256.org C++
>
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.3 (GNU/Linux)
>
> iD8DBQFFLlG0zze79KYWSSMRAlkyAKCchjYgrS0jkUgWIBdPoFhkqRiKEwCeL0tK
> MOgtIwqoX3ghDJCdL9N+Dk8=
> =QHQN
> -----END PGP SIGNATURE-----
>
>
>

Hi,

It might be a kioslave problem.
Please check bug #386233 for more info.
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=386233
Maybe these 2 bugreports can be merged?

And check also bug #358606
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=358606
And maybe all 3 bugreports can be merged?

kind regards,

Frank Schoolmeesters
http://krusader.sourceforge.net


Hi Rafal,

Date: Fri, 13 Oct 2006 10:16:43 +0200
From: Rafal Maj <rafal@raf256.org>
To: Frank Schoolmeesters <frank_schoolmeesters@yahoo.com>
Subject: Re: Bug#392607: krusader is horribly unstable in network connections


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Frank Schoolmeesters wrote:

> It might be a kioslave problem.
> Please check bug #386233 for more info.
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=386233
> Maybe these 2 bugreports can be merged?

> And check also bug #358606
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=358606
> And maybe all 3 bugreports can be merged?

Yes, they look like same problem.

Sorry for re-reporting
No problem at all

but noone seem to care.

I have also this impression.

I see this bug from like a half year(!) and still it isnt fix!
Yes it is.

Will anyone fix it?
I don't know, if kioslave is the cause, the kde-team need to fix it,
or someone needs to create a patch for it and send it to the kde-team.

Thanks
You're welcome.

Maybe check http://bugs.kde.org/
Is this bug reported there?
and maybe some more backtraces might help (i hope).

I have mailed this also to BTS.

btw. sorry for the delay to reply

regards,

Frank Schoolmeesters
http://krusader.sourceforge.net

Reply to: