[Bug 2064672] Re: [SRU] - fixes for apparmor on noble
@jjohansen Thank you very much for your detailed explanation! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064672 Title: [SRU] - fixes for apparmor on noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2064672/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064672] Re: [SRU] - fixes for apparmor on noble
Please forgive me as I am unfamiliar with Ubuntu's release process. What are the next steps to releasing this fix? And how soon could it appear in normal distribution? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064672 Title: [SRU] - fixes for apparmor on noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2064672/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062373] Re: 24.04 TPM backed FDE regression following snapd 2.62 update
I can confirm that updating from 23.10 to 24.04 also keeps the channel for pc-kernel at 23.10/stable. However the upgrade did install snapd 2.62 (which seems to work fine). Changing the channel for pc-kernel to 24/stable works fine though. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062373 Title: 24.04 TPM backed FDE regression following snapd 2.62 update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nullboot/+bug/2062373/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060412] [NEW] Gnome3 apps very slow
Public bug reported: Gnome3 apps became very slow. Even type in interminal. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.9-0ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Apr 7 21:39:03 2024 DisplayManager: gdm3 InstallationDate: Installed on 2023-07-21 (261 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) RelatedPackageVersions: mutter-common 42.9-0ubuntu7 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2023-07-23T12:30:16.555014 ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060412 Title: Gnome3 apps very slow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2060412/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969512] Re: Totem unable to play video: "The specified movie could not be found"
@Dave @XA Okay. It worked for me though. Just hope it wasn't a temporary fix. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969512 Title: Totem unable to play video: "The specified movie could not be found" To manage notifications about this bug go to: https://bugs.launchpad.net/totem/+bug/1969512/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969512] Re: Totem unable to play video: "The specified movie could not be found"
Run this command: sudo apt remove gstreamer1.0-vaapi Got my solution from this article, check it out too. https://www.makeuseof.com/things-to-do-after-upgrading-to-ubuntu-2204-lts/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969512 Title: Totem unable to play video: "The specified movie could not be found" To manage notifications about this bug go to: https://bugs.launchpad.net/totem/+bug/1969512/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958224] Re: brltty claiming cp210x devices on 22.04
> it's a bit unclear to me which entries there should be considered 'generic USB IDs'? They are marked "Generic Identifier", that's 0403:6001 10C4:EA60 10C4:EA80 > I also don't understand why those rules are debian specific See the diff between ./debian/brltty-udeb.udev.rules and ./Autostart/Udev/device.rules.in Note that in debian we use the udev rules *only* inside the installer. The current strategy in Debian is that in the installer we use udev rules to autodetect braille devices. But in the installed system we don't: when the user installs brltty, the user means that they have a Braille device and want to probe it, whether it uses a generic USB ID or not, i.e. we always start brltty > How does upstream handle the devices? When brltty is started it just always probes all devices. Its udev rules file always starts brltty, be it generic IDs or not. > We should stop installing brltty by default going forward That would align with the way it happens in Debian yes. Ideally the udev rules would be split so that the non-generic pieces get always installed to start brltty, and the generic pieces are installed only when necessary. That's a matter of actually spending time on implementing it. > we aren't going to respin ISOs on old serie for such changes and that wouldn't be a solution for already installed systems... Yes, rather disable the generic udev rules. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958224 Title: brltty claiming cp210x devices on 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1958224/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958224] Re: brltty claiming cp210x devices on 22.04
orca only suggests brltty, it's the *-desktop packages which seem to be recommending brltty. If Ubuntu really wants to install brltty by default, it should disable the udev entries for the generic USB IDs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958224 Title: brltty claiming cp210x devices on 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1958224/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968467] Re: CSD scripts do not work on jammy
Thanks, this w/a also worked for me. $ cat openssl.conf openssl_conf = openssl_init [openssl_init] ssl_conf = ssl_sect [ssl_sect] system_default = system_default_sect [system_default_sect] Options = UnsafeLegacyRenegotiation ~$ export OPENSSL_CONF=openssl.conf -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968467 Title: CSD scripts do not work on jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openconnect/+bug/1968467/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970039] Re: cannot disable Remote Desktop in Ubuntu 22.04
I uninstalled gnome-remote-desktop and it seems to be disabled, but I haven't actually checked the network connections. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970039 Title: cannot disable Remote Desktop in Ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/1970039/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970121] [NEW] sharing enabled by default on 22.04
Public bug reported: After install and first boot, sharing is enabled by default in Ubuntu 22.04. It should be disabled initially. I used the minimal install function and it seems to be related to gnome-remote-desktop. ** Affects: gnome-remote-desktop (Ubuntu) Importance: Undecided Status: New ** Information type changed from Private Security to Public ** Package changed: ubiquity (Ubuntu) => gnome-remote-desktop (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970121 Title: sharing enabled by default on 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/1970121/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1089389] Re: juju bootstrap fail behind a proxy when a gpg key must be imported
Thanks to all of you for sharing your experience. As I was facing the same issue due to which we have opened our https://gtavicecityapk.com/ from the last 2 weeks. And now the issue get fixed so I opened it after 2 weeks. The knowledge shared here is such awesome and brief. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1089389 Title: juju bootstrap fail behind a proxy when a gpg key must be imported To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1089389/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970011] [NEW] pulseaudio running but can't hear any sound
Public bug reported: ... ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.13 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sat Apr 23 00:50:09 2022 InstallationDate: Installed on 2022-04-06 (16 days ago) InstallationMedia: Xubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/25/2021 dmi.bios.release: 4.14 dmi.bios.vendor: coreboot dmi.bios.version: MrChromebox-4.14 dmi.board.name: Banon dmi.board.vendor: GOOGLE dmi.board.version: 1.0 dmi.chassis.type: 9 dmi.chassis.vendor: GOOGLE dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvncoreboot:bvrMrChromebox-4.14:bd07/25/2021:br4.14:efr0.0:svnGOOGLE:pnBanon:pvr1.0:rvnGOOGLE:rnBanon:rvr1.0:cvnGOOGLE:ct9:cvr:sku: dmi.product.family: Intel_Strago dmi.product.name: Banon dmi.product.version: 1.0 dmi.sys.vendor: GOOGLE modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2022-04-23T00:30:09.974603 ** Affects: pulseaudio (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/1970011 Title: pulseaudio running but can't hear any sound To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1970011/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968385] [NEW] [Banon, Intel Braswell HDMI, Digital Out, HDMI] No sound at all
Public bug reported: Can't hear any sound on my inbuilt speaker (but it works with lubuntu). Currently using xubuntu. Also cannot hear any sound in my headphones when plugged in, although volume control recognizes that headphones have been plugged in. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Fri Apr 8 18:54:56 2022 InstallationDate: Installed on 2022-04-06 (2 days ago) InstallationMedia: Xubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Digital Out, HDMI Symptom_Type: No sound at all Title: [Banon, Intel Braswell HDMI, Digital Out, HDMI] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/25/2021 dmi.bios.release: 4.14 dmi.bios.vendor: coreboot dmi.bios.version: MrChromebox-4.14 dmi.board.name: Banon dmi.board.vendor: GOOGLE dmi.board.version: 1.0 dmi.chassis.type: 9 dmi.chassis.vendor: GOOGLE dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvncoreboot:bvrMrChromebox-4.14:bd07/25/2021:br4.14:efr0.0:svnGOOGLE:pnBanon:pvr1.0:rvnGOOGLE:rnBanon:rvr1.0:cvnGOOGLE:ct9:cvr:sku: dmi.product.family: Intel_Strago dmi.product.name: Banon dmi.product.version: 1.0 dmi.sys.vendor: GOOGLE ** Affects: alsa-driver (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/1968385 Title: [Banon, Intel Braswell HDMI, Digital Out, HDMI] No sound at all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1968385/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968337] [NEW] package python-apt 2.0.0ubuntu0.20.04.7 failed to install/upgrade: installed python-apt package post-installation script subprocess returned error exit status 2
Public bug reported: my computer froze & i rebooted it and got this error ProblemType: Package DistroRelease: Ubuntu 20.04 Package: python-apt 2.0.0ubuntu0.20.04.7 Uname: Linux 5.16.11-76051611-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 AptOrdering: python-apt:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Apr 4 12:38:40 2022 ErrorMessage: installed python-apt package post-installation script subprocess returned error exit status 2 Python3Details: /usr/local/bin/python3.10, Python 3.10.3, unpackaged PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: python-apt Title: package python-apt 2.0.0ubuntu0.20.04.7 failed to install/upgrade: installed python-apt package post-installation script subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: python-apt (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968337 Title: package python-apt 2.0.0ubuntu0.20.04.7 failed to install/upgrade: installed python-apt package post-installation script subprocess returned error exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1968337/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968338] [NEW] package software-properties-common 0.99.9.8 failed to install/upgrade: new software-properties-common package pre-removal script subprocess returned error exit status 127
Public bug reported: my computer froze, i rebooted, and got this error ProblemType: Package DistroRelease: Ubuntu 20.04 Package: software-properties-common 0.99.9.8 Uname: Linux 5.16.11-76051611-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 AptOrdering: software-properties-common:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Apr 4 13:07:14 2022 ErrorMessage: new software-properties-common package pre-removal script subprocess returned error exit status 127 PackageArchitecture: all Python3Details: /usr/local/bin/python3.10, Python 3.10.3, unpackaged PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: software-properties Title: package software-properties-common 0.99.9.8 failed to install/upgrade: new software-properties-common package pre-removal script subprocess returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968338 Title: package software-properties-common 0.99.9.8 failed to install/upgrade: new software-properties-common package pre-removal script subprocess returned error exit status 127 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1968338/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968109] Re: "Apply changes" button remains disabled after selecting Wi-Fi driver in Software Sources
Forgot to add: the date in the screen record file is not correct because this laptop doesn't have a battery (that's on me; I'm working on that). I don't remember exactly when I took the screen record itself, but the recorded "last modified" time is April 2, 2022 at 7:33 PM. I transferred it to my smartphone offline (via cable) before transferring it to another computer (again via cable; it was the easy option for me) to send this bug report. This is the Ubuntu Studio 22.04 "beta" ISO, not a daily release. In Ubuntu Studio 21.10, I can get the correct time after I connect to the Internet, *because* I can do so. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968109 Title: "Apply changes" button remains disabled after selecting Wi-Fi driver in Software Sources To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1968109/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968109] [NEW] "Apply changes" button remains disabled after selecting Wi-Fi driver in Software Sources
Public bug reported: I'm testing the live USB of Ubuntu Studio 22.04 beta on a mid-2009 MacBook Pro. (Can't do a full install yet.) Wi-Fi doesn't work out of the box. What I expect to happen is something I can do successfully in Ubuntu Studio 21.10 (live USB). Wi-Fi also didn't work out of the box in that version. In KDE Settings I click on "Driver Manager", which automatically opens Software Sources (that's the only way I know how to get there). It finds and shows my [proprietary Broadcom] Wi-Fi driver; I click on it, then the "Apply Changes" button is enabled after a second or two. I click that, wait about half a minute with a progress bar in action below, and then the Wi-Fi options appear the notification area, allowing me to connect. I attached a screen record of what actually happens in Ubuntu Studio 22.04 beta (thankfully this distro comes with screen recording software out of the box). When I click on "Driver Manager", a "xterm" window (version 372-1ubuntu1 I think?) opens unexpectedly with some code showing up in it (the code is in the screen record), shortly before Software Sources (version 0.99.20) opens as expected. The same driver still appears on the list. When I click on the driver, it seems to still take that second or two to transition, with some more code appearing in "xterm", but the "Apply Changes" button never enables itself. It remains disabled so I can't click it. The "revert" button directly next to it is also disabled. Thus, I can't connect my computer to Wi-Fi in 22.04 beta. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: software-properties-qt 0.99.20 ProcVersionSignature: Ubuntu 5.15.0-22.22-lowlatency 5.15.19 Uname: Linux 5.15.0-22-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.468 CurrentDesktop: KDE Date: Fri Mar 18 17:00:53 2022 LiveMediaBuild: Ubuntu-Studio 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ** Attachment added: "Screen record of the process I do in Ubuntu Studio 21.10 to get my Wi-Fi driver working, but fails in 22.04." https://bugs.launchpad.net/bugs/1968109/+attachment/5577783/+files/vokoscreenNG-2022-03-18_16-35-55.mp4 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968109 Title: "Apply changes" button remains disabled after selecting Wi-Fi driver in Software Sources To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1968109/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967580] Re: Gnome not loading on boot after fresh install.
** Description changed: - After fresh install. I ma getting no login screen. Sreen blanks out. - Had to open command to submit bug. + After fresh install. I am getting no login screen. Screen blanks out. + Had to open command to submit bug. Was able to startx via command + prompt. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42~beta-1ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Apr 1 17:54:03 2022 DisplayManager: gdm3 GsettingsChanges: - + InstallationDate: Installed on 2022-04-01 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) ProcEnviron: - TERM=linux - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=linux + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash RelatedPackageVersions: mutter-common 42~beta-1ubuntu2 SourcePackage: gnome-shell 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/1967580 Title: Gnome not loading on boot after fresh install. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1967580/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967580] [NEW] Gnome not loading on boot after fresh install.
Public bug reported: After fresh install. I am getting no login screen. Screen blanks out. Had to open command to submit bug. Was able to startx via command prompt. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42~beta-1ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Apr 1 17:54:03 2022 DisplayManager: gdm3 GsettingsChanges: InstallationDate: Installed on 2022-04-01 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42~beta-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967580 Title: Gnome not loading on boot after fresh install. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1967580/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1954413] Re: firefox snap cannot be started: firefox already running
I have a similar issue (let me know if I should open a new bug): launching firefox for the first time (ie. while it's not running) works fine. But, once it's running, any further invocation of firefox fails with the "Firefox is already running..." dialog - for example, clicking on a url in a terminal, or running `firefox https://example.com`. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1954413 Title: firefox snap cannot be started: firefox already running To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1954413/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 874181] Re: brltty daemon prevents creation of ttyUSB0 device link
Yes, unfortunately there is no way to fix it in that case. The udev rules properly avoid starting brltty when the iManufacturer field is changed from FTDI to the actual manufacturer of the device, but not when it is left to FTDI. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/874181 Title: brltty daemon prevents creation of ttyUSB0 device link To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/874181/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958224] Re: brltty claiming cp210x devices on 22.04
> In this case, brltty appeared (or at least the device claim) after a dist-upgrade Ah, do you happen to have a log of that dist-upgrade, so we can determine what brought it in? > It still feels very bad form for a vendor device to use the default VID/PID of the underlying converter chip Yes. Unfortunately that's what they have done, those devices are out there, and people have already bought them (and they cost a lot of money) :( -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958224 Title: brltty claiming cp210x devices on 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1958224/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958224] Re: brltty claiming cp210x devices on 22.04
Debian is installing the brltty package only when brltty was used during installation. Brltty gets started during installation either through the udev rules, or started manually from the kernel command line. The finish-install script just checks out /var/run/brltty.pid to determine whether a brltty is running. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958224 Title: brltty claiming cp210x devices on 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1958224/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964808] [NEW] Wifi keeps disconnecting
Public bug reported: I have a box with 802-11n and I run into a problem with my Lenovo laptop : - when I change the wifi password, it connects immediately and works well - the next time (for example after switching the airplane mode on and off), it fails and the network manager keeps asking me the password again and again Please notice that I have no problem with other wifi access points (when going in other places with my laptop), and my box works well with every other devices (ubuntu laptops, android phones) but mine ! My laptop runs an updated 20.04.4, but the problem first came when I was on 21.04. I then made a fresh install of 21.10 and then a fresh install on 20.04 just to make sure the kernel was not involved. Even tried the last Intel Clear Linux without success. As a workaround, I tried to stop and restart wpa_supplicant: sudo systemctl disable --now wpa_supplicant.service sudo systemctl enable --now wpa_supplicant.service but this did not solve the problem. I also contacted the support of my ISP and they made a clear reset of my box without success. Here is what I see in dmesg : [ 4203.366374] wlp4s0: authenticate with e4:9e:12:8c:8e:1a [ 4203.374010] wlp4s0: send auth to e4:9e:12:8c:8e:1a (try 1/3) [ 4203.378464] wlp4s0: authenticated [ 4203.383534] wlp4s0: associate with e4:9e:12:8c:8e:1a (try 1/3) [ 4203.387408] wlp4s0: RX AssocResp from e4:9e:12:8c:8e:1a (capab=0x1411 status=0 aid=6) [ 4203.391628] wlp4s0: associated [ 4203.399358] wlp4s0: deauthenticating from e4:9e:12:8c:8e:1a by local choice (Reason: 17=IE_DIFFERENT) And here is the restult of lspci : 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers (rev 02) 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 620 (rev 02) 00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model 00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller (rev 21) 00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP Thermal subsystem (rev 21) 00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME HECI #1 (rev 21) 00:1c.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #1 (rev f1) 00:1c.2 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #3 (rev f1) 00:1c.4 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #5 (rev f1) 00:1d.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #9 (rev f1) 00:1f.0 ISA bridge: Intel Corporation Sunrise Point-LP LPC Controller (rev 21) 00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21) 00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21) 00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21) 00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (4) I219-V (rev 21) 02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI Express Card Reader (rev 01) 04:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 88) 05:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM961/PM961 ** Affects: network-manager (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/1964808 Title: Wifi keeps disconnecting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1964808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 527200] Re: accerciser crashed with LookupError in _inner()
*** This bug is a duplicate of bug 526398 *** https://bugs.launchpad.net/bugs/526398 ** This bug has been marked a duplicate of bug 526398 accerciser crashed with LookupError in _inner() -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/527200 Title: accerciser crashed with LookupError in _inner() To manage notifications about this bug go to: https://bugs.launchpad.net/accerciser/+bug/527200/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 718572] Re: accerciser crashed with LookupError in _inner()
*** This bug is a duplicate of bug 526398 *** https://bugs.launchpad.net/bugs/526398 ** This bug has been marked a duplicate of bug 526398 accerciser crashed with LookupError in _inner() -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/718572 Title: accerciser crashed with LookupError in _inner() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accerciser/+bug/718572/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958224] Re: brltty claiming cp210x devices on 22.04
Yes, but it is meant to be so: the Seika Braille device is announced as such, so we have to recognize such devices in brltty, otherwise the Seika Braille devices would not work at all. The question is rather: why is brltty installed on your system? It is supposed to be installed only if you installed your system with a Braille device connected. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958224 Title: brltty claiming cp210x devices on 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1958224/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1757689] Re: Please port your package away from Qt 4
I apologize if this is the wrong place to put this, but it appears the Qt 5 version of this package (or its equivalent) is called "ffmpegthumbs" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1757689 Title: Please port your package away from Qt 4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kffmpegthumbnailer/+bug/1757689/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950488] Re: brltty ftbfs in jammy
Ah, the patch is already in brltty 6.4 actually, so no change on the Debian side actually :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950488 Title: brltty ftbfs in jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1950488/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950488] Re: brltty ftbfs in jammy
Ok, thanks! The corresponding commit upstream is e6ed2372887ac0106db8854f70e9b2fdcadec74f, attached here, could somebody check that this fixes the build issue on Ubuntu? I'll then integrate the patch in Debian as well. ** Attachment added: "patch" https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1950488/+attachment/5541197/+files/patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950488 Title: brltty ftbfs in jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1950488/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950488] Re: brltty ftbfs in jammy
> it is probably newer python versions being stricter with the use of non existing options? The --without-viavoice is not passed to the python bindings, so that cannot be the problem. That said I have now dropped the option from debian/rules, thanks :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950488 Title: brltty ftbfs in jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1950488/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950488] Re: brltty ftbfs in jammy
Please provide the whole build log. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950488 Title: brltty ftbfs in jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1950488/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945180] Re: vrf: fix refcnt leak with vxlan slaves
** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945180 Title: vrf: fix refcnt leak with vxlan slaves To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945180/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945180] Re: vrf: fix refcnt leak with vxlan slaves
Hi Kelsey, sorry, I missed the notification, I'll take care of it right away. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945180 Title: vrf: fix refcnt leak with vxlan slaves To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945180/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945180] Re: vrf: fix refcnt leak with vxlan slaves
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945180 Title: vrf: fix refcnt leak with vxlan slaves To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945180/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1035208] Re: touchpad stops working (moving the pointer doesn't work)
** Also affects: archlinux 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/1035208 Title: touchpad stops working (moving the pointer doesn't work) To manage notifications about this bug go to: https://bugs.launchpad.net/ac100/+bug/1035208/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942459] Re: Speakup modules not included in Hirsute kernel
> Enabling CONFIG_ACCESSIBILITY could affect console output No it won't: no source code uses CONFIG_ACCESSIBILITY. CONFIG_ACCESSIBILITY only enables the accessibility configuration menu which allows enabling speakup. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942459 Title: Speakup modules not included in Hirsute kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942459/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944472] Re: Bug configuration monitor
** 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/1944472 Title: Bug configuration monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944472/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944472] [NEW] Bug configuration monitor
Public bug reported: Bug in the monitor settings, when clicking on the icon it does not open making it impossible to change the monitor configuration. Ex: Monitor resolution, position change and wallpaper. 5.11.0-36-generic #40~20.04.1-Ubuntu SMP Sat Sep 18 02:14:19 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944472 Title: Bug configuration monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944472/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1417160] Re: aeskeyfind doesn´t work as expected on big files
** Changed in: aeskeyfind (Ubuntu) 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/1417160 Title: aeskeyfind doesn´t work as expected on big files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aeskeyfind/+bug/1417160/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838334] Re: aeskeyfind problem with constraints results
** Bug watch added: Debian Bug tracker #989179 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989179 ** Also affects: aeskeyfind (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989179 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838334 Title: aeskeyfind problem with constraints results To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aeskeyfind/+bug/1838334/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930584] Re: InstallProgress is not being used as a context manager
Ok, thanks Julian. For future reference, which was the proper place to report this bug? Here or over at bugs.debian? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930584 Title: InstallProgress is not being used as a context manager To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1930584/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930584] Re: InstallProgress is not being used as a context manager
Also reported to debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989389 ** Bug watch added: Debian Bug tracker #989389 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989389 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930584 Title: InstallProgress is not being used as a context manager To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1930584/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930584] [NEW] InstallProgress is not being used as a context manager
Public bug reported: Package: python3-apt Version: 2.2.0 As can be seen in the constructor, InstallProgress is designed to be used in a 'with' in order to properly close write_stream and status_stream: https://git.launchpad.net/python-apt/tree/apt/progress/base.py#n163 This commit added support for using InstallProgress as a context manager: https://git.launchpad.net/python- apt/commit/?id=462c05b39eae5a0fa2270d329b03d4711742f20d It also modified a test, but didn't change the way InstallProgress is used by cache.py. This causes Python 3 to complain that InstallProgress's constructor leaves unclosed files: > /usr/lib/python3.9/glob.py:123: ResourceWarning: unclosed file > <_io.TextIOWrapper name=4 mode='r' encoding='UTF-8'> > with os.scandir(dirname) as it: > Object allocated at (most recent call last): > File "/opt/thinlinc/modules/thinlinc/packageinstaller/__init__.py", lineno > 33 > OOO0o000 = globals ( ) [ IIi1i111IiII ] . Backend ( ) > File "/opt/thinlinc/modules/thinlinc/packageinstaller/aptbackend.py", > lineno 88 > self . _aptcallback = i1Ii1i ( self ) > File "/opt/thinlinc/modules/thinlinc/packageinstaller/aptbackend.py", > lineno 31 > super ( ) . __init__ ( ) > File "/usr/lib/python3/dist-packages/apt/progress/base.py", lineno 164 > self.status_stream = os.fdopen(self.statusfd, "r") # type: io.TextIOBase > # noqa > File "/usr/lib/python3.9/os.py", lineno 1023 > return io.open(fd, *args, **kwargs) > /usr/lib/python3.9/glob.py:123: ResourceWarning: unclosed file > <_io.TextIOWrapper name=5 mode='w' encoding='UTF-8'> > with os.scandir(dirname) as it: > Object allocated at (most recent call last): > File "/opt/thinlinc/modules/thinlinc/packageinstaller/__init__.py", lineno > 33 > OOO0o000 = globals ( ) [ IIi1i111IiII ] . Backend ( ) > File "/opt/thinlinc/modules/thinlinc/packageinstaller/aptbackend.py", > lineno 88 > self . _aptcallback = i1Ii1i ( self ) > File "/opt/thinlinc/modules/thinlinc/packageinstaller/aptbackend.py", > lineno 31 > super ( ) . __init__ ( ) > File "/usr/lib/python3/dist-packages/apt/progress/base.py", lineno 163 > self.write_stream = os.fdopen(self.writefd, "w") # type: io.TextIOBase > File "/usr/lib/python3.9/os.py", lineno 1023 > return io.open(fd, *args, **kwargs) The issue was identified on Ubuntu 21.04: > Linux ubuntu2104 5.11.0-17-generic #18-Ubuntu SMP Thu May 6 20:10:11 > UTC 2021 x86_64 x86_64 x86_64 GNU/Linux ** Affects: python-apt (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/1930584 Title: InstallProgress is not being used as a context manager To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1930584/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904480] Re: RTL8822CE Realtek Wi-Fi dropping connection
Bug also occurring on Ubuntu 20.04 LTS, kernel 5.8.0-53-generic. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904480 Title: RTL8822CE Realtek Wi-Fi dropping connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928996] Re: [X58A-UD3R, Nvidia GPU 84 HDMI/DP, Digital Out, HDMI] No sound at all after resuming from suspend
Just woke up from a suspend once again and still getting this issue. The most recent log lines are May 19 17:30:18 skainswo-X58A-UD3R systemd[1798]: Starting Sound Service... May 19 17:30:18 skainswo-X58A-UD3R systemd[1798]: Started Sound Service. May 19 17:30:27 skainswo-X58A-UD3R pulseaudio[1811]: GetManagedObjects() failed: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) May 19 17:33:38 skainswo-X58A-UD3R pulseaudio[1811]: ALSA woke us up to write new data to the device, but there was actually nothing to write. May 19 17:33:38 skainswo-X58A-UD3R pulseaudio[1811]: Most likely this is a bug in the ALSA driver 'snd_hda_intel'. Please report this issue to the ALSA developers. May 19 17:33:38 skainswo-X58A-UD3R pulseaudio[1811]: We were woken up with POLLOUT set -- however a subsequent snd_pcm_avail() returned 0 or another value < min_avail. But these logs are from two days ago... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928996 Title: [X58A-UD3R, Nvidia GPU 84 HDMI/DP, Digital Out, HDMI] No sound at all after resuming from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1928996/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928996] Re: [X58A-UD3R, Nvidia GPU 84 HDMI/DP, Digital Out, HDMI] No sound at all after resuming from suspend
As a quick update, I managed to kill all of the spurious pulseaudio processes that had been lying around as a result of `pulseaudio -k && pulseaudio --start` and got the systemd pulseaudio process back on its feet. Then I confirmed that the audio worked, suspended my system, and woke it up again and the audio still works! Therefore I suspect that pulseaudio processes started by the user in terminal sessions (daemonized) do not survive the suspend/resume cycle for some reason(?). How the systemd pulseaudio process failed to begin with remains the larger issue, however. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928996 Title: [X58A-UD3R, Nvidia GPU 84 HDMI/DP, Digital Out, HDMI] No sound at all after resuming from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1928996/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928996] [NEW] [X58A-UD3R, Nvidia GPU 84 HDMI/DP, Digital Out, HDMI] No sound at all after resuming from suspend
Public bug reported: Sound works fine after an initial boot up, but fails after resuming from a suspend. Going to the "Sound" section in the Settings app, I no longer see the HDMI device presented as an output option when this occurs. I suspect this is due to issues with pulseaudio. At least, running `pulseaudio -k && pulseaudio --start`, then restarting apps seems to fix the issue. In particular I've found that the pulseaudio systemd service has failed after resuming from suspend. After scanning through journalctl, there are a few suspect sections. I've attached the logs in their entirety, and an abbreviated log with only sections that I found interesting. I cannot be sure which are at fault, but hopefully it helps narrow the search. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106 Uname: Linux 5.4.0-73-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: skainswo 2282708 F pulseaudio /dev/snd/controlC0: skainswo 2282708 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 19 16:08:41 2021 InstallationDate: Installed on 2020-05-15 (369 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=en_US.UTF-8 SHELL=/home/username/.nix-profile/bin/zsh SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:NVidia failed Symptom_Card: GP106 High Definition Audio Controller - HDA NVidia Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: skainswo 2282708 F pulseaudio /dev/snd/controlC0: skainswo 2282708 F pulseaudio Symptom_Jack: Digital Out, HDMI Symptom_Type: No sound at all Title: [X58A-UD3R, Nvidia GPU 84 HDMI/DP, Digital Out, HDMI] No sound at all UpgradeStatus: Upgraded to focal on 2020-08-08 (284 days ago) dmi.bios.date: 04/20/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: FA dmi.board.name: X58A-UD3R dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrFA:bd04/20/2010:svnGigabyteTechnologyCo.,Ltd.:pnX58A-UD3R:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnX58A-UD3R:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: X58A-UD3R dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages ** Attachment added: "pulseaudio-logs.zip" https://bugs.launchpad.net/bugs/1928996/+attachment/5498825/+files/pulseaudio-logs.zip -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928996 Title: [X58A-UD3R, Nvidia GPU 84 HDMI/DP, Digital Out, HDMI] No sound at all after resuming from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1928996/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1889416] Re: pulseaudio.service: Start request repeated too quickly.
As a workaround, you can try to edit the systemd file "/usr/lib/systemd/user/pulseaudio.service" and add the line: ``` RestartSec=2s ``` Your [Service] section would look like to this: ``` [Service] ExecStart=/usr/bin/pulseaudio --daemonize=no --log-target=journal LockPersonality=yes MemoryDenyWriteExecute=yes NoNewPrivileges=yes Restart=on-failure RestartSec=2s RestrictNamespaces=yes SystemCallArchitectures=native SystemCallFilter=@system-service # Note that notify will only work if --daemonize=no Type=notify UMask=0077 ``` Samuel -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1889416 Title: pulseaudio.service: Start request repeated too quickly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fscrypt/+bug/1889416/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916722] Re: Pulseaudio fails to start after reboot if home partition is encrypted
Hi Anton, As a workaround, you can try to edit the systemd file "/usr/lib/systemd/user/pulseaudio.service" and add the line: ``` RestartSec=2s ``` Your [Service] section would look like to this: ``` [Service] ExecStart=/usr/bin/pulseaudio --daemonize=no --log-target=journal LockPersonality=yes MemoryDenyWriteExecute=yes NoNewPrivileges=yes Restart=on-failure RestartSec=2s RestrictNamespaces=yes SystemCallArchitectures=native SystemCallFilter=@system-service # Note that notify will only work if --daemonize=no Type=notify UMask=0077 ``` Samuel -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916722 Title: Pulseaudio fails to start after reboot if home partition is encrypted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1916722/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917474] [NEW] Vaio touchpad dont work properly
Public bug reported: I'm a Vaio user and my touchpad do not work at all OS boots. Sometimes the touchpad initialize with system but stop to work after a variate time lapse (5 minutes or 5 hours). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-44-generic 5.8.0-44.50~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Mar 2 11:46:27 2021 InstallationDate: Installed on 2020-12-09 (83 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) 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/1917474 Title: Vaio touchpad dont work properly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1917474/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916110] [NEW] package mysql-server-8.0 8.0.23-0ubuntu0.20.04.1 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1
Public bug reported: ock /var/lib/dpkg/lock-frontend. It is heWaiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is heWaiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is heWaiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is heWaiting for cache lock: Could not get lock /var/lib/dpkg/lock- frontend. It is heWaiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is heWaiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is heWaiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is heWaiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is heWaiting for cache lock: Could not get lock /var/lib/dpkg/lock- frontend. It is heWaiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is heWaiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is heWaiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is heWaiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is heWaiting for cache lock: Could not get lock /var/lib/dpkg/lock- frontend. It is heWaiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is heWaiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is heWaiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is heWaiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is heWaiting for cache lock: Could not get lock /var/lib/dpkg/lock- frontend. It is heWaiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is heWaiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is heWaiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is heWaiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is heWaiting for cache lock: Could not get lock /var/lib/dpkg/lock- frontend. It is heWaiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is heWaiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is heWaiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is heWaiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is heWaiting for cache lock: Could not get lock /var/lib/dpkg/lock- frontend. It is heWaiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is heWaiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is heWaiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is heWaiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is heWaiting for cache lock: Could not get lock /var/lib/dpkg/lock- frontend. It is heWaiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is heWaiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is heWaiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is heWaiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is heWaiting for cache lock: Could not get lock /var/lib/dpkg/lock- frontend. It is heWaiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is heWaiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is heWaiting for cache lock: Could not get lock /var/lib/dpkg/lock-f ProblemType: Package DistroRelease: Ubuntu 20.04 Package: mysql-server-8.0 8.0.23-0ubuntu0.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 Date: Thu Feb 18 13:42:16 2021 ErrorMessage: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2021-02-16 (2 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Logs.var.log.daemon.log: MySQLConf.etc.mysql.conf.d.mysql.cnf: [mysql] MySQLConf.etc.mysql.conf.d.mysqldump.cnf: [mysqldump] quick quote-names max_allowed_packet = 16M MySQLVarLibDirListing: ['#innodb_temp', 'client-key.pem', 'ib_buffer_pool', 'ibtmp1', 'debian-5.7.flag', 'binlog.08', 'ib_logfile0', 'ibdata1', 'mysql.ibd', 'sys', 'undo_001', 'binlog.02', 'public_key.pem', 'performance_schema', '#ib_16384_1.dblwr', 'binlog.01', 'binlog.05', 'ca.pem', 'private_key.pem', '#ib_16384_0.dblwr', 'ib_logfile1', 'binlog.04', 'covid_project', 'binlog.06', 'binlog.03', 'ca-key.pem', 'client-cert.pem', 'auto.cnf', 'server-key.pem', 'server-cert.pem', 'mysql', 'wdsamuel-Inspiron-14-3467.pid', 'binlog.09', 'binlog.07', 'undo_002', 'binlog.index'] ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.8.0-43-generic root=UUID=240f372f-ab2d-4586-b48b-c7cb5967a9c6 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2
[Bug 1085]
Yea, I realized that edit as new works for my purposes after writing the above comment. The show source feature displays things correctly, UTF-8 characters should be encoded during transmission and thus should be encoded in the source but the address input field does not handle that kind of encoding. Is there any way to add this workaround to these bugs in a little more visible location? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1085 Title: selecting text in full header mode fails To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1085/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1085]
While waiting for this to be fixed could we have a button "new email to all recipients", possibly behind the "more" menu/button, since that probably is one main use of the copy feature. By the way, the workaround to open the source and copy / paste from there does not work well when UTF8 characters are involved. Pasting what is copied from the message source into the address field does not convert the encoded character back, it shows the encoding. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1085 Title: selecting text in full header mode fails To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1085/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911056] Re: BCM4331 not working in Macbook Pro 2012
Please delete this report! BCM4331 is working fine again! ** Changed in: ubuntu Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1911056 Title: BCM4331 not working in Macbook Pro 2012 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1911056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911056] [NEW] BCM4331 not working in Macbook Pro 2012
Public bug reported: Deleting module version: 6.30.223.271+bdcom completely from the DKMS tree. -- Done. Loading new bcmwl-6.30.223.271+bdcom DKMS files... Building for 5.8.0-36-generic Building for architecture x86_64 Building initial module for 5.8.0-36-generic ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/bcmwl-kernel-source.0.crash' Error! Bad return status for module build on kernel: 5.8.0-36-generic (x86_64) Consult /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/make.log for more information. dpkg: error processing package bcmwl-kernel-source (--configure): installed bcmwl-kernel-source package post-installation script subprocess returned error exit status 10 Errors were encountered while processing: bcmwl-kernel-source E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firmware-b43-installer 1:019-4 ProcVersionSignature: Ubuntu 5.8.0-36.40~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-36-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jan 11 21:44:57 2021 InstallationDate: Installed on 2020-10-25 (78 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: b43-fwcutter UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1911056 Title: BCM4331 not working in Macbook Pro 2012 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1911056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 520546] Re: [SRU]Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right
It seems I have to insist again: patch https://launchpadlibrarian.net/405256420/patch should definitely really really be applied. As explained in https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1508146/comments/73 that script should really *not* pass --force to setupcon. There is no reason for that except that it was copy/pasted from the Debian installer, where it is needed due to the use of bterm. On Ubuntu it should really not be used. Can somebody at last apply that patch that has been waiting for 2 years? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/520546 Title: [SRU]Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/520546/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905787] [NEW] package linux-firmware 1.187.6 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1
Public bug reported: Migrating from 18.04.05 to 20.04.1 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.6 ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73 Uname: Linux 5.4.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ba033462279 F pulseaudio /dev/snd/controlC0: ba033462279 F pulseaudio CasperMD5CheckResult: skip Date: Thu Nov 26 15:29:42 2020 Dependencies: ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 HibernationDevice: RESUME=UUID=bdfb5b60-2f66-45e6-a1fc-7c87d5f3867d InstallationDate: Installed on 2017-08-20 (1194 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: System manufacturer System Product Name PackageArchitecture: all ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-56-generic root=UUID=66854b36-6a3e-46f6-930d-2c9ca2f26faf ro PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: grub-pc N/A SourcePackage: linux-firmware Title: package linux-firmware 1.187.6 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/22/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0906 dmi.board.asset.tag: Default string dmi.board.name: STRIX Z270E GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0906:bd03/22/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSTRIXZ270EGAMING:rvrRev1.xx: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: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal package-from-proposed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905787 Title: package linux-firmware 1.187.6 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1905787/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905770] [NEW] package linux-firmware 1.187.5 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1
Public bug reported: Migration de UBUNTU 18.04.05 (LTS) vers UBUNTU 20.04.01 (LTS) ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.5 ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73 Uname: Linux 5.4.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 AptOrdering: linux-firmware:amd64: Install xdg-utils:amd64: Install NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ba033462280 F pulseaudio /dev/snd/controlC0: ba033462280 F pulseaudio CasperMD5CheckResult: skip Date: Thu Nov 26 13:16:19 2020 Dependencies: ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 HibernationDevice: RESUME=UUID=bdfb5b60-2f66-45e6-a1fc-7c87d5f3867d InstallationDate: Installed on 2017-08-20 (1194 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: System manufacturer System Product Name PackageArchitecture: all ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-56-generic root=UUID=66854b36-6a3e-46f6-930d-2c9ca2f26faf ro PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: grub-pc N/A SourcePackage: linux-firmware Title: package linux-firmware 1.187.5 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/22/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0906 dmi.board.asset.tag: Default string dmi.board.name: STRIX Z270E GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0906:bd03/22/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSTRIXZ270EGAMING:rvrRev1.xx: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: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal package-from-proposed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905770 Title: package linux-firmware 1.187.5 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1905770/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905195] Re: package linux-firmware 1.187.4 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1
Upgrade from Ubuntu 18-04 (LTS) to 20.04 (LTS). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905195 Title: package linux-firmware 1.187.4 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1905195/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905195] Re: package linux-firmware 1.187.4 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1
Upgrade from Ubuntu 18-04 (LTS) to 20.04 (LTS). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905195 Title: package linux-firmware 1.187.4 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1905195/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905195] Re: package linux-firmware 1.187.4 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1
Upgrade from Ubuntu 18-04 (LTS) to 20.04 (LTS). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905195 Title: package linux-firmware 1.187.4 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1905195/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905195] Re: package linux-firmware 1.187.4 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1
Upgrade from Ubuntu 18-04 (LTS) to 20.04 (LTS). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905195 Title: package linux-firmware 1.187.4 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1905195/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905195] Re: package linux-firmware 1.187.4 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1
Upgrade from Ubuntu 18-04 (LTS) to 20.04 (LTS). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905195 Title: package linux-firmware 1.187.4 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1905195/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905195] Re: package linux-firmware 1.187.4 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1
Upgrade from Ubuntu 18-04 (LTS) to 20.04 (LTS). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905195 Title: package linux-firmware 1.187.4 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1905195/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905195] Re: package linux-firmware 1.187.4 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1
Upgrade from Ubuntu 18-04 (LTS) to 20.04 (LTS). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905195 Title: package linux-firmware 1.187.4 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1905195/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905195] Re: package linux-firmware 1.187.4 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1
Upgrade from Ubuntu 18-04 (LTS) to 20.04 (LTS). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905195 Title: package linux-firmware 1.187.4 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1905195/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905195] [NEW] package linux-firmware 1.187.4 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1
Public bug reported: Upgrade from Ubuntu 18-04 (LTS) to 20.04 (LTS). ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.4 ProcVersionSignature: Ubuntu 4.15.0-125.128-generic 4.15.18 Uname: Linux 4.15.0-125-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gdm1660 F pulseaudio ba03346 13324 F pulseaudio /dev/snd/controlC0: gdm1660 F pulseaudio ba03346 13324 F pulseaudio CasperMD5CheckResult: skip Date: Sun Nov 22 13:51:18 2020 Dependencies: ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 HibernationDevice: RESUME=UUID=bdfb5b60-2f66-45e6-a1fc-7c87d5f3867d InstallationDate: Installed on 2017-08-20 (1190 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: System manufacturer System Product Name PackageArchitecture: all ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-125-generic root=UUID=66854b36-6a3e-46f6-930d-2c9ca2f26faf ro PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: grub-pc N/A SourcePackage: linux-firmware Title: package linux-firmware 1.187.4 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/22/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0906 dmi.board.asset.tag: Default string dmi.board.name: STRIX Z270E GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0906:bd03/22/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSTRIXZ270EGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905195 Title: package linux-firmware 1.187.4 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1905195/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905194] Re: package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1
Upgrading from 18.04 to 20.04 (LTS) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905194 Title: package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1905194/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905194] Re: package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1
Upgrading from 18.04 to 20.04 (LTS) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905194 Title: package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1905194/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905194] [NEW] package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1
Public bug reported: Upgrading from 18.04 to 20.04 (LTS) ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6.3 ProcVersionSignature: Ubuntu 4.15.0-125.128-generic 4.15.18 Uname: Linux 4.15.0-125-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Nov 22 12:04:13 2020 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2017-08-20 (1190 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905194 Title: package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1905194/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904508] [NEW] package firmware-b43legacy-installer 1:019-4 failed to install/upgrade: el subproceso instalado paquete firmware-b43legacy-installer script post-installation devolvió el código de
Public bug reported: intento hacer que funcione el wifi en mi laptop lenovo idepad 330 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: firmware-b43legacy-installer 1:019-4 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 AptOrdering: firmware-b43legacy-installer:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Nov 16 23:41:28 2020 ErrorMessage: el subproceso instalado paquete firmware-b43legacy-installer script post-installation devolvió el código de salida de error 1 InstallationDate: Installed on 2020-11-13 (3 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: b43-fwcutter Title: package firmware-b43legacy-installer 1:019-4 failed to install/upgrade: el subproceso instalado paquete firmware-b43legacy-installer script post-installation devolvió el código de salida de error 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: b43-fwcutter (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904508 Title: package firmware-b43legacy-installer 1:019-4 failed to install/upgrade: el subproceso instalado paquete firmware-b43legacy- installer script post-installation devolvió el código de salida de error 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/b43-fwcutter/+bug/1904508/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1095751] Re: bcmwl fails to build with 3.8 kernels [error: 'struct cfg80211_ibss_params' has no member named 'channel']
** Changed in: broadcom-sta (Ubuntu) Status: Triaged => Incomplete ** Changed in: broadcom-sta (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1095751 Title: bcmwl fails to build with 3.8 kernels [error: 'struct cfg80211_ibss_params' has no member named 'channel'] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1095751/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893511] Re: espeak cannot find voice file for mbrola-br2
This works with espeak-ng, so not a bug in mbrola-br2 but in espeak -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893511 Title: espeak cannot find voice file for mbrola-br2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mbrola-br2/+bug/1893511/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 483928] Re: ssh-keyscan(1) exits prematurely on some non-fatal errors
8 years later, we saw this on one of our customer's systems. Looking at the status of this entry, it looks like it's still unresolved? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/483928 Title: ssh-keyscan(1) exits prematurely on some non-fatal errors To manage notifications about this bug go to: https://bugs.launchpad.net/openssh/+bug/483928/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898135] [NEW] Sound crackles and rewinds for 1 millisecond, periodically
Public bug reported: Using Lubuntu, Bug began not too long ago, fine before then, short sounds are fine. Discovered bug using YouTube ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pulseaudio 1:13.0-1ubuntu1.2 ProcVersionSignature: Ubuntu 5.3.0-64.58-generic 5.3.18 Uname: Linux 5.3.0-64-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: admin 1391 F pulseaudio /dev/snd/pcmC0D0p: admin 1391 F...m pulseaudio CurrentDesktop: LXQt Date: Fri Oct 2 09:46:45 2020 InstallationDate: Installed on 2019-12-27 (279 days ago) InstallationMedia: Lubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Right Symptom_PulseAudioLog: Oct 01 16:00:36 admin-pc dbus-daemon[804]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.41' (uid=1000 pid=1391 comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined") Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [350V5C/350V5X/350V4C/350V4X/351V5C/351V5X/351V4C/351V4X/3540VC/3540VX/3440VC/3440VX, Realtek ALC269VC, Black Headphone Out, Right] Underruns, dropouts or crackling sound UpgradeStatus: Upgraded to eoan on 2020-05-17 (137 days ago) dmi.bios.date: 06/30/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P04AAL dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: NP350V5C-S02AU dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: BOARD REVISION 00 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP04AAL:bd06/30/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pn350V5C/350V5X/350V4C/350V4X/351V5C/351V5X/351V4C/351V4X/3540VC/3540VX/3440VC/3440VX:pvrP04AAL.022.CP:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP350V5C-S02AU:rvrBOARDREVISION00:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.family: Eureka dmi.product.name: 350V5C/350V5X/350V4C/350V4X/351V5C/351V5X/351V4C/351V4X/3540VC/3540VX/3440VC/3440VX dmi.product.sku: P04AAL.022.CP dmi.product.version: P04AAL.022.CP dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. ** Affects: ubuntu Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898135 Title: Sound crackles and rewinds for 1 millisecond, periodically To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1898135/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1884398] Re: pulseaudio
Ah, okay, sorry about that. On Sun, Jun 21, 2020 at 5:01 AM Julian Andres Klode < 1884...@bugs.launchpad.net> wrote: > No, this error happened when you were (re)installing the bootloader, and > there is no error message in the log. > > Maybe /var/log/apt/term.log provides more info, but so far it's not > clear what's going on. > > ** Changed in: shim-signed (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1884398 > > Title: > pulseaudio > > Status in shim-signed package in Ubuntu: > Incomplete > > Bug description: > I was trying to fix my crakling, static-filled audio by running some > pulseaudio commands in the console. The sound settings gui was open, > and I think this error appeared when I tried to open a dropdown > > ProblemType: Package > DistroRelease: Ubuntu 20.04 > Package: shim-signed 1.40.3+15+1533136590.3beb971-0ubuntu1 > ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 > Uname: Linux 5.4.0-26-generic x86_64 > NonfreeKernelModules: nvidia_modeset nvidia > .proc.sys.kernel.moksbstate_disabled: Error: [Errno 2] No such file or > directory: '/proc/sys/kernel/moksbstate_disabled' > ApportVersion: 2.20.11-0ubuntu27 > AptOrdering: >shim:amd64: Install >shim-signed:amd64: Install >NULL: ConfigurePending > Architecture: amd64 > BootEFIContents: >BOOTX64.CSV >grub.cfg >grubx64.efi >mmx64.efi >shimx64.efi > CasperMD5CheckResult: skip > Date: Sat Jun 20 09:09:55 2020 > EFITables: >Jun 20 09:47:02 samuel-All-Series kernel: efi: EFI v2.31 by American > Megatrends > Jun 20 09:47:02 samuel-All-Series kernel: efi: ESRT=0xbef4c818 ACPI > 2.0=0xbdc9a000 ACPI=0xbdc9a000 SMBIOS=0xf04d0 MPS=0xfd5e0 >Jun 20 09:47:02 samuel-All-Series kernel: secureboot: Secure boot > enabled >Jun 20 09:47:02 samuel-All-Series kernel: esrt: Reserving ESRT space > from 0xbef4c818 to 0xbef4c850. >Jun 20 09:47:02 samuel-All-Series kernel: secureboot: Secure boot > enabled > ErrorMessage: installed shim-signed package post-installation script > subprocess returned error exit status 1 > InstallationDate: Installed on 2020-06-20 (0 days ago) > InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 > (20200423) > Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, > 3.8.2-0ubuntu2 > PythonDetails: N/A > RelatedPackageVersions: >dpkg 1.19.7ubuntu3 >apt 2.0.2 > SecureBoot: 6 0 0 0 1 > SourcePackage: shim-signed > Title: package shim-signed 1.40.3+15+1533136590.3beb971-0ubuntu1 failed > to install/upgrade: installed shim-signed package post-installation script > subprocess returned error exit status 1 > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1884398/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1884398 Title: pulseaudio To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1884398/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884398] [NEW] pulseaudio
Public bug reported: I was trying to fix my crakling, static-filled audio by running some pulseaudio commands in the console. The sound settings gui was open, and I think this error appeared when I tried to open a dropdown ProblemType: Package DistroRelease: Ubuntu 20.04 Package: shim-signed 1.40.3+15+1533136590.3beb971-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.sys.kernel.moksbstate_disabled: Error: [Errno 2] No such file or directory: '/proc/sys/kernel/moksbstate_disabled' ApportVersion: 2.20.11-0ubuntu27 AptOrdering: shim:amd64: Install shim-signed:amd64: Install NULL: ConfigurePending Architecture: amd64 BootEFIContents: BOOTX64.CSV grub.cfg grubx64.efi mmx64.efi shimx64.efi CasperMD5CheckResult: skip Date: Sat Jun 20 09:09:55 2020 EFITables: Jun 20 09:47:02 samuel-All-Series kernel: efi: EFI v2.31 by American Megatrends Jun 20 09:47:02 samuel-All-Series kernel: efi: ESRT=0xbef4c818 ACPI 2.0=0xbdc9a000 ACPI=0xbdc9a000 SMBIOS=0xf04d0 MPS=0xfd5e0 Jun 20 09:47:02 samuel-All-Series kernel: secureboot: Secure boot enabled Jun 20 09:47:02 samuel-All-Series kernel: esrt: Reserving ESRT space from 0xbef4c818 to 0xbef4c850. Jun 20 09:47:02 samuel-All-Series kernel: secureboot: Secure boot enabled ErrorMessage: installed shim-signed package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-06-20 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2 SecureBoot: 6 0 0 0 1 SourcePackage: shim-signed Title: package shim-signed 1.40.3+15+1533136590.3beb971-0ubuntu1 failed to install/upgrade: installed shim-signed package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: shim-signed (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1884398 Title: pulseaudio To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1884398/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882966] Re: Recent updates to some packages make it impossible to build an Orca Master in Ubuntu-MATE 20.04
I guess this is due to the following change in at-spi2-atk: * Meson: don't hard-code shared_library (!19). which made meson emit a lot of new libraries in Requires.private of atk- bridge-2.0.pc, and thus the -dev package now has to add them in Depends. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882966 Title: Recent updates to some packages make it impossible to build an Orca Master in Ubuntu-MATE 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi2-atk/+bug/1882966/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1638842] Re: network-manager does not manage ethernet and bluetooth interfaces when Ubuntu 16.10 is installed using chroot/netboot method
*** This bug is a duplicate of bug 1676547 *** https://bugs.launchpad.net/bugs/1676547 New Install from netboot method ubuntu 20.04 focal same error, I did everything, but nothing worked -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1638842 Title: network-manager does not manage ethernet and bluetooth interfaces when Ubuntu 16.10 is installed using chroot/netboot method To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1638842/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872527] Re: Clipboard doesn't work 100% of the time in Ubuntu 20.04 (in KVM guests)
I have experienced the same inconsistencies as reported by OP between Ubuntu 20.04 guest and hosts. The guest is connected through SPICE. On top of that, the clipboard has been working unreliably within the host system (i3). For example, I often have to copy multiple times the same text to have it enter the system clipboard. Moreover, calls to clipboard with CTRL+V can take a few seconds. When the guest is powered off, the issue does not resurface. I have tried to reproduce the issue with Debian 10 and other guests, with no “luck”. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872527 Title: Clipboard doesn't work 100% of the time in Ubuntu 20.04 (in KVM guests) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1872527/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879068] [NEW] Ubuntu 18 hangs and seeing a report like Radeon ring 4 stalled for 100000+ seconds
Public bug reported: System Config : Dell precision M4800, 16GB RAM, i7 processor, AMD RAdeon GPU, Ubuntu 18.0.4 solomon@solomon:~$ lsmod Module Size Used by pci_stub 16384 1 vboxpci24576 0 vboxnetadp 28672 0 vboxnetflt 28672 0 vboxdrv 471040 3 vboxpci,vboxnetadp,vboxnetflt ccm20480 6 amdgpu 4112384 0 amd_iommu_v2 20480 1 amdgpu gpu_sched 32768 1 amdgpu intel_rapl_msr 20480 0 intel_rapl_common 24576 1 intel_rapl_msr x86_pkg_temp_thermal20480 0 intel_powerclamp 20480 0 coretemp 20480 0 kvm_intel 245760 0 kvm 655360 1 kvm_intel irqbypass 16384 1 kvm mei_hdcp 24576 0 crct10dif_pclmul 16384 1 crc32_pclmul 16384 0 dell_laptop20480 0 ghash_clmulni_intel16384 0 uvcvideo 94208 0 dell_smm_hwmon 20480 0 snd_soc_rt5640143360 0 snd_hda_codec_realtek 118784 1 v4l2_common16384 1 uvcvideo snd_hda_codec_generic81920 1 snd_hda_codec_realtek videobuf2_vmalloc 20480 1 uvcvideo ledtrig_audio 16384 3 snd_hda_codec_generic,snd_hda_codec_realtek,dell_laptop snd_soc_rl6231 20480 1 snd_soc_rt5640 videobuf2_memops 20480 1 videobuf2_vmalloc snd_hda_codec_hdmi 57344 1 aesni_intel 372736 4 radeon 1454080 32 iwldvm233472 0 snd_hda_intel 53248 8 videobuf2_v4l2 24576 1 uvcvideo aes_x86_64 20480 1 aesni_intel snd_intel_nhlt 20480 1 snd_hda_intel videobuf2_common 49152 2 videobuf2_v4l2,uvcvideo snd_soc_core 237568 1 snd_soc_rt5640 crypto_simd16384 1 aesni_intel mac80211 847872 1 iwldvm snd_hda_codec 131072 4 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec_realtek videodev 208896 4 v4l2_common,videobuf2_v4l2,uvcvideo,videobuf2_common snd_compress 24576 1 snd_soc_core cryptd 24576 2 crypto_simd,ghash_clmulni_intel ac97_bus 16384 1 snd_soc_core mc 53248 4 videodev,videobuf2_v4l2,uvcvideo,videobuf2_common glue_helper16384 1 aesni_intel snd_hda_core 90112 5 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek ttm 102400 2 amdgpu,radeon libarc416384 1 mac80211 snd_pcm_dmaengine 16384 1 snd_soc_core snd_hwdep 20480 1 snd_hda_codec drm_kms_helper180224 2 amdgpu,radeon intel_cstate 20480 0 snd_pcm 102400 7 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_soc_rt5640,snd_soc_core,snd_hda_core,snd_pcm_dmaengine drm 491520 21 gpu_sched,drm_kms_helper,amdgpu,radeon,ttm dell_wmi 20480 0 intel_rapl_perf20480 0 snd_seq_midi 20480 0 dell_smbios28672 2 dell_wmi,dell_laptop i2c_algo_bit 16384 2 amdgpu,radeon snd_seq_midi_event 16384 1 snd_seq_midi input_leds 16384 0 joydev 28672 0 dcdbas 20480 1 dell_smbios fb_sys_fops16384 1 drm_kms_helper snd_rawmidi36864 1 snd_seq_midi serio_raw 20480 0 syscopyarea16384 1 drm_kms_helper sparse_keymap 16384 1 dell_wmi iwlwifi 348160 1 iwldvm snd_seq69632 2 snd_seq_midi,snd_seq_midi_event sysfillrect16384 1 drm_kms_helper wmi_bmof 16384 0 dell_wmi_descriptor20480 2 dell_wmi,dell_smbios sysimgblt 16384 1 drm_kms_helper snd_seq_device 16384 3 snd_seq,snd_seq_midi,snd_rawmidi snd_timer 36864 2 snd_seq,snd_pcm snd86016 29 snd_hda_codec_generic,snd_seq,snd_seq_device,snd_hda_codec_hdmi,snd_hwdep,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek,snd_timer,snd_compress,snd_soc_core,snd_pcm,snd_rawmidi cfg80211 704512 3 iwldvm,iwlwifi,mac80211 mei_me 40960 1 soundcore 16384 1 snd mei 102400 3 mei_hdcp,mei_me lpc_ich24576 0 ie31200_edac 16384 0 dell_rbtn 20480 1 dell_smo8800 20480 0 mac_hid16384 0 sch_fq_codel 20480 6 cuse 16384 3 parport_pc 40960 0 ppdev 24576 0 lp 20480 0 parport53248 3 parport_pc,lp,ppdev ip_tables 32768 0 x_tables 40960 1 ip_tables autofs445056 2 sdhci_pci 45056 0 ahci 40960 1 psmouse 151552 0 cqhci 28672 1 sdhci_pci e1000e253952 0 sdhci 57344 1 sdhci_pci libahci
[Bug 1872159] Re: booting with splash hangs when external monitors are connected (pure intel 8th gen laptop)
It seems to be the same problem here with ThinkPad X1 Carbon (2017 version with integrated Intel HD Graphics 620). Booting with external monitor attached to the HDMI port systematically makes the boot hangs atfer grub boot menu. To get out of this, I have to press the power button for a long time, and then I can boot again with the external cable unplugged. Once the graphical password prompt is shown, I can plug the external monitor again without ayn further problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872159 Title: booting with splash hangs when external monitors are connected (pure intel 8th gen laptop) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1872159/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1755305] Re: .xsession-errors filled with entries
Hi, is there any updates for this? I see this issue in xubuntu 20.04 (and previously 19.10). It clogs up the .xsessions-errors file periodically until I run out of disk space. A temporary fix is to write a cron job to empty this file if it exceeds some threshold -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1755305 Title: .xsession-errors filled with entries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1755305/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1755305] Re: .xsession-errors filled with entries
Hi, is there any updates for this? I see this issue in xubuntu 20.04 (and previously 19.10). It clogs up the .xsessions-errors file periodically until I run out of disk space. A temporary fix is to write a cron job to empty this file if it exceeds some threshold -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1755305 Title: .xsession-errors filled with entries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1755305/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873746] Re: kmail in Kubuntu 20.04 beta cannot connect to dovecot IMAP server
The solution (for me) was to modify /etc/ssl/openssl.cnf after the line: oid_section = new_oids by adding: openssl_conf = default_conf [default_conf] ssl_conf = ssl_sect [ssl_sect] system_default = system_default_sect [system_default_sect] MinProtocol = TLSv1.2 CipherString = DEFAULT@SECLEVEL=1 This is obviously not a Kubuntu or KDE bug so I'll close this now. ** Changed in: kdepim (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873746 Title: kmail in Kubuntu 20.04 beta cannot connect to dovecot IMAP server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdepim/+bug/1873746/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873746] Re: kmail in Kubuntu 20.04 beta cannot connect to dovecot IMAP server
Hi there, I have a strong suspicion that this is SSL related. I've found that this does not work: openssl s_client -connect example.com:993 [...] 139765775537472:error:141A318A:SSL routines:tls_process_ske_dhe:dh key too small:../ssl/statem/statem_clnt.c:2149: [...] but this does (found here: https://imlc.me/dh-key-too-small ): openssl s_client -connect example.com:993 --cipher 'DEFAULT:!DH' Now the received wisdom is that this is because of OpenSSL configuration and you can fix it by adding this to /etc/ssl/openssl.cnf: [system_default_sect] MinProtocol = TLSv1.2 CipherString = DEFAULT@SECLEVEL=2 However, that does not seem to work, either for the OpenSSL command line or for Akonadi. All the best, Chris -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873746 Title: kmail in Kubuntu 20.04 beta cannot connect to dovecot IMAP server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdepim/+bug/1873746/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873746] [NEW] kmail in Kubuntu 20.04 beta cannot connect to dovecot IMAP server
Public bug reported: Hi there, I've just upgraded to Kubuntu 20.04 beta and run straight into KDE bug https://bugs.kde.org/show_bug.cgi?id=419782 where kmail cannot connect to a dovecot IMAP server. This was working prior to the upgrade and the symptoms I see match what's reported in the bug. Apr 20 00:24:35 [redacted] dovecot: imap-login: Disconnected (no auth attempts in 1 secs): user=<>, rip=[redacted], lip=[redacted], TLS handshaking: Disconnected, session= Any chance of getting their fix backported please? All the best, Chris Requested info: chris@quad:~$ lsb_release -rd Description:Ubuntu 20.04 LTS Release:20.04 chris@quad:~$ dpkg -l kmail Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name VersionArchitecture Description +++-==-==-- ii kmail 4:19.12.3-0ubuntu1 amd64full featured graphical email client ** Affects: kdepim (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kdepim in Ubuntu. https://bugs.launchpad.net/bugs/1873746 Title: kmail in Kubuntu 20.04 beta cannot connect to dovecot IMAP server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdepim/+bug/1873746/+subscriptions -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1872023] Re: libsdl2-ttf-dev and libsdl2-dev headers not at the same place, causing compilation error
Since last update, the problem has moved, now this error happens: In file included from /usr/include/SDL2/SDL.h:32: In file included from /usr/include/SDL2/SDL_main.h:25: In file included from /usr/include/SDL2/SDL_stdinc.h:31: In file included from /usr/include/SDL2/SDL_config.h:4: In file included from /usr/include/x86_64-linux-gnu/SDL2/_real_SDL_config.h:33: /usr/include/x86_64-linux-gnu/SDL2/SDL_platform.h:179:10: fatal error: 'begin_code.h' file not found #include "begin_code.h" A workaround is to add -I/usr/include/SDL2 into compiling flags, but not very clean. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872023 Title: libsdl2-ttf-dev and libsdl2-dev headers not at the same place, causing compilation error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsdl2-ttf/+bug/1872023/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872023] [NEW] libsdl2-ttf-dev and libsdl2-dev headers not at the same place, causing compilation error
Public bug reported: Since update to focal, libsdl2 and libsdl2-ttf headers have a different location, causing a compilation error when trying to include SDL2/SDL_ttf.h header : $ sudo apt install libsdl2-ttf-dev libsdl2-dev $ echo "#include " > main.c $ gcc main.c In file included from main.c:1: /usr/include/SDL2/SDL_ttf.h:34:10: fatal error: SDL.h: Aucun fichier ou dossier de ce type 34 | #include "SDL.h" | ^~~ compilation terminated. It seems that SDL_ttf.h header expects to be in the same place that SDL ones, which is not the case : $ dpkg -L libsdl2-ttf-dev /. /usr /usr/include /usr/include/SDL2 /usr/include/SDL2/SDL_ttf.h ... $ dpkg -L libsdl2-dev /. /usr /usr/bin /usr/bin/sdl2-config /usr/include /usr/include/x86_64-linux-gnu /usr/include/x86_64-linux-gnu/SDL2 /usr/include/x86_64-linux-gnu/SDL2/SDL.h ... ** Affects: libsdl2-ttf (Ubuntu) Importance: Undecided Status: New ** Summary changed: - libsdl2-ttf-dev headers and libsdl2-dev headers not at the same place, causing compilation error + libsdl2-ttf-dev and libsdl2-dev headers not at the same place, causing compilation error ** Description changed: - Since update focal, libsdl2 and libsdl2-ttf headers have a different + Since update to focal, libsdl2 and libsdl2-ttf headers have a different location, causing a compilation error when trying to include SDL2/SDL_ttf.h header : $ sudo apt install libsdl2-ttf-dev libsdl2-dev $ echo "#include " > main.c - $ gcc main.c + $ gcc main.c In file included from main.c:1: /usr/include/SDL2/SDL_ttf.h:34:10: fatal error: SDL.h: Aucun fichier ou dossier de ce type -34 | #include "SDL.h" - | ^~~ + 34 | #include "SDL.h" + | ^~~ compilation terminated. It seems that SDL_ttf.h header expects to be in the same place that SDL ones, which is not the case : $ dpkg -L libsdl2-ttf-dev /. /usr /usr/include /usr/include/SDL2 /usr/include/SDL2/SDL_ttf.h ... $ dpkg -L libsdl2-dev /. /usr /usr/bin /usr/bin/sdl2-config /usr/include /usr/include/x86_64-linux-gnu /usr/include/x86_64-linux-gnu/SDL2 /usr/include/x86_64-linux-gnu/SDL2/SDL.h ... ** Project changed: launchpad => libsdl ** Project changed: libsdl => libsdl2-ttf (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872023 Title: libsdl2-ttf-dev and libsdl2-dev headers not at the same place, causing compilation error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsdl2-ttf/+bug/1872023/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840725] Re: Microphone not working in Ubuntu 18.04.3 LTS on new hp-spectre-x360-convertible-15 laptop
Have the same issue on a lot of laptop in my company, we have a webteam that work with Ubuntu and i update all machines for the last version 19.10, after this update all laptops don't have a internal micro. Model: HP 830 G6 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840725 Title: Microphone not working in Ubuntu 18.04.3 LTS on new hp- spectre-x360-convertible-15 laptop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1840725/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840725] Re: Microphone not working in Ubuntu 18.04.3 LTS on new hp-spectre-x360-convertible-15 laptop
Have the same issue on a lot of laptop in my companie, we hame a webteam that work with Ubuntu and i update all machines for the last version 19.10, after this update all laptops don't have a internal micro. Model: HP 830 G6 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840725 Title: Microphone not working in Ubuntu 18.04.3 LTS on new hp- spectre-x360-convertible-15 laptop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1840725/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853082] Re: package mysql-server-8.0 8.0.18-0ubuntu0.19.10.1 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 127
** Changed in: mysql-8.0 (Ubuntu) Status: Expired => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853082 Title: package mysql-server-8.0 8.0.18-0ubuntu0.19.10.1 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 127 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1853082/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847937] Re: 'gpu has fallen off the bus' after return from suspend
Hi, Where was this fixed? If you are referring to the aforementioned kernel, I can confirm that the bug is still present. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847937 Title: 'gpu has fallen off the bus' after return from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1847937/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847937] Re: 'gpu has fallen off the bus' after return from suspend
I upgraded my kernel to 5.4.18 and the issue is still appearing for me. $ uname -a Linux pop-os 5.4.18-050418-generic #202002051737 SMP Wed Feb 5 22:42:14 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux $ nvidia-detector nvidia-driver-440 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847937 Title: 'gpu has fallen off the bus' after return from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1847937/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847937] Re: 'gpu has fallen off the bus' after return from suspend
If I might add to this issue; I also have an XPS15, GTX 1650 and Ubuntu and POP!Os both trigger the issue (kernel 5.3.0-7625-generic). I also have deep as mem_sleep and use s2idle. I have tried the following parameters without succcess: $ sudo kernelstub -a "rcutree.rcu_idle_gp_delay=1 acpi_osi=! acpi_osi='Linux'" $ sudo kernelstub -a "pcie_acpi=off" (In combination and alone) I have also tried forcing persistence with the driver which also did not work. Here is another thread in mint forums https://forums.linuxmint.com/viewtopic.php?p=1728952=d2f654dfa1082400eeea98c9fbf01918#p1728952 The added parameters seems to work for them, but I could not resolve the issue. Nvidia driver is also at the latest version. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847937 Title: 'gpu has fallen off the bus' after return from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1847937/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1862399] [NEW] Crash whilst attempting to partition Samsung EVO 960 M.2 drive
Public bug reported: Just trying to install 18.04 LTS alongside fresh Windows 10 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity 18.04.14.12 ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CasperVersion: 1.394 Date: Fri Feb 7 18:02:44 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubiquity-18.04.14.12 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1862399 Title: Crash whilst attempting to partition Samsung EVO 960 M.2 drive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1862399/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1862400] [NEW] Crash whilst attempting to partition Samsung EVO 960 M.2 drive
Public bug reported: Just trying to install 18.04 LTS alongside fresh Windows 10 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity 18.04.14.12 ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CasperVersion: 1.394 Date: Fri Feb 7 18:02:44 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubiquity-18.04.14.12 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1862400 Title: Crash whilst attempting to partition Samsung EVO 960 M.2 drive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1862400/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1859341] [NEW] Missing client_ed25519.so plugin
Public bug reported: Although `apt install mariadb-server` results in the auth_ed25519.so plugin being installed, `apt install mariadb-client` *doesn't* provide the equivalent client_ed25519.so, resulting in the ability to set a password with the -server package, that can't be accessed with just the -client package. The client_ed25519.so library can be found in libmariadbclient18 but this package is only depended on by the a development package (libmariadbclient-dev) and a test package (mariadb-test). Furthermore, due to the name of libmariadbclient18 it doesn't appear alongside mariadb-*. The minimum bug I am proposing is that the virtual package mariadb- client (or the versioned real package) should at least Suggest (if not Recommend) the libmariadbclient18 package. I might also suggest that the plugin libraries live in a separate -plugin package; although I appreciate there seem to be too many different mariadb packages already, so including the -client plugins in the -client package would make sense too. ** Affects: mariadb-10.1 (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/1859341 Title: Missing client_ed25519.so plugin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mariadb-10.1/+bug/1859341/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
