[Desktop-packages] [Bug 1988488] Re: Screen freeze before the login screen on VirtualBox (if the third party software option was selected)

[Marian Rainer-Harbach]

I'm using VirtualBox to test upcoming Ubuntu versions using the exact
same config and packages that will later be used on several physical
machines. So it's pretty important to me to install the third-party
packages in VMs as well. But yes, I can live with the workaround for
now.

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

Title:
  Screen freeze before the login screen on VirtualBox (if the third
  party software option was selected)

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gstreamer-vaapi package in Ubuntu:
  Confirmed
Status in libx11 package in Ubuntu:
  Confirmed
Status in libxcb package in Ubuntu:
  Confirmed

Bug description:
  The problem started to appear 2 weeks ago after one of my daily
  updates. It also happens after I re-install the system from a freshly
  downloaded ISO file. The system freezes at the moment, it starts the
  gnome display manager.

  I file the bug-report after a partial upgrade just before I will
  reboot the system. If needed I can reboot in recovery mode, since the
  gnome display manager is not started in that case.

  I tried the continue button without effect and also "apt upgrade" and
  "apt dist-upgrade" do have the same effect

  I run the VM from the Host-OpenZFS file system, so I can restore to
  before the update. Recently I use a Virtualbox snapshot to restore the
  system to before the update/upgrade.

  If you need log files, let me know.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: systemd 251.4-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.23.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep  1 19:42:04 2022
  InstallationDate: Installed on 2022-05-28 (96 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220526)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 80ee:0021 VirtualBox 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/6p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
  MachineType: innotek GmbH VirtualBox
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic 
root=UUID=9eaf84b0-b69b-4760-80b5-310e3a258bda ro quiet splash
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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


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

[Desktop-packages] [Bug 1988488] Re: Screen freeze before the login screen on VirtualBox (if the third party software option was selected)

[Daniel van Vugt]

Dropped to Medium because I don't think there's any useful reason to
tick the third party software option in virtual machines. You're not
missing out on anything that a virtual machine could otherwise do.


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

** Changed in: gstreamer-vaapi (Ubuntu)
   Importance: High => Medium

** Changed in: libx11 (Ubuntu)
   Importance: High => Medium

** Changed in: libxcb (Ubuntu)
   Importance: High => Medium

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

Title:
  Screen freeze before the login screen on VirtualBox (if the third
  party software option was selected)

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gstreamer-vaapi package in Ubuntu:
  Confirmed
Status in libx11 package in Ubuntu:
  Confirmed
Status in libxcb package in Ubuntu:
  Confirmed

Bug description:
  The problem started to appear 2 weeks ago after one of my daily
  updates. It also happens after I re-install the system from a freshly
  downloaded ISO file. The system freezes at the moment, it starts the
  gnome display manager.

  I file the bug-report after a partial upgrade just before I will
  reboot the system. If needed I can reboot in recovery mode, since the
  gnome display manager is not started in that case.

  I tried the continue button without effect and also "apt upgrade" and
  "apt dist-upgrade" do have the same effect

  I run the VM from the Host-OpenZFS file system, so I can restore to
  before the update. Recently I use a Virtualbox snapshot to restore the
  system to before the update/upgrade.

  If you need log files, let me know.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: systemd 251.4-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.23.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep  1 19:42:04 2022
  InstallationDate: Installed on 2022-05-28 (96 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220526)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 80ee:0021 VirtualBox 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/6p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
  MachineType: innotek GmbH VirtualBox
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic 
root=UUID=9eaf84b0-b69b-4760-80b5-310e3a258bda ro quiet splash
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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


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

[Desktop-packages] [Bug 1979111] Re: Changing printer default still printers to previous default in browser

[Launchpad Bug Tracker]

[Expired for chromium-browser (Ubuntu) because there has been no
activity for 60 days.]

** Changed in: chromium-browser (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Changing printer default still printers to previous default in browser

Status in chromium-browser package in Ubuntu:
  Expired

Bug description:
  Ubuntu Desktop 20.04, fully updated.
  Budgie Desktop

  Pre-configured printer profiles with predefined settings so we get the
  exact profiles we need. Settings have not changed in well over a year.

  Noticed in the past few months that when a USB printer is swapped with
  a slightly different model but same manufacture we do the following.

  1. Update the device URI. Save. Test print which works.
  2. Set default printer to the new printer.
  3. In a chromium browser that has kiosk mode enabled for auto print. Attempt 
to print which prints to the previous defaulted printer.

  If that happens, we delete the previous defaulted printer profile and
  print again from the browser and it works. The entire time the browser
  hasn't been closed or refreshed.

  Run the command to add the previous default printer. Browser prints to
  the current default printer.

  Never restarted cups service between step 2 or 3.

  This has happened twice now on two different machines with the exact
  same software/configuration, possibly different printer models
  selected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1979111/+subscriptions


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

[Desktop-packages] [Bug 1975853] Re: Firefox does not respect policies.json file anymore.

[Launchpad Bug Tracker]

[Expired for firefox (Ubuntu) because there has been no activity for 60
days.]

** Changed in: firefox (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Firefox does not respect policies.json file anymore.

Status in firefox package in Ubuntu:
  Expired

Bug description:
  I use ansible to deploy policies.json file into
  /usr/lib/firefox/distribution/ folder in order to ensure that all
  family users use the same set of plugins on all of the ubuntu machines
  we have.

  I found that in ubuntu 22.04 this is not the case anymore.

  If I open the following page in firefox: about:policies I get the
  following message:

  The Enterprise Policies service is inactive.

  Please advise if this is intended and if there is a replacement
  mechanism.

  Note: I visited the documentation of mozilla and could not find
  anything on this subject related to linux.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: firefox 1:1snap1-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30
  Uname: Linux 5.15.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 26 18:12:34 2022
  InstallationDate: Installed on 2022-05-26 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Snap.Changes:
   ID   Status  Spawn  Ready  Summary
   3Done2022-05-26T12:01:32+02:00  2022-05-26T12:02:14+02:00  
Auto-refresh 4 snaps
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1988488] Re: Screen freeze before the login screen on VirtualBox

[Daniel van Vugt]

Here's the minimal fix required:

  sudo apt remove gstreamer1.0-vaapi

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

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

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

** Tags added: regression-release

** Summary changed:

- Screen freeze before the login screen on VirtualBox
+ Screen freeze before the login screen on VirtualBox (if the third party 
software option was selected)

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

Title:
  Screen freeze before the login screen on VirtualBox (if the third
  party software option was selected)

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gstreamer-vaapi package in Ubuntu:
  Confirmed
Status in libx11 package in Ubuntu:
  Confirmed
Status in libxcb package in Ubuntu:
  Confirmed

Bug description:
  The problem started to appear 2 weeks ago after one of my daily
  updates. It also happens after I re-install the system from a freshly
  downloaded ISO file. The system freezes at the moment, it starts the
  gnome display manager.

  I file the bug-report after a partial upgrade just before I will
  reboot the system. If needed I can reboot in recovery mode, since the
  gnome display manager is not started in that case.

  I tried the continue button without effect and also "apt upgrade" and
  "apt dist-upgrade" do have the same effect

  I run the VM from the Host-OpenZFS file system, so I can restore to
  before the update. Recently I use a Virtualbox snapshot to restore the
  system to before the update/upgrade.

  If you need log files, let me know.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: systemd 251.4-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.23.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep  1 19:42:04 2022
  InstallationDate: Installed on 2022-05-28 (96 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220526)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 80ee:0021 VirtualBox 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/6p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
  MachineType: innotek GmbH VirtualBox
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic 
root=UUID=9eaf84b0-b69b-4760-80b5-310e3a258bda ro quiet splash
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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


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

[Desktop-packages] [Bug 1988488] Re: Screen freeze before the login screen on VirtualBox (if the third party software option was selected)

[Daniel van Vugt]

Looks like a bug in libx11 or libxcb because I don't think it's meant to
be possible for XOpenDisplay() to hang.

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

Title:
  Screen freeze before the login screen on VirtualBox (if the third
  party software option was selected)

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gstreamer-vaapi package in Ubuntu:
  Confirmed
Status in libx11 package in Ubuntu:
  Confirmed
Status in libxcb package in Ubuntu:
  Confirmed

Bug description:
  The problem started to appear 2 weeks ago after one of my daily
  updates. It also happens after I re-install the system from a freshly
  downloaded ISO file. The system freezes at the moment, it starts the
  gnome display manager.

  I file the bug-report after a partial upgrade just before I will
  reboot the system. If needed I can reboot in recovery mode, since the
  gnome display manager is not started in that case.

  I tried the continue button without effect and also "apt upgrade" and
  "apt dist-upgrade" do have the same effect

  I run the VM from the Host-OpenZFS file system, so I can restore to
  before the update. Recently I use a Virtualbox snapshot to restore the
  system to before the update/upgrade.

  If you need log files, let me know.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: systemd 251.4-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.23.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep  1 19:42:04 2022
  InstallationDate: Installed on 2022-05-28 (96 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220526)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 80ee:0021 VirtualBox 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/6p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
  MachineType: innotek GmbH VirtualBox
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic 
root=UUID=9eaf84b0-b69b-4760-80b5-310e3a258bda ro quiet splash
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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


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

[Desktop-packages] [Bug 1988488] Re: Screen freeze before the login screen on VirtualBox (if the third party software option was selected)

[Daniel van Vugt]

I think the problem is gnome-shell waiting for this command (which never
finishes):

/usr/lib/x86_64-linux-gnu/gstreamer1.0/gstreamer-1.0/gst-plugin-scanner
-l /usr/bin/gnome-shell

because it's waiting for an X server (which does exist as Xwayland):

#0  0x7f76ea710ec4 in __GI___poll (fds=0x7ffed6d30280, nfds=1, timeout=-1) 
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7f76e9c78e23 in ?? () from /lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7f76e9c7c522 in xcb_connect_to_fd () from 
/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7f76e9c7cedc in xcb_connect_to_display_with_auth_info () from 
/lib/x86_64-linux-gnu/libxcb.so.1
#4  0x7f76e9e57eea in _XConnectXCB () from /lib/x86_64-linux-gnu/libX11.so.6
#5  0x7f76e9e47d17 in XOpenDisplay () from /lib/x86_64-linux-gnu/libX11.so.6
#6  0x7f76ea37c537 in ?? () from 
/usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstvaapi.so
#7  0x7f76ea353d28 in ?? () from 
/usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstvaapi.so
#8  0x7f76ea3181f7 in ?? () from 
/usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstvaapi.so
#9  0x7f76eaae85c5 in ?? () from /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
#10 0x7f76eaaef84d in ?? () from /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
#11 0x7f76eaaf08f4 in ?? () from /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
#12 0x7f76eaaf19b8 in _gst_plugin_loader_client_run () from 
/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
#13 0x55c6eaeb61dc in ?? ()
#14 0x7f76ea623510 in __libc_start_call_main 
(main=main@entry=0x55c6eaeb6120, argc=argc@entry=3, 
argv=argv@entry=0x7ffed6d30c98) at ../sysdeps/nptl/libc_start_call_main.h:58
#15 0x7f76ea6235c9 in __libc_start_main_impl (main=0x55c6eaeb6120, argc=3, 
argv=0x7ffed6d30c98, init=, 
fini=, rtld_fini=, stack_end=0x7ffed6d30c88) 
at ../csu/libc-start.c:381
#16 0x55c6eaeb6235 in _start ()


** Also affects: gstreamer1.0 (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: gstreamer1.0 (Ubuntu)

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

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

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

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

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

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

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

Title:
  Screen freeze before the login screen on VirtualBox (if the third
  party software option was selected)

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gstreamer-vaapi package in Ubuntu:
  Confirmed
Status in libx11 package in Ubuntu:
  Confirmed
Status in libxcb package in Ubuntu:
  Confirmed

Bug description:
  The problem started to appear 2 weeks ago after one of my daily
  updates. It also happens after I re-install the system from a freshly
  downloaded ISO file. The system freezes at the moment, it starts the
  gnome display manager.

  I file the bug-report after a partial upgrade just before I will
  reboot the system. If needed I can reboot in recovery mode, since the
  gnome display manager is not started in that case.

  I tried the continue button without effect and also "apt upgrade" and
  "apt dist-upgrade" do have the same effect

  I run the VM from the Host-OpenZFS file system, so I can restore to
  before the update. Recently I use a Virtualbox snapshot to restore the
  system to before the update/upgrade.

  If you need log files, let me know.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: systemd 251.4-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.23.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep  1 19:42:04 2022
  InstallationDate: Installed on 2022-05-28 (96 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220526)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 80ee:0021 VirtualBox 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/6p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
  MachineType: innotek GmbH VirtualBox
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic 
root=UUID=9eaf84b0-b69b-4760-80b5-310e3a258bda ro quiet splash
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board

[Desktop-packages] [Bug 1949605] Re: Backport Thunderbird 91 to 20.04 LTS and 18.04 LTS

[Rolando Gorgs]

The Thunderbird story goes on here:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1990886

;-)

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

Title:
  Backport Thunderbird 91 to 20.04 LTS and 18.04 LTS

Status in thunderbird package in Ubuntu:
  Fix Released
Status in thunderbird source package in Bionic:
  Fix Released
Status in thunderbird source package in Focal:
  Fix Released
Status in thunderbird source package in Hirsute:
  Fix Released

Bug description:
  Similarly to bug #1895643, which was about upgrading thunderbird from
  68 to 78 in all supported Ubuntu releases, this bug is to track the
  update from thunderbird 78 to 91 in hirsute, focal and bionic.

  The rationale is that series 78 will soon be out of support (the last
  release, 78.14.0, was made public on September 7, 2021).

  Thunderbird follows the Firefox ESR release cycle, and the
  next/current series is 91 (already available in impish and jammy).

  User-facing announcement: https://discourse.ubuntu.com/t/thunderbird-
  lts-update-78-to-91/25391.

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


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

[Desktop-packages] [Bug 1990886] Re: Security updates missing after 91.11.0

[Rolando Gorgs]

Hello Olivier,

thank you very much for your efforts but I have to bring this up here:
Having "some general friction with following upstream" seems to be an ongoing 
problem with Thunderbird.

Transition from TB 68 to 78 left users of ubuntus latest LTS without security 
updates for over 6 months
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1895643

>From TB 78 to 91 the (un)security gap for (latest) LTS users has been over 4 
>months
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1949605

and now in the transition between TB 91 and 102 we are already over 3
months without security updates.

All this for the at that points of time latest Ubuntu LTS. Older LTS
have/had to wait even longer for security updates.

At the same time unpatched security vulnerabilities and CVEs are popping
up more and more.

I've been watching this misery for years now and I really appreciate
Olivier's efforts, but there seems to be something fundamentally wrong
here.

Besides browsers, mail clients are the second most exposed user
applications and a classic gateway for malware. It is unacceptable that
Thunderbird regularly exists unpatched for so long periods of time. This
sheds a very bad light on Ubuntu's security.

I know that there are optional Snaps but the vast majority of users
stick with the pre-installed programs and are led to believe that they
will receive regular updates this way. And they should be right about
that.

So what can be done to fix this issue once and for all?

/edit: and how long will it take this time?

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

Title:
  Security updates missing after 91.11.0

Status in thunderbird package in Ubuntu:
  In Progress

Bug description:
  Upstream released Thunderbird 91.11.0 on June 28, 2022.
  It's now at 91.13.1 from September 19, 2022. The release notes say:
  "By popular demand, Thunderbird 91.13.1 contains important security updates 
that shipped in Thunderbird 102.2.1. Users are encouraged to update as soon as 
possible."
  Source: https://www.thunderbird.net/en-US/thunderbird/91.13.1/releasenotes/

  Ubuntu 22.04 Jammy (but also the other supported LTS) still has Thunderbird 
91.11.0 (1:91.11.0+build2-0ubuntu0.22.04.1) without the security fixes after 
91.11.0.
  The package should be updated to 91.13.1.

  Given that it has been three months without security updates, there
  seems to be some general friction with following upstream.

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


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

[Desktop-packages] [Bug 1991598] Re: laptop not reliably going to sleep when lid closed on battery power

[Daniel van Vugt]

Thanks for the bug report. Please start by deleting all local
extensions:

  cd ~/.local/share/gnome-shell
  rm -rf extensions

and log in again. Does the bug still occur?


