Solved fluxbox 1.3.6 issue on 10.1 amd64

To downgrade, remove fluxbox-1.3.6, then
Code: 
cd some/tmp/dir
svnlite co https://svn0.us-east.FreeBSD.org/ports/head/x11-wm/fluxbox@376521
cd fluxbox
make install
 
Since I still had the fluxbox-1.3.5 source in my /usr/ports/distfiles, I tricked x11-wm/fluxbox into reinstalling, by altering the checksum and file size on the /usr/ports/x11-wm/fluxbox/distinfo to be the ones from the old tarball. :p

It's greeasy, but it worked. :)
 
I'm also having this problem on my laptop since updating to fluxbox-1.3.6. I'm running FreeBSD 10.1-RELEASE-p4. Fluxbox starts but crashes if any application is started. I ran gdb on the core file and it appears to be related to libXft.so.2. I've emailed the maintainer. In the meantime, I'll use another window manager.

gdb fluxbox fluxbox.core output is:
Code: 
...
#0  0x000000080188a0a3 in XftDrawString8 ()
  from /usr/local/lib/libXft.so.2
[New Thread 804c06400 (LWP 100426/fluxbox)]
 
Well, this is one way to avoid receiving bug reports:
"Sorry, either the product Ports Tree does not exist or you aren't authorized to enter a bug into it."
when trying to report the problem through BugZilla.

Guess we'll just have to e-mail maintainers instead. o_O
 
You can feel comfort in my misery now too. Another desktop I maintain had this in the syslog this morning:
Code: 
Jan 20 09:50:12 trp kernel: pid 1007 (fluxbox), uid 1002: exited on signal 6 (core dumped)
 
Thanks weif. Based on the information I've gleaned from the Fluxbox devs, I know they are doing their best. I am currently running the latest git (1.3.7) of Fluxbox and it's fine, except for weird encoding issues in the title bar and the taskbar buttons. They are good folks, so I'm sure they'll get it knocked out before long. :)
 
willbprog127 said:
Well, apparently the issue has been fixed upstream. I also sent another e-mail to the FreeBSD x11-wm/fluxbox maintainer with all of the information they need to patch this and get us back on 1.3.6. :)
Click to expand...

Just an update. I still have not heard back from the x11-wm/fluxbox maintainer and I haven't seen any activity related to Fluxbox on the ports system.

I have found that most developers / maintainers want to know when something is wrong with their project, and they usually at least give an acknowledgement. This experience is different and somewhat frustrating. Either this maintainer lives a reclusive life, has had a major event happen in their life or they have given up maintaining this port.

When a FreeBSD port maintainer is unresponsive, what's the next step?
 
https://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/makefile-maintainer.html

Other changes to the port will be sent to the maintainer for review and approval before being committed. If the maintainer does not respond to an update request after two weeks (excluding major public holidays), then that is considered a maintainer timeout, and the update may be made without explicit maintainer approval. If the maintainer does not respond within three months, or if there have been three consecutive timeouts, then that maintainer is considered absent without leave, and can be replaced as the maintainer of the particular port in question. Exceptions to this are anything maintained by the Ports Management Team <portmgr@FreeBSD.org>, or the Security Officer Team <security-officer@FreeBSD.org>. No unauthorized commits may ever be made to ports maintained by those groups.
Click to expand...

Haven't reviewed the whole thread, but if there is no answer to the bug report within the allotted time above then request action be taken on it based on the maintainer timeout.
 
Can you please do:
cd /usr/ports/x11-wm/fluxbox/files
fetch https://raw.githubusercontent.com/junovitch/my-freebsd-build/master/patches/patch-src_FbTk_TextButton.cc
cd /usr/ports/x11-wm/fluxbox; make deinstall; make clean; make install

And report back if this fixes the issue? You may need to pkg install ca_root_nss if the HTTPS link gives you an error.
 
So somebody already opened PR 197150 for this issue. It didn't have a real patch for the port but I made one and posted that with Poudriere logs. It looks like the fix works for me but I don't use Fluxbox everyday. If this works for you please say so and throw in a "me too" for the PR. If it looks good I'll explain in the PR that this has been sitting on the forum for as long as it has with no action taken. Thanks.
 
junovitch Thanks for that. My FreeBSD install basically crumbled around me today, so I'm probably not going to be reinstalling it anytime soon. I am again running into other problems FreeBSD has thrown at me in the past, so I'll wait for future releases and hope that FreeBSD has caught up with my hardware.

Thanks for looking into that for me...I wish I could see if your patch fixed it or not for me.
 
Yesterday I was on Freenode #fluxbox and it was said there is a 1.3.7 in the works. Without any major issues it's release is not too far in the future.
 
willbprog127,
I see your replies in http://sourceforge.net/p/fluxbox/bugs/1117/ In that bug report, did the first patch shown here resolve all your issues? This is the fix I've applied for the FreeBSD PR and it seems at a glance that I start start programs.
http://git.fluxbox.org/fluxbox.git/commit/?id=7b8fd2d81ad80a73564fc9fbb779f47568f12652

Did you need to apply the second fix mentioned in that bug report? I didn't not apply that one and it seems like it works. But I hadn't tested long enough to see if there were other issues.
http://git.fluxbox.org/fluxbox.git/commit/?id=2b70480b9740c36c50b69d87954c645217cd65cf
 
junovitch said:
Can you please do:
cd /usr/ports/x11-wm/fluxbox/files
fetch https://raw.githubusercontent.com/junovitch/my-freebsd-build/master/patches/patch-src_FbTk_TextButton.cc
cd /usr/ports/x11-wm/fluxbox; make deinstall; make clean; make install

And report back if this fixes the issue? You may need to pkg install ca_root_nss if the HTTPS link gives you an error.
Click to expand...
I applied the patch and it appears to have fixed the problem. I also never heard back from the maintainer after emailing on the 17th.
 
"the maintainer" refered to the port-maintainer? then... yes. iI checked my mails coz ibecause I was not aware of any unanswered mails or open issues regarding that issue :)
 
Mathias Gumz, the issue was in PR 197150 which was closed on the 4th of Feb. The port compiled fine but we had to apply 7b8fd2d8 from git for "Fix bug: integer underflow in startup phase" to get it to work at runtime. Otherwise it crashed when a window was opened.
 
You must log in or register to reply here.
Back
Top