[Desktop-packages] [Bug 1990341] Re: [SRU] Support to install nvidia driver by allowing list

[Chris Halse Rogers]

OOoooh, right. This is releasable, and has a sensible changelog, it's
just that LP isn't showing the full changes file.

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

Title:
  [SRU] Support to install nvidia driver by allowing list

Status in OEM Priority Project:
  Triaged
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common source package in Jammy:
  Fix Released
Status in ubuntu-drivers-common source package in Lunar:
  Fix Released

Bug description:
  [ Impact ]

   * In NVIDIA new GPU release cycle, NVIDIA ships their new GPUs to
  OEM/ODM for production.

  In the meantime, NVIDIA usually notify OEM/ODM/Canonical (under NDA)
  to use a specific nvidia version to development/production.

  NVIDIA and OEN/ODM will announce the next generation combination at
  the same time usually when the factory ready to ship the product.

  We made Ubuntu as a leading distribution supports many cutting edge
  devices, it's time to have an official way to make the nvidia
  installation consistent in unannounced (yet) nvidia devices to support
  OEM/ODM factory shipment for our growing counterparts.

  [ Test Plan ]

   * Steps to make sure it works:

  1. pick a cutting edge nvidia graphic.
  2. remove nv-525 from the pool by removing restricted in jammy-updates and 
jammy-security
  3. check the nv support status:
  ```
  $ ubuntu-drivers list
  oem-fix-gfx-nvidia-ondemandmode
  libfprint-2-tod1-broadcom
  oem-somerville-cinccino-meta
  ```
  4. modify custom file
  ```
  $ cat /etc/custom_supported_gpus.json
  {
    "chips": [
  {
    "devid": "0x24BA",
    "name": "TEST 24BA",
    "branch": "580.1234",
    "features": [
  "runtimepm"
    ]
  },
  {
    "devid": "0x25BC",
    "name": "TEST 25BC",
    "branch": "510",
    "features": [
  "runtimepm"
    ]
  }
    ]
  }
  ```
  5. make sure the hook works
  ```
  $ ubuntu-drivers list
  nvidia-driver-510, (kernel modules provided by nvidia-dkms-510)
  oem-fix-gfx-nvidia-ondemandmode
  libfprint-2-tod1-broadcom
  oem-somerville-cinccino-meta

  [ Where problems could occur ]

   * This feature only impact target system has a custom file
  "/etc/custom_supported_gpus.json". And it won't generate automatically
  which should not impact normal users

  [ Other Info ]

   * the patches are picked from
     - 
https://github.com/tseliot/ubuntu-drivers-common/commit/ec675fba22c68932da9fae95e0f4f2fd10732bf3
     - 
https://github.com/tseliot/ubuntu-drivers-common/commit/4776c6b9f78411ef3b269a28e9546e4ffd2b7115
     - 
https://github.com/tseliot/ubuntu-drivers-common/commit/83528313da84b55c04daa62b5edcbf823e5c067b.
   * Discussion is in https://github.com/tseliot/ubuntu-drivers-common/pull/71

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1990341/+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 1990341] Re: [SRU] Support to install nvidia driver by allowing list

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-drivers-common -
1:0.9.6.2~0.22.04.6

---
ubuntu-drivers-common (1:0.9.6.2~0.22.04.6) jammy; urgency=medium

  * UbuntuDrivers/detect.py:
- Skip modalias checking if id in force install list

 -- Dirk Su   Fri, 15 Sep 2023 16:59:17 +0800

** Changed in: ubuntu-drivers-common (Ubuntu Jammy)
   Status: Confirmed => Fix Released

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

Title:
  [SRU] Support to install nvidia driver by allowing list

Status in OEM Priority Project:
  Triaged
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common source package in Jammy:
  Fix Released
Status in ubuntu-drivers-common source package in Lunar:
  Fix Released

Bug description:
  [ Impact ]

   * In NVIDIA new GPU release cycle, NVIDIA ships their new GPUs to
  OEM/ODM for production.

  In the meantime, NVIDIA usually notify OEM/ODM/Canonical (under NDA)
  to use a specific nvidia version to development/production.

  NVIDIA and OEN/ODM will announce the next generation combination at
  the same time usually when the factory ready to ship the product.

  We made Ubuntu as a leading distribution supports many cutting edge
  devices, it's time to have an official way to make the nvidia
  installation consistent in unannounced (yet) nvidia devices to support
  OEM/ODM factory shipment for our growing counterparts.

  [ Test Plan ]

   * Steps to make sure it works:

  1. pick a cutting edge nvidia graphic.
  2. remove nv-525 from the pool by removing restricted in jammy-updates and 
jammy-security
  3. check the nv support status:
  ```
  $ ubuntu-drivers list
  oem-fix-gfx-nvidia-ondemandmode
  libfprint-2-tod1-broadcom
  oem-somerville-cinccino-meta
  ```
  4. modify custom file
  ```
  $ cat /etc/custom_supported_gpus.json
  {
    "chips": [
  {
    "devid": "0x24BA",
    "name": "TEST 24BA",
    "branch": "580.1234",
    "features": [
  "runtimepm"
    ]
  },
  {
    "devid": "0x25BC",
    "name": "TEST 25BC",
    "branch": "510",
    "features": [
  "runtimepm"
    ]
  }
    ]
  }
  ```
  5. make sure the hook works
  ```
  $ ubuntu-drivers list
  nvidia-driver-510, (kernel modules provided by nvidia-dkms-510)
  oem-fix-gfx-nvidia-ondemandmode
  libfprint-2-tod1-broadcom
  oem-somerville-cinccino-meta

  [ Where problems could occur ]

   * This feature only impact target system has a custom file
  "/etc/custom_supported_gpus.json". And it won't generate automatically
  which should not impact normal users

  [ Other Info ]

   * the patches are picked from
     - 
https://github.com/tseliot/ubuntu-drivers-common/commit/ec675fba22c68932da9fae95e0f4f2fd10732bf3
     - 
https://github.com/tseliot/ubuntu-drivers-common/commit/4776c6b9f78411ef3b269a28e9546e4ffd2b7115
     - 
https://github.com/tseliot/ubuntu-drivers-common/commit/83528313da84b55c04daa62b5edcbf823e5c067b.
   * Discussion is in https://github.com/tseliot/ubuntu-drivers-common/pull/71

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1990341/+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 2043538] [NEW] gnome-shell takes too much ram

[Vincent Jaubert]

Public bug reported:

I had no memory problems with Ubuntu 20.04.
After upgrading to Ubuntu 22.04, my 16GB laptop suffered from lack of memory.
I upgraded to 48GB (!), and the memory still continues to fill.
After a few days, with no program started, 12GB is taken. Gnome-shell alone is 
taking 17.4% of my 48GB.
I guess it is suffering from a memory leak. 

Description:Ubuntu 22.04.3 LTS

gnome-shell:
  Installé : 42.9-0ubuntu2
  Candidat : 42.9-0ubuntu2
 Table de version :
 *** 42.9-0ubuntu2 500
