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.
Latest upgrade (Sat Mar 23 22:49:52 UTC 2013) of network manager's gtk applet broke it's gui. Now I can't modify network connections because these windows never appears. It shows error instead:
Everyone who upgrades his or her slackware-current after the 23-march update should be aware that the upgraded NetworkManager package depends on another upgraded package: l/gdk-pixbuf2 .
You will experience a nasty problem when upgrading NetworkManager first: this will kill your network connection and you will have to install l/gdk-pixbuf2 too before you can get a network connection again.
If you are using slackpkg for the upgrade then you will be affected by this: since slackpkg works alphabetically, NetworkManager will come before all the rest and you will notice that slackpkg is unable to upgrade any of these other packages after NetworkManager... I fixed that on my PC by using /etc/rc.d/rc.inet1.conf to define a configuration for my eth0, then ran "/etc/rc.d/rc.inet1 eth0_restart" and then re-ran "slackpkg upgrade-all".
...
You will experience a nasty problem when upgrading NetworkManager first: this will kill your network connection and you will have to install l/gdk-pixbuf2 too before you can get a network connection again.
If you are using slackpkg for the upgrade then you will be affected by this: since slackpkg works alphabetically, NetworkManager will come before all the rest and you will notice that slackpkg is unable to upgrade any of these other packages after NetworkManager... I fixed that on my PC by using /etc/rc.d/rc.inet1.conf to define a configuration for my eth0, then ran "/etc/rc.d/rc.inet1 eth0_restart" and then re-ran "slackpkg upgrade-all".
...
After having similar problems last year with an update of wget, I have changed /etc/slackpkg/slackpkg.conf
Code:
...
# If this variable is set to "on", all files will be downloaded before the
# requested operation (install or upgrade) is performed. If set to "off",
# then the files will be downloaded and the operation (install/upgrade)
# performed one by one. Default=off
DOWNLOAD_ALL=on
...
now the "upgrade-all" is performed not before all packages are downloaded.
I solved this problem by having a local mirror first by rsync, and then let slackpkg perform the upgrade locally using http and not local filesystem since i found it faster than using local filesystem (file://)
Everyone who upgrades his or her slackware-current after the 23-march update should be aware that the upgraded NetworkManager package depends on another upgraded package: l/gdk-pixbuf2 .
You will experience a nasty problem when upgrading NetworkManager first: this will kill your network connection and you will have to install l/gdk-pixbuf2 too before you can get a network connection again.
Eric
Thank you Eric, but...
Unfortunately, installing the new gdk-pixbuf2 did not solve the problem with the unknown g_type_ensure.
Further checking identified glib2 as the culprit. Upgrading l/glib2-2.34.3-x86_64-1.txz resolved the problem.
My sidestep with my netbook with a WPA2 wireless connection to my router was to:
'/etc/rc.d/rc.networkmanager stop' # Kill the networkmanager daemon.
'pkill wpa_supplicant' # Kill remaining wpa_supplicant process
'rfkill unblock 1' # Unblock wireless LAN interface at index 1 ('rfkill list' for details)
'wpa_supplicant -B -c/etc/wpa_supplicant.conf -iwlan0 -Dwext' # Connect using wpa_supplicant (/etc/wpa_supplicant.conf was already in place)
'dhcpcd' # Get IP address via DHCP
'sh /etc/rc.d/rc.firewall' # Put firewall rules in place
The upgrade using the usual slackpkg dance went on without issue and NetworkManager is working without problems.
Networkmanager applet rebuilt in today's -current update.
Code:
Mon Mar 25 20:31:21 UTC 2013
a/file-5.11-i486-1.txz: Upgraded.
Reverted to file-5.11 to fix segfaults with libmagic. I'm unable to find
patches to fix this for either file itself (file-5.14 doesn't help), or
for affected programs such as nano, so this will have to do for now.
d/llvm-3.2-i486-4.txz: Rebuilt.
Added /usr/bin/$ARCH-slackware-linux-{clang,clang++} symlinks. If these
are present, LLVM/clang will be used to compile itself. Other programs
might need them as well.
xap/network-manager-applet-0.9.8.0-i486-2.txz: Rebuilt.
Patched for new version of GTK+. Thanks to venn.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
