Bug 457448 - gnome-settings-daemon cannot "set arguments () according to signature" on update
Summary: gnome-settings-daemon cannot "set arguments () according to signature" on update
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: PackageKit
Version: 9
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Robin Norwood
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-07-31 18:07 UTC by Michal Jaegermann
Modified: 2008-10-20 08:47 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-10-20 08:47:40 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Michal Jaegermann 2008-07-31 18:07:04 UTC 
Description of problem:

While doing a yum update to gnome-settings-daemon-2.22.2.1-2.fc9.x86_64
the following showed up:

  Cleanup        : gnome-settings-daemon                           [33/33]
ERROR:dbus.connection:Unable to set arguments () according to signature u's':
<type 'exceptions.TypeError'>: More items found in D-Bus signature than in
Python arguments
Unable to send message to PackageKit

Version-Release number of selected component (if applicable):
gnome-settings-daemon-2.22.2.1-2.fc9.x86_64

How reproducible:
I do not know.  Package scripts are not that clear.
Comment 1 David Wilson 2008-10-20 00:18:11 UTC 
This might be related:

After doing a yum update on f9 when adding gmfsk, fftw2, hamlib, grig, and linpsk I saw this error message:

ERROR:dbus.connection:Unable to set arguments ('posttrans',) according to signature '': <type 'exceptions.TypeError'>: Fewer items found in D-Bus signature than in Python arguments
Unable to send message to PackageKit

This was just after an update, and the system (laptop) has not been rebooted yet.
Comment 2 Bastien Nocera 2008-10-20 00:23:26 UTC 
Got nothing to do with gnome-settings-daemon I'm afraid.
Comment 3 David Wilson 2008-10-20 00:43:59 UTC 
OK... I found out after a reboot the error message went away.
My guess is that something changed related to yum routines.
Comment 4 Richard Hughes 2008-10-20 08:47:40 UTC 
Yup, the PK upgrade should have fixed things.
Note You need to log in before you can comment on or make changes to this bug.