(lightDM-) login frozen and keymap error messages after update

hank2121

well, after three days (in total) of upgrading (GhostBSD/Xlibre) and get it running , re-installing and configuring painfully my VirtualBox VMs, the last bigger update from yesterday killed my lightdm - desktop/login. Mouse and keyboard are frozen and error messages: "gkr-pam , convert keymap.pl - unable to localise daemon control file" or similar shows up!
So had to go back to yesterdays backup (boot environment 3of5) cause couldnt login anymore and only one boot environment worked back to normal. Why are these big updates now comin so rapidly after another and what means " insecure directory" with intropy or something like that in connection with zsh shell? I want to use bash anyway and always have to replace it in the scripts...
I have no time for all these re-installations and configurations at the moment, so have the feeling, the updates are comin a bit in a hurry right now ...
The Toshiba is now on GhostBSD 26.1-R15.0p5 with greybird and elementary-xfce (xfce 4.20).
There were around 360 packages to update, comin in yesterday eveing, and one extra update afterwards (1 package).
But as I can t navigate after these updates, i can t search in actual logs for infos...
my desktop is still on 25.0x cause of this, cause thats my workin environment.

vimanuelt

hank2121
If your computer is in production, then I suggest taking routine backups to avoid loss of data.

What I do is use a desktop with two hard disk drives, one drive for the operating system (ada0) and the other drive for my user home directory (/home/vic) on ada1. Whenever there is a serious issue, I can reinstall the OS on ada0 and later mount my user account without any issues. For laptop users with only a single disk, backing up data to a USB drive works well.

vimanuelt

Updates happen when needed. The latest update moved us from p5 to p8. Usually, if you see only one package, it means the update is for the pkg package itself. After the pkg package is updated, the system must download the new package library. This library contains packages built for the new kernel version. This is normal behavior and nothing unusual.

hank2121

vimanuelt

well, I know this my friend. that one package came after the 36x plus packages and after the normal mask with "restart" I did and login was not possible.

hank2121

vimanuelt agree on that.

hank2121

vimanuelt Vic, I do my backups but I m lost, if I cant get back to a working desktop, when the login (lightDM) screen is locked and doesn t allow input. But all worked before I did that major update this morning...
Is there a chance to update via commandline on a or do i run into the same problems, not be able to login after update again?
I don t know, what best strategy wd be, after restoring from BE backup a couple of hours before I ran that update... so, now back on p5 instead of 26.1-R15.0p8.
And because of this login problem, my desktop GhostBSD is still on 25.02-R14.3 p8. I need at least one working machine. ;-)

ericbsd

The package for VirtualBox got renamed to virtualbox-ose-additions-xlibre-72 before it was xlibre-virtualbox-ose-additions-72.

hank2121

ericbsd ooops, with all posts I lost overview. Thx Eric, will check this over the weekend and try my best. ;-)
On my ThinkPad testbed system is on xorg after upgrade, so I can test both versions later, VirtualBox with xorg and with xlibre, that s good.

hank2121

well, folks, not to run into misunderstandings:
Everything was working, got happily squirrel-sql and databases working again. Then started with my test environments in VirtualBox, 2of 3 also working well. Then I started laptop this morning, got another update message and started update-station. It found about these 360 (?) packages for GhostBSD 26.1 (not in VirtualBox, the "real" system), update process went trough, got that little window to restart system and it went till the login screen and then stuck. while booting, I could catch some of the errors (mentioned above), before system got stuck (no switch to terminal possible as well) then I got the white field to put in password, but no keyboard or mouse reacting!
So always have to switch back to boot environment backup 3 to get normal booting and login, but here now stuck with a complete fresh installation and all configuration and no booting into desktop possible. How can I get back to a normal boot process without loosing all fixed configurations or need to re-install again?
Everything was working until I clicked on that update button.

vimanuelt

Try this:

Boot into the working BE (the p5 environment)

Create a NEW safe clone before testing:

sudo bectl create safe-working-backup

Update only from terminal, not Update Station:

sudo pkg update -f
sudo pkg upgrade -fy

hank2121

vimanuelt ok, I ll give it a try tonight and let You know.
Thx for the info!

Robin

I'm curious, @vimanuelt , why you advised using the terminal instead of the Update Station. I assume it's the -f and the -fy components? I reckon they're not part of the regular update script that Update Station uses, correct?

vimanuelt

Robin

pkg update -y : Yes
pkg upgrade -fy : No

hank2121

ok, tried as You wrote @vimanuelt , but same result: after almost 1300 packages de-/re-installed and upgraded, it ends at login screen with no keyboard and no mouse (or should I say frozen mouse cursor). So again no navigation whatsoever. Will have to live with the p5-version then until - hopefully - the next major update will bring back full functionality on my Toshiba.

vimanuelt

Yes, it seems likely that there is an issue caused by changing your shell. If you changed to bash, it may be causing issues. Revert your shell setting and attempt to upgrade.

hank2121

vimanuelt so, You mean, going back to zsh may solve that issue?
can try tonight, when back from work...

hank2121

OK, this "lightDM, gkr-pam - unable to locate daemon control file" shows up again and this "zsh:compinit: insecure directories, run comaudit for list. Ignore insecure directories and continue (Y) or abort compinit (n) ncompinit initialization aborted", after I tried another command shell upgrade tog. with shell setting on zsh! seems to be another problem, why there s no mouse and keyboard available at login screen.
So will wait till next major update, that hopefully fixes this, as no kb and mouse, I cant search in any logfiles of this recent version p8!?
but had a look into "messages" under p5, which also includes the last upgrade messages from p8-version, where it says:
"hank-ghostbsd dbus-daemon [2976) (< package number ?, comment from me): Unable to set up transient service directory: XDG_RUNTIME_DIR '/var/run/user/164' not available: No such file or directory"
This message is repeated several times during re-installation/upgrade list.
The only real error, I could find.

vimanuelt

Try using fish instead.

hank2121

vimanuelt tried now. same result, no mouse, no keyboard on login screen, so no login possible.
will wait for the next major upgrade then and try again.
something goes wrong with my login when version p8 is active!?
and again this error about "lightDM, gkr-pam - unable to locate daemon control file"

vimanuelt

hank2121
I suggest reinstalling if your changes have materially affected the system state. Waiting for a future release is unlikely to resolve the issue, particularly as the behavior has not been reproduced in testing by others using the current code base.

hank2121

vimanuelt I was afraid, You d suggest that. sigh...
OK, maybe tomorrow on our holiday I ll try again and keep the add. configuration delayed until all is goin as expected...
thx my friend.