** Package changed: gnome-shell (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 gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1991598

Title:
  laptop not reliably going to sleep when lid closed on battery power

Status in Ubuntu:
  Incomplete

Bug description:
  I have the shell configured to lock the screen when I close the lid
  and go to sleep after 20 idle minutes on battery power.

  Immediately before I opened my laptop and unlocked it to submit this
  bug, the laptop was unplugged from battery power and sitting with the
  lid closed for hours and never went to sleep.

  When I opened the lid I found it locked as it should have been, so
  that's apparently not the issue. The issue is that it just never went
  to sleep even though it was idle for hours.

  This is a regression from Jammy.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-shell 43.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct  3 21:24:57 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-08-16 (1144 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  RelatedPackageVersions: mutter-common 43.0-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to kinetic on 2022-09-24 (9 days ago)

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


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

[Desktop-packages] [Bug 1991581] Re: Gnome restarts along with all apps when waking from sleep

[Daniel van Vugt]

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1970917, so it 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. Feel free to continue to report any other bugs you may
find.


** This bug has been marked a duplicate of bug 1970917
   gnome-shell crashes with SIGABRT due to assertion failure "!window->monitor 
|| g_list_find (meta_monitor_manager_get_logical_monitors (monitor_manager), 
window->monitor)" in meta_window_update_for_monitors_changed()

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

Title:
  Gnome restarts along with all apps when waking from sleep

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Using frame.work gen 12 i7 1260p after recent update gnome restarts
  after waking from sleep (or perhaps when sleeping, hard to tell). All
  gui apps are killed.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.4-0ubuntu0.22.04.1
  ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
  Uname: Linux 5.15.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  Date: Mon Oct  3 15:31:13 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-09-13 (20 days ago)
  InstallationMedia: Ubuntu Web
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 42.2-0ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to jammy on 2022-09-13 (20 days ago)

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


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

[Desktop-packages] [Bug 1991526] Re: Panel freezes on return from screensaver with external monitor attached

[Daniel van Vugt]

Thanks for the bug report. Next time the problem happens and unfreezes,
please run:

  journalctl -b0 > journal.txt

and attach the resulting text file here.

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

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

** Tags added: multimonitor

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

Title:
  Panel freezes on return from screensaver with external monitor
  attached

Status in Ubuntu:
  Incomplete

Bug description:
  My setup is composed of a Dell XPS13 9320, with one (or two) external
  USB-C monitors attached. The laptop panel is the primary screen. I'm
  using gnome on Wayland.

  Everything is working fine, except when resuming from screensaver: the
  prompt for password is shown on the laptop panel, and I start typing
  the password. At this point, the laptop panel freezes. This can happen
  almost immediately (I will see for example two or three dots as I
  typed the first characters of my password) or this can happen a few
  seconds later (meanwhile the screen has been unlocked, the panel shows
  the desktop, then it freezes).

  Interestingly, the external monitors are woken up, desktop is
  unlocked, and will continue working, while the laptop panel is frozen.

  After that, let's say 40% of the time, the panel will un-freeze itself
  after 30 seconds or so. 40% of the time it will remain frozen, and 20%
  of the time the whole display will freeze (including the external
  monitors).

  When it happens, I can recover by either un-plugging / re-plugging one
  of the external monitors, or by typing Ctrl-Alt-F1, then retyping my
  password, then everything is fine again... until the next screen lock.

  This bug is reproducible more or less 50% of the time (one in two
  screen locks causes freezes). Deactivating the dash-to-panel gnome
  extension made it less reproducible, but it still happens.

  I didn't see any interesting error message in the logs, but maybe I
  didn't look at the correct place.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gdm3 42.0-1ubuntu7
  ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
  Uname: Linux 5.15.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct  3 13:54:42 2022
  ExecutablePath: /usr/libexec/gdm-wayland-session
  InstallationDate: Installed on 2022-07-20 (75 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  ProcEnviron:
   SHELL=/bin/bash
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   XDG_RUNTIME_DIR=
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1990783] Re: distorted mouse pointer under Wayland in Kinetic

[Daniel van Vugt]

** Tags added: kinetic

** Tags added: wayland wayland-session

** Tags added: radeon

** Summary changed:

- distorted mouse pointer under Wayland in Kinetic
+ [radeon] Distorted mouse pointer under Wayland in Kubuntu 22.10

** No longer affects: wayland (Ubuntu)

** Bug watch added: KDE Bug Tracking System #456306
   https://bugs.kde.org/show_bug.cgi?id=456306

** Also affects: kdebase-workspace via
   https://bugs.kde.org/show_bug.cgi?id=456306
   Importance: Unknown
   Status: Unknown

** Tags added: cursor

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

Title:
  [radeon] Distorted mouse pointer under Wayland in Kubuntu 22.10

Status in KDE Base Workspace:
  Unknown
Status in kwin package in Ubuntu:
  New

Bug description:
  After upgrading to Kubuntu 22.10 Kinetic dev. I found mouse pointer
  distorted. Please, look at attached screenshot. Under X session mouse
  pointer looks as it should be.

To manage notifications about this bug go to:
https://bugs.launchpad.net/kdebase-workspace/+bug/1990783/+subscriptions


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

[Desktop-packages] [Bug 1960417] Re: Show applications in alphabetical order

[Bug Watch Updater]

** Changed in: gnome-shell
   Status: Unknown => 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/1960417

Title:
  Show applications in alphabetical order

Status in GNOME Shell:
  New
Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  ***
  *** Please change package to the appropriate one
  ***

  In Ubuntu 22.04, the "Show Applications" icon at the bottom of the
  launcher gives the apps in undesired order.

  This needs to be sorted in ascending order.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gedit 40.1-3
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Uname: Linux 5.15.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu76
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb  9 09:52:54 2022
  InstallationDate: Installed on 2022-02-06 (2 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220202)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gedit
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1970917] Re: gnome-shell crashes with SIGABRT due to assertion failure "!window->monitor || g_list_find (meta_monitor_manager_get_logical_monitors (monitor_manager), window->mo

[Daniel van Vugt]

Oh, actually the fix is already queued for mutter update 42.4 :)

** Also affects: mutter (Ubuntu Kinetic)
   Importance: High
   Status: Fix Released

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

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

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

** Tags added: fixed-in-42.4

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

Title:
  gnome-shell crashes with SIGABRT due to assertion failure
  "!window->monitor || g_list_find
  (meta_monitor_manager_get_logical_monitors (monitor_manager),
  window->monitor)" in meta_window_update_for_monitors_changed()

Status in Mutter:
  Unknown
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Jammy:
  Fix Committed
Status in mutter source package in Kinetic:
  Fix Released

Bug description:
  gnome-shell crashes with SIGABRT due to assertion failure:

  "!window->monitor || g_list_find
  (meta_monitor_manager_get_logical_monitors (monitor_manager),
  window->monitor)"

  in meta_window_update_for_monitors_changed().

  However a bug in errors.ubuntu.com is hiding it. Sometimes it is
  visible on
  https://errors.ubuntu.com/problem/bc718fcc290d04f4e23c6246836d992f140e7058
  (when the last crash report was from jammy) and sometimes not
  (impish).

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


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

[Desktop-packages] [Bug 1970917] Re: gnome-shell crashes with SIGABRT due to assertion failure "!window->monitor || g_list_find (meta_monitor_manager_get_logical_monitors (monitor_manager), window->mo

[Daniel van Vugt]

The upstream fix
(https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2554) is in
Ubuntu 22.10 already but it's relatively new and relatively complex. We
would need to wait a while for the fix to mature before considering
backports to 22.04.

In the meantime, if this bug is a major issue for you then I can only
recommend switching to 22.10 early: https://cdimage.ubuntu.com/daily-
live/current/

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

Title:
  gnome-shell crashes with SIGABRT due to assertion failure
  "!window->monitor || g_list_find
  (meta_monitor_manager_get_logical_monitors (monitor_manager),
  window->monitor)" in meta_window_update_for_monitors_changed()

Status in Mutter:
  Unknown
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Jammy:
  Fix Committed
Status in mutter source package in Kinetic:
  Fix Released

Bug description:
  gnome-shell crashes with SIGABRT due to assertion failure:

  "!window->monitor || g_list_find
  (meta_monitor_manager_get_logical_monitors (monitor_manager),
  window->monitor)"

  in meta_window_update_for_monitors_changed().

  However a bug in errors.ubuntu.com is hiding it. Sometimes it is
  visible on
  https://errors.ubuntu.com/problem/bc718fcc290d04f4e23c6246836d992f140e7058
  (when the last crash report was from jammy) and sometimes not
  (impish).

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


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

[Desktop-packages] [Bug 1960417] Re: Show applications in alphabetical order

[Daniel van Vugt]

There are at least three faster alternatives:

 - Right click on app icons and select 'Add to Favorites' to make them
permanent in the dock/dash.

 - Drag and drop your most frequently used app icons to the first page.

 - Type part of the name of the app you want in Search.

If for some reason none of those are convenient then your original
request is also being tracked in https://gitlab.gnome.org/GNOME/gnome-
shell/-/issues/4684

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

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

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

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

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

Title:
  Show applications in alphabetical order

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  ***
  *** Please change package to the appropriate one
  ***

  In Ubuntu 22.04, the "Show Applications" icon at the bottom of the
  launcher gives the apps in undesired order.

  This needs to be sorted in ascending order.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gedit 40.1-3
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Uname: Linux 5.15.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu76
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb  9 09:52:54 2022
  InstallationDate: Installed on 2022-02-06 (2 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220202)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gedit
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1970058] Re: Order of app icons in application grid seems to be random (not sorted alphabetically)

[Daniel van Vugt]

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

** This bug has been marked a duplicate of bug 1960417
   Show applications in alphabetical order

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

Title:
  Order of app icons in application grid seems to be random (not sorted
  alphabetically)

Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  I tried out Ubuntu 22.04 today, and the app icons in the application
  grid (or applications overview, I'm not sure what's the official name)
  seem to be sorted in random order (they're probably sorted, but I
  can't figure out how). I think it would be better if the app icons
  were sorted alphabetically by default after a fresh install.

  I know the icons can be rearranged manually, but I don't think this
  makes this issue less relevant.

  In Ubuntu 20.04 the icons were always sorted alphabetically (but on
  the other hand there was no way to reorder them if so desired).

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


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

[Desktop-packages] [Bug 1991598] [NEW] laptop not reliably going to sleep when lid closed on battery power

[Jonathan Kamens]

Public bug reported:

I have the shell configured to lock the screen when I close the lid and
go to sleep after 20 idle minutes on battery power.

Immediately before I opened my laptop and unlocked it to submit this
bug, the laptop was unplugged from battery power and sitting with the
lid closed for hours and never went to sleep.

When I opened the lid I found it locked as it should have been, so
that's apparently not the issue. The issue is that it just never went to
sleep even though it was idle for hours.

This is a regression from Jammy.

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: gnome-shell 43.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
Uname: Linux 5.19.0-15-generic x86_64
ApportVersion: 2.23.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct  3 21:24:57 2022
DisplayManager: gdm3
InstallationDate: Installed on 2019-08-16 (1144 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
RelatedPackageVersions: mutter-common 43.0-1ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to kinetic on 2022-09-24 (9 days ago)

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


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

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

Title:
  laptop not reliably going to sleep when lid closed on battery power

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I have the shell configured to lock the screen when I close the lid
  and go to sleep after 20 idle minutes on battery power.

  Immediately before I opened my laptop and unlocked it to submit this
  bug, the laptop was unplugged from battery power and sitting with the
  lid closed for hours and never went to sleep.

  When I opened the lid I found it locked as it should have been, so
  that's apparently not the issue. The issue is that it just never went
  to sleep even though it was idle for hours.

  This is a regression from Jammy.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-shell 43.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct  3 21:24:57 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-08-16 (1144 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  RelatedPackageVersions: mutter-common 43.0-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to kinetic on 2022-09-24 (9 days ago)

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


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

[Desktop-packages] [Bug 1990010] Re: VA error: resource allocation failed

[Bram Stolk]

I tried building a snap with 104.0.5112.101 version of chromium, and
that gives me working HW-decode on Wayland.

A later change in chromium must have broken vaapi playback.

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

Title:
  VA error: resource allocation failed

Status in chromium-browser package in Ubuntu:
  In Progress

Bug description:
  https://github.com/intel/media-driver/issues/1498

  ---

  When I play a H264/AAC video with HW decoding enabled on Alderlake
  12600k, using Wayland I get the error:

  vaCreateSurfaces (import mode) failed, VA error: resource allocation
  failed

  After which, chromium will proceed to play the video without HW
  acceleration using ffmpeg.

  This is both with using the pre-built snap from channel beta/hwacc and
  a snap built from source.

  (NOTE: HW decoding does work with same browser on X11 desktop, using
  VDAVideoDecoder.)

  To get more information on this VA error, I built the snap with debug
  versions of gmmlib and media-driver (latest git) using the latest git
  from valib as well.

  The log output from chromium now mentions why the allocation fails:

  [390012:14:0916/112615.428584:INFO:decoder.cc(41)] DecryptingVideoDecoder
  [389969:390095:0916/112615.445970:INFO:decoder.cc(65)] VDAVideoDecoder
  [390012:14:0916/112615.449426:INFO:decoder.cc(65)] VDAVideoDecoder
  [390012:14:0916/112615.449500:INFO:decoder.cc(65)] VDAVideoDecoder
  [LIBVA]:CRITICAL - DdiMediaUtil_AllocateSurface:378: Unsupported modifier.
  [389969:389969:0916/112615.467062:ERROR:vaapi_wrapper.cc(2389)] 
vaCreateSurfaces (import mode) failed, VA error: resource allocation failed
  
[389969:389969:0916/112615.467212:ERROR:vaapi_picture_native_pixmap_ozone.cc(66)]
 Failed creating VASurface for NativePixmap
  [LIBVA]:CRITICAL - DdiMediaUtil_AllocateSurface:378: Unsupported modifier.
  [389969:389969:0916/112615.468871:ERROR:vaapi_wrapper.cc(2389)] 
vaCreateSurfaces (import mode) failed, VA error: resource allocation failed
  
[389969:389969:0916/112615.468987:ERROR:vaapi_picture_native_pixmap_ozone.cc(66)]
 Failed creating VASurface for NativePixmap
  
[389969:389969:0916/112615.469140:ERROR:vaapi_video_decode_accelerator.cc(129)] 
{"code":6,"data":{},"group":"VaapiStatusCode","message":"","stack":[{"file":"media/gpu/vaapi/vaapi_picture_native_pixmap_ozone.cc","line":67}]}
  [390012:14:0916/112615.469740:INFO:decoder.cc(32)] VpxVideoDecoder
  [390012:14:0916/112615.470169:INFO:decoder.cc(44)] Dav1dVideoDecoder
  [390012:14:0916/112615.471713:INFO:decoder.cc(29)] FFmpegVideoDecoder
  [390012:14:0916/112615.471819:INFO:decoder.cc(29)] FFmpegVideoDecoder

  Note the message: "DdiMediaUtil_AllocateSurface:378: Unsupported
  modifier."

  I am on wayland, and use these chromium flags:

  export CHROMIUM_FLAGS="--enable-logging=stderr --use-gl=egl --enable-
  features=VaapiVideoDecoder,VaapiVideoEncoder --disable-
  features=UseChromeOSDirectVideoDecoder --ignore-gpu-blocklist
  --disable-gpu-driver-bug-workaround --ozone-platform=wayland"

  The video that fails: the 1080p/60 version downloaded from here:
  https://github.com/chthomos/video-media-samples/

  I will figure out which is the "unsupported modifier" and report back,
  here.

  Note: currently gmmlib and media-driver have failing debug builds, but I have 
created pull requests to both:
  https://github.com/intel/media-driver/pull/1491
  https://github.com/intel/gmmlib/pull/97

  CPU: 12600k

  GPU: Intel Alderlake_s (Gen12)

  Snap built with: core20

  Host OS: Ubuntu Kinetic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1990010/+subscriptions


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

[Desktop-packages] [Bug 1982699] Re: brltty breaks ttyUSB0 needed by Arduino

[Steve Langasek]

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

** This bug has been marked a duplicate of bug 1958224
   brltty claiming cp210x devices on 22.04

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

Title:
  brltty breaks ttyUSB0 needed by Arduino

Status in brltty package in Ubuntu:
  New

Bug description:
  BRLTTY breaks ttyUSB0 needed by Arduino

  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=22.04
  DISTRIB_CODENAME=jammy
  DISTRIB_DESCRIPTION="Ubuntu 22.04 LTS"
  PRETTY_NAME="Ubuntu 22.04 LTS"
  NAME="Ubuntu"
  VERSION_ID="22.04"
  VERSION="22.04 LTS (Jammy Jellyfish)"
  VERSION_CODENAME=jammy
  ID=ubuntu
  ID_LIKE=debian
  HOME_URL="https://www.ubuntu.com/";
  SUPPORT_URL="https://help.ubuntu.com/";
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/";
  
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy";
  UBUNTU_CODENAME=jammy

  [50272.956677] usb 5-1: USB disconnect, device number 2
  [50280.000551] usb 5-1: new full-speed USB device number 3 using xhci_hcd
  [50280.174486] usb 5-1: New USB device found, idVendor=10c4, idProduct=ea60, 
bcdDevice= 1.00
  [50280.174491] usb 5-1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [50280.174492] usb 5-1: Product: CP2104 USB to UART Bridge Controller
  [50280.174493] usb 5-1: Manufacturer: Silicon Labs
  [50280.174494] usb 5-1: SerialNumber: 014A135D
  [50280.193001] usbcore: registered new interface driver usbserial_generic
  [50280.193014] usbserial: USB Serial support registered for generic
  [50280.198881] usbcore: registered new interface driver cp210x
  [50280.198892] usbserial: USB Serial support registered for cp210x
  [50280.198915] cp210x 5-1:1.0: cp210x converter detected
  [50280.203407] usb 5-1: cp210x converter now attached to ttyUSB0
  [50280.208036] input: PC Speaker as /devices/platform/pcspkr/input/input27
  [50280.720855] input: BRLTTY 6.4 Linux Screen Driver Keyboard as 
/devices/virtual/input/input28
  [50280.920521] usb 5-1: usbfs: interface 0 claimed by cp210x while 'brltty' 
sets config #1
  [50280.923631] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0
  [50280.923702] cp210x 5-1:1.0: device disconnected

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xfce4-terminal 0.8.10-1
  ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39
  Uname: Linux 5.15.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: XFCE
  Date: Sun Jul 24 16:58:57 2022
  ExecutablePath: /usr/bin/xfce4-terminal
  InstallationDate: Installed on 2022-07-24 (0 days ago)
  InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: xfce4-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1973470] Re: Ubuntu-bug command can't find Firefox on Lubuntu Kinetic

[Steve Langasek]

** Tags added: foundations-todo

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

Title:
  Ubuntu-bug command can't find Firefox on Lubuntu Kinetic

Status in Apport:
  Triaged
Status in apport package in Ubuntu:
  Triaged
Status in xdg-utils package in Ubuntu:
  Invalid

Bug description:
  Test hardware is an Elitebook 8570p, 16 GB RAM, 120 GB SSD.

  While reporting Bug #1973469, I discovered that ubuntu-bug was unable
  to open Firefox at the very end of the process. Sadly, I closed the
  terminal window that contained the initial error, but I was able to
  easily reproduce it reporting this bug. The full console output of
  "ubuntu-bug apport" on Lubuntu Kinetic is:

  
  *** Collecting problem information

  The collected information can be sent to the developers to improve the
  application. This might take a few minutes.
  ..

  *** Send problem report to the developers?

  After the problem report has been sent, please fill out the form in the
  automatically opened web browser.

  What would you like to do? Your options are:
S: Send report (5.1 KB)
V: View report
K: Keep report file for sending later or copying to somewhere else
I: Cancel and ignore future crashes of this program version
C: Cancel
  Please choose (S/V/K/I/C): s

  *** Uploading problem information

  The collected information is being sent to the bug tracking system.
  This might take a few minutes.
  94%

  *** To continue, you must visit the following URL:

  
https://bugs.launchpad.net/ubuntu/+source/apport/+filebug/d7ffa3e0-d46d-11ec-a167-40a8f03099c8?

  You can launch a browser now, or copy this URL into a browser on
  another computer.

  
  Choices:
1: Launch a browser now
C: Cancel
  Please choose (1/C): 1
  /usr/bin/xdg-open: 882: firefox: not found
  /usr/bin/xdg-open: 882: firefox: not found
  xdg-open: no method available for opening 
'https://bugs.launchpad.net/ubuntu/+source/apport/+filebug/d7ffa3e0-d46d-11ec-a167-40a8f03099c8?'

  I am unsure if this problem is in Apport or Lubuntu. ubuntu-bug works
  just fine for me on Ubuntu Kinetic, but not on Lubuntu. I suspect this
  is due to the Snap version of Firefox, but I don't know for sure.
  Since ubuntu-bug is what gave me the error, I'm filing this against
  Apport.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: apport 2.20.11-0ubuntu82
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.470
  CurrentDesktop: LXQt
  Date: Sun May 15 11:41:07 2022
  LiveMediaBuild: Lubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220514)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1944519] Re: Xubuntu shutdown prompt is missing

