networkmanager (eth0 and wlan0) and ifup wifi not working after monster update

English Network/Internet
#1

Hi,

I’ve had 11.4/KDE working pretty well on dual boot Asus G73SW for a few weeks now. Only issues were the FN-* functions that control keyboard lights and whatnot but no biggie since the essential worked.

The last couple of days the update notification was indicating 1,201 updates to be made. Yeah it seemed extreme but I googled around and checked the forums and there was nothing related. I figured I might be missing some packages since I installed from the live KDE CD (still 1202 updates???). So I updated. Big mistake!!! Ever since NetworkManager cannot connect to the internet, be it wired or wireless. Initially it could not even see my home network but it picked it up after I removed the plasmoid from the panel and reinstalled it. However it doesn’t respond when I click the network icon and still no connection.

I managed to get eth0 working with ifup but not wifi. The last part of network manager log file is quoted below. I can send the whole thing to whoever is interested. I can’t make sense of it but maybe someone on the forums can.

Thanks in advance…

Z.


Jul 13 11:09:08 linux-yy10 NetworkManager[1649]: <info> NetworkManager (version 0.8.9997) is starting...
Jul 13 11:09:08 linux-yy10 NetworkManager[1649]: <info> Read config file /etc/NetworkManager/nm-system-settings.conf
Jul 13 11:09:08 linux-yy10 NetworkManager[1649]: <info> VPN: loaded org.freedesktop.NetworkManager.vpnc
Jul 13 11:09:08 linux-yy10 NetworkManager[1649]: <info> VPN: loaded org.freedesktop.NetworkManager.pptp
Jul 13 11:09:08 linux-yy10 NetworkManager[1649]: <info> VPN: loaded org.freedesktop.NetworkManager.openvpn
Jul 13 11:09:08 linux-yy10 NetworkManager[1649]: <info> Loaded plugin ifcfg-suse: (C) 2008 Novell, Inc.  To report bugs please use the NetworkManager mailing list.
Jul 13 11:09:08 linux-yy10 NetworkManager[1649]: <info> Loaded plugin keyfile: (c) 2007 - 2010 Red Hat, Inc.  To report bugs please use the NetworkManager mailing list.
Jul 13 11:09:08 linux-yy10 NetworkManager[1649]:    keyfile: parsing Auto eth0 ... 
Jul 13 11:09:08 linux-yy10 NetworkManager[1649]:    keyfile:     read connection 'Auto eth0'
Jul 13 11:09:08 linux-yy10 NetworkManager[1649]: <info> trying to start the modem manager...
Jul 13 11:09:08 linux-yy10 NetworkManager[1649]: <info> monitoring kernel firmware directory '/lib/firmware'.
Jul 13 11:09:08 linux-yy10 NetworkManager[1649]: <info> found WiFi radio killswitch rfkill1 (at /sys/devices/pci0000:00/0000:00:1c.1/0000:03:00.0/ieee80211/phy0/rfkill1) (driver (unknown))
Jul 13 11:09:08 linux-yy10 NetworkManager[1649]: <info> WiFi enabled by radio killswitch; enabled by state file
Jul 13 11:09:08 linux-yy10 NetworkManager[1649]: <info> WWAN enabled by radio killswitch; enabled by state file
Jul 13 11:09:08 linux-yy10 NetworkManager[1649]: <info> WiMAX enabled by radio killswitch; enabled by state file
Jul 13 11:09:08 linux-yy10 NetworkManager[1649]: <info> Networking is enabled by state file
Jul 13 11:09:08 linux-yy10 NetworkManager[1649]: <info> Clearing nscd hosts cache.
Jul 13 11:09:08 linux-yy10 NetworkManager[1649]: <info> Setting system hostname to 'linux-yy10.site' (from system configuration)
Jul 13 11:09:08 linux-yy10 NetworkManager[1649]: <info> (wlan0): driver supports SSID scans (scan_capa 0x01).
Jul 13 11:09:08 linux-yy10 NetworkManager[1649]: <info> (wlan0): new 802.11 WiFi device (driver: 'ath9k' ifindex: 3)
Jul 13 11:09:08 linux-yy10 NetworkManager[1649]: <info> (wlan0): exported as /org/freedesktop/NetworkManager/Devices/0
Jul 13 11:09:08 linux-yy10 NetworkManager[1649]: <info> (wlan0): now managed
Jul 13 11:09:08 linux-yy10 NetworkManager[1649]: <info> (wlan0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Jul 13 11:09:08 linux-yy10 NetworkManager[1649]: <info> (wlan0): bringing up device.
Jul 13 11:09:08 linux-yy10 NetworkManager[1649]: <info> (wlan0): preparing device.
Jul 13 11:09:08 linux-yy10 NetworkManager[1649]: <info> (wlan0): deactivating device (reason: 2).
Jul 13 11:09:08 linux-yy10 NetworkManager[1649]: marshal_object: assertion `g_variant_is_object_path (path)' failed
Jul 13 11:09:08 linux-yy10 NetworkManager[1649]: failed to marshal parameter 1 for signal DeviceAdded
Jul 13 11:09:08 linux-yy10 NetworkManager[1649]: marshal_object: assertion `g_variant_is_object_path (path)' failed
Jul 13 11:09:08 linux-yy10 NetworkManager[1649]: failed to marshal parameter 1 for signal DeviceAdded
Jul 13 11:09:08 linux-yy10 NetworkManager[1649]: <info> (eth0): carrier is OFF
Jul 13 11:09:08 linux-yy10 NetworkManager[1649]: <info> (eth0): new Ethernet device (driver: 'r8169' ifindex: 2)
Jul 13 11:09:08 linux-yy10 NetworkManager[1649]: <info> (eth0): exported as /org/freedesktop/NetworkManager/Devices/1
Jul 13 11:09:08 linux-yy10 NetworkManager[1649]: <info> (eth0): now managed
Jul 13 11:09:08 linux-yy10 NetworkManager[1649]: <info> (eth0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Jul 13 11:09:08 linux-yy10 NetworkManager[1649]: <info> (eth0): bringing up device.
Jul 13 11:09:08 linux-yy10 NetworkManager[1649]: <info> (eth0): preparing device.
Jul 13 11:09:08 linux-yy10 NetworkManager[1649]: <info> (eth0): deactivating device (reason: 2).
Jul 13 11:09:08 linux-yy10 NetworkManager[1649]: marshal_object: assertion `g_variant_is_object_path (path)' failed
Jul 13 11:09:08 linux-yy10 NetworkManager[1649]: failed to marshal parameter 1 for signal DeviceAdded
Jul 13 11:09:08 linux-yy10 NetworkManager[1649]: marshal_object: assertion `g_variant_is_object_path (path)' failed
Jul 13 11:09:08 linux-yy10 NetworkManager[1649]: failed to marshal parameter 1 for signal DeviceAdded
Jul 13 11:09:08 linux-yy10 NetworkManager[1649]: <info> modem-manager is now available
Jul 13 11:09:08 linux-yy10 NetworkManager[1649]: <info> wpa_supplicant started
Jul 13 11:09:08 linux-yy10 nm-dispatcher.action: Script '/etc/NetworkManager/dispatcher.d/netcontrol_services' exited with error status 127.
Jul 13 11:09:08 linux-yy10 NetworkManager[1649]: <info> (wlan0): supplicant interface state: starting -> ready
Jul 13 11:09:08 linux-yy10 NetworkManager[1649]: <info> (wlan0): device state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42]
Jul 13 11:09:08 linux-yy10 NetworkManager[1649]: <info> (wlan0): supplicant interface state: ready -> inactive
Jul 13 11:09:10 linux-yy10 NetworkManager[1649]: marshal_object: assertion `g_variant_is_object_path (path)' failed
Jul 13 11:09:10 linux-yy10 NetworkManager[1649]: failed to marshal parameter 1 for signal AccessPointAdded
Jul 13 11:09:10 linux-yy10 NetworkManager[1649]: marshal_object: assertion `g_variant_is_object_path (path)' failed
Jul 13 11:09:10 linux-yy10 NetworkManager[1649]: failed to marshal parameter 1 for signal AccessPointAdded
Jul 13 11:10:08 linux-yy10 NetworkManager[1649]: <info> (eth0): carrier now ON (device state 20)
Jul 13 11:10:08 linux-yy10 NetworkManager[1649]: <info> (eth0): device state change: unavailable -> disconnected (reason 'carrier-changed') [20 30 40]
Jul 13 11:10:08 linux-yy10 NetworkManager[1649]: <info> Activation (eth0) starting connection 'Auto eth0'
Jul 13 11:10:08 linux-yy10 NetworkManager[1649]: <info> (eth0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Jul 13 11:10:08 linux-yy10 NetworkManager[1649]: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) scheduled...
Jul 13 11:10:08 linux-yy10 NetworkManager[1649]: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) started...
Jul 13 11:10:08 linux-yy10 NetworkManager[1649]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) scheduled...
Jul 13 11:10:08 linux-yy10 NetworkManager[1649]: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) complete.
Jul 13 11:10:08 linux-yy10 NetworkManager[1649]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) starting...
Jul 13 11:10:08 linux-yy10 NetworkManager[1649]: <info> (eth0): device state change: prepare -> config (reason 'none') [40 50 0]
Jul 13 11:10:08 linux-yy10 NetworkManager[1649]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) successful.
Jul 13 11:10:08 linux-yy10 NetworkManager[1649]: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) scheduled.
Jul 13 11:10:08 linux-yy10 NetworkManager[1649]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) complete.
Jul 13 11:10:08 linux-yy10 NetworkManager[1649]: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) started...
Jul 13 11:10:08 linux-yy10 NetworkManager[1649]: <info> (eth0): device state change: config -> ip-config (reason 'none') [50 70 0]
Jul 13 11:10:08 linux-yy10 NetworkManager[1649]: <info> Activation (eth0) Beginning DHCPv4 transaction (timeout in 45 seconds)
Jul 13 11:10:08 linux-yy10 NetworkManager[1649]: <info> dhclient started with pid 3136
Jul 13 11:10:08 linux-yy10 NetworkManager[1649]: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) complete.
Jul 13 11:10:08 linux-yy10 NetworkManager[1649]: <info> (eth0): DHCPv4 state changed nbi -> preinit
Jul 13 11:10:10 linux-yy10 NetworkManager[1649]: <info> (eth0): DHCPv4 state changed preinit -> reboot
Jul 13 11:10:10 linux-yy10 NetworkManager[1649]: <info> Activation (eth0) Stage 4 of 5 (IP4 Configure Get) scheduled...
Jul 13 11:10:10 linux-yy10 NetworkManager[1649]: <info> Activation (eth0) Stage 4 of 5 (IP4 Configure Get) started...
Jul 13 11:10:10 linux-yy10 NetworkManager[1649]: <info>   address 192.168.1.105
Jul 13 11:10:10 linux-yy10 NetworkManager[1649]: <info>   prefix 24 (255.255.255.0)
Jul 13 11:10:10 linux-yy10 NetworkManager[1649]: <info>   gateway 192.168.1.1
Jul 13 11:10:10 linux-yy10 NetworkManager[1649]: <info>   nameserver '24.200.243.189'
Jul 13 11:10:10 linux-yy10 NetworkManager[1649]: <info>   nameserver '24.200.241.37'
Jul 13 11:10:10 linux-yy10 NetworkManager[1649]: <info>   nameserver '24.201.245.77'
Jul 13 11:10:10 linux-yy10 NetworkManager[1649]: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) scheduled...
Jul 13 11:10:10 linux-yy10 NetworkManager[1649]: <info> Activation (eth0) Stage 4 of 5 (IP4 Configure Get) complete.
Jul 13 11:10:10 linux-yy10 NetworkManager[1649]: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) started...
Jul 13 11:10:11 linux-yy10 NetworkManager[1649]: <info> Clearing nscd hosts cache.
Jul 13 11:10:11 linux-yy10 NetworkManager[1649]: <info> (eth0): device state change: ip-config -> activated (reason 'none') [70 100 0]
Jul 13 11:10:11 linux-yy10 NetworkManager[1649]: <info> Policy set 'Auto eth0' (eth0) as default for IPv4 routing and DNS.
Jul 13 11:10:11 linux-yy10 NetworkManager[1649]: <info> Activation (eth0) successful, device activated.
Jul 13 11:10:11 linux-yy10 NetworkManager[1649]: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) complete.
Jul 13 11:10:11 linux-yy10 nm-dispatcher.action: Script '/etc/NetworkManager/dispatcher.d/autofs' exited with error status 1.
Jul 13 11:10:12 linux-yy10 nm-dispatcher.action: Script '/etc/NetworkManager/dispatcher.d/nfs' exited with error status 2.
Jul 13 11:11:10 linux-yy10 NetworkManager[1649]: <info> caught signal 15, shutting down normally.
Jul 13 11:11:10 linux-yy10 NetworkManager[1649]: <warn> quit request received, terminating...
Jul 13 11:11:10 linux-yy10 NetworkManager[1649]: <info> (wlan0): now unmanaged
Jul 13 11:11:10 linux-yy10 NetworkManager[1649]: <info> (wlan0): device state change: disconnected -> unmanaged (reason 'removed') [30 10 36]
Jul 13 11:11:10 linux-yy10 NetworkManager[1649]: <info> (wlan0): cleaning up...
Jul 13 11:11:10 linux-yy10 NetworkManager[1649]: marshal_object: assertion `g_variant_is_object_path (path)' failed
Jul 13 11:11:10 linux-yy10 NetworkManager[1649]: failed to marshal parameter 1 for signal AccessPointRemoved
Jul 13 11:11:10 linux-yy10 NetworkManager[1649]: marshal_object: assertion `g_variant_is_object_path (path)' failed
Jul 13 11:11:10 linux-yy10 NetworkManager[1649]: failed to marshal parameter 1 for signal AccessPointRemoved
Jul 13 11:11:10 linux-yy10 NetworkManager[1649]: <info> (wlan0): taking down device.
Jul 13 11:11:10 linux-yy10 NetworkManager[1649]: marshal_object: assertion `g_variant_is_object_path (path)' failed
Jul 13 11:11:10 linux-yy10 NetworkManager[1649]: failed to marshal parameter 1 for signal DeviceRemoved
Jul 13 11:11:10 linux-yy10 NetworkManager[1649]: marshal_object: assertion `g_variant_is_object_path (path)' failed
Jul 13 11:11:10 linux-yy10 NetworkManager[1649]: failed to marshal parameter 1 for signal DeviceRemoved
Jul 13 11:11:10 linux-yy10 NetworkManager[1649]: marshal_object: assertion `g_variant_is_object_path (path)' failed
Jul 13 11:11:10 linux-yy10 NetworkManager[1649]: failed to marshal parameter 1 for signal DeviceRemoved
Jul 13 11:11:10 linux-yy10 NetworkManager[1649]: marshal_object: assertion `g_variant_is_object_path (path)' failed
Jul 13 11:11:10 linux-yy10 NetworkManager[1649]: failed to marshal parameter 1 for signal DeviceRemoved
Jul 13 11:11:10 linux-yy10 NetworkManager[1649]: <info> Clearing nscd hosts cache.
Jul 13 11:11:10 linux-yy10 NetworkManager[1649]: <info> exiting (success)
#2

