Comment 5 for bug 229750

that's because synaptic is ran using sudo and so doesn't use the current user settings, reassigning to synaptic, that will be fixed when synaptic will run as user and use policykit or similar to do priviledged actions