I'm on the 64bit version of M2

I installed some different components of Calligra
when I open Calligra spreadsheets, opens fine, when I try to start a new spread, it crashes & I'm offered the option to file a bug with KDE
1st I was missing I think it was GDM, so I installed

now I need to install:

/usr/bin/kdeinit4
/usr/lib64/libQtCore.so.4
/usr/lib64/libkowidgets.so.9
/usr/lib64/libkomain.so.9
/usr/lib64/libcalligrasheetscommon.so.9
/usr/lib64/libQtGui.so.4
/usr/lib64/libpigmentcms.so.9
/usr/lib64/kde4/calligradockers.so

could be I didn't install Calligra properly, then the bug is in the installer

how can I help figure it out?

First, GDM is "Gnome display manager", which shouldn't be needed by Calligra, a KDE application.

It could be due to a glitch (isolated one-time error) when you installed Calligra.
I'd first try uninstalling Calligra, then reinistalling, to see if that corrects running Calligra.

If you still have a problem, it could be useful to know how you installed Calligra.
One possible cause is missing dependancies in Calligra (a packaging problem).

Also, you list a number of files, and not packages.  Where did this list come from ?

CC: (none) => andre999mga

I uninstalled, reinstalled calligra
same result

I had Kexi 1st which I installed from MCC
made up a simple databse

installed calligra core, sheet, presentation, word using mcc
I can open any of the apps, as soon as I try to use a blank template, crash & bug handler

the uninstall reinstall broke kexi

I want the entire calligra suite, what should I be looking for on mcc?

Please test the package in updates_testing maybe it's work a little better.

ps: I don't know what to set for summary because you are very confuse.

CC: sysadmin-bugs => (none)
Summary: packages missing for KDE bug reporting => packages missing for KDE bug reporting (calligra crashing)

I don't use testing packages or stuff outside the official repositories


my goal was to have a database app similar to MS Access
the libre office version [base] has more than a few things that don't work & doesn't have anyone working on it

this lead me to Kexi, but no templates for forms
which lead me to try to install the rest of the calligra package, which being more nearly native to KDE, as I would prefer

clearly the calligra suite is not ready for use on Mageia 2 as yet

I'm not confused
calligra as installed on my machine, crashes & returns a series of missing stuff when I attempt to file a bug with KDE
to me it appears the problem is related to the calligra packages on mageia
hence I filed this bug

I hope this clears up any confusion you are perceiving

I told you about the package in testing since it's a new version, so you can enable the core/updates_testing repo, open rpmdrake, search calligra, install it, desactive the testing. (but if you don't wan't test..)

And kde bugs should be reported to the kde bugzilla (with the last version if possible) not in our one

how is an incomplete package [calligra] in mageia a KDE problem?
I have no idea of how to open rpm drake or what to do with it once open

should I gain any of these skills in the future, I'll check back

