Hardware acceleration Fedora/Cinnamon DE unusable w/ Brave 152.130

A recent Fedora/Cinnamon DE update caused Brave Browser to become unusable. Text, graphics, and most everything essential from a browser window disappeared. Using a backup browser, I found a suggestion to turn off hardware acceleration in Brave Browser which was darned difficult with no text in the browser, but I managed. The contents of the update made before the problem surfaced:

    Upgrade  cinnamon-5.8.4-1.fc38.x86_64                 @updates
    Upgraded cinnamon-5.8.2-1.fc38.x86_64                 @@System
    Upgrade  cinnamon-calendar-server-5.8.4-1.fc38.x86_64 @updates
    Upgraded cinnamon-calendar-server-5.8.2-1.fc38.x86_64 @@System
    Upgrade  cinnamon-themes-1:2.1.5-1.fc38.noarch        @updates
    Upgraded cinnamon-themes-1:2.1.2-1.fc38.noarch        @@System
    Upgrade  lightdm-settings-1.8.2-1.fc38.noarch         @updates
    Upgraded lightdm-settings-1.8.1-1.fc38.noarch         @@System
    Upgrade  mint-themes-1:2.1.5-1.fc38.noarch            @updates
    Upgraded mint-themes-1:2.1.2-1.fc38.noarch            @@System
    Upgrade  mint-themes-gtk3-1:2.1.5-1.fc38.noarch       @updates
    Upgraded mint-themes-gtk3-1:2.1.2-1.fc38.noarch       @@System
    Upgrade  mint-themes-gtk4-1:2.1.5-1.fc38.noarch       @updates
    Upgraded mint-themes-gtk4-1:2.1.2-1.fc38.noarch       @@System
    Upgrade  mint-y-icons-1.6.7-1.fc38.noarch             @updates
    Upgraded mint-y-icons-1.6.6-1.fc38.noarch             @@System
    Upgrade  mint-y-theme-1:2.1.5-1.fc38.noarch           @updates
    Upgraded mint-y-theme-1:2.1.2-1.fc38.noarch           @@System
    Upgrade  nemo-5.8.4-1.fc38.x86_64                     @updates
    Upgraded nemo-5.8.3-1.fc38.x86_64                     @@System
    Upgrade  nemo-extensions-5.8.4-1.fc38.x86_64          @updates
    Upgraded nemo-extensions-5.8.3-1.fc38.x86_64          @@System
    Upgrade  nemo-search-helpers-5.8.4-1.fc38.x86_64      @updates
    Upgraded nemo-search-helpers-5.8.3-1.fc38.x86_64      @@System
    Upgrade  selinux-policy-38.21-1.fc38.noarch           @updates
    Upgraded selinux-policy-38.20-1.fc38.noarch           @@System
    Upgrade  selinux-policy-targeted-38.21-1.fc38.noarch  @updates
    Upgraded selinux-policy-targeted-38.20-1.fc38.noarch  @@System
    Upgrade  slick-greeter-1.8.2-1.fc38.x86_64            @updates
    Upgraded slick-greeter-1.8.1-1.fc38.x86_64            @@System
    Upgrade  slick-greeter-cinnamon-1.8.2-1.fc38.noarch   @updates
    Upgraded slick-greeter-cinnamon-1.8.1-1.fc38.noarch   @@System
    Upgrade  xfce4-settings-4.18.3-1.fc38.x86_64          @updates
    Upgraded xfce4-settings-4.18.2-2.fc38.x86_64          @@System

Since the updates favored Cinnamon DE and Mint Themes, I tried switching to other environments, Gnome and LXDE, and multiple variations of themes in each (found a new one that I like), but no change made a perceptible difference in the browser’s performance. Brave Browser was still unusable and essentially displaying search results as a blank page, possibly with result titles, but no further details. Most graphics from any search or known page, like a weather forecast, were omitted. The home page photo was not displayed. It was simply a white snow storm.

I’m not looking for solutions, simply reporting an experience so that it might help others. I would be interested in knowing why the updates made caused the problem and if I should submit a bug report, but at the moment I don’t know if I have sufficient details to make a bug report useful.

Thanks all for your continued support of this excellent browser option!


@gregbrannon Could you check NOTICE: Chromium issue may affect Linux users to see if it might relate to your issue?

I’m not at the PC on which I had the problem and may not be for a few days. I appreciate you pointing to that issue, and I’ll investigate whether the suggested solution works when I can.



Sorry that it’s been so long. Sometimes it’s hard to find time to revisit problems that have been ‘fixed.’

I followed the directions at the link Saoiray provided, turned hardware acceleration back on, and all worked fine.

I noticed that the problem at the link provided has been closed without further explanation. Does that mean the problem has been fixed, or does it continue in the Chrome base? Will the fix have to be applied again? Not critical questions to answer, just curious. It seems to me that a reason for closing the topic should be given so that users have confidence in the program’s stability.

Thanks, Saoiray, for knowing/finding and pointing me in this direction.


The NOTICE got locked the moment it was shared. A lot of the official announcements get locked so people don’t go over and do a lot of off topic comments or whatever. Ideally always want people to create new topics for each individual issue except in some rare cases where Brave sees similarities and tries to narrow down to one post to make it easier to collect data.

I believe it has, especially since I haven’t seen any recent postings about it from anyone. Fix should have come out in one of the updates.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.