[Desktop-packages] [Bug 1963628] Re: Force IIO_SENSOR_PROXY_TYPE to iio-buffer-als for some Dell models

[Yao Wei]

I'd like to add another debdiff to jammy which resolves the issue from
the patch upstream

Upstream MR: https://gitlab.freedesktop.org/hadess/iio-sensor-
proxy/-/merge_requests/355

** Patch added: "iio-sensor-proxy_3.3-0ubuntu6.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/iio-sensor-proxy/+bug/1963628/+attachment/5570270/+files/iio-sensor-proxy_3.3-0ubuntu6.debdiff

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

Title:
  Force IIO_SENSOR_PROXY_TYPE to iio-buffer-als for some Dell models

Status in OEM Priority Project:
  New
Status in iio-sensor-proxy package in Ubuntu:
  Fix Committed

Bug description:
  We are encountering issues, that when enabling some Dell laptops, the readings
  from iio-poll-als are unstable, or could freeze on certain value.  On these
  systems they have ENV{IIO_SENSOR_PROXY_TYPE}="iio-poll-als iio-buffer-als", 
and
  removing iio-poll-als makes reading stable.

  This adds workaround to the affected Dell laptop models which may equip with
  ALS.

  [Impact]

   * Only models matching the same device BIOS IDs are affected.

  [Test Plan]

   * Pick devices which BIOS IDs are listed in the patch, and test
  whether it's ambient light sensors are working properly without
  unexpected brightness flickers.

  [Where problems could occur]

   * Machines matching the same BIOS ID, either having ALS built-in or
  not, but attached ambient light sensors externally (for example,
  ColorHug ALS) might experience failures.

  [Other Info]
   
   * Upstream merge request: 
https://gitlab.freedesktop.org/hadess/iio-sensor-proxy/-/merge_requests/352

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1963628/+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 1959888] Re: Wayland sessions can't use external monitors that are connected to an Nvidia GPU with the proprietary driver

[jeremyszu]

ok, I arranged one machine to give it a try.
I will share the result here later.

BTW, I'm not able to check bug 1965246

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

Title:
  Wayland sessions can't use external monitors that are connected to an
  Nvidia GPU with the proprietary driver

Status in Mutter:
  Unknown
Status in OEM Priority Project:
  New
Status in mutter package in Ubuntu:
  In Progress

Bug description:
  When an external display is connected to my laptop, running Ubuntu
  22.04, the display is detected and I am sent to the login screen.
  After logging in again, the display is not running, although the
  primary laptop display works fine. The external monitor is looking for
  connection in that moment, which it never founds.

  The bug is tested on two Samsung monitors: S24R350FHUXEN and
  S22F350FHU.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Uname: Linux 5.15.0-18-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  495.46  Wed Oct 27 16:31:33 
UTC 2021
   GCC version:  gcc version 11.2.0 (Ubuntu 11.2.0-14ubuntu1)
  ApportVersion: 2.20.11-0ubuntu76
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb  3 13:25:04 2022
  DistUpgraded: 2022-01-13 15:37:13,056 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia/495.46, 5.15.0-17-generic, x86_64: installed
   nvidia/495.46, 5.15.0-18-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:086f]
 Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:086f]
  InstallationDate: Installed on 2021-09-09 (146 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Dell Inc. G3 3579
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-18-generic 
root=UUID=fd3be223-e609-4a8d-97fb-31ee2f754766 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to jammy on 2022-01-13 (20 days ago)
  dmi.bios.date: 04/20/2021
  dmi.bios.release: 1.15
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.15.0
  dmi.board.name: 0M5H57
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A05
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.0:bd04/20/2021:br1.15:svnDellInc.:pnG33579:pvr:rvnDellInc.:rn0M5H57:rvrA05:cvnDellInc.:ct10:cvr:sku086F:
  dmi.product.family: GSeries
  dmi.product.name: G3 3579
  dmi.product.sku: 086F
  dmi.sys.vendor: Dell Inc.
  nvidia-settings:
   ERROR: Unable to find display on any available system
   
   
   ERROR: Unable to find display on any available system
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.109-2ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.2-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.14-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-1build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1959888/+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 1867578] Re: gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort() from g_assertion_message() from g_assertion_message_expr() from clutter_actor_set_mapped() [asse

[Daniel van Vugt]

Comment #3 sounds like

  https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5197
  https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5137
  https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3165

and the fix hasn't landed yet:

  https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2299

That should fix most recent occurrences of the crash. I'm not so sure
about older releases though. The stack trace here is a little too terse
so it will catch-all for other similar crashes too.

** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #5197
   https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5197

** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #5137
   https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5137

** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #3165
   https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3165

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

Title:
  gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort()
  from g_assertion_message() from g_assertion_message_expr() from
  clutter_actor_set_mapped() [assertion failed:
  (!CLUTTER_ACTOR_IS_MAPPED (self))]

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
3.35.91-1ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/be5b3f189bba5293ce040f812f28644f7ba22e17 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1867578/+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 1965428] Re: package xserver-xorg-legacy 2:1.20.11-1ubuntu1~20.04.2 failed to install/upgrade: dpkg-deb --control subprocess returned error exit status 2

[Daniel van Vugt]

Sounds like some kind of file corruption occurred, during the downloads
or on disk?

https://launchpadlibrarian.net/591096265/DpkgTerminalLog.txt

Try clearing out /tmp then reboot and update the system again.

** Changed in: xorg-server (Ubuntu)
   Status: New => Incomplete

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

Title:
  package xserver-xorg-legacy 2:1.20.11-1ubuntu1~20.04.2 failed to
  install/upgrade: dpkg-deb --control subprocess returned error exit
  status 2

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  I faced this issue when I tried to install Ubuntu alongside Windows 10

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg-legacy 2:1.20.11-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-35-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompositorRunning: None
  Date: Thu Mar 17 13:45:42 2022
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DuplicateSignature:
   package:xserver-xorg-legacy:2:1.20.11-1ubuntu1~20.04.2
   Unpacking libnss-systemd:amd64 (245.4-4ubuntu3.15) over (245.4-4ubuntu3.11) 
...
   dpkg-deb: error: 
'/tmp/apt-dpkg-install-4gY3X7/01-xserver-common_2%3a1.20.13-1ubuntu1~20.04.2_all.deb'
 is not a Debian format archive
   dpkg: error processing archive 
/tmp/apt-dpkg-install-4gY3X7/01-xserver-common_2%3a1.20.13-1ubuntu1~20.04.2_all.deb
 (--unpack):
dpkg-deb --control subprocess returned error exit status 2
  ErrorMessage: dpkg-deb --control subprocess returned error exit status 2
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 
[VGA controller])
 Subsystem: Hewlett-Packard Company UHD Graphics 620 (Whiskey Lake) 
[103c:84c1]
 Subsystem: Hewlett-Packard Company GP108M [GeForce MX250] [103c:84c1]
  InstallationDate: Installed on 2022-03-17 (0 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  MachineType: HP HP Pavilion Laptop 15-cs2xxx
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-35-generic 
root=UUID=de643cef-8a09-4604-9700-75c0ebf6cdeb ro recovery nomodeset 
dis_ucode_ldr
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.6
  SourcePackage: xorg-server
  Title: package xserver-xorg-legacy 2:1.20.11-1ubuntu1~20.04.2 failed to 
install/upgrade: dpkg-deb --control subprocess returned error exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/25/2020
  dmi.bios.release: 15.23
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.23
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 84C1
  dmi.board.vendor: HP
  dmi.board.version: 15.32
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 15.32
  dmi.modalias: 
dmi:bvnInsyde:bvrF.23:bd12/25/2020:br15.23:efr15.32:svnHP:pnHPPavilionLaptop15-cs2xxx:pvrType1ProductConfigId:rvnHP:rn84C1:rvr15.32:cvnHP:ct10:cvrChassisVersion:sku6MZ82UAR#ABA:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion Laptop 15-cs2xxx
  dmi.product.sku: 6MZ82UAR#ABA
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.105-3~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1965428/+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 1965437] Re: Cannot change background 22.04

[Daniel van Vugt]

Thanks for the bug report. I can't seem to be able to reproduce the
problem here.

Do you have any nonstandard extensions loaded? Please look in the
Extensions app.

If removing extensions doesn't explain it then please attach a video or
screenshot showing how you are changing the background.

** Changed in: gnome-shell (Ubuntu)
   Status: New => Incomplete

** Changed in: mutter (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/1965437

Title:
  Cannot change background 22.04

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  Background stuck on black. Cannot change via GUI or CLI

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 17 18:57:43 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox/6.1.32, 5.15.0-22-generic, x86_64: installed
   virtualbox/6.1.32, 5.15.0-23-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:0584]
  InstallationDate: Installed on 2022-03-15 (2 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313)
  MachineType: Dell Inc. Latitude 6430U
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic 
root=UUID=0b7063d6-5898-4f7f-ac0b-73d105ab566a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/30/2018
  dmi.bios.release: 4.6
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A15
  dmi.board.name: 0JCV3H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd11/30/2018:br4.6:svnDellInc.:pnLatitude6430U:pvr01:rvnDellInc.:rn0JCV3H:rvrA02:cvnDellInc.:ct9:cvr:skuLatitude6430U:
  dmi.product.name: Latitude 6430U
  dmi.product.sku: Latitude 6430U
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.3.5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build2
  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-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965437/+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 1965466] [NEW] [DEFENDER P10, Realtek ALC293, Mic, Internal] No sound at all

[Mark Dominik Bürkle]

Public bug reported:

auto-generated

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: alsa-base 1.0.25+dfsg-0ubuntu7
ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
Uname: Linux 5.15.0-22-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  mdb2244 F pulseaudio
 /dev/snd/controlC1:  mdb2244 F pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar 18 02:51:06 2022
InstallationDate: Installed on 2018-12-10 (1193 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful
Symptom_Card: Eingebautes Tongerät - HDA Intel PCH
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  mdb2244 F pulseaudio
 /dev/snd/controlC1:  mdb2244 F pulseaudio
Symptom_Jack: Mic, Internal
Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH 
successful
Symptom_Type: No sound at all
Title: [DEFENDER P10, Realtek ALC293, Mic, Internal] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/29/2020
dmi.bios.release: 7.5
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: 1.07.05RME1
dmi.board.asset.tag: Tag 12345
dmi.board.name: NH77Dx
dmi.board.vendor: MEDION
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: MEDION
dmi.chassis.version: N/A
dmi.ec.firmware.release: 7.1
dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.05RME1:bd08/29/2020:br7.5:efr7.1:svnMEDION:pnDEFENDERP10:pvrNotApplicable:rvnMEDION:rnNH77Dx:rvrNotApplicable:cvnMEDION:ct10:cvrN/A:skuML-21000930028862:
dmi.product.family: Erazer
dmi.product.name: DEFENDER P10
dmi.product.sku: ML-210009 30028862
dmi.product.version: Not Applicable
dmi.sys.vendor: MEDION

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


** Tags: amd64 apport-bug jammy

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

Title:
  [DEFENDER P10, Realtek ALC293, Mic, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  auto-generated

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
  Uname: Linux 5.15.0-22-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mdb2244 F pulseaudio
   /dev/snd/controlC1:  mdb2244 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 18 02:51:06 2022
  InstallationDate: Installed on 2018-12-10 (1193 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful
  Symptom_Card: Eingebautes Tongerät - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mdb2244 F pulseaudio
   /dev/snd/controlC1:  mdb2244 F pulseaudio
  Symptom_Jack: Mic, Internal
  Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH 
successful
  Symptom_Type: No sound at all
  Title: [DEFENDER P10, Realtek ALC293, Mic, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/29/2020
  dmi.bios.release: 7.5
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.05RME1
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: NH77Dx
  dmi.board.vendor: MEDION
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: MEDION
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 7.1
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.05RME1:bd08/29/2020:br7.5:efr7.1:svnMEDION:pnDEFENDERP10:pvrNotApplicable:rvnMEDION:rnNH77Dx:rvrNotApplicable:cvnMEDION:ct10:cvrN/A:skuML-21000930028862:
  dmi.product.family: Erazer
  dmi.product.name: DEFENDER P10
  dmi.product.sku: ML-210009 30028862
  dmi.product.version: Not Applicable
  dmi.sys.vendor: MEDION

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1965466/+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 1965437] Re: Cannot change background 22.04

[Daniel van Vugt]

** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu)

** Also affects: mutter (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/1965437

Title:
  Cannot change background 22.04

Status in gnome-shell package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New

Bug description:
  Background stuck on black. Cannot change via GUI or CLI

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 17 18:57:43 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox/6.1.32, 5.15.0-22-generic, x86_64: installed
   virtualbox/6.1.32, 5.15.0-23-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:0584]
  InstallationDate: Installed on 2022-03-15 (2 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313)
  MachineType: Dell Inc. Latitude 6430U
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic 
root=UUID=0b7063d6-5898-4f7f-ac0b-73d105ab566a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/30/2018
  dmi.bios.release: 4.6
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A15
  dmi.board.name: 0JCV3H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd11/30/2018:br4.6:svnDellInc.:pnLatitude6430U:pvr01:rvnDellInc.:rn0JCV3H:rvrA02:cvnDellInc.:ct9:cvr:skuLatitude6430U:
  dmi.product.name: Latitude 6430U
  dmi.product.sku: Latitude 6430U
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.3.5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build2
  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-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965437/+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 1934409] Re: Only one monitor showing in Color Corrections - System Settings Module

[nukedathlonman]

And yes, xrandr at all times shows this:

andrew@desky:~$ xrandr --verbose
Screen 0: minimum 320 x 200, current 3840 x 1080, maximum 16384 x 16384
DisplayPort-0 connected primary 1920x1080+0+0 (0x5a) normal (normal left 
inverted right x axis y axis) 480mm x 270mm
Identifier: 0x55
Timestamp:  9033
Subpixel:   unknown
Gamma:  0.92:0.94:0.90
Brightness: 1.0
Clones:
CRTC:   0
CRTCs:  0 1 2 3 4 5
Transform:  1.00 0.00 0.00
0.00 1.00 0.00
0.00 0.00 1.00
   filter: 
EDID: 
00001e6d355b01010101
0b1a0104a53c2278fb7b45a4554aa227
0b5054210800714081c0810081809500
9040a9c0b3002a4480a0703827403020
3500e00e111e00fd00284b55
5512010a20202020202000fc004d
503539470a20202020202020023a8018
71382d40582c4500e00e111e016f
02031cf149900403011012101f132309
0707830165030c00123a8018
71382d40582c4500fe22111e011d
007251d01e206e285500fe22111e
8c0ad08a20e02d10103e9600fe221100
0018

00e2
GAMMA_LUT_SIZE: 4096 
range: (0, -1)
DEGAMMA_LUT_SIZE: 4096 
range: (0, -1)
GAMMA_LUT: 0 
range: (0, 65535)
CTM: 0 1 0 0 0 0 0 0 0 1 0 0 0 0 0 0 
0 1 
DEGAMMA_LUT: 0 
range: (0, 65535)
TearFree: auto 
supported: off, on, auto
subconnector: Native 
supported: Unknown, VGA, DVI-D, HDMI, DP, Wireless, Native
HDCP Content Type: HDCP Type0 
supported: HDCP Type0, HDCP Type1
Content Protection: Undesired 
supported: Undesired, Desired, Enabled
vrr_capable: 1 
range: (0, 1)
max bpc: 8 
range: (8, 16)
underscan vborder: 0 
range: (0, 128)
underscan hborder: 0 
range: (0, 128)
underscan: off 
supported: off, on, auto
scaling mode: None 
supported: None, Full, Center, Full aspect
link-status: Good 
supported: Good, Bad
CONNECTOR_ID: 94 
supported: 94
non-desktop: 0 
range: (0, 1)
  1920x1080 (0x5a) 174.500MHz +HSync +VSync *current +preferred
h: width  1920 start 1968 end 2000 total 2080 skew0 clock  83.89KHz
v: height 1080 start 1083 end 1088 total 1119   clock  74.97Hz
  1920x1080 (0x5b) 148.500MHz +HSync +VSync
h: width  1920 start 2008 end 2052 total 2200 skew0 clock  67.50KHz
v: height 1080 start 1084 end 1089 total 1125   clock  60.00Hz
  1920x1080 (0x5c) 148.500MHz +HSync +VSync
h: width  1920 start 2448 end 2492 total 2640 skew0 clock  56.25KHz
v: height 1080 start 1084 end 1089 total 1125   clock  50.00Hz
  1920x1080 (0x5d) 148.352MHz +HSync +VSync
h: width  1920 start 2008 end 2052 total 2200 skew0 clock  67.43KHz
v: height 1080 start 1084 end 1089 total 1125   clock  59.94Hz
  1680x1050 (0x5e) 146.250MHz -HSync +VSync
h: width  1680 start 1784 end 1960 total 2240 skew0 clock  65.29KHz
v: height 1050 start 1053 end 1059 total 1089   clock  59.95Hz
  1400x1050 (0x5f) 121.750MHz -HSync +VSync
h: width  1400 start 1488 end 1632 total 1864 skew0 clock  65.32KHz
v: height 1050 start 1053 end 1057 total 1089   clock  59.98Hz
  1600x900 (0x60) 108.000MHz +HSync +VSync
h: width  1600 start 1624 end 1704 total 1800 skew0 clock  60.00KHz
v: height  900 start  901 end  904 total 1000   clock  60.00Hz
  1280x1024 (0x61) 108.000MHz +HSync +VSync
h: width  1280 start 1328 end 1440 total 1688 skew0 clock  63.98KHz
v: height 1024 start 1025 end 1028 total 1066   clock  60.02Hz
  1440x900 (0x62) 106.500MHz -HSync +VSync
h: width  1440 start 1520 end 1672 total 1904 skew0 clock  55.93KHz
v: height  900 start  903 end  909 total  934   clock  59.89Hz
  1280x800 (0x63) 83.500MHz -HSync +VSync
h: width  1280 start 1352 end 1480 total 1680 skew0 clock  49.70KHz
v: height  800 start  803 end  809 total  831   clock  59.81Hz
  1152x864 (0x64) 81.768MHz -HSync +VSync
h: width  1152 start 1216 end 1336 total 1520 skew0 clock  53.79KHz
v: height  864 start  867 end  871 total  897   clock  59.97Hz
  1280x720 (0x65) 74.250MHz +HSync +VSync
h: width  1280 start 1390 end 1430 total 

[Desktop-packages] [Bug 1934409] Re: Only one monitor showing in Color Corrections - System Settings Module

[nukedathlonman]

Been a while, but now that I'm on 21.10, colord is not picking up all
devices once again - just one monitor and printer...

andrew@desky:~$ sudo colormgr get-devices-by-kind display
[sudo] password for andrew: 
Object Path:   
/org/freedesktop/ColorManager/devices/xrandr_LG_Electronics_MP59G_16843009_andrew_1000
Owner: andrew
Created:   March 18 2022, 12:32:29 AM
Modified:  March 18 2022, 12:32:29 AM
Type:  display
Enabled:   Yes
Embedded:  Yes
Model: MP59G
Vendor:LG
Serial:16843009
Seat:  seat0
Scope: temp
Colorspace:rgb
Device ID: xrandr-LG Electronics-MP59G-16843009
Profile 1: icc-0ce2e8ad3e9d95972c92b26c7cf1ff76
   /var/lib/colord/icc/MP59G #1 2019-04-20 08-41 2.2 F-S 
XYZLUT+MTX.icc
Profile 2: icc-47d27b769d969b5b00c90fa6a22b30db
   
/home/andrew/.local/share/icc/edid-6f5d0bc1638b2166d7bc7cba7f413205.icc
Profile 3: icc-cc0f880e5208bfe2b012688549fa1d31
   /home/andrew/.local/share/icc/MP59G #2 2021-07-23 11-01 2.2 F-S 
XYZLUT+MTX.icc
Profile 4: icc-275750a8cb6525973773ab3c4861e84e
   
/home/andrew/.local/share/icc/edid-f211cb0460a11ad1896f3050a36f2712.icc
Metadata:  OutputEdidMd5=f211cb0460a11ad1896f3050a36f2712
Metadata:  OutputPriority=primary
Metadata:  XRANDR_name=DisplayPort-0
Metadata:  OwnerCmdline=/usr/bin/kded5

Reinstall colord and this is the result:

andrew@desky:~$ sudo colormgr get-devices-by-kind display
[sudo] password for andrew: 
Object Path:   
/org/freedesktop/ColorManager/devices/xrandr_DisplayPort_0_andrew_1000
Owner: andrew
Created:   March 18 2022, 01:06:41 AM
Modified:  March 18 2022, 01:06:41 AM
Type:  display
Enabled:   Yes
Embedded:  Yes
Model: MP59G
Vendor:LG
Serial:16843009
Seat:  seat0
Scope: temp
Colorspace:rgb
Device ID: xrandr-DisplayPort-0
Profile 1: icc-6cc2fc162f8d590624da325d5aecf601
   /var/lib/colord/icc/MP59G #1 2021-07-23 11-58 2.2 F-S 
XYZLUT+MTX.icc
Profile 2: icc-275750a8cb6525973773ab3c4861e84e
   
/home/andrew/.local/share/icc/edid-f211cb0460a11ad1896f3050a36f2712.icc
Profile 3: icc-cc0f880e5208bfe2b012688549fa1d31
   /home/andrew/.local/share/icc/MP59G #2 2021-07-23 11-01 2.2 F-S 
XYZLUT+MTX.icc
Metadata:  OutputEdidMd5=f211cb0460a11ad1896f3050a36f2712
Metadata:  OutputPriority=primary
Metadata:  XRANDR_name=DisplayPort-0
Metadata:  OwnerCmdline=/usr/bin/kded5 

Object Path:   
/org/freedesktop/ColorManager/devices/xrandr_DisplayPort_1_andrew_1000
Owner: andrew
Created:   March 18 2022, 01:06:41 AM
Modified:  March 18 2022, 01:06:41 AM
Type:  display
Enabled:   Yes
Embedded:  Yes
Model: MP59G
Vendor:LG
Serial:16843009
Seat:  seat0
Scope: temp
Colorspace:rgb
Device ID: xrandr-DisplayPort-1
Profile 1: icc-cc0f880e5208bfe2b012688549fa1d31
   /home/andrew/.local/share/icc/MP59G #2 2021-07-23 11-01 2.2 F-S 
XYZLUT+MTX.icc
Profile 2: icc-275750a8cb6525973773ab3c4861e84e
   
/home/andrew/.local/share/icc/edid-f211cb0460a11ad1896f3050a36f2712.icc
Metadata:  OutputEdidMd5=f211cb0460a11ad1896f3050a36f2712
Metadata:  OutputPriority=primary
Metadata:  XRANDR_name=DisplayPort-1
Metadata:  OwnerCmdline=/usr/bin/kded5

Picks up both screens, looses the printer.

Next reboot, right back at square one where colord only picks up one
monitor and the printer until I reinstall colord, and once I do that I
can see both monitors but not the printer...  *SIGH*

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

Title:
  Only one monitor showing in Color Corrections - System Settings Module

Status in colord package in Ubuntu:
  New

Bug description:
  I just made the switch to 21.04, and I've immediatly run into problem
  with color corrections.

  In the Color Correction - System settings Module, I can only see and
  apply a color profile to my first display on the first display port
  (DP0).  My second display on the 2nd display Port (DP1) is not shown,
  so I'm unable to apply a color profile to make the two monitors look
  identical.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: colord 1.4.5-3
  ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21
  Uname: Linux 5.11.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Thu Jul  1 17:43:58 2021
  InstallationDate: Installed on 2019-04-19 (804 days ago)
  InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: colord
  UpgradeStatus: Upgraded to hirsute on 2021-07-01 (0 days ago)

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1965459] [NEW] Remmina actively refusing VNC connection Ubuntu 22.04

