LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Software
User Name
Password
Linux - Software This forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.

Notices


Reply
  Search this Thread
Old 04-01-2003, 08:24 AM   #1
bphinney
LQ Newbie
 
Registered: Apr 2003
Distribution: Mandrake 9.1
Posts: 5

Rep: Reputation: 0
Mandrake 9.1, TightVNC and KDE 3.1


I am getting errors trying to run KDE as a desktop manager from a TightVNC session. TightVNC is being tunnelled through SSH and I can run Gnome and TWM but get major errors and non-functioning apps when I try to run KDE. Sorry for the long post but I wanted to include the xsessions log to help with this. Anyone have any ideas before I just blow the system away and reinstall everything?


I have included a copy of the xsession errors log:

Error while reading Indicator status
startkde: Starting up...
Xlib: extension "GLX" missing on display ":1.0".
...
kbuildsycoca running...
...
Server has no DPMS extension
...
mcop warning: user defined signal handler found for SIG_PIPE, overriding
...
mcop warning: user defined signal handler found for SIG_PIPE, overriding
...
*** kdesktop (2895) got signal 11
...
WARNING: KDE detected X Error: BadDrawable (invalid Pixmap or Window parameter) \x09
Major opcode: \x0e
kicker: crashHandler called
DCOP aborting call from 'anonymous-2898' to 'kicker'
ERROR: KUniqueApplication: DCOP communication error!
...
mcop warning: user defined signal handler found for SIG_PIPE, overriding
Xlib: extension "RENDER" missing on display ":1.0".
*** KGet got signal 11
DCOP aborting (delayed) call from 'anonymous-2917' to 'kget'
ERROR: KUniqueApplication: DCOP communication error!
Xlib: extension "RENDER" missing on display ":1.0".
WARNING: KDE detected X Error: BadDrawable (invalid Pixmap or Window parameter) \x09
Major opcode: \x0e
DCOP aborting call from 'anonymous-2923' to 'kicker'
ERROR: KUniqueApplication: DCOP communication error!
*** kdesktop (2907) got signal 11
...
mcop warning: user defined signal handler found for SIG_PIPE, overriding
*** kdesktop (2936) got signal 11
...
mcop warning: user defined signal handler found for SIG_PIPE, overriding
*** kdesktop (2942) got signal 11
...
mcop warning: user defined signal handler found for SIG_PIPE, overriding
*** kdesktop (2948) got signal 11
...
mcop warning: user defined signal handler found for SIG_PIPE, overriding......
blah, blah, blah

much more fo the same....

Last edited by bphinney; 04-01-2003 at 04:44 PM.
 
Old 04-01-2003, 02:38 PM   #2
bahamat
Member
 
Registered: Mar 2003
Distribution: Debian
Posts: 158

Rep: Reputation: 30
Um, we probaly could have done fine with only one glx error line.

Now let me hit you with a big fat cluebat.
the problem is GLX.
 
Old 04-01-2003, 02:56 PM   #3
RVK
Member
 
Registered: Mar 2003
Distribution: Mandrake 9.1
Posts: 42

Rep: Reputation: 15
Yup, GLX.....

I'd say that's the culprit.

I believe GLX has something to do with OpenGL hardware. Go to rpmfind.net and search for GLX. Hopefully that will solve your issue.

-R
 
Old 04-01-2003, 04:42 PM   #4
bphinney
LQ Newbie
 
Registered: Apr 2003
Distribution: Mandrake 9.1
Posts: 5

Original Poster
Rep: Reputation: 0
Well, I guess what is throwing me is that I see the same GLX error when loading Gnome but the desktop still comes up with Gnome. I have an Nvidia Geforce 4 ti 4600 and I am running the Nvidia drivers but even when I remove those drivers and go back to the default nv drivers that come with Xfree, I still get the exact same error messages. Also, if I use the default nv drivers and comment out GLX from my XF config file, I still get the same errors and can not load KDE from a VNC session. KDE loads just fine on the main display.

I was running the same video card with the same drivers using Mandrake 9.0 and was not having problems loading KDE prior to upgrading to the 9.1 package.

