Bug 384815

Summary: KDE KRDC 3 crashing
Product: [openSUSE] openSUSE 11.0 Reporter: Alexey Eremenko <al4321>
Component: KDE3Assignee: E-mail List <kde-maintainers>
Status: VERIFIED WONTFIX QA Contact: E-mail List <qa-bugs>
Severity: Critical    
Priority: P3 - Medium CC: forgotten_bSWU20Bh6O, novell.admin, sysop, wstephenson
Version: Beta 1   
Target Milestone: ---   
Hardware: Other   
OS: Other   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: Typical view of a broken krdc window

Description Alexey Eremenko 2008-04-29 14:35:38 UTC
Just installed openSUSE 11.0 BETA1. KDE 3 KRDC is constantly crashing, when trying to connect to remote VNC systems.

openSUSE 10.3 had stable Krdc3.

-Technologov, 29.4.2008.
Comment 1 Dirk Mueller 2008-05-02 13:58:27 UTC
backtrace?
Comment 2 Alexey Eremenko 2008-05-04 09:15:31 UTC
Results from GDB:

0xffffe430 in __kernel_vsyscall ()
(gdb) c
Continuing.
[New Thread 0xb6839b90 (LWP 1365)]
(no debugging symbols found)
(no debugging symbols found)
[New Thread 0xb5b50b90 (LWP 1366)]

Program received signal SIGABRT, Aborted.
[Switching to Thread 0xb6bf7b50 (LWP 1293)]
0xffffe430 in __kernel_vsyscall ()
(gdb)
Continuing.

Program exited with code 0375.
(gdb)
The program is not being run.
(gdb)
The program is not being run.
(gdb) bt
No stack.

-Technologov
Comment 3 Dirk Mueller 2008-05-05 12:18:23 UTC
it works fine for me, I'm sorry. when you get the SIGABRT message in gdb, can you type "bt" in gdb and then post the output?

thanks.
Comment 4 Alexey Eremenko 2008-05-05 19:19:43 UTC
My GDB output includes "bt" command.

-Technologov
Comment 5 Dirk Mueller 2008-05-06 08:38:50 UTC
yes, but you ran it after the program exited. see here:

(gdb)
Continuing.

Program exited with code 0375.
(gdb)
The program is not being run

I asked you to run it the app exits, right when you get the prompt for the first time. 
Comment 6 Dirk Mueller 2008-05-07 12:01:08 UTC
there is not a single line of code change in krfb of openSUSE 10.3 and the one in openSUSE 11.0. if the crash is new, it probably has the same reason like the KRDC4 bugreport you filed, so lets concentrate on that one. hopefully I can track down and fix the krdc4
Comment 7 Alexey Eremenko 2008-08-06 14:45:54 UTC
Please, lets try to fix this one. I cannot work without VNC.

Bug reopen.

-Alexey
Comment 8 Alexey Eremenko 2008-08-06 14:49:09 UTC
I used totally new PC and KRDC 3 crashes on both openSUSE 11.0 32-bit and 64-bit.
Comment 9 Alexey Eremenko 2008-08-06 14:53:18 UTC
GDB output of openSUSE 11.0 64-bit during KRDC 3 crash:

=============================================================
0x00007f5091153662 in select () from /lib64/libc.so.6
(gdb) c
Continuing.
[New Thread 0x40e16950 (LWP 14619)]
[Thread 0x432f5950 (LWP 14594) exited]
[Thread 0x45afa950 (LWP 14600) exited]
(no debugging symbols found)
[Thread 0x452f9950 (LWP 14599) exited]
[Thread 0x44af8950 (LWP 14598) exited]
[Thread 0x442f7950 (LWP 14597) exited]
[Thread 0x46afc950 (LWP 14602) exited]
[Thread 0x462fb950 (LWP 14601) exited]
[Thread 0x42af4950 (LWP 14593) exited]
[Thread 0x422f3950 (LWP 14592) exited]
[Thread 0x4170b950 (LWP 14595) exited]
[Thread 0x43af6950 (LWP 14596) exited]
[Thread 0x40e16950 (LWP 14619) exited]

[New Thread 0x40e16950 (LWP 14621)]
(no debugging symbols found)
(no debugging symbols found)
[New Thread 0x43af6950 (LWP 14622)]

