Porteus Nemesis v3.3 BUG REPORTS

Arch based Porteus community project
Locked
User avatar
Ed_P
Contributor
Contributor
Posts: 3069
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 3.2.2 64-bit ISO
Location: Western NY, USA

Re: Porteus Nemesis v3.3 BUG REPORTS

Post#76 by Ed_P » 29 Nov 2015, 19:34

Same machine, Porteus 3.0.1, wi-fi connected.

Code: Select all

guest@porteus:~$ nmcli c
NAME                      UUID                                   TYPE              TIMESTAMP-REAL                    
QuickMoose                e03268da-8b47-46bc-aed2-5d2b151a081f   802-11-wireless   Sun 29 Nov 2015 02:25:19 PM EST   
SouthwestWiFi             6f13492e-4c00-4278-a49e-d9aa9c8d4c3b   802-11-wireless   Wed 04 Mar 2015 03:14:38 PM EST   
Cisco02318-guest          58ab1667-8281-4449-926f-1cb16493c1a3   802-11-wireless   Sun 02 Nov 2014 11:57:41 PM EST   
Wired connection 1        aafa7c18-aa28-40b0-9e9a-6860e0444428   802-3-ethernet    Sun 29 Nov 2015 02:25:09 PM EST   
Frontier3716              a71c6b04-88e8-4418-ac39-fc555834273a   802-11-wireless   Sat 13 Jun 2015 11:09:15 AM EDT   
guest@porteus:~$ nmcli l
Error: Object 'l' is unknown, try 'nmcli help'.
guest@porteus:~$ nmcli a
Error: Object 'a' is unknown, try 'nmcli help'.
guest@porteus:~$ nmcli n
RUNNING         STATE           WIFI-HARDWARE   WIFI       WWAN-HARDWARE   WWAN      
running         connected       enabled         enabled    enabled         disabled  
guest@porteus:~$ nmcli g
Error: Object 'g' is unknown, try 'nmcli help'.
guest@porteus:~$ 
Same machine, Porteus 3.1, wi-fi connected.

Code: Select all

guest@porteus:~$ nmcli c
NAME                      UUID                                   TYPE              TIMESTAMP-REAL                    
Frontier3716              276dab92-69f7-4c08-ab14-bfe26745fd9a   802-11-wireless   Fri 28 Nov 2014 11:53:04 AM EST   
QuickMoose                8f9ed118-7001-4c37-9651-ec16376807a5   802-11-wireless   Sun 29 Nov 2015 02:48:02 PM EST   
Cisco02318-guest          17cbd70f-48f4-4bd6-bb07-dd5b5ac6bf1b   802-11-wireless   Fri 28 Nov 2014 01:20:21 PM EST   
Wired connection 1        b11fa235-e5dd-4610-9d05-8dc534b32447   802-3-ethernet    Sun 29 Nov 2015 02:47:50 PM EST   
guest@porteus:~$ nmcli l
Error: Object 'l' is unknown, try 'nmcli help'.
guest@porteus:~$ nmcli a
Error: Object 'a' is unknown, try 'nmcli help'.
guest@porteus:~$ nmcli n
RUNNING         STATE           WIFI-HARDWARE   WIFI       WWAN-HARDWARE   WWAN      
running         connected       enabled         enabled    enabled         disabled  
guest@porteus:~$ nmcli g
Error: Object 'g' is unknown, try 'nmcli help'.
guest@porteus:~$ 
Same machine with Porteus 3.3, no connection.

viewtopic.php?f=137&t=5242&start=60#p39381
Last edited by Ed_P on 29 Nov 2015, 22:51, edited 1 time in total.
Ed

User avatar
brokenman
Site Admin
Site Admin
Posts: 5439
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v3.2rcX all desktops
Location: Brazil
Contact:

Re: Porteus Nemesis v3.3 BUG REPORTS

Post#77 by brokenman » 29 Nov 2015, 22:50

