Feedback and Bug Reports for Porteus v2.1 RC2

New features which should be implemented in Porteus; suggestions are welcome. All questions or problems with testing releases (alpha, beta, or rc) should go in their relevant thread here, rather than the Bug Reports section.
donald
Full of knowledge
Full of knowledge
Posts: 1215
Joined: 17 Jun 2013, 13:17
Distribution: Porteus 3.2.2 XFCE 32bit
Location: Germany

Re: Feedback and Bug Reports for Porteus v2.1 RC2

Post#31 by donald » 11 Jul 2013, 04:07

@brokenman

"Putting a root password on it means that whenever the user starts it, they will not be changing the users config, but root's config."

That is the point I have not considered
Thanks for the explanation.

User avatar
Rava
Contributor
Contributor
Posts: 1319
Joined: 11 Jan 2011, 02:46
Distribution: Porteus 3.1.0 x86-64 XFCe
Location: Germany

Re: Feedback and Bug Reports for Porteus v2.1 RC2

Post#32 by Rava » 11 Jul 2013, 05:35

For some reason, /etc/rc.d/rc.FireWall is not started at bootup. I have to start it manually via "/etc/rc.d/rc.FireWall start"

And it gives an error:

Code: Select all

root@porteus:/mnt/live/memory/images# /etc/rc.d/rc.FireWall start
WARNING: The state match is obsolete. Use conntrack instead.
Could it be that rc.FireWall needs an update due to the recent version of iptables?


Me thinks the line it complains about is thie one:

Code: Select all

   # Allow previously established connections
   $IPTABLES -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT
Sadly, "conntrack" is not mentioned in either "man iptables" nor in "iptables -h" :(

Iptables in 2.1 rc2 x86-64 is: v1.4.17

But since it was written by Tomas M. ... maybe he has a never one, created / edited for Slax7?
_________________________________

And one man page is gzipped, instead of being plain:

Code: Select all

root@porteus:/usr/man$ ls -l /usr/man/man1/mpg321.1.gz
lrwxrwxrwx 1 root root 11 Jul  8 08:54 /usr/man/man1/mpg321.1.gz -> mpg123.1.gz
Cheers!
Yours Rava

User avatar
Rava
Contributor
Contributor
Posts: 1319
Joined: 11 Jan 2011, 02:46
Distribution: Porteus 3.1.0 x86-64 XFCe
Location: Germany

Re: Feedback and Bug Reports for Porteus v2.1 RC2

Post#33 by Rava » 11 Jul 2013, 06:27

My system: XFCe version, x65-64 with these modules loaded:

Code: Select all

000-kernel.xzm
001-core.xzm
002-xorg.xzm
003-xfce.xzm
010-nVidia-304.88-porteus-v2.1-rc2-x86_64-1ftm.xzm
04-firefox.xzm
050-viewnior-1.3-x86_64_stripped-locales.xzm
051-ncdu-1.9-x86_64-1cf.xzm
052-btar-1.1.1-1.20.x86_64.xzm
06-abiword.xzm
After suspend eth0 network is not automatically re-connected:

Code: Select all

root@porteus:/mnt/live/memory/images# ifconfig 
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet6 fe80::21a:92ff:fe31:9208  prefixlen 64  scopeid 0x20<link>
        ether 00:1a:92:31:92:08  txqueuelen 1000  (Ethernet)
        RX packets 10668  bytes 12397997 (11.8 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 7791  bytes 847018 (827.1 KiB)
        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 24  bytes 1928 (1.8 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 24  bytes 1928 (1.8 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

root@porteus:/mnt/live/memory/images# dhcpcd eth0
dhcpcd[4617]: sending commands to master dhcpcd process
root@porteus:/mnt/live/memory/images# ifconfig 
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.7.94  netmask 255.255.255.0  broadcast 192.168.7.255
        inet6 fe80::21a:92ff:fe31:9208  prefixlen 64  scopeid 0x20<link>
        ether 00:1a:92:31:92:08  txqueuelen 1000  (Ethernet)
        RX packets 10668  bytes 12397997 (11.8 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 7791  bytes 847018 (827.1 KiB)
        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 24  bytes 1928 (1.8 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 24  bytes 1928 (1.8 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
It works like a charm, but having to root@dhcpcd eth0 manually each and every resume is annoying.

The popup also tells me, after some time with no traffic (while copy'n'pasta the above info and typing this very post) "network disconnected", I ran a bash script checking for connectivity (by pining google), and that gave me the result that network is online.
After I ran my script, the popup told me "eth0 connected" ???


But all this can also be due to a slightly buggy switch, that I only use when having more than one PC online in a certain room, cause I only have one network cable into that room...
I try out all the above without that very script and give you the heads up, but Port 2.0 x86-64 did not have any of the above issues with the very same switch in between...

Here is the psinfo:

Code: Select all

----------------------
Output from psinfo
----------------------
script by jayflood
.

====== USER INFO =====
User is: root
.
===== MACHINE INFO =====
Platform: x86_64
Kernel: 3.9.4-porteus
Processor: Intel(R) Pentium(R) D  CPU 2.66GHz
Base Board Information
	Manufacturer: ASUSTeK Computer INC.
	Product Name: P5PL2-E
MemTotal:        3475484 kB
MemFree:         1620992 kB
Bootparam: quiet initrd=initrd.xz zram=20% fsck timezone=Europe/Berlin kmap=de BOOT_IMAGE=vmlinuz 
.
===== LIVE DEBUG INFO =====
# Recognized devices:
/dev/sda1: SEC_TYPE="msdos" LABEL="EXTUSB01" UUID="8C1F-A0EB" TYPE="vfat" 

# Booting device:
/mnt/sda1

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

# Changes are stored in:
memory

# Non standard /rootcopy dir:
none

# Modules activated during boot time:
/mnt/sda1/porteus/base/000-kernel.xzm
/mnt/sda1/porteus/base/001-core.xzm
/mnt/sda1/porteus/base/002-xorg.xzm
/mnt/sda1/porteus/base/003-xfce.xzm
/mnt/sda1/porteus/base/010-nVidia-304.88-porteus-v2.1-rc2-x86_64-1ftm.xzm
/mnt/sda1/porteus/base/04-firefox.xzm
/mnt/sda1/porteus/base/050-viewnior-1.3-x86_64_stripped-locales.xzm
/mnt/sda1/porteus/base/051-ncdu-1.9-x86_64-1cf.xzm
/mnt/sda1/porteus/base/052-btar-1.1.1-1.20.x86_64.xzm
/mnt/sda1/porteus/base/06-abiword.xzm

.
===== SOUND INFO =====
Sound card:  0 [Intel          ]: HDA-Intel - HDA Intel
                      HDA Intel at 0xdddf8000 irq 44
Sound driver: Advanced Linux Sound Architecture Driver Version k3.9.4-porteus.
.
===== PARTITION INFO =====
Mounted: 
devtmpfs       devtmpfs  1.7G  4.0K  1.7G   1% /dev
/dev/sda1      vfat      984M  858M  126M  88% /mnt/sda1
.
===== OPTICAl DRIVE =====
sr1
.
===== USB INFO =====
Removables: USB
Removable status: sd4:0:0:0:[sda]Protect
sd5:0:0:0:[sdb]Protect
sd6:0:0:0:[sdb]Protect
sd7:0:0:0:[sdc]Protect
sd8:0:0:0:[sdc]Protect
.
lsusb: Bus 001 Device 002: ID 0457:0151 Silicon Integrated Systems Corp. Super Flash 1GB / GXT  64MB Flash Drive
Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
Bus 002 Device 002: ID 046d:c03e Logitech, Inc. Premium Optical Wheel Mouse (M-BT58)
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
.
===== SCREEN INFO =====
Screen 0: minimum 8 x 8, current 2880 x 900, maximum 4096 x 4096
.
===== ACTIVATED MODULES =====
000-kernel.xzm
001-core.xzm
002-xorg.xzm
003-xfce.xzm
010-nVidia-304.88-porteus-v2.1-rc2-x86_64-1ftm.xzm
04-firefox.xzm
050-viewnior-1.3-x86_64_stripped-locales.xzm
051-ncdu-1.9-x86_64-1cf.xzm
052-btar-1.1.1-1.20.x86_64.xzm
06-abiword.xzm
.
===== NETWORK INFO =====
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet6 fe80::21a:92ff:fe31:9208  prefixlen 64  scopeid 0x20<link>
        ether 00:1a:92:31:92:08  txqueuelen 1000  (Ethernet)
        RX packets 52224  bytes 62243966 (59.3 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 37077  bytes 3922628 (3.7 MiB)
        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 24  bytes 1928 (1.8 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 24  bytes 1928 (1.8 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
.
# Generated by dhcpcd from eth0
nameserver 194.25.2.129
nameserver 194.25.0.68
domain ravadomain
nameserver 192.168.7.1
# /etc/resolv.conf.tail can replace this line
.
===== PCI INFO =====
lspci: 00:00.0 Host bridge [0600]: Intel Corporation 82945G/GZ/P/PL Memory Controller Hub [8086:2770] (rev 02)
	Subsystem: ASUSTeK Computer Inc. Device [1043:8178]
00:01.0 PCI bridge [0604]: Intel Corporation 82945G/GZ/P/PL PCI Express Root Port [8086:2771] (rev 02)
	Kernel driver in use: pcieport
00:1b.0 Audio device [0403]: Intel Corporation N10/ICH 7 Family High Definition Audio Controller [8086:27d8] (rev 01)
	Subsystem: ASUSTeK Computer Inc. P5LD2-VM Mainboard (Realtek ALC 882 codec) [1043:817f]
	Kernel driver in use: snd_hda_intel
00:1c.0 PCI bridge [0604]: Intel Corporation N10/ICH 7 Family PCI Express Port 1 [8086:27d0] (rev 01)
	Kernel driver in use: pcieport
00:1c.3 PCI bridge [0604]: Intel Corporation N10/ICH 7 Family PCI Express Port 4 [8086:27d6] (rev 01)
	Kernel driver in use: pcieport
00:1d.0 USB controller [0c03]: Intel Corporation N10/ICH 7 Family USB UHCI Controller #1 [8086:27c8] (rev 01)
	Subsystem: ASUSTeK Computer Inc. P5KPL-VM,P5LD2-VM Mainboard [1043:8179]
	Kernel driver in use: uhci_hcd
00:1d.1 USB controller [0c03]: Intel Corporation N10/ICH 7 Family USB UHCI Controller #2 [8086:27c9] (rev 01)
	Subsystem: ASUSTeK Computer Inc. P5KPL-VM,P5LD2-VM Mainboard [1043:8179]
	Kernel driver in use: uhci_hcd
00:1d.2 USB controller [0c03]: Intel Corporation N10/ICH 7 Family USB UHCI Controller #3 [8086:27ca] (rev 01)
	Subsystem: ASUSTeK Computer Inc. P5KPL-VM,P5LD2-VM Mainboard [1043:8179]
	Kernel driver in use: uhci_hcd
00:1d.3 USB controller [0c03]: Intel Corporation N10/ICH 7 Family USB UHCI Controller #4 [8086:27cb] (rev 01)
	Subsystem: ASUSTeK Computer Inc. P5KPL-VM,P5LD2-VM Mainboard [1043:8179]
	Kernel driver in use: uhci_hcd
00:1d.7 USB controller [0c03]: Intel Corporation N10/ICH 7 Family USB2 EHCI Controller [8086:27cc] (rev 01)
	Subsystem: ASUSTeK Computer Inc. P5KPL-VM,P5LD2-VM Mainboard [1043:8179]
	Kernel driver in use: ehci-pci
00:1e.0 PCI bridge [0604]: Intel Corporation 82801 PCI Bridge [8086:244e] (rev e1)
00:1f.0 ISA bridge [0601]: Intel Corporation 82801GB/GR (ICH7 Family) LPC Interface Bridge [8086:27b8] (rev 01)
	Subsystem: ASUSTeK Computer Inc. P5KPL-VM Motherboard [1043:8179]
00:1f.1 IDE interface [0101]: Intel Corporation 82801G (ICH7 Family) IDE Controller [8086:27df] (rev 01)
	Subsystem: ASUSTeK Computer Inc. P5KPL-VM Motherboard [1043:8179]
	Kernel driver in use: ata_piix
00:1f.2 IDE interface [0101]: Intel Corporation N10/ICH7 Family SATA Controller [IDE mode] [8086:27c0] (rev 01)
	Subsystem: ASUSTeK Computer Inc. Device [1043:2601]
	Kernel driver in use: ata_piix
00:1f.3 SMBus [0c05]: Intel Corporation N10/ICH 7 Family SMBus Controller [8086:27da] (rev 01)
	Subsystem: ASUSTeK Computer Inc. P5KPL-VM Motherboard [1043:8179]
02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller [10ec:8168] (rev 01)
	Subsystem: ASUSTeK Computer Inc. P5B [1043:81aa]
	Kernel driver in use: r8169
04:00.0 VGA compatible controller [0300]: nVidia Corporation NV44 [GeForce 6200 LE] [10de:0163] (rev a1)
	Subsystem: ASUSTeK Computer Inc. Device [1043:820b]
	Kernel driver in use: nvidia
.
.
===== LOGS INFO =====
dmesg | tail 
.
[11628.704147] PM: resume of devices complete after 3887.752 msecs
[11628.715196] Restarting tasks ... done.
[11630.331637] r8169 0000:02:00.0 eth0: rtl_phyar_cond == 1 (loop: 20, delay: 25).
[11630.332556] r8169 0000:02:00.0 eth0: rtl_phyar_cond == 1 (loop: 20, delay: 25).
[11630.333215] r8169 0000:02:00.0 eth0: rtl_phyar_cond == 1 (loop: 20, delay: 25).
[11630.333848] r8169 0000:02:00.0 eth0: rtl_phyar_cond == 1 (loop: 20, delay: 25).
[11631.354314] r8169 0000:02:00.0 eth0: link down
[11631.354390] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[11644.214991] r8169 0000:02:00.0 eth0: link up
[11644.215026] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
.
.
cat /var/log/messages | tail
.
Jul 12 05:09:24 porteus NetworkManager[2086]: <info> Activation (eth0) Stage 4 of 5 (IPv4 Configure Timeout) complete.
Jul 12 05:09:44 porteus NetworkManager[2086]: <info> (eth0): IP6 addrconf timed out or failed.
Jul 12 05:09:44 porteus NetworkManager[2086]: <info> Activation (eth0) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
Jul 12 05:09:44 porteus NetworkManager[2086]: <info> Activation (eth0) Stage 4 of 5 (IPv6 Configure Timeout) started...
Jul 12 05:09:44 porteus NetworkManager[2086]: <info> (eth0): device state change: ip-config -> failed (reason 'ip-config-unavailable') [70 120 5]
Jul 12 05:09:44 porteus NetworkManager[2086]: <info> Marking connection 'Wired connection 2' invalid.
Jul 12 05:09:44 porteus NetworkManager[2086]: <info> Activation (eth0) Stage 4 of 5 (IPv6 Configure Timeout) complete.
Jul 12 05:09:44 porteus NetworkManager[2086]: <info> (eth0): device state change: failed -> disconnected (reason 'none') [120 30 0]
Jul 12 05:09:44 porteus NetworkManager[2086]: <info> (eth0): deactivating device (reason 'none') [0]
Jul 12 05:09:44 porteus dhcpcd[2353]: eth0: removing IP address 192.168.7.94/24
..
Last edited by Rava on 12 Jul 2013, 03:11, edited 2 times in total.
Cheers!
Yours Rava

User avatar
fanthom
Site Admin
Site Admin
Posts: 4613
Joined: 28 Dec 2010, 02:42
Distribution: Porteus Kiosk
Location: Poland, currently - Cork, IE
Contact:

Re: Feedback and Bug Reports for Porteus v2.1 RC2

Post#34 by fanthom » 11 Jul 2013, 07:09

@donald
"Firefox default cache-setting 0MB ?"
yes - this is for 'always fresh' users to not fill up their '/' with firefox cache which grows rapidly.

@Rava
will update firewall against latest iptables and add a check to start it if exec bit is set on it (weird that nobody noticed it so far).
will check suspend issue in a minute.
Please add [Solved] to your thread title if the solution was found.

User avatar
Rava
Contributor
Contributor
Posts: 1319
Joined: 11 Jan 2011, 02:46
Distribution: Porteus 3.1.0 x86-64 XFCe
Location: Germany

Re: Feedback and Bug Reports for Porteus v2.1 RC2

Post#35 by Rava » 11 Jul 2013, 07:35

dmesg:

Code: Select all

[   48.759475] zram: module is from the staging directory, the quality is unknown, you have been warned.
[   48.759951] zram: Created 1 device(s) ...
[   48.801952] Adding 695096k swap on /dev/zram0.  Priority:100 extents:1 across

A warning sounds severe... What is it about?

________________________

And update on the eth0 disconnecting/connecting issue.

I connected the very machine directly to my local network, but the issue I mentioned above continues. Worked like a charm with Port 1.2 and 2.0 finale, all have been x86-64 version., when the very machine was connected like it is now.

It connects and re-connects without apparent reason (last 100 lines of /var/log/messages, minus the gpm messages that I am not yet able to keep away from being printed in the messages log. See another post on this very forum...)

Code: Select all

Jul 11 08:50:43 porteus NetworkManager[2086]: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) scheduled.
Jul 11 08:50:43 porteus NetworkManager[2086]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) complete.
Jul 11 08:50:43 porteus NetworkManager[2086]: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) started...
Jul 11 08:50:43 porteus NetworkManager[2086]: <info> (eth0): device state change: config -> ip-config (reason 'none') [50 70 0]
Jul 11 08:50:43 porteus NetworkManager[2086]: <info> Activation (eth0) Beginning DHCPv4 transaction (timeout in 45 seconds)
Jul 11 08:50:43 porteus NetworkManager[2086]: <info> dhcpcd started with pid 5183
Jul 11 08:50:43 porteus NetworkManager[2086]: <info> Activation (eth0) Beginning IP6 addrconf.
Jul 11 08:50:43 porteus NetworkManager[2086]: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) complete.
Jul 11 08:50:43 porteus dhcpcd[5183]: sending commands to master dhcpcd process
Jul 11 08:50:43 porteus dhcpcd[2353]: control command: /sbin/dhcpcd -B -K -L -G -c /usr/libexec/nm-dhcp-client.action -h porteus eth0
Jul 11 08:50:43 porteus NetworkManager[2086]: <info> (eth0): DHCPv4 client pid 5183 exited with status 0
Jul 11 08:50:43 porteus NetworkManager[2086]: <info> Activation (eth0) Stage 4 of 5 (IPv4 Configure Timeout) scheduled...
Jul 11 08:50:43 porteus NetworkManager[2086]: <info> Activation (eth0) Stage 4 of 5 (IPv4 Configure Timeout) started...
Jul 11 08:50:43 porteus NetworkManager[2086]: <info> Activation (eth0) Stage 4 of 5 (IPv4 Configure Timeout) complete.
Jul 11 08:50:48 porteus acpid: client 2395[0:1000] has disconnected
Jul 11 08:50:48 porteus acpid: client connected from 2395[0:1000]
Jul 11 08:50:48 porteus acpid: 1 client rule loaded
Jul 11 08:50:48 porteus acpid: client connected from 2395[0:1000]
Jul 11 08:50:48 porteus acpid: 1 client rule loaded
Jul 11 08:50:50 porteus acpid: client 2395[0:1000] has disconnected
Jul 11 08:50:55 porteus acpid: client 2395[0:1000] has disconnected
Jul 11 08:51:03 porteus NetworkManager[2086]: <info> (eth0): IP6 addrconf timed out or failed.
Jul 11 08:51:03 porteus NetworkManager[2086]: <info> Activation (eth0) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
Jul 11 08:51:03 porteus NetworkManager[2086]: <info> Activation (eth0) Stage 4 of 5 (IPv6 Configure Timeout) started...
Jul 11 08:51:03 porteus NetworkManager[2086]: <info> (eth0): device state change: ip-config -> failed (reason 'ip-config-unavailable') [70 120 5]
Jul 11 08:51:03 porteus NetworkManager[2086]: <info> Activation (eth0) Stage 4 of 5 (IPv6 Configure Timeout) complete.
Jul 11 08:51:03 porteus NetworkManager[2086]: <info> (eth0): device state change: failed -> disconnected (reason 'none') [120 30 0]
Jul 11 08:51:03 porteus NetworkManager[2086]: <info> (eth0): deactivating device (reason 'none') [0]
Jul 11 08:51:03 porteus dhcpcd[2353]: eth0: removing IP address 192.168.7.94/24
Jul 11 08:51:06 porteus NetworkManager[2086]: <info> Auto-activating connection 'Wired connection 2'.
Jul 11 08:51:06 porteus NetworkManager[2086]: <info> Activation (eth0) starting connection 'Wired connection 2'
Jul 11 08:51:06 porteus NetworkManager[2086]: <info> (eth0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Jul 11 08:51:06 porteus NetworkManager[2086]: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) scheduled...
Jul 11 08:51:06 porteus NetworkManager[2086]: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) started...
Jul 11 08:51:06 porteus NetworkManager[2086]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) scheduled...
Jul 11 08:51:06 porteus NetworkManager[2086]: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) complete.
Jul 11 08:51:06 porteus NetworkManager[2086]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) starting...
Jul 11 08:51:06 porteus NetworkManager[2086]: <info> (eth0): device state change: prepare -> config (reason 'none') [40 50 0]
Jul 11 08:51:06 porteus NetworkManager[2086]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) successful.
Jul 11 08:51:06 porteus NetworkManager[2086]: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) scheduled.
Jul 11 08:51:06 porteus NetworkManager[2086]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) complete.
Jul 11 08:51:06 porteus NetworkManager[2086]: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) started...
Jul 11 08:51:06 porteus NetworkManager[2086]: <info> (eth0): device state change: config -> ip-config (reason 'none') [50 70 0]
Jul 11 08:51:06 porteus NetworkManager[2086]: <info> Activation (eth0) Beginning DHCPv4 transaction (timeout in 45 seconds)
Jul 11 08:51:06 porteus NetworkManager[2086]: <info> dhcpcd started with pid 5207
Jul 11 08:51:06 porteus NetworkManager[2086]: <info> Activation (eth0) Beginning IP6 addrconf.
Jul 11 08:51:06 porteus NetworkManager[2086]: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) complete.
Jul 11 08:51:06 porteus dhcpcd[5207]: sending commands to master dhcpcd process
Jul 11 08:51:06 porteus dhcpcd[2353]: control command: /sbin/dhcpcd -B -K -L -G -c /usr/libexec/nm-dhcp-client.action -h porteus eth0
Jul 11 08:51:06 porteus NetworkManager[2086]: <info> (eth0): DHCPv4 client pid 5207 exited with status 0
Jul 11 08:51:06 porteus NetworkManager[2086]: <info> Activation (eth0) Stage 4 of 5 (IPv4 Configure Timeout) scheduled...
Jul 11 08:51:06 porteus NetworkManager[2086]: <info> Activation (eth0) Stage 4 of 5 (IPv4 Configure Timeout) started...
Jul 11 08:51:06 porteus NetworkManager[2086]: <info> Activation (eth0) Stage 4 of 5 (IPv4 Configure Timeout) complete.
Jul 11 08:51:26 porteus NetworkManager[2086]: <info> (eth0): IP6 addrconf timed out or failed.
Jul 11 08:51:26 porteus NetworkManager[2086]: <info> Activation (eth0) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
Jul 11 08:51:26 porteus NetworkManager[2086]: <info> Activation (eth0) Stage 4 of 5 (IPv6 Configure Timeout) started...
Jul 11 08:51:26 porteus NetworkManager[2086]: <info> (eth0): device state change: ip-config -> failed (reason 'ip-config-unavailable') [70 120 5]
Jul 11 08:51:26 porteus NetworkManager[2086]: <info> Activation (eth0) Stage 4 of 5 (IPv6 Configure Timeout) complete.
Jul 11 08:51:26 porteus NetworkManager[2086]: <info> (eth0): device state change: failed -> disconnected (reason 'none') [120 30 0]
Jul 11 08:51:26 porteus NetworkManager[2086]: <info> (eth0): deactivating device (reason 'none') [0]
Jul 11 08:51:26 porteus dhcpcd[2353]: eth0: removing IP address 192.168.7.94/24
Jul 11 08:51:29 porteus NetworkManager[2086]: <info> Auto-activating connection 'Wired connection 2'.
Jul 11 08:51:29 porteus NetworkManager[2086]: <info> Activation (eth0) starting connection 'Wired connection 2'
Jul 11 08:51:29 porteus NetworkManager[2086]: <info> (eth0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Jul 11 08:51:29 porteus NetworkManager[2086]: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) scheduled...
Jul 11 08:51:29 porteus NetworkManager[2086]: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) started...
Jul 11 08:51:29 porteus NetworkManager[2086]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) scheduled...
Jul 11 08:51:29 porteus NetworkManager[2086]: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) complete.
Jul 11 08:51:29 porteus NetworkManager[2086]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) starting...
Jul 11 08:51:29 porteus NetworkManager[2086]: <info> (eth0): device state change: prepare -> config (reason 'none') [40 50 0]
Jul 11 08:51:29 porteus NetworkManager[2086]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) successful.
Jul 11 08:51:29 porteus NetworkManager[2086]: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) scheduled.
Jul 11 08:51:29 porteus NetworkManager[2086]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) complete.
Jul 11 08:51:29 porteus NetworkManager[2086]: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) started...
Jul 11 08:51:29 porteus NetworkManager[2086]: <info> (eth0): device state change: config -> ip-config (reason 'none') [50 70 0]
Jul 11 08:51:29 porteus NetworkManager[2086]: <info> Activation (eth0) Beginning DHCPv4 transaction (timeout in 45 seconds)
Jul 11 08:51:29 porteus NetworkManager[2086]: <info> dhcpcd started with pid 5226
Jul 11 08:51:29 porteus NetworkManager[2086]: <info> Activation (eth0) Beginning IP6 addrconf.
Jul 11 08:51:29 porteus NetworkManager[2086]: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) complete.
Jul 11 08:51:29 porteus dhcpcd[5226]: sending commands to master dhcpcd process
Jul 11 08:51:29 porteus dhcpcd[2353]: control command: /sbin/dhcpcd -B -K -L -G -c /usr/libexec/nm-dhcp-client.action -h porteus eth0
Jul 11 08:51:29 porteus NetworkManager[2086]: <info> (eth0): DHCPv4 client pid 5226 exited with status 0
Jul 11 08:51:29 porteus NetworkManager[2086]: <info> Activation (eth0) Stage 4 of 5 (IPv4 Configure Timeout) scheduled...
Jul 11 08:51:29 porteus NetworkManager[2086]: <info> Activation (eth0) Stage 4 of 5 (IPv4 Configure Timeout) started...
Jul 11 08:51:29 porteus NetworkManager[2086]: <info> Activation (eth0) Stage 4 of 5 (IPv4 Configure Timeout) complete.
Jul 11 08:51:49 porteus NetworkManager[2086]: <info> (eth0): IP6 addrconf timed out or failed.
Jul 11 08:51:49 porteus NetworkManager[2086]: <info> Activation (eth0) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
Jul 11 08:51:49 porteus NetworkManager[2086]: <info> Activation (eth0) Stage 4 of 5 (IPv6 Configure Timeout) started...
Jul 11 08:51:49 porteus NetworkManager[2086]: <info> (eth0): device state change: ip-config -> failed (reason 'ip-config-unavailable') [70 120 5]
Jul 11 08:51:49 porteus NetworkManager[2086]: <info> Marking connection 'Wired connection 2' invalid.
Jul 11 08:51:49 porteus NetworkManager[2086]: <info> Activation (eth0) Stage 4 of 5 (IPv6 Configure Timeout) complete.
Jul 11 08:51:49 porteus NetworkManager[2086]: <info> (eth0): device state change: failed -> disconnected (reason 'none') [120 30 0]
Jul 11 08:51:49 porteus NetworkManager[2086]: <info> (eth0): deactivating device (reason 'none') [0]
Jul 11 08:51:49 porteus dhcpcd[2353]: eth0: removing IP address 192.168.7.94/24
At times I have to run dhcpcd eth0, at times not, and the pop up comes telling me network is connected or disconnected, all without any changes in the network, not even touching any cables.
Cheers!
Yours Rava

