Every time I plug in an iPhone to charge it from a USB hub connected to my PC, Zorin pops up a message saying...
Device Locked
The device "" is locked.
Enter the passcode on the device and click "Try again".
I have no desire to access the phone from my PC. I'm just charging it. But this message covers up the entire desktop every time forcing me to click cancel. I don't see any options to disable this nor does it even indicate what part of the system is reporting this to help see if there's an option there to stop this. Is there really no way to stop this unwanted behavior? I don't see this message when I plug in an android phone. It shows the android phone connected but doesn't bother me about it.
Hello and welcome,
You can try to take a look at this
Thanks. I had USB accessories turned off on the iphone. I tried turning it on and nothing changed. While it seems iOS is doing something different from android here, it's also that Zorin is doing something as well. I shouldn't have to change the phone. I would expect that there's something in Zorin that is trying to do something when an iOS phone is connected that is showing this message as it shows up on my PC, not on the phone. I want Zorin to stop doing that.
Just as a note, Windows was on my PC before this and it never did anything like this when I plugged this same phone into the same PC. So something in Zorin is trying to be overly fancy and try to automatically do something that I have no desire it do but I cannot find where it is set so that I can tell it to not try to be fancy.
try to disable auto-mounting
to disable automatic device mounting:
- Open Settings
- Apps > Default apps
- Look for options related to removable media or device auto-mount
- Disable auto-mounting there
Just know that comparing windows and linux is useless, 2 systems, 2 philosophy, and if windows doesn't care about security, linux does, because it prevent you when you plug something lock by security...
Settings->Apps->Default Apps has "Automatically Launch Apps" turned off for removable media. I was looking for any settings related to auto-mount and nothing comes up. And of course I want auto-mount for normal usb storage devices as that's what they are used for. The phone should only be used as a storage device when the phone itself approves that it should be used for storage. The phone asks when I plug it in if it should trust the computer it's been connected to. The PC doesn't need to do that. Or at least not until the phone has been approved and is indicating that it is ready to connect. Then the PC can complete the connection.
I only brought up Windows to give an example where things work as I would expect. Not trying to start a philosophy discussion here. I'm not sure how popping up a message that blocks the entire system after plugging in a phone is "more secure". More secure would be to just don't do anything. The list of connected devices in the system tray shows the devices and could be used to approve the connection if I wanted it to connect instead of it trying to do it automatically. Trying to connect to a phone automatically sounds more insecure than not doing anything until a user indicates they want something to happen.
So I installed some updates and rebooted in addition to the attempted settings changes on the PC and phone and the behavior seems to have changed. This time when I plugged in the phone, the message was something more along the lines of "Press Trust on the phone." It still blocked the entire system to let me know this as if it was the most important thing I needed to address immediately. But this matches more with what the phone was saying. So I did just hit Trust on the phone since this is my phone and my PC. Now I can connect the phone when locked and it charges but nothing happens on the PC like I would expect. If I do unlock the phone, the phone is accessible from my PC which I have no need for but at least it's not annoying. I doubt it was the software updates but is likely one of the changes I tried that didn't do anything on change but did change on reboot. Unfortunately I don't have an easy way to know what specific changed. But for as it is, the issue is resolved.