View Single Post
Posts: 3,328 | Thanked: 4,476 times | Joined on May 2011 @ Poland
#3189
@saponga: see #3181

Originally Posted by sulu View Post
I believe it may be related to this bug report. [1]
If so, it wouldn't be a gdb problem but rather the discovery of a dirty openssl trick via gdb.
This happens only when launching via debbie and only in gdb. If I launch transmission-gtk, then a couple of warnings are shown and then I get a segmentation fault. [1] On the other hand, if I launch transmission-gtk through gdb, SIGILL is emitted before anything is written to the terminal. So it must be connected with gdb

Originally Posted by sulu View Post
I think I know what you mean.
By default Maemo's $HOME directory is mounted into ED.
I don't like the idea of this because it tends to create confusion (at least in my head) which config belongs to which OS.
So I made ED not do that a long time ago and I'm not really testing the default case anymore.
Yep, but my $HOME is mounted (which I find great, since I can use my files from Fremantle) and there's no styling.

Originally Posted by sulu View Post
Actually it does, but only for a brief moment. During the window buildup sequence it loses the focus immediately to the underlying Maemo CLI. If you start a program via debbie from a terminal and try to input some characters you'll notice that the characters actually end up in the terminal.
The problem is, that you can't get the keyboard focus back to the window via a mouse click (for reasons I don't know). You need your WM to do that. This is what the script does, while most of its "intelligence" is not in switching the focus but in finding the right window.
Originally Posted by sulu View Post
Can you post those two files please?
They are in the package
Code:
$ dpkg -L easy-deb-chroot | grep "kbdactive\|xbind"
/usr/share/applications/hildon/xbindkeys.desktop
/home/user/.xbindkeysrc
/home/user/.kbdactive
Originally Posted by sulu View Post
Sure! If you know how to identify the window (not the app).
One easy way is by window title. The problem with this is that multiple windows may have the same name or that a window title is changed by its application. The more robust way, which is used in the script is via window id.
So, a dirty hack assuming there's only one window open. Feel free to improve it. At best a list of windows called "Mnemosyne" should be done and each of the windows fixed.

Code:
mnemosyne &
while [[ $(wmctrl -l | grep Mnemosyne) == "" ]]; do sleep 0.1; done
WINID=`wmctrl -l | grep Mnemosyne | awk '{print $1;}'`
echo $WINID
fixkbd $WINID
Is there any sensible way of finding the window id of the just-launched window?

Still, the problem is that is works only for the parent window. The children windows created by the focused parent remain unfocused. Besides, if I create a new window and gain focus, the parent loses its focus. So it's still far from what's desired.

Btw. LXDE stopped supporting rotation. In the old times with forced rotation I could get the desktop with a portrait resolution. Now not, the desktop stays in the old resolution so is cut off.

[1] http://paste.ubuntu.com/11227096/
__________________
If you want to support my work, you can donate by PayPal or Flattr

Projects no longer actively developed: here

Last edited by marmistrz; 2015-05-19 at 16:02.