[Desktop-packages] [Bug 1988658] [NEW] boot stops at black screen (blinking cursor in top left corner); pulseaudio fails to intialize?
Public bug reported: $ cat /etc/os-release NAME="Ubuntu" VERSION="20.04.5 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.5 LTS" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; VERSION_CODENAME=focal UBUNTU_CODENAME=focal 3 to 5 of 10 boot occasions stops prematurely. dmesg (included here, I assume) indicates a pulseaudio failure stopping the booting. I have NOT investigated further (knowledge limit). This very latest bootup seemed to indicate that there is something waiting on the keyboard, as I got all the way "up" after beating repeatedly - alternating - on ESC and ENTER --- dmesg tail on this boot --- 4 sec pause from previous line (at 9 secs) [ 13.444028] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, Reinit [ 13.444031] usb usb3: root hub lost power or was reset [ 13.444032] usb usb4: root hub lost power or was reset [ 13.557170] Lockdown: Xorg: raw io port access is restricted; see man kernel_lockdown.7 [ 13.791732] ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20210331/nsarguments-61) [ 17.001076] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [ 17.105681] rfkill: input handler disabled [ 28.694324] Bluetooth: RFCOMM TTY layer initialized [ 28.694328] Bluetooth: RFCOMM socket layer initialized [ 28.694331] Bluetooth: RFCOMM ver 1.11 [ 28.922797] rfkill: input handler enabled [ 29.043050] Lockdown: Xorg: raw io port access is restricted; see man kernel_lockdown.7 [ 31.669031] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [ 31.907300] rfkill: input handler disabled [ 41.959736] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [ 78.940836] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, Reinit [ 78.940840] usb usb3: root hub lost power or was reset [ 78.940841] usb usb4: root hub lost power or was reset [ 929.174665] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, Reinit [ 929.174669] usb usb3: root hub lost power or was reset [ 929.174671] usb usb4: root hub lost power or was reset -- end --- ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.13 ProcVersionSignature: Ubuntu 5.13.0-52.59~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D10p', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Date: Sun Sep 4 08:19:01 2022 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/19/2021 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: G731GU.312 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G731GU dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 0.6 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrG731GU.312:bd02/19/2021:br5.13:efr0.6:svnASUSTeKCOMPUTERINC.:pnROGStrixG731GU_G731GU:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG731GU:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ROG Strix dmi.product.name: ROG Strix G731GU_G731GU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1988658 Title: boot stops at black screen (blinking cursor in top left corner); pulseaudio fails to intialize? Status in pulseaudio package in Ubuntu: New Bug description: $ cat /etc/os-release NAME="Ubuntu" VERSION="20.04.5 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.5 LTS" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; VERSION_CODENAME=focal UBUNTU_CODENAME=foc
[Desktop-packages] [Bug 1824498] Re: Unable to connect to wifi since wpasupplicant_2.4-0ubuntu6.4_amd64.deb update
[Expired for wpa (Ubuntu) because there has been no activity for 60 days.] ** Changed in: wpa (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1824498 Title: Unable to connect to wifi since wpasupplicant_2.4-0ubuntu6.4_amd64.deb update Status in wpa package in Ubuntu: Expired Bug description: I'm unable to connect to internet through wifi since this morning, since wpasupplicant_2.4-0ubuntu6.4_amd64.deb was updated on my machine this morning at 3 am and I didn't have trouble ever before I strongly suspect this update to have caused the problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1824498/+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 1973441] Re: Printing does not work on Ubuntu 22.04 - cups-pki-invalid
This worked for me as well with an HP OfficeJet Pro 9025. -- 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/1973441 Title: Printing does not work on Ubuntu 22.04 - cups-pki-invalid Status in cups package in Ubuntu: Confirmed Bug description: After upgrading to 22.04 printing did not work. There is cups-pki- invalid error and printer goes to paused state. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cups 2.4.1op1-1ubuntu4 Uname: Linux 5.17.7-051707-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CupsErrorLog: Error: [Errno 13] Permission denied: '/var/log/cups/error_log' CurrentDesktop: ubuntu:GNOME Date: Sun May 15 15:34:47 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2021-10-12 (214 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Daily amd64 (20211010) Lpstat: device for HP_Color_LaserJet_M552_5F80BF: implicitclass://HP_Color_LaserJet_M552_5F80BF/ MachineType: ASUSTeK COMPUTER INC. ROG Strix G513QY_G513QY Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP_Color_LaserJet_M552_5F80BF.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP_Color_LaserJet_M552_5F80BF.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.17.7-051707-generic root=UUID=ff964c9b-ce92-4334-8759-9d785a262c60 ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to jammy on 2022-04-24 (21 days ago) dmi.bios.date: 03/29/2022 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: G513QY.318 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G513QY dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 0.81 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrG513QY.318:bd03/29/2022:br5.19:efr0.81:svnASUSTeKCOMPUTERINC.:pnROGStrixG513QY_G513QY:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG513QY:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ROG Strix dmi.product.name: ROG Strix G513QY_G513QY dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1973441/+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]
This morning I forgot to launch Firefox with the command line, I mean I launched Firefox by clicking the icon and it worked! I rebooted to try again but unfortunately it didn't work the second time. -- 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 1988230] Re: glib 2.73 breaks modemmanager
** Changed in: glib Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1988230 Title: glib 2.73 breaks modemmanager Status in GLib: Fix Released Status in glib2.0 package in Ubuntu: Triaged Status in modemmanager package in Ubuntu: Triaged 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 1988648] gnome-software crashed with SIGABRT when clicking on the firefox snap
StacktraceTop: g_assertion_message (domain=, file=, line=, func=0x7f5f8337bdf0 <__func__.0.lto_priv.50> "g_format_size_full", message=) at ../../../glib/gtestutils.c:3253 g_assertion_message_expr (domain=0x7f5f83317071 "GLib", file=0x7f5f8337a285 "../../../glib/gutils.c", line=2925, func=0x7f5f8337bdf0 <__func__.0.lto_priv.50> "g_format_size_full", expr=) at ../../../glib/gtestutils.c:3279 g_format_size_full (size=size@entry=507904, flags=flags@entry=(unknown: 0x8)) at ../../../glib/gutils.c:2925 gs_utils_format_size (size_bytes=507904, out_is_markup=0x7ffd2b32e43c) at ../src/gs-common.c:1245 update_storage_tile (self=self@entry=0x5593e767c9b0) at ../src/gs-app-context-bar.c:214 ** Tags removed: need-amd64-retrace -- 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/1988648 Title: gnome-software crashed with SIGABRT when clicking on the firefox snap Status in gnome-software package in Ubuntu: New Bug description: Clicking on the Install tab followed by the Firefox snap to display more info, gnome-software immediately crashes without displaying more info. Clicking on an installed deb package like gnome-calculator sometimes the more info is displayed - sometimes it is briefly displayed before crashing again. ProblemType: Crash DistroRelease: Ubuntu 22.10 Package: gnome-software 43~rc-2 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: Budgie:GNOME Date: Sat Sep 3 21:04:41 2022 ExecutablePath: /usr/bin/gnome-software InstallationDate: Installed on 2022-07-27 (38 days ago) InstallationMedia: Ubuntu-Budgie 22.10 "Kinetic Kudu" - Alpha amd64 (20220726) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snap43~rc-2 JournalErrors: -- No entries -- ProcCmdline: gnome-software Signal: 6 SourcePackage: gnome-software StacktraceTop: () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 gs_utils_format_size () () Title: gnome-software crashed with SIGABRT UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sbuild sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1988648/+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 1988648] [NEW] gnome-software crashed with SIGABRT when clicking on the firefox snap
Public bug reported: Clicking on the Install tab followed by the Firefox snap to display more info, gnome-software immediately crashes without displaying more info. Clicking on an installed deb package like gnome-calculator sometimes the more info is displayed - sometimes it is briefly displayed before crashing again. ProblemType: Crash DistroRelease: Ubuntu 22.10 Package: gnome-software 43~rc-2 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: Budgie:GNOME Date: Sat Sep 3 21:04:41 2022 ExecutablePath: /usr/bin/gnome-software InstallationDate: Installed on 2022-07-27 (38 days ago) InstallationMedia: Ubuntu-Budgie 22.10 "Kinetic Kudu" - Alpha amd64 (20220726) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snap43~rc-2 JournalErrors: -- No entries -- ProcCmdline: gnome-software Signal: 6 SourcePackage: gnome-software StacktraceTop: () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 gs_utils_format_size () () Title: gnome-software crashed with SIGABRT UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sbuild sudo separator: ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash kinetic third-party-packages -- 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/1988648 Title: gnome-software crashed with SIGABRT when clicking on the firefox snap Status in gnome-software package in Ubuntu: New Bug description: Clicking on the Install tab followed by the Firefox snap to display more info, gnome-software immediately crashes without displaying more info. Clicking on an installed deb package like gnome-calculator sometimes the more info is displayed - sometimes it is briefly displayed before crashing again. ProblemType: Crash DistroRelease: Ubuntu 22.10 Package: gnome-software 43~rc-2 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: Budgie:GNOME Date: Sat Sep 3 21:04:41 2022 ExecutablePath: /usr/bin/gnome-software InstallationDate: Installed on 2022-07-27 (38 days ago) InstallationMedia: Ubuntu-Budgie 22.10 "Kinetic Kudu" - Alpha amd64 (20220726) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snap43~rc-2 JournalErrors: -- No entries -- ProcCmdline: gnome-software Signal: 6 SourcePackage: gnome-software StacktraceTop: () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 gs_utils_format_size () () Title: gnome-software crashed with SIGABRT UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sbuild sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1988648/+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()
** Tags removed: need-amd64-retrace -- 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: New 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 1988643] ibus-x11 crashed with SIGSEGV in g_closure_invoke()
StacktraceTop: ?? () g_closure_invoke (closure=0x5585a8f5d740, return_value=0x0, n_param_values=2, param_values=0x7fffa8e38000, invocation_hint=0x7fffa8e37f80) at ../../../gobject/gclosure.c:832 signal_emit_unlocked_R.isra.0 (node=node@entry=0x5585a8e36990, detail=detail@entry=349, instance=instance@entry=0x5585a8e98840, emission_return=emission_return@entry=0x0, instance_and_params=instance_and_params@entry=0x7fffa8e38000) at ../../../gobject/gsignal.c:3796 g_signal_emit_valist (instance=, signal_id=, detail=, var_args=var_args@entry=0x7fffa8e381c0) at ../../../gobject/gsignal.c:3549 g_signal_emit (instance=, signal_id=, detail=) at ../../../gobject/gsignal.c:3606 ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1988643 Title: ibus-x11 crashed with SIGSEGV in g_closure_invoke() Status in ibus package in Ubuntu: New Bug description: occurred when toggle darkmode ProblemType: Crash DistroRelease: Ubuntu 22.10 Package: ibus 1.5.27-2 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 CurrentDesktop: ubuntu:GNOME Date: Sun Sep 4 02:00:33 2022 Disassembly: => 0x7f4e338e34f0: Cannot access memory at address 0x7f4e338e34f0 ExecutablePath: /usr/libexec/ibus-x11 InstallationDate: Installed on 2020-06-25 (799 days ago) InstallationMedia: JournalErrors: Error: command ['journalctl', '--priority=warning', '--since=@1662228023', '--until=@1662228043'] 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/libexec/ibus-x11 RebootRequiredPkgs: Error: path contained symlinks. SegvAnalysis: Segfault happened at: 0x7f4e338e34f0:Cannot access memory at address 0x7f4e338e34f0 PC (0x7f4e338e34f0) not located in a known VMA region (needed executable region)! SegvReason: executing unknown VMA Signal: 11 SourcePackage: ibus StacktraceTop: ?? () 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 g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: ibus-x11 crashed with SIGSEGV in g_closure_invoke() UpgradeStatus: Upgraded to kinetic on 2022-04-25 (131 days ago) UserGroups: nordvpn sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1988643/+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 1988643] [NEW] ibus-x11 crashed with SIGSEGV in g_closure_invoke()
Public bug reported: occurred when toggle darkmode ProblemType: Crash DistroRelease: Ubuntu 22.10 Package: ibus 1.5.27-2 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 CurrentDesktop: ubuntu:GNOME Date: Sun Sep 4 02:00:33 2022 Disassembly: => 0x7f4e338e34f0: Cannot access memory at address 0x7f4e338e34f0 ExecutablePath: /usr/libexec/ibus-x11 InstallationDate: Installed on 2020-06-25 (799 days ago) InstallationMedia: JournalErrors: Error: command ['journalctl', '--priority=warning', '--since=@1662228023', '--until=@1662228043'] 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/libexec/ibus-x11 RebootRequiredPkgs: Error: path contained symlinks. SegvAnalysis: Segfault happened at: 0x7f4e338e34f0: Cannot access memory at address 0x7f4e338e34f0 PC (0x7f4e338e34f0) not located in a known VMA region (needed executable region)! SegvReason: executing unknown VMA Signal: 11 SourcePackage: ibus StacktraceTop: ?? () 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 g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: ibus-x11 crashed with SIGSEGV in g_closure_invoke() UpgradeStatus: Upgraded to kinetic on 2022-04-25 (131 days ago) UserGroups: nordvpn sudo separator: ** Affects: ibus (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 ibus in Ubuntu. https://bugs.launchpad.net/bugs/1988643 Title: ibus-x11 crashed with SIGSEGV in g_closure_invoke() Status in ibus package in Ubuntu: New Bug description: occurred when toggle darkmode ProblemType: Crash DistroRelease: Ubuntu 22.10 Package: ibus 1.5.27-2 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 CurrentDesktop: ubuntu:GNOME Date: Sun Sep 4 02:00:33 2022 Disassembly: => 0x7f4e338e34f0: Cannot access memory at address 0x7f4e338e34f0 ExecutablePath: /usr/libexec/ibus-x11 InstallationDate: Installed on 2020-06-25 (799 days ago) InstallationMedia: JournalErrors: Error: command ['journalctl', '--priority=warning', '--since=@1662228023', '--until=@1662228043'] 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/libexec/ibus-x11 RebootRequiredPkgs: Error: path contained symlinks. SegvAnalysis: Segfault happened at: 0x7f4e338e34f0:Cannot access memory at address 0x7f4e338e34f0 PC (0x7f4e338e34f0) not located in a known VMA region (needed executable region)! SegvReason: executing unknown VMA Signal: 11 SourcePackage: ibus StacktraceTop: ?? () 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 g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: ibus-x11 crashed with SIGSEGV in g_closure_invoke() UpgradeStatus: Upgraded to kinetic on 2022-04-25 (131 days ago) UserGroups: nordvpn sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1988643/+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] [NEW] NetworkManager crashed with SIGABRT in g_assertion_message_expr()
Public bug reported: 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: ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash kinetic need-amd64-retrace ** Information type changed from Private to Public -- 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: New 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 1988642] Re: Messages do not load - Evolution 3.45.3-1
Yes, that seems to have done the trick. ** Package changed: evolution (Ubuntu) => webkit2gtk (Ubuntu) ** Changed in: webkit2gtk (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to webkit2gtk in Ubuntu. https://bugs.launchpad.net/bugs/1988642 Title: Messages do not load - Evolution 3.45.3-1 Status in webkit2gtk package in Ubuntu: Fix Committed Bug description: Testing Evolution 3.45.3-1 in Ubuntu Kinetic Kudu, messages are failing to load in either the preview pane or their own window. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: evolution 3.45.3-1 ProcVersionSignature: Ubuntu 5.19.0-1003.3-lowlatency 5.19.0 Uname: Linux 5.19.0-1003-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Sep 3 09:03:03 2022 InstallationDate: Installed on 2021-08-19 (380 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210818) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: evolution UpgradeStatus: Upgraded to kinetic on 2022-09-01 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/1988642/+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 1988642] [NEW] Messages do not load - Evolution 3.45.3-1
You have been subscribed to a public bug: Testing Evolution 3.45.3-1 in Ubuntu Kinetic Kudu, messages are failing to load in either the preview pane or their own window. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: evolution 3.45.3-1 ProcVersionSignature: Ubuntu 5.19.0-1003.3-lowlatency 5.19.0 Uname: Linux 5.19.0-1003-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Sep 3 09:03:03 2022 InstallationDate: Installed on 2021-08-19 (380 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210818) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: evolution UpgradeStatus: Upgraded to kinetic on 2022-09-01 (2 days ago) ** Affects: webkit2gtk (Ubuntu) Importance: Undecided Status: Fix Committed ** Tags: amd64 apport-bug kinetic -- Messages do not load - Evolution 3.45.3-1 https://bugs.launchpad.net/bugs/1988642 You received this bug notification because you are a member of Desktop Packages, which is subscribed to webkit2gtk 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 1988641] Re: goa-daemon crashed with SIGABRT in g_assertion_message_expr()
*** This bug is a duplicate of bug 1988613 *** https://bugs.launchpad.net/bugs/1988613 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 #1988613, 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/1988641/+attachment/5613455/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1988641/+attachment/5613457/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1988641/+attachment/5613460/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1988641/+attachment/5613461/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1988641/+attachment/5613462/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1988641/+attachment/5613463/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1988641/+attachment/5613464/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1988613 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1988641 Title: goa-daemon crashed with SIGABRT in g_assertion_message_expr() Status in gnome-online-accounts package in Ubuntu: New Bug description: crash occurred on restart from suspend ProblemType: Crash DistroRelease: Ubuntu 22.10 Package: gnome-online-accounts 3.45.2-1 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 Date: Sat Sep 3 16:58:30 2022 ExecutablePath: /usr/libexec/goa-daemon InstallationDate: Installed on 2022-08-31 (3 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220828) ProcCmdline: /usr/libexec/goa-daemon ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANGUAGE=en_GB:en LANG=en_GB.UTF-8 Signal: 6 SourcePackage: gnome-online-accounts 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/librest-1.0.so.0 rest_proxy_call_sync () from /lib/x86_64-linux-gnu/librest-1.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgoa-backend-1.0.so.1 Title: goa-daemon crashed with SIGABRT in g_assertion_message_expr() 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-online-accounts/+bug/1988641/+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 1988637] Re: nautilus crashed with SIGSEGV in g_str_hash()
*** This bug is a duplicate of bug 1987981 *** https://bugs.launchpad.net/bugs/1987981 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 #1987981, 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/1988637/+attachment/5613440/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1988637/+attachment/5613442/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1988637/+attachment/5613444/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1988637/+attachment/5613445/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1988637/+attachment/5613446/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1988637/+attachment/5613447/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1988637/+attachment/5613448/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1987981 nautilus crashed with SIGSEGV in g_str_hash() ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1988637 Title: nautilus crashed with SIGSEGV in g_str_hash() Status in nautilus package in Ubuntu: New Bug description: 1) Description: Ubuntu Kinetic Kudu (development branch) Release: 22.10 2) nautilus: Installed: 1:43~beta.1-2ubuntu3 Candidate: 1:43~beta.1-2ubuntu3 Version table: *** 1:43~beta.1-2ubuntu3 500 500 http://br.archive.ubuntu.com/ubuntu kinetic/main amd64 Packages 100 /var/lib/dpkg/status 3) Nautilus simply crashed while trying to use it with sudo powers. 4) Be able to use it as usual and not keep crashing. ProblemType: Crash 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: Sat Sep 3 11:47:38 2022 ExecutablePath: /usr/bin/nautilus GsettingsChanges: InstallationDate: Installed on 2022-09-03 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220829) JournalErrors: set 03 11:47:40 hostname systemd[2014]: update-notifier-crash.service: Failed with result 'exit-code'. set 03 11:47:40 hostname systemd[2014]: Failed to start Notification regarding a crash report. set 03 11:47:44 hostname systemd[2014]: update-notifier-crash.service: Failed with result 'exit-code'. set 03 11:47:44 hostname systemd[2014]: Failed to start Notification regarding a crash report. ProcCmdline: nautilus ProcEnviron: LANGUAGE=pt_BR:pt:en LANG=pt_BR.UTF-8 TERM=xterm-256color PATH=(custom, no user) SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f62a0037434 : movsbl (%rdi),%edx PC (0x7f62a0037434) ok source "(%rdi)" (0x) not located in a known VMA region (needed readable region)! destination "%edx" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: nautilus StacktraceTop: g_str_hash () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_hash_table_contains () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgtk-4.so.1 ?? () from /lib/x86_64-linux-gnu/libgtk-4.so.1 gtk_widget_unparent () from /lib/x86_64-linux-gnu/libgtk-4.so.1 Title: nautilus crashed with SIGSEGV in g_str_hash() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A separator: 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/1988637/+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 133133]
> Open containing folder function does nothing (KDE)
Is this still an issue?
Compare with e.g. bug 893799 …
--
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/133133
Title:
"Open containing folder" is only working if nautilus is present
Status in Mozilla Firefox:
Confirmed
Status in firefox package in Ubuntu:
Fix Released
Bug description:
Binary package hint: firefox
Tools->Downloads-> (Right click)->Open containing folder
Result: Nothing happens (not even an error).
Expected: An error, a dialog asking to choose a file manager or just
konqueror showing the folder.
Fix: add the following line to prefs.js
user_pref("network.protocol-handler.app.file", "konqueror");
ProblemType: Bug
Architecture: i386
Date: Fri Aug 17 12:54:22 2007
DistroRelease: Ubuntu 7.04
Package: firefox 2.0.0.5+1-0ubuntu1
PackageArchitecture: i386
SourcePackage: firefox
Uname: Linux localhost 2.6.20-12-generic #2 SMP Wed Mar 21 20:55:46 UTC 2007
i686 GNU/Linux
To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/133133/+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 1988622] Re: gnome-sushi stopped working
It looks like this was fixed in https://gitlab.gnome.org/GNOME/nautilus/-/commit/6bd3b8cd59c We should be getting Nautilus 43 RC with that fix in a few days. ** Package changed: gnome-sushi (Ubuntu) => nautilus (Ubuntu) ** Changed in: nautilus (Ubuntu) Status: New => Fix Committed -- 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/1988622 Title: gnome-sushi stopped working Status in nautilus package in Ubuntu: Fix Committed Bug description: Click a file, press space bar: nothing happens, sushi does not start. It was working few days ago. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-sushi 42.0-2 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: Sat Sep 3 09:48:06 2022 InstallationDate: Installed on 2022-08-11 (22 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220811) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gnome-sushi UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1988622/+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 1988622] [NEW] gnome-sushi stopped working
You have been subscribed to a public bug: Click a file, press space bar: nothing happens, sushi does not start. It was working few days ago. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-sushi 42.0-2 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: Sat Sep 3 09:48:06 2022 InstallationDate: Installed on 2022-08-11 (22 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220811) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gnome-sushi UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nautilus (Ubuntu) Importance: High Status: Fix Committed ** Tags: amd64 apport-bug kinetic wayland-session -- gnome-sushi stopped working https://bugs.launchpad.net/bugs/1988622 You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus 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 1988631] Re: Firefox snap update doesn't work and popup is very annoying
** Attachment added: "Popup" https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1988631/+attachment/5613416/+files/Screenshot_20220903_120858.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/1988631 Title: Firefox snap update doesn't work and popup is very annoying Status in firefox package in Ubuntu: New Bug description: Each time snap thinks that firefox should be updated (-> so this happens quite often) a popup message appears and stays above all other windows all the time to remind me to close firefox. It also gives me a couple of days that are granted to me to do that. I can close this popup - but after a shot time it comes up again. This popup is very annoying and distracts me from the work that I'm just doing. Every day in the evening I shut down my computer completely, so firefox is also closed. In the morning I start it up and firefox gets automatically started again (as intended by me). But it seems that snap is not capable to handle a shutdown and restart to do its work. It just prefers to annoy me in multiple ways instead: it takes away my authority over my system and my decision when I'm prepared to do an update or not. It doesn't give me a choice to skip a specific version when I don't want to use it. It tries to put me under pressure to do the update like a bad sales agent (only ... days left). All of this was perfectly solved when firefox was a normal APT package. The system I'm running is Kubuntu, based on Ubuntu 22.04.1 LTS Firefox is 104.0.1 - but it happend already with older versions of it as well To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1988631/+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 1988631] Re: Firefox snap update doesn't work and popup is very annoying
-- 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/1988631 Title: Firefox snap update doesn't work and popup is very annoying Status in firefox package in Ubuntu: New Bug description: Each time snap thinks that firefox should be updated (-> so this happens quite often) a popup message appears and stays above all other windows all the time to remind me to close firefox. It also gives me a couple of days that are granted to me to do that. I can close this popup - but after a shot time it comes up again. This popup is very annoying and distracts me from the work that I'm just doing. Every day in the evening I shut down my computer completely, so firefox is also closed. In the morning I start it up and firefox gets automatically started again (as intended by me). But it seems that snap is not capable to handle a shutdown and restart to do its work. It just prefers to annoy me in multiple ways instead: it takes away my authority over my system and my decision when I'm prepared to do an update or not. It doesn't give me a choice to skip a specific version when I don't want to use it. It tries to put me under pressure to do the update like a bad sales agent (only ... days left). All of this was perfectly solved when firefox was a normal APT package. The system I'm running is Kubuntu, based on Ubuntu 22.04.1 LTS Firefox is 104.0.1 - but it happend already with older versions of it as well To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1988631/+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 1988631] [NEW] Firefox snap update doesn't work and popup is very annoying
Public bug reported: Each time snap thinks that firefox should be updated (-> so this happens quite often) a popup message appears and stays above all other windows all the time to remind me to close firefox. It also gives me a couple of days that are granted to me to do that. I can close this popup - but after a shot time it comes up again. This popup is very annoying and distracts me from the work that I'm just doing. Every day in the evening I shut down my computer completely, so firefox is also closed. In the morning I start it up and firefox gets automatically started again (as intended by me). But it seems that snap is not capable to handle a shutdown and restart to do its work. It just prefers to annoy me in multiple ways instead: it takes away my authority over my system and my decision when I'm prepared to do an update or not. It doesn't give me a choice to skip a specific version when I don't want to use it. It tries to put me under pressure to do the update like a bad sales agent (only ... days left). All of this was perfectly solved when firefox was a normal APT package. The system I'm running is Kubuntu, based on Ubuntu 22.04.1 LTS Firefox is 104.0.1 - but it happend already with older versions of it as well ** Affects: firefox (Ubuntu) Importance: Undecided Status: New -- 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/1988631 Title: Firefox snap update doesn't work and popup is very annoying Status in firefox package in Ubuntu: New Bug description: Each time snap thinks that firefox should be updated (-> so this happens quite often) a popup message appears and stays above all other windows all the time to remind me to close firefox. It also gives me a couple of days that are granted to me to do that. I can close this popup - but after a shot time it comes up again. This popup is very annoying and distracts me from the work that I'm just doing. Every day in the evening I shut down my computer completely, so firefox is also closed. In the morning I start it up and firefox gets automatically started again (as intended by me). But it seems that snap is not capable to handle a shutdown and restart to do its work. It just prefers to annoy me in multiple ways instead: it takes away my authority over my system and my decision when I'm prepared to do an update or not. It doesn't give me a choice to skip a specific version when I don't want to use it. It tries to put me under pressure to do the update like a bad sales agent (only ... days left). All of this was perfectly solved when firefox was a normal APT package. The system I'm running is Kubuntu, based on Ubuntu 22.04.1 LTS Firefox is 104.0.1 - but it happend already with older versions of it as well To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1988631/+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 1988625] [NEW] Left-over cursor visible on second screen
Public bug reported: This sounds like (Fix Released) #1724977, but seems to happen on extra screens. When I move my mouse between screens, every once in a while a leftover cursor remains on the screen I just left. Moving to that screen again fixes. It may be related to different scales of my two displays (100% vs. 200%). ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43~beta-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Sep 3 11:51:47 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-08-31 (2 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220829) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/zsh RelatedPackageVersions: mutter-common 43~beta-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic wayland-session -- 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/1988625 Title: Left-over cursor visible on second screen Status in gnome-shell package in Ubuntu: New Bug description: This sounds like (Fix Released) #1724977, but seems to happen on extra screens. When I move my mouse between screens, every once in a while a leftover cursor remains on the screen I just left. Moving to that screen again fixes. It may be related to different scales of my two displays (100% vs. 200%). ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43~beta-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Sep 3 11:51:47 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-08-31 (2 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220829) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/zsh 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/ubuntu/+source/gnome-shell/+bug/1988625/+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 1988623] [NEW] Screen stuck off after locking
Public bug reported: When the screen goes off after a timeout, or locking the session, it doesn't wake again when I move the mouse or use the keyboard. Switching to GDM and back works, or logging in in GDM. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43~beta-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Sep 3 09:50:03 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-08-31 (2 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220829) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/zsh RelatedPackageVersions: mutter-common 43~beta-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic wayland-session -- 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/1988623 Title: Screen stuck off after locking Status in gnome-shell package in Ubuntu: New Bug description: When the screen goes off after a timeout, or locking the session, it doesn't wake again when I move the mouse or use the keyboard. Switching to GDM and back works, or logging in in GDM. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43~beta-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Sep 3 09:50:03 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-08-31 (2 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220829) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/zsh 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/ubuntu/+source/gnome-shell/+bug/1988623/+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 1988028] Re: separate firefox profiles open in the same dock icon
** Package changed: gnome (Ubuntu) => gnome-shell-extension-ubuntu-dock (Ubuntu) ** Tags added: jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1988028 Title: separate firefox profiles open in the same dock icon Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: This worked in Ubuntu 20.04, and broke in Ubuntu 22.04.1 LTS. I'm not sure if the module this bug is in is gnome. This seems to describe a similar issue: https://bugs.chromium.org/p/chromium/issues/detail?id=118613 except my problem occurs with multiple profiles of firefox, and is not fixed by adding --user-data-dir. The chromium bug report suggests the --class argument is ignored, which may be the problem. I have a separate icon and separate desktop file for each firefox profile. When I click on one of these icons in the dock, it (buggy behavior) creates a new icon on the dock with the generic firefox icon, instead of (expected behavior) associating the newly opened window with my unique icon for each profile. The chromium bug link above suggests it's fixed by adding --user-data- dir, but I tried that, e.g., --user-data-dir=/tmp/firefox1, but that didn't fix it for me. My desktop files contain: firefox1.desktop: Exec=firefox -P default %u --class firefox1 StartupWMClass=firefox1 wmclass=firefox1 Icon=firefox-green48.png firefox2.desktop: Exec=firefox -no-remote -P second %u --class firefox2 StartupWMClass=firefox2 wmclass=firefox2 Icon=firefox-purple48.png firefox3.desktop: Exec=firefox -no-remote -P third %u --class firefox3 StartupWMClass=firefox3 wmclass=firefox3 Icon=firefox-yellow48.png To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1988028/+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 1988028] [NEW] separate firefox profiles open in the same dock icon
You have been subscribed to a public bug: This worked in Ubuntu 20.04, and broke in Ubuntu 22.04.1 LTS. I'm not sure if the module this bug is in is gnome. This seems to describe a similar issue: https://bugs.chromium.org/p/chromium/issues/detail?id=118613 except my problem occurs with multiple profiles of firefox, and is not fixed by adding --user-data-dir. The chromium bug report suggests the --class argument is ignored, which may be the problem. I have a separate icon and separate desktop file for each firefox profile. When I click on one of these icons in the dock, it (buggy behavior) creates a new icon on the dock with the generic firefox icon, instead of (expected behavior) associating the newly opened window with my unique icon for each profile. The chromium bug link above suggests it's fixed by adding --user-data- dir, but I tried that, e.g., --user-data-dir=/tmp/firefox1, but that didn't fix it for me. My desktop files contain: firefox1.desktop: Exec=firefox -P default %u --class firefox1 StartupWMClass=firefox1 wmclass=firefox1 Icon=firefox-green48.png firefox2.desktop: Exec=firefox -no-remote -P second %u --class firefox2 StartupWMClass=firefox2 wmclass=firefox2 Icon=firefox-purple48.png firefox3.desktop: Exec=firefox -no-remote -P third %u --class firefox3 StartupWMClass=firefox3 wmclass=firefox3 Icon=firefox-yellow48.png ** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New -- separate firefox profiles open in the same dock icon https://bugs.launchpad.net/bugs/1988028 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock 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
