Did a hard reset. Upon reboot logged in via GUI and went to system update. 11 files were installed and I hit enter to exit Konsole. After a few screen flickers I got the GUI login screen back and logged in. Now I’m back to the black screen with the flashing white underscore in the top left.
By simply tapping the power button once, the system shut down. So I started it up again. It took some time but the GUI login screen came up and I logged in. Again, it took some time watching the black screen until the desktop appeared. After waiting about a minute the desktop disappeared and the login GUI came up for a few seconds until the same black screen with the flashing underscore in the top left. I’m beginning to feel like Bill Murray in Groundhog Day!
I just noticed something strange. When running the Live USB 3 icons appear on the desktop: Install OpenMandriva
Welcome
Info and Resources
Normally after installation is complete only the last two icons appear on the desktop when booted up. But, my installation still shows the Install OpenMandriva icon before the screen reverts to the black one again. Surely that icon should not be there. What might this be indicating? Should I try to reinstall OM over again?
The current issue sounds like a graphic issue. A question:
So that looks like you had a 25.06 system that worked for several days. And I am not exactly getting why there is so much trouble now. OK, that could be me not being smart enough for this issue. A suggestion would be to go to OpenMandriva Chat and talk to people there and we can hope get some more or different knowledge involved. I think this may not be that difficult and I am not seeing some key point. But I have not given up.
What is gfx1150? Are Radeon 890M and gfx1150 two different graphic cards or card/chip? If it is dual graphics that could be a possible problem.
A guess: Have you tried Wayland instead of X11? You can install it with sudo dnf in task-plasma6-wayland --refresh. Logout and in lower left of sddm login screen for Desktop session switch to Plasma(Wayland). Possibly that would work better.
Don’t know. We will look in to that. I can’t test this until tomorrow at the earliest. But yes the Installer icon should not appear on the installed system.
Don’t know. I would want to see if we can identify a cause of the problem/s if possible. Am thinking the guys on OpenMandriva Chat would be a help.
I did start a new build for ROME Wayland znver1 #4306.
Thank you.
Yes, I had the earlier build of Rome running very well for the best part of a week. But I think I had settings that would auto download updates. Can’t remember if it was also set to auto install or if I just carelessly started an install without looking carefully at the list of updates. Anyway, that’s when the problems began. I haven’t been able to get a stable installation since then.
The Radeon 890M is the on board graphics module. I believe the GFX1150 is a reference to the GPU in that module.
I suppose I can try the Wayland version. Can’t hurt.
Just checked the login screen. The only things that appear in the bottom left are Virtual Keyboard and Desktop Session which gives me the choice between Plasma (X11) and Failsafe X session. Don’t see any reference to Wayland.
Already posted that. Whether Wayland works better or not would be unknown until you install it and try it.
Edit: For problem solving we either need a way to reproduce the problem on out hardware or VM’s or we need some logs. In other words we need to find out exactly what is not working.
The basic system log is the journal invoked with the command journalctl. That will output many lines of information usually to much. To get the logs for users current boot use journalect -b for previous boots you first can run journalctl --list-boots. The next previous boot would be journalctl -b -1 and so on.
So we need the logs for a boot that did not boot properly if the current boot did not boot properly that will work. Put all the output, including the command used, in a text file and post that here. Here is one way to do this:
For current boot:
journalctl -b > journalctl.txt
For the immediately preceding boot:
journalctl -b -1 > journalctl.txt
That creates the file journalctl.txt you can post here. There are usually a lot of line of output.
Something to try:
Boot in to console mode:
Run:
sudo systemctl disable sddm
Reboot then at the command prompt login and run:
startx
or:
startplasma-x11
or for Wayland:
startplasma-wayland
The purpose is to see if you get a graphical desktop without using sddm. This would tell us if the is/is not a cause. If the problem is not sddm then graphic hardware of software become a possible suspect.
Another thing users with this kind of problem can do is to install icewm. This is a very simple graphical desktop. If you can boot into icewm and not Plasma desktop this tells us the problem is likely in KDE Plasma software.
The command line command to start icewm is:
starticewm
On any system I plan to keep for any period of time I install icewm as a graphical desktop backup. I do a lot of testing and testers tend to run in to a lot more problems, that is why we are testing.
Thank you. I followed your instructions and it seems that I am now using a stable, functional desktop for about 10 minutes now! I’m still anticipating trouble but none so far. One curious thing is that the Install OpenMandriva LX icon is still on the desktop, although it fails to perform its intended function.
I am still quite new to Linux, I have used Linux Mint for about a year. But right now, I see myself as a passenger on a plane whose pilot has passed out and I need air traffic controllers (like you) to help me land the plane.
I am unfamiliar with the inner workings of the operating system but, I am pretty good at following clear instructions. Do you want me to follow the instructions you posted and provide you with the logs that are revealed?
Was this a result of fixing your existing system? Installed from iso #4292? Knowing this might help us help other users.
Part of this is me understanding exactly, exactly, what users have actually done. Needless to say that tends to be more difficult with inexperienced users. But it is still necessary for good problem solving.
Sorry, yes. I did a fresh install of build 4292 and encountered all of the same difficulties. When I followed your instructions to switch to Wayland I had previously chosen the Desktop Session login using Failsafe X session. So when I logged in to carry out your instructions I found myself in CLI mode in a white rectangular box in the upper left of the screen. When I had just executed the last of your instructions and was about to reboot the screen blacked out again. I had to do a hard reset and whent the login GUI came up the choice to use Wayland was there and I chose it. I logged in and the system seems to be stable. In fact, I am communicating this message to the forum using helium browser from that desktop.
1 Like
Sorry, I should also point out that I have not performed the pcie_aspm=off modification to grub. I checked /etc/default/grub and the modifications are not there. And so far I am experiencing none of the crashing that had been occuring before.
1 Like
I have now configured a network printer and performed a reboot. So far everything is working fine.
2 Likes
I wanted to post the workaround here that was discussed on the chat. If anyone else experiences the same issue they can either switch to Wayland as discussed above or use the below workaround. Thank you everyone for your support!
I ran ‘systemctl disable sddm’ and then rebooted. Login via command line and ran startx.
1 Like
I have been running the 4292 build of Rome using the Wayland platform for several days now and I have not experienced any of the crashing problems previously mentioned. However, there are some minor annoyances I’m finding. Wayland doesn’t seem to play nice with some of the applications I depend upon. So, I would like to attempt the workaround you’re referring to and hopefully be using the X11 platform successfully. I haven’t been in the chat for a few days and I’m having trouble finding the references to your workaround (my Matrix client doesn’t seem to like Wayland or vice versa). From what I can tell here, I should switch back to X11, login, open a terminal window and run ‘sudo systemctl disable sddm’ and reboot. When I login after reboot I should find myself in CLI mode and I’m to run the command ‘sudo startx’. Is this correct or am I missing anything?
Not sudo startx. Just startx.
1 Like
Thank you. I’ll give it a try.
I got exaсtly the same issue after updating to latest ROME version;
to be precise after running
sudo dnf clean all ; sudo dnf distro-sync --refresh --allowerasing
and reboot.
Problem
After boot and login to desktop, system works for 1-2 minutes then desktop crashes and login manager prompt appear.
In console mode works ok.
Tried to install and use lxqt - did not help, same issue.
What helped
sudo dnf in task-plasma6-wayland then login to plasma(wayland) after reboot.
Typing this post from wayland session, did not crashed yet after couple of minutes, seems working
@ben79 I can try boot without wayland and provide logs of crash. Which logs would you like to see, and where to post them, would be ok in this topic?
I’ve seen this from time to time. In my case, it’s an issue with kwallet not getting opened.
My fix:
If this happens, when the desktop finally shows up, quickly log out and then back in. The second time, the desktop appears normally.
This thread has to many different things mentioned. What exact system is in use today, the exact problem today, what did user do before the problem occurred? I do not mean to be rude but I have time problems, not enough of it.
If I understand correctly this problem happened after user upgraded an existing working ROME X11 X86_64 system? And user has since reinstalled and still has the issue? I saw iso #4119 mentioned. The most recent ROME Plasma6 X11 x86_64 is #4305.
In other words we need to simply to where we are right now not days ago.
Some general info about the ROME upgrade Nov.9 is here. This is basically the upgrade from plasma6-sddm* to sddm* after which you have to re-enable systemd sddm service like this:
systemctl enable sddm
To be sure it is enabled:
systemctl status sddm
reboot
If you have the correct packages installed and sddm is working and there is some problem I may not be the best person to help, if so we can get other people involved. But we would need logs to do anything. I believe I described the journal logs needed here. I do not see any journal log posted, did I miss it? It needs to be a log from a boot failure on the problem system. If other logs are needed we will advise.
There are a number of other possible problems but without logs we can only speculate.