![]() ![]() ![]() (ran the system check software from Steam and generated a multipage report). Then I tried to contact tech support for more help. I have also made sure that my display is set to "Extended". and I have seen nothing but red in my headset since. Then the camera shifted up to an odd angle and froze. I was able to see the default "VR room" for about 60 seconds. When I doing my initial setup of the sensors and controllers. I have reinstalled the software as well for Steam, SteamVR, etc. I updated my GPU drivers (and everything else!) and I have enabled Direct Mode it will still not work and I cannot see or do any VR at all. " Well, I have gone the board and help menus and have done all that was suggested. You'll need this to be fullscreen for SteamVR to work correctly. I keep getting the message that my " Compositor is not full screen. I am trying to install my new HTV Vive on my brand new highend Asus Zephyrus laptop. (-) NVIDIA(GPU-0): DFP-4: Internal DisplayPort Looking at the Xorg.0.log I am seeing the screen disconnect. This bug should be submitted to xorg not kscreen I guess.ĬPU: Intel® Core™ i5-3570 CPU 3.40GHz × 4īase Sys: Debian GNU/Linux 9 (stretch) 64-bit I don't know what dpms at startup does but I can live with this bug for now as all it does, shuffles my windows all over the place and cairo dock can be reconfigured quickly. I believe this whole thing is down to timing when xorg is expecting all screens be ready to accept signal and reply with "Ready" signal but first screen responds faster and second may not respond in time and xorg believes that screen is off or not available so adjust config accordingly. (Cairo-dock is showing on left screen in the middle when mouse over right screen's edge etc.). Previous configuration was fine as screens came up quite swiftly but now my 4k screen takes longer to show up and this messes up whole config. Now I have upgraded screen and am using two DP where one screen is 4k and other is using DP2HDMI(same screen as used before). I used to use two screens with outputs on VGA and DP(with converter to HDMI as monitor has only HDMI input) and this worked fine as long as I used it. Sleep 10 & qdbus 5 /kded kscreen & qdbus 5 /kded kscreen Kscreen.kded: "The name was not provided by any. kded5.unloadMod ule kscreen & qdbus 5 /kded org.kde. When I reload kscreen in KDE settings or from command line - suspend on lid close is working as expected.Īdding this script to KDE autostart works for me as an workaround of the issue: I am not very familiar with all that stuff, but it looks like kscreen daemon is starting too soon and there's no power devil yet, so kscreen deamon doesn't have a reference to powerdevil "aboutToSuspend" signal or something.Īnyway. com/KDE/ kscreen/ blob/master/ kded/device. Solid.PowerMana gement was not provided by any. Kscreen.kded: PowerDevil SuspendSession action not available! cpp#L125)Īnd that is because of other error during kscreen daemon start: com/KDE/ kscreen/ blob/master/ kded/daemon. The thing is that function which is responsible for stopping the timer is not triggering. The thing is that it should not trigger that function on timeout, because my system is going to suspend and counting down should be stopped. Then, after resume from suspend, position of second monitor is set to (0,0) and is overlaying the primary one. Which is causing turning off the screen and saving info about that in new config. "Lid closed without system going to suspend -> turning off the screen" "Lid closed, waiting to see if the computer goes to sleep." I noticed that in my journalctl that during lid close kscreen.kded is sending My second screen position was resetting and overlaying primary laptop screen after resuming from suspend. Mine was more related to suspend on lid close, but maybe you'll find something useful. Everything goes back to normal until the next time the screen goes to sleep. My current work around is after unlocking the desktop log out & log back in. Plasma panel should be on the HDMI screen & not the laptop screen. My display settings should be used where HDMI is primary & laptop is secondary. HDMI screen doesn't have desktop background settings nor panel, nor right click functions. HDMI is no longer primary, laptop screen becomes primary. This happens every time, so yes it is reproducible.ġ. Weird thing is, it does use the screen positioning portion of the config & the resolution, just moves bar to other screen & HDMI screen is just black. It goes to using laptop display as main display & HDMI as a secondary display. If I leave my computer until the desktop locks & then the screen goes black, when I log back in I still have dual monitors.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |