Description of problem: Hello, When I connect a scsi burner or a pendrive to some of my USB 3.0 ports, automount does not mount automatically as usual and nautilus does not show the info message and the unit mounted. dmesg command detects units connected to this ports but it is necessary to mount them manually using command "mount". Version-Release number of selected component (if applicable): GNOME nautilus 3.10.1 How reproducible: Connect a pendrive to an USB 3.0 port. Steps to Reproduce: 1.Connect a pendrive to an USB 3.0 port. 2. 3. Actual results: Unit is not mounted automatically. Expected results: nautilus info message informing about new device detected and mount proccess without do it manually. Additional info: My system is Fedora 20 64bits alpha daily updated
Nautilus does not show me a bluray disc inserted as usually did.
MIght be related to https://bugzilla.redhat.com/show_bug.cgi?id=1042715 and caused by a kernel bug.
Hello Again, Due to a recent update this issue is now solved and automount works well. Thanks a lot, Alberto.
Hi again, Maybe the recent update I mentioned before didn't work enough. I mean, nautilus shows my blu-ray discs mounted but I didn't see the gnome's info message (at the bottom of the screen) indicating there is a new disc mounted. Maybe this is the cause of I can't burn correctly blank blu-rays discs using k3b. The problem is also extensible connecting usb 3.0 devices to usb 2.0 ports. * See:https://bugzilla.redhat.com/show_bug.cgi?id=1051806 Thanks, Alberto Segura.
Created attachment 852335 [details] k3b log error burning blu-ray disc
(In reply to Alberto Segura from comment #5) > Created attachment 852335 [details] > k3b log error burning blu-ray disc ... Maybe the automount problem is not extensible to all usb 3.0 devices: I have a usb 3.0 external hard disks working well without automount info message. Probably I can focus the error to my external usb 3.0 blu-ray burner (model LG BH12LS38) it used to work well under Fedora 19 (with some errors sometimes) but I think my device works well, I'm not sure what the problem is. I attach a file with some dmesg and lshw output... Thanks, Alberto Segura.
Created attachment 852348 [details] dmesg_lshw_related_to_my_device
Created attachment 852375 [details] Success recording dvd+r disc according to k3b log I think this problem is only reproducible now burning blank blu-ray discs with my device using k3b. There's a remote possibility that my blank blu-ray discs were defective (mediarange branded). But the use to work well some months ago. Thanks, Alberto
Created attachment 852547 [details] Successful blu-ray disc recording session using Nero Linux. Log detalis.
Today I was able to burn a blu-ray disc without problems using Nero Linux. I can discard defective blank media/burner and blame k3b or dvd+rw-tools. Thanks, Alberto.
I have experienced some nero errors. I think the automount problem still persists. When mounting unit I can here the gnome notification info sound but not always the info message. When I cannot see the info message (at the bottom of the screen) the probability of error during blu-ray burning process increases.I attach the nero session error log. Thanks, Alberto.
Created attachment 852670 [details] error in blu-ray burning session using Nero linux. Log details.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Hello, Yo can close it, I think it works. Thanks, Alberto. :)
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.