I joined a post concerning Leap 15.5 freezing but now I cannot even log in. To be able to start and log in I rebooted to an earlier snapshot. This is the and I doubt I did the right thing but I am attaching my boot log using
journalctl -r -b -1
``` and hope this will give somebody a clue as to what is going wrong. BTW I have dual boot so booted to Windows 10 and all seemed to be OK so at present I am hoping my hardware is OK.
https://susepaste.org/293ece675a70
https://paste.opensuse.org/293ece675a70
Not getting any help on this but I have checked my login screen which would not accept my login pw and noticed that three options are available two of which are X11 and Wayland.
Now I have always used X11 because Wayland had not been available to me. Now, without any notification on my system I found that if I switched to Wayland my problem has gone.
No idea if my other problems have gone and logging into this forum takes several attempts but at least this now seems OK.
For anybody who also has the problem, I am trying to run Leap 15.5 with a KDM desktop and the openSUSE Global theme.
I have found that I must select the Wayland Desktop Environment from the login screen before I can log in on every occasion even though the system appears to default to Wayland. I have never before selected Wayland or even been aware that it worked on openSUSE.
I can no longer use either Firefox, my usual browser nor Thunderbird, my normal email client. Both crash within a few second of trying to use them.
I have installed and am now using Brave to write this but I have had serious problems using my PW manager KeepassXC and logging into this forum .
Here is what I had from inxi:-
alastair@HP-Z640-1:~> sudo inxi -U
[sudo] password for root:
Starting inxi self updater.
Using tiny as downloader.
Currently running inxi version number: 3.3.29
Current version patch number: 00
Current version release date: 2023-08-15
Updating inxi in /usr/bin using main branch as download source...
Validating downloaded data...
Successfully updated to main branch version: 3.3.29
New main branch version patch number: 00
New main branch version release date: 2023-08-15
To run the new version, just start inxi again.
----------------------------------------
Starting download of man page file now.
Updating inxi.1 in /usr/share/man/man1
using main branch branch as download source
Downloading man page file...
Download successful. Validating downloaded man file data...
Contents validated. Writing to man location...
Writing successful. Compressing file...
Download, install, and compression of man page successful.
Check to make sure it works: man inxi
alastair@HP-Z640-1:~>
I tried to start over but the update has not been accepted. May need to restart later.
If there is an IceWM session selection available on your login screen, can you successfully login using it, and if so, do TB and FF work there? If there is no such option, install icewm.
# rpm -qi icewm | grep Size
Size : 986182
#
To diagnose anything to do with Xorg failing, running inxi in Wayland is of little use. The starting point should be uploading /var/log/Xorg.0.log e.g. with susepaste -e 40320 (to give it a month before expiring) from attempting to run Plasma and/or IceWM in X11.
Last time I tried icewm and X11 neither worked. I have no knowledge of Wayland and last time I read anything about it I recall it was not yet available on Leap 15.4 which is what I had been using until last week. I shall try again with the options you have suggested but this is working from Wayland with Brave as browser as the only way I could work on this machine other than booting to Windows 10.
I enclose the log file just in case it may be relevant but you say not:-
Hi,
No change here. I can only work if using Plasma (Wayland) and Brave and even with this working configuration TB crashes almost immediately. If I do select X11 or icewm I cannot log in or run any commands.
With help I might be able to work in console mode if you can remind me what I should put on the boot command line if I re-boot.
To stop X from automatically giving you a login screen or automatic login, leaving only 6 or so framebuffer login screens available, simply append 3 to the linu line’s ending whitespace.
Was the last time on this PC on this installation? If not, it’s not a reason not to try now. It’s just common troubleshooting to try and isolate fault.
Plasma via SDDM on 15.5 is working OK here on my newest NVidia, but it’s older than yours generationally (fermi), and running on the modesetting DIX display driver, not the nouveau DDX.
Hi mrmazda, Sorry I do not understand "append 3 to the linu(x?) line’s ending white space. Do you mean on the grub startup screen? Can you explain?
My efforts to use X11 and icewm are all on this machine on this installation.
I just tried setting up another user. I could set up a new user and log in as that user but I need to think about how to proceed as my PWs are on pCloud so I have to set up KeePassXC on this user account to get my PWs. Meanwhile and while logged in as the new user, the machine crashed and I had to to a Ctrl + SysReq +b and start over.
I have started again on my own account with Plasma Wayaland and Firefox and so far have been able to write this.
Please could you suggest how I can get to the init 3 console where hopefully I can run commands as you tell me.
1-press power button while computer is in powered off (shutdown) mode
2-when Grub menu appears, press E key
3-when edit screen appears, navigate using cursor and/or home and/or end keys to put cursor after some blank space after “mitigations=auto” at end of line that begins with letters l i n u. This line is probably wrapped, so not same physical line, but same logical line.
4-add whitespace after “mitigations=auto” using spacebar if none is there already
5-strike the 3 key
6-proceed with trying to boot Leap as instructed at bottom of grub edit screen
Ok now I understand and assume this will take me to the console where I can log in as if it rescue mode.
Which file/setting/log command do I start with, and more importantly once in the cli mode how do I communicate to inform you of the results. Do I try and work entirely on the problem machine or should I have my laptop running nearby so I can communicate in part on the forum?
OK, I appreciate this has taken too much time and I cannot work out why my system has been corrupted so I have decided to perform an upgrade to Tumbleweed.
I assumed the DVD install was the safest option so downloaded and ran the upgrade having checked the media.
Apart from some difficult questions with some python files all seemed good but I quickly ran into significant problems with the checks. I will try and send the pictures of the error messages I have taken but T’Bird is not working at present so they are still in my phone.
A typical error is with checksum of my file /var/adm/mount/AP_0xjBYrEb/x86_64/xorg-x11-libX11-ccache-7.6-22.6.x86_64.rpm.
Does this mean I have corrupted data on my drive or is it from my TW download?
Never seem this error before and even after many retries I still get the failure.
I shall try and boot to USB for Network upgrade but meanwhile am posting in case this is all aprt of my original problem with X11.
That rpm belongs to TW, not leap. You could try a direct download from http://download.opensuse.org/tumbleweed/repo/oss/x86_64/ using wget, then attemp to install/upgrade using rpm -[i,U]vh as root. /var/adm/mount/AP_0xjBYrEb/ is a temporary location, so there could be a file or filesystem corruption involved. ISTR that rpm has been turning up as unneeded when I run zypper pa --unneeded, so have been removing it in my recent TW upgrade sessions.
# zypper info xorg-x11-libX11-ccache | grep -A2 script
Description :
:::::::::Cache for X.Org compose files
:
#
Instead of trying to solve the xorg-x11-libX11-ccache problem, try removing it.
IIRC, Leap to TW upgrades are not “supported”, meaning there is no official QA on such process.
Hi mrmazda & Malcolm,
After further thought last night and before I saw your comments above I checked on my system and worked out that these errors were coming from the version of TW which I had downloaded so I used the Network version and installed from that. No errors encountered although several retries were needed during the process but the upgrade itself was effortless and this morning it appears my system is stable and almost back to “normal.”
I have only one issue now concerning Thunderbird and shall post a new thread.