date:20240105

Removing packages from noble:
nvidia-graphics-drivers-515 515.105.01-0ubuntu3 in noble
Comment: Unsupported driver version; LP: #2048087
1 package successfully removed.


** Changed in: nvidia-graphics-drivers-515 (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  RM: obsolete & superseded nvidia-graphics-drivers, leftovers

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-430 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-450 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-455 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515-server package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-530 package in Ubuntu:
  Fix Released

Bug description:
  
https://packages.ubuntu.com/search?suite=noble=all=any=nvidia-
  graphics-drivers=sourcenames

  Currently supported drivers are:
  nvidia-graphics-drivers-470
  nvidia-graphics-drivers-525
  nvidia-graphics-drivers-535
  nvidia-graphics-drivers-470-server
  nvidia-graphics-drivers-525-server
  nvidia-graphics-drivers-535-server

  all other drivers are superseded binaries, from obsolete and/or short-
  lived nvidia-graphics-drivers are however still published in the
  archive.

  please remove them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/2048087/+subscriptions


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

[Desktop-packages] [Bug 2048087] Re: RM: obsolete & superseded nvidia-graphics-drivers, leftovers

The other packages in this listed are reported by reverse-depends to
have non-empty revdeps.  However it looks like these all come from other
packages that have just been removed.  Rather than tracing this manually
and possibly making a mistake, I'll let the others sit for another
round.

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

Title:
  RM: obsolete & superseded nvidia-graphics-drivers, leftovers

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-430 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-450 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-455 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515-server package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-530 package in Ubuntu:
  Fix Released

Bug description:
  
https://packages.ubuntu.com/search?suite=noble=all=any=nvidia-
  graphics-drivers=sourcenames

  Currently supported drivers are:
  nvidia-graphics-drivers-470
  nvidia-graphics-drivers-525
  nvidia-graphics-drivers-535
  nvidia-graphics-drivers-470-server
  nvidia-graphics-drivers-525-server
  nvidia-graphics-drivers-535-server

  all other drivers are superseded binaries, from obsolete and/or short-
  lived nvidia-graphics-drivers are however still published in the
  archive.

  please remove them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/2048087/+subscriptions


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

[Desktop-packages] [Bug 2048087] Re: RM: obsolete & superseded nvidia-graphics-drivers, leftovers

Removing packages from noble:
nvidia-graphics-drivers-510 510.108.03-0ubuntu3 in noble
libnvidia-cfg1-495 510.108.03-0ubuntu3 in noble amd64
libnvidia-common-495 510.108.03-0ubuntu3 in noble amd64
libnvidia-common-495 510.108.03-0ubuntu3 in noble arm64
libnvidia-common-495 510.108.03-0ubuntu3 in noble armhf
libnvidia-common-495 510.108.03-0ubuntu3 in noble i386
libnvidia-common-495 510.108.03-0ubuntu3 in noble ppc64el
libnvidia-common-495 510.108.03-0ubuntu3 in noble riscv64
libnvidia-common-495 510.108.03-0ubuntu3 in noble s390x
libnvidia-common-510 510.108.03-0ubuntu3 in noble amd64
libnvidia-common-510 510.108.03-0ubuntu3 in noble arm64
libnvidia-common-510 510.108.03-0ubuntu3 in noble armhf
libnvidia-common-510 510.108.03-0ubuntu3 in noble i386
libnvidia-common-510 510.108.03-0ubuntu3 in noble ppc64el
libnvidia-common-510 510.108.03-0ubuntu3 in noble riscv64
libnvidia-common-510 510.108.03-0ubuntu3 in noble s390x
libnvidia-compute-495 510.108.03-0ubuntu3 in noble amd64
libnvidia-compute-495 510.108.03-0ubuntu3 in noble i386
libnvidia-decode-495 510.108.03-0ubuntu3 in noble amd64
libnvidia-decode-495 510.108.03-0ubuntu3 in noble i386
libnvidia-encode-495 510.108.03-0ubuntu3 in noble amd64
libnvidia-encode-495 510.108.03-0ubuntu3 in noble i386
libnvidia-extra-495 510.108.03-0ubuntu3 in noble amd64
libnvidia-extra-495 510.108.03-0ubuntu3 in noble i386
libnvidia-fbc1-495 510.108.03-0ubuntu3 in noble amd64
libnvidia-fbc1-495 510.108.03-0ubuntu3 in noble i386
libnvidia-gl-495 510.108.03-0ubuntu3 in noble amd64
libnvidia-gl-495 510.108.03-0ubuntu3 in noble i386
nvidia-compute-utils-495 510.108.03-0ubuntu3 in noble amd64
nvidia-dkms-495 510.108.03-0ubuntu3 in noble amd64
nvidia-driver-495 510.108.03-0ubuntu3 in noble amd64
nvidia-headless-495 510.108.03-0ubuntu3 in noble amd64
nvidia-headless-no-dkms-495 510.108.03-0ubuntu3 in noble amd64
nvidia-kernel-common-495 510.108.03-0ubuntu3 in noble amd64
nvidia-kernel-source-495 510.108.03-0ubuntu3 in noble amd64
nvidia-utils-495 510.108.03-0ubuntu3 in noble amd64
xserver-xorg-video-nvidia-495 510.108.03-0ubuntu3 in noble amd64
Comment: Unsupported driver version; LP: #2048087
1 package successfully removed.


** Changed in: nvidia-graphics-drivers-510 (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  RM: obsolete & superseded nvidia-graphics-drivers, leftovers

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-430 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-450 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-455 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515-server package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-530 package in Ubuntu:
  Fix Released

Bug description:
  
https://packages.ubuntu.com/search?suite=noble=all=any=nvidia-
  graphics-drivers=sourcenames

  Currently supported drivers are:
  nvidia-graphics-drivers-470
  nvidia-graphics-drivers-525
  nvidia-graphics-drivers-535
  nvidia-graphics-drivers-470-server
  nvidia-graphics-drivers-525-server
  nvidia-graphics-drivers-535-server

  all other drivers are superseded binaries, from obsolete and/or short-
  lived nvidia-graphics-drivers are however still published in the
  archive.

  please remove them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/2048087/+subscriptions


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

[Desktop-packages] [Bug 2048087] Re: RM: obsolete & superseded nvidia-graphics-drivers, leftovers

Removing packages from noble:
nvidia-graphics-drivers-530 530.41.03-0ubuntu2 in noble
Comment: Unsupported driver version; LP: #2048087
1 package successfully removed.


** Changed in: nvidia-graphics-drivers-530 (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  RM: obsolete & superseded nvidia-graphics-drivers, leftovers

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-430 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-450 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-455 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515-server package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-530 package in Ubuntu:
  Fix Released

Bug description:
  
https://packages.ubuntu.com/search?suite=noble=all=any=nvidia-
  graphics-drivers=sourcenames

  Currently supported drivers are:
  nvidia-graphics-drivers-470
  nvidia-graphics-drivers-525
  nvidia-graphics-drivers-535
  nvidia-graphics-drivers-470-server
  nvidia-graphics-drivers-525-server
  nvidia-graphics-drivers-535-server

  all other drivers are superseded binaries, from obsolete and/or short-
  lived nvidia-graphics-drivers are however still published in the
  archive.

  please remove them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/2048087/+subscriptions


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

[Desktop-packages] [Bug 2048087] Re: RM: obsolete & superseded nvidia-graphics-drivers, leftovers

Removing packages from noble:
nvidia-graphics-drivers-455 455.45.01-0ubuntu1 in noble
libnvidia-cfg1-435 455.45.01-0ubuntu1 in noble amd64
libnvidia-common-435 455.45.01-0ubuntu1 in noble amd64
libnvidia-common-435 455.45.01-0ubuntu1 in noble arm64
libnvidia-common-435 455.45.01-0ubuntu1 in noble armhf
libnvidia-common-435 455.45.01-0ubuntu1 in noble i386
libnvidia-common-435 455.45.01-0ubuntu1 in noble ppc64el
libnvidia-common-435 455.45.01-0ubuntu1 in noble riscv64
libnvidia-common-435 455.45.01-0ubuntu1 in noble s390x
libnvidia-common-455 455.45.01-0ubuntu1 in noble amd64
libnvidia-common-455 455.45.01-0ubuntu1 in noble arm64
libnvidia-common-455 455.45.01-0ubuntu1 in noble armhf
libnvidia-common-455 455.45.01-0ubuntu1 in noble i386
libnvidia-common-455 455.45.01-0ubuntu1 in noble ppc64el
libnvidia-common-455 455.45.01-0ubuntu1 in noble riscv64
libnvidia-common-455 455.45.01-0ubuntu1 in noble s390x
libnvidia-compute-435 455.45.01-0ubuntu1 in noble amd64
libnvidia-compute-435 455.45.01-0ubuntu1 in noble i386
libnvidia-decode-435 455.45.01-0ubuntu1 in noble amd64
libnvidia-decode-435 455.45.01-0ubuntu1 in noble i386
libnvidia-encode-435 455.45.01-0ubuntu1 in noble amd64
libnvidia-encode-435 455.45.01-0ubuntu1 in noble i386
libnvidia-fbc1-435 455.45.01-0ubuntu1 in noble amd64
libnvidia-fbc1-435 455.45.01-0ubuntu1 in noble i386
libnvidia-gl-435 455.45.01-0ubuntu1 in noble amd64
libnvidia-gl-435 455.45.01-0ubuntu1 in noble i386
libnvidia-ifr1-435 455.45.01-0ubuntu1 in noble amd64
libnvidia-ifr1-435 455.45.01-0ubuntu1 in noble i386
nvidia-compute-utils-435 455.45.01-0ubuntu1 in noble amd64
nvidia-dkms-435 455.45.01-0ubuntu1 in noble amd64
nvidia-driver-435 455.45.01-0ubuntu1 in noble amd64
nvidia-headless-435 455.45.01-0ubuntu1 in noble amd64
nvidia-headless-no-dkms-435 455.45.01-0ubuntu1 in noble amd64
nvidia-kernel-common-435 455.45.01-0ubuntu1 in noble amd64
nvidia-kernel-source-435 455.45.01-0ubuntu1 in noble amd64
nvidia-utils-435 455.45.01-0ubuntu1 in noble amd64
xserver-xorg-video-nvidia-435 455.45.01-0ubuntu1 in noble amd64
Comment: Unsupported driver version; LP: #2048087
1 package successfully removed.


** Changed in: nvidia-graphics-drivers-455 (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  RM: obsolete & superseded nvidia-graphics-drivers, leftovers

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-430 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-450 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-455 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515-server package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-530 package in Ubuntu:
  Fix Released

Bug description:
  
https://packages.ubuntu.com/search?suite=noble=all=any=nvidia-
  graphics-drivers=sourcenames

  Currently supported drivers are:
  nvidia-graphics-drivers-470
  nvidia-graphics-drivers-525
  nvidia-graphics-drivers-535
  nvidia-graphics-drivers-470-server
  nvidia-graphics-drivers-525-server
  nvidia-graphics-drivers-535-server

  all other drivers are superseded binaries, from obsolete and/or short-
  lived nvidia-graphics-drivers are however still published in the
  archive.

  please remove them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/2048087/+subscriptions


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

[Desktop-packages] [Bug 2048087] Re: RM: obsolete & superseded nvidia-graphics-drivers, leftovers

Removing packages from noble:
nvidia-graphics-drivers-435 435.21-0ubuntu8 in noble
Comment: Unsupported driver version; LP: #2048087
1 package successfully removed.


** Changed in: nvidia-graphics-drivers-435 (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  RM: obsolete & superseded nvidia-graphics-drivers, leftovers

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-430 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-450 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-455 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-515-server package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-530 package in Ubuntu:
  Triaged

Bug description:
  
https://packages.ubuntu.com/search?suite=noble=all=any=nvidia-
  graphics-drivers=sourcenames

  Currently supported drivers are:
  nvidia-graphics-drivers-470
  nvidia-graphics-drivers-525
  nvidia-graphics-drivers-535
  nvidia-graphics-drivers-470-server
  nvidia-graphics-drivers-525-server
  nvidia-graphics-drivers-535-server

  all other drivers are superseded binaries, from obsolete and/or short-
  lived nvidia-graphics-drivers are however still published in the
  archive.

  please remove them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/2048087/+subscriptions


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

[Desktop-packages] [Bug 2048087] Re: RM: obsolete & superseded nvidia-graphics-drivers, leftovers

Removing packages from noble:
nvidia-graphics-drivers-430 430.50-0ubuntu3 in noble
libnvidia-cfg1-418 430.50-0ubuntu3 in noble amd64
libnvidia-common-418 430.50-0ubuntu3 in noble amd64
libnvidia-common-418 430.50-0ubuntu3 in noble arm64
libnvidia-common-418 430.50-0ubuntu3 in noble armhf
libnvidia-common-418 430.50-0ubuntu3 in noble i386
libnvidia-common-418 430.50-0ubuntu3 in noble ppc64el
libnvidia-common-418 430.50-0ubuntu3 in noble riscv64
libnvidia-common-418 430.50-0ubuntu3 in noble s390x
libnvidia-common-430 430.50-0ubuntu3 in noble amd64
libnvidia-common-430 430.50-0ubuntu3 in noble arm64
libnvidia-common-430 430.50-0ubuntu3 in noble armhf
libnvidia-common-430 430.50-0ubuntu3 in noble i386
libnvidia-common-430 430.50-0ubuntu3 in noble ppc64el
libnvidia-common-430 430.50-0ubuntu3 in noble riscv64
libnvidia-common-430 430.50-0ubuntu3 in noble s390x
libnvidia-compute-418 430.50-0ubuntu3 in noble amd64
libnvidia-compute-418 430.50-0ubuntu3 in noble i386
libnvidia-decode-418 430.50-0ubuntu3 in noble amd64
libnvidia-decode-418 430.50-0ubuntu3 in noble i386
libnvidia-encode-418 430.50-0ubuntu3 in noble amd64
libnvidia-encode-418 430.50-0ubuntu3 in noble i386
libnvidia-fbc1-418 430.50-0ubuntu3 in noble amd64
libnvidia-fbc1-418 430.50-0ubuntu3 in noble i386
libnvidia-gl-418 430.50-0ubuntu3 in noble amd64
libnvidia-gl-418 430.50-0ubuntu3 in noble i386
libnvidia-ifr1-418 430.50-0ubuntu3 in noble amd64
libnvidia-ifr1-418 430.50-0ubuntu3 in noble i386
nvidia-compute-utils-418 430.50-0ubuntu3 in noble amd64
nvidia-dkms-418 430.50-0ubuntu3 in noble amd64
nvidia-driver-418 430.50-0ubuntu3 in noble amd64
nvidia-headless-418 430.50-0ubuntu3 in noble amd64
nvidia-headless-no-dkms-418 430.50-0ubuntu3 in noble amd64
nvidia-kernel-common-418 430.50-0ubuntu3 in noble amd64
nvidia-kernel-source-418 430.50-0ubuntu3 in noble amd64
nvidia-utils-418 430.50-0ubuntu3 in noble amd64
xserver-xorg-video-nvidia-418 430.50-0ubuntu3 in noble amd64
Comment: Unsupported driver version; LP: #2048087
1 package successfully removed.


** Changed in: nvidia-graphics-drivers-430 (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  RM: obsolete & superseded nvidia-graphics-drivers, leftovers

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-430 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-450 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-455 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-515-server package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-530 package in Ubuntu:
  Triaged

Bug description:
  
https://packages.ubuntu.com/search?suite=noble=all=any=nvidia-
  graphics-drivers=sourcenames

  Currently supported drivers are:
  nvidia-graphics-drivers-470
  nvidia-graphics-drivers-525
  nvidia-graphics-drivers-535
  nvidia-graphics-drivers-470-server
  nvidia-graphics-drivers-525-server
  nvidia-graphics-drivers-535-server

  all other drivers are superseded binaries, from obsolete and/or short-
  lived nvidia-graphics-drivers are however still published in the
  archive.

  please remove them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/2048087/+subscriptions


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

[Desktop-packages] [Bug 2048087] Re: RM: obsolete & superseded nvidia-graphics-drivers, leftovers

Removing packages from noble:
nvidia-graphics-drivers-340 340.108-0ubuntu8 in noble
libcuda1-340 340.108-0ubuntu8 in noble amd64
libcuda1-340 340.108-0ubuntu8 in noble armhf
nvidia-340 340.108-0ubuntu8 in noble amd64
nvidia-340 340.108-0ubuntu8 in noble armhf
nvidia-340-dev 340.108-0ubuntu8 in noble amd64
nvidia-340-dev 340.108-0ubuntu8 in noble armhf
nvidia-340-uvm 340.108-0ubuntu8 in noble amd64
nvidia-340-uvm 340.108-0ubuntu8 in noble armhf
nvidia-libopencl1-340 340.108-0ubuntu8 in noble amd64
nvidia-opencl-icd-340 340.108-0ubuntu8 in noble amd64
Comment: Unsupported driver version; LP: #2048087


** Changed in: nvidia-graphics-drivers-340 (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  RM: obsolete & superseded nvidia-graphics-drivers, leftovers

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-430 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-450 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-455 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-515-server package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-530 package in Ubuntu:
  Triaged

Bug description:
  
https://packages.ubuntu.com/search?suite=noble=all=any=nvidia-
  graphics-drivers=sourcenames

  Currently supported drivers are:
  nvidia-graphics-drivers-470
  nvidia-graphics-drivers-525
  nvidia-graphics-drivers-535
  nvidia-graphics-drivers-470-server
  nvidia-graphics-drivers-525-server
  nvidia-graphics-drivers-535-server

  all other drivers are superseded binaries, from obsolete and/or short-
  lived nvidia-graphics-drivers are however still published in the
  archive.

  please remove them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/2048087/+subscriptions


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

[Desktop-packages] [Bug 2042729] Re: gnome-shell freeze

2024-01-05 Thread Launchpad Bug Tracker

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

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

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

Title:
  gnome-shell freeze

Status in gnome-shell package in Ubuntu:
  Expired

Bug description:
  Computer unresponsive after closing laptop screen and reopening. GDM
  screen does not appear to login, just see contents of the X session
  before i closed the lid.  mouse moves and hardware buttons (mute, caps
  lock etc) are responsive with LEDs. Have to hard reboot to login and
  use computer

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  535.129.03  Thu Oct 19 
18:56:32 UTC 2023
   GCC version:
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Nov  4 15:33:14 2023
  DistUpgraded: 2023-11-02 15:19:38,871 DEBUG 'libkf5itemviews5' scheduled for 
remove but not safe to remove, skipping
  DistroCodename: mantic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Within the last few days
  GraphicsCard:
   Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (prog-if 
00 [VGA controller])
 Subsystem: Lenovo CoffeeLake-H GT2 [UHD Graphics 630] [17aa:229f]
   NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q] [10de:1f91] (rev 
a1) (prog-if 00 [VGA controller])
 Subsystem: Lenovo TU117M [GeForce GTX 1650 Mobile / Max-Q] [17aa:229f]
  InstallationDate: Installed on 2023-05-24 (164 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230417)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic 
root=UUID=45e4e3f8-045a-4651-bd83-6087eca44175 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to mantic on 2023-11-02 (2 days ago)
  dmi.bios.date: 09/19/2023
  dmi.bios.release: 1.48
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2OET61W (1.48 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QV00BRUK
  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.22
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2OET61W(1.48):bd09/19/2023:br1.48:efr1.22:svnLENOVO:pn20QV00BRUK:pvrThinkPadX1Extreme2nd:rvnLENOVO:rn20QV00BRUK:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20QV_BU_Think_FM_ThinkPadX1Extreme2nd:
  dmi.product.family: ThinkPad X1 Extreme 2nd
  dmi.product.name: 20QV00BRUK
  dmi.product.sku: LENOVO_MT_20QV_BU_Think_FM_ThinkPad X1 Extreme 2nd
  dmi.product.version: ThinkPad X1 Extreme 2nd
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.115-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~23.04.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Desktop-packages] [Bug 2047008] Re: [SRU] Add Telit FN990 compositions

Hello Laider, or anyone else affected,

Accepted modemmanager into jammy-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/modemmanager/1.20.0-1~ubuntu22.04.3
in a few hours, and then in the -proposed repository.

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

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

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

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

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

** Tags added: verification-needed verification-needed-jammy

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

Title:
  [SRU] Add Telit FN990 compositions

Status in OEM Priority Project:
  New
Status in modemmanager package in Ubuntu:
  Fix Released
Status in modemmanager source package in Jammy:
  Fix Committed

Bug description:
  [SRU] Add Telit FN990 compositions

  [ Impact ]

  The modemmanager v1.20.0 doesn't have Telit FN990 compositions.
  It works with compatibility mode.
  (lp: #2046699)

  [ Test Plan ]

  Under Jammy environment,
  check modemmanager can identify Telit FN990 modem correctly.

  [ Where problems could occur ]

  The Telit FN990 compositions is upstreamed to modemmanager v1.20.6
  
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/b68a1bb8474991a72cf988e8e24ba6549f1cf9c2

  Noble and Mantic already working with modemmanager v1.20.6.
  The target platform modem function works well on Mantic.

  The change parts just only add VID/PIDs for Telit's FN990 modems under
  the Telit plugin.

  [ Other Info ]

  N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2047008/+subscriptions


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

[Desktop-packages] [Bug 1958019]

2024-01-05 Thread florentinski

```
aplay -l

...
card 2: Generic_1 [HD-Audio Generic], device 0: ALC287 Analog [ALC287 Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
```

According to laptop's specs:
https://psref.lenovo.com/Product/Legion_Slim_7_16APH8?tab=spec

Audio Chip
High Definition (HD) Audio, Realtek® ALC3306 codec

It seems like Linux reports ALC287 instead of ALC3306. According to a
reddit post, ALC3306 is just a name change of ALC287.

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

Title:
  [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No
  sound at all

Status in sound-2.6 (alsa-kernel):
  Confirmed
Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by
  internal speakers, but it work by headphones connected to standard
  jack aux.

  uname -r
  5.11.0-44-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-44-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 15 15:10:53 2022
  InstallationDate: Installed on 2021-10-11 (96 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio 
Generic
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/08/2021
  dmi.bios.release: 1.49
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GKCN49WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion 7 16ACHg6
  dmi.ec.firmware.release: 1.49
  dmi.modalias: 
dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6:
  dmi.product.family: Legion 7 16ACHg6
  dmi.product.name: 82N6
  dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6
  dmi.product.version: Legion 7 16ACHg6
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/sound-2.6/+bug/1958019/+subscriptions


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

[Desktop-packages] [Bug 1958019]

2024-01-05 Thread florentinski

Same no audio problem on this laptop: Legion Slim 7 16APH8
https://psref.lenovo.com/Detail/Legion/Legion_Slim_7_16APH8?M=82Y4001UMZ

OS: Fedora 39
Kernel: 6.6.9-200.fc39.x86_64

alsa-info.sh
http://alsa-project.org/db/?f=dc0275d1836faea7ddf81a990b07e4a86313bf9a

Bios:
  Version: M1CN36WW
  Release Date: 09/21/2023

cat /sys/class/sound/hwC1D0/subsystem_id
0xaa0100

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

Title:
  [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No
  sound at all

Status in sound-2.6 (alsa-kernel):
  Confirmed
Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by
  internal speakers, but it work by headphones connected to standard
  jack aux.

  uname -r
  5.11.0-44-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-44-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 15 15:10:53 2022
  InstallationDate: Installed on 2021-10-11 (96 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio 
Generic
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/08/2021
  dmi.bios.release: 1.49
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GKCN49WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion 7 16ACHg6
  dmi.ec.firmware.release: 1.49
  dmi.modalias: 
dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6:
  dmi.product.family: Legion 7 16ACHg6
  dmi.product.name: 82N6
  dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6
  dmi.product.version: Legion 7 16ACHg6
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/sound-2.6/+bug/1958019/+subscriptions


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

[Desktop-packages] [Bug 2046360] Re: Heavy stuttering in Firefox with mutter 45.1/45.2

Hello Daniel, or anyone else affected,

Accepted mutter into mantic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/mutter/45.2-0ubuntu3
in a few hours, and then in the -proposed repository.

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

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

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

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

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

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

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

Title:
  Heavy stuttering in Firefox with mutter 45.1/45.2

Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Mantic:
  Fix Committed

Bug description:
  [ Impact ]

  There is heavy stuttering visible in Firefox with mutter 45.1/45.2
  when kinetic scrolling a non-animated web page with a touchpad. This
  is a regression introduced upstream in mutter 45.1 (8f27ebf8).

  [ Test Plan ]

  0. Find a laptop with a touchpad.
  1. Open a simple web page like a Wikipedia page in Firefox.
  2. Use two fingers on the touchpad to fling it so it continues scrolling.

  Expect: The scrolling proceeds and slows perfectly smoothly.

  [ Where problems could occur ]

  Anywhere in frame scheduling (visual smoothness), since that is the
  code affected.

  [ Other Info ]

  The bug was introduced upstream in 45.1 by
  
https://gitlab.gnome.org/GNOME/mutter/-/commit/8f27ebf87eee6057992a90560d4118ab7bdf138d
  but since it only hurts the triple buffering patch, that's where it
  has been fixed:

  
https://gitlab.gnome.org/Community/Ubuntu/mutter/-/commit/0b896518b2028d9c4d6ea44806d093fd33793689
  
https://gitlab.gnome.org/Community/Ubuntu/mutter/-/commits/triple-buffering-v4-45

  [ Workaround ]

  In /etc/environment:

    MUTTER_DEBUG_TRIPLE_BUFFERING=always

  or "never" also works. Just not "auto" because the bug is in auto mode
  (the default).

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


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

[Desktop-packages] [Bug 2043000] Re: Update mutter to 45.2

Hello Jeremy, or anyone else affected,

Accepted mutter into mantic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/mutter/45.2-0ubuntu3
in a few hours, and then in the -proposed repository.

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

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

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

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

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

** Tags added: verification-needed verification-needed-mantic

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

Title:
  Update mutter to 45.2

Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Mantic:
  Fix Committed

Bug description:
  Impact
  --
  There is a new bugfix release in the stable 45 series.
  https://gitlab.gnome.org/GNOME/mutter/-/blob/45.2/NEWS

  Test Case
  -
  Complete the test case from

  https://wiki.ubuntu.com/DesktopTeam/TestPlans/Mutter

  What Could Go Wrong
  ---
  Mutter is an essential component of the default Ubuntu desktop and for the 
desktop used by Ubuntu Budgie.

  A severe enough bug could mean that people are unable to use their
  desktop version of Ubuntu.

  Smaller bugs could interrupt people's workflows.

  mutter is part of GNOME Core and is included in the GNOME micro
  release exception

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  Other Info
  --
  This update landed in mantic-updates just before the end of year holidays but 
was reverted with 
https://launchpad.net/ubuntu/+source/mutter/45.2-0ubuntu2~really45.0

  Compared to mutter 45.2-0ubuntu1, this changes or adds about 3 lines
  of code in the triple buffering patch to avoid the regression reported
  in LP: #2046360

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


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

[Desktop-packages] [Bug 2035076] Re: Can't enter capital accented letters with Caps Lock on Wayland

Hello Jeremie, or anyone else affected,

Accepted mutter into mantic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/mutter/45.2-0ubuntu3
in a few hours, and then in the -proposed repository.

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

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

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

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

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

** Tags added: verification-needed verification-needed-mantic

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

Title:
  Can't enter capital accented letters with Caps Lock on Wayland

Status in Mutter:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Mantic:
  Fix Committed
Status in mutter package in Fedora:
  Unknown

Bug description:
  Impact
  --
  Capital accented letters can't be entered using CAPS LOCK in the Wayland 
session

  Test Case
  -
  Open a terminal and install basic French support:
  sudo apt install language-pack-gnome-fr

  Open the Settings app. In the sidebar, click Keyboard
  Click +, choose French (France), then choose the French (AZERTY) keyboard
  Close the Settings app
  In the top right of the screen, click en and switch the keyboard layout to 
French (AZERTY)
  In the text editor, type é (this is the number 2 key on a US English 
keyboard).
  Now, press the Caps Lock key to enable Caps Lock.
  Press the same key. You should get É

  What Could Go Wrong
  ---
  This fix is included in mutter 45.2 so see the master bug for this upstream 
update: LP: #2043000

  Original bug report
  ---
  Most programs don't recognize Italian accented capital letters.
  When "Caps Lock" is on àèìòù should be written as ÀÈÌÒÙ... but for some 
reasons they are not capitalized.
  I've noticed that everything works fine using the Live session which still 
uses X11 session.

  It looks there's no problem with programs that use xwayland like Gimp
  and MarkText.

  WORKAROUND
  ===
  In "Settings -> Keyboard" it's possible to set a "compose key".
  For example I've selected the [Super left] key. If I want to compose È I 
press and immediately release each key:
  [Super left] + [E] + [Alt Gr] + [']

  If you want É:
  [Super left] + [E] + [']

  Do the same for the other vowels.
  ===

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: gnome-text-editor 45~beta-1
  ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
  Uname: Linux 6.3.0-7-generic x86_64
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 11 11:48:41 2023
  InstallationDate: Installed on 2023-09-07 (4 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230906.3)
  ProcEnviron:
   LANG=it_IT.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: gnome-text-editor
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 2043027] Re: Wacom Intuos S stop working after upgrading to Ubuntu 23.10

Hello Gonzalo, or anyone else affected,

Accepted mutter into mantic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/mutter/45.2-0ubuntu3
in a few hours, and then in the -proposed repository.

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

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

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

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

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

** Tags added: verification-needed verification-needed-mantic

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

Title:
  Wacom Intuos S stop working after upgrading to Ubuntu 23.10

Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Mantic:
  Fix Committed

Bug description:
  Impact
  --
  Clicking does not work correctly with Wacom tablets in the Ubuntu/GNOME X11 
sessions

  Test Case
  -
  One of the people affected by this issue will verify whether their Wacom 
tablet is working noticably better with the upgraded Mutter packages

  What Could Go Wrong
  ---
  The fix for this issue is included in upstream's mutter 45.2 release so 
please see bug 2043000 as the master bug for this upgrade

  Original Bug Report
  ---
  Tablet seems to work until I open Krita (as I could read on Internet, it may 
be related with Qt Apps).

  When Krita is open, mouse movement works ok with the tablet, but when
  it comes to click action it doesn't work and any further action with
  mouse is not captured (even outside Krita!).

  To regain control of the mouse I have to Alt+Tab and then I can click
  again.

  Some details that may be handy:
  - I've got two monitors
  - Maybe Qt apps related
  - My graphic card is nVidia GTX 1060 6Gb, driver used nvidia-driver-535

  Thanks for your effort. I love Ubuntu!

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..06.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  535.129.03  Thu Oct 19 
18:56:32 UTC 2023
   GCC version:
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov  8 17:20:34 2023
  DistUpgraded: 2023-11-08 00:54:28,961 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: mantic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia/535.129.03, 6.2.0-36-generic, x86_64: installed (WARNING! Diff 
between built and installed module!) (WARNING! Diff between built and installed 
module!) (WARNING! Diff between built and installed module!) (WARNING! Diff 
between built and installed module!) (WARNING! Diff between built and installed 
module!)
   nvidia/535.129.03, 6.5.0-10-generic, x86_64: installed (WARNING! Diff 
between built and installed module!) (WARNING! Diff between built and installed 
module!) (WARNING! Diff between built and installed module!) (WARNING! Diff 
between built and installed module!) (WARNING! Diff between built and installed 
module!)
   virtualbox/7.0.10, 6.2.0-36-generic, x86_64: installed
   virtualbox/7.0.10, 6.5.0-10-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] (rev a1) 
(prog-if 00 [VGA controller])
     Subsystem: ZOTAC International (MCO) Ltd. GP106

[Desktop-packages] [Bug 2007702] Re: [SRU] Deb version numbering is misleading

One of the possible impacts of bumping the version like this is that if
a user has a local deb of chromium-browser installed that is higher than
the current version, the new epoch will cause them to be upgraded to the
transitional package that they had already opted out of.

This should be called out and the pros and cons weighed in the bug
description ("Where problems can occur" / "Regression potential")

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

Title:
  [SRU] Deb version numbering is misleading

Status in chromium-browser package in Ubuntu:
  Fix Released
Status in chromium-browser source package in Focal:
  In Progress
Status in chromium-browser source package in Jammy:
  In Progress
Status in chromium-browser source package in Lunar:
  In Progress
Status in chromium-browser source package in Mantic:
  Incomplete

Bug description:
  [Impact]
  For Ubuntu >= Focal the transitional debs are frozen at the version number 
1:85...

  This might make one think[1][2] that it will install a critically
  outdated Chromium while it does not, because it installs the snap.

  [Test plan]

  Install the package and confirm the version change with e.g.

    dpkg -l | grep '^ii *chromium-browser *2:1snap1-0ubuntu1'

  [Regression potential]

  If the version were incorrectly constructed the deb build could fail.

  [1] 
https://answers.launchpad.net/ubuntu/+source/chromium-browser/+question/702591
  [2] https://askubuntu.com/q/1420925

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


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

[Desktop-packages] [Bug 2007702] Re: [SRU] Deb version numbering is misleading

One of the possible impacts of bumping the version like this is that if
a user has a local deb of chromium-browser installed that is higher than
the current version, the new epoch will cause them to be upgraded to the
transitional package that they had already opted out of.

This should be called out and the pros and cons weighed in the bug
description ("Where problems can occur" / "Regression potential")

** Changed in: chromium-browser (Ubuntu Mantic)
   Status: In Progress => Incomplete

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

Title:
  [SRU] Deb version numbering is misleading

Status in chromium-browser package in Ubuntu:
  Fix Released
Status in chromium-browser source package in Focal:
  In Progress
Status in chromium-browser source package in Jammy:
  In Progress
Status in chromium-browser source package in Lunar:
  In Progress
Status in chromium-browser source package in Mantic:
  Incomplete

Bug description:
  [Impact]
  For Ubuntu >= Focal the transitional debs are frozen at the version number 
1:85...

  This might make one think[1][2] that it will install a critically
  outdated Chromium while it does not, because it installs the snap.

  [Test plan]

  Install the package and confirm the version change with e.g.

    dpkg -l | grep '^ii *chromium-browser *2:1snap1-0ubuntu1'

  [Regression potential]

  If the version were incorrectly constructed the deb build could fail.

  [1] 
https://answers.launchpad.net/ubuntu/+source/chromium-browser/+question/702591
  [2] https://askubuntu.com/q/1420925

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


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

[Desktop-packages] [Bug 2048390] [NEW] Desktop icons doesn't support accessibility (specifically Orca)

Public bug reported:

[ Impact ]

Currently, the Desktop Icons NG (DING) extension included in Ubuntu
doesn't support integration with screen readers like Orca. This is a
disadvantage for visually impaired users.

Since DING is implemented as a classic GTK application, it should be
easy to wire it up to make use of the accessibility functions already
available thanks to the ATK library. A patch for that has been recently
uploaded to upstream, after a fix for this was requested by an user.

The patch takes advantage of the already implemented keyboard
navigation, and just makes these little changes:

* sets a readable accessible description for the Desktop Icons window
(because the application uses the invisible title bar to communicate
with the extension, thus it contains just "odd characters and numbers")

* sets an accessible description for each icon with the type and the
visible name of the file, and marks each icon as focusable

* when an icon is marked as selected, it gives the focus to it, thus
triggering the screen reader to read the accessible description

Also, the code for keyboard navigation is moved from the "key-press"
event to the "key-release" event, because that's the event used by the
accessibility subsystem, and not doing this results in an incorrect icon
being read by it.

[ Test plan ]

* Enable the Orca screen reader by pressing Mod+Alt+S. A voice will say
"Screen reader enabled" (or a similar, translated message).

* Click on the desktop to give the focus to it.

* Press the arrow keys to navigate with the keyboard through the icons.
Only one icon should be highlighted, and it should change when the
arrows are moved.

* After the test, the screen reader can be disabled by pressing the same
keys combination.

Expected results:

The screen reader should say the type and name of the selected icon,
every time the arrow keys are pressed to change the selected icon.

Current results:

The screen reader remains silent while navigating with the keyboard.

[ Where problems could occur ]

A change in the way GTK manages the focus could result in the keyboard
navigation to work incorrectly.

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

** Patch added: "Patch to add accessibility support"

https://bugs.launchpad.net/bugs/2048390/+attachment/5736866/+files/add-accessibility-support.diff

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

Title:
Desktop icons doesn't support accessibility (specifically Orca)

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

Bug description:
[ Impact ]

Currently, the Desktop Icons NG (DING) extension included in Ubuntu
doesn't support integration with screen readers like Orca. This is a
disadvantage for visually impaired users.

Since DING is implemented as a classic GTK application, it should be
easy to wire it up to make use of the accessibility functions already
available thanks to the ATK library. A patch for that has been
recently uploaded to upstream, after a fix for this was requested by
an user.

The patch takes advantage of the already implemented keyboard
navigation, and just makes these little changes:

* sets an accessible description for each icon with the type and the
visible name of the file, and marks each icon as focusable

* when an icon is marked as selected, it gives the focus to it, thus
triggering the screen reader to read the accessible description

[ Test plan ]

* Enable the Orca screen reader by pressing Mod+Alt+S. A voice will
say "Screen reader enabled" (or a similar, translated message).

* Click on the desktop to give the focus to it.

* Press the arrow keys to navigate with the keyboard through the
icons. Only one icon should be highlighted, and it should change when
the arrows are moved.

* After the test, the screen reader can be disabled by pressing the
same keys combination.

Expected results:

The screen reader should say the type and name of the selected icon,
every time the arrow keys are pressed to change the selected icon.

Current results:

The screen reader remains silent while navigating with the keyboard.

[ Where problems could occur ]

A change in the way GTK manages the focus could result in the keyboard
navigation to work incorrectly.

To manage notifications

[Desktop-packages] [Bug 1971168] Re: [snap] Files on local network shares are not opened / written

Oh, you mean if it will be backported to LTS! I'm not sure... I'll check
it.

(sorry, I read the numbers wrong and interpreted 24.04)

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

Title:
  [snap] Files on local network shares are not opened / written

Status in Mozilla Firefox:
  Confirmed
Status in firefox package in Ubuntu:
  Triaged
Status in xdg-desktop-portal package in Ubuntu:
  Triaged
Status in xdg-desktop-portal-gnome package in Ubuntu:
  Fix Released
Status in xdg-desktop-portal-gnome source package in Jammy:
  Triaged
Status in xdg-desktop-portal-gnome source package in Lunar:
  Triaged

Bug description:
  [ Impact ]

  When the user is running a containerized application (like the snapped
  Firefox or Chromium), and tries to save a document, the xdg-desktop-
  portal-gnome backend does show remote drives (like SMB or SFTP ones),
  and allows to choose them, but then the save operation fails.

  The previous backend, xdg-desktop-portal-gtk, did work fine in these
  cases, because it returned the local path that corresponded to the
  local file exported by Gvfs using FUSE, so this behaviour is not only
  a serious bug, but also a regression.

  [ Test plan]
  Steps to reproduce:

  1. Run Firefox as a Snap package in Ubuntu 22.04
  2. Have a SMB file server available where the network shares can be mounted 
just by clicking on the share in Nautilus file manager (smb:// protocol, 
usually mounted dynamically via `/var/run/user/.../gvfs/...`)
  3. Have one such share mounted and writable
  4. Open any website containing images in Firefox
  5. Right-click on an image and select "Save Image As..."
  6. In the file save dialog, navigate to the mounted share
  7. Assert content of network share is visible and browsable from within the 
save dialog
  8. Select "Save" at any folder in the network share

  Actual behavior:

  * File is not saved to selected network share location
  * No download entry is created
  * No error is shown

  Expected behavior:

  * File is saved to selected network share location
  * No error is shown

  [ Where problems could occur ]

  - If the remote drives aren't exported as local files by Gvfs using
  FUSE, the patch won't work and the behaviour will be the same than
  now.

  - Any hidden  bug in g_file_get_path() when managing remote drives
  could be triggered by this patch.

  [ Additional information ]

  * When saving to a folder on the local machine instead, saving works 
correctly as expected
  * In contrast to files, new folders that are created from within the save 
dialog are saved correctly on the network share
  * Similar situation when trying to open a file with Ctrl + O on a network 
share from Firefox / Chromium. After double-clicking e.g. an image file in the 
file dialog, the file dialog closes but nothing happens otherwise. Opening an 
image on a local folder works fine.

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


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

[Desktop-packages] [Bug 1833322] Re: Consider removing irqbalance from default install on desktop images

2024-01-05 Thread Doug Smythies

Thank you for your incredibly thorough analysis of this. Since finding
this via bug 2046470, I have tried, without success, to create a test to
show any difference in performance or power or whatever between
irqbalance enabled/disabled on my Ubuntu 20.04 test server.

While my vote carries little weight here, I give it anyhow:

A) Change it from an opt-out to an opt-in and remove the dependency
   from ubuntu-standard

Mainly because, and from my own investigation, I agree with:

> To me this seems to be a perfect case for a few special images/deployments
> known to match the workload profile that needs this to enable it.
> It is also more likely that a professional admin of such a large scale machine
> (or cluster thereof) can make the opt-in decision and evaluation better than
> expecting every user of Ubuntu to think about an opt-out.

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

Title:
  Consider removing irqbalance from default install on desktop images

Status in irqbalance package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  as per https://github.com/pop-os/default-settings/issues/60

  Distribution (run cat /etc/os-release):

  $ cat /etc/os-release
  NAME="Pop!_OS"
  VERSION="19.04"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Pop!_OS 19.04"
  VERSION_ID="19.04"
  HOME_URL="https://system76.com/pop;
  SUPPORT_URL="http://support.system76.com;
  BUG_REPORT_URL="https://github.com/pop-os/pop/issues;
  PRIVACY_POLICY_URL="https://system76.com/privacy;
  VERSION_CODENAME=disco
  UBUNTU_CODENAME=disco

  Related Application and/or Package Version (run apt policy $PACKAGE
  NAME):

  $ apt policy irqbalance
  irqbalance:
  Installed: 1.5.0-3ubuntu1
  Candidate: 1.5.0-3ubuntu1
  Version table:
  *** 1.5.0-3ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages
  100 /var/lib/dpkg/status

  $ apt rdepends irqbalance
  irqbalance
  Reverse Depends:
  Recommends: ubuntu-standard
  gce-compute-image-packages

  Issue/Bug Description:

  as per konkor/cpufreq#48 and
  http://konkor.github.io/cpufreq/faq/#irqbalance-detected

  irqbalance is technically not needed on desktop systems (supposedly it
  is mainly for servers), and may actually reduce performance and power
  savings. It appears to provide benefits only to server environments
  that have relatively-constant loading. If it is truly a server-
  oriented package, then it shouldn't be installed by default on a
  desktop/laptop system and shouldn't be included in desktop OS images.

  Steps to reproduce (if you know):

  This is potentially an issue with all default installs.

  Expected behavior:

  n/a

  Other Notes:

  I can safely remove it via "sudo apt purge irqbalance" without any
  apparent adverse side-effects. If someone is running a situation where
  they need it, then they always have the option of installing it from
  the repositories.

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


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

[Desktop-packages] [Bug 1968513] Re: GNOME login fails to stay in the overview if DING is enabled

After checking that extension, I think that I can use the same trick for
DING.

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

Title:
  GNOME login fails to stay in the overview if DING is enabled

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

Bug description:
  Ubuntu 22.04 (April 9 daily, latest)

  If you either disable the ubuntu-dock or remove it all together. On
  every login after that, the Activities window appears for just a few
  seconds. After those few seconds the Activities window automatically
  closes, which exposes the desktop.

  What I expected to happen is no Activity window to appear on login. I
  just want the desktop to appear, no dock, no Activities. More or less,
  I'm going for a "kiosk" type of desktop.

  Thanks for your time!

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell-extension-ubuntu-dock 72~ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 10 19:42:00 2022
  InstallationDate: Installed on 2022-04-11 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220409)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1971168] Re: [snap] Files on local network shares are not opened / written

2024-01-05 Thread Miguel

Soo no fix to 22.04?

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

Title:
  [snap] Files on local network shares are not opened / written

Status in Mozilla Firefox:
  Confirmed
Status in firefox package in Ubuntu:
  Triaged
Status in xdg-desktop-portal package in Ubuntu:
  Triaged
Status in xdg-desktop-portal-gnome package in Ubuntu:
  Fix Released
Status in xdg-desktop-portal-gnome source package in Jammy:
  Triaged
Status in xdg-desktop-portal-gnome source package in Lunar:
  Triaged

Bug description:
  [ Impact ]

  When the user is running a containerized application (like the snapped
  Firefox or Chromium), and tries to save a document, the xdg-desktop-
  portal-gnome backend does show remote drives (like SMB or SFTP ones),
  and allows to choose them, but then the save operation fails.

  The previous backend, xdg-desktop-portal-gtk, did work fine in these
  cases, because it returned the local path that corresponded to the
  local file exported by Gvfs using FUSE, so this behaviour is not only
  a serious bug, but also a regression.

  [ Test plan]
  Steps to reproduce:

  1. Run Firefox as a Snap package in Ubuntu 22.04
  2. Have a SMB file server available where the network shares can be mounted 
just by clicking on the share in Nautilus file manager (smb:// protocol, 
usually mounted dynamically via `/var/run/user/.../gvfs/...`)
  3. Have one such share mounted and writable
  4. Open any website containing images in Firefox
  5. Right-click on an image and select "Save Image As..."
  6. In the file save dialog, navigate to the mounted share
  7. Assert content of network share is visible and browsable from within the 
save dialog
  8. Select "Save" at any folder in the network share

  Actual behavior:

  * File is not saved to selected network share location
  * No download entry is created
  * No error is shown

  Expected behavior:

  * File is saved to selected network share location
  * No error is shown

  [ Where problems could occur ]

  - If the remote drives aren't exported as local files by Gvfs using
  FUSE, the patch won't work and the behaviour will be the same than
  now.

  - Any hidden  bug in g_file_get_path() when managing remote drives
  could be triggered by this patch.

  [ Additional information ]

  * When saving to a folder on the local machine instead, saving works 
correctly as expected
  * In contrast to files, new folders that are created from within the save 
dialog are saved correctly on the network share
  * Similar situation when trying to open a file with Ctrl + O on a network 
share from Firefox / Chromium. After double-clicking e.g. an image file in the 
file dialog, the file dialog closes but nothing happens otherwise. Opening an 
image on a local folder works fine.

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


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

[Desktop-packages] [Bug 1007924] Re: pm-utils uses wrong interface for NetworkManager hook (should be org.freedesktop.NetworkManager.Sleep)

** Changed in: pm-utils (Debian)
   Status: Fix Released => Confirmed

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

Title:
  pm-utils uses wrong interface for NetworkManager hook (should be
  org.freedesktop.NetworkManager.Sleep)

Status in pm-utils:
  Won't Fix
Status in pm-utils package in Ubuntu:
  Triaged
Status in pm-utils package in Debian:
  Confirmed

Bug description:
  While looking at /var/log/pm-suspend.log I have noticed that the
  NetworkManager hooks fail:

Running hook /usr/lib/pm-utils/sleep.d/55NetworkManager suspend 
suspend_hybrid:
Having NetworkManager put all interaces to sleep...Failed.

Running hook /usr/lib/pm-utils/sleep.d/55NetworkManager resume 
suspend_hybrid:
Having NetworkManager wake interfaces back up...Failed.

  Looking at the script is uses org.freedesktop.NetworkManager.sleep and
  org.freedesktop.NetworkManager.wake.

  Calling this results in errors like this:
% sudo dbus-send --print-reply --system 
--dest=org.freedesktop.NetworkManager /org/freedesktop/NetworkManager 
org.freedesktop.NetworkManager.sleep
Error org.freedesktop.DBus.Error.UnknownMethod: Method "sleep" with 
signature "" on interface "org.freedesktop.NetworkManager" doesn't exist

  According to the documentation [1], the interface is different / has
  changed.

  The correct usage would be to call
  org.freedesktop.NetworkManager.Sleep with a boolean value, like:

  sudo dbus-send --print-reply --system
  --dest=org.freedesktop.NetworkManager /org/freedesktop/NetworkManager
  org.freedesktop.NetworkManager.Sleep boolean:true


  1: 
http://projects.gnome.org/NetworkManager/developers/api/09/spec.htmlorg.freedesktop.NetworkManager.Sleep

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: pm-utils 1.4.1-9
  ProcVersionSignature: Ubuntu 3.2.0-25.40-generic 3.2.18
  Uname: Linux 3.2.0-25-generic x86_64
  ApportVersion: 2.0.1-0ubuntu8
  Architecture: amd64
  Date: Sat Jun  2 21:36:40 2012
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  PackageArchitecture: all
  SourcePackage: pm-utils
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/pm-utils/+bug/1007924/+subscriptions


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

[Desktop-packages] [Bug 1950703] Re: Keyboard input does't work in several apps with iBus running

2024-01-05 Thread H

After today's package upgrade and a reboot, I can now type into Firefox
again without having to kill iBus first. 

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

Title:
  Keyboard input does't work in several apps with iBus running

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

Bug description:
  If installed through Snap and with iBus running the keyboard doesn't work in 
Standard Notes, XMind and Chromium apps on Manjaro 21.1. Killing iBus fixes the 
issue.
  The keyboard works in Visual Studio, however
  

  
  snap 2.51.3-2
  snapd 2.51.3-2
  series 16
  manjaro -
  kernel 5.10.70-1-MANJARO
  
  
  
   sudo snap connections chromium

  Interface PlugSlot
 Notes
  audio-playbackchromium:audio-playback 
:audio-playback  -
  audio-record  chromium:audio-record   
:audio-record-
  bluez chromium:bluez  :bluez  
 -
  browser-support   chromium:browser-sandbox
:browser-support -
  camerachromium:camera :camera 
 -
  content[gnome-3-28-1804]  chromium:gnome-3-28-1804
gnome-3-28-1804:gnome-3-28-1804  -
  content[gtk-3-themes] chromium:gtk-3-themes   
gtk-common-themes:gtk-3-themes   -
  content[icon-themes]  chromium:icon-themes
gtk-common-themes:icon-themes-
  content[sound-themes] chromium:sound-themes   
gtk-common-themes:sound-themes   -
  cups-control  chromium:cups-control   
:cups-control-
  desktop   chromium:desktop:desktop
 -
  desktop-legacychromium:desktop-legacy 
:desktop-legacy  -
  gsettings chromium:gsettings  :gsettings  
 -
  home  chromium:home   :home   
 -
  joystick  chromium:joystick   :joystick   
 -
  mount-observe chromium:mount-observe  -   
 -
  mpris -   
chromium:mpris   -
  network   chromium:network:network
 -
  network-bind  chromium:network-bind   
:network-bind-
  network-manager   chromium:network-manager-   
 -
  openglchromium:opengl :opengl 
 -
  password-manager-service  chromium:password-manager-service   -   
 -
  personal-fileschromium:chromium-config
:personal-files  -
  pulseaudiochromium:pulseaudio -   
 -
  raw-usb   chromium:raw-usb-   
 -
  removable-media   chromium:removable-media
:removable-media -
  screen-inhibit-controlchromium:screen-inhibit-control 
:screen-inhibit-control  -
  system-files  chromium:etc-chromium-browser-policies  
:system-files-
  system-packages-doc   chromium:system-packages-doc
:system-packages-doc -
  u2f-devices   chromium:u2f-devices
:u2f-devices -
  unity7chromium:unity7 :unity7 
 -
  upower-observechromium:upower-observe 
:upower-observe  -
  wayland   chromium:wayland:wayland
 -
  x11   chromium:x11:x11
 -


  
  sudo snap connections standard-notes

  Interface Plug Slot   
  Notes
  audio-playbackstandard-notes:audio-playback
:audio-playback  -
  browser-support   standard-notes:browser-support   
:browser-support -
  content[gnome-3-28-1804]  standard-notes:gnome-3-28-1804   
gnome-3-28-1804:gnome-3-28-1804  -
  content[gtk-3-themes] standard-notes:gtk-3-themes

[Desktop-packages] [Bug 1971168] Re: [snap] Files on local network shares are not opened / written

I have to check it, but probably the reason is that it still is using
the current version of gnome shell, so it won't be fixed until Gnome 46
is added to the repositories.

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

Title:
  [snap] Files on local network shares are not opened / written

Status in Mozilla Firefox:
  Confirmed
Status in firefox package in Ubuntu:
  Triaged
Status in xdg-desktop-portal package in Ubuntu:
  Triaged
Status in xdg-desktop-portal-gnome package in Ubuntu:
  Fix Released
Status in xdg-desktop-portal-gnome source package in Jammy:
  Triaged
Status in xdg-desktop-portal-gnome source package in Lunar:
  Triaged

Bug description:
  [ Impact ]

  When the user is running a containerized application (like the snapped
  Firefox or Chromium), and tries to save a document, the xdg-desktop-
  portal-gnome backend does show remote drives (like SMB or SFTP ones),
  and allows to choose them, but then the save operation fails.

  The previous backend, xdg-desktop-portal-gtk, did work fine in these
  cases, because it returned the local path that corresponded to the
  local file exported by Gvfs using FUSE, so this behaviour is not only
  a serious bug, but also a regression.

  [ Test plan]
  Steps to reproduce:

  1. Run Firefox as a Snap package in Ubuntu 22.04
  2. Have a SMB file server available where the network shares can be mounted 
just by clicking on the share in Nautilus file manager (smb:// protocol, 
usually mounted dynamically via `/var/run/user/.../gvfs/...`)
  3. Have one such share mounted and writable
  4. Open any website containing images in Firefox
  5. Right-click on an image and select "Save Image As..."
  6. In the file save dialog, navigate to the mounted share
  7. Assert content of network share is visible and browsable from within the 
save dialog
  8. Select "Save" at any folder in the network share

  Actual behavior:

  * File is not saved to selected network share location
  * No download entry is created
  * No error is shown

  Expected behavior:

  * File is saved to selected network share location
  * No error is shown

  [ Where problems could occur ]

  - If the remote drives aren't exported as local files by Gvfs using
  FUSE, the patch won't work and the behaviour will be the same than
  now.

  - Any hidden  bug in g_file_get_path() when managing remote drives
  could be triggered by this patch.

  [ Additional information ]

  * When saving to a folder on the local machine instead, saving works 
correctly as expected
  * In contrast to files, new folders that are created from within the save 
dialog are saved correctly on the network share
  * Similar situation when trying to open a file with Ctrl + O on a network 
share from Firefox / Chromium. After double-clicking e.g. an image file in the 
file dialog, the file dialog closes but nothing happens otherwise. Opening an 
image on a local folder works fine.

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


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

[Desktop-packages] [Bug 2047356] Re: gvfs-disks2-volume-monitor and gsd-housekeeping processes can eat a lot of CPU with k3s workload

2024-01-05 Thread Mossroy

I have the same behavior with Ubuntu 23.10.1 (with all current updates),
using latest stable k3s (v1.28.5+k3s1)

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

Title:
  gvfs-disks2-volume-monitor and gsd-housekeeping processes can eat a
  lot of CPU with k3s workload

Status in gvfs package in Ubuntu:
  New

Bug description:
  On Ubuntu 22.04.3 desktop, when running a k3s workload that uses volumes 
(using default local-path storageClass), process gvfs-disks2-volume-monitor can 
take around 100% of one CPU core, and process gsd-housekeeping around 25% of 
one CPU core.
  Even if the actual k3s workload is idle.

  Steps To Reproduce:

  - Use or install a desktop Ubuntu 22.04.3 (with default settings)
  - Install K3s on it (current version is "v1.28.4+k3s2"), with default 
settings: "curl -sfL https://get.k3s.io | sh -"
  - Deploy k8s manifests with many volumes, like 
https://gitlab.com/-/snippets/3634487: "wget 
https://gitlab.com/-/snippets/3634487/raw/main/deployment-with-many-volumes.yaml
 && sudo k3s kubectl apply -f deployment-with-many-volumes.yaml"
  - Check CPU consumption on the host, with top, gnome-system-monitor or 
anything else

  Expected behavior:
  Gnome desktop tools should not interfere with k3s.

  Actual behavior:
  Processes gvfs-disks2-volume-monitor and gsd-housekeeping consume a lot of 
CPU, at least at provisioning time.
  Same CPU consumption if you then remove the workload ("sudo k3s kubectl 
delete -f deployment-wit-many-volumes.yaml"), until the PVs are deleted by k3s.
  I have other workloads (with data in PVs) where this CPU consumption is 
always there, when the workload is running (even if idle)

  Additional context:
  The symptoms are very similar to https://github.com/k3s-io/k3s/issues/522, 
but the workaround of comment 
https://github.com/k3s-io/k3s/issues/522#issuecomment-811737023 (adding a udev 
rule to ignore some loopback devices) does not help.

  Executing "systemctl stop --user gvfs-udisks2-volume-monitor" can be a
  temporary workaround

  Technical details:
  k3s uses containerd to run containers. The local-path storageClass mounts 
local volumes (physically stored in /var/lib/rancher/k3s/storage subfolders) in 
these containers.
  I suppose gnome applications try to scan these mount points. In this case, 
the solution might be to make them ignore them, a bit like 
https://github.com/moby/moby/blob/master/contrib/udev/80-docker.rules does for 
docker

  NB: Was initially reported on
  https://github.com/k3s-io/k3s/issues/9093

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


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

[Desktop-packages] [Bug 1971168] Re: [snap] Files on local network shares are not opened / written

2024-01-05 Thread Miguel

It don't work, you can select a file but it don´t upload

** Attachment added: "Captura de ecrã de 2024-01-05 12-32-13.png"
   
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1971168/+attachment/5736847/+files/Captura%20de%20ecr%C3%A3%20de%202024-01-05%2012-32-13.png

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

Title:
  [snap] Files on local network shares are not opened / written

Status in Mozilla Firefox:
  Confirmed
Status in firefox package in Ubuntu:
  Triaged
Status in xdg-desktop-portal package in Ubuntu:
  Triaged
Status in xdg-desktop-portal-gnome package in Ubuntu:
  Fix Released
Status in xdg-desktop-portal-gnome source package in Jammy:
  Triaged
Status in xdg-desktop-portal-gnome source package in Lunar:
  Triaged

Bug description:
  [ Impact ]

  When the user is running a containerized application (like the snapped
  Firefox or Chromium), and tries to save a document, the xdg-desktop-
  portal-gnome backend does show remote drives (like SMB or SFTP ones),
  and allows to choose them, but then the save operation fails.

  The previous backend, xdg-desktop-portal-gtk, did work fine in these
  cases, because it returned the local path that corresponded to the
  local file exported by Gvfs using FUSE, so this behaviour is not only
  a serious bug, but also a regression.

  [ Test plan]
  Steps to reproduce:

  1. Run Firefox as a Snap package in Ubuntu 22.04
  2. Have a SMB file server available where the network shares can be mounted 
just by clicking on the share in Nautilus file manager (smb:// protocol, 
usually mounted dynamically via `/var/run/user/.../gvfs/...`)
  3. Have one such share mounted and writable
  4. Open any website containing images in Firefox
  5. Right-click on an image and select "Save Image As..."
  6. In the file save dialog, navigate to the mounted share
  7. Assert content of network share is visible and browsable from within the 
save dialog
  8. Select "Save" at any folder in the network share

  Actual behavior:

  * File is not saved to selected network share location
  * No download entry is created
  * No error is shown

  Expected behavior:

  * File is saved to selected network share location
  * No error is shown

  [ Where problems could occur ]

  - If the remote drives aren't exported as local files by Gvfs using
  FUSE, the patch won't work and the behaviour will be the same than
  now.

  - Any hidden  bug in g_file_get_path() when managing remote drives
  could be triggered by this patch.

  [ Additional information ]

  * When saving to a folder on the local machine instead, saving works 
correctly as expected
  * In contrast to files, new folders that are created from within the save 
dialog are saved correctly on the network share
  * Similar situation when trying to open a file with Ctrl + O on a network 
share from Firefox / Chromium. After double-clicking e.g. an image file in the 
file dialog, the file dialog closes but nothing happens otherwise. Opening an 
image on a local folder works fine.

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


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

[Desktop-packages] [Bug 2011385] Re: [950XED, Realtek ALC298, Speaker, Internal] No sound at all

2024-01-05 Thread Dmitry

Same problem Razer Blade 16 2023

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

Title:
  [950XED, Realtek ALC298, Speaker, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux-hwe-5.19 package in Ubuntu:
  Confirmed

Bug description:
  only bluetooth can work,im sungsang book2 pro

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-35-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  wang   1658 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 13 15:41:47 2023
  InstallationDate: Installed on 2023-03-08 (4 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed
  Symptom_Card: sof-hda-dsp - sof-hda-dsp
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  wang   1658 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [950XED, Realtek ALC298, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/17/2022
  dmi.bios.release: 5.25
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: P08RGF.054.220817.ZQ
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NT950XEW-A51AS
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGLFREEDOS-C00-R000-S+1.0.
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP08RGF.054.220817.ZQ:bd08/17/2022:br5.25:svnSAMSUNGELECTRONICSCO.,LTD.:pn950XED:pvrP08RGF:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNT950XEW-A51AS:rvrSGLFREEDOS-C00-R000-S+1.0.:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:skuSCAI-ICPS-A5A5-ADLP-PRGF:
  dmi.product.family: Galaxy Book2 Pro
  dmi.product.name: 950XED
  dmi.product.sku: SCAI-ICPS-A5A5-ADLP-PRGF
  dmi.product.version: P08RGF
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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


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

[Desktop-packages] [Bug 2039630] Re: When I open gnome-control-center it creates a bunch of transparent windows with the title 'OpenGL Renderer'.

2024-01-05 Thread Nathan Teodosio

Reproduced in Ubuntu 24.04.

Only thing in stderr is

--->
Gtk[47738]:CRITICAL: Unable to register the application: 
GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected 
from message bus without replying
<---

Graphics:

--->
$ lspci -k|egrep '3D|VGA' -A3
00:02.0 VGA compatible controller: Intel Corporation WhiskeyLake-U GT2 [UHD 
Graphics 620]
Subsystem: Acer Incorporated [ALI] WhiskeyLake-U GT2 [UHD Graphics 620]
Kernel driver in use: i915
Kernel modules: i915
--
01:00.0 3D controller: NVIDIA Corporation GM108M [GeForce MX130] (rev a2)
Subsystem: Acer Incorporated [ALI] GM108M [GeForce MX130]
Kernel modules: nvidiafb, nouveau, nvidia_drm, nvidia

$ glxinfo -B
name of display: :0
display: :0  screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
Vendor: Intel (0x8086)
Device: Mesa Intel(R) UHD Graphics 620 (WHL GT2) (0x3ea0)
Version: 23.2.1
Accelerated: yes
Video memory: 7781MB
Unified memory: yes
Preferred profile: core (0x1)
Max core profile version: 4.6
Max compat profile version: 4.6
Max GLES1 profile version: 1.1
Max GLES[23] profile version: 3.2
OpenGL vendor string: Intel
OpenGL renderer string: Mesa Intel(R) UHD Graphics 620 (WHL GT2)
OpenGL core profile version string: 4.6 (Core Profile) Mesa 23.2.1-1ubuntu4
OpenGL core profile shading language version string: 4.60
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile

OpenGL version string: 4.6 (Compatibility Profile) Mesa 23.2.1-1ubuntu4
OpenGL shading language version string: 4.60
OpenGL context flags: (none)
OpenGL profile mask: compatibility profile

OpenGL ES profile version string: OpenGL ES 3.2 Mesa 23.2.1-1ubuntu4
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20
<---

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

Title:
  When I open gnome-control-center it creates a bunch of transparent
  windows with the title 'OpenGL Renderer'.

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

Bug description:
  I recently upgraded to Ubuntu 23.10.
  When I open settings (gnome-control-center) and click "Mouse & Touchpad", it 
creates about 8 transparent windows with the title 'OpenGL Randerer'.
  You can only see the existence of a window when you press Alt+Tab. In other 
words, pressing the Windows key to view the window list does not show 'OpenGL 
Randerer'.
  A window with the title 'OpenGL Randerer' should not be visible to the user 
even when Alt+Tab is pressed.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: gnome-control-center 1:45.0-1ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 18 14:41:09 2023
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to mantic on 2023-10-15 (3 days ago)

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


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

[Desktop-packages] [Bug 1833322] Re: Consider removing irqbalance from default install on desktop images

After all the history I was looking at where we are right now:
- irqbalance already is not in ubuntu-cloud-minimal images
- irqbalance is in normal cloud images and installed systems via the dep from 
ubuntu-server

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

Title:
  Consider removing irqbalance from default install on desktop images

Status in irqbalance package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  as per https://github.com/pop-os/default-settings/issues/60

  Distribution (run cat /etc/os-release):

  $ cat /etc/os-release
  NAME="Pop!_OS"
  VERSION="19.04"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Pop!_OS 19.04"
  VERSION_ID="19.04"
  HOME_URL="https://system76.com/pop;
  SUPPORT_URL="http://support.system76.com;
  BUG_REPORT_URL="https://github.com/pop-os/pop/issues;
  PRIVACY_POLICY_URL="https://system76.com/privacy;
  VERSION_CODENAME=disco
  UBUNTU_CODENAME=disco

  Related Application and/or Package Version (run apt policy $PACKAGE
  NAME):

  $ apt policy irqbalance
  irqbalance:
  Installed: 1.5.0-3ubuntu1
  Candidate: 1.5.0-3ubuntu1
  Version table:
  *** 1.5.0-3ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages
  100 /var/lib/dpkg/status

  $ apt rdepends irqbalance
  irqbalance
  Reverse Depends:
  Recommends: ubuntu-standard
  gce-compute-image-packages

  Issue/Bug Description:

  as per konkor/cpufreq#48 and
  http://konkor.github.io/cpufreq/faq/#irqbalance-detected

  irqbalance is technically not needed on desktop systems (supposedly it
  is mainly for servers), and may actually reduce performance and power
  savings. It appears to provide benefits only to server environments
  that have relatively-constant loading. If it is truly a server-
  oriented package, then it shouldn't be installed by default on a
  desktop/laptop system and shouldn't be included in desktop OS images.

  Steps to reproduce (if you know):

  This is potentially an issue with all default installs.

  Expected behavior:

  n/a

  Other Notes:

  I can safely remove it via "sudo apt purge irqbalance" without any
  apparent adverse side-effects. If someone is running a situation where
  they need it, then they always have the option of installing it from
  the repositories.

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


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

[Desktop-packages] [Bug 2039630] Re: When I open gnome-control-center it creates a bunch of transparent windows with the title 'OpenGL Renderer'.

2024-01-05 Thread Nathan Teodosio

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

** Description changed:

  I recently upgraded to Ubuntu 23.10.
- When I open settings (gnome-control-center) and click on a certain menu, it 
creates about 8 transparent windows with the title 'OpenGL Randerer'.
+ When I open settings (gnome-control-center) and click "Mouse & Touchpad", it 
creates about 8 transparent windows with the title 'OpenGL Randerer'.
  You can only see the existence of a window when you press Alt+Tab. In other 
words, pressing the Windows key to view the window list does not show 'OpenGL 
Randerer'.
  A window with the title 'OpenGL Randerer' should not be visible to the user 
even when Alt+Tab is pressed.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: gnome-control-center 1:45.0-1ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 18 14:41:09 2023
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to mantic on 2023-10-15 (3 days ago)

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

Title:
  When I open gnome-control-center it creates a bunch of transparent
  windows with the title 'OpenGL Renderer'.

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

Bug description:
  I recently upgraded to Ubuntu 23.10.
  When I open settings (gnome-control-center) and click "Mouse & Touchpad", it 
creates about 8 transparent windows with the title 'OpenGL Randerer'.
  You can only see the existence of a window when you press Alt+Tab. In other 
words, pressing the Windows key to view the window list does not show 'OpenGL 
Randerer'.
  A window with the title 'OpenGL Randerer' should not be visible to the user 
even when Alt+Tab is pressed.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: gnome-control-center 1:45.0-1ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 18 14:41:09 2023
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to mantic on 2023-10-15 (3 days ago)

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


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

[Desktop-packages] [Bug 1833322] Re: Consider removing irqbalance from default install on desktop images

I subscribed a few people directly to get their input.

@Steve
I've subscribed you after trying to find, refer and summarize all of the past 
to allow you and anyone else to read into this in one go. I think I'll need 
your input as Architect and as participant of these discussions right from when 
they started 14 years ago.

@Phil/@John
Some past discussions, especially the backpedaling of Debian referred to 
virtual environments and/or large cloud providers. Is irqbalance anything you 
got asked to disable (or keep) for their environment?
No need to share names, but reasoning or data points would be helpful :-)

@Dimitri
Is there a more clear "this is what userspace should do in regard to this in 
2024" form the kernel? I couldn#t find it, but maybe you know or know who'd 
know ...

@Sebastien
Since most problems reported have been around Desktops (to be fair, that could 
be an coincidence because that is where people do more experiments and have 
more diverse special cases). But I think it is fair to ask you if requests or 
discussion like the above have come up towards Desktop that are worth to refer 
here?


Maybe one of you has more details that help to make the decision more clear and 
easy.
Or a gut feeling that is even stronger than mine, strong enough even to pick 
one of the options?

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

Title:
  Consider removing irqbalance from default install on desktop images

Status in irqbalance package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  as per https://github.com/pop-os/default-settings/issues/60

  Distribution (run cat /etc/os-release):

  $ cat /etc/os-release
  NAME="Pop!_OS"
  VERSION="19.04"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Pop!_OS 19.04"
  VERSION_ID="19.04"
  HOME_URL="https://system76.com/pop;
  SUPPORT_URL="http://support.system76.com;
  BUG_REPORT_URL="https://github.com/pop-os/pop/issues;
  PRIVACY_POLICY_URL="https://system76.com/privacy;
  VERSION_CODENAME=disco
  UBUNTU_CODENAME=disco

  Related Application and/or Package Version (run apt policy $PACKAGE
  NAME):

  $ apt policy irqbalance
  irqbalance:
  Installed: 1.5.0-3ubuntu1
  Candidate: 1.5.0-3ubuntu1
  Version table:
  *** 1.5.0-3ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages
  100 /var/lib/dpkg/status

  $ apt rdepends irqbalance
  irqbalance
  Reverse Depends:
  Recommends: ubuntu-standard
  gce-compute-image-packages

  Issue/Bug Description:

  as per konkor/cpufreq#48 and
  http://konkor.github.io/cpufreq/faq/#irqbalance-detected

  irqbalance is technically not needed on desktop systems (supposedly it
  is mainly for servers), and may actually reduce performance and power
  savings. It appears to provide benefits only to server environments
  that have relatively-constant loading. If it is truly a server-
  oriented package, then it shouldn't be installed by default on a
  desktop/laptop system and shouldn't be included in desktop OS images.

  Steps to reproduce (if you know):

  This is potentially an issue with all default installs.

  Expected behavior:

  n/a

  Other Notes:

  I can safely remove it via "sudo apt purge irqbalance" without any
  apparent adverse side-effects. If someone is running a situation where
  they need it, then they always have the option of installing it from
  the repositories.

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


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

[Desktop-packages] [Bug 1833322] Re: Consider removing irqbalance from default install on desktop images

# Summary

This discussion was seeminly easier to make the more dedicated to a singluar
use case you are - as then you have less "but what if" cases to consider.
That wide usage is great for Ubuntu but sometimes delays decisions.

List of reasons to remove it from the default dependencies:
- Seems to cause issues more often on Desktop environments
- cpufreq, thermald and similar struggle to save energy
- Impacts due to unepexcted throttling
- Conflicts with enabling/disabling threads/cores
- Problematic in virtual environments
- It is mostly an x86 thing but we pull it in everywhere
- It conflicts with manually fine tuned IRQ affinity e.g. in
  ultra low latency setups
- It is less useful on cpus with large and wide shared caches
  as well as in virtual environments without fix pinning

List of reasons to keep it in the set of default dependencies:
- Benefits seem mostly for large scale servers
- lacking irqbalance can be a performance degradation in some
  large scale high traffic cases

I think from all I've found - old and new - it seems it still has its purpose
in some scenarios, but the HW/SW world evolved and it is nowadays less often
useful and more often harmful than it was in the past.
On the other hand there is almost no clear cut "it is bad and that is why",
most issues were individual issues and special cases, nothing that would
apply to everyone.

And irqbalance still has is purpose, so we should surely keep it around.

In a perfect worlds this would have half a year of time or more and two people
to run all kinds of workloads on all kinds of HW to compare. But let us be
honest that will not happen and that would then also be not be worth the effort.
We'll have to decide with what we have.
Have the others that switched have more time to evaluate in depth, I do not
know. But usually once a significant amount of the ecosystems changed and you
lack better data it is better to also follow or common hints and optimizations
will no more apply due to being the one outlier in regard to behavior.

To me this seems to be a perfect case for a few special images/deployments
known to match the workload profile that needs this to enable it.
It is also more likely that a professional admin of such a large scale machine
(or cluster thereof) can make the opt-in decision and evaluation better than
expectint every user of Ubuntu to think about an opt-out.


---

Options IMHO:
A) Change it from an opt-out to an opt-in and remove the dependency
   from ubuntu-standard
B) Remove it from ubuntu-standard to get rid of it in Desktops and images
   used in virtual environments. But try to keep it in a place that is mostly
   used for bare metal which tend to be closer to the kind that benefits more
C) Do nothing, keep it as is

D) Any of the above, but let us not touch Noble more than half way through the
cycle, but do that early in 24.10 to have enough exposure before a release in
an LTS.

My gut feeling (and it can't be much more without much more time for much
deeper investigations) would be (A).

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

Title:
  Consider removing irqbalance from default install on desktop images

Status in irqbalance package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  as per https://github.com/pop-os/default-settings/issues/60

  Distribution (run cat /etc/os-release):

  $ cat /etc/os-release
  NAME="Pop!_OS"
  VERSION="19.04"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Pop!_OS 19.04"
  VERSION_ID="19.04"
  HOME_URL="https://system76.com/pop;
  SUPPORT_URL="http://support.system76.com;
  BUG_REPORT_URL="https://github.com/pop-os/pop/issues;
  PRIVACY_POLICY_URL="https://system76.com/privacy;
  VERSION_CODENAME=disco
  UBUNTU_CODENAME=disco

  Related Application and/or Package Version (run apt policy $PACKAGE
  NAME):

  $ apt policy irqbalance
  irqbalance:
  Installed: 1.5.0-3ubuntu1
  Candidate: 1.5.0-3ubuntu1
  Version table:
  *** 1.5.0-3ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages
  100 /var/lib/dpkg/status

  $ apt rdepends irqbalance
  irqbalance
  Reverse Depends:
  Recommends: ubuntu-standard
  gce-compute-image-packages

  Issue/Bug Description:

  as per konkor/cpufreq#48 and
  http://konkor.github.io/cpufreq/faq/#irqbalance-detected

  irqbalance is technically not needed on desktop systems (supposedly it
  is mainly for servers), and may actually reduce performance and power
  savings. It appears to provide benefits only to server environments
  that have relatively-constant loading. If it is truly a server-
  oriented package, then it shouldn't be installed by default on a
  desktop/laptop system and shouldn't be included in desktop OS images.

  Steps to reproduce (if you know):

  This is potentially an issue with all default installs.

  Expected behavior:

  n/a

[Desktop-packages] [Bug 1833322] Re: Consider removing irqbalance from default install on desktop images

# Actions by Others

Times have changes, as mentioned above the kernel learned many new tricks.
More new I/O hardware virtual or physical appeared that tries to be smart
and thereby sometimes conflict with what irqbalance does.

Some are mostly based on the links referred above, the Debian disucssion
was more about it being harmful (or at least not helpful) in virtual
environments and hence removed from cloud images (we close in on workload
specific again).

Indeed many projects already removed it from the default
- https://github.com/pop-os/iso/pull/288
- https://github.com/ValveSoftware/Proton/issues/3243
- https://lists.debian.org/debian-cloud/2019/04/msg00040.html

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

Title:
  Consider removing irqbalance from default install on desktop images

Status in irqbalance package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  as per https://github.com/pop-os/default-settings/issues/60

  Distribution (run cat /etc/os-release):

  $ cat /etc/os-release
  NAME="Pop!_OS"
  VERSION="19.04"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Pop!_OS 19.04"
  VERSION_ID="19.04"
  HOME_URL="https://system76.com/pop;
  SUPPORT_URL="http://support.system76.com;
  BUG_REPORT_URL="https://github.com/pop-os/pop/issues;
  PRIVACY_POLICY_URL="https://system76.com/privacy;
  VERSION_CODENAME=disco
  UBUNTU_CODENAME=disco

  Related Application and/or Package Version (run apt policy $PACKAGE
  NAME):

  $ apt policy irqbalance
  irqbalance:
  Installed: 1.5.0-3ubuntu1
  Candidate: 1.5.0-3ubuntu1
  Version table:
  *** 1.5.0-3ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages
  100 /var/lib/dpkg/status

  $ apt rdepends irqbalance
  irqbalance
  Reverse Depends:
  Recommends: ubuntu-standard
  gce-compute-image-packages

  Issue/Bug Description:

  as per konkor/cpufreq#48 and
  http://konkor.github.io/cpufreq/faq/#irqbalance-detected

  irqbalance is technically not needed on desktop systems (supposedly it
  is mainly for servers), and may actually reduce performance and power
  savings. It appears to provide benefits only to server environments
  that have relatively-constant loading. If it is truly a server-
  oriented package, then it shouldn't be installed by default on a
  desktop/laptop system and shouldn't be included in desktop OS images.

  Steps to reproduce (if you know):

  This is potentially an issue with all default installs.

  Expected behavior:

  n/a

  Other Notes:

  I can safely remove it via "sudo apt purge irqbalance" without any
  apparent adverse side-effects. If someone is running a situation where
  they need it, then they always have the option of installing it from
  the repositories.

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


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

[Desktop-packages] [Bug 1833322] Re: Consider removing irqbalance from default install on desktop images

# Integration and maintenance

Despite some saying it is for the past only, it is regularly updated
and has multiple releases per year throughout all the time [4]. Those
updates flow well into Debian and Ubuntu - so it is not a classic "old
and outdated" case. And while not much changes in those updates, it means
it still learns like about thermal events in 1.9.1 or about isolcpus in 1.0.9.
I'm not saying it is super modern doing it all, but it gets updates.

Currently this is seeded in ubuntu-standard [1], which is what makes it
default installed everywhere. But it is intentionally only a recommends,
so the set of people that want to remove it can do so.

It was added a long time ago [3] back when multi-core was a rare thing
at least for Desktop systems. This was based on a discussion [5] and was
related to the kernel [6] actively delegating this to userspace. Debian
did a similar change a bit later [17] for the same reasons.
But again this was the time of single-core being common.


[1]: 
https://git.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/+git/platform/tree/standard?h=noble#n19
[3]: 
https://git.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/+git/platform/commit/?h=noble=dcd02266953547e11221979eb17eb740a76a62b5
[4]: https://github.com/Irqbalance/irqbalance/tags
[5]: https://lists.ubuntu.com/archives/ubuntu-devel/2010-January/029939.html
[6]: 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=8b8e8c1bf7275eca859fe551dfa484134eaf013b
[17]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=577788


** Bug watch added: github.com/ValveSoftware/Proton/issues #3243
   https://github.com/ValveSoftware/Proton/issues/3243

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

Title:
  Consider removing irqbalance from default install on desktop images

Status in irqbalance package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  as per https://github.com/pop-os/default-settings/issues/60

  Distribution (run cat /etc/os-release):

  $ cat /etc/os-release
  NAME="Pop!_OS"
  VERSION="19.04"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Pop!_OS 19.04"
  VERSION_ID="19.04"
  HOME_URL="https://system76.com/pop;
  SUPPORT_URL="http://support.system76.com;
  BUG_REPORT_URL="https://github.com/pop-os/pop/issues;
  PRIVACY_POLICY_URL="https://system76.com/privacy;
  VERSION_CODENAME=disco
  UBUNTU_CODENAME=disco

  Related Application and/or Package Version (run apt policy $PACKAGE
  NAME):

  $ apt policy irqbalance
  irqbalance:
  Installed: 1.5.0-3ubuntu1
  Candidate: 1.5.0-3ubuntu1
  Version table:
  *** 1.5.0-3ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages
  100 /var/lib/dpkg/status

  $ apt rdepends irqbalance
  irqbalance
  Reverse Depends:
  Recommends: ubuntu-standard
  gce-compute-image-packages

  Issue/Bug Description:

  as per konkor/cpufreq#48 and
  http://konkor.github.io/cpufreq/faq/#irqbalance-detected

  irqbalance is technically not needed on desktop systems (supposedly it
  is mainly for servers), and may actually reduce performance and power
  savings. It appears to provide benefits only to server environments
  that have relatively-constant loading. If it is truly a server-
  oriented package, then it shouldn't be installed by default on a
  desktop/laptop system and shouldn't be included in desktop OS images.

  Steps to reproduce (if you know):

  This is potentially an issue with all default installs.

  Expected behavior:

  n/a

  Other Notes:

  I can safely remove it via "sudo apt purge irqbalance" without any
  apparent adverse side-effects. If someone is running a situation where
  they need it, then they always have the option of installing it from
  the repositories.

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


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

[Desktop-packages] [Bug 1833322] Re: Consider removing irqbalance from default install on desktop images

# Referred Arguments

An argument that might not have been so strong more than a decade ago
but is much more today is power savings and that is an aspect that comes up
over and over.
It also had reports of conflicts with power saving [10] and e.g. dynamically
disabling/enabling cores which is much more a thing nowadays as long ago
this was only reliably working on mainframes anyway.

I don't buy the "games need 100%" as even games need their I/O to happen,
but OTOH irqbalance just doesn't help much nowadays either as the kernel learned
many more tricks to do well - like to name just one all the traffic aware
and potentially offloaded rps/xps [2]. And irqbalance is not mutually exclusive
with most of those technologies not with RSS [18] nor with kernel policies [15].

Some report about conflicting with their custom tweaking of IRQs [8][16].
It is actually a common conflict between irqbalance being smart [9] and other
things like a particular device firmware being smart leading to a conflict of
interest.
=> But TBH that is why it is removable for such rare cases.

On one hand it clearly has some impact and various cases of bad impacts by it
have come up as well for frame rates [11], stuttering [14] or even network
traffic [12].

But on the other hand, there have been reports and cases where a broken
irqbalance led to impacted high-performance network traffic [7], so it is
not that it is clearly always bad [13]. While we never know how outdated
any such source might be, it proves that it is most likely workload and
system dependent. Many documentations also sitll refer to it only older RH,
Arch [19], ... you'll find it everywhere.

It is an interesting case, and the workload dependency leads many discussions
to even be contradicting - in one case it saves cpu power in the other it makes
it worse. In one it helps traffic in the other is degrades it. That is all a
consqeuence of it being workload and system dependent.
This back and forther is perfectly encapsulated in this phornix thread [15].
Which quotes interesting other POVs like kernel solutions often being "driver
centric" optimizing throughput, but maybe not always the best as policy for
the full system as irqbalance pilicies and tunables are configurable.

An interim summary might be:
"""
It could cause rare issues or conflicts, especially on Desktop,
but might be still wanted on Servers especially those with a
high rate of I/O
"""

Which is interestingly quite close to the arguments floating around when it
was added more than a decade ago (see further below).

[2]: https://www.kernel.org/doc/html/latest/networking/scaling.html
[7]: https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/2038573
[8]: https://groups.google.com/g/gce-discussion/c/Ns8hgOUW9GY
[9]: https://docs.xilinx.com/r/en-US/ug1523-x3522-user/Interrupt-Affinity
[10]: https://konkor.github.io/cpufreq/faq/#irqbalance-detected
[11]: 
https://askubuntu.com/questions/1067866/ubuntu-18-04-steam-games-frame-rate-drop
[12]: 
https://serverfault.com/questions/410928/irqbalance-on-linux-and-dropped-packets
[13]: https://bookofzeus.com/harden-ubuntu/server-setup/disable-irqbalance/
[14]: 
https://www.reddit.com/r/linux_gaming/comments/emnu3k/removing_irqbalance_fixed_major_stuttering_in/
[15]: 
https://www.phoronix.com/forums/forum/hardware/processors-memory/1335986-amd-zen-1-linux-performance-hit-from-retbleed-accumulated-cpu-mitigation-impact/page4
[16]: 
https://documentation.suse.com/sbp/server-linux/pdf/SBP-performance-tuning_en.pdf
[18]: 
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/6/html/performance_tuning_guide/network-rss
[19]: https://wiki.archlinux.org/title/Improving_performance#irqbalance

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

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

Title:
  Consider removing irqbalance from default install on desktop images

Status in irqbalance package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  as per https://github.com/pop-os/default-settings/issues/60

  Distribution (run cat /etc/os-release):

  $ cat /etc/os-release
  NAME="Pop!_OS"
  VERSION="19.04"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Pop!_OS 19.04"
  VERSION_ID="19.04"
  HOME_URL="https://system76.com/pop;
  SUPPORT_URL="http://support.system76.com;
  BUG_REPORT_URL="https://github.com/pop-os/pop/issues;
  PRIVACY_POLICY_URL="https://system76.com/privacy;
  VERSION_CODENAME=disco
  UBUNTU_CODENAME=disco

  Related Application and/or Package Version (run apt policy $PACKAGE
  NAME):

  $ apt policy irqbalance
  irqbalance:
  Installed: 1.5.0-3ubuntu1
  Candidate: 1.5.0-3ubuntu1
  Version table:
  *** 1.5.0-3ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages
  100 /var/lib/dpkg/status

  $ apt

[Desktop-packages] [Bug 1833322] Re: Consider removing irqbalance from default install on desktop images

Hi,
this was overlooked for too long but came up in bug 2046470 again which made me 
see this for the first time.

I'd wish we'd have had that even a bit earlier e.g. to release it with
mantic and not half way through noble, but still now is the time to
still change the next LTS.

I needed to make up my mind on this to come to a conclusion and so I wrote a
summary mostly for myself, but also for others that I want to ack to the
decision as well as for anyone to later be able to understand what changed
and why.

I must admit that I'm slightly biased, having looked at it ages ago, even
before I was more active in Ubuntu development and already wondering if that
should be used by default.

And yes, some people had a stronger wish to get it out of the default.
So as already reported, many have already asked to remove it.

I'll try to break up my answers to be more easily referable.


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

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

Title:
  Consider removing irqbalance from default install on desktop images

Status in irqbalance package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  as per https://github.com/pop-os/default-settings/issues/60

  Distribution (run cat /etc/os-release):

  $ cat /etc/os-release
  NAME="Pop!_OS"
  VERSION="19.04"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Pop!_OS 19.04"
  VERSION_ID="19.04"
  HOME_URL="https://system76.com/pop;
  SUPPORT_URL="http://support.system76.com;
  BUG_REPORT_URL="https://github.com/pop-os/pop/issues;
  PRIVACY_POLICY_URL="https://system76.com/privacy;
  VERSION_CODENAME=disco
  UBUNTU_CODENAME=disco

  Related Application and/or Package Version (run apt policy $PACKAGE
  NAME):

  $ apt policy irqbalance
  irqbalance:
  Installed: 1.5.0-3ubuntu1
  Candidate: 1.5.0-3ubuntu1
  Version table:
  *** 1.5.0-3ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages
  100 /var/lib/dpkg/status

  $ apt rdepends irqbalance
  irqbalance
  Reverse Depends:
  Recommends: ubuntu-standard
  gce-compute-image-packages

  Issue/Bug Description:

  as per konkor/cpufreq#48 and
  http://konkor.github.io/cpufreq/faq/#irqbalance-detected

  irqbalance is technically not needed on desktop systems (supposedly it
  is mainly for servers), and may actually reduce performance and power
  savings. It appears to provide benefits only to server environments
  that have relatively-constant loading. If it is truly a server-
  oriented package, then it shouldn't be installed by default on a
  desktop/laptop system and shouldn't be included in desktop OS images.

  Steps to reproduce (if you know):

  This is potentially an issue with all default installs.

  Expected behavior:

  n/a

  Other Notes:

  I can safely remove it via "sudo apt purge irqbalance" without any
  apparent adverse side-effects. If someone is running a situation where
  they need it, then they always have the option of installing it from
  the repositories.

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


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

[Desktop-packages] [Bug 2039660] Re: wayland application not inputting accentuated caps characters after upgrade to 23.10

2024-01-05 Thread Launchpad Bug Tracker

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

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

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

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

Title:
  wayland application not inputting accentuated caps characters after
  upgrade to 23.10

Status in mutter package in Ubuntu:
  Confirmed
Status in Fedora:
  Fix Released

Bug description:
  After upgrading to 23.10 from 23.04, I am unable to input accentuated
  caps chars like « É ».

  STR:
   - Configure keyboard input as french (any variant does the job it seems)
   - Make sure you are in caps lock mode
   - Type the "2 é" char on the keyboard

  Expected:
   - « É » is produced

  Actual:
   - « é » in produced

  Fun fact:
   When reproducing in the GNOME Settings app, there is an interesting behavior:
   - if you try to input « É » WITHOUT focusing first in the search field of 
the app, then the first char will be correctly produced as « É » but subsequent 
will not
   - obviously, if you try the same WITH focusing first in the search field, 
you end up in the first case

  Facts:
   - xev shows proper data arriving
   - reproduced on several wayland app (gnome-text-editor, firefox, 
gnome-settings, gedit)
   - not reproduced on xwayland (hexchat, GDB_BACKEND=x11 gedit)

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: ubuntu-release-upgrader-core 1:23.10.10
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 18 11:57:45 2023
  InstallationDate: Installed on 2022-07-04 (471 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: Upgraded to mantic on 2023-10-16 (2 days ago)
  VarLogDistupgradeXorgFixuplog:
   INFO:root:/usr/bin/do-release-upgrade running
   INFO:root:No xorg.conf, exiting

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


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

[Desktop-packages] [Bug 1927948] Re: Windows switch monitor after resuming from sleep

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

Title:
  Windows switch monitor after resuming from sleep

Status in GNOME Shell:
  New
Status in Mutter:
  New
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  What I expect:

  Window layout/positioning is identical after resume from sleep.

  What I observe:

  After resume from sleep, windows appear on a different monitor than
  before.

  I found this possibly relevant GNOME bug:

  https://gitlab.gnome.org/GNOME/mutter/-/issues/1419

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: mutter 3.38.4-1ubuntu2
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 10 13:40:28 2021
  InstallationDate: Installed on 2019-12-02 (524 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: mutter
  UpgradeStatus: Upgraded to hirsute on 2021-05-05 (4 days ago)

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


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

[Desktop-packages] [Bug 2043524] Re: audio disappeared after upgrade to Ubuntu 23.10

2024-01-05 Thread Enderson Maia

Same here, I was using Ubuntu 23.10 for a while, and on day my headset
started behaving weirdly, I didn't installed anything.

When trying to troubleshoot, I noticed that I had audio working when
choosing Handsfree mode, that's mono audio with mic input for my
Senheiser HD BT40, but it doesn't work when choosing other
configurations with stereo high fidelity aptX or anything else.

Moving forward, I noticed that even the laptop audio isn't working
(Comet Lake PCH cAVS) from my hinkPad X1 Extreme Gen 3 Intel (15").

I think I broke my system even harder trying to fix it trying pipewire,
wireplumber and such, now when I go to Sound Configuration I don't even
see other previously available configurations when selecting the
Headset. Is there some steps so I can restore default configurations =/?

http://alsa-project.org/db/?f=b74c74303071e17f6d87fe940f59d89132eecc53

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

Title:
  audio disappeared after upgrade to Ubuntu 23.10

Status in pulseaudio package in Ubuntu:
  Confirmed

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

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: pulseaudio 1:16.1+dfsg1-2ubuntu4
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  owner   975 F wireplumber
   /dev/snd/seq:owner   971 F pipewire
  CasperMD5CheckResult: fail
  CurrentDesktop: KDE
  Date: Tue Nov 14 17:50:17 2023
  InstallationDate: Installed on 2023-04-15 (213 days ago)
  InstallationMedia: Kubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: Upgraded to mantic on 2023-11-09 (5 days ago)
  dmi.bios.date: 07/04/2012
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V3.0
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H61M-P31/W8 (MS-7788)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV3.0:bd07/04/2012:br4.6:svnMSI:pnMS-7788:pvr1.0:rvnMSI:rnH61M-P31/W8(MS-7788):rvr1.0:cvnMSI:ct3:cvr1.0:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7788
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI

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


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

[Desktop-packages] [Bug 1971168] Re: [snap] Files on local network shares are not opened / written

Yes, it should, because the patch has been merged in upstream.

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

Title:
  [snap] Files on local network shares are not opened / written

Status in Mozilla Firefox:
  Confirmed
Status in firefox package in Ubuntu:
  Triaged
Status in xdg-desktop-portal package in Ubuntu:
  Triaged
Status in xdg-desktop-portal-gnome package in Ubuntu:
  Fix Released
Status in xdg-desktop-portal-gnome source package in Jammy:
  Triaged
Status in xdg-desktop-portal-gnome source package in Lunar:
  Triaged

Bug description:
  [ Impact ]

  When the user is running a containerized application (like the snapped
  Firefox or Chromium), and tries to save a document, the xdg-desktop-
  portal-gnome backend does show remote drives (like SMB or SFTP ones),
  and allows to choose them, but then the save operation fails.

  The previous backend, xdg-desktop-portal-gtk, did work fine in these
  cases, because it returned the local path that corresponded to the
  local file exported by Gvfs using FUSE, so this behaviour is not only
  a serious bug, but also a regression.

  [ Test plan]
  Steps to reproduce:

  1. Run Firefox as a Snap package in Ubuntu 22.04
  2. Have a SMB file server available where the network shares can be mounted 
just by clicking on the share in Nautilus file manager (smb:// protocol, 
usually mounted dynamically via `/var/run/user/.../gvfs/...`)
  3. Have one such share mounted and writable
  4. Open any website containing images in Firefox
  5. Right-click on an image and select "Save Image As..."
  6. In the file save dialog, navigate to the mounted share
  7. Assert content of network share is visible and browsable from within the 
save dialog
  8. Select "Save" at any folder in the network share

  Actual behavior:

  * File is not saved to selected network share location
  * No download entry is created
  * No error is shown

  Expected behavior:

  * File is saved to selected network share location
  * No error is shown

  [ Where problems could occur ]

  - If the remote drives aren't exported as local files by Gvfs using
  FUSE, the patch won't work and the behaviour will be the same than
  now.

  - Any hidden  bug in g_file_get_path() when managing remote drives
  could be triggered by this patch.

  [ Additional information ]

  * When saving to a folder on the local machine instead, saving works 
correctly as expected
  * In contrast to files, new folders that are created from within the save 
dialog are saved correctly on the network share
  * Similar situation when trying to open a file with Ctrl + O on a network 
share from Firefox / Chromium. After double-clicking e.g. an image file in the 
file dialog, the file dialog closes but nothing happens otherwise. Opening an 
image on a local folder works fine.

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


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

[Desktop-packages] [Bug 1971168] Re: [snap] Files on local network shares are not opened / written

2024-01-05 Thread Miguel

Hi,
This bug going to be solved for 22.04?

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

Title:
  [snap] Files on local network shares are not opened / written

Status in Mozilla Firefox:
  Confirmed
Status in firefox package in Ubuntu:
  Triaged
Status in xdg-desktop-portal package in Ubuntu:
  Triaged
Status in xdg-desktop-portal-gnome package in Ubuntu:
  Fix Released
Status in xdg-desktop-portal-gnome source package in Jammy:
  Triaged
Status in xdg-desktop-portal-gnome source package in Lunar:
  Triaged

Bug description:
  [ Impact ]

  When the user is running a containerized application (like the snapped
  Firefox or Chromium), and tries to save a document, the xdg-desktop-
  portal-gnome backend does show remote drives (like SMB or SFTP ones),
  and allows to choose them, but then the save operation fails.

  The previous backend, xdg-desktop-portal-gtk, did work fine in these
  cases, because it returned the local path that corresponded to the
  local file exported by Gvfs using FUSE, so this behaviour is not only
  a serious bug, but also a regression.

  [ Test plan]
  Steps to reproduce:

  1. Run Firefox as a Snap package in Ubuntu 22.04
  2. Have a SMB file server available where the network shares can be mounted 
just by clicking on the share in Nautilus file manager (smb:// protocol, 
usually mounted dynamically via `/var/run/user/.../gvfs/...`)
  3. Have one such share mounted and writable
  4. Open any website containing images in Firefox
  5. Right-click on an image and select "Save Image As..."
  6. In the file save dialog, navigate to the mounted share
  7. Assert content of network share is visible and browsable from within the 
save dialog
  8. Select "Save" at any folder in the network share

  Actual behavior:

  * File is not saved to selected network share location
  * No download entry is created
  * No error is shown

  Expected behavior:

  * File is saved to selected network share location
  * No error is shown

  [ Where problems could occur ]

  - If the remote drives aren't exported as local files by Gvfs using
  FUSE, the patch won't work and the behaviour will be the same than
  now.

  - Any hidden  bug in g_file_get_path() when managing remote drives
  could be triggered by this patch.

  [ Additional information ]

  * When saving to a folder on the local machine instead, saving works 
correctly as expected
  * In contrast to files, new folders that are created from within the save 
dialog are saved correctly on the network share
  * Similar situation when trying to open a file with Ctrl + O on a network 
share from Firefox / Chromium. After double-clicking e.g. an image file in the 
file dialog, the file dialog closes but nothing happens otherwise. Opening an 
image on a local folder works fine.

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


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

[Desktop-packages] [Bug 1927948] Re: Windows switch monitor after resuming from sleep

2024-01-05 Thread Daniel van Vugt

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

** Changed in: mutter
   Status: Fix Released => Unknown

** Changed in: mutter
 Remote watch: gitlab.gnome.org/GNOME/mutter/-/issues #1419 => 
gitlab.gnome.org/GNOME/mutter/-/issues #230

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

Title:
  Windows switch monitor after resuming from sleep

Status in GNOME Shell:
  New
Status in Mutter:
  Unknown
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  What I expect:

  Window layout/positioning is identical after resume from sleep.

  What I observe:

  After resume from sleep, windows appear on a different monitor than
  before.

  I found this possibly relevant GNOME bug:

  https://gitlab.gnome.org/GNOME/mutter/-/issues/1419

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: mutter 3.38.4-1ubuntu2
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 10 13:40:28 2021
  InstallationDate: Installed on 2019-12-02 (524 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: mutter
  UpgradeStatus: Upgraded to hirsute on 2021-05-05 (4 days ago)

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


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

[Desktop-packages] [Bug 1927948] Re: Windows switch monitor after resuming from sleep

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

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

Title:
  Windows switch monitor after resuming from sleep

Status in GNOME Shell:
  New
Status in Mutter:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  What I expect:

  Window layout/positioning is identical after resume from sleep.

  What I observe:

  After resume from sleep, windows appear on a different monitor than
  before.

  I found this possibly relevant GNOME bug:

  https://gitlab.gnome.org/GNOME/mutter/-/issues/1419

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: mutter 3.38.4-1ubuntu2
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 10 13:40:28 2021
  InstallationDate: Installed on 2019-12-02 (524 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: mutter
  UpgradeStatus: Upgraded to hirsute on 2021-05-05 (4 days ago)

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


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

[Desktop-packages] [Bug 1913218] Re: Obscure shortcut selector behaviour