[Desktop-packages] [Bug 2060266] [NEW] gnome-session no longer supports --builtin

2024-04-05 Thread Haw Loeung
Public bug reported:

Hi,

`gnome-session.service` has the following:

| [Service]
| ExecStart=/bin/sh -exc '[ "$DESKTOP_SESSION" != "gnome-classic" ] || export | 
GNOME_SHELL_SESSION_MODE=classic; \
| export GNOME_SESSION_XDG_SESSION_PATH=${XDG_SESSION_PATH}; \
| [ "$DESKTOP_SESSION" = gnome-flashback-metacity ] && \
| exec gnome-session --builtin --session=$DESKTOP_SESSION 
--disable-acceleration-check || \
| exec gnome-session --builtin --session=$DESKTOP_SESSION'

Unfortunately, the latest `gnome-session` no longer supports
`--builtin`. This causes login failures, in particular for me, using
Unity, I get logged back out from the unity greeter.

| $ apt-cache policy gnome-session-bin
| gnome-session-bin:
|   Installed: 46.0-1ubuntu2
|   Candidate: 46.0-1ubuntu2
|   Version table:
|  *** 46.0-1ubuntu2 500
| 500 http://haw-test.archive.ubuntu.com/ubuntu noble/main amd64 
Packages
| 100 /var/lib/dpkg/status
|  45.0-1ubuntu1 500
| 500 http://haw-test.archive.ubuntu.com/ubuntu noble-updates/main 
amd64 Packages

| $ gnome-session --builtin
|
| ** (gnome-session-binary:5602): WARNING **: 15:35:22.156: Unknown option 
--builtin

Removing `--builtin` from `/usr/lib/systemd/user/gnome-session.service`
let's me log in.

With that though, I was not able to input text in chromium (installed
via the snap).

Downgrading `gnome-session-bin`, `gnome-session-common`, and `unity-
session` back to 45.0-1ubuntu1 restores things for me:

| [hloeung@dharkan tmp]$ apt-cache policy gnome-session-bin
| gnome-session-bin:
|   Installed: 45.0-1ubuntu1
|   Candidate: 46.0-1ubuntu2
|   Version table:
|  46.0-1ubuntu2 500
| 500 http://haw-test.archive.ubuntu.com/ubuntu noble/main amd64 
Packages
|  *** 45.0-1ubuntu1 500
| 500 http://haw-test.archive.ubuntu.com/ubuntu noble-updates/main 
amd64 Packages
| 100 /var/lib/dpkg/status
| [hloeung@dharkan tmp]$ apt-cache policy gnome-session-common
| gnome-session-common:
|   Installed: 45.0-1ubuntu1
|   Candidate: 46.0-1ubuntu2
|   Version table:
|  46.0-1ubuntu2 500
| 500 http://haw-test.archive.ubuntu.com/ubuntu noble/main amd64 
Packages
|  *** 45.0-1ubuntu1 500
| 500 http://haw-test.archive.ubuntu.com/ubuntu noble-updates/main 
amd64 Packages
| 100 /var/lib/dpkg/status
| [hloeung@dharkan tmp]$ apt-cache policy unity-session
| unity-session:
|   Installed: 45.0-1ubuntu1
|   Candidate: 46.0-1ubuntu2
|   Version table:
|  46.0-1ubuntu2 500
| 500 http://haw-test.archive.ubuntu.com/ubuntu noble/universe amd64 
Packages
|  *** 45.0-1ubuntu1 500
| 500 http://haw-test.archive.ubuntu.com/ubuntu noble-updates/universe 
amd64 Packages
| 100 /var/lib/dpkg/status

** Affects: gnome-session (Ubuntu)
 Importance: Undecided
 Status: New

** Description changed:

  Hi,
  
  `gnome-session.service` has the following:
  
  | [Service]
  | ExecStart=/bin/sh -exc '[ "$DESKTOP_SESSION" != "gnome-classic" ] || export 
| GNOME_SHELL_SESSION_MODE=classic; \
  | export GNOME_SESSION_XDG_SESSION_PATH=${XDG_SESSION_PATH}; \
  | [ "$DESKTOP_SESSION" = gnome-flashback-metacity ] && \
  | exec gnome-session --builtin --session=$DESKTOP_SESSION 
--disable-acceleration-check || \
  | exec gnome-session --builtin --session=$DESKTOP_SESSION'
  
  Unfortunately, the latest `gnome-session` no longer supports
  `--builtin`. This causes login failures, in particular for me, using
  Unity, I get logged back out from the unity greeter.
  
  | $ apt-cache policy gnome-session-bin
  | gnome-session-bin:
  |   Installed: 46.0-1ubuntu2
  |   Candidate: 46.0-1ubuntu2
  |   Version table:
  |  *** 46.0-1ubuntu2 500
  | 500 http://haw-test.archive.ubuntu.com/ubuntu noble/main amd64 
Packages
  | 100 /var/lib/dpkg/status
  |  45.0-1ubuntu1 500
  | 500 http://haw-test.archive.ubuntu.com/ubuntu noble-updates/main 
amd64 Packages
  
  | $ gnome-session --builtin
  |
  | ** (gnome-session-binary:5602): WARNING **: 15:35:22.156: Unknown option 
--builtin
+ 
+ Removing `--builtin` from `/usr/lib/systemd/user/gnome-session.service`
+ let's me log in.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/2060266

Title:
  gnome-session no longer supports --builtin

Status in gnome-session package in Ubuntu:
  New

Bug description:
  Hi,

  `gnome-session.service` has the following:

  | [Service]
  | ExecStart=/bin/sh -exc '[ "$DESKTOP_SESSION" != "gnome-classic" ] || export 
| GNOME_SHELL_SESSION_MODE=classic; \
  | export GNOME_SESSION_XDG_SESSION_PATH=${XDG_SESSION_PATH}; \
  | [ "$DESKTOP_SESSION" = gnome-flashback-metacity ] && \
  | exec gnome-session --builtin --session=$DESKTOP_SESSION 
--disable-acceleration-check || \
  | exec gnome-session --builtin --session=$DESKTOP_SESSION'

  Unfortunately, the lat

[Desktop-packages] [Bug 2060266] Re: gnome-session no longer supports --builtin

2024-04-05 Thread Haw Loeung
** Tags added: noble

** Also affects: gnome-session (Ubuntu Noble)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/2060266

Title:
  gnome-session no longer supports --builtin

Status in gnome-session package in Ubuntu:
  New
Status in gnome-session source package in Noble:
  New

Bug description:
  Hi,

  `gnome-session.service` has the following:

  | [Service]
  | ExecStart=/bin/sh -exc '[ "$DESKTOP_SESSION" != "gnome-classic" ] || export 
| GNOME_SHELL_SESSION_MODE=classic; \
  | export GNOME_SESSION_XDG_SESSION_PATH=${XDG_SESSION_PATH}; \
  | [ "$DESKTOP_SESSION" = gnome-flashback-metacity ] && \
  | exec gnome-session --builtin --session=$DESKTOP_SESSION 
--disable-acceleration-check || \
  | exec gnome-session --builtin --session=$DESKTOP_SESSION'

  Unfortunately, the latest `gnome-session` no longer supports
  `--builtin`. This causes login failures, in particular for me, using
  Unity, I get logged back out from the unity greeter.

  | $ apt-cache policy gnome-session-bin
  | gnome-session-bin:
  |   Installed: 46.0-1ubuntu2
  |   Candidate: 46.0-1ubuntu2
  |   Version table:
  |  *** 46.0-1ubuntu2 500
  | 500 http://haw-test.archive.ubuntu.com/ubuntu noble/main amd64 
Packages
  | 100 /var/lib/dpkg/status
  |  45.0-1ubuntu1 500
  | 500 http://haw-test.archive.ubuntu.com/ubuntu noble-updates/main 
amd64 Packages

  | $ gnome-session --builtin
  |
  | ** (gnome-session-binary:5602): WARNING **: 15:35:22.156: Unknown option 
--builtin

  Removing `--builtin` from `/usr/lib/systemd/user/gnome-
  session.service` let's me log in.

  With that though, I was not able to input text in chromium (installed
  via the snap).

  Downgrading `gnome-session-bin`, `gnome-session-common`, and `unity-
  session` back to 45.0-1ubuntu1 restores things for me:

  | [hloeung@dharkan tmp]$ apt-cache policy gnome-session-bin
  | gnome-session-bin:
  |   Installed: 45.0-1ubuntu1
  |   Candidate: 46.0-1ubuntu2
  |   Version table:
  |  46.0-1ubuntu2 500
  | 500 http://haw-test.archive.ubuntu.com/ubuntu noble/main amd64 
Packages
  |  *** 45.0-1ubuntu1 500
  | 500 http://haw-test.archive.ubuntu.com/ubuntu noble-updates/main 
amd64 Packages
  | 100 /var/lib/dpkg/status
  | [hloeung@dharkan tmp]$ apt-cache policy gnome-session-common
  | gnome-session-common:
  |   Installed: 45.0-1ubuntu1
  |   Candidate: 46.0-1ubuntu2
  |   Version table:
  |  46.0-1ubuntu2 500
  | 500 http://haw-test.archive.ubuntu.com/ubuntu noble/main amd64 
Packages
  |  *** 45.0-1ubuntu1 500
  | 500 http://haw-test.archive.ubuntu.com/ubuntu noble-updates/main 
amd64 Packages
  | 100 /var/lib/dpkg/status
  | [hloeung@dharkan tmp]$ apt-cache policy unity-session
  | unity-session:
  |   Installed: 45.0-1ubuntu1
  |   Candidate: 46.0-1ubuntu2
  |   Version table:
  |  46.0-1ubuntu2 500
  | 500 http://haw-test.archive.ubuntu.com/ubuntu noble/universe amd64 
Packages
  |  *** 45.0-1ubuntu1 500
  | 500 http://haw-test.archive.ubuntu.com/ubuntu 
noble-updates/universe amd64 Packages
  | 100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/2060266/+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 2040977] Re: Mouse cursor stutters if nothing else is animating on screen

2024-04-05 Thread Launchpad Bug Tracker
This bug was fixed in the package mutter - 46.0-1ubuntu6

---
mutter (46.0-1ubuntu6) noble; urgency=medium

  * Rebuild for CVE-2024-3094

 -- Jeremy Bícha   Sun, 31 Mar 2024 10:24:22 -0400

** Changed in: mutter (Ubuntu)
   Status: Fix Committed => Fix Released

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2024-3094

-- 
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/2040977

Title:
  Mouse cursor stutters if nothing else is animating on screen

Status in Mutter:
  New
Status in linux package in Ubuntu:
  Opinion
Status in mutter package in Ubuntu:
  Fix Released

Bug description:
  Using the touchpad on an X1 Carbon G10 with 90Hz OLED the mouse cursor
  stutters, unless something else is changing on screen (like running
  glmark2-wayland).

  Workaround:

  Put this in /etc/environment:

MUTTER_DEBUG_FORCE_KMS_MODE=simple

  and reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: mutter (not installed)
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 26 15:48:28 2023
  InstallationDate: Installed on 2023-10-23 (3 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/2040977/+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 1982935] Re: Selecting "restore defaults" in software-properties-qt has no effect

2024-04-05 Thread ԜаӀtеr Ⅼарсһуnѕkі
This affects everything from Jammy to Noble. No output suggesting it's
related to bug 1795278, though.

** Changed in: software-properties (Ubuntu)
   Status: New => Triaged

** Also affects: software-properties
   Importance: Undecided
   Status: New

-- 
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/1982935

Title:
  Selecting "restore defaults" in software-properties-qt has no effect

Status in Software Properties:
  New
Status in software-properties package in Ubuntu:
  Triaged

Bug description:
  Testing Lubuntu Kinetic daily ISO 26-07-2022

  1. Open "Software Sources" from "Preferences menu
  2. Select "Authentication" 
  3. Delete the keys from "Trusted Service Providers"
  4. Select "Restore Defaults"
  5. After selecting "Restore Defaults" - nothing happens i.e the keys are not 
restored resulting in  the user being unable to perform updates to the system.

  
  This bug is most likely related to bug 11795278 
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1795278

  Attached is a screenshot after removing the keys re: step #3

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: software-properties-qt 0.99.25
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.22.0-0ubuntu4
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: LXQt
  Date: Wed Jul 27 09:19:33 2022
  InstallationDate: Installed on 2022-07-27 (0 days ago)
  InstallationMedia: Lubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220726)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/software-properties/+bug/1982935/+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 2060282] Re: Giflib 5.2.2-1 fails to build

2024-04-05 Thread Nathan Teodosio
** Bug watch added: Debian Bug tracker #1068438
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068438

** Also affects: giflib (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068438
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to giflib in Ubuntu.
https://bugs.launchpad.net/bugs/2060282

Title:
  Giflib 5.2.2-1 fails to build

Status in giflib package in Ubuntu:
  Fix Committed
Status in giflib package in Debian:
  Unknown

Bug description:
  https://launchpadlibrarian.net/721167206/buildlog_ubuntu-noble-
  amd64.giflib_5.2.2-1_BUILDING.txt.gz

  Upstream bug: https://sourceforge.net/p/giflib/bugs/170/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/giflib/+bug/2060282/+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 2059158] Re: proposed-migration for gtk4 4.14.1+ds-0ubuntu1

2024-04-05 Thread Steve Langasek
still tagged 'time-t' because it's in the batch of test regressions
we've allowed as part of the time_t migration

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gtk4 in Ubuntu.
https://bugs.launchpad.net/bugs/2059158

Title:
  proposed-migration for gtk4 4.14.1+ds-0ubuntu1

Status in gtk4 package in Ubuntu:
  New

Bug description:
  gtk4 4.14.1+ds-0ubuntu1 is stuck in -proposed with test regressions on
  armhf.

  1706s # Running test: gtk-4.0/tools/settings.test
  1706s # FAIL: gtk-4.0/tools/settings.test (Child process exited with code 126)
  1706s not ok - gtk-4.0/tools/settings.test

  2100s # Running test: gtk-4.0/tools/simplify.test
  2100s # FAIL: gtk-4.0/tools/simplify.test (Child process exited with code 126)
  2100s not ok - gtk-4.0/tools/simplify.test

  almost certainly time-t related.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk4/+bug/2059158/+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 1900783] Re: [snap] On Groovy, Chromium snap takes much longer to load the first time after reboot

