[SOLVED] Slackware 15.0 Alpha 1

however · 02-16-2021, 05:26 PM

I tried (twice) to upgrade my desktop with the usual

Code:

su
********
bash# slackpkg update
bash# slackpkg install-new
bash# slackpkg upgrade-all

When i get to the last step "upgrade-all" the upgrade stops and i get this msg

Quote:

bash-5.1# slackpkg upgrade-all

FATAL! There is some problem in packages database
or maybe an installation or upgrade in progress:

aaa_glibc-solibs-2.32-x86_64-2-upgraded-2021-02-16,23:31:50

If you continue you may corrupt packages database.
Check or retry later

bash-5.1#

I said twice but i should have said three times: the first time I removed the aaa_glibc-solibs package with pkgtool and started the upgrade-all process again: big messy salad! Upgrade process stopped at random, no other commands were executing i.e. lilo and/or firefox, dolphin, reboot, etc.

So, hard reset and, expectedly, I had the beautiful 'kernel panic' message at boot.

Managed to repair that with the original installation disc and booted again as normal so, back to slackpkg and started a clean update/upgrade process. Same thing: it stops on 'slackpkg upgrade-all' with the FATAL msg above.

What am i doing wrong this time?

p.s.: wasn't sure whether I should have started a new thread but since I saw the gblic being mentioned here and the call for testing and reporting of bugs, i decided to post here

upnort · 02-16-2021, 06:10 PM

New Updating Slackware 14.2 to 15.0 Megathread available.

however · 02-16-2021, 06:18 PM

Quote:

Originally Posted by however

I tried (twice) to upgrade my desktop with the usual

Code:

su
********
bash# slackpkg update
bash# slackpkg install-new
bash# slackpkg upgrade-all

When i get to the last step "upgrade-all" the upgrade stops and i get this msg

I said twice but i should have said three times: the first time I removed the aaa_glibc-solibs package with pkgtool and started the upgrade-all process again: big messy salad! Upgrade process stopped at random, no other commands were executing i.e. lilo and/or firefox, dolphin, reboot, etc.

So, hard reset and, expectedly, I had the beautiful 'kernel panic' message at boot.

Managed to repair that with the original installation disc and booted again as normal so, back to slackpkg and started a clean update/upgrade process. Same thing: it stops on 'slackpkg upgrade-all' with the FATAL msg above.

What am i doing wrong this time?

p.s.: wasn't sure whether I should have started a new thread but since I saw the gblic being mentioned here and the call for testing and reporting of bugs, i decided to post here

Ignore it!
I followed

Quote:

montagdude
I just upgraded my -current, which was stale by one or two weeks. I followed ponce's instructions here:

https://www.linuxquestions.org/quest...3/#post6217668

and upgrade process finished ok!

1337_powerslacker · 02-16-2021, 08:51 PM

Quote:

Originally Posted by LuckyCyborg

Phoronix.com : Slackware 15.0 On Approach With An Early Alpha Build Available

Looks like this gentleman reads our ChangeLog in a daily base - and apparently often than some proud Slackers who are casually bitten by the updates from -current...

Looks like you beat me to it...I was going to say that Slackware got a mention on Phoronix. Good to see a major Linux news site mention Slackware.

Rock on, Slackers!

andrew.46 · 02-16-2021, 09:15 PM

Quote:

Originally Posted by Paulo2

+1.
Should we post problems here?

'mail' doesn't work, it shows an error message about the lock file.
[...]

Another problem is with SBo(-current) tor-browser, it shows "Gah. Your tab just crashed."

I can confirm both issues here. Not many clues online about the error with s-nail...

pghvlaans · 02-17-2021, 01:44 AM

Quote:

Originally Posted by GazL

Well, on my sub £400 laptop with crappy 5200rpm spinning rust, it took approx one and a half episodes of Buffy. So, about an hour.

upgradepkg is painfully slow (but still not as annoying as windows update!).

Two and a half hours, not including download time. I was expecting worse. The computers that are actually good did much better!

however · 02-17-2021, 02:24 AM

Quote:

Originally Posted by however

Ignore it!
I followed

and upgrade process finished ok!

Was being positively hopefully!
Went to bed and left the upgrade running but this morning I saw that the upgrade process stopped again while upgrading gblic.
I had to repair the setup with the installation disc again (kernel panic issue) and I couldnt edit a file with the error msg as the whole desktop became unresponsive; I took a picture with my phone of the error msg
Shall i start a new thread?

Aeterna · 02-17-2021, 09:24 AM

firefox error after today's update

Quote:

[5605, Main Thread] WARNING: failed to open shm: Permission denied: file /tmp/firefox-78.7.1/ipc/chromium/src/base/shared_memory_posix.cc, line 246
Segmentation fault

thunderbird generates the same error:

Quote:

[1710, Main Thread] WARNING: failed to open shm: Permission denied: file /tmp/thunderbird-78.7.1/ipc/chromium/src/base/shared_memory_posix.cc, line 246
Segmentation fault

had to edit /etc/fstab

now error is related to
failed to find gam_server
failed to find gam_server
Failed to connect to socket /tmp/fam--
Failed to connect to socket /tmp/fam--

fixed this too but
firefox will launch only from command prompt.

this is seriously wrong:
firefox will not start if tmp setting in /etc/fstab is set to:

Quote:

#tmpfs /tmp tmpfs rw,nosuid,noatime,nodev,size=4G,mode=1777 0 0

it has to be

Quote:

tmpfs /dev/shm tmpfs defaults 0 0

still firefox will start only from command prompt

drgibbon · 02-17-2021, 10:04 AM

A few broken bits and pieces on -current:

Code:

~# mail
mailx: Creating file (dot) lock for /var/spool/mail/root . failed
mailx:   Fishy!  Is someone trying to "steal" foreign files?
mailx:   Please check the mailbox file etc. manually, then retry
mailx: Unable to (dot) lock mailbox, aborting operation: Resource temporarily unavailable
mailx: Creating file (dot) lock for /var/spool/mail/root . failed
mailx:   Fishy!  Is someone trying to "steal" foreign files?
mailx:   Please check the mailbox file etc. manually, then retry
mailx: Unable to (dot) lock mailbox: Resource temporarily unavailable
mailx: There are new messages in the error message ring (denoted by ERROR),
mailx:   which can be managed with the `errors' command
ERROR# Continue, possibly losing changes [yes]/no?

Code:

~# firefox
(firefox:10445): Gtk-WARNING **: 23:57:33.816: Could not load a pixbuf from icon theme.
This may indicate that pixbuf loaders or the mime database could not be found.
failed to find gam_server
failed to find gam_server
failed to find gam_server
failed to find gam_server
Failed to connect to socket /tmp/fam--

etc

Code:

~# plasma-systemmonitor
QIODevice::read (QFile, "/sys/fs/cgroup/user.slice/user-1000.slice/user@1000.service/cgroup.procs"): device not open
terminate called after throwing an instance of 'std::filesystem::__cxx11::filesystem_error'
  what():  filesystem error: directory iterator cannot open directory: No such file or directory [/sys/fs/cgroup/user.slice/user-1000.slice/user@1000.service]
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = plasma-systemmonitor path = /usr/bin pid = 10224
KCrash: Arguments: /usr/bin/plasma-systemmonitor 
KCrash: Attempting to start /usr/lib64/drkonqi
Unable to start Dr. Konqi
org.kde.drkonqi: The specified process does not exist.

Code:

~# tor-browser
Gah. Your tab just crashed.

LuckyCyborg · 02-17-2021, 10:31 AM

Quote:

Originally Posted by drgibbon

A few broken bits and pieces on -current:

Code:

~# plasma-systemmonitor
QIODevice::read (QFile, "/sys/fs/cgroup/user.slice/user-1000.slice/user@1000.service/cgroup.procs"): device not open
terminate called after throwing an instance of 'std::filesystem::__cxx11::filesystem_error'
  what():  filesystem error: directory iterator cannot open directory: No such file or directory [/sys/fs/cgroup/user.slice/user-1000.slice/user@1000.service]
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = plasma-systemmonitor path = /usr/bin pid = 10224
KCrash: Arguments: /usr/bin/plasma-systemmonitor 
KCrash: Attempting to start /usr/lib64/drkonqi
Unable to start Dr. Konqi
org.kde.drkonqi: The specified process does not exist.

This one apparently was already fixed, as shown bellow:
https://bugs.kde.org/show_bug.cgi?id=433013
And the relevant patch is there:
https://invent.kde.org/plasma/libksy...afbbc29323db06

Long story short, looks like this will be fixed on Plasma 5.21.1 but I hope that meantime the patch will be still applied by Slackware, as plasma-systemmonitor is dead on arrival.

drgibbon · 02-17-2021, 10:39 AM

@Aeterna No problems starting Firefox/Thunderbird here, they both start fine for me with:

Code:

tmpfs            /dev/shm         tmpfs       nosuid,nodev,noexec  0   0

in /etc/fstab. The gam_server issue was introduced back in the ktown days though, how did you manage to fix it?

Quote:

Originally Posted by LuckyCyborg

Long story short, looks like this will be fixed on Plasma 5.21.1 but I hope that meantime the patch will be still applied by Slackware, as plasma-systemmonitor is dead on arrival.

Ahh systemd, nice work, thanks.

Aeterna · 02-17-2021, 03:59 PM

Quote:

Originally Posted by drgibbon

@Aeterna No problems starting Firefox/Thunderbird here, they both start fine for me with:

Code:

tmpfs            /dev/shm         tmpfs       nosuid,nodev,noexec  0   0

in /etc/fstab. The gam_server issue was introduced back in the ktown days though, how did you manage to fix it?

Ahh systemd, nice work, thanks.

I will modify fstab as you suggest.

fix for gam server:
edit

Quote:

/etc/gamin/gaminrc

change for all used filesystems

Quote:

fsset fs poll 15
to
fsset fs poll 104

e.g.

Quote:

fsset ext4 poll 15
to
fsset ext4 poll 104

hope this will help

SCerovec · 02-17-2021, 06:34 PM

What, already?
But I'm not ready yet!
This is too early!
Can't we wait this out for half past May?
(just kidding, kudos to Slackware

)

SimonDevine · 02-17-2021, 09:29 PM

Having seen the front page news on Distrowatch for 15, I certainly felt immensely cheered that it's now going to Alpha.

I read all the messages in this thread and have to fully concur with hazel in that space should be made ready for Beta.

Thanks to PV and the team for all their hard work.

kgha · 02-18-2021, 06:05 AM

Re: the tor-browser - I ran into the "Gah" issue after the last -current upgrades (tor-browser stable 10.0.10). Turns out that the latest alpha release (10.5a8) runs OK, so the next stable release will probably do as well.