[SOLVED] Bug Hunting in Recent Slackware Upgrade (to 15.0)... Help Needed

vtel57 · 01-18-2024, 02:07 PM

As some of you may have noticed or read on THIS thread here earlier this week, I've finally gotten around to upgrading from 14.2 to 15. Everything seemed fine at first, but you know how that goes...

Got some annoying bugs running around. I squashed quite a few already, but have two that are still currently driving me batty. Maybe some of you folk here could point me in the right directions?

Bug No. 1 -> Upgrading TOR Browser from Slackbuild

I previously had v.10.x running on 14.2 and this newly upgraded 15, but I wanted to update all of my SlackBuilds today to the newest version for Slackware 15. All went will till I got to TOR.

I'm getting this error when attempting to run the SlackBuild script:

Code:

# sh tor-browser.SlackBuild

install: target '/tmp/SBo/package-tor-browser/usr/bin/tor-browser' is not a directory

I removed the old v.10 SBo tor directory and it still gives me this error. I've even removed the v.10 TOR Browser completely from my system and tried to run the newer SlackBuild script to install the newer TOR, but same error.

Any ideas? This is Willy Sudiarto Raharjo's script from SlackBuilds.org. Has anyone else had any issues with it?

___

OK, bugaboo Numero Dos: Shutdown and Reboot errors since upgrade to Slackware 15.

The issue I'm having here is that the system will go through all the normal procedures for run levels 0 and 6 (shutdown & reboot), but will not turn power off at the end... it just hangs there. I can see the last of the operations on the screen (mounting/unmounting / on primary drives, powering down apps other hardware, etc.), but then everthing stops just no actual shutting down or rebooting happens.

I just turn the power off to the system at that point. It's not how it's supposed to be working, though. I'd like it to shutdown/reboot like it's supposed to. Anyone seen this before and care to take a poke at what it might be that's causing it?

I've been in BIOS. I've slunk around the dark corners of Xfce's interface and settings. I've read through the logs; nothing is jumping out at me, though. I'm about at my wits end on this one. Any ideas, folks?

Thanks in advance for any assistance!

~Eric L.

lostintime · 01-18-2024, 03:30 PM

Quote:

OK, bugaboo Numero Dos: Shutdown and Reboot errors since upgrade to Slackware 15.

Perhaps try to determine whether this is a desktop environment, display manager, or system issue.

For example, if booting into runlevel 4, log out to the display manager and then try powering off or rebooting. Or, toggle to console tty6 and try either. Or boot to runlevel 3 and try again.

I empathize with updating from 14.2 to 15.0. While many people recommended fresh installs because of the number of changes, I chose to update in place. I have been using Slackware for a couple of decades and have a well-tested backup strategy. I have years of customizations and tweaks. Some people think that backing up /home is all that is needed, but seem to overlook system tweaks and changes and shell scripts. A fresh install means rebuilding all of that from scratch, although backups provide some kind of guide to what might be missing. Curiously, I have done a fresh install only once when moving from 32-bit to 64-bit. Otherwise I always have updated in place. I needed months to fully update from 14.2 to 15.0, maintaining the original 14.2 partition and a concurrent 15.0 partition, and spending an hour or two several times a week tinkering and toying. On some of the home LAN systems I still maintain the original 14.2 partitions because I continue to discover once-in-a-blue-moon mysteries.

I hope you resolve the issues!

vtel57 · 01-18-2024, 04:20 PM

HAHAHA! Hi there, lostintime. You remind me a bit of myself. And yes, I confirmed already that it was a system issue of some sort, not graphic interface only. Shutdown and Reboot are not functioning from the command line (no X running), either.

> I hope you resolve the issues!

Oh, I will. Just takes time and bit of aggravation.

I keep extensive notes on my Slackware and other technical doings. Sadly, I cannot remember exactly when this started... the shutdown/reboot bug, I mean. I seem to think that it happened not immediately after my upgrade-in-place from 14.2 -> 15.0, but shortly thereafter; possibly when I manually upgraded the kernel from the install version 5.15.19 to the recent security upgrade 5.15.145. I didn't specify in my notes when it began exactly. I could revert kernels and see what happens. I may try that.

Previous to this upgrade, I was also pidding around with settings in BIOS on this machine to find out why it would not Suspend properly. And eventhough I've returned to the pre-piddling settings, I'm not sure if the BIOS stuff is related to this bug in any way.

