XFCE mousepad Plugin directory '/usr/lib64/mousepad/plugins' not found

[Rava]

My system:

Code: Select all

root@porteus:~# cat /etc/porteus/*
001-core.xzm:20221006
002-xorg.xzm:20220723
002-xtra.xzm:20220630
003-xfce.xzm:20220925
initrd.xz:20220928

This happened after I activated the extra GTK3 module as needed e.g. for Redshift GUI, but i do not know if it's related to the activation of the module.
The module I activated after bootup is this:
021-libgtk+libgdk-x11-2.0.so.0.2400.33.xzm
its sole quite minimal contents:

Code: Select all

/usr
/usr/lib64
/usr/lib64/libgdk-x11-2.0.so
/usr/lib64/libgdk-x11-2.0.so.0
/usr/lib64/libgdk-x11-2.0.so.0.2400.33
/usr/lib64/libgtk-x11-2.0.so
/usr/lib64/libgtk-x11-2.0.so.0
/usr/lib64/libgtk-x11-2.0.so.0.2400.33

These should not interfere with '/usr/lib64/mousepad/plugins' or with the folder '/usr/lib64/mousepad/' to disappear.

Previously when I used in the guest terminal "mousepad whatever.txt" then the current running mousepad was put on the then active desktop and the text file opened in it, freeing the terminal without the need of adding a " &" at the end.
Now with that issue a new mousepad gets opened and the terminal is blocked unless I exit that new mousepad or put it into background by

Code: Select all

Ctrl+Z
bg

Does anyone have an idea what could have caused the folder '/usr/lib64/mousepad/' to disappear since I did not delete that folder?

Added in 31 minutes 10 seconds:
I now rebooted and used the boot device where mousepad previously ran without issue but it still gives me the same error. It's a mystery for now since the 4.16 XFCE module should be the very same that previously had no such issues but looking into it via my lsxzmgrep script there is no such folder as '/usr/lib64/mousepad/

I look into the md5sums of the used modules and report back.

Added in 23 minutes 29 seconds:
Update
this module

Code: Select all

4f61156879b273749c3af1d2b245c41b  003-xfce-4.16.xzm

is the one I am using (aka "003-xfce-4.16-20220925") contains no such folder:

Code: Select all

root@porteus:/mybin/linux/porteus/5.0/x86-64# lsxzmgrep 003-xfce-4.16.xzm usr/lib64/mousepad/
lsxzmgrep V2020-12-19
root@porteus:/mybin/linux/porteus/5.0/x86-64#

Any ideas why mousepad previously worked fine but now misses the /usr/lib64/mousepad/ folder that was never a part of 003-xfce-4.16.xzm to begin with?

Added in 34 minutes 23 seconds:
Even more weird, after initially testing mousepad via terminal and it giving me the

Code: Select all

mousepad Plugin directory '/usr/lib64/mousepad/plugins' not found

error, now I again used it via terminal, it once more like yesterday and all the previous days it silently opens the file in the already running mouspad instance (moving that from another desktop to the currently used one) - and no directory '/usr/lib64/mousepad/plugins' not found error is displayed (like in the past when it worked as it should) while the very folder /usr/lib64/mousepad/ is still none existing.
I do not get it.

[fulalas]

@Rava, there's nothing wrong here. Mousepad has support to plugins, but by default it doesn't ship with any hence why we don't even have plugins folder -- maybe we can add an empty folder for the next release just to make Mousepad less grumpy

[Ed_P]

FWIW

Code: Select all

guest@porteus:~$ su
Password: 
root@porteus:/home/guest# /usr/lib64/mousepad/
bash: /usr/lib64/mousepad/: No such file or directory
root@porteus:/home/guest# 

root@porteus:/home/guest# cat /etc/porteus/*
001-core.xzm:20221006
002-xorg.xzm:20221006
002-xtra.xzm:20220630
003-cinnamon.xzm:20220925
initrd.xz:20220928

[Rava]

@Rava, there's nothing wrong here. Mousepad has support to plugins, but by default it doesn't ship with any hence why we don't even have plugins folder -- maybe we can add an empty folder for the next release just to make Mousepad less grumpy

I have still no clue why the error did happen.

Usually mousepad doesn't care about the non existing plugins folder. Why it did display the error and why it was unable to access the running process I have no clue.
After a reboot (darn these extra buttons in the darkness, you so easily press them by mistake. ) all is back to normal and mousepad acts like it did in the past, accessing the already running process and never displaying that one error, just like it did in the past.