Vanilla Dpup 11.0.x Development Builds

[dimkr]

If you upgraded from <11.0.196, start a new save.

su is not supposed to work because root has no password, it's a very common system hardening technique. Use pkexec to run stuff as root.

(This is equivalent to the situation in distros that ship with sudo preinstalled. They don't allow login as root.)

[Keef]

I knew there was something about su that I'd forgotten.
I'll start with a new save. I only kept it because of the problems with connman-gtk.

[Keef]

Should the yad yes/no dialog still appear when root permissions are needed? I only get it on shutdown/reboot. Otherwise it is a pkexec terminal window asking for the root password. Mostly I can just hit enter and it closes. However, apt only works if I use the root password 'woofwoof', which I thought was no longer used.
I'd provide a screen shot, but the forum is still not displaying them for me (at least in preview).
Yes, I am using a fresh install and savefolder.

[dimkr]

Otherwise it is a pkexec terminal window asking for the root password. Mostly I can just hit enter and it closes. However, apt only works if I use the root password 'woofwoof', which I thought was no longer used.

If you provide spot's password (default is woof woof), it runs the application as root. If you close the window, don't type any password or provide the wrong password, it doesn't run the application. root has no password.

[Keef]

Ah yes. I understand now. Got there in the end.

[d-pupp]

@dimkr I'm just wondering what's left on your todo list for Dpup 11?

I'm daily driving 197. However I see 200 is out now can I use the same save folder when I upgrade?

[dimkr]

Currently the TODO list is only bug fixes and polish. I don't have plans for more features, all the big stuff (unprivileged users, better multi-monitor support, security hardening, build system simplification) is in place.

I think you should be able to continue with the same save file from 11.0.197, but if things don't work well you can start with a new save.

[d-pupp]

Thanks @dimkr for creating dpup. It works well for me.
I think security and hardening are a necessary step. Even if it is sometimes a pain. The way things are going I may even put clamav on at some point. Unfortunately the world is changing or at least my view of it.

Have a good day and I'll let you know about dpup 200 ... If there is anything to report.

[TerryH]

I haven't use Vanilla Dpup for a couple of months. I just did a new manual clean install on the internal nvme drive on my laptop. So far programs are running smoothly. Thanks for the continued development of Vanill Dpup

In setting the install up I attempted to make some configuration changes and see that some of spot's directories have ownership root:root. The directories are :
/home/spot/.config/geany
/home/spot/.config/gtk-3.0
/home/spot/.config/l3afpad
/home/spot/.config/spacefm
/home/spot/.thumbnails

Are these ownerships intentional? To do my change I changed the ownership of the spacefm directory to spot:spot.

[dimkr]

@TerryH No, they must be spot:spot. Are you sure you didn't change ownership?

[TerryH]

@TerryH No, they must be spot:spot. Are you sure you didn't change ownership?

Nothing I had done should have changed any ownership. This morning I have done the setup of another new installation 3 times, all directories/files have correct ownership spot:spot.

How I did my set up. In EasyOS I downloaded and the Vanilla Dpup 11.0.200 image, extracted using uextract. Manually copied components including save folder to a folder on my internal drive. I added a boot stanza to my grub.cfg.

On initial boot I was asked for a password, I tried many things: woofwoof; woof woof; woof; root or no password just hit Enter. I get an error 'Failed to add key:Operation not supported', then pause 60 seconds, followed by desktop being displayed. At this stage system seems functional, but any attempt to save (using 'Save changes') does not appear to work and following Shutdown/Restart, when I booted this install my changes hadn't been saved. Maybe I should have reported this issue, but as I don't normally use encryption I decided to just bypass this and not use encryption.

I deleted the save folder and re-copied it from the extracted image again. This time I deleted the .pfscrypt file to boot without encryption. This was successful. Saves and Shutdown/Restart were functioning correctly. I have redone this again 3 times today, including attempts to use encryption(which again failed). All saves had correct ownerships.

I did nothing to explicitly change ownership, or to even inadvertently change ownership. How 5 random directories in /home/spot had ownership incorrectly set, is baffling. It may have to remain a mystery.

[dimkr]

including attempts to use encryption(which again failed).

How did you enable encryption? Did you use the pupsave tool?

[TerryH]

including attempts to use encryption(which again failed).

How did you enable encryption? Did you use the pupsave tool?

I didn't, I stated I attempted to try to use encryption, which failed as had occurred each time. All my installs are unencrypted.

[TerryH]

I am looking for the location of the white icons which are used in the waybar bar2 (program launchers). I have searched throughout /usr/share. I have also done a forum search to check if mentioned in the forum. Thanks in advance for any assistance.

[TerryH]

I was testing bluetooth functionality. I was able to successfully connect bluetooth speaker and Ear buds. The issue is when connected/disconnect they are leaving the message as an artifact on the screen, which I am not able to get rid of. See screen shot image of multiple connection/disconnections.

Edit: Unfortunately the forum won't display my screenshot correctly, in either png or jpg format. The image has the screen with multiple message boxes displayed on the screen, for each change of state. As well a little bluetooth icons for each message box in the main waybar. They can't be clicked or moved.

Edit 2: On reboot the ear buds which were last connected, autoconnected and are working nicely. Thankfully there isn't a message box displayed for this connection.

Note: Re-uploaded the screenshot image.

[dimkr]

I didn't, I stated I attempted to try to use encryption, which failed as had occurred each time. All my installs are unencrypted.

It failed because you didn't enable support for encryption, you just copied a directory. Use pupsave to create a new save folder correctly.

I am looking for the location of the white icons which are used in the waybar bar2 (program launchers).

These are not icons, but glyphs from the FontAwesome font. See ~/.config/waybar/style.css and https://fontawesome.com/v4/icons/.

[d-pupp]

@TerryH
To post to the forum you need to turn off resist fingerprinting in Firefox
about:config search for privacy.resistFingerprinting = true and change it to false

It's a good idea to turn it back on again after your done.

[TerryH]

I didn't, I stated I attempted to try to use encryption, which failed as had occurred each time. All my installs are unencrypted.

It failed because you didn't enable support for encryption, you just copied a directory. Use pupsave to create a new save folder correctly.

I am looking for the location of the white icons which are used in the waybar bar2 (program launchers).

These are not icons, but glyphs from the FontAwesome font. See ~/.config/waybar/style.css and https://fontawesome.com/v4/icons/.

Thank you, the website is a good help.