application tries to dlopen /usr/lib/libpython2.5.so (only found in the -dev package)

An other comment, it is just for the Kubuntu specific options like
* UserManagement
* Restricted Drivers
* Windows Application
* System Services
* Disk & Filesystems

kde-systemsettings should be fixed to open libpython2.5.so.1 instead, there should be no need to depend on python-dev.

I can confirm this bug for version 0.0svn20070312-0ubuntu3

Raising priority, as this will be experience with all users of Gutsy Beta if they select Display, User, Disk or Services config applet from System Settings.
Workaround is to install python2.5-dev package, but I do not think it is acceptable.

This was fixed by adding a python2.5-dev dependency to libpythonize0, which seems to be the package pulling in libpython.

This bug happens again in Kubuntu Hardy. It seems python2.5-dev isn't installed automatically, I had to do it manually to resolve the issue.

Just to confirm that hardy is still broken in this regard. I just installed from alpha2, and then did
an upgrade to whatever is there today, and the kde system settings is broken. At first I got
the libpython2.5 error, so I installed python2.5-dev. Now I just get a non-specific "could not be loaded" error in the monitor and display settings (it seems to work ok to go into administrator mode in, for example, user management): but not in m&d.

The fix may have been released, but it's broken again now ...

broken in Hardy Alpha 4

I did a clean install of kubuntu (Hardy Alpha 4) over the weekend and this problem still exists when going to "System Setting" -> "Monitor and Display". (See Screenshot)
1) After trying the symlink suggestion in the bug description does not solve it, it merely changes the error message. i.e. the line showing the libpython2.5.so is gone, all the rest of the error message is still there.
2) I then removed the symlink, and installed python2.5-dev package, The package simply created the symlink again and the problem persists.

broken in Hardy Alpha 4

I did a clean install of kubuntu (Hardy Alpha 4) over the weekend and this problem still exists when going to "System Setting" -> "Monitor and Display". (See Screenshot)
1) After trying the symlink suggestion in the bug description does not solve it, it merely changes the error message. i.e. the line showing the libpython2.5.so is gone, all the rest of the error message is still there.
2) I then removed the symlink, and installed python2.5-dev package, The package simply created the symlink again and the problem persists.

I also have this problem in Hardy Heron! Alpha 4

After a clean-install, it didn't work! - I tried installing python2.5-dev - that didn't get it running either!

Here are the files in question:

nikoline@nikoline-laptop:/usr/lib$ ls -la | grep "libpython2.5"
lrwxrwxrwx 1 root root 17 2008-02-16 23:37 libpython2.5.so -> libpython2.5.so.1
lrwxrwxrwx 1 root root 19 2008-02-16 14:29 libpython2.5.so.1 -> libpython2.5.so.1.0
-rw-r--r-- 1 root root 1236568 2008-01-03 20:08 libpython2.5.so.1.0

...does it look right?

Still here in Hardy alpha 5.

I tried installing the -dev package and it got rid of the diagnostic error message "Library files for libpython2.5.so not found in paths", but the behavior didn't change at all. I still can't change my screen resolution.

Kalrog that is another bug #173768

This is a combination of 2 bugs:

1) Installation of -dev package will fix the problem with libpython2.5 (but that would still need to be fixed up properly), you can see this e.g. in user management which will work afterwards
2) But for Monitor&Display an extra error exists which is not solved by installing python development packages... apparantly this is because of inclusion of a new X server which doesn't require some lines in xorg.conf (while Monitor&Display checks for those lines).

Since there are actually 2 bugs some of the duplicates bugs are attached to the wrong one (some people started mixing up the 2 bugs). Anyway it would be best if they both would be fixed before hardy final release... all users will probably see this bug if left unfixed.

From a duplicate bug report: instead of installing python-dev, following also works around the problem:

sudo ln -s /usr/lib/libpython2.5.so.1 /usr/lib/libpython2.5.so

I confirm that I also run into this bug in my Hardy alpha5 installation and that Sven's workaround works great.
+1 for Mathias : libpythonize0 should not depend upon python-dev and kde-systemsettings should be debugged instead.

libpythonize0 has tried to dlopen libpython2.5.so since we've had it in Kubuntu. Traditionally this has been worked around by adding a dependency on python-dev. This got dropped early in the Hardy cycle (it seems to happen about once per development cycle). I'm leaving this bug open to document the long standing libpythonize0 problem and readding the work around as a solution to Bug #179668. I've moved the Hardy dupes of this bug to be dupes of that one.

btw this bug exists in Hardy KDE4 alpha 1 too.

On Sat, Mar 1, 2008 at 11:13 AM, Scott Kitterman <email address hidden> wrote:
> libpythonize0 has tried to dlopen libpython2.5.so since we've had it in
> Kubuntu. Traditionally this has been worked around by adding a
> dependency on python-dev. This got dropped early in the Hardy cycle (it
> seems to happen about once per development cycle). I'm leaving this bug
> open to document the long standing libpythonize0 problem and readding
> the work around as a solution to Bug #179668. I've moved the Hardy
> dupes of this bug to be dupes of that one.
>
>
> ** Changed in: pykdeextensions (Ubuntu Hardy)
> Importance: High => Medium
> Assignee: Scott Kitterman (kitterman) => (unassigned)
> Status: In Progress => Confirmed
> Target: ubuntu-7.10-beta => None
>
>
>
> --
> application tries to dlopen /usr/lib/libpython2.5.so (only found in the -dev package)
> https://bugs.launchpad.net/bugs/138189
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>

--
Edward Holcroft

It's probably using libpythonize0 too. Fixing it once in the correct lib will fix it everywhere.

The attached patch should fix libpythonize0 so it refers to the correct shared library (libpython2.5.so.1.0 or libpython2.5.so.1.0).

Perhaps it is dirty to hardwire the soname in the program, but it is the lesser of two evils. The libpython soname is extremely unlikely to change, but if it does, it's an easy fix.

I tested the fix by removing python-dev and running displayconfig and it works.

 I have built the source package and am ready to upload once I get the go-ahead from motu-release.

I'd love to give an ack, but I fear pykdeextensions is in main ;).

Indeed... Attaching debdiff.

This causes problems

kcmshell mountconfig

Pythonize constructor -- pid = 10847
Python interpreter initialized!

Pythonize constructor -- pid = 10847
Traceback (most recent call last):
  File "/var/lib/python-support/python2.5/mountconfig.py", line 19, in <module>
    from qt import *
ImportError: /usr/lib/python2.5/site-packages/qt.so: undefined symbol: PyUnicode_Type
Error in sys.excepthook:
Traceback (most recent call last):
  File "/usr/lib/python2.5/site-packages/apport_python_hook.py", line 36, in apport_excepthook
    from cStringIO import StringIO
ImportError: /usr/lib/python2.5/lib-dynload/cStringIO.so: undefined symbol: _Py_ZeroStruct

Original exception was:
Traceback (most recent call last):
  File "/var/lib/python-support/python2.5/mountconfig.py", line 19, in <module>
    from qt import *
ImportError: /usr/lib/python2.5/site-packages/qt.so: undefined symbol: PyUnicode_Type
error: ***failed to import module

mok0,

Sorry about that. I remembered wrong which kde-guidance module you need to test with. Apologies.

Scott K

I was same problem in UbuntuStudio.Fixed with Attachment libpython2.5.so.1.0

part of the problem is that kde-guidance also has an embedded reference to libpython.so here, which it inherits from pykdeextensions when building. so pykdeextensions needs to be fixed, and then kde-guidance needs to be rebuilt against it - with a versioned conflict or other measure to ensure the correct combination of packages is installed.

Sync'ed from Debian.

This is adequately worked around in Hardy. IMO there is no SRU worthy reason to update pykdeextensions in Hardy.

Impact is Hardy is not SRU worthy. Will fix in Intrepid.

This bug was fixed in the package kde-guidance - 0.8.0svn20080103-0ubuntu20

---------------
kde-guidance (0.8.0svn20080103-0ubuntu20) intrepid; urgency=low

  * No change upload to rebuild against new libpythonize and finally
    link to the right libpython.so (LP: #138189)

 -- Scott Kitterman <email address hidden> Sun, 13 Jul 2008 18:58:03 -0400