Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#40320 - [pitivi] Does not start
Attached to Project:
Community Packages
Opened by Alexandru Băluț (aleb) - Monday, 12 May 2014, 10:34 GMT
Last edited by Doug Newgard (Scimmia) - Monday, 12 May 2014, 16:54 GMT
Opened by Alexandru Băluț (aleb) - Monday, 12 May 2014, 10:34 GMT
Last edited by Doug Newgard (Scimmia) - Monday, 12 May 2014, 16:54 GMT
|
DetailsDescription:
App does not start (because the configparser python module is not available). pitivi-0.93-3 Steps to reproduce: $ pitivi Traceback (most recent call last): File "/usr/bin/pitivi", line 137, in <module> _run_pitivi() File "/usr/bin/pitivi", line 116, in _run_pitivi import pitivi.application as ptv File "pitivi/application.py", line 31, in <module> from pitivi.effects import EffectsHandler File "pitivi/effects.py", line 51, in <module> from pitivi.settings import GlobalSettings File "pitivi/settings.py", line 23, in <module> from configparser import SafeConfigParser, ParsingError ImportError: No module named configparser |
This task depends upon
Edit: I just confirmed that the package itself has "from ConfigParser import SafeConfigParser, ParsingError", which should work fine in py2. Notice the camel case. Have you been using Git HEAD or something?
Very tempted to just close this...