[Bug 2055012] Re: When I upgraded from 22.04 to 24.04, DNS resolution went wrong.
I have also faced the issue ... Same manner. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055012 Title: When I upgraded from 22.04 to 24.04, DNS resolution went wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2055012/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967630] Re: gnome-weather fails to use dark theme
I have enabled the proposed updates and the new update to gnome-weather has fixed the dark theming issue that I was facing. Thank you. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967630 Title: gnome-weather fails to use dark theme To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-weather/+bug/1967630/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969690] [NEW] gnome-weather fails to respect Yaru-dark theme
Public bug reported: gnome-weather fails to respect Yaru-dark theme If I use, GTK_THEME=Yaru-dark gnome-weather Gnome-weather respects dark version of yaru theme then. Another user in Ubuntu forums has reported that he is facing the same bug. forum link: https://ubuntuforums.org/showthread.php?t=2473957 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-weather 41.0-3 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Apr 21 05:27:40 2022 InstallationDate: Installed on 2022-04-18 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220417) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/fish SourcePackage: gnome-weather UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-weather (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969690 Title: gnome-weather fails to respect Yaru-dark theme To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-weather/+bug/1969690/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955638] [NEW] gimp crashed when applying filter
Public bug reported:
```
GNU Image Manipulation Program version 2.10.22
git-describe: GIMP_2_10_20-217-g0c8a7891f7
Build: unknown rev 0 for linux
# C compiler #
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/10/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none:amdgcn-amdhsa:hsa
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu
10.2.1-23ubuntu1' --with-bugurl=file:///usr/share/doc/gcc-10/README.Bugs
--enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++,m2 --prefix=/usr
--with-gcc-major-version-only --program-suffix=-10
--program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id
--libexecdir=/usr/lib --without-included-gettext --enable-threads=posix
--libdir=/usr/lib --enable-nls --enable-bootstrap --enable-clocale=gnu
--enable-libstdcxx-debug --enable-libstdcxx-time=yes
--with-default-libstdcxx-abi=new --enable-gnu-unique-object
--disable-vtable-verify --enable-plugin --enable-default-pie --with-system-zlib
--enable-libphobos-checking=release --with-target-system-zlib=auto
--enable-objc-gc=auto --enable-multiarch --disable-werror --with-arch-32=i686
--with-abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib
--with-tune=generic
--enable-offload-targets=nvptx-none=/build/gcc-10-p9aljy/gcc-10-10.2.1/debian/tmp-nvptx/usr,amdgcn-amdhsa=/build/gcc-10-p9aljy/gcc-10-10.2.1/debian/tmp-gcn/usr,hsa
--without-cuda-driver --enable-checking=release --build=x86_64-linux-gnu
--host=x86_64-linux-gnu --target=x86_64-linux-gnu
--with-build-config=bootstrap-lto-lean --enable-link-mutex
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 10.2.1 20210312 (Ubuntu 10.2.1-23ubuntu1)
# Libraries #
using babl version 0.1.86 (compiled against version 0.1.86)
using GEGL version 0.4.28 (compiled against version 0.4.28)
using GLib version 2.68.1 (compiled against version 2.67.5)
using GdkPixbuf version 2.42.2 (compiled against version 2.42.2)
using GTK+ version 2.24.33 (compiled against version 2.24.33)
using Pango version 1.48.2 (compiled against version 1.48.2)
using Fontconfig version 2.13.1 (compiled against version 2.13.1)
using Cairo version 1.16.0 (compiled against version 1.16.0)
```
> fatal error: Aborted
Stack trace:
```
# Stack traces obtained from PID 25678 - Thread 25680 #
[New LWP 25680]
[New LWP 25681]
[New LWP 25682]
[New LWP 25683]
[New LWP 25684]
[New LWP 25688]
[New LWP 26566]
syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
Id Target Id Frame
* 1LWP 25678 "gimp-2.10" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
2LWP 25680 "worker" __libc_read (nbytes=256, buf=0x7f8bca745d50,
fd=15) at ../sysdeps/unix/sysv/linux/read.c:26
3LWP 25681 "worker" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
4LWP 25682 "worker" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
5LWP 25683 "gmain" 0x7f8bcbb3922f in __GI___poll
(fds=0x5645dc62caf0, nfds=2, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29
6LWP 25684 "gdbus" 0x7f8bcbb3922f in __GI___poll
(fds=0x5645dc33e930, nfds=2, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29
7LWP 25688 "async" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
8LWP 26566 "swap writer" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
Thread 8 (LWP 26566 "swap writer"):
#0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
No locals.
#1 0x7f8bcbe34dd3 in g_cond_wait () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#2 0x7f8bcc330fed in ?? () from /lib/x86_64-linux-gnu/libgegl-0.4.so.0
No symbol table info available.
#3 0x7f8bcbe15901 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#4 0x7f8bcbc22450 in start_thread (arg=0x7f8ba137f640) at
pthread_create.c:473
ret =
pd = 0x7f8ba137f640
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {140237681980992,
8408066658678394346, 140721729150206, 140721729150207, 0, 140237681980992,
-8378887201457123862, -8378696898004595222}, mask_was_saved = 0}}, priv = {pad
= {0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0, canceltype = 0}}}
not_first_call = 0
#5 0x7f8bcbb44d53 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95
No locals.
Thread 7 (LWP 25688 "async"):
#0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
No locals.
#1 0x7f8bcbe34dd3 in g_cond_wait () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#2 0x5645da80274f in ?? ()
No symbol table info available.
#3 0x7f8bcbe15901 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#4 0x7f8bcbc22450 in start_thread
[Bug 1955637] [NEW] gimp crashed when applying filter
Public bug reported:
```
GNU Image Manipulation Program version 2.10.22
git-describe: GIMP_2_10_20-217-g0c8a7891f7
Build: unknown rev 0 for linux
# C compiler #
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/10/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none:amdgcn-amdhsa:hsa
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu
10.2.1-23ubuntu1' --with-bugurl=file:///usr/share/doc/gcc-10/README.Bugs
--enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++,m2 --prefix=/usr
--with-gcc-major-version-only --program-suffix=-10
--program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id
--libexecdir=/usr/lib --without-included-gettext --enable-threads=posix
--libdir=/usr/lib --enable-nls --enable-bootstrap --enable-clocale=gnu
--enable-libstdcxx-debug --enable-libstdcxx-time=yes
--with-default-libstdcxx-abi=new --enable-gnu-unique-object
--disable-vtable-verify --enable-plugin --enable-default-pie --with-system-zlib
--enable-libphobos-checking=release --with-target-system-zlib=auto
--enable-objc-gc=auto --enable-multiarch --disable-werror --with-arch-32=i686
--with-abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib
--with-tune=generic
--enable-offload-targets=nvptx-none=/build/gcc-10-p9aljy/gcc-10-10.2.1/debian/tmp-nvptx/usr,amdgcn-amdhsa=/build/gcc-10-p9aljy/gcc-10-10.2.1/debian/tmp-gcn/usr,hsa
--without-cuda-driver --enable-checking=release --build=x86_64-linux-gnu
--host=x86_64-linux-gnu --target=x86_64-linux-gnu
--with-build-config=bootstrap-lto-lean --enable-link-mutex
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 10.2.1 20210312 (Ubuntu 10.2.1-23ubuntu1)
# Libraries #
using babl version 0.1.86 (compiled against version 0.1.86)
using GEGL version 0.4.28 (compiled against version 0.4.28)
using GLib version 2.68.1 (compiled against version 2.67.5)
using GdkPixbuf version 2.42.2 (compiled against version 2.42.2)
using GTK+ version 2.24.33 (compiled against version 2.24.33)
using Pango version 1.48.2 (compiled against version 1.48.2)
using Fontconfig version 2.13.1 (compiled against version 2.13.1)
using Cairo version 1.16.0 (compiled against version 1.16.0)
```
> fatal error: Aborted
Stack trace:
```
# Stack traces obtained from PID 25678 - Thread 25680 #
[New LWP 25680]
[New LWP 25681]
[New LWP 25682]
[New LWP 25683]
[New LWP 25684]
[New LWP 25688]
[New LWP 26566]
syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
Id Target Id Frame
* 1LWP 25678 "gimp-2.10" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
2LWP 25680 "worker" __libc_read (nbytes=256, buf=0x7f8bca745d50,
fd=15) at ../sysdeps/unix/sysv/linux/read.c:26
3LWP 25681 "worker" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
4LWP 25682 "worker" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
5LWP 25683 "gmain" 0x7f8bcbb3922f in __GI___poll
(fds=0x5645dc62caf0, nfds=2, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29
6LWP 25684 "gdbus" 0x7f8bcbb3922f in __GI___poll
(fds=0x5645dc33e930, nfds=2, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29
7LWP 25688 "async" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
8LWP 26566 "swap writer" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
Thread 8 (LWP 26566 "swap writer"):
#0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
No locals.
#1 0x7f8bcbe34dd3 in g_cond_wait () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#2 0x7f8bcc330fed in ?? () from /lib/x86_64-linux-gnu/libgegl-0.4.so.0
No symbol table info available.
#3 0x7f8bcbe15901 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#4 0x7f8bcbc22450 in start_thread (arg=0x7f8ba137f640) at
pthread_create.c:473
ret =
pd = 0x7f8ba137f640
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {140237681980992,
8408066658678394346, 140721729150206, 140721729150207, 0, 140237681980992,
-8378887201457123862, -8378696898004595222}, mask_was_saved = 0}}, priv = {pad
= {0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0, canceltype = 0}}}
not_first_call = 0
#5 0x7f8bcbb44d53 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95
No locals.
Thread 7 (LWP 25688 "async"):
#0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
No locals.
#1 0x7f8bcbe34dd3 in g_cond_wait () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#2 0x5645da80274f in ?? ()
No symbol table info available.
#3 0x7f8bcbe15901 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#4 0x7f8bcbc22450 in start_thread
[Bug 1942176] [NEW] While printing the printer is printing an error message on the sheet cups_handleerror
Public bug reported:
When using the printer it prints this on the sheet:
___
userdict dup(\004)cvn{}put (\004\004)cvn{}put
/cups_handleerror{
2B$error /newerror false put
(:PostScript error in") print cups_query_keywords print (": ) print
$error /errorname get 128 string cvs print
(;offending command:) print $error /command get 128 string cvs print(
) print flush
} bind def
errordict /timeout {} put
/cups_query_query_keyword(?Unknown) def
_
THIS IS THE TERMINAL OUTPUT
overlord@OverLord:~$ lsmod|grep usb
usbhid 57344 0
hid 135168 2 usbhid,hid_generic
btusb 61440 0
btrtl 24576 1 btusb
btbcm 16384 1 btusb
btintel28672 1 btusb
bluetooth 638976 15 btrtl,btintel,btbcm,bnep,btusb,rfcomm
overlord@OverLord:~$ tail -f /var/log/syslog
Aug 31 12:43:40 OverLord kernel: [71467.827350] usblp 1-1.1:1.1: usblp1: USB
Bidirectional printer dev 6 if 1 alt 0 proto 2 vid 0x04B8 pid 0x08D1
Aug 31 12:43:40 OverLord systemd[1]: Started Configure Plugged-In Printer.
Aug 31 12:43:40 OverLord udev-configure-printer: add usb-001-006
Aug 31 12:43:41 OverLord udev-configure-printer: device devpath is
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.1
Aug 31 12:43:41 OverLord udev-configure-printer: MFG:EPSON MDL:L220 Series
SERN:- serial:5647584B3134343800
Aug 31 12:43:41 OverLord kernel: [71468.715833] usb 1-1.1: USB disconnect,
device number 6
Aug 31 12:43:41 OverLord kernel: [71468.716232] usblp1: removed
Aug 31 12:43:41 OverLord udev-configure-printer: remove
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1:1.1
Aug 31 12:43:48 OverLord udev-configure-printer: no corresponding CUPS device
found
Aug 31 12:43:48 OverLord systemd[1]: configure-printer@usb-001-006.service:
Succeeded.
Aug 31 12:44:33 OverLord kernel: [71520.685232] usb 1-1.1: new full-speed USB
device number 7 using ehci-pci
Aug 31 12:44:34 OverLord kernel: [71520.957538] usb 1-1.1: New USB device
found, idVendor=04b8, idProduct=08d1, bcdDevice= 1.00
Aug 31 12:44:34 OverLord kernel: [71520.957549] usb 1-1.1: New USB device
strings: Mfr=1, Product=2, SerialNumber=3
Aug 31 12:44:34 OverLord kernel: [71520.957553] usb 1-1.1: Product: EPSON L220
Series
Aug 31 12:44:34 OverLord kernel: [71520.957556] usb 1-1.1: Manufacturer: EPSON
Aug 31 12:44:34 OverLord kernel: [71520.957559] usb 1-1.1: SerialNumber:
5647584B3134343800
Aug 31 12:44:34 OverLord kernel: [71521.306906] usblp 1-1.1:1.1: usblp1: USB
Bidirectional printer dev 7 if 1 alt 0 proto 2 vid 0x04B8 pid 0x08D1
Aug 31 12:44:34 OverLord systemd[1]: Started Configure Plugged-In Printer.
Aug 31 12:44:34 OverLord udev-configure-printer: add usb-001-007
Aug 31 12:44:34 OverLord udev-configure-printer: device devpath is
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.1
Aug 31 12:44:34 OverLord udev-configure-printer: MFG:EPSON MDL:L220 Series
SERN:- serial:5647584B3134343800
Aug 31 12:44:39 OverLord kernel: [71526.576813] usblp1: removed
Aug 31 12:44:40 OverLord kernel: [71527.090914] usblp 1-1.1:1.1: usblp1: USB
Bidirectional printer dev 7 if 1 alt 0 proto 2 vid 0x04B8 pid 0x08D1
Aug 31 12:44:41 OverLord udev-configure-printer: URI contains USB serial number
Aug 31 12:44:41 OverLord udev-configure-printer: URI match:
usb://EPSON/L220%20Series?serial=5647584B3134343800=1
Aug 31 12:44:41 OverLord udev-configure-printer: URI of detected printer:
usb://EPSON/L220%20Series?serial=5647584B3134343800=1, normalized:
epson l220 series serial 5647584b3134343800 interface 1
Aug 31 12:44:41 OverLord udev-configure-printer: URI of print queue:
usb://EPSON/L220%20Series?serial=5647584B3134343800=1, normalized:
epson l220 series serial 5647584b3134343800 interface 1
Aug 31 12:44:41 OverLord udev-configure-printer: Queue
ipp://localhost/printers/L220-Series has matching device URI
Aug 31 12:44:41 OverLord udev-configure-printer: Re-enabled printer
ipp://localhost/printers/L220-Series
Aug 31 12:44:41 OverLord systemd[1]: configure-printer@usb-001-007.service:
Succeeded.
Aug 31 12:44:46 OverLord telegram-desktop_telegram-desktop.desktop[53993]:
OpenType support missing for "DAOpenSansSemibold", script 12
^C
overlord@OverLord:~$ lsusb
Bus 002 Device 040: ID 04f2:b249 Chicony Electronics Co., Ltd
Bus 002 Device 044: ID 1a2c:4c5e China Resource Semico Co., Ltd
Bus 002 Device 043: ID 1bcf:0005 Sunplus Innovation Technology Inc. Optical
Mouse
Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 004: ID 0a5c:21b4 Broadcom Corp. BCM2070 Bluetooth 2.1 + EDR
Bus 001 Device 007: ID 04b8:08d1 Seiko Epson Corp.
Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002
[Bug 1934814] [NEW] Grub Installer Chrashed and half of installation not done
Public bug reported: Its was failed to complete grub installation , its crashed and described as fatal error or crashed. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.15.10 ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckMismatches: ./boot/grub/efi.img CasperMD5CheckResult: fail CasperVersion: 1.445.1 CurrentDesktop: ubuntu:GNOME Date: Wed Jul 7 00:43:04 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) ProcEnviron: LANGUAGE=en_US.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubiquity-20.04.15.10 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934814 Title: Grub Installer Chrashed and half of installation not done To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1934814/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1933864] [NEW] Bluetooth sound card not detected.
Public bug reported: When the laptop starts then i can not turn bluetooth on, it remains off. To make bluetooth work i need to disable wifi and bluetooth hardware for a few minutes then enable it. 90 percent time it works. if this didn't start the service then enabling and disabling airplane mode works. Some times it really frustrates. kindly look at this bug. I have this old laptop through which i study. thanks in advance. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-59-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: overlord 1464 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jun 28 23:35:37 2021 InstallationDate: Installed on 2021-06-22 (6 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: Bluetooth sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/11/2011 dmi.bios.release: 15.4 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.04 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1668 dmi.board.vendor: Hewlett-Packard dmi.board.version: 08.10 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: N/A dmi.ec.firmware.release: 8.16 dmi.modalias: dmi:bvnHewlett-Packard:bvrF.04:bd02/11/2011:br15.4:efr8.16:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr059F100046100:rvnHewlett-Packard:rn1668:rvr08.10:cvnHewlett-Packard:ct10:cvrN/A: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP Pavilion g6 Notebook PC dmi.product.sku: LN246EA#A2N dmi.product.version: 059F100046100 dmi.sys.vendor: Hewlett-Packard ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1933864 Title: Bluetooth sound card not detected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1933864/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1932377] [NEW] [HDA-Intel - HDA Intel MID, playback] No sound at all. bluetooth hedphones aren connected but in built speakers are used. to make bluetooth headphones to work i need to remove them
Public bug reported: firstly bluetooth services is somehow dead. to make it work we need to disable the hardware for some time so that in power settings both wifi and bluetooth is turned off and them enable it again for bluetooth to work. and after that if bluetooth is connected automatically then the audio input and output both works from laptop and after removing and adding again the bluetooth then only output is given from headphone. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: overlord 2136 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Jun 18 09:26:55 2021 InstallationDate: Installed on 2021-01-27 (141 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID failed Symptom_Card: Built-in Audio - HDA Intel MID Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: overlord 2136 F pulseaudio Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel MID, playback] No sound at all UpgradeStatus: Upgraded to hirsute on 2021-06-08 (9 days ago) dmi.bios.date: 02/11/2011 dmi.bios.release: 15.4 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.04 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1668 dmi.board.vendor: Hewlett-Packard dmi.board.version: 08.10 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: N/A dmi.ec.firmware.release: 8.16 dmi.modalias: dmi:bvnHewlett-Packard:bvrF.04:bd02/11/2011:br15.4:efr8.16:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr059F100046100:rvnHewlett-Packard:rn1668:rvr08.10:cvnHewlett-Packard:ct10:cvrN/A: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP Pavilion g6 Notebook PC dmi.product.sku: LN246EA#A2N dmi.product.version: 059F100046100 dmi.sys.vendor: Hewlett-Packard ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1932377 Title: [HDA-Intel - HDA Intel MID, playback] No sound at all. bluetooth hedphones aren connected but in built speakers are used. to make bluetooth headphones to work i need to remove them from settings and addd them again. hp pavillion g6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1932377/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1932108] [NEW] bluetooth not starting also airplane mode is not working. laptop hp pavillion g6
Public bug reported: native bluetooth is not working.Sometimes disabling the wifi and bluetooth hardware and then enabling it again enables bluetooth. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Jun 16 11:28:58 2021 InstallationDate: Installed on 2021-01-27 (140 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) InterestingModules: bnep btusb bluetooth MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-18-generic root=UUID=35e14111-9084-42ac-baef-472ae96d2665 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to hirsute on 2021-06-08 (7 days ago) dmi.bios.date: 02/11/2011 dmi.bios.release: 15.4 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.04 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1668 dmi.board.vendor: Hewlett-Packard dmi.board.version: 08.10 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: N/A dmi.ec.firmware.release: 8.16 dmi.modalias: dmi:bvnHewlett-Packard:bvrF.04:bd02/11/2011:br15.4:efr8.16:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr059F100046100:rvnHewlett-Packard:rn1668:rvr08.10:cvnHewlett-Packard:ct10:cvrN/A: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP Pavilion g6 Notebook PC dmi.product.sku: LN246EA#A2N dmi.product.version: 059F100046100 dmi.sys.vendor: Hewlett-Packard hciconfig: hci0: Type: Primary Bus: USB BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0 DOWN RX bytes:34 acl:0 sco:0 events:3 errors:0 TX bytes:12 acl:0 sco:0 commands:4 errors:0 ** Affects: ubuntu Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1932108 Title: bluetooth not starting also airplane mode is not working. laptop hp pavillion g6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1932108/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926110] Re: Apps interface flickering
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 this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1926110/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926110] Re: Apps interface flickering
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-if 00 [VGA controller]) DeviceName: Onboard IGD Subsystem: Dell 4th Gen Core Processor Integrated Graphics Controller Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- https://bugs.launchpad.net/bugs/1926110 Title: Apps interface flickering To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1926110/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918915] [NEW] package gitweb 1:2.25.1-1ubuntu3.1 failed to install/upgrade: installed gitweb package post-installation script subprocess returned error exit status 1
Public bug reported: I was trying to install PHP and this error occurs. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: gitweb 1:2.25.1-1ubuntu3.1 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Mar 12 16:27:34 2021 ErrorMessage: installed gitweb package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2021-02-25 (15 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.4 SourcePackage: git Title: package gitweb 1:2.25.1-1ubuntu3.1 failed to install/upgrade: installed gitweb package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.apache2.conf-available.gitweb.conf: [deleted] ** Affects: git (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918915 Title: package gitweb 1:2.25.1-1ubuntu3.1 failed to install/upgrade: installed gitweb package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/git/+bug/1918915/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890186] Re: Failed to call EVIOCSKEYCODE with scan code 0xc022d, and key code 103: Invalid argument
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 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 103: Invalid argument To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890186/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890186] Re: Failed to call EVIOCSKEYCODE with scan code 0xc022d, and key code 103: Invalid argument
@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 politically intentional (against the standard!) design of the manufacturer.) As for the zoom in/out, I meant this: https://support.mozilla.org/en-US/kb/font-size-and-zoom-increase-size- of-web-pages -- 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 103: Invalid argument To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890186/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1915491] Re: Wifi adapter installed but can't be found in Settings
Hi Daniel, The problem happens again today. I follow the instructions in comments #1 and #3, yet the issue not solved. I'm attaching the files and screenshots if this helps you to figure out the problem. Note: the screenshot and rfkill.txt and iwconfig files taken while I'm facing the issue. Solution: Restart the pc when this problem occurs. [image: Screenshot from 2021-02-26 10-55-19.png] [image: Screenshot from 2021-02-26 10-56-36.png] [image: Screenshot from 2021-02-26 10-57-05.png] Sincerely, *Md Rezwanul Haque Razib* *Software Engineer* *Vivasoft Ltd.* On Mon, Feb 15, 2021 at 8:25 AM Daniel van Vugt <1915...@bugs.launchpad.net> wrote: > If the problem happens again then please follow the instructions in > comment #3. > > If no further comments are added here for 60 days then the bug will > close automatically. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1915491 > > Title: > Wifi adapter installed but can't be found in Settings > > Status in gnome-control-center package in Ubuntu: > Incomplete > > Bug description: > # Summary: > > ## Wifi Adpter Not found > > ## Steps to Reproduce: > - I don't know > > > ## Expected Results: > Wifi should always be available > > ## Problem Description: > Sometimes when startup my pc there is no wifi icon on the top right > corner menu. When checking the wifi settings on the settings window it > shows that the wifi adapter not found. But after restarting the pc, > everything back to normal again. This is happening too frequently now. > > * * * > > > Screenshot: > https://drive.google.com/file/d/1i1gyhacC9I7zDHs4vGgxra9_7uvCDOR7/view?usp=sharing > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: xorg 1:7.7+19ubuntu14 > ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 > Uname: Linux 5.8.0-43-generic x86_64 > ApportVersion: 2.20.11-0ubuntu27.16 > Architecture: amd64 > BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' > CasperMD5CheckResult: skip > CompositorRunning: None > CurrentDesktop: ubuntu:GNOME > Date: Fri Feb 12 11:13:48 2021 > DistUpgraded: Fresh install > DistroCodename: focal > DistroVariant: ubuntu > ExtraDebuggingInterest: I just need to know a workaround > GraphicsCard: >Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) > (prog-if 00 [VGA controller]) > Subsystem: Dell Latitude E7470 [1028:06dc] > InstallationDate: Installed on 2021-01-06 (36 days ago) > InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 > (20200731) > MachineType: Dell Inc. Latitude E7470 > ProcEnviron: >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/usr/bin/zsh > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-43-generic > root=UUID=26d49ac7-77fe-4d5d-abbd-c857cbefc6f2 ro quiet splash vt.handoff=7 > SourcePackage: xorg > Symptom: display > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 08/20/2018 > dmi.bios.release: 1.20 > dmi.bios.vendor: Dell Inc. > dmi.bios.version: 1.20.3 > dmi.board.name: 047I7V > dmi.board.vendor: Dell Inc. > dmi.board.version: A00 > dmi.chassis.type: 9 > dmi.chassis.vendor: Dell Inc. > dmi.modalias: > dmi:bvnDellInc.:bvr1.20.3:bd08/20/2018:br1.20:svnDellInc.:pnLatitudeE7470:pvr:rvnDellInc.:rn047I7V:rvrA00:cvnDellInc.:ct9:cvr: > dmi.product.family: Latitude > dmi.product.name: Latitude E7470 > dmi.product.sku: 06DC > dmi.sys.vendor: Dell Inc. > version.compiz: compiz N/A > version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 > version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 > version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 > version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 > version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A > version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 > version.xserver-xorg-video-intel: xserver-xorg-video-intel > 2:2.99.917+git20200226-1 > version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1915491/+subscriptions > ** Attachment added: "Screenshot from 2021-02-26 10-55-19.png" https://bugs.launchpad.net/bugs/1915491/+attachment/5467398/+files/Screenshot%20from%202021-02-26%2010-55-19.png ** Attachment added: "Screenshot from 2021-02-26 10-56-36.png" https://bugs.launchpad.net/bugs/1915491/+attach
Re: [Bug 1915491] Re: Wifi adapter installed but can't be found in Settings
I execute the above two commands but the issue won't arise like before. after restarting the network-manager-service it just reconnected to my wifi. Sincerely, *Md Rezwanul Haque Razib* *Software Engineer* *Vivasoft Ltd.* On Sun, Feb 14, 2021 at 3:01 AM Jeremy <1915...@bugs.launchpad.net> wrote: > Power management might be crashing the driver, in terminal > > sudo sed -i 's/3/2/' > /etc/NetworkManager/conf.d/default-wifi-powersave-on.conf > systemctl restart network-manager.service > > See if it happens again > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1915491 > > Title: > Wifi adapter installed but can't be found in Settings > > Status in gnome-control-center package in Ubuntu: > Incomplete > > Bug description: > # Summary: > > ## Wifi Adpter Not found > > ## Steps to Reproduce: > - I don't know > > > ## Expected Results: > Wifi should always be available > > ## Problem Description: > Sometimes when startup my pc there is no wifi icon on the top right > corner menu. When checking the wifi settings on the settings window it > shows that the wifi adapter not found. But after restarting the pc, > everything back to normal again. This is happening too frequently now. > > * * * > > > Screenshot: > https://drive.google.com/file/d/1i1gyhacC9I7zDHs4vGgxra9_7uvCDOR7/view?usp=sharing > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: xorg 1:7.7+19ubuntu14 > ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 > Uname: Linux 5.8.0-43-generic x86_64 > ApportVersion: 2.20.11-0ubuntu27.16 > Architecture: amd64 > BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' > CasperMD5CheckResult: skip > CompositorRunning: None > CurrentDesktop: ubuntu:GNOME > Date: Fri Feb 12 11:13:48 2021 > DistUpgraded: Fresh install > DistroCodename: focal > DistroVariant: ubuntu > ExtraDebuggingInterest: I just need to know a workaround > GraphicsCard: >Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) > (prog-if 00 [VGA controller]) > Subsystem: Dell Latitude E7470 [1028:06dc] > InstallationDate: Installed on 2021-01-06 (36 days ago) > InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 > (20200731) > MachineType: Dell Inc. Latitude E7470 > ProcEnviron: >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/usr/bin/zsh > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-43-generic > root=UUID=26d49ac7-77fe-4d5d-abbd-c857cbefc6f2 ro quiet splash vt.handoff=7 > SourcePackage: xorg > Symptom: display > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 08/20/2018 > dmi.bios.release: 1.20 > dmi.bios.vendor: Dell Inc. > dmi.bios.version: 1.20.3 > dmi.board.name: 047I7V > dmi.board.vendor: Dell Inc. > dmi.board.version: A00 > dmi.chassis.type: 9 > dmi.chassis.vendor: Dell Inc. > dmi.modalias: > dmi:bvnDellInc.:bvr1.20.3:bd08/20/2018:br1.20:svnDellInc.:pnLatitudeE7470:pvr:rvnDellInc.:rn047I7V:rvrA00:cvnDellInc.:ct9:cvr: > dmi.product.family: Latitude > dmi.product.name: Latitude E7470 > dmi.product.sku: 06DC > dmi.sys.vendor: Dell Inc. > version.compiz: compiz N/A > version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 > version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 > version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 > version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 > version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A > version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 > version.xserver-xorg-video-intel: xserver-xorg-video-intel > 2:2.99.917+git20200226-1 > version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1915491/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915491 Title: Wifi adapter installed but can't be found in Settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1915491/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1915491] Re: Wifi adapter installed but can't be found in Settings
[image: Screenshot from 2021-02-14 00-14-05.png] Currently, While I'm connected to wifi, I'm getting the above output on the terminal when executing `iwconfig` command. If I face the issue again I will post the result to this mail. Sincerely, *Md Rezwanul Haque Razib* *Software Engineer* *Vivasoft Ltd.* On Sat, Feb 13, 2021 at 9:30 PM Jeremy <1915...@bugs.launchpad.net> wrote: > What results do you get from this command in terminal before and after > the issue > > iwconfig > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1915491 > > Title: > Wifi adapter installed but can't be found in Settings > > Status in gnome-control-center package in Ubuntu: > Incomplete > > Bug description: > # Summary: > > ## Wifi Adpter Not found > > ## Steps to Reproduce: > - I don't know > > > ## Expected Results: > Wifi should always be available > > ## Problem Description: > Sometimes when startup my pc there is no wifi icon on the top right > corner menu. When checking the wifi settings on the settings window it > shows that the wifi adapter not found. But after restarting the pc, > everything back to normal again. This is happening too frequently now. > > * * * > > > Screenshot: > https://drive.google.com/file/d/1i1gyhacC9I7zDHs4vGgxra9_7uvCDOR7/view?usp=sharing > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: xorg 1:7.7+19ubuntu14 > ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 > Uname: Linux 5.8.0-43-generic x86_64 > ApportVersion: 2.20.11-0ubuntu27.16 > Architecture: amd64 > BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' > CasperMD5CheckResult: skip > CompositorRunning: None > CurrentDesktop: ubuntu:GNOME > Date: Fri Feb 12 11:13:48 2021 > DistUpgraded: Fresh install > DistroCodename: focal > DistroVariant: ubuntu > ExtraDebuggingInterest: I just need to know a workaround > GraphicsCard: >Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) > (prog-if 00 [VGA controller]) > Subsystem: Dell Latitude E7470 [1028:06dc] > InstallationDate: Installed on 2021-01-06 (36 days ago) > InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 > (20200731) > MachineType: Dell Inc. Latitude E7470 > ProcEnviron: >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/usr/bin/zsh > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-43-generic > root=UUID=26d49ac7-77fe-4d5d-abbd-c857cbefc6f2 ro quiet splash vt.handoff=7 > SourcePackage: xorg > Symptom: display > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 08/20/2018 > dmi.bios.release: 1.20 > dmi.bios.vendor: Dell Inc. > dmi.bios.version: 1.20.3 > dmi.board.name: 047I7V > dmi.board.vendor: Dell Inc. > dmi.board.version: A00 > dmi.chassis.type: 9 > dmi.chassis.vendor: Dell Inc. > dmi.modalias: > dmi:bvnDellInc.:bvr1.20.3:bd08/20/2018:br1.20:svnDellInc.:pnLatitudeE7470:pvr:rvnDellInc.:rn047I7V:rvrA00:cvnDellInc.:ct9:cvr: > dmi.product.family: Latitude > dmi.product.name: Latitude E7470 > dmi.product.sku: 06DC > dmi.sys.vendor: Dell Inc. > version.compiz: compiz N/A > version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 > version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 > version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 > version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 > version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A > version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 > version.xserver-xorg-video-intel: xserver-xorg-video-intel > 2:2.99.917+git20200226-1 > version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1915491/+subscriptions > ** Attachment added: "Screenshot from 2021-02-14 00-14-05.png" https://bugs.launchpad.net/bugs/1915491/+attachment/5463384/+files/Screenshot%20from%202021-02-14%2000-14-05.png ** Attachment added: "iwconfig(wifi-conected)-output.txt" https://bugs.launchpad.net/bugs/1915491/+attachment/5463385/+files/iwconfig%28wifi-conected%29-output.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915491 Title: Wifi adapter installed but can't be found in Settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1915491/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915491] [NEW] Wifi Adpter Not found
Public bug reported: # Summary: > ## Wifi Adpter Not found ## Steps to Reproduce: - I don't know ## Expected Results: Wifi should always be available ## Problem Description: Sometimes when startup my pc there is no wifi icon on the top right corner menu. When checking the wifi settings on the settings window it shows that the wifi adapter not found. But after restarting the pc, everything back to normal again. This is happening too frequently now. * * * Screenshot: https://drive.google.com/file/d/1i1gyhacC9I7zDHs4vGgxra9_7uvCDOR7/view?usp=sharing ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Feb 12 11:13:48 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Latitude E7470 [1028:06dc] InstallationDate: Installed on 2021-01-06 (36 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. Latitude E7470 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-43-generic root=UUID=26d49ac7-77fe-4d5d-abbd-c857cbefc6f2 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/20/2018 dmi.bios.release: 1.20 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.20.3 dmi.board.name: 047I7V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.20.3:bd08/20/2018:br1.20:svnDellInc.:pnLatitudeE7470:pvr:rvnDellInc.:rn047I7V:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: Latitude dmi.product.name: Latitude E7470 dmi.product.sku: 06DC dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: ubuntu Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915491 Title: Wifi Adpter Not found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1915491/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914284] [NEW] package gzip 1.10-2ubuntu1 failed to install/upgrade: unable to make backup link of './bin/zless' before installing new version: Input/output error
Public bug reported: installing plocate before mlocate ProblemType: Package DistroRelease: Ubuntu 20.10 Package: gzip 1.10-2ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 NonfreeKernelModules: wl zfs zunicode zavl icp zcommon znvpair Architecture: amd64 Date: Tue Feb 2 19:00:41 2021 Df: ErrorMessage: unable to make backup link of './bin/zless' before installing new version: Input/output error PythonDetails: N/A SourcePackage: gzip Title: package gzip 1.10-2ubuntu1 failed to install/upgrade: unable to make backup link of './bin/zless' before installing new version: Input/output error UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gzip (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914284 Title: package gzip 1.10-2ubuntu1 failed to install/upgrade: unable to make backup link of './bin/zless' before installing new version: Input/output error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gzip/+bug/1914284/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890186] Re: Failed to call EVIOCSKEYCODE with scan code 0xc022d, and key code 103: Invalid argument
@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) (such as Ctrl, Alt, or Shift) supposed to zoom in/out say, in the Firefox Web browser? -- 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 103: Invalid argument To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890186/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1910421] [NEW] Evince crashes on an unreadable nonempty postscript file owned by root
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 Segmentation fault (core dumped) An expected outcome would be a meaningful error message instead of a crash. Thanks in advance for repairing this bug. ** Affects: evince (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1910421 Title: Evince crashes on an unreadable nonempty postscript file owned by root To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1910421/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890186] Re: Failed to call EVIOCSKEYCODE with scan code 0xc022d, and key code 103: Invalid argument
** 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 103: Invalid argument To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890186/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890186] Re: Failed to call EVIOCSKEYCODE with scan code 0xc022d, and key code 103: Invalid argument
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.1) #36-Ubuntu SMP Wed Dec 9 09:14:40 UTC 2020 (Ubuntu 5.8.0-33.36-generic 5.8.17) [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.8.0-33-generic root=UUID=e5bf110c-cf26-4c1f-8f95-84c054455347 ro [0.00] KERNEL supported cpus: [0.00] Intel GenuineIntel [0.00] AMD AuthenticAMD [0.00] Hygon HygonGenuine [0.00] Centaur CentaurHauls [0.00] zhaoxin Shanghai [0.00] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' [0.00] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers' [0.00] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers' [0.00] x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256 [0.00] x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'standard' format. [0.00] BIOS-provided physical RAM map: [0.00] BIOS-e820: [mem 0x-0x0004efff] usable [0.00] BIOS-e820: [mem 0x0004f000-0x0004] reserved [0.00] BIOS-e820: [mem 0x0005-0x0009efff] usable [0.00] BIOS-e820: [mem 0x0009f000-0x0009] reserved [0.00] BIOS-e820: [mem 0x0010-0xbead8fff] usable [0.00] BIOS-e820: [mem 0xbead9000-0xbead] ACPI NVS [0.00] BIOS-e820: [mem 0xbeae-0xbf4d4fff] usable [0.00] BIOS-e820: [mem 0xbf4d5000-0xbf9b9fff] reserved [0.00] BIOS-e820: [mem 0xbf9ba000-0xc7db2fff] usable [0.00] BIOS-e820: [mem 0xc7db3000-0xc7ff] reserved [0.00] BIOS-e820: [mem 0xc800-0xc8758fff] usable [0.00] BIOS-e820: [mem 0xc8759000-0xc87f] reserved [0.00] BIOS-e820: [mem 0xc880-0xc8f92fff] usable [0.00] BIOS-e820: [mem 0xc8f93000-0xc8ff] ACPI data [0.00] BIOS-e820: [mem 0xc900-0xca6f9fff] usable [0.00] BIOS-e820: [mem 0xca6fa000-0xca7f] ACPI NVS [0.00] BIOS-e820: [mem 0xca80-0xcbce8fff] usable [0.00] BIOS-e820: [mem 0xcbce9000-0xcbff] reserved [0.00] BIOS-e820: [mem 0xcd00-0xcf1f] reserved [0.00] BIOS-e820: [mem 0xf800-0xfbff] reserved [0.00] BIOS-e820: [mem 0xfec0-0xfec00fff] reserved [0.00] BIOS-e820: [mem 0xfed0-0xfed03fff] reserved [0.00] BIOS-e820: [mem 0xfed1c000-0xfed1] reserved [0.00] BIOS-e820: [mem 0xfee0-0xfee00fff] reserved [0.00] BIOS-e820: [mem 0xff00-0x] reserved [0.00] BIOS-e820: [mem 0x0001-0x00042edf] usable [0.00] NX (Execute Disable) protection: active [0.00] e820: update [mem 0xc5467018-0xc546fa57] usable ==> usable [0.00] e820: update [mem 0xc5467018-0xc546fa57] usable ==> usable [0.00] e820: update [mem 0xc5456018-0xc5466057] usable ==> usable [0.00] e820: update [mem 0xc5456018-0xc5466057] usable ==> usable [0.00] e820: update [mem 0xc5445018-0xc5455457] usable ==> usable [0.00] e820: update [mem 0xc5445018-0xc5455457] usable ==> usable [0.00] extended physical RAM map: [0.00] reserve setup_data: [mem 0x-0x0004efff] usable [0.00] reserve setup_data: [mem 0x0004f000-0x0004] reserved [0.00] reserve setup_data: [mem 0x0005-0x0009efff] usable [0.00] reserve setup_data: [mem 0x0009f000-0x0009] reserved [0.00] reserve setup_data: [mem 0x0010-0xbead8fff] usable [0.00] reserve setup_data: [mem 0xbead9000-0xbead] ACPI NVS [0.00] reserve setup_data: [mem 0xbeae-0xbf4d4fff] usable [0.00] reserve setup_data: [mem 0xbf4d5000-0xbf9b9fff] reserved [0.00] reserve setup_data: [mem 0xbf9ba000-0xc5445017] usable [0.00] reserve setup_data: [mem 0xc5445018-0xc5455457] usable [0.00] reserve setup_data: [mem 0xc5455458-0xc5456017] usable [0.00] reserve setup_data: [mem 0xc5456018-0xc5466057] usable [0.00] reserve setup_data: [mem 0xc5466058-0xc5467017] usable [0.00] reserve setup_data: [mem 0xc5467018-0xc546fa57] usable [0.00]
Re: [Bug 1908719] Re: "installation crashed" while installation was about to finish.
Thanks a lot for your email.. I would like to inform you that after that problem i shutted my laptop down and turned it on again and then i saw it was working properly..then It asked for some updates.. But from my curiosity i searched about it and found out the solution from askubuntu site. and that was very simple that saying not to check the box of allowing third party app before installing what i did watching youtube tutorial.. Then at the second time i didnt check that box and went for the installation process and then it worked perfectly..Now im working on ubuntu without facing any major problem till now.. I will be very thankfull to you if you kindly let me know that *is this a proper solution of that issue or not? Can i use like this in future?* And also im confused about if my laptop is ok to use linux on it? because i saw the list of certified devices thats hardware can run linux on it and theres no Acer.. So as you are an expert please can you tell me about it? My device is Acer Aspire A515-52G-57N3. *Thank you!* -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908719 Title: "installation crashed" while installation was about to finish. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1908719/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890186] Re: Failed to call EVIOCSKEYCODE with scan code 0xc022d, and key code 103: Invalid argument
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 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 103: Invalid argument To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890186/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905108] Re: Cannot fax with HP Envy Photo 7800 All-in-One
** 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 AiO machine also works, but NOT faxing from Ubuntu. I tried several ways of sending a two-page PDF through a fax, in particular several ways of choosing the fax driver and the device URI, but, never mind what I did, the fax did not get sent. For example, the recent attempt put [14447.505158] audit: type=1400 audit(1605916929.875:51): apparmor="DENIED" operation="open" profile="/usr/lib/cups/backend/cups- pdf" name="/etc/cups/" pid=11678 comm="cups-pdf" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 - into the syslog. Is it a bug? Very likely. Does it have anything to - do with faxing? Perhaps, no idea. Some of my faxing attempts ended - with the "abgebrochen" status, others with "Die Druckerkonfiguration ist - nicht korrekt oder der Drucker existiert nicht mehr." status, yet others - with "Device communication error" accompanied by Code 5012 and "Please - correct the problem and try again". Yet another attempt ended with - "FileNotFoundError: [Errno 2] No such file or directory: - \'/home/my_username/.hplip/hp_fax-pipe-146\'" deep in - /var/log/cups/error_log . + into the syslog. Is it a bug? Very likely. Does it have anything to do with faxing? Perhaps, no idea. Some of my faxing attempts ended with the "abgebrochen" status, others with "Die Druckerkonfiguration ist nicht korrekt oder der Drucker existiert nicht mehr." status, yet others with "Device communication error" accompanied by Code 5012 and "Please correct the problem and try again". Yet another attempt ended with "FileNotFoundError: [Errno 2] No such file or directory: \'/home/my_username/.hplip/hp_fax-pipe-146\'" deep in /var/log/cups/error_log . + Starting hp-toolbox prints + + error: Unable to communicate with device (code=12): hpfax:/net/ENVY_Photo_7800_series?ip=192.168.1.225 + error: Device not found + + to the console in red, although the AiO device is on. All of these are probably bugs of various kinds which probably have something to do with faxing, directly or indirectly. I guess, my main point of criticism is that it's nowhere clearly written, in a step-by-step way, how to send a fax, what to expect at each step, and what or how to troubleshoot if the expected thing does not happen. For example, https://developers.hp.com/hp-linux-imaging-and-printing/howtos/faxing mentions the "Items" tab, but on my machine, there is no such tab in hp-sendfax or hp-toolbox. The description on https://wiki.ubuntuusers.de/HPLIP/#Faxen is equivalent to empty. Yes, I did run hp-sendfax -pENVY_Photo_7800_fax -fTargetFaxNumber (where the TargetFaxNumber is 03212... in my country). In short, how on earth do I fax my PDFs from Ubuntu through HP Envy Photo 7800 All-in-One? ** 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 AiO machine also works, but NOT faxing from Ubuntu. I tried several ways of sending a two-page PDF through a fax, in particular several ways of choosing the fax driver and the device URI, but, never mind what I did, the fax did not get sent. For example, the recent attempt put [14447.505158] audit: type=1400 audit(1605916929.875:51): apparmor="DENIED" operation="open" profile="/usr/lib/cups/backend/cups- pdf" name="/etc/cups/" pid=11678 comm="cups-pdf" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 into the syslog. Is it a bug? Very likely. Does it have anything to do with faxing? Perhaps, no idea. Some of my faxing attempts ended with the "abgebrochen" status, others with "Die Druckerkonfiguration ist nicht korrekt oder der Drucker existiert nicht mehr." status, yet others with "Device communication error" accompanied by Code 5012 and "Please correct the problem and try again". Yet another attempt ended with "FileNotFoundError: [Errno 2] No such file or directory: \'/home/my_username/.hplip/hp_fax-pipe-146\'" deep in /var/log/cups/error_log . - Starting hp-toolbox prints + Starting hp-toolbox prints error: Unable to communicate with device (code=12): hpfax:/net/ENVY_Photo_7800_series?ip=192.168.1.225 error: Device not found to the console in red, although the AiO device is on. All of these are probably bugs of various kinds which probably have something to do with faxing, directly or indirectly. - I guess, my main point of criticism is that it's nowhere clearly written, in a step-by-step way, how to send a fax, what to expect at each step, and what or how
[Bug 1905108] Re: Cannot fax with HP Envy Photo 7800 All-in-One
** 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 AiO machine - physically scan the paper, but this way has nothing to do with Ubuntu). - I tried several ways of sending a two-page PDF through a fax, in - particular several ways of choosing the fax driver and the device URI, - but, never mind what I did, the fax did not get sent. For example, the - recent attempt put + Printing from Ubuntu works, faxing directly with the AiO machine also + works, but NOT faxing from Ubuntu. I tried several ways of sending a + two-page PDF through a fax, in particular several ways of choosing the + fax driver and the device URI, but, never mind what I did, the fax did + not get sent. For example, the recent attempt put [14447.505158] audit: type=1400 audit(1605916929.875:51): apparmor="DENIED" operation="open" profile="/usr/lib/cups/backend/cups- pdf" name="/etc/cups/" pid=11678 comm="cups-pdf" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 into the syslog. Is it a bug? Perhaps. Does it have anything to do with faxing? Perhaps, no idea. Some of my faxing attempts ended with the "abgebrochen" status, others with "Die Druckerkonfiguration ist nicht korrekt oder der Drucker existiert nicht mehr." status, yet others with "Device communication error" accompanied by Code 5012 and "Please correct the problem and try again". Yet another attempt ended with "FileNotFoundError: [Errno 2] No such file or directory: \'/home/my_username/.hplip/hp_fax-pipe-146\'" deep in /var/log/cups/error_log . I guess, my main point of criticism is that it's nowhere clearly written, in a step-by-step way, how to send a fax, what to expect at each step, and how to troubleshoot if the expected thing does not happen. For example, https://developers.hp.com/hp-linux-imaging-and-printing/howtos/faxing mentions the "Items" tab, but on my machine, there is no such tab in hp-sendfax or hp-toolbox. The description on https://wiki.ubuntuusers.de/HPLIP/#Faxen is equivalent to empty. Yes, I did run hp-sendfax -pENVY_Photo_7800_fax -fTargetFaxNumber (where the TargetFaxNumber is 03212... in my country). In short, how on earth do I send my PDFs to the fax? ** 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 AiO machine also works, but NOT faxing from Ubuntu. I tried several ways of sending a two-page PDF through a fax, in particular several ways of choosing the fax driver and the device URI, but, never mind what I did, the fax did not get sent. For example, the recent attempt put [14447.505158] audit: type=1400 audit(1605916929.875:51): apparmor="DENIED" operation="open" profile="/usr/lib/cups/backend/cups- pdf" name="/etc/cups/" pid=11678 comm="cups-pdf" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 into the syslog. Is it a bug? Perhaps. Does it have anything to do with faxing? Perhaps, no idea. Some of my faxing attempts ended with the "abgebrochen" status, others with "Die Druckerkonfiguration ist nicht korrekt oder der Drucker existiert nicht mehr." status, yet others with "Device communication error" accompanied by Code 5012 and "Please correct the problem and try again". Yet another attempt ended with "FileNotFoundError: [Errno 2] No such file or directory: \'/home/my_username/.hplip/hp_fax-pipe-146\'" deep in /var/log/cups/error_log . I guess, my main point of criticism is that it's nowhere clearly written, in a step-by-step way, how to send a fax, what to expect at each step, and how to troubleshoot if the expected thing does not happen. For example, https://developers.hp.com/hp-linux-imaging-and-printing/howtos/faxing mentions the "Items" tab, but on my machine, there is no such tab in hp-sendfax or hp-toolbox. The description on https://wiki.ubuntuusers.de/HPLIP/#Faxen is equivalent to empty. Yes, I did run hp-sendfax -pENVY_Photo_7800_fax -fTargetFaxNumber (where the TargetFaxNumber is 03212... in my country). - In short, how on earth do I send my PDFs to the fax? + In short, how on earth do I fax my PDFs from Ubuntu through HP Envy + Photo 7800 All-in-One? ** 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 AiO machine also works, but NOT faxing from Ubuntu. I tried several ways of
[Bug 1905108] Re: Cannot fax with HP Envy Photo 7800 All-in-One
** 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 of sending a two- page PDF through a fax, in particular several ways of choosing the fax driver and the device URI, but, never mind what I did, the fax did not get sent. For example, the recent attempt put [14447.505158] audit: type=1400 audit(1605916929.875:51): apparmor="DENIED" operation="open" profile="/usr/lib/cups/backend/cups- pdf" name="/etc/cups/" pid=11678 comm="cups-pdf" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 into the syslog. Is it a bug? Perhaps. Does it have anything to do with faxing? Perhaps, no idea. Some of my faxing attempts ended with the "abgebrochen" status, others with "Die Druckerkonfiguration ist - nicht korrekt oder der Drucker existiert nicht mehr." status. + nicht korrekt oder der Drucker existiert nicht mehr." status. Yet + another attempt ended with "FileNotFoundError: [Errno 2] No such file or + directory: \'/home/my_username/.hplip/hp_fax-pipe-146\'" deep in + /var/log/cups/error_log . I guess, my main point of criticism is that it's nowhere clearly written, in a step-by-step way, how to send a fax and what to expect at each step. For example, https://developers.hp.com/hp-linux-imaging-and- printing/howtos/faxing mentions the "Items" tab, but on my machine, there is no such tab. The description on https://wiki.ubuntuusers.de/HPLIP/#Faxen is equivalent to empty. Yes, I did run the hp-sendfax program! I short, how on earth do I send my through the fax? ** 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 of sending a two- page PDF through a fax, in particular several ways of choosing the fax driver and the device URI, but, never mind what I did, the fax did not get sent. For example, the recent attempt put [14447.505158] audit: type=1400 audit(1605916929.875:51): apparmor="DENIED" operation="open" profile="/usr/lib/cups/backend/cups- pdf" name="/etc/cups/" pid=11678 comm="cups-pdf" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 into the syslog. Is it a bug? Perhaps. Does it have anything to do with faxing? Perhaps, no idea. Some of my faxing attempts ended with the "abgebrochen" status, others with "Die Druckerkonfiguration ist nicht korrekt oder der Drucker existiert nicht mehr." status. Yet another attempt ended with "FileNotFoundError: [Errno 2] No such file or directory: \'/home/my_username/.hplip/hp_fax-pipe-146\'" deep in /var/log/cups/error_log . I guess, my main point of criticism is that it's nowhere clearly written, in a step-by-step way, how to send a fax and what to expect at each step. For example, https://developers.hp.com/hp-linux-imaging-and- printing/howtos/faxing mentions the "Items" tab, but on my machine, - there is no such tab. The description on + there is no such tab in hp-sendfax or hp-toolbox. The description on https://wiki.ubuntuusers.de/HPLIP/#Faxen is equivalent to empty. Yes, I did run the hp-sendfax program! I short, how on earth do I send my through the fax? ** 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 of sending a two- page PDF through a fax, in particular several ways of choosing the fax driver and the device URI, but, never mind what I did, the fax did not get sent. For example, the recent attempt put [14447.505158] audit: type=1400 audit(1605916929.875:51): apparmor="DENIED" operation="open" profile="/usr/lib/cups/backend/cups- pdf" name="/etc/cups/" pid=11678 comm="cups-pdf" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 into the syslog. Is it a bug? Perhaps. Does it have anything to do with faxing? Perhaps, no idea. Some of my faxing attempts ended with the "abgebrochen" status, others with "Die Druckerkonfiguration ist nicht korrekt oder der Drucker existiert nicht mehr." status. Yet another attempt ended with "FileNotFoundError: [Errno 2] No such file or directory: \'/home/my_username/.hplip/hp_fax-pipe-146\'" deep in /var/log/cups/error_log . - I guess, my main point of criticism is that it's nowhere clearly - written, in a step-by-step way, how to send a fax and what to expect at - each step. For example, https://developers.hp.com/hp-linux-imaging-and- -
[Bug 1905108] [NEW] Cannot fax with HP Envy Photo 7800 All-in-One
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 a two- page PDF through a fax, in particular several ways of choosing the fax driver and the device URI, but, never mind what I did, the fax did not get sent. For example, the recent attempt put [14447.505158] audit: type=1400 audit(1605916929.875:51): apparmor="DENIED" operation="open" profile="/usr/lib/cups/backend/cups- pdf" name="/etc/cups/" pid=11678 comm="cups-pdf" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 into the syslog. Is it a bug? Perhaps. Does it have anything to do with faxing? Perhaps, no idea. Some of my faxing attempts ended with the "abgebrochen" status, others with "Die Druckerkonfiguration ist nicht korrekt oder der Drucker existiert nicht mehr." status. I guess, my main point of criticism is that it's nowhere clearly written, in a step-by-step way, how to send a fax and what to expect at each step. For example, https://developers.hp.com/hp-linux-imaging-and- printing/howtos/faxing mentions the "Items" tab, but on my machine, there is no such tab. The description on https://wiki.ubuntuusers.de/HPLIP/#Faxen is equivalent to empty. Yes, I did run the hp-sendfax program! I short, how on earth do I send my through the fax? ** Affects: hplip (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905108 Title: Cannot fax with HP Envy Photo 7800 All-in-One To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1905108/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897242] [NEW] Xorg crash
Public bug reported: when opening software source ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: Budgie:GNOME Date: Sat Sep 26 08:36:17 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 620 [1028:0767] Subsystem: Dell Radeon R7 M445 [1028:0767] InstallationDate: Installed on 2020-09-25 (0 days ago) InstallationMedia: Ubuntu-Budgie 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. Inspiron 5567 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=488db7bf-9ea8-4ae7-bc7e-8a245481d9e2 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/24/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.10 dmi.board.name: 02YHJP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.10:bd02/24/2020:svnDellInc.:pnInspiron5567:pvr:rvnDellInc.:rn02YHJP:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5567 dmi.product.sku: 0767 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug crash focal ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897242 Title: Xorg crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1897242/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894025] [NEW] sudo do-release-upgrade doesn't work
Public bug reported: It says again & again Could not calculate the upgrade An unresolvable problem occurred while calculating the upgrade. This was likely caused by: * Unofficial software packages not provided by Ubuntu Please use the tool 'ppa-purge' from the ppa-purge package to remove software from a Launchpad PPA and try the upgrade again. If none of this applies, then please report this bug using the command 'ubuntu-bug ubuntu-release-upgrader-core' in a terminal.If you want to investigate this yourself the log files in '/var/log/dist-upgrade' will contain details about the upgrade. Specifically, look at 'main.log' and 'apt.log'. Even though I removed all broken package. I don't know what to do now ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-release-upgrader-core 1:16.04.30 ProcVersionSignature: Ubuntu 4.15.0-115.116~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-115-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.24 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: Unity Date: Thu Sep 3 12:07:09 2020 InstallationDate: Installed on 2019-05-08 (483 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190227) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to xenial on 2020-09-03 (0 days ago) ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1894025 Title: sudo do-release-upgrade doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1894025/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890186] Re: Failed to call EVIOCSKEYCODE with scan code 0xc022d, and key code 103: Invalid argument
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 journalctl -b, though. Running evtest and checking event8 produces absolutely no effect for the slider keys. Running evtest and checking event9 produces the following effect for the slider keys up (+) followed by down (-): Event: time 1597336850.366186, type 4 (EV_MSC), code 4 (MSC_SCAN), value c022d Event: time 1597336850.366186, type 1 (EV_KEY), code 418 (KEY_ZOOMIN), value 1 Event: time 1597336850.366186, -- SYN_REPORT Event: time 1597336850.510185, type 4 (EV_MSC), code 4 (MSC_SCAN), value c022d Event: time 1597336850.510185, type 1 (EV_KEY), code 418 (KEY_ZOOMIN), value 0 Event: time 1597336850.510185, -- SYN_REPORT Event: time 1597336851.454182, type 4 (EV_MSC), code 4 (MSC_SCAN), value c022e Event: time 1597336851.454182, type 1 (EV_KEY), code 419 (KEY_ZOOMOUT), value 1 Event: time 1597336851.454182, -- SYN_REPORT Event: time 1597336851.526184, type 4 (EV_MSC), code 4 (MSC_SCAN), value c022e Event: time 1597336851.526184, type 1 (EV_KEY), code 419 (KEY_ZOOMOUT), value 0 Event: time 1597336851.526184, -- SYN_REPORT I'll revert to the prior default setting of /lib/udev/hwdb.d/60-keyboard.hwdb in the meantime. -- 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 103: Invalid argument To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1890186/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890186] Re: Failed to call EVIOCSKEYCODE with scan code 0xc022d, and key code 103: Invalid argument
# 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: DEVPATH=/devices/pci:00/:00:14.0/usb3/3-13/3-13.1/3-13.1:1.1/0003:045E:00DB.0003/input/input10/event9 E: DEVNAME=/dev/input/event9 E: MAJOR=13 E: MINOR=73 E: SUBSYSTEM=input E: USEC_INITIALIZED=4185161 E: KEYBOARD_KEY_c022d=up E: KEYBOARD_KEY_c022e=down E: ID_INPUT=1 E: ID_INPUT_KEY=1 E: ID_INPUT_KEYBOARD=1 E: ID_VENDOR=Microsoft E: ID_VENDOR_ENC=Microsoft E: ID_VENDOR_ID=045e E: ID_MODEL=Natural®_Ergonomic_Keyboard_4000 E: ID_MODEL_ENC=Natural®\x20Ergonomic\x20Keyboard\x204000 E: ID_MODEL_ID=00db E: ID_REVISION=0173 E: ID_SERIAL=Microsoft_Natural®_Ergonomic_Keyboard_4000 E: ID_TYPE=hid E: ID_BUS=usb E: ID_USB_INTERFACES=:030101:03: E: ID_USB_INTERFACE_NUM=01 E: ID_USB_DRIVER=usbhid E: ID_PATH=pci-:00:14.0-usb-0:13.1:1.1 E: ID_PATH_TAG=pci-_00_14_0-usb-0_13_1_1_1 E: XKBMODEL=pc105 E: XKBLAYOUT=de E: BACKSPACE=guess E: LIBINPUT_DEVICE_GROUP=3/45e/db:usb-:00:14.0-13 E: DEVLINKS=/dev/input/by-path/pci-:00:14.0-usb-0:13.1:1.1-event-kbd /dev/input/by-id/usb-Microsoft_Natural®_Ergonomic_Keyboard_4000-if01-event-kbd E: TAGS=:power-switch: -- 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 103: Invalid argument To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1890186/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890186] Re: Failed to call EVIOCSKEYCODE with scan code 0xc022d, and key code 103: Invalid argument
# 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: DEVPATH=/devices/pci:00/:00:14.0/usb3/3-13/3-13.1/3-13.1:1.0/0003:045E:00DB.0002/input/input9/event8 E: DEVNAME=/dev/input/event8 E: MAJOR=13 E: MINOR=72 E: SUBSYSTEM=input E: USEC_INITIALIZED=4188709 E: KEYBOARD_KEY_c022d=up E: KEYBOARD_KEY_c022e=down E: ID_INPUT=1 E: ID_INPUT_KEY=1 E: ID_INPUT_KEYBOARD=1 E: ID_VENDOR=Microsoft E: ID_VENDOR_ENC=Microsoft E: ID_VENDOR_ID=045e E: ID_MODEL=Natural®_Ergonomic_Keyboard_4000 E: ID_MODEL_ENC=Natural®\x20Ergonomic\x20Keyboard\x204000 E: ID_MODEL_ID=00db E: ID_REVISION=0173 E: ID_SERIAL=Microsoft_Natural®_Ergonomic_Keyboard_4000 E: ID_TYPE=hid E: ID_BUS=usb E: ID_USB_INTERFACES=:030101:03: E: ID_USB_INTERFACE_NUM=00 E: ID_USB_DRIVER=usbhid E: ID_PATH=pci-:00:14.0-usb-0:13.1:1.0 E: ID_PATH_TAG=pci-_00_14_0-usb-0_13_1_1_0 E: XKBMODEL=pc105 E: XKBLAYOUT=de E: BACKSPACE=guess E: LIBINPUT_DEVICE_GROUP=3/45e/db:usb-:00:14.0-13 E: DEVLINKS=/dev/input/by-id/usb-Microsoft_Natural®_Ergonomic_Keyboard_4000-event-kbd /dev/input/by-path/pci-:00:14.0-usb-0:13.1:1.0-event-kbd E: TAGS=:power-switch: -- 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 103: Invalid argument To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1890186/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890186] Re: Failed to call EVIOCSKEYCODE with scan code 0xc022d, and key code 103: Invalid argument
# 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 vendor 0x45e product 0xdb version 0x111 # Supported events: # Event type 0 (EV_SYN) # Event code 0 (SYN_REPORT) # Event code 1 (SYN_CONFIG) # Event code 2 (SYN_MT_REPORT) # Event code 3 (SYN_DROPPED) # Event code 4 ((null)) # Event code 5 ((null)) # Event code 6 ((null)) # Event code 7 ((null)) # Event code 8 ((null)) # Event code 9 ((null)) # Event code 10 ((null)) # Event code 11 ((null)) # Event code 12 ((null)) # Event code 13 ((null)) # Event code 14 ((null)) # Event code 15 (SYN_MAX) # Event type 1 (EV_KEY) # Event code 1 (KEY_ESC) # Event code 2 (KEY_1) # Event code 3 (KEY_2) # Event code 4 (KEY_3) # Event code 5 (KEY_4) # Event code 6 (KEY_5) # Event code 7 (KEY_6) # Event code 8 (KEY_7) # Event code 9 (KEY_8) # Event code 10 (KEY_9) # Event code 11 (KEY_0) # Event code 12 (KEY_MINUS) # Event code 13 (KEY_EQUAL) # Event code 14 (KEY_BACKSPACE) # Event code 15 (KEY_TAB) # Event code 16 (KEY_Q) # Event code 17 (KEY_W) # Event code 18 (KEY_E) # Event code 19 (KEY_R) # Event code 20 (KEY_T) # Event code 21 (KEY_Y) # Event code 22 (KEY_U) # Event code 23 (KEY_I) # Event code 24 (KEY_O) # Event code 25 (KEY_P) # Event code 26 (KEY_LEFTBRACE) # Event code 27 (KEY_RIGHTBRACE) # Event code 28 (KEY_ENTER) # Event code 29 (KEY_LEFTCTRL) # Event code 30 (KEY_A) # Event code 31 (KEY_S) # Event code 32 (KEY_D) # Event code 33 (KEY_F) # Event code 34 (KEY_G) # Event code 35 (KEY_H) # Event code 36 (KEY_J) # Event code 37 (KEY_K) # Event code 38 (KEY_L) # Event code 39 (KEY_SEMICOLON) # Event code 40 (KEY_APOSTROPHE) # Event code 41 (KEY_GRAVE) # Event code 42 (KEY_LEFTSHIFT) # Event code 43 (KEY_BACKSLASH) # Event code 44 (KEY_Z) # Event code 45 (KEY_X) # Event code 46 (KEY_C) # Event code 47 (KEY_V) # Event code 48 (KEY_B) # Event code 49 (KEY_N) # Event code 50 (KEY_M) # Event code 51 (KEY_COMMA) # Event code 52 (KEY_DOT) # Event code 53 (KEY_SLASH) # Event code 54 (KEY_RIGHTSHIFT) # Event code 55 (KEY_KPASTERISK) # Event code 56 (KEY_LEFTALT) # Event code 57 (KEY_SPACE) # Event code 58 (KEY_CAPSLOCK) # Event code 59 (KEY_F1) # Event code 60 (KEY_F2) # Event code 61 (KEY_F3) # Event code 62 (KEY_F4) # Event code 63 (KEY_F5) # Event code 64 (KEY_F6) # Event code 65 (KEY_F7) # Event code 66 (KEY_F8) # Event code 67 (KEY_F9) # Event code 68 (KEY_F10) # Event code 69 (KEY_NUMLOCK) # Event code 70 (KEY_SCROLLLOCK) # Event code 71 (KEY_KP7) # Event code 72 (KEY_KP8) # Event code 73 (KEY_KP9) # Event code 74 (KEY_KPMINUS) # Event code 75 (KEY_KP4) # Event code 76 (KEY_KP5) # Event code 77 (KEY_KP6) # Event code 78 (KEY_KPPLUS) # Event code 79 (KEY_KP1) # Event code 80 (KEY_KP2) # Event code 81 (KEY_KP3) # Event code 82 (KEY_KP0) # Event code 83 (KEY_KPDOT) # Event code 85 (KEY_ZENKAKUHANKAKU) # Event code 86 (KEY_102ND) # Event code 87 (KEY_F11) # Event code 88 (KEY_F12) # Event code 89 (KEY_RO) # Event code 90 (KEY_KATAKANA) # Event code 91 (KEY_HIRAGANA) # Event code 92 (KEY_HENKAN) # Event code 93 (KEY_KATAKANAHIRAGANA) # Event code 94 (KEY_MUHENKAN) # Event code 95 (KEY_KPJPCOMMA) # Event code 96 (KEY_KPENTER) # Event code 97 (KEY_RIGHTCTRL) # Event code 98 (KEY_KPSLASH) # Event code 99 (KEY_SYSRQ) # Event code 100 (KEY_RIGHTALT) # Event code 102 (KEY_HOME) # Event code 103 (KEY_UP) # Event code 104 (KEY_PAGEUP) # Event code 105 (KEY_LEFT) # Event code 106 (KEY_RIGHT) # Event code 107 (KEY_END) # Event code 108 (KEY_DOWN) # Event code 109 (KEY_PAGEDOWN) # Event code 110 (KEY_INSERT) # Event code 111 (KEY_DELETE) # Event code 113 (KEY_MUTE) # Event code 114 (KEY_VOLUMEDOWN) # Event code 115 (KEY_VOLUMEUP) # Event code 116 (KEY_POWER) # Event code 117 (KEY_KPEQUAL) # Event code 119 (KEY_PAUSE) # Event code 120 (KEY_SCALE) # Event code 121 (KEY_KPCOMMA) # Event code 122 (KEY_HANGEUL) # Event code 123 (KEY_HANJA) # Event code 124 (KEY_YEN) # Event code 125 (KEY_LEFTMETA) # Event code 126 (KEY_RIGHTMETA) # Event code 127 (KEY_COMPOSE) # Event code 128 (KEY_STOP) # Event code 129 (KEY_AGAIN) # Event code 130 (KEY_PROPS) # Event code 131 (KEY_UNDO) # Event code 132 (KEY_FRONT) # Event code 133 (KEY_COPY) # Event code 134 (KEY_OPEN) # Event code 135
[Bug 1890186] Re: Failed to call EVIOCSKEYCODE with scan code 0xc022d, and key code 103: Invalid argument
# 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 vendor 0x45e product 0xdb version 0x111 # Supported events: # Event type 0 (EV_SYN) # Event code 0 (SYN_REPORT) # Event code 1 (SYN_CONFIG) # Event code 2 (SYN_MT_REPORT) # Event code 3 (SYN_DROPPED) # Event code 4 ((null)) # Event code 5 ((null)) # Event code 6 ((null)) # Event code 7 ((null)) # Event code 8 ((null)) # Event code 9 ((null)) # Event code 10 ((null)) # Event code 11 ((null)) # Event code 12 ((null)) # Event code 13 ((null)) # Event code 14 ((null)) # Event code 15 (SYN_MAX) # Event type 1 (EV_KEY) # Event code 1 (KEY_ESC) # Event code 2 (KEY_1) # Event code 3 (KEY_2) # Event code 4 (KEY_3) # Event code 5 (KEY_4) # Event code 6 (KEY_5) # Event code 7 (KEY_6) # Event code 8 (KEY_7) # Event code 9 (KEY_8) # Event code 10 (KEY_9) # Event code 11 (KEY_0) # Event code 12 (KEY_MINUS) # Event code 13 (KEY_EQUAL) # Event code 14 (KEY_BACKSPACE) # Event code 15 (KEY_TAB) # Event code 16 (KEY_Q) # Event code 17 (KEY_W) # Event code 18 (KEY_E) # Event code 19 (KEY_R) # Event code 20 (KEY_T) # Event code 21 (KEY_Y) # Event code 22 (KEY_U) # Event code 23 (KEY_I) # Event code 24 (KEY_O) # Event code 25 (KEY_P) # Event code 26 (KEY_LEFTBRACE) # Event code 27 (KEY_RIGHTBRACE) # Event code 28 (KEY_ENTER) # Event code 29 (KEY_LEFTCTRL) # Event code 30 (KEY_A) # Event code 31 (KEY_S) # Event code 32 (KEY_D) # Event code 33 (KEY_F) # Event code 34 (KEY_G) # Event code 35 (KEY_H) # Event code 36 (KEY_J) # Event code 37 (KEY_K) # Event code 38 (KEY_L) # Event code 39 (KEY_SEMICOLON) # Event code 40 (KEY_APOSTROPHE) # Event code 41 (KEY_GRAVE) # Event code 42 (KEY_LEFTSHIFT) # Event code 43 (KEY_BACKSLASH) # Event code 44 (KEY_Z) # Event code 45 (KEY_X) # Event code 46 (KEY_C) # Event code 47 (KEY_V) # Event code 48 (KEY_B) # Event code 49 (KEY_N) # Event code 50 (KEY_M) # Event code 51 (KEY_COMMA) # Event code 52 (KEY_DOT) # Event code 53 (KEY_SLASH) # Event code 54 (KEY_RIGHTSHIFT) # Event code 55 (KEY_KPASTERISK) # Event code 56 (KEY_LEFTALT) # Event code 57 (KEY_SPACE) # Event code 58 (KEY_CAPSLOCK) # Event code 59 (KEY_F1) # Event code 60 (KEY_F2) # Event code 61 (KEY_F3) # Event code 62 (KEY_F4) # Event code 63 (KEY_F5) # Event code 64 (KEY_F6) # Event code 65 (KEY_F7) # Event code 66 (KEY_F8) # Event code 67 (KEY_F9) # Event code 68 (KEY_F10) # Event code 69 (KEY_NUMLOCK) # Event code 70 (KEY_SCROLLLOCK) # Event code 71 (KEY_KP7) # Event code 72 (KEY_KP8) # Event code 73 (KEY_KP9) # Event code 74 (KEY_KPMINUS) # Event code 75 (KEY_KP4) # Event code 76 (KEY_KP5) # Event code 77 (KEY_KP6) # Event code 78 (KEY_KPPLUS) # Event code 79 (KEY_KP1) # Event code 80 (KEY_KP2) # Event code 81 (KEY_KP3) # Event code 82 (KEY_KP0) # Event code 83 (KEY_KPDOT) # Event code 86 (KEY_102ND) # Event code 87 (KEY_F11) # Event code 88 (KEY_F12) # Event code 89 (KEY_RO) # Event code 92 (KEY_HENKAN) # Event code 93 (KEY_KATAKANAHIRAGANA) # Event code 94 (KEY_MUHENKAN) # Event code 95 (KEY_KPJPCOMMA) # Event code 96 (KEY_KPENTER) # Event code 97 (KEY_RIGHTCTRL) # Event code 98 (KEY_KPSLASH) # Event code 99 (KEY_SYSRQ) # Event code 100 (KEY_RIGHTALT) # Event code 102 (KEY_HOME) # Event code 103 (KEY_UP) # Event code 104 (KEY_PAGEUP) # Event code 105 (KEY_LEFT) # Event code 106 (KEY_RIGHT) # Event code 107 (KEY_END) # Event code 108 (KEY_DOWN) # Event code 109 (KEY_PAGEDOWN) # Event code 110 (KEY_INSERT) # Event code 111 (KEY_DELETE) # Event code 113 (KEY_MUTE) # Event code 114 (KEY_VOLUMEDOWN) # Event code 115 (KEY_VOLUMEUP) # Event code 116 (KEY_POWER) # Event code 117 (KEY_KPEQUAL) # Event code 119 (KEY_PAUSE) # Event code 121 (KEY_KPCOMMA) # Event code 122 (KEY_HANGEUL) # Event code 123 (KEY_HANJA) # Event code 124 (KEY_YEN) # Event code 125 (KEY_LEFTMETA) # Event code 126 (KEY_RIGHTMETA) # Event code 127 (KEY_COMPOSE) # Event code 128 (KEY_STOP) # Event code 129 (KEY_AGAIN) # Event code 130 (KEY_PROPS) # Event code 131 (KEY_UNDO) # Event code 132 (KEY_FRONT) # Event code 133 (KEY_COPY) # Event code 134 (KEY_OPEN) # Event code 135 (KEY_PASTE) # Event code 136 (KEY_FIND) # Event code 137 (KEY_CUT) # Event code 138 (KEY_HELP) # Event code 183 (KEY_F13) #
[Bug 1890186] Re: Failed to call EVIOCSKEYCODE with scan code 0xc022d, and key code 103: Invalid argument
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/input/event8 # evemu-describe /dev/input/event9 with the original file /lib/udev/hwdb.d/60-keyboard.hwdb will be attached or posted 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 scan code 0xc022d, and key code 103: Invalid argument To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1890186/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890186] Re: Failed to call EVIOCSKEYCODE with scan code 0xc022d, and key code 103: Invalid argument
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 scan code 0xc022d, and key code 103: Invalid argument To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1890186/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890186] Re: Failed to call EVIOCSKEYCODE with scan code 0xc022d, and key code 103: Invalid argument
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: MAJOR=13 E: MINOR=72 E: SUBSYSTEM=input E: USEC_INITIALIZED=4296811 E: ID_INPUT=1 E: ID_INPUT_ACCELEROMETER=1 E: ID_PATH=platform-lis3lv02d E: ID_PATH_TAG=platform-lis3lv02d E: IIO_SENSOR_PROXY_TYPE=input-accel E: SYSTEMD_WANTS=iio-sensor-proxy.service E: LIBINPUT_DEVICE_GROUP=19/0/0:lis3lv02d E: DEVLINKS=/dev/input/by-path/platform-lis3lv02d-event E: TAGS=:systemd: # udevadm info /dev/input/event9 P: /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:4f/LNXVIDEO:00/input/input10/event9 N: input/event9 L: 0 E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:4f/LNXVIDEO:00/input/input10/event9 E: DEVNAME=/dev/input/event9 E: MAJOR=13 E: MINOR=73 E: SUBSYSTEM=input E: USEC_INITIALIZED=4230143 E: ID_INPUT=1 E: ID_INPUT_KEY=1 E: ID_PATH=acpi-LNXVIDEO:00 E: ID_PATH_TAG=acpi-LNXVIDEO_00 E: XKBMODEL=pc105 E: XKBLAYOUT=de E: BACKSPACE=guess E: LIBINPUT_DEVICE_GROUP=19/0/6:LNXVIDEO/video E: TAGS=:power-switch: # 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: "ST LIS3LV02DL Accelerometer" # Input device ID: bus 0x19 vendor product version # Supported events: # Event type 0 (EV_SYN) # Event code 0 (SYN_REPORT) # Event code 1 (SYN_CONFIG) # Event code 2 (SYN_MT_REPORT) # Event code 3 (SYN_DROPPED) # Event code 4 ((null)) # Event code 5 ((null)) # Event code 6 ((null)) # Event code 7 ((null)) # Event code 8 ((null)) # Event code 9 ((null)) # Event code 10 ((null)) # Event code 11 ((null)) # Event code 12 ((null)) # Event code 13 ((null)) # Event code 14 ((null)) # Event code 15 (SYN_MAX) # Event type 3 (EV_ABS) # Event code 0 (ABS_X) # Value -172 # Min -2304 # Max 2304 # Fuzz18 # Flat18 # Resolution 0 # Event code 1 (ABS_Y) # Value -10 # Min -2304 # Max 2304 # Fuzz18 # Flat18 # Resolution 0 # Event code 2 (ABS_Z) # Value 1178 # Min -2304 # Max 2304 # Fuzz18 # Flat18 # Resolution 0 # Properties: N: ST LIS3LV02DL Accelerometer I: 0019 P: 00 00 00 00 00 00 00 00 B: 00 0b 00 00 00 00 00 00 00 B: 01 00 00 00 00 00 00 00 00 B: 01 00 00 00 00 00 00 00 00 B: 01 00 00 00 00 00 00 00 00 B: 01 00 00 00 00 00 00 00 00 B: 01 00 00 00 00 00 00 00 00 B: 01 00 00 00 00 00 00 00 00 B: 01 00 00 00 00 00 00 00 00 B: 01 00 00 00 00 00 00 00 00 B: 01 00 00 00 00 00 00 00 00 B: 01 00 00 00 00 00 00 00 00 B: 01 00 00 00 00 00 00 00 00 B: 01 00 00 00 00 00 00 00 00 B: 02 00 00 00 00 00 00 00 00 B: 03 07 00 00 00 00 00 00 00 B: 04 00 00 00 00 00 00 00 00 B: 05 00 00 00 00 00 00 00 00 B: 11 00 00 00 00 00 00 00 00 B: 12 00 00 00 00 00 00 00 00 B: 14 00 00 00 00 00 00 00 00 B: 15 00 00 00 00 00 00 00 00 B: 15 00 00 00 00 00 00 00 00 A: 00 -2304 2304 18 18 0 A: 01 -2304 2304 18 18 0 A: 02 -2304 2304 18 18 0 # 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: "Video Bus" # Input device ID: bus 0x19 vendor product 0x06 version # Supported events: # Event type 0 (EV_SYN) # Event code 0 (SYN_REPORT) # Event code 1 (SYN_CONFIG) # Event code 2 (SYN_MT_REPORT) # Event code 3 (SYN_DROPPED) # Event code 4 ((null)) # Event code 5 ((null)) # Event code 6 ((null)) # Event code 7 ((null)) # Event code 8 ((null)) # Event code 9 ((null)) # Event code 10 ((null)) # Event code 11 ((null)) # Event code 12 ((null)) # Event code 13 ((null)) # Event code 14 ((null)) # Event code 15 (SYN_MAX) # Event type 1 (EV_KEY) # Event code 224 (KEY_BRIGHTNESSDOWN) # Event code 225 (KEY_BRIGHTNESSUP) # Event code 227 (KEY_SWITCHVIDEOMODE) # Event code 241 (KEY_VIDEO_NEXT) # Event code 242 (KEY_VIDEO_PREV) # Event code 243 (KEY_BRIGHTNESS_CYCLE) # Event code 244 (KEY_BRIGHTNESS_AUTO) # Event code 245 (KEY_DISPLAY_OFF) # Properties: N: Video Bus I: 0019 0006 P: 00 00 00 00 00 00 00 00 B: 00 0b 00 00 00 00 00 00 00 B: 01 00 00 00 00 00 00 00 00 B: 01 00 00 00 00 00 00 00 00 B: 01 00 00 00 00 00 00 00 00 B: 01 00 00 00 00 0b 00 3e 00 B: 01 00 00 00 00 00 00 00 00 B: 01 00 00 00 00 00 00 00 00 B: 01 00 00 00 00 00 00 00 00 B: 01 00 00 00 00 00 00 00 00 B: 01 00 00 00 00 00 00 00 00 B: 01 00 00 00 00 00 00 00 00
[Bug 1890467] Re: wmi_bus wmi_bus-PNP0C14:00: WQBC data block query control method not found
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 very 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/1890467 Title: wmi_bus wmi_bus-PNP0C14:00: WQBC data block query control method not found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890467/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890467] Re: wmi_bus wmi_bus-PNP0C14:00: WQBC data block query control method not found
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 unmounted via the `unmount` command, the written data may be yet in the process of being transferred, so simply taking the drive out immediately after unmounting would probably damage the file system or the drive itself or both. I need to say `udisksctl power-off -b /dev/sdb` and wait for termination to make sure that the device is really safe to unplug. As for wake-up, the laptop seldom refuses to wake up and freezes instead. I simply gave the issue as an example of what goes wrong (there are dozens of such small issues). ** Attachment added: "Result of `sudo acpidump > acpi.log`." https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890467/+attachment/5399096/+files/acpi.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890467 Title: wmi_bus wmi_bus-PNP0C14:00: WQBC data block query control method not found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890467/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890467] Re: wmi_bus wmi_bus-PNP0C14:00: WQBC data block query control method not found
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) 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/1890467 Title: wmi_bus wmi_bus-PNP0C14:00: WQBC data block query control method not found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890467/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890467] [NEW] wmi_bus wmi_bus-PNP0C14:00: WQBC data block query control method not found
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 found Now, since this is a warning, I get, ergo, warned. What is it that I get warned about? Is it just a printf or is some action required? As every computer, the laptop suffers from various problems from time to time (e.g., boot or wakeup silently hangs up while the manufacturer splash screen is displayed), so, I don't know whether this message could be related to any of such problems. Here is the context of this warning in dmesg: # dmesg | grep -B 10 -A 5 "method not found" [0.518379] rtc_cmos 00:02: setting system clock to 2020-08-05T15:23:54 UTC (1596641034) [0.519455] Freeing unused decrypted memory: 2040K [0.520119] Freeing unused kernel image memory: 2712K [0.531430] Write protecting the kernel read-only data: 22528k [0.532242] Freeing unused kernel image memory: 2008K [0.532805] Freeing unused kernel image memory: 1192K [0.540186] x86/mm: Checked W+X mappings: passed, no W+X pages found. [0.540514] x86/mm: Checking user space page tables [0.547468] x86/mm: Checked W+X mappings: passed, no W+X pages found. [0.547786] Run /init as init process [0.659825] wmi_bus wmi_bus-PNP0C14:00: WQBC data block query control method not found [0.659921] ACPI Warning: SystemIO range 0x1828-0x182F conflicts with OpRegion 0x1800-0x183F (\_SB.PCI0.EHC2.E1PM) (20190816/utaddress-204) [0.661768] ACPI Warning: SystemIO range 0x1828-0x182F conflicts with OpRegion 0x1800-0x183F (\_SB.PCI0.EHC1.E1PM) (20190816/utaddress-204) [0.663121] ACPI Warning: SystemIO range 0x1828-0x182F conflicts with OpRegion 0x1800-0x187F (\PMIO) (20190816/utaddress-204) [0.664516] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [0.666167] e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k Some more info: # ls -la /sys/devices/platform/PNP0C14:00 drwxr-xr-x 4 root root0 Aug 5 17:23 . drwxr-xr-x 29 root root0 Aug 5 17:23 .. lrwxrwxrwx 1 root root0 Aug 5 17:23 driver -> ../../../bus/platform/drivers/acpi-wmi -rw-r--r-- 1 root root 4096 Aug 5 18:09 driver_override lrwxrwxrwx 1 root root0 Aug 5 18:09 firmware_node -> ../../LNXSYSTM:00/LNXSYBUS:00/PNP0C14:00 -r--r--r-- 1 root root 4096 Aug 5 18:09 modalias drwxr-xr-x 2 root root0 Aug 5 18:09 power lrwxrwxrwx 1 root root0 Aug 5 17:23 subsystem -> ../../../bus/platform -rw-r--r-- 1 root root 4096 Aug 5 17:23 uevent drwxr-xr-x 3 root root0 Aug 5 17:23 wmi_bus # ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: focal ** Description changed: 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): + While scrolling through the output of `journalctl -b` I came across the following warning (marked yellow): [0.659825] wmi_bus wmi_bus-PNP0C14:00: WQBC data block query control method not found Now, since this is a warning, I get, ergo, warned. What is it that I get warned about? Is it just a printf or is some action required? Here is the context of this warning in dmesg: # dmesg | grep -B 10 -A 5 "method not found" [0.518379] rtc_cmos 00:02: setting system clock to 2020-08-05T15:23:54 UTC (1596641034) [0.519455] Freeing unused decrypted memory: 2040K [0.520119] Freeing unused kernel image memory: 2712K [0.531430] Write protecting the kernel read-only data: 22528k [0.532242] Freeing unused kernel image memory: 2008K [0.532805] Freeing unused kernel image memory: 1192K [0.540186] x86/mm: Checked W+X mappings: passed, no W+X pages found. [0.540514] x86/mm: Checking user space page tables [0.547468] x86/mm: Checked W+X mappings: passed, no W+X pages found. [0.547786] Run /init as init process [0.659825] wmi_bus wmi_bus-PNP0C14:00: WQBC data block query control method not found [0.659921] ACPI Warning: SystemIO range 0x1828-0x182F conflicts with OpRegion 0x1800-0x183F (\_SB.PCI0.EHC2.E1PM) (20190816/utaddress-204) [0.661768] ACPI Warning: SystemIO range 0x1828-0x182F conflicts with OpRegion 0x1800-0x183F (\_SB.PCI0.EHC1.E1PM) (20190816/utaddress-204) [0.663121] ACPI Warning: SystemIO range 0x1828-0x182F conflicts with OpRegion 0x1800-0x187F (\PMIO)
[Bug 1890186] Re: Failed to call EVIOCSKEYCODE with scan code 0xc022d, and key code 103: Invalid argument
@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 Event: time 1596495480.180989, type 1 (EV_KEY), code 103 (KEY_UP), value 1 Event: time 1596495480.180989, -- SYN_REPORT ^[[AEvent: time 1596495480.439165, type 1 (EV_KEY), code 103 (KEY_UP), value 2 Event: time 1596495480.439165, -- SYN_REPORT Event: time 1596495480.439165, type 4 (EV_MSC), code 4 (MSC_SCAN), value c022d Event: time 1596495480.439165, type 1 (EV_KEY), code 103 (KEY_UP), value 0 Event: time 1596495480.439165, -- SYN_REPORT Event: time 1596495481.621007, type 4 (EV_MSC), code 4 (MSC_SCAN), value c022e Event: time 1596495481.621007, type 1 (EV_KEY), code 108 (KEY_DOWN), value 1 Event: time 1596495481.621007, -- SYN_REPORT ^[[BEvent: time 1596495481.844992, type 4 (EV_MSC), code 4 (MSC_SCAN), value c022e Event: time 1596495481.844992, type 1 (EV_KEY), code 108 (KEY_DOWN), value 0 Event: time 1596495481.844992, -- SYN_REPORT -- 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 103: Invalid argument To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1890186/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890186] Re: Failed to call EVIOCSKEYCODE with scan code 0xc022d, and key code 103: Invalid argument
@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 Title: Failed to call EVIOCSKEYCODE with scan code 0xc022d, and key code 103: Invalid argument To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1890186/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890186] Re: Failed to call EVIOCSKEYCODE with scan code 0xc022d, and key code 103: Invalid argument
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# zoomout Then, I rebooted and ran sudo journalctl -b. I still see Aug 04 00:28:28 pseudonymizedHostname systemd-udevd[400]: event8: Failed to call EVIOCSKEYCODE with scan code 0xc022d, and key code 103: Invalid argument Aug 04 00:28:28 pseudonymizedHostname systemd-udevd[400]: event8: Failed to call EVIOCSKEYCODE with scan code 0xc022e, and key code 108: Invalid argument there. Running `sudo evest` and choosing 8 leads to this: Testing ... (interrupt to exit) Event: time 1596494194.967361, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70028 Event: time 1596494194.967361, type 1 (EV_KEY), code 28 (KEY_ENTER), value 0 Event: time 1596494194.967361, -- SYN_REPORT ^[[A^[[B The output ^[[A comes from sliding up, the output ^[[B from sliding down. So, what next? Is it possible to zoom in/out with the slider? How? -- 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 103: Invalid argument To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1890186/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890186] Re: Failed to call EVIOCSKEYCODE with scan code 0xc022d, and key code 103: Invalid argument
@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 specified, trying to scan all of /dev/input/event* Available devices: /dev/input/event0: Lid Switch /dev/input/event1: Power Button /dev/input/event2: Sleep Button /dev/input/event3: Power Button /dev/input/event4: AT Translated Set 2 keyboard /dev/input/event5: USB Optical Mouse /dev/input/event6: AlpsPS/2 ALPS DualPoint Stick /dev/input/event7: AlpsPS/2 ALPS DualPoint TouchPad /dev/input/event8: Microsoft Natural® Ergonomic Keyboard 4000 /dev/input/event9: Microsoft Natural® Ergonomic Keyboard 4000 /dev/input/event10: ST LIS3LV02DL Accelerometer /dev/input/event11: HDA Intel PCH Dock Mic /dev/input/event12: HDA Intel PCH Dock Line Out /dev/input/event13: HDA Intel PCH Front Headphone /dev/input/event14: Laptop_Integrated_Webcam_HD: In /dev/input/event15: Dell WMI hotkeys /dev/input/event16: Video Bus /dev/input/event17: Video Bus /dev/input/event18: HDA Intel HDMI HDMI/DP,pcm=3 /dev/input/event19: HDA Intel HDMI HDMI/DP,pcm=7 /dev/input/event20: HDA Intel HDMI HDMI/DP,pcm=8 /dev/input/event21: HDA Intel HDMI HDMI/DP,pcm=9 /dev/input/event22: HDA Intel HDMI HDMI/DP,pcm=10 Select the device event number [0-22]: 1) What would I choose after editing the file and rebooting? 8 or 9 or something else? 2) How are they Zoom keys supposed to work under Linux? The up/down slider scrolls for me so far. Does a combination of modifier keys (Alt, Shift, Ctrl, AltGr) have to be pressed? Should the Fn key light be on or off? -- 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 103: Invalid argument To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1890186/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890186] [NEW] Failed to call EVIOCSKEYCODE with scan code 0xc022d, and key code 103: Invalid argument
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. Aug 03 19:22:15 pseudonymizedHostname systemd[1]: Condition check resulted in Forward Password Requests to Plymouth Directory Watch being skipped. Aug 03 19:22:15 pseudonymizedHostname systemd[1]: Condition check resulted in Set Up Additional Binary Formats being skipped. Aug 03 19:22:15 pseudonymizedHostname systemd[1]: Condition check resulted in File System Check on Root Device being skipped. Aug 03 19:22:15 pseudonymizedHostname systemd[1]: Condition check resulted in Rebuild Hardware Database being skipped. Aug 03 19:22:15 pseudonymizedHostname systemd[1]: Condition check resulted in Platform Persistent Storage Archival being skipped. Aug 03 19:22:15 pseudonymizedHostname kernel: [drm] radeon: dpm initialized Aug 03 19:22:15 pseudonymizedHostname kernel: [drm] GART: num cpu pages 524288, num gpu pages 524288 Aug 03 19:22:15 pseudonymizedHostname kernel: dell_laptop: Using dell-rbtn acpi driver for receiving events Aug 03 19:22:15 pseudonymizedHostname systemd-udevd[385]: event8: Failed to call EVIOCSKEYCODE with scan code 0xc022d, and key code 103: Invalid argument Aug 03 19:22:15 pseudonymizedHostname systemd-udevd[385]: event8: Failed to call EVIOCSKEYCODE with scan code 0xc022e, and key code 108: Invalid argument "Invalid argument" means that something goes wrong there, and I don't know what it is. On my laptop, event8 seems to be keyboard-related: $ sudo cat /proc/bus/input/devices | grep -C 5 event8 I: Bus=0003 Vendor=045e Product=00db Version=0111 N: Name="Microsoft Natural® Ergonomic Keyboard 4000" P: Phys=usb-:00:14.0-13.1/input0 S: Sysfs=/devices/pci:00/:00:14.0/usb3/3-13/3-13.1/3-13.1:1.0/0003:045E:00DB.0002/input/input9 U: Uniq= H: Handlers=sysrq kbd event8 leds B: PROP=0 B: EV=120013 B: KEY=10007 ff8007ff febeffdff3cf fffe B: MSC=10 B: LED=107 The issue report https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1754921 is probably related but marked as a duplicate of a no longer existing issue report (#1750855). The report https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1597415 describes a similar issue for older kernels; the differences pertain to error message, error code, input..., and, opposed to #19 there, I have no Windows partitions (except /boot/efi vfat) in /etc/fstab; mine is not a dual-boot machine. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: focal -- 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 103: Invalid argument To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1890186/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835660] Re: initramfs unpacking failed
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 reinstall with EFI secure boot). Unfortunately, I don't have this machine any longer. @mario-gleirscher would probably be of help if they provide us with some debugging when asked by the Ubuntu maintainers. On another machine, I still have this annoying printf in dmesg (and journalctl -b): [0.215092] NET: Registered protocol family 1 [0.215096] NET: Registered protocol family 44 [0.215105] pci :00:02.0: Video device with shadowed ROM at [mem 0x000c-0x000d] [0.215670] PCI: CLS 64 bytes, default 64 [0.215696] Trying to unpack rootfs image as initramfs... [0.303126] Initramfs unpacking failed: Decoding failed [0.306614] Freeing initrd memory: 48364K I run 5.4.0-42-generic in Ubuntu 20.04.1 LTS focal. As for me, this issue seems to simply uselessly burn processor cycles (and, as every such issue, indirectly generate superfluous carbon dioxide); there is a potential for optimization here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835660 Title: initramfs unpacking failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1835660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1837326] Re: platform eisa.0: EISA: Cannot allocate resource for mainboard
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-mapper: ioctl: 4.41.0-ioctl (2019-09-16) initialised: dm-de...@redhat.com Jul 27 14:42:41 undisclosedHostName kernel: platform eisa.0: Probing EISA bus 0 Jul 27 14:42:41 undisclosedHostName kernel: platform eisa.0: EISA: Cannot allocate resource for mainboard Jul 27 14:42:41 undisclosedHostName kernel: input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input4 Jul 27 14:42:41 undisclosedHostName kernel: platform eisa.0: Cannot allocate resource for EISA slot 1 Jul 27 14:42:41 undisclosedHostName kernel: platform eisa.0: Cannot allocate resource for EISA slot 2 Jul 27 14:42:41 undisclosedHostName kernel: platform eisa.0: Cannot allocate resource for EISA slot 3 Jul 27 14:42:41 undisclosedHostName kernel: platform eisa.0: Cannot allocate resource for EISA slot 4 Jul 27 14:42:41 undisclosedHostName kernel: platform eisa.0: Cannot allocate resource for EISA slot 5 Jul 27 14:42:41 undisclosedHostName kernel: platform eisa.0: Cannot allocate resource for EISA slot 6 Jul 27 14:42:41 undisclosedHostName kernel: platform eisa.0: Cannot allocate resource for EISA slot 7 Jul 27 14:42:41 undisclosedHostName kernel: platform eisa.0: Cannot allocate resource for EISA slot 8 Jul 27 14:42:41 undisclosedHostName kernel: platform eisa.0: EISA: Detected 0 cards Certain lines (listed again below) are marked in color. If they are harmless, why mark them? Jul 27 14:42:41 undisclosedHostName kernel: platform eisa.0: EISA: Cannot allocate resource for mainboard Jul 27 14:42:41 undisclosedHostName kernel: platform eisa.0: Cannot allocate resource for EISA slot 1 Jul 27 14:42:41 undisclosedHostName kernel: platform eisa.0: Cannot allocate resource for EISA slot 2 Jul 27 14:42:41 undisclosedHostName kernel: platform eisa.0: Cannot allocate resource for EISA slot 3 Jul 27 14:42:41 undisclosedHostName kernel: platform eisa.0: Cannot allocate resource for EISA slot 4 Jul 27 14:42:41 undisclosedHostName kernel: platform eisa.0: Cannot allocate resource for EISA slot 5 Jul 27 14:42:41 undisclosedHostName kernel: platform eisa.0: Cannot allocate resource for EISA slot 6 Jul 27 14:42:41 undisclosedHostName kernel: platform eisa.0: Cannot allocate resource for EISA slot 7 Jul 27 14:42:41 undisclosedHostName kernel: platform eisa.0: Cannot allocate resource for EISA slot 8 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1837326 Title: platform eisa.0: EISA: Cannot allocate resource for mainboard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1837326/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1725840] Re: resolvconf not correctly configured after update from 17.04 to 17.10
** Changed in: resolvconf (Ubuntu) Assignee: Dimitri John Ledkov (xnox) => md shoeb lincoln (lincolntgl1987) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1725840 Title: resolvconf not correctly configured after update from 17.04 to 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/cubic/+bug/1725840/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870994] Re: "*BAD*gran_size: 64K chunk_size: 32M num_reg: 10 lose cover RAM: -18M" in dmesg
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 lose cover RAM: -18M" in dmesg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1870994/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870994] Re: "*BAD*gran_size: 64K chunk_size: 32M num_reg: 10 lose cover RAM: -18M" in dmesg
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: 64Kchunk_size: 32M num_reg: 10 lose cover RAM: -18M" in dmesg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1870994/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822674] Re: aspell-de: replace instantiieren with instanziieren
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 instantiieren with instanziieren To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aspell-de/+bug/1822674/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829061] Re: long rightwards double arrow ⟹ should be longer and rightwards double arrow ⇒ should be shorter
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 received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829061 Title: long rightwards double arrow ⟹ should be longer and rightwards double arrow ⇒ should be shorter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/emacs/+bug/1829061/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1765220] Re: Latexmk uses deprecated function File::Glob::glob()
** 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/latexmk/+bug/1765220/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1765220] Re: Latexmk uses deprecated function File::Glob::glob()
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: Latexmk uses deprecated function File::Glob::glob() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/latexmk/+bug/1765220/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769147] Re: Please update cleveref in texlive-latex-extra
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/bugs/1769147 Title: Please update cleveref in texlive-latex-extra To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/texlive-extra/+bug/1769147/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1837245] Re: Failed to bump fs.file-max, ignoring: Invalid argument
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: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1837245/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867209] Re: evince crashes on searching in a PDF file
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 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.launchpad.net/ubuntu/+source/evince/+bug/1867209/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867209] Re: evince crashes on searching in a PDF file
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.launchpad.net/ubuntu/+source/evince/+bug/1867209/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 691394] Re: Pairing error from desktopcouch when attempting to run ubuntuone-preferences
** This bug is no longer a duplicate of bug 657850 Ubuntu One Preferences applet doesn't display info properly -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/691394 Title: Pairing error from desktopcouch when attempting to run ubuntuone- preferences To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/desktopcouch/+bug/691394/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1883680] [NEW] I have tryed a lot of time but fail to install ubuntu . beacouse of error 5
Public bug reported: error 5 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.15 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.445 CurrentDesktop: ubuntu:GNOME Date: Tue Jun 16 14:59:07 2020 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed initrd=/casper/initrd quiet splash --- maybe-ubiquity LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: LANGUAGE=en_US.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug focal ubiquity-20.04.15 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1883680 Title: I have tryed a lot of time but fail to install ubuntu . beacouse of error 5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1883680/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870994] Re: "*BAD*gran_size: 64K chunk_size: 32M num_reg: 10 lose cover RAM: -18M" in dmesg
@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_size: 64Kchunk_size: 32M num_reg: 10 lose cover RAM: -18M" in dmesg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1870994/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870995] Re: i8042: Warning: Keylock active
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/linux/+bug/1870995/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870995] Re: i8042: Warning: Keylock active
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. -- 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/linux/+bug/1870995/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870995] Re: i8042: Warning: Keylock active
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 log files. -- 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/linux/+bug/1870995/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1872639] Re: ubuntu installation failed for Grub2 error
didnt tried it yet, also i dont try beta at all for any kinds of software, games or os. On ১৪/৪/২০ ৪:৩৮ PM, Jouni Mettala wrote: > Ubuntu 20.04 LTS Focal Fossa is released in next week. > > There is already beta available. > http://releases.ubuntu.com/ > > Does this still happen with 20.04? > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872639 Title: ubuntu installation failed for Grub2 error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1872639/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872639] [NEW] ubuntu installation failed for Grub2 error
Public bug reported: this is the 7th time i tried and failed. at first i tried installing along windows 10. now im installing in seperate ssd with custom partition like, 1gb for EFI, rest of them are /, /home and swap area partition. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity 18.04.14.14 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-28-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CasperVersion: 1.394.3 Date: Tue Apr 14 12:26:53 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper quiet splash --- LiveMediaBuild: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubiquity-18.04.14.14 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872639 Title: ubuntu installation failed for Grub2 error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1872639/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872573] [NEW] grub 2 installer crashed
Public bug reported: I wanted to install ubuntu latest LTS version at my computer today, but when installer runs, it stopped suddenly when installing grub 2. It says this is a fatal error. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity 18.04.14.14 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-28-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CasperVersion: 1.394.3 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 14 08:07:38 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) ProcEnviron: LANGUAGE=en_US.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubiquity-18.04.14.14 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872573 Title: grub 2 installer crashed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1872573/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870994] Re: "*BAD*gran_size: 64K chunk_size: 32M num_reg: 10 lose cover RAM: -18M" in dmesg
** 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, 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? ** Description changed: - While looking at the attached 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 which comes from 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? -- 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 lose cover RAM: -18M" in dmesg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1870994/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870994] Re: "*BAD*gran_size: 64K chunk_size: 32M num_reg: 10 lose cover RAM: -18M" in dmesg
@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 Title: "*BAD*gran_size: 64Kchunk_size: 32M num_reg: 10 lose cover RAM: -18M" in dmesg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1870994/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1703964] Re: ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042F conflicts with OpRegion 0x0000000000000400-0x000000000000047F (\PMIO) (20170119/utaddress-247)
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 received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1703964 Title: ACPI Warning: SystemIO range 0x0428-0x042F conflicts with OpRegion 0x0400-0x047F (\PMIO) (20170119/utaddress-247) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1703964/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1703964] Re: ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042F conflicts with OpRegion 0x0000000000000400-0x000000000000047F (\PMIO) (20170119/utaddress-247)
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 with the laptop from time to time (e.g., headset sometimes not working properly), but I have no idea which of the dozens error/warning messages might be related at all, if any. ** Attachment added: "dmesg.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1703964/+attachment/5347376/+files/dmesg.log ** Changed in: linux (Ubuntu) Status: Invalid => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1703964 Title: ACPI Warning: SystemIO range 0x0428-0x042F conflicts with OpRegion 0x0400-0x047F (\PMIO) (20170119/utaddress-247) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1703964/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870995] [NEW] i8042: Warning: Keylock active
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 needs to be solved? ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Attachment added: "dmesg.log" https://bugs.launchpad.net/bugs/1870995/+attachment/5347375/+files/dmesg.log -- 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/alsa-driver/+bug/1870995/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870994] [NEW] "*BAD*gran_size: 64K chunk_size: 32M num_reg: 10 lose cover RAM: -18M" in dmesg
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 Status: Incomplete ** Tags: eoan ** Attachment added: "dmesg.log" https://bugs.launchpad.net/bugs/1870994/+attachment/5347374/+files/dmesg.log -- 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 lose cover RAM: -18M" in dmesg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1870994/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1837245] Re: Failed to bump fs.file-max, ignoring: Invalid argument
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 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: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1837245/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835660] Re: initramfs unpacking failed
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/bugs/1835660 Title: initramfs unpacking failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1835660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835660] Re: initramfs unpacking failed
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 added: "dmesg.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1835660/+attachment/5347364/+files/dmesg.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835660 Title: initramfs unpacking failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1835660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867209] Re: evince crashes on searching in a PDF file
** 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 starts searching, jumps to the first occurrence, and displays a thin progress bar while continuing searching. Evince doesn't terminate: about the middle of the search process, evince crashes: $ evince .pdf munmap_chunk(): invalid pointer Abgebrochen (Speicherabzug geschrieben) Unfortunately, I cannot share my PDF file due to legal reasons. However, the two files mentioned in https://gitlab.gnome.org/GNOME/evince/issues/1250 would do: - https://www.jaapsch.net/psion/pdffiles/hd6301-3_handbook.pdf - https://www.people.vcu.edu/~rhammack/BookOfProof/Main.pdf Searching for "the" (without the quotation marks) in any of these - documents reproducibly crashes them. I cannot debug Evince myself (and - a package such as evince-dbg seems to be unavailable anyway) and would - therefore kindly ask the Ubuntu folks to attract the attention of the - developers to this issue (or bugfix it or update Evince if a solution is - already available). + documents reproducibly crashes them. Here is the xterm contents on + these occasions: + + $ export EV_DEBUG_JOBS=1 + $ export G_MESSAGES_DEBUG=all + $ evince Main.pdf + (evince:8410): GLib-GIO-DEBUG: 21:40:47.788: _g_io_module_get_default: Found default implementation gvfs (GDaemonVfs) for ‘gio-vfs’ + (evince:8410): Gtk-DEBUG: 21:40:47.860: Connecting to session manager + (evince:8410): GLib-GIO-DEBUG: 21:40:47.869: desktop_file_dirs_lock: Resetting desktop app info dirs from (null) to /home/malkis/.config + (evince:8410): GLib-GIO-DEBUG: 21:40:47.926: _g_io_module_get_default: Found default implementation dconf (DConfSettingsBackend) for ‘gsettings-backend’ + (evince:8410): dconf-DEBUG: 21:40:47.926: watch_fast: "/org/gnome/evince/" (establishing: 0, active: 0) + (evince:8410): dconf-DEBUG: 21:40:47.927: watch_established: "/org/gnome/evince/" (establishing: 1) + (evince:8410): dconf-DEBUG: 21:40:47.951: watch_fast: "/org/gnome/evince/default/" (establishing: 0, active: 0) + (evince:8410): dconf-DEBUG: 21:40:47.951: watch_established: "/org/gnome/evince/default/" (establishing: 1) + (evince:8410): dconf-DEBUG: 21:40:48.028: watch_fast: "/org/gnome/desktop/lockdown/" (establishing: 0, active: 0) + (evince:8410): dconf-DEBUG: 21:40:48.029: watch_established: "/org/gnome/desktop/lockdown/" (establishing: 1) + + ** (evince:8410): WARNING **: 21:40:50.284: No offset found for match + "t" at page 9 after processing 55 results + + + ** (evince:8410): WARNING **: 21:40:50.551: No offset found for match "the" at page 9 after processing 8 results + + munmap_chunk(): invalid pointer + Abgebrochen (Speicherabzug geschrieben) + $ evince hd6301-3_handbook.pdf + (evince:8440): GLib-GIO-DEBUG: 21:41:26.259: _g_io_module_get_default: Found default implementation gvfs (GDaemonVfs) for ‘gio-vfs’ + (evince:8440): Gtk-DEBUG: 21:41:26.332: Connecting to session manager + (evince:8440): GLib-GIO-DEBUG: 21:41:26.340: desktop_file_dirs_lock: Resetting desktop app info dirs from (null) to /home/malkis/.config + (evince:8440): GLib-GIO-DEBUG: 21:41:26.400: _g_io_module_get_default: Found default implementation dconf (DConfSettingsBackend) for ‘gsettings-backend’ + (evince:8440): dconf-DEBUG: 21:41:26.400: watch_fast: "/org/gnome/evince/" (establishing: 0, active: 0) + (evince:8440): dconf-DEBUG: 21:41:26.401: watch_established: "/org/gnome/evince/" (establishing: 1) + (evince:8440): dconf-DEBUG: 21:41:26.424: watch_fast: "/org/gnome/evince/default/" (establishing: 0, active: 0) + (evince:8440): dconf-DEBUG: 21:41:26.424: watch_established: "/org/gnome/evince/default/" (establishing: 1) + (evince:8440): dconf-DEBUG: 21:41:26.596: watch_fast: "/org/gnome/desktop/lockdown/" (establishing: 0, active: 0) + (evince:8440): dconf-DEBUG: 21:41:26.597: watch_established: "/org/gnome/desktop/lockdown/" (establishing: 1) + free(): invalid next size (fast) + Abgebrochen (Speicherabzug geschrieben) + $ + + + I cannot debug Evince myself (and a package such as evince-dbg seems to be unavailable anyway) and would therefore kindly ask the Ubuntu folks to attract the attention of the developers to this issue (or bugfix it or update Evince if a solution is already available). -- 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.launchpad.net/ubuntu/+source/evince/+bug/1867209/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867209] [NEW] evince crashes on searching in a PDF file
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, jumps to the first occurrence, and displays a thin progress bar while continuing searching. Evince doesn't terminate: about the middle of the search process, evince crashes: $ evince .pdf munmap_chunk(): invalid pointer Abgebrochen (Speicherabzug geschrieben) Unfortunately, I cannot share my PDF file due to legal reasons. However, the two files mentioned in https://gitlab.gnome.org/GNOME/evince/issues/1250 would do: - https://www.jaapsch.net/psion/pdffiles/hd6301-3_handbook.pdf - https://www.people.vcu.edu/~rhammack/BookOfProof/Main.pdf Searching for "the" (without the quotation marks) in any of these documents reproducibly crashes them. Here is the xterm contents on these occasions: $ export EV_DEBUG_JOBS=1 $ export G_MESSAGES_DEBUG=all $ evince Main.pdf (evince:8410): GLib-GIO-DEBUG: 21:40:47.788: _g_io_module_get_default: Found default implementation gvfs (GDaemonVfs) for ‘gio-vfs’ (evince:8410): Gtk-DEBUG: 21:40:47.860: Connecting to session manager (evince:8410): GLib-GIO-DEBUG: 21:40:47.869: desktop_file_dirs_lock: Resetting desktop app info dirs from (null) to /home/malkis/.config (evince:8410): GLib-GIO-DEBUG: 21:40:47.926: _g_io_module_get_default: Found default implementation dconf (DConfSettingsBackend) for ‘gsettings-backend’ (evince:8410): dconf-DEBUG: 21:40:47.926: watch_fast: "/org/gnome/evince/" (establishing: 0, active: 0) (evince:8410): dconf-DEBUG: 21:40:47.927: watch_established: "/org/gnome/evince/" (establishing: 1) (evince:8410): dconf-DEBUG: 21:40:47.951: watch_fast: "/org/gnome/evince/default/" (establishing: 0, active: 0) (evince:8410): dconf-DEBUG: 21:40:47.951: watch_established: "/org/gnome/evince/default/" (establishing: 1) (evince:8410): dconf-DEBUG: 21:40:48.028: watch_fast: "/org/gnome/desktop/lockdown/" (establishing: 0, active: 0) (evince:8410): dconf-DEBUG: 21:40:48.029: watch_established: "/org/gnome/desktop/lockdown/" (establishing: 1) ** (evince:8410): WARNING **: 21:40:50.284: No offset found for match "t" at page 9 after processing 55 results ** (evince:8410): WARNING **: 21:40:50.551: No offset found for match "the" at page 9 after processing 8 results munmap_chunk(): invalid pointer Abgebrochen (Speicherabzug geschrieben) $ evince hd6301-3_handbook.pdf (evince:8440): GLib-GIO-DEBUG: 21:41:26.259: _g_io_module_get_default: Found default implementation gvfs (GDaemonVfs) for ‘gio-vfs’ (evince:8440): Gtk-DEBUG: 21:41:26.332: Connecting to session manager (evince:8440): GLib-GIO-DEBUG: 21:41:26.340: desktop_file_dirs_lock: Resetting desktop app info dirs from (null) to /home/malkis/.config (evince:8440): GLib-GIO-DEBUG: 21:41:26.400: _g_io_module_get_default: Found default implementation dconf (DConfSettingsBackend) for ‘gsettings-backend’ (evince:8440): dconf-DEBUG: 21:41:26.400: watch_fast: "/org/gnome/evince/" (establishing: 0, active: 0) (evince:8440): dconf-DEBUG: 21:41:26.401: watch_established: "/org/gnome/evince/" (establishing: 1) (evince:8440): dconf-DEBUG: 21:41:26.424: watch_fast: "/org/gnome/evince/default/" (establishing: 0, active: 0) (evince:8440): dconf-DEBUG: 21:41:26.424: watch_established: "/org/gnome/evince/default/" (establishing: 1) (evince:8440): dconf-DEBUG: 21:41:26.596: watch_fast: "/org/gnome/desktop/lockdown/" (establishing: 0, active: 0) (evince:8440): dconf-DEBUG: 21:41:26.597: watch_established: "/org/gnome/desktop/lockdown/" (establishing: 1) free(): invalid next size (fast) Abgebrochen (Speicherabzug geschrieben) $ I cannot debug Evince myself (and a package such as evince-dbg seems to be unavailable anyway) and would therefore kindly ask the Ubuntu folks to attract the attention of the developers to this issue (or bugfix it or update Evince if a solution is already available). ** Affects: evince (Ubuntu) Importance: Undecided Status: New ** Description changed: Package: evince Version: 3.34.1-1 - Evince crashes when searching in a particular file. I open a PDF file, - press Ctrl+F to open a search string box, and type in some string that - occurs in the document. Then, evince starts searching, jumps to the - first occurrence, and displays a thin progress bar while continuing + Evince crashes when searching in a particular 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, jumps to + the first occurrence, and displays a thin progress bar while continuing searching. Evince doesn't terminate: about the middle of the search process, evince crashes: $ evince .pdf munmap_chunk(): invalid pointer Abgebrochen (Speicherabzug geschrieben) Unfortunately, I cannot
[Bug 1859351] [NEW] package passwd 1:4.2-3.1ubuntu5.4 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
Public bug reported: This is failed to install. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: passwd 1:4.2-3.1ubuntu5.4 ProcVersionSignature: Ubuntu 4.15.0-74.83~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-74-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.21 AptOrdering: passwd: Configure NULL: ConfigurePending Architecture: amd64 Date: Sun Jan 12 23:16:37 2020 DpkgTerminalLog: dpkg: error processing package passwd (--configure): package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2020-01-12 (0 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190227) RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.2.32 SourcePackage: shadow Title: package passwd 1:4.2-3.1ubuntu5.4 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: shadow (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1859351 Title: package passwd 1:4.2-3.1ubuntu5.4 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1859351/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 662077] Re: WxWidgets apps don't have menus
** Changed in: wxwidgets2.8 (Ubuntu) Assignee: (unassigned) => Md Nuhin Nabi (nuhin-2) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/662077 Title: WxWidgets apps don't have menus To manage notifications about this bug go to: https://bugs.launchpad.net/libdbusmenu/+bug/662077/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847896] Re: Unable to shutdown or restart from log-in screen
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 about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1847896/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847896] Re: Unable to shutdown or restart from log-in screen
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 about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1847896/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847896] Re: Unable to shutdown or restart from log-in screen
@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://bugs.launchpad.net/bugs/1847896 Title: Unable to shutdown or restart from log-in screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1847896/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847896] Re: Unable to shutdown or restart from log-in screen
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 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 about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1847896/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849151] [NEW] Reboot and Powerdown buttons don't work in eoan
*** 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, otherwise, no result is observed. ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849151 Title: Reboot and Powerdown buttons don't work in eoan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1849151/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1806459] Re: software boutique broken on 32bit UM
** Also affects: ubuntu-mate-welcome-legacy Importance: Undecided Status: New ** No longer affects: ubuntu-mate-welcome-legacy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1806459 Title: software boutique broken on 32bit UM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1806459/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845757] [NEW] grub not installing
Public bug reported: I don't know ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity 18.04.14.12 ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CasperVersion: 1.394 CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 09:20:21 2019 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: LANGUAGE=en_US.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubiquity-18.04.14.12 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845757 Title: grub not installing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1845757/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838110] [NEW] "Zustanden" with capital "Z" is not a German word but the spellchecker does not compalin
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[Enter] german-new8[Enter] 4) M-x ispell-buffer 5) Observe that no spellcheck error is reported. On the contrary, I expect that "Zustanden" be marked as an error and two possibilities be suggested: "Zuständen" (which would make sense semantically) and "zustanden" (as the past tense of "zustehen", though it would make no sense semantically.) I think that the spellchecking in the background is done by aspell (though I'm unsure). ** Affects: emacs (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838110 Title: "Zustanden" with capital "Z" is not a German word but the spellchecker does not compalin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/emacs/+bug/1838110/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1836067] Re: Consider reenabling png to eps conversion in ImageMagick in disco
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 to Ubuntu. https://bugs.launchpad.net/bugs/1836067 Title: Consider reenabling png to eps conversion in ImageMagick in disco To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/imagemagick/+bug/1836067/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1836067] [NEW] Consider reenabling png to eps conversion in ImageMagick in disco
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)" Version: 8:6.9.10.14+dfsg-7ubuntu2.2 Zustand: Installiert $ grep "EPS" /etc/ImageMagick-6/policy.xml $ aptitude show ghostscript | egrep -i "(Version)|(Instal)" Version: 9.26~dfsg+0-0ubuntu7.1 Zustand: Installiert However, the bug https://www.kb.cert.org/vuls/id/332928/ has been closed in ghostscript version 9.24 already, whereas disco has ghostscript 9.26. So please consider reenabling file conversion in ImageMagick. ** Affects: imagemagick (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1836067 Title: Consider reenabling png to eps conversion in ImageMagick in disco To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/imagemagick/+bug/1836067/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829785] Re: Evince: ∞ not found
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.launchpad.net/evince/+bug/1829785/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829785] Re: Evince: ∞ not found
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 found To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/1829785/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829785] Re: Evince: ∞ not found
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 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.launchpad.net/evince/+bug/1829785/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829785] [NEW] Evince: ∞ not found
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 that evince doesn't find the symbol (shows no results in the search pane and lightens the search field red). I expect that the symbol, on the contrary, is found (i.e., that the pane shows page 1 and some context of the symbol). In qpdfview and okular, the symbol is found, as well as in evince from the current debian stable. Any bugfix? ** Affects: evince (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Document to view" https://bugs.launchpad.net/bugs/1829785/+attachment/5265120/+files/q.pdf ** Description changed: Package: evince Version: 3.32.0-1ubuntu0.1 OS: Disco 19.04 How to reproduce: - 1) Open the attached document in Evince + 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 that evince doesn't find the symbol (shows no results in the search pane and lightens the search field red). On the contrary, I expect the symbol to be found (the pane shows page 1 and the context). + 4) Observe that evince doesn't find the symbol (shows no results in the search pane and lightens the search field red). I expect that the symbol, on the contrary, is found (i.e., that the pane shows page 1 and some context of the symbol). In qpdfview and okular, the symbol is found, as well as in evince from the current debian stable. Any bugfix? -- 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.launchpad.net/ubuntu/+source/evince/+bug/1829785/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829061] [NEW] long rightwards double arrow ⟹ should be longer and rightwards double arrow ⇒ should be shorter
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 short and ⇒ (U+27F9) is shown long
in the emacs buffer (cf. the attachment). But it should be the other
way round!
M-x describe-font [Enter][Enter] returns the following:
name (opened by): -DAMA-Ubuntu
Mono-normal-normal-normal-*-13-*-*-*-m-0-iso10646-1
full name: Ubuntu
Mono:pixelsize=13:foundry=DAMA:weight=normal:slant=normal:width=normal:spacing=100:scalable=true
file name: /usr/share/fonts/truetype/ubuntu/UbuntuMono-R.ttf
size: 13
height: 14
baseline-offset: 0
relative-compose: 0
default-ascent: 0
ascent: 11
descent: 3
average-width: 7
space-width: 7
max-width: 7
I see the symbol width as expected in the character table for the font
Ubuntu Mono, therefore, I personally don't say that the font is guilty,
though the reader may do it if they think otherwise.
$ lsb_release -rd
Description:Ubuntu 19.04
Release:19.04
** Affects: emacs (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1829061
Title:
long rightwards double arrow ⟹ should be longer and rightwards double
arrow ⇒ should be shorter
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/emacs/+bug/1829061/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829061] Re: long rightwards double arrow ⟹ should be longer and rightwards double arrow ⇒ should be shorter
** 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 Title: long rightwards double arrow ⟹ should be longer and rightwards double arrow ⇒ should be shorter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/emacs/+bug/1829061/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
