[SOLVED] Last update put my Xorg into OOC state.

BW-userx · 03-30-2017, 10:56 AM

My xorg is now out of commission due to the latest update I just did.

I was going black screen so I switched ttys and I changed run level back to 3 - reboot - than startx gave me that error.

Code:

ck-launch-session: error while loading shared libraries: libgio-2.0.so.0: cannot open shared object file: No such file or directory

ls /usr/lib/ | grep libgio

libgio-2.0.la*
libgio-2.0.so@
libgio-2.0.so.0@
libgio-2.0.so.0.4600.2*

root@slackwhere:~# ln -s /usr/lib/libgio-2.0.0.la /usr/lib/libgio-2.0.so.0
ln: failed to create symbolic link '/usr/lib/libgio-2.0.so.0': File exists

# preforming hit and miss soft linking then got a message it is already linked. 

root@slackwhere:~# ls -la /usr/lib/libgio-2.0.so.0
lrwxrwxrwx 1 root root 22 Mar 30 09:42 /usr/lib/libgio-2.0.so.0 -> libgio-2.0.so.0.4600.2*

as it shows it is already there and still not working.

so now what just short of reinstalling Slack again?

slack 14.2 NOT current.

(good thing I got dual boot linux to get back on line and be able to get to Slack to get my message file I created using echo and " " and > and >> redirection. said for the under learned in Linux.

it saves having to write down everything on paper then again in a help me post.

copy paste - and having a mouse working in cli too helps a LOT. Thanks Slackware!)

bassmadrigal · 03-30-2017, 11:28 AM

What updates? There weren't any recent updates that should affect your glib2 package.

Can you post the output of the following command? It should show us the last 20 packages that were installed/upgraded.

Code:

ls -lrt /var/log/packages | tail -n 20

BW-userx · 03-30-2017, 11:35 AM

Quote:

Originally Posted by bassmadrigal

What updates? There weren't any recent updates that should affect your glib2 package.

Can you post the output of the following command? It should show us the last 20 packages that were installed/upgraded.

Code:

ls -lrt /var/log/packages | tail -n 20

I am doing a Alien bob mirror on standard 14.2 and used that.

Code:

# The slackware release we're mirroring (defaults to 'current').
# You can use the script's '-r' switch to alter this to another release,
# for instance mirror Slackware 13.37 by passing '-r 13.37' to the script.
RELEASE="14.2"

# The RSYNC mirror:
# Supply a full rsync URI in the RSYNCURLROOT variable, while leaving out
# the final "slackware-current" directory. Do not remove the trailing slash!
# RSYNCURL will become ${RSYNCURLROOT}${SLACKRELEASE} further down.
# An alternative rsync mirror URI can also be passed to the script with
# the '-m' option - that URI must *not* have a trailing slash.
RSYNCURLROOT="rsync.osuosl.org::slackware/"
RSYNCURL=""

let me boot back into Slack and get that info and boot back into Void to get it to you. wait I got the mirror on my secondary hdd, can I get that information off of that?
if yes do you know how and can you give me that information to do so while i'm trying to figure it out.

wait .. I too should be able to just mount Slack and do it off the mount. hold on.

Code:

userx@voider⚡~ $sudo ls -lrt /mnt/var/log/packages | tail -n 20
-rw-r--r-- 1 root root     907 Mar 28 18:53 libass-0.13.5-x86_64-1_SBo
-rw-r--r-- 1 root root    1197 Mar 28 18:53 x264-20160221-x86_64-1_SBo
-rw-r--r-- 1 root root    1750 Mar 28 18:53 lame-3.99.5-x86_64-1_SBo
-rw-r--r-- 1 root root    2551 Mar 28 19:01 HandBrake-0.10.5-x86_64-1_SBo
-rw-r--r-- 1 root root    1953 Mar 29 09:19 libdockapp-0.6.2-x86_64-1_SBo
-rw-r--r-- 1 root root    1375 Mar 29 09:29 axel-2.4-x86_64-1_SBo
-rw-r--r-- 1 root root    1713 Mar 29 09:49 freefont-20120503-noarch-1_SBo
-rw-r--r-- 1 root root   28063 Mar 29 10:16 dropbox-21.4.25-x86_64-1_SBo
-rw-r--r-- 1 root root    4727 Mar 29 10:25 xpenguins-2.2-x86_64-1_SBo
-rw-r--r-- 1 root root    7049 Mar 29 11:19 xfce4-cpufreq-plugin-1.1.3-x86_64-1_SBo
-rw-r--r-- 1 root root    6558 Mar 29 11:28 xfce4-cpugraph-plugin-1.0.5-x86_64-1_SBo
-rw-r--r-- 1 root root    7290 Mar 29 11:30 xfce4-sensors-plugin-1.2.6-x86_64-1_SBo
-rw-r--r-- 1 root root    5404 Mar 29 17:01 neofetch-3.0.1-noarch-1_SBo
-rw-r--r-- 1 root root   12891 Mar 30 10:41 bind-9.10.4_P6-i586-1_slack14.2
-rw-r--r-- 1 root root   19662 Mar 30 10:41 curl-7.51.0-i586-1_slack14.2
-rw-r--r-- 1 root root    1001 Mar 30 10:41 efibootmgr-0.6.0-i486-1
-rw-r--r-- 1 root root     928 Mar 30 10:41 expat-2.2.0-i586-1_slack14.2
-rw-r--r-- 1 root root  124820 Mar 30 10:41 gimp-2.8.18-i586-1_slack14.2
-rw-r--r-- 1 root root   47142 Mar 30 10:42 glib2-2.46.2-i586-3_slack14.2
-rw-r--r-- 1 root root    4463 Mar 30 10:42 gnupg-1.4.21-i586-1_slack14.2

ChangeLog.txt:
Your file of 381.3 KB bytes exceeds the forum's limit of 256.0 KB for this filetype.

off my changesLog.txt find glib2

Tue Mar 28 20:30:50 UTC 2017

Code:

patches/packages/glib2-2.46.2-i586-3_slack14.2.txz:  Rebuilt.
  Applied upstream patch to fix a use-before-allocate bug in libgio.  

Without this fix, Thunar will crash if $HOME is on an NFS volume.
Thanks to Jonathan Woithe.

Xorg

Code:

x/xorg-server-1.18.3-i586-2.txz:  Rebuilt.
  Applied a patch from https://bugs.freedesktop.org/show_bug.cgi?id=49950
  to fix applying keyboard layout settings when using a keyboard/mouse combo
  device such as a Logitech wireless keyboard with the unifying receiver.
  Thanks to Jean-Philippe Guillemin.
x/xorg-server-xephyr-1.18.3-i586-2.txz:  Rebuilt.
x/xorg-server-xnest-1.18.3-i586-2.txz:  Rebuilt.
x/xorg-server-xvfb-1.18.3-i586-2.txz:  Rebuilt.

now what?

bassmadrigal · 03-30-2017, 01:07 PM

There's no need to post the changelog. It is readily available from any mirror. But, when you said you did the "latest update", that doesn't imply you're installing updates from August 2016 (which is where the glib2 update came from). That's why I said there's nothing recent that would affect that package. The last change to it was over 6 months ago.

But, quick look at your packages and you have 32bit (i485 or i586) mixed with x86_64 packages. So my guess is that you uncommented the 32bit mirror when you should've uncommented the 64bit mirror. You now have mixed packages on your system. You could probably upgradepkg --reinstall them with the correct ones, but I'm not sure if there's any other repercussions from the initial action.

BW-userx · 03-30-2017, 02:00 PM

Quote:

Originally Posted by bassmadrigal

There's no need to post the changelog. It is readily available from any mirror. But, when you said you did the "latest update", that doesn't imply you're installing updates from August 2016 (which is where the glib2 update came from). That's why I said there's nothing recent that would affect that package. The last change to it was over 6 months ago.