[Eric Watson]

Public bug reported:

Recently installed the developer version of Ubuntu 22.04 on my laptop
with the following specifications.

Lenovo-ideapad-330-15ARR 
-- 
OS: Ubuntu Jammy Jellyfish (development branch) x86_64 
Host: 81D2 Lenovo ideapad 330-15ARR 
Kernel: 5.15.0-22-generic 
Uptime: 1 hour, 5 mins 
Packages: 2580 (dpkg), 12 (snap) 
Shell: bash 5.1.16 
Resolution: 1366x768 
Terminal: /dev/pts/0 
CPU: AMD Ryzen 3 2200U with Radeon Vega Mobile Gfx (4) @ 2.500GHz 
GPU: AMD ATI Radeon Vega Series / Radeon Vega Mobile Series 
Memory: 980MiB / 7493MiB
org.remmina.Remmina - SNAP Build - 1.4.25 (git v1.4.25)
Desktop Environment: GNOME
Connecting to: Ubuntu Jammy Jellyfish (development branch) x86_64
Connecting via: VNC

Description:  After installing Ubuntu Jammy Jellyfish (development
branch) x86_64 I tested the VNC connections that I have set up for my
machines.  My laptop is able to connect to any system with Ubuntu
20.04.4 LTS installed on it.  However, when trying to use Remmina to VNC
into my laptop with Jammy Jellyfish installed from another machine with
Ubuntu 20.04.4 LTS installed the connection is actively refused.

I have already checked to make sure that all sharing features are turned
on along with the UFW firewall configured to allow connections through
port 5900.  Also uninstalled Remmina, and reinstalled it on my laptop
with Jammy Jellyfish installed.  Still get the same issue.  The exact
error message that comes in in Remmina is "Unable to connect to VNC
server" when everything is configured correctly on my laptop with Jammy
Jellyfish installed.

Just for the sake of experimentation, I set up Jammy Jellyfish on
another machine of mine to troubleshoot the issue further.  When trying
to connect from one machine with Jammy Jellyfish installed on it to
another machine with Jammy Jellyfish installed on it;I still get the
same error "Unable to connect to VNC server" within the Remmina
software.

In summary, any machine of mine with Jammy Jellyfish is able to VNC into
any machine with Ubuntu 20.04.4 LTS installed on it.  No machine with
20.04.4 LTS is able to VNC into another machine with Jammy Jellyfish
installed.  VNC connections in Remmina between machines with Jammy
Jellyfish installed are unable to connect to each other.

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

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

Title:
  Remmina actively refusing VNC connection Ubuntu 22.04

Status in remmina package in Ubuntu:
  New

Bug description:
  Recently installed the developer version of Ubuntu 22.04 on my laptop
  with the following specifications.

  Lenovo-ideapad-330-15ARR 
  -- 
  OS: Ubuntu Jammy Jellyfish (development branch) x86_64 
  Host: 81D2 Lenovo ideapad 330-15ARR 
  Kernel: 5.15.0-22-generic 
  Uptime: 1 hour, 5 mins 
  Packages: 2580 (dpkg), 12 (snap) 
  Shell: bash 5.1.16 
  Resolution: 1366x768 
  Terminal: /dev/pts/0 
  CPU: AMD Ryzen 3 2200U with Radeon Vega Mobile Gfx (4) @ 2.500GHz 
  GPU: AMD ATI Radeon Vega Series / Radeon Vega Mobile Series 
  Memory: 980MiB / 7493MiB
  org.remmina.Remmina - SNAP Build - 1.4.25 (git v1.4.25)
  Desktop Environment: GNOME
  Connecting to: Ubuntu Jammy Jellyfish (development branch) x86_64
  Connecting via: VNC

  Description:  After installing Ubuntu Jammy Jellyfish (development
  branch) x86_64 I tested the VNC connections that I have set up for my
  machines.  My laptop is able to connect to any system with Ubuntu
  20.04.4 LTS installed on it.  However, when trying to use Remmina to
  VNC into my laptop with Jammy Jellyfish installed from another machine
  with Ubuntu 20.04.4 LTS installed the connection is actively refused.

  I have already checked to make sure that all sharing features are
  turned on along with the UFW firewall configured to allow connections
  through port 5900.  Also uninstalled Remmina, and reinstalled it on my
  laptop with Jammy Jellyfish installed.  Still get the same issue.  The
  exact error message that comes in in Remmina is "Unable to connect to
  VNC server" when everything is configured correctly on my laptop with
  Jammy Jellyfish installed.

  Just for the sake of experimentation, I set up Jammy Jellyfish on
  another machine of mine to troubleshoot the issue further.  When
  trying to connect from one machine with Jammy Jellyfish installed on
  it to another machine with Jammy Jellyfish installed on it;I still get
  the same error "Unable to connect to VNC server" within the Remmina
  software.

  In summary, any machine of mine with Jammy Jellyfish is able to VNC
  into any machine with Ubuntu 20.04.4 LTS installed on it.  No machine
  with 20.04.4 LTS is able to VNC into another machine with Jammy
  Jellyfish installed.  VNC connections in Remmina between 

[Desktop-packages] [Bug 1965458] [NEW] Ubuntu Jammy wallpaper not shown

[igi]

Public bug reported:

Just refreshed Ubuntu 22.04 in a test virtual machine.
ubuntu-wallpapers-jammy package installed during package upgrade.
Selecting a wallpaper in the system settings, only a purple solid background is 
shown (see screenshot).

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: ubuntu-wallpapers-jammy 22.04.1-0ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar 18 00:19:43 2022
Dependencies:
 
InstallationDate: Installed on 2022-02-27 (18 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220226)
PackageArchitecture: all
SourcePackage: ubuntu-wallpapers
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ubuntu-wallpapers (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug jammy package-from-proposed wayland-session

** Attachment added: "Screenshot"
   
https://bugs.launchpad.net/bugs/1965458/+attachment/5570229/+files/Screenshot%20from%202022-03-18%2000-25-56.png

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

Title:
  Ubuntu Jammy wallpaper not shown

Status in ubuntu-wallpapers package in Ubuntu:
  New

Bug description:
  Just refreshed Ubuntu 22.04 in a test virtual machine.
  ubuntu-wallpapers-jammy package installed during package upgrade.
  Selecting a wallpaper in the system settings, only a purple solid background 
is shown (see screenshot).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntu-wallpapers-jammy 22.04.1-0ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 18 00:19:43 2022
  Dependencies:
   
  InstallationDate: Installed on 2022-02-27 (18 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220226)
  PackageArchitecture: all
  SourcePackage: ubuntu-wallpapers
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-wallpapers/+bug/1965458/+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 1965453] Re: gjs-console assert failure: free(): invalid pointer

[Apport retracing service]

*** This bug is a duplicate of bug 1946165 ***
https://bugs.launchpad.net/bugs/1946165

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1946165, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1965453/+attachment/5570215/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1965453/+attachment/5570217/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1965453/+attachment/5570221/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1965453/+attachment/5570222/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1965453/+attachment/5570223/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1965453/+attachment/5570224/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1965453/+attachment/5570225/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1946165

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  gjs-console assert failure: free(): invalid pointer

Status in gjs package in Ubuntu:
  New

Bug description:
  Dash To Panel

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: gjs 1.71.90-1
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  AssertionMessage: free(): invalid pointer
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 18 01:21:00 2022
  ExecutablePath: /usr/bin/gjs-console
  InstallationDate: Installed on 2022-03-17 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220316)
  ProcCmdline: /usr/bin/gjs /usr/share/gnome-shell/org.gnome.Shell.Extensions
  Signal: 6
  SourcePackage: gjs
  StacktraceTop:
   __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f98acdebb8c 
"%s\n") at ../sysdeps/posix/libc_fatal.c:155
   malloc_printerr (str=str@entry=0x7f98acde9764 "free(): invalid pointer") at 
./malloc/malloc.c:5664
   _int_free (av=, p=, have_lock=0) at 
./malloc/malloc.c:4439
   __GI___libc_free (mem=) at ./malloc/malloc.c:3391
   ?? () from /lib/x86_64-linux-gnu/libgtk-4.so.1
  Title: gjs-console assert failure: free(): invalid pointer
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1965453/+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 1965449] [NEW] new Ubuntu logo looks bad

[Francois Thirioux]

Public bug reported:

0.9.5+git20211018-1ubuntu2

introduces the new Ubuntu branding logo.
The white rectangle supporting the new Ubuntu dotted circle does not look good 
to me.
Too much contrast with the black background.

Not a big deal and for sure just my opinion.

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

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

Title:
  new Ubuntu logo looks bad

Status in plymouth package in Ubuntu:
  New

Bug description:
  0.9.5+git20211018-1ubuntu2

  introduces the new Ubuntu branding logo.
  The white rectangle supporting the new Ubuntu dotted circle does not look 
good to me.
  Too much contrast with the black background.

  Not a big deal and for sure just my opinion.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1965449/+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 1867578] Re: gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort() from g_assertion_message() from g_assertion_message_expr() from clutter_actor_set_mapped() [asse

[Heather Ellsworth]

I wonder if this is the same thing I just saw:
https://paste.ubuntu.com/p/GSWYFy4jYh/

Or if it's not the same thing, I wonder if it is related. Also a
clutter_acto_set_mapped: assertion failed crash. I have a crash log too,
if you'd like to take a look.

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

Title:
  gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort()
  from g_assertion_message() from g_assertion_message_expr() from
  clutter_actor_set_mapped() [assertion failed:
  (!CLUTTER_ACTOR_IS_MAPPED (self))]

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
3.35.91-1ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/be5b3f189bba5293ce040f812f28644f7ba22e17 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1867578/+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 1964732] Re: [FFe] Include Desktop Icons Appearance Settings

[Launchpad Bug Tracker]

This bug was fixed in the package gnome-shell-extension-desktop-icons-ng
- 39+20220316.cc9c7d3e-1

---
gnome-shell-extension-desktop-icons-ng (39+20220316.cc9c7d3e-1) unstable; 
urgency=medium

  [ Jeremy Bicha ]
  * New upstream git snapshot compatible with GNOME Shell 42
  * Drop all patches: applied in new release

  [ Marco Trevisan (Treviño) ]
  * Add patch to use the Ubuntu Appearance panel to display settings
