after killing 'seat0' due to not having a gdm login. (loginctl --terminate-seat seat0) etc
gdm3 1613 root 0r CHR 1,3 0t0 6 /dev/null gdm3 1613 root 1u unix 0xffff884865f68400 0t0 31869 type=STREAM gdm3 1613 root 2u unix 0xffff884865f68400 0t0 31869 type=STREAM gdm3 1613 root 3u a_inode 0,13 0 12692 [eventfd] gdm3 1613 root 4u a_inode 0,13 0 12692 [eventfd] gdm3 1613 root 5u unix 0xffff88485e5cf000 0t0 23297 type=STREAM gdm3 1613 root 6u a_inode 0,13 0 12692 [eventfd] gdm3 1613 root 7u unix 0xffff884861a29000 0t0 23307 @/tmp/dbus-sSMbCGqA type=STREAM gdm3 1613 root 8u unix 0xffff884861a2e000 0t0 23308 @/tmp/dbus-79fbBUC2 type=STREAM gdm3 1613 root 9u unix 0xffff88483adf3800 0t0 2100934 @/tmp/dbus-0dYR00N4 type=STREAM gdm3 1613 root 10u unix 0xffff88483adf3c00 0t0 2100935 @/tmp/dbus-q34pj5Rp type=STREAM gdm3 1613 root 11u REG 0,22 102 1260 /run/gdm3/auth-for-gdm-Oeih8z/database gdm3 1613 root 12u unix 0xffff88482dcfa000 0t0 23313 @/tmp/dbus-DSlORT3r type=STREAM gdm3 1613 root 13u unix 0xffff884861584800 0t0 2006939 type=STREAM gdm3 1613 root 14u unix 0xffff884868444000 0t0 29948 @/tmp/dbus-aoClxyNW type=STREAM gdm3 1613 root 15u unix 0xffff884868442c00 0t0 29949 @/tmp/dbus-TpHvgcEH type=STREAM gdm3 1613 root 16u unix 0xffff884866b38000 0t0 791260 @/tmp/dbus-7BEa2EQm type=STREAM gdm3 1613 root 17u unix 0xffff884866b3e000 0t0 791261 @/tmp/dbus-SOXIIEWV type=STREAM gdm3 1613 root 18u unix 0xffff88484b21f800 0t0 779751 type=DGRAM gdm3 1613 root 19u unix 0xffff884863d11c00 0t0 33651 @/tmp/dbus-TpHvgcEH type=STREAM gdm3 1613 root 20u unix 0xffff884843ce9400 0t0 33653 @/tmp/dbus-79fbBUC2 type=STREAM gdm3 1613 root 21u unix 0xffff88482dcf8c00 0t0 2049575 @/tmp/dbus-dq7sN3q4 type=STREAM gdm3 1613 root 22u unix 0xffff884832eafc00 0t0 40604 @/tmp/dbus-3bgOJJm0 type=STREAM gdm3 1613 root 23u unix 0xffff884832eaf400 0t0 40605 @/tmp/dbus-dq7sN3q4 type=STREAM gdm3 1613 root 24u unix 0xffff88483051c800 0t0 47039 @/tmp/dbus-TpHvgcEH type=STREAM gdm3 1613 root 25u unix 0xffff884861580400 0t0 2006940 @/tmp/dbus-UKbjR5Jj type=STREAM gdm3 1613 root 26u unix 0xffff884861580800 0t0 2006941 @/tmp/dbus-7fYVmno7 type=STREAM gdm3 1613 root 27u unix 0xffff88483adf6400 0t0 2100936 @/tmp/dbus-3dGDoAE8 type=STREAM gdm3 1613 root 28u unix 0xffff88484b1e5c00 0t0 798514 @/tmp/dbus-SOXIIEWV type=STREAM gdm3 1613 root 29u unix 0xffff88484962f400 0t0 800887 @/tmp/dbus-SOXIIEWV type=STREAM gdm3 1613 root 30u unix 0xffff88483422e000 0t0 813851 @/tmp/dbus-SOXIIEWV type=STREAM gdm3 1613 root 31u unix 0xffff88483adf2000 0t0 2100937 @/tmp/dbus-hip0Tu6H type=STREAM gdm3 1613 root 32u REG 0,22 102 1269 /run/gdm3/auth-for-adiete-Hre8N7/database gdm3 1613 root 33u unix 0xffff88482eaeac00 0t0 2032282 @/tmp/dbus-7fYVmno7 type=STREAM gdm3 1613 root 34u unix 0xffff884861501400 0t0 2057676 @/tmp/dbus-7fYVmno7 type=STREAM gdm3 1613 root 35u unix 0xffff884863d13c00 0t0 2060151 @/tmp/dbus-UKbjR5Jj type=STREAM gdm3 1613 root 36u unix 0xffff88482e8e9c00 0t0 2100939 @/tmp/dbus-3dGDoAE8 type=STREAM gdm3 1613 root 37u unix 0xffff88486628ec00 0t0 2103865 @/tmp/dbus-q34pj5Rp type=STREAM gdm3 1613 root 38u unix 0xffff8848342a5400 0t0 2098115 @/tmp/dbus-0dYR00N4 type=STREAM gdm3 1613 root 39u unix 0xffff88482e9eb400 0t0 2107730 @/tmp/dbus-H9Qhetwq type=STREAM gdm3 1613 root 40u unix 0xffff88486ae18000 0t0 2107731 @/tmp/dbus-tcfx7GEs type=STREAM On Wed, 12 Sep 2018 at 18:50, Daniel van Vugt <daniel.van.v...@canonical.com> wrote: > Thanks. Please keep a close eye on those ones that look similar: > > gdm3 1561 root 8u unix 0xffff995a67bdcc00 0t0 25239 > @/tmp/dbus-VGj4R3Fs type=STREAM > gdm3 1561 root 9u unix 0xffff995a67bdd000 0t0 25240 > @/tmp/dbus-NnCbDQ5S type=STREAM > gdm3 1561 root 10u unix 0xffff995a67bdf800 0t0 25241 > @/tmp/dbus-7L6kj5Hp type=STREAM > gdm3 1561 root 11u unix 0xffff995a67bdc800 0t0 25242 > @/tmp/dbus-rb6ixhfk type=STREAM > gdm3 1561 root 12u unix 0xffff995a65b22800 0t0 25246 > @/tmp/dbus-7L6kj5Hp type=STREAM > gdm3 1561 root 13u unix 0xffff995a2be27c00 0t0 25301 > type=STREAM > > and tell us if the number of those entries increases over time. > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1717670). > https://bugs.launchpad.net/bugs/1597150 > > Title: > 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() > > Status in gdm3 package in Ubuntu: > Confirmed > > Bug description: > The Ubuntu Error Tracker has been receiving reports about a problem > regarding gdm3. This problem was most recently seen with version > 3.20.1-0ubuntu1~xenial1, the problem page at > > https://errors.ubuntu.com/problem/f1a0b7d69a408c29549cadfaef83d29a10d491db > contains more details. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1597150/+subscriptions > -- 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 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/1597150/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
