WindowMaker hangs when turning on TitleBar for application

[MarioNigrovic]

I use WindowMaker on my work desktop, because I really like the look and feel.
Recently, I've been having to use an application which tries to do its own window management and it disables the titlebar, titlebar icons and the resize bar. In the past I've been able to iconify applications like these and then right-click on the icon to access window attributes and add the titlebar back, etc.
However, with this application when I do this, wmaker just locks up and sits and spins 100% on a CPU.
I would really like to be able to force decorations on to this window so I can shade/unshade it to declutter the screen (it's unfriendly about popping up/down, too). What should I do to help diagnose this problem? Or is this just a lost cause?

[gryf]

Could you provide steps to reproduce this issue?

[MarioNigrovic]

It's pretty straighforward:

1. Start the application (icvwb from Synopsys if that helps)
2. Iconify it (Alt-M in my setup)
3. Right click on icon to bring up Attributes form
4. Un-click on "Disable titlebar" to re-enable it
5. Click on "Apply"

Immediately upon clicking Apply, WindowMaker freezes and starts burning 100% CPU.

I just discovered that if I kill the --for-real process, I can recover the session, and I used SIGABRT to get some sense of what it had been doing:

(gdb) backtrace
#0 0x0000000000410d01 in wArrangeIcons ()
#1 0x000000000041295e in paint_app_icon ()
#2 0x000000000047521d in applySettings ()
#3 0x00007fb3e7f70932 in handleActionEvents () from /tools/oss/packages/x86_64-centos7/wmaker/0.95.9/lib/libWINGs.so.3
#4 0x00007fb3e7f7caa7 in WMHandleEvent () from /tools/oss/packages/x86_64-centos7/wmaker/0.95.9/lib/libWINGs.so.3
#5 0x00000000004367a6 in EventLoop ()
#6 0x00000000004432b2 in real_main ()
#7 0x00000000004426a4 in main ()

I also discovered that I had a fair number of these "stuck" wmaker processes hanging around on my system, because they weren't dying when I killed of previous Xvnc's that were hosting them. I can attach the core file and binary if that would help?

[MarioNigrovic]

Oh, I did discover that when I manually add NoTitlebar = No; to my WMWindowAttributes, there's no problem.

[gryf]

Perhaps attaching core file could help, if you still think, that this is a problem. If you think that solution you discovered is good enough, than you can close the issue.

[crmafra]

On Sat, 5 Jun 2021 at 10:47:12 -0700, Roman Dobosz wrote: Perhaps attaching core file could help, if you still think, that this is a problem. If you think that solution you discovered is good enough, than you can close the issue.

I don't think he should close the issue. It's a bug.

[MarioNigrovic]

Here are both the core and the executable, in case having the latter helps with interpreting the core. I don't know if our IT department builds the version we run, or if they find a copy somewhere and just install it.
core.127721.gz
wmaker.gz

[MarioNigrovic]

Oh, BTW, I mentioned that there's a workaround mostly to clarify that it's not necessarily the interaction with the particular application that is the problem, but perhaps it's something about changing the titlebar setting.

[dmaciejak]

That icvwb is a proprietary software, where can we get a trial version? or do you have any other example of app that have the same issue. I tried to reproduce the issue with a gtk3 home made app but wmaker is working properly.

[MarioNigrovic]

Folks - It happens to me quite frequently with just ordinary xterms. Simply drag a window that starts partially hidden by another.

…

-- Mario 480-228-9853

On Fri, Feb 10, 2023 at 7:37 AM David Maciejak ***@***.***> wrote: That icvwb is a proprietary software, where can we get a trial version? or do you have any other example of app that have the same issue. I tried to reproduce the issue with a gtk3 home made app but wmaker is working properly. — Reply to this email directly, view it on GitHub <#13 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AUEVCJUS6LAHIYARRZT2CQ3WWZHEHANCNFSM46DWEANA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

-- This electronic communication and the information and any files transmitted with it, or attached to it, are confidential and are intended solely for the use of the individual or entity to whom it is addressed and may contain information that is confidential, legally privileged, protected by privacy laws, or otherwise restricted from disclosure to anyone else. If you are not the intended recipient or the person responsible for delivering the e-mail to the intended recipient, you are hereby notified that any use, copying, distributing, dissemination, forwarding, printing, or copying of this e-mail is strictly prohibited. If you received this e-mail in error, please return the e-mail to the sender, delete it from your computer, and destroy any printed copy of it.