Description of problem: I was trying to use dbus-introspectioon using DBusViewer ... I got a blank Java app. window with the appropriate labels of "session" and "system" .... error messages come up .... "class not found /cx/ath/matthew/unix/UnixSocket How do I find what package the offender belongs to? [steverex@localhost bin]$ rpm -q --whatprovides /usr/bin/DBusViewer dbus-java-2.7-12.fc19.x86_64 [steverex@localhost bin]$ rpm -ql dbus-java /usr/bin/CreateInterface /usr/bin/DBusCall /usr/bin/DBusDaemon /usr/bin/DBusViewer /usr/bin/ListDBus /usr/share/doc/dbus-java /usr/share/doc/dbus-java-2.7 /usr/share/doc/dbus-java-2.7/AUTHORS /usr/share/doc/dbus-java-2.7/COPYING /usr/share/doc/dbus-java-2.7/INSTALL ...... Are these elf files or script executable files: [steverex@localhost bin]$ file DB* DBusCall: POSIX shell script, ASCII text executable DBusDaemon: POSIX shell script, ASCII text executable DBusViewer: POSIX shell script, ASCII text executable [steverex@localhost bin]$ file ListDBus ListDBus: POSIX shell script, ASCII text executable [steverex@localhost bin]$ All command files are shell scripts. Here's a printout of /usr/bin/ListDBus [steverex@localhost bin]$ cat ListDBus #!/bin/sh -- JAVA=java DEBUG=disable VERSION=2.7 JARPATH=/usr/share/java/dbus-java JAVAUNIXLIBPATH=/usr/lib64/libmatthew-java JAVAUNIXJARPATH=/usr/lib64/libmatthew-java exec $JAVA -DPid=$$ -DVersion=$VERSION -Djava.library.path=$JAVAUNIXLIBPATH -cp $JAVAUNIXJARPATH/unix.jar:$JAVAUNIXJARPATH/debug-$DEBUG.jar:$JAVAUNIXJARPATH/hexdump.jar:$JARPATH/dbus.jar:$JARPATH/dbus-bin.jar org.freedesktop.dbus.bin.ListDBus "$@" Here is a Corrected Version of the DBusViewer script: [steverex@localhost bin]$ cat DBusViewer #!/bin/sh -- JAVA=java DEBUG=disable VERSION=2.7 JARPATH=/usr/share/java/dbus-java JAVAUNIXLIBPATH=/usr/lib64/libmatthew-java JAVAUNIXJARPATH=/usr/lib/java exec $JAVA -DPid=$$ -DVersion=$VERSION -Djava.library.path=$JAVAUNIXLIBPATH -cp $JAVAUNIXJARPATH/unix.jar:$JAVAUNIXJARPATH/debug-$DEBUG.jar:$JAVAUNIXJARPATH/hexdump.jar:$JARPATH/dbus.jar:$JARPATH/dbus-bin.jar:$JARPATH/dbus-viewer.jar org.freedesktop.dbus.viewer.DBusViewer "$@" [steverex@localhost bin]$ The correct value: $JAVAUNIX_JARPATH=/usr/lib/java ...must be changed from the incorrect value JAVAUNIXJARPATH=/usr/lib64/libmatthew-java ...and the change needs to be made in all five scripts: [steverex@localhost bin]$ rpm -ql dbus-java /usr/bin/CreateInterface /usr/bin/DBusCall /usr/bin/DBusDaemon /usr/bin/DBusViewer /usr/bin/ListDBus The fix works!
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.