500 http://fr.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 42.0-2ubuntu1 500
500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42.9-0ubuntu2
ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16
Uname: Linux 6.2.0-36-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Nov 15 07:04:21 2023
DisplayManager: gdm3
InstallationDate: Installed on 2023-08-31 (75 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: mutter-common 42.9-0ubuntu5
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  gnome-shell takes too much ram

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I had no memory problems with Ubuntu 20.04.
  After upgrading to Ubuntu 22.04, my 16GB laptop suffered from lack of memory.
  I upgraded to 48GB (!), and the memory still continues to fill.
  After a few days, with no program started, 12GB is taken. Gnome-shell alone 
is taking 17.4% of my 48GB.
  I guess it is suffering from a memory leak. 

  Description:Ubuntu 22.04.3 LTS

  gnome-shell:
Installé : 42.9-0ubuntu2
Candidat : 42.9-0ubuntu2
   Table de version :
   *** 42.9-0ubuntu2 500
  500 http://fr.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   42.0-2ubuntu1 500
  500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.9-0ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-36-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 15 07:04:21 2023
  DisplayManager: gdm3
  InstallationDate: Installed on 2023-08-31 (75 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 42.9-0ubuntu5
  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/2043538/+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 2043529] [NEW] HDMI port issues after ubuntu 23 upgrade

[Michael Forehnd]

Public bug reported:

Hdmi port will not recognize external display after lunar lobster
install. This issue was verified by upgrading my desktop to lunar
lobster that had 22.10 previously installed. The desktop has 3 monitors
working before the upgrade. After the upgrade only one monitor will
work. I have attempted to trouble shoot the issue but am leaning towards
a bug at this point. The thunderbolt works for displaying however I am
unable to get the hdmi to recognize any connection. The port is working
and was verified by windows that is dual booted on this laptop.

ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.2.0-27.28-generic 6.2.15
Uname: Linux 6.2.0-27-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  545.29.02  Thu Oct 26 21:21:38 
UTC 2023
 GCC version:  gcc version 12.3.0 (Ubuntu 12.3.0-1ubuntu1~23.04)
ApportVersion: 2.26.1-0ubuntu2.1
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Nov 14 18:29:03 2023
DistUpgraded: Fresh install
DistroCodename: lunar
DistroVariant: ubuntu
DkmsStatus:
 evdi/1.14.1, 6.2.0-27-generic, x86_64: installed
 nvidia/545.29.02, 6.2.0-27-generic, x86_64: installed
 rtl8812AU/#MODULE_VERSION#: added
 virtualbox/7.0.6, 6.2.0-27-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (prog-if 00 
[VGA controller])
   Subsystem: Dell CoffeeLake-H GT2 [UHD Graphics 630] [1028:087d]
   Subsystem: Dell GP107GLM [Quadro P2000 Mobile] [1028:087d]
InstallationDate: Installed on 2023-02-21 (266 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 27c6:5395 Shenzhen Goodix Technology Co.,Ltd. 
Fingerprint Reader
 Bus 001 Device 002: ID 8087:0025 Intel Corp. Wireless-AC 9260 Bluetooth Adapter
 Bus 001 Device 004: ID 0c45:671d Microdia Integrated_Webcam_HD
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Precision 5530
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/usr/bin/zsh
 XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-27-generic 
root=UUID=47692d38-dda2-45e4-b8f9-eb478775c1fe ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/13/2023
dmi.bios.release: 1.31
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.31.0
dmi.board.name: 0CDJF9
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.31.0:bd03/13/2023:br1.31:svnDellInc.:pnPrecision5530:pvr:rvnDellInc.:rn0CDJF9:rvrA01:cvnDellInc.:ct10:cvr:sku087D:
dmi.product.family: Precision
dmi.product.name: Precision 5530
dmi.product.sku: 087D
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.114-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~23.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~23.04.1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3.1
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

** Affects: xorg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug lunar ubuntu wayland-session

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

Title:
  HDMI port issues after ubuntu 23 upgrade

Status in xorg package in Ubuntu:
  New

Bug description:
  Hdmi port will not recognize external display after lunar lobster
  install. This issue was verified by upgrading my desktop to lunar
  lobster that had 22.10 previously installed. The desktop has 3
  monitors working before the upgrade. After the upgrade only one
  monitor will work. I have attempted to trouble shoot the issue but am
  leaning towards a bug at this point. The thunderbolt works for
  displaying however I am unable to get the hdmi to recognize any
  connection. 

[Desktop-packages] [Bug 2011806] Re: [lunar] Snaps don't launch due to cgroup issue

[Jonas Gamao]

Operating System: Kubuntu 23.10
KDE Plasma Version: 5.27.9
KDE Frameworks Version: 5.112.0
Qt Version: 5.15.10
Kernel Version: 6.5.0-10-generic (64-bit)
Graphics Platform: X11
Processors: 24 × AMD Ryzen 9 5900X 12-Core Processor
Memory: 62.7 GiB of RAM
Graphics Processor: AMD Radeon RX 6900 XT
Manufacturer: Gigabyte Technology Co., Ltd.
Product Name: X570S AORUS MASTER
System Version: -CF

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

Title:
  [lunar] Snaps don't launch due to cgroup issue

Status in GNOME Shell:
  New
Status in KDE Base:
  New
Status in gnome-desktop package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in kio package in Ubuntu:
  Confirmed
Status in snapd package in Ubuntu:
  Opinion

Bug description:
  Hi,

  Lunar up to date, Intel+Nvidia GPUs, Ubuntu Wayland or X11 session,
  hybrid or discrete graphics.

  If I click on a snap dash icon, nothing happens.
  Tested with Thunderbird, Firefox, Shortwave...
  (VS Code seems ok, maybe due to classic confinment?)

  I can launch without issue Chrome (deb), Synaptic, GNOME apps, etc.

  Recent updates included gnome-shell and libadwaita.

  ---

  I get this type of log for all problematic snaps:

  /user.slice/user-1000.slice/user@1000.service/app.slice/app-gnome-
  shortwave_shortwave-11885.scope is not a snap cgroup

  ---

  Context:

  $ snap --version
  snap2.58.3+23.04ubuntu1
  snapd   2.58.3+23.04ubuntu1
  series  16
  ubuntu  23.04
  kernel  6.1.0-16-generic

  $ snap list
  Nom   Version Révision  
Suivi Éditeur   Notes
  bare  1.0 5 
latest/stable canonical✓base
  code  ee2b180d122   
latest/stable vscode✓   classic
  core  16-2.58.2   14784 
latest/stable canonical✓core
  core18202303082714  
latest/stable canonical✓base
  core20202302071828  
latest/stable canonical✓base
  core2220230210522   
latest/stable canonical✓base
  firefox   111.0-2 2432  
latest/candidate  mozilla✓  -
  gimp  2.10.30 393   
latest/stable snapcrafters  -
  gnome-3-28-1804   3.28.0-19-g98f9e67.98f9e67  161   
latest/stable canonical✓-
  gnome-3-38-2004   0+git.6f39565   119   
latest/stable canonical✓-
  gnome-42-2204 0+git.09673a5   65
latest/stable canonical✓-
  gtk-common-themes 0.1-81-g442e511 1535  
latest/stable/…   canonical✓-
  gtk-theme-pocillo 0.14.4.15 
latest/stable ubuntubudgie  -
  gtk-theme-qogirbudgie 22.04.1 8 
latest/stable ubuntubudgie  -
  gtk2-common-themes0.1 13
latest/stable canonical✓-
  hunspell-dictionaries-1-7-20041.7-20.04+pkg-6fd6  2 
latest/stable brlin -
  kde-frameworks-5-91-qt-5-15-3-core20  5.91.0  1 
latest/stable kde✓  -
  kde-frameworks-5-99-qt-5-15-7-core20  5.99.0  15
latest/stable kde✓  -
  kde-frameworks-5-core18   5.67.0  35
latest/stable kde✓  -
  libreoffice   7.5.1.2 270   
latest/stable canonical✓-
  shortwave 3.0.0   79
latest/stable alexmurray✪   -
  snapd 2.58.2  18357 
latest/stable canonical✓snapd
  snapd-desktop-integration 0.1 71
latest/stable/…   canonical✓-
  stellarium-daily  v1.21396  
latest/stable t4saha-
  thunderbird   102.9.0-1   305   
latest/candidate  canonical✓-
  vlc   3.0.18  3078  
latest/stable videolan✓ -

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


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

[Desktop-packages] [Bug 2011806] Re: [lunar] Snaps don't launch due to cgroup issue

[Jonas Gamao]

When I launch Thunderbird

Nov 14 20:12:55 systemd[9205]: Started 
snap.thunderbird.thunderbird-218c47bb-9cdf-4585-8487-1e76547933b3.scope.
Nov 14 20:12:55 systemd[9205]: Started 
app-thunderbird_thunderbird-4758a597c99d427f91814da5b05c365a.scope - 
Thunderbird Mail - Mail Client.
Nov 14 20:12:55 plasmashell[133984]: 
/user.slice/user-1000.slice/user@1000.service/app.slice/app-thunderbird_thunderbird-4758a597c99d427f91814da5b05c365a.scope
 is not a snap cgroup

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

Title:
  [lunar] Snaps don't launch due to cgroup issue

Status in GNOME Shell:
  New
Status in KDE Base:
  New
Status in gnome-desktop package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in kio package in Ubuntu:
  Confirmed
Status in snapd package in Ubuntu:
  Opinion

Bug description:
  Hi,

  Lunar up to date, Intel+Nvidia GPUs, Ubuntu Wayland or X11 session,
  hybrid or discrete graphics.

  If I click on a snap dash icon, nothing happens.
  Tested with Thunderbird, Firefox, Shortwave...
  (VS Code seems ok, maybe due to classic confinment?)

  I can launch without issue Chrome (deb), Synaptic, GNOME apps, etc.

  Recent updates included gnome-shell and libadwaita.

  ---

  I get this type of log for all problematic snaps:

  /user.slice/user-1000.slice/user@1000.service/app.slice/app-gnome-
  shortwave_shortwave-11885.scope is not a snap cgroup

  ---

  Context:

  $ snap --version
  snap2.58.3+23.04ubuntu1
  snapd   2.58.3+23.04ubuntu1
  series  16
  ubuntu  23.04
  kernel  6.1.0-16-generic

  $ snap list
  Nom   Version Révision  
Suivi Éditeur   Notes
  bare  1.0 5 
latest/stable canonical✓base
  code  ee2b180d122   
latest/stable vscode✓   classic
  core  16-2.58.2   14784 
latest/stable canonical✓core
  core18202303082714  
latest/stable canonical✓base
  core20202302071828  
latest/stable canonical✓base
  core2220230210522   
latest/stable canonical✓base
  firefox   111.0-2 2432  
latest/candidate  mozilla✓  -
  gimp  2.10.30 393   
latest/stable snapcrafters  -
  gnome-3-28-1804   3.28.0-19-g98f9e67.98f9e67  161   
latest/stable canonical✓-
  gnome-3-38-2004   0+git.6f39565   119   
latest/stable canonical✓-
  gnome-42-2204 0+git.09673a5   65
latest/stable canonical✓-
  gtk-common-themes 0.1-81-g442e511 1535  
latest/stable/…   canonical✓-
  gtk-theme-pocillo 0.14.4.15 
latest/stable ubuntubudgie  -
  gtk-theme-qogirbudgie 22.04.1 8 
latest/stable ubuntubudgie  -
  gtk2-common-themes0.1 13
latest/stable canonical✓-
  hunspell-dictionaries-1-7-20041.7-20.04+pkg-6fd6  2 
latest/stable brlin -
  kde-frameworks-5-91-qt-5-15-3-core20  5.91.0  1 
latest/stable kde✓  -
  kde-frameworks-5-99-qt-5-15-7-core20  5.99.0  15
latest/stable kde✓  -
  kde-frameworks-5-core18   5.67.0  35
latest/stable kde✓  -
  libreoffice   7.5.1.2 270   
latest/stable canonical✓-
  shortwave 3.0.0   79
latest/stable alexmurray✪   -
  snapd 2.58.2  18357 
latest/stable canonical✓snapd
  snapd-desktop-integration 0.1 71
latest/stable/…   canonical✓-
  stellarium-daily  v1.21396  
latest/stable t4saha-
  thunderbird   102.9.0-1   305   
latest/candidate  canonical✓-
  vlc   3.0.18  3078  
latest/stable videolan✓ -

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : 

[Desktop-packages] [Bug 2011806] Re: [lunar] Snaps don't launch due to cgroup issue

[Jonas Gamao]

Any updates with this one?

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

Title:
  [lunar] Snaps don't launch due to cgroup issue

Status in GNOME Shell:
  New
Status in KDE Base:
  New
Status in gnome-desktop package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in kio package in Ubuntu:
  Confirmed
Status in snapd package in Ubuntu:
  Opinion

Bug description:
  Hi,

  Lunar up to date, Intel+Nvidia GPUs, Ubuntu Wayland or X11 session,
  hybrid or discrete graphics.

  If I click on a snap dash icon, nothing happens.
  Tested with Thunderbird, Firefox, Shortwave...
  (VS Code seems ok, maybe due to classic confinment?)

  I can launch without issue Chrome (deb), Synaptic, GNOME apps, etc.

  Recent updates included gnome-shell and libadwaita.

  ---

  I get this type of log for all problematic snaps:

  /user.slice/user-1000.slice/user@1000.service/app.slice/app-gnome-
  shortwave_shortwave-11885.scope is not a snap cgroup

  ---

  Context:

  $ snap --version
  snap2.58.3+23.04ubuntu1
  snapd   2.58.3+23.04ubuntu1
  series  16
  ubuntu  23.04
  kernel  6.1.0-16-generic

  $ snap list
  Nom   Version Révision  
Suivi Éditeur   Notes
  bare  1.0 5 
latest/stable canonical✓base
  code  ee2b180d122   
latest/stable vscode✓   classic
  core  16-2.58.2   14784 
latest/stable canonical✓core
  core18202303082714  
latest/stable canonical✓base
  core20202302071828  
latest/stable canonical✓base
  core2220230210522   
latest/stable canonical✓base
  firefox   111.0-2 2432  
latest/candidate  mozilla✓  -
  gimp  2.10.30 393   
latest/stable snapcrafters  -
  gnome-3-28-1804   3.28.0-19-g98f9e67.98f9e67  161   
latest/stable canonical✓-
  gnome-3-38-2004   0+git.6f39565   119   
latest/stable canonical✓-
  gnome-42-2204 0+git.09673a5   65
latest/stable canonical✓-
  gtk-common-themes 0.1-81-g442e511 1535  
latest/stable/…   canonical✓-
  gtk-theme-pocillo 0.14.4.15 
latest/stable ubuntubudgie  -
  gtk-theme-qogirbudgie 22.04.1 8 
latest/stable ubuntubudgie  -
  gtk2-common-themes0.1 13
latest/stable canonical✓-
  hunspell-dictionaries-1-7-20041.7-20.04+pkg-6fd6  2 
latest/stable brlin -
  kde-frameworks-5-91-qt-5-15-3-core20  5.91.0  1 
latest/stable kde✓  -
  kde-frameworks-5-99-qt-5-15-7-core20  5.99.0  15
latest/stable kde✓  -
  kde-frameworks-5-core18   5.67.0  35
latest/stable kde✓  -
  libreoffice   7.5.1.2 270   
latest/stable canonical✓-
  shortwave 3.0.0   79
latest/stable alexmurray✪   -
  snapd 2.58.2  18357 
latest/stable canonical✓snapd
  snapd-desktop-integration 0.1 71
latest/stable/…   canonical✓-
  stellarium-daily  v1.21396  
latest/stable t4saha-
  thunderbird   102.9.0-1   305   
latest/candidate  canonical✓-
  vlc   3.0.18  3078  
latest/stable videolan✓ -

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/2011806/+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 1831483] Re: metrics on pushed routes not applied

[Haw Loeung]

Any updates on this? We're still getting reports of issues from users
where we have two VPN endpoints each pushing routes with different
metrics for preferred routes / path.

We've had to work around this with smaller prefixes.

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

Title:
  metrics on pushed routes not applied

Status in NetworkManager-OpenVPN:
  Expired
Status in network-manager-openvpn package in Ubuntu:
  Triaged

Bug description:
  We have a couple of VPN endpoints located in different places.  These
  each provide access to a bunch of things located in both places.  We
  decided that it would be a good idea to let people connect to both
  endpoints so that by adjusting the metrics on the pushed routes (we
  used 500 and 1000) our users would always use the shortest available
  path.

  This works great with vanilla openvpn, but when using network-manager-
  openvpn, the metrics are lost and instead "50" is used, which means
  that only one gateway is used.  Ideally network-manager-openvpn would
  use the supplied metrics so that traffic is routed as intended.

  This seems to affect network-manager-openvpn in releases of Ubuntu up
  to 18.04 LTS, and possibly beyond.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager-openvpn/+bug/1831483/+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 2043524] [NEW] audio disappeared after upgrade to Ubuntu 23.10

[Mark Bixler]

Public bug reported:

I upgraded to Ubuntu 23.10 from 23.04. Everything seems to work except
there is no audio output on streaming functions. The external bluetooth
speaker is connected and detected. It is charged and responds to
testing. Just no sound when playing videos or podcasts.

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: pulseaudio 1:16.1+dfsg1-2ubuntu4
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  owner   975 F wireplumber
 /dev/snd/seq:owner   971 F pipewire
