Page 1 of 4

Slint64-14.2.1rc2, last call for testing.

Posted: 11. Nov 2017, 13:11
by DidierSpaier
Last call means "all bug reports and comments posted before Monday 20 November 2017 will be looked at before the official release."

The ISO is here:
http://slackware.uk/slint/x86_64/slint-testing/iso/

Most prominent change since the first release candidate: lightdm replaces lxdm as display manager.

This allows to make Slint fully accessible with speech and braille, now also at runlevel 4, i.e. starting directly a graphical environment after log in.

Some KDE apps like lokalize (not the KDE desktop itself) are now also accessible.

On the other hand installing KDE is now optional.

emacspeak as speechd-el are included, so emacs has now three ways to speak, including espeakup. You may use all three at the same time, if you don't fear cacophony...

A documentation for each package is installed in /usr/doc/package-<version>.

As a reminder, MATE can be easily added to Slint, with these commands
typed as root:
slept-get -u
slapt-get --install-set mate

It is fully accessible with speech, as much as possible with braille.

Please read carefully the relevant documents before installing or upgrading and testing:

Before installing:
http://slackware.uk/slint/x86_64/slint- ... iso/README

More specifically about accessibility:
http://slackware.uk/slint/x86_64/slint- ... ESSIBILITY

If you who have already installed Slint64-14.2 or slint64-14.2.1RC and prefer to upgrade than isntall anew, you should also read:
http://slackware.uk/slint/x86_64/slint- ... ME-UPGRADE

More specifically, folks having installed Slint64-4.2.1RC are encouraged to also read:
http://slackware.uk/slint/x86_64/slint- ... -rc-to-rc2.


I am looking forward for your feedback and questions.

Greetings,

Didier

Re: Slint64-14.2.1rc2, last call for testing.

