Red Hat Bugzilla – Bug 471417
PackageKit 'offline' message is misleading
Last modified: 2008-12-09 09:33:42 EST
Description of problem:
PackageKit tells me that it can't install a package because I'm offline. My understanding is that it's querying NetworkManager and NetworkManager is not managing my connection. I am not offline.
Version-Release number of selected component (if applicable):
A sensible message that helps to resolve the problem at hand.
*** Bug 457972 has been marked as a duplicate of this bug. ***
This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle.
Changing version to '10'.
More information and reason for this action is here:
Do you have Networkmanager running? Please see the options in /etc/PackageKit/PackageKit.conf if this is the case.
Hmm... I didn't even know that option was there. No, NetworkManager was not running - I ended up uninstalling NetworkManager instead.
Isn't there something more automatic that can be done here?
Short of that, maybe the message should indicate that this could be configuration problem and where to look?
(In reply to comment #4)
> No, NetworkManager was not
> running - I ended up uninstalling NetworkManager instead.
Let me correct myself a bit - NM was installed and running, but not managing any interface.
NetworkManager is the way to get the network state. If you're not using a "just works" interface, then you will have to edit the config file. We already use a fallback heuristic, and if that doesn't work, you're on your own.
I think you missed the point. The message that you are 'offline' is absolutely incorrect. I'm just asking for a better message.
Even something like 'you're either offline or not using NetworkManager so your interface state can not be determined' would be better.
The current message doesn't even begin to describe the real problem or offer helpful advice.
Would a new user know what "interface state can not be determined" means? We also kow the state of the interface, it's just not being managed by NetworkManager.
The current logic is:
if (NetworkManager is alive)
ask if we are connected
use a unix fallback detection
So if you are running NetworkManager, but not using it, then it's going to report offline. You can either turn off NetworkManager or use it, it's up to you.