[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    How to debug kioslave problems ? [Was: Problem opening bluetooth:/]
From:       Pavel Troller <patrol () sinus ! cz>
Date:       2006-04-03 4:18:04
Message-ID: 20060403041803.GA2308 () tangens ! sinus ! cz
[Download RAW message or body]

Hi!
  I would like to kindly ask for help with the problem below. I've sent the
message below to kde-devel at 18. of March, but I got no response yet.
  I would really like to debug the problem but I don't have enough knowledge
of internal kioslave operation so I don't know, where to start digging.
  I was waiting some time while hoping that maybe kdebluetooth team will look
at the problem, but there was no commit in this package and the problem still
persists.
  I have a new bit of information to maybe help to clarify the location of
the problem: When I try to open bluetooth:/ without a dongle being connected,
it pops two dialogs: One informing me that just the local services will be
displayed (that's correct and it comes from the kioslave) and the second about
the malformed URL. So the slave IS really called but then something goes wrong.
  Please give me some hints, what to examine/debug, where to put debug strings
or simply how to find more about the possible cause.
                                         With regards, Pavel Troller
  
----- Forwarded message from Pavel Troller <patrol@sinus.cz> -----

Hi!
  Since today's SVN update, I have problems accessing bluetooth:/ kioslave.
  Because there were almost no changes in the kdebluetooth package, I think
that something has changed in the base code, which is now incompatible with
kdebluetooth.
  The problem is that konq pops the message "Malformed URL bluetooth:/"
and does not display contents of the pseudo-filesystem.
  I've turned kio debugging on and the following appears in .xsession-errors:

DCOP: register 'anonymous-4785' -> number of clients is now 18
kio (KRun):  new KRun 0x8636350 bluetooth:/ timer=0x86363a8
kio (KRun): 0x8636350 slotTimeout called
kio (KRun): INIT called
kdeinit: Got EXEC_NEW 'kio_bluetooth' from launcher.
DCOP: unregister 'anonymous-29941'
kio (KLauncher): kio_bluetooth (pid 29942) up and running.
X Error: BadMatch (invalid parameter attributes) 8
  Major opcode:  159
  Minor opcode:  6
  Resource id:  0xa3
kio (KSycoca): Trying to open ksycoca from /var/tmp/kdecache-patrol/ksycoca
kio (KIOJob): error 9
kio (KTrader): query for inode/directory, Application : returning 2 offers
kio (KTrader): query for inode/directory, KParts/ReadOnlyPart : returning 14 offers
kio (KDirWatch): scanning /home/patrol/.kde/share/config 0 1142703022
kio (KDirWatch): scanning /home/patrol/.kde/share/config/mldonkeyrc 1 -1
kio (KTrader): query for ThumbCreator : returning 14 offers
kio (KDirWatch): ev wd: 124 mask 256 path: konqiconviewrc.lockibEnSa.tmp
kio (KDirWatch): -->got create subfile signal for /home/patrol/.kde/share/config
kio (KDirWatch): ev wd: 124 mask 4 path: konqiconviewrc.lockibEnSa.tmp

There are more KDirWatch messages but I think they are not related to the
problem.

Direct access to other bluetooth-related slaves (like sdp:/) is working well.

Any clue, what to fix or try to find the cause, would be highly appreciated! 
             With regards, Pavel Troller
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

----- End forwarded message -----
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]