2024-04-05 Thread Nathan Teodosio
This seems not to be an issue any more. Feel free to reset the status if
otherwise.

** Changed in: chromium-browser (Ubuntu)
   Status: Confirmed => Fix Released

-- 
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/1900783

Title:
  [snap] On Groovy, Chromium snap takes much longer to load the first
  time after reboot

Status in chromium-browser package in Ubuntu:
  Fix Released

Bug description:
  I upgraded from Focal to Groovy, and now the first launch of the
  Chromium snap after a reboot is taking much longer than before. On my
  main home laptop it takes over 30 seconds, while under Focal I don't
  remember it taking more than 10 seconds.

  I tried another computer I could erase. On Groovy that computer takes
  nearly a minute to launch the Chromium snap after rebooting. Then I
  clean installed Focal on the same machine, and the Chromium snap takes
  just under 10 seconds to launch after a reboot. For both I installed
  all updates, and I let the computer sit idle for a few minutes after
  rebooting to try to rule out other activity.

  I haven’t noticed the change for any other snap, although I don’t use
  any that I ever noticed as much of a launch delay as Chromium. (VS
  Code for one doesn’t seem slower — certainly not taking nearly a
  minute — but I haven't done a real comparison like for Chromium.)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 20 21:29:20 2020
  InstallationDate: Installed on 2020-04-01 (202 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200331)
  Snap: chromium 87.0.4280.20 (latest/beta)
  SnapSource: ubuntu/+source/chromium-browser
  UpgradeStatus: Upgraded to groovy on 2020-10-17 (3 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1900783/+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 2059861] Re: recovery test not possible

2024-04-05 Thread Michael Terry
Hmm, that's odd. That means... maybe there's a problem decrypting some
of your metadata, but you do have an unencrypted version of that
metadata in duplicity cache folders...?

But if you can restore stuff, that likely means you can decrypt the
latest actual data...

If you run "DEJA_DUP_DEBUG=1 deja-dup" and reproduce the issue, do you
see any interesting output?

** Changed in: deja-dup (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to deja-dup in Ubuntu.
https://bugs.launchpad.net/bugs/2059861

Title:
  recovery test not possible

Status in deja-dup package in Ubuntu:
  Incomplete

Bug description:
  When I'm asked for the password to encrypt, and I type the password and click 
Next, it briefly loads and the Enter password box appears again. 
  However, the password is correct, because I can restore a backup. Only the 
test doesn't work.

  lsb_release -rd
  Description:  Ubuntu 22.04.4 LTS
  Release:  22.04


  apt-cache policy deja-dup
  deja-dup:
Installiert:   42.9-1ubuntu3
Installationskandidat: 42.9-1ubuntu3
Versionstabelle:
   *** 42.9-1ubuntu3 500
  500 http://de.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   42.9-1ubuntu2 500
  500 http://de.archive.ubuntu.com/ubuntu jammy/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: deja-dup 42.9-1ubuntu3
  ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13
  Uname: Linux 6.5.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 31 15:07:23 2024
  InstallationDate: Installed on 2023-06-09 (296 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: deja-dup
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/2059861/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 2059847] Re: Input lag or freezes on Nvidia desktops with X11

2024-04-05 Thread Daniel van Vugt
> To get rid of the terminal slowness, what should I do?

sudo add-apt-repository ppa:vanvugt/mutter
sudo apt update
sudo apt upgrade

and reboot should be enough.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/2059847

Title:
  Input lag or freezes on Nvidia desktops with X11

Status in Mutter:
  New
Status in mutter package in Ubuntu:
  In Progress
Status in mutter source package in Jammy:
  Triaged
Status in mutter source package in Mantic:
  Triaged
Status in mutter source package in Noble:
  In Progress

Bug description:
  [ Impact ]

  Input or the entire screen may freeze at times on systems using the
  Nvidia Xorg driver with GNOME.

  [ Test Plan ]

  0. Set up a desktop with Nvidia driver 545 or 550.
  1. Log into Ubuntu, ensuring it's a Xorg session.
  2. Open a Terminal, resize it vigorously, and type several lines of text.
  3. Verify that input never froze for any perceptible period of time.
  4. Run: journalctl -b0 | grep MetaSyncRing
  5. Verify the above command does NOT show messages such as:

  Window manager warning: MetaSyncRing: Sync object is not ready -- were events 
handled properly?
  Window manager warning: MetaSyncRing: Sync object is not ready -- were events 
handled properly?
  Window manager warning: MetaSyncRing: Sync object is not ready -- were events 
handled properly?
  Window manager warning: MetaSyncRing: Too many reboots -- disabling

  [ Where problems could occur ]

  Anywhere in Nvidia (proprietary driver) Xorg sessions since that's the
  code being modified.

  [ Original Description ]

  There is a noticeable delay in input while using the native terminal.
  I belive it was caused by a recent software update, as this issue is
  relatively new.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13
  Uname: Linux 6.5.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia wl
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 30 19:57:13 2024
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash ---
  InstallationDate: Installed on 2024-03-30 (0 days ago)
  InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240220)
  SourcePackage: ubiquity
  Symptom: installation
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/2059847/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 2060223] Re: Nautilus slowness when expanding/collapsing folders

2024-04-05 Thread Daniel van Vugt
*** This bug is a duplicate of bug 2059847 ***
https://bugs.launchpad.net/bugs/2059847

Sounds like this is probably bug 2059847 so please try the test fix
mentioned there.

** Tags added: jammy nvidia

** This bug has been marked a duplicate of bug 2059847
   Input lag or freezes on Nvidia desktops with X11

-- 
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/2060223

Title:
  Nautilus slowness when expanding/collapsing folders

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  In the recent two days I noticed a slowness in Nautilus while trying
  to expand a folder in the List View.

  When I click on the icon which expands a folder, then it is written
  "Loading..." beneath the folder and after about 3 seconds then the
  list appears.

  Also when trying to "collapse" the expanded folder, then the effect
  happens only after few seconds (takes way too much time).

  Ubuntu version: 22.04.4.
  Using nvidia-driver-535 (proprietary, tested).

  $ nautilus --version
  GNOME nautilus 42.6

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2060223/+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 2060204] Re: Resolution drop on third monitor on USB C

2024-04-05 Thread Daniel van Vugt
Sounds like this could be a side effect of the fix for bug 2051074 that
you just installed. Maybe Kai-Heng Feng will have more insight.


** Tags added: multimonitor

-- 
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/2060204

Title:
  Resolution drop on third monitor on USB C

Status in mutter package in Ubuntu:
  New

Bug description:
  I have a laptop with an integrated intel intel gpu, 2/3 days ago it was 
working fine; I have 1 monitor plugged with hdmi and the other one with USB-c
  Now, the one plugged with USB-C get a lower resolution 1024*768 (not 
changeable) if the HDMI is plugged at the same time (it works well if I only 
have the USB c plugged)
  Feel free to ask if you need information

  cat /var/log/apt/history.log (relevant lines)
  Start-Date: 2024-03-29  14:21:01
  Commandline: apt upgrade -y
  Requested-By: roudonro (1000)
  Upgrade: snapd:amd64 (2.58+22.04.1, 2.61.3+22.04)
  End-Date: 2024-03-29  14:21:15

  Start-Date: 2024-04-02  16:06:48
  Commandline: apt upgrade gnome-calendar
  Requested-By: roudonro (1000)
  Upgrade: coreutils:amd64 (8.32-4.1ubuntu1.1, 8.32-4.1ubuntu1.2), apt:amd64 
(2.4.11, 2.4.12), libapt-pkg6.0:amd64 (2.4.11, 2.4.12), libmutter-10-0:amd64 
(42.9-0ubuntu5, 42.9-0ubuntu7), libwbclient0:amd64 (2:4.15.13+dfsg-0ubuntu1.5, 
2:4.15.13+dfsg-0ubuntu1.6), libsmbclient:amd64 (2:4.15.13+dfsg-0ubuntu1.5, 
2:4.15.13+dfsg-0ubuntu1.6), mutter-common:amd64 (42.9-0ubuntu5, 42.9-0ubuntu7), 
update-notifier:amd64 (3.192.54.6, 3.192.54.8), gir1.2-mutter-10:amd64 
(42.9-0ubuntu5, 42.9-0ubuntu7), samba-libs:amd64 (2:4.15.13+dfsg-0ubuntu1.5, 
2:4.15.13+dfsg-0ubuntu1.6), apt-utils:amd64 (2.4.11, 2.4.12), 
update-notifier-common:amd64 (3.192.54.6, 3.192.54.8)
  End-Date: 2024-04-02  16:06:51

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13
  Uname: Linux 6.5.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  4 09:15:15 2024
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) 
(prog-if 00 [VGA controller])
 Subsystem: Dell TigerLake-LP GT2 [Iris Xe Graphics] [1028:0a21]
  InstallationDate: Installed on 2024-03-27 (7 days ago)
  InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240220)
  MachineType: Dell Inc. Latitude 5520
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-26-generic 
root=UUID=d63caf0d-f785-49dd-94e1-518dc8a874be ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2023
  dmi.bios.release: 1.31
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.31.0
  dmi.board.name: 0DPC2R
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.31.0:bd08/08/2023:br1.31:svnDellInc.:pnLatitude5520:pvr:rvnDellInc.:rn0DPC2R:rvrA00:cvnDellInc.:ct10:cvr:sku0A21:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5520
  dmi.product.sku: 0A21
  dmi.sys.vendor: Dell Inc.
  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 23.0.4-0ubuntu1~22.04.1
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2060204/+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 2060038] Re: splix version 2.0.0+svn315-7fakesync1ubuntu0.22.04.1 in jammy is higher than versions in mantic and noble

2024-04-05 Thread Till Kamppeter
** Changed in: splix (Ubuntu)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to splix in Ubuntu.
https://bugs.launchpad.net/bugs/2060038

Title:
  splix version 2.0.0+svn315-7fakesync1ubuntu0.22.04.1 in jammy is
  higher than versions in mantic and noble

Status in splix package in Ubuntu:
  Fix Released

Bug description:
  This package cannot be upgraded, we're going to need a mantic SRU and
  an ubuntu1 for noble.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/splix/+bug/2060038/+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 2060266] Re: gnome-session no longer supports --builtin

2024-04-05 Thread Haw Loeung
** Description changed:

  Hi,
  
  `gnome-session.service` has the following:
  
  | [Service]
  | ExecStart=/bin/sh -exc '[ "$DESKTOP_SESSION" != "gnome-classic" ] || export 
| GNOME_SHELL_SESSION_MODE=classic; \
  | export GNOME_SESSION_XDG_SESSION_PATH=${XDG_SESSION_PATH}; \
  | [ "$DESKTOP_SESSION" = gnome-flashback-metacity ] && \
  | exec gnome-session --builtin --session=$DESKTOP_SESSION 
--disable-acceleration-check || \
  | exec gnome-session --builtin --session=$DESKTOP_SESSION'
  
  Unfortunately, the latest `gnome-session` no longer supports
  `--builtin`. This causes login failures, in particular for me, using
  Unity, I get logged back out from the unity greeter.
  
  | $ apt-cache policy gnome-session-bin
  | gnome-session-bin:
  |   Installed: 46.0-1ubuntu2
  |   Candidate: 46.0-1ubuntu2
  |   Version table:
  |  *** 46.0-1ubuntu2 500
  | 500 http://haw-test.archive.ubuntu.com/ubuntu noble/main amd64 
Packages
  | 100 /var/lib/dpkg/status
  |  45.0-1ubuntu1 500
  | 500 http://haw-test.archive.ubuntu.com/ubuntu noble-updates/main 
amd64 Packages
  
  | $ gnome-session --builtin
  |
  | ** (gnome-session-binary:5602): WARNING **: 15:35:22.156: Unknown option 
--builtin
  
  Removing `--builtin` from `/usr/lib/systemd/user/gnome-session.service`
  let's me log in.
+ 
+ With that though, I was not able to input text in chromium (installed
+ via the snap).
+ 
+ Downgrading `gnome-session-bin`, `gnome-session-common`, and `unity-
+ session` back to 45.0-1ubuntu1 restores things for me:
+ 
+ | [hloeung@dharkan tmp]$ apt-cache policy gnome-session-bin
+ | gnome-session-bin:
+ |   Installed: 45.0-1ubuntu1
+ |   Candidate: 46.0-1ubuntu2
+ |   Version table:
+ |  46.0-1ubuntu2 500
+ | 500 http://haw-test.archive.ubuntu.com/ubuntu noble/main amd64 
Packages
+ |  *** 45.0-1ubuntu1 500
+ | 500 http://haw-test.archive.ubuntu.com/ubuntu noble-updates/main 
amd64 Packages
+ | 100 /var/lib/dpkg/status
+ | [hloeung@dharkan tmp]$ apt-cache policy gnome-session-common
+ | gnome-session-common:
+ |   Installed: 45.0-1ubuntu1
+ |   Candidate: 46.0-1ubuntu2
+ |   Version table:
+ |  46.0-1ubuntu2 500
+ | 500 http://haw-test.archive.ubuntu.com/ubuntu noble/main amd64 
Packages
+ |  *** 45.0-1ubuntu1 500
+ | 500 http://haw-test.archive.ubuntu.com/ubuntu noble-updates/main 
amd64 Packages
+ | 100 /var/lib/dpkg/status
+ | [hloeung@dharkan tmp]$ apt-cache policy unity-session
+ | unity-session:
+ |   Installed: 45.0-1ubuntu1
+ |   Candidate: 46.0-1ubuntu2
+ |   Version table:
+ |  46.0-1ubuntu2 500
+ | 500 http://haw-test.archive.ubuntu.com/ubuntu noble/universe amd64 
Packages
+ |  *** 45.0-1ubuntu1 500
+ | 500 http://haw-test.archive.ubuntu.com/ubuntu 
noble-updates/universe amd64 Packages
+ | 100 /var/lib/dpkg/status

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/2060266

