[Touch-packages] [Bug 1829785] Re: Evince: ∞ not found

2019-05-24 Thread Md Ayquassar
I've tested the updated version on the input file. Looks good so far, job well done! Feel free to close the bug report. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to poppler in Ubuntu.

[Touch-packages] [Bug 1829785] Re: Evince: ∞ not found

2019-05-24 Thread Md Ayquassar
And thanks very much for the fast and good solution! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1829785 Title: Evince: ∞ not found Status in Evince: Fix Released

[Touch-packages] [Bug 1847896] Re: Unable to shutdown or restart from log-in screen

2019-11-15 Thread Md Ayquassar
@paulw2u My apologies. After double-checking, I found out that (for whatever reason) eoan-proposed were disabled for me. I'll retest and report here if an update doesn't help. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to

[Touch-packages] [Bug 1847896] Re: Unable to shutdown or restart from log-in screen

2019-11-15 Thread Md Ayquassar
After a few tests, I confirm that the bug looks fixed to me. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1847896 Title: Unable to shutdown or restart from log-in

[Touch-packages] [Bug 1847896] Re: Unable to shutdown or restart from log-in screen

2019-11-15 Thread Md Ayquassar
After a few tests, I confirm that the bug looked fixed to me. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1847896 Title: Unable to shutdown or restart from log-in

[Touch-packages] [Bug 1847896] Re: Unable to shutdown or restart from log-in screen

2019-11-15 Thread Md Ayquassar
Same for me as of this today: logging off, then navigating through the menu in the right upper screen corner till the turn-off button and then clicking it produces no effect in eoan. ** Changed in: systemd (Ubuntu Eoan) Status: Fix Committed => In Progress -- You received this bug

[Touch-packages] [Bug 1835660] Re: initramfs unpacking failed

2020-04-05 Thread Md Ayquassar
After "update-grub; update-initramfs -c -k all; update-grub" and a reboot, the message disappeared on the boot after the reboot. We'll see what happens next. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in

[Touch-packages] [Bug 1835660] Re: initramfs unpacking failed

2020-04-05 Thread Md Ayquassar
Same message for me. The grub menu waits for at least 6 seconds, I think, instead of 0. I won't try anything crazy out before new package version(s) appears, as it is a production system, and I can't repair it in case booting fails. Attachment: the initial part of the dmesg log. ** Attachment

[Touch-packages] [Bug 1837245] Re: Failed to bump fs.file-max, ignoring: Invalid argument

2020-04-05 Thread Md Ayquassar
Same for me on eoan 19.10. The corresponding dmesg prefix is attached. ** Attachment added: "dmesg.log" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1837245/+attachment/5347373/+files/dmesg.log -- You received this bug notification because you are a member of Ubuntu Touch seeded

[Touch-packages] [Bug 1870995] [NEW] i8042: Warning: Keylock active

2020-04-05 Thread Md Ayquassar
Public bug reported: I see "i8042: Warning: Keylock active" in my dmesg. Since this is a warning, I get, ergo, warned. Well, about what do I get warned? I feel warned, but I don't know what's wrong and what do I have to avoid doing so that I don't get into trouble. Is there an issue there

[Touch-packages] [Bug 1835660] Re: initramfs unpacking failed

2020-08-03 Thread Md Ayquassar
I recall that on one of my machines I had exactly the same situation as reported in #20 and #21 up to the timings (5.3.0-26-generic in Ubuntu 19.10 with EFI Secure Boot and dual boot with Windows 10, fastboot/hibernation disabled, LZ4 image by default, booting failed often, booting succeeded upon

[Touch-packages] [Bug 1890186] Re: Failed to call EVIOCSKEYCODE with scan code 0xc022d, and key code 103: Invalid argument

2020-08-03 Thread Md Ayquassar
@ddstreet : Will do. Before commenting out # Microsoft Natural Ergonomic Keyboard 4000 evdev:input:b0003v045Ep00DB* KEYBOARD_KEY_c022d=up # zoomin KEYBOARD_KEY_c022e=down from /lib/udev/hwdb.d/60-keyboard.hwdb , the output of `sudo evtest` is this: No device

[Touch-packages] [Bug 1890186] Re: Failed to call EVIOCSKEYCODE with scan code 0xc022d, and key code 103: Invalid argument

2020-08-03 Thread Md Ayquassar
I commented the lines out as shown here: $ grep -A 4 Ergonomic /lib/udev/hwdb.d/60-keyboard.hwdb # # Microsoft Natural Ergonomic Keyboard 4000 # evdev:input:b0003v045Ep00DB* # KEYBOARD_KEY_c022d=up # zoomin # KEYBOARD_KEY_c022e=down

