Bug reports

Arch based Porteus community project
User avatar
ncmprhnsbl
DEV Team
DEV Team
Posts: 890
Joined: 20 Mar 2012, 03:42
Distribution: 3.2.2-64bit xfce/openbox
Location: australia
Contact:

Re: Bug reports

Post#46 by ncmprhnsbl » 12 Oct 2015, 03:59

guest login working here,,, check you dirs ownerships.. ls -la /home/guest
tracked my polkit permission errors bck to faulty build practice.... (or so i thought, see below)
files in TREE (at least) must be owned by root : etc, home,usr,var ended up owned by guest
############################
still no auto wired network (i see you're moving to netctl)

Code: Select all

pstree
systemd-+-dbus-daemon
        |-gpg-agent
        |-login---bash---pstree
        |-systemd---(sd-pam)
        |-systemd-journal
        |-systemd-logind
        |-systemd-network
        |-systemd-resolve
        |-systemd-timesyn---{sd-resolve}
        `-systemd-udevd
systemctl start dhcpcd works without issue now

Code: Select all

pstree
systemd-+-dbus-daemon
        |-dhcpcd
        |-gpg-agent
        |-login---bash---pstree
        |-polkitd-+-{JS GC Helper}
        |         |-{JS Sour~ Thread}
        |         |-{gdbus}
        |         |-{gmain}
        |         `-{runaway-killer-}
        |-systemd---(sd-pam)
        |-systemd-journal
        |-systemd-logind
        |-systemd-network
        |-systemd-resolve
        |-systemd-timesyn---{sd-resolve}
        `-systemd-udevd
but then... after reboot with pman-settings.xzm
its back to old behaviour.... other modules created don't have this effect..

Code: Select all

pstree
systemd-+-dbus-daemon
        |-gpg-agent
        |-login---bash---pstree
        |-systemd---(sd-pam)
        |-systemd-journal
        |-systemd-logind
        `-systemd-udevd
################################
made a bundle module -- worked fine , except
because the name (moc-1:2.5.0-3...) contained a colon(:) , it wouldnt read/load at bootup(said: corrupt?)
it activated live no prob and after renaming started at boot ok
but the bundled pkgs were also installed in /changes (when using that cheatcode)..
############
i see perl is there now, so i got lm_sensors >>> all good..
############
i see the unmount fail messages(breifly) at poweroff but have no ideas..
Forum Rules : http://forum.porteus.org/viewtopic.php?f=35&t=44

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

Re: Bug reports

Post#47 by brokenman » 12 Oct 2015, 04:11

Thanks. Nice reports. Please build as root.

For the pman-settings.xzm please see here. Something maybe you can troubleshoot.
Outstanding problems (Post by brokenman #37566)
because the name (moc-1:2.5.0-3...) contained a colon(:) , it wouldnt read/load at bootup(said: corrupt?)
Nice catch. Will check this out.
but the bundled pkgs were also installed in /changes (when using that cheatcode)..
Yes, because pacman installs the package. What do you suggest we do here? Check for changes cheatcode and not copy to modules folder?
How do i become super user?
Wear your underpants on the outside and put on a cape.

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

Re: Bug reports

Post#48 by ncmprhnsbl » 12 Oct 2015, 05:44

brokenman wrote:What do you suggest we do here? Check for changes cheatcode and not copy to modules folder?
what the behaviour in porteus? (i never use changes) are pkgs both installed to changes and modules made?
if so ,then there is no issue..
Forum Rules : http://forum.porteus.org/viewtopic.php?f=35&t=44

beny
Full of knowledge
Full of knowledge
Posts: 729
Joined: 02 Jan 2011, 11:33
Location: italy

Re: Bug reports

Post#49 by beny » 12 Oct 2015, 11:32

hi brokenman su guest give me a su:failed to execute /bin/bash: permission denied from root to su guest.

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

Re: Bug reports

Post#50 by brokenman » 13 Oct 2015, 04:27

what the behaviour in porteus?
In porteus the modules are activated and on shutdown they are removed from the live file system. On the next boot if they are not in the modules folder then they won't get loaded. In nemesis pacman installs the files so they will show up in the changes folder as installed. Then on the next boot the module will also be loaded into aufs and sit on a layer above the installed version, overwriting it. This double up is not a problem but it is also bloat. I think if changes are being used then perhaps asking the user what they want to do would be best.

Perhaps just download the packages (pacman -Sw package) and then create the module from them, providing the /var/lib/pacman/local files are all instact. Will check it out.

@Beny
Please download the latest ISO and check if it resolves this issue. Thanks.
How do i become super user?
Wear your underpants on the outside and put on a cape.

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

Re: Bug reports

Post#51 by ncmprhnsbl » 13 Oct 2015, 05:34

brokenman wrote:Perhaps just download the packages (pacman -Sw package) and then create the module from them
that had crossed my mind,
and then activate them or ask to..
and if using changes is detected ask if you want modules,bundle or plain install or both

nemesis-v1.1.0-151012-x86_64.iso installed to usb
fresh
login guest ok
su works but gives "failed to get D-Bus connection: operation not permitted"
login root ok
su guest works but "failed to get D-Bus connection: operation not permitted"

network all good, systemd happy:

Code: Select all

systemd-+-dbus-daemon
        |-dhcpcd
        |-login---bash---pstree
        |-systemd---(sd-pam)
        |-systemd-journal
        |-systemd-logind
        |-systemd-resolve
        |-systemd-timesyn---{sd-resolve}
        `-systemd-udevd

systemctl --failed
0 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.
--------------------------------
With pacman-config
guest login fails
root login ok
su to guest su:failed to execute /bin/bash: permission denied (i have to recheck all this, done only once)
network working even tho there are service failures

Code: Select all

systemd-+-dbus-daemon
        |-dhcpcd
        |-login---bash---pstree
        |-systemd---(sd-pam)
        |-systemd-journal
        |-systemd-logind
        `-systemd-udevd
systemctl is-system-running
degraded

systemctl --failed
  UNIT                      LOAD   ACTIVE SUB    DESCRIPTION
● systemd-networkd.service  loaded failed failed Network Service
● systemd-resolved.service  loaded failed failed Network Name Resolution
● systemd-timesyncd.service loaded failed failed Network Time Synchronization
● systemd-networkd.socket   loaded failed failed networkd rtnetlink socket
Forum Rules : http://forum.porteus.org/viewtopic.php?f=35&t=44

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

Re: Bug reports

Post#52 by brokenman » 13 Oct 2015, 14:41

Thanks. I located the problem of the pacman-settings.xzm file breaking some services. Replacing all mksquashfs commands in setup-pman with dir2xzm fixes it. It must therefore be a permissions problem. One thing that bugs me is that dir2xzm always returns an error code 1 even though the module creation is successful. I have to play with mksquashfs commands under arch more to see what is going on.

The dbus error is on my 'outstanding problems' list. Everything works ok even though the error is thrown, but I think it will affect things in stage 002. It is certainly related to the way systemd handles sessions, but I haven't figured it out yet.
How do i become super user?
Wear your underpants on the outside and put on a cape.

User avatar
francois
Contributor
Contributor
Posts: 5000
Joined: 28 Dec 2010, 14:25
Distribution: kde xfce porteus manjaro kubun
Location: Enfin l'été, le changement climatique attendu: le soleil.

Re: Bug reports

Post#53 by francois » 13 Oct 2015, 17:08

@brokenman:
Perhaps just download the packages (pacman -Sw package) and then create the module from them, providing the /var/lib/pacman/local files are all instact. Will check it out.

Or simply work in changes= or persistant mode to provide pman-settings.xzm

Personally, I am trying to understand the difference between the pacman and the pman use on the system. This has been upsetting me since the beginning. They do not have the same effect on the system.
Voltaire: Le mieux est l'ennemi du bien.

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

Re: Bug reports

Post#54 by brokenman » 14 Oct 2015, 01:35

Personally, I am trying to understand the difference between the pacman and the pman use on the system.
If you have any specific questions about it please ask. Essentially pman is just a wrapper that does the following:

1) Starts an inotify daemon to watch the folder /var/cache/pacman/pkgs
2) Runs pacman with the same command as was passed to it.
3) If a package lands in the watched folder it processes it (converts to module)

The last step is to create a module. The mksquashfs command (in older nemesis versions) was producing a module that had a strange effect on the system. I tracked that down to not settings certain permissions before making the module. When the pman-settings.xzm module loaded at boot it broke many things. The latest ISO should fix that.
How do i become super user?
Wear your underpants on the outside and put on a cape.

User avatar
francois
Contributor
Contributor
Posts: 5000
Joined: 28 Dec 2010, 14:25
Distribution: kde xfce porteus manjaro kubun
Location: Enfin l'été, le changement climatique attendu: le soleil.

Re: Bug reports

Post#55 by francois » 14 Oct 2015, 02:52

Your explanations and especially your inspiring and hard work, are really appreciated.

This said, I have not worked with pman in the last few days. Maybe pman of your last nemesis version does the same job as converting the changes folder, but in a more detailed and compact way.

I will look at that for sure. :wink:
Voltaire: Le mieux est l'ennemi du bien.

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

Re: Bug reports

Post#56 by brokenman » 14 Oct 2015, 03:46

If your end goal is just to get a working desktop and you are not concerned about space, or having modules, then saving changes (along with pacman) will do the job for you. pman is designed for people that want to create a lightweight modular system without saving changes ... as in the default porteus install. Hope that clears it up.
How do i become super user?
Wear your underpants on the outside and put on a cape.

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

