Mageia forum

Booting into a recent Beta1 installation I found out that - as if by magic - the continously conecting/disconnecting of the wifi network is gone.
Then I opened a text window and as root did

Code: Select all

# urpmi --auto-update
service usdisks (udisks-daemon) is not running or not ready
#

As the problem I mentioned above was probably caused by usdisks this seems to leave me in a lose:lose situation: either usdisks is running and I have no network or udisks is not running and I have a network but urpmi will not work.

Ah, stepped in to the trap of the forgotten cdrom in the list of package sources!
When I started urpmi it looked at the urpmi.cfg and found cdrom - as we all know this does not work.

After I removed the cdrom entry and added the proper package sources it worked ok.

Sorry for the DUA
(dumb user alert)

wobo wrote:When I started urpmi it looked at the urpmi.cfg and found cdrom - as we all know this does not work.
After I removed the cdrom entry and added the proper package sources it worked ok.

Would be nice if bugzilla #145 (the bug that causes this problem) would get fixed - quite an oldie by now. This kind of work-around is perfect during alpha testing, but should not survive into the beta period!

wobo wrote:When I started urpmi it looked at the urpmi.cfg and found cdrom - as we all know this does not work.

That's not true anymore, urpmi has been migrated to use udisks, but the problem is IIRC that we now have udisks2 in cauldron
and that's why you get that message, urpmi cdrom usage should be fine again.

doktor5000 wrote:

wobo wrote:When I started urpmi it looked at the urpmi.cfg and found cdrom - as we all know this does not work.

That's not true anymore, urpmi has been migrated to use udisks, but the problem is IIRC that we now have udisks2 in cauldron
and that's why you get that message, urpmi cdrom usage should be fine again.

No, obviously not. After I removed the cdrom entry the failure message about udisks was gone and I could use urpmi. This looks very much as a related issue.

Also in my experience, if you have udisks AND udisks2 then floppy mounting fails. That was Alpha2/3. In Beta1 I have no udisks, only udisks2 and everything seems to work fine. No cdrom in urpmi config so I'll check that now and see what happens...

wobo wrote:

doktor5000 wrote:

wobo wrote:When I started urpmi it looked at the urpmi.cfg and found cdrom - as we all know this does not work.

That's not true anymore, urpmi has been migrated to use udisks, but the problem is IIRC that we now have udisks2 in cauldron
and that's why you get that message, urpmi cdrom usage should be fine again.

No, obviously not. After I removed the cdrom entry the failure message about udisks was gone and I could use urpmi. This looks very much as a related issue.

Well, the previous error message was about hald not started/missing, not udisks. So the problem has just been updated
Surely the workaround of removing the cdrom medium still works, as it has the same root cause.

This sounds like what I just experienced.

Yes, the original bug has been marked as fixed, and after I commented out the entry in /etc/fstab for the cdrom, it was smooth sailing. I was going to add to the original bug report, but it is fixed, therefore hidden.

Today's updates called for the CD-ROM. I hadn't noticed it in KDE's list of removeable media found. There was a directory for cdrom/ under media/ which I hadn't put there.

I put in the DVD. It wasn't detected.

I ran "mount /media/cdrom" Reply: No such entry in /etc/fstab or /etc/mtab.

I uncommented the line in /etc/fstab and was able to mount the DVD. It was /dev/hda and not /dev/sr0, but that is a different bug. Dave Hodgins pointed me to the workaround for it. Talking about udisks-daemon is over my head, but I am willing to look if pointed in the right direction.

OT: why do updates need the CD at all? Isn't it history?

jaywalker wrote:Also in my experience, if you have udisks AND udisks2 then floppy mounting fails. That was Alpha2/3. In Beta1 I have no udisks, only udisks2 and everything seems to work fine. No cdrom in urpmi config so I'll check that now and see what happens...

However, there are still requirements for udisks:

Code: Select all

rpm -e udisks-1.0.4-5.mga2
error: Failed dependencies:
        udisks is needed by (installed) lib64gdu0-3.0.2-1.mga2.x86_64
        udisks is needed by (installed) libgdu0-3.0.2-1.mga2.i586
        udisks is needed by (installed) perl-Hal-Cdroms-0.04-2.mga2.noarch
        udisks is needed by (installed) kdelibs4-core-2:4.8.2-1.mga2.x86_64

I know about the KDE requirement for udisks but I am not in a position to explore exactly what use it makes of it. I was able to get around the perl-HAL-cdroms trap when it appeared on my test systems after an update a while back. I don't think I ever found out what "update" had made it re-appear but getting rid of it again was a complete cure.

I can't comment on libgdu. It isn't on my test systems and a quick google only told me it is a Gnome thing to to with disks and, presumably, interfacing with the deprecated udisks system.