Bug 169313 - krdc hang up when disconnecting from server
Summary: krdc hang up when disconnecting from server
Status: RESOLVED DUPLICATE of bug 160728
Alias: None
Product: krdc
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Urs Wolfer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-08-17 12:14 UTC by enthalpie
Modified: 2008-08-20 20:58 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:

Attachments
file from scratch (992 bytes, text/plain)
2008-08-17 12:15 UTC, enthalpie 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description enthalpie 2008-08-17 12:14:37 UTC 
Version:           kde4-Krdc 4.0.15-15 (using KDE 4.1.0)
Installed from:    SuSE RPMs
Compiler:          opensuse 10.3 
OS:                Linux

when i disconnect from vnc server (SLES 10 SP2) ckient Kde4-krdc closed
Comment 1 enthalpie 2008-08-17 12:15:39 UTC 
Created attachment 26893 [details]
file from scratch
Comment 2 enthalpie 2008-08-18 08:41:21 UTC 
I should said also something

when i connect to server i first got an error message " url as not the required form" but it is possible to connect after ?

regards
Comment 3 Urs Wolfer 2008-08-18 20:28:03 UTC 
Can you reporoduce all the time? Does it happen when you click the disconnect button, or when you quit KRDC? Please start also KRDC from Konsole and post the output.
Comment 4 enthalpie 2008-08-19 09:50:01 UTC 
Answer to your question

yes i can reproduce, this append when from the server kde menu i choice down the server. i hope man explanation are clear

what is written kde4-krdc launch from a terminal :

bernard@linux:~> KCrash: Application 'krdc' crashing...
sock_file=/home/bernard/.kde4/socket-linux/kdeinit4__0
Comment 5 enthalpie 2008-08-19 13:01:24 UTC 
I should said also because i update often  now i use kde4-krdc version 4.10-35.1 and the bug is still here
Comment 6 Urs Wolfer 2008-08-20 20:58:30 UTC 

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