Porteus 5.0 RC2 DE bug reports

[Rava]

This thread is exclusively for bug reports concerning the variants of DE's [Desktop Environments] when it is obvious to the user the bug is not due to any underlying issue that is not part of the specific DE or not part of what X displays.

In case you are unsure if your Bug Report(s) fit in here just post in the main thread for 5.0rc2: Porteus 5.0 RC2 bug reports

(the thread is made in the hopes the DE maintainers or other DE experts can solve the issue or make changes to updated DE modules without the need to bother the usually already quite busy core developers and maintainers of the non-X-part of Porteus)
______________________________________________

And how could it be any other that the running DE issue I report is about XFCE (but I also came to like Openbox quite well):

I use an extra module for having leafpad as additional stand-alone editor besides mousepad: 030-leafpad-0.8.18.1-x86_64-2ponce.xzm - based on leafpad-0.8.18.1-x86_64-2ponce.txz due to me as power user had the occurrence that mousepad when being open in several windows with at times dozens of open texts loaded in each refused to react and was frozen for a seemingly unlimited time, and since only one mousepad instance is running, regardless of how many mousepad windows you have, it means all text files are frozen and possible several unsaved changes can be in jeopardy.

In 5.0rc1 I had nice distinctive different icons for mousepad and leafpad - but with 5.0rc2 it switched to the same icon for both:

What is the best approach for having a distinctive icon for an extra module and not a more generic one that is shared with more than one program?
I would like to edit my extra modules - in this case 030-leafpad-0.8.18.1-x86_64-2ponce.xzm - so that leafpad retains a more distinctive icon.

When I remember right, mousepad had a red icon and leafpad the more bland one, so if I recall correct, it is more correct to say that mousepad's icon changed and leafpad's icon either not changed or only slightly changed. Still I think when it comes to altering such things it is better altering the extra non-standard module than altering the main porteus module - in this case either keep 002-xorg.xzm and 003-xfce-4.12-20201108.xzm as they are - and instead edit 030-leafpad-0.8.18.1-x86_64-2ponce.xzm ( <- yes, I need to reboot to have the newer performance-based 003-xfce-4.12-20201211-performance.xzm

Okay, exiting X and deactivating 003-xfce-4.12-20201108.xzm and activating 003-xfce-4.12-20201211-performance.xzm might also work, since I usually always boot into "3" aka text mode aka Virtual Terminal (VT) mode and start X manually as guest user logged into one VT using the mere "startx" command. I am old-school like that. )

[donald]

Hi Rava
you could edit the .desktop file [ /usr/share/applications/ ]
..add a path to an existing icon.

My compiled Alsaplayer package/module had no nice Icon.
but this time I placed one in the module with a full path:
/usr/share/icons/hicolor/48x48/apps/alsaplayer.png
this one get picked up automatically.

[Rava]

you could edit the .desktop file [ /usr/share/applications/ ]
..add a path to an existing icon.

My compiled Alsaplayer package/module had no nice Icon.
but this time I placed one in the module with a full path:
/usr/share/icons/hicolor/48x48/apps/alsaplayer.png
this one get picked up automatically.

but first I would have to figure out what went different running 5.0rc2, preferable without the need to boot it …

I think my lsxzmgrep will be helpful (maybe I recall wrong and lsxzmgrep is by someone else.)

Here its code

Code: Select all

#!/bin/bash

for module in $(find $1 -type f -name "*.xzm"); do
    lsxzm ${module} | grep "$2" | sed -r "s#.+#${module}\n&#"
done

(could also be someone from the forum helped me with lsxzmgrep)

[Ed_P]

(could also be someone from the forum helped me with lsxzmgrep)

