Bug 736952 - avogadro doesn't start anyway
Summary: avogadro doesn't start anyway
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: avogadro
Version: 15
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Kevin Kofler
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-09-09 07:44 UTC by nauton
Modified: 2011-09-12 10:33 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-09-12 06:21:52 UTC


Attachments (Terms of Use)

Description nauton 2011-09-09 07:44:01 UTC
Description of problem:
in graphical mode avogadro doesn't start, there is no error message available, ABRT report nothing's wrong.
in command line, avogadro return the following message :

[nauton@sancy ~]$ avogadro 
avogadro: symbol lookup error: /usr/lib64/libavogadro.so.1: undefined symbol: _ZN14QGraphicsScene11eventFilterEP7QObjectP6QEvent

Version-Release number of selected component (if applicable):
this concern 
[nauton@sancy ~]$ rpm -qa | grep avogadro
avogadro-devel-1.0.3-2.fc15.x86_64
avogadro-1.0.3-2.fc15.x86_64
avogadro-debuginfo-1.0.1-10.fc14.x86_64
avogadro-libs-1.0.3-2.fc15.x86_64

How reproducible: everytime


Steps to Reproduce:
1. starting avogadro
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Kevin Kofler 2011-09-09 13:32:48 UTC
Works for me. You seem to have a binary-incompatible Qt (an old version bundled with some proprietary application?) in your library path.

Can you please post the output of:
rpm -q qt qt-x11
and of:
ldd /usr/bin/avogadro
?

Comment 2 nauton 2011-09-09 15:02:34 UTC
in fact , i can run avogadro on my netbook with fedora 15 X86_64 so the problem comes to my desktop PC installation ...

the return of your command :

 [root@sancy ~]# rpm -q qt qt-x11
qt-4.7.3-8.fc15.x86_64
qt-4.7.3-8.fc15.i686
qt-x11-4.7.3-8.fc15.x86_64
qt-x11-4.7.3-8.fc15.i686
[root@sancy ~]# ldd /usr/bin/avogadro
	linux-vdso.so.1 =>  (0x00007fff41c8f000)
	libc.so.6 => /lib64/libc.so.6 (0x0000003a95800000)
	libopenbabel.so.4 => /usr/lib64/libopenbabel.so.4 (0x0000003aa3000000)
	libQtOpenGL.so.4 => /usr/lib64/libQtOpenGL.so.4 (0x0000003ad9c00000)
	libQtGui.so.4 => /usr/lib64/libQtGui.so.4 (0x0000003ad5000000)
	libQtNetwork.so.4 => /usr/lib64/libQtNetwork.so.4 (0x0000003a9e600000)
	libQtCore.so.4 => /usr/lib64/libQtCore.so.4 (0x0000003a9dc00000)
	libavogadro.so.1 => /usr/lib64/libavogadro.so.1 (0x000000356cc00000)
	libGLU.so.1 => /usr/lib64/libGLU.so.1 (0x0000003aa6600000)
	libGL.so.1 => /usr/lib64/nvidia/libGL.so.1 (0x0000003ab1000000)
	libSM.so.6 => /usr/lib64/libSM.so.6 (0x0000003aa1800000)
	libICE.so.6 => /usr/lib64/libICE.so.6 (0x0000003aa1c00000)
	libX11.so.6 => /usr/lib64/libX11.so.6 (0x0000003a98c00000)
	libXext.so.6 => /usr/lib64/libXext.so.6 (0x0000003a99800000)
	libGLEW.so.1.5 => /usr/lib64/libGLEW.so.1.5 (0x0000003a9a400000)
	libpython2.7.so.1.0 => /usr/lib64/libpython2.7.so.1.0 (0x0000003aa7400000)
	libboost_python-mt.so.1.46.0 => /usr/lib64/libboost_python-mt.so.1.46.0 (0x0000003a9c400000)
	libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x0000003a9cc00000)
	libm.so.6 => /lib64/libm.so.6 (0x0000003a95c00000)
	libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x0000003a97000000)
	libpthread.so.0 => /lib64/libpthread.so.0 (0x0000003a96000000)
	/lib64/ld-linux-x86-64.so.2 (0x0000003a95400000)
	libdl.so.2 => /lib64/libdl.so.2 (0x0000003a96400000)
	libz.so.1 => /lib64/libz.so.1 (0x0000003a96800000)
	libfreetype.so.6 => /usr/lib64/freetype-freeworld/libfreetype.so.6 (0x0000003ad3000000)
	libXi.so.6 => /usr/lib64/libXi.so.6 (0x0000003a9b800000)
	libXrender.so.1 => /usr/lib64/libXrender.so.1 (0x0000003a9ac00000)
	libXrandr.so.2 => /usr/lib64/libXrandr.so.2 (0x0000003a9b400000)
	libXfixes.so.3 => /usr/lib64/libXfixes.so.3 (0x0000003a9c800000)
	libXcursor.so.1 => /usr/lib64/libXcursor.so.1 (0x0000003a9c000000)
	libXinerama.so.1 => /usr/lib64/libXinerama.so.1 (0x0000003a9bc00000)
	libfontconfig.so.1 => /usr/lib64/libfontconfig.so.1 (0x0000003ad2c00000)
	libgthread-2.0.so.0 => /lib64/libgthread-2.0.so.0 (0x0000003a97c00000)
	librt.so.1 => /lib64/librt.so.1 (0x0000003a96c00000)
	libglib-2.0.so.0 => /lib64/libglib-2.0.so.0 (0x0000003a97800000)
	libpng12.so.0 => /usr/lib64/libpng12.so.0 (0x0000003a99c00000)
	libgobject-2.0.so.0 => /lib64/libgobject-2.0.so.0 (0x0000003a98400000)
	libssl.so.10 => /usr/lib64/libssl.so.10 (0x0000003aa2000000)
	libcrypto.so.10 => /lib64/libcrypto.so.10 (0x0000003aa1400000)
	libnvidia-tls.so.280.13 => /usr/lib64/nvidia/tls/libnvidia-tls.so.280.13 (0x0000003ab0000000)
	libnvidia-glcore.so.280.13 => /usr/lib64/nvidia/libnvidia-glcore.so.280.13 (0x0000003aad000000)
	libuuid.so.1 => /lib64/libuuid.so.1 (0x0000003a9f800000)
	libxcb.so.1 => /usr/lib64/libxcb.so.1 (0x0000003a99000000)
	libutil.so.1 => /lib64/libutil.so.1 (0x0000003aa9a00000)
	libexpat.so.1 => /lib64/libexpat.so.1 (0x0000003a99400000)
	libgssapi_krb5.so.2 => /lib64/libgssapi_krb5.so.2 (0x0000003aa1000000)
	libkrb5.so.3 => /lib64/libkrb5.so.3 (0x0000003aa0000000)
	libcom_err.so.2 => /lib64/libcom_err.so.2 (0x0000003a9fc00000)
	libk5crypto.so.3 => /lib64/libk5crypto.so.3 (0x0000003aa0c00000)
	libXau.so.6 => /usr/lib64/libXau.so.6 (0x0000003a98800000)
	libkrb5support.so.0 => /lib64/libkrb5support.so.0 (0x0000003aa0800000)
	libkeyutils.so.1 => /lib64/libkeyutils.so.1 (0x0000003aa0400000)
	libresolv.so.2 => /lib64/libresolv.so.2 (0x0000003a98000000)
	libselinux.so.1 => /lib64/libselinux.so.1 (0x0000003a97400000)
[root@sancy ~]#

Comment 3 Kevin Kofler 2011-09-09 15:30:41 UTC
Assuming you normally run Avogadro as nauton, not as root, please also run the ldd command as nauton. (LD_LIBRARY_PATH can be set per user.)

Comment 4 nauton 2011-09-12 06:21:52 UTC
I have removed qt-4.7.3-8.fc15.i686 and qt-X11-4.7.3-8.fc15.i686, and it works now...
yes as you write in the previous mail, it was not working in my session too.
i have made the different command in my session and on root session.

I have a little trouble believing that to remove programs as qt for i686 change something, but it works, so thanks to have spend time for my problem.

regards

Comment 5 Kevin Kofler 2011-09-12 10:33:30 UTC
qt.i686 cannot possibly be the true source of the problem. But whatever, if it works for you now, we can keep this closed, it was definitely something on your machine.


Note You need to log in before you can comment on or make changes to this bug.