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

List:       kde-bugs-dist
Subject:    [Bug 234498] BluezDevil crash, invalid D-Bus path ""
From:       Christoph Feck <christoph () maxiom ! de>
Date:       2010-04-16 15:17:36
Message-ID: 20100416151736.0E8DD3E764 () immanuel ! kde ! org
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=234498





--- Comment #2 from Christoph Feck <christoph maxiom de>  2010-04-16 17:15:40 ---
I replaced "isNull" with "isEmpty", and no longer got a crash, thanks.

If the default interface/path is read from some configuration file, it is
probably wise to apply some more sanity checks to ensure no invalid path is
passed to D-Bus functions. Maybe Qt has some isValid() functions ...

Additional note: I did not configure anything, but just started with an empty
.kde when I got the crash. I also don't know if my computer has bluetooth
devices, how can I check? lspci does not list it.

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
[prev in list] [next in list] [prev in thread] [next in thread]