Well it appears the lsxzm part is from 82issa. Re: Must have apps - 64bit version (Post by 82issa #3522)
And the loop part is from brokenman. Re: search multiple modules (Post by brokenman #67979)

The 2nd line of many/most of my scripts is a # followed by the posting they originated from.

[Rava]

Well it appears the lsxzm part is from 82issa. Re: Must have apps - 64bit version (Post by 82issa #3522)
And the loop part is from brokenman. Re: search multiple modules (Post by brokenman #67979)

sounds plausible, usually I put in a comment when I received help for a script or function; at times when I only focus in getting it to work as intended I can forget adding any info of help or collaboration, looks like lsxzmgrep is of the later.

lsxzmgrep lacks the check for both parameters. Giving none would still search all modules in $PWD - but it would search for nothing, e.g. the whole execution would be pointless.
And it should check if run by root.

[donald]

leafpad icon
I extracted leafpad-0.8.18.1-x86_64-2_slonly.xzm > the icons are included.
They go into /usr/share/icons/hicolor/ and so on....
...seems that the elementary-dark icon theme does not care about hicolor..
( study index.theme if you like )

Quick fix:
open /usr/share/applications/leafpad.desktop and set
Icon=/usr/share/icons/hicolor/scalable/apps/leafpad.svg

[Ed_P]

Here its code

Code: Select all

#!/bin/bash

for module in $(find $1 -type f -name "*.xzm"); do
    lsxzm ${module} | grep "$2" | sed -r "s#.+#${module}\n&#"
done

The script is useful Rava. I just used it. Thank you for sharing.

[Rava]

Quick fix:
open /usr/share/applications/leafpad.desktop and set
Icon=/usr/share/icons/hicolor/scalable/apps/leafpad.svg

Thanks, will do.

The script is useful Rava. I just used it. Thank you for sharing.

It is helpful indeed, but it still should check the amount of parameter and tell the user what $1 and $2 are when started without any parameter.

Back when I put it together I just wanted it to do properly what I wanted it to do, and quick.

Since RL and the ridiculous lockdown - see Hysteria: COVID-19 for everybody. (Post by Rava #80392) - is keeping me too busy for having time to properly make lsxzmgrep more informative - without adding any bugs - but anyone if free to enhance it. *nudge* *nudge*

… then again, being imprisoned from 21:00 till 05:00 until at least Jan 10th might give me boredom and inspiration enhancing scripts - like lsxzmgrep.

[Rava]

Update

done the changes of

open /usr/share/applications/leafpad.desktop and set
Icon=/usr/share/icons/hicolor/scalable/apps/leafpad.svg

and ran update-menu - the menu icon of leafpad changed.
Icon of a new started leafpad in XFCE itself is still the same, though.

I will upgrade my leafpad module and presume after a reboot the icons of the leafpads in the XFCE DE will also be changed.

[donald]

Understanding the mechanics.

Elementary-xfce (dark) is a stripped down icon theme for xfce.
Leafpad doesn't belong to xfce = no Leafpad icon in that theme.
There is only a link leafpad.svg to accessories-text-editor.svg
which is the (bad) icon you see.

If you select the Paper icon theme (for Example) the real Leafpad icon
is displayed.

Note:
You may have to restart the panel manually,depending on which
003-xfce you use.
(003-xfce-4.12-20201108.xzm didn't refresh the panel automatically)

Code: Select all

guest@porteus:~$ xfce4-panel -r

Options:
a) edit the .desktop file in the Leafpad module
b) edit the .desktop file in /usr/share/applications
c) copy Leafpad icons into the elementary icon theme and
link them properly.

If you ask me, option b is the way to go = not altering the module
or the Icon theme.

ymmv, especially if the leafpad module is not always activated.

[Rava]

Understanding the mechanics.

That is usually always true. Like they used to write in the 1990th pre-internet Fido or Mousenet groups "Wer lesen kann, ist glatt im Vorteil"

ymmv, especially if the leafpad module is not always activated.

Usually it is, but… due to my main crashed internal partition grub4dos is no longer working, and while the Windoze-7 menu is working, the later grub menu is not working. And so nothing can be booted by internal hard drive. I plan on re-installing Witless-7 via its recovery function, which should install me a brand new version, and then I need to re-install grub4dos again to be able to boot a real OS like Puppy or Porteus. :-D

The windoze menu only had 2 entries: boot Linux (default, duh) and boot Windoze (none-default)

Then grub4dos will take over and load its c:/NST/menu.lst - but grub4dos is no longer functional due to c:/ being the crashed and currently still empty /dev/sda2

So I am using alternatively a 4 GB USB-stick.

But that one has only one partition - a FAT32 one, and I cannot set any symlinks to my rc1 and rc2 rootcopy folders on /dev/sda5 on that. (I presume I could use a cheatcode that uses UUID to link to the rootcopy/ folder on the internal hard drive - but then this USB stick would not work on any PC like it now does since then I would have to save the most recent file(s) in rootcopy/ on its rootcopy.xzm anyway)

So I have to save all and any changes via module, either via changed program module or via 992-rootcopy_5.0rc2_YYYY-MM-DD.xzm. (Since I run always fresh and not save any changes automatically)

Since I need to have the modules doubled for 5.0rc1 (sits in porteus/ ) and 5.0rc2 (sits in Porteus_5.0rc2/porteus ) anyway I choose to alter the 030-leafpad module - I use the original 030-leafpad-0.8.18.1-x86_64-2ponce.xzm for 5.0rc1 and the altered 030-leafpad-0.8.18.1-x86_64-2rava.xzm for 5.0rc2. Maybe I better should rename the latter one into 030-leafpad-0.8.18.1-x86_64-2_for_Porteus_5.0rc2-rava.xzm …

[Ed_P]

That sounds like a bad situation Rava.

I recommend copying your bootable USB drive to another USB drive and adding the r1/r2 symlinks to it so you can access your rootcopy folders on the harddrive.

I also recommend you backing up everything you want to save on that harddrive.

My backup desktop is Windows 7, and I like Windows 7, but Microsoft dropped support for it the end of last year so I don't know what you will end up with using your system's Windows Recovery function. And if you have problems there will be no help from Microsoft. See what your machine's vendor might suggest for a recovery approach.

[donald]

Super grub2 disk
https://www.supergrubdisk.org/

[Rava]

That sounds like a bad situation Rava.

There is a reason I created TestDisk & PhotoRec 7.2 WIP

I recommend copying your bootable USB drive to another USB drive and adding the r1/r2 symlinks to it so you can access your rootcopy folders on the harddrive.

I already have one of my many blue 8 GB USB sticks for that prepared.

I just wonder - sda1 aka System is still working. So is sda4 aka HDDRECOVERY and also sda5 aka intHDD1_5.

On sda1 are the boot files and probably kernel for Witless7. But more importantly all Linux initrds, kernels and compressed modules for:
one Puppy
one TinyCorePure
Several Porteus versions

It should be possible to only use syslinux and loading the menu of porteus.cfg from USB stick - while using UUID for loading initrd, kernel and compressed modules from sda1. At least I never attempted it, but it is possible thanks to the myriads of Porteus cheatcodes. Yay!

For now, running all from USB stick means the instance I remove that stick (e.g. by accident) brings instant death to the running Porteus.

I also recommend you backing up everything you want to save on that harddrive.

WIP.

My backup desktop is Windows 7, and I like Windows 7

My backup desktops are Puppy or TinyCorePure, and I like both Puppy and TinyCorePure, but despise all Windoze.
And for dozens of rational reasons.

but Microsoft dropped support for it the end of last year so I don't know what you will end up with using your system's Windows Recovery function. And if you have problems there will be no help from Microsoft.

I never went even once online with that Windoze, it knows nothing of any updates or support.

And there are enough Witless OS forums willing to give support. I just have to call SM-Witless7 not by its functional name (e.g. SM-Windoze or SM-Witzlos) but by its SM-Mickysøft øfficial næme.

See what your machine's vendor might suggest for a recovery approach.

Toshiba wanted me burning several DVDs as backup.
Supporting external harddrives: nope, not even Toshiba is that advanced.

And so I did such backup only once, many years ago.

But all that helps me getting to know TestDisk & PhotoRec 7.2 WIP better.

And last but not least my lsfind scripts based approach of indexing all my internal and external partitions is also helpful with recovery, since it knows a files original name by looking for the exact file size in the *.ls.gz file - and restoring the original folder structure via looking up the original file name in the *.find.gz file .

[Ed_P]

… then again, being imprisoned from 21:00 till 05:00 until at least Jan 10th might give me boredom and inspiration

When do you sleep?