MX Fluxbox: touchpad-indicator fails to start, gives error message

Help for MX Fluxbox
When asking for help, use Quick System Info from MX Tools. It will be properly formatted using the following steps.
1. Click on Quick System Info in MX Tools
2. Right click in your post and paste.
Message
Author
User avatar
kevjonesin
Posts: 8
Joined: Wed May 18, 2016 7:52 am

MX Fluxbox: touchpad-indicator fails to start, gives error message

#1 Post by kevjonesin »

Here's my quick system info:

Code: Select all

System:
  Kernel: 6.1.0-13-amd64 [6.1.55-1] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
    parameters: persist_all zswap.enabled=1
  Desktop: Fluxbox v: 1.3.7 info: tint2 vt: 7 dm: LightDM v: 1.26.0 Distro: MX-23.1_fluxbox_x64
    Libretto October 15 2023 base: Debian GNU/Linux 12 (bookworm)
Machine:
  Type: Laptop System: LENOVO product: 76641KU v: ThinkPad T61 serial: <superuser required>
    Chassis: type: 10 serial: <superuser required>
  Mobo: LENOVO model: 76641KU serial: <superuser required> BIOS: LENOVO v: 7LETD0WW (2.30 )
    date: 02/27/2012
Battery:
  ID-1: BAT0 charge: 7.3 Wh (98.6%) condition: 7.4/71.3 Wh (10.4%) volts: 12.3 min: 10.8
    model: SANYO 42T4522 type: Li-ion serial: <filter> status: not charging
