Error getting killswitch power arguments: org.freedesktop.DBus.Error.InvalidArgs - Argument 0 is specified to be of type "uint32", but is actually of type "int32"

[Juan Pablo Salazar Bertín]

Binary package hint: network-manager

I'm getting a lot of lines like this:

Sep 10 22:03:23 snifer-laptop NetworkManager: <info> Error getting killswitch power arguments: org.freedesktop.DBus.Error.InvalidArgs - Argument 0 is specified to be of type "uint32", but is actually of type "int32"

Probably due to changes in hal version 0.5.9.1-1ubuntu7.

ProblemType: Bug
Architecture: i386
Date: Mon Sep 10 22:02:05 2007
DistroRelease: Ubuntu 7.10
Package: network-manager 0.6.5-0ubuntu11
PackageArchitecture: i386
SourcePackage: network-manager
Uname: Linux snifer-laptop 2.6.22-11-generic #1 SMP Fri Sep 7 05:07:05 GMT 2007 i686 GNU/Linux

[tduermeier (tduermeier)]

I'm getting this same error after following the instructions here: [url=https://bugs.launchpad.net/ubuntu/+source/hal/+bug/131835]bug #131835[/url].

[Anish Bhatt (anish7)]

Seeing the same error in SuSE currently, not an ubuntu thing.

[Alexander Sack (asac)]

do you have any issues with rfkill and network-manager?

[Alexander Sack (asac)]

please test the packages from my ppa:

http://ppa.launchpad.net/asac/ubuntu/pool/main/n/network-manager/

the version to test is: 0.6.5-0ubuntu16~ppa2 (will appear i a few hours as I just uploaded)

Thanks,

 - Alexander

[Juan Pablo Salazar Bertín (snifer)]

I'm using hal version 0.5.9.1-6ubuntu5 and network-manager version 0.6.5-0ubuntu15 and this issue is not present anymore, at least in a default gutsy rc install.

[Philip Peitsch (philip-peitsch)]

Just found this bug is actually present again in hal version 0.5.9.1-6ubuntu5 with network-manager version 0.6.5-0ubuntu16. This is running on a Dell inspiron 640m, using the ipw3945 driver.

[Marc Carson (baggageclaim)]

I am now experiencing this bug after following the workaround listed here:

https://bugs.launchpad.net/ubuntu/+source/hal/+bug/131835

[Marc Carson (baggageclaim)]

Forgot to mention my machine: Dell E1505, Intel Wireless

[Alexander Sack (asac)]

this is not fixed released. The fix for gutsy will now go through gutsy-proposed. Stay tuned.

[Alexander Sack (asac)]

network-manager (0.6.5-0ubuntu17) hardy; urgency=low

  * upload 0.6.5-0ubuntu17 to hardy

network-manager (0.6.5-0ubuntu16.7.10.0) gutsy-proposed; urgency=low

  Release changes from test package previously known as 0.6.5-0ubuntu16~ppa3:
  * drop gracefull supplicant shutdown feature and its followup patches,
    because they cause crashes and a real fix would need more intrusive code
    rewrites: (LP: #145683, LP: #83623, LP: #152098, LP: #151405)
    - debian/patches/41n_graceful_supplicant_shutdown.patch,
      debian/patches/41q_retry_supplicant_cleanup_startup_if_ctrl_interface_connect_failes.patch,
      debian/patches/41v_lp141233-fix-supplicant-cleanup-crashes.patch,
      debian/patches/41w_lp145683_cancel_scan_in_supplicant_cleanup.patch: drop
        patches that belong to the "graveful supplicant feature".
    - debian/patches/41u_custom_timeout_for_some_wpa_ctrl_operations.patch: update
      interleaving patch
    - debian/patches/series: update quilt series accordingly.
  * debian/patches/24pp_svn2604_Add-HAL-based-rfkill-support.patch: use
    gint32 instead of guint32 for getting the killswitch power argument
    (LP: #138794).

 -- Alexander Sack <email address hidden> Mon, 05 Nov 2007 19:14:43 +0100

[Alexander Sack (asac)]

network-manager (0.6.5-0ubuntu16.7.10.0) gutsy-proposed; urgency=low

  Release changes from test package previously known as 0.6.5-0ubuntu16~ppa3:
  * drop gracefull supplicant shutdown feature and its followup patches,
    because they cause crashes and a real fix would need more intrusive code
    rewrites: (LP: #145683, LP: #83623, LP: #152098, LP: #151405)
    - debian/patches/41n_graceful_supplicant_shutdown.patch,
      debian/patches/41q_retry_supplicant_cleanup_startup_if_ctrl_interface_connect_failes.patch,
      debian/patches/41v_lp141233-fix-supplicant-cleanup-crashes.patch,
      debian/patches/41w_lp145683_cancel_scan_in_supplicant_cleanup.patch: drop
        patches that belong to the "graveful supplicant feature".
    - debian/patches/41u_custom_timeout_for_some_wpa_ctrl_operations.patch: update
      interleaving patch
    - debian/patches/series: update quilt series accordingly.
  * debian/patches/24pp_svn2604_Add-HAL-based-rfkill-support.patch: use
    gint32 instead of guint32 for getting the killswitch power argument
    (LP: #138794).

 -- Alexander Sack <email address hidden> Mon, 05 Nov 2007 18:01:13 +0100

[Martin Pitt (pitti)]

Accepted into gutsy-proposed, please test.

[YorTheGreat (jord-swart)]

Fixed it for me. Used to have problems with rescanning my collection with Amarok. Collection was on an NFS share always failed. Updated it now while using Google Maps and ktorrent. All fine.

[Juan Pablo Salazar Bertín (snifer)]

I installed version 0.6.5-0ubuntu16.7.10.0, and now I see the message again.
It was working fine before this update.
lshal output attached.

[Juan Pablo Salazar Bertín (snifer)]

I'm sorry, actually, the message I'm seeing is:

NetworkManager: <info> Error getting killswitch power: org.freedesktop.Hal.Device.KillSwitch.NotSupported - Access type not supported

which was reported as bug #131835, so I'm reopening it.

[Kow (kow)]

This problem is back in Hardy. Please fix Status as it is not fixed and there is no fixed released.
Dec 8 20:20:34 CSC-KDRAKE-002 NetworkManager: <info> Error getting killswitch power: org.freedesktop.Hal.Device.KillSwitch.NotSupported - Access type not supported
Dec 8 20:21:10 CSC-KDRAKE-002 last message repeated 6 times
Dec 8 20:22:11 CSC-KDRAKE-002 last message repeated 10 times
Dec 8 20:23:17 CSC-KDRAKE-002 last message repeated 11 times
Dec 8 20:23:29 CSC-KDRAKE-002 last message repeated 2 times

[Kow (kow)]

Whoever created the 24pp_svn2604_Add-HAL-based-rfkill-support.patch needs to be more careful and think about just how many times:
+ nm_info ("Error getting killswitch power arguments: %s - %s", err.name, err.message); could be true.

[Kow (kow)]

The easiest fix would be to create 2 global bools that are set to true once the error message they represent has been reported. Each nm_info needs to be embedded within a if(!error_bool{1,2}) for instance. This method would lead to each error msg only being reported once per network-manager run.

[Martin Pitt (pitti)]

Reopening in hardy as per comment 17.

[Martin Pitt (pitti)]

The fix for the int32 -> uint32 is in gutsy and hardy, so I close this again. The Dell killswitch issue is bug 131835, please followup there.