Closed artogahr closed 2 years ago
Just realized I opened the issue on the wrong extension github, sorry
This problem also happens with this extension btw, so I'm editing and opening this one in hopes that someone here might be able to help me as well 😅
I encountered the same problem on two Fedora 35 systems. It's been going on for a couple of weeks and may have come with the update to ddcutil 1.3.0. I downgraded to version 0.9.9, which resolved it
Could you both provide your gnome-shell logs?
Journal logs
journalctl --no-pager -b /usr/bin/gnome-shell
Run above command and paste the log here
Having already downgraded, I'm afraid my log is not helpful here, but I'll try to post the log from my other device tomorrow.
The underlying problem in ddcutil
seems to have been reported and fixed in the 1.4.0-dev branch.
I can confirm switching to ddcutil-git from AUR fixed the issue, but weirdly enough it's only detecting one of my monitors right now. For context, both monitors are the same model and are connected to the dock using same type of DP cables.
Both monitors have the 0x10 capability, and in fact their capabilities are the same:
➜ ~ ddcutil capabilities --bus 16 > 16
➜ ~ ddcutil capabilities --bus 15 > 15
➜ ~ diff 15 16
➜ ~
The main issue like you both figured out is upstream bug, but for the second issue you have @artogahr, disable display state check from the settings, this is a known issue in some monitors.
On August 29, 2022 10:58:10 AM GMT+03:00, Artoghrul Gahramanli @.***> wrote:
I can confirm switching to ddcutil-git from AUR fixed the issue, but weirdly enough it's only detecting one of my monitors right now. For context, both monitors are the same model and are connected to the dock using same type of DP cables.
Here are the logs for that
``` ➜ ~ journalctl --no-pager -b /usr/bin/gnome-shell Aug 29 09:51:13 fortiowl gnome-shell[1472]: Running GNOME Shell (using mutter 42.4) as a Wayland display server Aug 29 09:51:13 fortiowl gnome-shell[1472]: Device '/dev/dri/card0' prefers shadow buffer Aug 29 09:51:14 fortiowl gnome-shell[1472]: Added device '/dev/dri/card0' (i915) using atomic mode setting. Aug 29 09:51:14 fortiowl gnome-shell[1472]: Created gbm renderer for '/dev/dri/card0' Aug 29 09:51:14 fortiowl gnome-shell[1472]: Boot VGA GPU /dev/dri/card0 selected as primary Aug 29 09:51:15 fortiowl gnome-shell[1472]: Using public X11 display :1024, (using :1025 for managed services) Aug 29 09:51:15 fortiowl gnome-shell[1472]: Using Wayland display name 'wayland-0' Aug 29 09:51:15 fortiowl gnome-shell[1472]: Unset XDG_SESSION_ID, getCurrentSessionProxy() called outside a user session. Asking logind directly. Aug 29 09:51:15 fortiowl gnome-shell[1472]: Will monitor session 1 Aug 29 09:51:15 fortiowl gnome-shell[1472]: Extension ***@***.*** already installed in ***@***.*** ***@***.*** will not be loaded Aug 29 09:51:15 fortiowl gnome-shell[1472]: Extension ***@***.*** already installed in ***@***.*** ***@***.*** will not be loaded Aug 29 09:51:15 fortiowl gnome-shell[1472]: Extension ***@***.*** already installed in ***@***.*** ***@***.*** will not be loaded Aug 29 09:51:15 fortiowl gnome-shell[1472]: Extension ***@***.*** already installed in ***@***.*** ***@***.*** will not be loaded Aug 29 09:51:15 fortiowl gnome-shell[1472]: Extension ***@***.*** already installed in ***@***.*** ***@***.*** will not be loaded Aug 29 09:51:15 fortiowl gnome-shell[1472]: Extension ***@***.*** already installed in ***@***.*** ***@***.*** will not be loaded Aug 29 09:51:15 fortiowl gnome-shell[1472]: Extension ***@***.*** already installed in ***@***.*** ***@***.*** will not be loaded Aug 29 09:51:15 fortiowl gnome-shell[1472]: Extension ***@***.*** already installed in ***@***.*** ***@***.*** will not be loaded Aug 29 09:51:15 fortiowl gnome-shell[1472]: Extension ***@***.*** already installed in ***@***.*** ***@***.*** will not be loaded Aug 29 09:51:15 fortiowl gnome-shell[1472]: Extension ***@***.*** already installed in ***@***.*** ***@***.*** will not be loaded Aug 29 09:51:15 fortiowl gnome-shell[1472]: Extension ***@***.*** already installed in ***@***.*** ***@***.*** will not be loaded Aug 29 09:51:15 fortiowl gnome-shell[1472]: Extension ***@***.*** already installed in ***@***.*** ***@***.*** will not be loaded Aug 29 09:51:16 fortiowl org.gnome.Shell.desktop[1472]: Window manager warning: Failed to parse saved session file: Failed to open file “/var/lib/gdm/.config/mutter/sessions/102a93a1ac10b9927b166175947366545700000014640000.ms”: No such file or directory Aug 29 09:51:16 fortiowl gnome-shell[1472]: Failed to launch ibus-daemon: Failed to execute child process “ibus-daemon” (No such file or directory) Aug 29 09:51:16 fortiowl gnome-shell[1472]: Error looking up permission: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation Aug 29 09:51:16 fortiowl gnome-shell[1472]: ATK Bridge is disabled but a11y has already been enabled. Aug 29 09:51:17 fortiowl gnome-shell[1472]: Failed to launch ibus-daemon: Failed to execute child process “ibus-daemon” (No such file or directory) Aug 29 09:51:17 fortiowl gnome-shell[1472]: Registering session with GDM Aug 29 09:51:40 fortiowl gnome-shell[2127]: Running GNOME Shell (using mutter 42.4) as a Wayland display server Aug 29 09:51:40 fortiowl gnome-shell[2127]: Device '/dev/dri/card0' prefers shadow buffer Aug 29 09:51:40 fortiowl gnome-shell[2127]: Added device '/dev/dri/card0' (i915) using atomic mode setting. Aug 29 09:51:40 fortiowl gnome-shell[2127]: Created gbm renderer for '/dev/dri/card0' Aug 29 09:51:40 fortiowl gnome-shell[2127]: Boot VGA GPU /dev/dri/card0 selected as primary Aug 29 09:51:41 fortiowl gnome-shell[2127]: Using public X11 display :0, (using :1 for managed services) Aug 29 09:51:41 fortiowl gnome-shell[2127]: Using Wayland display name 'wayland-0' Aug 29 09:51:41 fortiowl gnome-shell[2127]: Unset XDG_SESSION_ID, getCurrentSessionProxy() called outside a user session. Asking logind directly. Aug 29 09:51:41 fortiowl gnome-shell[2127]: Will monitor session 3 Aug 29 09:51:41 fortiowl gnome-shell[2127]: Telepathy is not available, chat integration will be disabled. Aug 29 09:51:41 fortiowl gnome-shell[2127]: loading user theme: /usr/share/themes/Yaru-blue/gnome-shell/gnome-shell.css Aug 29 09:51:41 fortiowl gnome-shell[2127]: gtk_icon_theme_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed Aug 29 09:51:41 fortiowl gnome-shell[2127]: Some code accessed the property 'SecondaryMonitorDisplay' on the module 'workspacesView'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway. Aug 29 09:51:41 fortiowl gnome-shell[2127]: Some code accessed the property 'ThumbnailsBox' on the module 'workspacesView'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway. Aug 29 09:51:41 fortiowl gnome-shell[2127]: JS ERROR: Could not load extension GPaste-42.1: Error: Missing metadata.json ***@***.***:///org/gnome/shell/ui/extensionSystem.js:298:19 ***@***.***:///org/gnome/shell/ui/extensionSystem.js:626:34 ***@***.***:///org/gnome/shell/misc/fileUtils.js:27:28 ***@***.***:///org/gnome/shell/ui/extensionSystem.js:610:19 ***@***.***:///org/gnome/shell/ui/extensionSystem.js:637:18 ***@***.***:///org/gnome/shell/ui/extensionSystem.js:657:14 ***@***.***:///org/gnome/shell/ui/extensionSystem.js:55:14 ***@***.***:///org/gnome/shell/ui/main.js:289:22 ***@***.***:///org/gnome/shell/ui/main.js:166:5 @resource:///org/gnome/shell/ui/init.js:6:17 Aug 29 09:51:41 fortiowl gnome-shell[2127]: g_signal_handler_disconnect: assertion 'handler_id > 0' failed Aug 29 09:51:41 fortiowl gnome-shell[2127]: g_signal_handler_disconnect: assertion 'handler_id > 0' failed Aug 29 09:51:41 fortiowl gnome-shell[2127]: Disabling 'Window Is Ready' Notification Aug 29 09:51:41 fortiowl gnome-shell[2127]: ../glib/gobject/gsignal.c:1739: signal "hide" already exists in the 'ClutterActor' class ancestry Aug 29 09:51:41 fortiowl gnome-shell[2127]: [pano] [extension] extension is initialized Aug 29 09:51:41 fortiowl gnome-shell[2127]: [pano] [key-manager] Trying to listen for hot key [accelerator=v] Aug 29 09:51:41 fortiowl gnome-shell[2127]: [pano] [key-manager] Grabbed accelerator [action=116] Aug 29 09:51:41 fortiowl gnome-shell[2127]: [pano] [key-manager] Received binding name for action [name=external-grab-116, action=116] Aug 29 09:51:41 fortiowl gnome-shell[2127]: [pano] [extension] extension is enabled Aug 29 09:51:41 fortiowl gnome-shell[2127]: display-brightness-ddcutil extension: Adding to panel Aug 29 09:51:41 fortiowl gnome-shell[2127]: display-brightness-ddcutil extension: Add keyboard shortcuts Aug 29 09:51:41 fortiowl gnome-shell[2127]: Extension ***@***.*** already installed in ***@***.*** ***@***.*** will not be loaded Aug 29 09:51:41 fortiowl gnome-shell[2127]: Extension ***@***.*** already installed in ***@***.*** ***@***.*** will not be loaded Aug 29 09:51:41 fortiowl gnome-shell[2127]: Could not issue 'GetUnit' systemd call Aug 29 09:51:41 fortiowl gnome-shell[2127]: st_widget_get_theme_node called on the widget [0x563586e44c40 StLabel.monospace:insensitive ("100%")] which is not in the stage. Aug 29 09:51:41 fortiowl gnome-shell[2127]: st_widget_get_theme_node called on the widget [0x56358743eb50 StLabel.monospace:insensitive ("100%")] which is not in the stage. Aug 29 09:51:41 fortiowl gnome-shell[2127]: st_widget_get_theme_node called on the widget [0x56358744c220 StLabel.monospace:insensitive ("100%")] which is not in the stage. Aug 29 09:51:41 fortiowl gnome-shell[2127]: st_widget_get_theme_node called on the widget [0x563587443500 StLabel.monospace:insensitive ("100%")] which is not in the stage. Aug 29 09:51:41 fortiowl gnome-shell[2127]: st_widget_get_theme_node called on the widget [0x5635862510a0 StLabel.monospace:insensitive ("100%")] which is not in the stage. Aug 29 09:51:41 fortiowl gnome-shell[2127]: st_widget_get_theme_node called on the widget [0x56358745e7e0 StLabel.monospace:insensitive ("100%")] which is not in the stage. Aug 29 09:51:41 fortiowl gnome-shell[2127]: Failed to launch ibus-daemon: Failed to execute child process “ibus-daemon” (No such file or directory) Aug 29 09:51:41 fortiowl gnome-shell[2127]: Error looking up permission: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation Aug 29 09:51:41 fortiowl gnome-shell[2127]: clutter_actor_get_child_at_index: assertion 'index_ <= self->priv->n_children' failed Aug 29 09:51:41 fortiowl gnome-shell[2127]: clutter_actor_get_child_at_index: assertion 'index_ <= self->priv->n_children' failed Aug 29 09:51:41 fortiowl gnome-shell[2127]: display-brightness-ddcutil extension: Monitor change detected, reloading extension in 5 seconds. Aug 29 09:51:41 fortiowl gnome-shell[2127]: display-brightness-ddcutil extension: ddcutil brief info: Display 1 I2C bus: /dev/i2c-15 DRM connector: card0-DP-3 Monitor: DEL:DELL P2419H:5CQ5PM2 > Display 2 I2C bus: /dev/i2c-16 DRM connector: card0-DP-4 Monitor: DEL:DELL P2419H:J0PDPD3 > Aug 29 09:51:41 fortiowl gnome-shell[2127]: display-brightness-ddcutil extension: ddcutil brief info found bus line: I2C bus: /dev/i2c-15 Aug 29 09:51:41 fortiowl gnome-shell[2127]: display-brightness-ddcutil extension: ddcutil reading display state for bus: 15 Aug 29 09:51:41 fortiowl gnome-shell[2127]: display-brightness-ddcutil extension: ddcutil brief info found bus line: I2C bus: /dev/i2c-16 Aug 29 09:51:41 fortiowl gnome-shell[2127]: display-brightness-ddcutil extension: ddcutil reading display state for bus: 16 Aug 29 09:51:41 fortiowl gnome-shell[2127]: Usage of object.actor is deprecated for Indicator ***@***.***:///org/gnome/shell/ui/environment.js:411:29 _refresh@***@***.***/extension.js:116:13 _runLoop@***@***.***/extension.js:48:14 Aug 29 09:51:42 fortiowl gnome-shell[2127]: clutter_actor_get_child_at_index: assertion 'index_ <= self->priv->n_children' failed Aug 29 09:51:42 fortiowl gnome-shell[2127]: clutter_actor_get_child_at_index: assertion 'index_ <= self->priv->n_children' failed Aug 29 09:51:42 fortiowl gnome-shell[2127]: display-brightness-ddcutil extension: ddcutil reading display status for bus: 15 is: No monitor detected on bus /dev/i2c-15 Aug 29 09:51:42 fortiowl gnome-shell[2127]: DWifi Debug: Adding menu.. Aug 29 09:51:42 fortiowl gnome-shell[2127]: DWifi Debug: Device Current State: 30 Aug 29 09:51:42 fortiowl gnome-shell[2127]: display-brightness-ddcutil extension: ddcutil reading display status for bus: 16 is: VCP D6 SNC x01 Aug 29 09:51:43 fortiowl gnome-shell[2127]: Could not issue 'GetUnit' systemd call Aug 29 09:51:43 fortiowl gnome-shell[2127]: Failed to launch ibus-daemon: Failed to execute child process “ibus-daemon” (No such file or directory) Aug 29 09:51:43 fortiowl gnome-shell[2127]: ATK Bridge is disabled but a11y has already been enabled. Aug 29 09:51:43 fortiowl gnome-shell[2127]: GNOME Shell started at Mon Aug 29 2022 09:51:41 GMT+0200 (Central European Summer Time) Aug 29 09:51:43 fortiowl gnome-shell[2127]: Registering session with GDM Aug 29 09:51:43 fortiowl gnome-shell[1472]: Connection to xwayland lost Aug 29 09:51:44 fortiowl gnome-shell[2127]: display-brightness-ddcutil extension: Reloading widgets Aug 29 09:51:45 fortiowl ***@***.***[2127]: Microsoft Teams - Preview1, Impossible to lookup icon for 'Microsoft Teams - Preview1_2-panel' in path /tmp/.org.chromium.Chromium.MeBkGe Aug 29 09:51:45 fortiowl ***@***.***[2127]: unable to update icon for Microsoft Teams - Preview1 Aug 29 09:51:45 fortiowl ***@***.***[2127]: Microsoft Teams - Preview1, Impossible to lookup icon for 'Microsoft Teams - Preview1_2-panel' in path /tmp/.org.chromium.Chromium.MeBkGe Aug 29 09:51:45 fortiowl ***@***.***[2127]: unable to update icon for Microsoft Teams - Preview1 Aug 29 09:51:47 fortiowl gnome-shell[2127]: display-brightness-ddcutil extension: Reload extension Aug 29 09:51:47 fortiowl gnome-shell[2127]: display-brightness-ddcutil extension: Remove keyboard shortcuts Aug 29 09:51:47 fortiowl gnome-shell[2127]: display-brightness-ddcutil extension: Adding to panel Aug 29 09:51:47 fortiowl gnome-shell[2127]: display-brightness-ddcutil extension: Add keyboard shortcuts Aug 29 09:51:47 fortiowl ***@***.***[2127]: unable to update icon for Microsoft Teams - Preview1 Aug 29 09:51:47 fortiowl gnome-shell[2127]: display-brightness-ddcutil extension: ddcutil brief info: Display 1 I2C bus: /dev/i2c-15 DRM connector: card0-DP-3 Monitor: DEL:DELL P2419H:5CQ5PM2 > Display 2 I2C bus: /dev/i2c-16 DRM connector: card0-DP-4 Monitor: DEL:DELL P2419H:J0PDPD3 > Aug 29 09:51:47 fortiowl gnome-shell[2127]: display-brightness-ddcutil extension: ddcutil brief info found bus line: I2C bus: /dev/i2c-15 Aug 29 09:51:47 fortiowl gnome-shell[2127]: display-brightness-ddcutil extension: ddcutil reading display state for bus: 15 Aug 29 09:51:47 fortiowl gnome-shell[2127]: display-brightness-ddcutil extension: ddcutil brief info found bus line: I2C bus: /dev/i2c-16 Aug 29 09:51:47 fortiowl gnome-shell[2127]: display-brightness-ddcutil extension: ddcutil reading display state for bus: 16 Aug 29 09:51:48 fortiowl gnome-shell[2127]: display-brightness-ddcutil extension: ddcutil reading display status for bus: 15 is: No monitor detected on bus /dev/i2c-15 Aug 29 09:51:48 fortiowl gnome-shell[2127]: display-brightness-ddcutil extension: ddcutil reading display status for bus: 16 is: VCP D6 SNC x01 Aug 29 09:51:50 fortiowl gnome-shell[2127]: display-brightness-ddcutil extension: Reloading widgets Aug 29 09:51:50 fortiowl gnome-shell[2127]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. Aug 29 09:51:50 fortiowl gnome-shell[2127]: The offending callback was set_actor(), a vfunc. Aug 29 09:51:50 fortiowl gnome-shell[2127]: == Stack trace for context 0x7f7c2412b4b0 == Aug 29 09:51:50 fortiowl gnome-shell[2127]: == Stack trace for context 0x7f7c2412b4b0 == Aug 29 09:51:50 fortiowl gnome-shell[2127]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. Aug 29 09:51:50 fortiowl gnome-shell[2127]: The offending callback was set_actor(), a vfunc. Aug 29 09:52:11 fortiowl gnome-shell[2127]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed Aug 29 09:52:11 fortiowl gnome-shell[2127]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed Aug 29 09:53:14 fortiowl gnome-shell[2127]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x100000f ``` Both monitors have the 0x10 capability, and in fact their capabilities are the same:
➜ ~ ddcutil capabilities --bus 16 > 16 ➜ ~ ddcutil capabilities --bus 15 > 15 ➜ ~ diff 15 16 > ➜ ~ >
-- > Reply to this email directly or view it on GitHub:
https://github.com/daitj/gnome-display-brightness-ddcutil/issues/81#issuecomment-1229916656
You are receiving this because you commented.
Message ID: @.***>
Thanks for the response, unfortunately that didn't fix the issue
Try these commands and see what happens.
For state (skipable by settings)
ddcutil getvcp --brief D6 --bus 15
For brightness info (needed to read monitor's current brightness, possible max and min brightness value)
ddcutil getvcp --brief 10 --bus 15
For setting brightness
ddcutil setvcp 10 30 --bus 15
Adjusting brightness through cli still works, no problem
➜ ~ ddcutil getvcp --brief D6 --bus 15
VCP D6 SNC x01
➜ ~ ddcutil getvcp --brief D6 --bus 16
VCP D6 SNC x01
➜ ~ ddcutil getvcp --brief 10 --bus 15
VCP 10 C 30 100
➜ ~ ddcutil getvcp --brief 10 --bus 16
VCP 10 C 20 100
➜ ~
Any other logs you think I might check? I can also try downgrading to ddcutil 0.99 or build the latest ddcutil from source, instead of using the aur version
From the previous log I cannot see anything suspicious.
What exactly doesn't work at the moment?
Do you have both display in the menu? Brightness slider(s) not doing anything?
Also do you have something in $XDG_CACHE_HOME/ddcutil_detect?
I have only one display in the menu, specifically bus 16. For the bus 15 there's this log:
ddcutil reading display status for bus: 15 is: No monitor detected on bus /dev/i2c-15
However:
Aug 29 10:17:39 fortiowl gnome-shell[2127]: display-brightness-ddcutil extension:
ddcutil brief info:
Display 1
I2C bus: /dev/i2c-15
DRM connector: card0-DP-3
Monitor: DEL:DELL P2419H:5CQ5PM2
Display 2
I2C bus: /dev/i2c-16
DRM connector: card0-DP-4
Monitor: DEL:DELL P2419H:J0PDPD3
Also do you have something in $XDG_CACHE_HOME/ddcutil_detect?
I used to, but I deleted it for testing, didn't fix it
Well according to the extension, this command is returning No monitor detected
or DDC communication failed
ddcutil getvcp --brief D6 --bus 15
Could you check this again, also remember to not use sudo or root shell, these commands should work with current user without root access.
Just a note, this extension explicitly uses /usr/bin/ddcutil
in case you have multiple version installed in different places.
This is done through normal shell with correct ddcutil permission stuff applied, with normal user:
➜ ~ which ddcutil
/usr/bin/ddcutil
➜ ~ /usr/bin/ddcutil getvcp --brief D6 --bus 15
VCP D6 SNC x01
Need latest gnome logs one more time?
Also which version of the extension are you using, you can see this in extension manager.
May be the age old method of restarting everything will fix the issue
Extenstion version is 31, installed from extension.gnome.org
Tried restarting multiple times with no avail I'm afraid :/
@steffen-stell can I ask how you downgraded? I built the 1.0.0 tarball from source and that one didn't work for me at all. Also are you using multiple monitors or just a single one?
@artogahr
I suggest you to install the current version manually, README
Then in your system, you will find the installed extension.js here: ~/.local/share/gnome-shell/extensions/display-brightness-ddcuti@themightydeity.github.com/extension.js
which should be edited.
Hopefully you are able to do this, try to remove the condition with "No monitor detected" from this line
Logout and login (for wayland) restart gnome-shell (for x11)
That did in fact fix the issue!
For reference:
//if (vcpPowerInfos.indexOf("DDC communication failed") === -1 && vcpPowerInfos.indexOf("No monitor detected") === -1) {
// Edited as below
if (vcpPowerInfos.indexOf("DDC communication failed") === -1) {
Both monitors are shown and are adjustable:
Thanks.
One thing: The "All monitors" slider only seems to be affecting the second monitor (bus 16). The UI show the change in bus 15 as well but the acutal brightness only changes at 16. Manually changing both works, so I disabled the all monitors slider for now, just wanted to let you know.
One thing: The "All monitors" slider only seems to be affecting the second monitor (bus 16). The UI show the change in bus 15 as well but the acutal brightness only changes at 16. Manually changing both works, so I disabled the all monitors slider for now, just wanted to let you know.
Update on that: Sometime it works for both monitors, sometimes it doesn't, it's weird, but discussion for another issue I guess, so disregard
@artogahr May be there is some disturbance in DDC communication with your monitor on bus 15.
Three reasons:
ddcutil setvcp 10 30 > file.log &
in a for loop and log everything, i am thinking about simultaneous calls, of course they could be failing because of the reasons below or just that there is some bug in ddcutilI'll test, shall we close this issue?
It seems like you have same model monitors, I would check by swapping the cables and also swapping the port they are connected to as well. If you get some errors in ddcutil, you should follow up with ddcutil's developer to get it sorted.
Basically what the title says:
I have two monitors on bus /dev/i2c-15 and 16. I can change their brightness using ddcutil itself, with normal user permissions, no problem:
I'm guessing the errors might be throwing off the parser based on other issues I read of this repo, but I don't know what to do about them, couldn'd find anything on google. I also tried putting an errors omitted version of ddcutil detect to .cache/ddcutil_detect as some issue suggested, but that didn't help either.
Extension Log from "Auto Display Brightness" extension, might help
``` ### initializing, version 21 ### getDisplays - Unable to open directory /sys/bus/i2c/devices/i2c--1: No such file or directory Device /dev/i2c-255 does not exist. Error = ENOENT(2): No such file or directory /sys/bus/i2c buses without /dev/i2c-N devices: /sys/bus/i2c/devices/i2c-255 Driver i2c_dev must be loaded or builtin See https://www.ddcutil.com/kernel_module Invalid display I2C bus: /dev/i2c-12 DRM connector: card0-eDP-1 Monitor: SHP:: Phantom display I2C bus: /dev/i2c-13 DRM connector: card0-DP-1 Monitor: DEL:DELL P2419H:5CQ5PM2 Display 1 I2C bus: /dev/i2c-15 DRM connector: card0-DP-3 Monitor: DEL:DELL P2419H:5CQ5PM2 Display 2 I2C bus: /dev/i2c-16 DRM connector: card0-DP-4 Monitor: DEL:DELL P2419H:J0PDPD3 ### getDisplays - ERR 255 does not exist. Error = ENOENT(2): No such file or directory, null, null ### getDisplays - ERR 15, null, null ### getDisplays - ERR 16, null, null ### ScreenBrightnessPanelMenu init finsihed. ```ddcutil detect output
``` ➜ ~ ddcutil detect Unable to open directory /sys/bus/i2c/devices/i2c--1: No such file or directory Device /dev/i2c-255 does not exist. Error = ENOENT(2): No such file or directory /sys/bus/i2c buses without /dev/i2c-N devices: /sys/bus/i2c/devices/i2c-255 Driver i2c_dev must be loaded or builtin See https://www.ddcutil.com/kernel_module Invalid display I2C bus: /dev/i2c-12 DRM connector: card0-eDP-1 EDID synopsis: Mfg id: SHP - Sharp Corporation Model: Product code: 5442 (0x1542) Serial number: Binary serial number: 0 (0x00000000) Manufacture year: 2021, Week: 10 DDC communication failed This is an eDP laptop display. Laptop displays do not support DDC/CI. Phantom display I2C bus: /dev/i2c-13 DRM connector: card0-DP-1 EDID synopsis: Mfg id: DEL - Dell Inc. Model: DELL P2419H Product code: 53465 (0xd0d9) Serial number: 5CQ5PM2 Binary serial number: 826421314 (0x31423042) Manufacture year: 2018, Week: 46 DDC communication failed Use non-phantom device bus /dev/i2c-15 Display 1 I2C bus: /dev/i2c-15 DRM connector: card0-DP-3 EDID synopsis: Mfg id: DEL - Dell Inc. Model: DELL P2419H Product code: 53465 (0xd0d9) Serial number: 5CQ5PM2 Binary serial number: 826421314 (0x31423042) Manufacture year: 2018, Week: 46 VCP version: 2.1 Display 2 I2C bus: /dev/i2c-16 DRM connector: card0-DP-4 EDID synopsis: Mfg id: DEL - Dell Inc. Model: DELL P2419H Product code: 53465 (0xd0d9) Serial number: J0PDPD3 Binary serial number: 876034380 (0x3437394c) Manufacture year: 2021, Week: 23 VCP version: 2.1 ```Some troubleshooting info: