x11-wm/flwm-1.00-r4 emerges fine and starts ok. Starting any application per menu results in a killed xserver. If an application is started via .xinitrc the xserver gets killed too. No information in /var/log/kern.log or /var/log/Xorg.0.log Reproducible: Always Steps to Reproduce: 1. emerge flwm 2. edit .xinitrc to enable flwm as windowmanager 3. startx 4. open an xterm through the menu 5. xserver killed, returned to the console Actual Results: xserver killed Expected Results: start the application succesfully Portage 2.0.51.22-r2 (default-linux/ppc/2005.0, gcc-3.4.4, glibc-2.3.4.20041102-r1, 2.6.11-h15 ppc) ================================================================= System uname: 2.6.11-h15 ppc 7447A, altivec supported Gentoo Base System version 1.6.13 dev-lang/python: 2.3.5 sys-apps/sandbox: 1.2.11 sys-devel/autoconf: 2.13, 2.59-r6 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.5 sys-devel/binutils: 2.15.90.0.3-r5 sys-devel/libtool: 1.5.18-r1 virtual/os-headers: 2.6.8.1-r4 ACCEPT_KEYWORDS="ppc" AUTOCLEAN="yes" CBUILD="powerpc-unknown-linux-gnu" CFLAGS="-O2 -mtune=G4 -maltivec -mabi=altivec -fno-strict-aliasing -pipe" CHOST="powerpc-unknown-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.3/env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3.4/env /usr/kde/3.4/share/config /usr/kde/3.4/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/lib/mozilla/defaults/pref /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O2 -mtune=G4 -maltivec -mabi=altivec -fno-strict-aliasing -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig distlocks sandbox sfperms strict userpriv usersandbox" GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/Linux/distributions/gentoo" LC_ALL="en_GB.utf8" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="ppc X alsa altivec berkdb bitmap-fonts crypt cups curl dlloader dvd dvdread eds emboss esd fam fortran gdbm gif gnome gpm gstreamer gtk gtk2 imlib ipv6 jpeg kde libwww mad motif mozilla mp3 mpeg ncurses network nls ogg oggvorbis opengl pam pdflib perl png python qt readline slang spell ssl tcpd tiff truetype truetype-fonts type1-fonts unicode vorbis xml2 xprint xv zlib userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CTARGET, LANG, LDFLAGS, LINGUAS, MAKEOPTS
I'm not even getting that far. I build a .xinitrc the way "man flwm" tells me to and it starts to start up, then "flwm" segfaults. I'm planning to build a system from scratch with just X and flwm (thanks to VMWare :)) and see if I can narrow this down a little better.
Don't know if anyone is still kicking around with this. I was wondering if the status on this is still correct? I'm going to make an ebuild of the newest version 1.02 tonight or tomorrow. Hopefully someone will be willing to test for me :D
Hrmm well I made an ebuild for the new version 1.02 but it still segfaults. So I will have to debug it sometime. It will probably get done this weekend 3/10 or so.
Ok figured out what the problem is. FLTK supports x configured with xft and x just straight. However FLWM counts on FLTK being configured without xft. It does so by calling into the XFontStruct directly. Since Xft replaces XFontStruct with XftFont uhh this causes badness (segfault). Most people probably are probably using xft because the fonts are prettier so this is a fairly large problem. Soo I guess I could patch this but it could take some work (it already took a bit of work to debug it, mainly because gdb is new to me). Gonna email the FLWM author maybe he'll fix it.
Ack forgot to mention that there is a work around. All you need do is recompile FLTK with the noxft use flag # echo "x11-libs/fltk noxft" >> /etc/portage/package.use # emerge --ask --verbose --oneshot fltk
Did someone contact upstream about this?
I contacted Bill Spitzak who is the author of flwm on 2007/03/13. He said he would fix it asap on 2007/03/15 but looks like it's taking awhile. I guess I can post the ebuild I made for 1.02 if that'll help anyone with some time for fixing this.
Created attachment 123737 [details] Ebuild to build FLWM version 1.02
Now the ebuild dies on pkg_setup when flwm is compiled with USE="-noxft". Please, don't close the bug until flwm gets support for xft.
I just took a look at FLWM's CVS repository, and apparently the newest commit is actually 12 months old. It appears to me that the author has no intention on fixing this anytime soon. This seems to be a rather large problem. I'm considering removing the package from the tree, or at least masking it. Your thoughts?
(In reply to comment #10) > I just took a look at FLWM's CVS repository, and apparently the newest commit > is actually 12 months old. It appears to me that the author has no intention on > fixing this anytime soon. > > This seems to be a rather large problem. I'm considering removing the package > from the tree, or at least masking it. Your thoughts? > I wouldn't remove it, but masking is a good idea. There aren't all that many viable window managers as it is -- maybe this one dying is a *good* thing because it will free up people to work on Beryl/Compiz, Enlightenment, WindowMaker, Fluxbox and IceWM, all of which appear to be viable.
You forgot to mention Openbox, the best of them all. ;) Yeah, I'll probably mask it soon unless anyone has any better ideas.
Well rather than removing it since it does still work fine with a certain configuration, couldn't the ebuild be written so that it will depend on a (slotted?) version of fltk compiled with noxft?
Two years without a fix is enough. So I vote for removal. Anyway, I look forward an overlay for removed packages...
+1 for removal unless upstream wakes up pretty soon.
(In reply to comment #15) > +1 for removal unless upstream wakes up pretty soon. Same here. (Btw, the bugzie voting is cool :-P)
Debian has patches for fltk and flwm to solve this problem. I'm looking into it ;-)
(In reply to comment #17) > Debian has patches for fltk and flwm to solve this problem. I'm looking into it > ;-) > You have 60 days to import them, or it's gone.
Created attachment 138245 [details] new ebuild with xft support this need patched fltk version
Created attachment 138246 [details, diff] xft patch for flwm this need patched fltk
Created attachment 138247 [details] patched fltk ebuild patched fltk ebuild for rotated text wuth xft
Created attachment 138249 [details, diff] patch for fltk include rotated text patch. i send it to upstream too.
Reassigning
This bug is fixed. It just needs stabilisation of x11-libs/fltk-1.1.7-r3 (needs a bit of testing yet). Stabilisation of x11-wm/flwm-1.02 would be nice too.
(In reply to comment #24) > This bug is fixed. It just needs stabilisation of x11-libs/fltk-1.1.7-r3 (needs > a bit of testing yet). Stabilisation of x11-wm/flwm-1.02 would be nice too. > ?! amd64 will not stabilize anything that hasn't been unmasked 30 days, so please revert our keyword to ~ if there is one and unmask the thing now..
(In reply to comment #25) > > amd64 will not stabilize anything that hasn't been unmasked 30 days, so please > revert our keyword to ~ if there is one and unmask the thing now.. > Don't panic! I haven't filed a stabilisation bug nor CC'ed arches here (and of course, I haven't marked it stable since I'm not AT myself). I just pointed out what needs to be done to close this bug.
Old versions removed and unmasked (no stable keywords anymore).
