[Desktop-packages] [Bug 1898483] Re: [Inspiron 7591, Realtek ALC3254, Speaker, Internal] No sound at all despite the sound bars moving fine and device detected
@ Paramvir Could you try new kernel and update the information? Thanks ** Changed in: alsa-driver (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1898483 Title: [Inspiron 7591, Realtek ALC3254, Speaker, Internal] No sound at all despite the sound bars moving fine and device detected Status in alsa-driver package in Ubuntu: Incomplete Bug description: The volume bars in sound settings react to what sound is played correctly but I can't hear any sounds ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-49.53-generic 5.4.65 Uname: Linux 5.4.0-49-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: paramvir 1924 F pulseaudio /dev/snd/pcmC0D0p: paramvir 1924 F...m pulseaudio /dev/snd/pcmC0D6c: paramvir 1924 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Oct 5 02:22:25 2020 InstallationDate: Installed on 2020-04-26 (161 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed Symptom_Card: Cannon Lake PCH cAVS - sof-hda-dsp Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: paramvir 1924 F pulseaudio /dev/snd/pcmC0D0p: paramvir 1924 F...m pulseaudio /dev/snd/pcmC0D6c: paramvir 1924 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [Inspiron 7591, Realtek ALC3254, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.0 dmi.board.name: 0K1VDX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.0:bd07/22/2019:svnDellInc.:pnInspiron7591:pvr:rvnDellInc.:rn0K1VDX:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7591 dmi.product.sku: 0923 dmi.sys.vendor: Dell Inc. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-10-04T03:10:08.906233 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1898483/+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 2063397] [NEW] nautilus extract option causes date loss from rar archives
Public bug reported:
Extraction of rar files (v5) from the context menu ("Extract")
occasionally results in one or more subfolders silently being skipped.
This behavior is not systematic. Some rar archives extract properly,
other ones do not.
There is not any warning or error message when the problem manifests,
which make it likely that the problem goes overlooked. I have
effectively sustained data loss until I discovered that one of my
extracted folders was much smaller than it should have been.
I have unrar (non-free) and 7z installed.
Applications like file-roller and arqiver appear to function properly.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: nautilus 1:46.0-0ubuntu2
ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
Uname: Linux 6.8.0-31-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.28.1-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr 25 05:26:17 2024
InstallationDate: Installed on 2022-03-27 (759 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_nautilus:
eiciel0.10.0-1build2
file-roller 44.1-1
nautilus-extension-gnome-terminal 3.52.0-1ubuntu2
python3-nautilus 4.0-1build4
** Affects: nautilus (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug noble third-party-packages
--
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/2063397
Title:
nautilus extract option causes date loss from rar archives
Status in nautilus package in Ubuntu:
New
Bug description:
Extraction of rar files (v5) from the context menu ("Extract")
occasionally results in one or more subfolders silently being skipped.
This behavior is not systematic. Some rar archives extract properly,
other ones do not.
There is not any warning or error message when the problem manifests,
which make it likely that the problem goes overlooked. I have
effectively sustained data loss until I discovered that one of my
extracted folders was much smaller than it should have been.
I have unrar (non-free) and 7z installed.
Applications like file-roller and arqiver appear to function properly.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: nautilus 1:46.0-0ubuntu2
ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
Uname: Linux 6.8.0-31-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.28.1-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr 25 05:26:17 2024
InstallationDate: Installed on 2022-03-27 (759 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_nautilus:
eiciel0.10.0-1build2
file-roller 44.1-1
nautilus-extension-gnome-terminal 3.52.0-1ubuntu2
python3-nautilus 4.0-1build4
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2063397/+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 1532544] Re: Window becomes unresponsive and sound stops when skipping to next track
** Changed in: rhythmbox (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1532544 Title: Window becomes unresponsive and sound stops when skipping to next track Status in rhythmbox package in Ubuntu: Fix Released Bug description: When skipping to the next track rhythmbox will sometimes become unresponsive and rapidly send the error (rhythmbox:4897): GStreamer-CRITICAL **: gst_poll_write_control: assertion 'set != NULL' failed (rhythmbox:4897): GStreamer-WARNING **: gstsystemclock: write control failed in wakeup_async, trying again: 11:Resource temporarily unavailable to ~/.cache/upstart/indicator-sound.log which takes up most of the CPU and quickly fills all hard drive space. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: rhythmbox 3.2.1-1ubuntu3.1 ProcVersionSignature: Ubuntu 4.2.0-23.28-generic 4.2.6 Uname: Linux 4.2.0-23-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jan 10 23:04:18 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2015-07-26 (168 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: rhythmbox UpgradeStatus: Upgraded to wily on 2015-10-23 (79 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1532544/+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 1532185] Re: Rhythmbox sometimes crashes when skipping to next track
Does this still occur? I'm guessing not seen as this hasn't been touched in nearly a decade. ** Changed in: rhythmbox (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1532185 Title: Rhythmbox sometimes crashes when skipping to next track Status in rhythmbox package in Ubuntu: Incomplete Bug description: When hitting the next track key on my keyboard sometimes rhythmbox will crash ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: rhythmbox 3.2.1-1ubuntu3.1 ProcVersionSignature: Ubuntu 4.2.0-23.28-generic 4.2.6 Uname: Linux 4.2.0-23-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Fri Jan 8 23:11:33 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2015-07-26 (166 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: rhythmbox UpgradeStatus: Upgraded to wily on 2015-10-23 (77 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1532185/+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 1969999] Re: Looping music without no gui
*** This bug is a duplicate of bug 2063387 *** https://bugs.launchpad.net/bugs/2063387 ** This bug has been marked a duplicate of bug 2063387 No tray icon -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/196 Title: Looping music without no gui Status in rhythmbox package in Ubuntu: New Bug description: rhythmbox 3.4.2 loop music without no gui. OS Ubuntu 18.04 LTS. 5.4.0-109-generic #123~18.04.1-Ubuntu SMP Fri Apr 8 09:48:52 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux rhytmbox version is 3.4.4 When you click playlist. Play song. Close the program in window x button. (From the x button right at the top. It's kill ui, but not stop music. Now is is looping your playlist. There is no icon for unhide the program. When you open program again and press play. You have seconds song playing. But you cannot stop first one. You can only kill app for find top command rhythmbox id, but i cannot find task manager any rhythmbox apps. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/196/+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 2063387] Re: No tray icon
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: rhythmbox (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/2063387 Title: No tray icon Status in rhythmbox package in Ubuntu: Confirmed Bug description: When I minimise Rhythmbox it disappears. There's no tray icon and I can see no way to bring it back. It continues playing music but I cannot control it any way. I have to kill the process. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: rhythmbox 3.4.4-5ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-28.29~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: MATE Date: Thu Apr 25 03:46:54 2024 SourcePackage: rhythmbox UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2019-08-06T11:56:22.315382 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/2063387/+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 2063387] [NEW] No tray icon
Public bug reported: When I minimise Rhythmbox it disappears. There's no tray icon and I can see no way to bring it back. It continues playing music but I cannot control it any way. I have to kill the process. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: rhythmbox 3.4.4-5ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-28.29~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: MATE Date: Thu Apr 25 03:46:54 2024 SourcePackage: rhythmbox UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2019-08-06T11:56:22.315382 ** Affects: rhythmbox (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug jammy third-party-packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/2063387 Title: No tray icon Status in rhythmbox package in Ubuntu: Confirmed Bug description: When I minimise Rhythmbox it disappears. There's no tray icon and I can see no way to bring it back. It continues playing music but I cannot control it any way. I have to kill the process. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: rhythmbox 3.4.4-5ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-28.29~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: MATE Date: Thu Apr 25 03:46:54 2024 SourcePackage: rhythmbox UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2019-08-06T11:56:22.315382 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/2063387/+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 2063049] Re: Google Chrome and Chromium 124 have a transparent window on Wayland
Tracking upstream in:
https://issues.chromium.org/issues/329678163
** Summary changed:
- chromium snap doesnt launch properly on 24.04
+ Google Chrome and Chromium 124 have a transparent window on Wayland
** Bug watch added: issues.chromium.org/issues #329678163
https://issues.chromium.org/issues/329678163
** Also affects: chromium-browser via
https://issues.chromium.org/issues/329678163
Importance: Unknown
Status: Unknown
** Tags added: jammy
** Changed in: chromium-browser (Ubuntu)
Importance: Undecided => Critical
** Changed in: chromium-browser (Ubuntu)
Status: Confirmed => Triaged
--
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/2063049
Title:
Google Chrome and Chromium 124 have a transparent window on Wayland
Status in Chromium Browser:
Unknown
Status in chromium-browser package in Ubuntu:
Triaged
Bug description:
chromium snap only launches with titlebar and transparent window after
recent snap update on wayland and intel grafics.
Adding --ozone-platform=wayland fixes the issue for me. (workaround
from bug #1968610)
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: chromium-browser 2:1snap1-0ubuntu2
ProcVersionSignature: Ubuntu 6.8.0-28.28-generic 6.8.1
Uname: Linux 6.8.0-28-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.28.1-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: sway
Date: Sun Apr 21 20:25:30 2024
DiskUsage:
FilesystemType Size Used Avail Use% Mounted on
rpool/ROOT/ubuntu_gk6kaa zfs 50G 7,7G 42G 16% /
tmpfs tmpfs 16G 128M 16G 1% /dev/shm
rpool/USERDATA/k1l_0tberh zfs437G 396G 42G 91% /home/k1l
InstallationDate: Installed on 2022-03-24 (760 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220321)
ProcEnviron:
LANG=de_DE.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
Snap.Changes:
ID Status Spawn Ready Summary
635 Done2024-04-21T00:51:33+02:00 2024-04-21T00:52:11+02:00 Snap
"chromium" aktualisieren
Snap.ChromeDriverVersion: ChromeDriver 124.0.6367.60
(8771130bd84f76d855ae42fbe02752b03e352f17-refs/branch-heads/6367@{#798})
Snap.ChromiumVersion: Chromium 124.0.6367.60 snap
SourcePackage: chromium-browser
UpgradeStatus: Upgraded to noble on 2024-03-25 (27 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/chromium-browser/+bug/2063049/+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 2063304] Re: chromium 124.0.6367.60 fails to draw its window
*** This bug is a duplicate of bug 2063049 ***
https://bugs.launchpad.net/bugs/2063049
** This bug has been marked a duplicate of bug 2063049
Google Chrome and Chromium 124 have a transparent window on Wayland
--
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/2063304
Title:
chromium 124.0.6367.60 fails to draw its window
Status in chromium-browser package in Ubuntu:
Confirmed
Bug description:
Since the last snap update to 124.0.6367.60, I cannot use chromium.
It launches fine, but the window itself is fully transparent (e.g.
triggering the Overview makes it look like a piece of my wallpaper).
I have Intel graphics and use a Wayland session on Ubuntu 23.10.
At first I thought I was experiencing bug 1967488, but the more I looked at
it, the less sure I was (no Nvidia here, no issues with older snap versions, no
KMS errors in journalctl), so I'm filing a new one.
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/nvme0n1p5 ext4 732G 483G 212G 70% /
tmpfs tmpfs 7,7G 75M 7,6G 1% /dev/shm
/dev/nvme0n1p5 ext4 732G 483G 212G 70% /
DistroRelease: Ubuntu 23.10
EcryptfsInUse: Yes
InstallationDate: Installed on 2019-06-12 (1777 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
Package: chromium-browser 1:85.0.4183.83-0ubuntu3
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 6.5.0-28.29-generic 6.5.13
Snap.Changes:
ID Status Spawn Ready Summary
824 Done2024-04-23T20:13:38+03:00 2024-04-23T20:28:35+03:00
Auto-refresh snap "chromium"
Snap.ChromeDriverVersion: ChromeDriver 124.0.6367.60
(8771130bd84f76d855ae42fbe02752b03e352f17-refs/branch-heads/6367@{#798})
Snap.ChromiumVersion: Chromium 124.0.6367.60 snap
Tags: mantic wayland-session
Uname: Linux 6.5.0-28-generic x86_64
UpgradeStatus: Upgraded to mantic on 2023-10-13 (194 days ago)
UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2063304/+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 2063336] Re: All Chromium based applications fail to render on Wayland
*** This bug is a duplicate of bug 2063049 *** https://bugs.launchpad.net/bugs/2063049 Since this isn't the first report of the problem, and is also confused by separate Nvidia issues, let's use bug 2063049 instead. ** Changed in: chromium-browser (Ubuntu) Milestone: ubuntu-24.04 => None ** This bug has been marked a duplicate of bug 2063049 Google Chrome and Chromium 124 have a transparent window on Wayland -- 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/2063336 Title: All Chromium based applications fail to render on Wayland Status in Chromium Browser: Unknown Status in chromium-browser package in Ubuntu: Confirmed Bug description: Most of the time (3/4 desktop sessions attempted) all Chromium based applications I have tested (Chromium, VS Code, Mattermost) fail to render themselves, on actual display panel presenting random garbage, and when screenshotted, showing supposedly transparent pixels. I have also recorded an example video I can share in case this is of use (attached the screenshot with the video). ProblemType: Bug DistroRelease: Ubuntu 24.04 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: zfs nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 24 16:21:15 2024 InstallationDate: Installed on 2021-11-08 (898 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Snap: chromium 124.0.6367.60 (latest/stable) SnapChanges: no changes found SnapSource: ubuntu/+source/chromium-browser UpgradeStatus: Upgraded to noble on 2024-04-24 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/2063336/+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 2063341] Re: gnome-shell crashed with SIGSEGV
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Run these commands: journalctl -b0 > journal.txt journalctl -b-1 > prevjournal.txt and attach the resulting text files here. 2. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 3. If step 2 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Summary changed: - Ubuntu crashesh after KVM swicth back/wake up/suspend + gnome-shell crashed with SIGSEGV ** 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/2063341 Title: gnome-shell crashed with SIGSEGV Status in gnome-shell package in Ubuntu: Incomplete Bug description: I've been using Ubuntu for almost 2 years and it's been working fine. I use a KVM switch (built in Benq monitor) all the time. Since last month Ubuntu randomly crashes when I switch back to it. Or it could be wake up/suspend, I can't see when it exactly happens, it's just logging screen after crash. I am running: openVPN, firefox (dozen tabs), chrome (ms teams), slack, postman, 3x Intellij IDEA, VS Code System logs don't show anything meaningful to me or Google and I don't know how to get a clue as to what's going on. I suspect a new version of MS Teams that was introduced a few weeks ago. Please help me I cannot reproduce the crash or find anything on the web about it. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.9-0ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-28.29~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 24 15:59:03 2024 DisplayManager: gdm3 InstallationDate: Installed on 2022-08-31 (601 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) RelatedPackageVersions: mutter-common 42.9-0ubuntu7 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2063341/+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 2063383] Re: [SRU] Ubuntu Unity takes 90 seconds to log out
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/2063383 ** Tags added: iso-testing -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/2063383 Title: [SRU] Ubuntu Unity takes 90 seconds to log out Status in gnome-session package in Ubuntu: Confirmed Status in gnome-session source package in Noble: Confirmed Bug description: [ Impact ] Ubuntu Unity reliably takes 90 seconds to log out. This is due to the user-level gnome-session.service systemd unit not properly terminating gnome-session on logout. An attempt is made to send SIGTERM to the process, which gnome-session does not care about. Instead, gnome-session-quit should be invoked when the systemd unit shuts down, which acts effectively and immediately. [ Test Plan ] Actual behavior: 1. Log in to a Unity session on Ubuntu Unity 24.04. 2. Log out of Ubuntu Unity. 3. Observe that only the wallpaper is shown for 90 seconds prior to the login manager showing again. Expected behavior: 1. Log in to a Unity session on Ubuntu Unity 24.04. 2. Log out of Ubuntu Unity. 3. Observe that logging out takes a few seconds at most, and you are able to log back in as the same user, or a different one. [ Where problems could occur ] If the gnome-session or gnome-session-quit binaries change the arguments they accept by default, log in and log out functionality on Unity sessions are likely to break. Additionally, if lightdm or systemd changes in a non-reverse- compatible way, this increases the chance of a user-facing regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/2063383/+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 2037015] Re: Screen corruption of webkit2gtk apps in X11 on Raspberry Pi, such as during install
** Changed in: webkit2gtk (Ubuntu) Milestone: ubuntu-24.04 => noble-updates -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to webkit2gtk in Ubuntu. https://bugs.launchpad.net/bugs/2037015 Title: Screen corruption of webkit2gtk apps in X11 on Raspberry Pi, such as during install Status in Webkit: Confirmed Status in mesa package in Ubuntu: Confirmed Status in webkit2gtk package in Ubuntu: In Progress Bug description: [ Impact ] Screen corruption of webkit2gtk apps in X11 on Raspberry Pi, such as during install. [ Test Plan ] 1. Log into a Xorg session on a Raspberry Pi 4/400. 2. Open the default Help app by clicking the question mark icon in the dock or by running 'yelp'. 3. Verify it didn't crash and the window contents are not corrupt. [ Where problems could occur ] The fix is limited to webkit2gtk so can only affect apps such as yelp or the Raspberry Pi installer. [ Other Info ] During the initial configuration of the Ubuntu Desktop for Raspberry Pi (the oem-config process, derived from ubiquity), on the Mantic beta images, after the various pages of information have been filled out and the process moves onto configuration, the "slide deck" that is usually displayed during the process appeared corrupted as if a horizontal stride were incorrectly set somewhere. I'm attached a photo of the screen (as, while I could take a screenshot during the process, it evidently wasn't saved somewhere persistent). I originally thought this might be a regression of LP: #1924251 as the corruption in the window looks very similar (incorrect horizontal stride causing "banding"), but I tested the embedded browser (via the help system) after completing setup and it worked perfectly so that's *probably* unrelated. To manage notifications about this bug go to: https://bugs.launchpad.net/webkit/+bug/2037015/+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 2063383] [NEW] [SRU] Ubuntu Unity takes 90 seconds to log out
Public bug reported: [ Impact ] Ubuntu Unity reliably takes 90 seconds to log out. This is due to the user-level gnome-session.service systemd unit not properly terminating gnome-session on logout. An attempt is made to send SIGTERM to the process, which gnome-session does not care about. Instead, gnome-session-quit should be invoked when the systemd unit shuts down, which acts effectively and immediately. [ Test Plan ] Actual behavior: 1. Log in to a Unity session on Ubuntu Unity 24.04. 2. Log out of Ubuntu Unity. 3. Observe that only the wallpaper is shown for 90 seconds prior to the login manager showing again. Expected behavior: 1. Log in to a Unity session on Ubuntu Unity 24.04. 2. Log out of Ubuntu Unity. 3. Observe that logging out takes a few seconds at most, and you are able to log back in as the same user, or a different one. [ Where problems could occur ] If the gnome-session or gnome-session-quit binaries change the arguments they accept by default, log in and log out functionality on Unity sessions are likely to break. Additionally, if lightdm or systemd changes in a non-reverse-compatible way, this increases the chance of a user-facing regression. ** Affects: gnome-session (Ubuntu) Importance: High Assignee: Simon Quigley (tsimonq2) Status: Confirmed ** Affects: gnome-session (Ubuntu Noble) Importance: High Assignee: Simon Quigley (tsimonq2) Status: Confirmed ** Summary changed: - Ubuntu Unity takes 90 seconds to log out + [SRU] Ubuntu Unity takes 90 seconds to log out ** Changed in: gnome-session (Ubuntu) Status: New => Confirmed ** Changed in: gnome-session (Ubuntu) Importance: Undecided => High ** Changed in: gnome-session (Ubuntu) Assignee: (unassigned) => Simon Quigley (tsimonq2) ** Also affects: gnome-session (Ubuntu Noble) Importance: High Assignee: Simon Quigley (tsimonq2) Status: Confirmed ** Changed in: gnome-session (Ubuntu Noble) Milestone: None => noble-updates -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/2063383 Title: [SRU] Ubuntu Unity takes 90 seconds to log out Status in gnome-session package in Ubuntu: Confirmed Status in gnome-session source package in Noble: Confirmed Bug description: [ Impact ] Ubuntu Unity reliably takes 90 seconds to log out. This is due to the user-level gnome-session.service systemd unit not properly terminating gnome-session on logout. An attempt is made to send SIGTERM to the process, which gnome-session does not care about. Instead, gnome-session-quit should be invoked when the systemd unit shuts down, which acts effectively and immediately. [ Test Plan ] Actual behavior: 1. Log in to a Unity session on Ubuntu Unity 24.04. 2. Log out of Ubuntu Unity. 3. Observe that only the wallpaper is shown for 90 seconds prior to the login manager showing again. Expected behavior: 1. Log in to a Unity session on Ubuntu Unity 24.04. 2. Log out of Ubuntu Unity. 3. Observe that logging out takes a few seconds at most, and you are able to log back in as the same user, or a different one. [ Where problems could occur ] If the gnome-session or gnome-session-quit binaries change the arguments they accept by default, log in and log out functionality on Unity sessions are likely to break. Additionally, if lightdm or systemd changes in a non-reverse- compatible way, this increases the chance of a user-facing regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/2063383/+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 2037015] Re: Screen corruption of webkit2gtk apps in X11 on Raspberry Pi, such as during install
This is one of those first-touch experience items that, since this is Edubuntu's first foray into the Raspberry Pi experience, I'd rather get right the first time. Unfortunately, the corruption on the slideshow is sub-par and looks amateurish for us. So no, this needs to be reprioritized. ** Changed in: webkit2gtk (Ubuntu) Milestone: noble-updates => ubuntu-24.04 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to webkit2gtk in Ubuntu. https://bugs.launchpad.net/bugs/2037015 Title: Screen corruption of webkit2gtk apps in X11 on Raspberry Pi, such as during install Status in Webkit: Confirmed Status in mesa package in Ubuntu: Confirmed Status in webkit2gtk package in Ubuntu: In Progress Bug description: [ Impact ] Screen corruption of webkit2gtk apps in X11 on Raspberry Pi, such as during install. [ Test Plan ] 1. Log into a Xorg session on a Raspberry Pi 4/400. 2. Open the default Help app by clicking the question mark icon in the dock or by running 'yelp'. 3. Verify it didn't crash and the window contents are not corrupt. [ Where problems could occur ] The fix is limited to webkit2gtk so can only affect apps such as yelp or the Raspberry Pi installer. [ Other Info ] During the initial configuration of the Ubuntu Desktop for Raspberry Pi (the oem-config process, derived from ubiquity), on the Mantic beta images, after the various pages of information have been filled out and the process moves onto configuration, the "slide deck" that is usually displayed during the process appeared corrupted as if a horizontal stride were incorrectly set somewhere. I'm attached a photo of the screen (as, while I could take a screenshot during the process, it evidently wasn't saved somewhere persistent). I originally thought this might be a regression of LP: #1924251 as the corruption in the window looks very similar (incorrect horizontal stride causing "banding"), but I tested the embedded browser (via the help system) after completing setup and it worked perfectly so that's *probably* unrelated. To manage notifications about this bug go to: https://bugs.launchpad.net/webkit/+bug/2037015/+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 2059847] Re: Input lag or freezes on Nvidia desktops with X11 after logging "MetaSyncRing: Sync object is not ready -- were events handled properly?"
I have been experiencing this problem since I updated on 4/22, been away. After the update gnome-term is very slow to echo. Dpkg: ||/ Name Version Architecture Description +++--=--===> ii libmutter-10-0:amd64 42.9-0ubuntu7 amd64window manager library from> in libmutter-14-0 amd64(no description available) Distributor ID: Ubuntu Description:Ubuntu 22.04.4 LTS Release:22.04 Codename: jammy Nvidia version 535.171.04 The PPA referred to in previous posts as a potential fix seems to have done the trick. Thanks. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2059847 Title: Input lag or freezes on Nvidia desktops with X11 after logging "MetaSyncRing: Sync object is not ready -- were events handled properly?" Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Jammy: In Progress Status in mutter source package in Mantic: In Progress Status in mutter source package in Noble: Fix Released Bug description: [ Impact ] Input or the entire screen may freeze at times on systems using the Nvidia Xorg driver with GNOME. [ Test Plan ] 0. Set up a desktop with Nvidia driver 545 or 550. 1. Log into Ubuntu, ensuring it's a Xorg session. 2. Open a Terminal, resize it vigorously, and type several lines of text. 3. Run: journalctl -b0 | grep MetaSyncRing 4. Verify the above command does NOT show "MetaSyncRing" messages such as: Window manager warning: MetaSyncRing: Sync object is not ready -- were events handled properly? Window manager warning: MetaSyncRing: Sync object is not ready -- were events handled properly? Window manager warning: MetaSyncRing: Sync object is not ready -- were events handled properly? Window manager warning: MetaSyncRing: Too many reboots -- disabling [ Where problems could occur ] Anywhere in Nvidia (proprietary driver) Xorg sessions since the code being modified is only used with that driver. [ Original Description ] There is a noticeable delay in input while using the native terminal. I belive it was caused by a recent software update, as this issue is relatively new. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia wl ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Mar 30 19:57:13 2024 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- InstallationDate: Installed on 2024-03-30 (0 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220) SourcePackage: ubiquity Symptom: installation UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2059847/+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 2063304] Re: chromium 124.0.6367.60 fails to draw its window
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: chromium-browser (Ubuntu)
Status: New => Confirmed
--
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/2063304
Title:
chromium 124.0.6367.60 fails to draw its window
Status in chromium-browser package in Ubuntu:
Confirmed
Bug description:
Since the last snap update to 124.0.6367.60, I cannot use chromium.
It launches fine, but the window itself is fully transparent (e.g.
triggering the Overview makes it look like a piece of my wallpaper).
I have Intel graphics and use a Wayland session on Ubuntu 23.10.
At first I thought I was experiencing bug 1967488, but the more I looked at
it, the less sure I was (no Nvidia here, no issues with older snap versions, no
KMS errors in journalctl), so I'm filing a new one.
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/nvme0n1p5 ext4 732G 483G 212G 70% /
tmpfs tmpfs 7,7G 75M 7,6G 1% /dev/shm
/dev/nvme0n1p5 ext4 732G 483G 212G 70% /
DistroRelease: Ubuntu 23.10
EcryptfsInUse: Yes
InstallationDate: Installed on 2019-06-12 (1777 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
Package: chromium-browser 1:85.0.4183.83-0ubuntu3
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 6.5.0-28.29-generic 6.5.13
Snap.Changes:
ID Status Spawn Ready Summary
824 Done2024-04-23T20:13:38+03:00 2024-04-23T20:28:35+03:00
Auto-refresh snap "chromium"
Snap.ChromeDriverVersion: ChromeDriver 124.0.6367.60
(8771130bd84f76d855ae42fbe02752b03e352f17-refs/branch-heads/6367@{#798})
Snap.ChromiumVersion: Chromium 124.0.6367.60 snap
Tags: mantic wayland-session
Uname: Linux 6.5.0-28-generic x86_64
UpgradeStatus: Upgraded to mantic on 2023-10-13 (194 days ago)
UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2063304/+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 2062667] Re: Fails on (and should be removed from) raspi desktop
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/2062667 ** Tags added: iso-testing -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2062667 Title: Fails on (and should be removed from) raspi desktop Status in protection-domain-mapper package in Ubuntu: Confirmed Status in qrtr package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: The protection-domain-mapper package (and qrtr-tools) are both installed by default on the Ubuntu Desktop for Raspberry Pi images, thanks to their inclusion in the desktop-minimal seed for arm64. However, there's no hardware that they target on these platforms, and the result is a permanently failed service (pd-mapper.service). It appears these were added to support the X13s laptop [1]. I've attempted to work around the issue by excluding these packages in the desktop-raspi seed (experimentally in my no-pd-mapper branch [2]) but this does not work (the packages still appear in the built images). Ideally, these packages should be moved into a hardware-specific seed for the X13s (and/or whatever other laptops need these things). Alternatively, at a bare minimum, the package should have some conditional that causes the service not to attempt to start when it's not on Qualcomm hardware. [1]: https://git.launchpad.net/~ubuntu-core-dev/ubuntu- seeds/+git/ubuntu/commit/desktop- minimal?id=afe820cd49514896e96d02303298ed873d8d7f8a [2]: https://git.launchpad.net/~waveform/ubuntu- seeds/+git/ubuntu/commit/?id=875bddac19675f7e971f56d9c5d39a9912dc6e38 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/protection-domain-mapper/+bug/2062667/+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 2062667] Re: Fails on (and should be removed from) raspi desktop
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-meta (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2062667 Title: Fails on (and should be removed from) raspi desktop Status in protection-domain-mapper package in Ubuntu: Confirmed Status in qrtr package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: The protection-domain-mapper package (and qrtr-tools) are both installed by default on the Ubuntu Desktop for Raspberry Pi images, thanks to their inclusion in the desktop-minimal seed for arm64. However, there's no hardware that they target on these platforms, and the result is a permanently failed service (pd-mapper.service). It appears these were added to support the X13s laptop [1]. I've attempted to work around the issue by excluding these packages in the desktop-raspi seed (experimentally in my no-pd-mapper branch [2]) but this does not work (the packages still appear in the built images). Ideally, these packages should be moved into a hardware-specific seed for the X13s (and/or whatever other laptops need these things). Alternatively, at a bare minimum, the package should have some conditional that causes the service not to attempt to start when it's not on Qualcomm hardware. [1]: https://git.launchpad.net/~ubuntu-core-dev/ubuntu- seeds/+git/ubuntu/commit/desktop- minimal?id=afe820cd49514896e96d02303298ed873d8d7f8a [2]: https://git.launchpad.net/~waveform/ubuntu- seeds/+git/ubuntu/commit/?id=875bddac19675f7e971f56d9c5d39a9912dc6e38 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/protection-domain-mapper/+bug/2062667/+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 2062667] Re: Fails on (and should be removed from) raspi desktop
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: qrtr (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2062667 Title: Fails on (and should be removed from) raspi desktop Status in protection-domain-mapper package in Ubuntu: Confirmed Status in qrtr package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: The protection-domain-mapper package (and qrtr-tools) are both installed by default on the Ubuntu Desktop for Raspberry Pi images, thanks to their inclusion in the desktop-minimal seed for arm64. However, there's no hardware that they target on these platforms, and the result is a permanently failed service (pd-mapper.service). It appears these were added to support the X13s laptop [1]. I've attempted to work around the issue by excluding these packages in the desktop-raspi seed (experimentally in my no-pd-mapper branch [2]) but this does not work (the packages still appear in the built images). Ideally, these packages should be moved into a hardware-specific seed for the X13s (and/or whatever other laptops need these things). Alternatively, at a bare minimum, the package should have some conditional that causes the service not to attempt to start when it's not on Qualcomm hardware. [1]: https://git.launchpad.net/~ubuntu-core-dev/ubuntu- seeds/+git/ubuntu/commit/desktop- minimal?id=afe820cd49514896e96d02303298ed873d8d7f8a [2]: https://git.launchpad.net/~waveform/ubuntu- seeds/+git/ubuntu/commit/?id=875bddac19675f7e971f56d9c5d39a9912dc6e38 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/protection-domain-mapper/+bug/2062667/+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 2062667] Re: Fails on (and should be removed from) raspi desktop
** Also affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2062667 Title: Fails on (and should be removed from) raspi desktop Status in protection-domain-mapper package in Ubuntu: Confirmed Status in qrtr package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: The protection-domain-mapper package (and qrtr-tools) are both installed by default on the Ubuntu Desktop for Raspberry Pi images, thanks to their inclusion in the desktop-minimal seed for arm64. However, there's no hardware that they target on these platforms, and the result is a permanently failed service (pd-mapper.service). It appears these were added to support the X13s laptop [1]. I've attempted to work around the issue by excluding these packages in the desktop-raspi seed (experimentally in my no-pd-mapper branch [2]) but this does not work (the packages still appear in the built images). Ideally, these packages should be moved into a hardware-specific seed for the X13s (and/or whatever other laptops need these things). Alternatively, at a bare minimum, the package should have some conditional that causes the service not to attempt to start when it's not on Qualcomm hardware. [1]: https://git.launchpad.net/~ubuntu-core-dev/ubuntu- seeds/+git/ubuntu/commit/desktop- minimal?id=afe820cd49514896e96d02303298ed873d8d7f8a [2]: https://git.launchpad.net/~waveform/ubuntu- seeds/+git/ubuntu/commit/?id=875bddac19675f7e971f56d9c5d39a9912dc6e38 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/protection-domain-mapper/+bug/2062667/+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 2062667] Re: Fails on (and should be removed from) raspi desktop
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: protection-domain-mapper (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2062667 Title: Fails on (and should be removed from) raspi desktop Status in protection-domain-mapper package in Ubuntu: Confirmed Status in qrtr package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: The protection-domain-mapper package (and qrtr-tools) are both installed by default on the Ubuntu Desktop for Raspberry Pi images, thanks to their inclusion in the desktop-minimal seed for arm64. However, there's no hardware that they target on these platforms, and the result is a permanently failed service (pd-mapper.service). It appears these were added to support the X13s laptop [1]. I've attempted to work around the issue by excluding these packages in the desktop-raspi seed (experimentally in my no-pd-mapper branch [2]) but this does not work (the packages still appear in the built images). Ideally, these packages should be moved into a hardware-specific seed for the X13s (and/or whatever other laptops need these things). Alternatively, at a bare minimum, the package should have some conditional that causes the service not to attempt to start when it's not on Qualcomm hardware. [1]: https://git.launchpad.net/~ubuntu-core-dev/ubuntu- seeds/+git/ubuntu/commit/desktop- minimal?id=afe820cd49514896e96d02303298ed873d8d7f8a [2]: https://git.launchpad.net/~waveform/ubuntu- seeds/+git/ubuntu/commit/?id=875bddac19675f7e971f56d9c5d39a9912dc6e38 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/protection-domain-mapper/+bug/2062667/+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 2063371] Re: protection-domain-mapper and qrtr-tools should not be in ubuntu-desktop-raspi
*** This bug is a duplicate of bug 2062667 *** https://bugs.launchpad.net/bugs/2062667 ** This bug has been marked a duplicate of bug 2062667 Fails on (and should be removed from) raspi desktop -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2063371 Title: protection-domain-mapper and qrtr-tools should not be in ubuntu- desktop-raspi Status in ubuntu-meta package in Ubuntu: New Bug description: I noticed from our automated certification tests on raspberry pi Noble desktop images that the pd-mapper service was failing on boot. It looks like this is a package only intended for qualcomm desktop system, and not something that is needed by raspberry pi. It looks like this got added with https://code.launchpad.net/~xnox/ubuntu- seeds/+git/ubuntu/+merge/453233 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2063371/+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 2063371] [NEW] protection-domain-mapper and qrtr-tools should not be in ubuntu-desktop-raspi
Public bug reported: I noticed from our automated certification tests on raspberry pi Noble desktop images that the pd-mapper service was failing on boot. It looks like this is a package only intended for qualcomm desktop system, and not something that is needed by raspberry pi. It looks like this got added with https://code.launchpad.net/~xnox/ubuntu-seeds/+git/ubuntu/+merge/453233 ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2063371 Title: protection-domain-mapper and qrtr-tools should not be in ubuntu- desktop-raspi Status in ubuntu-meta package in Ubuntu: New Bug description: I noticed from our automated certification tests on raspberry pi Noble desktop images that the pd-mapper service was failing on boot. It looks like this is a package only intended for qualcomm desktop system, and not something that is needed by raspberry pi. It looks like this got added with https://code.launchpad.net/~xnox/ubuntu- seeds/+git/ubuntu/+merge/453233 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2063371/+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 2061882] Re: Thunderbird snap loses local folder settings in 24.04
I did not try that, and I can no longer reproduce it. I have 7 or 8 other machines that need to be eventually upgraded, I will try on one of those but this can be quite a few months and I am very weary of this release. It did try to import things so it was a partial success. My .thunderbird folder was symlinked maybe it has something to do with the issue. I have a SSD/spindle scenario, and symlink to the spindle for bulky things. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/2061882 Title: Thunderbird snap loses local folder settings in 24.04 Status in thunderbird package in Ubuntu: Invalid Bug description: After Thunderbird snap installs the local folders do not import from the deb Thunderbird. There also seems to be no way to get back to the deb version. I needed to manually move the local directory back to the original. I can no longer see my inbox and it keeps telling me that the /home/me/snap/thunderbird/hdd/home/me/.thunderbird/24a1u6qp.default/ImapMail/ is invalid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/2061882/+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 2063143] Re: Frequent boot to black display
** Bug watch added: github.com/sddm/sddm/issues #1917 https://github.com/sddm/sddm/issues/1917 ** Also affects: sddm via https://github.com/sddm/sddm/issues/1917 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to plymouth in Ubuntu. https://bugs.launchpad.net/bugs/2063143 Title: Frequent boot to black display Status in Linux: New Status in Plymouth: Unknown Status in SDDM: Unknown Status in linux package in Ubuntu: Incomplete Status in plymouth package in Ubuntu: New Status in sddm package in Ubuntu: New Bug description: Hardware: AMD Framework 13 OS: Ubuntu Noble 24.04 DE: Plasma Wayland BIOS: version 3.03 and 3.05 (latest new release) Kernel: 6.8.0-31-generic #31-Ubuntu SMP PREEMPT_DYNAMIC Sat Apr 20 00:40:06 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux This issue started about 2-3 weeks ago I believe around the time that Ubuntu updated Noble to linux kernel 6.8 and linux firmware packages. This issue may not be a kernel regression but instead a wayland regression but I am not certain and looking for help. The issue is that on boot the (internal laptop and external displays if connected) are black but backlight is lit. I am able to boot into recovery mode without issue since the graphics drivers are not loaded in that case (only amd framebuffer driver and userspace mesa llvmpipe). Cold boot from OFF seems to be the most common case for this issue and it happens about 50-75% of the time from there. I have to force power the device off and try again in this case. I don't know how to get proper bootlogs from the previous boot when this is the case since /var/log only seems to contain logs from the current boot. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu3 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: KDE Date: Mon Apr 22 13:35:21 2024 DistUpgraded: Fresh install DistroCodename: noble DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Since a couple weeks or more GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Phoenix1 [1002:15bf] (rev cb) (prog-if 00 [VGA controller]) Subsystem: Framework Computer Inc. Phoenix1 [f111:0006] InstallationDate: Installed on 2023-11-16 (159 days ago) InstallationMedia: Kubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231010) MachineType: Framework Laptop 13 (AMD Ryzen 7040Series) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic root=UUID=8484eee5-4c87-4cb9-9f40-5f1c9a24db18 ro rtc_cmos.use_acpi_alarm=1 quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/17/2023 dmi.bios.release: 3.3 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 03.03 dmi.board.asset.tag: * dmi.board.name: FRANMDCP05 dmi.board.vendor: Framework dmi.board.version: A5 dmi.chassis.asset.tag: FRANDGCPA5342400SJ dmi.chassis.type: 10 dmi.chassis.vendor: Framework dmi.chassis.version: A5 dmi.modalias: dmi:bvnINSYDECorp.:bvr03.03:bd10/17/2023:br3.3:svnFramework:pnLaptop13(AMDRyzen7040Series):pvrA5:rvnFramework:rnFRANMDCP05:rvrA5:cvnFramework:ct10:cvrA5:skuFRANDGCP05: dmi.product.family: Laptop dmi.product.name: Laptop 13 (AMD Ryzen 7040Series) dmi.product.sku: FRANDGCP05 dmi.product.version: A5 dmi.sys.vendor: Framework version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.120-2build1 version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2063143/+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 2063143] Re: Frequent boot to black display
AMD kernel developer wants to classify this is as both SDDM bug and plymouth bug https://gitlab.freedesktop.org/drm/amd/-/issues/3341. amdgpu kernel driver is not ready by the time that sddm and plymouth are started in some cases (race condition). Marking this as a sddm and plymouth bug (in addition to linux) because of this. To me it seems that at least a systemd service should be handling blocking starting GUI userspace services until the kernel drivers are actually loaded but that is just my thought. I guess the AMD developer sees this the same way you do Daniel. ** Also affects: sddm (Ubuntu) Importance: Undecided Status: New ** Also affects: plymouth (Ubuntu) Importance: Undecided Status: New ** No longer affects: plymouth (Ubuntu) ** Also affects: plymouth (Ubuntu) Importance: Undecided Status: New ** Bug watch added: gitlab.freedesktop.org/plymouth/plymouth/-/issues #253 https://gitlab.freedesktop.org/plymouth/plymouth/-/issues/253 ** Also affects: plymouth via https://gitlab.freedesktop.org/plymouth/plymouth/-/issues/253 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to plymouth in Ubuntu. https://bugs.launchpad.net/bugs/2063143 Title: Frequent boot to black display Status in Linux: New Status in Plymouth: Unknown Status in SDDM: Unknown Status in linux package in Ubuntu: Incomplete Status in plymouth package in Ubuntu: New Status in sddm package in Ubuntu: New Bug description: Hardware: AMD Framework 13 OS: Ubuntu Noble 24.04 DE: Plasma Wayland BIOS: version 3.03 and 3.05 (latest new release) Kernel: 6.8.0-31-generic #31-Ubuntu SMP PREEMPT_DYNAMIC Sat Apr 20 00:40:06 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux This issue started about 2-3 weeks ago I believe around the time that Ubuntu updated Noble to linux kernel 6.8 and linux firmware packages. This issue may not be a kernel regression but instead a wayland regression but I am not certain and looking for help. The issue is that on boot the (internal laptop and external displays if connected) are black but backlight is lit. I am able to boot into recovery mode without issue since the graphics drivers are not loaded in that case (only amd framebuffer driver and userspace mesa llvmpipe). Cold boot from OFF seems to be the most common case for this issue and it happens about 50-75% of the time from there. I have to force power the device off and try again in this case. I don't know how to get proper bootlogs from the previous boot when this is the case since /var/log only seems to contain logs from the current boot. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu3 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: KDE Date: Mon Apr 22 13:35:21 2024 DistUpgraded: Fresh install DistroCodename: noble DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Since a couple weeks or more GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Phoenix1 [1002:15bf] (rev cb) (prog-if 00 [VGA controller]) Subsystem: Framework Computer Inc. Phoenix1 [f111:0006] InstallationDate: Installed on 2023-11-16 (159 days ago) InstallationMedia: Kubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231010) MachineType: Framework Laptop 13 (AMD Ryzen 7040Series) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic root=UUID=8484eee5-4c87-4cb9-9f40-5f1c9a24db18 ro rtc_cmos.use_acpi_alarm=1 quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/17/2023 dmi.bios.release: 3.3 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 03.03 dmi.board.asset.tag: * dmi.board.name: FRANMDCP05 dmi.board.vendor: Framework dmi.board.version: A5 dmi.chassis.asset.tag: FRANDGCPA5342400SJ dmi.chassis.type: 10 dmi.chassis.vendor: Framework dmi.chassis.version: A5 dmi.modalias: dmi:bvnINSYDECorp.:bvr03.03:bd10/17/2023:br3.3:svnFramework:pnLaptop13(AMDRyzen7040Series):pvrA5:rvnFramework:rnFRANMDCP05:rvrA5:cvnFramework:ct10:cvrA5:skuFRANDGCP05: dmi.product.family: Laptop dmi.product.name: Laptop 13 (AMD Ryzen 7040Series) dmi.product.sku: FRANDGCP05 dmi.product.version: A5 dmi.sys.vendor: Framework version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.120-2build1 version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1
[Desktop-packages] [Bug 2061882] Re: Thunderbird snap loses local folder settings in 24.04
> Well the snap is supposed to import my previous profile - it does not. Could you move ~/snap/thunderbird away, start /snap/bin/thunderbird from a cmdline and share was is being printed? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/2061882 Title: Thunderbird snap loses local folder settings in 24.04 Status in thunderbird package in Ubuntu: Invalid Bug description: After Thunderbird snap installs the local folders do not import from the deb Thunderbird. There also seems to be no way to get back to the deb version. I needed to manually move the local directory back to the original. I can no longer see my inbox and it keeps telling me that the /home/me/snap/thunderbird/hdd/home/me/.thunderbird/24a1u6qp.default/ImapMail/ is invalid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/2061882/+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 2063153] Re: Incorrect display Graphics Card in System -> system details
Thanks, that seems correct which means the problem is the settings, it's somewhat similar to bug #2037076 ** Package changed: switcheroo-control (Ubuntu) => gnome-control-center (Ubuntu) ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-control-center (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2063153 Title: Incorrect display Graphics Card in System -> system details Status in gnome-control-center package in Ubuntu: New Bug description: NVIDIA GeForce RTX 3050 Ti Mobile should be displayed here To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2063153/+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 2037076] Re: System Details incorrectly shows multiple GPUs
** Changed in: gnome-control-center (Ubuntu) Status: Incomplete => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2037076 Title: System Details incorrectly shows multiple GPUs Status in gnome-control-center: New Status in gnome-control-center package in Ubuntu: Triaged Bug description: My system has multiple GPUs: 00:02.0 Display controller: Intel Corporation HD Graphics 630 (rev 04) 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Polaris 22 XT [Radeon RX Vega M GH] (rev c0) 40:00.0 VGA compatible controller: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] (rev a1) It's an Intel Hades Canyon NUC with an external GPU in an enclosure. But it's equally valid to have multiple different GPUs in one desktop computer. What happens (see screenshot) In GNOME Control Center, the System Details overlay lists them as: -- Graphics NVIDIA GeForce GTX 1080 Ti Graphics 1 NVIDIA GeForce GTX 1080 Ti Graphics 2 NVIDIA GeForce GTX 1080 Ti -- Expected outcome I would expect each GPU to be displayed correctly. -- Graphics 1 NVIDIA GeForce GTX 1080 Ti Graphics 2 Intel HD Graphics 630 Graphics 3 AMD ATI Radeon RX Vega M GH -- ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-control-center 1:45.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 NonfreeKernelModules: zfs nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Sep 22 11:41:21 2023 InstallationDate: Installed on 2023-08-06 (47 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-control-center UpgradeStatus: Upgraded to mantic on 2023-09-18 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/2037076/+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 2063323] Re: Crash Connecting to RDP with FreeRDP 3.5.0 and Remmina (24.04)
*** This bug is a duplicate of bug 2062177 *** https://bugs.launchpad.net/bugs/2062177 ** This bug has been marked a duplicate of bug 2062177 Remmina crashes after RDP connection -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to remmina in Ubuntu. https://bugs.launchpad.net/bugs/2063323 Title: Crash Connecting to RDP with FreeRDP 3.5.0 and Remmina (24.04) Status in remmina package in Ubuntu: New Bug description: Core dumps with: [freerdp_settings_get_bool]: Invalid key index 0 [FreeRDP_instance|FREERDP_SETTINGS_TYPE_POINTER] Seems there is a fix here: https://gitlab.com/Remmina/Remmina/-/issues/3090 ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: remmina 1.4.35+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Apr 24 12:13:39 2024 SourcePackage: remmina UpgradeStatus: Upgraded to noble on 2024-04-23 (1 days ago) modified.conffile..etc.logrotate.d.apport: [modified] mtime.conffile..etc.logrotate.d.apport: 2023-06-10T11:09:46.502839 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/2063323/+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 2059756] Re: [SRU] adsys 0.14.1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: golang-1.22 (Ubuntu Jammy) Status: New => Confirmed -- 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/2059756 Title: [SRU] adsys 0.14.1 Status in adsys package in Ubuntu: Fix Released Status in golang-1.22 package in Ubuntu: Fix Released Status in adsys source package in Jammy: Confirmed Status in golang-1.22 source package in Jammy: Confirmed Bug description: [context] ADSys is a tool designed for administering and implementing Group Policy Objects (GPOs) from Active Directory on Linux systems. It includes a suite of services and commands that empower administrators to efficiently manage policy updates and maintain compliance with organizational business rules. Given that ADSys directly interfaces with Active Directory and needs to align with new business requirements in LTS releases, it has been essential to keep the package consistently updated with the latest changes of ADSys upstream source. As ADSys is a key component of our commercial offerings, our customers anticipate the availability of recently implemented features in the 22.04 release. Now that ADSys has a complete set of features, the request is to proceed with a one-off release of ADSys 0.14.1 to 22.04. Please note that any new features introduced in subsequent versions will be exclusively available in 24.04 and later releases. This version includes a comprehensive end to end automated test suite that runs ADSys against a real Active directory environment. Version 0.14.1 is available for 22.04 in a PPA (https://launchpad.net/~ubuntu-enterprise- desktop/+archive/ubuntu/adsys) and already used in production by customers. At this time of writing the number of open issues is 1 in Launchpad and 16 in GitHub including 6 enhancements. None of them have a high or critical importance. [references] LP: https://launchpad.net/ubuntu/+source/adsys LP Bugs: https://bugs.launchpad.net/ubuntu/+source/adsys GitHub: https://github.com/ubuntu/adsys/ GH Bugs: https://github.com/ubuntu/adsys/issues Documentation: https://canonical-adsys.readthedocs-hosted.com/en/stable/ Initial SRU discussion: https://lists.ubuntu.com/archives/ubuntu-release/2023-June/005650.html [changes] Full LP Changelog: https://launchpad.net/ubuntu/+source/adsys/+changelog * New features * New policies: - Add mount / network shares policy manager - Add AppArmor policy manager - Support multiple AD backends and implement Winbind support - Add system proxy policy manager - Add certificate policy manager for machines - Add adsysctl policy purge command to purge applied policies - Full documentation - Full end to end automated test suite. * Enhancements * Add a --machine / -m flag to adsysctl applied, indicating the policies applied to the current machine * Expose Ubuntu Pro status in the "status" command * Update scripts manager creation * List Pro policy types in service status output * Warn when Pro-only rules are configured * Use systemd via D-Bus instead of systemctl commands * Add placeholder notes for entry types * Rework Kerberos ticket handling logic to satisfy the Heimdal implementation of Kerberos * Rework policy application sync strategy * Print logs when policies are up to date * Update policy definitions to include dconf key for dark mode background * Infer user KRB5CCNAME path via the libkrb5 API (LP: #2049061) * Allow sssd backend to work without ad_domain being set (LP: #2054445) * Update apport hook to include journal errors and package logs * Bug fixes * Fix policy update failing when GPT.INI contains no version key * Fix object lookup for users having a FQDN as their hostname * Support special characters in domains when parsing sssd configuration * Fix DCONF_PROFILE not considering default_domain_suffix on sssd.conf * Ensure empty state for dconf policy * Handle case mismatches in GPT.INI file name * Ensure GPO URLs contain the FQDN of the domain controller * Add runtime dependency on nfs-common * Other * Updates to latest versions of Go (fixing known Go vulnerabilities) * Updates to latest versions of the Go dependencies * Updates and improvements to CI and QoL * Migrate translation support to native approach using go-i18n + gotext and switch to upstream gotext version Dependencies: * Build-dep: golang-go (>= 2:1.22~) * Dependencies to backport to 22.04: * golang-go >= 2:1.22 * ubuntu-proxy-manager (suggest. Required for Proxy support - feature will be disabled otherwise) * python3-cepces (suggest. Required for Certificates autoenrollment support - feature will be disabled otherwise) *
[Desktop-packages] [Bug 2059756] Re: [SRU] adsys 0.14.1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: adsys (Ubuntu Jammy) Status: New => Confirmed -- 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/2059756 Title: [SRU] adsys 0.14.1 Status in adsys package in Ubuntu: Fix Released Status in golang-1.22 package in Ubuntu: Fix Released Status in adsys source package in Jammy: Confirmed Status in golang-1.22 source package in Jammy: Confirmed Bug description: [context] ADSys is a tool designed for administering and implementing Group Policy Objects (GPOs) from Active Directory on Linux systems. It includes a suite of services and commands that empower administrators to efficiently manage policy updates and maintain compliance with organizational business rules. Given that ADSys directly interfaces with Active Directory and needs to align with new business requirements in LTS releases, it has been essential to keep the package consistently updated with the latest changes of ADSys upstream source. As ADSys is a key component of our commercial offerings, our customers anticipate the availability of recently implemented features in the 22.04 release. Now that ADSys has a complete set of features, the request is to proceed with a one-off release of ADSys 0.14.1 to 22.04. Please note that any new features introduced in subsequent versions will be exclusively available in 24.04 and later releases. This version includes a comprehensive end to end automated test suite that runs ADSys against a real Active directory environment. Version 0.14.1 is available for 22.04 in a PPA (https://launchpad.net/~ubuntu-enterprise- desktop/+archive/ubuntu/adsys) and already used in production by customers. At this time of writing the number of open issues is 1 in Launchpad and 16 in GitHub including 6 enhancements. None of them have a high or critical importance. [references] LP: https://launchpad.net/ubuntu/+source/adsys LP Bugs: https://bugs.launchpad.net/ubuntu/+source/adsys GitHub: https://github.com/ubuntu/adsys/ GH Bugs: https://github.com/ubuntu/adsys/issues Documentation: https://canonical-adsys.readthedocs-hosted.com/en/stable/ Initial SRU discussion: https://lists.ubuntu.com/archives/ubuntu-release/2023-June/005650.html [changes] Full LP Changelog: https://launchpad.net/ubuntu/+source/adsys/+changelog * New features * New policies: - Add mount / network shares policy manager - Add AppArmor policy manager - Support multiple AD backends and implement Winbind support - Add system proxy policy manager - Add certificate policy manager for machines - Add adsysctl policy purge command to purge applied policies - Full documentation - Full end to end automated test suite. * Enhancements * Add a --machine / -m flag to adsysctl applied, indicating the policies applied to the current machine * Expose Ubuntu Pro status in the "status" command * Update scripts manager creation * List Pro policy types in service status output * Warn when Pro-only rules are configured * Use systemd via D-Bus instead of systemctl commands * Add placeholder notes for entry types * Rework Kerberos ticket handling logic to satisfy the Heimdal implementation of Kerberos * Rework policy application sync strategy * Print logs when policies are up to date * Update policy definitions to include dconf key for dark mode background * Infer user KRB5CCNAME path via the libkrb5 API (LP: #2049061) * Allow sssd backend to work without ad_domain being set (LP: #2054445) * Update apport hook to include journal errors and package logs * Bug fixes * Fix policy update failing when GPT.INI contains no version key * Fix object lookup for users having a FQDN as their hostname * Support special characters in domains when parsing sssd configuration * Fix DCONF_PROFILE not considering default_domain_suffix on sssd.conf * Ensure empty state for dconf policy * Handle case mismatches in GPT.INI file name * Ensure GPO URLs contain the FQDN of the domain controller * Add runtime dependency on nfs-common * Other * Updates to latest versions of Go (fixing known Go vulnerabilities) * Updates to latest versions of the Go dependencies * Updates and improvements to CI and QoL * Migrate translation support to native approach using go-i18n + gotext and switch to upstream gotext version Dependencies: * Build-dep: golang-go (>= 2:1.22~) * Dependencies to backport to 22.04: * golang-go >= 2:1.22 * ubuntu-proxy-manager (suggest. Required for Proxy support - feature will be disabled otherwise) * python3-cepces (suggest. Required for Certificates autoenrollment support - feature will be disabled otherwise) * Note:
[Desktop-packages] [Bug 2062177] Re: Remmina crashes after RDP connection
facing the same issue
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to remmina in Ubuntu.
https://bugs.launchpad.net/bugs/2062177
Title:
Remmina crashes after RDP connection
Status in remmina package in Ubuntu:
In Progress
Bug description:
When connecting with RDP Remmina crashes. Syslog show the following:
2024-04-18T13:49:02.969819+02:00 localhost dbus-daemon[3214]: [session
uid=1001 pid=3214] Successfully activated service
'org.gnome.seahorse.Application'
2024-04-18T13:49:03.655883+02:00 localhost systemd[3176]: Started
app-gnome-org.remmina.Remmina-53436.scope - Application launched by gnome-shell.
2024-04-18T13:49:03.656884+02:00 localhost remmina[53441]: Remmina does not
log all output statements. Turn on more verbose output by using
"G_MESSAGES_DEBUG=remmina" as an environment variable.#012More info available
on the Remmina wiki
at:#012https://gitlab.com/Remmina/Remmina/-/wikis/Usage/Remmina-debugging
2024-04-18T13:49:03.766401+02:00 localhost remmina[53441]:
gtk_menu_attach_to_widget(): menu already attached to GtkMenuItem
2024-04-18T13:49:13.851397+02:00 localhost
org.remmina.Remmina.desktop[53441]: [13:49:13:572] [53441:d116]
[ERROR][com.freerdp.common.settings] - [freerdp_settings_get_bool]: Invalid key
index 0 [FreeRDP_instance|FREERDP_SETTINGS_TYPE_POINTER]
2024-04-18T13:49:13.851716+02:00 localhost
org.remmina.Remmina.desktop[53441]: [13:49:13:572] [53441:d116]
[FATAL][com.freerdp.winpr.assert] - [winpr_int_assert]: FALSE
[obj-x86_64-linux-gnu/libfreerdp/CMakeFiles/freerdp.dir/compiler_depend.ts:freerdp_settings_get_bool:637]
2024-04-18T13:49:13.851760+02:00 localhost
org.remmina.Remmina.desktop[53441]: [13:49:13:572] [53441:d116]
[FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 0:
dli_fname=/lib/x86_64-linux-gnu/libwinpr3.so.3 [0x70e694e2b000],
dli_sname=winpr_backtrace [0x70e694e97660]
2024-04-18T13:49:13.851791+02:00 localhost
org.remmina.Remmina.desktop[53441]: [13:49:13:572] [53441:d116]
[FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 1:
dli_fname=/lib/x86_64-linux-gnu/libwinpr3.so.3 [0x70e694e2b000],
dli_sname=winpr_log_backtrace_ex [0x70e694e9f150]
2024-04-18T13:49:13.851803+02:00 localhost
org.remmina.Remmina.desktop[53441]: [13:49:13:572] [53441:d116]
[FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 2:
dli_fname=/lib/x86_64-linux-gnu/libfreerdp3.so.3 [0x70e69420],
dli_sname=(null) [(nil)]
2024-04-18T13:49:13.851815+02:00 localhost
org.remmina.Remmina.desktop[53441]: [13:49:13:572] [53441:d116]
[FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 3:
dli_fname=/lib/x86_64-linux-gnu/libfreerdp3.so.3 [0x70e69420],
dli_sname=freerdp_settings_get_bool [0x70e6942658a0]
2024-04-18T13:49:13.851827+02:00 localhost
org.remmina.Remmina.desktop[53441]: [13:49:13:572] [53441:d116]
[FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 4:
dli_fname=/usr/lib/x86_64-linux-gnu/remmina/plugins/remmina-plugin-rdp.so
[0x70e6958dd000], dli_sname=(null) [(nil)]
2024-04-18T13:49:13.851839+02:00 localhost
org.remmina.Remmina.desktop[53441]: [13:49:13:572] [53441:d116]
[FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 5:
dli_fname=/usr/lib/x86_64-linux-gnu/remmina/plugins/remmina-plugin-rdp.so
[0x70e6958dd000], dli_sname=(null) [(nil)]
2024-04-18T13:49:13.851851+02:00 localhost
org.remmina.Remmina.desktop[53441]: [13:49:13:572] [53441:d116]
[FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 6:
dli_fname=/usr/bin/../lib/x86_64-linux-gnu/libc.so.6 [0x70e69940],
dli_sname=(null) [(nil)]
2024-04-18T13:49:13.851873+02:00 localhost
org.remmina.Remmina.desktop[53441]: [13:49:13:572] [53441:d116]
[FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 7:
dli_fname=/usr/bin/../lib/x86_64-linux-gnu/libc.so.6 [0x70e69940],
dli_sname=(null) [(nil)]
2024-04-18T13:49:13.851885+02:00 localhost
org.remmina.Remmina.desktop[53441]: [13:49:13:572] [53441:d116]
[FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 8: unresolvable,
address=(nil)
2024-04-18T13:49:14.938231+02:00 localhost
org.remmina.Remmina.desktop[53436]: /usr/bin/remmina-file-wrapper: line 37:
53441 Aborted (core dumped) "$REMMINA" "${@}"
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: remmina 1.4.35+dfsg-0ubuntu4
ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
Uname: Linux 6.8.0-22-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: pass
CloudArchitecture: x86_64
CloudID: none
CloudName: none
CloudPlatform: none
CloudSubPlatform: config
Date: Thu Apr 18 13:59:31 2024
InstallationDate: Installed on 2022-05-21 (698 days ago)
InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64
(20220421)
[Desktop-packages] [Bug 2063336] Re: All Chromium based applications fail to render on Wayland
Sounds like bug 1967488 might've got fixed in the past few months (which would be great news), worked for a while and then https://issues.chromium.org/issues/329678163 hit which affects all GPUs and OS releases. Also the glitchy rendering after typing is bug 1970389 (if not bug 2059847 on Xorg), but after that I have no more bad news because those are all the blockers for Wayland on Nvidia: https://bugs.launchpad.net/ubuntu/+bugs?field.tag=nvidia-wayland -- 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/2063336 Title: All Chromium based applications fail to render on Wayland Status in Chromium Browser: Unknown Status in chromium-browser package in Ubuntu: Confirmed Bug description: Most of the time (3/4 desktop sessions attempted) all Chromium based applications I have tested (Chromium, VS Code, Mattermost) fail to render themselves, on actual display panel presenting random garbage, and when screenshotted, showing supposedly transparent pixels. I have also recorded an example video I can share in case this is of use (attached the screenshot with the video). ProblemType: Bug DistroRelease: Ubuntu 24.04 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: zfs nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 24 16:21:15 2024 InstallationDate: Installed on 2021-11-08 (898 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Snap: chromium 124.0.6367.60 (latest/stable) SnapChanges: no changes found SnapSource: ubuntu/+source/chromium-browser UpgradeStatus: Upgraded to noble on 2024-04-24 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/2063336/+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 2061242] Re: gnome-shell crashes randomly
Hi Brian, my report once again got "invalid core dump" message. Strangely, now it took 2 weeks instead of 1 hour. We've previously talked in https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2058693, you said to attach a .crash file and make report private, which I did. Can you access the report now? If not, how can I add you to it? ** Information type changed from Private to Public -- 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/2061242 Title: gnome-shell crashes randomly Status in gnome-shell package in Ubuntu: Invalid Bug description: Don't yet understand what triggers it, maybe monitor connect/disconnect. ProblemType: Crash DistroRelease: Ubuntu 24.04 Package: gnome-shell 46.0-0ubuntu4 Uname: Linux 6.9.0-rc2 x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 13 20:29:01 2024 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2024-02-14 (60 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240212) ProcAttrCurrent: Error: [Errno 22] Invalid argument ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 46.0-1ubuntu6 Signal: 6 SignalName: SIGABRT SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker libvirt lpadmin ollama plugdev sudo users To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2061242/+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 2063336] Re: All Chromium based applications fail to render on Wayland
Daniel, yes it's indeed an NVIDIA GPU as the primary one (both primary and secondary are NVIDIA, an RTX A6000 and a RTX3090). The issue shows up for both the Chromium snap and any other Chromium based app I could find. I did have some Wayland & NVIDIA issues (glitchy rendering after typing on the keyboard) also on Mantic and before on this same system, but this symptom is a lot more extreme now on Noble. Another observation as I messed around with reproducing this: I can see that on Noble hotplugging the display on Wayland doesn't really work (between these same NVIDIA GPUs), whereas on Mantic I didn't have the same problem. ** Description changed: - I am noticing two - - - Most of the time (3/4 desktop sessions attempted) all Chromium based + Most of the time (3/4 desktop sessions attempted) all Chromium based applications I have tested (Chromium, VS Code, Mattermost) fail to render themselves, on actual display panel presenting random garbage, - and when screenshotted, showing supposedly showing transparent pixels. + and when screenshotted, showing supposedly transparent pixels. I have also recorded an example video I can share in case this is of use (attached the screenshot with the video). ProblemType: Bug DistroRelease: Ubuntu 24.04 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: zfs nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 24 16:21:15 2024 InstallationDate: Installed on 2021-11-08 (898 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Snap: chromium 124.0.6367.60 (latest/stable) SnapChanges: no changes found SnapSource: ubuntu/+source/chromium-browser UpgradeStatus: Upgraded to noble on 2024-04-24 (0 days ago) -- 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/2063336 Title: All Chromium based applications fail to render on Wayland Status in Chromium Browser: Unknown Status in chromium-browser package in Ubuntu: Confirmed Bug description: Most of the time (3/4 desktop sessions attempted) all Chromium based applications I have tested (Chromium, VS Code, Mattermost) fail to render themselves, on actual display panel presenting random garbage, and when screenshotted, showing supposedly transparent pixels. I have also recorded an example video I can share in case this is of use (attached the screenshot with the video). ProblemType: Bug DistroRelease: Ubuntu 24.04 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: zfs nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 24 16:21:15 2024 InstallationDate: Installed on 2021-11-08 (898 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Snap: chromium 124.0.6367.60 (latest/stable) SnapChanges: no changes found SnapSource: ubuntu/+source/chromium-browser UpgradeStatus: Upgraded to noble on 2024-04-24 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/2063336/+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 2063341] Re: Ubuntu crashesh after KVM swicth back/wake up/suspend
** Package changed: ubuntu => gnome-shell (Ubuntu) -- 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/2063341 Title: Ubuntu crashesh after KVM swicth back/wake up/suspend Status in gnome-shell package in Ubuntu: New Bug description: I've been using Ubuntu for almost 2 years and it's been working fine. I use a KVM switch (built in Benq monitor) all the time. Since last month Ubuntu randomly crashes when I switch back to it. Or it could be wake up/suspend, I can't see when it exactly happens, it's just logging screen after crash. I am running: openVPN, firefox (dozen tabs), chrome (ms teams), slack, postman, 3x Intellij IDEA, VS Code System logs don't show anything meaningful to me or Google and I don't know how to get a clue as to what's going on. I suspect a new version of MS Teams that was introduced a few weeks ago. Please help me I cannot reproduce the crash or find anything on the web about it. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.9-0ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-28.29~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 24 15:59:03 2024 DisplayManager: gdm3 InstallationDate: Installed on 2022-08-31 (601 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) RelatedPackageVersions: mutter-common 42.9-0ubuntu7 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2063341/+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 2063341] [NEW] Ubuntu crashesh after KVM swicth back/wake up/suspend
You have been subscribed to a public bug: I've been using Ubuntu for almost 2 years and it's been working fine. I use a KVM switch (built in Benq monitor) all the time. Since last month Ubuntu randomly crashes when I switch back to it. Or it could be wake up/suspend, I can't see when it exactly happens, it's just logging screen after crash. I am running: openVPN, firefox (dozen tabs), chrome (ms teams), slack, postman, 3x Intellij IDEA, VS Code System logs don't show anything meaningful to me or Google and I don't know how to get a clue as to what's going on. I suspect a new version of MS Teams that was introduced a few weeks ago. Please help me I cannot reproduce the crash or find anything on the web about it. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.9-0ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-28.29~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 24 15:59:03 2024 DisplayManager: gdm3 InstallationDate: Installed on 2022-08-31 (601 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) RelatedPackageVersions: mutter-common 42.9-0ubuntu7 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- Ubuntu crashesh after KVM swicth back/wake up/suspend https://bugs.launchpad.net/bugs/2063341 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. -- 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 2063336] Re: All Chromium based applications fail to render (dual NVIDIA GPU system)
Fixed upstream today? https://issues.chromium.org/issues/329678163 ** Also affects: chromium-browser via https://issues.chromium.org/issues/329678163 Importance: Unknown Status: Unknown ** Summary changed: - All Chromium based applications fail to render (dual NVIDIA GPU system) + All Chromium based applications fail to render on Wayland -- 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/2063336 Title: All Chromium based applications fail to render on Wayland Status in Chromium Browser: Unknown Status in chromium-browser package in Ubuntu: Confirmed Bug description: I am noticing two - Most of the time (3/4 desktop sessions attempted) all Chromium based applications I have tested (Chromium, VS Code, Mattermost) fail to render themselves, on actual display panel presenting random garbage, and when screenshotted, showing supposedly showing transparent pixels. I have also recorded an example video I can share in case this is of use (attached the screenshot with the video). ProblemType: Bug DistroRelease: Ubuntu 24.04 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: zfs nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 24 16:21:15 2024 InstallationDate: Installed on 2021-11-08 (898 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Snap: chromium 124.0.6367.60 (latest/stable) SnapChanges: no changes found SnapSource: ubuntu/+source/chromium-browser UpgradeStatus: Upgraded to noble on 2024-04-24 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/2063336/+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 2063336] Re: All Chromium based applications fail to render (dual NVIDIA GPU system)
If you're using Nvidia as the primary GPU though, it was never working according to bug 1967488. ** Bug watch added: issues.chromium.org/issues #329678163 https://issues.chromium.org/issues/329678163 -- 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/2063336 Title: All Chromium based applications fail to render on Wayland Status in Chromium Browser: Unknown Status in chromium-browser package in Ubuntu: Confirmed Bug description: I am noticing two - Most of the time (3/4 desktop sessions attempted) all Chromium based applications I have tested (Chromium, VS Code, Mattermost) fail to render themselves, on actual display panel presenting random garbage, and when screenshotted, showing supposedly showing transparent pixels. I have also recorded an example video I can share in case this is of use (attached the screenshot with the video). ProblemType: Bug DistroRelease: Ubuntu 24.04 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: zfs nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 24 16:21:15 2024 InstallationDate: Installed on 2021-11-08 (898 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Snap: chromium 124.0.6367.60 (latest/stable) SnapChanges: no changes found SnapSource: ubuntu/+source/chromium-browser UpgradeStatus: Upgraded to noble on 2024-04-24 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/2063336/+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 2063336] Re: All Chromium based applications fail to render (dual NVIDIA GPU system)
It's a Chromium bug. Same is happening with Google Chrome on jammy with Intel graphics. Workaround: google-chrome --ozone-platform=x11 ** Changed in: ubuntu Status: New => Invalid ** Package changed: ubuntu => chromium-browser (Ubuntu) ** Changed in: chromium-browser (Ubuntu) Status: Invalid => Confirmed ** Tags added: jammy -- 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/2063336 Title: All Chromium based applications fail to render on Wayland Status in Chromium Browser: Unknown Status in chromium-browser package in Ubuntu: Confirmed Bug description: I am noticing two - Most of the time (3/4 desktop sessions attempted) all Chromium based applications I have tested (Chromium, VS Code, Mattermost) fail to render themselves, on actual display panel presenting random garbage, and when screenshotted, showing supposedly showing transparent pixels. I have also recorded an example video I can share in case this is of use (attached the screenshot with the video). ProblemType: Bug DistroRelease: Ubuntu 24.04 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: zfs nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 24 16:21:15 2024 InstallationDate: Installed on 2021-11-08 (898 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Snap: chromium 124.0.6367.60 (latest/stable) SnapChanges: no changes found SnapSource: ubuntu/+source/chromium-browser UpgradeStatus: Upgraded to noble on 2024-04-24 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/2063336/+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 2063336] [NEW] All Chromium based applications fail to render (dual NVIDIA GPU system)
You have been subscribed to a public bug: I am noticing two - Most of the time (3/4 desktop sessions attempted) all Chromium based applications I have tested (Chromium, VS Code, Mattermost) fail to render themselves, on actual display panel presenting random garbage, and when screenshotted, showing supposedly showing transparent pixels. I have also recorded an example video I can share in case this is of use (attached the screenshot with the video). ProblemType: Bug DistroRelease: Ubuntu 24.04 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: zfs nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 24 16:21:15 2024 InstallationDate: Installed on 2021-11-08 (898 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Snap: chromium 124.0.6367.60 (latest/stable) SnapChanges: no changes found SnapSource: ubuntu/+source/chromium-browser UpgradeStatus: Upgraded to noble on 2024-04-24 (0 days ago) ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug noble snap wayland-session -- All Chromium based applications fail to render (dual NVIDIA GPU system) https://bugs.launchpad.net/bugs/2063336 You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. -- 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 2061214] Re: [SRU] Software Sources is not compatible with deb822
Yeah sorry folks this was a bit awkward, to avoid respinning other images we temporarily spun out software-properties-qt into its own package (0.99.48.1) and fixed it there, and hence there was no bug closure or anything. This will fold back into the main package in a zero-day SRU in 0.99.49. ** Also affects: software-properties-qt (Ubuntu) Importance: Undecided Status: New ** Changed in: software-properties-qt (Ubuntu Noble) Status: New => 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/2061214 Title: [SRU] Software Sources is not compatible with deb822 Status in software-properties package in Ubuntu: Confirmed Status in software-properties-qt package in Ubuntu: Fix Released Status in software-properties source package in Noble: Confirmed Status in software-properties-qt source package in Noble: Fix Released Bug description: [ Impact ] Ubuntu 24.04 now uses deb822 to represent software sources for deb packages, instead of /etc/apt/sources.list. The complete rationale for this change can be found here: https://discourse.ubuntu.com/t/spec- apt-deb822-sources-by-default/29333 software-properties has two graphical frontends for editing these software sources, one is GTK-based and the other is Qt-based. When the underlying change to deb822 sources was made, the GTK-based frontend and the DBus backend interface gained support. The original bug report shown below informed us of the lack of deb822 support in the Qt frontend, which results in a broken, non-functional interface when attempting to view or edit most values on the first two tabs. The fix for this is to implement a Qt dialog for deb822 sources that somewhat matches the existing GTK interface. [ Test Plan ] Install software-properties-qt 0.99.48 or earlier. Reproducing the bug: 1. From the menu, open Software Sources. Alternatively, run `sudo -E software-properties-qt` in a terminal. 2. Observe that all four checkboxes on the Ubuntu Software tab (main, universe, restricted, and multiverse) are unchecked. 3. Move to the Other Software tab and observe that there are no items in the list. Upgrade to software-properties-qt 0.99.49. Intended functionality: 1. From the menu, open Software Sources. Alternatively, run `sudo -E software-properties-qt` in a terminal. 2. Observe that one or more checkboxes on the Ubuntu Software tab (representing main, universe, restricted, or multiverse) are checked. Toggle one or more of the checkboxes. 3. Using a text editor of some kind (perhaps Vim), confirm that /etc/apt/sources.list.d/ubuntu.sources reflects your changes. 4. Switch to the Other Software tab, there should be one item in the list. 5. Select that item, then click Edit at the bottom of the dialog. Make a modification to every field on the screen, or a combination of fields you would like to test. All fields should work. 6. Click the OK button at the bottom of the dialog to confirm the changes, then click Edit for that item again. The changes you made should be reflected (meaning, the changes were saved.) 7. Using a text editor of some kind (perhaps Vim), confirm that /etc/apt/sources.list.d/ubuntu.sources reflects your changes. [ Where problems could occur ] This is well-tested code. That being said, the following small edge cases exist: - If you create a very large amount of rows, it infinitely expands the dialog without a scroll wheel. This is the same functionality as the GTK frontend. - Error validation is not performed on the deb822 lines, they are simply written to the ubuntu.sources file. This is good as a starting point, but also relies on the appropriate update notifier handling these errors. This is the same functionality as the GTK frontend. In a future update, this functionality could be broken by one or more of the following underlying changes: - Changes to the software-properties backend which are only implemented for the GTK frontend. - Changes to the location or formatting of the ubuntu.sources file. - Regressions in the Python bindings for Qt 5, which are rare but possible. - Regressions in Python itself. [ Other Info ] Ubuntu Studio's live ISO and installed system are affected by this. Only Lubuntu's installed system is affected by this. [ Original Report ] Upgrading Lubuntu Jammy to Lubuntu Noble using TUI results in "Software sources" not correctly updated after upgrade. Prompt= shows normal and not LTS Used command sudo do-release-upgrade -d Otherwise the upgrade is good see attached screenshot ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: software-properties-common 0.99.46 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 ApportVersion: 2.28.0-0ubuntu1
[Desktop-packages] [Bug 2056760] Re: [snap]Thunderbird doesn't authenticate with sssd-kcm
Marking the sssd tracker as invalid then.
** Tags removed: server-traige-discuss
** Changed in: sssd (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/2056760
Title:
[snap]Thunderbird doesn't authenticate with sssd-kcm
Status in sssd package in Ubuntu:
Invalid
Status in thunderbird package in Ubuntu:
New
Bug description:
I have Kerberos authentication set up in Thunderbird for my mailbox.
My environment contains:
helga@helga-rashomon:~$ env | grep KRB
KRB5CCNAME=KCM:
This means that Kerberos authentication should work through the sssd-
kcm server.
I initialize Kerberos and verify that it functions correctly:
helga@helga-rashomon:~$ klist
Ticket cache: KCM:1000
Default principal: he...@example.org
Valid starting Expires Service principal
03/11/24 04:14:24 03/12/24 04:14:24 krbtgt/example@example.org
03/11/24 04:15:24 03/12/24 04:14:24 HTTP/redmine.example.org@
Ticket server: HTTP/redmine.example@example.org
(listing redacted to say example.org instead of the real address. the
redmine listing shows that Firefox works correctly with this address)
However, when I open the Snap Thunderbird, it does not recognize this
Kerberos setup, showing me "The Kerberos/GSSAPI ticket was not
accepted by the IMAP server". klist -A likewise shows no changes.
The exact same setup works when I specify KRB5CCNAME=DIR:${HOME}/krb5cc in
.profile instead.
The sssd-kcm setup also works in Thunderbird native and Flatpak profiles.
Considering the Flatpak specifically permits access to
/run/.heim_org.h5l.kcm-socket, could it be that the Thunderbird Snap
is not allowed to access this socket?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/2056760/+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 1980836] Re: Regression in Ubuntu 22.04: Content of form field stored invisibly
SRU information added.
** Description changed:
- Evince on Ubuntu 22.04 is not able to handle some PDF forms correctly
- anymore that it was able to handle on Ubuntu 21.10 and on Ubuntu 20.04.
+ [ Impact ]
+
+ The bug causes text entered in certain PDF form fields to be stored but
+ both displayed and printed white (on white background).
+
+ [ Test Plan ]
+
+ 1. Download the attached 230-muster-01.pdf.
+ 2. Try to input to any of the main content fields starting with 06-09
("Anrede des Zahlungspflichtigen etc").
+ 3. Observe that it does not work.
+ 4. Install the updated poppler package versions
+ 5. Try the same fields and see they're functoning properly now with visibla
text.
+ 6. Test also that the fields like "Aktenzeichen", "TL-Nr." or
"Buchungsstelle" that weren't broken continue to work.
+
+ [ Where problems could occur ]
+
+ It is a merged upstream fix to Annot.cc file that fixed two upstream
+ bugs https://gitlab.freedesktop.org/poppler/poppler/-/issues/1189 and
+ https://gitlab.freedesktop.org/poppler/poppler/-/issues/1267.
+
+ There are no indications of upstream regressions caused by this fix, and
+ it was released in upstream stable release 22.08.0 (Ubuntu 22.04 LTS has
+ version based on 22.02.0).
+
+ However, since it's an individual cherry-pick there could always be a
+ PDF somewhere having issues with this, so it's useful to let it be
+ tested with various files in addition to the problematic ones.
+
+
+
+ --- original report ---
+
+
+ Evince on Ubuntu 22.04 is not able to handle some PDF forms correctly anymore
that it was able to handle on Ubuntu 21.10 and on Ubuntu 20.04.
The symptom is that one can edit the form content and also save it, but
that the entered text is only visible when the form field is focused and
in edit mode. Otherwise the text it is invisible, also on printouts.
Such bugs have been reported against Evince for a long time (e.g.,
https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/265033) but I am
reporting this as a new bug because for the current form with which I am
experiencing this it is a regression.
I have attached the problematic form with two form fields filled out, one in
the upper left corner and the big one in the lower half.
I have produced this by taking the original, empty form (produced by somebody
else) and first opened it in Evince 41.4, which I have installed from the snap
package (revision 1017) on Ubuntu 22.04. I entered text in the upper left field
and saved the form.
Then I opened the PDF in Evince 42.3 from the apt package of Ubuntu 22.04 and
entered text in the big field and saved the form.
Evince 3.36 on Ubuntu 20.04 has the same (correct) behavior as Evince
41.4.
When I open the PDF again, only the text in the first field is visible.
The text in the second field is visible only if I click into the field.
The visibility of the field contents is the same for Evince 41.4 (snap),
Evince 42.3 (apt), and Okular 20.12.3 (snap). So it seems that the
problem is with Evince 42.3 incorrectly saving the field content, not
with displaying it.
Firefox shows and prints the content of both fields, though.
Note that I cannot switch back to Evince 41 because for some other forms
that I have the exact same problem happens only with the old version and
the new version fixes it. So it seems that something changed that fixed
it for some forms and broke it for others.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: evince 42.3-0ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35
Uname: Linux 5.15.0-40-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Jul 6 14:32:27 2022
InstallationDate: Installed on 2021-11-26 (222 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
RebootRequiredPkgs: Error: path contained symlinks.
Snap.Changes:
- ID Status Spawn Bereit
Zusammenfassung
- 137 Done2022-07-06T12:48:33+02:00 2022-07-06T12:48:41+02:00
Installiere "evince" Snap
+ ID Status Spawn Bereit
Zusammenfassung
+ 137 Done2022-07-06T12:48:33+02:00 2022-07-06T12:48:41+02:00
Installiere "evince" Snap
SourcePackage: evince
UpgradeStatus: Upgraded to jammy on 2022-06-22 (13 days ago)
** Also affects: evince (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: poppler (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: poppler (Ubuntu Jammy)
Status: New => Triaged
** Changed in: poppler (Ubuntu Jammy)
Assignee: (unassigned) => Timo Jyrinki (timo-jyrinki)
** Changed in: evince (Ubuntu Jammy)
Status: New => Invalid
** Description changed:
[ Impact ]
The bug causes text entered in certain PDF form fields to be stored but
both displayed
[Desktop-packages] [Bug 1980805] Re: Backport packages for 20.04.5 HWE stack
** Changed in: mesa-amber (Ubuntu Focal) Status: Fix Committed => Won't Fix ** Changed in: llvm-toolchain-13 (Ubuntu Focal) Status: Fix Committed => Won't Fix ** Changed in: libdrm (Ubuntu Focal) Status: Fix Committed => Won't Fix -- 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/1980805 Title: Backport packages for 20.04.5 HWE stack Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-13 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in mesa-amber package in Ubuntu: Invalid Status in libdrm source package in Focal: Won't Fix Status in llvm-toolchain-13 source package in Focal: Won't Fix Status in mesa source package in Focal: Won't Fix Status in mesa-amber source package in Focal: Won't Fix Bug description: [Impact] These are needed for 20.04.5 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. [What could go wrong] libdrm: pci-id updates, some minor api updates mesa: a new major release, but we'll pull the final stable release of 22.0.x series, so there shouldn't be any regressions left at that point mesa-amber: forked from mesa 21.3.x, this LTS branch keeps old DRI drivers that were removed from main mesa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1980805/+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 2056434] Re: Thunderbird profile not migrated to snap
@Pablo, could you report a new bug and include what is printed on stdout on first start of the thunderbird snap? basically remove ~/snap/thunderbird, start thunderbird and see what is printed One potential reason could be that you don't have enough free space in your userdir to copy the profile but it's difficult to say without the log details... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/2056434 Title: Thunderbird profile not migrated to snap Status in thunderbird package in Ubuntu: Fix Released Bug description: Today's update installed the thunderbird snap and removed the thunderbird binary but it did not migrate my thunderbird profile. Now I don't have access to any old mails anymore. Looking at ~/.thunderbird: $ cat profiles.ini [Profile1] Name=default IsRelative=1 Path=ao6t0qef.default Default=1 [InstallFDC34C9F024745EB] Default=ji04wv64.default-release Locked=1 [Profile0] Name=default-release IsRelative=1 Path=ji04wv64.default-release [General] StartWithLastProfile=1 Version=2 ji04wv64.default-release is the folder that should have been migrated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/2056434/+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 2058514] Re: System crashes/freezes when suspending
Well, my specific problem might be related to the Thinkpad model:
https://www.reddit.com/r/thinkpad/comments/13pzjlq/t14_gen_3_amd_sleep_hibernate_issues_collection/
Suspend works perfectly on my other computers.
--
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/2058514
Title:
System crashes/freezes when suspending
Status in xserver-xorg-video-amdgpu package in Ubuntu:
Confirmed
Bug description:
Sometimes (I'd say 20% of the time) either a manual or automatic
suspend fails in these ways:
* power button remains lit (on succesful suspend it flashes)
* Fans may remain spinning and (indirectly observed) battery drains quite fast
* Screen black, impossible to wake, only to shut down by long power button
press
Bug occurs BOTH on Wayland and Xorg Gnome, so not sure which package
is at fault.
In addition, bug submission documentation is not very good, I'm filing this
bug after 30 minutes of bug documentation and I'm still confident this is filed
incorrectly.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xserver-xorg-video-amdgpu 23.0.0-1
ProcVersionSignature: Ubuntu 6.5.0-26.26-generic 6.5.13
Uname: Linux 6.5.0-26-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Mar 20 19:57:53 2024
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
GraphicsCard:
Advanced Micro Devices, Inc. [AMD/ATI] Lucienne [1002:164c] (rev c2)
(prog-if 00 [VGA controller])
Subsystem: Lenovo Lucienne [17aa:5097]
InstallationDate: Installed on 2023-12-08 (103 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64
(20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-26-generic
root=UUID=112bce1c-b1dd-49e6-b6e9-7c913a1842d9 ro quiet splash
usbcore.autosuspend=-1 vt.handoff=7
SourcePackage: xserver-xorg-video-amdgpu
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/29/2023
dmi.bios.release: 1.16
dmi.bios.vendor: LENOVO
dmi.bios.version: R1OET37W (1.16 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20YG00BRMH
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.16
dmi.modalias:
dmi:bvnLENOVO:bvrR1OET37W(1.16):bd09/29/2023:br1.16:efr1.16:svnLENOVO:pn20YG00BRMH:pvrThinkPadE15Gen3:rvnLENOVO:rn20YG00BRMH:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20YG_BU_Think_FM_ThinkPadE15Gen3:
dmi.product.family: ThinkPad E15 Gen 3
dmi.product.name: 20YG00BRMH
dmi.product.sku: LENOVO_MT_20YG_BU_Think_FM_ThinkPad E15 Gen 3
dmi.product.version: ThinkPad E15 Gen 3
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
1:1.0.17-2build1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/2058514/+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 2059756] Re: [SRU] adsys 0.14.1
** Description changed: [context] ADSys is a tool designed for administering and implementing Group Policy Objects (GPOs) from Active Directory on Linux systems. It includes a suite of services and commands that empower administrators to efficiently manage policy updates and maintain compliance with organizational business rules. Given that ADSys directly interfaces with Active Directory and needs to align with new business requirements in LTS releases, it has been essential to keep the package consistently updated with the latest changes of ADSys upstream source. As ADSys is a key component of our commercial offerings, our customers anticipate the availability of recently implemented features in the 22.04 release. Now that ADSys has a complete set of features, the request is to proceed with a one-off release of ADSys 0.14.1 to 22.04. Please note that any new features introduced in subsequent versions will be exclusively available in 24.04 and later releases. This version includes a comprehensive end to end automated test suite that runs ADSys against a real Active directory environment. Version 0.14.1 is available for 22.04 in a PPA (https://launchpad.net/~ubuntu-enterprise-desktop/+archive/ubuntu/adsys) and already used in production by customers. At this time of writing the number of open issues is 1 in Launchpad and 16 in GitHub including 6 enhancements. None of them have a high or critical importance. [references] LP: https://launchpad.net/ubuntu/+source/adsys LP Bugs: https://bugs.launchpad.net/ubuntu/+source/adsys GitHub: https://github.com/ubuntu/adsys/ GH Bugs: https://github.com/ubuntu/adsys/issues Documentation: https://canonical-adsys.readthedocs-hosted.com/en/stable/ Initial SRU discussion: https://lists.ubuntu.com/archives/ubuntu-release/2023-June/005650.html [changes] Full LP Changelog: https://launchpad.net/ubuntu/+source/adsys/+changelog * New features * New policies: - Add mount / network shares policy manager - Add AppArmor policy manager - Support multiple AD backends and implement Winbind support - Add system proxy policy manager - Add certificate policy manager for machines - Add adsysctl policy purge command to purge applied policies - Full documentation - Full end to end automated test suite. * Enhancements * Add a --machine / -m flag to adsysctl applied, indicating the policies applied to the current machine * Expose Ubuntu Pro status in the "status" command * Update scripts manager creation * List Pro policy types in service status output * Warn when Pro-only rules are configured * Use systemd via D-Bus instead of systemctl commands * Add placeholder notes for entry types * Rework Kerberos ticket handling logic to satisfy the Heimdal implementation of Kerberos * Rework policy application sync strategy * Print logs when policies are up to date * Update policy definitions to include dconf key for dark mode background * Infer user KRB5CCNAME path via the libkrb5 API (LP: #2049061) * Allow sssd backend to work without ad_domain being set (LP: #2054445) * Update apport hook to include journal errors and package logs * Bug fixes * Fix policy update failing when GPT.INI contains no version key * Fix object lookup for users having a FQDN as their hostname * Support special characters in domains when parsing sssd configuration * Fix DCONF_PROFILE not considering default_domain_suffix on sssd.conf * Ensure empty state for dconf policy * Handle case mismatches in GPT.INI file name * Ensure GPO URLs contain the FQDN of the domain controller * Add runtime dependency on nfs-common * Other * Updates to latest versions of Go (fixing known Go vulnerabilities) * Updates to latest versions of the Go dependencies * Updates and improvements to CI and QoL * Migrate translation support to native approach using go-i18n + gotext and switch to upstream gotext version Dependencies: * Build-dep: golang-go (>= 2:1.22~) * Dependencies to backport to 22.04: * golang-go >= 2:1.22 * ubuntu-proxy-manager (suggest. Required for Proxy support - feature will be disabled otherwise) * python3-cepces (suggest. Required for Certificates autoenrollment support - feature will be disabled otherwise) * Note: Both are currently in the new queue of 22.04 : https://launchpad.net/ubuntu/jammy/+queue?queue_state=0_text= [test plan] # Process Adsys follows a robust continuous integration and testing process. It is covered by a comprehensive automated tests suite (https://github.com/ubuntu/adsys/actions/workflows/qa.yaml) and an automated end to end test suite that runs in a real active directory environment (https://github.com/ubuntu/adsys/actions/workflows/e2e-tests.yaml). The team applied the following quality
[Desktop-packages] [Bug 2063333] [NEW] gnome-remote-desktop.service: Failed to determine user credentials: No such process
Public bug reported:
On a RISC-V Ubuntu 24.04 I installed ubuntu-desktop.
The desktop does not show up though gdm3 is running.
I see the following error messages which might indicate a dependency
issue:
pr 24 12:29:35 unmatched systemd[1]: Starting gnome-remote-desktop.service -
GNOME Remote Desktop...
Apr 24 12:29:35 unmatched (p-daemon)[1752]: gnome-remote-desktop.service:
Failed to determine user credentials: No such process
Apr 24 12:29:35 unmatched systemd[1]: gnome-remote-desktop.service: Main
process exited, code=exited, status=217/USER
Apr 24 12:29:35 unmatched systemd[1]: gnome-remote-desktop.service: Failed with
result 'exit-code'.
Apr 24 12:29:35 unmatched systemd[1]: Failed to start
gnome-remote-desktop.service - GNOME Remote Desktop.
Apr 24 12:29:35 unmatched systemd[1]: gnome-remote-desktop.service: Scheduled
restart job, restart counter is at 1.
Apr 24 12:29:35 unmatched systemd[1]: Starting gnome-remote-desktop.service -
GNOME Remote Desktop...
Apr 24 12:29:35 unmatched (p-daemon)[1753]: gnome-remote-desktop.service:
Failed to determine user credentials: No such process
Apr 24 12:29:35 unmatched systemd[1]: gnome-remote-desktop.service: Main
process exited, code=exited, status=217/USER
Apr 24 12:29:35 unmatched systemd[1]: gnome-remote-desktop.service: Failed with
result 'exit-code'.
Apr 24 12:29:35 unmatched systemd[1]: Failed to start
gnome-remote-desktop.service - GNOME Remote Desktop.
Apr 24 12:29:36 unmatched systemd[1]: gnome-remote-desktop.service: Scheduled
restart job, restart counter is at 2.
Apr 24 12:29:36 unmatched systemd[1]: Starting gnome-remote-desktop.service -
GNOME Remote Desktop...
Apr 24 12:29:36 unmatched (p-daemon)[1754]: gnome-remote-desktop.service:
Failed to determine user credentials: No such process
Apr 24 12:29:36 unmatched systemd[1]: gnome-remote-desktop.service: Main
process exited, code=exited, status=217/USER
Apr 24 12:29:36 unmatched systemd[1]: gnome-remote-desktop.service: Failed with
result 'exit-code'.
Apr 24 12:29:36 unmatched systemd[1]: Failed to start
gnome-remote-desktop.service - GNOME Remote Desktop.
Apr 24 12:29:36 unmatched systemd[1]: gnome-remote-desktop.service: Scheduled
restart job, restart counter is at 3.
Apr 24 12:29:36 unmatched systemd[1]: Starting gnome-remote-desktop.service -
GNOME Remote Desktop...
Apr 24 12:29:36 unmatched (p-daemon)[1755]: gnome-remote-desktop.service:
Failed to determine user credentials: No such process
Apr 24 12:29:36 unmatched systemd[1]: gnome-remote-desktop.service: Main
process exited, code=exited, status=217/USER
Apr 24 12:29:36 unmatched systemd[1]: gnome-remote-desktop.service: Failed with
result 'exit-code'.
Apr 24 12:29:36 unmatched systemd[1]: Failed to start
gnome-remote-desktop.service - GNOME Remote Desktop.
Apr 24 12:29:36 unmatched systemd[1]: gnome-remote-desktop.service: Scheduled
restart job, restart counter is at 4.
Apr 24 12:29:36 unmatched systemd[1]: Starting gnome-remote-desktop.service -
GNOME Remote Desktop...
Apr 24 12:29:36 unmatched (p-daemon)[1756]: gnome-remote-desktop.service:
Failed to determine user credentials: No such process
Apr 24 12:29:36 unmatched systemd[1]: gnome-remote-desktop.service: Main
process exited, code=exited, status=217/USER
Apr 24 12:29:36 unmatched systemd[1]: gnome-remote-desktop.service: Failed with
result 'exit-code'.
Apr 24 12:29:36 unmatched systemd[1]: Failed to start
gnome-remote-desktop.service - GNOME Remote Desktop.
Apr 24 12:29:36 unmatched systemd[1]: gnome-remote-desktop.service: Scheduled
restart job, restart counter is at 5.
Apr 24 12:29:36 unmatched systemd[1]: gnome-remote-desktop.service: Start
request repeated too quickly.
Apr 24 12:29:36 unmatched systemd[1]: gnome-remote-desktop.service: Failed with
result 'exit-code'.
Apr 24 12:29:36 unmatched systemd[1]: Failed to start
gnome-remote-desktop.service - GNOME Remote Desktop.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: gnome-remote-desktop 46.1-1
ProcVersionSignature: Ubuntu 6.8.0-31.31.1-generic 6.8.1
Uname: Linux 6.8.0-31-generic riscv64
ApportVersion: 2.28.1-0ubuntu2
Architecture: riscv64
CasperMD5json:
{
"result": "skip"
}
Date: Wed Apr 24 12:34:26 2024
InstallationDate: Installed on 2024-04-24 (0 days ago)
InstallationMedia: Ubuntu-Server 24.04 LTS "Noble Numbat" - Release riscv64
(20240423)
SourcePackage: gnome-remote-desktop
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: gnome-remote-desktop (Ubuntu)
Importance: Undecided
Status: New
** Tags: apport-bug noble riscv64
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-remote-desktop in Ubuntu.
https://bugs.launchpad.net/bugs/206
Title:
gnome-remote-desktop.service: Failed to determine user credentials: No
such process
Status in gnome-remote-desktop package in Ubuntu:
New
Bug description:
On a RISC-V Ubuntu 24.04 I installed ubuntu-desktop.
The desktop
[Desktop-packages] [Bug 2056434] Re: Thunderbird profile not migrated to snap
Hello: Thunderbird still does not migrate my profile. My system works fine after ``` apt remove thunderbird snap remove thunderbird dpkg -i ~/software/thunderbird_115.9.0+build1-0ubuntu0.22.04.1_amd64.deb ``` but thunderbird gets updated every day (unattended-upgrades?, snap refresh?) and starts fresh, ignoring my profile. I have tried to delete the ~/snap/thunderbird folder, but it still does not migrate the profile correctly. Any ideas? Regards! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/2056434 Title: Thunderbird profile not migrated to snap Status in thunderbird package in Ubuntu: Fix Released Bug description: Today's update installed the thunderbird snap and removed the thunderbird binary but it did not migrate my thunderbird profile. Now I don't have access to any old mails anymore. Looking at ~/.thunderbird: $ cat profiles.ini [Profile1] Name=default IsRelative=1 Path=ao6t0qef.default Default=1 [InstallFDC34C9F024745EB] Default=ji04wv64.default-release Locked=1 [Profile0] Name=default-release IsRelative=1 Path=ji04wv64.default-release [General] StartWithLastProfile=1 Version=2 ji04wv64.default-release is the folder that should have been migrated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/2056434/+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 2053289] Re: Internal microphone realtek ALC257 is not working in 24.04 Noble (Fujitsu WU4/H1)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: alsa-driver (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/2053289 Title: Internal microphone realtek ALC257 is not working in 24.04 Noble (Fujitsu WU4/H1) Status in alsa-driver package in Ubuntu: Confirmed Bug description: I tried to record sound with my internal Mic. Nothing is working. I use arecord. ``` bagus:~$ arecord test.wav arecord: main:834: audio open error: Operation not supported bagus:~$ arecord -d 10 -f cd -t wav -D copy foobar.wav ALSA lib pcm.c:2675:(snd_pcm_open_noupdate) Unknown PCM copy arecord: main:834: audio open error: No such file or directory bagus:~$ arecord -l List of CAPTURE Hardware Devices card 0: sofhdadsp [sof-hda-dsp], device 0: HDA Analog (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: sofhdadsp [sof-hda-dsp], device 6: DMIC (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: sofhdadsp [sof-hda-dsp], device 7: DMIC16kHz (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 bagus:~$ lsb_release -rd No LSB modules are available. Description: Ubuntu Noble Numbat (development branch) Release: 24.04 bagus:~$ apt-cache policy alsa-base alsa-base: Installed: (none) Candidate: 1.0.25+dfsg-0ubuntu7 Version table: 1.0.25+dfsg-0ubuntu7 500 500 http://archive.ubuntu.com/ubuntu noble/main amd64 Packages ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2053289/+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 2059847] Re: Input lag or freezes on Nvidia desktops with X11 after logging "MetaSyncRing: Sync object is not ready -- were events handled properly?"
Thanks - this fix appears to have resolved my lag issues. OS: Ubuntu 22.04.04 LTS $XDG_SESSION_TYPE: x11 nVidia: 535.171.04 Mobo/CPU: MSI MAG B550M BAZOOKA / AMD Ryzen 5 5600X Video card: MSI GeForce GT1030 2GB PCI Express Mostly this was affecting Gnome terminal for me, but just prior to applying this patch (thanks again!!) I used GnuCash and that lagged too. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2059847 Title: Input lag or freezes on Nvidia desktops with X11 after logging "MetaSyncRing: Sync object is not ready -- were events handled properly?" Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Jammy: In Progress Status in mutter source package in Mantic: In Progress Status in mutter source package in Noble: Fix Released Bug description: [ Impact ] Input or the entire screen may freeze at times on systems using the Nvidia Xorg driver with GNOME. [ Test Plan ] 0. Set up a desktop with Nvidia driver 545 or 550. 1. Log into Ubuntu, ensuring it's a Xorg session. 2. Open a Terminal, resize it vigorously, and type several lines of text. 3. Run: journalctl -b0 | grep MetaSyncRing 4. Verify the above command does NOT show "MetaSyncRing" messages such as: Window manager warning: MetaSyncRing: Sync object is not ready -- were events handled properly? Window manager warning: MetaSyncRing: Sync object is not ready -- were events handled properly? Window manager warning: MetaSyncRing: Sync object is not ready -- were events handled properly? Window manager warning: MetaSyncRing: Too many reboots -- disabling [ Where problems could occur ] Anywhere in Nvidia (proprietary driver) Xorg sessions since the code being modified is only used with that driver. [ Original Description ] There is a noticeable delay in input while using the native terminal. I belive it was caused by a recent software update, as this issue is relatively new. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia wl ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Mar 30 19:57:13 2024 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- InstallationDate: Installed on 2024-03-30 (0 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220) SourcePackage: ubiquity Symptom: installation UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2059847/+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 2061882] Re: Thunderbird snap loses local folder settings in 24.04
Well the snap is supposed to import my previous profile - it does not. I tied to point my local directory (under account settings) to the old location - this does not work. The email is supposed to work - it does not. I deleted my profile, reconfigured the mail - it still does not work. I can send mails but I cannot receive any. I can only see my account name but I cannot see my Inbox folder etc. I cannot revert back to the deb version - so I "reverted" back to Debian. (And I have been using Ubuntu since Warty so that is 20 years) but not having mail is kinda a deal breaker for me. I may give 24.04.2 a go - but I will thoroughly test everything from the live install before installing. Off topic there are other issues, which I filed bugs for. (Filezilla crashing, RDP crashing, boot not working so don't feel bad) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/2061882 Title: Thunderbird snap loses local folder settings in 24.04 Status in thunderbird package in Ubuntu: Invalid Bug description: After Thunderbird snap installs the local folders do not import from the deb Thunderbird. There also seems to be no way to get back to the deb version. I needed to manually move the local directory back to the original. I can no longer see my inbox and it keeps telling me that the /home/me/snap/thunderbird/hdd/home/me/.thunderbird/24a1u6qp.default/ImapMail/ is invalid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/2061882/+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 2061882] Re: Thunderbird snap loses local folder settings in 24.04
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/2061882 Title: Thunderbird snap loses local folder settings in 24.04 Status in thunderbird package in Ubuntu: Invalid Bug description: After Thunderbird snap installs the local folders do not import from the deb Thunderbird. There also seems to be no way to get back to the deb version. I needed to manually move the local directory back to the original. I can no longer see my inbox and it keeps telling me that the /home/me/snap/thunderbird/hdd/home/me/.thunderbird/24a1u6qp.default/ImapMail/ is invalid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/2061882/+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 2063323] [NEW] Crash Connecting to RDP with FreeRDP 3.5.0 and Remmina (24.04)
Public bug reported: Core dumps with: [freerdp_settings_get_bool]: Invalid key index 0 [FreeRDP_instance|FREERDP_SETTINGS_TYPE_POINTER] Seems there is a fix here: https://gitlab.com/Remmina/Remmina/-/issues/3090 ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: remmina 1.4.35+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Apr 24 12:13:39 2024 SourcePackage: remmina UpgradeStatus: Upgraded to noble on 2024-04-23 (1 days ago) modified.conffile..etc.logrotate.d.apport: [modified] mtime.conffile..etc.logrotate.d.apport: 2023-06-10T11:09:46.502839 ** Affects: remmina (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble third-party-packages wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to remmina in Ubuntu. https://bugs.launchpad.net/bugs/2063323 Title: Crash Connecting to RDP with FreeRDP 3.5.0 and Remmina (24.04) Status in remmina package in Ubuntu: New Bug description: Core dumps with: [freerdp_settings_get_bool]: Invalid key index 0 [FreeRDP_instance|FREERDP_SETTINGS_TYPE_POINTER] Seems there is a fix here: https://gitlab.com/Remmina/Remmina/-/issues/3090 ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: remmina 1.4.35+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Apr 24 12:13:39 2024 SourcePackage: remmina UpgradeStatus: Upgraded to noble on 2024-04-23 (1 days ago) modified.conffile..etc.logrotate.d.apport: [modified] mtime.conffile..etc.logrotate.d.apport: 2023-06-10T11:09:46.502839 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/2063323/+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 2058514] Re: System crashes/freezes when suspending
Still having this problem on 24.04 LTS with the latest upgrades. It happens rarely, systemctl -b -1 says: Apr 24 10:43:50 ThinkPad-P14s-Gen-3 systemd-logind[1171]: Lid closed. Apr 24 10:43:50 ThinkPad-P14s-Gen-3 systemd-logind[1171]: Suspending... Apr 24 10:43:50 ThinkPad-P14s-Gen-3 kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Apr 24 10:43:50 ThinkPad-P14s-Gen-3 kernel: audit: type=1107 audit(1713948230.548:853): pid=1144 uid=101 auid=4294967295 ses=4294967295 subj=unconfined msg='apparmor="DENIED" operatio> exe="/usr/bin/dbus-daemon" sauid=101 hostname=? addr=? terminal=?' Apr 24 10:43:50 ThinkPad-P14s-Gen-3 ModemManager[1373]: [sleep-monitor-systemd] system is about to suspend Apr 24 10:43:50 ThinkPad-P14s-Gen-3 NetworkManager[1209]: [1713948230.5501] manager: sleep: sleep requested (sleeping: no enabled: yes) Apr 24 10:43:50 ThinkPad-P14s-Gen-3 kernel: audit: type=1107 audit(1713948230.549:854): pid=1144 uid=101 auid=4294967295 ses=4294967295 subj=unconfined msg='apparmor="DENIED" operatio> exe="/usr/bin/dbus-daemon" sauid=101 hostname=? addr=? terminal=?' Apr 24 10:43:50 ThinkPad-P14s-Gen-3 NetworkManager[1209]: [1713948230.5503] manager: NetworkManager state is now ASLEEP Apr 24 10:43:50 ThinkPad-P14s-Gen-3 NetworkManager[1209]: [1713948230.5506] device (wlp1s0): state change: activated -> deactivating (reason 'sleeping', sys-iface-state: 'mana> Apr 24 10:43:50 ThinkPad-P14s-Gen-3 dbus-daemon[1144]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' > Apr 24 10:43:50 ThinkPad-P14s-Gen-3 kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Apr 24 10:43:50 ThinkPad-P14s-Gen-3 kernel: audit: type=1107 audit(1713948230.556:855): pid=1144 uid=101 auid=4294967295 ses=4294967295 subj=unconfined msg='apparmor="DENIED" operatio> exe="/usr/bin/dbus-daemon" sauid=101 hostname=? addr=? terminal=?' Apr 24 10:43:50 ThinkPad-P14s-Gen-3 kernel: audit: type=1107 audit(1713948230.556:856): pid=1144 uid=101 auid=4294967295 ses=4294967295 subj=unconfined msg='apparmor="DENIED" operatio> exe="/usr/bin/dbus-daemon" sauid=101 hostname=? addr=? terminal=?' Apr 24 10:43:50 ThinkPad-P14s-Gen-3 kernel: audit: type=1107 audit(1713948230.557:857): pid=1144 uid=101 auid=4294967295 ses=4294967295 subj=unconfined msg='apparmor="DENIED" operatio> exe="/usr/bin/dbus-daemon" sauid=101 hostname=? addr=? terminal=?' Apr 24 10:43:50 ThinkPad-P14s-Gen-3 kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Apr 24 10:43:50 ThinkPad-P14s-Gen-3 kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Apr 24 10:43:50 ThinkPad-P14s-Gen-3 systemd[1]: Starting NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service... Apr 24 10:43:50 ThinkPad-P14s-Gen-3 kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Apr 24 10:43:50 ThinkPad-P14s-Gen-3 kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Apr 24 10:43:50 ThinkPad-P14s-Gen-3 dbus-daemon[1144]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' Apr 24 10:43:50 ThinkPad-P14s-Gen-3 systemd[1]: Started NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service. Apr 24 10:43:50 ThinkPad-P14s-Gen-3 kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Apr 24 10:43:50 ThinkPad-P14s-Gen-3 kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Apr 24 10:43:50 ThinkPad-P14s-Gen-3 kernel: audit: type=1107 audit(1713948230.619:858): pid=1144 uid=101 auid=4294967295 ses=4294967295 subj=unconfined msg='apparmor="DENIED" operatio> exe="/usr/bin/dbus-daemon" sauid=101 hostname=? addr=? terminal=?' Apr 24 10:43:50 ThinkPad-P14s-Gen-3 kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Apr 24 10:43:50 ThinkPad-P14s-Gen-3 kernel: wlp1s0: deauthenticating from ba:09:f7:80:71:c9 by local choice (Reason: 3=DEAUTH_LEAVING) Apr 24 10:43:50 ThinkPad-P14s-Gen-3 gnome-shell[3172]: Failed to create new MetaSelectionSourceMemory: Failed to create MetaAnonymousFile Apr 24 10:43:50 ThinkPad-P14s-Gen-3 gnome-shell[3172]: Failed to create new MetaSelectionSourceMemory: Failed to create MetaAnonymousFile Apr 24 10:43:50 ThinkPad-P14s-Gen-3 wpa_supplicant[1211]: wlp1s0: CTRL-EVENT-DISCONNECTED bssid=ba:09:f7:80:71:c9 reason=3 locally_generated=1 Apr 24 10:43:50 ThinkPad-P14s-Gen-3 wpa_supplicant[1211]: wlp1s0: CTRL-EVENT-DSCP-POLICY clear_all Apr 24 10:43:50
[Desktop-packages] [Bug 2063153] Re: Incorrect display Graphics Card in System -> system details
Thank you for your bug report, what's the output of $ switcherooctl on your system? ** Package changed: ubuntu => switcheroo-control (Ubuntu) ** Changed in: switcheroo-control (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to switcheroo-control in Ubuntu. https://bugs.launchpad.net/bugs/2063153 Title: Incorrect display Graphics Card in System -> system details Status in switcheroo-control package in Ubuntu: Incomplete Bug description: NVIDIA GeForce RTX 3050 Ti Mobile should be displayed here To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/switcheroo-control/+bug/2063153/+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 2063153] [NEW] Incorrect display Graphics Card in System -> system details
You have been subscribed to a public bug: NVIDIA GeForce RTX 3050 Ti Mobile should be displayed here ** Affects: switcheroo-control (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: bot-comment -- Incorrect display Graphics Card in System -> system details https://bugs.launchpad.net/bugs/2063153 You received this bug notification because you are a member of Desktop Packages, which is subscribed to switcheroo-control in Ubuntu. -- 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 2057835] Re: migration to snap broke openpgp; no private key found
Do you have any apparmor denial in the journal? How did you configure you key signing? ** Changed in: thunderbird (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/2057835 Title: migration to snap broke openpgp; no private key found Status in thunderbird package in Ubuntu: Incomplete Bug description: This means that it keeps complaining when trying to save emails to drafts, also the openpgp settings show that the private key can't be found. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/2057835/+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 2061918] Re: package thunderbird 2:1snap1-0ubuntu1 failed to install/upgrade: new thunderbird package pre-installation script subprocess returned error exit status 1
The initial problem should have addressed at the archive level where we removed the transitional libglib2.0-0 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/2061918 Title: package thunderbird 2:1snap1-0ubuntu1 failed to install/upgrade: new thunderbird package pre-installation script subprocess returned error exit status 1 Status in thunderbird package in Ubuntu: Confirmed Bug description: This happened during an upgrade from Mantic to Noble. ProblemType: Package DistroRelease: Ubuntu 24.04 Package: thunderbird 2:1snap1-0ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset wl nvidia zfs ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue Apr 16 13:15:42 2024 ErrorMessage: new thunderbird package pre-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2018-08-10 (2076 days ago) InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Python3Details: /usr/bin/python3.12, Python 3.12.3, python3-minimal, 3.12.3-0ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.22.6ubuntu6 apt 2.7.14build2 SnapChanges: IDStatus Spawn Ready Summary 3563 Error 2024-04-16T13:15:26-07:00 2024-04-16T13:15:42-07:00 Install "thunderbird" snap 3564 Done2024-04-16T13:22:00-07:00 2024-04-16T13:22:09-07:00 Install "thunderbird" snap SourcePackage: thunderbird Title: package thunderbird 2:1snap1-0ubuntu1 failed to install/upgrade: new thunderbird package pre-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to noble on 2024-04-16 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/2061918/+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 2060900] Re: gst-plugin-scanner crashed with SIGABRT in __assert_fail_base()
** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/2060900 Title: gst-plugin-scanner crashed with SIGABRT in __assert_fail_base() Status in gstreamer1.0 package in Ubuntu: New Bug description: this give me error from some files ProblemType: Crash DistroRelease: Ubuntu 24.04 Package: libgstreamer1.0-0 1.24.1-1build1 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Apr 11 11:07:09 2024 ExecutablePath: /usr/lib/x86_64-linux-gnu/gstreamer1.0/gstreamer-1.0/gst-plugin-scanner InstallationDate: Installed on 2024-04-04 (7 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240323) ProcCmdline: /usr/lib/x86_64-linux-gnu/../../lib/x86_64-linux-gnu/gstreamer1.0/gstreamer-1.0/gst-plugin-scanner -l /usr/bin/rhythmbox ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RebootRequiredPkgs: Error: path contained symlinks. Signal: 6 SignalName: SIGABRT SourcePackage: gstreamer1.0 StacktraceTop: __assert_fail_base (fmt=0x702a92dd01e8 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=assertion@entry=0x702a7b4e1c90 "subsampling == SUBSAMPLE_YUV420 || subsampling == SUBSAMPLE_YUV422H || subsampling == SUBSAMPLE_YUV422V || subsampling == SUBSAMPLE_RGBX", file=file@entry=0x702a7b4e44b6 "i965_drv_video.c", line=line@entry=4653, function=function@entry=0x702a7b511600 "i965_check_alloc_surface_bo") at ./assert/assert.c:94 __assert_fail (assertion=0x702a7b4e1c90 "subsampling == SUBSAMPLE_YUV420 || subsampling == SUBSAMPLE_YUV422H || subsampling == SUBSAMPLE_YUV422V || subsampling == SUBSAMPLE_RGBX", file=0x702a7b4e44b6 "i965_drv_video.c", line=4653, function=0x702a7b511600 "i965_check_alloc_surface_bo") at ./assert/assert.c:103 ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so vaCreateSurfaces () from /lib/x86_64-linux-gnu/libva.so.2 Title: gst-plugin-scanner crashed with SIGABRT in __assert_fail_base() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/2060900/+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 2062949] Re: gnome-remote-desktop-daemon crashed with SIGSEGV in g_main_context_iteration()
Thank you for your report! However, processing it in order to get sufficient information for the developers failed as the report has a core dump which is invalid. The corruption may have happened on the system which the crash occurred or during transit. Thank you for your understanding, and sorry for the inconvenience! ** Changed in: gnome-remote-desktop (Ubuntu) Status: New => Invalid ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/2062949/+attachment/5768431/+files/CoreDump.gz ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-remote-desktop in Ubuntu. https://bugs.launchpad.net/bugs/2062949 Title: gnome-remote-desktop-daemon crashed with SIGSEGV in g_main_context_iteration() Status in gnome-remote-desktop package in Ubuntu: Invalid Bug description: In 24.04, attempting to launch into a Remote Login RDP session (which uses the wayland compositor) with an Nvidia GPU connected on the host gives a black screen. The purpose of having the GPU is to provide HW acceleration to gnome-remote-desktop on the host (the RDP host is a 24.04 VM.) The Nvidia GPU does not have a display adapter, therefore a dummy adapter cannot be used to fool the machine into believing there is a monitor attached. The Remote Login session is only black screen if the Nvidia GPU is attached. When the RDP client (I am using the standard Remote Desktop connection client on a Windows 10 device) logs out from gnome-remote-desktop, both grd and gnome-shell crash with SIGSEGV. In Ubuntu version 22.04, attaching a Nvidia GPU to the 22.04 host VM and launching a gnome-remote-desktop on "Ubuntu on Wayland" did not cause a crash or any black screens, and the RDP instance had fully supported HW acceleration for the desktop. ProblemType: Crash DistroRelease: Ubuntu 24.04 Package: gnome-remote-desktop 46.1-1 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Apr 19 00:29:37 2024 ExecutablePath: /usr/libexec/gnome-remote-desktop-daemon InstallationDate: Installed on 2024-04-18 (1 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240410.2) ProcCmdline: /usr/libexec/gnome-remote-desktop-daemon --system ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SegvAnalysis: Segfault happened at: 0x76f9b13c9a11:cmpq $0x0,0x18(%rax) PC (0x76f9b13c9a11) ok source "$0x0" ok destination "0x18(%rax)" (0x0018) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SignalName: SIGSEGV SourcePackage: gnome-remote-desktop StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_application_run () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: gnome-remote-desktop-daemon crashed with SIGSEGV in g_main_context_iteration() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/2062949/+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 2060693] Re: No welcome/login sound on Ubuntu desktop
If it's specific to raspi is it maybe the same problem than bug #2063255? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libcanberra in Ubuntu. https://bugs.launchpad.net/bugs/2060693 Title: No welcome/login sound on Ubuntu desktop Status in libcanberra package in Ubuntu: New Bug description: Under the Ubuntu desktop for Raspberry Pi, for several recent releases, the startup sound from the Yaru sound theme has failed to play both at the initial setup (from oem-config, where it used to play just before language selection), and at the greeter. This worked in Jammy (22.04), but on at least mantic (23.10) and the forthcoming noble (24.04) (and possibly earlier), this has failed. It's not due to a crash in canberra-gtk-play (used to play the sound). The only hint that something has failed appears in the oem-config.log: Failed to play sound: Not available Unfortunately there's nothing else in the log that hints at why canberra-gtk-play is failing. There are several similar bug report, but I doubt they are related given their age (e.g. LP: #1002114 relates to ubuntu 12.04 which had a very different sound stack and predates the preinstalled desktop images). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcanberra/+bug/2060693/+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 2054868] Re: invalid escape sequence
*** This bug is a duplicate of bug 2029480 ***
https://bugs.launchpad.net/bugs/2029480
** This bug has been marked a duplicate of bug 2029480
SyntaxWarnings with Python3.12
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to hplip in Ubuntu.
https://bugs.launchpad.net/bugs/2054868
Title:
invalid escape sequence
Status in hplip package in Ubuntu:
Confirmed
Bug description:
Todays update with python 3.12
/usr/share/hplip/base/LedmWifi.py:34: SyntaxWarning: invalid escape sequence
'\d
'
http_result_pat = re.compile("""HTTP/\d.\d\s(\d+)""", re.I)
/usr/share/hplip/base/device.py:49: SyntaxWarning: invalid escape sequence
'\d'
http_result_pat = re.compile("""HTTP/\d.\d\s(\d+)""", re.I)
/usr/share/hplip/base/g.py:304: SyntaxWarning: invalid escape sequence '\|'
spinner = "\|/-\|/-"
/usr/share/hplip/base/g.py:354: SyntaxWarning: invalid escape sequence '\d'
m = re.search('python(\d(\.\d){0,2})', ext_path)#get the python
ve
rsion where the .so file is found
/usr/share/hplip/base/imagesize.py:186: SyntaxWarning: invalid escape
sequence '
\#'
re.compile('\#define\s+\S+\s+\d+') : ('image/x-xbitmap', xbmsize),
/usr/share/hplip/base/imagesize.py:187: SyntaxWarning: invalid escape
sequence '
\/'
re.compile('\/\* XPM \*\/'): ('image/x-xpixmap', xpmsize),
/usr/share/hplip/base/imagesize.py:189: SyntaxWarning: invalid escape
sequence '
\*'
re.compile('^II\*\x00'): ('image/tiff', tiffsize),
/usr/share/hplip/base/logger.py:439: SyntaxWarning: invalid escape sequence
'\<'
elem_start = re.findall("(\<\W{0,1}\w+) ?", line)[0]
/usr/share/hplip/base/logger.py:440: SyntaxWarning: invalid escape sequence
'\]'
elem_finished = re.findall("([?|\]\]]*\>)", line)[0]
/usr/share/hplip/base/logger.py:442: SyntaxWarning: invalid escape sequence
'\S'
attrs = re.findall("(\S*?\=\".*?\")", line)
/usr/share/hplip/base/models.py:37: SyntaxWarning: invalid escape sequence
'\d'
pat_prod_num = re.compile("""(\d+)""", re.I)
/usr/share/hplip/base/models.py:428: SyntaxWarning: invalid escape sequence
'\d'
re.compile('^r(\d+)-agent(\d+)-kind', re.IGNORECASE) : TYPE_INT,
/usr/share/hplip/base/models.py:429: SyntaxWarning: invalid escape sequence
'\d'
re.compile('^r(\d+)-agent(\d+)-type', re.IGNORECASE) : TYPE_INT,
/usr/share/hplip/base/models.py:430: SyntaxWarning: invalid escape sequence
'\d'
re.compile('^r(\d+)-agent(\d+)-sku', re.IGNORECASE) : TYPE_STR,
/usr/share/hplip/base/models.py:431: SyntaxWarning: invalid escape sequence
'\d'
re.compile('^agent(\d+)-desc', re.IGNORECASE) : TYPE_STR,
/usr/share/hplip/base/models.py:432: SyntaxWarning: invalid escape sequence
'\d'
re.compile('^agent(\d+)-virgin', re.IGNORECASE) : TYPE_BOOL,
/usr/share/hplip/base/models.py:433: SyntaxWarning: invalid escape sequence
'\d'
re.compile('^agent(\d+)-dvc', re.IGNORECASE) : TYPE_INT,
/usr/share/hplip/base/models.py:434: SyntaxWarning: invalid escape sequence
'\d'
re.compile('^agent(\d+)-kind', re.IGNORECASE) : TYPE_INT,
/usr/share/hplip/base/models.py:435: SyntaxWarning: invalid escape sequence
'\d'
re.compile('^agent(\d+)-type', re.IGNORECASE) : TYPE_INT,
/usr/share/hplip/base/models.py:436: SyntaxWarning: invalid escape sequence
'\d'
re.compile('^agent(\d+)-id', re.IGNORECASE) : TYPE_INT,
/usr/share/hplip/base/models.py:437: SyntaxWarning: invalid escape sequence
'\d'
re.compile('^agent(\d+)-hp-ink', re.IGNORECASE) : TYPE_BOOL,
/usr/share/hplip/base/models.py:438: SyntaxWarning: invalid escape sequence
'\d'
re.compile('^agent(\d+)-health-desc', re.IGNORECASE) : TYPE_STR,
/usr/share/hplip/base/models.py:439: SyntaxWarning: invalid escape sequence
'\d'
re.compile('^agent(\d+)-health$', re.IGNORECASE) : TYPE_INT,
/usr/share/hplip/base/models.py:440: SyntaxWarning: invalid escape sequence
'\d'
re.compile('^agent(\d+)-known', re.IGNORECASE) : TYPE_BOOL,
/usr/share/hplip/base/models.py:441: SyntaxWarning: invalid escape sequence
'\d'
re.compile('^agent(\d+)-level', re.IGNORECASE) : TYPE_INT,
/usr/share/hplip/base/models.py:442: SyntaxWarning: invalid escape sequence
'\d'
re.compile('^agent(\d+)-ack', re.IGNORECASE) : TYPE_BOOL,
/usr/share/hplip/base/models.py:443: SyntaxWarning: invalid escape sequence
'\d'
re.compile('^agent(\d+)-sku', re.IGNORECASE) : TYPE_STR,
/usr/share/hplip/base/models.py:444: SyntaxWarning: invalid escape sequence
'\d'
re.compile('^in-tray(\d+)', re.IGNORECASE) : TYPE_BOOL,
/usr/share/hplip/base/models.py:445: SyntaxWarning: invalid escape sequence
'\d'
re.compile('^out-tray(\d+)', re.IGNORECASE) : TYPE_BOOL,
/usr/share/hplip/base/models.py:446: SyntaxWarning: invalid escape sequence
'\d'
re.compile('^model(\d+)', re.IGNORECASE) : TYPE_STR,
/usr/share/hplip/base/password.py:212: SyntaxWarning: invalid escape
[Desktop-packages] [Bug 2062967] Re: ubuntu-drivers no longer offers nvidia 550 drivers
Agreed. I recently installed Ubuntu 23.10 after some absence and the first thing noted is the Nvidia drivers 535 are the default / tested version in the preinstalled driver tool app, and while that's fine, the newer version 550 is missing completely. Please add 550 both the proprietary and as open kernel module. IIRC on Ubuntu 22.04.4 version 550 open was available but only as a server edition (or was it 23.10?). In addition, please make sure that switching between graphic drivers via the driver tool is safe. I say this because I was switching back and forth between Ubuntu LTS and 23.10 for testing purposes (separate hard drives), and the last time I switched to 545 via the driver tool app, it showed me an error window without error message and wouldn't install. After a reboot Ubuntu just freezed with a blinking cursor. Now I read what Jack posted above and understand why this is happening, but a normal user just wanting to switch drivers won't understand what's going on. This isn't the first time these things happen either. GPU: Nvidia RTX A2000 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/2062967 Title: ubuntu-drivers no longer offers nvidia 550 drivers Status in ubuntu-drivers-common package in Ubuntu: Confirmed Bug description: While I am unclear which package update impacted the video drivers detected by ubuntu-drivers, the nvidia 545 and nvidia 550 video drivers are no longer shown as an option on NVIDIA GeForce GTX 1050 video card. I can understand the removal of the nvidia 545 drivers as the current kernel's linux-signatures-nvidia-6.8.0-28-generic package lacks signatures for the nvidia 545 kernel modules for secure boot but the nvidia 550 kernel modules signatures are available. So while it would be acceptable to downgrade the 'tested' default nvidia driver to 535, ubuntu-drivers and Additional Drivers should be offering the nvidia 550 drivers as an untested option. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/2062967/+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 1926863] Re: gjs process (desktop-icons-ng extension) eats all available RAM and Freezes Computer
Thank you for reporting this bug to Ubuntu. Ubuntu 23.04 (lunar) reached end-of-life on January 25, 2024. Ubuntu 21.04 (hirsute) reached end-of-life on January 20, 2022. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it anymore. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in. ** Changed in: gnome-shell-extension-desktop-icons-ng (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons-ng in Ubuntu. https://bugs.launchpad.net/bugs/1926863 Title: gjs process (desktop-icons-ng extension) eats all available RAM and Freezes Computer Status in Gnome Shell Extension Desktop Icons Ng: New Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: Won't Fix Bug description: Title sums it up. Just upgraded to 21.04 from 20.10, and gjs has now three times eaten all memory and frozen the everything solid. Some sort of massive memory leak. I caught a screenshot of it doing it, ticks up about 1/10th GB every few seconds until computer goes bye-bye. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gjs 1.67.2-2ubuntu1 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: unknown CurrentDesktop: ubuntu:GNOME Date: Sat May 1 19:22:11 2021 InstallationDate: Installed on 2020-05-07 (359 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gjs UpgradeStatus: Upgraded to hirsute on 2021-05-01 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons-ng/+bug/1926863/+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 2063312] Re: gjs error restart show icon desktop
This is recurring in the log. I wonder if there are more Desktop files than it can handle: [ 4576.663765] u-hcm-dkp-026 gnome-shell[2229]: DING: (gjs:23000): GLib-ERROR **: 08:05:34.803: Creating pipes for GWakeup: Too many open files [ 4579.212965] u-hcm-dkp-026 gnome-shell[2229]: DING: Detected async api for thumbnails [ 4579.267543] u-hcm-dkp-026 gnome-shell[2229]: DING: GNOME nautilus 42.6 [ 4581.476956] u-hcm-dkp-026 gnome-shell[2229]: DING: (gjs:23081): GLib-ERROR **: 08:05:39.617: Creating pipes for GWakeup: Too many open files [ 4583.855992] u-hcm-dkp-026 gnome-shell[2229]: DING: Detected async api for thumbnails [ 4583.910279] u-hcm-dkp-026 gnome-shell[2229]: DING: GNOME nautilus 42.6 [ 4591.667699] u-hcm-dkp-026 gnome-shell[2229]: DING: (gjs:23118): GLib-ERROR **: 08:05:49.807: Creating pipes for GWakeup: Too many open files [ 4594.203465] u-hcm-dkp-026 gnome-shell[2229]: DING: Detected async api for thumbnails [ 4594.274686] u-hcm-dkp-026 gnome-shell[2229]: DING: GNOME nautilus 42.6 ** Package changed: gnome-shell (Ubuntu) => gnome-shell-extension- desktop-icons-ng (Ubuntu) -- 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/2063312 Title: gjs error restart show icon desktop Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: New Bug description: There is a bug when I start my computer. After 2 seconds, the icon on the desktop is not show and shows again. I checked the CPU% processes is max in CPU 3 over 100%. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.9-0ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-28.29~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-28-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 24 15:16:23 2024 DisplayManager: gdm3 InstallationDate: Installed on 2023-03-28 (392 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) RelatedPackageVersions: mutter-common 42.9-0ubuntu7 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons-ng/+bug/2063312/+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 2062967] Re: ubuntu-drivers no longer offers nvidia 550 drivers
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-drivers-common (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/2062967 Title: ubuntu-drivers no longer offers nvidia 550 drivers Status in ubuntu-drivers-common package in Ubuntu: Confirmed Bug description: While I am unclear which package update impacted the video drivers detected by ubuntu-drivers, the nvidia 545 and nvidia 550 video drivers are no longer shown as an option on NVIDIA GeForce GTX 1050 video card. I can understand the removal of the nvidia 545 drivers as the current kernel's linux-signatures-nvidia-6.8.0-28-generic package lacks signatures for the nvidia 545 kernel modules for secure boot but the nvidia 550 kernel modules signatures are available. So while it would be acceptable to downgrade the 'tested' default nvidia driver to 535, ubuntu-drivers and Additional Drivers should be offering the nvidia 550 drivers as an untested option. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/2062967/+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 2063312] [NEW] gjs error restart show icon desktop
Public bug reported: There is a bug when I start my computer. After 2 seconds, the icon on the desktop is not show and shows again. I checked the CPU% processes is max in CPU 3 over 100%. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.9-0ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-28.29~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-28-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 24 15:16:23 2024 DisplayManager: gdm3 InstallationDate: Installed on 2023-03-28 (392 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) RelatedPackageVersions: mutter-common 42.9-0ubuntu7 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session ** Attachment added: "Screenshot from 2024-04-24 15-21-38.png" https://bugs.launchpad.net/bugs/2063312/+attachment/5769969/+files/Screenshot%20from%202024-04-24%2015-21-38.png -- 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/2063312 Title: gjs error restart show icon desktop Status in gnome-shell package in Ubuntu: New Bug description: There is a bug when I start my computer. After 2 seconds, the icon on the desktop is not show and shows again. I checked the CPU% processes is max in CPU 3 over 100%. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.9-0ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-28.29~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-28-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 24 15:16:23 2024 DisplayManager: gdm3 InstallationDate: Installed on 2023-03-28 (392 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) RelatedPackageVersions: mutter-common 42.9-0ubuntu7 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2063312/+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 2057835] Re: migration to snap broke openpgp; no private key found
I have snapd snap installed, so this is not a dupe of the other bug ** This bug is no longer a duplicate of bug 2056458 upgrade to thunderbird snap, missing snapd depdency -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/2057835 Title: migration to snap broke openpgp; no private key found Status in thunderbird package in Ubuntu: New Bug description: This means that it keeps complaining when trying to save emails to drafts, also the openpgp settings show that the private key can't be found. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/2057835/+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 2054868] Re: invalid escape sequence
** Changed in: hplip (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to hplip in Ubuntu.
https://bugs.launchpad.net/bugs/2054868
Title:
invalid escape sequence
Status in hplip package in Ubuntu:
Confirmed
Bug description:
Todays update with python 3.12
/usr/share/hplip/base/LedmWifi.py:34: SyntaxWarning: invalid escape sequence
'\d
'
http_result_pat = re.compile("""HTTP/\d.\d\s(\d+)""", re.I)
/usr/share/hplip/base/device.py:49: SyntaxWarning: invalid escape sequence
'\d'
http_result_pat = re.compile("""HTTP/\d.\d\s(\d+)""", re.I)
/usr/share/hplip/base/g.py:304: SyntaxWarning: invalid escape sequence '\|'
spinner = "\|/-\|/-"
/usr/share/hplip/base/g.py:354: SyntaxWarning: invalid escape sequence '\d'
m = re.search('python(\d(\.\d){0,2})', ext_path)#get the python
ve
rsion where the .so file is found
/usr/share/hplip/base/imagesize.py:186: SyntaxWarning: invalid escape
sequence '
\#'
re.compile('\#define\s+\S+\s+\d+') : ('image/x-xbitmap', xbmsize),
/usr/share/hplip/base/imagesize.py:187: SyntaxWarning: invalid escape
sequence '
\/'
re.compile('\/\* XPM \*\/'): ('image/x-xpixmap', xpmsize),
/usr/share/hplip/base/imagesize.py:189: SyntaxWarning: invalid escape
sequence '
\*'
re.compile('^II\*\x00'): ('image/tiff', tiffsize),
/usr/share/hplip/base/logger.py:439: SyntaxWarning: invalid escape sequence
'\<'
elem_start = re.findall("(\<\W{0,1}\w+) ?", line)[0]
/usr/share/hplip/base/logger.py:440: SyntaxWarning: invalid escape sequence
'\]'
elem_finished = re.findall("([?|\]\]]*\>)", line)[0]
/usr/share/hplip/base/logger.py:442: SyntaxWarning: invalid escape sequence
'\S'
attrs = re.findall("(\S*?\=\".*?\")", line)
/usr/share/hplip/base/models.py:37: SyntaxWarning: invalid escape sequence
'\d'
pat_prod_num = re.compile("""(\d+)""", re.I)
/usr/share/hplip/base/models.py:428: SyntaxWarning: invalid escape sequence
'\d'
re.compile('^r(\d+)-agent(\d+)-kind', re.IGNORECASE) : TYPE_INT,
/usr/share/hplip/base/models.py:429: SyntaxWarning: invalid escape sequence
'\d'
re.compile('^r(\d+)-agent(\d+)-type', re.IGNORECASE) : TYPE_INT,
/usr/share/hplip/base/models.py:430: SyntaxWarning: invalid escape sequence
'\d'
re.compile('^r(\d+)-agent(\d+)-sku', re.IGNORECASE) : TYPE_STR,
/usr/share/hplip/base/models.py:431: SyntaxWarning: invalid escape sequence
'\d'
re.compile('^agent(\d+)-desc', re.IGNORECASE) : TYPE_STR,
/usr/share/hplip/base/models.py:432: SyntaxWarning: invalid escape sequence
'\d'
re.compile('^agent(\d+)-virgin', re.IGNORECASE) : TYPE_BOOL,
/usr/share/hplip/base/models.py:433: SyntaxWarning: invalid escape sequence
'\d'
re.compile('^agent(\d+)-dvc', re.IGNORECASE) : TYPE_INT,
/usr/share/hplip/base/models.py:434: SyntaxWarning: invalid escape sequence
'\d'
re.compile('^agent(\d+)-kind', re.IGNORECASE) : TYPE_INT,
/usr/share/hplip/base/models.py:435: SyntaxWarning: invalid escape sequence
'\d'
re.compile('^agent(\d+)-type', re.IGNORECASE) : TYPE_INT,
/usr/share/hplip/base/models.py:436: SyntaxWarning: invalid escape sequence
'\d'
re.compile('^agent(\d+)-id', re.IGNORECASE) : TYPE_INT,
/usr/share/hplip/base/models.py:437: SyntaxWarning: invalid escape sequence
'\d'
re.compile('^agent(\d+)-hp-ink', re.IGNORECASE) : TYPE_BOOL,
/usr/share/hplip/base/models.py:438: SyntaxWarning: invalid escape sequence
'\d'
re.compile('^agent(\d+)-health-desc', re.IGNORECASE) : TYPE_STR,
/usr/share/hplip/base/models.py:439: SyntaxWarning: invalid escape sequence
'\d'
re.compile('^agent(\d+)-health$', re.IGNORECASE) : TYPE_INT,
/usr/share/hplip/base/models.py:440: SyntaxWarning: invalid escape sequence
'\d'
re.compile('^agent(\d+)-known', re.IGNORECASE) : TYPE_BOOL,
/usr/share/hplip/base/models.py:441: SyntaxWarning: invalid escape sequence
'\d'
re.compile('^agent(\d+)-level', re.IGNORECASE) : TYPE_INT,
/usr/share/hplip/base/models.py:442: SyntaxWarning: invalid escape sequence
'\d'
re.compile('^agent(\d+)-ack', re.IGNORECASE) : TYPE_BOOL,
/usr/share/hplip/base/models.py:443: SyntaxWarning: invalid escape sequence
'\d'
re.compile('^agent(\d+)-sku', re.IGNORECASE) : TYPE_STR,
/usr/share/hplip/base/models.py:444: SyntaxWarning: invalid escape sequence
'\d'
re.compile('^in-tray(\d+)', re.IGNORECASE) : TYPE_BOOL,
/usr/share/hplip/base/models.py:445: SyntaxWarning: invalid escape sequence
'\d'
re.compile('^out-tray(\d+)', re.IGNORECASE) : TYPE_BOOL,
/usr/share/hplip/base/models.py:446: SyntaxWarning: invalid escape sequence
'\d'
re.compile('^model(\d+)', re.IGNORECASE) : TYPE_STR,
/usr/share/hplip/base/password.py:212: SyntaxWarning: invalid escape sequence
'\
['
cb = cb.replace("[", "\[")
/usr/share/hplip/base/password.py:213: SyntaxWarning: invalid escape
[Desktop-packages] [Bug 2061235] Re: Login screen doesn't offer authentication using Yubikey after upgrade 23.10 => 24.04
thanks for the update, closing ** Changed in: gdm3 (Ubuntu) Status: New => Fix Released -- 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/2061235 Title: Login screen doesn't offer authentication using Yubikey after upgrade 23.10 => 24.04 Status in gdm3 package in Ubuntu: Fix Released Bug description: I own YubiKey 5 Nano. In Ubuntu 23.10 I had configured a login to Gnome using YubiKey so that when I started OS with YubiKey inserted, clicked on my username in login screen, I was offered to touch YubiKey and when I did it, then a login succeeded ✓. But when I upgraded to Ubuntu 24.04 beta, in login screen I'm prompted by entering of password only and no "touch" method is offered anymore . Note that YubiKey auth works well e.g. for "sudo": --- $ sudo apt update Please touch the device. ... This is my GDM policy configuration /etc/pam.d/gdm-password --- #%PAM-1.0 authrequisite pam_nologin.so auth requiredpam_succeed_if.so user != root quiet_success @include common-u2f @include common-auth authoptionalpam_gnome_keyring.so @include common-account # SELinux needs to be the first session rule. This ensures that any # lingering context has been cleared. Without this it is possible # that a module could execute code in the wrong domain. session [success=ok ignore=ignore module_unknown=ignore default=bad] pam_selinux.so close session requiredpam_loginuid.so # SELinux needs to intervene at login time to ensure that the process # starts in the proper default security context. Only sessions which are # intended to run in the user's context should be run after this. # pam_selinux.so changes the SELinux context of the used TTY and configures # SELinux in order to transition to the user context with the next execve() # call. session [success=ok ignore=ignore module_unknown=ignore default=bad] pam_selinux.so open session optionalpam_keyinit.so force revoke session requiredpam_limits.so session requiredpam_env.so readenv=1 session requiredpam_env.so readenv=1 user_readenv=1 envfile=/etc/default/locale @include common-session session optionalpam_gnome_keyring.so auto_start @include common-password /etc/pam.d/common-u2f - auth sufficient pam_u2f.so authfile=/etc/u2f_mappings cue Used SW and HW: --- * HW: laptop Yoga Slim 7 14ARE05 * SW: * Ubuntu 24.04 * kernel 6.8.0-22-generic * gdm3 46.0-2ubuntu1, I'm using default Wayland session * libpam-yubico 2.26-1.1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2061235/+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 2062177] Re: Remmina crashes after RDP connection
** Changed in: remmina (Ubuntu)
Importance: Undecided => High
** Changed in: remmina (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to remmina in Ubuntu.
https://bugs.launchpad.net/bugs/2062177
Title:
Remmina crashes after RDP connection
Status in remmina package in Ubuntu:
In Progress
Bug description:
When connecting with RDP Remmina crashes. Syslog show the following:
2024-04-18T13:49:02.969819+02:00 localhost dbus-daemon[3214]: [session
uid=1001 pid=3214] Successfully activated service
'org.gnome.seahorse.Application'
2024-04-18T13:49:03.655883+02:00 localhost systemd[3176]: Started
app-gnome-org.remmina.Remmina-53436.scope - Application launched by gnome-shell.
2024-04-18T13:49:03.656884+02:00 localhost remmina[53441]: Remmina does not
log all output statements. Turn on more verbose output by using
"G_MESSAGES_DEBUG=remmina" as an environment variable.#012More info available
on the Remmina wiki
at:#012https://gitlab.com/Remmina/Remmina/-/wikis/Usage/Remmina-debugging
2024-04-18T13:49:03.766401+02:00 localhost remmina[53441]:
gtk_menu_attach_to_widget(): menu already attached to GtkMenuItem
2024-04-18T13:49:13.851397+02:00 localhost
org.remmina.Remmina.desktop[53441]: [13:49:13:572] [53441:d116]
[ERROR][com.freerdp.common.settings] - [freerdp_settings_get_bool]: Invalid key
index 0 [FreeRDP_instance|FREERDP_SETTINGS_TYPE_POINTER]
2024-04-18T13:49:13.851716+02:00 localhost
org.remmina.Remmina.desktop[53441]: [13:49:13:572] [53441:d116]
[FATAL][com.freerdp.winpr.assert] - [winpr_int_assert]: FALSE
[obj-x86_64-linux-gnu/libfreerdp/CMakeFiles/freerdp.dir/compiler_depend.ts:freerdp_settings_get_bool:637]
2024-04-18T13:49:13.851760+02:00 localhost
org.remmina.Remmina.desktop[53441]: [13:49:13:572] [53441:d116]
[FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 0:
dli_fname=/lib/x86_64-linux-gnu/libwinpr3.so.3 [0x70e694e2b000],
dli_sname=winpr_backtrace [0x70e694e97660]
2024-04-18T13:49:13.851791+02:00 localhost
org.remmina.Remmina.desktop[53441]: [13:49:13:572] [53441:d116]
[FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 1:
dli_fname=/lib/x86_64-linux-gnu/libwinpr3.so.3 [0x70e694e2b000],
dli_sname=winpr_log_backtrace_ex [0x70e694e9f150]
2024-04-18T13:49:13.851803+02:00 localhost
org.remmina.Remmina.desktop[53441]: [13:49:13:572] [53441:d116]
[FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 2:
dli_fname=/lib/x86_64-linux-gnu/libfreerdp3.so.3 [0x70e69420],
dli_sname=(null) [(nil)]
2024-04-18T13:49:13.851815+02:00 localhost
org.remmina.Remmina.desktop[53441]: [13:49:13:572] [53441:d116]
[FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 3:
dli_fname=/lib/x86_64-linux-gnu/libfreerdp3.so.3 [0x70e69420],
dli_sname=freerdp_settings_get_bool [0x70e6942658a0]
2024-04-18T13:49:13.851827+02:00 localhost
org.remmina.Remmina.desktop[53441]: [13:49:13:572] [53441:d116]
[FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 4:
dli_fname=/usr/lib/x86_64-linux-gnu/remmina/plugins/remmina-plugin-rdp.so
[0x70e6958dd000], dli_sname=(null) [(nil)]
2024-04-18T13:49:13.851839+02:00 localhost
org.remmina.Remmina.desktop[53441]: [13:49:13:572] [53441:d116]
[FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 5:
dli_fname=/usr/lib/x86_64-linux-gnu/remmina/plugins/remmina-plugin-rdp.so
[0x70e6958dd000], dli_sname=(null) [(nil)]
2024-04-18T13:49:13.851851+02:00 localhost
org.remmina.Remmina.desktop[53441]: [13:49:13:572] [53441:d116]
[FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 6:
dli_fname=/usr/bin/../lib/x86_64-linux-gnu/libc.so.6 [0x70e69940],
dli_sname=(null) [(nil)]
2024-04-18T13:49:13.851873+02:00 localhost
org.remmina.Remmina.desktop[53441]: [13:49:13:572] [53441:d116]
[FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 7:
dli_fname=/usr/bin/../lib/x86_64-linux-gnu/libc.so.6 [0x70e69940],
dli_sname=(null) [(nil)]
2024-04-18T13:49:13.851885+02:00 localhost
org.remmina.Remmina.desktop[53441]: [13:49:13:572] [53441:d116]
[FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 8: unresolvable,
address=(nil)
2024-04-18T13:49:14.938231+02:00 localhost
org.remmina.Remmina.desktop[53436]: /usr/bin/remmina-file-wrapper: line 37:
53441 Aborted (core dumped) "$REMMINA" "${@}"
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: remmina 1.4.35+dfsg-0ubuntu4
ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
Uname: Linux 6.8.0-22-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: pass
CloudArchitecture: x86_64
CloudID: none
CloudName: none
CloudPlatform: none
CloudSubPlatform: config
Date: Thu Apr 18 13:59:31 2024
InstallationDate: Installed on
[Desktop-packages] [Bug 2063154] Re: Wireguard imported with Network manager does not work after latest upgrade, wg-quick using the same config file works
thanks for the update, closing the report then but feel free to reopen if you get it again ** Changed in: network-manager (Ubuntu) Status: New => Invalid -- 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/2063154 Title: Wireguard imported with Network manager does not work after latest upgrade, wg-quick using the same config file works Status in network-manager package in Ubuntu: Invalid Bug description: Until a few days ago, after some upgrade, wireguard config imported with Network manager worked ootb. Now, it does not, there is no handshake. Activating the same config file with wg-quick does work. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: network-manager 1.46.0-1ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-1005.5-oem 6.8.1 Uname: Linux 6.8.0-1005-oem x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Apr 22 22:41:06 2024 InstallationDate: Installed on 2024-04-08 (14 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240408) IpRoute: default via 192.168.173.139 dev wlp1s0 proto dhcp src 192.168.173.61 metric 600 192.168.173.0/24 dev wlp1s0 proto kernel scope link src 192.168.173.61 metric 600 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE IP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH wlp1s0 wifi connected full limited /org/freedesktop/NetworkManager/Devices/2 MR Net 1 f92fae58-e84a-487e-9bdd-8d1ffbf8ca17 /org/freedesktop/NetworkManager/ActiveConnection/2 lo loopback connected (externally) unknown unknown /org/freedesktop/NetworkManager/Devices/1 lo 6fc7aa03-b696-4081-a275-4dc81c74c13e /org/freedesktop/NetworkManager/ActiveConnection/1 P14s_wg wireguard connected (externally) limited limited /org/freedesktop/NetworkManager/Devices/4 P14s_wg 40fadfce-b931-472f-b4cd-9922f77068ee /org/freedesktop/NetworkManager/ActiveConnection/14 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.46.0 connected started full enabled enabled enabled missing enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2063154/+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 2063304] Re: chromium 124.0.6367.60 fails to draw its window
The syscall=330, the mknod denial, the /etc/vulkan/ denials are also
produced by the working chromium snap.
The /etc/igfx_user_feature.txt denial only shows up with the broken
chromium snap.
--
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/2063304
Title:
chromium 124.0.6367.60 fails to draw its window
Status in chromium-browser package in Ubuntu:
New
Bug description:
Since the last snap update to 124.0.6367.60, I cannot use chromium.
It launches fine, but the window itself is fully transparent (e.g.
triggering the Overview makes it look like a piece of my wallpaper).
I have Intel graphics and use a Wayland session on Ubuntu 23.10.
At first I thought I was experiencing bug 1967488, but the more I looked at
it, the less sure I was (no Nvidia here, no issues with older snap versions, no
KMS errors in journalctl), so I'm filing a new one.
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/nvme0n1p5 ext4 732G 483G 212G 70% /
tmpfs tmpfs 7,7G 75M 7,6G 1% /dev/shm
/dev/nvme0n1p5 ext4 732G 483G 212G 70% /
DistroRelease: Ubuntu 23.10
EcryptfsInUse: Yes
InstallationDate: Installed on 2019-06-12 (1777 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
Package: chromium-browser 1:85.0.4183.83-0ubuntu3
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 6.5.0-28.29-generic 6.5.13
Snap.Changes:
ID Status Spawn Ready Summary
824 Done2024-04-23T20:13:38+03:00 2024-04-23T20:28:35+03:00
Auto-refresh snap "chromium"
Snap.ChromeDriverVersion: ChromeDriver 124.0.6367.60
(8771130bd84f76d855ae42fbe02752b03e352f17-refs/branch-heads/6367@{#798})
Snap.ChromiumVersion: Chromium 124.0.6367.60 snap
Tags: mantic wayland-session
Uname: Linux 6.5.0-28-generic x86_64
UpgradeStatus: Upgraded to mantic on 2023-10-13 (194 days ago)
UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2063304/+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 2063304] Re: chromium 124.0.6367.60 fails to draw its window
(sorry, copy/paste fail) > dmesg has a bunch of repeated bal. 24 09:40:04 blynas kernel: audit: type=1400 audit(1713940804.105:20243): apparmor="DENIED" operation="open" class="file" profile="snap.firefox.firefox" name="/etc/igfx_user_feature.txt" pid=7070 comm="FSBroker7944" requested_mask="r" denied_mask=" r" fsuid=1000 ouid=0 bal. 24 09:40:04 blynas kernel: audit: type=1400 audit(1713940804.105:20244): apparmor="DENIED" operation="open" class="file" profile="snap.firefox.firefox" name="/etc/igfx_user_feature_next.txt" pid=7070 comm="FSBroker7944" requested_mask="r" denied_m ask="r" fsuid=1000 ouid=0 bal. 24 09:40:12 blynas kernel: audit: type=1400 audit(1713940812.841:20245): apparmor="DENIED" operation="mknod" class="file" profile="snap.firefox.firefox" name="/home/mg/.local/share/fonts/.uuid.TMP-tJGwe8" pid=191609 comm=57656220436F6E74656E74 req uested_mask="c" denied_mask="c" fsuid=1000 ouid=1000 and on startup bal. 24 09:20:31 blynas systemd[3777]: Started snap.chromium.chromium-0ad4ed29-f99c-4296-9b4f-349b888ce2f6.scope. bal. 24 09:20:32 blynas kernel: audit: type=1326 audit(1713939632.053:20170): auid=1000 uid=1000 gid=1000 ses=3 subj=snap.chromium.chromium pid=189920 comm="chrome" exe="/snap/chromium/2828/usr/lib/chromium-browser/chrome" sig=0 arch=c03e syscall=330 compat=0 ip=0x77eb42b8ff6b code=0x5 bal. 24 09:20:32 blynas kernel: audit: type=1326 audit(1713939632.053:20171): auid=1000 uid=1000 gid=1000 ses=3 subj=snap.chromium.chromium pid=189921 comm="chrome" exe="/snap/chromium/2828/usr/lib/chromium-browser/chrome" sig=0 arch=c03e syscall=330 compat=0 ip=0x7980e32def6b code=0x5 bal. 24 09:20:32 blynas chrome[189858]: Not loading module "atk-bridge": The functionality is provided by GTK natively. Please try to not load it. bal. 24 09:20:32 blynas kernel: audit: type=1400 audit(1713939632.165:20172): apparmor="DENIED" operation="mknod" class="file" profile="snap.chromium.chromium" name="/home/mg/.local/share/fonts/.uuid.TMP-u02YgN" pid=189858 comm="ThreadPoolForeg" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000 bal. 24 09:20:32 blynas gnome-keyring-daemon[3862]: asked to register item /org/freedesktop/secrets/collection/login/16, but it's already registered bal. 24 09:20:32 blynas gnome-keyring-d[3862]: asked to register item /org/freedesktop/secrets/collection/login/16, but it's already registered bal. 24 09:20:32 blynas kernel: audit: type=1400 audit(1713939632.201:20173): apparmor="DENIED" operation="open" class="file" profile="snap.chromium.chromium" name="/etc/vulkan/implicit_layer.d/" pid=189957 comm="chrome" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 bal. 24 09:20:32 blynas kernel: audit: type=1400 audit(1713939632.201:20174): apparmor="DENIED" operation="open" class="file" profile="snap.chromium.chromium" name="/etc/vulkan/implicit_layer.d/" pid=189957 comm="chrome" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 bal. 24 09:20:32 blynas kernel: audit: type=1400 audit(1713939632.201:20175): apparmor="DENIED" operation="open" class="file" profile="snap.chromium.chromium" name="/etc/vulkan/icd.d/" pid=189957 comm="chrome" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 bal. 24 09:20:32 blynas kernel: audit: type=1400 audit(1713939632.201:20176): apparmor="DENIED" operation="open" class="file" profile="snap.chromium.chromium" name="/etc/vulkan/icd.d/" pid=189957 comm="chrome" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 bal. 24 09:20:32 blynas kernel: audit: type=1400 audit(1713939632.201:20177): apparmor="DENIED" operation="open" class="file" profile="snap.chromium.chromium" name="/etc/vulkan/implicit_layer.d/" pid=189957 comm="chrome" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 bal. 24 09:20:32 blynas kernel: audit: type=1400 audit(1713939632.201:20178): apparmor="DENIED" operation="open" class="file" profile="snap.chromium.chromium" name="/etc/vulkan/implicit_layer.d/" pid=189957 comm="chrome" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 bal. 24 09:20:32 blynas kernel: audit: type=1400 audit(1713939632.201:20179): apparmor="DENIED" operation="open" class="file" profile="snap.chromium.chromium" name="/etc/vulkan/icd.d/" pid=189957 comm="chrome" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 bal. 24 09:20:32 blynas chromium_chromium.desktop[189858]: [189858:189858:0424/092032.211248:ERROR:chrome_browser_cloud_management_controller.cc(161)] Cloud management controller initialization aborted as CBCM is not enabled. Please use the `--enable-chrome-browser-cloud-management` command line flag to enable it if you are not using the official Google Chrome build. bal. 24 09:20:33 blynas chromium_chromium.desktop[189858]: [189858:189858:0424/092033.495512:ERROR:object_proxy.cc(576)] Failed to call method: org.freedesktop.ScreenSaver.GetActive: object_path= /org/freedesktop/ScreenSaver: org.freedesktop.DBus.Error.NotSupported: This method is not part of the idle
[Desktop-packages] [Bug 2037015] Re: Screen corruption of webkit2gtk apps in X11 on Raspberry Pi, such as during install
** Description changed: + [ Impact ] + + Screen corruption of webkit2gtk apps in X11 on Raspberry Pi, such as + during install. + + [ Test Plan ] + + 1. Open the default Help app by clicking the question mark icon in the + dock or by running 'yelp'. + + 2. Verify it didn't crash and the window contents are not corrupt. + + [ Where problems could occur ] + + The fix is limited to webkit2gtk so can only affect apps such as yelp or + the Raspberry Pi installer. + + [ Other Info ] + During the initial configuration of the Ubuntu Desktop for Raspberry Pi (the oem-config process, derived from ubiquity), on the Mantic beta images, after the various pages of information have been filled out and the process moves onto configuration, the "slide deck" that is usually displayed during the process appeared corrupted as if a horizontal stride were incorrectly set somewhere. I'm attached a photo of the screen (as, while I could take a screenshot during the process, it evidently wasn't saved somewhere persistent). I originally thought this might be a regression of LP: #1924251 as the corruption in the window looks very similar (incorrect horizontal stride causing "banding"), but I tested the embedded browser (via the help system) after completing setup and it worked perfectly so that's *probably* unrelated. ** Description changed: [ Impact ] Screen corruption of webkit2gtk apps in X11 on Raspberry Pi, such as during install. [ Test Plan ] - 1. Open the default Help app by clicking the question mark icon in the + 1. Log into a Xorg session on a Raspberry Pi 4/400. + + 2. Open the default Help app by clicking the question mark icon in the dock or by running 'yelp'. - 2. Verify it didn't crash and the window contents are not corrupt. + 3. Verify it didn't crash and the window contents are not corrupt. [ Where problems could occur ] The fix is limited to webkit2gtk so can only affect apps such as yelp or the Raspberry Pi installer. [ Other Info ] During the initial configuration of the Ubuntu Desktop for Raspberry Pi (the oem-config process, derived from ubiquity), on the Mantic beta images, after the various pages of information have been filled out and the process moves onto configuration, the "slide deck" that is usually displayed during the process appeared corrupted as if a horizontal stride were incorrectly set somewhere. I'm attached a photo of the screen (as, while I could take a screenshot during the process, it evidently wasn't saved somewhere persistent). I originally thought this might be a regression of LP: #1924251 as the corruption in the window looks very similar (incorrect horizontal stride causing "banding"), but I tested the embedded browser (via the help system) after completing setup and it worked perfectly so that's *probably* unrelated. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to webkit2gtk in Ubuntu. https://bugs.launchpad.net/bugs/2037015 Title: Screen corruption of webkit2gtk apps in X11 on Raspberry Pi, such as during install Status in Webkit: Confirmed Status in mesa package in Ubuntu: Confirmed Status in webkit2gtk package in Ubuntu: In Progress Bug description: [ Impact ] Screen corruption of webkit2gtk apps in X11 on Raspberry Pi, such as during install. [ Test Plan ] 1. Log into a Xorg session on a Raspberry Pi 4/400. 2. Open the default Help app by clicking the question mark icon in the dock or by running 'yelp'. 3. Verify it didn't crash and the window contents are not corrupt. [ Where problems could occur ] The fix is limited to webkit2gtk so can only affect apps such as yelp or the Raspberry Pi installer. [ Other Info ] During the initial configuration of the Ubuntu Desktop for Raspberry Pi (the oem-config process, derived from ubiquity), on the Mantic beta images, after the various pages of information have been filled out and the process moves onto configuration, the "slide deck" that is usually displayed during the process appeared corrupted as if a horizontal stride were incorrectly set somewhere. I'm attached a photo of the screen (as, while I could take a screenshot during the process, it evidently wasn't saved somewhere persistent). I originally thought this might be a regression of LP: #1924251 as the corruption in the window looks very similar (incorrect horizontal stride causing "banding"), but I tested the embedded browser (via the help system) after completing setup and it worked perfectly so that's *probably* unrelated. To manage notifications about this bug go to: https://bugs.launchpad.net/webkit/+bug/2037015/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help :
[Desktop-packages] [Bug 2037015] Re: Screen corruption of webkit2gtk apps in X11 on Raspberry Pi, such as during install
Confirmed this fix is now working: https://salsa.debian.org/webkit-team/webkit/-/merge_requests/20 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to webkit2gtk in Ubuntu. https://bugs.launchpad.net/bugs/2037015 Title: Screen corruption of webkit2gtk apps in X11 on Raspberry Pi, such as during install Status in Webkit: Confirmed Status in mesa package in Ubuntu: Confirmed Status in webkit2gtk package in Ubuntu: In Progress Bug description: [ Impact ] Screen corruption of webkit2gtk apps in X11 on Raspberry Pi, such as during install. [ Test Plan ] 1. Log into a Xorg session on a Raspberry Pi 4/400. 2. Open the default Help app by clicking the question mark icon in the dock or by running 'yelp'. 3. Verify it didn't crash and the window contents are not corrupt. [ Where problems could occur ] The fix is limited to webkit2gtk so can only affect apps such as yelp or the Raspberry Pi installer. [ Other Info ] During the initial configuration of the Ubuntu Desktop for Raspberry Pi (the oem-config process, derived from ubiquity), on the Mantic beta images, after the various pages of information have been filled out and the process moves onto configuration, the "slide deck" that is usually displayed during the process appeared corrupted as if a horizontal stride were incorrectly set somewhere. I'm attached a photo of the screen (as, while I could take a screenshot during the process, it evidently wasn't saved somewhere persistent). I originally thought this might be a regression of LP: #1924251 as the corruption in the window looks very similar (incorrect horizontal stride causing "banding"), but I tested the embedded browser (via the help system) after completing setup and it worked perfectly so that's *probably* unrelated. To manage notifications about this bug go to: https://bugs.launchpad.net/webkit/+bug/2037015/+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 2063304] Snap.Info.gtk-common-themes.txt
apport information
** Attachment added: "Snap.Info.gtk-common-themes.txt"
https://bugs.launchpad.net/bugs/2063304/+attachment/5769956/+files/Snap.Info.gtk-common-themes.txt
** Tags added: snap
--
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/2063304
Title:
chromium 124.0.6367.60 fails to draw its window
Status in chromium-browser package in Ubuntu:
New
Bug description:
Since the last snap update to 124.0.6367.60, I cannot use chromium.
It launches fine, but the window itself is fully transparent (e.g.
triggering the Overview makes it look like a piece of my wallpaper).
I have Intel graphics and use a Wayland session on Ubuntu 23.10.
At first I thought I was experiencing bug 1967488, but the more I looked at
it, the less sure I was (no Nvidia here, no issues with older snap versions, no
KMS errors in journalctl), so I'm filing a new one.
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/nvme0n1p5 ext4 732G 483G 212G 70% /
tmpfs tmpfs 7,7G 75M 7,6G 1% /dev/shm
/dev/nvme0n1p5 ext4 732G 483G 212G 70% /
DistroRelease: Ubuntu 23.10
EcryptfsInUse: Yes
InstallationDate: Installed on 2019-06-12 (1777 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
Package: chromium-browser 1:85.0.4183.83-0ubuntu3
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 6.5.0-28.29-generic 6.5.13
Snap.Changes:
ID Status Spawn Ready Summary
824 Done2024-04-23T20:13:38+03:00 2024-04-23T20:28:35+03:00
Auto-refresh snap "chromium"
Snap.ChromeDriverVersion: ChromeDriver 124.0.6367.60
(8771130bd84f76d855ae42fbe02752b03e352f17-refs/branch-heads/6367@{#798})
Snap.ChromiumVersion: Chromium 124.0.6367.60 snap
Tags: mantic wayland-session
Uname: Linux 6.5.0-28-generic x86_64
UpgradeStatus: Upgraded to mantic on 2023-10-13 (194 days ago)
UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2063304/+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 2063304] Re: chromium 124.0.6367.60 fails to draw its window
dmesg has a bunch of repeated
`snap revert chromium` reverted to 123.0.6312.122, which works fine.
--
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/2063304
Title:
chromium 124.0.6367.60 fails to draw its window
Status in chromium-browser package in Ubuntu:
New
Bug description:
Since the last snap update to 124.0.6367.60, I cannot use chromium.
It launches fine, but the window itself is fully transparent (e.g.
triggering the Overview makes it look like a piece of my wallpaper).
I have Intel graphics and use a Wayland session on Ubuntu 23.10.
At first I thought I was experiencing bug 1967488, but the more I looked at
it, the less sure I was (no Nvidia here, no issues with older snap versions, no
KMS errors in journalctl), so I'm filing a new one.
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/nvme0n1p5 ext4 732G 483G 212G 70% /
tmpfs tmpfs 7,7G 75M 7,6G 1% /dev/shm
/dev/nvme0n1p5 ext4 732G 483G 212G 70% /
DistroRelease: Ubuntu 23.10
EcryptfsInUse: Yes
InstallationDate: Installed on 2019-06-12 (1777 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
Package: chromium-browser 1:85.0.4183.83-0ubuntu3
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 6.5.0-28.29-generic 6.5.13
Snap.Changes:
ID Status Spawn Ready Summary
824 Done2024-04-23T20:13:38+03:00 2024-04-23T20:28:35+03:00
Auto-refresh snap "chromium"
Snap.ChromeDriverVersion: ChromeDriver 124.0.6367.60
(8771130bd84f76d855ae42fbe02752b03e352f17-refs/branch-heads/6367@{#798})
Snap.ChromiumVersion: Chromium 124.0.6367.60 snap
Tags: mantic wayland-session
Uname: Linux 6.5.0-28-generic x86_64
UpgradeStatus: Upgraded to mantic on 2023-10-13 (194 days ago)
UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2063304/+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 2063304] Snap.Info.gnome-42-2204.txt
apport information
** Attachment added: "Snap.Info.gnome-42-2204.txt"
https://bugs.launchpad.net/bugs/2063304/+attachment/5769955/+files/Snap.Info.gnome-42-2204.txt
--
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/2063304
Title:
chromium 124.0.6367.60 fails to draw its window
Status in chromium-browser package in Ubuntu:
New
Bug description:
Since the last snap update to 124.0.6367.60, I cannot use chromium.
It launches fine, but the window itself is fully transparent (e.g.
triggering the Overview makes it look like a piece of my wallpaper).
I have Intel graphics and use a Wayland session on Ubuntu 23.10.
At first I thought I was experiencing bug 1967488, but the more I looked at
it, the less sure I was (no Nvidia here, no issues with older snap versions, no
KMS errors in journalctl), so I'm filing a new one.
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/nvme0n1p5 ext4 732G 483G 212G 70% /
tmpfs tmpfs 7,7G 75M 7,6G 1% /dev/shm
/dev/nvme0n1p5 ext4 732G 483G 212G 70% /
DistroRelease: Ubuntu 23.10
EcryptfsInUse: Yes
InstallationDate: Installed on 2019-06-12 (1777 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
Package: chromium-browser 1:85.0.4183.83-0ubuntu3
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 6.5.0-28.29-generic 6.5.13
Snap.Changes:
ID Status Spawn Ready Summary
824 Done2024-04-23T20:13:38+03:00 2024-04-23T20:28:35+03:00
Auto-refresh snap "chromium"
Snap.ChromeDriverVersion: ChromeDriver 124.0.6367.60
(8771130bd84f76d855ae42fbe02752b03e352f17-refs/branch-heads/6367@{#798})
Snap.ChromiumVersion: Chromium 124.0.6367.60 snap
Tags: mantic wayland-session
Uname: Linux 6.5.0-28-generic x86_64
UpgradeStatus: Upgraded to mantic on 2023-10-13 (194 days ago)
UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2063304/+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 2063304] Snap.Info.core20.txt
apport information
** Attachment added: "Snap.Info.core20.txt"
https://bugs.launchpad.net/bugs/2063304/+attachment/5769953/+files/Snap.Info.core20.txt
--
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/2063304
Title:
chromium 124.0.6367.60 fails to draw its window
Status in chromium-browser package in Ubuntu:
New
Bug description:
Since the last snap update to 124.0.6367.60, I cannot use chromium.
It launches fine, but the window itself is fully transparent (e.g.
triggering the Overview makes it look like a piece of my wallpaper).
I have Intel graphics and use a Wayland session on Ubuntu 23.10.
At first I thought I was experiencing bug 1967488, but the more I looked at
it, the less sure I was (no Nvidia here, no issues with older snap versions, no
KMS errors in journalctl), so I'm filing a new one.
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/nvme0n1p5 ext4 732G 483G 212G 70% /
tmpfs tmpfs 7,7G 75M 7,6G 1% /dev/shm
/dev/nvme0n1p5 ext4 732G 483G 212G 70% /
DistroRelease: Ubuntu 23.10
EcryptfsInUse: Yes
InstallationDate: Installed on 2019-06-12 (1777 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
Package: chromium-browser 1:85.0.4183.83-0ubuntu3
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 6.5.0-28.29-generic 6.5.13
Snap.Changes:
ID Status Spawn Ready Summary
824 Done2024-04-23T20:13:38+03:00 2024-04-23T20:28:35+03:00
Auto-refresh snap "chromium"
Snap.ChromeDriverVersion: ChromeDriver 124.0.6367.60
(8771130bd84f76d855ae42fbe02752b03e352f17-refs/branch-heads/6367@{#798})
Snap.ChromiumVersion: Chromium 124.0.6367.60 snap
Tags: mantic wayland-session
Uname: Linux 6.5.0-28-generic x86_64
UpgradeStatus: Upgraded to mantic on 2023-10-13 (194 days ago)
UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2063304/+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 2063304] Snap.Info.cups.txt
apport information
** Attachment added: "Snap.Info.cups.txt"
https://bugs.launchpad.net/bugs/2063304/+attachment/5769954/+files/Snap.Info.cups.txt
--
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/2063304
Title:
chromium 124.0.6367.60 fails to draw its window
Status in chromium-browser package in Ubuntu:
New
Bug description:
Since the last snap update to 124.0.6367.60, I cannot use chromium.
It launches fine, but the window itself is fully transparent (e.g.
triggering the Overview makes it look like a piece of my wallpaper).
I have Intel graphics and use a Wayland session on Ubuntu 23.10.
At first I thought I was experiencing bug 1967488, but the more I looked at
it, the less sure I was (no Nvidia here, no issues with older snap versions, no
KMS errors in journalctl), so I'm filing a new one.
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/nvme0n1p5 ext4 732G 483G 212G 70% /
tmpfs tmpfs 7,7G 75M 7,6G 1% /dev/shm
/dev/nvme0n1p5 ext4 732G 483G 212G 70% /
DistroRelease: Ubuntu 23.10
EcryptfsInUse: Yes
InstallationDate: Installed on 2019-06-12 (1777 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
Package: chromium-browser 1:85.0.4183.83-0ubuntu3
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 6.5.0-28.29-generic 6.5.13
Snap.Changes:
ID Status Spawn Ready Summary
824 Done2024-04-23T20:13:38+03:00 2024-04-23T20:28:35+03:00
Auto-refresh snap "chromium"
Snap.ChromeDriverVersion: ChromeDriver 124.0.6367.60
(8771130bd84f76d855ae42fbe02752b03e352f17-refs/branch-heads/6367@{#798})
Snap.ChromiumVersion: Chromium 124.0.6367.60 snap
Tags: mantic wayland-session
Uname: Linux 6.5.0-28-generic x86_64
UpgradeStatus: Upgraded to mantic on 2023-10-13 (194 days ago)
UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2063304/+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 2063304] Snap.Info.core.txt
apport information
** Attachment added: "Snap.Info.core.txt"
https://bugs.launchpad.net/bugs/2063304/+attachment/5769952/+files/Snap.Info.core.txt
--
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/2063304
Title:
chromium 124.0.6367.60 fails to draw its window
Status in chromium-browser package in Ubuntu:
New
Bug description:
Since the last snap update to 124.0.6367.60, I cannot use chromium.
It launches fine, but the window itself is fully transparent (e.g.
triggering the Overview makes it look like a piece of my wallpaper).
I have Intel graphics and use a Wayland session on Ubuntu 23.10.
At first I thought I was experiencing bug 1967488, but the more I looked at
it, the less sure I was (no Nvidia here, no issues with older snap versions, no
KMS errors in journalctl), so I'm filing a new one.
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/nvme0n1p5 ext4 732G 483G 212G 70% /
tmpfs tmpfs 7,7G 75M 7,6G 1% /dev/shm
/dev/nvme0n1p5 ext4 732G 483G 212G 70% /
DistroRelease: Ubuntu 23.10
EcryptfsInUse: Yes
InstallationDate: Installed on 2019-06-12 (1777 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
Package: chromium-browser 1:85.0.4183.83-0ubuntu3
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 6.5.0-28.29-generic 6.5.13
Snap.Changes:
ID Status Spawn Ready Summary
824 Done2024-04-23T20:13:38+03:00 2024-04-23T20:28:35+03:00
Auto-refresh snap "chromium"
Snap.ChromeDriverVersion: ChromeDriver 124.0.6367.60
(8771130bd84f76d855ae42fbe02752b03e352f17-refs/branch-heads/6367@{#798})
Snap.ChromiumVersion: Chromium 124.0.6367.60 snap
Tags: mantic wayland-session
Uname: Linux 6.5.0-28-generic x86_64
UpgradeStatus: Upgraded to mantic on 2023-10-13 (194 days ago)
UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2063304/+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 2063304] Snap.ChromiumPrefs.txt
apport information
** Attachment added: "Snap.ChromiumPrefs.txt"
https://bugs.launchpad.net/bugs/2063304/+attachment/5769949/+files/Snap.ChromiumPrefs.txt
--
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/2063304
Title:
chromium 124.0.6367.60 fails to draw its window
Status in chromium-browser package in Ubuntu:
New
Bug description:
Since the last snap update to 124.0.6367.60, I cannot use chromium.
It launches fine, but the window itself is fully transparent (e.g.
triggering the Overview makes it look like a piece of my wallpaper).
I have Intel graphics and use a Wayland session on Ubuntu 23.10.
At first I thought I was experiencing bug 1967488, but the more I looked at
it, the less sure I was (no Nvidia here, no issues with older snap versions, no
KMS errors in journalctl), so I'm filing a new one.
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/nvme0n1p5 ext4 732G 483G 212G 70% /
tmpfs tmpfs 7,7G 75M 7,6G 1% /dev/shm
/dev/nvme0n1p5 ext4 732G 483G 212G 70% /
DistroRelease: Ubuntu 23.10
EcryptfsInUse: Yes
InstallationDate: Installed on 2019-06-12 (1777 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
Package: chromium-browser 1:85.0.4183.83-0ubuntu3
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 6.5.0-28.29-generic 6.5.13
Snap.Changes:
ID Status Spawn Ready Summary
824 Done2024-04-23T20:13:38+03:00 2024-04-23T20:28:35+03:00
Auto-refresh snap "chromium"
Snap.ChromeDriverVersion: ChromeDriver 124.0.6367.60
(8771130bd84f76d855ae42fbe02752b03e352f17-refs/branch-heads/6367@{#798})
Snap.ChromiumVersion: Chromium 124.0.6367.60 snap
Tags: mantic wayland-session
Uname: Linux 6.5.0-28-generic x86_64
UpgradeStatus: Upgraded to mantic on 2023-10-13 (194 days ago)
UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2063304/+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 2063304] Snap.Info.chromium.txt
apport information
** Attachment added: "Snap.Info.chromium.txt"
https://bugs.launchpad.net/bugs/2063304/+attachment/5769951/+files/Snap.Info.chromium.txt
--
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/2063304
Title:
chromium 124.0.6367.60 fails to draw its window
Status in chromium-browser package in Ubuntu:
New
Bug description:
Since the last snap update to 124.0.6367.60, I cannot use chromium.
It launches fine, but the window itself is fully transparent (e.g.
triggering the Overview makes it look like a piece of my wallpaper).
I have Intel graphics and use a Wayland session on Ubuntu 23.10.
At first I thought I was experiencing bug 1967488, but the more I looked at
it, the less sure I was (no Nvidia here, no issues with older snap versions, no
KMS errors in journalctl), so I'm filing a new one.
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/nvme0n1p5 ext4 732G 483G 212G 70% /
tmpfs tmpfs 7,7G 75M 7,6G 1% /dev/shm
/dev/nvme0n1p5 ext4 732G 483G 212G 70% /
DistroRelease: Ubuntu 23.10
EcryptfsInUse: Yes
InstallationDate: Installed on 2019-06-12 (1777 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
Package: chromium-browser 1:85.0.4183.83-0ubuntu3
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 6.5.0-28.29-generic 6.5.13
Snap.Changes:
ID Status Spawn Ready Summary
824 Done2024-04-23T20:13:38+03:00 2024-04-23T20:28:35+03:00
Auto-refresh snap "chromium"
Snap.ChromeDriverVersion: ChromeDriver 124.0.6367.60
(8771130bd84f76d855ae42fbe02752b03e352f17-refs/branch-heads/6367@{#798})
Snap.ChromiumVersion: Chromium 124.0.6367.60 snap
Tags: mantic wayland-session
Uname: Linux 6.5.0-28-generic x86_64
UpgradeStatus: Upgraded to mantic on 2023-10-13 (194 days ago)
UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2063304/+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 2063304] ProcCpuinfoMinimal.txt
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/2063304/+attachment/5769947/+files/ProcCpuinfoMinimal.txt
--
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/2063304
Title:
chromium 124.0.6367.60 fails to draw its window
Status in chromium-browser package in Ubuntu:
New
Bug description:
Since the last snap update to 124.0.6367.60, I cannot use chromium.
It launches fine, but the window itself is fully transparent (e.g.
triggering the Overview makes it look like a piece of my wallpaper).
I have Intel graphics and use a Wayland session on Ubuntu 23.10.
At first I thought I was experiencing bug 1967488, but the more I looked at
it, the less sure I was (no Nvidia here, no issues with older snap versions, no
KMS errors in journalctl), so I'm filing a new one.
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/nvme0n1p5 ext4 732G 483G 212G 70% /
tmpfs tmpfs 7,7G 75M 7,6G 1% /dev/shm
/dev/nvme0n1p5 ext4 732G 483G 212G 70% /
DistroRelease: Ubuntu 23.10
EcryptfsInUse: Yes
InstallationDate: Installed on 2019-06-12 (1777 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
Package: chromium-browser 1:85.0.4183.83-0ubuntu3
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 6.5.0-28.29-generic 6.5.13
Snap.Changes:
ID Status Spawn Ready Summary
824 Done2024-04-23T20:13:38+03:00 2024-04-23T20:28:35+03:00
Auto-refresh snap "chromium"
Snap.ChromeDriverVersion: ChromeDriver 124.0.6367.60
(8771130bd84f76d855ae42fbe02752b03e352f17-refs/branch-heads/6367@{#798})
Snap.ChromiumVersion: Chromium 124.0.6367.60 snap
Tags: mantic wayland-session
Uname: Linux 6.5.0-28-generic x86_64
UpgradeStatus: Upgraded to mantic on 2023-10-13 (194 days ago)
UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2063304/+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 2063304] Snap.Connections.txt
apport information
** Attachment added: "Snap.Connections.txt"
https://bugs.launchpad.net/bugs/2063304/+attachment/5769950/+files/Snap.Connections.txt
--
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/2063304
Title:
chromium 124.0.6367.60 fails to draw its window
Status in chromium-browser package in Ubuntu:
New
Bug description:
Since the last snap update to 124.0.6367.60, I cannot use chromium.
It launches fine, but the window itself is fully transparent (e.g.
triggering the Overview makes it look like a piece of my wallpaper).
I have Intel graphics and use a Wayland session on Ubuntu 23.10.
At first I thought I was experiencing bug 1967488, but the more I looked at
it, the less sure I was (no Nvidia here, no issues with older snap versions, no
KMS errors in journalctl), so I'm filing a new one.
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/nvme0n1p5 ext4 732G 483G 212G 70% /
tmpfs tmpfs 7,7G 75M 7,6G 1% /dev/shm
/dev/nvme0n1p5 ext4 732G 483G 212G 70% /
DistroRelease: Ubuntu 23.10
EcryptfsInUse: Yes
InstallationDate: Installed on 2019-06-12 (1777 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
Package: chromium-browser 1:85.0.4183.83-0ubuntu3
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 6.5.0-28.29-generic 6.5.13
Snap.Changes:
ID Status Spawn Ready Summary
824 Done2024-04-23T20:13:38+03:00 2024-04-23T20:28:35+03:00
Auto-refresh snap "chromium"
Snap.ChromeDriverVersion: ChromeDriver 124.0.6367.60
(8771130bd84f76d855ae42fbe02752b03e352f17-refs/branch-heads/6367@{#798})
Snap.ChromiumVersion: Chromium 124.0.6367.60 snap
Tags: mantic wayland-session
Uname: Linux 6.5.0-28-generic x86_64
UpgradeStatus: Upgraded to mantic on 2023-10-13 (194 days ago)
UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2063304/+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 2063304] ProcEnviron.txt
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/2063304/+attachment/5769948/+files/ProcEnviron.txt
--
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/2063304
Title:
chromium 124.0.6367.60 fails to draw its window
Status in chromium-browser package in Ubuntu:
New
Bug description:
Since the last snap update to 124.0.6367.60, I cannot use chromium.
It launches fine, but the window itself is fully transparent (e.g.
triggering the Overview makes it look like a piece of my wallpaper).
I have Intel graphics and use a Wayland session on Ubuntu 23.10.
At first I thought I was experiencing bug 1967488, but the more I looked at
it, the less sure I was (no Nvidia here, no issues with older snap versions, no
KMS errors in journalctl), so I'm filing a new one.
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/nvme0n1p5 ext4 732G 483G 212G 70% /
tmpfs tmpfs 7,7G 75M 7,6G 1% /dev/shm
/dev/nvme0n1p5 ext4 732G 483G 212G 70% /
DistroRelease: Ubuntu 23.10
EcryptfsInUse: Yes
InstallationDate: Installed on 2019-06-12 (1777 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
Package: chromium-browser 1:85.0.4183.83-0ubuntu3
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 6.5.0-28.29-generic 6.5.13
Snap.Changes:
ID Status Spawn Ready Summary
824 Done2024-04-23T20:13:38+03:00 2024-04-23T20:28:35+03:00
Auto-refresh snap "chromium"
Snap.ChromeDriverVersion: ChromeDriver 124.0.6367.60
(8771130bd84f76d855ae42fbe02752b03e352f17-refs/branch-heads/6367@{#798})
Snap.ChromiumVersion: Chromium 124.0.6367.60 snap
Tags: mantic wayland-session
Uname: Linux 6.5.0-28-generic x86_64
UpgradeStatus: Upgraded to mantic on 2023-10-13 (194 days ago)
UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2063304/+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 2063304] HookError_chromium_browser.txt
apport information
** Attachment added: "HookError_chromium_browser.txt"
https://bugs.launchpad.net/bugs/2063304/+attachment/5769946/+files/HookError_chromium_browser.txt
--
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/2063304
Title:
chromium 124.0.6367.60 fails to draw its window
Status in chromium-browser package in Ubuntu:
New
Bug description:
Since the last snap update to 124.0.6367.60, I cannot use chromium.
It launches fine, but the window itself is fully transparent (e.g.
triggering the Overview makes it look like a piece of my wallpaper).
I have Intel graphics and use a Wayland session on Ubuntu 23.10.
At first I thought I was experiencing bug 1967488, but the more I looked at
it, the less sure I was (no Nvidia here, no issues with older snap versions, no
KMS errors in journalctl), so I'm filing a new one.
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/nvme0n1p5 ext4 732G 483G 212G 70% /
tmpfs tmpfs 7,7G 75M 7,6G 1% /dev/shm
/dev/nvme0n1p5 ext4 732G 483G 212G 70% /
DistroRelease: Ubuntu 23.10
EcryptfsInUse: Yes
InstallationDate: Installed on 2019-06-12 (1777 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
Package: chromium-browser 1:85.0.4183.83-0ubuntu3
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 6.5.0-28.29-generic 6.5.13
Snap.Changes:
ID Status Spawn Ready Summary
824 Done2024-04-23T20:13:38+03:00 2024-04-23T20:28:35+03:00
Auto-refresh snap "chromium"
Snap.ChromeDriverVersion: ChromeDriver 124.0.6367.60
(8771130bd84f76d855ae42fbe02752b03e352f17-refs/branch-heads/6367@{#798})
Snap.ChromiumVersion: Chromium 124.0.6367.60 snap
Tags: mantic wayland-session
Uname: Linux 6.5.0-28-generic x86_64
UpgradeStatus: Upgraded to mantic on 2023-10-13 (194 days ago)
UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2063304/+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 2063304] Dependencies.txt
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/2063304/+attachment/5769945/+files/Dependencies.txt
--
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/2063304
Title:
chromium 124.0.6367.60 fails to draw its window
Status in chromium-browser package in Ubuntu:
New
Bug description:
Since the last snap update to 124.0.6367.60, I cannot use chromium.
It launches fine, but the window itself is fully transparent (e.g.
triggering the Overview makes it look like a piece of my wallpaper).
I have Intel graphics and use a Wayland session on Ubuntu 23.10.
At first I thought I was experiencing bug 1967488, but the more I looked at
it, the less sure I was (no Nvidia here, no issues with older snap versions, no
KMS errors in journalctl), so I'm filing a new one.
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/nvme0n1p5 ext4 732G 483G 212G 70% /
tmpfs tmpfs 7,7G 75M 7,6G 1% /dev/shm
/dev/nvme0n1p5 ext4 732G 483G 212G 70% /
DistroRelease: Ubuntu 23.10
EcryptfsInUse: Yes
InstallationDate: Installed on 2019-06-12 (1777 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
Package: chromium-browser 1:85.0.4183.83-0ubuntu3
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 6.5.0-28.29-generic 6.5.13
Snap.Changes:
ID Status Spawn Ready Summary
824 Done2024-04-23T20:13:38+03:00 2024-04-23T20:28:35+03:00
Auto-refresh snap "chromium"
Snap.ChromeDriverVersion: ChromeDriver 124.0.6367.60
(8771130bd84f76d855ae42fbe02752b03e352f17-refs/branch-heads/6367@{#798})
Snap.ChromiumVersion: Chromium 124.0.6367.60 snap
Tags: mantic wayland-session
Uname: Linux 6.5.0-28-generic x86_64
UpgradeStatus: Upgraded to mantic on 2023-10-13 (194 days ago)
UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2063304/+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 2063304] [NEW] chromium 124.0.6367.60 fails to draw its window
Public bug reported:
Since the last snap update to 124.0.6367.60, I cannot use chromium. It
launches fine, but the window itself is fully transparent (e.g.
triggering the Overview makes it look like a piece of my wallpaper).
I have Intel graphics and use a Wayland session on Ubuntu 23.10.
At first I thought I was experiencing bug 1967488, but the more I looked at it,
the less sure I was (no Nvidia here, no issues with older snap versions, no KMS
errors in journalctl), so I'm filing a new one.
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/nvme0n1p5 ext4 732G 483G 212G 70% /
tmpfs tmpfs 7,7G 75M 7,6G 1% /dev/shm
/dev/nvme0n1p5 ext4 732G 483G 212G 70% /
DistroRelease: Ubuntu 23.10
EcryptfsInUse: Yes
InstallationDate: Installed on 2019-06-12 (1777 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
Package: chromium-browser 1:85.0.4183.83-0ubuntu3
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 6.5.0-28.29-generic 6.5.13
Snap.Changes:
ID Status Spawn Ready Summary
824 Done2024-04-23T20:13:38+03:00 2024-04-23T20:28:35+03:00
Auto-refresh snap "chromium"
Snap.ChromeDriverVersion: ChromeDriver 124.0.6367.60
(8771130bd84f76d855ae42fbe02752b03e352f17-refs/branch-heads/6367@{#798})
Snap.ChromiumVersion: Chromium 124.0.6367.60 snap
Tags: mantic wayland-session
Uname: Linux 6.5.0-28-generic x86_64
UpgradeStatus: Upgraded to mantic on 2023-10-13 (194 days ago)
UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
** Affects: chromium-browser (Ubuntu)
Importance: Undecided
Status: New
** Tags: apport-collected mantic snap wayland-session
** Tags added: apport-collected mantic wayland-session
** Description changed:
Since the last snap update to 124.0.6367.60, I cannot use chromium. It
launches fine, but the window itself is fully transparent (e.g.
triggering the Overview makes it look like a piece of my wallpaper).
I have Intel graphics and use a Wayland session on Ubuntu 23.10.
- At first I thought I was experiencing bug 1967488, but the more I looked
- at it, the less sure I was (no Nvidia here, no issues with older snap
- versions, no KMS errors in journalctl), so I'm filing a new one.
+ At first I thought I was experiencing bug 1967488, but the more I looked at
it, the less sure I was (no Nvidia here, no issues with older snap versions, no
KMS errors in journalctl), so I'm filing a new one.
+ ---
+ ProblemType: Bug
+ ApportVersion: 2.27.0-0ubuntu5
+ Architecture: amd64
+ CasperMD5CheckResult: unknown
+ CurrentDesktop: ubuntu:GNOME
+ DiskUsage:
+ Filesystem Type Size Used Avail Use% Mounted on
+ /dev/nvme0n1p5 ext4 732G 483G 212G 70% /
+ tmpfs tmpfs 7,7G 75M 7,6G 1% /dev/shm
+ /dev/nvme0n1p5 ext4 732G 483G 212G 70% /
+ DistroRelease: Ubuntu 23.10
+ EcryptfsInUse: Yes
+ InstallationDate: Installed on 2019-06-12 (1777 days ago)
+ InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
+ Package: chromium-browser 1:85.0.4183.83-0ubuntu3
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 6.5.0-28.29-generic 6.5.13
+ Snap.Changes:
+ ID Status Spawn Ready Summary
+ 824 Done2024-04-23T20:13:38+03:00 2024-04-23T20:28:35+03:00
Auto-refresh snap "chromium"
+ Snap.ChromeDriverVersion: ChromeDriver 124.0.6367.60
(8771130bd84f76d855ae42fbe02752b03e352f17-refs/branch-heads/6367@{#798})
+ Snap.ChromiumVersion: Chromium 124.0.6367.60 snap
+ Tags: mantic wayland-session
+ Uname: Linux 6.5.0-28-generic x86_64
+ UpgradeStatus: Upgraded to mantic on 2023-10-13 (194 days ago)
+ UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo
+ _MarkForUpload: 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/2063304
Title:
chromium 124.0.6367.60 fails to draw its window
Status in chromium-browser package in Ubuntu:
New
Bug description:
Since the last snap update to 124.0.6367.60, I cannot use chromium.
It launches fine, but the window itself is fully transparent (e.g.
triggering the Overview makes it look like a piece of my wallpaper).
I have Intel graphics and use a Wayland session on Ubuntu 23.10.
At first I thought I was experiencing bug 1967488, but the more I looked at
it, the less sure I was (no Nvidia here, no issues with older snap versions, no
KMS errors in journalctl), so I'm filing a new one.
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DiskUsage:
Filesystem Type Size Used Avail Use%
[Desktop-packages] [Bug 1967488] Re: [nvidia] Chromium stable snap doesn't display anything on Wayland with Nvidia as primary GPU
That's a Chromium/Chrome regression and is not related to this Nvidia bug at all. Still, you can work around it with: google-chrome --ozone-platform=x11 -- 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/1967488 Title: [nvidia] Chromium stable snap doesn't display anything on Wayland with Nvidia as primary GPU Status in chromium-browser package in Ubuntu: Triaged Bug description: Hi I'm testing the Ubuntu 22.04 beta with wayland and when I try to open the Chromium browser (stable snap package), only see a black/transparent window. If I switch from Wayland to Xorg, everything is normal again. I tried to delete the profile folder , but I have the same result. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1967488/+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 2062146] Re: Raspberry Pi: webkit2gtk apps crash with SIGSEGV in v3d_load_utile
** Changed in: mesa (Ubuntu) Status: Invalid => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yelp in Ubuntu. https://bugs.launchpad.net/bugs/2062146 Title: Raspberry Pi: webkit2gtk apps crash with SIGSEGV in v3d_load_utile Status in Mesa: New Status in mesa package in Ubuntu: Triaged Status in webkit2gtk package in Ubuntu: In Progress Status in yelp package in Ubuntu: New Bug description: MiniBrowser crashed immediately on Raspberry Pi 400. ProblemType: Crash DistroRelease: Ubuntu 24.04 Package: libwebkit2gtk-4.1-0 2.44.0-2 ProcVersionSignature: Ubuntu 6.8.0-1002.2-raspi 6.8.1 Uname: Linux 6.8.0-1002-raspi aarch64 ApportVersion: 2.28.0-0ubuntu1 Architecture: arm64 CasperMD5CheckResult: unknown CloudArchitecture: aarch64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CurrentDesktop: ubuntu:GNOME Date: Thu Apr 18 17:32:12 2024 ExecutablePath: /usr/lib/aarch64-linux-gnu/webkit2gtk-4.1/MiniBrowser JournalErrors: -- No entries -- ProcCmdline: ./MiniBrowser ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= Signal: 11 SignalName: SIGSEGV SourcePackage: webkit2gtk StacktraceTop: ?? () from /usr/lib/aarch64-linux-gnu/dri/vc4_dri.so ?? () from /usr/lib/aarch64-linux-gnu/dri/vc4_dri.so ?? () from /usr/lib/aarch64-linux-gnu/dri/vc4_dri.so ?? () from /lib/aarch64-linux-gnu/libgbm.so.1 ?? () from /lib/aarch64-linux-gnu/libwebkit2gtk-4.1.so.0 Title: MiniBrowser crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/2062146/+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 2061882] Re: Thunderbird snap loses local folder settings in 24.04
Alright but I still don't understand what 'the local folders do not import from the deb Thunderbird' means so the report is of no use to us unless you are able to explain what your issue is... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/2061882 Title: Thunderbird snap loses local folder settings in 24.04 Status in thunderbird package in Ubuntu: Invalid Bug description: After Thunderbird snap installs the local folders do not import from the deb Thunderbird. There also seems to be no way to get back to the deb version. I needed to manually move the local directory back to the original. I can no longer see my inbox and it keeps telling me that the /home/me/snap/thunderbird/hdd/home/me/.thunderbird/24a1u6qp.default/ImapMail/ is invalid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/2061882/+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 2062146] Re: Raspberry Pi: webkit2gtk apps crash with SIGSEGV in v3d_load_utile
Thank you for your report! However, processing it in order to get sufficient information for the developers failed as the report has a core dump which is invalid. The corruption may have happened on the system which the crash occurred or during transit. Thank you for your understanding, and sorry for the inconvenience! ** Changed in: mesa (Ubuntu) Status: Triaged => Invalid ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/2062146/+attachment/5767410/+files/CoreDump.gz ** Tags removed: need-arm64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yelp in Ubuntu. https://bugs.launchpad.net/bugs/2062146 Title: Raspberry Pi: webkit2gtk apps crash with SIGSEGV in v3d_load_utile Status in Mesa: New Status in mesa package in Ubuntu: Invalid Status in webkit2gtk package in Ubuntu: In Progress Status in yelp package in Ubuntu: New Bug description: MiniBrowser crashed immediately on Raspberry Pi 400. ProblemType: Crash DistroRelease: Ubuntu 24.04 Package: libwebkit2gtk-4.1-0 2.44.0-2 ProcVersionSignature: Ubuntu 6.8.0-1002.2-raspi 6.8.1 Uname: Linux 6.8.0-1002-raspi aarch64 ApportVersion: 2.28.0-0ubuntu1 Architecture: arm64 CasperMD5CheckResult: unknown CloudArchitecture: aarch64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CurrentDesktop: ubuntu:GNOME Date: Thu Apr 18 17:32:12 2024 ExecutablePath: /usr/lib/aarch64-linux-gnu/webkit2gtk-4.1/MiniBrowser JournalErrors: -- No entries -- ProcCmdline: ./MiniBrowser ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= Signal: 11 SignalName: SIGSEGV SourcePackage: webkit2gtk StacktraceTop: ?? () from /usr/lib/aarch64-linux-gnu/dri/vc4_dri.so ?? () from /usr/lib/aarch64-linux-gnu/dri/vc4_dri.so ?? () from /usr/lib/aarch64-linux-gnu/dri/vc4_dri.so ?? () from /lib/aarch64-linux-gnu/libgbm.so.1 ?? () from /lib/aarch64-linux-gnu/libwebkit2gtk-4.1.so.0 Title: MiniBrowser crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/2062146/+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 1967488] Re: [nvidia] Chromium stable snap doesn't display anything on Wayland with Nvidia as primary GPU
I have the same problem but with Intel video. Chromium 124.0.6367.60 shows up camouflaged as my desktop wallpaper after the last snap update. -- 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/1967488 Title: [nvidia] Chromium stable snap doesn't display anything on Wayland with Nvidia as primary GPU Status in chromium-browser package in Ubuntu: Triaged Bug description: Hi I'm testing the Ubuntu 22.04 beta with wayland and when I try to open the Chromium browser (stable snap package), only see a black/transparent window. If I switch from Wayland to Xorg, everything is normal again. I tried to delete the profile folder , but I have the same result. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1967488/+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 2061293] Re: package libreoffice-impress 1:7.3.7-0ubuntu0.22.04.4 failed to install/upgrade: installed libreoffice-impress package post-installation script subprocess returned
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/2061293 Title: package libreoffice-impress 1:7.3.7-0ubuntu0.22.04.4 failed to install/upgrade: installed libreoffice-impress package post- installation script subprocess returned error exit status 1 Status in libreoffice package in Ubuntu: New Bug description: marina@marina-Latitude-7400-2-in-1:~$ sudo dpkg --configure -a Setting up ubuntu-desktop-minimal (1.481.1) ... Setting up libreoffice-impress (1:7.3.7-0ubuntu0.22.04.4) ... dpkg-divert: error: parsing file '/var/lib/dpkg/updates/0241' near line 0: newline in field name '#padding' dpkg: error processing package libreoffice-impress (--configure): installed libreoffice-impress package post-installation script subprocess returned error exit status 2 Setting up libreoffice-base-core (1:7.3.7-0ubuntu0.22.04.4) ... Setting up libreoffice-help-en-us (1:7.3.7-0ubuntu0.22.04.4) ... dpkg: unrecoverable fatal error, aborting: unable to install updated status of 'libreoffice-help-en-us': No such file or directory ProblemType: Package DistroRelease: Ubuntu 22.04 Package: libreoffice-impress 1:7.3.7-0ubuntu0.22.04.4 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Sun Apr 14 23:11:31 2024 DuplicateSignature: package:libreoffice-impress:1:7.3.7-0ubuntu0.22.04.4 Setting up libreoffice-impress (1:7.3.7-0ubuntu0.22.04.4) ... debconf: DbDriver "templatedb": /var/cache/debconf/templates.dat is locked by another process: Resource temporarily unavailable dpkg: error processing package libreoffice-impress (--configure): installed libreoffice-impress package post-installation script subprocess returned error exit status 1 ErrorMessage: installed libreoffice-impress package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2024-04-14 (0 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.3 apt 2.4.12 SourcePackage: libreoffice Title: package libreoffice-impress 1:7.3.7-0ubuntu0.22.04.4 failed to install/upgrade: installed libreoffice-impress package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2061293/+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