[Steve Langasek]

** Changed in: plymouth (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  Xubuntu shutdown prompt is missing

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

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

  Live session shutdown prompt is missing - system reboots at once

  Testing Ubuntu Mate Impish ISO 22.09,2021

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

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

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1944519/+subscriptions


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

[Desktop-packages] [Bug 1991253] Re: Fix test failure in abseil 0~20210324.2-4

[Launchpad Bug Tracker]

This bug was fixed in the package abseil - 0~20210324.2-4ubuntu1

---
abseil (0~20210324.2-4ubuntu1) kinetic; urgency=medium

  * d/p/emplace-bug-supression-gcc12.diff: Backported from upstream to fix
any-test.cc segmentation fault (LP: #1991253).

 -- Nathan Pratta Teodosio   Thu, 29 Sep
2022 09:47:28 -0300

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

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

Title:
  Fix test failure in abseil 0~20210324.2-4

Status in abseil package in Ubuntu:
  Fix Released

Bug description:
  Abseil is failing to build in Kinetic because of a segmentation fault
  in test phase[1].

  I'm forwarding a fix from upstream.

  [1]: https://launchpadlibrarian.net/625442454/buildlog_ubuntu-kinetic-
  amd64.abseil_0~20210324.2-4_BUILDING.txt.gz

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


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

[Desktop-packages] [Bug 1990997] Re: en_ZA locale not correct in applications

[Kai-Heng Feng]

** Package changed: linux (Ubuntu) => libreoffice (Ubuntu)

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

Title:
  en_ZA locale not correct in applications

Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  In all Ubuntu based distributions I have found that in applications
  such as LibreOffice Calc where I need to see formats applicable to my
  locale en_ZA (South Africa) the decimal place is denoted by , in the
  application even though the file /usr/share/i18n/locales/en_ZA is
  correct in specifying the decimal place as denoted by a .

  This is the same for monetary values where it is showing , in
  applications instead of the . as specified in the locale file. The
  comma was deprecated in South Africa in the 1990s and the generally
  accepted decimal is .

  This makes it extremely difficult to transfer Windows Excel files that
  have decimal points to a Linux distro that strictly enforces
  recognising a decimal with a comma and hence renders the Windows Excel
  file useless in Linux.

  The Windows feature of customising locales in terms of date, time,
  decimal place and digit grouping within the GUI is sorely missing from
  all desktops in Linux and so this cannot be fixed by the end-user.

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


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

[Desktop-packages] [Bug 1990997] [NEW] en_ZA locale not correct in applications

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

In all Ubuntu based distributions I have found that in applications such
as LibreOffice Calc where I need to see formats applicable to my locale
en_ZA (South Africa) the decimal place is denoted by , in the
application even though the file /usr/share/i18n/locales/en_ZA is
correct in specifying the decimal place as denoted by a .

This is the same for monetary values where it is showing , in
applications instead of the . as specified in the locale file. The comma
was deprecated in South Africa in the 1990s and the generally accepted
decimal is .

This makes it extremely difficult to transfer Windows Excel files that
have decimal points to a Linux distro that strictly enforces recognising
a decimal with a comma and hence renders the Windows Excel file useless
in Linux.

The Windows feature of customising locales in terms of date, time,
decimal place and digit grouping within the GUI is sorely missing from
all desktops in Linux and so this cannot be fixed by the end-user.

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


** Tags: africa currency decimal locale south za
-- 
en_ZA locale not correct in applications
https://bugs.launchpad.net/bugs/1990997
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to libreoffice 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 1980889] Re: X crashes with qxl(0): error doing QXL_ALLOC

[Ellis Whitehead]

I'm seeing the same error with a Xubuntu 22.04 VM.

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

Title:
  X crashes with qxl(0): error doing QXL_ALLOC

Status in xserver-xorg-video-qxl package in Ubuntu:
  Confirmed

Bug description:
  Have Lubuntu 22.04 installed in a virtual machine created with virt-
  manager. The X server will randomly crash with only Firefox and
  Thunderbird running, with one or the other minimized.

  Old bug reports found online suggested increasing the "vram" setting
  to 256 MiB (262144 in the XML file) fixed this problem, however at
  that setting, it crashed and this latest crash is when the "vram" was
  set to 512 MiB (524288 in the XML file).

  Below is the text from the Xorg.0.log.old file from the point of the
  crash. The crash of the X server terminated this particular log.

  [54.773] (II) event4  - spice vdagent tablet: device is a pointer
  [  3431.844] (EE) qxl(0): error doing QXL_ALLOC
  [  3431.844] (EE)
  [  3431.844] (EE) Backtrace:
  [  3431.861] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x56450cb3f2b9]
  [  3431.863] (EE) 1: /lib/x86_64-linux-gnu/libc.so.6 (__sigaction+0x50) 
[0x7fdab48da520]
  [  3431.864] (EE) unw_get_proc_name failed: no unwind info found [-10]
  [  3431.864] (EE) 2: /usr/lib/xorg/modules/drivers/qxl_drv.so (?+0x0) 
[0x7fdab413fb2d]
  [  3431.865] (EE) unw_get_proc_name failed: no unwind info found [-10]
  [  3431.865] (EE) 3: /usr/lib/xorg/modules/drivers/qxl_drv.so (?+0x0) 
[0x7fdab413ffc7]
  [  3431.866] (EE) unw_get_proc_name failed: no unwind info found [-10]
  [  3431.867] (EE) 4: /usr/lib/xorg/modules/drivers/qxl_drv.so (?+0x0) 
[0x7fdab414c7c0]
  [  3431.869] (EE) 5: /usr/lib/xorg/Xorg (miCopyRegion+0x9b) [0x56450cb1c59b]
  [  3431.870] (EE) 6: /usr/lib/xorg/Xorg (miDoCopy+0x456) [0x56450cb1ccf6]
  [  3431.872] (EE) unw_get_proc_name failed: no unwind info found [-10]
  [  3431.872] (EE) 7: /usr/lib/xorg/modules/drivers/qxl_drv.so (?+0x0) 
[0x7fdab414ca02]
  [  3431.873] (EE) 8: /usr/lib/xorg/Xorg (DamageRegionAppend+0x3886) 
[0x56450caafa86]
  [  3431.873] (EE) 9: /usr/lib/xorg/Xorg (SendGraphicsExpose+0x2cd) 
[0x56450c9c4efd]
  [  3431.874] (EE) 10: /usr/lib/xorg/Xorg (SendErrorToClient+0x365) 
[0x56450c9c94a5]
  [  3431.874] (EE) 11: /usr/lib/xorg/Xorg (InitFonts+0x3c4) [0x56450c9cd524]
  [  3431.876] (EE) 12: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_init_first+0x90) [0x7fdab48c1d90]
  [  3431.878] (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0x80) [0x7fdab48c1e40]
  [  3431.878] (EE) 14: /usr/lib/xorg/Xorg (_start+0x25) [0x56450c9b65f5]
  [  3431.878] (EE)
  [  3431.878] (EE) Segmentation fault at address 0x0
  [  3431.878] (EE)
  Fatal server error:
  [  3431.879] (EE) Caught signal 11 (Segmentation fault). Server aborting
  [  3431.879] (EE)
  [  3431.879] (EE)
  Please consult the The X.Org Foundation support
   at http://wiki.x.org
   for help.
  [  3431.879] (EE) Please also check the log file at "/var/log/Xorg.0.log" for 
additional information.
  [  3431.879] (EE)
  [  3431.880] (EE) Server terminated with error (1). Closing log file.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-qxl/+bug/1980889/+subscriptions


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

[Desktop-packages] [Bug 1991587] [NEW] Gnome Keyring SSH agent socket is ignored by Sway session

[Michał J . Gajda]

Public bug reported:

1. `apt-get install -y sway` to install an alternative Wayland window manager.
2. Login to `sway` user session.
3. Gnome Keyring will ask for passphrase to unlock SSH keys.
4. Then `gnome-keyring-daemon` stays in the background.
5. However, no shell terminal will see this ssh.

   Attempting to use `ssh` or `git` remote will ask for the same
passphrase again.

Workaround:

Add `export SSH_AUTH_SOCK=/run/user/${UID}/keyring/ssh` to `.bashrc`.
Then it works.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-keyring 40.0-3ubuntu3
ProcVersionSignature: Ubuntu 5.15.0-48.54-lowlatency 5.15.53
Uname: Linux 5.15.0-48-lowlatency x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: pass
Date: Tue Oct  4 00:09:03 2022
InstallationDate: Installed on 2022-09-05 (28 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
SourcePackage: gnome-keyring
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  Gnome Keyring SSH agent socket is ignored by Sway session

Status in gnome-keyring package in Ubuntu:
  New

Bug description:
  1. `apt-get install -y sway` to install an alternative Wayland window manager.
  2. Login to `sway` user session.
  3. Gnome Keyring will ask for passphrase to unlock SSH keys.
  4. Then `gnome-keyring-daemon` stays in the background.
  5. However, no shell terminal will see this ssh.

 Attempting to use `ssh` or `git` remote will ask for the same
  passphrase again.

  Workaround:

  Add `export SSH_AUTH_SOCK=/run/user/${UID}/keyring/ssh` to `.bashrc`.
  Then it works.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-keyring 40.0-3ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-48.54-lowlatency 5.15.53
  Uname: Linux 5.15.0-48-lowlatency x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Tue Oct  4 00:09:03 2022
  InstallationDate: Installed on 2022-09-05 (28 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  SourcePackage: gnome-keyring
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1980889] Re: X crashes with qxl(0): error doing QXL_ALLOC

[Launchpad Bug Tracker]

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

** Changed in: xserver-xorg-video-qxl (Ubuntu)
   Status: New => Confirmed

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

Title:
  X crashes with qxl(0): error doing QXL_ALLOC

Status in xserver-xorg-video-qxl package in Ubuntu:
  Confirmed

Bug description:
  Have Lubuntu 22.04 installed in a virtual machine created with virt-
  manager. The X server will randomly crash with only Firefox and
  Thunderbird running, with one or the other minimized.

  Old bug reports found online suggested increasing the "vram" setting
  to 256 MiB (262144 in the XML file) fixed this problem, however at
  that setting, it crashed and this latest crash is when the "vram" was
  set to 512 MiB (524288 in the XML file).

  Below is the text from the Xorg.0.log.old file from the point of the
  crash. The crash of the X server terminated this particular log.

  [54.773] (II) event4  - spice vdagent tablet: device is a pointer
  [  3431.844] (EE) qxl(0): error doing QXL_ALLOC
  [  3431.844] (EE)
  [  3431.844] (EE) Backtrace:
  [  3431.861] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x56450cb3f2b9]
  [  3431.863] (EE) 1: /lib/x86_64-linux-gnu/libc.so.6 (__sigaction+0x50) 
[0x7fdab48da520]
  [  3431.864] (EE) unw_get_proc_name failed: no unwind info found [-10]
  [  3431.864] (EE) 2: /usr/lib/xorg/modules/drivers/qxl_drv.so (?+0x0) 
[0x7fdab413fb2d]
  [  3431.865] (EE) unw_get_proc_name failed: no unwind info found [-10]
  [  3431.865] (EE) 3: /usr/lib/xorg/modules/drivers/qxl_drv.so (?+0x0) 
[0x7fdab413ffc7]
  [  3431.866] (EE) unw_get_proc_name failed: no unwind info found [-10]
  [  3431.867] (EE) 4: /usr/lib/xorg/modules/drivers/qxl_drv.so (?+0x0) 
[0x7fdab414c7c0]
  [  3431.869] (EE) 5: /usr/lib/xorg/Xorg (miCopyRegion+0x9b) [0x56450cb1c59b]
  [  3431.870] (EE) 6: /usr/lib/xorg/Xorg (miDoCopy+0x456) [0x56450cb1ccf6]
  [  3431.872] (EE) unw_get_proc_name failed: no unwind info found [-10]
  [  3431.872] (EE) 7: /usr/lib/xorg/modules/drivers/qxl_drv.so (?+0x0) 
[0x7fdab414ca02]
  [  3431.873] (EE) 8: /usr/lib/xorg/Xorg (DamageRegionAppend+0x3886) 
[0x56450caafa86]
  [  3431.873] (EE) 9: /usr/lib/xorg/Xorg (SendGraphicsExpose+0x2cd) 
[0x56450c9c4efd]
  [  3431.874] (EE) 10: /usr/lib/xorg/Xorg (SendErrorToClient+0x365) 
