Opened 7 years ago

Closed 7 years ago

#1679 closed defect (not a bug)

symbol lookup error: /lib64/libgtk-3.so.0: undefined symbol: g_log_structured

Reported by: Tristan Croll Owned by: Greg Couch
Priority: critical Milestone:
Component: Core Version: 0.9
Keywords: Cc:
Blocked By: Blocking:
Notify when closed: Platform: Linux64 (X11)
Project: ChimeraX

Description

I just noticed using last week's nightly rpm build (in a CentOS 7 environment) that ChimeraX would crash with the headline message when I attempted to open a QFileDialog. In today's build, it fails to start at all:

(chimerax-daily:17059): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/opt/UCSF/ChimeraX-daily/bin/../lib/gdk-pixbuf-2.0/2.10.0/loaders.cache': No such file or directory

This likely means that your installation is broken.
Try running the command
  gdk-pixbuf-query-loaders > /opt/UCSF/ChimeraX-daily/bin/../lib/gdk-pixbuf-2.0/2.10.0/loaders.cache
to make things work again for the time being.
WARNING: 'clip' is a prefix of an existing command 'clipper'
chimerax-daily: symbol lookup error: /lib64/libgtk-3.so.0: undefined symbol: g_log_structured
[17083:17083:0100/000000.555581:ERROR:broker_posix.cc(41)] Invalid node channel message

... but if I force ChimeraX's library dir to the front of the search path:

LD_LIBRARY_PATH=/opt/UCSF/ChimeraX-daily/lib chimerax-daily

... then it runs OK.

Change History (2)

comment:1 by Greg Couch, 7 years ago

Status: assignedaccepted

Sounds like a RUNPATH versus RPATH problem.

comment:2 by Tristan Croll, 7 years ago

Resolution: not a bug
Status: acceptedclosed

Never mind - this was entirely my fault. I was running ChimeraX from a Bash shell that was horribly polluted with environment variables from when I was testing something else. Sorry!

Note: See TracTickets for help on using tickets.