Roadie bought to my attention a problem he was having with wpa_supplicant. Please open a root console with the non-working wifi and issue the following:

Code: Select all

systemctl restart wpa_supplicant
Then try to connect again.
How do i become super user?
Wear your underpants on the outside and put on a cape.

User avatar
Ed_P
Contributor
Contributor
Posts: 3069
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 3.2.2 64-bit ISO
Location: Western NY, USA

Re: Porteus Nemesis v3.3 BUG REPORTS

Post#78 by Ed_P » 29 Nov 2015, 23:02

brokenman wrote:Please open a root console with the non-working wifi and issue the following:

Code: Select all

systemctl restart wpa_supplicant
Then try to connect again.
Do I do this after executing the previous nmctl commands?

-update-

Code: Select all

guest ~ $ nmcli c
NAME                UUID                                  TYPE            DEVICE 
Wired connection 1  6b78674f-9295-4b4a-be55-6b7ce19633f9  802-3-ethernet  --   
  
guest ~ $ systemctl restart wpa-supplicant
Failed to open /run/systemd/ask-password-block/136:0: No such file or directory
Failed to restart wpa-supplicant.service: Unit wpa-supplicant.service failed to load: No such file or directory.

guest ~ $ sudo systemctl restart wpa-supplicant

We trust you have received the usual lecture from the local System
Administrator. It usually boils down to these three things:

    #1) Respect the privacy of others.
    #2) Think before you type.
    #3) With great power comes great responsibility.

[sudo] password for guest:        <<<<< Wrong user name specified 

Failed to restart wpa-supplicant.service: Unit wpa-supplicant.service failed to load: No such file or directory.

guest ~ $ su
Password: 
Failed to connect to bus: Operation not permitted

root /home/guest # systemctl restart wpa-supplicant
Failed to restart wpa-supplicant.service: Unit wpa-supplicant.service failed to load: No such file or directory.
root /home/guest # 
Ed

User avatar
brokenman
Site Admin
Site Admin
Posts: 5439
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v3.2rcX all desktops
Location: Brazil
Contact:

Re: Porteus Nemesis v3.3 BUG REPORTS

Post#79 by brokenman » 30 Nov 2015, 02:04

wpa_supplicant <-- please note the underscore

No need to run the nmcli commands anymore. Just:

Code: Select all

systemctl restart wpa_supplicant
systemctl status wpa_supplicant
How do i become super user?
Wear your underpants on the outside and put on a cape.

User avatar
Ed_P
Contributor
Contributor
Posts: 3069
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 3.2.2 64-bit ISO
Location: Western NY, USA

Re: Porteus Nemesis v3.3 BUG REPORTS

Post#80 by Ed_P » 30 Nov 2015, 04:26

