Bugzilla – Bug 156503
starting xterm not possible
Last modified: 2006-03-10 07:29:03 UTC
using window manager openbox: starting "xterm" causes following error: evo:~ # xterm xterm: unable to open font "-adobe-courier-bold-r-normal--12-140-75-75-m-90-iso8859-1", trying "fixed".... X Error of failed request: BadWindow (invalid Window parameter) Major opcode of failed request: 18 (X_ChangeProperty) Resource id in failed request: 0x0 Serial number of failed request: 130 Current serial number in output stream: 131 Starting "xterm" with font parameter works fine: evo:~ # xterm -fn fixed I'm wondering why '... trying "fixed"' seams not to really try "fixed"
Looks like a bug in the openbox menu. At least I don't see such a font in my xlsfonts output.
the default xterm entry in the openbox menu is just "xterm" no font or anything given. Are you sure it isnt your .Xdefaults?
As you saw: starting xterm within a normal shell causes the problem as well. I tested it as root, a new created user and with my NIC account -> same problem
Probably, what's the output of "xrdb -query|grep -i font"
evo:~ # xrdb -query|grep -i font XSysinfo*.font: fixed xterm*font: -adobe-courier-bold-r-normal--12-140-75-75-m-90-iso8859-1
Nice try, but for sure this is not *our* default. :-) ~holgi/.Xdefaults: [...] xterm*font: -adobe-courier-bold-r-normal--12-140-75-75-m-90-iso8859-1
OK, catched me with my pants down. <:-) I did not realize that I'm using the same X environment when using a different user within 'my' X session. Sorry for the noise.