SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
After upgrading to kde Plasma 5.23.0, thumbnails of open applications at the bottom of the taskbar no longer appear in a Wayland session.
same behavior here (even with 5.23.1 / pipewire)
I cannot confirm this.
Yesterday, even I did an update to an external USB hard drive who still remained on Plasma 5.22.5 and thumbnails worked both before and after upgrading to latest packages set.
However, please bear in mind that a proper setup of PipeWire daemons is fundamental on Wayland/Plasma5, for working various features starting from taskbar thumbnails and ending with desktop sharing and VNC connections.
They aren't "optional" so there's no such thing like an "even" word.
Personally, I use a full PipeWire setup, including even the usage as PulseAudio server.
Last edited by ZhaoLin1457; 10-24-2021 at 12:02 PM.
Yesterday, even I did an update to an external USB hard drive who still remained on Plasma 5.22.5 and thumbnails worked both before and after upgrading to latest packages set.
However, please bear in mind that a proper setup of PipeWire daemons is fundamental on Wayland/Plasma5, for working various features starting from taskbar thumbnails and ending with desktop sharing and VNC connections.
They aren't "optional" so there's no such thing like an "even" word.
Personally, I use a full PipeWire setup, including even the usage as PulseAudio server.
yep
that's why I mentioned it : even with 5.23.1 / pipewire
in .local/share/sddm/wayland-session.log
on mouse over in the taskbar
Code:
kf.plasma.quick: Couldn't create KWindowShadow for ToolTipDialog(0x23e4230)
I do not think that this message from log is meaningful, because it's present also in my log, and the thumbnails works fine.
Code:
file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/ToolTipDelegate.qml:0: ReferenceError: AppPid is not defined
file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/ToolTipDelegate.qml:0: ReferenceError: AppPid is not defined
kf.plasma.quick: Couldn't create KWindowShadow for ToolTipDialog(0x5671af0)
kf.plasma.quick: Couldn't create KWindowShadow for ToolTipDialog(0x5671af0)
kf.plasma.quick: Couldn't create KWindowShadow for ToolTipDialog(0x5671af0)
file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/ToolTipDelegate.qml:0: ReferenceError: AppPid is not defined
file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/ToolTipDelegate.qml:0: ReferenceError: AppPid is not defined
Please triple check your PipeWire daemons setup, if everything works, you should be able to use it as audio server.
And, from my experience, the PipeWire works only with a KMS framebuffer, nothing else - e.g. no VESA or EFI framebuffer will work.
Also, did you remember the user who tried to create a VNC connection to a Wayland/Plasma5 session, which also needs a proper running PipeWire?
In the final he found that the issue/failure was generated by using the a non KMS graphics, e.g. with "nomodeset" parameter on kernel command line.
Last edited by ZhaoLin1457; 10-24-2021 at 12:57 PM.
I do not think that this message from log is meaningful, because it's present also in my log, and the thumbnails works fine.
Code:
file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/ToolTipDelegate.qml:0: ReferenceError: AppPid is not defined
file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/ToolTipDelegate.qml:0: ReferenceError: AppPid is not defined
kf.plasma.quick: Couldn't create KWindowShadow for ToolTipDialog(0x5671af0)
kf.plasma.quick: Couldn't create KWindowShadow for ToolTipDialog(0x5671af0)
kf.plasma.quick: Couldn't create KWindowShadow for ToolTipDialog(0x5671af0)
file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/ToolTipDelegate.qml:0: ReferenceError: AppPid is not defined
file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/ToolTipDelegate.qml:0: ReferenceError: AppPid is not defined
Please triple check your PipeWire daemons setup, if everything works, you should be able to use it as audio server.
And, from my experience, the PipeWire works only with a KMS framebuffer, nothing else - e.g. no VESA or EFI framebuffer will work.
Monsieur Marav, how about to tell us more about your graphics card setup?
Like Zhao Lin said already, unfortunately, the video side of PipeWire works only with the KMS framebuffer, even the Wayland itself manage to work on various other setups, so I am very curious to know full details about your graphics.
Secondly, please verify to have NOTHING on /etc/pipewire folder. No files, no directories, NOTHING. IF you found something, please remove everything and reboot.
Last edited by LuckyCyborg; 10-24-2021 at 01:39 PM.
Monsieur Marav, how about to tell us more about your graphics card setup?
Like Zhao Lin said already, unfortunately, the video side of PipeWire works only with the KMS framebuffer, even the Wayland itself manage to work on various other setups, so I am very curious to know full details about your graphics.
First, I have to mention that thumbnails / wayland works well with plasma 5.22.5
Took a look at that post and tried, again, to install pipewire and had the same negative result. This time it didn't even make any system sounds. Zip. It doesn't work, for whatever reason. I'm not going to fiddle with it again, so no response is necessary.
Took a look at that post and tried, again, to install pipewire and had the same negative result. This time it didn't even make any system sounds. Zip. It doesn't work, for whatever reason. I'm not going to fiddle with it again, so no response is necessary.
Pipewire just doesn't like you, that's all
Here, I have no problem since the beginning :
audio ok, bluetooth ok and - not a big deal, I can live without - thumbnails in the taskbar (ok with 5.22.5 but not with 5.23.x).
I am still getting the same behavior, I created another --Current iso , which includes Saturday's update (10/23/2021). I did another FULL install - nothing excluded not even akonadi. I changed inittab to 4, and chose one of the default (stock), login screens under SDDM(I chose the Maya theme):
Rebooted, and instead of the login screen it is a black screen until I randomly click - then I get the screen to type in my user name and password - and right before I do; the stupid soft-keyboard comes up again, why? :
So with or without akonadi, this behavior occurs. If it means anything I am also running with the VBox guest additions, but I do not see how that should affect it.
-edit
Oh, and the virtual keyboard always popups when I switch from username to password and get ready to type, and I always have to click on the keyboard icon to the lower right (where the smiley face is to the left of it), just to get the ability to type with my actual keyboard.... again, WHY does this even occur?
Distribution: Slackware64 15.0 (started with 13.37). Testing -current in a spare partition.
Posts: 934
Rep:
Quote:
Originally Posted by Jeebizz
I am still getting the same behavior, I created another --Current iso , which includes Saturday's update (10/23/2021). I did another FULL install - nothing excluded not even akonadi. I changed inittab to 4, and chose one of the default (stock), login screens under SDDM(I chose the Maya theme):
Rebooted, and instead of the login screen it is a black screen until I randomly click - then I get the screen to type in my user name and password - and right before I do; the stupid soft-keyboard comes up again, why? :
So with or without akonadi, this behavior occurs. If it means anything I am also running with the VBox guest additions, but I do not see how that should affect it.
-edit
Oh, and the virtual keyboard always popups when I switch from username to password and get ready to type, and I always have to click on the keyboard icon to the lower right (where the smiley face is to the left of it), just to get the ability to type with my actual keyboard.... again, WHY does this even occur?
I didn't test it, but according to "man sddm.conf" it is the "InputMethod" option in "/etc/sddm.conf".
Code:
OPTIONS
[General] section:
HaltCommand=
Halt command. Default value is "/usr/bin/loginctl poweroff".
RebootCommand=
Reboot command. Default value is "/usr/bin/loginctl reboot".
Numlock=
Change numlock state when sddm-greeter starts. Valid values are
on, off or none. If property is set to none, numlock won't be
changed. Default value is "none".
InputMethod=
Set the Qt input method for the greeter. Tablet users with Qt
Virtual Keyboard installed can set this to "qtvirtualkeyboard"
for the on-screen keyboard. Other known values are "ibus" for
the Intelligent Input Bus, or "compose" for dead keys support.
Leave this empty if unsure.
I didn't test it, but according to "man sddm.conf" it is the "InputMethod" option in "/etc/sddm.conf".
Code:
OPTIONS
[General] section:
HaltCommand=
Halt command. Default value is "/usr/bin/loginctl poweroff".
RebootCommand=
Reboot command. Default value is "/usr/bin/loginctl reboot".
Numlock=
Change numlock state when sddm-greeter starts. Valid values are
on, off or none. If property is set to none, numlock won't be
changed. Default value is "none".
InputMethod=
Set the Qt input method for the greeter. Tablet users with Qt
Virtual Keyboard installed can set this to "qtvirtualkeyboard"
for the on-screen keyboard. Other known values are "ibus" for
the Intelligent Input Bus, or "compose" for dead keys support.
Leave this empty if unsure.
Are those the only option? I want to only use a REAL keyboard, I am not running a tablet, nor do I have touchscreen either. What value is there for just a regular keyboard?
-edit
Since akonadi has no bearing on this, I am going continue to exclude it from now own like I have always done. It would be nice if I can lose the virtual keyboard (whatever package that it is under), but I fear KDE will probably have some kind of fit anyways, so I won't bother - I just want to know what option do I use in InputMethod= , to only default to a real keyboard, thus preventing the soft-keyboard from ever interfering.
Distribution: Slackware64 15.0 (started with 13.37). Testing -current in a spare partition.
Posts: 934
Rep:
Quote:
Originally Posted by Jeebizz
Are those the only option? I want to only use a REAL keyboard, I am not running a tablet, nor do I have touchscreen either. What value is there for just a regular keyboard?
-edit
Since akonadi has no bearing on this, I am going continue to exclude it from now own like I have always done. It would be nice if I can lose the virtual keyboard (whatever package that it is under), but I fear KDE will probably have some kind of fit anyways, so I won't bother - I just want to know what option do I use in InputMethod= , to only default to a real keyboard, thus preventing the soft-keyboard from ever interfering.
I think you could test it editing the file /etc/sddm.conf and change the line
Alright! ok, that solved it - question is why is then set to qtvirtualkeyboard in the first place?
It's not set on every SDDM theme, just a few of them. This is likely because KDE does not want to be left out of the touchscreen user crowd, including future smartphones. That way, just selecting an appropriate theme is already setup for the keyboard and mouse impaired.
It's not set on every SDDM theme, just a few of them. This is likely because KDE does not want to be left out of the touchscreen user crowd, including future smartphones. That way, just selecting an appropriate theme is already setup for the keyboard and mouse impaired.
So if I understand your statement correctly, each theme I would have to check sddm.conf in /etc to make sure that option is not there or modify it accordingly?
Then again I am forced to deal with touchscreen on hp laptops, even though I just don't want it - would be nice if the manufacturers would let you to just disable it via bios/uefi and never have to deal with it ever again; but thats neither here nor there.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
stupid virtual/soft-keyboard
