Gnome-keyring - unlocked

[simwin]

Plese help! :) Chromium, Chrome and Opera can't use gnome-keyring and I don't know why, what was doing by me...

Any error message?

chromium --enable-logging --v=10

Code: Select all

Using PPAPI flash.
[2573:2573:0722/023847.629965:ERROR:edid_parser.cc(102)] Too short EDID data: manufacturer id
[2573:2611:0722/023847.657287:ERROR:bus.cc(393)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[2573:2611:0722/023847.657350:ERROR:bus.cc(393)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[2573:2611:0722/023847.705783:ERROR:bus.cc(393)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[2573:2611:0722/023847.705858:ERROR:bus.cc(393)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[2612:2612:0722/023848.211788:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process.
[2612:2661:0722/023848.224186:ERROR:gbm_wrapper.cc(271)] Failed to export buffer to dma_buf: 
No such file or directory (2)
[2612:2661:0722/023848.224437:ERROR:gbm_wrapper.cc(271)] Failed to export buffer to dma_buf: 
No such file or directory (2)
[2612:2661:0722/023848.224554:ERROR:gbm_wrapper.cc(271)] Failed to export buffer to dma_buf: 
No such file or directory (2)
[2630:1:0722/023848.277511:ERROR:paint_controller.cc(646)] PaintController::FinishCycle() completed
[2630:1:0722/023848.405037:ERROR:paint_controller.cc(646)] PaintController::FinishCycle() completed
[2630:1:0722/023848.477842:ERROR:paint_controller.cc(646)] PaintController::FinishCycle() completed

Sorry - I have to sleep :) Try to solve to 02:40 am :)

[fehlix]

Plese help! :) Chromium, Chrome and Opera can't use gnome-keyring and I don't know why, what was doing by me...

Any error message?

chromium --enable-logging --v=10

Code: Select all

Using PPAPI flash.
[2573:2573:0722/023847.629965:ERROR:edid_parser.cc(102)] Too short EDID data: manufacturer id
[2573:2611:0722/023847.657287:ERROR:bus.cc(393)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[2573:2611:0722/023847.657350:ERROR:bus.cc(393)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[2573:2611:0722/023847.705783:ERROR:bus.cc(393)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[2573:2611:0722/023847.705858:ERROR:bus.cc(393)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[2612:2612:0722/023848.211788:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process.
[2612:2661:0722/023848.224186:ERROR:gbm_wrapper.cc(271)] Failed to export buffer to dma_buf: 
No such file or directory (2)
[2612:2661:0722/023848.224437:ERROR:gbm_wrapper.cc(271)] Failed to export buffer to dma_buf: 
No such file or directory (2)
[2612:2661:0722/023848.224554:ERROR:gbm_wrapper.cc(271)] Failed to export buffer to dma_buf: 
No such file or directory (2)
[2630:1:0722/023848.277511:ERROR:paint_controller.cc(646)] PaintController::FinishCycle() completed
[2630:1:0722/023848.405037:ERROR:paint_controller.cc(646)] PaintController::FinishCycle() completed
[2630:1:0722/023848.477842:ERROR:paint_controller.cc(646)] PaintController::FinishCycle() completed

Don't see any relationship with those error messages and your statement "can't use gnome-keyring".
The only one might be, a non running browser can not use gnome-keyring ... but you might have another reason, why you think that this has something todo with gnome-keyring. If not, your report would not fit into this thread.

[simwin]

Any error message?

chromium --enable-logging --v=10

Code: Select all

Using PPAPI flash.
[2573:2573:0722/023847.629965:ERROR:edid_parser.cc(102)] Too short EDID data: manufacturer id
[2573:2611:0722/023847.657287:ERROR:bus.cc(393)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[2573:2611:0722/023847.657350:ERROR:bus.cc(393)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[2573:2611:0722/023847.705783:ERROR:bus.cc(393)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[2573:2611:0722/023847.705858:ERROR:bus.cc(393)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[2612:2612:0722/023848.211788:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process.
[2612:2661:0722/023848.224186:ERROR:gbm_wrapper.cc(271)] Failed to export buffer to dma_buf: 
No such file or directory (2)
[2612:2661:0722/023848.224437:ERROR:gbm_wrapper.cc(271)] Failed to export buffer to dma_buf: 
No such file or directory (2)
[2612:2661:0722/023848.224554:ERROR:gbm_wrapper.cc(271)] Failed to export buffer to dma_buf: 
No such file or directory (2)
[2630:1:0722/023848.277511:ERROR:paint_controller.cc(646)] PaintController::FinishCycle() completed
[2630:1:0722/023848.405037:ERROR:paint_controller.cc(646)] PaintController::FinishCycle() completed
[2630:1:0722/023848.477842:ERROR:paint_controller.cc(646)] PaintController::FinishCycle() completed

Don't see any relationship with those error messages and your statement "can't use gnome-keyring".
The only one might be, a non running browser can not use gnome-keyring ... but you might have another reason, why you think that this has something todo with gnome-keyring. If not, your report would not fit into this thread.

Now I use nodm, fluxbox and I unlock gnome keys in seahorse by my hands. Chromium, Chrome and Opera can't generate its keys in gnome login key section. With lightdm the result is the same. All browsers can start and work perfectly, but save passwords without gnome-keyring in base type manner. May be some services don't run in fluxbox?

[simwin]

chromium --enable-logging --v=10

Code: Select all

Using PPAPI flash.
[2573:2573:0722/023847.629965:ERROR:edid_parser.cc(102)] Too short EDID data: manufacturer id
[2573:2611:0722/023847.657287:ERROR:bus.cc(393)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[2573:2611:0722/023847.657350:ERROR:bus.cc(393)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[2573:2611:0722/023847.705783:ERROR:bus.cc(393)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[2573:2611:0722/023847.705858:ERROR:bus.cc(393)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[2612:2612:0722/023848.211788:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process.
[2612:2661:0722/023848.224186:ERROR:gbm_wrapper.cc(271)] Failed to export buffer to dma_buf: 
No such file or directory (2)
[2612:2661:0722/023848.224437:ERROR:gbm_wrapper.cc(271)] Failed to export buffer to dma_buf: 
No such file or directory (2)
[2612:2661:0722/023848.224554:ERROR:gbm_wrapper.cc(271)] Failed to export buffer to dma_buf: 
No such file or directory (2)
[2630:1:0722/023848.277511:ERROR:paint_controller.cc(646)] PaintController::FinishCycle() completed
[2630:1:0722/023848.405037:ERROR:paint_controller.cc(646)] PaintController::FinishCycle() completed
[2630:1:0722/023848.477842:ERROR:paint_controller.cc(646)] PaintController::FinishCycle() completed

Don't see any relationship with those error messages and your statement "can't use gnome-keyring".
The only one might be, a non running browser can not use gnome-keyring ... but you might have another reason, why you think that this has something todo with gnome-keyring. If not, your report would not fit into this thread.

Now I use nodm, fluxbox and I unlock gnome keys in seahorse by my hands. Chromium, Chrome and Opera can't generate its keys in gnome login key section. With lightdm the result is the same. All browsers can start and work perfectly, but save passwords without gnome-keyring in base type manner. May be some services don't run in fluxbox?

My problem (and its name is Failed to connect to the bus) was solved by this line in ~/.xsessionrc:

• exec dbus-launch --sh-syntax --exit-with-session startfluxbox

The old version was:

• exec startfluxbox

So all my ~/.xsessionrc is:

Code: Select all

eval $(/usr/bin/gnome-keyring-daemon --start --components=pkcs11,secrets,ssh)
export SSH_AUTH_SOCK
exec dbus-launch --sh-syntax --exit-with-session startfluxbox 

[BitterTruth]

I added libpam-gnome-keyring to MX via Synaptic, and shutdown my MX system. When it reopened discovered It did not remember any passwords including Synaptic.
MX had forgotten all of my passwords.

OK, I digged into this a bit further ...
After adding libpam-gnome-keyring and having removed all
keyring-files from ~/.local/share/keyrings
only a logout/login is required. PAM will create a new login-keyring.
This new keyring will also become the "default" keyring, i.e. it has
the properties to be "default". And further PAM will unlock
this "default" login-keyring after you logged-in with a password.

Chrome will now see the new "default" keyring and will further use
this empty keyring to populated after syncing with your passwords.

Synaptic: We do have two GUI-ways to start synaptic, either through
the menu or through right-click of apt-notifier.
Starting synaptic through the menu will go through a pkexec-authentication
and will always ask for a password.

When you start synaptic through apt-notifier-icon it
goes with help of /usr/bin/su-to-root to a call of gksu.
Gksu is enabled with a PAM-API to call gnome-keyring.

And now we should assume that gksu would also use the "default" keyring,
which happens to be the login-keying, when you request the entered
password to be saved "permanently" not only for the session.

When you now enter the password to be saved "remember password"
it will than asked you to enter the password for a new "default" keyring.

And this is an outstanding bug with Gnome/GTK, which I remember have seen
a couple of years ago when gnome-keyring still was young.

The issue is that the gnome/gtk developer seem to be got confused
about the gnome-keyring API and the use of the term "default keyring".

The GTK-implementation used by gksu unfortunately misinterprets
the API-documention and do look for a keyring with the name "default"
instead of the property "default".
So the popup to create a new "default" keyring is about to create a new keyring
with the name "default", instead of using the existing "default" login-keyring

An the other side Chrome/Chromium are doing it right, both using
the existing login-keying (property default) to store/save the passwords.

Now what? The workaround is simple: Let GTK/gksu create
the new "default-keyring", i.e. enter any password you like.
The keyring will be unlocked by PAM. But you might still
enter than once again the password for the "default-keyring" where
you than got an option to click "remember password to unlock after login."

Summary: If you use app which intern relies on gksu, you might still need to"create" a new "default" keyring,
due to a gtk "bug" if you want to store the entered "root" password permanently.
Solution just create the new "default" keyring and click next time remember, if you like.

Ufff .. to many words .. I know .. sorry

APOLOGIES FOR BUMPING AN OLD THREAD but just to maintain the accuracy and completeness of the thread, I thought I would point out a couple of things here:

1) gksu has been deprecated from Debian so it can't be used any longer to 'unlock' synaptic in the way you described.

I had an amazing function in my MX15 build before I installed MX19 a few days ago which I really miss alot. Whenever I would run apt-notifier (or synaptic as you mentioned above and the package installer too if i remember correctly) a dialog box would come up and ask me if I wanted to save my sudo password for the session or for longer. I would choose entire session and then it was always so easy to keep opening synaptic without entering passwords. Over the last few days, I have had to open synaptic hundreds of times to check the packages themselves as well as detailed info on dependencies, file locations etc and it has been very very frustrating and exhausting to constantly type the password in.

Also

2) since I did an MX19 install with a preserved /home partition, my previous keys (Evolution, chrome) were still stored in ~./local/share/keyrings so I had a look and THEY WERE IN PLAIN TEXT FILES!!!!!! The Passwords and Keys app had also picked the old keys up automatically and they were saved in the app as well. I had 2 keys: Login and Default. The old chrome and old evolution (uninstalled a long time ago even before updating to MX19) passwords were stored under the Default key and the Login key was empty. The Default key was 'set as default'. I took your advice and deleted the old keyrings directory from my ~./local/share/ (actually I just renamed it keyrings.bak) and rebooted. After reboot, I checked Passwords and Keys and indeed there was only ONE key there called Login and it was 'set as default'. I close the app and then opened SLIMJET browser, which is based on Chromium and SLIMJET asked me to sign-in again. (I was already signed in before rebooting). Anyway, after signing in, I closed and re-opened Passwords and Keys app and there was still only one key: Login but this time the chrome and Chromium passwords were stored under it. When I clicked on the chrome password a dialog box came up with the password highlighted but hidden i.e. *********. I clicked on the symbol to see if it would reveal the password. IT DID, BUT IS WAS ENCRYPTED. I checked the ./local/share keyrings directory (the app automatically made a new one) and there are NO TEXT FILES so it looks like everything is working as it should and safe and secure.

To summarise: Just delete the hidden /home/user/.local/share/keyrings directory as Fehlix mentioned and reboot and you should be good to go.

[michaelbr]

Not sure if I can tag along or open another thread. I followed the instructions, when I closed my browser (Brave), and opened Password and Keys, my Login entry Set default is grayed out, what I'm missing? Here's my screenshot
ps: how can I post my image on my desktop?

[fehlix]

I followed the instructions, when I closed my browser (Brave), and opened Password and Keys, my Login entry Set default is grayed out, what I'm missing? Here's my screenshot

Not sure what you followd and what you actually did.
Just checked within a live system.
Installing Brave and Vivaldi from MX Package Installer ->Pop.Apps->Browser:
First on Live System I need to logout and login again, b/c live's auto-login would prevent PAM to create a login-keyring.
Opening Brave and closing shows in Password'n'Keys this:

brave-safe-storage.png

Now open Vivaldi:

chrome-safe-storage.png

So Vivaldi still uses the original chromium safe-storage name.
PS: You would attach an image with the "Attachments" button below the editor.

[michaelbr]

Not sure what you followd and what you actually did.
Just checked within a live system.
Installing Brave and Vivaldi from MX Package Installer ->Pop.Apps->Browser:
First on Live System I need to logout and login again, b/c live's auto-login would prevent PAM to create a login-keyring.

I followed your first post on this topic, when I tried to set my keyring as default, it's grayed out, unfortunately the screenshot doesn't allow me to right click, as you can see, the Brave is in the list.

[fehlix]

I followed your first post on this topic, when I tried to set my keyring as default ...

The automatically generated login keyring is also the default b/c there is only one keyring - nothing to set here.

[michaelbr]

The automatically generated login keyring is also the default b/c there is only one keyring - nothing to set here.

So why everytime I login, a message came up saying that

Code: Select all

my login keyring could not unlock

or something similar, and asked for my password? Is this supposed to work this way?
ps: I set to automatically login, this has something to do with asking for password?