Only immedialtly after first install there will be a massive update. After that, YaST > Software > Online update gives me only a few Security/recommended updates from the Update repo in a week at maximum.

#3

I am aware of that. I usually do it like that do and am pretty sure I did it for this install, two or three weeks ago. Since I installed I’ve had 3 or 4 updates through the panel plasmoid and they were never more than a dozen features at a time. This is why this particular update seemed weird. I am wondering if it isn’t a bug in 11.4. Mind you I’ve been using/installing opensuse for over 7 years now.

There’s something I noticed while trying to switch to the Network Manager through Yast2, Network Devices. It reports at the very end that there is no network found, right after the “Run SuSeconfig” step at the very end.

#4

I guess that with the “panel plasmoid” you mean PackageKit. There is a general consensus here that you should not use that, but native openSUSE toole like YaST and zypper.

#5

Yep that’s the one! I disabled it yesterday.

Working right now through Cygwin from the windows boot until I have time to fix this. Any idea how to reinstall the networking package?

#6

Yep that’s the one! I disabled it yesterday.

Working right now through Cygwin from the windows boot until I have time to fix this. Any idea how to reinstall the networking package?

#7

I still do not understand where you got all those updates from. Do you have many repos and thus made a mess of the whole? Post the output of

zypper lr -d
#8

