hen I have run "ink -p usb" and got the expected result:
ink 0.5.3 (c) 2018 Markus Heinz
hp deskjet 5550
Black: 0%
Color: 0%
Therefore with the updated libusb packages the segfault does not occur anymore.
Thank you f
** Attachment added: "whoopsie file for incident added"
https://bugs.launchpad.net/ubuntu/+source/libusb-1.0/+bug/1973091/+attachment/5588779/+files/_usr_bin_ink.1000.crash
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bu
** Tags added: jammy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1973091
Title:
Ubuntu 22.04: libusb-1.0.25 breaks libinklevel and ink
To manage notifications about this bug go to:
https://bugs.l
To my knowledge this issue is not related to the Linux kernel, but to
the libusb-1.0-0 package.
** Changed in: libusb-1.0 (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.lau
** Package changed: linux (Ubuntu) => libusb-1.0 (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1973091
Title:
Ubuntu 22.04: libusb-1.0.25 breaks libinklevel and ink
To manage notifications
/libc.so.6
#8 0x5795 in ?? ()
I have compiled libusb-1.0.26 into my $HOME and pointed LD_LIBRARY_PATH
to it. Then I get the expected result:
ink -p usb
ink 0.5.3 (c) 2018 Markus Heinz
hp deskjet 5550
Black: 0%
Color: 0
The 14.04 Ubuntu kernel "Linux computer4 3.13.0-77-generic #121-Ubuntu
SMP Wed Jan 20 10:50:42 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux"
successfully resolves the described issue.
Thank you very much.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
Mathias Nyman wrote me:
"I'll revert the patch e210c422b6fdd2dc123bedc588f399aefd8bf9de "xhci:
don't finish a TD if we get a short transfer event mid TD" after 4.5 rc1
is out, and send the revert to stable kernels."
--
You received this bug notification because you are a member of Ubuntu
Bugs, w
I have reported this issue upstream:
http://article.gmane.org/gmane.linux.usb.general/136182
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1529077
Title:
USB device resets since kernel version 3.13
I have tested the kernel "Linux computer4 3.13.0-75-generic #119-Ubuntu
SMP Mon Jan 11 13:49:34 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux" from
the trusty-proposed repository. It resolves the described issue
successfully.
** Tags removed: verification-needed-trusty
** Tags added: verification-done-t
As I wrote in the bug description with the distribution kernel "Linux
computer4 3.13.0-71-generic #114-Ubuntu SMP Tue Dec 1 02:34:22 UTC 2015
x86_64 x86_64 x86_64 GNU/Linux" everything is fine.
I have just checked it again: When I boot with the above kernel version,
the CD player application detec
I have tested with the following kernel:
Linux computer4 4.4.0-040400rc7-generic #201512272230 SMP Mon Dec 28
03:32:16 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
The behaviour is the same as with Linux computer4 3.13.0-74-generic
#118-Ubuntu SMP Thu Dec 17 22:52:10 UTC 2015 x86_64 x86_64 x86_64
GNU/
** Tags added: kernel-bug-exists-upstream kernel-bug-exists-
upstream-4.4-rc7
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1529077
Title:
USB device resets since kernel version 3.13.0-73-generic #1
The computer model is a MSI Windbox DC111-W10374G50XX. If you need more
information or want me to test something let me know.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1529077
Title:
USB device
Public bug reported:
I am using Ubuntu 14.04 with Gnome desktop.
When running "goobox" (a cd-player application) the application hangs
for about 30 seconds before being initialized. During this one core of
the cpu is running at 100% utilization. The following lines appear then
in the syslog:
Dec
15 matches
Mail list logo