Ubuntu
gdm3 package

gdm3 crashed with signal 5 in g_wakeup_new() from g_main_context_new() from g_dbus_connection_send_message_with_reply_sync()

Bug #1867667 reported by GTB
14
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gdm3 (Ubuntu)
Expired
Medium
Unassigned

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:

Revision history for this message
GTB (gbrow04) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceTop.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in gdm3 (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Daniel van Vugt (vanvugt) 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: - 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: Private → Public
Revision history for this message
GTB (gbrow04) wrote : 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()
  • journal.txt Edit (337.6 KiB, text/plain; charset="US-ASCII"; name="journal.txt")

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 <
<email address hidden>> 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
>

Revision history for this message
Daniel van Vugt (vanvugt) 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.

Revision history for this message
GTB (gbrow04) wrote :

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 <
<email address hidden>> 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
>

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Thanks. That's also inconclusive.

Please repeat the command(s) from comment #6 after the crash happens again.

Revision history for this message
GTB (gbrow04) wrote :

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 <
<email address hidden>> 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
>

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1867667/comments/6

Revision history for this message
Sebastien Bacher (seb128) 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?

Revision history for this message
GTB (gbrow04) wrote :

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 <email address hidden> 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
>

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Please repeat the command(s) from comment #6 after the crash happens again:

https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1867667/comments/6

At the same time, it looks likely this is actually just bug 1597150 so maybe also subscribe to that.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for gdm3 (Ubuntu) because there has been no activity for 60 days.]

Changed in gdm3 (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.