Difference between revisions of "Installation Problems"

From PANGU Wiki
Jump to: navigation, search
m (MartinDunstan moved page Installation to Installation Problems without leaving a redirect: This page only deals with installation problems)
 
(2 intermediate revisions by the same user not shown)
Line 1: Line 1:
 
__FORCETOC__
 
__FORCETOC__
This page provides answers to issues that users have encountered when installing PANGU.
+
This obsolete page provides answers to issues that users have encountered when installing PANGU.
 +
 
 +
This page has been replaced by the [[FAQ]] page.
  
 
== Error: not authorised ==
 
== Error: not authorised ==
Line 19: Line 21:
 
If the contents of the licence file are not displayed then the environment variable is wrong. Correct the error and remember to close the terminal and open a new one.
 
If the contents of the licence file are not displayed then the environment variable is wrong. Correct the error and remember to close the terminal and open a new one.
  
== QGtkStyle was unable to detect the current GTK+ theme ==
+
== Other known issues ==
This error might occur when running the PANGU Qt viewers under Linux when using XFCE, LXDE or KDE desktops with Ubuntu 18.04. This affects any Qt application, not just PANGU.
+
Please check the [[Known Issues]] page for other problems which might be encountered.
 
+
The simplest solution is to define the following environment variable:
+
 
+
GTK2_RC_FILES="$HOME/.gtkrc-2.0:/etc/gtk-2.0/gtkrc"
+
 
+
If neither of those configuration files exists then create a text file called .gtkrc-2.0 in your home directory and add the following line of text to it:
+
 
+
  gtk-theme-name="GTK+"
+
 
+
Save the file and the issue ought to be resolved.
+
 
+
For more details see [http://alien.slackbook.org/blog/running-vlc-in-xfce/ http://alien.slackbook.org/blog/running-vlc-in-xfce/]
+
 
+
== Failed to load module "canberra-gtk-module" ==
+
This error might occur when running the PANGU Qt viewers under Linux when using XFCE, LXDE or KDE desktops with Ubuntu 18.04. This affects any Qt application, not just PANGU.
+
 
+
The problem is due to the specified module not being installed on your system.
+
 
+
Ubuntu users might be able to resolve this issue by using this command:
+
sudo apt install libcanberra-gtk-module
+
 
+
CentOS users might need to use one of these commands instead:
+
sudo yum install libcanberra-gtk2
+
sudo yum install libcanberra-gtk3
+
 
+
See [https://askubuntu.com/questions/208431/failed-to-load-module-canberra-gtk-module https://askubuntu.com/questions/208431/failed-to-load-module-canberra-gtk-module] or [https://askubuntu.com/questions/971560/what-is-the-purpose-of-canberra-gtk-module https://askubuntu.com/questions/971560/what-is-the-purpose-of-canberra-gtk-module] for more details.
+

Latest revision as of 14:30, 14 June 2021

This obsolete page provides answers to issues that users have encountered when installing PANGU.

This page has been replaced by the FAQ page.

Error: not authorised

The most common reason for this problem is failure to open a new terminal window after setting the PANGU_LICENCE_FILE environment variable. If you don't have a licence file for your machine then you must request one via the licence request page on the pangu.software site.

Note: used licence file ′′

If the licence file used by PANGU is reported as the empty string ′′ then you probably forgot to close the terminal/command window and open a new one after setting the PANGU_LICENCE_FILE environment variable. Environment variable changes will only apply to programs that are started after the change is made. So any existing windows will use the previous setting.

The specified licence file is not found

Check that the PANGU_LICENCE_FILE environment variable is set correctly. At a Windows/DOS/cmd.exe prompt type:

type %PANGU_LICENCE_FILE%

For Linux users type:

cat $PANGU_LICENCE_FILE

If the contents of the licence file are not displayed then the environment variable is wrong. Correct the error and remember to close the terminal and open a new one.

Other known issues

Please check the Known Issues page for other problems which might be encountered.