Page MenuHomeSolus

Screen resolution set to 1280x800 on one of 2 identical 4k monitors
Open, Needs More InfoPublic

Description

I posted this to GitHub first: https://github.com/solus-project/budgie-desktop/issues/1776

Description

I have 2 4k monitors (same brand, same model).
For the last week and a half or so, whenever I boot the system, one of the screens is stuck at 1280x800 while the other one is set to 3840x2160. Weirdly enough, the panel also switches screens.

Budgie version

10.5

Operating system

Solus 4.0

Steps to reproduce the issue

I have no idea. I don't know if I'm the only one having this issue.

My monitors are LG 27MU67-B

Actual result

see description

Expected result

Both monitors are set to 3840x2160

Additional information

I found this in the journal:

budgie-wm[1254]: Failed to use stored monitor configuration: Invalid mode 3840x2160 (59,996624) for monitor 'GSM LG Ultra HD'

xrandr:

Screen 0: minimum 320 x 200, current 5120 x 2160, maximum 16384 x 16384
DisplayPort-0 connected primary 1280x800+0+0 (normal left inverted right x axis y axis) 600mm x 340mm
   1280x800      59.81* 
   1152x864      59.97  
   1280x720      60.00    59.94  
   1024x768      60.00  
   800x600       60.32  
   720x480       60.00    59.94  
   640x480       60.00    59.94  
DisplayPort-1 connected 3840x2160+1280+0 (normal left inverted right x axis y axis) 600mm x 340mm
   3840x2160     60.00*+  30.00  
   1920x1200     60.00  
   1920x1080     60.00    59.94  
   1600x1200     60.00  
   1680x1050     60.00  
   1600x900      60.00  
   1280x1024     60.02  
   1440x900      60.00  
   1280x800      59.81  
   1152x864      59.97  
   1280x720      60.00    59.94  
   1024x768      60.00  
   800x600       60.32  
   720x480       60.00    59.94  
   640x480       60.00    59.94  
HDMI-A-0 disconnected (normal left inverted right x axis y axis)
HDMI-A-1 disconnected (normal left inverted right x axis y axis)
DVI-D-0 disconnected (normal left inverted right x axis y axis)

dmesg doesn't show anything suspicious or unusual.

The issue resolved itself after the latest update

Girtablulu closed this task as Resolved.Apr 7 2019, 8:08 AM
Girtablulu claimed this task.
Girtablulu added a subscriber: Girtablulu.

So maybe a regression between kernels

Gaming4LifeDE reopened this task as Open.Apr 8 2019, 12:11 PM

The issue reappeared a few reboots after the update.

Girtablulu edited projects, added Software; removed Lacks Project.Apr 10 2019, 8:57 AM

I noticed that if you lock your screen and wait for a few minutes after the screen turns off, it works again until the next reboot

DataDrake edited projects, added Hardware; removed Software.Tue, Apr 30, 2:00 PM
DataDrake triaged this task as Needs More Info priority.
DataDrake added a subscriber: DataDrake.

What GPU?