in the Ubuntu session (LP: #1964732)
  * Add patches to show full settings directly from the Extensions apps

 -- Jeremy Bicha   Thu, 17 Mar 2022 08:37:01 -0400

** Changed in: gnome-shell-extension-desktop-icons-ng (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  [FFe] Include Desktop Icons Appearance Settings

Status in gnome-control-center package in Ubuntu:
  Triaged
Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu:
  Fix Released

Bug description:
  In Jammy the default desktop extension is providing lots settings in a
  poorly integrated way, accessible from right-click:

  https://i.imgur.com/boMhCrH.png

  We got a community contribution
  (https://gitlab.gnome.org/Community/Ubuntu/gnome-conyol-
  center/-/merge_requests/9) to move the most relevant (for ubuntu)
  settings into the ubuntu "appearance" panel in gnome-control-center so
  that we can explicitly only support a restricted number of options
  that we care about, while all the rest can be tuned when using the
  ding options manually or tools such as d-conf editor.

  The appearance options will include these new widgets:

  https://i.imgur.com/Cup75om.png (wording to be improved before UIF)

  This is the code involved:
   - 
https://salsa.debian.org/gnome-team/gnome-control-center/-/commit/3f7c10501b1ac28311dd9edb64e64bfbbcd67204

  Plus we need to change DING code to call `gnome-settings-daemon
  ubuntu` on desktop context menu.

  Not sure this is fully a FFe request, given that from the global
  desktop point of view we want actually support less features.

  ---

  It would be nice to be able to upload the update before UIF, so that
  we don't require further exception steps.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1964732/+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 1965440] [NEW] After the Gnome 42 beta update, desktop freezes periodically

[rue]

Public bug reported:

After updating my laptop yesterday 17.03.2022 I have noticed random
Desktop freezes, where the nothing on the desktop is responsive apart
from the mouse. This doesn't appear to be a hard lockup where you need
to hard reset.

I am able to get my desktop back by hitting the Super(Windows) key which
seems to unfreeze the desktop with no errors or corruption.

I am also experiencing this on another Desktop computer running Jammy
20.04. This desktop is running an old AND/ATI RV710 card under wayland.

There doesn't seem to be any pattern or obvious trigger that is causing
this.

I can submit a report from the other computer if needed.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xwayland 2:22.1.0-1
Uname: Linux 5.15.25-051525-generic x86_64
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar 18 08:14:15 2022
InstallationDate: Installed on 2022-02-23 (21 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220202)
ProcEnviron:
 LANGUAGE=en_NZ:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_NZ.UTF-8
 SHELL=/bin/bash
SourcePackage: xwayland
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: xwayland (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 xwayland in Ubuntu.
https://bugs.launchpad.net/bugs/1965440

Title:
  After the Gnome 42 beta update, desktop freezes periodically

Status in xwayland package in Ubuntu:
  New

Bug description:
  After updating my laptop yesterday 17.03.2022 I have noticed random
  Desktop freezes, where the nothing on the desktop is responsive apart
  from the mouse. This doesn't appear to be a hard lockup where you need
  to hard reset.

  I am able to get my desktop back by hitting the Super(Windows) key
  which seems to unfreeze the desktop with no errors or corruption.

  I am also experiencing this on another Desktop computer running Jammy
  20.04. This desktop is running an old AND/ATI RV710 card under
  wayland.

  There doesn't seem to be any pattern or obvious trigger that is
  causing this.

  I can submit a report from the other computer if needed.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xwayland 2:22.1.0-1
  Uname: Linux 5.15.25-051525-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 18 08:14:15 2022
  InstallationDate: Installed on 2022-02-23 (21 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220202)
  ProcEnviron:
   LANGUAGE=en_NZ:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_NZ.UTF-8
   SHELL=/bin/bash
  SourcePackage: xwayland
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xwayland/+bug/1965440/+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 1964132] Re: [FFe] webkit2gtk additionally built with libsoup3 support

[Jeremy Bicha]

** Tags removed: block-proposed

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

Title:
  [FFe] webkit2gtk additionally built with libsoup3 support

Status in webkit2gtk package in Ubuntu:
  Triaged

Bug description:
  Request
  ---
  1. Add the new libsoup3-using packages in webkit2gtk

  2. Build Epiphany with the new webkit2gtk 4.1 API built with libsoup3

  Why Needed
  --
  Our webkit2gtk packaging is built with libsoup2 (webkitgtk's 4.0 API). 
Debian's packaging recently added additional packages built with libsoup3 
(webkitgtk's 4.1 API); these should not affect the existing libsoup2 packages.

  The libsoup2 > libsoup3 transition is a big one and will not happen
  for 22.04 LTS; I am hoping we can finish it for main by 23.04 but I
  haven't looked into it yet.

  It's expected that GNOME 43 will try to switch to libsoup3. Having
  webkit2gtk with libsoup3 support in 22.04 LTS will make it easier for
  newer versions of the GNOME Web Browser (epiphany) to run on this
  release. It also will make it easier to create snaps of GNOME 43 apps
  using a core22 base.

  My instinct is that we want libsoup3 and the new webkit+libsoup3
  packages to stay in universe for 22.04 LTS and then Main Inclusion can
  be recommended for 22.10.

  It is not intended for any traditional (.deb) packages in 22.04 LTS
  itself to use these new packages except epiphany.

  I already uploaded the webkit2gtk merge/sync with this change. If this
  FFe is rejected, I can undo the addition.

  What Changed
  
  See above

  Build Test
  --
  https://launchpad.net/ubuntu/+source/webkit2gtk/2.35.90-1ubuntu1

  Install Test
  
  Not done yet.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/1964132/+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 1963279] Re: [SRU] libreoffice 7.2.6 for impish

[Rico Tzschichholz]

Upgraded libreoffice from 1:7.2.5-0ubuntu0.21.10.3 to
1:7.2.6-0ubuntu0.21.10.1 from impish-proposed in a clean and up-to-date
impish amd64 VM, and successfully ran test plan at
https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice.

** Tags removed: verification-needed verification-needed-impish
** Tags added: verification-done verification-done-impish

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

Title:
  [SRU] libreoffice 7.2.6 for impish

Status in libreoffice package in Ubuntu:
  New
Status in libreoffice source package in Impish:
  Fix Committed

Bug description:
  [Impact]

   * LibreOffice 7.2.6 is in its sixth bugfix release of the 7.2 line:
   https://wiki.documentfoundation.org/ReleasePlan/7.2#7.2.6_release

   * Version 7.2.5 is currently released in impish. For a list of fixed bugs 
compared to 7.2.5 see the list of bugs fixed in the release candidates of 7.2.6 
(that's a total of 52 bugs):
   https://wiki.documentfoundation.org/Releases/7.2.6/RC1#List_of_fixed_bugs
   https://wiki.documentfoundation.org/Releases/7.2.6/RC2#List_of_fixed_bugs

   * Given the nature of the project, the complexity of the codebase and
  the high level of quality assurance upstream, it is preferable to SRU
  a minor release rather than cherry-pick selected bug fixes.

  [Testing]

   * Upstream testing. Bugs fixed upstream typically include
  unit/regression tests, and the release itself is extensively exercised
  (both in an automated manner and manually).

    * A recent set of upstream's automated jenkins testing can be found here:
  https://ci.libreoffice.org/job/gerrit_72/1492/

    * More information about the upstream QA testing can be found here:
  * Automated tests
    https://wiki.documentfoundation.org/QA/Testing/Automated_Tests
  * Automated UI tests
    https://wiki.documentfoundation.org/Development/UITests
  * Regression tests
    https://wiki.documentfoundation.org/QA/Testing/Regression_Tests
  * Feature tests
    https://wiki.documentfoundation.org/QA/Testing/Feature_Tests

   * Launchpad testing. The libreoffice packages include autopkgtests that were 
run and verified as passing.
  * [amd64] 
https://autopkgtest.ubuntu.com/results/autopkgtest-impish-libreoffice-libreoffice-still/impish/amd64/libr/libreoffice/20220306_160418_6b7ed@/log.gz
  * [arm64] 
https://autopkgtest.ubuntu.com/results/autopkgtest-impish-libreoffice-libreoffice-still/impish/arm64/libr/libreoffice/20220306_163451_0d390@/log.gz
  * [armhf] 
https://autopkgtest.ubuntu.com/results/autopkgtest-impish-libreoffice-libreoffice-still/impish/armhf/libr/libreoffice/20220306_175952_950a3@/log.gz
  * [ppc64el] 
https://autopkgtest.ubuntu.com/results/autopkgtest-impish-libreoffice-libreoffice-still/impish/ppc64el/libr/libreoffice/20220306_151710_6d5ad@/log.gz
  * [s390x] 
https://autopkgtest.ubuntu.com/results/autopkgtest-impish-libreoffice-libreoffice-still/impish/s390x/libr/libreoffice/20220306_145252_b5efa@/log.gz
   * General smoke testing of all the applications in the office suite were 
carried out by going through the manual testplan as documented by: 
https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice

  [Regression Potential]

   * A minor release with a total of 52 bug fixes always carries the
  potential for introducing regressions, even though it is a bugfix-only
  release, meaning that no new features were added, and no existing
  features were removed.

   * A combination of autopkgtests and careful smoke testing as
  described above should provide reasonable confidence that no
  regressions sneaked in.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1963279/+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 1965112] Re: cupsd crashed with SIGSEGV in __strnlen_avx2_rtm()

[Launchpad Bug Tracker]

This bug was fixed in the package cups - 2.4.1op1-1ubuntu3

---
cups (2.4.1op1-1ubuntu3) jammy; urgency=low

  * Fixed crasher in the patch for temporary queues for local services
in the previous release. Updated the patch and the upstream pull
request (LP: #1965112, Upstream pull request #353).

 -- Till Kamppeter   Wed, 16 Mar 2022 18:24:08
+0100

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

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

Title:
  cupsd crashed with SIGSEGV in __strnlen_avx2_rtm()

Status in cups package in Ubuntu:
  Fix Released

Bug description:
  trying to print with jammy 20220316, to a network printer

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: cups-daemon 2.4.1op1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
  Uname: Linux 5.15.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Wed Mar 16 11:00:00 2022
  ExecutablePath: /usr/sbin/cupsd
  InstallationDate: Installed on 2022-02-28 (15 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220226)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: LENOVO 20Y5CTO1WW
  Papersize: a4
  ProcAttrCurrent: /usr/sbin/cupsd (enforce)
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic 
root=UUID=229d75cc-2aa3-4f8f-b5bd-d310f6218a3f ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic 
root=UUID=229d75cc-2aa3-4f8f-b5bd-d310f6218a3f ro quiet splash vt.handoff=7
  RebootRequiredPkgs: Error: path contained symlinks.
  SegvAnalysis:
   Segfault happened at: 0x7fdde6d9698c <__strcmp_evex+44>: vpcmpeqb 
(%rsi),%ymm17,%k1{%k2}
   PC (0x7fdde6d9698c) ok
   source "(%rsi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%ymm17" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: cups
  StacktraceTop:
   __strcmp_evex () at ../sysdeps/x86_64/multiarch/strcmp-evex.S:139
   ?? ()
   ?? ()
   ?? ()
   __libc_start_call_main (main=main@entry=0x55ea813993a0, argc=argc@entry=2, 
argv=argv@entry=0x7fffb71a6eb8) at ../sysdeps/nptl/libc_start_call_main.h:58
  Title: cupsd crashed with SIGSEGV in __strcmp_evex()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  dmi.bios.date: 10/14/2021
  dmi.bios.release: 1.11
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N40ET29W (1.11 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20Y5CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T08861 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.11
  dmi.modalias: 
dmi:bvnLENOVO:bvrN40ET29W(1.11):bd10/14/2021:br1.11:efr1.11:svnLENOVO:pn20Y5CTO1WW:pvrThinkPadX1ExtremeGen4i:rvnLENOVO:rn20Y5CTO1WW:rvrSDK0T08861WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20Y5_BU_Think_FM_ThinkPadX1ExtremeGen4i:
  dmi.product.family: ThinkPad X1 Extreme Gen 4i
  dmi.product.name: 20Y5CTO1WW
  dmi.product.sku: LENOVO_MT_20Y5_BU_Think_FM_ThinkPad X1 Extreme Gen 4i
  dmi.product.version: ThinkPad X1 Extreme Gen 4i
  dmi.sys.vendor: LENOVO
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1965112/+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 1965437] [NEW] Cannot change background 22.04

[Chief]

Public bug reported:

Background stuck on black. Cannot change via GUI or CLI

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Mar 17 18:57:43 2022
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
DkmsStatus:
 virtualbox/6.1.32, 5.15.0-22-generic, x86_64: installed
 virtualbox/6.1.32, 5.15.0-23-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:0584]
InstallationDate: Installed on 2022-03-15 (2 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313)
MachineType: Dell Inc. Latitude 6430U
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic 
root=UUID=0b7063d6-5898-4f7f-ac0b-73d105ab566a ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/30/2018
dmi.bios.release: 4.6
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A15
dmi.board.name: 0JCV3H
dmi.board.vendor: Dell Inc.
dmi.board.version: A02
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd11/30/2018:br4.6:svnDellInc.:pnLatitude6430U:pvr01:rvnDellInc.:rn0JCV3H:rvrA02:cvnDellInc.:ct9:cvr:skuLatitude6430U:
dmi.product.name: Latitude 6430U
dmi.product.sku: Latitude 6430U
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.110-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 21.3.5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build2
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-2

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


** Tags: amd64 apport-bug jammy reproducible 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/1965437

Title:
  Cannot change background 22.04

Status in xorg package in Ubuntu:
  New

Bug description:
  Background stuck on black. Cannot change via GUI or CLI

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 17 18:57:43 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox/6.1.32, 5.15.0-22-generic, x86_64: installed
   virtualbox/6.1.32, 5.15.0-23-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:0584]
  InstallationDate: Installed on 2022-03-15 (2 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313)
  MachineType: Dell Inc. Latitude 6430U
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic 
root=UUID=0b7063d6-5898-4f7f-ac0b-73d105ab566a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/30/2018
  dmi.bios.release: 4.6
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A15
  dmi.board.name: 0JCV3H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd11/30/2018:br4.6:svnDellInc.:pnLatitude6430U:pvr01:rvnDellInc.:rn0JCV3H:rvrA02:cvnDellInc.:ct9:cvr:skuLatitude6430U:
  dmi.product.name: Latitude 6430U
  dmi.product.sku: Latitude 6430U
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  

[Desktop-packages] [Bug 1965168] Re: jammy community competition wallpapers

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-wallpapers - 22.04.1-0ubuntu1

---
ubuntu-wallpapers (22.04.1-0ubuntu1) jammy; urgency=medium

  * Add Jammy's wallpapers, default and community contest winners
(lp: #1965168)

 -- Sebastien Bacher   Thu, 17 Mar 2022 16:19:03
+0100

** Changed in: ubuntu-wallpapers (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  jammy community competition wallpapers

Status in ubuntu-wallpapers package in Ubuntu:
  Fix Released

Bug description:
  We have the winning images, in full size and both under CC by SA 4.0

  The author of the first image is Elena Stravoravdi

  The author of the remaining images, both light and dark mode, is by
  hiking93

  If it is possible, we would like to include both the light and dark
  mode of the jellyfish image. If there is not enough room, please only
  include the light jellyfish image.

  Let me know if there are any other concerns or questions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-wallpapers/+bug/1965168/+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 1965428] [NEW] package xserver-xorg-legacy 2:1.20.11-1ubuntu1~20.04.2 failed to install/upgrade: dpkg-deb --control subprocess returned error exit status 2

[Karthik]

Public bug reported:

I faced this issue when I tried to install Ubuntu alongside Windows 10

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: xserver-xorg-legacy 2:1.20.11-1ubuntu1~20.04.2
ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-35-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
CasperMD5CheckResult: skip
CompositorRunning: None
Date: Thu Mar 17 13:45:42 2022
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
DuplicateSignature:
 package:xserver-xorg-legacy:2:1.20.11-1ubuntu1~20.04.2
 Unpacking libnss-systemd:amd64 (245.4-4ubuntu3.15) over (245.4-4ubuntu3.11) ...
 dpkg-deb: error: 
'/tmp/apt-dpkg-install-4gY3X7/01-xserver-common_2%3a1.20.13-1ubuntu1~20.04.2_all.deb'
 is not a Debian format archive
 dpkg: error processing archive 
/tmp/apt-dpkg-install-4gY3X7/01-xserver-common_2%3a1.20.13-1ubuntu1~20.04.2_all.deb
 (--unpack):
  dpkg-deb --control subprocess returned error exit status 2
ErrorMessage: dpkg-deb --control subprocess returned error exit status 2
GraphicsCard:
 Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 [VGA 
controller])
   Subsystem: Hewlett-Packard Company UHD Graphics 620 (Whiskey Lake) 
[103c:84c1]
   Subsystem: Hewlett-Packard Company GP108M [GeForce MX250] [103c:84c1]
InstallationDate: Installed on 2022-03-17 (0 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
MachineType: HP HP Pavilion Laptop 15-cs2xxx
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-35-generic 
root=UUID=de643cef-8a09-4604-9700-75c0ebf6cdeb ro recovery nomodeset 
dis_ucode_ldr
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.6
SourcePackage: xorg-server
Title: package xserver-xorg-legacy 2:1.20.11-1ubuntu1~20.04.2 failed to 
install/upgrade: dpkg-deb --control subprocess returned error exit status 2
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/25/2020
dmi.bios.release: 15.23
dmi.bios.vendor: Insyde
dmi.bios.version: F.23
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 84C1
dmi.board.vendor: HP
dmi.board.version: 15.32
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 15.32
dmi.modalias: 
dmi:bvnInsyde:bvrF.23:bd12/25/2020:br15.23:efr15.32:svnHP:pnHPPavilionLaptop15-cs2xxx:pvrType1ProductConfigId:rvnHP:rn84C1:rvr15.32:cvnHP:ct10:cvrChassisVersion:sku6MZ82UAR#ABA:
dmi.product.family: 103C_5335KV HP Pavilion
dmi.product.name: HP Pavilion Laptop 15-cs2xxx
dmi.product.sku: 6MZ82UAR#ABA
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.105-3~20.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-package focal need-duplicate-check ubuntu

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

Title:
  package xserver-xorg-legacy 2:1.20.11-1ubuntu1~20.04.2 failed to
  install/upgrade: dpkg-deb --control subprocess returned error exit
  status 2

Status in xorg-server package in Ubuntu:
  New

Bug description:
  I faced this issue when I tried to install Ubuntu alongside Windows 10

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg-legacy 2:1.20.11-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-35-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompositorRunning: None
  Date: Thu Mar 17 13:45:42 2022
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DuplicateSignature:
   package:xserver-xorg-legacy:2:1.20.11-1ubuntu1~20.04.2
   Unpacking libnss-systemd:amd64 (245.4-4ubuntu3.15) over (245.4-4ubuntu3.11) 
...
   dpkg-deb: error: 
'/tmp/apt-dpkg-install-4gY3X7/01-xserver-common_2%3a1.20.13-1ubuntu1~20.04.2_all.deb'
 is not a Debian format archive
   dpkg: error processing archive 
/tmp/apt-dpkg-install-4gY3X7/01-xserver-common_2%3a1.20.13-1ubuntu1~20.04.2_all.deb
 (--unpack):
dpkg-deb --control subprocess returned error exit status 2
  ErrorMessage: dpkg-deb --control subprocess returned error exit status 2
  GraphicsCard:
   Intel 

[Desktop-packages] [Bug 1965331] Re: Dutch translations is incomplete

[Gunnar Hjalmarsson]

I can confirm that quite a few strings are not yet translated into
Dutch.

https://gitlab.com/rastersoft/desktop-icons-ng/-/blob/master/po/nl.po

Assigning this bug to the Ubuntu Dutch Translators team as a reminder.
While it's best in the long run to translate upstream, using Launchpad
for now may be wise since 22.04 will be released soon:

https://translations.launchpad.net/ubuntu/jammy/+source/gnome-shell-
extension-desktop-icons-ng/+pots/ding/nl

P.S. Please disregard lotuspsychje's request. Such info is irrelevant
for this kind of bug.

** Also affects: ubuntu-translations
   Importance: Undecided
   Status: New

** Changed in: ubuntu-translations
   Importance: Undecided => Medium

** Changed in: ubuntu-translations
   Status: New => Confirmed

** Changed in: ubuntu-translations
 Assignee: (unassigned) => Ubuntu Dutch Translators (ubuntu-l10n-nl)

** Changed in: gnome-shell-extension-desktop-icons-ng (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  Dutch translations is incomplete

Status in Ubuntu Translations:
  Confirmed
Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu:
  Invalid

Bug description:
  I installed ubuntu 22.04 to do some testing. So far the experience has
  been really smooth. The only thing i am missing is that the Dutch
  translations are incomplete for the Desktop Icon Settings.

  I right click the desktop and click "Desktop Icon Settings"(Menu item
  is also not translated). After that is see that the first 3 options
  are correctly translated except for the icon size dropdown.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-translations/+bug/1965331/+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 1965331] [NEW] Dutch translations is incomplete

[Executenor]

Public bug reported:

I installed ubuntu 22.04 to do some testing. So far the experience has
been really smooth. The only thing i am missing is that the Dutch
translations are incomplete for the Desktop Icon Settings.

I right click the desktop and click "Desktop Icon Settings"(Menu item is
also not translated). After that is see that the first 3 options are
correctly translated except for the icon size dropdown.

** Affects: gnome-shell-extension-desktop-icons-ng (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Dutch translations is incomplete

Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu:
  New

Bug description:
  I installed ubuntu 22.04 to do some testing. So far the experience has
  been really smooth. The only thing i am missing is that the Dutch
  translations are incomplete for the Desktop Icon Settings.

  I right click the desktop and click "Desktop Icon Settings"(Menu item
  is also not translated). After that is see that the first 3 options
  are correctly translated except for the icon size dropdown.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons-ng/+bug/1965331/+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 1965112] ThreadStacktrace.txt

[Apport retracing service]

** Attachment added: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1965112/+attachment/5570110/+files/ThreadStacktrace.txt

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1965112/+attachment/5569535/+files/CoreDump.gz

** Changed in: cups (Ubuntu)
   Importance: Undecided => Medium

** Summary changed:

- cupsd crashed with SIGSEGV in __strcmp_evex()
+ cupsd crashed with SIGSEGV in __strnlen_avx2_rtm()

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

Title:
  cupsd crashed with SIGSEGV in __strnlen_avx2_rtm()

Status in cups package in Ubuntu:
  Fix Committed

Bug description:
  trying to print with jammy 20220316, to a network printer

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: cups-daemon 2.4.1op1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
  Uname: Linux 5.15.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Wed Mar 16 11:00:00 2022
  ExecutablePath: /usr/sbin/cupsd
  InstallationDate: Installed on 2022-02-28 (15 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220226)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: LENOVO 20Y5CTO1WW
  Papersize: a4
  ProcAttrCurrent: /usr/sbin/cupsd (enforce)
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic 
root=UUID=229d75cc-2aa3-4f8f-b5bd-d310f6218a3f ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic 
root=UUID=229d75cc-2aa3-4f8f-b5bd-d310f6218a3f ro quiet splash vt.handoff=7
  RebootRequiredPkgs: Error: path contained symlinks.
  SegvAnalysis:
   Segfault happened at: 0x7fdde6d9698c <__strcmp_evex+44>: vpcmpeqb 
(%rsi),%ymm17,%k1{%k2}
   PC (0x7fdde6d9698c) ok
   source "(%rsi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%ymm17" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: cups
  StacktraceTop:
   __strcmp_evex () at ../sysdeps/x86_64/multiarch/strcmp-evex.S:139
   ?? ()
   ?? ()
   ?? ()
   __libc_start_call_main (main=main@entry=0x55ea813993a0, argc=argc@entry=2, 
argv=argv@entry=0x7fffb71a6eb8) at ../sysdeps/nptl/libc_start_call_main.h:58
  Title: cupsd crashed with SIGSEGV in __strcmp_evex()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  dmi.bios.date: 10/14/2021
  dmi.bios.release: 1.11
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N40ET29W (1.11 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20Y5CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T08861 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.11
  dmi.modalias: 
dmi:bvnLENOVO:bvrN40ET29W(1.11):bd10/14/2021:br1.11:efr1.11:svnLENOVO:pn20Y5CTO1WW:pvrThinkPadX1ExtremeGen4i:rvnLENOVO:rn20Y5CTO1WW:rvrSDK0T08861WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20Y5_BU_Think_FM_ThinkPadX1ExtremeGen4i:
  dmi.product.family: ThinkPad X1 Extreme Gen 4i
  dmi.product.name: 20Y5CTO1WW
  dmi.product.sku: LENOVO_MT_20Y5_BU_Think_FM_ThinkPad X1 Extreme Gen 4i
  dmi.product.version: ThinkPad X1 Extreme Gen 4i
  dmi.sys.vendor: LENOVO
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1965112/+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 1965112] StacktraceSource.txt

[Apport retracing service]

** Attachment added: "StacktraceSource.txt"
   
https://bugs.launchpad.net/bugs/1965112/+attachment/5570109/+files/StacktraceSource.txt

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

Title:
  cupsd crashed with SIGSEGV in __strnlen_avx2_rtm()

Status in cups package in Ubuntu:
  Fix Committed

Bug description:
  trying to print with jammy 20220316, to a network printer

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: cups-daemon 2.4.1op1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
  Uname: Linux 5.15.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Wed Mar 16 11:00:00 2022
  ExecutablePath: /usr/sbin/cupsd
  InstallationDate: Installed on 2022-02-28 (15 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220226)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: LENOVO 20Y5CTO1WW
  Papersize: a4
  ProcAttrCurrent: /usr/sbin/cupsd (enforce)
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic 
root=UUID=229d75cc-2aa3-4f8f-b5bd-d310f6218a3f ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic 
root=UUID=229d75cc-2aa3-4f8f-b5bd-d310f6218a3f ro quiet splash vt.handoff=7
  RebootRequiredPkgs: Error: path contained symlinks.
  SegvAnalysis:
   Segfault happened at: 0x7fdde6d9698c <__strcmp_evex+44>: vpcmpeqb 
(%rsi),%ymm17,%k1{%k2}
   PC (0x7fdde6d9698c) ok
   source "(%rsi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%ymm17" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: cups
  StacktraceTop:
   __strcmp_evex () at ../sysdeps/x86_64/multiarch/strcmp-evex.S:139
   ?? ()
   ?? ()
   ?? ()
   __libc_start_call_main (main=main@entry=0x55ea813993a0, argc=argc@entry=2, 
argv=argv@entry=0x7fffb71a6eb8) at ../sysdeps/nptl/libc_start_call_main.h:58
  Title: cupsd crashed with SIGSEGV in __strcmp_evex()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  dmi.bios.date: 10/14/2021
  dmi.bios.release: 1.11
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N40ET29W (1.11 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20Y5CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T08861 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.11
  dmi.modalias: 
dmi:bvnLENOVO:bvrN40ET29W(1.11):bd10/14/2021:br1.11:efr1.11:svnLENOVO:pn20Y5CTO1WW:pvrThinkPadX1ExtremeGen4i:rvnLENOVO:rn20Y5CTO1WW:rvrSDK0T08861WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20Y5_BU_Think_FM_ThinkPadX1ExtremeGen4i:
  dmi.product.family: ThinkPad X1 Extreme Gen 4i
  dmi.product.name: 20Y5CTO1WW
  dmi.product.sku: LENOVO_MT_20Y5_BU_Think_FM_ThinkPad X1 Extreme Gen 4i
  dmi.product.version: ThinkPad X1 Extreme Gen 4i
  dmi.sys.vendor: LENOVO
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1965112/+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 1965112] cupsd crashed with SIGSEGV in __strcmp_evex()

[Apport retracing service]

StacktraceTop:
 __strnlen_avx2_rtm () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:256
 create_local_printer (con=0x55ea82141090) at 
/build/cups-y1LIcO/cups-2.4.1op1/scheduler/ipp.c:5539
 cupsdProcessIPPRequest (con=0x55ea82141090) at 
/build/cups-y1LIcO/cups-2.4.1op1/scheduler/ipp.c:604
 cupsdReadClient (con=0x55ea82141090) at 
/build/cups-y1LIcO/cups-2.4.1op1/scheduler/client.c:1814
 cupsdDoSelect (timeout=) at 
/build/cups-y1LIcO/cups-2.4.1op1/scheduler/select.c:480

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

Title:
  cupsd crashed with SIGSEGV in __strnlen_avx2_rtm()

Status in cups package in Ubuntu:
  Fix Committed

Bug description:
  trying to print with jammy 20220316, to a network printer

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: cups-daemon 2.4.1op1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
  Uname: Linux 5.15.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Wed Mar 16 11:00:00 2022
  ExecutablePath: /usr/sbin/cupsd
  InstallationDate: Installed on 2022-02-28 (15 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220226)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: LENOVO 20Y5CTO1WW
  Papersize: a4
  ProcAttrCurrent: /usr/sbin/cupsd (enforce)
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic 
root=UUID=229d75cc-2aa3-4f8f-b5bd-d310f6218a3f ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic 
root=UUID=229d75cc-2aa3-4f8f-b5bd-d310f6218a3f ro quiet splash vt.handoff=7
  RebootRequiredPkgs: Error: path contained symlinks.
  SegvAnalysis:
   Segfault happened at: 0x7fdde6d9698c <__strcmp_evex+44>: vpcmpeqb 
(%rsi),%ymm17,%k1{%k2}
   PC (0x7fdde6d9698c) ok
   source "(%rsi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%ymm17" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: cups
  StacktraceTop:
   __strcmp_evex () at ../sysdeps/x86_64/multiarch/strcmp-evex.S:139
   ?? ()
   ?? ()
   ?? ()
   __libc_start_call_main (main=main@entry=0x55ea813993a0, argc=argc@entry=2, 
argv=argv@entry=0x7fffb71a6eb8) at ../sysdeps/nptl/libc_start_call_main.h:58
  Title: cupsd crashed with SIGSEGV in __strcmp_evex()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  dmi.bios.date: 10/14/2021
  dmi.bios.release: 1.11
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N40ET29W (1.11 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20Y5CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T08861 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.11
  dmi.modalias: 
dmi:bvnLENOVO:bvrN40ET29W(1.11):bd10/14/2021:br1.11:efr1.11:svnLENOVO:pn20Y5CTO1WW:pvrThinkPadX1ExtremeGen4i:rvnLENOVO:rn20Y5CTO1WW:rvrSDK0T08861WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20Y5_BU_Think_FM_ThinkPadX1ExtremeGen4i:
  dmi.product.family: ThinkPad X1 Extreme Gen 4i
  dmi.product.name: 20Y5CTO1WW
  dmi.product.sku: LENOVO_MT_20Y5_BU_Think_FM_ThinkPad X1 Extreme Gen 4i
  dmi.product.version: ThinkPad X1 Extreme Gen 4i
  dmi.sys.vendor: LENOVO
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1965112/+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 1965112] Stacktrace.txt

[Apport retracing service]

** Attachment added: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1965112/+attachment/5570108/+files/Stacktrace.txt

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

Title:
  cupsd crashed with SIGSEGV in __strnlen_avx2_rtm()

Status in cups package in Ubuntu:
  Fix Committed

Bug description:
  trying to print with jammy 20220316, to a network printer

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: cups-daemon 2.4.1op1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
  Uname: Linux 5.15.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Wed Mar 16 11:00:00 2022
  ExecutablePath: /usr/sbin/cupsd
  InstallationDate: Installed on 2022-02-28 (15 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220226)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: LENOVO 20Y5CTO1WW
  Papersize: a4
  ProcAttrCurrent: /usr/sbin/cupsd (enforce)
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic 
root=UUID=229d75cc-2aa3-4f8f-b5bd-d310f6218a3f ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic 
root=UUID=229d75cc-2aa3-4f8f-b5bd-d310f6218a3f ro quiet splash vt.handoff=7
  RebootRequiredPkgs: Error: path contained symlinks.
  SegvAnalysis:
   Segfault happened at: 0x7fdde6d9698c <__strcmp_evex+44>: vpcmpeqb 
(%rsi),%ymm17,%k1{%k2}
   PC (0x7fdde6d9698c) ok
   source "(%rsi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%ymm17" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: cups
  StacktraceTop:
   __strcmp_evex () at ../sysdeps/x86_64/multiarch/strcmp-evex.S:139
   ?? ()
   ?? ()
   ?? ()
   __libc_start_call_main (main=main@entry=0x55ea813993a0, argc=argc@entry=2, 
argv=argv@entry=0x7fffb71a6eb8) at ../sysdeps/nptl/libc_start_call_main.h:58
  Title: cupsd crashed with SIGSEGV in __strcmp_evex()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  dmi.bios.date: 10/14/2021
  dmi.bios.release: 1.11
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N40ET29W (1.11 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20Y5CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T08861 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.11
  dmi.modalias: 
dmi:bvnLENOVO:bvrN40ET29W(1.11):bd10/14/2021:br1.11:efr1.11:svnLENOVO:pn20Y5CTO1WW:pvrThinkPadX1ExtremeGen4i:rvnLENOVO:rn20Y5CTO1WW:rvrSDK0T08861WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20Y5_BU_Think_FM_ThinkPadX1ExtremeGen4i:
  dmi.product.family: ThinkPad X1 Extreme Gen 4i
  dmi.product.name: 20Y5CTO1WW
  dmi.product.sku: LENOVO_MT_20Y5_BU_Think_FM_ThinkPad X1 Extreme Gen 4i
  dmi.product.version: ThinkPad X1 Extreme Gen 4i
  dmi.sys.vendor: LENOVO
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1965112/+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 1964923] Re: list-oem-metapackages crashed with AttributeError in packages_for_modalias(): 'Cache' object has no attribute 'packages'

[Brian Murray]

** Tags added: fr-2117

** Also affects: update-notifier (Ubuntu Jammy)
   Importance: High
   Status: Confirmed

** Also affects: ubuntu-drivers-common (Ubuntu Jammy)
   Importance: High
   Status: Confirmed

** Tags removed: rls-jj-incoming

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

Title:
  list-oem-metapackages crashed with AttributeError in
  packages_for_modalias(): 'Cache' object has no attribute 'packages'

Status in ubuntu-drivers-common package in Ubuntu:
  Confirmed
Status in update-notifier package in Ubuntu:
  Confirmed
Status in ubuntu-drivers-common source package in Jammy:
  Confirmed
Status in update-notifier source package in Jammy:
  Confirmed

Bug description:
  This bug occurred after install of Ubuntu Mate Jammy daily ISO
  15-03-2022

  Test machine Dell Optiplex 7060 in UEFI+secure boot mode.

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: update-notifier-common 3.192.51
  ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
  Uname: Linux 5.15.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: MATE
  Date: Tue Mar 15 10:21:14 2022
  ExecutablePath: /usr/lib/update-notifier/list-oem-metapackages
  InstallationDate: Installed on 2022-03-15 (0 days ago)
  InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Alpha amd64 
(20220315)
  InterpreterPath: /usr/bin/python3.10
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/lib/update-notifier/list-oem-metapackages
  Python3Details: /usr/bin/python3.10, Python 3.10.2, python3-minimal, 
3.10.1-0ubuntu1
  PythonArgs: ['/usr/lib/update-notifier/list-oem-metapackages']
  PythonDetails: N/A
  SourcePackage: update-notifier
  Title: list-oem-metapackages crashed with AttributeError in 
packages_for_modalias(): 'Cache' object has no attribute 'packages'
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1964923/+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 1965314] Re: Please remove firefox binaries for ppc64el and s390x from the release pocket

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: firefox (Ubuntu)
   Status: New => Confirmed

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

Title:
  Please remove firefox binaries for ppc64el and s390x from the release
  pocket

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  With bug #1962021, the firefox packages in jammy are becoming "transitional 
packages" that install the firefox snap and wrapper scripts.
  However the snap is available only on amd64, armhf and arm64, so to allow the 
new packages to migrate the existing binaries for ppc64el and s390x that are no 
longer built from source need to be removed.

  For s390x this should be fairly uncontroversial, as Ubuntu desktop in
  general isn't officially supported on this architecture, and firefox
  isn't tested there, only known to build successfully (autopkgtests
  have always been failing there).

  For ppc64el this is perhaps a bit more controversial, although the
  reality is that firefox on this architecture receives no testing from
  Ubuntu developers (not from the desktop team anyway), and autopkgtests
  have always been failing there. I don't have numbers of firefox users
  on this architecture.

  Note that upstream is not committed to supporting these architectures
  either, they fall in their Tier-3 targets (see https://firefox-source-
  docs.mozilla.org/contributing/build/supported.html#supported-build-
  targets). Given that the maintenance of the firefox snap is a joint
  effort between Mozilla and the Ubuntu desktop team, it is unlikely
  that we will start building the firefox snap for ppc64el or s390x.

  The binaries that need removing are: firefox, firefox-dbg, firefox-
  dev, firefox-geckodriver.

  The last three in the list (firefox-dbg, firefox-dev, firefox-geckodriver) do 
not have any reverse dependencies.
  The binary package firefox itself is recommended or suggested by a good 
number of packages, and is also a direct dependency of the following packages:
    - cinnamon-desktop-environment (all): depends on "firefox-esr | firefox | 
chromium | gnome-www-browser"
    - firefox-dbg: not an issue as this one also needs removing
    - firefox-geckodriver: not an issue as this one also needs removing
    - firefox-launchpad-plugin (all): depends on "firefox"
    - gnome-core (linux-any): depends on "firefox-esr (>= 78) | firefox (>= 78) 
| chromium | chromium-browser | epiphany-browser"
    - webhttrack (any): depends on "iceape-browser | iceweasel | icecat | 
mozilla | firefox | mozilla-firefox | www-browser"
    - x2gothinclient-minidesktop (all): depends on "firefox-esr | firefox | 
chromium | x-www-browser"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1965314/+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 1965180] Re: apt-add-repository requires --login for private repos, breaking automated workflows

[Brian Murray]

** Tags added: fr-2116

** Also affects: software-properties (Ubuntu Jammy)
   Importance: High
   Status: New

** Tags removed: rls-jj-incoming

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

Title:
  apt-add-repository requires --login for private repos, breaking
  automated workflows

Status in software-properties package in Ubuntu:
  New
Status in software-properties source package in Jammy:
  New

Bug description:
  On Focal, in an automated environment (such as a launchpad builder), a
  used can do the following workflow:

  curl
  "https://keyserver.ubuntu.com/pks/lookup?op=get=0x${FINGERPRINT};
  --output /etc/apt/trusted.gpg.d/${FINGERPRINT}.asc

  apt-add-repository "deb https://${USERNAME}:${PASSWORD}@private-
  ppa.launchpad.net/${REPO}/ubuntu focal main"

  Hit:1 http://archive.ubuntu.com/ubuntu focal InRelease
  Hit:2 http://archive.ubuntu.com/ubuntu focal-updates InRelease
  Hit:3 http://archive.ubuntu.com/ubuntu focal-backports InRelease
  Hit:4 http://security.ubuntu.com/ubuntu focal-security InRelease
  Get:5 https://private-ppa.launchpad.net/$REPO/ubuntu focal InRelease [24.3 kB]
  Get:6 https://private-ppa.launchpad.net/$REPO/ubuntu focal/main amd64 
Packages [3288 B] 
  Get:7 https://private-ppa.launchpad.net/$REPO/ubuntu focal/main 
Translation-en [1892 B]  

  However, on Jammy, I get the following:

  
  curl "https://keyserver.ubuntu.com/pks/lookup?op=get=0x${FINGERPRINT}; 
--output /etc/apt/trusted.gpg.d/${FINGERPRINT}.asc

  apt-add-repository "deb https://${USERNAME}:${PASSWORD}@private-
  ppa.launchpad.net/${REPO}/ubuntu jammy main"

  Repository: 'deb https://private-ppa.launchpad.net/$REPO/ubuntu jammy main'
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 105, 
in lpppa
  self._lpppa = self.lpteam.getPPAByName(name=self.ppaname)
File "/usr/lib/python3/dist-packages/lazr/restfulclient/resource.py", line 
592, in __call__
  response, content = self.root._browser._request(
File "/usr/lib/python3/dist-packages/lazr/restfulclient/_browser.py", line 
429, in _request
  raise error
  lazr.restfulclient.errors.NotFound: HTTP Error 404: Not Found
  Response headers:
  ---
  -content-encoding: gzip
  content-length: 91
  content-type: text/plain;charset=utf-8
  date: Wed, 16 Mar 2022 19:54:16 GMT
  server: gunicorn/19.8.1
  status: 404
  vary: Accept-Encoding
  x-powered-by: Zope (www.zope.org), Python (www.python.org)
  x-request-id: ec4bd7ff-f333-4543-ba91-3b7b063fab0e
  x-vcs-revision: 81acd06336f3c4be8f28a2213f7a64912593402d
  ---
  Response body:
  ---
  b"Object: , 
name: '$REPO'"
  ---

  
  During handling of the above exception, another exception occurred:

  Traceback (most recent call last):
File "/usr/bin/apt-add-repository", line 364, in 
  sys.exit(0 if addaptrepo.main() else 1)
File "/usr/bin/apt-add-repository", line 352, in main
  self.prompt_user_shortcut(shortcut)
File "/usr/bin/apt-add-repository", line 140, in prompt_user_shortcut
  if shortcut.description:
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 117, 
in description
  return self.lpppa.description
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 109, 
in lpppa
  raise ShortcutException(msg)
  softwareproperties.shortcuthandler.ShortcutException: ERROR: ppa 
'$REPO/proposed' not found (use --login if private)

  Impish similarly breaks. Digging through changelogs, I see various
  entries in Impish forward, starting with version 0.99.0 where a
  refactor was done.

  using `--login` is not possible in an automated setup (such as a
  builder) as it starts an OAuth dance, which requires human
  interaction. this will break existing automation utilizing apt-add-
  repository for users when migrating to Jammy

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1965180/+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 1962021] Re: Make the deb package install the firefox snap

[Olivier Tilloy]

I filed bug #1965314 to request the removal of firefox binary packages
that are no longer built from source on ppc64el and s390x.

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

Title:
  Make the deb package install the firefox snap

Status in firefox package in Ubuntu:
  In Progress

Bug description:
  Canonical and Mozilla are working together to make the firefox snap
  the only supported package in Ubuntu, thus deprecating the deb package
  in the archive.

  This bug tracks the transformation of the firefox package in the
  archive into a transitional package that installs the snap, much like
  was done for chromium-browser in Ubuntu 19.10.

  There are a number of known problems and regressions with the snap
  compared to the deb (see
  https://bugzilla.mozilla.org/show_bug.cgi?id=snap and
  https://bugs.launchpad.net/ubuntu/+source/firefox/+bugs?field.tag=snap),
  those are actively being worked on and will be addressed in due time,
  please refrain from using this bug to point them out. Instead, file
  separate bugs in the upstream bug tracker
  (https://bugzilla.mozilla.org/enter_bug.cgi), making sure to specify
  this is about the snap package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1962021/+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 1965168] Re: jammy community competition wallpapers

[Sebastien Bacher]

** Changed in: ubuntu-wallpapers (Ubuntu)
   Status: Triaged => Fix Committed

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

Title:
  jammy community competition wallpapers

Status in ubuntu-wallpapers package in Ubuntu:
  Fix Committed

Bug description:
  We have the winning images, in full size and both under CC by SA 4.0

  The author of the first image is Elena Stravoravdi

  The author of the remaining images, both light and dark mode, is by
  hiking93

  If it is possible, we would like to include both the light and dark
  mode of the jellyfish image. If there is not enough room, please only
  include the light jellyfish image.

  Let me know if there are any other concerns or questions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-wallpapers/+bug/1965168/+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 1965323] [NEW] Wayland: overview hotspot is not recognised if cursor slides to it along top of screen

[Yotam Benshalom]

Public bug reported:

Using Wayland, ubuntu-gnome, nvidia-510, RTL locale (hebrew).

When sliding the cursor along the top (horizontal) edge of the screen to
the hotspot at the top right corner of the screen (where the activities
menu is found in an rtl environment), gnome-shell does not go into
overview mode (and back).

When sliding the cursor to the very same hotspot along the right
(vertical) edge of the screen, gnome-shell works properly and goes to
overview mode (and back).

This problem exists only in wayland gnome sessions. It does not occur in
x11 gnome sessions.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42~beta-1ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
Uname: Linux 5.15.0-22-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: GNOME
Date: Thu Mar 17 17:21:49 2022
DisplayManager: gdm3
InstallationDate: Installed on 2022-01-31 (44 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220126)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=he_IL.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug jammy rtl

** Description changed:

  Using Wayland, ubuntu-gnome, nvidia-510, RTL locale (hebrew).
  
  When sliding the cursor along the top (horizontal) edge of the screen to
- the hotspot at top right corner of the screen (where the activities menu
- is found in an rtl environment), gnome-shell does not go into overview
- mode (and back).
+ the hotspot at the top right corner of the screen (where the activities
+ menu is found in an rtl environment), gnome-shell does not go into
+ overview mode (and back).
  
  When sliding the cursor to the very same hotspot along the right
  (vertical) edge of the screen, gnome-shell works properly and goes to
  overview mode (and back).
  
  This problem exists only in wayland gnome sessions. It does not occur in
  x11 gnome sessions.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42~beta-1ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
  Uname: Linux 5.15.0-22-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: GNOME
  Date: Thu Mar 17 17:21:49 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-01-31 (44 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220126)
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=he_IL.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=he_IL.UTF-8
+  SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

** Tags added: rtl

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

Title:
  Wayland: overview hotspot is not recognised if cursor slides to it
  along top of screen

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Using Wayland, ubuntu-gnome, nvidia-510, RTL locale (hebrew).

  When sliding the cursor along the top (horizontal) edge of the screen
  to the hotspot at the top right corner of the screen (where the
  activities menu is found in an rtl environment), gnome-shell does not
  go into overview mode (and back).

  When sliding the cursor to the very same hotspot along the right
  (vertical) edge of the screen, gnome-shell works properly and goes to
  overview mode (and back).

  This problem exists only in wayland gnome sessions. It does not occur
  in x11 gnome sessions.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42~beta-1ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
  Uname: Linux 5.15.0-22-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: GNOME
  Date: Thu Mar 17 17:21:49 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-01-31 (44 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220126)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=he_IL.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1964923] Re: list-oem-metapackages crashed with AttributeError in packages_for_modalias(): 'Cache' object has no attribute 'packages'

