Bug 23707

Summary:	Pre-configure KDE please. Everything from icons size to wallpaper-pack should be fixed.
Product:	Mageia	Reporter:	Roman Fomin <sodix89>
Component:	RPM Packages	Assignee:	KDE maintainers <kde>
Status:	RESOLVED OLD	QA Contact:
Severity:	enhancement
Priority:	Normal	CC:	marja11, ouaurelien
Version:	Cauldron
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:		CVE:
Status comment:

Description Roman Fomin 2018-10-16 02:47:49 CEST

Description of problem:
Current mageia KDE5 is a pain in the ass because of it non-configured properly, and user should do configuration for himself. Giant icons by default, only one wallpaper, crappy fonts, disgusting theme(srsly base developers are from France, and can't find a worthy designer?!), size of launch bar etc. All little things should be polished like in top10 KDE distros. If you have no resources, just port configuration from OpenSuSe or Debian. Make user experience with Mageia KDE great again.

Roman Fomin 2018-10-16 02:49:04 CEST

Summary: Pre-configure KDE please. Everithing from icon sizes to wallpaper-pack => Pre-configure KDE please. Everything from icon sizes to wallpaper-pack should be fixed.

Roman Fomin 2018-10-16 02:49:21 CEST

Summary: Pre-configure KDE please. Everything from icon sizes to wallpaper-pack should be fixed. => Pre-configure KDE please. Everything from icons size to wallpaper-pack should be fixed.

Comment 1 Marja Van Waes 2018-10-16 20:13:07 CEST

Giant icons? I never noticed that, but do remember having had an issue with the tiny and skinny font on some machines.

Note that Mageia is a community distribution, which means that we, the users, make Mageia ourselves. 

AFAIK our Plasma5 configuration comes from http://gitweb.mageia.org/software/desktop/plasma5/config/

Please attach your suggested git patches to this bug report!

Assignee: bugsquad => kde
CC: (none) => marja11

Comment 2 Marja Van Waes 2018-10-29 08:11:39 CET

*** Bug 23768 has been marked as a duplicate of this bug. ***

Comment 3 Aurelien Oudelet 2021-05-17 01:39:12 CEST

Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information.

Closing as OLD.

Resolution: (none) => OLD
CC: (none) => ouaurelien
Status: NEW => RESOLVED