Debian/Bullseye screen doesn't lock
For the last several days, my screen doesn't lock automatically after 10 minutes (as I specified in the power management settings). I've tried rebooting and resetting the power management setting but it's still not locking. I'm running Debian/Bullseye on an AMD64 system. Any suggestions on how to fix this?
Re: [Pkg-xmpp-devel] Qt/KDE XMPP/Jabber client with OMEMO
On 2019-08-19 22:23, Boris Pek wrote: > And now you have a choice between Debian XMPP team and Debian Qt+KDE team: > https://salsa.debian.org/qt-kde-team In fact, I suggested to Jonah and Linus, that Kaidan may be better off in the latter team. Mainly, because Qt/KDE perform complex transitions every some years, so packaging work will need more knowledge around those frameworks than about XMPP. Also, the KDE team is larger than the XMPP team, which might help the Kaidan developers. When the package has landed in Debian, they can easily change teams, if they like.
Re: [Pkg-xmpp-devel] Qt/KDE XMPP/Jabber client with OMEMO
>> >> Then there is kaidan.im which is not packaged yet. >> >> I saw mentions of this project few times (in qxmpp related >> discussions) but have not looked on program yet. >> >> As I see there is related team on Salsa: >> https://salsa.debian.org/kaidan-team >> >> But I have no idea why these packages are not in Debian repos yet and >> why its maintainers have decided to maintain these packages outside >> of Debian XMPP Maintainers team. >> >> Probably Jonah may comment this. (CC-ing) > > We don't "have decided" to maintain it outside of debian, we just > didn't have an idea how to get it into debian. I mean outside of XMPP team in Debian, but not outside of Debian. Now git repos for your packages are in independent Salsa group: https://salsa.debian.org/kaidan-team and I have found them only because I was searching for kaidan mentions in Debian infrastructure. As for adding of kaidan into Debian repos, then joining to specialized Debian team usually simplify finding Debian Developers who are interested in checking and uploading of your packages into Debian. See this as an advertisement of our team: https://salsa.debian.org/xmpp-team =) > Kaidan is still in > development: the basic functionality is not implemented completely yet. And this is absolutely normal. Dino.im is not released yet and lucks some features too, but it is already available in Debian and may work fine for some not exacting users. > Also, we only recently became a KDE project, so we didn't have the > contact to the debian team. These are great news! Congratulations! And now you have a choice between Debian XMPP team and Debian Qt+KDE team: https://salsa.debian.org/qt-kde-team > However recently there were some mails about packaging Kaidan in debian > on the Qt/KDE-list, so I hope it can get into debian soon. Excellent! > OMEMO is on our roadmap and also PEP (a dependency of OMEMO) has been > implemented for QXmpp (still needs to be upstreamed). But don't expect > OMEMO earlier than in one year. And this is fine. We are not in a hurry to anywhere. Best wishes, Boris
Re: [Pkg-xmpp-devel] Qt/KDE XMPP/Jabber client with OMEMO
On Mon, 19 Aug 2019 19:18:13 +0300 Boris Pek wrote: > >> Then there is kaidan.im which is not packaged yet. > > I saw mentions of this project few times (in qxmpp related > discussions) but have not looked on program yet. > > As I see there is related team on Salsa: > https://salsa.debian.org/kaidan-team > > But I have no idea why these packages are not in Debian repos yet and > why its maintainers have decided to maintain these packages outside > of Debian XMPP Maintainers team. > > Probably Jonah may comment this. (CC-ing) We don't "have decided" to maintain it outside of debian, we just didn't have an idea how to get it into debian. Kaidan is still in development: the basic functionality is not implemented completely yet. Also, we only recently became a KDE project, so we didn't have the contact to the debian team. However recently there were some mails about packaging Kaidan in debian on the Qt/KDE-list, so I hope it can get into debian soon. OMEMO is on our roadmap and also PEP (a dependency of OMEMO) has been implemented for QXmpp (still needs to be upstreamed). But don't expect OMEMO earlier than in one year.
Re: Qt/KDE XMPP/Jabber client with OMEMO
Hi Martin, >> Is there such a thing available in Debian? You may ask XMPP related questions in Debian XMPP Maintainers team mailing list: https://wiki.debian.org/Teams/pkg-xmpp >> Kopete 17.08 does not do it. Yes, IIRC Kopete has support only for GnuPG and OTR. >> PSI is said to have OMEMO, but does not appear to have it in Debian. Yes, unfortunately psi package in Debian is outdated and psi-plugins package is not in official repos yet. This is in my TODO list, but progress is slow... > I now also tried psi-plus. And found I missed two things before: > > There is a OMEMO plugin and I can activate. > > Messages send are still not encrypted as I can see in dino.im > > There is supposed to be a OMEMO plugin symbol in toolbar in chat window > but there is not, even tough it is supposed to be there according to > settings window. > > I leave it at that for today. Current version of Psi+ OMEMO plugin in Debian supports all necessary features: * e2e encryption in private chats * e2e encryption in group chats (all members of group chats should have enabled OMEMO plugins in their XMPP clients) * e2e encryption of files uploaded to XMPP server using HTTP Upload Plugin * etc. It is comprehensive tested with Gajim and Conversations. Please check: 1) Have you tried to restart application after enabling of OMEMO plugin? 2) Do you have OMEMO buttons on toolbars in chat windows? If not you may enable them in Psi+ Options dialog in Toolbars section. 3) In some rare cases you may face with broken databases. Try to remove files: ~/.local/share/psi+/profiles/default/omemo-*.sqlite and restart Psi+. Also there is no global option to enable OMEMO encryption in all chats of Psi+: you should explicitly enable encryption in each chat manually. > dino.im works out of the box. > >> Only working (!) XMPP client I found in Debian so far is: dino.im >> which is GTK based. Great! Martin (debacle) may be proud of his work! =) >> Gajim is supposed to be working, but gives a Python traceback on >> activating OMEMO. Its also GTK based. It is strange. Last time I have used Gajim for testing of OMEMO plugin in Psi+ it works fine. Except Gajim could not send OMEMO encrypted files to server. But is was able to decrypt such files sent from other XMPP clients! >> Apparently there more than a dozen XMPP clients for Linux, but none of >> them works as nicely as Conversations.im on Android for far. Conversations is not that perfect (it lucks support of some popular features), but it is really convenient and simple in usage by regular users, yes. >> Pidgin also does not do it. Pidgin is multi-protocol IM client and this significantly influences to its structure and development process. >> One thing to try still would be KDE Telepathy, as I read somewhere it >> would do OMEMO. But it appears to be similarly outdated as Kopete. And after news like this one: https://dot.kde.org/2019/02/20/kde-adding-matrix-its-im-framework I do not believe that any noticeable amount of KDE developers will be interested in development of XMPP client inside KDE project. Hope I am wrong here. >> Then there is kaidan.im which is not packaged yet. I saw mentions of this project few times (in qxmpp related discussions) but have not looked on program yet. As I see there is related team on Salsa: https://salsa.debian.org/kaidan-team But I have no idea why these packages are not in Debian repos yet and why its maintainers have decided to maintain these packages outside of Debian XMPP Maintainers team. Probably Jonah may comment this. (CC-ing) >> There are in part contradicting informations on which client can do it >> or not: >> >> https://omemo.top/ >> >> versus >> >> https://riseup.net/de/chat/clients >> >> for example. These tables are very useful in general, but they miss some information about OMEMO support. For example: in which versions of XMPP clients it was implemented. For example, Psi IM 2.0 with OMEMO support is not released yet. OMEMO plugin is currently available only in daily builds of Psi (from git master branch). Best wishes, Boris
