Description of problem: User1: jspaleta is the console owner cat /var/run/console/console.lock jspaleta User2: testuser is a second user logged in vig gdmflexiserver There are 2 devices which are mountable by the console owner on the system the floppy drive and the cd-rw. These devices are visible in both the jspaleta AND the testuser's Computer window in the Gnome desktop. Attempting to interact with the cd-rw device to eject it in testuser's desktop via the right click menu in the Computer window results in a nautilus crash.. which can not be recovered from. The gnome-session process for testuser must be killed and the gdmflexiserver restarted. Crash dialog appears in testuser's desktop but can not be interacted with to cancel or restart. Version-Release number of selected component (if applicable): nautilus-2.14.0-1 How reproducible: Everytime I have user2 login via a gdmflexiserver session while user1 is already logged in. 1)login to gnome on the console as user1 2)from a terminal in user1's desktop start gdmflexiserver-n 3)login to gnome desktop as user2 in the gdmflexiserver window 4)in user2's desktop open computer window find the cd-rw device and attempt to eject it 5)watch as the crash dialog for nautilus appears for user2 and user2's login session locks up requiring killing of the gnome-session manually. also happens with non-nested gdmflexiserv session for user2 Expected results: nautilus should fail gracefully to eject, similar to how it fails gracefully when attempting to mount the devices which user2 doesn't have permissions to interact with. Nautilus should most definitely not crash. -jef
This could be related to the bug I just submitted: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=188259
Created attachment 129495 [details] Backtrace of Bug 186740 Confirmed, and I made a backtrace just in case it reveals anything.
Fedora Core 5 and Fedora Core 6 are no longer maintained. Is this bug still present in Fedora 7 or Fedora 8?
Fedora apologizes that these issues have not been resolved yet. We're sorry it's taken so long for your bug to be properly triaged and acted on. We appreciate the time you took to report this issue and want to make sure no important bugs slip through the cracks. If you're currently running a version of Fedora Core between 1 and 6, please note that Fedora no longer maintains these releases. We strongly encourage you to upgrade to a current Fedora release. In order to refocus our efforts as a project we are flagging all of the open bugs for releases which are no longer maintained and closing them. http://fedoraproject.org/wiki/LifeCycle/EOL If this bug is still open against Fedora Core 1 through 6, thirty days from now, it will be closed 'WONTFIX'. If you can reporduce this bug in the latest Fedora version, please change to the respective version. If you are unable to do this, please add a comment to this bug requesting the change. Thanks for your help, and we apologize again that we haven't handled these issues to this point. The process we are following is outlined here: http://fedoraproject.org/wiki/BugZappers/F9CleanUp We will be following the process here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this doesn't happen again. And if you'd like to join the bug triage team to help make things better, check out http://fedoraproject.org/wiki/BugZappers
This bug is open for a Fedora version that is no longer maintained and will not be fixed by Fedora. Therefore we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen thus bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.