[Bug 1923660] Re: Remote control events repeat several times

2021-07-04 Thread Martin Heckenbach
*** This bug is a duplicate of bug 1926030 *** https://bugs.launchpad.net/bugs/1926030 I can confirm that the problem is fixed in Ubuntu 20.04 with kernel 5.8.0-59 Issue is solved. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1923660] [NEW] Remote control events repeat several times

2021-04-13 Thread Martin Heckenbach
Public bug reported: I think that after latest kernel update to Linux 5.8.0-49-generic there is an issue related (at least) to IR remote control input devices. After a key is pressed the event is repeated 95 times. This is not related to lirc. This behaviour can be seen by utilizing evtest. After

[Bug 1747115] Re: scanbd does not find scanner

2018-12-01 Thread Martin Heckenbach
I've just tried to configure scanbd under Ubuntu 18.10 and ran into same trouble. Scanner device is available: # scanimage -L device `plustek:libusb:002:007' is a Canon CanoScan LiDE25 flatbed scanner But after starting scanbd it terminates with message that it is not available: # scanbd -f -d 7

[Bug 1747115] Re: scanbd does not find scanner

2019-03-17 Thread Martin Heckenbach
Remote access does not work as well e.g. by using the Windows client SaneTwain I'm uncertain if this is related to previuos issue. But it worked in Ubuntu 16.04. Error message in syslog is: Mar 17 08:18:00 my-desktop saned[26802]: saned (AF-indep+IPv6) from sane-backends 1.0.27 starting up Mar

[Bug 1747115] Re: scanbd does not find scanner

2018-12-08 Thread Martin Heckenbach
I made the next step. After I have changed the user from saned to root in scanbd.conf I am able to start scanbd and it starts polling the usb device. scanbd.conf looks like this now: # drop priviliges to this user #= # Linux (most distributions use the saned user): #

[Bug 1747115] Re: scanbd does not find scanner

2018-12-08 Thread Martin Heckenbach
Finally, the following is what works for me: It seems that there is the need to change users to root at several places: 1. /etc/scanbd/scanbd.conf Change user so that it is 'root' instead of 'saned' # drop priviliges to this user #= # Linux (m

[Bug 1769848] Re: wodim no longer works from non-root accounts

2018-12-11 Thread Martin Heckenbach
I also see this problem in Ubuntu 18.10 cosmic: $ wodim -prcap wodim: Operation not permitted. Warning: Cannot raise RLIMIT_MEMLOCK limits. wodim: Resource temporarily unavailable. Cannot get mmap for 12587008 Bytes on /dev/zero. Kernel is: Linux 4.18.0-12-generic #13-Ubuntu SMP Wed Nov 14 15:

[Bug 1769848] Re: wodim no longer works from non-root accounts

2019-01-20 Thread Martin Heckenbach
I found this solution, see https://bugzilla.redhat.com/show_bug.cgi?id=1580021 sudo chmod u+s /usr/bin/wodim ** Bug watch added: Red Hat Bugzilla #1580021 https://bugzilla.redhat.com/show_bug.cgi?id=1580021 -- You received this bug notification because you are a member of Ubuntu Bugs, which

[Bug 1949262] Re: Power Savings doesn't turn monitor off on NUC8i5INH

2021-11-17 Thread Martin Heckenbach
I run Ubuntu Budgie 21.10. Since two days before turning off display after idle went well (DPMS mode). Since yesterday turning off display doesn't work anymore. The display goes black for a second but then it comes back again. However, the screen is frozen (no repainting) as long as I use the desk