I only posted the changes log I have to reflect the changes to glib2 and it surely helps cut down on time making the other person having to look it up when it is now right there in front of them so I see no wrong in that one.

it states a date of Tue Mar 28 20:30:50 UTC 2017 which is just a few days ago so I do not know where you're getting the only changes where made over 6 months ago.

as well as it shows that update or patch to the file being installed Mar 30 (2017) 10:42 glib2-2.46.2-i586-3_slack14.2

which by the way is TODAYs DATE. due to this bug listed in the changelog that I kindly provided for extra information stating it is a bug fix.

Quote:

patches/packages/glib2-2.46.2-i586-3_slack14.2.txz: Rebuilt.
Applied upstream patch to fix a use-before-allocate bug in libgio.

Quote:

Originally Posted by bassmadrigal

But, quick look at your packages and you have 32bit (i485 or i586) mixed with x86_64 packages. So my guess is that you uncommented the 32bit mirror when you should've uncommented the 64bit mirror. You now have mixed packages on your system. You could probably upgradepkg --reinstall them with the correct ones, but I'm not sure if there's any other repercussions from the initial action.

but now that you point out that it is using i586 then that mirror 14.2 is not defaulting to 64bit?

so it looks like I need to change it to something like

http://slackware.osuosl.org/slackware64-14.2/

taken off there webpage it should read something like

rsync.osuosl.org::slackware64/

instead then 14.2 for the version number and just remove the i586 stuff redo upgrade to be safe keep track of what i remove and look to be sure the x86_64 equivalent is installed before I reboot and hope it fixes everything.

else default to reinstall again ;.. woo hoo

BW-userx · 03-30-2017, 02:07 PM

OK now I see exactly where it got screwed up in that config file I missed a line that needs to be changed instead.

Code:

ARCH="x86"
needs to read
ARCH="x86_64"

bamn ...

Now I get to see if I can back out the i586 stuff and fix this situation. After I get that mirror downloaded first.

thanks for pointing out that i586 part. It does help to have another pair of eyes sometimes.

thanks.

this is all of the i586 I do suppose in the system

Code:

userx@voider⚡~ $ls -lrt /mnt/var/log/packages | grep i586
-rw-r--r-- 1 root root   12891 Mar 30 10:41 bind-9.10.4_P6-i586-1_slack14.2
-rw-r--r-- 1 root root   19662 Mar 30 10:41 curl-7.51.0-i586-1_slack14.2
-rw-r--r-- 1 root root     928 Mar 30 10:41 expat-2.2.0-i586-1_slack14.2
-rw-r--r-- 1 root root  124820 Mar 30 10:41 gimp-2.8.18-i586-1_slack14.2
-rw-r--r-- 1 root root   47142 Mar 30 10:42 glib2-2.46.2-i586-3_slack14.2
-rw-r--r-- 1 root root    4463 Mar 30 10:42 gnupg-1.4.21-i586-1_slack14.2

so theoretically I should only have to removepkg i586 pkg name. then use my mirror and installpkg x86_64 equivalent. Then reboot and cross my fingers.

bassmadrigal · 03-30-2017, 02:20 PM

Quote:

Originally Posted by BW-userx

I only posted the changes log I have to reflect the changes to glib2 and it surely helps cut down on time making the other person having to look it up when it is now right there in front of them so I see no wrong in that one.

My comment was directed at this message you posted when I assume you tried to upload the changelog to the forum. Since changelogs are available online, there's no need to upload the whole thing to the forum.

Quote:

ChangeLog.txt:
Your file of 381.3 KB bytes exceeds the forum's limit of 256.0 KB for this filetype.

Quote:

Originally Posted by BW-userx

it states a date of Tue Mar 28 20:30:50 UTC 2017 which is just a few days ago so I do not know where you're getting the only changes where made over 6 months ago.

