Bug 10326 - kde classick launcher/start menu background not configurable
Summary: kde classick launcher/start menu background not configurable
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 3
Hardware: All Linux
Priority: Normal enhancement
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords: Triaged
Depends on:
Blocks:
 
Reported: 2013-05-28 12:15 CEST by peter winterflood
Modified: 2015-03-31 16:06 CEST (History)
5 users (show)

See Also:
Source RPM: kde-style-mageia ?
CVE:
Status comment:


Attachments

Description peter winterflood 2013-05-28 12:15:13 CEST
in mageia 2 the classic start menu background could be changed in line with the theme to a pleasing theme using Iora.

Now with the dropping of Iora anyone wanting to use a different theme from kde.org, still gets stuck with the same background in the classic launcher/start menu, ie oxygen.

I personaly dont like the oxygen theme because it looks to macosx like.

on choosing some windows 7 themes from kde.org i find ive still got the oxygen theme on the start menu.

I want to stick with using the minimalist start menu, and not the fuller default kde one.
but also want to change the theme of this menu to be more in line with the theme ive chosen for the task bar and window surrounds.

so the enhancment request is to me able to change this.

I dont mind if its a dot file i need to edit.

and please be aware this applies to the classic taskbar, and start bar, not then plasmoid taskbar/start menu.


Reproducible: 

Steps to Reproduce:
Manuel Hiebel 2013-05-28 14:24:44 CEST

Keywords: (none) => Triaged
CC: (none) => balcaen.john, lmenut, nicolas.lecureuil
Source RPM: kde-style-mageia => kde-style-mageia ?

Florian Hubold 2013-05-30 21:36:06 CEST

CC: (none) => doktor5000

Comment 1 Otto Leipälä 2014-08-31 12:52:43 CEST
Bug affects to kickoff too,icons are provided in icon themes in kickoff and classic menu but mageia kde4 configs forcing it to oxygen and you cannot change them what just sucks.:(

CC: (none) => ozkyster

Comment 2 Florian Hubold 2014-08-31 14:29:18 CEST
You should report that upstream at https://bugs.kde.org or ask about it in https://forum.kde.org .

FWIW, you should test again with vanilla-kde4-config if you think that this is because of the Mageia KDE configs.
Comment 3 Otto Leipälä 2014-08-31 14:36:33 CEST
I tested kubuntu 13.10 have kde 4.11 and it changed every kickoff and classic menu icons so this bug is not upstream.
Comment 4 Otto Leipälä 2014-08-31 14:43:05 CEST
I tested that vanilla config but same issue still.
Comment 5 Otto Leipälä 2014-08-31 16:05:04 CEST
I asked it from kde forum.
https://forum.kde.org/viewtopic.php?f=67&t=122653
Comment 6 Luc Menut 2014-08-31 23:32:31 CEST
(In reply to Otto Leipälä from comment #1)
> Bug affects to kickoff too,icons are provided in icon themes in kickoff and
> classic menu but mageia kde4 configs forcing it to oxygen and you cannot
> change them what just sucks.:(

We use Oxygen as icons theme by default, but we don't force its use.
I've just tried on mga4 to switch to Tango Icon Theme (tango-icon-theme-0.8.90-10.mga4) in systemsettings, and both kickoff and classic menus use Tango icons.
I guess that the icon theme that you try to use doesn't have some icons that Mageia uses for menus .directory.
You can check the icons used in our menus by
grep "^Icon" /usr/share/desktop-directories/*.directory
Comment 7 Florian Hubold 2014-09-01 00:34:52 CEST
(In reply to Otto Leipälä from comment #1)
> Bug affects to kickoff too,icons are provided in icon themes in kickoff and
> classic menu but mageia kde4 configs forcing it to oxygen and you cannot
> change them what just sucks.:(

For your icon issue, please open a separate bug report. The initial report is about theming (background) of classic kicker menu, not about icons.
Comment 8 Marja Van Waes 2015-03-31 16:06:47 CEST
Mageia 3 changed to end-of-life (EOL) status 4 months ago.
http://blog.mageia.org/en/2014/11/26/lets-say-goodbye-to-mageia-3/ 

Mageia 3 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of Mageia
please feel free to click on "Version" change it against that version of Mageia
and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--
The Mageia Bugsquad

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


Note You need to log in before you can comment on or make changes to this bug.