systemd: outdated messages about Support and Documentation ?

Manjaro Development Testing Branch
#1

Hi,
during some investigations, the people of systemd-devel-requestNO-SPAMlists.freedesktop.org told me that there are outdated messages after a back trace.


---------------

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)


------------------------------

Meant were the last entries here:

systemd-coredump

Apr 30 18:37:08 systemd-coredump[1042]: Process 690 (xfwm4) of user 1000 dumped core.

                                            Stack trace of thread 690:
                                            #0  0x00007f4aaf99d186 n/a (libglib-2.0.so.0)
                                            #1  0x00007f4aaf99af5c g_log_writer_default (libglib-2.0.so.0)
                                            #2  0x00007f4aaf991a49 g_log_structured_array (libglib-2.0.so.0)
                                            #3  0x00007f4aaf999f0d g_log_structured_standard (libglib-2.0.so.0)
                                            #4  0x00007f4aafcf654e n/a (libgdk-3.so.0)
                                            #5  0x00007f4aafd036e5 n/a (libgdk-3.so.0)
                                            #6  0x00007f4aaf61e52a _XError (libX11.so.6)
                                            #7  0x00007f4aaf61b3f8 n/a (libX11.so.6)
                                            #8  0x00007f4aaf61b4a5 n/a (libX11.so.6)
                                            #9  0x00007f4aaf61c410 _XReply (libX11.so.6)
                                            #10 0x00007f4ab04bf742 XIQueryDevice (libXi.so.6)
                                            #11 0x00007f4aafcf31bd n/a (libgdk-3.so.0)
                                            #12 0x00007f4aafcfe36d n/a (libgdk-3.so.0)
                                            #13 0x00007f4aafcfde36 n/a (libgdk-3.so.0)
                                            #14 0x00007f4aafcc6ea2 gdk_display_get_event (libgdk-3.so.0)
                                            #15 0x00007f4aafcfdaa4 n/a (libgdk-3.so.0)
                                            #16 0x00007f4aaf9a37bf g_main_context_dispatch (libglib-2.0.so.0)
                                            #17 0x00007f4aaf9a5739 n/a (libglib-2.0.so.0)
                                            #18 0x00007f4aaf9a66d2 g_main_loop_run (libglib-2.0.so.0)
                                            #19 0x00007f4aaffcee6f gtk_main (libgtk-3.so.0)
                                            #20 0x000055ea1c733765 n/a (xfwm4)
                                            #21 0x00007f4aaf0cdce3 __libc_start_main (libc.so.6)
                                            #22 0x000055ea1c73395e n/a (xfwm4)
                                            
                                            Stack trace of thread 702:
                                            #0  0x00007f4aaf19a0d1 __poll (libc.so.6)
                                            #1  0x00007f4aaf9a5690 n/a (libglib-2.0.so.0)
                                            #2  0x00007f4aaf9a66d2 g_main_loop_run (libglib-2.0.so.0)
                                            #3  0x00007f4aaeab1568 n/a (libgio-2.0.so.0)
                                            #4  0x00007f4aaf980c21 n/a (libglib-2.0.so.0)
                                            #5  0x00007f4aaf276a92 start_thread (libpthread.so.0)
                                            #6  0x00007f4aaf1a4cd3 __clone (libc.so.6)
                                            
                                            Stack trace of thread 701:
                                            #0  0x00007f4aaf19a0d1 __poll (libc.so.6)
                                            #1  0x00007f4aaf9a5690 n/a (libglib-2.0.so.0)
                                            #2  0x00007f4aaf9a577e g_main_context_iteration (libglib-2.0.so.0)
                                            #3  0x00007f4aaf9a57d2 n/a (libglib-2.0.so.0)
                                            #4  0x00007f4aaf980c21 n/a (libglib-2.0.so.0)
                                            #5  0x00007f4aaf276a92 start_thread (libpthread.so.0)
                                            #6  0x00007f4aaf1a4cd3 __clone (libc.so.6)
                                            
                                            Stack trace of thread 851:
                                            #0  0x00007f4aaf27cbac pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
                                            #1  0x00007f4aa6d691e4 n/a (nouveau_dri.so)
                                            #2  0x00007f4aa6d68f08 n/a (nouveau_dri.so)
                                            #3  0x00007f4aaf276a92 start_thread (libpthread.so.0)
                                            #4  0x00007f4aaf1a4cd3 __clone (libc.so.6)


 Subject: Speicherabbild für Prozess 690 (@COREDUMP_COMM) generiert
 Defined-By: systemd
 Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
 Documentation: man:core(5)
 Prozess 690 (xfwm4) ist abgebrochen worden und
 ein Speicherabbild wurde generiert.
 
 Üblicherweise ist dies ein Hinweis auf einen Programmfehler und sollte
 als Fehler dem jeweiligen Hersteller gemeldet werden.

I have asked:

Hi Zbyszek,
ok, all your points taken.
Do you mean that this Support + 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...

The answer was:

The idea is that downstreams use the "support-url" meson build-time
option to direct support requests to one of their own sites.
Lennart

Lennart Poettering, Berlin

So what is to do here?
LF

#2

True with most packages.
But manjaro takes SystemD directly from upstream and package it.
So yes, it's the systemd package maintainer here at Manjaro that needs to remove that it seems.

#3

@oberon then :kissing_heart:

1 Like
#4

We compile systemd ourselves, but use a very similar PKGBUILD as Archlinux does. It can be found here
As you can see we pull the source from
https://github.com/systemd/systemd and
https://github.com/systemd/systemd-stable

That's nonsense! I don't really see where this message originally comes from, but we certainly don't add it. Possible that there would be an option to override it with a custom message as explained by Mr Poettering. But since we currently don't specify support-url in our build, I can only assume that it's the default.

What do you mean? I don't see the 'Support' message mentioned anywhere.

Stack trace of thread 851:
#0  0x00007f4aaf27cbac pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
#1  0x00007f4aa6d691e4 n/a (nouveau_dri.so)
#2  0x00007f4aa6d68f08 n/a (nouveau_dri.so)
#3  0x00007f4aaf276a92 start_thread (libpthread.so.0)
#4  0x00007f4aaf1a4cd3 __clone (libc.so.6)
#5

Hi,
sorry it was an formatting error...
after the backtrace this final lines


-- Subject: Speicherabbild für Prozess 690 (@COREDUMP_COMM) generiert
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: man:core(5)
-- 
-- Prozess 690 (xfwm4) ist abgebrochen worden und
-- ein Speicherabbild wurde generiert.
-- 
-- Üblicherweise ist dies ein Hinweis auf einen Programmfehler und sollte
-- als Fehler dem jeweiligen Hersteller gemeldet werden.

there is Support: https://lists.freedesktop.org/... and Documentation: man core (5).
This was ment.

(Also about the bit harsh answer, i think there are maybe some different politics about that feature, that now is a bug (-:wink:

#6

Maybe the smart guy then should have a look at their own code?
Anyway, we will use the meson build-option to override it with something custom manjaro ... :sunglasses:

4 Likes
#7

I have now overwritten this 'support url' message in systemd 242.19-2, currently on the unstable branch.
Should make everybody happy, I guess, although it's probably always better to NOT see the message anywhere, anyway :laughing:
Cheers! :partying_face:

Back in Time nicht aktualisierbar
[Unstable Update] 2019-05-03 - Kernels, Backintime, Palemoon
#8

Well lets say polite, i have seen friendly people @ the linuxworld and stressed people. We do not know how much workload they have. So now they wont get much noise from us anymore :wink:

#9

This topic was automatically closed after 90 days. New replies are no longer allowed.

Forum kindly sponsored by