[systemd-devel] remove Support + Documentation message?
Hi Zbyszek, ok, all your points taken. Do you mean that this *S**upport + Documentation* message was or should be removed? Well Manjaro takes all the ARCH packages. We are +/- 2 Weeks behind ARCH for testing reasons. Well if you say so, i'll tell them to remove this. But i think this comes from ARCH. Do you have some link when this was removed years ago, just in case someone does not belive me... --- first start to complain at your distribution for that nonsense which was removed from systemd years ago: -- Support:https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- Documentation:man:core(5) -- regards LF On 30.04.19 14:00, systemd-devel-requ...@lists.freedesktop.org wrote: Send systemd-devel mailing list submissions to systemd-devel@lists.freedesktop.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.freedesktop.org/mailman/listinfo/systemd-devel or, via email, send a message with subject or body 'help' to systemd-devel-requ...@lists.freedesktop.org You can reach the person managing the list at systemd-devel-ow...@lists.freedesktop.org When replying, please edit your Subject line so it is more specific than "Re: Contents of systemd-devel digest..." Today's Topics: 4. Re: systemd-coredump[2529]: Process 2326 (xfwm4) of user 1000 dumped core maybe because of lightdm[2482]: gkr-pam: unable to locate daemon control file (Reindl Harald) -- -- Message: 4 Date: Mon, 29 Apr 2019 21:43:40 +0200 From: Reindl Harald To:systemd-devel@lists.freedesktop.org Subject: Re: [systemd-devel] systemd-coredump[2529]: Process 2326 (xfwm4) of user 1000 dumped core maybe because of lightdm[2482]: gkr-pam: unable to locate daemon control file Message-ID: Content-Type: text/plain; charset=utf-8 --- first start to complain at your distribution for that nonsense which was removed from systemd years ago: -- Support:https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- Documentation:man:core(5) -- ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemd-coredump[2529]: Process 2326 (xfwm4) of user 1000 dumped core maybe because of lightdm[2482]: gkr-pam: unable to locate daemon control file
Hi Zbyszek, i've already did this. It started after desktop freezes here: https://forum.manjaro.org/t/xfce-desktop-freezes-after-automated-screen-lock-manjaro-18-0-4-illyria/84717/12 which were solved, but there are still systemd-coredump's and see comments 33 to 36 here: https://bugzilla.xfce.org/show_bug.cgi?id=15325#c33 LF On 29.04.19 21:29, Zbigniew Jędrzejewski-Szmek wrote: On Mon, Apr 29, 2019 at 09:22:30PM +0200, linuxfr...@gmx.at wrote: Hi, i do not know who is the correct person / mailing list, to ask for this one. 1) screen-lock locks the screen (OK) 2) screensaver comes and screen is going to be black. (OK) 3) Everytime i unlock my locked screen (after the screensaver kicked in) i got this:*systemd-coredump* (NOT OK) What are the next steps to fix this? regards LF *Apr 29 21:08:37 lightdm[2482]: gkr-pam: unable to locate daemon control file** **Apr 29 21:08:40 systemd-coredump[2529]: Process 2326 (xfwm4) of user 1000 dumped core.* Please take this up with your distribution, component xfwm4. Most likely this has nothing to do with systemd. Zbyszek ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] systemd-coredump[2529]: Process 2326 (xfwm4) of user 1000 dumped core maybe because of lightdm[2482]: gkr-pam: unable to locate daemon control file
Hi, i do not know who is the correct person / mailing list, to ask for this one. 1) screen-lock locks the screen (OK) 2) screensaver comes and screen is going to be black. (OK) 3) Everytime i unlock my locked screen (after the screensaver kicked in) i got this:*systemd-coredump* (NOT OK) What are the next steps to fix this? regards LF *Apr 29 21:08:37 lightdm[2482]: gkr-pam: unable to locate daemon control file** **Apr 29 21:08:40 systemd-coredump[2529]: Process 2326 (xfwm4) of user 1000 dumped core.* Stack trace of thread 2326: #0 0x7f35c1525186 n/a (libglib-2.0.so.0) #1 0x7f35c1522f5c g_log_writer_default (libglib-2.0.so.0) #2 0x7f35c1519a49 g_log_structured_array (libglib-2.0.so.0) #3 0x7f35c1521f0d g_log_structured_standard (libglib-2.0.so.0) #4 0x7f35c187e54e n/a (libgdk-3.so.0) #5 0x7f35c188b6e5 n/a (libgdk-3.so.0) #6 0x7f35c11a652a _XError (libX11.so.6) #7 0x7f35c11a33f8 n/a (libX11.so.6) #8 0x7f35c11a34a5 n/a (libX11.so.6) #9 0x7f35c11a4410 _XReply (libX11.so.6) #10 0x7f35c2047742 XIQueryDevice (libXi.so.6) #11 0x7f35c187b1bd n/a (libgdk-3.so.0) #12 0x7f35c188636d n/a (libgdk-3.so.0) #13 0x7f35c1885e36 n/a (libgdk-3.so.0) #14 0x7f35c184eea2 gdk_display_get_event (libgdk-3.so.0) #15 0x7f35c1885aa4 n/a (libgdk-3.so.0) #16 0x7f35c152b7bf g_main_context_dispatch (libglib-2.0.so.0) #17 0x7f35c152d739 n/a (libglib-2.0.so.0) #18 0x7f35c152e6d2 g_main_loop_run (libglib-2.0.so.0) #19 0x7f35c1b56e6f gtk_main (libgtk-3.so.0) #20 0x55dba8e9a765 n/a (xfwm4) #21 0x7f35c0c55ce3 __libc_start_main (libc.so.6) #22 0x55dba8e9a95e n/a (xfwm4) Stack trace of thread 2328: #0 0x7f35c0d220d1 __poll (libc.so.6) #1 0x7f35c152d690 n/a (libglib-2.0.so.0) #2 0x7f35c152e6d2 g_main_loop_run (libglib-2.0.so.0) #3 0x7f35c0639568 n/a (libgio-2.0.so.0) #4 0x7f35c1508c21 n/a (libglib-2.0.so.0) #5 0x7f35c0dfea92 start_thread (libpthread.so.0) #6 0x7f35c0d2ccd3 __clone (libc.so.6) Stack trace of thread 2339: #0 0x7f35c0e04bac pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0) #1 0x7f35bc8411e4 n/a (nouveau_dri.so) #2 0x7f35bc840f08 n/a (nouveau_dri.so) #3 0x7f35c0dfea92 start_thread (libpthread.so.0) #4 0x7f35c0d2ccd3 __clone (libc.so.6) Stack trace of thread 2327: #0 0x7f35c0d220d1 __poll (libc.so.6) #1 0x7f35c152d690 n/a (libglib-2.0.so.0) #2 0x7f35c152d77e g_main_context_iteration (libglib-2.0.so.0) #3 0x7f35c152d7d2 n/a (libglib-2.0.so.0) #4 0x7f35c1508c21 n/a (libglib-2.0.so.0) #5 0x7f35c0dfea92 start_thread (libpthread.so.0) #6 0x7f35c0d2ccd3 __clone (libc.so.6) -- Subject: Speicherabbild für Prozess 2326 (@COREDUMP_COMM)
