LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   Requests for -current (14.2-->15.0) (https://www.linuxquestions.org/questions/slackware-14/requests-for-current-14-2-15-0-a-4175620463/)

ZhaoLin1457 06-22-2018 04:28 AM

Quote:

Originally Posted by RadicalDreamer (Post 5870453)
I don't think so. I had an issue with qt5-5.9.6 so I went back to qt5-5.9.5. Is it this past update or all updates for you?

This issue manifests since at least several versions, I do not remember right when it appeared first.

In fact, there are two issue. The KWin crashes its effects with no aparent reason and that icons getting lost. Roughly similar with what Darth Vader describe.

That happens in the system with Radeon video, within the Intel one Plasma5 works fine.

RadicalDreamer 06-22-2018 04:32 AM

Quote:

Originally Posted by ZhaoLin1457 (Post 5870456)
This issue manifest since at least several versions, I do not remember right when it appeared first.

In fact, there are two issue. The KWin crashes its effects and that icons getting lost. Roughly similar with what Darth Vader describe.

That happens in the system with Radeon video, within the Intel one Plasma5 works fine.

Have you tried turning off the effects? I disabled the compositor because it didn't play nice with NVIDIA and OpenGL full screen applications.

ZhaoLin1457 06-22-2018 04:36 AM

Quote:

Originally Posted by RadicalDreamer (Post 5870459)
Have you tried turning off the effects? I disabled the compositor because it didn't play nice with NVIDIA and OpenGL full screen applications.

I tried that, with the effect turned off there is no KWin effects crashing, but still appears the icons issue.

However, without the effects, I feel that the deskop behave very bad and with a lot of tears.

So I keep them on, with OpenGL 2.0, because with the 3.1 the issues appears often and XRender is really slow.

RadicalDreamer 06-22-2018 04:44 AM

Quote:

Originally Posted by ZhaoLin1457 (Post 5870462)
I tried that, with the effect turned off there is no KWin effects crashing, but still appears the icons issue.

However, without the effects, I feel that the deskop behave very bad and with a lot of tears.

So I keep them on, with OpenGL 2.0, because with the 3.1 the issues appears often and XRender is really slow.

Maybe try
Quote:

XV_VSYNC is used to control whether textured adapter synchronizes the screen update to the monitor vertical refresh to eliminate tearing. It has two values: 'off'(0) and 'on'(1). The default is 'on'(1).
https://linux.die.net/man/4/radeon

gmgf 06-22-2018 04:45 AM

dialog-1.3-20180621:

ftp://ftp.invisible-island.net/dialo...3-20180621.tgz

ZhaoLin1457 06-22-2018 05:20 AM

Quote:

Originally Posted by RadicalDreamer (Post 5870464)
Maybe try
Code:

XV_VSYNC is used to control whether textured adapter synchronizes the screen update to the monitor vertical refresh to eliminate tearing. It has two values: 'off'(0) and 'on'(1). The default is 'on'(1).
https://linux.die.net/man/4/radeon

This one is for textured video, then has effects only while using Xv as output driver on MPlayer, as example.

gmgf 06-22-2018 07:09 AM

nss-3.37.3:

https://ftp.mozilla.org/pub/security...-3.37.3.tar.gz

RadicalDreamer 06-22-2018 07:21 AM

Quote:

Originally Posted by ZhaoLin1457 (Post 5870470)
This one is for textured video, then has effects only while using Xv as output driver on MPlayer, as example.

NVIDIA provides compositing. I don't know about the Radeon driver. Before people rage at me I'm going to stop derailing this thread. I don't like the KDE compositor myself. Maybe look for a different one like this one if the Radeon driver can't do it: https://slackbuilds.org/repository/1.../compton-conf/

dugan 06-22-2018 11:33 AM

Quote:

Originally Posted by Darth Vader (Post 5870414)
Did you guys really believe that Plasma5 is ready for the inclusion in Slackware? :D

I do, yeah.

And if your video card can't handle it? That's why Slackware also ships Xfce.

upnort 06-24-2018 11:52 AM

XDG_RUNTIME_DIR and /var/run in tmpfs
 
By default the $XDG_RUNTIME_DIR environment variable is not set in Slackware, nor is /var/run sym linked to /run.

With many other distros the $XDG_RUNTIME_DIR defaults to /run/user/$UID. In many distros, /var/run is a sym link to /run. Both Slackware and most other distros mount /run to tmpfs, but Slackware does not create the /var/run sym link or create a default $XDG_RUNTIME_DIR variable. Using a sym link and tmpfs creates a nice way to clean the directory on reboot.

The sym link could be created in rc.S. The variable could be set in /etc/profile.d with:

Code:

if [ ! -d /run/user/$UID ]; then
  mkdir -p /run/user/$UID
fi
export XDG_RUNTIME_DIR=/run/user/$UID

Possibly some people would want /var/run fixed rather than use tmpfs. Perhaps rc.S could source /etc/default/var_run to determine whether to create the sym link.

Code:

/etc/default/var_run
VAR_RUN_IN_TMPFS=true

Just a proposal. :)

Markus Wiesner 06-24-2018 12:08 PM

Quote:

Originally Posted by upnort (Post 5871392)
With many other distros the $XDG_RUNTIME_DIR defaults to /run/user/$UID. In many distros, /var/run is a sym link to /run. Both Slackware and most other distros mount /run to tmpfs, but Slackware does not create the /var/run sym link or create a default $XDG_RUNTIME_DIR variable. Using a sym link and tmpfs creates a nice way to clean the directory on reboot.

There are several packages with subdirectories in /var/run. Those directories would be lost with tmpfs, so all of these packages would need to be adapted so that their start script recreates the directories with the necessary access rights.

elcore 06-24-2018 12:37 PM

It defaults to /tmp/runtime-user if not set, no idea why would one write it somewhere other than /tmp.
I usually mount tmpfs as /tmp, and TBH I'd prefer not to write and re-write runtime on ssd.

gmgf 06-24-2018 12:49 PM

qpdf-8.1.0:

http://qpdf.sourceforge.net/files/qp....release-notes
https://github.com/qpdf/qpdf/releases
https://github.com/qpdf/qpdf/release...f-8.1.0.tar.gz

sip-4.19.10:

https://www.riverbankcomputing.com/s.../sip/ChangeLog
https://sourceforge.net/projects/pyq...4.19.10.tar.gz

stunnel-5.47:

https://www.stunnel.org/sdf_ChangeLog.html
https://www.stunnel.org/downloads/stunnel-5.47.tar.gz

upnort 06-24-2018 01:49 PM

Quote:

There are several packages with subdirectories in /var/run. Those directories would be lost with tmpfs, so all of these packages would need to be adapted so that their start script recreates the directories with the necessary access rights.
I have been using /var/run sym-linked to /run for a couple of years or more. While possible, I have not encountered such issues. On my Slackware systems, everything is repopulated with each boot. Unlike /var/tmp, I don't believe /var/run is intended to be a persistent storage location. Additionally, rc.S scrubs /var/run: rm -f /var/run/* /var/run/*/* /var/run/*/*/*.

olear 06-24-2018 02:08 PM

Quote:

Originally Posted by upnort (Post 5871392)
By default the $XDG_RUNTIME_DIR environment variable is not set in Slackware

XDG_RUNTIME_DIR is usually set by your desktop environment. If you don't have it add it to your X startup file, or something. It should not be set in profile.d.


All times are GMT -5. The time now is 05:47 AM.