Program received signal SIGABRT, Aborted.
[Switching to Thread 0x40e16950 (LWP 14621)]
0x00007f50910b95c5 in raise () from /lib64/libc.so.6
(gdb)
Continuing.

Program received signal SIGCONT, Continued.
[Switching to Thread 0x7f509441c700 (LWP 14570)]
0x00007f5091a33dd9 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
(gdb)
Continuing.

Program received signal SIGCONT, Continued.
[Switching to Thread 0x43af6950 (LWP 14622)]
0x00007f5091a3405d in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
(gdb)
Continuing.

Program exited with code 0375.
Comment 10 Zsolt Sági 2008-09-04 08:31:28 UTC
I tried to uninstall the kdenetwork3-vnc of 11.0 and installed the kdenetwork3-vnc package of 10.3. It always crashes the same way, indeed. However, as far, as I can remember, it only happens when connecting to an Xvnc server. It seems to work with krfb or windows' UltraVNC, but crashes with openSUSE 10.3's Xvnc. See my 10.3 xinetd.conf (defaults):

service vnc1
{
        socket_type     = stream
        protocol        = tcp
        wait            = no
        user            = nobody
        server          = /usr/bin/Xvnc
        server_args     = -SecurityTypes None -inetd -once -query localhost -geometry 1024x768 -depth 16
        type            = UNLISTED
        port            = 5901
}
Comment 11 Zsolt Sági 2008-09-04 11:30:48 UTC
I also send an output listing of the gdb output:

