Closed farblos closed 1 hour ago
Ah ... probably the key here is that both monitors are mirrored and have the same x and y coordinates.
Does that mean that they are identical in terms of function monitor_compare
and, hence, show up only once in the RB-tree?
That would probably explain some of my confusion.
Thanks for reporting your bug here! The following template will help with giving as much information as possible so that it's easier to diagnose and fix.
Upfront Information
Please provide the following information by running the command and providing the output.
fvwm3 --version
)Commit b92ecb292ec639dc2701c3d172d6891417858d8a, then built as in Debian with
Debian testing with Fvwm3 built from main.
uname -sp
)Linux unknown
Expected Behaviour
I'm trying to understand Fvwm's monitor handling and patched it as follows:
Then I ensured that xrandr finds both monitors:
In that scenario, I'd expect that the call to
monitor_dump_state
would list also both these monitors when I restart Fvwm3 with above changes.Actual Behaviour
However, I get the following in my journal:
So
monitor_add
/monitor_mark_new
get called on both monitors, but the resulting dump shows only one?!Unfortunately, my gdb foo is not good enough to trace down the RB-tree ops. What I could get from gdb was that information from
monitor_get_count
(with the same monitor setup as shown above):