Bug 173467

Summary: krdc suddenly crashes while in use - no clear pattern
Product: [Applications] krdc Reporter: Philip Schlesinger <philip.schlesinger>
Component: generalAssignee: Urs Wolfer <uwolfer>
Status: RESOLVED DUPLICATE    
Severity: crash CC: philip.schlesinger
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Philip Schlesinger 2008-10-24 20:23:47 UTC 
Version:           3.5.10 (using KDE 3.5.10)
Compiler:          gcc (GCC) 4.2.4 (Ubuntu 4.2.4-1ubuntu3)  
OS:                Linux
Installed from:    Ubuntu Packages

$ krdc
VNC server supports protocol version 3.8 (viewer 3.3)
VNC authentication succeeded
Desktop name "VNC stephen@"
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 16 green 8 blue 0
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
Using shared memory PutImage
intersect abort
intersect abort
intersect abort
intersect abort
intersect abort
intersect abort
intersect abort
intersect abort
intersect abort
QClipboard::setData: Cannot set X11 selection owner for PRIMARY
intersect abort
krdc: ../../src/xcb_lock.c:77: _XGetXCBBuffer: Assertion `((int) ((xcb_req) - (dpy->request)) >= 0)' failed.
KCrash: Application 'krdc' crashing...
krdc: write: Bad file descriptor
$ krdc --version
Qt: 3.3.8b
KDE: 3.5.10
Remote Desktop Connection: 3.5.10
$ uname -a
Linux modigliani 2.6.24-21-generic #1 SMP Mon Aug 25 16:57:51 UTC 2008 x86_64 GNU/Linux
Comment 1 Philip Schlesinger 2008-10-24 20:25:06 UTC 
vnc server to which this is connecting is x11vnc on Kubuntu 8.04 x86_64
Comment 2 Urs Wolfer 2008-10-24 21:45:36 UTC 

*** This bug has been marked as a duplicate of bug 168598 ***