brokenman wrote:wpa_supplicant <-- please note the underscore
:oops: Good grief. :fool: :(
No need to run the nmcli commands anymore. Just:

Code: Select all

systemctl restart wpa_supplicant
systemctl status wpa_supplicant

Code: Select all

guest ~ $ su
Password: 
Failed to connect to bus: Operation not permitted
root /home/guest # systemctl restart wpa_supplicant
root /home/guest # systemctl status wpa_supplicant
● wpa_supplicant.service - WPA supplicant
   Loaded: loaded (/usr/lib/systemd/system/wpa_supplicant.service; disabled; vendor preset: disabled)
   Active: active (running) since Sun 2015-11-29 23:10:27 UTC; 15s ago
 Main PID: 1780 (wpa_supplicant)
   CGroup: /system.slice/wpa_supplicant.service
           └─1780 /usr/bin/wpa_supplicant -u

Nov 29 23:10:27 porteus systemd[1]: Starting WPA supplicant...
Nov 29 23:10:27 porteus systemd[1]: Started WPA supplicant.

root /home/guest # nmcli c
NAME                UUID                                  TYPE            DEVICE 
Wired connection 1  6e181c70-d7eb-474f-bf13-50903116cf5c  802-3-ethernet  --     
 
root /home/guest # nmcli g
STATE         CONNECTIVITY  WIFI-HW  WIFI     WWAN-HW  WWAN    
disconnected  none          enabled  enabled  enabled  enabled 
root /home/guest # 
Ed

User avatar
brokenman
Site Admin
Site Admin
Posts: 5439
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v3.2rcX all desktops
Location: Brazil
Contact:

Re: Porteus Nemesis v3.3 BUG REPORTS

Post#81 by brokenman » 30 Nov 2015, 22:01

Hmmmm. Output of the following please (cut and paste it)

cat /var/log/porteus-livedbg
ps aux|grep NetworkManager
ls /sys/class/net
netctl list
How do i become super user?
Wear your underpants on the outside and put on a cape.

User avatar
Ed_P
Contributor
Contributor
Posts: 3069
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 3.2.2 64-bit ISO
Location: Western NY, USA

Re: Porteus Nemesis v3.3 BUG REPORTS

Post#82 by Ed_P » 30 Nov 2015, 23:58

brokenman wrote:Hmmmm. Output of the following please (cut and paste it)

cat /var/log/porteus-livedbg
ps aux|grep NetworkManager
ls /sys/class/net
netctl list

Code: Select all

guest ~ $ cat /var/log/porteus-livedbg
# Recognized devices:
/dev/sda1: LABEL="PQSERVICE" UUID="9894832D94830CC6" TYPE="ntfs" 
/dev/sda2: LABEL="SYSTEM RESERVED" UUID="ECF483DEF483AA02" TYPE="ntfs" 
/dev/sda3: LABEL="Acer" UUID="48168114168103E2" TYPE="ntfs" 
/dev/sda5: LABEL="Data" UUID="01CD20066B8BF780" TYPE="ntfs" 
/dev/sda6: LABEL="BKUPS" UUID="1ECAD5A8CAD57C89" TYPE="ntfs" 

# Booting device:
/mnt/sda5

# Porteus data found in:
/mnt/isoloop/porteus

# Changes are stored in:
/porteus3.x/porteussave.dat

# Non standard /rootcopy dir:
none

# Modules activated during boot time:
/mnt/isoloop/porteus/base/000-kernel.xzm
/mnt/isoloop/porteus/base/001-core.xzm
/mnt/isoloop/porteus/base/002-xorg.xzm
/mnt/isoloop/porteus/base/003-lxde.xzm
guest ~ $ ps aux|grep NetworkManager
root       650  0.4  0.9 357512 16308 ?        Ssl  18:27   0:02 /usr/bin/NetworkManager --no-daemon
guest     1851  0.0  0.1  10728  2280 pts/0    S+   18:37   0:00 grep --color=auto NetworkManager
guest ~ $ ls /sys/class/net
eth0  lo
guest ~ $ netctl list 
guest ~ $ 

guest ~ $ /mnt/sda5/porteus3.0/Guest/bootdev.sh
Boot device:   /mnt/sda5
Boot device format: "ntfs" 
Boot folder:   /porteus3.x/
Boot mode:     ISO /ISOs/porteus-nemesis-v3.3-x86_64.iso
OS:      Porteus-v3.3
ARCH:    x86_64
Kernel:  Linux porteus 4.3.0-porteus #2
Cmdline: quiet from=/ISOs/porteus-nemesis-v3.3-x86_64.iso changes=/porteus3.x/porteussave.dat volume=40 ramsize=80%  
guest ~ $ 
Ed

User avatar
brokenman
Site Admin
Site Admin
Posts: 5439
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v3.2rcX all desktops
Location: Brazil
Contact:

Re: Porteus Nemesis v3.3 BUG REPORTS

Post#83 by brokenman » 01 Dec 2015, 03:12

Have to admit I can't think of what could be wrong. Everything seems in order. You have ...

1) Network card drivers loaded and working
2) NetworkManager service running
3) wpa_supplicant service running

