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.
I have a mess with language settings. Default is English US, but in konsole, or uxterm
Code:
bash-5.1$ ls foo
ls: nie ma dostępu do 'foo': Nie ma takiego pliku ani katalogu
the output message is in Polish. I read Settings -> Regional Settings -> Formats, Region is set to Estados Unidos - espanol (en_US). I mean description is in Spanic. It is Plasma related - under Xfce bash output is in English, in virtual console is also in English.
I have a mess with language settings. Default is English US, but in konsole, or uxterm
Code:
bash-5.1$ ls foo
ls: nie ma dostępu do 'foo': Nie ma takiego pliku ani katalogu
the output message is in Polish. I read Settings -> Regional Settings -> Formats, Region is set to Estados Unidos - espanol (en_US). I mean description is in Spanic. It is Plasma related - under Xfce bash output is in English, in virtual console is also in English.
I'm running plasma 5.21.1 / slackware-current
Plasma X11 show taskbar tooltips correctly
But, under plasma_wayland session, they are all blank
Cf: capture
In .local/share/ssdm/wayland-session.log, I have :
Code:
kf.plasma.quick: Couldn't create KWindowShadow for ToolTipDialog(0x5942640)
kf.plasma.quick: Couldn't create KWindowShadow for ToolTipDialog(0x5942640)
kf.plasma.quick: Couldn't create KWindowShadow for ToolTipDialog(0x5942640)
And, on mouse-over :
Code:
kwin_screencast: Failed to connect PipeWire context
error creating screencast "Failed to connect PipeWire context"
kwin_screencast: Failed to connect PipeWire context
kwin_screencast: Failed to connect PipeWire context
Anyone experiencing the same problem ?
EDIT : afterthought, probably not the best place to post. Sorry for that.
I'm running plasma 5.21.1 / slackware-current
Plasma X11 show taskbar tooltips correctly
But, under plasma_wayland session, they are all blank
Cf: capture
In .local/share/ssdm/wayland-session.log, I have :
Code:
kf.plasma.quick: Couldn't create KWindowShadow for ToolTipDialog(0x5942640)
kf.plasma.quick: Couldn't create KWindowShadow for ToolTipDialog(0x5942640)
kf.plasma.quick: Couldn't create KWindowShadow for ToolTipDialog(0x5942640)
And, on mouse-over :
Code:
kwin_screencast: Failed to connect PipeWire context
error creating screencast "Failed to connect PipeWire context"
kwin_screencast: Failed to connect PipeWire context
kwin_screencast: Failed to connect PipeWire context
Anyone experiencing the same problem ?
This happens because you do not run the PipeWire audio/video server, as Slackware -current just added it as hard dependency of Wayland/Plasma5, with no startup setup at all.
Fortunately, the PipeWire is well packaged, just like other packages made by Mr. Volkerding.
There is how I've setup the PipeWire server:
To start the PipeWire on desktop login, you should create a file named: /etc/xdg/autostart/pipewire.desktop
With this content:
Code:
[Desktop Entry]
Version=1.0
Name=PipeWire Media System
Comment=Start the PipeWire Media System
Exec=pipewire
Terminal=false
Type=Application
X-GNOME-Autostart-Phase=Initialization
X-KDE-autostart-phase=1
But unlike PulseAudio, the Pipewire server does not know how to quit itself on user logout, because it is supposed to be run by systemd as "user target service". So you will end with hanged up instances on user logout.
The simplest way to fix this is to instruct elogind to kill all user processes on logout, make a change on /etc/elogind/logind.conf
Code:
KillUserProcesses=yes
There's a caveat on this setup of elogind and that's why it is not active by default on Slackware: all user processes being killed, also applications like screen or tmux will be killed, so no way to keep them alive when login remote then logout.
So, if you intend also to run screen from a remote login session to your box, probably is better to have a separate account for this, then to instruct appropiately the elogind to behave for this user.
Honestly, those things was first explained by @LuckyCyborg, eventually you can ask him more details, but that's all what I did to have a proper setup of PipeWire with the note that I do not use screen or tmux, as my box is just for entertainment.
PS. Looks like that in the near future we will have a way to avoid that "kill mode" on elogind setup, by using a daemon supervisor which will know to quit itself and its client, on user logout
The developer aggreed to add this feature, and when it will be ready, we will have a good way to make PipeWire or other "user target daemons" to behave on Slackware, just like PulseAudio.
Last edited by ZhaoLin1457; 02-27-2021 at 09:50 AM.
Fortunately, the PipeWire is well packaged, just like other packages made by Mr. Volkerding.
Here I do want to chime in that the pipewire SlackBuild is mine originally (part of 'ktown' Plasma5) and adopted by Pat into slackware-current... but it really is not that much of an issue since this is almost a template SlackBuild script, no customizations were needed. Anyone could have written it. The interesting/challenging parts would have been an integration into the OS as a/v server which starts when the user logs into a graphical session and stops on logoff.
The way Dolphin sorts (or doesn't) files is killing me. My preferences are set to sort files by name. Every time I open a new directory files are sorted by created date. So I click sort alphabetically. The default for that is Z-A for some reason so again another click to sort by A-Z. Any decent alternatives to this thing?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
