cbyt trace window issues in Ubuntu

[tamen...@gmail.com]

I'm having an issue in cbyt where any functionality requiring mouse clicks in the trace display window isn't working and results in a "donk" sound with each click (like a "you can't do that" kind of warning sound). This is all things like trying to zoom, or pick a mute, or pick first breaks, or estimate velocity, etc. This has been happening with data in both .segy or .tr (trcio) format. The trace headers are all populated with geometry info, but even if that wasn't the case, I'd still think at least the zoom functionality should work.

I'm running the latest revision of cpseis. I noticed the issue in Ubuntu Jammy Jellyfish, but later updated to Noble Numbat and it still persists. I'm not sure where to look for any kind of debugging info, but I'd imagine this is probabaly Java related?

Has anyone experienced this or have any ideas?

[cpseis-user]

I haven't had any problems with Ubuntu 22.04, but I haven't used Ubuntu after that. I have built it in Debian, Suse and Red Hat family distros without problem. I have only found it broken in Arch linux derivatives. I doubt it is Java, as cbyt is c++ code. I have used Java up to version 21 and gcc up to version 14. Are you using a Wayland desktop? I have stuck with the old dinosaur X11.

[tamen...@gmail.com]

Oh it appears I am actually using a Wayland desktop and didn't realize it. Let me see if I can get going on X11 and I'll report back. Thanks!

[tamen...@gmail.com]

hmm, still no luck on x11, same issue. cbyt does seems to provide some amount of info in the command line while it's running, but it doesn't print any error messages out whenever the "donk" sound occurs as I try to zoom or pick a mute. Is there a good place to start for debugging cbyt? I may just try an older ubuntu distribution if necessary.

[cpseis-user]

I dug out some old installations. Ubuntu 20.04 and 22.04 were working. I upgraded to 24.04 and recompiled CPSeis. cbyt is okay, I can do trace picks with mouse. I cannot reproduce this problem.

[tamen...@gmail.com]

OK thanks for verifying that - it seems there's probably something wrong in my setup then. Is there anything special you do when installing motif? I am doing:
     sudo apt install -y libmotif-dev libxmu-dev libxext-dev

[cpseis-user]

I can't remember offhand, as those libraries are named differently in various distros, but if it compiled, then you have gotten enough dependencies.

Oh by the way, do you have Num Lock off when trying to pick?

[tamen...@gmail.com]

Num Lock is off, and I've been experiencing the same issue on two different machines, an iMac desktop and a Toshiba laptop - running Noble Numbat on the iMac, and Jammy Jellyfish on the Toshiba. The laptop doesn't have a Num Lock option. It does feel like it could be (and it wouldn't surprise me) if it were pilot error to blame, just not sure what I'm doing wrong. 

I do get an interesting print out in the terminal when trying any of interactive functionality - this prints only when I exit the action I was attempting (like "abort zoom", or "end picking", etc...)

"Warning: Actions not found: startZoom, zoomMotion, endZoom, startPan, panMotion, endPan"

Seems suspicious, is this warning normal?

[cpseis-user]

No that is a strange message; I don't know where it comes from. The cbyt code does have a startZoom function, but not those others.

[tamen...@gmail.com]

Ah sorry, disregard that... I induced that particular error as a result of a test where I had been tinkering inside the code to see if I could brute-force some mouse interactions in cbyt. 

I'm going to try a fresh install on a RHEL-based linux, (probably Rocky 9 to avoid the RHEL10 wayland/xwayland stuff.) If my issue with cbyt persists there, then I'm convinced it's user-error and nothing to do with the setup/installation.

[tamen...@gmail.com]

I've finally resolved this issue; note cbyt appears sensitive to certain types of keyboards (even if they don't have numlock).

I did end up doing a fresh install on Rocky Linux 9 and sure enough ran into the same error, so I was sure by that point there were no issues with my setup/installation. The issue was actually with my keyboard(s), but interestingly, neither of the ones I had been using have a  numberpad. I have cpseis installed on 2 different machines, a Toshiba Satellite laptop and an old iMac with an old keyboard. In order for cbyt to register my mouse clicks for trace related functions (zoom, mute, trace edits, etc...), I had to plug in a totally different Dell keyboard that I had lying around which does have a numberpad and numlock key. I then switched the numlock off on that keyboard and cbyt finally started working normally for me.

So for posterity, if anyone ever runs into this, try a different keyboard entirely! (especially one with a numberpad and numlock key that can be turned off)

Thanks for everyone's help on this!