[Bug 1897754] [NEW] The icon does not appear in the GNOME bar
Public bug reported: When upgrading from gnome-shell-extension-appindicator_33-3_all.deb to gnome-shell-extension-appindicator_34-1_all.deb the icon does not appear in the GNOME toolbar. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: flameshot 0.8.1-1 Uname: Linux 5.8.12-050812-generic x86_64 ApportVersion: 2.20.11-0ubuntu48 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Sep 29 11:55:57 2020 InstallationDate: Installed on 2020-06-19 (102 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200609) SourcePackage: flameshot UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: flameshot (Ubuntu) Importance: Undecided Status: New ** Affects: gnome-shell-extension-appindicator (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy ** Also affects: gnome-shell-extension-appindicator (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1897754 Title: The icon does not appear in the GNOME bar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flameshot/+bug/1897754/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1897754] Re: The icon does not appear in the GNOME bar
** Description changed: + https://github.com/flameshot-org/flameshot/issues/1009 + + --- + When upgrading from gnome-shell-extension-appindicator_33-3_all.deb to gnome-shell-extension-appindicator_34-1_all.deb the icon does not appear in the GNOME toolbar. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: flameshot 0.8.1-1 Uname: Linux 5.8.12-050812-generic x86_64 ApportVersion: 2.20.11-0ubuntu48 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Sep 29 11:55:57 2020 InstallationDate: Installed on 2020-06-19 (102 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200609) SourcePackage: flameshot UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1897754 Title: The icon does not appear in the GNOME bar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flameshot/+bug/1897754/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1822350] Re: evince crashed with SIGABRT in g_assertion_message()
https://gitlab.gnome.org/GNOME/evince/issues/1120 ** Description changed: Click in 'File options->Dual' my PDF. + + JournalErrors.txt: + mar 29 13:24:40 hostname evince[3914]: invalid cast from 'EvSidebar' to 'EvWindow' + mar 29 13:24:40 hostname org.gnome.Nautilus[1515]: ** + mar 29 13:24:40 hostname org.gnome.Nautilus[1515]: GLib:ERROR:../../../glib/ghash.c:468:g_hash_table_lookup_node: assertion failed: (!g_atomic_ref_count_compare (&hash_table->ref_count, 0)) + mar 29 13:24:40 hostname evince[3914]: invalid cast from 'EvSidebar' to 'EvWindow' ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: evince 3.32.0-1 Uname: Linux 5.0.5-050005-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 29 13:24:40 2019 ExecutablePath: /usr/bin/evince InstallationDate: Installed on 2018-12-02 (116 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: BOOT_IMAGE=/@/boot/vmlinuz-5.0.5-050005-generic root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet splash vt.handoff=1 ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash LANGUAGE=es_CL:es PATH=(custom, no user) LANG=es_CL.UTF-8 Signal: 6 SourcePackage: evince StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_hash_table_lookup () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () ?? () Title: evince crashed with SIGABRT in g_assertion_message_expr() UpgradeStatus: Upgraded to disco on 2018-12-02 (116 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: ** Information type changed from Private to Public ** Description changed: Click in 'File options->Dual' my PDF. - - JournalErrors.txt: - mar 29 13:24:40 hostname evince[3914]: invalid cast from 'EvSidebar' to 'EvWindow' - mar 29 13:24:40 hostname org.gnome.Nautilus[1515]: ** - mar 29 13:24:40 hostname org.gnome.Nautilus[1515]: GLib:ERROR:../../../glib/ghash.c:468:g_hash_table_lookup_node: assertion failed: (!g_atomic_ref_count_compare (&hash_table->ref_count, 0)) - mar 29 13:24:40 hostname evince[3914]: invalid cast from 'EvSidebar' to 'EvWindow' ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: evince 3.32.0-1 Uname: Linux 5.0.5-050005-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 29 13:24:40 2019 ExecutablePath: /usr/bin/evince InstallationDate: Installed on 2018-12-02 (116 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: BOOT_IMAGE=/@/boot/vmlinuz-5.0.5-050005-generic root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet splash vt.handoff=1 ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash LANGUAGE=es_CL:es PATH=(custom, no user) LANG=es_CL.UTF-8 Signal: 6 SourcePackage: evince StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_hash_table_lookup () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () ?? () Title: evince crashed with SIGABRT in g_assertion_message_expr() UpgradeStatus: Upgraded to disco on 2018-12-02 (116 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: ** Description changed: + https://gitlab.gnome.org/GNOME/evince/issues/1120 + + --- + Click in 'File options->Dual' my PDF. ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: evince 3.32.0-1 Uname: Linux 5.0.5-050005-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 29 13:24:40 2019 ExecutablePath: /usr/bin/evince InstallationDate: Installed on 2018-12-02 (116 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: BOOT_IMAGE=/@/boot/vmlinuz-5.0.5-050005-generic root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet splash vt.handoff=1 ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash LANGUAGE=es_CL:es PATH=(custom, no user) LANG=es_CL.UTF-8 Signal: 6 SourcePackage: evince StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_hash_table_lookup () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () ?? () Title: evince crashed with SIGABRT in g_assertion_message_expr() UpgradeStatus: Upgraded to disco on 2018-12-02 (116 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: ** Bug watch added: gitlab.gnome.org/GNOME/evince/issues #1120 https://gitlab.gnome.org/GNOME/evince/issues/1120 ** Also affects: evince via https://gitlab.gnome.org/GNOME
[Bug 1822350] Re: evince crashed with SIGABRT in g_assertion_message()
** Description changed: https://gitlab.gnome.org/GNOME/evince/issues/1120 --- - Click in 'File options->Dual' my PDF. + Click in 'File options->Dual' in my PDF. ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: evince 3.32.0-1 Uname: Linux 5.0.5-050005-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 29 13:24:40 2019 ExecutablePath: /usr/bin/evince InstallationDate: Installed on 2018-12-02 (116 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: BOOT_IMAGE=/@/boot/vmlinuz-5.0.5-050005-generic root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet splash vt.handoff=1 ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash LANGUAGE=es_CL:es PATH=(custom, no user) LANG=es_CL.UTF-8 Signal: 6 SourcePackage: evince StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_hash_table_lookup () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () ?? () Title: evince crashed with SIGABRT in g_assertion_message_expr() UpgradeStatus: Upgraded to disco on 2018-12-02 (116 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1822350 Title: evince crashed with SIGABRT in g_assertion_message() To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/1822350/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1823529] Re: nautilus crashed with SIGABRT in g_assertion_message()
** Description changed: + [Impact] + After opening nautilus, I open 'another' tab with the mouse wheel button (middle mouse button) in 'Other Locations' and nautilius crashes. + + [Test Case] + 1. Open nautilus + 2. Click with the middle mouse button on 'Other Locations' + 3. Crash nautilus + + [Original Description] I do not know what happened. ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: nautilus 1:3.32.0-0ubuntu2 Uname: Linux 5.0.7-050007-generic x86_64 ApportVersion: 2.20.10-0ubuntu25 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 7 08:21:59 2019 ExecutablePath: /usr/bin/nautilus GsettingsChanges: - b'org.gnome.nautilus.window-state' b'sidebar-width' b'341' - b'org.gnome.nautilus.window-state' b'initial-size' b'(1458, 748)' - b'org.gnome.nautilus.window-state' b'maximized' b'true' - b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" + b'org.gnome.nautilus.window-state' b'sidebar-width' b'341' + b'org.gnome.nautilus.window-state' b'initial-size' b'(1458, 748)' + b'org.gnome.nautilus.window-state' b'maximized' b'true' + b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" InstallationDate: Installed on 2018-12-02 (125 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/nautilus --gapplication-service ProcEnviron: - SHELL=/bin/bash - XDG_RUNTIME_DIR= - PATH=(custom, no user) - LANGUAGE=es_CL:es - LANG=es_CL.UTF-8 + SHELL=/bin/bash + XDG_RUNTIME_DIR= + PATH=(custom, no user) + LANGUAGE=es_CL:es + LANG=es_CL.UTF-8 Signal: 6 SourcePackage: nautilus StacktraceTop: - ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 - g_assertion_message_expr () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 - ?? () - ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 - g_main_context_dispatch () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 + ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 + g_assertion_message_expr () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 + ?? () + ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 + g_main_context_dispatch () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: nautilus crashed with SIGABRT in g_assertion_message_expr() UpgradeStatus: Upgraded to disco on 2018-12-02 (125 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: - + usr_lib_nautilus: ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1823529 Title: nautilus crashed with SIGABRT in g_assertion_message() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1823529/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1823529] Re: nautilus crashed with SIGABRT in g_assertion_message()
** Description changed: [Impact] After opening nautilus, I open 'another' tab with the mouse wheel button (middle mouse button) in 'Other Locations' and nautilius crashes. [Test Case] 1. Open nautilus - 2. Click with the middle mouse button on 'Other Locations' + 2. Click with the middle mouse button on 'Other Locations' (To open another tab) 3. Crash nautilus [Original Description] I do not know what happened. ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: nautilus 1:3.32.0-0ubuntu2 Uname: Linux 5.0.7-050007-generic x86_64 ApportVersion: 2.20.10-0ubuntu25 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 7 08:21:59 2019 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'341' b'org.gnome.nautilus.window-state' b'initial-size' b'(1458, 748)' b'org.gnome.nautilus.window-state' b'maximized' b'true' b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" InstallationDate: Installed on 2018-12-02 (125 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/nautilus --gapplication-service ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANGUAGE=es_CL:es LANG=es_CL.UTF-8 Signal: 6 SourcePackage: nautilus StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_main_context_dispatch () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: nautilus crashed with SIGABRT in g_assertion_message_expr() UpgradeStatus: Upgraded to disco on 2018-12-02 (125 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: usr_lib_nautilus: -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1823529 Title: nautilus crashed with SIGABRT in g_assertion_message() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1823529/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1823529] Re: nautilus crashed with SIGABRT in g_assertion_message()
** Description changed: + https://gitlab.gnome.org/GNOME/nautilus/issues/980 + + --- + [Impact] After opening nautilus, I open 'another' tab with the mouse wheel button (middle mouse button) in 'Other Locations' and nautilius crashes. [Test Case] 1. Open nautilus - 2. Click with the middle mouse button on 'Other Locations' (To open another tab) + 2. Click with the middle mouse button on 'Other Locations' 3. Crash nautilus [Original Description] I do not know what happened. ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: nautilus 1:3.32.0-0ubuntu2 Uname: Linux 5.0.7-050007-generic x86_64 ApportVersion: 2.20.10-0ubuntu25 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 7 08:21:59 2019 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'341' b'org.gnome.nautilus.window-state' b'initial-size' b'(1458, 748)' b'org.gnome.nautilus.window-state' b'maximized' b'true' b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" InstallationDate: Installed on 2018-12-02 (125 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/nautilus --gapplication-service ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANGUAGE=es_CL:es LANG=es_CL.UTF-8 Signal: 6 SourcePackage: nautilus StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_main_context_dispatch () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: nautilus crashed with SIGABRT in g_assertion_message_expr() UpgradeStatus: Upgraded to disco on 2018-12-02 (125 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: usr_lib_nautilus: -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1823529 Title: nautilus crashed with SIGABRT in g_assertion_message() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1823529/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1823529] Re: nautilus crashed with SIGABRT in g_assertion_message()
https://gitlab.gnome.org/GNOME/nautilus/issues/980 ** Bug watch added: gitlab.gnome.org/GNOME/nautilus/issues #980 https://gitlab.gnome.org/GNOME/nautilus/issues/980 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1823529 Title: nautilus crashed with SIGABRT in g_assertion_message() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1823529/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1824637] [NEW] Full load
Public bug reported: It always happens when I start the notebook. I must close it with 'kill -u ProcessNumber' Please indicate that more information is needed to repair this error. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: tracker 2.1.8-2 Uname: Linux 5.0.7-050007-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 13 12:42:44 2019 InstallationDate: Installed on 2018-12-02 (131 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: tracker UpgradeStatus: Upgraded to disco on 2018-12-02 (131 days ago) ** Affects: tracker (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco wayland-session -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1824637 Title: Full load To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1824637/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1810316] Re: gnome-control-center SIGABRT when n-m is not working (G_IS_OBJECT (object))
https://gitlab.gnome.org/GNOME/gnome-control-center/issues/342 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/issues #342 https://gitlab.gnome.org/GNOME/gnome-control-center/issues/342 ** Description changed: - https://gitlab.gnome.org/GNOME/gnome-control-center/issues/432 + https://gitlab.gnome.org/GNOME/gnome-control-center/issues/342 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/143 --- [Impact] gnome-control-center goes crash when I try to work with two USB WiFi cards. [Test Case] I have a wireless card connected and then I connect 'another' wireless card and the network module starts to malfunction in the gnome-control-center. [Potential Regression] I think it's not a potential regression. Original Description * I was trying to open wifi settings * I'm connecting 2 WiFi USB in ubuntu disk ProblemType: Crash DistroRelease: Ubuntu 18.10 Package: gnome-control-center 1:3.30.2-1ubuntu0.18.10.1 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 2 09:54:42 2019 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2018-09-27 (97 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: gnome-control-center wifi ProcEnviron: LC_COLLATE=C PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: gnome-control-center StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 cc_object_storage_add_object () cc_wifi_panel_static_init_func () cc_panel_loader_fill_model () Title: gnome-control-center crashed with SIGABRT UpgradeStatus: Upgraded to cosmic on 2018-11-08 (54 days ago) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo vboxusers wireshark modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2018-10-04T06:36:50.792292 ** No longer affects: gnome-control-center ** Also affects: gnome-control-center via https://gitlab.gnome.org/GNOME/gnome-control-center/issues/342 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1810316 Title: gnome-control-center SIGABRT when n-m is not working (G_IS_OBJECT (object)) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1810316/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1810316] Re: gnome-control-center SIGABRT when n-m is not working (G_IS_OBJECT (object))
** Description changed: + The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-control-center. This problem was most recently seen with package version 1:3.30.0-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/b90090b3330514b0e5d6f1ed58c2260a77b8e5e8 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. + If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. + + --- + https://gitlab.gnome.org/GNOME/gnome-control-center/issues/342 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/143 --- [Impact] gnome-control-center goes crash when I try to work with two USB WiFi cards. [Test Case] I have a wireless card connected and then I connect 'another' wireless card and the network module starts to malfunction in the gnome-control-center. [Potential Regression] I think it's not a potential regression. Original Description * I was trying to open wifi settings * I'm connecting 2 WiFi USB in ubuntu disk ProblemType: Crash DistroRelease: Ubuntu 18.10 Package: gnome-control-center 1:3.30.2-1ubuntu0.18.10.1 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 2 09:54:42 2019 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2018-09-27 (97 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: gnome-control-center wifi ProcEnviron: LC_COLLATE=C PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: gnome-control-center StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 cc_object_storage_add_object () cc_wifi_panel_static_init_func () cc_panel_loader_fill_model () Title: gnome-control-center crashed with SIGABRT UpgradeStatus: Upgraded to cosmic on 2018-11-08 (54 days ago) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo vboxusers wireshark modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2018-10-04T06:36:50.792292 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1810316 Title: gnome-control-center SIGABRT when n-m is not working (G_IS_OBJECT (object)) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1810316/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1758287] Re: totem crashed with SIGTRAP in __glXSendError() from MakeContextCurrent()
https://bugs.freedesktop.org/show_bug.cgi?id=110452 ** Also affects: mesa (Ubuntu) Importance: Undecided Status: New ** Bug watch added: freedesktop.org Bugzilla #110452 https://bugs.freedesktop.org/show_bug.cgi?id=110452 ** Also affects: mesa via https://bugs.freedesktop.org/show_bug.cgi?id=110452 Importance: Unknown Status: Unknown ** Description changed: https://errors.ubuntu.com/problem/c7d8b2eb8ea371781ada6f2182d6926557d2fa91 + + --- + + https://bugs.freedesktop.org/show_bug.cgi?id=110452 --- totem crashed with signal 5 ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: totem 3.26.0-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 23 11:26:51 2018 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2017-05-04 (323 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170503) ProcCmdline: /usr/bin/totem --gapplication-service Signal: 5 SourcePackage: totem StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0 ?? () from /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstvaapi.so Title: totem crashed with signal 5 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo ** Description changed: + https://bugs.freedesktop.org/show_bug.cgi?id=110452 https://errors.ubuntu.com/problem/c7d8b2eb8ea371781ada6f2182d6926557d2fa91 - - --- - - https://bugs.freedesktop.org/show_bug.cgi?id=110452 --- totem crashed with signal 5 ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: totem 3.26.0-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 23 11:26:51 2018 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2017-05-04 (323 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170503) ProcCmdline: /usr/bin/totem --gapplication-service Signal: 5 SourcePackage: totem StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0 ?? () from /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstvaapi.so Title: totem crashed with signal 5 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1758287 Title: totem crashed with SIGTRAP in __glXSendError() from MakeContextCurrent() To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1758287/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1758287] Re: totem crashed with SIGTRAP in __glXSendError() from MakeContextCurrent()
** Changed in: mesa (Ubuntu)
Status: New => Invalid
** Description changed:
- https://bugs.freedesktop.org/show_bug.cgi?id=110452
+ https://bugs.freedesktop.org/show_bug.cgi?id=110452 (RESOLVED NOTOURBUG)
https://errors.ubuntu.com/problem/c7d8b2eb8ea371781ada6f2182d6926557d2fa91
---
totem crashed with signal 5
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: totem 3.26.0-0ubuntu5
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar 23 11:26:51 2018
ExecutablePath: /usr/bin/totem
InstallationDate: Installed on 2017-05-04 (323 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170503)
ProcCmdline: /usr/bin/totem --gapplication-service
Signal: 5
SourcePackage: totem
StacktraceTop:
?? () from /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0
?? () from /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0
?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0
?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0
?? () from /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstvaapi.so
Title: totem crashed with signal 5
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
** Description changed:
https://bugs.freedesktop.org/show_bug.cgi?id=110452 (RESOLVED NOTOURBUG)
https://errors.ubuntu.com/problem/c7d8b2eb8ea371781ada6f2182d6926557d2fa91
---
- totem crashed with signal 5
+ Backtrace goes through:
+
+ totem -> clutter-gst (frame update) -> cogl (pipeline free) -> gstreamer
+ (buffer free) -> gstreamer-vaapi (destroy objects) -> Nvidia libglvd
+ (CommonMakeCurrent / InternalMakeCurrentVendor) -> Mesa GLX
+ (MakeContextCurrent) -> Xlib (XError)
+
+ Ubuntu bug doesn't say anything about what's the use-case / when this
+ happens and whether it's reproducible (is it e.g. timing related), it
+ seems just some random crash that Apport collects.
+
+ In the backtrace Mesa MakeContextCurrent() calls __glXSendError() to tell
that it was given invalid/bad context. Corresponding Mesa code:
+ ---
+if (gc) {
+ /* Attempt to bind the context. We do this before mucking with
+* gc and __glXSetCurrentContext to properly handle our state in
+* case of an error.
+*
+* If an error occurs, set the Null context since we've already
+* blown away our old context. The caller is responsible for
+* figuring out how to handle setting a valid context.
+*/
+ if (gc->vtable->bind(gc, oldGC, draw, read) != Success) {
+ __glXSetCurrentContextNull();
+ __glXUnlock();
+ __glXSendError(dpy, GLXBadContext, None, X_GLXMakeContextCurrent,
+ False);
+ return GL_FALSE;
+ }
+ ---
+
+ I.e. bug is in what is given to Mesa, not what Mesa does.
+
+ -> NOTOURBUG
+
+
+ To me it looks something that could happen when Totem is exiting, gst-vaapi
is trying to use resources that have already been freed, and X catching that
when Gstreamer gstvaapitexture_glx.c::destroy_objects() ask libglvnd to do
CommonMakeCurrent().
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: totem 3.26.0-0ubuntu5
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar 23 11:26:51 2018
ExecutablePath: /usr/bin/totem
InstallationDate: Installed on 2017-05-04 (323 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170503)
ProcCmdline: /usr/bin/totem --gapplication-service
Signal: 5
SourcePackage: totem
StacktraceTop:
?? () from /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0
?? () from /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0
?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0
?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0
?? () from /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstvaapi.so
Title: totem crashed with signal 5
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
** Also affects: gstreamer (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: gstreamer (Ubuntu)
** Also affects: gstreamer-vaapi (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to totem in Ubuntu.
https://bugs.launchpad.net/bugs/1758287
Title:
totem crashed with SIGTRAP in __glXSendError() from
MakeContextCurrent()
To manage notifications about this bug go to:
https://bugs.launchpad.net/gstreamer/+bug/1758287/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mail
[Bug 1758287] Re: totem crashed with SIGTRAP in __glXSendError() from MakeContextCurrent()
https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/153
** Bug watch added: gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues #153
https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/153
** Also affects: gstreamer via
https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/153
Importance: Unknown
Status: Unknown
** Description changed:
+ https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/153
https://bugs.freedesktop.org/show_bug.cgi?id=110452 (RESOLVED NOTOURBUG)
https://errors.ubuntu.com/problem/c7d8b2eb8ea371781ada6f2182d6926557d2fa91
---
Backtrace goes through:
totem -> clutter-gst (frame update) -> cogl (pipeline free) -> gstreamer
(buffer free) -> gstreamer-vaapi (destroy objects) -> Nvidia libglvd
(CommonMakeCurrent / InternalMakeCurrentVendor) -> Mesa GLX
(MakeContextCurrent) -> Xlib (XError)
Ubuntu bug doesn't say anything about what's the use-case / when this
happens and whether it's reproducible (is it e.g. timing related), it
seems just some random crash that Apport collects.
In the backtrace Mesa MakeContextCurrent() calls __glXSendError() to tell
that it was given invalid/bad context. Corresponding Mesa code:
---
-if (gc) {
- /* Attempt to bind the context. We do this before mucking with
-* gc and __glXSetCurrentContext to properly handle our state in
-* case of an error.
-*
-* If an error occurs, set the Null context since we've already
-* blown away our old context. The caller is responsible for
-* figuring out how to handle setting a valid context.
-*/
- if (gc->vtable->bind(gc, oldGC, draw, read) != Success) {
- __glXSetCurrentContextNull();
- __glXUnlock();
- __glXSendError(dpy, GLXBadContext, None, X_GLXMakeContextCurrent,
- False);
- return GL_FALSE;
- }
+ if (gc) {
+ /* Attempt to bind the context. We do this before mucking with
+ * gc and __glXSetCurrentContext to properly handle our state in
+ * case of an error.
+ *
+ * If an error occurs, set the Null context since we've already
+ * blown away our old context. The caller is responsible for
+ * figuring out how to handle setting a valid context.
+ */
+ if (gc->vtable->bind(gc, oldGC, draw, read) != Success) {
+ __glXSetCurrentContextNull();
+ __glXUnlock();
+ __glXSendError(dpy, GLXBadContext, None, X_GLXMakeContextCurrent,
+ False);
+ return GL_FALSE;
+ }
---
I.e. bug is in what is given to Mesa, not what Mesa does.
-> NOTOURBUG
-
- To me it looks something that could happen when Totem is exiting, gst-vaapi
is trying to use resources that have already been freed, and X catching that
when Gstreamer gstvaapitexture_glx.c::destroy_objects() ask libglvnd to do
CommonMakeCurrent().
+ To me it looks something that could happen when Totem is exiting, gst-
+ vaapi is trying to use resources that have already been freed, and X
+ catching that when Gstreamer gstvaapitexture_glx.c::destroy_objects()
+ ask libglvnd to do CommonMakeCurrent().
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: totem 3.26.0-0ubuntu5
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar 23 11:26:51 2018
ExecutablePath: /usr/bin/totem
InstallationDate: Installed on 2017-05-04 (323 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170503)
ProcCmdline: /usr/bin/totem --gapplication-service
Signal: 5
SourcePackage: totem
StacktraceTop:
?? () from /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0
?? () from /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0
?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0
?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0
?? () from /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstvaapi.so
Title: totem crashed with signal 5
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to totem in Ubuntu.
https://bugs.launchpad.net/bugs/1758287
Title:
totem crashed with SIGTRAP in __glXSendError() from
MakeContextCurrent()
To manage notifications about this bug go to:
https://bugs.launchpad.net/gstreamer/+bug/1758287/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1758287] Re: totem crashed with SIGTRAP in __glXSendError() from MakeContextCurrent()
** Changed in: totem (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1758287 Title: totem crashed with SIGTRAP in __glXSendError() from MakeContextCurrent() To manage notifications about this bug go to: https://bugs.launchpad.net/gstreamer/+bug/1758287/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1825167] Re: It does not correctly display the hard drive icon
https://gitlab.gnome.org/GNOME/nautilus/issues/991 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1825167 Title: It does not correctly display the hard drive icon To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1825167/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1825167] [NEW] It does not correctly display the hard drive icon
Public bug reported: https://gitlab.gnome.org/GNOME/nautilus/issues/991 --- The icon of my hard drive is SSD (Attach image). ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: nautilus 1:3.32.0-0ubuntu2 Uname: Linux 5.0.8-050008-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 Date: Wed Apr 17 08:52:05 2019 InstallationDate: Installed on 2018-12-02 (135 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: LANGUAGE=es_CL:es TERM=xterm-256color PATH=(custom, no user) LANG=es_CL.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: Upgraded to disco on 2018-12-02 (135 days ago) usr_lib_nautilus: ** Affects: nautilus Importance: Unknown Status: Unknown ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco ** Attachment added: "Captura de pantalla de 2019-04-17 08-48-24.png" https://bugs.launchpad.net/bugs/1825167/+attachment/5256541/+files/Captura%20de%20pantalla%20de%202019-04-17%2008-48-24.png ** Description changed: + https://gitlab.gnome.org/GNOME/nautilus/issues/991 + + --- + The icon of my hard drive is SSD (Attach image). ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: nautilus 1:3.32.0-0ubuntu2 Uname: Linux 5.0.8-050008-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 Date: Wed Apr 17 08:52:05 2019 InstallationDate: Installed on 2018-12-02 (135 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: - LANGUAGE=es_CL:es - TERM=xterm-256color - PATH=(custom, no user) - LANG=es_CL.UTF-8 - SHELL=/bin/bash + LANGUAGE=es_CL:es + TERM=xterm-256color + PATH=(custom, no user) + LANG=es_CL.UTF-8 + SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: Upgraded to disco on 2018-12-02 (135 days ago) usr_lib_nautilus: ** Bug watch added: gitlab.gnome.org/GNOME/nautilus/issues #991 https://gitlab.gnome.org/GNOME/nautilus/issues/991 ** Also affects: nautilus via https://gitlab.gnome.org/GNOME/nautilus/issues/991 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1825167 Title: It does not correctly display the hard drive icon To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1825167/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1825167] Re: It does not correctly display the hard drive icon
I changed the name of the gmail account to USER. ** Attachment added: "$ gio mount -li" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1825167/+attachment/5256545/+files/gio_mount_-liV2.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1825167 Title: It does not correctly display the hard drive icon To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1825167/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1758287] Re: totem crashed with SIGTRAP in __glXSendError() from MakeContextCurrent()
** No longer affects: mesa -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1758287 Title: totem crashed with SIGTRAP in __glXSendError() from MakeContextCurrent() To manage notifications about this bug go to: https://bugs.launchpad.net/gstreamer/+bug/1758287/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1758287] Re: totem crashed with SIGTRAP in __glXSendError() from MakeContextCurrent()
https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/143
** Bug watch added: gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues #143
https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/143
** Description changed:
- https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/153
+ https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/153
(DUPLICATE OF
https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/143 )
https://bugs.freedesktop.org/show_bug.cgi?id=110452 (RESOLVED NOTOURBUG)
https://errors.ubuntu.com/problem/c7d8b2eb8ea371781ada6f2182d6926557d2fa91
---
Backtrace goes through:
totem -> clutter-gst (frame update) -> cogl (pipeline free) -> gstreamer
(buffer free) -> gstreamer-vaapi (destroy objects) -> Nvidia libglvd
(CommonMakeCurrent / InternalMakeCurrentVendor) -> Mesa GLX
(MakeContextCurrent) -> Xlib (XError)
Ubuntu bug doesn't say anything about what's the use-case / when this
happens and whether it's reproducible (is it e.g. timing related), it
seems just some random crash that Apport collects.
In the backtrace Mesa MakeContextCurrent() calls __glXSendError() to tell
that it was given invalid/bad context. Corresponding Mesa code:
---
if (gc) {
/* Attempt to bind the context. We do this before mucking with
* gc and __glXSetCurrentContext to properly handle our state in
* case of an error.
*
* If an error occurs, set the Null context since we've already
* blown away our old context. The caller is responsible for
* figuring out how to handle setting a valid context.
*/
if (gc->vtable->bind(gc, oldGC, draw, read) != Success) {
__glXSetCurrentContextNull();
__glXUnlock();
__glXSendError(dpy, GLXBadContext, None, X_GLXMakeContextCurrent,
False);
return GL_FALSE;
}
---
I.e. bug is in what is given to Mesa, not what Mesa does.
-> NOTOURBUG
To me it looks something that could happen when Totem is exiting, gst-
vaapi is trying to use resources that have already been freed, and X
catching that when Gstreamer gstvaapitexture_glx.c::destroy_objects()
ask libglvnd to do CommonMakeCurrent().
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: totem 3.26.0-0ubuntu5
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar 23 11:26:51 2018
ExecutablePath: /usr/bin/totem
InstallationDate: Installed on 2017-05-04 (323 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170503)
ProcCmdline: /usr/bin/totem --gapplication-service
Signal: 5
SourcePackage: totem
StacktraceTop:
?? () from /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0
?? () from /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0
?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0
?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0
?? () from /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstvaapi.so
Title: totem crashed with signal 5
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
** No longer affects: gstreamer
** Also affects: totem via
https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/143
Importance: Unknown
Status: Unknown
** Description changed:
- https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/153
(DUPLICATE OF
https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/143 )
+ https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/153 DUPLICATE
OF:
+ https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/143
+
https://bugs.freedesktop.org/show_bug.cgi?id=110452 (RESOLVED NOTOURBUG)
https://errors.ubuntu.com/problem/c7d8b2eb8ea371781ada6f2182d6926557d2fa91
---
Backtrace goes through:
totem -> clutter-gst (frame update) -> cogl (pipeline free) -> gstreamer
(buffer free) -> gstreamer-vaapi (destroy objects) -> Nvidia libglvd
(CommonMakeCurrent / InternalMakeCurrentVendor) -> Mesa GLX
(MakeContextCurrent) -> Xlib (XError)
Ubuntu bug doesn't say anything about what's the use-case / when this
happens and whether it's reproducible (is it e.g. timing related), it
seems just some random crash that Apport collects.
In the backtrace Mesa MakeContextCurrent() calls __glXSendError() to tell
that it was given invalid/bad context. Corresponding Mesa code:
---
if (gc) {
/* Attempt to bind the context. We do this before mucking with
* gc and __glXSetCurrentContext to properly handle our state in
* case of an error.
*
* If an error occurs, set the Null context since we've already
[Bug 1758287] Re: totem crashed with SIGTRAP in __glXSendError() from MakeContextCurrent()
** Project changed: totem => gstreamer -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1758287 Title: totem crashed with SIGTRAP in __glXSendError() from MakeContextCurrent() To manage notifications about this bug go to: https://bugs.launchpad.net/gstreamer/+bug/1758287/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1825449] Re: org.gnome.Shell.desktop[1779]: == Stack trace for context 0x55635b5da210 ==
** Attachment added: "$ journalctl -b" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1825449/+attachment/5256863/+files/journalctl_-b.txt ** Description changed: - $ journalctl -f - abr 18 20:03:18 localhost gnome-shell[1779]: Object Gio.Settings (0x5563611f1ba0), has been already deallocated — impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. - abr 18 20:03:18 localhost org.gnome.Shell.desktop[1779]: == Stack trace for context 0x55635b5da210 == - abr 18 20:03:18 localhost org.gnome.Shell.desktop[1779]: #0 55635d2d6848 i resource:///org/gnome/shell/ui/messageTray.js:195 (7f76fa393e50 @ 22) - abr 18 20:03:18 localhost org.gnome.Shell.desktop[1779]: #1 55635d2d67a8 i resource:///org/gnome/shell/ui/messageTray.js:802 (7f76fa3a3430 @ 28) - abr 18 20:03:18 localhost org.gnome.Shell.desktop[1779]: #2 55635d2d6710 i resource:///org/gnome/shell/ui/windowAttentionHandler.js:79 (7f76fa0875e0 @ 62) - abr 18 20:03:18 localhost org.gnome.Shell.desktop[1779]: #3 7ffeef8a4b60 b self-hosted:979 (7f76fa350c10 @ 440) - abr 18 20:03:18 localhost org.gnome.Shell.desktop[1779]: #4 55635d2d6680 i resource:///org/gnome/shell/ui/messageTray.js:121 (7f76fa393700 @ 71) - abr 18 20:03:18 localhost org.gnome.Shell.desktop[1779]: #5 55635d2d65d8 i resource:///org/gnome/shell/ui/messageTray.js:1408 (7f76fa3a4dc0 @ 22) - abr 18 20:03:18 localhost org.gnome.Shell.desktop[1779]: #6 55635d2d6520 i resource:///org/gnome/shell/ui/messageTray.js:1237 (7f76fa3a4700 @ 729) - abr 18 20:03:18 localhost org.gnome.Shell.desktop[1779]: #7 55635d2d6488 i resource:///org/gnome/shell/ui/messageTray.js:1055 (7f76fa3a4280 @ 124) - abr 18 20:03:18 localhost org.gnome.Shell.desktop[1779]: #8 7ffeef8a8630 b self-hosted:979 (7f76fa350c10 @ 440) - abr 18 20:03:18 localhost org.gnome.Shell.desktop[1779]: #9 7ffeef8a8720 b resource:///org/gnome/gjs/modules/signals.js:128 (7f76fa7cb820 @ 386) - abr 18 20:03:18 localhost org.gnome.Shell.desktop[1779]: #10 55635d2d63f8 i resource:///org/gnome/shell/ui/messageTray.js:479 (7f76fa3a0e50 @ 50) - abr 18 20:03:18 localhost org.gnome.Shell.desktop[1779]: #11 55635d2d6358 i resource:///org/gnome/shell/ui/messageTray.js:808 (7f76fa3a3430 @ 99) - abr 18 20:03:18 localhost org.gnome.Shell.desktop[1779]: #12 55635d2d62c8 i resource:///org/gnome/shell/ui/windowAttentionHandler.js:69 (7f76fa0874c0 @ 13) - abr 18 20:03:18 localhost org.gnome.Shell.desktop[1779]: #13 55635d2d6220 i resource:///org/gnome/shell/ui/main.js:577 (7f76fa7d9a60 @ 216) - abr 18 20:03:18 localhost org.gnome.Shell.desktop[1779]: #14 55635d2d6170 i resource:///org/gnome/shell/ui/windowAttentionHandler.js:103 (7f76fa087820 @ 27) - abr 18 20:03:18 localhost org.gnome.Shell.desktop[1779]: #15 55635d2d60f8 i resource:///org/gnome/shell/ui/windowAttentionHandler.js:43 (7f76fa087310 @ 17) - abr 18 20:03:18 localhost org.gnome.Shell.desktop[1779]: #16 7ffeef8ac2e0 b resource:///org/gnome/gjs/modules/signals.js:128 (7f76fa7cb820 @ 386) - abr 18 20:03:18 localhost org.gnome.Shell.desktop[1779]: #17 55635d2d6070 i resource:///org/gnome/shell/ui/messageTray.js:471 (7f76fa3a0dc0 @ 22) - abr 18 20:03:18 localhost org.gnome.Shell.desktop[1779]: #18 55635d2d5ff0 i resource:///org/gnome/shell/ui/calendar.js:752 (7f76fa3ad310 @ 22) - abr 18 20:03:18 localhost org.gnome.Shell.desktop[1779]: #19 7ffeef8ad920 b self-hosted:979 (7f76fa350c10 @ 440) - abr 18 20:03:18 localhost gnome-shell[1779]: g_object_run_dispose: assertion 'G_IS_OBJECT (object)' failed + gnome-shell[1779]: Object Gio.Settings (0x5563611f1ba0), has been + already deallocated — impossible to access it. This might be caused by + the object having been destroyed from C code using something such as + destroy(), dispose(), or remove() vfuncs. + + == Stack trace for context 0x55635b5da210 == + org.gnome.Shell.desktop[1779]: #0 55635d2d6848 i resource:///org/gnome/shell/ui/messageTray.js:195 (7f76fa393e50 @ 22) + + [...] ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.0+git20190410-1ubuntu1 Uname: Linux 5.1.0-050100rc5-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 18 21:00:01 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-12-02 (137 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2018-12-02 (137 days ago) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1825449 Title: org.gnome.Shell.desktop[1779]: == Stack trace for context 0x55635b5da210 == To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu
[Bug 1825449] [NEW] org.gnome.Shell.desktop[1779]: == Stack trace for context 0x55635b5da210 ==
Public bug reported: gnome-shell[1779]: Object Gio.Settings (0x5563611f1ba0), has been already deallocated — impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. == Stack trace for context 0x55635b5da210 == org.gnome.Shell.desktop[1779]: #0 55635d2d6848 i resource:///org/gnome/shell/ui/messageTray.js:195 (7f76fa393e50 @ 22) [...] ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.0+git20190410-1ubuntu1 Uname: Linux 5.1.0-050100rc5-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 18 21:00:01 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-12-02 (137 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2018-12-02 (137 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco third-party-packages wayland-session -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1825449 Title: org.gnome.Shell.desktop[1779]: == Stack trace for context 0x55635b5da210 == To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1825449/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1825574] [NEW] Can not handle device
Public bug reported: [Impact] A device that is manipulated through the graphical interface appears. But nothing can be done. [Test Case] 1. Open gnome-control-center 2. Then go to 'Power' 3. The device appears Review attached image. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-control-center 1:3.32.1-1ubuntu4 Uname: Linux 5.1.0-050100rc5-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 19 16:29:23 2019 InstallationDate: Installed on 2018-12-02 (138 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to disco on 2018-12-02 (138 days ago) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco third-party-packages wayland-session ** Attachment added: "Captura de pantalla de 2019-04-19 16-29-49.png" https://bugs.launchpad.net/bugs/1825574/+attachment/5257128/+files/Captura%20de%20pantalla%20de%202019-04-19%2016-29-49.png ** Summary changed: - Can not handle device information + Can not handle device -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1825574 Title: Can not handle device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1825574/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1827154] Re: gnome-control-center crashed with SIGSEGV in _gdk_event_queue_handle_motion_compression()
https://gitlab.gnome.org/GNOME/gnome-control-center/issues/503 ** Also affects: gnome-control-center via https://gitlab.gnome.org/GNOME/gnome-control-center/issues/503 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1827154 Title: gnome-control-center crashed with SIGSEGV in _gdk_event_queue_handle_motion_compression() To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1827154/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1827154] [NEW] gnome-control-center crashed with SIGSEGV in _gdk_event_queue_handle_motion_compression()
Public bug reported: https://gitlab.gnome.org/GNOME/gnome-control-center/issues/503 --- [Impact] When I try to set the pen on my touch screen. gnome-control-center crashes. [Fix] That you can configure the pencil to later occupy it with my touch screen. [Test Case] 1. Open gnome-control-center 2. Click on Wacom tablet 3. Press the buttons of the pencil, touching the screen 4. gnome-control-center crashes ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-control-center 1:3.32.1-1ubuntu5 Uname: Linux 5.1.0-050100rc7-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 30 19:28:42 2019 InstallationDate: Installed on 2018-12-02 (149 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to eoan on 2018-12-02 (149 days ago) ** Affects: gnome-control-center Importance: Unknown Status: Unknown ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan wayland-session ** Attachment added: "BackTrace.txt" https://bugs.launchpad.net/bugs/1827154/+attachment/5260430/+files/BackTrace.txt ** Description changed: + https://gitlab.gnome.org/GNOME/gnome-control-center/issues/503 + + --- + [Impact] When I try to set the pen on my touch screen. gnome-control-center crashes. [Fix] That you can configure the pencil to later occupy it with my touch screen. [Test Case] 1. Open gnome-control-center 2. Click on Wacom tablet 3. Press the buttons of the pencil, touching the screen 4. gnome-control-center crashes ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-control-center 1:3.32.1-1ubuntu5 Uname: Linux 5.1.0-050100rc7-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 30 19:28:42 2019 InstallationDate: Installed on 2018-12-02 (149 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to eoan on 2018-12-02 (149 days ago) ** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/issues #503 https://gitlab.gnome.org/GNOME/gnome-control-center/issues/503 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1827154 Title: gnome-control-center crashed with SIGSEGV in _gdk_event_queue_handle_motion_compression() To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1827154/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1827154] Re: gnome-control-center crashed with SIGSEGV in _gdk_event_queue_handle_motion_compression()
** Also affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1827154 Title: gnome-control-center crashed with SIGSEGV in _gdk_event_queue_handle_motion_compression() To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1827154/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1796606] Re: gnome-shell crashed with SIGSEGV in st_widget_get_theme_node() from BoxPointer::_reposition()
** Description changed: https://gitlab.gnome.org/GNOME/gnome-shell/issues/1018 https://gitlab.gnome.org/GNOME/gnome-shell/issues/804 + --- + [ Impact ] - - GNOME Shell crashes in st_widget_get_theme_node - + - GNOME Shell crashes in st_widget_get_theme_node [ Test Case ] - - No clear test case for this, monitoring errors.ubuntu.com is the only + - No clear test case for this, monitoring errors.ubuntu.com is the only feasible solution - [ Regression Potential ] Shell actors might have wrong theming. The crash will be converted in error trackable through journalctl --- The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.30.0-3ubuntu1, the problem page at https://errors.ubuntu.com/problem/b693e6165eedd2cd0390c2e800ccb28aaca4cd0d contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1796606 Title: gnome-shell crashed with SIGSEGV in st_widget_get_theme_node() from BoxPointer::_reposition() To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1796606/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1829417] [NEW] When I download OI-hipster-gui-20190511.iso 'tracker-miner-f' works a lot
Public bug reported: [Impact] 'tracker-miner-f' works a lot when I download with chrome [Fix] tracker-miner-f work with much less intencity [Test Case] 1. Open Chrome 2. Download http://dlc.openindiana.org/isos/hipster/latest//OI-hipster-gui-20190511.iso 3. Open gnome-terminal and run top 4. While the download of OI-hipster-gui-20190511.iso occurs, 'tracker-miner-f' works constantly and intentionally ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: tracker 2.1.8-2 Uname: Linux 5.1.2-050102-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu May 16 12:47:13 2019 InstallationDate: Installed on 2018-12-02 (164 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: tracker UpgradeStatus: Upgraded to eoan on 2018-12-02 (164 days ago) ** Affects: tracker (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan wayland-session -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1829417 Title: When I download OI-hipster-gui-20190511.iso 'tracker-miner-f' works a lot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1829417/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1726129] Re: nautilus crashed with SIGSEGV in widget_needs_widget_path
** Description changed: + https://errors.ubuntu.com/problem/7c06cf06fd970ce31033f0d775b3adf97559e4ea + + --- + . + ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: nautilus 1:3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Budgie:GNOME Date: Sun Oct 22 15:30:05 2017 ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2017-10-19 (3 days ago) InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Release amd64 (20171017.1) ProcCmdline: nautilus --new-window ProcEnviron: - LANGUAGE=en_US - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + LANGUAGE=en_US + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash SegvAnalysis: - Segfault happened at: 0x7fe0115bd2a4:mov0x380(%rax),%rax - PC (0x7fe0115bd2a4) ok - source "0x380(%rax)" (0x0380) not located in a known VMA region (needed readable region)! - destination "%rax" ok + Segfault happened at: 0x7fe0115bd2a4:mov0x380(%rax),%rax + PC (0x7fe0115bd2a4) ok + source "0x380(%rax)" (0x0380) not located in a known VMA region (needed readable region)! + destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: nautilus StacktraceTop: - ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 - ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 - ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 - ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 - ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 + ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 + ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 + ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 + ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 + ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Title: nautilus crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1726129 Title: nautilus crashed with SIGSEGV in widget_needs_widget_path To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1726129/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1726129] Re: nautilus crashed with SIGSEGV in widget_needs_widget_path
** Tags added: eoan -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1726129 Title: nautilus crashed with SIGSEGV in widget_needs_widget_path To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1726129/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1723181] Re: shotwell crashed with SIGSEGV in g_menu_model_get_n_items()
** Tags added: eoan -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to shotwell in Ubuntu. https://bugs.launchpad.net/bugs/1723181 Title: shotwell crashed with SIGSEGV in g_menu_model_get_n_items() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1723181/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1726129] Re: nautilus crashed with SIGSEGV in widget_needs_widget_path
** Description changed: https://errors.ubuntu.com/problem/7c06cf06fd970ce31033f0d775b3adf97559e4ea - - --- - - . - ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: nautilus 1:3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Budgie:GNOME Date: Sun Oct 22 15:30:05 2017 ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2017-10-19 (3 days ago) InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Release amd64 (20171017.1) ProcCmdline: nautilus --new-window ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7fe0115bd2a4:mov0x380(%rax),%rax PC (0x7fe0115bd2a4) ok source "0x380(%rax)" (0x0380) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: nautilus StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Title: nautilus crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1726129 Title: nautilus crashed with SIGSEGV in widget_needs_widget_path To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1726129/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1774587] Re: nautilus crashes in recent_thread_func -> is_file_valid_recursive -> g_local_file_query_info -> free(): invalid pointer
Thanks for your work! -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1774587 Title: nautilus crashes in recent_thread_func -> is_file_valid_recursive -> g_local_file_query_info -> free(): invalid pointer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1774587/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1774587] Re: nautilus crashes in recent_thread_func -> is_file_valid_recursive -> g_local_file_query_info -> free(): invalid pointer
And bionic? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1774587 Title: nautilus crashes in recent_thread_func -> is_file_valid_recursive -> g_local_file_query_info -> free(): invalid pointer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1774587/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1826918] Re: gnome-shell crashed with SIGSEGV in meta_x11_display_get_xdisplay() from detach_pixmap() from meta_surface_actor_x11_dispose() from g_object_unref() from g_object_unref()
** Tags added: bionic -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1826918 Title: gnome-shell crashed with SIGSEGV in meta_x11_display_get_xdisplay() from detach_pixmap() from meta_surface_actor_x11_dispose() from g_object_unref() from g_object_unref() To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1826918/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1834367] Re: nautilus crashed with SIGSEGV in gtk_places_sidebar_set_drop_targets_visible()
** Information type changed from Private to Public ** Bug watch added: gitlab.gnome.org/GNOME/nautilus/issues #1082 https://gitlab.gnome.org/GNOME/nautilus/issues/1082 ** Also affects: nautilus via https://gitlab.gnome.org/GNOME/nautilus/issues/1082 Importance: Unknown Status: Unknown ** Description changed: + https://gitlab.gnome.org/GNOME/nautilus/issues/1082 + + --- + I was moving movies from one directory to another directory. ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: nautilus 1:3.32.1-1ubuntu1 Uname: Linux 5.1.15-050115-generic x86_64 ApportVersion: 2.20.11-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jun 26 15:49:12 2019 ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2018-12-02 (206 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/nautilus --gapplication-service ProcEnviron: - SHELL=/bin/bash - XDG_RUNTIME_DIR= - PATH=(custom, no user) - LANGUAGE=es_CL:es - LANG=es_CL.UTF-8 + SHELL=/bin/bash + XDG_RUNTIME_DIR= + PATH=(custom, no user) + LANGUAGE=es_CL:es + LANG=es_CL.UTF-8 SegvAnalysis: - Segfault happened at: 0x7f1f91d44914 :mov0xe8(%rdi),%eax - PC (0x7f1f91d44914) ok - source "0xe8(%rdi)" (0x00e8) not located in a known VMA region (needed readable region)! - destination "%eax" ok + Segfault happened at: 0x7f1f91d44914 :mov0xe8(%rdi),%eax + PC (0x7f1f91d44914) ok + source "0xe8(%rdi)" (0x00e8) not located in a known VMA region (needed readable region)! + destination "%eax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: nautilus StacktraceTop: - gtk_places_sidebar_set_drop_targets_visible () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 - () - g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 - () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 - g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 + gtk_places_sidebar_set_drop_targets_visible () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 + () + g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 + () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 + g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: nautilus crashed with SIGSEGV in gtk_places_sidebar_set_drop_targets_visible() UpgradeStatus: Upgraded to eoan on 2018-12-02 (205 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: - + usr_lib_nautilus: -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1834367 Title: nautilus crashed with SIGSEGV in gtk_places_sidebar_set_drop_targets_visible() To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1834367/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1834367] Re: nautilus crashed with SIGSEGV in gtk_places_sidebar_set_drop_targets_visible()
** Description changed: - https://gitlab.gnome.org/GNOME/nautilus/issues/1082 - - --- - - I was moving movies from one directory to another directory. + I was moving movies from one directory to another directory with mouse. ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: nautilus 1:3.32.1-1ubuntu1 Uname: Linux 5.1.15-050115-generic x86_64 ApportVersion: 2.20.11-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jun 26 15:49:12 2019 ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2018-12-02 (206 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/nautilus --gapplication-service ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANGUAGE=es_CL:es LANG=es_CL.UTF-8 SegvAnalysis: Segfault happened at: 0x7f1f91d44914 :mov0xe8(%rdi),%eax PC (0x7f1f91d44914) ok source "0xe8(%rdi)" (0x00e8) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: nautilus StacktraceTop: gtk_places_sidebar_set_drop_targets_visible () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 () g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: nautilus crashed with SIGSEGV in gtk_places_sidebar_set_drop_targets_visible() UpgradeStatus: Upgraded to eoan on 2018-12-02 (205 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: usr_lib_nautilus: -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1834367 Title: nautilus crashed with SIGSEGV in gtk_places_sidebar_set_drop_targets_visible() To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1834367/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1748563] Re: /usr/bin/eog:11:gtk_tree_model_get_valist:gtk_tree_model_get:is_file_in_list_store:is_file_in_list_store_file:file_monitor_changed_cb
** Tags added: eoan -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/1748563 Title: /usr/bin/eog:11:gtk_tree_model_get_valist:gtk_tree_model_get:is_file_in_list_store:is_file_in_list_store_file:file_monitor_changed_cb To manage notifications about this bug go to: https://bugs.launchpad.net/eog/+bug/1748563/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1614143] Re: gedit (11) update_actions_sensitivity → readonly_changed → g_closure_invoke → signal_emit_unlocked_R → g_signal_emit_valist
** Tags added: eoan -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1614143 Title: gedit (11) update_actions_sensitivity → readonly_changed → g_closure_invoke → signal_emit_unlocked_R → g_signal_emit_valist To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/1614143/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1726129] Re: nautilus crashed with SIGSEGV in widget_needs_widget_path
This still happens in eoan. ** Changed in: nautilus (Ubuntu) Status: Expired => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1726129 Title: nautilus crashed with SIGSEGV in widget_needs_widget_path To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1726129/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1836070] Re: seahorse crashed with signal 5
** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to seahorse in Ubuntu. https://bugs.launchpad.net/bugs/1836070 Title: seahorse crashed with signal 5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1836070/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1603324] Re: file-roller crashed with SIGSEGV in confirmation_dialog_response()
** Tags added: eoan -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/1603324 Title: file-roller crashed with SIGSEGV in confirmation_dialog_response() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1603324/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1837546] Re: totem assert failure: totem: gen9_mfd.c:649: gen9_hcpd_get_reference_picture_frame_id: La declaración `0' no se cumple.
** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1837546 Title: totem assert failure: totem: gen9_mfd.c:649: gen9_hcpd_get_reference_picture_frame_id: La declaración `0' no se cumple. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1837546/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1832869] Re: gnome-shell crashed with SIGSEGV in g_hash_table_iter_next → meta_display_list_windows → meta_workspace_list_windows → ffi_call_SYSV → ffi_call()
** Tags added: eoan -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1832869 Title: gnome-shell crashed with SIGSEGV in g_hash_table_iter_next → meta_display_list_windows → meta_workspace_list_windows → ffi_call_SYSV → ffi_call() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1832869/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1839211] [NEW] Upgrade to 2.2.1-1(Debian)
Public bug reported: I am testing gnome-music [0]night, and request tracker version 2.2.0 or higher. [0] https://wiki.gnome.org/Apps/Music/Resources ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: tracker 2.1.8-2 Uname: Linux 5.2.6-050206-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 6 16:10:43 2019 InstallationDate: Installed on 2018-12-02 (247 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: tracker UpgradeStatus: Upgraded to eoan on 2018-12-02 (247 days ago) ** Affects: tracker (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan upgrade-software-version wayland-session ** Description changed: - I am testing gnome-music night, and request tracker version 2.2.0 or - higher. + I am testing gnome-music [0]night, and request tracker version 2.2.0 or higher. + [0] https://wiki.gnome.org/Apps/Music/Resources ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: tracker 2.1.8-2 Uname: Linux 5.2.6-050206-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 6 16:10:43 2019 InstallationDate: Installed on 2018-12-02 (247 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: tracker UpgradeStatus: Upgraded to eoan on 2018-12-02 (247 days ago) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1839211 Title: Upgrade to 2.2.1-1(Debian) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1839211/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1726129] Re: nautilus crashed with SIGSEGV in widget_needs_widget_path
** Description changed: + https://gitlab.gnome.org/GNOME/nautilus/issues/1190 + + --- + https://errors.ubuntu.com/problem/7c06cf06fd970ce31033f0d775b3adf97559e4ea ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: nautilus 1:3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Budgie:GNOME Date: Sun Oct 22 15:30:05 2017 ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2017-10-19 (3 days ago) InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Release amd64 (20171017.1) ProcCmdline: nautilus --new-window ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7fe0115bd2a4:mov0x380(%rax),%rax PC (0x7fe0115bd2a4) ok source "0x380(%rax)" (0x0380) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: nautilus StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Title: nautilus crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1726129 Title: nautilus crashed with SIGSEGV in widget_needs_widget_path To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1726129/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1726129] Re: nautilus crashed with SIGSEGV in widget_needs_widget_path
** Bug watch added: gitlab.gnome.org/GNOME/nautilus/issues #1190 https://gitlab.gnome.org/GNOME/nautilus/issues/1190 ** Also affects: nautilus via https://gitlab.gnome.org/GNOME/nautilus/issues/1190 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1726129 Title: nautilus crashed with SIGSEGV in widget_needs_widget_path To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1726129/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1726129] Re: nautilus crashed with SIGSEGV in widget_needs_widget_path
** Also affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1726129 Title: nautilus crashed with SIGSEGV in widget_needs_widget_path To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1726129/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1839782] Re: totem crashed with SIGABRT
*** This bug is a duplicate of bug 1501049 *** https://bugs.launchpad.net/bugs/1501049 ** Description changed: $ LANGUAGE=C totem Click 'Channels' - Click 'MyCloudEX2Ultra' + Click 'ServerDLNA' Click 'Photos' Click 'All Photos' In console: ** Totem:ERROR:../src/totem-grilo.c:703:browse_cb: code should not be reached Bail out! Totem:ERROR:../src/totem-grilo.c:703:browse_cb: code should not be reached Abortado (`core' generado) ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: totem 3.33.90-2ubuntu1 Uname: Linux 5.2.8-050208-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Sun Aug 11 16:06:29 2019 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2018-12-02 (252 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: totem Signal: 6 SourcePackage: totem StacktraceTop: - () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 - g_assertion_message_expr () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 - () at /usr/lib/x86_64-linux-gnu/libtotem.so.0 - () at /usr/lib/x86_64-linux-gnu/libgrilo-0.3.so.0 - g_main_context_dispatch () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 + () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 + g_assertion_message_expr () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 + () at /usr/lib/x86_64-linux-gnu/libtotem.so.0 + () at /usr/lib/x86_64-linux-gnu/libgrilo-0.3.so.0 + g_main_context_dispatch () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: totem crashed with SIGABRT UpgradeStatus: Upgraded to eoan on 2018-12-02 (252 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1839782 Title: totem crashed with SIGABRT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1839782/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1501049] Re: totem crashed with assertion failure [Totem:ERROR:totem-grilo.c:729:browse_cb: code should not be reached]
** Description changed: https://errors.ubuntu.com/problem/49f61eb5b4c7c242dac2179ff053a937285c37ce --- the gnome video application crashed twice while attempting to browse a upnp media server. at first I tried to play a video which failed to play, then twice afterwards the application crashed before it would even load the file list + + --- + + $ LANGUAGE=C totem + Click 'Channels' + Click 'ServerDLNA' + Click 'Photos' + Click 'All Photos' + + In console: + ** + Totem:ERROR:../src/totem-grilo.c:703:browse_cb: code should not be reached + Bail out! Totem:ERROR:../src/totem-grilo.c:703:browse_cb: code should not be reached + Abortado (`core' generado) ProblemType: Crash DistroRelease: Ubuntu 15.10 Package: totem 3.16.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-11.13-generic 4.2.1 Uname: Linux 4.2.0-11-generic x86_64 ApportVersion: 2.19-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Sep 29 16:31:47 2015 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2015-09-28 (0 days ago) InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150825) ProcCmdline: /usr/bin/totem --gapplication-service ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_US.UTF-8 Signal: 6 SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1501049 Title: totem crashed with assertion failure [Totem:ERROR:totem- grilo.c:729:browse_cb: code should not be reached] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1501049/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1501049] Re: totem crashed with assertion failure [Totem:ERROR:totem-grilo.c:729:browse_cb: code should not be reached]
** Description changed: https://errors.ubuntu.com/problem/49f61eb5b4c7c242dac2179ff053a937285c37ce --- the gnome video application crashed twice while attempting to browse a upnp media server. at first I tried to play a video which failed to play, then twice afterwards the application crashed before it would even load the file list --- $ LANGUAGE=C totem Click 'Channels' - Click 'ServerDLNA' + Click 'DLNAServer' Click 'Photos' Click 'All Photos' In console: ** Totem:ERROR:../src/totem-grilo.c:703:browse_cb: code should not be reached Bail out! Totem:ERROR:../src/totem-grilo.c:703:browse_cb: code should not be reached Abortado (`core' generado) ProblemType: Crash DistroRelease: Ubuntu 15.10 Package: totem 3.16.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-11.13-generic 4.2.1 Uname: Linux 4.2.0-11-generic x86_64 ApportVersion: 2.19-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Sep 29 16:31:47 2015 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2015-09-28 (0 days ago) InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150825) ProcCmdline: /usr/bin/totem --gapplication-service ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_US.UTF-8 Signal: 6 SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo ** Description changed: https://errors.ubuntu.com/problem/49f61eb5b4c7c242dac2179ff053a937285c37ce --- the gnome video application crashed twice while attempting to browse a upnp media server. at first I tried to play a video which failed to play, then twice afterwards the application crashed before it would even load the file list --- $ LANGUAGE=C totem Click 'Channels' - Click 'DLNAServer' + Click 'DLNA-Server' Click 'Photos' Click 'All Photos' In console: ** Totem:ERROR:../src/totem-grilo.c:703:browse_cb: code should not be reached Bail out! Totem:ERROR:../src/totem-grilo.c:703:browse_cb: code should not be reached Abortado (`core' generado) ProblemType: Crash DistroRelease: Ubuntu 15.10 Package: totem 3.16.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-11.13-generic 4.2.1 Uname: Linux 4.2.0-11-generic x86_64 ApportVersion: 2.19-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Sep 29 16:31:47 2015 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2015-09-28 (0 days ago) InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150825) ProcCmdline: /usr/bin/totem --gapplication-service ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_US.UTF-8 Signal: 6 SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1501049 Title: totem crashed with assertion failure [Totem:ERROR:totem- grilo.c:729:browse_cb: code should not be reached] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1501049/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1840996] Re: Working with smb
Add: https://gitlab.gnome.org/GNOME/nautilus/issues/1201 ** Information type changed from Private to Public ** Description changed: + https://gitlab.gnome.org/GNOME/nautilus/issues/1201 + + --- + I opened nautilus, accessed a shared resource with samba. Then I tried to write in that mounted folder. And he threw me that he had no writing privileges. I went to the samba server configuration and increased the privileges. And I tried to write *without* closing nautilus. It was something similar to what I mention. ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: nautilus 1:3.33.90-1ubuntu1 Uname: Linux 5.2.9-050209-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Aug 21 19:25:59 2019 ExecutablePath: /usr/bin/nautilus ExecutableTimestamp: 1565361020 GsettingsChanges: b'org.gnome.nautilus.window-state' b'maximized' b'true' InstallationDate: Installed on 2018-12-02 (262 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/nautilus --gapplication-service ProcCwd: /home/caravena ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANGUAGE=es_CL:es LANG=es_CL.UTF-8 Signal: 6 SourcePackage: nautilus UpgradeStatus: Upgraded to eoan on 2018-12-02 (262 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo usr_lib_nautilus: ** Bug watch added: gitlab.gnome.org/GNOME/nautilus/issues #1201 https://gitlab.gnome.org/GNOME/nautilus/issues/1201 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1840996 Title: Working with smb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1840996/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1840996] Re: Working with Samba
** Summary changed: - Working with smb + Working with Samba ** Also affects: nautilus via https://gitlab.gnome.org/GNOME/nautilus/issues/1201 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1840996 Title: Working with Samba To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1840996/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1843467] Re: nautilus crashed with SIGSEGV in NAUTILUS_VIEW_GET_IFACE()
https://gitlab.gnome.org/GNOME/nautilus/issues/1216 ** Information type changed from Private to Public ** Description changed: + https://gitlab.gnome.org/GNOME/nautilus/issues/1216 + + --- + I opened nautilus to see my files from my account u...@gmail.com. And before it loaded, I pressed the magnifying glass. After all this, nautilus crash. ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: nautilus 1:3.33.90-1ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Sep 10 14:44:44 2019 ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2018-12-02 (282 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/nautilus --gapplication-service ProcEnviron: - SHELL=/bin/bash - XDG_RUNTIME_DIR= - PATH=(custom, no user) - LANGUAGE=es_CL:es - LANG=es_CL.UTF-8 + SHELL=/bin/bash + XDG_RUNTIME_DIR= + PATH=(custom, no user) + LANGUAGE=es_CL:es + LANG=es_CL.UTF-8 SegvAnalysis: - Segfault happened at: 0x55ae33b30b2d : mov0x0(%rbp),%rdi - PC (0x55ae33b30b2d) ok - source "0x0(%rbp)" (0x) not located in a known VMA region (needed readable region)! - destination "%rdi" ok + Segfault happened at: 0x55ae33b30b2d : mov0x0(%rbp),%rdi + PC (0x55ae33b30b2d) ok + source "0x0(%rbp)" (0x) not located in a known VMA region (needed readable region)! + destination "%rdi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: nautilus StacktraceTop: - nautilus_view_is_searching () - () - g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 - () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 - g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 + nautilus_view_is_searching () + () + g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 + () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 + g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: nautilus crashed with SIGSEGV in nautilus_view_is_searching() UpgradeStatus: Upgraded to eoan on 2018-12-02 (281 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: - + usr_lib_nautilus: ** Bug watch added: gitlab.gnome.org/GNOME/nautilus/issues #1216 https://gitlab.gnome.org/GNOME/nautilus/issues/1216 ** Also affects: nautilus via https://gitlab.gnome.org/GNOME/nautilus/issues/1216 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1843467 Title: nautilus crashed with SIGSEGV in NAUTILUS_VIEW_GET_IFACE() To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1843467/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1843627] Re: evolution-calendar-factory crashed with SIGSEGV in tcache_get()
https://gitlab.gnome.org/GNOME/evolution/issues/616 ** Information type changed from Private to Public ** Description changed: + https://gitlab.gnome.org/GNOME/evolution/issues/616 + + --- + I don't know what happened. ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: evolution-data-server 3.33.91-3 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Wed Sep 11 13:41:26 2019 ExecutablePath: /usr/libexec/evolution-calendar-factory InstallationDate: Installed on 2018-12-02 (282 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/libexec/evolution-calendar-factory ProcEnviron: - LANG=es_CL.UTF-8 - LANGUAGE=es_CL:es - PATH=(custom, no user) - SHELL=/bin/bash - XDG_RUNTIME_DIR= + LANG=es_CL.UTF-8 + LANGUAGE=es_CL:es + PATH=(custom, no user) + SHELL=/bin/bash + XDG_RUNTIME_DIR= SegvAnalysis: - Segfault happened at: 0x7f36355653ae <__GI___libc_malloc+286>: mov (%r8),%rsi - PC (0x7f36355653ae) ok - source "(%r8)" (0x7f36) not located in a known VMA region (needed readable region)! - destination "%rsi" ok - Stack memory exhausted (SP below stack segment) + Segfault happened at: 0x7f36355653ae <__GI___libc_malloc+286>: mov (%r8),%rsi + PC (0x7f36355653ae) ok + source "(%r8)" (0x7f36) not located in a known VMA region (needed readable region)! + destination "%rsi" ok + Stack memory exhausted (SP below stack segment) SegvReason: reading unknown VMA Signal: 11 SourcePackage: evolution-data-server StacktraceTop: - tcache_get (tc_idx=) at malloc.c:2937 - __GI___libc_malloc (bytes=32) at malloc.c:3051 - g_malloc () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 - g_datalist_id_set_data_full () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 - () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 + tcache_get (tc_idx=) at malloc.c:2937 + __GI___libc_malloc (bytes=32) at malloc.c:3051 + g_malloc () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 + g_datalist_id_set_data_full () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 + () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: evolution-calendar-factory crashed with SIGSEGV in tcache_get() UpgradeStatus: Upgraded to eoan on 2018-12-02 (282 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: ** Bug watch added: gitlab.gnome.org/GNOME/evolution/issues #616 https://gitlab.gnome.org/GNOME/evolution/issues/616 ** Also affects: evolution-data-server via https://gitlab.gnome.org/GNOME/evolution/issues/616 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1843627 Title: evolution-calendar-factory crashed with SIGSEGV in tcache_get() To manage notifications about this bug go to: https://bugs.launchpad.net/evolution-data-server/+bug/1843627/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1843698] Re: gnome-software crashed with SIGSEGV in __memmove_avx_unaligned_erms()
https://gitlab.gnome.org/GNOME/gnome-software/issues/792 ** Information type changed from Private to Public ** Description changed: + https://gitlab.gnome.org/GNOME/gnome-software/issues/792 + + --- + I do not know what happened. ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: gnome-software 3.30.6-2ubuntu10 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Sep 12 07:57:24 2019 ExecutablePath: /usr/bin/gnome-software InstallationDate: Installed on 2018-12-02 (283 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) InstalledPlugins: - gnome-software-plugin-flatpak 3.30.6-2ubuntu10 - gnome-software-plugin-snap3.30.6-2ubuntu10 + gnome-software-plugin-flatpak 3.30.6-2ubuntu10 + gnome-software-plugin-snap3.30.6-2ubuntu10 ProcCmdline: /usr/bin/gnome-software --gapplication-service ProcEnviron: - LANG=es_CL.UTF-8 - LANGUAGE=es_CL:es - PATH=(custom, no user) - SHELL=/bin/bash - XDG_RUNTIME_DIR= + LANG=es_CL.UTF-8 + LANGUAGE=es_CL:es + PATH=(custom, no user) + SHELL=/bin/bash + XDG_RUNTIME_DIR= SegvAnalysis: - Segfault happened at: 0x7f565aa3fcc4 <__memmove_avx_unaligned_erms+372>: vmovdqu -0x20(%rsi,%rdx,1),%ymm5 - PC (0x7f565aa3fcc4) ok - source "-0x20(%rsi,%rdx,1)" (0x7f5e4c1bab30) not located in a known VMA region (needed readable region)! - destination "%ymm5" ok - Stack memory exhausted (SP below stack segment) + Segfault happened at: 0x7f565aa3fcc4 <__memmove_avx_unaligned_erms+372>: vmovdqu -0x20(%rsi,%rdx,1),%ymm5 + PC (0x7f565aa3fcc4) ok + source "-0x20(%rsi,%rdx,1)" (0x7f5e4c1bab30) not located in a known VMA region (needed readable region)! + destination "%ymm5" ok + Stack memory exhausted (SP below stack segment) SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnome-software StacktraceTop: - __memmove_avx_unaligned_erms () at ../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:384 - g_ptr_array_remove_range () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 - g_ptr_array_set_size () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 - as_store_remove_all () at /usr/lib/x86_64-linux-gnu/libappstream-glib.so.8 - () at /usr/lib/x86_64-linux-gnu/gs-plugins-12/libgs_plugin_flatpak.so + __memmove_avx_unaligned_erms () at ../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:384 + g_ptr_array_remove_range () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 + g_ptr_array_set_size () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 + as_store_remove_all () at /usr/lib/x86_64-linux-gnu/libappstream-glib.so.8 + () at /usr/lib/x86_64-linux-gnu/gs-plugins-12/libgs_plugin_flatpak.so Title: gnome-software crashed with SIGSEGV in __memmove_avx_unaligned_erms() UpgradeStatus: Upgraded to eoan on 2018-12-02 (283 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: ** Bug watch added: gitlab.gnome.org/GNOME/gnome-software/issues #792 https://gitlab.gnome.org/GNOME/gnome-software/issues/792 ** Also affects: gnome-software via https://gitlab.gnome.org/GNOME/gnome-software/issues/792 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1843698 Title: gnome-software crashed with SIGSEGV in __memmove_avx_unaligned_erms() To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1843698/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1843703] Re: gnome-shell crashed with SIGSEGV in async_get_property_finish()
https://gitlab.gnome.org/GNOME/gnome-shell/issues/1599 ** Description changed: + https://gitlab.gnome.org/GNOME/gnome-shell/issues/1599 + + --- + I have proposed to the list of package updates. Selecting some packages to update from there. After restarting, he does not log in and he votes me for the session. Then I try again and I can enter. ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Thu Sep 12 08:56:37 2019 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2018-12-02 (283 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: - LANG=es_CL.UTF-8 - LANGUAGE=es_CL:es - PATH=(custom, no user) - SHELL=/bin/bash - XDG_RUNTIME_DIR= + LANG=es_CL.UTF-8 + LANGUAGE=es_CL:es + PATH=(custom, no user) + SHELL=/bin/bash + XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.34.0-1ubuntu1 Signal: 11 SourcePackage: gnome-shell StacktraceTop: - __GI_raise (sig=) at ../sysdeps/unix/sysv/linux/raise.c:50 - () - () at /lib/x86_64-linux-gnu/libc.so.6 - () at /usr/lib/x86_64-linux-gnu/libmutter-5.so.0 - () at /usr/lib/x86_64-linux-gnu/libmutter-5.so.0 + __GI_raise (sig=) at ../sysdeps/unix/sysv/linux/raise.c:50 + () + () at /lib/x86_64-linux-gnu/libc.so.6 + () at /usr/lib/x86_64-linux-gnu/libmutter-5.so.0 + () at /usr/lib/x86_64-linux-gnu/libmutter-5.so.0 Title: gnome-shell crashed with SIGSEGV in __GI_raise() UpgradeStatus: Upgraded to eoan on 2018-12-02 (283 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #1599 https://gitlab.gnome.org/GNOME/gnome-shell/issues/1599 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/issues/1599 Importance: Unknown Status: Unknown ** Description changed: https://gitlab.gnome.org/GNOME/gnome-shell/issues/1599 --- I have proposed to the list of package updates. Selecting some packages to update from there. After restarting, he does not log in and he votes me for the session. Then I try again and I can enter. + + Also crashed _usr_lib_gnome-session_gnome-session-binary.1000 ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Thu Sep 12 08:56:37 2019 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2018-12-02 (283 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=es_CL.UTF-8 LANGUAGE=es_CL:es PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.34.0-1ubuntu1 Signal: 11 SourcePackage: gnome-shell StacktraceTop: __GI_raise (sig=) at ../sysdeps/unix/sysv/linux/raise.c:50 () () at /lib/x86_64-linux-gnu/libc.so.6 () at /usr/lib/x86_64-linux-gnu/libmutter-5.so.0 () at /usr/lib/x86_64-linux-gnu/libmutter-5.so.0 Title: gnome-shell crashed with SIGSEGV in __GI_raise() UpgradeStatus: Upgraded to eoan on 2018-12-02 (283 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: ** No longer affects: gnome-shell ** Bug watch added: gitlab.gnome.org/GNOME/mutter/issues #780 https://gitlab.gnome.org/GNOME/mutter/issues/780 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/mutter/issues/780 Importance: Unknown Status: Unknown ** Description changed: - https://gitlab.gnome.org/GNOME/gnome-shell/issues/1599 + https://gitlab.gnome.org/GNOME/mutter/issues/780 --- I have proposed to the list of package updates. Selecting some packages to update from there. After restarting, he does not log in and he votes me for the session. Then I try again and I can enter. Also crashed _usr_lib_gnome-session_gnome-session-binary.1000 ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Thu Sep 12 08:56:37 2019 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2018-12-02 (283 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/gno
[Bug 1867905] Re: Sound output volume controls not showing in menu
*** This bug is a duplicate of bug 1865169 *** https://bugs.launchpad.net/bugs/1865169 ** This bug has been marked a duplicate of bug 1865169 volume and light not working in Gnome Shell 3.35 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1867905 Title: Sound output volume controls not showing in menu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1867905/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1868999] Re: Characters in the web browser do not work
** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1868999 Title: Characters in the web browser do not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1868999/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1868999] Re: Characters in the web browser do not work
Good morning, I just rebooted with the kernel: 5.4.0-18-generic And everything works perfectly. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1868999 Title: Characters in the web browser do not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1868999/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1868999] Re: Characters in the web browser do not work
How strange, I just rebooted and selected my 5.6.0-050600rc7-generic and tried Xorg and Xwayland and everything works fine again. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1868999 Title: Characters in the web browser do not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1868999/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1868999] Re: Characters in the web browser do not work
** Changed in: gnome-shell (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1868999 Title: Characters in the web browser do not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1868999/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1868999] Re: Characters in the web browser do not work
@Olivier, This morning it happened again. I had to restart three times. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1868999 Title: Characters in the web browser do not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1868999/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1869404] Re: nautilus crashed with SIGABRT
https://gitlab.gnome.org/GNOME/nautilus/-/issues/1426 ** Information type changed from Private to Public ** Bug watch added: gitlab.gnome.org/GNOME/nautilus/-/issues #1426 https://gitlab.gnome.org/GNOME/nautilus/-/issues/1426 ** Also affects: nautilus via https://gitlab.gnome.org/GNOME/nautilus/-/issues/1426 Importance: Unknown Status: Unknown ** Description changed: + https://gitlab.gnome.org/GNOME/nautilus/-/issues/1426 + + --- + I was working with: NAS(samba) + nautilus + nautilus search bar in folder of NAS. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.0-1ubuntu1 Uname: Linux 5.6.0-050600rc7-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 27 14:35:37 2020 ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2018-12-02 (480 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/nautilus --gapplication-service ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANGUAGE=es_CL:es LANG=es_CL.UTF-8 Signal: 6 SourcePackage: nautilus StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 () nautilus_window_slot_open_location_full () () at /usr/lib/x86_64-linux-gnu/libffi.so.7 Title: nautilus crashed with SIGABRT UpgradeStatus: Upgraded to focal on 2018-12-02 (480 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: usr_lib_nautilus: -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1869404 Title: nautilus crashed with SIGABRT To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1869404/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1869404] Re: nautilus crashed with SIGABRT
** Description changed: https://gitlab.gnome.org/GNOME/nautilus/-/issues/1426 --- - I was working with: NAS(samba) + nautilus + nautilus search bar in - folder of NAS. + I was working with: NAS(samba) + nautilus search bar in folder of NAS. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.0-1ubuntu1 Uname: Linux 5.6.0-050600rc7-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 27 14:35:37 2020 ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2018-12-02 (480 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/nautilus --gapplication-service ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANGUAGE=es_CL:es LANG=es_CL.UTF-8 Signal: 6 SourcePackage: nautilus StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 () nautilus_window_slot_open_location_full () () at /usr/lib/x86_64-linux-gnu/libffi.so.7 Title: nautilus crashed with SIGABRT UpgradeStatus: Upgraded to focal on 2018-12-02 (480 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: usr_lib_nautilus: -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1869404 Title: nautilus crashed with SIGABRT To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1869404/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1869876] Re: totem crashed with SIGSEGV in g_mount_spec_get()
https://gitlab.gnome.org/GNOME/totem/-/issues/411 ** Information type changed from Private to Public ** Bug watch added: gitlab.gnome.org/GNOME/totem/-/issues #411 https://gitlab.gnome.org/GNOME/totem/-/issues/411 ** Also affects: totem via https://gitlab.gnome.org/GNOME/totem/-/issues/411 Importance: Unknown Status: Unknown ** Description changed: + https://gitlab.gnome.org/GNOME/totem/-/issues/411 + + --- + I don't know how it happened. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: totem 3.34.1-2ubuntu2 Uname: Linux 5.6.0-050600-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 30 19:29:08 2020 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2018-12-02 (484 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/totem --gapplication-service ProcEnviron: - SHELL=/bin/bash - XDG_RUNTIME_DIR= - PATH=(custom, no user) - LANGUAGE=es_CL:es - LANG=es_CL.UTF-8 + SHELL=/bin/bash + XDG_RUNTIME_DIR= + PATH=(custom, no user) + LANGUAGE=es_CL:es + LANG=es_CL.UTF-8 SegvAnalysis: - Segfault happened at: 0x7f981803dd09 : mov (%rbx),%rdi - PC (0x7f981803dd09) ok - source "(%rbx)" (0x7000700070006) not located in a known VMA region (needed readable region)! - destination "%rdi" ok - Stack memory exhausted (SP below stack segment) + Segfault happened at: 0x7f981803dd09 : mov (%rbx),%rdi + PC (0x7f981803dd09) ok + source "(%rbx)" (0x7000700070006) not located in a known VMA region (needed readable region)! + destination "%rdi" ok + Stack memory exhausted (SP below stack segment) SegvReason: reading unknown VMA Signal: 11 SourcePackage: totem StacktraceTop: - g_mount_spec_get () at /usr/lib/x86_64-linux-gnu/gvfs/libgvfscommon.so - () at /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so - () at /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so - () at /usr/lib/x86_64-linux-gnu/libtotem-plparser.so.18 - totem_pl_parser_parse_with_base () at /usr/lib/x86_64-linux-gnu/libtotem-plparser.so.18 + g_mount_spec_get () at /usr/lib/x86_64-linux-gnu/gvfs/libgvfscommon.so + () at /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so + () at /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so + () at /usr/lib/x86_64-linux-gnu/libtotem-plparser.so.18 + totem_pl_parser_parse_with_base () at /usr/lib/x86_64-linux-gnu/libtotem-plparser.so.18 Title: totem crashed with SIGSEGV in g_mount_spec_get() UpgradeStatus: Upgraded to focal on 2018-12-02 (484 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1869876 Title: totem crashed with SIGSEGV in g_mount_spec_get() To manage notifications about this bug go to: https://bugs.launchpad.net/totem/+bug/1869876/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1869876] Re: totem crashed with SIGSEGV in g_mount_spec_get()
*** This bug is a duplicate of bug 1860235 *** https://bugs.launchpad.net/bugs/1860235 ** This bug has been marked a duplicate of bug 1860235 totem crashed with SIGSEGV in g_mount_spec_get() -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1869876 Title: totem crashed with SIGSEGV in g_mount_spec_get() To manage notifications about this bug go to: https://bugs.launchpad.net/totem/+bug/1869876/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1873003] Re: gnome-shell-hotplug-sniffer crashed with SIGSEGV in g_str_hash()
** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1873003 Title: gnome-shell-hotplug-sniffer crashed with SIGSEGV in g_str_hash() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1873003/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1873003] Re: gnome-shell-hotplug-sniffer crashed with SIGSEGV in g_str_hash()
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2643 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #2643 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2643 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2643 Importance: Unknown Status: Unknown ** Description changed: + https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2643 + + --- + I don't know what happened. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 Uname: Linux 5.6.4-050604-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 15 10:11:16 2020 DisplayManager: gdm3 ExecutablePath: /usr/libexec/gnome-shell-hotplug-sniffer InstallationDate: Installed on 2018-12-02 (499 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/libexec/gnome-shell-hotplug-sniffer ProcEnviron: - SHELL=/bin/bash - XDG_RUNTIME_DIR= - PATH=(custom, no user) - LANGUAGE=es_CL:es - LANG=es_CL.UTF-8 + SHELL=/bin/bash + XDG_RUNTIME_DIR= + PATH=(custom, no user) + LANGUAGE=es_CL:es + LANG=es_CL.UTF-8 RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 SegvAnalysis: - Segfault happened at: 0x7f89b635e494 : movsbl (%rdi),%eax - PC (0x7f89b635e494) ok - source "(%rdi)" (0x) not located in a known VMA region (needed readable region)! - destination "%eax" ok + Segfault happened at: 0x7f89b635e494 : movsbl (%rdi),%eax + PC (0x7f89b635e494) ok + source "(%rdi)" (0x) not located in a known VMA region (needed readable region)! + destination "%eax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: - g_str_hash () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 - g_hash_table_lookup () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 - () - () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 - () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 + g_str_hash () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 + g_hash_table_lookup () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 + () + () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 + () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: gnome-shell-hotplug-sniffer crashed with SIGSEGV in g_str_hash() UpgradeStatus: Upgraded to focal on 2018-12-02 (499 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1873003 Title: gnome-shell-hotplug-sniffer crashed with SIGSEGV in g_str_hash() To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1873003/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1874262] [NEW] User session does not start: xkbcomp "Internal error: Could not resolve keysym Invalid"
Public bug reported: https://gitlab.gnome.org/GNOME/gdm/-/issues/593 --- Today I tried to log into my ubuntu session with my personal account through Xorg and Xwayland. And I couldn't, I had to install lightdm and to be able to enter. In my experience, I found this message ($journalctl): Apr 22 09:06:44 romanescu gnome-shell [3651]: The XKEYBOARD keymap compiler (xkbcomp) reports: Apr 22 09:06:44 romanescu gnome-shell [3651]:> Warning: Unsupported maximum keycode 569, clipping. Apr 22 09:06:44 romanescu gnome-shell [3651]:> X11 cannot support keycodes above 255. Apr 22 09:06:44 romanescu gnome-shell [3651]:> Internal error: Could not resolve keysym Invalid Apr 22 09:06:44 romanescu gnome-shell [3651]: Errors from xkbcomp are not fatal to the X server Attached log of the attempt to log in. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gdm3 3.34.1-1ubuntu1 Uname: Linux 5.6.6-050606-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 22 09:54:26 2020 InstallationDate: Installed on 2018-12-02 (506 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "gdm.log" https://bugs.launchpad.net/bugs/1874262/+attachment/5357963/+files/gdm.log ** Summary changed: - User session does not start "Internal error: Could not resolve keysym Invalid" + User session does not start: xkbcomp "Internal error: Could not resolve keysym Invalid" -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1874262 Title: User session does not start: xkbcomp "Internal error: Could not resolve keysym Invalid" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1874262/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1874262] Re: User session does not start: xkbcomp "Internal error: Could not resolve keysym Invalid"
https://gitlab.gnome.org/GNOME/gdm/-/issues/593 ** Description changed: + https://gitlab.gnome.org/GNOME/gdm/-/issues/593 + + --- + Today I tried to log into my ubuntu session with my personal account through Xorg and Xwayland. And I couldn't, I had to install lightdm and to be able to enter. In my experience, I found this message ($journalctl): Apr 22 09:06:44 romanescu gnome-shell [3651]: The XKEYBOARD keymap compiler (xkbcomp) reports: Apr 22 09:06:44 romanescu gnome-shell [3651]:> Warning: Unsupported maximum keycode 569, clipping. Apr 22 09:06:44 romanescu gnome-shell [3651]:> X11 cannot support keycodes above 255. Apr 22 09:06:44 romanescu gnome-shell [3651]:> Internal error: Could not resolve keysym Invalid Apr 22 09:06:44 romanescu gnome-shell [3651]: Errors from xkbcomp are not fatal to the X server Attached log of the attempt to log in. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gdm3 3.34.1-1ubuntu1 Uname: Linux 5.6.6-050606-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 22 09:54:26 2020 InstallationDate: Installed on 2018-12-02 (506 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) ** Bug watch added: gitlab.gnome.org/GNOME/gdm/-/issues #593 https://gitlab.gnome.org/GNOME/gdm/-/issues/593 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1874262 Title: User session does not start: xkbcomp "Internal error: Could not resolve keysym Invalid" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1874262/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1874262] Re: User session does not start: xkbcomp "Internal error: Could not resolve keysym Invalid"
https://gitlab.freedesktop.org/xorg/app/xkbcomp/-/issues/14 ** Also affects: xorg (Ubuntu) Importance: Undecided Status: New ** Changed in: gdm3 (Ubuntu) Status: New => Invalid ** Description changed: + https://gitlab.freedesktop.org/xorg/app/xkbcomp/-/issues/14 https://gitlab.gnome.org/GNOME/gdm/-/issues/593 --- Today I tried to log into my ubuntu session with my personal account through Xorg and Xwayland. And I couldn't, I had to install lightdm and to be able to enter. In my experience, I found this message ($journalctl): Apr 22 09:06:44 romanescu gnome-shell [3651]: The XKEYBOARD keymap compiler (xkbcomp) reports: Apr 22 09:06:44 romanescu gnome-shell [3651]:> Warning: Unsupported maximum keycode 569, clipping. Apr 22 09:06:44 romanescu gnome-shell [3651]:> X11 cannot support keycodes above 255. Apr 22 09:06:44 romanescu gnome-shell [3651]:> Internal error: Could not resolve keysym Invalid Apr 22 09:06:44 romanescu gnome-shell [3651]: Errors from xkbcomp are not fatal to the X server Attached log of the attempt to log in. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gdm3 3.34.1-1ubuntu1 Uname: Linux 5.6.6-050606-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 22 09:54:26 2020 InstallationDate: Installed on 2018-12-02 (506 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) ** Bug watch added: gitlab.freedesktop.org/xorg/app/xkbcomp/-/issues #14 https://gitlab.freedesktop.org/xorg/app/xkbcomp/-/issues/14 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1874262 Title: User session does not start: xkbcomp "Internal error: Could not resolve keysym Invalid" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1874262/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1874262] Re: User session does not start: Problem with chrome-remote-desktop
** Summary changed: - User session does not start: xkbcomp "Internal error: Could not resolve keysym Invalid" + User session does not start: Problem with chrome-remote-desktop -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1874262 Title: User session does not start: Problem with chrome-remote-desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1874262/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1820859] Re: /usr/bin/nautilus:11:g_application_impl_get_dbus_object_path:g_application_get_dbus_object_path:update_dbus_opened_locations:bus_acquired_cb:connection_get_cb
** Tags added: groovy -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1820859 Title: /usr/bin/nautilus:11:g_application_impl_get_dbus_object_path:g_application_get_dbus_object_path:update_dbus_opened_locations:bus_acquired_cb:connection_get_cb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1820859/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1726129] Re: nautilus crashed with SIGSEGV in widget_needs_widget_path
** Tags added: groovy -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1726129 Title: nautilus crashed with SIGSEGV in widget_needs_widget_path To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1726129/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1723181] Re: shotwell crashed with SIGSEGV in g_menu_model_get_n_items()
** Tags added: gro ** Tags removed: gro ** Tags added: groovy -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to shotwell in Ubuntu. https://bugs.launchpad.net/bugs/1723181 Title: shotwell crashed with SIGSEGV in g_menu_model_get_n_items() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1723181/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1865300] Re: gnome-shell-hotplug-sniffer crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup() from deep_count_more_files_callback()
** Tags added: groovy -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1865300 Title: gnome-shell-hotplug-sniffer crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup() from deep_count_more_files_callback() To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1865300/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1880742] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance()
** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1880742 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1880742/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1880742] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance()
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2840 ** Description changed: + https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2840 + + --- + I was working with nautilus, I hit a 'recent' click. ProblemType: Crash DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.36.2-1ubuntu1 Uname: Linux 5.7.0-050700rc7-generic x86_64 ApportVersion: 2.20.11-0ubuntu36 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 26 13:55:31 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2018-12-02 (541 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: - LANG=es_CL.UTF-8 - LANGUAGE=es_CL:es - PATH=(custom, no user) - SHELL=/bin/bash - XDG_RUNTIME_DIR= + LANG=es_CL.UTF-8 + LANGUAGE=es_CL:es + PATH=(custom, no user) + SHELL=/bin/bash + XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1 Signal: 11 SourcePackage: gnome-shell StacktraceTop: - __GI_raise (sig=) at ../sysdeps/unix/sysv/linux/raise.c:50 - () - () at /lib/x86_64-linux-gnu/libc.so.6 - g_type_check_instance () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 - g_signal_connect_data () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 + __GI_raise (sig=) at ../sysdeps/unix/sysv/linux/raise.c:50 + () + () at /lib/x86_64-linux-gnu/libc.so.6 + g_type_check_instance () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 + g_signal_connect_data () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-shell crashed with SIGSEGV in __GI_raise() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom chrome-remote-desktop dip lpadmin plugdev sambashare sudo separator: ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #2840 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2840 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1880742 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1880742/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1880742] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance()
** Also affects: mutter (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1880742 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1880742/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1880742] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance()
https://gitlab.gnome.org/GNOME/mutter/-/issues/1274 ** Description changed: - https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2840 + https://gitlab.gnome.org/GNOME/mutter/-/issues/1274 --- I was working with nautilus, I hit a 'recent' click. ProblemType: Crash DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.36.2-1ubuntu1 Uname: Linux 5.7.0-050700rc7-generic x86_64 ApportVersion: 2.20.11-0ubuntu36 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 26 13:55:31 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2018-12-02 (541 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=es_CL.UTF-8 LANGUAGE=es_CL:es PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1 Signal: 11 SourcePackage: gnome-shell StacktraceTop: __GI_raise (sig=) at ../sysdeps/unix/sysv/linux/raise.c:50 () () at /lib/x86_64-linux-gnu/libc.so.6 g_type_check_instance () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_connect_data () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-shell crashed with SIGSEGV in __GI_raise() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom chrome-remote-desktop dip lpadmin plugdev sambashare sudo separator: ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1274 https://gitlab.gnome.org/GNOME/mutter/-/issues/1274 ** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/-/issues/1274 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1880742 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance() To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1880742/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1702151] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() from g_object_ref() from st_theme_get_custom_stylesheets()
** Tags added: groovy -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1702151 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() from g_object_ref() from st_theme_get_custom_stylesheets() To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1702151/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1812593] [NEW] gnome-shell[3159]: JS ERROR: Exception in callback for signal: activate: Error: Error invoking IBus.set_global_engine_async: Expected function for callback argument callback, got u
Public bug reported: $ journalctl -b [...] gnome-shell[3159]: JS ERROR: Exception in callback for signal: activate: Error: Error invoking IBus.set_global_engine_async: Expected function for callback argument callback, got undefined setEngine@resource:///org/gnome/shell/misc/ibusManager.js:212:9 wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22 activateInputSource@resource:///org/gnome/shell/ui/status/keyboard.js:490:13 wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22 _emit@resource:///org/gnome/gjs/modules/signals.js:128:27 activate@resource:///org/gnome/shell/ui/status/keyboard.js:65:9 wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22 _inputSourcesChanged@resource:///org/gnome/shell/ui/status/keyboard.js:620:13 wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22 reload@resource:///org/gnome/shell/ui/status/keyboard.js:369:9 wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22 _ibusSetContentType@resource:///org/gnome/shell/ui/status/keyboard.js:691:9 wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22 _emit@resource:///org/gnome/gjs/modules/signals.js:128:27 _setContentType@resource:///org/gnome/shell/misc/ibusManager.js:188:9 wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.30.2-1ubuntu1 Uname: Linux 4.20.3-042003-generic x86_64 ApportVersion: 2.20.10-0ubuntu19 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jan 20 19:36:57 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-12-02 (49 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2018-12-02 (49 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco third-party-packages wayland-session -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1812593 Title: gnome-shell[3159]: JS ERROR: Exception in callback for signal: activate: Error: Error invoking IBus.set_global_engine_async: Expected function for callback argument callback, got undefined To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1812593/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1814884] Re: gvfsd-sftp crashed with SIGABRT in g_assertion_message()
** Information type changed from Private to Public ** Description changed: + https://gitlab.gnome.org/GNOME/gvfs/issues/371 + + --- + I do not know how this happened. ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: gvfs-backends 1.38.1-1ubuntu2 Uname: Linux 5.0.0-05rc5-generic x86_64 ApportVersion: 2.20.10-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Feb 6 07:42:20 2019 ExecutablePath: /usr/lib/gvfs/gvfsd-sftp InstallationDate: Installed on 2018-12-02 (65 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/lib/gvfs/gvfsd-sftp --spawner :1.15 /org/gtk/gvfs/exec_spaw/5 Signal: 6 SourcePackage: gvfs StacktraceTop: - ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 - g_assertion_message_expr () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 - g_vfs_job_emit_finished () from /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so - g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 - ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 + ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 + g_assertion_message_expr () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 + g_vfs_job_emit_finished () from /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so + g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 + ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gvfsd-sftp crashed with SIGABRT in g_assertion_message_expr() UpgradeStatus: Upgraded to disco on 2018-12-02 (65 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1814884 Title: gvfsd-sftp crashed with SIGABRT in g_assertion_message() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1814884/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1815236] Re: totem assert failure: totem: src/intel/genxml/gen9_pack.h:72: __gen_uint: La declaración `v <= max' no se cumple.
** Information type changed from Private to Public ** Description changed: + https://gitlab.gnome.org/GNOME/totem/issues/297 + + --- + I'm not sure, but this happened after updating to gstreamer 1.15.1-1ubuntu1 ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: totem 3.30.0-4ubuntu1 Uname: Linux 4.20.7-042007-generic x86_64 ApportVersion: 2.20.10-0ubuntu20 Architecture: amd64 AssertionMessage: totem: src/intel/genxml/gen9_pack.h:72: __gen_uint: La declaración `v <= max' no se cumple. CurrentDesktop: ubuntu:GNOME Date: Thu Feb 7 18:40:29 2019 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2018-12-02 (68 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/totem --gapplication-service Signal: 6 SourcePackage: totem StacktraceTop: - __assert_fail_base (fmt=0x7ff31939be23 , assertion=0x7ff312a5416c "v <= max", file=0x7ff312a5644c "src/intel/genxml/gen9_pack.h", line=72, function=) at assert.c:92 - __GI___assert_fail (assertion=0x7ff312a5416c "v <= max", file=0x7ff312a5644c "src/intel/genxml/gen9_pack.h", line=72, function=0x7ff312a56938 "__gen_uint") at assert.c:101 - ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so - ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so - ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so + __assert_fail_base (fmt=0x7ff31939be23 , assertion=0x7ff312a5416c "v <= max", file=0x7ff312a5644c "src/intel/genxml/gen9_pack.h", line=72, function=) at assert.c:92 + __GI___assert_fail (assertion=0x7ff312a5416c "v <= max", file=0x7ff312a5644c "src/intel/genxml/gen9_pack.h", line=72, function=0x7ff312a56938 "__gen_uint") at assert.c:101 + ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so + ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so + ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so Title: totem assert failure: totem: src/intel/genxml/gen9_pack.h:72: __gen_uint: La declaración `v <= max' no se cumple. UpgradeStatus: Upgraded to disco on 2018-12-02 (67 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1815236 Title: totem assert failure: totem: src/intel/genxml/gen9_pack.h:72: __gen_uint: La declaración `v <= max' no se cumple. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1815236/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1815236] Re: totem assert failure: totem: src/intel/genxml/gen9_pack.h:72: __gen_uint: La declaración `v <= max' no se cumple.
** Description changed: https://gitlab.gnome.org/GNOME/totem/issues/297 --- - I'm not sure, but this happened after updating to gstreamer - 1.15.1-1ubuntu1 + I'm not sure, but this happened after updating to gstreamer 1.15.1 ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: totem 3.30.0-4ubuntu1 Uname: Linux 4.20.7-042007-generic x86_64 ApportVersion: 2.20.10-0ubuntu20 Architecture: amd64 AssertionMessage: totem: src/intel/genxml/gen9_pack.h:72: __gen_uint: La declaración `v <= max' no se cumple. CurrentDesktop: ubuntu:GNOME Date: Thu Feb 7 18:40:29 2019 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2018-12-02 (68 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/totem --gapplication-service Signal: 6 SourcePackage: totem StacktraceTop: __assert_fail_base (fmt=0x7ff31939be23 , assertion=0x7ff312a5416c "v <= max", file=0x7ff312a5644c "src/intel/genxml/gen9_pack.h", line=72, function=) at assert.c:92 __GI___assert_fail (assertion=0x7ff312a5416c "v <= max", file=0x7ff312a5644c "src/intel/genxml/gen9_pack.h", line=72, function=0x7ff312a56938 "__gen_uint") at assert.c:101 ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so Title: totem assert failure: totem: src/intel/genxml/gen9_pack.h:72: __gen_uint: La declaración `v <= max' no se cumple. UpgradeStatus: Upgraded to disco on 2018-12-02 (67 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1815236 Title: totem assert failure: totem: src/intel/genxml/gen9_pack.h:72: __gen_uint: La declaración `v <= max' no se cumple. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1815236/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1815236] Re: totem assert failure: totem: src/intel/genxml/gen9_pack.h:72: __gen_uint: La declaración `v <= max' no se cumple.
https://gitlab.gnome.org/GNOME/totem/issues/297#note_432608 Bastien Nocera: "Looks like a crash inside the application side intel driver inside Mesa. It's going to be a driver problem rather than something that totem can deal with." ** Also affects: mesa (Ubuntu) Importance: Undecided Status: New ** Also affects: xserver-xorg-video-intel (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1815236 Title: totem assert failure: totem: src/intel/genxml/gen9_pack.h:72: __gen_uint: La declaración `v <= max' no se cumple. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1815236/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1815236] Re: totem assert failure: totem: src/intel/genxml/gen9_pack.h:72: __gen_uint: La declaración `v <= max' no se cumple.
** Description changed: + https://bugs.freedesktop.org/show_bug.cgi?id=109594 (mesa) + + --- + https://gitlab.gnome.org/GNOME/totem/issues/297 --- I'm not sure, but this happened after updating to gstreamer 1.15.1 ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: totem 3.30.0-4ubuntu1 Uname: Linux 4.20.7-042007-generic x86_64 ApportVersion: 2.20.10-0ubuntu20 Architecture: amd64 AssertionMessage: totem: src/intel/genxml/gen9_pack.h:72: __gen_uint: La declaración `v <= max' no se cumple. CurrentDesktop: ubuntu:GNOME Date: Thu Feb 7 18:40:29 2019 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2018-12-02 (68 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/totem --gapplication-service Signal: 6 SourcePackage: totem StacktraceTop: __assert_fail_base (fmt=0x7ff31939be23 , assertion=0x7ff312a5416c "v <= max", file=0x7ff312a5644c "src/intel/genxml/gen9_pack.h", line=72, function=) at assert.c:92 __GI___assert_fail (assertion=0x7ff312a5416c "v <= max", file=0x7ff312a5644c "src/intel/genxml/gen9_pack.h", line=72, function=0x7ff312a56938 "__gen_uint") at assert.c:101 ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so Title: totem assert failure: totem: src/intel/genxml/gen9_pack.h:72: __gen_uint: La declaración `v <= max' no se cumple. UpgradeStatus: Upgraded to disco on 2018-12-02 (67 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1815236 Title: totem assert failure: totem: src/intel/genxml/gen9_pack.h:72: __gen_uint: La declaración `v <= max' no se cumple. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1815236/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1815236] Re: totem assert failure: totem: src/intel/genxml/gen9_pack.h:72: __gen_uint: La declaración `v <= max' no se cumple.
** Also affects: libdrm (Ubuntu) Importance: Undecided Status: New ** Description changed: + https://bugs.freedesktop.org/show_bug.cgi?id=109595 (DRM/Intel) + + --- + https://bugs.freedesktop.org/show_bug.cgi?id=109594 (mesa) --- https://gitlab.gnome.org/GNOME/totem/issues/297 --- I'm not sure, but this happened after updating to gstreamer 1.15.1 ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: totem 3.30.0-4ubuntu1 Uname: Linux 4.20.7-042007-generic x86_64 ApportVersion: 2.20.10-0ubuntu20 Architecture: amd64 AssertionMessage: totem: src/intel/genxml/gen9_pack.h:72: __gen_uint: La declaración `v <= max' no se cumple. CurrentDesktop: ubuntu:GNOME Date: Thu Feb 7 18:40:29 2019 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2018-12-02 (68 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/totem --gapplication-service Signal: 6 SourcePackage: totem StacktraceTop: __assert_fail_base (fmt=0x7ff31939be23 , assertion=0x7ff312a5416c "v <= max", file=0x7ff312a5644c "src/intel/genxml/gen9_pack.h", line=72, function=) at assert.c:92 __GI___assert_fail (assertion=0x7ff312a5416c "v <= max", file=0x7ff312a5644c "src/intel/genxml/gen9_pack.h", line=72, function=0x7ff312a56938 "__gen_uint") at assert.c:101 ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so Title: totem assert failure: totem: src/intel/genxml/gen9_pack.h:72: __gen_uint: La declaración `v <= max' no se cumple. UpgradeStatus: Upgraded to disco on 2018-12-02 (67 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo ** Description changed: https://bugs.freedesktop.org/show_bug.cgi?id=109595 (DRM/Intel) --- https://bugs.freedesktop.org/show_bug.cgi?id=109594 (mesa) --- https://gitlab.gnome.org/GNOME/totem/issues/297 --- - I'm not sure, but this happened after updating to gstreamer 1.15.1 + I'm not sure, but this happened after updating to gstreamer 1.15.1. The + problem occurs when I maximize totem. ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: totem 3.30.0-4ubuntu1 Uname: Linux 4.20.7-042007-generic x86_64 ApportVersion: 2.20.10-0ubuntu20 Architecture: amd64 AssertionMessage: totem: src/intel/genxml/gen9_pack.h:72: __gen_uint: La declaración `v <= max' no se cumple. CurrentDesktop: ubuntu:GNOME Date: Thu Feb 7 18:40:29 2019 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2018-12-02 (68 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/totem --gapplication-service Signal: 6 SourcePackage: totem StacktraceTop: __assert_fail_base (fmt=0x7ff31939be23 , assertion=0x7ff312a5416c "v <= max", file=0x7ff312a5644c "src/intel/genxml/gen9_pack.h", line=72, function=) at assert.c:92 __GI___assert_fail (assertion=0x7ff312a5416c "v <= max", file=0x7ff312a5644c "src/intel/genxml/gen9_pack.h", line=72, function=0x7ff312a56938 "__gen_uint") at assert.c:101 ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so Title: totem assert failure: totem: src/intel/genxml/gen9_pack.h:72: __gen_uint: La declaración `v <= max' no se cumple. UpgradeStatus: Upgraded to disco on 2018-12-02 (67 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo ** Description changed: - https://bugs.freedesktop.org/show_bug.cgi?id=109595 (DRM/Intel) - - --- - https://bugs.freedesktop.org/show_bug.cgi?id=109594 (mesa) --- https://gitlab.gnome.org/GNOME/totem/issues/297 --- I'm not sure, but this happened after updating to gstreamer 1.15.1. The problem occurs when I maximize totem. ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: totem 3.30.0-4ubuntu1 Uname: Linux 4.20.7-042007-generic x86_64 ApportVersion: 2.20.10-0ubuntu20 Architecture: amd64 AssertionMessage: totem: src/intel/genxml/gen9_pack.h:72: __gen_uint: La declaración `v <= max' no se cumple. CurrentDesktop: ubuntu:GNOME Date: Thu Feb 7 18:40:29 2019 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2018-12-02 (68 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/totem --gapplication-service Signal: 6 SourcePackage: totem StacktraceTop: __assert_fail_base (fmt=0x7ff31939be23 , assertion=0x7ff312a5416c "v <= max", file=0x7ff312a5644c "src/intel/genxml/gen9_pack.h", line=72, function=) at assert.c:92 __GI___assert_fail (assertion=0x7ff312a5416c "v <= max", file=0x7ff312a5644c "src/intel/genxml/gen9_pack.h", line=72, function=0x7ff312a56938 "__gen_uint") at assert.c:101 ?? () from /usr/lib/x86_64-l
[Bug 1815785] Re: gnome-shell crashed with SIGABRT in __GI_raise()
** Description changed: - I do not know how this happened. + In gdm I changed the login from Wayland to Xorg. ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.30.2-2ubuntu2 ProcVersionSignature: Ubuntu 4.19.0-12.13-generic 4.19.18 Uname: Linux 4.20.8-042008-generic x86_64 ApportVersion: 2.20.10-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Feb 13 13:15:27 2019 DisplayManager: - + ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1549536707 GsettingsChanges: - + InstallationDate: Installed on 2018-12-02 (72 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/gnome-shell ProcCwd: /home/caravena Signal: 6 SourcePackage: gnome-shell StacktraceTop: - __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 - __GI_abort () at abort.c:79 - ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 - g_assertion_message_expr () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 - ?? () from /usr/lib/gnome-shell/libst-1.0.so + __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 + __GI_abort () at abort.c:79 + ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 + g_assertion_message_expr () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 + ?? () from /usr/lib/gnome-shell/libst-1.0.so UpgradeStatus: Upgraded to disco on 2018-12-02 (72 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo ** Information type changed from Private to Public ** Description changed: + https://gitlab.gnome.org/GNOME/gnome-shell/issues/972 + + --- + In gdm I changed the login from Wayland to Xorg. ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.30.2-2ubuntu2 ProcVersionSignature: Ubuntu 4.19.0-12.13-generic 4.19.18 Uname: Linux 4.20.8-042008-generic x86_64 ApportVersion: 2.20.10-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Feb 13 13:15:27 2019 DisplayManager: ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1549536707 GsettingsChanges: InstallationDate: Installed on 2018-12-02 (72 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/gnome-shell ProcCwd: /home/caravena Signal: 6 SourcePackage: gnome-shell StacktraceTop: __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 __GI_abort () at abort.c:79 ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/gnome-shell/libst-1.0.so UpgradeStatus: Upgraded to disco on 2018-12-02 (72 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1815785 Title: gnome-shell crashed with SIGABRT in __GI_raise() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1815785/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1816392] [NEW] The notebook runs slow after updating
Public bug reported: Attach image of top. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.30.2-2ubuntu2 Uname: Linux 5.0.0-05rc7-generic x86_64 ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 18 08:06:10 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-12-02 (77 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2018-12-02 (77 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco wayland-session -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1816392 Title: The notebook runs slow after updating To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1816392/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1816392] Re: The notebook runs slow after updating
** Attachment added: "Captura de pantalla de 2019-02-18 08-07-52.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1816392/+attachment/5239489/+files/Captura%20de%20pantalla%20de%202019-02-18%2008-07-52.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1816392 Title: The notebook runs slow after updating To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1816392/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1816392] Re: The notebook runs slow after updating (In Wayland and Xorg)
** Summary changed: - The notebook runs slow after updating + The notebook runs slow after updating (In Wayland and Xorg) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1816392 Title: The notebook runs slow after updating (In Wayland and Xorg) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1816392/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1816392] Re: The notebook runs slow after updating (In Wayland and Xorg)
*** This bug is a duplicate of bug 1816415 *** https://bugs.launchpad.net/bugs/1816415 ** This bug has been marked a duplicate of private bug 1816415 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1816392 Title: The notebook runs slow after updating (In Wayland and Xorg) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1816392/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1816415] Re: gjs-console crashed with SIGSEGV in g_socket_receive_message_with_timeout()
** Information type changed from Private to Public ** Description changed: + https://gitlab.gnome.org/GNOME/gjs/issues/227 + + --- + I have performance problems, after updating. ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: gjs 1.54.3-1build1 Uname: Linux 5.0.0-05rc6-generic x86_64 ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 18 07:39:11 2019 ExecutablePath: /usr/bin/gjs-console InstallationDate: Installed on 2018-12-02 (77 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: gjs /home/username/.local/share/gnome-shell/extensions/gsconn...@andyholmes.github.io/service/daemon.js SegvAnalysis: - Segfault happened at: 0x7f224b1fafd8:mov(%r15),%edx - PC (0x7f224b1fafd8) ok - source "(%r15)" (0xfff98002) not located in a known VMA region (needed readable region)! - destination "%edx" ok + Segfault happened at: 0x7f224b1fafd8:mov(%r15),%edx + PC (0x7f224b1fafd8) ok + source "(%r15)" (0xfff98002) not located in a known VMA region (needed readable region)! + destination "%edx" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: gjs StacktraceTop: - ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 - g_socket_receive_message () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 - ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 - ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6 - ?? () from /usr/lib/libgjs.so.0 + ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 + g_socket_receive_message () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 + ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 + ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6 + ?? () from /usr/lib/libgjs.so.0 Title: gjs-console crashed with SIGSEGV in g_socket_receive_message() UpgradeStatus: Upgraded to disco on 2018-12-02 (77 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1816415 Title: gjs-console crashed with SIGSEGV in g_socket_receive_message_with_timeout() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1816415/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1816458] [NEW] Full load
Public bug reported: https://gitlab.gnome.org/GNOME/gnome-keyring/issues/25 --- I do not know what happens, but the gnome-keyring process occupies the entire processor for a long time. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-keyring 3.28.2-3ubuntu1 Uname: Linux 5.0.0-05rc7-generic x86_64 ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 18 12:45:51 2019 InstallationDate: Installed on 2018-12-02 (77 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-keyring UpgradeStatus: Upgraded to disco on 2018-12-02 (77 days ago) ** Affects: gnome-keyring (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco third-party-packages wayland-session ** Description changed: + https://gitlab.gnome.org/GNOME/gnome-keyring/issues/25 + + --- + I do not know what happens, but the gnome-keyring process occupies the entire processor for a long time. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-keyring 3.28.2-3ubuntu1 Uname: Linux 5.0.0-05rc7-generic x86_64 ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 18 12:45:51 2019 InstallationDate: Installed on 2018-12-02 (77 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-keyring UpgradeStatus: Upgraded to disco on 2018-12-02 (77 days ago) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1816458 Title: Full load To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1816458/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1816458] Re: Full load
** Description changed: https://gitlab.gnome.org/GNOME/gnome-keyring/issues/25 --- - I do not know what happens, but the gnome-keyring process occupies the - entire processor for a long time. + Description of problem: + After logging into my session, the gnome-keyring-daemon process overloads the notebook. With this I have a drop in performance of important equipment. + + Version-Release number of selected component (if applicable): Disco + 19.04. + + How reproducible: + Forever. + + Steps to reproducible: + 1. Login with my user account and password in GDM3 + 2. Then I check with the 'top' program in terminal + 3. I have had loads of ~ 7...11 (load average) + + Actual results: + The gnome-keyring-daemon process demands the processor. And therefore, the team does not respond quickly + + Expected results: + That when entering my session, the gnome-keyring-daemos process does not occupy the processor so much. And so I can have a lighter session. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-keyring 3.28.2-3ubuntu1 Uname: Linux 5.0.0-05rc7-generic x86_64 ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 18 12:45:51 2019 InstallationDate: Installed on 2018-12-02 (77 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-keyring UpgradeStatus: Upgraded to disco on 2018-12-02 (77 days ago) ** Attachment added: "journalctl_-b-1.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1816458/+attachment/5239830/+files/journalctl_-b-1.txt ** Description changed: https://gitlab.gnome.org/GNOME/gnome-keyring/issues/25 --- Description of problem: - After logging into my session, the gnome-keyring-daemon process overloads the notebook. With this I have a drop in performance of important equipment. + After logging, the gnome-keyring-daemon process overloads the notebook. With this I have a drop in performance. Version-Release number of selected component (if applicable): Disco 19.04. How reproducible: Forever. Steps to reproducible: 1. Login with my user account and password in GDM3 2. Then I check with the 'top' program in terminal 3. I have had loads of ~ 7...11 (load average) Actual results: The gnome-keyring-daemon process demands the processor. And therefore, the team does not respond quickly Expected results: That when entering my session, the gnome-keyring-daemos process does not occupy the processor so much. And so I can have a lighter session. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-keyring 3.28.2-3ubuntu1 Uname: Linux 5.0.0-05rc7-generic x86_64 ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 18 12:45:51 2019 InstallationDate: Installed on 2018-12-02 (77 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-keyring UpgradeStatus: Upgraded to disco on 2018-12-02 (77 days ago) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1816458 Title: Full load To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1816458/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1816458] Re: Full load
** Description changed: https://gitlab.gnome.org/GNOME/gnome-keyring/issues/25 --- Description of problem: After logging, the gnome-keyring-daemon process overloads the notebook. With this I have a drop in performance. Version-Release number of selected component (if applicable): Disco 19.04. How reproducible: Forever. Steps to reproducible: 1. Login with my user account and password in GDM3 2. Then I check with the 'top' program in terminal 3. I have had loads of ~ 7...11 (load average) Actual results: - The gnome-keyring-daemon process demands the processor. And therefore, the team does not respond quickly + The gnome-keyring-daemon process demands the processor. And therefore, the computer does not respond quickly Expected results: That when entering my session, the gnome-keyring-daemos process does not occupy the processor so much. And so I can have a lighter session. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-keyring 3.28.2-3ubuntu1 Uname: Linux 5.0.0-05rc7-generic x86_64 ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 18 12:45:51 2019 InstallationDate: Installed on 2018-12-02 (77 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-keyring UpgradeStatus: Upgraded to disco on 2018-12-02 (77 days ago) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1816458 Title: Full load To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1816458/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1816458] Re: Full load
** Description changed: https://gitlab.gnome.org/GNOME/gnome-keyring/issues/25 --- Description of problem: After logging, the gnome-keyring-daemon process overloads the notebook. With this I have a drop in performance. Version-Release number of selected component (if applicable): Disco 19.04. How reproducible: - Forever. + Always. Steps to reproducible: 1. Login with my user account and password in GDM3 2. Then I check with the 'top' program in terminal 3. I have had loads of ~ 7...11 (load average) Actual results: The gnome-keyring-daemon process demands the processor. And therefore, the computer does not respond quickly Expected results: That when entering my session, the gnome-keyring-daemos process does not occupy the processor so much. And so I can have a lighter session. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-keyring 3.28.2-3ubuntu1 Uname: Linux 5.0.0-05rc7-generic x86_64 ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 18 12:45:51 2019 InstallationDate: Installed on 2018-12-02 (77 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-keyring UpgradeStatus: Upgraded to disco on 2018-12-02 (77 days ago) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1816458 Title: Full load To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1816458/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