[Brian Murray]

** Changed in: update-notifier (Ubuntu)
   Importance: Undecided => High

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

Title:
  list-oem-metapackages crashed with AttributeError in
  packages_for_modalias(): 'Cache' object has no attribute 'packages'

Status in ubuntu-drivers-common package in Ubuntu:
  Confirmed
Status in update-notifier package in Ubuntu:
  Confirmed

Bug description:
  This bug occurred after install of Ubuntu Mate Jammy daily ISO
  15-03-2022

  Test machine Dell Optiplex 7060 in UEFI+secure boot mode.

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: update-notifier-common 3.192.51
  ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
  Uname: Linux 5.15.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: MATE
  Date: Tue Mar 15 10:21:14 2022
  ExecutablePath: /usr/lib/update-notifier/list-oem-metapackages
  InstallationDate: Installed on 2022-03-15 (0 days ago)
  InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Alpha amd64 
(20220315)
  InterpreterPath: /usr/bin/python3.10
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/lib/update-notifier/list-oem-metapackages
  Python3Details: /usr/bin/python3.10, Python 3.10.2, python3-minimal, 
3.10.1-0ubuntu1
  PythonArgs: ['/usr/lib/update-notifier/list-oem-metapackages']
  PythonDetails: N/A
  SourcePackage: update-notifier
  Title: list-oem-metapackages crashed with AttributeError in 
packages_for_modalias(): 'Cache' object has no attribute 'packages'
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1964923/+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 1965189] Re: Add session migration for GNOME 42 dark theme

[Jeremy Bicha]

** Description changed:

  Test Case
  -
  1. From Ubuntu 20.04 LTS or 21.10, open the Settings app. Click Appearance 
and choose Dark
  2. Upgrade to Ubuntu 22.04 LTS
  3. Log out then log back in
  4. Your apps should still be dark
  
  Linked Issue
  
  That test case is broken by the libhandy update. See LP: #1964841
  
  We are updating gnome-control-center to set the correct gsettings value
  (below) when choosing a dark theme.
  
  Workaround
  --
  If you want the fix to apply without logging out at any time, you can run
  session-migration --file 
/usr/share/session-migration/scripts/dark-theme-migration.sh
  
- This requires gsettings-desktop-schemas 42~rc-1ubuntu2 or higher
+ This requires gsettings-desktop-schemas 42~rc-1ubuntu3 or higher
  
  Or you can run this command yourself instead
  gsettings set org.gnome.desktop.interface color-scheme 'prefer-dark'

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

