On Fri, Mar 29, 2013 at 1:57 AM, Daniel Vacek <[email protected]> wrote:
> Hi,
>
> I can confirm the bug and this patch fixes it.
Ok, the problem is elsewhere. This patch won't fix the bug. Instead
we must realize there is no bug.
I tested the patch with LD_PRELOAD of 'fixed' library and it was all
right. But after I installed lib to the system the problem did not
disappear. So I investigated a little more.
The bug is gone even with LD_PRELOAD of unpatched library and it
turned out to this:
neelx@sweeney:~$ ldd `which totem` | grep libcogl.so
libcogl.so.9 => /usr/lib/i386-linux-gnu/libcogl.so.9 (0xb7278000)
libcogl.so.12 => /usr/lib/i386-linux-gnu/libcogl.so.12 (0xb62c4000)
neelx@sweeney:~$ LD_PRELOAD=/usr/lib/i386-linux-gnu/libcogl.so.12 ldd
`which totem` | grep libcogl.so
/usr/lib/i386-linux-gnu/libcogl.so.12 (0xb7660000)
libcogl.so.9 => /usr/lib/i386-linux-gnu/libcogl.so.9 (0xb7135000)
neelx@sweeney:~$ ldd `which gnome-shell` | grep libcogl.so
libcogl.so.9 => /usr/lib/i386-linux-gnu/libcogl.so.9 (0xb6799000)
libcogl.so.12 => /usr/lib/i386-linux-gnu/libcogl.so.12 (0xb52c0000)
neelx@sweeney:~$ LD_PRELOAD=/usr/lib/i386-linux-gnu/libcogl.so.12 ldd
`which gnome-shell` | grep libcogl.so
/usr/lib/i386-linux-gnu/libcogl.so.12 (0xb768d000)
libcogl.so.9 => /usr/lib/i386-linux-gnu/libcogl.so.9 (0xb668e000)
llibcogl12
It's fine as long as it get's loaded _before_the_old_ version (surprisingly).
neelx@sweeney:~$ readelf -d `which totem` | grep libcogl.so
0x00000001 (NEEDED) Shared library: [libcogl.so.9]
neelx@sweeney:~$ readelf -d `which gnome-shell` | grep libcogl.so
0x00000001 (NEEDED) Shared library: [libcogl.so.9]
Well, so the point is, totem or gnome-shell needs libcogl.so.9, but
other library/ies they depends on (namely package libclutter-1.0-0 (>=
1.13.10-1)) needs libcogl.so.12.
As of version 1.14.0-1 package libclutter-1.0-0 correctly breaks
libcogl9 and libcogl11. So should the package libcogl12 probably Break
libclutter-1.0-0 (< 1.14.0-1)?
--nX
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