[Touch-packages] [Bug 1890186] [NEW] Failed to call EVIOCSKEYCODE with scan code 0xc022d, and key code 103: Invalid argument

2020-08-03 Thread Md Ayquassar
Public bug reported: I run an up-to-date Ubuntu 20.04.1 LTS "focal" with kernel 5.4.0-42-generic on Dell Latitude E6440. Upon examining the output of journalctl -b, I see this: Aug 03 19:22:15 pseudonymizedHostname systemd[1]: Condition check resulted in Show Plymouth Boot Screen being

[Touch-packages] [Bug 1890186] Re: Failed to call EVIOCSKEYCODE with scan code 0xc022d, and key code 103: Invalid argument

2020-08-03 Thread Md Ayquassar
@ddstreet Similar stuff happens when I choose device 9 instead of device 8 and the lines /lib/udev/hwdb.d/60-keyboard.hwdb are still commented out. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu.

[Touch-packages] [Bug 1890186] Re: Failed to call EVIOCSKEYCODE with scan code 0xc022d, and key code 103: Invalid argument

2020-08-03 Thread Md Ayquassar
@ddstreet However, if in sudo evtest I choose device 9 instead of device 8 and the lines /lib/udev/hwdb.d/60-keyboard.hwdb are in their original state (i.e., active), I get this when pressing the slider up then down: Event: time 1596495480.180989, type 4 (EV_MSC), code 4 (MSC_SCAN), value c022d

[Touch-packages] [Bug 1890186] Re: Failed to call EVIOCSKEYCODE with scan code 0xc022d, and key code 103: Invalid argument

2020-08-13 Thread Md Ayquassar
With the original file /lib/udev/hwdb.d/60-keyboard.hwdb : # udevadm info /dev/input/event8 P: /devices/platform/lis3lv02d/input/input9/event8 N: input/event8 L: 0 S: input/by-path/platform-lis3lv02d-event E: DEVPATH=/devices/platform/lis3lv02d/input/input9/event8 E: DEVNAME=/dev/input/event8 E:

[Touch-packages] [Bug 1890186] Re: Failed to call EVIOCSKEYCODE with scan code 0xc022d, and key code 103: Invalid argument

2020-08-13 Thread Md Ayquassar
Please ignore #8: at new boot, the device numbers have changed :-(. Sorry, will post anew in short. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1890186 Title: Failed

[Touch-packages] [Bug 1890186] Re: Failed to call EVIOCSKEYCODE with scan code 0xc022d, and key code 103: Invalid argument

2020-08-13 Thread Md Ayquassar
After commenting the corresponding lines /lib/udev/hwdb.d/60-keyboard.hwdb out, issuing # systemd-hwdb update and rebooting, the middle slider up/down keys stopped producing any effect completely at least in Firefox (i.e., it got worse). The "Failed to call ..." error is gone from the output of

[Touch-packages] [Bug 1890186] Re: Failed to call EVIOCSKEYCODE with scan code 0xc022d, and key code 103: Invalid argument

2020-08-13 Thread Md Ayquassar
I rebooted once again to ensure that `sudo evtest` returns /dev/input/event8: Microsoft Natural® Ergonomic Keyboard 4000 /dev/input/event9: Microsoft Natural® Ergonomic Keyboard 4000 The results of # udevadm info /dev/input/event8 # udevadm info /dev/input/event9 # evemu-describe

[Touch-packages] [Bug 1890186] Re: Failed to call EVIOCSKEYCODE with scan code 0xc022d, and key code 103: Invalid argument

2020-08-13 Thread Md Ayquassar
# evemu-describe /dev/input/event9 # EVEMU 1.3 # Kernel: 5.4.0-42-generic # DMI: dmi:bvnDellInc.:bvrA21:bd02/01/2018:svnDellInc.:pnLatitudeE6440:pvr00:rvnDellInc.:rn02P3T1:rvrA00:cvnDellInc.:ct9:cvr: # Input device name: "Microsoft Natural® Ergonomic Keyboard 4000" # Input device ID: bus 0x03

[Touch-packages] [Bug 1890186] Re: Failed to call EVIOCSKEYCODE with scan code 0xc022d, and key code 103: Invalid argument

2020-08-13 Thread Md Ayquassar
# udevadm info /dev/input/event9 P: /devices/pci:00/:00:14.0/usb3/3-13/3-13.1/3-13.1:1.1/0003:045E:00DB.0003/input/input10/event9 N: input/event9 L: 0 S: input/by-path/pci-:00:14.0-usb-0:13.1:1.1-event-kbd S: input/by-id/usb-Microsoft_Natural®_Ergonomic_Keyboard_4000-if01-event-kbd E:

[Touch-packages] [Bug 1890186] Re: Failed to call EVIOCSKEYCODE with scan code 0xc022d, and key code 103: Invalid argument

