#7 Non-Debian cannot et Event ID

[Anonymous]

I installed the non-deb fs2 on a new installation of Manjaro on a laptop to test it prior to rebuilding our old "footswitch" m/c - my wfe has been using fs2 since its beginning but the Mint OS is now EOL. Everything seems to work ok on the laptop (which has ben used successfully before under Mint) except that I cannot select a proper event ID. The dropdown shows only eventx.

I installed fs2 without the footswitch plugged in - it was in use on the "footswitch" m/c at the time. I have since rebooted the laptop several times with the footswitch plugged in but cannot change the event ID.

I state this as an acedemic problem at the moment. It has occurred to me since then that Debian would, with unattened-upgrade, take less of my attention than Manjaro.

And now... Installation on Debian has a problem. Debian Bullseye reports...
Dependency is not satisfiable: libreoffice-gtk2

Bullseye uses libreoffice-gtk3 not libreoffice-gtk2, which is not in the repo. I have spent some time trying to replace gtk2 with gtk3 in the Control file but I cannot rebuild the deb package for some reason. I will retry later today but thought you should be aware of the problem.

Apart from the above, many thanks for a useful and reliable program!

Dave Stiles

[Dave Stiles]

Hello, Rolf. Is there any chance of a new .deb using gtk3 instead of gtk2, to work on bullseye, please? I have tried to modify the deb myself but failed.

[Rolf]

Sorry Dave, I only log in occasionally.
I'll have a look and see why I put that stipulation in the control file. It's probably just historical.
Does the foot pedal's event id show up in if you hover "pedal device" input selection in Tools->Configuration?
Ensure you haven't locked the device
If you click on the Icon opposite Device Info, it will give you a detailed report on the current device, that may point to something useful.
In the Help is a detailed breakdown of how to remap a footpedal in section "Remapping foot pedal input codes".
Finally check that the entries in /dev/input are owned by either plugdev or input and that your user-id is a member of those groups. This detail of the non-debian installation may have escaped your notice.

[Dave Stiles]

Thanks for the updates, Rolf. Haven't managed to do the Manjaro m/c yet but the Debian installs fine now. The footswitch pedal setup is ok but I cannot load the Config using the Configure option in the tools menu so can't complete the installation...

Manjaro pre-new install file - no event ID anywhere and device not locke.

[Rolf]

Regards "I cannot load the Config"
Run fs2 from the command line and see what error message is written to the terminal, or there maybe a message in the Help->Debug Log
I can't think what that could be, I've never come across an issue with that before, are you sure you're not clicking away on the menu header (Configuration & Tools)?

In Manjaro:
Does the foot pedal show when you run the lsusb command?
Does the foot pedal show when you run evtest and do you get the expected output from it?

[Rolf]

Discovered why I'm not receiving updates on tickets.
An old email address, Doh!

[Dave Stiles]

With NO pedal (in use elsewhere)...

Running fs2 in Terminal...
(fs2:13470): Gtk-CRITICAL **: 14:23:51.717: gtk_box_gadget_distribute: assertion 'size >= 0' failed in GtkScrollbar

After notification "initializing Footswitch" FS failed to run. Same when launched from GUI icon.

Ran Task Manager, found 4 instances of "fs2" (about the number of times I'd tried to launch it).

killall fs2

GUI icon launch ok except for pedal.

I'll report back when I can test with pedal.

[Rolf]

Morning Dave,
try editing the $HOME/.config/fs2/fs2.cfg file
HID_FILE_ID = /dev/input/eventx
This stipulates that there is no pedal or after establishing which device is the pedal, edit that into fs2.cfg

This is how footswitch establishes which devices are available:
In a python3 session:

Python 3.8.10 (default, Nov 14 2022, 12:59:47)
[GCC 9.4.0] on linux
Type "help", "copyright", "credits" or "license" for more information.

from evdev import InputDevice, ecodes, categorize, list_devices
all_devices = [InputDevice(fn) for fn in list_devices()]
for d in all_devices:
... print(d)
...
device /dev/input/event3, name "VEC VEC USB Footpedal", phys "usb-0000:00:14.0-4.4/input0"
device /dev/input/event13, name "HDA Intel PCH HDMI/DP,pcm=3", phys "ALSA"
device /dev/input/event12, name "HDA Intel PCH Front Headphone", phys "ALSA"
device /dev/input/event11, name "HDA Intel PCH Line Out", phys "ALSA"
device /dev/input/event10, name "HDA Intel PCH Rear Mic", phys "ALSA"
device /dev/input/event9, name "HDA Intel PCH Front Mic", phys "ALSA"
device /dev/input/event8, name "BTC USB Multimedia Keyboard Consumer Control", phys "usb-0000:00:14.0-4.3.3/input1"
device /dev/input/event7, name "BTC USB Multimedia Keyboard System Control", phys "usb-0000:00:14.0-4.3.3/input1"
device /dev/input/event6, name "BTC USB Multimedia Keyboard", phys "usb-0000:00:14.0-4.3.3/input0"
device /dev/input/event5, name "Logitech USB Optical Mouse", phys "usb-0000:00:14.0-4.3.1/input0"
device /dev/input/event4, name "Video Bus", phys "LNXVIDEO/video/input0"
device /dev/input/event2, name "Power Button", phys "LNXPWRBN/button/input0"
device /dev/input/event1, name "Sleep Button", phys "PNP0C0E/button/input0"
device /dev/input/event0, name "Power Button", phys "PNP0C0C/button/input0"

As you can see, my footpedal is /dev/input/event3

If you still have issues, feel free to be as verbose as possible, about the error and the environment.
Better too much, than too little!

Regards,
Rolf

[Dave Stiles]

Ok, Rolf, now have pedal plugged in to Debian m/c.Using icon to start FS, works ok. Editing config manually I can set Classic to 1 and it plays/pauses but still cannot get config menu option to work. So...

Start fs in terminal - no error, opens fine
Select config from menu - error in termainal reads...

Traceback (most recent call last):
File "/usr/bin/fs2", line 6424, in OnConf
Edit_Config(parent=self)
File "/usr/bin/fs2", line 8233, in init
self.fc_hidfile_lock = oob.OnOffButton(self.tab1, wx.ID_ANY)
File "/usr/share/footswitch2/onoffbutton.py", line 302, in init
self.SetImage(self._initial)
File "/usr/share/footswitch2/onoffbutton.py", line 703, in SetImage
self.SetFont(self._font)
File "/usr/share/footswitch2/onoffbutton.py", line 656, in SetFont
self.SetLabel(self._label)
File "/usr/share/footswitch2/onoffbutton.py", line 533, in SetLabel
self.txt_colour = self.GetBrightness(_colour)
File "/usr/share/footswitch2/onoffbutton.py", line 545, in GetBrightness
brightness = wx.Colour(_colour).GetLuminance()
AttributeError: 'Colour' object has no attribute 'GetLuminance'

... and fs2 GUI closes.

[Rolf]

Hi Dave,
You are using a version of wxpython prior to 4.1 when GetLuminance was added to Colour.

load the attached into /usr/share/footswitch2
I'll update the package if you give me the OK.

Regards,
Rolf

[Dave Stiles]

There isn't a wxpython, only wxpython-tools 4.0.7, and that is not installed (this is latest Debian Bullseye).

Installing the onoffbutton patch has worked without wxpython. Config now seems to work fine. Many thanks!

Now to pursue the Manjaro installation...

[Rolf]

You might want to take a gander at:
https://extras.wxpython.org/wxPython4/extras/linux/gtk3/debian-11/