Solved.
sysupgrade -s
(after reboot, gnome loaded)
bash-5.0# uname -r
6.9
On Sat, 6 Mar 2021 at 22:53, Sivan ! <[email protected]> wrote:
>
> /use/x11/ports/gnome make install didn't work. Images attached.
>
> On Sat, Mar 6, 2021, 22:12 Sivan ! <[email protected]> wrote:
>>
>>
>> dear Ed,
>>
>> It wasn't complicated at all in till the unintended upgrade, and I wish to
>> try and resolve this, even though I a person with copy&paste skills in
>> command line. OpenBSD 6.8 was booting fine with gnome, but now stuck in
>> xterm.
>>
>> Now in xsession cd/use/pets/gnome, typed make, it is making, will report
>> what happens.
>>
>> Thank you.
>>
>>
>> On Fri, 5 Mar 2021 at 23:23, Ed Gray <[email protected]> wrote:
>> >
>> > Hi Sivan,
>> >
>> > Sorry I've not had chance to look at everything you sent.
>> >
>> > Firstly the message about SSH keys sounds normal as this is part of a
>> > normal X session startup. I suspect you have a key that has changed or
>> > needs a passphrase entered and it's just picking it up when you try to
>> > start X.
>> >
>> > The command history looks strange, you're running shutdown and reboot and
>> > then other commands, unless these are from another session?
>> >
>> > Openbsd needs the -h option to both shutdown and power off the machine or
>> > -r for reboot.
>> >
>> > Where is your startx program and is it a custom program?
>> >
>> > If you have done unintended upgrades and your /usr is also full it's going
>> > to cause all sorts of problems. I would recommend reinstalling a release
>> > from scratch if you can.
>> >
>> > Alternatively when the boot program runs you can choose bad.rd to get the
>> > installer ramdisk and manually repair from there but it's a rather complex
>> > process.
>> >
>> > On my system I had to boot bad.rd, type s for shell, run the MAKEDEV
>> > script in /dev to create device nodes and then run disklabel manually to
>> > rearrange volumes to make space.
>> >
>> > You would also need to grow or shrink the volumes.
>> >
>> > Regarding further troubleshooting of X sessions I would recommend moving
>> > .xsession to .xsession.bak and starting with a fresh configuration.
>> >
>> > I would need to understand more about how you are starting gnome like more
>> > details of any changes you made to the standard installation.
>>
>> I see gnome-sessiin-bi.core.core under /
>> and .xauthority under /root, as in the attached image
>> > Regards
>> > Ed Gray
>> >
>> > On Fri, 5 Mar 2021, 12:03 am Sivan !, <[email protected]> wrote:
>> >>
>> >> Dear Stuart Henderson.
>> >>
>> >> I ran sysmerge.
>> >>
>> >> I posted, earlier in this thread, 11 images in response to Ed Gray's
>> >> comment that I had not shared sufficient details. In addition there
>> >> are four more images attached here that I think are important.
>> >>
>> >> One of these four images show the output of sysmerge and startx commands.
>> >> Another is a screenshot of a strange prompt that appears before boot,
>> >> it asks for the ssh password - not an encryption password, which
>> >> might be understandable, if I had an encrypted disk, I haven't
>> >> encrypted -- so why does it ask for the ssh password, before asking
>> >> for a login password in X Term?
>> >> Two more pictures show the reboot sequence that is some sort of a loop
>> >> when shutdown now command is issued as user or root, from x Term, then
>> >> the main screen command line is seen flashing the status, and
>> >> invariably reboots the system in X Term. This happened in gnome (or
>> >> gde) before the accidental upgrade to 6.9 beta and happens in x Term
>> >> in 6.9 beta.
>> >>
>> >> Thank you.
>> >>
>> >> On Thu, 4 Mar 2021 at 14:10, Stuart Henderson <[email protected]>
>> >> wrote:
>> >> >
>> >> > On 2021-03-03, Sivan ! <[email protected]> wrote:
>> >> > > After sysupgrade -s, during which there were two or more automatic
>> >> > > reboots, freebsd, upgraded to 6.9 booted after asking password for
>> >> > > ssh key,
>> >> > > and started with xvterm console. Startx attempted to switch to gui,
>> >> > > but
>> >> > > returned errors.
>> >> > >
>> >> > > Please advise.
>> >> > >
>> >> > > Thank you
>> >> > >
>> >> >
>> >> > Make sure you have run sysmerge.
>> >> >
>> >> > If that doesn't help then we need more than just "returned errors" -
>> >> > *what* errors?
>> >> >
