As I tried to decsribe, that was only after I created an empty db with
executing "touch /home/XXX/.local/share/flatpak/db/documents". Please
ignore that.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://
There does not seem to be anything relevant in the server NFS logs. I
can try harder, I can try to add verbose and check that the logs are
actually being produced, if this does not seem to lead us to the problem
source:
With "journalctl -f" only, I can get the following messages. A lot of
them see
With journalctl -f | grep DEN these messages appear to the console after
waiting the 12ms timeout:
loka 24 20:56:42 koira audit[12568]: AVC apparmor="DENIED"
operation="file_mmap" profile="/snap/snapd/4992/usr/lib/snapd/snap-confine"
name="/usr/lib/x86_64-linux-gnu/libgtk3-nocsd.so.0" pid=12
>> Should we continue solving the timeout problem in this issue?
> Yes, let's do that. What do you mean by a 12ms timeout, does the
chromium window take 2 whole minutes to appear when you launch it?
Yes it does wait for 2 minutes before showing a window. It's a pain and
makes the chromium pra
Should we continue solving the timeout problem in this issue? It was
actually in the header from the beginning and password manager nuance
can be removed from the description.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-brows
Or to be exact, a 12ms timeout.
Anyway I suspect the chromium and password manager connection might have
failed due to headless custom made auto-update script that is run from
cron.daily. You can see it working in my term.log on lines 20685-20713.
It seems to be unable to find the snapd runnin
Oh, wait! Chromium remembers my passwords now. The pain is now a slow
start of 12000 ms timeout! Thank you for solving my problem.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs
I also tried rebooting. And after all that the connection between chromium and
password-maager seems to be existing:
XXX@koira:~$ snap connections chromium | grep password
password-manager-service chromium:password-manager-service
:password-manager-service manual
--
You received this bu
Yes, indeed the stored passwords inside chromiums sqlite file are
encrypted. I didn't try to decrypt those, I didn't know where the key
was. After seeking there are keys in the seahorse-application (it has a
title "keyring") for chromium (and also chrome separately). Another key
looks like a dummy
** Description changed:
I have my /home folder shared via NFS from a local server one floor
below in my house. The server runs Ubuntu 18.04.
After starting a snapped version of chromium-browser in my Ubuntu 19.10
the document portal timeouts like this:
XXX@koira:~$ chromium-browser
And to be precise with my wordings, I'm not actually using a separate
password manager. I'm storing the passwords to Chromium. And the
passwords are on a sqlite db that is stored under my NFS shared /home.
--
You received this bug notification because you are a member of Desktop
Packages, which i
Thank you for removing the workaround. I was just coming back to remove
it myself when it didn't seem to be a stable solution for some reason.
Here is your answer to a command:
XXX@koira:~$ snap connections chromium | grep password
password-manager-service chromium:password-manager-service -
term.log as requested
** Attachment added: "term.log"
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1848753/+attachment/5298278/+files/term.log
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ub
history.log as requested
** Attachment added: "history.log"
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1848753/+attachment/5298277/+files/history.log
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-brows
** Description changed:
- I have my /home folder shared via NFS from a local server. The server
- runs Ubuntu 18.04.
+ I have my /home folder shared via NFS from a local server one floor
+ below in my house. The server runs Ubuntu 18.04.
After starting a snapped version of chromium-browser in
** Description changed:
- I have my /home folder shared via NFS from a local server one floor
- below in my house. The server runs Ubuntu 18.04.
+ I have my /home folder shared via NFS from a local server. The server
+ runs Ubuntu 18.04.
After starting a snapped version of chromium-browser in
16 matches
Mail list logo
