Inside the "tests" folder of gtk+-3.2.3 there's a script called "testgtk".
When you run the script you get a UI with 56 buttons to launch other demo's.
The demo "alpha windows" works but "composited window" only gives a button on a red window with the warning:
Gdk-WARNING **: gdk_window_set_composited called but compositing is
not supported
I'm on Ubuntu Natty, gtk+-3.2.3
Related
Whenever I try to run any Gtk+ Flatpak-ed app on wayland I get error such as:
(porto:3): Gtk-WARNING **: 00:55:13.780: cannot open display: :99.0
(setzer:2): Gtk-WARNING **: 01:01:41.868: cannot open display:
(org.gnome.Maps:2): Gtk-WARNING **: 01:02:18.136: cannot open display:
The problem seems to be that GDK_BACKEND variable is for some reason set to X11. Run following commands to check whether you have the same problem. I'm using gnome maps, but you can use whichever app you like.
flatpak run --command=sh org.gnome.Maps
echo $GDK_BACKEND:$WAYLAND_DISPLAY:$DISPLAY
Your output should be something like wayland-0,x11:wayland-0,:0.0. If it's not you should try experimenting with those variables
export GDK_BACKEND="wayland,x11"
export WAYLAND_DISPLAY="wayland-0"
export DISPLAY="wayland-0"
gnome-maps
Variable changes aren't permanent and are set only until container's shell is closed.
In my case it was a Java app under flatpak refusing to launch with said cannot open display error.
I fixed it by changing "--socket=fallback-x11" to be just "--socket=x11" in the flatpak manifest "finish-args" element.
i have a rcp application that run on windows and linux.
First off all, in windows all is working fine, but when i compile the app on linux i have a lot of this message outputs.
GLib-CRITICAL **: 09:40:58.143: g_base64_encode_step: assertion 'in !=
NULL' failed
Gtk-WARNING **: 09:41:00.169: Negative content height -7 (allocation
1, extents 4x4) while allocating gadget (node button, owner
GtkToggleButton)
the linux version is:
Linux 3.10.0-957.10.1.el7.x86_64 GNU/Linux
In the other hand i have problems with the visualization of the controls, maybe is releated with the other issue.
I try to change the --launcher.GTK_version 2 in the .ini file but the controls problems remains.
login problem
enter image description here
It seems that everything cygwin-related configured and works fine in my Eclipse project, for example Eclipse is able to invoke 'make' or 'gcc', and can even run the compiled binary and show the output in the Eclipse console window.
However, when I try to debug my binary within Eclipse, I get the following error:
Error in final launch sequence:
Failed to execute MI command:
-exec-run
Error message from debugger back end:
During startup program exited with code 0xc0000135.
Failed to execute MI command:
-exec-run
Error message from debugger back end:
During startup program exited with code 0xc0000135.
During startup program exited with code 0xc0000135.
I do able to launch gdb from my Cygwin console, so it is installed correctly (I assume). But why it fails when I try to use it from Eclipse?
For my case, as you say, it turns out that adding the Cygwin bin folder to the PATH variable solves this problem.
I use Eclipse 2020-06 and Cygwin 64bit on Win7 64bit. And installing Cygwin doesn't change the PATH variable currently.
But it is also confused to me that "build" and "run" work fine in Eclipse whithout the Cygwin bin in PATH.
This is the full error message I got after running ionic emulate android
*running cordova emulate android
Running command: /Users/DeadLift/Documents/ionic/myApp/hooks/after_prepare/010_add_platform_class.js /Users/DeadLift/Documents/ionic/myApp
add to body class: platform-android
Running command: /Users/DeadLift/Documents/ionic/myApp/platforms/android/cordova/run --emulator
ANDROID_HOME=/usr/local/Cellar/android-sdk/24.1.2
JAVA_HOME=/Library/Java/JavaVirtualMachines/jdk1.8.0_45.jdk/Contents/Home
/Users/DeadLift/Documents/ionic/myApp/platforms/android/cordova /node_modules/q/q.js:126
throw e;
^
ERROR : No emulator images (avds) found.
1. Download desired System Image by running: /usr/local/Cellar/android-sdk/24.1.2/bin/android sdk
2. Create an AVD by running: /usr/local/Cellar/android-sdk/24.1.2/bin/android avd
HINT: For a faster emulator, use an Intel System Image and install the HAXM device driver
Error: /Users/DeadLift/Documents/ionic/myApp/platforms/android/cordova/run: Command failed with exit code 1
at ChildProcess.whenDone (/usr/local/lib/node_modules/cordova/node_modules/cordova-lib/src/cordova/superspawn.js:131:23) *emphasized text*
at ChildProcess.emit (events.js:110:17)
at maybeClose (child_process.js:1015:16)
at Process.ChildProcess._handle.onexit (child_process.js:1087:5)*
I follow all the above by creating an avd and it give me the same message again.
Thanks.
Vikas's answer is pretty spot on, however (sometimes) just running android avd won't work, which is what I found out after hours of trying to get it working.
When ever I ran android avd in my terminal it would give me the following error:
zsh: command not found: android
This is because I needed to add the Android SDK paths for the platform-tools and tools to my zshrc file (you might be running bash or something else on your terminal).
Simple fix was to add these files to my zshrc PATH environment, You can do this too by using your favourite text editor and depending on what shell you're using.
This link: http://docs.phonegap.com/en/2.8.0/guide_getting-started_android_index.md.html#Getting%20Started%20with%20Android helped me out a hell of a lot getting this fixed.
So I used subl ~/.zshrc (because sublime is my text editor and i've setup symlinks)
I Found my exports PATH and changed it to represent the following:
export PATH="/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Users/dev/.rbenv/versions/2.2.3/bin/ruby:/Users/dev/Library/Android/sdk/platform-tools:/Users/dev/Library/Android/sdk/tools:$PATH"
I then saved the file, closed down sublime and ran source ~/.zshrc in my terminal window, and now I can run android avd and it now opens the Android Virtual Device Manager with no problems.
A reminder your shell might be different to mine (i.e. not running with zsh)and your exports PATH might look different as well, but it's pretty easy to figure out, and the link above will also help if you get stuck.
Actually it is not able to find AVD (Android virtual device). You have to create one.
Type "android avd" from Command Promt to use the graphical manager to setup an emulator image to work with for running your app on. The graphical tool is fairly straight forward to use.
When I click the run as android application it shows the following error:
[2011-05-20 10:32:45 - Emulator] invalid command-line parameter: on.
[2011-05-20 10:32:45 - Emulator] Hint: use '#foo' to launch a virtual device named 'foo'.
[2011-05-20 10:32:45 - Emulator] please use -help for more information
This is most probably due to a space in the path. As Revision 12 is giving this error for everyone. Mine is Revision 12 in Eclipse Indigo Classic.
Please move your android-sdk folder to somewhere so that there doesn't contain any space in the path.
Or, try from command line.
Use below steps -
Right click Project -> Run As -> Run Configure -> Target
Scroll Down
Additional emulator command line option, type
-http-proxy http://10.1.1.10:8080
Restart ur emulator, it will work, and it is working for me too