[Desktop-packages] [Bug 2054769] Re: Boot animation and login screen use different display scales
** Changed in: plymouth (Ubuntu) Status: Fix Committed => In Progress ** Tags added: mantic -- 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/2054769 Title: Boot animation and login screen use different display scales Status in Plymouth: New Status in mutter package in Ubuntu: Won't Fix Status in plymouth package in Ubuntu: In Progress Bug description: Boot animation and login screen use different display scales, on some (not many) machines. For example on a Microsoft Surface Laptop 4, Plymouth seems to use scale 2 for the boot screen while GNOME selects scale 1 for the login screen. This means the Ubuntu logo shrinks. I've tried a few laptops and so far it's only the Surface Laptop 4 that has the problem: 13.5" 2256x1504, 201 PPI To manage notifications about this bug go to: https://bugs.launchpad.net/plymouth/+bug/2054769/+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 1758512] Re: No virtual terminals (CTRL+ALT+F?) when no user logged in
Indeed this doesn't seem to have happened since 2020. ** No longer affects: mutter (Ubuntu) ** No longer affects: plasma-desktop (Ubuntu) ** Changed in: gdm3 (Ubuntu) Status: Confirmed => Fix Released ** Changed in: linux (Ubuntu) Status: Confirmed => 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/1758512 Title: No virtual terminals (CTRL+ALT+F?) when no user logged in Status in gdm3 package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: As of today's 18.04 version, on a dell xps-13 (the old i7-4500U one), to reproduce: - boot Ubuntu - Press Ctrl+Alt+F2 (or F3 or...) Expected behaviour: virtual console should appear with login prompt. Actual behaviour: nothing happens. When a user is logged in, Ctrl+Alt+F3 switches to terminal tty3... However, hitting first Ctrl+Alt+F1 and, subsequently, hitting Ctrl+Alt+F3 does not show tty3, and remains at the graphical login screen but keyboard and mouse are unresponsive until either Ctrl+Alt+F1 or Ctrl+Alt+F? are pressed, being ? the virtual terminal the ubuntu session is running at. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.27.92-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Mar 24 10:11:26 2018 InstallationDate: Installed on 2014-05-05 (1418 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: Upgraded to bionic on 2018-03-22 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1758512/+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 1891783] Re: autologin breaks keyboard and mouse in GDM3
** Package changed: plasma-desktop (Ubuntu) => gdm3 (Ubuntu) -- 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/1891783 Title: autologin breaks keyboard and mouse in GDM3 Status in gdm3 package in Ubuntu: New Bug description: After upgrade from 19.10 to 20.04, mouse and keyboard are unresponsive. Re-installing does not fix the problem. Problem is not apparent in KDE or LightDM. Three workarounds have been found so far: 1. Boot into recovery mode, then exit to normal boot via "resume" 2. Disable autologin. Allows normal bootup via login screen 3. Install alternative desktop manager such as KDE Plasma or LightDM. Source package is unknown Release: Ubuntu 20.04 and 20.04.1 Expected behaviour: System boots directly into desktop, mouse and keyboard both work as normal Actual behaviour: Mouse and keyboard are non-responsive unless autologin is disabled. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1891783/+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 1891783] [NEW] autologin breaks keyboard and mouse in GDM3
You have been subscribed to a public bug: After upgrade from 19.10 to 20.04, mouse and keyboard are unresponsive. Re-installing does not fix the problem. Problem is not apparent in KDE or LightDM. Three workarounds have been found so far: 1. Boot into recovery mode, then exit to normal boot via "resume" 2. Disable autologin. Allows normal bootup via login screen 3. Install alternative desktop manager such as KDE Plasma or LightDM. Source package is unknown Release: Ubuntu 20.04 and 20.04.1 Expected behaviour: System boots directly into desktop, mouse and keyboard both work as normal Actual behaviour: Mouse and keyboard are non-responsive unless autologin is disabled. ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: auto-login keyboard mouse -- autologin breaks keyboard and mouse in GDM3 https://bugs.launchpad.net/bugs/1891783 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 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 2004532] Re: Hardware acceleration broken for amdgpu/mesa in snap
** Changed in: chromium-browser (Ubuntu)
Status: Fix Committed => 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/2004532
Title:
Hardware acceleration broken for amdgpu/mesa in snap
Status in ubuntu-spotify-app:
New
Status in chromium-browser package in Ubuntu:
Confirmed
Status in firefox package in Ubuntu:
Fix Released
Bug description:
Snap packages which use hardware accelerated graphics are broken after
the last routine system upgrade via apt. My system is using AMD Radeon
RX 5500 XT graphics card from ASUS, with stock amdgpu kernel drivers.
Two snap packages which are now unusable are Mozilla Firefox and
Chromium browsers. Both display animated speckled color garbage inside
their windows, overlayed with the correct image. Disabling hardware
acceleration in the settings for the snap version of Firefox fixed it.
Also, Firefox version installed from the original Mozilla tarball into
/opt/ works just fine with the acceleration enabled on the same
system, as well as glmark2 benchmark. Looks like the issue is only
affecting snap packages.
$ snap list firefox chromium
Name Version Rev Tracking Publisher Notes
chromium 109.0.5414.119 2295 latest/stable canonical✓ -
firefox 109.0.1-1 2311 latest/stable mozilla✓-
$ dpkg -l snapd|grep ^ii
ii snapd 2.58+22.10 amd64Daemon and tooling that enable
snap packages
$ dpkg -l mesa\* | grep ^ii
ii mesa-utils8.5.0-1 amd64Miscellaneous
Mesa utilities -- symlinks
ii mesa-utils-bin:amd64 8.5.0-1 amd64Miscellaneous
Mesa utilities -- native applications
ii mesa-va-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa VA-API
video acceleration drivers
ii mesa-vdpau-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa VDPAU video
acceleration drivers
ii mesa-vulkan-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa Vulkan
graphics drivers
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 22.10
Release:22.10
Codename: kinetic
$ uname -a
Linux xx 5.19.0-29-generic #30-Ubuntu SMP PREEMPT_DYNAMIC Wed Jan 4
12:14:09 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: snap (not installed)
ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17
Uname: Linux 5.19.0-29-generic x86_64
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Wed Feb 1 22:55:48 2023
InstallationDate: Installed on 2020-08-02 (913 days ago)
InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
SourcePackage: snap
UpgradeStatus: Upgraded to kinetic on 2023-02-02 (0 days ago)
---
ProblemType: Bug
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
DRM.card0-DP-1:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAebQd34yoBAAQcAQS1PCJ4nz4xrlBHrCcMUFQhCABxQIGAgcCpwNHAgQABAQEBTdAAoPBwPoAwIGUMWFQhAAAaKGgAoPBwPoAIkGUMWFQhAAAa/QAwPYeHOAEKICAgICAg/ABMRyBIRFIgNEsKICAgAfsCAxlxRJAEAwEjCQcHgwEAAOMFwADjBgUBAjqAGHE4LUBYLEUAWFQhAAAeVl4AoKCgKVAwIDUAWFQhAAAaKQ==
modes: 3840x2160 3840x2160 3840x2160 3840x2160 3840x2160 2560x1440 1920x1200
1920x1080 1920x1080 1920x1080 1600x1200 1680x1050 1600x900 1280x1024 1440x900
1280x800 1152x864 1280x720 1280x720 1280x720 1024x768 800x600 720x480 720x480
640x480 640x480 640x480
DRM.card0-DP-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-DP-3:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/nvme0n1p2 ext4 916G 222G 648G 26% /
tmpfs tmpfs 16G 0 16G 0% /dev/shm
/dev/nvme0n1p2 ext4 916G 222G 648G 26% /
DistroRelease: Ubuntu 22.10
InstallationDate: Installed on 2020-08-02 (914 days ago)
InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: ASUS System Product Name
Package: chromium-browser 1:85.0.4183.83-0ubuntu2
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-29-generic
root=UUID=1a37d538-d59f-477b-96f0-f949ce9b4553 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17
Snap.Changes: no changes found
Snap.ChromeDriverVersion: ChromeDriver 109.0.5414.119
(772095164c7d5d4e73160f858efed3b5e87eca83-refs/branch-heads/5414@{#1458})
[Desktop-packages] [Bug 1758512] Re: No virtual terminals (CTRL+ALT+F?) when no user logged in
I cannot reproduce this on noble ( plasma-desktop ) I logged out, CTRL+ALT+F? worked as expected. ** Changed in: plasma-desktop (Ubuntu) Status: Confirmed => Incomplete -- 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/1758512 Title: No virtual terminals (CTRL+ALT+F?) when no user logged in Status in gdm3 package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in plasma-desktop package in Ubuntu: Incomplete Bug description: As of today's 18.04 version, on a dell xps-13 (the old i7-4500U one), to reproduce: - boot Ubuntu - Press Ctrl+Alt+F2 (or F3 or...) Expected behaviour: virtual console should appear with login prompt. Actual behaviour: nothing happens. When a user is logged in, Ctrl+Alt+F3 switches to terminal tty3... However, hitting first Ctrl+Alt+F1 and, subsequently, hitting Ctrl+Alt+F3 does not show tty3, and remains at the graphical login screen but keyboard and mouse are unresponsive until either Ctrl+Alt+F1 or Ctrl+Alt+F? are pressed, being ? the virtual terminal the ubuntu session is running at. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.27.92-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Mar 24 10:11:26 2018 InstallationDate: Installed on 2014-05-05 (1418 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: Upgraded to bionic on 2018-03-22 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1758512/+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 2009712] Re: Gnome lock screen loses focus if a window opens while screen is locked
** Information type changed from Public to Public Security -- 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/2009712 Title: Gnome lock screen loses focus if a window opens while screen is locked Status in gnome-shell package in Ubuntu: Triaged Bug description: The Gnome lock screen has caused me a lot of frustration over time, since I've often found that is unresponsive to the keyboard when I come back to the system and try to get back in after the screen lock has activated. I finally realized that this is usually due to the "Software Updater" window popping up while I'm away from the computer, though it can be triggered by any window opening while the screen is locked. To reproduce: Open a terminal window and type "sleep 15; gnome-terminal", then immediately click on the upper-right notification area and select the "Lock" option in the popup menu. Observe the screen go into lock. Wait 15 seconds. Press a key like Ctrl or Alt to wake the screen. Attempt to type in the password (or use a fingerprint reader if you have one). Nothing happens. Click the screen (or possibly tap/swipe it if you have a touchscreen). The password prompt will now appear, and it should be possible to type in the password (or use the fingerprint reader) This is a very annoying behavior. It shouldn't be necessary to click/tap the screen to restore focus when the whole desktop has been taken over by the screen locker. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.4-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 Uname: Linux 5.15.0-50-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Mar 8 08:21:43 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-10-13 (146 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.2-0ubuntu1 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/2009712/+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 2056506] Re: GNOME Shell crashes when I close any application
That's very unusual. Please start by deleting any local extensions: cd ~/.local/share/gnome-shell/ rm -rf extensions and then log in again. If the bug still occurs after that then 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. ** Tags added: noble ** 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/2056506 Title: GNOME Shell crashes when I close any application Status in gnome-shell package in Ubuntu: Incomplete Bug description: I'm using Noble for sometime and I'm having a very annoying and odd problem: everytime I close an application on x11 (Wayland doesn't work any better) clicking with the right button in the dock and choosing "Quit" I got that screen saying that something went wrong and I need to close the session and start over. Please, let me know what logs do you need. I couldn't find any meaningful information by myself. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2056506/+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 2056506] [NEW] GNOME Shell crashes when I close any application
Public bug reported: I'm using Noble for sometime and I'm having a very annoying and odd problem: everytime I close an application on x11 (Wayland doesn't work any better) clicking with the right button in the dock and choosing "Quit" I got that screen saying that something went wrong and I need to close the session and start over. Please, let me know what logs do you need. I couldn't find any meaningful information by myself. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- 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/2056506 Title: GNOME Shell crashes when I close any application Status in gnome-shell package in Ubuntu: New Bug description: I'm using Noble for sometime and I'm having a very annoying and odd problem: everytime I close an application on x11 (Wayland doesn't work any better) clicking with the right button in the dock and choosing "Quit" I got that screen saying that something went wrong and I need to close the session and start over. Please, let me know what logs do you need. I couldn't find any meaningful information by myself. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2056506/+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 2051074] Re: Mirror mode doesn't work when panel only supports one refresh rate with reduced blanking
Kai-Heng Feng, please remember to verify mantic. -- 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/2051074 Title: Mirror mode doesn't work when panel only supports one refresh rate with reduced blanking Status in HWE Next: New Status in OEM Priority Project: New Status in mutter package in Ubuntu: Fix Committed Status in mutter source package in Jammy: Fix Committed Status in mutter source package in Mantic: Fix Committed Status in mutter source package in Noble: Fix Committed Bug description: [Impact] On systems equipped with reduced blanking panel, mirror mode can result to no image on external monitor. The reason is due to current fallback modes don't have pixelclock for reduced blanking, so inadequate refresh rate is used to mode set, and result with atomic commit failure. [Fix] https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3449 Add reduced blanking (RB) to fallback modes, so mutter can use RB mode to meet pixelclock requirement in order to pick the right refresh rate. [Test] Connect an external monitor to affected system. Use the monitor hotkey to switch to mirror mode or use GNOME control center to choose mirror mode. With the patch included, the issue is no longer observed. [Where problems could occur] The modelines of reduced blanking have reversed Hsync and Vsync flags, so if the driver doesn't handle those flags correctly, the atomic modeset/commit may fail. I haven't observe any issue on Intel/AMD/Nvidia GPU so far. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2051074/+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 2056500] Re: missing words in /usr/share/dict/words
it looks like I needed to install wamerican-insane then run sudo select-default-wordlist ** Changed in: scowl (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to scowl in Ubuntu. https://bugs.launchpad.net/bugs/2056500 Title: missing words in /usr/share/dict/words Status in scowl package in Ubuntu: Invalid Bug description: ``` luke@opus91:~$ dpkg -S /usr/share/dict/words wamerican: /usr/share/dict/words luke@opus91:~$ luke@opus91:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 22.04.3 LTS Release:22.04 Codename: jammy luke@opus91:~$ ``` ```grep tuck /usr/share/dict/words ``` shows that the following words (minimally) are missing: ``` tuckahoe tuckahoe tuckshops untuck untucked untucks untucking tuckerization tuckedly stuckism ``` all of which show up on https://www.thefreedictionary.com/words- containing-tuck and some of which are used in the NY Times spelling bee game. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: wamerican 2020.12.07-2 ProcVersionSignature: Ubuntu 6.2.0-1017.17~22.04.1-aws 6.2.16 Uname: Linux 6.2.0-1017-aws x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CloudArchitecture: x86_64 CloudID: aws CloudName: aws CloudPlatform: ec2 CloudRegion: us-east-1 CloudSubPlatform: metadata (http://169.254.169.254) Date: Thu Mar 7 22:21:42 2024 Ec2AMI: ami-0c7217cdde317cfec Ec2AMIManifest: (unknown) Ec2Architecture: x86_64 Ec2AvailabilityZone: us-east-1a Ec2Imageid: ami-0c7217cdde317cfec Ec2InstanceType: t3.medium Ec2Instancetype: t3.medium Ec2Kernel: unavailable Ec2Ramdisk: unavailable Ec2Region: us-east-1 PackageArchitecture: all RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: scowl UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/scowl/+bug/2056500/+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 2051074] Re: Mirror mode doesn't work when panel only supports one refresh rate with reduced blanking
That failing test case: 1180s # FAIL: mutter-13/minimized.test (Child process exited with code 133) is known to be flaky. I've seen it fail on unrelated changes upstream. And it is indeed unrelated to these changes. The rebuild has now succeeded: https://launchpad.net/ubuntu/+source/mutter/45.2-0ubuntu4 -- 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/2051074 Title: Mirror mode doesn't work when panel only supports one refresh rate with reduced blanking Status in HWE Next: New Status in OEM Priority Project: New Status in mutter package in Ubuntu: Fix Committed Status in mutter source package in Jammy: Fix Committed Status in mutter source package in Mantic: Fix Committed Status in mutter source package in Noble: Fix Committed Bug description: [Impact] On systems equipped with reduced blanking panel, mirror mode can result to no image on external monitor. The reason is due to current fallback modes don't have pixelclock for reduced blanking, so inadequate refresh rate is used to mode set, and result with atomic commit failure. [Fix] https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3449 Add reduced blanking (RB) to fallback modes, so mutter can use RB mode to meet pixelclock requirement in order to pick the right refresh rate. [Test] Connect an external monitor to affected system. Use the monitor hotkey to switch to mirror mode or use GNOME control center to choose mirror mode. With the patch included, the issue is no longer observed. [Where problems could occur] The modelines of reduced blanking have reversed Hsync and Vsync flags, so if the driver doesn't handle those flags correctly, the atomic modeset/commit may fail. I haven't observe any issue on Intel/AMD/Nvidia GPU so far. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2051074/+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 2054510] Re: Incomplete screen redraws in virtual machines running Xorg
That failing test case: 1180s # FAIL: mutter-13/minimized.test (Child process exited with code 133) is known to be flaky. I've seen it fail on unrelated changes upstream. And it is indeed unrelated to these changes. The rebuild has now succeeded: https://launchpad.net/ubuntu/+source/mutter/45.2-0ubuntu4 -- 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/2054510 Title: Incomplete screen redraws in virtual machines running Xorg Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Committed Status in mutter source package in Jammy: Fix Committed Status in mutter source package in Mantic: Fix Committed Status in mutter source package in Noble: Fix Committed Bug description: [ Impact ] When using software rendering on Xorg (so usually just in VMs), some parts of app windows may fail to redraw. https://gitlab.gnome.org/GNOME/mutter/-/issues/2880 [ Test Plan ] 1. Set up a virtual machine without graphics acceleration. 2. Log into 'Ubuntu on Xorg'. 3. Open Settings > About and verify Graphics = llvmpipe (or "Software Rendering"), and Windowing System = X11. 4. sudo snap install chromium 5. Open Chromium and find a web page with lots of text. Plain text without any links and staying at the top of the page will work best because you don't want to trigger any scrolling. 6. Start selecting text with the mouse and while holding the button move the mouse up and down rapidly. Avoid triggering any page scrolling. 7. Release the mouse button in roughly the middle of the area of text that was selected. 8. Verify the remaining text selection is contiguous and not broken into multiple disconnected text selections (the bug). 9. Repeat steps 7 and 8 several times to be sure. [ Where problems could occur ] The fix adds a new synchronization point between the compositor and X server. This should be inconsequential, although there is a "sync ring" in mutter used for this, and if a mistake occurs there then other parts of the desktop could appear to stop responding in Xorg sessions. [ Other Info ] This is a regression that started in 3.37.3 due to https://gitlab.gnome.org/GNOME/mutter/-/commit/551101c65cda. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2054510/+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 2056500] [NEW] missing words in /usr/share/dict/words
Public bug reported: ``` luke@opus91:~$ dpkg -S /usr/share/dict/words wamerican: /usr/share/dict/words luke@opus91:~$ luke@opus91:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 22.04.3 LTS Release:22.04 Codename: jammy luke@opus91:~$ ``` ```grep tuck /usr/share/dict/words ``` shows that the following words (minimally) are missing: ``` tuckahoe tuckahoe tuckshops untuck untucked untucks untucking tuckerization tuckedly stuckism ``` all of which show up on https://www.thefreedictionary.com/words- containing-tuck and some of which are used in the NY Times spelling bee game. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: wamerican 2020.12.07-2 ProcVersionSignature: Ubuntu 6.2.0-1017.17~22.04.1-aws 6.2.16 Uname: Linux 6.2.0-1017-aws x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CloudArchitecture: x86_64 CloudID: aws CloudName: aws CloudPlatform: ec2 CloudRegion: us-east-1 CloudSubPlatform: metadata (http://169.254.169.254) Date: Thu Mar 7 22:21:42 2024 Ec2AMI: ami-0c7217cdde317cfec Ec2AMIManifest: (unknown) Ec2Architecture: x86_64 Ec2AvailabilityZone: us-east-1a Ec2Imageid: ami-0c7217cdde317cfec Ec2InstanceType: t3.medium Ec2Instancetype: t3.medium Ec2Kernel: unavailable Ec2Ramdisk: unavailable Ec2Region: us-east-1 PackageArchitecture: all RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: scowl UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: scowl (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ec2-images jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to scowl in Ubuntu. https://bugs.launchpad.net/bugs/2056500 Title: missing words in /usr/share/dict/words Status in scowl package in Ubuntu: New Bug description: ``` luke@opus91:~$ dpkg -S /usr/share/dict/words wamerican: /usr/share/dict/words luke@opus91:~$ luke@opus91:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 22.04.3 LTS Release:22.04 Codename: jammy luke@opus91:~$ ``` ```grep tuck /usr/share/dict/words ``` shows that the following words (minimally) are missing: ``` tuckahoe tuckahoe tuckshops untuck untucked untucks untucking tuckerization tuckedly stuckism ``` all of which show up on https://www.thefreedictionary.com/words- containing-tuck and some of which are used in the NY Times spelling bee game. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: wamerican 2020.12.07-2 ProcVersionSignature: Ubuntu 6.2.0-1017.17~22.04.1-aws 6.2.16 Uname: Linux 6.2.0-1017-aws x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CloudArchitecture: x86_64 CloudID: aws CloudName: aws CloudPlatform: ec2 CloudRegion: us-east-1 CloudSubPlatform: metadata (http://169.254.169.254) Date: Thu Mar 7 22:21:42 2024 Ec2AMI: ami-0c7217cdde317cfec Ec2AMIManifest: (unknown) Ec2Architecture: x86_64 Ec2AvailabilityZone: us-east-1a Ec2Imageid: ami-0c7217cdde317cfec Ec2InstanceType: t3.medium Ec2Instancetype: t3.medium Ec2Kernel: unavailable Ec2Ramdisk: unavailable Ec2Region: us-east-1 PackageArchitecture: all RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: scowl UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/scowl/+bug/2056500/+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 2051074] Autopkgtest regression report (mutter/45.2-0ubuntu4)
All autopkgtests for the newly accepted mutter (45.2-0ubuntu4) for mantic have finished running. The following regressions have been reported in tests triggered by the package: mutter/45.2-0ubuntu4 (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/mantic/update_excuses.html#mutter [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/2051074 Title: Mirror mode doesn't work when panel only supports one refresh rate with reduced blanking Status in HWE Next: New Status in OEM Priority Project: New Status in mutter package in Ubuntu: Fix Committed Status in mutter source package in Jammy: Fix Committed Status in mutter source package in Mantic: Fix Committed Status in mutter source package in Noble: Fix Committed Bug description: [Impact] On systems equipped with reduced blanking panel, mirror mode can result to no image on external monitor. The reason is due to current fallback modes don't have pixelclock for reduced blanking, so inadequate refresh rate is used to mode set, and result with atomic commit failure. [Fix] https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3449 Add reduced blanking (RB) to fallback modes, so mutter can use RB mode to meet pixelclock requirement in order to pick the right refresh rate. [Test] Connect an external monitor to affected system. Use the monitor hotkey to switch to mirror mode or use GNOME control center to choose mirror mode. With the patch included, the issue is no longer observed. [Where problems could occur] The modelines of reduced blanking have reversed Hsync and Vsync flags, so if the driver doesn't handle those flags correctly, the atomic modeset/commit may fail. I haven't observe any issue on Intel/AMD/Nvidia GPU so far. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2051074/+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 2054510] Autopkgtest regression report (mutter/45.2-0ubuntu4)
All autopkgtests for the newly accepted mutter (45.2-0ubuntu4) for mantic have finished running. The following regressions have been reported in tests triggered by the package: mutter/45.2-0ubuntu4 (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/mantic/update_excuses.html#mutter [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/2054510 Title: Incomplete screen redraws in virtual machines running Xorg Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Committed Status in mutter source package in Jammy: Fix Committed Status in mutter source package in Mantic: Fix Committed Status in mutter source package in Noble: Fix Committed Bug description: [ Impact ] When using software rendering on Xorg (so usually just in VMs), some parts of app windows may fail to redraw. https://gitlab.gnome.org/GNOME/mutter/-/issues/2880 [ Test Plan ] 1. Set up a virtual machine without graphics acceleration. 2. Log into 'Ubuntu on Xorg'. 3. Open Settings > About and verify Graphics = llvmpipe (or "Software Rendering"), and Windowing System = X11. 4. sudo snap install chromium 5. Open Chromium and find a web page with lots of text. Plain text without any links and staying at the top of the page will work best because you don't want to trigger any scrolling. 6. Start selecting text with the mouse and while holding the button move the mouse up and down rapidly. Avoid triggering any page scrolling. 7. Release the mouse button in roughly the middle of the area of text that was selected. 8. Verify the remaining text selection is contiguous and not broken into multiple disconnected text selections (the bug). 9. Repeat steps 7 and 8 several times to be sure. [ Where problems could occur ] The fix adds a new synchronization point between the compositor and X server. This should be inconsequential, although there is a "sync ring" in mutter used for this, and if a mistake occurs there then other parts of the desktop could appear to stop responding in Xorg sessions. [ Other Info ] This is a regression that started in 3.37.3 due to https://gitlab.gnome.org/GNOME/mutter/-/commit/551101c65cda. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2054510/+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 2055351] Re: [amdgpu] Firefox and Chromium browser windows are corrupt in Xorg
I encountered the same kind of corruption on AMD graphics last night. Using Firefox on Wayland in Ubuntu 24.04. -- 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/2055351 Title: [amdgpu] Firefox and Chromium browser windows are corrupt in Xorg Status in mesa package in Ubuntu: New Status in xserver-xorg-video-amdgpu package in Ubuntu: New Bug description: I downloaded the 22.04.4 iso and did a fresh install on an AMD Athlon 200GE using built-in graphics. (Radeon™ Vega 3 Graphics) Firefox and Chromium browsers had their windows corrupted to the point where they were unreadable. I think this is an xorg bug, because when I installed Wayland and logged in with a Wayland session, the browsers displayed correctly. Same behaviour with an Athlon 220GE. KDE or Ubuntu's Gnome desktop made no difference - it seemed to be xorg vs Wayland that was the critical difference. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistroCodename: jammy DistroRelease: Ubuntu 22.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] (rev cb) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. PRIME Motherboard [1043:876b] InstallationDate: Installed on 2024-02-26 (3 days ago) InstallationMedia: Kubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240216.1) MachineType: System manufacturer System Product Name Package: xorg-server (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-21-generic root=UUID=7e6c3c76-1566-4670-97ab-3755e9a04b18 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-21.21~22.04.1-generic 6.5.8 Tags: jammy wayland-session ubuntu Uname: Linux 6.5.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/04/2023 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 6210 dmi.board.asset.tag: Default string dmi.board.name: PRIME A320M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr6210:bd09/04/2023:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEA320M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1~22.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 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 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistroCodename: jammy DistroRelease: Ubuntu 22.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] (rev cb) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. PRIME Motherboard [1043:876b] InstallationDate: Installed on 2024-02-26 (3 days ago) InstallationMedia: Kubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240216.1) MachineType: System manufacturer System Product Name Package: xorg-server (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-21-generic root=UUID=7e6c3c76-1566-4670-97ab-3755e9a04b18 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-21.21~22.04.1-generic 6.5.8 Tags: jammy ubuntu Uname: Linux 6.5.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True
[Desktop-packages] [Bug 2056331] Re: [SRU] fix suspend/resume when there are no input devices
** Also affects: xorg-server (Ubuntu Noble) Importance: Medium Status: Triaged ** Also affects: xorg-server (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: xorg-server (Ubuntu Jammy) Status: New => In Progress ** Changed in: xorg-server (Ubuntu Noble) Status: Triaged => In Progress ** Changed in: xorg-server (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: xorg-server (Ubuntu Jammy) Assignee: (unassigned) => Talha Can Havadar (tchavadar) ** Changed in: xorg-server (Ubuntu Noble) Assignee: (unassigned) => Talha Can Havadar (tchavadar) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/2056331 Title: [SRU] fix suspend/resume when there are no input devices Status in X.Org X server: Fix Released Status in xorg-server package in Ubuntu: In Progress Status in xorg-server source package in Jammy: In Progress Status in xorg-server source package in Noble: In Progress Bug description: [Impact] Bug is impacting the suspend/resume flow when there is no input device connected to machine. xorg hangs in this case. [Where problems could occur] The problem could occur in places where there is no input device connected to the system but a suspend/resume is triggered. [Test Case] * Enable proposed updates (https://wiki.ubuntu.com/Testing/EnableProposed) * Update xorg-server to the version in -proposed: sudo apt install -t jammy-proposed xorg-server * Unplug all USB devices such as USB drive, keyboard, mouse, etc. * Set RTC timer and suspend the system via UART console $ echo 8 > /proc/sys/kernel/printk $ sudo rtcwake -v -m no -s 240 $ sudo systemctl suspend [Regression Potential] The patch defines a default behavior in systemd_logind_drop_master function so there is a possibility that there might be a regression that may affect all the systems that utilizes systemd_logind_drop_master Upstream Bug: https://gitlab.freedesktop.org/xorg/xserver/-/issues/1387 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/2056331/+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 2056494] [NEW] Snap profile import fails with EPERM
Public bug reported: A regular noble full-upgrade transitioned my laptop to the thunderbird snap this morning, and I ended up with no profile due to an EPERM reading ~/.thunderbird during the migration. thunderbird.launcher says it needs personal-files, but the thunderbird snap doesn't seem to have that plug. wgrant@vanth:~$ thunderbird du: cannot read directory '/home/wgrant/.thunderbird': Permission denied Importing existing thunderbird profiles from /home/wgrant/.thunderbird cp: cannot stat '/home/wgrant/.thunderbird/*': No such file or directory Usage: /snap/thunderbird/450/patch-default-profile.py /path/to/profiles_dir/profiles.ini Import done in 0.029 s wgrant@vanth:~$ ls -ld /home/wgrant/.thunderbird drwx-- 6 wgrant wgrant 4096 Aug 13 2020 /home/wgrant/.thunderbird wgrant@vanth:~$ dpkg -l thunderbird | tail -n1 ii thunderbird1:115.8.1+build1+snap2 amd64Transitional package - thunderbird -> thunderbird snap wgrant@vanth:~$ snap info thunderbird | tail -n1 installed: 115.8.1-2(450) 145MB - wgrant@vanth:~$ snap connections thunderbird Interface Plug Slot Notes audio-playback thunderbird:audio-playback:audio-playback - avahi-observe thunderbird:avahi-observe - - browser-support thunderbird:browser-sandbox :browser-support - camera thunderbird:camera- - content[gnome-42-2204] thunderbird:gnome-42-2204 gnome-42-2204:gnome-42-2204 - content[gtk-3-themes] thunderbird:gtk-3-themes gtk-common-themes:gtk-3-themes - content[icon-themes]thunderbird:icon-themes gtk-common-themes:icon-themes - content[sound-themes] thunderbird:sound-themes gtk-common-themes:sound-themes - cups-controlthunderbird:cups-control - - dbus- thunderbird:dbus-daemon - desktop thunderbird:desktop :desktop - desktop-legacy thunderbird:desktop-legacy:desktop-legacy - gpg-keysthunderbird:gpg-keys - - gsettings thunderbird:gsettings :gsettings - homethunderbird:home :home - network thunderbird:network :network - network-control thunderbird:network-control - - opengl thunderbird:opengl:opengl - removable-media thunderbird:removable-media - - system-filesthunderbird:etc-thunderbird-policies :system-files - u2f-devices thunderbird:u2f-devices - - wayland thunderbird:wayland :wayland - x11 thunderbird:x11 :x11 - ** Affects: thunderbird (Ubuntu) Importance: Undecided Status: New -- 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/2056494 Title: Snap profile import fails with EPERM Status in thunderbird package in Ubuntu: New Bug description: A regular noble full-upgrade transitioned my laptop to the thunderbird snap this morning, and I ended up with no profile due to an EPERM reading ~/.thunderbird during the migration. thunderbird.launcher says it needs personal-files, but the thunderbird snap doesn't seem to have that plug. wgrant@vanth:~$ thunderbird du: cannot read directory '/home/wgrant/.thunderbird': Permission denied Importing existing thunderbird profiles from /home/wgrant/.thunderbird cp: cannot stat '/home/wgrant/.thunderbird/*': No such file or directory Usage: /snap/thunderbird/450/patch-default-profile.py /path/to/profiles_dir/profiles.ini Import done in 0.029 s wgrant@vanth:~$ ls -ld /home/wgrant/.thunderbird drwx-- 6 wgrant wgrant 4096 Aug 13 2020 /home/wgrant/.thunderbird wgrant@vanth:~$ dpkg -l thunderbird | tail -n1 ii thunderbird1:115.8.1+build1+snap2 amd64Transitional package - thunderbird -> thunderbird snap wgrant@vanth:~$ snap info thunderbird | tail -n1 installed: 115.8.1-2(450) 145MB - wgrant@vanth:~$ snap connections thunderbird Interface Plug
[Desktop-packages] [Bug 2056488] Re: audio output defaults to dummy output
** Package changed: ubuntu => alsa-driver (Ubuntu) -- 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/2056488 Title: audio output defaults to dummy output Status in alsa-driver package in Ubuntu: New Bug description: audio defaults to dummu output instead of HDMI audio Using Ubuntu 23.04 Audio need to stay at HDMI output from shutdown or restart Alsamixer did not repair problem and am unable to download Pulse Audio ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.5.0-15.15-generic 6.5.3 Uname: Linux 6.5.0-15-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: photom 923 F wireplumber /dev/snd/controlC1: photom 923 F wireplumber /dev/snd/seq:photom 917 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Mar 7 14:27:41 2024 InstallationDate: Installed on 2023-07-08 (243 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: alsa-driver Symptom: audio UpgradeStatus: Upgraded to mantic on 2023-11-17 (111 days ago) dmi.bios.date: 11/18/2016 dmi.bios.release: 8.15 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0502 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M5A78L-M PLUS/USB3 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0502:bd11/18/2016:br8.15:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78L-MPLUS/USB3:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2056488/+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 2056488] [NEW] audio output defaults to dummy output
You have been subscribed to a public bug: audio defaults to dummu output instead of HDMI audio Using Ubuntu 23.04 Audio need to stay at HDMI output from shutdown or restart Alsamixer did not repair problem and am unable to download Pulse Audio ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.5.0-15.15-generic 6.5.3 Uname: Linux 6.5.0-15-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: photom 923 F wireplumber /dev/snd/controlC1: photom 923 F wireplumber /dev/snd/seq:photom 917 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Mar 7 14:27:41 2024 InstallationDate: Installed on 2023-07-08 (243 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: alsa-driver Symptom: audio UpgradeStatus: Upgraded to mantic on 2023-11-17 (111 days ago) dmi.bios.date: 11/18/2016 dmi.bios.release: 8.15 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0502 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M5A78L-M PLUS/USB3 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0502:bd11/18/2016:br8.15:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78L-MPLUS/USB3:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic wayland-session -- audio output defaults to dummy output https://bugs.launchpad.net/bugs/2056488 You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver 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 2056458] Re: upgrade to thunderbird snap, missing snapd depdency
** Information type changed from Private Security to Public -- 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/2056458 Title: upgrade to thunderbird snap, missing snapd depdency Status in thunderbird package in Ubuntu: New Bug description: latest upgrade on noble replaces thunderbird with snap version. This package does not provide snapd dependency. Simple dist-upgrade on installations (lxqt minimal or server installations) not having snapd installed at all breaking thunderbird because of missing snapd. There is another problem with the missing snapd depdency: the package could not be blocked via pin priority on snapd (when i want use package with the same name from anothe ppa). In general the snapd thunderbird is big crap (cursor theme not working, much slower, x11 ssh forwarding issues etc). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/2056458/+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 2055519] Re: Mutter rebuilds on jammy fail test: mutter:cogl+cogl/conform / framebuffer-get-bits (due to Mesa >= 23.1.1)
Thank you. I have uploaded this to the jammy queue so I am unsubscribing ubuntu-sponsors. Feel free to resubscribe if you have something else that needs to be sponsored. -- 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/2055519 Title: Mutter rebuilds on jammy fail test: mutter:cogl+cogl/conform / framebuffer-get-bits (due to Mesa >= 23.1.1) Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Jammy: In Progress Bug description: [ Impact ] Mutter's test cases fail on jammy since Mesa got updated: mutter:cogl+cogl/conform / framebuffer-get-bits [ Test Plan ] Build mutter and run its tests (done automatically during packaging) [ Where problems could occur ] More tests fail. [ Other Info ] 27/113 mutter:cogl+cogl/conform / framebuffer-get-bits RUNNING >>> RUN_TESTS_QUIET=1 PATH=/usr/lib/s390x-linux-gnu:/<>/obj-s390x-linux-gnu/cogl/cogl:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games MALLOC_PERTURB_=176 /<>/src/tests/meta-dbus-runner.py /<>/cogl/tests/run-tests.sh /<>/obj-s390x-linux-gnu/cogl/tests/config.env cogl/tests/conform/test-conformance test_framebuffer_get_bits ― ✀ ― Starting D-Bus daemons (session & system)... Starting mocked services... Running test case... Test GL+GLSL GL3 ES2 test_framebuffer_get_bits: ok FAIL n/a Traceback (most recent call last): File "/<>/src/tests/meta-dbus-runner.py", line 184, in test_case.wrap_call(rest[1:]) File "/<>/src/tests/meta-dbus-runner.py", line 171, in wrap_call self.assertEqual(p.wait(), 0) File "/usr/lib/python3.10/unittest/case.py", line 845, in assertEqual assertion_func(first, second, msg=msg) File "/usr/lib/python3.10/unittest/case.py", line 838, in _baseAssertEqual raise self.failureException(msg) AssertionError: 134 != 0 ―― 27/113 mutter:cogl+cogl/conform / framebuffer-get-bits FAIL 2.35s exit status 1 and 27/113 mutter:cogl+cogl/conform / framebuffer-get-bits RUNNING >>> MALLOC_PERTURB_=159 PATH=/<>/obj-aarch64-linux-gnu/cogl/cogl:/usr/lib/aarch64-linux-gnu:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games RUN_TESTS_QUIET=1 /<>/src/tests/meta-dbus-runner.py /<>/cogl/tests/run-tests.sh /<>/obj-aarch64-linux-gnu/cogl/tests/config.env cogl/tests/conform/test-conformance test_framebuffer_get_bits ― ✀ ― Starting D-Bus daemons (session & system)... Starting mocked services... Running test case... Test GL+GLSL GL3 ES2 test_framebuffer_get_bits: ok FAIL n/a Traceback (most recent call last): File "/<>/src/tests/meta-dbus-runner.py", line 184, in test_case.wrap_call(rest[1:]) File "/<>/src/tests/meta-dbus-runner.py", line 171, in wrap_call self.assertEqual(p.wait(), 0) File "/usr/lib/python3.10/unittest/case.py", line 845, in assertEqual assertion_func(first, second, msg=msg) File "/usr/lib/python3.10/unittest/case.py", line 838, in _baseAssertEqual raise self.failureException(msg) AssertionError: 134 != 0 ―― 27/113 mutter:cogl+cogl/conform / framebuffer-get-bits FAIL 0.83s exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2055519/+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 2043517] Re: gnome-shell on non-active VT busy-loops through libwayland-server.so (sometimes)
** Changed in: xorg-server
Status: Unknown => New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xwayland in Ubuntu.
https://bugs.launchpad.net/bugs/2043517
Title:
gnome-shell on non-active VT busy-loops through libwayland-server.so
(sometimes)
Status in X.Org X server:
New
Status in mutter package in Ubuntu:
New
Status in xwayland package in Ubuntu:
New
Bug description:
I run several gnome sessions at once - different users on different
Virtual Terminals.
Sometimes, gnome-shell for a non-active VT starts using 100% CPU. Or,
actually 99% CPU because it's doing IPC as well. And the
corresponding XWayland uses 40% CPU.
FWIW, sending SIGSTOP to either gnome-shell or XWayland stops the
other one from busy-looping as well.
If I switch back to the affected VT, it appears to function fine, but
it is still using 100% + 40% CPU.
Version numbers:
Ubuntu 22.04.3 LTS
gnome-shell 42.9-0ubuntu2
xwayland 2:22.1.1-1ubuntu0.7
$ ps -aux | grep 'alan .*gnome-shell$'
alan9248 26.1 3.4 5492888 269136 ? Rsl 19:54 30:26
/usr/bin/gnome-shell
$ sudo strace -p 9248 2>&1|head
strace: Process 9248 attached
epoll_wait(37, [{events=EPOLLIN, data={u32=403234816, u64=139797293752320}}],
32, 0) = 1
recvmsg(21, {msg_name=NULL, msg_namelen=0,
msg_iov=[{iov_base="\1\0\0\0\0\0\f\0\3\0\0\0", iov_len=752}, {iov_base="",
iov_len=3344}], msg_iovlen=2, msg_controllen=0, msg_flags=MSG_CMSG_CLOEXEC},
MSG_DONTWAIT|MSG_CMSG_CLOEXEC) = 12
write(4, "\1\0\0\0\0\0\0\0", 8) = 8
sendmsg(21, {msg_name=NULL, msg_namelen=0,
msg_iov=[{iov_base="\3\0\0\0\0\0\f\0[\2\0\0\1\0\0\0\1\0\f\0\3\0\0\0",
iov_len=24}], msg_iovlen=1, msg_controllen=0, msg_flags=0},
MSG_DONTWAIT|MSG_NOSIGNAL) = 24
poll([{fd=4, events=POLLIN}, {fd=8, events=POLLIN}, {fd=9, events=POLLIN},
{fd=19, events=POLLIN}, {fd=20, events=POLLIN}, {fd=23, events=POLLIN}, {fd=24,
events=POLLIN}, {fd=25, events=POLLIN}, {fd=34, events=POLLIN}, {fd=36,
events=POLLIN}, {fd=37, events=POLLIN}, {fd=54, events=POLLIN}, {fd=63,
events=POLLIN}, {fd=66, events=POLLIN}], 14, 79809702) = 2 ([{fd=4,
revents=POLLIN}, {fd=37, revents=POLLIN}])
read(4, "\2\0\0\0\0\0\0\0", 16) = 8
write(4, "\1\0\0\0\0\0\0\0", 8) = 8
epoll_wait(37, [{events=EPOLLIN, data={u32=403234816, u64=139797293752320}}],
32, 0) = 1
The recvmsg() call is here:
#0 __libc_recvmsg (fd=21, msg=0x7fff1de64a50, flags=1073741888) at
../sysdeps/unix/sysv/linux/recvmsg.c:35
#1 0x7f2531ea5ad6 in () at /lib/x86_64-linux-gnu/libwayland-server.so.0
#2 0x7f2531ea4eea in wl_event_loop_dispatch () at
/lib/x86_64-linux-gnu/libwayland-server.so.0
#3 0x7f2531d2b45b in wayland_event_source_dispatch (base=, callback=, data=)
at ../src/wayland/meta-wayland.c:110
#4 0x7f2532b42d3b in g_main_dispatch (context=0x55c0046cc8f0) at
../../../glib/gmain.c:3419
#5 g_main_context_dispatch (context=0x55c0046cc8f0) at
../../../glib/gmain.c:4137
#6 0x7f2532b98258 in g_main_context_iterate.constprop.0
(context=0x55c0046cc8f0, block=block@entry=1, dispatch=dispatch@entry=1,
self=) at ../../../glib/gmain.c:4213
#7 0x7f2532b422b3 in g_main_loop_run (loop=0x55c00698ae30) at
../../../glib/gmain.c:4413
#8 0x7f2531cd0b79 in meta_context_run_main_loop
(context=context@entry=0x55c0046c70c0, error=error@entry=0x7fff1de64f08)
at ../src/core/meta-context.c:437
#9 0x55c003cf4f12 in main (argc=, argv=)
at ../src/main.c:650
The sendmsg() call is here:
Thread 1 "gnome-shell" hit Breakpoint 1, __libc_sendmsg (fd=21,
msg=0x7fff1de64c50, flags=16448) at ../sysdeps/unix/sysv/linux/sendmsg.c:26
26../sysdeps/unix/sysv/linux/sendmsg.c: No such file or directory.
(gdb) where
#0 __libc_sendmsg (fd=21, msg=0x7fff1de64c50, flags=16448) at
../sysdeps/unix/sysv/linux/sendmsg.c:26
#1 0x7f2531ea1c9d in () at /lib/x86_64-linux-gnu/libwayland-server.so.0
#2 0x7f2531ea565e in wl_display_flush_clients () at
/lib/x86_64-linux-gnu/libwayland-server.so.0
#3 0x7f2531d2b437 in wayland_event_source_prepare
(base=base@entry=0x55c004a374d0, timeout=timeout@entry=0x7fff1de64dc4)
at ../src/wayland/meta-wayland.c:97
#4 0x7f2532b428e7 in g_main_context_prepare (context=0x55c0046cc8f0,
priority=0x7fff1de64e50) at ../../../glib/gmain.c:3739
#5 0x7f2532b98123 in g_main_context_iterate.constprop.0
(context=0x55c0046cc8f0, block=block@entry=1, dispatch=dispatch@entry=1,
self=) at ../../../glib/gmain.c:4193
#6 0x7f2532b422b3 in g_main_loop_run (loop=0x55c00698ae30) at
../../../glib/gmain.c:4413
#7 0x7f2531cd0b79 in meta_context_run_main_loop
(context=context@entry=0x55c0046c70c0, error=error@entry=0x7fff1de64f08)
at ../src/core/meta-context.c:437
#8 0x55c003cf4f12 in main (argc=, argv=)
at ../src/main.c:650
To manage notifications about this
[Desktop-packages] [Bug 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP
** Also affects: loupe (Ubuntu) Importance: Undecided Status: New ** Changed in: loupe (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/2046844 Title: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP Status in AppArmor: New Status in akonadiconsole package in Ubuntu: Fix Released Status in akregator package in Ubuntu: Fix Released Status in angelfish package in Ubuntu: Fix Released Status in apparmor package in Ubuntu: Fix Released Status in bubblewrap package in Ubuntu: Confirmed Status in cantor package in Ubuntu: Fix Released Status in devhelp package in Ubuntu: Fix Released Status in digikam package in Ubuntu: Fix Released Status in epiphany-browser package in Ubuntu: Fix Released Status in evolution package in Ubuntu: Fix Released Status in falkon package in Ubuntu: Fix Released Status in firefox package in Ubuntu: Confirmed Status in freecad package in Ubuntu: Confirmed Status in geary package in Ubuntu: Confirmed Status in ghostwriter package in Ubuntu: Fix Released Status in gnome-packagekit package in Ubuntu: Confirmed Status in goldendict-webengine package in Ubuntu: Confirmed Status in kalgebra package in Ubuntu: Fix Released Status in kchmviewer package in Ubuntu: Confirmed Status in kdeplasma-addons package in Ubuntu: Fix Released Status in kgeotag package in Ubuntu: Fix Released Status in kiwix package in Ubuntu: Confirmed Status in kmail package in Ubuntu: Fix Released Status in konqueror package in Ubuntu: Fix Released Status in kontact package in Ubuntu: Fix Released Status in loupe package in Ubuntu: Confirmed Status in marble package in Ubuntu: Fix Released Status in notepadqq package in Ubuntu: Confirmed Status in opam package in Ubuntu: Fix Released Status in pageedit package in Ubuntu: Confirmed Status in plasma-desktop package in Ubuntu: Fix Released Status in plasma-welcome package in Ubuntu: Fix Released Status in privacybrowser package in Ubuntu: Confirmed Status in qmapshack package in Ubuntu: Confirmed Status in qutebrowser package in Ubuntu: Confirmed Status in rssguard package in Ubuntu: Confirmed Status in steam package in Ubuntu: Fix Committed Status in supercollider package in Ubuntu: Confirmed Status in tellico package in Ubuntu: Fix Released Bug description: Hi, I run Ubuntu development branch 24.04 and I have a problem with Epiphany browser 45.1-1 (Gnome Web): program doesn't launch, and I get this error $ epiphany bwrap: Creating new namespace failed: Permission denied ** (epiphany:12085): ERROR **: 14:44:35.023: Failed to fully launch dbus-proxy: Le processus fils s’est terminé avec le code 1 Trappe pour point d'arrêt et de trace (core dumped) $ epiphany bwrap: Creating new namespace failed: Permission denied ** (epiphany:30878): ERROR **: 22:22:26.926: Failed to fully launch dbus-proxy: Le processus fils s’est terminé avec le code 1 Trappe pour point d'arrêt et de trace (core dumped) Thanks for your help! To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/2046844/+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 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP
** Also affects: apparmor Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/2046844 Title: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP Status in AppArmor: New Status in akonadiconsole package in Ubuntu: Fix Released Status in akregator package in Ubuntu: Fix Released Status in angelfish package in Ubuntu: Fix Released Status in apparmor package in Ubuntu: Fix Released Status in bubblewrap package in Ubuntu: Confirmed Status in cantor package in Ubuntu: Fix Released Status in devhelp package in Ubuntu: Fix Released Status in digikam package in Ubuntu: Fix Released Status in epiphany-browser package in Ubuntu: Fix Released Status in evolution package in Ubuntu: Fix Released Status in falkon package in Ubuntu: Fix Released Status in firefox package in Ubuntu: Confirmed Status in freecad package in Ubuntu: Confirmed Status in geary package in Ubuntu: Confirmed Status in ghostwriter package in Ubuntu: Fix Released Status in gnome-packagekit package in Ubuntu: Confirmed Status in goldendict-webengine package in Ubuntu: Confirmed Status in kalgebra package in Ubuntu: Fix Released Status in kchmviewer package in Ubuntu: Confirmed Status in kdeplasma-addons package in Ubuntu: Fix Released Status in kgeotag package in Ubuntu: Fix Released Status in kiwix package in Ubuntu: Confirmed Status in kmail package in Ubuntu: Fix Released Status in konqueror package in Ubuntu: Fix Released Status in kontact package in Ubuntu: Fix Released Status in loupe package in Ubuntu: Confirmed Status in marble package in Ubuntu: Fix Released Status in notepadqq package in Ubuntu: Confirmed Status in opam package in Ubuntu: Fix Released Status in pageedit package in Ubuntu: Confirmed Status in plasma-desktop package in Ubuntu: Fix Released Status in plasma-welcome package in Ubuntu: Fix Released Status in privacybrowser package in Ubuntu: Confirmed Status in qmapshack package in Ubuntu: Confirmed Status in qutebrowser package in Ubuntu: Confirmed Status in rssguard package in Ubuntu: Confirmed Status in steam package in Ubuntu: Fix Committed Status in supercollider package in Ubuntu: Confirmed Status in tellico package in Ubuntu: Fix Released Bug description: Hi, I run Ubuntu development branch 24.04 and I have a problem with Epiphany browser 45.1-1 (Gnome Web): program doesn't launch, and I get this error $ epiphany bwrap: Creating new namespace failed: Permission denied ** (epiphany:12085): ERROR **: 14:44:35.023: Failed to fully launch dbus-proxy: Le processus fils s’est terminé avec le code 1 Trappe pour point d'arrêt et de trace (core dumped) $ epiphany bwrap: Creating new namespace failed: Permission denied ** (epiphany:30878): ERROR **: 22:22:26.926: Failed to fully launch dbus-proxy: Le processus fils s’est terminé avec le code 1 Trappe pour point d'arrêt et de trace (core dumped) Thanks for your help! To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/2046844/+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 1881180] Re: drop suru-icon-theme (and use UBports' suru-icon-theme as upstream)
I dropped suru-icon-theme from the ubuntu-themes source today and synced
Debian's version of suru-icon-theme.
** Changed in: ubuntu-themes (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-themes in Ubuntu.
https://bugs.launchpad.net/bugs/1881180
Title:
drop suru-icon-theme (and use UBports' suru-icon-theme as upstream)
Status in ubuntu-themes package in Ubuntu:
Fix Released
Bug description:
As part of the initiative of packaging Lomiri (former Unity8) for
Debian, I have just created a standalone source project for suru-icon-
theme [1]. This will soon be packaged for and uploaded to Debian
unstable.
The UBports developers have added several changes to "their" suru-
icon-theme which makes it impossible to use suru-icon-theme from the
ubuntu-theme src:pkg on Ubuntu Touch. On the other hand, UBports'
suru-icon-theme should still be good to go with on Ubuntu.
Furthermore, for Debian upload, I preferred not to package the ubuntu
specific artwork as a whole. The solution at UBports upstream was
providing suru-icon-theme as a standalone upstream project.
Thus, I'd like to suggest dropping suru-icon-theme from Ubuntu Theme
(at least the bin:pkg) and use the suru-icon-theme package being
available in Debian soon('ish (dependening on NEW queue processing)).
The UBports devs are open to merge requests if that is required from
time to time.
Thanks+Greets,
Mike (aka sunweaver at debian.org)
[1] https://gitlab.com/ubports/core/suru-icon-theme
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1881180/+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 2056481] Re: [snap] Thunderbird does not support native notifications on KDE Plasma Desktop
** Summary changed: - [snap] Does not support native notifications on KDE Plasma Desktop + [snap] Thunderbird does not support native notifications on KDE Plasma Desktop -- 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/2056481 Title: [snap] Thunderbird does not support native notifications on KDE Plasma Desktop Status in thunderbird package in Ubuntu: New Status in xdg-desktop-portal package in Ubuntu: New Bug description: After testing and upgrading, I have discovered that the thunderbird snap does not support native notifications on KDE Plasma Desktop on either Kubuntu or Ubuntu Studio (same packages and desktop, really). This might be an issue with xdg-desktop-portal, so I'm also going to mark it as affected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/2056481/+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 2056481] [NEW] [snap] Thunderbird does not support native notifications on KDE Plasma Desktop
Public bug reported: After testing and upgrading, I have discovered that the thunderbird snap does not support native notifications on KDE Plasma Desktop on either Kubuntu or Ubuntu Studio (same packages and desktop, really). This might be an issue with xdg-desktop-portal, so I'm also going to mark it as affected. ** Affects: thunderbird (Ubuntu) Importance: High Status: New ** Affects: xdg-desktop-portal (Ubuntu) Importance: High Status: New ** Also affects: xdg-desktop-portal (Ubuntu) Importance: Undecided Status: New ** Changed in: xdg-desktop-portal (Ubuntu) Importance: Undecided => High -- 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/2056481 Title: [snap] Thunderbird does not support native notifications on KDE Plasma Desktop Status in thunderbird package in Ubuntu: New Status in xdg-desktop-portal package in Ubuntu: New Bug description: After testing and upgrading, I have discovered that the thunderbird snap does not support native notifications on KDE Plasma Desktop on either Kubuntu or Ubuntu Studio (same packages and desktop, really). This might be an issue with xdg-desktop-portal, so I'm also going to mark it as affected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/2056481/+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 2052925] Re: lpoptions -d as root
This bug was fixed in the package cups - 2.4.1op1-1ubuntu4.8 --- cups (2.4.1op1-1ubuntu4.8) jammy; urgency=medium * The "lpoptions" utility, when run as root was writing into the file /root/.cups/lpoptions instread of /etc/cups/lpoptions. System software should never write into /root/ (LP: #2052925). -- Till Kamppeter Wed, 14 Feb 2023 14:10:00 +0100 ** Changed in: cups (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/2052925 Title: lpoptions -d as root Status in cups package in Ubuntu: Fix Released Status in cups source package in Jammy: Fix Released Bug description: Copied from https://github.com/OpenPrinting/cups/issues/454 Yair Yarom submitted Debian bug 1008053 and observed that running lpoptions as root does not update /etc/cups/lpoptions but /root/.cups/lpoptions. Running lpoptions as root (e.g. "lpoptions -d HP-OfficeJet") should update /etc/cups/lpoptions to be the defaults for all users. But instead it tries to update /root/.cups/lpoptions. This has been fixed upstream in cups, in debian sid, and mantic. Proposing to add this change in jammy and older (still supported) series as well. The fix is a one line change in https://github.com/OpenPrinting/cups/pull/456 Thanks. 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu ubuntu@jammy-vm:~$ lsb_release -rd Description: Ubuntu 22.04.3 LTS Release: 22.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center ubuntu@jammy-vm:~$ apt-cache policy cups cups: Installed: 2.4.1op1-1ubuntu4.7 Candidate: 2.4.1op1-1ubuntu4.7 Version table: *** 2.4.1op1-1ubuntu4.7 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 100 /var/lib/dpkg/status 2.4.1op1-1ubuntu4 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 3) What you expected to happen: root@jammy-vm:~# lpstat -p printer HP-Officejet-Pro-8710 is idle. enabled since Thu 01 Feb 2024 03:17:49 PM UTC root@jammy-vm:~# root@jammy-vm:~# lpoptions -d HP-Officejet-Pro-8710 copies=1 device-uri=lpd://10.20.135.153:515/PASSTHRU finishings=3 job-cancel-after=10800 job-hold-until=no-hold job-priority=50 job-sheets=none,none marker-change-time=0 number-up=1 print-color-mode=color printer-commands=none printer-info=HP-Officejet-Pro-8710 printer-is-accepting-jobs=true printer-is-shared=true printer-is-temporary=false printer-location printer-make-and-model='HP Officejet Pro 8710, hpcups 3.21.12' printer-state=3 printer-state-change-time=1706800669 printer-state-reasons=none printer-type=4124 printer-uri-supported=ipp://localhost/printers/HP-Officejet-Pro-8710 root@jammy-vm:~# root@jammy-vm:~# cat /etc/cups/lpoptions Default HP-Officejet-Pro-8710 root@jammy-vm:~# root@jammy-vm:~# cat /root/.cups/lpoptions cat: /etc/cups/lpoptions: No such file or directory root@jammy-vm:~# 4) What happened instead: root@jammy-vm:~# lpstat -p printer HP-Officejet-Pro-8710 is idle. enabled since Thu 01 Feb 2024 03:17:49 PM UTC root@jammy-vm:~# root@jammy-vm:~# lpoptions -d HP-Officejet-Pro-8710 copies=1 device-uri=lpd://10.20.135.153:515/PASSTHRU finishings=3 job-cancel-after=10800 job-hold-until=no-hold job-priority=50 job-sheets=none,none marker-change-time=0 number-up=1 print-color-mode=color printer-commands=none printer-info=HP-Officejet-Pro-8710 printer-is-accepting-jobs=true printer-is-shared=true printer-is-temporary=false printer-location printer-make-and-model='HP Officejet Pro 8710, hpcups 3.21.12' printer-state=3 printer-state-change-time=1706800669 printer-state-reasons=none printer-type=4124 printer-uri-supported=ipp://localhost/printers/HP-Officejet-Pro-8710 root@jammy-vm:~# root@jammy-vm:~# cat /etc/cups/lpoptions cat: /etc/cups/lpoptions: No such file or directory root@jammy-vm:~# root@jammy-vm:~# cat /root/.cups/lpoptions Default HP-Officejet-Pro-8710 root@jammy-vm:~# To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/2052925/+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 2052925] Update Released
The verification of the Stable Release Update for cups has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/2052925 Title: lpoptions -d as root Status in cups package in Ubuntu: Fix Released Status in cups source package in Jammy: Fix Released Bug description: Copied from https://github.com/OpenPrinting/cups/issues/454 Yair Yarom submitted Debian bug 1008053 and observed that running lpoptions as root does not update /etc/cups/lpoptions but /root/.cups/lpoptions. Running lpoptions as root (e.g. "lpoptions -d HP-OfficeJet") should update /etc/cups/lpoptions to be the defaults for all users. But instead it tries to update /root/.cups/lpoptions. This has been fixed upstream in cups, in debian sid, and mantic. Proposing to add this change in jammy and older (still supported) series as well. The fix is a one line change in https://github.com/OpenPrinting/cups/pull/456 Thanks. 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu ubuntu@jammy-vm:~$ lsb_release -rd Description: Ubuntu 22.04.3 LTS Release: 22.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center ubuntu@jammy-vm:~$ apt-cache policy cups cups: Installed: 2.4.1op1-1ubuntu4.7 Candidate: 2.4.1op1-1ubuntu4.7 Version table: *** 2.4.1op1-1ubuntu4.7 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 100 /var/lib/dpkg/status 2.4.1op1-1ubuntu4 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 3) What you expected to happen: root@jammy-vm:~# lpstat -p printer HP-Officejet-Pro-8710 is idle. enabled since Thu 01 Feb 2024 03:17:49 PM UTC root@jammy-vm:~# root@jammy-vm:~# lpoptions -d HP-Officejet-Pro-8710 copies=1 device-uri=lpd://10.20.135.153:515/PASSTHRU finishings=3 job-cancel-after=10800 job-hold-until=no-hold job-priority=50 job-sheets=none,none marker-change-time=0 number-up=1 print-color-mode=color printer-commands=none printer-info=HP-Officejet-Pro-8710 printer-is-accepting-jobs=true printer-is-shared=true printer-is-temporary=false printer-location printer-make-and-model='HP Officejet Pro 8710, hpcups 3.21.12' printer-state=3 printer-state-change-time=1706800669 printer-state-reasons=none printer-type=4124 printer-uri-supported=ipp://localhost/printers/HP-Officejet-Pro-8710 root@jammy-vm:~# root@jammy-vm:~# cat /etc/cups/lpoptions Default HP-Officejet-Pro-8710 root@jammy-vm:~# root@jammy-vm:~# cat /root/.cups/lpoptions cat: /etc/cups/lpoptions: No such file or directory root@jammy-vm:~# 4) What happened instead: root@jammy-vm:~# lpstat -p printer HP-Officejet-Pro-8710 is idle. enabled since Thu 01 Feb 2024 03:17:49 PM UTC root@jammy-vm:~# root@jammy-vm:~# lpoptions -d HP-Officejet-Pro-8710 copies=1 device-uri=lpd://10.20.135.153:515/PASSTHRU finishings=3 job-cancel-after=10800 job-hold-until=no-hold job-priority=50 job-sheets=none,none marker-change-time=0 number-up=1 print-color-mode=color printer-commands=none printer-info=HP-Officejet-Pro-8710 printer-is-accepting-jobs=true printer-is-shared=true printer-is-temporary=false printer-location printer-make-and-model='HP Officejet Pro 8710, hpcups 3.21.12' printer-state=3 printer-state-change-time=1706800669 printer-state-reasons=none printer-type=4124 printer-uri-supported=ipp://localhost/printers/HP-Officejet-Pro-8710 root@jammy-vm:~# root@jammy-vm:~# cat /etc/cups/lpoptions cat: /etc/cups/lpoptions: No such file or directory root@jammy-vm:~# root@jammy-vm:~# cat /root/.cups/lpoptions Default HP-Officejet-Pro-8710 root@jammy-vm:~# To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/2052925/+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 2052925] Re: lpoptions -d as root
I noticed this SRU was prepared without the SRU Template[1] filled in. While most of the data we want is in the bug description as is (what's wrong, test plan), it's lacking an analysis of what could go wrong. That boat has sailed now, and doing an analysis of the patch right now, basically what could go wrong is if someone was relying on the old behavior, of the command only changing the local user's (root in this case) config, instead of system-wide. The lpoptions[1] manpage doesn't really special case root when the -d option is used: -d destination[/instance] Sets the user default printer to destination. If instance is supplied then that particular instance is used. This option overrides the system default printer for the current user. But later down, in "FILES", we see: ~/.cups/lpoptions - user defaults and instances created by non-root users. /etc/cups/lpoptions - system-wide defaults and instances created by the root user. So it does seem the intention of that option when used by the root user was to update the system-wide /etc/cups/lpoptions file instead. So even if someone was relying on the previous behavior, it was incorrect, and the documentation (which could be clearer, but isn't) seems to agree that the previous behavior was incorrect. That's the kind of analysis we would like to see in "what could go wrong", and "other info" sections of the SRU template. 1. https://manpages.ubuntu.com/manpages/jammy/en/man1/lpoptions.1.html -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/2052925 Title: lpoptions -d as root Status in cups package in Ubuntu: Fix Released Status in cups source package in Jammy: Fix Released Bug description: Copied from https://github.com/OpenPrinting/cups/issues/454 Yair Yarom submitted Debian bug 1008053 and observed that running lpoptions as root does not update /etc/cups/lpoptions but /root/.cups/lpoptions. Running lpoptions as root (e.g. "lpoptions -d HP-OfficeJet") should update /etc/cups/lpoptions to be the defaults for all users. But instead it tries to update /root/.cups/lpoptions. This has been fixed upstream in cups, in debian sid, and mantic. Proposing to add this change in jammy and older (still supported) series as well. The fix is a one line change in https://github.com/OpenPrinting/cups/pull/456 Thanks. 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu ubuntu@jammy-vm:~$ lsb_release -rd Description: Ubuntu 22.04.3 LTS Release: 22.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center ubuntu@jammy-vm:~$ apt-cache policy cups cups: Installed: 2.4.1op1-1ubuntu4.7 Candidate: 2.4.1op1-1ubuntu4.7 Version table: *** 2.4.1op1-1ubuntu4.7 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 100 /var/lib/dpkg/status 2.4.1op1-1ubuntu4 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 3) What you expected to happen: root@jammy-vm:~# lpstat -p printer HP-Officejet-Pro-8710 is idle. enabled since Thu 01 Feb 2024 03:17:49 PM UTC root@jammy-vm:~# root@jammy-vm:~# lpoptions -d HP-Officejet-Pro-8710 copies=1 device-uri=lpd://10.20.135.153:515/PASSTHRU finishings=3 job-cancel-after=10800 job-hold-until=no-hold job-priority=50 job-sheets=none,none marker-change-time=0 number-up=1 print-color-mode=color printer-commands=none printer-info=HP-Officejet-Pro-8710 printer-is-accepting-jobs=true printer-is-shared=true printer-is-temporary=false printer-location printer-make-and-model='HP Officejet Pro 8710, hpcups 3.21.12' printer-state=3 printer-state-change-time=1706800669 printer-state-reasons=none printer-type=4124 printer-uri-supported=ipp://localhost/printers/HP-Officejet-Pro-8710 root@jammy-vm:~# root@jammy-vm:~# cat /etc/cups/lpoptions Default HP-Officejet-Pro-8710 root@jammy-vm:~# root@jammy-vm:~# cat /root/.cups/lpoptions cat: /etc/cups/lpoptions: No such file or directory root@jammy-vm:~# 4) What happened instead: root@jammy-vm:~# lpstat -p printer HP-Officejet-Pro-8710 is idle. enabled since Thu 01 Feb 2024 03:17:49 PM UTC root@jammy-vm:~# root@jammy-vm:~# lpoptions -d HP-Officejet-Pro-8710 copies=1 device-uri=lpd://10.20.135.153:515/PASSTHRU finishings=3 job-cancel-after=10800 job-hold-until=no-hold job-priority=50 job-sheets=none,none marker-change-time=0 number-up=1 print-color-mode=color printer-commands=none printer-info=HP-Officejet-Pro-8710 printer-is-accepting-jobs=true printer-is-shared=true printer-is-temporary=false printer-location printer-make-and-model='HP Officejet Pro 8710, hpcups
[Desktop-packages] [Bug 2054111] Update Released
The verification of the Stable Release Update for libreoffice has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/2054111 Title: [SRU] libreoffice 7.6.5 for mantic Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Mantic: Fix Released Bug description: [Impact] * LibreOffice 7.6.5 is in its fifth bugfix release of the 7.6 line: https://wiki.documentfoundation.org/ReleasePlan/7.6#7.6.5_release * Version 7.6.4 is currently released in mantic. For a list of fixed bugs compared to 7.6.4 see the list of bugs fixed in the release candidates of 7.6.5 (that's a total of 94 bugs): https://wiki.documentfoundation.org/Releases/7.6.5/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/7.6.5/RC2#List_of_fixed_bugs 7.6.5 RC2 is identical to the 7.6.5 release * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_76/1816/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. Tested build can be found at https://launchpad.net/~ricotz/+archive/ubuntu/ppa/+sourcepub/15791929/+listing-archive-extra * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-ricotz-ppa/mantic/amd64/libr/libreoffice/20240216_132420_3c270@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-ricotz-ppa/mantic/arm64/libr/libreoffice/20240216_140709_197f6@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-ricotz-ppa/mantic/armhf/libr/libreoffice/20240216_222053_83134@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-ricotz-ppa/mantic/ppc64el/libr/libreoffice/20240216_130131_fd665@/log.gz * [riscv64] not available * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-ricotz-ppa/mantic/s390x/libr/libreoffice/20240216_141429_f0d16@/log.gz * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A minor release with a total of 94 bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2054111/+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 2054111] Re: [SRU] libreoffice 7.6.5 for mantic
This bug was fixed in the package libreoffice - 4:7.6.5-0ubuntu0.23.10.1 --- libreoffice (4:7.6.5-0ubuntu0.23.10.1) mantic; urgency=medium * New upstream release (LP: #2054111) [ Rene Engelhard ] * debian/rules: - Don't remove libforuilo.so in -core-nogui. It's subsumed in libmerged on 64bit archs only (similar as libuuilo.so). - Build with --disable-split-debug on riscv64 to resolve GDB debugging issues * debian/patches/fix-riscv64-bridge.diff: More riscv64 bridge fixes from https://gerrit.libreoffice.org/c/core/+/160970 -- Rico Tzschichholz Wed, 21 Feb 2024 18:58:24 +0100 ** Changed in: libreoffice (Ubuntu Mantic) Status: Fix Committed => Fix Released -- 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/2054111 Title: [SRU] libreoffice 7.6.5 for mantic Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Mantic: Fix Released Bug description: [Impact] * LibreOffice 7.6.5 is in its fifth bugfix release of the 7.6 line: https://wiki.documentfoundation.org/ReleasePlan/7.6#7.6.5_release * Version 7.6.4 is currently released in mantic. For a list of fixed bugs compared to 7.6.4 see the list of bugs fixed in the release candidates of 7.6.5 (that's a total of 94 bugs): https://wiki.documentfoundation.org/Releases/7.6.5/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/7.6.5/RC2#List_of_fixed_bugs 7.6.5 RC2 is identical to the 7.6.5 release * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_76/1816/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. Tested build can be found at https://launchpad.net/~ricotz/+archive/ubuntu/ppa/+sourcepub/15791929/+listing-archive-extra * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-ricotz-ppa/mantic/amd64/libr/libreoffice/20240216_132420_3c270@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-ricotz-ppa/mantic/arm64/libr/libreoffice/20240216_140709_197f6@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-ricotz-ppa/mantic/armhf/libr/libreoffice/20240216_222053_83134@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-ricotz-ppa/mantic/ppc64el/libr/libreoffice/20240216_130131_fd665@/log.gz * [riscv64] not available * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-ricotz-ppa/mantic/s390x/libr/libreoffice/20240216_141429_f0d16@/log.gz * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A minor release with a total of 94 bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2054111/+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 1962327]
It is not corrcted yet To see the proper expected rendering open the following webpage in firefox and compare the result with Libreoffice https://fonts.atipra.in/afrc-test.html -- 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/1962327 Title: [Upstream] Vertical fraction feature present in font not applied by Writer Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: Triaged Bug description: ~ $ lsb_release -rd Description: Ubuntu 20.04.3 LTS Release: 20.04 ~$ apt-cache policy libreoffice-writer libreoffice-writer: Installed: 1:6.4.7-0ubuntu0.20.04.2 Candidate: 1:6.4.7-0ubuntu0.20.04.2 Version table: *** 1:6.4.7-0ubuntu0.20.04.2 500 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 1:6.4.2-0ubuntu3 500 500 http://in.archive.ubuntu.com/ubuntu focal/main amd64 Packages ~$ apt-show-versions -r libreoffice* liblibreofficekitgtk:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-base-core:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-calc:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-common:all/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-core:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-draw:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-gnome:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-gtk:all/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-gtk2:all/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-gtk3:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-impress:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-java-common:all/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-l10n-bn:all/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-math:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-style-colibre:all/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-style-elementary:all/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-style-tango:all/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-writer:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreofficekit-data:all/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate What is expected to happen in Writer is My font has vertical fraction look up for Bengali script. On selecting Format > Characters > CTL Font > Features Alternate (vertical) Fraction Feature is visible in options. Selecting the option should apply the feature on selected fraction see screenshot http://cloud.atipra.in/index.php/s/YosGiyFSoTQeW8i What happened instead is.. The feature is not applied, and the selected text is unchanged It should change as happens in firefox on selecting alternate (Vertical) fraction lookup in css see screenshot http://cloud.atipra.in/index.php/s/MxYbEisyFT3KnKT Extension installed : None ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libreoffice-writer 1:6.4.7-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.4.0-100.113-generic 5.4.166 Uname: Linux 5.4.0-100-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Feb 25 20:33:24 2022 InstallationDate: Installed on 2020-01-03 (783 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: libreoffice UpgradeStatus: Upgraded to focal on 2021-09-16 (162 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1962327/+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 1962327] Re: [Upstream] Vertical fraction feature present in font not applied by Writer
The rendering is still flawed To see how it should be renderered, please see https://fonts.atipra.in/afrc-test.html in a browser like firefox or chrome -- 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/1962327 Title: [Upstream] Vertical fraction feature present in font not applied by Writer Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: Triaged Bug description: ~ $ lsb_release -rd Description: Ubuntu 20.04.3 LTS Release: 20.04 ~$ apt-cache policy libreoffice-writer libreoffice-writer: Installed: 1:6.4.7-0ubuntu0.20.04.2 Candidate: 1:6.4.7-0ubuntu0.20.04.2 Version table: *** 1:6.4.7-0ubuntu0.20.04.2 500 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 1:6.4.2-0ubuntu3 500 500 http://in.archive.ubuntu.com/ubuntu focal/main amd64 Packages ~$ apt-show-versions -r libreoffice* liblibreofficekitgtk:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-base-core:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-calc:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-common:all/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-core:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-draw:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-gnome:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-gtk:all/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-gtk2:all/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-gtk3:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-impress:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-java-common:all/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-l10n-bn:all/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-math:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-style-colibre:all/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-style-elementary:all/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-style-tango:all/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-writer:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreofficekit-data:all/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate What is expected to happen in Writer is My font has vertical fraction look up for Bengali script. On selecting Format > Characters > CTL Font > Features Alternate (vertical) Fraction Feature is visible in options. Selecting the option should apply the feature on selected fraction see screenshot http://cloud.atipra.in/index.php/s/YosGiyFSoTQeW8i What happened instead is.. The feature is not applied, and the selected text is unchanged It should change as happens in firefox on selecting alternate (Vertical) fraction lookup in css see screenshot http://cloud.atipra.in/index.php/s/MxYbEisyFT3KnKT Extension installed : None ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libreoffice-writer 1:6.4.7-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.4.0-100.113-generic 5.4.166 Uname: Linux 5.4.0-100-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Feb 25 20:33:24 2022 InstallationDate: Installed on 2020-01-03 (783 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: libreoffice UpgradeStatus: Upgraded to focal on 2021-09-16 (162 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1962327/+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 1962327]
Created attachment 193019 Screen shot from firefox showing proper rendering This is how the vertical fraction should look. Newer versions of Chrome also messes it so see the link https://fonts.atipra.in/afrc-test.html in Firefox only o see the proper rendering -- 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/1962327 Title: [Upstream] Vertical fraction feature present in font not applied by Writer Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: Triaged Bug description: ~ $ lsb_release -rd Description: Ubuntu 20.04.3 LTS Release: 20.04 ~$ apt-cache policy libreoffice-writer libreoffice-writer: Installed: 1:6.4.7-0ubuntu0.20.04.2 Candidate: 1:6.4.7-0ubuntu0.20.04.2 Version table: *** 1:6.4.7-0ubuntu0.20.04.2 500 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 1:6.4.2-0ubuntu3 500 500 http://in.archive.ubuntu.com/ubuntu focal/main amd64 Packages ~$ apt-show-versions -r libreoffice* liblibreofficekitgtk:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-base-core:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-calc:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-common:all/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-core:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-draw:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-gnome:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-gtk:all/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-gtk2:all/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-gtk3:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-impress:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-java-common:all/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-l10n-bn:all/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-math:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-style-colibre:all/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-style-elementary:all/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-style-tango:all/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreoffice-writer:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate libreofficekit-data:all/focal-security 1:6.4.7-0ubuntu0.20.04.2 uptodate What is expected to happen in Writer is My font has vertical fraction look up for Bengali script. On selecting Format > Characters > CTL Font > Features Alternate (vertical) Fraction Feature is visible in options. Selecting the option should apply the feature on selected fraction see screenshot http://cloud.atipra.in/index.php/s/YosGiyFSoTQeW8i What happened instead is.. The feature is not applied, and the selected text is unchanged It should change as happens in firefox on selecting alternate (Vertical) fraction lookup in css see screenshot http://cloud.atipra.in/index.php/s/MxYbEisyFT3KnKT Extension installed : None ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libreoffice-writer 1:6.4.7-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.4.0-100.113-generic 5.4.166 Uname: Linux 5.4.0-100-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Feb 25 20:33:24 2022 InstallationDate: Installed on 2020-01-03 (783 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: libreoffice UpgradeStatus: Upgraded to focal on 2021-09-16 (162 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1962327/+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 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP
Yes, since today's updates, Firefox Nightly 125.0a1 from Mozilla repositery which worked very fined until now, stopped : program still well starts, but every tab gets a crash error and doesn't laod the page (even the start about:blank one)… -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/2046844 Title: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP Status in akonadiconsole package in Ubuntu: Fix Released Status in akregator package in Ubuntu: Fix Released Status in angelfish package in Ubuntu: Fix Released Status in apparmor package in Ubuntu: Fix Released Status in bubblewrap package in Ubuntu: Confirmed Status in cantor package in Ubuntu: Fix Released Status in devhelp package in Ubuntu: Fix Released Status in digikam package in Ubuntu: Fix Released Status in epiphany-browser package in Ubuntu: Fix Released Status in evolution package in Ubuntu: Fix Released Status in falkon package in Ubuntu: Fix Released Status in firefox package in Ubuntu: Confirmed Status in freecad package in Ubuntu: Confirmed Status in geary package in Ubuntu: Confirmed Status in ghostwriter package in Ubuntu: Fix Released Status in gnome-packagekit package in Ubuntu: Confirmed Status in goldendict-webengine package in Ubuntu: Confirmed Status in kalgebra package in Ubuntu: Fix Released Status in kchmviewer package in Ubuntu: Confirmed Status in kdeplasma-addons package in Ubuntu: Fix Released Status in kgeotag package in Ubuntu: Fix Released Status in kiwix package in Ubuntu: Confirmed Status in kmail package in Ubuntu: Fix Released Status in konqueror package in Ubuntu: Fix Released Status in kontact package in Ubuntu: Fix Released Status in marble package in Ubuntu: Fix Released Status in notepadqq package in Ubuntu: Confirmed Status in opam package in Ubuntu: Fix Released Status in pageedit package in Ubuntu: Confirmed Status in plasma-desktop package in Ubuntu: Fix Released Status in plasma-welcome package in Ubuntu: Fix Released Status in privacybrowser package in Ubuntu: Confirmed Status in qmapshack package in Ubuntu: Confirmed Status in qutebrowser package in Ubuntu: Confirmed Status in rssguard package in Ubuntu: Confirmed Status in steam package in Ubuntu: Fix Committed Status in supercollider package in Ubuntu: Confirmed Status in tellico package in Ubuntu: Fix Released Bug description: Hi, I run Ubuntu development branch 24.04 and I have a problem with Epiphany browser 45.1-1 (Gnome Web): program doesn't launch, and I get this error $ epiphany bwrap: Creating new namespace failed: Permission denied ** (epiphany:12085): ERROR **: 14:44:35.023: Failed to fully launch dbus-proxy: Le processus fils s’est terminé avec le code 1 Trappe pour point d'arrêt et de trace (core dumped) $ epiphany bwrap: Creating new namespace failed: Permission denied ** (epiphany:30878): ERROR **: 22:22:26.926: Failed to fully launch dbus-proxy: Le processus fils s’est terminé avec le code 1 Trappe pour point d'arrêt et de trace (core dumped) Thanks for your help! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/akonadiconsole/+bug/2046844/+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 2055720] Re: Edubuntu upgrade removed universe repo mantic -> noble
As a quick fix, we will just make sure that universe and multiverse are included in the default sources generated when this case is encountered. That should be the case either way. I am still not sure why you hit this case, but according to the log it didn't look like you had other sources enabled somehow. I marked software-properties invalid since this is pertaining to u-r-u. ** Tags removed: rls-nn-incoming ** Tags added: foundations-todo ** Changed in: ubuntu-release-upgrader (Ubuntu) Assignee: (unassigned) => Nick Rosbrook (enr0n) ** Changed in: software-properties (Ubuntu) Status: New => Invalid ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: New => Confirmed -- 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/2055720 Title: Edubuntu upgrade removed universe repo mantic -> noble Status in software-properties package in Ubuntu: Invalid Status in ubuntu-release-upgrader package in Ubuntu: Confirmed Bug description: Upon upgrade from mantic to noble, my bare metal Edubuntu install removed the Universe repo from the installation and, therefore, did not upgrade any Edubuntu-specific packages. I suspect this was caused by the apt DEB-822 upgrade to the repo and not detecting the universe repo as required by the Edubuntu installation. As Edubuntu looks identical to Ubuntu Desktop in terms of installation on the surface due to it also being a GNOME desktop, I suspect an assumption may have been derived from this. Additionally, simply trying `add-apt-repository universe` was ineffective, so that might need some work as well. Will attach logs if I can find them, but please do advise what logs you need. --- ProblemType: Bug ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 24.04 InstallationDate: Installed on 2023-03-04 (366 days ago) InstallationMedia: Edubuntu 23.04 "Lunar Lobster" - Alpha amd64 Binary-1 (20230304) NonfreeKernelModules: nvidia_modeset nvidia Package: ubuntu-release-upgrader (not installed) ProcVersionSignature: Ubuntu 6.5.0-21.21-generic 6.5.8 Tags: noble wayland-session dist-upgrade Uname: Linux 6.5.0-21-generic x86_64 UpgradeStatus: Upgraded to noble on 2024-03-01 (3 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2055720/+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 2055352] Re: Ubuntu 24.04 texlive fails install
*** This bug is a duplicate of bug 2055216 *** https://bugs.launchpad.net/bugs/2055216 ** This bug has been marked a duplicate of bug 2055216 Syntax error in /usr/bin/mtxrun.lua -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to texlive-base in Ubuntu. https://bugs.launchpad.net/bugs/2055352 Title: Ubuntu 24.04 texlive fails install Status in texlive-base package in Ubuntu: New Bug description: texlive fails with error. lua error : startup file: /usr/bin/mtxrun.lua:2438: attempt to assign to const variable 'i' ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: texlive 2023.20240207-1 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Feb 28 19:20:48 2024 InstallationDate: Installed on 2022-04-07 (693 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220405) PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: texlive-base UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.init.d.apport: 2024-02-22T08:20:00 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/texlive-base/+bug/2055352/+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 2021881] Re: Kwin and plasmashell freeze randomly
Were you able to update mesa to see if it fixes the issue? ** Changed in: kwin (Ubuntu) Status: New => Incomplete ** Changed in: mesa (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2021881 Title: Kwin and plasmashell freeze randomly Status in kwin package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Incomplete Bug description: kwin and plasmashell randomly freeze usually when there is a notification window pop up. I have to use kwin_x11 --replace or plasmashell --replace in order to make screen responsive. Please note I can still type to the app that currently is open (let's say FeatherPad) but things are stuck and I cannot switch tasks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kwin/+bug/2021881/+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 2034986] Re: some text became unreadable during a distribution upgrade
** Tags removed: foundations-todo -- 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/2034986 Title: some text became unreadable during a distribution upgrade Status in Cinnamon: New Status in Ubuntu MATE: New Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-release-upgrader package in Ubuntu: Fix Released Status in ubuntu-release-upgrader source package in Jammy: Fix Released Status in ubuntu-release-upgrader source package in Lunar: Fix Released Status in ubuntu-meta source package in Mantic: Fix Released Status in ubuntu-release-upgrader source package in Mantic: Fix Released Bug description: [ Impact ] * On Ubuntu Mate with the Lunar series, when running ubuntu-release-upgrader, the displayed font of running applications (including the upgrader) becomes very corrupted. * This is not just a display problem, it is also a functional one. The release upgrader will have text corrupted to the point where a dialog asks a decision, and displays two buttons, but the text is unreadable and one has to guess which button is the one that carries out their desired action. * In the early parts of the upgrader tool, users are told in bold: "To prevent data loss close all open applications and documents." This is just before the "Start Upgrade" button is available. But they may not do so. Many applications may have a corrupted font. * To address this, an additional environment variable is being passed along to pkexec, XDG_CURRENT_DESKTOP, as this is the critical criteria for making the Mate version of the fix work. * Also in the change are * an update to tests * from pre-build.sh * an update of the mirrors.cfg, adding and removing several mirrors * a refresh of the po files [ Test Plan ] * acquire an Ubuntu Mate environment running Ubuntu Lunar on amd64 * as user, run "update-manager -d" * monitor the "Distribution Upgrade" screen. During the "Installing the upgrades" step (and mind that this step will be long), observe the text of the "Distribution Upgrade" screen and verify that the font does not corrupt. * Repeat the above for Ubuntu Desktop [ Where problems could occur ] * We are changing, at release time, ubuntu-release upgrader. If we are careless, we could regress upgrades for a wider group of users than just Ubuntu Mate. That said, it is believed that passing the additional XDG_CURRENT_DESKTOP variable is relatively low risk. [ Other Info ] * TBD --- Original description: I was upgrading from Lunar to Mantic the other day and left a couple of applications open during the upgrade process. During the upgrade the text in audacious became unreadable (I'll attach a screenshot) and I seem to recall the title bar of Firefox being unreadable but the contents of web pages still being readable. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: ubuntu-release-upgrader-core 1:23.10.5 ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0 Uname: Linux 6.5.0-4-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Sep 8 15:39:27 2023 InstallationDate: Installed on 2018-08-10 (1855 days ago) InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago) VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', '/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 126: Error executing command as another user: Request dismissed VarLogDistupgradeTermlog: mtime.conffile..etc.update-manager.meta-release: 2021-05-27T16:30:16.970490 To manage notifications about this bug go to: https://bugs.launchpad.net/cinnamon-project/+bug/2034986/+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 1989976]
It seems Firefox implemented passkeys for Windows and MacOS but lack support for Linux as shown in https://www.passkeys.io/compatible-devices I don't quite understand what is so platform specific. Of course, integration in the native platform password manager is nice but not mandatory. Firefox already stores its passwords and can sync them with Firefox Sync. What's so different with passkeys and what's the status of this feature? As a web developer if I can provide passkeys as the primary login method, this would be a great step forward, but it'd be better to have full browser compatibility. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1989976 Title: [upstream] wishlist: Passkeys should be supported Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: Starting from 2022 the main big tech companies introduce Passkeys. Or in the more official name Fido Multi-device credentials. Basically this is a webauthn login, but the private key is distributed among all the devices in a persons Google, Microsoft and iCloud account. If a person wants to login in on a device not in the account a QR code should be scanned after which the computers do some cryptographic magic via Bluetooth. And the new device also has the private key. This method is supposed to be a lot safer and more convenient than the usual passwords. As far as I know this system is open. My wish is that Ubuntu and Linux in general also will support this Passkeys thing. Regards, Martijn. See : https://fidoalliance.org/multi-device-fido-credentials/ https://developers.google.com/identity/fido https://developer.apple.com/passkeys/ To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1989976/+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 2003031] Re: [i915] Using gnome-shell with a USB-C dock causes the kernel to log "adding CRTC not allowed without modesets" and crashes in drm_atomic_check_only
Possibly related? https://bugs.kde.org/show_bug.cgi?id=462214 This bug seems to be for gnome. It looks KDE fixed kwin if I am correctly understanding the bug. ** Bug watch added: KDE Bug Tracking System #462214 https://bugs.kde.org/show_bug.cgi?id=462214 ** Changed in: kwin (Ubuntu) Status: New => Incomplete -- 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/2003031 Title: [i915] Using gnome-shell with a USB-C dock causes the kernel to log "adding CRTC not allowed without modesets" and crashes in drm_atomic_check_only Status in GNOME Shell: New Status in Linux: Unknown Status in kwin package in Ubuntu: Incomplete Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: GJS crashes - here's the crashdump. I saw the crash occur after a screensaver had been running, and the screens had gone blank. I assume this means they were turned off by the sleep timer. When I worke the machine, I was presented with a prompt, I *quickly* entered my login credentials and momentarily saw the desktop and all open programs on it. Then, the screens (3) flickered and I saw the login prompt again. I logged in (again), and all applications had been shut down. I checked /var/log/syslog and saw the following details -- see (log). Uploaded file, and the crashdump. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jan 16 20:52:55 2023 DistUpgraded: 2023-01-14 21:42:30,924 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: kinetic DistroVariant: ubuntu DkmsStatus: 8812au/5.6.4.2_35491.20191025, 5.15.0-58-generic, x86_64: installed 8812au/5.6.4.2_35491.20191025, 5.19.0-29-generic, x86_64: installed nvidia/470.161.03, 5.19.0-29-generic, x86_64: installed virtualbox/6.1.38, 5.15.0-58-generic, x86_64: installed virtualbox/6.1.38, 5.19.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo TigerLake-LP GT2 [Iris Xe Graphics] [17aa:22d4] InstallationDate: Installed on 2023-01-09 (7 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LENOVO 20XY0027US ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-29-generic root=UUID=1cae8af8-977f-4853-9106-9169f34c4bc2 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to kinetic on 2023-01-15 (1 days ago) dmi.bios.date: 07/27/2022 dmi.bios.release: 1.55 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET79W (1.55 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XY0027US dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.33 dmi.modalias: dmi:bvnLENOVO:bvrN32ET79W(1.55):bd07/27/2022:br1.55:efr1.33:svnLENOVO:pn20XY0027US:pvrThinkPadX1YogaGen6:rvnLENOVO:rn20XY0027US:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20XY_BU_Think_FM_ThinkPadX1YogaGen6: dmi.product.family: ThinkPad X1 Yoga Gen 6 dmi.product.name: 20XY0027US dmi.product.sku: LENOVO_MT_20XY_BU_Think_FM_ThinkPad X1 Yoga Gen 6 dmi.product.version: ThinkPad X1 Yoga Gen 6 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.3 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/gnome-shell/+bug/2003031/+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 2000463] Re: Session crashes (desktop environment (Plasma/KWin) and game) due to AMD RX 6900XT GPU "resetting"
I feel like this is more drm / mesa / driver issue and not kwin... Is this still an issue? ** Changed in: kwin (Ubuntu) Status: New => Incomplete ** Changed in: xserver-xorg-video-amdgpu (Ubuntu) Status: New => Incomplete -- 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/2000463 Title: Session crashes (desktop environment (Plasma/KWin) and game) due to AMD RX 6900XT GPU "resetting" Status in kwin package in Ubuntu: Incomplete Status in xserver-xorg-video-amdgpu package in Ubuntu: Incomplete Bug description: I was playing Halo Infinite when my session would lock up and would needed to be restarted. Dec 26 02:26:51 Y4M1-II kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! Dec 26 02:26:51 Y4M1-II kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! Dec 26 02:26:51 Y4M1-II kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! Dec 26 02:26:51 Y4M1-II kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! Dec 26 02:26:51 Y4M1-II kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! Dec 26 02:26:51 Y4M1-II kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! Dec 26 02:26:51 Y4M1-II kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! Dec 26 02:26:51 Y4M1-II kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! Dec 26 02:26:51 Y4M1-II kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! Dec 26 02:26:51 Y4M1-II kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! Dec 26 02:26:51 Y4M1-II kernel: amdgpu_cs_ioctl: 3017 callbacks suppressed Dec 26 02:26:46 Y4M1-II kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! Dec 26 02:26:46 Y4M1-II kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! Dec 26 02:26:46 Y4M1-II kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! Dec 26 02:26:46 Y4M1-II kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! Dec 26 02:26:46 Y4M1-II kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! Dec 26 02:26:46 Y4M1-II kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! Dec 26 02:26:46 Y4M1-II kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! Dec 26 02:26:46 Y4M1-II kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! Dec 26 02:26:46 Y4M1-II kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! Dec 26 02:26:46 Y4M1-II kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! Dec 26 02:26:46 Y4M1-II kernel: amdgpu_cs_ioctl: 4783 callbacks suppressed Dec 26 02:26:41 Y4M1-II kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! Dec 26 02:26:41 Y4M1-II kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! Dec 26 02:26:41 Y4M1-II kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! Dec 26 02:26:41 Y4M1-II kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! Dec 26 02:26:41 Y4M1-II kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! Dec 26 02:26:41 Y4M1-II kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! Dec 26 02:26:41 Y4M1-II kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! Dec 26 02:26:41 Y4M1-II kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! Dec 26 02:26:41 Y4M1-II kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! Dec 26 02:26:41 Y4M1-II kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! Dec 26 02:26:41 Y4M1-II kernel: amdgpu_cs_ioctl: 5290 callbacks suppressed Dec 26 02:26:37 Y4M1-II audit[1084821]: SECCOMP auid=1000 uid=1000 gid=1000 ses=4 subj=snap.firefox_beta.firefox pid=1084821 comm="crashreporter" exe="/snap/firefox/2240/usr/lib/firefox/crashreporter" sig=0 ar> Dec 26 02:26:37 Y4M1-II audit[1084756]: AVC apparmor="DENIED" operation="open" class="file" profile="snap.firefox_beta.firefox" name="/proc/14786/environ" pid=1084756 comm="firefox" requested_mask="r" denied_m> Dec 26 02:26:37 Y4M1-II audit[1084754]: SECCOMP auid=1000 uid=1000 gid=1000 ses=4 subj=snap.thunderbird.thunderbird pid=1084754 comm="crashreporter" exe="/snap/thunderbird/281/crashreporter" sig=0 arch=c03> Dec 26 02:26:37 Y4M1-II audit[1084658]: AVC apparmor="DENIED" operation="open" class="file"
[Desktop-packages] [Bug 2049254] Re: Snap Firefox crashes when trying to save anything
ThomasWG, my somewhat delayed reply acknowledges your comment #2. As the issue was never confirmed by another user and in the absence of an upstream bug report from Mozilla I'm closing this as 'Invalid' rather than 'Fix Released' but thanks for reporting your issue. ** Changed in: firefox (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/2049254 Title: Snap Firefox crashes when trying to save anything Status in firefox package in Ubuntu: Invalid Bug description: This was originally a fresh install from an ISO from 4 days ago, I have already ripped it out and reinstalled it with same errors. Snap Firefox crashes when trying to save anything, or trying to save settings, once you close and reopen it, most reset, but extensions still work somewhat. This is from Ubuntu 22.04.3 LTS Jammy Jellyfish (x86-64) Its says in the 'About Mozilla Firefox" thats this is the 110.0 64-bit version, Mozilla Firefox Snap for Ubuntu canonical-002 - 1.0 The previous non snap version worked great, this version forget it. These are the results, I got. thomas@thomas:~$ sudo apt install firefox [sudo] password for thomas: Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages were automatically installed and are no longer required: attr gnome-desktop-testing libqrcodegencpp1 librlottie0-1 libwmf0.2-7 libxcb-record0 libxcb-screensaver0 Use 'sudo apt autoremove' to remove them. The following NEW packages will be installed: firefox 0 upgraded, 1 newly installed, 0 to remove and 1 not upgraded. Need to get 72.3 kB of archives. After this operation, 261 kB of additional disk space will be used. Get:1 http://ca.archive.ubuntu.com/ubuntu jammy/main amd64 firefox amd64 1:1snap1-0ubuntu2 [72.3 kB] Fetched 72.3 kB in 1s (116 kB/s) Preconfiguring packages ... Selecting previously unselected package firefox. (Reading database ... 414409 files and directories currently installed.) Preparing to unpack .../firefox_1%3a1snap1-0ubuntu2_amd64.deb ... => Installing the firefox snap ==> Checking connectivity with the snap store ==> Installing the firefox snap snap "firefox" is already installed, see 'snap help refresh' => Snap installation complete Unpacking firefox (1:1snap1-0ubuntu2) ... Setting up firefox (1:1snap1-0ubuntu2) ... Processing triggers for mailcap (3.70+nmu1ubuntu1) ... Processing triggers for desktop-file-utils (0.26-1ubuntu3) ... Processing triggers for hicolor-icon-theme (0.17-2) ... Processing triggers for gnome-menus (3.36.0-1ubuntu3) ... thomas@thomas:~$ firefox -safemode Gtk-Message: 02:00:31.385: Failed to load module "xapp-gtk3-module" Gtk-Message: 02:00:31.385: Not loading module "atk-bridge": The functionality is provided by GTK natively. Please try to not load it. /home/thomas/snap/firefox/common/.cache/gio-modules/libgioenvironmentproxy.so: cannot open shared object file: No such file or directory Failed to load module: /home/thomas/snap/firefox/common/.cache/gio-modules/libgioenvironmentproxy.so /home/thomas/snap/firefox/common/.cache/gio-modules/libgiognomeproxy.so: cannot open shared object file: No such file or directory Failed to load module: /home/thomas/snap/firefox/common/.cache/gio-modules/libgiognomeproxy.so /home/thomas/snap/firefox/common/.cache/gio-modules/libgiolibproxy.so: cannot open shared object file: No such file or directory Failed to load module: /home/thomas/snap/firefox/common/.cache/gio-modules/libgiolibproxy.so /home/thomas/snap/firefox/common/.cache/gio-modules/libdconfsettings.so: cannot open shared object file: No such file or directory Failed to load module: /home/thomas/snap/firefox/common/.cache/gio-modules/libdconfsettings.so /home/thomas/snap/firefox/common/.cache/gio-modules/libgiognutls.so: cannot open shared object file: No such file or directory Failed to load module: /home/thomas/snap/firefox/common/.cache/gio-modules/libgiognutls.so (firefox:39363): Gtk-WARNING **: 02:00:31.578: Could not load a pixbuf from icon theme. This may indicate that pixbuf loaders or the mime database could not be found. [Parent 39363, Main Thread] WARNING: gdk_cairo_surface_create_from_pixbuf: assertion 'GDK_IS_PIXBUF (pixbuf)' failed: 'glib warning', file /build/firefox/parts/firefox/build/toolkit/xre/nsSigHandlers.cpp:167 (firefox:39363): Gdk-CRITICAL **: 02:00:31.578: gdk_cairo_surface_create_from_pixbuf: assertion 'GDK_IS_PIXBUF (pixbuf)' failed [Parent 39363, Main Thread] WARNING: g_object_unref: assertion 'G_IS_OBJECT (object)' failed: 'glib warning', file /build/firefox/parts/firefox/build/toolkit/xre/nsSigHandlers.cpp:167 (firefox:39363): GLib-GObject-CRITICAL **: 02:00:31.578: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
[Desktop-packages] [Bug 2056432] Re: Thunderbird profile not migrated to snap
The problems seems to be caused by the property LastProfile not being copied to the Snap instance. -- 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/2056432 Title: Thunderbird profile not migrated to snap Status in thunderbird package in Ubuntu: New 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. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: thunderbird 1:115.8.1+build1+snap2 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 NonfreeKernelModules: zfs nvidia_modeset nvidia ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Mar 7 09:57:56 2024 InstallationDate: Installed on 2021-05-26 (1016 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SnapChanges: IDStatus Spawn Ready Summary 1092 Done2024-03-07T09:44:07+01:00 2024-03-07T09:54:05+01:00 Install "thunderbird" snap SourcePackage: thunderbird UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/2056432/+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 2039235] Re: gnome-online-accounts -> when signing into google account, infinite loading after entering password
I am closing this issue because it is fixed in Ubuntu 24.04 LTS which is expected to be released later in April. It was fixed by switching gnome- online-accounts to always use your browser for log in instead of an embedded webkit powered popup window. That kind of change is probably too large to try to backport to Ubuntu 23.10 and our developer time is focused now on getting Ubuntu 24.04 LTS ready. ** Changed in: gnome-online-accounts (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/2039235 Title: gnome-online-accounts -> when signing into google account, infinite loading after entering password Status in gnome-online-accounts package in Ubuntu: Fix Released Bug description: 1) What you expected to happen - sign in is successful, which will allow google services to populate the appropriate applications (calendar, mail, google drive) 2) What actually happened - sign in hangs infinitely after entering the password - the process is able to detect that the password is correct or incorrect. When entering an incorrect password, it will correctly and quickly complain that the password is incorrect. When entering the correct password, the bug will occur. 3) Steps to reproduce a) start the program b) select online accounts c) select google d) enter email e) enter password f) loads forever ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-online-accounts 3.48.0-2 ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Oct 12 22:27:59 2023 InstallationDate: Installed on 2023-10-12 (0 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231011) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-online-accounts UpgradeStatus: No upgrade log present (probably fresh install) Hardware info (not sure if relevant): cpu: intel gpu: nvidia (driver version: "Using NVIDIA driver metapackage from nvidia-driver-535(proprietary, tested)") To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/2039235/+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 1885646] Re: RM ring FTBFS
** Tags removed: update-excuse -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nettle in Ubuntu. https://bugs.launchpad.net/bugs/1885646 Title: RM ring FTBFS Status in nettle package in Ubuntu: Incomplete Status in ring package in Ubuntu: Fix Released Status in ring package in Debian: Fix Released Bug description: Please remove ring 20190215.1.f152c98~ds1-1build4 groovy-proposed ring 20190215.1.f152c98~ds1-1build2 groovy-release FTBFS, RC-buggy, removed from testing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nettle/+bug/1885646/+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 2039235] Re: gnome-online-accounts -> when signing into google account, infinite loading after entering password
I have the same issue. I have security key added to my account. The reload did the trick. Thank you for sharing this! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/2039235 Title: gnome-online-accounts -> when signing into google account, infinite loading after entering password Status in gnome-online-accounts package in Ubuntu: Confirmed Bug description: 1) What you expected to happen - sign in is successful, which will allow google services to populate the appropriate applications (calendar, mail, google drive) 2) What actually happened - sign in hangs infinitely after entering the password - the process is able to detect that the password is correct or incorrect. When entering an incorrect password, it will correctly and quickly complain that the password is incorrect. When entering the correct password, the bug will occur. 3) Steps to reproduce a) start the program b) select online accounts c) select google d) enter email e) enter password f) loads forever ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-online-accounts 3.48.0-2 ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Oct 12 22:27:59 2023 InstallationDate: Installed on 2023-10-12 (0 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231011) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-online-accounts UpgradeStatus: No upgrade log present (probably fresh install) Hardware info (not sure if relevant): cpu: intel gpu: nvidia (driver version: "Using NVIDIA driver metapackage from nvidia-driver-535(proprietary, tested)") To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/2039235/+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 1970069] Re: Annoying boot messages interfering with splash screen
I've analysed a couple of Noble systems today and don't think initramfs-
tools needs improving (although it might not hurt). On both systems,
plymouth-start was within 1 second of simpledrm starting (same
timestamp), but the bug still occurs. The reasons are:
1. One system actually experiences the bug ("fbcon: Taking over
console") _before_ "Initialized simpledrm" due to kernel error-level
messages.
2. After setting loglevel=3 (bug 2049390), it's a slight improvement but
the "clean" message from fsck via systemd still interrupts the boot
sequence.
So it looks like we need either:
* loglevel=3 (bug 2049390) and a systemd fix for fsck; or
* The kernel patch I've already proposed upstream.
** Changed in: initramfs-tools (Ubuntu)
Status: In Progress => Opinion
--
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/1970069
Title:
Annoying boot messages interfering with splash screen
Status in initramfs-tools package in Ubuntu:
Opinion
Status in linux package in Ubuntu:
In Progress
Status in plymouth package in Ubuntu:
Invalid
Status in systemd package in Ubuntu:
In Progress
Bug description:
[ Impact ]
Kernel (and systemd) log messages appear during boot for many
machines, when the user should be seeing only the BIOS logo and/or
Plymouth splash screens.
[ Workaround ]
On most machines you can hide the problem by using these kernel parameters
together:
quiet splash loglevel=2 fastboot
[ Test Plan ]
1. Boot Ubuntu on a number of laptops that have the problem and verify no
console text messages appear during boot.
2. Verify you can switch VTs (e.g. Ctrl + Alt + F4) and log into them still.
3. Reboot Ubuntu and remove the "splash" kernel parameter, now messages
should appear.
[ Where problems could occur ]
Since the fix works by deferring fbcon's takeover of the console, the
main problem encountered during its development was the inability to
VT switch.
[ Original Description ]
Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not
as clean as it used to be.
Basically, the flow used to be in 20.04:
GRUB > Splash screen > Login prompt
Currently in 22.04:
GRUB > Splash screen > Messages (in the attached file) > Splash screen
again for a sec > Login prompt
All of those messages already existed in 20.04, the difference is that
they were not appearing during boot.
I was able to get rid of the "usb" related messages by just adding
"loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash".
Regarding the fsck related message, I can get rid of them by adding
"fsck.mode=skip".
However, I do not want to just disable fsck or set the loglevel to 0.
This is not a sustainable solution.
Something definitely changed here. These messages are not of enough
relevance to be shown at boot by default, and they should remain
hidden like they were in Focal.
Obviously a minor issue, but important to the whole look and feel of
the OS for desktop.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1970069/+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 2054213] Re: Desktop Settings dialog hanging
** Package changed: ubuntu => gnome-control-center (Ubuntu) -- 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/2054213 Title: Desktop Settings dialog hanging Status in gnome-control-center package in Ubuntu: New Bug description: After reconfiguring a dual display to 'mirror' and then 'join' and changing display size %age the dialog appears to hang. The 'apply' button is disable and I can't close the dialog. The dialog appears to pick up your settings, but you need to logout and login again to close the dialog and for the settings to apply. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2054213/+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 2056436] [NEW] Every time Firefox starts it produces a file not found page
Public bug reported: Every time Firefox starts it produces a file not found page saying File not found Firefox can’t find the file at /snap/snapd/current/usr/bin/snap. Check the file name for capitalisation or other typing errors. Check to see if the file was moved, renamed or deleted. There is no such file on the system. There is a /snap directory, but not /snap/snapd/ . This happens regardless of the at Startup settings ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: firefox 1:1snap1-0ubuntu5 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Mar 7 09:52:10 2024 InstallationDate: Installed on 2017-12-06 (2283 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SnapChanges: IDStatus Spawn Ready Summary 1331 Done2024-03-06T10:00:00Z 2024-03-06T10:00:25Z Refresh snaps "firefox", "snap-store" SourcePackage: firefox UpgradeStatus: Upgraded to noble on 2023-11-28 (100 days ago) ** Affects: firefox (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 firefox in Ubuntu. https://bugs.launchpad.net/bugs/2056436 Title: Every time Firefox starts it produces a file not found page Status in firefox package in Ubuntu: New Bug description: Every time Firefox starts it produces a file not found page saying File not found Firefox can’t find the file at /snap/snapd/current/usr/bin/snap. Check the file name for capitalisation or other typing errors. Check to see if the file was moved, renamed or deleted. There is no such file on the system. There is a /snap directory, but not /snap/snapd/ . This happens regardless of the at Startup settings ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: firefox 1:1snap1-0ubuntu5 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Mar 7 09:52:10 2024 InstallationDate: Installed on 2017-12-06 (2283 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SnapChanges: IDStatus Spawn Ready Summary 1331 Done2024-03-06T10:00:00Z 2024-03-06T10:00:25Z Refresh snaps "firefox", "snap-store" SourcePackage: firefox UpgradeStatus: Upgraded to noble on 2023-11-28 (100 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2056436/+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 2055351] Re: [amdgpu] Firefox and Chromium browser windows are corrupt in Xorg
Similar hardware: R7 240 graphics card (previous generation graphics cores) on Athlon 200GE: everything works fine on X11 Plugged SSD from Athlon install into 5600G (Vega 6 graphics instead of Vega 3): everything works fine on X11. So it seems to be something weird about Vega 3 graphics in relation to amdgpu & xserver-xorg-video-amdgpu. I don't speak Git, but I am happy to download, compile, and test anything you would like me to if you don't have access to matching hardware. -- 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/2055351 Title: [amdgpu] Firefox and Chromium browser windows are corrupt in Xorg Status in mesa package in Ubuntu: New Status in xserver-xorg-video-amdgpu package in Ubuntu: New Bug description: I downloaded the 22.04.4 iso and did a fresh install on an AMD Athlon 200GE using built-in graphics. (Radeon™ Vega 3 Graphics) Firefox and Chromium browsers had their windows corrupted to the point where they were unreadable. I think this is an xorg bug, because when I installed Wayland and logged in with a Wayland session, the browsers displayed correctly. Same behaviour with an Athlon 220GE. KDE or Ubuntu's Gnome desktop made no difference - it seemed to be xorg vs Wayland that was the critical difference. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistroCodename: jammy DistroRelease: Ubuntu 22.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] (rev cb) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. PRIME Motherboard [1043:876b] InstallationDate: Installed on 2024-02-26 (3 days ago) InstallationMedia: Kubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240216.1) MachineType: System manufacturer System Product Name Package: xorg-server (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-21-generic root=UUID=7e6c3c76-1566-4670-97ab-3755e9a04b18 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-21.21~22.04.1-generic 6.5.8 Tags: jammy wayland-session ubuntu Uname: Linux 6.5.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/04/2023 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 6210 dmi.board.asset.tag: Default string dmi.board.name: PRIME A320M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr6210:bd09/04/2023:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEA320M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1~22.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 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 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistroCodename: jammy DistroRelease: Ubuntu 22.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] (rev cb) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. PRIME Motherboard [1043:876b] InstallationDate: Installed on 2024-02-26 (3 days ago) InstallationMedia: Kubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240216.1) MachineType: System manufacturer System Product Name Package: xorg-server (not installed) ProcKernelCmdLine:
[Desktop-packages] [Bug 2054213] [NEW] Desktop Settings dialog hanging
You have been subscribed to a public bug: After reconfiguring a dual display to 'mirror' and then 'join' and changing display size %age the dialog appears to hang. The 'apply' button is disable and I can't close the dialog. The dialog appears to pick up your settings, but you need to logout and login again to close the dialog and for the settings to apply. ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- Desktop Settings dialog hanging https://bugs.launchpad.net/bugs/2054213 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center 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 2056434] Re: Thunderbird profile not migrated to snap
Looking at ~/.cache/thunderbird it is evident that ji04wv64.default- release is last. drwxr-xr-x 70 user group 4096 Mär 7 09:58 .. drwx-- 5 user group 4096 Mär 6 10:16 ji04wv64.default-release drwx-- 4 user group 4096 Jul 8 2021 . drwx-- 2 user group 4096 Jul 8 2021 ao6t0qef.default -- 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: New 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 2056434] Re: Thunderbird profile not migrated to snap
Could it be that the LastProfile property is not migrated? -- 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: New 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 2056434] [NEW] Thunderbird profile not migrated to snap
Public bug reported: 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. ** Affects: thunderbird (Ubuntu) Importance: Undecided Status: New -- 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: New 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 2055519] Re: Mutter rebuilds on jammy fail test: mutter:cogl+cogl/conform / framebuffer-get-bits (due to Mesa >= 23.1.1)
** Changed in: mutter (Ubuntu) Importance: High => Medium ** Changed in: mutter (Ubuntu Jammy) Importance: High => Medium -- 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/2055519 Title: Mutter rebuilds on jammy fail test: mutter:cogl+cogl/conform / framebuffer-get-bits (due to Mesa >= 23.1.1) Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Jammy: In Progress Bug description: [ Impact ] Mutter's test cases fail on jammy since Mesa got updated: mutter:cogl+cogl/conform / framebuffer-get-bits [ Test Plan ] Build mutter and run its tests (done automatically during packaging) [ Where problems could occur ] More tests fail. [ Other Info ] 27/113 mutter:cogl+cogl/conform / framebuffer-get-bits RUNNING >>> RUN_TESTS_QUIET=1 PATH=/usr/lib/s390x-linux-gnu:/<>/obj-s390x-linux-gnu/cogl/cogl:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games MALLOC_PERTURB_=176 /<>/src/tests/meta-dbus-runner.py /<>/cogl/tests/run-tests.sh /<>/obj-s390x-linux-gnu/cogl/tests/config.env cogl/tests/conform/test-conformance test_framebuffer_get_bits ― ✀ ― Starting D-Bus daemons (session & system)... Starting mocked services... Running test case... Test GL+GLSL GL3 ES2 test_framebuffer_get_bits: ok FAIL n/a Traceback (most recent call last): File "/<>/src/tests/meta-dbus-runner.py", line 184, in test_case.wrap_call(rest[1:]) File "/<>/src/tests/meta-dbus-runner.py", line 171, in wrap_call self.assertEqual(p.wait(), 0) File "/usr/lib/python3.10/unittest/case.py", line 845, in assertEqual assertion_func(first, second, msg=msg) File "/usr/lib/python3.10/unittest/case.py", line 838, in _baseAssertEqual raise self.failureException(msg) AssertionError: 134 != 0 ―― 27/113 mutter:cogl+cogl/conform / framebuffer-get-bits FAIL 2.35s exit status 1 and 27/113 mutter:cogl+cogl/conform / framebuffer-get-bits RUNNING >>> MALLOC_PERTURB_=159 PATH=/<>/obj-aarch64-linux-gnu/cogl/cogl:/usr/lib/aarch64-linux-gnu:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games RUN_TESTS_QUIET=1 /<>/src/tests/meta-dbus-runner.py /<>/cogl/tests/run-tests.sh /<>/obj-aarch64-linux-gnu/cogl/tests/config.env cogl/tests/conform/test-conformance test_framebuffer_get_bits ― ✀ ― Starting D-Bus daemons (session & system)... Starting mocked services... Running test case... Test GL+GLSL GL3 ES2 test_framebuffer_get_bits: ok FAIL n/a Traceback (most recent call last): File "/<>/src/tests/meta-dbus-runner.py", line 184, in test_case.wrap_call(rest[1:]) File "/<>/src/tests/meta-dbus-runner.py", line 171, in wrap_call self.assertEqual(p.wait(), 0) File "/usr/lib/python3.10/unittest/case.py", line 845, in assertEqual assertion_func(first, second, msg=msg) File "/usr/lib/python3.10/unittest/case.py", line 838, in _baseAssertEqual raise self.failureException(msg) AssertionError: 134 != 0 ―― 27/113 mutter:cogl+cogl/conform / framebuffer-get-bits FAIL 0.83s exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2055519/+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 2056432] [NEW] Thunderbird profile not migrated to snap
Public bug reported: 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. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: thunderbird 1:115.8.1+build1+snap2 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 NonfreeKernelModules: zfs nvidia_modeset nvidia ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Mar 7 09:57:56 2024 InstallationDate: Installed on 2021-05-26 (1016 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SnapChanges: IDStatus Spawn Ready Summary 1092 Done2024-03-07T09:44:07+01:00 2024-03-07T09:54:05+01:00 Install "thunderbird" snap SourcePackage: thunderbird UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: thunderbird (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble -- 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/2056432 Title: Thunderbird profile not migrated to snap Status in thunderbird package in Ubuntu: New 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. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: thunderbird 1:115.8.1+build1+snap2 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 NonfreeKernelModules: zfs nvidia_modeset nvidia ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Mar 7 09:57:56 2024 InstallationDate: Installed on 2021-05-26 (1016 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SnapChanges: IDStatus Spawn Ready Summary 1092 Done2024-03-07T09:44:07+01:00 2024-03-07T09:54:05+01:00 Install "thunderbird" snap SourcePackage: thunderbird UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/2056432/+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 1970069] Re: Annoying boot messages interfering with splash screen
** Also affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Changed in: initramfs-tools (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: initramfs-tools (Ubuntu) Importance: Undecided => Medium ** Changed in: initramfs-tools (Ubuntu) Status: New => In Progress -- 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/1970069 Title: Annoying boot messages interfering with splash screen Status in initramfs-tools package in Ubuntu: In Progress Status in linux package in Ubuntu: In Progress Status in plymouth package in Ubuntu: Invalid Status in systemd package in Ubuntu: In Progress Bug description: [ Impact ] Kernel (and systemd) log messages appear during boot for many machines, when the user should be seeing only the BIOS logo and/or Plymouth splash screens. [ Workaround ] On most machines you can hide the problem by using these kernel parameters together: quiet splash loglevel=2 fastboot [ Test Plan ] 1. Boot Ubuntu on a number of laptops that have the problem and verify no console text messages appear during boot. 2. Verify you can switch VTs (e.g. Ctrl + Alt + F4) and log into them still. 3. Reboot Ubuntu and remove the "splash" kernel parameter, now messages should appear. [ Where problems could occur ] Since the fix works by deferring fbcon's takeover of the console, the main problem encountered during its development was the inability to VT switch. [ Original Description ] Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not as clean as it used to be. Basically, the flow used to be in 20.04: GRUB > Splash screen > Login prompt Currently in 22.04: GRUB > Splash screen > Messages (in the attached file) > Splash screen again for a sec > Login prompt All of those messages already existed in 20.04, the difference is that they were not appearing during boot. I was able to get rid of the "usb" related messages by just adding "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash". Regarding the fsck related message, I can get rid of them by adding "fsck.mode=skip". However, I do not want to just disable fsck or set the loglevel to 0. This is not a sustainable solution. Something definitely changed here. These messages are not of enough relevance to be shown at boot by default, and they should remain hidden like they were in Focal. Obviously a minor issue, but important to the whole look and feel of the OS for desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1970069/+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
