what cryptic stuff??

[Steve]

---- Beartooth <Beartooth at swva.net> wrote: 
> 
> 	On F9, yum update wanted to do things to 13 packages; it did, 
> then did cleanup on all, then ouput this : 
> 
> ERROR:dbus.proxies:Introspect error on :1.63:/org/freedesktop/PackageKit: 
> dbus.exceptions.DBusException: org.freedesktop.DBus.Error.AccessDenied: A 
> security policy in place prevents this sender from sending this message 
> to this recipient, see message bus configuration file (rejected message 
> had interface "org.freedesktop.DBus.Introspectable" member "Introspect" 
> error name "(unset)" destination ":1.63")
> 
> `Then it skipped a line, and said : 
> 
> Updated: PackageKit.i386 0:0.3.10-3.fc9 PackageKit-glib.i386 
> 0:0.3.10-3.fc9 PackageKit-gstreamer-plugin.i386 0:0.3.10-3.fc9 PackageKit-
> udev-helper.i386 0:0.3.10-3.fc9 PackageKit-yum.i386 0:0.3.10-3.fc9 
> PackageKit-yum-plugin.i386 0:0.3.10-3.fc9 cups.i386 1:1.3.9-2.fc9 cups-
> libs.i386 1:1.3.9-2.fc9 kdelibs.i386 6:4.1.3-4.fc9 kdelibs-common.i386 
> 6:4.1.3-4.fc9 libtirpc.i386 0:0.1.10-1.fc9 system-config-printer.i386 
> 0:1.0.12-2.fc9 system-config-printer-libs.i386 0:1.0.12-2.fc9
> Complete!
> You have new mail in /var/spool/mail/root
> 
> 	(I have SELinux set to disable, btw; yet it's denying access to 
> something to root ...)

I had a similar experience this morning when I ran 
$ sudo yum update 
on my F9 system. It installed 10 packages, updated 24 and removed 4 and I got the "Introspect error". 

In addition I got this really useful message in an error dialog:

Error Type: <type
'exceptions.IndexError'>
Error Value: list index out
of range

Well, duh! Stupid me. I should have known that!

To make matters worse, ther error dialog is about 2" square on my 20" monitor and is not resizable. Taking into account, the icon and the Close button, that leaves about 1" horizontal by 1/2" vertical for the text box which needed both horizontal and vertical scroll bars because of its small size, futher reducing the space for the actual message.

Please tell me that this is just a side effect of the current PackageKit issues and not a final-designed-for-the-end-user message.

Well, at least the kmod-ndiswrapper dependency issues are resolved this morning.

Steve.