User avatar
bdheeman
Contributor
Contributor
Posts: 77
Joined: 15 Sep 2012, 19:39
Distribution: Porteus 3.0.1+ MATE/XFCE
Location: Chandigarh, PB, India
Contact:

Re: Feedback and Bug Reports for Porteus v2.1 RC2

Post#36 by bdheeman » 11 Jul 2013, 10:27

The default XFCE window manager style 'Evolve" is buggy.

Title bar is missing, title text is not shown and dragging a window from title bar with the mouse does not work at all :(
--
Balwinder S "bdheeman" Dheeman (http://bdheeman.BlogSpot.in/)
"Working together, works! The proof is GNU/Linux and F/LOSS Projects;
Do you too voluntarily work on or contribute to making any difference?"

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: Feedback and Bug Reports for Porteus v2.1 RC2

Post#37 by Ahau » 11 Jul 2013, 15:16

@bdheeman-

The issue with Evolve and xfwm4 (actually, a bug somewhere between xorg-server and xfwm4) was present in RC1 but should be fixed in RC2; Please make sure you have the correct XFCE module present. One way to tell would be to check for mpg123 since I left it out of RC1 on accident:

Code: Select all

ls -l /mnt/live/memory/images/003-lxde.xzm/var/log/packages|grep mpg
if a result is shown for mpg123, then you're using the RC2 module, if it's not there, you're still in RC1. If you've got the RC2 module and this is still happening, please check in always fresh mode to make sure you don't have the old theme files in saved changes or some other module, and if it's still there I will make a special module for you to test, I want to make 100% sure this is fixed in all cases for final as it's a very serious bug for those users that it hits (only some video drivers run into it).

@Rava -

Thanks for the report on the .gz man page. This actually was not a gzipped manpage, but a symlink with a .gz suffix. Since it was a symlink it wasn't touched by my cleanup script which only unzips real .gz files. The bad news here is that it is still pointing to a .gz man page file, so if you run 'man mpg123' it works but if you run 'man mpg321' it fails because mpg321.1.gz is pointing to mpg123.1.gz which no longer exists. I realized that I have some more of these present in my printing module, so I've written a function that finds all of these and fixes them, and added it to my cleanup script. This will be fixed in final.

@ncmprhnsbl and n2prtsusr -

I think I've isolated the problem with the right click "Build Module" and "convert tgz/txz" functions in pcmanfm but haven't quite found the right solution. There were some changes to the underlying scripts (/opt/porteus-scripts/fmanager/create-module, etc) just prior to RC2 and they seem to work in XFCE but not LXDE. It seems that when the directory name is passed to the build script it uses the full path instead of the final directory name, so you wind up with a command that looks like "dir2xzm /home/guest/home/guest/mydir /home/guest/home/guest/mydir.xzm" instead of "dir2xzm /home/guest/mydir /home/guest/mydir.xzm". I'll get that sorted out and post a fix for it. Thanks!
Please take a look at our online documentation, here. Suggestions are welcome!

User avatar
Rava
Contributor
Contributor
Posts: 1319
Joined: 11 Jan 2011, 02:46
Distribution: Porteus 3.1.0 x86-64 XFCe
Location: Germany

Re: Feedback and Bug Reports for Porteus v2.1 RC2

Post#38 by Rava » 11 Jul 2013, 19:24

@Ahau:
Thanks for that, sounds great. Hopefully that code snippet be included into all scripts that have to handle the conversation of packages into txz, be it slackware, debian or rpm ones,,,

_____________________

Update for XFCe and network issue:

I just ran my script that asks a internet page about my i-net ip to verify a working connection after FFx told me that there is no connection, and just like taht, by running my script, FFx was also able top connect, and while FFx connected, the pop up appeared telling me the network was disconnected...

Any ideas of how to further investigate this issue?
Cheers!
Yours Rava

User avatar
Saman
Black ninja
Black ninja
Posts: 32
Joined: 18 May 2013, 20:31
Distribution: Porteus 2.1 RC1 KDE / LXDE
Location: Iran

Re: Feedback and Bug Reports for Porteus v2.1 RC2

Post#39 by Saman » 11 Jul 2013, 21:43

Hello

On KDE, Please kindly add proxy settings to network settings.
All these, I can not bear to witness any longer. Can not the kingdom of salvation take me home?
-Cliff Burton R.I.P.-

donald
Full of knowledge
Full of knowledge
Posts: 1215
Joined: 17 Jun 2013, 13:17
Distribution: Porteus 3.2.2 XFCE 32bit
Location: Germany

Re: Feedback and Bug Reports for Porteus v2.1 RC2

Post#40 by donald » 12 Jul 2013, 00:21

MATE-DE_32bit

@brokenman

""What does about:cache show in FF after some browsing?""
Here it is:
This was done in fresh-mode, all FF-settings default,
Information about the Cache Service
Memory cache device
Number of entries: 861
Maximum storage size: 18432 KiB
Storage in use: 10845 KiB
Inactive storage: 10845 KiB
List Cache Entries
Offline cache device
Number of entries: 0
Maximum storage size: 512000 KiB
Storage in use: 0 KiB
Cache Directory: /home/guest/.cache/mozilla/firefox/c3pp43bg.default/OfflineCache

I don't know if this Info is needed anymore,because fanthom explained:
"Firefox default cache-setting 0MB ?"
yes - this is for 'always fresh' users to not fill up their '/' with firefox cache which grows rapidly.

xtudiux
Black ninja
Black ninja
Posts: 72
Joined: 07 Mar 2011, 06:01
Location: Philippines

Re: Feedback and Bug Reports for Porteus v2.1 RC2

Post#41 by xtudiux » 12 Jul 2013, 04:22

Porteus 2.1 rc2 wizard xfce

It boots fast but the dongle mobile isnt putting the right setup until you manually set it up unlike the on in v2.0.

The corruption of the OK button is no longer there(this one I have experience randomly in v2.0 PPM).

Will further test it later... :D

Thx for the work...heheheh

PS. is the blueman be included in the iso???
Last edited by xtudiux on 12 Jul 2013, 10:05, edited 1 time in total.

User avatar
ncmprhnsbl
DEV Team
DEV Team
Posts: 959
Joined: 20 Mar 2012, 03:42
Distribution: 3.2.2-64bit xfce/openbox
Location: australia
Contact:

Re: Feedback and Bug Reports for Porteus v2.1 RC2

Post#42 by ncmprhnsbl » 12 Jul 2013, 07:01

kde 64 rc2 wizard built

"Build Module" not working same as lxde^, txz > xzm works here and deb>xzm.
missing superuser dolphin in menu(classic style) ....and kicker..

Tablet settings correctly detects my wacom intuos5 and enables button setting(definately not a bug)
Forum Rules : http://forum.porteus.org/viewtopic.php?f=35&t=44

User avatar
fanthom
Site Admin
Site Admin
Posts: 4613
Joined: 28 Dec 2010, 02:42
Distribution: Porteus Kiosk
Location: Poland, currently - Cork, IE
Contact:

Re: Feedback and Bug Reports for Porteus v2.1 RC2

Post#43 by fanthom » 12 Jul 2013, 09:34

@Rava
tested suspend on kde4 and ethernet connection is restored properly after waking up.
could you check on kde4 desktop just to make sure it's not nm-applet related (i use networkmanagement in kde4)?

@saman
"On KDE, Please kindly add proxy settings to network settings."
proxy kcm module belongs to konqueror (same as samba kcm) and it affects konqueror settings only. we dont have konqueror in default ISO so there is no point for bringing these kcm modules in.

@ncmprhnsbl
yup - seems that something broke after last update. will double check all dolphin menu services for final.

thanks guys
Please add [Solved] to your thread title if the solution was found.

User avatar
Saman
Black ninja
Black ninja
Posts: 32
Joined: 18 May 2013, 20:31
Distribution: Porteus 2.1 RC1 KDE / LXDE
Location: Iran

Re: Feedback and Bug Reports for Porteus v2.1 RC2

Post#44 by Saman » 12 Jul 2013, 12:25

fanthom wrote:@proxy kcm module belongs to konqueror (same as samba kcm) and it affects konqueror settings only. we dont have konqueror in default ISO so there is no point for bringing these kcm modules in.
Dear Fanthom,
So, Should I install samba to apply a general proxy heavily on all applications for example PPM or Terminal on KDE? in fact I need to authenticate via a username/password through a proxy, and no other thing except Firefox access the network :(

Meanwhile, I investigated a bug in new KDE, opening "some" windows causes the window to close/open intermittently for example:
KDE System Settings > Window decorations > Get new decorations
All these, I can not bear to witness any longer. Can not the kingdom of salvation take me home?
-Cliff Burton R.I.P.-

User avatar
wread
Module Guard
Module Guard
Posts: 1091
Joined: 09 Jan 2011, 18:48
Distribution: Porteus v3.2.5-kde5-64 bits
Location: Santo Domingo
Contact:

Re: Feedback and Bug Reports for Porteus v2.1 RC2

Post#45 by wread » 12 Jul 2013, 13:38

@fanthom, @saman

Maybe we can put kcm proxy in rootcopy or make an extra module for those who need it with other browsers. For instance, you can use a proxy with chromium too. Click the button top right (three dashes)>Settings>Show advanced settings...>Change proxy settings...
This is useful in schools and universities, where they block access to many download-sites, so that the students won't overload bandwidth getting large files downloaded. Using a proxy, through a mobile phone, they can access otherwise blocked sites (mostly youtube!).

I will try to make this patch..

Regards

PS: I could not reproduce saman's bug at window decorations
Porteus is proud of the FASTEST KDE ever made.....(take akonadi, nepomuk and soprano out and you will have a decent OS).
The Porteus Community never sleeps!

Post Reply