CasperMD5CheckResult: fail
CurrentDesktop: KDE
Date: Tue Nov 14 17:50:17 2023
InstallationDate: Installed on 2023-04-15 (213 days ago)
InstallationMedia: Kubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
ProcEnviron:
 LANG=en_US.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: pulseaudio
Symptom: audio
UpgradeStatus: Upgraded to mantic on 2023-11-09 (5 days ago)
dmi.bios.date: 07/04/2012
dmi.bios.release: 4.6
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V3.0
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H61M-P31/W8 (MS-7788)
dmi.board.vendor: MSI
dmi.board.version: 1.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV3.0:bd07/04/2012:br4.6:svnMSI:pnMS-7788:pvr1.0:rvnMSI:rnH61M-P31/W8(MS-7788):rvr1.0:cvnMSI:ct3:cvr1.0:skuTobefilledbyO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: MS-7788
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: 1.0
dmi.sys.vendor: MSI

** Affects: pulseaudio (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug mantic

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

Title:
  audio disappeared after upgrade to Ubuntu 23.10

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I upgraded to Ubuntu 23.10 from 23.04. Everything seems to work except
  there is no audio output on streaming functions. The external
  bluetooth speaker is connected and detected. It is charged and
  responds to testing. Just no sound when playing videos or podcasts.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: pulseaudio 1:16.1+dfsg1-2ubuntu4
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  owner   975 F wireplumber
   /dev/snd/seq:owner   971 F pipewire
  CasperMD5CheckResult: fail
  CurrentDesktop: KDE
  Date: Tue Nov 14 17:50:17 2023
  InstallationDate: Installed on 2023-04-15 (213 days ago)
  InstallationMedia: Kubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  ProcEnviron:
   LANG=en_US.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: pulseaudio
  Symptom: audio
  UpgradeStatus: Upgraded to mantic on 2023-11-09 (5 days ago)
  dmi.bios.date: 07/04/2012
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V3.0
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H61M-P31/W8 (MS-7788)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV3.0:bd07/04/2012:br4.6:svnMSI:pnMS-7788:pvr1.0:rvnMSI:rnH61M-P31/W8(MS-7788):rvr1.0:cvnMSI:ct3:cvr1.0:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7788
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI

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

[Alan Jenkins]

I tried installing dbgsym packages or using debuginfod to get a full
backtrace for libwayland-server.so, but I failed.

$ sudo apt install -qq libwayland-server0-dbgsym
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies.
 libwayland-server0-dbgsym : Depends: libwayland-server0 (= 1.20.0-1) but 
1.20.0-1ubuntu0.1 is to be installed
E: Unable to correct problems, you have held broken packages.


$ export DEBUGINFOD_URLS="https://debuginfod.ubuntu.com;
$ sudo gdb 
...
(gdb) set debuginfod enabled on
(gdb) attach 9248
(gdb) break recvmsg
Breakpoint 1 at 0x7f25319279d0: file ../sysdeps/unix/sysv/linux/recvmsg.c, line 
35.
(gdb) cont
Continuing.

Thread 1 "gnome-shell" hit Breakpoint 1, __libc_recvmsg (fd=21, 
msg=0x7fff1de64a50, flags=1073741888) at ../sysdeps/unix/sysv/linux/recvmsg.c:35
35  ../sysdeps/unix/sysv/linux/recvmsg.c: No such file or directory.
(gdb) bt full
#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
source = 
loop = 
...
(gdb) finish
Run till exit from #0  __libc_recvmsg (fd=21, msg=0x7fff1de64a50, 
flags=1073741888) at ../sysdeps/unix/sysv/linux/recvmsg.c:35
0x7f2531ea5ad6 in ?? () from /lib/x86_64-linux-gnu/libwayland-server.so.0
Value returned is $2 = 12
(gdb) finish
Run till exit from #0  0x7f2531ea5ad6 in ?? () from 
/lib/x86_64-linux-gnu/libwayland-server.so.0
0x7f2531ea4eea in wl_event_loop_dispatch () from 
/lib/x86_64-linux-gnu/libwayland-server.so.0

(gdb) s
Single stepping until exit from function wl_event_loop_dispatch,
which has no line number information.
wayland_event_source_dispatch (base=, callback=, 
data=) at ../src/wayland/meta-wayland.c:112
112 ../src/wayland/meta-wayland.c: No such file or directory.

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

Title:
  gnome-shell on non-active VT busy-loops through libwayland-server.so
  (sometimes)

Status in gnome-shell 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  

[Desktop-packages] [Bug 2043517] [NEW] gnome-shell on non-active VT busy-loops through libwayland-server.so (sometimes)

[Alan Jenkins]

Public bug reported:

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

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

Title:
  gnome-shell on non-active VT busy-loops through libwayland-server.so
  (sometimes)

Status in gnome-shell 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,
  

[Desktop-packages] [Bug 2043403] Re: screen is flickering

[Muriel Ritsch]

** Attachment added: "_usr_bin_seahorse.1000.crash"
   
https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/2043403/+attachment/5719404/+files/_usr_bin_seahorse.1000.crash

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

Title:
  screen is flickering

Status in seahorse package in Ubuntu:
  New

Bug description:
  I have already posted my problems here and I should report my bugs here:
  
https://ubuntuforums.org/showthread.php?t=2492208=f45e03446f15046b1befc5497ef42eb1

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: seahorse 41.0-2
  ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-36-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 13 17:13:12 2023
  InstallationDate: Installed on 2023-08-29 (76 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  SourcePackage: seahorse
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/2043403/+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 2043395] Re: Updating to Ubuntu 23.10 (mantic) fails as the gnome-remote-desktop & gnome-shell packages are broken

[Peter]

** Attachment added: "apt.log"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2043395/+attachment/5719403/+files/apt.log

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

Title:
  Updating to Ubuntu 23.10 (mantic) fails as the gnome-remote-desktop &
  gnome-shell packages are broken

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Running do-release-upgrade on 23.04 (lunar), **ubuntu-desktop-minimal
  based** install:

  2023-11-10 07:03:16,578 DEBUG nvidiaUpdate()
  2023-11-10 07:03:20,125 INFO no old nvidia driver installed, installing no new
  2023-11-10 07:03:20,125 DEBUG quirks: running PostDistUpgradeCache
  2023-11-10 07:03:20,125 DEBUG running Quirks.PostDistUpgradeCache
  2023-11-10 07:03:20,237 DEBUG Comparing 6.2.0-35 with
  2023-11-10 07:03:20,237 DEBUG Comparing 6.2.0-36 with 6.2.0-35
  2023-11-10 07:03:20,238 DEBUG Comparing 6.5.0-10 with 6.2.0-36
  2023-11-10 07:03:20,554 ERROR Dist-upgrade failed: 'Broken packages after 
upgrade: gnome-remote-desktop, gnome-shell'
  2023-11-10 07:03:20,564 DEBUG abort called

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2043395/+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 2043395] Re: Updating to Ubuntu 23.10 (mantic) fails as the gnome-remote-desktop & gnome-shell packages are broken

[Peter]

@jbicha 
Which files are those are those in? /var/log/dist-upgrade/apt.log for apt logs 
I assume but where can I find full upgrader logs?


I worked around this issue by removing gnome-remote-desktop, and installing 
ubuntu-desktop in addition to ubuntu-desktop-minimal, and then the upgrade 
worked (somewhat - see 
https://bugs.launchpad.net/ubuntu/+source/friendly-recovery/+bug/2043394 ) so I 
can't reproduce now as I'm on 23.10

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

Title:
  Updating to Ubuntu 23.10 (mantic) fails as the gnome-remote-desktop &
  gnome-shell packages are broken

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Running do-release-upgrade on 23.04 (lunar), **ubuntu-desktop-minimal
  based** install:

  2023-11-10 07:03:16,578 DEBUG nvidiaUpdate()
  2023-11-10 07:03:20,125 INFO no old nvidia driver installed, installing no new
  2023-11-10 07:03:20,125 DEBUG quirks: running PostDistUpgradeCache
  2023-11-10 07:03:20,125 DEBUG running Quirks.PostDistUpgradeCache
  2023-11-10 07:03:20,237 DEBUG Comparing 6.2.0-35 with
  2023-11-10 07:03:20,237 DEBUG Comparing 6.2.0-36 with 6.2.0-35
  2023-11-10 07:03:20,238 DEBUG Comparing 6.5.0-10 with 6.2.0-36
  2023-11-10 07:03:20,554 ERROR Dist-upgrade failed: 'Broken packages after 
upgrade: gnome-remote-desktop, gnome-shell'
  2023-11-10 07:03:20,564 DEBUG abort called

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2043395/+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 2043507] [NEW] xdg-desktop-portal-gtk - asks two times "Select window to share with requesting application" when starting sharing a window in google meet

[Vlad Gheorghe]

Public bug reported:


Expected (initial) behavior in Google Meet was
During the meeting:
When I click "Present Now"
Then popup:  "Choose what to share with meet.google.com"
When I click "Window" and select window to share and click OK
Then the selected window is shared in the meet

Observed behaviour:
When I click "Present Now"
Then Popup1:  "Choose what to share with meet.google.com"
When I click "Window" tab
Then Popup2 "Select window to share with requesting application"
- and Popup1 window list remains empty
When I select a window and click Share
Then Popup1 > Window shows a small image of the selected window
When in Popup1 i click on the window image and Share
Then Popup3: "Select window to share with requesting application" and a list of 
open windows
When in Popup3 I select again the window to share and click Share
Then the selected window is shared in the meet


Based on the window title it seems that the extra popups (2/3 above) come from 
https://github.com/flatpak/xdg-desktop-portal-gtk/blob/1.14.0/src/screencastwidget.c


release: Ubuntu 22.04.3 LTS
xdg-desktop-portal-gtk/jammy,now 1.14.0-1build1 amd64 
Google Chrome: Version 119.0.6045.123 (Official Build) (64-bit)

** Affects: vino (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  xdg-desktop-portal-gtk - asks two times "Select window to share with
  requesting application" when  starting sharing a window in google meet

Status in vino package in Ubuntu:
  New

Bug description:
  
  Expected (initial) behavior in Google Meet was
  During the meeting:
  When I click "Present Now"
  Then popup:  "Choose what to share with meet.google.com"
  When I click "Window" and select window to share and click OK
  Then the selected window is shared in the meet

  Observed behaviour:
  When I click "Present Now"
  Then Popup1:  "Choose what to share with meet.google.com"
  When I click "Window" tab
  Then Popup2 "Select window to share with requesting application"
  - and Popup1 window list remains empty
  When I select a window and click Share
  Then Popup1 > Window shows a small image of the selected window
  When in Popup1 i click on the window image and Share
  Then Popup3: "Select window to share with requesting application" and a list 
of open windows
  When in Popup3 I select again the window to share and click Share
  Then the selected window is shared in the meet


  
  Based on the window title it seems that the extra popups (2/3 above) come 
from 
  
https://github.com/flatpak/xdg-desktop-portal-gtk/blob/1.14.0/src/screencastwidget.c

  
  release: Ubuntu 22.04.3 LTS
  xdg-desktop-portal-gtk/jammy,now 1.14.0-1build1 amd64 
  Google Chrome: Version 119.0.6045.123 (Official Build) (64-bit)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vino/+bug/2043507/+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 2043015] Re: Update gnome-shell to 45.1

[Launchpad Bug Tracker]

This bug was fixed in the package gnome-shell - 45.1-1ubuntu1

---
gnome-shell (45.1-1ubuntu1) noble; urgency=medium

  * Merge with Debian. Remaining changes:
- Add some Recommends:
  + ubuntu-session (| gnome-session) to have the ubuntu session available
  + ubuntu-wallpapers
  + xserver-xorg-legacy
  + yaru-theme-gnome-shell for the default ubuntu theming
- Move some Recommends to Suggests:
  + chrome-gnome-shell
  + gnome-backgrounds
