[SOLVED] Can't launch chrome or firefox after slackpkg upgrade

dsotm · 04-12-2017, 09:03 PM

Can't launch either program, probably others as well, accidentally cancelled the process halfway through the upgrade and restarted. When I added the multilib packages I get the following error:

Code:

cat: /var/log/scripts/autoload: No such file or directory
cat: /var/log/scripts/bye: No such file or directory
cat: /var/log/scripts/chdir: No such file or directory
cat: /var/log/scripts/declare: No such file or directory
cat: /var/log/scripts/float: No such file or directory
cat: /var/log/scripts/history: No such file or directory
cat: /var/log/scripts/integer: No such file or directory
cat: /var/log/scripts/local: No such file or directory
cat: /var/log/scripts/logout: No such file or directory
cat: /var/log/scripts/pushln: No such file or directory
cat: /var/log/scripts/r: No such file or directory
cat: /var/log/scripts/readonly: No such file or directory
cat: /var/log/scripts/rehash: No such file or directory
cat: /var/log/scripts/type: No such file or directory
cat: /var/log/scripts/unalias: No such file or directory
cat: /var/log/scripts/unfunction: No such file or directory
cat: /var/log/scripts/where: No such file or directory
cat: /var/log/scripts/which: No such file or directory
cat: /var/log/scripts/zprofile: No such file or directory
cat: /var/log/scripts/zsh-5.3.1: No such file or directory

Get the following when I try to launch chrome:

Code:

--2017-04-12 19:02:12--  https://clients2.google.com/cr/report
Resolving clients2.google.com... 2607:f8b0:4007:80b::200e, 
216.58.193.206
Connecting to clients2.google.com|2607:f8b0:4007:80b::200e|:443... 
connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: ‘/dev/fd/3’


     0K Crash dump id:   9efc120e80000000 
                                                     663K=0s

Segmentation fault

Any ideas how I might go about fixing this or am I going to have to reinstall?

bassmadrigal · 04-12-2017, 09:25 PM

If you cancelled during the upgrade, you could be running some frankenstein version of Slackware-current that is quite possibly broken. I would first try to reinstall using slackpkg and see if that fixes the issue.

Code:

slackpkg reinstall slackware64

dsotm · 04-12-2017, 11:18 PM

Quote:

Originally Posted by bassmadrigal

If you cancelled during the upgrade, you could be running some frankenstein version of Slackware-current that is quite possibly broken. I would first try to reinstall using slackpkg and see if that fixes the issue.

Code:

slackpkg reinstall slackware64

Gave that a try and still having the same issue, noticed the same missing files error when some packages were installing

bassmadrigal · 04-13-2017, 12:42 AM

Unfortunately, that probably means you broke some fairly important applications. There's several ways to recover from this, but the easiest would probably be to just boot off your installation media and reinstall Slackware without formatting anything. That should keep all your 3rd-party applications intact and it should fix your installation. For alternative methods to fixing it, we'd need more information on your errors (or is it just the errors in the first post?), and possibly a list of the last 20 or so installed and removed packages.

dsotm · 04-13-2017, 11:04 AM

Quote:

Originally Posted by bassmadrigal

Unfortunately, that probably means you broke some fairly important applications. There's several ways to recover from this, but the easiest would probably be to just boot off your installation media and reinstall Slackware without formatting anything. That should keep all your 3rd-party applications intact and it should fix your installation. For alternative methods to fixing it, we'd need more information on your errors (or is it just the errors in the first post?), and possibly a list of the last 20 or so installed and removed packages.

Going to try this when I get home tonight, forgot to bring the laptop to work today unfortunately. Didn't know this was even an option, much better than starting from scratch.

bassmadrigal · 04-13-2017, 11:42 AM

The same thing can be done by running upgradepkg --reinstall slackware64/*/*.t?z, but many would likely find the installer easier. And that is also assuming your upgradepkg package isn't broken (using the installer wouldn't be affected since it uses an internal upgradepkg, not the one installed to the system).

dsotm · 04-13-2017, 10:42 PM

Installing without formatting did the trick, thanks for your help!