View Single Post
Posts: 1,101 | Thanked: 1,185 times | Joined on Aug 2008 @ Spain
#424
Originally Posted by many408 View Post
Yes mutch

but

There is now a small problem with Videocamera.

When I start it, it does not get past the "starting camera" stage (unless it times out to standby) until I tap somewhere above the screen in the grey area where the "Videocamera" text is. When I do that, the settings/about/close menu drops down. Another tap gets rid of the menu and shows the camera image(s), with a blanked-out square where the menu was.

More details:

The initial "starting camera" message appears in a white-line frame, which after a short pause to is shifted up about 10 pixels, loosing the top and right lines of the frame and leaving a grey line on the bottom where the bottom white line of the frame was.

If I wait until the app says the camera is on standby and then tap on the little white box it shows me ("tap <box> to activate") almost the same thing happens - "starting camera" in white-line frame, no images BUT there's no upward shift - the top and right lines of the frame do however disappear.

If I wait and do it a second then it does wake up and show images correctly.

In all cases tapping "record" shows a full-screen and it starts recording as it should.

It this a window-priority-thing?
Yes, it is a bug in X window compositing, which has been enabled by telescope.
As workaround you can start the camera app with the following command line:
Code:
(camera &); sleep 5; dbus-send --type=method_call --dest=org.freedesktop.Notifications /org/freedesktop/Notifications org.freedesktop.Notifications.SystemNoteInfoprint string:""
The dbus-send command will cause a small empty notification in the tray, and that will remap the window.
 

The Following User Says Thank You to maacruz For This Useful Post: