Friday the 13th Massive Upgrade

cwizardone · 07-22-2012, 03:48 PM

As reported earlier, since the Nightmare on Slackware Street upgrades NetworkManager does not work. It reports there is no connection, wired or wireless. I've tried several times, every day, sometimes a few times a day, every time wicd stalls.
Over the last year and a half, on two different boxes, in two different locations, I've tried wicd without much success.
Now that NetworkManager no longer works, I'm forced to use, ugh, wicd, and its behavior has not changed.
It appears to work fine, the first time after a boot up, and then I disconnect and do other things. The next time I try to us wicd it reports there are no networks available. As I've said before, at any given moment, 24/7, in this urban area there are 15-20 wireless networks, two of which I have access to, and one of them, the router is in line of site across the room, about 12 feet away.
When wicd reports there are no networks available I've tried ifconfig, ifconfig -a, ifconfig wlan0, ifconfig wlan0 up, etc. and nothing refreshes the connection. The only things that works is rebooting the machine.
There has to be a better way?
Any suggestions greatly appreciate. How to fix Networkmanager would be even better. It ran perfectly until this last batch of "upgrades."
Thanks.

TommyC7 · 07-22-2012, 05:15 PM

You can always setup /etc/rc.d/rc.inet1.conf and add in any protected networks you wish to access in /etc/wpa_supplicant.conf. That's always worked for me, and just about every distribution I've used has some way of connecting to the internet wirelessly without the use of NetworkManager or wicd.

volkerdi · 07-22-2012, 05:20 PM

Quote:

Originally Posted by cwizardone

Any suggestions greatly appreciate. How to fix Networkmanager would be even better. It ran perfectly until this last batch of "upgrades."

No problems with NetworkManager have been noted here or with other members of the team, nor are there reports of this. How close to a stock install is your system? Any .new config files remaining unresolved?

I'd be curious if you could reproduce the issue on a fresh installation.

cwizardone · 07-22-2012, 06:30 PM

Quote:

Originally Posted by volkerdi

No problems with NetworkManager have been noted here or with other members of the team, nor are there reports of this. How close to a stock install is your system? Any .new config files remaining unresolved?

I'd be curious if you could reproduce the issue on a fresh installation.

This is a fresh install. Third in the last few days (maybe the fourth. I was so tired the other night I lost track). I have just finished going through the -current log on Slackware.com item by item to make sure everything that was supposed to be updated or added has been, and everything that was supposed to be removed has been removed.

At least one other person has reported trouble with NetworkManager in Xfce 4.10. His solution was to install the latest kernel (3.4.6). I haven't been able to make it work in either Xfce 4.10 or KDE 4.8.4. One person has reported trouble with wicd.

I was so tired the other night, actually morning by that time, I said, "screw it" and copied my personal files over to the Xp partition. That lasted about 10 minutes before I delete them and booted back to Slackware64.

leeeoooooo · 07-22-2012, 11:19 PM

I've been trying to upgrade to current from a fresh install of Slack64 under VirtualBox on my XP host with slackpkg, but I'm not getting anywhere.

I set my mirror to osuosl, change slackconfig to DOWNLOAD=on, and install-new fails with gpg errors.

I haven't witnessed at what point the failure occurs (I issue the command, wait for the list of packages to be built, and watch the packages start downloading -- then I'm off to do some other dumb stuff I gotta do -- when I return, I'm greeted with a long list of packages that have failed gpg check.

When I try to run upgrade-all or rerun install-new, I get the message that the gpg key needs to be updated. I run update-gpg and then try to run upgrade-all or rerun install new and I get the "you need to update-gpg" message again.

Whats going on?

Didier Spaier · 07-23-2012, 02:41 AM

I am downloading it right now and plan to install it from scratch.

According to the changelog, some of the problems reported here or elsewhere should automagically disappear, so go test it

EDIT Running Slackware 14 beta/xfce 4.10. So far, so good:
- mount and df show the "real" device for /, no more /dev/root, with huge as well as generic kernels
- no more booting problem after "mkinitrd -c -k 3.2.23-smp -m ext4"
- wicd works for wired and wireless connections
- no more duplicated udev rules for wired/wireless interfaces
- "terminal" doesn't eat more CPU than it should anymore

Congrats to Pat and the Slackware team !

rworkman · 07-23-2012, 02:56 AM

Quote:

Originally Posted by leeeoooooo

I've been trying to upgrade to current from a fresh install of Slack64 under VirtualBox on my XP host with slackpkg, but I'm not getting anywhere.

I set my mirror to osuosl, change slackconfig to DOWNLOAD=on, and install-new fails with gpg errors.

I haven't witnessed at what point the failure occurs (I issue the command, wait for the list of packages to be built, and watch the packages start downloading -- then I'm off to do some other dumb stuff I gotta do -- when I return, I'm greeted with a long list of packages that have failed gpg check.

When I try to run upgrade-all or rerun install-new, I get the message that the gpg key needs to be updated. I run update-gpg and then try to run upgrade-all or rerun install new and I get the "you need to update-gpg" message again.

Whats going on?

Check your system time.

andrew.46 · 07-23-2012, 06:06 AM

Quote:

Originally Posted by TommyC7

There seems to be a lot of things with SCSI drivers though, and I've run into one of them too it seems:

Code:

# cdrecord -scanbus
Cdrecord-ProDVD-ProBD-Clone 3.01a07 (x86_64-unknown-linux-gnu) Copyright (C) 1995-2012 Joerg Schilling
cdrecord: No such file or directory. Cannot open '/dev/pg*'. Cannot open or use SCSI driver.
cdrecord: For possible targets try 'cdrecord -scanbus'.
cdrecord: For possible transport specifiers try 'cdrecord dev=help'.
#

