New ISO build to try.

sleekmason · 2022-03-26 14:45:26

@eight.bit.al,

Absolutely awesome!

This is exactly the feedback I need! Thank you:)

For each of those, I will certainly look and enable if I am able to. I may have to ask a question or two to get it done. These should be in the next builds:)

I am currently building to upload new releases starting tonight/tomorrow? if everything checks out. Misko_2083's version of the random wallpaper changer is included as well, and it is pretty dang neat. When enabled, look in the system tray for the new icon. right-click gives options, left-click gives a wallpaper shuffler that can be left open and moved.

Using any of the latest couple images, there should be an option listed under Utilities --> Extras to add the backports repo, and if desired, the fasttrack repos as well.

Yeah, time to remove the fbpanel option I suppose. You are right about the tinkering:) The fbpanel option was back when I was toggling between four window managers on the fly using the lxde session manager. It worked kinda sorta good? Was pretty cool anyway:) I kept fbpanel for an option because visually is kind of cool, and I had combined tint2 and fbpanel to create 'Monter panel' lol. People can still grab all this kind of stuff from my github though anything old is kind of jumbled together.

Thank you so much for both your thoughts and kind words. It must have been some work to get it all together. I will certainly do what I can.

I'll post again too, when I get at least the main amd-64 image up. It is very fickle to upload to Sourceforge sometimes. They must get tons of weird stuff going on. I've been dropped at %99 on an upload before. Wild.

*Edit - The screenshot choice! Just didn't know, and found it easy to use:)

Last edited by sleekmason (2022-03-26 16:22:30)

sleekmason · 2022-03-27 17:08:18

New Release for 11.3

Both the regular amd64 and the the i386 images are uploaded and available Here: https://sourceforge.net/projects/lilidog/
The minimal image is currently uploading, and should be available in a few hours if it doesn't tank.

Here is what is new:

Bullseye Point release 11.3 - Many security fixes and updates.
Added different sound options to Dunst notifications - Enable through toggles.
Added 'Sharpen image with copy' dialog to Thunar right-click actions when right-clicking on an image.
Improved Random Background changer with more options - enable through toggles, and look for the tray icon in the panel.
Changed 'selection' in the Lilidog-Slate Geany theme for better visibility.
Adjusted tint2 tray to 'ascending' from 'descending' icon placement, and adjusted the transparency thereof.

Please let me know if you have any issues.

deleted0 · 2022-03-27 17:40:59

I'm gunna list things as I find them. First up:

While trying to port MX Linux NVIDIA driver installer to LD, discovered there is no lsb-release file in /etc.

Another thing to look into is writing to the UEFI. UEFI/BIOS thinks MX is still installed on the test machine; happens to be the last OS installed before LD. efibootmgr is the tool. Also, add UEFI Firmware Settings option to the boot screen.

Still pounding on LD to see what shakes out.

8bit

edit: add version number to ISO, so I (users) can save new ISOs with out having to change the file name, and help keep things sorted.

Last edited by deleted0 (2022-03-27 17:47:00)

sleekmason · 2022-03-27 17:55:34

^ Excellent! and Yes Please! Good stuff:) I'm already excited about the next release.

Looks like MX also has some good stuff I should be checking out to see what fits. I've heard about a few items recently that caught my attention.

sleekmason · 2022-03-30 21:56:59

A small update and a request to test out an auto login script for lightdm.

Currently pre-release:
The apt xapian index will now update for synaptic after sudo apt update.
Added the shade button to the frame.
Changed the primary monitor settings from fixed to active.

@eight.bit.al - I am uncertain if this is the fix for the monitor settings?, or the dialog directly above it?

Below is the script for the auto login feature of lightdm:) This script uses sed to grab the $USER name and place a separate line for autologin in /ect/lightdm/lightdm.conf. This is not set up for multi users and the like.

You can test by opening /etc/lightdm/lightdm.conf in a text editor and just observing the changes as you select the options. reboot if your comfortable with the changes you see. (hint - click on the text after your choice to see the change).

Be aware, you may have to edit /etc/lightdm/lightdm.conf from the console if problems arise. Or maybe just startx. No, I don't expect any issues. Basically, use common sense and don't try this yet unless you understand the risks and can cope with any problems that may arise.

