Re: [Kde-hardware-devel] API addition in Solid

2007-11-17 Thread Matthias Kretz
On Saturday 17 November 2007, Kevin Ottens wrote: > Le samedi 17 novembre 2007, Matthias Kretz a écrit : > > You mean if I have e.g. USB headsets of the same brand and type. Yes. But > > they get the same name, the same icon and have the same initialPreference > > anyway. There's nothing to tell th

Re: [Kde-hardware-devel] multithreading restrictions?

2007-11-17 Thread Kevin Ottens
Le samedi 17 novembre 2007, Marcel Wiesweg a écrit : > My question is: Is this a bug, or are there restrictions on calling Solid > methods from a non-UI thread? In my fantasy world it shouldn't. That said, maybe the D-Bus binding is causing this, in particular because at a few places I made some

Re: [Kde-hardware-devel] API addition in Solid

2007-11-17 Thread Kevin Ottens
Le samedi 17 novembre 2007, Matthias Kretz a écrit : > You mean if I have e.g. USB headsets of the same brand and type. Yes. But > they get the same name, the same icon and have the same initialPreference > anyway. There's nothing to tell them apart and for what I'm concerned I > actually want thos

[Kde-hardware-devel] multithreading restrictions?

2007-11-17 Thread Marcel Wiesweg
Hi, I have lately been observing a problem with Solid: I have moved tasks to a thread, and this includes calls to Solid. The main thread is suspended in an event loop. A call to Solid::Device::listFromType then causes a "pause" in the thread, it hangs for a few seconds and then continues successf

Re: [Kde-hardware-devel] API addition in Solid

2007-11-17 Thread Matthias Kretz
On Saturday 17 November 2007, Kevin Ottens wrote: > It's unlikely that you can forge such an id though, for instance the way you > do it you'll get the same id for twin devices. You mean if I have e.g. USB headsets of the same brand and type. Yes. But they get the same name, the same icon and hav

Re: [Kde-hardware-devel] API addition in Solid

2007-11-17 Thread Kevin Ottens
Le samedi 17 novembre 2007, Matthias Kretz a écrit : > It is not globally unique, where globally == unique identifier I can use on > your computer and on mine. Ah right, skipped the globally part. It's unlikely that you can forge such an id though, for instance the way you do it you'll get the sa

Re: [Kde-hardware-devel] API addition in Solid

2007-11-17 Thread Matthias Kretz
On Saturday 17 November 2007, Kevin Ottens wrote: > Le samedi 17 novembre 2007, Matthias Kretz a écrit : > > I need a globally unique identifier for the devices listed by Solid. And > > Solid::Device::udi() is not that. > > It is. It is unique for a given system. It is not globally unique, where g

Re: [Kde-hardware-devel] ASSERT: "dev->backendObject()==0" in file /SVN/kdelibs/solid/solid/devicemanager.cpp, line 164

2007-11-17 Thread Kevin Ottens
Le samedi 17 novembre 2007, Christian Esken a écrit : > I ran Valgrind to find out what might be going wrong and found "Invalid > read of size 8" inside Solid when *unplugging* the device. It looks to me > like the device table is already corrupt on unplug. It looks like Valgrind is confused by QP

Re: [Kde-hardware-devel] ASSERT: "dev->backendObject()==0" in file /SVN/kdelibs/solid/solid/devicemanager.cpp, line 164

2007-11-17 Thread Kevin Ottens
Le samedi 17 novembre 2007, Christian Esken a écrit : > Theoretically: Yes. > Practically: No > Explanation: KMix can not use the device list from Solid for building its > internal list of devices. The main reason is that there is no support of > the Solaris Sound System (according to the Solid Aud

Re: [Kde-hardware-devel] API addition in Solid

2007-11-17 Thread Kevin Ottens
Le samedi 17 novembre 2007, Matthias Kretz a écrit : > I need a globally unique identifier for the devices listed by Solid. And > Solid::Device::udi() is not that. It is. It is unique for a given system. > So I added the API and implementation for it, but the HAL implementation > currently is jus

Re: [Kde-hardware-devel] ASSERT: "dev->backendObject()==0" in file /SVN/kdelibs/solid/solid/devicemanager.cpp, line 164

2007-11-17 Thread Will Stephenson
On Saturday 17 November 2007 12:09:36 Christian Esken wrote: > > > Unfortunately there is no backtrace, as the > > > "Q_ASSERT(dev->backendObject()==0);" just makes the application exit. > > > > Make it run from gdb. > > This also produces no backtrace. I now added a breakpoint directly before > th

[Kde-hardware-devel] API addition in Solid

2007-11-17 Thread Matthias Kretz
Hi, I need a globally unique identifier for the devices listed by Solid. And Solid::Device::udi() is not that. So I added the API and implementation for it, but the HAL implementation currently is just proof-of-concept and the fakecomputer.xml doesn't have any uniqueIdentifiers for now. I nee

Re: [Kde-hardware-devel] ASSERT: "dev->backendObject()==0" in file /SVN/kdelibs/solid/solid/devicemanager.cpp, line 164

2007-11-17 Thread Christian Esken
Am Samstag, 17. November 2007 schrieb Christian Esken: > Am Samstag, 17. November 2007 schrieb Kevin Ottens: > > Le samedi 17 novembre 2007, Christian Esken a écrit : > > > it is easily reproducable for me, as it happens frequently (nearly > > > always). > > > Just unplug and plug the USB sound st

Re: [Kde-hardware-devel] ASSERT: "dev->backendObject()==0" in file /SVN/kdelibs/solid/solid/devicemanager.cpp, line 164

2007-11-17 Thread Christian Esken
Am Samstag, 17. November 2007 schrieb Kevin Ottens: > Le samedi 17 novembre 2007, Christian Esken a écrit : > > it is easily reproducable for me, as it happens frequently (nearly always). > > Just unplug and plug the USB sound stick. Depending on some magic, the hit > > rate is between 10% and 100%

Re: [Kde-hardware-devel] ASSERT: "dev->backendObject()==0" in file /SVN/kdelibs/solid/solid/devicemanager.cpp, line 164

2007-11-17 Thread Kevin Ottens
Le samedi 17 novembre 2007, Christian Esken a écrit : > it is easily reproducable for me, as it happens frequently (nearly always). > Just unplug and plug the USB sound stick. Depending on some magic, the hit > rate is between 10% and 100%. It's with kmix from trunk, right? I have a usb sound devi