I'll keep tinkering. Not a pressing issue, actually. Neither is the TOR Browser for that matter. I still have the older version of TOR up and running OK.

Thanks for the reply, anyway. I was getting lonely here.

lostintime · 01-18-2024, 05:13 PM

I know you have been around Slackware a long time, but when I run into these issues I start with the obvious:

* Is /etc/rc.d/rc.acpid enabled?

* Anything goofy in /etc/acpi?

* Log in as root from a tty console. Does /sbin/poweroff and /sbin/reboot succeed?

Since you mentioned fiddling with the BIOS, perhaps boot with the 15.0 ISO, log in, and test the same commands. That should disclose Whether the BIOS is causing issues.

Presuming this in place update implies no hardware changes.

vtel57 · 01-18-2024, 07:06 PM

Ah, yes... I've been around the block a few times with Slackware. Unfortunately, though, I haven't been a tweaker/tinkerer with it in a long time. I got comfortable with it and just kicked back and enjoyed using it. So, with that longevity came old age, forgetfulness, and impatience when shit doesn't work.

But anyway...

- yup to /etc/rc.d/acpid
- nothing unusual in /etc/acpi

- # /sbin/reboot worked, but # /sbin/poweroff and shutdown did not work, which jogged a memory cell in my brain somewhere. I thought of something I need to check. Back in a few...

vtel57 · 01-18-2024, 07:59 PM

Well, I believe I've fixed the shutdown/reboot issue. It was a combination of screwups. Firstly, I had not completely reverted some BIOS setting back to their original settings after tweaking and tinkering a few days ago trying to get "Suspend" to work on this machine. During that time I also turned off PolicyKit Authentication Agent in Session Manager for some damned reason that I cannot remember now.

Anyway, after setting the ACPI goodies in BIOS back and reactivating polkit at login, Shutdown/Reboot are now functioning properly from command line and from Whisker Menu graphic interface buttons, so YAY! I'm too old and wise to get carried away with tweaking and tinkering in such a way to lose track of what I did. I must have been having an "elderly" person day that day.

Thanks for the help and suggestions, lostintime. Your mention of the acpi stuff in the post above is what triggered the memory for me.

Now that this is taken care of, the TOR SlackBuild issus should be a breeze. I also am having buggy crashing Firefox issues, but that's whole 'nother can of worms.

Have a wonderful weekend, everyone!

vtel57 · 01-18-2024, 08:06 PM

Not completely solved... still have the TOR SlackBuild issue. However, that'll be trivial compared to the one we were working on above. I'm just glad it's fixed now. I'll mark the thread resolved. I'll figure the TOR thing out eventually.

henca · 01-19-2024, 12:42 AM

Quote:

Originally Posted by vtel57

Code:

# sh tor-browser.SlackBuild

install: target '/tmp/SBo/package-tor-browser/usr/bin/tor-browser' is not a directory

That SlackBuild seems to work fine here:

Code:

slpkg -s sbo tor-browser

did not give me any such error message. Do you have a full Slackware 15.0 installation or did you omit some packages during install/upgrade?

regards Henrik

vtel57 · 01-19-2024, 11:32 AM

Full in situ upgrade. My other SlackBuilds that I had to upgrade manually all worked fine when building them; this one is the only exception.

vtel57 · 01-21-2024, 11:33 AM

Hmm... something interesting that may be the cause/effect of my recent inability to power down/reboot via graphical interface or CLI commands:

Read the bit about "elogind" in the Slackware Announcements for v15.0:

http://www.slackware.com/announce/15.0.php

Also, read this interesting issue re: Suspend/Hibernate in Xfce that I found:

https://unix.stackexchange.com/quest...for-power-user

I believe I'm going to have to investigate this further and possibly seek advice/assistance from a Slackware guru to get this straightened up on my system.

lostintime · 01-21-2024, 02:50 PM

When I updated to 15.0 I never fiddled with any elogind files. All I use are /etc/acpi files. I do not use suspend with any desktops but all of the systems in the home LAN halt and reboot as expected, including VMs. I have two laptops in the house and both suspend as expected. I do not use hibernate anywhere. Doesn't help you directly.

You mentioned, ". . . this one is the only exception." Perhaps share what might be different about this system. For example, in my home LAN just about every single system has something that is different to foil blanket or generic configurations and scripting. And when I added the second laptop I thought I could more or less clone the first laptop. Nothing so easy despite both being Thinkpads. I had to fiddle with the /etc/acpi files to get related functions working on the second laptop.