Posted: 11. Nov 2017, 22:19
by laprjns
Hi Didlier,
I installed Slint 14.2.1rc2 on my Asus laptop without problems and was surprise to find that I had a stable connection using NetworkManager. So the first thing I did was to update and upgrade the system using spi. There were a number of packages that where updated including slapt-get. I follow this by accepting all the dotnew configuration files except the one for the new NetworkManger package (it wanted to change the dhcp client from dhclient to dhcpcd from . I immediately follow this with a slap-get update and upgrade where I was informed that there were 87 packages that needed to be updated.

Code: Select all

root[/etc/slapt-get]# slapt-get --upg
Reading Package Lists...Done
The following NEW packages will be installed:
  webkitgtk blas lapack 
The following packages will be upgraded:
  BeautifulSoup ConfigParser NetworkManager asunder atril bdf2psf bicon 
  depfinder doclifter dotnew engrampa espeak fakeroot fbautostart fbterm geany 
  geany-plugins gnome-common gpicview grub gslapt gtkspell3 guefi hardinfo 
  hyphen imlib2 inkscape isomaster json-glib ktsuss libburn libcdr libetpan 
  libisoburn libisofs libreoffice 
  libreoffice-extension-ancient-greek-dictionary 
  libreoffice-extension-libregreek libwebp lxappearance lxde-common lxinput 
  lxlauncher lxmenu-data lxrandr lxsession lxtask menu-cache mlterm 
  mozilla-firefox network-manager-applet numpy orc pandoc parole 
  perl-Encode-EUCJPASCII perl-Encode-HanExtra perl-Encode-ISO2022 
  perl-Encode-JISX0213 perl-MIME-Charset perl-Module-Build perl-Text-CharWidth 
  perl-Text-WrapI18N perl-Unicode-LineBreak perl-inc-latest podofo potrace 
  py3cairo py3gobject py3xdg python-lxml python-six python-urllib3 python3 
  salix-codecs-installer salix-update-notifier scribus slkbuild sourcery 
  speech-dispatcher spi spkg transifex-client txt2tags viewnior xdgmenumaker 
  zenity 
87 upgraded, 0 reinstalled, 3 newly installed, 0 to remove, 0 not upgraded.
I did check on a few of these upgrades and found that slapt-get wanted t replace Slint package with Salix packages:

Code: Select all

root[/etc/slapt-get]# slapt-get -i -s geany zenity slkbuild speech-dispatcher
Reading Package Lists...Done
The following packages will be upgraded:
  geany zenity slkbuild speech-dispatcher 
4 upgraded, 0 reinstalled, 0 newly installed, 0 to remove, 0 not upgraded.
Need to get 6.9MB of archives.
After unpacking 7.7MB of additional disk space will be used.
geany-1.31-x86_64-1slint is to be upgraded to version 1.28-x86_64-1gv
zenity-3.18.1.1-x86_64-1slint is to be upgraded to version 3.18.1.1-x86_64-1gv
slkbuild-1.2-noarch-1slint is to be upgraded to version 1.2-noarch-1gv
speech-dispatcher-0.8.7-x86_64-2slint is to be upgraded to verrsion 0.8.3-x86_64-1dj
So I took a look at the slapt-getrc config file in the slapt-get-0.10.2t-x86_64-6slint.txz package and saw that the Salix repos was designated as OFFICIAL and Slint as PREFERRED. According to the slapt-get documentation OFFICIAL repos have priority over PREFERRED. So this is why it wants to upgrade to all of the Salix packages. However the root cause of the problem is that the package on your repo (slapt-get-0.10.2t-x86_64-6slint) is an earlier version from what is on the ISO (slapt-get-0.10.2t-x86_64-9slint). When I updated the first time, the version on 9 package was replaced with the version 6 which has the wrong repo priority.

Re: Slint64-14.2.1rc2, last call for testing.

Posted: 11. Nov 2017, 23:48
by DidierSpaier
Hi Rich,

Well, actually the problem comes from the fact that in the RC2 ISO I ship slapt-get-0.10.2t-x86_64-9slint with this line for the Slint source:
SOURCE=http://slackware.uk/slint/x86_64/slint-14.2/:PREFERRED
but currently the packages for upcoming Slint64-14.2.1 are tentatively in a separate repository:
http://slackware.uk/slint/x86_64/slint-testing.
So after installation the line in slapt-getrc should be changed like this:
SOURCE=http://slackware.uk/slint/x86_64/slint- ... :PREFERRED
This is stated in http://slackware.uk/slint/x86_64/slint- ... iso/README but maybe you missed it.

So slapt-get --upgrade actually did a downgrade to 14.2, including of slapt-get itself.

Maybe at this point the safest thing to do would be to reinstall rc2

However you could instead just follow the instructions given in http://slackware.uk/slint/x86_64/slint- ... ME-UPGRADE, which if all goes well should restore Slint64-14.2.1.

Also, I am aware that according to the slapt-get documentation OFFICIAL repos have priority over PREFERRED, but actually it's the opposite: PREFERRED have priority over OFFICIAL.

I have attempted to clarify things in this file (shipped in the RC2ISO as slapt-getrc).

Greetings,

Didier

Re: Slint64-14.2.1rc2, last call for testing.

Posted: 12. Nov 2017, 09:10
by gapan
DidierSpaier wrote:Also, I am aware that according to the slapt-get documentation OFFICIAL repos have priority over PREFERRED,
Where does it say that?
DidierSpaier wrote:but actually it's the opposite: PREFERRED have priority over OFFICIAL.
Yes, that's how it works. Priorities are defined in the source code in this enumeration:

Code: Select all

typedef enum {
    SLAPT_PRIORITY_DEFAULT = 0,
    SLAPT_PRIORITY_DEFAULT_PATCH,
    SLAPT_PRIORITY_OFFICIAL,
    SLAPT_PRIORITY_OFFICIAL_PATCH,
    SLAPT_PRIORITY_PREFERRED,
    SLAPT_PRIORITY_PREFERRED_PATCH,
    SLAPT_PRIORITY_CUSTOM,
    SLAPT_PRIORITY_CUSTOM_PATCH
} SLAPT_PRIORITY_T;

Re: Slint64-14.2.1rc2, last call for testing.

Posted: 12. Nov 2017, 12:30
by laprjns
gapan wrote:
DidierSpaier wrote:Also, I am aware that according to the slapt-get documentation OFFICIAL repos have priority over PREFERRED,
Where does it say that?
This is where I read it;
usr/doc/slapt-get-0.10.2t/README wrote: Each SOURCE can be a assigned a priority level, by appending :{PRIORITY} to
the source URI. For example:

SOURCE={url}:DEFAULT is the default, lowest priority
SOURCE={url}:PREFERRED assigns more weight to this source
SOURCE={url}:OFFICIAL even more weight, used to denote official sources
SOURCE={url}:CUSTOM highest priority, for your custom package source
I interpreted this as meaning that CUSTOM has the highest priority followed by OFFICIAL, then PREFERRED, with DEFAULT having the lowest priority,
DidierSpaier wrote:So after installation the line in slapt-getrc should be changed like this:
SOURCE=http://slackware.uk/slint/x86_64/slint-14.2/:PREFERRED
Do you mean that slapt-getrc should be edited to look like this?
SOURCE=http://slackware.uk/slint/x86_64/slint-testing/:PREFERRED
DidierSpaier wrote:This is stated in http://slackware.uk/slint/x86_64/slint- ... iso/README but maybe you missed it.
Well yes I did. Are you going to change the testing repo to 14.2 when you release the 14.2.1 iso?
DidierSpaier wrote:So slapt-get --upgrade actually did a downgrade to 14.2, including of slapt-get itself.

So the first update I did to my Slint 14.2.1 install actually downgraded to Slint 14.2. And the second update, if I had followed through with it. would have updated the common packages, 87 packages in this case, to Salix 14.2.
I'm going to just reinstall.

Re: Slint64-14.2.1rc2, last call for testing.

Posted: 12. Nov 2017, 18:42
by DidierSpaier
laprjns wrote:Do you mean that slapt-getrc should be edited to look like this?
SOURCE=http://slackware.uk/slint/x86_64/slint-testing/:PREFERRED
Yes I did, sorry for the typo, now corrected
laprjns wrote:Are you going to change the testing repo to 14.2 when you release the 14.2.1 iso?
Yes. Maybe making a symlink testing => 14.2 during some time? I have still to inform properly people people
  • running 14.2 that they need to get the new and upgraded packages and modify their user configurations, as stated in http://slackware.uk/slint/x86_64/slint- ... ME-UPGRADE (minus the change of the repo),
  • running testing that they have to update again slapt-getrc the other way round.
Advice on how to insure a smooth transition for all users is welcome
laprjns wrote:I'm going to just reinstall.
That's probably faster, sorry for the inconvenience.

Note: Edited for clarity (bullet list added).

Re: Slint64-14.2.1rc2, last call for testing.

Posted: 13. Nov 2017, 01:10
by Atip
Every now and then I see in gkrellm that the cpu is used by 100%
Checking with Top it shows that it is python. Killing it stops it.
I have not yet found what causes this runaway. Sometimes after opening
a kde program. I am using fluxbox as my desktop.

Re: Slint64-14.2.1rc2, last call for testing.

Posted: 13. Nov 2017, 11:15
by DidierSpaier
Hello,
Atip wrote:Every now and then I see in gkrellm that the cpu is used by 100%
Checking with Top it shows that it is python. Killing it stops it.
I have not yet found what causes this runaway. Sometimes after opening
a kde program. I am using fluxbox as my desktop.
Please try htop instead of top, it will give you the command that started python, helpful to find the cause.

Didier

Re: Slint64-14.2.1rc2, last call for testing.

Posted: 19. Nov 2017, 03:45
by Atip
DidierSpaier wrote:Hello,
Atip wrote:Every now and then I see in gkrellm that the cpu is used by 100%
Checking with Top it shows that it is python. Killing it stops it.
I have not yet found what causes this runaway. Sometimes after opening
a kde program. I am using fluxbox as my desktop.
Please try htop instead of top, it will give you the command that started python, helpful to find the cause.

Didier
Made an upgrade to RC2 following instuctions. Now I cannot duplicate it anymore.

However, after this upgrade when booting I get now a scrolling for about 30 seconds:
failed to execute '/lib/udev/socket:/org/freedesktop/hal/udev_event' 'socket:/org/freedesktop/hal/udev_event': No such file or directory
It does not seem to affect the performance of the box at all once logged-in.

Further run:

Code: Select all

installpkg ./14.2/slackwar64-compat32/*-compat32/*.txz
Now I can open "steak" and "gpasman". :D

Re: Slint64-14.2.1rc2, last call for testing.

Posted: 20. Nov 2017, 08:19
by Atip
python using 100 % of CPU.

This time I caught it and htop says:
python /usr/bin/hp-systray -x
Further, there was no /dev/audio during past boots.
So my program "saytime" would not work.
I copied /dev/audio over from Slint-32 and saytime
is working and /dev/audio survives a reboot sofar.