** Changed in: snapd
Status: New => Triaged
** Changed in: snapd
Importance: Undecided => Medium
** Changed in: snapd (Ubuntu)
Status: New => Triaged
** Changed in: snapd (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member
Ah, forgive me.
I think this bug requires someone to sit down and attempt to reproduce
it in a controlled environment. I cannot commit to do that anytime soon
as we have a number of open bugs, features we promised to deliver and a
handful of people working on the project.
I'd like to keep the bug
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1
It seems that loka 29 20:02:33 koira xdg-document-portal[16225]: error: Failed
to load db: invalid gvdb header
is relevant. I wonder if the database, whatever the format, is somehow corrupt.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
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
Hello there.
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=12568
comm="snap-confine" requested_mask="m" denied_mask="m" fsuid=0 ouid=0
I'm very curious
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
Ack, that's pretty bad. As requested by Paweł in comment #13, could you
check whether you get apparmor denials when starting chromium? You can
run the following command in a terminal, then launch chromium:
journalctl -f | grep DEN
Please attach the output after the chromium window has appeare
>> 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
> 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
No, the connection to the password-manager-service interface wasn't even
attempted, but that's a separate bug, which is being fixed (bug
#1849160)
Do you have any apparmor denials in the system log when you observe this
slowdown? (run journalctl, look for 'apparmor=DENIED'?
(for what it is worth chromium snap starts just fine for me on fresh
18.04 and 19.10 systems, but I reckon NFS may be a key here, and I don't
have it).
--
You received
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
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
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
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848753
Title:
[snap]
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
Right, chromium now always stores its saved passwords in a sqlite database in
the profile directory, but if available it uses the system's keyring to store
the key used to encrypt the contents of that database.
Please run the following command:
sudo snap connect chromium:password-manager-ser
** 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
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
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 Ubuntu
Bugs, which is sub
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
I'm also marking snapd affected, since the timeout when activating
org.freedesktop.portal.Documents doesn't seem chromium-specific.
** Also affects: snapd (Ubuntu)
Importance: Undecided
Status: New
** Also affects: snapd
Importance: Undecided
Status: New
** Changed in: chromi
23 matches
Mail list logo