Also, I would imagine if you have pkexec, this script may work for anybody using lightdm. Please Let me know if this turns out to be the case.

To try it out, copy to a file and name it something like "lightdm-autologin" Place it in ~/bin. Make the file executable and call from a terminal.

Enable, and reboot to see if you are good to go.

#! /bin/bash
# Turn on/off autologin in Lightdm.
# Made by sleekmason 3-30-2022

logi=$(yad --width 300 --borders=10 --entry --title "Auto Login" --center --window-icon=applications-system \
    --image="user-info" \
    --button="gtk-ok:0" --button="gtk-close:1" \
    --text "Auto Login Options" \
    --entry-text \
    "Please Select" "Disable Auto Login" "Enable Auto login")

case $logi in
  Disable*)
   pkexec sed -i '/autologin-user='"$USER"'/d' /etc/lightdm/lightdm.conf 
notify-send 'Auto Login Disabled' ;;
   Enable*)
   if grep -q autologin-user="$USER" "/etc/lightdm/lightdm.conf"; then
   pkexec sh -c 'sed -i '/autologin-user='$USER'/d' /etc/lightdm/lightdm.conf & sed -i '125aautologin-user='$USER'' /etc/lightdm/lightdm.conf' &&
notify-send -t 29000 'Auto Login Re Enabled

Please Look In:
/etc/lightdm/lightdm.conf
If Encountering Problems.'
   else
   pkexec sed -i '125aautologin-user='"$USER"'' /etc/lightdm/lightdm.conf
notify-send 'Auto Login Enabled' 
fi ;;
        *) exit 1 ;;
    esac

deleted0 · 2022-03-30 23:09:49

sleekmason wrote:

A small update and a request to test out an auto login script for lightdm.
Currently pre-release:
The apt xapian index will now update for synaptic after sudo apt update.
Added the shade button to the frame.

Sweet

Changed the primary monitor settings from fixed to active.
@eight.bit.al - I am uncertain if this is the fix for the monitor settings?, or the dialog directly above it?
https://i.postimg.cc/hJQBYZ3H/monitor.png

Placing windows is the answer. That works and I think it's as good as it can be for Openbox. The Primary Monitor setting is for dialogs.

I now think it's mostly my lack of familiarity with OB. With Xfce, the window opens on the last screen it was used on regardless of what's the active/primary monitor.

Below is the script for the auto login feature of lightdm:)

I'll check it out after supper. I've tried everything I could find online with no joy.

deleted0 · 2022-03-31 01:47:40

Nice little script, works a charm.

sleekmason · 2022-03-31 02:22:03

eight.bit.al wrote:

Nice little script, works a charm.

Cool! It will be called from a menu entry in the 'toggles' section. Thank you for testing it for me! I'll study the monitor situation a bit more too. Just working my way down the list;) *Edit - xfce4-screenshooter is awesome!

Last edited by sleekmason (2022-03-31 03:40:02)

sleekmason · 2022-03-31 13:42:36

eight.bit.al wrote:

While trying to port MX Linux NVIDIA driver installer to LD, discovered there is no lsb-release file in /etc.

This is interesting. The /etc/lsb-release file has no real merit as such, and has been replaced by /etc/os-release. In any event, the lsb-release for mx appears to be an added handmade file, that is used by older programs. I will add the file as well to see how that goes. Apparently doesn't affect anything else that doesn't directly look for it:)

So, you can still grab all the info by looking at /etc/os-release, or still by entering 'lsb_release -a' in a terminal. (the program is installed).

The short story is that I'll add the file and see if that is enough to get the nvidia script working, and I'll also see what they are using for that script, and will add it to Lilidog if able. (this also means you can just create the file to see if the nvidia deal will work).

Other things: Finally occurred to me to look and see what BL uses for their monitor settings, and so adjusted likewise, unless there is some know issue with their setup? I'm guessing not:)

The xfce4-screenshooter . . . Jeez I really should have caught all that sooner! lol.
All fixed? now. Have it setup so that just hitting print gives you gui options, whilst shift + a + print, gives a selection dialog for the screen area.

Much more cohesive, and allowed me to do away with both gnome-screenshot and scrot.

Removed fbpanel, and thought about wbar as well, but am leaving it for the moment. Doesn't weigh anything, and does provide icons if wanted. Opinions?

I think I'm going to go with the numbering version ubuntu has. Basically year/month, so Lilidog-22.04-amd64 or some such. Maybe a naming scheme in the future. Also note that the previous two builds (and future) have the build date showing in one of the conkys not connected to the conky chooser yad dialog.

Still looking at Calamares too, but it now has to wait a bit. The season for me is about to take off and I'll have less time to figure these big things out. This shouldn't affect any of the smaller items though.

*EDIT - Here is the lsb_release as basically copied the form from mx. Maybe copy to /etc and give it another go?

PRETTY_NAME="Lilidog"
DISTRIB_ID=Lilidog
DISTRIB_RELEASE=22
DISTRIB_CODENAME="Lilidog"
DISTRIB_DESCRIPTION="Lilidog 22"

I'm guessing that won't work, and they are just checking to see if using mx, but ya never know. Grabbing the three nvidia scripts to take a look now.

*EDIT2 I've grabbed the scripts from mx that I could find, and they look fairly straightforward. There is an nvidia-detect, and nvidia-detect-mx, which look the same minus the labeling, and nvidia-run-mx, which is just a one liner of:

__NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia "$@"

exit 0

Maybe start them in a terminal in mx to see if either of these are the script you are calling? I'm guessing maybe another script that checks these, but don't know.

Without an nvidia card, its hard for me to test, but one thing we can do if necessary, is just add the scripts in anyway, as they don't weigh anything, and see if they will work. Any other ideas, and i'll implement them to see whats up.

Last edited by sleekmason (2022-03-31 14:47:36)

deleted0 · 2022-03-31 17:48:01

^ I'm gunna reinstall LD sometime today, so I have a known entity to work with. I've monkeyed around so much I'd feel safer.

Scrot doesn't weight anything, ~30 KiB, and advanced users like it. I'd leave it in.

Here's an odd observation.

I distro hop on NVME drives, using HP Z TurboDrives. I've added an extension cable to save wear in the mobo slot.

When I swap in the card with LD, the UEFI cannot find it and I run MX Linux boot repair to fix it (just 'cause I'm lazy); which I'm thinking updates the UEFI. I'm gunna check on that.

When I swap in the card with Fedora, for example, the UEFI can handle the change and I get a UEFI screen saying it's updating, then reboots. I think this relates to the earlier mention of LD needs to write to the UEFI.

edit: maybe rbh or unklar who are so much more knowledgeable than I, has something to share on this.

Last edited by deleted0 (2022-03-31 17:58:37)

sleekmason · 2022-03-31 20:05:44

eight.bit.al wrote:

^ I'm gunna reinstall LD sometime today, so I have a known entity to work with. I've monkeyed around so much I'd feel safer.
Scrot doesn't weight anything, ~30 KiB, and advanced users like it. I'd leave it in.
Here's an odd observation.
I distro hop on NVME drives, using HP Z TurboDrives. I've added an extension cable to save wear in the mobo slot.
https://i.ibb.co/KNFDnDj/NVME-Drives.jpg
When I swap in the card with LD, the UEFI cannot find it and I run MX Linux boot repair to fix it (just 'cause I'm lazy); which I'm thinking updates the UEFI. I'm gunna check on that.
When I swap in the card with Fedora, for example, the UEFI can handle the change and I get a UEFI screen saying it's updating, then reboots. I think this relates to the earlier mention of LD needs to write to the UEFI.
https://i.ibb.co/zH8JTYF/me-again2.gif
edit: maybe rbh or unklar who are so much more knowledgeable than I, has something to share on this.

^ He's great:)

I hope they will share!

Because of the way the whole thing is set up, I'm thinking it almost has to be a missing package rather than anything strange with the build setup itself. (I say that now )

Maybe something along the lines of syslinux? Extlinux is installed, but none of the other bootloaders. So something like isolinux maybe? or another package along those lines?

Yeah, these are areas where I don't know much at all right now. I started building on a 12 year old dell, and now on a newer model, but nothing else, so no experimentation with any of it really. Like you said, hopefully they or somebody else will have an answer.

If we can't figure it, I'll build one with recommends and diff the packages to see if anything falls out of the cracks.

rbh · 2022-03-31 20:16:59

If I could lay my hand om the system, I sure could sa something... As of no, I pass.

DeepDayze · 2022-03-31 20:36:32

Nice idea for the PCIe extension cable @8bit.al and I plan to get one as well so that I can swap pcie cards as well without putting too much wear on the slots. Same with SATA cables for swapping ordinary drives to save wear on the fragile mobo SATA connectors as I broke one on another older mobo after so many disk swaps.

Last edited by DeepDayze (2022-03-31 20:37:05)

Bearded_Blunder · 2022-03-31 21:21:55

DeepDayze wrote:

Same with SATA cables for swapping ordinary drives to save wear on the fragile mobo SATA connectors ..

The actual original specification for SATA connectors only envisaged a life of 50 mating & disconnection cycles. Decent quality ones as sold by the likes of RS Components claim 500, with caveats about insertion force, & I expect the testing to make the claim was done with nice new ones rather than old ones where the plastic became brittle.

If you actually swap disks a lot, the thing to use is eSATA which is way more robust as routine plugging & unplugging was envisaged from the outset.

DeepDayze · 2022-03-31 23:40:40

Bearded_Blunder wrote:

DeepDayze wrote:
Same with SATA cables for swapping ordinary drives to save wear on the fragile mobo SATA connectors ..
The actual original specification for SATA connectors only envisaged a life of 50 mating & disconnection cycles. Decent quality ones as sold by the likes of RS Components claim 500, with caveats about insertion force, & I expect the testing to make the claim was done with nice new ones rather than old ones where the plastic became brittle.
If you actually swap disks a lot, the thing to use is eSATA which is way more robust as routine plugging & unplugging was envisaged from the outset.

Esata can work too if you use an enclosure to hold the drive and it's also relatively easy to switch out drives that way rather than mucking around in the case. In addition thought a SATA extender may work and once the extender wore out can easily replace the cable easily. That way less stress on those relatively fragile mobo SATA connectors.

Last edited by DeepDayze (2022-03-31 23:40:53)

unklar · 2022-04-01 12:12:24

eight.bit.al wrote:

edit: maybe rbh or unklar who are so much more knowledgeable than I, has something to share on this.

I don't really understand what you guys are doing here.
My opinion.

autologin
Um, I've never been able to get my head around the 'autologin'

What happens when debian decides to make changes regarding lightdm and its files? Do you then provide support for the users who have locked themselves out of their system and don't know how to get back in?
There should be more than enough of them already.

nvidia
I have the great luck to never have owned nvidia, even if it was a coincidence when I bought my first computer.

In the meantime 'nouveau' is recommended again and again.
If you want to run Linux and choose the non-free nvidia crap, it's your own fault. I mean, if the kernel builder of siduction last year in the forum decides against it, then it needs no more reasoning.

sleekmason · 2022-04-01 14:32:11

unklar wrote:

eight.bit.al wrote:
edit: maybe rbh or unklar who are so much more knowledgeable than I, has something to share on this.
I don't really understand what you guys are doing here.
My opinion.
autologin
Um, I've never been able to get my head around the 'autologin'
What happens when debian decides to make changes regarding lightdm and its files? Do you then provide support for the users who have locked themselves out of their system and don't know how to get back in?
There should be more than enough of them already.
nvidia
I have the great luck to never have owned nvidia, even if it was a coincidence when I bought my first computer.
In the meantime 'nouveau' is recommended again and again.
If you want to run Linux and choose the non-free nvidia crap, it's your own fault. I mean, if the kernel builder of siduction last year in the forum decides against it, then it needs no more reasoning.

I suppose anything is possible. However, The changes debian would need to make to the lightdm setup would be extreme, leading to having to do something different anyway.

The way I wrote the script, the line gets placed specifically in the section needed when enabled, but ANY instances of the same get deleted when disabled, so that even if the line was placed in the wrong section for any reason (or moved), it will still get removed when disabled.

Also, as it is, if the necessary line is placed in the wrong section, nothing happens at all and you just get the login prompt as usual. I reckon it will be okay, and if problems arise, they will be dealt with just like the other 200 we will find between now and then:)

I am going to go ahead and release what I have right now, as it pretty much completes everything to this point.

I don't see any reason why holding it for a month or some such helps anybody. Plus there are a couple of new cool things:) Anyone using Discord?

