Jing: > I'm trying to run ConsoleKit on Solaris X86. I'd downloaded ConsoleKit 0.3.0 > released at the end of last month and successfully built it. Now, 3 C test > programs (test-tty-idle-monitor, test-vt-monitor and test-event-logger) and > console-kit-daemon can run well. But the 2 Python test scripts > (test-open-session & test-open-session-with-parameters) have not passed yet. > The > following error info was always reported:
The VT stuff hasn't been integrated into Solaris yet. The VT related ConsoleKit stuff won't work unless you have a BFU'ed your system to have VT support. Here is information about their project. http://opensolaris.org/os/project/vconsole/ There is a vconsole-discuss at opensolaris.org mailing list, which is probably a better forum for VT related questions. > Got cookie: 85c0571a58ed63e2dd47c6df4896d010-1218780407.588252-472908783 > ERROR:dbus.proxies:Introspect error on: > 1.8:/org/freedesktop/ConsoleKit/Session2: > dbus.exceptions.IntrospectionParserException: Error parsing introspect data: > xml.parsers.expat.ExpatError: mismatched tag: line 87, column 6 > Current session: /org/freedesktop/ConsoleKit/Session2 > ERROR:dbus.proxies:Introspect error on: > 1.8:/org/freedesktop/ConsoleKit/Session2: > dbus.exceptions.IntrospectionParserException: Error parsing introspect data: > xml.parsers.expat.ExpatError: mismatched tag: line 87, column 6 Assuming that the above didn't answer your question. What version of Solaris or OpenSolaris are you using? Are you using the desktop stack that came with the OS, or did you upgrade your packages to install the latest desktop stack? What does your /etc/release file say? > My station was configured with > SunOS solaris-156 5.11 /ws/onnv-gate i86pc i386 i86pc > and dbus 1.2.1 was installed. What Nevada build is that? The above errors seem to be complaining about libexpat not working, or not being properly integrated into D-Bus. You might ask your question on desktop-discuss at opensolaris.org to find out if there might be any known issues with libexpat. You might also send an email to the FreeDesktop HAL mailing list about general ConsoleKit related questions. That would be a good place to pose your question. http://lists.freedesktop.org/mailman/listinfo/hal Some tips on debugging console-kit - Did you enable console-kit via SMF? Programs which use it won't work until you run this command: svcadm enable consolekit If you built ConsoleKit from the spec-file in spec-files-extra, it should set up the SMF files for you. If you aren't using spec-files-extra, then it probably isn't working because this spec file does some patches which are needed for things to work. - Note that you can run /usr/sbin/console-kit-daemon by hand with the --debug and --no-daemon arguments. If it isn't working, I'd run "svcadm disable consolekit" to make sure it isn't running via SMF, and run it by hand with these arguments and see if any error messages are echoed back to the terminal when you perform the operation which fails. - Note that I sometimes find that ConsoleKit core dumps. I set up coreadm this way so that global core files are sent to /var/tmp. Normally they are not generated, so if you don't set up coreadm this way, you won't get the core file for analysis. If you find it is core dumping, then you can debug it. Just run "man coreadm" to see how to set up coreadm. global core file pattern: /var/tmp/core.%p global core file content: default init core file pattern: core init core file content: default global core dumps: enabled per-process core dumps: enabled global setid core dumps: enabled per-process setid core dumps: enabled global core dump logging: disabled Brian
