Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Settings - Display: wrong resolution selected #205

Open
tuananh opened this issue Mar 19, 2024 · 13 comments
Open

Settings - Display: wrong resolution selected #205

tuananh opened this issue Mar 19, 2024 · 13 comments
Milestone
alpha 7

Comments

@tuananh
Copy link

tuananh commented Mar 19, 2024 •
edited
Loading

My monitor resolution is 5120x1440 and it shows that resolution (5120x1440) is selected. But it feels like it's 3840x1080.

when i tried to select 3840x1080, it automatically select 5120x1440 back.

I'm not sure how I can provide more information on this.
@tuananh
Copy link
Author

tuananh commented Mar 19, 2024

I install cosmic from 22.04. Not sure if that make any difference.

@Drakulix
Copy link
Member

I would be very confused, if actually runs at a lower resolution, but lets see.

First could you run cosmic-randr and see, if that also reports 5120x1440?
If it does, could you run drm_info please (you might need to install that) from a terminal in cosmic and post the output?

@tuananh
Copy link
Author

tuananh commented Mar 19, 2024 •
edited
Loading

cosmic-randr indeed reported that it's using the lower resolution

cosmic-randr list
DP-1 (enabled)
  Model: 
  Physical Size: 1190 x 340 mm
  Position: 0,0
  Scale: 100%
  Transform: normal
  Modes:
    3840x1080 @ 119.974 Hz (current) (preferred)
    5120x1440 @ 119.970 Hz
    5120x1440 @  99.996 Hz
    5120x1440 @  59.977 Hz
    3840x1080 @  99.956 Hz
    3840x1080 @  59.968 Hz
    2560x1440 @  59.951 Hz
    2560x1080 @ 119.881 Hz
    2560x1080 @ 100.00 Hz
    2560x1080 @  60.00 Hz
    2560x1080 @  59.939 Hz
    1920x1080 @ 119.879 Hz
    1920x1080 @ 100.00 Hz
    1920x1080 @  60.00 Hz
    1920x1080 @  59.939 Hz
    1680x1050 @  59.954 Hz

I change it with the command line and it works now

cosmic-randr mode DP-1 5120 1440

but in cosmic settings, it's now showing the lower resolution as selected.

I'm guessing its sth to do with the index when displaying?

summary:

  • settings show 5120x1440 but it's indeed 3840x1080.
  • changing with cosmic-randr to 5120x1440 and settings is now showing 3840x1080

@Drakulix
Copy link
Member

I'm guessing its sth to do with the index when displaying?

Not unlikely, it might be thrown of by the order of the resolutions reported, with the one being reported first and preferred by the display, not being the one with the maximum size.

Definitely a cosmic-settings bug then, cc @mmstick

@WatchMkr WatchMkr moved this to Alpha Bugs ToDo in COSMIC Epoch 1 May 7, 2024
@WatchMkr WatchMkr added this to the alpha 1 milestone May 7, 2024
@WatchMkr WatchMkr moved this from Alpha Bugs ToDo to Alpha 2 in COSMIC Epoch 1 May 25, 2024
@WatchMkr WatchMkr modified the milestones: alpha 1, alpha 2 May 25, 2024
@mmstick
Copy link
Member

mmstick commented May 28, 2024

Is this still an issue?

@curiousercreative
Copy link
Contributor

Not sure if it's the same issue, but I just encountered similar. I have a laptop in clamshell with a 5120x2160 monitor connected. After making some changes, I was unable to return to full resolution. Approximate reproduction steps:

  1. With display settings open (5120x2160 @ 125% @ 72hz selected)
  2. Change scaling to 100%
    AR/ER: scaling adjusts immediately and prompt to confirm seting
  3. Change scaling back to 125%
    AR/ER: scaling adjusts immediately and prompt to confirm seting
  4. Change resolution to 3440x1440 (or some lower resolution)
    AR/ER: monitor takes a moment to output display, prompt to confirm setting
  5. Change resolution back to 5120x2160
    ER: monitor takes a moment to output display, prompt to confirm setting
    AR: no change, immediately prompted to confirm settings
  6. Change resolution to 1920x1080
    AR/ER: monitor takes a moment to output display, prompt to confirm setting
  7. Change resolution back to 5120x2160
    ER: monitor takes a moment to output display, prompt to confirm setting
    AR: no change, immediately prompted to confirm settings

@DW8Reaper
Copy link

@mmstick I think it is still a valid issue I have the same problem (though my resolution is 5120x1440) and that is the preferred resolution in randr but when I select it in display settings nothing happens (I attached a recording).

my system is a Thelio Mira (intel) everything is standard except the graphics card which I added:

