Description of problem: This is just an FYI, for the record, in case it escalates to a low-level issue. What started as flickering within Firefox Nightly may be corrupting the in-memory system (reboot resolves). No objection to closing; just wanted Mageia to be aware of this situation... However, I've been having a nagging feeling lately that the flickering may be within KDE; no hard proof, just random intermittent flickering triggered by moving mouse through the task bar area... Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. use Firefox Nightly 2. watch some streaming video 3. Until the last ~48 hours, firefox would start to flicker. Moving the affected tabs to a new window and closing the affected window cleared the problem for a while. Now, both screens go dark with random flashes. See https://bugzilla.mozilla.org/show_bug.cgi?id=1746708 where I just posted latest info...
A short summary: - you are using an alpha (nightly) upstream Firefox - you are using cauldron (unstable development version) - you are heavily tinkering with system values like MAXCLIENTS (bug 30358) - you are using a RX6600XT which has many reports about screen flickering How can we reproduce this? There are many informations missing what additional system values you changed on your system. Many others here are using Plasma on cauldron and Firefox (the beta one provided by Mageia) and they have no flickering. So there is one or more key information missing (i suspect the tinkered system values and the RX6600XT) so that anybody from our devs could help you...
(In reply to sturmvogel from comment #1) > A short summary: I opened this as an FYI... but, you bring up valid points: > - you are using an alpha (nightly) upstream Firefox Been doing that for years; bug reporting helps the developers. In the same vein, I've been running Alpha LibreOffice 7.5.0 for a few weeks; mainly because I need the new Jumbo mode... it's a tradeoff between features and but reporting... > - you are using cauldron (unstable development version) Yup... :) > - you are heavily tinkering with system values like MAXCLIENTS (bug 30358) One change doesn't strike me as "heavily tinkering"... :) > - you are using a RX6600XT which has many reports about screen flickering The reason I chose that card is because the reviews I read before purchasing indicated AMD was better supported by Linux than NVIDIA... I'm open to replacing it. Any suggestions? I don't do heavy graphics or gaming. > How can we reproduce this? There are many informations missing what > additional system values you changed on your system. I went through the journal file that I posted at Mozilla; it has more info about my system in the log than I could provide from a query, other than maybe hardinfo -- I'll add it shortly... > Many others here are using Plasma on cauldron and Firefox (the beta one > provided by Mageia) and they have no flickering. Open to hearing which graphics cards people are using... tried a quick search and saw this: * Mageia 8 will be supported until August 31st, 2022. which is only 2 weeks away... Hmmm...?? > So there is one or more key information missing (i suspect the tinkered > system values and the RX6600XT) so that anybody from our devs could help > you... You already found the "heavy tinkering"... :) I'm mainly a "user". I wouldn't consider myself a sysadmin, developer (other than python scripting), etc.
Created attachment 13364 [details] hardinfo report Should be more system info than needed... Want 'rpm -qa', or other output?
(In reply to Pierre Fortin from comment #2) > tried a quick > search and saw this: > > * Mageia 8 will be supported until August 31st, 2022. > > which is only 2 weeks away... Hmmm...?? And the sentence above this: "Lifecycle Mageia releases are supported at least for 18 months. Or a minimum of 3 months after the next release, whichever is longer"
Did you already try to switch off hardware acceleration in Firefox?
Was not aware of that setting; it's well hidden in Nightly -- online help provided a clue (UI changed since the help info I found) Turned off; let's see if that helps... Thanks.
No change was noticed from that change. It may be resolved since kernel 6. Closing for now.
Resolution: (none) => WORKSFORMEStatus: NEW => RESOLVED