[Desktop-packages] [Bug 2022391] Re: security breach
[Expired for gnome-control-center (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-control-center (Ubuntu) Status: Incomplete => Expired -- 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/2022391 Title: security breach Status in gnome-control-center package in Ubuntu: Expired Bug description: i update to lunar-lobster a few days ago (40 days ).I understand that i as a beta version but when i go to the security settings i saw that my firmware didnt pass the test so i dont know if is a problem of the version or is my laptop's problem My computer hardware : System: Host: carlos-NBD-WXX9 Kernel: 6.2.0-20-generic arch: x86_64 bits: 64 Desktop: GNOME v: 44.0 Distro: Ubuntu 23.04 (Lunar Lobster) Machine: Type: Laptop System: HUAWEI product: NBD-WXX9 v: M1010 serial: Mobo: HUAWEI model: NBD-WXX9-PCB-B4 v: M1010 serial: UEFI: HUAWEI v: 2.30 date: 07/04/2022 Battery: ID-1: BAT1 charge: 17.9 Wh (33.0%) condition: 54.2/54.9 Wh (98.7%) volts: 7.5 min: 7.6 CPU: Info: quad core 11th Gen Intel Core i5-1135G7 [MT MCP] speed (MHz): avg: 1364 min/max: 400/4200 Graphics: Device-1: Intel TigerLake-LP GT2 [Iris Xe Graphics] driver: i915 v: kernel Device-2: Quanta ov9734_techfront_camera type: USB driver: uvcvideo Display: wayland server: X.Org v: 1.22.1.8 with: Xwayland v: 22.1.8 compositor: gnome-shell driver: X: loaded: modesetting unloaded: fbdev,vesa dri: iris gpu: i915 resolution: 1920x1080~60Hz API: OpenGL v: 4.6 Mesa 23.0.2 renderer: Mesa Intel Xe Graphics (TGL GT2) Network: Device-1: Intel Wi-Fi 6 AX201 driver: iwlwifi Drives: Local Storage: total: 476.94 GiB used: 149.06 GiB (31.3%) Info: Processes: 337 Uptime: 1h 35m Memory: 7.54 GiB used: 4.27 GiB (56.6%) Shell: Bash inxi: 3.3.25 Informe de seguridad del dispositivo == Detalles del informe Fecha generada: 2023-06-02 22:48:37 Versión de fwupd1.8.12 System details Modelo de hardware: HUAWEI NBD-WXX9 Procesador 11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz SO: Ubuntu 23.04 Nivel de seguridad: HSI:0! (v1.8.12) HSI-1 Pruebas Intel Management Engine Version: Falló (No válido) UEFI Platform Key: Correcto (Válido) TPM v2.0:Correcto (Encontrada) Firmware BIOS Region:Correcto (Bloqueada) Firmware Write Protection Lock: Correcto (Activada) Platform Debugging: Correcto (No activada) Intel Management Engine Manufacturing Mode: Correcto (Bloqueada) UEFI Secure Boot:Correcto (Activada) Firmware Write Protection: Correcto (No activada) Intel Management Engine Override:Correcto (Bloqueada) TPM Platform Configuration: Correcto (Válido) HSI-2 Pruebas Intel BootGuard Fuse:Correcto (Válido) Intel BootGuard Verified Boot: Falló (No válido) Intel BootGuard ACM Protected: Falló (No válido) Intel BootGuard: Correcto (Activada) TPM Reconstruction:Falló (No encontrada) IOMMU Protection: Falló (No encontrada) Platform Debugging: Correcto (Bloqueada) HSI-3 Pruebas Suspend To RAM: Correcto (No activada) Intel BootGuard Error Policy: Falló (No válido) Pre-boot DMA Protection: Correcto (Activada) Intel CET: Correcto (Activada) Suspend To Idle: Correcto (Activada) HSI-4 Pruebas Encrypted RAM: Falló (No admitida) Intel SMAP: Correcto (Activada) Pruebas de tiempo de ejecución Firmware Updater Verification: Correcto (No envenenado) Linux Kernel Lockdown: Correcto (Activada) Linux Swap:Falló (No cifrado) Linux Kernel Verification: Correcto (No envenenado) Intel CET: Correcto (Admitida) Eventos de seguridad del equipo 2023-04-21 20:11:14 Firmware Updater VerificationCorrecto (No activada → No envenenado) 2023-01-28 17:13:05 Firmware
[Desktop-packages] [Bug 1903632]
i can confirm tat LO is not really usable with a touchscreen at the moment. laptops with touch screen seem to become more and more common these days, i therefore think it would be great if LibreOffice would be able to assign this a higher priority. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1903632 Title: Touchscreen can't be used to scroll anymore. Instead it will select everything on its way. Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: Confirmed Bug description: Ever since I upgrade to 20.10 from 20.04, I have been experiencing this issue. There are times when a user might want to scroll their screen by touching their screen. But I can't do this anymore. I want to know what went wrong? What can I do? Any info is appreciated. Note: Currently, I can scroll without in issue in Nautilus. But I can't do the same in Firefox, Tor browser, Libre Office, etc. Except Nautilus, all apps select words on screen whenever I touch my screen to scroll. But we all know, SCROLL ≠ SELECT. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Nov 10 09:25:39 2020 DistUpgraded: 2020-10-28 23:47:17,717 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: groovy DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.14, 5.8.0-26-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 5500 [1028:0641] InstallationDate: Installed on 2020-02-16 (267 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. Inspiron 5548 ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_i45x0v@/vmlinuz-5.8.0-26-generic root=ZFS=rpool/ROOT/ubuntu_i45x0v ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to groovy on 2020-10-28 (12 days ago) dmi.bios.date: 05/28/2019 dmi.bios.release: 5.4 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0FFJC4 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A10 dmi.modalias: dmi:bvnDellInc.:bvrA10:bd05/28/2019:br5.4:svnDellInc.:pnInspiron5548:pvrA10:rvnDellInc.:rn0FFJC4:rvrA00:cvnDellInc.:ct8:cvrA10: dmi.product.name: Inspiron 5548 dmi.product.sku: 0641 dmi.product.version: A10 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.1-1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.1-1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1903632/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2047705] Re: Packaging ships /etc/gtk-3.0/settings.ini, forcing the GTK3 theme to Yaru and preventing flavors from overriding it with XDG configuration
This bug was fixed in the package lxqt-session - 1.4.0-0ubuntu3 --- lxqt-session (1.4.0-0ubuntu3) noble; urgency=medium * Copy over GTK 3 settings by default (LP: #2047705). -- Simon Quigley Fri, 29 Dec 2023 12:36:24 -0600 ** Changed in: lxqt-session (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/2047705 Title: Packaging ships /etc/gtk-3.0/settings.ini, forcing the GTK3 theme to Yaru and preventing flavors from overriding it with XDG configuration Status in gtk+3.0 package in Ubuntu: Confirmed Status in lxqt-session package in Ubuntu: Fix Released Bug description: Lubuntu uses Qt as the primary framework for most of the apps we ship. However, some functionality we ship in Lubuntu doesn't have a Qt application that provides that functionality, so we have some GTK3 apps that we ship as well. Starting in Lubuntu 24.04, we are adding and enabling the breeze-gtk-theme package, providing more uniform theming between Qt and GTK apps on Lubuntu. However, this bug makes this impossible. As we do not ship xsettingsd, but instead use the XDG specification for shipping configuration, we are attempting to place the default configuration files for GTK2 and GTK3 theming in /etc/xdg/xdg- Lubuntu/gtk-2.0/gtkrc and /etc/xdg/xdg-Lubuntu/gtk-3.0/settings.ini. This solutions works for GTK2 apps, however GTK3 apps silently ignore the vendored configuration file and are using a different theme. As it turns out, this is because the /etc directory is given higher priority than /etc/xdg/xdg-Lubuntu when searching for XDG configuration files, and as it happens, libgtk-3-0 ships a /etc/gtk-3.0/settings.ini file that sets Yaru as the default theme. GTK3 applications end up selecting this configuration file rather than /etc/xdg/xdg-Lubuntu/gtk-3.0/settings.ini. /etc/gtk-3.0 is, I would argue, *not* a place where GTK3's settings.ini file should go, as it makes it difficult for flavors who rely on XDG configuration to override it without risking a file conflict. (Technically I guess a flavor package *could* use dpkg- divert to simply "get rid of" the /etc/gtk-3.0/settings.ini file, but that seems like the wrong way to approach this.) ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: libgtk-3-0 3.24.38-5ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Fri Dec 29 10:08:23 2023 InstallationDate: Installed on 2023-10-22 (69 days ago) InstallationMedia: Lubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231010) SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/2047705/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1968907] Re: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed
This bug still exists in Ubuntu 22.04.3. gnome-session-bin is 42.0-1ubuntu2. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1968907 Title: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed Status in gnome-session: Fix Released Status in gnome-session package in Ubuntu: Fix Released Bug description: Hi, I see the following errors in the system logs: # journalctl | grep gnome-session-binary Apr 13 18:22:54 vougeot gnome-session[3453]: gnome-session-binary[3453]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed Apr 13 18:22:54 vougeot gnome-session[3453]: gnome-session-binary[3453]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed Apr 13 18:22:54 vougeot gnome-session-binary[3453]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed Apr 13 18:22:54 vougeot gnome-session-binary[3453]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-session-bin 42.0-1ubuntu2 Uname: Linux 5.17.2-051702-generic x86_64 ApportVersion: 2.20.11-0ubuntu81 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Apr 13 19:48:49 2022 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-session/+bug/1968907/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2047711] [NEW] console error after upgrade to ubuntu 22.04
Public bug reported:
>From my log file:
Dec 29 14:15:17 cerberus thunderbird.desktop[7609]: console.error: " tried to scroll to a row that doesn't exist: 4294967295"
Dec 29 14:15:17 cerberus thunderbird.desktop[7609]: JavaScript error:
chrome://messenger/content/about3Pane.js, line 4592: : Component returned
failure code: 0x80550018 [nsIMsgDBView.getFlagsAt]
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: thunderbird 1:115.5.0+build1-0ubuntu0.22.04.1
ProcVersionSignature: Ubuntu 5.15.0-91.101-generic 5.15.131
Uname: Linux 5.15.0-91-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC3: jlquinn5991 F pulseaudio
/dev/snd/controlC0: jlquinn5991 F pulseaudio
/dev/snd/controlC2: jlquinn5991 F pulseaudio
/dev/snd/controlC1: jlquinn5991 F pulseaudio
BuildID: 20231120220011
CasperMD5CheckResult: unknown
Channel: Unavailable
CurrentDesktop: ubuntu:GNOME
Date: Fri Dec 29 14:43:23 2023
ForcedLayersAccel: False
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
IncompatibleExtensions: Thunderbird (default) -
{972ce4c6-7e08-4474-a285-3208198ce6fd}
InstallationDate: Installed on 2020-05-29 (1308 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
IpRoute:
default via 192.168.1.1 dev enp4s0 proto dhcp metric 100
169.254.0.0/16 dev enp4s0 scope link metric 1000
192.168.1.0/24 dev enp4s0 proto kernel scope link src 192.168.1.110 metric 100
PrefErrors: Unexpected character ',' before close parenthesis @
/usr/lib/thunderbird/omni.ja:greprefs.js:299
PrefSources: prefs.js
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
Profiles: Profile0 (Default) - LastVersion=115.5.0/20231120220011 (In use)
RunningIncompatibleAddons: True
SourcePackage: thunderbird
UpgradeStatus: Upgraded to jammy on 2023-12-28 (1 days ago)
dmi.bios.date: 12/16/2019
dmi.bios.release: 5.11
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3.2
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: X10DAI
dmi.board.vendor: Supermicro
dmi.board.version: 1.01
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To be filled by O.E.M.
dmi.chassis.version: To be filled by O.E.M.
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr3.2:bd12/16/2019:br5.11:svnSupermicro:pnX10DAi:pvr123456789:rvnSupermicro:rnX10DAI:rvr1.01:cvnTobefilledbyO.E.M.:ct3:cvrTobefilledbyO.E.M.:sku083615D9:
dmi.product.family: SMC X10
dmi.product.name: X10DAi
dmi.product.sku: 083615D9
dmi.product.version: 123456789
dmi.sys.vendor: Supermicro
** Affects: thunderbird (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 thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/2047711
Title:
console error after upgrade to ubuntu 22.04
Status in thunderbird package in Ubuntu:
New
Bug description:
From my log file:
Dec 29 14:15:17 cerberus thunderbird.desktop[7609]: console.error:
" tried to scroll to a row that doesn't exist:
4294967295"
Dec 29 14:15:17 cerberus thunderbird.desktop[7609]: JavaScript error:
chrome://messenger/content/about3Pane.js, line 4592: : Component returned
failure code: 0x80550018 [nsIMsgDBView.getFlagsAt]
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: thunderbird 1:115.5.0+build1-0ubuntu0.22.04.1
ProcVersionSignature: Ubuntu 5.15.0-91.101-generic 5.15.131
Uname: Linux 5.15.0-91-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC3: jlquinn5991 F pulseaudio
/dev/snd/controlC0: jlquinn5991 F pulseaudio
/dev/snd/controlC2: jlquinn5991 F pulseaudio
/dev/snd/controlC1: jlquinn5991 F pulseaudio
BuildID: 20231120220011
CasperMD5CheckResult: unknown
Channel: Unavailable
CurrentDesktop: ubuntu:GNOME
Date: Fri Dec 29 14:43:23 2023
ForcedLayersAccel: False
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
IncompatibleExtensions: Thunderbird (default) -
{972ce4c6-7e08-4474-a285-3208198ce6fd}
InstallationDate: Installed on 2020-05-29 (1308 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64
(20190805)
IpRoute:
default via 192.168.1.1 dev enp4s0 proto dhcp metric 100
169.254.0.0/16 dev enp4s0 scope link metric 1000
192.168.1.0/24 dev enp4s0 proto kernel scope link src 192.168.1.110 metric
100
PrefErrors: Unexpected character ',' before close parenthesis @
/usr/lib/thunderbird/omni.ja:greprefs.js:299
PrefSources: prefs.js
ProcEnviron:
[Desktop-packages] [Bug 2047705] Re: Packaging ships /etc/gtk-3.0/settings.ini, forcing the GTK3 theme to Yaru and preventing flavors from overriding it with XDG configuration
** Also affects: lxqt-session (Ubuntu) Importance: Undecided Status: New ** Changed in: lxqt-session (Ubuntu) Status: New => In Progress ** Changed in: lxqt-session (Ubuntu) Importance: Undecided => High ** Changed in: lxqt-session (Ubuntu) Assignee: (unassigned) => Simon Quigley (tsimonq2) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/2047705 Title: Packaging ships /etc/gtk-3.0/settings.ini, forcing the GTK3 theme to Yaru and preventing flavors from overriding it with XDG configuration Status in gtk+3.0 package in Ubuntu: Confirmed Status in lxqt-session package in Ubuntu: In Progress Bug description: Lubuntu uses Qt as the primary framework for most of the apps we ship. However, some functionality we ship in Lubuntu doesn't have a Qt application that provides that functionality, so we have some GTK3 apps that we ship as well. Starting in Lubuntu 24.04, we are adding and enabling the breeze-gtk-theme package, providing more uniform theming between Qt and GTK apps on Lubuntu. However, this bug makes this impossible. As we do not ship xsettingsd, but instead use the XDG specification for shipping configuration, we are attempting to place the default configuration files for GTK2 and GTK3 theming in /etc/xdg/xdg- Lubuntu/gtk-2.0/gtkrc and /etc/xdg/xdg-Lubuntu/gtk-3.0/settings.ini. This solutions works for GTK2 apps, however GTK3 apps silently ignore the vendored configuration file and are using a different theme. As it turns out, this is because the /etc directory is given higher priority than /etc/xdg/xdg-Lubuntu when searching for XDG configuration files, and as it happens, libgtk-3-0 ships a /etc/gtk-3.0/settings.ini file that sets Yaru as the default theme. GTK3 applications end up selecting this configuration file rather than /etc/xdg/xdg-Lubuntu/gtk-3.0/settings.ini. /etc/gtk-3.0 is, I would argue, *not* a place where GTK3's settings.ini file should go, as it makes it difficult for flavors who rely on XDG configuration to override it without risking a file conflict. (Technically I guess a flavor package *could* use dpkg- divert to simply "get rid of" the /etc/gtk-3.0/settings.ini file, but that seems like the wrong way to approach this.) ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: libgtk-3-0 3.24.38-5ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Fri Dec 29 10:08:23 2023 InstallationDate: Installed on 2023-10-22 (69 days ago) InstallationMedia: Lubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231010) SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/2047705/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1958019]
(In reply to zacherytapp from comment #796) > Hey it looks like Lenovo has released a new BIOS version for the Legion S7 > 16ARHA7 Slim model (the one I have that still has no sound). I'm curious if > anyone has updated to this BIOS yet and if that's resolved any issues or if > this would allow further development on the audio issue. i got the sound working on my 16APH8 (Slim 7 AMD Gen 8 2023). I mainly followed this guide https://gist.github.com/masselstine/8fe9634b4c31cef07b8dfab089e4eb38 . Just check if the Cirrus chip is connected in I2C. You can know that by putting kernel in log level 7 and seeing logs in dmesg. Just make sure to shutdown and unplug power, wait about 10s and boot up again to test the sound everytime -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN49WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6: dmi.product.family: Legion 7 16ACHg6 dmi.product.name: 82N6 dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6 dmi.product.version: Legion 7 16ACHg6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1958019/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2047705] [NEW] Packaging ships /etc/gtk-3.0/settings.ini, forcing the GTK3 theme to Yaru and preventing flavors from overriding it with XDG configuration
Public bug reported: Lubuntu uses Qt as the primary framework for most of the apps we ship. However, some functionality we ship in Lubuntu doesn't have a Qt application that provides that functionality, so we have some GTK3 apps that we ship as well. Starting in Lubuntu 24.04, we are adding and enabling the breeze-gtk-theme package, providing more uniform theming between Qt and GTK apps on Lubuntu. However, this bug makes this impossible. As we do not ship xsettingsd, but instead use the XDG specification for shipping configuration, we are attempting to place the default configuration files for GTK2 and GTK3 theming in /etc/xdg/xdg- Lubuntu/gtk-2.0/gtkrc and /etc/xdg/xdg-Lubuntu/gtk-3.0/settings.ini. This solutions works for GTK2 apps, however GTK3 apps silently ignore the vendored configuration file and are using a different theme. As it turns out, this is because the /etc directory is given higher priority than /etc/xdg/xdg-Lubuntu when searching for XDG configuration files, and as it happens, libgtk-3-0 ships a /etc/gtk-3.0/settings.ini file that sets Yaru as the default theme. GTK3 applications end up selecting this configuration file rather than /etc/xdg/xdg- Lubuntu/gtk-3.0/settings.ini. /etc/gtk-3.0 is, I would argue, *not* a place where GTK3's settings.ini file should go, as it makes it difficult for flavors who rely on XDG configuration to override it without risking a file conflict. (Technically I guess a flavor package *could* use dpkg-divert to simply "get rid of" the /etc/gtk-3.0/settings.ini file, but that seems like the wrong way to approach this.) ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: libgtk-3-0 3.24.38-5ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Fri Dec 29 10:08:23 2023 InstallationDate: Installed on 2023-10-22 (69 days ago) InstallationMedia: Lubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231010) SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/2047705 Title: Packaging ships /etc/gtk-3.0/settings.ini, forcing the GTK3 theme to Yaru and preventing flavors from overriding it with XDG configuration Status in gtk+3.0 package in Ubuntu: New Bug description: Lubuntu uses Qt as the primary framework for most of the apps we ship. However, some functionality we ship in Lubuntu doesn't have a Qt application that provides that functionality, so we have some GTK3 apps that we ship as well. Starting in Lubuntu 24.04, we are adding and enabling the breeze-gtk-theme package, providing more uniform theming between Qt and GTK apps on Lubuntu. However, this bug makes this impossible. As we do not ship xsettingsd, but instead use the XDG specification for shipping configuration, we are attempting to place the default configuration files for GTK2 and GTK3 theming in /etc/xdg/xdg- Lubuntu/gtk-2.0/gtkrc and /etc/xdg/xdg-Lubuntu/gtk-3.0/settings.ini. This solutions works for GTK2 apps, however GTK3 apps silently ignore the vendored configuration file and are using a different theme. As it turns out, this is because the /etc directory is given higher priority than /etc/xdg/xdg-Lubuntu when searching for XDG configuration files, and as it happens, libgtk-3-0 ships a /etc/gtk-3.0/settings.ini file that sets Yaru as the default theme. GTK3 applications end up selecting this configuration file rather than /etc/xdg/xdg-Lubuntu/gtk-3.0/settings.ini. /etc/gtk-3.0 is, I would argue, *not* a place where GTK3's settings.ini file should go, as it makes it difficult for flavors who rely on XDG configuration to override it without risking a file conflict. (Technically I guess a flavor package *could* use dpkg- divert to simply "get rid of" the /etc/gtk-3.0/settings.ini file, but that seems like the wrong way to approach this.) ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: libgtk-3-0 3.24.38-5ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Fri Dec 29 10:08:23 2023 InstallationDate: Installed on 2023-10-22 (69 days ago) InstallationMedia: Lubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231010) SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/2047705/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to :
[Desktop-packages] [Bug 2047696] Re: Entire system becomes laggy for unknown reason
** Package changed: ubuntu => gnome-shell (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2047696 Title: Entire system becomes laggy for unknown reason Status in gnome-shell package in Ubuntu: New Bug description: Similar to whats described in https://bugs.launchpad.net/ubuntu/+bug/2032847 the system became super laggy since yesterday. It seems like something fundamental is affected. It can happen for typing, switching between tabs in browser (chrome or firefox), VS code (switching tabs, code highlighting), opening and closing applications, opening a new tmux session. Everything takes super long. Starting chromium or vs code will result in 100% cpu usage on all 8 cores according to htop for many seconds until it settles to stay around 30 to 50% all the time. Even opening a new browser tab causes comparable CPU load. But the described behaviour also happens without running chromium or vs code. Restarting gnome shell or gdm3 doesn't help. Switching back to Wayland doesn't help, there I even get mouse freezing. In summary, it seems like something multiplies the CPU usage of a lot of different processes. I've never seen anything like that. Yesterday I thought it could be the SSD breaking, because even booting (only after restart) took very long. But fsck before booting didn't show any problems. A full shutdown made it go away yesterday, and it seemed it would only appear again when I get notifications from Slack running in chromium, so I disabled it and was able to finish the work day. Today it started out well, I switched Slack to Firefox. But then it appeared again and now a shutdown doesn't fix it anymore. I know, it sounds funny, but I'm out of ideas even to narrow the source of the problem down and I really need this machine to work for work. Since yesterday I updated a system package called gjs (manually, since it was held back in sudo apt upgrade), which seems to be related to gnome-shell, it appears with quite high CPU usage in htop. I attached the output of journalctl -b0 and memfree -h, as this was asked in the thread mentioned above. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.9-0ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Dec 29 13:21:03 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-03-28 (640 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.9-0ubuntu5 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-09-06 (478 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2047696/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2047696] [NEW] Entire system becomes laggy for unknown reason
You have been subscribed to a public bug: Similar to whats described in https://bugs.launchpad.net/ubuntu/+bug/2032847 the system became super laggy since yesterday. It seems like something fundamental is affected. It can happen for typing, switching between tabs in browser (chrome or firefox), VS code (switching tabs, code highlighting), opening and closing applications, opening a new tmux session. Everything takes super long. Starting chromium or vs code will result in 100% cpu usage on all 8 cores according to htop for many seconds until it settles to stay around 30 to 50% all the time. Even opening a new browser tab causes comparable CPU load. But the described behaviour also happens without running chromium or vs code. Restarting gnome shell or gdm3 doesn't help. Switching back to Wayland doesn't help, there I even get mouse freezing. In summary, it seems like something multiplies the CPU usage of a lot of different processes. I've never seen anything like that. Yesterday I thought it could be the SSD breaking, because even booting (only after restart) took very long. But fsck before booting didn't show any problems. A full shutdown made it go away yesterday, and it seemed it would only appear again when I get notifications from Slack running in chromium, so I disabled it and was able to finish the work day. Today it started out well, I switched Slack to Firefox. But then it appeared again and now a shutdown doesn't fix it anymore. I know, it sounds funny, but I'm out of ideas even to narrow the source of the problem down and I really need this machine to work for work. Since yesterday I updated a system package called gjs (manually, since it was held back in sudo apt upgrade), which seems to be related to gnome-shell, it appears with quite high CPU usage in htop. I attached the output of journalctl -b0 and memfree -h, as this was asked in the thread mentioned above. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.9-0ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Dec 29 13:21:03 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-03-28 (640 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.9-0ubuntu5 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-09-06 (478 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- Entire system becomes laggy for unknown reason https://bugs.launchpad.net/bugs/2047696 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1984107] Re: Printer SSL certificates are added but never removed, resulting in "no suitable destination host found by cups-browsed"
Hello Valentijn and thanks for this bug report, it really helped me figure out an otherwise obscure printing issue. However I don't agree with the suggested solution: the security model of cups for ipps is TOFU (trust on first use): the certificate is accepted the first time and then expected to be the same in the future. This is why the printer certificate is saved to file in the first place. (This approach is similar to what SSH uses: the first time you connect to a host the pubkey is saved in authorized_keys; if at some point the key changes ssh will refuse to connect and require manual deletion of the old key from authorized_keys.) I think this is a UI issue: from the cups web interface or cups logs it was not clear at all that the issue was with ipps certificate validation. Cups (or maybe the ipps backend? I'm not that familiar with cups internals) should log a proper error message instead. -- 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/1984107 Title: Printer SSL certificates are added but never removed, resulting in "no suitable destination host found by cups-browsed" Status in cups package in Ubuntu: Confirmed Bug description: If a printer preferrably prints through ipps, Cups will store the printers (self signed) certificate in /etc/cups/ssl/ However, if this certificate becomes outdated or invalid, or if it changes, it will *not be removed* and Cups only complains that the "backend returned status 4", "No suitable destination host found by cups-browsed". Even removing the printer manually will not remove the old certificate, rendering the printer invalid for life: when te printer re-appears, the old, invalid certificate is still there, resulting in the printer still not working. Steps to reproduce: - use a printer that prefers ipps, let's call it printer_bob - let this printer appear in your printer list - make a test print - Now remove the printer and check that the certificate will survive: lpadmin -x printer_bob; ls -al /etc/cups/ssl/*bob*crt What happens: - certificate is still there What should happen: - a removed printer should not have a certificate left Now in this example, it's rather harmless because the certificate is probably still valid. But a printer update, rename or otherwise will render it invalid and printing will become impossible. You could simulate a name change for printers: mv /etc/cups/ssl/printer-carol.local.crt /etc/cups/ssl/printer-bob.local.crt Or simply mess up the certificate: sed -i '2s/./a/g' /etc/cups/ssl/printer-bob.local.crt After this, you will *not* be able to print to printer-bob, because bob has the wrong certificate (obviously). Removing printer-bob does not help. You will need to manually remove the certificate in order to make bob print again. /var/log/cups/error.log will only say that "no suitable destination host found", which is not true: there *is* a destination but the SSL certificate does not match and Cups will only try the first printing method, ipps. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1984107/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2047698] [NEW] I have no audio.
Public bug reported: Audio isn't working, I have tried everything including this bug report. Still no audio. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Dec 29 13:58:32 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation TigerLake-H GT1 [UHD Graphics] [8086:9a60] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation TigerLake-H GT1 [UHD Graphics] [8086:2212] InstallationDate: Installed on 2023-12-28 (0 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) MachineType: Default string Default string ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-39-generic root=UUID=b5301c3d-1b26-47f8-ad4f-90997f62a480 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/21/2023 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 5.19 dmi.board.asset.tag: Default string dmi.board.name: Default string dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr5.19:bd04/21/2023:br5.19:svnDefaultstring:pnDefaultstring:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: Default string dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Default string version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ubuntu wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2047698 Title: I have no audio. Status in xorg package in Ubuntu: New Bug description: Audio isn't working, I have tried everything including this bug report. Still no audio. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Dec 29 13:58:32 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation TigerLake-H GT1 [UHD Graphics] [8086:9a60] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation TigerLake-H GT1 [UHD Graphics] [8086:2212] InstallationDate: Installed on 2023-12-28 (0 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) MachineType: Default string Default string ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-39-generic root=UUID=b5301c3d-1b26-47f8-ad4f-90997f62a480 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/21/2023 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 5.19 dmi.board.asset.tag: Default string dmi.board.name: Default string dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr5.19:bd04/21/2023:br5.19:svnDefaultstring:pnDefaultstring:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: Default string
[Desktop-packages] [Bug 1984107] Re: Printer SSL certificates are added but never removed, resulting in "no suitable destination host found by cups-browsed"
Hello Valentijn and thanks for this bug report, it really helped me figure out an otherwise obscure printing issue. However I don't agree with the suggested solution: the security model of cups for ipps is TOFU (trust on first use): the certificate is accepted the first time and then expected to be the same in the future. This is why the printer certificate is saved to file in the first place. (This approach is similar to what SSH uses: the first time you connect to a host the pubkey is saved in authorized_keys; if at some point the key changes ssh will refuse to connect and require manual deletion of the old key from authorized_keys.) I think this is a UI issue: from the cups web interface or cups logs it was not clear at all that the issue was with ipps certificate validation. Cups (or maybe the ipps backend? I'm not that familiar with cups internals) should log a proper error message instead. ** Changed in: cups (Ubuntu) Status: New => Confirmed -- 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/1984107 Title: Printer SSL certificates are added but never removed, resulting in "no suitable destination host found by cups-browsed" Status in cups package in Ubuntu: Confirmed Bug description: If a printer preferrably prints through ipps, Cups will store the printers (self signed) certificate in /etc/cups/ssl/ However, if this certificate becomes outdated or invalid, or if it changes, it will *not be removed* and Cups only complains that the "backend returned status 4", "No suitable destination host found by cups-browsed". Even removing the printer manually will not remove the old certificate, rendering the printer invalid for life: when te printer re-appears, the old, invalid certificate is still there, resulting in the printer still not working. Steps to reproduce: - use a printer that prefers ipps, let's call it printer_bob - let this printer appear in your printer list - make a test print - Now remove the printer and check that the certificate will survive: lpadmin -x printer_bob; ls -al /etc/cups/ssl/*bob*crt What happens: - certificate is still there What should happen: - a removed printer should not have a certificate left Now in this example, it's rather harmless because the certificate is probably still valid. But a printer update, rename or otherwise will render it invalid and printing will become impossible. You could simulate a name change for printers: mv /etc/cups/ssl/printer-carol.local.crt /etc/cups/ssl/printer-bob.local.crt Or simply mess up the certificate: sed -i '2s/./a/g' /etc/cups/ssl/printer-bob.local.crt After this, you will *not* be able to print to printer-bob, because bob has the wrong certificate (obviously). Removing printer-bob does not help. You will need to manually remove the certificate in order to make bob print again. /var/log/cups/error.log will only say that "no suitable destination host found", which is not true: there *is* a destination but the SSL certificate does not match and Cups will only try the first printing method, ipps. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1984107/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2047687] [NEW] HP ScanJet 3670 failing to scan with "Failed to Scan - Unable to start scan" in Mantic
Public bug reported:
Recently unearthed the power supply to my flatbed scanner after being
without it for a year. In the interim, I migrated to a newer computer
running Ubuntu 23.10 Mantic.
I have added myself to the saned and scanner groups. and have logged
out, and logged back in again, as well as unplugged and replugged the
scanner into a different USB port.
Installed simple-scan package, and went to scan a test page with my HP
ScanJet 3670 USB flatbed scanner.
lsusb shows the scanner, and I can hear the stepper motor move a little,
and light in bed goes on, but it times out waiting for data.
Any ideas?
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: simple-scan 44.0+git20230905-0ubuntu1
ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Dec 29 19:48:38 2023
InstallationDate: Installed on 2023-11-25 (34 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic
root=UUID=e7ed7850-c7b5-48e9-aa48-4995fc8fbfc4 ro quiet splash vt.handoff=7
SourcePackage: simple-scan
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/08/2018
dmi.bios.release: 4.6
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P2.61
dmi.board.name: Z97 Pro4
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrP2.61:bd08/08/2018:br4.6:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
** Affects: simple-scan (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug mantic
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to simple-scan in Ubuntu.
https://bugs.launchpad.net/bugs/2047687
Title:
HP ScanJet 3670 failing to scan with "Failed to Scan - Unable to start
scan" in Mantic
Status in simple-scan package in Ubuntu:
New
Bug description:
Recently unearthed the power supply to my flatbed scanner after being
without it for a year. In the interim, I migrated to a newer computer
running Ubuntu 23.10 Mantic.
I have added myself to the saned and scanner groups. and have logged
out, and logged back in again, as well as unplugged and replugged the
scanner into a different USB port.
Installed simple-scan package, and went to scan a test page with my HP
ScanJet 3670 USB flatbed scanner.
lsusb shows the scanner, and I can hear the stepper motor move a
little, and light in bed goes on, but it times out waiting for data.
Any ideas?
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: simple-scan 44.0+git20230905-0ubuntu1
ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Dec 29 19:48:38 2023
InstallationDate: Installed on 2023-11-25 (34 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64
(20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic
root=UUID=e7ed7850-c7b5-48e9-aa48-4995fc8fbfc4 ro quiet splash vt.handoff=7
SourcePackage: simple-scan
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/08/2018
dmi.bios.release: 4.6
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P2.61
dmi.board.name: Z97 Pro4
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrP2.61:bd08/08/2018:br4.6:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
To manage notifications about this bug go to:
