Salix Forums

Yup, I'm an idiot. I temporarily uninstalled Qt via Gslapt to force a configure script to find the updated version of Qt I have installed outside the PATH. I didn't realize uninstalling Qt would also uninstall wicd. So now my main laptop has no internet access. I know it's possible to access the net without the wicd GUI. But I can't figure out how.

I tried using the USB drive I installed Salix with as a rescue disc to get wicd back. That's when I discovered the laptop no longer recognizes USB drives either. I have two USB sticks that are perfectly operational, I have them plugged in to this laptop right now, but I can't use them to transfer anything to the other laptop because it won't recognize them.

I need to either get online without wicd, wi-fi or hardline, so I can reinstall Qt or I need to get the USB drive to work so I can use it as a rescue disc.


Then I probably need to quit tinkering and just play games like most people do with computers.

I don't think there is a reason for wicd to be removed if qt is uninstalled. I'll have a look but you probably did something else too?

Anyway, plug in an ethernet cable if it's not already plugged in and (assuming your ethernet port is eth0)

gapan wrote:I don't think there is a reason for wicd to be removed if qt is uninstalled. I'll have a look but you probably did something else too?

Anyway, plug in an ethernet cable if it's not already plugged in and

Code: Select all

sudo dhcpcd eth0

(assuming your ethernet port is eth0)

I swear, all I did was mark Qt for removal and click the execute button. Gslapt told me ten packages were going to be removed. I assumed they were all libraries. I have no idea why wicd was included in that list. I got it reinstalled now and it didn't require adding Qt back.

I knew there was a simple way to get online without a GUI. You wouldn't believe how complicated some of the answers were that I found while searching. Thanks for fixing my screwup again. One of these days I'll learn to quit breaking things.

**EDIT**
Apparently the problem isn't wicd itself, but the KDE client. After reinstalling wicd I couldn't get it to open. I decided to install the KDE client and it forced the installation of all the Qt stuff again.

So, the question is why are you using the kde client instead of the bundled gtk one?

Also, if you want to do quick removals/reinstallations, don't use gslapt or slapt-get. Just use "spkg -d". It will never remove anything else.

gapan wrote:So, the question is why are you using the kde client instead of the bundled gtk one?

I don't know. I probably don't need to. I got error messages when I tried running wicd from the menu button after reinstalling. And I think that was because I hadn't started the wicd server as su before trying to run the client. So I will probably go back into Gslapt later and uninstall the KDE client.

I don't remember having the KDE client installed before. I may have done it out of stupidity. That seems to be the reason I do most things on my computer.

rich[~]$ sudo slapt-get --remove qt
Password:
Reading Package Lists...Done
The following packages will be REMOVED:
PyQt attica choqok kdelibs avahi libvirt cmake libdbusmenu-qt phonon
polkit-qt-1 qca qoauth qjson soprano strigi suil ffmpeg aubio libquicktime
mjpegtools gst-plugins-bad qt5 PyQt5 qTox qt5-webkit gst-plugins-bad0 hplip
python-pillow deluge sane simple-scan wicd qt
0 upgraded, 0 reinstalled, 0 newly installed, 33 to remove, 0 not upgraded.
After unpacking 702.7MB disk space will be freed.

Note that the wicd being removed is not the kde client. Next time use spkg; it will only uninstall the package you want.

Interesting.

I also notice you have newer versions of things. Are you running an unstable version for testing? Or are there other repositories I could use to update some things?

Running 14.2 with the normal repositories.

I need to do that upgrade. Still running 14.1. As prone as I am to breaking things I've been worried about following the steps in the wiki.

If your system is running ok, there is really no need to upgrade. If you do want to, take a careful look at the wiki page with instructions. It's straightforward enough really, but it's also easy to get into a muddle if you're new to it. So your caution is sensible.

Salix will continue to support 14.1 as long as Slackware does, that is, for the foreseeable future. We are not Ubuntu.