Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#78941 - got many same unclear message in qjackctl
Attached to Project:
Arch Linux
Opened by MMMM (Mikkk) - Saturday, 01 July 2023, 13:50 GMT
Last edited by Toolybird (Toolybird) - Saturday, 01 July 2023, 22:54 GMT
Opened by MMMM (Mikkk) - Saturday, 01 July 2023, 13:50 GMT
Last edited by Toolybird (Toolybird) - Saturday, 01 July 2023, 22:54 GMT
|
DetailsDescription:
since the last upgrade I got many same unclear message in qjackctl: "qt.qpa.input.events: scroll event from unregistered device a" only the device name change from "a" to "e". I tried to reboot jack, the system. I still get the message. Additional info: qjackctl 0.9.1 qt 6.5.1 jack 1.9.22 Steps to reproduce: just run qjackctl. please, let me know if you don't reproduce.= |
This task depends upon
Closed by Toolybird (Toolybird)
Saturday, 01 July 2023, 22:54 GMT
Reason for closing: Works for me
Additional comments about closing: See comments
Saturday, 01 July 2023, 22:54 GMT
Reason for closing: Works for me
Additional comments about closing: See comments
Comment by MMMM (Mikkk) -
Saturday, 01 July 2023, 14:01 GMT
I feel that it maybe comes from a kvm box I use on this computer. When I switch on the other system. If it's the case I don't understand why qjackctl care about keyboard. is there a way to tell qjackctl to ignore disconnect events from a device?
Comment by MMMM (Mikkk) -
Saturday, 01 July 2023, 14:22 GMT
the appearance of the messages seems to be the same time as the appearance of the "udev worker" processes as children of the "sytemd-udevd" process.
Comment by Toolybird (Toolybird) -
Saturday, 01 July 2023, 22:54 GMT
Cannot repro, and there is no evidence of an Arch packaging bug here. This kind of issue is more suited to the proper support channels (Forum/IRC/Mailing Lists/Reddit/etc). Please follow up there.