I am having real problems installing any kind of version of Orange either on Windows 7, Windows 8 or Ubuntu.
I used to have a version of Orange working on a different computer and I believe it might have stopped working when I installed enthought canopy. Both my windows 7 and 8 machines also have had enthought installed. I have tried uninstalling and reinstalling both systems but I can not get it to work.
In windows the icon appears on the desktop but it does nothing when I click on it, the target of the icon is 'C:\Users\localadmin\AppData\Local\Enthought\Canopy\User\pythonw.exe -m Orange.OrangeCanvas.main'
In linux (ubuntu) I have installed the normal version of Orange, but half the widgets do not appear, even smiple ones like view a data table etc. It also looks like an older version then what I used to have on Windows.
I also installed Orange3 on ubuntu but again this did not have all the widgets I used to have on my old windows version of Orange and it generally did not seem finished.
Does anyone know of any problems with having enthought and orange installed? What can I do to resolve this? (I have uninstalled enthought but Orange still does not work)
Run Orange canvas from the command prompt
C:\Users\localadmin\AppData\Local\Enthought\Canopy\User\python.exe -m Orange.OrangeCanvas.main -l3
or with a standard python install
C:\Python27\python.exe -m Orange.OrangeCanvas.main -l3
This should give you more information about the error.
I had a similar problem on a Windows machine. I installed Orange and it reported the installation to be correct. However, when I clicked on the desktop icon, nothing happened. If I tried to run Orange from the command prompt, I got no errors, warnings or anything, but the program still didn't start.
Eventually I uninstalled Python and all Python libraries. I had several previously installed Python libraries/packages before I installed Orange. Removing all and performing a reinstallation of Orange and the required libraries fixed the issue.
Related
I have been using Enthought Canopy for quite a while now with the academic license. Till today it was working fine, today I got the request to update Canopy. I assume to version 1.7 since that seems to be the latest. After installing and restarting the computer no error message but Canopy does not open anymore. Just nothing happens when I try to open Canopy, Package Manager, Code Editor nevertheless the Canopy cmd seem to be fine.
Now it is getting interesting, I can still start Ipython/Jupyter notebooks via regular win cmd and run python scripts with Canopy. Although the files are no longer marked as to be opened by canopy with the blueish symbol and do not open on click or double click as before.
import sys
print sys.prefix
C:\Users\MYNAME\AppData\Local\Enthought\Canopy32\User
Consequently, I can work and I am hesistant to try fixes since I am afraid to make it even worse. Reinstall is is only okay if I can get back all my installed libraries with ease.
However, I found very convenient to use canopy since I was able to start ipython notebooks directly in the file explorer by double click instead of going through the cmd. Furthermore, the Package Manager is also a quite handy tool, I really would like to have both back working fully.
Thank you for your suggestions:
System:
Windows 8, 64-bit operating system
Installed Version of Canopy:
`Canopy32\\App\\appdata\\canopy-1.6.2.3262.win-x86\\lib`
(consistent in sys path and control panel - program and features)
The Canopy Support Directed me to a working solution:
Note, uninstalling Canopy does not affect your installed package set.
You have two choices:
A) It would be cleanest to start with the up-to-date package set in
Canopy 1.7.
To do that, then after you uninstall Canopy 1.6, but before you
install 1.7, delete directories:
C:\Users\MYNAME\AppData\Local\Enthought\
C:\Users\MYNAME\AppData\Roaming\Enthought\ B) However if you have a
number of non-Enthought packages installed into Canopy, which would be
troublesome to re-install, you could choose to delete the above
directories and their subdirectories, with the exception of this
directory C:\Users\MYNAME\AppData\Local\Enthought\Canopy32\User\
which is where your existing packages are installed.
If you do this, then after restarting you'll be running Canopy 1.7 but
with your pre-existing package set from Canopy 1.6.2.
I chose to deinstall 1.6. and install 1.7.1 and I did not delete the directory with the external libraries.
I did a yum remove fontconfig not knowing that it removes all packages that depend on it as well. That's 300 packages that have been removed.
I have tried to reverse the process by running yum remove fontconfig again on another similarly-configured CentOS 5.5 machine and reinstalling those packages in the output of the command.
The Gnome logon screen is stuck at loading cursor.
My Gnome is still broken and I have switched to KDE for the time being. I can use a weird hybrid of Gnome Desktop and KDE window manager where the UI is Gnome but the desktop is not clickable and there's KDE apps instead of the Gnome ones.
/etc/sysconfig/desktop
DESKTOP="GNOME"
DISPLAYMANAGER="KDE"
Using the KDE login to choose Gnome also gives me this weird KDE/Gnome hybrid.
I have reinstalled the Gnome-related packages several times and it doesn't fix the issue.
yum should have given you an indication of the volume of packages that it was going to remove and should have given you the chance to abort the attempt (unless you used -y which, I imagine you now realize, you shouldn't).
There's no need to attempt to "reproduce" the problem to find the list of packages. The yum log file /var/log/yum.log will tell you everything that yum installed and removed.
On CentOS 6 and newer yum has a history command that can also display this (and other) information.
I have a networked home directory, which is used by linux and OSX machines. I want to install the linux and OSX versions of Canopy so that I can use it from any machine.
I first installed the linux version by running the '.sh' file. Despite asking where I wanted to put Canopy, the installer puts most of the stuff in ~/Library/Enthought/Canopy_64bit/. This is a problem because later, when I try to install Canopy in OSX, it just assumes again that Canopy is in ~/Library/Enthought so somethings will be overwritten but other binaries will be kept untouched, and the whole thing doesn't work in OSX or Linux.
Is there a way to force the linux version to be installed somewhere else? From the documentation it seems that it used to be ~/Enthought, but it doesn't work for me.
I suspect the problem is with having your locations.cfg file in ~/.canopy which is shared by both the versions of Canopy. Can you try the following:
Install the Linux version of Canopy and run it.
Remove your ~/.canopy/locations.cfg
Install your OSX version, and see if that works?
When you go back to running your Linux version, it'll again prompt you for install locations for the user environment, where you could select the old Linux install location.
Even if this works, I'm not sure, this would be too convenient. Let me know, how it goes. :)
I was previously running Enthought EPD 7.3.2, but switched over to Canopy (academic license). I completely uninstalled EPD before running the Canopy install.
After installing Canopy, I have a shortcut to IDLE in the Canopy start menu folder, but I can't get it to launch (I click it and nothing happens). Tried uninstalling and reinstalling Canopy, but am having the same issue.
Running the 64-bit version of Canopy on Win7, 64bit.
I had a similar problem and found a very simple solution. Try it out and see if it works in your situation too. There is a directory for the Canopy installation:
C:\Users\\AppData\Local\Enthought\Canopy\App\appdata\canopy-1.7.4.3348.win-x86_64\Lib\idlelib
Find “idle.ico” file there, copy and paste it into “Icons” subdirectory.
This fixed the problem!
Canopy 1.0 and 1.0.1 versions have problems with tcl and TKinter, and IDLE doesn't work. This should be fixed in an update, which is just round the corner.
As an afterthought, is there a specific reason you wish to use IDLE? Canopy's editor comes integrated with an IPython console (along with many other goodies), which gives a much better user experience while programming, IMO. (Disclaimer: I work for Enthought)
Yesterday I installed Teamviewer 7 on my Centos 5.8 desktop. After a reboot, am not able to see the login screen. Only a blue color screen is visible.
I read https://superuser.com/questions/403548/os-x-stuck-at-blue-screen-after-installing-teamviewer-host-and-rebooting?rq=1
But how do I do that on Centos?
I know that to login to Single User Mode, we need to press a key while the os boots up. And then type single in the cmd. And then?
Once in Single User Mode, you can try to remove TeamViewer from your system.
For example, if you have installed TeamViewer by running the rpm -ivh teamviewer_linux.rpm command, you can run the rpm -e teamviewer_linux command to uninstall it.
I don't think that the Mac OS link you've referred to can be very useful in your case.
If you peek into the teamviewer_linux.rpm (for example by running the command rpm -qpl teamviewer_linux.rpm) you won't find any "Launch Agents and Daemons", since on CentOS TeamViewer is wrapped around a Windows Emulator (wine).
By default the TeamViewer files gets installed in the /opt/teamviewer folder; the only exception is the startup script /usr/bin/teamviewer7.
Finally, the rpm post-installation script does nothing more and nothing less than create a desktop icon and add a menu entry, so I can't really understand how the TeamViewer installation could have broken your system.