SliTaz Forum

tcll

Member

Registered: 2026-01-25

Posts: 31

Beaver editor appimage issues

ok, so this is either a lack of documentation problem

or a hard-coded path problem

so I was doing what I do normally with many other programs I like and building an appimage of them before removing them from the system

I was able to get an appimage for beaver completely built and working

but once I uninstalled it completely (just with tazpkg, not my local appimage), I'm now getting:

[c]** Message building menus failed: Failed to open file '/usr/share/beaver/resource/standard.xml': No such file or directory[/c]

looking through the source lead me to this in [c]interface.c[/c]:

[c]gtk_ui_manager_add_ui_from_file (MenuManager, RESOURCE_DIR "/standard.xml",[/c]

but I'm not sure if [c]RESOURCE_DIR[/c] is a hard path, or an XDG data path I can override in my AppRun

is there any sort of env var I can override for this??

I do already have:

[c]DEFAULT_XDG_DATA_DIRS='./share/:/usr/share/gnome:/usr/local/share/:/usr/share/'[/c]

[c]export XDG_DATA_DIRS="${HERE}/usr/share/:${XDG_DATA_DIRS:-$DEFAULT_XDG_DATA_DIRS}"[/c]

in my AppRun, so that should be getting picked up, which leads me to believe the path is hard-coded

but I'd like some verification on that if it is or not

I really like this editor as a replacement for Mousepad, but if I can't run it as an appimage, well... I guess that's a problem

tcll

Member

Registered: 2026-01-25

Posts: 31

Re: Beaver editor appimage issues

I guess I'll just do what I did to my xorg appimage for now and create a symlink at [c]/usr/share/beaver[/c] to my appimage

xorg needs a symlink at [c]/usr/bin/xkbcomp[/c] because that path is hard coded for some reason