Fresh Install Problems in Plasma

I just performed a fresh install with the latest ISO about a week ago now, and I have a small list of problems I can’t seem to locate solutions for. Anyone able to help me out with some or all of these? Please go easy on me, still learning Linux as a whole.

Setup details:
Lenovo E490 with Lenovo Dock, connected to External 32" Display over DisplayPort

  1. Panel(s) do not load upon fresh boot
  • Happens with any themes including default
  • Can restore using a script I built to kill plasmashell and restart
  • Tried placing this script in Settings > Autostart but does not work at login
    – ** Seems to only happen when connected to external display **
  1. Konsole only loads default color profile
  • Have created my own color profile, but does not load by default (setting somewhere?)

Have you tried it without the Dock?

1 Like

Yep, I edited the post after testing off dock.

Do you mean this is above is edited? Because below makes me think it’s connected to the dock.

Sorry, perhaps I was not clear enough. I have removed the laptop from the dock to test (after posting) and was confirming that yes, undocked the desktop panels load fine. It appears to be related to when I have an external display connected. I have also tried to enable both laptop and external displays and rebooted only to have the same missing panel effect.

I think there may be a way to script this into a solution but I am not smart enough to do so. Maybe I should simply alter my routine and boot up un-docked, then connect and see what happens. Idk.

I am due to get my new Surface Laptop 4 soon, scared to try and dual boot with it (EndeavorOS and Win10/Win11).

Why? EndeavourOS and Windows is no issue.

I heard Surface products have a lot of… “fun” issues loooool

In a few weeks when it arrives, I’m sure I’ll be posting a ton lol.

I’m sure it does. :wink: It’s tuned to run Windows I’m sure.

My t480s does not work well at all coming from a full shut down while on the dock on kde either. It’s fine from hibernation or sleep, but I also need to do the initial start up off the dock for some reason. I never really looked into it since it was easy enough to just do. And realistically I rarely have my computer cold. It’s almost always asleep or in hibernate.

Hi Zamostny,

I’m using a Lenovo dock with my T450 with Gnome with no issue. Its not a fair comparison because your E490 uses either a USB-C or Thunderbolt dock which is a different technology then my laptops.

I was wondering if you could look at the below article and let us know which specific Lenovo dock you are using.

https://pcsupport.lenovo.com/ca/en/products/laptops-and-netbooks/thinkpad-edge-laptops/thinkpad-e490-type-20n8-20n9/solutions/ht504806-docks-and-docking-stations-solution-links

Additionally I am assuming you are using Windows 10 (dual boot). Did you install the Lenovo Vantage software and make sure your laptop and docking station have the latest firmware?

Thanks.

So, the dock I am using is the USB C Gen 2. I am not dual booting with Windows (though the next laptop will be if I can pull it off). This one just has ArchCraft on another partition.

The display issue is def related to being connected to the dock. The panels load just fine if I am only on the laptop display. My script to kill and restart works well enough - however, I haven’t gotten the disown command to work correctly - causing me to kill the terminal session while tasks are still being executed.

As for the Konsole color thing, I finally located some documentation to address this and all is well there.

I actually purchased a very specific NVME drive to go into my WWLAN slot on my 480. So I have Windows on that 256GB drive and Arch on my 1TB NVME in the normal slot and dual boot using the boot manager.

1 Like

So, I figured I would post the log that generates after I run this script to correct the Plasma panel issue I have been dealing with - hoping someone sees something that leads to a fix. If not, any tips on getting this script to run automatically upon log in would be helpful. It wont run when I put it in the Settings > Startup and Shutdown > Autostart

Here is the output after launching the script manually.

🕙 07:01:14 ❯❯❯ cd Documents/```

```~/Documents 
🕙 07:01:20 ❯❯❯ bash plasma_fix.sh ```

```~/Documents 
🕙 07:01:24 ❯❯❯ Icon theme "gnome" not found.
kf.plasma.quick: Applet preload policy set to 1
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
trying to show an empty dialog
trying to show an empty dialog
file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:134:19: QML Loader: Binding loop detected for property "height"
file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:134:19: QML Loader: Binding loop detected for property "height"
Plasma Shell startup completed
kf.service.services: Parsing "exist Exec and ('/usr/bin/yad --window-icon=/usr/share/endeavouros/EndeavourOS-icon.png --notebook --key=886720 --center --title=Welcome v3.16.9-1 --use-interp --expand --tab=General Info --tab=After Install --tab=Assistant --tab=Tips --tab=Add More Apps --active-tab=2 --button= Software News!applications-development!Important news about EndeavourOS software:ImportantNews --button= Changelog!applications-development!Show the changelog of Welcome:WelcomeChangelog --button= Don't show me anymore!face-crying!Don't show me anymore:5 --button= Help!help-contents!:WelcomeHelp' =~ Exec)" gave: syntax error
kf.service.services: Parsing "exist Exec and ('yad --window-icon=/usr/share/endeavouros/EndeavourOS-icon.png --notebook --key=886720 --center --title=Welcome v3.16.9-1 --use-interp --expand --tab=General Info --tab=After Install --tab=Assistant --tab=Tips --tab=Add More Apps --active-tab=2 --button= Software News!applications-development!Important news about EndeavourOS software:ImportantNews --button= Changelog!applications-development!Show the changelog of Welcome:WelcomeChangelog --button= Don't show me anymore!face-crying!Don't show me anymore:5 --button= Help!help-contents!:WelcomeHelp' =~ Exec)" gave: syntax error
file:///usr/share/plasma/plasmoids/org.kde.plasma.panelspacer/contents/ui/main.qml:39:5: Unable to assign [undefined] to QQuickGridLayout*
file:///usr/share/plasma/plasmoids/org.kde.plasma.panelspacer/contents/ui/main.qml:39:5: Unable to assign [undefined] to QQuickGridLayout*
file:///usr/share/plasma/plasmoids/org.kde.plasma.digitalclock/contents/ui/DigitalClock.qml:520:9: QML Label: Binding loop detected for property "height"
file:///usr/share/plasma/plasmoids/org.kde.plasma.digitalclock/contents/ui/DigitalClock.qml:475:13: QML Label: Binding loop detected for property "height"
trying to show an empty dialog
file:///usr/share/plasma/plasmoids/org.kde.panel/contents/ui/main.qml:18:1: QML DropArea (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "minimumWidth"
file:///usr/share/plasma/plasmoids/org.kde.plasma.digitalclock/contents/ui/DigitalClock.qml:475:13: QML Label: Binding loop detected for property "height"
file:///usr/share/plasma/plasmoids/org.kde.plasma.digitalclock/contents/ui/DigitalClock.qml:520:9: QML Label: Binding loop detected for property "height"
file:///usr/share/plasma/plasmoids/org.kde.plasma.digitalclock/contents/ui/DigitalClock.qml:542:5: QML Label: Binding loop detected for property "height"
trying to show an empty dialog
file:///usr/share/plasma/plasmoids/org.kde.panel/contents/ui/main.qml:18:1: QML DropArea (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "minimumWidth"
trying to show an empty dialog
file:///usr/share/plasma/plasmoids/org.kde.panel/contents/ui/main.qml:18:1: QML DropArea (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "minimumWidth"
libkcups: CUPS-Get-Printers last error: 0 successful-ok
libkcups: Create-Printer-Subscriptions last error: 0 successful-ok
libkcups: Get-Jobs last error: 0 successful-ok
libkcups: Get-Jobs last error: 0 successful-ok
Cyclic dependency detected between "file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml" and "file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationHeader.qml"
libkcups: 3 "PB650"
libkcups: 0
libkcups: 0
trying to show an empty dialog
file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:134:19: QML Loader: Binding loop detected for property "height"
file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:134:19: QML Loader: Binding loop detected for property "height"
trying to show an empty dialog
trying to show an empty dialog
file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:134:19: QML Loader: Binding loop detected for property "height"
file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:134:19: QML Loader: Binding loop detected for property "height"
trying to show an empty dialog
file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:134:19: QML Loader: Binding loop detected for property "height"
file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:134:19: QML Loader: Binding loop detected for property "height"
QFont::setPointSizeF: Point size <= 0 (0.000000), must be greater than 0
Trying to take space not available BasicAppletContainer_QMLTYPE_180(0x561198d05fd0, parent=0x561198be1130, geometry=2432,1360 128x64)
trying to show an empty dialog
trying to show an empty dialog
Both point size and pixel size set. Using pixel size.
trying to show an empty dialog```

Can you please format this output with code tags to make it readable.

```
text
```

Or just run this from yakuake and copy the output

killall plasmashell; kstart5 plasmashell&

Any other errors reported?

journalctl -p err -b

What does this mean? Is the panel visible but empty or missing altogether?

When panels fail to load it can be plasmoid related.

ls -al ~/.local/share/plasma/plasmoids/

If you remove your panels and replace them with minmal new ones does the problem persist?

So no issues directly after fresh install?

What did you do between fresh install and breakage?

Is it only your personal color profile that fails to load? If you select another or download a new color profile it is not saved?

If so start konsole from a konsole and see if any error messages are triggered.

1 Like

I have edited the post as requested (sorry about that, kinda new here).

This started right after the fresh install and connected to the docking station using an external display. This does not happen when I am not connected to another display and simply just laptop screen alone.

The panels do not load at all, just the eos welcome app and a wallpaper. Problem does persist if I remove my panels and replace with default.

The Konsole issue has been sorted out.

Output for plasmoids:

🕙 07:34:37 ❯❯❯ ls -al ~/.local/share/plasma/plasmoids/
total 20
drwxr-xr-x 5 jerry jerry 4096 Nov  1 14:27 .
drwxr-xr-x 5 jerry jerry 4096 Nov  1 14:27 ..
drwxr-xr-x 3 jerry jerry 4096 Nov  1 14:27 launchpadPlasma
drwxr-xr-x 3 jerry jerry 4096 Nov  1 14:27 org.kde.plasma.splitdigitalclock
drwxr-xr-x 3 jerry jerry 4096 Nov  1 14:27 SimplePager

~ 
🕙 07:34:54 ❯❯❯ ```

So this is a dock external display only issue.

Is the dock display port treated as a separate display?

Run this command with laptop screen only and dock external display?

xrandr

Also check your Settings → Display & Monitor → Display Configuration setup in both instances.

inxi -G

Also, are there any journal errors on boot?

1 Like

Journal output:

-- Journal begins at Fri 2021-10-22 09:03:37 EDT, ends at Fri 2021-11-05 08:07:33 EDT. --
Nov 05 07:00:31 endeavor kernel: ucsi_acpi USBC000:00: con1: failed to register alternate modes
Nov 05 07:00:31 endeavor kernel: Bluetooth: hci0: command 0xfc01 tx timeout
Nov 05 07:00:39 endeavor kernel: Bluetooth: hci0: FW download error recovery failed (-110)
Nov 05 07:00:40 endeavor kernel: usb 1-2.3.2: 1:1: cannot set freq 48000 to ep 0x3
Nov 05 07:00:40 endeavor kernel: usb 1-2.3.3.3.1: 3:1: cannot get freq at ep 0x84
Nov 05 07:01:10 endeavor kernel: usb 1-2.3.3.3.1: 3:1: cannot get freq at ep 0x84
Nov 05 07:01:10 endeavor kernel: usb 1-2.3.3.3.1: 3:1: cannot get freq at ep 0x84
Nov 05 07:19:47 endeavor pulseaudio[1447]: ALSA woke us up to write new data to the device, but there>
Nov 05 07:19:47 endeavor pulseaudio[1447]: Most likely this is a bug in the ALSA driver 'snd_usb_audi>
Nov 05 07:19:47 endeavor pulseaudio[1447]: We were woken up with POLLOUT set -- however a subsequent >


~  took 15s
🕙 08:07:51 ❯❯❯ 

xrandr output:

Screen 0: minimum 8 x 8, current 2560 x 1440, maximum 32767 x 32767
eDP1 connected (normal left inverted right x axis y axis)
   1920x1080     60.01 +  59.93  
   1680x1050     59.88  
   1400x1050     59.98  
   1600x900      60.00    59.95    59.82  
   1280x1024     60.02  
   1400x900      59.96    59.88  
   1280x960      60.00  
   1368x768      60.00    59.88    59.85  
   1280x800      59.81    59.91  
   1280x720      59.86    60.00    59.74  
   1024x768      60.00  
   1024x576      60.00    59.90    59.82  
   960x540       60.00    59.63    59.82  
   800x600       60.32    56.25  
   864x486       60.00    59.92    59.57  
   640x480       59.94  
   720x405       59.51    60.00    58.99  
   640x360       59.84    59.32    60.00  
DP1 disconnected (normal left inverted right x axis y axis)
DP1-1 disconnected (normal left inverted right x axis y axis)
DP1-2 connected primary 2560x1440+0+0 (normal left inverted right x axis y axis) 700mm x 390mm
   2560x1440     59.95*+  74.93  
   1920x1440     75.00    60.00  
   2560x1080     60.00    59.94    50.00  
   1856x1392     75.00    60.00  
   1792x1344     75.00    60.00  
   2048x1152     60.00  
   1920x1200     74.93    59.88  
   1920x1080     60.00    50.00    59.94  
   1600x1200     75.00    70.00    65.00    60.00  
   1680x1050     74.89    59.95  
   1680x945      60.02  
   1400x1050     74.87    59.98  
   1600x900      60.00  
   1280x1024     75.02    60.02  
   1440x900      74.98    59.89  
   1280x960      60.00  
   1366x768      59.79  
   1360x768      60.02  
   1280x800      74.93    59.81  
   1152x864      75.00  
   1280x768      74.89    59.87  
   1280x720      60.00    50.00    59.94  
   1440x576      50.00  
   1024x768      75.03    70.07    60.00  
   1440x480      60.00    59.94  
   1024x576      59.97  
   832x624       74.55  
   800x600       72.19    75.00    60.32    56.25  
   720x576       50.00  
   848x480       60.00  
   720x480       60.00    59.94  
   640x480       75.00    72.81    66.67    60.00    59.94  
   720x400       70.08  
DP1-3 disconnected (normal left inverted right x axis y axis)
HDMI1 disconnected (normal left inverted right x axis y axis)
HDMI2 disconnected (normal left inverted right x axis y axis)
VIRTUAL1 disconnected (normal left inverted right x axis y axis)

Dunno.

Panels work fine with the laptop screen display, but when docked the display auto switch to the external monitor crashes panels initially.

On reboot are you restoring a previous session or starting a new one?

You could try replacing your panel with latte-dock and see if the issue is isolated to the panel only.

KDE should handle ThinkPad docks OOTB.

1 Like

@otherbarry

I am set to start an empty session, did not change this setting.

I may have to give latte-dock a try then.

A manual plasmashell restart post boot works fine, but plasmashell starting during boot process doesn’t. Weird race condition-ish type behavior. PITA to diagnose.

Maybe try the KDE forum, or create a bug on KDE bugtracker … but that may gather dust. Arch forum could maybe help as last resort, but if they sniff out a EOS install you’ll probably be insta-banned.

If it were me I’d rule out silly stuff, like changing dock DP ports and / or using the HDMI ports instead. Try re-installing KDE again whilst docked. Try latte-dock.

If this is a deal breaker you coud also try Gnome (:scream_cat:) , they supposedly have good ThinkPad dock support OOTB.