The changelog's timestamp will show the timestamp of the mirror, which is the time it was last changed. But, if you actually look at the changelog and find that entry, you'll find it under the "Tue Aug 23 19:45:33 UTC 2016" updates.

Code:

+--------------------------+
Tue Aug 23 19:45:33 UTC 2016
patches/packages/gnupg-1.4.21-x86_64-1_slack14.2.txz: Upgraded.
       Fix critical security bug in the RNG [CVE-2016-6313]. An attacker who
       obtains 580 bytes from the standard RNG can trivially predict the next
       20 bytes of output. (This is according to the NEWS file included in the
       source. According to the annoucement linked below, an attacker who obtains
       4640 bits from the RNG can trivially predict the next 160 bits of output.)
       Problem detected by Felix Doerre and Vladimir Klebanov, KIT.
       For more information, see:
       https://lists.gnupg.org/pipermail/gnupg-announce/2016q3/000395.html
       http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-6313
       (* Security fix *)
patches/packages/glib2-2.46.2-x86_64-3_slack14.2.txz: Rebuilt.
       Applied upstream patch to fix a use-before-allocate bug in libgio. Without
       this fix, Thunar will crash if $HOME is on an NFS volume.
       Thanks to Jonathan Woithe.
patches/packages/libgcrypt-1.7.3-x86_64-1_slack14.2.txz: Upgraded.
       Fix critical security bug in the RNG [CVE-2016-6313]. An attacker who
       obtains 580 bytes from the standard RNG can trivially predict the next
       20 bytes of output. (This is according to the NEWS file included in the
       source. According to the annoucement linked below, an attacker who obtains
       4640 bits from the RNG can trivially predict the next 160 bits of output.)
       Problem detected by Felix Doerre and Vladimir Klebanov, KIT.
       For more information, see:
       https://lists.gnupg.org/pipermail/gnupg-announce/2016q3/000395.html
       http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-6313
       (* Security fix *)