(In reply to comment #7)
> how is an incomplete package [calligra] in mageia a KDE problem?

Calligra is developped as part of KDE.
Mageia just takes Calligra as developped, adapting to Mageia if necessary (if at all), and adding patches from KDE for recently solved bugs.
The problem adding new documents is most likely a bug from KDE.
The problem filing the error reports automatically refers to KDE bugzilla and not Mageia bugzilla.
Note that Calligra is a relatively new and complex application, presumably undergoing a lot of development.  Thus open to a lot of bugs.

> I have no idea of how to open rpm drake or what to do with it once open

You could use the "install and uninstall software" option on the first page of the MCC, under menu : tools : system_tools : configure_your_computer.
Easier, use "install and uninstall software" at the bottom of the first menu page.
They both run rpmdrake, which can also be run directly in console.
(You have to enter your system password to start.)

Once in rpmdrake, choose menu : options : software_media_manager,
and check the leftmost box by "core updates testing" (which is "distrib5).
Then press "ok" to return to rpmdrake, and under calligra you will see the latest package from core/updates_testing.
(To verify, click on the package line above, and in the box below click on details to open, and by *Media* it should say "Core Updates Testing (distrib5)"
After installing the new package (with its' dependancies), return to the software media manager and uncheck "core updates testing".

> 
> should I gain any of these skills in the future, I'll check back

Hope the above helps.  If you have any questions, don't hesitate to ask.
Good luck

the path to add the core update testing repository

MCC>Software Manager>Configure Media Sources> core updates testing

I uninstalled calligra, checked to make sure there was no calligra or kexi left
installed calligra core version 2.4.3 1.mga2 x64

which fails  

Installation failed, some files are missing:
    rsync://mirrors.kernel.org/mirrors/mageia/distrib/2/x86_64/media/core/updates_testing/calligra-l10n-en_GB-2.4.3-1.mga2.noarch.rpm
You may need to update your urpmi database.

no update pending through mcc or notifier

(In reply to comment #9)
> the path to add the core update testing repository
> 
> MCC>Software Manager>Configure Media Sources> core updates testing
> 
> I uninstalled calligra, checked to make sure there was no calligra or kexi left
> installed calligra core version 2.4.3 1.mga2 x64
> 
> which fails  
> 
> Installation failed, some files are missing:
>    
> rsync://mirrors.kernel.org/mirrors/mageia/distrib/2/x86_64/media/core/updates_testing/calligra-l10n-en_GB-2.4.3-1.mga2.noarch.rpm
> You may need to update your urpmi database.

Note that the mirrors have
.../2/x86_64/media/core/updates_testing/calligra-l10n-en_GB-2.4.3-1.1mga2.noarch.rpm,
but only 2.4.3-1.mga2 for most other localisations.
(If correct, there was a recent update to en_GB, along with whatever other bug fixes.)

> 
> no update pending through mcc or notifier

Try updating your core/updates testing media again.
It was just updated (2012-07-23 16:50 UTC), and it could be that the mirror used wasn't completely up to date when you activated updates_testing.  Sometimes mirrors sync quite a few hours later.
(On activating a media, it automatically updates the media.)

If that doesn't work, this would probably be an error in how Mageia linked the dependancies.  We are working on replacing manual linking with an alternate (automatic) system.

I've tried to install a few time & still get the error [even after a few updates this morning]

still the same error

well your media seems to be not updated as kernel.org updates his mirrors less than every 5 hours

What is it that I should do about that?
here's a webalbum with my configure media
https://plus.google.com/photos/109896885556870005680/albums/5768846231101857521?authkey=CO6cm9uj14aOjAE

No it's Core Updates Testing (distrib4 iirc) and you should read a little doc (like browsing our wiki) before reporting bugs.

no idea what it is you are trying to tell me?
what is 
(distrib4 iirc)
?

(distrib 4) is show in rpmdrake-edit-media (and iirc is for if I remember correctly)

So if you still don't understand as root:
urpmi.update --no-ignore Core\ Updates\ Testing ; urpmi.update -a ; urpmi calligra

are you saying I should enable
Mirror list Core Update (distrib 4)
?

no, again one time, Core Updates testing.

I have
Mirror list Core Update testing (distrib 5)


I'm still trying to make sense of what you wrote on the 24th

@Garth
From your photos, you have the right media activated (Core Update testing = distrib5),
but you may need to update (refresh) the media since the mirror used might not have been completely up to date when you activated the media.
That just happens from time to time with mirrors if activated/updated shortly after new packages are added.

Just to make sure : When I asked you to try updating the media in comment #10, did you do, from rpmdrake (the menu which you show in your photos) :
menu : file : update_media
and check the box to the left of "Core Updates Testing (distrib5)"
then press the button "Update" to the lower right ?
This will download the info to update your rpm database of packages available.

If after doing that you still have a problem, then there is (probably) a bug to be fixed.

won the battle 
lost the war

thanks Andre,
I understand how to update my repositories now!

but after reinstalling 
calligra core & Kexi
I can't find any of the apps on the application launcher
I can type kexi in the search box on the app launcher & find kexi
which will launch kexi [no way to find on the apps menu or add to favorites]

went back & installed
calligra words, spread
I haven't been able to open these at all

clearly there is still a problem

It looks like you now need a KDE and/or Calligra expert.
Unfortunately I can't help much, as I use Gnome and not KDE.
You might try installing the various other Calligra packages not already installed, since it looks a lot like missing dependancies.
If you find that that works, in would be helpful to report back, as that would help it being fixed for other users.

Good luck :)

FWIW, as explained in forums thread https://forums.mageia.org/en/viewtopic.php?f=7&t=3166 normal core/release packages work just fine. Seesm to be a problem of not installing the whole of calligra, or missing dependencies, already encountered in https://forums.mageia.org/en/viewtopic.php?f=7&t=2843

CC: (none) => doktor5000

so as the forums users said they can't reproduce, changing the status

Status: NEW => UNCONFIRMED
Ever confirmed: 1 => 0

This message is a reminder that Mageia 2 is nearing its end of life.
Approximately one month from now Mageia will stop maintaining and issuing updates for Mageia 2. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '2'.

Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 2's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 2 is end of life.  If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia.

Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete.

-- 
The Mageia Bugsquad

Mageia 2 changed to end-of-life (EOL) status on ''22 November''. Mageia 2 is no
longer maintained, which means that it will not receive any further security or
bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of Mageia
please feel free to click on "Version" change it against that version of Mageia
and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--
The Mageia Bugsquad

Status: UNCONFIRMED => RESOLVED
Resolution: (none) => OLD