-
-
Notifications
You must be signed in to change notification settings - Fork 78
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FvwmButtons fails silently; Fvwm3 #60
Comments
Hi @PackRat-SC2018, Thanks for the report. Do you have a core file left behind from FvwmButtons? |
I don't think so. Where would it get dumped? I started Fvwm again with "fvwm3 -D" - that the correct way to generate the file you need? |
Hi,
Ah, alas First we need to compile
As for corefiles, you should check that corefiles can be created:
If that returns
and restart X11. Corefiles will usually be in the CWD for the program you're using, so check Then it's just a case of installing
If you're using Then attach the output here. |
Recompiled Fvwm3 ulimit returned unlimited. Not sure the gdb command worked as intended. Here is the terminal output: `[doug@WILLOW-01 .fvwm]$ ls /usr/local/bin For help, type "help". |
Hi @PackRat-SC2018, That's because Kindly, |
Recompiled Fwm3 on a clean ArchLabs install, and on Void. Used the make command you provided above. FvwmButtons working as expected on both systems. |
Thanks, @PackRat-SC2018! I'll close this for now then, but if you find anything else, feel free to file another issue, please. |
On both Void and ArchLabs, kernel 5.6.x, FvwmButtons does not start.
With the default RightPanel configuration, there is a quick flash (FvwmPager, I think) and then just the wallpaper visible. Sometimes, FvwmIconMan or stalonetray will remain, but not both.
Fvwm3 is functional afterwards, I can start both FvwmPager and FvwmIconMan from FvwmConsole. If I try to start FvwmButtons from FvwmConsole (either the RightPanel or a simple test panel with just FvwmIconMan) no FvwmModule starts, and there is no message in FvwmConsole.
The text was updated successfully, but these errors were encountered: