Arne Blankerts

At least on my Desktop when checking `journactl`'s output, I see `bluetoothd` throwing an error when pairing: ``` Sep 17 15:48:25 ..... bluetoothd[4216]: src/device.c:new_auth() No agent available for request type...

``` # rpm -qa |grep bluez bluez-5.65-1.fc36.x86_64 bluez-libs-5.65-1.fc36.x86_64 bluez-obexd-5.65-1.fc36.x86_64 bluez-cups-5.65-1.fc36.x86_64 kf5-bluez-qt-5.97.0-1.fc36.x86_64 ``` I did set the `Appearance=0x0192` into the corresponding file in `/var/lib/bluetooth/...../info` and also, for the just in case,...

I keep getting ``` Sep 17 22:56:27 ..... kernel: Bluetooth: hci0: Opcode 0x 401 failed: -16 Sep 17 22:56:44 ..... bluetoothd[1712140]: profiles/deviceinfo/deviceinfo.c:read_pnpid_cb() Error reading PNP_ID value: Request attribute has encountered...

It seems that the aforementioned patch is included in 5.65. ( https://git.kernel.org/pub/scm/bluetooth/bluez.git/log/?h=5.65 )

Our how-to page suggests to upload keys to `pgp.mit.edu`. That's a server which is part of the "classic" sks keyserver pool. Given that there are various issues with their approach...

Glad it worked. Two Small notes: * Technically, the signature file is supposed to be called `phpmd.phar.asc` rather than `your.phar.asc` ;-) * You might want to register `phpmd` as an...

While I agree the design with the Facade and how it is currently implemented leaves room for improvements, I so far fail to see how either of your proposed changes...

Sorry, maybe I'm just blind or stupid - or it's still to early but I still fail to see the problem with the facade. I'm perfectly happy to admit the...

> @theseer I don't think 3rd parties should reset the state: it's PHPUnit's duty to leave a clean state after run Valid point. I was actually somehow expecting it to...

> > That leaves the question, what do we consider a "run"? > > `PHPUnit\TextUI\Application::main` or `PHPUnit\TextUI\Application::run`? See, that's where I'm not sure yet. And that would include a bunch...