[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926110 Title: Apps interface flickering To manage notifications about thi

[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) (prog-i

[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

[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 politic

[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) (suc

[Bug 1910421] [NEW] Evince crashes on an unreadable nonempty postscript file owned by root

2021-01-06 Thread Md Ayquassar
Public bug reported: Package: evince Version: 3.38.0-1 I run an up-to-date groovy 20.10. This is how to reproduce the segfault: root@host:/tmp# rm mwe.ps root@host:/tmp# echo "test" > mwe.ps root@host:/tmp# chmod g-rwx,o-rwx mwe.ps root@host:/tmp# exit logout user@host:/tmp$ evince mwe.ps Segme

[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890186 Title: Failed to call EVIOCSKEYCODE with scan code 0xc022d, and key code 10

[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) 2.35

[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

[Bug 1905108] Re: Cannot fax with HP Envy Photo 7800 All-in-One

2020-11-20 Thread Md Ayquassar
** Description changed: I use Ubuntu 20.10 with hplip 3.20.5+dfsg0-3build1. The AiO fax is physically attached to the router via the fax cable and via the Ethernet cable, and my Ubuntu machine communicates with the router through WiFi. Printing from Ubuntu works, faxing directly with the

[Bug 1905108] Re: Cannot fax with HP Envy Photo 7800 All-in-One

2020-11-20 Thread Md Ayquassar
** Description changed: I use Ubuntu 20.10 with hplip 3.20.5+dfsg0-3build1. The AiO fax is physically attached to the router via the fax cable and via the Ethernet cable, and my Ubuntu machine communicates with the router through WiFi. - Printing works, but not faxing (except by making the

[Bug 1905108] Re: Cannot fax with HP Envy Photo 7800 All-in-One

2020-11-20 Thread Md Ayquassar
** Description changed: I use Ubuntu 20.10 with hplip 3.20.5+dfsg0-3build1. The AiO fax is physically attached to the router via the fax cable and via the Ethernet cable, and my Ubuntu machine communicates with the router through WiFi. Printing works, but not faxing. I tried several ways

[Bug 1905108] [NEW] Cannot fax with HP Envy Photo 7800 All-in-One

2020-11-20 Thread Md Ayquassar
Public bug reported: I use Ubuntu 20.10 with hplip 3.20.5+dfsg0-3build1. The AiO fax is physically attached to the router via the fax cable and via the Ethernet cable, and my Ubuntu machine communicates with the router through WiFi. Printing works, but not faxing. I tried several ways of sending

[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

[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:

[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: DEVPA

[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 vend

[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 vend

[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 /dev/i

[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890186 Title: Failed to call EVIOCSKEYCODE with sca

[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: M

[Bug 1890467] Re: wmi_bus wmi_bus-PNP0C14:00: WQBC data block query control method not found

2020-08-05 Thread Md Ayquassar
By the way, I know the BIOS is outdated (A21 instead of A24), but I failed to update it via FreeDOS process. (The manual https://wiki.ubuntuusers.de/BIOS_aktualisieren is partially out of date in this point or I do something wrong, but it's a different issue anyway, having little to do with this ve

[Bug 1890467] Re: wmi_bus wmi_bus-PNP0C14:00: WQBC data block query control method not found

2020-08-05 Thread Md Ayquassar
Result of `sudo acpidump > acpi.log` attached. As for USB issues: 1. I sometimes experience bad contact to my iPhone when I charge it using a USB port. This seems to be a physically bad contact to me, however, but I cannot tell for sure. 2. Another issue is that after a USB thumb drive has been

[Bug 1890467] Re: wmi_bus wmi_bus-PNP0C14:00: WQBC data block query control method not found

2020-08-05 Thread Md Ayquassar
I won't run the suggested command (apport-collect 1890467), as is doesn't anonymize or pseudonymize my data or the data of the laptop sufficiently. If given an opportunity to do so manually and paste the result using the Web interface, I will gladly proceed. ** Changed in: linux (Ubuntu) S

[Bug 1890467] [NEW] wmi_bus wmi_bus-PNP0C14:00: WQBC data block query control method not found

2020-08-05 Thread Md Ayquassar
Public bug reported: I run the kernel 5.4.0-42-generic on a fully up-to-date Ubuntu "focal" on Dell Latitude E6440. While scrolling through the output of `journalctl -b` I came across a warning (marked yellow): [0.659825] wmi_bus wmi_bus-PNP0C14:00: WQBC data block query control method not

[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 Ev

[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890186

[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

[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

[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 skipped.

[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 r

[Bug 1837326] Re: platform eisa.0: EISA: Cannot allocate resource for mainboard

2020-07-27 Thread Md Ayquassar
Same for me here on Ubuntu focal. # uname -a Linux undisclosedHostName 5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Jul 27 14:42:41 undisclosedHostName kernel: device-mapper: uevent: version 1.0.3 Jul 27 14:42:41 undisclosedHostName kernel: device-

[Bug 1870994] Re: "*BAD*gran_size: 64K chunk_size: 32M num_reg: 10 lose cover RAM: -18M" in dmesg

2020-07-03 Thread Md Ayquassar
See #6. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870994 Title: "*BAD*gran_size: 64Kchunk_size: 32M num_reg: 10

[Bug 1870994] Re: "*BAD*gran_size: 64K chunk_size: 32M num_reg: 10 lose cover RAM: -18M" in dmesg

2020-07-03 Thread Md Ayquassar
Provide me with a method to anonymize my data... ** Changed in: linux (Ubuntu) Status: Expired => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870994 Title: "*BAD*gran_size: 64Kchu

[Bug 1822674] Re: aspell-de: replace instantiieren with instanziieren

2020-07-02 Thread Md Ayquassar
Bug still present in focal as of today. ** Package changed: texlive-extra (Ubuntu) => aspell-de (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822674 Title: aspell-de: replace instantiiere

[Bug 1829061] Re: long rightwards double arrow ⟹ should be longer and rightwards double arrow ⇒ should be shorter

2020-07-02 Thread Md Ayquassar
As of now, on Ubuntu Focal, the long one arrow seems to be really longer than the short one, although the font file /usr/share/fonts/truetype/ubuntu/UbuntuMono-R.ttf seems to be still old (still dating 2011). The issue has probably been fixed. Please double- check and close if necessary. -- You r

[Bug 1765220] Re: Latexmk uses deprecated function File::Glob::glob()

2020-07-02 Thread Md Ayquassar
** Changed in: latexmk (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1765220 Title: Latexmk uses deprecated function File::Glob::glob() To manage n

[Bug 1765220] Re: Latexmk uses deprecated function File::Glob::glob()

2020-07-02 Thread Md Ayquassar
Looks fixed to me as of now in focal. @auerswal : Still present for you? If not, please close or suggest closing the issue report. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1765220 Title: Late

[Bug 1769147] Re: Please update cleveref in texlive-latex-extra

2020-07-02 Thread Md Ayquassar
Looks updated to 0.21.4 in focal. Thx, please feel free to close the issue repoirt. ** Changed in: texlive-extra (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/b

[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1837245 Title: Failed to bump fs.file-max, ignoring: Invalid argument To manage notifications about this bug go to:

[Bug 1867209] Re: evince crashes on searching in a PDF file

2020-07-02 Thread Md Ayquassar
I've tried to reproduce the issue with evince 3.36.5 that has just been release into focal. The bug seems to be gone, at least as far as the two PDF files from the internet (mentioned above) are concerned. -- You received this bug notification because you are a member of Ubuntu Bugs, which is su

[Bug 1867209] Re: evince crashes on searching in a PDF file

2020-07-02 Thread Md Ayquassar
Thanks for handling this!!! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867209 Title: evince crashes on searching in a PDF file To manage notifications about this bug go to: https://bugs.launchp

[Bug 1870994] Re: "*BAD*gran_size: 64K chunk_size: 32M num_reg: 10 lose cover RAM: -18M" in dmesg

2020-06-06 Thread Md Ayquassar
@janitor I won't do "apport-collect ", since I do wish to anonymize my private data and the laptop data before it goes here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870994 Title: "*BAD*gran_s

[Bug 1870995] Re: i8042: Warning: Keylock active

2020-05-20 Thread Md Ayquassar
Alright; thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870995 Title: i8042: Warning: Keylock active To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/

[Bug 1870995] Re: i8042: Warning: Keylock active

2020-05-20 Thread Md Ayquassar
I don't even have PS/2 mouse/keyboard ports on the machine in question. They are only present on the docking station. If the computer is not plugged into the docking station, the warning still appears. If the computer is plugged into the docking station, USB keyboard and USB mouse are used. --

[Bug 1870995] Re: i8042: Warning: Keylock active

2020-05-20 Thread Md Ayquassar
If WHAT doesn't affect normal usage? As all computers, the computer in question suffers various issues of varying degree of severity from time to time, starting with (luckily, extremely seldom) shutting itsself off without warning and ending with dozens of warning printfs scattered over dozens of

[Bug 1870994] Re: "*BAD*gran_size: 64K chunk_size: 32M num_reg: 10 lose cover RAM: -18M" in dmesg

2020-04-06 Thread Md Ayquassar
** Description changed: - While looking at a dmesg on an up-to-date eoan, I found certain lines - containing *BAD* and "can not find optimal value", "please specify...". - For me, they are just intimidating printfs. Should I get worried? + While looking at the attached dmesg on an up-to-date eoan

[Bug 1870994] Re: "*BAD*gran_size: 64K chunk_size: 32M num_reg: 10 lose cover RAM: -18M" in dmesg

2020-04-05 Thread Md Ayquassar
@Ubuntu Kernel Bot: I won't do "apport-collect ", since I have to manually anonymize my private data and the laptop data before it goes here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870994 Titl

[Bug 1703964] Re: ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042F conflicts with OpRegion 0x0000000000000400-0x000000000000047F (\PMIO) (20170119/utaddress-247)

2020-04-05 Thread Md Ayquassar
Btw., the messages for me is slightly different as far as the numbers are concerned, e.g.: [0.556821] ACPI Warning: SystemIO range 0x1828-0x182F conflicts with OpRegion 0x1800-0x183F (\_SB.PCI0.EHC2.E1PM) (20190703/utaddress-204) -- You receive

[Bug 1703964] Re: ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042F conflicts with OpRegion 0x0000000000000400-0x000000000000047F (\PMIO) (20170119/utaddress-247)

2020-04-05 Thread Md Ayquassar
Since the above is a warning, I feel, ergo, warned. But I don't know about what. I usually expect to get warned the following way: "If you do this and that, you run into such and such kind of trouble". Now, what is it that I get warned about in this case? I have various kinds of problems wi

[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 that

[Bug 1870994] [NEW] "*BAD*gran_size: 64K chunk_size: 32M num_reg: 10 lose cover RAM: -18M" in dmesg

2020-04-05 Thread Md Ayquassar
Public bug reported: While looking at a dmesg on an up-to-date eoan, I found certain lines containing *BAD* and "can not find optimal value", "please specify...". For me, they are just intimidating printfs. Should I get worried? ** Affects: linux (Ubuntu) Importance: Undecided Stat

[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 Bugs, which is

[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bu

[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 add

[Bug 1867209] Re: evince crashes on searching in a PDF file

2020-03-12 Thread Md Ayquassar
** Description changed: Package: evince Version: 3.34.1-1 In the up-to-date Ubuntu 19.10 "eoan", Evince crashes when searching in a particular long PDF file. I open the file, press Ctrl+F to open a search string box, and type in some string that occurs in the document. Then, Evince

[Bug 1867209] [NEW] evince crashes on searching in a PDF file

2020-03-12 Thread Md Ayquassar
Public bug reported: Package: evince Version: 3.34.1-1 In the up-to-date Ubuntu 19.10 "eoan", Evince crashes when searching in a particular long PDF file. I open the file, press Ctrl+F to open a search string box, and type in some string that occurs in the document. Then, Evince starts searching

[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847896 Title: Unable to shutdown or restart from log-in screen To manage notifications a

[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847896 Title: Unable to shutdown or restart from log-in screen To manage notifications ab

[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 Bugs, which is subscribed to Ubuntu. https://b

[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 notific

[Bug 1849151] [NEW] Reboot and Powerdown buttons don't work in eoan

2019-10-21 Thread Md Ayquassar
*** This bug is a duplicate of bug 1847896 *** https://bugs.launchpad.net/bugs/1847896 Public bug reported: After an upgrade to eoan, the reboot and poweroff buttons on the login screen (from the pulldown menu in the right upper corner) stopped working. I.e., clicking them hides the menu, but

[Bug 1838110] [NEW] "Zustanden" with capital "Z" is not a German word but the spellchecker does not compalin

2019-07-26 Thread Md Ayquassar
Public bug reported: Package: emacs Version: 1:26.1+1-3.2ubuntu2 Distribution: 19.04 disco. How to reproduce: 1) Open an empty text file in emacs 2) Type in the following German sentence without the quotation marks: "Wir sprechen von Zustanden in diesem Fall." 3) M-x ispell-change-dictionary[

[Bug 1836067] Re: Consider reenabling png to eps conversion in ImageMagick in disco

2019-07-10 Thread Md Ayquassar
Note: convert file.png file.eps shouldn't parse any Postscript code, but rather generate it from image data. Can re-enabling be done by locally by a user? (Instead of globally for all the users.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed t

[Bug 1836067] [NEW] Consider reenabling png to eps conversion in ImageMagick in disco

2019-07-10 Thread Md Ayquassar
Public bug reported: $ lsb_release -d Description:Ubuntu 19.04 $ convert file.png file.eps convert-im6.q16: attempt to perform an operation not allowed by the security policy `EPS' @ error/constitute.c/IsCoderAuthorized/408. $ aptitude show imagemagick | egrep -i "(Version)|(Instal)" Versio

[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829785 Title: Evince: ∞ not found To manage notifications about this bug go to: https://bugs.laun

[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829785 Title: Evince: ∞ not fou

[Bug 1829785] Re: Evince: ∞ not found

2019-05-20 Thread Md Ayquassar
Sebastien, though the Russians the same symbol in mathematics for the infinity, the infinity symbol ∞ itself is not Cyrillic. Have you tested their solution, whatever it may be, simply to make sure that that's the same issue? -- You received this bug notification because you are a member of Ubun

[Bug 1829785] [NEW] Evince: ∞ not found

2019-05-20 Thread Md Ayquassar
Public bug reported: Package: evince Version: 3.32.0-1ubuntu0.1 OS: Disco 19.04 How to reproduce: 1) Open the attached document in Evince 2) Select the infinity symbol ∞ (U+221E) and copy it into clipboard 3) Press Ctrl+F and paste the symbol from the clipboard into the search field 4) Observe

[Bug 1829061] [NEW] long rightwards double arrow ⟹ should be longer and rightwards double arrow ⇒ should be shorter

2019-05-14 Thread Md Ayquassar
Public bug reported: Package: emacs Version: 1:26.1+1-3.2ubuntu2 How to reproduce: 1) Run emacs-gtk 2) Enter the text in the title ("long rightwards double arrow ⟹ should be longer and rightwards double arrow ⇒ should be shorter") into the scratch buffer 3) Observe that ⟹ (U+21D2) is shown sho

[Bug 1829061] Re: long rightwards double arrow ⟹ should be longer and rightwards double arrow ⇒ should be shorter

2019-05-14 Thread Md Ayquassar
** Attachment added: "Emacs screenshot" https://bugs.launchpad.net/ubuntu/+source/emacs/+bug/1829061/+attachment/5263706/+files/screenshot.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829061

[Bug 1822674] [NEW] aspell-de: replace instantiieren with instanziieren

2019-04-01 Thread Md Ayquassar
Public bug reported: Package: aspell-de Version: 20161207-5 I'm using Ubuntu cosmic. How to reproduce: 1) Run any of aspell -d de_DE-neu -a aspell -d de-neu -a 2) Type in instantiieren instanziieren 3) Observe that aspell knows the version with "t", but not with "z". However, www.duden.de s

[Bug 1769147] Re: Please update cleveref in texlive-latex-extra

2018-05-04 Thread Md Ayquassar
for me and produces - to known ill effects in a document over 400 pages that heavily uses + no known ill effects in a document over 400 pages that heavily uses cleveref. Thanks in advance, Md Ayquassar -- You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 1765220] Re: Latexmk uses deprecated function File::Glob::glob()

2018-05-04 Thread Md Ayquassar
** Description changed: Upon doing `latexmk -c `, I got Latexmk: This is Latexmk, John Collins, 1 January 2015, version: 4.41. File::Glob::glob() will disappear in perl 5.30. Use File::Glob::bsd_glob() instead. at /usr/bin/latexmk line 3259 - So far, no ill effects except this printf.

[Bug 1769147] [NEW] Please update cleveref in texlive-latex-extra

2018-05-04 Thread Md Ayquassar
ll effects in a document over 400 pages that heavily uses cleveref. Thanks in advance, Md Ayquassar ** Affects: texlive-extra (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubu

[Bug 1765220] [NEW] Latexmk uses deprecated function File::Glob::glob()

2018-04-18 Thread Md Ayquassar
Public bug reported: Upon doing `latexmk -c `, I got Latexmk: This is Latexmk, John Collins, 1 January 2015, version: 4.41. File::Glob::glob() will disappear in perl 5.30. Use File::Glob::bsd_glob() instead. at /usr/bin/latexmk line 3259 So far, no ill effects except this printf. I guess, whoe