[Touch-packages] [Bug 1302932] Re: libpgm fails to recognize eth0
** Bug watch added: github.com/steve-o/openpgm/issues #34 https://github.com/steve-o/openpgm/issues/34 ** Also affects: openpgm via https://github.com/steve-o/openpgm/issues/34 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libpgm in Ubuntu. https://bugs.launchpad.net/bugs/1302932 Title: libpgm fails to recognize eth0 Status in OpenPGM: Unknown Status in libpgm package in Ubuntu: New Bug description: Please see https://code.google.com/p/openpgm/issues/detail?id=34 Since it will be resolved in a future version of libpgm, we need a quick fix for now. All machines in my company with Ubuntu 14.04 beta installed yield this bug. To manage notifications about this bug go to: https://bugs.launchpad.net/openpgm/+bug/1302932/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1885990] Re: server: Match has no effect in include file (upstream 3122)
This bug was fixed in the package openssh - 1:8.4p1-2 --- openssh (1:8.4p1-2) unstable; urgency=medium * Revert incorrect upstream patch that claimed to fix the seccomp sandbox on x32 but in fact broke it instead. -- Colin Watson Mon, 26 Oct 2020 17:41:13 + ** Changed in: openssh (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1885990 Title: server: Match has no effect in include file (upstream 3122) Status in portable OpenSSH: Unknown Status in openssh package in Ubuntu: Fix Released Bug description: Hello Ubuntu version: focal 20.04 LTS Version: openssh-server: Installed: 1:8.2p1-4ubuntu0.1 Candidate: 1:8.2p1-4ubuntu0.1 Expected: match statement in included files work as documented in the fine manual What happens: the statements are ignored. If you add Match statements in an included file, it will generate no error but have no effect. The exact same statements work in the main server config file (/etc/ssh/sshd_config) this is to track upstream bug 3122: https://bugzilla.mindrot.org/show_bug.cgi?id=3122 it's fixed but will only be in 8.4 so it affects Ubuntu 20.04 LTS where openssh is at 8.2. I'm not *absolutely* whining for a backport since include files is a new feature for openssl in focal so it's not a regression. Would be nice though :), because include files are standard for any server software in Linux since at least a decade... To manage notifications about this bug go to: https://bugs.launchpad.net/openssh/+bug/1885990/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1896333] Re: [Dell Inspiron 5548] "Select an audio" menu when user have not even inserted headphone jack.
[Expired for pulseaudio (Ubuntu) because there has been no activity for 60 days.] ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1896333 Title: [Dell Inspiron 5548] "Select an audio" menu when user have not even inserted headphone jack. Status in pulseaudio package in Ubuntu: Expired Bug description: GNOME 3.36.3 | Ubuntu 20.04.1 It has been a month and I have been experiencing this weird behavior. Earphone option like this 3 while unlocking the laptop as if I have inserted earphones. Some details this issue: I have to wait like 10 min or so after the lock of the screen. This will trigger something and when I open the lid or touch mouse pad to unlock, I get earphone options to chooose in the screen as if I have inserted headphone jack. Something is wrong. I want to know why. This didn't used to happen a month ago. I waited a month to report this issue thinking it will get resolved in upcoming updates but sadly no changes so far. I think some Ubuntu's GNOME update might have something to do this. This is my wild guess. But very certain about it. Let me know. Although the issue might seems really small issue but very annoying to go throw this EVERYDAY. I would love to know what is causing this? When its fixed? Is there something wrong on my side? Note: This happens ONLY when I try to unlock the screen after like >10 min or so. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.6 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: pranav 3554 F pulseaudio /dev/snd/controlC0: pranav 3554 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Sep 19 20:54:36 2020 InstallationDate: Installed on 2020-02-16 (216 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: pulseaudio UpgradeStatus: Upgraded to focal on 2020-05-08 (134 days ago) dmi.bios.date: 05/28/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0FFJC4 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A10 dmi.modalias: dmi:bvnDellInc.:bvrA10:bd05/28/2019:svnDellInc.:pnInspiron5548:pvrA10:rvnDellInc.:rn0FFJC4:rvrA00:cvnDellInc.:ct8:cvrA10: dmi.product.name: Inspiron 5548 dmi.product.sku: 0641 dmi.product.version: A10 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1896333/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1899100] Re: whoopsie assert failure: double free or corruption (fasttop)
This bug was fixed in the package whoopsie - 0.2.73 --- whoopsie (0.2.73) hirsute; urgency=medium * Attempt to fix double free issue (LP: #1899100) - src/whoopsie.c: reject duplicate keys, re-order certain operations. - src/tests/data/crash/invalid_key_duplicate, src/tests/test_parse_report.c: added test for duplicate keys. -- Marc Deslauriers Mon, 26 Oct 2020 14:40:14 -0400 ** Changed in: whoopsie (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1899100 Title: whoopsie assert failure: double free or corruption (fasttop) Status in whoopsie package in Ubuntu: Fix Released Bug description: Apport popped up saying whoopsie had crashed (I assume during a previous crash report upload?) ProblemType: Crash DistroRelease: Ubuntu 20.10 Package: whoopsie 0.2.72 ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10 Uname: Linux 5.8.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu49 Architecture: amd64 AssertionMessage: double free or corruption (fasttop) CasperMD5CheckResult: skip CrashCounter: 1 Date: Fri Oct 9 08:08:56 2020 ExecutablePath: /usr/bin/whoopsie InstallationDate: Installed on 2019-11-18 (325 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcCmdline: /usr/bin/whoopsie -f ProcEnviron: LANG=en_AU.UTF-8 LANGUAGE=en_AU:en PATH=(custom, no user) RelatedPackageVersions: apport-noui N/A Signal: 6 SourcePackage: whoopsie StacktraceTop: __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f5982159128 "%s\n") at ../sysdeps/posix/libc_fatal.c:155 malloc_printerr (str=str@entry=0x7f598215b5d8 "double free or corruption (fasttop)") at malloc.c:5389 _int_free (av=0x7f598218bba0 , p=0x55964a2bf3e0, have_lock=0) at malloc.c:4298 () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_hash_table_remove_all () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: whoopsie assert failure: double free or corruption (fasttop) UpgradeStatus: Upgraded to groovy on 2020-10-06 (2 days ago) UserGroups: N/A separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1899100/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1904775] Re: software-properties-gtk hangs indefinitely if a single source server is down
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1904775 Title: software-properties-gtk hangs indefinitely if a single source server is down Status in software-properties package in Ubuntu: New Bug description: Since this prevents non-technical users from installing critical security updates and does not give them any useful information, I consider it a security issue. A single repository server is down and a bug in software-properties- gtk will prevent non-technical users to continue installing security updates. Example: The Darktable repository is currently offline: https://software.opensuse.org/download.html?project=graphics:darktable:stable=darktable Running sudo apt update clearly shows that one repository is offline. When I open Software Sources app (software-properties-gtk) and it starts to “Refresh Software Cache”, I expect the following: - software sources are being refreshed. - this might take a little longer than normal. - it throws an error and returns to the main screen. - the user can continue normally. In short: it should cope with a server being down. The actual behaviour: - refreshing takes forever. - Ubuntu throws an error saying it hit an error, asking to send the report about software-properties. - I have to manually force close the loading screen. - I can close the main window of software-properties. - when I launch "Software Sources" again, I get an empty square window. This should not happen when a server happens to be down. Running sudo apt update clearly shows that one repository is offline. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: software-properties-gtk 0.98.9.3 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Wed Nov 18 19:59:49 2020 InstallationDate: Installed on 2020-11-18 (0 days ago) InstallationMedia: Ubuntu-Budgie 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1904775/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1904939] [NEW] Monitor Settings Don't Get Applied in Wayland
Public bug reported: When configuring a 1080p monitor and a 4k monitor in extended screen mode while using Wayland, when trying to change the screen positions or which screen is the primary screen in the Monitor Settings, the settings reset to default when Apply is clicked. Choosing to "Revert the Settings" during the 15-second timer causes it to apply the changed settings, but this resets whenever a pop-up message appears or when returning to the Monitor Settings. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Nov 19 16:47:09 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 630 [1028:08ac] Subsystem: Dell Polaris 22 MGL XL [Radeon Pro WX Vega M GL] [1028:08ac] InstallationDate: Installed on 2020-11-18 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. Precision 5530 2-in-1 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-54-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/09/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.11.10 dmi.board.name: 02TH5P dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.11.10:bd07/09/2020:svnDellInc.:pnPrecision55302-in-1:pvr:rvnDellInc.:rn02TH5P:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: Precision dmi.product.name: Precision 5530 2-in-1 dmi.product.sku: 08AC dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1904939 Title: Monitor Settings Don't Get Applied in Wayland Status in xorg package in Ubuntu: New Bug description: When configuring a 1080p monitor and a 4k monitor in extended screen mode while using Wayland, when trying to change the screen positions or which screen is the primary screen in the Monitor Settings, the settings reset to default when Apply is clicked. Choosing to "Revert the Settings" during the 15-second timer causes it to apply the changed settings, but this resets whenever a pop-up message appears or when returning to the Monitor Settings. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Nov 19 16:47:09 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 630 [1028:08ac] Subsystem: Dell Polaris 22 MGL XL [Radeon Pro WX Vega M GL] [1028:08ac] InstallationDate: Installed on 2020-11-18 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. Precision 5530 2-in-1 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-54-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/09/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.11.10 dmi.board.name: 02TH5P dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias:
[Touch-packages] [Bug 1900729] Re: gnome-terminal font settings show only italic version of ubuntu mono
This bug was fixed in the package pango1.0 - 1.46.2-3 --- pango1.0 (1.46.2-3) unstable; urgency=medium * Team upload * d/p/fc_Sort-faces-of-a-family.patch, d/p/fontconfig_Try-harder-to-return-a-default-face.patch: - Show regular monospace fonts in gnome-terminal's profile editor and not arbitrary font styles (LP: #1900729) [ Simon McVittie ] * d/gbp.conf: Use upstream/1.46.x branch -- Gunnar Hjalmarsson Tue, 10 Nov 2020 21:41:00 +0100 ** Changed in: pango1.0 (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1900729 Title: gnome-terminal font settings show only italic version of ubuntu mono Status in gnome-terminal package in Ubuntu: Invalid Status in gtk+3.0 package in Ubuntu: Fix Released Status in pango1.0 package in Ubuntu: Fix Released Status in gnome-terminal source package in Groovy: Fix Released Status in gtk+3.0 source package in Groovy: Won't Fix Bug description: [Impact] When you want to select a monospace font in gnome-terminal's profile editor, it does not always show the regular font but rather an arbitrarily chosen one. The proposed gnome-terminal upload reverts an upstream commit, which means that all weights/styles for monospace fonts are shown. It takes us back to how it works in focal. [Test case] * Install the binaries built from gnome-terminal in groovy-proposed * Relogin * Open gnome-terminal -> Preferences and open the window for selecting a custom font for the profile. Find that it shows all available monospace fonts. Confirm for a few fonts that they can actually be selected without issues. [Where problems could occur] This is a one liner in gnome-terminal and does not affect other applications. So given a successful verification of the test case, this ought to be a safe change. [Other info] Please note that this particular change has not been made in hirsute. The reason is that we intend to follow upstream there, which means that the issue will be resolved through changes in gtk and pango. [Original description] trying to change the font in gnome-terminal, only the italics version of the ubuntu mono font is shown, as can be seen in the attachment. on the other hand, when changing fonts in the appearance settings, i can see all variants of the ubuntu fonts... ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-terminal 3.38.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Tue Oct 20 16:56:57 2020 InstallationDate: Installed on 2020-10-20 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201019.1) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1900729/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1573095] Re: Cloud images fail to boot when a serial port is not available
Oh, so it's explained! Thanks Javier for the data. You're using an outdated version of the package that doesn't contain this fix. You need initramfs-tools version 0.122ubuntu8.17 - you can either try to get an updated cloud image, or after the first boot you may be able to update it (you could disable the console=ttySX entry in the cmdline as a workaround in the 1st boot). If possible, please try the new version and let us all know how it goes. Cheers, Guilherme -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1573095 Title: Cloud images fail to boot when a serial port is not available Status in cloud-images: Invalid Status in cloud-init: Invalid Status in Ubuntu: Invalid Status in initramfs-tools package in Ubuntu: Fix Released Bug description: I tried to launch a ubuntu 16.04 cloud image within KVM. The image is not booting up and hangs at "Btrfs loaded" Hypervisor env is Proxmox 4.1 [racb: see comment 40 for minimal steps to reproduce using Ubuntu- provided tooling only] Related bugs: * bug 1016695: add console=tty1 to cloud-image kernel boot parameters * bug 1123220: cloud-image VM causes kernel panic if image is resized * bug 1061977: Machine fails to commission when console=ttyS0 is present on kernel opts * bug 1573095: Cloud images fail to boot when a serial port is not available * bug 1122245: booting from a cloud image hangs until virsh console is used To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1573095/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1904616] Re: after upgrade analog audio output vanished
*** This bug is a duplicate of bug 1897965 *** https://bugs.launchpad.net/bugs/1897965 i confirm that purging pipewire solves the issue. the analog audio output is back. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1904616 Title: after upgrade analog audio output vanished Status in pulseaudio package in Ubuntu: New Bug description: after an upgrade from 20.04 to 20.10 the analog audio output vanished. in pavucontrol there is no corresponding profile available for the built-in audio in the configuration tab. additional info: > aplay -l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC887-VD Analog [ALC887-VD Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4] Subdevices: 1/1 Subdevice #0: subdevice #0 > pacmd list-cards 2 card(s) available. index: 0 name: driver: owner module: 7 properties: alsa.card = "0" alsa.card_name = "HDA Intel PCH" alsa.long_card_name = "HDA Intel PCH at 0xb123 irq 140" alsa.driver_name = "snd_hda_intel" device.bus_path = "pci-:00:1f.3" sysfs.path = "/devices/pci:00/:00:1f.3/sound/card0" device.bus = "pci" device.vendor.id = "8086" device.vendor.name = "Intel Corporation" device.product.id = "02c8" device.form_factor = "internal" device.string = "0" device.description = "Built-in Audio" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" profiles: input:analog-stereo: Analog Stereo Input (priority 65, available: no) output:hdmi-stereo: Digital Stereo (HDMI) Output (priority 5900, available: unknown) output:hdmi-stereo+input:analog-stereo: Digital Stereo (HDMI) Output + Analog Stereo Input (priority 5965, available: no) output:hdmi-stereo-extra1: Digital Stereo (HDMI 2) Output (priority 5700, available: no) output:hdmi-stereo-extra1+input:analog-stereo: Digital Stereo (HDMI 2) Output + Analog Stereo Input (priority 5765, available: no) output:hdmi-surround-extra1: Digital Surround 5.1 (HDMI 2) Output (priority 600, available: no) output:hdmi-surround-extra1+input:analog-stereo: Digital Surround 5.1 (HDMI 2) Output + Analog Stereo Input (priority 665, available: no) output:hdmi-surround71-extra1: Digital Surround 7.1 (HDMI 2) Output (priority 600, available: no) output:hdmi-surround71-extra1+input:analog-stereo: Digital Surround 7.1 (HDMI 2) Output + Analog Stereo Input (priority 665, available: no) output:hdmi-stereo-extra2: Digital Stereo (HDMI 3) Output (priority 5700, available: no) output:hdmi-stereo-extra2+input:analog-stereo: Digital Stereo (HDMI 3) Output + Analog Stereo Input (priority 5765, available: no) output:hdmi-surround-extra2: Digital Surround 5.1 (HDMI 3) Output (priority 600, available: no) output:hdmi-surround71-extra2: Digital Surround 7.1 (HDMI 3) Output (priority 600, available: no) output:hdmi-stereo-extra3: Digital Stereo (HDMI 4) Output (priority 5700, available: no) output:hdmi-stereo-extra3+input:analog-stereo: Digital Stereo (HDMI 4) Output + Analog Stereo Input (priority 5765, available: no) output:hdmi-surround-extra3: Digital Surround 5.1 (HDMI 4) Output (priority 600, available: no) output:hdmi-surround71-extra3: Digital Surround 7.1 (HDMI 4) Output (priority 600, available: no) output:hdmi-stereo-extra4: Digital Stereo (HDMI 5) Output (priority 5700, available: no) output:hdmi-stereo-extra4+input:analog-stereo: Digital Stereo (HDMI 5) Output + Analog Stereo Input (priority 5765, available: no) output:hdmi-surround-extra4: Digital Surround 5.1 (HDMI 5) Output (priority 600, available: no) output:hdmi-surround71-extra4: Digital Surround 7.1 (HDMI 5) Output (priority 600, available: no) off: Off (priority 0, available: unknown) active profile: sinks:
[Touch-packages] [Bug 1904924] [NEW] Xorg freeze
Public bug reported:
Sounds like a fairly common problem according to [this
page](https://wiki.ubuntu.com/X/Troubleshooting/Freeze): my display
freezes, and while I'm still able to move the mouse around, I can't
successfully click or type at any windows. It takes about 30 seconds for
gnome-shell to restart, and then the clock starts running (and the
system monitor starts updating) again.
This problem has been bugging me for a few months now, but I'm not sure
when it started. It tends to happen in clumps; sometimes it will go
several days without happening, but once it starts it often happens
twice pretty quickly, and often a few times across a day. I haven't been
able to isolate what causes it, but more often than not it has something
to do with clicking on a window or tab in Chrome. (It definitely also
happens in other applications, though.)
Every time it happens, dmesg contains a stack dump for gnome-shell
("page allocation failure"). I can provide gists of these dumps if
that's helpful (and not already included in the apport data). So I'm not
sure if this is actually an xorg thing or a gnome-shell thing.
% lsb_release -rd
Description:Ubuntu 20.10
Release:20.10
% dpkg -l xorg* gnome-shell* | grep '^ii'
ii gnome-shell 3.38.1-1ubuntu1.1
amd64graphical shell for the GNOME desktop
ii gnome-shell-common 3.38.1-1ubuntu1.1
all common files for the GNOME graphical shell
ii gnome-shell-extension-appindicator 34-1
all AppIndicator/KStatusNotifierItem support for GNOME Shell
ii gnome-shell-extension-desktop-icons 20.04.0+git20200908-1
all desktop icon support for GNOME Shell
ii gnome-shell-extension-prefs 3.38.1-1ubuntu1.1
amd64tool to enable / disable GNOME Shell extensions
ii gnome-shell-extension-system-monitor 38+git20200414-32cc79e-1
all Display system information in GNOME Shell status bar
ii gnome-shell-extension-system76-power 2.0.0~1602857239~20.10~914b531~dev
all Gnome-shell extension for System76 Power Management
ii gnome-shell-extension-ubuntu-dock68ubuntu20.10.1
all Ubuntu Dock for GNOME Shell
ii gnome-shell-extensions 3.38.1-1
all Extensions to extend functionality of GNOME Shell
ii xorg 1:7.7+19ubuntu15
amd64X.Org X Window System
ii xorg-docs-core 1:1.7.1-1.1
all Core documentation for the X.org X Window System
ii xorg-sgml-doctools 1:1.11-1
all Common tools for building X.Org SGML documentation
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: xorg 1:7.7+19ubuntu15
ProcVersionSignature: Ubuntu 5.8.0-7630.32~1605108806~20.10~7e52b13~dev-generic
5.8.17
Uname: Linux 5.8.0-7630-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory:
'/proc/driver/nvidia/capabilities/gpu0'
.proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory:
'/proc/driver/nvidia/capabilities/mig'
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory:
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 455.38 Thu Oct 22 06:06:59
UTC 2020
GCC version: gcc version 10.2.0 (Ubuntu 10.2.0-13ubuntu1)
ApportVersion: 2.20.11-0ubuntu50.1
Architecture: amd64
BootLog:
CasperMD5CheckResult: skip
CompizPlugins: No value set for
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Nov 19 15:05:17 2020
DistUpgraded: 2020-11-16 10:15:57,099 DEBUG Running PostInstallScript:
'./xorg_fix_proprietary.py'
DistroCodename: groovy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) (prog-if
00 [VGA controller])
Subsystem: eVga.com. Corp. GP106 [GeForce GTX 1060 3GB] [3842:6162]
InstallationDate: Installed on 2018-01-19 (1035 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
MachineType: System76, Inc. Wild Dog Performance
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-7630-generic
root=UUID=e12a4ebc-6235-4471-a2da-3f9da9d48f74 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: Upgraded to groovy on 2020-11-16
[Touch-packages] [Bug 1573095] Re: Cloud images fail to boot when a serial port is not available
You are welcome. This is what i see in the ubuntu image i'm running on VMware for debugging purposes: ** Attachment added: "ubuntu16.04.PNG" https://bugs.launchpad.net/cloud-images/+bug/1573095/+attachment/5436062/+files/ubuntu16.04.PNG -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1573095 Title: Cloud images fail to boot when a serial port is not available Status in cloud-images: Invalid Status in cloud-init: Invalid Status in Ubuntu: Invalid Status in initramfs-tools package in Ubuntu: Fix Released Bug description: I tried to launch a ubuntu 16.04 cloud image within KVM. The image is not booting up and hangs at "Btrfs loaded" Hypervisor env is Proxmox 4.1 [racb: see comment 40 for minimal steps to reproduce using Ubuntu- provided tooling only] Related bugs: * bug 1016695: add console=tty1 to cloud-image kernel boot parameters * bug 1123220: cloud-image VM causes kernel panic if image is resized * bug 1061977: Machine fails to commission when console=ttyS0 is present on kernel opts * bug 1573095: Cloud images fail to boot when a serial port is not available * bug 1122245: booting from a cloud image hangs until virsh console is used To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1573095/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1903048] Re: [SRU] Bluetooth won't activate on the pi 400
I also tried this on my pi400 and confirmed I can see and connect to bluetooth devices after updating to bluez 5.55-0ubuntu1.1 from groovy- proposed ** Tags removed: verification-needed verification-needed-groovy ** Tags added: verification-done verification-done-groovy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1903048 Title: [SRU] Bluetooth won't activate on the pi 400 Status in bluez package in Ubuntu: Triaged Status in bluez source package in Groovy: Fix Committed Status in bluez source package in Hirsute: Triaged Bug description: [Impact] Without these patches, Bluetooth is inoperable on the recently released Raspberry Pi 400. [Test Case] * Boot the Ubuntu Desktop for Pi image on a Pi 400. * Start the Settings application and switch to the Bluetooth tab * Verify that Bluetooth is not enabled and attempting to activate it fails * Enable the -proposed repository for the release (groovy) * sudo apt update * sudo apt install bluez * sudo reboot * Start the Settings application and switch to the Bluetooth tab * Verify that Bluetooth is active and that Bluetooth devices (e.g. mice, mobile phones, headphones, etc.) can connect and operate correctly [Regression Potential] Extremely low (on groovy in particular, this has the same version of bluez as hirsute). The only significant risk is to non-Pi platforms or dongles which also use the Broadcom 43xx (or Cypress 305) chips for Bluetooth which might be inadvertently affected by these patches. [Original Description] The new Pi 400 has a slightly different Wifi/BT chip to the Pi4. Whilst wifi works happily, Bluetooth fails to operate. This doesn't appear to be an issue with either the firmware (the latest versions from upstream Raspbian have been tried), or the kernel (a known-good raspi kernel has been tested under Ubuntu), but with Bluez itself. Specifically, tracing the initialization with btmon on Raspbian and Ubuntu, the stack consistently fails when attempting to "Set Default PHY" on the latter. Curiously, under Ubuntu the adapter also appears to lack a MAC address. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1903048/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1901090] Re: run-parts: failed to stat component /etc/network/if-post-down.d/avahi-daemon: No such file or directory
This bug was fixed in the package avahi - 0.8-3ubuntu2 --- avahi (0.8-3ubuntu2) hirsute; urgency=medium * debian/avahi-daemon.links: - remove buggy symlink, the target doesn't exist anymore (lp: #1901090) * debian/avahi-daemon.postinst: - remove the deprecated conffiles if-up/down entries on upgrade, use a simple logic and no dpkg-maintscript-helper since there is no configuration worth saving -- Sebastien Bacher Tue, 10 Nov 2020 15:03:56 +0100 ** Changed in: avahi (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1901090 Title: run-parts: failed to stat component /etc/network/if-post-down.d/avahi- daemon: No such file or directory Status in avahi package in Ubuntu: Fix Released Bug description: avahi-daemon 0.7-4ubuntu7 installs a symlink /etc/network/if-post- down.d/avahi-daemon -> ../if-up.d/avahi-daemon but doesn't install the symlink target /etc/network/if-up.d/avahi-daemon That makes ifdown complain: $ sudo ifdown enp2s0f3 run-parts: failed to stat component /etc/network/if-post-down.d/avahi-daemon: No such file or directory The problem only occurs if avahi-daemon is installed from scratch; if it is upgraded from older versions, the missing file is still there according to this line in /var/lib/dpkg/status: /etc/network/if-up.d/avahi-daemon 6dbf1a91ab420a99d1205972d6401e67 obsolete To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1901090/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1573095] Re: Cloud images fail to boot when a serial port is not available
Thanks for the report Javier! What version of initramfs-tools are you using ? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1573095 Title: Cloud images fail to boot when a serial port is not available Status in cloud-images: Invalid Status in cloud-init: Invalid Status in Ubuntu: Invalid Status in initramfs-tools package in Ubuntu: Fix Released Bug description: I tried to launch a ubuntu 16.04 cloud image within KVM. The image is not booting up and hangs at "Btrfs loaded" Hypervisor env is Proxmox 4.1 [racb: see comment 40 for minimal steps to reproduce using Ubuntu- provided tooling only] Related bugs: * bug 1016695: add console=tty1 to cloud-image kernel boot parameters * bug 1123220: cloud-image VM causes kernel panic if image is resized * bug 1061977: Machine fails to commission when console=ttyS0 is present on kernel opts * bug 1573095: Cloud images fail to boot when a serial port is not available * bug 1122245: booting from a cloud image hangs until virsh console is used To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1573095/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1904903] [NEW] Pulseaudio always defaults to any external audio device connected when booting up
Public bug reported: When I am booting the computer up, it never sets the default output to the one I was using previously, which should be the norm. This is also the same for audio inputs. It works perfectly fine when connecting any new sound sources to the PC, which then pulseaudio sets the output/input to. But regarding it's state when booting up, it should stay on the last used audio device. 1) Description: Ubuntu 20.10 Release:20.10 2) pulseaudio: Instalado: 1:13.99.2-1ubuntu2 Candidato: 1:13.99.2-1ubuntu2 Tabela de versão: *** 1:13.99.2-1ubuntu2 500 500 http://br.archive.ubuntu.com/ubuntu groovy-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:13.99.2-1ubuntu1 500 500 http://br.archive.ubuntu.com/ubuntu groovy/main amd64 Packages ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1904903 Title: Pulseaudio always defaults to any external audio device connected when booting up Status in pulseaudio package in Ubuntu: New Bug description: When I am booting the computer up, it never sets the default output to the one I was using previously, which should be the norm. This is also the same for audio inputs. It works perfectly fine when connecting any new sound sources to the PC, which then pulseaudio sets the output/input to. But regarding it's state when booting up, it should stay on the last used audio device. 1) Description: Ubuntu 20.10 Release: 20.10 2) pulseaudio: Instalado: 1:13.99.2-1ubuntu2 Candidato: 1:13.99.2-1ubuntu2 Tabela de versão: *** 1:13.99.2-1ubuntu2 500 500 http://br.archive.ubuntu.com/ubuntu groovy-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:13.99.2-1ubuntu1 500 500 http://br.archive.ubuntu.com/ubuntu groovy/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1904903/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1904902] [NEW] Pulseaudio produces a lot of crackling audio after awhile
Public bug reported: 1) Description: Ubuntu 20.10 Release: 20.10 2) pulseaudio: Instalado: 1:13.99.2-1ubuntu2 Candidato: 1:13.99.2-1ubuntu2 Tabela de versão: *** 1:13.99.2-1ubuntu2 500 500 http://br.archive.ubuntu.com/ubuntu groovy-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:13.99.2-1ubuntu1 500 500 http://br.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 3) What you expected to happen: It shouldn't produce any crackles in the audio after a set amount of time. 4) What happened instead: It starts to crackle with a very low volume, then it keeps increasing until it reaches the same volume as the music/audio. Running systemctl --user restart pulseaudio.service fixes the issue until the next restart. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Uname: Linux 5.8.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Nov 19 14:09:37 2020 ExecutablePath: /usr/bin/pulseaudio InstallationDate: Installed on 2020-06-16 (156 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: LANG=pt_BR.UTF-8 LANGUAGE=pt_BR:pt:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/14/2020 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2202 dmi.board.asset.tag: Default string dmi.board.name: PRIME B450-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2202:bd07/14/2020:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB450-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1904902 Title: Pulseaudio produces a lot of crackling audio after awhile Status in pulseaudio package in Ubuntu: New Bug description: 1) Description: Ubuntu 20.10 Release: 20.10 2) pulseaudio: Instalado: 1:13.99.2-1ubuntu2 Candidato: 1:13.99.2-1ubuntu2 Tabela de versão: *** 1:13.99.2-1ubuntu2 500 500 http://br.archive.ubuntu.com/ubuntu groovy-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:13.99.2-1ubuntu1 500 500 http://br.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 3) What you expected to happen: It shouldn't produce any crackles in the audio after a set amount of time. 4) What happened instead: It starts to crackle with a very low volume, then it keeps increasing until it reaches the same volume as the music/audio. Running systemctl --user restart pulseaudio.service fixes the issue until the next restart. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Uname: Linux 5.8.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Nov 19 14:09:37 2020 ExecutablePath: /usr/bin/pulseaudio InstallationDate: Installed on 2020-06-16 (156 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: LANG=pt_BR.UTF-8 LANGUAGE=pt_BR:pt:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/14/2020 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2202 dmi.board.asset.tag: Default string dmi.board.name: PRIME B450-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2202:bd07/14/2020:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB450-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to:
[Touch-packages] [Bug 1573095] Re: Cloud images fail to boot when a serial port is not available
I've been able to reproduce this with a 16.04 Amazon EC2 exported image on VMware vSphere 6.7. The VM boot fine after adding a serial port. We will try to reproduce the same workaround adding a serial console connection in OCI (which is the final target for that cloud image). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1573095 Title: Cloud images fail to boot when a serial port is not available Status in cloud-images: Invalid Status in cloud-init: Invalid Status in Ubuntu: Invalid Status in initramfs-tools package in Ubuntu: Fix Released Bug description: I tried to launch a ubuntu 16.04 cloud image within KVM. The image is not booting up and hangs at "Btrfs loaded" Hypervisor env is Proxmox 4.1 [racb: see comment 40 for minimal steps to reproduce using Ubuntu- provided tooling only] Related bugs: * bug 1016695: add console=tty1 to cloud-image kernel boot parameters * bug 1123220: cloud-image VM causes kernel panic if image is resized * bug 1061977: Machine fails to commission when console=ttyS0 is present on kernel opts * bug 1573095: Cloud images fail to boot when a serial port is not available * bug 1122245: booting from a cloud image hangs until virsh console is used To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1573095/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1872504] Re: date modified is wrong for files on an exfat formatted drive
I made some experiments to define the behaviour, the problem is, that 3 computers with installed ubuntu 20.04.1 LTS behave(d) differently (installing fuse-exfat 1.3.0 stopped the described behaviour in two of the computers, seems, that nautilus is able to bypass fuse-exfat in some conditions). I made the tests in an alternative terminal session without active GUI and manually mounting without the fstab-entries. I repeatedly mounted the device, created files, read them with cat, modified them with touch. I did not apply status changes. Then I unmounted, mounted read-only, checked changes and changeability, seeing, that mount with -r option really protected the file system from being changed. touch xy creates a file, the time applied to the system was correct in atime, ctime, mtime but highly fractioned below milliseconds, which is not really in accordance to the exfat system where the time resolution is 2 seconds and in an additional field 10 ms. if unmounted and mounted read only again the newly created files were advanced 1 month and the seconds were rounded to the next lower even number (conforming to the time resolution of 2 seconds in the mtime and ctime, the atime was set to Dec, 31, 1979, 1:00 (+001). cat and touch (which results in the expected error message) made no changes to the files, also if unmounted and remounted rw. The same results came with remounting read/writeable. After using cat the mtime and ctime remains unchanged (1 month advanced), atime is set to the correct timestamp. After using touch all three timestamps are updated to the actual time and date (without fraction, just even seconds!) if unmounted and mounted again files that were only read, showed a further advance of the date by one month in mtime and ctime and again Dec, 31,1979 in atime. The touched files advanced by 1 month in mtime and ctime and also showed Dec, 31, 1979 in atime. Files that were only listed showed no change (remained the one month advanced as happend by the unmounting after their creation). It seems that the procedure that writes some buffers back to the hard drive during unmounting has bugs in converting to the exfat file entries. The month in the c time-structure is 0-11, in exfat 1-12, this may be an issue. The field for last access seems to be left empty. And the fractions below the 2 seconds seem to be omitted in the procedures that work with the filesystem even before flushing the buffers, but they seem to be used in the procedure, that creates a file newly. After installing fuse-exfat this behaviour stopped in one computer, in the other not (where I will try uninstall and reinstall...). A bit less important, but now with cat even the atime stays unchanged completely (other than with ext4); ctime is changed together with mtime. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1872504 Title: date modified is wrong for files on an exfat formatted drive Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: When using exfat formatted drives (e.g. my camera card) with focal fossa any access causes the date modified to be set, even when it would not normally be set, and it is set a month into the future. Installing exfat-fuse and exfat-utils results in the correct behaviour. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.18 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Mon Apr 13 17:27:30 2020 InstallationDate: Installed on 2020-04-12 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) PackageArchitecture: all ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1872504/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
** Tags removed: champagne -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm Status in systemd: New Status in accountsservice package in Ubuntu: Invalid Status in dbus package in Ubuntu: Incomplete Status in gnome-shell package in Ubuntu: Invalid Status in accountsservice source package in Focal: Invalid Status in dbus source package in Focal: Incomplete Status in gnome-shell source package in Focal: Invalid Bug description: This morning I found my computer on the login screen. But not the one of the screen log, no a new one - so something must have crashed. Logging in again confirmed that all apps were gone and the gnome shell was brought down what seems like triggered by a background update o accountsservice. As always things are not perfectly clear :-/ The following goes *back* in time through my logs one by one. Multiple apps crashed at 06:09, but we will find later that this is a follow on issue of the underlying gnome/X/... recycling. -rw-r- 1 paelzer whoopsie 52962868 Apr 8 06:09 _usr_bin_konversation.1000.crash -rw-r- 1 paelzer whoopsie 986433 Apr 8 06:09 _usr_lib_x86_64-linux-gnu_libexec_drkonqi.1000.crash rdkit was failing fast and giving up (that will be a different bug, it just seems broken on my system): Apr 08 06:10:13 Keschdeichel systemd[1]: Started RealtimeKit Scheduling Policy Service. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully called chroot. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully dropped privileges. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully limited resources. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: pthread_create failed: Resource temporarily unavailable Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Canary thread running. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Exiting canary thread. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoting known real-time threads. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoted 0 threads. Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Main process exited, code=exited, status=1/FAILURE Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with result 'exit-code'. Apr 08 06:10:13 Keschdeichel dbus-daemon[1208]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.1176' (uid=121 pid=> Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Start request repeated too quickly. Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with result 'exit-code'. Apr 08 06:10:13 Keschdeichel systemd[1]: Failed to start RealtimeKit Scheduling Policy Service. Apr 08 06:10:13 Keschdeichel bluetoothd[1729331]: Bluetooth daemon 5.53 But that already was only triggered by a gnome restart that kicked of earlier: Apr 08 06:09:27 Keschdeichel systemd[1726656]: Started GNOME Shell on Wayland. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Shell on Wayland. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session is initialized. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Wayland Session. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session (session: gnome-login). X was recycleing before: Apr 08 06:09:19 Keschdeichel systemd[10683]: Stopping GNOME Shell on X11... ... Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (EE) systemd-logind: ReleaseControl failed: Unknown object '/org/freedesktop/login1/session/_32'. Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (II) Server terminated successfully (0). Closing log file. It seems like some internal service broke and everything that followed was a secondary issue to that: Apr 08 06:09:19 Keschdeichel systemd[1]: NetworkManager.service: Unexpected error response from GetNameOwner(): Connection terminated Apr 08 06:09:19 Keschdeichel systemd[1]: wpa_supplicant.service: Unexpected error response from GetNameOwner(): Connection terminated Apr 08 06:09:19 Keschdeichel systemd[1]: thermald.service: Unexpected error response from GetNameOwner(): Connection terminated Apr 08 06:09:19 Keschdeichel thermald[1256]: [WARN]Terminating ... Apr 08 06:09:19 Keschdeichel avahi-daemon[1204]: Got SIGTERM, quitting. Apr 08 06:09:19 Keschdeichel systemd[1]: udisks2.service: Unexpected error response from GetNameOwner(): Connection terminated Apr 08 06:09:19 Keschdeichel ModemManager[1308]: Caught signal, shutting down... Apr 08 06:09:19 Keschdeichel systemd[1]: switcheroo-control.service: Unexpected error
[Touch-packages] [Bug 1903849] Re: vim ftbfs
** Tags removed: rls-hh-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1903849 Title: vim ftbfs Status in vim package in Ubuntu: Confirmed Bug description: see https://launchpad.net/ubuntu/+source/vim/2:8.2.1913-1ubuntu1 blocking the perl transition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1903849/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1902244] Re: Backport packages for 20.04.1 HWE stack
Hello Timo, or anyone else affected, Accepted mesa into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mesa/20.2.1-1~ubuntu0.20.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: mesa (Ubuntu Focal) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1902244 Title: Backport packages for 20.04.1 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-11 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Invalid Status in libclc source package in Focal: Fix Committed Status in libdrm source package in Focal: Fix Committed Status in llvm-toolchain-11 source package in Focal: Fix Committed Status in mesa source package in Focal: Fix Committed Status in xorg-server source package in Focal: Confirmed Bug description: [Impact] These are needed for 20.04.1 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. Check upgrade from stock bionic. [Regression potential] libdrm: very minimal chance for regressions llvm-11: a new package, no regression potential on it's own libclc: just a rebuild against the new llvm mesa: a new major release, but we'll pull the final stable release of 20.2.x series, so there shouldn't be any regressions left at that point xserver: a new point-release xorg drivers: modest updates, if any To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1902244/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1904638] Re: Xbox Series X|S controller doesn't work and Xbox icon still blinks after pairing
I'm using the 5.10-rc4 and the problem still occurs. Seems (but I'm probably wrong) the controoler is using another MAC address. ** Attachment added: "dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1904638/+attachment/5435972/+files/dmesg.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1904638 Title: Xbox Series X|S controller doesn't work and Xbox icon still blinks after pairing Status in bluez package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I have Xbox Series X|S controller and the Xbox icon still blinks after the successful pairing. I'm using Ubuntu 20.10 updated with BlueZ latest release. I'm following this bug closely and I can provide any information you need and do any tests you want. mhalano@glados:~$ lsb_release -rd Description: Ubuntu 20.10 Release: 20.10 mhalano@glados:~$ apt policy bluez bluez: Installed: 5.55-0ubuntu1.1 Candidate: 5.55-0ubuntu1.1 Version table: *** 5.55-0ubuntu1.1 500 500 http://br.archive.ubuntu.com/ubuntu groovy-proposed/main amd64 Packages 100 /var/lib/dpkg/status 5.55-0ubuntu1 500 500 http://br.archive.ubuntu.com/ubuntu groovy/main amd64 Packages --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2020-10-23 (25 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. Inspiron 5590 NonfreeKernelModules: nvidia_modeset nvidia Package: linux PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-30-generic root=UUID=1e3484bb-be3c-4f5d-be22-044d9df06a4a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-30.32-generic 5.8.17 Tags: groovy package-from-proposed Uname: Linux 5.8.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/13/2020 dmi.bios.release: 1.11 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.11.0 dmi.board.name: 0XRXN9 dmi.board.vendor: Dell Inc. dmi.board.version: A04 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.11.0:bd08/13/2020:br1.11:svnDellInc.:pnInspiron5590:pvr:rvnDellInc.:rn0XRXN9:rvrA04:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5590 dmi.product.sku: 0957 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: 14:F6:D8:6A:A3:F0 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:5307486 acl:57516 sco:0 events:78636 errors:0 TX bytes:18701 acl:357 sco:0 commands:841 errors:0 mtime.conffile..etc.bluetooth.main.conf: 2020-11-04T10:53:00.842656 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1904638/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1900348] Re: Canon TS705 printer stopped working
I now connected the printer with the network cable instead of USB and it seems I can use "driverless printing" for this one. Still strange with the canon driver. Also there should be more users with this issue. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1900348 Title: Canon TS705 printer stopped working Status in cups package in Ubuntu: Invalid Bug description: My Canon TS705 printer stopped working in Ubuntu. Last time I used it was over a week ago so it could be something with the updates installed in the last two weeks. The printer queue says "filter failed". I've attached the cups log of the last print job. I already tried (besides rebooting) removing / installing the printer and reinstalling the canon driver package. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1.1 ProcVersionSignature: Ubuntu 5.4.0-51.56-generic 5.4.65 Uname: Linux 5.4.0-51-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sun Oct 18 20:42:50 2020 InstallationDate: Installed on 2019-09-20 (394 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190919) Lpstat: Gerät für CanonTS705: cnijbe2://canon/?port=usb=10746E MachineType: Dell Inc. Latitude 5591 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/CanonTS705.ppd'] failed with exit code 2: grep: /etc/cups/ppd/CanonTS705.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-51-generic root=UUID=c0cdf9a7-59c9-4ce4-8dfa-06ad760e34a5 ro quiet splash usbcore.autosuspend=-1 vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/23/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.1 dmi.board.name: 0CGP1G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.1:bd05/23/2019:svnDellInc.:pnLatitude5591:pvr:rvnDellInc.:rn0CGP1G:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5591 dmi.product.sku: 0819 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1900348/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1904870] Re: unable to upgrade linux-image in 21.04 daily build using sudo apt dist-upgrade
And yes, the answer is most likely that linux-image-5.8.0-30-generic was not built when you tried, hence it could not upgrade the meta package. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1904870 Title: unable to upgrade linux-image in 21.04 daily build using sudo apt dist-upgrade Status in apt package in Ubuntu: Invalid Bug description: I am using ubuntu mate 21.04 daily build.I tried updating with sudo apt update && sudo apt upgrade -y && sudo apt dist-upgrade -y && sudo apt autoremove -y I saw version update of linux image from 5.8.0-25-generic to 1.linux-image-generic/hirsute-proposed 5.8.0.30.32+21.04.34 amd64 [upgradable from: 5.8.0.25.30] 2.linux-image-generic/hirsute,now 5.8.0.25.30 amd64 [installed,upgradable to: 5.8.0.30.32+21.04.34] Even after rebooting several time update doesn't install ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: apt 2.1.11 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu53 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt Date: Thu Nov 19 20:18:04 2020 InstallationDate: Installed on 2020-11-19 (0 days ago) InstallationMedia: Lubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201118) SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1904870/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1904870] Re: unable to upgrade linux-image in 21.04 daily build using sudo apt dist-upgrade
Please don't use proposed if you don't know what you're getting yourselves into. Especially on a development release. ** Changed in: apt (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1904870 Title: unable to upgrade linux-image in 21.04 daily build using sudo apt dist-upgrade Status in apt package in Ubuntu: Invalid Bug description: I am using ubuntu mate 21.04 daily build.I tried updating with sudo apt update && sudo apt upgrade -y && sudo apt dist-upgrade -y && sudo apt autoremove -y I saw version update of linux image from 5.8.0-25-generic to 1.linux-image-generic/hirsute-proposed 5.8.0.30.32+21.04.34 amd64 [upgradable from: 5.8.0.25.30] 2.linux-image-generic/hirsute,now 5.8.0.25.30 amd64 [installed,upgradable to: 5.8.0.30.32+21.04.34] Even after rebooting several time update doesn't install ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: apt 2.1.11 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu53 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt Date: Thu Nov 19 20:18:04 2020 InstallationDate: Installed on 2020-11-19 (0 days ago) InstallationMedia: Lubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201118) SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1904870/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1904870] [NEW] unable to upgrade linux-image in 21.04 daily build using sudo apt dist-upgrade
Public bug reported: I am using ubuntu mate 21.04 daily build.I tried updating with sudo apt update && sudo apt upgrade -y && sudo apt dist-upgrade -y && sudo apt autoremove -y I saw version update of linux image from 5.8.0-25-generic to 1.linux-image-generic/hirsute-proposed 5.8.0.30.32+21.04.34 amd64 [upgradable from: 5.8.0.25.30] 2.linux-image-generic/hirsute,now 5.8.0.25.30 amd64 [installed,upgradable to: 5.8.0.30.32+21.04.34] Even after rebooting several time update doesn't install ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: apt 2.1.11 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu53 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt Date: Thu Nov 19 20:18:04 2020 InstallationDate: Installed on 2020-11-19 (0 days ago) InstallationMedia: Lubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201118) SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apt (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1904870 Title: unable to upgrade linux-image in 21.04 daily build using sudo apt dist-upgrade Status in apt package in Ubuntu: New Bug description: I am using ubuntu mate 21.04 daily build.I tried updating with sudo apt update && sudo apt upgrade -y && sudo apt dist-upgrade -y && sudo apt autoremove -y I saw version update of linux image from 5.8.0-25-generic to 1.linux-image-generic/hirsute-proposed 5.8.0.30.32+21.04.34 amd64 [upgradable from: 5.8.0.25.30] 2.linux-image-generic/hirsute,now 5.8.0.25.30 amd64 [installed,upgradable to: 5.8.0.30.32+21.04.34] Even after rebooting several time update doesn't install ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: apt 2.1.11 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu53 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt Date: Thu Nov 19 20:18:04 2020 InstallationDate: Installed on 2020-11-19 (0 days ago) InstallationMedia: Lubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201118) SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1904870/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1903048] Re: [SRU] Bluetooth won't activate on the pi 400
I've just used a fresh image of Mate 20.10 and used -proposed and done a full update and reboot. My bluetooth mouse, headphones and external keyboard are working fine now with this build so this bug has been fixed for me. Thank you all for your efforts in getting it sorted Kind regards Tony -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1903048 Title: [SRU] Bluetooth won't activate on the pi 400 Status in bluez package in Ubuntu: Triaged Status in bluez source package in Groovy: Fix Committed Status in bluez source package in Hirsute: Triaged Bug description: [Impact] Without these patches, Bluetooth is inoperable on the recently released Raspberry Pi 400. [Test Case] * Boot the Ubuntu Desktop for Pi image on a Pi 400. * Start the Settings application and switch to the Bluetooth tab * Verify that Bluetooth is not enabled and attempting to activate it fails * Enable the -proposed repository for the release (groovy) * sudo apt update * sudo apt install bluez * sudo reboot * Start the Settings application and switch to the Bluetooth tab * Verify that Bluetooth is active and that Bluetooth devices (e.g. mice, mobile phones, headphones, etc.) can connect and operate correctly [Regression Potential] Extremely low (on groovy in particular, this has the same version of bluez as hirsute). The only significant risk is to non-Pi platforms or dongles which also use the Broadcom 43xx (or Cypress 305) chips for Bluetooth which might be inadvertently affected by these patches. [Original Description] The new Pi 400 has a slightly different Wifi/BT chip to the Pi4. Whilst wifi works happily, Bluetooth fails to operate. This doesn't appear to be an issue with either the firmware (the latest versions from upstream Raspbian have been tried), or the kernel (a known-good raspi kernel has been tested under Ubuntu), but with Bluez itself. Specifically, tracing the initialization with btmon on Raspbian and Ubuntu, the stack consistently fails when attempting to "Set Default PHY" on the latter. Curiously, under Ubuntu the adapter also appears to lack a MAC address. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1903048/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1902244] Re: Backport packages for 20.04.1 HWE stack
Hello Timo, or anyone else affected, Accepted libclc into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libclc/0.2.0+git20190827-7~ubuntu0.20.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: libclc (Ubuntu Focal) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1902244 Title: Backport packages for 20.04.1 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-11 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Invalid Status in libclc source package in Focal: Fix Committed Status in libdrm source package in Focal: Fix Committed Status in llvm-toolchain-11 source package in Focal: Fix Committed Status in mesa source package in Focal: Confirmed Status in xorg-server source package in Focal: Confirmed Bug description: [Impact] These are needed for 20.04.1 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. Check upgrade from stock bionic. [Regression potential] libdrm: very minimal chance for regressions llvm-11: a new package, no regression potential on it's own libclc: just a rebuild against the new llvm mesa: a new major release, but we'll pull the final stable release of 20.2.x series, so there shouldn't be any regressions left at that point xserver: a new point-release xorg drivers: modest updates, if any To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1902244/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1815101] Re: [master] Restarting systemd-networkd breaks keepalived, heartbeat, corosync, pacemaker (interface aliases are restarted)
Dear Eric Desrochers,
I add the PPA into my ubuntu 18.04 corosync/pacemaker service node.
Then I upgrade the following libnss-systemd libpam-systemd libsystemd0 libudev1
systemd systemd-sysv udev package.
But it still failed after re-connect the notwork.
The crmsh show as below:
ERROR: status: crm_mon (rc=107): Connection to cluster failed: Transport
endpoint is not connected.
I also check the dmesg but it seem ok.
e1000: enp0s8 NIC Link is Down
e1000: enp0s8 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
Could you describe more detail to help me figure out it is my mistake operation
or something wrong in my environment?
Thank you.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1815101
Title:
[master] Restarting systemd-networkd breaks keepalived, heartbeat,
corosync, pacemaker (interface aliases are restarted)
Status in netplan:
Confirmed
Status in heartbeat package in Ubuntu:
Won't Fix
Status in keepalived package in Ubuntu:
In Progress
Status in systemd package in Ubuntu:
In Progress
Status in keepalived source package in Xenial:
Confirmed
Status in systemd source package in Xenial:
Confirmed
Status in keepalived source package in Bionic:
Confirmed
Status in systemd source package in Bionic:
In Progress
Status in systemd source package in Disco:
Won't Fix
Status in systemd source package in Eoan:
Fix Released
Status in keepalived source package in Focal:
Confirmed
Status in systemd source package in Focal:
Fix Released
Bug description:
[impact]
- ALL related HA software has a small problem if interfaces are being
managed by systemd-networkd: nic restarts/reconfigs are always going
to wipe all interfaces aliases when HA software is not expecting it to
(no coordination between them.
- keepalived, smb ctdb, pacemaker, all suffer from this. Pacemaker is
smarter in this case because it has a service monitor that will
restart the virtual IP resource, in affected node & nic, before
considering a real failure, but other HA service might consider a real
failure when it is not.
[test case]
- comment #14 is a full test case: to have 3 node pacemaker, in that
example, and cause a networkd service restart: it will trigger a
failure for the virtual IP resource monitor.
- other example is given in the original description for keepalived.
both suffer from the same issue (and other HA softwares as well).
[regression potential]
- this backports KeepConfiguration parameter, which adds some
significant complexity to networkd's configuration and behavior, which
could lead to regressions in correctly configuring the network at
networkd start, or incorrectly maintaining configuration at networkd
restart, or losing network state at networkd stop.
- Any regressions are most likely to occur during networkd start,
restart, or stop, and most likely to involve missing or incorrect ip
address(es).
- the change is based in upstream patches adding the exact feature we
needed to fix this issue & it will be integrated with a netplan change
to add the needed stanza to systemd nic configuration file
(KeepConfiguration=)
[other info]
original description:
---
Configure netplan for interfaces, for example (a working config with
IP addresses obfuscated)
network:
ethernets:
eth0:
addresses: [192.168.0.5/24]
dhcp4: false
nameservers:
search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com,
phone.blah.com]
addresses: [10.22.11.1]
eth2:
addresses:
- 12.13.14.18/29
- 12.13.14.19/29
gateway4: 12.13.14.17
dhcp4: false
nameservers:
search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com,
phone.blah.com]
addresses: [10.22.11.1]
eth3:
addresses: [10.22.11.6/24]
dhcp4: false
nameservers:
search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com,
phone.blah.com]
addresses: [10.22.11.1]
eth4:
addresses: [10.22.14.6/24]
dhcp4: false
nameservers:
search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com,
phone.blah.com]
addresses: [10.22.11.1]
eth7:
addresses: [9.5.17.34/29]
dhcp4: false
optional: true
nameservers:
search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com,
phone.blah.com]
addresses: [10.22.11.1]
version: 2
Configure keepalived (again, a working config with IP addresses
obfuscated)
global_defs # Block id
{
notification_email {
[Touch-packages] [Bug 1904845] [NEW] [ASUS Vivo AIO V241DA_M241DA, Realtek ALC294, Speaker, Internal] fails after a while
Public bug reported: sounds stops after few seconds I tried to modify the list order of the sound cards as alsamixer was showing me that the chip ATI R6xx HDMI set as 0 HD-Audio Generic seems to have no output when the chip Realtek ALC294 set as 1 HD-Audio Generic displays all controls That's why I did edit /etc/modprobe.d/alsa-base.conf I also tried to change with sudo nano /etc/group audio:x:29:pulse to audio:x:29:cyrille as advised there https://fluoblog.wordpress.com/2008/01/13/resolution-des-problemes-de-son-sous-ubuntu/ but it didn't seem to have made any change as grep 'audio' /etc/group returns audio:x:29:pulse ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-53.59~18.04.1-generic 5.4.65 Uname: Linux 5.4.0-53-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Nov 19 09:57:10 2020 InstallationDate: Installed on 2020-11-05 (13 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: HD-Audio Generic - HD-Audio Generic Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: nov. 19 08:38:26 cyrille-ASUS-Vivo-AIO-V241DA-M241DA dbus-daemon[819]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.37' (uid=121 pid=1237 comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined") Symptom_Type: Sound works for a while, then breaks Title: [ASUS Vivo AIO V241DA_M241DA, Realtek ALC294, Speaker, Internal] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2020 dmi.bios.vendor: ASUSTeK COMPUTER INC. dmi.bios.version: V241DA.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: V241DA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 13 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnASUSTeKCOMPUTERINC.:bvrV241DA.300:bd05/18/2020:svnASUSTeKCOMPUTERINC.:pnASUSVivoAIOV241DA_M241DA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnV241DA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct13:cvr1.0: dmi.product.family: ASUS Vivo AIO dmi.product.name: ASUS Vivo AIO V241DA_M241DA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-11-19T09:44:02.150839 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1904845 Title: [ASUS Vivo AIO V241DA_M241DA, Realtek ALC294, Speaker, Internal] fails after a while Status in alsa-driver package in Ubuntu: New Bug description: sounds stops after few seconds I tried to modify the list order of the sound cards as alsamixer was showing me that the chip ATI R6xx HDMI set as 0 HD-Audio Generic seems to have no output when the chip Realtek ALC294 set as 1 HD-Audio Generic displays all controls That's why I did edit /etc/modprobe.d/alsa-base.conf I also tried to change with sudo nano /etc/group audio:x:29:pulse to audio:x:29:cyrille as advised there https://fluoblog.wordpress.com/2008/01/13/resolution-des-problemes-de-son-sous-ubuntu/ but it didn't seem to have made any change as grep 'audio' /etc/group returns audio:x:29:pulse ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-53.59~18.04.1-generic 5.4.65 Uname: Linux 5.4.0-53-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Nov 19 09:57:10 2020 InstallationDate: Installed on 2020-11-05 (13 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: HD-Audio Generic - HD-Audio Generic Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: nov. 19 08:38:26 cyrille-ASUS-Vivo-AIO-V241DA-M241DA dbus-daemon[819]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.37' (uid=121 pid=1237 comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined") Symptom_Type: Sound works for a while, then breaks Title: [ASUS Vivo AIO V241DA_M241DA, Realtek ALC294, Speaker, Internal] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2020