- Update debian/gbp.conf with Ubuntu settings
- Add debian/ubuntu-session-mods/ubuntu.json
- debian/patches: Do not hang & crash if fingerprint service fails to start
  (LP: #1962566)
- ubuntu/desktop_detect.patch:
  + add caching for desktop detection to avoid querying the current
desktop env variable as iterate through the list each time. For the
time of the Shell process, we can expect this env variable to stay
stable.
- ubuntu/lightdm-user-switching.patch:
  + Allow user switching when using LightDM.
- ubuntu/lock_on_suspend.patch
  + Respect Ubuntu's lock-on-suspend setting.
- ubuntu/background_login.patch
  + Change default background color as we modified the default GDM color
for our ubuntu session.
- ubuntu/gdm_alternatives.patch
  + Add support for GDM3 theme alternatives
- main-show-an-error-message-on-gnome-shell-crash.patch,
  global-make-possible-to-set-debug-flags-dynamically.patch,
  main-increase-the-granularity-of-backtraces-in-SHELL_DEBU.patch,
  main-add-backtrace-crashes-all-and-backtrace-all.patch,
  sessionMode-add-support-for-debugFlags-parameter.patch:
  + Improve debug JS tracing for crash reports
- ubuntu/smarter_alt_tab.patch:
  + quick alt-tab (without showing up the switcher) switch only between
the last window of the last 2 applications to be focused instead of
raising all windows of those apps.
- magnifier-Show-cursor-when-magnifier-is-enabled-and-scale.patch:
  + Show monitor scaled cursor when magnifier is enabled
- ubuntu/search-call-XUbuntuCancel-method-on-providers-when-no-dat.patch:
  + stop searches when requested from UI
- magnifier-Show-cursor-when-magnifier-is-enabled-and-scale.patch
- u/search-call-XUbuntuCancel-method-on-providers-when-no-dat.patch
- ubuntu/resolve_alternate_theme_path.patch
- ubuntu/secure_mode_extension.patch
- ubuntu/keep-ubuntu-logo-bright-lp1867133-v1.patch
- ubuntu/configure_login_screen.patch
- ubuntu/layout-Make-starting-in-the-overview-optional.patch:
  + Makes dock replace overview easier
- ubuntu/layout-Try-to-allocate-before-getting-size-of-tracke.patch:
  + Ensure windows don't get maximized under the panels / dock
- debian/patches: Compute system background color from theme (LP: #1965727)
- ubuntu/configure-login-screen.patch: Use bg color for initial system bg
  (LP: #1965727)
- debian/patches: Ensure St.Entry's `selected-color` CSS property is
  honored (LP: #1878998)
- ubuntu/support-loading-Yaru-variants: Handle dark/light variants better
- d/p/use-favorites-strings: Only apply this to ubuntu session
- debian/patches: Support configuring icons resource to use for mode
- Revert-st-Apply-css-foreground-color-to-text-as-a-PangoAt.patch:
  + Ensure selected-text foreground color is preserved
- ubuntu/sessionMode-Add-support-for-configuring-an-icons-resource.patch:
  + Support loading iconsResourceName from session file
- ubuntu/main-Support-loading-multiple-Yaru-theme-variants.patch,
- ubuntu/darkMode-Add-support-to-Yaru-theme-color-variants.patch:
  + Support loading Yaru theme variants (for accent color)
- ubuntu/shell-global-util-Do-not-move-snap-apps-to-gnome-apps-sco.patch
  * Drop 2 patches applied in new release

gnome-shell (45.1-1) experimental; urgency=medium

  [ Jeremy Bícha ]
  * New upstream release (LP: #2043015)
  * Stop using debian/control.in and dh_gnome_clean

  [ Simon McVittie ]
  * Merge with version 44.5-2 from unstable

 -- Jeremy Bícha   Wed, 08 Nov 2023 15:34:45 +0200

** Changed in: gnome-shell (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Update gnome-shell to 45.1

Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Mantic:
  Fix Committed

Bug description:
  Impact
  --
  There is a new bugfix release in the stable 45 series.

  https://gitlab.gnome.org/GNOME/gnome-shell/-/blob/45.1/NEWS

  Test Case
  -
  Complete all the non-optional test cases at 
https://wiki.ubuntu.com/DesktopTeam/TestPlans/GNOMEShell

  What Could Go Wrong
  ---
  GNOME Shell is the heart of the Ubuntu desktop experience.

  A severe enough bug 

[Desktop-packages] [Bug 2043395] Re: Updating to Ubuntu 23.10 (mantic) fails as the gnome-remote-desktop & gnome-shell packages are broken

[Jeremy Bícha]

If the issue was phased updates, the upgrade should work fine today.

** Changed in: gnome-shell (Ubuntu)
   Importance: Undecided => High

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

Title:
  Updating to Ubuntu 23.10 (mantic) fails as the gnome-remote-desktop &
  gnome-shell packages are broken

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Running do-release-upgrade on 23.04 (lunar), **ubuntu-desktop-minimal
  based** install:

  2023-11-10 07:03:16,578 DEBUG nvidiaUpdate()
  2023-11-10 07:03:20,125 INFO no old nvidia driver installed, installing no new
  2023-11-10 07:03:20,125 DEBUG quirks: running PostDistUpgradeCache
  2023-11-10 07:03:20,125 DEBUG running Quirks.PostDistUpgradeCache
  2023-11-10 07:03:20,237 DEBUG Comparing 6.2.0-35 with
  2023-11-10 07:03:20,237 DEBUG Comparing 6.2.0-36 with 6.2.0-35
  2023-11-10 07:03:20,238 DEBUG Comparing 6.5.0-10 with 6.2.0-36
  2023-11-10 07:03:20,554 ERROR Dist-upgrade failed: 'Broken packages after 
upgrade: gnome-remote-desktop, gnome-shell'
  2023-11-10 07:03:20,564 DEBUG abort called

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2043395/+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 2043395] Re: Updating to Ubuntu 23.10 (mantic) fails as the gnome-remote-desktop & gnome-shell packages are broken

[Jeremy Bícha]

We need the full apt and upgrader logs to better understand why gnome-
shell is broken.

The date you reported corresponds with when a mutter update was being
pushed to -updates. Perhaps this is a bad interaction with Ubuntu's
phased updates.

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

Title:
  Updating to Ubuntu 23.10 (mantic) fails as the gnome-remote-desktop &
  gnome-shell packages are broken

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Running do-release-upgrade on 23.04 (lunar), **ubuntu-desktop-minimal
  based** install:

  2023-11-10 07:03:16,578 DEBUG nvidiaUpdate()
  2023-11-10 07:03:20,125 INFO no old nvidia driver installed, installing no new
  2023-11-10 07:03:20,125 DEBUG quirks: running PostDistUpgradeCache
  2023-11-10 07:03:20,125 DEBUG running Quirks.PostDistUpgradeCache
  2023-11-10 07:03:20,237 DEBUG Comparing 6.2.0-35 with
  2023-11-10 07:03:20,237 DEBUG Comparing 6.2.0-36 with 6.2.0-35
  2023-11-10 07:03:20,238 DEBUG Comparing 6.5.0-10 with 6.2.0-36
  2023-11-10 07:03:20,554 ERROR Dist-upgrade failed: 'Broken packages after 
upgrade: gnome-remote-desktop, gnome-shell'
  2023-11-10 07:03:20,564 DEBUG abort called

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2043395/+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 2043395] Re: Updating to Ubuntu 23.10 (mantic) fails as the gnome-remote-desktop & gnome-shell packages are broken

[Peter]

** Description changed:

- Running do-release-upgrade on a 23.04 (lunar), **ubuntu-desktop-minimal
+ Running do-release-upgrade on 23.04 (lunar), **ubuntu-desktop-minimal
  based** install:
  
  2023-11-10 07:03:16,578 DEBUG nvidiaUpdate()
  2023-11-10 07:03:20,125 INFO no old nvidia driver installed, installing no new
  2023-11-10 07:03:20,125 DEBUG quirks: running PostDistUpgradeCache
  2023-11-10 07:03:20,125 DEBUG running Quirks.PostDistUpgradeCache
  2023-11-10 07:03:20,237 DEBUG Comparing 6.2.0-35 with
  2023-11-10 07:03:20,237 DEBUG Comparing 6.2.0-36 with 6.2.0-35
  2023-11-10 07:03:20,238 DEBUG Comparing 6.5.0-10 with 6.2.0-36
  2023-11-10 07:03:20,554 ERROR Dist-upgrade failed: 'Broken packages after 
upgrade: gnome-remote-desktop, gnome-shell'
  2023-11-10 07:03:20,564 DEBUG abort called

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

Title:
  Updating to Ubuntu 23.10 (mantic) fails as the gnome-remote-desktop &
  gnome-shell packages are broken

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Running do-release-upgrade on 23.04 (lunar), **ubuntu-desktop-minimal
  based** install:

  2023-11-10 07:03:16,578 DEBUG nvidiaUpdate()
  2023-11-10 07:03:20,125 INFO no old nvidia driver installed, installing no new
  2023-11-10 07:03:20,125 DEBUG quirks: running PostDistUpgradeCache
  2023-11-10 07:03:20,125 DEBUG running Quirks.PostDistUpgradeCache
  2023-11-10 07:03:20,237 DEBUG Comparing 6.2.0-35 with
  2023-11-10 07:03:20,237 DEBUG Comparing 6.2.0-36 with 6.2.0-35
  2023-11-10 07:03:20,238 DEBUG Comparing 6.5.0-10 with 6.2.0-36
  2023-11-10 07:03:20,554 ERROR Dist-upgrade failed: 'Broken packages after 
upgrade: gnome-remote-desktop, gnome-shell'
  2023-11-10 07:03:20,564 DEBUG abort called

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2043395/+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 2043442] Re: /usr/libexec/ibus-ui-gtk3 --enable-wayland-im system freezes

[Gunnar Hjalmarsson]

Thanks for your report.

I see Plasma and Wayland, which reminds me of
 and .

* Have you applied the IBus Wayland virtual keyboard?

* If you have, can you please run this command:

  im-config -n none

  and reboot, and then let us know if that improves things.

** Bug watch added: Debian Bug tracker #1052005
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052005

** Changed in: ibus (Ubuntu)
   Status: New => Incomplete

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

Title:
  /usr/libexec/ibus-ui-gtk3 --enable-wayland-im system freezes

Status in ibus package in Ubuntu:
  Incomplete

Bug description:
  Apport captured a system freeze [crash] which required a hard reboot.
  However I could not confirm that the report was successfully uploaded.

  The /var/log/apport.log entry is as follows.
  
  ERROR: apport (pid 17772) 2023-11-13 17:17:02,197: this executable already 
crashed 2 times, ignoring
  INFO: apport (pid 27019) 2023-11-13 21:07:39,820: called for pid 17786, 
signal 11, core limit 0, dump mode 1
  INFO: apport (pid 27019) 2023-11-13 21:07:39,821: executable: 
/usr/libexec/ibus-ui-gtk3 (command line "/usr/libexec/ibus-ui-gtk3 
--enable-wayland-im --exec-daemon --daemon-args --xim\ --panel\ disable")
  ERROR: apport (pid 27019) 2023-11-13 21:07:40,821: gdbus call error: Error: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.gnome.SessionManager was not provided by any .service files

  INFO: apport (pid 27019) 2023-11-13 21:07:42,687: wrote report 
/var/crash/_usr_libexec_ibus-ui-gtk3.1000.crash
  INFO: apport (pid 29410) 2023-11-13 21:38:11,084: called for pid 27746, 
signal 11, core limit 0, dump mode 1
  INFO: apport (pid 29410) 2023-11-13 21:38:11,085: executable: 
/usr/libexec/ibus-ui-gtk3 (command line "/usr/libexec/ibus-ui-gtk3 
--enable-wayland-im --exec-daemon --daemon-args --xim\ --panel\ disable")
  ERROR: apport (pid 29410) 2023-11-13 21:38:12,085: gdbus call error: Error: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.gnome.SessionManager was not provided by any .service files

  Note:The last line may explain why I could not verify the file
  upload when I performed the following proceedure per:
  https://help.ubuntu.com/community/ReportingBugs

  ---
  luigi@l-g905:~$ ubuntu-bug /var/crash/_usr_libexec_ibus-ui-gtk3.1000.crash

  luigi@l-g905:~$ sudo cat /var/lib/whoopsie/whoopsie-id
  
7a0c123f5172023e795f73a584fa57e5efd8e12b9c45fd40142d884f4260a9abe2b1d30152e6d8f6c7cbc21190d542ebda3b4cfc316047ba6be306793ee2fe80

  
https://errors.ubuntu.com/user/7a0c123f5172023e795f73a584fa57e5efd8e12b9c45fd40142d884f4260a9abe2b1d30152e6d8f6c7cbc21190d542ebda3b4cfc316047ba6be306793ee2fe80:
 No such file or directory
  -

  
  This upload fialure seemed confirmed when in: 
https://answers.launchpad.net/ubuntu/+questions?
  a search found no Questions matching "ibus-ui-gtk3" for Ubuntu
  "ibus-ui-gtk3" is not mentioned in the release notes bugs section.

  In
  https://errors.ubuntu.com/?release=Ubuntu%2023.10=day
  text Searches for _usr_libexec_ibus-ui-gtk3 and the "Whoopsie-id" above both 
returned "phrase not found"

  I reproduced the executable failure using Terminal with these results
  --
  ~$ /usr/libexec/ibus-ui-gtk3 --enable-wayland-im --exec-daemon --daemon-args 
--xim\ --panel\ disable

  Returns:
  ~$ /usr/libexec/ibus-ui-gtk3 --enable-wayland-im --exec-daemon --daemon-args 
--xim\ --panel\ disable

  (ibus-ui-gtk3:9353): IBUS-CRITICAL **: 23:11:04.233: string_substring:
  assertion '(offset + len) <= string_length' failed

  (ibus-ui-gtk3:9353): IBUS-CRITICAL **: 23:11:04.233: string_substring:
  assertion '(offset + len) <= string_length' failed

  ** (ibus-ui-gtk3:9353): ERROR **: 23:11:04.236: No input_method global

  Trace/breakpoint trap (core dumped)
  -

  I am attaching the _usr_libexec_ibus-ui-gtk3.1000.crash file
  /var/crash/ _ust_libexec_ibus-ui-gtk3.1000.crash (3.1 MiB - 1144 lines
  - modified on 11/13/23 9:07 PM - US-ASCII)

  Platform Information 
  Operating System: Ubuntu Studio 23.10
  KDE Plasma Version:   5.27.8
  KDE Frameworks Version:   5.110.0
  Qt Version:   5.15.10
  Kernel Version:   6.5.0-10-lowlatency (64-bit)
  Graphics Platform:Wayland
  Processors:   24 × AMD Ryzen 9 7900X 12-Core Processor
  Memory:   31.0 GiB of RAM
  Graphics Processor:   NV172
  Manufacturer: MicroElectronics
  Product Name: G905
  System Version:   1.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/2043442/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to   

[Desktop-packages] [Bug 2043492] Re: Installed 23.10 on Huawei 16s. Speakers don't work. When I plug in headphones, the speakers work. the operating system seems to have the two switched. Also, on goo

[Ubuntu Foundations Team Bug Bot]

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

Title:
  Installed 23.10 on Huawei 16s.  Speakers don't work.  When I plug in
  headphones, the speakers work.  the operating system seems to have the
  two switched.  Also, on google meets, it cannot find a sound device.

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  No further information.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  noe2350 F pipewire
noe2357 F wireplumber
   /dev/snd/seq:noe2350 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 14 16:42:30 2023
  InstallationDate: Installed on 2023-11-01 (13 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  PackageArchitecture: all
  ProcEnviron:
   LANG=en_US.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: 11/08/2022
  dmi.bios.release: 1.23
  dmi.bios.vendor: HUAWEI
  dmi.bios.version: 1.23
  dmi.board.asset.tag: N/A
  dmi.board.name: CREF-XX-PCB
  dmi.board.vendor: HUAWEI
  dmi.board.version: M1010
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: HUAWEI
  dmi.chassis.version: M1010
  dmi.ec.firmware.release: 1.23
  dmi.modalias: 
dmi:bvnHUAWEI:bvr1.23:bd11/08/2022:br1.23:efr1.23:svnHUAWEI:pnCREF-XX:pvrM1010:rvnHUAWEI:rnCREF-XX-PCB:rvrM1010:cvnHUAWEI:ct10:cvrM1010:skuC100:
  dmi.product.family: MateBook
  dmi.product.name: CREF-XX
  dmi.product.sku: C100
  dmi.product.version: M1010
  dmi.sys.vendor: HUAWEI

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2043492/+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 2043215] Re: Since upgrading to Ubuntu 23.10, the stylus (pen) does not work in Xorg.

[Peter Freeth]

Same problem. Under Xorg, the Wacom tablet can move the pointer but as
soon as I tap to click, the system locks up. Pressing alt tab a few
times restores movement to the pointer. The Wacom is therefore unusable
under Xorg. Sadly, in GIMP it's also unusable under Wayland as the
pointers are invisible.

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

Title:
  Since upgrading to Ubuntu 23.10, the stylus (pen) does not work in
  Xorg.

Status in xorg package in Ubuntu:
  New

Bug description:
  There is more information on this issue: 
https://github.com/xournalpp/xournalpp/issues/5303
  and the other bug report that is linked there.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Nov 10 07:17:22 2023
  DistUpgraded: 2023-11-06 20:32:35,715 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: mantic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox/7.0.10, 6.2.0-36-generic, x86_64: installed
   virtualbox/7.0.10, 6.5.0-10-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Fujitsu Limited. HD Graphics 5500 [10cf:1898]
  InstallationDate: Installed on 2021-05-25 (899 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-10-generic 
root=UUID=ce1b5a3a-3fee-4143-a385-d16e7d44c53a ro i8042.notimeout i8042.nomux 
quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to mantic on 2023-11-07 (3 days ago)
  dmi.bios.date: 12/21/2015
  dmi.bios.release: 1.15
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: Version 1.15
  dmi.board.name: FJNB288
  dmi.board.vendor: FUJITSU
  dmi.board.version: D2
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.15:bd12/21/2015:br1.15:svnFUJITSU:pnLIFEBOOKT935:pvr:rvnFUJITSU:rnFJNB288:rvrD2:cvnFUJITSU:ct10:cvr:sku:
  dmi.product.name: LIFEBOOK T935
  dmi.sys.vendor: FUJITSU
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.115-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2043215/+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 2019137] Re: gnome-software should (?) be separated from the packagekit

[Jeremy Bícha]

> we will have to figure out where and how to insert the plugin as
mandatory (for example, when the user completely gives up on snap
packages)

This is not possible.

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

Title:
  gnome-software should (?) be separated from the packagekit

Status in gnome-software package in Ubuntu:
  Triaged

Bug description:
  Given that the Snap Store is currently the default in Ubuntu instead
  of GNOME Software, the only reason GNOME Software (along with the Snap
  Store) can be installed is to support Flatpak applications.

  In the current instance, if you want to add flatpak support, GNOME
  Software is installed with both the apt packagekit add-on and the
  flatpak plugin, which is duplication of work (Software Updater already
  works on updates, and Snap Store works on showing deb apps).

  And since the future app store explicitly refuses [1], [2] to support
  flatpak applications, users who need this package format will be
  forced to put GNOME Software with everything I pointed out above.

  Therefore, it would be very nice if the developers removed the
  packagekit add-on from the "gnome-software part" and made it a "plug-
  in for gnome-software".

  I, unfortunately, have no such experience with packaging deb packages
  at the moment, and it turns out that it will obviously be necessary to
  work out both the code part (which, as far as I can see, won't be very
  difficult [3]), as well as the part where we will have to figure out
  where and how to insert the plugin as mandatory (for example, when the
  user completely gives up on snap packages) and as optional (because
  the Snap Store already stands).

  Also, let me know if this needs to be sent to upstream (Debian) instead of 
here.
  
---
  1. https://github.com/ubuntu-flutter-community/software/issues/126
  2. https://github.com/ubuntu-flutter-community/software/issues/30
  3. https://build.opensuse.org/request/show/1031279

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/2019137/+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 2043442] Re: /usr/libexec/ibus-ui-gtk3 --enable-wayland-im system freezes

[Paul White]

** Tags added: mantic

** Package changed: ubuntu => ibus (Ubuntu)

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

Title:
  /usr/libexec/ibus-ui-gtk3 --enable-wayland-im system freezes

Status in ibus package in Ubuntu:
  New

Bug description:
  Apport captured a system freeze [crash] which required a hard reboot.
  However I could not confirm that the report was successfully uploaded.

  The /var/log/apport.log entry is as follows.
  
  ERROR: apport (pid 17772) 2023-11-13 17:17:02,197: this executable already 
crashed 2 times, ignoring
  INFO: apport (pid 27019) 2023-11-13 21:07:39,820: called for pid 17786, 
signal 11, core limit 0, dump mode 1
  INFO: apport (pid 27019) 2023-11-13 21:07:39,821: executable: 
/usr/libexec/ibus-ui-gtk3 (command line "/usr/libexec/ibus-ui-gtk3 
--enable-wayland-im --exec-daemon --daemon-args --xim\ --panel\ disable")
  ERROR: apport (pid 27019) 2023-11-13 21:07:40,821: gdbus call error: Error: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.gnome.SessionManager was not provided by any .service files

  INFO: apport (pid 27019) 2023-11-13 21:07:42,687: wrote report 
/var/crash/_usr_libexec_ibus-ui-gtk3.1000.crash
  INFO: apport (pid 29410) 2023-11-13 21:38:11,084: called for pid 27746, 
signal 11, core limit 0, dump mode 1
  INFO: apport (pid 29410) 2023-11-13 21:38:11,085: executable: 
/usr/libexec/ibus-ui-gtk3 (command line "/usr/libexec/ibus-ui-gtk3 
--enable-wayland-im --exec-daemon --daemon-args --xim\ --panel\ disable")
  ERROR: apport (pid 29410) 2023-11-13 21:38:12,085: gdbus call error: Error: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.gnome.SessionManager was not provided by any .service files

  Note:The last line may explain why I could not verify the file
  upload when I performed the following proceedure per:
  https://help.ubuntu.com/community/ReportingBugs

  ---
  luigi@l-g905:~$ ubuntu-bug /var/crash/_usr_libexec_ibus-ui-gtk3.1000.crash

  luigi@l-g905:~$ sudo cat /var/lib/whoopsie/whoopsie-id
  
7a0c123f5172023e795f73a584fa57e5efd8e12b9c45fd40142d884f4260a9abe2b1d30152e6d8f6c7cbc21190d542ebda3b4cfc316047ba6be306793ee2fe80

  
https://errors.ubuntu.com/user/7a0c123f5172023e795f73a584fa57e5efd8e12b9c45fd40142d884f4260a9abe2b1d30152e6d8f6c7cbc21190d542ebda3b4cfc316047ba6be306793ee2fe80:
 No such file or directory
  -

  
  This upload fialure seemed confirmed when in: 
https://answers.launchpad.net/ubuntu/+questions?
  a search found no Questions matching "ibus-ui-gtk3" for Ubuntu
  "ibus-ui-gtk3" is not mentioned in the release notes bugs section.

  In
  https://errors.ubuntu.com/?release=Ubuntu%2023.10=day
  text Searches for _usr_libexec_ibus-ui-gtk3 and the "Whoopsie-id" above both 
returned "phrase not found"

  I reproduced the executable failure using Terminal with these results
  --
  ~$ /usr/libexec/ibus-ui-gtk3 --enable-wayland-im --exec-daemon --daemon-args 
--xim\ --panel\ disable

  Returns:
  ~$ /usr/libexec/ibus-ui-gtk3 --enable-wayland-im --exec-daemon --daemon-args 
--xim\ --panel\ disable

  (ibus-ui-gtk3:9353): IBUS-CRITICAL **: 23:11:04.233: string_substring:
  assertion '(offset + len) <= string_length' failed

  (ibus-ui-gtk3:9353): IBUS-CRITICAL **: 23:11:04.233: string_substring:
  assertion '(offset + len) <= string_length' failed

  ** (ibus-ui-gtk3:9353): ERROR **: 23:11:04.236: No input_method global

  Trace/breakpoint trap (core dumped)
  -

  I am attaching the _usr_libexec_ibus-ui-gtk3.1000.crash file
  /var/crash/ _ust_libexec_ibus-ui-gtk3.1000.crash (3.1 MiB - 1144 lines
  - modified on 11/13/23 9:07 PM - US-ASCII)

  Platform Information 
  Operating System: Ubuntu Studio 23.10
  KDE Plasma Version:   5.27.8
  KDE Frameworks Version:   5.110.0
  Qt Version:   5.15.10
  Kernel Version:   6.5.0-10-lowlatency (64-bit)
  Graphics Platform:Wayland
  Processors:   24 × AMD Ryzen 9 7900X 12-Core Processor
  Memory:   31.0 GiB of RAM
  Graphics Processor:   NV172
  Manufacturer: MicroElectronics
  Product Name: G905
  System Version:   1.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/2043442/+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 2019137] Re: gnome-software should (?) be separated from the packagekit

[Jeremy Bícha]

Yes, I agree that this is a valid request and should be looked into.

It will need coordination with the Ubuntu desktop flavors that are not
currently using Ubuntu's App Center.

Also, this is the kind of work that is done in the development version
of Ubuntu (currently Noble Numbat) and is unlikely to affect existing
stable Ubuntu releases like 22.04 LTS.

** Changed in: gnome-software (Ubuntu)
   Status: Confirmed => Triaged

** Changed in: gnome-software (Ubuntu)
   Importance: Undecided => Low

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

Title:
  gnome-software should (?) be separated from the packagekit

Status in gnome-software package in Ubuntu:
  Triaged

Bug description:
  Given that the Snap Store is currently the default in Ubuntu instead
  of GNOME Software, the only reason GNOME Software (along with the Snap
  Store) can be installed is to support Flatpak applications.

  In the current instance, if you want to add flatpak support, GNOME
  Software is installed with both the apt packagekit add-on and the
  flatpak plugin, which is duplication of work (Software Updater already
  works on updates, and Snap Store works on showing deb apps).

  And since the future app store explicitly refuses [1], [2] to support
  flatpak applications, users who need this package format will be
  forced to put GNOME Software with everything I pointed out above.

  Therefore, it would be very nice if the developers removed the
  packagekit add-on from the "gnome-software part" and made it a "plug-
  in for gnome-software".

  I, unfortunately, have no such experience with packaging deb packages
  at the moment, and it turns out that it will obviously be necessary to
  work out both the code part (which, as far as I can see, won't be very
  difficult [3]), as well as the part where we will have to figure out
  where and how to insert the plugin as mandatory (for example, when the
  user completely gives up on snap packages) and as optional (because
  the Snap Store already stands).

  Also, let me know if this needs to be sent to upstream (Debian) instead of 
here.
  
---
  1. https://github.com/ubuntu-flutter-community/software/issues/126
  2. https://github.com/ubuntu-flutter-community/software/issues/30
  3. https://build.opensuse.org/request/show/1031279

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/2019137/+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 2043492] [NEW] Installed 23.10 on Huawei 16s. Speakers don't work. When I plug in headphones, the speakers work. the operating system seems to have the two switched. Also, on g

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

No further information.

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: alsa-base 1.0.25+dfsg-0ubuntu7
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  noe2350 F pipewire
  noe2357 F wireplumber
 /dev/snd/seq:noe2350 F pipewire
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Nov 14 16:42:30 2023
InstallationDate: Installed on 2023-11-01 (13 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1)
PackageArchitecture: all
ProcEnviron:
 LANG=en_US.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: 11/08/2022
dmi.bios.release: 1.23
dmi.bios.vendor: HUAWEI
dmi.bios.version: 1.23
dmi.board.asset.tag: N/A
dmi.board.name: CREF-XX-PCB
dmi.board.vendor: HUAWEI
dmi.board.version: M1010
dmi.chassis.asset.tag: N/A
dmi.chassis.type: 10
dmi.chassis.vendor: HUAWEI
dmi.chassis.version: M1010
dmi.ec.firmware.release: 1.23
dmi.modalias: 
dmi:bvnHUAWEI:bvr1.23:bd11/08/2022:br1.23:efr1.23:svnHUAWEI:pnCREF-XX:pvrM1010:rvnHUAWEI:rnCREF-XX-PCB:rvrM1010:cvnHUAWEI:ct10:cvrM1010:skuC100:
dmi.product.family: MateBook
dmi.product.name: CREF-XX
dmi.product.sku: C100
dmi.product.version: M1010
dmi.sys.vendor: HUAWEI

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


** Tags: amd64 apport-bug mantic wayland-session
-- 
Installed 23.10 on Huawei 16s.  Speakers don't work.  When I plug in 
headphones, the speakers work.  the operating system seems to have the two 
switched.  Also, on google meets, it cannot find a sound device.
https://bugs.launchpad.net/bugs/2043492
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 2043442] [NEW] /usr/libexec/ibus-ui-gtk3 --enable-wayland-im system freezes

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Apport captured a system freeze [crash] which required a hard reboot.
However I could not confirm that the report was successfully uploaded.

The /var/log/apport.log entry is as follows.

ERROR: apport (pid 17772) 2023-11-13 17:17:02,197: this executable already 
crashed 2 times, ignoring
INFO: apport (pid 27019) 2023-11-13 21:07:39,820: called for pid 17786, signal 
11, core limit 0, dump mode 1
INFO: apport (pid 27019) 2023-11-13 21:07:39,821: executable: 
/usr/libexec/ibus-ui-gtk3 (command line "/usr/libexec/ibus-ui-gtk3 
--enable-wayland-im --exec-daemon --daemon-args --xim\ --panel\ disable")
ERROR: apport (pid 27019) 2023-11-13 21:07:40,821: gdbus call error: Error: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.gnome.SessionManager was not provided by any .service files

INFO: apport (pid 27019) 2023-11-13 21:07:42,687: wrote report 
/var/crash/_usr_libexec_ibus-ui-gtk3.1000.crash
INFO: apport (pid 29410) 2023-11-13 21:38:11,084: called for pid 27746, signal 
11, core limit 0, dump mode 1
INFO: apport (pid 29410) 2023-11-13 21:38:11,085: executable: 
/usr/libexec/ibus-ui-gtk3 (command line "/usr/libexec/ibus-ui-gtk3 
--enable-wayland-im --exec-daemon --daemon-args --xim\ --panel\ disable")
ERROR: apport (pid 29410) 2023-11-13 21:38:12,085: gdbus call error: Error: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.gnome.SessionManager was not provided by any .service files

Note:The last line may explain why I could not verify the file
upload when I performed the following proceedure per:
https://help.ubuntu.com/community/ReportingBugs

---
luigi@l-g905:~$ ubuntu-bug /var/crash/_usr_libexec_ibus-ui-gtk3.1000.crash

luigi@l-g905:~$ sudo cat /var/lib/whoopsie/whoopsie-id
7a0c123f5172023e795f73a584fa57e5efd8e12b9c45fd40142d884f4260a9abe2b1d30152e6d8f6c7cbc21190d542ebda3b4cfc316047ba6be306793ee2fe80

https://errors.ubuntu.com/user/7a0c123f5172023e795f73a584fa57e5efd8e12b9c45fd40142d884f4260a9abe2b1d30152e6d8f6c7cbc21190d542ebda3b4cfc316047ba6be306793ee2fe80:
 No such file or directory
-


This upload fialure seemed confirmed when in: 
https://answers.launchpad.net/ubuntu/+questions?
a search found no Questions matching "ibus-ui-gtk3" for Ubuntu
"ibus-ui-gtk3" is not mentioned in the release notes bugs section.

In
https://errors.ubuntu.com/?release=Ubuntu%2023.10=day
text Searches for _usr_libexec_ibus-ui-gtk3 and the "Whoopsie-id" above both 
returned "phrase not found"

I reproduced the executable failure using Terminal with these results
--
~$ /usr/libexec/ibus-ui-gtk3 --enable-wayland-im --exec-daemon --daemon-args 
--xim\ --panel\ disable

Returns:
~$ /usr/libexec/ibus-ui-gtk3 --enable-wayland-im --exec-daemon --daemon-args 
--xim\ --panel\ disable

(ibus-ui-gtk3:9353): IBUS-CRITICAL **: 23:11:04.233: string_substring:
assertion '(offset + len) <= string_length' failed

(ibus-ui-gtk3:9353): IBUS-CRITICAL **: 23:11:04.233: string_substring:
assertion '(offset + len) <= string_length' failed

** (ibus-ui-gtk3:9353): ERROR **: 23:11:04.236: No input_method global

Trace/breakpoint trap (core dumped)
-

I am attaching the _usr_libexec_ibus-ui-gtk3.1000.crash file /var/crash/
_ust_libexec_ibus-ui-gtk3.1000.crash (3.1 MiB - 1144 lines - modified on
11/13/23 9:07 PM - US-ASCII)

Platform Information 
Operating System: Ubuntu Studio 23.10
KDE Plasma Version: 5.27.8
KDE Frameworks Version: 5.110.0
Qt Version: 5.15.10
Kernel Version: 6.5.0-10-lowlatency (64-bit)
Graphics Platform:  Wayland
Processors: 24 × AMD Ryzen 9 7900X 12-Core Processor
Memory: 31.0 GiB of RAM
Graphics Processor: NV172
Manufacturer:   MicroElectronics
Product Name:   G905
System Version: 1.0

** Affects: ibus (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport bot-comment crash failure halt mantic system upload
-- 
/usr/libexec/ibus-ui-gtk3 --enable-wayland-im system freezes
https://bugs.launchpad.net/bugs/2043442
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to ibus 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 2043487] Re: Nautilus Freezing

[Sebastien Bacher]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please try to obtain a backtrace following the
instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload
the backtrace (as an attachment) to the bug report. This will greatly
help us in tracking down your problem.

Is there any warning printed in the journal?


** Changed in: nautilus (Ubuntu)
   Status: New => Incomplete

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

Title:
  Nautilus Freezing

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
   I usually organize my files by opening two windows in Nautilus and
  transferring the files from one window to the next. But about every
  15/30 mins or so, the receiving folder will freeze; forcing me to
  manually from close nautilus from the program manager and restart the
  program.

  The weird thing is. It’s only one folder freezing, with any other
  active instance of the program running normally. It always freezes
  between transfers. I move one item, but the next will not transfer.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: nautilus 1:44.2.1-0ubuntu1
  ProcVersionSignature: Ubuntu 6.2.0-36.37-generic 6.2.16
  Uname: Linux 6.2.0-36-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 14 10:07:31 2023
  GsettingsChanges:
   b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'large'"
   b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'large'"
   b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true'
   b'org.gnome.nautilus.preferences' b'search-filter-time-type' b"'created'"
   b'org.gnome.nautilus.window-state' b'initial-size' b'(960, 1053)'
  InstallationDate: Installed on 2023-01-06 (312 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to lunar on 2023-07-09 (128 days ago)
  usr_lib_nautilus:
   file-roller   43.0-1
   nautilus-extension-gnome-terminal 3.48.0-1ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2043487/+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 2019137] Re: gnome-software should (?) be separated from the packagekit

[Milachew]

Part of the work has already been done here:
https://discourse.ubuntu.com/t/ideas-for-improving-the-experience-with-
flatpak-packages-in-ubuntu/39643/16?u=milachew

Also, after studying the patch, it will be better to understand what I
was trying to convey.

(my idea was to separate, not remove, packagekit/dpkg from GNOME
Software and offer to install it only when it is really needed, and not
always when GNOME Software is installed)

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

Title:
  gnome-software should (?) be separated from the packagekit

Status in gnome-software package in Ubuntu:
  Confirmed

Bug description:
  Given that the Snap Store is currently the default in Ubuntu instead
  of GNOME Software, the only reason GNOME Software (along with the Snap
  Store) can be installed is to support Flatpak applications.

  In the current instance, if you want to add flatpak support, GNOME
  Software is installed with both the apt packagekit add-on and the
  flatpak plugin, which is duplication of work (Software Updater already
  works on updates, and Snap Store works on showing deb apps).

  And since the future app store explicitly refuses [1], [2] to support
  flatpak applications, users who need this package format will be
  forced to put GNOME Software with everything I pointed out above.

  Therefore, it would be very nice if the developers removed the
  packagekit add-on from the "gnome-software part" and made it a "plug-
  in for gnome-software".

  I, unfortunately, have no such experience with packaging deb packages
  at the moment, and it turns out that it will obviously be necessary to
  work out both the code part (which, as far as I can see, won't be very
  difficult [3]), as well as the part where we will have to figure out
  where and how to insert the plugin as mandatory (for example, when the
  user completely gives up on snap packages) and as optional (because
  the Snap Store already stands).

  Also, let me know if this needs to be sent to upstream (Debian) instead of 
here.
  
---
  1. https://github.com/ubuntu-flutter-community/software/issues/126
  2. https://github.com/ubuntu-flutter-community/software/issues/30
  3. https://build.opensuse.org/request/show/1031279

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/2019137/+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 2039104] Re: ubuntu-settings must drop ubuntu-raspi-settings* from debian/control

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-settings - 23.10.6

---
ubuntu-settings (23.10.6) noble; urgency=medium

  * Remove ubuntu-raspi-settings{,-desktop,-server} packages; these are now
produced by the ubuntu-raspi-settings package (LP: #2039104)

 -- Dave Jones   Mon, 06 Nov 2023 09:21:35
+

** Changed in: ubuntu-settings (Ubuntu)
   Status: New => Fix Released

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

Title:
  ubuntu-settings must drop ubuntu-raspi-settings* from debian/control

Status in ubuntu-settings package in Ubuntu:
  Fix Released
Status in ubuntu-settings source package in Mantic:
  New

Bug description:
  In response to LP: #2038964 and due to the timing we have forked
  ubuntu-raspi-settings into a separate source package.

  ubuntu-settings must therefore be updated to drop ubuntu-raspi-
  settings* from debian/control as otherwise binary builds of the
  package will be rejected by the archive (if the version number is <=
  23.10.6) or will wrongly supersede the fixes that have just been
  uploaded to mantic (if the version number is > 23.10.6).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2039104/+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 2043487] [NEW] Nautilus Freezing

[No]

Public bug reported:

 I usually organize my files by opening two windows in Nautilus and
transferring the files from one window to the next. But about every
15/30 mins or so, the receiving folder will freeze; forcing me to
manually from close nautilus from the program manager and restart the
program.

The weird thing is. It’s only one folder freezing, with any other active
instance of the program running normally. It always freezes between
transfers. I move one item, but the next will not transfer.

ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: nautilus 1:44.2.1-0ubuntu1
ProcVersionSignature: Ubuntu 6.2.0-36.37-generic 6.2.16
Uname: Linux 6.2.0-36-generic x86_64
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Nov 14 10:07:31 2023
GsettingsChanges:
 b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'large'"
 b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'large'"
 b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true'
 b'org.gnome.nautilus.preferences' b'search-filter-time-type' b"'created'"
 b'org.gnome.nautilus.window-state' b'initial-size' b'(960, 1053)'
InstallationDate: Installed on 2023-01-06 (312 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
SourcePackage: nautilus
UpgradeStatus: Upgraded to lunar on 2023-07-09 (128 days ago)
usr_lib_nautilus:
 file-roller   43.0-1
 nautilus-extension-gnome-terminal 3.48.0-1ubuntu1

** Affects: nautilus (Ubuntu)
 Importance: Undecided
 Status: New


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

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

Title:
  Nautilus Freezing

Status in nautilus package in Ubuntu:
  New

Bug description:
   I usually organize my files by opening two windows in Nautilus and
  transferring the files from one window to the next. But about every
  15/30 mins or so, the receiving folder will freeze; forcing me to
  manually from close nautilus from the program manager and restart the
  program.

  The weird thing is. It’s only one folder freezing, with any other
  active instance of the program running normally. It always freezes
  between transfers. I move one item, but the next will not transfer.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: nautilus 1:44.2.1-0ubuntu1
  ProcVersionSignature: Ubuntu 6.2.0-36.37-generic 6.2.16
  Uname: Linux 6.2.0-36-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 14 10:07:31 2023
  GsettingsChanges:
   b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'large'"
   b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'large'"
   b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true'
   b'org.gnome.nautilus.preferences' b'search-filter-time-type' b"'created'"
   b'org.gnome.nautilus.window-state' b'initial-size' b'(960, 1053)'
  InstallationDate: Installed on 2023-01-06 (312 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to lunar on 2023-07-09 (128 days ago)
  usr_lib_nautilus:
   file-roller   43.0-1
   nautilus-extension-gnome-terminal 3.48.0-1ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2043487/+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 1973084] Re: transmission-daemon high RAM usage

[Paride Legovini]

Hi Marius, Andrey, Lem and other affected users. Please consider testing
the package from the PPA that Andreas prepared. This definitely looks
like SRU material, but we need some kind of verification before
proceeding. Thanks!

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

Title:
  transmission-daemon high RAM usage

Status in transmission package in Ubuntu:
  Confirmed
Status in transmission source package in Jammy:
  New
Status in transmission source package in Lunar:
  New
Status in transmission package in Debian:
  New

Bug description:
  Transmission uses a lot of RAM in ubuntu 22.04 server (arm64) runnign
  on a Raspberry Pi 4.

  It "eats" RAM and the RAM usage grows each hour until it crashes the
  system.

  I sideloaded transmission-daemon and its dependancies from debian 11
  (arm64) locked the packages so apt won't update them and, ever since,
  this issue hasn't happened.

  
  Description:Ubuntu 22.04 LTS
  Release:22.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1973084/+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 2043306] Re: Sync tepl 6.8.0-2 (universe) from Debian unstable (main)

[Simon Quigley]

This bug was fixed in the package tepl - 6.8.0-2
Sponsored for Hans Joachim Desserud (hjd)

---
tepl (6.8.0-2) unstable; urgency=medium

  * Stop using debian/control.in
  * Drop X-Ubuntu-Use-Langpack from debian/control
  * Drop the now unnecessary dh-sequence-gnome from Build-Depends

 -- Amin Bandali   Wed, 08 Nov 2023 16:43:37 +0200

tepl (6.8.0-1) experimental; urgency=medium

  * New upstream release
  * debian/control.in: Add myself to uploaders
  * debian/control.in: Adjust dependencies according to upstream
  * debian/control.in: Update standards version to 4.6.2, no changes needed
  * debian/control.in: Rename library package to match soversion bump
  * debian/libtepl-6-4.symbols: Update symbols following upstream
  * debian/copyright: Bump copyright years and list contributors to
debian/* thus far

 -- Amin Bandali   Wed, 18 Oct 2023 16:05:30 -0400

** Changed in: tepl (Ubuntu)
   Status: New => Fix Released

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

Title:
  Sync tepl 6.8.0-2 (universe) from Debian unstable (main)

Status in tepl package in Ubuntu:
  Fix Released

Bug description:
  Please sync tepl 6.8.0-2 (universe) from Debian unstable (main)

  Explanation of the Ubuntu delta and why it can be dropped:
* No change upload to trigger a translations import on launchpad,
  the template was not correctly set for the new ABI version and the
  existing translations weren't imported in the previous upload
* No change upload to trigger a translations import on launchpad,
  the template was not correctly set for the new ABI version and the
  existing translations weren't imported in the previous upload
* debian/control.in:
  - remove 'X-Ubuntu-Use-Langpack: yes', the template name changed and the
one wasn't accepted on launchpad so the translations are missing from
the langpacks, we aren't going to get a respin of those for lunar so
go back to have the translations included in the deb. Resolve the
issue when some strings in gedit show untranslated (lp: #2016923)
* Rebuild against latest icu
* Rebuild against latest icu

  X-Ubuntu-Use-Langpack was removed from the control file in Debian too
  
https://salsa.debian.org/gnome-team/tepl/-/commit/f550e49edab938302eae6c2bb582b51148935e1d
  And control.in was dropped which is why the above commit only lists changes 
in one file
  
https://salsa.debian.org/gnome-team/tepl/-/commit/50b77ecd10434a97307886aadb20d755b8c3ab54

  
  Changelog entries since current noble version 6.4.0-7ubuntu2:

  tepl (6.8.0-2) unstable; urgency=medium

* Stop using debian/control.in
* Drop X-Ubuntu-Use-Langpack from debian/control
* Drop the now unnecessary dh-sequence-gnome from Build-Depends

   -- Amin Bandali   Wed, 08 Nov 2023 16:43:37 +0200

  tepl (6.8.0-1) experimental; urgency=medium

* New upstream release
* debian/control.in: Add myself to uploaders
* debian/control.in: Adjust dependencies according to upstream
* debian/control.in: Update standards version to 4.6.2, no changes needed
* debian/control.in: Rename library package to match soversion bump
* debian/libtepl-6-4.symbols: Update symbols following upstream
* debian/copyright: Bump copyright years and list contributors to
  debian/* thus far

   -- Amin Bandali   Wed, 18 Oct 2023 16:05:30 -0400

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tepl/+bug/2043306/+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 2043472] Re: "Files" is not responding this issue occurring again and again , when i tried renaming multiples files then i can see this issue and randomly also occuring

[Sebastien Bacher]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please try to obtain a backtrace following the
instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload
the backtrace (as an attachment) to the bug report. This will greatly
help us in tracking down your problem.

Is there any warning printed in the journal?

** Changed in: nautilus (Ubuntu)
   Status: New => Incomplete

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

Title:
  "Files" is not responding this issue occurring again and again , when
  i tried renaming multiples files then i can see this issue and
  randomly also occuring

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  "Files" is not responding this issue occurring again and again , when
  i tried renaming multiples files then i can see this issue and
  randomly also occuring

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: nautilus 1:42.6-0ubuntu1
  ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-36-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 14 18:11:12 2023
  GsettingsChanges:
   b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'large'"
   b'org.gnome.nautilus.window-state' b'maximized' b'true'
  InstallationDate: Installed on 2023-06-04 (163 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:
   evince42.3-0ubuntu3
   file-roller   3.42.0-1
   nautilus-extension-gnome-terminal 3.44.0-1ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2043472/+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 1516025] Re: Realtek ALC3661 Alienware14 / Soundoutput / Jack

[kakarot23]

Investing basics lay the foundation for individuals seeking to navigate
the world of financial markets and wealth accumulation. At its core,
investing involves deploying capital with the expectation of generating
returns over time. https://thefinancialappetite.net/category/getting-
started/investing-basics/

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

Title:
  Realtek ALC3661 Alienware14 / Soundoutput / Jack

Status in ALSA driver:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  When watching the following video (but also audio from other programs) with 
the volume at 100%, the audio loudness is lower in comparison to the same audio 
being played at 100% in Windows 10:
  https://www.youtube.com/watch?v=YQHsXMglC9A

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-18-generic 4.2.0-18.22
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  imran  1619 F pulseaudio
   /dev/snd/controlC1:  imran  1619 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Nov 13 18:08:07 2015
  HibernationDevice: RESUME=UUID=2401d43e-85ec-4c88-81c1-c597086504a1
  InstallationDate: Installed on 2015-11-07 (5 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Alienware Alienware 14
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic 
root=UUID=a534221a-37cb-4092-8ce2-934940eede6d ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-18-generic N/A
   linux-backports-modules-4.2.0-18-generic  N/A
   linux-firmware1.149.1
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/23/2014
  dmi.bios.vendor: Alienware
  dmi.bios.version: A09
  dmi.board.name: 07MJ2Y
  dmi.board.vendor: Alienware
  dmi.board.version: A01
  dmi.chassis.type: 8
  dmi.chassis.vendor: Alienware
  dmi.chassis.version: A09
  dmi.modalias: 
dmi:bvnAlienware:bvrA09:bd04/23/2014:svnAlienware:pnAlienware14:pvrA09:rvnAlienware:rn07MJ2Y:rvrA01:cvnAlienware:ct8:cvrA09:
  dmi.product.name: Alienware 14
  dmi.product.version: A09
  dmi.sys.vendor: Alienware

To manage notifications about this bug go to:
https://bugs.launchpad.net/alsa-driver/+bug/1516025/+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 2043472] [NEW] "Files" is not responding this issue occurring again and again , when i tried renaming multiples files then i can see this issue and randomly also occuring

[Sahil]

Public bug reported:

"Files" is not responding this issue occurring again and again , when i
tried renaming multiples files then i can see this issue and randomly
also occuring

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: nautilus 1:42.6-0ubuntu1
ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16
Uname: Linux 6.2.0-36-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Nov 14 18:11:12 2023
GsettingsChanges:
 b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'large'"
 b'org.gnome.nautilus.window-state' b'maximized' b'true'
InstallationDate: Installed on 2023-06-04 (163 days ago)
InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_nautilus:
 evince42.3-0ubuntu3
 file-roller   3.42.0-1
 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1

** Affects: nautilus (Ubuntu)
 Importance: Undecided
 Status: New


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

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

Title:
  "Files" is not responding this issue occurring again and again , when
  i tried renaming multiples files then i can see this issue and
  randomly also occuring

Status in nautilus package in Ubuntu:
  New

Bug description:
  "Files" is not responding this issue occurring again and again , when
  i tried renaming multiples files then i can see this issue and
  randomly also occuring

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: nautilus 1:42.6-0ubuntu1
  ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-36-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 14 18:11:12 2023
  GsettingsChanges:
   b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'large'"
   b'org.gnome.nautilus.window-state' b'maximized' b'true'
  InstallationDate: Installed on 2023-06-04 (163 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:
   evince42.3-0ubuntu3
   file-roller   3.42.0-1
   nautilus-extension-gnome-terminal 3.44.0-1ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2043472/+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 2043255] Re: Wayland user session terminates when screen is disabled on inactivity

[Timo Aaltonen]

** Package changed: wayland (Ubuntu) => mutter (Ubuntu)

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

Title:
  Wayland user session terminates when screen is disabled on inactivity

Status in mutter package in Ubuntu:
  New

Bug description:
  Reproducibly, the user is logged out the moment the screen gets
  disabled due to inactivity. Can be worked around by disabling the
  "screen disabling on inactivity" feature in the system settings.

  Issue started after upgrade from 23.04 to 23.10. Wayland is used.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Nov 11 09:21:02 2023
  DistUpgraded: 2023-11-03 18:23:57,803 DEBUG icon theme changed, re-reading
  DistroCodename: mantic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Lucienne [1002:164c] (rev c1) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo Lucienne [17aa:5097]
  InstallationDate: Installed on 2021-08-27 (806 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-10-generic 
root=UUID=86fa7801-2441-4de0-bdff-28c460a157ee ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to mantic on 2023-11-03 (8 days ago)
  dmi.bios.date: 05/17/2021
  dmi.bios.release: 1.6
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1OET27W (1.06 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20YHS00A00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.6
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1OET27W(1.06):bd05/17/2021:br1.6:efr1.6:svnLENOVO:pn20YHS00A00:pvrThinkPadE15Gen3:rvnLENOVO:rn20YHS00A00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20YH_BU_Think_FM_ThinkPadE15Gen3:
  dmi.product.family: ThinkPad E15 Gen 3
  dmi.product.name: 20YHS00A00
  dmi.product.sku: LENOVO_MT_20YH_BU_Think_FM_ThinkPad E15 Gen 3
  dmi.product.version: ThinkPad E15 Gen 3
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.115-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2043255/+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 2043400] Re: xrandr can't set default resolution

[Timo Aaltonen]

** Package changed: x11-xserver-utils (Ubuntu) => nvidia-graphics-
drivers-535 (Ubuntu)

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

Title:
  xrandr can't set default resolution

Status in nvidia-graphics-drivers-535 package in Ubuntu:
  New

Bug description:
  sometimes when i play with wine and various old programs application fails 
and keeps reolution which it set
  when it happends, before ubuntu 23.10 i was able to launch xrandr -s 
1680x1050 and had my original resolution back

  after upgrade to 23.10 it doesn't work
  xrandr -q lists correct resolution as first one

  Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 32767 x 32767
  DP-0 disconnected (normal left inverted right x axis y axis)
  DP-1 disconnected (normal left inverted right x axis y axis)
  HDMI-0 connected primary 1920x1080+0+0 (normal left inverted right x axis y 
axis) 480mm x 300mm
 1680x1050 59.95 +
 1920x1080 59.94* 
 1280x1024 75.0260.02  
 1280x960  60.00  
 1280x720  60.0059.94  
 1152x864  75.00  
 1024x768  75.0370.0760.00  
 800x600   75.0072.1960.3256.25  
 640x480   75.0072.8159.9459.93  
  DP-2 disconnected (normal left inverted right x axis y axis)
  DP-3 disconnected (normal left inverted right x axis y axis)
  DP-4 disconnected (normal left inverted right x axis y axis)
  DP-5 disconnected (normal left inverted right x axis y axis)

  but attempt to set it fails
  xrandr -s 1680x1050
  Size 1680x1050 not found in available modes

  i can set all other resolutions (this is why current one listed is
  1980x1080), except the one i need

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: x11-xserver-utils 7.7+9build1
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  535.129.03  Thu Oct 19 
18:56:32 UTC 2023
   GCC version:
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 13 16:52:28 2023
  DistUpgraded: 2023-11-03 12:42:15,779 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: mantic
  DistroVariant: ubuntu
  DkmsStatus: nvidia/535.129.03, 6.5.0-10-generic, x86_64: installed (WARNING! 
Diff between built and installed module!) (WARNING! Diff between built and 
installed module!) (WARNING! Diff between built and installed module!) 
(WARNING! Diff between built and installed module!) (WARNING! Diff between 
built and installed module!)
  GraphicsCard:
   NVIDIA Corporation TU104 [GeForce RTX 2070 SUPER] [10de:1e84] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] TU104 [GeForce RTX 
2070 SUPER] [1462:c729]
  InstallationDate: Installed on 2022-12-23 (325 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-10-generic 
root=UUID=d944c09b-3160-4d61-9aa0-32372d3381dd ro quiet splash vt.handoff=7
  SourcePackage: x11-xserver-utils
  UpgradeStatus: Upgraded to mantic on 2023-11-03 (10 days ago)
  dmi.bios.date: 10/27/2022
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2806
  dmi.board.asset.tag: Default string
  dmi.board.name: TUF GAMING B550-PLUS WIFI II
  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.:bvr2806:bd10/27/2022:br5.17:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGB550-PLUSWIFIII: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: ASUS
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.115-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: 

[Desktop-packages] [Bug 1930387] Re: The system voice doesn't change after disable "Over-Amplification"

[Bug Watch Updater]

** Changed in: gnome-settings-daemon
   Status: Unknown => New

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

Title:
  The system voice doesn't change after disable "Over-Amplification"

Status in GNOME Settings Daemon:
  New
Status in OEM Priority Project:
  New
Status in gnome-control-center package in Ubuntu:
  Invalid
Status in gnome-settings-daemon package in Ubuntu:
  New

Bug description:
  [Summary]
  The system voice doesn't change after disable "Over-Amplification"

  [Reproduce]
  1. Boot into the system.
  2. Launch Settings > Sound
  3. Enable "Over-Amplification"
  4. Maximize the system Volume
  5. Disable "Over-Amplification"

  [Expected result]
  The system voice can become lower.

  [Actual result]
  The system volume showed as 100 but the voice doesn't become lower.

  [Fail Rate]
  100%

  [Additional information]
  Ubuntu Version: 20.04.2 LTS
  Image: sutton-newell-focal-amd64-20210414-220
  gnome-control-center: 1:3.36.5-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-settings-daemon/+bug/1930387/+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 2038727] Re: Chromium snap theme parsing error

[Nathan Teodosio]

** Changed in: chromium-browser (Ubuntu)
   Status: Fix Committed => 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/2038727

Title:
  Chromium snap theme parsing error

Status in chromium-browser package in Ubuntu:
  Fix Released

Bug description:
  Chromium Version 117.0.5938.149 (Official Build) snap (64-bit) not
  following my GTK theme.  Starting the Chromium snap from the terminal
  yields a theme parsing error:

  (chrome:95638): Gtk-WARNING **: 11:01:12.220: Theme parsing error:
  gtk.css:1:0: Failed to import: Error opening file
  /home/aej/.local/share/themes/Adwaita_modified/gtk-3.0/gtk.css:
  Permission denied

  Previous versions of the Chromium snap have not had this problem.
  Debian 11 + XFCE.  I have been running the chromium snap for about two
  years without an issue like this on this system.  I have reverted to
  the previous version of the chromium snap.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2038727/+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 1849346] Re: [snap] kerberos GSSAPI no longer works after deb->snap transition

[Vegard Søbstad Alsli]

Any updates on this?

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

Title:
  [snap] kerberos GSSAPI no longer works after deb->snap transition

Status in Mozilla Firefox:
  New
Status in snapd:
  New
Status in chromium-browser package in Ubuntu:
  Triaged
Status in firefox package in Ubuntu:
  Triaged

Bug description:
  I configure AuthServerWhitelist as documented:

  https://www.chromium.org/developers/design-documents/http-
  authentication

  and can see my whitelisted domains in chrome://policy/

  but websites that used to work with SPNEGO/GSSAPI/kerberos no longer
  work. I'm guessing the snap needs some sort of permission to use the
  kerberos ticket cache (or the plumbing to do so doesn't exist...).

  I can confirm that Chrome has the desired behavior.

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1849346/+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 2043462] [NEW] after the sleeping mod, the login process takes a loooong time. Also, pages get freezed.

[Suren Nersisyan]

Public bug reported:

after login one of the monitors is not turning on, in case the monitor turns 
on, it looks like fizzed. 
it take a looong time to get PC work correctly.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42.9-0ubuntu2
ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16
Uname: Linux 6.2.0-36-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Nov 14 14:55:52 2023
DisplayManager: gdm3
InstallationDate: Installed on 2023-03-03 (255 days ago)
InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
RelatedPackageVersions: mutter-common 42.9-0ubuntu5
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug jammy third-party-packages

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

Title:
  after the sleeping mod, the login process takes a lng time. Also,
  pages get freezed.

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  after login one of the monitors is not turning on, in case the monitor turns 
on, it looks like fizzed. 
  it take a looong time to get PC work correctly.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.9-0ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-36-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 14 14:55:52 2023
  DisplayManager: gdm3
  InstallationDate: Installed on 2023-03-03 (255 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  RelatedPackageVersions: mutter-common 42.9-0ubuntu5
  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/2043462/+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 1884759] Re: [snap] U2f yubikey not recognized until unplugged and plugged back in

[Nathan Teodosio]

Thanks, Alex! Requested at https://forum.snapcraft.io/t/chromium-
hardware-observe-auto-connect-request.

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

Title:
  [snap] U2f yubikey not recognized until unplugged and plugged back in

Status in chromium-browser package in Ubuntu:
  Fix Committed

Bug description:
  I was previously using u2f from yubikey in chromium snap, but now it doesn't 
work.
  No apparmor deny in dmesg (except accessing bluez), u2f slot is conneced.
  U2f still works in firefox installed as deb.

  # snap connections chromium | grep u2f
  u2f-devices   chromium:u2f-devices   :u2f-devices 
   manual

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1884759/+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 1930387] Re: The system voice doesn't change after disable "Over-Amplification"

[Andy Chi]

** Also affects: gnome-settings-daemon via
   https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues/767
   Importance: Unknown
   Status: Unknown

** No longer affects: gnome-control-center

** Also affects: gnome-settings-daemon (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: gnome-control-center (Ubuntu)
   Status: Triaged => Invalid

** Changed in: oem-priority
 Assignee: (unassigned) => Arturr (artur)

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

Title:
  The system voice doesn't change after disable "Over-Amplification"

Status in GNOME Settings Daemon:
  Unknown
Status in OEM Priority Project:
  New
Status in gnome-control-center package in Ubuntu:
  Invalid
Status in gnome-settings-daemon package in Ubuntu:
  New

Bug description:
  [Summary]
  The system voice doesn't change after disable "Over-Amplification"

  [Reproduce]
  1. Boot into the system.
  2. Launch Settings > Sound
  3. Enable "Over-Amplification"
  4. Maximize the system Volume
  5. Disable "Over-Amplification"

  [Expected result]
  The system voice can become lower.

  [Actual result]
  The system volume showed as 100 but the voice doesn't become lower.

  [Fail Rate]
  100%

  [Additional information]
  Ubuntu Version: 20.04.2 LTS
  Image: sutton-newell-focal-amd64-20210414-220
  gnome-control-center: 1:3.36.5-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-settings-daemon/+bug/1930387/+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