[Bug 2066359] [NEW] package firmware-b43-installer 1:019-11build1 failed to install/upgrade: le sous-processus paquet firmware-b43-installer script post-installation installé a renvoyé un état de sort
Public bug reported: said my installation was uncomplete ProblemType: Package DistroRelease: Ubuntu 24.04 Package: firmware-b43-installer 1:019-11build1 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed May 22 13:12:48 2024 ErrorMessage: le sous-processus paquet firmware-b43-installer script post-installation installé a renvoyé un état de sortie d'erreur 1 InstallationDate: Installed on 2023-10-20 (215 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) PackageArchitecture: all Python3Details: /usr/bin/python3.12, Python 3.12.3, python3-minimal, 3.12.3-0ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.22.6ubuntu6 apt 2.7.14build2 SourcePackage: b43-fwcutter Title: package firmware-b43-installer 1:019-11build1 failed to install/upgrade: le sous-processus paquet firmware-b43-installer script post-installation installé a renvoyé un état de sortie d'erreur 1 UpgradeStatus: Upgraded to noble on 2024-05-22 (0 days ago) ** Affects: b43-fwcutter (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066359 Title: package firmware-b43-installer 1:019-11build1 failed to install/upgrade: le sous-processus paquet firmware-b43-installer script post-installation installé a renvoyé un état de sortie d'erreur 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/b43-fwcutter/+bug/2066359/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066360] [NEW] package firmware-b43-installer 1:019-11build1 failed to install/upgrade: le sous-processus paquet firmware-b43-installer script post-installation installé a renvoyé un état de sort
Public bug reported: said my installation was uncomplete ProblemType: Package DistroRelease: Ubuntu 24.04 Package: firmware-b43-installer 1:019-11build1 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed May 22 13:12:48 2024 ErrorMessage: le sous-processus paquet firmware-b43-installer script post-installation installé a renvoyé un état de sortie d'erreur 1 InstallationDate: Installed on 2023-10-20 (215 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) PackageArchitecture: all Python3Details: /usr/bin/python3.12, Python 3.12.3, python3-minimal, 3.12.3-0ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.22.6ubuntu6 apt 2.7.14build2 SourcePackage: b43-fwcutter Title: package firmware-b43-installer 1:019-11build1 failed to install/upgrade: le sous-processus paquet firmware-b43-installer script post-installation installé a renvoyé un état de sortie d'erreur 1 UpgradeStatus: Upgraded to noble on 2024-05-22 (0 days ago) ** Affects: b43-fwcutter (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066360 Title: package firmware-b43-installer 1:019-11build1 failed to install/upgrade: le sous-processus paquet firmware-b43-installer script post-installation installé a renvoyé un état de sortie d'erreur 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/b43-fwcutter/+bug/2066360/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061382] [NEW] cups always prints with default olptions
Public bug reported: I have CUPS set to default to 2-sided printing. If, when printing, I select single-sided I still get 2-sided. Currently trying to print from Atril. Each time I want to print I have to check and set the default options. I am running the .deb version, not the snap. Related to #357732? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cups 2.4.1op1-1ubuntu4.8 ProcVersionSignature: Ubuntu 5.15.0-101.111-generic 5.15.143 Uname: Linux 5.15.0-101-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Mon Apr 15 12:40:47 2024 InstallationDate: Installed on 2020-09-17 (1305 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lpstat: device for Brother_HL_L8260CDW_series: implicitclass://Brother_HL_L8260CDW_series/ device for Brother_HL_L8260CDW_series@BRWD46A6A5387E2.local: implicitclass://Brother_HL_L8260CDW_series%40BRWD46A6A5387E2.local/ device for PDF: cups-pdf:/ MachineType: LENOVO 20BSCTO1WW Papersize: a4 PpdFiles: Brother_HL_L8260CDW_series: HL-L8260CDW series - IPP Everywhere PDF: Generic CUPS-PDF Printer (w/ options) Brother_HL_L8260CDW_series@BRWD46A6A5387E2.local: Brother HL-L8260CDW series, driverless, cups-filters 1.28.15 ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-101-generic root=/dev/mapper/vgxubuntu-root ro quiet splash vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: cups UpgradeStatus: Upgraded to jammy on 2022-10-30 (532 days ago) dmi.bios.date: 07/14/2016 dmi.bios.release: 1.14 dmi.bios.vendor: LENOVO dmi.bios.version: N14ET36W (1.14 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BSCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnLENOVO:bvrN14ET36W(1.14):bd07/14/2016:br1.14:efr1.9:svnLENOVO:pn20BSCTO1WW:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BSCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20BS_BU_Think_FM_ThinkPadX1Carbon3rd: dmi.product.family: ThinkPad X1 Carbon 3rd dmi.product.name: 20BSCTO1WW dmi.product.sku: LENOVO_MT_20BS_BU_Think_FM_ThinkPad X1 Carbon 3rd dmi.product.version: ThinkPad X1 Carbon 3rd dmi.sys.vendor: LENOVO ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061382 Title: cups always prints with default olptions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/2061382/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893781] Re: xfce4-screensaver shows desktop and no login screen when waking from suspend
Similar. New install early Feb 2024 xubuntu 22.04 On opening the lid the screen is clearly locked. If I type the password into the invisible input box it unlocks properly. Alternatively ctl- alt-F3, login to the tty, and "pkill -9 screensaver", but then I have to re-enable the screensaver -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893781 Title: xfce4-screensaver shows desktop and no login screen when waking from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-screensaver/+bug/1893781/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967785] [NEW] 22.04 beta preview : parametre/comptes en ligne/google = crash
Public bug reported: ubuntu 22.04 beta en préversion Ubuntu Jammy Jellyfish (development branch) Dans parametre/comptes en ligne/google = crash (impossible de se connecter !) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.8 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Mon Apr 4 19:08:50 2022 InstallationDate: Installed on 2021-07-25 (253 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210725) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to jammy on 2022-04-04 (0 days ago) mtime.conffile..etc.update-manager.release-upgrades: 2022-04-04T18:12:39.161655 ** Affects: ubuntu Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade jammy wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967785 Title: 22.04 beta preview : parametre/comptes en ligne/google = crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1967785/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964488] Re: Qemu fails with daemonize and enabled elevateprivileges
Thanks Christian for your quick answer! I just stumbled across a similar issue (https://gitlab.com/qemu- project/qemu/-/issues/798) which got closed with 'intended behavior'. This issue can be closed, I guess. ** Bug watch added: gitlab.com/qemu-project/qemu/-/issues #798 https://gitlab.com/qemu-project/qemu/-/issues/798 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964488 Title: Qemu fails with daemonize and enabled elevateprivileges To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1964488/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964488] Re: Qemu fails with daemonize and enabled elevateprivileges
** Description changed: Qemu fails silently with exit code 1 when using daemonize and the sandbox option elevateprivileges=deny. This behavior got introduced by 0546c0609cb5a8d90c1cbac8e0d64b5a048bbb19 where the sandbox options gets parsed and enforced *before* daemonizing. Since the os_daemonize libc- call uses the syscall setsid, qemu gets killed by the signal 13 (SIGSYS). + + The documentation + (https://qemu.readthedocs.io/en/latest/system/security.html#isolation- + mechanisms) states that sanboxing "[...] disables system calls that are + not needed by QEMU[...]", but setsid obviously is needed. What I expected: - a hint in the documentation of the flags that elevateprivileges AND daemonize contradict -or- - working combination Reproducer: $ qemu-system-x86_64 -sandbox on,elevateprivileges=deny -daemonize Package: 1:6.2+dfsg-2ubuntu5 Ubuntu Version: 22.04 (Jammy Jellyfish) dmesg: [ 181.064898] audit: type=1326 audit(1646924855.830:13): auid=0 uid=0 gid=0 ses=1 subj=? pid=3622 comm="qemu-system-x86" exe="/usr/bin/qemu-system-x86_64" sig=31 arch=c03e syscall=112 compat=0 ip=0x7f725964f40b code=0x8000 Coredump: PID: 4402 (qemu-system-x86) UID: 0 (root) GID: 0 (root) Signal: 31 (SYS) Timestamp: Thu 2022-03-10 15:10:37 UTC (37s ago) Command Line: qemu-system-x86_64 -sandbox on,elevateprivileges=deny -daemonize Executable: /usr/bin/qemu-system-x86_64 Control Group: /user.slice/user-0.slice/session-1.scope Unit: session-1.scope Slice: user-0.slice Session: 1 Owner UID: 0 (root) Boot ID: 3cdf72ff261640e3a3f9e887d159bb2a Machine ID: 72874f2d047d4c87887abbc727924413 Hostname: raphael-20220310-145731 Storage: /var/lib/systemd/coredump/core.qemu-system-x86.0.3cdf72ff261640e3a3f9e887d159bb2a.4402.164692503700.zst (present) Disk Size: 405.6K Message: Process 4402 (qemu-system-x86) of user 0 dumped core. Found module linux-vdso.so.1 with build-id: aea445f382fbc134b3bc979d61dd291e78bea882 Found module libcrypto.so.3 with build-id: 16bbb788a98f53a5cd5ce19936946a279603f77a Found module liblzma.so.5 with build-id: 3eeacec54c1e109d7486961e9b56c01023dd492e Found module libpcre2-8.so.0 with build-id: 730c613f1746c1ddfca8a4420385ac363e86e2a2 Found module libblkid.so.1 with build-id: cdf95a964e3302bb356fefc4b801fae8c4340b31 Found module libkmod.so.2 with build-id: c8ac4bc8d0fe03ceb8cad8d24484c5cbad9daf5a Found module libuuid.so.1 with build-id: 64c0d0cb22fa2bdeca075a0c0418ba5ff314b220 Found module libnl-route-3.so.200 with build-id: 0d1ec15c789fe7cc860df8d8d2004a6c7b03c2a3 Found module libnl-3.so.200 with build-id: 63256316bd1135d4745d740781b42ca55f77a24f Found module libpcre.so.3 with build-id: 56ddb828685e501f1498130d1cc7f51c242554c1 Found module libffi.so.8 with build-id: 59c2a6b204f74f358ca7711d2dfd349d88711f6a Found module libselinux.so.1 with build-id: 2195967b677f320e35e0cdafe08a4713bc2a95e8 Found module libmount.so.1 with build-id: eeb33f2b4b9c3eb0a29575eb9932ef08663bd836 Found module libdaxctl.so.1 with build-id: f7dfbca3d72bc7ba36d6b60a28119269f2504db2 Found module libndctl.so.6 with build-id: 22fb97cc03c9bc2e81c12c5e1f82973cfea86338 Found module libgmp.so.10 with build-id: f110719303ddbea25a5e89ff730fec520eed67b0 Found module libhogweed.so.6 with build-id: 01a0b20878b525a7a33197fc23b738654682f3c4 Found module libtasn1.so.6 with build-id: efacd0b1b8ccb481fcb501cf76cf07cb2c444d45 Found module libunistring.so.2 with build-id: ca5149da8d5a298b8f286ffca3d6e2402ec0fe01 Found module libidn2.so.0 with build-id: f477d28cad4d54daee0070cd4949f0487ac93afc Found module libp11-kit.so.0 with build-id: 6e579cbca24932056e99bb54557cd5a1234811ea Found module ld-linux-x86-64.so.2 with build-id: c83a452679d23179c2ddd07c5c25d182e54908df Found module libc.so.6 with build-id: 094a2d85f72e893d0c15a66812d51d5493e30860 Found module libgcc_s.so.1 with build-id: 443a1e5dd16a55fd142e5e5fcdc544ba2052dda0 Found module libm.so.6 with build-id: a9832e9d3a777fc99a89d92e359eec6395deca29 Found module libaio.so.1 with build-id: a21eb19f17dd68947804f035aa6c27cd73a70439 Found module libfuse3.so.3 with build-id: d45830188e873e270f28ab91f11e6fc7d7b2159c Found module libnettle.so.8 with build-id: 89ee6d2af3edfaf90640d96b94afcef1e43d74a2 Found module lib
[Bug 1964488] [NEW] Qemu fails with daemonize and enabled elevateprivileges
Public bug reported: Qemu fails silently with exit code 1 when using daemonize and the sandbox option elevateprivileges=deny. This behavior got introduced by 0546c0609cb5a8d90c1cbac8e0d64b5a048bbb19 where the sandbox options gets parsed and enforced *before* daemonizing. Since the os_daemonize libc- call uses the syscall setsid, qemu gets killed by the signal 13 (SIGSYS). What I expected: - a hint in the documentation of the flags that elevateprivileges AND daemonize contradict -or- - working combination Reproducer: $ qemu-system-x86_64 -sandbox on,elevateprivileges=deny -daemonize Package: 1:6.2+dfsg-2ubuntu5 Ubuntu Version: 22.04 (Jammy Jellyfish) dmesg: [ 181.064898] audit: type=1326 audit(1646924855.830:13): auid=0 uid=0 gid=0 ses=1 subj=? pid=3622 comm="qemu-system-x86" exe="/usr/bin/qemu-system-x86_64" sig=31 arch=c03e syscall=112 compat=0 ip=0x7f725964f40b code=0x8000 Coredump: PID: 4402 (qemu-system-x86) UID: 0 (root) GID: 0 (root) Signal: 31 (SYS) Timestamp: Thu 2022-03-10 15:10:37 UTC (37s ago) Command Line: qemu-system-x86_64 -sandbox on,elevateprivileges=deny -daemonize Executable: /usr/bin/qemu-system-x86_64 Control Group: /user.slice/user-0.slice/session-1.scope Unit: session-1.scope Slice: user-0.slice Session: 1 Owner UID: 0 (root) Boot ID: 3cdf72ff261640e3a3f9e887d159bb2a Machine ID: 72874f2d047d4c87887abbc727924413 Hostname: raphael-20220310-145731 Storage: /var/lib/systemd/coredump/core.qemu-system-x86.0.3cdf72ff261640e3a3f9e887d159bb2a.4402.164692503700.zst (present) Disk Size: 405.6K Message: Process 4402 (qemu-system-x86) of user 0 dumped core. Found module linux-vdso.so.1 with build-id: aea445f382fbc134b3bc979d61dd291e78bea882 Found module libcrypto.so.3 with build-id: 16bbb788a98f53a5cd5ce19936946a279603f77a Found module liblzma.so.5 with build-id: 3eeacec54c1e109d7486961e9b56c01023dd492e Found module libpcre2-8.so.0 with build-id: 730c613f1746c1ddfca8a4420385ac363e86e2a2 Found module libblkid.so.1 with build-id: cdf95a964e3302bb356fefc4b801fae8c4340b31 Found module libkmod.so.2 with build-id: c8ac4bc8d0fe03ceb8cad8d24484c5cbad9daf5a Found module libuuid.so.1 with build-id: 64c0d0cb22fa2bdeca075a0c0418ba5ff314b220 Found module libnl-route-3.so.200 with build-id: 0d1ec15c789fe7cc860df8d8d2004a6c7b03c2a3 Found module libnl-3.so.200 with build-id: 63256316bd1135d4745d740781b42ca55f77a24f Found module libpcre.so.3 with build-id: 56ddb828685e501f1498130d1cc7f51c242554c1 Found module libffi.so.8 with build-id: 59c2a6b204f74f358ca7711d2dfd349d88711f6a Found module libselinux.so.1 with build-id: 2195967b677f320e35e0cdafe08a4713bc2a95e8 Found module libmount.so.1 with build-id: eeb33f2b4b9c3eb0a29575eb9932ef08663bd836 Found module libdaxctl.so.1 with build-id: f7dfbca3d72bc7ba36d6b60a28119269f2504db2 Found module libndctl.so.6 with build-id: 22fb97cc03c9bc2e81c12c5e1f82973cfea86338 Found module libgmp.so.10 with build-id: f110719303ddbea25a5e89ff730fec520eed67b0 Found module libhogweed.so.6 with build-id: 01a0b20878b525a7a33197fc23b738654682f3c4 Found module libtasn1.so.6 with build-id: efacd0b1b8ccb481fcb501cf76cf07cb2c444d45 Found module libunistring.so.2 with build-id: ca5149da8d5a298b8f286ffca3d6e2402ec0fe01 Found module libidn2.so.0 with build-id: f477d28cad4d54daee0070cd4949f0487ac93afc Found module libp11-kit.so.0 with build-id: 6e579cbca24932056e99bb54557cd5a1234811ea Found module ld-linux-x86-64.so.2 with build-id: c83a452679d23179c2ddd07c5c25d182e54908df Found module libc.so.6 with build-id: 094a2d85f72e893d0c15a66812d51d5493e30860 Found module libgcc_s.so.1 with build-id: 443a1e5dd16a55fd142e5e5fcdc544ba2052dda0 Found module libm.so.6 with build-id: a9832e9d3a777fc99a89d92e359eec6395deca29 Found module libaio.so.1 with build-id: a21eb19f17dd68947804f035aa6c27cd73a70439 Found module libfuse3.so.3 with build-id: d45830188e873e270f28ab91f11e6fc7d7b2159c Found module libnettle.so.8 with build-id: 89ee6d2af3edfaf90640d96b94afcef1e43d74a2 Found module libgmodule-2.0.so.0 with build-id: d64002b7a12e58f579eecf952daeb61435f8f343 Found module liburing.so.2 with build-id: 976771a582fd2e5c62faff76c026b09eaf3335a0 Found module libudev.so.1 with build-id: ffd1278cf71c4c9c09bac7cdefac3d58b9e1d1f8 Found module libslirp.so.0 with build-id: ccb8518051352845e15c5702d534bfb703b683d3 Found
[Bug 1964259] Re: Click and drag not working on MacBook trackpad (bcm5974)
PPS: The driver in question is bcm5974. ** Summary changed: - Click and drag not working on MacBook trackpad + Click and drag not working on MacBook trackpad (bcm5974) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964259 Title: Click and drag not working on MacBook trackpad (bcm5974) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1964259/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964259] Re: Click and drag not working on MacBook trackpad
PS: Unlike what i wrote before, click-dragging with two fingers doesn't work properly: the cursor gets stuck after a while – sometimes immediately, sometimes only after a few seconds. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964259 Title: Click and drag not working on MacBook trackpad To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1964259/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964259] [NEW] Click and drag not working on MacBook trackpad
Public bug reported: Click and drag is not working on a MacBookPro8,1 trackpad. (Oddly enough, dragging with two fingers does work.) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-30-generic 5.13.0-30.33~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Tue Mar 8 20:38:23 2022 InstallationDate: Installed on 2022-03-03 (4 days ago) InstallationMedia: Kubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: Upgraded to focal on 2022-03-08 (0 days ago) ** Affects: linux-signed-hwe-5.13 (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/1964259 Title: Click and drag not working on MacBook trackpad To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1964259/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955131] Re: Cash-flow report fails with exception
Still an issue: Version: 3.8 Build ID: 3.8b+(2019-12-29) Finance::Quote: 1.49 Report error An error occurred while running the report. 18 (apply-smob/1 #) In c-interface.scm: 22:4 17 (gnc:call-with-error-handling _ _) In ice-9/boot-9.scm: 829:9 16 (catch #t # # …) In c-interface.scm: 27:37 15 (_) In unknown file: 14 (eval-string "(gnc:report-run 2)" #) In ice-9/boot-9.scm: 2312:4 13 (save-module-excursion #) In ice-9/eval-string.scm: 38:6 12 (read-and-eval # #:lang _) In report.scm: 776:4 11 (gnc:report-run _) In c-interface.scm: 64:23 10 (gnc:backtrace-if-exception _ . _) 22:4 9 (gnc:call-with-error-handling _ _) In ice-9/boot-9.scm: 829:9 8 (catch #t # # …) In c-interface.scm: 26:40 7 (_) In report.scm: 780:24 6 (_) 756:25 5 (gnc:report-render-html #< type: f8748b813fab4220ba26e…> …) In cash-flow.scm: 200:16 4 (cash-flow-renderer _) In ice-9/boot-9.scm: 222:17 3 (map1 (() # # …)) In cash-flow.scm: 210:21 2 (_ ()) In html-utilities.scm: 35:35 1 (gnc:register-guid "acct-guid=" #f) In unknown file: 0 (string-append "acct-guid=" #f) In procedure string-append: Wrong type (expecting string): #f -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955131 Title: Cash-flow report fails with exception To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnucash/+bug/1955131/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1701788] Re: /usr/bin/plasmashell debug symbols are not provided by plasma-workspace-dbgsym
I feel like these debug symbols should've been installed by default; or at least get the "install" option to actually work. Otherwise it seems detrimental to the project if a user can't properly report their bugs (and telling them to fetch the necessary packages seems user-unfriendly design wise). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1701788 Title: /usr/bin/plasmashell debug symbols are not provided by plasma- workspace-dbgsym To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plasma-workspace/+bug/1701788/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955131] Re: Cash-flow report fails with exception
Added the 2nd attachment as the original form only permitted one attachment. ** Attachment added: "Report spec as saved by gnucash" https://bugs.launchpad.net/ubuntu/+source/gnucash/+bug/1955131/+attachment/5548305/+files/saved-reports-2.8 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955131 Title: Cash-flow report fails with exception To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnucash/+bug/1955131/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955131] [NEW] Cash-flow report fails with exception
Public bug reported: I have had a cash-flow report configured and unchanged for several y ears. Lately it is failing. Gnucash 3.8 No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04.3 LTS Release:20.04 Codename: focal Report output and specification attached ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnucash 1:3.8b-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-91.102-generic 5.4.151 Uname: Linux 5.4.0-91-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Fri Dec 17 12:15:35 2021 InstallationDate: Installed on 2018-02-09 (1407 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: gnucash UpgradeStatus: Upgraded to focal on 2020-10-09 (434 days ago) ** Affects: gnucash (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "Report output" https://bugs.launchpad.net/bugs/1955131/+attachment/5548301/+files/WebKitWebProcess_job__1__ng_non-Linux-generated_files-job_346.pdf -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955131 Title: Cash-flow report fails with exception To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnucash/+bug/1955131/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1935885] [NEW] Mouse stop working
Public bug reported: Hello, since a few days ago my mouse pointer stops to work out of a sudden. I saw that the reasons could be many and I really couldn't find helpful usage on the forums out there. This issue happens from time to time since the first occurrence and I IDK how to proceed. Any guidance is most welcome! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-59-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jul 12 21:57:37 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] (rev c6) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1462:7b84] InstallationDate: Installed on 2021-05-03 (70 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Micro-Star International Co., Ltd. MS-7B84 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-59-generic root=UUID=ab4dade8-974d-455c-9d51-5a51b71ada4d ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/30/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3.10 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A320M PRO-M2 V2 (MS-7B84) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 2.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: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.10:bd01/30/2019:br5.13:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B84:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnA320MPRO-M2V2(MS-7B84):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B84 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 2.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1935885 Title: Mouse stop working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1935885/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874144] Re: Suspends when lid closed despite "do nothing" option after using ext monitor
Still an issue. Kernel 5.4.0-74, -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874144 Title: Suspends when lid closed despite "do nothing" option after using ext monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1874144/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874144] Re: Suspends when lid closed despite "do nothing" option after using ext monitor
Still an issue... ** Changed in: systemd (Ubuntu) Status: Invalid => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874144 Title: Suspends when lid closed despite "do nothing" option after using ext monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1874144/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928342] [NEW] Installer crashed. Apparently due to a lack of free space
Public bug reported: The console of the installer said it couldn't do somthing because of a lack of space, i will try with a new USB key ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.15.10 ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.445.1 CurrentDesktop: ubuntu:GNOME Date: Thu May 13 15:17:08 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) ProcEnviron: LANGUAGE=en_US.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubiquity-20.04.15.10 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928342 Title: Installer crashed. Apparently due to a lack of free space To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1928342/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917336] Re: Mailman does not honour MAILMAN_USER on startup
Added log file ** Attachment added: "/etc/logrotate.d/mailman" https://bugs.launchpad.net/ubuntu/+source/mailman/+bug/1917336/+attachment/5471965/+files/mailman -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917336 Title: Mailman does not honour MAILMAN_USER on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mailman/+bug/1917336/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917341] Re: Thunderbird 78.1 cannot send mail
** Attachment added: "Thunderbid-config.png" https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1917341/+attachment/5471557/+files/Thunderbid-config.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917341 Title: Thunderbird 78.1 cannot send mail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1917341/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917341] [NEW] Thunderbird 78.1 cannot send mail
Public bug reported: I ran update-manager on28 Feb 2020 and rebooted my laptop. Since then I am unable to send mail. Another machine that is still running Thunderbird 68.10 has no problems with exactly the same server settings. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: thunderbird 1:78.7.1+build1-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86 Uname: Linux 5.4.0-66-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BuildID: 20210203182138 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Mon Mar 1 17:40:31 2021 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:732 DefaultProfileThemes: extensions.sqlite corrupt or missing InstallationDate: Installed on 2018-02-09 (1116 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=78.7.1/20210203182138 (In use) SourcePackage: thunderbird UpgradeStatus: Upgraded to focal on 2020-10-09 (143 days ago) ** Affects: thunderbird (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "Thunderbird-error.png" https://bugs.launchpad.net/bugs/1917341/+attachment/5471552/+files/Thunderbird-error.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917341 Title: Thunderbird 78.1 cannot send mail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1917341/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917336] [NEW] Mailman does not honour MAILMAN_USER on startup
Public bug reported: I am running mailman as www-data:list rather than as list:list. After a reboot something keeps resetting the ownership /var/run/mailman from www-data:list to list:list. After each reboot I have to reset/restart manually. All other directories & files are fine. I have hunted all over but I cannot find where this is happening. This is the tail of /etc/mailman/mm_cfg.py: #- # Uncomment if you want to filter mail with SpamAssassin. For # more information please visit this website: # http://www.jamesh.id.au/articles/mailman-spamassassin/ # GLOBAL_PIPELINE.insert(1, 'SpamAssassin') # Note - if you're looking for something that is imported from mm_cfg, but you # didn't find it above, it's probably in /usr/lib/mailman/Mailman/Defaults.py. MAILMAN_USER = 'www-data' ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mailman 1:2.1.29-1ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86 Uname: Linux 5.4.0-66-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Mar 1 17:03:44 2021 InstallationDate: Installed on 2021-01-14 (46 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: mailman UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mailman (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/1917336 Title: Mailman does not honour MAILMAN_USER on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mailman/+bug/1917336/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1913738] Re: aspell-ru seems to make a corrupt ru.cwl
It turns out this is not a bug exactly. ru.cwl is encoded in a different way to cy.cwl. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1913738 Title: aspell-ru seems to make a corrupt ru.cwl To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aspell/+bug/1913738/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1913738] [NEW] aspell-ru seems to make a corrupt ru.cwl
Public bug reported: Full walk through: sudo apt install aspell-ru cp /usr/share/aspell/ru.cwl.gz . gunzip -d ru.cwl.gz word-list-compress d < ru.cwl ERROR: Corrupt Input. The same steps do work with cy.cwl for example so it seems ru.cwl is corrupted. ** Affects: aspell (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/1913738 Title: aspell-ru seems to make a corrupt ru.cwl To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aspell/+bug/1913738/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911836] Re: package linux-image-5.4.0-62-generic 5.4.0-62.70 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Haha yeah that fixed it. Thanks Seth! I marked it private because way more info got uploaded than I was expecting. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1911836 Title: package linux-image-5.4.0-62-generic 5.4.0-62.70 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1911836/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911836] Re: package linux-image-5.4.0-62-generic 5.4.0-62.70 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Haha yeah that fixed it. Thanks Seth! I marked it private because way more info got uploaded than I was expecting. ** Attachment removed: "WifiSyslog.txt" https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1911836/+attachment/5453184/+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/1911836 Title: package linux-image-5.4.0-62-generic 5.4.0-62.70 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1911836/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911835] [NEW] package linux-firmware 1.187.7 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1
*** This bug is a security vulnerability *** Private security bug reported: Upgraded from 18.04 to 20.04 without doing a clean install. Just started encountering issues with updates. I'm not sure if it's related to my encrypted swap which seems to have been broken/unreadable at some point in upgrading. Happy to provide more info. $ lsb_release -rd Description:Ubuntu 20.04.1 LTS Release:20.04 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.7 ProcVersionSignature: Ubuntu 5.4.0-60.67-generic 5.4.78 Uname: Linux 5.4.0-60-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Jan 10 22:02:00 2021 Dependencies: ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 HibernationDevice: RESUME=UUID=b9d6e51c-6ef1-4b05-916a-17aa1a75141c InstallationDate: Installed on 2016-07-02 (1657 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: LENOVO 80K9 PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-60-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 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.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: grub-pc 2.04-1ubuntu26.7 SourcePackage: initramfs-tools Title: package linux-firmware 1.187.7 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2020-12-06 (39 days ago) dmi.bios.date: 07/21/2015 dmi.bios.vendor: Lenovo dmi.bios.version: A9CN61WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Edge 15 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Edge 15 dmi.modalias: dmi:bvnLenovo:bvrA9CN61WW:bd07/21/2015:svnLENOVO:pn80K9:pvrLenovoEdge15:rvnLENOVO:rnLenovoEdge15:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoEdge15: dmi.product.family: IDEAPAD dmi.product.name: 80K9 dmi.product.sku: LENOVO_MT_80K9_BU_idea_FM_Lenovo Edge 15 dmi.product.version: Lenovo Edge 15 dmi.sys.vendor: LENOVO ** Affects: ubuntu Importance: Undecided Status: New ** Tags: amd64 apport-package focal ** Information type changed from Public to Public Security ** 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/1911835 Title: package linux-firmware 1.187.7 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1911835/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911836] [NEW] package linux-image-5.4.0-62-generic 5.4.0-62.70 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
*** This bug is a security vulnerability *** Private security bug reported: Possibly related to https://bugs.launchpad.net/ubuntu/+bug/1911835 These just happened during the same update cycle. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-62-generic 5.4.0-62.70 ProcVersionSignature: Ubuntu 5.4.0-60.67-generic 5.4.78 Uname: Linux 5.4.0-60-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Jan 14 21:19:12 2021 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 HibernationDevice: RESUME=UUID=b9d6e51c-6ef1-4b05-916a-17aa1a75141c InstallationDate: Installed on 2016-07-02 (1657 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: LENOVO 80K9 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-60-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 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.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: grub-pc 2.04-1ubuntu26.7 SourcePackage: initramfs-tools Title: package linux-image-5.4.0-62-generic 5.4.0-62.70 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: Upgraded to focal on 2020-12-06 (39 days ago) dmi.bios.date: 07/21/2015 dmi.bios.vendor: Lenovo dmi.bios.version: A9CN61WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Edge 15 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Edge 15 dmi.modalias: dmi:bvnLenovo:bvrA9CN61WW:bd07/21/2015:svnLENOVO:pn80K9:pvrLenovoEdge15:rvnLENOVO:rnLenovoEdge15:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoEdge15: dmi.product.family: IDEAPAD dmi.product.name: 80K9 dmi.product.sku: LENOVO_MT_80K9_BU_idea_FM_Lenovo Edge 15 dmi.product.version: Lenovo Edge 15 dmi.sys.vendor: LENOVO ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal ** Information type changed from Public 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/1911836 Title: package linux-image-5.4.0-62-generic 5.4.0-62.70 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1911836/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892621] Re: No login screen when waking from sleep
Some more info: This bug affected me on a clean install of Ubuntu 20.04. On upgrading another machine from 18.04 to 20.04 I found that I had both xscreensaver and xfce4-screensaver installed. This caused me to have to do a double unlock each time I wanted to wake the PC. I therefore deleted xscreensaver and got the same problem as on the clean installation, only worse. On the clean installation I could type the unlock password even though unlock-widget was not visible; on the upgraded machine I could not unlock at all. I therefore removed xfce4-screensaver and re-installed xscreensaver. This fixed the problem. I now have two usable systems. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892621 Title: No login screen when waking from sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-power-manager/+bug/1892621/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898844] [NEW] Installation for dual boot with Win10
Public bug reported: grub-efi-amd64-signed package failed to install into /target/. Previous attempt: Executing 'grub-install/dev/sda' failed. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.15.2 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CasperVersion: 1.445.1 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 7 10:13:56 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: LANGUAGE=en_IE.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IE.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubiquity-20.04.15.2 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898844 Title: Installation for dual boot with Win10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1898844/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872108] Re: Bass not on working Lenovo ThinkPad X1 Carbon 7th gen running focal
Same here; the upgrade to alsa-ucm-conf 1.2.2-1ubuntu0.3 alone wasn't enough to fix the issue on my Regolith install (Ubuntu 20.04.1). However, after upgrading I once more tried the fixes described in the following article (essentially the same workarounds that others have suggested in this thread) and this time it worked! Not quite on par with the sound that comes out of the speakers on Win 10, but good enough. https://www.sysorchestra.com/linux-mint-20-upgrade-on-lenovo-thinkpad-x1 -carbon-7th-sound-and-fingerprints/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872108 Title: Bass not on working Lenovo ThinkPad X1 Carbon 7th gen running focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1872108/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892779] Re: Browser will not play videos
I think that this is related to bug #1894102. I suspect that this problem is in the sound system. Today I tried using a wired headset and, while the microphone was working (others on the call could hear me) I could not hear anything. I can play videos only if I have the microphone disabled. As soon as I have a mike connected the video stops. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892779 Title: Browser will not play videos To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1892779/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891402] Re: Bluetooth headset only works as sink
I suspect that this problem is elsewhere in the sound system. Today I tried using a wired headset and, while the microphone was working (others on the call could hear me) I could not hear anything. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891402 Title: Bluetooth headset only works as sink To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/blueman/+bug/1891402/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892779] Re: Browser will not play videos
Immediately after reporting this I tried again to play a video, and this time it worked. After much frustration the problem just disappeared. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892779 Title: Browser will not play videos To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1892779/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892779] [NEW] Browser will not play videos
Public bug reported: I cannot play videos in either firefox or chromium. The video appears to load but then I just get a spinner and nothing happens. I have tried youtube.com, operavision.eu and metopera.org. All fail. I have installed ubuntu-restricted-extras, turned off acceleration in firefox's preferences, and generally tried all the suggestions I can find on the web. Lots of people seem to have this problem. Firefox is 79.0 Chromium is 84.0.4147.105 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 79.0+build1-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: raph 1595 F pulseaudio /dev/snd/controlC0: raph 1595 F pulseaudio /dev/snd/pcmC0D0c: raph 1595 F...m pulseaudio /dev/snd/pcmC0D0p: raph 1595 F...m pulseaudio BuildID: 20200720193547 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: XFCE Date: Mon Aug 24 20:45:02 2020 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:725 DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Installed on 2020-08-09 (15 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.178.1 dev enx3c18a0095fb1 proto dhcp metric 100 default via 192.168.178.1 dev wlp82s0 proto dhcp metric 600 169.254.0.0/16 dev wlp82s0 scope link metric 1000 192.168.178.0/24 dev enx3c18a0095fb1 proto kernel scope link src 192.168.178.30 metric 100 192.168.178.0/24 dev wlp82s0 proto kernel scope link src 192.168.178.32 metric 600 Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:725 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=79.0/20200720193547 (In use) RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/07/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2OET44W (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QTCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2OET44W(1.31):bd05/07/2020:svnLENOVO:pn20QTCTO1WW:pvrThinkPadP1Gen2:rvnLENOVO:rn20QTCTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P1 Gen 2 dmi.product.name: 20QTCTO1WW dmi.product.sku: LENOVO_MT_20QT_BU_Think_FM_ThinkPad P1 Gen 2 dmi.product.version: ThinkPad P1 Gen 2 dmi.sys.vendor: LENOVO ** Affects: firefox (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/1892779 Title: Browser will not play videos To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1892779/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892621] Re: No login screen when waking from sleep
** Attachment added: "Screenshot_2020-08-23_10-55-21.png" https://bugs.launchpad.net/ubuntu/+source/xfce4-power-manager/+bug/1892621/+attachment/5403823/+files/Screenshot_2020-08-23_10-55-21.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892621 Title: No login screen when waking from sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-power-manager/+bug/1892621/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892621] [NEW] No login screen when waking from sleep
Public bug reported: This is similar to, but not identical to #1374830. I am running a Lenovo P1 with an external monitor. Generally the laptop lid is closed and I am relying just on an external monitor, mouse and keyboard. *Sometimes*, when waking the machine from sleep either: a. It does not wake the external monitor at all, or b1. It wakes the external monitor, but all I get is a mouse cursor on a black screen. Letting it time out and invoke the screensaver then enables me to login, or b2. As b1, but the screensaver does not start. I then have to open and shut the laptop lid in order to wake the external monitor properly. This whole behaviour is more common when the sleep has been of long duration, e.g. overnight. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xfce4-power-manager 1.6.6-1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sun Aug 23 10:44:58 2020 InstallationDate: Installed on 2020-08-09 (13 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: xfce4-power-manager UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: xfce4-power-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "Power manager settings" https://bugs.launchpad.net/bugs/1892621/+attachment/5403818/+files/Screenshot_2020-08-23_10-56-02.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892621 Title: No login screen when waking from sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-power-manager/+bug/1892621/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892621] Re: No login screen when waking from sleep
More screenshots ** Attachment added: "Screenshot_2020-08-23_10-55-51.png" https://bugs.launchpad.net/ubuntu/+source/xfce4-power-manager/+bug/1892621/+attachment/5403822/+files/Screenshot_2020-08-23_10-55-51.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892621 Title: No login screen when waking from sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-power-manager/+bug/1892621/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892621] Re: No login screen when waking from sleep
** Attachment added: "Screenshot_2020-08-23_10-56-02.png" https://bugs.launchpad.net/ubuntu/+source/xfce4-power-manager/+bug/1892621/+attachment/5403824/+files/Screenshot_2020-08-23_10-56-02.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892621 Title: No login screen when waking from sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-power-manager/+bug/1892621/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891402] [NEW] Bluetooth headset only works as sink
Public bug reported: I have a bluetooth headset that I use with both Ubuntu 18 and 20. On 18 everything works fine, on two different machines; on 20 I can only use the headset as a sink (no mike). When I try to set it in full headset mode (with mike) using pavucontrol the earphones shut down. The headset is a TaoTronics TT-BH-85 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: blueman 2.1.2-1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Wed Aug 12 22:55:39 2020 InstallationDate: Installed on 2020-08-09 (3 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: blueman UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: blueman (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/1891402 Title: Bluetooth headset only works as sink To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/blueman/+bug/1891402/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1853331] Re: nm-applet assertion failure manipulating widgets
On Tue, 2020-08-04 at 13:14 +, Sebastien Bacher wrote: > @Raphael, it could be that your mirror was not updated yet? > > what is output of > > $ apt policy network-manager-gnome > # apt policy network-manager-gnome network-manager-gnome: Installed: 1.8.10-2ubuntu3 Candidate: 1.8.10-2ubuntu3 Version table: *** 1.8.10-2ubuntu3 500 500 http://gb.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.8.10-2ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853331 Title: nm-applet assertion failure manipulating widgets To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1853331/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1853331] Re: nm-applet assertion failure manipulating widgets
Thank you, but I can't see how to install it. I have deb http://gb.archive.ubuntu.com/ubuntu/ bionic-proposed universe restricted multiverse main in /etc/apt/sources.list and I have run apt-update, but the new version does not appear in synaptic, software-updater or when I do an apt- search On Fri, 2020-07-31 at 12:58 +, Timo Aaltonen wrote: > Hello Raphael, or anyone else affected, > > Accepted network-manager-applet into focal-proposed. The package will > build now and be available at https://launchpad.net/ubuntu/+source > /network-manager-applet/1.8.24-1ubuntu3 in a few hours, and then in > the > -proposed repository. > > Please help us by testing this new package. See > https://wiki.ubuntu.com/Testing/EnableProposed for documentation on > how > to enable and use -proposed. Your feedback will aid us getting this > update out to other Ubuntu users. > > If this package fixes the bug for you, please add a comment to this > bug, > mentioning the version of the package you tested, what testing has > been > performed on the package and change the tag from verification-needed- > focal to verification-done-focal. If it does not fix the bug for you, > please add a comment stating that, and change the tag to > verification- > failed-focal. In either case, without details of your testing we will > not be able to proceed. > > Further information regarding the verification process can be found > at > https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you > in > advance for helping! > > N.B. The updated package will be released to -updates after the > bug(s) > fixed by this package have been verified and the package has been in > -proposed for a minimum of 7 days. > > ** Changed in: network-manager-applet (Ubuntu Focal) >Status: New => Fix Committed > > ** Tags added: verification-needed verification-needed-focal > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853331 Title: nm-applet assertion failure manipulating widgets To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1853331/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1885377] [NEW] installer crashed during installation. not sure if the drive or motherboard are having issues and it can't delete the 500GB partion on the pcie drive.
Public bug reported: I'm not sure what else to add. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.15 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.445 CurrentDesktop: ubuntu:GNOME Date: Sat Jun 27 08:44:15 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash nomodeset --- LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: LANGUAGE=en_US.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubiquity-20.04.15 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1885377 Title: installer crashed during installation. not sure if the drive or motherboard are having issues and it can't delete the 500GB partion on the pcie drive. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1885377/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1853331] Re: nm-applet assertion failure manipulatng widgets
I start from xfce4 with other odd apps added. On Tue, 2020-06-16 at 19:16 +, Sebastien Bacher wrote: > Thank you for your bug report. Is that still an issue? Which desktop > environment do you use? (nm-applet isn't used by GNOME) > > ** Changed in: network-manager-applet (Ubuntu) >Importance: Undecided => Low > > ** Changed in: network-manager-applet (Ubuntu) >Status: Confirmed => Incomplete > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853331 Title: nm-applet assertion failure manipulatng widgets To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1853331/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879276] Re: Esata port is dead after boot, impossible to hotplug external drive
no "make" log I guess... Tell me how I can compile any above version by sha, and I can reproduce. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879276 Title: Esata port is dead after boot, impossible to hotplug external drive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879276/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879276] Re: Esata port is dead after boot, impossible to hotplug external drive
done, but I think it's bad again: I only had "good" results, and had to skip some for "make" errors. See log file. What did I wrong? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879276 Title: Esata port is dead after boot, impossible to hotplug external drive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879276/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879276] Re: Esata port is dead after boot, impossible to hotplug external drive
** Attachment added: "KernelBisect-logs" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879276/+attachment/5382141/+files/KernelBisect-logs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879276 Title: Esata port is dead after boot, impossible to hotplug external drive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879276/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879276] Re: Esata port is dead after boot, impossible to hotplug external drive
I tried all 4.16 (1 to 18), none of them work. Should I bisect from 4.16-rc7 to 4.17 or to 4.16.1? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879276 Title: Esata port is dead after boot, impossible to hotplug external drive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879276/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879276] Re: Esata port is dead after boot, impossible to hotplug external drive
ok, I probably missed something. v4.16-rc7 works and v4.17-rc1 doesn't. to be sure: should I bisect between these one? what's the right syntax for version in first: git bisect good / bad $ ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879276 Title: Esata port is dead after boot, impossible to hotplug external drive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879276/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879276] Re: Esata port is dead after boot, impossible to hotplug external drive
sorry, since it said '0 step left' I thought it was over. Last one: f0308d76906a5b65ec4fcc3b133394caa9f00638 is the first bad commit commit f0308d76906a5b65ec4fcc3b133394caa9f00638 (refs/bisect/bad) Merge: 7928b2cbe55b 2f2f2db86d63 Author: Dave Airlie Date: Fri Feb 16 09:23:12 2018 +1000 Merge tag 'drm-intel-next-2018-02-07' of git://anongit.freedesktop.org/drm/drm-intel into drm-next UAPI Changes: - Userspace whitelist register GEN9_SLICE_COMMON_ECO_CHICKEN1 for GLK (Kenneth) - Non-existent PMU counters are not placed to sysfs (Tvrtko) - Add a note to deprecate I915_SET_COLORKEY_NONE and ignore it (Ville) * Intel DDX never ended using it, and implementation was wonky Core Changes: - Moved away from struct timeval into ktime_t in prep for 2038 (Arnd) * Merged the i915 portion through drm-tip, no core dependencies Driver Changes: - Base support for Icelake and Icelake PCH (Anusha, Rodrigo, Mahesh, Paulo, James, Kelvin) - Add AUX-F port support for Cannonlake (Rodrigo) - New DMC firmware for 1.07 Cannonlake (Anusha) * Go to linux-firmware.git to get it - Reject non-cursor planes nearly (3 px) out of screen on GLK/CNL (Imre) - Y/Yf modifiers restored for SKL+ sprites (Ville) - Compressed framebuffer support for sprites (Ville) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879276 Title: Esata port is dead after boot, impossible to hotplug external drive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879276/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879276] Re: Esata port is dead after boot, impossible to hotplug external drive
done latest output: Bissection : 0 révision à tester après ceci (à peu près 1 étape) [2f2f2db86d63605b1f57780ead21d4968e9d0bf3] drm/i915: Update DRIVER_DATE to 20180207 and Log: ~/linux $ git bisect log git bisect start # good: [0adb32858b0bddf4ada5f364a84ed60b196dbcda] Linux 4.16 git bisect good 0adb32858b0bddf4ada5f364a84ed60b196dbcda # bad: [29dcea88779c856c7dc92040a0c01233263101d4] Linux 4.17 git bisect bad 29dcea88779c856c7dc92040a0c01233263101d4 # bad: [97b1255cb27c551d7c3c5c496d787da40772da99] mm,oom_reaper: check for MMF_OOM_SKIP before complaining git bisect bad 97b1255cb27c551d7c3c5c496d787da40772da99 # bad: [bb2407a7219760926760f0448fddf00d625e5aec] Merge tag 'docs-4.17' of git://git.lwn.net/linux git bisect bad bb2407a7219760926760f0448fddf00d625e5aec # bad: [1c7095d2836baafd84e596dd34ba1a1293a4faa9] Merge airlied/drm-next into drm-misc-next git bisect bad 1c7095d2836baafd84e596dd34ba1a1293a4faa9 # bad: [65ad7cac3866f5fa80dcef3e5048a839046d6a46] drm/amd/pp: Refine powerplay instance git bisect bad 65ad7cac3866f5fa80dcef3e5048a839046d6a46 # bad: [5c2ff9a60d2123df1e4ccee363541dd17916ddea] drm/amdgpu: always allocate a PASIDs for each VM v2 git bisect bad 5c2ff9a60d2123df1e4ccee363541dd17916ddea # bad: [f0308d76906a5b65ec4fcc3b133394caa9f00638] Merge tag 'drm-intel-next-2018-02-07' of git://anongit.freedesktop.org/drm/drm-intel into drm-next git bisect bad f0308d76906a5b65ec4fcc3b133394caa9f00638 # good: [10bde236eff901407bdbcad2e605edaf7ba23bdb] drm/i915: Per-engine scratch VMA is mandatory git bisect good 10bde236eff901407bdbcad2e605edaf7ba23bdb # good: [5b364bec5cbfd6c23505952a40150b053ec551d1] drm/i915: Flush ggtt writes through the old fenced vma before changing fences git bisect good 5b364bec5cbfd6c23505952a40150b053ec551d1 # good: [d67c0ac19f9a3d900fbdf84924cb4d3aea934310] drm/i915: reduce indent in pch detection git bisect good d67c0ac19f9a3d900fbdf84924cb4d3aea934310 # good: [a8b66f2c2f3e03b70a5e72cb5034f8aff669bf34] drm/i915/selftests: Flush old resets between engines git bisect good a8b66f2c2f3e03b70a5e72cb5034f8aff669bf34 # good: [2f265fad9756a40c09e3f4dcc62d5d7fa73a9fb2] drm/i915/cmdparser: Check reg_table_count before derefencing. git bisect good 2f265fad9756a40c09e3f4dcc62d5d7fa73a9fb2 # good: [4b6ce6810a5dc0af387a238e8c852e0d3822381f] drm/i915/cnl: WaPipeControlBefore3DStateSamplePattern git bisect good 4b6ce6810a5dc0af387a238e8c852e0d3822381f -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879276 Title: Esata port is dead after boot, impossible to hotplug external drive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879276/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879276] Re: Esata port is dead after boot, impossible to hotplug external drive
** 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/1879276 Title: Esata port is dead after boot, impossible to hotplug external drive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879276/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879276] Re: Esata port is dead after boot, impossible to hotplug external drive
Exactly the same -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879276 Title: Esata port is dead after boot, impossible to hotplug external drive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879276/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879276] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1879276/+attachment/5373339/+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/1879276 Title: Esata port is dead after boot, impossible to hotplug external drive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879276/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879276] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1879276/+attachment/5373346/+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/1879276 Title: Esata port is dead after boot, impossible to hotplug external drive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879276/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879276] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1879276/+attachment/5373338/+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/1879276 Title: Esata port is dead after boot, impossible to hotplug external drive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879276/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879276] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1879276/+attachment/5373341/+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/1879276 Title: Esata port is dead after boot, impossible to hotplug external drive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879276/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879276] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1879276/+attachment/5373337/+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/1879276 Title: Esata port is dead after boot, impossible to hotplug external drive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879276/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879276] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1879276/+attachment/5373334/+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/1879276 Title: Esata port is dead after boot, impossible to hotplug external drive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879276/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879276] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1879276/+attachment/5373343/+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/1879276 Title: Esata port is dead after boot, impossible to hotplug external drive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879276/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879276] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1879276/+attachment/5373342/+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/1879276 Title: Esata port is dead after boot, impossible to hotplug external drive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879276/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879276] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1879276/+attachment/5373335/+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/1879276 Title: Esata port is dead after boot, impossible to hotplug external drive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879276/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879276] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1879276/+attachment/5373336/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879276 Title: Esata port is dead after boot, impossible to hotplug external drive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879276/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879276] Re: Esata port is dead after boot, impossible to hotplug external drive
apport information ** Tags added: apport-collected tara ** Description changed: Esata doesn't work after boot: when hotplug an external drive, nothing happens, no dmesg or syslog. It works perfectly when booting on the external HDD itself, and it mounts after boot if plugging on grub prompt. Works on 4.15.3 + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.14 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: raphael1888 F pulseaudio + /dev/snd/pcmC1D0p: raphael1888 F...m pulseaudio + /dev/snd/controlC0: raphael1888 F pulseaudio + CurrentDesktop: X-Cinnamon + DistroRelease: Linux Mint 19 + HibernationDevice: RESUME=UUID=33415494-1c4c-40d0-ad1b-a02add5f12de + InstallationDate: Installed on 2018-03-17 (793 days ago) + InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171124 + MachineType: TOSHIBA TECRA A50-A + NonfreeKernelModules: nvidia_modeset nvidia + Package: linux (not installed) + ProcFB: 0 i915drmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-51-generic root=UUID=96e69012-5a43-4af5-8b48-244d376f6fc2 ro quiet splash vt.handoff=1 + ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18 + RelatedPackageVersions: + linux-restricted-modules-5.3.0-51-generic N/A + linux-backports-modules-5.3.0-51-generic N/A + linux-firmware1.173.18 + Tags: tara + Uname: Linux 5.3.0-51-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo tty uucp + _MarkForUpload: True + dmi.bios.date: 04/18/2018 + dmi.bios.vendor: TOSHIBA + dmi.bios.version: Version 5.10 + dmi.board.asset.tag: 00 + dmi.board.name: TECRA A50-A + dmi.board.vendor: TOSHIBA + dmi.board.version: Version A0 + dmi.chassis.asset.tag: 00 + dmi.chassis.type: 10 + dmi.chassis.vendor: TOSHIBA + dmi.chassis.version: Version 1.0 + dmi.modalias: dmi:bvnTOSHIBA:bvrVersion5.10:bd04/18/2018:svnTOSHIBA:pnTECRAA50-A:pvrPT641E-00600GS4:rvnTOSHIBA:rnTECRAA50-A:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0: + dmi.product.family: 00 + dmi.product.name: TECRA A50-A + dmi.product.sku: PT641E + dmi.product.version: PT641E-00600GS4 + dmi.sys.vendor: TOSHIBA ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1879276/+attachment/537/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879276 Title: Esata port is dead after boot, impossible to hotplug external drive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879276/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879276] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1879276/+attachment/5373347/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879276 Title: Esata port is dead after boot, impossible to hotplug external drive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879276/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879276] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1879276/+attachment/5373344/+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/1879276 Title: Esata port is dead after boot, impossible to hotplug external drive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879276/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879276] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1879276/+attachment/5373345/+files/RfKill.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879276 Title: Esata port is dead after boot, impossible to hotplug external drive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879276/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879276] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1879276/+attachment/5373340/+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/1879276 Title: Esata port is dead after boot, impossible to hotplug external drive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879276/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879276] Re: Esata port is dead after boot, impossible to hotplug external drive
** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879276/+attachment/5373303/+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/1879276 Title: Esata port is dead after boot, impossible to hotplug external drive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879276/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879276] [NEW] Esata port is dead after boot, impossible to hotplug external drive
Public bug reported: Esata doesn't work after boot: when hotplug an external drive, nothing happens, no dmesg or syslog. It works perfectly when booting on the external HDD itself, and it mounts after boot if plugging on grub prompt. Works on 4.15.3 ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: esata ** Attachment added: "version.log" https://bugs.launchpad.net/bugs/1879276/+attachment/5373302/+files/version.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879276 Title: Esata port is dead after boot, impossible to hotplug external drive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879276/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875835] Re: Firefox fails to start - says it is already running
After another update today (30Apr2020) and another run of update-manager the problem appears to be gone. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875835 Title: Firefox fails to start - says it is already running To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1875835/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875835] [NEW] Firefox fails to start - says it is already running
Public bug reported: I have just run update-manager (29Apr2020) and restarted the laptop. On restart I get the message 'firefox is already running'. I disabled the apparmor profile for usr.bin.firefox and usr.lib.firefox.firefox and could then run firefox. Ubuntu-bug says that I have modified the apparmor profile, but while I have written new profiles for skype and zoom, I have not touched any pre-installed profiles. So a firefox bug, or an apparmor bug? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: firefox 75.0+build3-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-99.100-generic 4.15.18 Uname: Linux 4.15.0-99-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: raph 3525 F pulseaudio /dev/snd/controlC0: raph 3525 F pulseaudio BuildID: 20200403170909 Channel: Unavailable CurrentDesktop: XFCE Date: Wed Apr 29 09:46:51 2020 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2018-02-09 (809 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Locales: extensions.sqlite corrupt or missing PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:736 PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=75.0/20200403170909 (In use) RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to bionic on 2018-09-12 (594 days ago) dmi.bios.date: 09/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N11ET42W (1.18 ) dmi.board.asset.tag: Not Available dmi.board.name: 20CJS0UU00 dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: R90G3N7R dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN11ET42W(1.18):bd09/13/2017:svnLENOVO:pn20CJS0UU00:pvrThinkPadT550:rvnLENOVO:rn20CJS0UU00:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T550 dmi.product.name: 20CJS0UU00 dmi.product.version: ThinkPad T550 dmi.sys.vendor: LENOVO mtime.conffile..etc.apparmor.d.usr.bin.firefox: 2020-04-25T20:51:24.045158 ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875835 Title: Firefox fails to start - says it is already running To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1875835/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875835] Re: Firefox fails to start - says it is already running
Adding apparmor log ** Attachment added: "Apparmor messages" https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1875835/+attachment/5363318/+files/apparmor.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875835 Title: Firefox fails to start - says it is already running To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1875835/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874144] Re: Suspends when lid closed despite "do nothing" option after using ext monitor
seems related to https://bugs.launchpad.net/ubuntu/+bug/1857761 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874144 Title: Suspends when lid closed despite "do nothing" option after using ext monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1874144/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874144] [NEW] Suspends when lid closed despite "do nothing" option after using ext monitor
Public bug reported: I use "do nothing" (... I guess, "ne rien faire" in french) option on both battery and supply in power manager. It works until I plug an external monitor (DisplayPort), disconnect, then it suspends when closing lid. Changing options changes nothing in /etc/systemd/logind.conf: [Login] #NAutoVTs=6 #ReserveVT=6 #KillUserProcesses=no #KillOnlyUsers= #KillExcludeUsers=root #InhibitDelayMaxSec=5 #HandlePowerKey=poweroff #HandleSuspendKey=suspend #HandleHibernateKey=hibernate #HandleLidSwitch=suspend #HandleLidSwitchDocked=ignore #PowerKeyIgnoreInhibited=no #SuspendKeyIgnoreInhibited=no #HibernateKeyIgnoreInhibited=no #LidSwitchIgnoreInhibited=yes #HoldoffTimeoutSec=30s #IdleAction=ignore #IdleActionSec=30min #RuntimeDirectorySize=10% #RemoveIPC=yes #InhibitorsMax=8192 #SessionsMax=8192 #UserTasksMax=33% Problem appeared after Mint 18 -> 19 upgrade with 'mintupgrade' tool. System: Toshiba Tecra A50-A-130 Linux Mint 19 (= bionic) Cinnamon 3.8.9 5.3.0-46-generic Intel© Core™ i7-4600M CPU @ 2.90GHz × 2 apt-cache policy systemd systemd: Installé : 237-3ubuntu10.39 Candidat : 237-3ubuntu10.39 Table de version : *** 237-3ubuntu10.39 500 500 http://ubuntu.ethz.ch/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 237-3ubuntu10.38 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 237-3ubuntu10 500 500 http://ubuntu.ethz.ch/ubuntu bionic/main amd64 Packages ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874144 Title: Suspends when lid closed despite "do nothing" option after using ext monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1874144/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866832] [NEW] xfce4-power-manager not managing the machine
Public bug reported: I normally run xfce4-screen-saver and xfce4-power-manager with no problems. Within the past couple of weeks, say from Feb 2020, my machines are no longer shutting down the screen or suspending the cpu. To sort out which of the two is causing the problem, on one laptop I killed the screen-saver and on another killed the power-manager. The one with the screen-saver running locked the screen, the one with the power- manager did nothing. lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.4 LTS Release:18.04 Codename: bionic ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xfce4-power-manager 1.6.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-88.88-generic 4.15.18 Uname: Linux 4.15.0-88-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Mar 10 11:41:03 2020 InstallationDate: Installed on 2018-02-09 (759 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: xfce4-power-manager UpgradeStatus: Upgraded to bionic on 2018-09-12 (544 days ago) ** Affects: xfce4-power-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866832 Title: xfce4-power-manager not managing the machine To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-power-manager/+bug/1866832/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1857893] Re: Evolution looping using 100% cpu
** Attachment added: "Evolution using 100% cpu" https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1857893/+attachment/5316505/+files/Evolution_top_2019-12-30_13-53-29.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1857893 Title: Evolution looping using 100% cpu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1857893/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1857893] [NEW] Evolution looping using 100% cpu
Public bug reported: Possibly one bug, possibly two. At any rate there are two symptoms. 1. Evolution is constantly hogging the whole of one CPU. See attached screenshot. 2. Evolution is stuck opening a folder. If I try to cancel the open it just gets stuck in the close. It has been like this for a couple of weeks now. See attached screenshot. Neither coondition is cleared by killing and restarting the process. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: evolution 3.28.5-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 Uname: Linux 4.15.0-70-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Dec 30 13:55:31 2019 InstallationDate: Installed on 2018-02-09 (688 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: evolution UpgradeStatus: Upgraded to bionic on 2018-09-12 (473 days ago) ** Affects: evolution (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Attachment added: "Evolution stuck in 'open'" https://bugs.launchpad.net/bugs/1857893/+attachment/5316501/+files/Evolution_2019-12-30_13-54-36.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1857893 Title: Evolution looping using 100% cpu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1857893/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853328] [NEW] gdm-x-session loops printing its mode lines to syslog
Public bug reported: On waking from, generally a long sleep, my laptop loops in gdm. I get a continuous stream of: Nov 20 15:34:15 X1 /usr/lib/gdm3/gdm-x-session[2674]: (--) modeset(0): HDMI max TMDS frequency 31KHz Nov 20 15:34:16 X1 /usr/lib/gdm3/gdm-x-session[2674]: (II) modeset(0): EDID vendor "HPN", prod id 13450 Nov 20 15:34:16 X1 /usr/lib/gdm3/gdm-x-session[2674]: (II) modeset(0): Using hsync ranges from config file Nov 20 15:34:16 X1 /usr/lib/gdm3/gdm-x-session[2674]: (II) modeset(0): Using vrefresh ranges from config file Nov 20 15:34:16 X1 /usr/lib/gdm3/gdm-x-session[2674]: (II) modeset(0): Printing DDC gathered Modelines: Nov 20 15:34:16 X1 /usr/lib/gdm3/gdm-x-session[2674]: (II) modeset(0): Modeline "2560x1440"x0.0 241.50 2560 2608 2640 2720 1440 1443 1448 1481 +hsync -vsync (88.8 kHz eP) Nov 20 15:34:16 X1 /usr/lib/gdm3/gdm-x-session[2674]: (II) modeset(0): Modeline "1920x1080"x0.0 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.5 kHz e) Nov 20 15:34:16 X1 /usr/lib/gdm3/gdm-x-session[2674]: (II) modeset(0): Modeline "1920x1080"x0.0 148.35 1920 1936 1980 2640 1080 1084 1089 1125 +hsync +vsync (56.2 kHz e) Nov 20 15:34:16 X1 /usr/lib/gdm3/gdm-x-session[2674]: (II) modeset(0): Modeline "1280x720"x0.0 74.25 1280 1390 1430 1650 720 725 730 750 +hsync +vsync (45.0 kHz e) Nov 20 15:34:16 X1 /usr/lib/gdm3/gdm-x-session[2674]: (II) modeset(0): Modeline "2560x1440"x0.0 304.25 2560 2608 2640 2720 1440 1443 1448 1492 +hsync -vsync (111.9 kHz e) Nov 20 15:34:16 X1 /usr/lib/gdm3/gdm-x-session[2674]: (II) modeset(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e) Nov 20 15:34:16 X1 /usr/lib/gdm3/gdm-x-session[2674]: (II) modeset(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e) Nov 20 15:34:16 X1 /usr/lib/gdm3/gdm-x-session[2674]: (II) modeset(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e) Nov 20 15:34:16 X1 /usr/lib/gdm3/gdm-x-session[2674]: (II) modeset(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e) Nov 20 15:34:16 X1 /usr/lib/gdm3/gdm-x-session[2674]: (II) modeset(0): Modeline "1280x1024"x0.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e) Nov 20 15:34:16 X1 /usr/lib/gdm3/gdm-x-session[2674]: (II) modeset(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e) Nov 20 15:34:16 X1 /usr/lib/gdm3/gdm-x-session[2674]: (II) modeset(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e) Nov 20 15:34:16 X1 /usr/lib/gdm3/gdm-x-session[2674]: (II) modeset(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e) Nov 20 15:34:16 X1 /usr/lib/gdm3/gdm-x-session[2674]: (II) modeset(0): Modeline "1920x1080"x60.0 172.80 1920 2040 2248 2576 1080 1081 1084 1118 -hsync +vsync (67.1 kHz e) Nov 20 15:34:16 X1 /usr/lib/gdm3/gdm-x-session[2674]: (II) modeset(0): Modeline "1600x900"x60.0 119.00 1600 1696 1864 2128 900 901 904 932 -hsync +vsync (55.9 kHz e) Nov 20 15:34:16 X1 /usr/lib/gdm3/gdm-x-session[2674]: (II) modeset(0): Modeline "1280x720"x60.0 74.48 1280 1336 1472 1664 720 721 724 746 -hsync +vsync (44.8 kHz e) Nov 20 15:34:16 X1 /usr/lib/gdm3/gdm-x-session[2674]: (II) modeset(0): Modeline "1920x1200"x0.0 154.00 1920 1968 2000 2080 1200 1203 1209 1235 +hsync -vsync (74.0 kHz e) Nov 20 15:34:16 X1 /usr/lib/gdm3/gdm-x-session[2674]: (II) modeset(0): Modeline "1680x1050"x0.0 119.00 1680 1728 1760 1840 1050 1053 1059 1080 +hsync -vsync (64.7 kHz e) Nov 20 15:34:16 X1 /usr/lib/gdm3/gdm-x-session[2674]: (II) modeset(0): Modeline "1440x900"x0.0 88.75 1440 1488 1520 1600 900 903 909 926 +hsync -vsync (55.5 kHz e) Nov 20 15:34:16 X1 /usr/lib/gdm3/gdm-x-session[2674]: (II) modeset(0): Modeline "1280x800"x0.0 71.00 1280 1328 1360 1440 800 803 809 823 +hsync -vsync (49.3 kHz e) Nov 20 15:34:16 X1 /usr/lib/gdm3/gdm-x-session[2674]: (II) modeset(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e) Nov 20 15:34:16 X1 /usr/lib/gdm3/gdm-x-session[2674]: (II) modeset(0): Modeline "1920x1080"x0.0 148.50 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync (56.2 kHz e) Nov 20 15:34:16 X1 /usr/lib/gdm3/gdm-x-session[2674]: (II) modeset(0): Modeline "1280x720"x0.0 74.25 1280 1720 1760 1980 720 725 730 750 +hsync +vsync (37.5 kHz e) Nov 20 15:34:16 X1 /usr/lib/gdm3/gdm-x-session[2674]: (II) modeset(0): Modeline "720x480"x0.0 27.00 720 736 798 858 480 489 495 525 -hsync -vsync (31.5 kHz e) Nov 20 15:34:16 X1 /usr/lib/gdm3/gdm-x-session[2674]: (II) modeset(0): Modeline "720x576"x0.0 27.00 720 732 796 864 576 581 586 625 -hsync -vsync (31.2 kHz e) Nov 20 15:34:16 X1 /usr/lib/gdm3/gdm-x-session[2674]: (II) modeset(0):
[Bug 1853331] [NEW] nm-applet assertion failure manipulatng widgets
Public bug reported: nm-applet is logging a continuous stream of: Nov 20 15:42:54 X1 nm-applet[3092]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed Nov 20 15:42:54 X1 nm-applet[3092]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed Nov 20 15:42:54 X1 nm-applet[3092]: Can't set a parent on widget which has a parent Nov 20 15:44:54 X1 nm-applet[3092]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed Nov 20 15:44:54 X1 nm-applet[3092]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed Nov 20 15:44:54 X1 nm-applet[3092]: Can't set a parent on widget which has a parent Nov 20 15:45:55 X1 nm-applet[3092]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed Nov 20 15:45:55 X1 nm-applet[3092]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed Nov 20 15:45:55 X1 nm-applet[3092]: Can't set a parent on widget which has a parent Nov 20 15:46:40 X1 nm-applet[3092]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed Nov 20 15:46:40 X1 nm-applet[3092]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed Nov 20 15:46:40 X1 nm-applet[3092]: Can't set a parent on widget which has a parent Nov 20 15:46:40 X1 nm-applet[3092]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed Nov 20 15:46:40 X1 nm-applet[3092]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed Nov 20 15:46:40 X1 nm-applet[3092]: Can't set a parent on widget which has a parent Nov 20 15:46:55 X1 nm-applet[3092]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed Nov 20 15:46:55 X1 nm-applet[3092]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed Nov 20 15:46:55 X1 nm-applet[3092]: Can't set a parent on widget which has a parent Nov 20 15:46:55 X1 nm-applet[3092]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed Nov 20 15:46:55 X1 nm-applet[3092]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed Nov 20 15:46:55 X1 nm-applet[3092]: Can't set a parent on widget which has a parent System updated on 19 Nov 2019 lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.3 LTS Release:18.04 Codename: bionic ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager-gnome 1.8.10-2ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 Uname: Linux 4.15.0-70-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 Date: Wed Nov 20 15:48:21 2019 InstallationDate: Installed on 2018-11-06 (379 days ago) InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IpRoute: default via 192.168.178.1 dev enx3c18a0095fb1 proto dhcp metric 100 default via 192.168.178.1 dev wlp4s0 proto dhcp metric 600 192.168.178.0/24 dev enx3c18a0095fb1 proto kernel scope link src 192.168.178.24 metric 100 192.168.178.0/24 dev wlp4s0 proto kernel scope link src 192.168.178.29 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: network-manager-applet UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.14 connected started full enabled enabled enabled enabled enabled ** Affects: network-manager-applet (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853331 Title: nm-applet assertion failure manipulatng widgets To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1853331/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835647] Re: Saned does not start: service is masked
I have just ried this again and it is now working. No changes other than the normal updates. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835647 Title: Saned does not start: service is masked To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1835647/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1577137] Re: saned.service masked and cannot be unmasked
I ave already created a new bug #1835647 On Wed, 2019-07-10 at 00:37 +, Christopher M. Penalver wrote: > Raphael Mankin, as this report is closed, you don't have the same > problem, or root cause (although similar symptom). > > Despite this, if you would like your issue addressed, please provide > necessary debugging information by filing a new report via a > terminal: > ubuntu-bug sane-backends > > Please feel free to subscribe me to it. > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1577137 Title: saned.service masked and cannot be unmasked To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1577137/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835647] [NEW] Saned does not start: service is masked
Public bug reported: I have been running saned for a couple of years on both 16 and 18. Recently it has stopped working with the message that it is masked. I don't use the scanner all that often so I cannot say exactly when it stopped working, certainly in the last few weeks. root@T550:~# systemctl status saned.socket ● saned.socket - saned incoming socket Loaded: loaded (/lib/systemd/system/saned.socket; enabled; vendor preset: ena Active: active (listening) since Fri 2019-07-05 00:03:10 BST; 1min 46s ago Listen: 0.0.0.0:6566 (Stream) Accepted: 0; Connected: 0 Tasks: 0 (limit: 4915) CGroup: /system.slice/saned.socket Jul 05 00:03:10 T550 systemd[1]: Listening on saned incoming socket. root@T550:~# systemctl start saned Failed to start saned.service: Unit saned.service is masked. root@T550:~# service saned start Failed to start saned.service: Unit saned.service is masked. root@T550:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.2 LTS Release:18.04 Codename: bionic ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: sane-utils 1.0.27-1~experimental3ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-52.56-generic 4.15.18 Uname: Linux 4.15.0-52-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Jul 4 23:45:57 2019 InstallationDate: Installed on 2018-02-09 (510 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: sane-backends UpgradeStatus: Upgraded to bionic on 2018-09-12 (294 days ago) ** Affects: sane-backends (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835647 Title: Saned does not start: service is masked To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1835647/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828432] Re: update-notifier crashes on login
Dear all, I seem to have the same problem. Will try to post a backtrace, but for now this may be a first step: update-notifier --debug-misc (update-notifier:5568): dconf-DEBUG: 13:40:22.656: watch_fast: "/com/ubuntu/update-notifier/" (establishing: 0, active: 0) ** (update-notifier:5568): DEBUG: 13:40:22.656: livepatch_check () (update-notifier:5568): GLib-DEBUG: 13:40:22.656: posix_spawn avoided (automatic reaping requested) (fd close requested) (update-notifier:5568): dconf-DEBUG: 13:40:22.657: watch_established: "/com/ubuntu/update-notifier/" (establishing: 1) ** (update-notifier:5568): DEBUG: 13:40:22.658: Name com.canonical.AppMenu.Registrar does not exist on the session bus (update-notifier:5568): dconf-DEBUG: 13:40:22.658: watch_fast: "/org/appmenu/gtk-module/" (establishing: 0, active: 0) (update-notifier:5568): dconf-DEBUG: 13:40:22.658: unwatch_fast: "/org/appmenu/gtk-module/" (active: 0, establishing: 1) (update-notifier:5568): dconf-DEBUG: 13:40:22.658: watch_established: "/org/appmenu/gtk-module/" (establishing: 0) (livepatch-notification:5574): GLib-GIO-DEBUG: 13:40:22.683: _g_io_module_get_default: Found default implementation dconf (DConfSettingsBackend) for ‘gsettings-backend’ (livepatch-notification:5574): dconf-DEBUG: 13:40:22.683: watch_fast: "/org/appmenu/gtk-module/" (establishing: 0, active: 0) (livepatch-notification:5574): dconf-DEBUG: 13:40:22.684: unwatch_fast: "/org/appmenu/gtk-module/" (active: 0, establishing: 1) (livepatch-notification:5574): dconf-DEBUG: 13:40:22.685: watch_established: "/org/appmenu/gtk-module/" (establishing: 0) (livepatch-notification:5574): GLib-GIO-DEBUG: 13:40:22.688: _g_io_module_get_default: Found default implementation gvfs (GDaemonVfs) for ‘gio-vfs’ (livepatch-notification:5574): dconf-DEBUG: 13:40:22.714: watch_fast: "/org/appmenu/gtk-module/" (establishing: 0, active: 0) (livepatch-notification:5574): dconf-DEBUG: 13:40:22.714: unwatch_fast: "/org/appmenu/gtk-module/" (active: 0, establishing: 1) (livepatch-notification:5574): dconf-DEBUG: 13:40:22.714: watch_established: "/org/appmenu/gtk-module/" (establishing: 0) ** (update-notifier:5568): DEBUG: 13:40:24.335: trayapplet_create() ** (update-notifier:5568): DEBUG: 13:40:24.335: tray_applet_ui_ensure: software-update-available (update-notifier:5568): GLib-DEBUG: 13:40:24.340: posix_spawn avoided (fd close requested) ** (update-notifier:5568): DEBUG: 13:40:25.960: trayapplet_create() ** (update-notifier:5568): DEBUG: 13:40:25.960: tray_applet_ui_destroy: hook-notifier ** (update-notifier:5568): DEBUG: 13:40:25.960: trayapplet_create() ** (update-notifier:5568): DEBUG: 13:40:25.960: trayapplet_create() ** (update-notifier:5568): DEBUG: 13:40:27.331: crashreport_check (update-notifier:5568): GLib-DEBUG: 13:40:27.331: posix_spawn avoided (fd close requested) (update-notifier:5568): GLib-DEBUG: 13:40:27.338: posix_spawn avoided (fd close requested) (update-notifier:5568): GLib-DEBUG: 13:40:27.413: posix_spawn avoided (fd close requested) ** (update-notifier:5568): DEBUG: 13:40:27.489: crashreport found running apport now ** (update-notifier:5568): DEBUG: 13:40:27.489: fire up the crashreport tool (update-notifier:5568): GLib-DEBUG: 13:40:27.490: posix_spawn avoided (fd close requested) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828432 Title: update-notifier crashes on login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1828432/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1577137] Re: saned.service masked and cannot be unmasked
I am having the same problem on Ubuntu 18.04. It was working on both 16 and 18 until recently. root@T550:~# systemctl status saned.socket ● saned.socket - saned incoming socket Loaded: loaded (/lib/systemd/system/saned.socket; enabled; vendor preset: ena Active: active (listening) since Fri 2019-07-05 00:03:10 BST; 1min 46s ago Listen: 0.0.0.0:6566 (Stream) Accepted: 0; Connected: 0 Tasks: 0 (limit: 4915) CGroup: /system.slice/saned.socket Jul 05 00:03:10 T550 systemd[1]: Listening on saned incoming socket. root@T550:~# systemctl start saned Failed to start saned.service: Unit saned.service is masked. root@T550:~# service saned start Failed to start saned.service: Unit saned.service is masked. root@T550:~# -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1577137 Title: saned.service masked and cannot be unmasked To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1577137/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1831232] Re: Ubuntu 18.04 won't boot - failed to connect to lvmetad
Further experimentation: root@X1:~# ls /dev/mapper control sda3_crypt root@X1:~# cryptsetup -v open --type plain /dev/sda2 sda2_crypt Enter passphrase for /dev/sda2: Command successful. root@X1:~# ls /dev/mapper control sda2_crypt sda3_crypt root@X1:~# swapon -a swapon: /dev/mapper/sda2_crypt: read swap header failed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1831232 Title: Ubuntu 18.04 won't boot - failed to connect to lvmetad To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831232/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1832646] [NEW] Printing to Brother_HL_L8260CDW_series outputs garbage
Public bug reported: Today I ran the software updater and rebooted. I now find that I am unable to print to Brother_HL_L8260CDW_series printer; all I get is garbage and a lot of wasted paper. I am printing plain text. I have tried printing it from Evolution, Mousepad, and by piping it into lpr. Power cycling the printer does not help. I can print successfully from another PC with a native 18.04 installation (not upgraded from 16.xx). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2.6 ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 Uname: Linux 4.15.0-51-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CupsErrorLog: E [12/Jun/2019:21:31:10 +0100] [Job 96] Print job canceled at printer. E [12/Jun/2019:21:35:13 +0100] [Job 98] Print job canceled at printer. CurrentDesktop: XFCE Date: Wed Jun 12 21:39:03 2019 InstallationDate: Installed on 2018-02-09 (488 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lpstat: device for Brother_HL_L8260CDW_series: ipp://BRN3C2AF4345B8C.local:631/ipp/print device for HPLJ4: socket://192.168.1.3:9100 MachineType: LENOVO 20CJS0UU00 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HPLJ4.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HPLJ4.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-51-generic root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: Upgraded to bionic on 2018-09-12 (272 days ago) dmi.bios.date: 09/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N11ET42W (1.18 ) dmi.board.asset.tag: Not Available dmi.board.name: 20CJS0UU00 dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: R90G3N7R dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN11ET42W(1.18):bd09/13/2017:svnLENOVO:pn20CJS0UU00:pvrThinkPadT550:rvnLENOVO:rn20CJS0UU00:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T550 dmi.product.name: 20CJS0UU00 dmi.product.version: ThinkPad T550 dmi.sys.vendor: LENOVO ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apparmor apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832646 Title: Printing to Brother_HL_L8260CDW_series outputs garbage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1832646/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1831232] Re: Ubuntu 18.04 won't boot - failed to connect to lvmetad
Further to my previous note, trying to unlock the swap partition yields: # udisksctl unlock -b /dev/sda2 Object /org/freedesktop/UDisks2/block_devices/sda2 is not an encrypted device. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1831232 Title: Ubuntu 18.04 won't boot - failed to connect to lvmetad To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831232/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1831232] Re: Ubuntu 18.04 won't boot - failed to connect to lvmetad
If I leave the machine for a while and the exit the shell it boots, but with no swap. I have not discovered anything useful that I can do while in the busybox shell. I have dited /etc/initramfs-tools/conf.d/resume to read RESUME=none as suggested in https://www.reddit.com/r/Ubuntu/comments/a0whdw/failed_to_connect_to_lvmetad_bug_still_exists/ cat /etc/crypttab sda2_crypt UUID=91558a55-9299-492f-b3b7-324fa7d07396 none luks,swap,discard sda3_crypt UUID=04bbb9dd-9c3f-48c9-ad65-617c4030cd8a none luks,discard cat /etc/fstab # /etc/fstab: static file system information. # # Use 'blkid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added and removed. See fstab(5). # # /dev/mapper/sda3_crypt / ext4errors=remount-ro 0 1 # /boot was on /dev/sda1 during installation UUID=bedf1183-2c1a-4271-a983-f4924a87bb09 /boot ext4noatime 0 2 /dev/mapper/sda2_crypt noneswapsw 0 0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1831232 Title: Ubuntu 18.04 won't boot - failed to connect to lvmetad To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831232/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1831232] Re: Ubuntu 18.04 won't boot - failed to connect to lvmetad
** Attachment added: "Photo of my screen during the boot." https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831232/+attachment/5268075/+files/IMG_20190531_161254.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1831232 Title: Ubuntu 18.04 won't boot - failed to connect to lvmetad To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831232/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1831232] [NEW] Ubuntu 18.04 won't boot - failed to connect to lvmetad
Public bug reported: This bug report relates to a machine running 18.04, not the one I am submitting the report from. On 30 May The Software Updater prompted me to update. Included in the update were initramfs components. I now cannot boot the machine. After decrypting the root file system, instead of being prompted for the pass-phrase to decrypt the swap, I get the message "cannot connect to lvmetad: falling back to device scanning". This repeats for a while until I am dropped into a recovery shell of some sort from which I cannot access the root disk. Blocker. My machine is unusable. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-generic 4.15.0.48.50 ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18 Uname: Linux 4.15.0-48-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gdm2433 F pulseaudio raph 8920 F pulseaudio /dev/snd/controlC0: gdm2433 F pulseaudio Date: Fri May 31 12:08:33 2019 HibernationDevice: RESUME=UUID=2538baa4-d43e-4876-8d94-dd3221894bac InstallationDate: Installed on 2018-02-09 (475 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 20CJS0UU00 ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-48-generic root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-48-generic N/A linux-backports-modules-4.15.0-48-generic N/A linux-firmware 1.173.5 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-09-12 (260 days ago) dmi.bios.date: 09/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N11ET42W (1.18 ) dmi.board.asset.tag: Not Available dmi.board.name: 20CJS0UU00 dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: R90G3N7R dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN11ET42W(1.18):bd09/13/2017:svnLENOVO:pn20CJS0UU00:pvrThinkPadT550:rvnLENOVO:rn20CJS0UU00:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T550 dmi.product.name: 20CJS0UU00 dmi.product.version: ThinkPad T550 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1831232 Title: Ubuntu 18.04 won't boot - failed to connect to lvmetad To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831232/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1825841] [NEW] Laptop battery drains while suspend since 18.04 , even in deep sleep (STR)
Public bug reported: Hi, 1) My laptop battery drains very fast while suspend, which prevent using suspend-to-ram as I almost always find the laptop shut down due to battery being empty. I Observed this problem since my upgrade from 16.04 to 18.04 on my Laptop. It's Toshiba Portege. Suspend does work fine but battery drains while suspend; it was working pretty well in Ubuntu 16.04. I suspect a kind of regression in the i915 driver for now, but did not find any evident of this. After a suspend to ram, we can observe a kind of crash in the i915 driver suspend_late code : [ 475.970946] [ cut here ] [ 475.970947] Display power well on [ 475.971009] WARNING: CPU: 0 PID: 7579 at /build/linux-6ZmFRN/linux-4.15.0/drivers/gpu/drm/i915/intel_display.c:8696 assert_can_disable_lcpll+0x3b3/0x480 [i915] [ 475.971010] Modules linked in: rfcomm ccm cmac bnep cdc_mbim uvcvideo cdc_wdm qcserial cdc_ncm usb_wwan usbserial usbnet mii btusb btrtl btbcm videobuf2_vmalloc btintel videobuf2_memops videobuf2_v4l2 videobuf2_core bluetooth videodev media ecdh_generic msr arc4 snd_hda_codec_realtek snd_hda_codec_generic snd_hda_codec_hdmi snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp iwlmvm kvm_intel kvm mac80211 irqbypass snd_seq intel_cstate intel_rapl_perf iwlwifi snd_seq_device snd_timer joydev cfg80211 input_leds serio_raw wmi_bmof snd rtsx_pci_ms memstick lpc_ich shpchp mei_me toshiba_acpi mei soundcore sparse_keymap toshiba_bluetooth industrialio tpm_infineon mac_hid sch_fq_codel parport_pc [ 475.971045] ppdev lp parport ip_tables x_tables autofs4 algif_skcipher af_alg dm_crypt i915 crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc rtsx_pci_sdmmc i2c_algo_bit aesni_intel aes_x86_64 crypto_simd glue_helper cryptd psmouse drm_kms_helper syscopyarea ahci sysfillrect libahci sysimgblt e1000e fb_sys_fops drm rtsx_pci ptp pps_core video wmi [ 475.971062] CPU: 0 PID: 7579 Comm: kworker/u16:7 Not tainted 4.15.0-47-generic #50-Ubuntu [ 475.971063] Hardware name: TOSHIBA PORTEGE Z30-B/PORTEGE Z30-B, BIOS Version 3.20 04/09/2015 [ 475.971066] Workqueue: events_unbound async_run_entry_fn [ 475.971087] RIP: 0010:assert_can_disable_lcpll+0x3b3/0x480 [i915] [ 475.971088] RSP: 0018:a96642bbfd00 EFLAGS: 00010286 [ 475.971089] RAX: RBX: 9bf98b0a8000 RCX: bca62768 [ 475.971090] RDX: bca62768 RSI: 0082 RDI: 0202 [ 475.971091] RBP: a96642bbfd20 R08: R09: 0015 [ 475.971091] R10: 0600 R11: 0340 R12: 9bf98b0a8358 [ 475.971092] R13: 9bf98b0a8368 R14: c0580baf R15: [ 475.971093] FS: () GS:9bf9a140() knlGS: [ 475.971094] CS: 0010 DS: ES: CR0: 80050033 [ 475.971095] CR2: 7fb1afffeeb6 CR3: 00011e20a005 CR4: 003606f0 [ 475.971096] Call Trace: [ 475.971117] hsw_enable_pc8+0x87/0x310 [i915] [ 475.971129] i915_drm_suspend_late+0xdb/0x140 [i915] [ 475.971141] i915_pm_suspend_late+0x20/0x30 [i915] [ 475.971143] pm_generic_suspend_late+0x2e/0x40 [ 475.971145] pci_pm_suspend_late+0x31/0x40 [ 475.971147] dpm_run_callback+0x5a/0x150 [ 475.971149] ? pci_pm_poweroff_late+0x40/0x40 [ 475.971151] __device_suspend_late+0xc6/0x1d0 [ 475.971152] async_suspend_late+0x1f/0xa0 [ 475.971154] async_run_entry_fn+0x3c/0x150 [ 475.971156] process_one_work+0x1de/0x410 [ 475.971158] worker_thread+0x32/0x410 [ 475.971160] kthread+0x121/0x140 [ 475.971161] ? process_one_work+0x410/0x410 [ 475.971163] ? kthread_create_worker_on_cpu+0x70/0x70 [ 475.971166] ret_from_fork+0x35/0x40 [ 475.971167] Code: d5 ff 48 8b 83 18 07 00 00 e9 b0 fd ff ff 89 ce 4c 89 f7 e8 90 fc 1a fb 0f 0b e9 99 fc ff ff 48 c7 c7 c9 0b 58 c0 e8 7d fc 1a fb <0f> 0b e9 b5 fc ff ff 48 c7 c7 7a 0c 58 c0 e8 6a fc 1a fb 0f 0b [ 475.971192] ---[ end trace 91209fe53f0c0cc2 ]--- By using a more recent kernel (4.18), I get a crash in the pc8 disable function. I am not sure whether this thread backtrace is responsible for the battery drain or not. I also read Intel open source site to help debug this, without success for now : * https://01.org/blogs/rzhang/2015/best-practice-debug-linux-suspend/hibernate-issues The analyze_suspend.py script produced some bunch of data, if anyone needs them to understand what's happening while system is suspended, I can publish them. Other sources of information I consulted : * https://askubuntu.com/questions/1072066/sleep-mode-drains-battery- very-fast * https://www.reddit.com/r/Dell/comments/8b6eci/xp_13_9370_battery_drain_while_suspended/ I confirm my system is going to "deep" sleep and not "s2idle" sleep mode, which would explain the battery drain... Other information : Description:Ubuntu 18.04.1 LTS Release:
[Bug 1721909] Re: Goodix GF3208 (fingerprint reader) not being recognised by lsusb(usbutils)
@vicamo what can we do to help figure this thing out? We have a ton of Dells with this sensor in our company running Ubuntu and could really benefit from this fingerprint reader. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1721909 Title: Goodix GF3208 (fingerprint reader) not being recognised by lsusb(usbutils) To manage notifications about this bug go to: https://bugs.launchpad.net/usbutils/+bug/1721909/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1790000] Re: package libsdl2-2.0-0 2.0.8+1 failed to install/upgrade: tentative de remplacement de « /usr/share/doc/libsdl2-2.0-0/copyright », qui est différent d'autres instances du paquet libsd
Unfortunately I can't because I have reinstalled my PC so I don't have the issue anymore -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/179 Title: package libsdl2-2.0-0 2.0.8+1 failed to install/upgrade: tentative de remplacement de « /usr/share/doc/libsdl2-2.0-0/copyright », qui est différent d'autres instances du paquet libsdl2-2.0-0:amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsdl2/+bug/179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1799988] Re: Missing wifi and bluetooth after sleep on XPS 9370
I'll gladly try any patches, if that would be helpful to you. I do however not use ubuntu, so the kernel in #50 is not really an option. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1799988 Title: Missing wifi and bluetooth after sleep on XPS 9370 To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1799988/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1799988] Re: Missing wifi and bluetooth after sleep on XPS 9370
I'm now running the patches against 4.20.7 with firmware=RM.4.4.1.c2-00057-QCARMSWP-1 and I'm seeing some issues in the log after resume, however the wifi does work fine. Feb 09 08:13:21 hostname kernel: ACPI: Waking up from system sleep state S3 Feb 09 08:13:21 hostname kernel: ACPI: EC: interrupt unblocked Feb 09 08:13:21 hostname kernel: ACPI: EC: event unblocked Feb 09 08:13:21 hostname kernel: ath10k_pci :02:00.0: unsupported HTC service id: 1536 Feb 09 08:13:21 hostname kernel: ath10k_pci :02:00.0: Unknown eventid: 118809 Feb 09 08:13:21 hostname kernel: WARNING: CPU: 2 PID: 26770 at drivers/net/wireless/ath/ath10k/mac.c:5650 ath10k_bss_info_changed+0xe8e/0xfd0 [ath10k_core] Feb 09 08:13:21 hostname kernel: Modules linked in: cmac rfcomm bnep btusb btrtl btbcm btintel bluetooth ecdh_generic ath10k_pci ath10k_core mac80211 ath cfg80211 thunderbolt fuse ccm xt_CHECKSUM ipt_MASQUERADE tun bridge stp llc devlink nf_conntrack_netbios_ns nf_conntrack_broadcast xt_CT ip6t_rpfilter ip6t_REJECT nf_reject_ipv6 xt_conntrack ebtable_nat ip6table_nat nf_nat_ipv6 ip6table_mangle ip6table_raw ip6table_security iptable_nat nf_nat_ipv4 nf_nat iptable_mangle iptable_raw iptable_security nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c ip_set nfnetlink ebtable_filter ebtables ip6table_filter ip6_tables sunrpc vfat fat arc4 hid_multitouch snd_hda_codec_hdmi snd_soc_skl snd_soc_hdac_hda snd_hda_ext_core snd_soc_skl_ipc snd_soc_sst_ipc snd_soc_sst_dsp snd_soc_acpi_intel_match snd_soc_acpi snd_soc_core snd_hda_codec_realtek intel_rapl snd_hda_codec_generic snd_compress x86_pkg_temp_thermal intel_powerclamp ac97_bus iTCO_wdt coretemp snd_pcm_dmaengine dell_laptop iTCO_vendor_support mei_wdt kvm_intel Feb 09 08:13:21 hostname kernel: snd_hda_intel intel_cstate snd_hda_codec snd_hda_core snd_hwdep intel_uncore snd_seq intel_rapl_perf snd_seq_device snd_pcm dell_wmi uvcvideo dell_smbios joydev videobuf2_vmalloc dcdbas snd_timer videobuf2_memops videobuf2_v4l2 snd videobuf2_common wmi_bmof dell_wmi_descriptor intel_wmi_thunderbolt videodev soundcore rtsx_pci_ms mei_me cdc_acm memstick i2c_i801 media idma64 mei rfkill processor_thermal_device intel_lpss_pci ucsi_acpi typec_ucsi intel_lpss intel_soc_dts_iosf intel_pch_thermal typec intel_hid sparse_keymap int3403_thermal int3400_thermal int340x_thermal_zone acpi_thermal_rel pcc_cpufreq acpi_pad dm_crypt hid_logitech_hidpp hid_logitech_dj i915 r8152 mii kvmgt mdev vfio kvm rtsx_pci_sdmmc irqbypass mmc_core i2c_algo_bit drm_kms_helper crct10dif_pclmul crc32_pclmul crc32c_intel drm nvme ghash_clmulni_intel serio_raw rtsx_pci wmi i2c_hid nvme_core video pinctrl_sunrisepoint pinctrl_intel [last unloaded: cfg80211] Feb 09 08:13:21 hostname kernel: CPU: 2 PID: 26770 Comm: kworker/u16:1 Tainted: GW 4.20.7-201.0001_fix_ath10k_sleep_wake_issue.patch.fc29.x86_64 #1 Feb 09 08:13:21 hostname kernel: Hardware name: Dell Inc. XPS 13 9370/0F6P3V, BIOS 1.6.3 11/04/2018 Feb 09 08:13:21 hostname kernel: Workqueue: events_unbound async_run_entry_fn Feb 09 08:13:21 hostname kernel: RIP: 0010:ath10k_bss_info_changed+0xe8e/0xfd0 [ath10k_core] Feb 09 08:13:21 hostname kernel: Code: 89 c1 89 f2 4c 89 d7 48 c7 c6 80 ae 04 c1 4c 89 4c 24 10 89 44 24 08 e8 c0 36 00 00 8b 44 24 08 4c 8b 4c 24 10 e9 22 f8 ff ff <0f> 0b e9 7a f4 ff ff 8b b3 70 01 00 00 89 f2 89 c1 48 c7 c6 40 ae Feb 09 08:13:21 hostname kernel: RSP: :abdd422dfcc0 EFLAGS: 00010246 Feb 09 08:13:21 hostname kernel: RAX: RBX: 95eaec7cf3a0 RCX: Feb 09 08:13:21 hostname kernel: RDX: 95eadd4718f8 RSI: 0216 RDI: 0216 Feb 09 08:13:21 hostname kernel: RBP: 020674ff R08: 0020 R09: 001b Feb 09 08:13:21 hostname kernel: R10: 95eadd471580 R11: 00035000 R12: 95eaec7cf3a8 Feb 09 08:13:21 hostname kernel: R13: 95eadd471580 R14: 95eadd471580 R15: 95eaec7cf500 Feb 09 08:13:21 hostname kernel: FS: () GS:95eb1e48() knlGS: Feb 09 08:13:21 hostname kernel: CS: 0010 DS: ES: CR0: 80050033 Feb 09 08:13:21 hostname kernel: CR2: CR3: 00040320a001 CR4: 003606e0 Feb 09 08:13:21 hostname kernel: Call Trace: Feb 09 08:13:21 hostname kernel: ? ath10k_conf_tx+0x7d/0x4b0 [ath10k_core] Feb 09 08:13:21 hostname kernel: ieee80211_bss_info_change_notify+0xab/0x1a0 [mac80211] Feb 09 08:13:21 hostname kernel: ieee80211_reconfig+0x661/0x1310 [mac80211] Feb 09 08:13:21 hostname kernel: ? __switch_to_asm+0x40/0x70 Feb 09 08:13:21 hostname kernel: ? __switch_to_asm+0x40/0x70 Feb 09 08:13:21 hostname kernel: ? __switch_to_asm+0x34/0x70 Feb 09 08:13:21 hostname kernel: wiphy_resume+0x7f/0x120 [cfg80211] Feb 09 08:13:21 hostname kernel: ? wiphy_suspend+0x270/0x270 [cfg80211] Feb 09 08:13:21 hostname kernel: dpm_run_callback+0x59/0x150 Feb 09 08:13:21 hostname kernel:
[Bug 1799988] Re: Missing wifi and bluetooth after sleep on XPS 9370
I've been testing the patches you linked above on Fedora 29 against 4.19.15-302 for about two weeks and so far I haven't had wifi disappear. I'm reasonably certain that I've lost bluetooth at least once so I'm not quite sure whether the results are just a conicidence. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1799988 Title: Missing wifi and bluetooth after sleep on XPS 9370 To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1799988/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1799988] Re: Missing wifi and bluetooth after sleep on XPS 9370
I forgot to add, I'm currently using an older firmware version RM.4.4.1.c2-00057-QCARMSWP-1 (which is mostly a leftover of searching for one that doesn't result in crashes). If you'd like to get any logs or or want me to run any tests, I'll gladly help. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1799988 Title: Missing wifi and bluetooth after sleep on XPS 9370 To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1799988/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1810822] [NEW] pdfsam crashes immediately at startup
Public bug reported: $ pdfsam Exception in thread "main" java.lang.NoClassDefFoundError: javafx/scene/layout/HBox at java.base/java.lang.ClassLoader.defineClass1(Native Method) at java.base/java.lang.ClassLoader.defineClass(ClassLoader.java:1009) at java.base/java.security.SecureClassLoader.defineClass(SecureClassLoader.java:174) at java.base/jdk.internal.loader.BuiltinClassLoader.defineClass(BuiltinClassLoader.java:802) at java.base/jdk.internal.loader.BuiltinClassLoader.findClassOnClassPathOrNull(BuiltinClassLoader.java:700) at java.base/jdk.internal.loader.BuiltinClassLoader.loadClassOrNull(BuiltinClassLoader.java:623) at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:581) at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:190) at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:499) at org.pdfsam.community.App.main(App.java:34) Caused by: java.lang.ClassNotFoundException: javafx.scene.layout.HBox at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:583) at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:190) at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:499) ... 10 more ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pdfsam 3.3.5-1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 7 18:40:41 2019 InstallationDate: Installed on 2018-06-29 (191 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all SourcePackage: pdfsam UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: pdfsam (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1810822 Title: pdfsam crashes immediately at startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pdfsam/+bug/1810822/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
