Synaptic doesn't remember when pinned packages are unlocked

Bug #23476 reported by Eric Nichols
6
Affects Status Importance Assigned to Milestone
synaptic (Ubuntu)
Fix Released
Medium
Michael Vogt

Bug Description

Under the latest Breezy, I am having trouble unlocking pinned packages in synaptic.
I can unlock them from the menu option, but if I close synaptic and reopen it the
packages revert to their pinned state.

Revision history for this message
Dennis Kaarsemaker (dennis) wrote :

Did you hit apply?

Revision history for this message
Eric Nichols (eric.nichols) wrote :

You can't hit the apply button if the only thing you have done is unlock packages;
it remains inactive.

Revision history for this message
Michael Vogt (mvo) wrote :

Thanks for your bugreport.

I can't reproduce the problem here, can you please send me your
"/var/lib/synaptic/preferences" file ?

If the trouble is that you can't unlock packages that you locked "by-hand" (e.g.
by editing /etc/apt/preferences) than this is intentional. Synaptic will not
mess with the configuration in /etc/apt.

Revision history for this message
Eric Nichols (eric.nichols) wrote :

Created an attachment (id=4518)
Synaptic preferences file

Revision history for this message
Eric Nichols (eric.nichols) wrote :

I have attached my Synaptic preferences file. I pinned these packages using the
"lock package"
in Synaptic. I have not done any pinning "by hand", thus, I do not have an
/etc/apt/preferences
file. Is there anything in my apt settings independent of pinning-related
settings that could
be causing this behavior?

Revision history for this message
Michael Vogt (mvo) wrote :

(In reply to comment #5)
> I have attached my Synaptic preferences file. I pinned these packages using the
> "lock package"
> in Synaptic. I have not done any pinning "by hand", thus, I do not have an
> /etc/apt/preferences
> file. Is there anything in my apt settings independent of pinning-related
> settings that could
> be causing this behavior?

Thanks for your preferences file. I just tried to reproduce the problem with it
and was not successful (that means, it works for me).

Do you see anything usefull in your ~/.xsession-error file that looks releated
to this problem (feel free to attach it here). And what locale do you use?

Revision history for this message
Eric Nichols (eric.nichols) wrote :

Created an attachment (id=4539)
X session errors file

Revision history for this message
Eric Nichols (eric.nichols) wrote :

Created an attachment (id=4540)
X session errors on Synaptic restart

Revision history for this message
Eric Nichols (eric.nichols) wrote :

I have attached my .xsession-errors file. It had a couple of errors messages
that seem relevant.
I am using en_US.UTF-8 as my locale, but I also have the SCIM IME installed to
allow me to type
in Japanese. Perhaps this is the source of my problems?

Revision history for this message
Michael Vogt (mvo) wrote :

Is this still a problem with current dapper? I remember that I fixed a error in this a while ago.

Cheers,
 michael

Revision history for this message
Michael Vogt (mvo) wrote :

I close this bug for now because I got no feedback that it still happens. I'm pretty sure I fixed this bug. Please reopen if you still can reproduce it.

Changed in synaptic:
status: Needs Info → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.