Bug 886964 - Dolphin cannot start due to symbol lookup error
Summary: Dolphin cannot start due to symbol lookup error
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: kde-baseapps
Version: 18
Hardware: Unspecified
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Than Ngo
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-12-13 17:00 UTC by Peter Gückel
Modified: 2012-12-13 18:54 UTC (History)
7 users (show)

Fixed In Version: kde-baseapps-4.9.90-3
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-12-13 17:29:27 UTC
Type: Bug


Attachments (Terms of Use)

Description Peter Gückel 2012-12-13 17:00:34 UTC
Description of problem:
When dolphin is started, nothing happens. Other applications, kmail, knode, etc., do work. When starting dolphin from the command line, an error message is shown, as shown below.

Version-Release number of selected component (if applicable):
kde-baseapps-4.9.90-2.fc18.x86_64

How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:
Running dolphin & from the command line produces the following repeatable results:

Fontconfig warning: "/etc/fonts/conf.d/50-user.conf", line 9: reading configurations from ~/.fonts.conf is deprecated.
dolphin: symbol lookup error: /lib64/libkdeinit4_dolphin.so: undefined symbol: _ZN22KFilePlacesDeviceCache4selfEv

Expected results:


Additional info:

Comment 1 Rex Dieter 2012-12-13 17:22:24 UTC
rpm -q  kdelibs 
?

Comment 2 Rex Dieter 2012-12-13 17:23:32 UTC
ok, confirmed issue with
kde-baseapps-4.9.90-2
kdelibs-4.9.90-3

I *suspect* some binary compatibility broke here. :(

Comment 3 Rex Dieter 2012-12-13 17:26:34 UTC
Ah, kde-baseapps is using a bad patch, rebuilding without it...

Comment 4 Rex Dieter 2012-12-13 17:29:27 UTC
should be fixed in kde-baseaps-4.9.90-3

Comment 5 Peter Gückel 2012-12-13 18:54:36 UTC
(In reply to comment #1)
> rpm -q  kdelibs 
> ?

kdelibs-4.9.90-3.fc18.x86_64


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