openlp-core team mailing list archive

[phill <966071@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

From: http://support.openlp.org/issues/499

Ubuntu
OpenLP 1.9.9
 
/usr/lib/pymodules/python2.6/sqlalchemy/engine/default.py:230: SAWarning: Unicode type received non-unicode bind param value 3 param.append(processors[key](compiled_params[key])) /usr/lib/pymodules/python2.6/sqlalchemy/engine/default.py:230: SAWarning: Unicode type received non-unicode bind param value 1 param.append(processors[key](compiled_params[key])) Segmentation fault

 1. Regarding the two unicode messages I originally reported: I think
they only show up on a "first use" run after (re-)installing. I've seen
them each time I've done that (3 times now), but not on subsequent runs.
And they only seem to be warnings since I now find they don't stop the
program running.

2. No error messages now while starting or using OpenLP. But when I
close it (having started it from the command line) I still get a
Segmentation Fault message. It doesn't matter, the program just closes,
and if I were running the program from the main menu or a desktop icon I
would never see it. But it shouldn't happen, surely?

** Affects: openlp
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of OpenLP
Core, which is subscribed to OpenLP.
https://bugs.launchpad.net/bugs/966071

Title:
  segmentation fault and SAWarning's on exiting after first run?

Status in OpenLP - Worship Presentation Software:
  New

Bug description:
  From: http://support.openlp.org/issues/499

  Ubuntu
  OpenLP 1.9.9
   
  /usr/lib/pymodules/python2.6/sqlalchemy/engine/default.py:230: SAWarning: Unicode type received non-unicode bind param value 3 param.append(processors[key](compiled_params[key])) /usr/lib/pymodules/python2.6/sqlalchemy/engine/default.py:230: SAWarning: Unicode type received non-unicode bind param value 1 param.append(processors[key](compiled_params[key])) Segmentation fault

   1. Regarding the two unicode messages I originally reported: I think
  they only show up on a "first use" run after (re-)installing. I've
  seen them each time I've done that (3 times now), but not on
  subsequent runs. And they only seem to be warnings since I now find
  they don't stop the program running.

  2. No error messages now while starting or using OpenLP. But when I
  close it (having started it from the command line) I still get a
  Segmentation Fault message. It doesn't matter, the program just
  closes, and if I were running the program from the main menu or a
  desktop icon I would never see it. But it shouldn't happen, surely?

To manage notifications about this bug go to:
https://bugs.launchpad.net/openlp/+bug/966071/+subscriptions