I will take a look at Rpmfind.net and see what I can find about the GLX error.
 
Old 04-03-2003, 07:28 PM   #5
bphinney
LQ Newbie
 
Registered: Apr 2003
Distribution: Mandrake 9.1
Posts: 5

Original Poster
Rep: Reputation: 0
Follow-up

Just in case anyone runs across this message and is searching for a real answer, not the boneheaded comments that I did get, the problem is with the anti-aliased fonts that were introduced in the 9.1 distribution of Mandrake. Anti-aliased fonts require render support from whatever display device is being used and VNC, as well as most other virtual displays lack this support. GLX is not the issue, it is the fonts in the default mandrake distribution. The texstar site offers an updated QT3 library that replaces the AA fonts with non AA fonts and this will fix the display problem with VNC. However, it will also degrade the fonts on the normal display.

I would like to thank the other members of the Linux community that actually tried to help me and pointed me to the answer rather than attempting to blow their own horns by making unnecessary and, as it turns out, wrong-headed comments. Next time someone asks a question, some people might want to stick that big fat cluebat in their own mouths until they actually know the answer.

Last edited by bphinney; 04-03-2003 at 07:30 PM.
 
Old 04-04-2003, 02:31 AM   #6
acid_kewpie
Moderator
 
Registered: Jun 2001
Location: UK
Distribution: Gentoo, RHEL, Fedora, Centos
Posts: 43,417

Rep: Reputation: 1974Reputation: 1974Reputation: 1974Reputation: 1974Reputation: 1974Reputation: 1974Reputation: 1974Reputation: 1974Reputation: 1974Reputation: 1974Reputation: 1974
Have you always been that stuck up or have you just got that good through practise?
 
Old 04-04-2003, 07:02 AM   #7
bphinney
LQ Newbie
 
Registered: Apr 2003
Distribution: Mandrake 9.1
Posts: 5

Original Poster
Rep: Reputation: 0
???????

Who's stuck-up? I asked a question and at the very least, if no one knew the answer, I could have been greeted with silence.

Ahh, screw it anyway, I have my answer and if I have problems, I know where to go to try to get help.
 
Old 05-22-2003, 10:30 AM   #8
joerod
LQ Newbie
 
Registered: May 2003
Location: Sharon, Pa
Posts: 1

Rep: Reputation: 0
yea, bphinney i think you were a little wronged there. the cluebat thing was alittle funny tho.

anyway, i have a similiar problem with mdk9.1 and vncserver 3. nothing shows up except for the desktop; and i get an error message that says:

could not start process
unable to create io-slave
too many files open

the solution isn't obivious because there really isn't anything running. maybe it could be a font thing; but I doubt it. I'm gonna give that a shot, thanks; but if there is anything else anyone knows about I'd appreciate it.
 
Old 05-30-2003, 09:19 AM   #9
hir0
LQ Newbie
 
Registered: May 2003
Posts: 1

Rep: Reputation: 0
I'm having the same problem. Worked fine under Mandrake 9.0 from my Win32 machines, now I get the exact error message/scenarion below. When i first connect it seems to be fine, times out for a bit and finally produces the error message indicated. This appears to bne the case in KDE or Gnome.

Quote:
Originally posted by joerod
yea, bphinney i think you were a little wronged there. the cluebat thing was alittle funny tho.

anyway, i have a similiar problem with mdk9.1 and vncserver 3. nothing shows up except for the desktop; and i get an error message that says:

could not start process
unable to create io-slave
too many files open

the solution isn't obivious because there really isn't anything running. maybe it could be a font thing; but I doubt it. I'm gonna give that a shot, thanks; but if there is anything else anyone knows about I'd appreciate it.
 
Old 06-05-2003, 09:22 PM   #10
hotyopa
LQ Newbie
 
Registered: Jun 2003
Posts: 1

Rep: Reputation: 0
I found the answer here:

It is a bug in libqt-3.1 that was exposed when AA was compiled in. Get
Texstar's libqt-3.1-14 and this will allow you to use vnc, but it will
degrade your fonts slightly on the local display. It affects all displays
that do not support render, this includes vnc, Xnest, xforbserver,
XFree-3.3.6 and older video cards.