2020-08-13 Thread Md Ayquassar
# udevadm info /dev/input/event8 P: /devices/pci:00/:00:14.0/usb3/3-13/3-13.1/3-13.1:1.0/0003:045E:00DB.0002/input/input9/event8 N: input/event8 L: 0 S: input/by-id/usb-Microsoft_Natural®_Ergonomic_Keyboard_4000-event-kbd S: input/by-path/pci-:00:14.0-usb-0:13.1:1.0-event-kbd E:

[Touch-packages] [Bug 1890186] Re: Failed to call EVIOCSKEYCODE with scan code 0xc022d, and key code 103: Invalid argument

2020-08-13 Thread Md Ayquassar
# evemu-describe /dev/input/event8 # EVEMU 1.3 # Kernel: 5.4.0-42-generic # DMI: dmi:bvnDellInc.:bvrA21:bd02/01/2018:svnDellInc.:pnLatitudeE6440:pvr00:rvnDellInc.:rn02P3T1:rvrA00:cvnDellInc.:ct9:cvr: # Input device name: "Microsoft Natural® Ergonomic Keyboard 4000" # Input device ID: bus 0x03

[Touch-packages] [Bug 1837245] Re: Failed to bump fs.file-max, ignoring: Invalid argument

2020-07-02 Thread Md Ayquassar
Looks fixed to me in focal. Thx!!! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1837245 Title: Failed to bump fs.file-max, ignoring: Invalid argument Status in systemd

[Touch-packages] [Bug 1890186] Re: Failed to call EVIOCSKEYCODE with scan code 0xc022d, and key code 103: Invalid argument

2020-12-24 Thread Md Ayquassar
In the meantime, I updated Ubuntu to groovy 20.10. My dmesg is [0.00] microcode: microcode updated early to revision 0x28, date = 2019-11-12 [0.00] Linux version 5.8.0-33-generic (buildd@lgw01-amd64-036) (gcc (Ubuntu 10.2.0-13ubuntu1) 10.2.0, GNU ld (GNU Binutils for Ubuntu)

[Touch-packages] [Bug 1890186] Re: Failed to call EVIOCSKEYCODE with scan code 0xc022d, and key code 103: Invalid argument

2020-12-24 Thread Md Ayquassar
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1890186 Title: Failed to call EVIOCSKEYCODE with scan

[Touch-packages] [Bug 1890186] Re: Failed to call EVIOCSKEYCODE with scan code 0xc022d, and key code 103: Invalid argument

2020-12-13 Thread Md Ayquassar
This command would disclose potentially sensitive information of a production machine to the public; I won't do it unless given an opportunity to anonymize the results upfront. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you

[Touch-packages] [Bug 1890186] Re: Failed to call EVIOCSKEYCODE with scan code 0xc022d, and key code 103: Invalid argument

2021-01-24 Thread Md Ayquassar
@ddstreet Thanks for the feedback. The keyboard has “Microsoft® Natural® Ergonomic Keyboard 4000 v1.0”, “Model 1048” printed on its bottom. The keyboard looks pretty standard to me from outside. Do you really mean it's broken? Is any combination of the sliding key with any modifier key(s)

[Touch-packages] [Bug 1926110] Re: Apps interface flickering

2021-04-30 Thread Md Ayquassar
After switching from X on groove to wayland on hirsute, I see no flickering. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1926110 Title: Apps interface flickering Status

[Touch-packages] [Bug 1926110] Re: Apps interface flickering

2021-04-28 Thread Md Ayquassar
Same flickering effect for me on groovy. I don't know which packages got updates back then. As for now, I run 5.8.0-50 and don't have older kernels. The videocard is this: 00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller (rev 06)

[Touch-packages] [Bug 1890186] Re: Failed to call EVIOCSKEYCODE with scan code 0xc022d, and key code 103: Invalid argument

2021-03-10 Thread Md Ayquassar
Yes, Ctrl + zooms in and out. If we believe https://www.microsoft.com/accessories/en-ww/products/keyboards/natural- ergonomic-keyboard-4000/b2m-00012 (though my model is not B2M-00012 but 1048) , Microsoft intended the zoom slider on the keyboard to map to zoom in and out, too. -- You received

[Touch-packages] [Bug 1890186] Re: Failed to call EVIOCSKEYCODE with scan code 0xc022d, and key code 103: Invalid argument

2021-02-28 Thread Md Ayquassar
@ddstreet Thank for the explanation. (Myself, I don't know why the keyboard behaves this way; I can imagine any option, e.g., a glitch of the keyboard firmware or hardware, an unintended bug introduced by the developers of the manufacturer, a cost-reducing design of the manufacturer, or an