Conversation
Notices
-
Great, no RSS feeds this morning
$ liferea
EGLDisplay Initialization failed: EGL_NOT_INITIALIZED
Cannot create EGL context: invalid display (last error: EGL_SUCCESS)
Segmentation fault
Anyone has any idea?
-
@condret no idea what that means
-
@coolboymew can you valgrind it?
-
@coolboymew do
echo $DISPLAY
what does it say
-
@Moon
Results in
:0
I have an inkling of what could be the problem now
CC: @olmitch
Alright, so I upgraded MX a while back and it did not seem to add the Wayland option to switch to it anywhere VS a fresh install. I'm guessing this is shit starting to possibly switch to wayland leaving me with some half broken shit now?
-
@coolboymew @olmitch I forgot about Wayland but your speculation seems likely.
-
@Moon @olmitch yeah and the login screen completely lacks the option to switch to wayland, as it should have
-
@condret I'm not a prog, I don't know what to do with that
-
@coolboymew valgrind liferea
this is how i usually approach segfaults
-
@condret this is the output
$ valgrind liferea
==15833== Memcheck, a memory error detector
==15833== Copyright (C) 2002-2022, and GNU GPL'd, by Julian Seward et al.
==15833== Using Valgrind-3.19.0 and LibVEX; rerun with -h for copyright info
==15833== Command: liferea
==15833==
==15833== Warning: set address range perms: large range [0x59c8b000, 0x99c8d000) (defined)
==15833== Warning: set address range perms: large range [0x99c8d000, 0x299c8d000) (defined)
==15833== Warning: set address range perms: large range [0x99c8d000, 0x100000000) (noaccess)
==15833== Warning: set address range perms: large range [0x200000000, 0x299c8d000) (noaccess)
EGLDisplay Initialization failed: EGL_NOT_INITIALIZED
Cannot create EGL context: invalid display (last error: EGL_SUCCESS)
==15833== Invalid read of size 8
==15833== at 0x742B7EB: ??? (in /usr/lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37.67.4)
==15833== by 0x58B8DF7: ??? (in /usr/lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37.67.4)
==15833== by 0xBCD4EA6: __pthread_once_slow (pthread_once.c:116)
==15833== by 0x58B7A3B: ??? (in /usr/lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37.67.4)
==15833== by 0x58B68CA: ??? (in /usr/lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37.67.4)
==15833== by 0x58BF12A: ??? (in /usr/lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37.67.4)
==15833== by 0x58BF1AC: ??? (in /usr/lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37.67.4)
==15833== by 0x58CAC49: ??? (in /usr/lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37.67.4)
==15833== by 0x5758DA1: ??? (in /usr/lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37.67.4)
==15833== by 0x5736F8B: ??? (in /usr/lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37.67.4)
==15833== by 0x57373B1: ??? (in /usr/lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37.67.4)
==15833== by 0x5776E66: ??? (in /usr/lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37.67.4)
==15833== Address 0x10 is not stack'd, malloc'd or (recently) free'd
==15833==
==15833==
==15833== Process terminating with default action of signal 11 (SIGSEGV)
==15833== Access not within mapped region at address 0x10
==15833== at 0x742B7EB: ??? (in /usr/lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37.67.4)
==15833== by 0x58B8DF7: ??? (in /usr/lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37.67.4)
==15833== by 0xBCD4EA6: __pthread_once_slow (pthread_once.c:116)
==15833== by 0x58B7A3B: ??? (in /usr/lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37.67.4)
==15833== by 0x58B68CA: ??? (in /usr/lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37.67.4)
==15833== by 0x58BF12A: ??? (in /usr/lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37.67.4)
==15833== by 0x58BF1AC: ??? (in /usr/lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37.67.4)
==15833== by 0x58CAC49: ??? (in /usr/lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37.67.4)
==15833== by 0x5758DA1: ??? (in /usr/lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37.67.4)
==15833== by 0x5736F8B: ??? (in /usr/lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37.67.4)
==15833== by 0x57373B1: ??? (in /usr/lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37.67.4)
==15833== by 0x5776E66: ??? (in /usr/lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37.67.4)
==15833== If you believe this happened as a result of a stack
==15833== overflow in your program's main thread (unlikely but
==15833== possible), you can try to increase the size of the
==15833== main thread stack using the --main-stacksize= flag.
==15833== The main thread stack size used in this run was 8388608.
==15833==
==15833== HEAP SUMMARY:
==15833== in use at exit: 5,947,312 bytes in 27,787 blocks
==15833== total heap usage: 203,952 allocs, 176,165 frees, 20,893,004 bytes allocated
==15833==
==15833== LEAK SUMMARY:
==15833== definitely lost: 0 bytes in 0 blocks
==15833== indirectly lost: 0 bytes in 0 blocks
==15833== possibly lost: 2,378,535 bytes in 498 blocks
==15833== still reachable: 3,293,641 bytes in 25,023 blocks
==15833== of which reachable via heuristic:
==15833== length64 : 810,504 bytes in 268 blocks
==15833== newarray : 14,168 bytes in 14 blocks
==15833== suppressed: 0 bytes in 0 blocks
==15833== Rerun with --leak-check=full to see details of leaked memory
==15833==
==15833== For lists of detected and suppressed errors, rerun with: -s
==15833== ERROR SUMMARY: 2 errors from 1 contexts (suppressed: 0 from 0)
Segmentation fault
-
@coolboymew but maybe i can help you debug the problem
-
@condret thankfully liferea kept a feed backup but every other RSS reader either sucks or seems to have troubles processing it
-
@condret ah no, fixed the Akregator bugs but closing it
-
@condret anyways, thanks, but don't waste your time on it, Akregator is working I guess, thanks to Liferea doing backups, so I don't have to go into an older install and fetch the database
-
@Moon @olmitch I decided fuck it, I just went with the flatpak version. It works????
-
@coolboymew @Moon thats also a solution! Debian packaged software is kind of dog shit lately, I was using flatpak more and more until I went back to an arch based system recently. Flatpak provides its own dependencies so it's in dependent from the OS
-
@olmitch @Moon I have no idea wtf happened because I didn't do any updates I recall of yesterday
-
@olmitch @Moon bruh. The flatpak liferea refuses to have anything render in the feed preview bar where it should show the content of the feed items
The fuck is going on