So I went looking into /dev:

Code:

# ls /dev/pg*
/bin/ls: cannot access /dev/pg*: No such file or directory.

I'm not sure if a rebuild of cdrtools would fix this, but seeing as how it's looking for something in /dev I'm going to think it wouldn't.

Just noticed the same issue here:

Code:

root@skamandros/home/andrew# cdrecord -scanbus
Cdrecord-ProDVD-ProBD-Clone 3.01a07 (x86_64-unknown-linux-gnu) Copyright (C) 1995-2012 Joerg Schilling
cdrecord: No such file or directory. Cannot open '/dev/pg*'. Cannot open or use SCSI driver.
cdrecord: For possible targets try 'cdrecord -scanbus'.
cdrecord: For possible transport specifiers try 'cdrecord dev=help'.

sahko · 07-23-2012, 06:37 AM

On a clean 32bit current installation, without e/,f/,kde/,kdei/,t/,tcl/ and y/ but everything else installed, i seem to be having trouble with NM and nm-applet as well.
I'm getting

Code:

** (nm-applet:1957): WARNING **: Failed to register as an agent: (32) No session found for uid 1000

I just started investigating this.

Here's a thread that offers some possible solutions:
https://bbs.archlinux.org/viewtopic.php?pid=1125153

edit: It seems to be related to dbus cause when i plug in eth0 i get this:

Code:

 ** (nm-applet:1957): WARNING **: async_got_type: could not read properties for /org/freedesktop/NetworkManager/ActiveConnection/0: Rejected send message, 2 matched rules; type="method_call", sender=":1.13" (uid=1000 pid=1957 comm="nm-applet ") interface="org.freedesktop.DBus.Properties" member="Get" error name="(unset)" requested_reply="0" destination="org.freedesktop.NetworkManager: (uid=0 pid=1819 comm="/usr/sbin/NetworkManager ")

edit2: FWIW my user is part of the netdev group and im running the huge-smp kernel.

edit3: i found the solution. starting XFCE as user with startxfce4 makes nm-applet not work. What i did was copy over the /root/.xinitrc file to my users home and use startx instead.

bamalabs · 07-23-2012, 10:02 AM

Quote:

Originally Posted by imitheos

Is CONFIG_DEVTMPFS disabled in the kernel that is failing ?

udevd (according to the manpage) should copy the devices from /lib/udev/devices so /dev/urandom should be in /dev. However, for some reason it doesn't get copied (at least in my case and yours) and cryptsetup fails. If CONFIG_DEVTMPFS is enabled (as it is in the generic slackware kernel) then the devices are present and everything works fine.

Quote:

Originally Posted by rworkman

devtmpfs is *required* - go ahead and enable it.

This worked for me. Thanks guys.

volkerdi · 07-23-2012, 10:22 AM

Quote:

Originally Posted by sahko

edit3: i found the solution. starting XFCE as user with startxfce4 makes nm-applet not work. What i did was copy over the /root/.xinitrc file to my users home and use startx instead.

In that case, perhaps "startxfce4 --with-ck-launch" would also do the trick.

rworkman · 07-23-2012, 10:41 AM

Quote:

Originally Posted by volkerdi

In that case, perhaps "startxfce4 --with-ck-launch" would also do the trick.

Yes, but I'd recommend that users just re-run "xwmconfig" so that the new /etc/X11/xinit/xinitrc.xfce is copied to $HOME/.xinitrc and then things should "just work" for them. Luckily, this is only going to be an issue on upgrades...

ponce · 07-23-2012, 11:37 AM

sorry for the question, maybe I am missing something: is there a particular reason why the xinitrc for xfce doesn't has at the top the usual

Code:

userresources=$HOME/.Xresources
usermodmap=$HOME/.Xmodmap
sysresources=/etc/X11/xinit/.Xresources
sysmodmap=/etc/X11/xinit/.Xmodmap

# merge in defaults and keymaps

if [ -f $sysresources ]; then
    xrdb -merge $sysresources
fi

if [ -f $sysmodmap ]; then
    xmodmap $sysmodmap
fi

if [ -f $userresources ]; then
    xrdb -merge $userresources
fi

if [ -f $usermodmap ]; then
    xmodmap $usermodmap
fi

?

colorpurple21859 · 07-23-2012, 03:18 PM

I don't know if anybody else's updates worked this way, but when upgrading a current system to the latest, I have to set the download everything first in slackpkg to keep from breaking while upgrading. However with a fresh install of slack13.37 and upgrading to current using slackpkg the upgrade ran smoothly by doing slackpkg upgrade-all first then running install-new second, without having to set the download everything option. Haven't really had a chance to play with the upgraded systems yet.

TommyC7 · 07-23-2012, 03:29 PM

Quote:

Originally Posted by colorpurple21859

I don't know if anybody else's updates worked this way, but when upgrading a current system to the latest, I have to set the download everything first in slackpkg to keep from breaking while upgrading. However with a fresh install of slack13.37 and upgrading to current using slackpkg the upgrade ran smoothly by doing slackpkg upgrade-all first then running install-new second, without having to set the download everything option. Haven't really had a chance to play with the upgraded systems yet.

There were some packages slackpkg relied on which got upgraded on the Friday the 13th upgrade. You had to either upgrade them manually or not upgrade the system at all until Pat fixed it himself (which he did a few days later). That explains why 13.37 -> current works, but you probably upgraded during the 13th and didn't manually upgrade the packages as we discussed a few pages back on this thread.