[Bug 2084049] [NEW] package nvidia-dkms-535 535.183.01-0ubuntu0.24.04.1 failed to install/upgrade: »installiertes post-installation-Skript des Paketes nvidia-dkms-535«-Unterprozess gab den Fehlerwert
Public bug reported: Ich hatte Ubuntu Studio installiert und bin in ubuntu gerutscht, und wollte den nvidia treiber installieren und der löste diesen fehler aus . aus grund ein fehler bin ich von ubuntu studio in ubuntu gerutscht ProblemType: Package DistroRelease: Ubuntu 24.04 Package: nvidia-dkms-535 535.183.01-0ubuntu0.24.04.1 ProcVersionSignature: Ubuntu 6.8.1-1009.9-realtime 6.8.12 Uname: Linux 6.8.1-1009-realtime x86_64 ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Wed Oct 9 15:19:53 2024 ErrorMessage: »installiertes post-installation-Skript des Paketes nvidia-dkms-535«-Unterprozess gab den Fehlerwert 10 zurück InstallationDate: Installed on 2024-10-04 (5 days ago) InstallationMedia: Ubuntu-Studio 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240216) Python3Details: /usr/bin/python3.12, Python 3.12.3, python3-minimal, 3.12.3-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.22.6ubuntu6.1 apt 2.7.14build2 SourcePackage: nvidia-graphics-drivers-535 Title: package nvidia-dkms-535 535.183.01-0ubuntu0.24.04.1 failed to install/upgrade: »installiertes post-installation-Skript des Paketes nvidia-dkms-535«-Unterprozess gab den Fehlerwert 10 zurück UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.init.d.apport: 2024-07-22T16:59:07 ** Affects: nvidia-graphics-drivers-535 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2084049 Title: package nvidia-dkms-535 535.183.01-0ubuntu0.24.04.1 failed to install/upgrade: »installiertes post-installation-Skript des Paketes nvidia-dkms-535«-Unterprozess gab den Fehlerwert 10 zurück To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-535/+bug/2084049/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066990] Re: high memory consumption in Ubuntu Noble
This issue arises because the container is running on top of a FIPS- enabled kernel which provides the /proc/sys/crypto/fips_enabled = 1 flag. On Noble, openssl sees this flag and expects therefore to be operating in FIPS mode, but at this point the Noble container is not in FIPS mode - we haven't finished developing the FIPS components and haven't released them - and the result is that it throws some errors. The workaround is to either not run the container on a FIPS-enabled kernel; or to set the environment variable in the Noble container to disable FIPS mode: ENV OPENSSL_FORCE_FIPS_MODE=0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066990 Title: high memory consumption in Ubuntu Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/2066990/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078280] Re: System Crash on reboot/screen lockout: systemd-logind crashed with SIGABRT in __epoll_wait_nocancel()
Hey, I attached the crash log that was found in /var/crash ** Attachment added: "crash_report.log" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2078280/+attachment/5810437/+files/crash_report.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078280 Title: System Crash on reboot/screen lockout: systemd-logind crashed with SIGABRT in __epoll_wait_nocancel() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2078280/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078280] [NEW] System Crash on reboot/screen lockout: systemd-logind crashed with SIGABRT in __epoll_wait_nocancel()
Public bug reported: Title: systemd-logind crashed with SIGABRT in __epoll_wait_nocancel() ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-142.146~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-142-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.30 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Thu Aug 29 00:09:44 2024 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Red Hat, Inc. QXL paravirtual graphic card [1b36:0100] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Red Hat, Inc. QEMU Virtual Machine [1af4:1100] InstallationDate: Installed on 2024-08-19 (9 days ago) InstallationMedia: Ubuntu 16.04.7 LTS "Xenial Xerus" - Release amd64 (20200806) LightdmLog: [+9875.17s] DEBUG: Seat seat0 changes active session to c2 [+9875.17s] DEBUG: Session c2 is already active Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Ubuntu 24.04 PC (i440FX + PIIX, 1996) ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-142-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 Renderer: Software SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.16.3-debian-1.16.3-2 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-noble dmi.modalias: dmi:bvnSeaBIOS:bvr1.16.3-debian-1.16.3-2:bd04/01/2014:svnQEMU:pnUbuntu24.04PC(i440FX+PIIX,1996):pvrpc-i440fx-noble:cvnQEMU:ct1:cvrpc-i440fx-noble: dmi.product.name: Ubuntu 24.04 PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-noble dmi.sys.vendor: QEMU version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Wed Aug 28 19:13:02 2024 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputQEMU QEMU USB Tablet TOUCHSCREEN, id 7 inputAT Translated Set 2 keyboard KEYBOARD, id 8 inputImExPS/2 Generic Explorer Mouse MOUSE, id 9 xserver.errors: AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.outputs: Output Virtual-0 Virtual-1 Virtual-2 Virtual-3 xserver.version: 2:1.19.6-1ubuntu4.1~16.04.6 xserver.video_driver: qxl ** Affects: ubuntu Importance: Undecided Status: New ** Tags: amd64 apport-bug crash ubuntu xenial ** Attachment added: "Screenshot from 2024-08-28 19-18-19.png" https://bugs.launchpad.net/bugs/2078280/+attachment/5810190/+files/Screenshot%20from%202024-08-28%2019-18-19.png ** Summary changed: - Screen Crash on reboot or when locked out from userspace + System Crash on reboot/screen lockout: systemd-logind crashed with SIGABRT in __epoll_wait_nocancel() -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078280 Title: System Crash on reboot/screen lockout: systemd-logind crashed with SIGABRT in __epoll_wait_nocancel() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2078280/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952970] Re: mesa GLX change leads to wine showing GLXBadFBConfig
TLDR version, yes it's fixed! I guess there's only one way to find out! I've been running kisak PPA so was on 24.1.x on there, but I'm ppa-purge'ing is now to test. I no longer have that Sandy Bridge notebook, but have an Ivy Bridge desktop (and I verified based on the plenty of debug info Wine prints that it does skip over the nearly useless "partial" Vulkan support on it and is using OpenGL code paths.) It now has 23.2.1 on it. I don't usually game on this system but I ran The Stanley Parable on there to test. Looks good! I realized the Ivy Bridge supports up to OpenGL 4.2 rather than the 3.3 of the Sandy Bridge so I also ran with MESA_GL_VERSION_OVERRIDE=3.3 to hold it down to an older OpenGL version and make sure it works then too. It did. Also tested with MESA_GL_VERSION_OVERRIDE=2.1 to make sure the version override was working. Indeed wine said the requested D3D feature levels are unavailable and the game didn't load. Fixed! Thanks! --Henry -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952970 Title: mesa GLX change leads to wine showing GLXBadFBConfig To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1952970/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2070448] [NEW] Black screen after boot
Public bug reported: After update to Kernel 5.15.0-113 i have black screen after booting. The same bug when i update to Kernel 5.15.0-112. I have an AMD machine. Best regards ** Affects: linux (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/2070448 Title: Black screen after boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2070448/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064860] [NEW] sytem hangs on opening Files (Nautilus?)
Public bug reported: I clicked on the icon for my external HDD, the Files app started, showed 'Searching for files...' and immediately the system hung. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome (not installed) ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun May 5 15:47:41 2024 InstallationDate: Installed on 2024-04-26 (9 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: meta-gnome3 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: meta-gnome3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble 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/2064860 Title: sytem hangs on opening Files (Nautilus?) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/meta-gnome3/+bug/2064860/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060948] Re: pinta not available for Noble
Thanks for pointing me in the right direction. It looks like this is not a valid bug report after all then. ** Changed in: pinta (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060948 Title: pinta not available for Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pinta/+bug/2060948/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060948] [NEW] pinta not available for Noble
Public bug reported: Using a Daily build installation of Noble from 10/04/2024, updated on 11/04/2024, I can't install pinta using apt. henry@pc2:~$ sudo apt update [sudo] password for henry: Warning: The unit file, source configuration file or drop-ins of apt-news.service changed on disk. Run 'systemctl daemon-reload' to reload units. Warning: The unit file, source configuration file or drop-ins of esm-cache.service changed on disk. Run 'systemctl daemon-reload' to reload units. Get:1 http://gb.archive.ubuntu.com/ubuntu noble InRelease [255 kB] Get:2 http://gb.archive.ubuntu.com/ubuntu noble-updates InRelease [89.7 kB] Hit:3 http://gb.archive.ubuntu.com/ubuntu noble-backports InRelease Get:4 http://gb.archive.ubuntu.com/ubuntu noble/universe amd64 Packages [15.7 MB] Hit:5 http://security.ubuntu.com/ubuntu noble-security InRelease Get:6 http://gb.archive.ubuntu.com/ubuntu noble/universe Translation-en [6,069 kB] Fetched 22.1 MB in 2s (9,693 kB/s) Reading package lists... Done Building dependency tree... Done Reading state information... Done All packages are up to date. henry@pc2:~$ sudo apt upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. henry@pc2:~$ sudo apt install pinta Reading package lists... Done Building dependency tree... Done Reading state information... Done Package pinta is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source E: Package 'pinta' has no installation candidate henry@pc2:~$ date Thu Apr 11 11:48:32 AM BST 2024 ** Affects: pinta (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/2060948 Title: pinta not available for Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pinta/+bug/2060948/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060947] [NEW] Warnings produced in apt upgrade processing triggers for initramfs-tools
Public bug reported: Using Noble, installed from Daily build on 10/4/2024, I updated the system on 11/4/2024 using `sudo apt update; sudo apt -y upgrade` The following warning was printed in the `apt upgrade` output: Processing triggers for initramfs-tools (0.142ubuntu24) ... update-initramfs: Generating /boot/initrd.img-6.8.0-22-generic cryptsetup: WARNING: dm_crypt-0: couldn't determine device type, assuming default (plain). cryptsetup: WARNING: Option 'cipher' missing in crypttab for plain dm-crypt mapping dm_crypt-0. Please read /usr/share/doc/cryptsetup-initramfs/README.initramfs.gz and add the correct 'cipher' option to your crypttab(5). cryptsetup: WARNING: Option 'size' missing in crypttab for plain dm-crypt mapping dm_crypt-0. Please read /usr/share/doc/cryptsetup-initramfs/README.initramfs.gz and add the correct 'size' option to your crypttab(5). cryptsetup: WARNING: Resume target dm_crypt-0 uses a key file The VM was provisioned with ZFS and encryption. This is the lsblk output: NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS loop0 7:00 4K 1 loop /snap/bare/5 loop1 7:10 268.3M 1 loop /snap/firefox/4090 loop2 7:20 74.2M 1 loop /snap/core22/1122 loop3 7:30 505.1M 1 loop /snap/gnome-42-2204/176 loop4 7:40 10.7M 1 loop /snap/firmware-updater/121 loop5 7:50 39.1M 1 loop /snap/snapd/21184 loop6 7:60 91.7M 1 loop /snap/gtk-common-themes/1535 loop7 7:70 10.3M 1 loop /snap/snap-store/1124 loop8 7:80 476K 1 loop /snap/snapd-desktop-integration/157 loop9 7:90 10.7M 1 loop /snap/firmware-updater/127 sr0 11:01 4.3G 0 rom /media/henry/Ubuntu 24.04 LTS amd64 zd0 230:0020M 0 disk └─keystore-rpool 252:00 4M 0 crypt /run/keystore/rpool vda 253:0025G 0 disk ├─vda1 253:10 1M 0 part ├─vda2 253:20 2G 0 part ├─vda3 253:30 3.8G 0 part │ └─dm_crypt-0 252:10 3.8G 0 crypt [SWAP] └─vda4 253:40 19.2G 0 part ** Affects: cryptsetup (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/2060947 Title: Warnings produced in apt upgrade processing triggers for initramfs- tools To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/2060947/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1761739] Re: Submits a message to a remote server even when "No, don't send any info" is selected
I've observed the same behaviour with Noble installer, and it does appear to be very counter-intuitive for a user to select "Don't send" and then be told that their send request failed. On a related point, the UI appears to block on this network request - which is probably not necessary - and when the server is not responding in a timely manner it leads to a UI that looks like it's hung. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1761739 Title: Submits a message to a remote server even when "No, don't send any info" is selected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/1761739/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1085]
There are still plans to update the message header recipient list along the lines of https://bugzilla.mozilla.org/attachment.cgi?id=9243994&action=edit I'm not aware of an open bug for this specifically. Bug 1752532 is introducing new multi-selection widgets that we plan on using for the recipients list (specifically, the "grouped list" widget). I'll block on this for the time being. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1085 Title: selecting text in full header mode fails To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1085/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971788] Re: Failure to enable SSL out of the box when in fips mode
** Changed in: mysql-8.0 (Ubuntu) Assignee: (unassigned) => Henry Coggill (henrycoggill) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971788 Title: Failure to enable SSL out of the box when in fips mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1971788/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958467] Re: focal linux-firmware package omits amdgpu/navi12 firmware
My apologies for not including the specific version in my comment - I tested linux-firmware package 1.187.27 from the focal proposed repository. ubuntu@ip-172-31-38-36:~$ apt list | grep linux-firmware/ linux-firmware/focal-proposed,now 1.187.27 all [installed] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958467 Title: focal linux-firmware package omits amdgpu/navi12 firmware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1958467/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962371] [NEW] Abiword segfaults when trying to do about anything useful
Public bug reported: The Abiword binary is broken to the point of unusability: it segfaults when I attempt to (1) save a file via "Save", "Save as", or "Save a copy", (2) insert a file, (3) insert a picture, (4) import styles. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: abiword 3.0.4~dfsg-3 ProcVersionSignature: Ubuntu 5.11.0-49.55-generic 5.11.22 Uname: Linux 5.11.0-49-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.4 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Sat Feb 26 08:05:23 2022 InstallationDate: Installed on 2021-03-15 (348 days ago) InstallationMedia: Xubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210314) SourcePackage: abiword UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: abiword (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962371 Title: Abiword segfaults when trying to do about anything useful To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/abiword/+bug/1962371/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962302] [NEW] Keyboard Settings for ¨Dumb¨ Quotemarks (ASCII-34 and ASCII-39) for C Code
Public bug reported: I have upgraded to 21.10 from 20.04 with Budgie desktop on a RPI-4. My internationalisation settings are Irish (UK keyboard layout) Since upgrading I cannot select a keyboard map that allows the ASCII double-quote and single-quote characters (ASCII-34 and ASCII-39) to be entered from the keyboard. Sometimes changing the keyboard settings allows this but after every reboot it returns to the "smart" key behaviour and/or the "intelligent" accenting behaviour. As one of the main tasks I use this system for is code development, this is almost impossible to use now. The behaviour is not confined to one package. Behaviour is the same for terminal and for editors including Mousepad and gedit, as well as the Geany IDE. ** Affects: ubuntu Importance: Undecided Status: New ** Tags: budgie keyboard -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962302 Title: Keyboard Settings for ¨Dumb¨ Quotemarks (ASCII-34 and ASCII-39) for C Code To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1962302/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958467] Re: focal linux-firmware package omits amdgpu/navi12 firmware
This is working well! Amazon EC2 instances with AMD graphics are able to initialize properly now, after installing the latest "linux-firmware" and "linux-modules-extra-aws" packages from proposed. ubuntu@ip-172-31-38-36:~$ sudo dmesg | grep "Initialized amdgpu" [4.908132] [drm] Initialized amdgpu 3.41.0 20150101 for :00:1e.0 on minor 0 ubuntu@ip-172-31-38-36:~$ sudo vainfo | grep NAVI12 vainfo: Driver version: Mesa Gallium driver 21.2.6 for AMD NAVI12 (DRM 3.41.0, 5.13.0-1014-aws, LLVM 12.0.0) ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958467 Title: focal linux-firmware package omits amdgpu/navi12 firmware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1958467/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956401] Re: amdgpu hangs for 90 seconds at a time in 5.13.0-23, but 5.13.0-22 works
Sorry about that! I initially filed this bug, but I'm no long-time user of the bug system. If 1956422 is marked dup and pointed here, it's fine with me! Still, as for GCP kernel specifically, a bot auto-generated the request to test against GCP kernel. I wonder how many drivers GCP kernel is missing (that'll be why the touchpad and lid switch didn't work.) I think for GCP kernel specifically, it won't matter if this patch is applied or not, no integrated GPUs so they won't be running affected hardware. I suppose first start is to attach any relevant logs and info -- does kern.log or dmesg show anything interesting when you suspend & resume? If you can ssh into the machine, does the machine lock solid on resume, or does it have a black screen but still running? You probably provided this info in 1956422 already but if it's being dup'ed to here, feel free to put it here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956401 Title: amdgpu hangs for 90 seconds at a time in 5.13.0-23, but 5.13.0-22 works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956401/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956401] Re: amdgpu hangs for 90 seconds at a time in 5.13.0-23, but 5.13.0-22 works
I don't think this patch is intended to fix suspend/resume bug, that's not the problem I was seeing at any rate. That said... Does this bug apply to GCP kernel? I'm assuming GCP is "Google Cloud Platform", so I'm not sure they are even using affected hardware. AMD CPUs are fairly power-efficient, so I could see Google using them, but probably not the ones with built-in GPU (in favor of getting ones with more CPU cores instead). I assume if they want to support CUDA-style workloads they'd thrown some monster GPUs into their "GPU compute" cloud systems. (That said, that all means for the use case of GCP kernel, it should be fine either way, apply or not apply this patch.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956401 Title: amdgpu hangs for 90 seconds at a time in 5.13.0-23, but 5.13.0-22 works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956401/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958832] [NEW] package libwine-development:arm64 6.0+repack-1ubuntu1 failed to install/upgrade: installed libwine-development:arm64 package post-installation script subprocess returned error exit
Public bug reported: On an M1 Macbook Air Running through a UTM virtual machine. System was only set up today. ProblemType: Package DistroRelease: Ubuntu 21.10 Package: libwine-development:arm64 6.0+repack-1ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-27.29-generic 5.13.19 Uname: Linux 5.13.0-27-generic aarch64 ApportVersion: 2.20.11-0ubuntu71 Architecture: arm64 CasperMD5CheckResult: pass Date: Mon Jan 24 07:53:18 2022 ErrorMessage: installed libwine-development:arm64 package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2022-01-24 (0 days ago) InstallationMedia: Ubuntu-Server 21.10 "Impish Indri" - Release arm64 (20211013) Python3Details: /usr/bin/python3.9, Python 3.9.7, python3-minimal, 3.9.4-1build1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.20.9ubuntu2 apt 2.3.9 SourcePackage: wine-development Title: package libwine-development:arm64 6.0+repack-1ubuntu1 failed to install/upgrade: installed libwine-development:arm64 package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: wine-development (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package arm64 impish uec-images -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958832 Title: package libwine-development:arm64 6.0+repack-1ubuntu1 failed to install/upgrade: installed libwine-development:arm64 package post- installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wine-development/+bug/1958832/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958467] [NEW] focal linux-firmware package omits amdgpu/navi12 firmware
Public bug reported: The 20.04 LTS linux-firmware package list was cut before the amdgpu/navi12* firmware files were upstreamed to the Linux kernel repository, which is unfortunate because this hardware is older than some other included firmware (navi14*), and the firmware is required for using the AMDGPU kernel module on AWS EC2 cloud instances with AMD GPUs. The files are included in 21.04 and 21.10, but to date they have not been included in the LTS hardware-enablement releases for 20.04. It would be helpful to include the navi12 firmware files for the next LTS+HWE release, since 22.04 isn't due out for a while. Without this firmware it is difficult to get AWS EC2 G4ad instances working with Ubuntu, as customers need to manually download and install the firmware from a reputable source and put it into the appropriate directory, which is not the experience they expect on hardware that is over a year old with the most recent HWE release. ** Affects: linux-firmware (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/1958467 Title: focal linux-firmware package omits amdgpu/navi12 firmware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1958467/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956401] Re: amdgpu hangs for 90 seconds at a time
I'm assuming the 5.14.15 or 5.14.16 amdgpu and amdkfd has been backported to the 5.13 Ubuntu kernel. Here's the patch in 5.14.17 that specifically addresses this. https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v5.14.17&id=7883e13c249461877ea3be7b24a5935fc8946e46 The other amd-related patches for 5.14.17 largely appear to be fixes to DCN3.1 support (newest GPU models from last 6 months or so.) This is a fairly serious regression for those affected (I may have only gotten to a desktop because I"m using Gnome Flashback so no compositor trying to exercise the 3D hardware for desktop use. I've simply gone back to 5.13.0-22 for now.) If the plan is to ship a quick update, I could see just patching in that one patch; if it'll be fixed in 5.13.0-23 at a usual schedule I could see incorporating all of them to benefit DCN 3.1 users. Not to dissemble, but kudos to the open source GPU driver developers, the Intel support's amazing (it's amusing on my friends Sandybridge, that he can run DX11 games in steam through Proton that it would not be able to run in Windows since Intel never shipped DX11 drivers for it...), and amdgpu has run every game I've thrown at it so far, generally at very good frame rates. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956401 Title: amdgpu hangs for 90 seconds at a time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1956401/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956401] Re: amdgpu hangs for 90 seconds at a time
Additional note, I did notice one "un-regression" -- I have a build of rocm where I've tried enabling "GFX902" support for my card, this is an unsupported configuration so I don't know if I have it 100% functional but rocminfo (which as the name suggests dumps info about the rocm install and any video or compute cards it detects that can use. ) With the 5.4.0-91-generic kernel I can run rocminfo and it dumps some info about the card. On 5.13.0-22 it prints: hsa api call failure at: /home/hwertz/ROCm/rocminfo/rocminfo.cc:1143 Call returned HSA_STATUS_ERROR_OUT_OF_RESOURCES: The runtime failed to allocate the necessary resources. This error may also occur when the core runtime library needs to spawn threads or create internal OS-specific events. On 5.13.0-23, although opengl is hosed the rocminfo didn't pause and printed the rocm-related information. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956401 Title: amdgpu hangs for 90 seconds at a time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1956401/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956401] Re: amdgpu hangs for 90 seconds at a time
** Attachment added: "Some kernel log showing amdgpu errors and others resulting from it" https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1956401/+attachment/5551255/+files/wow.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956401 Title: amdgpu hangs for 90 seconds at a time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1956401/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956401] [NEW] amdgpu hangs for 90 seconds at a time
Public bug reported: This does not occur with linux-image-5.13.0-22-generic, but does with linux-image-5.13.0-33-generic. On startup, I get about a 60 second hang, with the following in the kernel dmesg: Jan 4 15:26:36 inspiron-3505 kernel: [ 34.160572] amdgpu :04:00.0: amdgp : failed to write reg 28b4 wait reg 28c6 Jan 4 15:26:56 inspiron-3505 kernel: [ 54.189055] amdgpu :04:00.0: amdgp : failed to write reg 1a6f4 wait reg 1a706 Jan 4 15:27:16 inspiron-3505 kernel: [ 74.329264] amdgpu :04:00.0: amdgp : failed to write reg 28b4 wait reg 28c6 Jan 4 15:27:36 inspiron-3505 kernel: [ 94.337904] amdgpu :04:00.0: amdgp : failed to write reg 1a6f4 wait reg 1a706 I have the following GPU: 04:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Picass o (rev c2) (prog-if 00 [VGA controller]) 04:00.0 0300: 1002:15d8 (rev c2) (This is a Ryzen 5 3450U CPU with Radeon Vega Mobile.) I get a similar hang if I start firefox (when it's probing OpenGL contexts), and even with glxgears and glxinfo. Seems like anything that'd kick on a OpenGL context does it. I had a freeze as well when I tried running firefox and glxgears both. Along with odd BUG: messages logged (I have some in the attached log.) I was running with "iommu=pt", but did try with this removed, still got the errors (I think amdgpu driver uses the IOMMU even when it's set to IOMMU=pt though.). See the attached log for some very odd "[Hardware Error]" messages that were logged on one test run. I think this was when I tried to run firestorm (second life viewer) -- that had a large pause then opened to a black window. Per Google, I see there was a bug like this that turned up in kernel 5.14.15 but fixed in 5.14.17. See https://gitlab.freedesktop.org/drm/amd/-/issues/1770 Thanks! --Henry ** Affects: linux-hwe-5.13 (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/1956401 Title: amdgpu hangs for 90 seconds at a time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1956401/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952970] Re: mesa GLX change leads to wine showing GLXBadFBConfig
Suggested patch. For now, I've been running mesa 20.0.x on the affected system from (21.0.x is in ubuntu-updates, 20.0.x in base ubuntu repo, so I downgraded to that and thank goodness for apt-mark hold...) But I can update it straight away to test any update that comes out. Thanks! --Henry ** Patch added: "wine-fix-updated.diff" https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1952970/+attachment/5544778/+files/wine-fix-updated.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952970 Title: mesa GLX change leads to wine showing GLXBadFBConfig To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1952970/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952970] [NEW] mesa GLX change leads to wine showing GLXBadFBConfig
Public bug reported: A mesa GLX change (somewhere between the 20.0.4 and 21.0.3) causes both wine and Proton (on an older system that does not have Vulkan.. SandyBridge, OpenGL 3.3..) to exit with GLXBadFBConf when it tries to fire up OpenGL. Wine, for Direct3D support it tries to fire up (in order) Vulkan then progressively older OpenGL versions fro 4.5 down to 2.1 or maybe even 1.4 (of course the older the OpenGL the lower supported Direct3D version). Wine does not like getting an error back with the same transaction serial number as it sent out. See https://gitlab.freedesktop.org/mesa/mesa/-/issues/3969 Mesa issue 3969, The patch there throws in an "XNoOp()" to increment the transaction serial number. But the patch there caused issues in other apps, per https://gitlab.freedesktop.org/mesa/mesa/-/issues/4763 Mes issue 4763, They found XNoOp() increments the serial number, but xcb keeps a "shadow copy" of the serial number which is not incremented, causing problems. XFlush() increments the serial number, keeps xcb in sync and happy, with no real side effects (running XFlush() frequently would slow things down, but this code only runs when a GLX context is being created anyway which just doesn't happen all that frequently.) Please find attached a patch implementing the updated patch suggested in issue 4763. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libglx-mesa0 21.0.3-0ubuntu0.3~20.04.5 ProcVersionSignature: Ubuntu 5.13.0-22.22~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: GNOME-Flashback:GNOME Date: Wed Dec 1 18:59:43 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c2) (prog-if 00 [VGA controller]) Subsystem: Dell Picasso [1028:0a12] InstallationDate: Installed on 2020-05-05 (575 days ago) InstallationMedia: MachineType: Dell Inc. Inspiron 3505 ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=UUID=57669cb0-fd65-4eb0-9898-ed10f33d44d0 ro quiet splash nvme_core.io_timeout=300 nosmt vt.handoff=7 SourcePackage: mesa UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/31/2021 dmi.bios.release: 5.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.7 dmi.board.asset.tag: not specified dmi.board.name: 0RV9WY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.4.7 dmi.modalias: dmi:bvnDellInc.:bvr1.4.7:bd05/31/2021:br5.3:svnDellInc.:pnInspiron3505:pvr1.4.7:rvnDellInc.:rn0RV9WY:rvrA00:cvnDellInc.:ct10:cvr1.4.7:sku0A12: dmi.product.family: Inspiron dmi.product.name: Inspiron 3505 dmi.product.sku: 0A12 dmi.product.version: 1.4.7 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.5 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.5 version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 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: mesa (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/1952970 Title: mesa GLX change leads to wine showing GLXBadFBConfig To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1952970/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945741]
I'm changing the title to distinguish this from bug 1698140 (this is for PDF attachments that should be opened internally in Thunderbird, and the other bug is for PDF attachments being treated as a HTML when they are opened externally). This title change is a bit verbose, but I couldn't think of a better one. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945741 Title: [upstream] PDF attachment opens in Firefox instead of the built-in viewer when opened from the compose window To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1945741/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945741]
(In reply to Henry Wilkes [:henry] from comment #22) > Note that if a message is saved and reopened for editing, any saved pdf > attachments will open fine, but any newly added attachments are missing their > `contentType`. I think the missing `contentType` is probably a recent > regression, since I didn't notice this when reviewing this patch. Just tested in 91.2, and similarly new attachments have no `contentType`. So I guess I only tested on reopening drafts ... This kind of makes sense since the file's content is not read until it is saved/sent, so its `contentType` will not yet be determined. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945741 Title: [upstream] PDF attachment opens in Firefox instead of the built-in viewer when opened from the compose window To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1945741/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945741]
(In reply to WaltS48 [:walts48] from comment #21) > Error Console messages from 94.0b5: > > 17:17:29.906 TypeError: requestor is null PdfStreamConverter.jsm:140:13 > getDOMWindow resource://pdf.js/PdfStreamConverter.jsm:140 > onStopRequest resource://pdf.js/PdfStreamConverter.jsm:1262 > > From 95.0a1, where the PDF wants to be saved: > > 17:01:48.260 TypeError: can't access property "getInterface", requestor is > null 3 PdfStreamConverter.jsm:140:13 > getDOMWindow resource://pdf.js/PdfStreamConverter.jsm:140 > onStopRequest resource://pdf.js/PdfStreamConverter.jsm:1262 This seems to be because the `attachment.contentType` is empty for *new* attachments instead of `application/pdf` when it is read here https://searchfox.org/comm- central/rev/7be97df3877fcaef928606b01d455b2b49d8e9ab/mail/components/compose/content/MsgComposeCommands.js#7610). After this, the error is the same as Bug 1698140. Note that if a message is saved and reopened for editing, any saved pdf attachments will open fine, but any newly added attachments are missing their `contentType`. ~~I think the missing `contentType` is probably a recent regression, since I didn't notice this when reviewing this patch.~~ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945741 Title: [upstream] PDF attachment opens in Firefox instead of the built-in viewer when opened from the compose window To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1945741/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945741]
Could this be from bug 1698140? Because pdf attachments are treated as HTML files instead. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945741 Title: [upstream] PDF attachment opens in Firefox instead of the built-in viewer when opened from the compose window To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1945741/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891643] Re: amavisd-new suggests missing packages
amavis-mc service requires this missing package: "libzeromq-perl" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891643 Title: amavisd-new suggests missing packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/amavisd-new/+bug/1891643/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1751005] Re: libreoffice cannot open a document not within $HOME
And the symbolic link workaround doesn't cure the problem; I'm still getting write errors saving a file to an NFS mount, but /without any apparmor messages/. $ ls -l /etc/apparmor.d/disable/ total 0 lrwxrwxrwx 1 root root 52 May 20 12:15 usr.lib.libreoffice.program.oosplash -> /etc/apparmor.d/usr.lib.libreoffice.program.oosplash lrwxrwxrwx 1 root root 51 May 20 12:15 usr.lib.libreoffice.program.senddoc -> /etc/apparmor.d/usr.lib.libreoffice.program.senddoc lrwxrwxrwx 1 root root 55 May 20 12:15 usr.lib.libreoffice.program.soffice.bin -> /etc/apparmor.d/usr.lib.libreoffice.program.soffice.bin lrwxrwxrwx 1 root root 54 May 20 12:15 usr.lib.libreoffice.program.xpdfimport -> /etc/apparmor.d/usr.lib.libreoffice.program.xpdfimport -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1751005 Title: libreoffice cannot open a document not within $HOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1751005/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1751005] Re: libreoffice cannot open a document not within $HOME
This apparmor problem -- preventing saves on remote filesystems -- is suddenly back on Libreoffice 6. $ soffice --version LibreOffice 6.4.7.2 40(Build:2) $ uname -a Linux prospero 5.4.0-58-generic #64-Ubuntu SMP Wed Dec 9 08:16:25 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux $ cat /etc/lsb-release DISTRIB_ID=LinuxMint DISTRIB_RELEASE=20.1 DISTRIB_CODENAME=ulyssa DISTRIB_DESCRIPTION="Linux Mint 20.1 Ulyssa" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1751005 Title: libreoffice cannot open a document not within $HOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1751005/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928030] [NEW] s3ql 3.7.0 crash, version bump requested
Public bug reported: I "backported" s3ql (built .debs for python3-pyfuse3_3.2.0-2build1, python3-trio_0.18.0-1, and s3ql_3.7.0+dfsg-2build1-local1 to use in Ubuntu 20.04), and encountered a fairly quick crash (like under a minute) when I started writing data to the s3ql filesystem. The log ends with several "During handling of the above exception, another exception occurred:" python tracebacks, ending with "s3ql.block_cache.NoWorkerThreads: no upload threads". Per the bug referenced, this won't result in data loss, a umount + fsck.s3ql cleans it up fine. But still. https://github.com/s3ql/s3ql/issues/234 Bug fixed in 3.7.1, I built 3.7.2 and it works a treat. No crashes under very heavy usage; it's a bit faster than 3.3.4 that 20.04 focal ships with in general usage and much faster to unmount. 3.7.0 is current version in hirsute and impish, so should be bumped to 3.7.2. ** Affects: s3ql (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/1928030 Title: s3ql 3.7.0 crash, version bump requested To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/s3ql/+bug/1928030/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1913953] [NEW] package libqt5core5a:amd64 5.12.8+dfsg-0ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
Public bug reported: Can't install Calibre ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libqt5core5a:amd64 5.12.8+dfsg-0ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Jan 31 08:19:03 2021 DuplicateSignature: package:libqt5core5a:amd64:5.12.8+dfsg-0ubuntu1 Setting up netpbm (2:10.0-15.3build1) ... dpkg: error processing package libqt5core5a:amd64 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2021-01-02 (29 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) 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: qtbase-opensource-src Title: package libqt5core5a:amd64 5.12.8+dfsg-0ubuntu1 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: qtbase-opensource-src (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1913953 Title: package libqt5core5a:amd64 5.12.8+dfsg-0ubuntu1 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/qtbase-opensource-src/+bug/1913953/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1908500] Re: libxslt.a missing from libxslt1-dev
Mattia Rizzolo writes: > Could you please describe: > > * Which release you are basing this bug on? Buster > * Describe why you'd want the static library? My mistake, I had gotten confused while trying to fix a broken build with a libxslt dependency and thought I needed it. You can close this issue, apologies for wasting your time. ht -- Henry S. Thompson, School of Informatics, University of Edinburgh 10 Crichton Street, Edinburgh EH8 9AB, SCOTLAND -- (44) 131 650-4440 Fax: (44) 131 650-4587, e-mail: h...@inf.ed.ac.uk URL: http://www.ltg.ed.ac.uk/~ht/ [mail from me _always_ has a .sig like this -- mail without it is forged spam] The University of Edinburgh is a charitable body, registered in Scotland, with registration number SC005336. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908500 Title: libxslt.a missing from libxslt1-dev To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxslt/+bug/1908500/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1910481] [NEW] ubuntu 20.4.1 install on extenede partion with another existing partition
Public bug reported: as noted on the title ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.15.2 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckMismatches: ./boot/grub/efi.img CasperMD5CheckResult: fail CasperVersion: 1.445.1 CurrentDesktop: ubuntu:GNOME Date: Thu Jan 7 13:10:02 2021 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed initrd=/casper/initrd quiet splash --- maybe-ubiquity LiveMediaBuild: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) 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: New ** Tags: amd64 apport-bug focal ubiquity-20.04.15.2 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1910481 Title: ubuntu 20.4.1 install on extenede partion with another existing partition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1910481/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908500] [NEW] libxslt.a missing from libxslt1-dev
Public bug reported: The libxslt.a file is missing from 1.1.34 ** Affects: libxslt (Ubuntu) Importance: Undecided Status: New ** Summary changed: - libxslt.a missing from libxslt2-dev + libxslt.a missing from libxslt1-dev -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908500 Title: libxslt.a missing from libxslt1-dev To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxslt/+bug/1908500/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1871268] Re: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected
So, what IS the solution exactly On Thu, Dec 3, 2020 at 8:01 AM Josja Van Bever <1871...@bugs.launchpad.net> wrote: > The crash mentioned in previous comment could (most probably?) be > attributed to a (very small?) hardware failure of the usb stick used. > Though, the same stick was used earlier in the same conditions to > install ubuntu 18. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1871268 > > Title: > Installation fails due to useless immediate configuration error when > "Install Third-Party Drivers" is selected > > Status in Ubuntu CD Images: > Fix Released > Status in apt package in Ubuntu: > Fix Released > Status in apt source package in Bionic: > Confirmed > Status in apt source package in Focal: > Triaged > Status in apt source package in Groovy: > Triaged > Status in apt package in Debian: > Unknown > > Bug description: > [Impact] > Installations that really succeeded would then fail because APT could > not immediately configure a package. Which is a pointless way to fail at > that point, because everything did work out anyway. > > So what we do is change that to a warning. > > [Test case] > Not available right now. Issues can flare up and then disappear again. > > [Regression potential] > It's imaginable that we missed something somewhere and some path that > checked for a set error doesn't check it anymore, and we report success > when we hit an error, but it seems unlikely. > > Behavior of --simulate changes. This used to fail before as well, and > will now only produce a warning. We don't believe that is a reason of > concern. > > [Groovy SRU] > The groovy SRU is a sync of the 2.1.11 micro release from Debian > unstable which also incorporates changes to the documentation: A typo fix, > replacing focal with groovy in examples, and minor Dutch manual pages > translation updates. > > We do not have test cases for the documentation changes, and we do not > consider there to be a huge regression potential. As long as they > build, they should be readable - maybe some words are wrong in the > translation, who knows. > > [Original bug report] > Test Case > 1. Install Ubuntu Desktop on hardware with an nVidia card and select to > install 3rd party drivers > 2. Proceed with installation > > The following error message is displayed in /var/log/syslog > /plugininstall.py: Verifying downloads ... > /plugininstall.py: Failed to find package object for > /cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: > '9.3.0-1ubuntu2' not found." > /plugininstall.py: Failed to find package object for > /cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: > "Version: '4.4.10-10ubuntu4' not found." > /plugininstall.py: Failed to find package object for > /cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: > '9.3.0-1ubuntu2' not found." > /plugininstall.py: Failed to find package object for > /cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: > '1.2.11.dfsg-2ubuntu1' not found." > /plugininstall.py: Failed to find package object for > /cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: > '1.0.9-0ubuntu1' not found." > /plugininstall.py: Failed to find package object for > /cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: > "Version: '1.1.3-0ubuntu1' not found." > /plugininstall.py: Failed to find package object for > /cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: > '1.6.9-2ubuntu1' not found." > /plugininstall.py: Failed to find package object for > /cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: > '1.3.4-0ubuntu1' not found." > /plugininstall.py: Failed to find package object for > /cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: > "Version: '3.6.0-2ubuntu1' not found." > /plugininstall.py: Failed to find package object for > /cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: > "Version: '1.6.9-2ubuntu1' not found." > /plugininstall.py: Failed to find package object for > /cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: > '1.1.5-1' not found." > /plugininstall.py: Failed to find package object for > /cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: > '5.0.3-1' not found." > /plugininstall.py: Failed to find package object for > /cdrom//pool/main/libx/libxxf86vm/libxxf86vm1_1.1.4-1build1_i386.deb: > "Version: '1.1.4-1build1' not found." > /plugininstall.py: Downloads verified successfully > ubiquity: Error in function: install > /plugininstall.py: Exception during installation: > /plugininstall.py: apt_pkg.Error: E:Could not configure 'libc6:i386'. , > E:Could not perform immediate configuration on 'libgcc-s1:i386'. Please see > man 5 apt.conf under APT::Immediate-Configure for details
[Bug 1905815] Re: python2 code in greylistd
focal and groovy greylistd tagged v0.8.8.8 but it's still python2 codes https://github.com/eurovibes/greylistd/blob/master/program/greylistd shows working python3 codes -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905815 Title: python2 code in greylistd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/greylistd/+bug/1905815/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905815] [NEW] python2 code in greylistd
Public bug reported: python2 deprecated, greylistd has python3 ported ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: greylistd (not installed) ProcVersionSignature: Ubuntu 5.4.0-1031.32-azure 5.4.65 Uname: Linux 5.4.0-1031-azure x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Nov 27 11:43:55 2020 InstallationDate: Installed on 2020-01-29 (303 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: greylistd UpgradeStatus: Upgraded to focal on 2020-11-06 (20 days ago) ** Affects: greylistd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal uec-images -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905815 Title: python2 code in greylistd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/greylistd/+bug/1905815/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1903048] Re: [SRU] Bluetooth won't activate on the pi 400
I understand the logic of the of doing this and don't disagree. However, as this is an entry level device and I believe the only true 64bit O/S advertised for this device, the fact that it does not not work out of the box may impact on the perception of potential new Ubuntu users? Reading Tony's post the Mate website does not say it will work on the PI400 where as the Ubuntu site does. I think the main issue is that people think it is the same board as the Pi4 and it is not. Just my opinion. On Thu, 2020-11-12 at 11:11 +, Sebastien Bacher wrote: > Sorry but I'm reverting that upload for now until the patches are > properly upstreamed. We have been bitten too often by unforwarded > changes that create issues or create maintainance burden over the > years > and we currently don't have the team capacity to deal with extra > cost. > If foundations would like to step up and take over bluez though > that's a > discussion we could have... > > ** Changed in: bluez (Ubuntu Hirsute) >Status: Fix Released => Triaged > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903048 Title: [SRU] Bluetooth won't activate on the pi 400 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1903048/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903048] Re: [SRU] Bluetooth won't activate on the pi 400
Test case works perfectly on the Pi400. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903048 Title: [SRU] Bluetooth won't activate on the pi 400 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1903048/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903048] Re: [SRU] Bluetooth won't activate on the pi 400
Thanks guys for all the work. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903048 Title: [SRU] Bluetooth won't activate on the pi 400 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1903048/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903048] Re: Bluetooth won't activate on the pi 400
Is this the same as: #1903286? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903048 Title: Bluetooth won't activate on the pi 400 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1903048/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903286] Re: Pi400 Bluetooth device not being recognised, Bluetooth manager and Bluetooth adaptors commands show no screen output and appear inoperative
I can confirm all of the above. Also looking at the Pi OS the in which the bluetooth works it lists BCM2711-rpi-400.dts. Also unblocking the soft block has no effect. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903286 Title: Pi400 Bluetooth device not being recognised, Bluetooth manager and Bluetooth adaptors commands show no screen output and appear inoperative To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1903286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901083] Re: Inpsiron 1545 -- superflous key stroke logs (translated set 2, code 0x8d)
"1) Do you actually have superflous key strokes, along with that which is logged in dmesg?" Nope, totally asymptomatic. "2) Could you please test the latest mainline kernel (now 5.9.1) and advise to the results?" Here ya go. I can attach entire dmesg if you want, but from 5.9.1 dmesg: [ 256.705741] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [ 256.705745] atkbd serio0: Use 'setkeycodes e00d ' to make it known. [ 265.118971] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [ 265.118975] atkbd serio0: Use 'setkeycodes e00d ' to make it known. "3) Did you personally test this with your Inspiron 1545 in a prior version of Ubuntu" No. I don't think it started logging this (at least often enough to notice) until my battery went from holding like a minute or two of battery life to holding 0, which only happened in the last 2-4 weeks. Honestly, I'd be totally fine if it was closed "wontfix" (I guess launchpad doesn't have that) or "invalid", the kernel's logging a non- standard keystroke sent by the Dell, which seems legitimate and harmless (it'd be a nuisance if it was every second but it's not close to that); in addition the Dell is effectively sending it in response to a hardware failure, so I could see "if you don't want this in your kernel log, replace your battery" being a legitimate response. Let me know and I'll set it! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901083 Title: Inpsiron 1545 -- superflous key stroke logs (translated set 2, code 0x8d) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901083/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901083] Re: Inpsiron 1545 -- superflous key stroke logs (translated set 2, code 0x8d)
"1) Do you actually have superflous key strokes, along with that which is logged in dmesg?" Nope, totally asymptomatic. "2) Could you please test the latest mainline kernel (now 5.9.1) and advise to the results?" Here ya go. I can attach entire dmesg if you want, but from 5.9.1 dmesg: [ 256.705741] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [ 256.705745] atkbd serio0: Use 'setkeycodes e00d ' to make it known. [ 265.118971] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [ 265.118975] atkbd serio0: Use 'setkeycodes e00d ' to make it known. "3) Did you personally test this with your Inspiron 1545 in a prior version of Ubuntu" No. I don't think it started logging this (at least often enough to notice) until my battery went from holding like a minute or two of battery life to holding 0, which only happened in the last 2-4 weeks. Honestly, I'd be totally fine if it was closed "wontfix" (I guess launchpad doesn't have that) or "invalid", the kernel's logging a non- standard keystroke sent by the Dell, which seems legitimate and harmless (it'd be a nuisance if it was every second but it's not close to that); in addition the Dell is effectively sending it in response to a hardware failure, so I could see "if you don't want this in your kernel log, replace your battery" being a legitimate response. Let me know and I'll set it! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901083 Title: Inpsiron 1545 -- superflous key stroke logs (translated set 2, code 0x8d) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901083/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901083] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1901083/+attachment/5425626/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901083 Title: Inpsiron 1545 -- superflous key stroke logs (translated set 2, code 0x8d) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901083/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901083] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1901083/+attachment/5425632/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901083 Title: Inpsiron 1545 -- superflous key stroke logs (translated set 2, code 0x8d) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901083/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901083] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1901083/+attachment/5425630/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901083 Title: Inpsiron 1545 -- superflous key stroke logs (translated set 2, code 0x8d) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901083/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901083] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1901083/+attachment/5425634/+files/RfKill.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901083 Title: Inpsiron 1545 -- superflous key stroke logs (translated set 2, code 0x8d) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901083/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901083] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1901083/+attachment/5425636/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901083 Title: Inpsiron 1545 -- superflous key stroke logs (translated set 2, code 0x8d) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901083/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901083] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1901083/+attachment/5425627/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901083 Title: Inpsiron 1545 -- superflous key stroke logs (translated set 2, code 0x8d) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901083/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901083] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1901083/+attachment/5425629/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901083 Title: Inpsiron 1545 -- superflous key stroke logs (translated set 2, code 0x8d) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901083/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901083] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1901083/+attachment/5425628/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901083 Title: Inpsiron 1545 -- superflous key stroke logs (translated set 2, code 0x8d) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901083/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901083] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1901083/+attachment/5425635/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901083 Title: Inpsiron 1545 -- superflous key stroke logs (translated set 2, code 0x8d) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901083/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901083] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1901083/+attachment/5425631/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901083 Title: Inpsiron 1545 -- superflous key stroke logs (translated set 2, code 0x8d) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901083/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901083] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1901083/+attachment/5425633/+files/PulseList.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901083 Title: Inpsiron 1545 -- superflous key stroke logs (translated set 2, code 0x8d) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901083/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901083] Re: Inpsiron 1545 -- superflous key stroke logs (translated set 2, code 0x8d)
(uname -a: Linux inspiron-1545.local 5.4.0-52-generic #57~18.04.1-Ubuntu SMP Thu Oct 15 14:04:49 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux ) I've been using 5.7.19 by default, but I'm on 5.4.0-52-generic for this since it's a supported kernel. (These atkbd messages are identical in both.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901083 Title: Inpsiron 1545 -- superflous key stroke logs (translated set 2, code 0x8d) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901083/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901083] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1901083/+attachment/5425625/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901083 Title: Inpsiron 1545 -- superflous key stroke logs (translated set 2, code 0x8d) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901083/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901083] Re: Inpsiron 1545 -- superflous key stroke logs (translated set 2, code 0x8d)
apport information ** Tags added: apport-collected staging ** Description changed: I posted some information on bug #549741 stating that I was getting similar logs to what people were seeing in there, and was advised to go ahead and file a bug. I'm on a Dell Inspiron 1541 (this machine is approaching a decade old.) In dmesg, I get a pair like: [ 529.926369] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [ 529.926374] atkbd serio0: Use 'setkeycodes e00d ' to make it known. [ 536.168508] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [ 536.168512] atkbd serio0: Use 'setkeycodes e00d ' to make it known. This pair will be like 2-10 seconds apart, then it could be 5 minutes or more between pairs. I've been running 5.7.19 kernel (installed via mainline), but did boot 5.4.0-52-generic to file this since it's a supported kerenl (I seriously doubted it would make a difference since this has apparently been logged since at least the 2.6.x kernel series, and it didn't.) I consider this bug pretty minor to possibly invalid; these keystroke messages spam up the kernel log a little but not too badly (since I'm not getting them every second like the original poster in #549741, but rather getting one, getting another a few seconds later, then it may be 5 minutes or more before I get another pair of them a few seconds apart.). My battery packed up quite a while ago and shows 0% charge.. it has begun every so often "dropping off" and back on a few seconds later, both in gkrellm, and whatever app shows the battery icon in top right (near network manager, volume, etc.) I think it sends this 0x8d each time the battery status changes. Not sure what the point of the 0x8d is, but it's harmless for Linux to ignore, it's well aware of the status changes via ACPI anyway. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.4.0-52-generic 5.4.0-52.57~18.04.1 ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.18 Architecture: amd64 CurrentDesktop: GNOME-Flashback:GNOME Date: Thu Oct 22 15:13:25 2020 InstallationDate: Installed on 2018-09-09 (774 days ago) InstallationMedia: ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.4 UpgradeStatus: No upgrade log present (probably fresh install) + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.18 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: hwertz 3637 F pulseaudio + CurrentDesktop: GNOME-Flashback:GNOME + DistroRelease: Ubuntu 18.04 + InstallationDate: Installed on 2018-09-09 (774 days ago) + InstallationMedia: + + MachineType: Dell Inc. Inspiron 1545 + Package: linux (not installed) + ProcEnviron: + TERM=screen.xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: 0 i915drmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=e2909436-8fb2-4f09-a757-822f78af9d2e ro nosplash noautogroup mitigations=off + ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65 + RelatedPackageVersions: + linux-restricted-modules-5.4.0-52-generic N/A + linux-backports-modules-5.4.0-52-generic N/A + linux-firmware1.173.19 + StagingDrivers: ashmem_linux + Tags: bionic staging + Uname: Linux 5.4.0-52-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers xpra + _MarkForUpload: True + dmi.bios.date: 12/07/2009 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: A14 + dmi.board.name: 0G848F + dmi.board.vendor: Dell Inc. + dmi.chassis.type: 8 + dmi.chassis.vendor: Dell Inc. + dmi.modalias: dmi:bvnDellInc.:bvrA14:bd12/07/2009:svnDellInc.:pnInspiron1545:pvr:rvnDellInc.:rn0G848F:rvr:cvnDellInc.:ct8:cvr: + dmi.product.name: Inspiron 1545 + dmi.sys.vendor: Dell Inc. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1901083/+attachment/5425623/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901083 Title: Inpsiron 1545 -- superflous key stroke logs (translated set 2, code 0x8d) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901083/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901083] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1901083/+attachment/5425624/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901083 Title: Inpsiron 1545 -- superflous key stroke logs (translated set 2, code 0x8d) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901083/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901083] Re: Inpsiron 1545 -- superflous key stroke logs (translated set 2, code 0x8d)
** Description changed: I posted some information on bug #549741 stating that I was getting similar logs to what people were seeing in there, and was advised to go ahead and file a bug. In dmesg, I get a pair like: [ 529.926369] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [ 529.926374] atkbd serio0: Use 'setkeycodes e00d ' to make it known. [ 536.168508] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [ 536.168512] atkbd serio0: Use 'setkeycodes e00d ' to make it known. This pair will be like 2-10 seconds apart, then it could be 5 minutes or more between pairs. I've been running 5.7.19 kernel (installed via mainline), but did boot 5.4.0-52-generic to file this since it's a supported kerenl (I seriously doubted it would make a difference since this has apparently been logged since at least the 2.6.x kernel series, and it didn't.) I consider this bug pretty minor to possibly invalid; these keystroke messages spam up the kernel log a little but not too badly (since I'm not getting them every second like the original poster in #549741, but rather getting one, getting another a few seconds later, then it may be 5 minutes or more before I get another pair of them a few seconds apart.). My battery packed up quite a while ago and shows 0% charge.. it has begun every so often "dropping off" and back on a few seconds later, both in gkrellm, and whatever app shows the battery icon in top right (near network manager, volume, etc.) I think it sends this 0x8d each - time the battery status changes. + time the battery status changes. Not sure what the point of the 0x8d + is, but it's harmless for Linux to ignore, it's well aware of the status + changes via ACPI anyway. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.4.0-52-generic 5.4.0-52.57~18.04.1 ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.18 Architecture: amd64 CurrentDesktop: GNOME-Flashback:GNOME Date: Thu Oct 22 15:13:25 2020 InstallationDate: Installed on 2018-09-09 (774 days ago) InstallationMedia: - + ProcEnviron: - TERM=screen.xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=screen.xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.4 UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: - I posted some information on bug #549741 stating that I was getting similar logs to what people were seeing in there, and was advised to go ahead and file a bug. In dmesg, I get a pair like: + I posted some information on bug #549741 stating that I was getting similar logs to what people were seeing in there, and was advised to go ahead and file a bug. I'm on a Dell Inspiron 1541 (this machine is approaching a decade old.) In dmesg, I get a pair like: [ 529.926369] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [ 529.926374] atkbd serio0: Use 'setkeycodes e00d ' to make it known. [ 536.168508] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [ 536.168512] atkbd serio0: Use 'setkeycodes e00d ' to make it known. This pair will be like 2-10 seconds apart, then it could be 5 minutes or more between pairs. I've been running 5.7.19 kernel (installed via mainline), but did boot 5.4.0-52-generic to file this since it's a supported kerenl (I seriously doubted it would make a difference since this has apparently been logged since at least the 2.6.x kernel series, and it didn't.) I consider this bug pretty minor to possibly invalid; these keystroke messages spam up the kernel log a little but not too badly (since I'm not getting them every second like the original poster in #549741, but rather getting one, getting another a few seconds later, then it may be 5 minutes or more before I get another pair of them a few seconds apart.). My battery packed up quite a while ago and shows 0% charge.. it has begun every so often "dropping off" and back on a few seconds later, both in gkrellm, and whatever app shows the battery icon in top right (near network manager, volume, etc.) I think it sends this 0x8d each time the battery status changes. Not sure what the point of the 0x8d is, but it's harmless for Linux to ignore, it's well aware of the status changes via ACPI anyway. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.4.0-52-generic 5.4.0-52.57~18.04.1 ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.18 Architecture: amd64 CurrentDesktop: GNOME-Flashback:GNOME Date: Thu Oct 2
[Bug 1901083] Re: Inpsiron 1545 -- superflous key stroke logs (translated set 2, code 0x8d)
I assumed dmesg would be attached... It is now! ** Attachment added: "dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.4/+bug/1901083/+attachment/5425615/+files/dmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901083 Title: Inpsiron 1545 -- superflous key stroke logs (translated set 2, code 0x8d) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901083/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901083] [NEW] Inpsiron 1545 -- superflous key stroke logs (translated set 2, code 0x8d)
Public bug reported: I posted some information on bug #549741 stating that I was getting similar logs to what people were seeing in there, and was advised to go ahead and file a bug. In dmesg, I get a pair like: [ 529.926369] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [ 529.926374] atkbd serio0: Use 'setkeycodes e00d ' to make it known. [ 536.168508] atkbd serio0: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0). [ 536.168512] atkbd serio0: Use 'setkeycodes e00d ' to make it known. This pair will be like 2-10 seconds apart, then it could be 5 minutes or more between pairs. I've been running 5.7.19 kernel (installed via mainline), but did boot 5.4.0-52-generic to file this since it's a supported kerenl (I seriously doubted it would make a difference since this has apparently been logged since at least the 2.6.x kernel series, and it didn't.) I consider this bug pretty minor to possibly invalid; these keystroke messages spam up the kernel log a little but not too badly (since I'm not getting them every second like the original poster in #549741, but rather getting one, getting another a few seconds later, then it may be 5 minutes or more before I get another pair of them a few seconds apart.). My battery packed up quite a while ago and shows 0% charge.. it has begun every so often "dropping off" and back on a few seconds later, both in gkrellm, and whatever app shows the battery icon in top right (near network manager, volume, etc.) I think it sends this 0x8d each time the battery status changes. Not sure what the point of the 0x8d is, but it's harmless for Linux to ignore, it's well aware of the status changes via ACPI anyway. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.4.0-52-generic 5.4.0-52.57~18.04.1 ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.18 Architecture: amd64 CurrentDesktop: GNOME-Flashback:GNOME Date: Thu Oct 22 15:13:25 2020 InstallationDate: Installed on 2018-09-09 (774 days ago) InstallationMedia: ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.4 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901083 Title: Inpsiron 1545 -- superflous key stroke logs (translated set 2, code 0x8d) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901083/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 549741] Re: [Dell Latitude 131L] keyboard not recognized properly; logs fill up with messages
I have an Inspiron 1545 that's doing this (Ubuntu 18.04.5); mine is nowhere near every second though. My battery is toast, a while ago it began (occasionally) having the "0% battery" occasionally drop off then reappear a few seconds later (both in gkrellm and the battery status on the top right near network-manager etc.). Based on the timing in the logs (0x8d then another a few seconds later), I think it sends a 0x8d keystroke both on battery disappearing and once on reappearing. I'd hesitate to consider it a bug; it's minorly spamming up the logs with a superfluous keystroke the Dell's sending, while causing no harm (if the point of the keystroke is to indicate change in battery status, Linux is already well aware of this via ACPI anyway.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/549741 Title: [Dell Latitude 131L] keyboard not recognized properly; logs fill up with messages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/549741/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871268] Re: Installation fails with Could not configure 'libc6:i386'. , E:Could not perform immediate configuration on 'libgcc-s1:i386'
Installed correctly the first time. Upon reinstall, received this issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871268 Title: Installation fails with Could not configure 'libc6:i386'. , E:Could not perform immediate configuration on 'libgcc-s1:i386' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1871268/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887222] Re: Plugins bundled with Rhythmbox link to for-sale domain
** Information type changed from Private Security to Public Security ** Summary changed: - Plugins bundled with Rhythmbox link to for-sale domain + Plugins bundled with Rhythmbox link to for-sale domain (rhythmbox.org has been drop-caught) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887222 Title: Plugins bundled with Rhythmbox link to for-sale domain (rhythmbox.org has been drop-caught) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1887222/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1885234] Re: package zsys 0.4.6 failed to install/upgrade: installed zsys package post-installation script subprocess returned error exit status 1
Sorry If I am wasting people time but I have just been reading bug #1886154 This is the same issue I had when I started to install a package (libdvd-pkg) and was only resolved when I followed the instructions above. Could it be that they are connected? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1885234 Title: package zsys 0.4.6 failed to install/upgrade: installed zsys package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1885234/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886114] [NEW] package samba-common-bin 2:4.11.6+dfsg-0ubuntu1.3 failed to install/upgrade: installed samba-common-bin package post-installation script subprocess returned error exit status 1
Public bug reported: I was able to workaround the installation failure by using systemd- tmpfiles to create the missing directory: +bryan@bryanNAS:~$ sudo dpkg --configure -a Setting up samba-common-bin (2:4.11.6+dfsg-0ubuntu1.3) ... Checking smb.conf with testparm Load smb config files from /etc/samba/smb.conf Loaded services file OK. ERROR: lock directory /run/samba does not exist ERROR: pid directory /run/samba does not exist WARNING: some services use vfs_fruit, others don't. Mounting them in conjunction on OS X clients results in undefined behaviour. Server role: ROLE_STANDALONE dpkg: error processing package samba-common-bin (--configure): installed samba-common-bin package post-installation script subprocess returned error exit status 1 dpkg: dependency problems prevent configuration of samba: samba depends on samba-common-bin (= 2:4.11.6+dfsg-0ubuntu1.3); however: Package samba-common-bin is not configured yet. dpkg: error processing package samba (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: samba-common-bin samba +bryan@bryanNAS:~$ sudo /bin/systemd-tmpfiles --create /usr/lib/tmpfiles.d/samba.conf +bryan@bryanNAS:~$ sudo dpkg --configure -a Setting up samba-common-bin (2:4.11.6+dfsg-0ubuntu1.3) ... Checking smb.conf with testparm Load smb config files from /etc/samba/smb.conf Loaded services file OK. WARNING: some services use vfs_fruit, others don't. Mounting them in conjunction on OS X clients results in undefined behaviour. Server role: ROLE_STANDALONE Done Setting up samba (2:4.11.6+dfsg-0ubuntu1.3) ... Installing new version of config file /etc/init.d/nmbd ... Installing new version of config file /etc/init.d/samba-ad-dc ... Installing new version of config file /etc/init.d/smbd ... Installing new version of config file /etc/logrotate.d/samba ... Samba is not being run as an AD Domain Controller: Masking samba-ad-dc.service Please ignore the following error about deb-systemd-helper not finding those services. (samba-ad-dc.service already masked) Removing obsolete conffile /etc/init.d/samba ... Removing obsolete conffile /etc/init/nmbd.conf ... Removing obsolete conffile /etc/init/reload-smbd.conf ... Removing obsolete conffile /etc/init/samba-ad-dc.conf ... Removing obsolete conffile /etc/init/smbd.conf ... Failed to preset unit: Unit file /etc/systemd/system/samba-ad-dc.service is masked. /usr/bin/deb-systemd-helper: error: systemctl preset failed on samba-ad-dc.service: No such file or directory samba-ad-dc.service is a disabled or a static unit not running, not starting it. Processing triggers for libc-bin (2.31-0ubuntu9) ... Processing triggers for systemd (245.4-4ubuntu3.1) ... Processing triggers for ureadahead (0.100.0-21) ... ProblemType: Package DistroRelease: Ubuntu 20.04 Package: samba-common-bin 2:4.11.6+dfsg-0ubuntu1.3 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Jul 2 17:08:23 2020 ErrorMessage: installed samba-common-bin package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2017-08-20 (1047 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) OtherFailedConnect: Yes Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SambaServerRegression: Yes SmbConfIncluded: No SourcePackage: samba TestparmExitCode: 0 Title: package samba-common-bin 2:4.11.6+dfsg-0ubuntu1.3 failed to install/upgrade: installed samba-common-bin package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2020-07-02 (0 days ago) ** Affects: samba (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886114 Title: package samba-common-bin 2:4.11.6+dfsg-0ubuntu1.3 failed to install/upgrade: installed samba-common-bin package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1886114/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1885234] Re: package zsys 0.4.6 failed to install/upgrade: installed zsys package post-installation script subprocess returned error exit status 1
Exactly the same thing happened to me and I have no idea how or why the bpool had been exported. The one thing I would add to Corey's work around, which worked perfectly is that the $MYDRIVEID I used was the UUID of the bpool partition (best found in disks), unless that was just my issue? Thanks Corey I have been hours on this! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1885234 Title: package zsys 0.4.6 failed to install/upgrade: installed zsys package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1885234/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1885234] Re: package zsys 0.4.6 failed to install/upgrade: installed zsys package post-installation script subprocess returned error exit status 1
One additional point I had not enabled focal-proposed and have just checked it is still not enabled. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1885234 Title: package zsys 0.4.6 failed to install/upgrade: installed zsys package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1885234/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863116] Re: debian/rules editconfigs does not work on s390x to change s390x only configs
Running on an arm64 build machine, I checked out from git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/focal the branch HEAD detached at Ubuntu-5.4.0-39.43 and follow the instructions at https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel#Modifying_the_configuration and find that it iterates through all target machines, and requires that each target's cross compiler to be installed correctly. So from my perspective, working as close as possible to head, I still see the same problems I don't know why this was marked 'invalid'. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863116 Title: debian/rules editconfigs does not work on s390x to change s390x only configs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1863116/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879997] [NEW] HP-255-G7-Notebook-PC 5.3.0-51-generic
Public bug reported: HP-255-G7-Notebook-PC System wont reboot or shutdown after kernel 5.3.0-53 update ** Affects: linux (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/1879997 Title: HP-255-G7-Notebook-PC 5.3.0-51-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879997/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853204] Re: "speedtest-cli 2.0.0-1" package outputs incorrect results
This is a really annoying bug to have in an LTS. I can confirm that if you install it from the command line with apt-get it fails to get the correct upload speed only displaying approx 20% of the correct upload speed. Installing the Python version via pip works but is not ideal. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853204 Title: "speedtest-cli 2.0.0-1" package outputs incorrect results To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/speedtest-cli/+bug/1853204/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872108] Re: Bass not on working Lenovo ThinkPad X1 Carbon 7th gen running focal
Hi, I'm affected by the same bug. I have read the last thread, and I understand there is a workaround for my laptop. However, they are not sure whether the workaround could affect other devices. So, I would like to know whether this means that this bug will get stuck here and stay in the current status. Could we expect a solution soon? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872108 Title: Bass not on working Lenovo ThinkPad X1 Carbon 7th gen running focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1872108/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 263435]
Removing the release note flag. Whatever was going on here was happening in the Firefox 48 timeframe. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/263435 Title: Cannot use firefox keyboard shortcuts when flash object is selected To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/263435/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1825842] Re: [vmware] Background goes white when using scaling (200%, 300% or 400%)
Hello, I have this problem on my Ubuntu VMs (since 19.04). However, my Debian 10 VMs are not affected. I hope this bug will be fixed before the LTS. This graphics bug makes my VMs unusable. 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/1825842 Title: [vmware] Background goes white when using scaling (200%, 300% or 400%) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1825842/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849543] [NEW] crontab truncates passed in filename to 100 characters
Public bug reported: If you want to install cron from a file you run crontab [filename]. Unfortunately the filename is truncated to 100 characters in the source code set from #define MAX_FNAME 100 The MAX_FNAME should actually be set to PATH_MAX which is 4096 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cron 3.0pl1-128.1ubuntu1 ProcVersionSignature: User Name 4.15.0-1048.50-aws 4.15.18 Uname: Linux 4.15.0-1048-aws x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 Date: Wed Oct 23 13:06:13 2019 Ec2AMI: ami-0977c44707608ee22 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-1d Ec2InstanceType: t2.large Ec2Kernel: unavailable Ec2Ramdisk: unavailable ProcEnviron: TERM=xterm-color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: cron UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: cron (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ec2-images 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/1849543 Title: crontab truncates passed in filename to 100 characters To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1849543/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1800465] Re: Vulkan error when using NVIDIA-Prime
Same bug here on two different laptop. Fresh install Ubuntu 18.04.2 nvidia-driver-418 4.18.0-18-generic First $vulkaninfo => OK Switch on Intel with NVIDIA X Server settings reboot Switch to NVIDIA with NVIDIA X Server settings reboot $vulkaninfo => VK_ERROR_INITIALIZATION_FAILED $sudo vulkaninfo => OK then vulkaninfo => OK So now before launch Steam to play games that use vulkan I always do sudo vulkaninfo -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1800465 Title: Vulkan error when using NVIDIA-Prime To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1800465/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1791427] Re: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th
Hi Aaron,
I did:
$ sudo dpkg -i linux-{image,headers}-4.20.0-rc3+_4.20.0-rc3+-6_amd64.deb
# edit /etc/default/grub so it now reads:
GRUB_CMDLINE_LINUX_DEFAULT="acpi_osi=! acpi_osi='Windows 2009'
modprobe.blacklist=nouveau rmi_core.debug_flags=0x7"
$ sudo update-grub
$ sudo /sbin/shutdown now
# reboot into kernel 4.20
# touchpad now more responsive - it picks up lighter and faster touches as
clicks.
# close lid to suspend. on first two wakeups, touchpad worked
# on third wakeup, touchpad didn't work. then:
$ cat /proc/interrupts | grep rmi > rmi_irq.log
# move finger around on touchpad for several seconds, even though mouse
pointer didn't move
$ cat /proc/interrupts | grep rmi >> rmi_irq.log
# rmi_irq.log is empty
$ journalctl -b 0 -k > journalctl.log
# just for curiosity, close lid again, wait 10 seconds, reopen. Still,
mousepad is unresponsive.
# Then, without warning, laptop goes into sleep mode (with lid still open. I
press the button to resume. Screen blinks about five times, and finally wakes
up. Now, mousepad works.
$ journalctl -b 0 -k > journalctl.after_blink.log
$ wc -l journalctl.*
1735 journalctl.after_blink.log
1586 journalctl.log
Have attached journalctl.after_blink.log
Thanks in advance for any information you could provide!
** Attachment added: "journalctl.after_blink.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791427/+attachment/5258047/+files/journalctl.after_blink.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1791427
Title:
Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1
Carbon 6th
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791427/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823779] [NEW] package systemd 239-7ubuntu10.12 failed to install/upgrade: package systemd is already installed and configured
Public bug reported: I was updating from the software updater ProblemType: Package DistroRelease: Ubuntu 18.10 Package: systemd 239-7ubuntu10.12 ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13.2 AptdaemonVersion: 1.1.1+bzr982-0ubuntu20 Architecture: amd64 Date: Mon Apr 8 14:01:33 2019 DpkgTerminalLog: dpkg: error processing package systemd (--configure): package systemd is already installed and configured ErrorMessage: package systemd is already installed and configured InstallationDate: Installed on 2019-04-04 (3 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0cf3:e500 Atheros Communications, Inc. Bus 001 Device 003: ID 04f2:b5d9 Chicony Electronics Co., Ltd Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80X2 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-17-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.10 PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3 RelatedPackageVersions: dpkg 1.19.0.5ubuntu5 apt 1.7.4 SourcePackage: dpkg Title: package systemd 239-7ubuntu10.12 failed to install/upgrade: package systemd is already installed and configured UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/23/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 4QCN48WW(V2.12) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40679 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 520S-14IKB dmi.modalias: dmi:bvnLENOVO:bvr4QCN48WW(V2.12):bd11/23/2018:svnLENOVO:pn80X2:pvrLenovoideapad520S-14IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad520S-14IKB: dmi.product.family: ideapad 520S-14IKB dmi.product.name: 80X2 dmi.product.sku: LENOVO_MT_80X2_BU_idea_FM_ideapad 520S-14IKB dmi.product.version: Lenovo ideapad 520S-14IKB dmi.sys.vendor: LENOVO ** Affects: dpkg (Ubuntu) Importance: Undecided Status: New ** Tags: already-installed amd64 apport-package cosmic 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/1823779 Title: package systemd 239-7ubuntu10.12 failed to install/upgrade: package systemd is already installed and configured To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1823779/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1816319] Re: package shim-signed 1.33.1~14.04.4+13-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Killed)
(p.-) I should have know that! Thanks. On 2/17/19 9:45 PM, Steve Langasek wrote: > I'm sorry to tell you that this wasn't an infinite loop, it was going > through the process of generating signed kernel module files for each of > the kernel versions you have installed and you have a LOT of kernel > versions installed. You might want to try running 'sudo apt autoremove > --purge' to remove the older unused kernels, since they waste space on > your system and slow down all upgrades of bootloader packages. > > Be sure to check the output of this command before saying 'Y', to ensure > only the packages you expect to remove are being removed. > > ** Changed in: shim-signed (Ubuntu) > Status: New => Invalid > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1816319 Title: package shim-signed 1.33.1~14.04.4+13-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Killed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1816319/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1816319] [NEW] package shim-signed 1.33.1~14.04.4+13-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Killed)
Public bug reported: install process went into an infinite loop, installing and uninstalling the same components. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: shim-signed 1.33.1~14.04.4+13-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-165.215-generic 3.13.11-ckt39 Uname: Linux 3.13.0-165-generic x86_64 .proc.sys.kernel.moksbstate.disabled: 0 ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 BootEFIContents: grub.cfg grubx64.efi mmx64.efi shimx64.efi Date: Sun Feb 17 17:49:49 2019 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 DuplicateSignature: package:shim-signed:1.33.1~14.04.4+13-0ubuntu2:subprocess installed post-installation script was killed by signal (Killed) ErrorMessage: subprocess installed post-installation script was killed by signal (Killed) InstallationDate: Installed on 2017-08-25 (541 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 RelatedPackageVersions: dpkg 1.17.5ubuntu5.8 apt 1.0.1ubuntu2.19 SecureBoot: 6 0 0 0 0 SourcePackage: shim-signed Title: package shim-signed 1.33.1~14.04.4+13-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Killed) UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: shim-signed (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1816319 Title: package shim-signed 1.33.1~14.04.4+13-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Killed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1816319/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1799430] Re: Icon dock visible on lock screen
*** This bug is a duplicate of bug 1769383 *** https://bugs.launchpad.net/bugs/1769383 I am effected by this as well. Ubuntu 18.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1799430 Title: Icon dock visible on lock screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-dashtodock/+bug/1799430/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1791427] Re: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th
Hi all, Just wanted to add my experience with this. I also have found that my Synaptics touchpad becomes unresponsive after waking from a suspend. It isn't restored by a modprobe -r psmouse / modprobe psmouse. The only thing that restores it is a shutdown (without -r option) followed by a fresh boot. I noticed also that, when it is showing this unresponsive touchpad symptom, sudo cat /dev/input/event8 | hexdump produces nothing at all when i move my finger around on the touchpad (event8 is the touchpad in my system, as shown by /proc/bus/input/devices). Yet, doing: sudo cat /dev/input/event16 | hexdump (which is my usb wireless mouse) does produce output when I move my mouse around. I'm not very familiar with kernel, drivers, firmware, etc. I did think the bit about /dev/input/event8 was interesting though, but I'm not sure what to do with that information. If anyone is interested, please feel free to suggest a set of commands and their output you might want to see, or procedures to try. I hope this new data point is useful. Thanks in advance! Henry Some other things: henry@henry-gs65:~$ uname -a Linux henry-gs65 4.15.0-43-generic #46-Ubuntu SMP Thu Dec 6 14:45:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux henry@henry-gs65:~$ sudo lshw | head -n 25 henry-gs65 description: Notebook product: GS65 Stealth Thin 8RF (16Q2.1) vendor: Micro-Star International Co., Ltd. version: REV:1.0 serial: 9S716Q211405ZI883 width: 64 bits capabilities: smbios-3.1 dmi-3.1 smp vsyscall32 configuration: boot=normal chassis=notebook family=GS sku=16Q2.1 uuid=FCEFF7B9-5244-47ED-B96D-2A2CF506C220 *-core description: Motherboard product: MS-16Q2 vendor: Micro-Star International Co., Ltd. physical id: 0 version: REV:1.0 serial: BSS-0123456789 slot: Default string *-firmware description: BIOS vendor: American Megatrends Inc. physical id: 1 version: E16Q2IMS.110 date: 10/08/2018 size: 64KiB capacity: 15MiB henry@henry-gs65:~$ grep -B 1 -A 10 Synaptics /proc/bus/input/devices I: Bus=0011 Vendor=0002 Product=0001 Version= N: Name="PS/2 Synaptics TouchPad" P: Phys=isa0060/serio1/input0 S: Sysfs=/devices/platform/i8042/serio1/input/input34 U: Uniq= H: Handlers=mouse0 event8 B: PROP=1 B: EV=7 B: KEY=70000 0 0 0 0 B: REL=3 henry@henry-gs65:~$ journalctl -b 0 | grep -i touchpad | grep kernel Jan 06 21:02:58 henry-gs65 kernel: psmouse serio1: synaptics: Your touchpad (PNP: SYN150d SYN1500 SYN0002 PNP0f13) says it can support a different bus. If i2c-hid and hid-rmi are not used, you might want to try setting psmouse.synaptics_intertouch to 1 and report this to linux-in...@vger.kernel.org. Jan 06 21:02:58 henry-gs65 kernel: psmouse serio1: synaptics: Touchpad model: 1, fw: 8.16, id: 0x1e2b1, caps: 0xf00123/0x840300/0x12e800/0x40, board id: 3414, fw id: 2667658 Jan 06 21:02:58 henry-gs65 kernel: input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input6 Jan 09 19:40:09 henry-gs65 kernel: psmouse serio1: synaptics: Your touchpad (PNP: SYN150d SYN1500 SYN0002 PNP0f13) says it can support a different bus. If i2c-hid and hid-rmi are not used, you might want to try setting psmouse.synaptics_intertouch to 1 and report this to linux-in...@vger.kernel.org. Jan 09 19:40:09 henry-gs65 kernel: psmouse serio1: synaptics: Touchpad model: 1, fw: 8.16, id: 0x1e2b1, caps: 0xf00123/0x840300/0x12e800/0x40, board id: 3414, fw id: 2667658 Jan 09 19:40:09 henry-gs65 kernel: input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input24 Jan 09 19:43:16 henry-gs65 kernel: input: PS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input26 Jan 09 19:49:15 henry-gs65 kernel: input: PS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input28 Jan 09 20:15:08 henry-gs65 kernel: input: PS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input30 Jan 09 20:15:21 henry-gs65 kernel: psmouse serio1: synaptics: Your touchpad (PNP: SYN150d SYN1500 SYN0002 PNP0f13) says it can support a different bus. If i2c-hid and hid-rmi are not used, you might want to try setting psmouse.synaptics_intertouch to 1 and report this to linux-in...@vger.kernel.org. Jan 09 20:15:21 henry-gs65 kernel: psmouse serio1: synaptics: Touchpad model: 1, fw: 8.16, id: 0x1e2b1, caps: 0xf00123/0x840300/0x12e800/0x40, board id: 3414, fw id: 2667658 Jan 09 20:15:21 henry-gs65 kernel: input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input32 Jan 09 20:30:49 henry-gs65 kernel: input: PS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input34 Jan 06 21:02:58 henry-gs65 kernel: psmouse serio1: synaptics: Your touchpad (PNP: SYN150d SYN1500 SYN0002 PNP0f13) says it can support a different bus. If i2c-hid and hid-rmi are not used, you
[Bug 1811122] [NEW] Cannot use xrdp to login to sesman-Xvnc after 0.6.1-2ubuntu0.1
Public bug reported:
After upgrading xrdp from 0.6.1-2 to 0.6.1-2ubuntu0.1, xrdp would fail
when logging into sesman-Xvnc.
Log:
connecting to sesman ip 127.0.0.1 port 3350
sesman connect ok
sending login info to session manager, please wait...
xrdp_mm_process_login_response: login successful for display
started connecting
connecting to 127.0.0.1 5910
tcp connected
security level is 2 (1 = none, 2 = standard)
password failed
error - problem connecting
I tried deleting the old ~/.vnc, restarting xrdp, killing xvnc
processes, rebooting the server, and manually regenerating
sesman_{user}_passwd using vncpasswd, but still got "error - problem
connecting" at every step. I downgraded xrdp back to 0.6.1-2, and it
worked again. Upgrading back up to 0.6.1-2ubuntu0.1 reproduced the
problem.
I'm on Ubuntu 16.04.5 LTS.
** Affects: xrdp (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/1811122
Title:
Cannot use xrdp to login to sesman-Xvnc after 0.6.1-2ubuntu0.1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xrdp/+bug/1811122/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1806867] [NEW] Increase DVB_MAX_ADAPTERS from 8 to 16 in kernel config
Public bug reported: I installed 12 dvb adapters in my setup and noticed, that the DVB_MAX_ADAPTERS is still limited to 8 instead of 16. This bug has been reported and confirmed in earlier versions of Ubuntu. ProblemType: Bug Description: Ubuntu 18.04.1 LTS Release: 18.04 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: 4.15.0-42-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 :~$ cat lspci-vnvn.log 00:00.0 Host bridge [0600]: Intel Corporation 82G33/G31/P35/P31 Express DRAM Controller [8086:29c0] Subsystem: Red Hat, Inc QEMU Virtual Machine [1af4:1100] Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: [90] Express (v2) Root Port (Slot+), MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0 ExtTag- RBE+ DevCtl: Report errors: Correctable+ Non-Fatal+ Fatal+ Unsupported+ RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend- LnkCap: Port #1, Speed 2.5GT/s, Width x1, ASPM L0s, Exit Latency L0s <64ns, L1 <1us ClockPM- Surprise- LLActRep- BwNot- ASPMOptComp- LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk- ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk- DLActive+ BWMgmt- ABWMgmt- SltCap: AttnBtn+ PwrCtrl+ MRL- AttnInd+ PwrInd+ HotPlug+ Surprise+ Slot #0, PowerLimit 0.000W; Interlock+ NoCompl- SltCtl: Enable: AttnBtn+ PwrFlt- MRL- PresDet- CmdCplt+ HPIrq+ LinkChg- Control: AttnInd Off, PwrInd On, Power- Interlock- SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet+ Interlock- Changed: MRL- PresDet- LinkState- RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna- CRSVisible- RootCap: CRSVisible- RootSta: PME ReqID , PMEStatus- PMEPending- DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, OBFF Not Supported ARIFwd+ DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled ARIFwd- LnkCtl2: Target Link Speed: 2.5GT/s, EnterCompliance- SpeedDis- Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS- Compliance De-emphasis: -6dB LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete-, EqualizationPhase1- EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest- Capabilities: [60] MSI: Enable+ Count=1/2 Maskable+ 64bit- Address: fee0 Data: 4021 Masking: 0002 Pending: Capabilities: [40] Subsystem: Intel Corporation 7500/5520/5500/X58 I/O Hub PCI Express Root Port 0 [8086:] Capabilities: [100 v2] Advanced Error Reporting UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol- CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr- CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+ AERCap: First Error Pointer: 00, GenCap+ CGenEn- ChkCap+ ChkEn- Kernel driver in use: pcieport Kernel modules: shpchp 00:1c.1 PCI bridge [0604]: Intel Corporation 7500/5520/5500/X58 I/O Hub PCI Express Root Port 0 [8086:3420] (rev 02) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: [90] Express (v2) Root Port (Slot+), MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0 ExtTag- RBE+ DevCtl: Report errors: Correctable+ Non-Fatal+ Fatal+ Unsupported+ RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSt
[Bug 1325614] Re: Cannot unlock screen in KDE
I was offsite all day yesterday. I came in today and the lock screen was responsive. Unplugging the monitor seemed to prevent the issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1325614 Title: Cannot unlock screen in KDE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1325614/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1325614] Re: Cannot unlock screen in KDE
I am running Kubuntu 18.04 on a Dell Precision 5810 with a NVIDIA Quadro K4200 graphics card. The driver is NVIDIA 390.77. I have two Dell 27" U2713 monitors with display port cables. If the screen is locked for a long time, i.e. when I leave work for the day, but not during lunch, the keyboard no longer responds. The mouse cursor is still moving but does not seem to interact with the screen. If I use ssh to kill the session with loginctl, everything starts working again. I will try unplugging the second monitor tonight to see if that makes a difference with the issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1325614 Title: Cannot unlock screen in KDE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1325614/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1325614] Re: Cannot unlock screen in KDE
** Also affects: sddm (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/1325614 Title: Cannot unlock screen in KDE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1325614/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1797945] Re: Lightning incompatible with Thunderbird 60.2.1
I found it really hard to find good answers to this problem - It was such a shock, and so important, that I was surprised this site was not no.1 in a Google search. After hours of trying different things and searching, I reverted to 57.2 and locked that in. Then, I accidentally came across https://addons.thunderbird.net/en-us/ which contained the https://ftp.mozilla/pub/calendar/lightning/candidates/ solution - in French. That worked for me. I know it's free software, and I've been using it for years, quite contentedly, but This is not the first time that a Ubuntu Thunderbird update has broken something important. If this is not a bug, what it is? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1797945 Title: Lightning incompatible with Thunderbird 60.2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1797945/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1792644] [NEW] If snapd is not working it can take down systemd
Public bug reported: I'll start out with saying, this bug is probably priority "invalid" due to my non-stock configuration (this 18.04.1 install is on an Acer Chromebook 13, so it has a held back kernel and Xorg for the lovely nvidia drivers it came with.) But I figure I'll file anyway since the problem is rather serious if it arises on your particular system, and the workaround/fix is easy once you figure out what the heck is happening. So, snapd has errored out since I updated to 18.04 due to my held back kernel (snap packages are using xz compression, and this kernel has no xz support...) I found within the last day or so that my machine would not boot to graphical environment, just to text login with no networking up and several missing services (ntp and a few others.) journalctl -xe showed failures due to "file not found" on files like tr, cut, modprobe, cat, that should definitely be found. PATH problems! Ultimately, I found /usr/lib/systemd/system-environment-generators/snapd-env-generator (which appears -- not sure since it's a binary instead of a shell script -- to be intended to just add "/snap/bin" to the PATH.)I moved this out of the folder, on reboot everything worked fine. Then I went ahead and uninstalled snapd. I suspect systemd is "too smart for it's own good", and instead of providing it's own environment variables then letting items in /usr/lib/systemd/system-environment-generators/ modify the environment (as docs say), instead systemd either decided "snapd-env-generator" is setting a PATH so systemd doesn't have to (resulting in PATH of ":/snap/bin") or systemd "rolled back" that PATH when snapd service failed, resetting PATH to empty instead of the default PATH value. ** Affects: systemd (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/1792644 Title: If snapd is not working it can take down systemd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1792644/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1581384] Re: Desktop contents displayed on resume before lock screen is shown
This might be related: https://bugzilla.gnome.org/show_bug.cgi?id=753678 it's still active, it been like this since 2015-2016 ish, and other distributions report the same thing. similar links: https://bugzilla.redhat.com/show_bug.cgi?id=713640 https://bugzilla.redhat.com/show_bug.cgi?id=1391126 https://github.com/linuxmint/Cinnamon/issues/4324 (I use Ubuntu 18.04 (lightdm with gnome), and I encountered the same problem.) ** Bug watch added: GNOME Bug Tracker #753678 https://bugzilla.gnome.org/show_bug.cgi?id=753678 ** Bug watch added: Red Hat Bugzilla #713640 https://bugzilla.redhat.com/show_bug.cgi?id=713640 ** Bug watch added: Red Hat Bugzilla #1391126 https://bugzilla.redhat.com/show_bug.cgi?id=1391126 ** Bug watch added: github.com/linuxmint/Cinnamon/issues #4324 https://github.com/linuxmint/Cinnamon/issues/4324 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1581384 Title: Desktop contents displayed on resume before lock screen is shown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1581384/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1786910] Re: Latest patch breaks command line 'restart all'
To confirm we are seeing this on all our servers which is causing quite a lot of problems for us. Details on how to roll this back would be welcome. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1786910 Title: Latest patch breaks command line 'restart all' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/monit/+bug/1786910/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1780106] [NEW] package grub-efi-amd64-signed 1.93.1+2.02-2ubuntu8.1 failed to install/upgrade: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit stat
Public bug reported: ni idea que paso , trate de montar la actualización y arrojo el error. no preste detalles al error , mas un error que si tengo es que en ocasiones no puedo seleccionar algunos iconos del escritorio con el click del raton, es como si existiera algo super puesto , eso paso desde hace 5 meses mas o menos ProblemType: Package DistroRelease: Ubuntu 18.04 Package: grub-efi-amd64-signed 1.93.1+2.02-2ubuntu8.1 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Wed Jul 4 09:22:01 2018 ErrorMessage: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2017-06-08 (390 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.2 SourcePackage: grub2-signed Title: package grub-efi-amd64-signed 1.93.1+2.02-2ubuntu8.1 failed to install/upgrade: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to bionic on 2018-05-29 (36 days ago) ** Affects: grub2-signed (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic package-from-proposed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1780106 Title: package grub-efi-amd64-signed 1.93.1+2.02-2ubuntu8.1 failed to install/upgrade: installed grub-efi-amd64-signed package post- installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1780106/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1752712] Re: Etherape crashes when trying to run on Xubuntu
Installing libgnomeui-0:amd64 resolved the issue for me. Ubuntu 18.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1752712 Title: Etherape crashes when trying to run on Xubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/etherape/+bug/1752712/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1772270] [NEW] Desktop font error ubuntu16.04
Public bug reported: Having problems with desktop fonts not sticking. its getting worse and worse everyday. keeps changing from time to time. it goes bigger and smaller every 5-mins working on the laptop. Am running Ubuntu 16.04 with Cairo dock ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unity 7.4.5+16.04.20180221-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-124.148-generic 4.4.117 Uname: Linux 4.4.0-124-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun May 20 16:22:44 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GconfCompiz: /apps/compiz-1/general: /apps/compiz-1/general/screen0: /apps/compiz-1/general/screen0/options: active_plugins = [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Mobile 4 Series Chipset Integrated Graphics Controller [1028:0233] Subsystem: Dell Mobile 4 Series Chipset Integrated Graphics Controller [1028:0233] InstallationDate: Installed on 2016-07-02 (687 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Dell Inc. Latitude E6400 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-124-generic root=UUID=443b288d-cccd-4fef-9fd8-90c64adeb94c ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/30/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.name: 0W620R dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd10/30/2009:svnDellInc.:pnLatitudeE6400:pvr:rvnDellInc.:rn0W620R:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude E6400 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sun May 20 10:59:26 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 21316 vendor AUO xserver.version: 2:1.18.4-0ubuntu0.7 ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1772270 Title: Desktop font error ubuntu16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1772270/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