Title:
  gnome-session no longer supports --builtin

Status in gnome-session package in Ubuntu:
  New

Bug description:
  Hi,

  `gnome-session.service` has the following:

  | [Service]
  | ExecStart=/bin/sh -exc '[ "$DESKTOP_SESSION" != "gnome-classic" ] || export 
| GNOME_SHELL_SESSION_MODE=classic; \
  | export GNOME_SESSION_XDG_SESSION_PATH=${XDG_SESSION_PATH}; \
  | [ "$DESKTOP_SESSION" = gnome-flashback-metacity ] && \
  | exec gnome-session --builtin --session=$DESKTOP_SESSION 
--disable-acceleration-check || \
  | exec gnome-session --builtin --session=$DESKTOP_SESSION'

  Unfortunately, the latest `gnome-session` no longer supports
  `--builtin`. This causes login failures, in particular for me, using
  Unity, I get logged back out from the unity greeter.

  | $ apt-cache policy gnome-session-bin
  | gnome-session-bin:
  |   Installed: 46.0-1ubuntu2
  |   Candidate: 46.0-1ubuntu2
  |   Version table:
  |  *** 46.0-1ubuntu2 500
  | 500 http://haw-test.archive.ubuntu.com/ubuntu noble/main amd64 
Packages
  | 100 /var/lib/dpkg/status
  |  45.0-1ubuntu1 500
  | 500 http://haw-test.archive.ubuntu.com/ubuntu noble-updates/main 
amd64 Packages

  | $ gnome-session --builtin
  |
  | ** (gnome-session-binary:5602): WARNING **: 15:35:22.156: Unknown option 
--builtin

  Removing `--builtin` from `/usr/lib/systemd/user/gnome-
  session.service` let's me log in.

  With that though, I was not able to input text in chromium (installed
  via the snap).

  Downgrading `gnome-session-bin`, `gnome-session-common`, and `unity-
  session` back to 45.0-1ubuntu1 restores things for me:

  | [hloeung@dharkan tmp]$ apt-cache policy gnome-session-bin
  | gnome-session-bin:
  |   Installed: 45.0-1ubuntu1
  |   Candidate: 46.0-1ubuntu2
  |   Version table:
  |  46.0-1ubuntu2 500
  | 500 http://haw-test.archive.ubuntu.com/ubuntu noble/main amd64 
Pack

[Desktop-packages] [Bug 2059335] Re: FFe: Sync file-roller 44-2 (main) from Debian unstable (main)

2024-04-05 Thread fossfreedom
I can confirm the revised file-roller works nicely with nemo + nemo-
fileroller.

Tested compress options, extract here and open in file-roller.

Happy to support this proposal moving forward.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to file-roller in Ubuntu.
https://bugs.launchpad.net/bugs/2059335

Title:
  FFe: Sync file-roller 44-2 (main) from Debian unstable (main)

Status in file-roller package in Ubuntu:
  Incomplete

Bug description:
  Freeze Exception Request
  
  I request to sync file-roller 44 from Debian. The largest change is that 
file-roller was ported from GTK3 to GTK4. However, this is also the strongest 
argument to doing the update: it will be significantly easier to backport 
bugfixes if Ubuntu 24.04 LTS is using the GTK4 version rather than by trying to 
port those fixes to GTK3.

  Although switching apps to GTK4 was problematic for Ubuntu 22.04 LTS,
  a significant number of apps these days are GTK4 and at least all the
  Ubuntu desktop flavors that ship file-roller do have appropriate basic
  themeing for GTK4 apps.

  Potential Problems
  --
  The new release drops the AppMenu option. In other words, showing a 
traditional File/Edit/View menu instead of a hamburger ☰ menu.

  Out of the desktop flavors that ship file-roller, it looks like this
  feature was only used in Ubuntu Unity. Notably Ubuntu Unity ships many
  MATE apps because of Unity's unique "global menu" feature. MATE does
  offer an older GTK3 file-roller fork named engrampa. If this feature
  is important to Ubuntu Unity, I recommend they switch to engrampa.

  However, Ubuntu Unity ships nemo as the default file browser. nemo
  recommends nemo-fileroller which Depends: file-roller. (Instead of
  engrampa). There is another nautilus fork named caja which Ubuntu MATE
  ships.

  Why This Didn't Happen Sooner
  
  file-roller 44 Beta was released March 10 but Feature Freeze was February 29 
so this already missed the Feature Freeze deadline.

  file-roller 44.0 was released last week

  Affected Desktop Flavors
  -
  - Ubuntu Desktop (although only in the "full" install option, but minimal is 
the default for new installs now)
  - Ubuntu Cinnamon
  - Ubuntu Unity

  Upstream changes
  -

  https://gitlab.gnome.org/GNOME/file-roller/-/blob/44/NEWS

  https://gitlab.gnome.org/GNOME/file-roller/-/compare/43.1...44

  Changelog entries since current noble version 43.1-1build2:
  -

  file-roller (44-2) unstable; urgency=medium

