If someone having this problem could kill system-config-printer-applet and re-start it like "system-config-printer-applet --debug", we'd be able to see what interactions with gnomekeyring are performed.
The gnomekeyring data that system-config-printer uses are stored under key {domain,server,protocol}, and has the item {user} in addition to the secret. Looking again at the code, I see that domain is stored case-sensitively, and server is always converted to lower case.
Take a look using seahorse to see which passwords are stored under which keys. For example, I have an IPP password stored with display name tim@1921.68.122.197, and in the details it says:
If someone having this problem could kill system- config- printer- applet and re-start it like "system- config- printer- applet --debug", we'd be able to see what interactions with gnomekeyring are performed.
The gnomekeyring data that system- config- printer uses are stored under key {domain, server, protocol} , and has the item {user} in addition to the secret. Looking again at the code, I see that domain is stored case-sensitively, and server is always converted to lower case.
Take a look using seahorse to see which passwords are stored under which keys. For example, I have an IPP password stored with display name tim@1921. 68.122. 197, and in the details it says:
protocol: ipp
server: 192.168.122.197
user: tim