Re: [Bug 1867667] Re: gdm3 crashed with signal 5 in g_wakeup_new() from g_main_context_new() from g_dbus_connection_send_message_with_reply_sync()
Hi, My apologies. I'm not a developer or even an advanced linux user, actually. I typed in "lsof | grep gdm3 > gdm3.txt" and have attached the output to this email. Let me know if I should do something different. Thanks! -G. Tom On Thu, Mar 26, 2020 at 3:41 AM Sebastien Bacher wrote: > The backtrace suggests a fd leak but it could be another process having > the issue and just letting the system in a state where gdm errors out > due to it > > Could you use lsof to figure out what process is using the fds? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1867667 > > Title: > gdm3 crashed with signal 5 in g_wakeup_new() from g_main_context_new() > from g_dbus_connection_send_message_with_reply_sync() > > Status in gdm3 package in Ubuntu: > Incomplete > > Bug description: > Honestly not sure why this bug appeared. I did not edit the gdm.conf > file. Possibly due to hotplugging/unplugging an external monitor? > > ProblemType: Crash > DistroRelease: Ubuntu 20.04 > Package: gdm3 3.34.1-1ubuntu1 > ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 > Uname: Linux 5.5.9-050509-generic x86_64 > NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair > ApportVersion: 2.20.11-0ubuntu20 > Architecture: amd64 > Date: Mon Mar 16 14:42:22 2020 > ExecutablePath: /usr/sbin/gdm3 > ProcCmdline: /usr/sbin/gdm3 > ProcEnviron: >LANG=en_US.UTF-8 >PATH=(custom, no user) > Signal: 5 > SourcePackage: gdm3 > StacktraceTop: >?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 >g_main_context_new () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 >g_dbus_connection_send_message_with_reply_sync () from > /lib/x86_64-linux-gnu/libgio-2.0.so.0 >?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 >g_dbus_connection_call_sync () from > /lib/x86_64-linux-gnu/libgio-2.0.so.0 > Title: gdm3 crashed with signal 5 in g_main_context_new() > UpgradeStatus: No upgrade log present (probably fresh install) > UserGroups: > > mtime.conffile..etc.gdm3.custom.conf: 2020-03-16T12:35:32.738705 > separator: > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1867667/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867667 Title: gdm3 crashed with signal 5 in g_wakeup_new() from g_main_context_new() from g_dbus_connection_send_message_with_reply_sync() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1867667/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1867667] Re: gdm3 crashed with signal 5 in g_wakeup_new() from g_main_context_new() from g_dbus_connection_send_message_with_reply_sync()
I'm sorry, comment #6? I don't know what that refers to. Can you copy and paste the commands in an email message? Thanks! On Wed, Mar 25, 2020 at 11:16 PM Daniel van Vugt < daniel.van.v...@canonical.com> wrote: > Thanks. That's also inconclusive. > > Please repeat the command(s) from comment #6 after the crash happens > again. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1867667 > > Title: > gdm3 crashed with signal 5 in g_wakeup_new() from g_main_context_new() > from g_dbus_connection_send_message_with_reply_sync() > > Status in gdm3 package in Ubuntu: > Incomplete > > Bug description: > Honestly not sure why this bug appeared. I did not edit the gdm.conf > file. Possibly due to hotplugging/unplugging an external monitor? > > ProblemType: Crash > DistroRelease: Ubuntu 20.04 > Package: gdm3 3.34.1-1ubuntu1 > ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 > Uname: Linux 5.5.9-050509-generic x86_64 > NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair > ApportVersion: 2.20.11-0ubuntu20 > Architecture: amd64 > Date: Mon Mar 16 14:42:22 2020 > ExecutablePath: /usr/sbin/gdm3 > ProcCmdline: /usr/sbin/gdm3 > ProcEnviron: >LANG=en_US.UTF-8 >PATH=(custom, no user) > Signal: 5 > SourcePackage: gdm3 > StacktraceTop: >?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 >g_main_context_new () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 >g_dbus_connection_send_message_with_reply_sync () from > /lib/x86_64-linux-gnu/libgio-2.0.so.0 >?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 >g_dbus_connection_call_sync () from > /lib/x86_64-linux-gnu/libgio-2.0.so.0 > Title: gdm3 crashed with signal 5 in g_main_context_new() > UpgradeStatus: No upgrade log present (probably fresh install) > UserGroups: > > mtime.conffile..etc.gdm3.custom.conf: 2020-03-16T12:35:32.738705 > separator: > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1867667/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867667 Title: gdm3 crashed with signal 5 in g_wakeup_new() from g_main_context_new() from g_dbus_connection_send_message_with_reply_sync() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1867667/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1867667] Re: gdm3 crashed with signal 5 in g_wakeup_new() from g_main_context_new() from g_dbus_connection_send_message_with_reply_sync()
Hi, I checked as instructed and cases appeared. However, I'm not sure if I'm the one who logged them all. I apologize, if that's the case. https://errors.ubuntu.com/user/c5ffbbbf9cd21738895082c5084ddf7a4d4691b1f9b058c4116352c751da2edbc4b1f9381b39ff8cccb2d075f25c6fd9860eae713d8e2f887b00d3ede92d906a Cheers, -G. Tom On Wed, Mar 25, 2020 at 10:10 PM Daniel van Vugt < daniel.van.v...@canonical.com> wrote: > Thanks, though the information I was hoping for is not there. > > Next please look at https://errors.ubuntu.com/user/ID where ID is the > content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you > find any links to recent problems on that page? If so then please send > the links to us. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1867667 > > Title: > gdm3 crashed with signal 5 in g_wakeup_new() from g_main_context_new() > from g_dbus_connection_send_message_with_reply_sync() > > Status in gdm3 package in Ubuntu: > Incomplete > > Bug description: > Honestly not sure why this bug appeared. I did not edit the gdm.conf > file. Possibly due to hotplugging/unplugging an external monitor? > > ProblemType: Crash > DistroRelease: Ubuntu 20.04 > Package: gdm3 3.34.1-1ubuntu1 > ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 > Uname: Linux 5.5.9-050509-generic x86_64 > NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair > ApportVersion: 2.20.11-0ubuntu20 > Architecture: amd64 > Date: Mon Mar 16 14:42:22 2020 > ExecutablePath: /usr/sbin/gdm3 > ProcCmdline: /usr/sbin/gdm3 > ProcEnviron: >LANG=en_US.UTF-8 >PATH=(custom, no user) > Signal: 5 > SourcePackage: gdm3 > StacktraceTop: >?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 >g_main_context_new () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 >g_dbus_connection_send_message_with_reply_sync () from > /lib/x86_64-linux-gnu/libgio-2.0.so.0 >?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 >g_dbus_connection_call_sync () from > /lib/x86_64-linux-gnu/libgio-2.0.so.0 > Title: gdm3 crashed with signal 5 in g_main_context_new() > UpgradeStatus: No upgrade log present (probably fresh install) > UserGroups: > > mtime.conffile..etc.gdm3.custom.conf: 2020-03-16T12:35:32.738705 > separator: > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1867667/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867667 Title: gdm3 crashed with signal 5 in g_wakeup_new() from g_main_context_new() from g_dbus_connection_send_message_with_reply_sync() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1867667/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1867667] Re: gdm3 crashed with signal 5 in g_wakeup_new() from g_main_context_new() from g_dbus_connection_send_message_with_reply_sync()
Hi, Sorry for the late reply. I have attached the output of the command you requested. This error happens whenever I log in now, regardless of external monitor or not. Some background: I'm running Ubuntu 20.04 with an upgraded 5.4 kernel with custom patches to allow Ubuntu to work properly (more or less) on a Apple MacBook Pro 16-inch with an AMD Radeon Pro 5500M (8GB). Cheers, G. Tom On Wed, Mar 18, 2020 at 10:55 PM Daniel van Vugt < daniel.van.v...@canonical.com> wrote: > This sounds like bug 1597150 but I can't be sure yet. If you haven't yet > rebooted since the crash then please run: > > journalctl -b0 > journal.txt > > If you have rebooted once since the crash then please run: > > journalctl -b-1 > prevboot.txt > > And in either case attach the resulting text file here. > > > ** Summary changed: > > - gdm3 crashed with signal 5 in g_main_context_new() > + gdm3 crashed with signal 5 in g_wakeup_new() from g_main_context_new() > from g_dbus_connection_send_message_with_reply_sync() > > ** Changed in: gdm3 (Ubuntu) >Status: New => Incomplete > > ** Information type changed from Private to Public > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1867667 > > Title: > gdm3 crashed with signal 5 in g_wakeup_new() from g_main_context_new() > from g_dbus_connection_send_message_with_reply_sync() > > Status in gdm3 package in Ubuntu: > Incomplete > > Bug description: > Honestly not sure why this bug appeared. I did not edit the gdm.conf > file. Possibly due to hotplugging/unplugging an external monitor? > > ProblemType: Crash > DistroRelease: Ubuntu 20.04 > Package: gdm3 3.34.1-1ubuntu1 > ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 > Uname: Linux 5.5.9-050509-generic x86_64 > NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair > ApportVersion: 2.20.11-0ubuntu20 > Architecture: amd64 > Date: Mon Mar 16 14:42:22 2020 > ExecutablePath: /usr/sbin/gdm3 > ProcCmdline: /usr/sbin/gdm3 > ProcEnviron: >LANG=en_US.UTF-8 >PATH=(custom, no user) > Signal: 5 > SourcePackage: gdm3 > StacktraceTop: >?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 >g_main_context_new () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 >g_dbus_connection_send_message_with_reply_sync () from > /lib/x86_64-linux-gnu/libgio-2.0.so.0 >?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 >g_dbus_connection_call_sync () from > /lib/x86_64-linux-gnu/libgio-2.0.so.0 > Title: gdm3 crashed with signal 5 in g_main_context_new() > UpgradeStatus: No upgrade log present (probably fresh install) > UserGroups: > > mtime.conffile..etc.gdm3.custom.conf: 2020-03-16T12:35:32.738705 > separator: > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1867667/+subscriptions > ** Attachment added: "journal.txt" https://bugs.launchpad.net/bugs/1867667/+attachment/5341711/+files/journal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867667 Title: gdm3 crashed with signal 5 in g_wakeup_new() from g_main_context_new() from g_dbus_connection_send_message_with_reply_sync() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1867667/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
