Bug 18845 - KDE 5 does not allow task bar/panel manipulation without log out & login
Summary: KDE 5 does not allow task bar/panel manipulation without log out & login
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: KDE maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-07-03 06:44 CEST by Bobbie Sellers
Modified: 2017-03-30 01:16 CEST (History)
3 users (show)

See Also:
Source RPM:
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Bobbie Sellers 2016-07-03 06:44:34 CEST 
I installed Mageia-6-sta1-x86_64-DVD.iso to my Dell E6420 today.
This machine has 8 Gibibytes of ram and an Intel 4000 GPU to help
out the i7.
I observed the same sort of behavior in the Live version earlier
but since I could resolve with a log out and then log back in I decided
to go ahead with the installation.

I first attempted to create a default panel at the top of the display
screen. The screen locked up but not as badly as on the Live version.
I logged out and the new default panel appeared. I created another
panel at the left side of the display.
 Then after a log out and log in it was properly displayed.
  I then deleted the original panel at the bottom of the display.

It was difficult as well to Switch the Menu from Launcher to Menu
format.  

For other reasons than the bug mentioned above I think 
the developers should have held off on KDE's Plasma 5 until Mageia 7.
Marja Van Waes 2016-07-04 07:37:28 CEST

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

Marja Van Waes 2016-07-04 07:38:01 CEST

Component: Release (media or process) => RPM Packages

Samuel Verschelde 2016-08-25 16:23:13 CEST

Assignee: mageia => kde

Comment 1 Nicolas Lécureuil 2017-03-15 16:04:33 CET 
is it still valid on current cauldron ?

CC: (none) => mageia

Comment 2 Nicolas Lécureuil 2017-03-30 01:16:00 CEST 
duplicate

Status: NEW => RESOLVED
Resolution: (none) => FIXED
Note You need to log in before you can comment on or make changes to this bug.