Opened 3 years ago

Closed 3 years ago

#10492 closed enhancement (fixed)

twm-1.0.10

Reported by: bdubbs@… Owned by: Bruce Dubbs
Priority: normal Milestone: 8.3
Component: BOOK Version: SVN
Severity: normal Keywords:
Cc:

Description

New point version.

Change History (13)

comment:1 by thomas, 3 years ago

Just tried to use it as a drop-in upgrade. Failed as the window titlebars disappeared. Downgrading to 1.0.9 brought them back again.

So i think instructions/configuration needs to be reviewed.

comment:2 by bdubbs@…, 3 years ago

Owner: changed from blfs-book@… to blfs-book

comment:3 by Bruce Dubbs, 3 years ago

Owner: changed from blfs-book to Bruce Dubbs
Status: newassigned

Time to go back to work. Will start with xorg, but will not to ati/amd video drivers or libwacom.

comment:4 by Bruce Dubbs, 3 years ago

Resolution: fixed
Status: assignedclosed

Fixed at revision 19947.

comment:5 by Pierre Labastie, 3 years ago

Resolution: fixed
Status: closedreopened

Reopened the ticket, since I have the same issue as Thomas: no title bars...

And also no menu when clicking in an empty region of the screen.

comment:6 by Pierre Labastie, 3 years ago

Same as Thomas, downgrading to 1.0.9 brings windows title bars back.

Did some comparisons: the twmrc files are identical for both version. The binaries /usr:bin/twm differ, of course.

comment:7 by Bruce Dubbs, 3 years ago

I didn't check title bars, but menu when clocking on the empty region of the screen worked for me.

in reply to:  7 comment:8 by Pierre Labastie, 3 years ago

Replying to bdubbs:

I didn't check title bars, but menu when clocking on the empty region of the screen worked for me.

Well, title bars are there or not. If you did not notice anything, they were there as usual ...

Are you using still a non UTF-8 locale? AH, that's it: using LANG=C startx, I get the title bars!

I guess Thomas uses de_DE.UTF-8... And I use fr_FR.UTF-8. Could you try LANG=en_US.UTF-8 startx?

So it must be a parsing problem: when doing a diff between build trees, it looks like some bison/flex generated files have been modified.

comment:9 by Bruce Dubbs, 3 years ago

I use LANG=en_US.UTF-8 by default now. I did try 'export LANG=C; startx twm'

In either case the xterm and xclock title bars were present. I have no problem with the menu on the screen for exit. etc.

I'll add that I build the xorg legacy fonts and some others to keep twm from complaining:

cc0726e4a277d6ed93b8e09c1f195470  font-arabic-misc-1.0.3.tar.bz2
3e0069d4f178a399cffe56daa95c2b63  font-cursor-misc-1.0.3.tar.bz2
6e7c5108f1b16d7a1c7b2c9760edd6e5  font-dec-misc-1.0.3.tar.bz2
143c228286fe9c920ab60e47c1b60b67  font-micro-misc-1.0.3.tar.bz2
96109d0890ad2b6b0e948525ebb0aba8  font-misc-cyrillic-1.0.3.tar.bz2
e3e7b0fda650adc7eb6964ff3c486b1c  font-misc-meltho-1.0.3.tar.bz2
c88eb44b3b903d79fb44b860a213e623  font-misc-misc-1.1.2.tar.bz2
56b0296e8862fc1df5cdbb4efe604e86  font-mutt-misc-1.0.3.tar.bz2
e805feb7c4f20e6bfb1118d19d972219  font-schumacher-misc-1.1.2.tar.bz2
beef61a9b0762aba8af7b736bb961f86  font-sony-misc-1.0.3.tar.bz2
948f2e07810b4f31195185921470f68d  font-sun-misc-1.0.3.tar.bz2
Last edited 3 years ago by Bruce Dubbs (previous) (diff)

comment:10 by Pierre Labastie, 3 years ago

I've built legacy too (not the other fonts). But shouldn't be the problem, since I get the title bars when using LANG=C. Note that If I use "LANG=en_US.UTF-8 startx", there are no title bars, and the menu fails as well.

One direction for digging: do you use the UTF-8 locale while building too?

Oh, and another question: what is your version of the Xorg server? Mine is 1.19.6. I see some weird messages about fonts when starting X:

[    13.927] (==) FontPath set to:
        ${prefix}/share/fonts/X11/misc/,
        ${prefix}/share/fonts/X11/TTF/,
        ${prefix}/share/fonts/X11/OTF/,
        ${prefix}/share/fonts/X11/Type1/,
        ${prefix}/share/fonts/X11/100dpi/,
        ${prefix}/share/fonts/X11/75dpi/

But nothing tells what the value of prefix is. There are messages of the type:

_FontTransOpen: Unable to Parse Address ${prefix}/share/fonts/X11/misc/

And there is also a message:

twm: unable to open fontset "-adobe-helvetica-bold-r-normal--*-120-*-*-*-*-*-*"

The last message does not appear if using LANG=C.

FWIW, I've installed Xorg in /usr.

comment:11 by Bruce Dubbs, 3 years ago

I do use en_US.utf8 (not en_US.UTF-8) for building but I don't think that makes a difference.

X.Org X Server 1.19.6
...
[ 82365.571] (==) FontPath set to:
   /opt/xorg/share/fonts/X11/misc/,
   /opt/xorg/share/fonts/X11/TTF/,
   /opt/xorg/share/fonts/X11/OTF/,
   /opt/xorg/share/fonts/X11/Type1/,
   /opt/xorg/share/fonts/X11/100dpi/,
   /opt/xorg/share/fonts/X11/75dpi/

There is no 'prefix' in my Xorg.0.log, but it appears that there is some sort of issue with twm finding fonts on your system.

I can find on mention of 'twm' in any log.

I do not know how to handle this because I cannot duplicate the problem.

comment:12 by Pierre Labastie, 3 years ago

OK, I think I've found what is wrong: the book states that Xorg Fonts are only needed at runtime for xorg-server. But actually, configure looks for font-utils, and issues a warning if it is not found. Then:

  • if not found: you get "checking for root directory for font files ...", then the warning, then "${datarootdir}/fonts/X11" (and I guess this is what gets expanded to ${prefix}share/fonts/X11, i.e. there is one missing stage of expansion), then default font paths to ${FONTROOTDIR}/misc, etc
  • if found: you get "checking for root directory for font files ... /usr/share/fonts/X11, then the paths are /usr/share/fonts/X11/misc, etc

So it means that Xorg Fonts should be built before xorg-server so that font-utils be available. I'll change the book.

comment:13 by Pierre Labastie, 3 years ago

Resolution: fixed
Status: reopenedclosed

Fixed at r19956. Note that although the fix is in the X server, something has changed in twm, which triggered the bug...

Note: See TracTickets for help on using tickets.