[0x56450c9c94a5]
  [  3431.874] (EE) 11: /usr/lib/xorg/Xorg (InitFonts+0x3c4) [0x56450c9cd524]
  [  3431.876] (EE) 12: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_init_first+0x90) [0x7fdab48c1d90]
  [  3431.878] (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0x80) [0x7fdab48c1e40]
  [  3431.878] (EE) 14: /usr/lib/xorg/Xorg (_start+0x25) [0x56450c9b65f5]
  [  3431.878] (EE)
  [  3431.878] (EE) Segmentation fault at address 0x0
  [  3431.878] (EE)
  Fatal server error:
  [  3431.879] (EE) Caught signal 11 (Segmentation fault). Server aborting
  [  3431.879] (EE)
  [  3431.879] (EE)
  Please consult the The X.Org Foundation support
   at http://wiki.x.org
   for help.
  [  3431.879] (EE) Please also check the log file at "/var/log/Xorg.0.log" for 
additional information.
  [  3431.879] (EE)
  [  3431.880] (EE) Server terminated with error (1). Closing log file.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-qxl/+bug/1980889/+subscriptions


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

[Desktop-packages] [Bug 1991581] [NEW] Gnome restarts along with all apps when waking from sleep

[Omer Trajman]

Public bug reported:

Using frame.work gen 12 i7 1260p after recent update gnome restarts
after waking from sleep (or perhaps when sleeping, hard to tell). All
gui apps are killed.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42.4-0ubuntu0.22.04.1
ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
Uname: Linux 5.15.0-48-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: GNOME
Date: Mon Oct  3 15:31:13 2022
DisplayManager: gdm3
InstallationDate: Installed on 2022-09-13 (20 days ago)
InstallationMedia: Ubuntu Web
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: mutter-common 42.2-0ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to jammy on 2022-09-13 (20 days ago)

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


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

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

Title:
  Gnome restarts along with all apps when waking from sleep

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Using frame.work gen 12 i7 1260p after recent update gnome restarts
  after waking from sleep (or perhaps when sleeping, hard to tell). All
  gui apps are killed.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.4-0ubuntu0.22.04.1
  ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
  Uname: Linux 5.15.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  Date: Mon Oct  3 15:31:13 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-09-13 (20 days ago)
  InstallationMedia: Ubuntu Web
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 42.2-0ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to jammy on 2022-09-13 (20 days ago)

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


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

[Desktop-packages] [Bug 1991578] [NEW] iwd does not reconnect after resume

[Julian Andres Klode]

Public bug reported:

[this is a regression from wpa_supplicant AFAICT, rebooting with
wpa_supplicant instead to reconfirm]

After a resume, iwd does not reconnect to the AP (Unifi WiFi 6 Lite). It
tries three times to resume an existing session but that one expired
already:


Okt 03 21:01:19 jak-t480s systemd[1]: systemd-suspend.service: Deactivated 
successfully.
Okt 03 21:01:19 jak-t480s NetworkManager[1909]:   [1664823679.1340] 
manager: sleep: wake requested (sleeping: yes  enabled: yes)
Okt 03 21:01:19 jak-t480s NetworkManager[1909]:   [1664823679.1341] 
device (enp0s31f6): state change: unavailable -> unmanaged (reason 'sleeping', 
sys-iface-state: 'managed')
Okt 03 21:01:19 jak-t480s NetworkManager[1909]:   [1664823679.2148] 
device (enp0s31f6): state change: unmanaged -> unavailable (reason 'managed', 
sys-iface-state: 'external')
Okt 03 21:01:19 jak-t480s NetworkManager[1909]:   [1664823679.4079] 
device (/net/connman/iwd/0): state change: unmanaged -> unavailable (reason 
'managed', sys-iface-state: 'external')
Okt 03 21:01:19 jak-t480s NetworkManager[1909]:   [1664823679.4082] 
device (wlan0): state change: unmanaged -> unavailable (reason 'managed', 
sys-iface-state: 'external')
Okt 03 21:01:19 jak-t480s NetworkManager[1909]:   [1664823679.4126] 
manager: NetworkManager state is now CONNECTED_LOCAL
Okt 03 21:01:19 jak-t480s audit[1822]: USER_AVC pid=1822 uid=103 
auid=4294967295 ses=4294967295 subj=? msg='apparmor="DENIED" 
operation="dbus_signal"  bus="system" path="/org/freedesktop/NetworkManager" 
interface="org.freedesktop.Ne
tworkManager" member="StateChanged" name=":1.9" mask="receive" pid=2294563 
label="snap.spotify.spotify" peer_pid=1909 peer_label="unconfined"
Okt 03 21:01:19 jak-t480s iwd[2215]: Could not register frame watch type 00d0: 
-114   
Okt 03 21:01:19 jak-t480s NetworkManager[1909]:   [1664823679.4171] 
device (/net/connman/iwd/0): state change: unavailable -> disconnected (reason 
'none', sys-iface-state: 'managed')
Okt 03 21:01:19 jak-t480s NetworkManager[1909]:   [1664823679.4176] 
device (wlan0): new IWD device state is disconnected
Okt 03 21:01:19 jak-t480s NetworkManager[1909]:   [1664823679.4177] 
device (wlan0): state change: unavailable -> disconnected (reason 
'supplicant-available', sys-iface-state: 'managed')
Okt 03 21:01:19 jak-t480s kernel: audit: type=1107 audit(1664823679.412:462): 
pid=1822 uid=103 auid=4294967295 ses=4294967295 subj=? msg='apparmor="DENIED" 
operation="dbus_signal"  bus="system" path="/org/freedesktop/NetworkManager"
 interface="org.freedesktop.NetworkManager" member="StateChanged" name=":1.9" 
mask="receive" pid=2294563 label="snap.spotify.spotify" peer_pid=1909 
peer_label="unconfined"
Okt 03 21:01:20 jak-t480s kernel: wlan0: authenticate with 7a:45:58:16:2b:36


Okt 03 21:01:20 jak-t480s kernel: wlan0: send auth to 7a:45:58:16:2b:36 (try 
1/3)
   
Okt 03 21:01:20 jak-t480s NetworkManager[1909]:   [1664823680.1593] 
device (wlan0): new IWD device state is connecting
Okt 03 21:01:20 jak-t480s NetworkManager[1909]:   [1664823680.1598] 
device (wlan0): Activation: starting connection 'JNet' 
(86a68c67-8004-4c7f-8eed-c2a5aa857c50)
Okt 03 21:01:20 jak-t480s NetworkManager[1909]:   [1664823680.1599] 
device (wlan0): state change: disconnected -> prepare (reason 'none', 
sys-iface-state: 'managed')
Okt 03 21:01:20 jak-t480s NetworkManager[1909]:   [1664823680.1601] 
manager: NetworkManager state is now CONNECTING 
  
Okt 03 21:01:20 jak-t480s NetworkManager[1909]:   [1664823680.1603] 
device (wlan0): state change: prepare -> config (reason 'none', 
sys-iface-state: 'managed')
Okt 03 21:01:20 jak-t480s audit[1822]: USER_AVC pid=1822 uid=103 
auid=4294967295 ses=4294967295 subj=? msg='apparmor="DENIED" 
operation="dbus_signal"  bus="system" path="/org/freedesktop/NetworkManager" 
interface="org.freedesktop.Ne
tworkManager" member="StateChanged" name=":1.9" mask="receive" pid=2294563 
label="snap.spotify.spotify" peer_pid=1909 peer_label="unconfined"  

Okt 03 21:01:20 jak-t480s kernel: audit: type=1107 audit(1664823680.156:464): 
pid=1822 uid=103 auid=4294967295 ses=4294967295 subj=? msg='apparmor="DENIED" 
operation="dbus_signal"  bus="system" path="/org/freedesktop/NetworkManager"
 interface="org.freedesktop.NetworkManager" member="StateChanged" name=":1.9" 
mask="receive" pid=2294563 label="snap.spotify.spotify" peer_pid=1909 
peer_label="unconfined"
Okt 03 21:01:21 jak-t480s kernel: wlan0: send auth to 7a:45:58:16:2b:36 (try 
2/3) 

[Desktop-packages] [Bug 1970917] Re: gnome-shell crashes with SIGABRT due to assertion failure "!window->monitor || g_list_find (meta_monitor_manager_get_logical_monitors (monitor_manager), window->mo

[ThatFatPat]

Hi, I recently implemented an additional mode in gnome-remote-desktop
which disables the physical monitors and creates a virtual monitor, so
that no matter your host configuration, the client can view all windows
and in the appropriate resolution.

This bug prevents me from using this mode as approximately 20% of the
times a new RDP connection is initiated, gnome-shell crashes thus
destroying the user session.

I would be really glad to see this fixed, especially as a fix was
already released. Running my own tests, it seems that cherry-picking the
patch onto the current version of mutter passes all tests.

Is there anything I can do to expedite the process?

Thanks in advance!

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

Title:
  gnome-shell crashes with SIGABRT due to assertion failure
  "!window->monitor || g_list_find
  (meta_monitor_manager_get_logical_monitors (monitor_manager),
  window->monitor)" in meta_window_update_for_monitors_changed()

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

Bug description:
  gnome-shell crashes with SIGABRT due to assertion failure:

  "!window->monitor || g_list_find
  (meta_monitor_manager_get_logical_monitors (monitor_manager),
  window->monitor)"

  in meta_window_update_for_monitors_changed().

  However a bug in errors.ubuntu.com is hiding it. Sometimes it is
  visible on
  https://errors.ubuntu.com/problem/bc718fcc290d04f4e23c6246836d992f140e7058
  (when the last crash report was from jammy) and sometimes not
  (impish).

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


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

[Desktop-packages] [Bug 1990783] Re: distorted mouse pointer under Wayland in Kinetic

[Gannet]

** Attachment added: "syslog"
   
https://bugs.launchpad.net/ubuntu/+source/kwin/+bug/1990783/+attachment/5620782/+files/syslog

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

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

Title:
  distorted mouse pointer under Wayland in Kinetic

Status in kwin package in Ubuntu:
  New
Status in wayland package in Ubuntu:
  New

Bug description:
  After upgrading to Kubuntu 22.10 Kinetic dev. I found mouse pointer
  distorted. Please, look at attached screenshot. Under X session mouse
  pointer looks as it should be.

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


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

[Desktop-packages] [Bug 1988786] Re: system does not boot after full-upgrade on kinetic

[Launchpad Bug Tracker]

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

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

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

Title:
  system does not boot after full-upgrade on kinetic

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-session package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  After a full upgrade on a kinetic system, the system no longer boots
  normally.

  When I power the computer on, I get a prompt to decrypt my disk. I
  insert the password, and am redirected to a screen saying a fschk is
  running. It spend hours in that screen with apparently no activity.
  Pressing ctrl+C does not help at that point.

  Booting through recovery mode and then requesting to proceed to boot
  works fine. A regular fschk also suceeds.

  Here is what I could extract from my journal:

  Sep 05 16:10:57 castor gnome-session[2000]: gnome-session-binary[2000]: 
WARNING: Application 'org.gnome.Shell.desktop' failed to register before timeout
  Sep 05 16:10:57 castor gnome-session-binary[2000]: WARNING: Application 
'org.gnome.Shell.desktop' failed to register before timeout
  Sep 05 16:10:57 castor gnome-session-binary[2000]: Unrecoverable failure in 
required component org.gnome.Shell.desktop
  Sep 05 16:10:57 castor /usr/libexec/gdm-wayland-session[1986]: 
dbus-daemon[1986]: [session uid=127 pid=1986] Activating service 
name='ca.desrt.dconf' requested by ':1.2' (uid=127 pid=2000 
comm="/usr/libexec/gnome-session-binary --autostart /usr" label="unconfined")
  Sep 05 16:10:57 castor /usr/libexec/gdm-wayland-session[1986]: 
dbus-daemon[1986]: [session uid=127 pid=1986] Successfully activated service 
'ca.desrt.dconf'
  Sep 05 16:10:57 castor dbus-daemon[1221]: [system] Activating via systemd: 
service name='org.freedesktop.hostname1' 
unit='dbus-org.freedesktop.hostname1.service' requested by ':1.54' (uid=127 
pid=3239 comm="/usr/libexec/gsd-rfkill" label="unconfined")
  Sep 05 16:10:57 castor /usr/libexec/gdm-wayland-session[1986]: 
dbus-daemon[1986]: [session uid=127 pid=1986] Activating service 
name='org.freedesktop.systemd1' requested by ':1.7' (uid=127 pid=3227 
comm="/usr/libexec/gsd-sharing" label="unconfined")
  Sep 05 16:10:57 castor /usr/libexec/gdm-wayland-session[1986]: 
dbus-daemon[1986]: [session uid=127 pid=1986] Activated service 
'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with 
status 1
  Sep 05 16:10:57 castor gsd-sharing[3227]: Failed to StopUnit service: 
GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process 
org.freedesktop.systemd1 exited with status 1
  Sep 05 16:10:57 castor gsd-sharing[3227]: Failed to StopUnit service: 
GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process 
org.freedesktop.systemd1 exited with status 1
  Sep 05 16:10:57 castor systemd[1]: Starting Hostname Service...
  Sep 05 16:10:57 castor dbus-daemon[1221]: [system] Successfully activated 
service 'org.freedesktop.hostname1'
  Sep 05 16:10:57 castor systemd[1]: Started Hostname Service.
  Sep 05 16:10:57 castor kernel: rfkill: input handler disabled
  Sep 05 16:11:27 castor systemd[1]: systemd-hostnamed.service: Deactivated 
successfully.
  Sep 05 16:12:27 castor gnome-session-binary[2000]: WARNING: Application 
'org.gnome.SettingsDaemon.Power.desktop' failed to register before timeout
  Sep 05 16:12:27 castor gnome-session[2000]: gnome-session-binary[2000]: 
WARNING: Application 'org.gnome.SettingsDaemon.Power.desktop' failed to 
register before timeout
  Sep 05 16:12:27 castor gnome-session[2000]: gnome-session-binary[2000]: 
WARNING: Application 'org.gnome.SettingsDaemon.MediaKeys.desktop' failed to 
register before timeout
  Sep 05 16:12:27 castor gnome-session[2000]: gnome-session-binary[2000]: 
WARNING: Application 'org.gnome.SettingsDaemon.Keyboard.desktop' failed to 
register before timeout
  Sep 05 16:12:27 castor gnome-session[2000]: gnome-session-binary[2000]: 
WARNING: Application 'org.gnome.SettingsDaemon.Color.desktop' failed to 
register before timeout
  Sep 05 16:12:27 castor gnome-session[2000]: gnome-session-binary[2000]: 
WARNING: Application 'org.gnome.SettingsDaemon.Wacom.desktop' failed to 
register before timeout
  Sep 05 16:12:27 castor gnome-session-binary[2000]: Unrecoverable failure in 
required component org.gnome.SettingsDaemon.Power.desktop
  Sep 05 16:12:27 castor gnome-session-binary[2000]: WARNING: Application 
'org.gnome.SettingsDaemon.MediaKeys.desktop' failed to register before timeout
  Sep 05 16:12:27 castor gnome-session-binary[2000]: Unrecoverable failure in 
required component org.gnome.SettingsDaemon.MediaKeys.desktop
  Sep 05 16:12:27 castor gnome-session-binary[2000]: WARNING: Application 
'org.gnome.SettingsDaemon.Keyboard.desktop' failed to register before timeout
  Sep 05 16:12:27 castor gnome-session-b

[Desktop-packages] [Bug 1988786] Re: system does not boot after full-upgrade on kinetic

[Launchpad Bug Tracker]

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

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

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

Title:
  system does not boot after full-upgrade on kinetic

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-session package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  After a full upgrade on a kinetic system, the system no longer boots
  normally.

  When I power the computer on, I get a prompt to decrypt my disk. I
  insert the password, and am redirected to a screen saying a fschk is
  running. It spend hours in that screen with apparently no activity.
  Pressing ctrl+C does not help at that point.

  Booting through recovery mode and then requesting to proceed to boot
  works fine. A regular fschk also suceeds.

  Here is what I could extract from my journal:

  Sep 05 16:10:57 castor gnome-session[2000]: gnome-session-binary[2000]: 
WARNING: Application 'org.gnome.Shell.desktop' failed to register before timeout
  Sep 05 16:10:57 castor gnome-session-binary[2000]: WARNING: Application 
'org.gnome.Shell.desktop' failed to register before timeout
  Sep 05 16:10:57 castor gnome-session-binary[2000]: Unrecoverable failure in 
required component org.gnome.Shell.desktop
  Sep 05 16:10:57 castor /usr/libexec/gdm-wayland-session[1986]: 
dbus-daemon[1986]: [session uid=127 pid=1986] Activating service 
name='ca.desrt.dconf' requested by ':1.2' (uid=127 pid=2000 
comm="/usr/libexec/gnome-session-binary --autostart /usr" label="unconfined")
  Sep 05 16:10:57 castor /usr/libexec/gdm-wayland-session[1986]: 