Yes I have a lot of repos but I can’t reboot into linux until this afternoon. Will post it then.

#9

Here it is:


#  | Alias                                               | Name                                                | Enabled | Refresh | Priority | Type   | URI                                                                                                          | Service
---+-----------------------------------------------------+-----------------------------------------------------+---------+---------+----------+--------+--------------------------------------------------------------------------------------------------------------+--------
 1 | download.nvidia.com-opensuse                        | nVidia Graphics Drivers                             | Yes     | Yes     |   99     | rpm-md | ftp://download.nvidia.com/opensuse/11.4/                                                                     |        
 2 | download.opensuse.org-Community                     | openSUSE BuildService - Mono:Community              | Yes     | Yes     |   99     | rpm-md | http://download.opensuse.org/repositories/Mono:/Community/openSUSE_11.4/                                     |        
 3 | download.opensuse.org-Education                     | openSUSE BuildService - Education                   | Yes     | Yes     |   99     | rpm-md | http://download.opensuse.org/repositories/Education/openSUSE_11.4/                                           |        
 4 | download.opensuse.org-Extra                         | openSUSE BuildService - KDE:Extra                   | Yes     | Yes     |   99     | rpm-md | http://download.opensuse.org/repositories/KDE:/Extra/openSUSE_11.4/                                          |        
 5 | download.opensuse.org-STABLE                        | openSUSE BuildService - OpenOffice.org              | Yes     | Yes     |   99     | rpm-md | http://download.opensuse.org/repositories/OpenOffice.org:/STABLE/openSUSE_11.4/                              |        
 6 | download.opensuse.org-UpdatedApps                   | openSUSE BuildService - KDE:UpdatedApps             | Yes     | Yes     |   99     | rpm-md | http://download.opensuse.org/repositories/KDE:/UpdatedApps/openSUSE_11.4/                                    |        
 7 | download.opensuse.org-Wine                          | openSUSE BuildService - Wine CVS Builds             | Yes     | Yes     |   99     | rpm-md | http://download.opensuse.org/repositories/Emulators:/Wine/openSUSE_11.4/                                     |        
 8 | download.opensuse.org-filesystems                   | openSUSE BuildService - filesystems                 | Yes     | Yes     |   99     | rpm-md | http://download.opensuse.org/repositories/filesystems/openSUSE_11.4/                                         |        
 9 | download.opensuse.org-games                         | openSUSE BuildService - Games                       | Yes     | Yes     |   99     | rpm-md | http://download.opensuse.org/repositories/games/openSUSE_11.4/                                               |        
