https://bugs.kde.org/show_bug.cgi?id=490601

Reg <r...@regproctor.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |r...@regproctor.com

--- Comment #2 from Reg <r...@regproctor.com> ---
(In reply to Zamundaaa from comment #1)
> Sounds like a regression in the radeon driver. Does the issue also happen on
> an older kernel?

My system is opensuse tumbleweed-slowroll, recently changed from from
tumbleweed. These rolling distros. don't give a lot in the way of options but I
did take note of versions in grub I am currently booting to the kernel 6.9.9-1
and I just tried it on the only other option which is 6.8.7-1. Same result.

That said, I think it's something else because this weekend I had to reinstall
my OS from scratch as it had some btrfs error that it couldn't repair. I
noticed a couple of things.

With a completely fresh install I was able to boot into wayland again so that's
with it's latest kernel. However, I did a few things, I:
- added pacman for video
- booted into KDE X11
- added a few apps I needed.

After this I could no longer log into KDE/Wayland, and out of curiosity I tried
a few things:

- I removed pacman and did a vendor swap back to opensuse, still couldn't not
log in.
- I created a new user and tried to log in there, no change.

I find it hard to believe that little utilities I added caused this, things
like htop. I did add some major apps: zoom, signal, slack but I don't see how
these could affect it, yet alone a clean install. I kind of wonder if logging
into KDE/X11 threw some sort of a switch that made logging into KDE/wayland
fail.

Anyway, I am a developer, not in this area so you will still have to help me
along but it means I know enough where I could give you more information if you
think it will help, system logs or whatever you want.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to