Texstar's libqt3 rpms can be found here

Last edited by hotyopa; 06-05-2003 at 10:24 PM.
 
Old 06-26-2003, 04:35 AM   #11
GoDan
LQ Newbie
 
Registered: Jun 2003
Posts: 1

Rep: Reputation: 0
Hi,
I have same problem (KDE not start).

I downloaded libqt3-3.1.2-8tex.i586.rpm and libqt3-common-3.1.2-8tex.i586.rpm.

I tried to install/upgrade/refresh:

rpm -F libqt3-3.1.2-8tex.i586.rpm libqt3-common-3.1.2-8tex.i586.rpm

but I get some dependecies errors and the install stops.
How can I install the new rpms?

Thanks.
 
Old 06-26-2003, 11:16 AM   #12
kip
LQ Newbie
 
Registered: Jun 2003
Posts: 2

Rep: Reputation: 0
-GoDan

I have not tried this yet, but here is a link to the -14 libqt rpms http://ftp.ibiblio.org/pub/Linux/dis...ndrake/vncfix/

It looks like you were trying to install the -8.

HTH
 
Old 06-29-2003, 07:36 PM   #13
mhchavez99
LQ Newbie
 
Registered: Jun 2003
Location: Lawrence, KS
Distribution: Mandrake9.1
Posts: 18

Rep: Reputation: 0
Quote:
Originally posted by GoDan
Hi,
I have same problem (KDE not start).

I downloaded libqt3-3.1.2-8tex.i586.rpm and libqt3-common-3.1.2-8tex.i586.rpm.

I tried to install/upgrade/refresh:

rpm -F libqt3-3.1.2-8tex.i586.rpm libqt3-common-3.1.2-8tex.i586.rpm

but I get some dependecies errors and the install stops.
How can I install the new rpms?

Thanks.
These dependencies can be ignored just use the command

rpm -ivh --nodeps --force libqt3-common-3.1.2-8tex.i586.rpm libqt3-3.1.2-8tex.i586.rpm

It worked for me, gook luck!
 
Old 06-29-2003, 08:19 PM   #14
kip
LQ Newbie
 
Registered: Jun 2003
Posts: 2

Rep: Reputation: 0
I installed the "-14" libqt-3.1.1-14

( libqt3-3.1.1-14tex.i586.rpm, libqt3-common-3.1.1-14tex.i586.rpm, libqt3-devel-3.1.1-14tex.i586.rpm)

from texstar and vnc works but text and images in KDE are not showing up correctly. Some of this is corrected by mousing over the objects, but overall it is bad enough I cannot use it from a remote machine. KDE works fine on the local machine of course.

I am certainly a newbie, so this could be just falty config.

Is anyone else experiencing this with the newer vncfixes?

Is this to be expected with the AA patch backed out?

This is a mdk 9.1 install. I can give more config info if that helps.

Thanks.
 
Old 06-30-2003, 10:40 PM   #15
mhchavez99
LQ Newbie
 
Registered: Jun 2003
Location: Lawrence, KS
Distribution: Mandrake9.1
Posts: 18

Rep: Reputation: 0
Yes the "-14" should be fine the significant part is the "--nodeps --force". The filenames should match what you have.

Last edited by mhchavez99; 06-30-2003 at 10:47 PM.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
TightVNC trouble on Mandrake 10.1 shea1roh Mandriva 16 11-24-2004 10:17 AM
Unable to connect to TightVNC on Mandrake 10 kt8993 Linux - Networking 3 09-30-2004 11:36 AM
start tightVNC server on mandrake 10.0 pelgrimforever Linux - Newbie 2 09-15-2004 05:43 AM
Mandrake 9.2, Windows XP and TightVNC Dave Tarmac Linux - Newbie 1 01-05-2004 10:19 PM
Mandrake 9.2/tightvnc server problem DirtDart Linux - Software 1 11-13-2003 05:08 AM


All times are GMT -5. The time now is 06:23 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration