Bug 114361 - XChat missing dependencies
Summary: XChat missing dependencies
Status: RESOLVED WORKSFORME
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: Other (show other bugs)
Version: Beta 3
Hardware: i586 SUSE Other
: P5 - None : Normal
Target Milestone: ---
Assignee: E-mail List
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-08-31 09:44 UTC by Christian Herrmann
Modified: 2005-08-31 13:57 UTC (History)
0 users

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Christian Herrmann 2005-08-31 09:44:54 UTC 
By starting XChat i get the following error message that some libraries are missing:

xchat: error while loading shared libraries: libcairo.so.1: cannot open shared
object file: No such file or directory

Checking for conflicts in Yast or missing components don't helps. The package
"cairo" brings libcairo.so.2
Comment 1 Christian Herrmann 2005-08-31 09:48:13 UTC 
Sorry, forget to add versions: cairo 0.9.2-3 from 08/20/2005 20:10:28
xchat 2.4.4-3 08/23/2005 04:25:50 all from Beta 3
Comment 2 Andreas Jaeger 2005-08-31 09:53:22 UTC 
That's strange, the package is having a require on libcairo.so.2:

$ rpm -qp --requires xchat-2.4.4-3.i586.rpm |grep cairo
libcairo.so.2
libpangocairo-1.0.so.0

Are you sure that you have no other selfcompiled binaries?

please double check and then sent the output of:
LD_DEBUG=files xchat
Comment 3 Christian Herrmann 2005-08-31 13:39:29 UTC 
No, there are no selfcompiled binaries. I did an update from Beta 1 to Beta 2
and then to Beta 3. I've now reinstalled the package. Now it works. But Yast
said it was the same version. So i don't know from where the problem did come.
Could be a problem from the update. Sorry anyway for posting this (wrong?) bug
report.
Comment 4 Andreas Jaeger 2005-08-31 13:57:10 UTC 
This is strange.  Thanks for reporting the bug anyhow and helping to nail down
the issue.  I would have rather this reported then ignored ;-)

Resolving as "WORKSFORYOU" :-)