Bug 52271 - pyuno exception handling breaks some applications
Summary: pyuno exception handling breaks some applications
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
(earliest affected)
Hardware: All All
: medium normal
Assignee: Not Assigned
Depends on:
Reported: 2012-07-19 15:26 UTC by David Burke
Modified: 2015-06-08 14:26 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:
Regression By:


Note You need to log in before you can comment on or make changes to this bug.
Description David Burke 2012-07-19 15:26:24 UTC
See https://code.djangoproject.com/ticket/11098

The django developer says "This looks like uno is installing some sort of an import hook that's written incorrectly to the point that it causes Django to fail. It's impossible for Django to handle all this sort of monkeypatching, so this is a bug that'll need to be fixed with uno."

Is this really a bug in pyuno? I'm afraid I don't understand exception handling well enough to determine this. 

It's annoying at least in django developement (and presumably elsewhere) because pyuno eats up the exceptions sometimes making it hard to debug. Some applications such as South break due to this. Here is a sample of how it can break

    __import__(app_name + '.management', {}, {}, [''])
except ImportError, exc:
    msg = exc.args[0]
    if not msg.startswith('No module named') or 'management' not in msg:

Perhaps the msg.startswith is a bit of a hack...but it demonstrates how annoying this is. I would except the django related exception here, but instead we pyuno stuff that just shouldn't be here.
Comment 1 Buovjaga 2014-11-06 11:52:03 UTC
Does this still happen in later versions?
Comment 2 QA Administrators 2015-05-06 14:15:11 UTC
Dear Bug Submitter,

This bug has been in NEEDINFO status with no change for at least
6 months. Please provide the requested information as soon as
possible and mark the bug as UNCONFIRMED. Due to regular bug
tracker maintenance, if the bug is still in NEEDINFO status with
no change in 30 days the QA team will close the bug as INVALID
due to lack of needed information.

For more information about our NEEDINFO policy please read the
wiki located here:

If you have already provided the requested information, please
mark the bug as UNCONFIRMED so that the QA team knows that the
bug is ready to be confirmed.
Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team
Comment 3 QA Administrators 2015-06-08 14:26:55 UTC
Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INVALID due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

-- The LibreOffice QA Team 

This INVALID Message was generated on: 2015-05-06

Warm Regards,
QA Team