Bug 168598 - krdc crashes due to assert in xcb_lock.c
Summary: krdc crashes due to assert in xcb_lock.c
Status: RESOLVED UNMAINTAINED
Alias: None
Product: krdc
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Debian testing Linux
: NOR crash
Target Milestone: ---
Assignee: Urs Wolfer
URL:
Keywords:
: 173467 (view as bug list)
Depends on:
Blocks:
 
Reported: 2008-08-07 14:31 UTC by woolfie
Modified: 2008-11-24 06:15 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description woolfie 2008-08-07 14:31:45 UTC
Version:           3.5.9 (using KDE 3.5.9)
Installed from:    Debian testing/unstable Packages
OS:                Linux

Connecting to a port forwarded over ssh. krdc connects and displays window, but crashes very soon afterwards.

$ krdc localhost:51
Xlib:  extension "XInputExtension" missing on display ":1.0".
Failed to get list of devices
VNC server supports protocol version 3.8 (viewer 3.3)
VNC authentication succeeded
Desktop name "something:1 (****)"
Connected to VNC server, using protocol version 3.3
VNC server default format:
  32 bits per pixel.
  Least significant byte first in each pixel.
  True colour: max red 255 green 255 blue 255, shift red 0 green 8 blue 16
Using default colormap which is TrueColor.  Pixel format:
  32 bits per pixel.
  Least significant byte first in each pixel.
  True colour: max red 255 green 255 blue 255, shift red 16 green 8 blue 0
Using shared memory PutImage
krdc: ../../src/xcb_lock.c:77: _XGetXCBBuffer: Assertion `((int) ((xcb_req) - (dpy->request)) >= 0)' failed.
KCrash: Application 'krdc' crashing...
krdc: write: Bad file descriptor


Here's the backtrace from gdb:

(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb6c346c0 (LWP 19663)]
[New Thread 0xb6776b90 (LWP 19664)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#6  0xffffe410 in __kernel_vsyscall ()
#7  0xb7908ef5 in raise () from /lib/i686/cmov/libc.so.6
#8  0xb790a871 in abort () from /lib/i686/cmov/libc.so.6
#9  0xb79020ee in __assert_fail () from /lib/i686/cmov/libc.so.6
#10 0xb7b9fbd4 in _XGetXCBBuffer () from /usr/lib/libX11.so.6
#11 0xb7ba0fa3 in _XSend () from /usr/lib/libX11.so.6
#12 0xb7ba1120 in _XEventsQueued () from /usr/lib/libX11.so.6
#13 0xb7b893d8 in XPending () from /usr/lib/libX11.so.6
#14 0xb716af82 in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
#15 0xb71d2b80 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#16 0xb71d2a16 in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#17 0xb71bbcff in QApplication::exec () from /usr/lib/libqt-mt.so.3
#18 0x0807026d in ?? ()
#19 0xbf9dbb6c in ?? ()
#20 0xbf9dbb6c in ?? ()
#21 0x00000000 in ?? ()
Comment 1 Urs Wolfer 2008-08-07 14:37:26 UTC
Please try to reproduce with KRDC from KDE 4.1. I do not support KRDC from 3.5 anymore.
Comment 2 Robin Pedersen 2008-08-26 21:37:17 UTC
Confirmed on Kubuntu 8.04, with
Qt: 3.3.8b
KDE: 3.5.9
Remote Desktop Connection: 3.5.9

See also:
https://bugs.launchpad.net/ubuntu/+source/kdenetwork/+bug/231315
Comment 3 Urs Wolfer 2008-08-26 21:56:39 UTC
There is no manpower to fix this in the KDE 4 version. (we cannot just backport fixes, since KRDC has been rewriten in KDE 4)

Please try to reproduce with the KDE 4 version.
Comment 4 Robin Pedersen 2008-08-27 10:17:49 UTC
I will try with KDE 4 as soon as I have a chance.

However, even if you don't have time to fix it in KDE 3, it's still a bug, and it's causing problems. Maybe by reporting it here, we will still be able to find a solution for people using KDE 3.
Comment 5 Robin Pedersen 2008-08-28 09:13:18 UTC
I've tried KRDC from KDE 4, and it seems like it doesn't have this problem. Not a big surprise, since it's been rewritten.

I've also tried the recent update 3.5.10, which probably isn't much changed from 3.5.9, but the problem is still there.
Comment 6 Urs Wolfer 2008-10-24 21:45:36 UTC
*** Bug 173467 has been marked as a duplicate of this bug. ***
Comment 7 Urs Wolfer 2008-11-23 09:26:58 UTC
KRDC from KDE 3.5 is not supported anymore. Do not expect a fix for this issue. In KDE 4 this issue is not valid anymore.