KDE plasma 5: No taskbar (no rightclick-menu on desktop either) anymoreHow to restore kde plasma desktopAutomatically refreshing Debian Wheezy KDE Plasma DesktopDark kde plasma 5 session on GentooKDE Plasma crashes after logging inHow to hide Kopete on KDE taskbar?KDE plasma disappear panel settingsKDE global menu disappeared in Plasma 5.12Robust command line (CLI) configuration of Plasma (KDE) appletsKDE Plasma System Try no percentage batterysystemsettings5 stays black on KDE Plasma

Why is my log file so massive? 22gb. I am running log backups

What is it called when one voice type sings a 'solo'?

Typesetting a double Over Dot on top of a symbol

If a centaur druid Wild Shapes into a Giant Elk, do their Charge features stack?

Is there any use for defining additional entity types in a SOQL FROM clause?

Why was the "bread communication" in the arena of Catching Fire left out in the movie?

How can I fix this gap between bookcases I made?

Does a dangling wire really electrocute me if I'm standing in water?

Why airport relocation isn't done gradually?

Calculate Levenshtein distance between two strings in Python

Doomsday-clock for my fantasy planet

Shall I use personal or official e-mail account when registering to external websites for work purpose?

Denied boarding due to overcrowding, Sparpreis ticket. What are my rights?

What is GPS' 19 year rollover and does it present a cybersecurity issue?

Crop image to path created in TikZ?

What is the command to reset a PC without deleting any files

extract characters between two commas?

Is there a familial term for apples and pears?

Does the average primeness of natural numbers tend to zero?

Pristine Bit Checking

Is Social Media Science Fiction?

New order #4: World

Is this food a bread or a loaf?

Landlord wants to switch my lease to a "Land contract" to "get back at the city"



KDE plasma 5: No taskbar (no rightclick-menu on desktop either) anymore


How to restore kde plasma desktopAutomatically refreshing Debian Wheezy KDE Plasma DesktopDark kde plasma 5 session on GentooKDE Plasma crashes after logging inHow to hide Kopete on KDE taskbar?KDE plasma disappear panel settingsKDE global menu disappeared in Plasma 5.12Robust command line (CLI) configuration of Plasma (KDE) appletsKDE Plasma System Try no percentage batterysystemsettings5 stays black on KDE Plasma






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;








-1















In short:

I have the same problem, as is described here. However the suggested solutions do not work for me.



I managed to kill plasmashell via killall plasmashell and could then manually restart it using the command plasmashell.

Doing so resulted in the following messages to pop up on my screen:



ddons.desktopparser: Could not locate service type file kservicetypes5/plasma-popupapplet.desktop, tried ("/home/<userName>/.local/share", "/home/<userName>/.local/share/flatpak/exports/share", "/var/lib/flatpak/exports/share", "/usr/share/usr/share/xsessions/plasma", "/usr/local/share", "/usr/share")
kf5.kcoreaddons.desktopparser: Could not locate service type file kservicetypes5/plasma-popupapplet.desktop, tried ("/home/<userName>/.local/share", "/home/<userName>/.local/share/flatpak/exports/share", "/var/lib/flatpak/exports/share", "/usr/share/usr/share/xsessions/plasma", "/usr/local/share", "/usr/share")
kf5.kcoreaddons.desktopparser: Could not locate service type file kservicetypes5/plasma-popupapplet.desktop, tried ("/home/<userName>/.local/share", "/home/<userName>/.local/share/flatpak/exports/share", "/var/lib/flatpak/exports/share", "/usr/share/usr/share/xsessions/plasma", "/usr/local/share", "/usr/share")
kf5.kcoreaddons.desktopparser: Could not locate service type file kservicetypes5/plasma-popupapplet.desktop, tried ("/home/<userName>/.local/share", "/home/<userName>/.local/share/flatpak/exports/share", "/var/lib/flatpak/exports/share", "/usr/share/usr/share/xsessions/plasma", "/usr/local/share", "/usr/share")
kf5.kcoreaddons.desktopparser: Could not locate service type file kservicetypes5/plasma-popupapplet.desktop, tried ("/home/<userName>/.local/share", "/home/<userName>/.local/share/flatpak/exports/share", "/var/lib/flatpak/exports/share", "/usr/share/usr/share/xsessions/plasma", "/usr/local/share", "/usr/share")
kf5.kcoreaddons.desktopparser: Could not locate service type file kservicetypes5/plasma-popupapplet.desktop, tried ("/home/<userName>/.local/share", "/home/<userName>/.local/share/flatpak/exports/share", "/var/lib/flatpak/exports/share", "/usr/share/usr/share/xsessions/plasma", "/usr/local/share", "/usr/share")
kf5.kcoreaddons.desktopparser: Could not locate service type file kservicetypes5/plasma-popupapplet.desktop, tried ("/home/<userName>/.local/share", "/home/<userName>/.local/share/flatpak/exports/share", "/var/lib/flatpak/exports/share", "/usr/share/usr/share/xsessions/plasma", "/usr/local/share", "/usr/share")
kf5.kcoreaddons.desktopparser: Could not locate service type file kservicetypes5/plasma-popupapplet.desktop, tried ("/home/<userName>/.local/share", "/home/<userName>/.local/share/flatpak/exports/share", "/var/lib/flatpak/exports/share", "/usr/share/usr/share/xsessions/plasma", "/usr/local/share", "/usr/share")
kf5.kcoreaddons.desktopparser: Could not locate service type file kservicetypes5/plasma-popupapplet.desktop, tried ("/home/<userName>/.local/share", "/home/<userName>/.local/share/flatpak/exports/share", "/var/lib/flatpak/exports/share", "/usr/share/usr/share/xsessions/plasma", "/usr/local/share", "/usr/share")
kf5.kcoreaddons.desktopparser: Could not locate service type file kservicetypes5/plasma-popupapplet.desktop, tried ("/home/<userName>/.local/share", "/home/<userName>/.local/share/flatpak/exports/share", "/var/lib/flatpak/exports/share", "/usr/share/usr/share/xsessions/plasma", "/usr/local/share", "/usr/share")
kf5.kcoreaddons.desktopparser: Could not locate service type file kservicetypes5/plasma-popupapplet.desktop, tried ("/home/<userName>/.local/share", "/home/<userName>/.local/share/flatpak/exports/share", "/var/lib/flatpak/exports/share", "/usr/share/usr/share/xsessions/plasma", "/usr/local/share", "/usr/share")
No metadata file in the package, expected it at: "/usr/share/backgrounds/linuxmint-sylvia/"
No metadata file in the package, expected it at: "/usr/share/backgrounds/linuxmint-sylvia/"
No metadata file in the package, expected it at: "/usr/share/backgrounds/linuxmint-sylvia/"
trying to show an empty dialog
file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:147:19: QML Loader: Binding loop detected for property "height"
file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:147:19: QML Loader: Binding loop detected for property "height"
file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Panel.qml:83: TypeError: Cannot read property 'Layout' of null
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/main.qml:112:20: Unable to assign [undefined] to int
kf5.kcoreaddons.desktopparser: Could not locate service type file kservicetypes5/plasma-popupapplet.desktop, tried ("/home/<userName>/.local/share", "/home/<userName>/.local/share/flatpak/exports/share", "/var/lib/flatpak/exports/share", "/usr/share/usr/share/xsessions/plasma", "/usr/local/share", "/usr/share")
Trying to use rootObject before initialization is completed, whilst using setInitializationDelayed. Forcing completion
file:///usr/share/plasma/plasmoids/org.kde.plasma.digitalclock/contents/ui/main.qml:78:27: Unable to assign [undefined] to QStringList
file:///usr/share/plasma/plasmoids/org.kde.plasma.digitalclock/contents/ui/main.qml:37: TypeError: Cannot read property 'DateTime' of undefined
trying to show an empty dialog
trying to show an empty dialog
trying to show an empty dialog
file:///usr/share/plasma/plasmoids/org.kde.plasma.digitalclock/contents/ui/DigitalClock.qml:443:5: QML Text: Cannot anchor to a null item.
kf5.kcoreaddons.desktopparser: Could not locate service type file kservicetypes5/plasma-popupapplet.desktop, tried ("/home/<userName>/.local/share", "/home/<userName>/.local/share/flatpak/exports/share", "/var/lib/flatpak/exports/share", "/usr/share/usr/share/xsessions/plasma", "/usr/local/share", "/usr/share")
kf5.kcoreaddons.desktopparser: Could not locate service type file kservicetypes5/plasma-popupapplet.desktop, tried ("/home/<userName>/.local/share", "/home/<userName>/.local/share/flatpak/exports/share", "/var/lib/flatpak/exports/share", "/usr/share/usr/share/xsessions/plasma", "/usr/local/share", "/usr/share")
kf5.kcoreaddons.desktopparser: Could not locate service type file kservicetypes5/plasma-popupapplet.desktop, tried ("/home/<userName>/.local/share", "/home/<userName>/.local/share/flatpak/exports/share", "/var/lib/flatpak/exports/share", "/usr/share/usr/share/xsessions/plasma", "/usr/local/share", "/usr/share")
kf5.kcoreaddons.desktopparser: Could not locate service type file kservicetypes5/plasma-popupapplet.desktop, tried ("/home/<userName>/.local/share", "/home/<userName>/.local/share/flatpak/exports/share", "/var/lib/flatpak/exports/share", "/usr/share/usr/share/xsessions/plasma", "/usr/local/share", "/usr/share")


I believe that most of this isn't too important but I guess the following lines have something to do with my problem:
trying to show an empty dialog



file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:147:19: QML Loader: Binding loop detected for property "height"
file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:147:19: QML Loader: Binding loop detected for property "height"
file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Panel.qml:83: TypeError: Cannot read property 'Layout' of null


To me this indicates that there is some invalid data being passed around/created at some point that results in a null-value here which (I believe) is the root cause of the desktop not functioning well.




The longer story:

So I have Linux Mint 19 installed on my laptop on top of which I installed KDE. Everything was working just fine.

Today I went ahead and installed KDE neon on another partition on my laptop, leaving (in theory) the Mint-partition completely untouched.

The thing that got changed was my EFI-partition and the swap partition which both systems share.

It also seems as if the KDE Neon install has completely overridden the GRUB loader I had from Mint (Via BIOS I can select the loader of each system but the both result in the very same bootloader so I believe Neon simply overwrote the one of Mint).



I can boot into Mint just fine though. The only problem being that when I am logged in the splash screen takes way longer than before and after that I enter my desktop that now misses the start menu and the complete task bar. They're just gone. Right-clicking on my desktop doesn't do anything either.

Although I can see all my shortcuts on the desktop, I can't click any of them (more precisely: I can click on them but nothing happens).




EDIT:

I have thought about this problem a bit more: When the installer formatted the boot-partition, it also deleted the installed kernels. So maybe the problem is that the KDE-Neon kernel isn't uite compatible with the Linux Mint system which causes some trouble. I'll investigate further into that...










