[Bug 1597150] Re: gdm3 crashed with SIGTRAP logging "Creating pipes for GWakeup: Too many open files\n" in g_wakeup_new() from g_main_context_new() from g_dbus_connection_send_message_with_reply_sync(

** Tags removed: eoan xenial -- 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/1597150 Title: gdm3 crashed with SIGTRAP logging "Creating pipes for GWakeup: Too many open files\n" in

[Bug 1597150] Re: gdm3 crashed with SIGTRAP logging "Creating pipes for GWakeup: Too many open files\n" in g_wakeup_new() from g_main_context_new() from g_dbus_connection_send_message_with_reply_sync(

** Tags added: eoan focal -- 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/1597150 Title: gdm3 crashed with SIGTRAP logging "Creating pipes for GWakeup: Too many open files\n" in

[Bug 1597150] Re: gdm3 crashed with SIGTRAP logging "Creating pipes for GWakeup: Too many open files\n" in g_wakeup_new() from g_main_context_new() from g_dbus_connection_send_message_with_reply_sync(

** Tags removed: artful cosmic -- 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/1597150 Title: gdm3 crashed with SIGTRAP logging "Creating pipes for GWakeup: Too many open files\n"

[Bug 1597150] Re: gdm3 crashed with SIGTRAP logging "Creating pipes for GWakeup: Too many open files\n" in g_wakeup_new() from g_main_context_new() from g_dbus_connection_send_message_with_reply_sync(

Thanks. Please keep a close eye on those ones that look similar: gdm31561 root8u unix 0x995a67bdcc00 0t0 25239 @/tmp/dbus-VGj4R3Fs type=STREAM gdm31561 root9u unix 0x995a67bdd000 0t0 25240 @/tmp/dbus-NnCbDQ5S type=STREAM gdm31561 root 10u

[Bug 1597150] Re: gdm3 crashed with SIGTRAP logging "Creating pipes for GWakeup: Too many open files\n" in g_wakeup_new() from g_main_context_new() from g_dbus_connection_send_message_with_reply_sync(

Thanks. Unfortunately that doesn't show a leak yet. Next, please leave the machine running for a few days first, and then repeat the command. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu.

[Bug 1597150] Re: gdm3 crashed with SIGTRAP logging "Creating pipes for GWakeup: Too many open files\n" in g_wakeup_new() from g_main_context_new() from g_dbus_connection_send_message_with_reply_sync(

I did the all stuff again and first crashed gnome-shell then Xwayland. gdm3 is still running with the same PID but gdm-wayland-session PID change after few seconds. Example: 821 ?Ssl0:00 /usr/sbin/gdm3 3911 pts/3S+ 0:00 grep --color=auto gdm3 3935 tty1 Ssl+ 0:00

[Bug 1597150] Re: gdm3 crashed with SIGTRAP logging "Creating pipes for GWakeup: Too many open files\n" in g_wakeup_new() from g_main_context_new() from g_dbus_connection_send_message_with_reply_sync(

Thanks. Sorry, I forgot to mention you need to run it under 'sudo' to avoid all those "Permission denied" errors. Try this: sudo lsof -c gdm3 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu.

[Bug 1597150] Re: gdm3 crashed with SIGTRAP logging "Creating pipes for GWakeup: Too many open files\n" in g_wakeup_new() from g_main_context_new() from g_dbus_connection_send_message_with_reply_sync(

Hi, here is the detail of what happend: - remove all files from /var/crash - restart computer, the Ubuntu screen with the dots is shown - when time of greeting appears in /var/crash _usr_bin_Xwayland.124.crash and .lock files - some seconds after appears _usr_bin_gnome-shell.124.crash in this

[Bug 1597150] Re: gdm3 crashed with SIGTRAP logging "Creating pipes for GWakeup: Too many open files\n" in g_wakeup_new() from g_main_context_new() from g_dbus_connection_send_message_with_reply_sync(

Thanks, but unfortunately that snapshot was taken at the wrong time. We would need 'lsof' to be run before gdm3 has crashed (but after it has been running for a long time), so as to see what exactly is accumulating over time. -- You received this bug notification because you are a member of

[Bug 1597150] Re: gdm3 crashed with SIGTRAP logging "Creating pipes for GWakeup: Too many open files\n" in g_wakeup_new() from g_main_context_new() from g_dbus_connection_send_message_with_reply_sync(

I ran lsof, max display lines I saw (sudo lsof |wc -l) are near of 22000. Attached is an lsof runned after I restart gdm3 Daniel ** Attachment added: "lsof_1597150.log" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1597150/+attachment/5185622/+files/lsof_1597150.log -- You received

[Bug 1597150] Re: gdm3 crashed with SIGTRAP logging "Creating pipes for GWakeup: Too many open files\n" in g_wakeup_new() from g_main_context_new() from g_dbus_connection_send_message_with_reply_sync(

** Summary changed: - gdm3 crashed with SIGTRAP in g_wakeup_new() from g_main_context_new() from g_dbus_connection_send_message_with_reply_sync() from g_dbus_connection_call_sync_internal() from g_dbus_connection_call_sync() + gdm3 crashed with SIGTRAP logging "Creating pipes for GWakeup: Too