Porteus Nemesis v3.3 BUG REPORTS

[roadie]

@aus9

I haven't had any problems with arc2xzm....I wonder if you're using it for what it's intended? I used it to extract system files, not from an xz pkg.

arc2xzm colordiff.....if colordiff is installed, arc2xzm will repack it to an xzm

[Ed_P]

New problem, it doesn't wake when opening the netbook's lid. Some kind of a colored circle on a black screen.

That's the screen lock. Just type your password and hit enter.

Actually it's not my password that is required, it is root's. toor.

Newest problem, unable to update the config/network file. It's read only!!

Yes. You are booting from a read only ISO no? In this case please edit the same config files in /etc/porteus.d and then run the boot-network* script in /usr/local/sbin
Unfortunately the easy config files in the root of the drive require a writable media. They are copied to /etc/porteus.d just in case you don't have writable media. The script in /usr/local/sbin (with the boot- prefix) run these config files. You can run them after you boot no problem.

Unfortunately....

Code: Select all

oot ~ # boot-network-setup
------
Line 261:
Fri Nov 27 15:22:12 UTC 2015
------
------
Line 69:
Ignore set to yes in config.
------
root ~ # 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=wireless

### This option is the name of your network device.
### A single ethernet card has the name: eth0
### A single wireless card has the name: wlan0
Interface=wlan0
....

it didn't work. The NetworkManager applet still did not show wireless networks.

I commented out the Ignore=yes option and retried the boot- command but it didn't change the results.

When making the Network changes I had a save.dat file active, via the changes=EXIT cheatcode, but when I rebooted the Network changes were gone.

[Ed_P]

The latest tests.

Changed changes=EXIT/porteus3.x/porteussave.dat to changes=/porteus3.x/porteussave.dat.

Booted to guest.
Checked thee /etc/porteus.d/ folder. My backup network file not there.
Switched logon to root.
Renamed the network file to networkBK.
Copied my copy of the network file, with the wireless/wlan0 changes/ to /etc/porteus.d
In LXTerminal executed boot-network-setup.
No Wireless shown in NetworkManager applet.
Switched logon to guest.
No Wireless shown in NetworkManager applet.
Switched logon to root.
Commented out Ignore=yes option in the /etc/Porteus.d/network file.
In LXterminal executed boot-network-setup
No Wireless shown in NetworkManager applet.
Switched logon to guest.
No Wireless shown in NetworkManager applet.
Rebooted
Loggedon on as guest
No Wireless shown in NetworkManager applet.
Checked the /etc/porteus.d folder. My networkBK file is present. changes= working
Checked the /etc/porteus.d/network file. The wireless/wlan0 changes are not there. changes= not working.

[Ahau]

@brokenman, systemctl commands don't affect my shutdown hangs, I've only experienced them at the very end of shutdown after the handoff back to /mnt/live/shutdown. I re-downloaded the iso and have tried it in vbox as well, with the same result, it still seems related to the halt command not executing properly through busybox.

I'm booting without changes, so that may be why I'm not experiencing the hangs earlier in the shutdown process.

HTH

[beny]

hi Ahau i have run the brokenman script and no hang at shutdown,i have changes active only the errors to umount /mnt/live/modules

[aus9]

possible bug. umounting a mounted USB stick causes PCManFM to close, which is not expected.

I have used no changes= cheatcode to check this.

insert USB stick, media name appears in FM but without configs does not automount....which is not the issue
click the new entry and mounting occurs.....as expected
eject icon also appears

click eject icon and FM exits without warning

[Ahau]

@beny

Open a terminal and type the command 'halt'. Enter your password if you are not already root. The system will go through the entire shutdown process then hang right as it is supposed to turn off. If you use the command "poweroff", "reboot", or if you shutdown through the gui buttons, this hang will not occur.

[beny]

hi right on this, hang on umount everything else, maybe systemd have something to do with that?

[brokenman]

@Ed_P
This is most perplexing. Please give the output of:
nmcli c
nmcli l
nmcli a
nmcli n
nmcli g

click eject icon and FM exits without warning

Does it happen if you change to another directory outside of the place you are removing.

I don't use the 'halt' command. I only use 'poweroff' or 'shutdown' but I still experienced these hangs after doing some complicated mounting such as a chroot somewhere, then activating a few modules.

[beny]

halt -f give the same hang,maybe is a different way of systemd to look at runlevel,i use the menu' to stop system and work ok.

[brokenman]

shutdown and reboot are aliased to = systemctl poweroff
halt is aliased to = systemctl halt

cat /root/.bashrc

[Ed_P]

@Ed_P
This is most perplexing. Please give the output of:
nmcli c
nmcli l
nmcli a
nmcli n
nmcli g

Code: Select all

guest ~ $ nmcli c
NAME                UUID                                  TYPE            DEVICE 
Wired connection 1  dec876de-d07a-4a56-8667-f40bcff31186  802-3-ethernet  --     
guest ~ $ nmcli l
Error: Object 'l' is unknown, try 'nmcli help'.
guest ~ $ nmcli 1
Error: Object '1' is unknown, try 'nmcli help'.
guest ~ $ nmcli a
nmcli successfully registered as a NetworkManager's secret agent.

** (process:1773): WARNING **: Unable to register authentication agent: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: An authentication agent already exists for the given subject
^C
Error: nmcli terminated by signal Interrupt (2)
guest ~ $ nmcli n
enabled
guest ~ $ nmcli g
STATE         CONNECTIVITY  WIFI-HW  WIFI     WWAN-HW  WWAN    
disconnected  none          enabled  enabled  enabled  enabled 
guest ~ $ 
guest ~ $ su
Password: 
Failed to connect to bus: Operation not permitted
root /home/guest # nmcli c
NAME                UUID                                  TYPE            DEVICE 
Wired connection 1  dec876de-d07a-4a56-8667-f40bcff31186  802-3-ethernet  --     
root /home/guest # nmcli l
Error: Object 'l' is unknown, try 'nmcli help'.
root /home/guest # nmcli 1
Error: Object '1' is unknown, try 'nmcli help'.
root /home/guest # nmcli a
nmcli successfully registered as a NetworkManager's secret agent.

** (process:1797): WARNING **: Unable to register authentication agent: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: An authentication agent already exists for the given subject
^C
Error: nmcli terminated by signal Interrupt (2)
root /home/guest # nmcli n
enabled
root /home/guest # nmcli g
STATE         CONNECTIVITY  WIFI-HW  WIFI     WWAN-HW  WWAN    
disconnected  none          enabled  enabled  enabled  enabled 
root /home/guest #

[aus9]

chroot and shutdown problems

I experienced those shutdown problems when I used a changes= cheatcode, just rebooted and without any changes= cheatcode and found a new error

Code: Select all

root /tmp # cd squashfs-root/
root /tmp/squashfs-root # systemd-nspawn
Spawning container squashfs-root on /tmp/squashfs-root.
Press ^] three times within 1s to kill container.
Failed to connect to bus: No such file or directory
root ~ # exit
logout
Container squashfs-root failed with error code 123

I will choose shutdown to see if I get similar shutdown delays

EDIT
No shutdown delays by not using any changes= cheatcode.

I might add, that I think its safer to not use changes= cheatcode to prevent something appearing in changes dir as well if I choose to chroot.
To be more blunt, you can have a script remove certain things from your changes dir without having to address the appearance of the .whitelist entries if you had chosen changes cheatcode

[brokenman]

@Ed_P
From the output it appears that your wifi is enabled.

[Ed_P]

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.

http://forum.porteus.org/viewtopic.php? ... =60#p39381