Is Wacom still broken in Wayland Plasma?
My Wacom-based touchscreen works fine in X with only libinput installed. In Wayland, the touchscreen, stylus and all other features are completely unresponsive. I found complaints a few years old that this was a known defect. However, references to it in https://community.kde.org/Plasma/Wayland_Showstoppers have been removed. Is it still known to be broken or have I not set it up correctly? I can find plenty of information about setting up tablets in X, but not on Wayland or with libinput. Guidance would be much appreciated if it's possible.
Re: Kaidan XMPP client
Hi John. John Scott - 28.05.20, 23:34:46 CEST: > (cc'ing packaging list in case anyone there knows or is working on it) > On Thursday, May 28, 2020 7:15:24 AM EDT Martin Steigerwald wrote: > > Fair enough. I was not able to use it as a XMPP client reliably. > > I am in exactly the same boat as you. Never got Kopete or KDE > Telepathy to work with XMPP, granted KTp as packaged is pretty old > ATM. There is a new XMPP-centric KDE program called Kaidan [1] that > looks very nice. Yeah, I am aware of it. It looks nice and modern, you can even install it as a Flatpak. However so far as to my knowledge it has no OMEMO encryption yet. That is a no-go for me. And while there are nice updated versions of PSI Plus in Debian experimental, I again went back to dino-im… it is not great UI wise, especially as it insists of opening images I receive by chat with Imagemagick which has a GUI that IMHO should not be thrown at mere mortals…¹ however, that may just be cause its GTK and such does not use the standard applications set for KDE applications. But I did not find where to set which application it shall use. I hope I do not have to install GNOME Settings to change that. PSI Plus? Well it appears to have a ton of features, but it does not work with one of my XMPP accounts and… its a ton of complexity. I don't really understand this software. Kopete and especially KDE Telepathy are quite nice approaches. It is a pity that those seem to be abandoned. But yeah, it may make sense to have something that does not try to support every chat protocol in existence. As far as I see about what currently matters, support IRC, XMPP and Matrix… and be done with it. Especially skip all the proprietary platforms like ICQ – is thing still a thing? – and AOL and what not. [1] On command line it can be really handy, but please leave me alone with that GUI. Thanks, -- Martin
Re: Kaidan XMPP client [was Re: KDEPIM 20.04 and KDE Frameworks 5.70 coming to unstable now]
(cc'ing packaging list in case anyone there knows or is working on it) On Thursday, May 28, 2020 7:15:24 AM EDT Martin Steigerwald wrote: > Fair enough. I was not able to use it as a XMPP client reliably. I am in exactly the same boat as you. Never got Kopete or KDE Telepathy to work with XMPP, granted KTp as packaged is pretty old ATM. There is a new XMPP-centric KDE program called Kaidan [1] that looks very nice. It already supports Jingle. I was able to build it from source a while ago, all deps are packaged and it just needed a library version from experimental. They produce their own not-necessarily-high-quality/automatic debs upstream. I asked them here [2] if they'd talked to anyone about packaging it in Debian proper, or if it were a good idea since Kaidan is still semi-betaish. I didn't hear back but it looks very promising. [1] https://www.kaidan.im/2020/04/06/kaidan-0.5.0/ [2] https://invent.kde.org/network/kaidan/-/issues/29 signature.asc Description: This is a digitally signed message part.
[bts-link] source package ksystemlog
# # bts-link upstream status pull for source package ksystemlog # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # https://bts-link-team.pages.debian.net/bts-link/ # user debian-bts-l...@lists.debian.org # remote status report for #889919 (http://bugs.debian.org/889919) # Bug title: ksystemlog: SIGSEGV in QAction::setEnabled # * http://bugs.kde.org/show_bug.cgi?id=409375 # * remote status changed: CONFIRMED -> RESOLVED # * remote resolution changed: (?) -> FIXED # * closed upstream tags 889919 + fixed-upstream usertags 889919 - status-CONFIRMED usertags 889919 + status-RESOLVED resolution-FIXED thanks
Processed: [bts-link] source package ksystemlog
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package ksystemlog > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #889919 (http://bugs.debian.org/889919) > # Bug title: ksystemlog: SIGSEGV in QAction::setEnabled > # * http://bugs.kde.org/show_bug.cgi?id=409375 > # * remote status changed: CONFIRMED -> RESOLVED > # * remote resolution changed: (?) -> FIXED > # * closed upstream > tags 889919 + fixed-upstream Bug #889919 [ksystemlog] ksystemlog: SIGSEGV in QAction::setEnabled Added tag(s) fixed-upstream. > usertags 889919 - status-CONFIRMED Usertags were: status-CONFIRMED. Usertags are now: . > usertags 889919 + status-RESOLVED resolution-FIXED There were no usertags set. Usertags are now: resolution-FIXED status-RESOLVED. > thanks Stopping processing here. Please contact me if you need assistance. -- 889919: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889919 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Re: KDEPIM 20.04 and KDE Frameworks coming to unstable now
Le jeudi 28 mai 2020, 16:42:52 CEST Martin Steigerwald a écrit : > Hi Merlin. > > MERLIN Philippe - 28.05.20, 16:24:52 CEST: > > Is it normal today that under Sid Kdepim is still in version 17.12 ? > > That is just a meta package to install the set of packages to have > KDEPIM. Those do not need to be changed all that often. > > Look at versions of packages like kmail, kontact or so or just about > version in the application or… > > % akonadictl --version > akonadictl 5.14.1 (20.04.0) > % kmail --version > kmail2 5.14.1 (20.04.0) > > > Ciao, Ok. For the update I use apt and it asked me to delete Kontact Kmail ... Kdepim also I blocked the update following your message , I tried aptitude and the update seems to be carried out correctly. Thank you very much. Cheers. Philippe Merlin
Re: KDEPIM 20.04 and KDE Frameworks coming to unstable now
HI! Is it normal today that under Sid Kdepim is still in version 17.12 ? Cheers. Philippe Merlin Le mercredi 27 mai 2020, 08:53:42 CEST Martin Steigerwald a écrit : > Hi! > > Woooho… it's all coming now! > > As usual wait till complete. > > Right now apt dist-upgrading would remove quite some packages here. > > Thank you a lot, Sandro! And everyone else who may have helped with > that. > > I know it is a lot of packages. It is a lot of work to do. Even with > some automation in place, there is still quite some manual work involved > to have high quality packages! > > Best,
Re: KDEPIM 20.04 and KDE Frameworks coming to unstable now
Hi Merlin. MERLIN Philippe - 28.05.20, 16:24:52 CEST: > Is it normal today that under Sid Kdepim is still in version 17.12 ? That is just a meta package to install the set of packages to have KDEPIM. Those do not need to be changed all that often. Look at versions of packages like kmail, kontact or so or just about version in the application or… % akonadictl --version akonadictl 5.14.1 (20.04.0) % kmail --version kmail2 5.14.1 (20.04.0) Ciao, -- Martin
Bug#961731: sddm: Please remove Recommends: haveged
Package: sddm Version: 0.18.1-1 Severity: wishlist Dear Maintainer, your package currently Recommends: haveged. On modern kernels, so whatever will ship in bulleye, the kernel will provide enough entropy, so there should be no need for haveged, except in exceptional situations. Please remove the Recommends: haveged. Thanks, Chris
Re: KDEPIM 20.04 and KDE Frameworks 5.70 coming to unstable now
Sorry, accidentally sent half finished mail before due to typo which triggered sending the mail. Martin Steigerwald - 28.05.20, 09:19:00 CEST: > Sedat Dilek - 27.05.20, 13:03:40 CEST: > > Some stuff like kmail I have stolen from > > incoming.d.o/buildd-unstable. > So I did something ridiculous: I actually waited till I could upgrade > using just the packages from unstable – Kopete still got > uninstalled, but as I do not need it and I think its not even up to > date regarding XMPP/Jabber and OMEMO… I said, yes, go ahead. Thing > is, right now it appears to me KDE does not have any suitable chat > application. Konversation for IRC may be good to go, but I use > Quassel IRC with core running on my server for that. But Kopete or > KDE Telepathy appear to be mostly unmaintained and buggy. About kopete: I still had it from experimental. The older version has been removed from unstable due to using Qt4 and the newer version while based in Qt 5 may just not be suitable for inclusion at the moment. Fair enough. I was not able to use it as a XMPP client reliably. Bug#935659: Removed package(s) from unstable https://bugs.debian.org/935659 Ciao, -- Martin
Re: KDEPIM 20.04 and KDE Frameworks 5.70 coming to unstable now
Martin Steigerwald - 28.05.20, 09:19:00 CEST: > Sedat Dilek - 27.05.20, 13:03:40 CEST: > > Some stuff like kmail I have stolen from > > incoming.d.o/buildd-unstable. > So I did something ridiculous: I actually waited till I could upgrade > using just the packages from unstable – Kopete still got > uninstalled, but as I do not need it and I think its not even up to > date regarding XMPP/Jabber and OMEMO… I said, yes, go ahead. Thing > is, right now it appears to me KDE does not have any suitable chat > application. Konversation for IRC may be good to go, but I use > Quassel IRC with core running on my server for that. But Kopete or > KDE Telepathy appear to be mostly unmaintained and buggy. About kopete: I still had it from experimental. The older version has been removed from unstable due to using Qt4 and the newer version while based in Qt 5 may just not be suitable for inclusion at the moment. Bug#935659: Removed package(s) from unstable https://bugs.debian.org/935659 Ciao, -- Martin
Processed: Re: Bug#958479: qmake passes unsupported -isystem to gcc
Processing control commands: > forwarded -1 https://codereview.qt-project.org/c/qt/qtbase/+/302175 Bug #958479 [qt5-qmake] qmake passes unsupported -isystem to gcc Set Bug forwarded-to-address to 'https://codereview.qt-project.org/c/qt/qtbase/+/302175'. -- 958479: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958479 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#958479: qmake passes unsupported -isystem to gcc
Control: forwarded -1 https://codereview.qt-project.org/c/qt/qtbase/+/302175 Hi Helmut, On Wed, May 27, 2020 at 09:35:10PM +0200, Helmut Grohne wrote: > I looked and the process is waaay to beyond what I can do. I'm not up to > consenting to a 10-page TOS for a 5-line patch. Sorry. > > The 5-page CLA doesn't make this any better. Not a friendly project to > contribute to. OK, that is understandable. > Your suggestion to explicitly license it under BSD seems much more > reasonable to me. Let's do that. However, given that I find you much > more trustworthy than QT upstream, I think that there is an even simpler > option: Please treat the patch I sent to this bug as yours. You may > claim authorship. I think legally that means I transfer whatever > copyright I may have on this particular patch to you after licensing it > under BSD. I have now submitted this patch to Gerrit, see forwarded link. Let's see what upstream thinks about it. Also I simplified the unixmake2.cpp part of the patch a bit. The logic should stay the same as in your patch. -- Dmitry Shachnev signature.asc Description: PGP signature
Re: [Nicholas D Steeves] Re: KDEPIM 20.04 and KDE Frameworks 5.70 coming to unstable now
Hey, > Also replying to debian-qt-kde, in case some team members are not > following debian-kde. this list is for bugreports only. If you want to reach the Maintainer team you need to use the pkg-kde-t...@alioth-lists.debian.net. hefee signature.asc Description: This is a digitally signed message part.
Baloo 5.70 likely lighter on system under laod
Hi! There is a nice change in Baloo 5.70. The Baloo file indexing service now uses fewer system resources–in particular disk I/O–when the system is in use by the user (Stefan Brüns, Frameworks 5.70) https://pointieststick.com/2020/04/17/this-week-in-kde-our-cup-overfloweth-with-improvements/ [Extractor] Better balance idle and busy mode https://phabricator.kde.org/D28864 So Baloo should be lighter on the system especially when the system is in use for something else. Let's how that will work out. Another nice one will come in 5.7.1: The Baloo file indexing service no longer triggers a brief I/O spike when renaming files, and its database now stores information more efficiently and therefore grows more slowly (Stefan Brüns, Frameworks 5.71) https://pointieststick.com/2020/05/08/this-week-in-kde-get-new-clipped-subsurface-dolphin-folder-sizes/ Store filename terms just once https://phabricator.kde.org/D28932 Ciao, -- Martin
Re: KDEPIM 20.04 and KDE Frameworks 5.70 coming to unstable now
Hi Sedat, hi community! Sedat Dilek - 27.05.20, 13:03:40 CEST: > Some stuff like kmail I have stolen from incoming.d.o/buildd-unstable. So I did something ridiculous: I actually waited till I could upgrade using just the packages from unstable :) – Kopete still got uninstalled, but as I do not need it and I think its not even up to date regarding XMPP/Jabber and OMEMO… I said, yes, go ahead. Thing is, right now it appears to me KDE does not have any suitable chat application. Konversation for IRC may be good to go, but I use Quassel IRC with core running on my server for that. But Kopete or KDE Telepathy appear to be mostly unmaintained and buggy. So far everything works. Three observations so far: - I got a warning of KAlarm about using archived alarms without having a calendar for it. Well I just told it not to archive alarms. So far so good. - A connection error I got with a nice mail provider I use some accounts with IMAP got more specific and I now see that it was related to sieve protocol. As I don't use sieve filtering on that account I just disabled it. Also good. - Unread mails in message list in KMail show in *purple* color. Interesting choice. So I told it to use custom color scheme and set a color that better suits my taste. I may report a bug about this, as with white background that purple really does not look that readable. Let's see whether anything else comes up. I do hope that the frequent stalls during POP3 retrieval or message filtering are gone now. They appeared somewhat before KDEPIM/Akonadi 19.08 tough. If they aren't gone: I have not much of an idea on how to provide a useful upstream bug report about it, cause I have no idea what is causing those stalls and I see nothing obvious in logs. I am pretty certain tough that these are not caused by my Dovecot POP3/IMAP server. Best, -- Martin
