- User Since
- Jul 2 2018, 09:15 (173 w, 22 h)
Oct 24 2019
That would means that without a Nextcloud/Owncloud account I could set up a CardDAV/CaldDAV service using the option dedicated for Nextcloud?
Perhaps. But I imagine you'd want to ask upstream in GNOME to determine for sure
Oct 4 2019
Well, it seems quite easy to me to fix T663 (blacklist all non-free services). But you can't whitelist CardDAV and CalDAV support, it needs to be implemented first… The upstream bug report is pending for six years now.
Oh, I didn't see that. However, this report is not about the promotion of non-free services (like T663) but about the missing support (and thus promotion) of common open standard protocols.
Oct 2 2019
Yes, and that means that by default (to my knowledge) PureOS supports
- Microsoft Exchange and
for calendar and addressbook sync. The only freedom respecting option is Nextcloud/Owncloud (which uses these standard protocols by the way).
I can confirm this issue.
Oct 30 2018
I guess I can confirm this bug.
indeed there is no file in that directory at all
Oct 29 2018
so far we don't have anyone in-house who is able to re-create this specific problem but clearly you are getting some kind of support request that motivated you to file this ticket.
Aug 9 2018
@mladen.pejakovic As far as I know when installed (like on debian with the non-free firmware-atheros package) the firmware is loaded into a volatile memory of the wireless card. Volatile memory requires power to maintain the stored information. So when you restart, the firmware remains, when you shut down, wait a bit and then start your system the firmware is lost.
@mladen.pejakovic Did you restart into Parabola from a distro with the firmware installed?
Jul 17 2018
People from thinkpenguin insist on that their card works with Trisquel 7 – and that if it doesn't work for me it has something to do with my system ("USB controller related problems/USB hub issues/or whatnot").
Jul 16 2018
I was able to reproduce the same behaviour I see in Trisquel 7.0 with the card I got from thinkpenguin (with bluetooth module 0489:e076) – device is initialized but not usable, see above – with a recent kernel (Linux version 4.18.0-rc4) by reverting this commit. I'm quite sure I get the same result with the combo card I got with my Librem 13, but I don't want to change the cards too often… I'm afraid to fret the antenna connectors…
Jul 14 2018
After playing around a bit I suspect the only reason why in Trisquel 7.0 both devices are initialized is that it uses an old kernel version (linux-libre 3.13), so the driver btusb is used instead of ath3k… Have a look at this commit: our bluetooth module (04ca:300d) is blacklistet in btusb and included in ath3k. I'm not sure but this could be a simple answer to the question why in Trisquel 7.0 the device is initialized but not in recent Debian versions / PureOS / …
Jul 13 2018
I received the module from thinkpenguin – and it's really a different QCNFA222… But yesterday I wasn't able to get it to work with Trisquel 7, it behaved the same way as our module (which is built in the Librem 13): the bluetooth device is initialized without the firmware but I can't find my other bluetooth devices to connect and when I set the device to visible I can't find it with my other devices.
Jul 5 2018
@zlatan.todoric I made pictures of the module in my Librem 13 v3 (see below). I didn't recieve the module from thinkpenguin yet, I'll send pictures as soon as I receive it.
Jul 2 2018
People from thinkpenguin.com told me that in fact not all Qualcomm Atheros wireless combo cards require proprietary firmware for bluetooth to function. But with current distros you won't even notice that you have a card that doesn't need the firmware since the kernel wouldn't try anything without it… If you don't make the firmware available the driver (and not the firmware loading mechanism) will be disabled.