Black screen bug with bazzite-nvidia:testing build for explicit sync
Ello, just as the title says, got a black screen showing up after booting into the new bazzite testing image, just putting this here for point of reference for people to view at a later time when people are online and wanting logs, didnt want the discussion to get buried in gen chat.
Can provide hardware specs and anything else when needed
712 Replies
@wolfyreload opened it here
I'd rename the title to bazzite-nvidia:testing just so it's specific
and for now I think the hardware specs would be good
KDE
CPU: AMD 5800x
GPU: Nvidia 4080
RAM: 32GB 3600mhz Corsair
Also black screen
DE: KDE
CPU: AMD 3600
GPU: Nvidia 3070
RAM: PATRIOT 3200MHZ
Working for me KDE version
KDE
HP Probook 450 Nvidia Optimus laptop (I did check that the games were running on the discrete GPU)
CPU: Intel Core i78550U
GPU: Nvidia Geforce 930MX
RAM: 32GB Kingston 2400MHZ
Working for me
HP Omen 15 Laptop
CPU: Intel Core i7-7700HQ
GPU: Nvidia Geforce 1060 GTX 6GB Mobile
RAM: 16GB
Out fo curiosity what's in this testing image? I guess 555?
Yup bazzite-nvidia testing image. Has Nvidia 555 drive in it and it's working for some and not for others. Hoping to find a pattern to help the Bazzite Maintainers figure out what is up with it
nice, you have the command to rebase anywhere? would love to give it a shot
just did rpm-ostree rebase ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-nvidia:testing let see
Yup. That looks right. Just make sure you know how to get into grub to switch back to your old deployment if anything goes wrong
might be worth pinning your current image to be on the safe side
great, lets reboot 🤞
yep, got a nice black screen haha
rolling back
Ahhh :(. Please post your hardware on here
KDE:
Processors: 12 × AMD Ryzen 5 5600X 6-Core Processor
Memory: 31.3 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 3080/PCIe/SSE2
Manufacturer: Gigabyte Technology Co., Ltd.
Product Name: X570 AORUS PRO
seems all black screens are series 30/40?
The working ones appear to be the Nvidia Optimus laptops so far
Everyone with AMD GPU and Nvidia... blank screen
Looks like integrated graphics is fine
Dedicated graphics seems to be the issue
yeah, looks like it. Would love to retry again
same, black screen here with dedicated graphics connected to the display
KDE
CPU: Intel Core i5-12400
GPU: NVIDIA RTX 4060 Ti
RAM 16 GB 3200 MHz
gonna test with my Optimus laptop to be sure
do add if you're KDE or GNOME
we had issues with GDM on Nvidia 555 prior
which is why we didn't push this sooner
and then also dmesgs would be helpful
edited my specs (kde, black screen, 3080)
how could we get those?
control+alt+f4
sudo dmesg | fpaste
added, running KDE
laptop worked fine, run some games and all are surely using the Nvidia. Big Picture now runs very smooth
HP Probook 440 G5
KDE
CPU: Intel Core i5-8250U
GPU: NVIDIA Geforce 930MX
RAM: 8 GB 2400 MHz
will rebase again on desktop to provide dmesgs
Sadly blackscreen for me and eventually just shut itself down.
KDE
12700k
3080ti
32gb ram
nothing stands out
might be an sddm issue?
do you need me to share anything to help or have I done everything required for a black screen test?
if more info needed anyway just ping. I am a bit of a novice always but I can give shiz a go
learnt how to post this as well using the tty from when the shiz occured
Pushed an update to add fbdev args to nvidia-drm, may help
Would it help if paste a working boot for comparison?
I also see reports about black screens in 6.9 under 555
Looking into that
I don't think so in this case, there's no errors in these logs
Driver is loading and working properly, issue is likely in KDE or a setting or some kind
What might help after that update is an SDDM log
How long does the push take to percolate? I can volunteer my 4090 as tribute in an hour-ish
As long as there's no build failures it will most certainly be ready to go by then
Ready to test whenever and try the other sddm log thing
fyi Kyle that build failed
Works fine for me
KDE
HP Pavilion Notebook
CPU: 8 × Intel® Core™ i5-8250U CPU @ 1.60GHz
GPU: GP107M [GeForce GTX 1050 Mobile]
RAM: 8 GiB
KDE
CPU: AMD Ryzen 7 5800X
GPU: NVIDIA GeForce RTX 3070 [Discrete]
Desktop, obviously.
Need to update mesa
lots of posts here now 😄 kyle do you need anything from myself other then my parts?
computer parts of course
Found some reports that GSP breaks KDE under kernel 6.9
building mesa 24.1.2 now, then I'll rebuild testing with that fix in place
I will also need GNOME tested, original reason for negativo's drivers not being used was GDM refusing to run on Wayland
and instead using X11
https://github.com/ublue-os/bazzite/actions/runs/9616950162 this pipeline here yeh
GitHub
Build Bazzite · ublue-os/bazzite@548a9cc
Bazzite is a custom image built upon Fedora Atomic Desktops that brings the best of Linux gaming to all of your devices - including your favorite handheld. - Build Bazzite · ublue-os/bazzite@548a9cc
https://copr.fedorainfracloud.org/coprs/kylegospo/bazzite-multilib/build/7647701/
when this is done (Takes about 30)
I will push a new testing build
cool cool
happy to test all aspects of it btw, gnome, kde, anything else that might have errors cropping up
btw what was the command to pin the current image?
ostree admin pin <deployment number you want to pin>
You might need to run with sudoYeah, it needs sudo.
GitHub
Merge branch 'main' into testing · ublue-os/bazzite@064db3b
Bazzite is a custom image built upon Fedora Atomic Desktops that brings the best of Linux gaming to all of your devices - including your favorite handheld. - Merge branch 'main' int...
🤞🏽 You think you know what was the issue with the black screen then?
yeah, might work noiw
all builds done
ooo
time for a rematch
will give it a go now
I think it needs a bit longer. Isos are buildinh
dang I jsut started. I think kytle just said they were done as well
Ah ofc don't need iso formats for this I guess?
I dnt think so
but I dnt know
Yeah this is new for me
iso is separate
you may ignore
The pipelines finished for the build itself, i think it doesn't need to wait for isos if rebasing
maybe soon I will get to feel waylands tender embrace working properly
aight brb will report soon
🫡
I can confirm it is black
Yes, it is still black
I should have also ostree pinned like last time
I clearly got confused how that worked cos my 2 died
@matt_schwartz if you've got any more info on KDE's problem here would appreciate it
But I can go back to 1
Would u like me to do anything in the tty or all good?
restart sddm and see what it's outputting
Sorry image quality is poor
Imma need to sit down and do a computer search instead or mobile discord search in a bit
systemctl restart sddmCheers
Is my system supposed to restart after this?
Lmao
Still black screen
Tty shows it did it as well
One weird thing it did do when I first did it is make the mouse bigger for a bit
Yeh that happens here
thats probably wayland applying the res instead of x11 I assume. My sddm did increase in size as well
Makes sense
Well I did the command twice and the second time crashed it
Will await the next test
Or next diagnostic step
On my side, new deployment seems working nicely
As the last thing I assume was meant to restart my pc and show something
the command simply restarts sddm, which is the login manager
Arr okay
Well now it makes sense what happened I guess to some extent
With that restarting
I guess it is new plasma failing ATM with my shiz
From reading what everyone was saying
I see there is more stuff building as well
but gonna leave till it is mentioned that it should be tried
I couldn't get into tty when I tried the first test build lol
prob the same for me tbh
I think first time no mouse
and the pc then shutdown
2nd time booted in there was a mouse
this timearound the first time had a mouse too
resetting the login manager simply duplciated my screen and did the mouse thing it does when testing resolution or whatever
Reddit
From the NixOS community on Reddit: Plasma 6 stuck on black screen ...
Explore this post and more from the NixOS community
Okay, I think I found a way to bypass sddm.
Testing with gnome now, everything seems to be working fine so far!
@Marko open tt3 and run this
I think I erased the image as I updated just now on stable. Would it help the guys with their test or understanding?
Oh then nvm
I do enjoy testing and appreciate it
Dont know if that would help though, this seems an upstream issue, is just a possible workaround
Is there if you want to try 555 so badly
I can wait for sure
waited this long
damn, I like kde but is gnome is better behaved...
Hmm, what I noticed is that in stable sddm would stay open in tty2 and open plasma in tty1. Now with plasma 6.1 that leftover seems gone
Ok I don't know what I did but KDE is now working too
I don't know if it's useful but just in case
I checked negativo and they do most of what my modprobe did, so I just pulled it
Simplifies things
We get KDE acting consistent and we should be good
:clueless:
kde needs some polish, but as for nvidia 555, pretty happy with it so far
if its not working its not an upstream kde issue
Is this a hybrid system or DGPU?
dgpu
And what kernel version?
6.9.5
also works on 6.8.12
Hmmm
So we're also 6.9
And as of the newest update I am not doing anything that negativo isn't
GNOME works, but SDDM seems to black screen
Very odd stuff
i do have autologin enabled but its not enabled by default and it was working before that too
I have to put a password in when I login
https://copr-dist-git.fedorainfracloud.org/cgit/gloriouseggroll/nobara-40/sddm.git/tree/sddm-0.20.0-fedora_config.patch?id=fd24c795543a5fb13b5ef6b551e050e13b076102 hmm we're also using wayland for sddm now looks like, maybe its cachyos that still uses x11 for that
Hold on if you're patching SDDM to be Wayland then what is upstream doing?
Ok this is weird. I got to sddm login screen, I input the password and it says "login failed"
is there value to me taking a crack at installing this with my 4090 \right now or is a new image being built/hypothesis being formed?
works for some, does not work for others
if you can find something others have missed it would be greatly appreciated
logs of any kind that show a problem
OK, wish me luck
Something wrong with sddm, I get login failed, I do ctrl alt f4 login and this shows up. Any idea how could I debug this?
not able to reproduce this in a VM
could be SDDM crashing
make sure you're fully up to date
Doing ujust update just in case
Ahh wait I know what's happening
I appear to have made it to the other end successfully
Is this on a laptop or a desktop?
I did rebase -> manual restart -> system comes up and boots normally, but eventually shows some red errors about a device being busy, then reboots (expected?) -> Reboot is successful -> KDE Login Screen, type password, log in no problems
Corsair desktop with 4090
interesting, maybe that last changed cleaned this up?
you should be the target for the earlier black screen bug
the only odd thing I see in
journalctl is this:
It's repeated over and over for a three or so PIDs, but it doesn't seem to make anything visibly sadI think is trying to login into x11 but there is no x11
what's in
/etc/sddm.confI have no sddm.conf there!
you should have one, it's a default file
odd
Ahhh got it, is empty
well, normally it's a ton of comments
but no values
empty is fine too
I looked under /etc/sddm /etc/sddm.conf.d but nothing looks off is either empty or default
my conf is a ton of commented out stuff
Sddm is definitely borked for me, I rebooted twice and now it's unresponsive, like can't type
So, should I try a rebase?
yay im in!
tried installing x11 in my VM
switching to it
and then uninstalling
no issue
I edited sddm.conf with:
[Autologin]
User=myuser
Session=plasma
but I think this is a me problem because I've always had issues with the user, for example, this setting on kde never sticks:
now its like this, if I change the setting page, it reverts to blank
Killed GWE?
relying entirely on negativo
I'm in on wayland, but now XIV launcher crashes.
give a log please
Trying to figure out how to get them now.
iirc xivlauncher is a flatpak
so just run it from a term
and give the whole output
maybe you need to give it wayland permissions?
Enabling that doesn't always mean that the application actually uses it, and application should work exactly the same under xwayland
Had to manually disable the x11 fallback.
And.... game didn't launch.
>;<
im seeing someone whos got in sucesfully with a 4090, was there a new re build?
Yeah a few
i can give it a try just before i head off and report back in 🙂
so far so good here, on a 3080. let me try a couple of games.
Getting there
One thing I noticed is that on one of my screens the cursor fells very choppy, like its going at 30fps
while the other screen looks fine
weird
was it any workarounds or a simple re base and it worked after a new build?
I removed our previous Nvidia modprobe files
Negativo ships their own and we can just rely on them now
ahhh okay nice 🙂
Ended up rolling back, it was acting up a good bit. I'll wait for it to hit stable.
Yeah, because the game runs under wine, which I doubt it has wayland support enabled, it's still experimental as far as I'm aware.
Instead it uses xwayland
Right, always best to leave the flatpak options alone
They are like that for a reason
The better option was to post the log so we can figure out why it was crashing
Agreed, though it is better to not expect a testing branch to work out of the box
Nope, but its making great progress there guys.
I'm going to ping the xivlauncher team for more info.
post a log
they log is empty, nothing to show, just fails to start the compability layer.
Make sure th wayland issues isn't some known bug I'm already overlooking.
Wayland in theory should not be the culprit there
As it only uses xwayland
Tbh gonna try that thing, maybe it works for me, so far, I had 0 issue with 555
Yeah, give xivluancher a try. See if it works. I'm torn. Part of me really wants to get it working on Wayland cause I like the smoothness. But with how rough testing is expect I don't want the headaches.
How long do we think it will be testing?
Okay so ive rebased back to stable, do i just run
to run this latest build that people have been finding some success with?
yep
or if you were already on it, just
ujust updateor do i need to do some pruning of the old testing image at all?
nope
okay cool
As in making it to stable? I think i remember Kyle mention 555 wouldnt hit stable, rather 560(?)
about the XIVLauncher I don't think it's a issue with Wayland. I've being playing with 1/2 v-sync for a while on Wayland to avoid the flickering, and now using 555 with 1/1 v-sync is working great with VRR kicking in
555 won't hit stable on rpmfusion, but this change is switching to negativo as the source for the driver where 555 is in their stable release
point of this testing is to work out any surprise issues so we can merge this now
Ah lright
So stable will be releasing 555 or 560?
560
560 is stable nvidia
we will happily ship 555 if the issues are worked out
:0
that's what the change to negativo affords us
take it back I should not have said shizzle lol.
I will try this in a bit
Got it. So we need to iron out the xiv launcher fixes then. @rin when you moved to testing , did the launcher start no issues?
that appears to be a you thing, based on what @Rin said
please set the flatpak perms back to what they were and give us a full log
If I'm the odd case out I'll rebase back to testing when I get home and try and supply any logs I can gather.
does it happen with xiv only?
So i get to the login screen now, i hit login and then it goes black screen
if you're on latest we'll need a log, iirc you are the only person with this issue atm
also
rpm-ostree status | fpasteOkay how would i go about getting this log then? Is there a shortcut to bring up a terminal on the black screen?
control+alt+f4
Thats not brought anything up
Anything else?
Also, I don't think this should be released as long as Firefox keeps crashing
that is a kernel-spawned thing
if that failed, your system is hard locked
and there is no saving it
Ah okay
Ill go back to the other version
okay back on the stable version now
yeap, just launched and it was ready perfectly fine. The driver should be the only change from stable
I think I fricked up somehow lol
Only one I had time to test.
so i managed to do a hard reset and got back into the version 1 on the selection screen of bazzite
the stable one i mean
you're already on testing
rpm-ostree update and rebootodd I could not boot in testing
I literally was going to do this to see if I now could
if you mean earlier, yea
we pushed fixes
looks like it works for you now
what the hell I did not udpate since earlier. I think this just randomly worked and I accidentally loaded the test one XD
there's auto updates on desktop builds
like I said,
rpm-ostree update and rebootok
rpm-ostree status to confirm what you're onyep I clearly got confused
it wasn't that I was not believing u. I just did not realise it worked or how or when but happy it does lmao
I got myself in tree inception
updating anyhow
so now I am like did this auto update when on my other tree
or like just happen to work when booting it
should be fixed now
disabled wayland on firefox
Lovely!
Wonder how long the testing cycle will be.
well I am on nvidia testing now and was going to show a screenshot but thas tbugged lol
there we go
That said, this has been the most painless Linux package testing ever. Great jobs guys and gals and all those someplace not included.
and it says testing and we up and running
to see ubisoft connect work well
mama mia
🤌
okay so noticed one issue but not sure if related and only appears in a chat I want to keep secret as it has confidential information
oh it happened just now
okay still a bit of a discord bug
will record
okay obs is a struggle too atm recording
to be continued
OBS should work w/ gamecapture
okay will try gamecap to record my discord
pipewire screen record did not work
I dunno what pipewire is except for it being a linux thing but seemed to be an issue there
game capo is a rip as well
will try reinstalling obs
you need a launch option to use it, it's obs-vkcapture
check their github
reinstall fixed screen capture
right away
either it needed a restart or a reinstall
will search up the thing u mentioned for game capture another time
trust when I want to capture this discord bug it stops doing it lol
hard to capture it. Sometimes it can be obvious and sometimes really hard to produce. Even had a channel flickering but it is rare
ONe more example. Basically the flickering can still occur but not nearly as much
maybe I am not on new drivers as flickering still confirmed on steam when fullscreening and seeing the old behaviour still appearing here and there but as I am nto recording ofc
nope defo 555
so point of reference, ive just done a full reinstall of bazzite, as in wiped my drive, everything and reinstalled with usb, im just about to rebase to testing after running a system update and rebooting, lets see if that removed any issues
I need to turn of that new kde plasma feature of locking mouse ont he edge of the screen as u go across. At least I think it is a feature
edit: noticed u have to swipe mouse quicker between screens now basically so must be a feature.
Okay so im in
must have been something wrong with my setup 🤷
MOuse size bug u can make happen if u move ur mouse fast between screens or it could be a feature
Ha mine did the same
I dunno if these things are meant to be features u know
yes this must be intended
lmao
Yeh its gotta be the old find your mouse accesibility option
never seen that before
but yes thought about it and okay I could get it being useful for sm1
I need to stop the mouse stopping at the edge though
between screens?
I really dislike it as I use windows key and arrow keys to move my windows
yes
yep mine does that
it is a new feature I am sure of it
not a bug
but me no like
i cant really test any games out until tomorrow as its very late, but things seem semi stable, no flickering of windows as of yet, HDR seems to be working well i think, although i know thats experimental, good job on this test build ngl
quick ass progress
for flicker I found the easiest way is going to steam and watching a trailer in fullscreen
but not sure if steam glitch
XD
let me check like that now then 🙂
did you maximise the trailer or left in the window?
skip to the end of this
last 10 seconds or something
fullscreened it
white flashes
holy shit
yeh
thats blinding
u get that too?
yep
and liek with discord I noticed the same old behaviours can occur
just not as aggressive maybe
trying to find a vid in discord to play
discord is fine
u can try my vids
lol
yeh discord is fine
i use vesktop anyway
just for screensharing audio purposes
Has Kyle marked down that white flickering screen issue with vids on steam?
should already be fixed
ive just rebased to testing about 8 mins ago and its still happening to me
odd
I am going another system update and trying again
is there version appendages to any of these build updates?
but also having that and discord issues we had already
probably CEF weirdness from the looks of it
guna try testing youtube, etc see if its just steam
hmm okay firefox just crashed, do i need to change some form of setting in there?
ive just pulled in an update under flatpack system pacakges
Lol after update it auto logged me in then it booted me to login screen so I logged in then blackscreen
Was just about to report the same thing
Lmao
I love testing genuinely
All the wild shit u see
After reboot it has let me login but now cannot do anything and black screen
Oh wait it loaded
Took a long time this timd
Ill try leaving it a while
Lol back to login screeb
Whilst typing in discord
Then the login kills it maybe again
Yes ima leave it probs
Back to watching the boys on my pinned tree
My tree of safety
Yeah, I had that for a long time, not exclusive to 555
Yes I just thought 555 is fixing that
Maybe
I'm all about 560 now
Jkin
Ive never watched a trailer on steam so might be something there previously. Im guna leave it for now, will do some further testing of future builds if i get a chance on sunday
Deffo there previously on Wayland
well back to my stable x11 tree
will bve a pleasure to test again though ofc
Okay, purged the win prefix, and make sure to update the deps in discovery first and it looks like its working?!
was there a fix for firefox crashing?
rebasing back to stable, its a little off, hope 560 fixes things.
@LibertyBetaok so regarding xiv. Installed with that launcher you mentioned. Got crashes, something about error with directx, with this interesting line here
then i ran with this
and
Idk if its the same exact issue as you, leaving this for the record
the weirdest thing is i only had to use that enviromental variable once, afterwwards i can open the launcher from the apps menu and still works
Nope, different error. Killing the prefix fixed things.
Also, some how in all the rebasing it went from fedora 39 to 40?
Or my brain is just mush.
from 39? what version where you before rebasing to testing?
cuz stable has been in 40 for a while
It was a brain fart. I was on 40, I checked my logs. One of the deps for a project has 39 as a min and I was conflating it.
But yeah, rolled back. Its getting there but I'll wait.
Understandable, testing requires a LOT of pacience
I only can deal with it because im a masochist with computers xD
I've got too much in my plate right now with two software releases going out this month.
If I was a younger man, I'd help test.
what logs are we looking for?
Lol Discord typing is still laggy
Firefox crashes as reported. Steam is behaving nicely
yeah mouse wiggle making cursor big is accessibility and can be turned off easy
perhaps useful updates
Not lagging here. Are you sure discord is running on wayland and not x?
Not sure - if I force wayland windowing in flatseal it crashes
But I reset flatseal permissions and reopened Discord and it's all good now so that's great
Does G-Sync work with dual monitor? IIRC no...
Gaming seems fine
Gsync works with single monitor
I dropped gamescope and ran Helldivers 2.
Performance in borderless window is horrific, but if you switch to full screen it's nice (just has the black screen bug if you don't set it back to borderless window before closing)
Aside from Firefox (which seems to be a Firefox bug) everything works nicely so far
Sometimes it takes a second to transition from black screen to desktop after unlocking but nothing to worry about
*I'm a prolifically light user so not a good baseline
Yup, I can reproduce the strobe light when doing full screen videos in stream. Games running nicely though
noticed using my keyboard to move around a window can cause this whereby you cannot see minimise, expand and close on google chrome
Just noticed this thread has over 400 replies lol.
Is there some form of collation of issues for us testing the release at all? Not sure if we should be creating issues on the github issues page or not, dont want to inundate devs with uncollated unorganised issues from here
Rather a big thread than 10 tickets on here all with similar issues. I'd hold off making github tickets unless Kyle or one of the team asks for it
Yeh fair point lol
I was wondering why I get so much flickering on xwayland apps on bazzite and not on arch, most probably is because right now on bazzite we are using xwayland 23.2 which doesn't support explicit sync, it should get bumped to 24.1
Now that comment, probably should go to the github issues. Nice find! That will be great for everyone. A bunch of AMD users have also been having flickering issues
holy cow
there is hope yet for 555 x wayland
Might be more needed
wayland-protocols 1.36-1
xorg-xwayland 24.1.0-1
xcb-proto 1.17.0-2
xorgproto 2024.1-2
I'm also having my Vesktop from time to time not showing up anymore, happens when I quit and reopen. I always have to reset and log in again to solve it, might be related to xwayland
Tried pulling the newest build of testing again and booted into it, still a black screen after logging in, unable to use ctrl alt f4 as its just totally black, so just sticking to stable until theres a new release of testing to try out
Just updated, steam videos not flashing weird colours, firefox still broken. Discord solid af now
Borderless window no longer has performance issues in Helldivers 2
Amazing!
Firefox is a Mozilla problem to fix unfortunately
All I can do is apply a workaround to force it to run on xwayland
Which is less than ideal
Yeah they seem to have ackowledged it now so ball is in their court
no harm to have two browsers until they sort it
there is a little bit of frame dropping here or there in KDE - noticed it when Vulkan shaders were loading
idk if some caches are being cleaned up but closing and opening apps first time around seems to resolve any lingering issues they have
Discover crashed once and now it's back to normal
Thanks Kyle for setting this up for us. I was kind of hoping we'd get a test build with 555
The Vulkan shader caching was noticable for me. I actually heard fan spin, which I never do.
ill give latest image a try later on tonight 🙂
ooo I was 24 layers behind
lets go
on normal discord and seems to be working fine on test now
dunno which thing fixed it but yes
only cam eback after the updates now
and steam video not flickering
nice one folks
thanks to the team that work on it and to make everyone's time great
looking forward to when all this is confirmed for stable
I think we're just waiting on a fix for Firefox now?
Found an issue
If I hit log out
Black screen
Well let me explain better
I saw the login screen and before I could log back in I got a black screen
And I am stuck there basically lol
So more of what I believe people called the sbmm
Just rebooting but I can report major improvement everywhere else lol
I am able to replicate this as well
Made a vid on my phone but may need to find a way to compress or record for less time
uploading lower qual video now (whcih does not matter for the purpose of the video thankfully)
Since you're all on testing let me know about performance next build as well
how would you like us to go about that. Just test something GPU demanding then something cpu demanding?
compare to what we had before I dunno
Just games tbh
no worries. I will get cyberpunk out I guess
do you want a comparison or just simply record footage of a game with fps and frametime graph or osmething
or u just want us to say good performance or bad
ima go to bed soon but cp over halfway now wiht 14mins remaining tomorrow
This
If you notice a difference one way or another
Will do
Basically good or bad will come out of it
Have pulled latest version, unfortunately still get a black screen on boot up, which is unfortunate
After login i might add tho
I think you're the only one getting that consistently
Gonna need some logs
Okay, how do you want me to produce them? I cant get into tje cli with ctrl alt f4 when i get passed the login screen to the black screem
That's an issue then, hard lock up
Maybe SSH?
I could try that sure, ill get my laptop booted up and ssh into the pc and grab some logs on the bootup after the login?
What logs do you need specifically
Just rebooting into testing again, guna ssh into the machine on the login screen, then login on desktop and produce some logs. Just let me know directory/location of the logs needed
Okay all ready to grab logs now
Im going to have to hit the sack now as its very late here at 2:30am lol. I grabbed the Xorg log from var log, hopefully that'll be helpful, if not will have to catch you another time
Xorg isn't installed anymore
Need a dmesg
Ah okay
Whats the location of that?
Found it
@Kyle Gospo hope that helps boil down what the issue could be
Anyway i gotta go to bed, almost 3am 🙂
must be uk like me
in my case only thing I noticed is that normal discord did not load this morning but updating then rebooting to see
then will so something to say performance good or bad
High five UK gang
:catDance:
DOing more than asked cos I canno thelp it otherwise I would not know if perform good or bad.
Wayland on test buil then x11 on old stable build from a week ago benchmarks on cp ultra preset show performance is good. Wayland ofc here better but in the realm of margin of error maybe
so no issues for me with the latest in that regard
yehh its hard providing feedback sometimes due to the time difference lol, ive provided the logs needed anyway, im going to try again for a brand new fresh installation and then switch to testing that way, doubt itll do anything but who knows
yesz I am lucky on my end
as u can see when I logout I have an issue occur
of the black screen
last I tried anyway
https://discord.com/channels/1072614816579063828/1253638858940092500/1254206422095368292
there are deffo some bugs here and there
I dunno where to report them but I try to here
not that I am trying to find them either
crazy how our experiences can differ so much as well deespite same gpu
Welp
I just booted up, logged in no issues, launched Helldivers 2 in gamescope after turning on HDR in KDE settings and walked away for 15 mins to deal with something
Came back to black screen.
Rebooting doesn't resolve it - I can get to SDDM, log in, and then I'm black screened
Perhaps HDR is the issue?
Used my stable image to boot
Disabled HDR
Will test booting into test now
Yep now I'm back into test
But now it's kicked me back to SDDM and logging in gives the same black screen
do you have it so it lcoks your screen by default?
after a certain amount of time
Yeah
look what happens here https://discord.com/channels/1072614816579063828/1253638858940092500/1254206422095368292
probably the same as me
the 2nd time I log out
and wait a bit longer
basically I cannot logout without blackscreen
ur prob the same
when u reboot into the os I guess u will be fine but then if u logout and leave it for a bit or drag mouse to the other screen it will black screen on u
Mmm just went into tty and back out again and desktop is back
oh okay lol
Logging out
Yeah black screen
I did not test just locking my screen to be fair
could be only logout the thing I mentioned
I could sleep without issues before. System would resume and I could log in
lets hope whatever is causing it gets patched I guess
There were 6 failed log in attempts since the last successful login
So it's crashing during log in
Coz I didn't screw up my password
startplasma-wayland command gets me back in from tty
But the original session with ctrl alt F1 is dead
yes I had that
had to tty2
I do not know much linux so that spartplasma-waylland command will come in handy
for me
but yes there have been lots of bugs which obv can be expected from testing tree. NIce to be able to use wayland this well now though once a bunch were fixed over the last 2 days
running great so far here no flicker on xwayland apps on latest image. Only thing missing for me its firefox, but that's on firefox
yes flickers gone.
JUst tried firefox and same for mee though I Mostly use chrome despite whatever reasons
what command are you guys running exactly to get rebased to testing?
is it this?
I believe so rpm-ostree rebase ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-nvidia:testing
arr for me nvidia
at the end
bazzite-nvidia
ah
yeh
thought that looked wrong
two secs
forgot the nvidia bit xD
okay im in!
i bet you i was running that non nvidia command really late last night
okay time to download some games and go from there
:EvilSchemeOcelot:
yeah it's intermittent. I just rebooted, usual log in experience and then decided to try logging out again and it's all fine
I did catch the logs just in case - I can't find anything there other than some issues with themes that look a bit sus
for me it is consistant when I log out
if I leave it for a certain amount of time
it happens
or if mouse goes to the other screen not sure
it also looses my display settings in the login screen once logged out
as my mouse has to go right to go to my left monitor
Okay so rebooting after a ujust update has brought me to login screen, i then login and its a black screen. Some nvidia stuff got updated during that ujust update
I just updated this morning
so I guess we are not experiencing the same stuff. Interesting buggyness
Yehh weird stuff
Worked fine before the update tho, so just not going to run any ujust update and continue using for a bit
so I tested the logout thing again just now and did not happen lol
so yes maybe it can just happen or it is no longer a bug for me
If you leave out the nvidia, it then it will revert to the nouveau driver. The opensource driver is supposed to have gotten a lot better lately. Would be interesting to compare benchmarks with the official driver vs the opensource one. Suspect that you'll probably loose 40% performance or so
Try launch a game and sleep the machine. For me that results in a blank screen
I never really have my pc in sleep mode
it sometimes does not work on windows either
but okay sure
lets do it
I also had this disabled in the past as it cannot tell ur watching crunchyroll on the web
so will sleep mid video (we talking before I tried test build)
I've had that on Windows 🤣 , very annoying. The worst is when it detects that the machine is inactive while you watching a video and reboots for updates...
tbh sleep worked
fine
it suspended
I pressed power button
logged back in
does it happen to u every single time?
or a bit random when sleep causes this behaviour for u? FOr me it was actually all good but still not allowing my pc to get sleep
sleep is for the weak
Let me confirm
one thing is my fans seem louder after reboot from sleep
interesting bug on a newly installed system, my primary display is the one that doesnt have a taskbar, and the secondary one does, to get my taskbar onto my main monitor i need to switch my 2nd monitor to be my primary
thats not on testing, just weird shenanigans
Yeah that's just KDE standard lol
rather amusing lol
is there a way to have the taskbar on both displays?
I used to get that
not anymore
but I used to have that issue a lot
Yeah that annoyed me for the first few weeks of using KDE, used to having the taskbar on all screens
not happened to me in ages u know
even on x11
yeh just feels odd to open everything from my 2nd monitor and then have my primary have the screens opened on
first time its happened
but yes u can do anything
u can have a panel top and bottom
anything dumb
too
lol
like that
how do i change those things?
right click ur taskbar
and show edit configuration or whateve rit is called
it will look like this
so fresh install, updated, rebased to testing, booted in, and im in, just not going to run a ujust update just in case
if you brake it completely just reapply the theme again and you can fix it.
to add a panel u do what i idd here
thanks! that did the trick
silly thing
😄
to set a position one of the ways is to clifk the relevant panel and then select through this one
though windows has the same sort of thing for having a taskbar on whatever screen. THis obv allows for nice customisation and I love how u see what u are doing
on windows I think it is a dropdown
so i did have firefox crash, is ther a workaround or just use a diff browser?
like have on primary display only
etc
I did too. DUnno if workarounds. I have been using chrome anyway
Messing with these settings seems to crash KDE for me
interesting
Even simply opening the extended task tray breaks it
Everything is non responsive but I can use terminal etc no issues
always been the case or just this testing build?
Just test build
seems I am very lucky
I noticed I coudl not change how transparent they were and that was it for me
everything seems okay with me, i did get a plasma session crash briefly, but that was on opening brave
I think tbf it is too bugged for stable maybe
seems to be too many issues for that from such a small amount of people reporting
The one positive is it will stop the "is 555 available yet" in the main page? I also think it's cool being able to be a tester if you want
yes I kind of god bazzite to have something stable but the thing about bazzite is that it feels safe to test shiz and all the stuff I download is still on my older build for when I go back
cool af
loving this os that I can break a tree of
Okay so it seems some form of update is happening being pulled from nvidia which is stopping me from rebooting correctly, its fine on the rebase, i do my configuration etc, reboot, then get to login screen and it flops
and go back like iwth nothing lost
it feels anyway
I really appreciate being given the opportunity to use 555 as well and I do like testing things too
Nothing has been complicated either to try out
with the discord here as well
Jun 23 13:11:27 fedora kwin_wayland[5423]: kf.windowsystem: static bool KX11Extras::mapViewport() may only be used on X11
Jun 23 13:11:24 fedora kactivitymanagerd[5624]: kf.windowsystem: virtual void KX11Extras::connectNotify(const QMetaMethod&) may only be used on X11
Jun 23 13:10:52 fedora nvidia-ctk[4199]: time="2024-06-23T13:10:52+01:00" level=info msg="Selecting /etc/X11/xorg.conf.d/10-nvidia.conf as /etc/X11/xorg.conf.d/10-nvidia.conf"
Some calls to x11
Do you have anything layered?
No just defaults
Something razor might be layered but was installed from the setup tool
one thing that I have found. Despite discord working it will not copy and paste whereas vesktop visktop whatever it was called allows my copy and pasting
will just be using it from now on anyway I guess
Are we sure kernel-headers are not required?
https://github.com/ublue-os/bazzite/commit/8d5e8331af0585bf54e192b672aa8de7c7e7fc37
If the drivers are prebuilt against the current kernal then we shouldn't need the kernal devel stuff. Well the part that needs the kernal headers, not sure how that all works with proprietary drivers lol
Closest I can find is this report:
https://www.reddit.com/r/linux_gaming/comments/1cndjuh/after_installing_nvidia_driver_and_logging_in_in/
Reddit
From the linux_gaming community on Reddit
Explore this post and more from the linux_gaming community
looks very similar to what i was seeinf
im going to wait for further testing until i see a few big changes, maybe a week or so, then will report back any issues i have
We should be fine without devel, as I think navigto doesn't need do any at time compile.
Just confirmed, any game if I sleep the laptop while a game is running. Blank screen or if in Window mode, the window changes to a black window
fairs I guess anothjer depends on the hw issue
Do you have drives that auto mount by chance?
I doubt this is at all related to our issue because it was working fine under Wayland before driver changes but this user has similar behaviour issues on Wayland with a weird drive mount set up:
https://forum.endeavouros.com/t/black-screen-after-login-with-kde-wayland-because-of-bash-profile-script-not-with-kde-x11/52229/18
EndeavourOS
Black screen after login with KDE/Wayland because of .bash_profile ...
OK, I solved the issue. It has nothing to do with amdgpu or plasma6. It has to do with wayland, though, although I’m not sure about the mechanism. I have a .bash_profile file which mounts all the removable stuff and Windows disks currently present upon login: # # ~/.bash_profile # [[ -f ~/.bashrc ]] && . ~/.bashrc # mount unmounted disks a...
i do have secondary drives that are automounting yeah
Me too
It doesn't really explain it though because some boots work just fine
I'm getting the same errors that you seeing in the your log and I can get in
@Marko if you run
journalctl --since="2024-06-23" | grep "only be used on X11" can you see if you getting these errors too?
not going to impact my game or anything right?
I am also on wayland atm and the command says only for x11
does that matter
All I want to do is eliminate errors. You used to get the blank screen and it's working for you now. So that is probably not the error stopping them from being able to log in. Also just printing from the logs shouldn't mess up your game at all
From what I can see of the Nvidia config, it's the container config so not affecting main system iirc
This command just grabs logs
You can also add "| fpaste " to the end and it'll upload it for you to copy paste a link here for us
Is this log from stable?
I'm on the testing branch
Ah cool
And Marko is back on stable branch?
Would be interesting to see if it's in the logs on stable. If so, not likely our issue
Yeah also on stable so not our issue
Could it be fsync kernel 6.9.6? Was updated today
I just did what wolf said to do
I am on testing tree
as u can see there at the top
I love that I learnt how to make logs just like this so cool
had no idea till this discord
@wolfyreload was that of any help?
Thanks, then we know that isn't the underlying issue.
kernal updates are a good candidate for issues
Where is the fsync kernel git / changelog?
Okay I booted with today's update, I could get passed the login screen, then after some seconds I went back to the login and black screen after trying to login again. Rebooted from button and now everything seems fine, don't get it
I used to have that issue with the testing release but it stopped for some reason https://discord.com/channels/1072614816579063828/1253638858940092500/1254206422095368292
Yeah login very inconsistent
But I'm 100% having to type my password and try to login multiple times to login after I manually log out
I'm also getting that same errors and they seem to align with my login tries
I've been running these testing builds on my own hardware, none of which is Nvidia
So I can at least confirm the login issues and black screening problems are a Nvidia only issue
as for gaming so far, everything is running totally fine that I can't really notice any difference from the stable with X11. Some might be even more smooth now that I can use VRR
I'm thinking of moving to Gnome, do you think worth testing there?
GNOME Wayland has been generally far more favorable to Nvidia
Worth trying
At least you get looped around to keep trying. We were getting black screened lol
still get black screened from time to time after reboot, but yeah at least I can login after logout
nice, will reinstall Gnome from Silverblue later
I don't have a 10 GB flash drive at the moment so I'm having to always rebase from Fedora
It's a shame you can't rebase between DEs directly or I'd try gnome
You can
We just tell people not to because it's a support nightmare
Make a new user after you rebase
You'll have no problems
Good shout
Thanks might try for testing purposes
Great then! I already had a second user for testing, remaking now
Don't tell me I need to rebuild my os for gnome Wayland. I like kde.
That said, what's the preferred de for bazzite on desktops?
we support GNOME and KDE equally
Oh good.
That said, most of my issues with 555 werent kde related.
Okay so walked back to pc and now having the issue the other dude mentioned
I now login and eventually takes me back to login screen which I login and get black screened
And the old stuff if I dnt login fast enough
Rip
and fine this time around
dunno what fixed it but will take the w
Just rebased to bazzite-gnome-nvidia:testing and getting a black screen immediately after reboot. Running an AMD 7600 CPU and RTX4070 GPU.
That's so strange, I've been using Gnome all day and no issues so far. Login and reboot working fine, gaming wise the same as was getting on KDE so good for now
This guy had the original issue we faced with black screen + cursor but got it working by nuking the KDE configs:
https://github.com/JackPala/KDEnuker
Could be worth trying to create a new user in KDE and see if he's right that new users with clean configs don't face issues with black screens (though I think we're past the black screen w cursor issue and onto something else)
Someone else suggested they found their problem in SDDM logs and not journal by checking here:
/.local/share/SDDM/wayland-session.log
GitHub
GitHub - JackPala/KDEnuker: Deletes all KDE related files in the ev...
Deletes all KDE related files in the event that your KDE Plasma install gets broken - JackPala/KDEnuker
I suspect it might be an issue with DisplayPort, I’ll try to connect my system with HDMI and see if it works.
@Rin How is your machine connected to your display?
https://github.com/NiHaiden/aurora/issues/20
https://paste.centos.org/view/6b606d2d
/etc/dracut.conf.d/ is indeed empty for me
I'm using DP, 1920x1080@144Hz specifically
Applied and building
Oh, mine was also over display port. Could that be the common issue?
I was using DP
I am using DP on both my monitors. Both are 1440p and one is 165hz with the other 144hz
legend
😎
Ironically updated and blackscreen. Just reporting as not an issue for me personally knowing it will get fixed one day
If we can get a log for this black screen that points to something tangible that would be very helpful
Sadly I am not a very good penguin user
Happy to try whatever is suggested
I can access tty2 in this state
Oddly had no black screen from updates yesterday afaik and only occured again today
Dunno if each update refreshes something
Sorry I would.not be sure what to log as I'm a complete novice really
I only recently learnt >whatever.txt to log what I run
Wonder if the ujust logs-this-boot it helpful
Tried lastest testing KDE and same, just back screen with mouse again
hoping tht is somehow helpful
all this stuff could be normal I dnt know
Anyway I will stop pretending I get any of that lol
Might have found it, new build going up now
For future reference is that log I provided helpful or utterly useless?
Haven't looked yet, I just found that negativo ships a config file that prevents the driver from being added to initramfs
Completely undoing the change I just made
It's reason for doing so is irrelevant to us and our build process
Worth noting that the option in the grub starting in 623 (my ostree 1) works and the latest (my ostree at the time) did not work
no worries. Not sure if I over report or not
but willing to test as for this round of testing
been enjoying wayland + 555
If the issue is what I think it is it's a timing thing
Every time you boot you have a chance of black screening or maybe not
Which is why it's been so hit or miss for you guys, I haven't been changing anything between builds
arr interesting
well I tried 624 like 5 times with no success. I know the number 624 may not be too useful
623 I have just tried twice and no problems
but I did experience hit or miss with one of the builds the other day as u say
whereby one part of the day it worked then the next it did not
lol
So I was about 50% helpful
Yay
Worse than the black screen for me is that KDE randomly locks up if I play with the editor or the quick settings too much lol
But I'm gonna say that's a KDE issue
it is fun how this could breakdown into a timing issue
lmao
I like test builds with this atomic desktop setup we got though
we can test shiz without worry
I wonder if that other guy I found was right and that simply cleaning KDE configs helps with that
I'll probably try a new user to see
I certainly did not experience that
I have been using test branch every day and after work on the weekdays
nothing like that
Can you try messing around with the layout editor, just change the task bar behaviour to something and back, then start playing with quick settings menus open and close nothing else
That's enough to kill it for me
done that before
not an issue
I have a video here of me doing it
well not a video https://discord.com/channels/1072614816579063828/1253638858940092500/1254408236468146208
I did at one pont do that though
I swear it
oooo n ew change has finished cooking in the oven
time to update
:PU_PeepoDab:
so blackscreen still occured but aghreeing with Kyle. You see the screen that normally loads for longer before login flash before ur eyes in an instant on the latest. THis is my latest log on it from earlier
back to tree 1 for now as this seems to not flash for an instant when the screen before login is showing the spinning circle and my mobos logo plus bazzite logo
Jun 24 20:22:12 fedora sddm-greeter-qt6[6713]: Loading file:///usr/share/sddm/themes/01-breeze-fedora/Main.qml...
Jun 24 20:22:12 fedora sddm-helper-start-wayland[6702]: "QSoundEffect(pulseaudio): Error decoding source file:///usr/share/maliit/keyboard2/sounds/key_tick2_quiet.wav\n"
Jun 24 20:22:13 fedora sddm-helper-start-wayland[6702]: "MESA: error: zink: could not create swapchain\n"
Jun 24 20:22:13 fedora sddm-greeter-qt6[6713]: file:///usr/share/sddm/themes/01-breeze-fedora/KeyboardButton.qml:19: TypeError: Cannot read property 'longName' of undefined
Jun 24 20:22:13 fedora sddm-helper-start-wayland[6702]: "MESA: error: zink: could not create swapchain\n"
Perhaps revert it? Pulse audio isnt happy. Actually has the start up / log in sound disappeared recently?
Jun 24 20:22:09 fedora sddm-helper-start-wayland[6702]: "OpenGL vendor string: Mesa\nOpenGL renderer string: llvmpipe (LLVM 18.1.6, 256 bits)\nOpenGL version string: 4.5 (Core Profile) Mesa 24.1.2\nOpenGL shading language version string: 4.50\nDriver: LLVMpipe\nGPU class: Unknown\nOpenGL version: 4.5\nGLSL version: 4.50\nMesa version: 24.1.2\nRequires strict binding: no\nVirtual Machine: no\n"
Jun 24 20:22:09 fedora sddm-helper-start-wayland[6702]: "OpenGL vendor string: Mesa\nOpenGL renderer string: llvmpipe (LLVM 18.1.6, 256 bits)\nOpenGL version string: 4.5 (Core Profile) Mesa 24.1.2\nOpenGL shading language version string: 4.50\nDriver: LLVMpipe\nGPU class: Unknown\nOpenGL version: 4.5\nGLSL version: 4.50\nMesa version: 24.1.2\nRequires strict binding: no\nVirtual Machine: no\n"
Jun 24 20:22:09 fedora sddm-helper-start-wayland[6702]: "kwin_scene_opengl: No render nodes have been found, falling back to primary node\n"
Jun 24 20:22:09 fedora sddm-helper-start-wayland[6702]: "kwin_wayland_drm: Failed to create framebuffer: Invalid argument\n"
Jun 24 20:22:09 fedora sddm-helper-start-wayland[6702]: "libEGL warning: MESA-LOADER: failed to open simpledrm: /usr/lib64/dri/simpledrm_dri.so: cannot open shared object file: No such file or directory (search paths /usr/lib64/dri, suffix _dri)\n\n"
Jun 24 20:22:10 fedora sddm-helper-start-wayland[6702]: "libEGL warning: MESA-LOADER: failed to open simpledrm: /usr/lib64/dri/simpledrm_dri.so: cannot open shared object file: No such file or directory (search paths /usr/lib64/dri, suffix _dri)\n\n"
Jun 24 20:22:08 fedora systemd[6682]: /etc/systemd/user.conf.d/timeout.conf:1: Assignment outside of section. Ignoring
Searching points me here:
https://wiki.archlinux.org/title/NVIDIA#DRM_kernel_mode_setting
Which suggests were not using Nvidia drm but we are...
I think we're somewhere there with today's changes and looking into initramfs
https://bbs.archlinux.org/viewtopic.php?id=295937
fbdev is there
this shows the nvidia driver for opengl, your example slows llvmpipe
totally different issue
Latest build
first issue with Gnome today. I'm sure I was using Wayland yesterday but today I'm stuck in X11 and the option to change is not on the login screen
I thought X11 wasn't even supposed to be an option? Or it's just going to be dropped for Fedora 41?
it should not be an option
ast least in kde I dnt have it
yeah it's 100% not an option in KDE for Fedora 40
If i follow commit history correctly, it was there early on, but unfortunately got removed when moving to negativo? Fingers crossed for your latest commit
negativo has it in theirs
seems it's missing though (?)
so I restored ours
Yeah it's all jumbled. Your setup seems like it was cleaner than negativo
latest build failed?
I will be likely testing tomorrow whatever the result and reporting as per usual and with that ujust log thing I found as well
What's the ujust log thing
well honestly I don't know but it is this message I am replying to here
u know how u have ujust commands
well one of them is like log everything in this boot
and I used that and added a > wahteverIwanttocallmylogfile.txt
then went on a version of wayland plus 555 that worked for me still to send the log here
but I would not know if helpful or not
its like for me if there is a way to help and simple enough then I will attempt it
fairly willing if it helps other users later down the line
green
Sorry m8 it's time for a cuppa and a kip
not hard to tempt me
consider it done :EvilSchemeOcelot:
it worked for me
not sure if luck that it did not close that loading screen too quickly that norm just flashes for a microsec u barely see it
or not
but it worked after update which iwas consistantly not doing before
log of it working past login not that it is required but to be thorough I guess lol
going to bed
Don’t wanna jinx it but the latest testing build seems to have fixed my black screen on reboot for GNOME
Na let's jinx it to not jinx it
nvm, it's back on the last build!
sooo aside from Firefox crashing, everything running fine
believe so
that should be fixed now as well
I was setting that manually too, works mostly fine only issue I have seen is this when I open the first window, opening a new one solve this. But totally minor, it's usable for now and there's always Chromium if needed until they fix it
ty so much for all the effort, loving this 555 testing!
I can't wait for it to hit stable.
You might want to try it now, I think this is almost there at this point
I'm not seeing much in the way of blockers
Especially given how many things this fixes
Only issue I've seen was Firefox crashing.
Rebased to testing. Forgot to include Gnome, so was KDE. 3090 FE. Black screen with what looks like a tiny non-blinking cursor in the top left. Can’t switch to another tty to gather any stats, so seems like rebooting is the only option.
So seemingly no dmesg available to provide.
Grub was fine, selected the ostree image. The black screen appears to be where I would expect to see a login screen fyi.
Once I boot back into the previous pinned image, would I want to remove the 0 image (testing)?
Or from the prior 1 pin, would I want to rebase back into the non testing branch (which would be what the actively booted image is already)
I did an rpm-ostree cleanup -p which removed it. I will test another :testing image soon and see what happens and hopefully provide some data.
If it’s helpful, using a Ryzen 9 3900x, 32GB of ram. Asus TUF 570
Firefox still crashes when watching a video etc, but it opens now
The networks taskbar crashes KDE for me still though. If I hover on it and the info pops up, KDE freezes up and I have to launch everything from terminal
and copy paste keyboard shortcuts freeze chromium when in this state - trying to check logs
https://paste.centos.org/view/e6f32e26
Probably a KDE issue. There's some old posts about the same behaviour from up to a year ago
And a black screen after rebooting lol
My Hdmi screen works, but my DP screen has no signal
Detected but black screen
And on shutdown it got output lol. Kde bug maybe
Rebooted and now it's working
I'm going to call it a win. Either I need to clean up KDE configs or wait for them to fix bugs
Not that it seems to matter, but dracut.d is still empty - just flagging incase it should be populated with recent changes
wrong dir
I'd never add to /etc/
/usr/lib/dracut/dracut.conf.d/
Sorry I am a nightmare user
it's there
all good, need people checking me
So whats the general consensus here for testing? Nvidia people to gnome and everyone else on kde?
I was on kde last night
it worked perfectly fine for me
okay will give kde a go 🙂
do you use Display port?
yes
both monitors
not saying it will work
but for me perfectly fine after last nights update
yeye thats fine of course lol, just guna give it a try now
gl
i mean, good signs so far
straight into login screen, logged in okay
then u prob good
the main issue for people has been login
apart from that works as expected for the most part
as far as I could tell
amazing
has anyone tested the hdr capabilities yet?
my monitors are not worth hdr
I imagine many in the same position
u may be our only hope soldier
ill give it a go now
the applying of things is WAY snappier now
in display config i mean
i think my main issue that did happen was an update happening in the background for nvidia that borked the login
so guna give it a little until i do a reboot
fairs
yes for me an update before the prior one defo worked for days without issue
obv only days cos I keep uopdating
most recent one I have tried for a bti of an evening sooooo
and gamed on it a bit
seems good though
I love how u test this shiz and even if broken u go to another tree and it just works with all the stuff u had
- DRG works great with everything on max, still have the HDR option greyed out but i had this problem on windows. Running on DX12
- Control with Ray tracing and DLSS at 3440x1440 with 77% resolution was working well, was getting slight stutters here and there but nothing different to its windows counterpart. Running on DX12
- Running desktop mode at HDR on both displays, one HDMI and one DP, 3440x1440 on DP and 2560x1440 on HDMI, no flickering issues from menus, youtube works great
- Jellyfin Media Player doesnt seem to open fully, just get a black screen inside the windowed borders. Tried a reinstall of jellyfin, that didnt work, Discover store did crash as well on installing
- In general the discover store has crashed a few times now
- Firefox crashes but floorp seems fine
- Plex HDR playback seems good direct play and no transcoding, so HDR seems to be working well
Guna attempt a restart now as well as this was the issue i had last time, some nvidia drivers got downloaded in the background and caused black screen issues on reboot
Okay restart has brought back a black screen
Cant get into terminal so its a hard lock up
Restarted back into stable okay, ill rebase back to stable after a prune and then should be alright.
So seems the black login screen issue is still there after a restart after updates are done in the background for nvidia drivers
for jellyfin try "--disable-gpu" flag when launching
Okay will keep that in mind for future testing, ive rebased to stable now though as i cant login on testing after a reboot with a background update
wait discover crashing cos hdr on?
or just in general lol
I wonder why these nvidia updates are not happening for me
in the background
to frick up my shiz
Just in general, its the same issue as before thats not been fixed yet
And now rebasing to testing i cannot get past the login screen, will be waiting for stable i think and seeing if that works. Otherwise will be pinning version
fairs. I wonder why the experience differs
to that degree
Might be just down to different gpu generation issues
who knows
it looks bad in desktop usage so not worth having it always on to get it working in game, especially as then gamescope is required. My monitor isnt' great with HDR anyway
This looks important - latest build failed so not available to us yet: https://github.com/ublue-os/bazzite/commit/181b207221a0180c350ef85194a50f9ebe257923
I'd be tempted to say the first build ~21st June was fine and didn't have log in issues, then things got mixed up in some commits migrating properly across so it may just be a case of working back through commits to see what was configured before, and making sure we have all necessities in place
Im way over simplifying though
HDR looks bad in desktop use? Just in general or on linux?
In general - looks like ass in windows for me. My screen isn't great it's like the worst HDR you can get. But in Linux you can't enable HDR for games only - has to be enabled in KDE and game
Oh for me hdr looks amazing, but i have a kick ass monitor so yeh
LG ultragear 34gp950g, dont think its sold anymore but yeh
Also had hdr enabled for kde as a whole. Just couldn't get the option in drg but i get that problem on windows so isnt a linux problem
Oh, I have the sucessor to that one. Its a great panel.
has firefox been acting up from anuone?
Today its frozen, like you can't do anything
Yeah it's still broken
Crashes a lot but you can open and use it briefly
suposedly its launching on x11 mode, and it's been working for a couple of days so far like that, but today it's just refusing to do anything, not even crashing just sitting there frozen
werid
yes I can confirm I logged back into the updated tree from last night and it worked fine
so yes prob some hw diff I guess
Okay, i'm giving testing a spin again.
going to try the latest update and see how firefox behaves
:EvilSchemeOcelot:
the one from last night it opens but from there it was useless lol
okay firefox works for me now afte the udpate
there was some weird laggy behaviour at the login screen. Not sure if it ever got my pw to login or what as I did not see it input visually
but probably a one-off
will reboot and see if that login thing always happens or one-off
okay next login worked fine
it feels to me that it is that first time u boot a tree that is critical when u boot a tree up. I could be wrong but mearly feeding back as I see it which could be utterly useless 🙂
just got a flatpak update - maybe fixed?
doesnt crash in videos anymore
https://github.com/ublue-os/bazzite/issues/1271 - seems the KDE freeze issue is drivers and KDE / Nvidia need to fix, but it can be mitigated by not using the "dodge windows" or hide behaviour of task bar
and the app lagging is a KDE (?) issue they are addressing with triple buffering being used
Triple buffering was part of 6.1, that should be there already
I think the dude was saying it's the use of triple buffering that's the issue but idk it's not a big deal for me
I see
Well, it's getting there
I might push this to main sooner but with the X11 session present since we're still working out the kinks upstream
So long as these black screen bugs go away
A decent fallback strategy until nvidia 560 releases and hopefully fixes all the edge cases or until Fedora 41 nukes X11. I guess we'll see which happens first 😂
Okay, I'm back in, lets see how we do!
Can confirm that that firefox video crashes.
Did you update flatpaks? or just switch to test branch?
Ah if Firefox fixed their issue, would the temporary fix need to be reverted so it runs on Wayland properly?
yep
you can remove the environment variable in flatseal
Will test after next update
Let discover run an update.
Going to try the ujust now.
Oh man, it fixed the vrr.
- cannot install both gstreamer1-1.24.5-1.fc40.x86_64 from updates and gstreamer1-1.24.4-1.fc40.x86_64 from @System
- cannot install both gstreamer1-1.22.9-1.fc40.x86_64 from fedora and gstreamer1-1.24.4-1.fc40.x86_64 from @System
F
It's packaged drift, it'll be fixed later
God, i think at this point id take a hardware swap for a 7900xtx for my gpu at this point 😄 nvidia are a proper pia for linux users
Pretty much the nail in the coffin for me. I only settled on Nvidia last time because I had no pull either way and it's what I could get for MSRP during the shortage
The AMD guys admit they have issues too but I think just the mentality that you're not relying on proprietary drivers is a relief
I personally wont be uprgading for 2 gens at least, so i got a while left with this card, its a bit annoying
updated gnome today and I'm stuck with X11 again, any thoughts on this?
I was doing some testing on the no-nvidia image earlier to try NVK, there I was always on Wayland
Did an update just drop?
Not since yesterday I guess - current build failed
Huh, saw a notification.
Silverblue build completed
Seems like fixed
@1/4 Life is this normal ?
If you're on testing, yes
No X11
It's up to Nvidia to finish updating their control panel, they're in the process of that
they working on linux ?
Yes
oh
Green with envy is likely dead, I've removed it from the portal
Something else will take its place
and about optimus manager do i have to install it ?
my laptop has no mux switch
where do i install LACT can't find it in bazzite portal
You can use supergfxctl to manage Optimus
There's an ujust script to install LACT
another day, another question as to why kde keeps resuming apps.
this is not working?
I had to toggle it off and on again.
So far only show stopper I've found is firefox.
LACT is for AMD
I do use bazzite on god win mini and my intel laptop
But yeah i load lact on win mini but it can’t be use on 8840u
massive thank you for putting out the testing branch again. I will just enjoy as I have been unless anything I need to do
Do the latest changes need to be tested for KDE? I think the last test build only completed for the gnome "main" variant
I'll ping here when that's built
Upstream didn't build 40 last night so version drift is still a problem
I can't get Firefox working on the build I have where the temp fix is still applied. I tried tweaking the variables but couldn't get it to stop crashing despite the flatpak update
I think everything else is more or less the same - just the new logic of copying over nvidia-modeset to /usr
And I don't really understand the latest commit. I might end up figuring out how ublue works
Newest commit is just building initramfs dead last
No functional change from how it was done previously, just saves possible future headache
Do we have an ETA for the firefox fix?
That's entirely up to Mozilla
They haven't promised anything
So what's the plan for merging this to stable with that in mind?
Tbd
Might merge it with the X11 session still present
Might wait longer
The beta driver works but is not great, for example idle power draw is through the roof, Firefox not working and some degraded performance (expected per nvidia engineers in this driver)
Imo I wouldn't ship it till stable
I might ship stable if you default it to x11. But its a hard maybe.
I think it would be a good idea to keep x11 for a bit alongside wayland changes until like the issues of logging in etc are resolved.
Obv wayland seems to be the future but many using bazzite will just want it to work from the set go and they will be novices if I understand the userbase at all. I think it would attract a lot of people to the OS (not that I know/think that to be the aim or whatever).
I know in another discord sm1 moved away just for the reason they tried wayland to start with without knowing it was supposed to be buggy atm for nvidia users.
THough people may also expect users with a bit more knowledge and research before they jump on. I dunno :PU_PeepoSmokeH:
Kill x11
My 2 cents
if I can without breaking something as basic as firefox
I will
I would say the Firefox issue is a deal breaker.
Agreed
Seconded. It just sucks as wayland is SO much better than x11 for me for EVERYTHING ELSE.
I'm debating rebasing back to stable, but he VRR is just so... nice to have.
This is why I use several browsers. Guess I'm on a chromium based one for a little bit
Latest build is done
running upgrade
Hey.... firefox isn't crashing.
Firefox is stable.
no updates on that issue, no traction
if it's working for you now that's great, but no way is it fixed proper
still 100% crashing on Wayland and corruptions on XWayland for me
Latest testing is now also zstd compressed
Updates should be considerably smaller going forward
Is the zstd compression just on the testing branches for now or also in stable?
testing only atm
Updated just now - KDE Main testing version
Boots fine, no new behaviours observed.
Hopefully we benefit from fedora updating to KDE 6.1.1 as I see bug fixes
Looking good!
NVIDIA 555.58 Stable Linux Driver Brings Wayland Explicit Sync, GSP...
The NVIDIA 555.58 Linux driver has debuted this morning as the first stable version in the R555 driver series
as for the changelog from current beta:
who tf knows
to be noted my firefox was working since u did the firefox being able to launch fix. It can crash from time to time so I believe that user would eventually experience that if he used it enough.
Installed testing on laptop with intel igpu and 1050 - works great
Wee
Was meant to be wew but wee works too ig
firefox patch is in progress now too
soon s that's live I'll merge this since 555 is now stable
Was a good run Microsoft, but windows is dead
Gg
the irony when people say this is that kyle is a ms engineer
shiz be funny
Further irony he runs what's probably going to be one of the biggest projects that draws people over from windows
But still, the big bucks are in enterprise and it's not going anywhere anytime soon
I dunno if that is one in the end. I think MS ultimatley targets enterprise with the stuff we have seen recently
and fairly sure ms use linux
I work with a few tech companies and looking at their annual reports, enterprise just makes up so much more of their revenue than retail. They'll take both but b2b is the real revenue driver
Is the advantage there reduced screen tearing?
And better frame to frame timing.
VRR basically makes inconsistent frametime a non-issue as long as you are in the window your monitor can handle
but it's really hard to work around using on the 555 branch right now
why would you want to work around it? Do you mean disable it?
no i mean it's buggy
Latest test build has the black screen bug:
Logged in, took a long time to get to desktop, ran fastfetch, KDE crashed to lock screen, logged in again, no video output
Switching through ttys eventually got me back into DE
black screen bug was a failure to load from boot
whatever you ran into is totally different, sounds like a Kwin crash
Okay that's good
Its been flawless for me, but YMMV.
That said, I think its mostly because i use DP and not any of the HDMI impl.
Okay, today's build is oddly suttery with VRR set to automatic. Set to always and its buttery smooht.
Okay, it was fun but today is been crashing left and right. back to stable I go for a while.
Just got this after switching to :testing - black screen, bazzite doesn’t appear to boot.
This thread has gotten pretty long; is there a resolution?
black screen bug should be fixed in the latest image
/shrug - I just (last 20 minutes) rebase to :testing, and not getting a boot.
Any work around to rebase again, back to stable? CTRL->ALT->F4 doesn’t pull up term, so I’m assuming it didn’t boot os at all
It finally did, my keyboard is just dumb and wanted a fn butting for f#
Rebasing to stable now, may try testing again in a while to see if same results
Well - that’s fun. Stable appears to do the same…
I can hold ctrl/alt/f4 to get a terminal and login with my user/pw.
Almost seems like maybe KDE/Lock Screen just isn’t starting?
https://paste.centos.org/view/d8d31d93
Any thoughts?
https://paste.centos.org/view/d0274940
did you mean to be on bazzite-deck?
no nvidia drivers there
Negative - on desktop
Ahhh - I rebased to deck
Lol@me
rpm-ostree rebase ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-nvidia:stable
happens lolDoesn't deck images boot directly to gaming mode? It's not going to display at all on Nvidia
I was like wtf
Yeah I’m just a big old dumb
it also looks like you tested the deck testing image. Probably worth retrying that test again
Yeah I had just done testing on my deck, went to desktop and my fingers just typed what it wanted. Then I used up to change from testing->stable
100% user error
At the other side, I've being testing a bit with non-nvidia images and NVK seems actually fine to use overall. Ofc I noticed it's way slower and bad frame pacing, but with frame cap on light games it's acceptable, and yes Firefox doesn't crash
I also played around with NVK a bit, it's decent if you mostly play indie games
Maybe we're not too far from daily driving it :D (maybe just one more decade)
I suspect it'll be performant within the year
If so it really is going to be amazing
I tried nvk on the testing image but could only get one screen out of two and just 1024 era
So after accounting for being an idiot, I was able to get :testing to load.
However - I’m having some lag/cursor stuttering. Any idea what could be causing that?
Looks like the cursor location doesn’t match where it actually is either - weird
Idk why this is happening, but may be an argument for keeping x11? (I don’t see x11 drop-down on testing)
Plasma?
KDE? Yep
More than one screen? I got that mouse lag on the 60hz screen on plasma, but not on the 144 one
Don't know how to troubleshot that
2 screen, both 60hz 4K, both appear to have it
For me it feels like they are running at half refresh rate
I don't get that on gnome so I'm betting on a kwin bug?
GNOME - Last testing got me stuck in black screen too, rollbacked to yesterday and it's working fine
Do you have Wayland option in GDM?
Tried 555.58 and didnt have the gear option to change
so I was stuck in X11 and rollbacked
Have used the testing branch a couple of days without issues and now wayland is completely gone. The option at the login screen is gone and I can only login with x11
Yep same issue
They are aware and working on it
was an update to the nvidia driver this morning
will be fixed up soon
Thanks Kyle
Nope, literally nothing just black screen for me
Damn it, now I want to try on to testing again.
can confirm new build solved the issue, thanks!
anyone coming from rebase, be sure to perform
ujust update to update the flatpaksKDE guys, do we have 6.1.1 yet? It made it to Fedora already
Do you get Wayland in gdm now?
I do, I'm in Wayland now
So, still getting black screen after login, is there something I can do to fix it?
KDE
CPU: AMD 5800x3d
GPU: Nvidia 3080
RAM: 32GB 3200mhz Corsair
Edit: nvm, tty works at login screen
The anser is yes - KDE Plasma 6.1.1
Aware this is a different distro then bazzite as ive switched to endeavour, but just got the update through on a yay update, no black screen, no issues with firefox, not sure if maybe this might help any one or its totally useless, havent tried gaming yet however, only just got the update through
firefox also seems to be all good over here
What version of Firefox is it? Maybe they have merged the fixes now
I'm not having any black screen issues anymore in Bazzite with the latest driver. New KDE stuff seems to have made big improvements too
So 🤞
Same as flathub
On the main chat someone said it might be running under xwayland on endeavouros which is the work around but not full fix
Ah okay, not sure how i would check that
Ahhh cool so yeh they are using a workaround
See if they dropped it into /etc/environment by default
They don't mention doing it
Oh okay, ill check shortly and put my env vars up if its there
I can't find anything in their GitHub suggesting they applied a fix.
If you watch a video in full screen from Firefox does it work?
Lemme try two secs
Oh no, i may very well have just lucked out on a reboot earlier, getting the dreaded single white line after entering password
Whyyy
Yeh i jynxed it. Back to gnome i go 😎
Stop tempting me with GNOME. I like KDE's smoothness.
its nice and smooth as a black screen 😄
im joking of course, just needs more time in the oven
Yep. It was testing before dawntrail released and it was awesome to have working VRR, something that did not work in windows.
Just make sure everything is set up correctly from endeavour
Yeh im almost certain it is, its the same issues i had with bazzite during testing
How had is it to rebase over to gnome?
I mean, I know its suggested to do a full wipe but......
😄 i just do a full wipe every time
It's not too bad, you have to sign into everything again, need to nuke a bunch of flatpaks. Safest way is to make a new user account and test the different DEs that way.
Desktop working in PlasmaX11 but not on default (Wayland I guess). Any workaround?
What I did was create a new user upon logging into gnome, keep it default, then log in with my main user, and that seemed to fix my issues
You will see a white bar at the top left, that means XWaylandVideoBridge is running, it's not a bug. Although I wish there was a way to disable it autorruning since it doesn't even seem to work and most of my apps are native Wayland anyway
Can I download the testing iso? Or do I have to download normal iso and rebase?
I don't think there are testing isos available
rebasing is kinda trivial though.
yes just rebase
there are iso's you see but easy to just rebase
and pin the tree ur using
I think u can pickup iso here though but have no idea if people should use them or not
lol
https://github.com/ublue-os/bazzite/actions/runs/9730352669
yeah no prob, I just rebased no issues so far
other than firefox crashing like crazy haha
Is there a tracking issue for this somewhere on github? Plasma Wayland consistently crashes on startup, and Plasma (X11)'s compositor crashes consistently on start.
I rolled back to 20240625 for now
I'm not exactly sure where to file this issue
Okay so, its come to light exactly what my original issue was, in the 700 odd messages in this thread. @Kyle Gospo @wolfyreload
https://bbs.archlinux.org/viewtopic.php?id=297236
Theres a bug in KDE with HDR being enabled and then rebooting with the new nvidia drivers, there is a fix workaround as stated above and heres the bug tracker
https://bugs.kde.org/show_bug.cgi?id=488941
Aware this is on Arch linux, but may also explain the previous time on bazzite i had a similar issue, i do remember enabling hdr and not being able to ctrl alt and f4, with a single line at the top left. Its the exact same behaviour in EndeavourOS
That explains why I'm not having issues. My hardware doesn't support HDR
Yep!
Ah yeah I flagged this earlier but thought it was fixed
Just have to wait on KDE to fix it up
Yeh its definitely not yet, at least i have not pulled any updates yet today, patch day for me is on Thursdays
Looks to happen on Nvidia drivers 550 too so feels more a KDE issue than anything else
Oh its definitely a KDE issue at this point, i just couldnt see it on previous drivers as id always us x11 on there, due to flickering 😄
So no wonder i never noticed it being hdr as the issue
But at least if it's a KDE Wayland issue they should hopefully fix it.
I don't remember using HDR because my display contrast is trash, but may worth trying it too
HDR is a mess in general.
I will be getting a HDR display soon
there is an absolutre bargain hdr1000 display atm for like $280
I know this is not the rifght place but I think that is like too important to miss out on depending on the person
lol
Im curious, whats the display?
mwahahaha
let me get it up again
mate showed me and I Was like why was the title not hdr1000 lol
aoc q27g3xmn
I cannot get it in the UK till August. I dnt know if cos out of stock or what but that will be a 2nd monitor then going for something premium af as the main one. NOt bad for a second monitor though. Hardware unboxed did a vid on it
main weakness is latency but not bad for single player games imo
I am waiting for a true black hdr 400 oled monitor to become available in the uk as well
glossy panel at last
Anyway leave it at that lol
Rip appears to be out of stock for me, oh well
same here
not out yet in the UK afaik . America gets it all first
Yeah I noticed UK monitor market is shockingly bad
We get the scraps
I mean im in US and its out of stock
honestly I got excited thinking all these changes happened in the monitor market since I last looked. My debit card was ready to go and I got ripped
fairs. Probably a sign it is well below the price it should be lol
Yeah but I will def keep it on my radar
yes that and another I am keeping on my radar as I want 2 monitors
I dunno how bad oled really is for working as my 2nd monitor will be that which seems risky lol
given the text clarity issues