| Thread Previous • Date Previous • Date Next • Thread Next |
Thank you for taking the time to report this bug and helping to make Ubuntu better,
* can you reproduce it ?
* if so than which version are you on ?
** Changed in: gwibber
Status: New => Incomplete
--
You received this bug notification because you are a member of Gwibber
Bug Heros, which is subscribed to Gwibber.
https://bugs.launchpad.net/bugs/871819
Title:
Gwibber will not find python2.7, when /usr/bin/python is linked to an
earlier version
Status in Gwibber:
Incomplete
Bug description:
I am running Ubuntu 11.04 linux for some specific purpose where python 2.7 does not work.
I am using:
sudo update-alternatives --install /usr/bin/python python /usr/bin/python2.6 10
sudo update-alternatives --install /usr/bin/python python /usr/bin/python2.7 1
sudo update-alternatives --set python /usr/bin/python2.6
to set python to what I want (python-2.6).
This seems to be the preferred way to select python version.
When I do this, then gwibber will break the upgrade function.
Even if I reset using
sudo update-alternatives --set python /usr/bin/python2.7
upgrade fails, since this ssems to require that
/usr/bin/python is linked to /usr/bin/python2.7
The method above creates a link from
/usr/bin/python to /etc/alternatives/python
and another link from
/etc/alternatives/python to /usr/bin/python2.7
which should work, but this still breaks the upgrade.
It is not only the gwibber upgrade that is broken.
The GUI upgrade handler is frozen until
/usr/bin/python is set to /usr/bin/python2.7.
Also, It it not possible to deinstall gwibber (until you create the link
/usr/bin/python -> /usr/bin/python2.7
I think that if /usr/bin/python2.7 is installed on the system,
then gwibber should work, regardless if /usr/bin/python
is set to this or not.
Possibly with the use of an environment variable...
To manage notifications about this bug go to:
https://bugs.launchpad.net/gwibber/+bug/871819/+subscriptions
| Thread Previous • Date Previous • Date Next • Thread Next |
