In Mandriva, that file is part of the w3c-libwww package.

CC: (none) => davidwhodgins
Source RPM: (none) => qutecom-2.2-6.mga1.src.rpm

I just realized w3c-libwww is available in Mageia, so it's just a missing requires
in the qutecom package.

Workaround would be to manually install w3c-libwww.

Which to install? 

a) w3c-libwww (HTTP library of common code)
b) w3c-libwww-apps

or both?

You can use "urpmf libmd5.so.0" to see which package contains the file.
It shows that it can be found in w3c-libwww (so w3c-libwww-apps is not necessary, unless its a required dependency of the first one, but urpmi will tell you):
   [root@cauldron akien]# urpmf libmd5.so.0
   w3c-libwww:/usr/lib/libmd5.so.0
   w3c-libwww:/usr/lib/libmd5.so.0.1.0

CC: (none) => rverschelde

Rémi, 

I installed the file w3c-libwww. Qutecom continued without work.

I commented in the forum Mageia:

https://forums.mageia.org/en/viewtopic.php?f=7&t=541&p=3441#p3441

Obs: This software Qutecom has a bug 60902 already registered on Mandriva bugzilla since September 2010 and is still open.

What happens now when you try to run qutecom in a terminal?

I've installed qutecom and w3c-libwww in an install running cauldron,
and the program seems to be working fine here.

IINM libmd5.so.0 is only loaded by the crash reporter (google-breakpad), so it's a result of the crash but not the main cause.

What happens now when you load qutecom from terminal?

(In reply to comment #7)
> IINM libmd5.so.0 só é carregado pelo repórter acidente (google-Breakpad), por isso é uma consequência do acidente, mas não a causa principal.
> O que acontece agora, quando você qutecom carga do terminal?

Two windows didn't open completely and I type the command "ctrl esc" and it says: "process stopped expecting something to happen". I wait and nothing happens.

( https://forums.mageia.org/en/viewtopic.php?f=7&t=541&p=3441#p3463 )

Try loading it this way:
qutecom -style plastique

Keywords: (none) => NEEDINFO

(In reply to comment #9)
> Try loading it this way:
> qutecom -style plastique

I did as you suggested:

    "qutecom -style plastique"

It worked. 

thanks :)

Note: I'm using the GTK + style (is it the reason it has not worked?)

Created attachment 564 [details]
Testing urpmi command to see if any packages are missing.

Please run the attached script, to see if it would install any packages.
(it won't actually install anything due to the --test option)

I generated the command by running qutecom in a 32 bit kde clean install of
mageia 1 under strace, piping the strace output to a file.  I then ran a script
that extracts all file names accessed by the program, and then uses rpm to
find the package that owns the file.  It then generates the list of packages
used in the form of a urpmi command.

If running the command in the attachment will install any packages, please
post back which ones they are.

Sorry missed that you have it working. Please ignore my prior posting.

(In reply to comment #10)
[...]
> Note: I'm using the GTK + style (is it the reason it has not worked?)

Yeah, it's the GTK+ style, it's an upstream issue, see the last comment here: http://trac.qutecom.org/ticket/154

Maybe you should open a bug report upstream.

Keywords: NEEDINFO => Triaged
Summary: Qutecom doesn't run - Mageia 1 => Qutecom doesn't run when the GTK+ Qt style is used

This issue has been added to the Errata: http://www.mageia.org/wiki/doku.php?id=mageia1:errata#qutecom_crashes_or_hangs_showing_blank_windows_when_launched

cc'ing fwang who committed qutecom several times for cauldron

CC: (none) => fundawang, marja11

No changes to the upstream bug report

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

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 1'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 1 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.

--
Mageia Bugsquad

Mageia 1 changed to end-of-life (EOL) status on ''1st December''. Mageia 1 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.

--
Mageia Bugsquad

Status: NEW => RESOLVED
Resolution: (none) => WONTFIX