[Desktop-packages] [Bug 1929038] Re: [SRU] Backport to 20.04 LTS
Hey Łukasz! Thanks for accepting it! impish has a version of adsys. This is an entreprise feature and I doubt we have users there, as by default, this is hilighted for LTSes only. Functionality-wise, as there is no ubuntu-advantage-desktop-daemon, this is equivalent to the version already present there (apart from one bug fix). We can prepare the SRU if you feel this is a deal-breaker, but I think this is more for paperwork than having a real rationale. What’s your opinion on this? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to adsys in Ubuntu. https://bugs.launchpad.net/bugs/1929038 Title: [SRU] Backport to 20.04 LTS Status in adsys package in Ubuntu: Fix Released Status in golang-1.16 package in Ubuntu: Fix Released Status in adsys source package in Focal: Fix Committed Status in golang-1.16 source package in Focal: Fix Released Bug description: As part of our entreprise desktop offering, there is the request to backport ADSys to 20.04 LTS. The package is in universe for now. ADSys is our Active Directory GPO integration. It’s available starting Ubuntu 21.04. [Impact] * ADSys is a new package. Impacts is thus only for people installing. * It depends on a recent Golang (1.16). We thus needs to backport this package from Ubuntu 21.04/21.10 (1.16.2-0ubuntu1 at the time of this writing) by introducing a versioned separate package (each Go version is a separate package already in the distribution). It is similar to what has been done for snaps in previous LTS. * This is a entreprise feature requested by desktop customers running LTS. [Test Plan for Golang 1.16] 1. Ensure Golang 1.16 is published in -proposed 2. Start a build with a package, requiring Golang 1.16 (dependency + PATH set to Golang 1.16 go binary). 3. Ensure the package builds successfully. 4. Run go version which should display: "go1.16.x" (x being the version uploaded). [Test Plan for ADSys] 1. Configure your machine with AD, with a correctly configured SSSD and KRB5 (AD user should be able to log in). Instructions can be found on https://github.com/ubuntu/adsys/wiki/2.-Prerequisites 2. Install admx and adml files on your AD controller: https://github.com/ubuntu/adsys/wiki/3.-AD-Setup 3. Configure some values in AD (https://github.com/ubuntu/adsys/wiki/4.-Using-GPO), for instance: * GDM login screen background * User favorites apps 4. Install ADSys, reboot the machine and login in as an AD user 5. Ensure both GDM background and user favorites apps follows what you set in AD [Where problems could occur] For Go 1.16: * Package depending on this Go version would not be able to compile. * As this is a separate, versionned, new package, no impact on existing ones. * FYI, we already built ADSys against this Go version in our ppa: https://launchpad.net/~didrocks/+archive/ubuntu/adsys For ADSys: * Machine will fail booting if ADSys can’t connect to AD on first boot. * AD User will fail logging if ADSys can’t connect to AD on first boot. * As this is a separate, versionned, new package, no impact on existing installations. [Other Info] * ADSys (built against Go 1.16 in the same PPA) is battle-tested from our PPA. * We will first upload Go 1.16 and let it migrate before uploading ADSys itself. * Of course, ADSys new version (the one we will backport) will be first uploaded in Impish. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1929038/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1929038] Re: [SRU] Backport to 20.04 LTS
Hey Łukasz! Thanks for accepting it! impish has a version of adsys. This is an entreprise feature and I doubt we have users there, as by default, this is hilighted for LTSes only. Functionality-wise, as there is no ubuntu-advantage-desktop-daemon, this is equivalent to the version already present there (apart from one bug fix). We can prepare the SRU if you feel this is a deal-breaker, but I think this is more for paperwork than having a real rationale. What’s your opinion on this? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to adsys in Ubuntu. https://bugs.launchpad.net/bugs/1929038 Title: [SRU] Backport to 20.04 LTS Status in adsys package in Ubuntu: Fix Released Status in golang-1.16 package in Ubuntu: Fix Released Status in adsys source package in Focal: Fix Committed Status in golang-1.16 source package in Focal: Fix Released Bug description: As part of our entreprise desktop offering, there is the request to backport ADSys to 20.04 LTS. The package is in universe for now. ADSys is our Active Directory GPO integration. It’s available starting Ubuntu 21.04. [Impact] * ADSys is a new package. Impacts is thus only for people installing. * It depends on a recent Golang (1.16). We thus needs to backport this package from Ubuntu 21.04/21.10 (1.16.2-0ubuntu1 at the time of this writing) by introducing a versioned separate package (each Go version is a separate package already in the distribution). It is similar to what has been done for snaps in previous LTS. * This is a entreprise feature requested by desktop customers running LTS. [Test Plan for Golang 1.16] 1. Ensure Golang 1.16 is published in -proposed 2. Start a build with a package, requiring Golang 1.16 (dependency + PATH set to Golang 1.16 go binary). 3. Ensure the package builds successfully. 4. Run go version which should display: "go1.16.x" (x being the version uploaded). [Test Plan for ADSys] 1. Configure your machine with AD, with a correctly configured SSSD and KRB5 (AD user should be able to log in). Instructions can be found on https://github.com/ubuntu/adsys/wiki/2.-Prerequisites 2. Install admx and adml files on your AD controller: https://github.com/ubuntu/adsys/wiki/3.-AD-Setup 3. Configure some values in AD (https://github.com/ubuntu/adsys/wiki/4.-Using-GPO), for instance: * GDM login screen background * User favorites apps 4. Install ADSys, reboot the machine and login in as an AD user 5. Ensure both GDM background and user favorites apps follows what you set in AD [Where problems could occur] For Go 1.16: * Package depending on this Go version would not be able to compile. * As this is a separate, versionned, new package, no impact on existing ones. * FYI, we already built ADSys against this Go version in our ppa: https://launchpad.net/~didrocks/+archive/ubuntu/adsys For ADSys: * Machine will fail booting if ADSys can’t connect to AD on first boot. * AD User will fail logging if ADSys can’t connect to AD on first boot. * As this is a separate, versionned, new package, no impact on existing installations. [Other Info] * ADSys (built against Go 1.16 in the same PPA) is battle-tested from our PPA. * We will first upload Go 1.16 and let it migrate before uploading ADSys itself. * Of course, ADSys new version (the one we will backport) will be first uploaded in Impish. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1929038/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1951599] Re: gnome-shell logs errors when ejecting SD card
On impish, I tried the new version of gnome-shell-extenstion-ubuntu- dock, I couldn't find this recurring error any more, this issue is fixed on impish. Upgrade: gnome-shell-extension-ubuntu-dock:amd64 (70~ubuntu3, 70~ubuntu3.21.10.1) ** Tags removed: verification-needed-impish ** Tags added: verification-done-impish ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1951599 Title: gnome-shell logs errors when ejecting SD card Status in OEM Priority Project: Triaged Status in gnome-shell-extension-dashtodock package in Ubuntu: Fix Committed Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock source package in Impish: Fix Committed Bug description: [ Impact ] When I click eject SD card in Files(nautilus), I found the gnome-shell reported some crash logs. [ Test case ] - Mount a device - Eject the device - No errors should be shown and the device re-mountable [ Regression Potential ] Devices could be leaked if gc doesn't work as expected --- Nov 19 22:43:57 binli-ThinkPad-X1-Extreme-Gen-3 gnome-shell[2357]: Object .Gjs_components_autorunManager_AutorunSource (0x55a9d8e846e0), has been already deallocated — impossible to emit any signal on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Nov 19 22:43:57 binli-ThinkPad-X1-Extreme-Gen-3 gnome-shell[2357]: Object Gio.Settings (0x55a9db521970), has been already deallocated — impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Nov 19 22:43:57 binli-ThinkPad-X1-Extreme-Gen-3 gnome-shell[2357]: == Stack trace for context 0x55a9d8a00120 == Nov 19 22:43:57 binli-ThinkPad-X1-Extreme-Gen-3 gnome-shell[2357]: #0 7ffc0b63cc20 b resource:///org/gnome/shell/ui/messageTray.js:785 (bc6f58577e0 @ 149) Nov 19 22:43:57 binli-ThinkPad-X1-Extreme-Gen-3 gnome-shell[2357]: #1 55a9d8f150b0 i resource:///org/gnome/shell/ui/components/autorunManager.js:270 (1ec3f0bf4060 @ 69) Nov 19 22:43:57 binli-ThinkPad-X1-Extreme-Gen-3 gnome-shell[2357]: #2 55a9d8f15018 i resource:///org/gnome/shell/ui/components/autorunManager.js:176 (1ec3f0bf4290 @ 25) Nov 19 22:43:57 binli-ThinkPad-X1-Extreme-Gen-3 gnome-shell[2357]: #3 7ffc0b63d8c0 b self-hosted:850 (1ec3f0b2a650 @ 454) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1951599/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1532508] Re: Screen contents revealed briefly on resume, before even unlocking
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #2133 https://gitlab.gnome.org/GNOME/mutter/-/issues/2133 ** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/-/issues/2133 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1532508 Title: Screen contents revealed briefly on resume, before even unlocking Status in GNOME Shell: Unknown Status in Mutter: Unknown Status in gnome-shell package in Ubuntu: Confirmed Status in unity package in Ubuntu: Fix Released Status in unity source package in Xenial: Fix Released Status in gnome-shell package in Debian: Confirmed Bug description: [Impact] When lock is enabled, the screen doesn't get blank/covered by lockscreen before suspending, thus on early resume the content might be shown. Video showing the bug: https://youtu.be/dDOgtK1MldI Reproduced on Ubuntu 2015.10, Ubuntu 2014.04 [Test case] 1. Work on highly secret files 2. Close the lid of your laptop and go have a break 3. Anyone who opens the lid of the laptop can see the secret files for a half second before the lock screen appears [Possible Regression] Content on screen isn't painted anymore and screen stays black. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1532508/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1960386] Re: udisksd assert failure: malloc_consolidate(): unaligned fastbin chunk detected
*** This bug is a duplicate of bug 1955758 *** https://bugs.launchpad.net/bugs/1955758 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1955758, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1960386/+attachment/5559840/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1960386/+attachment/5559843/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1960386/+attachment/5559854/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1960386/+attachment/5559856/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1960386/+attachment/5559857/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1960386/+attachment/5559858/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1960386/+attachment/5559859/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1955758 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1960386 Title: udisksd assert failure: malloc_consolidate(): unaligned fastbin chunk detected Status in udisks2 package in Ubuntu: New Bug description: + ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: udisks2 2.9.4-1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 AssertionMessage: malloc_consolidate(): unaligned fastbin chunk detected CasperMD5CheckResult: unknown CustomUdevRuleFiles: 70-snap.snap-store.rules 70-snap.snapd.rules Date: Sun Feb 6 16:12:54 2022 ExecutablePath: /usr/libexec/udisks2/udisksd InstallationDate: Installed on 2021-12-21 (50 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: ASUSTeK COMPUTER INC. VM42 ProcCmdline: /usr/libexec/udisks2/udisksd ProcEnviron: LANG=ru_RU.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-18-generic root=UUID=3a06b8ea-b3f7-4e97-9c47-ac958cb75ccd ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: udisks2 StacktraceTop: __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f438d57813d "%s\n") at ../sysdeps/posix/libc_fatal.c:155 malloc_printerr (str=str@entry=0x7f438d57abc8 "malloc_consolidate(): unaligned fastbin chunk detected") at malloc.c:5543 malloc_consolidate (av=av@entry=0x7f438d5b1c60 ) at malloc.c:4637 _int_free (av=0x7f438d5b1c60 , p=0x55a77aec5fc0, have_lock=) at malloc.c:4561 __GI___libc_free (mem=) at malloc.c:3278 Title: udisksd assert failure: malloc_consolidate(): unaligned fastbin chunk detected UpgradeStatus: Upgraded to jammy on 2022-01-16 (23 days ago) UserGroups: N/A dmi.bios.date: 10/07/2015 dmi.bios.release: 4.6 dmi.bios.vendor: ASUSTeK COMPUTER INC. (Licensed from AMI) dmi.bios.version: 1401 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: VM42 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnASUSTeKCOMPUTERINC.(LicensedfromAMI):bvr1401:bd10/07/2015:br4.6:svnASUSTeKCOMPUTERINC.:pnVM42:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnVM42:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuSKU: dmi.product.family: Vivo PC dmi.product.name: VM42 dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUSTeK COMPUTER INC. separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1960386/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1578138] Re: 'BadRegion (invalid Region parameter)' causes WM to exit
[Expired for xorg (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1578138 Title: 'BadRegion (invalid Region parameter)' causes WM to exit Status in xorg package in Ubuntu: Expired Bug description: Same as https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1455916 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed May 4 12:03:42 2016 DistUpgraded: 2016-04-22 15:24:35,321 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process "./xorg_fix_proprietary.py" (No such file or directory) (8)) DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: vboxhost, 5.0.10, 4.2.0-35-generic, x86_64: installed vboxhost, 5.0.10, 4.4.0-21-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Tahiti XT [Radeon HD 7970/8970 OEM / R9 280X] [1002:6798] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Tahiti XT [Radeon HD 7970/8970 OEM / R9 280X] [1043:0442] InstallationDate: Installed on 2014-03-29 (766 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash swapaccount=1 nomdmonddf nomdmonisw nomdmonddf nomdmonisw vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2016-04-22 (11 days ago) dmi.bios.date: 07/05/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F11 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X79-UD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF11:bd07/05/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnX79-UD3:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Wed May 4 11:51:49 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.3-1ubuntu2 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1578138/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1629837] Re: Chrome + hardware acceleration after resume causes unusable system with Nvidia
[Expired for xorg (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1629837 Title: Chrome + hardware acceleration after resume causes unusable system with Nvidia Status in xorg package in Ubuntu: Expired Bug description: After resuming from a suspend, the Ubuntu UI lags so much the system is not usable. However, this happens only if chrome is running (or is started if not already running) and hardware acceleration is enabled in chrome. I've tried both GNOME Shell and Unity with the same result. ssh into the host works fine while the UI is unusable, showing excessive CPU usage by Xorg, gnome-shell and chrome processes. I tried disable the NVIDIA drivers to test with nouveau, but then the screen will not turn on after resume. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 NonfreeKernelModules: nvidia_uvm zfs zunicode zcommon znvpair zavl nvidia_drm 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.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 370.28 Thu Sep 1 19:45:04 PDT 2016 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.2) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Mon Oct 3 12:10:12 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.4.0-34-generic, x86_64: installed bbswitch, 0.8, 4.4.0-38-generic, x86_64: installed nvidia-370, 370.28, 4.4.0-38-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation Device [10de:1c60] (rev a1) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Device [1558:6a04] Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 10ab:9008 USI Co., Ltd Bus 001 Device 003: ID 1c7a:0603 LighTuning Technology Inc. Bus 001 Device 002: ID 046d:c047 Logitech, Inc. Laser Mouse M-UAL120 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook P65xRP ProcKernelCmdLine: BOOT_IMAGE=/ROOT/ubuntu@/boot/vmlinuz-4.4.0-38-generic root=ZFS=rpool/ROOT/ubuntu ro boot=zfs bootfs=rpool/ROOT/ubuntu SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/18/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.01 dmi.board.asset.tag: Tag 12345 dmi.board.name: P65xRP dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.01:bd07/18/2016:svnNotebook:pnP65xRP:pvrNotApplicable:rvnNotebook:rnP65xRP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.name: P65xRP dmi.product.version: Not Applicable dmi.sys.vendor: Notebook version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Mon Oct 3 11:34:58 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.3-1ubuntu2.3 To manage notifications about this bug go to:
[Desktop-packages] [Bug 1960383] [NEW] package libglib2.0-0:i386 2.64.6-1~ubuntu20.04.4 failed to install/upgrade: dependency problems - leaving triggers unprocessed
Public bug reported: While installing 21.04 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libglib2.0-0:i386 2.64.6-1~ubuntu20.04.4 ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Feb 9 13:04:28 2022 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2022-02-03 (5 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: i386 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.1 apt 2.0.6 SourcePackage: glib2.0 Title: package libglib2.0-0:i386 2.64.6-1~ubuntu20.04.4 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: glib2.0 (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package focal i386 need-duplicate-check third-party-packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1960383 Title: package libglib2.0-0:i386 2.64.6-1~ubuntu20.04.4 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in glib2.0 package in Ubuntu: New Bug description: While installing 21.04 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libglib2.0-0:i386 2.64.6-1~ubuntu20.04.4 ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Feb 9 13:04:28 2022 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2022-02-03 (5 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: i386 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.1 apt 2.0.6 SourcePackage: glib2.0 Title: package libglib2.0-0:i386 2.64.6-1~ubuntu20.04.4 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1960383/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1960336] Re: No login screen after recent update
To avoid confusion we should also not mention DisplayLink here. That's a separate issue so if you have problems with DisplayLink then please open a new bug about that. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1960336 Title: No login screen after recent update Status in gnome-shell package in Ubuntu: Incomplete Bug description: After a recent update, when using gdm3 as login manager, there is no account visible and it is not possible to login. When switching to lightdm I can login but sleep is broken and some notifications do not work. Running the latest 22.04 dev branch with Wayland and Nvidia driver. Had to select kernel 5.12 to have display link working. This issue occurs with and without external displays attached. A recent attempt to switch back to gdm3 gave me just a black screen. I tried to reinstall gdm3 to no avail. This seems like a quite serious issue, hence this report for the dev version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1960336/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1960336] Re: no login screen on Wayland with gdm3 after recent update
The login screen is provided by 'gnome-shell' so reassigning there. Also please run these commands to gather more information from the machine: apport-collect 1960336 lspci -k > lspci.txt journalctl -b-1 > prevboot.txt and attach the resulting text files here. In future please be sure to report bugs using the 'ubuntu-bug' command which will collect the required information automatically. ** Tags added: jammy ** Summary changed: - no login screen on Wayland with gdm3 after recent update + No login screen after recent update ** Package changed: gdm3 (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1960336 Title: No login screen after recent update Status in gnome-shell package in Ubuntu: Incomplete Bug description: After a recent update, when using gdm3 as login manager, there is no account visible and it is not possible to login. When switching to lightdm I can login but sleep is broken and some notifications do not work. Running the latest 22.04 dev branch with Wayland and Nvidia driver. Had to select kernel 5.12 to have display link working. This issue occurs with and without external displays attached. A recent attempt to switch back to gdm3 gave me just a black screen. I tried to reinstall gdm3 to no avail. This seems like a quite serious issue, hence this report for the dev version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1960336/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1738838] Re: Bluetooth icon shows "Off" and the only option given below it is "Turn Off"
** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Fix Committed ** Tags added: fixed-in-42 fixed-upstream -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1738838 Title: Bluetooth icon shows "Off" and the only option given below it is "Turn Off" Status in GNOME Bluetooth: Fix Released Status in GNOME Shell: Unknown Status in gnome-bluetooth package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Fix Committed Bug description: See video. I have installed bluetooth, blueman, bluez but it makes no difference to a broken interface to control bluetooth under Gnome 17.10, as shown in the attached video. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: bluetooth 5.46-0ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Dec 17 22:32:30 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-18 (30 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) InterestingModules: bnep btusb bluetooth MachineType: LENOVO 20BXCTO1WW PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic.efi.signed root=UUID=02bd5120-a925-442c-a0dd-1cce59920632 ro quiet splash psmouse.synaptics_intertouch=0 vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/06/2015 dmi.bios.vendor: LENOVO dmi.bios.version: JBET54WW (1.19 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BXCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET54WW(1.19):bd11/06/2015:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450s dmi.product.name: 20BXCTO1WW dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO hciconfig: To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-bluetooth/+bug/1738838/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1960372] Re: DPMS ignores attempts to DISABLE IT
If normal user programs are allowed to access dpms then it is a security issue. Requesting the security team be brought in to help on this. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libxcb in Ubuntu. https://bugs.launchpad.net/bugs/1960372 Title: DPMS ignores attempts to DISABLE IT Status in libxcb package in Ubuntu: New Bug description: I'm on a fresh installation of Debian, linux image 5.10, with a radeon RX580 gpu. My computer is not honoring the setting to "never" turn the monitor off, in power settings. DPMS is still killing the monitor after 10 minutes. It appears bugged. I have to manually turn DPMS with a cron job every 5 minutes to make sure it "stays off". I don't want DPMS. I want my monitor to always stay on ALWAYS FOREVER AND EVER NO MATTER WHAT HAPPENS. Why is DPMS fighting me??? How do I completely disable and REMOVE this bugged program "dpms" from my system, safely??? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxcb/+bug/1960372/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1960372] Re: DPMS ignores attempts to DISABLE IT
One part of this issue seems to be, MAYBE, that VLC is enabling DPMS somehow. It should not be allowed to do that. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libxcb in Ubuntu. https://bugs.launchpad.net/bugs/1960372 Title: DPMS ignores attempts to DISABLE IT Status in libxcb package in Ubuntu: New Bug description: I'm on a fresh installation of Debian, linux image 5.10, with a radeon RX580 gpu. My computer is not honoring the setting to "never" turn the monitor off, in power settings. DPMS is still killing the monitor after 10 minutes. It appears bugged. I have to manually turn DPMS with a cron job every 5 minutes to make sure it "stays off". I don't want DPMS. I want my monitor to always stay on ALWAYS FOREVER AND EVER NO MATTER WHAT HAPPENS. Why is DPMS fighting me??? How do I completely disable and REMOVE this bugged program "dpms" from my system, safely??? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxcb/+bug/1960372/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1960372] [NEW] DPMS ignores attempts to DISABLE IT
Public bug reported: I'm on a fresh installation of Debian, linux image 5.10, with a radeon RX580 gpu. My computer is not honoring the setting to "never" turn the monitor off, in power settings. DPMS is still killing the monitor after 10 minutes. It appears bugged. I have to manually turn DPMS with a cron job every 5 minutes to make sure it "stays off". I don't want DPMS. I want my monitor to always stay on ALWAYS FOREVER AND EVER NO MATTER WHAT HAPPENS. Why is DPMS fighting me??? How do I completely disable and REMOVE this bugged program "dpms" from my system, safely??? ** Affects: libxcb (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libxcb in Ubuntu. https://bugs.launchpad.net/bugs/1960372 Title: DPMS ignores attempts to DISABLE IT Status in libxcb package in Ubuntu: New Bug description: I'm on a fresh installation of Debian, linux image 5.10, with a radeon RX580 gpu. My computer is not honoring the setting to "never" turn the monitor off, in power settings. DPMS is still killing the monitor after 10 minutes. It appears bugged. I have to manually turn DPMS with a cron job every 5 minutes to make sure it "stays off". I don't want DPMS. I want my monitor to always stay on ALWAYS FOREVER AND EVER NO MATTER WHAT HAPPENS. Why is DPMS fighting me??? How do I completely disable and REMOVE this bugged program "dpms" from my system, safely??? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxcb/+bug/1960372/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1959525] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1959525 Title: Occasional no display output on 6900XT or if been idle for too long Status in libdrm package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: New Bug description: ## No output at boot The dmesg I attached is from when nothing showed at boot. Journal output: $ journalctl -r --grep amdgpu -- Journal begins at Thu 2022-01-27 05:36:17 EST, ends at Sun 2022-01-30 15:58:40 EST. -- Jan 30 15:50:24 Y4M1-II kernel: amdgpu: probe of :0c:00.0 failed with error -110 Jan 30 15:50:24 Y4M1-II kernel: [drm] amdgpu: ttm finalized Jan 30 15:50:24 Y4M1-II kernel: amdgpu_init+0x77/0x1000 [amdgpu] Jan 30 15:50:24 Y4M1-II kernel: amdgpu_pci_probe+0x12a/0x1b0 [amdgpu] Jan 30 15:50:24 Y4M1-II kernel: amdgpu_driver_load_kms.cold+0x46/0x83 [amdgpu] Jan 30 15:50:24 Y4M1-II kernel: amdgpu_driver_unload_kms+0x43/0x70 [amdgpu] Jan 30 15:50:24 Y4M1-II kernel: amdgpu_device_fini+0xc5/0x1e5 [amdgpu] Jan 30 15:50:24 Y4M1-II kernel: amdgpu_device_ip_fini.isra.0+0x206/0x2cd [amdgpu] Jan 30 15:50:24 Y4M1-II kernel: gmc_v10_0_sw_fini+0x33/0x40 [amdgpu] Jan 30 15:50:24 Y4M1-II kernel: amdgpu_bo_fini+0x12/0x50 [amdgpu] Jan 30 15:50:24 Y4M1-II kernel: amdgpu_ttm_fini+0xab/0x100 [amdgpu] Jan 30 15:50:24 Y4M1-II kernel: amdgpu_vram_mgr_fini+0xe8/0x160 [amdgpu] Jan 30 15:50:24 Y4M1-II kernel: Modules linked in: hid_generic usbhid hid amdgpu(+) iommu_v2 gpu_sched i2c_algo_bit drm_ttm_helper ttm drm_kms_helper crct10dif_pclmul syscopyarea crc32_pclmul sysfillrect ghash_clmulni_intel sysimgblt fb_sys_fops cec aesni_intel rc_core crypto_simd cryptd drm nvme ahci xhci_pci i2c_piix4 nvme_core igc libahci xhci_pci_renesas wmi Jan 30 15:50:24 Y4M1-II kernel: [drm:psp_v11_0_ring_destroy [amdgpu]] *ERROR* Fail to stop psp ring Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: amdgpu: finishing device. Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: Fatal error during GPU init Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: amdgpu_device_ip_init failed Jan 30 15:50:24 Y4M1-II kernel: [drm:amdgpu_device_ip_init [amdgpu]] *ERROR* hw_init of IP block failed -110 Jan 30 15:50:24 Y4M1-II kernel: [drm:amdgpu_gfx_enable_kcq.cold [amdgpu]] *ERROR* KCQ enable failed Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: [drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring kiq_2.1.0 test failed (-110) Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: SMU is initialized successfully! Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: use vbios provided pptable Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: SMU driver if version not matched Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: smu driver if version = 0x003d, smu fw if version = 0x0040, smu fw version = 0x003a4700 (58.71.0) Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: Will use PSP to load VCN firmware Jan 30 15:50:24 Y4M1-II kernel: [drm] amdgpu: 16368M of GTT memory ready. Jan 30 15:50:24 Y4M1-II kernel: [drm] amdgpu: 16368M of VRAM memory ready Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: AGP: 267894784M 0x0084 - 0x Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: GART: 512M 0x - 0x1FFF Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: VRAM: 16368M 0x0080 - 0x0083FEFF (16368M used) Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: SRAM ECC is not presented. Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: MEM ECC is not presented. Jan 30 15:50:24 Y4M1-II kernel: amdgpu: ATOM BIOS: 113-EXT800216-L05 Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: Fetched VBIOS from VFCT Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: Trusted Memory Zone (TMZ) feature not supported Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: enabling device (0006 -> 0007) Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: vgaarb: deactivate vga console Jan 30 15:50:24 Y4M1-II kernel: fb0: switching to amdgpudrmfb from EFI VGA Jan 30 15:50:24 Y4M1-II kernel: amdgpu: Topology: Add CPU node Jan 30 15:50:24 Y4M1-II kernel: amdgpu: Virtual CRAT table created for CPU Jan 30 15:50:24 Y4M1-II kernel: amdgpu: Ignoring ACPI CRAT on non-APU system Jan 30 15:50:24 Y4M1-II kernel: [drm] amdgpu kernel modesetting enabled. Jan 30 15:50:24 Y4M1-II kernel: Kernel command
[Desktop-packages] [Bug 1960313] Re: [snap] chromium crashes regularly
guiverc@d960-ubu2:/de2900/others/railway$ snap info --abs-time gnome-3-38-2004 name: gnome-3-38-2004 summary: Shared GNOME 3.38 Ubuntu stack publisher: Canonical✓ store-url: https://snapcraft.io/gnome-3-38-2004 license: unset description: | This snap includes a GNOME 3.38 stack (the base libraries and desktop integration components) and shares it through the content interface. snap-id: rw36mkAjdIKl13dzfwyxP87cejpyIcct tracking: latest/stable refresh-date: 2022-01-11T15:21:38+11:00 channels: latest/stable:0+git.cd626d1 2021-11-22T21:01:02Z (87) 259MB - latest/candidate: 0+git.1f9014a 2022-01-08T01:54:11Z (99) 260MB - latest/beta: ↑ latest/edge: ↑ installed: 0+git.cd626d1 (87) 259MB - --- guiverc@d960-ubu2:/de2900/others/railway$ snap info --abs-time core20 name: core20 summary: Runtime environment based on Ubuntu 20.04 publisher: Canonical✓ store-url: https://snapcraft.io/core20 contact: https://github.com/snapcore/core20/issues license: unset description: | The base snap based on the Ubuntu 20.04 release. type: base snap-id: DLqre5XGLbDqg9jPtiAhRRjDuPVa5X1q tracking: latest/stable refresh-date: 2022-01-27T12:47:40+11:00 channels: latest/stable:20220114 2022-01-28T16:10:53Z (1328) 64MB - latest/candidate: 20220114 2022-01-25T21:05:26Z (1328) 64MB - latest/beta: 20220207 2022-02-07T17:05:29Z (1340) 64MB - latest/edge: 20220207 2022-02-07T12:16:10Z (1340) 64MB - installed: 20220114 (1328) 64MB base --- guiverc@d960-ubu2:/de2900/others/railway$ snap get core experimental.refresh-app-awareness error: access denied (try with sudo) guiverc@d960-ubu2:/de2900/others/railway$ sudo snap get core experimental.refresh-app-awareness [sudo] password for guiverc: true -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1960313 Title: [snap] chromium crashes regularly Status in chromium-browser package in Ubuntu: Incomplete Bug description: This was initially mentioned here (https://discourse.ubuntu.com/t/call-for-testing-chromium-browser-deb- to-snap-transition/11179/317) ** Description For awhile now I just find my chromium just closes and is gone. It’s been at least the last two updates (I get the nag screen on my screen telling me an update is available; I tend to ignore it but reboot my box every ~fortnight so it’ll update at least once per fortnight as I ensure it’s upgraded before I load it after reboot). It’s ~10:40 local time, and I’ve lost the chromium snap at least twice today… no clues as to why, just I get to see my wallpaper on that part of my monitor as the window silently disappears. On re-opening I get a ‘closed ; do you want to restore you tabs’ dialog (something like that anyway) which works, but my box has been up ~13 days, and it was giving me trouble before this reboot as I hoped that reboot would help; alas no; neither last update(s). If I was to guess how long, I'd guess 20-30 days if not more; ie. I'm basing that on two ~14 day reboot cycles... I can't recall if started during the last cycle or just prior to my second-last reboot ~28 days ago As I file this bug; it's now ~23:15 and whilst I mentioned it'd closed twice prior to ~10:40 (I turn box on ~07:30), I'm pretty sure the window has not closed since I posted on the community hub. I'm not usually using the window when it closes; though its closed ~twice whilst I'm using it. ** Limited details sorry I'm not very specific here sorry, I'd file it as 'incomplete', but I don't know how/where to get details. As a snap there is nothing in /var/crash; so as an aside; is there somewhere I can look for clues as to why etc. (like the .crash file in /var/crash, even if I can only understand bits of it) My box is slow (2009 dell desktop)... and I've got in the habit of keeping a terminal open with `htop` running so I can detect if `firefox` (deb package still) or `chromium` are losing RAM.. I've concluded (rightly/wrongly) it's extension related; but if I recognize extensive swapping I look at the `htop` window and if either browser is using a load more RAM than usual & swap size is growing, I tend to close browser, wait for OS to recover the RAM, then re-open.. I've NOT been doing this with chromium of late; so I wondered if it's started crashing where I'd normally notice a slowing box & switch to my htop window, then close the window down... HOWEVER it could also be the regular crashing means the 'ram bleed' issue isn't getting bad enough for the thrashing to become a problem; it's usually only a problem after 2-4 days.. I'm convinced the issue (what I call 'ram bleed') is related to
[Desktop-packages] [Bug 1927063] Re: Terminal prompt got strangely replicated when resizing terminal horizontally
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: readline (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1927063 Title: Terminal prompt got strangely replicated when resizing terminal horizontally Status in bash package in Ubuntu: Confirmed Status in gnome-terminal package in Ubuntu: Confirmed Status in mate-terminal package in Ubuntu: Confirmed Status in readline package in Ubuntu: Confirmed Status in tilix package in Ubuntu: Confirmed Status in vte2.91 package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have Ubuntu installed 2. Launch MATE Terminal 3. Navigate to some folder with long name - `cd /usr/share/doc/ayatana-indicator-application` 4. Resize terminal horizontally Expected results: * terminal shows the same "user@host:/usr/share/doc/ayatana-indicator-application$" with single occurrence Actual results: * terminal shows multiple occurrencies of "user@host:/usr/share/doc/ayatana-indicator-application$" (see attached screencast) ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: mate-terminal 1.24.1-1 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Tue May 4 10:54:59 2021 InstallationDate: Installed on 2021-04-23 (10 days ago) InstallationMedia: Ubuntu-MATE 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: mate-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1927063/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1958710] Re: Merge network-manager 1.34.0-2 (main) from Debian unstable/testing (main)
This bug was fixed in the package network-manager - 1.34.0-2ubuntu3 --- network-manager (1.34.0-2ubuntu3) jammy; urgency=medium * d/tests/control: Have nm.py autopkgtest Depend on wpasupplicant -- Jeremy Bicha Mon, 07 Feb 2022 16:40:52 -0500 ** Changed in: network-manager (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1958710 Title: Merge network-manager 1.34.0-2 (main) from Debian unstable/testing (main) Status in network-manager package in Ubuntu: Fix Released Bug description: There are some differences between versions from Debian and Ubuntu. A new version has been released a week ago. Debian Changelog: network-manager (1.34.0-2) unstable; urgency=medium * Demote wpasupplicant to Recommends. There are enough use cases for network-manager not involving Wi-Fi which justifies to make this dependency optional. (Closes: #919619, #980218) -- Michael Biebl Tue, 18 Jan 2022 20:59:36 +0100 network-manager (1.34.0-1) unstable; urgency=medium * New upstream version 1.34.0 * Rebase patches * Install nm-priv-helper service * Update symbols file for libnm0 -- Michael Biebl Fri, 14 Jan 2022 00:18:58 +0100 NM ChangeLog: = NetworkManager-1.34 Overview of changes since NetworkManager-1.32 = * initrd: wait for both IPv4 and IPv6 with "ip=dhcp,dhcp6". * core: better handle sd-resolved errors when resolving hostnames. * nmcli: fix import WireGuard profile with DNS domain and address family disabled. * ndisc: send router solicitations before expiry. * policy: send earlier the ip configs to the DNS manager. * core: support linking with LLD 13. * wireguard: importing wg-quick configuration files with nmcli no longer sets a negative, exclusive "dns-priority". This plays better with common split DNS setups that use systemd-resolved. Adjust the "dns-priority" to your liking after import yourself. * NetworkManager no longer listens for netlink events for traffic control objects (qdiscs and filters). * core: add internal nm-priv-helper service for separating privileges and have a way to drop capabilities from NetworkManager daemon. * bond: add support for setting queue-id of bond port. * dns: support configuring DNS over TLS (DoT) with systemd-resolved. * nmtui: add support for WireGuard profiles. * nmcli: add aliases `nmcli device up|down` beside connect|disconnect. * conscious language: Deprecate 'Device.Slaves' D-Bus property in favor of new 'Device.Ports' property. Depracate 'nm_device_*_get_slaves()' in favor of 'nm_device_get_ports()' in libnm. * nmcli: invoking nmcli command without arguments will now show 'default' instead of null address in route4 or route6 section. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1958710/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1929038] Re: [SRU] Backport to 20.04 LTS
Thank you! Accepted into focal-proposed. I think your proposition makes sense! Also, the bug description mentions updating adsys in impish as well - could someone prepare the SRU for that series and upload? It's not as important, but I think we should still not leave out impish users. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to adsys in Ubuntu. https://bugs.launchpad.net/bugs/1929038 Title: [SRU] Backport to 20.04 LTS Status in adsys package in Ubuntu: Fix Released Status in golang-1.16 package in Ubuntu: Fix Released Status in adsys source package in Focal: Fix Committed Status in golang-1.16 source package in Focal: Fix Released Bug description: As part of our entreprise desktop offering, there is the request to backport ADSys to 20.04 LTS. The package is in universe for now. ADSys is our Active Directory GPO integration. It’s available starting Ubuntu 21.04. [Impact] * ADSys is a new package. Impacts is thus only for people installing. * It depends on a recent Golang (1.16). We thus needs to backport this package from Ubuntu 21.04/21.10 (1.16.2-0ubuntu1 at the time of this writing) by introducing a versioned separate package (each Go version is a separate package already in the distribution). It is similar to what has been done for snaps in previous LTS. * This is a entreprise feature requested by desktop customers running LTS. [Test Plan for Golang 1.16] 1. Ensure Golang 1.16 is published in -proposed 2. Start a build with a package, requiring Golang 1.16 (dependency + PATH set to Golang 1.16 go binary). 3. Ensure the package builds successfully. 4. Run go version which should display: "go1.16.x" (x being the version uploaded). [Test Plan for ADSys] 1. Configure your machine with AD, with a correctly configured SSSD and KRB5 (AD user should be able to log in). Instructions can be found on https://github.com/ubuntu/adsys/wiki/2.-Prerequisites 2. Install admx and adml files on your AD controller: https://github.com/ubuntu/adsys/wiki/3.-AD-Setup 3. Configure some values in AD (https://github.com/ubuntu/adsys/wiki/4.-Using-GPO), for instance: * GDM login screen background * User favorites apps 4. Install ADSys, reboot the machine and login in as an AD user 5. Ensure both GDM background and user favorites apps follows what you set in AD [Where problems could occur] For Go 1.16: * Package depending on this Go version would not be able to compile. * As this is a separate, versionned, new package, no impact on existing ones. * FYI, we already built ADSys against this Go version in our ppa: https://launchpad.net/~didrocks/+archive/ubuntu/adsys For ADSys: * Machine will fail booting if ADSys can’t connect to AD on first boot. * AD User will fail logging if ADSys can’t connect to AD on first boot. * As this is a separate, versionned, new package, no impact on existing installations. [Other Info] * ADSys (built against Go 1.16 in the same PPA) is battle-tested from our PPA. * We will first upload Go 1.16 and let it migrate before uploading ADSys itself. * Of course, ADSys new version (the one we will backport) will be first uploaded in Impish. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1929038/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1929038] Re: [SRU] Backport to 20.04 LTS
Hello Didier, or anyone else affected, Accepted adsys into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/adsys/0.8~22.04 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: adsys (Ubuntu Focal) Status: Triaged => Fix Committed ** Tags removed: verification-done verification-done-focal ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to adsys in Ubuntu. https://bugs.launchpad.net/bugs/1929038 Title: [SRU] Backport to 20.04 LTS Status in adsys package in Ubuntu: Fix Released Status in golang-1.16 package in Ubuntu: Fix Released Status in adsys source package in Focal: Fix Committed Status in golang-1.16 source package in Focal: Fix Released Bug description: As part of our entreprise desktop offering, there is the request to backport ADSys to 20.04 LTS. The package is in universe for now. ADSys is our Active Directory GPO integration. It’s available starting Ubuntu 21.04. [Impact] * ADSys is a new package. Impacts is thus only for people installing. * It depends on a recent Golang (1.16). We thus needs to backport this package from Ubuntu 21.04/21.10 (1.16.2-0ubuntu1 at the time of this writing) by introducing a versioned separate package (each Go version is a separate package already in the distribution). It is similar to what has been done for snaps in previous LTS. * This is a entreprise feature requested by desktop customers running LTS. [Test Plan for Golang 1.16] 1. Ensure Golang 1.16 is published in -proposed 2. Start a build with a package, requiring Golang 1.16 (dependency + PATH set to Golang 1.16 go binary). 3. Ensure the package builds successfully. 4. Run go version which should display: "go1.16.x" (x being the version uploaded). [Test Plan for ADSys] 1. Configure your machine with AD, with a correctly configured SSSD and KRB5 (AD user should be able to log in). Instructions can be found on https://github.com/ubuntu/adsys/wiki/2.-Prerequisites 2. Install admx and adml files on your AD controller: https://github.com/ubuntu/adsys/wiki/3.-AD-Setup 3. Configure some values in AD (https://github.com/ubuntu/adsys/wiki/4.-Using-GPO), for instance: * GDM login screen background * User favorites apps 4. Install ADSys, reboot the machine and login in as an AD user 5. Ensure both GDM background and user favorites apps follows what you set in AD [Where problems could occur] For Go 1.16: * Package depending on this Go version would not be able to compile. * As this is a separate, versionned, new package, no impact on existing ones. * FYI, we already built ADSys against this Go version in our ppa: https://launchpad.net/~didrocks/+archive/ubuntu/adsys For ADSys: * Machine will fail booting if ADSys can’t connect to AD on first boot. * AD User will fail logging if ADSys can’t connect to AD on first boot. * As this is a separate, versionned, new package, no impact on existing installations. [Other Info] * ADSys (built against Go 1.16 in the same PPA) is battle-tested from our PPA. * We will first upload Go 1.16 and let it migrate before uploading ADSys itself. * Of course, ADSys new version (the one we will backport) will be first uploaded in Impish. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1929038/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1960339] [NEW] Problems setting Monday as first day of week
Public bug reported: I came across an interesting issue on my Ubuntu 21.10 machine. Originally I wanted to make the calendar applet in the shell menu to start the week on monday so I set up my language section according to the attached picture. Then I logged out from Gnome and nothing had changed when I logged back in. Pursuing this issue a bit further I thought of using gnome-calendar to isolate the problem but when I started the program from the application launcher, I noticed that gnome-calendar also had sunday as first day of the week. Digging a little deeper among the tips found through Google, I came across a post suggesting to set up my locale to deal with this situation: > locale LANG=sv_SE.UTF-8 LANGUAGE=en LC_CTYPE=sv_SE.UTF-8 LC_NUMERIC=sv_SE.UTF-8 LC_TIME=sv_SE.UTF-8 LC_COLLATE=sv_SE.UTF-8 LC_MONETARY=sv_SE.UTF-8 LC_MESSAGES=en_US.UTF-8 LC_PAPER=sv_SE.UTF-8 LC_NAME=sv_SE.UTF-8 LC_ADDRESS=sv_SE.UTF-8 LC_TELEPHONE=sv_SE.UTF-8 LC_MEASUREMENT=sv_SE.UTF-8 LC_IDENTIFICATION=sv_SE.UTF-8 LC_ALL= > grep first_weekday /usr/share/i18n/locales/sv_SE first_weekday 2 So, I tried starting gnome-calendar from my gnome-terminal, where I knew the regional settings were correct, and I still got the issue with sunday being the first day of the week. For no real reason I restarted the application just to make sure I hadn't committed a user error but the problem still persisted. Being a bit frustrated at the point I rage- quit the program and just as I did that I realised I had to check an appointment so I quickly started gnome-calendar from the same terminal again and got an error message GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying When I re-tried starting gnome-calendar from the same terminal again, the application launched and this time with monday as first day of the week. Steps to reproduce 1. Start gnome-terminal 2. In terminal, issue command gnome-calendar 3. Quit Calendar and issue command gnome-calendar again in the same terminal two more times until error message appears as described above 4. Issue command gnome-calendar 5. Observe start of week is monday (as expected) This problem only seems to occur when I start the X11 session. I logged into the Wayland session to look at another problem and noticed that the calendar applet in the shell had monday as first day of the week. Starting gnome-calendar (from the shell menu) also presented me with a calendar where monday was the first day of the week. Logging out and into the X11 session again made the problem, as originally described above, re-appear. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-calendar 41.0-1 ProcVersionSignature: Ubuntu 5.13.0-28.31-generic 5.13.19 Uname: Linux 5.13.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Tue Feb 8 17:01:43 2022 InstallationDate: Installed on 2021-10-20 (111 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: gnome-calendar UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-calendar (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug gnome-calendar impish ** Attachment added: "Language settings" https://bugs.launchpad.net/bugs/1960339/+attachment/5559743/+files/Screenshot%20from%202021-12-10%2018-04-17.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1960339 Title: Problems setting Monday as first day of week Status in gnome-calendar package in Ubuntu: New Bug description: I came across an interesting issue on my Ubuntu 21.10 machine. Originally I wanted to make the calendar applet in the shell menu to start the week on monday so I set up my language section according to the attached picture. Then I logged out from Gnome and nothing had changed when I logged back in. Pursuing this issue a bit further I thought of using gnome-calendar to isolate the problem but when I started the program from the application launcher, I noticed that gnome-calendar also had sunday as first day of the week. Digging a little deeper among the tips found through Google, I came across a post suggesting to set up my locale to deal with this situation: > locale LANG=sv_SE.UTF-8 LANGUAGE=en LC_CTYPE=sv_SE.UTF-8 LC_NUMERIC=sv_SE.UTF-8 LC_TIME=sv_SE.UTF-8 LC_COLLATE=sv_SE.UTF-8 LC_MONETARY=sv_SE.UTF-8 LC_MESSAGES=en_US.UTF-8 LC_PAPER=sv_SE.UTF-8 LC_NAME=sv_SE.UTF-8 LC_ADDRESS=sv_SE.UTF-8 LC_TELEPHONE=sv_SE.UTF-8 LC_MEASUREMENT=sv_SE.UTF-8 LC_IDENTIFICATION=sv_SE.UTF-8 LC_ALL= > grep first_weekday /usr/share/i18n/locales/sv_SE first_weekday 2 So, I tried starting gnome-calendar from my gnome-terminal, where I knew the regional settings were correct, and I
[Desktop-packages] [Bug 1960333] Re: package xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 failed to install/upgrade: dpkg-deb --control subprocess returned error exit status 2
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that there was an error on your system when trying to install a particular package. Please execute the following command, as it will clear your package cache, in a terminal: sudo apt-get clean Then try performing the update again. This will likely resolve your issue, but the failure could be caused by filesystem or memory corruption. So please also run a fsck on your filesystem(s) and a memory test. Thanks in advance! [This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.] ** Tags added: corrupted-package ** Changed in: xorg-server (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1960333 Title: package xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 failed to install/upgrade: dpkg-deb --control subprocess returned error exit status 2 Status in xorg-server package in Ubuntu: Invalid Bug description: na ProblemType: Package DistroRelease: Ubuntu 20.04 Package: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None Date: Tue Feb 8 20:49:03 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ErrorMessage: dpkg-deb --control subprocess returned error exit status 2 ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RS740 [Radeon 2100] [1002:796e] (prog-if 00 [VGA controller]) Subsystem: Biostar Microtech Int'l Corp RS740 [Radeon 2100] [1565:0117] InstallationDate: Installed on 2022-02-08 (0 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: BIOSTAR Group A740G M2+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-27-generic root=UUID=86ee0e4f-7825-4af7-b47f-77b1960671e8 ro quiet splash vt.handoff=7 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: xorg-server Title: package xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 failed to install/upgrade: dpkg-deb --control subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/02/2008 dmi.bios.release: 8.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080014 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: A740G M2+ dmi.board.vendor: BIOSTAR Group dmi.board.version: 6.0 dmi.chassis.asset.tag: None dmi.chassis.type: 3 dmi.chassis.vendor: BIOSTAR Group dmi.chassis.version: 6.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080014:bd05/02/2008:br8.14:svnBIOSTARGroup:pnA740GM2+:pvr6.0:rvnBIOSTARGroup:rnA740GM2+:rvr6.0:cvnBIOSTARGroup:ct3:cvr6.0: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: A740G M2+ dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: 6.0 dmi.sys.vendor: BIOSTAR Group version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.5 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1960333/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1956915] Re: New bugfix release 21.2.6
Hi, since 4 weeks the state is "fix released". But I do not see this with: sudo apt dist-upgrade Why? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1956915 Title: New bugfix release 21.2.6 Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Focal: Fix Committed Status in mesa source package in Impish: Fix Committed Bug description: [Impact] This is the last point-release of the 21.2.x-series, we should put it in impish so latest bugfixes would get there, and in focal for 20.04.4 image. [Test case] Install the updates, test desktop use and some basic games etc on at least AMD and Intel hw. [Where things could go wrong] It's possible that some apps (like games) might regress on some hw, but there should not be a big risk for more wider bugs appearing in this update, since upstream and vendor (Intel) CI machinery have tested these. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1956915/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1951075] Re: Nautilus doesn't load and gives GVFS-WARNING
I can confirm the same intermittent issue and I also have Keybase installed. I don't recall having the issue prior to installing it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1951075 Title: Nautilus doesn't load and gives GVFS-WARNING Status in nautilus package in Ubuntu: Confirmed Bug description: After loading a cifs network drive on the command line, nautilus no longer loads and shows (org.gnome.Nautilus:17319): GVFS-WARNING **: 20:32:43.301: The peer- to-peer connection failed: Timeout was reached. Falling back to the session bus. Your application is probably missing --filesystem=xdg- run/gvfsd privileges. when run from the command line. This is not the same as https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1935734 as I'm not trying to open as root but as a non-privileged user. This only started happening after upgrading to 21.10 recently. I tried upgrading gvfs to 1.48.x though a ppa and the update didn't resolve the issue. It was working in 21.04, so I assume downgrading gvfs $ lsb_release -rd Description: Ubuntu 21.10 Release: 21.10 $ apt-cache policy nautilus gvfs nautilus: Installed: 1:40.2-1ubuntu1 Candidate: 1:40.2-1ubuntu1 Version table: *** 1:40.2-1ubuntu1 500 500 http://au.archive.ubuntu.com/ubuntu impish/main amd64 Packages 100 /var/lib/dpkg/status gvfs: Installed: 1.47.91-1ubuntu1 Candidate: 1.47.91-1ubuntu1 Version table: *** 1.47.91-1ubuntu1 500 500 http://au.archive.ubuntu.com/ubuntu impish/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: nautilus 1:40.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Nov 16 20:35:33 2021 InstallationDate: Installed on 2019-01-27 (1024 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: nautilus UpgradeStatus: Upgraded to impish on 2021-11-12 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1951075/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1960147] Re: download desktop 20.04.3 lts
No worries, this is understandable. Given that this isn't a problem specific to the Firefox Ubuntu package, and that fortunately you managed to work around the problem by using Chrome to download the iso, I'm closing this bug. Thanks again for the report. ** Changed in: firefox (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1960147 Title: download desktop 20.04.3 lts Status in firefox package in Ubuntu: Invalid Bug description: on http://releases.ubuntu.com/20.04.3/ - click on http://releases.ubuntu.com/20.04.3/ubuntu-20.04.3-desktop-amd64.iso, start to download image but it never finishes. I am using firefox 96.0.3 (64-bit) with the following extensions; adblockplus, noscript, print pdf, save page we, ublock origin and video downloadhelper. speedtest shows my connection to be about 80 mbps.My system is currently running win10 pro. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1960147/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1958047] Re: Clicking to close, but send report, didnt open chromium-browser bug report
Sorry for the lack of a timely response. If this was a crash, no bug was opened, only a crash report which was automatically uploaded to errors.ubuntu.com. You can inspect the list of all the crashes you reported with the following command: xdg-open https://errors.ubuntu.com/user/$(sudo cat /var/lib/whoopsie/whoopsie-id) As an aside, I see that you're using the i386 architecture. Note that chromium (as an upstream project) dropped support for this architecture a while back, so there's no guarantee with regards to stability or even functionality that Ubuntu packages can offer, unfortunately. ** Changed in: chromium-browser (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1958047 Title: Clicking to close, but send report, didnt open chromium-browser bug report Status in chromium-browser package in Ubuntu: Invalid Bug description: Clicking to close, but send report, didnt open chromium-browser bug report ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: chromium-browser 97.0.4692.71-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 5.4.0-94.106~18.04.1-generic 5.4.157 Uname: Linux 5.4.0-94-generic i686 ApportVersion: 2.20.9-0ubuntu7.27 Architecture: i386 CurrentDesktop: KDE DRM.card0-LVDS-1: enabled: enabled dpms: On status: connected edid-base64: AP///wAyDACpAAAQAQOAIRV4Cg8Ql1hSiCgjUFQBAQEBAQEBAQEBAQEBAQEBORwAoFAgFzAwICYAS88QAAAZORwAoFAgFzAwICYAS88Q/gBDRDUxNgIxNTRXMDEK/gAuPkxXerXo/wEBCiAgAE0= modes: 1280x800 DRM.card0-SVIDEO-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-VGA-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: Date: Sun Jan 16 04:16:30 2022 Desktop-Session: 'plasma' '/etc/xdg/xdg-plasma:/etc/xdg:/usr/share/kubuntu-default-settings/kf5-settings' '/usr/share/plasma:/usr/local/share:/usr/share:/var/lib/snapd/desktop' Env: 'None' 'None' InstallationDate: Installed on 2022-01-15 (0 days ago) InstallationMedia: Kubuntu 18.04.5 LTS "Bionic Beaver" - Release i386 (20200806.1) InstalledPlugins: Load-Avg-1min: 2.63 Load-Processes-Running-Percent: 0.2% Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Dell Inc. ME051 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-94-generic root=UUID=8c2d7681-4766-4186-bb7a-845993d56fb2 ro quiet splash vt.handoff=1 SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/07/2006 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0RJ272 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA10:bd11/07/2006:svnDellInc.:pnME051:pvr:rvnDellInc.:rn0RJ272:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: ME051 dmi.sys.vendor: Dell Inc. modified.conffile..etc.default.chromium-browser: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1958047/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1951075] Re: Nautilus doesn't load and gives GVFS-WARNING
I've been experiencing the same (intermittent) symptom on a relatively new install. It's hard to be sure, but I think I've resolved it by disabling keybase. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1951075 Title: Nautilus doesn't load and gives GVFS-WARNING Status in nautilus package in Ubuntu: Confirmed Bug description: After loading a cifs network drive on the command line, nautilus no longer loads and shows (org.gnome.Nautilus:17319): GVFS-WARNING **: 20:32:43.301: The peer- to-peer connection failed: Timeout was reached. Falling back to the session bus. Your application is probably missing --filesystem=xdg- run/gvfsd privileges. when run from the command line. This is not the same as https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1935734 as I'm not trying to open as root but as a non-privileged user. This only started happening after upgrading to 21.10 recently. I tried upgrading gvfs to 1.48.x though a ppa and the update didn't resolve the issue. It was working in 21.04, so I assume downgrading gvfs $ lsb_release -rd Description: Ubuntu 21.10 Release: 21.10 $ apt-cache policy nautilus gvfs nautilus: Installed: 1:40.2-1ubuntu1 Candidate: 1:40.2-1ubuntu1 Version table: *** 1:40.2-1ubuntu1 500 500 http://au.archive.ubuntu.com/ubuntu impish/main amd64 Packages 100 /var/lib/dpkg/status gvfs: Installed: 1.47.91-1ubuntu1 Candidate: 1.47.91-1ubuntu1 Version table: *** 1.47.91-1ubuntu1 500 500 http://au.archive.ubuntu.com/ubuntu impish/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: nautilus 1:40.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Nov 16 20:35:33 2021 InstallationDate: Installed on 2019-01-27 (1024 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: nautilus UpgradeStatus: Upgraded to impish on 2021-11-12 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1951075/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1960147] Re: download desktop 20.04.3 lts
I'm a newbie to bugzilla and it doesn't make sense to me. Also I'm involved in some significant personal issues and don't have the time to try to figure this out - sorry. On 2022-02-08 10:27 AM, Olivier Tilloy wrote: > Thanks for the feedback. Given that this is happening on Windows, would > you mind filing an upstream bug at > https://bugzilla.mozilla.org/enter_bug.cgi#h=dupes|Firefox, and sharing > the link to it here? > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1960147 Title: download desktop 20.04.3 lts Status in firefox package in Ubuntu: Incomplete Bug description: on http://releases.ubuntu.com/20.04.3/ - click on http://releases.ubuntu.com/20.04.3/ubuntu-20.04.3-desktop-amd64.iso, start to download image but it never finishes. I am using firefox 96.0.3 (64-bit) with the following extensions; adblockplus, noscript, print pdf, save page we, ublock origin and video downloadhelper. speedtest shows my connection to be about 80 mbps.My system is currently running win10 pro. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1960147/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1960336] [NEW] no login screen on Wayland with gdm3 after recent update
Public bug reported: After a recent update, when using gdm3 as login manager, there is no account visible and it is not possible to login. When switching to lightdm I can login but sleep is broken and some notifications do not work. Running the latest 22.04 dev branch with Wayland and Nvidia driver. Had to select kernel 5.12 to have display link working. This issue occurs with and without external displays attached. A recent attempt to switch back to gdm3 gave me just a black screen. I tried to reinstall gdm3 to no avail. This seems like a quite serious issue, hence this report for the dev version. ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1960336 Title: no login screen on Wayland with gdm3 after recent update Status in gdm3 package in Ubuntu: New Bug description: After a recent update, when using gdm3 as login manager, there is no account visible and it is not possible to login. When switching to lightdm I can login but sleep is broken and some notifications do not work. Running the latest 22.04 dev branch with Wayland and Nvidia driver. Had to select kernel 5.12 to have display link working. This issue occurs with and without external displays attached. A recent attempt to switch back to gdm3 gave me just a black screen. I tried to reinstall gdm3 to no avail. This seems like a quite serious issue, hence this report for the dev version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1960336/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1960333] [NEW] package xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 failed to install/upgrade: dpkg-deb --control subprocess returned error exit status 2
Public bug reported: na ProblemType: Package DistroRelease: Ubuntu 20.04 Package: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None Date: Tue Feb 8 20:49:03 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ErrorMessage: dpkg-deb --control subprocess returned error exit status 2 ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RS740 [Radeon 2100] [1002:796e] (prog-if 00 [VGA controller]) Subsystem: Biostar Microtech Int'l Corp RS740 [Radeon 2100] [1565:0117] InstallationDate: Installed on 2022-02-08 (0 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: BIOSTAR Group A740G M2+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-27-generic root=UUID=86ee0e4f-7825-4af7-b47f-77b1960671e8 ro quiet splash vt.handoff=7 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: xorg-server Title: package xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 failed to install/upgrade: dpkg-deb --control subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/02/2008 dmi.bios.release: 8.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080014 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: A740G M2+ dmi.board.vendor: BIOSTAR Group dmi.board.version: 6.0 dmi.chassis.asset.tag: None dmi.chassis.type: 3 dmi.chassis.vendor: BIOSTAR Group dmi.chassis.version: 6.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080014:bd05/02/2008:br8.14:svnBIOSTARGroup:pnA740GM2+:pvr6.0:rvnBIOSTARGroup:rnA740GM2+:rvr6.0:cvnBIOSTARGroup:ct3:cvr6.0: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: A740G M2+ dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: 6.0 dmi.sys.vendor: BIOSTAR Group version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.5 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1960333 Title: package xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 failed to install/upgrade: dpkg-deb --control subprocess returned error exit status 2 Status in xorg-server package in Ubuntu: New Bug description: na ProblemType: Package DistroRelease: Ubuntu 20.04 Package: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None Date: Tue Feb 8 20:49:03 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ErrorMessage: dpkg-deb --control subprocess returned error exit status 2 ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RS740 [Radeon 2100] [1002:796e] (prog-if 00 [VGA controller]) Subsystem: Biostar Microtech Int'l Corp RS740 [Radeon 2100] [1565:0117] InstallationDate: Installed on 2022-02-08 (0 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: BIOSTAR Group A740G M2+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-27-generic root=UUID=86ee0e4f-7825-4af7-b47f-77b1960671e8 ro quiet splash vt.handoff=7 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: xorg-server Title: package xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 failed to install/upgrade: dpkg-deb --control subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/02/2008 dmi.bios.release: 8.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080014 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: A740G M2+ dmi.board.vendor: BIOSTAR Group dmi.board.version: 6.0
[Desktop-packages] [Bug 1927205] Re: Chromium menu is blank and freezes application
Possibly related: https://forum.snapcraft.io/t/some-snap-apps-no-longer- starting-up-on-amd-laptop/26403. That post mentions that core20-based snaps aren't affected, and chromium was recently updated to core20. To anyone affected, can you please test again and let us know whether the problem is gone? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1927205 Title: Chromium menu is blank and freezes application Status in chromium-browser package in Ubuntu: Confirmed Bug description: When opening the Chromium menu (3 dots button), it shows an empty blank white box. Very often it also freezes the whole application for about 10 seconds Installed version: name: chromium summary: Chromium web browser, open-source version of Chrome publisher: Canonical✓ store-url: https://snapcraft.io/chromium contact: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bugs?field.tag=snap license: unset description: | An open-source browser project that aims to build a safer, faster, and more stable way for all Internet users to experience the web. commands: - chromium.chromedriver - chromium snap-id: XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R tracking: latest/stable refresh-date: 6 days ago, at 08:45 EEST channels: latest/stable:90.0.4430.93 2021-04-28 (1568) 145MB - latest/candidate: 90.0.4430.93 2021-04-28 (1568) 145MB - latest/beta: 91.0.4472.19 2021-04-28 (1566) 148MB - latest/edge: 92.0.4496.0 2021-05-05 (1575) 148MB - installed: 90.0.4430.93(1568) 145MB - Ubuntu version Description:Ubuntu 21.04 Release:21.04 DE: plasmashell 5.21.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1927205/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1956434] Re: bbswitch-dkms: drop support for armhf and ppc64el
** Changed in: bbswitch (Ubuntu Jammy) Importance: Undecided => High ** Changed in: bbswitch (Ubuntu Jammy) Status: New => Fix Committed ** Changed in: bbswitch (Ubuntu Jammy) Assignee: (unassigned) => Andrea Righi (arighi) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bbswitch in Ubuntu. https://bugs.launchpad.net/bugs/1956434 Title: bbswitch-dkms: drop support for armhf and ppc64el Status in bbswitch package in Ubuntu: Fix Committed Status in bbswitch source package in Jammy: Fix Committed Bug description: [Impact] bbswitch is a kernel module that is supposed to detect certain ACPI calls and toggle power on NVIDIA optimus video cards. There is no reason to provide this feature on architectures that don't have an ACPI bus. This will also prevent potential build failures in the future. [Test case] On armhf or ppc64el: apt install bbswitch-dkms ... ERROR: modpost: "acpi_root_dir" [/var/lib/dkms/bbswitch/0.8/build/bbswitch.ko] undefined! [Fix] Simply drop support for armhf and ppc64el. [Regression potential] This module won't be available if there's any "special" armhf or ppc64el system with an NVIDIA optimus card (I doubt a system like this will ever exist). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bbswitch/+bug/1956434/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1960147] Re: download desktop 20.04.3 lts
Thanks for the feedback. Given that this is happening on Windows, would you mind filing an upstream bug at https://bugzilla.mozilla.org/enter_bug.cgi#h=dupes|Firefox, and sharing the link to it here? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1960147 Title: download desktop 20.04.3 lts Status in firefox package in Ubuntu: Incomplete Bug description: on http://releases.ubuntu.com/20.04.3/ - click on http://releases.ubuntu.com/20.04.3/ubuntu-20.04.3-desktop-amd64.iso, start to download image but it never finishes. I am using firefox 96.0.3 (64-bit) with the following extensions; adblockplus, noscript, print pdf, save page we, ublock origin and video downloadhelper. speedtest shows my connection to be about 80 mbps.My system is currently running win10 pro. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1960147/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1960147] Re: download desktop 20.04.3 lts
Just tried with FF 96.0.3 and disabled all extensions - took just over an hour but never completed. When I tried with Chrome took about 20 minutes using the same hardware and same internet connection (realize that internet usage can vary day to day - that might account for a few minutes but not a factor of three (3)). On 2022-02-08 6:52 AM, Olivier Tilloy wrote: > Just tested this with Firefox 97.0 installed as a snap (candidate > channel) on Ubuntu 21.10, and the iso downloads fine from the http link > in the description. > > Also tested in an Ubuntu 20.04 VM with Firefox 96.0.3 installed as a > snap (stable channel), and the iso also downloads fine from the http > link. > > Finally I tested in the same Ubuntu 20.04 VM with Firefox 97.0 installed > as a deb (from the PPA used to prepare firefox updates), and downloading > the iso from the http link worked too. > > Could it be that one of your extensions is getting in the way? Can you > try again with Firefox in safe mode (with all extensions disabled)? > > ** Changed in: firefox (Ubuntu) > Status: New => Incomplete > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1960147 Title: download desktop 20.04.3 lts Status in firefox package in Ubuntu: Incomplete Bug description: on http://releases.ubuntu.com/20.04.3/ - click on http://releases.ubuntu.com/20.04.3/ubuntu-20.04.3-desktop-amd64.iso, start to download image but it never finishes. I am using firefox 96.0.3 (64-bit) with the following extensions; adblockplus, noscript, print pdf, save page we, ublock origin and video downloadhelper. speedtest shows my connection to be about 80 mbps.My system is currently running win10 pro. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1960147/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1949553] Re: Backport packages for 20.04.4 HWE stack
tested on intel TGL-U, WHL, and AMD Radeon 520 Mobile, everything looks good ** Description changed: [Impact] These are needed for 20.04.4 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. [What could go wrong] libdrm: adds some new api, no changes to old stuff - llvm-13: a new package, no regression potential on it's own - mesa: a new major release, but we'll pull the final stable release of 21.2.x series, so there shouldn't be any regressions left at that point xserver: a new point-release, 1.20.x series is in deep maintenance mode, so there should be little chance of breakage ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1949553 Title: Backport packages for 20.04.4 HWE stack Status in libdrm package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Invalid Status in libdrm source package in Focal: Fix Committed Status in mesa source package in Focal: Fix Committed Status in xorg-server source package in Focal: Fix Released Bug description: [Impact] These are needed for 20.04.4 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. [What could go wrong] libdrm: adds some new api, no changes to old stuff mesa: a new major release, but we'll pull the final stable release of 21.2.x series, so there shouldn't be any regressions left at that point xserver: a new point-release, 1.20.x series is in deep maintenance mode, so there should be little chance of breakage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1949553/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1956915] Re: New bugfix release 21.2.6
** Tags removed: verification-needed verification-needed-focal verification-needed-impish ** Tags added: verification-done verification-done-focal verification-done-impish -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1956915 Title: New bugfix release 21.2.6 Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Focal: Fix Committed Status in mesa source package in Impish: Fix Committed Bug description: [Impact] This is the last point-release of the 21.2.x-series, we should put it in impish so latest bugfixes would get there, and in focal for 20.04.4 image. [Test case] Install the updates, test desktop use and some basic games etc on at least AMD and Intel hw. [Where things could go wrong] It's possible that some apps (like games) might regress on some hw, but there should not be a big risk for more wider bugs appearing in this update, since upstream and vendor (Intel) CI machinery have tested these. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1956915/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1960313] Re: chromium-browser has started closing regularly
Could you please share the output of the following commands? snap info --abs-time gnome-3-38-2004 snap info --abs-time core20 snap get core experimental.refresh-app-awareness ** Summary changed: - chromium-browser has started closing regularly + [snap] chromium crashes regularly ** Changed in: chromium-browser (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1960313 Title: [snap] chromium crashes regularly Status in chromium-browser package in Ubuntu: Incomplete Bug description: This was initially mentioned here (https://discourse.ubuntu.com/t/call-for-testing-chromium-browser-deb- to-snap-transition/11179/317) ** Description For awhile now I just find my chromium just closes and is gone. It’s been at least the last two updates (I get the nag screen on my screen telling me an update is available; I tend to ignore it but reboot my box every ~fortnight so it’ll update at least once per fortnight as I ensure it’s upgraded before I load it after reboot). It’s ~10:40 local time, and I’ve lost the chromium snap at least twice today… no clues as to why, just I get to see my wallpaper on that part of my monitor as the window silently disappears. On re-opening I get a ‘closed ; do you want to restore you tabs’ dialog (something like that anyway) which works, but my box has been up ~13 days, and it was giving me trouble before this reboot as I hoped that reboot would help; alas no; neither last update(s). If I was to guess how long, I'd guess 20-30 days if not more; ie. I'm basing that on two ~14 day reboot cycles... I can't recall if started during the last cycle or just prior to my second-last reboot ~28 days ago As I file this bug; it's now ~23:15 and whilst I mentioned it'd closed twice prior to ~10:40 (I turn box on ~07:30), I'm pretty sure the window has not closed since I posted on the community hub. I'm not usually using the window when it closes; though its closed ~twice whilst I'm using it. ** Limited details sorry I'm not very specific here sorry, I'd file it as 'incomplete', but I don't know how/where to get details. As a snap there is nothing in /var/crash; so as an aside; is there somewhere I can look for clues as to why etc. (like the .crash file in /var/crash, even if I can only understand bits of it) My box is slow (2009 dell desktop)... and I've got in the habit of keeping a terminal open with `htop` running so I can detect if `firefox` (deb package still) or `chromium` are losing RAM.. I've concluded (rightly/wrongly) it's extension related; but if I recognize extensive swapping I look at the `htop` window and if either browser is using a load more RAM than usual & swap size is growing, I tend to close browser, wait for OS to recover the RAM, then re-open.. I've NOT been doing this with chromium of late; so I wondered if it's started crashing where I'd normally notice a slowing box & switch to my htop window, then close the window down... HOWEVER it could also be the regular crashing means the 'ram bleed' issue isn't getting bad enough for the thrashing to become a problem; it's usually only a problem after 2-4 days.. I'm convinced the issue (what I call 'ram bleed') is related to extensions, as the issue didn't occur with no extensions being used; but I prefer having privacy badger/ublock running - google docs offline - privacy badger - ublock origin - startpage (this was only ~recently added; not this one) FYI: I use same extensions with firefox too (except no startpage), and issue is the same; ~same frequency too (2-4 days) Anyway; if you can tell me if it'd be helpful to get/keep certain details; I'll do it, as I realize I'm not giving much. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: chromium-browser 1:85.0.4183.83-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: LXQt DRM.card0-DVI-I-1: enabled: enabled dpms: On status: connected edid-base64: AP///wAs7hAkAQEBAQAaAQOANB14KrclpFdRoCYQUFS/74CzAKlAlQCBwIGAqcBxT4EAAjqAGHE4LUBYLEUACSUhAAAeZiFQsFEAGzBAcDYACSUhAAAe/QA3TB5SEQAKICAgICAg/ABLQUxFRDI0TU9OQ0EKAJo= modes: 1920x1080 1600x1200 1680x1050 1600x900 1280x1024 1280x1024 1440x900 1360x768 1280x800 1152x864 1280x720 1024x768 1024x768 1024x768 832x624 800x600 800x600 800x600 800x600 640x480 640x480 640x480 640x480 720x400 DRM.card0-DVI-I-2: enabled: enabled dpms: On status: connected edid-base64: AP///wAEchMBz9ogAhYUAQOAMx14KsKFpFZNnCUSUFSzDABxT4EAgYCVALMA0cABAQEBAjqAGHE4LUBYLEUA/h8RAAAe/QA4Sx5TEQAKICAgICAg/ABBY2VyIEcyMzVICiAg/wBMSkswVzAxNjQzMjAKAIg= modes:
[Desktop-packages] [Bug 1866999] Re: gnome-calendar does not sync with Google Calendar
I'm on Ubuntu 20.04 with gnome-calendar 3.36.2 and have the same problem: Google calendar did not sync. Then I removed the cache in "~/.cache/evolution/calendar/", and gnome calendar showed no appointments at all (as expected). Clicking the "sync now" menu item changed the calendar icon briefly to a checkmark, but "journalctrl -f" said: > Feb 08 13:28:20 sybo gnome-calendar[17021]: Error synchronizing client > Feb 08 13:28:20 sybo gnome-calendar[17021]: Error synchronizing client > Feb 08 13:28:20 sybo gnome-calendar[17021]: Error synchronizing client for every calendar, enabled or not. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1866999 Title: gnome-calendar does not sync with Google Calendar Status in gnome-calendar package in Ubuntu: Confirmed Bug description: Since upgrading to 20.04dev, gnome-calendar doesn't show the events in my Google Calendar. Online accounts is activated and, for example, gnome-contacts does show the contacts I have in Google. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-calendar 3.36.0-1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 11 09:47:25 2020 InstallationDate: Installed on 2018-02-23 (746 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222) SourcePackage: gnome-calendar UpgradeStatus: Upgraded to focal on 2020-03-01 (9 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1866999/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1960313] [NEW] chromium-browser has started closing regularly
Public bug reported: This was initially mentioned here (https://discourse.ubuntu.com/t/call- for-testing-chromium-browser-deb-to-snap-transition/11179/317) ** Description For awhile now I just find my chromium just closes and is gone. It’s been at least the last two updates (I get the nag screen on my screen telling me an update is available; I tend to ignore it but reboot my box every ~fortnight so it’ll update at least once per fortnight as I ensure it’s upgraded before I load it after reboot). It’s ~10:40 local time, and I’ve lost the chromium snap at least twice today… no clues as to why, just I get to see my wallpaper on that part of my monitor as the window silently disappears. On re-opening I get a ‘closed ; do you want to restore you tabs’ dialog (something like that anyway) which works, but my box has been up ~13 days, and it was giving me trouble before this reboot as I hoped that reboot would help; alas no; neither last update(s). If I was to guess how long, I'd guess 20-30 days if not more; ie. I'm basing that on two ~14 day reboot cycles... I can't recall if started during the last cycle or just prior to my second-last reboot ~28 days ago As I file this bug; it's now ~23:15 and whilst I mentioned it'd closed twice prior to ~10:40 (I turn box on ~07:30), I'm pretty sure the window has not closed since I posted on the community hub. I'm not usually using the window when it closes; though its closed ~twice whilst I'm using it. ** Limited details sorry I'm not very specific here sorry, I'd file it as 'incomplete', but I don't know how/where to get details. As a snap there is nothing in /var/crash; so as an aside; is there somewhere I can look for clues as to why etc. (like the .crash file in /var/crash, even if I can only understand bits of it) My box is slow (2009 dell desktop)... and I've got in the habit of keeping a terminal open with `htop` running so I can detect if `firefox` (deb package still) or `chromium` are losing RAM.. I've concluded (rightly/wrongly) it's extension related; but if I recognize extensive swapping I look at the `htop` window and if either browser is using a load more RAM than usual & swap size is growing, I tend to close browser, wait for OS to recover the RAM, then re-open.. I've NOT been doing this with chromium of late; so I wondered if it's started crashing where I'd normally notice a slowing box & switch to my htop window, then close the window down... HOWEVER it could also be the regular crashing means the 'ram bleed' issue isn't getting bad enough for the thrashing to become a problem; it's usually only a problem after 2-4 days.. I'm convinced the issue (what I call 'ram bleed') is related to extensions, as the issue didn't occur with no extensions being used; but I prefer having privacy badger/ublock running - google docs offline - privacy badger - ublock origin - startpage (this was only ~recently added; not this one) FYI: I use same extensions with firefox too (except no startpage), and issue is the same; ~same frequency too (2-4 days) Anyway; if you can tell me if it'd be helpful to get/keep certain details; I'll do it, as I realize I'm not giving much. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: chromium-browser 1:85.0.4183.83-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: LXQt DRM.card0-DVI-I-1: enabled: enabled dpms: On status: connected edid-base64: AP///wAs7hAkAQEBAQAaAQOANB14KrclpFdRoCYQUFS/74CzAKlAlQCBwIGAqcBxT4EAAjqAGHE4LUBYLEUACSUhAAAeZiFQsFEAGzBAcDYACSUhAAAe/QA3TB5SEQAKICAgICAg/ABLQUxFRDI0TU9OQ0EKAJo= modes: 1920x1080 1600x1200 1680x1050 1600x900 1280x1024 1280x1024 1440x900 1360x768 1280x800 1152x864 1280x720 1024x768 1024x768 1024x768 832x624 800x600 800x600 800x600 800x600 640x480 640x480 640x480 640x480 720x400 DRM.card0-DVI-I-2: enabled: enabled dpms: On status: connected edid-base64: AP///wAEchMBz9ogAhYUAQOAMx14KsKFpFZNnCUSUFSzDABxT4EAgYCVALMA0cABAQEBAjqAGHE4LUBYLEUA/h8RAAAe/QA4Sx5TEQAKICAgICAg/ABBY2VyIEcyMzVICiAg/wBMSkswVzAxNjQzMjAKAIg= modes: 1920x1080 1680x1050 1280x1024 1440x900 1280x800 1152x864 1024x768 1024x768 800x600 800x600 640x480 640x480 720x400 Date: Tue Feb 8 22:48:11 2022 DiskUsage: Filesystem Type Size Used Avail Use% Mounted on /dev/sda4 xfs32G 32G 63M 100% /home tmpfs tmpfs 3.9G 174M 3.7G 5% /dev/shm /home/guiverc/.Private ecryptfs 32G 32G 63M 100% /home/guiverc EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-16 (1545 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: Dell Inc. OptiPlex 960 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-17-generic root=UUID=afa7971f-3dd5-4b30-9c98-0af3e56a6f2b ro quiet splash vt.handoff=7 RebootRequiredPkgs:
[Desktop-packages] [Bug 1929038] Re: [SRU] Backport to 20.04 LTS
Thanks Łukasz! This is now in focal NEW. I think this could be accepted, migrate to update even and then, we can think about promoting it to main once #1936907 is approved. What do you think? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to adsys in Ubuntu. https://bugs.launchpad.net/bugs/1929038 Title: [SRU] Backport to 20.04 LTS Status in adsys package in Ubuntu: Fix Released Status in golang-1.16 package in Ubuntu: Fix Released Status in adsys source package in Focal: Triaged Status in golang-1.16 source package in Focal: Fix Released Bug description: As part of our entreprise desktop offering, there is the request to backport ADSys to 20.04 LTS. The package is in universe for now. ADSys is our Active Directory GPO integration. It’s available starting Ubuntu 21.04. [Impact] * ADSys is a new package. Impacts is thus only for people installing. * It depends on a recent Golang (1.16). We thus needs to backport this package from Ubuntu 21.04/21.10 (1.16.2-0ubuntu1 at the time of this writing) by introducing a versioned separate package (each Go version is a separate package already in the distribution). It is similar to what has been done for snaps in previous LTS. * This is a entreprise feature requested by desktop customers running LTS. [Test Plan for Golang 1.16] 1. Ensure Golang 1.16 is published in -proposed 2. Start a build with a package, requiring Golang 1.16 (dependency + PATH set to Golang 1.16 go binary). 3. Ensure the package builds successfully. 4. Run go version which should display: "go1.16.x" (x being the version uploaded). [Test Plan for ADSys] 1. Configure your machine with AD, with a correctly configured SSSD and KRB5 (AD user should be able to log in). Instructions can be found on https://github.com/ubuntu/adsys/wiki/2.-Prerequisites 2. Install admx and adml files on your AD controller: https://github.com/ubuntu/adsys/wiki/3.-AD-Setup 3. Configure some values in AD (https://github.com/ubuntu/adsys/wiki/4.-Using-GPO), for instance: * GDM login screen background * User favorites apps 4. Install ADSys, reboot the machine and login in as an AD user 5. Ensure both GDM background and user favorites apps follows what you set in AD [Where problems could occur] For Go 1.16: * Package depending on this Go version would not be able to compile. * As this is a separate, versionned, new package, no impact on existing ones. * FYI, we already built ADSys against this Go version in our ppa: https://launchpad.net/~didrocks/+archive/ubuntu/adsys For ADSys: * Machine will fail booting if ADSys can’t connect to AD on first boot. * AD User will fail logging if ADSys can’t connect to AD on first boot. * As this is a separate, versionned, new package, no impact on existing installations. [Other Info] * ADSys (built against Go 1.16 in the same PPA) is battle-tested from our PPA. * We will first upload Go 1.16 and let it migrate before uploading ADSys itself. * Of course, ADSys new version (the one we will backport) will be first uploaded in Impish. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1929038/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1956949] Re: CPC AWS jammy builds fail with: "fuse3 : Breaks: fuse"
@Paride Thanks for your help and explanations. Yeah I know what multi- arch does although I didn't know about 'Multi-Arch: foreign' - so thank you very much for the pointers. @Christian I have uploaded the updated package to mentors on Sunday. It was prepared on Ubuntu, though, I guess it is better when to redo the steps through a debian chroot - I hope I come to that in the evening. https://mentors.debian.net/package/unionfs-fuse/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1956949 Title: CPC AWS jammy builds fail with: "fuse3 : Breaks: fuse" Status in launchpad-buildd: Invalid Status in fuse3 package in Ubuntu: Invalid Status in gvfs package in Ubuntu: Fix Released Status in open-vm-tools package in Ubuntu: Fix Released Status in unionfs-fuse package in Ubuntu: New Bug description: CPC Jammy AWS image builds with livecd-rootfs fail now with: The following packages have unmet dependencies: fuse3 : Breaks: fuse This is relatively new (build worked on 20220104). The full build log can be seen at https://launchpad.net/~cloudware/+livefs/ubuntu/jammy/cpc/+build/320984 To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad-buildd/+bug/1956949/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1960147] Re: download desktop 20.04.3 lts
Just tested this with Firefox 97.0 installed as a snap (candidate channel) on Ubuntu 21.10, and the iso downloads fine from the http link in the description. Also tested in an Ubuntu 20.04 VM with Firefox 96.0.3 installed as a snap (stable channel), and the iso also downloads fine from the http link. Finally I tested in the same Ubuntu 20.04 VM with Firefox 97.0 installed as a deb (from the PPA used to prepare firefox updates), and downloading the iso from the http link worked too. Could it be that one of your extensions is getting in the way? Can you try again with Firefox in safe mode (with all extensions disabled)? ** Changed in: firefox (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1960147 Title: download desktop 20.04.3 lts Status in firefox package in Ubuntu: Incomplete Bug description: on http://releases.ubuntu.com/20.04.3/ - click on http://releases.ubuntu.com/20.04.3/ubuntu-20.04.3-desktop-amd64.iso, start to download image but it never finishes. I am using firefox 96.0.3 (64-bit) with the following extensions; adblockplus, noscript, print pdf, save page we, ublock origin and video downloadhelper. speedtest shows my connection to be about 80 mbps.My system is currently running win10 pro. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1960147/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1958242] Re: mesa update freeze/crash screen before login
please try the latest stable release from https://launchpad.net/~kisak/+archive/ubuntu/kisak-mesa then at least we'd know if it's fixed in 21.3.x ** Changed in: mesa (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1958242 Title: mesa update freeze/crash screen before login Status in mesa package in Ubuntu: Incomplete Bug description: After updating my laptop after a long trip. It starts to bootm, then screen goes black with the mouse pointer hanging over, sddm does not start. This symptoms I saw them before and were related to mesa libraries. See https://bugs.launchpad.net/ubuntu/+source/sddm/+bug/1909171 for details on that. But the actual problem seems somewhat different this time. Furthermore dmesg shows: [66.441074] QSGRenderThread[1134]: segfault at 39 ip 7f1ca6c7311b sp 7f1c98b76630 error 4 in r300_dri.so[7f1ca660b000+10ab000] [66.441088] Code: b6 40 2d eb ef 66 2e 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 31 f6 e9 95 a2 f9 ff 0f 1f 44 00 00 41 54 48 8d 15 97 b8 b2 00 55 53 <0f> b6 47 39 48 89 f3 48 63 04 82 48 01 d0 3e ff e0 0f 1f 40 00bd r300_dri.so is from the package libgl1-mesa-dri I applied the same workaround I did for the previous time that mesa was broken: downgrade to previous mesa version. I went to Ctrl+Alt-F2, logged in and: ** sudo apt install libglapi-mesa=21.0.3-0ubuntu0.3~20.04.5 libglx-mesa0=21.0.3-0ubuntu0.3~20.04.5 libgl1-mesa-dri=21.0.3-0ubuntu0.3~20.04.5 libegl-mesa0=21.0.3-0ubuntu0.3~20.04.5 libgbm1=21.0.3-0ubuntu0.3~20.04.5 sudo apt-mark hold libglapi-mesa=21.0.3-0ubuntu0.3~20.04.5 libglx-mesa0=21.0.3-0ubuntu0.3~20.04.5 libgl1-mesa-dri=21.0.3-0ubuntu0.3~20.04.5 libegl-mesa0=21.0.3-0ubuntu0.3~20.04.5 libgbm1=21.0.3-0ubuntu0.3~20.04.5 *** Now everything works fine. Other than the mentioned mesa packages everything else is fully updated. === In short something got broken again in mesa 21.2.6, downgrading to 21.0.3 fixes the issue. === Running Lubuntu 20.04 Kernel: 5.4.0-94-generic #106-Ubuntu SMP Thu Jan 6 23:58:14 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux lsb_release -rd: Description:Ubuntu 20.04.3 LTS Release:20.04 GPU: Advanced Micro Devices [AMD/ATI] RS482M [Mobility Radeon Xpress 200] driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1958242/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1956949] Re: CPC AWS jammy builds fail with: "fuse3 : Breaks: fuse"
FYI the re-upload of a fuse3 open-vm-tools happened yesterday and it migrated to jammy-release. Any issues with the images? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1956949 Title: CPC AWS jammy builds fail with: "fuse3 : Breaks: fuse" Status in launchpad-buildd: Invalid Status in fuse3 package in Ubuntu: Invalid Status in gvfs package in Ubuntu: Fix Released Status in open-vm-tools package in Ubuntu: Fix Released Status in unionfs-fuse package in Ubuntu: New Bug description: CPC Jammy AWS image builds with livecd-rootfs fail now with: The following packages have unmet dependencies: fuse3 : Breaks: fuse This is relatively new (build worked on 20220104). The full build log can be seen at https://launchpad.net/~cloudware/+livefs/ubuntu/jammy/cpc/+build/320984 To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad-buildd/+bug/1956949/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1960265] Re: package chromium-browser 97.0.4692.71-0ubuntu0.18.04.1 failed to install/upgrade: »neues chromium-browser-Skript des Paketes pre-installation«-Unterprozess gab den
This is the relevant output from DpkgTerminalLog.txt: error: cannot perform the following tasks: - Mount snap "chromium" (1897) (systemctl command [start snap-chromium-1897.mount] failed with exit status 1: Job failed. See "journalctl -xe" for details. ) Could you please run the following command and attach its output here? journalctl -u snapd And the output of this command too: snap tasks --abs-time --last=install? Thanks! ** Changed in: chromium-browser (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1960265 Title: package chromium-browser 97.0.4692.71-0ubuntu0.18.04.1 failed to install/upgrade: »neues chromium-browser-Skript des Paketes pre- installation«-Unterprozess gab den Fehlerwert 1 zurück Status in chromium-browser package in Ubuntu: Incomplete Bug description: chromium browser install problem while ubuntu release upgrade from 18.04 lts to 20.04 lts ProblemType: Package DistroRelease: Ubuntu 20.04 Package: chromium-browser 97.0.4692.71-0ubuntu0.18.04.1 Uname: Linux 4.9.253-tegra aarch64 ApportVersion: 2.20.9-0ubuntu7.27 Architecture: arm64 Date: Mon Feb 7 19:41:24 2022 Desktop-Session: 'None' 'None' 'None' Env: 'None' 'None' ErrorMessage: »neues chromium-browser-Skript des Paketes pre-installation«-Unterprozess gab den Fehlerwert 1 zurück InstalledPlugins: Load-Avg-1min: 1.67 Load-Processes-Running-Percent: 0.1% ProcKernelCmdLine: console=ttyTCU0,115200 video=tegrafb earlycon=tegra_comb_uart,mmio32,0x0c168000 gpt rootfs.slot_suffix= usbcore.old_scheme_first=1 tegraid=19.1.2.0.0 maxcpus=6 boot.slot_suffix=_b boot.ratchetvalues=0.4.2 vpr_resize sdhci_tegra.en_boot_part_access=1quiet root=/dev/mmcblk0p1 rw rootwait rootfstype=ext4 console=ttyTCU0,115200n8 console=tty0 fbcon=map:0 net.ifnames=0 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 SourcePackage: chromium-browser Title: package chromium-browser 97.0.4692.71-0ubuntu0.18.04.1 failed to install/upgrade: »neues chromium-browser-Skript des Paketes pre-installation«-Unterprozess gab den Fehlerwert 1 zurück UpgradeStatus: Upgraded to focal on 2022-02-07 (0 days ago) modified.conffile..etc.default.chromium-browser: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1960265/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1960307] [NEW] No gstreamer dependency causes high-fidelity codecs to be missing for Bluetooth devices
Public bug reported: After the announcements of PulseAudio 15 and Gstreamer 1.20, which both advertised LDAC and AptX (HD) support, I expected that jammy (22.04) would support those codecs. Though in reality it seems that something is missing, gstreamer reports that those codecs are supported but "pactl [...] list-codec" only lists sbc (and variants). Checking here https://packages.ubuntu.com/jammy/pulseaudio-module- bluetooth it seems that PulseAudio is not built with gstreamer support, is that the current blocker? ** Affects: gst-plugins-bad1.0 (Ubuntu) Importance: Undecided Status: New ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Also affects: gst-plugins-bad1.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1960307 Title: No gstreamer dependency causes high-fidelity codecs to be missing for Bluetooth devices Status in gst-plugins-bad1.0 package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: After the announcements of PulseAudio 15 and Gstreamer 1.20, which both advertised LDAC and AptX (HD) support, I expected that jammy (22.04) would support those codecs. Though in reality it seems that something is missing, gstreamer reports that those codecs are supported but "pactl [...] list-codec" only lists sbc (and variants). Checking here https://packages.ubuntu.com/jammy/pulseaudio-module- bluetooth it seems that PulseAudio is not built with gstreamer support, is that the current blocker? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-bad1.0/+bug/1960307/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1956005] Re: Firefox Snap won't open links to WhatsApp API
Launchpad has imported 1 comments from the remote bug at https://bugzilla.mozilla.org/show_bug.cgi?id=1754164. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2022-02-08T10:50:53+00:00 Olivier Tilloy wrote: User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:97.0) Gecko/20100101 Firefox/97.0 Steps to reproduce: (initially reported on Launchpad: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1956005) When using the Firefox snap, clicking a hyperlink to api.whatsapp.com shows a dialog that offers to use the "System Handler" to open the link, whereas when using e.g. the deb package on Ubuntu, Firefox doesn't try to delegate opening the link to an external handler. Example link: https://api.whatsapp.com/send/?phone=+1234567890=foobar_absent=0 Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1956005/comments/9 ** Changed in: firefox Status: Unknown => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1956005 Title: Firefox Snap won't open links to WhatsApp API Status in Mozilla Firefox: New Status in firefox package in Ubuntu: Confirmed Bug description: The .deb version of Firefox handles links to WhatsApp API (https://api.whatsapp.com/send/?phone=) without any problem: these links open the WhatsApp web client. Snap version of Firefox doesn't know how to handle these links. It opens the pop up "Choose an application to open whatsapp lnks" that only shows the option System Handler (which fails opening them if selected). Choosing Firefox is not possible as /bin and similar folders are out of range for the snap. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1956005/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1956005] Re: Firefox Snap won't open links to WhatsApp API
** Bug watch added: Mozilla Bugzilla #1754164 https://bugzilla.mozilla.org/show_bug.cgi?id=1754164 ** Also affects: firefox via https://bugzilla.mozilla.org/show_bug.cgi?id=1754164 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1956005 Title: Firefox Snap won't open links to WhatsApp API Status in Mozilla Firefox: New Status in firefox package in Ubuntu: Confirmed Bug description: The .deb version of Firefox handles links to WhatsApp API (https://api.whatsapp.com/send/?phone=) without any problem: these links open the WhatsApp web client. Snap version of Firefox doesn't know how to handle these links. It opens the pop up "Choose an application to open whatsapp lnks" that only shows the option System Handler (which fails opening them if selected). Choosing Firefox is not possible as /bin and similar folders are out of range for the snap. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1956005/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1956005] Re: Firefox Snap won't open links to WhatsApp API
LDZ: the firefox snap is not classic, it is strictly confined, you won't be able to install it with the "classic" mode. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1956005 Title: Firefox Snap won't open links to WhatsApp API Status in firefox package in Ubuntu: Confirmed Bug description: The .deb version of Firefox handles links to WhatsApp API (https://api.whatsapp.com/send/?phone=) without any problem: these links open the WhatsApp web client. Snap version of Firefox doesn't know how to handle these links. It opens the pop up "Choose an application to open whatsapp lnks" that only shows the option System Handler (which fails opening them if selected). Choosing Firefox is not possible as /bin and similar folders are out of range for the snap. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1956005/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1959995] Re: present: Crash in 'present_scmd_get_crtc' and 'present_flush' (NVIDIA 495.46)
I can confirm that this patch works. It fixed the crash on my computer. I'm running the Nvidia 510.47 drivers. ** Attachment added: "it works.png" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1959995/+attachment/5559655/+files/it%20works.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1959995 Title: present: Crash in 'present_scmd_get_crtc' and 'present_flush' (NVIDIA 495.46) Status in X.Org X server: Unknown Status in xorg-server package in Ubuntu: Triaged Bug description: This bug causes xserver to crash when using newer Nvidia drivers (NVIDIA 495.46+) with Optimus. It's apparently triggered when using the MATE desktop environment. It has been noticed on xorg-server-21.1, but it's likely affecting version 1.20.13 as well. It has been fixed already, but could you please backport the fix? Patch that fixes it is here: https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/841/diffs?commit_id=22d5818851967408bb7c903cb345b7ca8766094c The bug report at freedesktop.org is here: https://gitlab.freedesktop.org/xorg/xserver/-/issues/1275 Thank you! To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1959995/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1959015] Re: Switch to new HTTPS-capable domains for PPAs
This bug was fixed in the package software-properties - 0.99.18 --- software-properties (0.99.18) jammy; urgency=medium [ Colin Watson ] * Use new HTTPS-capable PPA domains (LP: #1959015). -- Brian Murray Mon, 07 Feb 2022 10:33:15 -0800 ** Changed in: software-properties (Ubuntu Jammy) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1959015 Title: Switch to new HTTPS-capable domains for PPAs Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Jammy: Fix Released Bug description: As described in bug 1473091, PPAs are now being served from new domains that aren't under launchpad.net and so can safely serve HTTPS without risk of compromising Launchpad session cookies. The old domains will keep working indefinitely, but nevertheless it would be good if we could arrange for add-apt-repository to use the new domains as of 22.04. The changes are: * http://ppa.launchpad.net/ → https://ppa.launchpadcontent.net/ (or http:// works too, but we should prefer https://) * https://private-ppa.launchpad.net/ → https://private-ppa.launchpadcontent.net/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1959015/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
