Currently, when you install Kubuntu 19.10 onto a computer that has multiple monitors, KDE only puts panels onto the default monitor and the user has to add panels to all additional monitors. I want to make my case that this should NOT be the default practice. I think all panels, that are visible in a one-monitor setup, should also be on each and every additional monitor until they are decidedly remove. I'll make my case with the "Application Menu Panel" alone, but I have the same opinion for all other panels. Because KDE doesn't put an Application Menu Panel onto each monitor, the new KDE user will not know how to access an Application's main menu if they have the window open on one of the additional monitors. For new users of KDE, like myself, it is very clear that the burden of customization should be on the advanced user and not the new user. The advanced KDE user will know instantly how to remove an unwanted panel, but the new user is burdened with a task that is way more difficult than removing an unwanted panel: learning what panels are, learning the names of each type of panel, dealing with bad panel creation workflow (explained below in #4). Please let me help you see this from the eyes of a new user who has an application open on one of the additional monitors in a multi-monitor setup. 1) First I looked at the top of the application window and didn't see the application's main menu where I'd expected it to be (either in that window's title bar, or at the top of the entire monitor's screen). 2) I hit the alt-key (a common MS shortcut), hoping that the Application's main menu was just hidden and that alt would bring it up. 3) I had to do an internet search and learn about panels in KDE and then proceed to create my first panel. 4) When I right-clicked on the additional monitor's desktop and selected Panel > Application Menu, nothing happened on the vary monitor I did this on, instead (outside of my eye's focus) it added an additional Application Menu panel to the default monitor (which already has an Application Menu Panel), and worse: it added it on top of the existing Application Menu panel that was already on that monitor (making it practically invisible that anything had occurred)! Now, I ask you this. Is this the type of user experience that produces new user adoption? Wouldn't it be better to put all the panels, that are on the default monitor, onto each and every additional monitor by default? Put the burden of customization onto the advanced user (the one who already know how to do it). After all, the burden of removing a panel is easier that creating and customizing a new one from scratch (especially for a new user who doesn't even know what a "panel" is). You don't need to put this burden onto the new user who can't access the main menu of an application their using because it is simply open within and additional monitor. Who on the KDE development team thinks this is an acceptable default behavior (to not make the "main menu of an application" accessible until you create and customize a panel onto that monitor)? I love that KDE is so customizable, but you guys need to couple that richness with sensible defaults and this is an area that is not sensible (to the new user)! ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: kubuntu-desktop 1.387 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: KDE Date: Tue Jan 28 03:13:51 2020 InstallationDate: Installed on 2020-01-27 (1 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: kubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) Downstream Report: https://bugs.launchpad.net/ubuntu/+source/kubuntu-meta/+bug/1861088