Bug 148324

Summary: flash automounts on first user graphics session instead of second
Product: [I don't know] kde Reporter: Marina Korobejnikova <salatiq>
Component: generalAssignee: Stephan Kulow <coolo>
Status: RESOLVED FIXED    
Severity: normal CC: nate
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Debian stable   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Marina Korobejnikova 2007-07-29 14:12:49 UTC 
Version:            (using KDE KDE 3.5.7)
Installed from:    Debian stable Packages
OS:                Linux

I have Debian GNU Linux (lenny) with kernel 2.6.18 compiled from sourse on debian.nsu.ru (notebook hp)

When automounted flash on second graphics kde session it said that access denied. Flash was automounted on first session and there all was right.

Steps:
1. Turn on computer.
2. Start kdm.
3. login as one user
4. press Ctrl+Alt+f8 
5. login as another user 
6. insert usb flash
7. click "open" dialog 

result: opens empty folder and writes that access is denied.

8. press Ctrl+Alt+f7

result2:  flash successfully automounted and I can work with it.

But second user should have had access instead of first.

Thanks, 
Marina Korobejnikova, 
former QA Engineer (Sibers), 
student of Novosibirsk State University.
Comment 1 Andrew Crouthamel 2018-11-02 04:15:52 UTC 
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 2 Andrew Crouthamel 2018-11-16 02:45:55 UTC 
Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version?

Thank you for helping us make KDE software even better for everyone!
Comment 3 Nate Graham 2020-09-28 23:40:28 UTC 
No response; assuming it was fixed since then.