AutoRotate 0.4 Release
A week after the 0.3 release of my AutoRotate daemon, a big bug was found (Thank you, Jonas). By default on Ubuntu systems (and probably others), system buses are not allowed to be created unless they are specified as a special exception in a file. And for 0.3, I’ve forgot to include this special file in the release so if you tried to run the auto-rotate.py program, you would get this error:
Traceback (most recent call last):
File “/usr/bin/auto-rotate.py”, line 50, in
main()
File “/usr/bin/auto-rotate.py”, line 40, in main
busname = dbus.service.BusName(“net.krizka.autorotate”,system_bus);
File “/usr/lib/pymodules/python2.6/dbus/service.py”, line 129, in __new__
retval = bus.request_name(name, name_flags)
File “/usr/lib/pymodules/python2.6/dbus/bus.py”, line 306, in request_name
’su’, (name, flags))
File “/usr/lib/pymodules/python2.6/dbus/connection.py”, line 620, in call_blocking
message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.AccessDenied: Connection “:1.148″ is not allowed to own the service “net.krizka.autorotate” due to security policies in the configuration file
This is now fixed in the 0.4 release of AutoRotate, the sources for which you can download here and follow these instructions to install it. Also, the Ubuntu package is currently being build in my PPA and will be installable soon, following these instructions.
Finally, there are a few other changes in this release. The most notable being the employment of libnotify, by the manual-rotate.py script, to notify you when the automatic rotation has been enabled/disabled.
The full change log is as follows:
- Added .conf file to allow creation of system bus
- manual-rotate.py notifies the user when automatic rotation is enabled/disabled via libnotify
- Check if autorotate daemon already running before starting another one
- Added dbus .service file describing the autorotate service
- Fixed the dependencies in the debian control file
Hi,
thank u very much for the update!
Now almost everything is working fine.
But i got another little problem: after returning from tablet to normal mode my mouse cursor isnt visible any more.
Maybe u have an idea how to solve this problem.
Thanks!
Jonas
Hmm, that is weird. Do you have the problem if the screen gets rotated in tablet mode? Because nothing special is done as you go from tablet to laptop mode, other than the screen is set to 0 degree rotation.
No it only occurs when returning to desktop mode.
But I always get the error “no such device: stylus” .
About returning to laptop mode:
What distribution are you using? How about X.Org version?
About “no such device: stylus”:
I assume you are using an X.Org version that uses HAL for detecting input devices, because that could explain the error. HAL by default gives weird names to wacom devices, so wacomctl can’t find them. You need to rename them following these instructions (should work outside of Ubuntu too):
https://help.ubuntu.com/community/X61T#Wacomcpl
Thank you for reporting your problems!
Hi Karol,
I’m a user of Linux Mint & Thinkpad X61 tablet (with SXGA+ 1400×1050).
Your website is a great find for me, thank you for sharing your geek knowledge in implementing of linux and your knowledge to the internet community.
I guess you are using a Thinkpad X61t with SXGA (1024×768) resolution, because neither the auto rotation nor the manual rotation python script did the right job to fix the mouse pointer location in all screen orientations except the normal xrandr.
Will there be a simple fix to that? I shall look into the code if I need to.
Thanks a lot again.
Best,
J.
Hi Menuhin,
I am using the SXGA display with the 1400×1050 resolution too.
Can you give me the output of the following command?
xsetwacom list
Weird.
There is no output.
You might need to do this:
https://help.ubuntu.com/community/X61T#Wacomcpl
By default, X.org/HAL in Ubuntu has trouble picking up the wacom stylus.