Bug 8533 - rpmdrake requests "Insert core release" which is inserted
Summary: rpmdrake requests "Insert core release" which is inserted
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-12-28 15:15 CET by Pierre Jarillon
Modified: 2015-04-16 22:31 CEST (History)
1 user (show)

See Also:
Source RPM: urpmi
CVE:
Status comment:


Attachments

Description Pierre Jarillon 2012-12-28 15:15:26 CET
I made a fresh install of mga3 b1 on a laptop. At the end of the installation, the remote sources of packages were not loaded.
I reboot, start mcc -> rpmdrake and select some packages to install. I press the button Apply, agree the list and I got the message: « insert the media "Core Release" »

The media is already inserted, I just close the tray, but the same massage is issued again. 

IMO, the name requested is not the name of the DVD...
Comment 1 Pierre Jarillon 2012-12-28 16:11:33 CET
Other way to investigate:
- The DVD cannot be mounted as a file system. There is also a problem to mount an USB memory key. I open another bug report.
-
Comment 2 Manuel Hiebel 2012-12-28 18:04:02 CET
the mounting issue is a dbus issue, for « insert the media
"Core Release" » can you attach your file /etc/urpmi/urpmi.cfg

Component: Release (media or process) => RPM Packages
Source RPM: (none) => urpmi

Comment 3 Pierre Jarillon 2012-12-28 19:13:27 CET
See https://bugs.mageia.org/show_bug.cgi?id=8381 it can be the same problem...

USB memory key are not detected. I can mount it with diskdrake.
Comment 4 Marja Van Waes 2015-04-16 22:31:29 CEST
Sorry, but this bug saw no action since over 2 yrs ago - no cauldron package has stayed the same - and is still assigned to Bug Squad.

Closing as OLD

Please reopen if this report is still valid for _current_ cauldron and/or fully
updated Mageia 4

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


Note You need to log in before you can comment on or make changes to this bug.