Bug 14805 - 5beta2: USB stick not being auto mounted or any notification in gnome
Summary: 5beta2: USB stick not being auto mounted or any notification in gnome
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Olav Vitters
QA Contact:
URL:
Whiteboard: 5beta2
Keywords: NEEDINFO
Depends on:
Blocks:
 
Reported: 2014-12-15 16:33 CET by claire robinson
Modified: 2015-05-16 19:31 CEST (History)
3 users (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments
journal.txt (1.65 KB, text/plain)
2014-12-15 16:39 CET, claire robinson
Details

Description claire robinson 2014-12-15 16:33:17 CET
5beta2 Classic DVD 32 with default gnome installation

Plugged in a USB stick to save some debugging files onto but it is not auto mounted. Neither is there any notification on the desktop that it has been plugged in.

The journal shows it is being recognised and assigned as sdf with sdf1 partition but not mounted.

Reproducible: 

Steps to Reproduce:
claire robinson 2014-12-15 16:33:50 CET

Source RPM: (none) => ennael
Whiteboard: (none) => 5beta2

claire robinson 2014-12-15 16:34:04 CET

CC: (none) => ennael1
Source RPM: ennael => (none)

Comment 1 claire robinson 2014-12-15 16:39:01 CET
Created attachment 5710 [details]
journal.txt

journal snippet showing device being plugged in and unplugged.

Note it ends with..

systemd-udevd[502]: error opening USB device 'descriptors' file
claire robinson 2014-12-15 16:39:13 CET

CC: (none) => mageia

Comment 2 Marja Van Waes 2015-04-14 20:45:34 CEST
Is this bug still valid for 5RC?

CC: (none) => marja11

Comment 3 Samuel Verschelde 2015-05-16 19:18:38 CEST
(In reply to Marja van Waes from comment #2)
> Is this bug still valid for 5RC?

same question about 5final :)

Keywords: (none) => NEEDINFO

Comment 4 claire robinson 2015-05-16 19:31:29 CEST
fixed now

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


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