[hardy] krdc crashes after upgrade to hardy
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
| kdenetwork (Ubuntu) |
Low
|
Unassigned | ||
Bug Description
Binary package hint: krdc
After upgrade to hardy, krdc crashes when trying to connect to a windows xp box running realvnc server 4.1.1/4.1.2. krdc worked fine with the same vnc server with gutsy. I upgraded the realvnc server from 4.1.1 to 4.1.2 because of the openssl vulnerability, but that did not change anything.
When I start krdc from the console, it shows:
werner@
VNC server supports protocol version 3.8 (viewer 3.3)
VNC authentication succeeded
Desktop name "PDFW"
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
krdc: ../../src/
KCrash: Application 'krdc' crashing...
krdc: write: Bad file descriptor
werner@
Most of the times kCrash comes up with SIGNAL 6, SIGABRT
Ulrik Mikaelsson (rawler) wrote : | #1 |
Quantum (quantumstate) wrote : | #2 |
Yep, crashes like a sissy repeatedly and infuriatingly.
HH AMD64 on Core2Duo, Qt: 3.3.8b, KDE: 3.5.9, Remote Desktop Connection: 3.5.9
TightVNC server over Debian Etch, through a reverse SSH tunnel, deprivileged.
Quantum (quantumstate) wrote : | #3 |
$ krdc
VNC server supports protocol version 3.3 (viewer 3.3)
VNC authentication succeeded
Desktop name "quantum's Hex desktop (hex:1)"
Connected to VNC server, using protocol version 3.3
VNC server default format:
16 bits per pixel.
Least significant byte first in each pixel.
True colour: max red 31 green 63 blue 31, shift red 11 green 5 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
krdc: ../../src/
KCrash: Application 'krdc' crashing...
$
Ntweat (hinduja-saurabh) wrote : | #4 |
i m having the same problem after updating to Kubuntu Hardy 8.04
ntweat@IBM:~$ krdc
VNC server supports protocol version 3.8 (viewer 3.3)
VNC authentication succeeded
Desktop name "x11"
Connected to VNC server, using protocol version 3.3
VNC server default format:
16 bits per pixel.
Least significant byte first in each pixel.
True colour: max red 31 green 63 blue 31, shift red 11 green 5 blue 0
Using default colormap and translating from BGR233. Pixel format:
8 bits per pixel.
True colour: max red 7 green 7 blue 3, shift red 0 green 3 blue 6
Got 256 exact BGR233 colours out of 256
Using shared memory PutImage
krdc: ../../src/
KCrash: Application 'krdc' crashing...
Harald Sitter (apachelogger) wrote : | #5 |
Does this still happen with KDE 4.1.1 or KDE 3.5.10?
Changed in kdenetwork: | |
status: | New → Incomplete |
Werner Karl (wkarl-bfe) wrote : | #6 |
Yes, it still happens on KDE 3.5.10.
My krdc version is 4:3.5.10-
Harald Sitter (apachelogger) wrote : | #7 |
Would be interesting whether it is still valid in KDE 4. Should be fixed for KDE 3 either way.
Changed in kdenetwork: | |
importance: | Undecided → Low |
status: | Incomplete → Confirmed |
Jonathan Thomas (echidnaman) wrote : | #8 |
Kubuntu 8.04 is no longer supported, so this won't be fixed for KDE 3.
Changed in kdenetwork (Ubuntu): | |
status: | Confirmed → Won't Fix |
Possibly related: /bugs.launchpad .net/ubuntu/ +source/ libxcb/ +bug/185311 forum.tuxx- home.at/ viewtopic. php?f=10& t=565
https:/
http://