Red Hat Bugzilla – Bug 123255
vncviewer Segmentation fault
Last modified: 2007-11-30 17:10:42 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.1)
Description of problem:
vncviewer crashes all the time. never got it to work. It doesn't
matter what version of vncserver I try to connect to. Connecting to
my rh9 system running vnc-server-3.3.3r2-47 crashes vncviewer. So I
thought it could be a version problem, but connecting to a fedora core
1 vnc-server-4.0-0.beta4.3.2 system also crashes vncviewer.
Here's an example:
[son@localhost son]$ vncviewer localhost:1
VNC viewer for X version 4.0b4 - built Nov 17 2003 13:17:08
Copyright (C) 2002-2003 RealVNC Ltd.
See http://www.realvnc.com for information on VNC.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
2. vncviewer localhost:1
step 2 assumes vncserver is running on display 1. change it
Please install vnc-debuginfo-4.0-0.beta4.3.2:
and run vncviewer like this:
gdb --args vncviewer localhost:1
and tell me what it says.
Created attachment 100904 [details]
Output from gdb --args vncviewer localhost:1
This is the result of running gdb --args vncviewer localhost:1 on my system:
Dual PIII 550, 512MB, scsi, 2.4.22-1.2188.nptlsmp smp, XFree86 4.3.0-55, ATI
Okay, I installed the source, too. It seems to crap out on line 73/4
On the next line, the returned value is used as a pointer,
defaultFont = defaultFS -> fid;
but defaultFS is NULL, hence the crash. So for some reason, I don't
have "-*-helvetica-medium-r-*-*-12-*-*-*-*-*-*-*" on my system. I can
provide a list of the font packages I've installed, if required. I
assume the fix is to use a font that does exist, but I know nowt about
X font programming, so I'll have to look this one up. Over to you guys?
What does '/sbin/chkconfig --list xfs' say?
Yes, the fix will be to fall back to something else, but I'd like to
be sure about the reason the first choice isn't working.
Created attachment 100949 [details]
Output of chkconfig --list xfs + others
I've put the output of the command requested in the attachment, along with some
other info that may be useful.
So according to xlsfonts the font request ought to have been granted,
since you have fonts that match!
So it's still a bit of a mystery that it failed in the first place.
But besides, I have seen situations in which that particular font
pattern can't be provided, so perhaps it should fall back to 'fixed'.
*** Bug 131357 has been marked as a duplicate of this bug. ***
I have exactly the same problem. But additional info.
It used to work a few months ago. I constantly update
packages I think important using yum or up2date.
=> Some update breaks some font aspect?
I can still connect to my server from windows-client.
And if I then start vncviewer from there ... It works!
Running vncviewer when the X-environment is vncserver
appears to work!
Running fc2 with updates on my server and workstation.
Both behave the same. Machine is P4 (i686)
Please try the test update for FC2 announced here:
Does that fix the problem?
I had exactly the same segfault after I upgraded xorg to
xorg-x11-18.104.22.1683, and it is solved by the update which works
for me. I have apentium III.
Looks good with vnc-4.0-5, thanks a bunch.