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.
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
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:
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.
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?
Distribution: VM Host: Slackware-current, VM Guests: Artix, Venom, antiX, Gentoo, FreeBSD, OpenBSD, OpenIndiana
Posts: 1,011
Rep:
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:
~# 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.
~# 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.
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.
Last edited by LuckyCyborg; 02-17-2021 at 10:44 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.
Distribution: Slackware 64 -current multilib from AlienBob's LiveSlak MATE
Posts: 1,086
Rep:
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.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.