Description of problem: For the second time my Mageia 8 system (Dell touchscreen, Intel(R) Core(TM) i3-8100 CPU @ 3.60GHz 8GB momory, 00:00.0 Host bridge: Intel Corporation 8th Gen Core 4-core Desktop Processor Host Bridge/DRAM Registers [Coffee Lake S] (rev 08) 00:02.0 VGA compatible controller: Intel Corporation CoffeeLake-S GT2 [UHD Graphics 630] 00:14.2 RAM memory: Intel Corporation Cannon Lake PCH Shared SRAM (rev 10) 00:1f.3 Audio device: Intel Corporation Cannon Lake PCH cAVS (rev 10) >uname -a Linux tunnel.physics.ubc.ca 5.15.25-desktop-1.mga8 #1 SMP Wed Feb 23 19:39:18 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux While watching a Due South episode from cbc.ca on Google chrome Version 99.0.4844.51 (Official Build) (64-bit) The system went into an infinite loop of the video with about a 2 sec loop time. Ie, video and sound kept repeating for at least 2 min, at which point I did a hard resset (Ie, pushed the power switch on the computer-- nothing else worked.) This is at least the scond time ( in about 4 months) this has happened. No idea what is causing it.
Oh yes, running updated: Mageia 8 and XFCE X.
Is there a reason why you are using a heavily outdated Google Chrome with countless open vulnerabilities?
You could help test the update now building: Bug 30259
CC: (none) => fri
Summary: Movie loops -- both video and sound-- forever. => Movie loops forever - Google Chrome 99.0.4844.51Source RPM: ?? => (none)
And please be aware that: Google Chrome is not in our repos! Chromium is in our repos! Which are you using?
You: Google chrome Version 99.0.4844.51 Mageia: chromium-browser in: chromium-browser-stable-100.0.4896.60-1.mga8.src.rpm chromium-browser-stable in: chromium-browser-stable-100.0.4896.60-1.mga8.src.rpm Yes indeed w unruh [can you give us a real name to talk to you?] You cannot expect resolution of problems for 3rd party applications. Especially when they are in lieu of our own packaging of the equivalent thing. And especially when you seem to be using an out-of-date upstream version. Please install instead our latest supported version (above), which is more recent that what you cite; and report back. Better still, try the pending update chromium-browser-stable-100.0.4896.75-1.mga8 from core/updates_testing a noted in comment 3. It would be legitimate to raise a complaint against our packaged application if you know that the same upstream version does not exhibit the same problem.
CC: (none) => lewyssmith
A) Actually I am not at all sure what the version is. I updated Chrome, and the google Chrome Help still listed it as 99.04844.51, even though I installed 100.0.4896.75-1 and it is listed like that in my list of rpms. Since that was where I got the number from that I reported, I am no longer sure what version it was I had installed. Yes, I do understand that you cannot support Chrome, especially as you do not have the source for it. However, the reason I reported it to Mageia was because it struck me as not a Chrome problem. The whole machine froze, nothing worked except this video and sound looping forever. Ie, it seemed to me to far more likely to be a video/audio driver problem than a Chrome problem. But as you can imagine it was impossible to figure out exactly where the problem was, since the problem is really sporadic (as I said twice in aout 4 months), but also felt is was something which Mageia should be aware of, and others should be aware of in case they stumble into the same problem-- they are not alone. Whether or not I should use chromium or chrome is still up in the air, because the transition (eg password safe, etc) was problematic when I did try to use Chromium. .0.4896.75-1 But I suspect that there are loads of users who use Chrome, rather than Chromium. and something which causes a complete meltdown of the machine is something that you Mageia folks should at least be aware of, even if you cannot fix it. As far as trying the new Chromium, as I said, the rpoblem is so rare, that by the time it happens again, you are liable to be at Chromium 102 or 105, in which case 100.0 will be irrelevant. So, no I do not expect you to fix it. I do hope that this report is there so if someone else runs into the problem, whether on Chrome or Chromium, they can point to this event to show it is not unknown. One problem with the bugs report is that if the problem is closed, noone ever sees it when searching, which is a shame.
Oh, and my first name is Bill.
It is no general Google Chrome problem. On all of my machines (including VM’s) Google Chrome is running (from old to newest hardware). There was never a problem like you described. BTW: You can also find closed bugs. Click at the question mark next to the search box ans you will find a help/wiki for a howto.
Bill (at last!) Re your comment 6, point taken. You say only a hard reset was effective, which implies that killing the desktop (Ctl/Alt/Bksp/Bksp) did nothing, and that you could not get to a virtual console (Ctl/Alt/F2-7). A last resort to try after such an event is, after the reboot, do: $ journalctl -b-1 --no-hostname > anyfile.txt and either edit that file to leave the last bit showing the looping; and/or compress the whole journal or the edited part: $ xz anyfile.txt and attach anyfile.txt.xz to the bug. > One problem with the bugs report is that if the problem is closed, > noone ever sees it when searching, which is a shame The hint given in the previous comment is good, but the simplest way to include closed bugs is to put ALL at the start of the search term(s).
For searching there is also the advanced search - the link left of search field here above. (In reply to w unruh from comment #6) > A) Actually I am not at all sure what the version is. I updated Chrome, and > the google Chrome Help still listed it as 99.04844.51, even though I > installed 100.0.4896.75-1 and it is listed like that in my list of rpms. Then there is the problem. On my system with chromium from testing repo is in the about window chrome://settings/help telling the correct Version: 100.0.4896.75 Do you perhaps have another chromium installed (too)? Bill, please in a terminal execute same commands as I do here to see what is different: § chromium-browser --version Chromium 100.0.4896.75 Mageia.Org 8 $ rpm -qa | grep chromium chromium-browser-stable-100.0.4896.75-1.mga8 chromium-browser-100.0.4896.75-1.mga8
[unruh]>chrome --version Google Chrome 100.0.4896.75 And yet the :->Help->About Googlr Chrome says Version 99.0.4844.84 (Official Build) (64-bit) This is clearly a bog in Chrome (Note not chromium, Chrome-- and no I do not expect Mageiea to do anything since they have no pull with Google-- noone does. It was purely to say that I have no idea if the version of Chrome I was using was the 99 version since I got the information from that Help menu which apparently can be wrong on Chrome--NOT chromium-browser. Again IF the problem is with the browser, there is nothing Mageia can do. I reported it because I suspect the problem is elsewhere, but I have no idea where. The suggestions to look at journal is good. However I looked now and there is nothing but an abrupt stop to the journal There is a report from Shorewall about attempts on port 22 and the last entry is Apr 06 00:00:00 systemd[1]: Started Update a database for mlocate. There are reports from dnf and Thunar 3.5 hrs earlier (strange since I do not use dnf-- I use urpmi -- but dnf is installed) That the journal ends so abruptly suggests to me again that the problem is not in chrome but somewhere much deeper in the kernal, like the video driver, but again no evidence for that, and the crashes are rare enough (months) that I am not going to be able to track it down.
You have apparently some other google chrome install, that is launched by "chrome". If you launch that "chrome" from console, does it not say version 100.. in the about page?? Try exactly "chromium-browser" which is the name for the application in Mageia package :) Try launching that from console.
Nope. The Desktop icon launches /opt/google/chrome/google-chrome and ir gives me the 99 version number in the Help, and the 100 in the --version. It is a bug in Chrome. I do not use chromium, I use Chrome-- the one that Google supplies from http://dl.google.com/linux/chrome/rpm/stable/x86_64 It is that which seems to have the bug in reporting its version.
This is no bug in Google Chrome! As many websites aren‘t working with 3 digit browser versions, Google tweaked the serial number showed to the websites. This will go on some time until the majority of websites fixed their programming. This information was widely spread in all Major IT publications….
Great, closing then. Bill is using not the new Mageia package. And the old directly from upstream or as packaged is "working as designed" Web compatibility have never been and will never be stable...
Resolution: (none) => INVALIDStatus: NEW => RESOLVED
[rolf@x570i ~]$ google-chrome --version Google Chrome 100.0.4896.88 [rolf@x570i ~]$ rpm -q google-chrome-stable google-chrome-stable-100.0.4896.88-1 [rolf@x570i ~]$ From Chrome Help menu: About Chrome Google Chrome Version 100.0.4896.88 (Official Build) (64-bit) ~installed by following wiki instructions, referred from forum: https://wiki.mageia.org/en/Installing_Google_Chrome_in_Mageia Rolf
CC: (none) => rolfpedersen
(In reply to w unruh from comment #6) > However, the reason I reported it to Mageia was because it struck me as not > a Chrome problem. The whole machine froze, nothing worked except this video > and sound looping forever. Ie, it seemed to me to far more likely to be a This most likely mean a driver hang, crash or reset happends... > video/audio driver problem than a Chrome problem. But as you can imagine it > was impossible to figure out exactly where the problem was, since the > problem is really sporadic (as I said twice in aout 4 months), but also felt > is was something which Mageia should be aware of, and others should be aware > of in case they stumble into the same problem-- they are not alone. ... so when it "hangs", if you have another machine nearby, try to ssh from that into the computer and try to grab dmesg output ... Otherwise, if it's really stuck and you have to hard reset it to get it back in working order, try to check the logs if anything got written to them before it locked up...