10 | download.opensuse.org-mozilla                       | openSUSE BuildService - Mozilla                     | Yes     | Yes     |   99     | rpm-md | http://download.opensuse.org/repositories/mozilla/openSUSE_11.4/                                             |        
11 | download.opensuse.org-openSUSE_11.4_Update_standard | openSUSE BuildService - Virtualization (VirtualBox) | Yes     | Yes     |   99     | rpm-md | http://download.opensuse.org/repositories/Virtualization:/VirtualBox_backports/openSUSE_11.4_Update_standard |        
12 | download.opensuse.org-packages                      | openSUSE BuildService - Java:packages               | Yes     | Yes     |   99     | rpm-md | http://download.opensuse.org/repositories/Java:/packages/openSUSE_11.4/                                      |        
13 | download.opensuse.org-perl                          | openSUSE BuildService - devel:languages:perl        | Yes     | Yes     |   99     | rpm-md | http://download.opensuse.org/repositories/devel:/languages:/perl/openSUSE_11.4/                              |        
14 | download.opensuse.org-php                           | openSUSE BuildService - PHP                         | Yes     | Yes     |   99     | rpm-md | http://download.opensuse.org/repositories/server:/php/openSUSE_11.4/                                         |        
15 | download.opensuse.org-python                        | openSUSE BuildService - devel:languages:python      | Yes     | Yes     |   99     | rpm-md | http://download.opensuse.org/repositories/devel:/languages:/python/openSUSE_11.4/                            |        
16 | download.opensuse.org-webcam                        | openSUSE BuildService - Drivers for webcams         | Yes     | Yes     |   99     | rpm-md | http://download.opensuse.org/repositories/drivers:/webcam/openSUSE_11.4/                                     |        
17 | google-talkplugin                                   | google-talkplugin                                   | Yes     | Yes     |   99     | rpm-md | http://dl.google.com/linux/talkplugin/rpm/stable/x86_64                                                      |        
18 | openSUSE:Factory                                    | openSUSE:Factory                                    | Yes     | Yes     |   99     | yast2  | http://download.opensuse.org/factory/repo/oss/                                                               |        
19 | opensuse-guide.org-repo                             | libdvdcss repository                                | Yes     | Yes     |   99     | rpm-md | http://opensuse-guide.org/repo/11.4/                                                                         |        
20 | packman.inode.at-suse                               | Packman Repository                                  | Yes     | Yes     |   99     | rpm-md | http://packman.inode.at/suse/openSUSE_11.4/                                                                  |        
21 | repo-debug                                          | openSUSE-11.4-Debug                                 | No      | Yes     |   99     | NONE   | http://download.opensuse.org/debug/distribution/11.4/repo/oss/                                               |        
22 | repo-debug-update                                   | openSUSE-11.4-Update-Debug                          | No      | Yes     |   99     | NONE   | http://download.opensuse.org/debug/update/11.4/                                                              |        
23 | repo-non-oss                                        | openSUSE-11.4-Non-Oss                               | Yes     | Yes     |   99     | yast2  | http://download.opensuse.org/distribution/11.4/repo/non-oss/                                                 |        
24 | repo-oss                                            | openSUSE-11.4-Oss                                   | Yes     | Yes     |   99     | yast2  | http://download.opensuse.org/distribution/11.4/repo/oss/                                                     |        
25 | repo-source                                         | openSUSE-11.4-Source                                | No      | Yes     |   99     | NONE   | http://download.opensuse.org/source/distribution/11.4/repo/oss/                                              |        
26 | repo-update                                         | openSUSE-11.4-Update                                | Yes     | Yes     |   99     | rpm-md | http://download.opensuse.org/update/11.4/                                                                    |
#10