@eight.bit.al, I didn't see anything else in regards to the system being seen except for python3-distro, and if that's it, then that is a hoot.

This means there may be something more to do with the bootloaders in Live-build that I can adjust, or something else entirely. I think I need to pick up a couple of beater boxes to mess with. If you can figure it, I'll implement it. And I don't have any problem including nvidia if I have the parts. If we can, we'll include it. With the work you have put in, you are part of the Lilidog team as far as I am concerned, and get some decision choices if at all able:)

Okay, here are the changes for this round:

Added switch to use Auto Login. Look in "Toggles" for the menu selection.
Added an installer for the Discord AppImage. (This looks like fun;)
Change Monitor layout for better window settings.
Added shade button to the Openbox window frames.
Added xfce4-screenshooter to replace gnome-screenshot. Scrot still included.
removed the option for FB panel from the menu. Config still available in github.
added xapian index for the Synaptic Package Manager quick search feature. (Only tested in vm)
Changed Lilidog to use a numbering scheme of year/month (Lilidog-22.04-amd64)
Added some necessary and/or recommended packages. (I bare boned the hell out this originally, so some packages continue to trickle in.

Anyhow, amd64 will update tonight, and the other two afterwards. May take up to 48 hours for all three to update.

And then . . Then we can make more changes!

For those that might be new to Linux or the forums, please don't be afraid to speak up. There really are no stupid questions here, and I would love to hear any and all perspectives as what people would like to see or not see as the case may be. This really is a community effort, with a bunch of people here providing insight and help with scripting when needed.

This of course shapes the final result, giving us better product in the end. Knowing the fiddly bits about a missing icon, or misspelled words can make all the difference in the world! So, please share what you find and we'll fix it:)

deleted0 · 2022-04-01 14:41:05

@unklar Thanks for your input

Um, I've never been able to get my head around the 'autologin'
What happens when debian decides to make changes regarding lightdm and its files?

Seeing as autologin is a feature of lightdm, appropriately made changes should prevent issues, no?
From lightdm.conf:

<snip>
#autologin-guest=false
autologin-user=al
autologin-user-timeout=0
#autologin-session=UNIMPLEMENTED
<snip>

If inappropriate changes were made, someone should get Chris Rocked. Ba-dum - tish!
We return you now to the regularly scheduled post.

Yeah NVIDIA sucks. But here we are in the real world. Not NVIDIA for compatibility, NVIDIA for s̶p̶e̶e̶d̶ evil.
@unklar What do you suggest for GPU? TIA

Last edited by deleted0 (2022-04-01 14:47:50)

deleted0 · 2022-04-01 15:11:45

@sleekmason

PM me the info; I'll send ya a Quadro K600

https://c1.neweggimages.com/ProductImag … 482-06.jpg

sleekmason · 2022-04-01 18:23:36

Thank you for your kind offer:) Message sent!

#181 2022-03-26 14:45:26

Re: New ISO build to try.

#182 2022-03-27 17:08:18

Re: New ISO build to try.

#183 2022-03-27 17:40:59

Re: New ISO build to try.

#184 2022-03-27 17:55:34

Re: New ISO build to try.

#185 2022-03-30 21:56:59

Re: New ISO build to try.

#186 2022-03-30 23:09:49

Re: New ISO build to try.

#187 2022-03-31 01:47:40

Re: New ISO build to try.

#188 2022-03-31 02:22:03

Re: New ISO build to try.

#189 2022-03-31 13:42:36

Re: New ISO build to try.

#190 2022-03-31 17:48:01

Re: New ISO build to try.

#191 2022-03-31 20:05:44

Re: New ISO build to try.

#192 2022-03-31 20:16:59

Re: New ISO build to try.

#193 2022-03-31 20:36:32

Re: New ISO build to try.

#194 2022-03-31 21:21:55

Re: New ISO build to try.

#195 2022-03-31 23:40:40

Re: New ISO build to try.

#196 2022-04-01 12:12:24

Re: New ISO build to try.

#197 2022-04-01 14:32:11

Re: New ISO build to try.

#198 2022-04-01 14:41:05

Re: New ISO build to try.

#199 2022-04-01 15:11:45

Re: New ISO build to try.

#200 2022-04-01 18:23:36

Re: New ISO build to try.

Board footer