dbus-daemon[1986]: [session uid=127 pid=1986] Successfully activated service 
'ca.desrt.dconf'
  Sep 05 16:10:57 castor dbus-daemon[1221]: [system] Activating via systemd: 
service name='org.freedesktop.hostname1' 
unit='dbus-org.freedesktop.hostname1.service' requested by ':1.54' (uid=127 
pid=3239 comm="/usr/libexec/gsd-rfkill" label="unconfined")
  Sep 05 16:10:57 castor /usr/libexec/gdm-wayland-session[1986]: 
dbus-daemon[1986]: [session uid=127 pid=1986] Activating service 
name='org.freedesktop.systemd1' requested by ':1.7' (uid=127 pid=3227 
comm="/usr/libexec/gsd-sharing" label="unconfined")
  Sep 05 16:10:57 castor /usr/libexec/gdm-wayland-session[1986]: 
dbus-daemon[1986]: [session uid=127 pid=1986] Activated service 
'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with 
status 1
  Sep 05 16:10:57 castor gsd-sharing[3227]: Failed to StopUnit service: 
GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process 
org.freedesktop.systemd1 exited with status 1
  Sep 05 16:10:57 castor gsd-sharing[3227]: Failed to StopUnit service: 
GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process 
org.freedesktop.systemd1 exited with status 1
  Sep 05 16:10:57 castor systemd[1]: Starting Hostname Service...
  Sep 05 16:10:57 castor dbus-daemon[1221]: [system] Successfully activated 
service 'org.freedesktop.hostname1'
  Sep 05 16:10:57 castor systemd[1]: Started Hostname Service.
  Sep 05 16:10:57 castor kernel: rfkill: input handler disabled
  Sep 05 16:11:27 castor systemd[1]: systemd-hostnamed.service: Deactivated 
successfully.
  Sep 05 16:12:27 castor gnome-session-binary[2000]: WARNING: Application 
'org.gnome.SettingsDaemon.Power.desktop' failed to register before timeout
  Sep 05 16:12:27 castor gnome-session[2000]: gnome-session-binary[2000]: 
WARNING: Application 'org.gnome.SettingsDaemon.Power.desktop' failed to 
register before timeout
  Sep 05 16:12:27 castor gnome-session[2000]: gnome-session-binary[2000]: 
WARNING: Application 'org.gnome.SettingsDaemon.MediaKeys.desktop' failed to 
register before timeout
  Sep 05 16:12:27 castor gnome-session[2000]: gnome-session-binary[2000]: 
WARNING: Application 'org.gnome.SettingsDaemon.Keyboard.desktop' failed to 
register before timeout
  Sep 05 16:12:27 castor gnome-session[2000]: gnome-session-binary[2000]: 
WARNING: Application 'org.gnome.SettingsDaemon.Color.desktop' failed to 
register before timeout
  Sep 05 16:12:27 castor gnome-session[2000]: gnome-session-binary[2000]: 
WARNING: Application 'org.gnome.SettingsDaemon.Wacom.desktop' failed to 
register before timeout
  Sep 05 16:12:27 castor gnome-session-binary[2000]: Unrecoverable failure in 
required component org.gnome.SettingsDaemon.Power.desktop
  Sep 05 16:12:27 castor gnome-session-binary[2000]: WARNING: Application 
'org.gnome.SettingsDaemon.MediaKeys.desktop' failed to register before timeout
  Sep 05 16:12:27 castor gnome-session-binary[2000]: Unrecoverable failure in 
required component org.gnome.SettingsDaemon.MediaKeys.desktop
  Sep 05 16:12:27 castor gnome-session-binary[2000]: WARNING: Application 
'org.gnome.SettingsDaemon.Keyboard.desktop' failed to register before timeout
  Sep 05 16:12:27 castor gnome-session-binary[200

Re: [Desktop-packages] [Bug 1991563] [NEW] download.default_directory inside /tmp/snap.chromium

[Nathan Teodosio]

Sorry, this is by design[1][2]:

 > snaps aren’t allowed to share content in directories like /tmp, 
/run/shm or /var/tmp. This is one reason why we use a mount namespace to 
the snap has a snap-specific /tmp directory

[1]: 
https://forum.snapcraft.io/t/tizonia-snap-apparmor-denied-suggestion-adjust-program-to-use-tmpdir-or-tmp/4951/2
[2]: https://forum.snapcraft.io/t/accessing-tmp-from-snaps/22384

** Changed in: chromium-browser (Ubuntu)
   Status: New => Won't Fix

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

Title:
  download.default_directory inside /tmp/snap.chromium

Status in chromium-browser package in Ubuntu:
  Won't Fix

Bug description:
  While using a selenium test, I found out the download files are not
  inside the download.default_directory the test is setting, but
  prefixed by /tmp/snap.chromium/

  Python example:

  options = Options()
  prefs = { "download.default_directory": "/tmp" }
  options.add_experimental_option("prefs", prefs)
  browser = webdriver.Chrome(options=options)

  # click on a button that download a file.

  This file would be in /tmp/snap.chromium/tmp instead of just /tmp/

  I'm on Ubuntu 22.04.1 LTS and I use Chromium 105.0.5195.125 (Official
  Build) snap (64-bit)

  Any idea how to relocate where the files are saved during a selenium
  test to be outside of /tmp/snap.chromium directory (which belongs to
  root user)?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1991563/+subscriptions


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

[Desktop-packages] [Bug 1970148] Re: Brave & Chrome browsers freezes on download and print to pdf

[Vu Quoc Huy]

I can confirm #37, thanks

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

Title:
  Brave & Chrome browsers freezes on download and print to pdf

Status in chromium-browser package in Ubuntu:
  Invalid

Bug description:
  Whenever any file is downloaded, the browser will freeze. Download
  files, from any page does not work. Same issue with Firefox.

  Similarly, the browser will freeze when a page is printed to pdf.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1970148/+subscriptions


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

[Desktop-packages] [Bug 1793295] Re: nautilus-share

[Jeremy Bicha]

There isn't enough information here to further process this bug. And
it's a 4-year old bug so maybe whatever issue was here has been resolved
already. Feel free to open a new bug if you experience this issue or
another issue.

** Changed in: nautilus-share (Ubuntu)
   Status: New => Invalid

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

Title:
  nautilus-share

Status in nautilus-share package in Ubuntu:
  Invalid

Bug description:
  Impossibile installare «nautilus-share»

  L'avanzamento procederà, ma il pacchetto «nautilus-share» potrebbe non
  essere in uno stato funzionante. Segnalare questo evento come bug.

  dependency problems - leaving unconfigured

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus-share/+bug/1793295/+subscriptions


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

[Desktop-packages] [Bug 1990841] Re: Local network share option disappeared

[Jeremy Bicha]

I'm marking as fixed since nautilus-share will be available for install
later today on Ubuntu 22.10.

** Changed in: nautilus-share (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  Local network share option disappeared

Status in nautilus-share package in Ubuntu:
  Fix Released

Bug description:
  On Ubuntu 22.10 nautilus: 1:43.0-1ubuntu1
  right click on a folder: the option 'Local network share' no longer appears

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: nautilus 1:43.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 26 13:57:35 2022
  GsettingsChanges: b'org.gnome.nautilus.window-state' b'initial-size' b'(1545, 
823)'
  InstallationDate: Installed on 2022-09-08 (18 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220908)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:
   file-roller   43.0-1
   nautilus-extension-gnome-terminal 3.46.1-2ubuntu1
   python3-nautilus  4.0-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus-share/+bug/1990841/+subscriptions


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

[Desktop-packages] [Bug 1991563] [NEW] download.default_directory inside /tmp/snap.chromium

[Guendalf]

Public bug reported:

While using a selenium test, I found out the download files are not
inside the download.default_directory the test is setting, but prefixed
by /tmp/snap.chromium/

Python example:

options = Options()
prefs = { "download.default_directory": "/tmp" }
options.add_experimental_option("prefs", prefs)
browser = webdriver.Chrome(options=options)

# click on a button that download a file.

This file would be in /tmp/snap.chromium/tmp instead of just /tmp/

I'm on Ubuntu 22.04.1 LTS and I use Chromium 105.0.5195.125 (Official
Build) snap (64-bit)

Any idea how to relocate where the files are saved during a selenium
test to be outside of /tmp/snap.chromium directory (which belongs to
root user)?

** Affects: chromium-browser (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  download.default_directory inside /tmp/snap.chromium

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  While using a selenium test, I found out the download files are not
  inside the download.default_directory the test is setting, but
  prefixed by /tmp/snap.chromium/

  Python example:

  options = Options()
  prefs = { "download.default_directory": "/tmp" }
  options.add_experimental_option("prefs", prefs)
  browser = webdriver.Chrome(options=options)

  # click on a button that download a file.

  This file would be in /tmp/snap.chromium/tmp instead of just /tmp/

  I'm on Ubuntu 22.04.1 LTS and I use Chromium 105.0.5195.125 (Official
  Build) snap (64-bit)

  Any idea how to relocate where the files are saved during a selenium
  test to be outside of /tmp/snap.chromium directory (which belongs to
  root user)?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1991563/+subscriptions


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

[Desktop-packages] [Bug 1900167] Re: gnome-software Unable to install updates

[Nathan Teodosio]

I kept clicking the button and at some point it turned into Download,
not sure if as a result of insisting or of a completed snap-store update
that I had to do manually with

  snap-store --quit
  snap refresh snap-store

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

Title:
  gnome-software Unable to install updates

Status in gnome-software package in Ubuntu:
  Expired

Bug description:
  Click on 'Updates' and then on 'Restart & Update' I have a message:
  Unable to install updates: GDBus.error... Prepared update not 
found:/var/lib/PackageKit/prepared-update

  corrado@corrado-x2-gg-1009:~$ apt policy gnome-software
  gnome-software:
Installed: 3.38.0-2build1
Candidate: 3.38.0-2build1
Version table:
   *** 3.38.0-2build1 500
  500 http://archive.ubuntu.com/ubuntu groovy/universe amd64 Packages
  100 /var/lib/dpkg/status
  corrado@corrado-x2-gg-1009:~$ inxi -Fx
  System:
Host: corrado-x2-gg-1009 Kernel: 5.8.0-23-generic x86_64 bits: 64 
compiler: gcc v: 10.2.0 Desktop: N/A Distro: Ubuntu 20.10 (Groovy Gorilla) 
  Machine:
Type: Desktop Mobo: ASRock model: H110M-G/M.2 
serial:  UEFI: American Megatrends v: P1.10 
date: 05/11/2017 
  CPU:
Info: Dual Core model: Intel Core i3-7100 bits: 64 type: MT MCP 
arch: Kaby Lake rev: 9 L2 cache: 3072 KiB 
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
bogomips: 31199 
Speed: 800 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 800 2: 800 
3: 800 4: 800 
  Graphics:
Device-1: Intel HD Graphics 630 vendor: ASRock driver: i915 v: kernel 
bus ID: 00:02.0 
Display: x11 server: X.Org 1.20.8 driver: modesetting unloaded: fbdev,vesa 
resolution: 1920x1080~60Hz 
OpenGL: renderer: Mesa Intel HD Graphics 630 (KBL GT2) v: 4.6 Mesa 20.2.0 
direct render: Yes 
  Audio:
Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: ASRock 
driver: snd_hda_intel v: kernel bus ID: 00:1f.3 
Device-2: Logitech QuickCam Pro 9000 type: USB 
driver: snd-usb-audio,uvcvideo bus ID: 1-8:4 
Sound Server: ALSA v: k5.8.0-23-generic 
  Network:
Device-1: Intel Ethernet I219-V vendor: ASRock driver: e1000e v: 3.2.6-k 
port: f040 bus ID: 00:1f.6 
IF: enp0s31f6 state: up speed: 100 Mbps duplex: full 
mac: 70:85:c2:44:7b:86 
  Drives:
Local Storage: total: 2.05 TiB used: 9.42 GiB (0.4%) 
ID-1: /dev/nvme0n1 vendor: Kingston model: SKC2000M8250G size: 232.89 GiB 
ID-2: /dev/sda vendor: Toshiba model: DT01ACA100 size: 931.51 GiB 
ID-3: /dev/sdb vendor: Hitachi model: HDS721010CLA332 size: 931.51 GiB 
  Partition:
ID-1: / size: 31.25 GiB used: 9.41 GiB (30.1%) fs: ext4 
dev: /dev/nvme0n1p2 
  Swap:
ID-1: swap-1 type: partition size: 8.00 GiB used: 0 KiB (0.0%) 
dev: /dev/sda2 
  Sensors:
System Temperatures: cpu: 43.5 C mobo: N/A 
Fan Speeds (RPM): N/A 
  Info:
Processes: 224 Uptime: 3h 13m Memory: 7.48 GiB used: 1.66 GiB (22.2%) 
Init: systemd runlevel: 5 Compilers: gcc: N/A Packages: 1874 Shell: Bash 
v: 5.0.17 inxi: 3.1.07 
  corrado@corrado-x2-gg-1009:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-software 3.38.0-2build1
  ProcVersionSignature: Ubuntu 5.8.0-23.24-generic 5.8.14
  Uname: Linux 5.8.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 16 18:20:00 2020
  InstallationDate: Installed on 2020-10-10 (6 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201009.1)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-snap3.38.0-2build1
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1980839] Re: thunderbird -compose returns error since the 102 snap update?

[Petar Andrejic]

OK went through and added any thunderbird apparmor denials that were
occurring into
/var/lib/snapd/apparmor/profiles/snap.thunderbird.thunderbird, as well
doing similar for a seccomp violation that was showing up. Still no
luck, same bug. Only thing in journalctl when I try thunderbird
--compose is:

Oct 03 17:23:44 Kronos systemd[5565]: Started
snap.thunderbird.thunderbird.300ee151-4b07-40c9-a74a-5ee783e71cfa.scope

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

Title:
  thunderbird -compose returns error since the 102 snap update?

Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  After updating to the latest thunderbird 102.0.1 snap on Ubuntu 20.04,
  it is no longer possible to open mailto links from the firefox snap in
  thunderbird. When clicking a mailto link in the firefox 102.0.1 snap,
  thunderbird returns the following error message: "Thunderbird is
  already running, but is not responding. To use Thunderbird, you must
  first close the existing Thunderbird process, restart your device, or
  use a different profile." The issue appears related to the thunderbird
  update as there was no issue opening links in the previous 91 version.

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


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

[Desktop-packages] [Bug 1900167] Re: gnome-software Unable to install updates

[Nathan Teodosio]

I confirm this bug on Jammy. The error message in the notification box
is

  Unable to install updates
  Prepared update not found: "/var/lib/PackageKit/prepared-update"

and stderr says

  Snapd snapd_client_refresh_sync: assertion 'name != NULL' failed
  Gs  snap did not set error for gs_plugin_update
  Gs  not GsPlugin error pk-engine-error-quark:1: Prepared update not found: 
/var/lib/PackageKit/prepared-update

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

Title:
  gnome-software Unable to install updates

Status in gnome-software package in Ubuntu:
  Expired

Bug description:
  Click on 'Updates' and then on 'Restart & Update' I have a message:
  Unable to install updates: GDBus.error... Prepared update not 
found:/var/lib/PackageKit/prepared-update

  corrado@corrado-x2-gg-1009:~$ apt policy gnome-software
  gnome-software:
Installed: 3.38.0-2build1
Candidate: 3.38.0-2build1
Version table:
   *** 3.38.0-2build1 500
  500 http://archive.ubuntu.com/ubuntu groovy/universe amd64 Packages
  100 /var/lib/dpkg/status
  corrado@corrado-x2-gg-1009:~$ inxi -Fx
  System:
Host: corrado-x2-gg-1009 Kernel: 5.8.0-23-generic x86_64 bits: 64 
compiler: gcc v: 10.2.0 Desktop: N/A Distro: Ubuntu 20.10 (Groovy Gorilla) 
  Machine:
Type: Desktop Mobo: ASRock model: H110M-G/M.2 
serial:  UEFI: American Megatrends v: P1.10 
date: 05/11/2017 
  CPU:
Info: Dual Core model: Intel Core i3-7100 bits: 64 type: MT MCP 
arch: Kaby Lake rev: 9 L2 cache: 3072 KiB 
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
bogomips: 31199 
Speed: 800 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 800 2: 800 
3: 800 4: 800 
  Graphics:
Device-1: Intel HD Graphics 630 vendor: ASRock driver: i915 v: kernel 
bus ID: 00:02.0 
Display: x11 server: X.Org 1.20.8 driver: modesetting unloaded: fbdev,vesa 
resolution: 1920x1080~60Hz 
OpenGL: renderer: Mesa Intel HD Graphics 630 (KBL GT2) v: 4.6 Mesa 20.2.0 
direct render: Yes 
  Audio:
Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: ASRock 
driver: snd_hda_intel v: kernel bus ID: 00:1f.3 
Device-2: Logitech QuickCam Pro 9000 type: USB 
driver: snd-usb-audio,uvcvideo bus ID: 1-8:4 
Sound Server: ALSA v: k5.8.0-23-generic 
  Network:
Device-1: Intel Ethernet I219-V vendor: ASRock driver: e1000e v: 3.2.6-k 
port: f040 bus ID: 00:1f.6 
IF: enp0s31f6 state: up speed: 100 Mbps duplex: full 
mac: 70:85:c2:44:7b:86 
  Drives:
Local Storage: total: 2.05 TiB used: 9.42 GiB (0.4%) 
ID-1: /dev/nvme0n1 vendor: Kingston model: SKC2000M8250G size: 232.89 GiB 
ID-2: /dev/sda vendor: Toshiba model: DT01ACA100 size: 931.51 GiB 
ID-3: /dev/sdb vendor: Hitachi model: HDS721010CLA332 size: 931.51 GiB 
  Partition:
ID-1: / size: 31.25 GiB used: 9.41 GiB (30.1%) fs: ext4 
dev: /dev/nvme0n1p2 
  Swap:
ID-1: swap-1 type: partition size: 8.00 GiB used: 0 KiB (0.0%) 
dev: /dev/sda2 
  Sensors:
System Temperatures: cpu: 43.5 C mobo: N/A 
Fan Speeds (RPM): N/A 
  Info:
Processes: 224 Uptime: 3h 13m Memory: 7.48 GiB used: 1.66 GiB (22.2%) 
Init: systemd runlevel: 5 Compilers: gcc: N/A Packages: 1874 Shell: Bash 
v: 5.0.17 inxi: 3.1.07 
  corrado@corrado-x2-gg-1009:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-software 3.38.0-2build1
  ProcVersionSignature: Ubuntu 5.8.0-23.24-generic 5.8.14
  Uname: Linux 5.8.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 16 18:20:00 2020
  InstallationDate: Installed on 2020-10-10 (6 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201009.1)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-snap3.38.0-2build1
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1991553] [NEW] can't add a private PPA

[Junien Fridrick]

Public bug reported:

As per today's discussion in ~is :

add-apt-repository has a bug when adding a private PPA. Quoting
~cjwatson :

===
It asks Launchpad for all your personal archive subscriptions _that have 
tokens_.  But `Person:+archivesubscriptions` also shows subscriptions without 
tokens - the token is generated when you click on Viewt here for the first time.

Instead, `add-apt-repository` should call `getArchiveSubscriptionURL` (not 
`getArchiveSubscriptionURLs`) for the archive it's interested in.  That 
generates tokens on-demand.  Either it will get an HTTP 401, or it will get a 
URL which it can parse for the username and password.
===

Thanks !

