| Summary: | desktop sharing crashes upon connection | ||
|---|---|---|---|
| Product: | [Applications] krfb | Reporter: | Matthew Gleed <mgleed> |
| Component: | general | Assignee: | Alessandro Praduroux <pradu> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | crash | CC: | kyron |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Gentoo Packages | ||
| OS: | IRIX | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | desktop sharing crash backtrace | ||
|
Description
Matthew Gleed
2005-03-23 19:52:14 UTC
I am running the latest Slackware 10.2 install of KDE 3.4.2 and Krfb has been crashing like this for me. Strange thing is, before i upgraded to Slack 10.2, KDE 3.4.0 didn't give me any problems (i built that from source using the config tool...konstruct). *** This bug has been confirmed by popular vote. *** The same problem occurs with Chicken of the VNC on Mac OS X. I can actually use the desktop for a short time before it crashes, but bug 84204 occurs during this time. Same problem; using Chicken of the VNC: This backtrace appears to be of no use. This is probably because your packages are built in a way which prevents creation of proper backtraces, or the stack frame was seriously corrupted in the crash. (no debugging symbols found) Using host libthread_db library "/lib/tls/libthread_db.so.1". Screenshot: http://img431.imageshack.us/img431/9215/krfb9zy.png Can anyone provide a decent backtrace for this crash? There is nothing to go on here. Hi, I don't have a backtrace handy, but you can get one by connecting to krfb with vnc or remotedesktop. (Not the krdc client). That is what was causing the crash for me. If you can't replicate, let me know. I will try and get one to you. -JZ On Friday 28 July 2006 05:19, Andreas Kling wrote: [bugs.kde.org quoted mail] Created attachment 19076 [details]
desktop sharing crash backtrace
I am trying to connect using Chicken of the VNC (Mac OS X) to KDE 3.5.5
(Kubuntu). The application crashes immediately after accepting the connection
I am having the same problem with Suse 10.2. Every time I connect with any vnc client I get the same error messages as above. The version of KDE is 3.5.5. Same problem here. Decent backtrace is as follows:
(gdb) bt
#0 0x00002b283f40907b in raise () from /lib/libc.so.6
#1 0x00002b283f40a84e in abort () from /lib/libc.so.6
#2 0x00002b283f402af4 in __assert_fail () from /lib/libc.so.6
#3 0x00002b283de3fd10 in __pthread_mutex_cond_lock ()
from /lib/libpthread.so.0
#4 0x00002b283de3bde0 in pthread_cond_timedwait@@GLIBC_2.3.2 ()
from /lib/libpthread.so.0
#5 0x00000000004258cd in clientOutput (data=<value optimized out>)
at /build/buildd/kdenetwork-3.5.5/./krfb/libvncserver/main.c:263
#6 0x00002b283de38f1a in start_thread () from /lib/libpthread.so.0
#7 0x00002b283f4a3612 in clone () from /lib/libc.so.6
#8 0x0000000000000000 in ?? ()
__assert_fail has the following arguments:
"mutex->__data.__owner == 0"
"../nptl/pthread_mutex_lock.c"
108
"__pthread_mutex_cond_lock"
Hope this helps (and lead to a solution !).
Loïc
(no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (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 -1231976784 (LWP 5430)] [New Thread -1258296416 (LWP 5433)] [New Thread -1249903712 (LWP 5432)] (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) 0xffffe410 in __kernel_vsyscall () #0 0xffffe410 in __kernel_vsyscall () #1 0xb6a3c803 in poll () from /lib/tls/i686/cmov/libc.so.6 #2 0xb72a9b69 in XProcessInternalConnection () from /usr/lib/libX11.so.6 #3 0xb72a9f4f in _XRead () from /usr/lib/libX11.so.6 #4 0xb72aa924 in _XReply () from /usr/lib/libX11.so.6 #5 0xb733ebfa in XShmGetImage () from /usr/lib/libXext.so.6 #6 0x08055a40 in ?? () #7 0x080ae0b0 in ?? () #8 0x00000075 in ?? () #9 0x082c3590 in ?? () #10 0x00000000 in ?? () any updates on this? did this happen to get fixed on 'accident' in 3.5.5/6 maybe? :-) System configuration startup check disabled. (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (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 -1232763184 (LWP 13202)] [New Thread -1268679792 (LWP 13205)] [New Thread -1260287088 (LWP 13204)] (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) 0xb7f3b410 in ?? () #0 0xb7f3b410 in ?? () #1 0xbfa625f8 in ?? () #2 0xffffffff in ?? () #3 0x00000001 in ?? () #4 0xb6c6eea3 in poll () from /lib/libc.so.6 #5 0xb6e1d469 in XAddConnectionWatch () from /usr/lib/libX11.so.6 #6 0xb6e1d84f in _XRead () from /usr/lib/libX11.so.6 #7 0xb6e1e1c4 in _XReply () from /usr/lib/libX11.so.6 #8 0xb6f1b0ee in XShmGetImage () from /usr/lib/libXext.so.6 #9 0x08055770 in QWidget::setUpdatesEnabled () #10 0x080aabe8 in ?? () #11 0x00000076 in ?? () #12 0x08219118 in ?? () #13 0x00000000 in ?? () Connecting from Windows XP SP2 with firewall disabled using TightVNC version 1.2.9 to Suse 10.2 KDE 3.5.5 release 45. I'm running dual monitors (if that makes a difference). dogatemycomputer@gmail.com or (602)410-3210 if there is anything I can do to help troubleshoot. The problem also occurs using RealVNC P4.2.8 (recent download). There do not appear to be any options configurable in VNC that would help prevent this crash. The crash occurs within seconds of connecting. I too am experiencing the same issues described in previous posts. Connecting to Sidux and Freespire both running KDE 3.5.5. Connecting client Windows XP SP2, VNC viewer 3.3.3.R2. I too have tried earlier and recent versions. Within a few seconds of connection the KDE side crashes with Backtrace message as posted above. FYI...no problems connecting and maintaing connection to GNOME desktop. *** This bug has been marked as a duplicate of 124529 *** |
