Bug #11781
closedUbuntu Unity: Click USB thumb drive icon brings up Chirp(!)
0%
Description
Steps to reproduce the problem:
Vanilla Ubuntu 24.04.1 (with Unity interface), updated from the repository today (15-Jan-2025)
Chirp 20250110 installed from the whl file, thus:
** Execute these commands from a terminal:
*** pipx install --system-site-packages chirp-20250110-py3-none-any.whl
*** pipx ensurepath
*** Verified that ~/.local/bin/chirp is present
*** Verified that ~/.local/bin is in $PATH
Login as a normal unprivileged user
Insert a USB thumb drive
Wait for the USB thumb drive icon to appear on the left side of the screen
Click that icon, expecting a file manager to appear.
Unexpectedly, Chirp starts(!). The expected file manager never appears.
Updated by Andy Stewart 5 months ago
Update:
On another computer, I installed vanilla Ubuntu, updated it, installed python3-wxgtk4.0 and pipx, and then installed chirp 20250110 from the whl file. I could not reproduce this problem, so clearly something else is happening on my system.
As crazy as this bug probably sounds, there is precedent in a similar issue that happened with the USB thumb drive icon and VS code:
https://usercomp.com/news/1399992/change-default-usb-stick-app-on-ubuntu-unity
If you have any clues where I should look, that would be appreciated. I think I've shown that this probably isn't a CHIRP bug, but I can't fathom what I did on my system to create this situation.
73,
Andy
Updated by Dan Smith 5 months ago
- Status changed from New to Closed
Hi Andy,
In short, I have no idea. Installing the whl file doesn't do anything with file associations or run any scripts (it actually can't do this), nor install any files outside of the python module directory. Now, chirp files end in .img which is also used for "disk image" files in some places. Is it possible you had another distro (or other) chirp package installed at some point that associated chirp with disk images? That's the closest thing I can think of between your USB device and chirp.
Anyway, as you say, this is not a chirp bug I imagine, so I'll close this. Obviously if you figure out something that requires action from us, let me know.