date:20230324

[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/2003656

Title:
  [nvidia] "night light" setting only affects one of 2 used screens

Status in gnome-shell package in Ubuntu:
  Expired

Bug description:
  I have an external display that I declared my primary display (my
  laptop screen being the 2nd one). When night light is applied, it only
  affects the built-in display. It should affect both, otherwise it's
  kind of useless.

  I noticed this just now, no clue how repeatable it is. No known
  workaround (maybe "don't use the computer at night?").

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.36.5-0ubuntu4
  ProcVersionSignature: Ubuntu 5.15.0-56.62~20.04.1-generic 5.15.64
  Uname: Linux 5.15.0-56-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 22 20:16:01 2023
  InstallationDate: Installed on 2022-11-03 (80 days ago)
  InstallationMedia: Ubuntu 20.04.5 LTS "Focal Fossa" - Release amd64 (20220831)
  SourcePackage: gnome-control-center
  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/2003656/+subscriptions


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

[Desktop-packages] [Bug 2012781] Re: package cups 2.4.1op1-1ubuntu4.1 failed to install/upgrade: o subprocesso instalado, do pacote cups, o script post-installation foi morto pelo sinal (Erro no barra

2023-03-24 Thread Ubuntu Foundations Team Bug Bot

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

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

Title:
  package cups 2.4.1op1-1ubuntu4.1 failed to install/upgrade: o
  subprocesso instalado, do pacote cups, o script post-installation foi
  morto pelo sinal (Erro no barramento), gerou um core

Status in cups package in Ubuntu:
  New

Bug description:
  abc

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: cups 2.4.1op1-1ubuntu4.1
  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
  AptOrdering:
   printer-driver-splix:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Thu Mar 23 20:47:31 2023
  ErrorMessage: o subprocesso instalado, do pacote cups, o script 
post-installation foi morto pelo sinal (Erro no barramento), gerou um core
  InstallationDate: Installed on 2023-03-20 (4 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0bda:5521 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 004: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 003: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5584
  Papersize: a4
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.19.0-35-generic 
root=UUID=e080f2c9-2ee1-4e8a-a8e4-01af8fec25a1 ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-35-generic 
root=UUID=e080f2c9-2ee1-4e8a-a8e4-01af8fec25a1 ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.1
   apt  2.4.8
  SourcePackage: cups
  Title: package cups 2.4.1op1-1ubuntu4.1 failed to install/upgrade: o 
subprocesso instalado, do pacote cups, o script post-installation foi morto 
pelo sinal (Erro no barramento), gerou um core
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/04/2020
  dmi.bios.release: 1.12
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.12.0
  dmi.board.name: 012D2F
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.12.0:bd11/04/2020:br1.12:svnDellInc.:pnInspiron5584:pvr:rvnDellInc.:rn012D2F:rvrA00:cvnDellInc.:ct10:cvr:sku08FA:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5584
  dmi.product.sku: 08FA
  dmi.sys.vendor: Dell Inc.

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


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

[Desktop-packages] [Bug 2012781] [NEW] package cups 2.4.1op1-1ubuntu4.1 failed to install/upgrade: o subprocesso instalado, do pacote cups, o script post-installation foi morto pelo sinal (Erro no bar

You have been subscribed to a public bug:

abc

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: cups 2.4.1op1-1ubuntu4.1
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
AptOrdering:
 printer-driver-splix:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
CasperMD5CheckResult: pass
Date: Thu Mar 23 20:47:31 2023
ErrorMessage: o subprocesso instalado, do pacote cups, o script 
post-installation foi morto pelo sinal (Erro no barramento), gerou um core
InstallationDate: Installed on 2023-03-20 (4 days ago)
InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 002: ID 0bda:5521 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
 Bus 001 Device 004: ID 046d:c534 Logitech, Inc. Unifying Receiver
 Bus 001 Device 003: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Inspiron 5584
Papersize: a4
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.19.0-35-generic 
root=UUID=e080f2c9-2ee1-4e8a-a8e4-01af8fec25a1 ro quiet splash vt.handoff=7
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-35-generic 
root=UUID=e080f2c9-2ee1-4e8a-a8e4-01af8fec25a1 ro quiet splash vt.handoff=7
Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.21.1ubuntu2.1
 apt  2.4.8
SourcePackage: cups
Title: package cups 2.4.1op1-1ubuntu4.1 failed to install/upgrade: o 
subprocesso instalado, do pacote cups, o script post-installation foi morto 
pelo sinal (Erro no barramento), gerou um core
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/04/2020
dmi.bios.release: 1.12
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.12.0
dmi.board.name: 012D2F
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.12.0:bd11/04/2020:br1.12:svnDellInc.:pnInspiron5584:pvr:rvnDellInc.:rn012D2F:rvrA00:cvnDellInc.:ct10:cvr:sku08FA:
dmi.product.family: Inspiron
dmi.product.name: Inspiron 5584
dmi.product.sku: 08FA
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-package jammy
-- 
package cups 2.4.1op1-1ubuntu4.1 failed to install/upgrade: o subprocesso 
instalado, do pacote cups, o script post-installation foi morto pelo sinal 
(Erro no barramento), gerou um core
https://bugs.launchpad.net/bugs/2012781
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to cups in Ubuntu.

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

[Desktop-packages] [Bug 2012736] Re: language and region > login screen > formats does not display United Kingdom

2023-03-24 Thread Gunnar Hjalmarsson

Thanks. That helped me reproduce it. It's an upstream thing, and I
reported it via the linked upstream issue.

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

** Changed in: gnome-control-center (Ubuntu)
   Status: Incomplete => In Progress

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

** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/-/issues #2418
   https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2418

** Also affects: gnome-control-center via
   https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2418
   Importance: Unknown
   Status: Unknown

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

Title:
  language and region > login screen > formats does not display United
  Kingdom

Status in gnome-control-center:
  Unknown
Status in gnome-control-center package in Ubuntu:
  In Progress

Bug description:
  When there are multiple accounts on a machine the "Language and
  Region" settings screen shows a "Login Screen" section. Under the
  "Formats", if "Canada" is selected then the UI shows "Canada",
  however, if "United Kingdom" is selected then the Formats section
  displays "United States".

  It displays correctly under the "Your Account" section.

  I have attached a screen recording to demonstrate.

  This is on Lunar.

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


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

[Desktop-packages] [Bug 2012778] Re: Totem crashing with OpenGL error

2023-03-24 Thread Ubuntu QA Website

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
https://iso.qa.ubuntu.com/qatracker/reports/bugs/2012778

** Tags added: iso-testing

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

Title:
  Totem crashing with OpenGL error

Status in totem package in Ubuntu:
  New

Bug description:
  Release: Lunar development branch, desktop, 03/24/23 GMT-5
  Totem: Version 43.0-2ubuntu1 (candidate)

  GNOME totem crashes when launched from terminal while conducting test
  case for the ARM Lunar daily build on Raspberry Pi. Journal readout
  indicates failed assertion of window stack position as well as
  inconsistent timestamps between window switches, though this could not
  be narrowed down to Totem specifically.

  Command: totem big_buck_bunny_720p_surround.mp4
  Expectation: Video Player to open and play the video in question.
  Result: Video Player opened with no playback and an error message reading 
"Could not initialise OpenGL support."

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


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

[Desktop-packages] [Bug 2012778] Re: Totem crashing with OpenGL error

2023-03-24 Thread Paul White

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

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

Title:
  Totem crashing with OpenGL error

Status in totem package in Ubuntu:
  New

Bug description:
  Release: Lunar development branch, desktop, 03/24/23 GMT-5
  Totem: Version 43.0-2ubuntu1 (candidate)

  GNOME totem crashes when launched from terminal while conducting test
  case for the ARM Lunar daily build on Raspberry Pi. Journal readout
  indicates failed assertion of window stack position as well as
  inconsistent timestamps between window switches, though this could not
  be narrowed down to Totem specifically.

  Command: totem big_buck_bunny_720p_surround.mp4
  Expectation: Video Player to open and play the video in question.
  Result: Video Player opened with no playback and an error message reading 
"Could not initialise OpenGL support."

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


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

[Desktop-packages] [Bug 2012778] [NEW] Totem crashing with OpenGL error

You have been subscribed to a public bug:

Release: Lunar development branch, desktop, 03/24/23 GMT-5
Totem: Version 43.0-2ubuntu1 (candidate)

GNOME totem crashes when launched from terminal while conducting test
case for the ARM Lunar daily build on Raspberry Pi. Journal readout
indicates failed assertion of window stack position as well as
inconsistent timestamps between window switches, though this could not
be narrowed down to Totem specifically.

Command: totem big_buck_bunny_720p_surround.mp4
Expectation: Video Player to open and play the video in question.
Result: Video Player opened with no playback and an error message reading 
"Could not initialise OpenGL support."

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


** Tags: arm arm64 desktop gnome graphics lunar opengl player raspi totem video
-- 
Totem crashing with OpenGL error
https://bugs.launchpad.net/bugs/2012778
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to totem in Ubuntu.

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

[Desktop-packages] [Bug 2012288] Re: Ubuntu Gnome Settings / Chrome / CUPS (printing) communications

2023-03-24 Thread beadon

Update, I found that CUPS was failing to be modified by the gnome(?)
user interface component.

apparmor is getting in the way, "protecting" cupsd.


To fix this, install the apparmor utilities:

sudo apt-get install apparmor-utils


Then set apparmor to complain about cupsd, instead of blocking access:

sudo aa-complain cupsd


You can now print.  I hope this helps someone else too.  This was quite 
difficult to troubleshoot.


ar 24 16:10:45 semiauto google-chrome.desktop[216920]: 
[216913:216943:0324/161045.967690:ERROR:connection_factory_impl.cc(428)] Failed 
to connect to MCS endpoint with error -105
Mar 24 16:10:46 semiauto google-chrome.desktop[216920]: 
[216913:216913:0324/161046.442656:ERROR:device_event_log_impl.cc(222)] 
[16:10:46.442] Printer: local_printer_handler_default.cc:167 Failure 
enumerating local printers, result: kFailed
Mar 24 16:10:46 semiauto google-chrome.desktop[216920]: Warning: disabling flag 
--expose_wasm due to conflicting flags
Mar 24 16:10:51 semiauto google-chrome.desktop[216920]: 
/usr/share/system-config-printer/system-config-printer.py:325: 
DeprecationWarning: Gtk.ActionGroup.list_actions is deprecated
Mar 24 16:10:51 semiauto google-chrome.desktop[216920]:   for action in 
printer_manager_action_group.list_actions ():
Mar 24 16:10:51 semiauto google-chrome.desktop[216920]: 
/usr/share/system-config-printer/system-config-printer.py:326: 
DeprecationWarning: Gtk.Action.set_sensitive is deprecated
Mar 24 16:10:51 semiauto google-chrome.desktop[216920]:   action.set_sensitive 
(False)
Mar 24 16:10:51 semiauto google-chrome.desktop[216920]: 
/usr/share/system-config-printer/system-config-printer.py:334: 
DeprecationWarning: Gtk.ActionGroup.get_action is deprecated
Mar 24 16:10:51 semiauto google-chrome.desktop[216920]:   act = 
printer_manager_action_group.get_action (action)
Mar 24 16:10:51 semiauto google-chrome.desktop[216920]: 
/usr/share/system-config-printer/system-config-printer.py:364: 
DeprecationWarning: Gtk.UIManager.ensure_update is deprecated
Mar 24 16:10:51 semiauto google-chrome.desktop[216920]:   
self.ui_manager.ensure_update ()
Mar 24 16:10:51 semiauto google-chrome.desktop[216920]: 
/usr/share/system-config-printer/system-config-printer.py:365: 
DeprecationWarning: Gtk.UIManager.get_accel_group is deprecated
Mar 24 16:10:51 semiauto google-chrome.desktop[216920]:   
self.PrintersWindow.add_accel_group (self.ui_manager.get_accel_group ())
Mar 24 16:10:51 semiauto google-chrome.desktop[216920]: 
/usr/share/system-config-printer/system-config-printer.py:374: 
DeprecationWarning: Gtk.UIManager.get_action is deprecated
Mar 24 16:10:51 semiauto google-chrome.desktop[216920]:   action = 
self.ui_manager.get_action ("/new-printer")
Mar 24 16:10:51 semiauto google-chrome.desktop[216920]: 
/usr/share/system-config-printer/system-config-printer.py:375: 
DeprecationWarning: Gtk.Action.create_menu_item is deprecated
Mar 24 16:10:51 semiauto google-chrome.desktop[216920]:   newprinteritem = 
action.create_menu_item ()
Mar 24 16:10:51 semiauto google-chrome.desktop[216920]: 
/usr/share/system-config-printer/system-config-printer.py:673: 
DeprecationWarning: Gtk.Action.get_proxies is deprecated
Mar 24 16:10:51 semiauto google-chrome.desktop[216920]:   for widget in 
action.get_proxies ():
Mar 24 16:10:51 semiauto google-chrome.desktop[216920]: 
/usr/share/system-config-printer/system-config-printer.py:2253: 
DeprecationWarning: Gdk.threads_enter is deprecated
Mar 24 16:10:51 semiauto google-chrome.desktop[216920]:   Gdk.threads_enter ()
Mar 24 16:10:51 semiauto dbus-daemon[764]: [system] Activating via systemd: 
service name='org.freedesktop.hostname1' 
unit='dbus-org.freedesktop.hostname1.service' requested by ':1.1686' (uid=1000 
pid=395280 comm="/usr/bin/python3 /usr/share/system-config-printer/" 
label="unconfined")
Mar 24 16:10:51 semiauto systemd[1]: Starting Hostname Service...
Mar 24 16:10:51 semiauto dbus-daemon[764]: [system] Successfully activated 
service 'org.freedesktop.hostname1'
Mar 24 16:10:51 semiauto systemd[1]: Started Hostname Service.
Mar 24 16:10:53 semiauto kernel: [663246.142511] serial :00:16.3: LSR 
safety check engaged!
Mar 24 16:10:53 semiauto kernel: [663246.142539] audit: type=1400 
audit(1679688653.733:100): apparmor="DENIED" operation="capable" class="cap" 
profile="/usr/sbin/cupsd" pid=395323 comm="serial" capability=21  
capname="sys_admin"


Here were a few other telling messages:
Mar 24 16:13:14 semiauto kernel: [663387.182005] audit: type=1400 
audit(1679688794.769:101): apparmor="DENIED" operation="file_lock" class="file" 
profile="/usr/sbin/cupsd" name="/run/utmp" pid=287961 comm="cupsd" 
requested_mask="k" denied_mask="k" fsuid=0 ouid=0
Mar 24 16:13:17 semiauto kernel: [663389.718118] audit: type=1400 
audit(1679688797.305:102): apparmor="DENIED" operation="file_lock" class="file" 
profile="/usr/sbin/cupsd" name="/run/utmp" pid=287961 comm="cupsd" 
requested_mask="k" denied_mask="k" fsuid=0 ouid=0
Mar 24 16:13:24 semiauto

[Desktop-packages] [Bug 2012762] [NEW] If fonts-ubuntu isn't installed, the initramfs plymouth hook fails at fc-cache

2023-03-24 Thread feren

Public bug reported:

If you remove fonts-ubuntu from your system, or never have said package 
installed in the first place, and have plymouth installed, and try to 
update-initramfs, the hook at /usr/share/initramfs-tools/hooks/plymouth will 
abort, causing the update-initramfs command to fail.
While semi-unrelated, in the case of an APT operation triggering 
initramfs-tools, this would also lead to package management failure (which can 
cause an endless loop of package management failure as APT may attempt, and 
fail, to run update-initramfs before it ever tries to install other packages 
such as fonts-ubuntu).

The script fails at line 147 (fc-cache) and removing the output
disabling contents at the end of the command reveals that it fails to
read /usr/share/fonts - upon further inspection /usr/share/fonts indeed
never exists, with these conditions in effect, inside the initramfs
being created.

It appears that having fonts-ubuntu installed leads to a mkdir command
right before that command, which only runs if the Ubuntu fonts exist,
creating /usr/share/fonts while it's in the process of creating a
directory to copy those fonts to.

This can be fixed by adding this command underneath 'mkdir -p 
"${DESTDIR}/usr/local/share/fonts"':
mkdir -p "${DESTDIR}/usr/share/fonts"

Ubuntu version: 22.04.2
plymouth version: 0.9.5+git20211018-1ubuntu3

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

** Description changed:

- If you remove fonts-ubuntu from your system, or never have said package 
installed in the first place, and have plymouth installed, and try to 
`update-initramfs`, the hook at /usr/share/initramfs-tools/hooks/plymouth will 
exit code 1, causing the former to also fail.
+ If you remove fonts-ubuntu from your system, or never have said package 
installed in the first place, and have plymouth installed, and try to 
update-initramfs, the hook at /usr/share/initramfs-tools/hooks/plymouth will 
abort, causing the update-initramfs command to fail.
  While semi-unrelated, in the case of an APT operation triggering 
initramfs-tools, this would also lead to package management failure (which can 
cause an endless loop of package management failure as APT may attempt, and 
fail, to run update-initramfs before it ever tries to install fonts-ubuntu).
  
  The script fails at line 147, fc-cache, and removing the output
  disabling contents at the end of the command reveals that it fails to
  read /usr/share/fonts - upon further inspection /usr/share/fonts indeed
  never exists, with these conditions in effect, inside the initramfs
  being created.
  
  It appears that having fonts-ubuntu installed leads to a mkdir command
  right before that command, which only runs if the Ubuntu fonts exist,
  creating /usr/share/fonts while it's in the process of creating a
  directory to copy those fonts to.
  
  This can be fixed by adding this command underneath 'mkdir -p 
"${DESTDIR}/usr/local/share/fonts"':
  mkdir -p "${DESTDIR}/usr/share/fonts"
  
  It wouldn't clash with the aforementioned Ubuntu-fonts-only mkdir as it
  would run before it.
  
- 
  Ubuntu version: 22.04.2
  plymouth version: 0.9.5+git20211018-1ubuntu3

** Description changed:

  If you remove fonts-ubuntu from your system, or never have said package 
installed in the first place, and have plymouth installed, and try to 
update-initramfs, the hook at /usr/share/initramfs-tools/hooks/plymouth will 
abort, causing the update-initramfs command to fail.
- While semi-unrelated, in the case of an APT operation triggering 
initramfs-tools, this would also lead to package management failure (which can 
cause an endless loop of package management failure as APT may attempt, and 
fail, to run update-initramfs before it ever tries to install fonts-ubuntu).
+ While semi-unrelated, in the case of an APT operation triggering 
initramfs-tools, this would also lead to package management failure (which can 
cause an endless loop of package management failure as APT may attempt, and 
fail, to run update-initramfs before it ever tries to install other packages 
such as fonts-ubuntu).
  
  The script fails at line 147, fc-cache, and removing the output
  disabling contents at the end of the command reveals that it fails to
  read /usr/share/fonts - upon further inspection /usr/share/fonts indeed
  never exists, with these conditions in effect, inside the initramfs
  being created.
  
  It appears that having fonts-ubuntu installed leads to a mkdir command
  right before that command, which only runs if the Ubuntu fonts exist,
  creating /usr/share/fonts while it's in the process of creating a
  directory to copy those fonts to.
  
  This can be fixed by adding this command underneath 'mkdir -p 
"${DESTDIR}/usr/local/share/fonts"':
  mkdir -p "${DESTDIR}/usr/share/fonts"
  
  It wouldn't clash with the aforementioned Ubuntu-fonts-only mkdir as it
  would run before it.
  
  Ubuntu version: 22.04.2
  plymouth version:

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

2023-03-24 Thread Batuhan

> I think this is down to a race condition between gnome-shell and
snapd.

As someone who is using Kubuntu where gnome-shell is not present, I'd
like to mention that I'm also experiencing the same exact issue. Not
sure if there is a similar race condition is present on a KDE
application in Kubuntu (like Konsole?) but this feels like more of a
snap problem than a GNOME problem.

Adding snap version since I missed the chance of doing so in the last
post:

❯ snap version
snap2.58.3+23.04ubuntu1
snapd   2.58.3+23.04ubuntu1
series  16
ubuntu  23.04
kernel  6.2.7-060207-generic

Also I was able to record a trace of `SNAPD_DEBUG=1 krunner --replace
slack` which includes a bit more information (not sure how useful)



** Attachment added: "logs.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2011806/+attachment/5657354/+files/logs.txt

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

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

Status in gnome-shell package in Ubuntu:
  In Progress

Bug description:
  Hi,

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

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

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

  Recent updates included gnome-shell and libadwaita.

  ---

  I get this type of log for all problematic snaps:

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

  ---

  Context:

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

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

To

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

2023-03-24 Thread Batuhan

Not super how much it helps, but I have the same exact issue on two
different systems (one using Kubuntu 22.10 -- with a mainline kernel of
6.0 and the other one using Kubuntu 23.04 [upgraded from 22.10]
development branch with a mainline kernel of 6.2.7).

This specifically happens when krunner is used to launch an application,
and it happens randomly (even in the same session; but I noticed that it
is less likely to happen when the first session started and more likely
to happen after you start a few apps).

Here is what I get when I run krunner and choose slack to launch.

❯ krunner --replace
/user.slice/user-1000.slice/user@1000.service/app.slice/app-slack_slack-7092918b60f045318ad5898c1cd14a71.scope
 is not a snap cgroup

First attempt fails with this, but then I try it again and it works (2nd
attempt). I quite and try to launch it again, but this time first two
attempts fail and the third one succeeds and launches slack again.

/user.slice/user-1000.slice/user@1000.service/app.slice/app-slack_slack-e699191c66c043c49b21af01db44a21f.scope
 is not a snap cgroup
/user.slice/user-1000.slice/user@1000.service/app.slice/app-slack_slack-a38502fd65ca425ebdf9b3cbac2d154c.scope
 is not a snap cgroup

❯ echo $DBUS_SESSION_BUS_ADDRESS
unix:path=/run/user/1000/bus

Everything I have is stock Kubuntu 23.04 (I'm updating it each day)
except the mainline kernel (which is needed for the graphics driver).

System: AMD Ryzen 9 7950X as both the CPU and iGPU.

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

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

Status in gnome-shell package in Ubuntu:
  In Progress

Bug description:
  Hi,

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

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

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

  Recent updates included gnome-shell and libadwaita.

  ---

  I get this type of log for all problematic snaps:

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

  ---

  Context:

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

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

[Desktop-packages] [Bug 2012736] Re: language and region > login screen > formats does not display United Kingdom

I've been able to re-create the issue on my laptop after adding a second
user so not sure what the difference is in my setups. As requested:

```
[I] tim@saturn ~> cat /etc/default/locale
LANG=en_GB.UTF-8
[I] tim@saturn ~> locale -a
C
C.utf8
en_AG
en_AG.utf8
en_AU.utf8
en_BW.utf8
en_CA.utf8
en_DK.utf8
en_GB.utf8
en_HK.utf8
en_IE.utf8
en_IL
en_IL.utf8
en_IN
en_IN.utf8
en_NG
en_NG.utf8
en_NZ.utf8
en_PH.utf8
en_SG.utf8
en_US.utf8
en_ZA.utf8
en_ZM
en_ZM.utf8
en_ZW.utf8
POSIX
[I] tim@saturn ~> locale
LANG=en_GB.UTF-8
LANGUAGE=en_GB:en
LC_CTYPE="en_GB.UTF-8"
LC_NUMERIC="en_GB.UTF-8"
LC_TIME="en_GB.UTF-8"
LC_COLLATE="en_GB.UTF-8"
LC_MONETARY="en_GB.UTF-8"
LC_MESSAGES="en_GB.UTF-8"
LC_PAPER="en_GB.UTF-8"
LC_NAME="en_GB.UTF-8"
LC_ADDRESS="en_GB.UTF-8"
LC_TELEPHONE="en_GB.UTF-8"
LC_MEASUREMENT="en_GB.UTF-8"
LC_IDENTIFICATION="en_GB.UTF-8"
LC_ALL=
```

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

Title:
  language and region > login screen > formats does not display United
  Kingdom

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

Bug description:
  When there are multiple accounts on a machine the "Language and
  Region" settings screen shows a "Login Screen" section. Under the
  "Formats", if "Canada" is selected then the UI shows "Canada",
  however, if "United Kingdom" is selected then the Formats section
  displays "United States".

  It displays correctly under the "Your Account" section.

  I have attached a screen recording to demonstrate.

  This is on Lunar.

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


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

[Desktop-packages] [Bug 2012757] [NEW] Incorrect total system memory

2023-03-24 Thread Adrian Feliks

Public bug reported:

Gnome System Monitor has been incorrectly showing the amount of RAM for
some time (months?). Based on the system logs, I was able to determine
that Gnome System Monitor has not been updated recently. So where is the
incorrect data coming from?

Gnome System Monitor:
RAM: 33.5 GB
SWAP: 1.5 GB

$ free
totalusedfree shared buff/cache available
Mem:3270654012241184 5677344 12234281478801211034196
Swap:1459904 0 1459904

Everything indicates that Gnome System Monitor as RAM, gives the amount of RAM
+ SWAP. Why? Before that, the indications were correct - 32 GB RAM.
In addition, SWAP is shown separately.

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

** Description changed:

Gnome System Monitor:
RAM: 33.5 GB
SWAP: 1.5 GB

-
$ free
-totalusedfree shared buff/cache
available
+ totalusedfree shared buff/cache
available
Mem:3270654012241184 5677344 122342814788012
11034196
Swap:1459904 0 1459904

- Everything indicates that Gnome System Monitor as RAM, gives the amount of
RAM + SWAP. Why?
+ Everything indicates that Gnome System Monitor as RAM, gives the amount of
RAM + SWAP. Why? Before that, the indications were correct - 32 GB RAM.
In addition, SWAP is shown separately.

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

Title:
Incorrect total system memory

Status in gnome-system-monitor package in Ubuntu:
New

Bug description:
Gnome System Monitor has been incorrectly showing the amount of RAM
for some time (months?). Based on the system logs, I was able to
determine that Gnome System Monitor has not been updated recently. So
where is the incorrect data coming from?

Gnome System Monitor:
RAM: 33.5 GB
SWAP: 1.5 GB

$ free
totalusedfree shared buff/cache
available
Mem:3270654012241184 5677344 122342814788012
11034196
Swap:1459904 0 1459904

Everything indicates that Gnome System Monitor as RAM, gives the amount of
RAM + SWAP. Why? Before that, the indications were correct - 32 GB RAM.
In addition, SWAP is shown separately.

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

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

Re: [Desktop-packages] [Bug 1532508] Re: Screen contents revealed briefly on resume, before even unlocking

2023-03-24 Thread Free Beachler

To a non-maintainer-but-longtime-user, it appears that the lock screen
implementation in Gnome (or whatever OS stack) is completely broken -> it
isn't secure, breaks NVIDIA drivers, inexplicably shows a different
rendition (version) of the lockscreen in some cases, and doesn't work with
popular screen savers from the Software manager.

But I suppose it all works for some people.


On Fri, Mar 24, 2023 at 2:15 AM Ralf Dünkelmann <1532...@bugs.launchpad.net>
wrote:

> Hi there,
>
> I am using ubuntu budgie 22 on a tuxedo laptop and can reproduce
> reveiling of content when I lock the screen and connect to an external
> monitor afterwards. When connecting the monitor the lower part of the
> screen is reveiled shortly. When disconnecting the monitor, the upper
> part reveils (and stays visible). Everything before typing the password.
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1935690).
> https://bugs.launchpad.net/bugs/1532508
>
> Title:
>   Screen contents revealed briefly on resume, before even unlocking
>
> Status in GNOME Shell:
>   New
> Status in Mutter:
>   New
> Status in gnome-shell package in Ubuntu:
>   Confirmed
> Status in unity package in Ubuntu:
>   Fix Released
> Status in unity source package in Xenial:
>   Fix Released
> Status in gnome-shell package in Debian:
>   Confirmed
>
> Bug description:
>   [Impact]
>
>   When lock is enabled, the screen doesn't get blank/covered by
>   lockscreen before suspending, thus on early resume the content might
>   be shown.
>
>   Video showing the bug: https://youtu.be/dDOgtK1MldI
>
>   Reproduced on Ubuntu 2015.10, Ubuntu 2014.04
>
>   [Test case]
>
>   1. Work on highly secret files
>   2. Close the lid of your laptop and go have a break
>   3. Anyone who opens the lid of the laptop can see the secret files for a
> half second before the lock screen appears
>
>   [Possible Regression]
>
>   Content on screen isn't painted anymore and screen stays black.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/gnome-shell/+bug/1532508/+subscriptions
>
>

-- 
This electronic mail (including any attachments) may contain information
that is privileged, confidential, and/or otherwise protected from
disclosure to anyone other than its intended recipient(s). Any
dissemination or use of this electronic mail or its contents (including any
attachments) by persons other than the intended recipient(s) is strictly
prohibited. If you have received this message in error, please notify me
immediately by reply e-mail so that I may correct my records, then please
delete the original message (including any attachments) in its entirety.
Thank you.

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

Title:
  Screen contents revealed briefly on resume, before even unlocking

Status in GNOME Shell:
  New
Status in Mutter:
  New
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Fix Released
Status in unity source package in Xenial:
  Fix Released
Status in gnome-shell package in Debian:
  Confirmed

Bug description:
  [Impact]

  When lock is enabled, the screen doesn't get blank/covered by
  lockscreen before suspending, thus on early resume the content might
  be shown.

  Video showing the bug: https://youtu.be/dDOgtK1MldI

  Reproduced on Ubuntu 2015.10, Ubuntu 2014.04

  [Test case]

  1. Work on highly secret files
  2. Close the lid of your laptop and go have a break
  3. Anyone who opens the lid of the laptop can see the secret files for a half 
second before the lock screen appears

  [Possible Regression]

  Content on screen isn't painted anymore and screen stays black.

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


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

[Desktop-packages] [Bug 2011770] Autopkgtest regression report (gnome-settings-daemon/43.0-1ubuntu1.1)

2023-03-24 Thread Ubuntu SRU Bot

All autopkgtests for the newly accepted gnome-settings-daemon (43.0-1ubuntu1.1) 
for kinetic have finished running.
The following regressions have been reported in tests triggered by the package:

mutter/43.0-1ubuntu4 (amd64, arm64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/kinetic/update_excuses.html#gnome-settings-daemon

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  [gsd-rfkill] WwanEnabled never get synced

Status in OEM Priority Project:
  Triaged
Status in gnome-settings-daemon package in Ubuntu:
  Fix Released
Status in gnome-settings-daemon source package in Jammy:
  Fix Committed
Status in gnome-settings-daemon source package in Kinetic:
  Fix Committed

Bug description:
  [ Impact ]

   * Sometimes on devices with WWAN card, whenever user presses the
  wireless function key (Fn+F8) or turn on the airplane mode radio
  button in Settings, the airplane mode will not be enabled, and the
  airplane mode icon is not shown in the status bar.

   * There is a unmerged upstream merge request that delivers the fix:
  https://gitlab.gnome.org/GNOME/gnome-settings-
  daemon/-/merge_requests/310

  It works perfectly well on several Lenovo laptops with WWAN cards.
  The root causes is that the value of "WwanEnabled" under 
"org.freedesktop.NetworkManager" is not synced correctly, gsd-rfkill should 
listen to "g-properties-changed" instead of "g-signal" now.

  [ Test Plan ]

   1. Find a machine which has WWAN card.
   2. Boot the machine, and run rfkill list to see if WWAN is unblocked. if not 
use rfkill to unblock the WWAN, and reboot.
   3. Press the wireless media key (Fn+F8) or turn on the airplane mode radio 
button in Settings.
   4. The airplane mode should be enabled, but actually not.

  [ Where problems could occur ]

   * When user is using a very low version network-manager (< 1.20) that
  still broadcasting DBUS "PropertiesChanged" events on "g-signal"
  instead of the concurrent "g-properties-changed", the airplane mode
  will sometimes not be able to enable.

  [1]: 
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/853
  [2]: 
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/6fb917178aa19c61e909957f5146aa4565e0cb2f

  [ Other Info ]

  1. About Ubuntu
  Description:Ubuntu 22.04.2 LTS
  Release:22.04
  Kernel: 6.1.0-1007-oem

  2. The version of packages:
  gnome-settings-daemon:
    Installed: 42.1-1ubuntu2.1

  network-manager:
    Installed: 1.36.6-0ubuntu2

  3. Expect:
  The function nm_signal(plugins/rfkill/gsd-rfkill-manager.c) is called, and 
manager->wwan_enabled is set to the correct value.

  4. Actual:
  The function nm_signal(plugins/rfkill/gsd-rfkill-manager.c) is never called, 
so manager->wwan_enabled is not synced, If machine has WWAN device(s), and the 
initial value of manager->wwan_enabled is true, it will never be able to switch 
to airplane mode.

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


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

[Desktop-packages] [Bug 2012734] Re: no audio after update

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

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

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

Title:
  no audio after update

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Description:  Ubuntu 22.10
  Release:  22.10

  
  during normal patching Ubuntu pushed from kernel 5.19.0-31 to 5.19.0-35. 
After this push, I lost audio from my AMD RX570 hdmi. I booted back to -31 
waiting for the next kernel push in the hopes the problem would be caught and 
addressed. It wasn't, and still persists in -38. The card info is below and was 
taken while booted into -38.

  01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] (rev ef)
  01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere HDMI 
Audio [Radeon RX 470/480 / 570/580/590]

  root@x:~# hwinfo --sound
  35: PCI 100.1: 0403 Audio device
  [Created at pci.386]
  Unique ID: NXNs.TsyFmhFLPLA
  Parent ID: mnDB.fA+tdbAkMSD
  SysFS ID: /devices/pci:00/:00:01.1/:01:00.1
  SysFS BusID: :01:00.1
  Hardware Class: sound
  Model: "ATI Ellesmere HDMI Audio [Radeon RX 470/480 / 570/580/590]"
  Vendor: pci 0x1002 "ATI Technologies Inc"
  Device: pci 0xaaf0 "Ellesmere HDMI Audio [Radeon RX 470/480 / 570/580/590]"
  SubVendor: pci 0x1458 "Gigabyte Technology Co., Ltd"
  SubDevice: pci 0xaaf0
  Driver: "snd_hda_intel"
  Driver Modules: "snd_hda_intel"
  Memory Range: 0xfcf6-0xfcf63fff (rw,non-prefetchable)
  IRQ: 86 (5 events)
  Module Alias: "pci:v1002dAAF0sv1458sdAAF0bc04sc0 3i00"
  Driver Info #0:
  Driver Status: snd_hda_intel is active
  Driver Activation Cmd: "modprobe snd_hda_intel"
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #31 (PCI bridge)


  The errors I am getting during intialization are:

  [ 4.895282] hdaudio hdaudioC0D0: no AFG or MFG node found
  [ 4.895306] snd_hda_intel :01:00.1: no codecs initialized

  
  and if I try to validate the card

  root@x:~# aplay -l
  aplay: device_list:274: no soundcards found...

  I have tried passing numerous arguments to the module but to no avail.
  Booting back to -31 brings the card right back to fully functioning. I
  believe there has been an update to snd_hda_intel which is causing
  this issue and is most likely a regression situation. Can anyone
  assist? I have searched for a model to be passed specific to AMD
  cards, but can't find one. Any suggestions would be greatly
  appreciated. Additionally, I'm wondering if this should be directed to
  Ubuntu, or should it go to kernel.org the HD-Audio group? Again,
  thanks for your thoughts.

  options snd_hda_intel dmic_detect=0
  options snd_hda_intel model=generic
  options snd_hda_intel model=auto
  options snd_hda_intel probe_mask=1
  options snd-intel-dspcfg dsp_driver=1

  Under -31 the error messages are not displayed, sound works. If I
  again validate, I get the below:

  root@media2:~# aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: HDMI [HDA ATI HDMI], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: HDMI [HDA ATI HDMI], device 7: HDMI 1 [HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: HDMI [HDA ATI HDMI], device 8: HDMI 2 [HDMI 2]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: HDMI [HDA ATI HDMI], device 9: HDMI 3 [65Q825]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: HDMI [HDA ATI HDMI], device 10: HDMI 4 [HDMI 4]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: HDMI [HDA ATI HDMI], device 11: HDMI 5 [HDMI 5]
Subdevices: 1/1
Subdevice #0: subdevice #0

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: pulseaudio 1:16.1+dfsg1-1ubuntu3.1
  ProcVersionSignature: Ubuntu 5.19.0-38.39-generic 5.19.17
  Uname: Linux 5.19.0-38-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:gdm1585 F pipewire
  CasperMD5CheckResult: unknown
  Date: Fri Mar 24 07:45:50 2023
  InstallationDate: Installed on 2019-05-09 (1415 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  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 kinetic on 2023-01-13 (69 days ago)
  dmi.bios.date: 11/27/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F50

[Desktop-packages] [Bug 2012736] Re: language and region > login screen > formats does not display United Kingdom

2023-03-24 Thread Gunnar Hjalmarsson

Thanks for your report. I made a quick test, and couldn't reproduce the
behavior.

After having set "United Kingdom", can you please run the below terminal
commands and show us what they output in a comment here.

cat /etc/default/locale

locale -a

locale

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

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

Title:
  language and region > login screen > formats does not display United
  Kingdom

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

Bug description:
  When there are multiple accounts on a machine the "Language and
  Region" settings screen shows a "Login Screen" section. Under the
  "Formats", if "Canada" is selected then the UI shows "Canada",
  however, if "United Kingdom" is selected then the Formats section
  displays "United States".

  It displays correctly under the "Your Account" section.

  I have attached a screen recording to demonstrate.

  This is on Lunar.

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


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

[Desktop-packages] [Bug 2011770] Autopkgtest regression report (gnome-settings-daemon/42.1-1ubuntu2.2)

2023-03-24 Thread Ubuntu SRU Bot

All autopkgtests for the newly accepted gnome-settings-daemon (42.1-1ubuntu2.2) 
for jammy have finished running.
The following regressions have been reported in tests triggered by the package:

mutter/42.5-0ubuntu1 (ppc64el)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#gnome-settings-daemon

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  [gsd-rfkill] WwanEnabled never get synced

Status in OEM Priority Project:
  Triaged
Status in gnome-settings-daemon package in Ubuntu:
  Fix Released
Status in gnome-settings-daemon source package in Jammy:
  Fix Committed
Status in gnome-settings-daemon source package in Kinetic:
  Fix Committed

Bug description:
  [ Impact ]

   * Sometimes on devices with WWAN card, whenever user presses the
  wireless function key (Fn+F8) or turn on the airplane mode radio
  button in Settings, the airplane mode will not be enabled, and the
  airplane mode icon is not shown in the status bar.

   * There is a unmerged upstream merge request that delivers the fix:
  https://gitlab.gnome.org/GNOME/gnome-settings-
  daemon/-/merge_requests/310

  It works perfectly well on several Lenovo laptops with WWAN cards.
  The root causes is that the value of "WwanEnabled" under 
"org.freedesktop.NetworkManager" is not synced correctly, gsd-rfkill should 
listen to "g-properties-changed" instead of "g-signal" now.

  [ Test Plan ]

   1. Find a machine which has WWAN card.
   2. Boot the machine, and run rfkill list to see if WWAN is unblocked. if not 
use rfkill to unblock the WWAN, and reboot.
   3. Press the wireless media key (Fn+F8) or turn on the airplane mode radio 
button in Settings.
   4. The airplane mode should be enabled, but actually not.

  [ Where problems could occur ]

   * When user is using a very low version network-manager (< 1.20) that
  still broadcasting DBUS "PropertiesChanged" events on "g-signal"
  instead of the concurrent "g-properties-changed", the airplane mode
  will sometimes not be able to enable.

  [1]: 
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/853
  [2]: 
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/6fb917178aa19c61e909957f5146aa4565e0cb2f

  [ Other Info ]

  1. About Ubuntu
  Description:Ubuntu 22.04.2 LTS
  Release:22.04
  Kernel: 6.1.0-1007-oem

  2. The version of packages:
  gnome-settings-daemon:
    Installed: 42.1-1ubuntu2.1

  network-manager:
    Installed: 1.36.6-0ubuntu2

  3. Expect:
  The function nm_signal(plugins/rfkill/gsd-rfkill-manager.c) is called, and 
manager->wwan_enabled is set to the correct value.

  4. Actual:
  The function nm_signal(plugins/rfkill/gsd-rfkill-manager.c) is never called, 
so manager->wwan_enabled is not synced, If machine has WWAN device(s), and the 
initial value of manager->wwan_enabled is true, it will never be able to switch 
to airplane mode.

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


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

[Desktop-packages] [Bug 2012734] Re: no audio after update

2023-03-24 Thread Ubuntu Foundations Team Bug Bot

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

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

Title:
  no audio after update

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu 22.10
  Release:  22.10

  
  during normal patching Ubuntu pushed from kernel 5.19.0-31 to 5.19.0-35. 
After this push, I lost audio from my AMD RX570 hdmi. I booted back to -31 
waiting for the next kernel push in the hopes the problem would be caught and 
addressed. It wasn't, and still persists in -38. The card info is below and was 
taken while booted into -38.

  01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] (rev ef)
  01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere HDMI 
Audio [Radeon RX 470/480 / 570/580/590]

  root@x:~# hwinfo --sound
  35: PCI 100.1: 0403 Audio device
  [Created at pci.386]
  Unique ID: NXNs.TsyFmhFLPLA
  Parent ID: mnDB.fA+tdbAkMSD
  SysFS ID: /devices/pci:00/:00:01.1/:01:00.1
  SysFS BusID: :01:00.1
  Hardware Class: sound
  Model: "ATI Ellesmere HDMI Audio [Radeon RX 470/480 / 570/580/590]"
  Vendor: pci 0x1002 "ATI Technologies Inc"
  Device: pci 0xaaf0 "Ellesmere HDMI Audio [Radeon RX 470/480 / 570/580/590]"
  SubVendor: pci 0x1458 "Gigabyte Technology Co., Ltd"
  SubDevice: pci 0xaaf0
  Driver: "snd_hda_intel"
  Driver Modules: "snd_hda_intel"
  Memory Range: 0xfcf6-0xfcf63fff (rw,non-prefetchable)
  IRQ: 86 (5 events)
  Module Alias: "pci:v1002dAAF0sv1458sdAAF0bc04sc0 3i00"
  Driver Info #0:
  Driver Status: snd_hda_intel is active
  Driver Activation Cmd: "modprobe snd_hda_intel"
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #31 (PCI bridge)


  The errors I am getting during intialization are:

  [ 4.895282] hdaudio hdaudioC0D0: no AFG or MFG node found
  [ 4.895306] snd_hda_intel :01:00.1: no codecs initialized

  
  and if I try to validate the card

  root@x:~# aplay -l
  aplay: device_list:274: no soundcards found...

  I have tried passing numerous arguments to the module but to no avail.
  Booting back to -31 brings the card right back to fully functioning. I
  believe there has been an update to snd_hda_intel which is causing
  this issue and is most likely a regression situation. Can anyone
  assist? I have searched for a model to be passed specific to AMD
  cards, but can't find one. Any suggestions would be greatly
  appreciated. Additionally, I'm wondering if this should be directed to
  Ubuntu, or should it go to kernel.org the HD-Audio group? Again,
  thanks for your thoughts.

  options snd_hda_intel dmic_detect=0
  options snd_hda_intel model=generic
  options snd_hda_intel model=auto
  options snd_hda_intel probe_mask=1
  options snd-intel-dspcfg dsp_driver=1

  Under -31 the error messages are not displayed, sound works. If I
  again validate, I get the below:

  root@media2:~# aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: HDMI [HDA ATI HDMI], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: HDMI [HDA ATI HDMI], device 7: HDMI 1 [HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: HDMI [HDA ATI HDMI], device 8: HDMI 2 [HDMI 2]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: HDMI [HDA ATI HDMI], device 9: HDMI 3 [65Q825]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: HDMI [HDA ATI HDMI], device 10: HDMI 4 [HDMI 4]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: HDMI [HDA ATI HDMI], device 11: HDMI 5 [HDMI 5]
Subdevices: 1/1
Subdevice #0: subdevice #0

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: pulseaudio 1:16.1+dfsg1-1ubuntu3.1
  ProcVersionSignature: Ubuntu 5.19.0-38.39-generic 5.19.17
  Uname: Linux 5.19.0-38-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:gdm1585 F pipewire
  CasperMD5CheckResult: unknown
  Date: Fri Mar 24 07:45:50 2023
  InstallationDate: Installed on 2019-05-09 (1415 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  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 kinetic on 2023-01-13 (69 days ago)
  dmi.bios.date: 11/27/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F50
  dmi.board.asset.tag: Default string
  dmi.board.name: B450 AORUS PRO WIFI-CF

[Desktop-packages] [Bug 2012734] [NEW] no audio after update

You have been subscribed to a public bug:

Description:Ubuntu 22.10
Release:22.10


during normal patching Ubuntu pushed from kernel 5.19.0-31 to 5.19.0-35. After 
this push, I lost audio from my AMD RX570 hdmi. I booted back to -31 waiting 
for the next kernel push in the hopes the problem would be caught and 
addressed. It wasn't, and still persists in -38. The card info is below and was 
taken while booted into -38.

01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] (rev ef)
01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere HDMI 
Audio [Radeon RX 470/480 / 570/580/590]

root@x:~# hwinfo --sound
35: PCI 100.1: 0403 Audio device
[Created at pci.386]
Unique ID: NXNs.TsyFmhFLPLA
Parent ID: mnDB.fA+tdbAkMSD
SysFS ID: /devices/pci:00/:00:01.1/:01:00.1
SysFS BusID: :01:00.1
Hardware Class: sound
Model: "ATI Ellesmere HDMI Audio [Radeon RX 470/480 / 570/580/590]"
Vendor: pci 0x1002 "ATI Technologies Inc"
Device: pci 0xaaf0 "Ellesmere HDMI Audio [Radeon RX 470/480 / 570/580/590]"
SubVendor: pci 0x1458 "Gigabyte Technology Co., Ltd"
SubDevice: pci 0xaaf0
Driver: "snd_hda_intel"
Driver Modules: "snd_hda_intel"
Memory Range: 0xfcf6-0xfcf63fff (rw,non-prefetchable)
IRQ: 86 (5 events)
Module Alias: "pci:v1002dAAF0sv1458sdAAF0bc04sc0 3i00"
Driver Info #0:
Driver Status: snd_hda_intel is active
Driver Activation Cmd: "modprobe snd_hda_intel"
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #31 (PCI bridge)


The errors I am getting during intialization are:

[ 4.895282] hdaudio hdaudioC0D0: no AFG or MFG node found
[ 4.895306] snd_hda_intel :01:00.1: no codecs initialized


and if I try to validate the card

root@x:~# aplay -l
aplay: device_list:274: no soundcards found...

I have tried passing numerous arguments to the module but to no avail.
Booting back to -31 brings the card right back to fully functioning. I
believe there has been an update to snd_hda_intel which is causing this
issue and is most likely a regression situation. Can anyone assist? I
have searched for a model to be passed specific to AMD cards, but can't
find one. Any suggestions would be greatly appreciated. Additionally,
I'm wondering if this should be directed to Ubuntu, or should it go to
kernel.org the HD-Audio group? Again, thanks for your thoughts.

options snd_hda_intel dmic_detect=0
options snd_hda_intel model=generic
options snd_hda_intel model=auto
options snd_hda_intel probe_mask=1
options snd-intel-dspcfg dsp_driver=1

Under -31 the error messages are not displayed, sound works. If I again
validate, I get the below:

root@media2:~# aplay -l
 List of PLAYBACK Hardware Devices 
card 0: HDMI [HDA ATI HDMI], device 3: HDMI 0 [HDMI 0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: HDMI [HDA ATI HDMI], device 7: HDMI 1 [HDMI 1]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: HDMI [HDA ATI HDMI], device 8: HDMI 2 [HDMI 2]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: HDMI [HDA ATI HDMI], device 9: HDMI 3 [65Q825]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: HDMI [HDA ATI HDMI], device 10: HDMI 4 [HDMI 4]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: HDMI [HDA ATI HDMI], device 11: HDMI 5 [HDMI 5]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: pulseaudio 1:16.1+dfsg1-1ubuntu3.1
ProcVersionSignature: Ubuntu 5.19.0-38.39-generic 5.19.17
Uname: Linux 5.19.0-38-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/seq:gdm1585 F pipewire
CasperMD5CheckResult: unknown
Date: Fri Mar 24 07:45:50 2023
InstallationDate: Installed on 2019-05-09 (1415 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
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 kinetic on 2023-01-13 (69 days ago)
dmi.bios.date: 11/27/2019
dmi.bios.release: 5.14
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F50
dmi.board.asset.tag: Default string
dmi.board.name: B450 AORUS PRO WIFI-CF
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF50:bd11/27/2019:br5.14:svnGigabyteTechnologyCo.,Ltd.:pnB450AORUSPROWIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450AORUSPROWIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
dmi.product.family: Default string

[Desktop-packages] [Bug 2011751] Re: openbox crashed with SIGABRT

This bug was fixed in the package openbox - 3.6.1-10ubuntu1

---
openbox (3.6.1-10ubuntu1) lunar; urgency=medium

  * Cherry-pick patch from

http://git.openbox.org/?p=mikachu/openbox.git;a=commit;h=d41128e5a1002af41c976c8860f8299cfcd3cd72
to avoid crashing when switching from a fullscreen window (LP: #2011751)
  * Updated copyright file.

 -- Aaron Rainbolt   Thu, 23 Mar 2023 15:47:38
-0500

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

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

Title:
  openbox crashed with SIGABRT

Status in glib2.0 package in Ubuntu:
  Invalid
Status in openbox package in Ubuntu:
  Fix Released

Bug description:
  Lubuntu lunar (primary box) on
  - dell [optiplex] 7050 (i5-6500, 16gb, intel hd530/i915)

  I experienced a crash yesterday (openbox) but tend to ignore the first
  crashes... Whilst using the machine again today a crash occurred.

  This is my primary box, so my setup is pretty consistent

  - featherpad (restored session)
  - hexchat (irc)
  - qterminal (only single tab today; usually many)
  - firefox (snap, most sites excluding google related)
  - chromium (snap, used for anything google related)
  - telegram (snap)
  - element

  I was using chromium full screen (trying to read my gmail inbox) when
  borders around windows disappeared & I lost the capacity to switch
  between windows; mouse would move, but keyboard appeared mostly dead
  (it wasn't, more I think windows weren't responding, inc. clicks with
  mouse though that's likely inconsistent; I could [not] work out how to
  describe it yesterday, but todays is almost identical).

  I switched to text terminal (ctrl+alt+f4) & explored; returned to GUI and used
  - ctrl+alt+t to open new terminal
  - openbox &

  session returned to what I expect...

  ** expected outcome

  Openbox doesn't crash

  ** actual outcome

  all windows lost borders, and i lost ability to switch between windows
  I appeared to have minimal control (not true, more a fraction of what I 
expect)

  ** How to get crash

  For me,

  - I used chromium (browser)
  - make chromium full screen (ie. F11)
  - click on link/something & right-click to open in new window
  OPENBOX CRASH.

  ProblemType: Crash
  DistroRelease: Ubuntu 23.04
  Package: openbox 3.6.1-10
  ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6
  Uname: Linux 6.1.0-16-generic x86_64
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashCounter: 1
  CurrentDesktop: LXQt
  Date: Thu Mar 16 09:46:22 2023
  ExecutablePath: /usr/bin/openbox
  ExecutableTimestamp: 1643543619
  InstallationDate: Installed on 2023-01-25 (49 days ago)
  InstallationMedia: Lubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230124)
  JournalErrors: -- No entries --
  ProcCmdline: /usr/bin/openbox
  ProcCwd: /home/guiverc
  RebootRequiredPkgs: Error: path contained symlinks.
  Signal: 6
  SourcePackage: openbox
  StacktraceTop:
   () at /lib/x86_64-linux-gnu/libobt.so.2
    () at /lib/x86_64-linux-gnu/libc.so.6
   client_calc_layer ()
   ()
   () at /lib/x86_64-linux-gnu/libobt.so.2
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2011751/+subscriptions


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

[Desktop-packages] [Bug 2012745] [NEW] IPA modules are not resigned after dh_strip

2023-03-24 Thread Dylan Aïssi

Public bug reported:

[ Reason ]
Open source IPA (Image Processing Algorithms) modules are signed at build time 
allowing them to be trusted. However, IPA binaries are modified by dh_strip 
invalidating the signatures. Thus IPA modules provided in the package are not 
trusted anymore and need to be re-signed after the dh_strip step. This fix is 
applied in 0.0.4-3.

[ Impact ]
Not resigning IPA modules will make them untrusted, they will be isolated 
inside a Sandbox environment with restricted access to the system (like any 
closed-source module). Provided IPA modules won't work as expected.

[ Risks ]
The risk is low since we only regenerate signatures after dh_strip, i.e. 
/usr/lib/*/libcamera/ipa_.so.sign files.

** Affects: libcamera (Ubuntu)
 Importance: Undecided
 Status: Confirmed

** Affects: libcamera (Debian)
 Importance: Unknown
 Status: Unknown

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

** Also affects: libcamera (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033118
   Importance: Unknown
   Status: Unknown

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

** Changed in: libcamera (Ubuntu)
Milestone: None => ubuntu-23.04

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

Title:
  IPA modules are not resigned after dh_strip

Status in libcamera package in Ubuntu:
  Confirmed
Status in libcamera package in Debian:
  Unknown

Bug description:
  [ Reason ]
  Open source IPA (Image Processing Algorithms) modules are signed at build 
time allowing them to be trusted. However, IPA binaries are modified by 
dh_strip invalidating the signatures. Thus IPA modules provided in the package 
are not trusted anymore and need to be re-signed after the dh_strip step. This 
fix is applied in 0.0.4-3.

  [ Impact ]
  Not resigning IPA modules will make them untrusted, they will be isolated 
inside a Sandbox environment with restricted access to the system (like any 
closed-source module). Provided IPA modules won't work as expected.

  [ Risks ]
  The risk is low since we only regenerate signatures after dh_strip, i.e. 
/usr/lib/*/libcamera/ipa_.so.sign files.

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


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

[Desktop-packages] [Bug 2003259] Re: [MIR] libcupsfilters libppd cups-browsed

2023-03-24 Thread Till Kamppeter

** Changed in: libppd (Ubuntu)
   Status: Invalid => New

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

Title:
  [MIR] libcupsfilters libppd cups-browsed

Status in cups-browsed package in Ubuntu:
  Fix Released
Status in libcupsfilters package in Ubuntu:
  Fix Released
Status in libppd package in Ubuntu:
  New

Bug description:
  == Summary =

  Source packages to be promoted to Main:
  - libcupsfilters
  - libppd
  - cups-browsed

  Binary packages to be promoted to Main:
  - libcupsfilters2
  - libcupsfilters2-common
  - libppd-dev
  - libppd2
  - libppd2-common
  - ppdc

  No source packages and no binary packages which are in Main should get
  demoted to Universe.

  == Overview 

  Due to a major change in the printing architecture [1] the
  cups-filters upstream project at OpenPrinting got split into 5
  components [2]:

  - libcupsfilters
  - libppd
  - cups-filters
  - braille-printer-app
  - cups-browsed

  [1] 
https://openprinting.github.io/current/#the-new-architecture-for-printing-and-scanning
  [2] 
https://openprinting.github.io/cups-filters-Second-Generation-First-Beta-Release/

  To reflect this in the Debian/Ubuntu packaging also the cups-filters
  source package there is getting split, rendering 3 new source
  packages (+) and therefore we need this MIR:

  Binaries:  Source BEFORE (1.x)  Source AFTER (2.x)
  -
  cups-browsed   cups-filters cups-browsed +
  cups-filters   cups-filters cups-filters
  cups-filters-core-drivers  cups-filters cups-filters
  libcupsfilters-dev cups-filters libcupsfilters +
  libcupsfilters1 X  cups-filters Replaced by
    libcupsfilters2 *
  libcupsfilters2 +   libcupsfilters + (NEW)
  libcupsfilters2-common +libcupsfilters + (NEW)
  libfontembed-dev X cups-filters REMOVED **
  libfontembed X cups-filters REMOVED **
  libppd-dev +libppd + (NEW) ***
  libppd2 +   libppd + (NEW) ***
  libppd2-common +libppd + (NEW) ***
  ppdc +  libppd + (NEW) ***

  *  : libcupsfilters has new API generation/SONAME 1 -> 2
  ** : libfontembed code folded into libcupsfilters, API removed, no other
   package is using it.
  ***: libppd contains all PPD-supporting code of CUPS, as in CUPS 3.x
   this code will get removed. libppd is for legacy-retro-fitting of
   classic CUPS drivers with PPD files. Code comes from CUPS source:
   cups/ppd*.[ch], scheduler/cups-driverd.cxx, ppdc/*
  X:   Binary package getting REMOVED from Lunar
  +:   Source or binary package to be promoted to Main via this MIR

  The purposes of the new generation's binary packages are principally
  the same as before:

  - cups-browsed: Daemon to auto-create queues for network printers and to
  form printer clusters
  - cups-filters: Print data format conversion filters and printer
  communication backends for CUPS 2.x - Complete set
  - cups-filters-core-drivers: Print data format conversion filters and
  printer communication backends for CUPS 2.x - Essential
  ones for minimum configurations, like mobile or IoT
  - libcupsfilters-dev: C Header files for libcupsfilters2
  - libcupsfilters2: Shared library containing common code for print data
  conversion filters, printer drivers, printer model
  identification and distinction, PDF file manipulation,
  PDF font embedding, color space conversion, ...
  - libcupsfilters2-common: Architecture-indpendent auxiliary files
  - libppd2-dev:  C Header files for libppd2
  - libppd2:  Shared library for support of PPD files, parsing the
  files, converting PPD options into IPP attributes,
  managing collections of PPDs, finding PPD for given
  printer, generating PPDs from CUPS' *.drv files
  - libppd2-common: Architecture-indpendent auxiliary files
  - ppdc: Command line tools to generate PPD files from *.drv
  files (only for development and debugging, or to
  keep scripts using them working, not end-user-facing)

  --> ALL THESE BINARY PACKAGES MUST BE IN MAIM, SO THE FOLLOWING BINARY
  PACKAGES NEED TO GET PROMOTED:

    - libcupsfilters2
    - libcupsfilters2-common
    - libppd-dev
    - libppd2
    - libppd2-common
    - ppdc

  For current CUPS (2.x, provided by Debian packages) there is

[Desktop-packages] [Bug 2012738] Re: language support crashes on install missing translations or writing aids

The issue is in fact due to bug #1991606  and fixed with the lunar-
proposed version of devscripts

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

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

** Package changed: aptdaemon (Ubuntu) => devscripts (Ubuntu)

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

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

Title:
  language support crashes on install missing translations or writing
  aids

Status in devscripts package in Ubuntu:
  Fix Committed
Status in gnome-control-center package in Ubuntu:
  Invalid

Bug description:
  Installing missing "translations or writing aids" crashes the gnome-
  language-selector app.

  I have attached a recording (sorry should have had capture cursor on)
  and relevant stack trace from journalctl.

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


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

[Desktop-packages] [Bug 2003259] Re: [MIR] libcupsfilters libppd cups-browsed

2023-03-24 Thread Mark Esler

Since libppd MIR is no longer required per comment 37 and MM discussion,
setting status to invalid and removing Security Team.

** Changed in: libppd (Ubuntu)
   Status: New => Invalid

** Changed in: libppd (Ubuntu)
 Assignee: Ubuntu Security Team (ubuntu-security) => (unassigned)

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

Title:
  [MIR] libcupsfilters libppd cups-browsed

Status in cups-browsed package in Ubuntu:
  Fix Released
Status in libcupsfilters package in Ubuntu:
  Fix Released
Status in libppd package in Ubuntu:
  Invalid

Bug description:
  == Summary =

  Source packages to be promoted to Main:
  - libcupsfilters
  - libppd
  - cups-browsed

  Binary packages to be promoted to Main:
  - libcupsfilters2
  - libcupsfilters2-common
  - libppd-dev
  - libppd2
  - libppd2-common
  - ppdc

  No source packages and no binary packages which are in Main should get
  demoted to Universe.

  == Overview 

  Due to a major change in the printing architecture [1] the
  cups-filters upstream project at OpenPrinting got split into 5
  components [2]:

  - libcupsfilters
  - libppd
  - cups-filters
  - braille-printer-app
  - cups-browsed

  [1] 
https://openprinting.github.io/current/#the-new-architecture-for-printing-and-scanning
  [2] 
https://openprinting.github.io/cups-filters-Second-Generation-First-Beta-Release/

  To reflect this in the Debian/Ubuntu packaging also the cups-filters
  source package there is getting split, rendering 3 new source
  packages (+) and therefore we need this MIR:

  Binaries:  Source BEFORE (1.x)  Source AFTER (2.x)
  -
  cups-browsed   cups-filters cups-browsed +
  cups-filters   cups-filters cups-filters
  cups-filters-core-drivers  cups-filters cups-filters
  libcupsfilters-dev cups-filters libcupsfilters +
  libcupsfilters1 X  cups-filters Replaced by
    libcupsfilters2 *
  libcupsfilters2 +   libcupsfilters + (NEW)
  libcupsfilters2-common +libcupsfilters + (NEW)
  libfontembed-dev X cups-filters REMOVED **
  libfontembed X cups-filters REMOVED **
  libppd-dev +libppd + (NEW) ***
  libppd2 +   libppd + (NEW) ***
  libppd2-common +libppd + (NEW) ***
  ppdc +  libppd + (NEW) ***

  *  : libcupsfilters has new API generation/SONAME 1 -> 2
  ** : libfontembed code folded into libcupsfilters, API removed, no other
   package is using it.
  ***: libppd contains all PPD-supporting code of CUPS, as in CUPS 3.x
   this code will get removed. libppd is for legacy-retro-fitting of
   classic CUPS drivers with PPD files. Code comes from CUPS source:
   cups/ppd*.[ch], scheduler/cups-driverd.cxx, ppdc/*
  X:   Binary package getting REMOVED from Lunar
  +:   Source or binary package to be promoted to Main via this MIR

  The purposes of the new generation's binary packages are principally
  the same as before:

  - cups-browsed: Daemon to auto-create queues for network printers and to
  form printer clusters
  - cups-filters: Print data format conversion filters and printer
  communication backends for CUPS 2.x - Complete set
  - cups-filters-core-drivers: Print data format conversion filters and
  printer communication backends for CUPS 2.x - Essential
  ones for minimum configurations, like mobile or IoT
  - libcupsfilters-dev: C Header files for libcupsfilters2
  - libcupsfilters2: Shared library containing common code for print data
  conversion filters, printer drivers, printer model
  identification and distinction, PDF file manipulation,
  PDF font embedding, color space conversion, ...
  - libcupsfilters2-common: Architecture-indpendent auxiliary files
  - libppd2-dev:  C Header files for libppd2
  - libppd2:  Shared library for support of PPD files, parsing the
  files, converting PPD options into IPP attributes,
  managing collections of PPDs, finding PPD for given
  printer, generating PPDs from CUPS' *.drv files
  - libppd2-common: Architecture-indpendent auxiliary files
  - ppdc: Command line tools to generate PPD files from *.drv
  files (only for development and debugging, or to
  keep scripts using them working, not end-user-facing)

  --> ALL THESE BINARY PACKAGES MUST BE IN MAIM, SO THE FOLLOWING BINARY

[Desktop-packages] [Bug 2012738] Re: language support crashes on install missing translations or writing aids

Confirmed, the log points to an aptdaemon issue

> Mar 24 13:40:37 earth org.debian.apt[88811]: ModuleNotFoundError: No
module named 'aptdaemon.pkutils'

or devscripts

> pkg_resources.extern.packaging.version.InvalidVersion: Invalid version: 
> '2.22.2ubuntu5'
(similar to https://launchpad.net/bugs/1991606)

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

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

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

Title:
  language support crashes on install missing translations or writing
  aids

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

Bug description:
  Installing missing "translations or writing aids" crashes the gnome-
  language-selector app.

  I have attached a recording (sorry should have had capture cursor on)
  and relevant stack trace from journalctl.

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


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

[Desktop-packages] [Bug 2012736] Re: language and region > login screen > formats does not display United Kingdom

** Description changed:

  When there are multiple accounts on a machine the "Language and Region"
- settings screen shows a "Login Screen" section. Under the "Formats"
- heading, if "Canada" is selected then the UI shows "Canada", however, if
- "United Kingdom" is selected then the Formats section displays "United
- States".
+ settings screen shows a "Login Screen" section. Under the "Formats", if
+ "Canada" is selected then the UI shows "Canada", however, if "United
+ Kingdom" is selected then the Formats section displays "United States".
+ 
+ It displays correctly under the "Your Account" section.
  
  I have attached a screen recording to demonstrate.
  
  This is on Lunar.

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

Title:
  language and region > login screen > formats does not display United
  Kingdom

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

Bug description:
  When there are multiple accounts on a machine the "Language and
  Region" settings screen shows a "Login Screen" section. Under the
  "Formats", if "Canada" is selected then the UI shows "Canada",
  however, if "United Kingdom" is selected then the Formats section
  displays "United States".

  It displays correctly under the "Your Account" section.

  I have attached a screen recording to demonstrate.

  This is on Lunar.

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


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

[Desktop-packages] [Bug 2012738] Re: language support crashes on install missing translations or writing aids

Stack trace from journalctl

** Attachment added: "logging.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2012738/+attachment/5657278/+files/logging.txt

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

Title:
  language support crashes on install missing translations or writing
  aids

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

Bug description:
  Installing missing "translations or writing aids" crashes the gnome-
  language-selector app.

  I have attached a recording (sorry should have had capture cursor on)
  and relevant stack trace from journalctl.

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


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

[Desktop-packages] [Bug 2012738] [NEW] language support crashes on install missing translations or writing aids

Public bug reported:

Installing missing "translations or writing aids" crashes the gnome-
language-selector app.

I have attached a recording (sorry should have had capture cursor on)
and relevant stack trace from journalctl.

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


** Tags: bug lunar rls-ll-incoming

** Attachment added: "Screencast from 2023-03-24 13-56-47.webm"
   
https://bugs.launchpad.net/bugs/2012738/+attachment/5657277/+files/Screencast%20from%202023-03-24%2013-56-47.webm

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

Title:
  language support crashes on install missing translations or writing
  aids

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

Bug description:
  Installing missing "translations or writing aids" crashes the gnome-
  language-selector app.

  I have attached a recording (sorry should have had capture cursor on)
  and relevant stack trace from journalctl.

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


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

[Desktop-packages] [Bug 2012736] [NEW] language and region > login screen > formats does not display United Kingdom

Public bug reported:

When there are multiple accounts on a machine the "Language and Region"
settings screen shows a "Login Screen" section. Under the "Formats"
heading, if "Canada" is selected then the UI shows "Canada", however, if
"United Kingdom" is selected then the Formats section displays "United
States".

I have attached a screen recording to demonstrate.

This is on Lunar.

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


** Tags: bug lunar rls-ll-incoming

** Attachment added: "Screencast from 2023-03-24 12-24-46.webm"
   
https://bugs.launchpad.net/bugs/2012736/+attachment/5657275/+files/Screencast%20from%202023-03-24%2012-24-46.webm

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

Title:
  language and region > login screen > formats does not display United
  Kingdom

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

Bug description:
  When there are multiple accounts on a machine the "Language and
  Region" settings screen shows a "Login Screen" section. Under the
  "Formats" heading, if "Canada" is selected then the UI shows "Canada",
  however, if "United Kingdom" is selected then the Formats section
  displays "United States".

  I have attached a screen recording to demonstrate.

  This is on Lunar.

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


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

[Desktop-packages] [Bug 2011770] Please test proposed package

2023-03-24 Thread Timo Aaltonen

Hello Atlas, or anyone else affected,

Accepted gnome-settings-daemon into jammy-proposed. The package will
build now and be available at
https://launchpad.net/ubuntu/+source/gnome-settings-
daemon/42.1-1ubuntu2.2 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.

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

Title:
  [gsd-rfkill] WwanEnabled never get synced

Status in OEM Priority Project:
  Triaged
Status in gnome-settings-daemon package in Ubuntu:
  Fix Released
Status in gnome-settings-daemon source package in Jammy:
  Fix Committed
Status in gnome-settings-daemon source package in Kinetic:
  Fix Committed

Bug description:
  [ Impact ]

   * Sometimes on devices with WWAN card, whenever user presses the
  wireless function key (Fn+F8) or turn on the airplane mode radio
  button in Settings, the airplane mode will not be enabled, and the
  airplane mode icon is not shown in the status bar.

   * There is a unmerged upstream merge request that delivers the fix:
  https://gitlab.gnome.org/GNOME/gnome-settings-
  daemon/-/merge_requests/310

  It works perfectly well on several Lenovo laptops with WWAN cards.
  The root causes is that the value of "WwanEnabled" under 
"org.freedesktop.NetworkManager" is not synced correctly, gsd-rfkill should 
listen to "g-properties-changed" instead of "g-signal" now.

  [ Test Plan ]

   1. Find a machine which has WWAN card.
   2. Boot the machine, and run rfkill list to see if WWAN is unblocked. if not 
use rfkill to unblock the WWAN, and reboot.
   3. Press the wireless media key (Fn+F8) or turn on the airplane mode radio 
button in Settings.
   4. The airplane mode should be enabled, but actually not.

  [ Where problems could occur ]

   * When user is using a very low version network-manager (< 1.20) that
  still broadcasting DBUS "PropertiesChanged" events on "g-signal"
  instead of the concurrent "g-properties-changed", the airplane mode
  will sometimes not be able to enable.

  [1]: 
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/853
  [2]: 
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/6fb917178aa19c61e909957f5146aa4565e0cb2f

  [ Other Info ]

  1. About Ubuntu
  Description:Ubuntu 22.04.2 LTS
  Release:22.04
  Kernel: 6.1.0-1007-oem

  2. The version of packages:
  gnome-settings-daemon:
    Installed: 42.1-1ubuntu2.1

  network-manager:
    Installed: 1.36.6-0ubuntu2

  3. Expect:
  The function nm_signal(plugins/rfkill/gsd-rfkill-manager.c) is called, and 
manager->wwan_enabled is set to the correct value.

  4. Actual:
  The function nm_signal(plugins/rfkill/gsd-rfkill-manager.c) is never called, 
so manager->wwan_enabled is not synced, If machine has WWAN device(s), and the 
initial value of manager->wwan_enabled is true, it will never be able to switch 
to airplane mode.

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


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

[Desktop-packages] [Bug 2011770] Re: [gsd-rfkill] WwanEnabled never get synced

2023-03-24 Thread Timo Aaltonen

Hello Atlas, or anyone else affected,

Accepted gnome-settings-daemon into kinetic-proposed. The package will
build now and be available at
https://launchpad.net/ubuntu/+source/gnome-settings-
daemon/43.0-1ubuntu1.1 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-
kinetic to verification-done-kinetic. If it does not fix the bug for
you, please add a comment stating that, and change the tag to
verification-failed-kinetic. 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: gnome-settings-daemon (Ubuntu Kinetic)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-kinetic

** Changed in: gnome-settings-daemon (Ubuntu Jammy)
   Status: New => Fix Committed

** Tags added: verification-needed-jammy

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

Title:
  [gsd-rfkill] WwanEnabled never get synced

Status in OEM Priority Project:
  Triaged
Status in gnome-settings-daemon package in Ubuntu:
  Fix Released
Status in gnome-settings-daemon source package in Jammy:
  Fix Committed
Status in gnome-settings-daemon source package in Kinetic:
  Fix Committed

Bug description:
  [ Impact ]

   * Sometimes on devices with WWAN card, whenever user presses the
  wireless function key (Fn+F8) or turn on the airplane mode radio
  button in Settings, the airplane mode will not be enabled, and the
  airplane mode icon is not shown in the status bar.

   * There is a unmerged upstream merge request that delivers the fix:
  https://gitlab.gnome.org/GNOME/gnome-settings-
  daemon/-/merge_requests/310

  It works perfectly well on several Lenovo laptops with WWAN cards.
  The root causes is that the value of "WwanEnabled" under 
"org.freedesktop.NetworkManager" is not synced correctly, gsd-rfkill should 
listen to "g-properties-changed" instead of "g-signal" now.

  [ Test Plan ]

   1. Find a machine which has WWAN card.
   2. Boot the machine, and run rfkill list to see if WWAN is unblocked. if not 
use rfkill to unblock the WWAN, and reboot.
   3. Press the wireless media key (Fn+F8) or turn on the airplane mode radio 
button in Settings.
   4. The airplane mode should be enabled, but actually not.

  [ Where problems could occur ]

   * When user is using a very low version network-manager (< 1.20) that
  still broadcasting DBUS "PropertiesChanged" events on "g-signal"
  instead of the concurrent "g-properties-changed", the airplane mode
  will sometimes not be able to enable.

  [1]: 
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/853
  [2]: 
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/6fb917178aa19c61e909957f5146aa4565e0cb2f

  [ Other Info ]

  1. About Ubuntu
  Description:Ubuntu 22.04.2 LTS
  Release:22.04
  Kernel: 6.1.0-1007-oem

  2. The version of packages:
  gnome-settings-daemon:
    Installed: 42.1-1ubuntu2.1

  network-manager:
    Installed: 1.36.6-0ubuntu2

  3. Expect:
  The function nm_signal(plugins/rfkill/gsd-rfkill-manager.c) is called, and 
manager->wwan_enabled is set to the correct value.

  4. Actual:
  The function nm_signal(plugins/rfkill/gsd-rfkill-manager.c) is never called, 
so manager->wwan_enabled is not synced, If machine has WWAN device(s), and the 
initial value of manager->wwan_enabled is true, it will never be able to switch 
to airplane mode.

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


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

[Desktop-packages] [Bug 2003259] Re: [MIR] libcupsfilters libppd cups-browsed

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

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

Title:
  [MIR] libcupsfilters libppd cups-browsed

Status in cups-browsed package in Ubuntu:
  Fix Released
Status in libcupsfilters package in Ubuntu:
  Fix Released
Status in libppd package in Ubuntu:
  New

Bug description:
  == Summary =

  Source packages to be promoted to Main:
  - libcupsfilters
  - libppd
  - cups-browsed

  Binary packages to be promoted to Main:
  - libcupsfilters2
  - libcupsfilters2-common
  - libppd-dev
  - libppd2
  - libppd2-common
  - ppdc

  No source packages and no binary packages which are in Main should get
  demoted to Universe.

  == Overview 

  Due to a major change in the printing architecture [1] the
  cups-filters upstream project at OpenPrinting got split into 5
  components [2]:

  - libcupsfilters
  - libppd
  - cups-filters
  - braille-printer-app
  - cups-browsed

  [1] 
https://openprinting.github.io/current/#the-new-architecture-for-printing-and-scanning
  [2] 
https://openprinting.github.io/cups-filters-Second-Generation-First-Beta-Release/

  To reflect this in the Debian/Ubuntu packaging also the cups-filters
  source package there is getting split, rendering 3 new source
  packages (+) and therefore we need this MIR:

  Binaries:  Source BEFORE (1.x)  Source AFTER (2.x)
  -
  cups-browsed   cups-filters cups-browsed +
  cups-filters   cups-filters cups-filters
  cups-filters-core-drivers  cups-filters cups-filters
  libcupsfilters-dev cups-filters libcupsfilters +
  libcupsfilters1 X  cups-filters Replaced by
    libcupsfilters2 *
  libcupsfilters2 +   libcupsfilters + (NEW)
  libcupsfilters2-common +libcupsfilters + (NEW)
  libfontembed-dev X cups-filters REMOVED **
  libfontembed X cups-filters REMOVED **
  libppd-dev +libppd + (NEW) ***
  libppd2 +   libppd + (NEW) ***
  libppd2-common +libppd + (NEW) ***
  ppdc +  libppd + (NEW) ***

  *  : libcupsfilters has new API generation/SONAME 1 -> 2
  ** : libfontembed code folded into libcupsfilters, API removed, no other
   package is using it.
  ***: libppd contains all PPD-supporting code of CUPS, as in CUPS 3.x
   this code will get removed. libppd is for legacy-retro-fitting of
   classic CUPS drivers with PPD files. Code comes from CUPS source:
   cups/ppd*.[ch], scheduler/cups-driverd.cxx, ppdc/*
  X:   Binary package getting REMOVED from Lunar
  +:   Source or binary package to be promoted to Main via this MIR

  The purposes of the new generation's binary packages are principally
  the same as before:

  - cups-browsed: Daemon to auto-create queues for network printers and to
  form printer clusters
  - cups-filters: Print data format conversion filters and printer
  communication backends for CUPS 2.x - Complete set
  - cups-filters-core-drivers: Print data format conversion filters and
  printer communication backends for CUPS 2.x - Essential
  ones for minimum configurations, like mobile or IoT
  - libcupsfilters-dev: C Header files for libcupsfilters2
  - libcupsfilters2: Shared library containing common code for print data
  conversion filters, printer drivers, printer model
  identification and distinction, PDF file manipulation,
  PDF font embedding, color space conversion, ...
  - libcupsfilters2-common: Architecture-indpendent auxiliary files
  - libppd2-dev:  C Header files for libppd2
  - libppd2:  Shared library for support of PPD files, parsing the
  files, converting PPD options into IPP attributes,
  managing collections of PPDs, finding PPD for given
  printer, generating PPDs from CUPS' *.drv files
  - libppd2-common: Architecture-indpendent auxiliary files
  - ppdc: Command line tools to generate PPD files from *.drv
  files (only for development and debugging, or to
  keep scripts using them working, not end-user-facing)

  --> ALL THESE BINARY PACKAGES MUST BE IN MAIM, SO THE FOLLOWING BINARY
  PACKAGES NEED TO GET PROMOTED:

    - libcupsfilters2
    - libcupsfilters2-common
    - libppd-dev
    - libppd2
    - libppd2-common
    - ppdc

  For current CUPS (2.x, provided by Debian

[Desktop-packages] [Bug 2012733] [NEW] [lunar] [X11] Adwaita instead of Yaru in non GNOME apps

2023-03-24 Thread Francois Thirioux

Public bug reported:

Hi,

Nvidia 530 (graphics ppa), dGPU mode, GS 44, Lunar

X1 session:
If I launch Synaptic or ChessX, eg., the title bar is Adwaita-styled (greyish + 
icons).
No issue with GNOME apps (and some other like FF or TB snaps, etc.).

Wayland session:
all is ok (except many other bugs!)

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


** Tags: lunar

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

Title:
  [lunar] [X11] Adwaita instead of Yaru in non GNOME apps

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Hi,

  Nvidia 530 (graphics ppa), dGPU mode, GS 44, Lunar

  X1 session:
  If I launch Synaptic or ChessX, eg., the title bar is Adwaita-styled (greyish 
+ icons).
  No issue with GNOME apps (and some other like FF or TB snaps, etc.).

  Wayland session:
  all is ok (except many other bugs!)

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


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

[Desktop-packages] [Bug 951585] Re: gvfsd-afp consumes 100% of processor cycles

2023-03-24 Thread linuxgeoff

ubuntu 22.10.  Network has no macs, but two samba NASs, one mounted with
GVFS and the other as CIFS in fstab.  Had to kill the process to get my
machine back.

Have been running this network and ubuntu since 07, and never noticed
this bug till now.

After killing the process, I tried to recreate the bug by browsing,
copying to and deleting files on both NASs using both Gnome Files and
Thunar - all worked as it should and no CPU-hog processes show up

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

Title:
  gvfsd-afp consumes 100% of processor cycles

Status in gvfs package in Ubuntu:
  Confirmed

Bug description:
  Happens on an irregular basis on 12.04 and I think I've experienced it
  on 11.10.

  For no reason gvfsd-afp starts up. Cooling fan kicks in, system
  becomes laggy. Easily cured using system monitor and killing the
  process. Someone on the Ubuntu Forum asked if I have a Mac on the
  network and the answer is yes, an iMac and there are shares on that
  machine I can access.

  Have experienced this issue on my Acer Aspire 5742 and Compaq Mini 110

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


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

[Desktop-packages] [Bug 2012726] [NEW] System freezes with "can't update stage views actor" for MetaWindowGroup and MetaWindowActorX11

2023-03-24 Thread Laurence

Public bug reported:

Syslog spam...

Mar 24 11:09:07 myhostname gnome-shell[2307]: Can't update stage views actor 
[:0x555ca1fa0350] is on because it needs an 
allocation.
Mar 24 11:09:07 myhostname gnome-shell[2307]: Can't update stage views actor 
[:0x555ca3c79b10] is on because it needs an 
allocation.
Mar 24 11:09:07 myhostname gnome-shell[2307]: Can't update stage views actor 
[:0x555ca3c7cdc0] is on because it needs an 
allocation.
Mar 24 11:09:07 myhostname gnome-shell[2307]: Can't update stage views actor 
[:0x555ca1fa0350] is on because it needs an 
allocation.
Mar 24 11:09:07 myhostname gnome-shell[2307]: Can't update stage views actor 
[:0x555ca3c79b10] is on because it needs an 
allocation.
Mar 24 11:09:07 myhostname gnome-shell[2307]: Can't update stage views actor 
[:0x555ca3c7cdc0] is on because it needs an 
allocation.
Mar 24 11:09:07 myhostname gnome-shell[2307]: Can't update stage views actor 
[:0x555ca1fa0350] is on because it needs an 
allocation.
Mar 24 11:09:07 myhostname gnome-shell[2307]: Can't update stage views actor 
[:0x555ca3c79b10] is on because it needs an 
allocation.
Mar 24 11:09:07 myhostname gnome-shell[2307]: Can't update stage views actor 
[:0x555ca3c7cdc0] is on because it needs an 
allocation.
Mar 24 11:09:07 myhostname gnome-shell[2307]: Can't update stage views actor 
[:0x555ca1fa0350] is on because it needs an 
allocation.
Mar 24 11:09:07 myhostname gnome-shell[2307]: Can't update stage views actor 
[:0x555ca3c79b10] is on because it needs an 
allocation.
Mar 24 11:09:07 myhostname gnome-shell[2307]: Can't update stage views actor 
[:0x555ca3c7cdc0] is on because it needs an 
allocation.
Mar 24 11:09:07 myhostname gnome-shell[2307]: Can't update stage views actor 
[:0x555ca1fa0350] is on because it needs an 
allocation.
Mar 24 11:09:07 myhostname gnome-shell[2307]: Can't update stage views actor 
[:0x555ca3c79b10] is on because it needs an 
allocation.
Mar 24 11:09:07 myhostname gnome-shell[2307]: Can't update stage views actor 
[:0x555ca3c7cdc0] is on because it needs an 
allocation.
Mar 24 11:09:07 myhostname gnome-shell[2307]: Can't update stage views actor 
[:0x555ca1fa0350] is on because it needs an 
allocation.
Mar 24 11:09:07 myhostname gnome-shell[2307]: Can't update stage views actor 
[:0x555ca3c79b10] is on because it needs an 
allocation.
Mar 24 11:09:07 myhostname gnome-shell[2307]: Can't update stage views actor 
[:0x555ca3c7cdc0] is on because it needs an 
allocation.
Mar 24 11:09:13 myhostname gnome-shell[2307]: Can't update stage views actor 
[:0x555ca1fa0350] is on because it needs an 
allocation.
Mar 24 11:09:13 myhostname gnome-shell[2307]: Can't update stage views actor 
[:0x555ca3c79b10] is on because it needs an 
allocation.
Mar 24 11:09:13 myhostname gnome-shell[2307]: Can't update stage views actor 
[:0x555ca3c7cdc0] is on because it needs an 
allocation.
Mar 24 11:09:13 myhostname gnome-shell[2307]: Can't update stage views actor 
[:0x555ca1fa0350] is on because it needs an 
allocation.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42.5-0ubuntu1
ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17
Uname: Linux 5.19.0-35-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar 24 11:17:07 2023
DisplayManager: gdm3
InstallationDate: Installed on 2022-06-17 (280 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
RelatedPackageVersions: mutter-common 42.5-0ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug jammy

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

Title:
  System freezes with "can't update stage views actor" for
  MetaWindowGroup and MetaWindowActorX11

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Syslog spam...

  Mar 24 11:09:07 myhostname gnome-shell[2307]: Can't update stage views actor 
[:0x555ca1fa0350] is on because it needs an 
allocation.
  Mar 24 11:09:07 myhostname gnome-shell[2307]: Can't update stage views actor 
[:0x555ca3c79b10] is on because it needs an 
allocation.
  Mar 24 11:09:07 myhostname gnome-shell[2307]: Can't update stage views actor 
[:0x555ca3c7cdc0] is on because it needs an 
allocation.
  Mar 24 11:09:07 myhostname gnome-shell[2307]: Can't update stage views actor 
[:0x555ca1fa0350] is on because it needs an 
allocation.
  Mar 24 11:09:07 myhostname gnome-shell[2307]: Can't update stage views actor 
[:0x555ca3c79b10] is on because it needs an 
allocation.
  Mar 24 11:09:07 myhostname gnome-shell[2307]: Can't update stage views actor 
[:0x555ca3c7cdc0] is on because it needs an 
allocation.
  Mar 24

[Desktop-packages] [Bug 2003259] Re: [MIR] libcupsfilters libppd cups-browsed

$ ./change-override -c main -t libcupsfilters
Override component to main
libcupsfilters 2.0~b4-0ubuntu5 in lunar: universe/net -> main
Override [y|N]? y
1 publication overridden.

$ ./change-override -c main libcupsfilters2 libcupsfilters2-common
Override component to main
libcupsfilters2 2.0~b4-0ubuntu5 in lunar amd64: universe/libs/optional/100% -> 
main
libcupsfilters2 2.0~b4-0ubuntu5 in lunar arm64: universe/libs/optional/100% -> 
main
libcupsfilters2 2.0~b4-0ubuntu5 in lunar armhf: universe/libs/optional/100% -> 
main
libcupsfilters2 2.0~b4-0ubuntu5 in lunar ppc64el: universe/libs/optional/100% 
-> main
libcupsfilters2 2.0~b4-0ubuntu5 in lunar riscv64: universe/libs/optional/100% 
-> main
libcupsfilters2 2.0~b4-0ubuntu5 in lunar s390x: universe/libs/optional/100% -> 
main
libcupsfilters2-common 2.0~b4-0ubuntu5 in lunar amd64: 
universe/libs/optional/100% -> main
libcupsfilters2-common 2.0~b4-0ubuntu5 in lunar arm64: 
universe/libs/optional/100% -> main
libcupsfilters2-common 2.0~b4-0ubuntu5 in lunar armhf: 
universe/libs/optional/100% -> main
libcupsfilters2-common 2.0~b4-0ubuntu5 in lunar i386: 
universe/libs/optional/100% -> main
libcupsfilters2-common 2.0~b4-0ubuntu5 in lunar ppc64el: 
universe/libs/optional/100% -> main
libcupsfilters2-common 2.0~b4-0ubuntu5 in lunar riscv64: 
universe/libs/optional/100% -> main
libcupsfilters2-common 2.0~b4-0ubuntu5 in lunar s390x: 
universe/libs/optional/100% -> main
Override [y|N]? y
13 publications overridden.


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

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

Title:
  [MIR] libcupsfilters libppd cups-browsed

Status in cups-browsed package in Ubuntu:
  In Progress
Status in libcupsfilters package in Ubuntu:
  Fix Released
Status in libppd package in Ubuntu:
  New

Bug description:
  == Summary =

  Source packages to be promoted to Main:
  - libcupsfilters
  - libppd
  - cups-browsed

  Binary packages to be promoted to Main:
  - libcupsfilters2
  - libcupsfilters2-common
  - libppd-dev
  - libppd2
  - libppd2-common
  - ppdc

  No source packages and no binary packages which are in Main should get
  demoted to Universe.

  == Overview 

  Due to a major change in the printing architecture [1] the
  cups-filters upstream project at OpenPrinting got split into 5
  components [2]:

  - libcupsfilters
  - libppd
  - cups-filters
  - braille-printer-app
  - cups-browsed

  [1] 
https://openprinting.github.io/current/#the-new-architecture-for-printing-and-scanning
  [2] 
https://openprinting.github.io/cups-filters-Second-Generation-First-Beta-Release/

  To reflect this in the Debian/Ubuntu packaging also the cups-filters
  source package there is getting split, rendering 3 new source
  packages (+) and therefore we need this MIR:

  Binaries:  Source BEFORE (1.x)  Source AFTER (2.x)
  -
  cups-browsed   cups-filters cups-browsed +
  cups-filters   cups-filters cups-filters
  cups-filters-core-drivers  cups-filters cups-filters
  libcupsfilters-dev cups-filters libcupsfilters +
  libcupsfilters1 X  cups-filters Replaced by
    libcupsfilters2 *
  libcupsfilters2 +   libcupsfilters + (NEW)
  libcupsfilters2-common +libcupsfilters + (NEW)
  libfontembed-dev X cups-filters REMOVED **
  libfontembed X cups-filters REMOVED **
  libppd-dev +libppd + (NEW) ***
  libppd2 +   libppd + (NEW) ***
  libppd2-common +libppd + (NEW) ***
  ppdc +  libppd + (NEW) ***

  *  : libcupsfilters has new API generation/SONAME 1 -> 2
  ** : libfontembed code folded into libcupsfilters, API removed, no other
   package is using it.
  ***: libppd contains all PPD-supporting code of CUPS, as in CUPS 3.x
   this code will get removed. libppd is for legacy-retro-fitting of
   classic CUPS drivers with PPD files. Code comes from CUPS source:
   cups/ppd*.[ch], scheduler/cups-driverd.cxx, ppdc/*
  X:   Binary package getting REMOVED from Lunar
  +:   Source or binary package to be promoted to Main via this MIR

  The purposes of the new generation's binary packages are principally
  the same as before:

  - cups-browsed: Daemon to auto-create queues for network printers and to
  form printer clusters
  - cups-filters: Print data format conversion filters and printer
  communication backends for CUPS 2.x - Complete set
  - cups-filters-core-drivers: Print

[Desktop-packages] [Bug 2012720] [NEW] /usr/bin/gnome-software:11:as_utils_fnmatch:as_app_parse_data:gs_plugin_appstream_load_desktop_cb:xb_builder_source_get_istream:xb_builder_compile_source

2023-03-24 Thread errors.ubuntu.com bug bridge

Public bug reported:

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

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


** Tags: focal jammy

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

Title:
  /usr/bin/gnome-
  
software:11:as_utils_fnmatch:as_app_parse_data:gs_plugin_appstream_load_desktop_cb:xb_builder_source_get_istream:xb_builder_compile_source

Status in gnome-software package in Ubuntu:
  New

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

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


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

[Desktop-packages] [Bug 2012540] Re: Please merge tiff 4.5.0-5 from Debian unstable

Thanks Nathan!

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

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

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

Title:
  Please merge tiff 4.5.0-5 from Debian unstable

Status in tiff package in Ubuntu:
  Fix Committed

Bug description:
  Please merge tiff 4.5.0-5 from Debian unstable.

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


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

[Desktop-packages] [Bug 2006633] Re: Merge librsvg 2.54.5+dfsg-1 (main) from Debian unstable (main)

This bug was fixed in the package librsvg - 2.54.5+dfsg-1ubuntu2

---
librsvg (2.54.5+dfsg-1ubuntu2) lunar; urgency=medium

  * Don't fail the build on tests issues on s390x

 -- Sebastien Bacher   Tue, 21 Mar 2023 15:45:43
+0100

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

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

Title:
  Merge librsvg 2.54.5+dfsg-1 (main) from Debian unstable (main)

Status in librsvg package in Ubuntu:
  Fix Released

Bug description:
  Please merge librsvg 2.54.5+dfsg-1 (main) from Debian unstable (main)

  Changelog entries since current lunar version 2.54.4+dfsg-1ubuntu1:

  librsvg (2.54.5+dfsg-1) unstable; urgency=medium

* New upstream release
* debian/librsvg2-2.docs: NEWS.md -> NEWS

   -- Jeremy Bicha   Thu, 22 Sep 2022 17:00:54 -0400

  Remaining differences with librsvg from Debian unstable:

* Don't fail the build on tests error for i386

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


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

[Desktop-packages] [Bug 2012717] Re: GNOME 44 multi-monitor screen freeze when resuming from sleep

** Summary changed:

- Multi-monitor screen freeze when resuming from sleep
+ GNOME 44 multi-monitor screen freeze when resuming from sleep

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

Title:
  GNOME 44 multi-monitor screen freeze when resuming from sleep

Status in Mutter:
  Unknown
Status in mutter package in Ubuntu:
  In Progress

Bug description:
  Testing GNOME 44 I find it can't resume from sleep properly if two
  monitors are plugged in. Both monitors wake up, but one is completely
  frozen and the other is partially frozen (stops responding to anything
  but cursor movement).

  Using Intel graphics with two USB-C monitors.

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


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

[Desktop-packages] [Bug 2004623] Re: [GNOME 44] JS ERROR: TypeError: function Meta.new: At least 2 arguments required, but only 1 passed

** Tags added: rls-ll-incoming

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

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

Title:
  [GNOME 44] JS ERROR: TypeError: function Meta.new: At least 2
  arguments required, but only 1 passed

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

Bug description:
  (gnome-shell:76461): Gjs-CRITICAL **: 14:37:54.077: JS ERROR: TypeError: 
function Meta.new: At least 2 arguments required, but only 1 passed
  
LaunchSubprocess@/usr/share/gnome-shell/extensions/d...@rastersoft.com/extension.js:492:54
  
launchDesktop@/usr/share/gnome-shell/extensions/d...@rastersoft.com/extension.js:443:27
  
innerEnable/data.dbusConnectionId<@/usr/share/gnome-shell/extensions/d...@rastersoft.com/extension.js:182:9

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons-ng/+bug/2004623/+subscriptions


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

[Desktop-packages] [Bug 2012691] Re: Triple buffering is missing/disabled in lunar

** Tags added: rls-ll-incoming

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

Title:
  Triple buffering is missing/disabled in lunar

Status in mutter package in Ubuntu:
  In Progress

Bug description:
  Triple buffering is missing/disabled in lunar

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


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

[Desktop-packages] [Bug 2012717] [NEW] Multi-monitor screen freeze when resuming from sleep

Public bug reported:

Testing GNOME 44 I find it can't resume from sleep properly if two
monitors are plugged in. Both monitors wake up, but one is completely
frozen and the other is partially frozen (stops responding to anything
but cursor movement).

Using Intel graphics with two USB-C monitors.

** Affects: mutter
 Importance: Unknown
 Status: Unknown

** Affects: mutter (Ubuntu)
 Importance: High
 Assignee: Daniel van Vugt (vanvugt)
 Status: In Progress


** Tags: lunar multimonitor rls-ll-incoming

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

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

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

Title:
  Multi-monitor screen freeze when resuming from sleep

Status in Mutter:
  Unknown
Status in mutter package in Ubuntu:
  In Progress

Bug description:
  Testing GNOME 44 I find it can't resume from sleep properly if two
  monitors are plugged in. Both monitors wake up, but one is completely
  frozen and the other is partially frozen (stops responding to anything
  but cursor movement).

  Using Intel graphics with two USB-C monitors.

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


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

[Desktop-packages] [Bug 1973467] Re: [Wayland] Backlight stays on with black screen when monitor should be sleeping

2023-03-24 Thread Michał Fita

Interesting thing is that I've reinstalled Kubuntu recently, then added
Wayland. Plasma on Wayland seem to disable screens correctly.

I've installed `ubuntu-desktop` and switch again to Gnome... and screens
remain backlighted. This time I haven't added any extensions.

Maybe some studies how Plasma deals with that would help solve this
annoying issue?

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

Title:
  [Wayland] Backlight stays on with black screen when monitor should be
  sleeping

Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  In Power -> Power Saving Options -> Screen Blank - the option states
  that the screen will be turned off after some period, which is what
  I'd expect from a sleep mode.

  I have a hybrid system. I have disabled the internal display and I use
  the external connected via HDMI (and I believe it is connected to the
  NVIDIA GPU). When the screen goes blank the external monitor is not
  turned off really. It goes blank but it is still turned on and glows,
  so no power is saved.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  510.60.02  Wed Mar 16 
11:24:05 UTC 2022
   GCC version:
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 15 19:16:56 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 630 [1028:0798]
   NVIDIA Corporation GP107M [GeForce GTX 1050 Ti Mobile] [10de:1c8c] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:0798]
  InstallationDate: Installed on 2022-05-01 (14 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Dell Inc. Inspiron 15 7000 Gaming
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic 
root=UUID=19e3ad11-d1ce-49ce-8809-80fc68612eb3 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/30/2021
  dmi.bios.release: 1.15
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.15.0
  dmi.board.name: 065C71
  dmi.board.vendor: Dell Inc.
  dmi.board.version: X02
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.0:bd08/30/2021:br1.15:svnDellInc.:pnInspiron157000Gaming:pvr:rvnDellInc.:rn065C71:rvrX02:cvnDellInc.:ct10:cvr:sku0798:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 15 7000 Gaming
  dmi.product.sku: 0798
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

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

2023-03-24 Thread Carl Martin MIkael Randau

Same problem here on Ubuntu 23.04 with wayland on AMD Ryzen 6850. Most
snaps only start occasionally from dash icon. Works every time from
console.

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

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

Status in gnome-shell package in Ubuntu:
  In Progress

Bug description:
  Hi,

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

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

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

  Recent updates included gnome-shell and libadwaita.

  ---

  I get this type of log for all problematic snaps:

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

  ---

  Context:

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

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

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


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

[Desktop-packages] [Bug 2012645] Re: Double icon in the dock starting system-monitor

** Tags added: rls-ll-incoming

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

Title:
  Double icon in the dock starting system-monitor

Status in gnome-shell package in Ubuntu:
  In Progress

Bug description:
  I have gnome-system-monitor pinned to the dock (favorites).
  When i click the icon in the dock a new icon with the red dot appears in the 
dock instead adding the red dot to the 1st icon.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: gnome-system-monitor 44~beta-1
  ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6
  Uname: Linux 6.2.0-18-generic x86_64
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 23 16:09:01 2023
  InstallationDate: Installed on 2023-02-25 (26 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230224)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: gnome-system-monitor
  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/2012645/+subscriptions


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

[Desktop-packages] [Bug 1967539] Re: All file downloads fail

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

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

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

Title:
  All file downloads fail

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  Moving to the snap version results in all file download failing.
  Message is just "failed".

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: firefox 1:1snap1-0ubuntu2
  Uname: Linux 5.16.0-18.2-liquorix-amd64 x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Fri Apr  1 15:56:13 2022
  InstallationDate: Installed on 2017-12-06 (1577 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  RebootRequiredPkgs: Error: path contained symlinks.
  Snap.Changes: no changes found
  SourcePackage: firefox
  UpgradeStatus: Upgraded to jammy on 2021-12-08 (114 days ago)

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


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

[Desktop-packages] [Bug 1532508] Re: Screen contents revealed briefly on resume, before even unlocking

2023-03-24 Thread Ralf Dünkelmann

Hi there,

I am using ubuntu budgie 22 on a tuxedo laptop and can reproduce
reveiling of content when I lock the screen and connect to an external
monitor afterwards. When connecting the monitor the lower part of the
screen is reveiled shortly. When disconnecting the monitor, the upper
part reveils (and stays visible). Everything before typing the password.

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

Title:
  Screen contents revealed briefly on resume, before even unlocking

Status in GNOME Shell:
  New
Status in Mutter:
  New
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Fix Released
Status in unity source package in Xenial:
  Fix Released
Status in gnome-shell package in Debian:
  Confirmed

Bug description:
  [Impact]

  When lock is enabled, the screen doesn't get blank/covered by
  lockscreen before suspending, thus on early resume the content might
  be shown.

  Video showing the bug: https://youtu.be/dDOgtK1MldI

  Reproduced on Ubuntu 2015.10, Ubuntu 2014.04

  [Test case]

  1. Work on highly secret files
  2. Close the lid of your laptop and go have a break
  3. Anyone who opens the lid of the laptop can see the secret files for a half 
second before the lock screen appears

  [Possible Regression]

  Content on screen isn't painted anymore and screen stays black.

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


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

[Desktop-packages] [Bug 2012698] [NEW] Plymouth is just a plain black screen