patches/packages/linux-4.4.19/*: Upgraded.
       A flaw was found in the implementation of the Linux kernels handling of
       networking challenge ack where an attacker is able to determine the shared
       counter. This may allow an attacker located on different subnet to inject
       or take over a TCP connection between a server and client without having to
       be a traditional Man In the Middle (MITM) style attack.
       Be sure to upgrade your initrd after upgrading the kernel packages.
       If you use lilo to boot your machine, be sure lilo.conf points to the correct
       kernel and initrd and run lilo as root to update the bootloader.
       If you use elilo to boot your machine, you should run eliloconfig to copy the
       kernel and initrd to the EFI System Partition.
       For more information, see:
       http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-5389
       (* Security fix *)
patches/packages/screen-4.4.0-x86_64-2_slack14.2.txz: Rebuilt.
       Reverted a change to /etc/screenrc.new that prevented the console from being
       cleared when a screen session was detached. Thanks to Stuart Winter.
patches/packages/stunnel-5.35-x86_64-2_slack14.2.txz: Rebuilt.
       Fixed incorrect config file name in generate-stunnel-key.sh.
       Thanks to Ebben Aries.

Quote:

as well as it shows that update or patch to the file being installed Mar 30 (2017) 10:42 glib2-2.46.2-i586-3_slack14.2

which by the way is TODAYs DATE. due to this bug listed in the changelog that I kindly provided for extra information stating it is a bug fix.

Yes, the date in your log file will show the date the package was installed. Again, when you say you installed the "latest update", it implies you were relatively up-to-date before the 28 MAR updates were pushed... not running a mostly (or completely) unpatched 14.2 install. This is what caused me to state that there were no recent updates that should've affected that package. The five most recent dates there were updates pushed contained the packages below (which covers all of March's updates to this point). As you can see, glib2 shouldn't have been touched in any of those patches.

Code:

Tue Mar 28 20:30:50 UTC 2017
patches/packages/mariadb-10.0.30-x86_64-1_slack14.2.txz: Upgraded.
       This update fixes security issues:
       Crash in libmysqlclient.so.
       Difficult to exploit vulnerability allows low privileged attacker with
       logon to compromise the server. Successful attacks of this vulnerability
       can result in unauthorized access to data.
       For more information, see:
       https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-3302
       https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-3313
       (* Security fix *)
patches/packages/mozilla-firefox-52.0.2esr-x86_64-1_slack14.2.txz: Upgraded.
       Upgraded to new Firefox 52.x ESR branch.
+--------------------------+
Thu Mar 23 21:38:23 UTC 2017
patches/packages/glibc-zoneinfo-2017b-noarch-1_slack14.2.txz: Upgraded.
       This package provides the latest timezone updates.
patches/packages/mcabber-1.0.5-x86_64-1_slack14.2.txz: Upgraded.
       This update fixes a security issue:
       An incorrect implementation of XEP-0280: Message Carbons in multiple XMPP
       clients allows a remote attacker to impersonate any user, including
       contacts, in the vulnerable application's display. This allows for various
       kinds of social engineering attacks.
       For more information, see:
       https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5604
       (* Security fix *)
patches/packages/samba-4.4.12-x86_64-1_slack14.2.txz: Upgraded.
       This update fixes a security issue:
       All versions of Samba prior to 4.6.1, 4.5.7, 4.4.12 are vulnerable to
       a malicious client using a symlink race to allow access to areas of
       the server file system not exported under the share definition.
       For more information, see:
       https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-2619
       (* Security fix *)
+--------------------------+
Thu Mar 16 01:37:05 UTC 2017
patches/packages/pidgin-2.12.0-x86_64-1_slack14.2.txz: Upgraded.
       This update fixes a minor security issue (out of bounds memory read in
       purple_markup_unescape_entity).
       For more information, see:
       https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-2640
       (* Security fix *)
+--------------------------+
Wed Mar 8 00:17:36 UTC 2017
patches/packages/mozilla-firefox-45.8.0esr-x86_64-1_slack14.2.txz: Upgraded.
       This release contains security fixes and improvements.
       For more information, see:
       https://www.mozilla.org/security/known-vulnerabilities/firefoxESR.html
       (* Security fix *)
patches/packages/mozilla-thunderbird-45.8.0-x86_64-1_slack14.2.txz: Upgraded.
       This release contains security fixes and improvements.
       For more information, see:
       https://www.mozilla.org/security/known-vulnerabilities/thunderbird.html
       (* Security fix *)
+--------------------------+
Wed Mar 1 19:09:44 UTC 2017
patches/packages/libcgroup-0.41-x86_64-2_slack14.2.txz: Rebuilt.
       This is a bugfix package update.
       Fixed rc.cgred to source the correct config file.
       Don't remove the entire cgroup file system with "rc.cgconfig stop".
       Thanks to chris.willing.
       NOTE: Be sure to install any .new config files.

Quote:

Originally Posted by BW-userx

but now that you point out that it is using i586 then that mirror 14.2 is not defaulting to 64bit?

so it looks like I need to change it to something like

http://slackware.osuosl.org/slackware64-14.2/

taken off there webpage it should read something like

rsync.osuosl.org::slackware64/

instead then 14.2 for the version number and just remove the i586 stuff redo upgrade to be safe keep track of what i remove and look to be sure the x86_64 equivalent is installed before I reboot and hope it fixes everything.

else default to reinstall again ;.. woo hoo

Personally, I wouldn't remove the i486/i586 stuff, I'd just upgradepkg --reinstall over it... but this is uncharted territory for me. I've never done that, so I haven't tried various methods to recover from it.

At least you've got the Slackware installation down by now

BW-userx · 03-30-2017, 02:33 PM

Quote:

Originally Posted by bassmadrigal

My comment was directed at this message you posted when I assume you tried to upload the changelog to the forum. Since changelogs are available online, there's no need to upload the whole thing to the forum.

got ya. my misunderstanding.

Quote:

Originally Posted by bassmadrigal

The changelog's timestamp will show the timestamp of the mirror, which is the time it was last changed. But, if you actually look at the changelog and find that entry, you'll find it under the "Tue Aug 23 19:45:33 UTC 2016" updates.

Code:

+--------------------------+
Tue Aug 23 19:45:33 UTC 2016
patches/packages/gnupg-1.4.21-x86_64-1_slack14.2.txz: Upgraded.
       Fix critical security bug in the RNG [CVE-2016-6313]. An attacker who
       obtains 580 bytes from the standard RNG can trivially predict the next
       20 bytes of output. (This is according to the NEWS file included in the
       source. According to the annoucement linked below, an attacker who obtains
       4640 bits from the RNG can trivially predict the next 160 bits of output.)
       Problem detected by Felix Doerre and Vladimir Klebanov, KIT.
       For more information, see:
       https://lists.gnupg.org/pipermail/gnupg-announce/2016q3/000395.html
       http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-6313
       (* Security fix *)
patches/packages/glib2-2.46.2-x86_64-3_slack14.2.txz: Rebuilt.
       Applied upstream patch to fix a use-before-allocate bug in libgio. Without
       this fix, Thunar will crash if $HOME is on an NFS volume.
       Thanks to Jonathan Woithe.
patches/packages/libgcrypt-1.7.3-x86_64-1_slack14.2.txz: Upgraded.
       Fix critical security bug in the RNG [CVE-2016-6313]. An attacker who
       obtains 580 bytes from the standard RNG can trivially predict the next
       20 bytes of output. (This is according to the NEWS file included in the
       source. According to the annoucement linked below, an attacker who obtains
       4640 bits from the RNG can trivially predict the next 160 bits of output.)
       Problem detected by Felix Doerre and Vladimir Klebanov, KIT.
       For more information, see:
       https://lists.gnupg.org/pipermail/gnupg-announce/2016q3/000395.html
       http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-6313
       (* Security fix *)
patches/packages/linux-4.4.19/*: Upgraded.
       A flaw was found in the implementation of the Linux kernels handling of
       networking challenge ack where an attacker is able to determine the shared
       counter. This may allow an attacker located on different subnet to inject
       or take over a TCP connection between a server and client without having to
       be a traditional Man In the Middle (MITM) style attack.
       Be sure to upgrade your initrd after upgrading the kernel packages.
       If you use lilo to boot your machine, be sure lilo.conf points to the correct
       kernel and initrd and run lilo as root to update the bootloader.
       If you use elilo to boot your machine, you should run eliloconfig to copy the
       kernel and initrd to the EFI System Partition.
       For more information, see:
       http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-5389
       (* Security fix *)
patches/packages/screen-4.4.0-x86_64-2_slack14.2.txz: Rebuilt.
       Reverted a change to /etc/screenrc.new that prevented the console from being
       cleared when a screen session was detached. Thanks to Stuart Winter.
patches/packages/stunnel-5.35-x86_64-2_slack14.2.txz: Rebuilt.
       Fixed incorrect config file name in generate-stunnel-key.sh.
       Thanks to Ebben Aries.

Yes, the date in your log file will show the date the package was installed. Again, when you say you installed the "latest update", it implies you were relatively up-to-date before the 28 MAR updates were pushed... not running a mostly (or completely) unpatched 14.2 install. This is what caused me to state that there were no recent updates that should've affected that package. The five most recent dates there were updates pushed contained the packages below (which covers all of March's updates to this point). As you can see, glib2 shouldn't have been touched in any of those patches.

Code:

Tue Mar 28 20:30:50 UTC 2017
patches/packages/mariadb-10.0.30-x86_64-1_slack14.2.txz: Upgraded.
       This update fixes security issues:
       Crash in libmysqlclient.so.
       Difficult to exploit vulnerability allows low privileged attacker with
       logon to compromise the server. Successful attacks of this vulnerability
       can result in unauthorized access to data.
       For more information, see:
       https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-3302
       https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-3313
       (* Security fix *)
patches/packages/mozilla-firefox-52.0.2esr-x86_64-1_slack14.2.txz: Upgraded.
       Upgraded to new Firefox 52.x ESR branch.
+--------------------------+
Thu Mar 23 21:38:23 UTC 2017
patches/packages/glibc-zoneinfo-2017b-noarch-1_slack14.2.txz: Upgraded.
       This package provides the latest timezone updates.
patches/packages/mcabber-1.0.5-x86_64-1_slack14.2.txz: Upgraded.
       This update fixes a security issue:
       An incorrect implementation of XEP-0280: Message Carbons in multiple XMPP
       clients allows a remote attacker to impersonate any user, including
       contacts, in the vulnerable application's display. This allows for various
       kinds of social engineering attacks.
       For more information, see:
       https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5604
       (* Security fix *)
patches/packages/samba-4.4.12-x86_64-1_slack14.2.txz: Upgraded.
       This update fixes a security issue:
       All versions of Samba prior to 4.6.1, 4.5.7, 4.4.12 are vulnerable to
       a malicious client using a symlink race to allow access to areas of
       the server file system not exported under the share definition.
       For more information, see:
       https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-2619
       (* Security fix *)
+--------------------------+
Thu Mar 16 01:37:05 UTC 2017
patches/packages/pidgin-2.12.0-x86_64-1_slack14.2.txz: Upgraded.
       This update fixes a minor security issue (out of bounds memory read in
       purple_markup_unescape_entity).
       For more information, see:
       https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-2640
       (* Security fix *)
+--------------------------+
Wed Mar 8 00:17:36 UTC 2017
patches/packages/mozilla-firefox-45.8.0esr-x86_64-1_slack14.2.txz: Upgraded.
       This release contains security fixes and improvements.
       For more information, see:
       https://www.mozilla.org/security/known-vulnerabilities/firefoxESR.html
       (* Security fix *)
patches/packages/mozilla-thunderbird-45.8.0-x86_64-1_slack14.2.txz: Upgraded.
       This release contains security fixes and improvements.
       For more information, see:
       https://www.mozilla.org/security/known-vulnerabilities/thunderbird.html
       (* Security fix *)
+--------------------------+
Wed Mar 1 19:09:44 UTC 2017
patches/packages/libcgroup-0.41-x86_64-2_slack14.2.txz: Rebuilt.
       This is a bugfix package update.
       Fixed rc.cgred to source the correct config file.
       Don't remove the entire cgroup file system with "rc.cgconfig stop".
       Thanks to chris.willing.
       NOTE: Be sure to install any .new config files.

Personally, I wouldn't remove the i486/i586 stuff, I'd just upgradepkg --reinstall over it... but this is uncharted territory for me. I've never done that, so I haven't tried various methods to recover from it.

At least you've got the Slackware installation down by now

haha thanks, did that a while back. then I've just been going into Void, I just recently decided to use Slack as a main OS, learning how to use /rc.d/files and config mods to mke it work the way I want and WM configs etc and have been finding out the "new" things that'd probably been out for a long time that have to do with it on keeping it maintained and installing tools that are now out there that where not long long ago.

now I just need to slow down and read the logs thoroughly now. Instead of the Evian woodhead speed reading way just skimming through it picking up key words then seeing the first date and using that one in assuming its meaning.

upgradepkg --reinstall over it
that'd be a thing to try first then check it to see if it changed to the x86_64, then if not remove the i586 and install the x86_64. that last part install pkg should be redundant.

I'll see how it goes. As it is a hypothesis as it stands right now.

BW-userx · 03-30-2017, 05:09 PM

issued

Code:

ls -lrt /var/log/packages | grep i586

gave me list of pkg not needing to be installed.

removepkg

Code:

find /media/slack-mirror/slackware64-14.2 -name pkgshortname*

gave me the one needing to be installed.

installpkg /path/to/pkg/pkgLongName

remove each one then installed the x86_64 version one at a time, rebooted, now I'm back in business.