Am Donnerstag, dem 27.01.2022 um 18:55 -0500 schrieb Andres Salomon:
> you can also run "chromium --ozone-platform=wayland" to get native
> wayland.
Thanks for the tip, I never tried that. I do the chrome://flags way
because it's persistent and doesn't require running chromium from the
On 1/27/22 18:50, Amr Ibrahim wrote:
Hello,
I just want to give a small guide into how to enable Wayland again for
people like me who prefer Wayland and it works well for them:
1. Start chromium
2. Type chrome://flags in the address bar
3. Search for ozone
4. Change "Preferred Ozone platform"
Hello,
I just want to give a small guide into how to enable Wayland again for
people like me who prefer Wayland and it works well for them:
1. Start chromium
2. Type chrome://flags in the address bar
3. Search for ozone
4. Change "Preferred Ozone platform" into "Auto"
5. Restart chromium
Best,
On 1/21/22 03:21, Martin Dosch wrote:
Hi,
there you go.
Best regards,
Martin
Thanks!
Wow, okay, this is not what I expected. The upstream version has
hardware acceleration disabled for your graphics hardware. Yet it's only
disabled if running in wayland native mode; it's enabled for X11
On 1/21/22 03:04, Martin Dosch wrote:
Hi,
On 20.01.2022 19:51, Andres Salomon wrote:
I uploaded 99.0.4818.0-0.1 to experimental. It would be really
helpful if you could also test with that version, so I can figure out
if the wayland graphics problem is introduced by debian's various
patches
On 1/17/22 05:20, Martin Dosch wrote:
Hi,
On 17.01.2022 03:00, Andres Salomon wrote:
I would encourage both of you to also grab a stock chromium binary
from upstream (via snap or whatever mechanism you prefer), and file
bug reports upstream if --ozone-platform=wayland still fails to run
on
Dear Maintainer,
we're also experiencing issues with the latest chromium update. We run
chromium in kiosk mode without a full desktop environment. After
updating to 97.0.4692.71-0.1~deb11u1, chromium fails to start. We were
able to resolve this initial problem by installing libgtk-3-0
On 1/17/22 03:00, Andres Salomon wrote:
On Sat, 15 Jan 2022 14:58:20 +0100 Adrien Ponchelet wrote:
> Dear Andres,
>
> I have the same problem as Martin.
>
> The "--use-gl=desktop" option doesn't work for me to. Open is ok, but
> window is figed. I cannot do anything.
> When I commenting the line
On Sat, 15 Jan 2022 14:58:20 +0100 Adrien Ponchelet wrote:
> Dear Andres,
>
> I have the same problem as Martin.
>
> The "--use-gl=desktop" option doesn't work for me to. Open is ok, but
> window is figed. I cannot do anything.
> When I commenting the line 61 to 63 (/usr/bin/chromium) which refer
Dear Andres,
I have the same problem as Martin.
The "--use-gl=desktop" option doesn't work for me to. Open is ok, but
window is figed. I cannot do anything.
When I commenting the line 61 to 63 (/usr/bin/chromium) which refer to
Wayland, it works fine.
The "--ozone-platform-hint=auto" option
On 1/14/22 03:10, Martin Dosch wrote:
Dear Andres,
[...]
Also, I'm guessing you're running this under Wayland. If
--use-gl=desktop doesn't help, can you try deleting lines 61 through
63 in /usr/bin/chromium? These are the lines to delete:
That's it! Thank you, this fixed it. Chromium starts
On Thu, 13 Jan 2022 19:24:30 +0100 Martin Dosch wrote:
> Package: chromium
> Version: 97.0.4692.71-0.1
> Severity: normal
> X-Debbugs-Cc: mar...@mdosch.de
>
> Dear Maintainer,
>
> chromium is no more starting on my system. If I try to start it in a
terminal I
> get the following output:
>
>
12 matches
Mail list logo
