Bug 361779 - unable to place Plasma desktop shortcuts anywhere desired.
Summary: unable to place Plasma desktop shortcuts anywhere desired.
Status: RESOLVED UNMAINTAINED
Alias: None
Product: plasma4
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: Mageia RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-04-14 21:15 UTC by Bit Twister
Modified: 2018-06-08 18:24 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Bit Twister 2016-04-14 21:15:27 UTC
Unable to place Plasma desktop shortcuts anywhere desired.


Reproducible: Always

Steps to Reproduce:
Desktop: Plasma Layout: Folder Theme: Oxygen    Window Decorations: plastik
Desktop effects are disabled.

1. systemsettings5->Appearance Workspace Theme->Look And Feel
   select Oxygen

2. systemsettings5->Appearance->Icons  select Advanced tab, set Size: 16

3. systemsettings5->Window Behavior click Moving tab, set no border/window/center  snap zone and uncheck Snap windows only when overlapping

4. Right click blank spot on desktop, Select Folder Settings->Icons
   move Size: slider all the way to the Left

5. Right click blank spot on desktop, select Create New Link->New Link to app
   name it xterm1, repeat for xterm2, xterm3, xterm4

6. now arrange them in two rows, xterm 1 and 2, second row with xterm 3 and 4
   as close as possible to each other.



Expected Results:  
I should be able to place shortcut any where I want like I can in  4.14.5
Comment 1 Bit Twister 2016-04-14 22:52:30 UTC
# kde4-config --version
Qt: 4.8.7
KDE Development Platform: 4.14.18
kde4-config: 1.0
Comment 2 Nate Graham 2018-06-08 18:24:16 UTC
Hello!

This bug report was filed for KDE Plasma 4, which reached end-of-support status in August 2015. KDE Plasma 5's desktop shell has been almost completely rewritten for better performance and usability, so it is likely that this bug has already been resolved in Plasma 5.

Accordingly, we hope you understand why we must close this bug report. If the issue described  here is still present in KDE Plasma 5.12 or later, please feel free to open a new ticket in the "plasmashell" product after reading https://community.kde.org/Get_Involved/Bug_Reporting

If you would like to get involved in KDE's bug triaging effort so that future mass bug closes like this are less likely, please read https://community.kde.org/Get_Involved#Bug_Triaging

Thanks for your understanding!

Nate Graham