description: VGA compatible controller
product: Navi 32 [Radeon RX 7700 XT / 7800 XT]
vendor: Advanced Micro Devices, Inc. [AMD/ATI]
physical id: 0
bus info: pci@0000:03:00.0
logical name: /dev/fb0
version: c8
width: 64 bits
clock: 33MHz
capabilities: vga_controller bus_master cap_list rom fb
configuration: depth=32 driver=amdgpu latency=0 resolution=3840,2160

cosmic-rander reports:
screenshot-2024-08-20-13-33-05

My app versions (not sure which are useful):

➜  ~ apt info cosmic-randr
Package: cosmic-randr
Version: 0.1.0~1722404448~22.04~71fabbb
Priority: optional
Section: utils
Maintainer: Michael Murphy <[email protected]>
Installed-Size: 1,424 kB
Depends: libc6 (>= 2.34), libgcc-s1 (>= 4.2)
Homepage: https://github.com/pop-os/cosmic-randr
Download-Size: 521 kB
APT-Manual-Installed: no
APT-Sources: http://apt.pop-os.org/release jammy/main amd64 Packages
Description: Display and configure wayland display outputs
 Display and configure wayland display outputs

➜  ~ apt info cosmic-comp
Package: cosmic-comp
Version: 0.1~1723813191~22.04~a3c8111
Priority: optional
Section: x11
Maintainer: Victoria Brekenfeld <[email protected]>
Installed-Size: 22.7 MB
Depends: libc6 (>= 2.35), libgbm1 (>= 21.3.0~rc1), libgcc-s1 (>= 4.2), libinput10 (>= 1.19.1), libpixman-1-0 (>= 0.30.0), libseat1 (>= 0.5.0), libudev1 (>= 183), libxkbcommon0 (>= 0.5.0), libegl1, libwayland-server0
Recommends: cosmic-session, libgl1-mesa-dri
Homepage: https://github.com/pop-os/cosmic-comp
Download-Size: 7,360 kB
APT-Manual-Installed: no
APT-Sources: http://apt.pop-os.org/release jammy/main amd64 Packages
Description: Wayland compositor of pop-os cosmic shell

➜  ~ apt info cosmic-settings
Package: cosmic-settings
Version: 0.1.0~1723893909~22.04~83a4296
Priority: optional
Section: utils
Maintainer: Michael Murphy <[email protected]>
Installed-Size: 60.7 MB
Depends: libc6 (>= 2.35), libgcc-s1 (>= 4.2), libpipewire-0.3-0 (>= 0.3.1), libpulse0 (>= 0.99.4), libudev1 (>= 183), libxkbcommon0 (>= 0.5.0), accountsservice, cosmic-randr, gettext, iso-codes, xkb-data
Recommends: adw-gtk3
Homepage: https://github.com/pop-os/cosmic-settings
Download-Size: 10.9 MB
APT-Manual-Installed: no
APT-Sources: http://apt.pop-os.org/release jammy/main amd64 Packages
Description: Settings application for the COSMIC desktop environment
 Settings application for the COSMIC desktop environment

there doesn't seem to be anything useful in my journalctl log:

Aug 20 09:49:12 desktop sudo[47470]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000)
Aug 20 09:49:12 desktop sudo[47470]:  *** : TTY=pts/0 ; PWD=/home/*** ; USER=root ; COMMAND=/usr/bin/journalctl -r
Aug 20 09:49:08 desktop kernel: [UFW BLOCK] IN=enp9s0 OUT= MAC=*** SRC=fe80:0000:0000:0000:7a9a:18ff:fe9f:6185 DST=ff02:0000:0000:0000:0000:0000:0000:0001 LEN=205 TC=0 HOPLIMIT=1 FLOWLBL=223633 PROTO=UDP SPT=5678 DPT=5678 LEN=165
Aug 20 09:48:56 desktop systemd[1]: Configuration file /run/systemd/system/netplan-ovs-cleanup.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.
Aug 20 09:48:13 desktop cosmic-comp[45093]: Failed to apply config. Resetting
Aug 20 09:48:08 desktop kernel: [UFW BLOCK] IN=enp9s0 OUT= MAC=*** SRC=fe80:0000:0000:0000:7a9a:18ff:fe9f:6185 DST=ff02:0000:0000:0000:0000:0000:0000:0001 LEN=205 TC=0 HOPLIMIT=1 FLOWLBL=223633 PROTO=UDP SPT=5678 DPT=5678 LEN=165
Aug 20 09:48:04 desktop cosmic-comp[45093]: Failed to apply config. Resetting
Aug 20 09:47:56 desktop systemd[1]: Configuration file /run/systemd/system/netplan-ovs-cleanup.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.
Aug 20 09:47:51 desktop cosmic-comp[45093]: Failed to apply config. Resetting
Aug 20 09:47:41 desktop systemd[36399]: Started Application launched by COSMIC.
Aug 20 09:47:38 desktop systemd[36399]: app-cosmic-com.system76.CosmicSettings-46785.scope: Consumed 4.133s CPU time.
Aug 20 09:47:20 desktop cosmic-comp[45093]: [GL] GL_INVALID_VALUE in glTexSubImage2D(xoffset 0 + width 24 > 10)
Aug 20 09:47:20 desktop cosmic-comp[45093]: [GL] GL_INVALID_VALUE in glTexSubImage2D(xoffset 0 + width 24 > 10)
Aug 20 09:47:19 desktop dbus-broker[2419]: A security policy denied :1.685 to send method call /org/freedesktop/NetworkManager/Settings:org.freedesktop.NetworkManager.Settings.LoadConnections to org.freedesktop.NetworkManager.
Aug 20 09:47:19 desktop dbus-broker[2419]: A security policy denied :1.689 to send method call /org/freedesktop/NetworkManager/Settings:org.freedesktop.NetworkManager.Settings.LoadConnections to org.freedesktop.NetworkManager.
Aug 20 09:47:13 desktop kernel: amdgpu 0000:03:00.0: [drm] enabling link 2 failed: 15
Aug 20 09:47:11 desktop flatpak[45945]: [56:0820/094711.837143:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 3 times!
Aug 20 09:47:08 desktop kernel: [UFW BLOCK] IN=enp9s0 OUT= MAC=*** SRC=fe80:0000:0000:0000:7a9a:18ff:fe9f:6185 DST=ff02:0000:0000:0000:0000:0000:0000:0001 LEN=205 TC=0 HOPLIMIT=1 FLOWLBL=223633 PROTO=UDP SPT=5678 DPT=5678 LEN=165
Aug 20 09:47:02 desktop systemd[36399]: Started Application launched by COSMIC.
Aug 20 09:46:56 desktop systemd[1]: Configuration file /run/systemd/system/netplan-ovs-cleanup.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.
Aug 20 09:46:49 desktop systemd[1]: systemd-localed.service: Deactivated successfully.
Aug 20 09:46:30 desktop systemd[36399]: Started Portal service (GNOME implementation).
Aug 20 09:46:30 desktop systemd[36399]: Starting Portal service (GNOME implementation)...
Aug 20 09:46:30 desktop systemd[36399]: Failed to start Application launched by COSMIC.
Aug 20 09:46:30 desktop systemd[36399]: app-cosmic-com.system76.CosmicTerm-46186.scope: Failed with result 'resources'.
Aug 20 09:46:30 desktop systemd[36399]: app-cosmic-com.system76.CosmicTerm-46186.scope: Failed to add PIDs to scope's control group: No such process
Aug 20 09:46:30 desktop systemd[36399]: app-cosmic-com.system76.CosmicTerm-46186.scope: Couldn't move process 46186 to requested cgroup '/user.slice/user-1000.slice/[email protected]/app.slice/app-cosmic-com.system76.CosmicTerm-46186.scope': No such process
Aug 20 09:46:21 desktop flatpak[45945]: [56:0820/094621.984954:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 2 times!
Aug 20 09:46:21 desktop flatpak[45945]: [56:0820/094621.982186:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 1 times!
Aug 20 09:46:20 desktop systemd[36399]: dbus-:[email protected]: Failed with result 'exit-code'.
Aug 20 09:46:20 desktop systemd[36399]: dbus-:[email protected]: Main process exited, code=exited, status=1/FAILURE
Aug 20 09:46:20 desktop ibus-portal[46085]: Not connected to the ibus bus
Aug 20 09:46:20 desktop systemd[36399]: Started dbus-:[email protected].

@mmstick
Copy link
Member

mmstick commented Aug 20, 2024

@DW8Reaper Do you have logs from cosmic-settings? It should display the cosmic-randr command it is running.

@DW8Reaper
Copy link

How do I specifically get cosmic-settings logs or is it just journalctl filtered to cosmic-settings output?

@mmstick
Copy link
Member

mmstick commented Aug 20, 2024

env RUST_LOG=debug cosmic-settings

@DW8Reaper
Copy link

Hopefully this is helpful

➜  ~ env RUST_LOG=debug cosmic-settings
   WARN  Key-Binding 'Period' only matched case insensitive for "period"
    at /build/cosmic-settings-OUJ10n/cosmic-settings-0.1.0~1723893909~22.04~83a4296/vendor/cosmic-settings-config/src/shortcuts/sym.rs:26 on main

   WARN  Key-Binding 'Comma' only matched case insensitive for "comma"
    at /build/cosmic-settings-OUJ10n/cosmic-settings-0.1.0~1723893909~22.04~83a4296/vendor/cosmic-settings-config/src/shortcuts/sym.rs:26 on main

   WARN  Key-Binding 'Period' only matched case insensitive for "period"
    at /build/cosmic-settings-OUJ10n/cosmic-settings-0.1.0~1723893909~22.04~83a4296/vendor/cosmic-settings-config/src/shortcuts/sym.rs:26 on main

   WARN  Key-Binding 'Comma' only matched case insensitive for "comma"
    at /build/cosmic-settings-OUJ10n/cosmic-settings-0.1.0~1723893909~22.04~83a4296/vendor/cosmic-settings-config/src/shortcuts/sym.rs:26 on main

  ERROR  shortcuts custom config error: GetKey("custom", Os { code: 2, kind: NotFound, message: "No such file or directory" })
    at /build/cosmic-settings-OUJ10n/cosmic-settings-0.1.0~1723893909~22.04~83a4296/vendor/cosmic-settings-config/src/shortcuts/mod.rs:43 on main

  DEBUG  executing, command: Command { std: "cosmic-randr" "mode" "DP-3" "5120" "1440", kill_on_drop: false }
    at cosmic-settings/src/pages/display/mod.rs:949 on tokio-runtime-worker

Error: "configuration failed"
  DEBUG  executing, command: Command { std: "cosmic-randr" "mode" "DP-3" "5120" "1440", kill_on_drop: false }
    at cosmic-settings/src/pages/display/mod.rs:949 on tokio-runtime-worker

Error: "configuration failed"

@DW8Reaper
Copy link

DW8Reaper commented Aug 20, 2024 •
edited
Loading

I just ran cosmic-randr mode DP-3 5120 1440 directly and it give that configuration failed error. Then I tried cosmic-randr mode DP-3 5120 1440 --test and it sort-of messed up my desktop so I Crtl+Alt+F3 to a TTY then switched back with Ctrl+Alt+F2 and now my resolution is 5120x1140 so a happy accident.

If I switch to 3840x1080 I'm back to the orignal problem where I cannot switch. Once I have set that resolution with the --test trick then I can change my refresh rate in cosmic settings but as soon as I mess with resolution again I cannot switch here is the log:

  ERROR  shortcuts custom config error: GetKey("custom", Os { code: 2, kind: NotFound, message: "No such file or directory" })
    at /build/cosmic-settings-OUJ10n/cosmic-settings-0.1.0~1723893909~22.04~83a4296/vendor/cosmic-settings-config/src/shortcuts/mod.rs:43 on main

  DEBUG  executing, command: Command { std: "cosmic-randr" "mode" "--refresh" "119.999" "DP-3" "5120" "1440", kill_on_drop: false }
    at cosmic-settings/src/pages/display/mod.rs:949 on tokio-runtime-worker

  DEBUG  executing, command: Command { std: "cosmic-randr" "mode" "--refresh" "239.761" "DP-3" "5120" "1440", kill_on_drop: false }
    at cosmic-settings/src/pages/display/mod.rs:949 on tokio-runtime-worker

  DEBUG  executing, command: Command { std: "cosmic-randr" "mode" "--refresh" "119.999" "DP-3" "5120" "1440", kill_on_drop: false }
    at cosmic-settings/src/pages/display/mod.rs:949 on tokio-runtime-worker

  DEBUG  executing, command: Command { std: "cosmic-randr" "mode" "DP-3" "3840" "1080", kill_on_drop: false }
    at cosmic-settings/src/pages/display/mod.rs:949 on tokio-runtime-worker

  DEBUG  executing, command: Command { std: "cosmic-randr" "mode" "DP-3" "5120" "1440", kill_on_drop: false }
    at cosmic-settings/src/pages/display/mod.rs:949 on tokio-runtime-worker

Error: "configuration failed"

That led me to try run cosmic-randr mode DP-3 5120 1440 --refresh "119.999" and that works so it looks like as long as I pass an explicit refresh rate then cosmic-randr works from the terminal

@mmstick
Copy link
Member

mmstick commented Aug 20, 2024

Then I'll make a change to always define the refresh rate when setting a resolution.

@WatchMkr WatchMkr modified the milestones: alpha 2, alpha 3 Sep 16, 2024
@WatchMkr WatchMkr moved this from Alpha 5 Settings to Post-Current-Alpha ToDo in COSMIC Epoch 1 Dec 3, 2024
@WatchMkr WatchMkr modified the milestones: alpha 3, alpha 6 Dec 3, 2024
@WatchMkr WatchMkr modified the milestones: alpha 6, alpha 7 Jan 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
COSMIC Epoch 1
Status: Post-Current-Alpha ToDo
Milestone
alpha 7
Development

No branches or pull requests
6 participants
@tuananh @curiousercreative @WatchMkr @DW8Reaper @mmstick @Drakulix