Occurrences if chromium in the dpkg.log:

root@flupp:/var/log# grep chromium dpkg.log
2019-10-24 16:15:45 upgrade chromium-browser-l10n:all 
76.0.3809.100-0ubuntu0.19.04.1 77.0.3865.120-0ubuntu1~snap1
2019-10-24 16:15:45 status half-configured chromium-browser-l10n:all 
76.0.3809.100-0ubuntu0.19.04.1
2019-10-24 16:15:45 status unpacked chromium-browser-l10n:all 
76.0.3809.100-0ubuntu0.19.04.1
2019-10-24 16:15:45 status half-installed chromium-browser-l10n:all 
76.0.3809.100-0ubuntu0.19.04.1
2019-10-24 16:15:45 status unpacked chromium-browser-l10n:all 
77.0.3865.120-0ubuntu1~snap1
2019-10-24 16:15:45 upgrade chromium-browser:amd64 
76.0.3809.100-0ubuntu0.19.04.1 77.0.3865.120-0ubuntu1~snap1
2019-10-24 16:15:45 status half-configured chromium-browser:amd64 
76.0.3809.100-0ubuntu0.19.04.1
2019-10-24 16:15:45 status unpacked chromium-browser:amd64 
76.0.3809.100-0ubuntu0.19.04.1
2019-10-24 16:15:46 status half-installed chromium-browser:amd64 
76.0.3809.100-0ubuntu0.19.04.1
2019-10-24 16:17:26 status unpacked chromium-browser:amd64 
77.0.3865.120-0ubuntu1~snap1
2019-10-24 16:18:43 upgrade chromium-codecs-ffmpeg-extra:amd64 
76.0.3809.100-0ubuntu0.19.04.1 77.0.3865.120-0ubuntu1~snap1
2019-10-24 16:18:43 status half-configured chromium-codecs-ffmpeg-extra:amd64 
76.0.3809.100-0ubuntu0.19.04.1
2019-10-24 16:18:43 status unpacked chromium-codecs-ffmpeg-extra:amd64 
76.0.3809.100-0ubuntu0.19.04.1
2019-10-24 16:18:43 status half-installed chromium-codecs-ffmpeg-extra:amd64 
76.0.3809.100-0ubuntu0.19.04.1
2019-10-24 16:18:43 status unpacked chromium-codecs-ffmpeg-extra:amd64 
77.0.3865.120-0ubuntu1~snap1
2019-10-24 16:22:23 configure chromium-codecs-ffmpeg-extra:amd64 
77.0.3865.120-0ubuntu1~snap1 <none>
2019-10-24 16:22:23 status unpacked chromium-codecs-ffmpeg-extra:amd64 
77.0.3865.120-0ubuntu1~snap1
2019-10-24 16:22:23 status half-configured chromium-codecs-ffmpeg-extra:amd64 
77.0.3865.120-0ubuntu1~snap1
2019-10-24 16:22:23 status installed chromium-codecs-ffmpeg-extra:amd64 
77.0.3865.120-0ubuntu1~snap1
2019-10-24 16:44:26 configure chromium-browser:amd64 
77.0.3865.120-0ubuntu1~snap1 <none>
2019-10-24 16:44:26 status unpacked chromium-browser:amd64 
77.0.3865.120-0ubuntu1~snap1
2019-10-24 16:44:26 status half-configured chromium-browser:amd64 
77.0.3865.120-0ubuntu1~snap1
2019-10-24 16:44:26 status installed chromium-browser:amd64 
77.0.3865.120-0ubuntu1~snap1
2019-10-24 16:44:26 configure chromium-browser-l10n:all 
77.0.3865.120-0ubuntu1~snap1 <none>
2019-10-24 16:44:26 status unpacked chromium-browser-l10n:all 
77.0.3865.120-0ubuntu1~snap1
2019-10-24 16:44:26 status half-configured chromium-browser-l10n:all 
77.0.3865.120-0ubuntu1~snap1
2019-10-24 16:44:26 status installed chromium-browser-l10n:all 
77.0.3865.120-0ubuntu1~snap1
2019-10-24 16:47:12 status installed chromium-browser-l10n:all 
77.0.3865.120-0ubuntu1~snap1
2019-10-24 16:47:13 remove chromium-browser-l10n:all 
77.0.3865.120-0ubuntu1~snap1 <none>
2019-10-24 16:47:13 status half-configured chromium-browser-l10n:all 
77.0.3865.120-0ubuntu1~snap1
2019-10-24 16:47:13 status half-installed chromium-browser-l10n:all 
77.0.3865.120-0ubuntu1~snap1
2019-10-24 16:47:13 status config-files chromium-browser-l10n:all 
77.0.3865.120-0ubuntu1~snap1
2019-10-24 16:47:13 status not-installed chromium-browser-l10n:all <none>

After starting the PC and logging into KDE without starting chromium:
gert@flupp:~$ snap connections chromium | grep password
password-manager-service  chromium:password-manager-service  
:password-manager-service       manual

I remember that after the upgrade when the configs have not been
transfered, that last "manual" was not printed. I think it was a "-"
instead. After starting up the connection manually as mentioned in the
bug 1849160 the "manual" was printed.

After removing the ~/snap/chromium/current/.config/ directory and
starting chromium the following was printed to konsole. (And the
settings were not transfered.)

gert@flupp:~$ which chromium
/snap/bin/chromium
gert@flupp:~$ chromium
[4498:4498:1026/104128.629497:ERROR:sandbox_linux.cc(369)] InitializeSandbox() 
called with multiple threads in process gpu-process.
[4498:4498:1026/104128.968059:ERROR:buffer_manager.cc(488)] 
[.DisplayCompositor]GL ERROR :GL_INVALID_OPERATION : glBufferData: <- error 
from previous GL command
[4560:1:1026/104130.143320:ERROR:child_process_sandbox_support_impl_linux.cc(81)]
 FontService unique font name matching request did not receive a response.
[4560:1:1026/104130.143846:ERROR:child_process_sandbox_support_impl_linux.cc(81)]
 FontService unique font name matching request did not receive a response.
[4573:1:1026/104132.869494:ERROR:child_process_sandbox_support_impl_linux.cc(81)]
 FontService unique font name matching request did not receive a response.
[4573:1:1026/104132.869978:ERROR:child_process_sandbox_support_impl_linux.cc(81)]
 FontService unique font name matching request did not receive a response.

If I can test and report something else, please let me know.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849693

Title:
  [snap] Upgrading from kubuntu 19.04 to 19.10 lost all chromium
  settings

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1849693/+subscriptions

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to