Bug 21228

Summary:	Is Mageia6 infected by addware?
Product:	Mageia	Reporter:	Bjarne Thomsen <bjarne.thomsen>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED INVALID	QA Contact:
Severity:	normal
Priority:	Normal	CC:	marja11
Version:	6
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:	chromium-browser-stable-57.0.2987.133-6	CVE:
Status comment:

Description Bjarne Thomsen 2017-07-12 10:24:41 CEST

Description of problem:
It has happened twice that chromium started from a casino site
or a site that could earn me millions within a few months.

Version-Release number of selected component (if applicable):

chromium-browser-stable-57.0.2987.133-6
How reproducible:
It is not. It has never happened before, but it has now
happened twice within the last two days.
I intend to install from scratch when 6 is officially out.
I assume that this is not a new way to earn money for Mageia.

Steps to Reproduce:
1.
2.
3.

Comment 1 Rémi Verschelde 2017-07-12 10:46:31 CEST

Well Mageia itself doesn't ship adware in Chromium obviously :)

But like on any OS, you might have installed some addon or let some website modify your Chromium profile to change the Home page, or the default search engine, etc. Deleting your Chromium profile in your $HOME might help fix that (albeit with a sledgehammer, there might be simpler ways to get back to a working profile than just deleting it all ;)).

Comment 2 Bjarne Thomsen 2017-07-12 13:03:51 CEST

Well, I had been using chromium for a long time without installing
any add-blocker extensions. It was news to me that a cookie can
change the start page at random, but after the first pop-up
I installed several blocker extensions. I have been running these
extensions in Mageia5 for a long time.
It happened again this morning, and all extensions had led 4 cookies pass.
I blocked these and the page dissabeared. It does not simply change
the start page permanently. It happened at random.

Comment 3 Marja Van Waes 2017-07-12 23:42:55 CEST


If anyone can reproduce this issue with a fresh chromium profile or with a new user on then starting Chromium for the first time, then please reopen this report.

Status: NEW => RESOLVED
CC: (none) => marja11
Resolution: (none) => INVALID