Red Hat Bugzilla – Bug 609827
Last modified: 2010-07-07 13:44:30 EDT
The update setting for mobile connections seems to be ignored on GPRS over Bluetooth.
This happens daily.
Steps to Reproduce:
1. Bind a GSM mobile phone using bluetooth;
2. Connect to Internet using NetworkManager;
The GPRS/EDGE connection becomes active, network available. After some time PackageKit starts checking for updates.
This does not match with my update settings, I have unchecked the «Check for updates when using mobile broadband» box in my preferences.
Today it ate about 9 megabytes of my 85 megabytes of pre-paid traffic. For comparison, it takes me less that 1 meg to check my emails and news, which I do once a day when using mobile Internet.
Created attachment 428211 [details]
Hmm, well, apologies for wasting 9Mb. It would be interesting to see why gnome--packagekit thinks you're not on a mobile connection. First, can you switch to a root user doing:
then kill the daemon (if it is running) with:
then make sure you're on wireless mobile internet and start up the daemon with debugging:
/usr/sbin/packagekitd --backend=yum --verbose --immediate-exit
This should print a line line:
>network state is mobile
It would be interesting to see what value you get. Please also attach the full output of packagekitd, it would be interesting to see if there are any other errors. If you grab me on IRC (nick: hughsie) then I can debug this with you in real time. Thanks.
Created attachment 428354 [details]
> network state online
PackageKit-0.6.6-1.fc13 has been submitted as an update for Fedora 13.
PackageKit-0.6.6-1.fc13 has been pushed to the Fedora 13 testing repository. If problems still persist, please make note of it in this bug report.
If you want to test the update, you can install it with
su -c 'yum --enablerepo=updates-testing update PackageKit'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/PackageKit-0.6.6-1.fc13
PackageKit-0.6.6-1.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.