share|improve this question






























    -1















    In short:

    I have the same problem, as is described here. However the suggested solutions do not work for me.



    I managed to kill plasmashell via killall plasmashell and could then manually restart it using the command plasmashell.

    Doing so resulted in the following messages to pop up on my screen:



    ddons.desktopparser: Could not locate service type file kservicetypes5/plasma-popupapplet.desktop, tried ("/home/<userName>/.local/share", "/home/<userName>/.local/share/flatpak/exports/share", "/var/lib/flatpak/exports/share", "/usr/share/usr/share/xsessions/plasma", "/usr/local/share", "/usr/share")
    kf5.kcoreaddons.desktopparser: Could not locate service type file kservicetypes5/plasma-popupapplet.desktop, tried ("/home/<userName>/.local/share", "/home/<userName>/.local/share/flatpak/exports/share", "/var/lib/flatpak/exports/share", "/usr/share/usr/share/xsessions/plasma", "/usr/local/share", "/usr/share")
    kf5.kcoreaddons.desktopparser: Could not locate service type file kservicetypes5/plasma-popupapplet.desktop, tried ("/home/<userName>/.local/share", "/home/<userName>/.local/share/flatpak/exports/share", "/var/lib/flatpak/exports/share", "/usr/share/usr/share/xsessions/plasma", "/usr/local/share", "/usr/share")
    kf5.kcoreaddons.desktopparser: Could not locate service type file kservicetypes5/plasma-popupapplet.desktop, tried ("/home/<userName>/.local/share", "/home/<userName>/.local/share/flatpak/exports/share", "/var/lib/flatpak/exports/share", "/usr/share/usr/share/xsessions/plasma", "/usr/local/share", "/usr/share")
    kf5.kcoreaddons.desktopparser: Could not locate service type file kservicetypes5/plasma-popupapplet.desktop, tried ("/home/<userName>/.local/share", "/home/<userName>/.local/share/flatpak/exports/share", "/var/lib/flatpak/exports/share", "/usr/share/usr/share/xsessions/plasma", "/usr/local/share", "/usr/share")
    kf5.kcoreaddons.desktopparser: Could not locate service type file kservicetypes5/plasma-popupapplet.desktop, tried ("/home/<userName>/.local/share", "/home/<userName>/.local/share/flatpak/exports/share", "/var/lib/flatpak/exports/share", "/usr/share/usr/share/xsessions/plasma", "/usr/local/share", "/usr/share")
    kf5.kcoreaddons.desktopparser: Could not locate service type file kservicetypes5/plasma-popupapplet.desktop, tried ("/home/<userName>/.local/share", "/home/<userName>/.local/share/flatpak/exports/share", "/var/lib/flatpak/exports/share", "/usr/share/usr/share/xsessions/plasma", "/usr/local/share", "/usr/share")
    kf5.kcoreaddons.desktopparser: Could not locate service type file kservicetypes5/plasma-popupapplet.desktop, tried ("/home/<userName>/.local/share", "/home/<userName>/.local/share/flatpak/exports/share", "/var/lib/flatpak/exports/share", "/usr/share/usr/share/xsessions/plasma", "/usr/local/share", "/usr/share")
    kf5.kcoreaddons.desktopparser: Could not locate service type file kservicetypes5/plasma-popupapplet.desktop, tried ("/home/<userName>/.local/share", "/home/<userName>/.local/share/flatpak/exports/share", "/var/lib/flatpak/exports/share", "/usr/share/usr/share/xsessions/plasma", "/usr/local/share", "/usr/share")
    kf5.kcoreaddons.desktopparser: Could not locate service type file kservicetypes5/plasma-popupapplet.desktop, tried ("/home/<userName>/.local/share", "/home/<userName>/.local/share/flatpak/exports/share", "/var/lib/flatpak/exports/share", "/usr/share/usr/share/xsessions/plasma", "/usr/local/share", "/usr/share")
    kf5.kcoreaddons.desktopparser: Could not locate service type file kservicetypes5/plasma-popupapplet.desktop, tried ("/home/<userName>/.local/share", "/home/<userName>/.local/share/flatpak/exports/share", "/var/lib/flatpak/exports/share", "/usr/share/usr/share/xsessions/plasma", "/usr/local/share", "/usr/share")
    No metadata file in the package, expected it at: "/usr/share/backgrounds/linuxmint-sylvia/"
    No metadata file in the package, expected it at: "/usr/share/backgrounds/linuxmint-sylvia/"
    No metadata file in the package, expected it at: "/usr/share/backgrounds/linuxmint-sylvia/"
    trying to show an empty dialog
    file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:147:19: QML Loader: Binding loop detected for property "height"
    file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:147:19: QML Loader: Binding loop detected for property "height"
    file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Panel.qml:83: TypeError: Cannot read property 'Layout' of null
    Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
    file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/main.qml:112:20: Unable to assign [undefined] to int
    kf5.kcoreaddons.desktopparser: Could not locate service type file kservicetypes5/plasma-popupapplet.desktop, tried ("/home/<userName>/.local/share", "/home/<userName>/.local/share/flatpak/exports/share", "/var/lib/flatpak/exports/share", "/usr/share/usr/share/xsessions/plasma", "/usr/local/share", "/usr/share")
    Trying to use rootObject before initialization is completed, whilst using setInitializationDelayed. Forcing completion
    file:///usr/share/plasma/plasmoids/org.kde.plasma.digitalclock/contents/ui/main.qml:78:27: Unable to assign [undefined] to QStringList
    file:///usr/share/plasma/plasmoids/org.kde.plasma.digitalclock/contents/ui/main.qml:37: TypeError: Cannot read property 'DateTime' of undefined
    trying to show an empty dialog
    trying to show an empty dialog
    trying to show an empty dialog
    file:///usr/share/plasma/plasmoids/org.kde.plasma.digitalclock/contents/ui/DigitalClock.qml:443:5: QML Text: Cannot anchor to a null item.
    kf5.kcoreaddons.desktopparser: Could not locate service type file kservicetypes5/plasma-popupapplet.desktop, tried ("/home/<userName>/.local/share", "/home/<userName>/.local/share/flatpak/exports/share", "/var/lib/flatpak/exports/share", "/usr/share/usr/share/xsessions/plasma", "/usr/local/share", "/usr/share")
    kf5.kcoreaddons.desktopparser: Could not locate service type file kservicetypes5/plasma-popupapplet.desktop, tried ("/home/<userName>/.local/share", "/home/<userName>/.local/share/flatpak/exports/share", "/var/lib/flatpak/exports/share", "/usr/share/usr/share/xsessions/plasma", "/usr/local/share", "/usr/share")
    kf5.kcoreaddons.desktopparser: Could not locate service type file kservicetypes5/plasma-popupapplet.desktop, tried ("/home/<userName>/.local/share", "/home/<userName>/.local/share/flatpak/exports/share", "/var/lib/flatpak/exports/share", "/usr/share/usr/share/xsessions/plasma", "/usr/local/share", "/usr/share")
    kf5.kcoreaddons.desktopparser: Could not locate service type file kservicetypes5/plasma-popupapplet.desktop, tried ("/home/<userName>/.local/share", "/home/<userName>/.local/share/flatpak/exports/share", "/var/lib/flatpak/exports/share", "/usr/share/usr/share/xsessions/plasma", "/usr/local/share", "/usr/share")


    I believe that most of this isn't too important but I guess the following lines have something to do with my problem:
    trying to show an empty dialog



    file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:147:19: QML Loader: Binding loop detected for property "height"
    file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:147:19: QML Loader: Binding loop detected for property "height"
    file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Panel.qml:83: TypeError: Cannot read property 'Layout' of null


    To me this indicates that there is some invalid data being passed around/created at some point that results in a null-value here which (I believe) is the root cause of the desktop not functioning well.




    The longer story:

    So I have Linux Mint 19 installed on my laptop on top of which I installed KDE. Everything was working just fine.

    Today I went ahead and installed KDE neon on another partition on my laptop, leaving (in theory) the Mint-partition completely untouched.

    The thing that got changed was my EFI-partition and the swap partition which both systems share.

    It also seems as if the KDE Neon install has completely overridden the GRUB loader I had from Mint (Via BIOS I can select the loader of each system but the both result in the very same bootloader so I believe Neon simply overwrote the one of Mint).



    I can boot into Mint just fine though. The only problem being that when I am logged in the splash screen takes way longer than before and after that I enter my desktop that now misses the start menu and the complete task bar. They're just gone. Right-clicking on my desktop doesn't do anything either.

    Although I can see all my shortcuts on the desktop, I can't click any of them (more precisely: I can click on them but nothing happens).




    EDIT:

    I have thought about this problem a bit more: When the installer formatted the boot-partition, it also deleted the installed kernels. So maybe the problem is that the KDE-Neon kernel isn't uite compatible with the Linux Mint system which causes some trouble. I'll investigate further into that...










    share|improve this question


























      -1












      -1








      -1








      In short:

      I have the same problem, as is described here. However the suggested solutions do not work for me.



      I managed to kill plasmashell via killall plasmashell and could then manually restart it using the command plasmashell.

      Doing so resulted in the following messages to pop up on my screen:



      ddons.desktopparser: Could not locate service type file kservicetypes5/plasma-popupapplet.desktop, tried ("/home/<userName>/.local/share", "/home/<userName>/.local/share/flatpak/exports/share", "/var/lib/flatpak/exports/share", "/usr/share/usr/share/xsessions/plasma", "/usr/local/share", "/usr/share")
      kf5.kcoreaddons.desktopparser: Could not locate service type file kservicetypes5/plasma-popupapplet.desktop, tried ("/home/<userName>/.local/share", "/home/<userName>/.local/share/flatpak/exports/share", "/var/lib/flatpak/exports/share", "/usr/share/usr/share/xsessions/plasma", "/usr/local/share", "/usr/share")
      kf5.kcoreaddons.desktopparser: Could not locate service type file kservicetypes5/plasma-popupapplet.desktop, tried ("/home/<userName>/.local/share", "/home/<userName>/.local/share/flatpak/exports/share", "/var/lib/flatpak/exports/share", "/usr/share/usr/share/xsessions/plasma", "/usr/local/share", "/usr/share")
      kf5.kcoreaddons.desktopparser: Could not locate service type file kservicetypes5/plasma-popupapplet.desktop, tried ("/home/<userName>/.local/share", "/home/<userName>/.local/share/flatpak/exports/share", "/var/lib/flatpak/exports/share", "/usr/share/usr/share/xsessions/plasma", "/usr/local/share", "/usr/share")
      kf5.kcoreaddons.desktopparser: Could not locate service type file kservicetypes5/plasma-popupapplet.desktop, tried ("/home/<userName>/.local/share", "/home/<userName>/.local/share/flatpak/exports/share", "/var/lib/flatpak/exports/share", "/usr/share/usr/share/xsessions/plasma", "/usr/local/share", "/usr/share")
      kf5.kcoreaddons.desktopparser: Could not locate service type file kservicetypes5/plasma-popupapplet.desktop, tried ("/home/<userName>/.local/share", "/home/<userName>/.local/share/flatpak/exports/share", "/var/lib/flatpak/exports/share", "/usr/share/usr/share/xsessions/plasma", "/usr/local/share", "/usr/share")
      kf5.kcoreaddons.desktopparser: Could not locate service type file kservicetypes5/plasma-popupapplet.desktop, tried ("/home/<userName>/.local/share", "/home/<userName>/.local/share/flatpak/exports/share", "/var/lib/flatpak/exports/share", "/usr/share/usr/share/xsessions/plasma", "/usr/local/share", "/usr/share")
      kf5.kcoreaddons.desktopparser: Could not locate service type file kservicetypes5/plasma-popupapplet.desktop, tried ("/home/<userName>/.local/share", "/home/<userName>/.local/share/flatpak/exports/share", "/var/lib/flatpak/exports/share", "/usr/share/usr/share/xsessions/plasma", "/usr/local/share", "/usr/share")
      kf5.kcoreaddons.desktopparser: Could not locate service type file kservicetypes5/plasma-popupapplet.desktop, tried ("/home/<userName>/.local/share", "/home/<userName>/.local/share/flatpak/exports/share", "/var/lib/flatpak/exports/share", "/usr/share/usr/share/xsessions/plasma", "/usr/local/share", "/usr/share")
      kf5.kcoreaddons.desktopparser: Could not locate service type file kservicetypes5/plasma-popupapplet.desktop, tried ("/home/<userName>/.local/share", "/home/<userName>/.local/share/flatpak/exports/share", "/var/lib/flatpak/exports/share", "/usr/share/usr/share/xsessions/plasma", "/usr/local/share", "/usr/share")
      kf5.kcoreaddons.desktopparser: Could not locate service type file kservicetypes5/plasma-popupapplet.desktop, tried ("/home/<userName>/.local/share", "/home/<userName>/.local/share/flatpak/exports/share", "/var/lib/flatpak/exports/share", "/usr/share/usr/share/xsessions/plasma", "/usr/local/share", "/usr/share")
      No metadata file in the package, expected it at: "/usr/share/backgrounds/linuxmint-sylvia/"
      No metadata file in the package, expected it at: "/usr/share/backgrounds/linuxmint-sylvia/"
      No metadata file in the package, expected it at: "/usr/share/backgrounds/linuxmint-sylvia/"
      trying to show an empty dialog
      file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:147:19: QML Loader: Binding loop detected for property "height"
      file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:147:19: QML Loader: Binding loop detected for property "height"
      file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Panel.qml:83: TypeError: Cannot read property 'Layout' of null
      Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
      file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/main.qml:112:20: Unable to assign [undefined] to int
      kf5.kcoreaddons.desktopparser: Could not locate service type file kservicetypes5/plasma-popupapplet.desktop, tried ("/home/<userName>/.local/share", "/home/<userName>/.local/share/flatpak/exports/share", "/var/lib/flatpak/exports/share", "/usr/share/usr/share/xsessions/plasma", "/usr/local/share", "/usr/share")
      Trying to use rootObject before initialization is completed, whilst using setInitializationDelayed. Forcing completion
      file:///usr/share/plasma/plasmoids/org.kde.plasma.digitalclock/contents/ui/main.qml:78:27: Unable to assign [undefined] to QStringList
      file:///usr/share/plasma/plasmoids/org.kde.plasma.digitalclock/contents/ui/main.qml:37: TypeError: Cannot read property 'DateTime' of undefined
      trying to show an empty dialog
      trying to show an empty dialog
      trying to show an empty dialog
      file:///usr/share/plasma/plasmoids/org.kde.plasma.digitalclock/contents/ui/DigitalClock.qml:443:5: QML Text: Cannot anchor to a null item.
      kf5.kcoreaddons.desktopparser: Could not locate service type file kservicetypes5/plasma-popupapplet.desktop, tried ("/home/<userName>/.local/share", "/home/<userName>/.local/share/flatpak/exports/share", "/var/lib/flatpak/exports/share", "/usr/share/usr/share/xsessions/plasma", "/usr/local/share", "/usr/share")
      kf5.kcoreaddons.desktopparser: Could not locate service type file kservicetypes5/plasma-popupapplet.desktop, tried ("/home/<userName>/.local/share", "/home/<userName>/.local/share/flatpak/exports/share", "/var/lib/flatpak/exports/share", "/usr/share/usr/share/xsessions/plasma", "/usr/local/share", "/usr/share")
      kf5.kcoreaddons.desktopparser: Could not locate service type file kservicetypes5/plasma-popupapplet.desktop, tried ("/home/<userName>/.local/share", "/home/<userName>/.local/share/flatpak/exports/share", "/var/lib/flatpak/exports/share", "/usr/share/usr/share/xsessions/plasma", "/usr/local/share", "/usr/share")
      kf5.kcoreaddons.desktopparser: Could not locate service type file kservicetypes5/plasma-popupapplet.desktop, tried ("/home/<userName>/.local/share", "/home/<userName>/.local/share/flatpak/exports/share", "/var/lib/flatpak/exports/share", "/usr/share/usr/share/xsessions/plasma", "/usr/local/share", "/usr/share")


      I believe that most of this isn't too important but I guess the following lines have something to do with my problem:
      trying to show an empty dialog



      file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:147:19: QML Loader: Binding loop detected for property "height"
      file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:147:19: QML Loader: Binding loop detected for property "height"
      file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Panel.qml:83: TypeError: Cannot read property 'Layout' of null


      To me this indicates that there is some invalid data being passed around/created at some point that results in a null-value here which (I believe) is the root cause of the desktop not functioning well.




      The longer story:

      So I have Linux Mint 19 installed on my laptop on top of which I installed KDE. Everything was working just fine.

      Today I went ahead and installed KDE neon on another partition on my laptop, leaving (in theory) the Mint-partition completely untouched.

      The thing that got changed was my EFI-partition and the swap partition which both systems share.

      It also seems as if the KDE Neon install has completely overridden the GRUB loader I had from Mint (Via BIOS I can select the loader of each system but the both result in the very same bootloader so I believe Neon simply overwrote the one of Mint).



      I can boot into Mint just fine though. The only problem being that when I am logged in the splash screen takes way longer than before and after that I enter my desktop that now misses the start menu and the complete task bar. They're just gone. Right-clicking on my desktop doesn't do anything either.

      Although I can see all my shortcuts on the desktop, I can't click any of them (more precisely: I can click on them but nothing happens).




      EDIT:

      I have thought about this problem a bit more: When the installer formatted the boot-partition, it also deleted the installed kernels. So maybe the problem is that the KDE-Neon kernel isn't uite compatible with the Linux Mint system which causes some trouble. I'll investigate further into that...










      share|improve this question
















      In short:

      I have the same problem, as is described here. However the suggested solutions do not work for me.



      I managed to kill plasmashell via killall plasmashell and could then manually restart it using the command plasmashell.

      Doing so resulted in the following messages to pop up on my screen:



      ddons.desktopparser: Could not locate service type file kservicetypes5/plasma-popupapplet.desktop, tried ("/home/<userName>/.local/share", "/home/<userName>/.local/share/flatpak/exports/share", "/var/lib/flatpak/exports/share", "/usr/share/usr/share/xsessions/plasma", "/usr/local/share", "/usr/share")
      kf5.kcoreaddons.desktopparser: Could not locate service type file kservicetypes5/plasma-popupapplet.desktop, tried ("/home/<userName>/.local/share", "/home/<userName>/.local/share/flatpak/exports/share", "/var/lib/flatpak/exports/share", "/usr/share/usr/share/xsessions/plasma", "/usr/local/share", "/usr/share")
      kf5.kcoreaddons.desktopparser: Could not locate service type file kservicetypes5/plasma-popupapplet.desktop, tried ("/home/<userName>/.local/share", "/home/<userName>/.local/share/flatpak/exports/share", "/var/lib/flatpak/exports/share", "/usr/share/usr/share/xsessions/plasma", "/usr/local/share", "/usr/share")
      kf5.kcoreaddons.desktopparser: Could not locate service type file kservicetypes5/plasma-popupapplet.desktop, tried ("/home/<userName>/.local/share", "/home/<userName>/.local/share/flatpak/exports/share", "/var/lib/flatpak/exports/share", "/usr/share/usr/share/xsessions/plasma", "/usr/local/share", "/usr/share")
      kf5.kcoreaddons.desktopparser: Could not locate service type file kservicetypes5/plasma-popupapplet.desktop, tried ("/home/<userName>/.local/share", "/home/<userName>/.local/share/flatpak/exports/share", "/var/lib/flatpak/exports/share", "/usr/share/usr/share/xsessions/plasma", "/usr/local/share", "/usr/share")
      kf5.kcoreaddons.desktopparser: Could not locate service type file kservicetypes5/plasma-popupapplet.desktop, tried ("/home/<userName>/.local/share", "/home/<userName>/.local/share/flatpak/exports/share", "/var/lib/flatpak/exports/share", "/usr/share/usr/share/xsessions/plasma", "/usr/local/share", "/usr/share")
      kf5.kcoreaddons.desktopparser: Could not locate service type file kservicetypes5/plasma-popupapplet.desktop, tried ("/home/<userName>/.local/share", "/home/<userName>/.local/share/flatpak/exports/share", "/var/lib/flatpak/exports/share", "/usr/share/usr/share/xsessions/plasma", "/usr/local/share", "/usr/share")
      kf5.kcoreaddons.desktopparser: Could not locate service type file kservicetypes5/plasma-popupapplet.desktop, tried ("/home/<userName>/.local/share", "/home/<userName>/.local/share/flatpak/exports/share", "/var/lib/flatpak/exports/share", "/usr/share/usr/share/xsessions/plasma", "/usr/local/share", "/usr/share")
      kf5.kcoreaddons.desktopparser: Could not locate service type file kservicetypes5/plasma-popupapplet.desktop, tried ("/home/<userName>/.local/share", "/home/<userName>/.local/share/flatpak/exports/share", "/var/lib/flatpak/exports/share", "/usr/share/usr/share/xsessions/plasma", "/usr/local/share", "/usr/share")
      kf5.kcoreaddons.desktopparser: Could not locate service type file kservicetypes5/plasma-popupapplet.desktop, tried ("/home/<userName>/.local/share", "/home/<userName>/.local/share/flatpak/exports/share", "/var/lib/flatpak/exports/share", "/usr/share/usr/share/xsessions/plasma", "/usr/local/share", "/usr/share")
      kf5.kcoreaddons.desktopparser: Could not locate service type file kservicetypes5/plasma-popupapplet.desktop, tried ("/home/<userName>/.local/share", "/home/<userName>/.local/share/flatpak/exports/share", "/var/lib/flatpak/exports/share", "/usr/share/usr/share/xsessions/plasma", "/usr/local/share", "/usr/share")
      No metadata file in the package, expected it at: "/usr/share/backgrounds/linuxmint-sylvia/"
      No metadata file in the package, expected it at: "/usr/share/backgrounds/linuxmint-sylvia/"
      No metadata file in the package, expected it at: "/usr/share/backgrounds/linuxmint-sylvia/"
      trying to show an empty dialog
      file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:147:19: QML Loader: Binding loop detected for property "height"
      file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:147:19: QML Loader: Binding loop detected for property "height"
      file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Panel.qml:83: TypeError: Cannot read property 'Layout' of null
      Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
      file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/main.qml:112:20: Unable to assign [undefined] to int
      kf5.kcoreaddons.desktopparser: Could not locate service type file kservicetypes5/plasma-popupapplet.desktop, tried ("/home/<userName>/.local/share", "/home/<userName>/.local/share/flatpak/exports/share", "/var/lib/flatpak/exports/share", "/usr/share/usr/share/xsessions/plasma", "/usr/local/share", "/usr/share")
      Trying to use rootObject before initialization is completed, whilst using setInitializationDelayed. Forcing completion
      file:///usr/share/plasma/plasmoids/org.kde.plasma.digitalclock/contents/ui/main.qml:78:27: Unable to assign [undefined] to QStringList
      file:///usr/share/plasma/plasmoids/org.kde.plasma.digitalclock/contents/ui/main.qml:37: TypeError: Cannot read property 'DateTime' of undefined
      trying to show an empty dialog
      trying to show an empty dialog
      trying to show an empty dialog
      file:///usr/share/plasma/plasmoids/org.kde.plasma.digitalclock/contents/ui/DigitalClock.qml:443:5: QML Text: Cannot anchor to a null item.
      kf5.kcoreaddons.desktopparser: Could not locate service type file kservicetypes5/plasma-popupapplet.desktop, tried ("/home/<userName>/.local/share", "/home/<userName>/.local/share/flatpak/exports/share", "/var/lib/flatpak/exports/share", "/usr/share/usr/share/xsessions/plasma", "/usr/local/share", "/usr/share")
      kf5.kcoreaddons.desktopparser: Could not locate service type file kservicetypes5/plasma-popupapplet.desktop, tried ("/home/<userName>/.local/share", "/home/<userName>/.local/share/flatpak/exports/share", "/var/lib/flatpak/exports/share", "/usr/share/usr/share/xsessions/plasma", "/usr/local/share", "/usr/share")
      kf5.kcoreaddons.desktopparser: Could not locate service type file kservicetypes5/plasma-popupapplet.desktop, tried ("/home/<userName>/.local/share", "/home/<userName>/.local/share/flatpak/exports/share", "/var/lib/flatpak/exports/share", "/usr/share/usr/share/xsessions/plasma", "/usr/local/share", "/usr/share")
      kf5.kcoreaddons.desktopparser: Could not locate service type file kservicetypes5/plasma-popupapplet.desktop, tried ("/home/<userName>/.local/share", "/home/<userName>/.local/share/flatpak/exports/share", "/var/lib/flatpak/exports/share", "/usr/share/usr/share/xsessions/plasma", "/usr/local/share", "/usr/share")


      I believe that most of this isn't too important but I guess the following lines have something to do with my problem:
      trying to show an empty dialog



      file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:147:19: QML Loader: Binding loop detected for property "height"
      file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:147:19: QML Loader: Binding loop detected for property "height"
      file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Panel.qml:83: TypeError: Cannot read property 'Layout' of null


      To me this indicates that there is some invalid data being passed around/created at some point that results in a null-value here which (I believe) is the root cause of the desktop not functioning well.




      The longer story:

      So I have Linux Mint 19 installed on my laptop on top of which I installed KDE. Everything was working just fine.

      Today I went ahead and installed KDE neon on another partition on my laptop, leaving (in theory) the Mint-partition completely untouched.

      The thing that got changed was my EFI-partition and the swap partition which both systems share.

      It also seems as if the KDE Neon install has completely overridden the GRUB loader I had from Mint (Via BIOS I can select the loader of each system but the both result in the very same bootloader so I believe Neon simply overwrote the one of Mint).



      I can boot into Mint just fine though. The only problem being that when I am logged in the splash screen takes way longer than before and after that I enter my desktop that now misses the start menu and the complete task bar. They're just gone. Right-clicking on my desktop doesn't do anything either.

      Although I can see all my shortcuts on the desktop, I can't click any of them (more precisely: I can click on them but nothing happens).




      EDIT:

      I have thought about this problem a bit more: When the installer formatted the boot-partition, it also deleted the installed kernels. So maybe the problem is that the KDE-Neon kernel isn't uite compatible with the Linux Mint system which causes some trouble. I'll investigate further into that...







      kde plasma toolbar






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited 2 days ago







      Raven

















      asked Mar 28 at 16:39









      RavenRaven

      259216




      259216




















          1 Answer
          1






          active

          oldest

          votes


















          0














          Your Problem was possibly caused by KDE-Neon overwriting desktop configuration files in your home directory ('/home/Your_User/.config/plasma-org.kde.plasma.desktop-appletsrc').



          When you click on the shortcuts, they refer to applet definitions like this one:



          [Containments][23][Applets][48][Configuration]
          PreloadWeight=0
          localPath=/home/me/.local/share/plasma_icons/chromium-browser.desktop
          url=file:///usr/share/applications/chromium-browser.desktop


          Your 'url=file:///' have been changed to refer to the mount point(s) of the neon partition, which doesn't exist when you load up mint.



          If you have a backup of the file from BEFORE the Neon installation, overwrite the Neon-installed changes with the old file. If you don't... you can hand-edit the file. Or, you might have to delete everything and build it new (new panels, new desktop shortcuts). Sorry! But be careful running different Distros with the same software, sharing the same home partition and directories. ALWAYS BACKUP FIRST.



          When trying a new 'live' Distro, you can also create a new UserID within /home - logging in as the new user (with empty config files). With this method, the Live Distro will write it's default config files into the new UserID, rather than overwriting your production 'User' information.



          Here is a snip of text, from Mageia's "live DVD" warning section, describing the issue with their own "Live" media versions:




          Warning!
          Create a user with a new login if you don't format a /home
          partition. User's configuration is written in user's space,
          which can overwrite some personal data. This can be the case for
          Firefox, Thunderbird, Kmail data...




          ... and this will apply to your .config settings, as well.



          You installed Neon in a separate partition (containing system root root "/", "/var", "/usr", and swap). But, as with Mageiea-Live, if it recognizes an existing /home partition and you use it, with an already-configured existing login ... it will edit and overwrite files within your Mint UserID configuration.



          Slightly OT: It seems 'unfriendly' that KDE-NEON can't "install" without destroying the GRUB2 information for other Distros... but that is a different problem from the .config over-writing.






          share|improve this answer




















          • 1





            I installed Neon im its own partition so I doubt that it has overwritten any of those config files. But I'll definitely check that. Thanks for the hint! :)

            – Raven
            Mar 29 at 8:46











          • So I tried this and it didn't do much. Neither with my backed up config files nor with removing them and letting KDE create completely fresh ones.

            – Raven
            Apr 1 at 10:58











          Your Answer








          StackExchange.ready(function()
          var channelOptions =
          tags: "".split(" "),
          id: "106"
          ;
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function()
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled)
          StackExchange.using("snippets", function()
          createEditor();
          );

          else
          createEditor();

          );

          function createEditor()
          StackExchange.prepareEditor(
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: false,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: null,
          bindNavPrevention: true,
          postfix: "",
          imageUploader:
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          ,
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          );



          );













          draft saved

          draft discarded


















          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f509267%2fkde-plasma-5-no-taskbar-no-rightclick-menu-on-desktop-either-anymore%23new-answer', 'question_page');

          );

          Post as a guest















          Required, but never shown

























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          0














          Your Problem was possibly caused by KDE-Neon overwriting desktop configuration files in your home directory ('/home/Your_User/.config/plasma-org.kde.plasma.desktop-appletsrc').



          When you click on the shortcuts, they refer to applet definitions like this one:



          [Containments][23][Applets][48][Configuration]
          PreloadWeight=0
          localPath=/home/me/.local/share/plasma_icons/chromium-browser.desktop
          url=file:///usr/share/applications/chromium-browser.desktop


          Your 'url=file:///' have been changed to refer to the mount point(s) of the neon partition, which doesn't exist when you load up mint.



          If you have a backup of the file from BEFORE the Neon installation, overwrite the Neon-installed changes with the old file. If you don't... you can hand-edit the file. Or, you might have to delete everything and build it new (new panels, new desktop shortcuts). Sorry! But be careful running different Distros with the same software, sharing the same home partition and directories. ALWAYS BACKUP FIRST.



          When trying a new 'live' Distro, you can also create a new UserID within /home - logging in as the new user (with empty config files). With this method, the Live Distro will write it's default config files into the new UserID, rather than overwriting your production 'User' information.



          Here is a snip of text, from Mageia's "live DVD" warning section, describing the issue with their own "Live" media versions:




          Warning!
          Create a user with a new login if you don't format a /home
          partition. User's configuration is written in user's space,
          which can overwrite some personal data. This can be the case for
          Firefox, Thunderbird, Kmail data...




          ... and this will apply to your .config settings, as well.



          You installed Neon in a separate partition (containing system root root "/", "/var", "/usr", and swap). But, as with Mageiea-Live, if it recognizes an existing /home partition and you use it, with an already-configured existing login ... it will edit and overwrite files within your Mint UserID configuration.



          Slightly OT: It seems 'unfriendly' that KDE-NEON can't "install" without destroying the GRUB2 information for other Distros... but that is a different problem from the .config over-writing.






          share|improve this answer




















          • 1





            I installed Neon im its own partition so I doubt that it has overwritten any of those config files. But I'll definitely check that. Thanks for the hint! :)

            – Raven
            Mar 29 at 8:46











          • So I tried this and it didn't do much. Neither with my backed up config files nor with removing them and letting KDE create completely fresh ones.

            – Raven
            Apr 1 at 10:58















          0














          Your Problem was possibly caused by KDE-Neon overwriting desktop configuration files in your home directory ('/home/Your_User/.config/plasma-org.kde.plasma.desktop-appletsrc').



          When you click on the shortcuts, they refer to applet definitions like this one:



          [Containments][23][Applets][48][Configuration]
          PreloadWeight=0
          localPath=/home/me/.local/share/plasma_icons/chromium-browser.desktop
          url=file:///usr/share/applications/chromium-browser.desktop


          Your 'url=file:///' have been changed to refer to the mount point(s) of the neon partition, which doesn't exist when you load up mint.



          If you have a backup of the file from BEFORE the Neon installation, overwrite the Neon-installed changes with the old file. If you don't... you can hand-edit the file. Or, you might have to delete everything and build it new (new panels, new desktop shortcuts). Sorry! But be careful running different Distros with the same software, sharing the same home partition and directories. ALWAYS BACKUP FIRST.



          When trying a new 'live' Distro, you can also create a new UserID within /home - logging in as the new user (with empty config files). With this method, the Live Distro will write it's default config files into the new UserID, rather than overwriting your production 'User' information.



          Here is a snip of text, from Mageia's "live DVD" warning section, describing the issue with their own "Live" media versions:




          Warning!
          Create a user with a new login if you don't format a /home
          partition. User's configuration is written in user's space,
          which can overwrite some personal data. This can be the case for
          Firefox, Thunderbird, Kmail data...




          ... and this will apply to your .config settings, as well.



          You installed Neon in a separate partition (containing system root root "/", "/var", "/usr", and swap). But, as with Mageiea-Live, if it recognizes an existing /home partition and you use it, with an already-configured existing login ... it will edit and overwrite files within your Mint UserID configuration.



          Slightly OT: It seems 'unfriendly' that KDE-NEON can't "install" without destroying the GRUB2 information for other Distros... but that is a different problem from the .config over-writing.






          share|improve this answer




















          • 1





            I installed Neon im its own partition so I doubt that it has overwritten any of those config files. But I'll definitely check that. Thanks for the hint! :)

            – Raven
            Mar 29 at 8:46











          • So I tried this and it didn't do much. Neither with my backed up config files nor with removing them and letting KDE create completely fresh ones.

            – Raven
            Apr 1 at 10:58













          0












          0








          0







          Your Problem was possibly caused by KDE-Neon overwriting desktop configuration files in your home directory ('/home/Your_User/.config/plasma-org.kde.plasma.desktop-appletsrc').



          When you click on the shortcuts, they refer to applet definitions like this one:



          [Containments][23][Applets][48][Configuration]
          PreloadWeight=0
          localPath=/home/me/.local/share/plasma_icons/chromium-browser.desktop
          url=file:///usr/share/applications/chromium-browser.desktop


          Your 'url=file:///' have been changed to refer to the mount point(s) of the neon partition, which doesn't exist when you load up mint.



          If you have a backup of the file from BEFORE the Neon installation, overwrite the Neon-installed changes with the old file. If you don't... you can hand-edit the file. Or, you might have to delete everything and build it new (new panels, new desktop shortcuts). Sorry! But be careful running different Distros with the same software, sharing the same home partition and directories. ALWAYS BACKUP FIRST.



          When trying a new 'live' Distro, you can also create a new UserID within /home - logging in as the new user (with empty config files). With this method, the Live Distro will write it's default config files into the new UserID, rather than overwriting your production 'User' information.



          Here is a snip of text, from Mageia's "live DVD" warning section, describing the issue with their own "Live" media versions:




          Warning!
          Create a user with a new login if you don't format a /home
          partition. User's configuration is written in user's space,
          which can overwrite some personal data. This can be the case for
          Firefox, Thunderbird, Kmail data...




          ... and this will apply to your .config settings, as well.



          You installed Neon in a separate partition (containing system root root "/", "/var", "/usr", and swap). But, as with Mageiea-Live, if it recognizes an existing /home partition and you use it, with an already-configured existing login ... it will edit and overwrite files within your Mint UserID configuration.



          Slightly OT: It seems 'unfriendly' that KDE-NEON can't "install" without destroying the GRUB2 information for other Distros... but that is a different problem from the .config over-writing.






          share|improve this answer















          Your Problem was possibly caused by KDE-Neon overwriting desktop configuration files in your home directory ('/home/Your_User/.config/plasma-org.kde.plasma.desktop-appletsrc').



          When you click on the shortcuts, they refer to applet definitions like this one:



          [Containments][23][Applets][48][Configuration]
          PreloadWeight=0
          localPath=/home/me/.local/share/plasma_icons/chromium-browser.desktop
          url=file:///usr/share/applications/chromium-browser.desktop


          Your 'url=file:///' have been changed to refer to the mount point(s) of the neon partition, which doesn't exist when you load up mint.



          If you have a backup of the file from BEFORE the Neon installation, overwrite the Neon-installed changes with the old file. If you don't... you can hand-edit the file. Or, you might have to delete everything and build it new (new panels, new desktop shortcuts). Sorry! But be careful running different Distros with the same software, sharing the same home partition and directories. ALWAYS BACKUP FIRST.



          When trying a new 'live' Distro, you can also create a new UserID within /home - logging in as the new user (with empty config files). With this method, the Live Distro will write it's default config files into the new UserID, rather than overwriting your production 'User' information.



          Here is a snip of text, from Mageia's "live DVD" warning section, describing the issue with their own "Live" media versions:




          Warning!
          Create a user with a new login if you don't format a /home
          partition. User's configuration is written in user's space,
          which can overwrite some personal data. This can be the case for
          Firefox, Thunderbird, Kmail data...




          ... and this will apply to your .config settings, as well.



          You installed Neon in a separate partition (containing system root root "/", "/var", "/usr", and swap). But, as with Mageiea-Live, if it recognizes an existing /home partition and you use it, with an already-configured existing login ... it will edit and overwrite files within your Mint UserID configuration.



          Slightly OT: It seems 'unfriendly' that KDE-NEON can't "install" without destroying the GRUB2 information for other Distros... but that is a different problem from the .config over-writing.







          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited Mar 30 at 19:01

























          answered Mar 29 at 4:11









          Rick StocktonRick Stockton

          1364




          1364







          • 1





            I installed Neon im its own partition so I doubt that it has overwritten any of those config files. But I'll definitely check that. Thanks for the hint! :)

            – Raven
            Mar 29 at 8:46











          • So I tried this and it didn't do much. Neither with my backed up config files nor with removing them and letting KDE create completely fresh ones.

            – Raven
            Apr 1 at 10:58












          • 1





            I installed Neon im its own partition so I doubt that it has overwritten any of those config files. But I'll definitely check that. Thanks for the hint! :)

            – Raven
            Mar 29 at 8:46











          • So I tried this and it didn't do much. Neither with my backed up config files nor with removing them and letting KDE create completely fresh ones.

            – Raven
            Apr 1 at 10:58







          1




          1





          I installed Neon im its own partition so I doubt that it has overwritten any of those config files. But I'll definitely check that. Thanks for the hint! :)

          – Raven
          Mar 29 at 8:46





          I installed Neon im its own partition so I doubt that it has overwritten any of those config files. But I'll definitely check that. Thanks for the hint! :)

          – Raven
          Mar 29 at 8:46













          So I tried this and it didn't do much. Neither with my backed up config files nor with removing them and letting KDE create completely fresh ones.

          – Raven
          Apr 1 at 10:58





          So I tried this and it didn't do much. Neither with my backed up config files nor with removing them and letting KDE create completely fresh ones.

          – Raven
          Apr 1 at 10:58

















          draft saved

          draft discarded
















































          Thanks for contributing an answer to Unix & Linux Stack Exchange!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid


          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.

          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f509267%2fkde-plasma-5-no-taskbar-no-rightclick-menu-on-desktop-either-anymore%23new-answer', 'question_page');

          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          -kde, plasma, toolbar

          Popular posts from this blog

          Frič See also Navigation menuinternal link

          Identify plant with long narrow paired leaves and reddish stems Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern) Announcing the arrival of Valued Associate #679: Cesar Manara Unicorn Meta Zoo #1: Why another podcast?What is this plant with long sharp leaves? Is it a weed?What is this 3ft high, stalky plant, with mid sized narrow leaves?What is this young shrub with opposite ovate, crenate leaves and reddish stems?What is this plant with large broad serrated leaves?Identify this upright branching weed with long leaves and reddish stemsPlease help me identify this bulbous plant with long, broad leaves and white flowersWhat is this small annual with narrow gray/green leaves and rust colored daisy-type flowers?What is this chilli plant?Does anyone know what type of chilli plant this is?Help identify this plant

          fontconfig warning: “/etc/fonts/fonts.conf”, line 100: unknown “element blank” The 2019 Stack Overflow Developer Survey Results Are In“tar: unrecognized option --warning” during 'apt-get install'How to fix Fontconfig errorHow do I figure out which font file is chosen for a system generic font alias?Why are some apt-get-installed fonts being ignored by fc-list, xfontsel, etc?Reload settings in /etc/fonts/conf.dTaking 30 seconds longer to boot after upgrade from jessie to stretchHow to match multiple font names with a single <match> element?Adding a custom font to fontconfigRemoving fonts from fontconfig <match> resultsBroken fonts after upgrading Firefox ESR to latest Firefox