This is still happening for me on Ubuntu 14.04 on a Thinkpad 440S. When
I undock and redock the external monitor physically on the left side is
configured to be on the right and the activities bar remains on the
laptop. If I reset the machine while docked it returns to the correct
state.
--
This bug is present in Ubuntu 12.10. If I undocking the laptop from docking
station, and after that re docking it, and press any key on keyboard, then the
display setting goes to mirror mode by automatically. If I do not use the
docking station, and disconnect/connect the 2nd monitor to
The attached python script utilizes pyudev (available from Natty onward)
to wait for docking events and then calls gnome-settings-daemon
ApplyConfiguration method. It's a slight improvement over the udev rules
hackery before. Would be interesting to hear if this approach resolves
the original
I can reproduce this problem on a Lenovo T61 with a docking station, the
monitor layout setting is not used. However, when I call
ApplyConfiguration via dbus, then the correct setting is applied:
dbus-send --type=method_call --print-reply --session
--dest=org.gnome.SettingsDaemon
Calling gsd_xrandr_manager_apply_configuration (mgr, error);
unconditionally from plugins/xrandr/gsd-xrandr-manager.c handle_fn_f7
will restore the existing configuration as well. But fn-f7 cycling
through display modes stops working, as the existing configuration will
always take precedence.
I followed the path of calling ApplyConfiguration from a script upon
docking, and while it is not pretty, it basically works:
# cat /etc/udev/rules.d/80-thinkpad-T61.rules
KERNEL==dock.0, ATTR{docked}==1, RUN+=/usr/local/bin/dock.sh 1
KERNEL==dock.0, ATTR{docked}==0, RUN+=/usr/local/bin/dock.sh
Torsten Spindler [2011-09-15 11:58 -]:
Is there any other place in the system that is run only when a system is
being docked?
We don't have that, but current upower has a property for this, and
libupower-glib exports it. So you can hook a callback to that signal
to run somethign whenever
Unfortunately upower 0.9.1 on Ubuntu 10.04 LTS does not have
up_client_get_is_docked. The earliest upower that has it is in Natty.
Backporting this to Lucid seems like a task, due to dependencies:
dpkg-checkbuilddeps: Unmet build dependencies: debhelper (= 8)
libusb-1.0-0-dev (= 1.0.0)
gnome-settings-daemon listens for drm udev events to trigger automatic
layout updates. As it turns out, upower's current definition for is
this machine docked is does this machine have more than one output
connected, and it...also listens for udev events - specifically from
drm, not dock devices -
