[Desktop-packages] [Bug 2081692] Re: apparmor profile too restrictive : kernel logs spammed with ~/.cache/mesa_shader_cache_db accesses
In fact the problem comes from the apparmor package and this file:
/etc/apparmor.d/abstractions/mesa
which contains the following rules:
# User files
owner @{HOME}/.cache/ w, # if user clears all caches
owner @{HOME}/.cache/mesa_shader_cache/ rw,
whereas the Mesa shader cache is now named "mesa_shader_cache_db"
instead of "mesa_shader_cache".
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/2081692
Title:
apparmor profile too restrictive : kernel logs spammed with
~/.cache/mesa_shader_cache_db accesses
Status in apparmor package in Ubuntu:
New
Status in xorg-server package in Ubuntu:
New
Bug description:
Hi,
I am running Plasma on X11, and Xorg is running in AppArmor complain
mode:
# aa-status
[...]
1 processes are in complain mode.
/usr/lib/xorg/Xorg (5903) Xorg
The kernel logs are spammed with the following AppArmor messages:
# dmesg | grep mesa_shader_cache_db
[ 30.513476] audit: type=1400 audit(1727008543.347:433): apparmor="ALLOWED"
operation="mknod" class="file" profile="Xorg"
name="/home/bonnaudl/.cache/mesa_shader_cache_db/part0/mesa_cache.db" pid=5903
comm="Xorg" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000
[ 30.513562] audit: type=1400 audit(1727008543.347:434): apparmor="ALLOWED"
operation="open" class="file" profile="Xorg"
name="/home/bonnaudl/.cache/mesa_shader_cache_db/part0/mesa_cache.db" pid=5903
comm="Xorg" requested_mask="rc" denied_mask="rc" fsuid=1000 ouid=1000
[ 30.513584] audit: type=1400 audit(1727008543.347:435): apparmor="ALLOWED"
operation="open" class="file" profile="Xorg"
name="/home/bonnaudl/.cache/mesa_shader_cache_db/part0/mesa_cache.db" pid=5903
comm="Xorg" requested_mask="wr" denied_mask="wr" fsuid=1000 ouid=1000
[ 30.513592] audit: type=1400 audit(1727008543.347:436): apparmor="ALLOWED"
operation="mknod" class="file" profile="Xorg"
name="/home/bonnaudl/.cache/mesa_shader_cache_db/part0/mesa_cache.idx" pid=5903
comm="Xorg" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000
I think that the Xorg AppArmor profile should be updated to allow
those accesses.
ProblemType: Bug
DistroRelease: Ubuntu 24.10
Package: xserver-xorg-core 2:21.1.13-2ubuntu1
ProcVersionSignature: Ubuntu 6.11.0-7.7-generic 6.11.0-rc7
Uname: Linux 6.11.0-7-generic x86_64
ApportVersion: 2.30.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: KDE
Date: Mon Sep 23 09:36:08 2024
DistUpgraded: Fresh install
DistroCodename: oracular
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
Advanced Micro Devices, Inc. [AMD/ATI] Phoenix1 [1002:15bf] (rev d7)
(prog-if 00 [VGA controller])
Subsystem: Hewlett-Packard Company Device [103c:8b6e]
MachineType: HP HP EliteBook 865 16 inch G10 Notebook PC
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.11.0-7-generic
root=/dev/mapper/MonVolume-Racine ro vsyscall=none security=apparmor
preempt=full split_lock_detect=warn quiet splash
crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M
vt.handoff=7
SourcePackage: xorg-server
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/18/2024
dmi.bios.release: 5.11
dmi.bios.vendor: HP
dmi.bios.version: V82 Ver. 01.05.11
dmi.board.name: 8B6E
dmi.board.vendor: HP
dmi.board.version: KBC Version 60.2E.60
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.ec.firmware.release: 96.46
dmi.modalias:
dmi:bvnHP:bvrV82Ver.01.05.11:bd06/18/2024:br5.11:efr96.46:svnHP:pnHPEliteBook86516inchG10NotebookPC:pvrSBKPF:rvnHP:rn8B6E:rvrKBCVersion60.2E.60:cvnHP:ct10:cvr:sku70A94AV:
dmi.product.family: 103C_5336AN HP EliteBook
dmi.product.name: HP EliteBook 865 16 inch G10 Notebook PC
dmi.product.sku: 70A94AV
dmi.product.version: SBKPF
dmi.sys.vendor: HP
version.compiz: compiz 1:0.9.14.2+22.10.20220822-0ubuntu12
version.libdrm2: libdrm2 2.4.122-1
version.libgl1-mesa-dri: libgl1-mesa-dri 24.2.2-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.13-2ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build3
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
1:1.0.17-3ubuntu1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2081692/+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 2081692] [NEW] apparmor profile too restrictive : kernel logs spammed with ~/.cache/mesa_shader_cache_db accesses
Public bug reported: Hi, I am running Plasma on X11, and Xorg is running in AppArmor complain mode: # aa-status [...] 1 processes are in complain mode. /usr/lib/xorg/Xorg (5903) Xorg The kernel logs are spammed with the following AppArmor messages: # dmesg | grep mesa_shader_cache_db [ 30.513476] audit: type=1400 audit(1727008543.347:433): apparmor="ALLOWED" operation="mknod" class="file" profile="Xorg" name="/home/bonnaudl/.cache/mesa_shader_cache_db/part0/mesa_cache.db" pid=5903 comm="Xorg" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000 [ 30.513562] audit: type=1400 audit(1727008543.347:434): apparmor="ALLOWED" operation="open" class="file" profile="Xorg" name="/home/bonnaudl/.cache/mesa_shader_cache_db/part0/mesa_cache.db" pid=5903 comm="Xorg" requested_mask="rc" denied_mask="rc" fsuid=1000 ouid=1000 [ 30.513584] audit: type=1400 audit(1727008543.347:435): apparmor="ALLOWED" operation="open" class="file" profile="Xorg" name="/home/bonnaudl/.cache/mesa_shader_cache_db/part0/mesa_cache.db" pid=5903 comm="Xorg" requested_mask="wr" denied_mask="wr" fsuid=1000 ouid=1000 [ 30.513592] audit: type=1400 audit(1727008543.347:436): apparmor="ALLOWED" operation="mknod" class="file" profile="Xorg" name="/home/bonnaudl/.cache/mesa_shader_cache_db/part0/mesa_cache.idx" pid=5903 comm="Xorg" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000 I think that the Xorg AppArmor profile should be updated to allow those accesses. ProblemType: Bug DistroRelease: Ubuntu 24.10 Package: xserver-xorg-core 2:21.1.13-2ubuntu1 ProcVersionSignature: Ubuntu 6.11.0-7.7-generic 6.11.0-rc7 Uname: Linux 6.11.0-7-generic x86_64 ApportVersion: 2.30.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: KDE Date: Mon Sep 23 09:36:08 2024 DistUpgraded: Fresh install DistroCodename: oracular DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Phoenix1 [1002:15bf] (rev d7) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:8b6e] MachineType: HP HP EliteBook 865 16 inch G10 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.11.0-7-generic root=/dev/mapper/MonVolume-Racine ro vsyscall=none security=apparmor preempt=full split_lock_detect=warn quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M vt.handoff=7 SourcePackage: xorg-server UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/18/2024 dmi.bios.release: 5.11 dmi.bios.vendor: HP dmi.bios.version: V82 Ver. 01.05.11 dmi.board.name: 8B6E dmi.board.vendor: HP dmi.board.version: KBC Version 60.2E.60 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 96.46 dmi.modalias: dmi:bvnHP:bvrV82Ver.01.05.11:bd06/18/2024:br5.11:efr96.46:svnHP:pnHPEliteBook86516inchG10NotebookPC:pvrSBKPF:rvnHP:rn8B6E:rvrKBCVersion60.2E.60:cvnHP:ct10:cvr:sku70A94AV: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 865 16 inch G10 Notebook PC dmi.product.sku: 70A94AV dmi.product.version: SBKPF dmi.sys.vendor: HP version.compiz: compiz 1:0.9.14.2+22.10.20220822-0ubuntu12 version.libdrm2: libdrm2 2.4.122-1 version.libgl1-mesa-dri: libgl1-mesa-dri 24.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.13-2ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build3 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-3ubuntu1 ** Affects: apparmor (Ubuntu) Importance: Undecided Status: New ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug oracular ubuntu ** Also affects: apparmor (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/2081692 Title: apparmor profile too restrictive : kernel logs spammed with ~/.cache/mesa_shader_cache_db accesses Status in apparmor package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: Hi, I am running Plasma on X11, and Xorg is running in AppArmor complain mode: # aa-status [...] 1 processes are in complain mode. /usr/lib/xorg/Xorg (5903) Xorg The kernel logs are spammed with the following AppArmor messages: # dmesg | grep mesa_shader_cache_db [ 30.513476] audit: type=1400 audit(1727008543.347:433): apparmor="ALLOWED" operation="mknod" class="file" profile="Xorg" name="/home/bonnaudl/.cache/mesa_shader_cache_db/part0/mesa_cache.db" pid=5903 comm="Xorg" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000 [ 30.513562] audit: type=1400 audit(1727008543.347:434): a
[Desktop-packages] [Bug 2081635] [NEW] Error in 61-gdm.rules
Public bug reported: Hi, when my system boots and gdm is started, the following error messages are added to the logs: # journalctl | grep 61-gdm Sep 22 14:35:19 vougeot systemd-udevd[684]: /usr/lib/udev/rules.d/61-gdm.rules:96 GOTO="gdm_prefer_xorg" has no matching label, ignoring. Sep 22 14:35:19 vougeot systemd-udevd[684]: /usr/lib/udev/rules.d/61-gdm.rules:96 The line has no effect any more, dropping. ProblemType: Bug DistroRelease: Ubuntu 24.10 Package: gdm3 47.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.11.0-7.7-generic 6.11.0-rc7 Uname: Linux 6.11.0-7-generic x86_64 ApportVersion: 2.30.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sun Sep 22 16:06:10 2024 SourcePackage: gdm3 UpgradeStatus: Upgraded to oracular on 2024-09-22 (0 days ago) ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug oracular -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/2081635 Title: Error in 61-gdm.rules Status in gdm3 package in Ubuntu: New Bug description: Hi, when my system boots and gdm is started, the following error messages are added to the logs: # journalctl | grep 61-gdm Sep 22 14:35:19 vougeot systemd-udevd[684]: /usr/lib/udev/rules.d/61-gdm.rules:96 GOTO="gdm_prefer_xorg" has no matching label, ignoring. Sep 22 14:35:19 vougeot systemd-udevd[684]: /usr/lib/udev/rules.d/61-gdm.rules:96 The line has no effect any more, dropping. ProblemType: Bug DistroRelease: Ubuntu 24.10 Package: gdm3 47.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.11.0-7.7-generic 6.11.0-rc7 Uname: Linux 6.11.0-7-generic x86_64 ApportVersion: 2.30.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sun Sep 22 16:06:10 2024 SourcePackage: gdm3 UpgradeStatus: Upgraded to oracular on 2024-09-22 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2081635/+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 2078443] Re: Upgrade from 22.04 to 24.04.1 failed - firefox package
I was able to complete the upgrade using --fix-broken, dpkg --configure -a and apt dist-upgrade. Just need to remove the firefox/thunderbird snap packages and install them from dpkg. nvidia-driver is still 535 after upgrade. 550 is the latest. -- 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/2078443 Title: Upgrade from 22.04 to 24.04.1 failed - firefox package Status in firefox package in Ubuntu: New Status in snapd package in Ubuntu: New Status in ubuntu-release-upgrader package in Ubuntu: Triaged Bug description: Trying to upgrade my updated 22.04 to 24.04 using do-release-upgrade -d Upgrade failed Errors were encountered while processing: /var/cache/apt/archives/firefox_1%3a1snap1-0ubuntu5_amd64.deb ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/firefox.0.crash' /usr/bin/gdbus: error while loading shared libraries: libgio-2.0.so.0: cannot open shared object file: No such file or directory /usr/bin/gdbus: error while loading shared libraries: libgio-2.0.so.0: cannot open shared object file: No such file or directory /usr/bin/gdbus: error while loading shared libraries: libgio-2.0.so.0: cannot open shared object file: No such file or directory Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned an error code (1) Description:Ubuntu 22.04.4 LTS Release:22.04 firefox: Installed: 129.0.2+build1-0ubuntu0.22.04.1~mt1 Candidate: 1:1snap1-0ubuntu5 Version table: 1:1snap1-0ubuntu5 500 500 http://fr.archive.ubuntu.com/ubuntu noble/main amd64 Packages *** 129.0.2+build1-0ubuntu0.22.04.1~mt1 100 100 /var/lib/dpkg/status I don't use firefox snap package as my home directory is in /nethome/ and not in /home/ (is there a way to fix this ?) I had to remove the firefox snap package and install firefox using dpkg. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2078443/+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 2061997] [NEW] gnome-shell and fprintd : Authorization denied to :1.65 to call method 'Claim' for device 'Elan MOC Sensors': Device was already claimed
Public bug reported: Hi, I have registered a fingerprint in fprintd and when when system boots and starts gdm, the following error messages are logged: # journalctl -b | grep fprintd Apr 17 14:08:45 vougeot dbus-daemon[1799]: [system] Activating via systemd: service name='net.reactivated.Fprint' unit='fprintd.service' requested by ':1.42' (uid=108 pid=4112 comm="/usr/bin/gnome-shell") Apr 17 14:08:46 vougeot systemd[1]: Starting fprintd.service - Fingerprint Authentication Daemon... Apr 17 14:08:46 vougeot systemd[1]: Started fprintd.service - Fingerprint Authentication Daemon. Apr 17 14:08:52 vougeot fprintd[4606]: Authorization denied to :1.65 to call method 'Claim' for device 'Elan MOC Sensors': Device was already claimed ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-shell 46.0-0ubuntu4 Uname: Linux 6.8.7-060807-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Apr 17 14:19:44 2024 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 46.0-1ubuntu6 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: fprintd (Ubuntu) Importance: Undecided Status: New ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble ** Also affects: fprintd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2061997 Title: gnome-shell and fprintd : Authorization denied to :1.65 to call method 'Claim' for device 'Elan MOC Sensors': Device was already claimed Status in fprintd package in Ubuntu: New Status in gnome-shell package in Ubuntu: New Bug description: Hi, I have registered a fingerprint in fprintd and when when system boots and starts gdm, the following error messages are logged: # journalctl -b | grep fprintd Apr 17 14:08:45 vougeot dbus-daemon[1799]: [system] Activating via systemd: service name='net.reactivated.Fprint' unit='fprintd.service' requested by ':1.42' (uid=108 pid=4112 comm="/usr/bin/gnome-shell") Apr 17 14:08:46 vougeot systemd[1]: Starting fprintd.service - Fingerprint Authentication Daemon... Apr 17 14:08:46 vougeot systemd[1]: Started fprintd.service - Fingerprint Authentication Daemon. Apr 17 14:08:52 vougeot fprintd[4606]: Authorization denied to :1.65 to call method 'Claim' for device 'Elan MOC Sensors': Device was already claimed ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-shell 46.0-0ubuntu4 Uname: Linux 6.8.7-060807-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Apr 17 14:19:44 2024 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 46.0-1ubuntu6 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fprintd/+bug/2061997/+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 1847493] Re: recentmanager crashed with signal 5 in _g_log_abort()
This bug seems to be fixed in Ubuntu noble. Thanks! ** Package changed: gtk+3.0 (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => 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/1847493 Title: recentmanager crashed with signal 5 in _g_log_abort() Status in Ubuntu: Fix Released Bug description: recentmanager crashed while I was running gnome-desktop-testing-runner ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: gtk-3-examples 3.24.12-1ubuntu1 Uname: Linux 5.3.5-050305-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: KDE Date: Wed Oct 9 11:44:28 2019 ExecutablePath: /usr/libexec/installed-tests/gtk+/recentmanager ProcCmdline: /usr/libexec/installed-tests/gtk+/recentmanager --tap Signal: 5 SourcePackage: gtk+3.0 StacktraceTop: _g_log_abort (breakpoint=1) at ../../../glib/gmessages.c:554 g_log_writer_default (log_level=18, log_level@entry=G_LOG_LEVEL_WARNING, fields=fields@entry=0x7ffd694bb840, n_fields=n_fields@entry=6, user_data=user_data@entry=0x0) at ../../../glib/gmessages.c:2694 g_log_structured_array (n_fields=6, fields=0x7ffd694bb840, log_level=G_LOG_LEVEL_WARNING) at ../../../glib/gmessages.c:1925 g_log_structured_array (log_level=G_LOG_LEVEL_WARNING, fields=0x7ffd694bb840, n_fields=6) at ../../../glib/gmessages.c:1898 g_log_structured_standard (log_domain=log_domain@entry=0x7f4c5831c047 "Gtk", log_level=log_level@entry=G_LOG_LEVEL_WARNING, file=file@entry=0x7f4c58379b60 "../../../../gtk/gtkrecentmanager.c", line=, func=, message_format=) at ../../../glib/gmessages.c:1982 Title: recentmanager crashed with signal 5 in _g_log_abort() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip fuse kvm libvirt libvirt-qemu libvirtd lpadmin plugdev sambashare staff sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1847493/+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 1968901] Re: org.gnome.Shell.desktop: Window manager warning: Failed to parse saved session file
** Tags added: noble -- 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/1968901 Title: org.gnome.Shell.desktop: Window manager warning: Failed to parse saved session file Status in mutter package in Ubuntu: Confirmed Bug description: Hi, when I boot my system, the following warning message is logged: # journalctl | grep /var/lib/gdm3 Apr 13 18:22:56 vougeot org.gnome.Shell.desktop[3472]: Window manager warning: Failed to parse saved session file: Failed to open file “/var/lib/gdm3/.config/mutter/sessions/10f526ebe1d06fb2ad1649866974815191003453.ms”: No such file or directory Note that the missing file depends on the system. For instance, on another system: # journalctl | grep /var/lib/gdm3 Apr 13 14:34:45 jophur org.gnome.Shell.desktop[791]: Window manager warning: Failed to parse saved session file: Failed to open file “/var/lib/gdm3/.config/mutter/sessions/10a247c4d323226d33164985328443594000779.ms”: No such file or directory ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 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 18:15:28 2022 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gdm3 UpgradeStatus: Upgraded to jammy on 2022-04-12 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1968901/+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 1968910] Re: Extension NAME already installed in /usr/share/gnome-shell/extensions/NAME. /usr/share/gnome-shell/extensions/NAME will not be loaded
** Tags added: noble -- 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/1968910 Title: Extension NAME already installed in /usr/share/gnome- shell/extensions/NAME. /usr/share/gnome-shell/extensions/NAME will not be loaded Status in gnome-shell package in Ubuntu: Confirmed Bug description: Hi, I see the following error messages in the system logs about gnome- shell extensions: # journalctl | grep Extension [...] Apr 13 18:30:51 jophur gnome-shell[831]: Extension d...@rastersoft.com already installed in /usr/share/gnome-shell/extensions/d...@rastersoft.com. /usr/share/gnome-shell/extensions/d...@rastersoft.com will not be loaded Apr 13 18:30:51 jophur gnome-shell[831]: Extension ubuntu-appindicat...@ubuntu.com already installed in /usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com. /usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com will not be loaded Apr 13 18:30:51 jophur gnome-shell[831]: Extension ubuntu-d...@ubuntu.com already installed in /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com. /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com will not be loaded ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell-extension-ubuntu-dock 72~ubuntu3 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:57:37 2022 PackageArchitecture: all RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1968910/+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 2013544] Re: font names displayed in an unreadable way
** Bug watch added: gitlab.gnome.org/GNOME/gnome-font-viewer/-/issues #80 https://gitlab.gnome.org/GNOME/gnome-font-viewer/-/issues/80 ** Also affects: gnome-font-viewer via https://gitlab.gnome.org/GNOME/gnome-font-viewer/-/issues/80 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-font-viewer in Ubuntu. https://bugs.launchpad.net/bugs/2013544 Title: font names displayed in an unreadable way Status in GNOME Font Viewer: Unknown Status in gnome-font-viewer package in Ubuntu: New Bug description: Hi, in the attached screenshot, font names in the 4th row are displayed in a vertical way that is unreadable. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-font-viewer 44.0-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: KDE Date: Fri Mar 31 14:30:35 2023 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gnome-font-viewer UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-font-viewer/+bug/2013544/+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 2013544] Re: font names displayed in an unreadable way
Flatpak version of g-f-v ** Attachment added: "flatpak-gfv.png" https://bugs.launchpad.net/ubuntu/+source/gnome-font-viewer/+bug/2013544/+attachment/5765601/+files/flatpak-gfv.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-font-viewer in Ubuntu. https://bugs.launchpad.net/bugs/2013544 Title: font names displayed in an unreadable way Status in gnome-font-viewer package in Ubuntu: New Bug description: Hi, in the attached screenshot, font names in the 4th row are displayed in a vertical way that is unreadable. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-font-viewer 44.0-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: KDE Date: Fri Mar 31 14:30:35 2023 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gnome-font-viewer UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-font-viewer/+bug/2013544/+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 2013544] Re: font names displayed in an unreadable way
I doubt so because the flatpak version of gnome-font-viewer has no problem with the Cantarell font, but has a similar problem with other fonts. ** Tags added: noble -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-font-viewer in Ubuntu. https://bugs.launchpad.net/bugs/2013544 Title: font names displayed in an unreadable way Status in gnome-font-viewer package in Ubuntu: New Bug description: Hi, in the attached screenshot, font names in the 4th row are displayed in a vertical way that is unreadable. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-font-viewer 44.0-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: KDE Date: Fri Mar 31 14:30:35 2023 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gnome-font-viewer UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-font-viewer/+bug/2013544/+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 2061173] [NEW] Feature request : send a notification when print job and USB printer not connected
Public bug reported: Hello :), Thanks for your hard work. I have a printer Canon G7050. And I configured the drivers to use it on USB only. From time to time, I launch a print job, start the printer and forget to plug the USB cable in my laptop. I think it would be a very nice addition to have the system send a notification: "The print job cannot be sent because the USB printer is off or the cable is not plugged." I'm not certain that this feature request belongs to cups. Let me know if I should transfer this feature request somewhere else :) Thanks, best regards, Laurent Lyaudet ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Description changed: Hello :), Thanks for your hard work. I have a printer Canon G7050. And I configured the drivers to use it on USB only. From time to time, I launch a print job, start the printer and forget to plug the USB cable in my laptop. I think it would be a very nice addition to have the system send a notification: "The print job cannot be sent because the USB printer is off or the cable is not plugged." I'm not certain that this feature request belongs to cups. Let me know if I should transfer this feature request somewhere else :) Thanks, best regards, - Laurent Lyaudet + Laurent Lyaudet -- 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/2061173 Title: Feature request : send a notification when print job and USB printer not connected Status in cups package in Ubuntu: New Bug description: Hello :), Thanks for your hard work. I have a printer Canon G7050. And I configured the drivers to use it on USB only. From time to time, I launch a print job, start the printer and forget to plug the USB cable in my laptop. I think it would be a very nice addition to have the system send a notification: "The print job cannot be sent because the USB printer is off or the cable is not plugged." I'm not certain that this feature request belongs to cups. Let me know if I should transfer this feature request somewhere else :) Thanks, best regards, Laurent Lyaudet To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/2061173/+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 1568772] Re: Process '/usr/sbin/alsactl -E HOME=/run/alsa restore 0' failed with exit code 99.
** Bug watch added: Debian Bug tracker #959170 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959170 ** Also affects: alsa-driver (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959170 Importance: Unknown Status: Unknown ** Tags added: mantic -- 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/1568772 Title: Process '/usr/sbin/alsactl -E HOME=/run/alsa restore 0' failed with exit code 99. Status in alsa-driver package in Ubuntu: Confirmed Status in alsa-driver package in Debian: Unknown Bug description: Get that error logged into journalctl, on a fresh xenial 64 bits installed from mini.iso and sharing a /home partition with a wily installation. No third party package, only genuine default install. Note that sound has no trouble; only this logged. There is no sound card on this system, only a mobo chipset. systemd-udevd[412]: Process '/usr/sbin/alsactl -E HOME=/run/alsa restore 0' failed with exit code 99. systemd-udevd[407]: Process '/usr/sbin/alsactl -E HOME=/run/alsa restore 1' failed with exit code 99. Maybe its related to the 'i' aka '--no-init-fallback' found here: http://manpages.ubuntu.com/manpages/wily/man1/alsactl.1.html ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: oem1755 F pulseaudio /dev/snd/pcmC0D0p: oem1755 F...m pulseaudio /dev/snd/controlC0: oem1755 F pulseaudio CurrentDesktop: GNOME Date: Mon Apr 11 13:50:55 2016 PackageArchitecture: all SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3002 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5W DH Deluxe dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5W DH Deluxe dmi.product.version: System Version dmi.sys.vendor: ASUSTEK COMPUTER INC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1568772/+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 2037212] [NEW] ConfigurationDirectory 'bluetooth' already exists but the mode is different. (File system: 755 ConfigurationDirectoryMode: 555)
Public bug reported:
Hi,
when my system boots it logs the following warning in the journal:
$ journalctl | grep ConfigurationDirectory
Sep 24 13:20:56 vougeot (uetoothd)[2715]: ConfigurationDirectory 'bluetooth'
already exists but the mode is different. (File system: 755
ConfigurationDirectoryMode: 555)
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: bluez 5.68-0ubuntu1
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
Uname: Linux 6.5.0-5-generic x86_64
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Sun Sep 24 13:28:20 2023
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-5-generic
root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor
tpm_tis.interrupts=0 preempt=full split_lock_detect=off quiet splash
vt.handoff=7
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/26/2022
dmi.bios.release: 7.16
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: 1.07.16NRTR4
dmi.board.asset.tag: Tag 12345
dmi.board.name: NS50_70MU
dmi.board.vendor: TUXEDO
dmi.board.version: Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Notebook
dmi.chassis.version: N/A
dmi.ec.firmware.release: 7.7
dmi.modalias:
dmi:bvnINSYDECorp.:bvr1.07.16NRTR4:bd05/26/2022:br7.16:efr7.7:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50_70MU:rvrApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable:
dmi.product.family: Not Applicable
dmi.product.name: TUXEDO InfinityBook S 15 Gen6
dmi.product.sku: Not Applicable
dmi.product.version: Not Applicable
dmi.sys.vendor: TUXEDO
hciconfig:
hci0: Type: Primary Bus: USB
BD Address: 70:9C:D1:50:1F:7B ACL MTU: 1021:4 SCO MTU: 96:6
DOWN
RX bytes:20308 acl:0 sco:0 events:3292 errors:0
TX bytes:813298 acl:0 sco:0 commands:3290 errors:0
** Affects: bluez (Ubuntu)
Importance: Undecided
Status: New
** Affects: bluez (Debian)
Importance: Unknown
Status: Unknown
** Tags: amd64 apport-bug mantic
** Bug watch added: Debian Bug tracker #1017988
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017988
** Also affects: bluez (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017988
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2037212
Title:
ConfigurationDirectory 'bluetooth' already exists but the mode is
different. (File system: 755 ConfigurationDirectoryMode: 555)
Status in bluez package in Ubuntu:
New
Status in bluez package in Debian:
Unknown
Bug description:
Hi,
when my system boots it logs the following warning in the journal:
$ journalctl | grep ConfigurationDirectory
Sep 24 13:20:56 vougeot (uetoothd)[2715]: ConfigurationDirectory 'bluetooth'
already exists but the mode is different. (File system: 755
ConfigurationDirectoryMode: 555)
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: bluez 5.68-0ubuntu1
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
Uname: Linux 6.5.0-5-generic x86_64
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Sun Sep 24 13:28:20 2023
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-5-generic
root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor
tpm_tis.interrupts=0 preempt=full split_lock_detect=off quiet splash
vt.handoff=7
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/26/2022
dmi.bios.release: 7.16
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: 1.07.16NRTR4
dmi.board.asset.tag: Tag 12345
dmi.board.name: NS50_70MU
dmi.board.vendor: TUXEDO
dmi.board.version: Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Notebook
dmi.chassis.version: N/A
dmi.ec.firmware.release: 7.7
dmi.modalias:
dmi:bvnINSYDECorp.:bvr1.07.16NRTR4:bd05/26/2022:br7.16:efr7.7:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50_70MU:rvrApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable:
dmi.product.family: Not Applicable
dmi.product.name: TUXEDO InfinityBook S 15 Gen6
dmi.product.sku: Not Applicable
dmi.product.version: Not Applicable
dmi.sys.vendor: TUXEDO
hciconfig:
hci0:Type: Primary Bus: USB
BD Address: 70:9C:D1:50:1F:7B ACL MTU: 1021:4 SCO MTU: 96:6
DOWN
RX bytes:20308 acl:0 sco:0 events:3292 errors:0
TX bytes:813298 acl:0 sco:0 commands:3290 errors:0
To manage notifications about this bug go to:
ht
[Desktop-packages] [Bug 1629633] Re: evince displays blank thumbnails for some pages
** Tags added: mantic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1629633 Title: evince displays blank thumbnails for some pages Status in Evince: New Status in evince package in Ubuntu: Triaged Bug description: Hi, To reproduce this bug: - load the attached PS file into evince - if thumbnails are not displayed then press F9 and choose to display thumbnails - evince displayd a blank thumbnail for pages 6 and 7 ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: evince 3.22.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-19.21-lowlatency 4.8.0-rc8 Uname: Linux 4.8.0-19-lowlatency x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: KDE Date: Sun Oct 2 10:10:28 2016 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/1629633/+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 1762133] Re: gvfsd-smb-browse crashed with SIGABRT
I am closing this bug since I have not seen it again since my report. Thanks! ** Changed in: gvfs (Ubuntu) Status: New => Fix Released -- 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/1762133 Title: gvfsd-smb-browse crashed with SIGABRT Status in gvfs package in Ubuntu: Fix Released Bug description: I was not even using a SMB share when gvfsd-smb-browse crashed. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gvfs-backends 1.36.0-1ubuntu1 Uname: Linux 4.15.15-041515-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: KDE Date: Sat Apr 7 22:06:05 2018 ExecutablePath: /usr/lib/gvfs/gvfsd-smb-browse ProcCmdline: /usr/lib/gvfs/gvfsd-smb-browse --spawner :1.64 /org/gtk/gvfs/exec_spaw/10 Signal: 6 SourcePackage: gvfs StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libtalloc.so.2 _talloc_free () at /usr/lib/x86_64-linux-gnu/libtalloc.so.2 () at /usr/lib/x86_64-linux-gnu/libsmbconf.so.0 gencache_parse () at /usr/lib/x86_64-linux-gnu/libsmbconf.so.0 gencache_get_data_blob () at /usr/lib/x86_64-linux-gnu/libsmbconf.so.0 Title: gvfsd-smb-browse crashed with SIGABRT UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip fuse kvm libvirt libvirtd lpadmin plugdev sambashare staff sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1762133/+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 1799675] Re: /usr/bin/gnome-control-center:ERROR:../shell/cc-shell-model.c:458:cc_shell_model_set_panel_visibility: assertion failed: (valid)
In recent versions, gnome-control-center refuses to run under another desktop environment: $ gnome-control-center Running gnome-control-center is only supported under GNOME and Unity, exiting -- 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/1799675 Title: /usr/bin/gnome-control-center:ERROR:../shell/cc-shell- model.c:458:cc_shell_model_set_panel_visibility: assertion failed: (valid) Status in gnome-control-center: New Status in gnome-control-center package in Ubuntu: Triaged Status in gnome-control-center package in Fedora: Unknown Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-control-center. This problem was most recently seen with package version 1:3.30.1-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/8de5ebcde9e4492a3bc570a4caa376cefbdfcbec 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/gnome-control-center/+bug/1799675/+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 1877725] Re: Displays aberrant percentages for disks belonging to btrfs RAID volume
** Tags added: mantic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1877725 Title: Displays aberrant percentages for disks belonging to btrfs RAID volume Status in GNOME Disks: New Status in gnome-disk-utility package in Ubuntu: Triaged Bug description: Hi, when I use gnome-disks to display information about disks that belong to a btrfs RAID volume, I see percentages that are way above 100% (see screenshot below). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-disk-utility 3.36.1-1ubuntu1 Uname: Linux 5.6.11-050611-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sat May 9 11:18:26 2020 SourcePackage: gnome-disk-utility UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-disk-utility/+bug/1877725/+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 1922414] Re: ssh-agent fails to start (has_option: command not found)
** Changed in: lightdm (Ubuntu) Status: Confirmed => Invalid ** Changed in: lightdm Status: New => Invalid -- 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/1922414 Title: ssh-agent fails to start (has_option: command not found) Status in Light Display Manager: Invalid Status in gdm3 package in Ubuntu: Fix Released Status in lightdm package in Ubuntu: Invalid Status in xorg package in Ubuntu: Confirmed Bug description: Hi, I have been using ssh-agent for years and since I upgraded my system to Ubuntu 21.04/groovy, ssh-agent fails to start. Here is the error message: # journalctl | grep ssh-agent [...] Apr 02 20:16:32 vougeot /usr/libexec/gdm-x-session[3752]: /etc/X11/Xsession.d/90x11-common_ssh-agent: line 9: has_option: command not found ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: x11-common 1:7.7+22ubuntu1 Uname: Linux 5.11.11-05-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Sat Apr 3 09:02:46 2021 Dependencies: lsb-base 11.1.0ubuntu2 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: tuxedo-keyboard, 3.0.4, 5.11.0-13-generic, x86_64: installed tuxedo-keyboard, 3.0.4, 5.11.0-13-lowlatency, x86_64: installed tuxedo-keyboard, 3.0.4, 5.11.11-05-lowlatency, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation TigerLake GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Iris Xe Graphics [1558:51a1] MachineType: TUXEDO TUXEDO InfinityBook S 15 Gen6 PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.11-05-lowlatency root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/07/2020 dmi.bios.release: 7.3 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.03RTR dmi.board.name: NS50MU dmi.board.vendor: TUXEDO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.03RTR:bd09/07/2020:br7.3:efr7.2:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50MU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: TUXEDO InfinityBook S 15 Gen6 dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: TUXEDO version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu4 version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.1-1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.10-3ubuntu5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1922414/+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 1945907] Re: tracker-miner-fs-3 crashed with SIGSEGV
I am closing this bug since I have not seen a tracker crash since then. Thanks! ** Changed in: tracker-miners (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tracker-miners in Ubuntu. https://bugs.launchpad.net/bugs/1945907 Title: tracker-miner-fs-3 crashed with SIGSEGV Status in tracker-miners package in Ubuntu: Fix Released Bug description: I found a file in /var/crash after upgrading my system to Ubuntu 21.10 ProblemType: Crash DistroRelease: Ubuntu 21.10 Package: tracker-miner-fs 3.1.3-1 Uname: Linux 5.14.9-051409-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: unknown Date: Sun Oct 3 17:26:55 2021 ExecutablePath: /usr/libexec/tracker-miner-fs-3 ProcCmdline: /usr/libexec/tracker-miner-fs-3 SegvAnalysis: Segfault happened at: 0x7fb88ead6b97:mov0x8(%rax),%rcx PC (0x7fb88ead6b97) ok source "0x8(%rax)" (0x0008) not located in a known VMA region (needed readable region)! destination "%rcx" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: tracker-miners StacktraceTop: () at /lib/x86_64-linux-gnu/libtracker-sparql-3.0.so.0 g_task_return_now (task=0x5585cc574d80) at ../../../gio/gtask.c:1219 complete_in_idle_cb (task=0x5585cc574d80) at ../../../gio/gtask.c:1233 g_main_dispatch (context=0x5585cc569180) at ../../../glib/gmain.c:3337 g_main_context_dispatch (context=0x5585cc569180) at ../../../glib/gmain.c:4055 Title: tracker-miner-fs-3 crashed with SIGSEGV UpgradeStatus: Upgraded to impish on 2021-10-03 (0 days ago) UserGroups: N/A separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker-miners/+bug/1945907/+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 1968901] Re: org.gnome.Shell.desktop: Window manager warning: Failed to parse saved session file
** Tags added: mantic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1968901 Title: org.gnome.Shell.desktop: Window manager warning: Failed to parse saved session file Status in mutter package in Ubuntu: Confirmed Bug description: Hi, when I boot my system, the following warning message is logged: # journalctl | grep /var/lib/gdm3 Apr 13 18:22:56 vougeot org.gnome.Shell.desktop[3472]: Window manager warning: Failed to parse saved session file: Failed to open file “/var/lib/gdm3/.config/mutter/sessions/10f526ebe1d06fb2ad1649866974815191003453.ms”: No such file or directory Note that the missing file depends on the system. For instance, on another system: # journalctl | grep /var/lib/gdm3 Apr 13 14:34:45 jophur org.gnome.Shell.desktop[791]: Window manager warning: Failed to parse saved session file: Failed to open file “/var/lib/gdm3/.config/mutter/sessions/10a247c4d323226d33164985328443594000779.ms”: No such file or directory ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 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 18:15:28 2022 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gdm3 UpgradeStatus: Upgraded to jammy on 2022-04-12 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1968901/+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 1969015] Re: Recursion depth exceeded calculating colors
The bug has been fixed in mantic. Thanks! ** Changed in: yelp (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yelp in Ubuntu. https://bugs.launchpad.net/bugs/1969015 Title: Recursion depth exceeded calculating colors Status in yelp package in Ubuntu: Fix Released Bug description: Hi, here is the problem: $ yelp Recursion depth exceeded calculating green bg color. Using rgb(250,250,250) Recursion depth exceeded calculating dark fg color. Using rgb(80,82,81) Recursion depth exceeded calculating red bg color. Using rgb(250,250,250) Recursion depth exceeded calculating dark bg color. Using rgb(250,250,250) Recursion depth exceeded calculating yellow bg color. Using rgb(250,250,250) Recursion depth exceeded calculating orange bg color. Using rgb(254,250,250) Recursion depth exceeded calculating gray bg color. Using rgb(250,250,250) Recursion depth exceeded calculating purple bg color. Using rgb(250,250,250) Recursion depth exceeded calculating blue bg color. Using rgb(250,250,250) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: yelp 42.1-1 Uname: Linux 5.17.3-051703-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Apr 14 10:10:44 2022 SourcePackage: yelp UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yelp/+bug/1969015/+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 1968910] Re: Extension NAME already installed in /usr/share/gnome-shell/extensions/NAME. /usr/share/gnome-shell/extensions/NAME will not be loaded
** Tags added: mantic -- 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/1968910 Title: Extension NAME already installed in /usr/share/gnome- shell/extensions/NAME. /usr/share/gnome-shell/extensions/NAME will not be loaded Status in gnome-shell package in Ubuntu: Confirmed Bug description: Hi, I see the following error messages in the system logs about gnome- shell extensions: # journalctl | grep Extension [...] Apr 13 18:30:51 jophur gnome-shell[831]: Extension d...@rastersoft.com already installed in /usr/share/gnome-shell/extensions/d...@rastersoft.com. /usr/share/gnome-shell/extensions/d...@rastersoft.com will not be loaded Apr 13 18:30:51 jophur gnome-shell[831]: Extension ubuntu-appindicat...@ubuntu.com already installed in /usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com. /usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com will not be loaded Apr 13 18:30:51 jophur gnome-shell[831]: Extension ubuntu-d...@ubuntu.com already installed in /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com. /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com will not be loaded ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell-extension-ubuntu-dock 72~ubuntu3 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:57:37 2022 PackageArchitecture: all RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1968910/+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 1971242] Re: printing PDF appears always grey, no color
The bug was in cups.
** Changed in: okular (Ubuntu)
Status: Confirmed => Invalid
** Changed in: atril (Ubuntu)
Status: Confirmed => Invalid
--
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/1971242
Title:
printing PDF appears always grey, no color
Status in CUPS:
Fix Released
Status in atril package in Ubuntu:
Invalid
Status in cups package in Ubuntu:
Fix Released
Status in okular package in Ubuntu:
Invalid
Status in cups source package in Jammy:
Fix Released
Status in cups source package in Lunar:
Fix Released
Bug description:
After upgrading from 20.04 LTS to 22.04 LTS I can't print colored PDF
document. The print appears always b/w regardless color printing was
enabled or not. Printing from LibreOffice produces a color print. This
behavior (bug) is reproducible on three upgraded machines. It would be
nice to have color print back again.
[ Impact ]
If the PPD file for a printer has a ColorModel option and the only
choice in it for printing in color is not named RGB but CMYK instead,
the printer cannot be made printing in color with intuitive methods,
usually selcting the color choice in the print dialog (which makes
ColorModel=CMYK be sent along with the job).
Only an ugly command-line-based workaround, running the command
lpadmin -p PRINTER -o print-color-mode-default=color
makes the printer print in color.
An example for printers with such PPDs are printers from RICOH and OEM
(Lanier, InfoTec, Savin, ..), so many high-end color laser printers
are affected.
[ Test Plan ]
Remove the workaround if you had applied it:
lpadmin -p PRINTER -R print-color-mode-default
If you have an affected printer, print a PDF file (or use the print
functionality in an application) with colored content and choose the
setting for color printing in the print dialog. When printing via
command line do
lp -d PRINTER -o ColorModel=CMYK FILE.pdf
Without the SRU applied you will get a grayscale/monochrome printout,
with it applied, you will get a colored printout.
To test without a printer:
Stop CUPS:
sudo systemctl stop cups
Edit /etc/cups/cups-files.conf to have a line
FileDevice Yes
and start CUPS again:
sudo systemctl start cups
Then create a queue using the attached sample PPD file:
lpadmin -p color-test -E -v file:/tmp/printout -P Ricoh-
PDF_Printer-PDF.ppd
Print a file to this queue as described above. When the job is done
("lpstat" does not show it any more), open /tmp/printout with a text
editor. Check whether it contains a line
@PJL SET RENDERMODE=COLOR
near its beginning, and NOT a line
@PJL SET RENDERMODE=GRAYSCALE
[ Where problems could occur ]
The patches are simple and they are also for some time in newer CUPS
versions (2.4.2 and newer) which are included in several distributions
(Ubuntu 22.10, 23.04, and others) and did not cause any complaints
about color printing. So the regression potential is very low.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cups/+bug/1971242/+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 2013324] Re: gnome-desktop-testing-runner finds a crash in /usr/libexec/installed-tests/gtk+/scrolledwindow
I am closing this bug since it has been fixed in mantic. Thanks! ** Package changed: gtk+3.0 (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => 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/2013324 Title: gnome-desktop-testing-runner finds a crash in /usr/libexec/installed- tests/gtk+/scrolledwindow Status in Ubuntu: Fix Released Bug description: Hi, here is the problem: $ gnome-desktop-testing-runner [...] FAIL: gtk+/scrolledwindow.test (Child process killed by signal 6) ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gtk-3-examples 3.24.37-1ubuntu1 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: KDE Date: Thu Mar 30 12:05:24 2023 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/+bug/2013324/+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 2013544] Re: font names displayed in an unreadable way
** Tags added: mantic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-font-viewer in Ubuntu. https://bugs.launchpad.net/bugs/2013544 Title: font names displayed in an unreadable way Status in gnome-font-viewer package in Ubuntu: New Bug description: Hi, in the attached screenshot, font names in the 4th row are displayed in a vertical way that is unreadable. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-font-viewer 44.0-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: KDE Date: Fri Mar 31 14:30:35 2023 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gnome-font-viewer UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-font-viewer/+bug/2013544/+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 1922414] Re: ssh-agent fails to start (has_option: command not found)
Hi, the bug is still there on an Ubuntu 23.10/mantic system: # journalctl | grep has_option Sep 22 13:46:02 xeelee /usr/libexec/gdm-x-session[2101]: /etc/X11/Xsession.d/30x11-common_xresources: line 16: has_option: command not found Sep 22 13:46:03 xeelee /usr/libexec/gdm-x-session[2123]: /etc/X11/Xsession.d/75dbus_dbus-launch: line 9: has_option: command not found Sep 22 13:46:03 xeelee /usr/libexec/gdm-x-session[2150]: /etc/X11/Xsession.d/90x11-common_ssh-agent: line 9: has_option: command not found ** Tags added: lunar mantic -- 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/1922414 Title: ssh-agent fails to start (has_option: command not found) Status in Light Display Manager: New Status in gdm3 package in Ubuntu: Fix Released Status in lightdm package in Ubuntu: Confirmed Status in xorg package in Ubuntu: Confirmed Bug description: Hi, I have been using ssh-agent for years and since I upgraded my system to Ubuntu 21.04/groovy, ssh-agent fails to start. Here is the error message: # journalctl | grep ssh-agent [...] Apr 02 20:16:32 vougeot /usr/libexec/gdm-x-session[3752]: /etc/X11/Xsession.d/90x11-common_ssh-agent: line 9: has_option: command not found ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: x11-common 1:7.7+22ubuntu1 Uname: Linux 5.11.11-05-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Sat Apr 3 09:02:46 2021 Dependencies: lsb-base 11.1.0ubuntu2 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: tuxedo-keyboard, 3.0.4, 5.11.0-13-generic, x86_64: installed tuxedo-keyboard, 3.0.4, 5.11.0-13-lowlatency, x86_64: installed tuxedo-keyboard, 3.0.4, 5.11.11-05-lowlatency, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation TigerLake GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Iris Xe Graphics [1558:51a1] MachineType: TUXEDO TUXEDO InfinityBook S 15 Gen6 PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.11-05-lowlatency root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/07/2020 dmi.bios.release: 7.3 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.03RTR dmi.board.name: NS50MU dmi.board.vendor: TUXEDO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.03RTR:bd09/07/2020:br7.3:efr7.2:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50MU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: TUXEDO InfinityBook S 15 Gen6 dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: TUXEDO version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu4 version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.1-1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.10-3ubuntu5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1922414/+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 1968910] Re: Extension NAME already installed in /usr/share/gnome-shell/extensions/NAME. /usr/share/gnome-shell/extensions/NAME will not be loaded
Here is an updated error message list from lunar: # journalctl | grep Extension Jun 28 08:27:35 vougeot gnome-shell[4088]: Extension apps-m...@gnome-shell-extensions.gcampax.github.com already installed in /usr/share/gnome-shell/extensions/apps-m...@gnome-shell-extensions.gcampax.github.com. /usr/share/gnome-shell/extensions/apps-m...@gnome-shell-extensions.gcampax.github.com will not be loaded Jun 28 08:27:35 vougeot gnome-shell[4088]: Extension auto-move-wind...@gnome-shell-extensions.gcampax.github.com already installed in /usr/share/gnome-shell/extensions/auto-move-wind...@gnome-shell-extensions.gcampax.github.com. /usr/share/gnome-shell/extensions/auto-move-wind...@gnome-shell-extensions.gcampax.github.com will not be loaded Jun 28 08:27:35 vougeot gnome-shell[4088]: Extension drive-m...@gnome-shell-extensions.gcampax.github.com already installed in /usr/share/gnome-shell/extensions/drive-m...@gnome-shell-extensions.gcampax.github.com. /usr/share/gnome-shell/extensions/drive-m...@gnome-shell-extensions.gcampax.github.com will not be loaded Jun 28 08:27:35 vougeot gnome-shell[4088]: Extension launch-new-insta...@gnome-shell-extensions.gcampax.github.com already installed in /usr/share/gnome-shell/extensions/launch-new-insta...@gnome-shell-extensions.gcampax.github.com. /usr/share/gnome-shell/extensions/launch-new-insta...@gnome-shell-extensions.gcampax.github.com will not be loaded Jun 28 08:27:35 vougeot gnome-shell[4088]: Extension native-window-placem...@gnome-shell-extensions.gcampax.github.com already installed in /usr/share/gnome-shell/extensions/native-window-placem...@gnome-shell-extensions.gcampax.github.com. /usr/share/gnome-shell/extensions/native-window-placem...@gnome-shell-extensions.gcampax.github.com will not be loaded Jun 28 08:27:35 vougeot gnome-shell[4088]: Extension places-m...@gnome-shell-extensions.gcampax.github.com already installed in /usr/share/gnome-shell/extensions/places-m...@gnome-shell-extensions.gcampax.github.com. /usr/share/gnome-shell/extensions/places-m...@gnome-shell-extensions.gcampax.github.com will not be loaded Jun 28 08:27:35 vougeot gnome-shell[4088]: Extension screenshot-window-si...@gnome-shell-extensions.gcampax.github.com already installed in /usr/share/gnome-shell/extensions/screenshot-window-si...@gnome-shell-extensions.gcampax.github.com. /usr/share/gnome-shell/extensions/screenshot-window-si...@gnome-shell-extensions.gcampax.github.com will not be loaded Jun 28 08:27:35 vougeot gnome-shell[4088]: Extension ubuntu-appindicat...@ubuntu.com already installed in /usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com. /usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com will not be loaded Jun 28 08:27:35 vougeot gnome-shell[4088]: Extension ubuntu-d...@ubuntu.com already installed in /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com. /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com will not be loaded Jun 28 08:27:35 vougeot gnome-shell[4088]: Extension user-th...@gnome-shell-extensions.gcampax.github.com already installed in /usr/share/gnome-shell/extensions/user-th...@gnome-shell-extensions.gcampax.github.com. /usr/share/gnome-shell/extensions/user-th...@gnome-shell-extensions.gcampax.github.com will not be loaded Jun 28 08:27:35 vougeot gnome-shell[4088]: Extension window-l...@gnome-shell-extensions.gcampax.github.com already installed in /usr/share/gnome-shell/extensions/window-l...@gnome-shell-extensions.gcampax.github.com. /usr/share/gnome-shell/extensions/window-l...@gnome-shell-extensions.gcampax.github.com will not be loaded Jun 28 08:27:35 vougeot gnome-shell[4088]: Extension windowsnaviga...@gnome-shell-extensions.gcampax.github.com already installed in /usr/share/gnome-shell/extensions/windowsnaviga...@gnome-shell-extensions.gcampax.github.com. /usr/share/gnome-shell/extensions/windowsnaviga...@gnome-shell-extensions.gcampax.github.com will not be loaded Jun 28 08:27:35 vougeot gnome-shell[4088]: Extension workspace-indica...@gnome-shell-extensions.gcampax.github.com already installed in /usr/share/gnome-shell/extensions/workspace-indica...@gnome-shell-extensions.gcampax.github.com. /usr/share/gnome-shell/extensions/workspace-indica...@gnome-shell-extensions.gcampax.github.com will not be loaded Jun 28 08:27:35 vougeot gnome-shell[4088]: Extension d...@rastersoft.com already installed in /usr/share/gnome-shell/extensions/d...@rastersoft.com. /usr/share/gnome-shell/extensions/d...@rastersoft.com will not be loaded [...] ** Tags added: kinetic 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/1968910 Title: Extension NAME already installed in /usr/share/gnome- shell/extensions/NAME. /usr/share/gnome-shell/extensions/NAME will not be loaded Status in gnome-shell package in Ubuntu: Confirmed Bug description: Hi,
[Desktop-packages] [Bug 1968857] Re: Upgrading to jammy leaves obsolete conffiles
Thank you for the fix!
** Summary changed:
- upgading to jammy leaves obsolete conffiles
+ Upgrading to jammy leaves obsolete conffiles
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to policykit-1 in Ubuntu.
https://bugs.launchpad.net/bugs/1968857
Title:
Upgrading to jammy leaves obsolete conffiles
Status in policykit-1 package in Ubuntu:
Fix Committed
Status in policykit-1 package in Debian:
Fix Released
Bug description:
Hi,
after upgrading my system from impish to jammy, it is left with the
following obsolete conffiles:
$ dpkg-query -W -f='${Conffiles}\n' | grep obsolete
/etc/polkit-1/localauthority.conf.d/51-ubuntu-admin.conf
c4dbd2117c52f367f1e8b8c229686b10 obsolete
/etc/polkit-1/localauthority.conf.d/50-localauthority.conf
2adb9d174807b0a3521fabf03792fbc8 obsolete
/etc/pam.d/polkit-1 7c794427f656539b0d4659b030904fe0 obsolete
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: polkitd 0.105-33
Uname: Linux 5.17.2-051702-generic x86_64
ApportVersion: 2.20.11-0ubuntu81
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Wed Apr 13 10:58:03 2022
SourcePackage: policykit-1
UpgradeStatus: Upgraded to jammy on 2022-04-12 (0 days ago)
modified.conffile..etc.pam.d.polkit-1: [deleted]
modified.conffile..etc.polkit-1.localauthority.conf.d.50-localauthority.conf:
[deleted]
modified.conffile..etc.polkit-1.localauthority.conf.d.51-ubuntu-admin.conf:
[deleted]
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1968857/+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 1972790] Re: Can't connect to hotspot created on ubuntu
Hello, Thanks for your hard work :) I have the following bug when using Ubuntu Hotspot on my laptop : - my Android smartphone can connect to my laptop on the Wifi Hotspot Network - but my smartphone says it cannot connect to Internet through the Hotspot... XD which is kind of unfortunate since the goal was to access Internet :) I don't know if it should be better to create another bug report, since it is slightly different. Please, let me know :) I'm using latest Ubuntu 23.04 fully patched. I rarely use Hotspot feature, hence I cannot say if it worked on Ubuntu 22.10 or 22.04, etc. Let me know if you need more informations that I can provide. Best regards, Laurent Lyaudet -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1972790 Title: Can't connect to hotspot created on ubuntu Status in wpa package in Ubuntu: Confirmed Bug description: We currently have older systems (18.04) with hotspot's and we will migrate to 22.04. Anything work's fine, expect the hotspot. The Hotspot will be created and is visible in the WLAN-List, but if the security is set to "WPA & WPA2 Personal" we get the error message "Failed to connect to the network". If we change the Security to "WPA3 Personal" we get the error message "Invalid Password", even if the password is correct. As soon we remove the security (change it to "none"), we can connect with out any problems. We can reproduce it with a fresh installtion of the Ubuntu Server 22.04 and the following two commands: apt install network-manager nmcli c add type wifi ifname wlp3s0 con-name Hotspot autoconnect yes ssid test-ap 802-11-wireless.mode ap 802-11-wireless.band bg 802-11-wireless.mac-address "80:45:dd:f0:27:ba" wifi-sec.group ccmp wifi-sec.key-mgmt wpa-psk wifi-sec.pairwise ccmp wifi-sec.proto rsn wifi-sec.psk "test12345" ipv4.addresses 192.168.60.1/24 ipv4.method shared && nmcli connection up Hotspot We thought it could be similar to this issue: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267 Because if we test it with 20.04 it worked fine, because 20.04 uses the Version 2:2.9.0-21build1 as described in the Ticket. As @Sebastian Bacher suggested (https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/comments/58), i created a own report. In the attachment is the requested log file. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: wpasupplicant 2:2.10-6 [modified: lib/systemd/system/wpa_supplicant.service] ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue May 10 07:24:15 2022 InstallationDate: Installed on 2022-05-10 (0 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220421) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1972790/+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
Thanks for the fix! -- 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 1987528] Re: Since upgrade from 20.04 → 22.04 ; unable to print in color, only black and white
*** This bug is a duplicate of bug 1971242 *** https://bugs.launchpad.net/bugs/1971242 ** This bug has been marked a duplicate of bug 1971242 printing PDF appears always grey, no color -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-filters in Ubuntu. https://bugs.launchpad.net/bugs/1987528 Title: Since upgrade from 20.04 → 22.04 ; unable to print in color, only black and white Status in cups-filters package in Ubuntu: Confirmed Bug description: Hi, Printer ( in my context ) is Ricoh Aficio mpc 3002 and most Ricoh's drivers are open-source ( https://www.openprinting.org/printer/Ricoh/Ricoh-Aficio_MP_C3002 ) Since I « upgraded » my installation from 20.04 → 22.04, I'm unable to print in colors, only black and white, whatever I set in driver. I tried what's suggested in ⋅ https://askubuntu.com/questions/1410583/upgrading-to-22-04-printer-doesnt-works-in-color ⋅ https://discourse.ubuntubudgie.org/t/22-04-unable-to-add-printer-which-perfectly-worked-in-20-04/6209 I might go wrong somewhere cause I still can't manage to print in color. → the snap thing ( Gutenprint Printer Application ) does not detect my ( network ) printer, → I'm not sure of the name for PRINTER I should input in command « lpadmin -p PRINTER -o print-color-mode-default=color » ( and is this as normal user or sudo ? ) It seems related to ⋅ https://github.com/OpenPrinting/cups/issues/421 It's a regression ( as it used to work out of the box before 22.04 ). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1987528/+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 2013544] [NEW] font names displayed in an unreadable way
Public bug reported: Hi, in the attached screenshot, font names in the 4th row are displayed in a vertical way that is unreadable. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-font-viewer 44.0-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: KDE Date: Fri Mar 31 14:30:35 2023 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gnome-font-viewer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-font-viewer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-font-viewer in Ubuntu. https://bugs.launchpad.net/bugs/2013544 Title: font names displayed in an unreadable way Status in gnome-font-viewer package in Ubuntu: New Bug description: Hi, in the attached screenshot, font names in the 4th row are displayed in a vertical way that is unreadable. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-font-viewer 44.0-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: KDE Date: Fri Mar 31 14:30:35 2023 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gnome-font-viewer UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-font-viewer/+bug/2013544/+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 2013544] Re: font names displayed in an unreadable way
Screenshot ** Attachment added: "Screenshot_20230331_143235.png" https://bugs.launchpad.net/ubuntu/+source/gnome-font-viewer/+bug/2013544/+attachment/5659564/+files/Screenshot_20230331_143235.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-font-viewer in Ubuntu. https://bugs.launchpad.net/bugs/2013544 Title: font names displayed in an unreadable way Status in gnome-font-viewer package in Ubuntu: New Bug description: Hi, in the attached screenshot, font names in the 4th row are displayed in a vertical way that is unreadable. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-font-viewer 44.0-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: KDE Date: Fri Mar 31 14:30:35 2023 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gnome-font-viewer UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-font-viewer/+bug/2013544/+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 1629633] Re: evince displays blank thumbnails for some pages
This bug still exists in Ubuntu 23.04/lunar with this package version: Package: evince Version: 43.1-2build1 ** Tags added: kinetic lunar -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1629633 Title: evince displays blank thumbnails for some pages Status in Evince: New Status in evince package in Ubuntu: Triaged Bug description: Hi, To reproduce this bug: - load the attached PS file into evince - if thumbnails are not displayed then press F9 and choose to display thumbnails - evince displayd a blank thumbnail for pages 6 and 7 ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: evince 3.22.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-19.21-lowlatency 4.8.0-rc8 Uname: Linux 4.8.0-19-lowlatency x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: KDE Date: Sun Oct 2 10:10:28 2016 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/1629633/+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 1671519] Re: Please show hardening flags in about:buildconfig
Firefox changed completely since this report, so closing. ** Changed in: firefox (Ubuntu) Status: New => Invalid -- 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/1671519 Title: Please show hardening flags in about:buildconfig Status in firefox package in Ubuntu: Invalid Bug description: Hi, the firefox package provided by Ubuntu seems to be built with hardening flags, for instance: $ hardening-check /usr/lib/firefox/firefox /usr/lib/firefox/firefox: Position Independent Executable: yes Stack protected: yes Fortify Source functions: yes (some protected functions found) Read-only relocations: yes Immediate binding: yes $ hardening-check /usr/lib/firefox/libxul.so /usr/lib/firefox/libxul.so: Position Independent Executable: no, regular shared library (ignored) Stack protected: yes Fortify Source functions: yes (some protected functions found) Read-only relocations: yes Immediate binding: no, not found! but the compilation options (-fstack-protector-strong and -D_FORTIFY_SOURCE=2) do not show up in about:buildconfig. Here is what I have in about:buildconfig: about:buildconfig Source Built from https://hg.mozilla.org/releases/mozilla-release/rev/44d6a57ab554308585a67a13035d31b264be781e Build platform target x86_64-pc-linux-gnu Build tools CompilerVersion Compiler flags /usr/bin/gcc -std=gnu99 6.2.0 -Wall -Wempty-body -Wignored-qualifiers -Wpointer-arith -Wsign-compare -Wtype-limits -Wunreachable-code -Wno-error=maybe-uninitialized -Wno-error=deprecated-declarations -Wno-error=array-bounds -fno-lifetime-dse -fno-strict-aliasing -ffunction-sections -fdata-sections -fno-math-errno -pthread -pipe /usr/bin/g++ -std=gnu++11 6.2.0 -Wall -Wc++11-compat -Wempty-body -Wignored-qualifiers -Woverloaded-virtual -Wpointer-arith -Wsign-compare -Wtype-limits -Wunreachable-code -Wwrite-strings -Wno-invalid-offsetof -Wc++14-compat -Wno-error=maybe-uninitialized -Wno-error=deprecated-declarations -Wno-error=array-bounds -fno-lifetime-dse -fno-exceptions -fno-strict-aliasing -fno-rtti -ffunction-sections -fdata-sections -fno-exceptions -fno-math-errno -pthread -pipe -g -freorder-blocks -Os -fomit-frame-pointer When I look at the same page in the firefox build in Debian stretch, here is what I see: about:buildconfig Build platform target x86_64-pc-linux-gnu Build tools CompilerVersion Compiler flags gcc 6.3.0 -Wall -Wempty-body -Wpointer-to-int-cast -Wsign-compare -Wtype-limits -Wno-unused -Wcast-align -fstack-protector-strong -Wformat -Werror=format-security -fno-schedule-insns2 -fno-lifetime-dse -fno-delete-null-pointer-checks -std=gnu99 -fgnu89-inline -fno-strict-aliasing -ffunction-sections -fdata-sections -fno-math-errno -pthread -pipe g++ 6.3.0 -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wempty-body -Woverloaded-virtual -Wsign-compare -Wwrite-strings -Wno-invalid-offsetof -Wcast-align -fstack-protector-strong -Wformat -Werror=format-security -fno-schedule-insns2 -fno-lifetime-dse -fno-delete-null-pointer-checks -fno-exceptions -fno-strict-aliasing -fno-rtti -ffunction-sections -fdata-sections -fno-exceptions -fno-math-errno -std=gnu++0x -pthread -pipe -DNDEBUG -DTRIMMED -g -freorder-blocks -Os -fomit-frame-pointer The D_FORTIFY_SOURCE=2 and -fstack-protector-strong do show up which IMHO is a good thing from the point of view of someone who would like to check the hardening of firefox builds. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: firefox 52.0+build2-0ubuntu0.16.10.1 ProcVersionSignature: Error: [Errno 2] No such file or directory: '/proc/version_signature' Uname: Linux 4.10.1-041001-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bonnaudl 15515 F pulseaudio BuildID: 20170303012224 Channel: Unavailable CurrentDesktop: KDE Date: Thu Mar 9 15:55:13 2017 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePlugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so DefaultProfilePrefSources: /usr/lib/firefox/defaults/pref/all-ubuntumate.js prefs.js [Profile]/extensions/perspecti...@cmu.edu/defaults/preferences/prefs.js DefaultProfileThemes: extensions.sqlite corrupt or missing EcryptfsInUse: Yes ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 193.55.51.129 dev eth0 proto static metric 100 169.254.
[Desktop-packages] [Bug 2013324] [NEW] gnome-desktop-testing-runner finds a crash in /usr/libexec/installed-tests/gtk+/scrolledwindow
Public bug reported: Hi, here is the problem: $ gnome-desktop-testing-runner [...] FAIL: gtk+/scrolledwindow.test (Child process killed by signal 6) ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gtk-3-examples 3.24.37-1ubuntu1 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: KDE Date: Thu Mar 30 12:05:24 2023 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 lunar -- 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/2013324 Title: gnome-desktop-testing-runner finds a crash in /usr/libexec/installed- tests/gtk+/scrolledwindow Status in gtk+3.0 package in Ubuntu: New Bug description: Hi, here is the problem: $ gnome-desktop-testing-runner [...] FAIL: gtk+/scrolledwindow.test (Child process killed by signal 6) ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gtk-3-examples 3.24.37-1ubuntu1 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: KDE Date: Thu Mar 30 12:05:24 2023 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/2013324/+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 1877725] Re: Displays aberrant percentages for disks belonging to btrfs RAID volume
** Tags added: jammy lunar -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1877725 Title: Displays aberrant percentages for disks belonging to btrfs RAID volume Status in GNOME Disks: New Status in gnome-disk-utility package in Ubuntu: Triaged Bug description: Hi, when I use gnome-disks to display information about disks that belong to a btrfs RAID volume, I see percentages that are way above 100% (see screenshot below). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-disk-utility 3.36.1-1ubuntu1 Uname: Linux 5.6.11-050611-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sat May 9 11:18:26 2020 SourcePackage: gnome-disk-utility UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-disk-utility/+bug/1877725/+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 1968901] Re: org.gnome.Shell.desktop: Window manager warning: Failed to parse saved session file
** Tags added: kinetic lunar -- 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/1968901 Title: org.gnome.Shell.desktop: Window manager warning: Failed to parse saved session file Status in mutter package in Ubuntu: Confirmed Bug description: Hi, when I boot my system, the following warning message is logged: # journalctl | grep /var/lib/gdm3 Apr 13 18:22:56 vougeot org.gnome.Shell.desktop[3472]: Window manager warning: Failed to parse saved session file: Failed to open file “/var/lib/gdm3/.config/mutter/sessions/10f526ebe1d06fb2ad1649866974815191003453.ms”: No such file or directory Note that the missing file depends on the system. For instance, on another system: # journalctl | grep /var/lib/gdm3 Apr 13 14:34:45 jophur org.gnome.Shell.desktop[791]: Window manager warning: Failed to parse saved session file: Failed to open file “/var/lib/gdm3/.config/mutter/sessions/10a247c4d323226d33164985328443594000779.ms”: No such file or directory ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 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 18:15:28 2022 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gdm3 UpgradeStatus: Upgraded to jammy on 2022-04-12 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1968901/+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 1968999] Re: [jammy] Option "-listen" for file descriptors is deprecated. Please use "-listenfd" instead.
The bug is fixed in lunar. Thanks! ** Changed in: mutter (Ubuntu) Status: Triaged => Fix Released -- 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/1968999 Title: [jammy] Option "-listen" for file descriptors is deprecated. Please use "-listenfd" instead. Status in mutter package in Ubuntu: Fix Released Bug description: Hi, I see this warning message in the logs: root@vougeot:~# journalctl | grep -e -listen Apr 14 00:06:45 vougeot org.gnome.Shell.desktop[3461]: (WW) Option "-listen" for file descriptors is deprecated Apr 14 00:06:45 vougeot org.gnome.Shell.desktop[3461]: Please use "-listenfd" instead. Apr 14 00:06:45 vougeot org.gnome.Shell.desktop[3461]: (WW) Option "-listen" for file descriptors is deprecated Apr 14 00:06:45 vougeot org.gnome.Shell.desktop[3461]: Please use "-listenfd" instead. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 Uname: Linux 5.17.3-051703-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Apr 14 09:42:34 2022 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 42.0-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1968999/+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 1969015] Re: Recursion depth exceeded calculating colors
** Tags added: kinetic lunar -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yelp in Ubuntu. https://bugs.launchpad.net/bugs/1969015 Title: Recursion depth exceeded calculating colors Status in yelp package in Ubuntu: New Bug description: Hi, here is the problem: $ yelp Recursion depth exceeded calculating green bg color. Using rgb(250,250,250) Recursion depth exceeded calculating dark fg color. Using rgb(80,82,81) Recursion depth exceeded calculating red bg color. Using rgb(250,250,250) Recursion depth exceeded calculating dark bg color. Using rgb(250,250,250) Recursion depth exceeded calculating yellow bg color. Using rgb(250,250,250) Recursion depth exceeded calculating orange bg color. Using rgb(254,250,250) Recursion depth exceeded calculating gray bg color. Using rgb(250,250,250) Recursion depth exceeded calculating purple bg color. Using rgb(250,250,250) Recursion depth exceeded calculating blue bg color. Using rgb(250,250,250) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: yelp 42.1-1 Uname: Linux 5.17.3-051703-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Apr 14 10:10:44 2022 SourcePackage: yelp UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yelp/+bug/1969015/+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 is not fixed yet (no new package version has been released) ** Changed in: gnome-session (Ubuntu) Status: Fix Released => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1968907 Title: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed Status in gnome-session package in Ubuntu: Confirmed 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/ubuntu/+source/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 715874] Re: gnome thumbnailers should have an apparmor profile
** Tags added: focal jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-desktop3 in Ubuntu. https://bugs.launchpad.net/bugs/715874 Title: gnome thumbnailers should have an apparmor profile Status in gnome-desktop3 package in Ubuntu: Triaged Status in gnome-utils package in Ubuntu: Triaged Status in totem package in Ubuntu: Triaged Bug description: Binary package hint: gnome-control-center Nautilus normally uses gnome-thumbnail-font, to provide font previews. Eg: $ gconftool-2 -g /desktop/gnome/thumbnailers/application@x-font-ttf/enable true $ gconftool-2 -g /desktop/gnome/thumbnailers/application@x-font-ttf/command gnome-thumbnail-font %u %o If a flaw is discovered in a font library or Gnome and a user navigates to a directory that has a malicious font file, gnome- thumbnail-font could be used to execute arbitrary code, write out to files or leak information. Providing an apparmor profile for gnome- thumbnail-font would be a good step towards proactively protecting the user from this sort of attack. The same can be said for other thumbnailers. Nautilus also uses totem- video-thumbnail and evince-thumbnailer (evince-thumbnailer has an apparmor profile already). For images, nautilus uses gdk-pixbuf routines via gnome-desktop, but these can be altered to use evince- thumbnailer by installing schema files for the various image mime- types and updating gnome-desktop to not fallback to gdk-pixbuf on thumbnail script error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop3/+bug/715874/+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
> I have upgrade to 22.04, and thats two week i am unable to use my computer. Please note that my Ubuntu system is perfectly useable, even if it logs this error message. People having a black screen (or any other problem) should look elsewhere for a solution. -- 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 package in Ubuntu: Confirmed 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/ubuntu/+source/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 1629633] Re: evince displays blank thumbnails for some pages
This bug still exists in Ubuntu 22.04/jammy with this package version: Package: evince Version: 42.1-3 ** Tags added: jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1629633 Title: evince displays blank thumbnails for some pages Status in Evince: New Status in evince package in Ubuntu: Triaged Bug description: Hi, To reproduce this bug: - load the attached PS file into evince - if thumbnails are not displayed then press F9 and choose to display thumbnails - evince displayd a blank thumbnail for pages 6 and 7 ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: evince 3.22.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-19.21-lowlatency 4.8.0-rc8 Uname: Linux 4.8.0-19-lowlatency x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: KDE Date: Sun Oct 2 10:10:28 2016 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/1629633/+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 1968911] Re: assertion failures in cr_parser_new_from_buf and cr_declaration_parse_list_from_buf
After upgrading the gnome-shell package on my system, the following assertions are no longer present in the system logs: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed cr_declaration_parse_list_from_buf: assertion 'parser' failed Thanks a lot! -- 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/1968911 Title: assertion failures in cr_parser_new_from_buf and cr_declaration_parse_list_from_buf Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Jammy: Fix Committed Bug description: Impact -- gnome-shell is emitting a lot of warnings to the systemd journal Test Case - Install the update Restart your computer Log in. Run this command in a terminal. It should not return any thing. journalctl -b | grep cr_ What Could Go Wrong --- See the master bug for this update LP: #1973373 Original Bug Report --- Hi, I see the following assertion failures in the system logs: # journalctl | grep cr_ Apr 13 18:22:56 vougeot gnome-shell[3472]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed Apr 13 18:22:56 vougeot gnome-shell[3472]: cr_declaration_parse_list_from_buf: assertion 'parser' failed Apr 13 18:22:56 vougeot gnome-shell[3472]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed Apr 13 18:22:56 vougeot gnome-shell[3472]: cr_declaration_parse_list_from_buf: assertion 'parser' failed Apr 13 18:22:56 vougeot gnome-shell[3472]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed Apr 13 18:22:56 vougeot gnome-shell[3472]: cr_declaration_parse_list_from_buf: assertion 'parser' failed ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 Uname: Linux 5.17.2-051702-generic x86_64 ApportVersion: 2.20.11-0ubuntu81 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Apr 13 20:04:54 2022 DisplayManager: gdm3 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 42.0-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1968911/+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 1879137] Re: The snap-store is using hundreds of MiBs of RAM.
$ find /proc -maxdepth 2 -path "/proc/[0-9]*/status" -readable -exec awk
-v FS=":" '{process[$1]=$2;sub(/^[ \t]+/,"",process[$1]);} END
{if(process["VmSwap"] && process["VmSwap"] != "0 kB") printf "%10s %-30s
%20s\n",process["Pid"],process["Name"],process["VmSwap"]}' '{}' \; | awk
'{print $(NF-1),$0}' | sort -h | cut -d " " -f2-
snap-store eating my swap file
:(
--
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/1879137
Title:
The snap-store is using hundreds of MiBs of RAM.
Status in GNOME Software:
Unknown
Status in snap-store-desktop:
Confirmed
Status in gnome-software package in Ubuntu:
Confirmed
Bug description:
The snap-store process is intermittently using hundreds of megabytes
of RAM. Is this normal? Is there a solution?
Ubuntu 20.04
To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-software/+bug/1879137/+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 1968999] Re: [jammy] Option "-listen" for file descriptors is deprecated. Please use "-listenfd" instead.
I do not even have to log in to have those messages. They are generated by gdm before I log in. And gdm itself uses Wayland. -- 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/1968999 Title: [jammy] Option "-listen" for file descriptors is deprecated. Please use "-listenfd" instead. Status in gdm3 package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: Hi, I see this warning message in the logs: root@vougeot:~# journalctl | grep -e -listen Apr 14 00:06:45 vougeot org.gnome.Shell.desktop[3461]: (WW) Option "-listen" for file descriptors is deprecated Apr 14 00:06:45 vougeot org.gnome.Shell.desktop[3461]: Please use "-listenfd" instead. Apr 14 00:06:45 vougeot org.gnome.Shell.desktop[3461]: (WW) Option "-listen" for file descriptors is deprecated Apr 14 00:06:45 vougeot org.gnome.Shell.desktop[3461]: Please use "-listenfd" instead. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 Uname: Linux 5.17.3-051703-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Apr 14 09:42:34 2022 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 42.0-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1968999/+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 1969015] [NEW] Recursion depth exceeded calculating colors
Public bug reported: Hi, here is the problem: $ yelp Recursion depth exceeded calculating green bg color. Using rgb(250,250,250) Recursion depth exceeded calculating dark fg color. Using rgb(80,82,81) Recursion depth exceeded calculating red bg color. Using rgb(250,250,250) Recursion depth exceeded calculating dark bg color. Using rgb(250,250,250) Recursion depth exceeded calculating yellow bg color. Using rgb(250,250,250) Recursion depth exceeded calculating orange bg color. Using rgb(254,250,250) Recursion depth exceeded calculating gray bg color. Using rgb(250,250,250) Recursion depth exceeded calculating purple bg color. Using rgb(250,250,250) Recursion depth exceeded calculating blue bg color. Using rgb(250,250,250) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: yelp 42.1-1 Uname: Linux 5.17.3-051703-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Apr 14 10:10:44 2022 SourcePackage: yelp UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: yelp (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 yelp in Ubuntu. https://bugs.launchpad.net/bugs/1969015 Title: Recursion depth exceeded calculating colors Status in yelp package in Ubuntu: New Bug description: Hi, here is the problem: $ yelp Recursion depth exceeded calculating green bg color. Using rgb(250,250,250) Recursion depth exceeded calculating dark fg color. Using rgb(80,82,81) Recursion depth exceeded calculating red bg color. Using rgb(250,250,250) Recursion depth exceeded calculating dark bg color. Using rgb(250,250,250) Recursion depth exceeded calculating yellow bg color. Using rgb(250,250,250) Recursion depth exceeded calculating orange bg color. Using rgb(254,250,250) Recursion depth exceeded calculating gray bg color. Using rgb(250,250,250) Recursion depth exceeded calculating purple bg color. Using rgb(250,250,250) Recursion depth exceeded calculating blue bg color. Using rgb(250,250,250) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: yelp 42.1-1 Uname: Linux 5.17.3-051703-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Apr 14 10:10:44 2022 SourcePackage: yelp UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yelp/+bug/1969015/+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 1922539] Re: Option "-listen" for file descriptors is deprecated. Please use "-listenfd" instead.
*** This bug is a duplicate of bug 1968999 *** https://bugs.launchpad.net/bugs/1968999 OK, done and bugs merged. ** This bug has been marked a duplicate of bug 1968999 Option "-listen" for file descriptors is deprecated. Please use "-listenfd" instead. -- 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/1922539 Title: Option "-listen" for file descriptors is deprecated. Please use "-listenfd" instead. Status in mutter package in Ubuntu: Confirmed Bug description: Hi, I see this warning message in the logs: # journalctl | grep -e -listen Apr 02 20:16:24 vougeot org.gnome.Shell.desktop[3329]: (WW) Option "-listen" for file descriptors is deprecated Apr 02 20:16:24 vougeot org.gnome.Shell.desktop[3329]: Please use "-listenfd" instead. Apr 02 20:16:24 vougeot org.gnome.Shell.desktop[3329]: (WW) Option "-listen" for file descriptors is deprecated Apr 02 20:16:24 vougeot org.gnome.Shell.desktop[3329]: Please use "-listenfd" instead. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu1 Uname: Linux 5.11.11-05-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Mon Apr 5 10:07:15 2021 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 3.38.4-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1922539/+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 1968911] Re: assertion failures in cr_parser_new_from_buf and cr_declaration_parse_list_from_buf
Thanks for the upstream bug! -- 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/1968911 Title: assertion failures in cr_parser_new_from_buf and cr_declaration_parse_list_from_buf Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Confirmed Bug description: Hi, I see the following assertion failures in the system logs: # journalctl | grep cr_ Apr 13 18:22:56 vougeot gnome-shell[3472]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed Apr 13 18:22:56 vougeot gnome-shell[3472]: cr_declaration_parse_list_from_buf: assertion 'parser' failed Apr 13 18:22:56 vougeot gnome-shell[3472]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed Apr 13 18:22:56 vougeot gnome-shell[3472]: cr_declaration_parse_list_from_buf: assertion 'parser' failed Apr 13 18:22:56 vougeot gnome-shell[3472]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed Apr 13 18:22:56 vougeot gnome-shell[3472]: cr_declaration_parse_list_from_buf: assertion 'parser' failed ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 Uname: Linux 5.17.2-051702-generic x86_64 ApportVersion: 2.20.11-0ubuntu81 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Apr 13 20:04:54 2022 DisplayManager: gdm3 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 42.0-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1968911/+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 1968999] [NEW] Option "-listen" for file descriptors is deprecated. Please use "-listenfd" instead.
Public bug reported: Hi, I see this warning message in the logs: root@vougeot:~# journalctl | grep -e -listen Apr 14 00:06:45 vougeot org.gnome.Shell.desktop[3461]: (WW) Option "-listen" for file descriptors is deprecated Apr 14 00:06:45 vougeot org.gnome.Shell.desktop[3461]: Please use "-listenfd" instead. Apr 14 00:06:45 vougeot org.gnome.Shell.desktop[3461]: (WW) Option "-listen" for file descriptors is deprecated Apr 14 00:06:45 vougeot org.gnome.Shell.desktop[3461]: Please use "-listenfd" instead. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 Uname: Linux 5.17.3-051703-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Apr 14 09:42:34 2022 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 42.0-3ubuntu1 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/1968999 Title: Option "-listen" for file descriptors is deprecated. Please use "-listenfd" instead. Status in gnome-shell package in Ubuntu: New Bug description: Hi, I see this warning message in the logs: root@vougeot:~# journalctl | grep -e -listen Apr 14 00:06:45 vougeot org.gnome.Shell.desktop[3461]: (WW) Option "-listen" for file descriptors is deprecated Apr 14 00:06:45 vougeot org.gnome.Shell.desktop[3461]: Please use "-listenfd" instead. Apr 14 00:06:45 vougeot org.gnome.Shell.desktop[3461]: (WW) Option "-listen" for file descriptors is deprecated Apr 14 00:06:45 vougeot org.gnome.Shell.desktop[3461]: Please use "-listenfd" instead. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 Uname: Linux 5.17.3-051703-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Apr 14 09:42:34 2022 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 42.0-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1968999/+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 1968910] Re: Extension NAME already installed in /usr/share/gnome-shell/extensions/NAME. /usr/share/gnome-shell/extensions/NAME will not be loaded
Thanks for the better title and for reassigning this bug! -- 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/1968910 Title: Extension NAME already installed in /usr/share/gnome- shell/extensions/NAME. /usr/share/gnome-shell/extensions/NAME will not be loaded Status in gnome-shell package in Ubuntu: New Bug description: Hi, I see the following error messages in the system logs about gnome- shell extensions: # journalctl | grep Extension [...] Apr 13 18:30:51 jophur gnome-shell[831]: Extension d...@rastersoft.com already installed in /usr/share/gnome-shell/extensions/d...@rastersoft.com. /usr/share/gnome-shell/extensions/d...@rastersoft.com will not be loaded Apr 13 18:30:51 jophur gnome-shell[831]: Extension ubuntu-appindicat...@ubuntu.com already installed in /usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com. /usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com will not be loaded Apr 13 18:30:51 jophur gnome-shell[831]: Extension ubuntu-d...@ubuntu.com already installed in /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com. /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com will not be loaded ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell-extension-ubuntu-dock 72~ubuntu3 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:57:37 2022 PackageArchitecture: all RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1968910/+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 1968911] [NEW] assertion failures in cr_parser_new_from_buf and cr_declaration_parse_list_from_buf
Public bug reported: Hi, I see the following assertion failures in the system logs: # journalctl | grep cr_ Apr 13 18:22:56 vougeot gnome-shell[3472]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed Apr 13 18:22:56 vougeot gnome-shell[3472]: cr_declaration_parse_list_from_buf: assertion 'parser' failed Apr 13 18:22:56 vougeot gnome-shell[3472]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed Apr 13 18:22:56 vougeot gnome-shell[3472]: cr_declaration_parse_list_from_buf: assertion 'parser' failed Apr 13 18:22:56 vougeot gnome-shell[3472]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed Apr 13 18:22:56 vougeot gnome-shell[3472]: cr_declaration_parse_list_from_buf: assertion 'parser' failed ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 Uname: Linux 5.17.2-051702-generic x86_64 ApportVersion: 2.20.11-0ubuntu81 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Apr 13 20:04:54 2022 DisplayManager: gdm3 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 42.0-3ubuntu1 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/1968911 Title: assertion failures in cr_parser_new_from_buf and cr_declaration_parse_list_from_buf Status in gnome-shell package in Ubuntu: New Bug description: Hi, I see the following assertion failures in the system logs: # journalctl | grep cr_ Apr 13 18:22:56 vougeot gnome-shell[3472]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed Apr 13 18:22:56 vougeot gnome-shell[3472]: cr_declaration_parse_list_from_buf: assertion 'parser' failed Apr 13 18:22:56 vougeot gnome-shell[3472]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed Apr 13 18:22:56 vougeot gnome-shell[3472]: cr_declaration_parse_list_from_buf: assertion 'parser' failed Apr 13 18:22:56 vougeot gnome-shell[3472]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed Apr 13 18:22:56 vougeot gnome-shell[3472]: cr_declaration_parse_list_from_buf: assertion 'parser' failed ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 Uname: Linux 5.17.2-051702-generic x86_64 ApportVersion: 2.20.11-0ubuntu81 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Apr 13 20:04:54 2022 DisplayManager: gdm3 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 42.0-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1968911/+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 1968910] [NEW] Extension drive-m...@gnome-shell-extensions.gcampax.github.com already installed in /usr/share/gnome-shell/extensions/
Public bug reported: Hi, I see the following error messages in the system logs about gnome-shell extensions: # journalctl | grep Extension [...] Apr 13 18:30:51 jophur gnome-shell[831]: Extension d...@rastersoft.com already installed in /usr/share/gnome-shell/extensions/d...@rastersoft.com. /usr/share/gnome-shell/extensions/d...@rastersoft.com will not be loaded Apr 13 18:30:51 jophur gnome-shell[831]: Extension ubuntu-appindicat...@ubuntu.com already installed in /usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com. /usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com will not be loaded Apr 13 18:30:51 jophur gnome-shell[831]: Extension ubuntu-d...@ubuntu.com already installed in /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com. /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com will not be loaded ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell-extension-ubuntu-dock 72~ubuntu3 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:57:37 2022 PackageArchitecture: all RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell-extension-ubuntu-dock (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-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1968910 Title: Extension drive-m...@gnome-shell-extensions.gcampax.github.com already installed in /usr/share/gnome-shell/extensions/ Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: Hi, I see the following error messages in the system logs about gnome- shell extensions: # journalctl | grep Extension [...] Apr 13 18:30:51 jophur gnome-shell[831]: Extension d...@rastersoft.com already installed in /usr/share/gnome-shell/extensions/d...@rastersoft.com. /usr/share/gnome-shell/extensions/d...@rastersoft.com will not be loaded Apr 13 18:30:51 jophur gnome-shell[831]: Extension ubuntu-appindicat...@ubuntu.com already installed in /usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com. /usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com will not be loaded Apr 13 18:30:51 jophur gnome-shell[831]: Extension ubuntu-d...@ubuntu.com already installed in /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com. /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com will not be loaded ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell-extension-ubuntu-dock 72~ubuntu3 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:57:37 2022 PackageArchitecture: all RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1968910/+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] [NEW] GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed
Public bug reported: 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) ** Affects: gnome-session (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-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 package in Ubuntu: New 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/ubuntu/+source/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 1968901] [NEW] org.gnome.Shell.desktop: Window manager warning: Failed to parse saved session file
Public bug reported: Hi, when I boot my system, the following warning message is logged: # journalctl | grep /var/lib/gdm3 Apr 13 18:22:56 vougeot org.gnome.Shell.desktop[3472]: Window manager warning: Failed to parse saved session file: Failed to open file “/var/lib/gdm3/.config/mutter/sessions/10f526ebe1d06fb2ad1649866974815191003453.ms”: No such file or directory Note that the missing file depends on the system. For instance, on another system: # journalctl | grep /var/lib/gdm3 Apr 13 14:34:45 jophur org.gnome.Shell.desktop[791]: Window manager warning: Failed to parse saved session file: Failed to open file “/var/lib/gdm3/.config/mutter/sessions/10a247c4d323226d33164985328443594000779.ms”: No such file or directory ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 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 18:15:28 2022 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gdm3 UpgradeStatus: Upgraded to jammy on 2022-04-12 (1 days ago) ** Affects: gdm3 (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 gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1968901 Title: org.gnome.Shell.desktop: Window manager warning: Failed to parse saved session file Status in gdm3 package in Ubuntu: New Bug description: Hi, when I boot my system, the following warning message is logged: # journalctl | grep /var/lib/gdm3 Apr 13 18:22:56 vougeot org.gnome.Shell.desktop[3472]: Window manager warning: Failed to parse saved session file: Failed to open file “/var/lib/gdm3/.config/mutter/sessions/10f526ebe1d06fb2ad1649866974815191003453.ms”: No such file or directory Note that the missing file depends on the system. For instance, on another system: # journalctl | grep /var/lib/gdm3 Apr 13 14:34:45 jophur org.gnome.Shell.desktop[791]: Window manager warning: Failed to parse saved session file: Failed to open file “/var/lib/gdm3/.config/mutter/sessions/10a247c4d323226d33164985328443594000779.ms”: No such file or directory ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 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 18:15:28 2022 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gdm3 UpgradeStatus: Upgraded to jammy on 2022-04-12 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1968901/+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 1922539] Re: Option "-listen" for file descriptors is deprecated. Please use "-listenfd" instead.
I am reopening this bug because it reappeared in jammy. ** Changed in: mutter (Ubuntu) Status: Fix Released => Confirmed ** Tags removed: hirsute ** Tags added: jammy -- 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/1922539 Title: Option "-listen" for file descriptors is deprecated. Please use "-listenfd" instead. Status in mutter package in Ubuntu: Confirmed Bug description: Hi, I see this warning message in the logs: # journalctl | grep -e -listen Apr 02 20:16:24 vougeot org.gnome.Shell.desktop[3329]: (WW) Option "-listen" for file descriptors is deprecated Apr 02 20:16:24 vougeot org.gnome.Shell.desktop[3329]: Please use "-listenfd" instead. Apr 02 20:16:24 vougeot org.gnome.Shell.desktop[3329]: (WW) Option "-listen" for file descriptors is deprecated Apr 02 20:16:24 vougeot org.gnome.Shell.desktop[3329]: Please use "-listenfd" instead. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu1 Uname: Linux 5.11.11-05-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Mon Apr 5 10:07:15 2021 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 3.38.4-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1922539/+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 1968857] [NEW] upgading to jammy leaves obsolete conffiles
Public bug reported:
Hi,
after upgrading my system from impish to jammy, it is left with the
following obsolete conffiles:
$ dpkg-query -W -f='${Conffiles}\n' | grep obsolete
/etc/polkit-1/localauthority.conf.d/51-ubuntu-admin.conf
c4dbd2117c52f367f1e8b8c229686b10 obsolete
/etc/polkit-1/localauthority.conf.d/50-localauthority.conf
2adb9d174807b0a3521fabf03792fbc8 obsolete
/etc/pam.d/polkit-1 7c794427f656539b0d4659b030904fe0 obsolete
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: polkitd 0.105-33
Uname: Linux 5.17.2-051702-generic x86_64
ApportVersion: 2.20.11-0ubuntu81
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Wed Apr 13 10:58:03 2022
SourcePackage: policykit-1
UpgradeStatus: Upgraded to jammy on 2022-04-12 (0 days ago)
modified.conffile..etc.pam.d.polkit-1: [deleted]
modified.conffile..etc.polkit-1.localauthority.conf.d.50-localauthority.conf:
[deleted]
modified.conffile..etc.polkit-1.localauthority.conf.d.51-ubuntu-admin.conf:
[deleted]
** Affects: policykit-1 (Ubuntu)
Importance: Undecided
Status: New
** Affects: policykit-1 (Debian)
Importance: Unknown
Status: Unknown
** Tags: amd64 apport-bug jammy
** Bug watch added: Debian Bug tracker #1006203
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006203
** Also affects: policykit-1 (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006203
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to policykit-1 in Ubuntu.
https://bugs.launchpad.net/bugs/1968857
Title:
upgading to jammy leaves obsolete conffiles
Status in policykit-1 package in Ubuntu:
New
Status in policykit-1 package in Debian:
Unknown
Bug description:
Hi,
after upgrading my system from impish to jammy, it is left with the
following obsolete conffiles:
$ dpkg-query -W -f='${Conffiles}\n' | grep obsolete
/etc/polkit-1/localauthority.conf.d/51-ubuntu-admin.conf
c4dbd2117c52f367f1e8b8c229686b10 obsolete
/etc/polkit-1/localauthority.conf.d/50-localauthority.conf
2adb9d174807b0a3521fabf03792fbc8 obsolete
/etc/pam.d/polkit-1 7c794427f656539b0d4659b030904fe0 obsolete
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: polkitd 0.105-33
Uname: Linux 5.17.2-051702-generic x86_64
ApportVersion: 2.20.11-0ubuntu81
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Wed Apr 13 10:58:03 2022
SourcePackage: policykit-1
UpgradeStatus: Upgraded to jammy on 2022-04-12 (0 days ago)
modified.conffile..etc.pam.d.polkit-1: [deleted]
modified.conffile..etc.polkit-1.localauthority.conf.d.50-localauthority.conf:
[deleted]
modified.conffile..etc.polkit-1.localauthority.conf.d.51-ubuntu-admin.conf:
[deleted]
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1968857/+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 1762133] Re: gvfsd-smb-browse crashed with SIGABRT
** This bug is no longer a duplicate of private bug 1725476 -- 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/1762133 Title: gvfsd-smb-browse crashed with SIGABRT Status in gvfs package in Ubuntu: New Bug description: I was not even using a SMB share when gvfsd-smb-browse crashed. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gvfs-backends 1.36.0-1ubuntu1 Uname: Linux 4.15.15-041515-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: KDE Date: Sat Apr 7 22:06:05 2018 ExecutablePath: /usr/lib/gvfs/gvfsd-smb-browse ProcCmdline: /usr/lib/gvfs/gvfsd-smb-browse --spawner :1.64 /org/gtk/gvfs/exec_spaw/10 Signal: 6 SourcePackage: gvfs StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libtalloc.so.2 _talloc_free () at /usr/lib/x86_64-linux-gnu/libtalloc.so.2 () at /usr/lib/x86_64-linux-gnu/libsmbconf.so.0 gencache_parse () at /usr/lib/x86_64-linux-gnu/libsmbconf.so.0 gencache_get_data_blob () at /usr/lib/x86_64-linux-gnu/libsmbconf.so.0 Title: gvfsd-smb-browse crashed with SIGABRT UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip fuse kvm libvirt libvirtd lpadmin plugdev sambashare staff sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1762133/+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 1940836] Re: Libreoffice Calc rendering very slow on GTK3
Experiencing similar slowdowns running the LibreOffice 7.2.1.2 snap on Ubuntu 20.04.3 -- 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/1940836 Title: Libreoffice Calc rendering very slow on GTK3 Status in libreoffice package in Ubuntu: Confirmed Bug description: I'm on a MATE 20.04 machine, with Nvidia proprietary drivers (for reference, can't use Nouveau, since my machine doesn't boot with it). Libreoffice Calc renders slow. The delay is very noticeable, even when just typing characters. If I remove the GTK3 styling (`libreoffice-gtk3` package), then the rendering speed is fine (but of course, the program is unstyled, with some workflow consequences). I've tried to run on GTK2 (`libreoffice-gtk2` package installed), but I see Calc as unstyled, so it seems it's not actually running on GTK2. I've also tried to disable HW acceleration, but there is no improvement. I don't experience this slowness on any other program on my installation. I've noticed that when there's a delay, the Xorg process CPU occupation skyrockets (depending on how fast I type, it may go even to 100% (single thread)). I've reproduced the same problem on all the LO versions, from the default (6.4.7) to the latest (7.2). The kernel version doesn't affect the problem as well (experienced on different 5.x versions). I've tried a packaged LO (from https://libreoffice.soluzioniopen.com), and it has the same behavior. I'd be perfectly happy to run on GTK2 as workaround, if that allowed persistent copy/paste :) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libreoffice-calc 1:6.4.7-0ubuntu0.20.04.1 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Mon Aug 23 15:21:08 2021 InstallationDate: Installed on 2020-07-01 (418 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1940836/+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 1922420] Re: eog takes a lot of CPU to start
This problem no longer exists in Ubuntu 21.10. ** Changed in: eog (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/1922420 Title: eog takes a lot of CPU to start Status in eog package in Ubuntu: Fix Released Bug description: Hi, eog is very slow to start, more than 3 times slower, compared to other image viewers (eom for instance). Here is a time measurement that demonstrates the problem: $ time eog P1024037.jpg real0m3.824s user0m3.391s sys 0m0.082s $ time eom P1024037.jpg real0m1.025s user0m0.588s sys 0m0.068s Notice how the "user" time, which measures CPU usage, is much higher than in eom. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: eog 40.0-1 Uname: Linux 5.11.11-05-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sat Apr 3 12:33:50 2021 SourcePackage: eog UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1922420/+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 1922414] Re: ssh-agent fails to start (has_option: command not found)
Great, thank you for the fix! -- 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/1922414 Title: ssh-agent fails to start (has_option: command not found) Status in gdm3 package in Ubuntu: Fix Released Status in xorg package in Ubuntu: Invalid Bug description: Hi, I have been using ssh-agent for years and since I upgraded my system to Ubuntu 21.04/groovy, ssh-agent fails to start. Here is the error message: # journalctl | grep ssh-agent [...] Apr 02 20:16:32 vougeot /usr/libexec/gdm-x-session[3752]: /etc/X11/Xsession.d/90x11-common_ssh-agent: line 9: has_option: command not found ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: x11-common 1:7.7+22ubuntu1 Uname: Linux 5.11.11-05-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Sat Apr 3 09:02:46 2021 Dependencies: lsb-base 11.1.0ubuntu2 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: tuxedo-keyboard, 3.0.4, 5.11.0-13-generic, x86_64: installed tuxedo-keyboard, 3.0.4, 5.11.0-13-lowlatency, x86_64: installed tuxedo-keyboard, 3.0.4, 5.11.11-05-lowlatency, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation TigerLake GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Iris Xe Graphics [1558:51a1] MachineType: TUXEDO TUXEDO InfinityBook S 15 Gen6 PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.11-05-lowlatency root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/07/2020 dmi.bios.release: 7.3 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.03RTR dmi.board.name: NS50MU dmi.board.vendor: TUXEDO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.03RTR:bd09/07/2020:br7.3:efr7.2:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50MU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: TUXEDO InfinityBook S 15 Gen6 dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: TUXEDO version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu4 version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.1-1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.10-3ubuntu5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1922414/+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 1936864] Re: Samsung printer can't print after 21.04 update
Hi konrad, Here is my recipe to downgrade. Don't do that unless you know what you do. - go to https://packages.ubuntu.com/groovy/libcups2, scroll down to « Download libcups2 », click on the link corresponding to your architecture, then choose a mirror server, and download the libcups2_2.3.3-3ubuntu1_amd64.deb file. - do the same with https://packages.ubuntu.com/groovy/cups to get cups_2.3.3-3ubuntu1_amd64.deb - open a terminal to get a shell, and go to directory where you stored the two .deb file - type " sudo dpkg -i cups_2.3.3-3ubuntu1_amd64.deb libcups2_2.3.3-3ubuntu1_amd64.deb " to install these packages. - then restart cups with " sudo systemctl restart cups.service " Be aware that further package upgrade ( sudo apt upgrade ) will not work until you issue " sudo apt --fix-broken install " to get back the current cups and libcups2 packages. -- 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/1936864 Title: Samsung printer can't print after 21.04 update Status in cups package in Ubuntu: Confirmed Bug description: Hi, Since 21.04 update, I can't print any document with my Samsung ML-1665 laser printer. When I send a 1 page PDF, the printer warms up, the job appears to be successful, but no document is printed. A few minutes later, the printer prints this message : "INTERNAL ERROR - Incomplete Session by time out POSITION : 0x46069 (286825) SYSTEM : h6fw_5.37/os_hook LINE : 1226 VERSION : SPL 5.37 09-04-2009 " If I send the PDF to the printer twice in a row, the printer prints this message : "INTERNAL ERROR - Incomplete Corrupted Data POSITION : 0x38f72 (20) SYSTEM : h6fw_5.37/xl_image LINE : 154 VERSION : SPL 5.37 09-04-2009 " The problem happens with either Splix or Postscript-Samsung driver. Workaround === downgrade cups and libcups2 to version 2.3.3-3ubuntu1 (from Ubuntu 20.10 Groovy) After these 2 package downgrade, all work as expected. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: cups 2.3.3op2-3ubuntu3 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Jul 19 21:27:14 2021 Lpstat: device for ml1665: usb://Samsung/ML-1660%20Series?serial=Z4ZFBKBZ807421A. device for ml1665-recto-verso: usb://Samsung/ML-1660%20Series?serial=Z4ZFBKBZ807421A. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 413c:2105 Dell Computer Corp. Model L100 Keyboard Bus 001 Device 002: ID 04e8:3301 Samsung Electronics Co., Ltd ML-1660 Series Bus 001 Device 004: ID 3938:1031 MOSART Semi. 2.4G Wireless Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M |__ Port 7: Dev 2, If 0, Class=Printer, Driver=, 12M |__ Port 8: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 10: Dev 4, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: Gigabyte Technology Co., Ltd. B360M H Papersize: a4 PpdFiles: ml1665-recto-verso: Samsung ML-1660, 2.0.0 ml1665: Samsung ML-1660 Series ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-22-generic root=/dev/mapper/vg_acer-lv_root ro SourcePackage: cups UpgradeStatus: Upgraded to hirsute on 2021-06-04 (45 days ago) dmi.bios.date: 03/14/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F12 dmi.board.asset.tag: Default string dmi.board.name: B360M H 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.:bvrF12:bd03/14/2019:br5.13:svnGigabyteTechnologyCo.,Ltd.:pnB360MH:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB360MH:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: B360M H dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. mtime.conffile..etc.cups.cupsd.conf: 2021-06-09T13:29:52.283606 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1936864/+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 1936864] [NEW] Samsung printer can't print after 21.04 update
Public bug reported: Hi, Since 21.04 update, I can't print any document with my Samsung ML-1665 laser printer. When I send a 1 page PDF, the printer warms up, the job appears to be successful, but no document is printed. A few minutes later, the printer prints this message : "INTERNAL ERROR - Incomplete Session by time out POSITION : 0x46069 (286825) SYSTEM : h6fw_5.37/os_hook LINE : 1226 VERSION : SPL 5.37 09-04-2009 " If I send the PDF to the printer twice in a row, the printer prints this message : "INTERNAL ERROR - Incomplete Corrupted Data POSITION : 0x38f72 (20) SYSTEM : h6fw_5.37/xl_image LINE : 154 VERSION : SPL 5.37 09-04-2009 " The problem happens with either Splix or Postscript-Samsung driver. Workaround === downgrade cups and libcups2 to version 2.3.3-3ubuntu1 (from Ubuntu 20.10 Groovy) After these 2 package downgrade, all work as expected. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: cups 2.3.3op2-3ubuntu3 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Jul 19 21:27:14 2021 Lpstat: device for ml1665: usb://Samsung/ML-1660%20Series?serial=Z4ZFBKBZ807421A. device for ml1665-recto-verso: usb://Samsung/ML-1660%20Series?serial=Z4ZFBKBZ807421A. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 413c:2105 Dell Computer Corp. Model L100 Keyboard Bus 001 Device 002: ID 04e8:3301 Samsung Electronics Co., Ltd ML-1660 Series Bus 001 Device 004: ID 3938:1031 MOSART Semi. 2.4G Wireless Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M |__ Port 7: Dev 2, If 0, Class=Printer, Driver=, 12M |__ Port 8: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 10: Dev 4, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: Gigabyte Technology Co., Ltd. B360M H Papersize: a4 PpdFiles: ml1665-recto-verso: Samsung ML-1660, 2.0.0 ml1665: Samsung ML-1660 Series ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-22-generic root=/dev/mapper/vg_acer-lv_root ro SourcePackage: cups UpgradeStatus: Upgraded to hirsute on 2021-06-04 (45 days ago) dmi.bios.date: 03/14/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F12 dmi.board.asset.tag: Default string dmi.board.name: B360M H 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.:bvrF12:bd03/14/2019:br5.13:svnGigabyteTechnologyCo.,Ltd.:pnB360MH:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB360MH:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: B360M H dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. mtime.conffile..etc.cups.cupsd.conf: 2021-06-09T13:29:52.283606 ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute wayland-session -- 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/1936864 Title: Samsung printer can't print after 21.04 update Status in cups package in Ubuntu: New Bug description: Hi, Since 21.04 update, I can't print any document with my Samsung ML-1665 laser printer. When I send a 1 page PDF, the printer warms up, the job appears to be successful, but no document is printed. A few minutes later, the printer prints this message : "INTERNAL ERROR - Incomplete Session by time out POSITION : 0x46069 (286825) SYSTEM : h6fw_5.37/os_hook LINE : 1226 VERSION : SPL 5.37 09-04-2009 " If I send the PDF to the printer twice in a row, the printer prints this message : "INTERNAL ERROR - Incomplete Corrupted Data POSITION : 0x38f72 (20) SYSTEM : h6fw_5.37/xl_image LINE : 154 VERSION : SPL 5.37 09-04-2009 " The problem happens with either Splix or Postscript-Samsung driver. Workaround === downgrade cups and libcups2 to version 2.3.3-3ubuntu1 (from Ubuntu 20.10 Groovy) After these 2 package downgrade, all work as expected. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: cups 2.3.3op2-3ubuntu3 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Jul 19 21:27:14 20
[Desktop-packages] [Bug 1681249] Re: tracker-extract crashed with signal 31 in chdir()
I am closing this bug since it is very old, tracker evolved a lot since then, and tracker no longer crashes on my system. ** Changed in: tracker (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1681249 Title: tracker-extract crashed with signal 31 in chdir() Status in tracker package in Ubuntu: Fix Released Bug description: tracker crash while indexing my homedir ProblemType: Crash DistroRelease: Ubuntu 17.04 Package: tracker-extract 1.12.0-0ubuntu1 Uname: Linux 4.10.8-041008-generic x86_64 ApportVersion: 2.20.4-0ubuntu3 Architecture: amd64 CurrentDesktop: KDE Date: Sat Apr 8 14:00:45 2017 EcryptfsInUse: Yes ExecutablePath: /usr/lib/tracker/tracker-extract ExecutableTimestamp: 1490023113 JournalErrors: No journal files were found. -- No entries -- ProcCmdline: /usr/lib/tracker/tracker-extract ProcCwd: /home/bonnaudl Signal: 31 SourcePackage: tracker Title: tracker-extract crashed with signal 31 in chdir() UpgradeStatus: Upgraded to zesty on 2017-04-08 (0 days ago) UserGroups: adm cdrom dip fuse libvirt libvirtd lpadmin plugdev sambashare staff sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1681249/+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 1075868] Re: New mounting point incompatible with Wine apps
Still an issue in 21.04 -- 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/1075868 Title: New mounting point incompatible with Wine apps Status in gvfs package in Ubuntu: Confirmed Bug description: The new mount point since 12.10 is incompatible with Wine apps. Basically a right click>open with will fail because of invalid characters. Same with File>Open dialogs. Example invalid mount point: /var/run/user/username/gvfs/smb-share:server=192.168.0.1,share=public That is annoying when Office 2010 is needed to open/edit a file that LibreOffice don't render properly (Yes, that happens) ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: gvfs 1.14.0-0ubuntu6 ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7 Uname: Linux 3.5.0-18-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 Date: Wed Nov 7 17:43:00 2012 InstallationDate: Installed on 2012-10-31 (7 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MarkForUpload: True SourcePackage: gvfs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1075868/+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 1922539] Re: Option "-listen" for file descriptors is deprecated. Please use "-listenfd" instead.
Thanks for the fix! -- 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/1922539 Title: Option "-listen" for file descriptors is deprecated. Please use "-listenfd" instead. Status in mutter package in Ubuntu: Fix Released Bug description: Hi, I see this warning message in the logs: # journalctl | grep -e -listen Apr 02 20:16:24 vougeot org.gnome.Shell.desktop[3329]: (WW) Option "-listen" for file descriptors is deprecated Apr 02 20:16:24 vougeot org.gnome.Shell.desktop[3329]: Please use "-listenfd" instead. Apr 02 20:16:24 vougeot org.gnome.Shell.desktop[3329]: (WW) Option "-listen" for file descriptors is deprecated Apr 02 20:16:24 vougeot org.gnome.Shell.desktop[3329]: Please use "-listenfd" instead. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu1 Uname: Linux 5.11.11-05-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Mon Apr 5 10:07:15 2021 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 3.38.4-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1922539/+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 1922539] [NEW] Option "-listen" for file descriptors is deprecated. Please use "-listenfd" instead.
Public bug reported: Hi, I see this warning message in the logs: # journalctl | grep -e -listen Apr 02 20:16:24 vougeot org.gnome.Shell.desktop[3329]: (WW) Option "-listen" for file descriptors is deprecated Apr 02 20:16:24 vougeot org.gnome.Shell.desktop[3329]: Please use "-listenfd" instead. Apr 02 20:16:24 vougeot org.gnome.Shell.desktop[3329]: (WW) Option "-listen" for file descriptors is deprecated Apr 02 20:16:24 vougeot org.gnome.Shell.desktop[3329]: Please use "-listenfd" instead. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu1 Uname: Linux 5.11.11-05-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Mon Apr 5 10:07:15 2021 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 3.38.4-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute -- 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/1922539 Title: Option "-listen" for file descriptors is deprecated. Please use "-listenfd" instead. Status in gnome-shell package in Ubuntu: New Bug description: Hi, I see this warning message in the logs: # journalctl | grep -e -listen Apr 02 20:16:24 vougeot org.gnome.Shell.desktop[3329]: (WW) Option "-listen" for file descriptors is deprecated Apr 02 20:16:24 vougeot org.gnome.Shell.desktop[3329]: Please use "-listenfd" instead. Apr 02 20:16:24 vougeot org.gnome.Shell.desktop[3329]: (WW) Option "-listen" for file descriptors is deprecated Apr 02 20:16:24 vougeot org.gnome.Shell.desktop[3329]: Please use "-listenfd" instead. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu1 Uname: Linux 5.11.11-05-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Mon Apr 5 10:07:15 2021 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 3.38.4-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1922539/+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 1922420] Re: eog takes a lot of CPU to start
The same problem existed in groovy, but not focal. ** Tags added: groovy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/1922420 Title: eog takes a lot of CPU to start Status in eog package in Ubuntu: New Bug description: Hi, eog is very slow to start, more than 3 times slower, compared to other image viewers (eom for instance). Here is a time measurement that demonstrates the problem: $ time eog P1024037.jpg real0m3.824s user0m3.391s sys 0m0.082s $ time eom P1024037.jpg real0m1.025s user0m0.588s sys 0m0.068s Notice how the "user" time, which measures CPU usage, is much higher than in eom. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: eog 40.0-1 Uname: Linux 5.11.11-05-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sat Apr 3 12:33:50 2021 SourcePackage: eog UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1922420/+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 1922420] [NEW] eog takes a lot of CPU to start
Public bug reported: Hi, eog is very slow to start, more than 3 times slower, compared to other image viewers (eom for instance). Here is a time measurement that demonstrates the problem: $ time eog P1024037.jpg real0m3.824s user0m3.391s sys 0m0.082s $ time eom P1024037.jpg real0m1.025s user0m0.588s sys 0m0.068s Notice how the "user" time, which measures CPU usage, is much higher than in eom. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: eog 40.0-1 Uname: Linux 5.11.11-05-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sat Apr 3 12:33:50 2021 SourcePackage: eog UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: eog (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy hirsute -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/1922420 Title: eog takes a lot of CPU to start Status in eog package in Ubuntu: New Bug description: Hi, eog is very slow to start, more than 3 times slower, compared to other image viewers (eom for instance). Here is a time measurement that demonstrates the problem: $ time eog P1024037.jpg real0m3.824s user0m3.391s sys 0m0.082s $ time eom P1024037.jpg real0m1.025s user0m0.588s sys 0m0.068s Notice how the "user" time, which measures CPU usage, is much higher than in eom. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: eog 40.0-1 Uname: Linux 5.11.11-05-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sat Apr 3 12:33:50 2021 SourcePackage: eog UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1922420/+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 1922414] Re: ssh-agent fails to start (has_option: command not found)
The has_option shell function is not defined in the same file: - in Ubuntu groovy it is defined in /etc/X11/Xsession.d/20x11-common_process-args - in Ubuntu hirsute it is defined in /etc/X11/Xsession -- 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/1922414 Title: ssh-agent fails to start (has_option: command not found) Status in xorg package in Ubuntu: New Bug description: Hi, I have been using ssh-agent for years and since I upgraded my system to Ubuntu 21.04/groovy, ssh-agent fails to start. Here is the error message: # journalctl | grep ssh-agent [...] Apr 02 20:16:32 vougeot /usr/libexec/gdm-x-session[3752]: /etc/X11/Xsession.d/90x11-common_ssh-agent: line 9: has_option: command not found ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: x11-common 1:7.7+22ubuntu1 Uname: Linux 5.11.11-05-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Sat Apr 3 09:02:46 2021 Dependencies: lsb-base 11.1.0ubuntu2 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: tuxedo-keyboard, 3.0.4, 5.11.0-13-generic, x86_64: installed tuxedo-keyboard, 3.0.4, 5.11.0-13-lowlatency, x86_64: installed tuxedo-keyboard, 3.0.4, 5.11.11-05-lowlatency, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation TigerLake GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Iris Xe Graphics [1558:51a1] MachineType: TUXEDO TUXEDO InfinityBook S 15 Gen6 PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.11-05-lowlatency root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/07/2020 dmi.bios.release: 7.3 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.03RTR dmi.board.name: NS50MU dmi.board.vendor: TUXEDO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.03RTR:bd09/07/2020:br7.3:efr7.2:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50MU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: TUXEDO InfinityBook S 15 Gen6 dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: TUXEDO version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu4 version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.1-1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.10-3ubuntu5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1922414/+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 1922414] Re: ssh-agent fails to start (has_option: command not found)
The /etc/X11/Xsession.d/90x11-common_ssh-agent file is the same in Ubuntu groovy and hirsute. Therefore, the problem is elsewhere. -- 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/1922414 Title: ssh-agent fails to start (has_option: command not found) Status in xorg package in Ubuntu: New Bug description: Hi, I have been using ssh-agent for years and since I upgraded my system to Ubuntu 21.04/groovy, ssh-agent fails to start. Here is the error message: # journalctl | grep ssh-agent [...] Apr 02 20:16:32 vougeot /usr/libexec/gdm-x-session[3752]: /etc/X11/Xsession.d/90x11-common_ssh-agent: line 9: has_option: command not found ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: x11-common 1:7.7+22ubuntu1 Uname: Linux 5.11.11-05-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Sat Apr 3 09:02:46 2021 Dependencies: lsb-base 11.1.0ubuntu2 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: tuxedo-keyboard, 3.0.4, 5.11.0-13-generic, x86_64: installed tuxedo-keyboard, 3.0.4, 5.11.0-13-lowlatency, x86_64: installed tuxedo-keyboard, 3.0.4, 5.11.11-05-lowlatency, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation TigerLake GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Iris Xe Graphics [1558:51a1] MachineType: TUXEDO TUXEDO InfinityBook S 15 Gen6 PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.11-05-lowlatency root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/07/2020 dmi.bios.release: 7.3 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.03RTR dmi.board.name: NS50MU dmi.board.vendor: TUXEDO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.03RTR:bd09/07/2020:br7.3:efr7.2:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50MU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: TUXEDO InfinityBook S 15 Gen6 dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: TUXEDO version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu4 version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.1-1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.10-3ubuntu5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1922414/+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 1922414] [NEW] ssh-agent fails to start (has_option: command not found)
Public bug reported: Hi, I have been using ssh-agent for years and since I upgraded my system to Ubuntu 21.04/groovy, ssh-agent fails to start. Here is the error message: # journalctl | grep ssh-agent [...] Apr 02 20:16:32 vougeot /usr/libexec/gdm-x-session[3752]: /etc/X11/Xsession.d/90x11-common_ssh-agent: line 9: has_option: command not found ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: x11-common 1:7.7+22ubuntu1 Uname: Linux 5.11.11-05-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Sat Apr 3 09:02:46 2021 Dependencies: lsb-base 11.1.0ubuntu2 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: tuxedo-keyboard, 3.0.4, 5.11.0-13-generic, x86_64: installed tuxedo-keyboard, 3.0.4, 5.11.0-13-lowlatency, x86_64: installed tuxedo-keyboard, 3.0.4, 5.11.11-05-lowlatency, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation TigerLake GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Iris Xe Graphics [1558:51a1] MachineType: TUXEDO TUXEDO InfinityBook S 15 Gen6 PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.11-05-lowlatency root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/07/2020 dmi.bios.release: 7.3 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.03RTR dmi.board.name: NS50MU dmi.board.vendor: TUXEDO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.03RTR:bd09/07/2020:br7.3:efr7.2:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50MU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: TUXEDO InfinityBook S 15 Gen6 dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: TUXEDO version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu4 version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.1-1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.10-3ubuntu5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1922414 Title: ssh-agent fails to start (has_option: command not found) Status in xorg package in Ubuntu: New Bug description: Hi, I have been using ssh-agent for years and since I upgraded my system to Ubuntu 21.04/groovy, ssh-agent fails to start. Here is the error message: # journalctl | grep ssh-agent [...] Apr 02 20:16:32 vougeot /usr/libexec/gdm-x-session[3752]: /etc/X11/Xsession.d/90x11-common_ssh-agent: line 9: has_option: command not found ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: x11-common 1:7.7+22ubuntu1 Uname: Linux 5.11.11-05-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Sat Apr 3 09:02:46 2021 Dependencies: lsb-base 11.1.0ubuntu2 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: tuxedo-keyboard, 3.0.4, 5.11.0-13-generic, x86_64: installed tuxedo-keyboard, 3.0.4, 5.11.0-13-lowlatency, x86_64: installed tuxedo-keyboard, 3.0.4, 5.11.11-05-lowlatency, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation TigerLake GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Iris Xe Graphics [1558:51a1] MachineType: TUXEDO TUXEDO InfinityBook S 15 Gen6 PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.11-05-lowlatency root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh inst
[Desktop-packages] [Bug 1629633] Re: evince displays blank thumbnails for some pages
** Tags removed: gnome3-ppa third-party-packages yakkety ** Tags added: focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1629633 Title: evince displays blank thumbnails for some pages Status in Evince: Unknown Status in evince package in Ubuntu: Triaged Bug description: Hi, To reproduce this bug: - load the attached PS file into evince - if thumbnails are not displayed then press F9 and choose to display thumbnails - evince displayd a blank thumbnail for pages 6 and 7 ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: evince 3.22.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-19.21-lowlatency 4.8.0-rc8 Uname: Linux 4.8.0-19-lowlatency x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: KDE Date: Sun Oct 2 10:10:28 2016 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/1629633/+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 1826639] Re: wpasupplicant: unknown keys in no-mac-addr-change.conf
I installed this package: Package: wpasupplicant Version: 2:2.9-1ubuntu4.1 from focal-proposed and now this command: journalctl | grep cloned-mac-address gives no output. Therefore, the error message is gone. And of course Wi-Fi still works on my WPA2-protected home network. Thanks a lot! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1826639 Title: wpasupplicant: unknown keys in no-mac-addr-change.conf Status in wpa package in Ubuntu: Fix Released Status in wpa source package in Focal: Fix Committed Status in wpa package in Debian: New Bug description: * Impact wpa ships an invalid network-manager configuration that triggers warnings * Test case $ journalctl | grep no-mac-addr-change should not have errors listed * Regression potential the change removes configurations which are not needed (since they set the value to the same one as the default) and in the wrong section, it shouldn't have any visible impact Hi, NetworkManager warns that no-mac-addr-change.conf contains unknown configuration directives: # journalctl | grep no-mac-addr-change Apr 25 09:24:50 vougeot NetworkManager[573]: [1556177090.0596] Read config: /etc/NetworkManager/NetworkManager.conf (lib: 10-dns-resolved.conf, 20-connectivity-ubuntu.conf, no-mac-addr-change.conf) (etc: 10-globally-managed-devices.conf, default-wifi-powersave-on.conf) Apr 25 09:24:50 vougeot NetworkManager[573]: [1556177090.0596] config: unknown key 'wifi.cloned-mac-address' in section [device-mac-addr-change-wifi] of file '/usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf' Apr 25 09:24:50 vougeot NetworkManager[573]: [1556177090.0596] config: unknown key 'ethernet.cloned-mac-address' in section [device-mac-addr-change-wifi] of file '/usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf' ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: wpasupplicant 2:2.6-21ubuntu3 Uname: Linux 5.0.9-050009-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: KDE Date: Sat Apr 27 13:15:27 2019 SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1826639/+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 1826639] Re: wpasupplicant: unknown keys in no-mac-addr-change.conf
** Bug watch added: Debian Bug tracker #951268 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951268 ** Also affects: wpa (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951268 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1826639 Title: wpasupplicant: unknown keys in no-mac-addr-change.conf Status in wpa package in Ubuntu: Fix Committed Status in wpa package in Debian: Unknown Bug description: * Impact wpa ships an invalid network-manager configuration that triggers warnings * Test case $ journalctl | grep no-mac-addr-change should not have errors listed * Regression potential the change removes configurations which are not needed (since they set the value to the same one as the default) and in the wrong section, it shouldn't have any visible impact Hi, NetworkManager warns that no-mac-addr-change.conf contains unknown configuration directives: # journalctl | grep no-mac-addr-change Apr 25 09:24:50 vougeot NetworkManager[573]: [1556177090.0596] Read config: /etc/NetworkManager/NetworkManager.conf (lib: 10-dns-resolved.conf, 20-connectivity-ubuntu.conf, no-mac-addr-change.conf) (etc: 10-globally-managed-devices.conf, default-wifi-powersave-on.conf) Apr 25 09:24:50 vougeot NetworkManager[573]: [1556177090.0596] config: unknown key 'wifi.cloned-mac-address' in section [device-mac-addr-change-wifi] of file '/usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf' Apr 25 09:24:50 vougeot NetworkManager[573]: [1556177090.0596] config: unknown key 'ethernet.cloned-mac-address' in section [device-mac-addr-change-wifi] of file '/usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf' ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: wpasupplicant 2:2.6-21ubuntu3 Uname: Linux 5.0.9-050009-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: KDE Date: Sat Apr 27 13:15:27 2019 SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1826639/+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 1877725] Re: Displays aberrant percentages for disks belonging to btrfs RAID volume
** Also affects: gnome-disk-utility via https://gitlab.gnome.org/GNOME/gnome-disk-utility/-/issues/24 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1877725 Title: Displays aberrant percentages for disks belonging to btrfs RAID volume Status in GNOME Disks: Unknown Status in gnome-disk-utility package in Ubuntu: Triaged Bug description: Hi, when I use gnome-disks to display information about disks that belong to a btrfs RAID volume, I see percentages that are way above 100% (see screenshot below). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-disk-utility 3.36.1-1ubuntu1 Uname: Linux 5.6.11-050611-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sat May 9 11:18:26 2020 SourcePackage: gnome-disk-utility UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-disk-utility/+bug/1877725/+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 1877725] [NEW] Displays aberrant percentages for disks belonging to btrfs RAID volume
Public bug reported: Hi, when I use gnome-disks to display information about disks that belong to a btrfs RAID volume, I see percentages that are way above 100% (see screenshot below). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-disk-utility 3.36.1-1ubuntu1 Uname: Linux 5.6.11-050611-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sat May 9 11:18:26 2020 SourcePackage: gnome-disk-utility UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-disk-utility (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1877725 Title: Displays aberrant percentages for disks belonging to btrfs RAID volume Status in gnome-disk-utility package in Ubuntu: New Bug description: Hi, when I use gnome-disks to display information about disks that belong to a btrfs RAID volume, I see percentages that are way above 100% (see screenshot below). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-disk-utility 3.36.1-1ubuntu1 Uname: Linux 5.6.11-050611-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sat May 9 11:18:26 2020 SourcePackage: gnome-disk-utility UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1877725/+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 1877725] Re: Displays aberrant percentages for disks belonging to btrfs RAID volume
In this example /dev/sde is part of a 5-disks RAID5 volume. ** Attachment added: "screenshot" https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1877725/+attachment/5368860/+files/Screenshot_20200506_125603.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1877725 Title: Displays aberrant percentages for disks belonging to btrfs RAID volume Status in gnome-disk-utility package in Ubuntu: New Bug description: Hi, when I use gnome-disks to display information about disks that belong to a btrfs RAID volume, I see percentages that are way above 100% (see screenshot below). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-disk-utility 3.36.1-1ubuntu1 Uname: Linux 5.6.11-050611-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sat May 9 11:18:26 2020 SourcePackage: gnome-disk-utility UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1877725/+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 1742852] Re: [hostname, Realtek ALC294, Speaker, Internal] No sound at all after windows update
Hi everybody, On my asus, the sound come back after a standby. Good luck Le ven. 1 mai 2020 à 17:30, Filippo Saglimbeni <1742...@bugs.launchpad.net> a écrit : > Hi everyone! > Asus Zenbook UX533FTC has the same problem with Ubuntu 20.04 with Windows > 10 in dual boot. > > 00-00: ALC294 Analog : ALC294 Analog : playback 1 : capture 1 > > uname -r > 5.4.0-26-generic > > No sound at all. It's a good while I'm stuck on this... > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1742852 > > Title: > [hostname, Realtek ALC294, Speaker, Internal] No sound at all after > windows update > > Status in alsa-driver package in Ubuntu: > Confirmed > > Bug description: > After a windows update I lost all the sound on my ubuntu machine. It's > the second time that this happends. > My sound is unmuted and at a loud level and nothing is comming out of my > speakers. > > ProblemType: Bug > DistroRelease: Ubuntu 16.04 > Package: alsa-base 1.0.25+dfsg-0ubuntu5 > ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13 > Uname: Linux 4.13.0-26-generic x86_64 > ApportVersion: 2.20.1-0ubuntu2.15 > Architecture: amd64 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC0: gbergeron 2408 F pulseaudio > gbergeron 3656 F alsamixer > CurrentDesktop: Unity > Date: Thu Jan 11 22:21:23 2018 > InstallationDate: Installed on 2017-11-29 (43 days ago) > InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 > (20170801) > PackageArchitecture: all > SourcePackage: alsa-driver > Symptom: audio > Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed > Symptom_Card: Built-in Audio - HDA Intel PCH > Symptom_DevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/pcmC0D0p: gbergeron 2408 F...m pulseaudio >/dev/snd/controlC0: gbergeron 2408 F pulseaudio > gbergeron 3656 F alsamixer > Symptom_Jack: Speaker, Internal > Symptom_Type: No sound at all > Title: [hostname, Realtek ALC294, Speaker, Internal] No sound at all > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 08/23/2017 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: UX430UAR.203 > dmi.board.asset.tag: ATN12345678901234567 > dmi.board.name: UX430UAR > dmi.board.vendor: ASUSTeK COMPUTER INC. > dmi.board.version: 1.0 > dmi.chassis.asset.tag: No Asset Tag > dmi.chassis.type: 10 > dmi.chassis.vendor: ASUSTeK COMPUTER INC. > dmi.chassis.version: 1.0 > dmi.modalias: > dmi:bvnAmericanMegatrendsInc.:bvrUX430UAR.203:bd08/23/2017:svnASUSTeKCOMPUTERINC.:pnUX430UAR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX430UAR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: > dmi.product.family: UX > dmi.product.name: UX430UAR > dmi.product.version: 1.0 > dmi.sys.vendor: ASUSTeK COMPUTER INC. > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1742852/+subscriptions > -- 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/1742852 Title: [hostname, Realtek ALC294, Speaker, Internal] No sound at all after windows update Status in alsa-driver package in Ubuntu: Confirmed Bug description: After a windows update I lost all the sound on my ubuntu machine. It's the second time that this happends. My sound is unmuted and at a loud level and nothing is comming out of my speakers. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13 Uname: Linux 4.13.0-26-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gbergeron 2408 F pulseaudio gbergeron 3656 F alsamixer CurrentDesktop: Unity Date: Thu Jan 11 22:21:23 2018 InstallationDate: Installed on 2017-11-29 (43 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: gbergeron 2408 F...m pulseaudio /dev/snd/controlC0: gbergeron 2408 F pulseaudio gbergeron 3656 F alsamixer Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [hostname, Realtek ALC294, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/23/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version
[Desktop-packages] [Bug 1847112] Re: gnome-control-center SIGSEGV in cc_display_config_set_minimum_size() when used outside of GNOME
This bug is now fixed in focal. It has been marked as fixed in a duplicate bug report. How about closing this report? -- 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/1847112 Title: gnome-control-center SIGSEGV in cc_display_config_set_minimum_size() when used outside of GNOME Status in gnome-control-center: Unknown Status in gnome-control-center package in Ubuntu: Triaged Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-control-center. This problem was most recently seen with package version 1:3.34.0.1-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/632d9f96d3eb6abd96d55642aa6551a01850331c 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/gnome-control-center/+bug/1847112/+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 1870735] Re: gnome-control-center crashed with SIGSEGV in cc_display_config_set_minimum_size()
*** This bug is a duplicate of bug 1847112 *** https://bugs.launchpad.net/bugs/1847112 Thanks a lot for the fix! -- 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/1870735 Title: gnome-control-center crashed with SIGSEGV in cc_display_config_set_minimum_size() Status in gnome-control-center package in Ubuntu: Fix Released Bug description: I was running gnome-control-center from KDE/plasma and trying all sections. The crash occurred when I tried to enter the "Display" section. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.1-1ubuntu3 Uname: Linux 5.6.2-050602-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: KDE Date: Sat Apr 4 08:57:48 2020 ExecutablePath: /usr/bin/gnome-control-center ProcCmdline: gnome-control-center SegvAnalysis: Segfault happened at: 0x563298319f44 : mov(%rdi),%rax PC (0x563298319f44) ok source "(%rdi)" (0x) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: cc_display_config_set_minimum_size () () () (instance=, signal_id=, detail=) at ../../../gobject/gsignal.c:3554 () Title: gnome-control-center crashed with SIGSEGV in cc_display_config_set_minimum_size() UpgradeStatus: Upgraded to focal on 2020-04-02 (1 days ago) UserGroups: adm cdrom dip fuse kvm libvirt libvirtd lpadmin plugdev sambashare staff sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870735/+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 1870977] Re: Inexistent refresh rate listed
See attached screenshot. -- 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/1870977 Title: Inexistent refresh rate listed Status in gnome-control-center package in Ubuntu: New Bug description: gnome-control-center lists a ~120Hz refresh rate whereas it is not supported by my hardware. According to xrandr the maximal refresh rate is 60Hz: $ xrandr | grep 1920 Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 16384 x 16384 eDP-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 194mm 1920x1080 60.00 + 59.97* 59.9659.9348.00 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.1-1ubuntu3 Uname: Linux 5.6.2-050602-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 5 21:26:12 2020 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-control-center/+bug/1870977/+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 1870977] [NEW] Inexistent refresh rate listed
Public bug reported: gnome-control-center lists a ~120Hz refresh rate whereas it is not supported by my hardware. According to xrandr the maximal refresh rate is 60Hz: $ xrandr | grep 1920 Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 16384 x 16384 eDP-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 194mm 1920x1080 60.00 + 59.97* 59.9659.9348.00 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.1-1ubuntu3 Uname: Linux 5.6.2-050602-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 5 21:26:12 2020 SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "screenshot" https://bugs.launchpad.net/bugs/1870977/+attachment/5347302/+files/Screenshot%20from%202020-04-05%2020-07-33.png -- 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/1870977 Title: Inexistent refresh rate listed Status in gnome-control-center package in Ubuntu: New Bug description: gnome-control-center lists a ~120Hz refresh rate whereas it is not supported by my hardware. According to xrandr the maximal refresh rate is 60Hz: $ xrandr | grep 1920 Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 16384 x 16384 eDP-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 194mm 1920x1080 60.00 + 59.97* 59.9659.9348.00 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.1-1ubuntu3 Uname: Linux 5.6.2-050602-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 5 21:26:12 2020 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-control-center/+bug/1870977/+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 1870735] Re: gnome-control-center crashed with SIGSEGV in cc_display_config_set_minimum_size()
*** This bug is a duplicate of bug 1843699 *** https://bugs.launchpad.net/bugs/1843699 ** Attachment removed: "JournalErrors.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870735/+attachment/5346033/+files/JournalErrors.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/1870735 Title: gnome-control-center crashed with SIGSEGV in cc_display_config_set_minimum_size() Status in gnome-control-center package in Ubuntu: New Bug description: I was running gnome-control-center from KDE/plasma and trying all sections. The crash occurred when I tried to enter the "Display" section. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.1-1ubuntu3 Uname: Linux 5.6.2-050602-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: KDE Date: Sat Apr 4 08:57:48 2020 ExecutablePath: /usr/bin/gnome-control-center ProcCmdline: gnome-control-center SegvAnalysis: Segfault happened at: 0x563298319f44 : mov(%rdi),%rax PC (0x563298319f44) ok source "(%rdi)" (0x) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: cc_display_config_set_minimum_size () () () (instance=, signal_id=, detail=) at ../../../gobject/gsignal.c:3554 () Title: gnome-control-center crashed with SIGSEGV in cc_display_config_set_minimum_size() UpgradeStatus: Upgraded to focal on 2020-04-02 (1 days ago) UserGroups: adm cdrom dip fuse kvm libvirt libvirtd lpadmin plugdev sambashare staff sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870735/+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 1847112] Re: gnome-control-center crashed with SIGSEGV in cc_display_config_set_minimum_size() from reset_current_config() from on_screen_changed() from g_closure_invoke() from
** Tags added: focal -- 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/1847112 Title: gnome-control-center crashed with SIGSEGV in cc_display_config_set_minimum_size() from reset_current_config() from on_screen_changed() from g_closure_invoke() from signal_emit_unlocked_R() Status in gnome-control-center package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-control-center. This problem was most recently seen with package version 1:3.34.0.1-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/632d9f96d3eb6abd96d55642aa6551a01850331c 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-control-center/+bug/1847112/+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 1826639] Re: wpasupplicant: unknown keys in no-mac-addr-change.conf
** Tags added: focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1826639 Title: wpasupplicant: unknown keys in no-mac-addr-change.conf Status in wpa package in Ubuntu: Confirmed Bug description: Hi, NetworkManager warns that no-mac-addr-change.conf contains unknown configuration directives: # journalctl | grep no-mac-addr-change Apr 25 09:24:50 vougeot NetworkManager[573]: [1556177090.0596] Read config: /etc/NetworkManager/NetworkManager.conf (lib: 10-dns-resolved.conf, 20-connectivity-ubuntu.conf, no-mac-addr-change.conf) (etc: 10-globally-managed-devices.conf, default-wifi-powersave-on.conf) Apr 25 09:24:50 vougeot NetworkManager[573]: [1556177090.0596] config: unknown key 'wifi.cloned-mac-address' in section [device-mac-addr-change-wifi] of file '/usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf' Apr 25 09:24:50 vougeot NetworkManager[573]: [1556177090.0596] config: unknown key 'ethernet.cloned-mac-address' in section [device-mac-addr-change-wifi] of file '/usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf' ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: wpasupplicant 2:2.6-21ubuntu3 Uname: Linux 5.0.9-050009-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: KDE Date: Sat Apr 27 13:15:27 2019 SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1826639/+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 1869319] Re: kolla-ansibe debloy vitrage, lack persistor service
Hello Qitao Why is this assigned to libssh? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libssh in Ubuntu. https://bugs.launchpad.net/bugs/1869319 Title: kolla-ansibe debloy vitrage, lack persistor service Status in libssh package in Ubuntu: In Progress Bug description: https://github.com/openstack/kolla- ansible/tree/master/ansible/roles/vitrage/templates ， it only have vitrage-ml ,vitrage-graph ,vitrage-api，vitrage-notifier. No vitrage- persistor is can not store data in DB. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libssh/+bug/1869319/+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 1853574] Re: Syntax error in /usr/bin/chromium-browser when xdg-settings get default-web-browser is empty
The problem is also fixed on my system.
Thanks everybody for the fix!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1853574
Title:
Syntax error in /usr/bin/chromium-browser when xdg-settings get
default-web-browser is empty
Status in chromium-browser package in Ubuntu:
Fix Released
Status in chromium-browser source package in Eoan:
Fix Committed
Bug description:
[Impact]
Minor. Apparently under certain circumstances "xdg-settings get
default-web-browser" can return an empty string (although I haven't been able
to reproduce this myself), and this will make the /usr/bin/chromium-browser
wrapper script spit out a console error (but it won't prevent it from running
the browser).
This is trivial to fix by enclosing the call to "xdg-settings get
default-web-browser" in double quotes, to cater for the empty result case (see
https://bazaar.launchpad.net/~chromium-team/chromium-browser/eoan-stable/revision/1526).
[Test Case]
1. Install chromium-browser
2. Patch /usr/bin/xdg-settings to make the get_browser_gnome3() function
return an empty string (replace its body with 'echo ""')
3. From a terminal, run "chromium-browser"
Expected result: no error
Current result: /usr/bin/chromium-browser: 12: [: =: unexpected operator
[Regression Potential]
Low, enclosing a call to a command in double quotes in bash shouldn't
have any undesirable side effect, and that's all that the patch does.
[Original Description]
Hi,
here is the error:
$ chromium-browser
/usr/bin/chromium-browser: 12: [: =: unexpected operator
[...]
Here is line 12 in /usr/bin/chromium-browser:
if [ $(xdg-settings get default-web-browser) = "chromium-
browser.desktop" ]; then
The error occurs because on my system the default-web-browser setting
is unset:
$ xdg-settings get default-web-browser
[nothing]
I suggest putting double quotes around:
if [ "$(xdg-settings get default-web-browser)" = "chromium-
browser.desktop" ]; then
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: chromium-browser 77.0.3865.120-0ubuntu1.19.10.1
Uname: Linux 5.3.12-050312-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.3
Architecture: amd64
CurrentDesktop: KDE
DRM.card0-DP-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-eDP-1:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAJ5csGAAEaAQSVIhN4CvmglV1ZlCkkUFQBAQEBAQEBAQEBAQEBAQEBGjuAJHE4PEAwIDYAWMIQAAAa/S2ADnE4KEAwIDYAWMIQAAAa/gBSTUpDWYBOVjE1TjQyQSKWABoBCiAgAMg=
modes: 1920x1080 1920x1080
Date: Fri Nov 22 10:27:14 2019
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/mapper/MonVolume2-UbuntuRacine ext4 492G 235G 232G 51% /
tmpfs tmpfs 7.8G 124M 7.7G 2% /dev/shm
/dev/mapper/MonVolume2-UbuntuRacine ext4 492G 235G 232G 51% /
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 0bda:58f6 Realtek Semiconductor Corp.
Integrated_Webcam_HD
Bus 001 Device 002: ID 046d:c03e Logitech, Inc. Premium Optical Wheel Mouse
(M-BT58)
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Latitude 5590
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.12-050312-generic
root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor
intel_iommu=on quiet splash vt.handoff=7
Snap.ChromeDriverVersion: ChromeDriver 78.0.3904.108
(4b26898a39ee037623a72fcfb77279fce0e7d648-refs/branch-heads/3904@{#889})
Snap.ChromiumVersion:
/bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8)
Chromium 78.0.3904.108 snap
SourcePackage: chromium-browser
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/19/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.10.1
dmi.board.name: 0VYDFF
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.10.1:bd07/19/2019:svnDellInc.:pnLatitude5590:pvr:rvnDellInc.:rn0VYDFF:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: Latitude
dmi.product.name: Latitude 5590
dmi.product.sku: 0817
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1853574/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https
[Desktop-packages] [Bug 1847514] Re: libssh-0.8 is detected as 0.7
** Also affects: libssh (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: libssh (Ubuntu Bionic) Status: New => Confirmed ** Changed in: libssh (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libssh in Ubuntu. https://bugs.launchpad.net/bugs/1847514 Title: libssh-0.8 is detected as 0.7 Status in libssh package in Ubuntu: Fix Released Status in libssh source package in Bionic: Confirmed Bug description: QEMU consumes the library and its configure script use the libssh pkg-config cflags. The it checks if ssh_get_server_publickey() is present and assume it is a libssh-0.8 based. Ubuntu libssh is not based on upstream 0.8 but on the 0.7 branch, with commit bbd052202 cherry-picked. This commit adds the ssh_get_server_publickey() function that QEMU uses to check 0.8 compatibility. Now commit 963c46e4f is present in libssh-0.8 but has not been cherry-picked by Ubuntu, so QEMU fails at compiling because the ssh_known_hosts_e enums this commit introduced are missing. QEMU tracker is https://bugs.launchpad.net/qemu/+bug/1838763 How to reproduce: - install libssh-dev - try to build QEMU 4.1 (sources from https://www.qemu.org/download/#source) $ ./configure ... libssh support yes ... $ make ... CC block/ssh.o block/ssh.c: In function 'check_host_key_knownhosts': block/ssh.c:281:28: error: storage size of 'state' isn't known enum ssh_known_hosts_e state; ^ block/ssh.c:289:13: error: implicit declaration of function 'ssh_session_is_known_server' [-Werror=implicit-function-declaration] state = ssh_session_is_known_server(s->session); ^~~ block/ssh.c:289:13: error: nested extern declaration of 'ssh_session_is_known_server' [-Werror=nested-externs] block/ssh.c:293:10: error: 'SSH_KNOWN_HOSTS_OK' undeclared (first use in this function); did you mean 'SSH_OPTIONS_HOSTKEYS'? case SSH_KNOWN_HOSTS_OK: ^~ SSH_OPTIONS_HOSTKEYS block/ssh.c:293:10: note: each undeclared identifier is reported only once for each function it appears in block/ssh.c:297:10: error: 'SSH_KNOWN_HOSTS_CHANGED' undeclared (first use in this function); did you mean 'SSH_KNOWN_HOSTS_OK'? case SSH_KNOWN_HOSTS_CHANGED: ^~~ SSH_KNOWN_HOSTS_OK block/ssh.c:301:48: error: 'SSH_PUBLICKEY_HASH_SHA256' undeclared (first use in this function); did you mean 'SSH_PUBLICKEY_HASH_SHA1'? r = ssh_get_publickey_hash(pubkey, SSH_PUBLICKEY_HASH_SHA256, ^ SSH_PUBLICKEY_HASH_SHA1 block/ssh.c:307:27: error: implicit declaration of function 'ssh_get_fingerprint_hash'; did you mean 'ssh_get_pubkey_hash'? [-Werror=implicit-function-declaration] fingerprint = ssh_get_fingerprint_hash(SSH_PUBLICKEY_HASH_SHA256, ^~~~ ssh_get_pubkey_hash block/ssh.c:307:27: error: nested extern declaration of 'ssh_get_fingerprint_hash' [-Werror=nested-externs] block/ssh.c:324:10: error: 'SSH_KNOWN_HOSTS_OTHER' undeclared (first use in this function); did you mean 'SSH_KNOWN_HOSTS_OK'? case SSH_KNOWN_HOSTS_OTHER: ^ SSH_KNOWN_HOSTS_OK block/ssh.c:329:10: error: 'SSH_KNOWN_HOSTS_UNKNOWN' undeclared (first use in this function); did you mean 'SSH_KNOWN_HOSTS_CHANGED'? case SSH_KNOWN_HOSTS_UNKNOWN: ^~~ SSH_KNOWN_HOSTS_CHANGED block/ssh.c:333:10: error: 'SSH_KNOWN_HOSTS_NOT_FOUND' undeclared (first use in this function); did you mean 'SSH_KNOWN_HOSTS_UNKNOWN'? case SSH_KNOWN_HOSTS_NOT_FOUND: ^ SSH_KNOWN_HOSTS_UNKNOWN block/ssh.c:337:10: error: 'SSH_KNOWN_HOSTS_ERROR' undeclared (first use in this function); did you mean 'SSH_KNOWN_HOSTS_OTHER'? case SSH_KNOWN_HOSTS_ERROR: ^ SSH_KNOWN_HOSTS_OTHER block/ssh.c:281:28: error: unused variable 'state' [-Werror=unused-variable] enum ssh_known_hosts_e state; ^ cc1: all warnings being treated as errors rules.mak:69: recipe for target 'block/ssh.o' failed make: *** [block/ssh.o] Error 1 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libssh-dev 0.8.0~20170825.94fa1e38-1ubuntu0.2 Uname: Linux 5.2.17-200.fc30.x86_64 x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 Date: Wed Oct 9 18:21:25 2019 ProcEnviron: TERM=xterm PATH=(custom, no user) SourcePackage: libssh UpgradeStatus: No upgrade log present (probably fresh install) To ma
[Desktop-packages] [Bug 1846944] Re: Nextcloud client app indicator icon not visible in 19.10 Eoan Beta
Not only Enpass is affected. Try killall nextcloud and restart It seems to affect app with indicators that are autostarted -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1846944 Title: Nextcloud client app indicator icon not visible in 19.10 Eoan Beta Status in gnome-shell-extension-appindicator package in Ubuntu: Confirmed Bug description: When running the Nextcloud Client (flatpak or PPA) in Eoan Beta, its app indicator icon is never displayed in the notification area. Other apps sch as Steam and Skype have their indicator icons displayed fine. Output from the command line when running the flatpak produces the following error: Qt: Session management error: None of the authentication protocols specified are supported I can duplicate this issue 100% of the time. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell-extension-appindicator 30-1 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Oct 6 13:35:44 2019 InstallationDate: Installed on 2019-09-23 (12 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all SourcePackage: gnome-shell-extension-appindicator UpgradeStatus: Upgraded to eoan on 2019-09-27 (8 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1846944/+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 1853574] Re: Syntax error in /usr/bin/chromium-browser when xdg-settings get default-web-browser is empty
Thank you for the quick fix!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1853574
Title:
Syntax error in /usr/bin/chromium-browser when xdg-settings get
default-web-browser is empty
Status in chromium-browser package in Ubuntu:
Fix Released
Bug description:
Hi,
here is the error:
$ chromium-browser
/usr/bin/chromium-browser: 12: [: =: unexpected operator
[...]
Here is line 12 in /usr/bin/chromium-browser:
if [ $(xdg-settings get default-web-browser) = "chromium-
browser.desktop" ]; then
The error occurs because on my system the default-web-browser setting
is unset:
$ xdg-settings get default-web-browser
[nothing]
I suggest putting double quotes around:
if [ "$(xdg-settings get default-web-browser)" = "chromium-
browser.desktop" ]; then
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: chromium-browser 77.0.3865.120-0ubuntu1.19.10.1
Uname: Linux 5.3.12-050312-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.3
Architecture: amd64
CurrentDesktop: KDE
DRM.card0-DP-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-eDP-1:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAJ5csGAAEaAQSVIhN4CvmglV1ZlCkkUFQBAQEBAQEBAQEBAQEBAQEBGjuAJHE4PEAwIDYAWMIQAAAa/S2ADnE4KEAwIDYAWMIQAAAa/gBSTUpDWYBOVjE1TjQyQSKWABoBCiAgAMg=
modes: 1920x1080 1920x1080
Date: Fri Nov 22 10:27:14 2019
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/mapper/MonVolume2-UbuntuRacine ext4 492G 235G 232G 51% /
tmpfs tmpfs 7.8G 124M 7.7G 2% /dev/shm
/dev/mapper/MonVolume2-UbuntuRacine ext4 492G 235G 232G 51% /
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 0bda:58f6 Realtek Semiconductor Corp.
Integrated_Webcam_HD
Bus 001 Device 002: ID 046d:c03e Logitech, Inc. Premium Optical Wheel Mouse
(M-BT58)
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Latitude 5590
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.12-050312-generic
root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor
intel_iommu=on quiet splash vt.handoff=7
Snap.ChromeDriverVersion: ChromeDriver 78.0.3904.108
(4b26898a39ee037623a72fcfb77279fce0e7d648-refs/branch-heads/3904@{#889})
Snap.ChromiumVersion:
/bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8)
Chromium 78.0.3904.108 snap
SourcePackage: chromium-browser
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/19/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.10.1
dmi.board.name: 0VYDFF
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.10.1:bd07/19/2019:svnDellInc.:pnLatitude5590:pvr:rvnDellInc.:rn0VYDFF:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: Latitude
dmi.product.name: Latitude 5590
dmi.product.sku: 0817
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1853574/+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 1853574] [NEW] Syntax eror in /usr/bin/chromium-browser when xdg-settings get default-web-browser is empty
Public bug reported:
Hi,
here is the error:
$ chromium-browser
/usr/bin/chromium-browser: 12: [: =: unexpected operator
[...]
Here is line 12 in /usr/bin/chromium-browser:
if [ $(xdg-settings get default-web-browser) = "chromium-
browser.desktop" ]; then
The error occurs because on my system the default-web-browser setting is
unset:
$ xdg-settings get default-web-browser
[nothing]
I suggest putting double quotes around:
if [ "$(xdg-settings get default-web-browser)" = "chromium-
browser.desktop" ]; then
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: chromium-browser 77.0.3865.120-0ubuntu1.19.10.1
Uname: Linux 5.3.12-050312-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.3
Architecture: amd64
CurrentDesktop: KDE
DRM.card0-DP-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-eDP-1:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAJ5csGAAEaAQSVIhN4CvmglV1ZlCkkUFQBAQEBAQEBAQEBAQEBAQEBGjuAJHE4PEAwIDYAWMIQAAAa/S2ADnE4KEAwIDYAWMIQAAAa/gBSTUpDWYBOVjE1TjQyQSKWABoBCiAgAMg=
modes: 1920x1080 1920x1080
Date: Fri Nov 22 10:27:14 2019
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/mapper/MonVolume2-UbuntuRacine ext4 492G 235G 232G 51% /
tmpfs tmpfs 7.8G 124M 7.7G 2% /dev/shm
/dev/mapper/MonVolume2-UbuntuRacine ext4 492G 235G 232G 51% /
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 0bda:58f6 Realtek Semiconductor Corp.
Integrated_Webcam_HD
Bus 001 Device 002: ID 046d:c03e Logitech, Inc. Premium Optical Wheel Mouse
(M-BT58)
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Latitude 5590
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.12-050312-generic
root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor
intel_iommu=on quiet splash vt.handoff=7
Snap.ChromeDriverVersion: ChromeDriver 78.0.3904.108
(4b26898a39ee037623a72fcfb77279fce0e7d648-refs/branch-heads/3904@{#889})
Snap.ChromiumVersion:
/bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8)
Chromium 78.0.3904.108 snap
SourcePackage: chromium-browser
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/19/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.10.1
dmi.board.name: 0VYDFF
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.10.1:bd07/19/2019:svnDellInc.:pnLatitude5590:pvr:rvnDellInc.:rn0VYDFF:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: Latitude
dmi.product.name: Latitude 5590
dmi.product.sku: 0817
dmi.sys.vendor: Dell Inc.
** Affects: chromium-browser (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug eoan snap
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1853574
Title:
Syntax eror in /usr/bin/chromium-browser when xdg-settings get
default-web-browser is empty
Status in chromium-browser package in Ubuntu:
New
Bug description:
Hi,
here is the error:
$ chromium-browser
/usr/bin/chromium-browser: 12: [: =: unexpected operator
[...]
Here is line 12 in /usr/bin/chromium-browser:
if [ $(xdg-settings get default-web-browser) = "chromium-
browser.desktop" ]; then
The error occurs because on my system the default-web-browser setting
is unset:
$ xdg-settings get default-web-browser
[nothing]
I suggest putting double quotes around:
if [ "$(xdg-settings get default-web-browser)" = "chromium-
browser.desktop" ]; then
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: chromium-browser 77.0.3865.120-0ubuntu1.19.10.1
Uname: Linux 5.3.12-050312-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.3
Architecture: amd64
CurrentDesktop: KDE
DRM.card0-DP-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-eDP-1:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAJ5csGAAEaAQSVIhN4CvmglV1ZlCkkUFQBAQEBAQEBAQEBAQEBAQEBGjuAJHE4PEAwIDYAWMIQAAAa/S2ADnE4KEAwIDYAWMIQAAAa/gBSTUpDWYBOVjE1TjQyQSKWABoBCiAgAMg=
modes: 1920x1080 1920x1080
Date: Fri Nov 22 10:27:14 2019
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/mapper/MonVolume2-UbuntuRacine ext4 492G 235G 232G 51% /
tmp
[Desktop-packages] [Bug 1799675] Re: /usr/bin/gnome-control-center:ERROR:../shell/cc-shell-model.c:458:cc_shell_model_set_panel_visibility: assertion failed: (valid)
** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/issues #248 https://gitlab.gnome.org/GNOME/gnome-control-center/issues/248 ** Also affects: gnome-control-center via https://gitlab.gnome.org/GNOME/gnome-control-center/issues/248 Importance: Unknown Status: Unknown ** Bug watch added: Red Hat Bugzilla #1665639 https://bugzilla.redhat.com/show_bug.cgi?id=1665639 ** Also affects: gnome-control-center (Fedora) via https://bugzilla.redhat.com/show_bug.cgi?id=1665639 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/1799675 Title: /usr/bin/gnome-control-center:ERROR:../shell/cc-shell- model.c:458:cc_shell_model_set_panel_visibility: assertion failed: (valid) Status in gnome-control-center: Unknown Status in gnome-control-center package in Ubuntu: Triaged Status in gnome-control-center package in Fedora: Unknown Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-control-center. This problem was most recently seen with package version 1:3.30.1-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/8de5ebcde9e4492a3bc570a4caa376cefbdfcbec 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/gnome-control-center/+bug/1799675/+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 1847491] Re: gnome-control-center assert failure: ERROR:../shell/cc-shell-model.c:458:cc_shell_model_set_panel_visibility: assertion failed: (valid)
*** This bug is a duplicate of bug 1799675 *** https://bugs.launchpad.net/bugs/1799675 ** Attachment removed: "JournalErrors.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1847491/+attachment/5295962/+files/JournalErrors.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/1847491 Title: gnome-control-center assert failure: ERROR:../shell/cc-shell- model.c:458:cc_shell_model_set_panel_visibility: assertion failed: (valid) Status in gnome-control-center package in Ubuntu: New Bug description: When I try to use gnome-control-center under Plasma, it crashes. Steps to reproduce: 1. start a Plasma session 2. start gnome-control-center ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: gnome-control-center 1:3.34.1-1ubuntu1 Uname: Linux 5.3.5-050305-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AssertionMessage: ERROR:../shell/cc-shell-model.c:458:cc_shell_model_set_panel_visibility: assertion failed: (valid) CurrentDesktop: KDE Date: Wed Oct 9 10:46:52 2019 ExecutablePath: /usr/bin/gnome-control-center ExecutableTimestamp: 1570461969 ProcCmdline: gnome-control-center ProcCwd: /home/bonnaudl Signal: 6 SourcePackage: gnome-control-center StacktraceTop: g_assertion_message (domain=, file=, line=, func=0x5612db26af40 "cc_shell_model_set_panel_visibility", message=) at ../../../glib/gtestutils.c:2912 g_assertion_message_expr (domain=0x0, file=0x5612db26aeff "../shell/cc-shell-model.c", line=458, func=0x5612db26af40 "cc_shell_model_set_panel_visibility", expr=) at ../../../glib/gtestutils.c:2938 cc_shell_model_set_panel_visibility () () cc_wifi_panel_static_init_func () Title: gnome-control-center assert failure: ERROR:../shell/cc-shell-model.c:458:cc_shell_model_set_panel_visibility: assertion failed: (valid) UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip fuse kvm libvirt libvirt-qemu libvirtd lpadmin plugdev sambashare staff sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1847491/+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 1847491] [NEW] gnome-control-center assert failure: ERROR:../shell/cc-shell-model.c:458:cc_shell_model_set_panel_visibility: assertion failed: (valid)
Public bug reported: When I try to use gnome-control-center under Plasma, it crashes. Steps to reproduce: 1. start a Plasma session 2. start gnome-control-center ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: gnome-control-center 1:3.34.1-1ubuntu1 Uname: Linux 5.3.5-050305-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AssertionMessage: ERROR:../shell/cc-shell-model.c:458:cc_shell_model_set_panel_visibility: assertion failed: (valid) CurrentDesktop: KDE Date: Wed Oct 9 10:46:52 2019 ExecutablePath: /usr/bin/gnome-control-center ExecutableTimestamp: 1570461969 ProcCmdline: gnome-control-center ProcCwd: /home/bonnaudl Signal: 6 SourcePackage: gnome-control-center StacktraceTop: g_assertion_message (domain=, file=, line=, func=0x5612db26af40 "cc_shell_model_set_panel_visibility", message=) at ../../../glib/gtestutils.c:2912 g_assertion_message_expr (domain=0x0, file=0x5612db26aeff "../shell/cc-shell-model.c", line=458, func=0x5612db26af40 "cc_shell_model_set_panel_visibility", expr=) at ../../../glib/gtestutils.c:2938 cc_shell_model_set_panel_visibility () () cc_wifi_panel_static_init_func () Title: gnome-control-center assert failure: ERROR:../shell/cc-shell-model.c:458:cc_shell_model_set_panel_visibility: assertion failed: (valid) UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip fuse kvm libvirt libvirt-qemu libvirtd lpadmin plugdev sambashare staff sudo separator: ** Affects: gnome-control-center (Ubuntu) Importance: Medium Status: New ** Tags: amd64 apport-crash eoan ** Information type changed from Private to Public -- 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/1847491 Title: gnome-control-center assert failure: ERROR:../shell/cc-shell- model.c:458:cc_shell_model_set_panel_visibility: assertion failed: (valid) Status in gnome-control-center package in Ubuntu: New Bug description: When I try to use gnome-control-center under Plasma, it crashes. Steps to reproduce: 1. start a Plasma session 2. start gnome-control-center ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: gnome-control-center 1:3.34.1-1ubuntu1 Uname: Linux 5.3.5-050305-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AssertionMessage: ERROR:../shell/cc-shell-model.c:458:cc_shell_model_set_panel_visibility: assertion failed: (valid) CurrentDesktop: KDE Date: Wed Oct 9 10:46:52 2019 ExecutablePath: /usr/bin/gnome-control-center ExecutableTimestamp: 1570461969 ProcCmdline: gnome-control-center ProcCwd: /home/bonnaudl Signal: 6 SourcePackage: gnome-control-center StacktraceTop: g_assertion_message (domain=, file=, line=, func=0x5612db26af40 "cc_shell_model_set_panel_visibility", message=) at ../../../glib/gtestutils.c:2912 g_assertion_message_expr (domain=0x0, file=0x5612db26aeff "../shell/cc-shell-model.c", line=458, func=0x5612db26af40 "cc_shell_model_set_panel_visibility", expr=) at ../../../glib/gtestutils.c:2938 cc_shell_model_set_panel_visibility () () cc_wifi_panel_static_init_func () Title: gnome-control-center assert failure: ERROR:../shell/cc-shell-model.c:458:cc_shell_model_set_panel_visibility: assertion failed: (valid) UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip fuse kvm libvirt libvirt-qemu libvirtd lpadmin plugdev sambashare staff sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1847491/+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 1826639] Re: wpasupplicant: unknown keys in no-mac-addr-change.conf
** Tags added: eoan -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1826639 Title: wpasupplicant: unknown keys in no-mac-addr-change.conf Status in wpa package in Ubuntu: Confirmed Bug description: Hi, NetworkManager warns that no-mac-addr-change.conf contains unknown configuration directives: # journalctl | grep no-mac-addr-change Apr 25 09:24:50 vougeot NetworkManager[573]: [1556177090.0596] Read config: /etc/NetworkManager/NetworkManager.conf (lib: 10-dns-resolved.conf, 20-connectivity-ubuntu.conf, no-mac-addr-change.conf) (etc: 10-globally-managed-devices.conf, default-wifi-powersave-on.conf) Apr 25 09:24:50 vougeot NetworkManager[573]: [1556177090.0596] config: unknown key 'wifi.cloned-mac-address' in section [device-mac-addr-change-wifi] of file '/usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf' Apr 25 09:24:50 vougeot NetworkManager[573]: [1556177090.0596] config: unknown key 'ethernet.cloned-mac-address' in section [device-mac-addr-change-wifi] of file '/usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf' ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: wpasupplicant 2:2.6-21ubuntu3 Uname: Linux 5.0.9-050009-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: KDE Date: Sat Apr 27 13:15:27 2019 SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1826639/+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 34813] Re: gedit fails to save files over smbfs/cifs
On Ubuntu 19.10 it fails saying "Cannot handle “file:” locations in write mode. Please check that you typed the location correctly and try again." -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/34813 Title: gedit fails to save files over smbfs/cifs Status in gedit: Expired Status in Samba Server: Invalid Status in SSHFS Mounter: Confirmed Status in gedit package in Ubuntu: Triaged Status in gedit package in CentOS: New Bug description: Saving files over a cifs/smbfs server doesnt work. You can open file, edit then save perfectly. But repeated saves after give you this error: "The file /home/dhonn/website/arrays.php has been modified since reading it. If you save it, all the external changes could be lost. Save it anyway?" The think is lying to me because I havent made any external changes. When I click "Save Anyway", i get this error: "Could not save the file /home/dhonn/website/arrays.php." But on the third try it works just fine. Here are the error messages, btw there are also GUI glitches too: http://dhonn.com/images/gedit-0.jpg http://dhonn.com/images/gedit-1.jpg To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/34813/+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 1725779] Re: Gnome network manager cannot find authentication binary
Just for a sanity check, I rebooted and I can now connect without passing by the nm-applet... Not sure why but it's worth a test for anyone who had the same issue. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-pptp in Ubuntu. https://bugs.launchpad.net/bugs/1725779 Title: Gnome network manager cannot find authentication binary Status in network-manager-pptp package in Ubuntu: Confirmed Status in network-manager-ssh package in Ubuntu: Confirmed Status in network-manager-vpnc package in Ubuntu: Confirmed Bug description: From logs: Oct 21 13:54:03 V NetworkManager[5935]: [1508608443.7424] audit: op="connection-activate" uuid="71868b90-3a57-4fee-9933-bf7c9b22d44d" name="Library" pid=2510 uid=1000 result="success" Oct 21 13:54:03 V NetworkManager[5935]: [1508608443.7473] vpn-connection[0x55e8f7b612f0,71868b90-3a57-4fee-9933-bf7c9b22d44d,"Library",0]: Started the VPN service, PID 6934 Oct 21 13:54:03 V NetworkManager[5935]: [1508608443.7518] vpn-connection[0x55e8f7b612f0,71868b90-3a57-4fee-9933-bf7c9b22d44d,"Library",0]: Saw the service appear; activating connection Oct 21 13:54:03 V gnome-shell[2510]: Invalid VPN service type (cannot find authentication binary) Oct 21 13:54:03 V gnome-shell[2510]: Invalid VPN service type (cannot find authentication binary) Oct 21 13:54:03 V NetworkManager[5935]: [1508608443.7698] vpn-connection[0x55e8f7b612f0,71868b90-3a57-4fee-9933-bf7c9b22d44d,"Library",0]: Failed to request VPN secrets #3: No agents were available for t his request. Oct 21 13:54:03 V NetworkManager[5935]: [1508608443.7708] vpn-connection[0x55e8f7b612f0,71868b90-3a57-4fee-9933-bf7c9b22d44d,"Library",0]: VPN plugin: state changed: stopped (6) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: network-manager-pptp-gnome 1.2.4-4 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Oct 21 14:07:06 2017 InstallationDate: Installed on 2017-10-20 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager-pptp UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-pptp/+bug/1725779/+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
