**** BEGIN LOGGING AT Fri Jan 11 02:59:57 2019 Jan 11 10:11:05 hi, can anybody access oesf.org? Jan 11 10:22:52 works now here, it seems to have been a temporary ISP issue Jan 11 12:49:55 does anyone have a clue how to disable connman system tray? Jan 11 12:50:32 When it runs I lose the b and n keys in xfce Jan 11 12:50:38 And it starts automatically somehow Jan 11 13:40:57 its unlikely to be the connman system tray eating those keys, it'll be whatever shortcut manager your using Jan 11 13:43:37 but to stop the system tray you'd need to look for 'cmst' in your xfce config Jan 11 13:45:53 I've had a look in the session startup and it isn't there Jan 11 13:46:11 I think it's something to do with a qt app starting Jan 11 13:46:42 It's odd, the terminal is started first as part of the session, and as soon as cmst appears those keys stop working Jan 11 13:47:20 Admittedly it could be some other part of session startup causing it, but it happens at that moment Jan 11 13:48:12 The other annoying bug I have is that the mouse (digitizer) click only works on sometimes, I think the problem is only on GTK 2 widgets Jan 11 13:48:31 The click gives the widget focus but doesn't cause a click event Jan 11 13:48:51 you've read the first two paragraphs of: https://github.com/gemian/gemini-keyboard-apps/wiki/DebianTP#key-maps-and-shortcuts Jan 11 13:48:54 I am wondering if somehow it's registering as the wrong mouse button (middle maybe) Jan 11 13:49:36 adam_b thanks yes I've seen that Jan 11 13:50:04 so then you know that it is expected that most desktops will eat keys Jan 11 13:50:19 and that it'll be the bit of the desktop that handles keyboard shortcuts Jan 11 13:50:55 adam_b well it isn't really clear what the issue is. lxqt has the same behaviour for me Jan 11 13:51:09 no idea about your mouse issues Jan 11 13:51:24 you mean lxqt also eats r etc Jan 11 13:51:31 It only eats b and n Jan 11 13:51:42 Same as xfce Jan 11 13:51:42 you are using gemain branched builds right? Jan 11 13:52:21 or it could be that you've installed both lxqt and xfce and have now got both of them launching both of their key grabbers Jan 11 13:52:23 Yes, but I am running buster with the gemian repo Jan 11 13:52:48 So I know to expect some things to be non working Jan 11 13:53:41 I've not checked buster lately, might be that a newer upstream version of the keygrabber has been released and we need to update our versions to overwrite it Jan 11 13:54:28 can you check the version of lxqt-globalkeys you've got installed? Jan 11 13:56:45 lxqt-globalkeysd is version 0.13.0 Jan 11 13:57:36 It isnt running under xfce Jan 11 13:58:33 our version is 0.13.0-gemian so you should be fine, sounds like its the lxde version of the same thing messing things up for you Jan 11 13:58:59 its an 'apt show lxqt-globalkeys' that'll show the full version for you Jan 11 13:59:25 no idea what lxde calls its key grabber though Jan 11 14:00:18 adam_b 0.13.0+gemian+0~20180531094652.15~1.gbp048e6d Jan 11 14:01:11 yea so it should work fine with lxqt if only the key grabber from some other desktop hadn't weasled its way into being launched by default Jan 11 14:02:20 if you find where cmst is being launched from you can check that same place for other things that involve the word 'key' etc? Jan 11 14:03:00 seems it might be called lxhotkey Jan 11 14:03:29 or that might be the config tool to control the hotkeys where you could remove the definitions for print etc Jan 11 14:11:25 adam_b I'm poking around now Jan 11 14:11:28 thanks Jan 11 15:06:23 What are all the things in /vendor? binaries supplied from mediatek? Jan 11 15:13:58 Well it does not seem to be cmst, though I'm mystified as to what is starting cmst Jan 11 15:29:51 I think cmst is registered as some kind of dbus system service. I'm confused Jan 11 15:45:13 I had a look in xev and it sees keymapnotify events when I press those keys Jan 11 15:45:16 Not key presses Jan 11 15:46:00 Keydown causes focusOut, release causes focusein and keymapnotify events. Bizarre Jan 11 16:55:20 munchausen: on mine I've got a .config/cmst/cmst.conf with run_on_startup=true in it, so that could be why it starts on startup, so not helpful in terms of finding out whats starting your key grabber Jan 11 16:58:13 yes the r key sends a normal r value as you would expect, its only the fn+r that sends the Print value. The bug is with key grabbers that make the unbelievable assumption that the print or similar key has only one function so it asks what is print, then gets told its fn+r, then says well I'll take all r's thank you, and then forever more r and fn+r give you print Jan 11 16:59:45 if you've not found the errant process yet, then start by listing running process owned by your user and kill off key related ones until you get r to be r again Jan 11 17:47:35 adam_b thanks for your help. I've been reading around and it looks as though it could well be related to xfce hidden shortcut settings Jan 11 17:47:57 I started by listing all processes and finding out what the ones I didn't recognise were for, but none are directly key related Jan 11 17:48:42 I assume that in xfce key shortcuts must be managed by one of the main processes Jan 11 17:48:50 It's odd though that it also happens in other DEs Jan 11 17:49:02 Anyway have to leave it for tonight, might get back on it tomorrow **** ENDING LOGGING AT Sat Jan 12 02:59:57 2019