<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED FIXED - xorg-server-1.13.0: core dump on regen" href="https://bugs.freedesktop.org/show_bug.cgi?id=56608#c47">Comment # 47</a> on <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED FIXED - xorg-server-1.13.0: core dump on regen" href="https://bugs.freedesktop.org/show_bug.cgi?id=56608">bug 56608</a> from <a class="email" href="mailto:mmokrejs@fold.natur.cuni.cz" title="Martin Mokrejs <mmokrejs@fold.natur.cuni.cz>"> Martin Mokrejs</a> <pre>The whole year I used to live with logging in as a user and starting up startx manually. I tried to whether I could finally loging in through xdm window like years before. No, still not. I upgraded from x11-drivers/xf86-video-intel-2.21.6 to x11-drivers/xf86-video-intel-2.21.12 . I do NOT get core dumps anymore but still, my xdm window disappears after entering the Password[enter] and reappears back again with Login. I am not arguing the issue (core dumps) is fixed or not. So, what I want to report here is that at least, startx gives now some more interesting messages (to its STDOUT and STDERR, so they are in the VT console): <quote> (xfce4-session:3876): GLib-WARNING **: GError set over the top of a previous GError or uninitialized memory. This indicates a bug in someone's code. You must ensure an error is NULL before it's set. The overwriting error message was: Could not get owner of name 'org.freedesktop.ConsoleKit': no such name ** (xfce4-session:3876): CRITICAL **: dbus_set_g_error: assertion `gerror == NULL || *gerror == NULL' failed xfce4-session: Querying suspend failed: Could not get owner of name 'org.freedesktop.ConsoleKit': no such name xinit: connection to X server lost waiting for X server to shut down .Server terminated successfully (0). Closing log file. </quote> I will attach this as a full file. Second, I see that at least at the very moment, I do NOT have installed consolekit. I fear that X/xdm/pam/whoever is looking for consolekit and because of that /var/log/xdm.log says: <quote> xdm info (pid 3255): sourcing /usr/lib64/X11/xdm/TakeConsole XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0" after 286 requests (209 known processed) with 0 events remaining. xdm info (pid 3202): Starting X server on :0 ... xdm info (pid 3553): sourcing /usr/lib64/X11/xdm/Xsetup_0 xdm error (pid 3553): pam_authenticate failure: Error in service module xdm error (pid 3553): pam_authenticate failure: Error in service module xdm info (pid 3553): sourcing /usr/lib64/X11/xdm/GiveConsole xdm info (pid 3682): executing session /usr/lib64/X11/xdm/Xsession xdm info (pid 3553): sourcing /usr/lib64/X11/xdm/TakeConsole xdm info (pid 3202): Starting X server on :0 XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0" after 118 requests (111 known processed) with 0 events remaining. </quote> Here is what the package handling tool on Gentoo asks me to do now: <quote> [ebuild U ] xfce-base/libxfce4util-4.10.1 [4.10.0] [ebuild N ] x11-misc/xscreensaver-5.21 USE="jpeg opengl pam perl -gdm -new-login (-selinux) -suid -xinerama" [ebuild N ] sys-auth/polkit-0.111 USE="gtk introspection nls pam -examples -kde (-selinux) -systemd" [ebuild N ] gnome-extra/polkit-gnome-0.105 [ebuild N ] sys-auth/consolekit-0.4.5_p20120320-r2 USE="acl pam policykit -debug -doc (-selinux) {-test}" [ebuild U ] sys-auth/pambase-20120417-r2 [20120417-r1] USE="consolekit*" [ebuild N ] sys-power/upower-0.9.20-r2 USE="deprecated introspection -doc -ios -systemd" [ebuild U ] xfce-base/xfce4-session-4.10.1 [4.10.0-r1] USE="-systemd%" The following USE changes are necessary to proceed: (see "package.use" in the portage(5) man page for more details) # required by sys-auth/polkit-0.111[-systemd,pam] # required by sys-auth/consolekit-0.4.5_p20120320-r2[policykit] >=sys-auth/pambase-20120417-r2 consolekit # required by sys-auth/polkit-0.111[-systemd] # required by sys-power/upower-0.9.20-r2 # required by xfce-base/xfce4-session-4.10.1[udev] # required by @selected # required by @world (argument) >=sys-auth/consolekit-0.4.5_p20120320-r2 policykit </quote> So, could anything be done so that xdm would NOT even start if it cannot use PAM/consolekit? Or at least give a useful error message back to the XDM login window? Or xorg-server could complain during its startup? Possible similar issues: <a href="http://lists.freebsd.org/pipermail/freebsd-xfce/2012-November/000599.html">http://lists.freebsd.org/pipermail/freebsd-xfce/2012-November/000599.html</a> <a href="http://lists.freebsd.org/pipermail/freebsd-questions/2013-June/251744.html">http://lists.freebsd.org/pipermail/freebsd-questions/2013-June/251744.html</a> <a href="https://bbs.archlinux.org/viewtopic.php?id=132922">https://bbs.archlinux.org/viewtopic.php?id=132922</a></pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>