Bug 1272103 - Error message appearing when running vim : "Unable to import powerline, is it installed?" but everything looks fine.
Error message appearing when running vim : "Unable to import powerline, is it...
Status: CLOSED ERRATA
Product: Fedora
Classification: Fedora
Component: powerline (Show other bugs)
22
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Andreas Schneider
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-10-15 09:56 EDT by Fujisan
Modified: 2015-11-09 19:24 EST (History)
1 user (show)

See Also:
Fixed In Version: powerline-2.3-1.fc23 powerline-2.3-1.fc22
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-11-09 16:54:07 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Fujisan 2015-10-15 09:56:35 EDT
Description of problem:
When I start vim (or gvim), I get the following error message on the terminal:

$ vi /usr/share/vim/vimfiles/plugin/powerline.vim
Traceback (most recent call last):
  File "<string>", line 4, in <module>
ImportError: No module named 'powerline'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
  File "<string>", line 9, in <module>
ImportError: No module named 'powerline'
An error occurred while importing powerline module.
This could be caused by invalid sys.path setting,
or by an incompatible Python version (powerline requires
Python 2.6, 2.7 or 3.2 and later to work). Please consult
the troubleshooting section in the documentation for
possible solutions.
Unable to import powerline, is it installed?
Press ENTER or type command to continue


Version-Release number of selected component (if applicable):
powerline-2.2-2.fc22.x86_64
vim-powerline-2.2-2.fc22.noarch

How reproducible:
Always

Steps to Reproduce:
1. Just run vim in terminal
2. message appears on terminal
3. press ENTER and everything looks fine. Powerline has been imported as usual.

Additional info:
I didn't have the problem with the previous release of powerline 2.1-1.

The message "Unable to import powerline, is it installed?" comes from file /usr/share/vim/vimfiles/plugin/powerline.vim (line 112) in vim-powerline package.
Comment 1 Fedora Update System 2015-10-20 10:29:39 EDT
powerline-2.3-1.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2015-9d6632c476
Comment 2 Fedora Update System 2015-10-20 10:44:13 EDT
powerline-2.3-1.fc22 has been submitted as an update to Fedora 22. https://bodhi.fedoraproject.org/updates/FEDORA-2015-30494f69c4
Comment 3 Fedora Update System 2015-10-20 17:57:21 EDT
powerline-2.3-1.fc23 has been pushed to the Fedora 23 testing repository. If problems still persist, please make note of it in this bug report.
If you want to test the update, you can install it with
$ su -c 'dnf --enablerepo=updates-testing update powerline'
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2015-9d6632c476
Comment 4 Fedora Update System 2015-10-26 14:31:26 EDT
powerline-2.3-1.fc22 has been pushed to the Fedora 22 testing repository. If problems still persist, please make note of it in this bug report.
If you want to test the update, you can install it with
$ su -c 'dnf --enablerepo=updates-testing update powerline'
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2015-30494f69c4
Comment 5 Fedora Update System 2015-11-09 16:54:05 EST
powerline-2.3-1.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report.
Comment 6 Fedora Update System 2015-11-09 19:24:11 EST
powerline-2.3-1.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.

Note You need to log in before you can comment on or make changes to this bug.