* Cherry-pick 5 patches to fix various issues

   -- Jeremy Bícha   Tue, 02 Apr 2024 14:45:40 -0400

  file-roller (44-1) unstable; urgency=medium

    * New upstream release (LP: #2059335)
    * Drop patch applied in new release
    * Depend on 7zip instead of p7zip on Debian (Closes: #1042447)

   -- Jeremy Bícha   Wed, 27 Mar 2024 17:38:22 -0400

  file-roller (44~beta-1) unstable; urgency=medium

    * New upstream release
    * debian/control: Bump minimum required libglib2.0-dev to 2.38.0
    * debian/control: Update to build with GTK 4, following upstream
    * debian/patches/ftbfs-gdkscreen.patch: Add patch to drop call to
  deprecated and removed GdkScreen-related method causing FTBFS
  with -Werror=implicit-function-declaration
    * debian/copyright: Drop superfluous 'Files: src/egg*' pattern (and
  accompanying license text) for unused files that were previously
  dropped upstream

   -- Amin Bandali   Thu, 21 Mar 2024 15:49:58 -0400

  Build log
  --
  
https://launchpad.net/~ubuntu-desktop/+archive/ubuntu/ubuntu-desktop-gnome/+packages

  Testing Done
  
  I have verified that file-roller 44 does work on Ubuntu Desktop, Ubuntu 
Budgie, Ubuntu Cinnamon, and Ubuntu Unity

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/2059335/+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 2060273] [NEW] secondary users are not listed in polkit graphical prompt

2024-04-05 Thread Didier Roche-Tolomelli
Public bug reported:

Tested with 124-1ubuntu1 on noble

1. Create 3 users on the machine:
- sudo-user1, part of sudo group
- sudo-user2, part of sudo group
- normal-user, not part of the sudo group
2. Login with normal-user
3. Try to execute pkexec or any other command prompting for polkit
-> only sudo-user1 password auth is proposed, before, we had a listbox to 
select all eligible user
4. Remove sudo-user1
5. Try pkexec again:
-> now sudo-user2 is proposed, showing that the configuration for this user is 
correct.

It seems that only the first "admin" of the machine is taken into
account. However, as normal-user, I may not have sudo-user1 around, but
only sudo-user2.

** Affects: policykit-1 (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to policykit-1 in Ubuntu.
https://bugs.launchpad.net/bugs/2060273

Title:
  secondary users are not listed in polkit graphical prompt

Status in policykit-1 package in Ubuntu:
  New

Bug description:
  Tested with 124-1ubuntu1 on noble

  1. Create 3 users on the machine:
  - sudo-user1, part of sudo group
  - sudo-user2, part of sudo group
  - normal-user, not part of the sudo group
  2. Login with normal-user
  3. Try to execute pkexec or any other command prompting for polkit
  -> only sudo-user1 password auth is proposed, before, we had a listbox to 
select all eligible user
  4. Remove sudo-user1
  5. Try pkexec again:
  -> now sudo-user2 is proposed, showing that the configuration for this user 
is correct.

  It seems that only the first "admin" of the machine is taken into
  account. However, as normal-user, I may not have sudo-user1 around,
  but only sudo-user2.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/2060273/+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 2043820] Re: Unable to contact snap store on Xubuntu from Jammy to Noble

2024-04-05 Thread Tim Andersson
Tried this again today, still an issue, see files attached

** Attachment added: "dist-upgrade.tar"
   
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/2043820/+attachment/5761639/+files/dist-upgrade.tar

-- 
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/2043820

Title:
  Unable to contact snap store on Xubuntu from Jammy to Noble

Status in firefox package in Ubuntu:
  Confirmed
Status in snapd package in Ubuntu:
  Confirmed
Status in firefox source package in Noble:
  Confirmed
Status in snapd source package in Noble:
  Confirmed

Bug description:
  When running `do-release-upgrade -d` on Jammy Xubuntu, the upgrade
  fails consistently at the `Installing the firefox snap` step.

  This was first detected on Jenkins [1], then reproduced locally with
  `auto-upgrade-testing`, then finally by manually running a `do-
  release-upgrade -d` in a VM.

  [1]: https://platform-qa-jenkins.ps5.ubuntu.com/view/upgrade-
  list/job/upgrade_ubuntu-jammy-noble-xubuntu-amd64_qemu/7/consoleFull
  (Jenkins full log attached)

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntu-release-upgrader-core 1:22.04.17
  ProcVersionSignature: User Name 5.15.0-88.98-generic 5.15.126
  Uname: Linux 5.15.0-88-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: XFCE
  Date: Fri Nov 17 18:24:22 2023
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2043820/+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 2060223] [NEW] Nautilus slowness when expanding/collapsing folders

2024-04-05 Thread niix
Public bug reported:

In the recent two days I noticed a slowness in Nautilus while trying to
expand a folder in the List View.

When I click on the icon which expands a folder, then it is written
"Loading..." beneath the folder and after about 3 seconds then the list
appears.

Also when trying to "collapse" the expanded folder, then the effect
happens only after few seconds (takes way too much time).

Ubuntu version: 22.04.4.
Using nvidia-driver-535 (proprietary, tested).

$ nautilus --version
GNOME nautilus 42.6

** 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/2060223

Title:
  Nautilus slowness when expanding/collapsing folders

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  In the recent two days I noticed a slowness in Nautilus while trying
  to expand a folder in the List View.

  When I click on the icon which expands a folder, then it is written
  "Loading..." beneath the folder and after about 3 seconds then the
  list appears.

  Also when trying to "collapse" the expanded folder, then the effect
  happens only after few seconds (takes way too much time).

  Ubuntu version: 22.04.4.
  Using nvidia-driver-535 (proprietary, tested).

  $ nautilus --version
  GNOME nautilus 42.6

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2060223/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 2059847] Re: Input lag or freezes on Nvidia desktops with X11

2024-04-05 Thread Daniel van Vugt
> Should we remove the ppa after the official packages are released?

When a higher official version number is available from the archive,
your system should automatically start using that. So this particular
PPA is harmless to keep active but that's not true for all PPAs.

You should still remove the PPA when you no longer need it because it
will raise some annoying flags from bots if you try to report new Ubuntu
bugs while using a PPA.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/2059847

Title:
  Input lag or freezes on Nvidia desktops with X11

Status in Mutter:
  New
Status in mutter package in Ubuntu:
  In Progress
Status in mutter source package in Jammy:
  Triaged
Status in mutter source package in Mantic:
  Triaged
Status in mutter source package in Noble:
  In Progress

Bug description:
  [ Impact ]

  Input or the entire screen may freeze at times on systems using the
  Nvidia Xorg driver with GNOME.

  [ Test Plan ]

  0. Set up a desktop with Nvidia driver 545 or 550.
  1. Log into Ubuntu, ensuring it's a Xorg session.
  2. Open a Terminal, resize it vigorously, and type several lines of text.
  3. Verify that input never froze for any perceptible period of time.
  4. Run: journalctl -b0 | grep MetaSyncRing
  5. Verify the above command does NOT show messages such as:

  Window manager warning: MetaSyncRing: Sync object is not ready -- were events 
handled properly?
  Window manager warning: MetaSyncRing: Sync object is not ready -- were events 
handled properly?
  Window manager warning: MetaSyncRing: Sync object is not ready -- were events 
handled properly?
  Window manager warning: MetaSyncRing: Too many reboots -- disabling

  [ Where problems could occur ]

  Anywhere in Nvidia (proprietary driver) Xorg sessions since that's the
  code being modified.

  [ Original Description ]

  There is a noticeable delay in input while using the native terminal.
  I belive it was caused by a recent software update, as this issue is
  relatively new.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13
  Uname: Linux 6.5.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia wl
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 30 19:57:13 2024
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash ---
  InstallationDate: Installed on 2024-03-30 (0 days ago)
  InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240220)
  SourcePackage: ubiquity
  Symptom: installation
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/2059847/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 2060206] [NEW] No Sound on my Samsung NP950QED Laptop Speakers

2024-04-05 Thread Thierry Marchisio
Public bug reported:

Hello,

Yesterday I have installed Ubuntu 23.10 on my laptop Samsung Galaxy Book2 Pro 
NP950QED for the first time.
I never heard any sound from my laptop since the installation of Ubuntu. It 
worked with Microsoft Windows.

I spent the whole day on many forums, alsa-project.org... Nothing worked yet.
Every time I try a new configuration, I test both left and right speakers in 
the Settings application.

You can find my Ubuntu Alsa configuration in the file attached generared
by alsa-info.sh

Thank you for your help !

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: alsa-base 1.0.25+dfsg-0ubuntu7
ProcVersionSignature: Ubuntu 6.5.0-26.26-generic 6.5.13
Uname: Linux 6.5.0-26-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  thierry2651 F pipewire
  thierry2657 F wireplumber
 /dev/snd/seq:thierry2651 F pipewire
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr  4 16:24:59 2024
InstallationDate: Installed on 2024-04-03 (1 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1)
PackageArchitecture: all
ProcEnviron:
 LANG=fr_FR.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
SourcePackage: alsa-driver
Symptom: audio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/03/2023
dmi.bios.release: 5.25
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: P10AKK.730.230203.SH
dmi.board.asset.tag: No Asset Tag
dmi.board.name: NP950QED-KA1FR
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: SGLB182A1Z-C01-G002-S0002+10.0.22000
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 31
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP10AKK.730.230203.SH:bd02/03/2023:br5.25:svnSAMSUNGELECTRONICSCO.,LTD.:pn950QED:pvrP10AKK:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP950QED-KA1FR:rvrSGLB182A1Z-C01-G002-S0002+10.0.22000:cvnSAMSUNGELECTRONICSCO.,LTD.:ct31:cvrN/A:skuSCAI-ICPS-A5A5-ADLP-PAKK:
dmi.product.family: Galaxy Book2 Pro 360
dmi.product.name: 950QED
dmi.product.sku: SCAI-ICPS-A5A5-ADLP-PAKK
dmi.product.version: P10AKK
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug mantic wayland-session

** Attachment added: "alsa-info.sh Generated File"
   
https://bugs.launchpad.net/bugs/2060206/+attachment/5761575/+files/alsa-info.txt.blWk58tjXY

-- 
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/2060206

Title:
  No Sound on my Samsung NP950QED Laptop Speakers

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Hello,

  Yesterday I have installed Ubuntu 23.10 on my laptop Samsung Galaxy Book2 Pro 
NP950QED for the first time.
  I never heard any sound from my laptop since the installation of Ubuntu. It 
worked with Microsoft Windows.

  I spent the whole day on many forums, alsa-project.org... Nothing worked yet.
  Every time I try a new configuration, I test both left and right speakers in 
the Settings application.

  You can find my Ubuntu Alsa configuration in the file attached
  generared by alsa-info.sh

  Thank you for your help !

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 6.5.0-26.26-generic 6.5.13
  Uname: Linux 6.5.0-26-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  thierry2651 F pipewire
thierry2657 F wireplumber
   /dev/snd/seq:thierry2651 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  4 16:24:59 2024
  InstallationDate: Installed on 2024-04-03 (1 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  PackageArchitecture: all
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: alsa-driver
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/03/2023
  dmi.bios.release: 5.25
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: P10AKK.730.230203.SH
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP950QED-KA1FR
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGLB182A1Z

[Desktop-packages] [Bug 2059847] Re: Input lag or freezes on Nvidia desktops with X11

2024-04-05 Thread Tais P. Hansen
I can confirm the lag is gone on my 23.10 system using X11 with nvidia-
driver-550 when using the PPA packages.

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/2059847

Title:
  Input lag or freezes on Nvidia desktops with X11

Status in Mutter:
  New
Status in mutter package in Ubuntu:
  In Progress
Status in mutter source package in Jammy:
  Triaged
Status in mutter source package in Mantic:
  Triaged
Status in mutter source package in Noble:
  In Progress

Bug description:
  [ Impact ]

  Input or the entire screen may freeze at times on systems using the
  Nvidia Xorg driver with GNOME.

  [ Test Plan ]

  0. Set up a desktop with Nvidia driver 545 or 550.
  1. Log into Ubuntu, ensuring it's a Xorg session.
  2. Open a Terminal, resize it vigorously, and type several lines of text.
  3. Verify that input never froze for any perceptible period of time.
  4. Run: journalctl -b0 | grep MetaSyncRing
  5. Verify the above command does NOT show messages such as:

  Window manager warning: MetaSyncRing: Sync object is not ready -- were events 
handled properly?
  Window manager warning: MetaSyncRing: Sync object is not ready -- were events 
handled properly?
  Window manager warning: MetaSyncRing: Sync object is not ready -- were events 
handled properly?
  Window manager warning: MetaSyncRing: Too many reboots -- disabling

  [ Where problems could occur ]

  Anywhere in Nvidia (proprietary driver) Xorg sessions since that's the
  code being modified.

  [ Original Description ]

  There is a noticeable delay in input while using the native terminal.
  I belive it was caused by a recent software update, as this issue is
  relatively new.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13
  Uname: Linux 6.5.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia wl
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 30 19:57:13 2024
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash ---
  InstallationDate: Installed on 2024-03-30 (0 days ago)
  InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240220)
  SourcePackage: ubiquity
  Symptom: installation
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/2059847/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 2059847] Re: Input lag or freezes on Nvidia desktops with X11

2024-04-05 Thread Filip M
Should we remove the ppa after the official packages are released?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/2059847

Title:
  Input lag or freezes on Nvidia desktops with X11

Status in Mutter:
  New
Status in mutter package in Ubuntu:
  In Progress
Status in mutter source package in Jammy:
  Triaged
Status in mutter source package in Mantic:
  Triaged
Status in mutter source package in Noble:
  In Progress

Bug description:
  [ Impact ]

  Input or the entire screen may freeze at times on systems using the
  Nvidia Xorg driver with GNOME.

  [ Test Plan ]

  0. Set up a desktop with Nvidia driver 545 or 550.
  1. Log into Ubuntu, ensuring it's a Xorg session.
  2. Open a Terminal, resize it vigorously, and type several lines of text.
  3. Verify that input never froze for any perceptible period of time.
  4. Run: journalctl -b0 | grep MetaSyncRing
  5. Verify the above command does NOT show messages such as:

  Window manager warning: MetaSyncRing: Sync object is not ready -- were events 
handled properly?
  Window manager warning: MetaSyncRing: Sync object is not ready -- were events 
handled properly?
  Window manager warning: MetaSyncRing: Sync object is not ready -- were events 
handled properly?
  Window manager warning: MetaSyncRing: Too many reboots -- disabling

  [ Where problems could occur ]

  Anywhere in Nvidia (proprietary driver) Xorg sessions since that's the
  code being modified.

  [ Original Description ]

  There is a noticeable delay in input while using the native terminal.
  I belive it was caused by a recent software update, as this issue is
  relatively new.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13
  Uname: Linux 6.5.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia wl
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 30 19:57:13 2024
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash ---
  InstallationDate: Installed on 2024-03-30 (0 days ago)
  InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240220)
  SourcePackage: ubiquity
  Symptom: installation
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/2059847/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 2060204] Re: Resolution drop on third monitor on USB C

2024-04-05 Thread Ubuntu Foundations Team Bug Bot
** Package changed: ubuntu => xorg (Ubuntu)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2060204

Title:
  Resolution drop on third monitor on USB C

Status in xorg package in Ubuntu:
  New

Bug description:
  I have a laptop with an integrated intel intel gpu, 2/3 days ago it was 
working fine; I have 1 monitor plugged with hdmi and the other one with USB-c
  Now, the one plugged with USB-C get a lower resolution 1024*768 (not 
changeable) if the HDMI is plugged at the same time (it works well if I only 
have the USB c plugged)
  Feel free to ask if you need information

  cat /var/log/apt/history.log (relevant lines)
  Start-Date: 2024-03-29  14:21:01
  Commandline: apt upgrade -y
  Requested-By: roudonro (1000)
  Upgrade: snapd:amd64 (2.58+22.04.1, 2.61.3+22.04)
  End-Date: 2024-03-29  14:21:15

  Start-Date: 2024-04-02  16:06:48
  Commandline: apt upgrade gnome-calendar
  Requested-By: roudonro (1000)
  Upgrade: coreutils:amd64 (8.32-4.1ubuntu1.1, 8.32-4.1ubuntu1.2), apt:amd64 
(2.4.11, 2.4.12), libapt-pkg6.0:amd64 (2.4.11, 2.4.12), libmutter-10-0:amd64 
(42.9-0ubuntu5, 42.9-0ubuntu7), libwbclient0:amd64 (2:4.15.13+dfsg-0ubuntu1.5, 
2:4.15.13+dfsg-0ubuntu1.6), libsmbclient:amd64 (2:4.15.13+dfsg-0ubuntu1.5, 
2:4.15.13+dfsg-0ubuntu1.6), mutter-common:amd64 (42.9-0ubuntu5, 42.9-0ubuntu7), 
update-notifier:amd64 (3.192.54.6, 3.192.54.8), gir1.2-mutter-10:amd64 
(42.9-0ubuntu5, 42.9-0ubuntu7), samba-libs:amd64 (2:4.15.13+dfsg-0ubuntu1.5, 
2:4.15.13+dfsg-0ubuntu1.6), apt-utils:amd64 (2.4.11, 2.4.12), 
update-notifier-common:amd64 (3.192.54.6, 3.192.54.8)
  End-Date: 2024-04-02  16:06:51

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13
  Uname: Linux 6.5.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  4 09:15:15 2024
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) 
(prog-if 00 [VGA controller])
 Subsystem: Dell TigerLake-LP GT2 [Iris Xe Graphics] [1028:0a21]
  InstallationDate: Installed on 2024-03-27 (7 days ago)
  InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240220)
  MachineType: Dell Inc. Latitude 5520
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-26-generic 
root=UUID=d63caf0d-f785-49dd-94e1-518dc8a874be ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2023
  dmi.bios.release: 1.31
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.31.0
  dmi.board.name: 0DPC2R
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.31.0:bd08/08/2023:br1.31:svnDellInc.:pnLatitude5520:pvr:rvnDellInc.:rn0DPC2R:rvrA00:cvnDellInc.:ct10:cvr:sku0A21:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5520
  dmi.product.sku: 0A21
  dmi.sys.vendor: Dell Inc.
  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 23.0.4-0ubuntu1~22.04.1
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2060204/+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 2058840] Re: Chromium Snap & KDE Plasma 6: AppArmor Profile Update Needed

2024-04-05 Thread Nathan Teodosio
** Changed in: chromium-browser (Ubuntu)
   Status: Triaged => Fix Committed

-- 
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/2058840

Title:
  Chromium Snap & KDE Plasma 6: AppArmor Profile Update Needed

Status in chromium-browser package in Ubuntu:
  Fix Committed

Bug description:
  Ubuntu 22.04 LTS Jammy x64


  I hope this is the correct package to assign this request to:

  In KDE Plasma 6, the Chromium snap cannot longer access KDE Wallet to
  decrypt its password store.

  This makes all stored passwords unavailable as soon as the system is
  upgraded from Plasma 5 to Plasma 6.

  Chromium writes the following error messages to the console:

  -
  [5362:5362:0324/103716.837413:ERROR:object_proxy.cc(576)] Failed to call 
method: org.kde.KWallet.isEnabled: object_path= /modules/kwalletd6: 
org.freedesktop.DBus.Error.AccessDenied: An AppArmor policy prevents this 
sender from sending this message to this recipient; type="method_call", 
sender=":1.113" (uid=1000 pid=5362 
comm="/snap/chromium/2786/usr/lib/chromium-browser/chrom" 
label="snap.chromium.chromium (enforce)") interface="org.kde.KWallet" 
member="isEnabled" error name="(unset)" requested_reply="0" 
destination="org.kde.kwalletd6" (uid=1000 pid=2523 comm="/usr/bin/kwalletd6 
--pam-login 13 14 " label="unconfined")
  [5362:5362:0324/103716.837451:ERROR:kwallet_dbus.cc(112)] Error contacting 
kwalletd6 (isEnabled)
  [5362:5362:0324/103716.838022:ERROR:object_proxy.cc(576)] Failed to call 
method: org.kde.KLauncher.start_service_by_desktop_name: object_path= 
/KLauncher: org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.kde.klauncher was not provided by any .service files
  [5362:5362:0324/103716.838042:ERROR:kwallet_dbus.cc(81)] Error contacting 
klauncher to start kwalletd6
  [5362:5362:0324/103716.838264:ERROR:object_proxy.cc(576)] Failed to call 
method: org.kde.KWallet.close: object_path= /modules/kwalletd6: 
org.freedesktop.DBus.Error.AccessDenied: An AppArmor policy prevents this 
sender from sending this message to this recipient; type="method_call", 
sender=":1.113" (uid=1000 pid=5362 
comm="/snap/chromium/2786/usr/lib/chromium-browser/chrom" 
label="snap.chromium.chromium (enforce)") interface="org.kde.KWallet" 
member="close" error name="(unset)" requested_reply="0" 
destination="org.kde.kwalletd6" (uid=1000 pid=2523 comm="/usr/bin/kwalletd6 
--pam-login 13 14 " label="unconfined")
  [5362:5362:0324/103716.838295:ERROR:kwallet_dbus.cc(503)] Error contacting 
kwalletd6 (close)
  -

  Followed by hundreds of messages as the following:

  -
  ERROR:login_database.cc(1046) Password decryption failed, encryption_result 
is 2
  -

  It appears to work to "just" whitelist the new kwalletd module name in

  /var/lib/snapd/apparmor/profiles/snap.chromium.chromium (and maybe
  /var/lib/snapd/apparmor/profiles/snap.chromium.chromedriver ?)

  followed by

  $ systemctl restart apparmor
  $ systemctl restart snapd.apparmor
  $ systemctl restart apparmor

  (Not sure if both of these are necessary, and if so, in what order.)

  and completely restart Chromium.

  The new KWallet section looks as follows - I only added the ",6" to
  the patterns:

  -

  # KWallet's client API is still in use in KDE/Plasma. It's DBus API relies 
upon
  # member data for access to its 'folders' and 'entries' and it therefore does
  # not allow for application isolation via AppArmor. For details, see:
  # - https://cgit.kde.org/kdelibs.git/tree/kdeui/util/kwallet.h?h=v4.14.33
  #
  dbus (receive, send)
  bus=session
  path=/modules/kwalletd{,5,6}
  interface=org.freedesktop.DBus.*
  peer=(label=unconfined),

  dbus (receive, send)
  bus=session
  path=/modules/kwalletd{,5,6}
  interface=org.kde.KWallet
  peer=(label=unconfined),

  -

  I hope that at least this report may be found by other people running
  into the same trouble I just did...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2058840/+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