@9d9, please post these logs on the other thread.
This is a regression indeed. Iâve filed bug #1837746 to track it.
This is bug #1836616, which I just fixed. Until the fix reaches you, you can work around the problem by manually connecting the password-manager-service interface:
snap connect chromium:password-manager-service
This is probably caused by the lack of the --force-device-scale-factor=2 parameter. Does it go away if you run:
chromium --force-device-scale-factor=2
Nope, still small and cursor theme is different.
1 Like
This fixed the problem, thanks.
- I had client certificate installed to access site wth certificate authentication. After switching to snap certificate isnât installed anymore.
What cursor theme do you use on your system? Can you please share a screenshot of what it looks like in the chromium snap, and the expected one?
And what cursor theme is that?
The cursor from 90s, I believe. It reminds of when I had to install Linux (Redhat in my case, pre-fedora days), and after it had booted I had to type in startx to start the x server which loaded the GUI, in my case was GNOME 1.x
I can observe the issue too. I filed bug #1838008 to track it. Thanks for spotting and reporting it!
1 Like
I have always used basic password store instead of keyring in the desktop file. But this doesnât work with snap. Can anyone tell me how can I keep doing that ?
Are you saying the basic password is not working or the keyring in the desktop file is not working? Have you given the appriate app permission?
- When clicking web link from sylpheed mail client chromium often crashes. I havenât found reliable way to reproduce it without sylpeed, but running
echo -n | chromium-browser --new-window 'https://www.google.com/'about 10 times causes crash too.
Make sure the password-manager-service interface is disconnected:
snap disconnect chromium:password-manager-service
This will force chromium to use the basic password store.
I can reproduce the crash. I have filed bug #1838508 to track it, and I am investigating it.
I was away from my PC for about 90 minutes. I left Chromium and a few applications running each on their own work spaces. When I returned I used Chromium briefly, switched to another work space and when I tried to switch back to Chromium using the dock icon I noticed that the indicator which would confirm that Chromium was running was missing. At first I thought Chromium had crashed but I looked through the work spaces and found Chromium just as I had left it.
snap changes and snap info chromium confirmed there had been an auto-refresh from version 75 to version 76 while I had been away.
Clicking on the dock icon opened a new blank Chromium window (v.75). I then closed Chromium (v.75) completely and restarted it (v.76) from the dock icon. I saw the standard warning that Chromium did not close down correctly. My previous session was partly restored but Iâm not sure up to what point.
I donât think Iâm reporting anything new and I am probably just confirming that known problems still exist. But I thought that I would post my findings as I was confused for a while and those less familiar with the Chromium snap might have been even more confused.
2 Likes
This is a known problem with snaps, and is slated to be fixed soon. See https://forum.snapcraft.io/t/wip-refresh-app-awareness/10736 for full details.
2 Likes
When going to Details | Default Applications | Web in the Settings Application I expect to see a single entry for each web browser that I have installed but âChromium Web Browserâ appears twice.
Selecting either entry appears to correctly set Chromium as the default browser although when I first started to look at this I saw a notification that Chromium had not previously closed correctly when I next tried to use it. I havenât seen that notification since.
Does anyone else see two entries for Chromium?
I found the cause of the crash (itâs a recent regression) and pushed a fix for it, the next builds will have it.
I do. Thanks for the report @paulw2u, I filed bug #1838628 to track it.