[Bug 1966203] Re: journal shows "systemd-udevd[2837]: nvme0n1: Process ... failed with exit code 1."
that worked. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966203 Title: journal shows "systemd-udevd[2837]: nvme0n1: Process ... failed with exit code 1." To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1966203/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822937] Re: NVIDIA settings won't write to /etc/xorg
May the fourth(be with you) 2024 STILL EXISTS sudo chmod +x /usr/share/screen-resolution-extra/nvidia-polkit fixes it, but c'mon. it's one line of code(maybe more for you, but it's only one in the terminal) I really can't believe this hasn't been solved by now. Maybe it doesn't seem important enough? too hard? nvidia won't cooperate? dev's being pig headed? I don't think the user base cares about any of that. They just want a system that works as it should. And this issue has been ongoing for YEARS without a fix. I know, I'm not a dev. I have more than enough knowledge and I can read code, so maybe I'm missing something, but 5 years for one line of code is RIDICULOUS Sorry for the tone, but c'mon. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822937 Title: NVIDIA settings won't write to /etc/xorg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1822937/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966203] Re: journal shows "systemd-udevd[2837]: nvme0n1: Process ... failed with exit code 1."
Xubuntu 24.04 May 04 18:28:06 xxx (udev-worker)[494]: nvme0n1: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1' failed with exit code 1. trying sudo mv /lib/udev/rules.d/66-snapd-autoimport.rules /lib/udev/rules.d/OFF.66-snapd-autoimport.rules -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966203 Title: journal shows "systemd-udevd[2837]: nvme0n1: Process ... failed with exit code 1." To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1966203/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1986913] Re: privilege escallation
A disk partitioning and formatting tool, such as GParted, requires root privilege to be able to create new partition tables, format disks and partitions, update the Linux kernel with the changes, etc. By its very nature GParted can completely overwrite everything on a disk device. With this in mind, why is the ability to overwrite a file considered a security concern when GParted could be used to change the entire contents of the disk device? -- 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/1986913 Title: privilege escallation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gparted/+bug/1986913/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960344] Re: Can't mount my encrypted drive with 5.4.0.99-generic
Applied the "apport-collect 1960344" command as requested. Note that this is while using the 5.4.0-94 kernel, because I cannot successfully log in with the 5.4.0-99 kernel. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960344 Title: Can't mount my encrypted drive with 5.4.0.99-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960344/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960344] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1960344/+attachment/5560024/+files/acpidump.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960344 Title: Can't mount my encrypted drive with 5.4.0.99-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960344/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960344] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1960344/+attachment/5560023/+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/1960344 Title: Can't mount my encrypted drive with 5.4.0.99-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960344/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960344] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1960344/+attachment/5560022/+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/1960344 Title: Can't mount my encrypted drive with 5.4.0.99-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960344/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960344] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1960344/+attachment/5560019/+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/1960344 Title: Can't mount my encrypted drive with 5.4.0.99-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960344/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960344] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1960344/+attachment/5560021/+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/1960344 Title: Can't mount my encrypted drive with 5.4.0.99-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960344/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960344] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1960344/+attachment/5560020/+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/1960344 Title: Can't mount my encrypted drive with 5.4.0.99-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960344/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960344] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1960344/+attachment/5560018/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960344 Title: Can't mount my encrypted drive with 5.4.0.99-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960344/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960344] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1960344/+attachment/5560017/+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/1960344 Title: Can't mount my encrypted drive with 5.4.0.99-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960344/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960344] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1960344/+attachment/5560015/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960344 Title: Can't mount my encrypted drive with 5.4.0.99-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960344/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960344] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1960344/+attachment/5560016/+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/1960344 Title: Can't mount my encrypted drive with 5.4.0.99-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960344/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960344] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1960344/+attachment/5560013/+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/1960344 Title: Can't mount my encrypted drive with 5.4.0.99-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960344/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960344] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1960344/+attachment/5560014/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960344 Title: Can't mount my encrypted drive with 5.4.0.99-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960344/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960344] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1960344/+attachment/5560012/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960344 Title: Can't mount my encrypted drive with 5.4.0.99-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960344/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960344] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1960344/+attachment/5560011/+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/1960344 Title: Can't mount my encrypted drive with 5.4.0.99-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960344/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960344] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1960344/+attachment/5560010/+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/1960344 Title: Can't mount my encrypted drive with 5.4.0.99-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960344/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960344] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1960344/+attachment/5560009/+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/1960344 Title: Can't mount my encrypted drive with 5.4.0.99-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960344/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960344] Re: Can't mount my encrypted drive with 5.4.0.99-generic
apport information ** Tags added: apport-collected una ** Description changed: When I boot with kernel 5.4.0-94 my Linux system properly asks me for the passphrase to my encrypted drive (full disk encryption) and then after that successfully gets me to the user login screen. But when I updated my kernel to 5.4.0-99, the booting Linux system does not ask me for my drive encryption passphrase but instead indicates that it is waiting for a drive partition and eventually times out and drops me into a busybox session. The GRUB arguments are identical for both kernels 5.4.0-94 and 5.4.0-99, yet I can only successfully get into my Linux system using the 5.4.0-94 kernel. I don't know whether the following info is useful or not, since it is gathered only from the kernel 5.4.0-94 where I can actually log in. cat /proc/version_signature : Ubuntu 5.4.0-94.106-generic 5.4.157 lspci-vnvn.log is attached. Output of mount command : sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime) proc on /proc type proc (rw,nosuid,nodev,noexec,relatime) udev on /dev type devtmpfs (rw,nosuid,noexec,relatime,size=16365340k,nr_inodes=4091335,mode=755) devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000) tmpfs on /run type tmpfs (rw,nosuid,nodev,noexec,relatime,size=3282420k,mode=755) /dev/mapper/vgmint-root on / type ext4 (rw,relatime,errors=remount-ro,stripe=16) securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime) tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev) tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k) tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755) cgroup2 on /sys/fs/cgroup/unified type cgroup2 (rw,nosuid,nodev,noexec,relatime,nsdelegate) cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,name=systemd) pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime) efivarfs on /sys/firmware/efi/efivars type efivarfs (rw,nosuid,nodev,noexec,relatime) none on /sys/fs/bpf type bpf (rw,nosuid,nodev,noexec,relatime,mode=700) cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory) cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices) cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio) cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer) cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event) cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids) cgroup on /sys/fs/cgroup/rdma type cgroup (rw,nosuid,nodev,noexec,relatime,rdma) cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls,net_prio) cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct) cgroup on /sys/fs/cgroup/hugetlb type cgroup (rw,nosuid,nodev,noexec,relatime,hugetlb) cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset) systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=28,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=29737) hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime,pagesize=2M) mqueue on /dev/mqueue type mqueue (rw,nosuid,nodev,noexec,relatime) debugfs on /sys/kernel/debug type debugfs (rw,nosuid,nodev,noexec,relatime) tracefs on /sys/kernel/tracing type tracefs (rw,nosuid,nodev,noexec,relatime) fusectl on /sys/fs/fuse/connections type fusectl (rw,nosuid,nodev,noexec,relatime) configfs on /sys/kernel/config type configfs (rw,nosuid,nodev,noexec,relatime) /dev/mapper/isw_dbbdgggiei_Volume0p2 on /boot type ext4 (rw,relatime,stripe=16) /dev/mapper/isw_dbbdgggiei_Volume0p1 on /boot/efi type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro) tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=3282416k,mode=700,uid=1000,gid=1000) /home/.ecryptfs/cfast/.Private on /home/cfast type ecryptfs (rw,nosuid,nodev,relatime,ecryptfs_fnek_sig=2e786df13a224d25,ecryptfs_sig=bae1facf9d2afaeb,ecryptfs_cipher=aes,ecryptfs_key_bytes=16,ecryptfs_unlink_sigs) gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id=1000) binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,nosuid,nodev,noexec,relatime) + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.21 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: cfast 1658 F pulseaudio + /dev/snd/controlC0: cfast 1658 F pulseaudio + CasperMD5CheckResult: skip + CurrentDesktop: X-Cinnamon + DistroRelease: Linux Mint 20.3 + EcryptfsInUse: Yes + InstallationDate: Installed on 2021-12-11 (60 days ago) +
[Bug 1960344] [NEW] Can't mount my encrypted drive with 5.4.0.99-generic
Public bug reported: When I boot with kernel 5.4.0-94 my Linux system properly asks me for the passphrase to my encrypted drive (full disk encryption) and then after that successfully gets me to the user login screen. But when I updated my kernel to 5.4.0-99, the booting Linux system does not ask me for my drive encryption passphrase but instead indicates that it is waiting for a drive partition and eventually times out and drops me into a busybox session. The GRUB arguments are identical for both kernels 5.4.0-94 and 5.4.0-99, yet I can only successfully get into my Linux system using the 5.4.0-94 kernel. I don't know whether the following info is useful or not, since it is gathered only from the kernel 5.4.0-94 where I can actually log in. cat /proc/version_signature : Ubuntu 5.4.0-94.106-generic 5.4.157 lspci-vnvn.log is attached. Output of mount command : sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime) proc on /proc type proc (rw,nosuid,nodev,noexec,relatime) udev on /dev type devtmpfs (rw,nosuid,noexec,relatime,size=16365340k,nr_inodes=4091335,mode=755) devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000) tmpfs on /run type tmpfs (rw,nosuid,nodev,noexec,relatime,size=3282420k,mode=755) /dev/mapper/vgmint-root on / type ext4 (rw,relatime,errors=remount-ro,stripe=16) securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime) tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev) tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k) tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755) cgroup2 on /sys/fs/cgroup/unified type cgroup2 (rw,nosuid,nodev,noexec,relatime,nsdelegate) cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,name=systemd) pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime) efivarfs on /sys/firmware/efi/efivars type efivarfs (rw,nosuid,nodev,noexec,relatime) none on /sys/fs/bpf type bpf (rw,nosuid,nodev,noexec,relatime,mode=700) cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory) cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices) cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio) cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer) cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event) cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids) cgroup on /sys/fs/cgroup/rdma type cgroup (rw,nosuid,nodev,noexec,relatime,rdma) cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls,net_prio) cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct) cgroup on /sys/fs/cgroup/hugetlb type cgroup (rw,nosuid,nodev,noexec,relatime,hugetlb) cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset) systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=28,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=29737) hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime,pagesize=2M) mqueue on /dev/mqueue type mqueue (rw,nosuid,nodev,noexec,relatime) debugfs on /sys/kernel/debug type debugfs (rw,nosuid,nodev,noexec,relatime) tracefs on /sys/kernel/tracing type tracefs (rw,nosuid,nodev,noexec,relatime) fusectl on /sys/fs/fuse/connections type fusectl (rw,nosuid,nodev,noexec,relatime) configfs on /sys/kernel/config type configfs (rw,nosuid,nodev,noexec,relatime) /dev/mapper/isw_dbbdgggiei_Volume0p2 on /boot type ext4 (rw,relatime,stripe=16) /dev/mapper/isw_dbbdgggiei_Volume0p1 on /boot/efi type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro) tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=3282416k,mode=700,uid=1000,gid=1000) /home/.ecryptfs/cfast/.Private on /home/cfast type ecryptfs (rw,nosuid,nodev,relatime,ecryptfs_fnek_sig=2e786df13a224d25,ecryptfs_sig=bae1facf9d2afaeb,ecryptfs_cipher=aes,ecryptfs_key_bytes=16,ecryptfs_unlink_sigs) gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id=1000) binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,nosuid,nodev,noexec,relatime) ** Affects: ubuntu Importance: Undecided Status: New ** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/bugs/1960344/+attachment/5559764/+files/lspci-vnvn.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960344 Title: Can't mount my encrypted drive with 5.4.0.99-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1960344/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com
[Bug 1883698] Re: openscenegraph needs to be updated to 3.6.5
I doubt Ubuntu will backport OSG 3.6.5 to Bionic and Focal; but OSG here is busted. ** Changed in: openmw (Ubuntu) Status: New => Confirmed ** Changed in: openscenegraph (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1883698 Title: openscenegraph needs to be updated to 3.6.5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openmw/+bug/1883698/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900388] Re: blk_update_request: I/O error, dev sr0, sector 9180400 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
kernel: blk_update_request: I/O error, dev sr0, sector 661504 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 kernel: Buffer I/O error on dev sr0, logical block 82688, async page read Description:Ubuntu 20.04.3 LTS Release:20.04 Machine: Type: Desktop Mobo: Micro-Star model: MPG B550 GAMING EDGE WIFI (MS-7C91) v: 1.0 serial: UEFI: American Megatrends LLC. v: 1.70 date: 06/29/2021 Drive: /dev/sr0 Vendor : ASUS Model : DRW-24F1ST d Revision: 2.00 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900388 Title: blk_update_request: I/O error, dev sr0, sector 9180400 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1900388/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945845] Re: package linux-firmware 1.187.16 failed to install/upgrade: unable to open '/lib/firmware/qcom/a530_zap.mdt.dpkg-new': Operation not permitted
Similar problem occurred during upgrade to linux-firmware (1.187.20); initial install failed, but was able to successfully install after a reboot. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945845 Title: package linux-firmware 1.187.16 failed to install/upgrade: unable to open '/lib/firmware/qcom/a530_zap.mdt.dpkg-new': Operation not permitted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1945845/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945845] Re: package linux-firmware 1.187.16 failed to install/upgrade: unable to open '/lib/firmware/qcom/a530_zap.mdt.dpkg-new': Operation not permitted
Appears to have installed successfully after a reboot. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945845 Title: package linux-firmware 1.187.16 failed to install/upgrade: unable to open '/lib/firmware/qcom/a530_zap.mdt.dpkg-new': Operation not permitted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1945845/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945845] [NEW] package linux-firmware 1.187.16 failed to install/upgrade: unable to open '/lib/firmware/qcom/a530_zap.mdt.dpkg-new': Operation not permitted
Public bug reported: Description:Ubuntu 20.04.3 LTS Release:20.04 linux-firmware: Installed: 1.187.16 Candidate: 1.187.17 Version table: 1.187.17 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main i386 Packages *** 1.187.16 100 100 /var/lib/dpkg/status 1.187 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu focal/main i386 Packages Installation failed during system update. Unpacking libgl1-mesa-dev:amd64 (21.0.3-0ubuntu0.3~20.04.2) over (21.0.3-0ubuntu 0.3~20.04.1) ... Errors were encountered while processing: /tmp/apt-dpkg-install-hJ8TxR/47-linux-firmware_1.187.17_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.16 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gdm2654 F pulseaudio curts 3716 F pulseaudio /dev/snd/controlC0: gdm2654 F pulseaudio curts 3716 F pulseaudio CasperMD5CheckResult: skip Date: Fri Oct 1 19:32:59 2021 Dependencies: ErrorMessage: unable to open '/lib/firmware/qcom/a530_zap.mdt.dpkg-new': Operation not permitted InstallationDate: Installed on 2021-02-21 (222 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) IwConfig: lono wireless extensions. enp42s0 no wireless extensions. tun0 no wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7C91 PackageArchitecture: all ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz root=UUID=7A200ADA-3790-4EBA-8897-FF422F2FB377 quiet splash rootflags=subvol=@ PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu26.13 RfKill: SourcePackage: linux-firmware Title: package linux-firmware 1.187.16 failed to install/upgrade: unable to open '/lib/firmware/qcom/a530_zap.mdt.dpkg-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/14/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 1.50 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MPG B550 GAMING EDGE WIFI (MS-7C91) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.50:bd01/14/2021:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C91:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMPGB550GAMINGEDGEWIFI(MS-7C91):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C91 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. ** Affects: linux-firmware (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/1945845 Title: package linux-firmware 1.187.16 failed to install/upgrade: unable to open '/lib/firmware/qcom/a530_zap.mdt.dpkg-new': Operation not permitted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1945845/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943092] Re: package linux-headers-5.11.0-34-generic (not installed) failed to install/upgrade: unable to open '/usr/src/linux-headers-5.11.0-34-generic/scripts/mod/empty.dwo.dpkg-new': Operation
$ sudo apt --fix-broken install Reading package lists... Done Building dependency tree Reading state information... Done Correcting dependencies... Done The following additional packages will be installed: linux-headers-5.11.0-34-generic linux-hwe-5.11-headers-5.11.0-34 The following NEW packages will be installed: linux-headers-5.11.0-34-generic The following packages will be upgraded: linux-hwe-5.11-headers-5.11.0-34 1 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. 57 not fully installed or removed. Need to get 0 B/13.1 MB of archives. After this operation, 90.4 MB of additional disk space will be used. Do you want to continue? [Y/n] y Setting up libgcrypt20:amd64 (1.8.5-5ubuntu1.1) ... Setting up libsystemd0:amd64 (245.4-4ubuntu3.13) ... Setting up libgcrypt20:i386 (1.8.5-5ubuntu1.1) ... Setting up systemd-timesyncd (245.4-4ubuntu3.13) ... Setting up systemd (245.4-4ubuntu3.13) ... Installing new version of config file /etc/dhcp/dhclient-enter-hooks.d/resolved ... (Reading database ... 263621 files and directories currently installed.) Preparing to unpack .../linux-hwe-5.11-headers-5.11.0-34_5.11.0-34.36~20.04.1_al l.deb ... Unpacking linux-hwe-5.11-headers-5.11.0-34 (5.11.0-34.36~20.04.1) over (5.11.0-3 4.36~20.04.1) ... Preparing to unpack .../linux-headers-5.11.0-34-generic_5.11.0-34.36~20.04.1_amd 64.deb ... Unpacking linux-headers-5.11.0-34-generic (5.11.0-34.36~20.04.1) ... dpkg: error processing archive /var/cache/apt/archives/linux-headers-5.11.0-34-g eneric_5.11.0-34.36~20.04.1_amd64.deb (--unpack): unable to open '/usr/src/linux-headers-5.11.0-34-generic/scripts/mod/empty.dwo. dpkg-new': Operation not permitted Errors were encountered while processing: /var/cache/apt/archives/linux-headers-5.11.0-34-generic_5.11.0-34.36~20.04.1_am d64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943092 Title: package linux-headers-5.11.0-34-generic (not installed) failed to install/upgrade: unable to open '/usr/src/linux- headers-5.11.0-34-generic/scripts/mod/empty.dwo.dpkg-new': Operation not permitted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1943092/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943092] Re: package linux-headers-5.11.0-34-generic (not installed) failed to install/upgrade: unable to open '/usr/src/linux-headers-5.11.0-34-generic/scripts/mod/empty.dwo.dpkg-new': Operation
This is with the NVIDIA 460 driver. At present, I can't successfully switch to the 470 driver, because it tries to use the 5.11.0-34.36 kernel files as part of the install. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943092 Title: package linux-headers-5.11.0-34-generic (not installed) failed to install/upgrade: unable to open '/usr/src/linux- headers-5.11.0-34-generic/scripts/mod/empty.dwo.dpkg-new': Operation not permitted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1943092/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943092] [NEW] package linux-headers-5.11.0-34-generic (not installed) failed to install/upgrade: unable to open '/usr/src/linux-headers-5.11.0-34-generic/scripts/mod/empty.dwo.dpkg-new': Operati
Public bug reported: Description:Ubuntu 20.04.3 LTS Release:20.04 \linux-headers-5.11.0-34-generic: Installed: (none) Candidate: 5.11.0-34.36~20.04.1 Version table: 5.11.0-34.36~20.04.1 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages Install failed during latest kernel update. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-headers-5.11.0-34-generic (not installed) ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Sep 8 20:26:11 2021 DuplicateSignature: package:linux-headers-5.11.0-34-generic:(not installed) Unpacking linux-hwe-5.11-headers-5.11.0-34 (5.11.0-34.36~20.04.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-26WFDo/10-linux-hwe-5.11-headers-5.11.0-34_5.11.0-34.36~20.04.1_all.deb (--unpack): unable to create new file '/var/lib/dpkg/info/linux-hwe-5.11-headers-5.11.0-34.list-new': Operation not permitted ErrorMessage: unable to open '/usr/src/linux-headers-5.11.0-34-generic/scripts/mod/empty.dwo.dpkg-new': Operation not permitted InstallationDate: Installed on 2021-02-21 (199 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: linux-hwe-5.11 Title: package linux-headers-5.11.0-34-generic (not installed) failed to install/upgrade: unable to open '/usr/src/linux-headers-5.11.0-34-generic/scripts/mod/empty.dwo.dpkg-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-hwe-5.11 (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/1943092 Title: package linux-headers-5.11.0-34-generic (not installed) failed to install/upgrade: unable to open '/usr/src/linux- headers-5.11.0-34-generic/scripts/mod/empty.dwo.dpkg-new': Operation not permitted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1943092/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934538] [NEW] Package linux-modules-nvidia-460-5.8.0-59-generic not included in kernel 5.8.0-59-generic upgrade
Public bug reported: Description:Ubuntu 20.04.2 LTS Release:20.04 linux-modules-nvidia-460-5.8.0-59-generic: Installed: 5.8.0-59.66~20.04.1 Candidate: 5.8.0-59.66~20.04.1 Version table: *** 5.8.0-59.66~20.04.1 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/restricted amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/restricted amd64 Packages 100 /var/lib/dpkg/status During the upgrade to the 5.8.0-59-generic kernel in Ubuntu 20.04, apt showed an upgrade to the NVIDIA 460 driver as withheld. Proceeding with the 5.8.0-59-generic upgrade breaks the installed NVIDIA 460 driver and causes the Nouveau driver to load after reboot. Manually installing package linux-modules-nvidia-460-5.8.0-59-generic allows the updated NVIDIA 460.80 driver to complete installation and makes the Ubuntu 20.04 installation whole and completely up-to-date again after a subsequent reboot. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-modules-nvidia-460-5.8.0-59-generic 5.8.0-59.66~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-59-generic x86_64 NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice talpa_vcdevice talpa_core talpa_linux talpa_syscallhook nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 2 15:04:08 2021 InstallationDate: Installed on 2021-02-21 (131 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-restricted-modules-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-restricted-modules-hwe-5.8 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934538 Title: Package linux-modules-nvidia-460-5.8.0-59-generic not included in kernel 5.8.0-59-generic upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-hwe-5.8/+bug/1934538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928355] Re: linux 5.11.0-17 kernel fails to auto load amdgpu module
The same thing happens to me with 5.11.0-18, I have to use 5.11.0-16 for now. I also have a AMD Radeon RX 6700 XT -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928355 Title: linux 5.11.0-17 kernel fails to auto load amdgpu module To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928355/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922757] Re: Ubuntu 21.04 Laptop Installation
I re-completed the process and the crash occurred when completing the grub-setup to sda hard drive. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922757 Title: Ubuntu 21.04 Laptop Installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1922757/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922757] [NEW] Ubuntu 21.04 Laptop Installation
Public bug reported: installation crash after downloading/applying updates ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.13 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.461 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 6 11:47:08 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210405) ProcEnviron: LANGUAGE=en_US.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 LC_NUMERIC=C.UTF-8 RebootRequiredPkgs: linux-image-5.11.0-13-generic linux-base SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute ubiquity-21.04.13 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922757 Title: Ubuntu 21.04 Laptop Installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1922757/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912970] Re: Fix for GRUB_FLAVOUR_ORDER in grub-mkconfig_lib
Well, it would do exactly what I need if I can convince the XanMod developers to adjust their naming scheme. I do not build the new kernels myself (https://xanmod.org/#install_via_apturl). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912970 Title: Fix for GRUB_FLAVOUR_ORDER in grub-mkconfig_lib To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1912970/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912970] Re: Fix for GRUB_FLAVOUR_ORDER in grub-mkconfig_lib
Thank you for the feedback. I will notify the XanMod Developers Forum. I am just a humble user trying to get the Grub2 menu on my system to update properly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912970 Title: Fix for GRUB_FLAVOUR_ORDER in grub-mkconfig_lib To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1912970/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912970] Re: Fix for GRUB_FLAVOUR_ORDER in grub-mkconfig_lib
** Patch added: "grub-mkconfig_lib.patch" https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1912970/+attachment/5456433/+files/grub-mkconfig_lib.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912970 Title: Fix for GRUB_FLAVOUR_ORDER in grub-mkconfig_lib To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1912970/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912970] [NEW] Fix for GRUB_FLAVOUR_ORDER in grub-mkconfig_lib
Public bug reported: Description:Ubuntu 20.04.1 LTS Release:20.04 I am submitting a patch for /usr/share/grub/grub-mkconfig_lib to fix the usage of GRUB_FLAVOUR_ORDER in method version_test_gt(). I have installed the XanMod-LTS kernel in my Ubuntu 20.04 installation. The Ubuntu 20.04 kernel is currently 5.8.0-38-generic and the current xanmod1 kernel is 5.4.91-xanmod1. The sort routine in /usr/share/grub/grub-mkconfig_lib will sort the Ubuntu kernel ahead of the xanmod1 kernel due to the higher version number when assigning the default Ubuntu menu entry at the beginning of the grub2 menu. If /etc/default/grub is updated to include the following entry, it should change the sort order: # Set xanmod1 as the preferred flavour for the default Ubuntu menu entry GRUB_FLAVOUR_ORDER="xanmod1 generic" Unfortunately, there is a trivial bug in method version_test_gt() in /usr/share/grub/grub-mkconfig_lib that prevents this from working. I have attached a patch that corrects it. Once the bug is fixed, the desired sort order is achieved and the 5.4.91-xanmod1 kernel is made the default Ubuntu menu entry. $ sudo update-grub Sourcing file `/etc/default/grub' Sourcing file `/etc/default/grub.d/init-select.cfg' Generating grub configuration file ... using custom appearance settings Found background image: /usr/share/images/grub/Movie_TRON-Legacy_131740_1600x1200.tga Found linux image: /boot/vmlinuz-5.4.91-xanmod1 Found initrd image: /boot/initrd.img-5.4.91-xanmod1 Found linux image: /boot/vmlinuz-5.4.89-xanmod1 Found initrd image: /boot/initrd.img-5.4.89-xanmod1 Found linux image: /boot/vmlinuz-5.8.0-38-generic Found initrd image: /boot/initrd.img-5.8.0-38-generic Found linux image: /boot/vmlinuz-5.8.0-36-generic Found initrd image: /boot/initrd.img-5.8.0-36-generic ** Affects: grub2 (Ubuntu) Importance: Undecided Status: New ** Tags: grub2 ** Package changed: gvfs (Ubuntu) => grub2 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912970 Title: Fix for GRUB_FLAVOUR_ORDER in grub-mkconfig_lib To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1912970/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1879183] Re: Cheese does not show preferences/options/menus to non-GNOME Users
Bullshit it does > On Oct 7, 2020, at 04:20, Paul White <1879...@bugs.launchpad.net> wrote: > > Further to comment #18 I updated cheese to version 3.34.0-1ubuntu1 and > logged into both a GNOME session and an Ubuntu session. In both sessions > the menu in the title bar is visible and usable. > > ** Tags removed: verification-needed > ** Tags added: verification-done > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1884461). > https://bugs.launchpad.net/bugs/1879183 > > Title: > Cheese does not show preferences/options/menus to non-GNOME Users > > Status in cheese package in Ubuntu: > Fix Released > Status in cheese source package in Focal: > Fix Committed > Status in cheese package in Debian: > New > > Bug description: > [Impact] > Cheese no longer displays its menu button on non-GNOME desktop environments. > https://gitlab.gnome.org/GNOME/cheese/-/issues/62 > > Xubuntu uses cheese as its default camera program. Advanced users can > still change these settings through dconf-editor, but this is neither > convenient nor intuitive. > > [Test Case] > > Use the cheese program in Xubuntu/xfce, Kubuntu/KDE or other non-GNOME > desktop environments. Notice missing menu in titlebar. > > [Regression Potential] > > The most likely regression would be if the patch disabled the menu in > GNOME. Testing has not shown this to be an issue. > > > [ORIGINAL REPORT] > Cheese has removed the GUI method of accessing preferences for non-GNOME > users. > > https://github.com/GNOME/cheese/commit/48882da6a6dc4fc1c19e15f5210c9e10feb67ff5#diff-b2b45275b16940829b5f6f068943108d > > I'm not sure if upstream cheese devs care enough to fix it: > https://gitlab.gnome.org/GNOME/cheese/-/issues/62 > https://gitlab.gnome.org/GNOME/cheese/-/issues/52 > > Should Xubuntu default to a different camera program, such as > guvcview? > > (Partial?) WORKAROUND is to use dconf-editor: > dconf-editor /org/gnome/cheese > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1879183/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879183 Title: Cheese does not show preferences/options/menus to non-GNOME Users To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1879183/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879183] Re: Cheese does not show preferences/options/menus to non-GNOME Users
Ha, I know right? That would fit the pattern of decreased functionality if the fix was just to disable the menu in Gnome too! saboteur style : ) Maybe they'll allow burning of blue ray data disks someday too? umm er... sorry. > On Oct 6, 2020, at 19:35, Brian Murray <1879...@bugs.launchpad.net> wrote: > > I'd like to see this tested in an Ubuntu Gnome session to confirm that > it does not regress there. > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1884461). > https://bugs.launchpad.net/bugs/1879183 > > Title: > Cheese does not show preferences/options/menus to non-GNOME Users > > Status in cheese package in Ubuntu: > Fix Released > Status in cheese source package in Focal: > Fix Committed > Status in cheese package in Debian: > New > > Bug description: > [Impact] > Cheese no longer displays its menu button on non-GNOME desktop environments. > https://gitlab.gnome.org/GNOME/cheese/-/issues/62 > > Xubuntu uses cheese as its default camera program. Advanced users can > still change these settings through dconf-editor, but this is neither > convenient nor intuitive. > > [Test Case] > > Use the cheese program in Xubuntu/xfce, Kubuntu/KDE or other non-GNOME > desktop environments. Notice missing menu in titlebar. > > [Regression Potential] > > The most likely regression would be if the patch disabled the menu in > GNOME. Testing has not shown this to be an issue. > > > [ORIGINAL REPORT] > Cheese has removed the GUI method of accessing preferences for non-GNOME > users. > > https://github.com/GNOME/cheese/commit/48882da6a6dc4fc1c19e15f5210c9e10feb67ff5#diff-b2b45275b16940829b5f6f068943108d > > I'm not sure if upstream cheese devs care enough to fix it: > https://gitlab.gnome.org/GNOME/cheese/-/issues/62 > https://gitlab.gnome.org/GNOME/cheese/-/issues/52 > > Should Xubuntu default to a different camera program, such as > guvcview? > > (Partial?) WORKAROUND is to use dconf-editor: > dconf-editor /org/gnome/cheese > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1879183/+subscriptions ** Bug watch added: gitlab.gnome.org/GNOME/cheese/-/issues #52 https://gitlab.gnome.org/GNOME/cheese/-/issues/52 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879183 Title: Cheese does not show preferences/options/menus to non-GNOME Users To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1879183/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871268] Re: Installation fails when "Install Third-Party Drivers" is selected
Well, I see the 20.04.1 live image still has a problem installing (NVIDIA?) drivers during the initial install that was in the original 20.04 release. I shall try again without the drivers install option. I was trying a minimal clean install this time if that makes any difference for the analysis. -- 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 when "Install Third-Party Drivers" is selected To manage notifications about this bug go to: https://bugs.launchpad.net/glibc/+bug/1871268/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881214] Re: Intel Wireless 8260 [8086:24f3] Subsystem [8086:1010] on channel switch, iwlwifi Microcode SW Error: FW error in SYNC CMD CHANNEL_SWITCH_TIME_EVENT_CMD
This bug is not present with other distro's I use, that is Arch. This indicates that it can be distribution centric. Ubuntu has the bug, Arch does not. A workaround is if your system has this Intel device use another distro. It is not convenient but it works. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881214 Title: Intel Wireless 8260 [8086:24f3] Subsystem [8086:1010] on channel switch, iwlwifi Microcode SW Error: FW error in SYNC CMD CHANNEL_SWITCH_TIME_EVENT_CMD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881214/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1883693] Re: openmw randomly crashes
Redirecting to openscenegraph; openmw works fine with OSG 3.6.5; OSG 3.6.4 is broken and causes applications linked against it to crash. ** Package changed: openmw (Ubuntu) => openscenegraph (Ubuntu) ** Also affects: openscenegraph via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945875 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1883693 Title: openmw randomly crashes To manage notifications about this bug go to: https://bugs.launchpad.net/openscenegraph/+bug/1883693/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1883693] Re: openmw randomly crashes
As reported https://gitlab.com/OpenMW/openmw/-/issues/5205 and also in Debian https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945875 OSG 3.6.4 is broken (by broken, it crashes applications that links to it) and should not have been pulled downstream, compounded by the fact that it replaced working OSG 3.4. The OpenMW team worked hard to trace the problems down and sent patches upstream to openscenegraph which made a 3.6.5 release which does not crash. There are still additional patches in for OSG 3.6.6 but that has not yet be releases but those are more quality-of-life patches. I do not know if it is still possible to get OSG 3.6.5 into 20.04 proper; could it at least be put into bionic-backports? Cheers, Bret Curtis (OpenMW Lead and Debian Package Maintainer) ** Bug watch added: gitlab.com/OpenMW/openmw/-/issues #5205 https://gitlab.com/OpenMW/openmw/-/issues/5205 ** Bug watch added: Debian Bug tracker #945875 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945875 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1883693 Title: openmw randomly crashes To manage notifications about this bug go to: https://bugs.launchpad.net/openscenegraph/+bug/1883693/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1883693] Re: openmw randomly crashes
** Changed in: openmw (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1883693 Title: openmw randomly crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openmw/+bug/1883693/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1738736] Re: ACPI error message flooding syslog
Has there been any progress on this. I still have the same problem on both kernel 4.15 and 5.4. I still have to modify logrotate to limit logging or more recently I have tried stopping the logging of any errors which was not as simple as I expected as rsyslog uses socket activation under systemd. So whenever there is a log message coming in, rsyslog will be started on demand. The unit is named syslog.socket. So to stop the rsyslog service one needs to stop both units: systemctl stop syslog.socket rsyslog.service or completely to disable logging from the next boot by: systemctl disable syslog.socket rsyslog.service None of these are satisfactory long term solutions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1738736 Title: ACPI error message flooding syslog To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1738736/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882408] [NEW] package python3-netifaces-dbg (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/python3/dist-packages/netifaces.cpython-38d-x86_64-linux-gnu.so', which is al
Public bug reported: trying out net interfaces programming on 20.04 and programming in general. package 0.10.4-1ubuntu4 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: python3-netifaces-dbg (not installed) ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Jun 6 20:18:14 2020 DuplicateSignature: package:python3-netifaces-dbg:(not installed) Unpacking cpp-9-x86-64-linux-gnu:i386 (9.3.0-10ubuntu1cross2) ... dpkg: error processing archive /tmp/apt-dpkg-install-fnnzsz/1285-cpp-9-x86-64-linux-gnu_9.3.0-10ubuntu1cross2_i386.deb (--unpack): trying to overwrite '/usr/bin/x86_64-linux-gnu-cpp-9', which is also in package cpp-9 9.3.0-10ubuntu2 ErrorMessage: trying to overwrite '/usr/lib/python3/dist-packages/netifaces.cpython-38d-x86_64-linux-gnu.so', which is also in package python3-netifaces 0.10.4-1ubuntu4 InstallationDate: Installed on 2020-06-06 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: netifaces Title: package python3-netifaces-dbg (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/python3/dist-packages/netifaces.cpython-38d-x86_64-linux-gnu.so', which is also in package python3-netifaces 0.10.4-1ubuntu4 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: netifaces (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal package-conflict -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882408 Title: package python3-netifaces-dbg (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/python3/dist- packages/netifaces.cpython-38d-x86_64-linux-gnu.so', which is also in package python3-netifaces 0.10.4-1ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netifaces/+bug/1882408/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881214] Re: syslog and kern.log grow endlessly - related to channel switch, Intel wifi?
syslog and kern.log grew until the filesystem was full. This happened twice. It can be replicated. My workaround is to regress to 19.10. I have a system on 20.04 that does not use wireless and there is no error. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881214 Title: syslog and kern.log grow endlessly - related to channel switch, Intel wifi? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881214/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827967] Re: There are 4 HDMI/Displayport audio output listed in sound setting without attach any HDMI/DP monitor
** Changed in: linux (Ubuntu) Assignee: Hui Wang (hui.wang) => tony curtis (tonyc433) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827967 Title: There are 4 HDMI/Displayport audio output listed in sound setting without attach any HDMI/DP monitor To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1827967/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877894] Re: "True Wireless" Bluetooth headsets not connecting in Ubuntu 20.04
Here is the output from `journalctl -b 0`: $ journalctl -b 0 -- Logs begin at Sun 2020-05-03 06:17:09 EDT, end at Fri 20> May 14 12:11:14 user-linux kernel: microcode: microcode u> May 14 12:11:14 user-linux kernel: Linux version 5.4.0-29> May 14 12:11:14 user-linux kernel: Command line: BOOT_IMA> May 14 12:11:14 user-linux kernel: KERNEL supported cpus: May 14 12:11:14 user-linux kernel: Intel GenuineIntel May 14 12:11:14 user-linux kernel: AMD AuthenticAMD May 14 12:11:14 user-linux kernel: Hygon HygonGenuine May 14 12:11:14 user-linux kernel: Centaur CentaurHauls May 14 12:11:14 user-linux kernel: zhaoxin Shanghai May 14 12:11:14 user-linux kernel: x86/fpu: Supporting XS> May 14 12:11:14 user-linux kernel: x86/fpu: Supporting XS> May 14 12:11:14 user-linux kernel: x86/fpu: Supporting XS -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877894 Title: "True Wireless" Bluetooth headsets not connecting in Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877894/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877894] [NEW] "True Wireless" Bluetooth headsets not connecting in Ubuntu 20.04
Public bug reported: I upgraded my Ubuntu installation from 19.10 to 20.04 and I have lost the ability to connect to any kind of Bluetooth "True Wireless" earphones (Apple AirPods, Galaxy Earpods+, etc). Standard Bluetooth headphones connect correctly but all "True Wireless" style headphones briefly connect then disconnect immediately. bluetoothctl output: ``` [bluetooth]# devices Device C0:28:8D:1D:42:90 Jaybird X3 Device 7C:38:AD:4A:C8:F9 Galaxy Buds (C8F9) Device 40:26:19:DC:12:E6 Apple AirPods [bluetooth]# connect C0:28:8D:1D:42:90 Attempting to connect to C0:28:8D:1D:42:90 [CHG] Device C0:28:8D:1D:42:90 Connected: yes Connection successful [Jaybird X3]# connect 7C:38:AD:4A:C8:F9 ttempting to connect to 7C:38:AD:4A:C8:F9 [CHG] Device 7C:38:AD:4A:C8:F9 Connected: yes Failed to connect: org.bluez.Error.Failed Jaybird X3]# connect 40:26:19:DC:12:E6 Attempting to connect to 40:26:19:DC:12:E6 [CHG] Device 40:26:19:DC:12:E6 Connected: yes Failed to connect: org.bluez.Error.Failed [CHG] Device 40:26:19:DC:12:E6 Connected: no [CHG] Device 40:26:19:DC:12:E6 Connected: yes [CHG] Device 40:26:19:DC:12:E6 Connected: no [Jaybird X3]# ``` ``` $ lsb_release -rd Description:Ubuntu 20.04 LTS Release:20.04 ``` possible packages involved: -pulseaudio -pulseaudio-module-bluetooth -bluez ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: curtis 8167 F pulseaudio /dev/snd/controlC2: curtis 8167 F pulseaudio /dev/snd/pcmC2D0c: curtis 8167 F...m pulseaudio /dev/snd/controlC0: curtis 8167 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun May 10 15:52:42 2020 InstallationDate: Installed on 2019-05-24 (352 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh SourcePackage: alsa-driver Symptom: audio Title: Bluetooth sound card not detected UpgradeStatus: Upgraded to focal on 2020-05-04 (5 days ago) dmi.bios.date: 06/20/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1204 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97-AR dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1204:bd06/20/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-AR:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS ** Affects: ubuntu Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877894 Title: "True Wireless" Bluetooth headsets not connecting in Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1877894/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1762163] Re: [Kubuntu 18.04]Device notifier pretends it cannot mount usb device while actually mounting it
Thanks Claudio for confirming that my PPA with the upstream Solid patch fixes the issue. Thanks also YAFU for creating this bug report. I just noticed that you had also included a link to the upstream patch to the Solid package. When I tried to track down the cause there were many related bug reports, such as those listed in post #7. This made it difficult to discover what the cause and fix might be. It would be great if this upstream fix could be applied to the official Kubuntu repositories. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to solid in Ubuntu. https://bugs.launchpad.net/bugs/1762163 Title: [Kubuntu 18.04]Device notifier pretends it cannot mount usb device while actually mounting it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/solid/+bug/1762163/+subscriptions -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1762163] Re: [Kubuntu 18.04]Device notifier pretends it cannot mount usb device while actually mounting it
Thank you Claudio Lanconelli for your post #6 which indicated where a patch could be found. I created a PPA that has that upstream fix applied to the current Kubuntu 18.04 solid package. See: https://launchpad.net/~gedakc/+archive/ubuntu/solid-1804-ppa In my testing the updated packages in my PPA did indeed fix the problem as described in this bug report. Please feel free to try my PPA and let me know if it works for you. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1762163 Title: [Kubuntu 18.04]Device notifier pretends it cannot mount usb device while actually mounting it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/solid/+bug/1762163/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1762163] Re: [Kubuntu 18.04]Device notifier pretends it cannot mount usb device while actually mounting it
This issue with mounting and displaying "Malformed URL" is still a problem with Kubuntu 18.04.4 LTS Bionic Beaver with all updates applied as of today (Feb 17, 2020). There is a confusing history of bug reports and patches for this issue, as follows: USB Drives Give Malformed URL From Device Notifier https://www.kubuntuforums.net/showthread.php/73500-USB-Drives-Give-Malformed-URL-From-Device-Notifier Plugging in usb drive gives malformed url from device notifer https://bugs.kde.org/show_bug.cgi?id=391381 device notifier pretends it cannot mount usb device while actually mounting it https://bugs.kde.org/show_bug.cgi?id=370975 Backport fix for 391706 into Frameworks 5.44 https://phabricator.kde.org/T9525 Backport automount fix into Bionic https://bugs.launchpad.net/ubuntu/+source/solid/+bug/1762433 Backport fix for KDE bug 391706 into Frameworks 5.44 https://bugs.launchpad.net/ubuntu/+source/solid/+bug/1789292 It would be helpful to myself and other kubuntu 18.04 users if the issue could be fixed soon. ** Bug watch added: KDE Bug Tracking System #391381 https://bugs.kde.org/show_bug.cgi?id=391381 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1762163 Title: [Kubuntu 18.04]Device notifier pretends it cannot mount usb device while actually mounting it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/solid/+bug/1762163/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1550444] Re: Parole media player segfaults when seeking forward in a video file
Hello.
Because 'Parole' is a part of an Universe section, it will be - probably
- not updated by Developers in Xenial/16.04 (please see rules about
updating packages, because I can be wrong). Of course, your method
Fixitman Arizona is okay.
By the way: please notice Gimp situation [1]: there are multiple
security issues fixed in various Gimp versions and Releases - even in
14.04/Trusty, which is older than Xenial, right? Never mind. I have no
idea why there is no security update for Gimp in Xenial.
Anyway, I solved problem with segfaults described by mikewhatever - an
original poster by using AppArmor. Because in the past I've created a
profile for Gimp, I decided to check what will happen when `mpris2.so`
library will be blocked. And it worked!
,[ AppArmor rule ]
| deny /usr/lib/@{multiarch}/parole-0/parole-mpris2.so mr,
`
With above rule in use, I can play any supported file/video and as
Original Poster wrote: "click or drag the slider to seek forward (...)"
and so on.
Thanks, best regards.
_
[1] https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1773561
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1550444
Title:
Parole media player segfaults when seeking forward in a video file
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/parole/+bug/1550444/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1585434] Re: ecryptfs_decrypt_page: Error attempting to read lower page; rc = [-4]
Hello. Today, I've noticed two entries about 'ecryptfs_decrypt_page' and 'ecryptfs_readpage' errors in `/var/log/syslog` file. I have no idea if there was/is more such entries. However, it looks this way: ,[ ✖ Error ] | kernel: [25312.360714] ecryptfs_decrypt_page: Error attempting to read lower page; rc = [-4] | kernel: [25312.360724] ecryptfs_readpage: Error decrypting page; rc = [-4] ` There was not any system slowdowns, freezing etc. Anyway, `/home` partition was encrypted during installation with eCryptfs (vide `/home/.ecryptfs/t4/.Private`). Here are some technical informations about system: ,[ ✖ lsb_release ] | Distributor ID: Ubuntu | Description: Ubuntu 16.04.6 LTS | Release: 16.04 | Codename: xenial | --- | Linux:4.4.0-173-generic | Architecture: i686/x86_32 ` It seems, that I'm not only one Xenial user who's seeing these errors (I mean another comments, for example #16 by Stefan Wagner etc). Thanks, best regards. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1585434 Title: ecryptfs_decrypt_page: Error attempting to read lower page; rc = [-4] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1585434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1775443] Re: Ubuntu 18.04 Bluetooth Crash
Thanks for following up. I had forgotten about this bug as I haven't had trouble with this in probably 6 months or more. Other than installing software updates, I didn't do anything to fix it. But it seems to be resolved for me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1775443 Title: Ubuntu 18.04 Bluetooth Crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775443/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847862] [NEW] gdebi UnicodeDecodeError: 'utf-8' codec can't decode byte 0x92 in position 504: invalid start byte
Public bug reported: Tried to use gdebi to install dependencies for daemonsync_2.2.0.0059_amd64.deb sync server (https://www.daemon- tools.cc/products/daemonsync) on Ubuntu 18.04.3 LTS (4.15.0-65-generic). Gdebi execution failed while building the dependency tree. sudo gdebi daemonsync_2.2.0.0059_amd64.deb Reading package lists... Done Building dependency tree Reading state information... Done Reading state information... Done Traceback (most recent call last): File "/usr/bin/gdebi", line 103, in debi.show_description() File "/usr/share/gdebi/GDebi/GDebiCli.py", line 96, in show_description print(self._deb["Description"]) File "/usr/share/gdebi/GDebi/DebPackage.py", line 39, in __getitem__ return self._sections[item] UnicodeDecodeError: 'utf-8' codec can't decode byte 0x92 in position 504: invalid start byte ** Affects: gdebi (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/1847862 Title: gdebi UnicodeDecodeError: 'utf-8' codec can't decode byte 0x92 in position 504: invalid start byte To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1847862/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838090] Re: Ubuntu 16.04: read access incorrectly implies 'm' rule
*** This bug is a duplicate of bug 1658219 ***
https://bugs.launchpad.net/bugs/1658219
Hello.
I would like to note, that when Linux kernel has been updated to
4.4.0-160.188 version[1] (with, among others, patches for LP:#1658219
and LP:#1838090), I've had to update a few profiles (such as Audacious,
Parole, Xorg, Logrotate etc.), because of a lot of "DENIED" entries in
system log files. If it's about access controls (vide
'requested{denied}_mask'): most new rules required 'm' (memory map as
executable), but some of them needed 'k' (file locking) etc.)
However, it seems everything is okay now and I hope, that there will be
no such issues anymore. Anyway, Mr Tyler Hicks was right: "users with
custom policy have some reasonable expectation that upgrading to the new
Ubuntu release or kernel version will require them to update their
custom policy".
By the way; what is an impact of these changes? (I mean LP:#1658219 and
LP:#1838090). Does it means, that now, use of 'm' and 'k' access is
secured/restricted/checked correctly by AppArmor? And one more thing:
this problem is related to v4.4 kernel only, right?
Thanks, best regards.
__
[1] https://launchpad.net/ubuntu/+source/linux/4.4.0-160.188
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1838090
Title:
Ubuntu 16.04: read access incorrectly implies 'm' rule
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1838090/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1658219] Re: flock not mediated by 'k'
Hello.
I would like to note, that when Linux kernel has been updated to
4.4.0-160.188 version[1] (with, among others, patches for LP:#1658219
and LP:#1838090), I've had to update a few profiles (such as Audacious,
Parole, Xorg, Logrotate etc.), because of a lot of "DENIED" entries in
system log files. If it's about access controls (vide
'requested{denied}_mask'): most new rules required 'm' (memory map as
executable), but some of them needed 'k' (file locking) etc.)
However, it seems everything is okay now and I hope, that there will be
no such issues anymore. Anyway, Mr Tyler Hicks was right: "users with
custom policy have some reasonable expectation that upgrading to the new
Ubuntu release or kernel version will require them to update their
custom policy".
By the way; what is an impact of these changes? (I mean LP:#1658219 and
LP:#1838090). Does it means, that now, use of 'm' and 'k' access is
secured/restricted/checked correctly by AppArmor? And one more thing:
this problem is related to v4.4 kernel only, right?
Thanks, best regards.
__
[1] https://launchpad.net/ubuntu/+source/linux/4.4.0-160.188
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1658219
Title:
flock not mediated by 'k'
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1658219/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1617630] Re: Mousepad show the warning Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus -*
Hello. Sorry for writing post by post, but there still are problems with Mousepad and 'connecting to accessibility bus' during editing any file. Here is an example: ,[ $ mousepad /usr/bin/example ] | ** (mousepad:14099): WARNING **: Couldn't connect to accessibility bus: | Failed to connect to socket /tmp/dbus-Z3dGTATnQK: Connection refused ` Note: the same WARNING message is displayed no matter if 'sudo(8)' command is being used. (However, it seems it is not a rule - if I remember correctly, there wasn't such a message earlier. I mean a couple months ago etc. But I could be wrong.) If it's about release, Mousepad and Xfce4 version informations, everything is the same as above - in my previous post. By the way: because there is not any reaction on this issue/bug, maybe it should be reported once again, but this time, choosing different 'Affects'? What do you think? Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1617630 Title: Mousepad show the warning Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus -* To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1617630/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1790688] Re: x86/pti: 32-bit x86 systems support already available.
Hello H Buus. Thank You for a comment. According to BUGs with call traces from 'kern.log' file (I mean especially 'unable to handle kernel NULL pointer dereference at 0008' messages etc.) I think you should report all these informations on the linux-kernel mailing list (please see 1). Also, I think, that the kernel-team mailing list is a good place -maybe even better than 'lkml' - to report, because this mailing list is used to coordinate and plan kernel uploads for Ubuntu (please see 2). I hope, that 'PTI' will be backported soon, to the Linux kernel used in 16.04 LTS Release and x86_32/i386 architecture. Thanks, best regards. _ 1.: https://lkml.org/ 2.: https://lists.ubuntu.com/archives/kernel-team/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1790688 Title: x86/pti: 32-bit x86 systems support already available. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790688/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835285] Re: PDF files don't open; "Failed to load backend for 'application/pdf': libpdfdocument.so" and "Invalid ELF header".
Hello. Sebastien, there is a good news. On Mon., Jul. 22, Evince has been updated to 3.18.2-1ubuntu4.6 version to fix one security issue (buffer overflow; CVE-2019-1010006)*. And now, I can open '.pdf' files again! I think, that reinstalling Evince package, also could help - I mean with problem I described, because `debsums(1)` showed, that MD5 sum for 'libpdfdocument.so' and 'libdvidocument.so' files does not match so reinstall - probably - was a solution. However, I have not any possibilities to check this. Thank You and I apologize one more time for such a long time without my answer. Thanks, best regards. _ * https://lists.ubuntu.com/archives/xenial-changes/2019-July/025019.html ** CVE added: https://cve.mitre.org/cgi- bin/cvename.cgi?name=2019-1010006 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835285 Title: PDF files don't open; "Failed to load backend for 'application/pdf': libpdfdocument.so" and "Invalid ELF header". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1835285/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835285] Re: PDF files don't open; "Failed to load backend for 'application/pdf': libpdfdocument.so" and "Invalid ELF header".
Hi Sebastien.
Thank You for an answer. And I apologize for such a long time without my
answer. (An accident, nothing serious).
So Sebastien, please tell me, which informations exactly do you need?
I'm thinking about a `journalctl -b 0` command, of course. Is there
something specific, that you want or need to gather?
I'm asking, because there is not *any* informations about Evince or
loading backend for 'application/pdf' - for example - in system log
files, such as »/var/log/{syslog,kern.log}«, even right after trying to
open '.pdf' or 'djvu' files etc. (as you asked for it in your comment).
I mean nothing valuable, that can help to diagnose this problem.
Yes, there is the same problem with '.djvu' files - they cannot be
opened via Evince. Summarizing: I have problems not only with '.pdf',
but with '.djvu' files also. I have no idea what about other supported
file formats (please see 4. and Evince AppArmor profile), because I
can't test them, right now. And honestly, I don't know if I will be able
to do this. Sorry. (So, I updated the bug report and added this
information).
Sebastien, you also asked about the result of the `debsums(1)` for
'libevdocument3-4', right? I had to install `debsums` package first but
here it is:
,[ $ debsums libevdocument3-4 ]
| /usr/lib/i386-linux-gnu/evince/4/backends/comicsdocument.evince-backend
OK
| /usr/lib/i386-linux-gnu/evince/4/backends/djvudocument.evince-backend
OK
| /usr/lib/i386-linux-gnu/evince/4/backends/dvidocument.evince-backend
OK
| /usr/lib/i386-linux-gnu/evince/4/backends/libcomicsdocument.so
OK
| /usr/lib/i386-linux-gnu/evince/4/backends/libdjvudocument.so
OK
| /usr/lib/i386-linux-gnu/evince/4/backends/libdvidocument.so
FAILED
| /usr/lib/i386-linux-gnu/evince/4/backends/libpdfdocument.so
FAILED
| /usr/lib/i386-linux-gnu/evince/4/backends/libpsdocument.so
OK
| /usr/lib/i386-linux-gnu/evince/4/backends/libtiffdocument.so
OK
| /usr/lib/i386-linux-gnu/evince/4/backends/libxpsdocument.so
OK
| /usr/lib/i386-linux-gnu/evince/4/backends/pdfdocument.evince-backend
OK
| /usr/lib/i386-linux-gnu/evince/4/backends/psdocument.evince-backend
OK
| /usr/lib/i386-linux-gnu/evince/4/backends/tiffdocument.evince-backend
OK
| /usr/lib/i386-linux-gnu/evince/4/backends/xpsdocument.evince-backend
OK
| /usr/lib/i386-linux-gnu/libevdocument3.so.4.0.0
OK
| /usr/share/doc/libevdocument3-4/AUTHORS
OK
| /usr/share/doc/libevdocument3-4/NEWS.gz
OK
| /usr/share/doc/libevdocument3-4/README
OK
| /usr/share/doc/libevdocument3-4/TODO
OK
| /usr/share/doc/libevdocument3-4/changelog.Debian.gz
OK
| /usr/share/doc/libevdocument3-4/copyright
OK
| /usr/share/lintian/overrides/libevdocument3-4
OK
`
As We can see, there are two 'FAILED' results. So the file's MD5 sum
does not match, right? What do you think about this? Is this a bug or
something on my side went wrong?
Sebastien, I apologize You once again, for such a long time without
answer. Best regards.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1835285
Title:
PDF files don't open; "Failed to load backend for 'application/pdf':
libpdfdocument.so" and "Invalid ELF header".
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1835285/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835285] Re: PDF files don't open; "Failed to load backend for 'application/pdf': libpdfdocument.so" and "Invalid ELF header".
** Summary changed: - PDF files do not open. 'Failed to load backend for 'application/pdf': libpdfdocument.so' and 'Invalid ELF header'. + PDF files don't open; "Failed to load backend for 'application/pdf': libpdfdocument.so" and "Invalid ELF header". ** Description changed: Hello. On Wed, Jun 19. 2019, Evince has been updated to version '3.18.2-1ubuntu4.5' [1]. This update added, among other things, some hardening from Ubuntu 18.10 Release. However, now, it is impossible to open any '.pdf' files. When I try to open such file, there is an information (on the red background) in the main Evince window. And It looks this way: - - ,[ Evince .pdf issue ] + ,[ Opening '.pdf' error ] | | Cannot open document „file:///home/user/Docs/foo-bar.pdf”. | Failed to load backend for 'application/pdf': | /usr/lib/i386-linux-gnu/evince/4/backends/libpdfdocument.so: Invalid ELF | header | ` - - There is a reference to '/usr/lib/i386-linux-gnu/evince/4/backends/libpdfdocument.so'. According to dpkg(1) command this file is a part of the 'libevdocument3-4' package, which is already installed (version '3.18.2-1ubuntu4.5'). I also tried to open '.pdf' file via terminal, but nothing changed. Here are the results: - + There is a reference to »/usr/lib/i386-linux- + gnu/evince/4/backends/libpdfdocument.so«. According to `dpkg(1)` command + this file is a part of the 'libevdocument3-4' package, which is + installed already (version '3.18.2-1ubuntu4.5'). I also tried to open + '.pdf' file via terminal, but nothing changed. Here are the results: ,[ $ evince Docs/foo-bar.pdf ] | | (evince:26918): EvinceDocument-WARNING **: | /usr/lib/i386-linux-gnu/evince/4/backends/libpdfdocument.so: Invalid ELF | header | | (evince:26918): EvinceDocument-WARNING **: | /usr/lib/i386-linux-gnu/evince/4/backends/libpdfdocument.so: Invalid ELF | header | ` + I think, that the whole problem is/could be related with AppArmor and + Evince profile changes in the latest update, because - for example - day + before, before update, everything was okay. Anyway, described + problem/issue started to happen right after Evince update. (To check + differences between AppArmor profile versions, please see 2. and 3.). + There is one more thing to notice: Evince profile, has never been + changed by the User. - I think, that the whole problem is related with AppArmor changes in the latest update, because - for example - day before everything was okay. The described problem started right after Evince updated to the latest version. (To check differences between versions, please see 2. and 3.). The 'Evince' profile has never been changed by the Users. + If it's about AppArmor: I've tried to change Evince profile mode from + 'enforce' to 'complain'. Unfortunately, nothing changed. There wasn't + any valuable entries in system log files etc. (I'm sorry, but for now, I + can not check other variants/solutions, such as: (a) disable Evince + profile via `aa-disable(8)` command or (b) make links between + »/etc/apparmor.d/usr.bin.evince« file and »/etc/apparmor.d/disable/« + directory, next use `apparmor_parser(8)` command to remove profile etc.) - If it's about AppArmor: I've tried to change Evince profile mode form 'enforce' to 'complain'. Unfortunately, nothing changed. There wasn't any valuable entries in system log files etc. (I'm sorry, but for now, I can not check other variants/solutions, such as: (a) disabling Evince profile with 'aa-disable(8)' command or (b) making links between '/etc/apparmor.d/usr.bin.evince' and '/etc/apparmor.d/disable/' directory, next using 'apparmor_parser(8)' command to remove profile etc.) - + ✖ NOTE: to make some more tests, I've tried to open '.djvu' file, but + without success. It seems, that there is exactly the same informations + as with '.pdf' files. Of course, Evince + (»/etc/apparmor.d/usr.bin.evince«) profile contains rule to open such + file format etc. and many others, see 4. So, according to all of this, + maybe "Summary" should be changed to reflect this situation? Maybe + something like: "PDF and other files don't open; "Failed to load (...)". + + Sebastien, what do You think?. + + Here are some additional informations: ✗ Description: Ubuntu 16.04.6 LTS ✗ Release: 16.04 ✗ Architecture: x86_32/i386 - ✗ Linux: 4.4.0-154-generic (4.4.0-155-generic is already installed, but reboot is needed) + ✗ Linux: 4.4.0-155-generic ✓ AppArmor: 2.10.95-0ubuntu2.11 ✓ Evince: 3.18.2-1ubuntu4.5 - Best regards. __ [1] https://lists.ubuntu.com/archives/xenial-changes/2019-June/024691.html [2] http://launchpadlibrarian.net/429511526/evince_3.18.2-1ubuntu4.4_3.18.2-1ubuntu4.5.diff.gz [3] http://launchpadlibrarian.net/429293224/evince_3.18.2-1ubuntu4.1_3.18.2-1ubuntu4.5.diff.gz + [4]
[Bug 1835285] Re: PDF files do not open. 'Failed to load backend for 'application/pdf': libpdfdocument.so' and 'Invalid ELF header'.
** Description changed: Hello. On Wed, Jun 19. 2019, Evince has been updated to version '3.18.2-1ubuntu4.5' [1]. This update added, among other things, some - hardening from Ubuntu 18.10 Release. However, it seems to be impossible - to open any '.pdf' files. After Evince update, I notices I can't open - any '.pdf'. When I try to do it, Evince show this info: + hardening from Ubuntu 18.10 Release. However, now, it is impossible to + open any '.pdf' files. When I try to open such file, there is an + information (on the red background) in the main Evince window. And It + looks this way: ,[ Evince .pdf issue ] | | Cannot open document „file:///home/user/Docs/foo-bar.pdf”. | Failed to load backend for 'application/pdf': | /usr/lib/i386-linux-gnu/evince/4/backends/libpdfdocument.so: Invalid ELF | header | ` There is a reference to '/usr/lib/i386-linux-gnu/evince/4/backends/libpdfdocument.so'. According to dpkg(1) command this file is a part of the 'libevdocument3-4' package, which is already installed (version '3.18.2-1ubuntu4.5'). I also tried to open '.pdf' file via terminal, but nothing changed. Here are the results: ,[ $ evince Docs/foo-bar.pdf ] | | (evince:26918): EvinceDocument-WARNING **: | /usr/lib/i386-linux-gnu/evince/4/backends/libpdfdocument.so: Invalid ELF | header | | (evince:26918): EvinceDocument-WARNING **: | /usr/lib/i386-linux-gnu/evince/4/backends/libpdfdocument.so: Invalid ELF | header | ` I think, that the whole problem is related with AppArmor changes in the latest update, because - for example - day before everything was okay. The described problem started right after Evince updated to the latest version. (To check differences between versions, please see 2. and 3.). The 'Evince' profile has never been changed by the Users. If it's about AppArmor: I've tried to change Evince profile mode form 'enforce' to 'complain'. Unfortunately, nothing changed. There wasn't any valuable entries in system log files etc. (I'm sorry, but for now, I can not check other variants/solutions, such as: (a) disabling Evince profile with 'aa-disable(8)' command or (b) making links between '/etc/apparmor.d/usr.bin.evince' and '/etc/apparmor.d/disable/' directory, next using 'apparmor_parser(8)' command to remove profile etc.) + Here are some additional informations: - Here are some technical informations: + ✗ Description: Ubuntu 16.04.6 LTS + ✗ Release: 16.04 + ✗ Architecture: x86_32/i386 + ✗ Linux: 4.4.0-154-generic (4.4.0-155-generic is already installed, but reboot is needed) - ✗ Description:Ubuntu 16.04.6 LTS - ✗ Release:16.04 - ✗ Architecture: x86_32/i386 - ✗ Linux kernel: 4.4.0-154-generic (4.4.0-155-generic is already installed, but reboot is needed) - - ✓ AppArmor: 2.10.95-0ubuntu2.11 - ✓ Evince: 3.18.2-1ubuntu4.5 + ✓ AppArmor: 2.10.95-0ubuntu2.11 + ✓ Evince: 3.18.2-1ubuntu4.5 Best regards. __ [1] https://lists.ubuntu.com/archives/xenial-changes/2019-June/024691.html [2] http://launchpadlibrarian.net/429511526/evince_3.18.2-1ubuntu4.4_3.18.2-1ubuntu4.5.diff.gz [3] http://launchpadlibrarian.net/429293224/evince_3.18.2-1ubuntu4.1_3.18.2-1ubuntu4.5.diff.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835285 Title: PDF files do not open. 'Failed to load backend for 'application/pdf': libpdfdocument.so' and 'Invalid ELF header'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1835285/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835285] Re: PDF files do not open. 'Failed to load backend for 'application/pdf': libpdfdocument.so' and 'Invalid ELF header'.
** Description changed: Hello. On Wed, Jun 19. 2019, Evince has been updated to version '3.18.2-1ubuntu4.5' [1]. This update added, among other things, some hardening from Ubuntu 18.10 Release. However, it seems to be impossible to open any '.pdf' files. After Evince update, I notices I can't open any '.pdf'. When I try to do it, Evince show this info: ,[ Evince .pdf issue ] | | Cannot open document „file:///home/user/Docs/foo-bar.pdf”. - | Failed to load backend for 'application/pdf': /usr/lib/i386-linux-gnu/evince/4/backends - | /libpdfdocument.so: Invalid ELF header + | Failed to load backend for 'application/pdf': + | /usr/lib/i386-linux-gnu/evince/4/backends/libpdfdocument.so: Invalid ELF header | ` There is a reference to '/usr/lib/i386-linux-gnu/evince/4/backends/libpdfdocument.so'. According to dpkg(1) command this file is a part of the 'libevdocument3-4' package, which is already installed (version '3.18.2-1ubuntu4.5'). I also tried to open '.pdf' file via terminal, but nothing changed. Here are the results: ,[ $ evince Docs/foo-bar.pdf ] | - | (evince:26918): EvinceDocument-WARNING **: /usr/lib/i386-linux-gnu/evince/4/backends - | /libpdfdocument.so: Invalid ELF header + | (evince:26918): EvinceDocument-WARNING **: + | /usr/lib/i386-linux-gnu/evince/4/backends/libpdfdocument.so: Invalid ELF header | - | (evince:26918): EvinceDocument-WARNING **: /usr/lib/i386-linux-gnu/evince/4/backends - | /libpdfdocument.so: Invalid ELF header + | (evince:26918): EvinceDocument-WARNING **: + | /usr/lib/i386-linux-gnu/evince/4/backends/libpdfdocument.so: Invalid ELF header | ` I think, that the whole problem is related with AppArmor changes in the latest update, because - for example - day before everything was okay. The described problem started right after Evince updated to the latest version. (To check differences between versions, please see 2. and 3.). The 'Evince' profile has never been changed by the Users. If it's about AppArmor: I've tried to change Evince profile mode form 'enforce' to 'complain'. Unfortunately, nothing changed. There wasn't any valuable entries in system log files etc. (I'm sorry, but for now, I can not check other variants/solutions, such as: (a) disabling Evince profile with 'aa-disable(8)' command or (b) making links between '/etc/apparmor.d/usr.bin.evince' and '/etc/apparmor.d/disable/' directory, next using 'apparmor_parser(8)' command to remove profile etc.) Here are some technical informations: ✗ Description:Ubuntu 16.04.6 LTS ✗ Release:16.04 ✗ Architecture: x86_32/i386 ✗ Linux kernel: 4.4.0-154-generic (4.4.0-155-generic is already installed, but reboot is needed) ✓ AppArmor: 2.10.95-0ubuntu2.11 ✓ Evince: 3.18.2-1ubuntu4.5 Best regards. __ [1] https://lists.ubuntu.com/archives/xenial-changes/2019-June/024691.html [2] http://launchpadlibrarian.net/429511526/evince_3.18.2-1ubuntu4.4_3.18.2-1ubuntu4.5.diff.gz [3] http://launchpadlibrarian.net/429293224/evince_3.18.2-1ubuntu4.1_3.18.2-1ubuntu4.5.diff.gz ** Description changed: Hello. On Wed, Jun 19. 2019, Evince has been updated to version '3.18.2-1ubuntu4.5' [1]. This update added, among other things, some hardening from Ubuntu 18.10 Release. However, it seems to be impossible to open any '.pdf' files. After Evince update, I notices I can't open any '.pdf'. When I try to do it, Evince show this info: ,[ Evince .pdf issue ] | | Cannot open document „file:///home/user/Docs/foo-bar.pdf”. | Failed to load backend for 'application/pdf': - | /usr/lib/i386-linux-gnu/evince/4/backends/libpdfdocument.so: Invalid ELF header + | /usr/lib/i386-linux-gnu/evince/4/backends/libpdfdocument.so: Invalid ELF + | header | ` There is a reference to '/usr/lib/i386-linux-gnu/evince/4/backends/libpdfdocument.so'. According to dpkg(1) command this file is a part of the 'libevdocument3-4' package, which is already installed (version '3.18.2-1ubuntu4.5'). I also tried to open '.pdf' file via terminal, but nothing changed. Here are the results: ,[ $ evince Docs/foo-bar.pdf ] | | (evince:26918): EvinceDocument-WARNING **: - | /usr/lib/i386-linux-gnu/evince/4/backends/libpdfdocument.so: Invalid ELF header + | /usr/lib/i386-linux-gnu/evince/4/backends/libpdfdocument.so: Invalid ELF + | header | | (evince:26918): EvinceDocument-WARNING **: - | /usr/lib/i386-linux-gnu/evince/4/backends/libpdfdocument.so: Invalid ELF header + | /usr/lib/i386-linux-gnu/evince/4/backends/libpdfdocument.so: Invalid ELF + | header | ` I think, that the whole problem is related with AppArmor changes in the latest update, because - for example - day before everything was okay. The described problem started right after Evince updated to the latest version. (To check differences between versions, please
[Bug 1835285] [NEW] PDF files do not open. 'Failed to load backend for 'application/pdf': libpdfdocument.so' and 'Invalid ELF header'.
Public bug reported: Hello. On Wed, Jun 19. 2019, Evince has been updated to version '3.18.2-1ubuntu4.5' [1]. This update added, among other things, some hardening from Ubuntu 18.10 Release. However, it seems to be impossible to open any '.pdf' files. After Evince update, I notices I can't open any '.pdf'. When I try to do it, Evince show this info: ,[ Evince .pdf issue ] | | Cannot open document „file:///home/user/Docs/foo-bar.pdf”. | Failed to load backend for 'application/pdf': /usr/lib/i386-linux-gnu/evince/4/backends | /libpdfdocument.so: Invalid ELF header | ` There is a reference to '/usr/lib/i386-linux-gnu/evince/4/backends/libpdfdocument.so'. According to dpkg(1) command this file is a part of the 'libevdocument3-4' package, which is already installed (version '3.18.2-1ubuntu4.5'). I also tried to open '.pdf' file via terminal, but nothing changed. Here are the results: ,[ $ evince Docs/foo-bar.pdf ] | | (evince:26918): EvinceDocument-WARNING **: /usr/lib/i386-linux-gnu/evince/4/backends | /libpdfdocument.so: Invalid ELF header | | (evince:26918): EvinceDocument-WARNING **: /usr/lib/i386-linux-gnu/evince/4/backends | /libpdfdocument.so: Invalid ELF header | ` I think, that the whole problem is related with AppArmor changes in the latest update, because - for example - day before everything was okay. The described problem started right after Evince updated to the latest version. (To check differences between versions, please see 2. and 3.). The 'Evince' profile has never been changed by the Users. If it's about AppArmor: I've tried to change Evince profile mode form 'enforce' to 'complain'. Unfortunately, nothing changed. There wasn't any valuable entries in system log files etc. (I'm sorry, but for now, I can not check other variants/solutions, such as: (a) disabling Evince profile with 'aa-disable(8)' command or (b) making links between '/etc/apparmor.d/usr.bin.evince' and '/etc/apparmor.d/disable/' directory, next using 'apparmor_parser(8)' command to remove profile etc.) Here are some technical informations: ✗ Description: Ubuntu 16.04.6 LTS ✗ Release: 16.04 ✗ Architecture: x86_32/i386 ✗ Linux kernel: 4.4.0-154-generic (4.4.0-155-generic is already installed, but reboot is needed) ✓ AppArmor: 2.10.95-0ubuntu2.11 ✓ Evince: 3.18.2-1ubuntu4.5 Best regards. __ [1] https://lists.ubuntu.com/archives/xenial-changes/2019-June/024691.html [2] http://launchpadlibrarian.net/429511526/evince_3.18.2-1ubuntu4.4_3.18.2-1ubuntu4.5.diff.gz [3] http://launchpadlibrarian.net/429293224/evince_3.18.2-1ubuntu4.1_3.18.2-1ubuntu4.5.diff.gz ** Affects: evince (Ubuntu) Importance: Undecided Status: New ** Tags: elf evince header libpdfdocument.so pdf xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835285 Title: PDF files do not open. 'Failed to load backend for 'application/pdf': libpdfdocument.so' and 'Invalid ELF header'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1835285/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1492560] Re: package libopenal-data 1:1.14-4ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
Trusty is now end-of-life, later releases of openal-soft don't have this issue. ** Changed in: openal-soft (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/1492560 Title: package libopenal-data 1:1.14-4ubuntu1 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/openal-soft/+bug/1492560/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821019] Re: gnome-terminal does not gain focus upon launch
Updated description and title to add M_M comments as I can confirm them as well. ** Description changed: Ubuntu 19.04, 64 bit machine, nvidia graphics drivers - Upon first and subsequent launches of gnome-terminal the window shows - but does not immediately gain focus to start typing in commands. + Upon first and subsequent launches of gnome-terminal via clicking the + icon, the window shows but does not immediately gain focus to start + typing in commands. + + Using Ctrl+alt+T launches the terminal the way I expect, with immediate + focus to start typing commands. I expect it to immediately gain focus to type commands upon launch each - and every time. + and every time using both methods. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-terminal 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 20 10:40:18 2019 InstallationDate: Installed on 2018-03-02 (382 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) ** Summary changed: - gnome-terminal does not gain focus upon launch + gnome-terminal does not gain focus upon launch via clicking icon -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821019 Title: gnome-terminal does not gain focus upon launch via clicking icon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1821019/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821019] [NEW] gnome-terminal does not gain focus upon launch
Public bug reported: Ubuntu 19.04, 64 bit machine, nvidia graphics drivers Upon first and subsequent launches of gnome-terminal the window shows but does not immediately gain focus to start typing in commands. I expect it to immediately gain focus to type commands upon launch each and every time. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-terminal 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 20 10:40:18 2019 InstallationDate: Installed on 2018-03-02 (382 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821019 Title: gnome-terminal does not gain focus upon launch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1821019/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1815752] Re: nvidia-340 340.104-0ubuntu0.16.04.1: nvidia-340 kernel module failed to build
Hello. Once agains - I'm sorry for writing post by post, but there is a very interesting comment I found, while checking patches/fixes in Linux v4.4.0-143.169 version (see '1.'). This is excatly the same error, that happened when I updated kernel to the latest '-proposed' release etc. In both cases, it's about "Processing triggers for linux- image-4.4.0-143-generic" and bad return status for 'nvidia' module build. So, maybe the whole problem with building 'nvidia' module is related with "signing: only install a signed kernel (LP: #1764794)" (see '2.')? Thanks, best regards. _ [1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1764794/comments/6 [2] https://launchpad.net/ubuntu/+source/linux/4.4.0-143.169 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1815752 Title: nvidia-340 340.104-0ubuntu0.16.04.1: nvidia-340 kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1815752/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1815776] Re: nvidia-384 384.130-0ubuntu0.16.04.1: nvidia-384 kernel module failed to build
Hello. Once agains - I'm sorry for writing post by post, but there is a very interesting comment I found, while checking patches/fixes in Linux v4.4.0-143.169 version (see '1.'). This is excatly the same error, that happened when I updated kernel to the latest '-proposed' release etc. In both cases, it's about "Processing triggers for linux- image-4.4.0-143-generic" and bad return status for 'nvidia' module build. So, maybe the whole problem with building 'nvidia' module is related with "signing: only install a signed kernel (LP: #1764794)" (see '2.')? Thanks, best regards. _ [1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1764794/comments/6 [2] https://launchpad.net/ubuntu/+source/linux/4.4.0-143.169 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1815776 Title: nvidia-384 384.130-0ubuntu0.16.04.1: nvidia-384 kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-384/+bug/1815776/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1815858] Re: nvidia-304 304.135-0ubuntu0.16.04.2: nvidia-304 kernel module failed to build
Hello. Once agains - I'm sorry for writing post by post, but there is a very interesting comment I found, while checking patches/fixes in Linux v4.4.0-143.169 version (see '1.'). This is excatly the same error, that happened when I updated kernel to the latest '-proposed' release etc. In both cases, it's about "Processing triggers for linux- image-4.4.0-143-generic" and bad return status for 'nvidia' module build. So, maybe the whole problem with building 'nvidia' module is related with "signing: only install a signed kernel (LP: #1764794)" (see '2.')? In the last hours, two more more bug reports were created - all related with 'nvidia' module build issues etc. (see '3.', '4.'). One difference is nvidia driver version. Thanks, best regards. ___ [1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1764794/comments/6 [2] https://launchpad.net/ubuntu/+source/linux/4.4.0-143.169 [3] https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1815752 [4] https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-384/+bug/1815776 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1815858 Title: nvidia-304 304.135-0ubuntu0.16.04.2: nvidia-304 kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1815858/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1773561] Re: Xenial/16.04: GIMP needs a security update - unfixed issues (CVE-2017: 17784-17789).
** Changed in: gimp (Ubuntu Xenial) Status: Confirmed => New ** Information type changed from Public Security to Private Security -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1773561 Title: Xenial/16.04: GIMP needs a security update - unfixed issues (CVE-2017: 17784-17789). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1773561/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1815752] Re: nvidia-340 340.104-0ubuntu0.16.04.1: nvidia-340 kernel module failed to build
Hello. There is a similar raport about failed 'nvidia_304' module build on latest '-proposed' v4.4.0-143-generic kernel: ✗ https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics- drivers-304/+bug/1815858 Mentioned issue happened on both: amd64 and i385/i686 architectures. Best regards. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1815752 Title: nvidia-340 340.104-0ubuntu0.16.04.1: nvidia-340 kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1815752/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1815776] Re: nvidia-384 384.130-0ubuntu0.16.04.1: nvidia-384 kernel module failed to build
Hello. There is a similar raport about failed 'nvidia_304' module build on latest '-proposed' v4.4.0-143-generic kernel: ✗ https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics- drivers-304/+bug/1815858 Mentioned issue happened on both: amd64 and i385/i686 architectures. Best regards. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1815776 Title: nvidia-384 384.130-0ubuntu0.16.04.1: nvidia-384 kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-384/+bug/1815776/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1815858] Re: nvidia-304 304.135-0ubuntu0.16.04.2: nvidia-304 kernel module failed to build
Hello. I'm sorry for writing post by post, but I forget to write, that - in my case - architecture is i386/i686. There is also one more issue: I've made a mistake during writing my post, in the last 'Makefile/make[1]' informations (see exceptions from a build log): of course, there should be "recipe for target 'module' failed". Best regards. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1815858 Title: nvidia-304 304.135-0ubuntu0.16.04.2: nvidia-304 kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1815858/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1815858] Re: nvidia-304 304.135-0ubuntu0.16.04.2: nvidia-304 kernel module failed to build
Hello. It seems, that I'm experiencing exactly the same problem. During kernel update process to v4.4.0-143.169 (from '-proposed') there was an error message about some issues with 'nvidia' module etc. '/var/lib/dkms/nvidia-304/304.135/build/make.log' file contains a full build process informations. Here are some examples (I can paste it somewhere): [ NVIDIA Build log examples ] In file included from ./arch/x86/include/asm/preempt.h:5:0, from include/linux/preempt.h:59, from include/linux/spinlock.h:50, from include/linux/seqlock.h:35, from include/linux/time.h:5, from include/uapi/linux/timex.h:56, from include/linux/timex.h:56, from include/linux/sched.h:19, from include/linux/utsname.h:5, from /var/lib/dkms/nvidia-304/304.135/build/nv-linux.h:40, from /var/lib/dkms/nvidia-304/304.135/build/nv.c:13: include/linux/percpu-refcount.h: In function ‘percpu_ref_get_many’: ./arch/x86/include/asm/percpu.h:130:31: warning: comparison between signed and unsigned integer expressions [-Wsign-compare] ((val) == 1 || (val) == -1)) ? \ ^ (...) include/linux/percpu-refcount.h: In function ‘percpu_ref_get_many’: ./arch/x86/include/asm/percpu.h:130:31: warning: comparison between signed and unsigned integer expressions [-Wsign-compare] ((val) == 1 || (val) == -1)) ? \ ^ (...) include/linux/percpu-defs.h:394:11: note: in expansion of macro ‘this_cpu_add_1’ case 1: stem##1(variable, __VA_ARGS__);break; \ ^ (...) include/linux/percpu-refcount.h:276:3: note: in expansion of macro ‘this_cpu_sub’ this_cpu_sub(*percpu_count, nr); ^ (...) include/linux/compiler.h:165:40: note: in definition of macro ‘likely’ # define likely(x) __builtin_expect(!!(x), 1) ^ (...) In file included from /var/lib/dkms/nvidia-304/304.135/build/nv-linux.h:82:0, from /var/lib/dkms/nvidia-304/304.135/build/nv-mlock.c:15: include/linux/mm.h:1222:6: note: declared here long get_user_pages(struct task_struct *tsk, struct mm_struct *mm, ^ (...) make[2]: *** [_module_/var/lib/dkms/nvidia-304/304.135/build] Error 2 NVIDIA: left KBUILD. nvidia.ko failed to build! Makefile:257: commands for 'module' object failed make[1]: *** [module] Error 1 makefile:59: commands for 'module' object failed make: *** [module] Error 2 ● NOTE: There is more definitions of, mentioned above, 'macros'. For example: ‘__pcpu_size_call’, ‘this_cpu_add’, ‘percpu_add_op’, ‘this_cpu_add_4’ etc. Generally, they all are repeated in build log. [ END of NVIDIA Build log example ] That's is only an example (whole build log contains about ~1500 lines). Most interesting and strange part is that I'm not using 'nvidia' or 'nouveau' module, but I still can log to system via LightDM! Why is that? Shouldn't there be some graphics issues? Here are some more informations about 'nvidia' module (NOTE: I'm logged in and using v4.4.0-143-generic kernel - on which 'nvidia' module failed to build): [~]$ modinfo nvidia modinfo: ERROR: Module nvidia not found. [~]$ sudo modprobe nvidia modprobe: ERROR: ../libkmod/libkmod-module.c:832 kmod_module_insert_module() could not find module by name='nvidia_304' modprobe: ERROR: could not insert 'nvidia_304': Unknown symbol in module, or unknown parameter (see dmesg) [~]$ sudo modprobe nvidia_304 modprobe: FATAL: Module nvidia_304 not found in directory /lib/modules/4.4.0-143-generic (NOTE: dmesg(1) is empty - there is no informations about 'nvidia' issues). [~]$ lsmod |grep nvidia [~]$ lsmod |grep nouveau By the way: there were some problems with graphics when monitor blacked out (there should 'light-locker' show up), because of - for example - no mouse movements or no reaction from user side and after resume colors were bright, fonts thiner etc. If it's about X.org logs, there is something like this in '/var/log/Xorg.0.log' file: (II) LoadModule: "nvidia" (II) Loading /usr/lib/i386-linux-gnu/xorg/extra-modules/nvidia_drv.so (II) Module nvidia: vendor="NVIDIA Corporation" compiled for 4.0.2, module version = 1.0.0 (...) (EE) NVIDIA: Failed to load the NVIDIA kernel module. Please check your (EE) NVIDIA: system's kernel log for additional error messages. (II) UnloadModule: "nvidia" (II) Unloading nvidia (EE) Failed to load module "nvidia" (module-specific error, 0) (II) LoadModule: "nouveau" (II) Loading /usr/lib/xorg/modules/drivers/nouveau_drv.so Now, some technical informations about versions etc.: ✗ Linux kernel: v4.4.0-143-generic ✗ Description: Ubuntu 16.04.5 LTS Release: 16.04 ✗ nvidia-304 304.135-0ubuntu0.16.04.2 ✗ nvidia-304-updates 304.135-0ubuntu0.16.04.2 ✗ xserver-xorg-video-nouveau 1:1.0.12-1build2 ✗ lspci(8) info: 00:10.0
[Bug 1808421] Re: gparted produces unusual results when ZFS partitios exist
Yes, the issue you are experiencing looks similar. The next course of action is to "follow up with the authors of the util- linux package?" They should have a mailing list or something to track issues. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1808421 Title: gparted produces unusual results when ZFS partitios exist To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gparted/+bug/1808421/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1808421] Re: gparted produces unusual results when ZFS partitios exist
Alternatively you may need a fixed version of blkid if blkid is reporting 2 contradictory signatures for the whole disk: For example: - TYPE="zfs_member" ZFS file system on the whole disk. - PTTYPE="gpt" GPT (GUID Partition table). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1808421 Title: gparted produces unusual results when ZFS partitios exist To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gparted/+bug/1808421/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1808421] Re: gparted produces unusual results when ZFS partitios exist
>From the description it appears that at one time the whole disk was formatted as zfs and that those file system signatures remain. You can check what is going on with the following two commands: sudo blkid /dev/sda sudo wipefs --no-act /dev/sda To fix you will likely need to remove the extraneous file system signatures. The wipefs command can help you remove the specific incorrect signature. For reference, see: zfs partition wrongly shows occupying the whole disk https://gitlab.gnome.org/GNOME/gparted/issues/14 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1808421 Title: gparted produces unusual results when ZFS partitios exist To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gparted/+bug/1808421/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1738736] Re: ACPI error message flooding syslog
I have the same flooding of /var/log/syslog about every 200 msecs with: Oct 27 21:17:01 helios kernel: [11807.295919] ACPI Error: Method parse/execution failed \_SB.PCI0.LPCB.H_EC._Q50, AE_AML_OPERAND_TYPE (20170831/psparse-550) Oct 27 21:17:02 helios kernel: [11807.497617] ACPI Error: Needed type [Reference], found [Integer] dfb12c24 (20170831/exresop-103) Oct 27 21:17:02 helios kernel: [11807.497647] ACPI Exception: AE_AML_OPERAND_TYPE, While resolving operands for [Store] (20170831/dswexec-461) Oct 27 21:17:02 helios kernel: [11807.497677] No Local Variables are initialized for Method [_Q50] Oct 27 21:17:02 helios kernel: [11807.497683] No Arguments are initialized for method [_Q50] ~ $ inxi -Fx System:Host: helios Kernel: 4.15.0-38-generic x86_64 bits: 64 gcc: 7.3.0 Desktop: Cinnamon 3.8.9 (Gtk 3.22.30-1ubuntu1) Distro: Linux Mint 19 Tara Machine: Device: laptop System: Intel product: Skylake Platform v: 0.1 serial: N/A Mobo: Topstar model: WhiteTip Mountain1 Fab2 v: RVP7 serial: N/A UEFI: American Megatrends v: 5.11 date: 09/10/2015 BatteryBAT0: charge: 42.0 Wh 98.6% condition: 42.6/46.6 Wh (91%) model: TPS S10 status: N/A CPU: Dual core Intel Core i5-6200U (-MT-MCP-) arch: Skylake rev.3 cache: 3072 KB flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 9600 clock speeds: max: 2800 MHz 1: 500 MHz 2: 500 MHz 3: 500 MHz 4: 500 MHz Graphics: Card: Intel HD Graphics 520 bus-ID: 00:02.0 Display Server: x11 (X.Org 1.19.6 ) drivers: modesetting (unloaded: fbdev,vesa) Resolution: 1920x1080@60.00hz OpenGL: renderer: Mesa DRI Intel HD Graphics 520 (Skylake GT2) version: 4.5 Mesa 18.0.5 Direct Render: Yes Audio: Card Intel Sunrise Point-LP HD Audio driver: snd_hda_intel bus-ID: 00:1f.3 Sound: Advanced Linux Sound Architecture v: k4.15.0-38-generic Network: Card: Intel Wireless 3160 driver: iwlwifi bus-ID: 01:00.0 IF: wlp1s0 state: up mac: b4:6d:83:95:8c:b0 Drives:HDD Total Size: 250.1GB (57.3% used) ID-1: /dev/sda model: Samsung_SSD_850 size: 250.1GB Partition: ID-1: / size: 31G used: 24G (81%) fs: ext4 dev: /dev/sda2 ID-2: /home size: 62G used: 17G (29%) fs: ext4 dev: /dev/sda3 ID-3: swap-1 size: 10.49GB used: 0.00GB (0%) fs: swap dev: /dev/dm-0 RAID: No RAID devices: /proc/mdstat, md_mod kernel module present Sensors: System Temperatures: cpu: 34.0C mobo: N/A Fan Speeds (in rpm): cpu: N/A Info: Processes: 223 Uptime: 7:10 Memory: 1671.1/7886.5MB Init: systemd runlevel: 5 Gcc sys: 7.3.0 Client: Shell (bash 4.4.191) inxi: 2.3.56 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1738736 Title: ACPI error message flooding syslog To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1738736/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1790688] Re: x86/pti: 32-bit x86 systems support already available.
Hello. I would like to note, that "Meltdown" mitigation - for i386 architecture - among others improvements, is already available in OpenBSD 6.4 release (see "Security improvements" section [in:] https://www.openbsd.org/64.html). Best regards. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1790688 Title: x86/pti: 32-bit x86 systems support already available. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790688/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1516256] Re: MyGUI_OpenGLImageLoader.h is missing in libmygui-dev
And uploaded: https://incoming.debian.org/debian- buildd/pool/main/m/mygui/mygui_3.2.2%2Bdfsg-2.dsc ** Changed in: mygui (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1516256 Title: MyGUI_OpenGLImageLoader.h is missing in libmygui-dev To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mygui/+bug/1516256/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1516256] Re: MyGUI_OpenGLImageLoader.h is missing in libmygui-dev
Should be fixed in Debian with 3.2.2+dfsg-2, it just needs to be uploaded. ** Changed in: mygui (Ubuntu) Assignee: (unassigned) => Bret Curtis (psi29a) ** Changed in: mygui (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1516256 Title: MyGUI_OpenGLImageLoader.h is missing in libmygui-dev To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mygui/+bug/1516256/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1516256] Re: MyGUI_OpenGLImageLoader.h is missing in libmygui-dev
Fix Commited: https://salsa.debian.org/psi29a- guest/MyGUI/commit/9d3afce869d5e50f2423ab8bdd359db80009c05c -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1516256 Title: MyGUI_OpenGLImageLoader.h is missing in libmygui-dev To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mygui/+bug/1516256/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1797355] Re: Once logged in, GDM Shell process CPU usage spiking at 100%
NVIDIA GeForce GTX 970 using driver 390.87 64Bit architecture I know that my windows NVIDIA drivers are in the 400's. Would it be worth testing a newer NVIDIA driver? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1797355 Title: Once logged in, GDM Shell process CPU usage spiking at 100% To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1797355/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1796865] [NEW] package libwoff1 1.0.2-1build0.1 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2
Public bug reported: lsb_release -rd Description:Ubuntu 18.04.1 LTS Release:18.04 What I expected to happen: I expected Ubuntu to start without any errors. What happened instead: I received an error after logging in saying that a system app had a problem. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libwoff1 1.0.2-1build0.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 AptOrdering: libbrotli1:amd64: Install libwoff1:amd64: Install libwebkit2gtk-4.0-37:amd64: Install libjavascriptcoregtk-4.0-18:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Mon Oct 8 11:18:45 2018 Dependencies: gcc-8-base 8.2.0-1ubuntu2~18.04 libbrotli1 1.0.3-1ubuntu1.2 libc6 2.27-3ubuntu1 libgcc1 1:8.2.0-1ubuntu2~18.04 libstdc++6 8.2.0-1ubuntu2~18.04 DuplicateSignature: package:libwoff1:1.0.2-1build0.1 Unpacking libwoff1:amd64 (1.0.2-1build0.1) ... dpkg-deb: error: failed to read archive '/var/cache/apt/archives/libwoff1_1.0.2-1build0.1_amd64.deb': No such file or directory dpkg: error processing archive /var/cache/apt/archives/libwoff1_1.0.2-1build0.1_amd64.deb (--unpack): dpkg-deb --fsys-tarfile subprocess returned error exit status 2 ErrorMessage: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 InstallationDate: Installed on 2018-03-29 (193 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) Python3Details: /usr/bin/python3.6, Python 3.6.6, 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.3ubuntu0.1 SourcePackage: woff2 Title: package libwoff1 1.0.2-1build0.1 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 UpgradeStatus: Upgraded to bionic on 2018-05-08 (153 days ago) ** Affects: woff2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1796865 Title: package libwoff1 1.0.2-1build0.1 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/woff2/+bug/1796865/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1796504] Re: gparted does not see f2fs-tools installed (Ubuntu 18.10 Cosmic)
The behaviour seen in GParted is because GParted is unable to read the used/unused information from the F2FS file system. Hence it warns that some operations may be unavailable. This is due to limitations in the file system tools for F2FS. See also: https://gparted.org/features.php And note that GParted does not have READ capability for F2FS. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1796504 Title: gparted does not see f2fs-tools installed (Ubuntu 18.10 Cosmic) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gparted/+bug/1796504/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1773561] Re: Xenial/16.04: GIMP needs a security update - unfixed issues (CVE-2017: 17784-17789).
** Changed in: gimp (Ubuntu) Status: Confirmed => Incomplete ** Changed in: gimp (Ubuntu Xenial) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1773561 Title: Xenial/16.04: GIMP needs a security update - unfixed issues (CVE-2017: 17784-17789). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1773561/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1790688] Re: x86/pti: 32-bit x86 systems support already available.
** Summary changed:
- x86/pti: 32-Bit x86 systems support already available.
+ x86/pti: 32-bit x86 systems support already available.
** Description changed:
Hello.
- Linux kernel v4.19 release candidate [1], finally have kernel page-table
- isolation ('PTI', previously known as 'KAISER') support for x86_32
- architecture. As we know, 'PTI' provides protection against attack,
- known as the "Meltdown" (CVE-2017-5754), that breaks isolation between
- user applications and the operating system etc. However, kernel page-
- table isolation wasn't available on 32-Bit x86 systems. Until now.
+ This is a very good news: 'PTI' support for x86-32 architecture is
+ available. Linux kernel v4.19 release candidate, finally have Kernel
+ Page-Table Isolation ('PTI', previously known as 'KAISER') support. As
+ we know, 'PTI' provides protection against attack, known as the
+ "Meltdown" (CVE-2017-5754), that breaks isolation between user
+ applications and the operating system etc. However, this protection -
+ needed for "Meltdown" mitigation - wasn't available on 32-bit x86
+ systems. Until now.
So, I would like to ask a question: are there any plans to backport
- kernel page-table isolation patches for Linux kernels available in
- "Trusty"/14.04, "Xenial"/16.04 and "Bionic"/18.04 releases etc.? I mean
- x86_32 bit architecture, of course. I'm asking, because it seems, that
- pretty much no developers run 32-bit any more. However, there still are
- many 32-bit users out there.
+ Kernel Page-Table Isolation patches for Linux kernels available in
+ "Trusty"/14.04, "Xenial"/16.04 and "Bionic"/18.04 releases etc.? I'm
+ asking, because it seems, that pretty much no developers run 32-bit any
+ more. However, there still are many 32-bit users out there.
- For more informations about how 'PTI' was implementing on 32-Bit x86
- architecture, plase check - for example - commit '7757d607c6b31'
- ("x86/pti: Allow CONFIG_PAGE_TABLE_ISOLATION for x86_32"). Here are
- messages about 'PTI' support (PATCH v7, v8) for x86_32 [1]. Next, 'PTI'
- fixes for x86-32 [2] and more patches related to 'x86/mm/pti' [3]. There
- is also a short report for the first half of the 4.19 kernel merge
- window [4].
+ For more informations about how 'PTI' was implemented, created for 32
+ bit x86 architecture, please check - for example - commit
+ '7757d607c6b31' ("x86/pti: Allow CONFIG_PAGE_TABLE_ISOLATION for
+ x86_32") and these messages on lkml mailing list and lwn.net website
+ (which contains summary of the first half of the 4.19 kernel merge
+ window):
- I'm sorry for such a long message, but I'm very happy that 'PTI' support
- is already available for x86_32 architecture and I hope, that it will be
- backported to all Ubuntu LTS releases etc.
+ ✗ http://lkml.iu.edu/hypermail/linux/kernel/1807.2/02790.html ('PTI' on
x86-32; PATCH v.8)
+ ✗ https://lwn.net/Articles/762566/ (See "Architecture-specific" changes)
+
+ I would like to send a big "Thank You" to Mr Joerg Roedel (and Others,
+ of course) for his amazing work - a whole raft of measures and patches
+ to make this possible - to enable 'PTI' mitigation on x86-32
+ architecture etc.
Thanks, best regards.
- __
-
- [1] http://lkml.iu.edu/hypermail/linux/kernel/1807.1/03578.html (please see
every next patches etc.)
- http://lkml.iu.edu/hypermail/linux/kernel/1807.1/03181.html
- http://lkml.iu.edu/hypermail/linux/kernel/1807.2/02790.html
- [2] http://lkml.iu.edu/hypermail/linux/kernel/1808.0/05516.html
- [3] http://lkml.iu.edu/hypermail/linux/kernel/1807.1/03161.html
- [4] https://lwn.net/Articles/762566/ (See "Architecture-specific" changes)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1790688
Title:
x86/pti: 32-bit x86 systems support already available.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790688/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1790688] Re: x86/pti: 32-Bit x86 systems support already available.
Hello. One more thing: since kernel page-table isolation is already available on 32-Bit x86 systems (see Bug Description), maybe "SpectreAndMeltdown" information page (see 1.) should be updated, because of such a statement (see "Current Status"): "No fix is currently available for Meltdown on 32-bit x86; moving to a 64-bit kernel is the currently recommended mitigation." Maybe, it could be changed to note, that: "32-bit x86 finally have kernel page-table isolation support to mitigate "Meltdown". It is already available in Linux kernel v4.19". Or above statement, available on "SpectreAndMeltdown" page, could be changed to: "Fix/mitigation for Meltdown on 32-bit x86 is already available in Linux v4.19 kernel". But that's just my opinion. Best regards. __ 1. https://wiki.ubuntu.com/SecurityTeam/KnowledgeBase/SpectreAndMeltdown#Current_Status -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1790688 Title: x86/pti: 32-Bit x86 systems support already available. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790688/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1790688] Re: x86/pti: 32-Bit x86 systems support already available.
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1790688 Title: x86/pti: 32-Bit x86 systems support already available. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790688/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1790688] [NEW] x86/pti: 32-Bit x86 systems support already available.
Public bug reported:
Hello.
Linux kernel v4.19 release candidate [1], finally have kernel page-table
isolation ('PTI', previously known as 'KAISER') support for x86_32
architecture. As we know, 'PTI' provides protection against attack,
known as the "Meltdown" (CVE-2017-5754), that breaks isolation between
user applications and the operating system etc. However, kernel page-
table isolation wasn't available on 32-Bit x86 systems. Until now.
So, I would like to ask a question: are there any plans to backport
kernel page-table isolation patches for Linux kernels available in
"Trusty"/14.04, "Xenial"/16.04 and "Bionic"/18.04 releases etc.? I mean
x86_32 bit architecture, of course. I'm asking, because it seems, that
pretty much no developers run 32-bit any more. However, there still are
many 32-bit users out there.
For more informations about how 'PTI' was implementing on 32-Bit x86
architecture, plase check - for example - commit '7757d607c6b31'
("x86/pti: Allow CONFIG_PAGE_TABLE_ISOLATION for x86_32"). Here are
messages about 'PTI' support (PATCH v7, v8) for x86_32 [1]. Next, 'PTI'
fixes for x86-32 [2] and more patches related to 'x86/mm/pti' [3]. There
is also a short report for the first half of the 4.19 kernel merge
window [4].
I'm sorry for such a long message, but I'm very happy that 'PTI' support
is already available for x86_32 architecture and I hope, that it will be
backported to all Ubuntu LTS releases etc.
Thanks, best regards.
__
[1] http://lkml.iu.edu/hypermail/linux/kernel/1807.1/03578.html (please see
every next patches etc.)
http://lkml.iu.edu/hypermail/linux/kernel/1807.1/03181.html
http://lkml.iu.edu/hypermail/linux/kernel/1807.2/02790.html
[2] http://lkml.iu.edu/hypermail/linux/kernel/1808.0/05516.html
[3] http://lkml.iu.edu/hypermail/linux/kernel/1807.1/03161.html
[4] https://lwn.net/Articles/762566/ (See "Architecture-specific" changes)
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Incomplete
** Tags: i386 meltdown pti spectre x86-32
** Description changed:
Hello.
Linux kernel v4.19 release candidate [1], finally have kernel page-table
isolation ('PTI', previously known as 'KAISER') support for x86_32
architecture. As we know, 'PTI' provides protection against attack,
known as the "Meltdown" (CVE-2017-5754), that breaks isolation between
user applications and the operating system etc. However, kernel page-
table isolation wasn't available on 32-Bit x86 systems. Until now.
So, I would like to ask a question: are there any plans to backport
kernel page-table isolation patches for Linux kernels available in
"Trusty"/14.04, "Xenial"/16.04 and "Bionic"/18.04 releases etc.? I mean
x86_32 bit architecture, of course. I'm asking, because it seems, that
pretty much no developers run 32-bit any more. However, there still are
many 32-bit users out there.
- For more informations about how 'PTI' implementing on 32-Bit x86
+ For more informations about how 'PTI' was implementing on 32-Bit x86
architecture looks like, plase check - for example - commit
'7757d607c6b31' ("x86/pti: Allow CONFIG_PAGE_TABLE_ISOLATION for
x86_32"). Here are messages about 'PTI' support (PATCH v7, v8) for
x86_32 [1]. Next, 'PTI' fixes for x86-32 [2] and more patches related to
'x86/mm/pti' [3]. There is also a short report for the first half of the
4.19 kernel merge window [4].
I'm sorry for such a long message, but I'm very happy that 'PTI' support
is already available for x86_32 architecture and I hope, that it will be
backported to all Ubuntu LTS releases etc.
Thanks, best regards.
__
[1] http://lkml.iu.edu/hypermail/linux/kernel/1807.1/03578.html (please see
every next patches etc.)
http://lkml.iu.edu/hypermail/linux/kernel/1807.1/03181.html
http://lkml.iu.edu/hypermail/linux/kernel/1807.2/02790.html
[2] http://lkml.iu.edu/hypermail/linux/kernel/1808.0/05516.html
[3] http://lkml.iu.edu/hypermail/linux/kernel/1807.1/03161.html
[4] https://lwn.net/Articles/762566/ (See "Architecture-specific" changes)
** Description changed:
Hello.
Linux kernel v4.19 release candidate [1], finally have kernel page-table
isolation ('PTI', previously known as 'KAISER') support for x86_32
architecture. As we know, 'PTI' provides protection against attack,
known as the "Meltdown" (CVE-2017-5754), that breaks isolation between
user applications and the operating system etc. However, kernel page-
table isolation wasn't available on 32-Bit x86 systems. Until now.
So, I would like to ask a question: are there any plans to backport
kernel page-table isolation patches for Linux kernels available in
"Trusty"/14.04, "Xenial"/16.04 and "Bionic"/18.04 releases etc.? I mean
x86_32 bit architecture, of course. I'm asking, because it seems, that
pretty much no developers run 32-bit any more. However, there still are
many 32-bit users out there.
For more
[Bug 1780846] Re: After update 2018-07-08 menus and buttons are behaving badly
@Timo, I am using Intel HD Graphics and no longer experience issues as described in this report. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1780846 Title: After update 2018-07-08 menus and buttons are behaving badly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1780846/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1780846] Re: After update 2018-07-08 menus and buttons are behaving badly
Daniel, the KDE menu bar colour problem I experienced and noted in bug #1780664 also went away when I upgraded to the new xorg-server. I had to reboot and upgrade all my packages twice in order to get the latest. You might try checking to ensure that you have all the latest packages. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1780846 Title: After update 2018-07-08 menus and buttons are behaving badly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1780846/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1780846] Re: After update 2018-07-08 menus and buttons are behaving badly
Daniel, can you try rebooting your computer or otherwise restarting the xserver and then re-testing? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1780846 Title: After update 2018-07-08 menus and buttons are behaving badly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1780846/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1780664] Re: Recent libgl-mesa graphics update prevents drop down list menu appearing in apps like firefox three line/bar menu icon
Hi Timo, To test I removed the package holds, updated and upgraded to current released packages, and then rebooted. At this point I confirmed the issue in the original report. Next I enabled the xenial-proposed repository, updated and then installed the following two packages: sudo apt install xserver-common/xenial-proposed xserver-xorg-core /xenial-proposed Then I rebooted. After reboot I confirmed that these proposed xenial packages did indeed fix the issue. I was once again able to click on the three line/bar icon in Firefox and see the drop down menu list display. I also confirmed that there were no regressions in my testing (no SDDM hang on login, and no screen tearing). Following is the output you requested earlier. $ apt-cache policy xserver-xorg-core xserver-xorg-core: Installed: 2:1.18.4-0ubuntu0.8 Candidate: 2:1.18.4-0ubuntu0.8 Version table: *** 2:1.18.4-0ubuntu0.8 400 400 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 Packages 100 /var/lib/dpkg/status 2:1.18.4-0ubuntu0.7 500 500 http://ca.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 2:1.18.3-1ubuntu2 500 500 http://ca.archive.ubuntu.com/ubuntu xenial/main amd64 Packages $ Thank you very much for fixing this problem and seeing it through to xenial-proposed. If there is any more steps you need me to take to get this into an official release package then please let me know. Sincerely, Curtis Gedak ** Tags removed: verification-needed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1780664 Title: Recent libgl-mesa graphics update prevents drop down list menu appearing in apps like firefox three line/bar menu icon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1780664/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
