xterm not running in vnc session since tightvnc-1.3.10_6 / freebsd 13.2-RELEASE-p4 (32 bit)

D

dummy_01

Hi all,

after upgrading to 13.2-RELEASE-p4 (32 bit) my vnc client can still open a session and shows a twm window, but it doesn't show an xterm anymore and I can't start xterm from context menu as well (no error message, just nothing happens). There was definitely no configuration change and it was working before upgrading.

My reference system (same hardware except disk) is running 13.2-RELEASE-p3 (32 bit) and here it still works as expected.

The vnc server log tells me:
09/11/23 15:28:34 Using image quality level 8 for client <my_ip_number (replaced)>
X Error of failed request: BadAlloc (insufficient resources for operation)
Major opcode of failed request: 45 (X_OpenFont)
Serial number of failed request: 54
Current serial number in output stream: 55

I didn't find much useful for this, but I ran "mkfontdir" and "mkfontscale" inside ~/.vnc, but this didn't change anything.

Xterm itself has no issues, I can run it outside vnc with an exported display.

Any idea someone? What else do you need to narrow down the issue?

Thanks a lot.
Best regards,
Dummy_01
 
I have the same problem. The problem occurred after I installed quite a few updates yesterday. This is a production machine which I can't reboot every day. The Xserver is started via Xvfb. There I managed to somehow get a session running. xfce-terminal works. But X has some other quirks like the key repeat not working, need to do run xset r on and xset r rate 240 24 manually every time I vnc into the session. I did run mkfontdir and mkfontscale too. But no change. I use fluxbox as window manager.

I use x11vnc attaching to a Xvfb:

Code: 
xinit -f $HOME/.Xauthority -- /usr/local/bin/Xvfb :0 -screen 0 800x600x16 -dpi 75 -nolisten tcp -audit 4 -ac -auth $HOME/.Xauthority 2>>$HOME/.vnc/xvfb.log 1>&2 &
x11vnc -display :0 -nowf -xkb -rfbport 5901 -rfbauth &

Any ideas?

Code: 
$ xterm -display :2
X Error of failed request:  BadAlloc (insufficient resources for operation)
  Major opcode of failed request:  45 (X_OpenFont)
  Serial number of failed request:  61
  Current serial number in output stream:  62

$ xfontsel -display :2
Warning: Missing charsets in String to FontSet conversion
Warning: Unable to load any usable fontset
 
I followed cracauer@'s hint and switched to tigervnc, which is clearly slower and lagging like hell, but working without issues. Not really a solution, but a workaround at least ...

Thanks.
 
Same issue with tightvnc and FreeBSD 13.2-STABLE - xterm dies with "BadAlloc (insufficient resources for operation)" when started from the .vnc/xstartup file which is:

Code: 
#!/bin/sh
xrdb $HOME/.Xresources
xsetroot -solid grey
# start some nice programs
xclock -digital -geometry -1+1 -update 1 -title shadow &
xterm -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" &
twm

The curious thing is that all other X applications can be opened without issue (eg xcalc, xclock, emacs etc) which got me thinking... so I tried uxterm... but the same problem, next I tried roxterm... success.

So now my .vnc/xstartup file is:

Code: 
#!/bin/sh
xrdb $HOME/.Xresources
xsetroot -solid grey
# start some nice programs
xclock -digital -geometry -1+1 -update 1 -title shadow &
roxterm --geometry=80x30 -T "$VNCDESKTOP Desktop" &
twm

and harmony has returned for the moment.

[Edit: FreeBSD 64 bit, tightvnc-1.3.10_9]
 
You must log in or register to reply here.
Back
Top