Ubuntu
picard package

picard crashed with ImportError in <module>()

Bug #422032 reported by SebastienBarthelemy
282
This bug affects 53 people
Affects Status Importance Assigned to Milestone
picard (Ubuntu)
Fix Released
High
Unassigned
Nominated for Karmic by Matt Behrens

Bug Description

Binary package hint: picard

since the last update (picard 0.11-2ubuntu2), picard does not start anymore. It fails with the following message:

$ picard
Traceback (most recent call last):
  File "/usr/bin/picard", line 2, in <module>
    from picard.tagger import main; main('/usr/share/locale', False)
  File "/usr/lib/pymodules/python2.6/picard/tagger.py", line 52, in <module>
    import picard.plugins
ImportError: No module named plugins

ProblemType: Crash
Architecture: i386
Date: Mon Aug 31 17:19:55 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/picard
InterpreterPath: /usr/bin/python2.6
NonfreeKernelModules: nvidia
Package: picard 0.11-2ubuntu2
ProcCmdline: /usr/bin/python /usr/bin/picard
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=fr_FR.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-8.28-generic
PythonArgs: ['/usr/bin/picard']
SourcePackage: picard
Title: picard crashed with ImportError in <module>()
Uname: Linux 2.6.31-8-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Related branches

lp:ubuntu/karmic/picard
Revision history for this message
SebastienBarthelemy (barthelemy) wrote :
Apport retracing service (apport)
tags: removed: need-duplicate-check
SebastienBarthelemy (barthelemy)
visibility: private → public
Revision history for this message
SebastienBarthelemy (barthelemy) wrote :

Confirmed as reported by too someone else in https://bugs.launchpad.net/ubuntu/+source/picard/+bug/422288

I could also reproduce the bug with the guest account:
$ sudo su guest
guest@thinbox:/home/seb$ picard
Traceback (most recent call last):
  File "/usr/bin/picard", line 2, in <module>
    from picard.tagger import main; main('/usr/share/locale', False)
  File "/usr/lib/pymodules/python2.6/picard/tagger.py", line 52, in <module>
    import picard.plugins
ImportError: No module named plugins

Changed in picard (Ubuntu):
status: New → Confirmed
Revision history for this message
SebastienBarthelemy (barthelemy) wrote :

Here is a fix:
$ sudo mkdir /usr/lib/pymodules/python2.6/picard/plugins
$ sudo touch /usr/lib/pymodules/python2.6/picard/plugins/__init__.py

Revision history for this message
Matt Drake (mattduckman) wrote :

while looking in /usr/lib/pymodules/python2.6/picard I saw that there was a file called plugin.py but no plugins.py
copying this file to the name that the other scripts expect fixes the problem and everything runs as expected

sudo cp /usr/lib/pymodules/python2.6/picard/plugin.py /usr/lib/pymodules/python2.6/picard/plugins.py

unfortunately I have no idea how to create a patch for this

Revision history for this message
Matt Drake (mattduckman) wrote :

haha sorry Sebastien I didn't do a page refresh before sending my comment, but I'm glad we came up with similar suggestions

Ryan Kavanagh (ryanakca)
Changed in picard (Ubuntu):
importance: Undecided → Medium
Revision history for this message
Dominik George (natureshadow) wrote :

Same here on amd64, "fix" works but is no fix but a workaround.

Revision history for this message
Mathias Gug (mathiaz) wrote :

Setting to triaged. This is due to a missing directory and file in the package:

/usr/share/python-support/picard/picard/plugins/__init__.py

The __init__.py file is actually empty in the upstream source as this directory is meant for plugins. However setup.py doesn't seem to copy empty files.

The jaunty package as well as the debian package (0.11-2) do have the plugins/ directory and the empty pluings/__init__.py file packaged.

Changed in picard (Ubuntu):
importance: Medium → High
status: Confirmed → Triaged
Revision history for this message
ponty (ponty) wrote :

Beautiful .. that worked like a charm :)
Thanks!!

Revision history for this message
Chafnan (chafnan) wrote :

Fix worked for me too.

Thanks.

Revision history for this message
Carlos Sánchez Mateo (chukysoria) wrote :

Same bug in Karmic.

I try the workaround and works perfectly

Revision history for this message
Anders (andersja+launchpad-net) wrote :

Same bug affecting me in Karmic beta. With such an (apparently) simple fix as suggested above - is it overly optimistic to hope for a quick fix before Karmic release?

Revision history for this message
Chad Miller (cmiller) wrote :

I guess no one's working on this.

Changed in picard (Ubuntu):
status: Triaged → In Progress
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package picard - 0.11-2ubuntu3

---------------
picard (0.11-2ubuntu3) karmic; urgency=low

  * Add patch to set plugins/__init__.py nonempty so setup installs it.
    (LP: #422032)

 -- Chad Miller <email address hidden> Fri, 02 Oct 2009 15:10:11 -0400

Changed in picard (Ubuntu):
status: In Progress → Fix Released
Revision history for this message
Anders (andersja+launchpad-net) wrote :

Chad's fix works. Latest Karmic has picard back up and running again. Thanks!

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.