Description of problem:
Most of the koffice components in the new updates-testing package exit
immediately when they're run. The only one that starts up properly seems to
be "kugar". The versions from the base Fedora install (1.6.2-3.fc7) work fine;
this is definitely a regression in 1.6.3-1.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Run "kspread", "kpresenter", "kword", "krita", "karbon", ...
Command prompt returns immediately, program does not start (no error message,
no process running in "ps", nothing).
Requested program should start
Odd, WORKSFORME. ???
$ rpm -Va koffice-*
I just tried on another Fedora 7 machine and the same thing happened. The
rpm -V command didn't return anything
I can confirm what Mary Ellen Foster reported; kugar is the only app that starts
Regarding " rpm -Va koffice-* ", it didn't return anything. If needed, I can
provide only the output of 'strace $APP'.
What arch you folks running? i386, x86_64 (or ppc)?
Rex, I'm running i386.
i386 as well on both machines I tested this on.
confirmed, looks like our koffice build was done against kdelibs-3.5.7, and
exibits this problem on machines with kde < 3.5.7.
I'll withdraw the update, and rebuild with Requires: kdelibs >= 3.5.7.
I tried too and with kdelibs 3.5.7 it works.
Where are you getting 3.5.7 from? Rawhide? That doesn't seem to be in
updates-testing yet ...
Yes, at the moment it's only available in Koji (
* Fri Jun 15 2007 Rex Dieter <rdieter[AT]fedoraproject.org>
- Require version of kdelibs used to build against (#244091)
- -suite: use versioned Requires
koffice-1.6.3-3.fc7 update request queue'd.
koffice-1.6.3-3.fc7 has been pushed to the Fedora 7 testing repository. If problems still persist, please make note of it in this bug report.
Now it works perfectly. Thank you, Rex.
koffice-1.6.3-6.fc7 has been pushed to the Fedora 7 testing repository. If problems still persist, please make note of it in this bug report.
koffice-1.6.3-6.fc7 has been pushed to the Fedora 7 stable repository. If problems still persist, please make note of it in this bug report.