| Summary: | Deadlock in KRDC VNC plugin | ||
|---|---|---|---|
| Product: | [Applications] krdc | Reporter: | Tony White <tonywhite100> |
| Component: | VNC | Assignee: | Urs Wolfer <uwolfer> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | psibernetic |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Mandriva RPMs | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Bug Depends on: | |||
| Bug Blocks: | 201043, 205966, 220262, 220456, 225125, 227501, 229295, 230478, 233780, 234267, 235412, 235550, 236275, 242544, 242822 | ||
|
Description
Tony White
2009-02-24 19:18:58 UTC
Do you have any steps to reproduce this crash? What VNC server do you use? Regular vncserver and it happens randomly just using krdc to connect to a server. Normals steps of just adding the server by name it connects, Disconnect use the link created on the left in history to connect to the server. I didn't do anything unusual. I followed the manual to create the connection. I have same error report from The KDE Crash Handler. This happens to me when I am in VNC server mode and want to go full screen. I am connecting to another PC with tightVNC Server running in service mode. The server and this client are on same network and subnet. My dump follows: Application: KRDC (krdc), signal SIGABRT Thread 1 (Thread 0xb606d6c0 (LWP 6260)): [KCrash Handler] #6 0xb8031430 in __kernel_vsyscall () #7 0xb67858a0 in raise () from /lib/tls/i686/cmov/libc.so.6 #8 0xb6787268 in abort () from /lib/tls/i686/cmov/libc.so.6 #9 0xb6a2a795 in qt_message_output () from /usr/lib/libQtCore.so.4 #10 0xb6a2a872 in qFatal () from /usr/lib/libQtCore.so.4 #11 0xb6a2a8cc in qt_assert_x () from /usr/lib/libQtCore.so.4 #12 0x0807d865 in _start () Backtrace is not usable, please see: http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports krdc crashed on me, too. The VNC in question is RealVNC 4.0 on Windows 2000.
krdc keeps on crashing after a while (it used to work with this server....)
Used version is debian-packages 4:3.5.10-2
Backtrace:
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb6cd46d0 (LWP 29326)]
[KCrash handler]
#6 0xb80d3424 in __kernel_vsyscall ()
#7 0xb79ec640 in raise () from /lib/i686/cmov/libc.so.6
#8 0xb79ee008 in abort () from /lib/i686/cmov/libc.so.6
#9 0xb79e55ce in __assert_fail () from /lib/i686/cmov/libc.so.6
#10 0xb7c98127 in process_responses (dpy=0x8d7f0b0, wait_for_first_event=0,
current_error=0x0, current_request=0) at ../../src/xcb_io.c:242
#11 0xb7c98a86 in _XEventsQueued (dpy=0x8d7f0b0, mode=2)
at ../../src/xcb_io.c:256
#12 0xb7c81398 in XPending (dpy=0x8d7f0b0) at ../../src/Pending.c:56
#13 0xb720edba in QEventLoop::processEvents (this=0x8daa258, flags=4)
at kernel/qeventloop_x11.cpp:150
#14 0xb727d1a0 in QEventLoop::enterLoop (this=0x8daa258)
at kernel/qeventloop.cpp:201
#15 0xb727d066 in QEventLoop::exec (this=0x8daa258)
at kernel/qeventloop.cpp:148
#16 0xb7264e5f in QApplication::exec (this=0xbfcf122c)
at kernel/qapplication.cpp:2761
#17 0x080703ed in ?? ()
#18 0xbfcf122c in ?? ()
#19 0xbfcf122c in ?? ()
#20 0x00000000 in ?? ()
Ping, please provide the requested information. Without that I will not be able to fix it. Can anybody confirm if this bug is fixed (fix applied for KDE SC 4.5 Beta 2)? We have fixed some crashes in the VNC plugin recently. Can you still reproduce this issue with a recent version of KRDC (from KDE SC 4.5 or later)? Closing as fixed since nobody can reproduce this crashes anymore with the fixes from KRDC 4.5. |