From kde-devel Mon Apr 03 19:59:15 2006 From: "Paulo J. Matos" Date: Mon, 03 Apr 2006 19:59:15 +0000 To: kde-devel Subject: Re: Problem opening bluetooth:/ Message-Id: <11b141710604031259o7c5b3068r2e3b3b872b52466 () mail ! gmail ! com> X-MARC-Message: https://marc.info/?l=kde-devel&m=114409438109855 On 18/03/06, Pavel Troller wrote: > 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 "Invalid URL format bluetooth:/" > (in my local language, so it may be slightly different) 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. > Not here with 3.5.2. bluetooth:/ or sdp:/ not working! > 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 << > -- Paulo Jorge Matos - pocm at sat inesc-id pt Web: http://sat.inesc-id.pt/~pocm Computer and Software Engineering INESC-ID - SAT Group >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<