| Summary: | Latest python-coherence update breaks totem's dlna-upnp plugin, upnp-inspector | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Daniel Osmari <danielosmari> |
| Component: | RPM Packages | Assignee: | Philippe Makowski <makowski.mageia> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | ||
| Version: | 1 | ||
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | python-coherence-0.6.6.2-4.mga1 | CVE: | |
| Status comment: | |||
strange it was for fixing https://bugs.mageia.org/show_bug.cgi?id=1824 Assignee:
bugsquad =>
makowski.mageia really strange
urpmi python-coherence
then no problem with :
python
Python 2.7.1 (r271:86832, Sep 5 2011, 14:50:51)
[GCC 4.5.2] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> from coherence.base import Coherence
>>> from coherence.ui.av_widgets import TreeWidget
>>>
and if I install upnp-browser, I have no problem running /usr/bin/upnp-inspector
sorry I can't reproduce your bugStatus:
NEW =>
UNCONFIRMED $ python Python 2.7.1 (r271:86832, Sep 5 2011, 14:50:51) [GCC 4.5.2] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> from coherence.base import Coherence Traceback (most recent call last): File "<stdin>", line 1, in <module> ImportError: No module named base >>> from coherence.ui.av_widgets import TreeWidget Traceback (most recent call last): File "<stdin>", line 1, in <module> ImportError: No module named ui.av_widgets I noticed that the new package installs into /usr/lib/python2.7, and not /usr/lib64/python2.7 like before. It doesn't look like that is in Python's path: $ python -c "import sys; print sys.path" ['', '/usr/lib64/python2.7/site-packages/bx_python-0.7.1-py2.7-linux-x86_64.egg', '/usr/lib/python27.zip', '/usr/lib64/python2.7', '/usr/lib64/python2.7/plat-linux2', '/usr/lib64/python2.7/lib-tk', '/usr/lib64/python2.7/lib-old', '/usr/lib64/python2.7/lib-dynload', '/usr/lib64/python2.7/site-packages', '/usr/lib64/python2.7/site-packages/PIL', '/usr/lib64/python2.7/site-packages/gst-0.10', '/usr/lib64/python2.7/site-packages/gtk-2.0', '/usr/lib64/python2.7/site-packages/wx-2.8-gtk2-unicode', '/usr/lib/python2.7/site-packages', '/usr/lib/python2.7/site-packages/setuptools-0.6c11-py2.7.egg-info'] yes it is now in /usr/lib/python2.7/site-packages/ as a noarch package and it is in Python path ;) may be you have some nasty files remaining in /usr/lib64/python2.7/site-package try removing any files /usr/lib64/python2.7/site-packages/coherence/* and /usr/lib64/python2.7/site-packages/Coherence* may be that these files where not removed ? Indeed, there were leftovers in /usr/lib64/python2.7/site-packages/coherence. Removed the whole directory and the problem went away. I tried going back and forth between the version afterwards to see if any file would be left behind, but it didn't happen. Status:
UNCONFIRMED =>
RESOLVED |
Description of problem: Programs that use python-coherence such as totem (dlna/upnp plugin) and upnp-inspector are incompatible with the latest version. They work fine with the previous version (0.6.6.2-3)/ This is the output from totem trying to activate the plugin: File "/usr/lib64/totem/plugins/coherence_upnp/coherence_upnp.py", line 10, in <module> from coherence.ui.av_widgets import TreeWidget ImportError: No module named ui.av_widgets (totem:25553): Totem-WARNING **: Could not load plugin coherence_upnp And this from upnp-inspector: Traceback (most recent call last): File "/usr/bin/upnp-inspector", line 25, in <module> from upnp_inspector.base import Inspector File "/usr/lib64/python2.7/site-packages/upnp_inspector/base.py", line 19, in <module> from coherence.base import Coherence ImportError: No module named base Version-Release number of selected component (if applicable): 0.6.6.2-4.mga1 How reproducible: Just try to run upnp-inspector, or activate totem's dlna/upnp plugin. Steps to Reproduce: 1. Install python-coherence, totem, upnp-inspector 2. Activate totem's dlna/upnp plugin or try to run upnp-browser. 3. Look at console messages.