https://bugzilla.novell.com/show_bug.cgi?id=637165 https://bugzilla.novell.com/show_bug.cgi?id=637165#c3 Jon Schewe <jpschewe@mtu.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED InfoProvider|jpschewe@mtu.net | --- Comment #3 from Jon Schewe <jpschewe@mtu.net> 2010-09-06 14:11:09 UTC --- And you don't have an extra libpisock somewhere? If I leave my source built version in place, and install the RPMs for jpilot, then jpilot runs because it's linking against /usr/local/lib/libpisock.so.9. If I move /usr/local/lib out of the way so that the linker can't find that library and then make sure I've installed from the suse repositories it dies. RPMs installed: libpisock9-0.12.5-2.13.x86_64.rpm pilot-link-0.12.5-2.13.x86_64.rpm jpilot-1.8.0-1.25.x86_64.rpm Linker output: linux-vdso.so.1 => (0x00007fff1dbe0000) libpisock.so.9 => /usr/lib64/libpisock.so.9 (0x00007fbdc32a1000) libgtk-x11-2.0.so.0 => /usr/lib64/libgtk-x11-2.0.so.0 (0x00007fbdc2c68000) libgdk-x11-2.0.so.0 => /usr/lib64/libgdk-x11-2.0.so.0 (0x00007fbdc29b6000) libgdk_pixbuf-2.0.so.0 => /usr/lib64/libgdk_pixbuf-2.0.so.0 (0x00007fbdc2798000) libgobject-2.0.so.0 => /usr/lib64/libgobject-2.0.so.0 (0x00007fbdc254e000) libglib-2.0.so.0 => /usr/lib64/libglib-2.0.so.0 (0x00007fbdc226a000) libdl.so.2 => /lib64/libdl.so.2 (0x00007fbdc2066000) libpthread.so.0 => /lib64/libpthread.so.0 (0x00007fbdc1e49000) libc.so.6 => /lib64/libc.so.6 (0x00007fbdc1ae9000) libusb-0.1.so.4 => /usr/lib64/libusb-0.1.so.4 (0x00007fbdc18e4000) libbluetooth.so.3 => /usr/lib64/libbluetooth.so.3 (0x00007fbdc16c8000) libpangocairo-1.0.so.0 => /usr/lib64/libpangocairo-1.0.so.0 (0x00007fbdc14bb000) libX11.so.6 => /usr/lib64/libX11.so.6 (0x00007fbdc117b000) libXfixes.so.3 => /usr/lib64/libXfixes.so.3 (0x00007fbdc0f75000) libatk-1.0.so.0 => /usr/lib64/libatk-1.0.so.0 (0x00007fbdc0d53000) libcairo.so.2 => /usr/lib64/libcairo.so.2 (0x00007fbdc0ad2000) libgio-2.0.so.0 => /usr/lib64/libgio-2.0.so.0 (0x00007fbdc081b000) libpangoft2-1.0.so.0 => /usr/lib64/libpangoft2-1.0.so.0 (0x00007fbdc05e9000) libpango-1.0.so.0 => /usr/lib64/libpango-1.0.so.0 (0x00007fbdc039d000) libfontconfig.so.1 => /usr/lib64/libfontconfig.so.1 (0x00007fbdc0166000) libgmodule-2.0.so.0 => /usr/lib64/libgmodule-2.0.so.0 (0x00007fbdbff62000) libm.so.6 => /lib64/libm.so.6 (0x00007fbdbfd0b000) libXext.so.6 => /usr/lib64/libXext.so.6 (0x00007fbdbfaf8000) libXrender.so.1 => /usr/lib64/libXrender.so.1 (0x00007fbdbf8ed000) libXinerama.so.1 => /usr/lib64/libXinerama.so.1 (0x00007fbdbf6ea000) libXi.so.6 => /usr/lib64/libXi.so.6 (0x00007fbdbf4da000) libXrandr.so.2 => /usr/lib64/libXrandr.so.2 (0x00007fbdbf2d1000) libXcursor.so.1 => /usr/lib64/libXcursor.so.1 (0x00007fbdbf0c6000) libXcomposite.so.1 => /usr/lib64/libXcomposite.so.1 (0x00007fbdbeec3000) libXdamage.so.1 => /usr/lib64/libXdamage.so.1 (0x00007fbdbecc0000) libgthread-2.0.so.0 => /usr/lib64/libgthread-2.0.so.0 (0x00007fbdbeabb000) libpcre.so.0 => /lib64/libpcre.so.0 (0x00007fbdbe88d000) /lib64/ld-linux-x86-64.so.2 (0x00007fbdc34e2000) libusb-1.0.so.0 => /usr/lib64/libusb-1.0.so.0 (0x00007fbdbe67f000) libfreetype.so.6 => /usr/lib64/libfreetype.so.6 (0x00007fbdbe3f6000) libxcb.so.1 => /usr/lib64/libxcb.so.1 (0x00007fbdbe1d9000) libpixman-1.so.0 => /usr/lib64/libpixman-1.so.0 (0x00007fbdbdf77000) libpng14.so.14 => /usr/lib64/libpng14.so.14 (0x00007fbdbdd4d000) libxcb-render-util.so.0 => /usr/lib64/libxcb-render-util.so.0 (0x00007fbdbdb49000) libxcb-render.so.0 => /usr/lib64/libxcb-render.so.0 (0x00007fbdbd940000) libz.so.1 => /lib64/libz.so.1 (0x00007fbdbd72a000) libresolv.so.2 => /lib64/libresolv.so.2 (0x00007fbdbd513000) libselinux.so.1 => /lib64/libselinux.so.1 (0x00007fbdbd2f4000) libexpat.so.1 => /lib64/libexpat.so.1 (0x00007fbdbd0ca000) librt.so.1 => /lib64/librt.so.1 (0x00007fbdbcec1000) libXau.so.6 => /usr/lib64/libXau.so.6 (0x00007fbdbccbd000) Output from running:
jpilot removing stale pidfile jpilot: symbol lookup error: jpilot: undefined symbol: unpack_CalendarEvent
Moving .jpilot out of the way works, but then I don't have my calendar information. My guess is that jpilot recognizes the new calendar databases and is only trying to load that code when you have a new calendar database. Have you tested it with that? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.