When you make any attempt to use the on-screen keyboard, the system freezes and does not respond anymore. Tested on basyskom-plasma-active-archos-gen9-pvr-tablet-mer-testing-120817-1928 as well as with the omaps image. The screen goes black and there is no way to recover the system but hard reboot. Last week with testing and devel images, it was the same problem but the screen did not go black : "QML error" was written on the top link corner and nothing could still happen but the cursor in the text field (|) blinking. Reproducible: Always Steps to Reproduce: 1. Boot basyskom-plasma-active-archos-gen9-pvr-tablet-mer-testing-120817-1928 on Archos G9 2. Choose to type anything in any textfield Actual Results: The screen goes black andthe system freezes for ever. Expected Results: The keyboard appears, no freeze. May be related with bug #304875 It's a nasty bug, it makes the image hardly usable, even for testing.
Unable to reproduce on following images: basyskom-plasma-active-archos-gen9-pvr-tablet-mer-devel-120819-1857.tar.bz2 basyskom-plasma-active-archos-gen9-omapfb-tablet-mer-devel-120819-1800.tar.bz2 Tried on konsole, active webbrowser and active filebrowser.
I am able to reproduce the black screen problem in VirtualBox when using kwin's OpenGL backend. It does not happen when I use XRender backend. Maliit creates a fullscreen keyboard and uses transparency to show what is beneath the keyboard, when transparency does not work the keyboard's background, which is black by the way, covers the entire screen, that may be the problem. If you are able to hook up a USB keyboard can you check if compositing is active using the command below? qdbus org.kde.kwin /KWin org.kde.KWin.compositingActive
On following images the 'qdbus org.kde.kwin /KWin org.kde.KWin.compositingActive' results 'true': basyskom-plasma-active-archos-gen9-pvr-tablet-mer-devel-120819-1857.tar.bz2 basyskom-plasma-active-archos-gen9-omapfb-tablet-mer-devel-120819-1800.tar.bz2 The used 'kwinactiverc' contains 'Backend=XRender' in both images.
I tried with the basyskom-plasma-active-archos-gen9-pvr-tablet-mer-testing-120819-1926, the bug still occurs. Screen goes lack and there is no way to do anything else : the power button didn't show up. I don't have an USB keyboard but I can give you log or config files. The kwinrc is this (I didn't find any kwinactiverc) : ----- [Compositing] OpenGLIsUnsafe=false [Desktops] Name_1= Number=1 [TabBox] LayoutName=window_strip -------
Regarding compositing, I have two other issues : the task siwtcher is black with the icons in place of the screen miniatures and when you launch an app, it the focus remain on the "desktop" and not on the newly launched app. You've got to tap it in the activity switcher to see it. Maybe, it can help the diagnose.
the backend is set in /usr/share/kde4/config/kwinactiverc. What you described looks like what I see here when compositing is disabled, so that must be your prolbem. At least basyskom-plasma-active-wetab-exopc-tablet-mer-devel-120819-2015.iso set it to OpenGL instead of XRender.
Created attachment 73341 [details] My kwinactiverc [Compositing] AnimationSpeed=3 Backend=XRender DisableChecks=true Enabled=true GLDirect=true GLLegacy=false GLTextureFilter=2 GLVSync=false HiddenPreviews=5 OpenGLIsUnsafe=false UnredirectFullscreen=true XRenderSmoothScale=false
Could you try a 'rm -rf <path of mounted archos rootfs>' before executing the 'tar' deploying command? Maybe your system is affected by some artefacts of an older installation. I'm using 'rm -rf <path of mounted archos rootfs>' before updating the rootfs on archos and I'm unable to reproduce the black screen caused by broken compositing. In case its does not help, the 'dmesg' output of your machine could be usefull.
I install the image on the external sdcard. Before each install I remove everything with Dolphin (Shift+Del) want I had a bad previous experience with the rm command (I once rm all my /home by error, wrong path... ;-) ). How can I get the "dmesg" output without keyboard? An autostart script?
The following desktop file will trigger the collection of much more usefull system informations. All needed parts like 'generate-system-output.sh' are already pre installed and the resulting log will be stored on '/home/mer/collected-system-infos.txt' home/mer/.kde/Autostart/get-system-info.desktop <snip> [Desktop Entry] Comment= Exec=/usr/bin/generate-system-output.sh > /home/mer/collected-system-infos.txt GenericName= Icon=exec MimeType= Name=collect system infos Path= StartupNotify=true Terminal=true TerminalOptions= Type=Application X-DBUS-ServiceName= X-DBUS-StartupType=none X-KDE-SubstituteUID=false X-KDE-Username= <snap> chmod 777 home/mer/.kde/Autostart/get-system-info.desktop
Created attachment 73353 [details] Infos collected by the script /usr/bin/generate-system-output.sh Nice script Maurice.
Sorry, I have overseen you are using and filing bugs for the Archos 'testing' image and I'm talking about 'devel' images. Sadly the 'testing' project which is exactly planned for this purpose is mostly outdated and by this you are running into those issues. We are missing people who like to help with maintaining the 'testing' project in cases something is working really great on 'devel' project (by sync). At the moment the best we have are the 'devel' based images.
Created attachment 73371 [details] Infos collected by the script /usr/bin/generate-system-output.sh (devel image) I have tested the last devel image (pvr from 20120819). The compositing is fine but the problem with the keyboard persists, like with the image from two days ago: - Click in a text field - Result : "Error loading QML" in the top left corner. No black screen but no keyboard, no touch possible, the whole system freezes. Hard shutdown compulsory. In attachment the new infos gotten from the script generate-system-output.sh
Is there not any developper who use the Archos G9 and Basyskom's image and who could confirm the bug? It seems software and not hardware related (QML error).
Created attachment 73461 [details] Infos collected by the script /usr/bin/generate-system-output.sh (devel omapfc image 24/08/2012) I have tested on the new image basyskom-plasma-active-archos-gen9-omapfb-tablet-mer-devel-120824-1800. The problem persists : "Error loading QML". Another strange thing maybe related: Some buttons don't react on tap. They have a special look, not like standard Oxygen buttons. Example the "Change position" from the position applet, the buttons or icons from the "add widget" dialog from an activity. Maybe is it all this a bug with QML? My two cents…
Bug still present on basyskom-plasma-active-archos-gen9-pvr-tablet-mer-devel-120826-1901
I have now a USB keyboard. When I plug it in, I can type but it still gives the message "Error loading QML" in the top-left corner (he probably tries to load maliit at the same time), but I can still tap on OK or other classic buttons. Then, after a few taps the topbar disapeared. I'll try with the omap version to see if that also occurs. Please let me know if I giving an output (like dmesg) can be usefull.
I have found on the two last weekly devel images a sort of workaround with a USB keyboard : when you tap on a text field for the first time, the "Error loading QML" appears but you can use the keyboard to fill in the field. Then it is impossible to tap on "OK" for example but you can do it with the keboard. But, if you can write for the first time of your session with the keyboard without having to tap (only with the keyboard), then the "Error loading QML" will not appear any more and the on-screen keyboard comes up...
Created attachment 73782 [details] dmesg output after workaround with the USB keyboard (comment 18)
The workaround of comment 18 does not work anymore on the last images (I couldn't reproduce it). Not any progress sinds weeks.
Dis(In reply to comment #20) > The workaround of comment 18 does not work anymore on the last images (I > couldn't reproduce it). > > Not any progress sinds weeks. Did you plug the keyboard via backside 'G3-Stick' via USB Hub or did you use the small UBS otg and a adapter? I will take a close look to the Archos image today.
Thanks for the reaction. I plugged it with the micro USB, aside. The 3G key does not work with a normal USB keyboard. The keyboard works well on the latests images. But the "Error loading QML" shows up and prevent for the touch actions to be performed. The only way out is "Crtl+Alt+Del" on the keyboard to have the dialog to suspend/stop it or the powerbutton to show the lockscreen and then shut down. Some times it seems that the "Error loading QML" disappear after a few minutes. By the way the other maybe related bugs hereunder still occurs: Bug 304876 - Add item to an activity, window does not respond Bug 305859 - Buttons/links/star do not react to touch on Share/Like/Connect Bug 304875 - Creating / Editing an activity, window does not respond
We pushed a workaround (thanks to notmart) to the Mer based devel and release project for following Bugs: Bug 304876 Bug 304875 Sadly I'm not able to repoduce this Bug on my hardware but maybe this workaround will help too. Here a URL for a rc3 image which is in sync with the current Wetab/ExoPC image and containing this workaround (upload is in progress): http://share.basyskom.com/plasma-active/deployment/archos-gen9/tablet/mer/testing/ Great thanks for your feedback!
The bug has disapeared with the new rc3 image on Archos G9.Thanks for it.