[Bug 1915123] [NEW] package grub-pc 2.02-2ubuntu8.21 failed to install/upgrade: installed grub-pc package post-installation script subprocess returned error exit status 10
Public bug reported: Hello, I started having many kinds of updating and upgrading problems after I tried to install Jitsi Meet to my Ubuntu. Here are some of them (Sorry, they are in Finnish): Tehdään asetuksia: libldap-common (2.4.45+dfsg-1ubuntu1.9) ... Tehdään asetuksia: grub-pc (2.02-2ubuntu8.21) ... dpkg: error processing package grub-pc (--configure): installed grub-pc package post-installation script subprocess returned error exit status 10 Tehdään asetuksia: libldap-2.4-2:amd64 (2.4.45+dfsg-1ubuntu1.9) ... Tehdään asetuksia: libldap-2.4-2:i386 (2.4.45+dfsg-1ubuntu1.9) ... Käsitellään paketin libc-bin (2.27-3ubuntu1.4) liipaisimia... Käsitellään paketin man-db (2.8.3-2ubuntu0.1) liipaisimia... Käsittelyssä tapahtui liian monta virhettä: grub-pc E: Sub-process /usr/bin/dpkg returned an error code (1) This what happened now, gave me this kind of announcement: Error while installing package: installed grub-pc package post- installation script subprocess returned error exit status 10 I have Ubuntu 18.04 LTS - JP ProblemType: Package DistroRelease: Ubuntu 18.04 Package: grub-pc 2.02-2ubuntu8.21 ProcVersionSignature: Ubuntu 4.15.0-135.139-generic 4.15.18 Uname: Linux 4.15.0-135-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu7.23 AptOrdering: firefox:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Tue Feb 9 06:12:27 2021 DeviceMap: (hd0) /dev/sda ErrorMessage: installed grub-pc package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2016-08-05 (1648 days ago) InstallationMedia: Ubuntu 16.04 LTS (Finnish Remix) "Xenial Xerus" - Release amd64 (20160420.1) ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-135-generic root=UUID=aaecf835-e695-4894-9d96-34269b67a7ad ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.6, Python 3.6.9, unpackaged PythonDetails: /usr/bin/python2.7, Python 2.7.17, unpackaged RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.3 apt 1.6.12ubuntu0.2 SourcePackage: grub2 Title: package grub-pc 2.02-2ubuntu8.21 failed to install/upgrade: installed grub-pc package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915123 Title: package grub-pc 2.02-2ubuntu8.21 failed to install/upgrade: installed grub-pc package post-installation script subprocess returned error exit status 10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1915123/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915124] [NEW] Please package Pipewire >= 0.3.21 (required by mutter 40)
Public bug reported: Please package Pipewire >= 0.3.21 (required by mutter 40) ** Affects: pipewire (Ubuntu) Importance: Undecided Status: New ** Tags: upgrade-software-version -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915124 Title: Please package Pipewire >= 0.3.21 (required by mutter 40) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1915124/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915121] Re: /usr/bin/gnome-shell:11:on_stage_stage_views_changed:g_closure_invoke:signal_emit_unlocked_R:g_signal_emit_valist:g_signal_emit
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #3323 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3323 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3323 Importance: Unknown Status: Unknown ** Summary changed: - /usr/bin/gnome-shell:11:on_stage_stage_views_changed:g_closure_invoke:signal_emit_unlocked_R:g_signal_emit_valist:g_signal_emit + gnome-shell crashed with SIGSEGV in on_stage_stage_views_changed() from g_closure_invoke() from signal_emit_unlocked_R() from g_signal_emit_valist() from g_signal_emit() ** Changed in: gnome-shell (Ubuntu) Status: New => Fix Committed ** Tags added: fixed-upstream ** Tags added: fixed-in-3.38.4 ** Package changed: gnome-shell (Ubuntu) => mutter (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915121 Title: gnome-shell crashed with SIGSEGV in on_stage_stage_views_changed() from g_closure_invoke() from signal_emit_unlocked_R() from g_signal_emit_valist() from g_signal_emit() To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1915121/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915121] [NEW] gnome-shell crashed with SIGSEGV in on_stage_stage_views_changed() from g_closure_invoke() from signal_emit_unlocked_R() from g_signal_emit_valist() from g_signal_emit()
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.38.2-1ubuntu1~20.10.1, the problem page at https://errors.ubuntu.com/problem/bc3566d950d42340582580239b618869c4c1d038 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: gnome-shell Importance: Unknown Status: Unknown ** Affects: mutter (Ubuntu) Importance: Undecided Status: Fix Committed ** Tags: fixed-in-3.38.4 fixed-upstream groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915121 Title: gnome-shell crashed with SIGSEGV in on_stage_stage_views_changed() from g_closure_invoke() from signal_emit_unlocked_R() from g_signal_emit_valist() from g_signal_emit() To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1915121/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915118] Re: "No bluetooth found"
** Description changed: I'm running on Ubuntu 20.04. My system has a dual-boot installation and Bluetooth works fine on Windows. however whenever I try to turn it on on Ubuntu settings displays the message "No Bluetooth found, plug in dongle to use Bluetooth". - My devices uses an Intel Wireless-AC 9462My wireless card that drives - both WiFi and Bluetooth. + My devices uses an Intel Wireless-AC 9462 card that drives both WiFi and + Bluetooth. If I check the service status it says that Bluetooth is running but it won't show on my settings menu... $ /etc/init.d/bluetooth status ● bluetooth.service - Bluetooth service - Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled) - Active: active (running) since Mon 2021-02-08 18:21:07 MST; 5h 51min ago -Docs: man:bluetoothd(8) -Main PID: 706 (bluetoothd) - Status: "Running" - Tasks: 1 (limit: 18704) - Memory: 2.3M - CGroup: /system.slice/bluetooth.service - └─706 /usr/lib/bluetooth/bluetoothd + Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled) + Active: active (running) since Mon 2021-02-08 18:21:07 MST; 5h 51min ago + Docs: man:bluetoothd(8) + Main PID: 706 (bluetoothd) + Status: "Running" + Tasks: 1 (limit: 18704) + Memory: 2.3M + CGroup: /system.slice/bluetooth.service + └─706 /usr/lib/bluetooth/bluetoothd feb 08 18:21:07 criopc systemd[1]: Starting Bluetooth service... feb 08 18:21:07 criopc bluetoothd[706]: Bluetooth daemon 5.53 feb 08 18:21:07 criopc systemd[1]: Started Bluetooth service. feb 08 18:21:07 criopc bluetoothd[706]: Starting SDP server feb 08 18:21:07 criopc bluetoothd[706]: Bluetooth management interface 1.17…ized Hint: Some lines were ellipsized, use -l to show in full. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-43-generic 5.8.0-43.49~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Feb 9 00:06:48 2021 InstallationDate: Installed on 2021-02-08 (0 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) SourcePackage: linux-signed-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915118 Title: "No bluetooth found" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1915118/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915120] [NEW] FTBFS - netcfg tests fail on hirsute
Public bug reported: Ubiquity fails to build on hirsute. netcfg tests are failing Running suite(s): inet_mton inet_ptom netcfg_parse_cidr_address netcfg_network_address netcfg_gateway_reachable nc_v6_interface_configured sh: 1: ip: not found 95%: Checks: 23, Failures: 1, Errors: 0 test/test_nc_v6_interface_configured.c:18:F:nc_v6_interface_configured:test_nc_v6_interface_configured_simple:0: Didn't find SLAAC make[3]: *** [test/tests.mk:19: test] Error 1 make[3]: Leaving directory '/<>/d-i/source/netcfg' dh_auto_test: error: make -j1 test returned exit code 2 make[2]: *** [debian/rules:7: build] Error 25 make[2]: Leaving directory '/<>/d-i/source/netcfg' make[1]: *** [Makefile:35: build] Error 1 make[1]: Leaving directory '/<>/d-i' make: *** [debian/rules:40: build-stamp] Error 2 dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2 Full logs: https://launchpadlibrarian.net/521992228/buildlog_ubuntu-hirsute-amd64.ubiquity_21.04.9~ppa1_BUILDING.txt.gz ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18 Uname: Linux 5.8.0-36-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu57 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Feb 9 08:26:57 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- InstallationDate: Installed on 2020-05-31 (254 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200527) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Critical Status: New ** Tags: amd64 apport-bug hirsute rls-hh-incoming ubiquity-20.04.15 ** Changed in: ubiquity (Ubuntu) Importance: Undecided => Critical ** Tags added: rls-hh-incoming -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915120 Title: FTBFS - netcfg tests fail on hirsute To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1915120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902179] Re: [20.04 FEAT] Support/enhancement of NVMe IPL
A known-issue entry was added to the release notes: https://wiki.ubuntu.com/FocalFossa/ReleaseNotes Hence closing this ticket. ** Changed in: ubuntu-release-notes Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902179 Title: [20.04 FEAT] Support/enhancement of NVMe IPL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1902179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905010] Re: [snap] chromium forgets custom root certificates after each update
One workaround seems to be saving the chromium profile, deleting the profile, restarting chromium and then move the saved profile back into place. I could now add our internal root CA without a problem. Will have a look how chromium behaves with the next snap update. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905010 Title: [snap] chromium forgets custom root certificates after each update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1905010/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914573] Re: [DisplayLink] Xorg crashes and return to login screen
I opened my session in Xorg this morgning. I only want one of Wayland or Xorg to work, which one you think we have a better chance? You already see some logs and probably have some idea about Xorg. My suggest is to continue for this day with Xorg, I'll send you logs each time I get the crash (I used to send you only one or two) for you to get as much as information I can. After that, maybe you'll have a better idea if continue with Xorg is a better solution, or switch to Wayland. Many thanks for help, -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914573 Title: [DisplayLink] Xorg crashes and return to login screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evdi/+bug/1914573/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914711] Re: package u-boot-rpi:arm64 2020.10+dfsg-1ubuntu0~20.10.1 failed to install/upgrade: installed u-boot-rpi:arm64 package post-installation script subprocess returned error exit status 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: u-boot (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914711 Title: package u-boot-rpi:arm64 2020.10+dfsg-1ubuntu0~20.10.1 failed to install/upgrade: installed u-boot-rpi:arm64 package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/u-boot/+bug/1914711/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900690] Re: [Ubuntu 20.04] ceph: messages, mds: Fix decoding of enum types on big-endian systems
Since the requested patches are upstream in 15.2.8 (and later) and since we have now 15.2.8 in focal-proposed and groovy-proposed: ceph | 15.2.8-0ubuntu0.20.04.1 | focal-proposed ceph | 15.2.8-0ubuntu0.20.10.1 | groovy-proposed and 16.1.0 in hirsute-proposed: ceph | 16.1.0-0ubuntu1 | hirsute-proposed I'm updating the states to Fix Committed. ** Changed in: ceph (Ubuntu Groovy) Status: Triaged => Fix Committed ** Changed in: ceph (Ubuntu Focal) Status: Triaged => Fix Committed ** Changed in: ceph (Ubuntu) Status: Triaged => Fix Committed ** Changed in: ubuntu-z-systems Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900690 Title: [Ubuntu 20.04] ceph: messages,mds: Fix decoding of enum types on big- endian systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1900690/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900691] Re: [Ubuntu 20.04] ceph: include/encoding: Fix encode/decode of float types on big-endian systems
Since the requested patches are upstream in 15.2.8 (and later) and since we have now 15.2.8 in focal-proposed and groovy-proposed: ceph | 15.2.8-0ubuntu0.20.04.1 | focal-proposed ceph | 15.2.8-0ubuntu0.20.10.1 | groovy-proposed and 16.1.0 in hirsute-proposed: ceph | 16.1.0-0ubuntu1 | hirsute-proposed I'm updating the states to Fix Committed. ** Changed in: ceph (Ubuntu Groovy) Status: Triaged => Fix Committed ** Changed in: ceph (Ubuntu Focal) Status: Triaged => Fix Committed ** Changed in: ceph (Ubuntu) Status: Triaged => Fix Committed ** Changed in: ubuntu-z-systems Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900691 Title: [Ubuntu 20.04] ceph: include/encoding: Fix encode/decode of float types on big-endian systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1900691/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915118] [NEW] "No bluetooth found"
Public bug reported: I'm running on Ubuntu 20.04. My system has a dual-boot installation and Bluetooth works fine on Windows. however whenever I try to turn it on on Ubuntu settings displays the message "No Bluetooth found, plug in dongle to use Bluetooth". My devices uses an Intel Wireless-AC 9462My wireless card that drives both WiFi and Bluetooth. If I check the service status it says that Bluetooth is running but it won't show on my settings menu... $ /etc/init.d/bluetooth status ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled) Active: active (running) since Mon 2021-02-08 18:21:07 MST; 5h 51min ago Docs: man:bluetoothd(8) Main PID: 706 (bluetoothd) Status: "Running" Tasks: 1 (limit: 18704) Memory: 2.3M CGroup: /system.slice/bluetooth.service └─706 /usr/lib/bluetooth/bluetoothd feb 08 18:21:07 criopc systemd[1]: Starting Bluetooth service... feb 08 18:21:07 criopc bluetoothd[706]: Bluetooth daemon 5.53 feb 08 18:21:07 criopc systemd[1]: Started Bluetooth service. feb 08 18:21:07 criopc bluetoothd[706]: Starting SDP server feb 08 18:21:07 criopc bluetoothd[706]: Bluetooth management interface 1.17…ized Hint: Some lines were ellipsized, use -l to show in full. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-43-generic 5.8.0-43.49~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Feb 9 00:06:48 2021 InstallationDate: Installed on 2021-02-08 (0 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) SourcePackage: linux-signed-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.8 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915118 Title: "No bluetooth found" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1915118/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914573] Re: [DisplayLink] Xorg crashes and return to login screen
We should probably open a new bug about those problems in Wayland sessions. If you wanted to just focus on Wayland then we can close this bug about Xorg crashes. If you like? Or we can keep two bugs open, I don't mind. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914573 Title: [DisplayLink] Xorg crashes and return to login screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evdi/+bug/1914573/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915117] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915117 Title: [Regression] Audio card [8086:9d71] not detected after upgrade from linux 5.4 to 5.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915117/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915117] Re: [Regression] Audio card [8086:9d71] not detected after upgrade from linux 5.4 to 5.8
I've also tried booting a live USB with the latest alpha version from 21.04, based on kernel 5.8.0-36-generic, and the results are the same: no sound card detected, "Dummy Output" displayed in Sound Settings. See attached archive with same logs (dmesg, pactl, alsa-info). ** Attachment added: "21.04-kernel-5.8.0-36-audio-logs.tar.xz" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915117/+attachment/5461562/+files/21.04-kernel-5.8.0-36-audio-logs.tar.xz ** Description changed: Ubuntu version: 20.10 (updated from 20.04) Kernel: 5.8.0-41-generic #46-Ubuntu Manufacturer: Acer Product Name: Swift SF314-54 BIOS Revision: 1.11 Audio card: Realtek High Definition Audio Multimedia audio controller [0401]: Intel Corporation Sunrise Point-LP HD Audio [8086:9d71] (rev 21) Summary === After upgrading from linux kernel 5.4 to 5.8, there is no more sound card available. However, if I select kernel 5.4 in GRUB, the sound card is available. Steps to reproduce == 1. Install 20.04 or 20.10 with a kenel 5.4 2. Check that sound output works as excepted (Settings > Sound > Output > Test) 3. Check that `alsa-info` command returns information 4. Upgrade kernel to 5.8 Expected results Sound output still works. Actual results == - No more sound card detected (Sound Settings display "Dummy Output" in - the list of output devices). + 2. Sound card is available, and sound can be output to the internal speakers. + 4. No more sound card detected (Sound Settings display "Dummy Output" in the list of output devices). ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-41-generic 5.8.0-41.46 ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Feb 9 14:42:00 2021 InstallationDate: Installed on 2019-01-20 (751 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Acer Swift SF314-54 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-41-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash mem_sleep_default=deep vt.handoff=7 RelatedPackageVersions: - linux-restricted-modules-5.8.0-41-generic N/A - linux-backports-modules-5.8.0-41-generic N/A - linux-firmware1.190.3 + linux-restricted-modules-5.8.0-41-generic N/A + linux-backports-modules-5.8.0-41-generic N/A + linux-firmware1.190.3 SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2021-02-03 (5 days ago) dmi.bios.date: 11/21/2018 dmi.bios.release: 1.11 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.11 dmi.board.name: Strongbow_KL dmi.board.vendor: KBL dmi.board.version: V1.11 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.11 dmi.ec.firmware.release: 1.6 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.11:bd11/21/2018:br1.11:efr1.6:svnAcer:pnSwiftSF314-54:pvrV1.11:rvnKBL:rnStrongbow_KL:rvrV1.11:cvnAcer:ct10:cvrV1.11: dmi.product.family: Swift 3 dmi.product.name: Swift SF314-54 dmi.product.sku: dmi.product.version: V1.11 dmi.sys.vendor: Acer -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915117 Title: [Regression] Audio card [8086:9d71] not detected after upgrade from linux 5.4 to 5.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915117/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915117] Re: [Regression] Audio card [8086:9d71] not detected after upgrade from linux 5.4 to 5.8
** Attachment added: "pactl-list-20.10-kernel-5.4.0-65-generic.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915117/+attachment/5461560/+files/pactl-list-20.10-kernel-5.4.0-65-generic.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915117 Title: [Regression] Audio card [8086:9d71] not detected after upgrade from linux 5.4 to 5.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915117/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915117] Re: [Regression] Audio card [8086:9d71] not detected after upgrade from linux 5.4 to 5.8
** Attachment added: "dmesg-20.10-kernel-5.4.0-65-generic.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915117/+attachment/5461559/+files/dmesg-20.10-kernel-5.4.0-65-generic.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915117 Title: [Regression] Audio card [8086:9d71] not detected after upgrade from linux 5.4 to 5.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915117/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915117] Re: [Regression] Audio card [8086:9d71] not detected after upgrade from linux 5.4 to 5.8
As a point of comparison, below are attached logs when using the same device with the same Ubuntu (20.10) but with an older 5.4.0-65-generic kernel. ** Attachment added: "alsa-info.20.10-kernel-5.4.0-65-generic.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915117/+attachment/5461558/+files/alsa-info.20.10-kernel-5.4.0-65-generic.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915117 Title: [Regression] Audio card [8086:9d71] not detected after upgrade from linux 5.4 to 5.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915117/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915117] [NEW] [Regression] Audio card [8086:9d71] not detected after upgrade from linux 5.4 to 5.8
Public bug reported: Ubuntu version: 20.10 (updated from 20.04) Kernel: 5.8.0-41-generic #46-Ubuntu Manufacturer: Acer Product Name: Swift SF314-54 BIOS Revision: 1.11 Audio card: Realtek High Definition Audio Multimedia audio controller [0401]: Intel Corporation Sunrise Point-LP HD Audio [8086:9d71] (rev 21) Summary === After upgrading from linux kernel 5.4 to 5.8, there is no more sound card available. However, if I select kernel 5.4 in GRUB, the sound card is available. Steps to reproduce == 1. Install 20.04 or 20.10 with a kenel 5.4 2. Check that sound output works as excepted (Settings > Sound > Output > Test) 3. Check that `alsa-info` command returns information 4. Upgrade kernel to 5.8 Expected results Sound output still works. Actual results == 2. Sound card is available, and sound can be output to the internal speakers. 4. No more sound card detected (Sound Settings display "Dummy Output" in the list of output devices). ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-41-generic 5.8.0-41.46 ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Feb 9 14:42:00 2021 InstallationDate: Installed on 2019-01-20 (751 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Acer Swift SF314-54 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-41-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash mem_sleep_default=deep vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-41-generic N/A linux-backports-modules-5.8.0-41-generic N/A linux-firmware1.190.3 SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2021-02-03 (5 days ago) dmi.bios.date: 11/21/2018 dmi.bios.release: 1.11 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.11 dmi.board.name: Strongbow_KL dmi.board.vendor: KBL dmi.board.version: V1.11 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.11 dmi.ec.firmware.release: 1.6 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.11:bd11/21/2018:br1.11:efr1.6:svnAcer:pnSwiftSF314-54:pvrV1.11:rvnKBL:rnStrongbow_KL:rvrV1.11:cvnAcer:ct10:cvrV1.11: dmi.product.family: Swift 3 dmi.product.name: Swift SF314-54 dmi.product.sku: dmi.product.version: V1.11 dmi.sys.vendor: Acer ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915117 Title: [Regression] Audio card [8086:9d71] not detected after upgrade from linux 5.4 to 5.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915117/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874381] Re: LVM device unavailable after 18.04 to 20.04 upgrade Timed out waiting for device /dev/mapper/s5lp8--v g-home
Sorry, I can't answer that for huge LVM installations. But what I can say is that it is for s390x installations (multipath with LVMs on top) a kind of immediately responding. One thought is to check/do this for example at the end of the dist- upgrade process, where a potential delay wouldn't be a very huge drawback (compared to a system that doesn't come up again after reboot). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874381 Title: LVM device unavailable after 18.04 to 20.04 upgrade Timed out waiting for device /dev/mapper/s5lp8--v g-home To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1874381/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915114] Re: Ubiquity: No vmlinuz* after install. 20.04.2
** Package changed: ubuntu => ubiquity (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915114 Title: Ubiquity: No vmlinuz* after install. 20.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1915114/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1825343] Re: [21.04 FEAT] Valgrind add new hardware support for z Systems
** Changed in: valgrind (Ubuntu) Status: New => Confirmed ** Changed in: ubuntu-z-systems Status: Triaged => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1825343 Title: [21.04 FEAT] Valgrind add new hardware support for z Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1825343/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1913395] Re: [UBUNTU 21.04] qemu s390x/pci: Honor vfio DMA limiting
** Changed in: ubuntu-z-systems Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1913395 Title: [UBUNTU 21.04] qemu s390x/pci: Honor vfio DMA limiting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1913395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915114] [NEW] Ubiquity: No vmlinuz* after install. 20.04.2
Public bug reported: I was installing ubuntu on my fresh new notebook and found that kernel packages wasn't installed. As workaround to run the system I had to chroot into /target to complete installation. I have one disk and it was partitioned as GPT. Initialy I thought it was a problem with boot loader but I had installed debian without issue(except it not provide proper firmware). Then I tried to boot into ubuntu from debian's grub and found that there are no kernels. It took me 2 days((( ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915114 Title: Ubiquity: No vmlinuz* after install. 20.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1915114/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915114] Re: Ubiquity: No vmlinuz* after install. 20.04.2
Attaching installer logs ** Attachment added: "installer.tgz" https://bugs.launchpad.net/ubuntu/+bug/1915114/+attachment/5461536/+files/installer.tgz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915114 Title: Ubiquity: No vmlinuz* after install. 20.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1915114/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903864] Re: qemu-system-x86_64: -device tpm-tis, tpmdev=tpm-tpm0, id=tpm0: Property 'tpm-tis.tpmdev' can't find value 'tpm-tpm0'
Uploaded to Focal/Groovy unapproved fro consideration by the SRU Team. ** Changed in: qemu (Ubuntu Focal) Status: Triaged => In Progress ** Changed in: qemu (Ubuntu Groovy) Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903864 Title: qemu-system-x86_64: -device tpm-tis,tpmdev=tpm-tpm0,id=tpm0: Property 'tpm-tis.tpmdev' can't find value 'tpm-tpm0' To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad/+bug/1903864/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1913395] Re: [UBUNTU 21.04] qemu s390x/pci: Honor vfio DMA limiting
Uploaded to Focal/Groovy unapproved fro consideration by the SRU Team. ** Changed in: qemu (Ubuntu Focal) Status: Triaged => In Progress ** Changed in: qemu (Ubuntu Groovy) Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1913395 Title: [UBUNTU 21.04] qemu s390x/pci: Honor vfio DMA limiting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1913395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1913266] Re: [UBUNTU 20.04] Vsock can't be used with Secure Execution, required argument not supported
** Changed in: libvirt (Ubuntu Focal) Status: New => Incomplete ** Changed in: libvirt (Ubuntu Groovy) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1913266 Title: [UBUNTU 20.04] Vsock can't be used with Secure Execution, required argument not supported To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1913266/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914573] Re: [DisplayLink] Xorg crashes and return to login screen
Hello, You're true, I changed to Wayland because it seems to be the next default of ubuntu, and it's recommended to use with Displaylink (even if in the past it had some troubles). Whatever, I'll use Xorg as you ask and I'll send you next crash information. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914573 Title: [DisplayLink] Xorg crashes and return to login screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evdi/+bug/1914573/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894778] Re: Cannot probe sata disk on sata controller behind VMD: ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
`linux-image-5.8.0-43-generic` has been released and I have updated myself to it. Still patch doesn't work whereas it works on linux- oem-20.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1894778 Title: Cannot probe sata disk on sata controller behind VMD: ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4) To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1894778/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901391] Re: Ctrl+Alt+Shift+R screen recording not working anymore in 20.10 (Pipewire is now a requirement)
** Changed in: gnome-shell (Ubuntu) Status: Triaged => In Progress ** Changed in: gnome-shell (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901391 Title: Ctrl+Alt+Shift+R screen recording not working anymore in 20.10 (Pipewire is now a requirement) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1901391/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915096] Re: clock/calendar displays outdated information
I'm not completely sure what you mean. Are you talking about the notification from 10:10 still being displayed at 12:36? ** Summary changed: - clock/calendar does not have a refresh option + clock/calendar displays outdated information ** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915096 Title: clock/calendar displays outdated information To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1915096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909950] Re: named: TCP connections sometimes never close due to race in socket teardown
Attached is a V2 of the patch that fixes this bug, Bind9 for Focal. ** Patch removed: "Debdiff for bind9 on Focal" https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1909950/+attachment/5461528/+files/lp1909950_focal.debdiff ** Patch added: "Debdiff for bind9 on Focal V2" https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1909950/+attachment/5461529/+files/lp1909950_focal_v2.debdiff ** Tags added: sts-sponsor -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909950 Title: named: TCP connections sometimes never close due to race in socket teardown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1909950/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909950] Re: named: TCP connections sometimes never close due to race in socket teardown
Attached is a debdiff for Bind9 on Focal to fix this bug. ** Patch added: "Debdiff for bind9 on Focal" https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1909950/+attachment/5461528/+files/lp1909950_focal.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909950 Title: named: TCP connections sometimes never close due to race in socket teardown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1909950/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902025] Re: hwe kernel not scoped under "Ubuntu Base"
This bug was fixed in the package update-manager - 1:21.04.8 --- update-manager (1:21.04.8) hirsute; urgency=medium [ Brian Murray ] * Clean up apt cache binary files created by the unit tests thanks to William Wilson for the patch. [ William Wilson ] * Changing to a regex from a static list of packages to be included under "Ubuntu Base". This regex expands the list of packages under "Ubuntu Base" to include all kernel packages as well as binary packages built by linux-meta source packages (LP: #1902025) -- Brian Murray Thu, 04 Feb 2021 10:42:55 -0800 ** Changed in: update-manager (Ubuntu Hirsute) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902025 Title: hwe kernel not scoped under "Ubuntu Base" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1902025/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909950] Re: named: TCP connections sometimes never close due to race in socket teardown
** Summary changed:
- TCP connections never close
+ named: TCP connections sometimes never close due to race in socket teardown
** Description changed:
- The default timeout for TCP connections on port 53 to named/bind9 is 300
- seconds. The upstream ISC build of bind9 uses this and honors an
- overrides you set in the config files.
+ [Impact]
- The Ubuntu packaged version of bind9 seems to hold idle connections
- forever, eventually exhausting the allowed open socket limit and
- refusing to service any more requests. This is reproducible on all of
- our 20.04 hosts.
+ We are seeing busy Bind9 servers stop accepting TCP connections after a
+ period of time. Looking at netstat, named is still listening to port 53
+ on all interfaces, but if you send a dig, the connection will just time
+ out:
- lsb_release -rd
- Description: Ubuntu 20.04.1 LTS
- Release: 20.04
+ $ dig +tcp ubuntu.com @192.168.122.2
+ ;; Connection to 192.168.122.2#53(192.168.122.2) for ubuntu.com failed: timed
out.
+ Symptoms are the number of tcp connections slowly increase, as well as
+ the tcp high water mark increases, if you run the "rndc status" command.
+ Eventually, the number of tcp connections will reach the tcp connection
+ limit, and named will "break" and no longer accept any new tcp
+ connections.
- Package Version: 1:9.16.1-0ubuntu2.4 500
+ There will also be a number of connections in the conntrack table stuck
+ in the ESTABLISHED state, even through they are idle and ready to close,
+ and there will be a number of connections in the SYN_SENT state, due to
+ these connections getting stuck since the tcp connection limit has been
+ reached.
+
+ This appears to be caused by a race between deactivating a netmgr handle
+ and processing a asynchronous callback for the socket close code, which
+ can get triggered when a client sends a broken packet to the server and
+ then doesn't close the connection properly.
+
+ [Testcase]
+
+ You will need two VMs to reproduce this issue.
+
+ On the first, install bind9:
+
+ $ sudo apt install bind9
+
+ Set up a caching resolver by editing /etc/bind/named.conf.options and
+ uncommenting the forwarding block, and adding a DNS provider:
+
+ forwarders {
+ 8.8.8.8;
+ };
+
+ Next, restart the named service:
+
+ $ sudo systemctl restart named.service
+
+ Edit /etc/resolv.conf and change the resolver to 127.0.0.1.
+
+ Disable the systemd-resolved service:
+
+ $ sudo systemctl stop systemd-resolved.service
+
+ Test to make sure resolving ubuntu.com works, using the IP of the NIC:
+
+ $ dig +tcp @192.168.122.21 ubuntu.com
+ https://paste.ubuntu.com/p/7NQJ6RRJHN/
+
+ Now, go to the second VM:
+
+ Test to make sure that you can dig the other VM with:
+
+ $ dig +tcp @192.168.122.21 ubuntu.com
+
+ After that, use tc to intentionally drop some packets, so we can
+ simulate bad clients dropping connections and not closing them properly,
+ so we can see if we can trigger the race.
+
+ My NIC is enp1s0, and 30% drop should do the trick.
+
+ $ sudo tc qdisc add dev enp1s0 root netem loss 30%
+
+ Next, open gnome-terminal and paste and run the below command in 10-15
+ tabs, the more the better:
+
+ $ for run in {1..1}; do dig +tcp @192.168.122.21 ubuntu.com & done
+
+ This parallelizes the connections to the bind9 server, to try and get
+ above the 150 connection limit.
+
+ Back on the server, watch the tcp high water mark in:
+
+ $ sudo rndc status
+ ..
+ tcp clients: 0/150
+ TCP high-water: 10
+ ..
+
+ $ sudo rndc status
+ ..
+ tcp clients: 31/150
+ TCP high-water: 58
+ ..
+
+ $ sudo rndc status
+ ..
+ tcp clients: 56/150
+ TCP high-water: 141
+ ..
+
+ $ sudo rndc status
+ ..
+ tcp clients: 15/150
+ TCP high-water: 150
+ ..
+
+ If you can't hit the 150 mark on tcp high water, add more tabs to the
+ other VM and keep hitting the DNS server. This will likely make the
+ other VM unstable as well, FYI.
+
+ Eventually, you will hit the 150 mark. After hitting it a bit longer,
+ your bind9 server will be broken.
+
+ $ dig +tcp @192.168.122.21 ubuntu.com
+ ;; Connection to 192.168.122.21#53(192.168.122.21) for ubuntu.com failed:
timed out.
+ ;; Connection to 192.168.122.21#53(192.168.122.21) for ubuntu.com failed:
timed out.
+
+ ; <<>> DiG 9.16.1-Ubuntu <<>> +tcp @192.168.122.21 ubuntu.com
+ ; (1 server found)
+ ;; global options: +cmd
+ ;; connection timed out; no servers could be reached
+
+ ;; Connection to 192.168.122.21#53(192.168.122.21) for ubuntu.com
+ failed: timed out.
+
+ Do this from the bind9 server, so you don't get confused with the 30%
+ packet drop of the other VM.
+
+ If you install the test package from the below ppa:
+
+ https://launchpad.net/~mruffell/+archive/ubuntu/lp1909950-test
+
+ You can hit this bind9 as much as you can, but it will never become
+ broken. If you stop the thundering herd at the 150 max connections, the
+ server will correctly tear down tcp connections, and you will be able to
+ successfully
[Bug 1915078] Re: e4defrag failures should be fatal
This bug was fixed in the package flash-kernel - 3.103ubuntu2 --- flash-kernel (3.103ubuntu2) hirsute; urgency=medium * Make errors in workaround for HP Proliant m400 u-boot ext4 parsing bug fatal. LP: #1915078. -- dann frazier Mon, 08 Feb 2021 17:54:06 -0700 ** Changed in: flash-kernel (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915078 Title: e4defrag failures should be fatal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1915078/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914992] Re: gnome-calendar crashes after a few clicks when creating event or un/toggling which calendar to show
** Description changed: I am using gnome-calendar (3.36.2) on Linux Mint 20 (Ulyana), Cinnamon 4.6.7. I am able to replicate the crash by opening gnome-calendar, then clicking on "Manage your calendars" and toggling / untoggling different calendars at random. Here's a log from journalctl if it's of use: -- The job identifier is 27260. - Feb 08 01:44:12 saturn pia-daemon[1412]: [2021-02-08 09:44:12.386][7b0a][wireguardmethod][daemon/src/wireguardmethod.cpp:1041][info] BYTECOUNT: 3311031560, 118663140 - Feb 08 01:44:12 saturn pia-daemon[1412]: [2021-02-08 09:44:12.387][7b0a][wireguardmethod][daemon/src/wireguardmethod.cpp:942][info] peer: handshake at 1612777449 - "3 sec" ago Feb 08 01:44:15 saturn org.gnome.Calendar[249540]: ** Feb 08 01:44:15 saturn org.gnome.Calendar[249540]: GcalTimeline:ERROR:../src/core/gcal-timeline.c:212:increase_completed_calendars: assertion failed: (self->completed_calendars <= g_hash_table_size (self->calendars)) Feb 08 01:44:15 saturn org.gnome.Calendar[249540]: Bail out! GcalTimeline:ERROR:../src/core/gcal-timeline.c:212:increase_completed_calendars: assertion failed: (self->completed_calendars <= g_hash_table_size (self->calendars)) Feb 08 01:44:15 saturn systemd[1]: Started Process Core Dump (PID 249641/UID 0). -- Subject: A start job for unit systemd-coredump@41-249641-0.service has finished successfully -- Defined-By: systemd -- Support: http://www.ubuntu.com/support - -- + -- -- A start job for unit systemd-coredump@41-249641-0.service has finished successfully. - -- + -- -- The job identifier is 27350. Feb 08 01:44:16 saturn systemd-coredump[249642]: Process 249540 (gnome-calendar) of user 1000 dumped core. - - Stack trace of thread 249540: - #0 0x7f1ff002018b __GI_raise (libc.so.6 + 0x4618b) - #1 0x7f1fe859 __GI_abort (libc.so.6 + 0x25859) - #2 0x7f1ff0523b43 n/a (libglib-2.0.so.0 + 0x1db43) - #3 0x7f1ff0580b2f g_assertion_message_expr (libglib-2.0.so.0 + 0x7ab2f) - #4 0x5562ad7685a7 n/a (gnome-calendar + 0x455a7) - #5 0x7f1ff0645a56 n/a (libgobject-2.0.so.0 + 0x14a56) - #6 0x7f1ff0664b28 g_signal_emit_valist (libgobject-2.0.so.0 + 0x33b28) - #7 0x7f1ff06650d3 g_signal_emit (libgobject-2.0.so.0 + 0x340d3) - #8 0x5562ad7825ec n/a (gnome-calendar + 0x5f5ec) - #9 0x7f1ff0557e6e g_main_context_dispatch (libglib-2.0.so.0 + 0x51e6e) - #10 0x7f1ff0558220 n/a (libglib-2.0.so.0 + 0x52220) - #11 0x7f1ff05582c3 g_main_context_iteration (libglib-2.0.so.0 + 0x522c3) - #12 0x7f1ff0773fd5 g_application_run (libgio-2.0.so.0 + 0xe2fd5) - #13 0x5562ad747532 main (gnome-calendar + 0x24532) - #14 0x7f1ff00010b3 __libc_start_main (libc.so.6 + 0x270b3) - #15 0x5562ad74757e _start (gnome-calendar + 0x2457e) - - Stack trace of thread 249544: - #0 0x7f1ff00efaff __GI___poll (libc.so.6 + 0x115aff) - #1 0x7f1ff055818e n/a (libglib-2.0.so.0 + 0x5218e) - #2 0x7f1ff05582c3 g_main_context_iteration (libglib-2.0.so.0 + 0x522c3) - #3 0x7f1ff155799d n/a (libdconfsettings.so + 0xa99d) - #4 0x7f1ff0581911 n/a (libglib-2.0.so.0 + 0x7b911) - #5 0x7f1fef452609 start_thread (libpthread.so.0 + 0x9609) - #6 0x7f1ff00fc293 __clone (libc.so.6 + 0x122293) - - Stack trace of thread 249543: - #0 0x7f1ff00efaff __GI___poll (libc.so.6 + 0x115aff) - #1 0x7f1ff055818e n/a (libglib-2.0.so.0 + 0x5218e) -
[Bug 1912678] ThreadStacktrace.txt
*** This bug is a duplicate of bug 1910270 *** https://bugs.launchpad.net/bugs/1910270 ** Attachment added: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1912678/+attachment/5461527/+files/ThreadStacktrace.txt ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1912678/+attachment/5455255/+files/CoreDump.gz ** Changed in: redshift (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912678 Title: redshift-gtk crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/redshift/+bug/1912678/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912678] StacktraceSource.txt
*** This bug is a duplicate of bug 1910270 *** https://bugs.launchpad.net/bugs/1910270 ** Attachment added: "StacktraceSource.txt" https://bugs.launchpad.net/bugs/1912678/+attachment/5461526/+files/StacktraceSource.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912678 Title: redshift-gtk crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/redshift/+bug/1912678/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912678] Stacktrace.txt
*** This bug is a duplicate of bug 1910270 *** https://bugs.launchpad.net/bugs/1910270 ** Attachment added: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1912678/+attachment/5461525/+files/Stacktrace.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912678 Title: redshift-gtk crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/redshift/+bug/1912678/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912678] redshift-gtk crashed with SIGSEGV
*** This bug is a duplicate of bug 1910270 *** https://bugs.launchpad.net/bugs/1910270 StacktraceTop: _gtk_settings_get_screen (settings=0x0) at ../../../../gtk/gtksettings.c:3358 gtk_css_value_icon_theme_compute (icon_theme=, property_id=, provider=, style=, parent_style=) at ../../../../gtk/gtkcssiconthemevalue.c:84 gtk_css_static_style_compute_value (style=0x2536040, provider=0x0, parent_style=, id=3, specified=0x7fb4db0e4b20 , section=0x0) at ../../../../gtk/gtkcssstaticstyle.c:237 _gtk_css_lookup_resolve (lookup=lookup@entry=0x2532e30, provider=provider@entry=0x0, style=style@entry=0x2536040, parent_style=parent_style@entry=0x0) at ../../../../gtk/gtkcsslookup.c:122 gtk_css_static_style_new_compute (parent=0x0, matcher=0x0, provider=0x0) at ../../../../gtk/gtkcssstaticstyle.c:195 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912678 Title: redshift-gtk crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/redshift/+bug/1912678/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1026601] Re: passenger-status no longer works after upgrade to precise
[Expired for passenger (Ubuntu) because there has been no activity for 60 days.] ** Changed in: passenger (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1026601 Title: passenger-status no longer works after upgrade to precise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/passenger/+bug/1026601/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1229636] Re: libapache2-mod-passenger outdated
[Expired for passenger (Ubuntu) because there has been no activity for 60 days.] ** Changed in: passenger (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1229636 Title: libapache2-mod-passenger outdated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/passenger/+bug/1229636/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891100] Re: hp notebook 15-da0001nk sound mute led not working
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891100 Title: hp notebook 15-da0001nk sound mute led not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1891100/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901444] Re: mount --rbind /var/tmp /tmp/snap.rootfs_1DwCoc//var/tmp: Permission denied)
[Expired for snapd (Ubuntu) because there has been no activity for 60 days.] ** Changed in: snapd (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901444 Title: mount --rbind /var/tmp /tmp/snap.rootfs_1DwCoc//var/tmp: Permission denied) To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1901444/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901444] Re: mount --rbind /var/tmp /tmp/snap.rootfs_1DwCoc//var/tmp: Permission denied)
[Expired for snapd because there has been no activity for 60 days.] ** Changed in: snapd Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901444 Title: mount --rbind /var/tmp /tmp/snap.rootfs_1DwCoc//var/tmp: Permission denied) To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1901444/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902671] Re: First time setup on raspberry Pi
[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ubiquity (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902671 Title: First time setup on raspberry Pi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1902671/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906078] Re: Whoopsie sends bug reports automatically without consent
[Expired for whoopsie (Ubuntu) because there has been no activity for 60 days.] ** Changed in: whoopsie (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906078 Title: Whoopsie sends bug reports automatically without consent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1906078/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915096] Re: clock/calendar does not have a refresh option
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915096 Title: clock/calendar does not have a refresh option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1915096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915003] Re: Always update the initramfs when changing power profile
IMHO, shall we have a kernel boot parameter so that the script in the initrd check and decide what to load and/or parameter to added. If that's too much work, maybe put that as a long-term goal. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915003 Title: Always update the initramfs when changing power profile To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1915003/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912263] ThreadStacktrace.txt
** Attachment added: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1912263/+attachment/5461521/+files/ThreadStacktrace.txt ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1912263/+attachment/5454239/+files/CoreDump.gz ** Changed in: marco (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912263 Title: marco crashed when running on xubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/marco/+bug/1912263/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912263] StacktraceSource.txt
** Attachment added: "StacktraceSource.txt" https://bugs.launchpad.net/bugs/1912263/+attachment/5461520/+files/StacktraceSource.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912263 Title: marco crashed when running on xubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/marco/+bug/1912263/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912263] Stacktrace.txt
** Attachment added: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1912263/+attachment/5461519/+files/Stacktrace.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912263 Title: marco crashed when running on xubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/marco/+bug/1912263/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912263] marco crashed when running on xubuntu
StacktraceTop: g_settings_set_property (object=, prop_id=, value=, pspec=) at ../../../gio/gsettings.c:596 object_set_property (object=object@entry=0x5576ca307120, pspec=0x5576ca2e6a10, value=0x7ffc16034910, nqueue=nqueue@entry=0x5576ca306060) at ../../../gobject/gobject.c:1565 g_object_new_internal (class=class@entry=0x5576ca2f8810, params=params@entry=0x7ffc160349b0, n_params=n_params@entry=1) at ../../../gobject/gobject.c:1973 g_object_new_valist (object_type=, first_property_name=first_property_name@entry=0x7f1c8780739f "schema-id", var_args=var_args@entry=0x7ffc16034b00) at ../../../gobject/gobject.c:2264 g_object_new (object_type=, first_property_name=first_property_name@entry=0x7f1c8780739f "schema-id") at ../../../gobject/gobject.c:1782 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912263 Title: marco crashed when running on xubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/marco/+bug/1912263/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915014] Re: [amdgpu] [wayland] Screen goes occasionally black after taking a screenshot
Please: 1. Open a Terminal window. 2. Reproduce the bug again. 3. After the problem has started run this in the Terminal window: journalctl -b0 > journal.txt 4. Attach the resulting text file here. Separately, please try some other kernel versions like: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.10.14/ https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.8.18/ https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.4.96/ and tell us if any of those exhibit the same bug. ** Tags added: 5.8-gfx ** Changed in: mutter (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915014 Title: [amdgpu] [wayland] Screen goes occasionally black after taking a screenshot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1915014/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915102] Re: package grub-efi-amd64-signed 1.155.2+2.04-1ubuntu35.2 failed to install/upgrade: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit stat
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915102 Title: package grub-efi-amd64-signed 1.155.2+2.04-1ubuntu35.2 failed to install/upgrade: installed grub-efi-amd64-signed package post- installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1915102/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915102] [NEW] package grub-efi-amd64-signed 1.155.2+2.04-1ubuntu35.2 failed to install/upgrade: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit st
Public bug reported: Wipe previous Ubuntu 20.04 installation on SATA SSD and install with just a single / partition. Installed alongside Windows 10 installation on NVME driver. Bootloader installed to NVME drive. Not ZFS or LVM ProblemType: Package DistroRelease: Ubuntu 20.10 Package: grub-efi-amd64-signed 1.155.2+2.04-1ubuntu35.2 ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Feb 8 14:30:17 2021 ErrorMessage: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2021-02-08 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 3.8.6-0ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.20.5ubuntu2 apt 2.1.10ubuntu0.2 SourcePackage: grub2-signed Title: package grub-efi-amd64-signed 1.155.2+2.04-1ubuntu35.2 failed to install/upgrade: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub2-signed (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915102 Title: package grub-efi-amd64-signed 1.155.2+2.04-1ubuntu35.2 failed to install/upgrade: installed grub-efi-amd64-signed package post- installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1915102/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1910871] Re: Ubuntu 21.04 QA Testing Release notes hyperlink opens to wrong page
Ubuntu 20.04 Release notes open to the Ubuntu download page. Ubuntu Mate 20.04 Release notes open to the correct Release note page.-> https ://ubuntu-mate.org/blog/ubuntu-mate-focal-fossa-release-notes/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1910871 Title: Ubuntu 21.04 QA Testing Release notes hyperlink opens to wrong page To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1910871/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 580538] Re: nepomuk generates very large .xsession-error file
Thank you for reporting this bug to Ubuntu. Ubuntu 10.04 (lucid) reached end-of-life on May 9, 2013. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in. ** Changed in: virtuoso-opensource (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/580538 Title: nepomuk generates very large .xsession-error file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtuoso-opensource/+bug/580538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880405] Re: Unresponsive GUI and journal flooded with: JS ERROR: TypeError: null has no properties _onFocusChanged@resource:///org/gnome/shell/ui/closeDialog.js:135:9
** Summary changed: - Unresponsive GUI, sometimes high CPU, and journal flooded with: JS ERROR: TypeError: null has no properties _onFocusChanged@resource:///org/gnome/shell/ui/closeDialog.js:135:9 + Unresponsive GUI and journal flooded with: JS ERROR: TypeError: null has no properties _onFocusChanged@resource:///org/gnome/shell/ui/closeDialog.js:135:9 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880405 Title: Unresponsive GUI and journal flooded with: JS ERROR: TypeError: null has no properties _onFocusChanged@resource:///org/gnome/shell/ui/closeDialog.js:135:9 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1880405/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915040] Re: gnome-shell is so laggy after waking up
*** This bug is a duplicate of bug 1880405 *** https://bugs.launchpad.net/bugs/1880405 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1880405, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1880405 Unresponsive GUI, sometimes high CPU, and journal flooded with: JS ERROR: TypeError: null has no properties _onFocusChanged@resource:///org/gnome/shell/ui/closeDialog.js:135:9 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915040 Title: gnome-shell is so laggy after waking up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1915040/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915089] Re: Update to 3.38.3 and SRU it
Marco, Maybe also cherry pick the fix for bug 1880405? It's a doozy. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915089 Title: Update to 3.38.3 and SRU it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1915089/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1883890] Re: [MIR] libinih
I reviewed libinih 50-1 as checked into hirsute. This shouldn't be considered a full audit but rather a quick gauge of maintainability. libinih is a simple ini file parser for C and C++. - CVE History: - there's no cves in our database - Build-Depends: debhelper-compat, meson - pre/post inst/rm scripts? - None - init scripts? - None - systemd units? - None - dbus services? - None - setuid binaries? - None - binaries in PATH? - None - sudo fragments? - None - polkit files? - None - udev rules? - None - unit tests / autopkgtests? - Small test suite appears to be run both during the build and during autopkgtest - cron jobs? - None - Build logs: - Clean build logs, lintian warnings are out of date: W: libinih source: debhelper-compat-file-is-missing W: libinih source: package-uses-deprecated-debhelper-compat-version 1 E: libinih source: package-uses-debhelper-but-lacks-build-depends E: libinih source: missing-build-dependency debhelper W: libinih source: newer-standards-version 4.5.0 (current is 4.1.4) - Processes spawned? - None - Memory management? - Complicated by changing compile-time malloc vs stack into runtime; it seemed okay but it's C. - File IO? - No file writing; file reading under control of the library user. - Logging? - None - Environment variable usage? - None - Use of privileged functions? - None - Use of cryptography / random number sources etc? - None - Use of temp files? - None - Use of networking? - None - Use of WebKit? - None - Use of PolicyKit? - None - Any significant cppcheck results? - None - Any significant Coverity results? - One small warning https://github.com/benhoyt/inih/issues/127 - Any significant shellcheck results? - None - Any significant bandit results? - None There's an error when a strncpy() was replaced with a memcpy(). Thankfully there is already a fix upstream: https://github.com/benhoyt/inih/commit/d7f465792c0c7686b50ed45c9a435394ae418d3e #diff-bf9ac2185bcd8a2bc7227af48d0b5da96acee30f6c6a7ba75173c84ce6f2e2c9 This may or may not really justify a CVE: usually ini files are supplied by administrators or people who otherwise want the software to work. In any event, I'd like our packages fixed before we promote this package to main. So, security team PROVISIONAL ACK on promoting libinih to main, conditional upon this being fixed in our packaging, either via a fresh Debian import or patch. Thanks ** Bug watch added: github.com/benhoyt/inih/issues #127 https://github.com/benhoyt/inih/issues/127 ** Changed in: libinih (Ubuntu) Assignee: Ubuntu Security Team (ubuntu-security) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1883890 Title: [MIR] libinih To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinih/+bug/1883890/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915061] Re: Applications - Wrong pagination when exiting from a folder
*** This bug is a duplicate of bug 1889102 *** https://bugs.launchpad.net/bugs/1889102 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1889102, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1889102 [ubuntu-dock] App grid has too many page dots on right -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915061 Title: Applications - Wrong pagination when exiting from a folder To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1915061/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915097] [NEW] kernel needs to put a date/time-stamp in the log at boot
Public bug reported: The log as output by dmesg does not contain the date-time of last boot. This seems a serious oversight. Surely, the kernel is able to query the clock? Knowing the exact date-time could be crucial in cases of repeated reboots. Anyway, a date-time stamp would seem a reasonable requirement from an auditing perspective. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-41-generic 5.8.0-41.46~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Feb 9 13:32:23 2021 InstallationDate: Installed on 2021-01-14 (26 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: linux-signed-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.8 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915097 Title: kernel needs to put a date/time-stamp in the log at boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1915097/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573345] Re: Dual monitor loses settings after screen sleep
Further info: Kubuntu 20.10 KDE Plasma 5.19.5 Kernel 5.8.0-41-generic GTX 1070 with nvidia-driver-450 (also tried -460) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1573345 Title: Dual monitor loses settings after screen sleep To manage notifications about this bug go to: https://bugs.launchpad.net/kscreen/+bug/1573345/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573345] Re: Dual monitor loses settings after screen sleep
Confirmed I have the same bug, and the same sound issues as Jeff.m @vsteel. 1. LG UltraGear (DP-2) - After sleep, this one goes away. Display properties -> Enable brings it back. - Sound goes to this monitor, but doesn't work?! 2. E2742 (DVI-D-0) - After sleep, only monitor that works. Workarounds: * Display Properties, Dropdown to LG Ultragear, Enable. Brings it back. * Audio is much harder. Only thing I could find that re-enables it is HDAJackRetask. For some reason, the OS 'forgets' that I have 5.1 speakers on Realtek ALCS1200A codec, and only goes to the NVidia GPU 83 HDMI/DP. Gets annoying to apply after every time my system goes to sleep. :/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1573345 Title: Dual monitor loses settings after screen sleep To manage notifications about this bug go to: https://bugs.launchpad.net/kscreen/+bug/1573345/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915025] Re: Update to 3.38.3 and SRU it
** Tags added: fixed-in-3.38.3 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915025 Title: Update to 3.38.3 and SRU it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1915025/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915026] Re: Souris inactive et écran figé
Thanks for the bug report. It appears gnome-shell has frozen or crashed but Xorg is still working. Next time the problem happens, please: 1. Wait 10 seconds. 2. Reboot. 3. Open a Terminal and run: journalctl -b-1 > prevboot.txt 4. Attach the file 'prevboot.txt' here. Please also follow these steps to check for crashes: https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment ** Tags added: 5.8-gfx ** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915026 Title: Souris inactive et écran figé To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1915026/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915089] Re: Update to 3.38.3 and SRU it
** Tags added: groovy hirsute ** Tags added: fixed-in-3.38.3 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915089 Title: Update to 3.38.3 and SRU it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1915089/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915023] Re: Fix an extension spamming gnome logs?
** Package changed: gnome-shell-extension-ubuntu-dock (Ubuntu) => gnome- shell-extension-gamemode (Ubuntu) ** Summary changed: - Fix an extension spamming gnome logs? + Object .Gjs_gamemode_christian_kellner_me_extension_GameModeIndicator (0x5565b80a8c60), has been already deallocated — impossible to set any property on it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915023 Title: Object .Gjs_gamemode_christian_kellner_me_extension_GameModeIndicator (0x5565b80a8c60), has been already deallocated — impossible to set any property on it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-gamemode/+bug/1915023/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915096] [NEW] clock/calendar does not have a refresh option
Public bug reported: The drop-down calendar from the clock (in the middle of the top bar) does not offer a refresh option and consequently displays out-dated information (see attached). It needs a refresh-button. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Feb 9 13:25:24 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: rtl8821CU, 5.4.1, 5.8.0-40-generic, x86_64: installed rtl8821CU, 5.4.1, 5.8.0-41-generic, x86_64: installed virtualbox, 6.1.16, 5.8.0-40-generic, x86_64: installed virtualbox, 6.1.16, 5.8.0-41-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 530 [103c:8054] InstallationDate: Installed on 2021-01-14 (26 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: HP HP EliteDesk 800 G2 SFF ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-41-generic root=UUID=9dd289f2-eb84-4c73-92fb-e6050acc143d ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/14/2020 dmi.bios.release: 2.48 dmi.bios.vendor: HP dmi.bios.version: N01 Ver. 02.48 dmi.board.name: 8054 dmi.board.vendor: HP dmi.board.version: KBC Version 05.39 dmi.chassis.type: 4 dmi.chassis.vendor: HP dmi.ec.firmware.release: 5.57 dmi.modalias: dmi:bvnHP:bvrN01Ver.02.48:bd07/14/2020:br2.48:efr5.57:svnHP:pnHPEliteDesk800G2SFF:pvr:rvnHP:rn8054:rvrKBCVersion05.39:cvnHP:ct4:cvr: dmi.product.family: 103C_53307F G=D dmi.product.name: HP EliteDesk 800 G2 SFF dmi.product.sku: L1G76AV dmi.sys.vendor: HP 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 N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: ubuntu Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu ** Attachment added: "Workspace 1_331.png" https://bugs.launchpad.net/bugs/1915096/+attachment/5461481/+files/Workspace%201_331.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915096 Title: clock/calendar does not have a refresh option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1915096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914573] Re: [DisplayLink] Xorg crashes and return to login screen
Thanks for all that. Confusingly you now seem to be getting hangs in the Intel kernel driver followed by gnome-shell crashes. This seems to be a different bug to what we were looking at before, probably caused by using Wayland instead of Xorg... févr. 08 10:51:19 PORTABLE-PPAQUIN kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 févr. 08 10:51:19 PORTABLE-PPAQUIN gnome-shell[3042]: GNOME Shell crashed with signal 6 févr. 08 10:51:19 PORTABLE-PPAQUIN gnome-shell[3042]: == Stack trace for context 0x55e1400292a0 == févr. 08 12:58:22 PORTABLE-PPAQUIN kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 févr. 08 12:58:22 PORTABLE-PPAQUIN gnome-shell[2676]: GNOME Shell crashed with signal 6 févr. 08 12:58:22 PORTABLE-PPAQUIN gnome-shell[2676]: == Stack trace for context 0x5618d81e35d0 == Please change back to 'Ubuntu' instead of 'Ubuntu on Wayland', and then follow the steps in comment #16. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914573 Title: [DisplayLink] Xorg crashes and return to login screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evdi/+bug/1914573/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915014] Re: Screen goes occasionally black after taking a screenshot
** Package changed: xorg (Ubuntu) => mutter (Ubuntu) ** Tags added: amdgpu ** Summary changed: - Screen goes occasionally black after taking a screenshot + [amdgpu] [wayland] Screen goes occasionally black after taking a screenshot -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915014 Title: [amdgpu] [wayland] Screen goes occasionally black after taking a screenshot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1915014/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915025] Re: Update to 3.38.3 and SRU it
** Tags added: groovy hirsute -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915025 Title: Update to 3.38.3 and SRU it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1915025/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915095] [NEW] clamscan modifies atime during scheduled scans
Public bug reported: During operation, clamscan updates the atime on every file that it touches. Since Linux 2.6.8, it's possible to pass the O_NOATIME flag when opening a file. Unfortunately, clamscan does not do this. For example, see https://fossies.org/linux/clamav/clamscan/manager.c#l_399. My expectation is that system software like backups and antivirus would not update atimes. Would Ubuntu be willing to patch this, or should I submit this bug upstream? ** Affects: clamav (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/1915095 Title: clamscan modifies atime during scheduled scans To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1915095/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1164016] Re: restore type-ahead find
** Bug watch removed: gitlab.gnome.org/GNOME/nautilus/-/issues #1154 https://gitlab.gnome.org/GNOME/nautilus/-/issues/1154 ** Bug watch removed: gitlab.gnome.org/GNOME/nautilus/-/issues #1157 https://gitlab.gnome.org/GNOME/nautilus/-/issues/1157 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1164016 Title: restore type-ahead find To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1164016/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1910557] Re: Buildd images do not launch on macOS under multipass due to missing unpacked kernels and initrd
** Changed in: livecd-rootfs (Ubuntu Bionic) Status: New => In Progress ** Changed in: livecd-rootfs (Ubuntu Xenial) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1910557 Title: Buildd images do not launch on macOS under multipass due to missing unpacked kernels and initrd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1910557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914445] Re: Buildd tarball images do not include package manifests
Do we want this in xenial too? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914445 Title: Buildd tarball images do not include package manifests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1914445/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1730612] Re: Enable Remote desktop feature during build
** Changed in: mutter (Ubuntu) Importance: Wishlist => Medium ** Changed in: mutter (Ubuntu) Status: Triaged => In Progress ** Changed in: mutter (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1730612 Title: Enable Remote desktop feature during build To manage notifications about this bug go to: https://bugs.launchpad.net/baltix-default-settings/+bug/1730612/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1910557] Re: Buildd images do not launch on macOS under multipass due to missing unpacked kernels and initrd
** Changed in: livecd-rootfs (Ubuntu Focal) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1910557 Title: Buildd images do not launch on macOS under multipass due to missing unpacked kernels and initrd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1910557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915092] [NEW] lib-gtk-3 / lib-gtk-3-dev NOT compatible
Public bug reported: I'm using Ubuntu-Mate 20.04 and I am trying to compile California (a calendar program) which requires libgtk-3-dev. When I try to install libgtk-3-dev I get: The following packages have unmet dependencies: libgtk-3-dev : Depends: libgtk-3-0 (= 3.24.23-1ubuntu1) but 3.24.23-1ubuntu1.1 is to be installed So I look at what versions of libgtk-3-0 are available 3.24.23-1ubuntu1 and 3.24.23-1ubuntu1.1, of which the latter is installed. So I tried to force install the older version so that it would be compatible with the dev files but it then tries to uninstall my entire Mate desktop, NOT ACCEPTABLE. Launchpad says NOT to self compile Gtk-3 because it's already installed in Ubuntu 20.04 but the version installed seems to be borked having not been compatible with the development packages making it impossible to compile anything that uses gtk-3. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: libgtk-3-dev (not installed) Uname: Linux 5.11.0-rc7 x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Mon Feb 8 16:45:13 2021 InstallationDate: Installed on 2020-08-10 (182 days ago) InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915092 Title: lib-gtk-3 / lib-gtk-3-dev NOT compatible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1915092/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915091] [NEW] Nautilus shows LXD storage pool in sidebar
Public bug reported: I recently set up LXD 4.11 on Ubuntu 20.04 with a file-backed btrfs storage pool called "default". Now Nautilus shows a "default" device in the sidebar despite the loop device not being intended for users to directly interact with. System: Ubuntu 20.04.2 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Description changed: - I recently set up LXD on Ubuntu 20.04 with a file-backed btrfs storage - pool called "default". Now Nautilus shows a "default" device in the - sidebar despite the loop device not being intended for users to directly - interact with. + I recently set up LXD 4.11 on Ubuntu 20.04 with a file-backed btrfs + storage pool called "default". Now Nautilus shows a "default" device in + the sidebar despite the loop device not being intended for users to + directly interact with. + + System: Ubuntu 20.04.2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915091 Title: Nautilus shows LXD storage pool in sidebar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1915091/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912835] Re: ESP should be fscked
** Description changed: [Impact] - * ESP can be not clean, thus failing to mount on boot. + * ESP can be not clean, thus failing to mount on boot. - * fsck should be enabled for ESP partition. + * fsck should be enabled for ESP partition. [Test Case] - * $ systemctl status systemd-fsck@*.service + * $ systemctl status systemd-fsck*.service - On boot, that should produce status for two drives, the one with short + On boot, that should produce status for two drives, the one with short uuid should be the one mounted as /ESP [Where problems could occur] - * The change will affect only newly deployed instances. Old instances + * The change will affect only newly deployed instances. Old instances will have to correct this in fstab themselves. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912835 Title: ESP should be fscked To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1912835/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1910557] Re: Buildd images do not launch on macOS under multipass due to missing unpacked kernels and initrd
** Also affects: livecd-rootfs (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: livecd-rootfs (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: livecd-rootfs (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: livecd-rootfs (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: livecd-rootfs (Ubuntu Groovy) Importance: Undecided Status: New ** Changed in: livecd-rootfs (Ubuntu Hirsute) Status: New => Fix Released ** Changed in: livecd-rootfs (Ubuntu Groovy) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1910557 Title: Buildd images do not launch on macOS under multipass due to missing unpacked kernels and initrd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1910557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914883] Re: hart0: trap handler failed (error -2) (Needs cherry-pick ab3d207f)
** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914883 Title: hart0: trap handler failed (error -2) (Needs cherry-pick ab3d207f) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1914883/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871268] Re: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected
** Project changed: ubuntubudgie => ubuntu-cdimage -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871268 Title: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1871268/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915089] [NEW] Update to 3.38.3 and SRU it
Public bug reported: [ Impact ] That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/gnome-shell/-/commits/3.38.3 [ Test case ] The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME GNOME Shell and its components should continue working Ideally the verification should include checking those extensions before and after the update to ensure the SRU isn't creating regressions https://launchpadlibrarian.net/511426552/gse [ Regression potential ] Icon grid behavior has some changes reverted which may lead to slight difference in look. Workspace switch fixes have been included, so workspace behavior should be checked. ** Affects: gnome-shell (Ubuntu) Importance: Medium Assignee: Marco Trevisan (Treviño) (3v1n0) Status: In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915089 Title: Update to 3.38.3 and SRU it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1915089/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1865838] Re: no error displayed on failed fingerprint authentication
** Description changed: + [ Impact ] + + No fingerprint errors are exposed on fingerprint login failures. + from journalctl, gdm-fingerprint shows error there after retried 5 times of fingerprint login failed, so I open this issue here. - Steps to reproduce issue: + + [ Test case ] + 1. enroll fingerprint for your right index finger. 2. logout 3. login and try login by incorrect finger e.g. middle finger - 4. after 5 times retry. There's no error popup, then re-try index finger still no any message remind users they can not try fingerprint anymore. + 4. Each time the wrong finger is used an error is shown + 5. After 3 times retries, an authentication error is shown, suggesting +to use another method. - It will confuse user. + [ Regression potential] - Suggest behavior: - 1. Each time user try fingerprint failed, show error message to remind user. - 2. When user exceed 5 time errors, show error message to remind user input password instead. + Wrong errors are shown during both fingerprint auth and other kinds of authentications. + Password failures aren't properly exposed. Verification can't restart on error. - ProblemType: Bug - DistroRelease: Ubuntu 20.04 + --- + + ProblemType: BugDistroRelease: Ubuntu 20.04 Package: gdm3 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 3 15:32:00 2020 InstallationDate: Installed on 2020-03-02 (0 days ago) - InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200301) - SourcePackage: gdm3 + InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200301)SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1865838 Title: no error displayed on failed fingerprint authentication To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1865838/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915066] Re: Authentication is cancelled (and immediately restarted) hitting Escape causing fingerprint to stop working and multiple stale gdm working
** Description changed: + [ Test case ] + In the user session lockscreen (gdm login screen is fine): - Lock the screen - Hit Enter - Hit Escape - Repeat - You'll see by checking watch -n1 "ps aux |grep gdm-session-worker" (or - just ps'ing after unlocked) that many gdm workers are left around and - never terminated. + Checking watch -n1 "ps aux |grep gdm-session-worker" (or just ps'ing + after unlocked) gdm workers should not be running (a part the one used + for logging in). Fingerprint unlocking is particularly hit by this as the service may prevent further authentication to happen until the PAM module times out. https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3654 + + [ Regression potential ] + + Authenticating at login screen or at unlock screen stops working after + wrong credentials have been used once or the request has been cancelled + via escape key. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915066 Title: Authentication is cancelled (and immediately restarted) hitting Escape causing fingerprint to stop working and multiple stale gdm working To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1915066/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1523108] Re: Bluetooth doesn't work on ASUS Zenbook UX301LAA
Dear all; I had the same issue with Kubuntu 20.04LTS, yesterday and during the installation the bluetooth was working perfectly on my Asus UX305ua than, this morning, no bluetooth adapter found. I solved it by simply plugin in (power supply) my laptop. It appear to be an issue with the power management (energy saving). Something disable the bluetooth adapter to save energy. So if you have this issue could you try to replicated the issue by 1. pluging the power cord 2. spinning an ubuntu live-cd This might help the maintainer/developer to help us :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1523108 Title: Bluetooth doesn't work on ASUS Zenbook UX301LAA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1523108/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915082] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1915082/+attachment/5461464/+files/UdevDb.txt ** 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/1915082 Title: [Macbook7,1] backlight not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915082/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915082] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1915082/+attachment/5461463/+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/1915082 Title: [Macbook7,1] backlight not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915082/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915082] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1915082/+attachment/5461462/+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/1915082 Title: [Macbook7,1] backlight not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915082/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915082] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1915082/+attachment/5461461/+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/1915082 Title: [Macbook7,1] backlight not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915082/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915082] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1915082/+attachment/5461460/+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/1915082 Title: [Macbook7,1] backlight not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915082/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915082] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1915082/+attachment/5461459/+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/1915082 Title: [Macbook7,1] backlight not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915082/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915082] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1915082/+attachment/5461458/+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/1915082 Title: [Macbook7,1] backlight not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915082/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