tamas@milleniumfalcon:~> gdb /opt/kde3/bin/krdc
GNU gdb 6.8
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "i586-suse-linux"...
(no debugging symbols found)
(gdb) run
Starting program: /opt/kde3/bin/krdc
(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 0xb6bc7b50 (LWP 26020)]
*** WARNING *** The program 'krdc' uses the Apple Bonjour compatibility layer of Avahi.
*** WARNING *** Please fix your application to use the native API of Avahi!
*** WARNING *** For more information see <http://0pointer.de/avahi-compat?s=libdns_sd&e=krdc>
[New Thread 0xb6929b90 (LWP 26023)]
[New Thread 0xb6128b90 (LWP 26024)]
[New Thread 0xb5927b90 (LWP 26025)]
[New Thread 0xb50e8b90 (LWP 26027)]
[New Thread 0xb48e7b90 (LWP 26030)]
[New Thread 0xb40e6b90 (LWP 26032)]
[New Thread 0xb38e5b90 (LWP 26033)]
[Thread 0xb5927b90 (LWP 26025) exited]
[Thread 0xb48e7b90 (LWP 26030) exited]
[Thread 0xb50e8b90 (LWP 26027) exited]
[Thread 0xb38e5b90 (LWP 26033) exited]
[Thread 0xb40e6b90 (LWP 26032) exited]
[Thread 0xb6128b90 (LWP 26024) exited]
[Thread 0xb6929b90 (LWP 26023) exited]
[New Thread 0xb6929b90 (LWP 26034)]
VNC server supports protocol version 3.8 (viewer 3.3)
No authentication needed
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 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
[New Thread 0xb6128b90 (LWP 26035)]
krdc: xcb_lock.c:33: _XCBUnlockDisplay: Assertion `xcb_get_request_sent(dpy->xcb->connection) == dpy->request' failed.

Program received signal SIGABRT, Aborted.
[Switching to Thread 0xb6bc7b50 (LWP 26020)]
0xffffe430 in __kernel_vsyscall ()
(gdb) bt
#0  0xffffe430 in __kernel_vsyscall ()
#1  0xb6fe7900 in raise () from /lib/libc.so.6
#2  0xb6fe9238 in abort () from /lib/libc.so.6
#3  0xb6fe070e in __assert_fail () from /lib/libc.so.6
#4  0xb723480e in _XCBUnlockDisplay (dpy=0x80b0238) at xcb_lock.c:33
#5  0xb733284e in XShmPutImage () from /usr/lib/libXext.so.6
#6  0x0807dcfd in ?? ()
#7  0x08074b6d in ?? ()
#8  0x08074db7 in ?? ()
#9  0xb75ee8f6 in QObject::event () from /usr/lib/qt3/lib/libqt-mt.so.3
#10 0xb76291fc in QWidget::event () from /usr/lib/qt3/lib/libqt-mt.so.3
#11 0xb75893cd in QApplication::internalNotify () from /usr/lib/qt3/lib/libqt-mt.so.3
#12 0xb758a37d in QApplication::notify () from /usr/lib/qt3/lib/libqt-mt.so.3
#13 0xb7c78892 in KApplication::notify () from /opt/kde3/lib/libkdecore.so.4
#14 0xb758b4ea in QApplication::sendPostedEvents () from /usr/lib/qt3/lib/libqt-mt.so.3
#15 0xb758b646 in QApplication::sendPostedEvents () from /usr/lib/qt3/lib/libqt-mt.so.3
#16 0xb7533c75 in QEventLoop::processEvents () from /usr/lib/qt3/lib/libqt-mt.so.3
#17 0xb75a1d10 in QEventLoop::enterLoop () from /usr/lib/qt3/lib/libqt-mt.so.3
#18 0xb75a1ba6 in QEventLoop::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#19 0xb7589a5f in QApplication::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#20 0x0807050f in ?? ()
#21 0xb6fd35f5 in __libc_start_main () from /lib/libc.so.6
#22 0x08058d71 in ?? ()
(gdb) quit
The program is running.  Exit anyway? (y or n) y
tamas@milleniumfalcon:~>
Comment 12 Zsolt Sági 2008-09-04 11:32:25 UTC
Created attachment 237493 [details]
Typical view of a broken krdc window
Comment 13 Michael McCarthy 2008-10-09 14:34:41 UTC
On all of my openSUSE 11.0 systems krdc3 crashes as previously mentioned when connecting to an SLES 10 remote server.  krdc4 on 11.0 and krdc3 on 10.3 works properly.  krdc3 also seems to work properly when connecting to localhost and to 10.3 systems.  This really needs to get fixed as it makes it difficult to manage my SLES 10 servers.

Here is a dump:

System configuration startup check disabled.

[?1034h(no debugging symbols found)
(no debugging symbols found)
...
Thread debugging using libthread_db enabled]
[New Thread 0xb6baab50 (LWP 6687)]
[New Thread 0xb56c9b90 (LWP 6700)]
[New Thread 0xb5ecab90 (LWP 6699)]
(no debugging symbols found)
...
[KCrash handler]
#6  0xffffe430 in __kernel_vsyscall ()
#7  0xb6fca900 in raise () from /lib/libc.so.6
#8  0xb6fcc238 in abort () from /lib/libc.so.6
#9  0xb6fc370e in __assert_fail () from /lib/libc.so.6
#10 0xb721780e in ?? () from /usr/lib/libX11.so.6
#11 0xb731584e in XShmPutImage () from /usr/lib/libXext.so.6
#12 0x0807dcfd in ?? ()
#13 0x08074b6d in ?? ()
#14 0x08074db7 in ?? ()
#15 0xb75d18f6 in QObject::event () from /usr/lib/qt3/lib/libqt-mt.so.3
#16 0xb760c1fc in QWidget::event () from /usr/lib/qt3/lib/libqt-mt.so.3
#17 0xb756c3cd in QApplication::internalNotify ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#18 0xb756d37d in QApplication::notify () from /usr/lib/qt3/lib/libqt-mt.so.3
#19 0xb7c5b892 in KApplication::notify () from /opt/kde3/lib/libkdecore.so.4
#20 0xb756e4ea in QApplication::sendPostedEvents ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#21 0xb756e646 in QApplication::sendPostedEvents ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#22 0xb7516b5d in QEventLoop::processEvents ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#23 0xb7584d10 in QEventLoop::enterLoop () from /usr/lib/qt3/lib/libqt-mt.so.3
#24 0xb7584ba6 in QEventLoop::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#25 0xb756ca5f in QApplication::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#26 0x0807050f in ?? ()
#27 0xb6fb65f5 in __libc_start_main () from /lib/libc.so.6
#28 0x08058d71 in ?? ()

Comment 14 Forgotten User bSWU20Bh6O 2009-05-14 19:53:02 UTC
At this point there is no point in fixing KDE3 bugs like this if there is an alternative in KDE4.