While the delay during the live session certainly isn't ideal, the installed system doesn't have the delay. I think that those who asked for the builds understand the issue and are okay with it.

Thanks again!

I tried rebuilding the image again and now I can't get rid of the delay at all, $DEITY only knows how I managed it originally but it wasn't because of 0040-sudo.

For the record the rebuild was based on this function:

function mkiso {
 xorriso -as mkisofs \
 -iso-level 3 \
 -full-iso9660-filenames \
 -volid sharpbang_stretch \
 -eltorito-boot isolinux/isolinux.bin \
 -eltorito-catalog isolinux/boot.cat \
 -no-emul-boot -boot-load-size 4 -boot-info-table \
 -isohybrid-mbr isolinux/isohdpfx.bin \
 -eltorito-alt-boot \
 -e boot/grub/efi.img \
 -no-emul-boot -isohybrid-gpt-basdat \
 -output ../"$1" ./
}

But I removed the EFI-related lines and that must be what fixed things but I can't remember exactly what I removed and now I can't recreate it.

Sorry d00d.

Which method are you using to build the images?

I'm sorry, my last response showed up before I saw your last response...if that makes sense.   To answer your question...

1. I start with a netinstall and only install the base system.
2. After installation of the base system, I reboot and install only the packages that I want for the system that I'm creating.
3. After creating the system, I use refractasnapshot to create the .iso.

I'm very thankful for the help, and I hope my kidding around wasn't taken the wrong way.

The "Debian Testing" versions are made by request and aren't part of my normal releases. I only made them to try and help users. While the delay during the boot process isn't ideal, it isn't a deal-breaker on my end. I let that situation be known to those who have requested it. Luckily, the delay isn't a problem after installation.

Thank you HoaS...for trying to help figure this out. I most certainly appreciate your time and knowledge.

I will have a poke around when I've got time and see if I can get to the bottom of this.

Which method are you using to build the images?

Here it is...

miyo@miyolinux:~$ su
Password: 
root@miyolinux:/home/miyo# journalctl -u live-config
-- Logs begin at Sat 2019-04-20 18:53:49 UTC, end at Sat 2019-04-20 19:00:19 UTC. --
Apr 20 18:53:50 miyolinux systemd[1]: Starting live-config contains the components that configure a live system during the boot process (late userspace)....
Apr 20 18:56:53 miyolinux sudo[451]:     root : TTY=unknown ; PWD=/ ; USER=miyo ; COMMAND=/usr/bin/sh -c umask 0077 && mkdir -p /home/miyo/.kde/share/config && cat > /home/miyo/.kde/share/config/kdesurc
Apr 20 18:56:53 miyolinux sudo[451]: pam_unix(sudo:session): session opened for user miyo by (uid=0)
Apr 20 18:56:53 miyolinux sudo[451]: pam_unix(sudo:session): session closed for user miyo
Apr 20 18:56:57 miyolinux live-config[373]: live-config: debconf hostname user-setup sudo locales tzdata
Apr 20 18:56:57 miyolinux live-config[373]: Current default time zone: 'Etc/UTC'
Apr 20 18:56:57 miyolinux live-config[373]: Local time is now:      Sat Apr 20 18:56:57 UTC 2019.
Apr 20 18:56:57 miyolinux live-config[373]: Universal Time is now:  Sat Apr 20 18:56:57 UTC 2019.
Apr 20 18:56:58 miyolinux live-config[373]:  slim keyboard-configuration policykit util-linux login xserver-xorg xfce4-panel.
Apr 20 18:56:58 miyolinux systemd[1]: Started live-config contains the components that configure a live system during the boot process (late userspace)..
root@miyolinux:/home/miyo# 

Can you post it here then?

Ewww...I'll try. Miyo doesn't come with a browser. I'll try copying the output to a text file and transferring that to another partition.

LOLOL!!!

I think...

I did run your listed command in the live session, but nothing stood out to me

Can you post it here then?

I don't have the modified image any more (my storage space is limited) so I'll have to make another one to check at my end.

MiyoLinux wrote:

By commenting out that line, the start job still ran in the live session; however, its time was cut in half...about 2-3 minutes before booting into the desktop...as opposed to 5-7 minutes.

Was the error message the same for both images?

Check the output of my journalctl command for both.

I'm a bit busy at the moment but try a rebuild again later.

Hi HoaS.

Unfortunately, I can't check both. I did run your listed command in the live session, but nothing stood out to me.

I haven't uploaded the 32 bit version yet, so it's not available for observation...it may be a day or two before I upload it.

I don't consider these Debian Testing builds as official MiyoLinux releases...they were built at the request of single users, and in my attempt to help folks, I've ventured beyond my comfort zone.  

It's probably something that I'm doing wrong. LOL!!!

By commenting out that line, the start job still ran in the live session; however, its time was cut in half...about 2-3 minutes before booting into the desktop...as opposed to 5-7 minutes.

Was the error message the same for both images?

Check the output of my journalctl command for both.

I'm a bit busy at the moment but try a rebuild again later.

MiyoLinux wrote:

A start job is running ...blah...blah...blah... no time limit

That appears to be caused by /lib/live/config/0040-sudo, specifically this line:

       sudo -u "${LIVE_USERNAME}" sh -c "echo 'SU_TO_ROOT_SU=sudo' >> /home/${LIVE_USERNAME}/.su-to-rootrc"

I just tried unpacking your ISO, commenting the line then repacking the image and it then boots without error (in QEMU).

No idea why it causes the problem but the systemd journal helped me find it

For the record:

journalctl -u live-config

LOLOLOL!

WHEW! Okay...where to begin?

Since the release of the Miyo-Modern Debian Testing version (which I made for one individual), I was asked to make a 32 bit version of Miyo-Modern Debian Testing. Oy!

Taking HoaS's advice into account, I built the .iso twice...once without commenting out that line, and once with the line commented out.

By commenting out that line, the start job still ran in the live session; however, its time was cut in half...about 2-3 minutes before booting into the desktop...as opposed to 5-7 minutes.

To fsmithred (if this is helpful to you),
In order to get the GUI for the locale, keyboard layout, etc., I also had to add libgtk3-perl...libgtk2-perl wasn't enough for some reason.

I very rarely post anything by accident. Yeah, let me know if it works. I've never tried it.

(I do occasionally leave stuff out.)

LOL!

Hey...it stinkin' worked!   I'm writing this from it now.

Background info...

Host Computer:
2006 Sony Vaio 32 bit

Basic inxi info about the host computer:
CPU~Dual core Intel T2060 (-MCP-)
speed/max~1067/1600 MHz
Mem~995.3MB

The USB used:
8GB Sandisk Cruiser USB-2.0

Installed system:
MiyoLinux (codenamed Addy) i686

Refracta Tools:
refractainstaller-base: 9.4.2
refractainstaller-gui: 9.4.2
refractasnapshot-base: 10.1.1

What I did...

1. Booted from the USB and chose the load to RAM option.
2. Left the USB inserted.
3. When it reached the desktop, I opened gparted and...

a) deleted the .iso from the USB and applied it.
b) created a Partition Table (msdos) on the USB and applied it.
c) created an ext4 file system on the entire USB and applied it.

4. During installation, I allowed the installer to create a swap file.

Worked like a charm! Thanks fsr!

ALL HAIL FSR!!!

(I do occasionally leave stuff out.)