Bug#223673: bug present with krfb 3.4.2-2

2006-05-23 Thread tkotb
Hello Pierre,

First I'm trying to test with a non smp kernel.
I'll let you know soon.

Thanks

> could you boot a non smp kernel and see if that solves your problem
> (that seems unlikely, but the test is really simple for you) ? (or
> disable one CPU or hypertheading or ... from the bios if possible).
>
>
> I need a way to reproduce the bug, a backtrace, a strace log, anything
> that can help understanding the problem.
>
> to generate backtraces, please have qt-x11-free-dbg, kdelibs-dbg,
> kdebase-dbg and kdenetwork-dbg installed a please send the output in
> the KDE crash handler. without those information, I just cannot report
> that upstream's.
> --
> ·O·  Pierre Habouzit
> ··O
> [EMAIL PROTECTED] OOO
> http://www.madism.org






Bug#223673: bug present with krfb 3.4.2-2

2006-05-22 Thread tkotb
Hi Pierre,

I don't think it's a network / firewall issue, because I have another
computer that I access from the Internet the same way, and on which Krfb
works well.

This other computer (a dell laptop) is configured with almost the same
distribution (a kubuntu with recent Kde packages).

The two computers access the network the same way from another gateway +
firewall computer. On the main computer, there is no local firewall.

Another specificity of the computer on which krfb crashes is that it's a bi
processor.

Thanks
Jérôme

> tag 223673 + moreinfo
>
>
>  this looks like a firewall or sth like that problem. especially if you
> can't reproduce it on any other place.
>
>  are you really sure nothing can prevent the connection to run
> smoothly, either on your machine or on the remote one ?
>
> --
> ·O·  Pierre Habouzit
> ··O[EMAIL PROTECTED]
> OOO
> http://www.madism.org






Bug#223673: bug present with krfb 3.4.2-2

2006-05-22 Thread Pierre Habouzit
Le Lun 22 Mai 2006 16:39, [EMAIL PROTECTED] a écrit :
> Hi Pierre,
>
> I don't think it's a network / firewall issue, because I have another
> computer that I access from the Internet the same way, and on which
> Krfb works well.
>
> This other computer (a dell laptop) is configured with almost the
> same distribution (a kubuntu with recent Kde packages).
>
> The two computers access the network the same way from another
> gateway + firewall computer. On the main computer, there is no local
> firewall.
>
> Another specificity of the computer on which krfb crashes is that
> it's a bi processor.

could you boot a non smp kernel and see if that solves your problem 
(that seems unlikely, but the test is really simple for you) ? (or 
disable one CPU or hypertheading or ... from the bios if possible).


I need a way to reproduce the bug, a backtrace, a strace log, anything 
that can help understanding the problem.

to generate backtraces, please have qt-x11-free-dbg, kdelibs-dbg, 
kdebase-dbg and kdenetwork-dbg installed a please send the output in 
the KDE crash handler. without those information, I just cannot report 
that upstream's.
-- 
·O·  Pierre Habouzit
··O[EMAIL PROTECTED]
OOOhttp://www.madism.org


pgpBNVNilEkoe.pgp
Description: PGP signature


Bug#223673: bug present with krfb 3.4.2-2

2006-05-20 Thread Pierre HABOUZIT
tag 223673 + moreinfo
thanks

On Mon, Nov 21, 2005 at 01:25:40PM +0100, [EMAIL PROTECTED] wrote:
> Hi krfb maintainers,
> 
> Since around the beginning of the year I can't use krfb any more
> to access my debian from a windows computer. This bug is not client
> dependant: Plus Linux VNC clients, I have tried UltraVNC, and
> Thight VNC Clients, and I encounter the same issue that is described in the
> bug : I log on trough VNC, the screen appears, and then after a few seconds
> (after a very few mouse mooves), the krfb server crashes. On my debian
> server, I have a drkonqui crash dialog box.
> 
> What is strange is that for a few months after the bug appeared, I was
> connecting succesfully on my computer from another KDE VNC clients (mandrake
> 10, and another debian), but two months after even this solution was
> unsuccessfull (same crash). If needed I can check if this is still the case.
> 
> I have an unstable debian with KDE 3.4.2.
> I have a nvidia Geforce II mx video card.
> 
> here is the output of uname -a:
> Linux ancient_mikelange 2.6.12-1-686-smp #1 SMP Tue Aug 16 22:19:38 UTC 2005
> i686 GNU/Linux
> 
> The last VNC windows clients provide the share desktop connection, I don't
> know if this has an impact, I can check by disabeling this feature.

  this looks like a firewall or sth like that problem. especially if you
can't reproduce it on any other place.

  are you really sure nothing can prevent the connection to run
smoothly, either on your machine or on the remote one ?

-- 
·O·  Pierre Habouzit
··O[EMAIL PROTECTED]
OOOhttp://www.madism.org


signature.asc
Description: Digital signature


Bug#223673: bug present with krfb 3.4.2-2

2005-11-21 Thread tkotb
Hi krfb maintainers,

Since around the beginning of the year I can't use krfb any more
to access my debian from a windows computer. This bug is not client
dependant: Plus Linux VNC clients, I have tried UltraVNC, and
Thight VNC Clients, and I encounter the same issue that is described in the
bug : I log on trough VNC, the screen appears, and then after a few seconds
(after a very few mouse mooves), the krfb server crashes. On my debian
server, I have a drkonqui crash dialog box.

What is strange is that for a few months after the bug appeared, I was
connecting succesfully on my computer from another KDE VNC clients (mandrake
10, and another debian), but two months after even this solution was
unsuccessfull (same crash). If needed I can check if this is still the case.

I have an unstable debian with KDE 3.4.2.
I have a nvidia Geforce II mx video card.

here is the output of uname -a:
Linux ancient_mikelange 2.6.12-1-686-smp #1 SMP Tue Aug 16 22:19:38 UTC 2005
i686 GNU/Linux

The last VNC windows clients provide the share desktop connection, I don't
know if this has an impact, I can check by disabeling this feature.

Tell me if you need any log file, or other information.
Thanks.
Jerome