Title:
  Add session migration for GNOME 42 dark theme

Status in gsettings-desktop-schemas package in Ubuntu:
  Fix Committed
Status in gsettings-desktop-schemas source package in Jammy:
  Fix Committed

Bug description:
  Test Case
  -
  1. From Ubuntu 20.04 LTS or 21.10, open the Settings app. Click Appearance 
and choose Dark
  2. Upgrade to Ubuntu 22.04 LTS
  3. Log out then log back in
  4. Your apps should still be dark

  Linked Issue
  
  That test case is broken by the libhandy update. See LP: #1964841

  We are updating gnome-control-center to set the correct gsettings
  value (below) when choosing a dark theme.

  Workaround
  --
  If you want the fix to apply without logging out at any time, you can run
  session-migration --file 
/usr/share/session-migration/scripts/dark-theme-migration.sh

  This requires gsettings-desktop-schemas 42~rc-1ubuntu3 or higher

  Or you can run this command yourself instead
  gsettings set org.gnome.desktop.interface color-scheme 'prefer-dark'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gsettings-desktop-schemas/+bug/1965189/+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 1963767] Re: Microphone not working after suspend

[Nazar Mokrynskyi]

Yeah, situation on this laptop is very problematic. It loses microphone
audio all of a sudden often on its own (I unmute myself on Google Meet
and notice there is no audio from me).

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

Title:
  Microphone not working after suspend

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I have Logitech BRIO 4k Pro webcam connected via its USB cable to Asus
  Vivobook Pro 16X OLED M7600QE-L2014X (90NB0V71-M02190) laptop.

  On Ubuntu 21.10 after suspend (`systemctl suspend`) webcam's
  microphone stops working (device is still there, but audio level is at
  zero all the time).

  To make it work again I need to do 2 things (just one is not sufficient):
  1) Disconnect and connect webcam again to the laptop
  2) Restart pulseaudio with `pulseaudio --kill; pulseaudio --start`

  Not sure whose fault it is, likely kernel driver, but the fact that 
pulseaudio needs to be restarted is concerning as well. Reproducible 100% for 
me.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: Custom
  DistroRelease: Ubuntu 21.10
  Package: pulseaudio 1:15.0+dfsg1-1ubuntu2.2
  PackageArchitecture: amd64
  Tags:  impish
  Uname: Linux 5.16.11-xanmod1 x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip docker libvirt lpadmin plugdev 
sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1963767/+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 1965314] [NEW] Please remove firefox binaries for ppc64el and s390x from the release pocket

[Olivier Tilloy]

Public bug reported:

With bug #1962021, the firefox packages in jammy are becoming "transitional 
packages" that install the firefox snap and wrapper scripts.
However the snap is available only on amd64, armhf and arm64, so to allow the 
new packages to migrate the existing binaries for ppc64el and s390x that are no 
longer built from source need to be removed.

For s390x this should be fairly uncontroversial, as Ubuntu desktop in
general isn't officially supported on this architecture, and firefox
isn't tested there, only known to build successfully (autopkgtests have
always been failing there).

For ppc64el this is perhaps a bit more controversial, although the
reality is that firefox on this architecture receives no testing from
Ubuntu developers (not from the desktop team anyway), and autopkgtests
have always been failing there. I don't have numbers of firefox users on
this architecture.

Note that upstream is not committed to supporting these architectures
either, they fall in their Tier-3 targets (see https://firefox-source-
docs.mozilla.org/contributing/build/supported.html#supported-build-
targets). Given that the maintenance of the firefox snap is a joint
effort between Mozilla and the Ubuntu desktop team, it is unlikely that
we will start building the firefox snap for ppc64el or s390x.

The binaries that need removing are: firefox, firefox-dbg, firefox-dev,
firefox-geckodriver.

The last three in the list (firefox-dbg, firefox-dev, firefox-geckodriver) do 
not have any reverse dependencies.
The binary package firefox itself is recommended or suggested by a good number 
of packages, and is also a direct dependency of the following packages:
  - cinnamon-desktop-environment (all): depends on "firefox-esr | firefox | 
chromium | gnome-www-browser"
  - firefox-dbg: not an issue as this one also needs removing
  - firefox-geckodriver: not an issue as this one also needs removing
  - firefox-launchpad-plugin (all): depends on "firefox"
  - gnome-core (linux-any): depends on "firefox-esr (>= 78) | firefox (>= 78) | 
chromium | chromium-browser | epiphany-browser"
  - webhttrack (any): depends on "iceape-browser | iceweasel | icecat | mozilla 
| firefox | mozilla-firefox | www-browser"
  - x2gothinclient-minidesktop (all): depends on "firefox-esr | firefox | 
chromium | x-www-browser"

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

** Description changed:

  With bug #1962021, the firefox packages in jammy are becoming "transitional 
packages" that install the firefox snap and wrapper scripts.
- However the snap is available only on amd64, armhf and arm64, so to allow the 
new packages to migrate the existing binaries for ppc64el and s390x need to be 
removed.
+ However the snap is available only on amd64, armhf and arm64, so to allow the 
new packages to migrate the existing binaries for ppc64el and s390x that are no 
longer built from source need to be removed.
  
  For s390x this should be fairly uncontroversial, as Ubuntu desktop in
  general isn't officially supported on this architecture, and firefox
  isn't tested there, only known to build successfully (autopkgtests have
  always been failing there).
  
  For ppc64el this is perhaps a bit more controversial, although the
  reality is that firefox on this architecture receives no testing from
  Ubuntu developers (not from the desktop team anyway), and autopkgtests
  have always been failing there. I don't have numbers of firefox users on
  this architecture.
  
  Note that upstream is not committed to supporting these architectures
  either, they fall in their Tier-3 targets (see https://firefox-source-
  docs.mozilla.org/contributing/build/supported.html#supported-build-
  targets). Given that the maintenance of the firefox snap is a joint
  effort between Mozilla and the Ubuntu desktop team, it is unlikely that
  we will start building the firefox snap for ppc64el or s390x.
  
  The binaries that need removing are: firefox, firefox-dbg, firefox-dev,
  firefox-geckodriver.
  
  The last three in the list (firefox-dbg, firefox-dev, firefox-geckodriver) do 
not have any reverse dependencies.
  The binary package firefox itself is recommended or suggested by a good 
number of packages, and is also a direct dependency of the following packages:
-   - cinnamon-desktop-environment (all): depends on "firefox-esr | firefox | 
chromium | gnome-www-browser"
-   - firefox-dbg: not an issue as this one also needs removing
-   - firefox-geckodriver: not an issue as this one also needs removing
-   - firefox-launchpad-plugin (all): depends on "firefox"
-   - gnome-core (linux-any): depends on "firefox-esr (>= 78) | firefox (>= 78) 
| chromium | chromium-browser | epiphany-browser"
-   - webhttrack (any): depends on "iceape-browser | iceweasel | icecat | 
mozilla | firefox | mozilla-firefox | www-browser"
-   - x2gothinclient-minidesktop (all): depends on "firefox-esr | firefox | 
chromium | x-www-browser"
+   - 

[Desktop-packages] [Bug 1964747] Re: [Jammy][regression] u-d-c default to use 470 instead of 510

[Alberto Milone]

I have just uploaded ubuntu-drivers-common_0.9.0~0.20.04.7 and ubuntu-
drivers-common_0.9.2.4~0.21.10.2.

Note: this will have to be verified together with LP: #1958488, if we
want both fixes released at the same time.

** Description changed:

  [Impact]
  
-  * In Ubuntu 22.04, ubuntu-drivers install will install nvidia-470 instead of 
510. (the ubuntu-drivers install is the best and recommended way to install 
nvidia driver).
-  * nvidia-470 is LTSB (although webpage shows PB) and nvidia-510 is PB, in 
this case, we need to chose the newer version since the support is fair in both 
version.
-  * Also, 22.04 announces Wayland supports but nvidia-470 doesn't support in 
Wayland scope at least from gdm upstream.
+  * In Ubuntu 22.04, ubuntu-drivers install will install nvidia-470 instead of 
510. (the ubuntu-drivers install is the best and recommended way to install 
nvidia driver).
+  * nvidia-470 is LTSB (although webpage shows PB) and nvidia-510 is PB, in 
this case, we need to chose the newer version since the support is fair in both 
version.
+  * Also, 22.04 announces Wayland supports but nvidia-470 doesn't support in 
Wayland scope at least from gdm upstream.
  
  [Test Plan]
  
-  * ubuntu-drivers debug
+  * Call "ubuntu-drivers debug" and check that 510 is marked as 
"(auto-install)"
  ```
  ...
  === matching driver packages ===
- nvidia-driver-510: installed:available: 510.54-0ubuntu2  [distro]  
non-free  modalias: pci:v10DEd25A0sv1028sd0A61bc03sc02i00  
path: /sys/devices/pci:00/:00:01.0/:01:00.0  vendor: NVIDIA 
Corporation  model: GA107M [GeForce RTX 3050 Ti Mobile] 
+ nvidia-driver-510: installed:available: 510.54-0ubuntu2  [distro]  
non-free  modalias: pci:v10DEd25A0sv1028sd0A61bc03sc02i00  
path: /sys/devices/pci:00/:00:01.0/:01:00.0  vendor: NVIDIA 
Corporation  model: GA107M [GeForce RTX 3050 Ti Mobile]
  ...
- nvidia-driver-470: installed:available: 470.103.01-0ubuntu2 
(auto-install)  [distro]  non-free  modalias: 
pci:v10DEd25A0sv1028sd0A61bc03sc02i00  path: 
/sys/devices/pci:00/:00:01.0/:01:00.0  vendor: NVIDIA Corporation  
model: GA107M [GeForce RTX 3050 Ti Mobile]  support level: LTSB 
+ nvidia-driver-470: installed:available: 470.103.01-0ubuntu2 
(auto-install)  [distro]  non-free  modalias: 
pci:v10DEd25A0sv1028sd0A61bc03sc02i00  path: 
/sys/devices/pci:00/:00:01.0/:01:00.0  vendor: NVIDIA Corporation  
model: GA107M [GeForce RTX 3050 Ti Mobile]  support level: LTSB
  ...
  ```
-  * As you can see, "(auto-install)" is point to 470 because of it owns LTSB 
tag.
+  * As you can see, "(auto-install)" points to 470 because it owns LTSB tag.
  
  [Fix]
-  * Adjust the priority in UbuntuDrivers/detect.py, if the PB and LTSB 
versions found, then it needs to pick the newer version one.
+  * Adjust the priority in UbuntuDrivers/detect.py, if the PB and LTSB 
versions found, then it needs to pick the newer version one.
  
  [Where problems could occur]
-  * It has less possible to introduce regression since the patch only changes 
_cmp_gfx_alternatives() which counts the priority of nvidia drivers be 
installed.
-  * In Ubuntu, we have nvidia-390, 470 and 510 so far as I known and these 
cases are listed in test_system_driver_packages_chroot_support_branch_pb.
+  * It has less possible to introduce regression since the patch only changes 
_cmp_gfx_alternatives() which counts the priority of nvidia drivers be 
installed.
+  * In Ubuntu, we have nvidia-390, 470 and 510 so far as I known and these 
cases are listed in test_system_driver_packages_chroot_support_branch_pb.
  
  ---
  
  + nvidia-graphics-drivers-510 (510.54-0ubuntu0.20.04.1)
  +
  +   * New upstream release (LP: #1961075):
  + - Fixed a bug that could cause GPU exceptions when minimizing a
  +   fullscreen Vulkan application on certain desktops, such as
  +   Plasma.
  +   * debian/templates/control.in:
  + - Set XB-Support to PB (production branch).
  +   * debian/rules.defs:
  + - Add support for video ABI 25.
  
  ---
  
  Since
    * debian/templates/control.in:
  - Set XB-Support to PB (production branch).
  
  The u-d-c will choose LTS branch instead of PB branch.
  
  because `def _cmp_gfx_alternatives(x, y):` doesn't define PB.
  
  [Additional information]
  If installed 470 instead of 510, then it will cause
  https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1963701

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

Title:
  [Jammy][regression] u-d-c default to use 470 instead of 510

Status in OEM Priority Project:
  Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common source package in Bionic:
  In Progress
Status in ubuntu-drivers-common source package in Focal:
  In 

[Desktop-packages] [Bug 1965067] Re: [42beta] (some) GNOME applications use light theme when dark is set in gnome-control-center

[Jeremy Bicha]

libhandy-1's behavior is working as intended by GNOME. Let's reassign to
gnome-control-center.

The upgrade scenario is being handled by LP: #1965189
and the new libhandy-1 is being held in jammy-proposed by LP: #1964841

** Package changed: libhandy-1 (Ubuntu Jammy) => gnome-control-center
(Ubuntu Jammy)

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

** Changed in: gnome-control-center (Ubuntu Jammy)
 Assignee: Jeremy Bicha (jbicha) => Marco Trevisan (Treviño) (3v1n0)

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

Title:
  [42beta] (some) GNOME applications use light theme when dark is set in
  gnome-control-center

Status in gnome-control-center package in Ubuntu:
  Triaged
Status in gnome-control-center source package in Jammy:
  Triaged

Bug description:
  gnome-disks does not apply the Yaru theme, when all other GNOME
  applications respect the default theme.

  See attached screenshot.

  gnome-disks 42~rc-1ubuntu1
  gnome-shell 42~beta-1ubuntu2
  yaru-theme-gtk 22.04.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1965067/+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 1965189] Re: Add session migration for GNOME 42 dark theme

[Jeremy Bicha]

** Changed in: gsettings-desktop-schemas (Ubuntu Jammy)
   Status: In Progress => Fix Committed

** Description changed:

  Test Case
  -
  1. From Ubuntu 20.04 LTS or 21.10, open the Settings app. Click Appearance 
and choose Dark
  2. Upgrade to Ubuntu 22.04 LTS
- 3. Your apps should still be dark
+ 3. Log out then log back in
+ 4. Your apps should still be dark
  
  Linked Issue
  
  That test case is broken by the libhandy update. See LP: #1964841
  
  We are updating gnome-control-center to set the correct gsettings value
  (below) when choosing a dark theme.
  
- Implementation
- --
- We need to set gsettings org.gnome.desktop.interface color-scheme 
'prefer-dark' for users using a theme name ending in "-dark"
+ Workaround
+ --
+ If you want the fix to apply without logging out at any time, you can run
+ session-migration --file 
/usr/share/session-migration/scripts/dark-theme-migration.sh
  
- That gsettings schema is provided by gsettings-desktop-schemas.
+ This requires gsettings-desktop-schemas 42~rc-1ubuntu2 or higher
  
- I don't think we should do this in ubuntu-settings because there are
- people using GTK desktops that don't have ubuntu-settings installed.
- 
- I suggest we use dh-migrations/session-migration to do this from gnome-
- settings-daemon.
- 
- Let me know now if there is a better place for this.
+ Or you can run this command yourself instead
+ gsettings set org.gnome.desktop.interface color-scheme 'prefer-dark'

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

Title:
  Add session migration for GNOME 42 dark theme

Status in gsettings-desktop-schemas package in Ubuntu:
  Fix Committed
Status in gsettings-desktop-schemas source package in Jammy:
  Fix Committed

Bug description:
  Test Case
  -
  1. From Ubuntu 20.04 LTS or 21.10, open the Settings app. Click Appearance 
and choose Dark
  2. Upgrade to Ubuntu 22.04 LTS
  3. Log out then log back in
  4. Your apps should still be dark

  Linked Issue
  
  That test case is broken by the libhandy update. See LP: #1964841

  We are updating gnome-control-center to set the correct gsettings
  value (below) when choosing a dark theme.

  Workaround
  --
  If you want the fix to apply without logging out at any time, you can run
  session-migration --file 
/usr/share/session-migration/scripts/dark-theme-migration.sh

  This requires gsettings-desktop-schemas 42~rc-1ubuntu2 or higher

  Or you can run this command yourself instead
  gsettings set org.gnome.desktop.interface color-scheme 'prefer-dark'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gsettings-desktop-schemas/+bug/1965189/+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 1960387] Re: fprintd crashed with SIGSEGV in log_v() from usbi_log() from libusb_unref_device()

[Bug Watch Updater]

** Changed in: libusb
   Status: New => Fix Released

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

Title:
  fprintd crashed with SIGSEGV in log_v() from usbi_log() from
  libusb_unref_device()

Status in libusb:
  Fix Released
Status in fprintd package in Ubuntu:
  Won't Fix
Status in libusb package in Ubuntu:
  Fix Committed

Bug description:
  +

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: fprintd 1.94.1-1
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Uname: Linux 5.15.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu76
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Mon Feb  7 21:58:32 2022
  ExecutablePath: /usr/libexec/fprintd
  InstallationDate: Installed on 2021-12-21 (50 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  ProcCmdline: /usr/libexec/fprintd
  ProcEnviron:
   LANG=ru_RU.UTF-8
   PATH=(custom, no user)
  SegvAnalysis:
   Segfault happened at: 0x7fd8a7a3855f:call   *%rax
   PC (0x7fd8a7a3855f) ok
   source "*%rax" (0xd86d54af5d1db0f9) not located in a known VMA region 
(needed readable region)!
   destination "(%rsp)" (0x7ffdceacc590) ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: fprintd
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libusb-1.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libusb-1.0.so.0
   libusb_unref_device () from /lib/x86_64-linux-gnu/libusb-1.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgusb.so.2
   g_object_unref () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: fprintd crashed with SIGSEGV in libusb_unref_device()
  UpgradeStatus: Upgraded to jammy on 2022-01-16 (23 days ago)
  UserGroups: N/A
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/libusb/+bug/1960387/+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 1965189] Re: Add session migration for GNOME 42 dark theme

[Jeremy Bicha]

Since it's gsettings-desktop-schemas that provides the new schema, Seb
suggested we just add the migration there directly. Thanks!

** Package changed: gnome-settings-daemon (Ubuntu Jammy) => gsettings-
desktop-schemas (Ubuntu Jammy)

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

Title:
  Add session migration for GNOME 42 dark theme

Status in gsettings-desktop-schemas package in Ubuntu:
  In Progress
Status in gsettings-desktop-schemas source package in Jammy:
  In Progress

Bug description:
  Test Case
  -
  1. From Ubuntu 20.04 LTS or 21.10, open the Settings app. Click Appearance 
and choose Dark
  2. Upgrade to Ubuntu 22.04 LTS
  3. Your apps should still be dark

  Linked Issue
  
  That test case is broken by the libhandy update. See LP: #1964841

  We are updating gnome-control-center to set the correct gsettings
  value (below) when choosing a dark theme.

  Implementation
  --
  We need to set gsettings org.gnome.desktop.interface color-scheme 
'prefer-dark' for users using a theme name ending in "-dark"

  That gsettings schema is provided by gsettings-desktop-schemas.

  I don't think we should do this in ubuntu-settings because there are
  people using GTK desktops that don't have ubuntu-settings installed.

  I suggest we use dh-migrations/session-migration to do this from
  gnome-settings-daemon.

  Let me know now if there is a better place for this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gsettings-desktop-schemas/+bug/1965189/+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 802942] Re: printing PDFs (and other complex documents) from GTK applications fails

[Bug Watch Updater]

** Changed in: firefox
   Status: New => Expired

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

Title:
  printing PDFs (and other complex documents) from GTK applications
  fails

Status in Mozilla Firefox:
  Expired
Status in cups package in Ubuntu:
  Invalid
Status in cups-filters package in Ubuntu:
  Invalid
Status in firefox package in Ubuntu:
  Incomplete
Status in thunderbird package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  I'm discovering a bug when printing complex PDFs or other complex
  documents from GTK applications. Printing complex PDFs from evince, or
  sometimes even printing comples webpages from firefox result in one
  error page being printed instead of the document content:

  +-+
  | ERROR NAME;|
  | undefined|
  | COMMAND; |
  | Q|
  | OPERAND STACK;  |
  +-+

  My printer is a Brother HL 5270DN. It doesn't matter whether the
  printer is connected via USB or as network printer. In both cases the
  described bug does happen. The PPD I use is "Brother HL-5270DN BR-
  Script3", similar to the one at
  http://www.openprinting.org/download/PPD/Brother/BR5270_2_GPL.ppd

  I discovered this bug in up-to-date Debian unstable for several years
  already. Now I switched one of my laptops to Ubuntu Natty (fresh
  installation), and unfortunately discovered the same bug there as
  well.

  I'm pretty sure that this bug is related to bug #419143, and not
  really in CUPS, but rather in some library (poppler or cairo) used by
  GTK applications. The same PDFs that produce the described error in
  evince, print fine in okular.

  I attach an example PDF that doesn't print in evince, but prints fine
  in okular. It's sufficient to (try to) print page 1 of the document.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: cups 1.4.6-5ubuntu1.2
  ProcVersionSignature: Ubuntu 2.6.39-0.5~20110427-generic 2.6.39-rc5
  Uname: Linux 2.6.39-0-generic x86_64
  Architecture: amd64
  CupsErrorLog:
   
  Date: Tue Jun 28 13:13:29 2011
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110426)
  Lpstat: device for Brother-HL-5270DN: lpd://192.168.1.75/PASSTHRU
  MachineType: LENOVO 4180W1H
  Papersize: a4
  PpdFiles: Brother-HL-5270DN: Brother HL-5270DN BR-Script3
  ProcEnviron:
   LANGUAGE=de:en
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-2.6.39-0-generic 
root=/dev/mapper/vgsys-root ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/13/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 83ET56WW (1.26 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4180W1H
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr83ET56WW(1.26):bd05/13/2011:svnLENOVO:pn4180W1H:pvrThinkPadT420:rvnLENOVO:rn4180W1H:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4180W1H
  dmi.product.version: ThinkPad T420
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/802942/+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 1958267] Re: "Connection failed" for WPA Enterprise network eduroam

