Description of problem: Wordnet, a dependancy of Calligra, fails to load (nothing appears) when selected from the kickoff menu after installation. A loading icon appears but then after a minute, goes away and nothing happens. When attempting to run via command line as root, a permission denied error occurs. Version-Release number of selected component (if applicable): calligra-words 2.4.0-2.mga2 x86_64 wordnet 3.0-13.mga2 x86_64 How reproducible: Always Steps to Reproduce: 1. Install Calligra via RPMdrake 2. Wordnet is pulled in as a dependancy 3. Run wordnet from Kickoff Launcher
Source RPM: (none) => wordnet 3.0-13.mga2 x86_64
any message error when you launch the apps from a terminal ?
Wordnet produces a list of command line options to be used when launched in terminal however nothing loads at all (no GUI or anything) if launched through kickoff / application launcher. Calligra loads fine from terminal but produces the following message: words(7161)/koffice (lib kopageapp) KoOdfLoadingContext::KoOdfLoadingContext: could not parse manifest document When opening a file, the following messages are produced: words(7161)/kotext KoTextLoader::loadBody: unhandled text: "sequence-decls" Enchant dict for "en_US" 0x2b3be80 Enchant dict for "en_US" 0x2b3be80 Enchant dict for "en_US" 0x2b3be80 Enchant dict for "en_US" 0x2b3be80 Enchant dict for "en_US" 0x2b3be80 Enchant dict for "en_US" 0x2b3be80 words(7161)/kdeui (KAction) KActionCollection::setComponentData: this does not work on a KActionCollection containing actions! QFont::setPointSizeF: Point size <= 0 (0.000000), must be greater than 0
Ok thanks. Any ideas ?
CC: (none) => fundawangAssignee: bugsquad => n54
I have installed task-kde4 and wordnet, I can't reproduce it.
Hi, This bug was filed against cauldron, but we do not have cauldron at the moment. Please report whether this bug is still valid for Mageia 2. Thanks :) Cheers, marja
Keywords: (none) => NEEDINFO
Please look at the bottom of this mail to see whether you're the assignee of this bug, if you don't already know whether you are. If you're the assignee: We'd like to know for sure whether this bug was assigned correctly. Please change status to ASSIGNED if it is, or put OK on the whiteboard instead. If you don't have a clue and don't see a way to find out, then please put NEEDHELP on the whiteboard. Please assign back to Bug Squad or to the correct person to solve this bug if we were wrong to assign it to you, and explain why. Thanks :) **************************** @ the reporter and persons in the cc of this bug: If you have any new information that wasn't given before (like this bug being valid for another version of Mageia, too, or it being solved) please tell us. @ the reporter of this bug If you didn't reply yet to a request for more information, please do so within two weeks from now. Thanks all :-D
2x no reply, closing as old Feel free to reopen if needed and tell in which fully updated Mageia version(s) you still have this issue
Status: NEW => RESOLVEDCC: (none) => marja11Resolution: (none) => OLD