Bug 10412 - removable media cannot be mounted
Summary: removable media cannot be mounted
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 3
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords: NEEDINFO
Depends on:
Blocks:
 
Reported: 2013-06-03 16:46 CEST by Joep van Ham
Modified: 2015-03-31 02:45 CEST (History)
4 users (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description Joep van Ham 2013-06-03 16:46:35 CEST
Description of problem:


Removable madia cannot be mounted even after correct configuration in mageia's config centre.IT happens permanently.
This is a very great problem: all my data are saved on removable disks
Please afvise asap.
Regards Joep van Ham

Reproducible: 

Steps to Reproduce:
Comment 1 Thierry Vignaud 2013-06-03 20:49:18 CEST
You shouldn't setup anything in MCC for removable media.
What desktop are you using? GNOME? KDE?

Keywords: (none) => NEEDINFO
CC: (none) => thierry.vignaud
Component: Release (media or process) => RPM Packages
Source RPM: Mageia-3 upgrade from mageia 2 => (none)

Comment 2 Joep van Ham 2013-06-10 19:55:04 CEST
I am using KDE.
In between I restarted mageia 2 from scrats (DVD with ktorrent) after formating the complete disk(partions sdb1, sdb5 sdb6). easy, because all my data were on removable disks.Mageia2 works absolutely fine
I wantes to install netherlands in gnucash by:
LABGUAGE=ll_LL LANG=nl_NL
This instruction is unkown in KDE.
Is there a language instruction in KDE?
Tia and regards,
Joep van Ham
Comment 3 Dan Fandrich 2013-06-16 11:21:58 CEST
Please provide the steps to reproduce this problem. It's not clear at what stage you are experiencing issues.

CC: (none) => dan

Comment 4 Nic Baxter 2015-03-31 02:45:46 CEST
Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution.

Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information.

Closing as OLD.

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


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