Salix 15.0RC4

User avatar
gaucho
Donor
Posts: 116
Joined: 23. Dec 2010, 19:12

Re: Salix 15.0RC4

Post by gaucho »

I downloaded the RC4 and did a fresh installation this afternoon on the Dell laptop [specs in my signature]. I used the 64-bit .iso, BIOS installation, with a (US) English locale.

Almost everything I've tried so far is working normally / as expected :) , but there are a few new issues which I did not experience with the previous RC3 release.
  • More stringent control of setting password for user account(s):
When I reached the step of setting the password for my user account, the password that I normally use was rejected with the error message: "BAD PASSWORD: The password fails the dictionary check -- it is based on a dictionary word."

(I should mention that although this word is an [uncommon] English-language word (8 characters in length), it is found in dictionaries. However, in the past, the installer just warned me that it is a 'weak' password, then allowed me to proceed.

So I thought, "OK ... No problem. I'll modify it and try again." I tried using that same 8-character word, but also added a two-digit number [Arabic numerals] to it, for a total length of 10 characters. The new password was rejected with the same "BAD PASSWORD" error message).

I finally ended up creating a non-dictionary, alphanumeric password (11 characters long) which was accepted as being OK.

This isn't really a problem but I wasn't expecting to encounter this level of "pickiness" with the installer -- unless I did something wrong. It might be a good idea to include a brief pre-installation note advising users that password parameters are stricter than before. That could potentially eliminate some frustration ...
  • The Multimedia Codecs Installer was not removed from the menu after being run.
Although the multimedia codecs script downloaded and installed codecs correctly, when it finished, I chose the option of removing it from the menu. (I'm 99% sure that I clicked on the appropriate button :? ). However, when I checked, it was still present under the "Multimedia" section of the menu.

My workaround was to hide it, by right-clicking on the Codecs Installer in the menu and selecting "Hide Application."
  • pdfarranger does not launch after installation.
When I try to start it from the Terminal, I get the error message below:

Code: Select all

david[~]$ pdfarranger
Traceback (most recent call last):
  File "/usr/bin/pdfarranger", line 33, in <module>
    sys.exit(load_entry_point('pdfarranger==1.8.2', 'console_scripts', 'pdfarranger')())
  File "/usr/bin/pdfarranger", line 25, in importlib_load_entry_point
    return next(matches).load()
  File "/usr/lib64/python3.9/importlib/metadata.py", line 86, in load
    module = import_module(match.group('module'))
  File "/usr/lib64/python3.9/importlib/__init__.py", line 127, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 1030, in _gcd_import
  File "<frozen importlib._bootstrap>", line 1007, in _find_and_load
  File "<frozen importlib._bootstrap>", line 986, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 680, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 850, in exec_module
  File "<frozen importlib._bootstrap>", line 228, in _call_with_frames_removed
  File "/usr/lib64/python3.9/site-packages/pdfarranger/pdfarranger.py", line 30, in <module>
    import pikepdf
  File "/usr/lib64/python3.9/site-packages/pikepdf/__init__.py", line 19, in <module>
    from ._version import __version__
  File "/usr/lib64/python3.9/site-packages/pikepdf/_version.py", line 7, in <module>
    from pkg_resources import DistributionNotFound
  File "/usr/lib64/python3.9/site-packages/pkg_resources/__init__.py", line 3243, in <module>
    def _initialize_master_working_set():
  File "/usr/lib64/python3.9/site-packages/pkg_resources/__init__.py", line 3226, in _call_aside
    f(*args, **kwargs)
  File "/usr/lib64/python3.9/site-packages/pkg_resources/__init__.py", line 3255, in _initialize_master_working_set
    working_set = WorkingSet._build_master()
  File "/usr/lib64/python3.9/site-packages/pkg_resources/__init__.py", line 568, in _build_master
    ws.require(__requires__)
  File "/usr/lib64/python3.9/site-packages/pkg_resources/__init__.py", line 886, in require
    needed = self.resolve(parse_requirements(requirements))
  File "/usr/lib64/python3.9/site-packages/pkg_resources/__init__.py", line 772, in resolve
    raise DistributionNotFound(req, requirers)
pkg_resources.DistributionNotFound: The 'packaging>=20' distribution was not found and is required by pikepdf
I'll continue testing and report any other glitches that I experience.

As always, gapan, Ευχαριστώ πολύ! for all your effort. :)
Registered Linux User # 442201

Dell Latitude E4300 laptop: Intel Core2 Duo P9400 CPU, 8 GB RAM, Samsung 850 EVO 250 GB SSD, Intel Wireless 7260
User avatar
SalixManiac
Posts: 113
Joined: 15. Apr 2022, 02:26

Re: Salix 15.0RC4

Post by SalixManiac »

missTell
Dump that 'shitface' and install yourself IceWM!
Ok I'm going to show you Gapam's horrible secret and the victims of his experiments.

Image
blue wallpaper and led monitor (blue rayonnement)

Image
Thunar without zenity

Image
Salix user without graphic installer

Image
Salix user without daemons manager

Image
Salix with minimalist desktop
Colin Chapman “light is right” those last words "the middle pedal is for cowards"
User avatar
mimosa
Salix Warrior
Posts: 3311
Joined: 25. May 2010, 17:02
Contact:

Re: Salix 15.0RC4

Post by mimosa »

I can confirm the codecs installer is still there, though I am not one hundred percent certain I opted to remove it.

Removing it manually removes the menu entry too:

Code: Select all

mimosa[~]$ sudo slapt-get -i --remove salix-codecs-installer
User avatar
gapan
Salix Wizard
Posts: 6236
Joined: 6. Jun 2009, 17:40

Re: Salix 15.0RC4

Post by gapan »

gaucho wrote: 1. Sep 2022, 02:41
  • The Multimedia Codecs Installer was not removed from the menu after being run.
Although the multimedia codecs script downloaded and installed codecs correctly, when it finished, I chose the option of removing it from the menu. (I'm 99% sure that I clicked on the appropriate button :? ). However, when I checked, it was still present under the "Multimedia" section of the menu.
I just tried it and it worked. You can try again with something like:

Code: Select all

sudo spkg -d lame
Run the codecs installer, install the package that was removed and select to remove the package.
Image
Image
User avatar
mimosa
Salix Warrior
Posts: 3311
Joined: 25. May 2010, 17:02
Contact:

Re: Salix 15.0RC4

Post by mimosa »

Yes that works here (64 bits).

About the password, you can change it to a "bad" password after installation, with just a warning.
hugok
Posts: 373
Joined: 7. Dec 2011, 22:44
Location: Portugal
Contact:

Re: Salix 15.0RC4

Post by hugok »

SalixManiac wrote: 1. Sep 2022, 07:22
missTell
Dump that 'shitface' and install yourself IceWM!
Ok I'm going to show you Gapam's horrible secret and the victims of his experiments.

Image
blue wallpaper and led monitor (blue rayonnement)

Image
Thunar without zenity

Image
Salix user without graphic installer

Image
Salix user without daemons manager

Image
Salix with minimalist desktop
:lol: :lol: :lol:
Hugo Carvalho
Portuguese translator

https://github.com/hugok79
hugok
Posts: 373
Joined: 7. Dec 2011, 22:44
Location: Portugal
Contact:

Re: Salix 15.0RC4

Post by hugok »

mimosa wrote: 1. Sep 2022, 08:18
About the password, you can change it to a "bad" password after installation, with just a warning.
The point here is that if I want e.g. 1234; password or qwerty password etc... It should always accept that password and only warn you about it :?
Hugo Carvalho
Portuguese translator

https://github.com/hugok79
salpek
Posts: 11
Joined: 22. Apr 2022, 22:09

Re: Salix 15.0RC4

Post by salpek »

gapan wrote: 30. Aug 2022, 09:12 I have added an upgrade path from 14.2 to 15.0 in the wiki: https://docs.salixos.org/wiki/How_to_up ... .2_to_15.0
Upgrade on Dell Latitude D410:
(on this machine upgrade from 14.1 to 14.2 perfect - everything OK)

14.2 to 15.0
Issues:

1. LiLo:
- after kernels upgrading

Code: Select all

slapt-get -i lilo
No problem

Code: Select all

lilo -v
lilo: /lib/libc.so.6 version GLIBC_2.33" not found (required by lilo)
(Upgrade instruction 14.1 to 14.2 kernel and lilo update was the last step - now is the second before upgrading packages)

- after upgrading packages

Code: Select all

lilo -v
Fatal: Cannot open /etc/lilo.conf
Yes - file lilo.conf was deleted ;o

- solution:
liloconfig
and configure new lilo.conf file...

After reboot - no problems - lilo works and boot salix :)

===

2. Vi
- after complete dotnew step

Code: Select all

vi /etc/slackware-version
vi: error while loading shared libraries: libruby.so.3.0 - cannot open shared object file: no such file or directory
- solution:

Code: Select all

slapt-get -i ruby
vi is alive :)


----
After upgrade everything works great :)

+++
1 issue after upgrade:

LightDM Greeter on login use English, but after login everything is in PL.

solution:
XFCE Menu > System Language > Polish locale for Poland (already was selected) > Apply changes
After logout lightdm use PL locale :)
User avatar
gapan
Salix Wizard
Posts: 6236
Joined: 6. Jun 2009, 17:40

Re: Salix 15.0RC4

Post by gapan »

gaucho wrote: 1. Sep 2022, 02:41
  • pdfarranger does not launch after installation.
Yes, you need to also install the python-packaging and pyparsing packages. I'll add them to its dependencies. Thanks!
Image
Image
User avatar
gapan
Salix Wizard
Posts: 6236
Joined: 6. Jun 2009, 17:40

Re: Salix 15.0RC4

Post by gapan »

salpek wrote: 1. Sep 2022, 10:29 1. LiLo:
- after kernels upgrading

Code: Select all

slapt-get -i lilo
No problem

Code: Select all

lilo -v
lilo: /lib/libc.so.6 version GLIBC_2.33" not found (required by lilo)
(Upgrade instruction 14.1 to 14.2 kernel and lilo update was the last step - now is the second before upgrading packages)

- after upgrading packages

Code: Select all

lilo -v
Fatal: Cannot open /etc/lilo.conf
Yes - file lilo.conf was deleted ;o

- solution:
liloconfig
and configure new lilo.conf file...

After reboot - no problems - lilo works and boot salix :)
Thanks, I have edited the wiki accordingly.
salpek wrote: 1. Sep 2022, 10:29 2. Vi
- after complete dotnew step

Code: Select all

vi /etc/slackware-version
vi: error while loading shared libraries: libruby.so.3.0 - cannot open shared object file: no such file or directory
- solution:

Code: Select all

slapt-get -i ruby
vi is alive :)
Ah, yes, I had forgotten about this. Vim depends on ruby, but only on 32bits. I have added the dependency now.
Image
Image
Post Reply