Lfs 8.3 systemd programs not opening?
 

Hi All,
After having so much fun doing 8.3 on one of my laptops I decided to do the other.Everything went well until I installed Abiword. I'm using xfce4 for my DTE. I must have missed a program or something somewhere. Firefox works fine. When I click on Abi
it opens for about 1 second and then closes. I appreciate any and all help.
Thanks a bunch

ran abi in terminal

bash-4.4$ abiword

(process:2619): Gtk-WARNING **: 17:02:37.455: Locale not supported by C library.
Using the fallback 'C' locale.

(abiword:2619): Gtk-CRITICAL **: 17:02:37.713: gtk_render_background: assertion 'GTK_IS_STYLE_CONTEXT (context)' failed

(abiword:2619): Gtk-CRITICAL **: 17:02:37.713: gtk_render_frame: assertion 'GTK_IS_STYLE_CONTEXT (context)' failed
Aborted (core dumped)
bash-4.4$

I would normally take those "Gtk-CRITICAL **" errors an GTK needing tranquilizers, or the software equivalent. I get it shrieking at me here and everything's fine (usually). The core dumped is a different matter. That's a miscompile or a bug.

Run 'ldd /path/to/abiword |grep found' which should return no output. If it does give anything, it will be of the nature: "libThisOrThat.so not found." Check they're available and not buried in some library directory that never gets checked, and check for newbie 32/64 bit mistakes.

This is what showed:
ldd: /path/to/abiword: No such file or directory

seeing you have a bash-4.4$ prompt tells me you skipped installing the first thing necessary for starting to build blfs packages and that's BLFS Bash Shell Startup files. The ramifications are staggering. Lucky anything works right imo.
You can try and add them now and see if it helps your build find things it needs to run right. GTK-criticals are bad... warnings or info are ok.

/Sigh
If you typed in exactly what I wrote, that's correct. You were supposed to substitute /path/to with /usr/bin, or wherever abiword actually is. How do I know where abiword is on your box?

"Aborted" (as distinct from "Segment violation") indicates that the gtk library called an abort itself after an internal test failed. In other words, it's not a bug in the code, it's a problem with your system. I would be inclined to rebuild gtk, and perhaps its main dependencies, after fixing your environment as arch-linq suggested.

Thanks to all,
I must have missed something. I will go reinstall bash startup files at the beginning of blfs. Something didn't copy and paste somewhere I guess. And rebuild GTK

I will mention one other thing. Having just done LFS-8.3-systemd, but not started on BLFS yet, it seems they add a few bootscripts to LFS; the systemd vartiant doesn't want bootscripts but the systemd equivalent. That may be another issue.

I would indeed bow to hazel's superior detective work on GTK. I have learned to ignore almost everything it complains about, but it doesn't go Critical.

I think it possibly could be this Toshiba laptop too. 8.3 Systemd worked fine on my HP laptop and I even cloned it and put it on my
AMD desktop and its doing good. But I even tried to put the clone on the Toshiba but it wouldn't work either. If it doesn't work on
the Toshiba its ok. Just a lot of time, but when you are retired I guess I got plenty of that heading in to winter. I will keep fooling with it
and maybe I will learn something new. And yes, I always pay attention to Hazel's suggestions.

Solved
 

That fixed it with advice from Hazel and Arch-ling.
Thanks to you all

What exactly was the fix? I'm curious.

Hey Hazel,
I went to the beginning of blfs to bash startup files and copied and pasted them again. Then I reinstalled GTK+3.24.30 with required dependencies first.
I also looked at kernel config and made sure I disabled anything with AMD checked. Rebooted and abiword was good along with a few other things.
I'm now working on video player and sound. Hope to be finished this weekend with a basic system.
Regards
Dan