hmm I think I should use my intellij in distrobox
hmm I think I should use my intellij in distrobox
KIt's really similar to Beatmania but subjectively, its a much richer experience if the patterns are designed correctly.
KDue to differences in turntable spacing and the inclusion of a pedal
Hwhy tho
GWhat if I can’t get to a terminal after logging into a Wayland session lol
Hintellij works perfectly fine when installed with jetbrains toolbox
GI get the login screen, select Wayland session, then login chime and just black screen
Gctrl+alt+f3 etc even doesn’t display CLI
Moh I forgot they have toolbox, mostly just install everything on flatpak nowadays
GOn 550 drivers I could login to Wayland session but I had flickering screen (because nvidia). I was hoping 555 drivers would remedy but now I just get a black screen
Hthat's really odd
GIf I ctrl+alt+f3 before login I do get a CLI I can login to
ZI think we have x11 still in bazzite-nvidia
GWe do, I was hoping to use Wayland finally
Kyou do
KI decided to drop it w/ 41 instead of now
Kbecause there's still a couple wayland gremlins
ZMaybe you can login x11 and from there disable HDR ?
GAlso even on X11 I get blank screens unless my monitors are in HDR mode, which is especially odd since there’s no option to even enable HDR
Ktry the command on X11?
GThat’s what I was trying but in an X11 session kscreen just days HDR is unsupported
KI'm trying to search where kscreen-doctor is in the source
KAnyone knows?
ZMmm, another option is login but not with the login manager, but from a tty
GI think that’s what I’m trying right now and I’m getting kscreen errors (maybe because no KDE initialized yet?)
ZGitHub
KDE's screen management software. Contribute to KDE/libkscreen development by creating an account on GitHub.
Gkscreen-doctor output.DP-2.hdr.disable qt.pa.xcb: could not connect to display
qt-gpa-plugin: From 6.5.0, xcb cursora or libxcb-cursorD ts needed to load the Qt xcb platform plugin. gt.qpa.plugin: Could not load the ut platform plugin "xch" in " Even thaugh it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
Peven thaugh
ZOnly thing I can think it's modifying manually whatever config file plasma uses to store the HDR param
KYeah I meant that, to see where the config files are
GI’m not even 100% sure that’s what’s causing my issue
ZA lot of ppl were getting black screens with plasma, maybe something to do with config idk
ZSome reported removing certain config files fixed the issue(?) though I would do that as a last measure,
Goh thanks, that's a massive thread it might take me awhile to check out
Kcheck if you have libxcb-cursor package
Galso at this point I'm fine with leaving HDR disabled, I'd just like to get off of X11
ZStrongly inclined to this one Black screen bug with bazzite-nvidia:testing build for explicit sync
Krm ~/.config/kwinoutputconfig.jsoneasy
Gnot sure best way to do that but rpm -qa | grep libxcb returns a few packages but no libxcb-cursor
ZYeah same behavior almost
KOh, it seems to be in ~/config/kwinoutputconfig.json
Kcheck if highDynamicRange is set to true in the corresponding output
Gbrb rebooting after doing this
Kalso turn off
KwideColorGamut
KI wouldn't do that
G
Kjust change the booleans
K
