Tout
n00b
Joined: 18 Jul 2020
Posts: 42
|
 Posted: Fri Oct 11, 2024 11:34 am Post subject: New version Conky segfault at boot using Gnome |
 |
|
Hi!
After updating conky, I noticed that conky is not starting at boot anymore. When looking at syslog, I see a segfault is occuring.
I have two instances of conky starting at boot. So for 3 boots I got this:
| Code: | Oct 11 10:23:50 main kernel: conky[3708]: segfault at 10 ip 00007f389c981424 sp 00007ffd490c8cd8 error 4 in libc.so.6[7f389c916000+148000] likely on CPU 5 (core 5, socket 0)
Oct 11 10:23:50 main kernel: conky[3698]: segfault at 10 ip 00007f980905f424 sp 00007ffe62afc248 error 4 in libc.so.6[7f9808ff4000+148000] likely on CPU 10 (core 2, socket 0)
Oct 11 10:57:03 main kernel: conky[3679]: segfault at 10 ip 00007fd5c871b424 sp 00007fff3cfd83d8 error 4 in libc.so.6[7fd5c86b0000+148000] likely on CPU 6 (core 6, socket 0)
Oct 11 10:57:04 main kernel: conky[3669]: segfault at 10 ip 00007f8d89f05424 sp 00007ffd23630158 error 4 in libc.so.6[7f8d89e9a000+148000] likely on CPU 10 (core 2, socket 0)
Oct 11 11:16:44 main kernel: conky[4769]: segfault at 10 ip 00007f0f3a23e424 sp 00007ffd65640ed8 error 4 in libc.so.6[7f0f3a1d3000+148000] likely on CPU 4 (core 4, socket 0)
Oct 11 11:16:44 main kernel: conky[4762]: segfault at 10 ip 00007f1715727424 sp 00007ffe6fb446f8 error 4 in libc.so.6[7f17156bc000+148000] likely on CPU 0 (core 0, socket 0)
|
Reverting to the old version of conky, it does not occur.
New version being: 1.21.7
Old version is: 1.19.8
When using the new version, I do not get any error when starting it AFTER boot. No segfaults occurring.
I use gnome and autostart conky with an autostart config. Trying to add a delay did not work, cause I don't know how to configure that correctly. The internet is giving me spread info on if that is still working in gnome autostart.
| Code: | ~/.config/autostart $ cat conky.desktop
[Desktop Entry]
Type=Application
Name=Conky
Exec=conky
X-GNOME-Autostart-Delay=120 |
Two questions:
1) Can I further investigate what is going wrong besides the syslog entry?
2) Is there a correct way of delaying in autostart? My current workaround is masking the new version. There could be an alternative workaround to delay start, but not sure if it will help. It might, because starting conky from prompt works once system is running.
Any help appreciated. |
|
Portage & Programming
