[Bug 2060737] Re: Xorg assert failure: malloc(): unaligned tcache chunk detected
** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060737 Title: Xorg assert failure: malloc(): unaligned tcache chunk detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/2060737/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966064] [NEW] libc does not handle multi-byte grouping chars
Public bug reported: So I first reported this as a bug to `coreutils`, which closed the issue as the underlying reason lies in libc (*). Still, for the reproduction case I will still use `printf` from coreutils, as that uses `printf()` from libc internally. As can be seen below, the width specifier for numeric parameters does some weird calculations when the specified locale is `nb_NO.utf8`. For instance, the number formatting rules for US and NO locales both result in the same number of characters (with ' ' instead of ','), but the Norwegian version lacks two spaces in the padded output: $ LC_NUMERIC=en_US.utf8 printf "%s%'7d%s\n" XXX 1234 XXX XXX 1,234XXX $ LC_NUMERIC=nb_NO.utf8 printf "%s%'7d%s\n" XXX 1234 XXX XXX1 234XXX According to Pádraig Brady "The particular issue is the grouping char used in the nb_NO.utf8 locale is multi-byte. Specifically: e2 80 af. So that character counts as 3 bytes, and the printf implementation is counting bytes, not characters, or display cells. Given the usual consideration is display width, it probably should be considering display cells, but that's an issue for libc, not coreutils." Filing this here in the hopes that it will be pushed upstream at some point. * see https://debbugs.gnu.org/cgi/bugreport.cgi?bug=50336 for details ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: libc6-dev 2.34-0ubuntu3.2 ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Mar 23 12:45:17 2022 InstallationDate: Installed on 2021-08-26 (208 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: glibc UpgradeStatus: Upgraded to impish on 2022-02-08 (42 days ago) ** Affects: glibc (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966064 Title: libc does not handle multi-byte grouping chars To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1966064/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960285] [NEW] package openmpi-bin 4.1.0-10ubuntu1 failed to install/upgrade: installed openmpi-bin package post-installation script subprocess returned error exit status 2
Public bug reported: Happened during an OS upgrade. ProblemType: Package DistroRelease: Ubuntu 21.10 Package: openmpi-bin 4.1.0-10ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-99.112-generic 5.4.162 Uname: Linux 5.4.0-99-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown Date: Mon Feb 7 19:48:13 2022 DuplicateSignature: package:openmpi-bin:4.1.0-10ubuntu1 Installing new version of config file /etc/openmpi/openmpi-mca-params.conf ... update-alternatives: error: /var/lib/dpkg/alternatives/mpi corrupt: slave link same as main link /usr/bin/mpicc dpkg: error processing package openmpi-bin (--configure): installed openmpi-bin package post-installation script subprocess returned error exit status 2 ErrorMessage: installed openmpi-bin package post-installation script subprocess returned error exit status 2 InstallationDate: Installed on 2020-04-30 (648 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) Python3Details: /usr/bin/python3.9, Python 3.9.7, python3-minimal, 3.9.4-1build1 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.18-9 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.20.9ubuntu2 apt 2.3.9 SourcePackage: openmpi Title: package openmpi-bin 4.1.0-10ubuntu1 failed to install/upgrade: installed openmpi-bin package post-installation script subprocess returned error exit status 2 UpgradeStatus: Upgraded to impish on 2022-02-08 (0 days ago) ** Affects: openmpi (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package impish need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960285 Title: package openmpi-bin 4.1.0-10ubuntu1 failed to install/upgrade: installed openmpi-bin package post-installation script subprocess returned error exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openmpi/+bug/1960285/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956193] [NEW] package libnvidia-compute-390 (not installed) failed to install/upgrade: 共有されている '/etc/OpenCL/vendors/nvidia.icd' を上書きしようとしています。これはパッケージ libnvidia-compute-390:i386 の他の実体と異なります
Public bug reported: An attempt to do a clean install of NVIDIA drivers resulted in errors. I was doing so as a program I was intending to use detected that the pre- installed drivers did not let me use CUDA. Running a somewhat newly installed Ubuntu 20.04 I expected it to load the drivers as normal but it just gave me errors, ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libnvidia-compute-390 (not installed) ProcVersionSignature: Ubuntu 5.11.0-43.47~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-43-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Jan 2 16:36:13 2022 ErrorMessage: 共有されている '/etc/OpenCL/vendors/nvidia.icd' を上書きしようとしています。これはパッケージ libnvidia-compute-390:i386 の他の実体と異なります InstallationDate: Installed on 2021-12-26 (7 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: nvidia-graphics-drivers-390 Title: package libnvidia-compute-390 (not installed) failed to install/upgrade: 共有されている '/etc/OpenCL/vendors/nvidia.icd' を上書きしようとしています。これはパッケージ libnvidia-compute-390:i386 の他の実体と異なります UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal ** Attachment added: "Picture of additional drivers" https://bugs.launchpad.net/bugs/1956193/+attachment/5550702/+files/Screenshot%20from%202022-01-02%2016-44-06.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956193 Title: package libnvidia-compute-390 (not installed) failed to install/upgrade: 共有されている '/etc/OpenCL/vendors/nvidia.icd' を上書きしようとしています。これはパッケージ libnvidia-compute-390:i386 の他の実体と異なります To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1956193/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1676912] Re: Kernel 4.9+ regression: Suspend - Freezing of tasks failed
If it helps anyone, I have suggested a workaround in this Ask Ubuntu answer: https://askubuntu.com/a/263510/77322 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1676912 Title: Kernel 4.9+ regression: Suspend - Freezing of tasks failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1676912/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1912371] Re: [MIR] flashrom + libftdi
Hi, I thought we had deactivated the github bugtracker because flashrom development does not happen at github. The github mirror of flashrom is there purely for people who are unwilling or unable (due to corporate restrictions etc.) to download the source code from our self-hosted git trees. I'll try to get the github tracker deactivated to avoid giving people wrong impressions. As Stefan wrote, you can reach the flashrom developers at flash...@flashrom.org and you will also get attention if you send email there. Regards, Carl-Daniel Am 19.05.21 um 09:33 schrieb Stefan Tauner: > On Wed, 19 May 2021 06:52:55 - > Alex Murray <1912...@bugs.launchpad.net> wrote: > >> These failures of the mocked tests have been reported upstream at >> https://github.com/flashrom/flashrom/issues/186 by others but no >> response > Hi there, > > I was the flashrom maintainer till a few years ago. While I was using > the github repo+tracker, there is currently ~nobody taking care of that. > A more promising way to reach the right people is to write an email to > flash...@flashrom.org -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912371 Title: [MIR] flashrom + libftdi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flashrom/+bug/1912371/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875015] Re: Ubuntu 20.04 and Displaylink is extremely slow
Seems some people here are using the DisplayLink driver offered by the company for USB3-based DL-devices. I ran into this bug using the udl driver, since I'm using a DL-device based on one of the older USB2 DisplayLink chipsets. Confirmed the problem in Mint 20.1 and Ubuntu 20.04.2. In Ubuntu, I also tried Wayland but couldn't get DL working there at all. Some people here have stated that it helped running one of the screens with VGA or HDMI. Didn't help me though. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875015 Title: Ubuntu 20.04 and Displaylink is extremely slow To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1875015/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928485] [NEW] package git-man 1:2.27.0-1ubuntu1.1 [modified: usr/share/man/man1/git-add.1.gz usr/share/man/man1/git-am.1.gz usr/share/man/man1/git-annotate.1.gz usr/share/man/man1/git-archive.1.
Public bug reported: Error occurred during distro upgrade from 20.10 to 21.04. ProblemType: Package DistroRelease: Ubuntu 21.04 Package: git-man 1:2.27.0-1ubuntu1.1 [modified: usr/share/man/man1/git-add.1.gz usr/share/man/man1/git-am.1.gz usr/share/man/man1/git-annotate.1.gz usr/share/man/man1/git-archive.1.gz usr/share/man/man1/git-bisect.1.gz usr/share/man/man1/git-blame.1.gz] ProcVersionSignature: Ubuntu 5.8.0-1024.27-raspi 5.8.18 Uname: Linux 5.8.0-1024-raspi aarch64 ApportVersion: 2.20.11-0ubuntu65 Architecture: arm64 CasperMD5CheckResult: unknown Date: Fri May 14 15:53:23 2021 Dependencies: DuplicateSignature: package:git-man:1:2.27.0-1ubuntu1.1 [modified: usr/share/man/man1/git-add.1.gz usr/share/man/man1/git-am.1.gz usr/share/man/man1/git-annotate.1.gz usr/share/man/man1/git-archive.1.gz usr/share/man/man1/git-bisect.1.gz usr/share/man/man1/git-blame.1.gz] Unpacking git-man (1:2.30.2-1ubuntu1) over (1:2.27.0-1ubuntu1.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-pKushz/079-git-man_1%3a2.30.2-1ubuntu1_all.deb (--unpack): unable to stat './usr/share/man/man1/git-apply.1.gz' (which was about to be installed): Structure needs cleaning ErrorMessage: unable to stat './usr/share/man/man1/git-apply.1.gz' (which was about to be installed): Structure needs cleaning ImageMediaBuild: 20201022 PackageArchitecture: all Python3Details: /usr/bin/python3.9, Python 3.9.4, python3-minimal, 3.9.4-1 PythonDetails: N/A RebootRequiredPkgs: libc6 libssl1.1 RelatedPackageVersions: dpkg 1.20.9ubuntu1 apt 2.2.3 SourcePackage: git Title: package git-man 1:2.27.0-1ubuntu1.1 [modified: usr/share/man/man1/git-add.1.gz usr/share/man/man1/git-am.1.gz usr/share/man/man1/git-annotate.1.gz usr/share/man/man1/git-archive.1.gz usr/share/man/man1/git-bisect.1.gz usr/share/man/man1/git-blame.1.gz] failed to install/upgrade: unable to stat './usr/share/man/man1/git-apply.1.gz' (which was about to be installed): Structure needs cleaning UpgradeStatus: Upgraded to hirsute on 2021-05-14 (0 days ago) ** Affects: git (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package arm64 arm64-image hirsute raspi-image uec-images -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928485 Title: package git-man 1:2.27.0-1ubuntu1.1 [modified: usr/share/man/man1/git- add.1.gz usr/share/man/man1/git-am.1.gz usr/share/man/man1/git- annotate.1.gz usr/share/man/man1/git-archive.1.gz usr/share/man/man1 /git-bisect.1.gz usr/share/man/man1/git-blame.1.gz] failed to install/upgrade: unable to stat './usr/share/man/man1/git-apply.1.gz' (which was about to be installed): Structure needs cleaning To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/git/+bug/1928485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928201] [NEW] [Envaya Mini, playback] Playback problem
Public bug reported: After using the bluetooth device (Denon Envaya Mini) for video calls (Teams, Google Meet), it gets stuck on "Headset Head Unit (HSP/HFP)" config. Switching the configuration back to A2DP does nothing, restarting the app (Spotify, Poddr) etc does nothing. This worked just fine in 20.04 LTS. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: carl 1720 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed May 12 12:39:50 2021 InstallationDate: Installed on 2020-04-24 (382 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all ProcEnviron: LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nb_NO.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: Envaya Mini Symptom_Type: Only some of outputs are working Title: [Envaya Mini, playback] Playback problem UpgradeStatus: Upgraded to hirsute on 2021-04-27 (15 days ago) dmi.bios.date: 03/15/2019 dmi.bios.release: 1.28 dmi.bios.vendor: HUAWEI dmi.bios.version: 1.28 dmi.board.name: MACH-WX9 dmi.board.vendor: HUAWEI dmi.board.version: M12 dmi.chassis.type: 10 dmi.chassis.vendor: HUAWEI dmi.chassis.version: M12 dmi.ec.firmware.release: 1.28 dmi.modalias: dmi:bvnHUAWEI:bvr1.28:bd03/15/2019:br1.28:efr1.28:svnHUAWEI:pnMACH-WX9:pvrM12:rvnHUAWEI:rnMACH-WX9:rvrM12:cvnHUAWEI:ct10:cvrM12: dmi.product.family: MateBook X dmi.product.name: MACH-WX9 dmi.product.sku: C189 dmi.product.version: M12 dmi.sys.vendor: HUAWEI ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928201 Title: [Envaya Mini, playback] Playback problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1928201/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926938] Re: Recent mainline packages are built with Hirsuite 21.04, not Focal 20.04 LTS
It would be a shame for 20.04 LTS users to no longer be able to make use of the Mainline kernel PPA -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926938 Title: Recent mainline packages are built with Hirsuite 21.04, not Focal 20.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926938/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923525] Re: gnome-control-center sound won't set hdmi 5.1
this line looks relevent 18:57:44.0656 Gvc:DEBUG gvc_mixer_control_lookup_device_from_stream - Could not find a device for stream 'Built-in Audio Digital Stereo (HDMI)' ** Attachment added: "gnome-control-center -v > .log" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1923525/+attachment/5487068/+files/gnome-control-center.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1923525 Title: gnome-control-center sound won't set hdmi 5.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1923525/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923525] [NEW] gnome-control-center sound won't set hdmi 5.1
Public bug reported: gnome-control-center sound Shows output device: hdmi-audio configure: stereo I change configure to 5.1 output device changes to "dummy" and the configure UI goes away. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-control-center 1:3.38.5-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu62 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Apr 12 18:47:39 2021 InstallationDate: Installed on 2021-04-12 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210412) ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1923525 Title: gnome-control-center sound won't set hdmi 5.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1923525/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922935] [NEW] SEGFAULT on upgrade to 0.102-0ubuntu1~20.04.1
*** This bug is a duplicate of bug 1922898 *** https://bugs.launchpad.net/bugs/1922898 Public bug reported: Today a bunch of our ubuntu 20.04 servers on AWS EC2 (both amd64 and arm) upgraded to netplan 0.102-0ubuntu1~20.04.1, which resulted in a segfault when netplan ran generate, and then took the whole network down with it, the servers had to be force rebooted. kernel: [1938106.074273] netplan[2874371]: segfault at 1 ip 7f72cb991675 sp 7ffe8be03158 error 4 in libc-2.31.so[7f72cb82b000+178000] kernel: [1938106.074282] Code: 00 00 0f 1f 00 31 c0 c5 f8 77 c3 66 2e 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 89 f9 48 89 fa c5 f9 ef c0 83 e1 3f 83 f9 20 77 2b fd 74 0f c5 fd d7 c1 85 c0 0f 85 eb 00 00 00 48 83 c7 20 83 e1 systemd[2874368]: /usr/lib/systemd/system-generators/netplan terminated by signal SEGV. /etc/netplan/ is the default from aws ubuntu 20.04 image. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: netplan.io 0.102-0ubuntu1~20.04.1 ProcVersionSignature: Ubuntu 5.4.0-1041.43-aws 5.4.94 Uname: Linux 5.4.0-1041-aws x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Apr 7 15:34:08 2021 Ec2AMI: ami-09dd2e08d601bff67 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-west-2a Ec2InstanceType: t3.micro Ec2Kernel: unavailable Ec2Ramdisk: unavailable ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: netplan.io UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: netplan.io (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ec2-images focal ** This bug has been marked a duplicate of bug 1922898 SEGFAULT on upgrade to 0.102-0ubuntu1~20.04.1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922935 Title: SEGFAULT on upgrade to 0.102-0ubuntu1~20.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1922935/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918303] Re: Randomly set credentials written in cleartext to world-readable file
Hello all, I tested the focal-proposed package on a new install of Ubuntu Server and was unable to replicate the issue. The random passwords did not appear written in the cloud-init-output.log file and the output file's permissions were restricted. Near as I can tell it appears to be fixed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918303 Title: Randomly set credentials written in cleartext to world-readable file To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1918303/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903765] Re: Subwoofer mapped incorrectly on Macbook 2.1
This problem persists on the same system with all the latest updates. I
did however notice that in the "hardware" part of the GUI there is no
longer a "2.1" option, so defaulting to analogue stereo output.
I tried connecting an external speaker ("headphone") and it sounded as
it should.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1903765
Title:
Subwoofer mapped incorrectly on Macbook 2.1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1903765/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870839] Re: ModuleNotFoundError: No module named 'shatag.cli'
I noticed that the package is now fixed in Debian https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956373 It runs for me after I downloaded and installed the updated deb-file from Debian http://deb.debian.org/debian/pool/main/s/shatag/shatag_0.5.0-4_all.deb Thank you Didier Raboud and Hans Joachim Desserud! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870839 Title: ModuleNotFoundError: No module named 'shatag.cli' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shatag/+bug/1870839/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1912371] Re: [MIR] flashrom
[Adding flashrom mailing list to CC. Context: The Ubuntu bug is about moving flashrom from universe to main. See https://bugs.launchpad.net/ubuntu/+source/flashrom/+bug/1912371/ for details.] If anyone is interested, I can dig up my test scripts which I used to test flashrom, but I do not have any autopkgtest experience. Someone(TM) would have to convert that to autopkgtest format, or we can simply ship selftest scripts to be called from autopkgtest. The amount of testing depends on how much test coverage you want. We can do self-tests with internally emulated hardware or externally emulated hardware or real hardware (the last variant is probably not desirable in a build system). Besides that, flashrom always performs a few self-tests (mostly internal data structure consistency) during startup. The tests have repeatedly caught bugs before a merge when people added new features, but forgot to update all relevant data structures. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912371 Title: [MIR] flashrom To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flashrom/+bug/1912371/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1912371] Re: [MIR] flashrom
flashrom does have built-in self tests and also supports external tests, but apparently that is not well-known. If your build VM supports flash chip host controller emulation and flash chip emulation, you can run flashrom with root privileges against the emulated hardware. If you want to run only unprivileged code, the man page flashrom.8 has you covered with multiple pages of explanations and option descriptions and even working examples: dummy programmer The dummy programmer operates on a buffer in memory only. It provides a safe and fast way to test various aspects of flashrom and is mainly used in development and while debugging. It is able to emulate some chips to a certain degree (basic identify/read/erase/write operations work). [...] That feature is enabled by default if flashrom is built with the classic Makefile. AFAIK the Meson build doesn't have feature parity yet, so that feature might be missing (no promises). Regards, Carl-Daniel Am 04.02.21 um 16:17 schrieb William Wilson: > ** Description changed: > > + [Summary] > + There are a few issues before we can MIR this package. The package does not > have a test suite that runs at build time, nor does it have a test suite that > runs as autopkgtest. > + > [Availability] > Currently in universe. > + > + [Duplication] > + There is no other package in main providing the same functionality. > > [Rationale] > fwupd depends on libflashrom1 for its flashrom plugin, something that's > required to update Coreboot firmware. > > [Security] > - All known issues have bee resolved. > + All known issues have been resolved. > > [Quality Assurance] > + Package builds and runs easily > > [Dependencies] > N/A > > [Standards Compliance] > + Complies with FHS, though the organization of files in the source package > could be organized better. > + > + [Common blockers] > + flashrom does NOT have a test suite that runs at build time. > + flashrom does NOT have a test suite that runs as autopkgtest. > > [Maintenance] > Actively maintained - https://github.com/flashrom/flashrom > Packaging - https://salsa.debian.org/myczko-guest/flashrom.git > > ** Description changed: > > [Summary] > There are a few issues before we can MIR this package. The package does not > have a test suite that runs at build time, nor does it have a test suite that > runs as autopkgtest. > > [Availability] > Currently in universe. > > [Duplication] > There is no other package in main providing the same functionality. > > [Rationale] > fwupd depends on libflashrom1 for its flashrom plugin, something that's > required to update Coreboot firmware. > > [Security] > - All known issues have been resolved. > + No CVE's, but due to the nature of the package security should review. > > [Quality Assurance] > Package builds and runs easily > > [Dependencies] > N/A > > [Standards Compliance] > Complies with FHS, though the organization of files in the source package > could be organized better. > > [Common blockers] > flashrom does NOT have a test suite that runs at build time. > flashrom does NOT have a test suite that runs as autopkgtest. > > [Maintenance] > Actively maintained - https://github.com/flashrom/flashrom > Packaging - https://salsa.debian.org/myczko-guest/flashrom.git > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912371 Title: [MIR] flashrom To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flashrom/+bug/1912371/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1910995] Re: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5: bcmwl kernel module failed to build
*** This bug is a duplicate of bug 1872908 *** https://bugs.launchpad.net/bugs/1872908 @Rakhmanov's solution worked. Thank you. Confirmed on iMac 9,1 (late 2009) Many thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1910995 Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5: bcmwl kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1910995/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912827] [NEW] package oscar 1.0.1-r1 failed to install/upgrade: installed oscar package post-installation script subprocess returned error exit status 1
Public bug reported: Description:Ubuntu 20.10 Release:20.10 oscar: Installed: 1.0.1-r1 Candidate: 1.1.1-1 Version table: 1.1.1-1 500 500 http://ca.archive.ubuntu.com/ubuntu groovy/universe amd64 Packages *** 1.0.1-r1 100 100 /var/lib/dpkg/status This machine is a fresh install (groovy gorilla, amd64) with "minimal" packages - so LibreOffice was not installed by default. I attempted to open an .xls file by clicking it in the file manager; responded to the resulting pop-up dialogue with "find an app to open this" and (from the list of three suggested apps) selecting LibreOffice Calc. The "Ubuntu Software" app popped up; I clicked "Install" - it sat at "0% completed" for a minute or two, then failed with the prompt to report this to Ubuntu as a bug and with "Unable to install 'LibreOffice Calc' as not supported. An attempt to "apt install libreoffice" as root from the command line also fails, with: # apt install libreoffice Waiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 80096 (packagekitd) Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: libbrotli1:i386 libbsd0:i386 libcairo2:i386 libexpat1:i386 libffi8ubuntu1:i386 libfontconfig1:i386 libfreetype6:i386 libgdk-pixbuf2.0-0:i386 libglib2.0-0:i386 libjbig0:i386 libjpeg-turbo8:i386 libjpeg8:i386 libpixman-1-0:i386 libpng16-16:i386 libtiff5:i386 libwebp6:i386 libx11-6:i386 libxau6:i386 libxcb-render0:i386 libxcb-shm0:i386 libxcb1:i386 libxdmcp6:i386 libxext6:i386 libxrender1:i386 Use 'apt autoremove' to remove them. The following additional packages will be installed: firebird3.0-common firebird3.0-common-doc firebird3.0-server-core firebird3.0-utils fonts-crosextra-caladea fonts-crosextra-carlito fonts-dejavu fonts-linuxlibertine fonts-noto-core fonts-noto-extra fonts-noto-ui-core fonts-sil-gentium fonts-sil-gentium-basic gstreamer1.0-gtk3 libabw-0.1-1 libbsh-java libcommons-logging-java libe-book-0.1-1 libepubgen-0.1-1 libfbclient2 libfreehand-0.1-1 libib-util libmspub-0.1-1 libpagemaker-0.0-0 libpq5 libreoffice-base libreoffice-base-drivers libreoffice-draw libreoffice-gnome libreoffice-gtk3 libreoffice-impress libreoffice-java-common libreoffice-math libreoffice-nlpsolver libreoffice-report-builder libreoffice-report-builder-bin libreoffice-script-provider-bsh libreoffice-script-provider-js libreoffice-script-provider-python libreoffice-sdbc-firebird libreoffice-sdbc-mysql libreoffice-sdbc-postgresql libreoffice-style-elementary libreoffice-style-yaru libreoffice-wiki-publisher libreoffice-writer libtommath1 libunoil-java Suggested packages: firebird3.0-server firebird3.0-doc libavalon-framework-java libcommons-logging-java-doc libexcalibur-logkit-java liblog4j1.2-java gpa hyphen-hyphenation-patterns libreoffice-grammarcheck libreoffice-help libreoffice-l10n libreoffice-librelogo myspell-dictionary mythes-thesaurus openclipart2-libreoffice | openclipart-libreoffice pstoedit unixodbc libofficebean-java libjtds-java libreoffice-sdbc-hsqldb libsqliteodbc | tdsodbc | odbc-mdbtools libreoffice-evolution libreofficekit-data postgresql mediawiki The following NEW packages will be installed: firebird3.0-common firebird3.0-common-doc firebird3.0-server-core firebird3.0-utils fonts-crosextra-caladea fonts-crosextra-carlito fonts-dejavu fonts-linuxlibertine fonts-noto-core fonts-noto-extra fonts-noto-ui-core fonts-sil-gentium fonts-sil-gentium-basic gstreamer1.0-gtk3 libabw-0.1-1 libbsh-java libcommons-logging-java libe-book-0.1-1 libepubgen-0.1-1 libfbclient2 libfreehand-0.1-1 libib-util libmspub-0.1-1 libpagemaker-0.0-0 libpq5 libreoffice libreoffice-base libreoffice-base-drivers libreoffice-draw libreoffice-gnome libreoffice-gtk3 libreoffice-impress libreoffice-java-common libreoffice-math libreoffice-nlpsolver libreoffice-report-builder libreoffice-report-builder-bin libreoffice-script-provider-bsh libreoffice-script-provider-js libreoffice-script-provider-python libreoffice-sdbc-firebird libreoffice-sdbc-mysql libreoffice-sdbc-postgresql libreoffice-style-elementary libreoffice-style-yaru libreoffice-wiki-publisher libreoffice-writer libtommath1 libunoil-java 0 upgraded, 49 newly installed, 0 to remove and 1 not upgraded. 1 not fully installed or removed. Need to get 122 MB of archives. After this operation, 519 MB of additional disk space will be used. Do you want to continue? [Y/n] y Get:1 http://ca.archive.ubuntu.com/ubuntu groovy-updates/universe amd64 libreoffice-base-drivers amd64 1:7.0.3-0ubuntu0.20.10.1 [534 kB] Get:2 http://ca.archive.ubuntu.com/ubuntu groovy-updates/universe amd64 libreoffice-base amd64 1:7.0.3-0ubuntu0.20.10.1 [1,600 kB] Get:3
[Bug 1905522] Re: Error in fresh install of Ubuntu 20.10 package grub-efi-amd64-signed 1.155.1+2.04-1ubuntu35.1 failed
I'm seeing something similar on an ASUS desktop PC (AMD socket FM2, DDR3) which already has a few dual-boot options installed. I'm trying to install groovy 20.10 using Ubiquity from the live CD/DVD/USB. The installer goes through most of its paces, until it tries to install GRUB. It then dies with a pop-up box: Error installing grub-efi-amd64-signed installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 1 Attempting to install the package manually from a live desktop terminal window also fails, with: $ sudo su - # chroot /target # apt install grub-efi-amd64 giving: Setting up grub-efi-amd64 (2.04-1ubuntu35.1) ... Installing grub to /boot/efi. Installing for x86_64-efi platform. grub-install: warning: Cannot read EFI Boot* variables. grub-install: warning: read_file: could not read from file: Input/output error. grub-install: warning: vars_get_variable: read_file(/sys/firmware/efi/vars/Boot000C-8be4df61-93ca-11d2-aa0d-00e098032b8c/raw_var) failed : Input/output error. grub-install: warning: efi_get_variable: ops->get_variable failed: Input/output error. grub-install: error: failed to register the EFI boot entry: Input/output error. The workaround seems to be, while the installer is stopped at the error message box but still open, launching a terminal window from the live desktop and mounting efivarfs manually. At that point, apt may be used to install the package, install grub, apt upgrade everything to the current release... whatever. sudo su - chroot /mount/target sh -c "mount -t efivarfs efivarfs /sys/firmware/efi/efivars; grub-install; update-grub; apt install --reinstall grub-efi-amd64-signed After that, I was able to reboot into Ubuntu 20.10 (groovy) from the internal SSD. Without that, I could try the installer any number of times and it would always fail the same way. bugs.debian.org/cgi-bin/bugreport.cgi?bug=933523 looks to be related bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1874315 might be as well? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905522 Title: Error in fresh install of Ubuntu 20.10 package grub-efi-amd64-signed 1.155.1+2.04-1ubuntu35.1 failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1905522/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908799] Re: could not do a dist upgrade from eoan
Fixed after removal: sudo apt-get remove postgresql-server-dev-11 sudo apt-get remove postgresql-server-dev-12 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908799 Title: could not do a dist upgrade from eoan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1908799/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908799] [NEW] could not do a dist upgrade from eoan
Public bug reported: Output of release upgrade: sudo do-release-upgrade [sudo] password for litlfred: Checking for a new Ubuntu release Your Ubuntu release is not supported anymore. For upgrade information, please visit: http://www.ubuntu.com/releaseendoflife Get:1 Upgrade tool signature [1,554 B] Get:2 Upgrade tool [1,340 kB] Fetched 1,342 kB in 0s (0 B/s) authenticate 'focal.tar.gz' against 'focal.tar.gz.gpg' extracting 'focal.tar.gz' Reading cache Checking package manager Reading package lists... Done Building dependency tree Reading state information... Done Ign http://repos.azulsystems.com/ubuntu stable InRelease Hit http://dl.google.com/linux/chrome/deb stable InRelease Hit http://repos.azulsystems.com/ubuntu stable Release Ign http://linux.dropbox.com/ubuntu disco InRelease Get:1 http://linux.dropbox.com/ubuntu disco Release [6,598 B] Hit https://downloads.plex.tv/repo/deb public InRelease Hit https://repos.azul.com/zulu/deb stable InRelease Fetched 6,598 B in 0s (0 B/s) Reading package lists... Done Building dependency tree Reading state information... Done Checking for installed snaps Calculating snap size requirements Updating repository information Third party sources disabled Some third party entries in your sources.list were disabled. You can re-enable them after the upgrade with the 'software-properties' tool or your package manager. To continue please press [ENTER] Get:1 http://security.ubuntu.com/ubuntu focal-security InRelease [109 kB] Hit http://archive.ubuntu.com/ubuntu focal InRelease Get:2 http://archive.ubuntu.com/ubuntu focal-updates InRelease [114 kB] Get:3 http://security.ubuntu.com/ubuntu focal-security/main amd64 DEP-11 Metadata [24.3 kB] Get:4 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 DEP-11 Metadata [263 kB] Get:5 http://archive.ubuntu.com/ubuntu focal-updates/main DEP-11 64x64 Icons [82.1 kB] Fetched 593 kB in 0s (0 B/s) Checking package manager Reading package lists... Done Building dependency tree Reading state information... Done Calculating the changes Calculating the changes Could not calculate the upgrade An unresolvable problem occurred while calculating the upgrade. This was likely caused by: * Unofficial software packages not provided by Ubuntu Please use the tool 'ppa-purge' from the ppa-purge package to remove software from a Launchpad PPA and try the upgrade again. If none of this applies, then please report this bug using the command 'ubuntu-bug ubuntu-release-upgrader-core' in a terminal. If you want to investigate this yourself the log files in '/var/log/dist-upgrade' will contain details about the upgrade. Specifically, look at 'main.log' and 'apt.log'. Restoring original system state Aborting Reading package lists... Done Building dependency tree Reading state information... Done = Tail of /var/log/dist-upgrade/apt.log is: Broken dnsutils:amd64 Depends on liblwres161:amd64 < 1:9.11.5.P4+dfsg-5.1ubuntu2.2 -> 1:9.11.16+dfsg-3~ubuntu1 @ii ugU > (= 1:9.11.5.P4+dfsg-5.1ubuntu2.2) Considering liblwres161:amd64 0 as a solution to dnsutils:amd64 10002 Added liblwres161:amd64 to the remove list Fixing dnsutils:amd64 via keep of libbind9-161:amd64 MarkKeep libbind9-161:amd64 < 1:9.11.5.P4+dfsg-5.1ubuntu2.2 -> 1:9.11.16+dfsg-3~ubuntu1 @ii ugU > FU=0 Fixing dnsutils:amd64 via keep of libisccfg163:amd64 MarkKeep libisccfg163:amd64 < 1:9.11.5.P4+dfsg-5.1ubuntu2.2 -> 1:9.11.16+dfsg-3~ubuntu1 @ii umU > FU=0 Fixing dnsutils:amd64 via keep of liblwres161:amd64 MarkKeep liblwres161:amd64 < 1:9.11.5.P4+dfsg-5.1ubuntu2.2 -> 1:9.11.16+dfsg-3~ubuntu1 @ii ugU > FU=0 Try to Re-Instate (2) liblwres161:amd64 MarkKeep liblwres161:amd64 < 1:9.11.5.P4+dfsg-5.1ubuntu2.2 -> 1:9.11.16+dfsg-3~ubuntu1 @ii ugU > FU=0 Try to Re-Instate (2) libbind9-161:amd64 MarkKeep libbind9-161:amd64 < 1:9.11.5.P4+dfsg-5.1ubuntu2.2 -> 1:9.11.16+dfsg-3~ubuntu1 @ii ugU Ib > FU=0 Try to Re-Instate (3) libisccfg163:amd64 MarkKeep libisccfg163:amd64 < 1:9.11.5.P4+dfsg-5.1ubuntu2.2 -> 1:9.11.16+dfsg-3~ubuntu1 @ii umU > FU=0 Investigating
[Bug 1903765] [NEW] Subwoofer mapped incorrectly on Macbook 2.1
Public bug reported: It seems the 2.0 speakers get mapped to Speaker and the subwoofer is mapped to HEADPHONES, not LFE. I confirmed this by raising the volume for "headphones" in alsamixer and getting the base to play along. However, there seems to be no workaround in Ubuntu just using the sound GUI. My guess is, if ALSA would do the mapping to LFE correctly, I could use the 2.1 hardware map in the Ubuntu sound settings and all would be well! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: diskdoc3271 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Tue Nov 10 21:33:29 2020 InstallationDate: Installed on 2020-10-08 (33 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful Symptom_Card: Inbyggt ljud - HDA Intel Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Only some of outputs are working Title: [HDA-Intel - HDA Intel, playback] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/27/07 dmi.bios.vendor: Apple Inc. dmi.bios.version: MB21.88Z.00A5.B07.0706270922 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Mac-F4208CAA dmi.board.vendor: Apple Inc. dmi.board.version: PVT dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F4208CAA dmi.modalias: dmi:bvnAppleInc.:bvrMB21.88Z.00A5.B07.0706270922:bd06/27/07:svnAppleInc.:pnMacBook2,1:pvr1.0:rvnAppleInc.:rnMac-F4208CAA:rvrPVT:cvnAppleInc.:ct10:cvrMac-F4208CAA: dmi.product.family: MacBook dmi.product.name: MacBook2,1 dmi.product.sku: System SKUNumber dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. ** 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/1903765 Title: Subwoofer mapped incorrectly on Macbook 2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1903765/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1631514] Re: snap doesnt work. error: cannot communicate with server
I am having this issue with Ubuntu 20.10; and had it on 20.04 - but on 20.04 i wasn't doing as much development work and avoided the problem by just using the PPA or Synaptic; now it is unavoidable because the packages i need that are more architecture independent are in Snap, and each time I try to activate the store, troubleshoot any of the solutions previously stated, there's not an available socket, it's unresponsive, or only half opens with the majority of the store structure there but no apps. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1631514 Title: snap doesnt work. error: cannot communicate with server To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1631514/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899971] [NEW] Problematic dependency on python3-apport causes all Python invocations to install apport hook
Public bug reported: This would be no big deal if python3-apport just sat there until it was used (which it would never be on my system, since I removed apport). However, whenever python3-apport is installed, it unconditionally sets itself as sys.excepthook in Python3. The decision to have xserver-xorg depend on python3-apport basically means that every user who runs an X server will get this exception hook in Python whether they want it or not. And having python3-apport as the Python exception hook is not exactly harmless; it can still cause issues. My relatively minor but annoying issue is that I see deprecation warnings every time I get an error traceback, because python3-apport uses some deprecated code. I can imagine worse issues should there be an error in python3-apport; it could cause massive headaches and confusion for users who have no idea what's causing it. I'm not sure there is any point to have this dependency in the xserver- xorg package; it doesn't seem like those scripts will ever be run unless apport is installed and detects a crash, and apport already depends on python3-apport. I made a nice equivs package to allow myself to uninstall it, and as far as I can tell X and its applications still run fine. This is for Fossa, package version 1:7.7+19ubuntu. ** Affects: xorg (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/1899971 Title: Problematic dependency on python3-apport causes all Python invocations to install apport hook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1899971/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898919] [NEW] package grub-efi-amd64-signed 1.155+2.04-1ubuntu35 failed to install/upgrade: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status
Public bug reported: Update to Ubuntu 20.04.1 This bug was found when re-installing ubuntu due to a failed update to 20.04.1 The Display drivers didn't work for Nvidia GE graphic card for Samsung 3440x1440 resolution carl@LenovoDesk-H530s:~$ lspci | grep -i nvid 01:00.0 VGA compatible controller: NVIDIA Corporation GK208 [GeForce GT 720] (rev a1) 01:00.1 Audio device: NVIDIA Corporation GK208 HDMI/DP Audio Controller (rev a1) Tried various settings with cvt and xrandr but unable to get 3440x1440 resolution Re-installed with 20.1 and problem persists with display persist and also has this bug on new install. carl@LenovoDesk-H530s:~$ lsb_release -rd Description:Ubuntu Groovy Gorilla (development branch) Release:20.10 carl@LenovoDesk-H530s:~$ sudo apt-cache policy grub-efi-amd64-signed grub-efi-amd64-signed: Installed: 1.155+2.04-1ubuntu35 Candidate: 1.155+2.04-1ubuntu35 Version table: *** 1.155+2.04-1ubuntu35 500 500 http://gb.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Package DistroRelease: Ubuntu 20.10 Package: grub-efi-amd64-signed 1.155+2.04-1ubuntu35 ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10 Uname: Linux 5.8.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu48 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Oct 7 18:43:21 2020 ErrorMessage: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-10-07 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20200930) Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.20.5ubuntu2 apt 2.1.10 SourcePackage: grub2-signed Title: package grub-efi-amd64-signed 1.155+2.04-1ubuntu35 failed to install/upgrade: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub2-signed (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898919 Title: package grub-efi-amd64-signed 1.155+2.04-1ubuntu35 failed to install/upgrade: installed grub-efi-amd64-signed package post- installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1898919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892163] Re: Major networking regression linux-image-5.4.0-42-generic
** Attachment added: "dmesg.5.4.0" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1892163/+attachment/5403212/+files/dmesg.out -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892163 Title: Major networking regression linux-image-5.4.0-42-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1892163/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892163] Re: Major networking regression linux-image-5.4.0-42-generic
** Attachment added: "lspci.5.4.0" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1892163/+attachment/5403213/+files/lspci.out -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892163 Title: Major networking regression linux-image-5.4.0-42-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1892163/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892163] Re: Major networking regression linux-image-5.4.0-42-generic
More info, I am using wifi for the network. 5G -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892163 Title: Major networking regression linux-image-5.4.0-42-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1892163/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892163] Re: Major networking regression linux-image-5.4.0-42-generic
It works super nice, in 5.3.0 in 5.4.0 it just keeps going and going for over 10 minutes before I give up. It literally takes seconds in 5.3.0, I can send that one. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892163 Title: Major networking regression linux-image-5.4.0-42-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1892163/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892163] Re: Major networking regression linux-image-5.4.0-42-generic
I'm having lots of troubles with apport-collect since the network is so bad in 5.4.0, I tried apport-bug --save linux.apport linux, but that just locks up for 10 minutes. Is there any way I can run this offline and then send it with 5.3.0? Or what info do you need that I can run by hand and post? dmesg? lspci? boot logs? all installed packages? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892163 Title: Major networking regression linux-image-5.4.0-42-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1892163/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892163] Re: Major networking regression linux-image-5.4.0-42-generic
Also, running sudo apport-collect will not work since it can't attach to my firefox not running as root. But I did manage to get an authorization twice into my cache. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892163 Title: Major networking regression linux-image-5.4.0-42-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1892163/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892163] [NEW] Major networking regression linux-image-5.4.0-42-generic
Public bug reported: When booting into linux-image-5.4.0-42-generic networking grinds to a halt. It is 1x times slower than usual. Selecting an older kernel like linux-image-5.3.0-62-generic makes networking normal again. Description:Ubuntu 18.04.4 LTS Release:18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46~18.04.1 ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-62-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.16 Architecture: amd64 Date: Wed Aug 19 11:11:51 2020 InstallationDate: Installed on 2019-11-19 (273 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: linux-signed-hwe-5.4 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.4 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Attachment added: "Screenshot showing the slow download speeds compared to normal upload speeds." https://bugs.launchpad.net/bugs/1892163/+attachment/5402743/+files/Screenshot%20from%202020-08-17%2014-45-06.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892163 Title: Major networking regression linux-image-5.4.0-42-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.4/+bug/1892163/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891769] [NEW] package linux-image-3.13.0-77-generic 3.13.0-77.121 failed to install/upgrade: subprocess installed post-installation script returned error exit status 17
Public bug reported: happened durin 1st bootup after upgrade to 14.04LTS ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-77-generic 3.13.0-77.121 ProcVersionSignature: Ubuntu 3.13.0-170.220-generic 3.13.11-ckt39 Uname: Linux 3.13.0-170-generic i686 ApportVersion: 2.14.1-0ubuntu3.29 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sjf_inspiron 3091 F pulseaudio /dev/snd/seq:timidity 1741 F timidity Date: Sat Aug 15 15:27:57 2020 DuplicateSignature: package:linux-image-3.13.0-77-generic:3.13.0-77.121:subprocess installed post-installation script returned error exit status 17 ErrorMessage: subprocess installed post-installation script returned error exit status 17 HibernationDevice: RESUME=UUID=b1cff9b7-ebd8-4d65-bc43-06a8f955d36d InstallationDate: Installed on 2014-05-06 (2293 days ago) InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release i386 (20130820.1) MachineType: Dell Inc. Latitude D530 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-170-generic root=UUID=350e4fa5-87c3-4800-8ad3-e2e6452e0a75 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-9ubuntu1.17 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Title: package linux-image-3.13.0-77-generic 3.13.0-77.121 failed to install/upgrade: subprocess installed post-installation script returned error exit status 17 UpgradeStatus: Upgraded to trusty on 2020-08-15 (0 days ago) dmi.bios.date: 04/03/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd04/03/2008:svnDellInc.:pnLatitudeD530:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude D530 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package dist-upgrade i386 need-duplicate-check trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891769 Title: package linux-image-3.13.0-77-generic 3.13.0-77.121 failed to install/upgrade: subprocess installed post-installation script returned error exit status 17 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1891769/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866194] Re: External audio device shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker, or none at all.
The pulseaudio installed on my Ubuntu 20.04.1 systems is the following: pulseaudio - 1:13.99.1-1ubuntu3.5 deleting ~/.config/pulse and reboot fixed the problem of sound being directed to builtin speakers instead of the headphones although headphones were selected as the output device. Verified this on a Dell XPS labtop and an AMD desktop. Until 1:13.99.1-1ubuntu6 is released, I recommend deleting the config file and rebooting. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866194 Title: External audio device shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker, or none at all. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1866194/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881498] Re: Three monitor setup breaks if one+ screen rotated into portrait mode since Ubuntu 20.04
** Attachment added: "The screens, how I order them before I click apply." https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1881498/+attachment/5379186/+files/Screenshot%20from%202020-05-31%2017-22-04.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881498 Title: Three monitor setup breaks if one+ screen rotated into portrait mode since Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1881498/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881498] [NEW] Three monitor setup breaks if one+ screen rotated into portrait mode since Ubuntu 20.04
Public bug reported: Since I upgraded from Ubuntu 19.10 to 20.04 my multi monitor setup is broken. I put the screens into the shape of an H. The center screen is in landscape and to each side one screen in portrait/pivot orientation. I expected to rotate the virtual screens of the outer monitors into portrait mode as it was possible before. Instead the smallest (middle) screen gets scaled extremely in, the virtual screens overlap and just everything about the monitor setup breaks. The resolutions are from left to right 1440p, 1080p, 2160p. I could configure the outer screens to portrait mode over Nvidia X Server, but it doesn't survive a reboot. Also it breaks if I touch the screens over the gnome-control-center. == > apt-cache policy gnome-control-center gnome-control-center: Installed: 1:3.36.2-0ubuntu1 Candidate: 1:3.36.2-0ubuntu1 Version table: *** 1:3.36.2-0ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:3.36.1-1ubuntu5 500 500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 31 17:29:17 2020 DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-55-generic, x86_64: installed nvidia, 435.21, 5.4.0-33-generic, x86_64: installed virtualbox, 6.1.6, 5.3.0-55-generic, x86_64: installed virtualbox, 6.1.6, 5.4.0-33-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GM204 [GeForce GTX 970] [10de:13c2] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. GM204 [GeForce GTX 970] [19da:2370] InstallationDate: Installed on 2019-11-26 (186 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-33-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-05-29 (2 days ago) dmi.bios.date: 03/15/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3802 dmi.board.asset.tag: Default string dmi.board.name: MAXIMUS VIII RANGER 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.:bvr3802:bd03/15/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIRANGER: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 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu ** Attachment added: "After putting orienting the screens how I want them to be and click apply it gets scrambled like that" https://bugs.launchpad.net/bugs/1881498/+attachment/5379099/+files/Screenshot%20from%202020-05-31%2017-21-31.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881498 Title: Three monitor setup breaks if one+ screen rotated into portrait mode since Ubuntu 20.04 To manage notifications about this bug go to:
[Bug 1719143] Re: Unable to calibrate monitors through Gnome Control Center->Color in artful
This happened to me just now on a fresh installation of 20.04. Exactly as reported - first attempt at calibration with a Spyder 3 fails, on the second attempt gnome-control-center crashes hard. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1719143 Title: Unable to calibrate monitors through Gnome Control Center->Color in artful To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1719143/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878995] [NEW] Missing dependency on python-pyqt5.qtsvg
Public bug reported: Most of the toolbar icons in TortoiseHG do not render if python- pyqt5.qtsvg is not installed. ** Affects: tortoisehg (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/1878995 Title: Missing dependency on python-pyqt5.qtsvg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tortoisehg/+bug/1878995/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877236] Re: Ubunutu budgie 20.04 - I cannot switch the “connectivity checking” to “on”; the button/slider seems permanently “off” - is this being fixed? Many thanks
running gnome-control-center in terminal gives:- Gtk-Message: 13:33:44.500: Failed to load module "appmenu-gtk-module" output of $ nmcli d status DEVICE TYPE STATE CONNECTION wlp4s0 wifi connected BT-MRA2SS p2p-dev-wlp4s0 wifi-p2p disconnected -- enp0s31f6 ethernet unavailable -- lo loopback unmanaged -- -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877236 Title: Ubunutu budgie 20.04 - I cannot switch the “connectivity checking” to “on”; the button/slider seems permanently “off” - is this being fixed? Many thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1877236/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876023] Re: package mplayer-skin-blue (not installed) failed to install/upgrade: trying to overwrite '/usr/share/mplayer/skins/Blue/about.png', which is also in package mplayer-skins 3.2build1
After a full re-installation of 20.04 LTS, Videos now works as it is designed. Now if a commercial DVD is inserted, the player says the source file for the DVD is missing and tries to send the user to the software store for the file, which returns the error that the source is not available, and sends the user via hyperlink to a page that is no longer responding (I would guess the old Ubuntu Restricted Files for DVD playback page). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876023 Title: package mplayer-skin-blue (not installed) failed to install/upgrade: trying to overwrite '/usr/share/mplayer/skins/Blue/about.png', which is also in package mplayer-skins 3.2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mplayer-blue/+bug/1876023/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876733] Re: GruB boot on full Ubuntu 20.04 LTS install tries to use efi on mbr partition
Never mind what I wrote. I was seeing so many differences in the boot load that I went ahead and wiped the drive clean, set the zero fill option, reset the MBR and reformatted as ext4. Grab the up to date ISO, and re-installed 20.04 LTS. I let the install run as a normal full install, and the partitions that completed were as first noticed. sda1 vfat, sda2 extended, sda5 ext4. So that IS the default installer locations. Had never seen that arrangement on Ubuntu ever, so I assumed the arrangement were based on a previous Win10 partition. I was incorrect and apologize for the bug tracker. I guess the real answer here is to not run boot repair on a new install, as it will put the boot files in the wrong place and effect booting. In closing, as stated above "the reporter is confused". Can we know why this partition arrangement was needed? ** Changed in: ubiquity (Ubuntu) Status: New => Invalid ** Converted to question: https://answers.launchpad.net/ubuntu/+source/ubiquity/+question/690540 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876733 Title: GruB boot on full Ubuntu 20.04 LTS install tries to use efi on mbr partition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1876733/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877236] [NEW] Ubunutu budgie 20.04 - I cannot switch the “connectivity checking” to “on”; the button/slider seems permanently “off” - is this being fixed? Many thanks
Public bug reported: i cannot switch the “connectivity checking” to “on”; the button/slider seems permanently “off” - is this being fixed? assume package is gnome-control-center 1) Ubuntu 20.04 LTS (Ubuntu budgie) 2) gnome-control-center: Installed: 1:3.36.1-1ubuntu5 Candidate: 1:3.36.1-1ubuntu5 Version table: *** 1:3.36.1-1ubuntu5 500 500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3) I expected to be able to switch "connectivity checking" on 4) it doesnt; button/slider does not allow for "on"; other dials/buttons in settings do Screenshot attached ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.1-1ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Thu May 7 07:43:34 2020 InstallationDate: Installed on 2020-04-26 (10 days ago) InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages ** Attachment added: "connectivity checking.png" https://bugs.launchpad.net/bugs/1877236/+attachment/5367646/+files/connectivity%20checking.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877236 Title: Ubunutu budgie 20.04 - I cannot switch the “connectivity checking” to “on”; the button/slider seems permanently “off” - is this being fixed? Many thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1877236/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876733] Re: GruB boot on full Ubuntu 20.04 LTS install tries to use efi on mbr partition
Had some time to try to reinstall Grub and Boot files today with the assistance of Boot Repair as a guide, but following the Grub directions in Ubuntu on the terminal (not Boot Repair). When using Boot Repair Advanced Menu (After program launch and probe for setup) I noticed on my system that the program is interpreting my Bios (Insyde EFI) as a valid UEFI BIOS when it is not. The dmicode utility shows its name as "EFI" but the system as a standard (Old School) MBR and BIOS. In the BIOS Menu, there is no mention of Secure Boot, TPM, UEFI vs. Legacy, etc. Using Grub in MBR/BIOS mode, and turning off Secure Boot and EFI settings in Grub using Boot Repair as a guide (but following the directions in Ubuntu/Grub ONLY) I directed the Grub to install itself back on sda, and to include all relative locations (sda1-vfat-boot, sda5 -extended-ext4-ubuntu20.04LTS)where grub may be needed to boot. After reload, grub determined, based on BIOS/MBR settings that the sda1-vfat partition did not need a copy of Grub (even though the directions in Ubuntu said to be safe and select all partitions that may boot Grub) and placed all the boot data into sda5 where Ubuntu lives on the hard drive. I verified the sda1 partition in sudo file manager level. No files were loaded on the vfat (sda1) at all, but I am sure that Grub knows it is there now. So to be clear, I had to direct Grub to NOT USE UEFI/Secure Boot. It sees the name of the BIOS as Insyde EFI and thinks it is UEFI. Wrong Answer. Everything is OK now. I guess I could load Windows 10 but my hardware is not really ready for Win10 2004, so I am not really thrilled with the new OS upgrade from MS. (So we are clear, I do not like TPM, Secure Boot is eh, OK, but can be difficult to manage, and if chip- independent device, you can easily brick your device chip by playing around with it, even the OEM has to be careful, so God help us users. No tools to manage=don't mess with it! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876733 Title: GruB boot on full Ubuntu 20.04 LTS install tries to use efi on mbr partition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1876733/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876733] Re: GruB boot on full Ubuntu 20.04 LTS install tries to use efi on mbr partition
Dear Juhani, Just jumped on email, saw bug bot wanting a specific package in edit for bug. Tried to go to edit site and got a permission error saying I wasn't allowed or some such pish-posh. I suppose since it was during the installation on a full install, it had to be in Gparted or the Grub Bootloader. My system crashed this AM for some Dbus error (still fighting pulseaudio and alsa... hardware hates the audio) and the report got sent to HQ with my email and Acer5250. Just so you know, I did not read your email yet, just back on here, so let me go read that... hang on. Ok just assigned you to bug. Like I said, if you need the boot repair logs, just tell me what to scrub for privacy, and I'll send them where they need to go. Boot repair ran two logs, one on first run, then another after repairs of MBR. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876733 Title: GruB boot on full Ubuntu 20.04 LTS install tries to use efi on mbr partition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1876733/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876733] [NEW] GruB boot on full Ubuntu 20.04 LTS install tries to use efi on mbr partition
Public bug reported: Ubuntu 20.04 LTS on Acer 5250 laptop. Installed as a single operating system and told partition utility (Install Ubuntu) to claim entire hard drive on install. Install went well, but GruB was acting funny, loading the Grub Menu with a 30 Second Counter sometimes, then other times it would boot as normal. Decided to run Boot Repair and get report on drive boot. The program ran, but never reported what errors it found. It did find them, and prepared a set of reports, one upon install, the other after first run. The install utility partitioned the drive in three: 1 vfat(32), 2 extended, 5 ext4. Using the vfat(32) as the boot sector, it wrote all the bootfiles and GruB to 1. It tried to use esp and efi bootfiles, but this device is a old style mbr boot BIOS. So Grub went into fallback mode. Boot repair did repair the issue, by reinstalling GruB and kernel to partition 3, setting the boot loader mode to mbr, and removing the efi loader and all boot related files from partition 1. It looks like from the error logs in Boot Repair, that the Ubuntu Installer "best guess" from the previous setup (before install had Win10 and Ubuntu Mate Dual-Boot) was that Win10 needed that vfat(32) partition for installing Win10 AFTER Ubuntu and made a place for the win10 bootfiles, then added Ubuntu boot and kernel to the vfat(32) partition. However, during the install, what ever probe system was installed in kernel or grub incorrectly setup Ubuntu to use the efi bootfiles in a mbr environment. If you need the boot repair logs I can send them, but need to know what to scrub from them before sending or adding here. Not a programmer, just advanced user. ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876733 Title: GruB boot on full Ubuntu 20.04 LTS install tries to use efi on mbr partition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1876733/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876023] Re: package mplayer-skin-blue (not installed) failed to install/upgrade: trying to overwrite '/usr/share/mplayer/skins/Blue/about.png', which is also in package mplayer-skins 3.2build1
To resolve; 1) Left Videos installed as default player (still not playing commercial dvd, but no error shown. It picks up the data from the DVD, but will not play it) 2) Removed all MPlayer files (synaptic) 3) Installed VLC (runs good with libdvdcss2 and all code) *I forgot how big VLC is...space-wise... WOW) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876023 Title: package mplayer-skin-blue (not installed) failed to install/upgrade: trying to overwrite '/usr/share/mplayer/skins/Blue/about.png', which is also in package mplayer-skins 3.2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mplayer-blue/+bug/1876023/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876023] [NEW] package mplayer-skin-blue (not installed) failed to install/upgrade: trying to overwrite '/usr/share/mplayer/skins/Blue/about.png', which is also in package mplayer-skins 3.2build1
Public bug reported: MPlayer in new 20.04 LTS (2:1.3.0-8build5) fails to load GUI gives "skin errors" Using stock Ubuntu 20.04 LTS (3.36.1) in Gnome. Only thing added to system pulseaudio control gui and libdvdcss2 from source package set. Videos default player also will not run but gives no errors. MPlayer installs as a command line player, but the GUI and skins crash the program with skin errors. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: mplayer-skin-blue (not installed) ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Apr 29 23:18:33 2020 DuplicateSignature: package:mplayer-skin-blue:(not installed) Unpacking mplayer-skin-blue (1.11-2) ... dpkg: error processing archive /tmp/apt-dpkg-install-443vy4/3-mplayer-skin-blue_1.11-2_all.deb (--unpack): trying to overwrite '/usr/share/mplayer/skins/Blue/about.png', which is also in package mplayer-skins 3.2build1 ErrorMessage: trying to overwrite '/usr/share/mplayer/skins/Blue/about.png', which is also in package mplayer-skins 3.2build1 InstallationDate: Installed on 2020-04-26 (3 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 SourcePackage: mplayer-blue Title: package mplayer-skin-blue (not installed) failed to install/upgrade: trying to overwrite '/usr/share/mplayer/skins/Blue/about.png', which is also in package mplayer-skins 3.2build1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mplayer-blue (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal package-conflict -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876023 Title: package mplayer-skin-blue (not installed) failed to install/upgrade: trying to overwrite '/usr/share/mplayer/skins/Blue/about.png', which is also in package mplayer-skins 3.2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mplayer-blue/+bug/1876023/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871182] Re: [RTL810xE] No ethernet connection
@Paolo, I have this too: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873526 your -25 test kernel did work for me. [0.930604] r8169 :01:00.0: can't disable ASPM; OS doesn't have ASPM control [0.930615] ahci :00:17.0: version 3.0 [0.937784] libphy: r8169: probed [0.938205] r8169 :01:00.0 eth0: RTL8106e, a0:8c:fd:7e:9a:37, XID 449, IRQ 125 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871182 Title: [RTL810xE] No ethernet connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1871182/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873526] Re: regression: RTL810xE realtek.ko not loaded
*** This bug is a duplicate of bug 1871182 *** https://bugs.launchpad.net/bugs/1871182 5.4.0-21 - works juser@bb7b:~$ uname -a Linux bb7b 5.4.0-21-generic #25-Ubuntu SMP Sat Mar 28 13:10:28 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux juser@bb7b:~$ dmesg | grep r8169 [0.925034] r8169 :01:00.0: can't disable ASPM; OS doesn't have ASPM control [0.927657] libphy: r8169: probed [0.927838] r8169 :01:00.0 eth0: RTL8106e, a0:8c:fd:7e:9a:37, XID 449, IRQ 126 [0.944977] r8169 :01:00.0 enp1s0: renamed from eth0 [ 33.725813] Generic PHY r8169-100:00: attached PHY driver [Generic PHY] (mii_bus:phy_addr=r8169-100:00, irq=IGNORE) [ 33.984207] r8169 :01:00.0 enp1s0: Link is Down [ 35.504485] r8169 :01:00.0 enp1s0: Link is Up - 100Mbps/Full - flow control rx/tx -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873526 Title: regression: RTL810xE realtek.ko not loaded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873526/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873526] Re: regression: RTL810xE realtek.ko not loaded
*** This bug is a duplicate of bug 1873512 *** https://bugs.launchpad.net/bugs/1873512 juser@bb7b:~$ lsinitramfs /boot/initrd.img-5.4.0-24-generic | grep realtek usr/lib/modules/5.4.0-24-generic/kernel/drivers/net/dsa/realtek-smi.ko usr/lib/modules/5.4.0-24-generic/kernel/drivers/net/ethernet/realtek usr/lib/modules/5.4.0-24-generic/kernel/drivers/net/ethernet/realtek/8139cp.ko usr/lib/modules/5.4.0-24-generic/kernel/drivers/net/ethernet/realtek/8139too.ko usr/lib/modules/5.4.0-24-generic/kernel/drivers/net/ethernet/realtek/atp.ko usr/lib/modules/5.4.0-24-generic/kernel/drivers/net/ethernet/realtek/r8169.ko usr/lib/modules/5.4.0-24-generic/kernel/drivers/net/phy/realtek.ko usr/lib/modules/5.4.0-24-generic/kernel/drivers/usb/storage/ums-realtek.ko -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873526 Title: regression: RTL810xE realtek.ko not loaded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873526/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873526] [NEW] regression: RTL810xE realtek.ko not loaded
Public bug reported: juser@bb7b:~$ lsb_release -rd Description:Ubuntu 20.04 LTS Release:20.04 juser@bb7b:~$ apt-cache policy linux-generic linux-generic: Installed: 5.4.0.24.30 Candidate: 5.4.0.24.30 Version table: *** 5.4.0.24.30 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status wired network broke. worked in 5.4.0-21-generic update/upgrade/reboot lshw *-network UNCLAIMED description: Ethernet controller product: RTL810xE PCI Express Fast Ethernet controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:01:00.0 version: 07 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd cap_list configuration: latency=0 resources: ioport:4000(size=256) memory:b120-b1200fff memory:b100-b1003fff [0.926793] r8169 :01:00.0: can't disable ASPM; OS doesn't have ASPM control [0.930505] scsi host0: ahci [0.933726] libphy: r8169: probed [0.933729] r8169 :01:00.0: realtek.ko not loaded, maybe it needs to be added to initramfs? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-24-generic 5.4.0-24.28 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: juser 892 F pulseaudio CasperMD5CheckResult: skip Date: Fri Apr 17 15:42:00 2020 InstallationDate: Installed on 2020-04-04 (13 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 04f2:b52d Chicony Electronics Co., Ltd HP Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 5: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M |__ Port 5: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M MachineType: HP HP Notebook ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-24-generic root=UUID=3a88dbf4-b15b-4973-b898-5b78fe0613d7 ro quiet splash RelatedPackageVersions: linux-restricted-modules-5.4.0-24-generic N/A linux-backports-modules-5.4.0-24-generic N/A linux-firmware1.187 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/14/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.04 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 81EB dmi.board.vendor: HP dmi.board.version: 61.25 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.04:bd04/14/2016:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn81EB:rvr61.25:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.sku: X0S24UA#ABA dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** 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/1873526 Title: regression: RTL810xE realtek.ko not loaded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873526/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1190990] Re: Xfce4 mess up with icon positions
I am retired. I worked in IT all my life. Every attempt at evading the deliberate random rearrangement is nullified over the last 10 years.(read only flags, copying , desktop --reload etc) So there is no bug - it is deliberately programmed. This is disgraceful. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1190990 Title: Xfce4 mess up with icon positions To manage notifications about this bug go to: https://bugs.launchpad.net/xfdesktop/+bug/1190990/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824088] Re: unattended upgrade ran one day after schedule
Awesome work Magnus. Well done! Since the bug is related to APT, is Debian then considered the upstream of this source? Would it be appropriate to also file a bug in their bug tracker? If so, I can arrange that. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824088 Title: unattended upgrade ran one day after schedule To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1824088/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824088] Re: unattended upgrade ran one day after schedule
How about this idea? What if we add this line to the beginning of usr/lib/apt/apt.systemd.daily: export TZ="UTC0" (I got this idea from the GNU Coreutils manual. See https://www.gnu.org/software/coreutils/manual/html_node/Relative-items- in-date-strings.html) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824088 Title: unattended upgrade ran one day after schedule To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1824088/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824088] Re: unattended upgrade ran one day after schedule
If we look at lines 131 and 132 in /usr/lib/apt/apt.systemd.daily, we
will se the following:
interval="${interval%d}"
interval=$((interval*60*60*24))
I’m not 100% certain but I think that this time logic is what cause the
bug to occur, in accordance with what Magnus has pointed out in his
comments.
(It’s possible that lines 122-130 are also relevant.)
Any ideas on how to modify the code in order to avoid this bug?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824088
Title:
unattended upgrade ran one day after schedule
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1824088/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1794033] Re: i965: Failed to submit batchbuffer: Bad address
Also encountered this: $ uname -a Linux kaltop 5.3.0-40-generic #32-Ubuntu SMP Fri Jan 31 20:24:34 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 19.10 Release:19.10 Codename: eoan mar 06 12:44:09 kaltop /usr/lib/gdm3/gdm-x-session[2575]: i965: Failed to submit batchbuffer: Bad address mar 06 12:44:09 kaltop gnome-shell[2782]: X IO Error mar 06 12:44:09 kaltop pulseaudio[2557]: X connection to :0 broken (explicit kill or server shutdown). mar 06 12:44:09 kaltop WebKitWebProces[18049]: WebKitWebProcess: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. mar 06 12:44:09 kaltop gnome-shell[2782]: Gdk-Message: 12:44:09.213: /usr/lib/firefox/firefox: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1794033 Title: i965: Failed to submit batchbuffer: Bad address To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1794033/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1807047] Re: sync hd-media FLOPPY_SIZE with debian
** Patch added: "debian-installer_hd-media-floppysize.patch" https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1807047/+attachment/5292388/+files/debian-installer_hd-media-floppysize.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1807047 Title: sync hd-media FLOPPY_SIZE with debian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1807047/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1787402]
bump. me too. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1787402 Title: wrong working directory on autostart .desktop files To manage notifications about this bug go to: https://bugs.launchpad.net/xfce4-session/+bug/1787402/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1597466] Re: dpkg giving warning about '/etc/lsb-release' version number not starting with a digit when there is no apparent problem in the file
This has shown up again in 18.04. dpkg: warning: version '/etc/lsb-release' has bad syntax: version number does not start with digit $ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu 18.04.3 LTS" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1597466 Title: dpkg giving warning about '/etc/lsb-release' version number not starting with a digit when there is no apparent problem in the file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1597466/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838644] Re: Booting into desktop results in flickering
I suspended a couple of times and no ill effect Also I note someone mentions about backlight issues. Mine is fine Also did a restart again today and actually no flickering, not even at login Still on xrender in KDE settings -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838644 Title: Booting into desktop results in flickering To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1838644/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838644] Re: Booting into desktop results in flickering
So I just booted back to my 5 kernel. I switched KDE to xrender first The flickering is present at the login screen, but not in the running desktop, however, I do know from previous experiments with xrender as a solution it can still start flickering, perhaps that's after a suspend but I'd have to check. Here is more detail on my spec @Mike Wilson, interesting you quote my processor https://paste.ubuntu.com/p/gP5mDFgCHS/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838644 Title: Booting into desktop results in flickering To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1838644/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838644] Re: Booting into desktop results in flickering
I can confirm that I have experienced this and it is most definitely related to Kernel 5 > If it clears in upward versions I can't say I did let Kubuntu 18.04 upgrade to 19.04 and the issue appeared. Switching KDE settings to xrender seemed to help, but it didn't remove the problem totally. I re-installed 18.04 and have been running it since, however, 18.04 just had the Kernel upgrade to 5 > I let it run, just to see, and sure enough, there it was again. So i just booted from the older installed kernel and all is well. So it's certainly Kernel related My graphics are: https://paste.ubuntu.com/p/jggjBGmS9x/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838644 Title: Booting into desktop results in flickering To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1838644/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1837733] [NEW] gitg loses ancestors to commits after rebasing
Public bug reported: Ubuntu 18.04LTS uses an old version of gitg which has an annoying rendering bug which has been fixed in version 3.32. See this upstream bug. https://gitlab.gnome.org/GNOME/gitg/issues/234 It would be nice to see an update to 3.32 at least to remove this annoying bug. ** Affects: gitg (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/1837733 Title: gitg loses ancestors to commits after rebasing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gitg/+bug/1837733/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1807047] Re: sync hd-media FLOPPY_SIZE with debian
This does not fit: http://cdimage.ubuntu.com/ubuntu-server/daily/pending/ eoan-server-amd64.iso.zsync 2019-06-24 06:53754M just to be sure: wget.. unzip... like above cp: error writing 'mnt/eoan-server-amd64.iso': No space left on device Can we please bump FLOPPY_SIZE or should I file a bug against the iso for being too big? ;) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1807047 Title: sync hd-media FLOPPY_SIZE with debian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1807047/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1807047] Re: sync hd-media FLOPPY_SIZE with debian
I should have tested, the iso doesn't fit in the resulting free space. set -ex wget -N http://archive.ubuntu.com/ubuntu/dists/disco/main/installer-amd64/current/images/hd-media/boot.img.gz wget -N http://cdimage.ubuntu.com/releases/19.04/release/ubuntu-19.04-server-amd64.iso gunzip --keep --force boot.img.gz mkdir -p mnt sudo mount boot.img mnt df mnt ls -l ubuntu-19.04-server-amd64.iso sudo cp ubuntu-19.04-server-amd64.iso mnt/ ++ df mnt Filesystem 1K-blocks Used Available Use% Mounted on /dev/loop1800208 28612771596 4% /home/carl/temp/disco/mnt ++ ls -l ubuntu-19.04-server-amd64.iso -rw-rw-r-- 1 carl carl 790626304 May 10 01:44 ubuntu-19.04-server-amd64.iso ++ sudo cp ubuntu-19.04-server-amd64.iso mnt/ cp: error writing 'mnt/ubuntu-19.04-server-amd64.iso': No space left on device -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1807047 Title: sync hd-media FLOPPY_SIZE with debian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1807047/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824088] [NEW] unattended upgrade ran one day after schedule
Public bug reported: I have noticed a strange behaviour in unattended upgrades. The host in question is scheduled to run upgrades on Mondays every second week. However, this week it ran upgrades on Tuesday instead (2019-04-09). This is the first time I’ve noticed this behaviour. I checked the logs in /var/log/apt/history.log* and I saw that worked as intended up until this week. Upgrades ran as expected on 2019-03-11 and 2019-03-25, which where both Mondays. The schedule was set with the line 'APT::Periodic::Unattended-Upgrade "14";' in the file /etc/apt/apt.conf.d/20auto-upgrades. Could it be daylight savings time that has caused skewing of the schedule? The server is located in Sweden and on 2019-03-31 we switched from CET to CEST. If the time diff is calculated with hours instead of calendar days passed, perhaps the missing hour on 2019-03-31 caused the scheduler to believe that on Monday 2019-03-08, two weeks (336 hours) had not yet passed. ADDITIONAL INFO Description:Ubuntu 16.04.6 LTS Release:16.04 apt: Installed: 1.2.29ubuntu0.1 Candidate: 1.2.31 Version table: 1.2.31 500 500 http://se.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages *** 1.2.29ubuntu0.1 500 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status 1.2.10ubuntu1 500 500 http://se.archive.ubuntu.com/ubuntu xenial/main amd64 Packages unattended-upgrades: Installed: 0.90ubuntu0.10 Candidate: 0.90ubuntu0.10 Version table: *** 0.90ubuntu0.10 500 500 http://se.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://se.archive.ubuntu.com/ubuntu xenial-updates/main i386 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main i386 Packages 100 /var/lib/dpkg/status 0.90 500 500 http://se.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 500 http://se.archive.ubuntu.com/ubuntu xenial/main i386 Packages ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: apt 1.2.29ubuntu0.1 ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167 Uname: Linux 4.4.0-142-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Wed Apr 10 09:06:49 2019 InstallationDate: Installed on 2017-12-28 (467 days ago) InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apt (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial ** Attachment added: "Log data from apt" https://bugs.launchpad.net/bugs/1824088/+attachment/5254614/+files/history.txt ** Attachment removed: "Log data from apt" https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1824088/+attachment/5254614/+files/history.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824088 Title: unattended upgrade ran one day after schedule To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1824088/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824088] Re: unattended upgrade ran one day after schedule
** Attachment added: "Log data from apt" https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1824088/+attachment/5254618/+files/history.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824088 Title: unattended upgrade ran one day after schedule To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1824088/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 802942] Re: printing PDFs (and other complex documents) from GTK applications fails
See https://bugs.launchpad.net/ubuntu/+source/foomatic- db/+bug/1306849/comments/42 for a workaround for the broken Firefox -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/802942 Title: printing PDFs (and other complex documents) from GTK applications fails To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/802942/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1306849] Re: Printing error
Same issue with printing files from Firefox (and sometimes other applications) in Bionic with a Brother HL5250DN. The used driver does not matter (BR-Script3, PCL, PS). Related: https://bugzilla.redhat.com/show_bug.cgi?id=855009#c6 Solution: Use the BR-Script3 driver, then edit (as root) the PPD for your printer (for me it's /etc/cups/ppd/Brother_HL-5250DN_Brotherscript3.ppd ). The PPD starts with some comments, then the following content: [...] *% *% Copyright(C) 2005 Brother Industries, Ltd. *% "Brother HL-5250DN BR-Script3" *% *% General Information Keywords *FormatVersion: "4.3" *FileVersion: "1.03" *LanguageEncoding: ISOLatin1 *LanguageVersion: English *Manufacturer: "Brother" *PCFileName: "BR5250_2.PPD" *Product: "(Brother HL-5250DN series)" *PSVersion: "(3010.106) 5" *ShortNickName: "Brother HL-5250DN BR-Script3" *ModelName: "Brother HL-5250DN BR-Script3" *NickName: "Brother HL-5250DN BR-Script3" *1284DeviceID: "MFG:Brother;MDL:HL-5250DN series;CMD:PJL,PCL,PCLXL,POSTSCRIPT;" *% Basic Device Capabilities = *LanguageLevel: "3" [...] Edit the line with "LanguageLevel" and change the "3" to "2". It should now look like this: *LanguageLevel: "2" Restart cups with "systemctl restart cups". Enjoy. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1306849 Title: Printing error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/foomatic-db/+bug/1306849/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1040844] Re: Left Mouse Button Sometimes Gets Stuck in Unity (12.04)
If you have this issue and have a computer with a touch screen (like Dell XPS or HP clamshells), just touch the screen to fix it. Ref https://youtrack.jetbrains.com/issue/JBR-563#focus=streamItem-27-2843582.0-0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1040844 Title: Left Mouse Button Sometimes Gets Stuck in Unity (12.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1040844/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818363] Re: the duration (-t) option seems to be ignore
** Changed in: ffmpeg (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818363 Title: the duration (-t) option seems to be ignore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ffmpeg/+bug/1818363/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818363] Re: the duration (-t) option seems to be ignore
Isn't the point of this bug report that current FFmpeg quits after 30 seconds while older FFmpeg works for longer - completely independent of the "-t" option? Anyway, please run git bisect to find the change introducing the issue as I don't think there is another way to understand this issue. FFmpeg compilation by default produces static libraries and a binary that you do not have to install, it can be tested from the build directory, the issue should be reproducible with "./configure && make ffmpeg" if you use "-vcodec mpeg4 -qscale 5" as encoder. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818363 Title: the duration (-t) option seems to be ignore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ffmpeg/+bug/1818363/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 645404] Re: Support Private PPAs
please consider the CI case: headless process that runs periodically for months without user interaction. something like: deploy a private key (or similarly sensitive secret) file and a publicly readable script (apt-add-repository...) and it just runs, no browser, no user, no typing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/645404 Title: Support Private PPAs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/645404/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818363] Re: the duration (-t) option seems to be ignore
The console output of an earlier working version may be helpful. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818363 Title: the duration (-t) option seems to be ignore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ffmpeg/+bug/1818363/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818363] Re: the duration (-t) option seems to be ignore
Do you agree that the issue is (most likely) unrelated to the option -t? Please run git bisect to find the change introducing the issue, the alternative would be to provide a public rtsp stream (that may not be stable enough to reproduce). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818363 Title: the duration (-t) option seems to be ignore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ffmpeg/+bug/1818363/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818363] Re: the duration (-t) option seems to be ignore
How does the console output look without any "-t" option specified? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818363 Title: the duration (-t) option seems to be ignore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ffmpeg/+bug/1818363/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818363] Re: the duration (-t) option seems to be ignore
Instead of the input option "-t" (that used to be a global option) please use the output option "-t". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818363 Title: the duration (-t) option seems to be ignore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ffmpeg/+bug/1818363/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818363] Re: the duration (-t) option seems to be ignore
You are using an input option (it used to be a global option in the past) that apparently does not (or cannot) work for your input, please use the output option that is supposed to work as expected. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818363 Title: the duration (-t) option seems to be ignore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ffmpeg/+bug/1818363/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817620] Re: High cpu usage on alt-tab-ing
OK, removed. Just found it weird that both issues disappered by restarting `gnome-shell`, so assumed they were related by some root cause. Thank you. ** Description changed: Switching between apps was feeling extremely laggy and unsmooth after some days of keeping the laptop on and just alt-tab-ing between apps would keep the cpu consistently at 100% when hitting it more than 8-9 times per second and *not* letting go of Alt (meaning I stay at the same app). - - Also, just whizzing the mouse around on the screen (not moving anything) - would keep the cpu at 40-50%. Some investigation (1) led me to try out restarting the gnome-shell instance (killall followed by manually starting it in the terminal), upon which everything seemed zippy again. No lagginess. The restart was a supposed fix for a memory leak bug (2), but according to the comments a bug fix was supposed to have landed in 18.04 long ago. So either this has not been fixed or this bug is about something else - probably the latter, as the reported memory usage in htop was nowhere near the gigabytes of memory reported in the bug issue for 16722297. Another thing worth mentioning perhaps, based on comments in (3) found through (4), is that I have disabled all extensions. I used to use the Coverflow extension. Expected behaviour: There should be no percieved lag or stuttering in the interface when switching between applications. Actual behaviour: Switching between applications causes a noticable lag/stuttering when the computer has been running for an extended period of time (weeks, but where it has mostly been suspended, meaning actual usage is limited to 3-4 days). - 1. https://www.omgubuntu.co.uk/2018/03/gnome-shell-has-a-memory-leak-and-it-might-not-be-fixed-for-ubuntu-18-04-lts 2. https://bugs.launchpad.net/gnome-shell/+bug/1672297 3. https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1773959 4. https://askubuntu.com/a/1090987/165026 System info: Running Wayland. Description: Ubuntu 18.04.1 LTS Release: 18.04 gnome-shell: - Installert: 3.28.3-0ubuntu0.18.04.4 - Kandidat: 3.28.3-0ubuntu0.18.04.4 - Versjonstabell: - *** 3.28.3-0ubuntu0.18.04.4 500 - 500 http://no.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages - 100 /var/lib/dpkg/status - 3.28.1-0ubuntu2 500 - 500 http://no.archive.ubuntu.com/ubuntu bionic/main amd64 Packages + Installert: 3.28.3-0ubuntu0.18.04.4 + Kandidat: 3.28.3-0ubuntu0.18.04.4 + Versjonstabell: + *** 3.28.3-0ubuntu0.18.04.4 500 + 500 http://no.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages + 100 /var/lib/dpkg/status + 3.28.1-0ubuntu2 500 + 500 http://no.archive.ubuntu.com/ubuntu bionic/main amd64 Packages + + edit: removed info on high cpu usage when using mouse. supposedly + unrelated. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1817620 Title: High cpu usage on alt-tab-ing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1817620/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817620] Re: High cpu usage on alt-tab-ing
Thanks for the reply. I'll run Apport as soon as I can access the machine again. Regarding the actual issue, I don't think it is as cut and dry as this being just about rendering alone, as that would imply that the rendering performance was consistently bad. As I wrote, the performance seems fine on a fresh boot and also after restarting gnome-session (once the bug has appeared), which would not be the case if this was down to just rendering. Some kind of memory issue (leak, fragmentation, ...) seems to play a part in order to explain the time component. Also, there is no window preview (which I assume is a small boxed window preview when Alt-Tab-ing) when I have disabled the Coverflow plugin, yet the stuttering performance was very much present. When it comes to testing out the issue with 19.04, you'll have to bear with me, as this issue takes some time to materialize :-) I have not been able to reproduce it in a short time. Are there any debugging tools I can employ to gain some insight/stats/vitals if/when I encounter this issue? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1817620 Title: High cpu usage on alt-tab-ing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1817620/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1807047] Re: sync hd-media FLOPPY_SIZE with debian
some fit, some don't: FLOPPY_SIZE = 801792 ubuntu-18.10-server-amd64.iso 717M ubuntu-16.04.5-server-amd64.iso 870M ubuntu-18.04.2-server-amd64.iso 883M prerelease: http://cdimage.ubuntu.com/ubuntu-server/daily/pending/ disco-server-amd64.iso 752M -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1807047 Title: sync hd-media FLOPPY_SIZE with debian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1807047/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817620] [NEW] High cpu usage on alt-tab-ing
Public bug reported: Switching between apps was feeling extremely laggy and unsmooth after some days of keeping the laptop on and just alt-tab-ing between apps would keep the cpu consistently at 100% when hitting it more than 8-9 times per second and *not* letting go of Alt (meaning I stay at the same app). Also, just whizzing the mouse around on the screen (not moving anything) would keep the cpu at 40-50%. Some investigation (1) led me to try out restarting the gnome-shell instance (killall followed by manually starting it in the terminal), upon which everything seemed zippy again. No lagginess. The restart was a supposed fix for a memory leak bug (2), but according to the comments a bug fix was supposed to have landed in 18.04 long ago. So either this has not been fixed or this bug is about something else - probably the latter, as the reported memory usage in htop was nowhere near the gigabytes of memory reported in the bug issue for 16722297. Another thing worth mentioning perhaps, based on comments in (3) found through (4), is that I have disabled all extensions. I used to use the Coverflow extension. Expected behaviour: There should be no percieved lag or stuttering in the interface when switching between applications. Actual behaviour: Switching between applications causes a noticable lag/stuttering when the computer has been running for an extended period of time (weeks, but where it has mostly been suspended, meaning actual usage is limited to 3-4 days). 1. https://www.omgubuntu.co.uk/2018/03/gnome-shell-has-a-memory-leak-and-it-might-not-be-fixed-for-ubuntu-18-04-lts 2. https://bugs.launchpad.net/gnome-shell/+bug/1672297 3. https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1773959 4. https://askubuntu.com/a/1090987/165026 System info: Running Wayland. Description:Ubuntu 18.04.1 LTS Release:18.04 gnome-shell: Installert: 3.28.3-0ubuntu0.18.04.4 Kandidat: 3.28.3-0ubuntu0.18.04.4 Versjonstabell: *** 3.28.3-0ubuntu0.18.04.4 500 500 http://no.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.28.1-0ubuntu2 500 500 http://no.archive.ubuntu.com/ubuntu bionic/main amd64 Packages ** Affects: gnome-shell (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/1817620 Title: High cpu usage on alt-tab-ing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1817620/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1807047] Re: sync hd-media FLOPPY_SIZE with debian
ubuntu-18.10-server-amd64.iso 2018-10-17 22:20 717M (that fit) ubuntu-18.04.2-server-amd64.iso 2019-02-10 00:19883M (this does not) http://cdimage.ubuntu.com/releases/18.04.2/release/ + zcat cache/bionic/hd-media/boot.img.gz sudo dcfldd of=/dev/sda 24832 blocks (776Mb) written. 25056+0 records in 25056+0 records out + pmount /dev/sda + cp cache/bionic/ubuntu-18.04.2-server-amd64.iso cache/bionic/ubuntu-18.04.2-server-amd64.iso.SHA256SUM /media/sda cp: error writing '/media/sda/ubuntu-18.04.2-server-amd64.iso': No space left on device -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1807047 Title: sync hd-media FLOPPY_SIZE with debian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1807047/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1807047] Re: sync hd-media FLOPPY_SIZE with debian
ubuntu-18.10-server-amd64.iso 2018-10-17 22:20 717M (that fit) ubuntu-18.04.2-server-amd64.iso 2019-02-10 00:19883M (this does not) http://cdimage.ubuntu.com/releases/18.04.2/release/ + zcat cache/bionic/hd-media/boot.img.gz sudo dcfldd of=/dev/sda 24832 blocks (776Mb) written. 25056+0 records in 25056+0 records out + pmount /dev/sda + cp cache/bionic/ubuntu-18.04.2-server-amd64.iso cache/bionic/ubuntu-18.04.2-server-amd64.iso.SHA256SUM /media/sda cp: error writing '/media/sda/ubuntu-18.04.2-server-amd64.iso': No space left on device -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1807047 Title: sync hd-media FLOPPY_SIZE with debian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1807047/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1286910] Re: Lock screen uses last active window's language instead of default keyboard language
Yeah, that is the workaround we all use. However, it does not solve the bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1286910 Title: Lock screen uses last active window's language instead of default keyboard language To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1286910/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1812547] [NEW] wallpaper problem after restart
Public bug reported: after restart, wallpaper went black, and then after i replaced the black wallpaper, the wallpaper went white pixels ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: wallpaper (not installed) ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jan 20 16:43:53 2019 InstallationDate: Installed on 2019-01-20 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_PH.UTF-8 SHELL=/bin/bash SourcePackage: wallpaper UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: wallpaper (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug bionic ** Changed in: wallpaper (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1812547 Title: wallpaper problem after restart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wallpaper/+bug/1812547/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1575053] Re: Please move the "$HOME/snap" directory to a less obtrusive location
Not really a joke. Its the more reasonable approach. As someone already stated its not just configuration in the snap directory ... snap apps also seem (whether I agree with whether the SHOULD) to store data in the snap directory. My Videos are data. My Downloads are data. My Documents are data. Why cant snap apps store data in the Snap directory. Now an even MORE reasonable variant would be to put CONFIGURATION in .snap/ and DATA in Snap/. Apps that don't need to store data like the darn Calculator (come on please its a calculator if it needs temp files use /tmp) can just put config in .snap and not create the Snap directory at all. It IS a little ridiculous that every time i start the calculator it get a snap directory. Now ... don't get me wrong ... in a more ideal world (which I almost never get to live in in the not quite 30 years I have been writing software) you would put all data in the existing data directories where grandma knows where it is already and put config in .snap/ and call it a day. We, however, do not live in an ideal world and should, when POSSIBLE, compromise. For some people compromise seems to be a dirty word. When its a matter or principle you stand like an oak. When its a matter of style, bend like a willow. The problem is when you think EVERYTHING is principle. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1575053 Title: Please move the "$HOME/snap" directory to a less obtrusive location To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1575053/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1575053] Re: Please move the "$HOME/snap" directory to a less obtrusive location
A lot of discussion about moving the directory to .snap or .local. I would be happy is for all that is sacred if they are not going to hide it since data can be stored there PLEASE just capitalize it like every other visible folder in my home folder: \Desktop \Documents \Downloads \Music \Pictures \Public \Snap \Templates \Videos Whats so hard about being consistent so it does not immediately make me zero in on it and go ... one ... and only one of these is not like the other one. \Desktop \Documents \Downloads \Music \Pictures \Public \snap < \Templates \Videos -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1575053 Title: Please move the "$HOME/snap" directory to a less obtrusive location To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1575053/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1807047] Re: sync hd-media FLOPPY_SIZE with debian
why this? ubuntu-18.10-server-amd64.iso It isn't listed on http://releases.ubuntu.com/cosmic/ I did find it on: http://cdimage.ubuntu.com/releases/18.10/release/ 717M does fit so good. What for? hd-media installer needs it https://launchpad.net/iso-scan """ debian-installer component to scan hard drives for an installer ISO image. This is used in installer builds for removable USB drives. """ higher level goal: hd-media/boot.img is an fs I can mount, cp a replacement boot loader syslinux.cfg file, done. .iso is a read only fs, so not as easy to replace the file. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1807047 Title: sync hd-media FLOPPY_SIZE with debian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1807047/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1752961] Re: With kernel 4.13 btrfs scans for devices before all devices have been discovered
v4.17 final has the bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1752961 Title: With kernel 4.13 btrfs scans for devices before all devices have been discovered To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752961/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1807047] [NEW] sync hd-media FLOPPY_SIZE with debian
Public bug reported: please bump to 976560 (same as debian) https://git.launchpad.net/ubuntu/+source/debian-installer/tree/build/config/amd64/hd-media.cfg?h=ubuntu/disco FLOPPY_SIZE = 801792 https://salsa.debian.org/installer-team/debian-installer/blob/master/build/config/amd64/hd-media.cfg#L7 FLOPPY_SIZE = 976560 "large enough to put an Ubuntu iso in" No it is not, and I would like it to be. 881M Oct 17 18:39 ubuntu-18.10-live-server-amd64.iso ** Affects: debian-installer (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/1807047 Title: sync hd-media FLOPPY_SIZE with debian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1807047/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1752961] Re: With kernel 4.13 btrfs scans for devices before all devices have been discovered
I retested the last 2 builds from the original bisection, and I'm pretty confident that the results were correct: 362f672 has the bug. 6836796 does NOT have the bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1752961 Title: With kernel 4.13 btrfs scans for devices before all devices have been discovered To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752961/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1752961] Re: With kernel 4.13 btrfs scans for devices before all devices have been discovered
Mainline 4.20-rc2 has the bug. I went back and tested mainline 4.18-rc1 and mainline 4.18 a few more times, and they actually do have the bug. So it appears that the bug is not fixed upstream after all. Shall we go back to bisecting for the change that introduced the bug? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1752961 Title: With kernel 4.13 btrfs scans for devices before all devices have been discovered To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752961/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1752961] Re: With kernel 4.13 btrfs scans for devices before all devices have been discovered
It looks like I made a mistake on a previous build. I retested d60dafd, built on 20180911, and it actually does have the bug. Sorry! (Being an apparent race condition, a buggy kernel actually does work sometimes.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1752961 Title: With kernel 4.13 btrfs scans for devices before all devices have been discovered To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752961/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1752961] Re: With kernel 4.13 btrfs scans for devices before all devices have been discovered
18f1837 has the bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1752961 Title: With kernel 4.13 btrfs scans for devices before all devices have been discovered To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752961/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1752961] Re: With kernel 4.13 btrfs scans for devices before all devices have been discovered
Agreed. 68cc38f has the bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1752961 Title: With kernel 4.13 btrfs scans for devices before all devices have been discovered To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752961/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1280300] Re: Desktop contents displayed on resume, before lock screen is shown
I'd imagine a workaround could be to have a hook for suspend write to the framebuffer, but I failed at getting this working when I tried today (put a script in /usr/lib/systemd/system-sleep to invoke eog in fullscreen). Regarding the comment above about this being fixed in "certified" laptops, this doesn't seem to be 100% correct. See this on a Dell XPS 9350, and this machine was available in a "Developer edition" running Ubuntu. Still see this issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1280300 Title: Desktop contents displayed on resume, before lock screen is shown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1280300/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1752961] Re: With kernel 4.13 btrfs scans for devices before all devices have been discovered
6a8b25a has the bug. I also tried 4.18.0-10.11 from cosmic, and it appears to still have the bug. :( -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1752961 Title: With kernel 4.13 btrfs scans for devices before all devices have been discovered To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752961/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