[Sebastien Bacher]

The unsafe legacy disabled suggests it could be bug #1963834 and a
choice from upstream openssl to disable unsafe servers, maybe that's
something the eduroam admins need to sort out?

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

Title:
  "Connection failed" for WPA Enterprise network eduroam

Status in wpa package in Ubuntu:
  New

Bug description:
  With the current jammy version of wpasupplicant (2:2.10-1), I cannot
  connect to the WPA Enterprise network eduroam, which is used by
  Universities worldwide. I get a "Connection failed" message or a
  request to re-enter the password.

  - I've re-tried the credentials: no fix ;-)

  - Tried a 21.10 live session on the same machine: works fine!

  - Manually downgraded wpasupplicant to the impish version
  (2:2.9.0-21build1): connected normally.

  - Upgraded wpasupplicant to the latest version: fails to connect
  again.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: wpasupplicant 2:2.10-1
  ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12
  Uname: Linux 5.15.0-17-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 18 09:56:23 2022
  InstallationDate: Installed on 2021-11-30 (48 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/+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 1944519] Re: Xubuntu shutdown prompt is missing

[Sean Davis]

I've added plymouth back to this bug since this issue was originally a
plymouth+casper bug that was reportedly fixed:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1942987

We've had several additional reports of this issue, and I've reproduced
it on two different machines in the last couple of days with Xubuntu
Jammy. As always, the text is not displayed, but hitting the enter key
will continue the reboot process.


** Also affects: plymouth (Ubuntu)
   Importance: Undecided
   Status: New

** Tags added: xubuntu

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

Title:
  Xubuntu shutdown prompt is missing

Status in Release Notes for Ubuntu:
  Fix Released
Status in casper package in Ubuntu:
  Confirmed
Status in plymouth package in Ubuntu:
  Confirmed

Bug description:
  Update: 2021-10-08 ISO issues appear with Xubuntu still; not with
  Ubuntu-MATE

  Live session shutdown prompt is missing - system reboots at once

  Testing Ubuntu Mate Impish ISO 22.09,2021

  Clicked restart now button after install and no shutdown prompt
  appeared - the system rebooted at once and I could then login as
  normal.

  Please see bug #1942987
  https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1942987 for
  history.

  I am filing this under plymouth - not sure if that is correct package.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: plymouth 0.9.5git20210406-0ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu69
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CurrentDesktop: MATE
  Date: Wed Sep 22 06:59:59 2021
  DefaultPlymouth: 
/usr/share/plymouth/themes/ubuntu-mate-logo/ubuntu-mate-logo.plymouth
  InstallationDate: Installed on 2021-09-22 (0 days ago)
  InstallationMedia: Ubuntu-MATE 21.10 "Impish Indri" - Beta amd64 (20210922)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 046d:c535 Logitech, Inc. Dell Wireless Mouse WM123
   Bus 001 Device 004: ID 04f2:0402 Chicony Electronics Co., Ltd Genius 
LuxeMate i200 Keyboard
   Bus 001 Device 002: ID 1a40:0101 Terminus Technology Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. OptiPlex 7040
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-16-generic 
root=UUID=731e4ccb-cceb-48e4-bbda-f97dbe3b6f40 ro quiet splash vt.handoff=7
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-16-generic 
root=UUID=731e4ccb-cceb-48e4-bbda-f97dbe3b6f40 ro quiet splash vt.handoff=7
  SourcePackage: plymouth
  TextPlymouth: 
/usr/share/plymouth/themes/ubuntu-mate-text/ubuntu-mate-text.plymouth
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/23/2020
  dmi.bios.release: 1.18
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.18.1
  dmi.board.name: 0Y7WYT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.18.1:bd12/23/2020:br1.18:svnDellInc.:pnOptiPlex7040:pvr:sku06B9:rvnDellInc.:rn0Y7WYT:rvrA00:cvnDellInc.:ct3:cvr:
  dmi.product.family: OptiPlex
  dmi.product.name: OptiPlex 7040
  dmi.product.sku: 06B9
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1944519/+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 1964532] Re: /usr/libexec/udisks2/udisksd:malloc_consolidate(): unaligned fastbin chunk detected

[Sebastien Bacher]

Could someone having the issue attach the journalctl log from a session
where they had the crash to the bug?

** Changed in: udisks2 (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  /usr/libexec/udisks2/udisksd:malloc_consolidate(): unaligned fastbin
  chunk detected

Status in udisks2 package in Ubuntu:
  Incomplete

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
udisks2.  This problem was most recently seen with package version 2.9.4-1, the 
problem page at 
https://errors.ubuntu.com/problem/ee70e42ef96a41e0ae118869c75b7cc675ae974c 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1964532/+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 1901752] Re: Can’t connect to a specific Wi-Fi network with wpa_supplicant

[Sebastien Bacher]

Thank you for your bug report, do you have details on what sort of
configuration and security options is eduroam using?

Could you edit /lib/systemd/system/wpa_supplicant.service to add a '-d'
to the ExecStart cmd, restart, try to connect and share the 'journalctl
-b 0' log from the system?


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

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

Title:
  Can’t connect to a specific Wi-Fi network with wpa_supplicant

Status in wpa package in Ubuntu:
  Incomplete

Bug description:
  This is the error I get if I try to connect to a specific Wi-Fi
  network on Ubuntu 20.10 with wpa_supplicant:

  Error: Connection activation failed: (7) Secrets were required, but
  not provided.

  If I use iwd instead, everything works fine.

  I also can connect to other networks with wpa_supplicant.

  I had the same issue with the Live USB.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: wpasupplicant 2:2.9-1ubuntu8
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: i3
  Date: Tue Oct 27 20:55:39 2020
  InstallationDate: Installed on 2020-10-26 (1 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1901752/+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 1964100] Re: Cannot connect to open WLAN with 1.36.0-1ubuntu2 on Jammy

[Sebastien Bacher]

Could you try if that's an issue under GNOME? There is a similar report
on https://forum.endeavouros.com/t/wpa3-networkmanager-plasma-nm-
weirdness/10439 which suggests it could be an issue with plasma

** Changed in: network-manager (Ubuntu)
   Status: New => Incomplete

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

Title:
  Cannot connect to open WLAN with 1.36.0-1ubuntu2 on Jammy

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  I'm trying to connect to an open (i.e. no ecryption) WLAN with
  network-manager 1.36.0-1ubuntu2 on 22.04 but it's failing with the
  following error message (after selecting the network from the network-
  manager applet prompt):

  Mär 08 10:50:04 Isaac-Laptop NetworkManager[31754]: 
  [1646733004.4425] audit: op="connection-add-activate" pid=12122
  uid=1000 result="fail" reason="802-11-wireless-security.key-mgmt:
  Access point does not support PSK but setting requires it"

  I haven't changed any of the default settings for network-manager and
  this network worked on 20.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1964100/+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 1958267] Re: "Connection failed" for WPA Enterprise network eduroam

[Sebastien Bacher]

bug #1962541 seems a bit similar though the log here includes

> OpenSSL: openssl_handshake - SSL_connect error:0A000152:SSL
routines::unsafe legacy renegotiation disabled

I've reported it upstream now on
http://lists.infradead.org/pipermail/hostap/2022-March/040305.html

** Tags added: openssl3

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

Title:
  "Connection failed" for WPA Enterprise network eduroam

Status in wpa package in Ubuntu:
  New

Bug description:
  With the current jammy version of wpasupplicant (2:2.10-1), I cannot
  connect to the WPA Enterprise network eduroam, which is used by
  Universities worldwide. I get a "Connection failed" message or a
  request to re-enter the password.

  - I've re-tried the credentials: no fix ;-)

  - Tried a 21.10 live session on the same machine: works fine!

  - Manually downgraded wpasupplicant to the impish version
  (2:2.9.0-21build1): connected normally.

  - Upgraded wpasupplicant to the latest version: fails to connect
  again.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: wpasupplicant 2:2.10-1
  ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12
  Uname: Linux 5.15.0-17-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 18 09:56:23 2022
  InstallationDate: Installed on 2021-11-30 (48 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/+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 1962541] Re: PEAP wifi can't connect (ubuntu live/installer is also not working

[Sebastien Bacher]

bug #1958267 is also a similar issue

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

Title:
  PEAP wifi can't connect (ubuntu live/installer is also not working

Status in wpa package in Ubuntu:
  Triaged

Bug description:
  WPA2 enterprise can't connect PEAP
  ubuntu 22.04 live/installer is not working too

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntu-release-upgrader-core 1:22.04.6
  Uname: Linux 5.16.0-kali1-amd64 x86_64
  ApportVersion: 2.20.11-0ubuntu78
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar  1 09:18:42 2022
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDistupgradeTermlog:
   
  mtime.conffile..etc.update-manager.release-upgrades: 
2022-02-27T21:07:16.553410

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1962541/+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 1962541] Re: PEAP wifi can't connect (ubuntu live/installer is also not working

[Sebastien Bacher]

Thanks for the Debug log, I reported the issue upstream now on
http://lists.infradead.org/pipermail/hostap/2022-March/040304.html

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

Title:
  PEAP wifi can't connect (ubuntu live/installer is also not working

Status in wpa package in Ubuntu:
  Triaged

Bug description:
  WPA2 enterprise can't connect PEAP
  ubuntu 22.04 live/installer is not working too

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntu-release-upgrader-core 1:22.04.6
  Uname: Linux 5.16.0-kali1-amd64 x86_64
  ApportVersion: 2.20.11-0ubuntu78
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar  1 09:18:42 2022
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDistupgradeTermlog:
   
  mtime.conffile..etc.update-manager.release-upgrades: 
2022-02-27T21:07:16.553410

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1962541/+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 1962541] Re: PEAP wifi can't connect (ubuntu live/installer is also not working

[Sebastien Bacher]

** Package changed: network-manager (Ubuntu) => wpa (Ubuntu)

** Changed in: wpa (Ubuntu)
   Status: Incomplete => Triaged

** Tags added: rls-jj-incoming

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

Title:
  PEAP wifi can't connect (ubuntu live/installer is also not working

Status in wpa package in Ubuntu:
  Triaged

Bug description:
  WPA2 enterprise can't connect PEAP
  ubuntu 22.04 live/installer is not working too

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntu-release-upgrader-core 1:22.04.6
  Uname: Linux 5.16.0-kali1-amd64 x86_64
  ApportVersion: 2.20.11-0ubuntu78
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar  1 09:18:42 2022
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDistupgradeTermlog:
   
  mtime.conffile..etc.update-manager.release-upgrades: 
2022-02-27T21:07:16.553410

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1962541/+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 1965113] Re: Desktop snaps don't start at all in Xorg sessions if a Wayland session has been used

[Sebastien Bacher]

** Changed in: gnome-session (Ubuntu)
   Status: New => Triaged

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

Title:
  Desktop snaps don't start at all in Xorg sessions if a Wayland session
  has been used

Status in gnome-session:
  Unknown
Status in Snapcraft:
  New
Status in gnome-session package in Ubuntu:
  Triaged

Bug description:
  Firefox 98.0.1-2 snap doesn't start at all in Xorg sessions.

  $ /snap/bin/firefox
  Error: cannot open display: :0

  $ echo $DISPLAY
  :0

  And other X11 apps still work just fine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-session/+bug/1965113/+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 1961859] Re: When we install ModemManager1.16.6 and others, this will lead to ubuntu can not enter into GNOME UI.

[Sebastien Bacher]

The logs aren't really going to help there, we need someone having the
issue to run the cmd from #10, the one in comment #12 doesn't show the
issue so it was not done in an environment showing the problem

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

Title:
  When we install ModemManager1.16.6 and others, this will lead to
  ubuntu can not enter into GNOME UI.

Status in modemmanager package in Ubuntu:
  Incomplete

Bug description:
  1. We use sourcecode to install ModemManger1.16.6
  2. Ubuntu can not enter UI.
  3. We capture log and picture and add these on the attachment.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1961859/+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 1965072] Re: In Xorg sessions, desktop icons flicker when entering the overview

[Daniel van Vugt]

Fix proposed: https://gitlab.gnome.org/GNOME/gnome-
shell/-/merge_requests/2244

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

Title:
  In Xorg sessions, desktop icons flicker when entering the overview

Status in gnome-shell package in Ubuntu:
  In Progress
Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu:
  In Progress

Bug description:
  In Xorg sessions, desktop icons flicker when entering the overview.

  I think this is a combination of a new feature in DING:

https://gitlab.com/rastersoft/desktop-icons-
  ng/-/commit/6ab838e832b3771

  and an old problem where desktop icon fading is only implemented for
  Xorg sessions, as shown in:

https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1395
(see also https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1070)

  If DING intends to make the icons vanish immediately then also fading
  them in Xorg sessions may be causing them to disappear and then
  reappear to fade out.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell-extension-desktop-icons-ng 39-2ubuntu1 [modified: 
usr/share/gnome-shell/extensions/d...@rastersoft.com/extension.js]
  ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
  Uname: Linux 5.15.0-22-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Wed Mar 16 10:29:21 2022
  InstallationDate: Installed on 2021-11-05 (130 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211103)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-desktop-icons-ng
  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/1965072/+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 1961859] Re: When we install ModemManager1.16.6 and others, this will lead to ubuntu can not enter into GNOME UI.

[LeoLin]

Hi @Sebastien Bacher, could you help to check logs from DengYi provided
then kindly reply some suggestion?

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

Title:
  When we install ModemManager1.16.6 and others, this will lead to
  ubuntu can not enter into GNOME UI.

Status in modemmanager package in Ubuntu:
  Incomplete

Bug description:
  1. We use sourcecode to install ModemManger1.16.6
  2. Ubuntu can not enter UI.
  3. We capture log and picture and add these on the attachment.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1961859/+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 1965072] Re: In Xorg sessions, desktop icons flicker when entering the overview

[Daniel van Vugt]

** Changed in: gnome-shell (Ubuntu)
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

** Changed in: gnome-shell-extension-desktop-icons-ng (Ubuntu)
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

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

** Changed in: gnome-shell-extension-desktop-icons-ng (Ubuntu)
   Importance: Undecided => Low

** Changed in: gnome-shell (Ubuntu)
   Status: New => In Progress

** Changed in: gnome-shell-extension-desktop-icons-ng (Ubuntu)
   Status: New => In Progress

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

Title:
  In Xorg sessions, desktop icons flicker when entering the overview

Status in gnome-shell package in Ubuntu:
  In Progress
Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu:
  In Progress

Bug description:
  In Xorg sessions, desktop icons flicker when entering the overview.

  I think this is a combination of a new feature in DING:

https://gitlab.com/rastersoft/desktop-icons-
  ng/-/commit/6ab838e832b3771

  and an old problem where desktop icon fading is only implemented for
  Xorg sessions, as shown in:

https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1395
(see also https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1070)

  If DING intends to make the icons vanish immediately then also fading
  them in Xorg sessions may be causing them to disappear and then
  reappear to fade out.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell-extension-desktop-icons-ng 39-2ubuntu1 [modified: 
usr/share/gnome-shell/extensions/d...@rastersoft.com/extension.js]
  ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
  Uname: Linux 5.15.0-22-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Wed Mar 16 10:29:21 2022
  InstallationDate: Installed on 2021-11-05 (130 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211103)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-desktop-icons-ng
  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/1965072/+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 1964037] Re: gnome-shell crashes when attempting to enable second monitor on second GPU (Nvidia >= 495) in a Wayland session

[Daniel van Vugt]

Using the main branches:

#0  0x7f3255a9fccf in g_log_structured_array ()
at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f3255a9ff99 in g_log_default_handler ()
at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x5618851da1fd in default_log_handler
(log_domain=0x7f3254e5b2c6 "mutter", log_level=6, message=0x5618885d6810 
"Failed to create fallback offscreen framebuffer: Failed to create texture 2d 
due to size/format constraints", data=0x0) at ../src/main.c:297
#3  0x7f3255aa13fa in g_logv () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f3255aa16e3 in g_log () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f3254dfec77 in create_fallback_offscreen
(renderer_native=0x561885ea18f0, cogl_context=0x5618861d2750, width=1920, 
height=1200) at ../src/backends/native/meta-renderer-native.c:1213
#6  0x7f3254dfef76 in meta_renderer_native_create_view
(renderer=0x561885ea18f0, logical_monitor=0x561886d4f540, 
output=0x56188865d4a0, crtc=0x7f320018a610) at 
../src/backends/native/meta-renderer-native.c:1288
#7  0x7f3254c9a75d in meta_renderer_create_view
(renderer=0x561885ea18f0, logical_monitor=0x561886d4f540, 
output=0x56188865d4a0, crtc=0x7f320018a610) at 
../src/backends/meta-renderer.c:102
#8  0x7f3254c9a7cd in create_crtc_view
(logical_monitor=0x561886d4f540, monitor=0x561888572e80, 
output=0x56188865d4a0, crtc=0x7f320018a610, user_data=0x561885ea18f0)
at ../src/backends/meta-renderer.c:133
#9  0x7f3254c7ec1b in foreach_crtc
(monitor=0x561888572e80, mode=0x56188772e740, 
monitor_crtc_mode=0x56188621d670, user_data=0x7fffdc9b9760, error=0x0)
at ../src/backends/meta-logical-monitor.c:247
#10 0x7f3254c82d04 in meta_monitor_mode_foreach_crtc
(monitor=0x561888572e80, mode=0x56188772e740, func=0x7f3254c7ebb4 
, user_data=0x7fffdc9b9760, error=0x0)
at ../src/backends/meta-monitor.c:1955
#11 0x7f3254c7ecb5 in meta_logical_monitor_foreach_crtc
(logical_monitor=0x561886d4f540, func=0x7f3254c9a78d , 
user_data=0x561885ea18f0) at ../src/backends/meta-logical-monitor.c:274
#12 0x7f3254c9a8ee in meta_renderer_real_rebuild_views
(renderer=0x561885ea18f0) at ../src/backends/meta-renderer.c:168
#13 0x7f3254dff4c8 in meta_renderer_native_rebuild_views
(renderer=0x561885ea18f0)
at ../src/backends/native/meta-renderer-native.c:1422
#14 0x7f3254c9a78b in meta_renderer_rebuild_views (renderer=0x561885ea18f0)
at ../src/backends/meta-renderer.c:120
#15 0x7f3254e0ab20 in meta_stage_native_rebuild_views
(stage_native=0x5618860ff500)
at ../src/backends/native/meta-stage-native.c:66
#16 0x7f3254dc7e1b in meta_backend_native_update_screen_size
(backend=0x561885ded120, width=5043, height=3360)
at ../src/backends/native/meta-backend-native.c:411
#17 0x7f3254c6d7e7 in meta_backend_sync_screen_size
(backend=0x561885ded120) at ../src/backends/meta-backend.c:285
#18 0x7f3254c6da07 in meta_backend_monitors_changed 
(backend=0x561885ded120) at ../src/backends/meta-backend.c:356
#19 0x7f3254c946a3 in meta_monitor_manager_notify_monitors_changed 
(manager=0x561885df0340) at ../src/backends/meta-monitor-manager.c:3476
#20 0x7f3254c948f9 in meta_monitor_manager_rebuild (manager=0x561885df0340, 
config=0x561886083e80) at ../src/backends/meta-monitor-manager.c:3566
#21 0x7f3254ddc7b1 in meta_monitor_manager_native_apply_monitors_config 
(manager=0x561885df0340, config=0x561886083e80, 
method=META_MONITORS_CONFIG_METHOD_PERSISTENT, error=0x7fffdc9b9a60) at 
../src/backends/native/meta-monitor-manager-native.c:348
#22 0x7f3254c8e639 in meta_monitor_manager_apply_monitors_config 
(manager=0x561885df0340, config=0x561886083e80, 
method=META_MONITORS_CONFIG_METHOD_PERSISTENT, error=0x7fffdc9b9a60) at 
../src/backends/meta-monitor-manager.c:635
#23 0x7f3254c8e836 in meta_monitor_manager_ensure_configured 
(manager=0x561885df0340) at ../src/backends/meta-monitor-manager.c:708
#24 0x7f3254c94a49 in meta_monitor_manager_reconfigure 
(manager=0x561885df0340) at ../src/backends/meta-monitor-manager.c:3622
#25 0x7f3254c94a74 in meta_monitor_manager_reload (manager=0x561885df0340) 
at ../src/backends/meta-monitor-manager.c:3629
#26 0x7f3254ddcd99 in handle_hotplug_event (manager=0x561885df0340) at 
../src/backends/native/meta-monitor-manager-native.c:502
#27 0x7f3254ddce40 in on_kms_resources_changed (kms=0x561885def9c0, 
changes=META_KMS_UPDATE_CHANGE_FULL, manager=0x561885df0340) at 
../src/backends/native/meta-monitor-manager-native.c:538
#28 0x7f3255b90376 in g_cclosure_marshal_VOID__FLAGSv () at 
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#29 0x7f3255baf640 in g_signal_emit_valist () at 
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#30 0x7f3255baf7a3 in g_signal_emit () at 
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#31 0x7f3254df2a37 in handle_hotplug_event (kms=0x561885def9c0, 
udev_device=0x561887a9f340, changes=META_KMS_UPDATE_CHANGE_FULL) at 