Re: Bug reports

Post#57 by ncmprhnsbl » 14 Oct 2015, 05:19

ok ,, with nemesis-v1.1.1-151013-x86_64.iso
pmansettings issues resolved afaics
issues remaining:
su /dbus connection error
maybe these bug reports are related...
https://bugs.archlinux.org/index.php?st ... =&do=index

shutdown unmount /mnt/live failures
so whats happening here?
at boot initrd creates all the filesystem and mnt/live/ etc. before systemd starts? or?
what happens at poweroff? systemd trys to unmount stuff it never mounted? or is being used?
because systemd doesnt hand back to initrd at shutdown? or does it?
do we need systemd to unmount /mnt/live ? it seems to get over it pretty fast..
is this just ugly messages(and how to avoid them)? or something broken?
sorry for all the questions.. its more a statement of ignorance..

and
is Alt+arrows supposed to change tty?
Forum Rules : http://forum.porteus.org/viewtopic.php?f=35&t=44

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

Re: Bug reports

Post#58 by brokenman » 15 Oct 2015, 00:12

Thanks. Can you please fix the url code? Long link and I can't see it all.

Regarding shutdown, I am not sure what is going on yet. I haven't looked at it. It appears as though systemd doesn't hand back to initrd, but should still be able to unmount aufs cleanly. You can see the output by testing in virtualbox and setting the processor percentage down real low, then getting ready with print screen. I haven't had any cataclysmic problems with it, but francois did report a frozen shutdown at one point. In any case I would like to clean it up, perhaps by running a custom script at shutdown. I will bet my back teeth that the code for the shutdown procedure in systemd is a binary blob. I'll check it out this week.
How do i become super user?
Wear your underpants on the outside and put on a cape.

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

Re: Bug reports

Post#59 by ncmprhnsbl » 15 Oct 2015, 00:38

brokenman wrote:Can you please fix the url code? Long link and I can't see it all.
sorry about that...
might be easier : duckduckgo > !archbugs dbus
they seem to stem from 226 systemd update , which has exposed a dbus problem,apparently..
brokenman wrote:I will bet my back teeth that the code for the shutdown procedure in systemd is a binary blob.
fairly safe bet, that..
Forum Rules : http://forum.porteus.org/viewtopic.php?f=35&t=44

User avatar
francois
Contributor
Contributor
Posts: 5000
Joined: 28 Dec 2010, 14:25
Distribution: kde xfce porteus manjaro kubun
Location: Enfin l'été, le changement climatique attendu: le soleil.

Re: Bug reports

Post#60 by francois » 15 Oct 2015, 03:13

@ncm...:
https://wiki.archlinux.org/index.php/Sy ... _gettys.3F
If you want to change this behavior, then edit /etc/systemd/logind.conf and change the value of NAutoVTs. If you want all [Fx] keys to start a getty, increase the value of NAutoVTs to n

Actually NAutoVTs is not set for nemesis /etc/systemd/logind.conf:
#NAutoVTs=6
Voltaire: Le mieux est l'ennemi du bien.

Locked