When I click the launcher for gpk-update-viewer, it gets an error popup saying "No network connection available," even though one is, and every other app is using it. The "Details" in the popup say merely "Cannot refresh cache whilst offline."
If I close the popup, the update viewer will eventually find, download, and install the updates. But if I launch gpk-application itself, I am unable to add or remove any software. It hits the same popup, and unlike the updater, it stops cold when I close the popup.
How do I tell it to wake up and smell the coffee??
On Fri, 05 Jun 2009 16:01:32 +0000, Beartooth wrote:
When I click the launcher for gpk-update-viewer, it gets an error popup saying "No network connection available," even though one is, and every other app is using it. The "Details" in the popup say merely "Cannot refresh cache whilst offline."
I happened to think of stopping NetworkManager. Sure enough, now PackageKit works. I hope that tells somebody something.
On Fri, Jun 05, 2009 at 04:33:25PM +0000, Beartooth wrote:
On Fri, 05 Jun 2009 16:01:32 +0000, Beartooth wrote:
When I click the launcher for gpk-update-viewer, it gets an error popup saying "No network connection available," even though one is, and every other app is using it. The "Details" in the popup say merely "Cannot refresh cache whilst offline."
I happened to think of stopping NetworkManager. Sure enough, now PackageKit works. I hope that tells somebody something.
Is it possible your messagebus (D-Bus) had a problem? Do you have any other D-Bus listeners that are having problems?
The easiest way to test is to reboot and see if the problem persists. (Yes, this is not the only way, but it's easiest if you don't want to get into start/stopping services, and so forth.)
If it *does* persist, check your PK configuration perhaps?
[paul@salma ~]$ grep UseNetworkManager /etc/PackageKit/PackageKit.conf UseNetworkManager=true
(The default configuration is "true," by the way.) If PK is supposed to be using NetworkManager for managing your network connection and you disable a network connection in NM without telling it that you're managing it elsewhere, it may tell other apps that no network exists.
You can set manual configurations in NetworkManager, or if you set them with system-config-network, you can mark them as not to be managed by NetworkManager, and PK's heuristics should just do the right thing.
On Fri, 05 Jun 2009 13:30:03 -0400, Paul W. Frields wrote:
On Fri, Jun 05, 2009 at 04:33:25PM +0000, Beartooth wrote:
On Fri, 05 Jun 2009 16:01:32 +0000, Beartooth wrote:
When I click the launcher for gpk-update-viewer, it gets an error popup saying "No network connection available," even though one is, and every other app is using it. The "Details" in the popup say merely "Cannot refresh cache whilst offline."
I happened to think of stopping NetworkManager. Sure enough, now PackageKit works. I hope that tells somebody something.
Is it possible your messagebus (D-Bus) had a problem? Do you have any other D-Bus listeners that are having problems?
I have no faintest inkling; how do I check? Searching messagebus got me a file called /etc/rc.d/init.d, which Fedora opened with GVIM. What I know of any form of vi is how to spell it; but I looked. It's all in code, of course, and Greek to me; I don't see a mention of NM there.
The easiest way to test is to reboot and see if the problem persists. (Yes, this is not the only way, but it's easiest if you don't want to get into start/stopping services, and so forth.)
We've had several power failures lately; there's crew moving the power lines from poles to underground. So I've rebooted three or four times, if not more, just in the last week. The problem has survived that.
If it *does* persist, check your PK configuration perhaps?
[paul@salma ~]$ grep UseNetworkManager /etc/PackageKit/PackageKit.conf UseNetworkManager=true
I get the same, after I c&p the grep command to a prompt.
(The default configuration is "true," by the way.) If PK is supposed to be using NetworkManager for managing your network connection and you disable a network connection in NM without telling it that you're managing it elsewhere, it may tell other apps that no network exists.
The problem exists only on this one machine. I thought I had disabled NM some time ago in system-config-services; maybe some reboot restarted it??
You can set manual configurations in NetworkManager, or if you set them with system-config-network, you can mark them as not to be managed by NetworkManager, and PK's heuristics should just do the right thing.
I have seen those markings somewhere, but don't find them now. According to gedit, nm-system-settings.conf contains only
[main] plugins=ifcfg-rh
I don't find anything jumping out at me in /etc/PackageKit/ PackageKit.conf -- but maybe I wouldn't ...
On Fri, Jun 05, 2009 at 07:16:23PM +0000, Beartooth wrote:
On Fri, 05 Jun 2009 13:30:03 -0400, Paul W. Frields wrote:
If it *does* persist, check your PK configuration perhaps?
[paul@salma ~]$ grep UseNetworkManager /etc/PackageKit/PackageKit.conf UseNetworkManager=true
I get the same, after I c&p the grep command to a prompt.
(The default configuration is "true," by the way.) If PK is supposed to be using NetworkManager for managing your network connection and you disable a network connection in NM without telling it that you're managing it elsewhere, it may tell other apps that no network exists.
The problem exists only on this one machine. I thought I had disabled NM some time ago in system-config-services; maybe some reboot restarted it??
You can check that:
$ su -c '/sbin/chkconfig --list NetworkManager'
If you did, you probably want to change that PK configuration option above to "false."
You can set manual configurations in NetworkManager, or if you set them with system-config-network, you can mark them as not to be managed by NetworkManager, and PK's heuristics should just do the right thing.
I have seen those markings somewhere, but don't find them now. According to gedit, nm-system-settings.conf contains only
No need to dig in text files, you can just use the System > Administration > Network tool and turn off the "Managed by NetworkManager" option for the interface, and mark it to start by default at boot time.
On Fri, 05 Jun 2009 15:41:23 -0400, Paul W. Frields wrote:
On Fri, Jun 05, 2009 at 07:16:23PM +0000, Beartooth wrote:
On Fri, 05 Jun 2009 13:30:03 -0400, Paul W. Frields wrote:
[....]
The problem exists only on this one machine. I thought I had disabled NM some time ago in system-config-services; maybe some reboot restarted it??
You can check that:
$ su -c '/sbin/chkconfig --list NetworkManager'
[btth@Hbsk2 ~]$ su -c '/sbin/chkconfig --list NetworkManager' Password: NetworkManager 0:off 1:off 2:on 3:on 4:on 5:on 6:off [btth@Hbsk2 ~]$
-- which, alas!, is meaningless to me.
If you did, you probably want to change that PK configuration option above to "false."
Simply open that .conf file and change "true" to "false"?
I have seen those markings somewhere, but don't find them now. According to gedit, nm-system-settings.conf contains only
No need to dig in text files, you can just use the System > Administration > Network tool and turn off the "Managed by NetworkManager" option for the interface, and mark it to start by default at boot time.
I had to discover the place under the Edit button, but I did. Both those were already set that way.
On Sat, 2009-06-06 at 16:11 +0000, Beartooth wrote:
[btth@Hbsk2 ~]$ su -c '/sbin/chkconfig --list NetworkManager' Password: NetworkManager 0:off 1:off 2:on 3:on 4:on 5:on 6:off [btth@Hbsk2 ~]$
-- which, alas!, is meaningless to me.
In run level 0 (shutdown), the service will be off. In run level 1 (single), the service will be off. In run level 2 (traditionally, few services running), the service will be on. In run level 3 (traditionally, no X running), the service will be on. In run level 4, the service will be on. In run level 5 (traditionally, X is running), the service will be on. In run level 6 (rebooting), the service will be off.
Levels 3 and 5 being the usual run levels on a system that's being used. Run level 1 and 2 being used to diagnose/fixup a system, but not a normal operating condition.
Changing run levels will start and stop the service, as required. Likewise, when you boot, the service will be started according to the run level you boot up in.
If you manually start or stop a service, that doesn't change what will happen automatically, when changing run levels or rebooting. What was configured to happen before, will still happen. If you want to make a permanent change, you need to change the run level defaults.
Changing the run level defaults won't start and stop a service. If you want to do that, too, then you need to start or stop it, separately.
-
Beartooth -
Paul W. Frields -
Tim