[Bug 282335] devel/qt6 menus no longer working

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282335

--- Comment #5 from mmatalka at gmail.com ---
No problem Jason, I know it's hard to debug a user that could have a complete
different setup than expected.  For what it's worth (prior to this issue) your
shotcut patches have been working perfectly for me and I'm really happy with
them.

Yes, so when I click File with the mouse, nothing happens except for the menu
bar item itself gets highlight.  But I can Alt-F to open the file menu. 
Additionally, I can click an entry in the menu with the mouse and it performs
the action.  I just can't open the menu.  The place that this becomes a big
issue in obs-studio is I cannot add any sources because there is no hotkey
(afaik) to open the "+" menu.

Also in messing around in obs I noticed another issue that might be a clue: my
obs was setup to work before so I tried to start a screen capture recording and
it starts for a second or two and then the recording stops on its own.  I'm not
sure why.  And in messing around I removed the Video Capture source so I can't
test it anymore hahah.  Whoops!

The reason I think it's qt6 related is because I upgraded my ports on Oct 20th
going from 6.7.2 to 6.7.3 and after that I noticed this issue.  But I also tend
to update base and pkgs at the same time so which one it is, I don't know.  To
be fair, I didn't test it immediately so I'm sort of assuming that's the
connection and could easily be wrong.

I tried strawberry and it has the same behaviour around menus.

Now, I've been trying to revert back to 6.7.2 but running into issues getting
pkg to install the old packages so I haven't had success, so I don't have any
progress there.

I have also watched obs logs, and I don't get any error when I click menus, at
least, and otherwise I'm not sure what to look for in obs logs that might be a
clue.

I'm going to install latest base today, maybe there was a little transient
issue in there?  It is kind of weird that it would be such a specific failure
mode given a base issue.  But stranger things have happened.

Thank you for your time and help.

-- 
You are receiving this mail because:
You are the assignee for the bug.