I'm using Linux Mint, and I've downloaded XUL 1.8.0.4. Extracted it to the /opt/ dir, made symbolic link to /usr/bin/xulrunner, and I still can't run XUL apps.
When I type xulrunner -version in terminal, I got message:
Mozilla XULRunner 1.8.0.4
When I type whereis xulrunner i got message
xulrunner: /usr/bin/xulrunner /usr/lib/xulrunner /usr/bin/X11/xulrunner
So it should work, but when I go in the app folder and run xulrunner application.ini nothing happens.
Does your application have any files other than application.ini ? I think you need at least a preferences file (defaults/preferences/prefs.js) and a chrome.manifest (or an omni.ja with these in it) to make xulrunner actually do anything. If you just feed it a lone application.ini it parses the ini, goes looking for more application files, then exits when it finds none.
Related
Running PyInstaller v3.2 on Ubuntu 16.04, is it possible to get my bundled application to open a console for stdout? On Mac and Windows I can get this to work, as outlined in the options documentation. But nothing is mentioned for Linux. I've tried playing around with the -c flag, but that does not seem to have any effect. I also tried bundling it as a single file (-F) versus a directory, but neither seems to open a console for stdout...
Just for future reference, in Linux if you run a bundled app from the command line like a script, it will automatically use that same terminal as stdout ...
I have used Nix package manager to install Abiword in a Slackware/Salix install with Mate desktop. The application runs fine but it has not appeared in the main Menu. Is this usual for applications installed by Nix?
I got this working on openSUSE plasma-desktop by adding the following to my bashrc
export XDG_DATA_DIRS=~/.local/share/:~/.nix-profile/share:/usr/share
cp -f ~/.nix-profile/share/applications/*.desktop ~/.local/share/applications/
Then logging out or running kbuildsycoca4 rebuilds the start menu.
When I only set the XDG_DATA_DIRS, the icons would appear in the start menu. However kdelibs is trying to make those .desktop files executable and add a xdg-open shebang to them, which does not work since .nix-profile is not writeable.
Thus it was also necessary to copy the desktop files to a ~/.local/share/applications/, which however also needs the XDG_DATA_DIRS set to ~/.nix-profile, because the application icons still reside there.
I am trying to run a .run file in cygwin, but I always seem to get this error:
Unable to start '~.run': There is no application associated with the given file name extension.
I needed to be a superuser, so I tried using the command: cygstart --action=runas "$#"
I read somewhere that cygstart is for invoking registered Windows handler, so this may be the problem, but I am unsure. Is there any way that I can run my .run file as a superuser using cygwin?
Well, as has been said, no application is associated with .run files on your
system. So you can do that one of two ways
Call the file with the program, example
cygstart notepad.exe ~.run
Tell the registry what to do with unknown extensions
Windows Registry Editor Version 5.00
[HKEY_CLASSES_ROOT\Unknown]
#=""
[HKEY_CLASSES_ROOT\Unknown\shell\Open\command]
#="notepad.exe \"%1\""
This question is not related to Cygwin but rather to Windows. cygstart works the same as Windows' start. That means, if you use [cyg]start file.extension it works very similarly as if you double-click on that file in Windows Explorer.
Therefore if you configure Windows to do what you need when you double-click on your *.run file, cygstart will work fine too.
I think that easier is to use appropriate extension which Windows already knows. It depends on what you have inside your *.run file. If it's executable, use exe extension, if it's batch script, use cmd or bat, if it's JavaScript, use js etc.
If you use Linux or some derivation, you need to execute the .run file with an absolute path, even if you have already navigated to the appropriate directory containing the file. See here:
http://the-chronicon.blogspot.com/2011/08/execute-run-file-in-current-folder-from.html
I tried export XRE_CONSOLE_LOG as told in this page, but had no result.
Also, I would like to see in a file all errors I see in my console (as XPCom errors, not only javascript errors).
--update
I'm Running Xulrunner 1.9.2 on Ubuntu 10.04.
If you are seeing chrome errors but they do not get written to the file you indicated, maybe the file path contains an error? What OS are you on?
Are you correctly set all developer environment options?
I've been trying for some time to use the ExternalInterface.call method in flash, to no avail (see here: actionscript + javascript here: Using ExternalInterface in Flash and here: Flash trace output in firefox, linux) and now I'm trying to trace ExternalInterface.available. So far my best option seems to be FlashTracer for firefox, except that I have to have flash player 9 installed. I've removed my old flash player and downloaded the appropriate files (http://download.macromedia.com/pub/flashplayer/updaters/9/flash_player_9_linux_dev.tar.gz). According to the readme included these are the steps for installation:
Installing the debugger plugin tar.gz using Install script:
o the debugger plugin is located at:
./plugin/debugger/install_flash_player_9_linux.tar.gz
o Unpack the tar.gz file
o In terminal, navigate to the unpacked directory and enter:
+ $ ./flashplayer-installer
+ Click Enter key and follow prompts
except there's no file called flashplayer in the debugger directory. Anyone else ran into this? How can I install flash player 9 debugger on my Ubuntu system?
If you're using something like Ubuntu, the Flash plugin is probably a system wide thing. Under Ubuntu 8.10 for example, I have it at:
/usr/lib/flashplugin-installer
additionally you'll find at:
/etc/alternatives/
links to it, so you can change which .so is used depending on the user.
The easiest thing you could probably do if the ./flashplayer-installer file doesn't exist (though it does in mine) is to copy the debug flashplayer library to this directory. e.g:
root#me:/usr/lib/flashplugin-installer# mv libflashplayer.so libflashplayer.non-debug.so
root#me:/usr/lib/flashplugin-installer# cp ~jamie/Adobe_Flex_Builder_Linux/Player/linux/install_flash_player_9_linux/libflashplayer.so libflashplayer.debug.so
root#me:/usr/lib/flashplugin-installer# ln -s libflashplayer.debug.so libflashplayer.so
I haven't seen the issues you have, and perhaps your requirements restrict you to an older version, but I've had great success with flashplayer 10's debugger. You might try this one and see if it works.
Edit: Ahh, I just noticed one very pertinent statement you made: you require flashplayer 9. Sorry =(
Edit 2: I just had the same thing happen to me on Linux. When I extracted the tar.gz from Adobe, the installation script wasn't present. This said, I was able to get the debugger version of 9 installed anyway.
When you extracted, did you see a libflashplayer.so file? I didn't have an installation script, but I did get this file. If so, all you need to do is this:
Close all instances of Firefox
Backup your current libflashplayer.so module: ~/.mozilla/plugins/libflashplayer.so.org (this way, if something goes wrong, you can always put it back)
Copy the version you extracted from the Flash player download to the same plugins directory: cp /path/to/vers/9/libflashplayer.so ~/.mozilla/plugins/
Restart Firefox, open a Flash app, and right-click to check for the version
These steps worked perfectly for me, and I was able to run Flex Builder's debugger in Linux. Hope it works for you!
One way you can do it is downloading the flex 3 SDK for linux. When you download it you'll get a couple of tar's. You can find this in ~/flex_sdk_3/runtimes/10 if you want to install the flashplayer 10 and ~/flex_sdk_3/runtimes/lnx/ if you want the flashplayer 9. Uncompress those files (flashplayer.tar.gz and libflashplayer.so.tar.gz with tar -xvf). Now cp libflashplayer.so the file to /usr/lib/mozilla/plugins/ and if you want create symbolic links (ln -s flashplayer /usr/local/bin to have the player on your path
A tip for anyone who searches for this like I did... find out where libflashplayer.so currently is on your system:
sudo locate libflashplayer.so
Mine was in /usr/lib/flashplugin-installer/
Once I replaced that file with the debug version of the file, Firefox reported that I had the debug version of the player.
I also had the same issue with flash player debugger. I followed the instructions given by bedwyr. It worked for me. To make it work, you create a directory named 'plugins' into ~/.mozilla if plugins directory is not found.
mkdir ~/.mozilla/plugins
Then I copied libflashplayer.so to plugins directory. Now flash player debugger worked for my Flex Builder's application.