Porteus Nemesis v3.2 BUG REPORTS

Arch based Porteus community project
aus9

Re: Porteus Nemesis v3.2 BUG REPORTS

Post#16 by aus9 » 16 Nov 2015, 06:02

this post devoted to request to run mouse commands

Code: Select all

su
Password: 
Failed to connect to bus: Operation not permitted
root /home/guest # /usr/local/bin/setup-mouse
property 'libinput Tapping Enabled' doesn't exist, you need to specify its type and format
property 'libinput Disable While Typing Enabled' doesn't exist, you need to specify its type and format
property 'libinput Horizontal Scroll Enabled' doesn't exist, you need to specify its type and format
root /home/guest # setup-mouse
property 'libinput Tapping Enabled' doesn't exist, you need to specify its type and format
property 'libinput Disable While Typing Enabled' doesn't exist, you need to specify its type and format
property 'libinput Horizontal Scroll Enabled' doesn't exist, you need to specify its type and format
mouse is still working fine

aus9

Re: Porteus Nemesis v3.2 BUG REPORTS

Post#17 by aus9 » 16 Nov 2015, 06:21

this post devoted to suggestions on /etc/group
In looking at the bus issue I found mention of something that led me here...ran as guest

Code: Select all

$ groups
wheel users
suggest guest be added to the following groups but on cd logout and login as guest does not seem to make a dot of difference to the su command
or instead of guest use users

dbus
audio
video

Now we know that exist file for wheel as a comma and not a full colon and it works whereas I always thought you needed the :

aus9

Re: Porteus Nemesis v3.2 BUG REPORTS

Post#18 by aus9 » 16 Nov 2015, 06:40

DON'T DO THIS

I had a go at attempting to see if dbus will play with me and ended up with a frozen mouse and frozen kb etc

Code: Select all

su
passwd
systemctl stop dbus.service

aus9

Re: Porteus Nemesis v3.2 BUG REPORTS

Post#19 by aus9 » 16 Nov 2015, 07:45

su and Failed to connect to bus: Operation not permitted.....now solved

In case I failed to say so earlier, the previous posts about this error message occurs but I still get root.

2) rebooted cd and tried su -c but same error

3) open new terminal tab and just use sudo command works without dbus error.

eg

Code: Select all

sudo ls
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: 
Desktop  Documents  Downloads  Music  Pictures	Public	Templates  Videos
Now that I have been lectured, repeating the sudo command works as

Code: Select all

sudo ls
Desktop  Documents  Downloads  Music  Pictures	Public	Templates  Videos
Suggest you mention this in your how to get it post one?

aus9

Re: Porteus Nemesis v3.2 BUG REPORTS

Post#20 by aus9 » 16 Nov 2015, 07:54

but this introduces a new possible bug after being lectured.

Code: Select all

sudo cd /tmp
sudo: cd: command not found
I can get around it by

Code: Select all

guest ~ $ cd /tmp
guest /tmp $ sudo ls
ssh-FtIUUldDBojg  systemd-private-1922138e841942e18cf432a9e3c306a9-systemd-timesyncd.service-s3bsoi
now whats going on below?

Code: Select all

su
find / -name cd
/mnt/live/memory/images/002-xorg.xzm/usr/share/X11/xkb/symbols/cd
/usr/share/X11/xkb/symbols/cd
find: File system loop detected; `/sys/kernel/debug/pinctrl' is part of the same file system loop as `/sys/kernel/debug'.
root /tmp # ls /bin/cd
ls: cannot access /bin/cd: No such file or directory
root /tmp # ls /sbin/cd
ls: cannot access /sbin/cd: No such file or directory
root /tmp # ls /usr/sbin/cd
ls: cannot access /usr/sbin/cd: No such file or directory
root /tmp # ls /usr/bin/cd
ls: cannot access /usr/bin/cd: No such file or directory
root /tmp # ls /usr/local/bin/cd
ls: cannot access /usr/local/bin/cd: No such file or directory
root /tmp # ls /usr/local/sbin/cd
ls: cannot access /usr/local/sbin/cd: No such file or directory
OK lets look at another easy command=ls

Code: Select all

root /usr/bin # ls -al /usr/bin/ls
-rwxr-xr-x 1 root root 122352 Nov 15 16:37 /usr/bin/ls
root /usr/bin # ls -al /usr/bin/cd
ls: cannot access /usr/bin/cd: No such file or directory
me thinks cd should be in the same dir as ls ?

aus9

Re: Porteus Nemesis v3.2 BUG REPORTS

Post#21 by aus9 » 16 Nov 2015, 11:13

this next bit, not sure if its a bug but posting here as it gives an error message that others might help me resolve?

This is HD bootup

Firstly I have 2 folders on /mnt/sda3 nemesis and porteus
I downloaded the latest iso and copied over various bits.

In attempting to use cheatcode changes=/nemesis I got an error similar to below altho I did not record the exact wording, but the bottom of the screen is similar to
sgn file not found.

2) so I checked and file is 644 /mnt/sda3/nemesis/porteus-v3.2-86_64.sgn

new cheatcode
changes=/nemesis sgnfile= /mnt/sda3/nemesis/porteus-v3.2-86_64.sgn
record error message follows

Code: Select all

searching for /mnt/sda3/nemesis/porteus-v3.2-86_64.sgn
device not ready yet

(snip)  in coloured text
porteus data not found
3) I deleted a folder called /data from sda3, not sure if that is relevant. Instead I am concerned that device not ready means because its not ready, it can't search it and find the sign file?

but why?

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

Re: Porteus Nemesis v3.2 BUG REPORTS

Post#22 by brokenman » 16 Nov 2015, 13:31

The linger function goes like this:

Code: Select all

loginctl enable-linger username
It enables the logged in user to linger after logging in under another user, hopefully keeping the root dbus session alive.
I am really stuck on this error message, although it doesn't affect anything it looks ugly.

EDIT: linger does not solve anything. I thought systemd released 227 saying it would use a shared bus, but I am not seeing this. /run/user/0 and /run/user/1000 are being used instead.

@aus9
The cheatcode should be delay=5

On my hd bootup it fails by not finding the sign file called porteus-3.2*.sgn even though I have it at the base of /mnt/sda3/nemesis
I am testing on a frugal installation on HD at /mnt/sda9/nemesis. So the structure should look like this: /mnt/sda9/nemesis/{EFI,boot,config,porteus}
Check that you don't have other nemesis installed that initrd may be finding. For multiple installs it is best to use the from= cheatcode.
How do i become super user?
Wear your underpants on the outside and put on a cape.

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

Re: Porteus Nemesis v3.2 BUG REPORTS

Post#23 by brokenman » 16 Nov 2015, 14:24

When booting with changes= cheatcode (default) shutdown hangs with stopjob waiting for lxdm service to shutdown.
Next boot with changes= hangs on startup. Serious bug.
How do i become super user?
Wear your underpants on the outside and put on a cape.

fullmoonremix

Re: Porteus Nemesis v3.2 BUG REPORTS

Post#24 by fullmoonremix » 16 Nov 2015, 16:48

Salutations... :good:

Porteus (Nemesis Edition?) hangs before login when I use the "changes" and/or "rootcopy" cheatcode.
Otherwise it's the best thing since sliced bread. Perhaps I'll try the "from" cheatcode.

Best Regards... :beer:

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

Re: Porteus Nemesis v3.2 BUG REPORTS

Post#25 by brokenman » 16 Nov 2015, 18:09

Yes, as per post above yours, it hangs when using changes=. It is related to mtab being copied to changes folder. I am looking into this. rootcopy should still function, at least it works fine for me. Check permissions of stuff in rootcopy.

I am also expecting some reports of shutdown being heldup waiting for a stop job to finish. I need to revise the shutdown procedure again.
How do i become super user?
Wear your underpants on the outside and put on a cape.

User avatar
Blaze
Moderator
Moderator
Posts: 1386
Joined: 28 Dec 2010, 11:31
Distribution: ⟰ Porteus 3.2 Cinnamon x86_64
Location: ☭ Russian Federation, Lipetsk region, Dankov
Contact:

Re: Porteus Nemesis v3.2 BUG REPORTS

Post#26 by Blaze » 16 Nov 2015, 18:50

brokenman wrote:
It is bug repeated over and over again on my mouse.
Is it firmware? How do you fix it?
I can't to check this, because my Porteus Nemesis v3.2 after reboot received this error with systemd :)

Code: Select all

ln: /union/etc/systemd/system/multi-user.target.wants/lxdm.service: File exists
I don't touched lxdm.service

After clean changes

Code: Select all

root ~ # /usr/local/bin/setup-mouse
property 'libinput Tapping Enabled' doesn't exist, you need to specify its type and format
property 'libinput Disable While Typing Enabled' doesn't exist, you need to specify its type and format
property 'libinput Horizontal Scroll Enabled' doesn't exist, you need to specify its type and format
root ~ # 
Linux porteus 4.12.7-porteus #1 SMP PREEMPT Sun Aug 13 17:38:30 x86_64 Intel(R) Core(TM) i5-6600K CPU @ 3.50GHz GenuineIntel GNU/Linux
MS-7A12 » [AMD/ATI] Tobago PRO [Radeon R7 360 / R9 360 OEM] (rev 81) » Vengeance LPX 16GB DDR4 K2 3200MHz C16

aus9

Re: Porteus Nemesis v3.2 BUG REPORTS

Post#27 by aus9 » 16 Nov 2015, 23:32

booted cd with cheatcode delay=5
cat /proc/cmdline
quiet initrd=initrd.xz changes=/porteus delay=5 BOOT_IMAGE=vmlinuz
During the bootup I can see a kernel message paraphrased as
delay 5 seconds waiting for slow devices to settle up

That is very good......but
on login to desktop USB mouse is stil frozen so I redid my cable trick.
IMHO it looks like its not a delay that resolved this, but needs some better cheatcode for USB input devices to have at the menu?

2) forgot to mention that the slowness of MC has disappeared with this rebuild which is very nice

aus9

Re: Porteus Nemesis v3.2 BUG REPORTS

Post#28 by aus9 » 16 Nov 2015, 23:54

am testing on a frugal installation on HD at /mnt/sda9/nemesis. So the structure should look like this: /mnt/sda9/nemesis/{EFI,boot,config,porteus}
I am confused by this ^^ at end of line you say porteus so you mean I have keep the name as porteus?

Is that because on line 43, FOLDER is hardcoded as porteus?
http://paste.debian.net/333189/

^^ cd file called init at base of cd

AS I know there is a 10 hour difference between BR and AU I have elected to do things in a more simple way.
I moved Slackware porteus into a hidden folder and renamed nemesis to porteus and adjusted my grub config to keep it simple
and hd bootup has worked.

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

Re: Porteus Nemesis v3.2 BUG REPORTS

Post#29 by brokenman » 17 Nov 2015, 00:51

Yes you got it. Fine work. It is hard coded in initrd to look for the .sgn file in a folder called porteus.

For the next few releases Poreus Nemesis will use the exact same structure as Slackware Porteus. This means no nemesis folders. No Nemesis names.
I left my storage folder wth the name nemesis just for identification purposes.

Regarding the USB mouse I will procure one and do some testing. If you find the answer in the meantime please let me know.
How do i become super user?
Wear your underpants on the outside and put on a cape.

aus9

Re: Porteus Nemesis v3.2 BUG REPORTS

Post#30 by aus9 » 17 Nov 2015, 04:11

hd bootup still hangs but I made small progress by getting less errors?

First I boot up something else, and go into nemesis (called porteus)/changes/etc and delete the entire folder called system.d
Second I use grub cheatcode line that now reads
kernel /3/nemvm root=LABEL=p3 changes=LABEL:p3/porteus norootcopy
don't worry the kernel is called nemvm as I like to shorten names to make my kernel line shorter to read.
the 3 focusses my brain that I am on partition 3
changes entry changed from /porteus
norootcopy added.

bootup no longer shows any error messages that others have reported about the lxde file
bootup says something like paraphrased norootcopy dir skipped

2) last message on screen is
"live system is ready now - starting Porteus"
and then it hangs

#############################
I tried to boot the cd with a changed line that read
from=/mnt/sda3/porteus changes=/mnt/sda3/porteus
but that failed for me.

Locked