Update to Openindiana 2022.10

[berni51]

There is a new Hipster version 2022.10 available on openindiana.org. As I have a fine running system, I would like to ask if an update to 2022.10 is possible instead of a new installation.
Any experience?

Regards
Berni

[bsd-keith]

As per their website - https://www.openindiana.org/2021/12/...21-10-is-here/

The new images are interesting for people with newer hardware that hasn’t been supported in the past. There is no necessity to re-install from newer images as OpenIndiana Hipster is a rolling release and will bring all updates with a simple call of “pfexec pkg update -v”.

[berni51]

Grande catastrophe! I run the pkg update and everything looked fine, no error messages, perfect.
But when I rebooted the system, the DM (lightdm) no longer started and I ended up at the command line. Calling startx also did not work. And one of my pools (I called it opt) was corrupted.
I could start an older image, where lightdm and Xorg works, but the opt zpool stays corrupted.
This is the dmesg output of the updated system:

Jan 28 17:27:11 lian console-kit-daemon[435]: [ID 702911 daemon.warning] WARNING: signal "open_session_request" (from "OpenSessionRequest") exported but not found in object class "CkSeat"
Jan 28 17:27:11 lian console-kit-daemon[435]: [ID 702911 daemon.warning] WARNING: signal "close_session_request" (from "CloseSessionRequest") exported but not found in object class "CkSeat"
Jan 28 17:27:12 lian mac: [ID 435574 kern.info] NOTICE: rge0 link up, 1000 Mbps, full duplex
Jan 28 17:27:14 lian inetd[722]: [ID 702911 daemon.warning] Configuration file /etc/inet/inetd.conf has been modified since inetconv was last run. "inetconv -i /etc/inet/inetd.conf" must be run to apply any changes to the SMF
Jan 28 17:27:14 lian in.routed[873]: [ID 749644 daemon.notice] rge0 has a bad address 0.0.0.0
Jan 28 17:27:20 lian nvidia_modeset: [ID 107833 kern.notice] Unloading
Jan 28 17:27:26 lian ipf: [ID 774698 kern.info] IP Filter: v4.1.9, running.
Jan 28 17:27:26 lian svc.startd[9]: [ID 652011 daemon.warning] svc:/application/graphical-login/lightdm:default: Method "/lib/svc/method/svc-lightdm stop" failed with exit status 1.
Jan 28 17:27:26 lian last message repeated 2 times
Jan 28 17:27:26 lian svc.startd[9]: [ID 748625 daemon.error] application/graphical-login/lightdm:default failed: transitioned to maintenance (see 'svcs -xv' for details)
Jan 28 17:27:26 lian fmd: [ID 377184 daemon.error] SUNW-MSG-ID: SMF-8000-YX, TYPE: defect, VER: 1, SEVERITY: major
Jan 28 17:27:26 lian EVENT-TIME: Sat Jan 28 17:27:26 CET 2023
Jan 28 17:27:26 lian PLATFORM: System-Product-Name, CSN: System-Serial-Number, HOSTNAME: lian
Jan 28 17:27:26 lian SOURCE: software-diagnosis, REV: 0.1
Jan 28 17:27:26 lian EVENT-ID: db4eade6-acc5-4676-ade1-d451ee965e8a
Jan 28 17:27:26 lian DESC: A service failed - a method is failing in a retryable manner but too often.
Jan 28 17:27:26 lian   Refer to http://illumos.org/msg/SMF-8000-YX for more information.
Jan 28 17:27:26 lian AUTO-RESPONSE: The service has been placed into the maintenance state.
Jan 28 17:27:26 lian IMPACT: svc:/application/graphical-login/lightdm:default is unavailable.
Jan 28 17:27:26 lian REC-ACTION: Run 'svcs -xv svc:/application/graphical-login/lightdm:default' to determine the generic reason why the service failed, the location of any logfiles, and a list of other services impacted.
Jan 28 17:27:46 lian pseudo: [ID 129642 kern.info] pseudo-device: devinfo0
Jan 28 17:27:46 lian genunix: [ID 936769 kern.info] devinfo0 is /pseudo/devinfo@0
Jan 28 17:27:46 lian usba: [ID 912658 kern.info] USB 1.10 interface (usbif461,4e04.config1.1) operating at low speed (USB 1.x) on USB 2.10 external hub: input@1, hid18 at bus address 3
Jan 28 17:27:46 lian usba: [ID 349649 kern.info] NOVATEK USB NETVISTA FULL WIDTH KEYBOARD
Jan 28 17:27:46 lian genunix: [ID 936769 kern.info] hid18 is /pci@0,0/pci1043,8527@10,1/hub@4/device@1/input@1

Any ideas?

Berni

[nipos]

In your dmesg log I don't see the reason why LightDM or Xorg doesn't work,only that it failed.
Can you please also share your Xorg.0.log?
My first guess: The version of the default Nvidia graphics driver was changed a months ago,so if you're using a Nvidia graphics card,your model is probably not supported by the installed driver anymore and you need to switch to a older Nvidia driver (which is still available in the repo).
But let's see what the Xorg log says before speculating too much...

[berni51]

Thx for your reply. I don't have access to the OI pc currently, so I can show the Xorg.0.log tomorrow. What I just have is a part of a svc log file:

[ Jan. 28 17:27:26 Executing stop method ("/lib/svc/method/svc-lightdm stop"). ]
kill: 888: no such process
[ Jan. 28 17:27:26 Method "stop" exited with status 1. ]
[ Jan. 28 17:59:21 Enabled. ]
[ Jan. 28 17:59:26 Executing start method ("/lib/svc/method/svc-lightdm start"). ]

** (lightdm:818): WARNING **: 17:59:26.818: Failed to get list of logind seats: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.login1 was not provided by any .service files[ Jan. 28 17:59:26 Method "start" exited with status 0. ]


** (lightdm:818): WARNING **: 17:59:26.838: Error getting user list from org.freedesktop.Accounts: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Accounts was not provided by any .service files
X Error of failed request:  BadRROutput (invalid Output parameter)
  Major opcode of failed request:  140 (RANDR)
  Minor opcode of failed request:  9 (RRGetOutputInfo)
  Serial number of failed request:  15
  Current serial number in output stream:  15
[ Jan. 28 17:59:33 Stopping because all processes in service exited. ]
[ Jan. 28 17:59:33 Executing stop method ("/lib/svc/method/svc-lightdm stop"). ]
kill: 818: no such process
[ Jan. 28 17:59:33 Method "stop" exited with status 1. ]
[ Jan. 28 17:59:33 Executing stop method ("/lib/svc/method/svc-lightdm stop"). ]
kill: 818: no such process
[ Jan. 28 17:59:33 Method "stop" exited with status 1. ]
[ Jan. 28 17:59:33 Executing stop method ("/lib/svc/method/svc-lightdm stop"). ]
kill: 818: no such process
[ Jan. 28 17:59:33 Method "stop" exited with status 1. ]

As a workaround I have disabled lightdm and installed and enabled xdm, which works perfect. So the Nvidia driver may not be the reason for my problem. May it be a communication issue between dbus and lightdm?

Berni

[nipos]

Problems with Lightdm are not that common,but yes,that's also possible.
In that case the contents of /var/log/lightdm/lightdm.log may help to debug that.
The log you posted doesn't show any issue with starting Lightdm,it does only complain that it doesn't run when it tries to stop it.
The DBUS warnings can be safely ignored,they appear on my machine,too,and they're only warnings,not errors.

[berni51]

Today I could work on my OI machine again. I disabled xdm and enabled lightdm.As before the lightdm did not start, but now I had fresh logfiles. A Xorg.0.log does not exists, OK, because it was not started,
Now I followed @nipos hints to read the lightdm.org. And now the scales felt from my eyes:

[+0.01s] DEBUG: Adding default seat
[+0.01s] DEBUG: Seat seat0: Loading properties from config section Seat:*
[+0.01s] DEBUG: Seat seat0: Loading properties from config section Seat:
[+0.01s] DEBUG: Seat seat0: Starting
[+0.01s] DEBUG: Seat seat0: Creating greeter session
[+0.01s] DEBUG: Seat seat0: Failed to find session configuration lightdm-gtk-greeter
[+0.01s] DEBUG: Seat seat0: Failed to create greeter session

Failed to create greeter session!!! I figured out that the gtk-greeter was no longer installed.
So something crazy must have happened during my update, because I never ever have uninstalled the greeter.

OK, installing gtk-greeter was no problem, I disabled and enabled the lightdm once more - and the screen becomes black. Nothing more happensm but the machine was still alive and I could login via ssh to reboot.
And now everything was OK! The machine booted, the lightdm with all my old settings came up and started Xorg properly.



I did not unstand what has happened with my OI update, but thanks to your kind help everthing is OK now.

Berni, happy.

[nipos]

Being a rolling-release distribution unfortunately also means that things can break sometimes during upgrades.
We always try to avoid that,but not every computer behaves exactly the same way,so bugs may not appear during testing.
Nice to hear that it could be fixed for you that easily

[berni51]

Yes Nikla, off course thats right. But I am very glad to have such a nice alternative OS like OI and errors and bugs are accepted.
However it's crazy that the same thing happened today on a second machine. OK, the hardware was nearly identically (older Asus F2A85 board mit amdgpu, A10 processor, 32 GB of RAM and SATA and Nvme ssds. Today I could fix it very fast.

Thanks again for your kind assistance.

Berni