Do you have some type of wifi network toggle kill switch on this machine?
When you click on the nm-applet icon what do you see?
How do i become super user?
Wear your underpants on the outside and put on a cape.

User avatar
Ed_P
Contributor
Contributor
Posts: 3069
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 3.2.2 64-bit ISO
Location: Western NY, USA

Re: Porteus Nemesis v3.3 BUG REPORTS

Post#84 by Ed_P » 01 Dec 2015, 04:30

brokenman wrote:Do you have some type of wifi network toggle kill switch on this machine?
No. Windows 7, 10, Porteus 2.1, 3.0, 3.0.1, 3.1 don't have a problem with the network.
When you click on the nm-applet icon what do you see?
Image
Image
Image
Image
Ed

aus9

Re: Porteus Nemesis v3.3 BUG REPORTS

Post#85 by aus9 » 01 Dec 2015, 09:06

sorry to intrude again

if wireless drivers are loaded, maybe Ed_P can post the output to this command please? guest or root doesn't matter

Code: Select all

ifconfig
Leaping ahead I see local (lo) and wired (eth0) while I would expect Ed to see lo and maybe wlan0

User avatar
brokenman
Site Admin
Site Admin
Posts: 5439
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v3.2rcX all desktops
Location: Brazil
Contact:

Re: Porteus Nemesis v3.3 BUG REPORTS

Post#86 by brokenman » 01 Dec 2015, 09:14

Leaping ahead I see local (lo) and wired (eth0)
Oh man. I asked for the output to check if wifi was loaded. Clearly too many late nights for me, I somehow saw a wireless device there. Therein lies the problem.

Please post the model of wireless card you have, perhaps from Porteus-v3.1. Strange since Nemesis has a complete firmware set compared to v3.1
Thanks aus9.
How do i become super user?
Wear your underpants on the outside and put on a cape.

aus9

Re: Porteus Nemesis v3.3 BUG REPORTS

Post#87 by aus9 » 01 Dec 2015, 09:50

I am not the original poster to wifi problem again sorry if I intruded

User avatar
Ed_P
Contributor
Contributor
Posts: 3069
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 3.2.2 64-bit ISO
Location: Western NY, USA

Re: Porteus Nemesis v3.3 BUG REPORTS

Post#88 by Ed_P » 01 Dec 2015, 14:14

Thanks guys. :friends:

This is ifconfig from my normal system (3.0.1)

Code: Select all

guest@porteus:~$ ifconfig
eth0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether b8:70:f4:ef:57:5d  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

eth1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.200.212  netmask 255.255.255.0  broadcast 192.168.200.255
        inet6 2604:6000:1010:406b:62d8:19ff:fe1a:a1fc  prefixlen 64  scopeid 0x0<global>
        inet6 fe80::62d8:19ff:fe1a:a1fc  prefixlen 64  scopeid 0x20<link>
        ether 60:d8:19:1a:a1:fc  txqueuelen 1000  (Ethernet)
        RX packets 45  bytes 3481 (3.3 KiB)
        RX errors 0  dropped 0  overruns 0  frame 328
        TX packets 40  bytes 6516 (6.3 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 19  

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 0  (Local Loopback)
        RX packets 2  bytes 100 (100.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 2  bytes 100 (100.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

guest@porteus:~$ 
This is ifconfig from 3.3.

Code: Select all

guest ~ $ ifconfig
eth0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether b8:70:f4:ef:57:5d  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 0  (Local Loopback)
        RX packets 100  bytes 6000 (5.8 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 100  bytes 6000 (5.8 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

guest ~ $ cat /etc/porteus.d/network
### Network config file.
### Options listed here will be parsed at boot.
### Options must be listed one per line without space before them.

## IMPORTANT - If you use a graphical network manager then set Ignore=yes in this file

### This option means the file will be ignored at boot.
### Uncomment this if you will manually setup your network or
### another application handles the setup.
Ignore=yes

### Give this configuration profile a name. This can be used from
### inside netctl to switch between profiles after boot. If this
### profile already exists as a nemesis module it will be skipped.
### Please use a human friendly name without special characters.
### This option is obligatory.
Profile=wired

################################################
### Standard settings (most common)
################################################

### This option sets an ethernet (wired) or wireless network card.
### This option allows: ethernet or wireless
Connection=ethernet
And included is the top portion of the network file. Note that the Connection parm is back to ethernet. I change the parms to wireless and wlan0, I reboot and they get changed back. And I am using a save.dat file.

Code: Select all

Cmdline: quiet from=/ISOs/porteus-nemesis-v3.3-x86_64.iso changes=/porteus3.x/porteussave.dat volume=40 
brokenman wrote:Please post the model of wireless card you have, perhaps from Porteus-v3.1.
Any particular command(s) you want to see?

- update -

This is ifconfig from Porteus 3.1.

Code: Select all

guest@porteus:~$ ifconfig
bash: ifconfig: command not found
guest@porteus:~$ su
Password: 
root@porteus:/home/guest# ifconfig
eth0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether b8:70:f4:ef:57:5d  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

eth1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.200.213  netmask 255.255.255.0  broadcast 192.168.200.255
        inet6 2604:6000:1010:406b:62d8:19ff:fe1a:a1fc  prefixlen 64  scopeid 0x0<global>
        inet6 fe80::62d8:19ff:fe1a:a1fc  prefixlen 64  scopeid 0x20<link>
        ether 60:d8:19:1a:a1:fc  txqueuelen 1000  (Ethernet)
        RX packets 1274  bytes 688247 (672.1 KiB)
        RX errors 0  dropped 0  overruns 0  frame 8603
        TX packets 718  bytes 151483 (147.9 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 19  

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 0  (Local Loopback)
        RX packets 122  bytes 6100 (5.9 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 122  bytes 6100 (5.9 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

root@porteus:/home/guest# 
Plus

Code: Select all

guest@porteus:~$ cat /var/log/porteus-livedbg
# Recognized devices:
/dev/sda1: LABEL="PQSERVICE" UUID="9894832D94830CC6" TYPE="ntfs" 
/dev/sda2: LABEL="SYSTEM RESERVED" UUID="ECF483DEF483AA02" TYPE="ntfs" 
/dev/sda3: LABEL="Acer" UUID="48168114168103E2" TYPE="ntfs" 
/dev/sda5: LABEL="Data" UUID="01CD20066B8BF780" TYPE="ntfs" 
/dev/sda6: LABEL="BKUPS" UUID="1ECAD5A8CAD57C89" TYPE="ntfs" 
/mnt/sda5//porteus3.1/changes/porteussave.dat: UUID="e95e03b4-b1e3-4362-a61c-7744ddda7312" TYPE="xfs" 

# Booting device:
/mnt/sda5

# Porteus data found in:
/mnt/isoloop/porteus

# Changes are stored in:
memory

# Non standard /rootcopy dir:
none

# Modules activated during boot time:
/mnt/isoloop/porteus/base/000-kernel.xzm
/mnt/isoloop/porteus/base/001-core.xzm
/mnt/isoloop/porteus/base/002-xorg.xzm
/mnt/isoloop/porteus/base/003-lxqt.xzm
/mnt/isoloop/porteus/base/04-firefox.xzm
/mnt/sda5//porteus3.1/Modules/001-core_alldesktops-150124.xzm
/mnt/sda5//porteus3.1/Modules/002-xorg_alldesktops-150126.xzm
/mnt/sda5//porteus3.1/Modules/004-lxqt_fixes-150120.xzm
/mnt/sda5//porteus3.1/Modules/07-printing.xzm
/mnt/sda5//porteus3.1/Modules/MyWines.xzm
/mnt/sda5//porteus3.1/Modules/Wine-1.7.26-x64-GeckoMono-1.xzm
/mnt/sda5//porteus3.1/Modules/flashplayer-plugin-11.2.202.548-x86_64-1alien.xzm
/mnt/sda5//porteus3.1/Modules/java-builder-1.1_noarch.xzm
/mnt/sda5//porteus3.1/Modules/jre-8u66-x86_64-1.xzm
/mnt/sda5//porteus3.1/Modules/kpat/kpat-4.10.5-x86_64-1.xzm
/mnt/sda5//porteus3.1/Modules/kpat/kpat-4.10.5-x86_64-bundle.xzm
/mnt/sda5//porteus3.1/Modules/kpat/libdbusmenu-qt-0.9.2-x86_64-2.xzm
/mnt/sda5//porteus3.1/Modules/upkernel-3.18.18-noarch-1.xzm
/mnt/sda5//porteus3.1/Modules/xgames-0.3-x86_64-4.xzm
/mnt/sda5//porteus3.1/Modules/xscreensaver-5.29-x86_64-1_slack14.1.xzm
/mnt/sda5//porteus3.1/changes/porteussave.dat/changes
guest@porteus:~$ 
guest@porteus:~$ ps aux|grep NetworkManager
root      3947  0.1  0.3 318796  6080 ?        Ssl  09:22   0:00 /usr/sbin/NetworkManager
guest     4378  0.0  0.0   5092  1040 pts/0    R+   09:31   0:00 grep NetworkManager
guest@porteus:~$ 
guest@porteus:~$ ls /sys/class/net
eth0@  eth1@  lo@
guest@porteus:~$ 
guest@porteus:~$ netctl list
bash: netctl: command not found
guest@porteus:~$ 
Ed

User avatar
brokenman
Site Admin
Site Admin
Posts: 5439
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v3.2rcX all desktops
Location: Brazil
Contact:

Re: Porteus Nemesis v3.3 BUG REPORTS

Post#89 by brokenman » 01 Dec 2015, 15:57

Please post the model of wireless card you have
You can get this from porteus-settings-centre or from: lspci
How do i become super user?
Wear your underpants on the outside and put on a cape.

User avatar
Ahau
King of Docs
King of Docs
Posts: 1331
Joined: 28 Dec 2010, 15:18
Distribution: LXDE & Xfce 32/64-bit
Location: USA

Re: Porteus Nemesis v3.3 BUG REPORTS

Post#90 by Ahau » 01 Dec 2015, 16:38

@brokenman, I still haven't delved into how to get cliexec commands to have visible output on the screen while systemd is running the show, maybe I'll tackle that next.

to get guiexec working, all you need to do is copy /opt/porteus-scripts/xorg/gui-autostart into your tree from standard Porteus (I think it's in 002-xorg.xzm). You already have /etc/xdg/autostart/gui-autostart.desktop in your tree, which is what calls /opt/porteus-scripts/xorg/gui-autostart upon logging in to any xdg compliang desktop.

This will also get the "volume=" cheatcode working (tested) and I believe it will get "kmap=" working as well (did not test since I use the default kmap and ran out of time).

I'd also suggest copying 002-xorg.xzm/etc/X11/xinit/.Xresources from the standard Porteus into your tree to make xterm a little prettier. gui-autostart applies those settings (but I didn't think to check whether systemd handles this without the need for it to be in gui-autostart...).

In researching the 'su' bug (which also applies to 'sudo -i', btw) I found that systemd has implemented its own function for logging in as another user, see here:

https://www.phoronix.com/scan.php?page= ... su-Command

so you can type "machinectl shell" to login as root without any error messages (but you do get a gui popup for your password, which is nearly as annoying to me as the error message, plus the fact that I have 14 additional key strokes). Part of me wonders if the errors we are getting from 'su' are a subtle (or overt) hint from the systemd developers that we shouldn't be using 'su' and we should be using their "better" command instead, but it could still be something else that needs a fix. Does anyone have a current (i.e. same version of systemd as Nemesis) install of Arch to check if su works there without spitting errors?
Please take a look at our online documentation, here. Suggestions are welcome!

Locked