Latest update:

I got the wireless working through Yast2 by turning off the wired connection, setting up the wireless one and then rebooting. I’ll try to tinker some more with Network Manager and see if it works.

#11

When you use Yast (“ifup”) setup, then it will give a default route to ethernet, and only a local LAN route to wireless. Turning off the ethernet in Yast gets you a default route through the wireless.

I’m just explaining why that worked.

You should be able to switch back to NetworkManager, except that if you have a hidden SSID the networkmanager applet for KDE doesn’t always handle that well. With NetworkManager, if the ethernet cable is connected then you might still only get a default route for ethernet. If the ethernet cable is not connected at the time the WiFi connection is made, you should get a default route for WiFi.

#12

So what’s the difference between default route and local LAN route? Shouldn’t they be the same on a simple network like mine? I should probably read up on this stuff. Do you know of a good networking reference that would help?

My SSID is not hidden but when NetworkManager still worked I could pick up a Hidden Network with my own. Probably belongs to someone in the neighbourhood…

So I guess I should make sure the ethernet cable is not connected to switch back to NetworkManager. I turned off ethernet altogether anyway.

#13

I just tried to switch back to NetworkManager but it didn’t work.

After selecting networkmanager in Yast I got a message right before network settings conclude saying “no network found”.

So I launched the networkmanager plasmoid from the panel, selected “enable networking” and repeated the Yast procedure and got the same result. There was nothing in the networkmanager window.

