[Bug 1718736] Re: gsd-keyboard crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a()
[Expired for gnome-settings-daemon (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-settings-daemon (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1718736 Title: gsd-keyboard crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1718736/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1718736] Re: gsd-keyboard crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a()
** Description changed: I was using chromium-browser when first a general freeze has happened. Gnome-tweak-tool was not opened nor used previously. I have tried hitting Esc & other keyboard combinations to unlock the wayland session, but i only got that session crashing. And then relogin to a wayland session has failed, but a xorg one is ok. (not rebooted at time) note: the relogin problem is not met after a cold boot; so this seems a transitional issue due to some of the latest daily packages upgrade (needing a reboot to work as expected. Maybe that crash also is related to that fact) + + Feedback: that problem has not been reproduced; so it seems that either + the libinput or lintian previous upgrade have introduce a hidden need of + reboot, disturbing the system then freeze & crash. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-settings-daemon 3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1 Uname: Linux 4.13.0-11-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Sep 21 19:01:49 2017 EcryptfsInUse: Yes ExecutablePath: /usr/lib/gnome-settings-daemon/gsd-keyboard ProcCmdline: /usr/lib/gnome-settings-daemon/gsd-keyboard ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f6714b10d81: movzbl 0x14(%rdx),%eax PC (0x7f6714b10d81) ok source "0x14(%rdx)" (0x20014) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnome-settings-daemon StacktraceTop: g_type_check_instance_is_fundamentally_a () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_ref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_weak_ref_get () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gsd-keyboard crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo ** Changed in: gnome-settings-daemon (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1718736 Title: gsd-keyboard crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1718736/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1718736] Re: gsd-keyboard crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a()
** Description changed: I was using chromium-browser when first a general freeze has happened. Gnome-tweak-tool was not opened nor used previously. I have tried hitting Esc & other keyboard combinations to unlock the wayland session, but i only got that session crashing. And then relogin to a wayland session has failed, but a xorg one is ok. (not rebooted at time) + + note: + the relogin problem is not met after a cold boot; so this seems a transitional issue due to some of the latest packages upgrade (needing a reboot to work as expected. Maybe that crash also is related to that fact) ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-settings-daemon 3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1 Uname: Linux 4.13.0-11-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Sep 21 19:01:49 2017 EcryptfsInUse: Yes ExecutablePath: /usr/lib/gnome-settings-daemon/gsd-keyboard ProcCmdline: /usr/lib/gnome-settings-daemon/gsd-keyboard ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f6714b10d81: movzbl 0x14(%rdx),%eax PC (0x7f6714b10d81) ok source "0x14(%rdx)" (0x20014) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnome-settings-daemon StacktraceTop: g_type_check_instance_is_fundamentally_a () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_ref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_weak_ref_get () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gsd-keyboard crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo ** Description changed: I was using chromium-browser when first a general freeze has happened. Gnome-tweak-tool was not opened nor used previously. I have tried hitting Esc & other keyboard combinations to unlock the wayland session, but i only got that session crashing. And then relogin to a wayland session has failed, but a xorg one is ok. (not rebooted at time) note: - the relogin problem is not met after a cold boot; so this seems a transitional issue due to some of the latest packages upgrade (needing a reboot to work as expected. Maybe that crash also is related to that fact) + the relogin problem is not met after a cold boot; so this seems a transitional issue due to some of the latest daily packages upgrade (needing a reboot to work as expected. Maybe that crash also is related to that fact) ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-settings-daemon 3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1 Uname: Linux 4.13.0-11-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Sep 21 19:01:49 2017 EcryptfsInUse: Yes ExecutablePath: /usr/lib/gnome-settings-daemon/gsd-keyboard ProcCmdline: /usr/lib/gnome-settings-daemon/gsd-keyboard ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f6714b10d81 : movzbl 0x14(%rdx),%eax PC (0x7f6714b10d81) ok source "0x14(%rdx)" (0x20014) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnome-settings-daemon StacktraceTop: g_type_check_instance_is_fundamentally_a () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_ref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_weak_ref_get () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gsd-keyboard crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() 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 gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1718736 Title: gsd-keyboard crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1718736/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com
[Bug 1718736] Re: gsd-keyboard crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a()
** Description changed: I was using chromium-browser when first a general freeze has happened. - Gnome-tweak-tool was not opened nor used previously. I have tried hitting Esc & other keyboard combinations to unlock the wayland session, but i only got that crash. And then relogin to a wayland session has failed, but a xorg one is ok. (not rebooted at time) + Gnome-tweak-tool was not opened nor used previously. I have tried hitting Esc & other keyboard combinations to unlock the wayland session, but i only got that session crashing. And then relogin to a wayland session has failed, but a xorg one is ok. (not rebooted at time) ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-settings-daemon 3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1 Uname: Linux 4.13.0-11-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Sep 21 19:01:49 2017 EcryptfsInUse: Yes ExecutablePath: /usr/lib/gnome-settings-daemon/gsd-keyboard ProcCmdline: /usr/lib/gnome-settings-daemon/gsd-keyboard ProcEnviron: - LANGUAGE=en_US - PATH=(custom, no user) - LANG=en_US.UTF-8 - SHELL=/bin/bash + LANGUAGE=en_US + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash SegvAnalysis: - Segfault happened at: 0x7f6714b10d81: movzbl 0x14(%rdx),%eax - PC (0x7f6714b10d81) ok - source "0x14(%rdx)" (0x20014) not located in a known VMA region (needed readable region)! - destination "%eax" ok + Segfault happened at: 0x7f6714b10d81 : movzbl 0x14(%rdx),%eax + PC (0x7f6714b10d81) ok + source "0x14(%rdx)" (0x20014) not located in a known VMA region (needed readable region)! + destination "%eax" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnome-settings-daemon StacktraceTop: - g_type_check_instance_is_fundamentally_a () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 - g_object_ref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 - g_weak_ref_get () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 - ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 - g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 + g_type_check_instance_is_fundamentally_a () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 + g_object_ref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 + g_weak_ref_get () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 + ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 + g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gsd-keyboard crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() 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 gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1718736 Title: gsd-keyboard crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1718736/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs