Hello Manfred, Am Sonntag, 25. Juni 2023, 20:02:46 CEST schrieb Manfred Neubauer:
please excuse me. It lasts some time to overcome my internal resistence to send an email to Comunity. First of all during installation I got on screen an information: 'violation of signature'. I installed opensuse.15.5 dispite a warning.
you can check the md5 sum of the installation media to verify media is correct. Does that match?
With version 15.3 everything was perfect. I could create a virtuell space.
What is a 'virtuell space'? I never came around this so far, so I doubt that this is an openSUSE feature (but I'm happy to learn if it is different)
Pushing buttons 'escape and start' I started an other Linux from an USB-stick. The more I tried to realise to start my USB stick, the more I drifted into a disaster.
So what did you really do? - start openSUSE USB-stick? - start any other Linux-based distri from an USB stick?
In the meantime announsments poppt up: 'security Violation'. Booting an other version of Suse, I succided to install 'Tumpleweed'.
Tum*b*lewee is an openSUSE product, not SUSE (os Suse). So back to start, you booted your laptop with an USB stick containing a Tumbleweed installation image?
I was still in hope to start from zero my USB-stick. Never the less in Leap15.5 there was something configured with 'ssh'. The part'settings' -----> Remote log in' was the reason why everyting went wrong.
I doubt that..... In the installation summary of a standard Leap 15.5 you find that - ssh service is enabled - ssh port is open If you are scared, close them. 'Problem' solved
there was an encrypted connection all the time open to SuseLinux.
Please explain what SuseLinux should be
But I got no information to resolve encryotion. Tumpleweed was installed anew downloading 500 packages from 1200, after 500 packages all the screen became red.
Its the nature of a rolling release that it has a lot of new software arriving each day. Thats normal. If you feel that the download broke your system, boot into the last known good snapshot and activate it. Problem solved. Next thing could be to analyze the potential issue, collect hardware and log information and create a proper, structured bug report
I could not overcome the ssh encryption.
And thats a good thing. ssh w/o encryption would be an open connection. You dont really want that.....
Finally I have send my ZenBook to Asus to repair it. Thats the whole story. Its clear that a ' KI ' was responsable for the situation.
I doubt that.
kindly Dr. Neubauer
Except spreading conspiracy theories a more structured appraoch to problem solving would be the way to go. Maybe you had a hardware problem with your Zen book, but I doubt it was related to Tumbleweed. Cheers Axel -- Dr. Axel Braun <docb@opensuse.org> Member of the openSUSE Community