Chris you wanted to know what happens when an RPM is clicked on in Konqi.
Well it works sort of... every other build... literally everyother build.
I have been downloading every build of kde2 from Mandrake cooker and
clicking on an RPM will open kpackage in one build and then not open in the
next and then work again in the next build. It opens the older kpackage
(1.9.3?). The plus side is that it is VERY VERY FAST at opening an RPM in
kpackage.
Opening kpackage from a konsole opens kpackage pre2.0 which looks very
pretty but is not fully functional. Click on open and select an RPM in a
user's directory promptly causes kpackage to crash with the folowing
QToolBar::QToolBar main window cannot be 0.
kpackage: KGlobalSettings::initStatic
kdecore (KURL): KURL couldn't parse URL "Root Directory: /"
kio (Slave): createSlave for file:/home/EDITEDFORPRIVACY/
kio (Slave): PID of slave = 2800
kio (Slave): slave has connected to application
kio (Slave): got answer 10
kio (KIOJob): Finished [this = 0x86abe18]
kio (KIOJob): stat file:/home/EDITEDFORPRIVACY/GConf-0.7-1mdk.i586.rpm
kio (KIOJob): StatJob::slotStatEntry
kio (KIOJob): Finished [this = 0x86abe18]
kpackage: error in loading shared libraries: kpackage: undefined symbol:
fdOpen
This is going out as a bug report to KDE and really doesn't belong here, but
you did ask what is happening.