[Desktop-packages] [Bug 1965188] Re: Policies not being picked up anymore

[Michael]

If I install `chrome` (instead of snap chromium), and place the policy
in the documented location
(https://www.chromium.org/administrators/linux-quick-start/), then it
works first time like a charm. Whereas last night (I spent 6 hours
between 8pm and 2am trying to get it to work with the snap version), but
to me it felt like I was shooting in the dark. There must be something I
am missing, in which case if this is documented and sorted out, I
apologise.

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

Title:
  Policies not being picked up anymore

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Description: Ubuntu 20.04.4 LTS
  Release: 20.04

  chromium 99.0.4844.51 1926 latest/stable canonical✓

  I think with Chrome 99 manged policies in a json file are broken, they
  no longer seem to be picked up (used to work for me which a script I
  wrote). When one follows Chrome's documentation to use policies, it
  does not work: https://www.chromium.org/administrators/linux-quick-
  start/

  If snap mutates various path's and changes various things, I hope this
  layer of obfuscation is documented somewhere? I could not find it.

  Similar to this issue but none of the paths in this issue work for me anymore:
  https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1714244

  I have tried many combos of dirs/permissions from stackoverflow and
  bug reports but they don't seem to work.

  I don't know what snap is doing to Chromium behind the scenes, and
  perhaps it seems undocumented? Apologies if it is documentented (but
  can't find it).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1965188/+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 1714244] Re: [snap] apparmor denials on /etc/chromium-browser/policies/

[Michael]

According to the official docs:
https://www.chromium.org/administrators/linux-quick-start/

The path should be `/etc/chromium`

If the Ubuntu package maintainers move the path, how do people know
where the new path is?

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

Title:
  [snap] apparmor denials on /etc/chromium-browser/policies/

Status in chromium-browser package in Ubuntu:
  Fix Committed

Bug description:
  [1565519.440403] audit: type=1400 audit(1504185084.568:68574811):
  apparmor="ALLOWED" operation="open" profile="snap.chromium.chromium"
  name="/etc/chromium-browser/policies/managed/" pid=19433
  comm="chromium-browse" requested_mask="r" denied_mask="r" fsuid=1000
  ouid=0

  [1565519.440527] audit: type=1400 audit(1504185084.568:68574812):
  apparmor="ALLOWED" operation="open" profile="snap.chromium.chromium"
  name="/etc/chromium-browser/policies/recommended/" pid=19433
  comm="chromium-browse" requested_mask="r" denied_mask="r" fsuid=1000
  ouid=0

  Those denials don't appear to prevent the app from running. Still,
  they should be investigated and fixed if possible.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1714244/+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 1902464] Re: The rear panel of Lenovo P620 doesn't support more than one audio device at the same time

[Alex Tu]

** Changed in: oem-priority
   Importance: Undecided => Critical

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

Title:
  The rear panel of Lenovo P620 doesn't support more than one audio
  device at the same time

Status in HWE Next:
  New
Status in OEM Priority Project:
  Confirmed
Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  After backporting following patches from PA and alsa-ucm-conf and then
  it works.

  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/290
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/354
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/355

  https://github.com/alsa-project/alsa-ucm-conf/tree/master/ucm2/USB-
  Audio [landed by aa74f4c12eefcc98582572d2fc48982cf7478b51]

  Here is the test PPA:
  https://launchpad.net/~os369510/+archive/ubuntu/oem-package-test

  Since the upstream not yet accepted those patches, the regression
  potential may quite high.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1902464/+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 1965219] Re: gnome lock screen does not permit reentering password

[Daniel van Vugt]

You might be able to recover with something like:

  killall gnome-shell

or

  killall -9 gnome-shell

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