Another possible variable is if the system is a laptop then probably using NetworkManager. Perhaps some dispatcher scripts are involved.

vtel57 · 01-21-2024, 03:07 PM

I manually upgraded numerous SlackBuilds that I had installed in 14.2... Leafpad, Galculator, LibreOffice, etc. They all compiled correctly and installed/worked. The TOR SlackBuild was the only one to give me any issues. I fixed that in a round-a-bout way last night by downloading the Binary from TOR's website and installing in /opt. Works like a champ.

> When I updated to 15.0 I never fiddled with any elogind files.

Me, neither. I didn't even realize that were going to be an integral part of Slackware 15. I should read the damned Announcements every once in a while, huh?

vtel57 · 01-21-2024, 03:16 PM

Oh, and this box, which I recently revived, due to a catastrophic failure of my previous Primary system just before Christmas, never was capable of Suspend, even when brand new (in 2013). I just didn't bother back then to try to figure it out. However, since Suspend worked fine in the next machine and I had gotten used to using it on a daily basis, I figured I'd try to tinker and fiddle a bit to see if I could get it to work in this one.

That article I link to above where the fellow is successful at getting Suspend to work on his Slackware/Xfce system after editing policy files is interesting. I may give that a shot. If it works, fine. If not, no harm done.

Quote:

Solution found.

a) I have created 3 files, one for brightness, one for suspend, one for hibernate

/etc/polkit-1/rules.d/88-suspend.rules
/etc/polkit-1/rules.d/88-hibernate.rules
/etc/polkit-1/rules.d/89-backlight.rules

b) the contents of files: I assign to the group power the possibility to decrease brightness, suspend and hibernate the os, of course your user must be in the group power(as secondary or primary)

Code:

cat /etc/polkit-1/rules.d/88-hibernate.rules
polkit.addRule(function(action, subject) {
    if (action.id == "org.freedesktop.login1.hibernate" &&
        subject.isInGroup("power")) {
        return polkit.Result.YES;
    }
});

Code:

cat /etc/polkit-1/rules.d/88-suspend.rules
polkit.addRule(function(action, subject) {
    if (action.id == "org.freedesktop.login1.suspend" &&
        subject.isInGroup("power")) {
        return polkit.Result.YES;
    }
});

Code:

cat /etc/polkit-1/rules.d/89-blacklight.rules
polkit.addRule(function(action, subject) {
    if (action.id == "org.xfce.power.backlight-helper" &&
        subject.isInGroup("power")) {
        return polkit.Result.YES;
    }
});

c) restart power-manager

Code:

xfce4-power-manager --restart

Tested and works fine from xfce4 gui and loginctl command line

vtel57 · 01-22-2024, 05:50 PM

Well, I'm tired and aggravated. I still cannot Hibernate/Suspend or Shutdown. At least Reboot is working, huh?

I did solve the crashing Firefox by reverting to the older release (121.0). Working fine and dandy for a couple days already. I hope when FF puts out their next release that it doesn't also carry the bug that I was experiencing in 121.0.1.

Anyway, been searching online for days now. Can't find any specific information or assistance with this shutdown/hibernate baloney. I've been reading logs and resetting BIOS settings to do with ACPI and related crap. I also studied the polkit rules, inittab status, and /etc/rc.d settings. I'm not seeing any issues that would be causing me strange issues.

I probably need to just walk away from it for a few days so that ericsbane06 doesn't end up like ericsbane07 did... a victim of my lost patience.

I'm out... everyone have a great week!

rkelsen · 01-22-2024, 06:08 PM

Quote:

Originally Posted by lostintime

I empathize with updating from 14.2 to 15.0. While many people recommended fresh installs because of the number of changes, I chose to update in place. I have been using Slackware for a couple of decades and have a well-tested backup strategy. I have years of customizations and tweaks. Some people think that backing up /home is all that is needed, but seem to overlook system tweaks and changes and shell scripts.

One way to handle this, which I figured out a long time ago, is to put all of your custom scripts, tweaks and customizations under /usr/local. On a fresh installation, there are no files under there, and that whole sub-tree is included in paths, desktop configurations, etc. For example, you can put a custom launcher into /usr/local/share/applications, and it'll show up on your desktop menus.

One of the first things I do on a clean installation is restore my backed up copy of my /usr/local tree. Boom. Customisation done.