3.2.2 migration to 4.0 problem.

[Ed_P]

Jack, when you boot up and it hangs, press alt+PrtScr+e and see what happens.

[jssouza]

Ed_P, could you try booting with your 3.2.2 changes into text mode (cheatcode 3).
Then, either login as root and then run slim
Or, login as guest and then run startx
Please check if any of the above works with your changes.

[Ed_P]

I did as you asked jssouza or at least I thought I did. I used the cheatcode 3 and booted with my 3.2.2 changes, minus the network files. I logged in as root and ran slim and it is what I am running as I write this.

I suspect you want me to boot with the 3.2.2 network changes and that I didn't do. I will retry with those for you. But based on tests I have run with the current systems, OS & DE, there is a network file problem with changes saved in the current system's save.dat file.

BTW I'm reasonable certain starting startx requires the root login.

[Ed_P]

Wow!! jssouza, I booted using the 3 cheatcode and with my 3.2.2 changes mod that includes the network folders, logged in as root and started slim and here I am writing this!!

Let me retry with startx.

[Ed_P]

This is getting weird. Rebooted using the 3 cheatcode and my 3.2.2 changes that includes the network folders, logged in as guest and started startx!! (yes, you were right) And here I am again posting.

I am happy, and I suspect brokenman is also, but I don't understand how booting to text mode then starting slim or startx manually gets around the booting hanging problem.

I'll have to try this approach with my save.dat file.

[Ed_P]

Unbelievable!! Booting without my changes modules from 3.2.2 but rather with the save.dat file created with 4.0 and with a wi-fi network connection saved the system booted using the text mode cheatcode.

BTW in each test when the DE appeared I was connected to my wi-fi network.

[jssouza]

I don't understand how booting to text mode then starting slim or startx manually gets around the booting hanging problem.

Booting to text mode and then starting slim/X does two things:
1. Bypasses calling of /etc/rc.d/rc.4
2. Gives some time for something in base to stabilize before X and the DE (and along with it the nm-applet) are started

Re: 1 - I checked my notes and saw that I had fixed some gnome-keyring-daemon warnings in rc.4 long back in the cinnamon module dated 15-10-2017. Could you comment out the line

Code: Select all

/sbin/setcap cap_ipc_lock=+ep /usr/bin/gnome-keyring-daemon

in /etc/rc.d/rc.4, include it in your changes and boot to graphics with your changes (which also has your network configs)?

Or, boot to text mode, login as root and run telinit 4, which I think calls the rc.4 script.

BTW, my network configs of /etc/NetworkManager/system-connections/ are in an xzm module in $PORTDIR/modules that always get loaded during bootup, but I do not have any boot issues. Maybe this is wifi card/driver related. I have a marvell chipset.

[brokenman]

Can gnome-keyring-daemon be started elsewhere, perhaps in the autostart desktop file?

[Ed_P]

Could you comment out the line

Code: Select all

/sbin/setcap cap_ipc_lock=+ep /usr/bin/gnome-keyring-daemon

in /etc/rc.d/rc.4, include it in your changes and boot to graphics with your changes (which also has your network configs)?

Did as you asked, booting to graphics, with my changes, hung same as before.

Code: Select all

#!/bin/bash
#
# rc.4		This file is executed by init(8) when the system is being
#		initialized for run level 4.

# Run X11 startup helper:
pidof watch-xorg >/dev/null && sleep 4 || /opt/porteus-scripts/xorg/watch-xorg 2>/dev/null &

# Set IPC caps to GKD
#/sbin/setcap cap_ipc_lock=+ep /usr/bin/gnome-keyring-daemon

# Start Cinnamon desktop:
login=`egrep -o " login=[^ ]+*" /proc/cmdline | cut -d= -f2`
nologin=`grep -o nologin /proc/cmdline`
[ "$login" ] && sed -i 's/^.*default_user.*/default_user '$login'/g' /etc/slim.conf
[ "$nologin" ] && sed -i 's/^auto_login/#auto_login/g' /etc/slim.conf
/usr/bin/slim

BTW jssouza right clicking to rename a file in the /home/guest folder doesn't highlight the file's name when booted in text mode. And I even have Evo-Vertex-06.08.2017.xzm loaded.

[jssouza]

brokenman, gnome-keyring-daemon is started in xdg autostart. In rc.4, I am just setting capabilities on the binary itself, I think to supress some warnings. Maybe there is another place this can be set. This has to be done as root.

Ed_P, ok, other than that rc.4 should be same as that of 3.2.2.

right clicking to rename a file in the /home/guest folder doesn't highlight the file's name when booted in text mode. And I even have Evo-Vertex-06.08.2017.xzm loaded.

Evo-Vertex should be included in the latest cinnamon, but the default theme is still adwaita. Have you set it as the theme? System Settings->Appearance->Themes->Controls and change Adwaita to Evo Vertex.

[Ed_P]

Well obviously your rc.4 file change isn't the problem. I'll uncomment the line.

I was changing the font not the theme.

BTW brokenman found this approach works. Apparently your Cinnamon is too fast.

Also the latest cinnamon doesn't boot for me unless I delay the startup. I learned that the delay cheatcode does not work also. cliexec=sleep~1 allows cinnamon to boot. Still looking into it, if you find the answer please chime in. I don't think it's gnome-keyring but something is starting in the wrong order.

[brokenman]

n rc.4, I am just setting capabilities on the binary itself, I think to supress some warnings. Maybe there is another place this can be set. This has to be done as root.

Sorry. I'm paying attention now. Didn't even see the call to setcap. Interesting fix ... not so sure it is the right way to do it though. Is this an upstream bug in gnome-keyring?

[Ed_P]

cliexec=sleep~1 didn't work for me. Booting still hung.

[jssouza]

Interesting fix ... not so sure it is the right way to do it though. Is this an upstream bug in gnome-keyring?

Gnome Keyring Daemon was not able to allocate secure memory. So CAP_IPC_LOCK capability was set on the binary.

[wread]

Try taking out NetworkManager and ModemManager of 001-core. Traditionally they both belong in 002-xorg. The 001-core module includes the pns-tool from fanthom, so one can connect to the net easily in text mode; you don't need NetworkManager. That way you will definitely find out if NM is the cause of the trouble...