CPU:
  Info: model: Intel Core2 Duo T7500 bits: 64 type: MCP arch: Core2 Merom level: v1 built: 2006-09
    process: Intel 65nm family: 6 model-id: 0xF (15) stepping: 0xB (11) microcode: 0xBA
  Topology: cpus: 1x cores: 2 smt: <unsupported> cache: L1: 128 KiB desc: d-2x32 KiB; i-2x32 KiB
    L2: 4 MiB desc: 1x4 MiB
  Speed (MHz): avg: 799 high: 800 min/max: 800/2201 boost: enabled scaling: driver: acpi-cpufreq
    governor: ondemand cores: 1: 800 2: 798 bogomips: 8777
  Flags: ht lm nx pae sse sse2 sse3 ssse3 vmx
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: itlb_multihit status: KVM: VMX disabled
  Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT disabled
  Type: mds status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT disabled
  Type: meltdown mitigation: PTI
  Type: mmio_stale_data status: Unknown: No mitigations
  Type: retbleed status: Not affected
  Type: spec_rstack_overflow status: Not affected
  Type: spec_store_bypass status: Vulnerable
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 mitigation: Retpolines, STIBP: disabled, RSB filling, PBRSB-eIBRS: Not
    affected
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: NVIDIA G86M [Quadro NVS 140M] vendor: Lenovo ThinkPad T61 driver: nvidia v: 340.108
    non-free: series: 340.xx status: legacy (EOL) last: release: 340.108 kernel: 5.4 xorg: 1.20
    arch: Tesla process: 40-80nm built: 2006-13 pcie: gen: 1 speed: 2.5 GT/s lanes: 16
    bus-ID: 01:00.0 chip-ID: 10de:0429 class-ID: 0300
  Display: x11 server: X.Org v: 1.21.1.7 driver: X: loaded: nvidia gpu: nvidia display-ID: :0.0
    screens: 1
  Screen-1: 0 s-res: 1440x900 s-dpi: 121 s-size: 302x191mm (11.89x7.52") s-diag: 357mm (14.07")
  Monitor-1: LVDS-0 res: 1440x900 hz: 60 dpi: 120 size: 304x190mm (11.97x7.48")
    diag: 358mm (14.11") modes: N/A
  API: OpenGL v: 3.3.0 NVIDIA 340.108 renderer: Quadro NVS 140M/PCIe/SSE2 direct-render: Yes
Audio:
  Device-1: Intel 82801H HD Audio vendor: Lenovo ThinkPad T61/R61 driver: snd_hda_intel v: kernel
    bus-ID: 00:1b.0 chip-ID: 8086:284b class-ID: 0403
  API: ALSA v: k6.1.0-13-amd64 status: kernel-api tools: alsamixer,amixer
  Server-1: PipeWire v: 0.3.65 status: active with: 1: pipewire-pulse status: active
    2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Intel 82566MM Gigabit Network vendor: Lenovo ThinkPad T61/R61 driver: e1000e v: kernel
    port: 1840 bus-ID: 00:19.0 chip-ID: 8086:1049 class-ID: 0200
  IF: eth0 state: down mac: <filter>
  Device-2: Intel PRO/Wireless 4965 AG or AGN [Kedron] Network driver: iwl4965 v: in-tree:
    modules: wl pcie: gen: 1 speed: 2.5 GT/s lanes: 1 bus-ID: 03:00.0 chip-ID: 8086:4230
    class-ID: 0280
  IF: wlan0 state: up mac: <filter>
Drives:
  Local Storage: total: 262.65 GiB used: 15.48 GiB (5.9%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: Western Digital model: WD2500BEVS-60UST0 size: 232.89 GiB
    block-size: physical: 512 B logical: 512 B speed: 1.5 Gb/s type: N/A serial: <filter> rev: 1A01
    scheme: MBR
  ID-2: /dev/sdb maj-min: 8:16 type: USB vendor: PNY model: USB 3.0 FD size: 29.76 GiB
    block-size: physical: 512 B logical: 512 B type: N/A serial: <filter> rev: 1.00 scheme: MBR
  SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Partition:
  Message: No partition data found.
Swap:
  Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: partition size: 3.03 GiB used: 203.4 MiB (6.5%) priority: 2 dev: /dev/sda7
    maj-min: 8:7
  ID-2: swap-2 type: file size: 2.5 GiB used: 0 KiB (0.0%) priority: -2
    file: /live/boot-dev/swap-file
Sensors:
  System Temperatures: cpu: 44.0 C mobo: N/A gpu: nvidia temp: 59 C
  Fan Speeds (RPM): fan-1: 2987 fan-2: 2987
Repos:
  Packages: pm: dpkg pkgs: 1910 libs: 937 tools: apt,apt-get,aptitude,nala,synaptic pm: rpm pkgs: 0
    pm: flatpak pkgs: 0
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
    1: deb http://deb.debian.org/debian bookworm-updates main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/debian.list
    1: deb http://deb.debian.org/debian bookworm main contrib non-free non-free-firmware
    2: deb http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/mx.list
    1: deb http://mxrepo.com/mx/repo/ bookworm main non-free
  Active apt repos in: /etc/apt/sources.list.d/ookla_speedtest-cli.list
    1: deb [signed-by=/etc/apt/keyrings/ookla_speedtest-cli-archive-keyring.gpg] https://packagecloud.io/ookla/speedtest-cli/debian/ bookworm main
    2: deb-src [signed-by=/etc/apt/keyrings/ookla_speedtest-cli-archive-keyring.gpg] https://packagecloud.io/ookla/speedtest-cli/debian/ bookworm main
Info:
  Processes: 230 Uptime: 21h 13m wakeups: 3 Memory: 2.89 GiB used: 2.26 GiB (78.3%) Init: SysVinit
  v: 3.06 runlevel: 5 default: graphical tool: systemctl Compilers: gcc: 12.2.0 alt: 12:
  Client: shell wrapper v: 5.2.15-release inxi: 3.3.26
Boot Mode: BIOS (legacy, CSM, MBR)
I recently installed a live instance to a USB stick and have been exploring and tweaking it.

When I've tried to launch touchpad-indicator from "System Manager" gui it fails to launch (and sometimes leaves scrolling inverted afterwards).
So I tried launching it from a terminal and after a little delay got the following error message:
AttributeError: 'TouchpadIndicator' object has no attribute 'configuration'
… as so …

https://i.imgur.com/tEzicL0.png

I've tried purging and reinstalling the package but still returns the same error. I looked at the mentioned lines in the "touchpadindicator.py" script to check for obvious anomalies, like blatant typos or some such, but nothing stood out to a layman like myself.

Also, if/when we do get it working, will it include options for adjusting my ThinkPad's "TrackPoint" (the little 'toggle mouse' embedded in the keyboard)?

Thanks in advance for y'all's time and attention. MX has been my 'go to' distro since MX15 :-)




Moderator: image changed to link, please read the forum rules

ghunter
Posts: 175
Joined: Mon May 29, 2023 12:40 am

Re: MX Fluxbox: touchpad-indicator fails to start, gives error message

#2 Post by ghunter »

Hi

I do not have a laptop with Linux setup on it. But I have a tower and just installed it and notice there a number of packages for python you may like to check on?
Start-Date: 2023-11-19 15:43:12
Commandline: apt install touchpad-indicator
Requested-By: me (1000)
Install: gir1.2-gconf-2.0:amd64 (3.2.6-8, automatic), python3-evdev:amd64 (1.6.1+dfsg-1+b2, automatic), python3-pyudev:amd64 (0.24.0-1, automatic), gir1.2-ayatanaappindicator3-0.1:amd64 (0.5.92-1, automatic), gir1.2-rsvg-2.0:amd64 (2.54.7+dfsg-1~deb12u1, automatic), touchpad-indicator:amd64 (2.2.3-1mx23)
End-Date: 2023-11-19 15:43:13
launching it .....widget appears in my icewm tray and gives options for preferences.

launch no errors IMHO

Code: Select all

 <gettext.GNUTranslations object at 0x7f690ca831d0>
#####################################################
Distributor: Debian
Description: Debian GNU/Linux 12 (bookworm)
Release: 12
Codename: bookworm
Architecture: x86_64
#####################################################

Touchpad-Indicator version: 2.2.3-1mx23
=== 2 ===
=== 21 ===
=== 212 ===
==== start set_touch_enabled =====
set_touch_enabled: True
are_all_touchpad_enabled:  False
==|==

User avatar
kevjonesin
Posts: 8
Joined: Wed May 18, 2016 7:52 am

Re: MX Fluxbox: touchpad-indicator fails to start, gives error message

#3 Post by kevjonesin »

Yeah, I appear to have all the dependencies in place …

Image

I'm running fluxbox, not icewm.
Perhaps @Jerry3904 might have some ideas?

p.s. – I was able to run:

Code: Select all

touchpad-indicator -l
… in terminal and "POINTINGSTICK" shows up in various places in the output. Suggests that touchpad-indicator may be able to recognize and configure it if we can get the script error figured out.

I also tried to run `touchpad-indicator -s` and got the following output:

Code: Select all

$ touchpad-indicator -s
<gettext.GNUTranslations object at 0x7f0803caa090>
Another instance of Touchpad-Indicator is working
ERROR:dbus.proxies:Introspect error on :1.144:/es/atareao/TouchpadIndicator: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Traceback (most recent call last):
  File "/usr/bin/touchpad-indicator", line 36, in <module>
    main()
  File "/usr/share/touchpad-indicator/touchpadindicator.py", line 717, in main
    make_visible()
  File "/usr/share/touchpad-indicator/touchpadindicator.py", line 663, in make_visible
    unhide()
  File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 72, in __call__
    return self._proxy_method(*args, **keywords)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 141, in __call__
    return self._connection.call_blocking(self._named_service,
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3/dist-packages/dbus/connection.py", line 634, in call_blocking
    reply_message = self.send_message_with_reply_and_block(
                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
In regard to:
Another instance of Touchpad-Indicator is working
… it has been prefixing that to other attempts to interact with it from terminal as well. Yet when I go into htop and filter for "touchpad-indicator" or even just "touch" or "touchpad" no running process shows up. It has shown in htop briefly when I've checked htop for it while waiting for the error to post in terminal after an attempt to start touchpad-indicator from there.

I'm fairly befuddled at this point, lol.

Maybe some state data got left in an incorrect state somewhere during a hard shutdown? I had the system lock up a few times while interacting with the firefox browser prior to installing a proprietary nvidia driver to replace the default open-source one. I've put a lot of effort into configuring stuff and adding personal package choices and such at this point and would like to try to avoid wiping the USB stick and starting over with a fresh installation.

User avatar
Jerry3904
Administrator
Posts: 23103
Joined: Wed Jul 19, 2006 6:13 am

Re: MX Fluxbox: touchpad-indicator fails to start, gives error message

#4 Post by Jerry3904 »

I've never seen this problem before, but I do see a lot of hits when I google the full error message--you might want to take a look. Here's a general explanation that might be helpful:

https://www.geeksforgeeks.org/how-to-fi ... attribute/

And there are lots of others. I'm sure other Forum users here know much more than I do about this (the bar is very low...)

In my hack-a-hack approach, I would first delete the config file (~/config/touchpad-indicator/touchpad-indicator.conf), log out and back in and launch it. If that doesn't work, purge the app and then reinstall. After that, I have nothing to suggest except struggle through that linked page.
Production: 5.10, MX-23 Xfce, AMD FX-4130 Quad-Core, GeForce GT 630/PCIe/SSE2, 16 GB, SSD 120 GB, Data 1TB
Personal: Lenovo X1 Carbon with MX-23 Fluxbox
Other: Raspberry Pi 5 with MX-23 Xfce Raspberry Pi Respin

Post Reply

Return to “MX Fluxbox Official Release”