"RPM installer" is packagekit? (or rpmdrake), which one do you mean here?

Keywords: (none) => NEEDINFO

Sorry, it is "package installer". I set the locale to "English" and saw the exact English name. I found something different. If clicking a rpm package file in English locale, it will respond quickly. But when I click "Install" in the window "Do you want to install the file?", it will shows "Faild to install file" and the error detail is "InstallFiles not yet supported by backend". There is no window to ask root password. If I click "Close" in the window "Do you want to install the file?", it will shows "The request failed" and the error detail is "Message did not receive a reply (timeout by message bus)".

Source RPM: rpm installer? => Package installer

That's gnome-packagekit, IINM.

(FWIW, the default package manager GUI in Mageia is rpmdrake).

Keywords: NEEDINFO => Triaged
Source RPM: Package installer => gnome-packagekit

(In reply to comment #3)
> That's gnome-packagekit, IINM.
> 
> (FWIW, the default package manager GUI in Mageia is rpmdrake).

Right! I am using gnome. How can it work properly?

Well, after uninstalling gnome-packagekit-common, the problem is solved. The problem was caused by gnome-packagekit-common.

Indeed : packagekit support by urpmi is not perfect, you should use rpmdrake and gurpmi.

Closing this bug

Status: NEW => RESOLVED
CC: (none) => sfietkonstantin
Resolution: (none) => INVALID

Sorry for changing my mind quickly, but I think that packagekit support should be improved and so I reopened it with a better title, and targets packagekit now.

Status: RESOLVED => REOPENED
Resolution: INVALID => (none)
Summary: Rpm installer is extremely slow to respond. => Packagekit RPM installer is extremely slow to launch and does not support installing

Well we need a perl hacker to update the urpmi backend :/

CC: (none) => balcaen.john

Or we may use yum instead (for packagekit)
But I don't know if urpmi and yum are compatible ...

I'm not sure yum can handle our hdlist :/

Be aware of https://bugs.mageia.org/show_bug.cgi?id=2343#c10
which is currently blocking the update candidate
packagekit-0.6.13-3.4.mga1.src.rpm

CC: (none) => davidwhodgins

tracked at https://bugs.launchpad.net/rpm/+bug/913213

CC: (none) => n3npq

(In reply to comment #11)
> Be aware of https://bugs.mageia.org/show_bug.cgi?id=2343#c10
> which is currently blocking the update candidate
> packagekit-0.6.13-3.4.mga1.src.rpm

setting this bug to depend on bug 2343

CC: (none) => marja11
Depends on: (none) => 2343

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

(In reply to comment #2)
> ...when I click "Install" in the
> window "Do you want to install the file?", it will shows "Faild to install
> file" and the error detail is "InstallFiles not yet supported by backend".
> There is no window to ask root password...


The bug is still valid for Mageia 2 as the above description. It is caused by gnome-packagekit-common (GNOME GUI for packagekit). After uninstalling it, packagekit works properly. However, gnome-packagekit-common is a dependency of file-roller (An archive manage for GNOME) and its uninstallation will cause the uninstallation of file-roller. It's a dilemma for GNOME users.

Version: Cauldron => 2
Source RPM: packagekit => gnome-packagekit-common
Whiteboard: (none) => MGA2TOO

When I try to use Apper to install a RPM package in Nautilus of GNOME 3, an error says "Your current backend does not support installing files". The backend of gnome-packagekit-common and apper should be PackageKit, and Packagekit itself works properly.

Source RPM: gnome-packagekit-common => gnome-packagekit-common, apper

I am experiencing the same problem in the GNOME 3 GUI,when trying to install a driver for my Epson printer. Trying to install the exact same package from the command line kicks up a totally different error:

# urpmi epson-inkjet-printer-nx420-1.0.0-1lsb3.2.x86_64.rpm
In order to satisfy the 'sendmail-command' dependency, one of the following packages is needed:
1- postfix-2.8.8-1.mga2.x86_64: Postfix Mail Transport Agent (to install)
2- sendmail-8.14.5-2.mga2.x86_64: A widely used Mail Transport Agent (MTA) (to install)
3- ssmtp-2.64-5.mga1.x86_64: A minimal mail-transfer agent which forwards mail to an SMTP server (to install)
4- msmtp-1.4.24-1.mga2.x86_64: An SMTP client (to install)
5- dma-0.7-1.mga2.x86_64: dma is an end-system mail server and supports queueing and local & remote mail delivery via SMTP and SSL/TLS (to install)
What is your choice? (1-5)

Is anyone else experiencing this behavior at the command line on the same package that gives the bug report error in the GUI? Personally, I don't understand why installing a printer driver should kick up a dependency error for an MTA...

CC: (none) => globetrotterdk

(In reply to comment #18)
> Personally, I don't
> understand why installing a printer driver should kick up a dependency error
> for an MTA...

As already mentioned in forum thread, this is totally unrelated to this bug and the overall problem. You should complain to Epson about their driver packages.

CC: (none) => doktor5000

I absolutely agree that the fundamental problem, in this instance, is with the vendor. That doesn't necessarily mean that the inarticulate GUI response is unrelated to the command line kicking up a totally different error, however.

Well, maybe you misunderstood, it does not kick up a totally different error, it just wants to tell you that it currently doesn't support selecting from different alternatives in case you get to choose between multiple packages which provide the same thing.

As mentioned in Comment 16 you could try to remove the package gnome-packagekit-common and it should work then, seems like a minor integration issue.

should be quite a lot better in mga3

CC: (none) => thierry.vignaud

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: REOPENED => RESOLVED
Resolution: (none) => OLD