Title:
  gnome lock screen does not permit reentering password

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Initially, only the mouse works in the gnome lock screen, without any
  way to get a password prompt.  It's likely only happening when
  returning from suspend with lid open.

  It's possible to ssh into the machine or to press Fn+Ctrl+Alt+F?? and
  login without gnome.  After this, Fn+Ctrl+Alt+F1 brings up a purple
  ubuntu login screen, but then after login you simply return to the
  lock screen with no working keyboard.  I never found any method to
  force unlock from ssh or another vt though, so this always still
  required a reboot, or killing all of gnome.

  I've randomly tried some solutions from
  https://askubuntu.com/questions/1242110/after-upgrading-to-
  ubuntu-20-04-lockscreen-not-working  including reinstalling many gnome
  components.  After this, the behavior initially disappeared by
  returning from suspend merely took a long time, like 30 seconds or 1
  minute.  It's possible the delay stems from memory size, but a
  previous identical lenovo x1 had no such problems.

  I've now a worse problem just a few hours later where unsuspend went
  directly to a purple ubuntu login screen, but neither the mouse nor
  keyboard worked.  I've not yet been able to test ssh on this problem.

  It's possibly all connected to recent firmware upgrades, so I'm happy
  to try downgrading the firmware, but I've not found any instructions
  on doing so, or even identifying the firmware upgrade log.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.14.0-1027.30-oem 5.14.21
  Uname: Linux 5.14.0-1027-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 17 03:44:49 2022
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-sutton-focal-amd64-20210412-218+sutton-newell-focal-amd64+X00
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Occurs more often under certain circumstances
  GpuHangStarted: Within the last week or two
  GraphicsCard:
   Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:22d5]
  InstallationDate: Installed on 2021-04-15 (335 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20210412-22:07
  MachineType: LENOVO 20XWCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1027-oem 
root=UUID=6a411137-06bb-4de1-be93-c2fcd4f44a5a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/02/2021
  dmi.bios.release: 1.51
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N32ET75W (1.51 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20XWCTO1WW
  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.32
  dmi.modalias: 
dmi:bvnLENOVO:bvrN32ET75W(1.51):bd12/02/2021:br1.51:efr1.32:svnLENOVO:pn20XWCTO1WW:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XWCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9:
  dmi.product.family: ThinkPad X1 Carbon Gen 9
  dmi.product.name: 20XWCTO1WW
  dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9
  dmi.product.version: ThinkPad X1 Carbon Gen 9
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


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

[Desktop-packages] [Bug 1965219] Re: gnome lock screen does not permit reentering password

[Daniel van Vugt]

The lock screen is rendered by the gnome-shell process (which then sends
the image to Xorg for display in the case of a Xorg session). gdm3 does
nothing graphical, only launches other programs. Even the login screen
is rendered by a gnome-shell process.

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

Title:
  gnome lock screen does not permit reentering password

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Initially, only the mouse works in the gnome lock screen, without any
  way to get a password prompt.  It's likely only happening when
  returning from suspend with lid open.

  It's possible to ssh into the machine or to press Fn+Ctrl+Alt+F?? and
  login without gnome.  After this, Fn+Ctrl+Alt+F1 brings up a purple
  ubuntu login screen, but then after login you simply return to the
  lock screen with no working keyboard.  I never found any method to
  force unlock from ssh or another vt though, so this always still
  required a reboot, or killing all of gnome.

  I've randomly tried some solutions from
  https://askubuntu.com/questions/1242110/after-upgrading-to-
  ubuntu-20-04-lockscreen-not-working  including reinstalling many gnome
  components.  After this, the behavior initially disappeared by
  returning from suspend merely took a long time, like 30 seconds or 1
  minute.  It's possible the delay stems from memory size, but a
  previous identical lenovo x1 had no such problems.

  I've now a worse problem just a few hours later where unsuspend went
  directly to a purple ubuntu login screen, but neither the mouse nor
  keyboard worked.  I've not yet been able to test ssh on this problem.

  It's possibly all connected to recent firmware upgrades, so I'm happy
  to try downgrading the firmware, but I've not found any instructions
  on doing so, or even identifying the firmware upgrade log.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.14.0-1027.30-oem 5.14.21
  Uname: Linux 5.14.0-1027-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 17 03:44:49 2022
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-sutton-focal-amd64-20210412-218+sutton-newell-focal-amd64+X00
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Occurs more often under certain circumstances
  GpuHangStarted: Within the last week or two
  GraphicsCard:
   Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:22d5]
  InstallationDate: Installed on 2021-04-15 (335 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20210412-22:07
  MachineType: LENOVO 20XWCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1027-oem 
root=UUID=6a411137-06bb-4de1-be93-c2fcd4f44a5a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/02/2021
  dmi.bios.release: 1.51
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N32ET75W (1.51 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20XWCTO1WW
  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.32
  dmi.modalias: 
dmi:bvnLENOVO:bvrN32ET75W(1.51):bd12/02/2021:br1.51:efr1.32:svnLENOVO:pn20XWCTO1WW:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XWCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9:
  dmi.product.family: ThinkPad X1 Carbon Gen 9
  dmi.product.name: 20XWCTO1WW
  dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9
  dmi.product.version: ThinkPad X1 Carbon Gen 9
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1795649] Re: evince from snap doesn't save position in pdf document

[Sebastien Bacher]

** Changed in: evince (Ubuntu)
   Importance: Undecided => Low

** Also affects: evince via
   https://gitlab.gnome.org/GNOME/evince/-/issues/1642
   Importance: Unknown
   Status: Unknown

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

Title:
  evince from snap doesn't save position in pdf document

Status in Evince:
  Unknown
Status in evince package in Ubuntu:
  Confirmed

Bug description:
  I've installed evince 3.30.0 (46) via "sudo snap install evince" on
  Ubuntu 18.04. Every time I'm running evince and opening pdf document,
  it opens the document on the first page, though I closed the document
  on the different page.

  I can't reproduce that issue with evince installed via apt, so I think
  this is a snap-specific issue.

  Also, every time I'm opening the document, evince prints the error:
  Error registering document: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.gnome.evince.Daemon was not provided by any .service files

To manage notifications about this bug go to:
https://bugs.launchpad.net/evince/+bug/1795649/+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 1960387] Re: fprintd crashed with SIGSEGV in log_v() from usbi_log() from libusb_unref_device()

[Sebastien Bacher]

** Changed in: libusb (Ubuntu)
   Status: Confirmed => Fix Committed

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

Title:
  fprintd crashed with SIGSEGV in log_v() from usbi_log() from
  libusb_unref_device()

Status in libusb:
  New
Status in fprintd package in Ubuntu:
  Won't Fix
Status in libusb package in Ubuntu:
  Fix Committed

Bug description:
  +

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: fprintd 1.94.1-1
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Uname: Linux 5.15.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu76
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Mon Feb  7 21:58:32 2022
  ExecutablePath: /usr/libexec/fprintd
  InstallationDate: Installed on 2021-12-21 (50 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  ProcCmdline: /usr/libexec/fprintd
  ProcEnviron:
   LANG=ru_RU.UTF-8
   PATH=(custom, no user)
  SegvAnalysis:
   Segfault happened at: 0x7fd8a7a3855f:call   *%rax
   PC (0x7fd8a7a3855f) ok
   source "*%rax" (0xd86d54af5d1db0f9) not located in a known VMA region 
(needed readable region)!
   destination "(%rsp)" (0x7ffdceacc590) ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: fprintd
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libusb-1.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libusb-1.0.so.0
   libusb_unref_device () from /lib/x86_64-linux-gnu/libusb-1.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgusb.so.2
   g_object_unref () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: fprintd crashed with SIGSEGV in libusb_unref_device()
  UpgradeStatus: Upgraded to jammy on 2022-01-16 (23 days ago)
  UserGroups: N/A
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/libusb/+bug/1960387/+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 1965219] Re: gnome lock screen does not permit reentering password

[Jeff Burdges]

It's only the three built in extensions installed.

Thanks I'll run  journalctl -b-1 > prevboot.txt  next time.

ls /var/crash/ says

_usr_lib_systemd_systemd-timesyncd.102.crash
_usr_lib_systemd_systemd-timesyncd.102.upload
_usr_lib_systemd_systemd-timesyncd.102.uploaded


I only see a similar error on 

https://errors.ubuntu.com/user/f1e063bb5e8c4439fa13d51f06f02ce6ad03d098946e7597fd170a17325d98a76475f94a90f27677619cb85b6c0bd1cc406eece2601001754138f20d7209c37a

Is the lock screen handled by gnome-shell itself or some outside process
like gdm3?  If there some signal or whatever I can send to gnome-shell

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

Title:
  gnome lock screen does not permit reentering password

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Initially, only the mouse works in the gnome lock screen, without any
  way to get a password prompt.  It's likely only happening when
  returning from suspend with lid open.

  It's possible to ssh into the machine or to press Fn+Ctrl+Alt+F?? and
  login without gnome.  After this, Fn+Ctrl+Alt+F1 brings up a purple
  ubuntu login screen, but then after login you simply return to the
  lock screen with no working keyboard.  I never found any method to
  force unlock from ssh or another vt though, so this always still
  required a reboot, or killing all of gnome.

  I've randomly tried some solutions from
  https://askubuntu.com/questions/1242110/after-upgrading-to-
  ubuntu-20-04-lockscreen-not-working  including reinstalling many gnome
  components.  After this, the behavior initially disappeared by
  returning from suspend merely took a long time, like 30 seconds or 1
  minute.  It's possible the delay stems from memory size, but a
  previous identical lenovo x1 had no such problems.

  I've now a worse problem just a few hours later where unsuspend went
  directly to a purple ubuntu login screen, but neither the mouse nor
  keyboard worked.  I've not yet been able to test ssh on this problem.

  It's possibly all connected to recent firmware upgrades, so I'm happy
  to try downgrading the firmware, but I've not found any instructions
  on doing so, or even identifying the firmware upgrade log.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.14.0-1027.30-oem 5.14.21
  Uname: Linux 5.14.0-1027-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 17 03:44:49 2022
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-sutton-focal-amd64-20210412-218+sutton-newell-focal-amd64+X00
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Occurs more often under certain circumstances
  GpuHangStarted: Within the last week or two
  GraphicsCard:
   Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:22d5]
  InstallationDate: Installed on 2021-04-15 (335 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20210412-22:07
  MachineType: LENOVO 20XWCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1027-oem 
root=UUID=6a411137-06bb-4de1-be93-c2fcd4f44a5a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/02/2021
  dmi.bios.release: 1.51
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N32ET75W (1.51 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20XWCTO1WW
  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.32
  dmi.modalias: 
dmi:bvnLENOVO:bvrN32ET75W(1.51):bd12/02/2021:br1.51:efr1.32:svnLENOVO:pn20XWCTO1WW:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XWCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9:
  dmi.product.family: ThinkPad X1 Carbon Gen 9
  dmi.product.name: 20XWCTO1WW
  dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9
  dmi.product.version: ThinkPad X1 Carbon Gen 9
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 

[Desktop-packages] [Bug 1964541] Re: Cannot rearrange Firefox (snap) browser tabs in Wayland sessions

[Daniel van Vugt]

** Changed in: firefox (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  Cannot rearrange Firefox (snap) browser tabs in Wayland sessions

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  Since 42~beta-1ubuntu1, and still present in 42~beta-1ubuntu2,
  attempting to re-arrange tabs in Firefox fails. Click and drag the tab
  and release, nothing changes. The next click to the tab is ignored.

  syslog has the following:

  Mar 11 13:06:47 desktop firefox[2192]: Attempting to add a widget with type 
GtkWindow to a container of type GtkWindow, but the widget is already inside a 
container of type GtkWindow, please remove the widget from its existing 
container first.
  Mar 11 13:06:48 desktop firefox[2192]: Attempting to add a widget with type 
GtkWindow to a container of type GtkWindow, but the widget is already inside a 
container of type GtkWindow, please remove the widget from its existing 
container first.
  Mar 11 13:06:50 desktop firefox[2192]: Attempting to add a widget with type 
GtkWindow to a container of type GtkWindow, but the widget is already inside a 
container of type GtkWindow, please remove the widget from its existing 
container first.
  Mar 11 13:06:51 desktop firefox[2192]: Attempting to add a widget with type 
GtkWindow to a container of type GtkWindow, but the widget is already inside a 
container of type GtkWindow, please remove the widget from its existing 
container first.

  gnome-shell 42~beta-1ubuntu2
  Firefox Snap 98.0-3 (1073)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1964541/+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 1965113] Re: Desktop snaps don't start at all in Xorg sessions if a Wayland session has been used

[Daniel van Vugt]

** Changed in: gnome-session (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  Desktop snaps don't start at all in Xorg sessions if a Wayland session
  has been used

Status in gnome-session:
  Unknown
Status in Snapcraft:
  New
Status in gnome-session package in Ubuntu:
  New

Bug description:
  Firefox 98.0.1-2 snap doesn't start at all in Xorg sessions.

  $ /snap/bin/firefox
  Error: cannot open display: :0

  $ echo $DISPLAY
  :0

  And other X11 apps still work just fine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-session/+bug/1965113/+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 662840]

[R-bugs-h]

*** Bug 1759018 has been marked as a duplicate of this bug. ***

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

Title:
  Spell checking more than one language in Firefox

Status in Mozilla Firefox:
  In Progress
Status in firefox package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: firefox

  After upgrading to Ubuntu 10.10 x64 with Firefox 3.6.10 I lost Firefox
  capability to spell check for multiple languages in text forms. This
  is very annoying as I use two or three different languages in a single
  form when composing emails for example, and also switch between
  tabs/firefox windows to fill out forms in different languages, and now
  I have to switch between dictionaries back and forth. Never was an
  issue before.

  There is a need to set up multiple dictionaries/languages to be used
  at once for seamless spell check on a text form. Am I missing
  something?

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: firefox 3.6.10+build1+nobinonly-0ubuntu3
  ProcVersionSignature: Ubuntu 2.6.35-22.34-generic 2.6.35.4
  Uname: Linux 2.6.35-22-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  Date: Mon Oct 18 21:59:46 2010
  FirefoxPackages:
   firefox 3.6.10+build1+nobinonly-0ubuntu3
   firefox-gnome-support 3.6.10+build1+nobinonly-0ubuntu3
   firefox-branding 3.6.10+build1+nobinonly-0ubuntu3
   abroswer N/A
   abrowser-branding N/A
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
  ProcEnviron:
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: firefox

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/662840/+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 1558886] Re: gnome-shell crashed with SIGSEGV in _clutter_input_device_reset_scroll_info()

[Daniel van Vugt]

There are no crashes after 3.38 though, so I'm still hopeful this has
been fixed in Ubuntu 21.10 onward.


** No longer affects: mutter (Ubuntu Focal)

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

Title:
  gnome-shell crashed with SIGSEGV in
  _clutter_input_device_reset_scroll_info()

Status in Mutter:
  Unknown
Status in mutter package in Ubuntu:
  Fix Released

Bug description:
  [ Impact ]

  Using Ubuntu 16.04 and 20.04 LTS Beta release. Was using gnome-shell
  and using Chrome web browser when computer became unresponsive to any
  commands or mouse clicks. About 3-4 minutes later a crash report
  popped up on my screen. I clicked report and now I am reporting this
  as a new bug as I have never had this happen before on previous
  versions of Ubuntu. I was attempting to copy and save an image from
  Google Chrome when this happened.

  Similar crash still happening, as per
  https://errors.ubuntu.com/problem/fda12af21f79f7f1e23ab3cc830da47eca410baa

  

  [  Test case ]

  Run xinput and figure device IDs for your mouse.
  Run this evil script with 9 changed (be sure to change both) to your id:

for ((;;)) do xinput disable 9; echo Disabled; xinput enable 9; echo
  Enabled; done

  While the script runs, open some context menu in some program. It may require 
a few clicks due to evil script enabling/disabling mouse.
  This will sometimes crash GTK programs due to a mirror bug in GTK.

  GNOME Shell should not crash

  [ Regression potential ]

  Devices might be not be properly recognized when plugged and unplugged

  
  

  Description:  Ubuntu Xenial Xerus (development branch)
  Release:  16.04

  lostprophet@DigitalDamage:~$ apt-cache policy google-chrome-stable
  google-chrome-stable:
    Installed: 49.0.2623.75-1
    Candidate: 49.0.2623.75-1
    Version table:
   *** 49.0.2623.75-1 100
  100 /var/lib/dpkg/status

  ProblemType: CrashDistroRelease: Ubuntu 16.04
  Package: gnome-shell 3.18.4-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-14.30-generic 4.4.5
  Uname: Linux 4.4.0-14-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Mar 17 22:20:56 2016
  DisplayManager: lightdm
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2016-02-24 (22 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f634ba78320:mov0xe0(%rdi),%rax
   PC (0x7f634ba78320) ok
   source "0xe0(%rdi)" (0x00e0) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMASignal: 11SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0
   clutter_x11_handle_event () from 
/usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0
   ?? () from /usr/lib/libmutter.so.0
  Title: gnome-shell crashed with SIGSEGV in clutter_x11_handle_event()
  UpgradeStatus: Upgraded to xenial on 2016-03-03 (14 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1558886/+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 1558886] Re: gnome-shell crashed with SIGSEGV in _clutter_input_device_reset_scroll_info()

[Daniel van Vugt]

Still happening in 3.36.9 (bug 1965252 as well as thousands of reports
in
https://errors.ubuntu.com/problem/fda12af21f79f7f1e23ab3cc830da47eca410baa)

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

** Changed in: mutter (Ubuntu Focal)
 Assignee: Marco Trevisan (Treviño) (3v1n0) => (unassigned)

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

Title:
  gnome-shell crashed with SIGSEGV in
  _clutter_input_device_reset_scroll_info()

Status in Mutter:
  Unknown
Status in mutter package in Ubuntu:
  Fix Released

Bug description:
  [ Impact ]

  Using Ubuntu 16.04 and 20.04 LTS Beta release. Was using gnome-shell
  and using Chrome web browser when computer became unresponsive to any
  commands or mouse clicks. About 3-4 minutes later a crash report
  popped up on my screen. I clicked report and now I am reporting this
  as a new bug as I have never had this happen before on previous
  versions of Ubuntu. I was attempting to copy and save an image from
  Google Chrome when this happened.

  Similar crash still happening, as per
  https://errors.ubuntu.com/problem/fda12af21f79f7f1e23ab3cc830da47eca410baa

  

  [  Test case ]

  Run xinput and figure device IDs for your mouse.
  Run this evil script with 9 changed (be sure to change both) to your id:

for ((;;)) do xinput disable 9; echo Disabled; xinput enable 9; echo
  Enabled; done

  While the script runs, open some context menu in some program. It may require 
a few clicks due to evil script enabling/disabling mouse.
  This will sometimes crash GTK programs due to a mirror bug in GTK.

  GNOME Shell should not crash

  [ Regression potential ]

  Devices might be not be properly recognized when plugged and unplugged

  
  

  Description:  Ubuntu Xenial Xerus (development branch)
  Release:  16.04

  lostprophet@DigitalDamage:~$ apt-cache policy google-chrome-stable
  google-chrome-stable:
    Installed: 49.0.2623.75-1
    Candidate: 49.0.2623.75-1
    Version table:
   *** 49.0.2623.75-1 100
  100 /var/lib/dpkg/status

  ProblemType: CrashDistroRelease: Ubuntu 16.04
  Package: gnome-shell 3.18.4-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-14.30-generic 4.4.5
  Uname: Linux 4.4.0-14-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Mar 17 22:20:56 2016
  DisplayManager: lightdm
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2016-02-24 (22 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f634ba78320:mov0xe0(%rdi),%rax
   PC (0x7f634ba78320) ok
   source "0xe0(%rdi)" (0x00e0) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMASignal: 11SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0
   clutter_x11_handle_event () from 
/usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0
   ?? () from /usr/lib/libmutter.so.0
  Title: gnome-shell crashed with SIGSEGV in clutter_x11_handle_event()
  UpgradeStatus: Upgraded to xenial on 2016-03-03 (14 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1558886/+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 1809058] Re: gnome-shell crashed with SIGSEGV in _clutter_input_device_reset_scroll_info() from clutter_device_manager_xi2_translate_event() from clutter_backend_real_translate

[Daniel van Vugt]

*** This bug is a duplicate of bug 1558886 ***
https://bugs.launchpad.net/bugs/1558886

** This bug has been marked a duplicate of bug 1558886
   gnome-shell crashed with SIGSEGV in _clutter_input_device_reset_scroll_info()

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

Title:
  gnome-shell crashed with SIGSEGV in
  _clutter_input_device_reset_scroll_info() from
  clutter_device_manager_xi2_translate_event() from
  clutter_backend_real_translate_event() from clutter_x11_handle_event()
  from handle_host_xevent()

Status in gnome-shell package in Ubuntu:
  Fix Released

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
3.30.1-2ubuntu1.18.10.1, the problem page at 
https://errors.ubuntu.com/problem/aee56838cf05d6e1bf41d5249802782ca978ba03 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1809058/+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 1964037] Re: gnome-shell crashes when attempting to enable second monitor on second GPU (Nvidia >= 495) in a Wayland session

[Daniel van Vugt]

** Summary changed:

- gnome-shell crashes when attempting to enable second monitor
+ gnome-shell crashes when attempting to enable second monitor on second GPU 
(Nvidia >= 495) in a Wayland session

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

** Changed in: gnome-shell (Ubuntu)
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

** Changed in: gnome-shell (Ubuntu)
   Status: Invalid => Confirmed

** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #2182
   https://gitlab.gnome.org/GNOME/mutter/-/issues/2182

** Also affects: mutter via
   https://gitlab.gnome.org/GNOME/mutter/-/issues/2182
   Importance: Unknown
   Status: Unknown

** Information type changed from Private to Public

** Tags added: multimonitor

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

** Also affects: mutter (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: mutter (Ubuntu)
   Importance: Undecided => High

** Changed in: mutter (Ubuntu)
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

** Changed in: mutter (Ubuntu)
   Status: New => Triaged

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

Title:
  gnome-shell crashes when attempting to enable second monitor on second
  GPU (Nvidia >= 495) in a Wayland session

Status in Mutter:
  Unknown
Status in gnome-shell package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Triaged

Bug description:
  This is on my weird desktop setup, with one monitor plugged into an
  AMD card and one into an NVIDIA card.

  When using the Wayland session, by default Shell will come up on the
  monitor connected to the AMD card, and the second (NVIDIA) monitor
  will be blank. Attempting to enable the second monitor in Display
  Settings will immediately and reproducibly crash gnome-shell.

  This is trivial for me to reproduce, so if you need patches tested I
  can easily do so.

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 41.3-1ubuntu1
  ProcVersionSignature: Ubuntu 
5.15.0+bcachefs.git2026.1fa97551d-1.1-generic 5.15.2
  Uname: Linux 5.15.0+bcachefs.git2026.1fa97551d-1-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu78
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar  8 09:37:51 2022
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2021-11-02 (125 days ago)
  InstallationMedia: Ubuntu 21.10.0 2021.10.19 amd64 "bcachefs" (20211028)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=en_AU.UTF-8
   LANGUAGE=en_AU:en
   PATH=(custom, user)
   SHELL=/usr/bin/fish
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 41.3-3ubuntu1
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /lib/x86_64-linux-gnu/libmutter-9.so.0
   () at /lib/x86_64-linux-gnu/libmutter-9.so.0
   () at /lib/x86_64-linux-gnu/libmutter-9.so.0
   () at /lib/x86_64-linux-gnu/libmutter-9.so.0
   meta_monitor_mode_foreach_crtc () at /lib/x86_64-linux-gnu/libmutter-9.so.0
  Title: gnome-shell crashed with signal 5
  UpgradeStatus: Upgraded to jammy on 2021-11-02 (124 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1964037/+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 1962541] Re: PEAP wifi can't connect (ubuntu live/installer is also not working

[Guillaume Marmin]

I had edited the .service file but it was deleted when I reinstalled the ubuntu 
packages :-)
The new log is attached.

** Attachment added: "wpa_supplicant.log"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1962541/+attachment/5569942/+files/wpa_supplicant.log

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

Title:
  PEAP wifi can't connect (ubuntu live/installer is also not working

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  WPA2 enterprise can't connect PEAP
  ubuntu 22.04 live/installer is not working too

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntu-release-upgrader-core 1:22.04.6
  Uname: Linux 5.16.0-kali1-amd64 x86_64
  ApportVersion: 2.20.11-0ubuntu78
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar  1 09:18:42 2022
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDistupgradeTermlog:
   
  mtime.conffile..etc.update-manager.release-upgrades: 
2022-02-27T21:07:16.553410

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1962541/+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 1965251] Re: gnome-shell crashed with SIGBUS in disk_cache_has_key() from can_skip_compile() from can_skip_compile() from _mesa_glsl_compile_shader() from _mesa_compile_shader(

[Daniel van Vugt]

** Summary changed:

- 
/usr/bin/gnome-shell:7:disk_cache_has_key:can_skip_compile:can_skip_compile:_mesa_glsl_compile_shader:_mesa_compile_shader
+ gnome-shell crashed with SIGBUS in disk_cache_has_key() from 
can_skip_compile() from can_skip_compile() from _mesa_glsl_compile_shader() 
from _mesa_compile_shader()

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

Title:
  gnome-shell crashed with SIGBUS in disk_cache_has_key() from
  can_skip_compile() from can_skip_compile() from
  _mesa_glsl_compile_shader() from _mesa_compile_shader()

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
41.3-1ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/467a5181bf7cf0a579af4944e8d42945282b2af4 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965251/+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 1965251] [NEW] gnome-shell crashed with SIGBUS in disk_cache_has_key() from can_skip_compile() from can_skip_compile() from _mesa_glsl_compile_shader() from _mesa_compile_shade

[errors.ubuntu.com bug bridge]

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
41.3-1ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/467a5181bf7cf0a579af4944e8d42945282b2af4 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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


** Tags: bionic focal hirsute impish jammy

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

Title:
  gnome-shell crashed with SIGBUS in disk_cache_has_key() from
  can_skip_compile() from can_skip_compile() from
  _mesa_glsl_compile_shader() from _mesa_compile_shader()

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
41.3-1ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/467a5181bf7cf0a579af4944e8d42945282b2af4 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965251/+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 1965113] Re: Firefox 98.0.1-2 snap doesn't start at all in Xorg sessions if a Wayland session has been used

[Olivier Tilloy]

That's a known issue, see https://forum.snapcraft.io/t/cannot-open-
display-after-session-type-changed-wayland-x11/23838. The problem
appears to be partly in gnome-session
(https://gitlab.gnome.org/GNOME/gnome-session/-/issues/75), partly in
the snapcraft desktop extensions that assume a wayland session if
there's a lingering wayland socket
(https://github.com/snapcore/snapcraft/blob/main/extensions/desktop/common/desktop-
exports#L240).

It is not specific to the firefox snap, and it can be worked around by
running the apps with DISABLE_WAYLAND=1.

** Bug watch added: gitlab.gnome.org/GNOME/gnome-session/-/issues #75
   https://gitlab.gnome.org/GNOME/gnome-session/-/issues/75

** Package changed: firefox (Ubuntu) => gnome-session (Ubuntu)

** Also affects: gnome-session via
   https://gitlab.gnome.org/GNOME/gnome-session/-/issues/75
   Importance: Unknown
   Status: Unknown

** Also affects: snapcraft
   Importance: Undecided
   Status: New

** Summary changed:

- Firefox 98.0.1-2 snap doesn't start at all in Xorg sessions if a Wayland 
session has been used
+ Desktop snaps don't start at all in Xorg sessions if a Wayland session has 
been used

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

Title:
  Desktop snaps don't start at all in Xorg sessions if a Wayland session
  has been used

Status in gnome-session:
  Unknown
Status in Snapcraft:
  New
Status in gnome-session package in Ubuntu:
  New

Bug description:
  Firefox 98.0.1-2 snap doesn't start at all in Xorg sessions.

  $ /snap/bin/firefox
  Error: cannot open display: :0

  $ echo $DISPLAY
  :0

  And other X11 apps still work just fine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-session/+bug/1965113/+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 1959888] Re: Wayland sessions can't use external monitors that are connected to an Nvidia GPU with the proprietary driver

[Daniel van Vugt]

I've just tested with jammy again and it definitely fails with
Nvidia-510. The external monitor plugged into the secondary (Nvidia) GPU
doesn't light up for Wayland sessions, while the primary monitor (Intel)
works fine.

Although you need to have the monitor plugged in before logging in to
even get that far. If you try hotplugging a monitor on the secondary GPU
in a Wayland session then you get bug 1965246 instead. I've been aware
of it for quite some time but haven't yet got to triaging that crash.

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

Title:
  Wayland sessions can't use external monitors that are connected to an
  Nvidia GPU with the proprietary driver

Status in Mutter:
  Unknown
Status in OEM Priority Project:
  New
Status in mutter package in Ubuntu:
  In Progress

Bug description:
  When an external display is connected to my laptop, running Ubuntu
  22.04, the display is detected and I am sent to the login screen.
  After logging in again, the display is not running, although the
  primary laptop display works fine. The external monitor is looking for
  connection in that moment, which it never founds.

  The bug is tested on two Samsung monitors: S24R350FHUXEN and
  S22F350FHU.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Uname: Linux 5.15.0-18-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  495.46  Wed Oct 27 16:31:33 
UTC 2021
   GCC version:  gcc version 11.2.0 (Ubuntu 11.2.0-14ubuntu1)
  ApportVersion: 2.20.11-0ubuntu76
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb  3 13:25:04 2022
  DistUpgraded: 2022-01-13 15:37:13,056 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia/495.46, 5.15.0-17-generic, x86_64: installed
   nvidia/495.46, 5.15.0-18-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:086f]
 Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:086f]
  InstallationDate: Installed on 2021-09-09 (146 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Dell Inc. G3 3579
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-18-generic 
root=UUID=fd3be223-e609-4a8d-97fb-31ee2f754766 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to jammy on 2022-01-13 (20 days ago)
  dmi.bios.date: 04/20/2021
  dmi.bios.release: 1.15
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.15.0
  dmi.board.name: 0M5H57
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A05
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.0:bd04/20/2021:br1.15:svnDellInc.:pnG33579:pvr:rvnDellInc.:rn0M5H57:rvrA05:cvnDellInc.:ct10:cvr:sku086F:
  dmi.product.family: GSeries
  dmi.product.name: G3 3579
  dmi.product.sku: 086F
  dmi.sys.vendor: Dell Inc.
  nvidia-settings:
   ERROR: Unable to find display on any available system
   
   
   ERROR: Unable to find display on any available system
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.109-2ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.2-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.14-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-1build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1959888/+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 1965219] Re: gnome lock screen does not permit reentering password

[Daniel van Vugt]

Actually if you're using a Xorg session and only the mouse is working
then it's likely the gnome-shell process alone is hung or crashed.
Because the mouse movement is handled by Xorg, not gnome-shell.

Please:

1. Look in /var/crash for crash files and if found run:

ubuntu-bug YOURFILE.crash

   Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you find any links to recent problems on that page? If so then please
send the links to us.

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

Title:
  gnome lock screen does not permit reentering password

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Initially, only the mouse works in the gnome lock screen, without any
  way to get a password prompt.  It's likely only happening when
  returning from suspend with lid open.

  It's possible to ssh into the machine or to press Fn+Ctrl+Alt+F?? and
  login without gnome.  After this, Fn+Ctrl+Alt+F1 brings up a purple
  ubuntu login screen, but then after login you simply return to the
  lock screen with no working keyboard.  I never found any method to
  force unlock from ssh or another vt though, so this always still
  required a reboot, or killing all of gnome.

  I've randomly tried some solutions from
  https://askubuntu.com/questions/1242110/after-upgrading-to-
  ubuntu-20-04-lockscreen-not-working  including reinstalling many gnome
  components.  After this, the behavior initially disappeared by
  returning from suspend merely took a long time, like 30 seconds or 1
  minute.  It's possible the delay stems from memory size, but a
  previous identical lenovo x1 had no such problems.

  I've now a worse problem just a few hours later where unsuspend went
  directly to a purple ubuntu login screen, but neither the mouse nor
  keyboard worked.  I've not yet been able to test ssh on this problem.

  It's possibly all connected to recent firmware upgrades, so I'm happy
  to try downgrading the firmware, but I've not found any instructions
  on doing so, or even identifying the firmware upgrade log.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.14.0-1027.30-oem 5.14.21
  Uname: Linux 5.14.0-1027-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 17 03:44:49 2022
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-sutton-focal-amd64-20210412-218+sutton-newell-focal-amd64+X00
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Occurs more often under certain circumstances
  GpuHangStarted: Within the last week or two
  GraphicsCard:
   Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:22d5]
  InstallationDate: Installed on 2021-04-15 (335 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20210412-22:07
  MachineType: LENOVO 20XWCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1027-oem 
root=UUID=6a411137-06bb-4de1-be93-c2fcd4f44a5a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/02/2021
  dmi.bios.release: 1.51
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N32ET75W (1.51 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20XWCTO1WW
  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.32
  dmi.modalias: 
dmi:bvnLENOVO:bvrN32ET75W(1.51):bd12/02/2021:br1.51:efr1.32:svnLENOVO:pn20XWCTO1WW:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XWCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9:
  dmi.product.family: ThinkPad X1 Carbon Gen 9
  dmi.product.name: 20XWCTO1WW
  dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9
  dmi.product.version: ThinkPad X1 Carbon Gen 9
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2
  

[Desktop-packages] [Bug 1965219] Re: gnome lock screen does not permit reentering password

[Daniel van Vugt]

Thanks for the bug report.

Please open the 'Extensions' app and ensure no more than the three
built-in Ubuntu extensions are enabled. If any others are listed then
please disable/uninstall them and log in again.

Also next time the problem happens, after rebooting please run:

  journalctl -b-1 > prevboot.txt

and attach the resulting text file here.

** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu)

** Changed in: gnome-shell (Ubuntu)
   Status: New => Incomplete

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

Title:
  gnome lock screen does not permit reentering password

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Initially, only the mouse works in the gnome lock screen, without any
  way to get a password prompt.  It's likely only happening when
  returning from suspend with lid open.

  It's possible to ssh into the machine or to press Fn+Ctrl+Alt+F?? and
  login without gnome.  After this, Fn+Ctrl+Alt+F1 brings up a purple
  ubuntu login screen, but then after login you simply return to the
  lock screen with no working keyboard.  I never found any method to
  force unlock from ssh or another vt though, so this always still
  required a reboot, or killing all of gnome.

  I've randomly tried some solutions from
  https://askubuntu.com/questions/1242110/after-upgrading-to-
  ubuntu-20-04-lockscreen-not-working  including reinstalling many gnome
  components.  After this, the behavior initially disappeared by
  returning from suspend merely took a long time, like 30 seconds or 1
  minute.  It's possible the delay stems from memory size, but a
  previous identical lenovo x1 had no such problems.

  I've now a worse problem just a few hours later where unsuspend went
  directly to a purple ubuntu login screen, but neither the mouse nor
  keyboard worked.  I've not yet been able to test ssh on this problem.

  It's possibly all connected to recent firmware upgrades, so I'm happy
  to try downgrading the firmware, but I've not found any instructions
  on doing so, or even identifying the firmware upgrade log.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.14.0-1027.30-oem 5.14.21
  Uname: Linux 5.14.0-1027-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 17 03:44:49 2022
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-sutton-focal-amd64-20210412-218+sutton-newell-focal-amd64+X00
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Occurs more often under certain circumstances
  GpuHangStarted: Within the last week or two
  GraphicsCard:
   Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:22d5]
  InstallationDate: Installed on 2021-04-15 (335 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20210412-22:07
  MachineType: LENOVO 20XWCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1027-oem 
root=UUID=6a411137-06bb-4de1-be93-c2fcd4f44a5a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/02/2021
  dmi.bios.release: 1.51
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N32ET75W (1.51 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20XWCTO1WW
  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.32
  dmi.modalias: 
dmi:bvnLENOVO:bvrN32ET75W(1.51):bd12/02/2021:br1.51:efr1.32:svnLENOVO:pn20XWCTO1WW:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XWCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9:
  dmi.product.family: ThinkPad X1 Carbon Gen 9
  dmi.product.name: 20XWCTO1WW
  dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9
  dmi.product.version: ThinkPad X1 Carbon Gen 9
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati