Bug 192265 - kplato does not start in FC4
Summary: kplato does not start in FC4
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: koffice
Version: 4
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Andreas Bierfert
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-05-18 18:02 UTC by Prashanth N Udupa
Modified: 2007-11-30 22:11 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2006-11-07 17:06:26 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Prashanth N Udupa 2006-05-18 18:02:08 UTC 
Description of problem:
I installed koffice-kplato by using the yum command on
Fedora Core 4. It downloaded some 47 MB of related
updates along with koffice-kplato.

When I execute kplato from the command prompt in 
konsole; no GUI shows up. Then I thought of 
starting the koshell and launching kplato from
the shell. This the output I get when I run 
koshell from konsole.

[prashanth@udupa ~]$ koshell
koshell: symbol lookup error: /usr/lib/libkofficeui.so.3: undefined symbol:
_ZN9KIconView22contentsDragLeaveEventEP15QDragLeaveEvent
[prashanth@udupa ~]$ 

Version-Release number of selected component (if applicable):
kplato --version
Qt: 3.3.4
KDE: 3.4.0-6 Red Hat
KPlato: 0.5.0

koffice --version
koshell: symbol lookup error: /usr/lib/libkofficeui.so.3: undefined symbol:
_ZN9KIconView22contentsDragLeaveEventEP15QDragLeaveEvent

How reproducible:


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


Expected results:


Additional info:
Comment 1 Andreas Bierfert 2006-05-20 22:56:12 UTC 
hm... strange indeed...

rpm -q koffice please :)
Comment 2 Prashanth N Udupa 2006-05-21 04:49:56 UTC 
[root@udupa ~]# rpm -q koffice
package koffice is not installed
[root@udupa ~]#
Comment 3 Andreas Bierfert 2006-05-21 08:05:41 UTC 
Yes sorry my bad... should have been koffice-core and/or koffice-plato
Comment 4 Andreas Bierfert 2006-11-07 17:06:26 UTC 
This should be fixed by now. Closing.
Note You need to log in before you can comment on or make changes to this bug.