** Affects: software-properties (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  can't add a private PPA

Status in software-properties package in Ubuntu:
  New

Bug description:
  As per today's discussion in ~is :

  add-apt-repository has a bug when adding a private PPA. Quoting
  ~cjwatson :

  ===
  It asks Launchpad for all your personal archive subscriptions _that have 
tokens_.  But `Person:+archivesubscriptions` also shows subscriptions without 
tokens - the token is generated when you click on Viewt here for the first time.

  Instead, `add-apt-repository` should call `getArchiveSubscriptionURL` (not 
`getArchiveSubscriptionURLs`) for the archive it's interested in.  That 
generates tokens on-demand.  Either it will get an HTTP 401, or it will get a 
URL which it can parse for the username and password.
  ===

  Thanks !

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1991553/+subscriptions


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

[Desktop-packages] Fwd: [Bug 1991530] Re: After upgrading to Ubuntu 22.10-beta I lost the sound.

[jmst]

Another screen print; I don't know if it is useful.


 Forwarded Message 
Subject:Re: [Bug 1991530] Re: After upgrading to Ubuntu 22.10-beta I 
lost the sound.
Date:   Mon, 3 Oct 2022 15:51:33 +0100
From:   Joaquim Torres 
To: Bug 1991530 <1991...@bugs.launchpad.net>


Hello,

The problem remains. I'm trying to use the earphone output of my laptop.



Best regards,

Joaquim Torres


On 03/10/22 15:22, Aaron Rainbolt wrote:
> sudo apt install firmware-sof-signed

** Attachment added: "m921nhar3EQ4jweU.png"
   
https://bugs.launchpad.net/bugs/1991530/+attachment/5620753/+files/m921nhar3EQ4jweU.png

** Attachment added: "rlik00YNECJYXwYl.png"
   
https://bugs.launchpad.net/bugs/1991530/+attachment/5620754/+files/rlik00YNECJYXwYl.png

** Attachment added: "bZqsKXlsvwAr8d06.png"
   
https://bugs.launchpad.net/bugs/1991530/+attachment/5620755/+files/bZqsKXlsvwAr8d06.png

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

Title:
  After upgrading to Ubuntu 22.10-beta I lost the sound.

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  In the list of devices for testing sound I get only "Dummy Output".
  With 22.04 everything was ok.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', 
'/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct  3 14:27:59 2022
  InstallationDate: Installed on 2019-07-01 (1190 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: alsa-driver
  Symptom: audio
  UpgradeStatus: Upgraded to kinetic on 2022-09-30 (2 days ago)
  dmi.bios.date: 07/15/2022
  dmi.bios.release: 1.33
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0YET50W (1.33 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20NB002BPG
  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.ec.firmware.release: 1.23
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0YET50W(1.33):bd07/15/2022:br1.33:efr1.23:svnLENOVO:pn20NB002BPG:pvrThinkPadE590:rvnLENOVO:rn20NB002BPG:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20NB_BU_SMB_FM_ThinkPadE590:
  dmi.product.family: ThinkPad E590
  dmi.product.name: 20NB002BPG
  dmi.product.sku: LENOVO_MT_20NB_BU_SMB_FM_ThinkPad E590
  dmi.product.version: ThinkPad E590
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1991530/+subscriptions


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

Re: [Desktop-packages] [Bug 1991530] Re: After upgrading to Ubuntu 22.10-beta I lost the sound.

[jmst]

Hello,

The problem remains. I'm trying to use the earphone output of my laptop.



Best regards,

Joaquim Torres


On 03/10/22 15:22, Aaron Rainbolt wrote:
> sudo apt install firmware-sof-signed

** Attachment added: "rlik00YNECJYXwYl.png"
   
https://bugs.launchpad.net/bugs/1991530/+attachment/5620751/+files/rlik00YNECJYXwYl.png

** Attachment added: "bZqsKXlsvwAr8d06.png"
   
https://bugs.launchpad.net/bugs/1991530/+attachment/5620752/+files/bZqsKXlsvwAr8d06.png

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

Title:
  After upgrading to Ubuntu 22.10-beta I lost the sound.

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  In the list of devices for testing sound I get only "Dummy Output".
  With 22.04 everything was ok.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', 
'/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct  3 14:27:59 2022
  InstallationDate: Installed on 2019-07-01 (1190 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: alsa-driver
  Symptom: audio
  UpgradeStatus: Upgraded to kinetic on 2022-09-30 (2 days ago)
  dmi.bios.date: 07/15/2022
  dmi.bios.release: 1.33
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0YET50W (1.33 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20NB002BPG
  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.ec.firmware.release: 1.23
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0YET50W(1.33):bd07/15/2022:br1.33:efr1.23:svnLENOVO:pn20NB002BPG:pvrThinkPadE590:rvnLENOVO:rn20NB002BPG:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20NB_BU_SMB_FM_ThinkPadE590:
  dmi.product.family: ThinkPad E590
  dmi.product.name: 20NB002BPG
  dmi.product.sku: LENOVO_MT_20NB_BU_SMB_FM_ThinkPad E590
  dmi.product.version: ThinkPad E590
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1991530/+subscriptions


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

[Desktop-packages] [Bug 1991545] [NEW] Domain groups not accepted as 'AdminIdentities'

[James Paton-Smith]

Public bug reported:

Domain groups cannot be configured as 'AdminIdentities' under
/etc/polkit-1/localauthority.conf.d

EXAMPLE CONFIG

# /etc/polkit-1/localauthority.conf.d/90-test.conf
[Configuration]
AdminIdentities=unix-group:sysapp


With the above config, 'sysapp' is a group in LDAP. SSSD is configured on the 
machine to allow domain users to log in.
Sudo rules have been configured for the 'sysapp' group and work correctly.

However, any action that creates a polkit/GUI prompt for authentication
does not allow users in the 'sysapp' group to authenticate. Instead, it
only accepts auth from the root user.


If I change the config to use a local group, instead of a domain group, 
everything works as expected.
Similarly if I specify a domain USER instead of a domain group, everything 
works as expected.

The problem seems to only be with domain/LDAP groups.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: policykit-1 0.105-33
ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
Uname: Linux 5.15.0-48-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Mon Oct  3 15:20:36 2022
InstallationDate: Installed on 2022-07-15 (80 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
SourcePackage: policykit-1
UpgradeStatus: Upgraded to jammy on 2022-08-02 (61 days ago)

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


** Tags: amd64 apport-bug jammy

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

Title:
  Domain groups not accepted as  'AdminIdentities'

Status in policykit-1 package in Ubuntu:
  New

Bug description:
  Domain groups cannot be configured as 'AdminIdentities' under
  /etc/polkit-1/localauthority.conf.d

  EXAMPLE CONFIG

  # /etc/polkit-1/localauthority.conf.d/90-test.conf
  [Configuration]
  AdminIdentities=unix-group:sysapp

  
  With the above config, 'sysapp' is a group in LDAP. SSSD is configured on the 
machine to allow domain users to log in.
  Sudo rules have been configured for the 'sysapp' group and work correctly.

  However, any action that creates a polkit/GUI prompt for
  authentication does not allow users in the 'sysapp' group to
  authenticate. Instead, it only accepts auth from the root user.

  
  If I change the config to use a local group, instead of a domain group, 
everything works as expected.
  Similarly if I specify a domain USER instead of a domain group, everything 
works as expected.

  The problem seems to only be with domain/LDAP groups.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: policykit-1 0.105-33
  ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
  Uname: Linux 5.15.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Mon Oct  3 15:20:36 2022
  InstallationDate: Installed on 2022-07-15 (80 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  SourcePackage: policykit-1
  UpgradeStatus: Upgraded to jammy on 2022-08-02 (61 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1991545/+subscriptions


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

[Desktop-packages] [Bug 1991530] Re: After upgrading to Ubuntu 22.10-beta I lost the sound.

[Aaron Rainbolt]

Can you try running "sudo apt install firmware-sof-signed" and see if
that resolves the problem?

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

Title:
  After upgrading to Ubuntu 22.10-beta I lost the sound.

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  In the list of devices for testing sound I get only "Dummy Output".
  With 22.04 everything was ok.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', 
'/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct  3 14:27:59 2022
  InstallationDate: Installed on 2019-07-01 (1190 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: alsa-driver
  Symptom: audio
  UpgradeStatus: Upgraded to kinetic on 2022-09-30 (2 days ago)
  dmi.bios.date: 07/15/2022
  dmi.bios.release: 1.33
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0YET50W (1.33 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20NB002BPG
  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.ec.firmware.release: 1.23
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0YET50W(1.33):bd07/15/2022:br1.33:efr1.23:svnLENOVO:pn20NB002BPG:pvrThinkPadE590:rvnLENOVO:rn20NB002BPG:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20NB_BU_SMB_FM_ThinkPadE590:
  dmi.product.family: ThinkPad E590
  dmi.product.name: 20NB002BPG
  dmi.product.sku: LENOVO_MT_20NB_BU_SMB_FM_ThinkPad E590
  dmi.product.version: ThinkPad E590
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1991530/+subscriptions


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

[Desktop-packages] [Bug 1800740] Re: /usr/share/applications/evolution-calendar.desktop Exec program 'evolution -c calendar' has not ben found in th PATH

[Jeremy Bicha]

https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/2479

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

Title:
  /usr/share/applications/evolution-calendar.desktop Exec program
  'evolution -c calendar' has not ben found in th PATH

Status in gnome-shell package in Ubuntu:
  Triaged
Status in menulibre package in Ubuntu:
  Invalid

Bug description:
  Invalid desktop file detected! Please see details
  Parsing Errors
  The following desktop file have failed parsing by the underlying library, and 
will therefore not show up in MenuLibre
  Please investigate these problems with the associated package maintainer

  /usr/share/applications/evolution-calendar.desktop

  Exec program 'evolution -c calendar' has not been found in the PATH

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: menulibre 2.2.0-1
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 30 23:47:18 2018
  InstallationDate: Installed on 2018-10-28 (2 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: menulibre
  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/1800740/+subscriptions


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

[Desktop-packages] [Bug 1800740] Re: /usr/share/applications/evolution-calendar.desktop Exec program 'evolution -c calendar' has not ben found in th PATH

[Jeremy Bicha]

This is a minor issue. The evolution-calendar.desktop is not intended to
be used by anything except as an internal feature for GNOME Shell.

It looks like it will probably be fixed for GNOME Shell 44 (which will
likely be included in Ubuntu 23.04), but it probably is not worth the
effort to backport to earlier Ubuntu releases.

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

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

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

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

Title:
  /usr/share/applications/evolution-calendar.desktop Exec program
  'evolution -c calendar' has not ben found in th PATH

Status in gnome-shell package in Ubuntu:
  Triaged
Status in menulibre package in Ubuntu:
  Invalid

Bug description:
  Invalid desktop file detected! Please see details
  Parsing Errors
  The following desktop file have failed parsing by the underlying library, and 
will therefore not show up in MenuLibre
  Please investigate these problems with the associated package maintainer

  /usr/share/applications/evolution-calendar.desktop

  Exec program 'evolution -c calendar' has not been found in the PATH

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: menulibre 2.2.0-1
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 30 23:47:18 2018
  InstallationDate: Installed on 2018-10-28 (2 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: menulibre
  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/1800740/+subscriptions


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

[Desktop-packages] [Bug 1800740] Re: /usr/share/applications/evolution-calendar.desktop Exec program 'evolution -c calendar' has not ben found in th PATH

[Launchpad Bug Tracker]

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

Title:
  /usr/share/applications/evolution-calendar.desktop Exec program
  'evolution -c calendar' has not ben found in th PATH

Status in gnome-shell package in Ubuntu:
  Triaged
Status in menulibre package in Ubuntu:
  Invalid

Bug description:
  Invalid desktop file detected! Please see details
  Parsing Errors
  The following desktop file have failed parsing by the underlying library, and 
will therefore not show up in MenuLibre
  Please investigate these problems with the associated package maintainer

  /usr/share/applications/evolution-calendar.desktop

  Exec program 'evolution -c calendar' has not been found in the PATH

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: menulibre 2.2.0-1
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 30 23:47:18 2018
  InstallationDate: Installed on 2018-10-28 (2 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: menulibre
  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/1800740/+subscriptions


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

[Desktop-packages] [Bug 1800740] [NEW] /usr/share/applications/evolution-calendar.desktop Exec program 'evolution -c calendar' has not ben found in th PATH

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Invalid desktop file detected! Please see details
Parsing Errors
The following desktop file have failed parsing by the underlying library, and 
will therefore not show up in MenuLibre
Please investigate these problems with the associated package maintainer

/usr/share/applications/evolution-calendar.desktop

Exec program 'evolution -c calendar' has not been found in the PATH

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: menulibre 2.2.0-1
ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
Uname: Linux 4.15.0-38-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct 30 23:47:18 2018
InstallationDate: Installed on 2018-10-28 (2 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
PackageArchitecture: all
SourcePackage: menulibre
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-shell (Ubuntu)
 Importance: Low
 Status: Triaged

** Affects: menulibre (Ubuntu)
 Importance: Undecided
 Status: Invalid


** Tags: amd64 apport-bug bionic
-- 
/usr/share/applications/evolution-calendar.desktop Exec program 'evolution -c 
calendar' has not ben found in th PATH
https://bugs.launchpad.net/bugs/1800740
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 462564]

[Timur-y]

(In reply to Timur from comment #34)
> Here are the results of checking duplicates, they are good except attachment
> 142655 [details] from bug 118111 doesn't have a desired behavior, removing a
> column from 4 column table gives 2 columns instead of 3, like before the
> fix. Please comment if under enhancement, or bug should be reopened. 

Nah, it is good, I don't know how I tested.

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

Title:
  [Upstream] Deleting a column in Writer deletes whole table

Status in LibreOffice:
  Fix Released
Status in OpenOffice:
  Invalid
Status in libreoffice package in Ubuntu:
  Triaged
Status in openoffice.org package in Ubuntu:
  Won't Fix

Bug description:
  Binary package hint: openoffice.org

  1)  lsb_release -rd
  Description:  Ubuntu 11.04
  Release:  11.04

  2) apt-cache policy libreoffice-writer
  libreoffice-writer:
    Installed: 1:3.3.3-1ubuntu2
    Candidate: 1:3.3.3-1ubuntu2
    Version table:
   *** 1:3.3.3-1ubuntu2 0
  500 http://us.archive.ubuntu.com/ubuntu/ natty-updates/main i386 
Packages
  100 /var/lib/dpkg/status
   1:3.3.2-1ubuntu4 0
  500 http://us.archive.ubuntu.com/ubuntu/ natty/main i386 Packages

  3) What is expected to happen in LibreOffice Writer via the Terminal:

  cd ~/Desktop && wget
  
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/462564/+attachment/894856/+files/test.odt
  && lowriter -nologo test.odt

  is when one highlights the second column of the table -> secondary
  clicks -> Column -> Delete is only that column is deleted. Please see
  movie for more details:
  
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/462564/+attachment/894864/+files/out.ogv

  4) What happens instead is the whole table is deleted.

  Reproducible in:
  lsb_release -rd
  Description:  Ubuntu precise (development branch)
  Release:  12.04

  apt-cache policy libreoffice-writer
  libreoffice-writer:
Installed: 1:3.5.2-2ubuntu1
Candidate: 1:3.5.2-2ubuntu1
Version table:
   *** 1:3.5.2-2ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ precise/main i386 Packages
  100 /var/lib/dpkg/status

  WORKAROUND: Split the table then delete the column.

  WORKAROUND: Use Word via WINE.

  Microsoft Office Word 2003 (11.5604.6505)

  apt-cache policy wine1.3
  wine1.3:
    Installed: 1.3.28-0ubuntu1~ppa1~natty1
    Candidate: 1.3.28-0ubuntu1~ppa1~natty1
    Version table:
   *** 1.3.28-0ubuntu1~ppa1~natty1 0
  500 http://ppa.launchpad.net/ubuntu-wine/ppa/ubuntu/ natty/main i386 
Packages
  100 /var/lib/dpkg/status
   1.3.15-0ubuntu5 0
  500 http://us.archive.ubuntu.com/ubuntu/ natty/universe i386 Packages

  ProblemType: Bug
  Architecture: amd64
  Date: Wed Oct 28 09:43:20 2009
  DistroRelease: Ubuntu 9.10
  NonfreeKernelModules: fglrx
  Package: openoffice.org-core 1:3.1.1-5ubuntu1
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
  SourcePackage: openoffice.org
  Uname: Linux 2.6.31-14-generic x86_64

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/462564/+subscriptions


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

[Desktop-packages] [Bug 462564]

[Timur-y]

Thanks Justin for this one, OO reported in 2003!

attachment 182624 is a nice sample, covering more than what was
reported. Not sure that all really should be implemented.

Here are the results of checking duplicates, they are good except
attachment 142655 from bug 118111 doesn't have a desired behavior,
removing a column from 4 column table gives 2 columns instead of 3, like
before the fix. Please comment if under enhancement, or bug should be
reopened.

(attachment 126378 from bug 101091 has an unrelated weird behavior, I'll
comment there)

This is significant, it should go to
https://wiki.documentfoundation.org/ReleaseNotes/7.5.

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

Title:
  [Upstream] Deleting a column in Writer deletes whole table

Status in LibreOffice:
  Fix Released
Status in OpenOffice:
  Invalid
Status in libreoffice package in Ubuntu:
  Triaged
Status in openoffice.org package in Ubuntu:
  Won't Fix

Bug description:
  Binary package hint: openoffice.org

  1)  lsb_release -rd
  Description:  Ubuntu 11.04
  Release:  11.04

  2) apt-cache policy libreoffice-writer
  libreoffice-writer:
    Installed: 1:3.3.3-1ubuntu2
    Candidate: 1:3.3.3-1ubuntu2
    Version table:
   *** 1:3.3.3-1ubuntu2 0
  500 http://us.archive.ubuntu.com/ubuntu/ natty-updates/main i386 
Packages
  100 /var/lib/dpkg/status
   1:3.3.2-1ubuntu4 0
  500 http://us.archive.ubuntu.com/ubuntu/ natty/main i386 Packages

  3) What is expected to happen in LibreOffice Writer via the Terminal:

  cd ~/Desktop && wget
  
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/462564/+attachment/894856/+files/test.odt
  && lowriter -nologo test.odt

  is when one highlights the second column of the table -> secondary
  clicks -> Column -> Delete is only that column is deleted. Please see
  movie for more details:
  
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/462564/+attachment/894864/+files/out.ogv

  4) What happens instead is the whole table is deleted.

  Reproducible in:
  lsb_release -rd
  Description:  Ubuntu precise (development branch)
  Release:  12.04

  apt-cache policy libreoffice-writer
  libreoffice-writer:
Installed: 1:3.5.2-2ubuntu1
Candidate: 1:3.5.2-2ubuntu1
Version table:
   *** 1:3.5.2-2ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ precise/main i386 Packages
  100 /var/lib/dpkg/status

  WORKAROUND: Split the table then delete the column.

  WORKAROUND: Use Word via WINE.

  Microsoft Office Word 2003 (11.5604.6505)

  apt-cache policy wine1.3
  wine1.3:
    Installed: 1.3.28-0ubuntu1~ppa1~natty1
    Candidate: 1.3.28-0ubuntu1~ppa1~natty1
    Version table:
   *** 1.3.28-0ubuntu1~ppa1~natty1 0
  500 http://ppa.launchpad.net/ubuntu-wine/ppa/ubuntu/ natty/main i386 
Packages
  100 /var/lib/dpkg/status
   1.3.15-0ubuntu5 0
  500 http://us.archive.ubuntu.com/ubuntu/ natty/universe i386 Packages

  ProblemType: Bug
  Architecture: amd64
  Date: Wed Oct 28 09:43:20 2009
  DistroRelease: Ubuntu 9.10
  NonfreeKernelModules: fglrx
  Package: openoffice.org-core 1:3.1.1-5ubuntu1
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
  SourcePackage: openoffice.org
  Uname: Linux 2.6.31-14-generic x86_64

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/462564/+subscriptions


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

[Desktop-packages] [Bug 1976131] Re: automatic timezone updates to wrong timezone

[Launchpad Bug Tracker]

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

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

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

Title:
  automatic timezone updates to wrong timezone

Status in gnome-control-center:
  New
Status in gnome-control-center package in Ubuntu:
  Confirmed

Bug description:
  This is to mark a bug that I've reported upstream at:

  https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1874

  
  I am using GNOME 42.1 on Ubuntu 22.04. I leave the "Automatic Time Zone" on. 
When traveling last week to San Diego, with a layover in Seattle, I noticed 
that my timezone updated, but to the wrong timezone (MDT). I then got back on 
the plane and arrived in San Diego. This time the timezone updated to PTD as it 
should. I am now back in Seattle and the timezone has now updated from the 
correct zone PTD to the wrong one MDT.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-control-center 1:41.4-1ubuntu13.2
  ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30
  Uname: Linux 5.15.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 27 16:09:18 2022
  InstallationDate: Installed on 2021-10-12 (227 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to jammy on 2022-04-22 (34 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1976131/+subscriptions


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

[Desktop-packages] [Bug 1970663]

[Lite]

I'm chiming in to say that this is a bug on my setup as well.

I just upgraded from Ubuntu 20.04 LTS to 22.04.1 LTS, and the mouse
cursor is hard to see because it's so tiny. I have a 27"  4k LG monitor
connected with DP to an Nvidia graphics card.

I think Firefox sees the resolution, but not necessarily the scaling in
Gnome. In my case, it's also 200% (fractional scaling is not enabled on
this setup).

Not sure if it's exclusive to nvidia graphics either, but none of the
configuration that was available in 20.04 is available now in 22.04, as
far as I can tell. It's only been 30 minutes, though. I'm sure I'll get
more information as I use 22.04 more...

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

Title:
  Tiny mouse cursor in firefox snap

Status in Mozilla Firefox:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  Since a few day I've updated to Ubuntu Mate 22.04 with the firefox
  snap. Since then I've been having this strange bug. I have a 4k screen
  which I'm running at a 2180p resolution with scaling on HiDPI. This
  runs just fine except for in firefox. In the new firefox snap I get a
  really tiny mouse cursor. I also checked other snap, it is not the
  case there.

  Regards,
  Chris
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-02-02 (83 days ago)
  InstallationMedia: Ubuntu-MATE 21.10 "Impish Indri" - Release amd64 (20211012)
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: ubuntu-mate-artwork
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Snap: firefox 99.0.1-1 (stable)
  Snap.Changes: no changes found
  Tags:  jammy
  Uname: Linux 5.15.0-27-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-04-19 (7 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-02-02 (83 days ago)
  InstallationMedia: Ubuntu-MATE 21.10 "Impish Indri" - Release amd64 (20211012)
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: ubuntu-mate-artwork
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Snap: firefox 99.0.1-1 (stable)
  Snap.Changes: no changes found
  Tags:  jammy
  Uname: Linux 5.15.0-27-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-04-19 (7 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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


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

[Desktop-packages] [Bug 1970663]

[Ivan Sagalaev]

Another interesting observation. The cursor theme switches back to the
correct system one while dragging the Firefox window. But drops to the
tiny defaults as soon as you let go of dragging and move the cursor.

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

Title:
  Tiny mouse cursor in firefox snap

Status in Mozilla Firefox:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  Since a few day I've updated to Ubuntu Mate 22.04 with the firefox
  snap. Since then I've been having this strange bug. I have a 4k screen
  which I'm running at a 2180p resolution with scaling on HiDPI. This
  runs just fine except for in firefox. In the new firefox snap I get a
  really tiny mouse cursor. I also checked other snap, it is not the
  case there.

  Regards,
  Chris
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-02-02 (83 days ago)
  InstallationMedia: Ubuntu-MATE 21.10 "Impish Indri" - Release amd64 (20211012)
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: ubuntu-mate-artwork
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Snap: firefox 99.0.1-1 (stable)
  Snap.Changes: no changes found
  Tags:  jammy
  Uname: Linux 5.15.0-27-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-04-19 (7 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-02-02 (83 days ago)
  InstallationMedia: Ubuntu-MATE 21.10 "Impish Indri" - Release amd64 (20211012)
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: ubuntu-mate-artwork
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Snap: firefox 99.0.1-1 (stable)
  Snap.Changes: no changes found
  Tags:  jammy
  Uname: Linux 5.15.0-27-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-04-19 (7 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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


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

[Desktop-packages] [Bug 1991530] [NEW] After upgrading to Ubuntu 22.10-beta I lost the sound.

[jmst]

Public bug reported:

In the list of devices for testing sound I get only "Dummy Output". With
22.04 everything was ok.

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: alsa-base 1.0.25+dfsg-0ubuntu7
ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
Uname: Linux 5.19.0-15-generic x86_64
ApportVersion: 2.23.0-0ubuntu2
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', 
'/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct  3 14:27:59 2022
InstallationDate: Installed on 2019-07-01 (1190 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
PackageArchitecture: all
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
SourcePackage: alsa-driver
Symptom: audio
UpgradeStatus: Upgraded to kinetic on 2022-09-30 (2 days ago)
dmi.bios.date: 07/15/2022
dmi.bios.release: 1.33
dmi.bios.vendor: LENOVO
dmi.bios.version: R0YET50W (1.33 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20NB002BPG
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.ec.firmware.release: 1.23
dmi.modalias: 
dmi:bvnLENOVO:bvrR0YET50W(1.33):bd07/15/2022:br1.33:efr1.23:svnLENOVO:pn20NB002BPG:pvrThinkPadE590:rvnLENOVO:rn20NB002BPG:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20NB_BU_SMB_FM_ThinkPadE590:
dmi.product.family: ThinkPad E590
dmi.product.name: 20NB002BPG
dmi.product.sku: LENOVO_MT_20NB_BU_SMB_FM_ThinkPad E590
dmi.product.version: ThinkPad E590
dmi.sys.vendor: LENOVO

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


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

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

Title:
  After upgrading to Ubuntu 22.10-beta I lost the sound.

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  In the list of devices for testing sound I get only "Dummy Output".
  With 22.04 everything was ok.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', 
'/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct  3 14:27:59 2022
  InstallationDate: Installed on 2019-07-01 (1190 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: alsa-driver
  Symptom: audio
  UpgradeStatus: Upgraded to kinetic on 2022-09-30 (2 days ago)
  dmi.bios.date: 07/15/2022
  dmi.bios.release: 1.33
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0YET50W (1.33 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20NB002BPG
  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.ec.firmware.release: 1.23
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0YET50W(1.33):bd07/15/2022:br1.33:efr1.23:svnLENOVO:pn20NB002BPG:pvrThinkPadE590:rvnLENOVO:rn20NB002BPG:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20NB_BU_SMB_FM_ThinkPadE590:
  dmi.product.family: ThinkPad E590
  dmi.product.name: 20NB002BPG
  dmi.product.sku: LENOVO_MT_20NB_BU_SMB_FM_ThinkPad E590
  dmi.product.version: ThinkPad E590
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1991530/+subscriptions


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

[Desktop-packages] [Bug 1960417] Re: Show applications in alphabetical order

[peterzay]

I have never reordered anything manually.  Lots of software has been
installed.

Every time I want to find something, I must navigate the entire list.
Very unproductive.

Default behaviour should be sorted ascending.

Offer an option to turn that default off if you sort and group manually.

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

Title:
  Show applications in alphabetical order

Status in gnome-shell package in Ubuntu:
  Opinion

Bug description:
  ***
  *** Please change package to the appropriate one
  ***

  In Ubuntu 22.04, the "Show Applications" icon at the bottom of the
  launcher gives the apps in undesired order.

  This needs to be sorted in ascending order.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gedit 40.1-3
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Uname: Linux 5.15.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu76
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb  9 09:52:54 2022
  InstallationDate: Installed on 2022-02-06 (2 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220202)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gedit
  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/1960417/+subscriptions


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

[Desktop-packages] [Bug 1982885] Re: Firefox does not scroll with touch input

[Matthew Lovibond]

That fixes it!

MOZ_ENABLE_WAYLAND=1 firefox

Thanks

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

Title:
  Firefox does not scroll with touch input

Status in firefox package in Ubuntu:
  Expired

Bug description:
  Firefox does not scroll with the usual touch gesture of swiping up or
  down on the screen. This action just selects text on the page as
  though the left mouse button was depressed and the cursor moved across
  the page.

  lsb_release -rd
  Description:  Ubuntu 22.04 LTS
  Release:  22.04

  Snapstore version 103.0-1 latest stable

  Possibly related to being packaged as a snap (have noticed this
  behaviour on Fedora using the firefox snap).

  It's still possible to scroll by dragging the scrollbar but this
  essentially breaks firefox on touch systems

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


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

[Desktop-packages] [Bug 1991526] [NEW] Panel freezes on return from screensaver with external monitor attached

[stelian]

Public bug reported:

My setup is composed of a Dell XPS13 9320, with one (or two) external
USB-C monitors attached. The laptop panel is the primary screen. I'm
using gnome on Wayland.

Everything is working fine, except when resuming from screensaver: the
prompt for password is shown on the laptop panel, and I start typing the
password. At this point, the laptop panel freezes. This can happen
almost immediately (I will see for example two or three dots as I typed
the first characters of my password) or this can happen a few seconds
later (meanwhile the screen has been unlocked, the panel shows the
desktop, then it freezes).

Interestingly, the external monitors are woken up, desktop is unlocked,
and will continue working, while the laptop panel is frozen.

After that, let's say 40% of the time, the panel will un-freeze itself
after 30 seconds or so. 40% of the time it will remain frozen, and 20%
of the time the whole display will freeze (including the external
monitors).

When it happens, I can recover by either un-plugging / re-plugging one
of the external monitors, or by typing Ctrl-Alt-F1, then retyping my
password, then everything is fine again... until the next screen lock.

This bug is reproducible more or less 50% of the time (one in two screen
locks causes freezes). Deactivating the dash-to-panel gnome extension
made it less reproducible, but it still happens.

I didn't see any interesting error message in the logs, but maybe I
didn't look at the correct place.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gdm3 42.0-1ubuntu7
ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
Uname: Linux 5.15.0-48-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct  3 13:54:42 2022
ExecutablePath: /usr/libexec/gdm-wayland-session
InstallationDate: Installed on 2022-07-20 (75 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=fr_FR.UTF-8
 XDG_RUNTIME_DIR=
SourcePackage: gdm3
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  Panel freezes on return from screensaver with external monitor
  attached

Status in gdm3 package in Ubuntu:
  New

Bug description:
  My setup is composed of a Dell XPS13 9320, with one (or two) external
  USB-C monitors attached. The laptop panel is the primary screen. I'm
  using gnome on Wayland.

  Everything is working fine, except when resuming from screensaver: the
  prompt for password is shown on the laptop panel, and I start typing
  the password. At this point, the laptop panel freezes. This can happen
  almost immediately (I will see for example two or three dots as I
  typed the first characters of my password) or this can happen a few
  seconds later (meanwhile the screen has been unlocked, the panel shows
  the desktop, then it freezes).

  Interestingly, the external monitors are woken up, desktop is
  unlocked, and will continue working, while the laptop panel is frozen.

  After that, let's say 40% of the time, the panel will un-freeze itself
  after 30 seconds or so. 40% of the time it will remain frozen, and 20%
  of the time the whole display will freeze (including the external
  monitors).

  When it happens, I can recover by either un-plugging / re-plugging one
  of the external monitors, or by typing Ctrl-Alt-F1, then retyping my
  password, then everything is fine again... until the next screen lock.

  This bug is reproducible more or less 50% of the time (one in two
  screen locks causes freezes). Deactivating the dash-to-panel gnome
  extension made it less reproducible, but it still happens.

  I didn't see any interesting error message in the logs, but maybe I
  didn't look at the correct place.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gdm3 42.0-1ubuntu7
  ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
  Uname: Linux 5.15.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct  3 13:54:42 2022
  ExecutablePath: /usr/libexec/gdm-wayland-session
  InstallationDate: Installed on 2022-07-20 (75 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  ProcEnviron:
   SHELL=/bin/bash
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   XDG_RUNTIME_DIR=
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

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


-- 
Mailing list: https://launchpad.net/~de

[Desktop-packages] [Bug 1991524] [NEW] regression: broadwell-rt286 sound card audio output is extremely low

[Benjamin Richardson]

Public bug reported:

1) The release of Ubuntu you are using, via 'lsb_release -rd' or System
-> About Ubuntu

Description:Ubuntu Kinetic Kudu (development branch)
Release:22.10

2) The version of the package you are using, via 'apt-cache policy
pkgname' or by checking in Software Center

alsa-base:
  Installed: 1.0.25+dfsg-0ubuntu7
  Candidate: 1.0.25+dfsg-0ubuntu7
  Version table:
 *** 1.0.25+dfsg-0ubuntu7 500
500 http://us.archive.ubuntu.com/ubuntu kinetic/main amd64 Packages
500 http://us.archive.ubuntu.com/ubuntu kinetic/main i386 Packages
100 /var/lib/dpkg/status

3) What you expected to happen

In Ubuntu 22.04 and prior versions, audio output via my laptop speakers
worked just fine. It was clear and played at a reasonable max volume. I
expected the same for 22.10.

4) What happened instead

Audio output for my laptop (an HP Spectre x360 Convertible 13--802D) is
extremely low, to the point where I thought sound wasn't playing at all.
It was only when I played an extremely loud YouTube video with volume at
max with the speaker held up to my ear that I realized it was playing.
The same issue is happening with my laptop's headphone jack, but not
when I plug in a USB speaker or play sound via HDMI.

I know that Ubuntu is switching to pipewire and wireplumber for audio in
the 22.10 release. Pipewire has given me trouble on other distributions
that already use it for this particular device, so that may be part of
the problem.

I've tried increasing all volume sliders in alsamixer as well, with no
improvement.

Please let me know if there's any other information you need.

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: alsa-base 1.0.25+dfsg-0ubuntu7
ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
Uname: Linux 5.19.0-15-generic x86_64
ApportVersion: 2.23.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct  3 07:18:54 2022
InstallationDate: Installed on 2022-10-03 (0 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Beta amd64 (20220927.1)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/20/2018
dmi.bios.release: 15.81
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F.51
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 802D
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 58.63
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 58.99
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.51:bd06/20/2018:br15.81:efr58.99:svnHewlett-Packard:pnHPSpectrex360Convertible13:pvr:rvnHewlett-Packard:rn802D:rvr58.63:cvnHewlett-Packard:ct10:cvrChassisVersion:skuL0Q56UA#ABA:
dmi.product.family: 103C_5335KV G=N L=CON B=HP S=SPT
dmi.product.name: HP Spectre x360 Convertible 13
dmi.product.sku: L0Q56UA#ABA
dmi.sys.vendor: Hewlett-Packard

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


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

** Description changed:

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System
  -> About Ubuntu
  
  Description:  Ubuntu Kinetic Kudu (development branch)
  Release:  22.10
  
  2) The version of the package you are using, via 'apt-cache policy
  pkgname' or by checking in Software Center
  
  alsa-base:
-   Installed: 1.0.25+dfsg-0ubuntu7
-   Candidate: 1.0.25+dfsg-0ubuntu7
-   Version table:
-  *** 1.0.25+dfsg-0ubuntu7 500
- 500 http://us.archive.ubuntu.com/ubuntu kinetic/main amd64 Packages
- 500 http://us.archive.ubuntu.com/ubuntu kinetic/main i386 Packages
- 100 /var/lib/dpkg/status
+   Installed: 1.0.25+dfsg-0ubuntu7
+   Candidate: 1.0.25+dfsg-0ubuntu7
+   Version table:
+  *** 1.0.25+dfsg-0ubuntu7 500
+ 500 http://us.archive.ubuntu.com/ubuntu kinetic/main amd64 Packages
+ 500 http://us.archive.ubuntu.com/ubuntu kinetic/main i386 Packages
+ 100 /var/lib/dpkg/status
  
  3) What you expected to happen
  
  In Ubuntu 22.04 and prior versions, audio output via my laptop speakers
  worked just fine. It was clear and played at a reasonable max volume. I
  expected the same for 22.10.
  
  4) What happened instead
  
  Audio output for my laptop (an HP Spectre x360 Convertible 13--802D) is
  extremely low, to the point where I thought sound wasn't playing at all.
  It was only when I played an extremely loud YouTube video with volume at
  max with the speaker held up to my ear that I realized it was playing.
  The same issue is happening with my laptop's headphone jack, but not
  when I plug in a USB speaker or play sound via HDMI.
  
  I know that Ubuntu is switching to pipewire and wireplumber for audio in
  the 22.10 release. Pipewire has given me trouble on other distributions
  tha

[Desktop-packages] [Bug 1980839] Re: thunderbird -compose returns error since the 102 snap update?

[Petar Andrejic]

Same story with journald:
ran thunderbird --compose  from the command line, got this in journald:

USER_AVC pid=2914 uid=102 auid=4294967295 ses=4294967295 subj=?
msg='apparmor="DENIED" operation="dbus_method_call"  bus="system"
path="/org/freedesktop/DBus" interface="org.freedesktop.DBus"
member="ListNames" mask="send" name="org.freedesktop.DBus" pid=211487
label="snap.thunderbird.thunderbird" peer_label="unconfined"

However, it seems to be unrelated to this bug, as the bug still shows up
when I disable apparmor

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

Title:
  thunderbird -compose returns error since the 102 snap update?

Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  After updating to the latest thunderbird 102.0.1 snap on Ubuntu 20.04,
  it is no longer possible to open mailto links from the firefox snap in
  thunderbird. When clicking a mailto link in the firefox 102.0.1 snap,
  thunderbird returns the following error message: "Thunderbird is
  already running, but is not responding. To use Thunderbird, you must
  first close the existing Thunderbird process, restart your device, or
  use a different profile." The issue appears related to the thunderbird
  update as there was no issue opening links in the previous 91 version.

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


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

[Desktop-packages] [Bug 1991117] Re: 13.3.0-3build1 fails to build from source

[Graham Inggs]

** Tags added: ftbfs

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

Title:
  13.3.0-3build1 fails to build from source

Status in xserver-xorg-video-vmware package in Ubuntu:
  Fix Committed

Bug description:
  [Log]
  
https://launchpadlibrarian.net/625441992/buildlog_ubuntu-kinetic-amd64.xserver-xorg-video-vmware_1%3A13.3.0-3build1_BUILDING.txt.gz

  [Error]
  ../../vmwgfx/vmwgfx_tex_video.c: In function ‘stop_video’:
  ../../vmwgfx/vmwgfx_tex_video.c:240:20: error: the comparison will always 
evaluate as ‘true’ for the address of ‘yuv’ will never be NULL [-Werror=address]
240 |if (priv->yuv[i]) {
|^~~~
  ../../vmwgfx/vmwgfx_tex_video.c:125:24: note: ‘yuv’ declared here
125 | struct xa_surface *yuv[2][3];
|^~~

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-vmware/+bug/1991117/+subscriptions


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

[Desktop-packages] [Bug 1790608] Re: [snap] Libreoffice/Firefox do not open files from thunderbird (more general: from /tmp)

[Olivier Tilloy]

I've added a snapd task because it is a question that comes up time and
again on the snapcraft forum, and would likely require changes in snapd
itself for apps to be able to safely share a temporary directory.

** Also affects: snapd
   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/1790608

Title:
  [snap] Libreoffice/Firefox do not open files from thunderbird (more
  general: from /tmp)

Status in snapd:
  New
Status in firefox package in Ubuntu:
  Confirmed
Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  I received a document via e-mail in Thunderbird. I have the
  Libreoffice snap package installed. When I want to open the document
  from Thunderbird, I see the Libreoffice splash screen, and then a
  dialog stating "/tmp/mozilla_0/.docx does not exist."

  The same dialog appears when I navigate to the folder in Files and
  want to open it.

  When I copy the file to my desktop, however, I can open it without
  problems.

  I guess the source of the issue is confinement, that the Libreoffice
  snap can only access files from $HOME. But this breaks the case where
  thunderbird creates a temporary copy in /tmp.

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


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

[Desktop-packages] [Bug 1989726] Re: Only a quarter of the screen showing in VirtualBox

[Daniel van Vugt]

** Package changed: mutter (Ubuntu) => gnome-shell-extension-ubuntu-dock
(Ubuntu)

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

Title:
  Only a quarter of the screen showing in VirtualBox

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  In Progress

Bug description:
  Only the top left quarter of my Ubuntu 22.04.1 desktop is showing on
  VirtualBox 6.1.30. I've installed Guest Additions CD. apt updated and
  restarted twice.

  I've tried Xubuntu and Kubuntu 22.04 and they both work without any
  errors.

  Screenshot here: https://i.stack.imgur.com/KI0YO.png

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


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

[Desktop-packages] [Bug 1991512] Re: nautilus crashed with SIGSEGV in g_str_hash()

[Apport retracing service]

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

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 #1987981, 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/1991512/+attachment/5620691/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1987981
   nautilus crashed with SIGSEGV in g_str_hash()

** 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 nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1991512

Title:
  nautilus crashed with SIGSEGV in g_str_hash()

Status in nautilus package in Ubuntu:
  New

Bug description:
  While opening nautilus as root the application closed and generated
  this bug report. ueing ubuntu 22.10.

  ProblemType: Crash
  DistroRelease: Ubuntu 22.10
  Package: nautilus 1:43.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct  3 14:38:20 2022
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   
  InstallationDate: Installed on 2022-10-03 (0 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Beta amd64 (20220927.1)
  ProcCmdline: nautilus
  ProcEnviron:
   LANGUAGE=en_IN:en
   LANG=en_IN
   TERM=xterm-256color
   PATH=(custom, no user)
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f334f8720c4 : movsbl (%rdi),%edx
   PC (0x7f334f8720c4) ok
   source "(%rdi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%edx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: nautilus
  StacktraceTop:
   g_str_hash () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_hash_table_contains () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgtk-4.so.1
   ?? () from /lib/x86_64-linux-gnu/libgtk-4.so.1
   ?? () from /lib/x86_64-linux-gnu/libgtk-4.so.1
  Title: nautilus crashed with SIGSEGV in g_str_hash()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  separator:
   
  usr_lib_nautilus:
   file-roller   43.0-1
   nautilus-extension-gnome-terminal 3.46.1-2ubuntu1

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


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

[Desktop-packages] [Bug 1848942] Re: Freeze on opening font viewer

[James Paton-Smith]

I tested gnome-font-viewer again on the same systems after upgrading to
Ubuntu 22.04.1 and haven't been able to replicate the issue yet.

Ubuntu 22.04.1
gnome-font-viewer 41.0-2

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

Title:
  Freeze on opening font viewer

Status in gnome-font-viewer package in Ubuntu:
  Confirmed

Bug description:
  When I open gnome-font-viewer, after few seconds interface freezes and
  I only can move my cursor.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-font-viewer 3.34.0-1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 20 20:02:24 2019
  InstallationDate: Installed on 2019-10-20 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-font-viewer
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1991507] Re: Monitor does not turn on

[Daniel van Vugt]

Thanks for the bug report. This is probably bug 1968040 so please try
the workaround mentioned there.


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

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

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

Title:
  Monitor does not turn on

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  The main screen does not turn on after the monitors are turned off due
  to energy saving (there is no video signal). The secondary screen
  turns on correctly. It doesn't happen every time

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
  Uname: Linux 5.15.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct  3 09:17:24 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DpkgLog:
   
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company HD Graphics 630 [103c:8299]
  InstallationDate: Installed on 2022-09-26 (6 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 1c4f:00b0 SiGma Micro USB Optical Mouse
   Bus 001 Device 002: ID 03f0:2b4a HP, Inc Business Slim Keyboard
   Bus 001 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth 
Dongle (HCI mode)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP Z4D06EA#ABE
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic 
root=UUID=f28d3bdb-0af0-4cbf-a682-38f39118cb88 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/14/2019
  dmi.bios.release: 2.27
  dmi.bios.vendor: HP
  dmi.bios.version: P01 Ver. 02.27
  dmi.board.name: 8299
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 06.21
  dmi.chassis.type: 3
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 6.33
  dmi.modalias: 
dmi:bvnHP:bvrP01Ver.02.27:bd04/14/2019:br2.27:efr6.33:svnHP:pnZ4D06EA#ABE:pvr:rvnHP:rn8299:rvrKBCVersion06.21:cvnHP:ct3:cvr:skuZ4D06EA:
  dmi.product.family: 103C_53307F HP EliteDesk
  dmi.product.name: Z4D06EA#ABE
  dmi.product.sku: Z4D06EA
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.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-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Desktop-packages] [Bug 1991507] [NEW] Monitor does not turn on

[Pablo]

Public bug reported:

The main screen does not turn on after the monitors are turned off due
to energy saving (there is no video signal). The secondary screen turns
on correctly. It doesn't happen every time

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
Uname: Linux 5.15.0-48-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct  3 09:17:24 2022
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
DpkgLog:
 
ExtraDebuggingInterest: No
GraphicsCard:
 Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA 
controller])
   Subsystem: Hewlett-Packard Company HD Graphics 630 [103c:8299]
InstallationDate: Installed on 2022-09-26 (6 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 1c4f:00b0 SiGma Micro USB Optical Mouse
 Bus 001 Device 002: ID 03f0:2b4a HP, Inc Business Slim Keyboard
 Bus 001 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle 
(HCI mode)
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: HP Z4D06EA#ABE
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=es_ES.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic 
root=UUID=f28d3bdb-0af0-4cbf-a682-38f39118cb88 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/14/2019
dmi.bios.release: 2.27
dmi.bios.vendor: HP
dmi.bios.version: P01 Ver. 02.27
dmi.board.name: 8299
dmi.board.vendor: HP
dmi.board.version: KBC Version 06.21
dmi.chassis.type: 3
dmi.chassis.vendor: HP
dmi.ec.firmware.release: 6.33
dmi.modalias: 
dmi:bvnHP:bvrP01Ver.02.27:bd04/14/2019:br2.27:efr6.33:svnHP:pnZ4D06EA#ABE:pvr:rvnHP:rn8299:rvrKBCVersion06.21:cvnHP:ct3:cvr:skuZ4D06EA:
dmi.product.family: 103C_53307F HP EliteDesk
dmi.product.name: Z4D06EA#ABE
dmi.product.sku: Z4D06EA
dmi.sys.vendor: HP
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.110-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.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-2ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


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

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

Title:
  Monitor does not turn on

Status in xorg package in Ubuntu:
  New

Bug description:
  The main screen does not turn on after the monitors are turned off due
  to energy saving (there is no video signal). The secondary screen
  turns on correctly. It doesn't happen every time

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
  Uname: Linux 5.15.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct  3 09:17:24 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DpkgLog:
   
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company HD Graphics 630 [103c:8299]
  InstallationDate: Installed on 2022-09-26 (6 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 1c4f:00b0 SiGma Micro USB Optical Mouse
   Bus 001 Device 002: ID 03f0:2b4a HP, Inc Business Slim Keyboard
   Bus 001 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth 
Dongle (HCI mode)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP Z4D06EA#ABE
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic 
root=UUID=f28d3bdb-0af0-4cbf-a682-38f39118cb88 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh