Version: 3.1.1 (using KDE KDE 3.1) Installed from: Mandrake RPMs OS: Linux I've installed mandrake RC2. qt 3.1.1 kde 3.1 When I run apps locally they run fine. When I use a remote xserver (xwin32 5.4 on Windows XP) application crashes immetiately (I see a windows that opens for an istant then closes, then another windows opens and suddently disappear) No error are displayed (even if I think that second window is an error message report) except for "Mutex destroy failure: Device or resource busy" after few seconds. A core file is generated I've tried deleting /tmp dir, removing all home dir hidden files, killing all qt-related apps without any improvement root 15641 0.7 4.1 20040 7968 ? S 05:44 0:00 kdeinit: Running. root 15644 0.8 4.3 20424 8408 ? S 05:44 0:00 kdeinit: dcopserv root 15647 1.1 4.6 20456 8832 ? S 05:44 0:00 kdeinit: klaunche root 15649 16.3 6.2 22380 11976 ? S 05:44 0:00 kdeinit: kded after application crashes, and disappear after a while All other X applications run fines, I have only problem with k* application (so I think It's a QT problem) I've used mandrake 8.2 for over a year, and all kde app runned fine on my WinXP remote server. any clue?
I've just tried un another pc of my lan with another Windows xserver (exceed). Same problem.
Today I've installed Mandrake 9.1 final and the problem is still here This is the output rinning startkde: [root@server root]# startkde XIO: fatal IO error 104 (Connection reset by peer) on X server "192.168.0.100:0.0" after 0 requests (0 known processed) with 0 events remaining. xset: bad font path element (#36), possible causes are: Directory does not exist or has wrong permissions Directory missing fonts.dir Incorrect font server address or syntax xset: bad font path element (#36), possible causes are: Directory does not exist or has wrong permissions Directory missing fonts.dir Incorrect font server address or syntax startkde: Starting up... kbuildsycoca running... Xlib: extension "RENDER" missing on display "192.168.0.100:0.0". Server has no DPMS extension ERROR: X server has not matching XKB extension mcop warning: user defined signal handler found for SIG_PIPE, overriding Xlib: extension "RENDER" missing on display "192.168.0.100:0.0". Xlib: extension "RENDER" missing on display "192.168.0.100:0.0". kicker: crashHandler called Xlib: extension "RENDER" missing on display "192.168.0.100:0.0". Xlib: extension "RENDER" missing on display "192.168.0.100:0.0". Xlib: extension "RENDER" missing on display "192.168.0.100:0.0". Xlib: extension "RENDER" missing on display "192.168.0.100:0.0". WARNING: KDE detected X Error: BadDrawable (invalid Pixmap or Window parameter) \x09 Major opcode: \x0e WARNING: KDE detected X Error: BadDrawable (invalid Pixmap or Window parameter) \x09 Major opcode: \x0e DCOP aborting call from 'anonymous-11806' to 'kicker' ERROR: KUniqueApplication: DCOP communication error! Xlib: extension "RENDER" missing on display "192.168.0.100:0.0". QMetaObject::findSignal:KOTodoListView: Conflict with KListView::doubleClicked (QListViewItem*,const QPoint&,int) Xlib: extension "RENDER" missing on display "192.168.0.100:0.0". QMetaObject::findSignal:KOAgendaView: Conflict with KOEventView::editEventSignal (Event*) QMetaObject::findSignal:KOAgendaView: Conflict with KOEventView::showEventSignal (Event*) QMetaObject::findSignal:KOAgendaView: Conflict with KOEventView::deleteEventSignal(Event*) QMetaObject::findSignal:KOAgendaView: Conflict with KOEventView::editEventSignal (Event*) QMetaObject::findSignal:KOAgendaView: Conflict with KOEventView::showEventSignal (Event*) QMetaObject::findSignal:KOAgendaView: Conflict with KOEventView::deleteEventSignal(Event*) QMetaObject::findSignal:KOAgendaView: Conflict with KOEventView::editEventSignal (Event*) QMetaObject::findSignal:KOAgendaView: Conflict with KOEventView::editEventSignal (Event*) QMetaObject::findSignal:KOAgendaView: Conflict with KOEventView::showEventSignal (Event*) QMetaObject::findSignal:KOAgendaView: Conflict with KOEventView::showEventSignal (Event*) QMetaObject::findSignal:KOAgendaView: Conflict with KOEventView::deleteEventSignal(Event*) QMetaObject::findSignal:KOAgendaView: Conflict with KOEventView::deleteEventSignal(Event*) QMetaObject::findSignal:KOAgendaView: Conflict with KOEventView::newEventSignal (QDateTime) QMetaObject::findSignal:KOAgendaView: Conflict with KOEventView::newEventSignal (QDateTime,QDateTime) QMetaObject::findSignal:KOAgendaView: Conflict with KOEventView::editEventSignal (Event*) QMetaObject::findSignal:KOAgendaView: Conflict with KOEventView::showEventSignal (Event*) QMetaObject::findSignal:KOAgendaView: Conflict with KOEventView::deleteEventSignal(Event*) DCOP aborting call from 'anonymous-11827' to 'korganizer' DCOP aborting call from 'anonymous-11831' to 'korganizer' ERROR: KUniqueApplication: DCOP communication error! ERROR: KUniqueApplication: DCOP communication error! ksmserver: Fatal IO error: client killed ICE default IO error handler doing an exit(), pid = 11812, errno = 0 ICE default IO error handler doing an exit(), pid = 11829, errno = 0 ICE default IO error handler doing an exit(), pid = 11808, errno = 0 startkde: Shutting down... KLauncher: Exiting on signal 1 klauncher: Fatal IO error: client killed startkde: Running shutdown scripts... startkde: Done.
I've tried with a local VNC server. Same behavior. ALL KDE app crashes. The second windows that appears is krashhandler, but it's a k-apps so it crashes. If I add --nocrashhandler second windows not appears. (and a "segmentation fault" appears) Mandrake people said it's my x server that not support RENDER extension for antialiased fonts. I've just tried konsole --noxft, but still crash immediately. If I start a kapps from gnome, I can see the window title and windows border correcly for about half second. There is some that can tell me "this work for me, it's your configuration problem"? This is a CRITICAL feature.
I'm seeing a similar problem on Solaris 2.8, using tightvnc
IIRC, this is a Mandrake packaging bug. Please try rebuilding Qt packages with the following (utterly nonsense) path removed: http://cvs.mandrakesoft.com/cgi-bin/cvsweb.cgi/SPECS/qt3/qt-3.1-use-aa-by-default.patch?rev=1.1&content-type=text/x-cvsweb-markup (Or just build from source)
Yes, but this also fails on solaris 2.8. I compiled using qt 3.1.2, with render and xft turned off.
To Albert L. Ting: You are probably seeing a different bug entirely, which just happens to have similar symptoms. I am about 99.9% sure that it's the Mandrake patch that's causing problems for the original reporter, as if I am reading it right, it's forcing Qt to use render even if it doesn't detect it, or have it enabled. Do you have a useful backtrace?
Not sure how to do a backtrace, but I'll include an attachment the kde log. It fails near the end, when it tries to setup the Desktop. I should say some caveats. kde does not compile completely in Solaris 2.8 and have had to remove various modules. This worked fine with kde 2.2.2. Modules I skipped were: kdeadmin: kuser kdebindings: qsharp kdenetwork: kppp krdc krfb kmultimedia: mpeglib, mpeglib_plugin koffice: kivio
Created attachment 1830 [details] sample kde wm log
This problem goes away if I use the latest tightvnc (1.2.9) or the latest realvnc.
Log in #9 suggests that X-server kills the client, probably bug in X-server. Closing bugreport since newer versions of vnc clients fix it.
Repeating myself: Closing bugreport since newer versions of vnc clients fix it.