WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: flwm - "stock" build fails on exit  (Read 2418 times)

Offline dentonlt

  • Sr. Member
  • ****
  • Posts: 318
    • the trombone analog
flwm - "stock" build fails on exit
« on: July 21, 2012, 02:52:48 AM »
I re-compiled the FLWM code (1.14 - from the TC downloads/current release files pages) to add focus-follows-cursor. Everything works fine until I hit the "Exit" menu button. Rather than pulling up exittc, FLWM crashes - no menus available, no wbar, etc. I can still ctrl-alt-bkspc out.

I backtracked to try the original config.h (as posted for TC), and it fails, too. I'm not really sure what to try, actually.

I'm using compiletc, Xorg-7.6-dev.

Ideas?

Offline dentonlt

  • Sr. Member
  • ****
  • Posts: 318
    • the trombone analog
Re: flwm - "stock" build fails on exit
« Reply #1 on: July 21, 2012, 03:12:02 AM »
/tmp/wm_errors content:

Code: [Select]
flwm: X_GetProperty: BadImplementation (server does not implement operation) 0xb76ef038
Xlib: unexpected async reply (sequence 0x1ed)!
Xlib: unexpected async reply (sequence 0x1ee)!
X I/O error
X I/O error

Hmm ... I guess my Xlib doesn't match the one from the exittc binary?

Offline tinypoodle

  • Hero Member
  • *****
  • Posts: 3857
Re: flwm - "stock" build fails on exit
« Reply #2 on: July 21, 2012, 06:19:47 AM »
I re-compiled the FLWM code (1.14 - from the TC downloads/current release files pages) to add focus-follows-cursor.

Interesting to hear someone is on that...
Plenty of times in the past I gave up on flwm mainly due to that feature missing driving me sooner or later nuts...
"Software gets slower faster than hardware gets faster." Niklaus Wirth - A Plea for Lean Software (1995)

Offline dentonlt

  • Sr. Member
  • ****
  • Posts: 318
    • the trombone analog
Re: flwm - "stock" build fails on exit
« Reply #3 on: July 21, 2012, 09:23:55 AM »
Quote
Plenty of times in the past I gave up on flwm mainly due to that feature missing driving me sooner or later nuts...

If it's any consolation, that feature does indeed work. That part's great!

I'd like to sort out the other issue before posting my config.h, though ...  :(

Offline Rich

  • Administrator
  • Hero Member
  • *****
  • Posts: 11573
Re: flwm - "stock" build fails on exit
« Reply #4 on: July 21, 2012, 03:29:41 PM »
Hi dentonlt
Did you use he make file or the compileit script? I recompiled flwm_topside last year so I could disable that
annoying habit it has of moving my mouse pointer for me. I used the compileit script running under TC3.4
with Xorg-7.5-dev and it works just fine.

Offline dentonlt

  • Sr. Member
  • ****
  • Posts: 318
    • the trombone analog
Re: flwm - "stock" build fails on exit
« Reply #5 on: July 21, 2012, 06:51:23 PM »
Hi, Rich - winner! So much for following the README file.

I should have known - the compileit script ensures adds some parameters to the gcc call.

Solved!

tinypoodle: if you'd like to get follow-cursor, edit config.h and disable CLICK_TO_TYPE. Then recompile (using compileit ...)
« Last Edit: July 21, 2012, 06:53:06 PM by dentonlt »

Offline tinypoodle

  • Hero Member
  • *****
  • Posts: 3857
Re: flwm - "stock" build fails on exit
« Reply #6 on: July 22, 2012, 04:35:26 AM »
Good to know, thank you!
Wondering if that would not be worth it's own extension or even could be adapted by current flwm extensions.
"Software gets slower faster than hardware gets faster." Niklaus Wirth - A Plea for Lean Software (1995)

Offline curaga

  • Administrator
  • Hero Member
  • *****
  • Posts: 11041
Re: flwm - "stock" build fails on exit
« Reply #7 on: July 22, 2012, 12:35:50 PM »
The added gcc options were merely luck of the draw. Seems the source is out of date, see the exec exittc line (the variadic exec functions need to be NULL-terminated).
That's why your build crashed, the gcc options just happened to hide it.

This has already been fixed once, and I think we're running the fixed binaries given the lack of such reports ;)


Anyway, I'm not going to update the source tarball. I'll rather add that to my todo and fix that when we get version control, looking forward that.
The only barriers that can stop you are the ones you create yourself.