Mageia forum

Just installed Mageia 3 B2 on my newly reorganized box.

Install went well but I did not put on any particular DE. Booted up to some DE withwhich I am not the least familiar with.

Found the gui to add packages with. Would not work with some error about not being able to connect. Gui doesn't make much sense to me so I came back here and tried to do things in chroot.

Ran;

Code: Select all

[root@debian /]# urpmi --auto-update
Udisks daemon (udisks-daemon) is not running or not ready


I take it this was the problem when I was logged into Mageia too.

Get the same error with this, not surprising;

Code: Select all

[root@debian /]# urpmi task-xfce
To satisfy dependencies, the following packages are going to be installed:
  Package                        Version      Release       Arch   
(medium "Core Release")
  xfce4-artwork                  0.2          14.mga3       noarch  (suggested)
(medium "Core Release2")
  task-xfce                      4.10         2.mga3        noarch 
  xfmpc                          0.2.2        3.mga3        x86_64  (suggested)
4.8MB of additional disk space will be used.
4.3MB of packages will be retrieved.
Proceed with the installation of the 3 packages? (Y/n)
Udisks daemon (udisks-daemon) is not running or not ready
[root@debian /]#


Just took a look at the /etc/urpmi/mediacfg.d/Devel-3-x86_64/media.cfg file and I think that this looks fine;

Code: Select all

[core/release]
hdlist=hdlist_core_release.cz
name=Core Release
srpms=../../SRPMS/core/release
media_type=official:free:release


and this;

Code: Select all

[core/updates]
hdlist=hdlist_core_updates.cz
name=Core Updates
srpms=../../SRPMS/core/updates
media_type=official:free:updates
updates_for=core/release


Anyone have a clue to offer the clueless?

I should add that I set checked and FF had no trouble connecting with the net and the installer had no trouble updating packages.

That is a longstanding problem, best remove/disable the CD/DVD as a repo via drakrpm-edit-media.

doktor5000 wrote:That is a longstanding problem, best remove/disable the CD/DVD as a repo via drakrpm-edit-media.

Amazing how the package management systems use such different language.

So simple once you know the solution.

Have xfce4.10 installed. Will set it up later.

Time for bed.

Thanks an whole bunch. Would have lost sleep over this silly thing.

widget wrote:

doktor5000 wrote:That is a longstanding problem, best remove/disable the CD/DVD as a repo via drakrpm-edit-media.

Amazing how the package management systems use such different language.

Well, udisks is the backgrounddaemon which is responsible for removable/permanent storage devices and exposes them to the userspace.
Actually i think that's a good thing that urpmi/rpmdrake is so verbose there, otherwise you (or me) still wouldn't know where the problem
originates from

For background information, if you want you can take a look at https://bugs.mageia.org/show_bug.cgi?id=3639

Apart from that, please mark the thread accordingly by editing the topic of the first post and prefix it by [SOLVED], thanks

Interesting thing is that I am having no trouble with using urpmi but the gui is still not working.

It seems to be throwing 1 of 2 error messages at random. One is the same thing as before and the other is that something else is running.

As I had nothing running at the time I know that is wrong. Didn't even have thunar open, just the Mageia Control tool (which I like a lot). Could not update or install.

Urpmi is having no trouble. Just upgraded 2 packages and installed 2 with the attendent 33 depends and suggesteds.

In the background the update applet (mgaapplet) updates repository metadata when it checks for updates, but usually
in such a case urpmi or rpdmrake tell which process currently causes the locking, if i remember correctly.

Could you please post a screenshot if this reoccurs? You could also check in the same time via a terminal with e.g.

Code: Select all

ps -ef | grep -v grep | grep rpm

doktor5000 wrote:In the background the update applet (mgaapplet) updates repository metadata when it checks for updates, but usually
in such a case urpmi or rpdmrake tell which process currently causes the locking, if i remember correctly.

Could you please post a screenshot if this reoccurs? You could also check in the same time via a terminal with e.g.

Code: Select all

ps -ef | grep -v grep | grep rpm

I need to get back over there anyway so I will fool with it more.

Dropping the gui and going to urpmi did not bring any errors at all. Urpmi ran fine both updating and installing.

Running the command for drakrpm brought it up fine and it worked with no errors that way. I enabled and disabled a couple of things to check. It ran an update for all added media with no problem at all.

Will try all the package management stuff when I get over there very shortly.

widget wrote:It ran an update for all added media with no problem at all.

All added media, including testing? Can you please also post the output of

Code: Select all

urpmq --list-media active

doktor5000 wrote:

widget wrote:It ran an update for all added media with no problem at all.

All added media, including testing? Can you please also post the output of

Code: Select all

urpmq --list-media active

Code: Select all

[max@localhost ~]$ urpmq --list-media active
Core Release2
Core Updates
Nonfree Release2
Nonfree Updates
Tainted Release
Tainted Updates
Core 32bit Release
Core 32bit Updates
Core Release
Core Updates2
Nonfree Release
Nonfree Updates2
Tainted Release2
Tainted Updates2
Core 32bit Release2
Core 32bit Updates2


Now that is several more than it was before using drakrpm invoked from terminal.

Failed to open again, took a screen shot, dropped the error popup and had another saying the program had exited incorrectly, tried opening it again and it opened.

Dropped it and opened the package manager gui. Came up and is populated.

Dropped that after taking screen shots. Edited the shots for size. Then tried to reopen the gui. Wouldn't do it claimed it was still up. Closed it 3 times with the same song and dance. Forth try it opened back up fine.

This worries me about as much as the lack of working did. Do not see anything to have corrected it.