[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#899241: marked as done (Amplifier detected by source from program developer but not by Debian package.)

Your message dated Tue, 16 Jul 2024 12:50:13 +0200
with message-id <ZpZQZSh-B9EZpz8A@hjemme.reinholdtsen.name>
and subject line Re: Amplifier detected by source from program developer but not by Debian package.
has caused the Debian Bug report #899241,
regarding Amplifier detected by source from program developer but not by Debian package.
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
899241: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899241
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: mustang-plug
Version: 1.2-1+b1
Severity: grave

PROBLEM
Dear Maintainer,

I own a Mustang IV and Mustang I (both v2) and am used to using the Fender Fuse software to control both (this works perfectly with both). I have a reasonably solid understanding of Linux, have come across your "Plug" package and would like to use it.

Before I was aware of your package, I had installed the Plug software directly from the develope's website (v1.2). The install went perfectly:
 - unpacked to /home/me/Programs/Plug,
 - ran: apt install qt4.dev libusb-1.0-0-dev
 - ran: qmake plug.pro
 - ran make (lots of output...)
 - ran: export PATH=$PATH:/home/me/Programs/Plug
Entering "plug" into a terminal as user "me", ran the program and it showed sound patches I had saved in both amps themselves. So... great: connection no problem, loading from amps, no problem.

Then I became aware of your package and, as always, would prefer to use the Stretch repos than source. So, I installed your package. It installed with no error or messages.

I connected to my Mustang I. It connected immediately and I was able to load the sound patches from the amp. Great. But when I connected to my Mustang IV... nothing. 

So, I checked the developer's website and there was some advice...
 - I checked the existence of the group "plugdev"; it existed and I was already a member of it.
 - I followed the developer's advice to create a file called "50-mustang.rules" in /etc/udev/rules.d and added the following to it:

***
SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", ATTRS{idVendor}=="1ed8", ATTRS{idProduct}=="0004", GROUP="plugdev"
SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", ATTRS{idVendor}=="1ed8", ATTRS{idProduct}=="0005", GROUP="plugdev"
SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", ATTRS{idVendor}=="1ed8", ATTRS{idProduct}=="0006", GROUP="plugdev"
SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", ATTRS{idVendor}=="1ed8", ATTRS{idProduct}=="0007", GROUP="plugdev"
SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", ATTRS{idVendor}=="1ed8", ATTRS{idProduct}=="0010", GROUP="plugdev"
SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", ATTRS{idVendor}=="1ed8", ATTRS{idProduct}=="0011", GROUP="plugdev"
SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", ATTRS{idVendor}=="1ed8", ATTRS{idProduct}=="0012", GROUP="plugdev"
SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", ATTRS{idVendor}=="1ed8", ATTRS{idProduct}=="0013", GROUP="plugdev"
SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", ATTRS{idVendor}=="1ed8", ATTRS{idProduct}=="0014", GROUP="plugdev"
SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", ATTRS{idVendor}=="1ed8", ATTRS{idProduct}=="0015", GROUP="plugdev"
SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", ATTRS{idVendor}=="1ed8", ATTRS{idProduct}=="0016", GROUP="plugdev"
SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", ATTRS{idVendor}=="1ed8", ATTRS{idProduct}=="0017", GROUP="plugdev
***
 - restarted udev.
Nothing: the Mustang I still worked; the Mustang IV, no joy.

 - I added myself to the udev group. No joy.
 - I updated firmware using FUSE, no joy.
END PROBLEM

REPORTBUG OUTPUT
-- System Information:
Debian Release: 9.4
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-6-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages mustang-plug depends on:
ii  libc6           2.24-11+deb9u3
ii  libgcc1         1:6.3.0-18+deb9u1
ii  libqt4-network  4:4.8.7+dfsg-11
ii  libqtcore4      4:4.8.7+dfsg-11
ii  libqtgui4       4:4.8.7+dfsg-11
ii  libstdc++6      6.3.0-18+deb9u1
ii  libusb-1.0-0    2:1.0.21-1

mustang-plug recommends no packages.

mustang-plug suggests no packages.

-- no debconf information
END REPORTBUG OUTPUT


Just ask for anything else you need. Happy to send more information, outputs from diagnostic commands, etc.
Cheers,
Mike

--- End Message ---


--- Begin Message ---


Version: 1.2-3

As far as I can tell, the udev rule has been part of the package since
version 1.1-2, and the access should be granted to members of the
plugdev group upon installation.

The proper solution is of course to use the uaccess tag, granting access
to console users even without changing any group membership, and I will
submit a patch for this shortly.

In the mean time, I close this as resolved.
-- 
Happy hacking
Petter Reinholdtsen

--- End Message ---







Reply to: