Chromium won't start #3
Comments
Same bug here. |
oh.. this is weird :) Thanks, we'll check that out. |
I've got LMDE3 installed in VB as well. So far, all software installed has ran just fine except for Chromium. Same issue user "wooque" is having. |
+1 Fresh LMDE3 Beta x64 installation, package chromium from software manager, When i launch chromium i get:
Also, in package manager chromium on it's page come with picture from chromium-bsu page (package with arcade game). Not a big bug, but very funny. |
In short: this is because the Debian Stretch (old) Muffin version has a button-layout key in its gsettings schema org.cinnamon.muffin that the LMDE 3 (current) Muffin version doesn't have and Chromium on Debian Stretch is hardcoded to use that older Muffin schema. I compared output of On LMDE 2 it shows:
On LMDE 3 and Linux Mint 19 it shows the same except the first line is missing. Chromium on Linux Mint 19 doesn't have an issue with this but Chromium on LMDE 3 indeed does. Checking the Chromium sources on Debian Stretch it shows this is hardcoded specifically for Cinnamon in the file const char kCinnamonPreferencesSchema[] = "org.cinnamon.muffin";
[...]
const char kButtonLayoutKey[] = "button-layout"; The key can't be added manually with gsettings as there exists no schema that has it on LMDE 3. I doubt Chromium hardcoding will be fixed in Debian Stretch. A possible solution for LMDE 3 would be to add the schema back to the Muffin package for LMDE 3 and patch the Cinnamon Settings > Windows code so that the button layout in /org/cinnamon/desktop/wm/preferences/button-layout is always also set on /org/cinnamon/muffin/button-layout? |
Thanks. |
Update: Chrome is working correctly. |
Debian won't fix it because it doesn't affect them. We've established that with NM already. |
The simplest solution might be to add that key somewhere in debian-system-adjustments. |
sorry, closed by mistake :) |
Fixed in muffin 3.8.3. |
Error message in terminal
Installed in Virtualbox virtual machine
The text was updated successfully, but these errors were encountered: