date:20220412

This bug was fixed in the package gnome-control-center -
1:41.4-1ubuntu11

---
gnome-control-center (1:41.4-1ubuntu11) jammy; urgency=medium

  * debian/patches/ubuntu/sharing-rdp/*.path:
- Backport RDP support (LP: #1968518)
  * debian/patches/ubuntu/update-vnc-key.patch:
- Dropped as fixed in the above backport.

 -- Robert Ancell   Wed, 13 Apr 2022
11:38:18 +1200

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

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

Title:
  FFe: Backport new RDP settings

Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in gnome-user-docs package in Ubuntu:
  Fix Released

Bug description:
  We are shipping some GNOME 41 and some GNOME 42 components in jammy.
  In GNOME 42 the remote desktop support moved from VNC to RDP. We have
  the updated gnome-remote-desktop in jammy, but not the settings
  changes in gnome-control-center 41. The proposal is to backport these
  settings.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1968518/+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 1960237] Re: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libnvidia-ml.so', which is also in package libnvidia-c

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

** Changed in: nvidia-graphics-drivers-340 (Ubuntu)
   Status: New => Confirmed

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

Title:
  package nvidia-340 (not installed) failed to install/upgrade: trying
  to overwrite '/usr/lib/x86_64-linux-gnu/libnvidia-ml.so', which is
  also in package libnvidia-compute-470:amd64
  470.103.01-0ubuntu0.20.04.1

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Confirmed

Bug description:
  Unable to install Nvidia Driver

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: nvidia-340 (not installed)
  ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-28-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Mon Feb  7 19:31:01 2022
  ErrorMessage: trying to overwrite 
'/usr/lib/x86_64-linux-gnu/libnvidia-ml.so', which is also in package 
libnvidia-compute-470:amd64 470.103.01-0ubuntu0.20.04.1
  InstallationDate: Installed on 2022-02-07 (0 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  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: nvidia-graphics-drivers-340
  Title: package nvidia-340 (not installed) failed to install/upgrade: trying 
to overwrite '/usr/lib/x86_64-linux-gnu/libnvidia-ml.so', which is also in 
package libnvidia-compute-470:amd64 470.103.01-0ubuntu0.20.04.1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1960237/+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 1968518] Re: FFe: Backport new RDP settings

This bug was fixed in the package gnome-user-docs - 41.5-1ubuntu2

---
gnome-user-docs (41.5-1ubuntu2) jammy; urgency=medium

  * debian/patches/update_sharing-desktop.page.patch:
- Update to the GNOME 42 version to reflect significant changes to
  the gnome-remote-desktop and gnome-control-center packages
  (LP: #1968518).

 -- Gunnar Hjalmarsson   Tue, 12 Apr 2022 21:48:35
+0200

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

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

Title:
  FFe: Backport new RDP settings

Status in gnome-control-center package in Ubuntu:
  Fix Committed
Status in gnome-user-docs package in Ubuntu:
  Fix Released

Bug description:
  We are shipping some GNOME 41 and some GNOME 42 components in jammy.
  In GNOME 42 the remote desktop support moved from VNC to RDP. We have
  the updated gnome-remote-desktop in jammy, but not the settings
  changes in gnome-control-center 41. The proposal is to backport these
  settings.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1968518/+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 1968518] Re: FFe: Backport new RDP settings

2022-04-12 Thread Robert Ancell

Uploaded as 1:41.4-1ubuntu11

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

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

Title:
  FFe: Backport new RDP settings

Status in gnome-control-center package in Ubuntu:
  Fix Committed
Status in gnome-user-docs package in Ubuntu:
  Fix Committed

Bug description:
  We are shipping some GNOME 41 and some GNOME 42 components in jammy.
  In GNOME 42 the remote desktop support moved from VNC to RDP. We have
  the updated gnome-remote-desktop in jammy, but not the settings
  changes in gnome-control-center 41. The proposal is to backport these
  settings.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1968518/+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 1968663] Re: [impish] Screen freeze when unsuspending and entering password

** Summary changed:

- Screen freeze when unsuspending and entering password
+ [impish] Screen freeze when unsuspending and entering password

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

Title:
  [impish] Screen freeze when unsuspending and entering password

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Sometimes after unsuspending and entering the login screen password,
  the right spinning icon stops and the whole system hangs.  I am able
  to SSH into the machine and look at the logs, but everything seems
  pretty normal and I can't find relevant errors.  Do note that my
  internal webcam connection is kinda wonky but I don't know if that's
  related.  Pressing Alt+F# to switch to a TTY doesn't work.  I have to
  force power down every time by holding the power button.  This happens
  once in a while.  I'm using Wayland and Gnome.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: xorg 1:7.7+22ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-39.44-generic 5.13.19
  Uname: Linux 5.13.0-39-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  510.54  Tue Feb  8 04:42:21 
UTC 2022
   GCC version:  gcc version 11.2.0 (Ubuntu 11.2.0-7ubuntu2)
  ApportVersion: 2.20.11-0ubuntu71.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 11 20:05:34 2022
  DistUpgraded: Fresh install
  DistroCodename: impish
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GpuHangFrequency: Once a week
  GpuHangReproducibility: Occurs more often under certain circumstances
  GpuHangStarted: Immediately after installing this version of Ubuntu
  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:0905]
 Subsystem: Hewlett-Packard Company TU117M [GeForce GTX 1650 Mobile / 
Max-Q] [103c:8601]
  InstallationDate: Installed on 2021-10-15 (178 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: Dell Inc. XPS 15 7590
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-39-generic 
root=/dev/mapper/vgroot-lvroot--ubuntu--21.10 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/09/2021
  dmi.bios.release: 1.15
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.15.0
  dmi.board.name: 018W12
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.0:bd12/09/2021:br1.15:svnDellInc.:pnXPS157590:pvr:rvnDellInc.:rn018W12:rvrA02:cvnDellInc.:ct10:cvr:sku0905:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 7590
  dmi.product.sku: 0905
  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.107-8ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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/ubuntu/+source/gnome-shell/+bug/1968663/+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 1968099] Re: gnome shell crashes after disconnecting external monitors

If you have any unexplained crash that doesn't leave a crash file then
please:

1. When the crash occurs, wait 10 seconds and then reboot.

2. Run:

   journalctl -b-1 > prevboot.txt

3. Attach the resulting text file here.

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

Title:
  gnome shell crashes after disconnecting external monitors

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 22.04 Beta on Thinkpad Carbon Gen 6.

  After disconnecting external monitors Gnome crashes:
  - logged out to login screen
  - after login there is new session

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  7 00:51:54 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-01-12 (84 days ago)
  InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  RelatedPackageVersions: mutter-common 42.0-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to jammy on 2022-04-05 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1968099/+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 1961747] Re: [nvidia] Black screen (with grey squares) after resume from sleep

Nvidia mentioned that driver 510.60 fixes a bug that sounds like this
one...

https://www.nvidia.com/download/driverResults.aspx/187162/en-us

But don't download it from there. Please use the 'Additional Drivers'
app instead.

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

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

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

Title:
  [nvidia] Black screen (with grey squares) after resume from sleep

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

Bug description:
  Problem: Screen is black when resuming from sleep. Only a few grey
  squares are shown.

  Software: Latest Ubuntu 22.04 (updated 21st of february). Nvidia 495
  drivers.

  Hardware: Ryzen 5900x, Nvidia 3080ti GPU.

  Configuration: Wayland at login screen.

  Analysis: Maybe Video RAM is purged during sleep and then it is not
  restored when resuming.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1961747/+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 1961747] Re: [nvidia] Black screen (with grey squares) after resume from sleep

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

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

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

Title:
  [nvidia] Black screen (with grey squares) after resume from sleep

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

Bug description:
  Problem: Screen is black when resuming from sleep. Only a few grey
  squares are shown.

  Software: Latest Ubuntu 22.04 (updated 21st of february). Nvidia 495
  drivers.

  Hardware: Ryzen 5900x, Nvidia 3080ti GPU.

  Configuration: Wayland at login screen.

  Analysis: Maybe Video RAM is purged during sleep and then it is not
  restored when resuming.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1961747/+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 1967452] Re: [nvidia] When resume from suspend, monitor keep blinking and don't show the whole desktop.

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

** This bug has been marked a duplicate of bug 1961747
   [nvidia] Black screen (with grey squares) after resume from sleep

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

Title:
  [nvidia] When resume from suspend, monitor keep blinking and don't
  show the whole desktop.

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

Bug description:
  [Reproduce steps]

  1. Install jammy beta.
  2. Install nvidia-driver by ubuntu-driver install
  3. Suspend the system by clicking the button at the upper right corner.

  [Expected result]

  Should re-enter to desktop.

  [Actual result]

  Screen keep blinking and don't show the desktop screen.
  According to reaction of the system, it seems to login already, I can press 
ctrl+alt+del to pop out a logout menu.

  
  [Info]

  OS version: Ubuntu Jammy Jellyfish (development branch)
  Device: HP Z2 Mini G5 workstation
  CID: 202008-28179

  Wayland in use.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xwayland 2:22.1.0-1
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 31 23:27:12 2022
  InstallationDate: Installed on 2022-04-01 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 
(20220329.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.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/gnome-shell/+bug/1967452/+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 1961747] Re: Black screen after resume from sleep

Sounds like an extreme case of bug 1876632.

** Tags added: jammy nvidia suspend-resume

** Summary changed:

- Black screen after resume from sleep
+ [nvidia] Black screen after resume from sleep

** Summary changed:

- [nvidia] Black screen after resume from sleep
+ [nvidia] Black screen (with grey squares) after resume from sleep

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

Title:
  [nvidia] Black screen (with grey squares) after resume from sleep

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

Bug description:
  Problem: Screen is black when resuming from sleep. Only a few grey
  squares are shown.

  Software: Latest Ubuntu 22.04 (updated 21st of february). Nvidia 495
  drivers.

  Hardware: Ryzen 5900x, Nvidia 3080ti GPU.

  Configuration: Wayland at login screen.

  Analysis: Maybe Video RAM is purged during sleep and then it is not
  restored when resuming.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1961747/+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 1968792] Re: After F10 menu Enter key opens file instead of menu action

2022-04-12 Thread Erich Eickmeyer 

Filed upstream on your behalf.
https://gitlab.gnome.org/GNOME/nautilus/-/issues/2225

** Also affects: nautilus (Ubuntu Jammy)
   Importance: Undecided
   Status: Confirmed

** Bug watch added: gitlab.gnome.org/GNOME/nautilus/-/issues #2225
   https://gitlab.gnome.org/GNOME/nautilus/-/issues/2225

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

Title:
  After F10 menu Enter key opens file instead of menu action

Status in nautilus package in Ubuntu:
  Confirmed
Status in nautilus source package in Jammy:
  Confirmed

Bug description:
  When pressing F10 on Nautilus, the menu pops. Then the arrow keys navigate 
the menu, but when pressing Enter, does not execute the selected menu action.
  IE: if folder is selected, press F10, menu pops down arrow to choose "open in 
terminal", press enter, Nautilus navigates to the selected folder instead of 
opening terminal in the current location.
  Also with files: if text (or any) file is selected, press F10, menu pops, 
choose any action with arrows, press enter, gedit (or whatever) opens selected 
file.

  Tested all actions then selecting files or folders, same result.

  Expected behavior: After pressing F10, focus should be on the menu that just 
pops up, until ESC is pressed or mouse clicks somewhere else or focus is 
shifted by other means, so when pressing ENTER action gets performed.
  IE: file or folder is selected, press F10, down arrow to select PROPERTIES, 
press ENTER, PROPERTIES of selected item are shown.

  Also tried with SPACEBAR (just in case), but the result is the same.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: nautilus 1:42.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckMismatches: ./preseed/ubuntu.seed 
./pool/restricted/n/nvidia-graphics-drivers-470/nvidia-kernel-source-470_470.103.01-0ubuntu2_amd64.deb
 
./pool/restricted/n/nvidia-graphics-drivers-510/libnvidia-gl-510_510.60.02-0ubuntu1_amd64.deb
 
./pool/restricted/n/nvidia-graphics-drivers-510/nvidia-compute-utils-510_510.60.02-0ubuntu1_amd64.deb
 
./pool/restricted/n/nvidia-graphics-drivers-510/nvidia-driver-495_510.60.02-0ubuntu1_amd64.deb
 
./pool/restricted/n/nvidia-graphics-drivers-510/nvidia-driver-510_510.60.02-0ubuntu1_amd64.deb
 
./pool/restricted/n/nvidia-graphics-drivers-510/nvidia-kernel-common-510_510.60.02-0ubuntu1_amd64.deb
 
./pool/restricted/n/nvidia-graphics-drivers-510/nvidia-kernel-source-510_510.60.02-0ubuntu1_amd64.deb
 
./pool/restricted/n/nvidia-graphics-drivers-510/nvidia-utils-510_510.60.02-0ubuntu1_amd64.deb
 
./pool/restricted/n/nvidia-graphics-drivers-510/xserver-xorg-video-nvidia-510_510.60.02-0ubuntu1_amd64.deb
  CasperMD5CheckResult: fail
  CasperVersion: 1.468
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 12 23:08:24 2022
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   
  LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220409)
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:
   evince42.1-2
   file-roller   3.42.0-1
   nautilus-extension-gnome-terminal 3.44.0-1ubuntu1
   nautilus-share0.7.3-2ubuntu6

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1968792/+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 1968705] Re: one external monitor unresponsive after suspend

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

** This bug is no longer a duplicate of private bug 1968712
** This bug has been marked a duplicate of bug 1964120
   gnome-shell crashed with SIGSEGV at ?+a7c called from (Cannot access memory 
at address [in stack])

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

Title:
  one external monitor unresponsive after suspend

Status in gnome-shell package in Ubuntu:
  Invalid

Bug description:
  Ubuntu 22.04 Beta, Gnome, Wayland. Intel graphic

  Graphics:
Device-1: Intel UHD Graphics 620 driver: i915 v: kernel
Device-2: Acer Integrated Camera type: USB driver: uvcvideo
Display: wayland server: X.Org v: 1.22.1.1 with: Xwayland v: 22.1.1
  compositor: gnome-shell v: 42.0 driver: X: loaded: modesetting
  unloaded: fbdev,vesa gpu: i915 resolution: 1: 1920x1080~60Hz
  2: 2560x1440~60Hz
OpenGL: renderer: Mesa Intel UHD Graphics 620 (KBL GT2)
  v: 4.6 Mesa 22.0.1

  
  Laptop connected to two external monitors:

  laptop -> USB C / DisplayPort -> First monitor -> DisplayPort chain ->
  Second monitor

  After putting laptop to sleep (while monitors are connected) and
  waking it up the second monitor is unresponsive:

  - in Settings -> Display Gnome reports it as being on and working
  - turning it off and on does not bring it back
  - after switching it on in settings it for a moment appears in the overview 
(Drag displays to match physical display setup ...) but then instantly 
disappear. 

  
  After experiencing the "error" now I see following in /var/crash

  ll /var/crash/
  .rw-r- 4.2M rskolasinski 12 Apr 10:37 
_usr_libexec_gsd-xsettings.1000.crash
  .rw-rw-r--0 rskolasinski 12 Apr 10:37 
_usr_libexec_gsd-xsettings.1000.upload
  .rw---   37 whoopsie 12 Apr 10:37 
_usr_libexec_gsd-xsettings.1000.uploaded
  .rw-r- 1.8M rskolasinski 12 Apr 10:53 _usr_libexec_ibus-x11.1000.crash
  .rw-rw-r--0 rskolasinski 12 Apr 10:53 _usr_libexec_ibus-x11.1000.upload
  .rw---   37 whoopsie 12 Apr 10:53 _usr_libexec_ibus-x11.1000.uploaded


  One auto-reported itself to
  https://bugs.launchpad.net/ubuntu/+source/gnome-settings-
  daemon/+bug/1968695 but seems unrelated to this specific issue. Second
  one system suggest it may be
  https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1968478 so I am
  not sure any are related to the issue I am trying to report.

  
  Happy to provide any required information as this would potentially be 
blocking from using this once it reach stable.

  
  Last bit of information: it also happens on live usb of 22.04 beta (tested 
yesterday) and does not happen on live usb of fedora 36 beta (wanted to check 
as it also has gnome 42). All tested under wayland.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1968705/+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 1968792] Re: After F10 menu Enter key opens file instead of menu action

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

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

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

Title:
  After F10 menu Enter key opens file instead of menu action

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  When pressing F10 on Nautilus, the menu pops. Then the arrow keys navigate 
the menu, but when pressing Enter, does not execute the selected menu action.
  IE: if folder is selected, press F10, menu pops down arrow to choose "open in 
terminal", press enter, Nautilus navigates to the selected folder instead of 
opening terminal in the current location.
  Also with files: if text (or any) file is selected, press F10, menu pops, 
choose any action with arrows, press enter, gedit (or whatever) opens selected 
file.

  Tested all actions then selecting files or folders, same result.

  Expected behavior: After pressing F10, focus should be on the menu that just 
pops up, until ESC is pressed or mouse clicks somewhere else or focus is 
shifted by other means, so when pressing ENTER action gets performed.
  IE: file or folder is selected, press F10, down arrow to select PROPERTIES, 
press ENTER, PROPERTIES of selected item are shown.

  Also tried with SPACEBAR (just in case), but the result is the same.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: nautilus 1:42.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckMismatches: ./preseed/ubuntu.seed 
./pool/restricted/n/nvidia-graphics-drivers-470/nvidia-kernel-source-470_470.103.01-0ubuntu2_amd64.deb
 
./pool/restricted/n/nvidia-graphics-drivers-510/libnvidia-gl-510_510.60.02-0ubuntu1_amd64.deb
 
./pool/restricted/n/nvidia-graphics-drivers-510/nvidia-compute-utils-510_510.60.02-0ubuntu1_amd64.deb
 
./pool/restricted/n/nvidia-graphics-drivers-510/nvidia-driver-495_510.60.02-0ubuntu1_amd64.deb
 
./pool/restricted/n/nvidia-graphics-drivers-510/nvidia-driver-510_510.60.02-0ubuntu1_amd64.deb
 
./pool/restricted/n/nvidia-graphics-drivers-510/nvidia-kernel-common-510_510.60.02-0ubuntu1_amd64.deb
 
./pool/restricted/n/nvidia-graphics-drivers-510/nvidia-kernel-source-510_510.60.02-0ubuntu1_amd64.deb
 
./pool/restricted/n/nvidia-graphics-drivers-510/nvidia-utils-510_510.60.02-0ubuntu1_amd64.deb
 
./pool/restricted/n/nvidia-graphics-drivers-510/xserver-xorg-video-nvidia-510_510.60.02-0ubuntu1_amd64.deb
  CasperMD5CheckResult: fail
  CasperVersion: 1.468
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 12 23:08:24 2022
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   
  LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220409)
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:
   evince42.1-2
   file-roller   3.42.0-1
   nautilus-extension-gnome-terminal 3.44.0-1ubuntu1
   nautilus-share0.7.3-2ubuntu6

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1968792/+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 1968809] [NEW] Verify that the gdm cherry-picks are wanted for jammy

Public bug reported:

I need to check to make sure that we do in fact want the gdm3 cherry-
picks for Jammy so filing this bug to hold things for a moment.

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


** Tags: block-proposed jammy

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

Title:
  Verify that the gdm cherry-picks are wanted for jammy

Status in gdm3 package in Ubuntu:
  New

Bug description:
  I need to check to make sure that we do in fact want the gdm3 cherry-
  picks for Jammy so filing this bug to hold things for a moment.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1968809/+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 1738838] Re: Bluetooth icon shows "Off" and the only option given below it is "Turn Off"

2022-04-12 Thread Treviño

** Changed in: gnome-shell (Ubuntu)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

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

Title:
  Bluetooth icon shows "Off" and the only option given below it is "Turn
  Off"

Status in GNOME Bluetooth:
  Fix Released
Status in GNOME Shell:
  Unknown
Status in gnome-bluetooth package in Ubuntu:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Committed

Bug description:
  See video. I have installed bluetooth, blueman, bluez but it makes no
  difference to a broken interface to control bluetooth under Gnome
  17.10, as shown in the attached video.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: bluetooth 5.46-0ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec 17 22:32:30 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-18 (30 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  InterestingModules: bnep btusb bluetooth
  MachineType: LENOVO 20BXCTO1WW
  PackageArchitecture: all
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic.efi.signed 
root=UUID=02bd5120-a925-442c-a0dd-1cce59920632 ro quiet splash 
psmouse.synaptics_intertouch=0 vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/06/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET54WW (1.19 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BXCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET54WW(1.19):bd11/06/2015:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T450s
  dmi.product.name: 20BXCTO1WW
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO
  hciconfig:

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-bluetooth/+bug/1738838/+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 1964627] Re: Info (/usr/bin/info) is crashing (SIGABRT)

2022-04-12 Thread Ricardo

After a LOT of debugging, I've found the problem.

I have installed in my system the package "language-pack-pt-base". In 
this package there is the file:

/usr/share/locale-langpack/pt_BR/LC_MESSAGES/texinfo.mo

If you do:

$> msgunfmt /usr/share/locale-langpack/pt_BR/LC_MESSAGES/texinfo.mo |
less

and find the word "tutorial", you will see this text:

msgid ""
"Welcome to Info version %s.  Type \\[get-help-window] for help, \\[get-info-"
"help-node] for tutorial."
msgstr ""
"Bem vindo à versão Info %s. Digite \\[get-help-window] p/ ajuda,\\[get-inffo-"
"help-node] p/ tutorial."

The "get-inffo-help-node" crashes GNU Info with an abort() because it is not a 
valid function name. The correct function name is "get-info-help-node".

It is correct in the source of package "texinfo". It seems this file need to 
be updated in package "language-pack-pt-base". 

Hugs.

Ric.

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

Title:
  Info (/usr/bin/info) is crashing (SIGABRT)

Status in texinfo package in Ubuntu:
  Invalid

Bug description:
  
  

  My system:

  ~$ lsb_release -rd
  Description:  Ubuntu 20.04.4 LTS
  Release:  20.04
  ~$ apt-cache policy info
  info:
Instalado: 6.7.0.dfsg.2-5
Candidato: 6.7.0.dfsg.2-5
Tabela de versão:
   *** 6.7.0.dfsg.2-5 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  

  
  The application Info (/usr/bin/info) crashes with SIGABRT on startup running 
in terminal. 

  To replicate I need just to run:

  $ info

  Abortado (imagem do núcleo gravada)
  $ 

  
  My computer is in pt_BR. Translating the message: Aborted (core image 
recorded/saved)

  

  This happens in a terminal under X or on native text terminal.

  It behaves a bit differently if you redirect output with a pipe:

  $ info | less

  

  I hope this information help.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: info 6.7.0.dfsg.2-5
  ProcVersionSignature: Ubuntu 5.4.0-104.118-generic 5.4.166
  Uname: Linux 5.4.0-104-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Mar 11 14:55:59 2022
  InstallationDate: Installed on 2018-05-21 (1389 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  SourcePackage: texinfo
  UpgradeStatus: Upgraded to focal on 2021-09-16 (175 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/texinfo/+bug/1964627/+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 1968792] [NEW] After F10 menu Enter key opens file instead of menu action

2022-04-12 Thread Sebastian Benvenuti

Public bug reported:

When pressing F10 on Nautilus, the menu pops. Then the arrow keys navigate the 
menu, but when pressing Enter, does not execute the selected menu action.
IE: if folder is selected, press F10, menu pops down arrow to choose "open in 
terminal", press enter, Nautilus navigates to the selected folder instead of 
opening terminal in the current location.
Also with files: if text (or any) file is selected, press F10, menu pops, 
choose any action with arrows, press enter, gedit (or whatever) opens selected 
file.

Tested all actions then selecting files or folders, same result.

Expected behavior: After pressing F10, focus should be on the menu that just 
pops up, until ESC is pressed or mouse clicks somewhere else or focus is 
shifted by other means, so when pressing ENTER action gets performed.
IE: file or folder is selected, press F10, down arrow to select PROPERTIES, 
press ENTER, PROPERTIES of selected item are shown.

Also tried with SPACEBAR (just in case), but the result is the same.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: nautilus 1:42.0-1ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
Uname: Linux 5.15.0-25-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu80
Architecture: amd64
CasperMD5CheckMismatches: ./preseed/ubuntu.seed 
./pool/restricted/n/nvidia-graphics-drivers-470/nvidia-kernel-source-470_470.103.01-0ubuntu2_amd64.deb
 
./pool/restricted/n/nvidia-graphics-drivers-510/libnvidia-gl-510_510.60.02-0ubuntu1_amd64.deb
 
./pool/restricted/n/nvidia-graphics-drivers-510/nvidia-compute-utils-510_510.60.02-0ubuntu1_amd64.deb
 
./pool/restricted/n/nvidia-graphics-drivers-510/nvidia-driver-495_510.60.02-0ubuntu1_amd64.deb
 
./pool/restricted/n/nvidia-graphics-drivers-510/nvidia-driver-510_510.60.02-0ubuntu1_amd64.deb
 
./pool/restricted/n/nvidia-graphics-drivers-510/nvidia-kernel-common-510_510.60.02-0ubuntu1_amd64.deb
 
./pool/restricted/n/nvidia-graphics-drivers-510/nvidia-kernel-source-510_510.60.02-0ubuntu1_amd64.deb
 
./pool/restricted/n/nvidia-graphics-drivers-510/nvidia-utils-510_510.60.02-0ubuntu1_amd64.deb
 
./pool/restricted/n/nvidia-graphics-drivers-510/xserver-xorg-video-nvidia-510_510.60.02-0ubuntu1_amd64.deb
CasperMD5CheckResult: fail
CasperVersion: 1.468
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 12 23:08:24 2022
ExecutablePath: /usr/bin/nautilus
GsettingsChanges:
 
LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220409)
ProcEnviron:
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
 PATH=(custom, no user)
 LANG=en_US.UTF-8
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_nautilus:
 evince42.1-2
 file-roller   3.42.0-1
 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1
 nautilus-share0.7.3-2ubuntu6

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


** Tags: amd64 apport-bug jammy

** Attachment added: "Menu shown"
   
https://bugs.launchpad.net/bugs/1968792/+attachment/5580221/+files/Screenshot%20from%202022-04-12%2023-26-59.png

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

Title:
  After F10 menu Enter key opens file instead of menu action

Status in nautilus package in Ubuntu:
  New

Bug description:
  When pressing F10 on Nautilus, the menu pops. Then the arrow keys navigate 
the menu, but when pressing Enter, does not execute the selected menu action.
  IE: if folder is selected, press F10, menu pops down arrow to choose "open in 
terminal", press enter, Nautilus navigates to the selected folder instead of 
opening terminal in the current location.
  Also with files: if text (or any) file is selected, press F10, menu pops, 
choose any action with arrows, press enter, gedit (or whatever) opens selected 
file.

  Tested all actions then selecting files or folders, same result.

  Expected behavior: After pressing F10, focus should be on the menu that just 
pops up, until ESC is pressed or mouse clicks somewhere else or focus is 
shifted by other means, so when pressing ENTER action gets performed.
  IE: file or folder is selected, press F10, down arrow to select PROPERTIES, 
press ENTER, PROPERTIES of selected item are shown.

  Also tried with SPACEBAR (just in case), but the result is the same.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: nautilus 1:42.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckMismatches: ./preseed/ubuntu.seed 
./pool/restricted/n/nvidia-graphics-drivers-470/nvidia-kernel-source-470_470.103.01-0ubuntu2_amd64.deb

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

2022-04-12 Thread Brian Murray

Hello Yao, or anyone else affected,

Accepted iio-sensor-proxy into focal-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/iio-sensor-
proxy/2.8-1ubuntu2 in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Tags added: verification-needed verification-needed-focal

-- 
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 Released
Status in iio-sensor-proxy source package in Focal:
  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 1966178] Re: Screen-privacy couldn't work

2022-04-12 Thread Treviño

Ok, got it...

It was due to the triple-buffering patch that was ignoring the pending update, 
see
  https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1441#note_1428961

** Changed in: gnome-control-center (Ubuntu)
   Status: New => Won't Fix

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

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

Title:
  Screen-privacy couldn't work

Status in OEM Priority Project:
  New
Status in gnome-control-center package in Ubuntu:
  Won't Fix
Status in mutter package in Ubuntu:
  In Progress

Bug description:
  On ThinkPad X13 it supports 'Privacy Guard', but on jammy the g-c-c
  couldn't control it.

  From the GUI, I click 'Restrict Viewing Angle' on and off, there are
  no change at screen.

  From Fn+D, it could let screen change, and the GUI could follow the
  changes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1966178/+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 1968764] Re: Google Login Window not rendering when adding Google Account

2022-04-12 Thread Carlos Peralta

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

Same problem here, can not login into Google account in Ubuntu 22.04.

Login screen just blanks, no prompt.

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

Title:
  Google Login Window not rendering when adding Google Account

Status in gnome-online-accounts package in Ubuntu:
  New

Bug description:
  When attempting to add a Google account through settings, the login
  window doesn't render correctly.

  It appears to load but only shows a stock background color.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-online-accounts 3.44.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 12 11:08:57 2022
  InstallationDate: Installed on 2020-12-18 (480 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-online-accounts
  UpgradeStatus: Upgraded to jammy on 2022-04-09 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1968764/+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 1954628] Re: [USB-Audio - ALC4080] Front panel: Headphone output not working

2022-04-12 Thread Patrick Beckmann

I have a "MAG X570S TOMAHAWK MAX WIFI (MS-7D54)", which seems to be nearly 
identical except of WiFi and a M.2 cooler. On Ubuntu 22.04 the same problem 
exists. The above mentioned "pacmd" call works with that as well and allows 
front panel headphone audio, while running a similar command,
  pacmd load-module module-alsa-sink device=hw:2,3
allows me to use the SPDIF. Thanks a lot for hint!

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

Title:
  [USB-Audio - ALC4080] Front panel: Headphone output not working

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  I have a MSI MAG X570s Torpedo MAX motherboard, which has an onboard
  'Starship/Matisse HD Audio Controller' (-> ALC4080 USB based audio
  chip) controller that has a weird mapping via USB audio (see bug:
  https://bugzilla.kernel.org/show_bug.cgi?id=206873 for a similar
  configuration).

  Sound via line-out works fine without any interventions.

  Headphone output however does not, while Ubuntu correctly detects the
  headphones as being plugged in when selected sound is still output via
  line-out, instead of via the front panel headphone jack-out.

  After some debugging I figured the headphones are connected to a seperate 
Alsa device on the same card as the line-out.
  Running 'pacmd load-module module-alsa-sink device=hw:2,1' gives me a working 
audio output that plays just via the headphone out.

  I guess a quirk needs to be written for the configuration.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19
  Uname: Linux 5.13.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  gijs   2129 F pulseaudio
   /dev/snd/pcmC2D1p:   gijs   2129 F...m pulseaudio
   /dev/snd/controlC0:  gijs   2129 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 13 09:28:19 2021
  InstallationDate: Installed on 2020-12-06 (371 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Audio successful
  Symptom_Card: USB Audio - USB Audio
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: Only some of outputs are working
  Title: [USB-Audio - USB Audio, playback] Playback problem
  UpgradeStatus: Upgraded to impish on 2021-09-28 (75 days ago)
  dmi.bios.date: 07/09/2021
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: A.00
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MAG X570S TORPEDO MAX (MS-7D54)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrA.00:bd07/09/2021:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7D54:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMAGX570STORPEDOMAX(MS-7D54):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7D54
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1954628/+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 1954628] Re: [USB-Audio - ALC4080] Front panel: Headphone output not working

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

** Changed in: alsa-driver (Ubuntu)
   Status: New => Confirmed

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

Title:
  [USB-Audio - ALC4080] Front panel: Headphone output not working

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  I have a MSI MAG X570s Torpedo MAX motherboard, which has an onboard
  'Starship/Matisse HD Audio Controller' (-> ALC4080 USB based audio
  chip) controller that has a weird mapping via USB audio (see bug:
  https://bugzilla.kernel.org/show_bug.cgi?id=206873 for a similar
  configuration).

  Sound via line-out works fine without any interventions.

  Headphone output however does not, while Ubuntu correctly detects the
  headphones as being plugged in when selected sound is still output via
  line-out, instead of via the front panel headphone jack-out.

  After some debugging I figured the headphones are connected to a seperate 
Alsa device on the same card as the line-out.
  Running 'pacmd load-module module-alsa-sink device=hw:2,1' gives me a working 
audio output that plays just via the headphone out.

  I guess a quirk needs to be written for the configuration.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19
  Uname: Linux 5.13.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  gijs   2129 F pulseaudio
   /dev/snd/pcmC2D1p:   gijs   2129 F...m pulseaudio
   /dev/snd/controlC0:  gijs   2129 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 13 09:28:19 2021
  InstallationDate: Installed on 2020-12-06 (371 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Audio successful
  Symptom_Card: USB Audio - USB Audio
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: Only some of outputs are working
  Title: [USB-Audio - USB Audio, playback] Playback problem
  UpgradeStatus: Upgraded to impish on 2021-09-28 (75 days ago)
  dmi.bios.date: 07/09/2021
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: A.00
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MAG X570S TORPEDO MAX (MS-7D54)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrA.00:bd07/09/2021:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7D54:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMAGX570STORPEDOMAX(MS-7D54):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7D54
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1954628/+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 1967719] Re: No QXL display showing

2022-04-12 Thread Jonas Gamao

I'll try it out, but I got it working with VirtIO.

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

Title:
  No QXL display showing

Status in xorg-server package in Ubuntu:
  Incomplete
Status in xserver-xorg-video-qxl package in Ubuntu:
  Incomplete

Bug description:
  My Lubuntu VM isn't showing any display output Virt-manager.  Can't
  TTY as well.

  I tried to update Mesa driver using Oibaf's PPA, but didn't work.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xserver-xorg-video-qxl 0.1.5+git20200331-2build1
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  Date: Mon Apr  4 02:12:53 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  GraphicsCard:
   Red Hat, Inc. QXL paravirtual graphic card [1b36:0100] (rev 05) (prog-if 00 
[VGA controller])
 Subsystem: Red Hat, Inc. QEMU Virtual Machine [1af4:1100]
  InstallationDate: Installed on 2022-01-23 (70 days ago)
  InstallationMedia: Lubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 
(20220119)
  Lsusb:
   Bus 002 Device 003: ID 46f4:0001 QEMU QEMU USB HARDDRIVE
   Bus 002 Device 002: ID 46f4:0001 QEMU QEMU USB HARDDRIVE
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 5000M
   |__ Port 4: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 5000M
   |__ Port 5: Dev 3, If 0, Class=Mass Storage, Driver=usb-storage, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 480M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 
480M
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic 
root=UUID=a6cde581-8b64-4557-816a-f80ffc0a683e ro quiet splash vt.handoff=7
  SourcePackage: xserver-xorg-video-qxl
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/06/2015
  dmi.bios.release: 0.0
  dmi.bios.vendor: EFI Development Kit II / OVMF
  dmi.bios.version: 0.0.0
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-6.0
  dmi.modalias: 
dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-6.0:cvnQEMU:ct1:cvrpc-q35-6.0:sku:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-6.0
  dmi.sys.vendor: QEMU
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-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-2build3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-01-23 (70 days ago)
  InstallationMedia: Lubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 
(20220119)
  Package: xserver-xorg-video-qxl
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Tags:  jammy
  Uname: Linux 5.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroRelease: Ubuntu 22.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Red Hat, Inc. QXL paravirtual graphic card [1b36:0100] (rev 05) (prog-if 00 
[VGA controller])
 Subsystem: Red Hat, Inc. QEMU Virtual Machine [1af4:1100]
  InstallationDate: Installed on 2022-02-06 (56 days ago)
  InstallationMedia: Ubuntu Unity 22.04
  Lsusb:
   Bus 002 Device 003: ID 46f4:0001 QEMU QEMU USB HARDDRIVE
   Bus 002 Device 002: ID 46f4:0001 QEMU QEMU USB HARDDRIVE
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1,

[Desktop-packages] [Bug 1968518] Re: FFe: Backport new RDP settings

2022-04-12 Thread Gunnar Hjalmarsson

** Changed in: gnome-user-docs (Ubuntu)
   Status: Triaged => Fix Committed

** Changed in: gnome-user-docs (Ubuntu)
 Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)

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

Title:
  FFe: Backport new RDP settings

Status in gnome-control-center package in Ubuntu:
  Triaged
Status in gnome-user-docs package in Ubuntu:
  Fix Committed

Bug description:
  We are shipping some GNOME 41 and some GNOME 42 components in jammy.
  In GNOME 42 the remote desktop support moved from VNC to RDP. We have
  the updated gnome-remote-desktop in jammy, but not the settings
  changes in gnome-control-center 41. The proposal is to backport these
  settings.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1968518/+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 1968764] Re: Google Login Window not rendering when adding Google Account

2022-04-12 Thread Paul White

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

** This bug has been marked a duplicate of bug 1966418
   [jammy regression] webkit apps do not display content (yelp, epiphany, 
gnome-online-accounts etc)

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

Title:
  Google Login Window not rendering when adding Google Account

Status in gnome-online-accounts package in Ubuntu:
  New

Bug description:
  When attempting to add a Google account through settings, the login
  window doesn't render correctly.

  It appears to load but only shows a stock background color.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-online-accounts 3.44.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 12 11:08:57 2022
  InstallationDate: Installed on 2020-12-18 (480 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-online-accounts
  UpgradeStatus: Upgraded to jammy on 2022-04-09 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1968764/+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 1948339] Re: Logon screen can be bypassed using various shortcuts

This bug was fixed in the package marco - 1.26.0-3ubuntu1

---
marco (1.26.0-3ubuntu1) jammy; urgency=medium

  * debian/patches:
+ Add 1000_add-no-keybindings.patch (LP: #1948339)

 -- Martin Wimpress   Tue, 12 Apr 2022 10:28:18 +0100

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

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

Title:
  Logon screen can be bypassed using various shortcuts

Status in arctica-greeter package in Ubuntu:
  Fix Released
Status in lightdm package in Ubuntu:
  Invalid
Status in marco package in Ubuntu:
  Fix Released
Status in mate-settings-daemon package in Ubuntu:
  Invalid

Bug description:
  Hi,

  my little daughter discovered a logon screen bypass in Ubuntu Mate
  21.10 after hitting the keyboard for a while.

  It turns out that several keyboard shortcuts are allowed while Ubuntu
  Mate is locked (arctica-greeter):

  - Mod4 + S (mate-search-tool)
  - Mod4 + E (Open Caja / File Explorer)
  - CTRL + Shift + Esc (mate-system-monitor)
  - PRNT (Screenshot)

  All of the mentioned shortcuts could be used to spawn a file explorer
  (Caja) or various other binaries as user "lightdm", who owns the logon
  screen.

  Although an interactive terminal like mate-terminal, xterm, lxterm
  etc. could not be opened directly, there are various options to run
  commands as the lightdm user, for example by creating a shell script
  using "caja", and execute it directly using the GUI.

  I've attached Proof-of-Concept GIFs for all shortcuts mentioned above.
  There might be additional shortcuts that could be used to achieve the
  same, however I'm not aware about every shortcut that is configured,
  but I suppose that the root cause is located somewhere in arctica-
  greeter, rather than within every single binary launched by shortcuts.

  The bug was reproduced on a fresh installation of Ubuntu Mate 21.10. I
  haven't tested other versions of Ubuntu Mate yet.

  Please find additional version details below:

  $ apt-cache policy lightdm

  lightdm:
    Installed: 1.30.0-0ubuntu4
    Candidate: 1.30.0-0ubuntu4
    Version table:
   *** 1.30.0-0ubuntu4 500
  500 http://de.archive.ubuntu.com/ubuntu impish/universe amd64 Packages
  100 /var/lib/dpkg/status

  $ apt-cache policy arctica-greeter

  arctica-greeter:
    Installed: 0.99.1.5-2nmu1
    Candidate: 0.99.1.5-2nmu1
    Version table:
   *** 0.99.1.5-2nmu1 500
  500 http://de.archive.ubuntu.com/ubuntu impish/universe amd64 Packages
  100 /var/lib/dpkg/status

  Thanks,
  Basti

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/arctica-greeter/+bug/1948339/+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 1968359] Crash report cannot be processed

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

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate a useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

no debug symbol package found for libjpeg-turbo8
no debug symbol package found for libcrypt1


Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!


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

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

Title:
  gnome-shell crashed with SIGSEGV

Status in gnome-shell package in Ubuntu:
  Invalid

Bug description:
  gnome-shell crashed after a fresh 20.04 install (after all updates) on
  startup in a VM (KVM)

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr  8 16:02:41 2022
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.0'"
   b'org.gnome.desktop.app-folders' b'folder-children' b"['Utilities', 'YaST']"
   b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'de+nodeadkeys')]"
   b'org.gnome.desktop.notifications' b'application-children' 
b"['gnome-initial-setup']"
   b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
  InstallationDate: Installed on 2022-04-08 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220404)
  ProcCmdline: /usr/bin/gnome-shell
  RelatedPackageVersions: mutter-common 42.0-1ubuntu1
  Signal: 11
  SourcePackage: gnome-shell
  Stacktrace:
   #0  0x7f6f10b36a7c in ?? ()
   No symbol table info available.
   Backtrace stopped: Cannot access memory at address 0x7ffe867583a0
  StacktraceTop: ?? ()
  Title: gnome-shell crashed with SIGSEGV
  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/gnome-shell/+bug/1968359/+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 1968359] ThreadStacktrace.txt

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


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

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

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

Title:
  gnome-shell crashed with SIGSEGV

Status in gnome-shell package in Ubuntu:
  Invalid

Bug description:
  gnome-shell crashed after a fresh 20.04 install (after all updates) on
  startup in a VM (KVM)

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr  8 16:02:41 2022
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.0'"
   b'org.gnome.desktop.app-folders' b'folder-children' b"['Utilities', 'YaST']"
   b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'de+nodeadkeys')]"
   b'org.gnome.desktop.notifications' b'application-children' 
b"['gnome-initial-setup']"
   b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
  InstallationDate: Installed on 2022-04-08 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220404)
  ProcCmdline: /usr/bin/gnome-shell
  RelatedPackageVersions: mutter-common 42.0-1ubuntu1
  Signal: 11
  SourcePackage: gnome-shell
  Stacktrace:
   #0  0x7f6f10b36a7c in ?? ()
   No symbol table info available.
   Backtrace stopped: Cannot access memory at address 0x7ffe867583a0
  StacktraceTop: ?? ()
  Title: gnome-shell crashed with SIGSEGV
  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/gnome-shell/+bug/1968359/+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 1968359] gnome-shell crashed with SIGSEGV

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

Stacktrace:
 #0  0x7f6f10b36a7c in ?? ()
 No symbol table info available.
 Backtrace stopped: Cannot access memory at address 0x7ffe867583a0
StacktraceSource: #0  0x7f6f10b36a7c in ?? ()
StacktraceTop: ?? ()

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

Title:
  gnome-shell crashed with SIGSEGV

Status in gnome-shell package in Ubuntu:
  Invalid

Bug description:
  gnome-shell crashed after a fresh 20.04 install (after all updates) on
  startup in a VM (KVM)

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr  8 16:02:41 2022
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.0'"
   b'org.gnome.desktop.app-folders' b'folder-children' b"['Utilities', 'YaST']"
   b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'de+nodeadkeys')]"
   b'org.gnome.desktop.notifications' b'application-children' 
b"['gnome-initial-setup']"
   b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
  InstallationDate: Installed on 2022-04-08 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220404)
  ProcCmdline: /usr/bin/gnome-shell
  RelatedPackageVersions: mutter-common 42.0-1ubuntu1
  Signal: 11
  SourcePackage: gnome-shell
  Stacktrace:
   #0  0x7f6f10b36a7c in ?? ()
   No symbol table info available.
   Backtrace stopped: Cannot access memory at address 0x7ffe867583a0
  StacktraceTop: ?? ()
  Title: gnome-shell crashed with SIGSEGV
  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/gnome-shell/+bug/1968359/+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 1948339] Re: Logon screen can be bypassed using various shortcuts

This bug was fixed in the package arctica-greeter - 0.99.1.5-2nmu3

---
arctica-greeter (0.99.1.5-2nmu3) jammy; urgency=medium

  * debian/patches:
+ Add 2002_shutdown-dialog-font.patch. (LP: #1916770)
  * debian/control:
+ Version Recommends: marco (>= 1.26.0-3~) (LP: #1948339)

 -- Martin Wimpress   Tue, 12 Apr 2022 13:24:46 +0100

** Changed in: arctica-greeter (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Logon screen can be bypassed using various shortcuts

Status in arctica-greeter package in Ubuntu:
  Fix Released
Status in lightdm package in Ubuntu:
  Invalid
Status in marco package in Ubuntu:
  Fix Committed
Status in mate-settings-daemon package in Ubuntu:
  Invalid

Bug description:
  Hi,

  my little daughter discovered a logon screen bypass in Ubuntu Mate
  21.10 after hitting the keyboard for a while.

  It turns out that several keyboard shortcuts are allowed while Ubuntu
  Mate is locked (arctica-greeter):

  - Mod4 + S (mate-search-tool)
  - Mod4 + E (Open Caja / File Explorer)
  - CTRL + Shift + Esc (mate-system-monitor)
  - PRNT (Screenshot)

  All of the mentioned shortcuts could be used to spawn a file explorer
  (Caja) or various other binaries as user "lightdm", who owns the logon
  screen.

  Although an interactive terminal like mate-terminal, xterm, lxterm
  etc. could not be opened directly, there are various options to run
  commands as the lightdm user, for example by creating a shell script
  using "caja", and execute it directly using the GUI.

  I've attached Proof-of-Concept GIFs for all shortcuts mentioned above.
  There might be additional shortcuts that could be used to achieve the
  same, however I'm not aware about every shortcut that is configured,
  but I suppose that the root cause is located somewhere in arctica-
  greeter, rather than within every single binary launched by shortcuts.

  The bug was reproduced on a fresh installation of Ubuntu Mate 21.10. I
  haven't tested other versions of Ubuntu Mate yet.

  Please find additional version details below:

  $ apt-cache policy lightdm

  lightdm:
    Installed: 1.30.0-0ubuntu4
    Candidate: 1.30.0-0ubuntu4
    Version table:
   *** 1.30.0-0ubuntu4 500
  500 http://de.archive.ubuntu.com/ubuntu impish/universe amd64 Packages
  100 /var/lib/dpkg/status

  $ apt-cache policy arctica-greeter

  arctica-greeter:
    Installed: 0.99.1.5-2nmu1
    Candidate: 0.99.1.5-2nmu1
    Version table:
   *** 0.99.1.5-2nmu1 500
  500 http://de.archive.ubuntu.com/ubuntu impish/universe amd64 Packages
  100 /var/lib/dpkg/status

  Thanks,
  Basti

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/arctica-greeter/+bug/1948339/+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 1968764] [NEW] Google Login Window not rendering when adding Google Account

2022-04-12 Thread Steve Kluth

Public bug reported:

When attempting to add a Google account through settings, the login
window doesn't render correctly.

It appears to load but only shows a stock background color.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-online-accounts 3.44.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
Uname: Linux 5.15.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu80
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 12 11:08:57 2022
InstallationDate: Installed on 2020-12-18 (480 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-online-accounts
UpgradeStatus: Upgraded to jammy on 2022-04-09 (2 days ago)

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


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

** Attachment added: "Google Login Screen."
   
https://bugs.launchpad.net/bugs/1968764/+attachment/5580079/+files/Screenshot%20from%202022-04-12%2011-11-32.png

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

Title:
  Google Login Window not rendering when adding Google Account

Status in gnome-online-accounts package in Ubuntu:
  New

Bug description:
  When attempting to add a Google account through settings, the login
  window doesn't render correctly.

  It appears to load but only shows a stock background color.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-online-accounts 3.44.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 12 11:08:57 2022
  InstallationDate: Installed on 2020-12-18 (480 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-online-accounts
  UpgradeStatus: Upgraded to jammy on 2022-04-09 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1968764/+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 1968720] Re: Missing font on the Flutter installer UI in WSL

This bug was fixed in the package ubuntu-meta - 1.480

---
ubuntu-meta (1.480) jammy; urgency=medium

  * Refreshed dependencies
  * Added fonts-ubuntu to wsl (LP: #1968720)

 -- Didier Roche   Tue, 12 Apr 2022 14:12:50 +0200

** Changed in: ubuntu-meta (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Missing font on the Flutter installer UI in WSL

Status in ubuntu-meta package in Ubuntu:
  Fix Released

Bug description:
  Since in WSL we don't have a real complete snap setup and the Flutter
  UI sets the window title by using GTK+ API, it's necessary to make the
  fonts-ubuntu package available in the system to avoid the bad user
  experience of not being able to display the window title.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1968720/+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 1961747] Re: Black screen after resume from sleep

2022-04-12 Thread Henrik Harmsen

Updated today to 22.04 beta with latest updates. Same problem.

** Package changed: nvidia-graphics-drivers (Ubuntu) => gnome-shell
(Ubuntu)

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

Title:
  Black screen after resume from sleep

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Problem: Screen is black when resuming from sleep. Only a few grey
  squares are shown.

  Software: Latest Ubuntu 22.04 (updated 21st of february). Nvidia 495
  drivers.

  Hardware: Ryzen 5900x, Nvidia 3080ti GPU.

  Configuration: Wayland at login screen.

  Analysis: Maybe Video RAM is purged during sleep and then it is not
  restored when resuming.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1961747/+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 1966167] Re: Show Applications button is not clickable in the corner of the screen

2022-04-12 Thread Bug Watch Updater

** Changed in: yaru
   Status: Unknown => New

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

Title:
  Show Applications button is not clickable in the corner of the screen

Status in Yaru Theme:
  New
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Confirmed
Status in yaru-theme package in Ubuntu:
  New

Bug description:
  If you go to the bottom left corner of the dock and click, the All
  Apps button doesn't get triggered or highlighted. Check attached video
  for details.

  
  Ubuntu 21.10. Live mode. 1920x1080 screen.

To manage notifications about this bug go to:
https://bugs.launchpad.net/yaru/+bug/1966167/+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 1965210] Re: Grey (gray) panel menus don't contrast with the grey login screen

2022-04-12 Thread Bug Watch Updater

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

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

Title:
  Grey (gray) panel menus don't contrast with the grey login screen

Status in Yaru Theme:
  Fix Released
Status in yaru-theme package in Ubuntu:
  Fix Released

Bug description:
  Grey (gray) panel menus don't contrast with the grey login screen.

To manage notifications about this bug go to:
https://bugs.launchpad.net/yaru/+bug/1965210/+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 1961747] [NEW] Black screen after resume from sleep

You have been subscribed to a public bug:

Problem: Screen is black when resuming from sleep. Only a few grey
squares are shown.

Software: Latest Ubuntu 22.04 (updated 21st of february). Nvidia 495
drivers.

Hardware: Ryzen 5900x, Nvidia 3080ti GPU.

Configuration: Wayland at login screen.

Analysis: Maybe Video RAM is purged during sleep and then it is not
restored when resuming.

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


** Tags: bot-comment
-- 
Black screen after resume from sleep
https://bugs.launchpad.net/bugs/1961747
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gnome-shell in Ubuntu.

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

[Desktop-packages] [Bug 1968405] Re: yaru-theme-gnome-shell fails to install ["/usr/share/themes/Yaru/gnome-shell/calendar-today-light.svg.dpkg-new": No such file or directory]

2022-04-12 Thread Matthias Klumpp

I can confirm this bug, and it is not a space issue.
The problem is that is a symbolic link that messes with dpkg unpacking:
ls -lha /usr/share/themes/Yaru/gnome-shell
lrwxrwxrwx 1 root root 28 Feb  6  2020 /usr/share/themes/Yaru/gnome-shell -> 
../../gnome-shell/theme/Yaru

This currently prevents updates to Jammy (unless you delete the symlink
first).

** Also affects: yaru-theme (Ubuntu Jammy)
   Importance: Undecided
   Status: Confirmed

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

Title:
  yaru-theme-gnome-shell fails to install
  ["/usr/share/themes/Yaru/gnome-shell/calendar-today-light.svg.dpkg-
  new": No such file or directory]

Status in yaru-theme package in Ubuntu:
  Confirmed
Status in yaru-theme source package in Jammy:
  Confirmed

Bug description:
  The upgrade from Ubuntu 21.10 to 22.04 - Ubuntu Jammy Jellyfish (development 
branch) - stopped.
  An "apt install -f" shows that a file is missing in the Yaru package:

  -
  root@besa:/home/daniele/Downloads# apt install -f
  Lettura elenco dei pacchetti... Fatto
  Generazione albero delle dipendenze... Fatto
  Lettura informazioni sullo stato... Fatto   
  Correzione delle dipendenze... Fatto
  I seguenti pacchetti aggiuntivi saranno inoltre installati:
yaru-theme-gnome-shell
  I seguenti pacchetti saranno aggiornati:
yaru-theme-gnome-shell
  1 aggiornati, 0 installati, 0 da rimuovere e 0 non aggiornati.
  4 non completamente installati o rimossi.
  È necessario scaricare 0 B/85,4 kB di archivi.
  Dopo quest'operazione, verranno occupati 14,9 MB di spazio su disco.
  Continuare? [Y/n] 
  (Lettura del database... 392424 file e directory attualmente installati.)
  Preparativi per estrarre .../yaru-theme-gnome-shell_22.04.3.1_all.deb...
  Estrazione di yaru-theme-gnome-shell (22.04.3.1) su (21.10.2)...
  dpkg: errore nell'elaborare l'archivio 
/var/cache/apt/archives/yaru-theme-gnome-shell_22.04.3.1_all.deb (--unpack):
   impossibile aprire 
"/usr/share/themes/Yaru/gnome-shell/calendar-today-light.svg.dpkg-new": No such 
file or directory
  Segnalazione apport non scritta poiché il messaggio di errore indica un 
errore nel sistema locale.

Si sono verificati degli errori nell'elaborazione:
   /var/cache/apt/archives/yaru-theme-gnome-shell_22.04.3.1_all.deb
  

  
  The error line is:
  "/usr/share/themes/Yaru/gnome-shell/calendar-today-light.svg.dpkg-new": No 
such file or directory

  I unpacked the deb file and indeed there's no calendar-today-
  light.svg.dpkg-new file, the right name is calendar-today-light.svg

  
  It looks like a bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1968405/+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 1968728] Re: LibreOffice popups don't open on Wayland in KDE

2022-04-12 Thread Rico Tzschichholz

** Changed in: libreoffice (Ubuntu)
   Status: Triaged => Fix Committed

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

Title:
  LibreOffice popups don't open on Wayland in KDE

Status in libreoffice package in Ubuntu:
  Fix Committed

Bug description:
  In Kubuntu 22.04 beta, LibreOffice Calc drop-down popups are not
  displaying. For example, font size or autofilter. There is an upstream
  fix:

  https://bugs.documentfoundation.org/show_bug.cgi?id=144585

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1968728/+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 1968728] Re: LibreOffice popups don't open on Wayland in KDE

2022-04-12 Thread Rico Tzschichholz

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

** Changed in: libreoffice (Ubuntu)
 Assignee: (unassigned) => Rico Tzschichholz (ricotz)

** Changed in: libreoffice (Ubuntu)
Milestone: None => ubuntu-22.04

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

Title:
  LibreOffice popups don't open on Wayland in KDE

Status in libreoffice package in Ubuntu:
  Triaged

Bug description:
  In Kubuntu 22.04 beta, LibreOffice Calc drop-down popups are not
  displaying. For example, font size or autofilter. There is an upstream
  fix:

  https://bugs.documentfoundation.org/show_bug.cgi?id=144585

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1968728/+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 1968588] Re: Cannot create or add VPN in connection editor

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

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

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

Title:
  Cannot create or add VPN in connection editor

Status in network-manager-applet package in Ubuntu:
  Confirmed

Bug description:
  In 22.04 I am unable to create a new VPN in network manager and nm-
  connection-editor. After filing in the entire form the save button
  remains disabled!

  watching the terminal provides this error:
  Cannot save connection due to error: Invalid setting General: 
connection.interface-name: '': interface name must not be empty

  Seems like the form validator is not looking at the right field!

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: network-manager-gnome 1.24.0-1ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 11 10:49:34 2022
  ExecutablePath: /usr/bin/nm-connection-editor
  InstallationDate: Installed on 2022-04-09 (1 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 
(20220329.1)
  IpRoute:
   default via 10.0.2.2 dev enp0s3 proto dhcp metric 100 
   10.0.2.0/24 dev enp0s3 proto kernel scope link src 10.0.2.15 metric 100 
   169.254.0.0/16 dev enp0s3 scope link metric 1000
  IwConfig:
   lono wireless extensions.
   
   enp0s3no wireless extensions.
  ProcEnviron:
   SHELL=/bin/bash
   LANG=en_US.UTF-8
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
  RfKill:
   
  SourcePackage: network-manager-applet
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE  
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE  FILENAME
   
   Wired connection 1  31e61843-ef5f-31e8-96a2-cf86d47e015c  ethernet  
1649688323  Mon 11 Apr 2022 10:45:23 AM EDT  yes  -999  
no/org/freedesktop/NetworkManager/Settings/1  yes enp0s3  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/1  -- 
/run/NetworkManager/system-connections/Wired connection 1.nmconnection
  nmcli-dev:
   DEVICE  TYPE  STATE  IP4-CONNECTIVITY  IP6-CONNECTIVITY  DBUS-PATH   
   CONNECTION  CON-UUID 
 CON-PATH   
   enp0s3  ethernet  connected  full  limited   
/org/freedesktop/NetworkManager/Devices/2  Wired connection 1  
31e61843-ef5f-31e8-96a2-cf86d47e015c  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   lo  loopback  unmanaged  unknown   unknown   
/org/freedesktop/NetworkManager/Devices/1  --  --   
 --
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.36.4   connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1968588/+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 1967853] Crash report cannot be processed

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

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate a useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

no debug symbol package found for libcrypt1
no debug symbol package found for libjpeg-turbo8


Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!


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

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

Title:
  gnome-shell crashed with SIGSEGV

Status in gnome-shell package in Ubuntu:
  Invalid

Bug description:
  Tested jammy-desktop-amd64.iso from 2022-04-05 on Ubuntu 21.10 with
  virt-manager. I created a virtual machine and selected "Ubuntu 21.04"
  as OS (which then uses pc-q35-6.0) and changed the video to virtio
  with 3D acceleration.

  I tried all video models. Here is the result:

  * Bochs: works and gnome-shell is stable
  * QXL: Failed after "Try Ubuntu". Screen goes black.
  * Ramfb: No screen change/update after GRUB.
  * VGA: gnome-shell crashes
  * Virtio with 3D acceleration: gnome-shell crashes
  * Virtio without 3D acceleration: gnome-shell crashes

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.468
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  5 10:42:56 2022
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220405)
  ProcCmdline: gnome-shell --sm-disable --mode=ubiquity
  ProcEnviron:
   PATH=(custom, no user)
   LANG=C.UTF-8
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 42.0-1ubuntu1
  SegvAnalysis:
   Segfault happened at: 0x7ff155766f44:mov(%rsi),%rax
   PC (0x7ff155766f44) ok
   source "(%rsi)" (0x1bd441c0) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-shell
  Stacktrace:
   #0  0x7ff155766f44 in ?? ()
   No symbol table info available.
   Backtrace stopped: Cannot access memory at address 0x7fffd34c3ae0
  StacktraceTop: ?? ()
  Title: gnome-shell crashed with SIGSEGV
  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/gnome-shell/+bug/1967853/+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 1967853] ThreadStacktrace.txt

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


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

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

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

Title:
  gnome-shell crashed with SIGSEGV

Status in gnome-shell package in Ubuntu:
  Invalid

Bug description:
  Tested jammy-desktop-amd64.iso from 2022-04-05 on Ubuntu 21.10 with
  virt-manager. I created a virtual machine and selected "Ubuntu 21.04"
  as OS (which then uses pc-q35-6.0) and changed the video to virtio
  with 3D acceleration.

  I tried all video models. Here is the result:

  * Bochs: works and gnome-shell is stable
  * QXL: Failed after "Try Ubuntu". Screen goes black.
  * Ramfb: No screen change/update after GRUB.
  * VGA: gnome-shell crashes
  * Virtio with 3D acceleration: gnome-shell crashes
  * Virtio without 3D acceleration: gnome-shell crashes

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.468
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  5 10:42:56 2022
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220405)
  ProcCmdline: gnome-shell --sm-disable --mode=ubiquity
  ProcEnviron:
   PATH=(custom, no user)
   LANG=C.UTF-8
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 42.0-1ubuntu1
  SegvAnalysis:
   Segfault happened at: 0x7ff155766f44:mov(%rsi),%rax
   PC (0x7ff155766f44) ok
   source "(%rsi)" (0x1bd441c0) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-shell
  Stacktrace:
   #0  0x7ff155766f44 in ?? ()
   No symbol table info available.
   Backtrace stopped: Cannot access memory at address 0x7fffd34c3ae0
  StacktraceTop: ?? ()
  Title: gnome-shell crashed with SIGSEGV
  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/gnome-shell/+bug/1967853/+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 1967853] gnome-shell crashed with SIGSEGV

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

Stacktrace:
 #0  0x7ff155766f44 in ?? ()
 No symbol table info available.
 Backtrace stopped: Cannot access memory at address 0x7fffd34c3ae0
StacktraceSource: #0  0x7ff155766f44 in ?? ()
StacktraceTop: ?? ()

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

Title:
  gnome-shell crashed with SIGSEGV

Status in gnome-shell package in Ubuntu:
  Invalid

Bug description:
  Tested jammy-desktop-amd64.iso from 2022-04-05 on Ubuntu 21.10 with
  virt-manager. I created a virtual machine and selected "Ubuntu 21.04"
  as OS (which then uses pc-q35-6.0) and changed the video to virtio
  with 3D acceleration.

  I tried all video models. Here is the result:

  * Bochs: works and gnome-shell is stable
  * QXL: Failed after "Try Ubuntu". Screen goes black.
  * Ramfb: No screen change/update after GRUB.
  * VGA: gnome-shell crashes
  * Virtio with 3D acceleration: gnome-shell crashes
  * Virtio without 3D acceleration: gnome-shell crashes

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.468
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  5 10:42:56 2022
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220405)
  ProcCmdline: gnome-shell --sm-disable --mode=ubiquity
  ProcEnviron:
   PATH=(custom, no user)
   LANG=C.UTF-8
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 42.0-1ubuntu1
  SegvAnalysis:
   Segfault happened at: 0x7ff155766f44:mov(%rsi),%rax
   PC (0x7ff155766f44) ok
   source "(%rsi)" (0x1bd441c0) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-shell
  Stacktrace:
   #0  0x7ff155766f44 in ?? ()
   No symbol table info available.
   Backtrace stopped: Cannot access memory at address 0x7fffd34c3ae0
  StacktraceTop: ?? ()
  Title: gnome-shell crashed with SIGSEGV
  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/gnome-shell/+bug/1967853/+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 1968099] Re: gnome shell crashes after disconnecting external monitors

Just happened again. Disconnecting external monitors lead to crash in
which after log in the session was lost. I do not see a related crash in
/var/crash/... nor anything at https://errors.ubuntu.com/user/ID

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

Title:
  gnome shell crashes after disconnecting external monitors

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 22.04 Beta on Thinkpad Carbon Gen 6.

  After disconnecting external monitors Gnome crashes:
  - logged out to login screen
  - after login there is new session

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  7 00:51:54 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-01-12 (84 days ago)
  InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  RelatedPackageVersions: mutter-common 42.0-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to jammy on 2022-04-05 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1968099/+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 1968390] Re: JS ERROR: TypeError: this.window_container is null

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

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

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

Title:
JS ERROR: TypeError: this.window_container is null

Status in gnome-shell package in Ubuntu:
Confirmed

Bug description:
Ubuntu 22.04 Development

A 3 finger touchpad swipe up/down gesture with 1 application open
outputs a lot of JS errors and stacks to the journal. This issue may
be the same or related to
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1968383 but
the output is somewhat different when you have more than 1 app open.

This also happens with all extensions disabled, does not happen in
Fedora 36.

To reproduce

1. login and open terminal and watch the journal
2. perform the 3 finger swipe up gesture until the app grid displays then
swipe down to go back to the desktop.
3. See journal
4. If nothing happens try opening an app, closing it and try again.

Apr 08 21:18:49 x1c gnome-shell[21675]: JS ERROR: TypeError:
this.window_container is null

hideOverlay@resource:///org/gnome/shell/ui/windowPreview.js:373:9

vfunc_leave_event/this._idleHideOverlayId<@resource:///org/gnome/shell/ui/windowPreview.js:571:26

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1968390/+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 1968364] Re: [FFe] Switch gnome-shell to use gnome-bluetooth3

MIR Team approved at today's meeting so I'm setting to Triaged.

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

** Changed in: gnome-bluetooth (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/1968364

Title:
  [FFe] Switch gnome-shell to use gnome-bluetooth3

Status in gnome-bluetooth package in Ubuntu:
  In Progress
Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  Why It's Needed
  ---
  This will fix LP: #1738838

  gnome-shell 42 stable release updates for Ubuntu 22.04 will be easier
  since we don't have to revert all the bluetooth-related commits.

  Why, More Details
  -
  GNOME Shell 42 uses API from the new gnome-bluetooth library to fix LP: 
#1738838
  The API changes were not practical to forward-port (switch to a new 
GListModel API).
  Ubuntu's gnome-shell packaging had to revert ~6 commits to keep using the 
older gnome-bluetooth library, which is more awkward to maintain.

  Because of how GNOME Shell extensions work, if an extension tries to
  modify the bluetooth part of the system status menu in the top right
  corner of the screen, the extension may not work because Ubuntu's
  GNOME Shell 42 is different than what every other distro provides. I
  assess this concern as very low since extensions are "use at your own
  risk" and there aren't many working bluetooth extensions.

  The new gnome-bluetooth3 series has an expanded build test suite and
  has received lots of fixes that won't be ported to the older gnome-
  bluetooth series.

  Why It Wasn't Done Before
  -
  We needed to get a MIR to allow gnome-bluetooth3 in to main while the old 
gnome-bluetooth is still in main. See https://launchpad.net/bugs/1964600 .

  Sorry this is a bit late. Still about a week before Final Freeze to
  revert these changes is issues are identified but we're feeling
  confident this will be a worthwhile improvement.

  Other Change
  
  If this FFE is approved, we'd like to go ahead and drop the gir package built 
by the old gnome-bluetooth since nothing is using it. It is believed that 
gnome-shell is the only user of the gnome-bluetooth gir bindings.

  https://tracker.debian.org/media/packages/g/gnome-
  bluetooth/changelog-3.34.5-8

  Build Log for gnome-shell
  -
  This is from our git master so it includes a few other pending changes

  https://launchpad.net/~ubuntu-
  desktop/+archive/ubuntu/ppa/+sourcepub/13423631/+listing-archive-extra

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth/+bug/1968364/+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 1968743] [NEW] Rhythmbox Close & Quit shortcuts not working (Ctrl+W / Ctrl+Q) in Xubuntu

2022-04-12 Thread Matias N. Goldberg

Public bug reported:

Very simple to repro.

Starting Xubuntu 20.04 (bug still present in 22.04):

1. Open rhythmbox
2. Hit Ctrl+Q (Quit) or Ctrl+W (Close window)
3. Nothing happens

This was working fine in Xubuntu 18.04

This bug can be reproduced in the Live USB version (i.e. "Try Xubuntu")

Upstream claims it should be working and it works under GNOME:

https://gitlab.gnome.org/GNOME/rhythmbox/-/issues/1961

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: rhythmbox 3.4.4-1ubuntu2
Uname: Linux 5.13.7+ x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: XFCE
Date: Tue Apr 12 11:39:22 2022
InstallationDate: Installed on 2017-12-22 (1572 days ago)
InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
SourcePackage: rhythmbox
UpgradeStatus: Upgraded to focal on 2022-04-07 (4 days ago)

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


** Tags: amd64 apport-bug focal

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

Title:
  Rhythmbox Close & Quit shortcuts not working (Ctrl+W / Ctrl+Q) in
  Xubuntu

Status in rhythmbox package in Ubuntu:
  New

Bug description:
  Very simple to repro.

  Starting Xubuntu 20.04 (bug still present in 22.04):

  1. Open rhythmbox
  2. Hit Ctrl+Q (Quit) or Ctrl+W (Close window)
  3. Nothing happens

  This was working fine in Xubuntu 18.04

  This bug can be reproduced in the Live USB version (i.e. "Try
  Xubuntu")

  Upstream claims it should be working and it works under GNOME:

  https://gitlab.gnome.org/GNOME/rhythmbox/-/issues/1961

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: rhythmbox 3.4.4-1ubuntu2
  Uname: Linux 5.13.7+ x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Tue Apr 12 11:39:22 2022
  InstallationDate: Installed on 2017-12-22 (1572 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: rhythmbox
  UpgradeStatus: Upgraded to focal on 2022-04-07 (4 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1968743/+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 1968728] Re: LibreOffice popups don't open on Wayland in KDE

2022-04-12 Thread Rico Tzschichholz

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

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

Title:
  LibreOffice popups don't open on Wayland in KDE

Status in libreoffice package in Ubuntu:
  New

Bug description:
  In Kubuntu 22.04 beta, LibreOffice Calc drop-down popups are not
  displaying. For example, font size or autofilter. There is an upstream
  fix:

  https://bugs.documentfoundation.org/show_bug.cgi?id=144585

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1968728/+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 1922276] Re: Select All (Shift+Ctrl+A) followed by Copy (Shift+Ctrl+C) copies only visible part of terminal output

2022-04-12 Thread Tommi Nieminen

I have run Ubuntu Mate 22.04 in Virtual Box for the specific reason of
testing this. I updated VTE to 0.68, but this problem still existed.
Should it be fixed in 0.68? As for the workarounds, selecting text
manually stops being an option when you repeatedly have to scroll up
several minutes while pressing the mouse button...and one slip of the
finger in the end forces you do it all over again.

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

Title:
  Select All (Shift+Ctrl+A) followed by Copy (Shift+Ctrl+C) copies only
  visible part of terminal output

Status in mate-terminal package in Ubuntu:
  Invalid
Status in vte2.91 package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Have Ubuntu MATE 21.04 installed (or use Live session)
  2. Launch MATE Terminal
  3. Enable infinite history (Edit - Profile Preferences - Scrolling, 
Scrollback - Unlimited)
  4. Execute command with long output such as `journalctl | cat`
  5. Select Edit - Select All (or press ++), then Edit - Copy 
(or press ++)
  6. Open Pluma text editor and paste just copied terminal output

  Expected results:
  * whole terminal output is copied - staring by `user@host:~$ journalctl | 
cat` and ending by `user@host:~$`

  Actual results:
  * only last 15 lines were copied (depends on terminal size)

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: mate-terminal 1.24.1-1
  ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7
  Uname: Linux 5.11.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu61
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.461
  Date: Thu Apr  1 17:35:47 2021
  LiveMediaBuild: Ubuntu-MATE 21.04 "Hirsute Hippo" - Beta amd64 (20210331.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
  SourcePackage: mate-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mate-terminal/+bug/1922276/+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 1968364] Re: [FFe] Switch gnome-shell to use gnome-bluetooth3

2022-04-12 Thread Łukasz Zemczak

Is the MIR ready to go? If the MIR team is fine with moving gnome-
bluetooth3 into main as it is right now, consider this FFe approved -
but the deadline for any of this is, let's say, end of the day before
Final Freeze.

So yeah, consider it a conditional +1 - if MIR team is +1 and the
package goes to main, this is instantly '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/1968364

Title:
  [FFe] Switch gnome-shell to use gnome-bluetooth3

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

Bug description:
  Why It's Needed
  ---
  This will fix LP: #1738838

  gnome-shell 42 stable release updates for Ubuntu 22.04 will be easier
  since we don't have to revert all the bluetooth-related commits.

  Why, More Details
  -
  GNOME Shell 42 uses API from the new gnome-bluetooth library to fix LP: 
#1738838
  The API changes were not practical to forward-port (switch to a new 
GListModel API).
  Ubuntu's gnome-shell packaging had to revert ~6 commits to keep using the 
older gnome-bluetooth library, which is more awkward to maintain.

  Because of how GNOME Shell extensions work, if an extension tries to
  modify the bluetooth part of the system status menu in the top right
  corner of the screen, the extension may not work because Ubuntu's
  GNOME Shell 42 is different than what every other distro provides. I
  assess this concern as very low since extensions are "use at your own
  risk" and there aren't many working bluetooth extensions.

  The new gnome-bluetooth3 series has an expanded build test suite and
  has received lots of fixes that won't be ported to the older gnome-
  bluetooth series.

  Why It Wasn't Done Before
  -
  We needed to get a MIR to allow gnome-bluetooth3 in to main while the old 
gnome-bluetooth is still in main. See https://launchpad.net/bugs/1964600 .

  Sorry this is a bit late. Still about a week before Final Freeze to
  revert these changes is issues are identified but we're feeling
  confident this will be a worthwhile improvement.

  Other Change
  
  If this FFE is approved, we'd like to go ahead and drop the gir package built 
by the old gnome-bluetooth since nothing is using it. It is believed that 
gnome-shell is the only user of the gnome-bluetooth gir bindings.

  https://tracker.debian.org/media/packages/g/gnome-
  bluetooth/changelog-3.34.5-8

  Build Log for gnome-shell
  -
  This is from our git master so it includes a few other pending changes

  https://launchpad.net/~ubuntu-
  desktop/+archive/ubuntu/ppa/+sourcepub/13423631/+listing-archive-extra

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth/+bug/1968364/+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 1968720] Re: Missing font on the Flutter installer UI in WSL

https://git.launchpad.net/~ubuntu-core-dev/ubuntu-
seeds/+git/ubuntu/commit/?id=f49eb32c75f5fb4bed6f3316d1e558998dc264a8

** Changed in: ubuntu-meta (Ubuntu)
   Status: New => In Progress

** Tags added: jammy

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

Title:
  Missing font on the Flutter installer UI in WSL

Status in ubuntu-meta package in Ubuntu:
  In Progress

Bug description:
  Since in WSL we don't have a real complete snap setup and the Flutter
  UI sets the window title by using GTK+ API, it's necessary to make the
  fonts-ubuntu package available in the system to avoid the bad user
  experience of not being able to display the window title.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1968720/+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 1968518] Re: FFe: Backport new RDP settings

2022-04-12 Thread Łukasz Zemczak

Okay, thank you. In that case, please proceed o/

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

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

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

Title:
  FFe: Backport new RDP settings

Status in gnome-control-center package in Ubuntu:
  Triaged
Status in gnome-user-docs package in Ubuntu:
  Triaged

Bug description:
  We are shipping some GNOME 41 and some GNOME 42 components in jammy.
  In GNOME 42 the remote desktop support moved from VNC to RDP. We have
  the updated gnome-remote-desktop in jammy, but not the settings
  changes in gnome-control-center 41. The proposal is to backport these
  settings.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1968518/+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 1968722] Re: File fails to print when rendered with CUPS, prints fine when fed directly to printer

2022-04-12 Thread Jonathan Kamens

>Do you have cups-filter 1.28.15 installed

Yes, and I rebooted after installing it just to make sure. Problem
persists.

>Or did you try the option "pdftops-renderer=gs" as described there and
which you confirmed as fixing that bug?

I _also_ have this setting in my printers.conf. So clearly this bug is
different from that one.

> Generally, driverless printing is more reliable than PostScript
printing. PostScript interpreters in printers often have bugs.

These two statements seem to be contradictory. If driverless printing is
more reliable, that would seem to imply that files sent directly to the
printer print more reliably than files sent through the CUPS filters,
which would seem to imply that it is the filters, not the printer, that
have bugs.

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

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

Title:
  File fails to print when rendered with CUPS, prints fine when fed
  directly to printer

Status in cups package in Ubuntu:
  New

Bug description:
  I have a printer named "duplex" configured to print through CUPS
  PostScript rendering ("MakeModel HP LaserJet 500 color M551 Postscript
  (recommended)", "DeviceURI
  socket://m551dn.kamens.brookline.ma.us:9100" in printers.conf) and the
  same physical printer configured driverless in CUPS with a different
  name ("MakeModel HP LaserJet 500 color M551, driverless, cups-filters
  1.28.15", "DeviceURI
  implicitclass://HP_LaserJet_500_color_M551_1637DA/", "Option cups-
  browsed-dest-printer "1625
  ipps://HP%20LaserJet%20500%20color%20M551%20%5B1637DA%5D._ipps._tcp.local/
  pdf 600dpi"") in printers.conf.

  The attached file prints just fine when sent to the latter printer,
  i.e., prints fine with driverless printing, but fails to print when
  sent through the CUPS Postscript renderer, i.e., the former printer.
  In particular, the file stops printing after four pages and then the
  printer spits out this error page:

  ERROR:
  typecheck
  OFFENDING-COMMAND:
  known

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: cups 2.4.1op1-1ubuntu4
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 12 08:21:44 2022
  InstallationDate: Installed on 2019-01-02 (1195 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Lpstat:
   device for duplex: socket://m551dn.kamens.brookline.ma.us:9100
   device for HP_LaserJet_500_color_M551_1637DA: 
implicitclass://HP_LaserJet_500_color_M551_1637DA/
   device for simplex: socket://m551dn.kamens.brookline.ma.us:9100
  MachineType: Acer Predator G6-710
  Papersize: letter
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/simplex.ppd', 
'/etc/cups/ppd/duplex.ppd', 
'/etc/cups/ppd/HP_LaserJet_500_color_M551_1637DA.ppd'] failed with exit code 2: 
grep: /etc/cups/ppd/simplex.ppd: Permission denied
   grep: /etc/cups/ppd/duplex.ppd: Permission denied
   grep: /etc/cups/ppd/HP_LaserJet_500_color_M551_1637DA.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-25-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: Upgraded to jammy on 2022-02-20 (50 days ago)
  dmi.bios.date: 05/18/2016
  dmi.bios.release: 5.11
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R01-A4
  dmi.board.name: Predator G6-710
  dmi.board.vendor: Acer
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR01-A4:bd05/18/2016:br5.11:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:sku:
  dmi.product.family: Acer Desktop
  dmi.product.name: Predator G6-710
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1968722/+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 1968364] Re: [FFe] Switch gnome-shell to use gnome-bluetooth3

** Description changed:

  Why It's Needed
  ---
  This will fix LP: #1738838
  
  gnome-shell 42 stable release updates for Ubuntu 22.04 will be easier
  since we don't have to revert all the bluetooth-related commits.
  
  Why, More Details
  -
  GNOME Shell 42 uses API from the new gnome-bluetooth library to fix LP: 
#1738838
  The API changes were not practical to forward-port (switch to a new 
GListModel API).
  Ubuntu's gnome-shell packaging had to revert ~6 commits to keep using the 
older gnome-bluetooth library, which is more awkward to maintain.
  
  Because of how GNOME Shell extensions work, if an extension tries to
  modify the bluetooth part of the system status menu in the top right
  corner of the screen, the extension may not work because Ubuntu's GNOME
  Shell 42 is different than what every other distro provides. I assess
  this concern as very low since extensions are "use at your own risk" and
  there aren't many working bluetooth extensions.
  
  The new gnome-bluetooth3 series has an expanded build test suite and has
  received lots of fixes that won't be ported to the older gnome-bluetooth
  series.
  
  Why It Wasn't Done Before
  -
  We needed to get a MIR to allow gnome-bluetooth3 in to main while the old 
gnome-bluetooth is still in main. See https://launchpad.net/bugs/1964600 .
  
  Sorry this is a bit late. Still about a week before Final Freeze to
  revert these changes is issues are identified but we're feeling
  confident this will be a worthwhile improvement.
  
  Other Change
  
  If this FFE is approved, we'd like to go ahead and drop the gir package built 
by the old gnome-bluetooth since nothing is using it. It is believed that 
gnome-shell is the only user of the gnome-bluetooth gir bindings.
+ 
+ https://tracker.debian.org/media/packages/g/gnome-
+ bluetooth/changelog-3.34.5-8
+ 
+ Build Log for gnome-shell
+ -
+ This is from our git master so it includes a few other pending changes
+ 
+ https://launchpad.net/~ubuntu-
+ desktop/+archive/ubuntu/ppa/+sourcepub/13423631/+listing-archive-extra

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

Title:
  [FFe] Switch gnome-shell to use gnome-bluetooth3

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

Bug description:
  Why It's Needed
  ---
  This will fix LP: #1738838

  gnome-shell 42 stable release updates for Ubuntu 22.04 will be easier
  since we don't have to revert all the bluetooth-related commits.

  Why, More Details
  -
  GNOME Shell 42 uses API from the new gnome-bluetooth library to fix LP: 
#1738838
  The API changes were not practical to forward-port (switch to a new 
GListModel API).
  Ubuntu's gnome-shell packaging had to revert ~6 commits to keep using the 
older gnome-bluetooth library, which is more awkward to maintain.

  Because of how GNOME Shell extensions work, if an extension tries to
  modify the bluetooth part of the system status menu in the top right
  corner of the screen, the extension may not work because Ubuntu's
  GNOME Shell 42 is different than what every other distro provides. I
  assess this concern as very low since extensions are "use at your own
  risk" and there aren't many working bluetooth extensions.

  The new gnome-bluetooth3 series has an expanded build test suite and
  has received lots of fixes that won't be ported to the older gnome-
  bluetooth series.

  Why It Wasn't Done Before
  -
  We needed to get a MIR to allow gnome-bluetooth3 in to main while the old 
gnome-bluetooth is still in main. See https://launchpad.net/bugs/1964600 .

  Sorry this is a bit late. Still about a week before Final Freeze to
  revert these changes is issues are identified but we're feeling
  confident this will be a worthwhile improvement.

  Other Change
  
  If this FFE is approved, we'd like to go ahead and drop the gir package built 
by the old gnome-bluetooth since nothing is using it. It is believed that 
gnome-shell is the only user of the gnome-bluetooth gir bindings.

  https://tracker.debian.org/media/packages/g/gnome-
  bluetooth/changelog-3.34.5-8

  Build Log for gnome-shell
  -
  This is from our git master so it includes a few other pending changes

  https://launchpad.net/~ubuntu-
  desktop/+archive/ubuntu/ppa/+sourcepub/13423631/+listing-archive-extra

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth/+bug/1968364/+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 1968722] Re: File fails to print when rendered with CUPS, prints fine when fed directly to printer

2022-04-12 Thread Till Kamppeter

Do you have cups-filter 1.28.15 installed, which fixes bug #1967816? Or
did you try the option "pdftops-renderer=gs" as described there and
which you confirmed as fixing that bug? You do not need the option if
you have cups-filter 1.28.15 installed. Or could it be that this file
now needs the "pdftops-renderer=pdftops" option to print?

Generally, driverless printing is more reliable than PostScript
printing. PostScript interpreters in printers often have bugs.

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

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

Title:
  File fails to print when rendered with CUPS, prints fine when fed
  directly to printer

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  I have a printer named "duplex" configured to print through CUPS
  PostScript rendering ("MakeModel HP LaserJet 500 color M551 Postscript
  (recommended)", "DeviceURI
  socket://m551dn.kamens.brookline.ma.us:9100" in printers.conf) and the
  same physical printer configured driverless in CUPS with a different
  name ("MakeModel HP LaserJet 500 color M551, driverless, cups-filters
  1.28.15", "DeviceURI
  implicitclass://HP_LaserJet_500_color_M551_1637DA/", "Option cups-
  browsed-dest-printer "1625
  ipps://HP%20LaserJet%20500%20color%20M551%20%5B1637DA%5D._ipps._tcp.local/
  pdf 600dpi"") in printers.conf.

  The attached file prints just fine when sent to the latter printer,
  i.e., prints fine with driverless printing, but fails to print when
  sent through the CUPS Postscript renderer, i.e., the former printer.
  In particular, the file stops printing after four pages and then the
  printer spits out this error page:

  ERROR:
  typecheck
  OFFENDING-COMMAND:
  known

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: cups 2.4.1op1-1ubuntu4
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 12 08:21:44 2022
  InstallationDate: Installed on 2019-01-02 (1195 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Lpstat:
   device for duplex: socket://m551dn.kamens.brookline.ma.us:9100
   device for HP_LaserJet_500_color_M551_1637DA: 
implicitclass://HP_LaserJet_500_color_M551_1637DA/
   device for simplex: socket://m551dn.kamens.brookline.ma.us:9100
  MachineType: Acer Predator G6-710
  Papersize: letter
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/simplex.ppd', 
'/etc/cups/ppd/duplex.ppd', 
'/etc/cups/ppd/HP_LaserJet_500_color_M551_1637DA.ppd'] failed with exit code 2: 
grep: /etc/cups/ppd/simplex.ppd: Permission denied
   grep: /etc/cups/ppd/duplex.ppd: Permission denied
   grep: /etc/cups/ppd/HP_LaserJet_500_color_M551_1637DA.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-25-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: Upgraded to jammy on 2022-02-20 (50 days ago)
  dmi.bios.date: 05/18/2016
  dmi.bios.release: 5.11
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R01-A4
  dmi.board.name: Predator G6-710
  dmi.board.vendor: Acer
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR01-A4:bd05/18/2016:br5.11:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:sku:
  dmi.product.family: Acer Desktop
  dmi.product.name: Predator G6-710
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1968722/+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 1968728] [NEW] LibreOffice popups don't open on Wayland in KDE

2022-04-12 Thread Bruce Duncan

Public bug reported:

In Kubuntu 22.04 beta, LibreOffice Calc drop-down popups are not
displaying. For example, font size or autofilter. There is an upstream
fix:

https://bugs.documentfoundation.org/show_bug.cgi?id=144585

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

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

Title:
  LibreOffice popups don't open on Wayland in KDE

Status in libreoffice package in Ubuntu:
  New

Bug description:
  In Kubuntu 22.04 beta, LibreOffice Calc drop-down popups are not
  displaying. For example, font size or autofilter. There is an upstream
  fix:

  https://bugs.documentfoundation.org/show_bug.cgi?id=144585

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1968728/+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 1968588] Re: Cannot create or add VPN in connection editor

2022-04-12 Thread Aurelia

This is a NetworkManager bug. It happens in the GNOME applet and in nm-
connection-editor.

Also reproduces in Fedora 36 Beta 1.

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

Title:
  Cannot create or add VPN in connection editor

Status in network-manager-applet package in Ubuntu:
  New

Bug description:
  In 22.04 I am unable to create a new VPN in network manager and nm-
  connection-editor. After filing in the entire form the save button
  remains disabled!

  watching the terminal provides this error:
  Cannot save connection due to error: Invalid setting General: 
connection.interface-name: '': interface name must not be empty

  Seems like the form validator is not looking at the right field!

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: network-manager-gnome 1.24.0-1ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 11 10:49:34 2022
  ExecutablePath: /usr/bin/nm-connection-editor
  InstallationDate: Installed on 2022-04-09 (1 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 
(20220329.1)
  IpRoute:
   default via 10.0.2.2 dev enp0s3 proto dhcp metric 100 
   10.0.2.0/24 dev enp0s3 proto kernel scope link src 10.0.2.15 metric 100 
   169.254.0.0/16 dev enp0s3 scope link metric 1000
  IwConfig:
   lono wireless extensions.
   
   enp0s3no wireless extensions.
  ProcEnviron:
   SHELL=/bin/bash
   LANG=en_US.UTF-8
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
  RfKill:
   
  SourcePackage: network-manager-applet
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE  
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE  FILENAME
   
   Wired connection 1  31e61843-ef5f-31e8-96a2-cf86d47e015c  ethernet  
1649688323  Mon 11 Apr 2022 10:45:23 AM EDT  yes  -999  
no/org/freedesktop/NetworkManager/Settings/1  yes enp0s3  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/1  -- 
/run/NetworkManager/system-connections/Wired connection 1.nmconnection
  nmcli-dev:
   DEVICE  TYPE  STATE  IP4-CONNECTIVITY  IP6-CONNECTIVITY  DBUS-PATH   
   CONNECTION  CON-UUID 
 CON-PATH   
   enp0s3  ethernet  connected  full  limited   
/org/freedesktop/NetworkManager/Devices/2  Wired connection 1  
31e61843-ef5f-31e8-96a2-cf86d47e015c  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   lo  loopback  unmanaged  unknown   unknown   
/org/freedesktop/NetworkManager/Devices/1  --  --   
 --
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.36.4   connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1968588/+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 1968722] Re: File fails to print when rendered with CUPS, prints fine when fed directly to printer

2022-04-12 Thread Jonathan Kamens

Here's my printers.conf, since it doesn't look like ubuntu-bug attached
it, and there's no sensitive information in it.


** Attachment added: "printers.conf"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1968722/+attachment/5579950/+files/printers.conf

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

Title:
  File fails to print when rendered with CUPS, prints fine when fed
  directly to printer

Status in cups package in Ubuntu:
  New

Bug description:
  I have a printer named "duplex" configured to print through CUPS
  PostScript rendering ("MakeModel HP LaserJet 500 color M551 Postscript
  (recommended)", "DeviceURI
  socket://m551dn.kamens.brookline.ma.us:9100" in printers.conf) and the
  same physical printer configured driverless in CUPS with a different
  name ("MakeModel HP LaserJet 500 color M551, driverless, cups-filters
  1.28.15", "DeviceURI
  implicitclass://HP_LaserJet_500_color_M551_1637DA/", "Option cups-
  browsed-dest-printer "1625
  ipps://HP%20LaserJet%20500%20color%20M551%20%5B1637DA%5D._ipps._tcp.local/
  pdf 600dpi"") in printers.conf.

  The attached file prints just fine when sent to the latter printer,
  i.e., prints fine with driverless printing, but fails to print when
  sent through the CUPS Postscript renderer, i.e., the former printer.
  In particular, the file stops printing after four pages and then the
  printer spits out this error page:

  ERROR:
  typecheck
  OFFENDING-COMMAND:
  known

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: cups 2.4.1op1-1ubuntu4
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 12 08:21:44 2022
  InstallationDate: Installed on 2019-01-02 (1195 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Lpstat:
   device for duplex: socket://m551dn.kamens.brookline.ma.us:9100
   device for HP_LaserJet_500_color_M551_1637DA: 
implicitclass://HP_LaserJet_500_color_M551_1637DA/
   device for simplex: socket://m551dn.kamens.brookline.ma.us:9100
  MachineType: Acer Predator G6-710
  Papersize: letter
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/simplex.ppd', 
'/etc/cups/ppd/duplex.ppd', 
'/etc/cups/ppd/HP_LaserJet_500_color_M551_1637DA.ppd'] failed with exit code 2: 
grep: /etc/cups/ppd/simplex.ppd: Permission denied
   grep: /etc/cups/ppd/duplex.ppd: Permission denied
   grep: /etc/cups/ppd/HP_LaserJet_500_color_M551_1637DA.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-25-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: Upgraded to jammy on 2022-02-20 (50 days ago)
  dmi.bios.date: 05/18/2016
  dmi.bios.release: 5.11
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R01-A4
  dmi.board.name: Predator G6-710
  dmi.board.vendor: Acer
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR01-A4:bd05/18/2016:br5.11:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:sku:
  dmi.product.family: Acer Desktop
  dmi.product.name: Predator G6-710
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1968722/+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 1968722] [NEW] File fails to print when rendered with CUPS, prints fine when fed directly to printer

2022-04-12 Thread Jonathan Kamens

Public bug reported:

I have a printer named "duplex" configured to print through CUPS
PostScript rendering ("MakeModel HP LaserJet 500 color M551 Postscript
(recommended)", "DeviceURI socket://m551dn.kamens.brookline.ma.us:9100"
in printers.conf) and the same physical printer configured driverless in
CUPS with a different name ("MakeModel HP LaserJet 500 color M551,
driverless, cups-filters 1.28.15", "DeviceURI
implicitclass://HP_LaserJet_500_color_M551_1637DA/", "Option cups-
browsed-dest-printer "1625
ipps://HP%20LaserJet%20500%20color%20M551%20%5B1637DA%5D._ipps._tcp.local/
pdf 600dpi"") in printers.conf.

The attached file prints just fine when sent to the latter printer,
i.e., prints fine with driverless printing, but fails to print when sent
through the CUPS Postscript renderer, i.e., the former printer. In
particular, the file stops printing after four pages and then the
printer spits out this error page:

ERROR:
typecheck
OFFENDING-COMMAND:
known

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: cups 2.4.1op1-1ubuntu4
ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
Uname: Linux 5.15.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu80
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 12 08:21:44 2022
InstallationDate: Installed on 2019-01-02 (1195 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
Lpstat:
 device for duplex: socket://m551dn.kamens.brookline.ma.us:9100
 device for HP_LaserJet_500_color_M551_1637DA: 
implicitclass://HP_LaserJet_500_color_M551_1637DA/
 device for simplex: socket://m551dn.kamens.brookline.ma.us:9100
MachineType: Acer Predator G6-710
Papersize: letter
PpdFiles:
 Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/simplex.ppd', 
'/etc/cups/ppd/duplex.ppd', 
'/etc/cups/ppd/HP_LaserJet_500_color_M551_1637DA.ppd'] failed with exit code 2: 
grep: /etc/cups/ppd/simplex.ppd: Permission denied
 grep: /etc/cups/ppd/duplex.ppd: Permission denied
 grep: /etc/cups/ppd/HP_LaserJet_500_color_M551_1637DA.ppd: Permission denied
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-25-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
SourcePackage: cups
UpgradeStatus: Upgraded to jammy on 2022-02-20 (50 days ago)
dmi.bios.date: 05/18/2016
dmi.bios.release: 5.11
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: R01-A4
dmi.board.name: Predator G6-710
dmi.board.vendor: Acer
dmi.chassis.type: 3
dmi.chassis.vendor: Acer
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR01-A4:bd05/18/2016:br5.11:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:sku:
dmi.product.family: Acer Desktop
dmi.product.name: Predator G6-710
dmi.sys.vendor: Acer

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


** Tags: amd64 apport-bug jammy

** Attachment added: "comics.pdf"
   https://bugs.launchpad.net/bugs/1968722/+attachment/5579931/+files/comics.pdf

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

Title:
  File fails to print when rendered with CUPS, prints fine when fed
  directly to printer

Status in cups package in Ubuntu:
  New

Bug description:
  I have a printer named "duplex" configured to print through CUPS
  PostScript rendering ("MakeModel HP LaserJet 500 color M551 Postscript
  (recommended)", "DeviceURI
  socket://m551dn.kamens.brookline.ma.us:9100" in printers.conf) and the
  same physical printer configured driverless in CUPS with a different
  name ("MakeModel HP LaserJet 500 color M551, driverless, cups-filters
  1.28.15", "DeviceURI
  implicitclass://HP_LaserJet_500_color_M551_1637DA/", "Option cups-
  browsed-dest-printer "1625
  ipps://HP%20LaserJet%20500%20color%20M551%20%5B1637DA%5D._ipps._tcp.local/
  pdf 600dpi"") in printers.conf.

  The attached file prints just fine when sent to the latter printer,
  i.e., prints fine with driverless printing, but fails to print when
  sent through the CUPS Postscript renderer, i.e., the former printer.
  In particular, the file stops printing after four pages and then the
  printer spits out this error page:

  ERROR:
  typecheck
  OFFENDING-COMMAND:
  known

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: cups 2.4.1op1-1ubuntu4
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 12 08:21:44 2022
  InstallationDate: Installed on 2019-01-02 (1195 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Lpstat:
   device for duplex: socket://m551dn.kamens.brookline.ma.us:9100
   device for HP_LaserJet_500_color_M551_1637DA: 
implicitclass://HP_LaserJet_500_color_M551_1637DA/
   device for simplex:

[Desktop-packages] [Bug 1968518] Re: FFe: Backport new RDP settings

Yes, it is buildable. I was running it yesterday. It was just missing
one build-dependency so I added it and have done a PPA build for you:

https://launchpad.net/~ubuntu-
desktop/+archive/ubuntu/ppa/+sourcepub/13423577/+listing-archive-extra

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

Title:
  FFe: Backport new RDP settings

Status in gnome-control-center package in Ubuntu:
  New
Status in gnome-user-docs package in Ubuntu:
  New

Bug description:
  We are shipping some GNOME 41 and some GNOME 42 components in jammy.
  In GNOME 42 the remote desktop support moved from VNC to RDP. We have
  the updated gnome-remote-desktop in jammy, but not the settings
  changes in gnome-control-center 41. The proposal is to backport these
  settings.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1968518/+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 1968720] [NEW] Missing font on the Flutter installer UI in WSL

2022-04-12 Thread Carlos Nihelton

Public bug reported:

Since in WSL we don't have a real complete snap setup and the Flutter UI
sets the window title by using GTK+ API, it's necessary to make the
fonts-ubuntu package available in the system to avoid the bad user
experience of not being able to display the window title.

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

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

Title:
  Missing font on the Flutter installer UI in WSL

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Since in WSL we don't have a real complete snap setup and the Flutter
  UI sets the window title by using GTK+ API, it's necessary to make the
  fonts-ubuntu package available in the system to avoid the bad user
  experience of not being able to display the window title.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1968720/+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 1948339] Re: Logon screen can be bypassed using various shortcuts

@bkanbach I can version marco Recommends ensuring both packages update
in lockstep. I have spoken to the Ubuntu Security team and they will
handle the CVE assignment.

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

Title:
  Logon screen can be bypassed using various shortcuts

Status in arctica-greeter package in Ubuntu:
  Fix Committed
Status in lightdm package in Ubuntu:
  Invalid
Status in marco package in Ubuntu:
  Fix Committed
Status in mate-settings-daemon package in Ubuntu:
  Invalid

Bug description:
  Hi,

  my little daughter discovered a logon screen bypass in Ubuntu Mate
  21.10 after hitting the keyboard for a while.

  It turns out that several keyboard shortcuts are allowed while Ubuntu
  Mate is locked (arctica-greeter):

  - Mod4 + S (mate-search-tool)
  - Mod4 + E (Open Caja / File Explorer)
  - CTRL + Shift + Esc (mate-system-monitor)
  - PRNT (Screenshot)

  All of the mentioned shortcuts could be used to spawn a file explorer
  (Caja) or various other binaries as user "lightdm", who owns the logon
  screen.

  Although an interactive terminal like mate-terminal, xterm, lxterm
  etc. could not be opened directly, there are various options to run
  commands as the lightdm user, for example by creating a shell script
  using "caja", and execute it directly using the GUI.

  I've attached Proof-of-Concept GIFs for all shortcuts mentioned above.
  There might be additional shortcuts that could be used to achieve the
  same, however I'm not aware about every shortcut that is configured,
  but I suppose that the root cause is located somewhere in arctica-
  greeter, rather than within every single binary launched by shortcuts.

  The bug was reproduced on a fresh installation of Ubuntu Mate 21.10. I
  haven't tested other versions of Ubuntu Mate yet.

  Please find additional version details below:

  $ apt-cache policy lightdm

  lightdm:
    Installed: 1.30.0-0ubuntu4
    Candidate: 1.30.0-0ubuntu4
    Version table:
   *** 1.30.0-0ubuntu4 500
  500 http://de.archive.ubuntu.com/ubuntu impish/universe amd64 Packages
  100 /var/lib/dpkg/status

  $ apt-cache policy arctica-greeter

  arctica-greeter:
    Installed: 0.99.1.5-2nmu1
    Candidate: 0.99.1.5-2nmu1
    Version table:
   *** 0.99.1.5-2nmu1 500
  500 http://de.archive.ubuntu.com/ubuntu impish/universe amd64 Packages
  100 /var/lib/dpkg/status

  Thanks,
  Basti

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/arctica-greeter/+bug/1948339/+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 1968099] Re: gnome shell crashes after disconnecting external monitors

So far so good, will keep an eye and report back in case I experience a
bad crash again.

I do sometimes get logged out after messing with monitors still but
after log in all applications are still there. Don't know if this is
expected, I'd say not, but as the work is not lost it does not seem
"critical".

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

Title:
  gnome shell crashes after disconnecting external monitors

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 22.04 Beta on Thinkpad Carbon Gen 6.

  After disconnecting external monitors Gnome crashes:
  - logged out to login screen
  - after login there is new session

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  7 00:51:54 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-01-12 (84 days ago)
  InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  RelatedPackageVersions: mutter-common 42.0-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to jammy on 2022-04-05 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1968099/+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 1968705] Re: one external monitor unresponsive after suspend

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

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

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

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

Title:
  one external monitor unresponsive after suspend

Status in gnome-shell package in Ubuntu:
  Invalid

Bug description:
  Ubuntu 22.04 Beta, Gnome, Wayland. Intel graphic

  Graphics:
Device-1: Intel UHD Graphics 620 driver: i915 v: kernel
Device-2: Acer Integrated Camera type: USB driver: uvcvideo
Display: wayland server: X.Org v: 1.22.1.1 with: Xwayland v: 22.1.1
  compositor: gnome-shell v: 42.0 driver: X: loaded: modesetting
  unloaded: fbdev,vesa gpu: i915 resolution: 1: 1920x1080~60Hz
  2: 2560x1440~60Hz
OpenGL: renderer: Mesa Intel UHD Graphics 620 (KBL GT2)
  v: 4.6 Mesa 22.0.1

  
  Laptop connected to two external monitors:

  laptop -> USB C / DisplayPort -> First monitor -> DisplayPort chain ->
  Second monitor

  After putting laptop to sleep (while monitors are connected) and
  waking it up the second monitor is unresponsive:

  - in Settings -> Display Gnome reports it as being on and working
  - turning it off and on does not bring it back
  - after switching it on in settings it for a moment appears in the overview 
(Drag displays to match physical display setup ...) but then instantly 
disappear. 

  
  After experiencing the "error" now I see following in /var/crash

  ll /var/crash/
  .rw-r- 4.2M rskolasinski 12 Apr 10:37 
_usr_libexec_gsd-xsettings.1000.crash
  .rw-rw-r--0 rskolasinski 12 Apr 10:37 
_usr_libexec_gsd-xsettings.1000.upload
  .rw---   37 whoopsie 12 Apr 10:37 
_usr_libexec_gsd-xsettings.1000.uploaded
  .rw-r- 1.8M rskolasinski 12 Apr 10:53 _usr_libexec_ibus-x11.1000.crash
  .rw-rw-r--0 rskolasinski 12 Apr 10:53 _usr_libexec_ibus-x11.1000.upload
  .rw---   37 whoopsie 12 Apr 10:53 _usr_libexec_ibus-x11.1000.uploaded


  One auto-reported itself to
  https://bugs.launchpad.net/ubuntu/+source/gnome-settings-
  daemon/+bug/1968695 but seems unrelated to this specific issue. Second
  one system suggest it may be
  https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1968478 so I am
  not sure any are related to the issue I am trying to report.

  
  Happy to provide any required information as this would potentially be 
blocking from using this once it reach stable.

  
  Last bit of information: it also happens on live usb of 22.04 beta (tested 
yesterday) and does not happen on live usb of fedora 36 beta (wanted to check 
as it also has gnome 42). All tested under wayland.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1968705/+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 1948339] Re: Logon screen can be bypassed using various shortcuts

** Changed in: arctica-greeter (Ubuntu)
   Status: In Progress => Fix Committed

** Changed in: marco (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  Logon screen can be bypassed using various shortcuts

Status in arctica-greeter package in Ubuntu:
  Fix Committed
Status in lightdm package in Ubuntu:
  Invalid
Status in marco package in Ubuntu:
  Fix Committed
Status in mate-settings-daemon package in Ubuntu:
  Invalid

Bug description:
  Hi,

  my little daughter discovered a logon screen bypass in Ubuntu Mate
  21.10 after hitting the keyboard for a while.

  It turns out that several keyboard shortcuts are allowed while Ubuntu
  Mate is locked (arctica-greeter):

  - Mod4 + S (mate-search-tool)
  - Mod4 + E (Open Caja / File Explorer)
  - CTRL + Shift + Esc (mate-system-monitor)
  - PRNT (Screenshot)

  All of the mentioned shortcuts could be used to spawn a file explorer
  (Caja) or various other binaries as user "lightdm", who owns the logon
  screen.

  Although an interactive terminal like mate-terminal, xterm, lxterm
  etc. could not be opened directly, there are various options to run
  commands as the lightdm user, for example by creating a shell script
  using "caja", and execute it directly using the GUI.

  I've attached Proof-of-Concept GIFs for all shortcuts mentioned above.
  There might be additional shortcuts that could be used to achieve the
  same, however I'm not aware about every shortcut that is configured,
  but I suppose that the root cause is located somewhere in arctica-
  greeter, rather than within every single binary launched by shortcuts.

  The bug was reproduced on a fresh installation of Ubuntu Mate 21.10. I
  haven't tested other versions of Ubuntu Mate yet.

  Please find additional version details below:

  $ apt-cache policy lightdm

  lightdm:
    Installed: 1.30.0-0ubuntu4
    Candidate: 1.30.0-0ubuntu4
    Version table:
   *** 1.30.0-0ubuntu4 500
  500 http://de.archive.ubuntu.com/ubuntu impish/universe amd64 Packages
  100 /var/lib/dpkg/status

  $ apt-cache policy arctica-greeter

  arctica-greeter:
    Installed: 0.99.1.5-2nmu1
    Candidate: 0.99.1.5-2nmu1
    Version table:
   *** 0.99.1.5-2nmu1 500
  500 http://de.archive.ubuntu.com/ubuntu impish/universe amd64 Packages
  100 /var/lib/dpkg/status

  Thanks,
  Basti

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/arctica-greeter/+bug/1948339/+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 1967274] Re: Screen sometimes can't update on Intel Alder Lake GPUs [Failed to post KMS update: CRTC property (GAMMA_LUT) not found]

New fix proposed in:
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2360

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

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

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

Title:
  Screen sometimes can't update on Intel Alder Lake GPUs [Failed to post
  KMS update: CRTC property (GAMMA_LUT) not found]

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

Bug description:
  Screen can't turn back on by clicking keyboard after screen off by meta + l 
key.
  Try to do VT switch can make the screen back, some error poped when I try to 
wake up screen.

  gnome-shell[1666]: Failed to post KMS update: CRTC property (GAMMA_LUT) not 
found
  gnome-shell[1666]: Failed to post KMS update: CRTC property (GAMMA_LUT) not 
found
  gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid 
argument
  gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid 
argument
  gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid 
argument
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.04
  GsettingsChanges:
   b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.beta'"
   b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
  InstallationDate: Installed on 2022-03-31 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
  Package: gnome-shell 42~beta-1ubuntu3 [origin: unknown]
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
  Tags: wayland-session jammy third-party-packages
  Uname: Linux 5.15.0-23-generic x86_64
  UnreportableReason: This does not seem to be an official Ubuntu package. 
Please retry after updating the indexes of available packages, if that does not 
work then remove related third party packages and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1967274/+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 1968705] Re: one external monitor unresponsive after suspend

It just happened after booting with monitors disconnected and then connecting 
the monitor. 
Ubuntu offered to file a bug with more information 
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1968712 collected on 
its own so I will try to close this one and we can follow there.


Edit: apologies, it seems I don't know how to close the bug here, none of 
options seems appropriate

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

Title:
  one external monitor unresponsive after suspend

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Ubuntu 22.04 Beta, Gnome, Wayland. Intel graphic

  Graphics:
Device-1: Intel UHD Graphics 620 driver: i915 v: kernel
Device-2: Acer Integrated Camera type: USB driver: uvcvideo
Display: wayland server: X.Org v: 1.22.1.1 with: Xwayland v: 22.1.1
  compositor: gnome-shell v: 42.0 driver: X: loaded: modesetting
  unloaded: fbdev,vesa gpu: i915 resolution: 1: 1920x1080~60Hz
  2: 2560x1440~60Hz
OpenGL: renderer: Mesa Intel UHD Graphics 620 (KBL GT2)
  v: 4.6 Mesa 22.0.1

  
  Laptop connected to two external monitors:

  laptop -> USB C / DisplayPort -> First monitor -> DisplayPort chain ->
  Second monitor

  After putting laptop to sleep (while monitors are connected) and
  waking it up the second monitor is unresponsive:

  - in Settings -> Display Gnome reports it as being on and working
  - turning it off and on does not bring it back
  - after switching it on in settings it for a moment appears in the overview 
(Drag displays to match physical display setup ...) but then instantly 
disappear. 

  
  After experiencing the "error" now I see following in /var/crash

  ll /var/crash/
  .rw-r- 4.2M rskolasinski 12 Apr 10:37 
_usr_libexec_gsd-xsettings.1000.crash
  .rw-rw-r--0 rskolasinski 12 Apr 10:37 
_usr_libexec_gsd-xsettings.1000.upload
  .rw---   37 whoopsie 12 Apr 10:37 
_usr_libexec_gsd-xsettings.1000.uploaded
  .rw-r- 1.8M rskolasinski 12 Apr 10:53 _usr_libexec_ibus-x11.1000.crash
  .rw-rw-r--0 rskolasinski 12 Apr 10:53 _usr_libexec_ibus-x11.1000.upload
  .rw---   37 whoopsie 12 Apr 10:53 _usr_libexec_ibus-x11.1000.uploaded


  One auto-reported itself to
  https://bugs.launchpad.net/ubuntu/+source/gnome-settings-
  daemon/+bug/1968695 but seems unrelated to this specific issue. Second
  one system suggest it may be
  https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1968478 so I am
  not sure any are related to the issue I am trying to report.

  
  Happy to provide any required information as this would potentially be 
blocking from using this once it reach stable.

  
  Last bit of information: it also happens on live usb of 22.04 beta (tested 
yesterday) and does not happen on live usb of fedora 36 beta (wanted to check 
as it also has gnome 42). All tested under wayland.

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

*** 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/1968709/+attachment/5579897/+files/CoreDump.gz

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

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

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

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

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

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1968709/+attachment/5579907/+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/1968709

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

Status in gjs package in Ubuntu:
  New

Bug description:
  Just viewing youtube video in google chrome and this happened.

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: gjs 1.72.0-1
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  AssertionMessage: free(): invalid pointer
  CasperMD5CheckResult: pass
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 12 16:15:29 2022
  ExecutablePath: /usr/bin/gjs-console
  InstallationDate: Installed on 2022-03-29 (13 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
  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=0x7fd9cf466b8c 
"%s\n") at ../sysdeps/posix/libc_fatal.c:155
   malloc_printerr (str=str@entry=0x7fd9cf464764 "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
   () at /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/1968709/+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 1967816] Re: PDF file completely silently fails to print, computer claims it printed, printer shows no trace of it

This bug was fixed in the package cups-filters - 1.28.15-0ubuntu1

---
cups-filters (1.28.15-0ubuntu1) jammy; urgency=medium

  * New upstream bug fix release.
- In pdftops identify old LaserJets more precisely for working around
  PostScript interpreter bugs, older printers need Poppler, newer models
  need Ghostscript (LP: #1967816).

 -- Till Kamppeter   Mon, 11 Apr 2022 22:19:21
+0200

** Changed in: cups-filters (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  PDF file completely silently fails to print, computer claims it
  printed, printer shows no trace of it

Status in cups-filters package in Ubuntu:
  Fix Released

Bug description:
  I have an HP LaserJet M551dn printer which usually works just fine
  with CUPS. Tonight, however, I discovered that I was completely unable
  to print one particular PDF file (unfortunately I can't provide you
  with the file because it's a scan of a tax form with PII on it). CUPS
  claimed that it printed the file and there are no errors in the log.
  On the other side, the printer doesn't show any trace of the file
  haven't been sent to it. The print job isn't in the job log, and at no
  point while CUPS claims it's printing does the printer make any noise
  or any of its lights blink as they usually do when a job is being sent
  to it.

  I don't know how to debug this further. I'm attaching the section of
  /var/log/cups/error_log from the attempt to print the file.

  This is reproducible every time with this particular file, including
  immediately after updating to all current Jammy packages and
  rebooting.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: cups 2.4.1op1-1ubuntu4
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  4 20:51:23 2022
  InstallationDate: Installed on 2019-01-02 (1188 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Lpstat:
   device for duplex: socket://m551dn.kamens.brookline.ma.us:9100
   device for HP_LaserJet_500_color_M551_1637DA: 
implicitclass://HP_LaserJet_500_color_M551_1637DA/
   device for simplex: socket://m551dn.kamens.brookline.ma.us:9100
  MachineType: Acer Predator G6-710
  Papersize: letter
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/simplex.ppd', 
'/etc/cups/ppd/duplex.ppd', 
'/etc/cups/ppd/HP_LaserJet_500_color_M551_1637DA.ppd'] failed with exit code 2: 
grep: /etc/cups/ppd/simplex.ppd: Permission denied
   grep: /etc/cups/ppd/duplex.ppd: Permission denied
   grep: /etc/cups/ppd/HP_LaserJet_500_color_M551_1637DA.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: Upgraded to jammy on 2022-02-20 (43 days ago)
  dmi.bios.date: 05/18/2016
  dmi.bios.release: 5.11
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R01-A4
  dmi.board.name: Predator G6-710
  dmi.board.vendor: Acer
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR01-A4:bd05/18/2016:br5.11:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:sku:
  dmi.product.family: Acer Desktop
  dmi.product.name: Predator G6-710
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1967816/+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 1968705] [NEW] one external monitor unresponsive after suspend

Public bug reported:

Ubuntu 22.04 Beta, Gnome, Wayland. Intel graphic

Graphics:
  Device-1: Intel UHD Graphics 620 driver: i915 v: kernel
  Device-2: Acer Integrated Camera type: USB driver: uvcvideo
  Display: wayland server: X.Org v: 1.22.1.1 with: Xwayland v: 22.1.1
compositor: gnome-shell v: 42.0 driver: X: loaded: modesetting
unloaded: fbdev,vesa gpu: i915 resolution: 1: 1920x1080~60Hz
2: 2560x1440~60Hz
  OpenGL: renderer: Mesa Intel UHD Graphics 620 (KBL GT2)
v: 4.6 Mesa 22.0.1


Laptop connected to two external monitors:

laptop -> USB C / DisplayPort -> First monitor -> DisplayPort chain ->
Second monitor

After putting laptop to sleep (while monitors are connected) and waking
it up the second monitor is unresponsive:

- in Settings -> Display Gnome reports it as being on and working
- turning it off and on does not bring it back
- after switching it on in settings it for a moment appears in the overview 
(Drag displays to match physical display setup ...) but then instantly 
disappear. 


After experiencing the "error" now I see following in /var/crash

ll /var/crash/
.rw-r- 4.2M rskolasinski 12 Apr 10:37 _usr_libexec_gsd-xsettings.1000.crash
.rw-rw-r--0 rskolasinski 12 Apr 10:37 _usr_libexec_gsd-xsettings.1000.upload
.rw---   37 whoopsie 12 Apr 10:37 
_usr_libexec_gsd-xsettings.1000.uploaded
.rw-r- 1.8M rskolasinski 12 Apr 10:53 _usr_libexec_ibus-x11.1000.crash
.rw-rw-r--0 rskolasinski 12 Apr 10:53 _usr_libexec_ibus-x11.1000.upload
.rw---   37 whoopsie 12 Apr 10:53 _usr_libexec_ibus-x11.1000.uploaded


One auto-reported itself to
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-
daemon/+bug/1968695 but seems unrelated to this specific issue. Second
one system suggest it may be
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1968478 so I am not
sure any are related to the issue I am trying to report.


Happy to provide any required information as this would potentially be blocking 
from using this once it reach stable.


Last bit of information: it also happens on live usb of 22.04 beta (tested 
yesterday) and does not happen on live usb of fedora 36 beta (wanted to check 
as it also has gnome 42). All tested under wayland.

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

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

Title:
  one external monitor unresponsive after suspend

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Ubuntu 22.04 Beta, Gnome, Wayland. Intel graphic

  Graphics:
Device-1: Intel UHD Graphics 620 driver: i915 v: kernel
Device-2: Acer Integrated Camera type: USB driver: uvcvideo
Display: wayland server: X.Org v: 1.22.1.1 with: Xwayland v: 22.1.1
  compositor: gnome-shell v: 42.0 driver: X: loaded: modesetting
  unloaded: fbdev,vesa gpu: i915 resolution: 1: 1920x1080~60Hz
  2: 2560x1440~60Hz
OpenGL: renderer: Mesa Intel UHD Graphics 620 (KBL GT2)
  v: 4.6 Mesa 22.0.1

  
  Laptop connected to two external monitors:

  laptop -> USB C / DisplayPort -> First monitor -> DisplayPort chain ->
  Second monitor

  After putting laptop to sleep (while monitors are connected) and
  waking it up the second monitor is unresponsive:

  - in Settings -> Display Gnome reports it as being on and working
  - turning it off and on does not bring it back
  - after switching it on in settings it for a moment appears in the overview 
(Drag displays to match physical display setup ...) but then instantly 
disappear. 

  
  After experiencing the "error" now I see following in /var/crash

  ll /var/crash/
  .rw-r- 4.2M rskolasinski 12 Apr 10:37 
_usr_libexec_gsd-xsettings.1000.crash
  .rw-rw-r--0 rskolasinski 12 Apr 10:37 
_usr_libexec_gsd-xsettings.1000.upload
  .rw---   37 whoopsie 12 Apr 10:37 
_usr_libexec_gsd-xsettings.1000.uploaded
  .rw-r- 1.8M rskolasinski 12 Apr 10:53 _usr_libexec_ibus-x11.1000.crash
  .rw-rw-r--0 rskolasinski 12 Apr 10:53 _usr_libexec_ibus-x11.1000.upload
  .rw---   37 whoopsie 12 Apr 10:53 _usr_libexec_ibus-x11.1000.uploaded


  One auto-reported itself to
  https://bugs.launchpad.net/ubuntu/+source/gnome-settings-
  daemon/+bug/1968695 but seems unrelated to this specific issue. Second
  one system suggest it may be
  https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1968478 so I am
  not sure any are related to the issue I am trying to report.

  
  Happy to provide any required information as this would potentially be 
blocking from using this once it reach stable.

  
  Last bit of information: it also happens on live usb of 22.04 beta (tested 
yesterday) and does not happen on live usb of fedora 36 beta (wanted to check 
as it also has gnome 42). All tested under wayland.

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1959508] Re: enable BMFF support in exiv2

2022-04-12 Thread David H

Many thanks!

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

Title:
  enable BMFF support in exiv2

Status in exiv2 package in Ubuntu:
  Fix Released
Status in exiv2 package in Debian:
  Fix Released

Bug description:
  On https://answers.launchpad.net/ubuntu/jammy/+source/exiv2 I see that
  Ubuntu 22.04 currently includes exiv2 0.27.3

  Exiv2 v0.27.5 includes support for Canon *.CR3 image files. The CR3
  file format has been the Canon camera-raw file format since mid 2018,
  and is probably one of the most common raw image file formats today.
  Applications such as darktable, amongst others, use exiv2 to extract
  image metadata, thumbnails and previews, and can only open CR3 files
  when linked with exiv2 0.27.5 or later.

  Note that exiv2 0.27.5 needs to be built with -DEXIV2_ENABLE_BMFF=On
  to enable *.CR3 support.

  Would it be possible to get Exiv2 v0.27.5 with BMFF support enabled
  included in Ubuntu 22.04?

  Note that a similar request exists for Debian in
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000788

  References
  https://github.com/exiv2/exiv2#2-19
  https://github.com/Exiv2/exiv2/issues/1229
  https://github.com/darktable-org/darktable/pull/10332
  https://github.com/Beep6581/RawTherapee/issues/6248#issuecomment-869208918
  https://answers.launchpad.net/ubuntu/+source/exiv2/+question/700398

  Thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/exiv2/+bug/1959508/+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 1968099] Re: gnome shell crashes after disconnecting external monitors

Please check to see if the problem still occurs when the standard Ubuntu
extensions are enabled.

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

Title:
  gnome shell crashes after disconnecting external monitors

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 22.04 Beta on Thinkpad Carbon Gen 6.

  After disconnecting external monitors Gnome crashes:
  - logged out to login screen
  - after login there is new session

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  7 00:51:54 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-01-12 (84 days ago)
  InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  RelatedPackageVersions: mutter-common 42.0-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to jammy on 2022-04-05 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1968099/+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 1948339] Re: Logon screen can be bypassed using various shortcuts

2022-04-12 Thread Bastian Kanbach

That sounds great, thank you very much. I guess it's an optimal way to
keep the marco look-and-feel and have it invoked securely at the same
time.

Could there be a scenario where arctica-greeter is upgraded on a system
but marco is not? (e.g. arctica-greeter invoking "marco --no-
keybindings" when a version of marco is installed that doesn't support
this switch yet). I guess this would be a very rare edge case anyway.

Is the Ubuntu CNA handling the CVE assignment for this issue
automatically, or do I have to request a CVE-id?

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

Title:
  Logon screen can be bypassed using various shortcuts

Status in arctica-greeter package in Ubuntu:
  In Progress
Status in lightdm package in Ubuntu:
  Invalid
Status in marco package in Ubuntu:
  In Progress
Status in mate-settings-daemon package in Ubuntu:
  Invalid

Bug description:
  Hi,

  my little daughter discovered a logon screen bypass in Ubuntu Mate
  21.10 after hitting the keyboard for a while.

  It turns out that several keyboard shortcuts are allowed while Ubuntu
  Mate is locked (arctica-greeter):

  - Mod4 + S (mate-search-tool)
  - Mod4 + E (Open Caja / File Explorer)
  - CTRL + Shift + Esc (mate-system-monitor)
  - PRNT (Screenshot)

  All of the mentioned shortcuts could be used to spawn a file explorer
  (Caja) or various other binaries as user "lightdm", who owns the logon
  screen.

  Although an interactive terminal like mate-terminal, xterm, lxterm
  etc. could not be opened directly, there are various options to run
  commands as the lightdm user, for example by creating a shell script
  using "caja", and execute it directly using the GUI.

  I've attached Proof-of-Concept GIFs for all shortcuts mentioned above.
  There might be additional shortcuts that could be used to achieve the
  same, however I'm not aware about every shortcut that is configured,
  but I suppose that the root cause is located somewhere in arctica-
  greeter, rather than within every single binary launched by shortcuts.

  The bug was reproduced on a fresh installation of Ubuntu Mate 21.10. I
  haven't tested other versions of Ubuntu Mate yet.

  Please find additional version details below:

  $ apt-cache policy lightdm

  lightdm:
    Installed: 1.30.0-0ubuntu4
    Candidate: 1.30.0-0ubuntu4
    Version table:
   *** 1.30.0-0ubuntu4 500
  500 http://de.archive.ubuntu.com/ubuntu impish/universe amd64 Packages
  100 /var/lib/dpkg/status

  $ apt-cache policy arctica-greeter

  arctica-greeter:
    Installed: 0.99.1.5-2nmu1
    Candidate: 0.99.1.5-2nmu1
    Version table:
   *** 0.99.1.5-2nmu1 500
  500 http://de.archive.ubuntu.com/ubuntu impish/universe amd64 Packages
  100 /var/lib/dpkg/status

  Thanks,
  Basti

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/arctica-greeter/+bug/1948339/+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 1968099] Re: gnome shell crashes after disconnecting external monitors

This one seems not to happen any more after removing the said extensions
(system-monitor-next...) but I also disabled dash and icon desktop.

I am still experiencing another issue related to monitors but it is
probably separate so will follow in another report.

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

Title:
  gnome shell crashes after disconnecting external monitors

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 22.04 Beta on Thinkpad Carbon Gen 6.

  After disconnecting external monitors Gnome crashes:
  - logged out to login screen
  - after login there is new session

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  7 00:51:54 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-01-12 (84 days ago)
  InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  RelatedPackageVersions: mutter-common 42.0-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to jammy on 2022-04-05 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1968099/+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 1968698] Re: Desktop portal's file chooser displays disabled 'Save' button after switching directory

2022-04-12 Thread Maximilian Federle

** Attachment added: "Screenshot from 2022-04-12 11-48-25.png"

https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gtk/+bug/1968698/+attachment/5579838/+files/Screenshot%20from%202022-04-12%2011-48-25.png

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

Title:
Desktop portal's file chooser displays disabled 'Save' button after
switching directory

Status in xdg-desktop-portal-gtk package in Ubuntu:
New

Bug description:
## System

Ubuntu 22.04
xdg-desktop-portal-gtk 1.14.0-1build1

## How to reproduce

1. Open confined app, snap or flatpak, e.g. Firefox
2. Open file chooser, e.g. by pressing Ctrl + S
3. In the opened file chooser: Enter a subdirectory by clicking on it in the
central file list widget
4. Observe the 'Save' button turning to a disabled state (see the attached
screenshot)

## How to work around

You can work around the issue by editing the file name in the text
input at the top of the window. E.g. by adding and then removing a
single character.

## Expected results

No such problem should occur. There's probably some state management
issue going on. Ubuntu 21.10 did not show such behavior for me.

## Misc observations

A flatpak app showed the same problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gtk/+bug/1968698/+subscriptions

[Desktop-packages] [Bug 1948339] Re: Logon screen can be bypassed using various shortcuts

** Changed in: arctica-greeter (Ubuntu)
   Status: Triaged => In Progress

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

Title:
  Logon screen can be bypassed using various shortcuts

Status in arctica-greeter package in Ubuntu:
  In Progress
Status in lightdm package in Ubuntu:
  Invalid
Status in marco package in Ubuntu:
  In Progress
Status in mate-settings-daemon package in Ubuntu:
  Invalid

Bug description:
  Hi,

  my little daughter discovered a logon screen bypass in Ubuntu Mate
  21.10 after hitting the keyboard for a while.

  It turns out that several keyboard shortcuts are allowed while Ubuntu
  Mate is locked (arctica-greeter):

  - Mod4 + S (mate-search-tool)
  - Mod4 + E (Open Caja / File Explorer)
  - CTRL + Shift + Esc (mate-system-monitor)
  - PRNT (Screenshot)

  All of the mentioned shortcuts could be used to spawn a file explorer
  (Caja) or various other binaries as user "lightdm", who owns the logon
  screen.

  Although an interactive terminal like mate-terminal, xterm, lxterm
  etc. could not be opened directly, there are various options to run
  commands as the lightdm user, for example by creating a shell script
  using "caja", and execute it directly using the GUI.

  I've attached Proof-of-Concept GIFs for all shortcuts mentioned above.
  There might be additional shortcuts that could be used to achieve the
  same, however I'm not aware about every shortcut that is configured,
  but I suppose that the root cause is located somewhere in arctica-
  greeter, rather than within every single binary launched by shortcuts.

  The bug was reproduced on a fresh installation of Ubuntu Mate 21.10. I
  haven't tested other versions of Ubuntu Mate yet.

  Please find additional version details below:

  $ apt-cache policy lightdm

  lightdm:
    Installed: 1.30.0-0ubuntu4
    Candidate: 1.30.0-0ubuntu4
    Version table:
   *** 1.30.0-0ubuntu4 500
  500 http://de.archive.ubuntu.com/ubuntu impish/universe amd64 Packages
  100 /var/lib/dpkg/status

  $ apt-cache policy arctica-greeter

  arctica-greeter:
    Installed: 0.99.1.5-2nmu1
    Candidate: 0.99.1.5-2nmu1
    Version table:
   *** 0.99.1.5-2nmu1 500
  500 http://de.archive.ubuntu.com/ubuntu impish/universe amd64 Packages
  100 /var/lib/dpkg/status

  Thanks,
  Basti

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/arctica-greeter/+bug/1948339/+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 1968698] [NEW] Desktop portal's file chooser displays disabled 'Save' button after switching directory

2022-04-12 Thread Maximilian Federle

Public bug reported:

## System

Ubuntu 22.04
xdg-desktop-portal-gtk 1.14.0-1build1

## How to reproduce

## How to work around

You can work around the issue by editing the file name in the text input
at the top of the window. E.g. by adding and then removing a single
character.

## Expected results

No such problem should occur. There's probably some state management
issue going on. Ubuntu 21.10 did not show such behavior for me.

## Misc observations

A flatpak app showed the same problem.

** Affects: xdg-desktop-portal-gtk (Ubuntu)
Importance: Undecided
Status: New

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

Title:
Desktop portal's file chooser displays disabled 'Save' button after
switching directory

Status in xdg-desktop-portal-gtk package in Ubuntu:
New

Bug description:
## System

Ubuntu 22.04
xdg-desktop-portal-gtk 1.14.0-1build1

## How to reproduce

## How to work around

You can work around the issue by editing the file name in the text
input at the top of the window. E.g. by adding and then removing a
single character.

## Expected results

No such problem should occur. There's probably some state management
issue going on. Ubuntu 21.10 did not show such behavior for me.

## Misc observations

A flatpak app showed the same problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gtk/+bug/1968698/+subscriptions

[Desktop-packages] [Bug 1959508] Re: enable BMFF support in exiv2

This bug was fixed in the package exiv2 - 0.27.5-3ubuntu1

---
exiv2 (0.27.5-3ubuntu1) jammy; urgency=medium

  * Sync with Debian (LP: #1959508). Remaining change:
- Mark symbols as optional not seen when building with lto

exiv2 (0.27.5-3) unstable; urgency=medium

  * Team upload.
  * Update symbols from buildds.

exiv2 (0.27.5-2) unstable; urgency=medium

  * Team upload.
  * Update Multi-Arch information for -dev and -doc.
  * Enable BMFF support (Closes: #1000788)
  * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository,
Repository-Browse.
  * Fix day-of-week for changelog entry 0.10-1.
  * Enable hardening.
  * Update symbols from buildds.
  * Register documentation via doc-base.
  * Update symbols for BMFF support.

 -- Jeremy Bicha   Mon, 11 Apr 2022 13:55:15 -0400

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

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

Title:
  enable BMFF support in exiv2

Status in exiv2 package in Ubuntu:
  Fix Released
Status in exiv2 package in Debian:
  Fix Released

Bug description:
  On https://answers.launchpad.net/ubuntu/jammy/+source/exiv2 I see that
  Ubuntu 22.04 currently includes exiv2 0.27.3

  Exiv2 v0.27.5 includes support for Canon *.CR3 image files. The CR3
  file format has been the Canon camera-raw file format since mid 2018,
  and is probably one of the most common raw image file formats today.
  Applications such as darktable, amongst others, use exiv2 to extract
  image metadata, thumbnails and previews, and can only open CR3 files
  when linked with exiv2 0.27.5 or later.

  Note that exiv2 0.27.5 needs to be built with -DEXIV2_ENABLE_BMFF=On
  to enable *.CR3 support.

  Would it be possible to get Exiv2 v0.27.5 with BMFF support enabled
  included in Ubuntu 22.04?

  Note that a similar request exists for Debian in
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000788

  References
  https://github.com/exiv2/exiv2#2-19
  https://github.com/Exiv2/exiv2/issues/1229
  https://github.com/darktable-org/darktable/pull/10332
  https://github.com/Beep6581/RawTherapee/issues/6248#issuecomment-869208918
  https://answers.launchpad.net/ubuntu/+source/exiv2/+question/700398

  Thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/exiv2/+bug/1959508/+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 1968402] Re: Ubuntu 20.04.3 boots to black screen, no TTY available

Thanks for the bug report. Please be careful to report only one issue
per bug report.

When you have trouble with the USB not booting, that's usually a bad
copy of the ISO on the USB or a slightly faulty thumb drive. Very
common. Always have a different thumb drive handy to try.

I suggest the best place to start is with Ubuntu 22.04
(http://cdimage.ubuntu.com/daily-live/current/). If you have trouble
with that then we would like to know ASAP.

If you want to stick with 20.04 instead then please try 20.04.4
(https://ubuntu.com/download/desktop) and choose a single issue to
discuss, presumably the first issue you face.


** No longer affects: xorg-server (Ubuntu)

** No longer affects: nvidia-graphics-drivers-450 (Ubuntu)

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

** Changed in: ubuntu
   Status: New => Incomplete

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

Title:
  Ubuntu 20.04.3 boots to black screen, no TTY available

Status in gdm:
  New
Status in gnome-session:
  New
Status in grub:
  New
Status in os-prober-efi/trunk:
  New
Status in shim:
  New
Status in subiquity:
  New
Status in tty:
  New
Status in Ubuntu:
  Incomplete

Bug description:
  A fresh attempted install failed utterly, just as 20.04.1 failed two
  years ago.  Has anyone been paying attention?

  Ubuntu 20.04.3 burned just now to a USB stick and attempted to be
  installed.

  The first fail was that the stick booted to a couple of impenetrable
  boot-time messages and hung.  Really.  I'm not making this up.  It
  didn't just open the installer, as it should.

  The second fail was having just to guess that rebooting and trying
  another GRUB menu option might work and give that a try.  Really.  I'm
  not making this up, either.  The installer was entirely incapable of
  providing any direction

  The third failure was that the installer was incapable of detecting
  the video configuration and proceeding accordingly.  This is 20.04.3,
  the third attempt at getting this right, and it still fails.

  The fourth fail was an error message insisting on a designation of
  where root should be, even after the destination partition already had
  been specified.

  The fifth failure was that no obvious means existed to satisfy the
  installer about the root specification, which of course already had
  been made by specifying the destination partition.  All one could do
  was to see whether a context menu existed for any object on the screen
  that might possibly drill down through a few layers to something
  approximating what the content of the error message suggested.

  The sixth failure was that no GRUB menu appeared during boot,
  notwithstanding that the EFI system partition had clearly been
  identified in the installer.

  The seventh failure was that the machine booted only to a black screen
  with a non-blinking _ midway toward the upper left.  No login
  screen/display manager.  No GUI at all.  Just this little _.

  The eighth failure was that Ctrl-alt-f2, ctrl-alt-f5-f12 have no
  effect.  No TTY is available.  There is no way whatsoever to interact
  with the system.

  Expected behavior:  The software would install and the computer would
  work.

  Actual behavior:  The installer bricked my workstation.

  Obviously, no debug information is available BECAUSE THE SOFTWARE
  FAILED.  This post is being made from a borrowed Windows laptop.

  Any thoughts about how to get a working system would be appreciated.
  I am not optimistic about the prospects for 22.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdm/+bug/1968402/+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 1968402] Re: Ubuntu 20.04.3 boots to black screen, no TTY available

** No longer affects: wayland (Ubuntu)

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

** No longer affects: xorg (Ubuntu)

** No longer affects: grub2 (Ubuntu)

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

Title:
  Ubuntu 20.04.3 boots to black screen, no TTY available

Status in gdm:
  New
Status in gnome-session:
  New
Status in grub:
  New
Status in os-prober-efi/trunk:
  New
Status in shim:
  New
Status in subiquity:
  New
Status in tty:
  New
Status in mutter package in Ubuntu:
  New
Status in nvidia-graphics-drivers-450 package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New

Bug description:
  A fresh attempted install failed utterly, just as 20.04.1 failed two
  years ago.  Has anyone been paying attention?

  Ubuntu 20.04.3 burned just now to a USB stick and attempted to be
  installed.

  The first fail was that the stick booted to a couple of impenetrable
  boot-time messages and hung.  Really.  I'm not making this up.  It
  didn't just open the installer, as it should.

  The second fail was having just to guess that rebooting and trying
  another GRUB menu option might work and give that a try.  Really.  I'm
  not making this up, either.  The installer was entirely incapable of
  providing any direction

  The third failure was that the installer was incapable of detecting
  the video configuration and proceeding accordingly.  This is 20.04.3,
  the third attempt at getting this right, and it still fails.

  The fourth fail was an error message insisting on a designation of
  where root should be, even after the destination partition already had
  been specified.

  The fifth failure was that no obvious means existed to satisfy the
  installer about the root specification, which of course already had
  been made by specifying the destination partition.  All one could do
  was to see whether a context menu existed for any object on the screen
  that might possibly drill down through a few layers to something
  approximating what the content of the error message suggested.

  The sixth failure was that no GRUB menu appeared during boot,
  notwithstanding that the EFI system partition had clearly been
  identified in the installer.

  The seventh failure was that the machine booted only to a black screen
  with a non-blinking _ midway toward the upper left.  No login
  screen/display manager.  No GUI at all.  Just this little _.

  The eighth failure was that Ctrl-alt-f2, ctrl-alt-f5-f12 have no
  effect.  No TTY is available.  There is no way whatsoever to interact
  with the system.

  Expected behavior:  The software would install and the computer would
  work.

  Actual behavior:  The installer bricked my workstation.

  Obviously, no debug information is available BECAUSE THE SOFTWARE
  FAILED.  This post is being made from a borrowed Windows laptop.

  Any thoughts about how to get a working system would be appreciated.
  I am not optimistic about the prospects for 22.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdm/+bug/1968402/+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 1948339] Re: Logon screen can be bypassed using various shortcuts

** Changed in: marco (Ubuntu)
   Status: Triaged => In Progress

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

Title:
  Logon screen can be bypassed using various shortcuts

Status in arctica-greeter package in Ubuntu:
  Triaged
Status in lightdm package in Ubuntu:
  Invalid
Status in marco package in Ubuntu:
  In Progress
Status in mate-settings-daemon package in Ubuntu:
  Invalid

Bug description:
  Hi,

  my little daughter discovered a logon screen bypass in Ubuntu Mate
  21.10 after hitting the keyboard for a while.

  It turns out that several keyboard shortcuts are allowed while Ubuntu
  Mate is locked (arctica-greeter):

  - Mod4 + S (mate-search-tool)
  - Mod4 + E (Open Caja / File Explorer)
  - CTRL + Shift + Esc (mate-system-monitor)
  - PRNT (Screenshot)

  All of the mentioned shortcuts could be used to spawn a file explorer
  (Caja) or various other binaries as user "lightdm", who owns the logon
  screen.

  Although an interactive terminal like mate-terminal, xterm, lxterm
  etc. could not be opened directly, there are various options to run
  commands as the lightdm user, for example by creating a shell script
  using "caja", and execute it directly using the GUI.

  I've attached Proof-of-Concept GIFs for all shortcuts mentioned above.
  There might be additional shortcuts that could be used to achieve the
  same, however I'm not aware about every shortcut that is configured,
  but I suppose that the root cause is located somewhere in arctica-
  greeter, rather than within every single binary launched by shortcuts.

  The bug was reproduced on a fresh installation of Ubuntu Mate 21.10. I
  haven't tested other versions of Ubuntu Mate yet.

  Please find additional version details below:

  $ apt-cache policy lightdm

  lightdm:
    Installed: 1.30.0-0ubuntu4
    Candidate: 1.30.0-0ubuntu4
    Version table:
   *** 1.30.0-0ubuntu4 500
  500 http://de.archive.ubuntu.com/ubuntu impish/universe amd64 Packages
  100 /var/lib/dpkg/status

  $ apt-cache policy arctica-greeter

  arctica-greeter:
    Installed: 0.99.1.5-2nmu1
    Candidate: 0.99.1.5-2nmu1
    Version table:
   *** 0.99.1.5-2nmu1 500
  500 http://de.archive.ubuntu.com/ubuntu impish/universe amd64 Packages
  100 /var/lib/dpkg/status

  Thanks,
  Basti

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/arctica-greeter/+bug/1948339/+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 1968694] Re: gnome-shell crashed with SIGSEGV in meta_window_get_window_type()

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

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 #1965897, 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/1968694/+attachment/5579799/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1965897
   gnome-shell crashed with SIGSEGV in meta_window_get_window_type(window=NULL) 
from meta_window_actor_queue_destroy() from 
meta_compositor_real_remove_window() from meta_window_unmanage() from 
meta_display_unmanage_windows()

** 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 gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1968694

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

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  The error appeared after I used ALT + F2 and typed R to restart GNOME.

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 12 11:08:25 2022
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2022-03-16 (26 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 42.0-1ubuntu1
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   meta_window_get_window_type () from /lib/x86_64-linux-gnu/libmutter-10.so.0
   ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
   ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
   meta_display_close () from /lib/x86_64-linux-gnu/libmutter-10.so.0
   shell_global_reexec_self () from /usr/lib/gnome-shell/libgnome-shell.so
  Title: gnome-shell crashed with SIGSEGV in meta_window_get_window_type()
  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/gnome-shell/+bug/1968694/+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 1966808] Re: [radeon] gnome-shell Wayland sessions fail to start on legacy Radeon systems (Failed to lock front buffer on /dev/dri/cardN: drmModeAddFB2WithModifiers failed: Inv

Fixed upstream in:
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2359

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

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

** No longer affects: gnome-shell (Ubuntu)

** Tags added: fixed-in-42.1 fixed-upstream

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

Title:
  [radeon] gnome-shell Wayland sessions fail to start on legacy Radeon
  systems (Failed to lock front buffer on /dev/dri/cardN:
  drmModeAddFB2WithModifiers failed: Invalid argument)

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

Bug description:
  Wayland started crashing for me on upgrade to Jammy, which I'm aware
  is currently in alpha.

  gdm was crashing, and changing to lightdm addressed this issue.  If I
  select 'Ubuntu on Xorg' - I can login without problems.

  If I select Wayland instead, I just get a black screen, and I have to
  kill gnome-session from a virtual console.

  WORKAROUND:

  Add this to /etc/environment:  MUTTER_DEBUG_USE_KMS_MODIFIERS=0

  ---

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42~beta-1ubuntu3
  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: Mon Mar 28 15:23:51 2022
  DisplayManager: lightdm
  InstallationDate: Installed on 2022-03-19 (9 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220318)
  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:
https://bugs.launchpad.net/mutter/+bug/1966808/+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 1966808] Re: [radeon] gnome-shell Wayland sessions fail to start on legacy Radeon systems (Failed to lock front buffer on /dev/dri/cardN: drmModeAddFB2WithModifiers failed: Inv

The fix is also coming in the next Ubuntu update:

https://salsa.debian.org/gnome-team/mutter/-/commit/c0222e9b

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

Title:
  [radeon] gnome-shell Wayland sessions fail to start on legacy Radeon
  systems (Failed to lock front buffer on /dev/dri/cardN:
  drmModeAddFB2WithModifiers failed: Invalid argument)

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

Bug description:
  Wayland started crashing for me on upgrade to Jammy, which I'm aware
  is currently in alpha.

  gdm was crashing, and changing to lightdm addressed this issue.  If I
  select 'Ubuntu on Xorg' - I can login without problems.

  If I select Wayland instead, I just get a black screen, and I have to
  kill gnome-session from a virtual console.

  WORKAROUND:

  Add this to /etc/environment:  MUTTER_DEBUG_USE_KMS_MODIFIERS=0

  ---

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42~beta-1ubuntu3
  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: Mon Mar 28 15:23:51 2022
  DisplayManager: lightdm
  InstallationDate: Installed on 2022-03-19 (9 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220318)
  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:
https://bugs.launchpad.net/mutter/+bug/1966808/+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 1962699] Re: [jammy] gnome-shell memory usage spikes when deleting files in Nautilus if dash-to-dock show-trash is enabled

Hmm, debuild -S put the wrong (upstream) project name in the tarball. Is
there a way to automate/avoid that?

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

Title:
  [jammy] gnome-shell memory usage spikes when deleting files in
  Nautilus if dash-to-dock show-trash is enabled

Status in gnome-shell-extension-dashtodock package in Ubuntu:
  Invalid
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  In Progress

Bug description:
  gnome-shell memory usage spikes when deleting files in Nautilus if
  dash-to-dock show-trash is enabled.

  For example if I delete 1500 files in Nautilus then gnome-shell
  suddenly gets 15MB bigger. It does mostly come back down within about
  10 seconds, but still not ideal for performance.

  The same bug does not occur with upstream dash-to-dock so it looks
  like this has been fixed somewhere, but not yet in jammy.

  WORKAROUND:
  gsettings set org.gnome.shell.extensions.dash-to-dock show-trash false

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell-extension-ubuntu-dock 72~ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Uname: Linux 5.15.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu78
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Wed Mar  2 14:06:54 2022
  InstallationDate: Installed on 2021-11-05 (116 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211103)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-dashtodock/+bug/1962699/+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 1962699] Re: [jammy] gnome-shell memory usage spikes when deleting files in Nautilus if dash-to-dock show-trash is enabled

** Attachment added: "gnome-shell-extension-ubuntu-dock_72~ubuntu4.dsc"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1962699/+attachment/5579784/+files/gnome-shell-extension-ubuntu-dock_72~ubuntu4.dsc

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

Title:
  [jammy] gnome-shell memory usage spikes when deleting files in
  Nautilus if dash-to-dock show-trash is enabled

Status in gnome-shell-extension-dashtodock package in Ubuntu:
  Invalid
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  In Progress

Bug description:
  gnome-shell memory usage spikes when deleting files in Nautilus if
  dash-to-dock show-trash is enabled.

  For example if I delete 1500 files in Nautilus then gnome-shell
  suddenly gets 15MB bigger. It does mostly come back down within about
  10 seconds, but still not ideal for performance.

  The same bug does not occur with upstream dash-to-dock so it looks
  like this has been fixed somewhere, but not yet in jammy.

  WORKAROUND:
  gsettings set org.gnome.shell.extensions.dash-to-dock show-trash false

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell-extension-ubuntu-dock 72~ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Uname: Linux 5.15.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu78
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Wed Mar  2 14:06:54 2022
  InstallationDate: Installed on 2021-11-05 (116 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211103)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-dashtodock/+bug/1962699/+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 1962699] Re: [jammy] gnome-shell memory usage spikes when deleting files in Nautilus if dash-to-dock show-trash is enabled

** Attachment added: "gnome-shell-extension-ubuntu-dock_72~ubuntu4.tar.xz"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1962699/+attachment/5579783/+files/gnome-shell-extension-ubuntu-dock_72~ubuntu4.tar.xz

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

Title:
  [jammy] gnome-shell memory usage spikes when deleting files in
  Nautilus if dash-to-dock show-trash is enabled

Status in gnome-shell-extension-dashtodock package in Ubuntu:
  Invalid
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  In Progress

Bug description:
  gnome-shell memory usage spikes when deleting files in Nautilus if
  dash-to-dock show-trash is enabled.

  For example if I delete 1500 files in Nautilus then gnome-shell
  suddenly gets 15MB bigger. It does mostly come back down within about
  10 seconds, but still not ideal for performance.

  The same bug does not occur with upstream dash-to-dock so it looks
  like this has been fixed somewhere, but not yet in jammy.

  WORKAROUND:
  gsettings set org.gnome.shell.extensions.dash-to-dock show-trash false

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell-extension-ubuntu-dock 72~ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Uname: Linux 5.15.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu78
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Wed Mar  2 14:06:54 2022
  InstallationDate: Installed on 2021-11-05 (116 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211103)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-dashtodock/+bug/1962699/+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 1962699] Re: [jammy] gnome-shell memory usage spikes when deleting files in Nautilus if dash-to-dock show-trash is enabled

Fix re-committed here: https://github.com/micheleg/dash-to-
dock/commits/ubuntu-dock

** Description changed:

  gnome-shell memory usage spikes when deleting files in Nautilus if dash-
  to-dock show-trash is enabled.
  
  For example if I delete 1500 files in Nautilus then gnome-shell suddenly
  gets 15MB bigger. It does mostly come back down within about 10 seconds,
- but still not ideal for performance. There is a little bit of memory
- (~10%) that is not recovered so you could call this a leak too (see
- related bug 1876641).
+ but still not ideal for performance.
  
  The same bug does not occur with upstream dash-to-dock so it looks like
  this has been fixed somewhere, but not yet in jammy.
  
  WORKAROUND:
  gsettings set org.gnome.shell.extensions.dash-to-dock show-trash false
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell-extension-ubuntu-dock 72~ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Uname: Linux 5.15.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu78
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Wed Mar  2 14:06:54 2022
  InstallationDate: Installed on 2021-11-05 (116 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211103)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: No upgrade log present (probably fresh install)

** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
   Status: Fix Committed => In Progress

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

Title:
  [jammy] gnome-shell memory usage spikes when deleting files in
  Nautilus if dash-to-dock show-trash is enabled

Status in gnome-shell-extension-dashtodock package in Ubuntu:
  Invalid
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  In Progress

Bug description:
  gnome-shell memory usage spikes when deleting files in Nautilus if
  dash-to-dock show-trash is enabled.

  For example if I delete 1500 files in Nautilus then gnome-shell
  suddenly gets 15MB bigger. It does mostly come back down within about
  10 seconds, but still not ideal for performance.

  The same bug does not occur with upstream dash-to-dock so it looks
  like this has been fixed somewhere, but not yet in jammy.

  WORKAROUND:
  gsettings set org.gnome.shell.extensions.dash-to-dock show-trash false

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell-extension-ubuntu-dock 72~ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Uname: Linux 5.15.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu78
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Wed Mar  2 14:06:54 2022
  InstallationDate: Installed on 2021-11-05 (116 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211103)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-dashtodock/+bug/1962699/+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 1968679] Re: Unable to connect to online account

2022-04-12 Thread Paul White

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

** This bug has been marked a duplicate of bug 1966418
   [jammy regression] webkit apps do not display content (yelp, epiphany, 
gnome-online-accounts etc)

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

Title:
  Unable to connect to online account

Status in gnome-online-accounts package in Ubuntu:
  New

Bug description:
  When I try to create a new connection to an online service like Google, the 
process start but the connection window stay blank and the process seems to be 
blocked.
  Screenshot added

  Ubuntu 22.04, Wayland, AMD64

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-online-accounts 3.44.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 12 08:39:27 2022
  InstallationDate: Installed on 2020-04-10 (731 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  SourcePackage: gnome-online-accounts
  UpgradeStatus: Upgraded to jammy on 2022-04-09 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1968679/+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 1962699] Re: [jammy] gnome-shell memory usage spikes when deleting files in Nautilus if dash-to-dock show-trash is enabled

** Description changed:

  gnome-shell memory usage spikes when deleting files in Nautilus if dash-
  to-dock show-trash is enabled.
  
  For example if I delete 1500 files in Nautilus then gnome-shell suddenly
- gets 15MB bigger. It does come back down within about 10 seconds, but
- still not ideal for performance.
+ gets 15MB bigger. It does mostly come back down within about 10 seconds,
+ but still not ideal for performance. There is a little bit of memory
+ (~10%) that is not recovered so you could call this a leak too (see
+ related bug 1876641).
  
  The same bug does not occur with upstream dash-to-dock so it looks like
  this has been fixed somewhere, but not yet in jammy.
  
  WORKAROUND:
  gsettings set org.gnome.shell.extensions.dash-to-dock show-trash false
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell-extension-ubuntu-dock 72~ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Uname: Linux 5.15.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu78
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Wed Mar  2 14:06:54 2022
  InstallationDate: Installed on 2021-11-05 (116 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211103)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  [jammy] gnome-shell memory usage spikes when deleting files in
  Nautilus if dash-to-dock show-trash is enabled

Status in gnome-shell-extension-dashtodock package in Ubuntu:
  Invalid
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Fix Committed

Bug description:
  gnome-shell memory usage spikes when deleting files in Nautilus if
  dash-to-dock show-trash is enabled.

  For example if I delete 1500 files in Nautilus then gnome-shell
  suddenly gets 15MB bigger. It does mostly come back down within about
  10 seconds, but still not ideal for performance. There is a little bit
  of memory (~10%) that is not recovered so you could call this a leak
  too (see related bug 1876641).

  The same bug does not occur with upstream dash-to-dock so it looks
  like this has been fixed somewhere, but not yet in jammy.

  WORKAROUND:
  gsettings set org.gnome.shell.extensions.dash-to-dock show-trash false

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell-extension-ubuntu-dock 72~ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Uname: Linux 5.15.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu78
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Wed Mar  2 14:06:54 2022
  InstallationDate: Installed on 2021-11-05 (116 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211103)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-dashtodock/+bug/1962699/+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 1967826] Re: Text entry borders are malformed (but only when using Yaru theme)

** Summary changed:

- Search entry border is jagged and clipped (when using Yaru theme)
+ Text entry borders are malformed (but only when using Yaru theme)

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

Title:
  Text entry borders are malformed (but only when using Yaru theme)

Status in Yaru Theme:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Won't Fix
Status in yaru-theme package in Ubuntu:
  Fix Committed

Bug description:
  Search entry border is jagged and clipped (when using Yaru theme). I
  use scale 200%.

  This doesn't seem to be a problem in the default GNOME theme though.

To manage notifications about this bug go to:
https://bugs.launchpad.net/yaru/+bug/1967826/+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 1968518] Re: FFe: Backport new RDP settings

2022-04-12 Thread Łukasz Zemczak

Ok, thank you for all the great context everyone! I am still worried
that all of this lands so late and just a few days before Final Freeze.
That being said, as I see that Gunnar seems to be +1 on having this
change in jammy, I would generally be fine with this FFe.

However, I see that the build FTBFS in the PPA that Robert provided?!
https://launchpad.net/~robert-ancell/+archive/ubuntu/gnome-control-center

This does feel great I must say. Have these changes not been tested
before then? Can it be made buildable and testable before we accept the
FFe and UIFe?

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

Title:
  FFe: Backport new RDP settings

Status in gnome-control-center package in Ubuntu:
  New
Status in gnome-user-docs package in Ubuntu:
  New

Bug description:
  We are shipping some GNOME 41 and some GNOME 42 components in jammy.
  In GNOME 42 the remote desktop support moved from VNC to RDP. We have
  the updated gnome-remote-desktop in jammy, but not the settings
  changes in gnome-control-center 41. The proposal is to backport these
  settings.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1968518/+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 1914279] Re: linux from security may force reboots without complete dkms modules

2022-04-12 Thread Steve Beattie

All work for this report has been completed, I believe the linux and
linux-meta tasks can be closed out as well.

** Changed in: linux (Ubuntu)
   Status: Triaged => Fix Released

** Changed in: linux-meta (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  linux from security may force reboots without complete dkms modules

Status in acpi-call package in Ubuntu:
  Fix Released
Status in apt package in Ubuntu:
  Invalid
Status in backport-iwlwifi-dkms package in Ubuntu:
  Fix Released
Status in bcmwl package in Ubuntu:
  Fix Released
Status in dahdi-linux package in Ubuntu:
  Fix Released
Status in dkms package in Ubuntu:
  Fix Released
Status in dm-writeboost package in Ubuntu:
  Fix Released
Status in evdi package in Ubuntu:
  Fix Released
Status in gost-crypto package in Ubuntu:
  Fix Released
Status in iptables-netflow package in Ubuntu:
  Fix Released
Status in liblzf package in Ubuntu:
  Fix Released
Status in lime-forensics package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-meta package in Ubuntu:
  Fix Released
Status in lttng-modules package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in openafs package in Ubuntu:
  New
Status in oss4 package in Ubuntu:
  Fix Released
Status in r8168 package in Ubuntu:
  Fix Released
Status in rtl8812au package in Ubuntu:
  Fix Released
Status in sysdig package in Ubuntu:
  Fix Released
Status in unattended-upgrades package in Ubuntu:
  Invalid
Status in update-manager package in Ubuntu:
  Invalid
Status in v4l2loopback package in Ubuntu:
  Fix Released
Status in virtualbox package in Ubuntu:
  Fix Released
Status in virtualbox-hwe package in Ubuntu:
  Fix Released
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in acpi-call source package in Focal:
  Fix Released
Status in backport-iwlwifi-dkms source package in Focal:
  Fix Released
Status in bcmwl source package in Focal:
  Fix Released
Status in dahdi-linux source package in Focal:
  Fix Released
Status in dm-writeboost source package in Focal:
  Fix Released
Status in evdi source package in Focal:
  Fix Released
Status in gost-crypto source package in Focal:
  Fix Released
Status in iptables-netflow source package in Focal:
  Fix Released
Status in liblzf source package in Focal:
  Fix Released
Status in lime-forensics source package in Focal:
  Fix Released
Status in lttng-modules source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-340 source package in Focal:
  Fix Released
Status in oss4 source package in Focal:
  Fix Released
Status in r8168 source package in Focal:
  Fix Released
Status in rtl8812au source package in Focal:
  Fix Released
Status in sysdig source package in Focal:
  Fix Released
Status in v4l2loopback source package in Focal:
  Fix Released
Status in virtualbox source package in Focal:
  Fix Released
Status in virtualbox-hwe source package in Focal:
  Fix Released
Status in zfs-linux source package in Focal:
  Fix Released

Bug description:
  Whilst discussing

  https://discourse.ubuntu.com/t/improvements-for-hardware-support-in-
  ubuntu-desktop-installation-media/20606

  We have noticed a reference to somebody not having working backport-
  iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8
  switch.

  However, kernel meta switch was pushed to security pocket, but the
  dkms modules are all in -updates only.

  This may result in people automatically installing the new kernel with
  unatanded upgrades; dkms modules failing to build; and a reboot
  required flag left on disk.

  At this point launching update manager will not offer to install dkms
  modules from updates, and will guide the users to reboot. which
  will then cause them to boot the new kernel without the dkms modules
  that might be providing networking for them.

  Should dkms modules SRUs always getting published into -security
  pocket, as well as the -updates pocket?

  Should linux maintainer scripts prevent touching reboot required flag
  if any dkms modules fail to build?

  Should apt / unattanded-upgrades / update-manager always update dkms
  modules with kernels?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1914279/+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 1968395] Re: [impish] Wayland is with the black screen when I share it

What are you using to share the screen?

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

Title:
  [impish] Wayland is with the black screen when I share it

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Wayland is with the black screen when I share it.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gnome-shell 40.5-1ubuntu2
  Uname: Linux 5.16.0-051600-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  9 01:40:22 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-03-20 (19 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1968395/+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 1968513] Re: GNOME login fails to stay in the overview if DING is enabled

I think we might need to improve on a related fix that went in 8 months
ago:

  https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1925

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

Title:
  GNOME login fails to stay in the overview if DING is enabled

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

Bug description:
  Ubuntu 22.04 (April 9 daily, latest)

  If you either disable the ubuntu-dock or remove it all together. On
  every login after that, the Activities window appears for just a few
  seconds. After those few seconds the Activities window automatically
  closes, which exposes the desktop.

  What I expected to happen is no Activity window to appear on login. I
  just want the desktop to appear, no dock, no Activities. More or less,
  I'm going for a "kiosk" type of desktop.

  Thanks for your time!

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell-extension-ubuntu-dock 72~ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 10 19:42:00 2022
  InstallationDate: Installed on 2022-04-11 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220409)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell-extension-ubuntu-dock
  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/1968513/+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 1965901] Re: SRU the new 1.18 serie to focal for hwe

2022-04-12 Thread Bin Li

Hi seb128,

Currently we met issue for Fibocom L860-GL-16(8086:7560) could cause the
ACPI reporting huge interrupts when modemmanager(1.16.6-2~20.04.1) was
started. After upgrade to 1.18.6 from https://launchpad.net/~ubuntu-
desktop/+archive/ubuntu/transitions/ , this issue is gone, although this
type modem was not supported yet.

https://bugs.launchpad.net/bugs/1964767

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

Title:
  SRU the new 1.18 serie to focal for hwe

Status in libmbim package in Ubuntu:
  New
Status in libqmi package in Ubuntu:
  New
Status in modemmanager package in Ubuntu:
  New

Bug description:
  [Impact]

  We want to update to the newer serie for better hardware support
  (support for Quectel EM120R-GL and EM160R-GL)

  [Test Plan]

   * install modemmanager, libmbim, and libqmi from -proposed
   * reboot and try WWAN function to see if any regression there.
   * perform general dogfooding of its reverse dependencies (network-
     manager, gnome-control-center etc.)

  [Where problems could occur]

  The new version no longer automatically performs the FCC unlock
  procedure by default, see details on
  https://modemmanager.org/docs/modemmanager/fcc-unlock/

  It means some modem will stop working out of the box.
  Users can manually install the unlock utility as described in the "FCC unlock 
procedures in ModemManager >= 1.18.4" section in the page above.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libmbim/+bug/1965901/+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 1967719] Re: No QXL display showing