ERROR: The launchpadlib Python module is not installed.

libreoffice.apport file downloaded from Benjamin Drung's bug 1071059 demonstrating the problem https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1071059/+attachment/3414822/+files/libreoffice.apport .

Marking Confirmed. However, I'm still investigating as this seemed initially a duplicate https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1023964 .

Marking Triaged as the problem is reproducible. As well, I've installed all package candidate permutations for python, apport, and liblaunchpad, but still get the same error message.

Is there any workaround to attach collected report in an existing bug?

i had the same error, i solve it with sudo apt-get install python-launchpadlib python-launchpad-integration launchpad-integration

now i can do apport-collect

This issue still occurs in Raring when using either ubuntu-bug -u bug_number on the console or apport-cli -u bug_number.

After reading comments in bug #1023964, this is because apport-cli uses Python 3 but python-launchpadlib uses Python 2.7.

I think the error message that is displayed is very misleading and should be fixed to convey the fact that there is a Python version mismatch instead of message that is shown.

Installing from mini.iso, I had to...

apt-get install python-apport
apt-get install python-launchpadlib
apt-get install linux
apt-get install python-gi
apport-collect 1180419

confirmed on 13.04 (HP-Mini-210-1000)

Confirming what Christopher wrote in comment 8: The problem seems to be that apport-cli is now a python3 program, but python-launchpadlib has not been ported to python3. Therefore, it fails.

The workarounds posted so far do not work on raring.

This makes it rather difficult for users to gather system information for bug reports. I would think fixing it would be a high priority.

Forest, this would not be a python-launchpadlib issue as Apport is stating python-launchpadlib is not installed when it clearly is.

YMMV on WORKAROUNDs.

While the issue is annoying, it would not be a high priority as it doesn't affect an LTS.

The fix that I'm proposing here is to make the error message more meaningful since there is no python3-launchpadlib. This does address the fact that there is no python3-launchpadlib. That is tracked in other bugs such as bug #1153671 and bug #1060734.

The proper fix is to revert upgrading apport-cli to python3 until a python3-launchpadlib exists, and then it should show it as a dependency. Depending on an incompatible version of the library is a packaging error.

@psusi,

I tend to agree with what you say because I think not allowing apport-cli to use Launchpad is very bad. However, it seems the maintainers of Apport are reluctant or unwilling to revert apport-cli back to using Python2. And I'm not sure that Python3 support for launchpadlib will ever happen. I know my MP is not a "fix" per se, but since we cannot use launchpadlib, at least we should have a more accurate error message.

If the Apport maintainers are willing to revert back to Python2, then we can disregard my MP.

It's rather that our Python maintainers/foundations team don't want python2 dependencies on the default install. As we install apport by default, it can only depend on python3 stuff, so Barry asked me to make the python2 bits optional. And indeed launchpadlib is not needed for most apport operations (its main purpose is to file bugs), only if you invoke it as apport-collect. So the default install with python3 is still mostly fine.

> ubuntu-bug -c libreoffice.apport -u 1071059

This is not a valid usage, BTW. You cannot simultaneously report a bug (with -c) and update it (with -u). I'll make sure that this gives a proper error message. You should use "apport-collect 1071059" for updating, and "ubuntu-bug -c libreoffice.apport" for reporting.

Thanks Christopher! I fixed this a bit differently, but keep the spirit of this in trunk: http://bazaar.launchpad.net/~apport-hackers/apport/trunk/revision/2664

For the Ubuntu branch we can indeed be more specific and show the package name / a clearer error message for Python 3: http://bazaar.launchpad.net/~ubuntu-core-dev/ubuntu/saucy/apport/ubuntu/revision/2217

Thanks!

I now also fixed the real issue that you cannot use -u and -c (or other options) together: http://bazaar.launchpad.net/~apport-hackers/apport/trunk/revision/2665

@Martin,

Thanks for making this a more sane error message.

I guess in situations where X/Unity/Compiz are crashing (or situations where there is no window manager), there really is no way to file bugs since apport-collect needs a web browser to open to work. This situation is what led me to this bug. I guess our only hope is that the Launchpad team or some volunteer will actually port launchpadlib to Python3.

Christopher Townsend [2013-07-18 11:38 -0000]:
> I guess in situations where X/Unity/Compiz are crashing (or situations
> where there is no window manager), there really is no way to file bugs
> since apport-collect needs a web browser to open to work.

That seems like an unrelated issue, though. The confusion here was
mainly that the reporter used "apport-cli -c .. -u .." to update a
bug, which doesn't work. You can file a bug manually and then call
"apport-collect 12345" to update it.

@Martin

I see what you're saying, but how do file a bug manually if you don't have X/Unity/Compiz running? I thought apport-cli was a way to file a bug when you don't have a window manager running, but it can't since the launchpadlib is out of date.

Christopher Townsend [2013-07-18 12:25 -0000]:
> I see what you're saying, but how do file a bug manually if you don't
> have X/Unity/Compiz running? I thought apport-cli was a way to file a
> bug when you don't have a window manager running, but it can't since the
> launchpadlib is out of date.

You don't need launchpadlib for filing a bug. You need a browser.
"apport-cli compiz" will work just fine to file a new report against
compiz, as long as you have something like links or lynx installed.
Alternatively you can use "apport-cli --save /tmp/mybug.report compiz",
copy that file to another computer (or restore X), and report it from
there with apport-bug mybug.report.

You don't use -u for filing a bug, that's for updating an existing
bug. And that's the *only* use case which requires launchpadlib.
(Aside from apport-retrace, which is a wholly different tool)

Hi Martin,

Ok, thanks for the explanation. That makes perfect sense. I'll quit bothering you now:)

The issue isn't that it let you use -c and -u together, the issue is that -u is broken. This is a serious problem when asking users to attach needed logs to an existing bug report.

If I understand what Martin is saying, apport-collect 123456 will work as well to attach logs, etc. to existing bug reports. Is my understanding correct?

Yes, apport-collect will work. apport-cli -u cannot work, and that part is a wontfix.

Martin Pitt, thanks for checking in on this report. We could take this discussion off report as it seems unrelated, but as per the apport-cli manpage:
 -c report, --crash-file=report
              Upload a previously processed stored report in an arbitrary file
              location. This is useful for copying a crash report to a
              machine with internet connection and reporting it from there.
              Files must end in .crash or .apport.

-u report-number, --update-report report-number
              Run apport information collection on an already existing problem
              report. The affected package is taken from the report by
              default, but you can explicitly specify one with --package to
              collect information for a different package (this is useful if
              the report is assigned to the wrong package).

Hence, apport-cli -c *.crash -u 12345 is valid syntax. Are your advising this feature is intending to no longer be supported, is broken, something else?

Thank you for your time and consideration in this matter, and I look forward to your response.

Christopher M. Penalver [2013-07-19 10:52 -0000]:
> Hence, apport-cli -c *.crash -u 12345 is valid syntax. Are your advising
> this feature is intending to no longer be supported, is broken,
> something else?

It's broken because we don't have a python3-launchpadlib and because
we run apport-cli with python3.

This bug was fixed in the package apport - 2.12-0ubuntu2

---------------
apport (2.12-0ubuntu2) saucy; urgency=low

  * Merge from trunk:
    - sandboxutils.py, make_sandbox(): Install packages from Package: and
      Dependencies: fields also if we have a ProcMaps: field and there are any
      third-party packages. This fixes retracing crashes that use PPAs (as they
      don't have Contents.gz).
    - Robustify "progress bar visible" GTK and KDE UI checks for the faster
      collection due to dropping lsb_release.
 -- Martin Pitt <email address hidden> Fri, 02 Aug 2013 16:03:43 +0200

annalisa@annalisa-HP-Mini-210-1000:~$ sudo apport-collect 1231647
[sudo] password for annalisa:
ERROR: The launchpadlib Python module is not installed. This functionality is not available.

ubuntu 13.04 updated on 26/09/2013 (NO PROPOSED update selected)