Hi all,
Maybe not really a Trinity issue, but:
On my Toshiba z20t, I have setup so that I get an onscreen keyboard at login, for the (rare) occasions where I use the computer as a tablet.
This had been talked about some time ago on this list and involves adding
onboard &
in /etc/trinity/tdm/Xsetup
and
killall onboard
in /etc/trinity/tdm/Xstartup
Now, the issue: this works perfectly on Stretch. It does not on Buster. Both installs on the same machine. Onboard itself works, simlpy it does not appear on the login screen on my Buster install.
The only difference I can find (except for Debian's version) is that Buster's Trinity was installed from Slavek's repository.
Thierry
Anno domini 2019 Tue, 13 Aug 12:46:34 +0200 Thierry de Coulon scripsit:
Hi all,
Maybe not really a Trinity issue, but:
On my Toshiba z20t, I have setup so that I get an onscreen keyboard at login, for the (rare) occasions where I use the computer as a tablet.
This had been talked about some time ago on this list and involves adding
onboard &
in /etc/trinity/tdm/Xsetup
and
killall onboard
in /etc/trinity/tdm/Xstartup
Now, the issue: this works perfectly on Stretch. It does not on Buster. Both installs on the same machine. Onboard itself works, simlpy it does not appear on the login screen on my Buster install.
The only difference I can find (except for Debian's version) is that Buster's Trinity was installed from Slavek's repository.
Thierry
does "onboard" work at all on buster?
To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
On Tuesday 13 August 2019 13.14:46 Dr. Nikolaus Klepp wrote:
does "onboard" work at all on buster?
Yes, it does.
I tried florence, and florence does load with Xsetup but crahes or does not take input. Either something is broken in latest TDE or (more probably) something is broken in latest Debian. Wether this is another effect of systemd I can't say, or could it be linked to the fact that (if I read right) Buster uses Wayland?
Thierry
Anno domini 2019 Tue, 13 Aug 16:04:10 +0200 Thierry de Coulon scripsit:
On Tuesday 13 August 2019 13.14:46 Dr. Nikolaus Klepp wrote:
does "onboard" work at all on buster?
Yes, it does.
I tried florence, and florence does load with Xsetup but crahes or does not take input. Either something is broken in latest TDE or (more probably) something is broken in latest Debian. Wether this is another effect of systemd I can't say, or could it be linked to the fact that (if I read right) Buster uses Wayland?
IMO Wayland is not the default, but it could be worth checking. What does the log of Xsetup say?
Nik
Thierry
To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
On Tuesday 13 August 2019 20.55:05 Nikolaus Klepp wrote:
IMO Wayland is not the default, but it could be worth checking.
This is what I read: "In this release, GNOME defaults to using the Wayland display server instead of Xorg. Wayland has a simpler and more modern design, which has advantages for security. However, the Xorg display server is still installed by default and the default display manager allows users to choose Xorg as the display server for their next session."
https://www.debian.org/News/2019/20190706
I did not install Gnome however (but I do use apps that expect Gnome).
What does the log of Xsetup say?
Could not find anything like Xsetup.org. Nothing in /var/log and a search for Xsetup.log or xsetup.log did not return anything.
Thierry
Anno domini 2019 Tue, 13 Aug 22:42:38 +0200 Thierry de Coulon scripsit:
On Tuesday 13 August 2019 20.55:05 Nikolaus Klepp wrote:
IMO Wayland is not the default, but it could be worth checking.
This is what I read: "In this release, GNOME defaults to using the Wayland display server instead of Xorg. Wayland has a simpler and more modern design, which has advantages for security. However, the Xorg display server is still installed by default and the default display manager allows users to choose Xorg as the display server for their next session."
https://www.debian.org/News/2019/20190706
I did not install Gnome however (but I do use apps that expect Gnome).
What does the log of Xsetup say?
Could not find anything like Xsetup.org. Nothing in /var/log and a search for Xsetup.log or xsetup.log did not return anything.
hm .. add a "1>/tmp/log 2>&1" after the onscreen keyboard and look what's written to it.
Thierry
To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
On Tuesday 13 August 2019 23.07:14 Dr. Nikolaus Klepp wrote:
hm .. add a "1>/tmp/log 2>&1" after the onscreen keyboard and look what's written to it.
23:14:01.027 WARNING OnboardGtk: D-Bus session bus unavailable Onboard will start with reduced functionality. Single-instance check, D-Bus service and hover click are disabled. 23:14:01.094 WARNING Config: mousetweaks GSettings schema not found, mousetweaks integration disabled.
(onboard:659): dconf-WARNING **: 23:14:01.149: failed to commit changes to dconf: Failed to execute child process “dbus-launch” (No such file or directory)
(onboard:659): dconf-WARNING **: 23:14:01.411: failed to commit changes to dconf: Failed to execute child process “dbus-launch” (No such file or directory) Traceback (most recent call last): File "/usr/bin/onboard", line 36, in <module> ob = Onboard() File "/usr/lib/python3/dist-packages/Onboard/OnboardGtk.py", line 148, in __init__ self.init() File "/usr/lib/python3/dist-packages/Onboard/OnboardGtk.py", line 189, in init self._init_delayed() File "/usr/lib/python3/dist-packages/Onboard/OnboardGtk.py", line 270, in _init_delayed self.service_keyboard = ServiceOnboardKeyboard(self) File "/usr/lib/python3/dist-packages/Onboard/OnboardGtk.py", line 854, in __init__ ServiceBase.__init__(self, dbus.SessionBus(), self.NAME, self.PATH) File "/usr/lib/python3/dist-packages/dbus/_dbus.py", line 211, in __new__ mainloop=mainloop) File "/usr/lib/python3/dist-packages/dbus/_dbus.py", line 100, in __new__ bus = BusConnection.__new__(subclass, bus_type, mainloop=mainloop) File "/usr/lib/python3/dist-packages/dbus/bus.py", line 122, in __new__ bus = cls._new_for_bus(address_or_type, mainloop=mainloop) dbus.exceptions.DBusException: org.freedesktop.DBus.Error.Spawn.ExecFailed: /usr/bin/dbus-launch terminated abnormally without any error message
If I start onboard after login I get:
23:19:55.516 WARNING Config: mousetweaks GSettings schema not found, mousetweaks integration disabled.
(onboard:1116): Gdk-CRITICAL **: 23:19:57.706: gdk_window_thaw_toplevel_updates: assertion 'window->update_and_descendants_freeze_count > 0' failed
Thierry
Anno domini 2019 Tue, 13 Aug 23:22:10 +0200 Thierry de Coulon scripsit:
On Tuesday 13 August 2019 23.07:14 Dr. Nikolaus Klepp wrote:
hm .. add a "1>/tmp/log 2>&1" after the onscreen keyboard and look what's written to it.
23:14:01.027 WARNING OnboardGtk: D-Bus session bus unavailable Onboard will start with reduced functionality. Single-instance check, D-Bus service and hover click are disabled. 23:14:01.094 WARNING Config: mousetweaks GSettings schema not found, mousetweaks integration disabled.
(onboard:659): dconf-WARNING **: 23:14:01.149: failed to commit changes to dconf: Failed to execute child process “dbus-launch” (No such file or directory)
(onboard:659): dconf-WARNING **: 23:14:01.411: failed to commit changes to dconf: Failed to execute child process “dbus-launch” (No such file or directory) Traceback (most recent call last): File "/usr/bin/onboard", line 36, in <module> ob = Onboard() File "/usr/lib/python3/dist-packages/Onboard/OnboardGtk.py", line 148, in __init__ self.init() File "/usr/lib/python3/dist-packages/Onboard/OnboardGtk.py", line 189, in init self._init_delayed() File "/usr/lib/python3/dist-packages/Onboard/OnboardGtk.py", line 270, in _init_delayed self.service_keyboard = ServiceOnboardKeyboard(self) File "/usr/lib/python3/dist-packages/Onboard/OnboardGtk.py", line 854, in __init__ ServiceBase.__init__(self, dbus.SessionBus(), self.NAME, self.PATH) File "/usr/lib/python3/dist-packages/dbus/_dbus.py", line 211, in __new__ mainloop=mainloop) File "/usr/lib/python3/dist-packages/dbus/_dbus.py", line 100, in __new__ bus = BusConnection.__new__(subclass, bus_type, mainloop=mainloop) File "/usr/lib/python3/dist-packages/dbus/bus.py", line 122, in __new__ bus = cls._new_for_bus(address_or_type, mainloop=mainloop) dbus.exceptions.DBusException: org.freedesktop.DBus.Error.Spawn.ExecFailed: /usr/bin/dbus-launch terminated abnormally without any error message
If I start onboard after login I get:
23:19:55.516 WARNING Config: mousetweaks GSettings schema not found, mousetweaks integration disabled.
(onboard:1116): Gdk-CRITICAL **: 23:19:57.706: gdk_window_thaw_toplevel_updates: assertion 'window->update_and_descendants_freeze_count > 0' failed
to sum it up: without dbus, onboard will not work. I suggest you use some other onscreen keyboard.
Nik
Thierry
To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
On Wednesday 14 August 2019 08.36:54 Dr. Nikolaus Klepp wrote:
to sum it up: without dbus, onboard will not work. I suggest you use some other onscreen keyboard.
Nik
Hmm... Florence does not work. kvkbd-trinity doesn't either (complains about DCOP). I did not try KDE's kvkbd but I wouldn't expect much.
All this worked on Stretch so I will go back to stretch. The computer works well with it so why bother with Buster?
Thanks for the help anyway!
Thierry
On Wed, 14 Aug 2019 11:19:10 +0200 Thierry de Coulon tcoulon@decoulon.ch wrote:
On Wednesday 14 August 2019 08.36:54 Dr. Nikolaus Klepp wrote:
to sum it up: without dbus, onboard will not work. I suggest you use some other onscreen keyboard.
Nik
Hmm... Florence does not work. kvkbd-trinity doesn't either (complains about DCOP). I did not try KDE's kvkbd but I wouldn't expect much.
What about matchbox-keyboard, if your distro packages it? I've never used it, but it looks like its only dependencies are some X libraries (no dbus, DCOP, or other messaging service).
E. Liddell
On Wednesday 14 August 2019 13.28:27 E. Liddell wrote:
What about matchbox-keyboard, if your distro packages it? I've never used it, but it looks like its only dependencies are some X libraries (no dbus, DCOP, or other messaging service).
E. Liddell
Seems to work, but the keys are too small for my fingers on th login screen. Thanks for the hint, I did not know that one.
have you tried "xvkbd" ?
Nik
This seems to be the solution if I want to keep Buster. xvkbd is a bit crude compared to onboard, but for login it's enough.
Using -geometry I can get the keys to be big enough and the keyboard to be placed correctly. Not so bad.
Thanks Nik
-
Dr. Nikolaus Klepp -
E. Liddell -
Nikolaus Klepp
-
Thierry de Coulon