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.
today i encountered another never-seen before odd behaviour on my slackware-current box.
I was trying to update the system using the usual slackpkg update/install-new/upgrade-all.
Slackpkg update and install-new worked as usual, no issues. When I launched slackpkg upgrade-all at some point it stopped with an error referencing something about line 79 on slackpkg+. Once that happen, anything i tried to input on the console returned a 'Segmentation Fault' error and the system became 100% unresponsive (well, except being able to type something on console). Hard reset necessary to reboot the system -> kernel panic
Launched the installation CD -> mounted the partition on /mnt -> pkgtool -> system fixed.
Maybe I was distracted and I missed to upgrade slackpkg+. So, repeat -> slackpkg update > install-new > upgrade-all -> same error msg.
Upgrade stopped with a segmentation error at line 79 of slackpkg+ (i tried to copy the error on a file so that i could post it here, but once again, completely unresponsive system; nothing launched; not even the shut down/restart button; so, hard reset again and repeated the repair.
Now, does anyone have a clue of what is happening here? where can i find the slackpkg file log to view the error? (i looked on /etc/slackpkg, /var/log and /var/lock)
thanks
p.s.: interestingly, i upgraded my laptop almost simultaneously and it went flawless (usually, it happens the other way around as the laptop is older)
This morning i tried to run slackpkg update again and I was reminded
Quote:
No changes in ChangeLog.txt between your last update and now.
Do you really want to download all other files (y/N)?
I chose 'y' and continued as per usual; the upgrade stopped again on that 'line 79 segmentation fault' error returning an unresponsive system (being old school I didnt think of taking a picture of the screen with my mobile and attach it here). Interestingly, I looked at line 79 of /etc/slackpkg/slackpkgplus.conf and line 79 is empty
So, I guess the upgrade is still running on the 1st 'slackpkg update' I started last night.
I would like to try to delete that file and launch 'slackpkg update' again (just in case) but I can't find the file; (sometimes , I tried to run two instances of slackpkg, inadvertently, and I get reminded to delete the .../.../file as slackpkg cannot run two instances simultaneously; so far, I have looked in to /var/log, /var/lock, /run/lock, ).
Could someone remind me where that file is? so that i can try, once more to upgrade my slackware current?
However, something strange happened the 1st time I run
Quote:
DEBUG=1 bash -x slackpkg upgrade-all 2>&1 | tee slackpkg.trace
it stopped with the usual small blue-window of packages installed and, it stopped outlining something about 'glibc' being outdated and a newer version was available.
So, I am trying this option: as i am typing this reply, I upgraded 'glibc' and about to reboot.
However, something strange happened the 1st time I run
.... something about 'glibc' being outdated and a newer version was available.
it seems that the problem was caused by the older 'glibc' package; as soon as upgraded 'glibc' the upgrade-all finished smoothly with no errors.
Quote:
Originally Posted by zerouno
DEBUG=1 bash -x slackpkg upgrade-all 2>&1 | tee slackpkg.trace
I am not sure how important it was for you to read the output but since 'slackpkg upgrade-all' worked this time I didn't think it would show the same output.
Thank you 'zerouno' and everyone else who tried to help (without that debug line I wouldn't have seen the system outlining the older 'glibc')
I guess I will mark this thread a [Solved], (although I am not sure why it needed solving this way whilst the laptop also running slackware-current on 64b did not).
good.
if it works it is no longer important seeing the output
However it was a curios problem.
The upgrade-all command as the first thing does upgrade glibc then it continues with the other packages.
yep, but for some weird reason this time it didn't (i am not sure whether this could be the reason: often, while I run 'slackpkg update/install-new/upgrade-all', i do other things i.e.: browsing the net, opening&closing files, etc.... and I think i was doing something like that while waiting for the upgrade to finish)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.