So I rebooted and got an ethernet symbol for the plasmoid, with a bunch of network SSID’s picked up including mine and an “Error: Invalid state” message for both wireless and wired interfaces. Also clicking on any of the networks does not produce anything. They’re not clickable.

#14

The local LAN route will allow you to talk to other computers on your LAN. But it won’t get you to yahoo or google or opensuse.org.

You could manually add a default route with the “route” command, but it is better to set things up so that is automatic.

#15

I have no problem to understand where all those updates come from. All those are more or less developer repos where the owners can and will change a lot. It is your choice, but do not be amazed when this brings you almost daily new versions (and maybe even dependancy problems).

As said before, the “official” openSUSE repos will be much more stable and bring normaly only a few Security/Recommended updates a week (in the Update repo).
Packman will be a bit more dynamic and you can again decide for yourself if you follow with all their updates.

For the others, when I would realy need one of those, I would install the wanted package(s) and then disable such a repo. I would only enable and update from such a repo, when I was realy convinced that I needed an update of the packages from that one.

Either you want to live with a stable system that does the things you want it to do (and never touch a running system), or you want to try out all sorts of new software/versions. But in the second case you should not complain about many update and/or broken software.

#16

I hear you. But I’ve been using this configuration for years without any such problem. I’ve got it installed on a desktop PC and it still works pretty well as far as wireless is concerned. The only difference with the laptop on which the problem occurred is that I did not do the monster update from PackageKit. It is in fact disabled there and updates are done explicitly from Yast2 GUI.

All this leads me to think that the problem lies with PackageKit and not the various repos. It just might be better to reinstall :frowning: and follow the same update procedure as with the desktop PC… unless a different configuration is installed by default on laptops, which is entirely possible.

#17

All this leads me to think that the problem lies with PackageKit and not the various repos. It just might be better to reinstall :frowning: and follow the same update procedure as with the desktop PC… unless a different configuration is installed by default on laptops, which is entirely possible.

Not realy imho. The only thing that comes to my mind is that many people would use network manager on a “walk anywhere” laptop and of course use ifup on a desktop. But that is the decission taken during install (or redressed after) by the system manager, not an automatic default configuration.

#18

The desktop is also running knetworkmanager. This is why I think the problem lies with packagekit.