Re: KDE SC 4.10
Hello, I have build kdepim 4.10.2 packages from git, everything looks fine (i was building previous version of kdepim from git too, so no migration here) there is one conflict, it shows during upgrade -- Preparing to replace kleopatra 4:4.8.3-0r0 (using .../kleopatra_4.10.2-0r4_amd64.deb) ... Unpacking replacement kleopatra ... dpkg: error processing /root/debs/./kdepim-4.10.2/kleopatra_4.10.2-0r4_amd64.deb (--unpack): trying to overwrite '/usr/lib/libkleopatraclientgui.so.0.3.0', which is also in package libkleopatraclientgui0 4:4.8.3-0r0 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Errors were encountered while processing: /root/debs/./kdepim-4.10.2/kleopatra_4.10.2-0r4_amd64.deb --- With regards, Libor Dne Sunday 07 April 2013 19:50:57, Sune Vuorela napsal(a): > On 2013-04-06, Diederik de Haas wrote: > > Sune said: > >> the 'normal' experimental is where the action happens, but it happens > >> currently dripwise and not as a big chunk, as it makes stuff easier for > >> the developers. It includes prepearation for the modern kdepim. > > > > Is that the reason that if I want to do a full-upgrade, the 'solution' to > > the conflicts is to remove the kdepim apps? And will that be resolved > > once the modern kdepim (thanks!) is uploaded as well? > > Yes. and yes. > > I do have - completely untested - but allright-looking packages > available - and if there is a couple of interested people with a good > personal backup strategy, I don't mind sharing them a bit. > > Feel free to contact me privately. But note that that you need to have a > good personal backup strategy. > > /Sune signature.asc Description: This is a digitally signed message part.
Re: KDE SC 4.10
Hi you are right, it's not upgrade from or to version in official debian, i forgot that. Just wanted to help with possible conflict, i didn't realise, that it won't affect users, who use official packages Libor *On Friday 12 April 2013 14:48:17 Sune Vuorela wrote:* *> On 2013-04-12, Libor Klepáč wrote:* *> * *> Hi* *> * *> > Preparing to replace kleopatra 4:4.8.3-0r0 (using* *> * *> This is not a version we have been providing, so upgrading from it is on* *> your own.* *> * *> > .../kleopatra_4.10.2-0r4_amd64.deb) ...* *> * *> This is also not a package we have been providin so upgrading to it is* *> on your own.* *> * *> you should be able to recover with repaeting the install a couple of* *> times.* *> * *> /Sune*
Re: Automounted NFS shares never timeout
Hello, i have simillar problem, but with autofs+cifs. I run commands umount -l /mnt/smb4/*/* /etc/init.d/autofs stop before leaving home and suspending my notebook. When i forget to run those commands, plasma-desktop and krunner get stuck after resume. lsof is also stuck. Ussually, killing desktop and krunner helps. I was investigating this several times, without success. One time, i thought, it was caused by ksysguardd. Libor On Monday 17 March 2014 14:46:54 Michael Schuerig wrote: > I have a single NFS share automounted by autofs. Once it is mounted, it > is never (auto-)unmounted, even though I don't explicityl access it. > Lsof does not show any open files below the mount point. > > My hypothesis is that some process periodically accesses the share, > unfortunately, I can't find any such process. I'd have to catch it red- > handed exactly when it accesses the share. I was suspecting the > "Removable Device Automounter" (kded_device_automounter) and disabled > it, but that didn't change anything. > > Any suggestion what (if any!) part of KDE might be causing this? Any > general suggestion for finding the culprit? > > Michael
Re: Automounted NFS shares never timeout
Hello, i tried it too, in my case, it's 75seconds 2014-03-20 14:21:00 /mnt/smb4/backup/ OPEN,ISDIR 2014-03-20 14:21:00 /mnt/smb4/backup/ CLOSE_NOWRITE,CLOSE,ISDIR 2014-03-20 14:22:15 /mnt/smb4/backup/ OPEN,ISDIR 2014-03-20 14:22:15 /mnt/smb4/backup/ CLOSE_NOWRITE,CLOSE,ISDIR 2014-03-20 14:23:30 /mnt/smb4/backup/ OPEN,ISDIR 2014-03-20 14:23:30 /mnt/smb4/backup/ CLOSE_NOWRITE,CLOSE,ISDIR 2014-03-20 14:24:45 /mnt/smb4/backup/ OPEN,ISDIR 2014-03-20 14:24:45 /mnt/smb4/backup/ CLOSE_NOWRITE,CLOSE,ISDIR Libor On Thursday 20 March 2014 11:43:06 Michael Schuerig wrote: > On Tuesday 18 March 2014 11:47:38 Michael Schuerig wrote: > [...] > > I've reduced my setup to automount only a test share with very little > content. This share gets (auto-)mounted at /net/tardis/srv/test. Autofs > (/etc/auto.net) automatically creates the entire hierarchy including > /net > > $ inotifywait -m -r --format "%T %w %e" --timefmt "%F %T" /net > Setting up watches. Beware: since -r was given, this may take a while! > Watches established. > 2014-03-20 11:02:18 /net/ OPEN,ISDIR > 2014-03-20 11:02:18 /net/ CLOSE_NOWRITE,CLOSE,ISDIR > 2014-03-20 11:02:18 /net/ OPEN,ISDIR > 2014-03-20 11:02:18 /net/tardis/ OPEN,ISDIR > 2014-03-20 11:02:18 /net/ CLOSE_NOWRITE,CLOSE,ISDIR > 2014-03-20 11:02:18 /net/tardis/ CLOSE_NOWRITE,CLOSE,ISDIR > 2014-03-20 11:02:18 /net/tardis/ OPEN,ISDIR > 2014-03-20 11:02:18 /net/tardis/srv/ OPEN,ISDIR > 2014-03-20 11:02:18 /net/tardis/ CLOSE_NOWRITE,CLOSE,ISDIR > 2014-03-20 11:02:18 /net/tardis/srv/ CLOSE_NOWRITE,CLOSE,ISDIR > 2014-03-20 11:02:33 /net/ OPEN,ISDIR > 2014-03-20 11:02:33 /net/ CLOSE_NOWRITE,CLOSE,ISDIR > 2014-03-20 11:02:33 /net/ OPEN,ISDIR > 2014-03-20 11:02:33 /net/tardis/ OPEN,ISDIR > 2014-03-20 11:02:33 /net/ CLOSE_NOWRITE,CLOSE,ISDIR > 2014-03-20 11:02:33 /net/tardis/ CLOSE_NOWRITE,CLOSE,ISDIR > 2014-03-20 11:02:33 /net/tardis/ OPEN,ISDIR > 2014-03-20 11:02:33 /net/tardis/srv/ OPEN,ISDIR > 2014-03-20 11:02:33 /net/tardis/ CLOSE_NOWRITE,CLOSE,ISDIR > 2014-03-20 11:02:33 /net/tardis/srv/ CLOSE_NOWRITE,CLOSE,ISDIR > ... > > These accesses repeat exactly every 15s. They go only as deep as > /net/artis/srv and do not descend into /net/tardis/srv/test. They only > occur when plasma-desktop is running. > > I'm afraid that I may have to dismantle my panels to find the cause, > however, I'm reluctant to do so as setting them up the way I want them > takes quite some time. Is there a way to save/restore the configuration > of one or more panels? > > Michael
Re: Automounted NFS shares never timeout
Now, i have tried # kill -STOP {PID} for ksysguardd, plasma-desktop, krunner, kded4 processes. Only one stopped at a time. Event always occurs. Libor
Re: Automounted NFS shares never timeout
*Hello* *for me, removing all ksysguard plasmoids helped to solve the problem, but now, plasma-nm uses ksysguard for showing interface traffic, so problem is back.* *What's your experience?* *Libor* *On Tuesday 18 March 2014 14:20:25 Michael Schuerig wrote:* *> On Tuesday 18 March 2014 13:18:20 Libor Klepáč wrote:* *> > Hello,* *> > i have simillar problem, but with autofs+cifs.* *> > * *> > I run commands* *> > umount -l /mnt/smb4/*/** *> > /etc/init.d/autofs stop* *> > before leaving home and suspending my notebook.* *> * *> Somewhere in the autofs docs I read a warning against manually* *> unmounting (or mounting) automounted shares. I don't remember the* *> details.* *> * *> > When i forget to run those commands, plasma-desktop and krunner* *> > get stuck after resume.* *> > lsof is also stuck.* *> * *> Have a look at this bug report* *> * *> https://bugs.kde.org/show_bug.cgi?id=184062* *> * *> Michael*
Re: Kmail / Akonadi hanging
Hi, I have seen it once or twice, restarting kmail/kontact helped me. But i have another problem, my whole inbox is (re)downloaded several times a week. Content of inbox just disappears and then it starts to jump back in from year 2013 Libor > Since a while (few months) akonadi 'hangs' from time to time. > This happens when reading or removing emails from my folders. > When it happens, Kmail shows me a nice gfx saying "Retrieving Folder > Contents" and "Please wait ..." > > No matter how long I wait... Kmail does not recover. > Then, I open a console and do 'akonadictl restart', sometimes 'akonadictl > fsck'. Kmail starts working again for a while... > BTW, restarting Kmail does not help at all. > > I see this issue happen on two different SID installations. I already > downgraded on installation to testing, but it did not change a thing. > > Right now it happened again (I can write this mail but sending wouldn't > work. So I have to 'akonadictl restart' before I send it). > > But today, I have console output from akonadictl. Maybe someone may > understand it and can point me to a final solution :-) > > ### > processing retrieval request for item 48489 parts: ("HEAD", "RFC822") of > resource: "akonadi_mixedmaildir_resource_0" > Maildir::size unable to find: "1460545315.R604.blitz-lx" > akonadi_mixedmaildir_resource_0(6928)/akonadiresource (maildir): Failed to > read item "1460545315.R604.blitz-lx" in Maildir "/usr/oms/Mail/inbox" > akonadi_mixedmaildir_resource_0(6928)/akonadiresource (maildir): "Error > while reading mails from folder " > continuing > request for item 48489 "1460545315.R604.blitz-lx" failed: "Unable to > retrieve item from resource: Invalid item retrieved" > ItemRetrieverException : Unable to retrieve item from resource: > Invalid item retrieved > posting retrieval request for item 48352 there are 1 queues and 0 items > in mine > request for item 48352 still pending - waiting > processing retrieval request for item 48352 parts: ("RFC822", "HEAD") of > resource: "akonadi_mixedmaildir_resource_0" > continuing > request for item 48352 succeeded > posting retrieval request for item 48489 there are 1 queues and 0 items > in mine > request for item 48489 still pending - waiting > processing retrieval request for item 48489 parts: ("RFC822", "HEAD") of > resource: "akonadi_mixedmaildir_resource_0" > Maildir::size unable to find: "1460545315.R604.blitz-lx" > akonadi_mixedmaildir_resource_0(6928)/akonadiresource (maildir): Failed to > read item "1460545315.R604.blitz-lx" in Maildir "/usr/oms/Mail/inbox" > akonadi_mixedmaildir_resource_0(6928)/akonadiresource (maildir): "Error > while reading mails from folder " > continuing > request for item 48489 "1460545315.R604.blitz-lx" failed: "Unable to > retrieve item from resource: Invalid item retrieved" > ItemRetrieverException : Unable to retrieve item from resource: > Invalid item retrieved > ### > > > Any idea how I can fix this ? > > > With Best regards, > > Tim
Re: two current issues with Plasma / KF 5 from experimental
Hi, upgraded just yesterday. I see some improvements for now: - qupzilla doesn't say it has no access to network anymore (after resuming) - qupzilla, kmail, plasma panel are on screen - after using xrandr to remove my work monitor and suspend/resume (using systemctl) Which is great improvement for me. But - kded locks up during session start, it has no access to powermanagement + i cannot configure startup services in systemsettings - plasmashell has also slow start (long delay before wallpaper appears, than another delay to show panel and it's content) - krdc has delay in startup (but it had before startup too) - i think, it has something to do with kwallet, because i'm unable to connect to *some* hosts with saved credentials. - ktp cannot save credentials - it crashes when i say to save my password (it was this way before upgrade) ktp-auth-handle[22258]: segfault at c0 ip 7fa5c0b96df4 sp 7ffc7d22a670 error 4 in libsignon-qt5.so.1.0.0[7fa5c0b85000+32000] I tried to strace kded, but I don't see anything usable there. Looking forward for more new versions ;) Thanks, Libor Dne úterý 17. května 2016 9:51:20 CEST, Martin Steigerwald napsal(a): > Hello! > > This can easily be worked around by downgrading a package with > > apt install libkf5networkmanagerqt6=5.16.0-1 > > Bug#824531: Acknowledgement (plasma-nm: error loading QML file applet to > undefined symbol in libplasmanm_editor.so) > https://bugs.debian.org/824531 > > > I think this can also be worked around by downgrading packages, but I didn´t > try as it wants several packages to be downgraded: > > Bug#824528: Acknowledgement (plasma-systray-legacy: not coinstallable with > plasma-workspace 4:5.5.4-1 and some other packages) > https://bugs.debian.org/824528 > > > Otherwise I think my system is completely on Experimental packages now where > available, running Qt 5.6.0. I removed any self-compiled KF5 + KDEPIM stuff > as I had a ton of trouble with it and compiling KDEPIM from master again > needs needs Qt Webengine developer packages that I currently do not find > within Debian. > > I really look forward to a full transition of consistent and recent stable > versions of Plasma and KF 5 as well as Qt 5.6.1 to unstable. > > Thanks,
Re: two current issues with Plasma / KF 5 from experimental
PS: xembedsniproxy seems to be included in plasma-workspace hence the package conflict Libor On úterý 17. května 2016 9:51:20 CEST Martin Steigerwald wrote: > Hello! > > This can easily be worked around by downgrading a package with > > apt install libkf5networkmanagerqt6=5.16.0-1 > > Bug#824531: Acknowledgement (plasma-nm: error loading QML file applet to > undefined symbol in libplasmanm_editor.so) > https://bugs.debian.org/824531 > > > I think this can also be worked around by downgrading packages, but I didn´t > try as it wants several packages to be downgraded: > > Bug#824528: Acknowledgement (plasma-systray-legacy: not coinstallable with > plasma-workspace 4:5.5.4-1 and some other packages) > https://bugs.debian.org/824528 > > > Otherwise I think my system is completely on Experimental packages now where > available, running Qt 5.6.0. I removed any self-compiled KF5 + KDEPIM stuff > as I had a ton of trouble with it and compiling KDEPIM from master again > needs needs Qt Webengine developer packages that I currently do not find > within Debian. > > I really look forward to a full transition of consistent and recent stable > versions of Plasma and KF 5 as well as Qt 5.6.1 to unstable. > > Thanks,
Re: huge fonts and window decorations
Hi, On středa 1. června 2016 16:06:26 CEST Ignacio R. Morelle wrote: > On Wednesday 01 June 2016 21:56:56 Diederik de Haas wrote: > > On Wednesday 01 June 2016 10:58:17 Martin Albrecht wrote: > > > Does anyone have an idea how to fix that? > > > > It will likely fix itself over time. I had that issue too, but with the > > latest packages (on sid), the problem went away. > > I believe it's specifically installing plasma-integration (depended upon by > the newer plasma-desktop) that fixed it for me. It'll take a few days to > migrate to testing though. Thanks, it helped me. But i had to modify this package and drop dependency on QT5.5(abi) , because I installed 5.6 recently (I did same thing with deps in libkf5declarative5 now to be able to upgrade to latest plasma) Libor
akonadi-ews
Hello, just found this https://github.com/KrissN/akonadi-ews Seems to work nicely for now, let's see if it eleminates my problem of imap downloading all my emails several times per week (~4GB mailbox in total). Package is easily made with dh_make and adding --with kde to debian/rules Build deps seems to be extra-cmake-modules, libkf5libkdepim-dev, libkf5akonadimime-dev, libkf5calendarcore-dev, libkf5mime-dev Libor
Re: kde 5.7
Hi, it seems Plasma 5.8 was announced as LTS release, but it's scheduled on 2016/10, it's too late for Stretch? http://jriddell.org/2016/07/08/plasma-5-8-lts-kickerd-off-for-stability-and-performance/ https://community.kde.org/Schedules/Plasma_5 Libor Dne středa 6. července 2016 21:01:56 CEST, Martin Steigerwald napsal(a): > Hi Luc, > > Am Mittwoch, 6. Juli 2016, 19:07:02 CEST schrieb Luc Castermans: > > dear, how can I find out about plans to further absorb KDE release like > > 5.7? > > > > This list or other media. > > As told before here on this list, if you want to know timely about recent > plans of Debian/Kubuntu KDE Team, then lurk on #debian-qt-kde IRC channel. > > What I gathered so far: Maxy plans to go with Plasma 5.7 in Stretch. I don´t > know yet, when he plans starting to upload the packages for it. > > Ciao,
Long delays after suspend
Hello, since last week, I'm experiencing long delays/failures on lot of events. For example it takes minutes to lock screen, suspend doesn't work, plasma cannot control volume, kscreen doesn't detect new screen on putting laptop to docking station, kde-telepathy asking saved passwords ... I think that before first suspend, everything works fine, but after resume, everything is broken. I can't remember, when it started, maybe on upgrade of *gcc* from 6.2.* to 6.3.0 ? It acts like this even after reboot Anyone else experiencing it? Libor
Re: Long delays after suspend
Hi, probably solved. I broke it with pulseaudio settings "tuning" I set this in /etc/pulse/default.pa load-module module-native-protocol-unix auth-anonymous=1 socket=/tmp/pulse-shared-socket-name and in /etc/pulse/client.conf default-server = unix:/tmp/pulse-shared-socket-name autospawn stopped to work, caused some stalls/locks/timeouts. Libor On pátek 6. ledna 2017 14:33:08 CET Libor Klepáč wrote: > [This sender failed our fraud detection checks and may not be who they appear > to be. Learn about spoofing at http://aka.ms/LearnAboutSpoofing] > > Hello, > since last week, I'm experiencing long delays/failures on lot of events. > For example it takes minutes to lock screen, suspend doesn't work, plasma > cannot control volume, kscreen doesn't detect new screen on putting laptop to > docking station, kde-telepathy asking saved passwords ... > I think that before first suspend, everything works fine, but after resume, > everything is broken. > > I can't remember, when it started, maybe on upgrade of *gcc* from 6.2.* to > 6.3.0 ? > > It acts like this even after reboot > > Anyone else experiencing it? > > Libor > >
Re: Plasma 5.10 in experimental ?
Thanks for new packages, looking forward to break my desktop ;) Libor On pondělí 10. července 2017 11:11:14 CEST Maximiliano Curia wrote: > ¡Hola Martin! > > El 2017-07-10 a las 09:47 +0200, Martin Steigerwald escribió: > > Martin Steigerwald - 27.06.17, 11:29: > >> newbee...@nativobject.net - 27.06.17, 10:44: > >>> Is there any imports of Plasma 5.10 and/or KDE application 17.04 on some > >>> experimental mirrors ? > >>> > >> From what I gathered from #debian-qt-kde channel on IRC there is no ETA for > >> updated packages currently. Also from what I read there the team is working > >> on updated Qt packages first. My current bet is that updated KF5 and Plasma > >> packages will follow after Qt upgrade is done. > >> > >> What I have seen is upgraded Plasma LTS 5.8 and KF 5.28 packages in > >> Unstable > >> to fix bugs and requests to include them in Debian Stretch as well. I am > >> not sure how that will continue, once Plasma / KF packages of newer > >> versions are in unstable. > > > > A short update: > > > After the team prepared Qt 5.9.1 in experimental, Maxy is now uploading KF > > 5.36 to experimental as well. After that latest Plasma is a likely > > candidate. > > I've just uploaded most framework packages to experimental, they are not > really for public consumption but to have them go through NEW, probably get > some symbols updates, and reveal some problems with experimental. > > Happy hacking, >
Re: Plasma 5.10 and KF 5.37
Hi, just upgrade to qt5.9, frameworks 5.37 and plasma 5.10, upgrade was smooth, no problem. Logged in again, everything seem to be ok so far. Kde window manager is still in 5.8.7 version Thanks for packages, Libor On pondělí 28. srpna 2017 18:36:55 CEST Martin Steigerwald wrote: > Hello. > > Maxy started uploading Plasma 5.10 to experimental. KF 5.37 appears to be > almost done. > > This is still for build and other testing… but I bet it won´t take all that > long anymore… and our Sid systems should be pretty up-to-date again. > > Aim of Qt/KDE debian/ubuntu team is to remove Qt4 dependency til next release > (buster). Its a challenging task however. > > Thanks, >
Re: Plasma 5.10 and KF 5.37
I couldn't wait anymore ;) Font rendering is little different again, but it was somehow different for me since new fontconfig and libfreetype hit unstable. Now looking forward for refreshed kde-pim (I'm using kontact+self compiled akonadi-ews) Libor On úterý 29. srpna 2017 8:55:40 CEST Martin Steigerwald wrote: > Hi Libor. > > Libor Klepáč - 29.08.17, 08:39: > > just upgrade to qt5.9, frameworks 5.37 and plasma 5.10, > > upgrade was smooth, no problem. > > > > Logged in again, everything seem to be ok so far. > > Kde window manager is still in 5.8.7 version > > Lol, thanks for feedback, Libor. > > I feel tempted :) > > Maybe I wait a day or two whether you encounter a show stopper. > > Thanks, >
Re: Plasma 5.10 and KF 5.37
On úterý 29. srpna 2017 9:00:39 CEST Martin Steigerwald wrote: > Libor Klepáč - 29.08.17, 08:39: > > Kde window manager is still in 5.8.7 version > > Well, I didn´t write that the Plasma 5.10 upload of Maxy is complete yet :). > > There is no newer version available in the archive right now: > Yes of course, it was just info from my upgrade ;) First problem: Amarok stoped to react on play/pause,next,prev buttons. Global shortcut is assigned to component "media control" . I don't know, whether this changed during upgrade. Yes, I realize, that amarok is old and probably will be removed, because of QT4 removal. Libor
Re: Plasma 5.10 and KF 5.37
On úterý 29. srpna 2017 11:10:01 CEST Martin Steigerwald wrote: > Libor Klepáč - 29.08.17, 07:26: > > On úterý 29. srpna 2017 9:00:39 CEST Martin Steigerwald wrote: > > > Libor Klepáč - 29.08.17, 08:39: > > > > Kde window manager is still in 5.8.7 version > > > > > > Well, I didn´t write that the Plasma 5.10 upload of Maxy is complete yet > > > :). > > > There is no newer version available in the archive right now: > > Yes of course, it was just info from my upgrade ;) > > > > > > First problem: > > Amarok stoped to react on play/pause,next,prev buttons. > > Works here. Inside Amarok as well as via new jump list actions and the usual > media controls in system tray. > Can you please check global shortcuts, if media keys are "owned" by Amarok or Media control component? It works after assigning those keys directly to Amarok global shortcuts. It also works from new media control buttons on lock screen, great. > I bet you may missed some upgrade. Maybe > > > Global shortcut is assigned to component "media control" . > > I don't know, whether this changed during upgrade. > > Yes, I realize, that amarok is old and probably will be removed, because of > > QT4 removal. > > I do hope upstream developers manage to finalize a Qt5 versions… but it seems > they need help. It's good player, i got back to it after several years of using mpv from konsole. Libor
Re: Plasma 5.10 and KF 5.37
On úterý 29. srpna 2017 14:15:50 CEST Martin Steigerwald wrote: > Please do not Cc me. I read the list. Ok, sorry, i'm used to answer to all. > > Libor Klepáč - 29.08.17, 12:07: > > On úterý 29. srpna 2017 11:10:01 CEST Martin Steigerwald wrote: > > > Libor Klepáč - 29.08.17, 07:26: > > > > On úterý 29. srpna 2017 9:00:39 CEST Martin Steigerwald wrote: > > > > > Libor Klepáč - 29.08.17, 08:39: > > > > > > Kde window manager is still in 5.8.7 version > > > > > > > > > > Well, I didn´t write that the Plasma 5.10 upload of Maxy is complete > > > > > yet > > > > > > > > > > :). > > > > > > > > > > There is no newer version available in the archive right now: > > > > Yes of course, it was just info from my upgrade ;) > > > > > > > > > > > > First problem: > > > > Amarok stoped to react on play/pause,next,prev buttons. > > > > > > Works here. Inside Amarok as well as via new jump list actions and the > > > usual media controls in system tray. > > > > Can you please check global shortcuts, if media keys are "owned" by Amarok > > or Media control component? > > It works after assigning those keys directly to Amarok global shortcuts. > > > > It also works from new media control buttons on lock screen, great. > > You are using keys? I understood you pressed buttons, so that is what I did. > > I am not sure I have media keys on my ThinkPad keyboards. Hmmm, I don´t think > I have despite louder / more silent / mute. > > Thanks, > Yes, i have HW buttons on my external keyboard @ work, also FN+some key on my Dell laptop. Both are recognized as "Media Play" button See screenshot: https://download.bcom.cz/kde/Screenshot_20170829_142148.png "Přehrát/pozastavit" is "Play/Pause" https://download.bcom.cz/kde/Screenshot_20170829_142202.png "Ovládání medii" is "Media control" (sorry it's in czech language even after launching systemsettings5 with LANG=C + selecting english in help menu) This is how it works. After assigning "Media play" directly to Amarok. Libor
udisks2 upgrade brakes plasma
Hi, do not upgrade to udisk2 2.7.2 It breaks plasma https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873627 Libor
Re: udisks2 upgrade brakes plasma
Hi, On středa 30. srpna 2017 11:55:27 CEST Andrey Rahmatullin wrote: > On Wed, Aug 30, 2017 at 08:44:15AM +0200, Libor Klepáč wrote: > > Hi, > > do not upgrade to udisk2 2.7.2 > > > > It breaks plasma > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873627 > As the bug is RC it is enough to install apt-listbugs. > > thanks, looks useful, I will install it. But I upgraded several hours before this bugreport even existed ;) And was bitten by it today. Libor
Re: Plasma 5.10 and KF 5.37
Hi, kwin 5.10 is here, it was going thru NEW (new libraries abi). Today, i had problem with frozen plasma after wake from suspend to RAM, but it was probably related to yesterdays udisks2 upgrade. Even after launching from konsole, i got this: Trying to use rootObject before initialization is completed, whilst using setInitializationDelayed. Forcing completion Failed enumerating UDisks2 objects: "org.freedesktop.DBus.Error.TimedOut" "Failed to activate service 'org.freedesktop.UDisks2': timed out (service_start_timeout=25000ms)" Failed enumerating UDisks2 objects: "org.freedesktop.DBus.Error.TimedOut" "Failed to activate service 'org.freedesktop.UDisks2': timed out (service_start_timeout=25000ms)" Failed enumerating UDisks2 objects: "org.freedesktop.DBus.Error.TimedOut" "Failed to activate service 'org.freedesktop.UDisks2': timed out (service_start_timeout=25000ms)" After downgrading udisks back, everything works. Plasma still forgets wallpapers on secondary monitors, like in 5.8, i wasn't investigating why. I will have to test window placement with new KWIN, because at work, i have notebook in dock and I have primary monitor in middle, with another on left and my notebook screen on right. All windows are placed on the left one, not the middle one (primary) after putting notebook to dock and resuming from suspend. Libor On pondělí 28. srpna 2017 18:36:55 CEST Martin Steigerwald wrote: > Hello. > > Maxy started uploading Plasma 5.10 to experimental. KF 5.37 appears to be > almost done. > > This is still for build and other testing… but I bet it won´t take all that > long anymore… and our Sid systems should be pretty up-to-date again. > > Aim of Qt/KDE debian/ubuntu team is to remove Qt4 dependency til next release > (buster). Its a challenging task however. > > Thanks, >
Re: Plasma 5.10.5 coming to unstable
Hi, On úterý 12. září 2017 21:45:47 CEST Martin Steigerwald wrote: > KDEPIM 17.08 > does not yet appear to be fully build in experimental yet. I hope to see it > soon. It seems, that parts of KDEPIM are sitting in NEW queue, Libor
Re: Plasma 5.10 in Testing?
Hi, I see those sometimes, starting few minutes after resume. It's fixable by `kquitapp plasmashell` & run it again from krunner. I don't know when it started, i have to candidates: 1) after upgrading to Plasma 5.10 2) after enabling GPU accel in firefox My GPU is VGA compatible controller: Intel Corporation Haswell-ULT Integrated Graphics Controller (rev 0b) BTW: is it safe to upgrade to latest MESA, pulling in libegl1? Last time i tried, it broke GPU acceleration and also video acceleration. There are still some bug reports opened againts MESA. Libor > Dear, > > On " ...experiencing graphic glitches in Testing"since a while I see > irregular glitches on my screen indeed. I already suspected by GPU or > graphic driver, but is it a KDE component? > > > > > > > > > 2017-10-12 12:31 GMT+02:00 devfra : > > > Hi! > > Can someone give us some update about the migration of Plasma 5.10 in > TestingIt started about a month ago but there are components still blocked > in Sid,such as kwin [1] and plasma-workspace [2]. > > Thank you! > > PS: Anyone experiencing graphic glitches in Testing since this > migrationstarted? I have to restart X at least once a day and it is > becoming annoying. > > [1] https://packages.qa.debian.org/k/kwin.html[2] > https://packages.qa.debian.org/p/plasma-workspace.html[3] > > > > Luc Castermansmailto:luc.casterm...@gmail.com[4] > > > > > [1] mailto:devfra_...@inventati.org > [2] https://packages.qa.debian.org/k/kwin.html > [3] https://packages.qa.debian.org/p/plasma-workspace.html > [4] mailto:luc.casterm...@gmail.com
Re: KDEPIM 17.08: The whole thing works
Hi, it works,hurray ;) I find using aptitude easier for upgrades. I just choose some major package like kdepim or kontact or kmail for upgrade and then jump over broken packages with "b" until everything is ok, then press "g" for list of upgraded and not upgaded packages and skim thru not upgraded for any forgoten packages. After upgrade akonadi started it's db upgrade, but my FS became full, i noticed it after day of my disk LED constantly blinking. Maybe some warning/news in akonadi package should be in place? (about resource heavy upgrade of DB) So big thanks to maintainers for fresh packages. Btw. is there a plan for newer versions of kdepim? I have problem with akonadi-ews , unable to send it's emails, which should already be fixed in 17.08.0, but i'm still unable to send emails (I noticed it after 4 days, with over 20 work emails in my outgoing folder ...) https://github.com/KrissN/akonadi-ews/issues/35 Libor On pátek 17. listopadu 2017 0:01:45 CET Martin Steigerwald wrote: > Hello. > > Okay, so I installed Akonadi + KDEPIM 17.08 and the whole things works. > > I had some issues tough. > > What did I do? > > 1. apt install -t experimental kmail – kdewebdev got removed, it appears > it needs an update. Also kdepim related kio plugins got removed, maybe > thats intentional. > > 2. Rebooted and started KMail. Akonadi produced lots of database load > and after a while KMail complained it would not start. Akonadi was indeed > not running only > > 3. I then looked for old 16.04 packages and did the following: > > apt install -t experimental libkf5akonadisearch-data libkf5akonadisearchxapian5 libkf5akonadinotes5 libkf5akonadisearchcore5 > > apt install -t experimental libkf5libkdepim-plugins:amd64 > > apt purge kf5-kdepimlibs-kio-plugins kdepimlibs-data > > (old transitional packages) > > 4. I logged out and in again, making sure that all processes of the user are gone. > > 5. Again Akonadi stopped after a while, complaining it could not find MySQL > socket file, I did not look much closer, MySQL was running initially just > fine and there has been quite some MySQL load. > > 6. But this time KMail offered to start Akonadi again, which I did > > 7. Then KMail said that Akonadi is updating the database to improve > performance. > > 8. It took about 15 minutes or so. > > 9. KAlarm asked about upgrading archived alarms to a new format. > > > I was able to read news feeds in Akregator during the upgrade. Akgregator > is still not Akonadi based. But well whatever the reported crash on start > bug is about, I did not see it. > > > Thats for now. Time to sleep. > > Now let´s see whether it sends this mail :) > > Thanks, > [1] mailto:libor.kle...@bcom.cz [2] tel:+420377457676 [3] http://www.bcom.cz
Re: KDEPIM 17.08: The whole thing works
Hi, On středa 22. listopadu 2017 16:31:21 CET Sandro Knauß wrote: > Hey, > > > I find using aptitude easier for upgrades. > > I just choose some major package like kdepim or kontact or kmail for upgrade > > and then jump over broken packages with "b" until everything is ok, then > > press "g" for list of upgraded and not upgaded packages and skim thru not > > upgraded for any forgoten packages. > > that sounds like a lot of clicky-clicky :) > apt install -t experimental kontact finds a solution that works. Without > manually to solve broken packages. > Okay finding packages that could/should be updated to is not that easy. > Yeah, but it's my morning ritual ;) (and i'm little old-fashioned and like to choose upgrades by hand) And i don't upgrade everything to experimental, for example i was waiting for long time for Mesa and libva2. > > Btw. is there a plan for newer versions of kdepim? > > as always for Debian - it is ready when it is ready - as you see in other mail > thread - pino already started to package 17.08.3 and uploading to unstable. > Sorry i missed that, thanks (i'm not trying to push anyone to making new packages) > > I have problem with akonadi-ews , unable to send it's emails, which should > > already be fixed in 17.08.0, but i'm still unable to send emails (I noticed > > it after 4 days, with over 20 work emails in my outgoing folder ...) > > https://github.com/KrissN/akonadi-ews/issues/35 > > github is not the official channel to communicate with kde software. You > should use bugs.kde.org for this. Just a small subset of KDE developers care > about github... It's not my bug report ;) And author of akonadi-ews says here, that everything is working for him with newest kdepim (that's reason of my question on newer kdepim packages) - i have reverted to using SMTP for now. > > Best Regards, > > hefee > Thanks, Libor
Re: kdepim 17.12.3 entering unstable
Hi, thanks for all packages. I have used it also in experimental, everything is ok. I was able to switch from self-compiled akonadi-ews to one included in this new kdepim packages. But i was still missing EWS based send account. This problem can be fixed by installing kmailtransport-akonadi, so maybe kdepim-runtime should recommend this package. On sobota 31. března 2018 23:11:04 CEST Sandro Knauß wrote: > Hey, > > I now started to upload kdepim 17.12.3 to unstable. It will take some days > till the dust will settle. It is known, that kjots, digikam, zanshin and do > not play nicely toget with kdepim 17.12 and need to recompiled. This will > done within the transition #94342. > > kmymoney in experimental will get an update within the next days and should > be working with new kdepim afterwards. > > Unfortunately you need to say goodbye to blogilo, it was moved to > unmaintained by upstream and it does not build anymore with kdepim 17.12. > If anyone wants to step up for the mantainership... > > Additionally libkolab will be removed, too. Kolab do not ship updates > anymore, that's why kdepim now add a copy of libkolab inide kdepim-runtime. > So you don't loose support for your kolab accounts - but do not need > libkolab anymore. > > hefee
Re: Hanging plasmashell
Hi, i have observed simillar behaviour with autofs mounted samba. I connect to them at home and when I forget to unmount them and go to work (I have laptop and use suspend to RAM), my plasmashell sometime freezes. But krunner is always ok. Also, sometimes, my screen starts to flicker at random places, when i switch tabs in browser, old tab flashes back for few seconds, mouse clicks doesn't propagate, this is also fixable by restarting plasmashell. I have not find root cause of this behaviour. Recently, i switched compositor from OpenGL 3.1 to OpenGL 2.0, it lowered frequency of this events, but it can still happen. Libor On středa 30. května 2018 8:58:47 CEST Frank Mehnert wrote: > Hi all, > > since some days I experience arbitrary hangs of plasmashell. When this > happens, neither the application menu, the task bar nor any systray > application respond to any mouse click. Alt+F2 doesn't work either and > there is nothing else than "killall plasmashell && kstart plasmashell" > to fix the problem. This is Debian/Sid, all packages up-to-date. > > Does anybody else experience similar problems? > > Frank
Re: Hanging plasmashell
Hi, yes, it could be the problem, with new X server 1.20, even SDDM was freezing for me. I downgraded back to 1.19 on same day it appeared in unstable :) Libor On středa 30. května 2018 10:10:21 CEST MERLIN Philippe wrote: > Le mercredi 30 mai 2018, 10:02:35 CEST Frank Mehnert a écrit : > > Hi Libor, > > > > > > My problems started a few days ago and I don't remember changing my > > configuration during these days. > > > > Thanks, > > > > Frank > > look at Bug#900145. > Philippe Merlin
Re: Buster update of qtbase-opensource dfsg-6 to dfsg-7 breaks KMail 4:17.12.3-1
Hi, it also broke owncloud client for me Libor On pondělí 10. září 2018 13:06:04 CEST Andy G Wood wrote: > The recent update in testing/buster of qtbase-opensource from 5.11.1+dfsg-6 > to 5.11.1+dfsg-7 seems to break KMail 4:17.12.3-1. The only way I could > get KMail working again this morning with external imap servers was to > downgrade to the following: > libqt5concurrent5_5.11.1+dfsg-6_amd64.deb > libqt5core5a_5.11.1+dfsg-6_amd64.deb > libqt5dbus5_5.11.1+dfsg-6_amd64.deb > libqt5gui5_5.11.1+dfsg-6_amd64.deb > libqt5network5_5.11.1+dfsg-6_amd64.deb > libqt5opengl5_5.11.1+dfsg-6_amd64.deb > libqt5printsupport5_5.11.1+dfsg-6_amd64.deb > libqt5sql5_5.11.1+dfsg-6_amd64.deb > libqt5sql5-mysql_5.11.1+dfsg-6_amd64.deb > libqt5sql5-sqlite_5.11.1+dfsg-6_amd64.deb > libqt5test5_5.11.1+dfsg-6_amd64.deb > libqt5widgets5_5.11.1+dfsg-6_amd64.deb > libqt5xml5_5.11.1+dfsg-6_amd64.deb > > Andy.
Re: Chromium prevents screen going into power saving mode
Hi, i use teams for linux, which uses chromium to show "the app". Problem is, that chromium inhibits power management during upload or download. And teams app save something to server every few seconds .. https://github.com/ivelkov/teams-for-linux/issues/10 Libor On neděle 9. září 2018 21:09:52 CEST inkbottle wrote: > On my laptop, screen usually goes into power saving mode, after a few tens > of seconds. (this laptop never goes to sleep, generally speaking, but I > like the screen to turn itself off nevertheless) > > In contrast, when I have an opened Chromium window, screen often never goes > into power saving mode. > > I haven't found any comments, nowhere, regarding that, on the net. > > I might want to file a bug about that, but since it might be "desktop > dependent", I prefer to ask you if you have observed this situation. > > I can't see anything, but Chromium, at the origin of the screen remaining > turned on forever; occurrences point very consistently in that direction. > > Pages that were opened this time, were: > > Two google search pages; > > Five pages there: https://orgmode.org/worg/ and > there: https://orgmode.org/manual/ > > And that: https://www.cs.tufts.edu/~nr/noweb/ > > So, as it is this time, nothing with aggressive advertising, or auto-playing > videos, or whatever in that line. > > That issue, which I might be alone experiencing, is quite cumbersome, since > it forces me to close Chromium, even though I haven't finished reading what > it is I'm reading; that if I want my screen not to be prevented to go in > power saving mode. > > Thanks, > Chris
Re: kdepim 18.08.1 entering unstable
Hi, just upgraded, everything seems to be ok, thank you very much. I had problem before, kontact was eating 100% cpu, it is still eating 100% after upgrade. It's polling FD=5 poll([{fd=5, events=POLLIN}, {fd=8, events=POLLIN}, {fd=341, events=POLLIN}, {fd=397, events=POLLIN}, {fd=436, events=POLLIN}, {fd=445, events=POLLIN}, {fd=447, events=POLLIN}, {fd=449, events=POLLIN}, {fd=451, events=POLLIN}, {fd=452, events=POLLIN}, {fd=456, events=POLLIN}, {fd=458, events=POLLIN}, {fd=459, events=POLLIN}, which is something called [eventfd] Libor On středa 3. října 2018 0:15:21 CEST Sandro Knauß wrote: > Hey, > > I uploaded kdepim 18.08.1 to unstable some minutes ago. I tested it for > around 15 days, without any issues. It may take some days till the dust > will settle. It is additionally known, that ktorrent, kio-gdrive, blogilo, > kjots, zanshin, digikam, kraft and kmymoney needs to be recompiled against > kdepim 18.08. This will done within the transition #909288. > > kmymoney in experimental will get an update within the next days and should > be working with new kdepim afterwards. > > hefee [1] mailto:libor.kle...@bcom.cz [2] tel:+420377457676 [3] http://www.bcom.cz
Re: kdepim 18.08.1 entering unstable
Hi, my kmail shows this sidebar without problems in new version Libor On sobota 6. října 2018 11:49:26 CEST Martin Steigerwald wrote: > Martin Steigerwald - 06.10.18, 11:09: > > Martin Steigerwald - 03.10.18, 08:16: > > > Since I use kmymoney quite often meanwhile, I will likely wait till > > > it all fits together before I upgrade. > > > > What gives. I can do without KMyMoney for a while, so I just upgraded. > > > > All well so far. :) > > One minor thing I found: I now have that sidebar telling me whether it > is a HTML message or not. I think I made it to be gone before, but did > not find that option anymore. I remember having seen a bug report about > this. > > Anyway, that is clearly an upstream issue. > > Thanks,
Re: kdepim 18.08.1 entering unstable
On neděle 7. října 2018 0:42:29 CEST Martin Steigerwald wrote: > Libor Klepáč - 06.10.18, 19:32: > > On sobota 6. října 2018 11:49:26 CEST Martin Steigerwald wrote: > > > Martin Steigerwald - 06.10.18, 11:09: > […] > > > > One minor thing I found: I now have that sidebar telling me whether > > > it is a HTML message or not. I think I made it to be gone before, > > > but did not find that option anymore. I remember having seen a bug > > > report about this. > > > > > > Anyway, that is clearly an upstream issue. > > > > my kmail shows this sidebar without problems in new version > > Sure it does. > > But I prefer it not to be there. > > Thanks, Hi, sorry, i did read your email other way around. Libor
Re: KDEPIM 18.08.3 for Buster
Hi, i'm using EWS without problems for some time (well - sometimes, i have to restart akonadi or it won't sync emails ...). I have attached my setup as screenshot. (I have autodiscovery disabled and use "user agent"="Outlook 2016" on other tab). You have to install package kmailtransport-akonadi to be able to send emails thru EWS. This package is not recommended by any other package so it is not installed by default. Libor On čtvrtek 7. února 2019 11:10:21 CET you wrote: > Hello Sandro. > > Sandro Knauß - 07.02.19, 00:33: > > as Debian is already in freeze, the version of KDEPIM that will > > shipped with the next stable is 18.08.3. That was uploaded same days > > ago. There is no time to package 18.12.X sorry for that. > > So please test this version in more depth and report issues. If you > > also manage to point to existing bugfixes like done in #921535 it is > > very likely we can ship a that bugfix also for Buster. > > While I had hoped for KDEPIM 18.12, I certainly accept and understand > your decision. > > I probably will test whether I can get Akonadi EWS with Office 365 – not > my choice, mind you – to work for me with that version. So far I was not > able to, but by triaging upstream reports I did not yet find one that > applies to my situation. So maybe it is still a configuration issue on my > side. Evolution with EWS just works fine, including calendar. > > Aside from that since KDEPIM/Akonadi 18.08 I see stalls when downloading > POP3 messages from my private Dovecot server. Often Akonadi/KMail just > sits there, according to atop apparently doing nothing, for up to a > minute, before continuing as if nothing has happened. That behavior has > been so erratic, that I did not yet invest more time to actually find out > what is going on here. Sometimes it works normally and sometimes I see > those stalls. I was disappointed cause I expected the work of Daniel¹ to > improve performance of KDEPIM/Akonadi quite a bit and did not have those > delays with earlier KDEPIM/Akonadi. According to akonadictl fsck there > are quite some issues with my setup… and I wonder whether to recreate it > once again as akonadictl fsck does not seem to fix any of those. However… > that would be something for upstream mailing list kdepim-users (where I > raised this issue quite some time ago). > > I know both upstream development and packaging it can use more hands. So > I mean no offense to anybody with that. > > [1] https://www.dvratil.cz/2018/04/my-kde-pim-update/ > > Thanks, [1] mailto:libor.kle...@bcom.cz [2] tel:+420377457676 [3] http://www.bcom.cz
Re: KDEPIM 18.08.3 for Buster
Hi, thanks for update. Works ok, no problems. It took while to startup kontact on first run. I still have problem with 100% CPU usage in kontact (and/or kmail). It's using CPU even if i shutdown akonadi server. I don't know how to debug. According to strace, it's pooling file descriptor 5 in loop, which is [eventfd]. [pid 2317] poll([{fd=5, events=POLLIN}, {fd=8, events=POLLIN}, {fd=56, events=POLLIN}, {fd=170, events=POLLIN}, {fd=174, events=POLLIN}, {fd=175, events=POLLIN}, {fd=176, events=POLLIN}, {fd=177, events=POLLPRI}, {fd=178, events=POLLIN}], 9, 0) = 1 ([{fd=5, revents=POLLIN}]) [pid 2317] read(5, "\1\0\0\0\0\0\0\0", 16) = 8 [pid 2317] write(5, "\1\0\0\0\0\0\0\0", 8) = 8 [pid 2317] poll([{fd=5, events=POLLIN}, {fd=8, events=POLLIN}, {fd=56, events=POLLIN}, {fd=170, events=POLLIN}, {fd=174, events=POLLIN}, {fd=175, events=POLLIN}, {fd=176, events=POLLIN}, {fd=177, events=POLLPRI}, {fd=178, events=POLLIN}], 9, 0) = 1 ([{fd=5, revents=POLLIN}]) [pid 2317] read(5, "\1\0\0\0\0\0\0\0", 16) = 8 [pid 2317] write(5, "\1\0\0\0\0\0\0\0", 8) = 8 Libor On čtvrtek 7. února 2019 0:33:38 CET Sandro Knauß wrote: > Hey, > > as Debian is already in freeze, the version of KDEPIM that will shipped with > the next stable is 18.08.3. That was uploaded same days ago. There is no > time to package 18.12.X sorry for that. > So please test this version in more depth and report issues. If you also > manage to point to existing bugfixes like done in #921535 it is very likely > we can ship a that bugfix also for Buster. > > hefee
Re: Debian Buster, KDE, Amarok and zombies of ThreadWeaver::T
Hi, On úterý 12. února 2019 9:50:01 CET Lars Schimmer wrote: > On 2/11/19 2:22 PM, Lisandro Damián Nicanor Pérez Meyer wrote: > > El lunes, 11 de febrero de 2019 06:56:19 -03 Lars Schimmer escribió: > >> On 2/9/19 8:37 PM, Lisandro Damián Nicanor Pérez Meyer wrote: > >>> El jueves, 7 de febrero de 2019 10:44:31 -03 Lars Schimmer escribió: > Hi! > > > Is this already known, or new? > Should I open a bug in amarok debian? > Any ideas where it comes from? > >>> > >>> tl;dr: amarok is dead upstream (or almost dead), you are better of > >>> looking > >>> for another music player. > >>> > >>> I particulary like mpd + all it's clients, but it's for locally > >>> available > >>> music. > >> > >> Does any of these player play well with 2TB of MP3 files? > > > > mpd does, it depends on the client though. > > > >> Fast enough and comfortable like Amarok? > > > > That's a client thing, try cantata for example. > > Looks a bit too much for a local player, but will test it. > I have just unistalled amarok (which suited me, but was a little overkill for streaming internet radio) and installed clementine to find out, that it has problems with internet radio (after unpausing, it plays to end of buffer and then switches to next track). Strawbs player proposed in another email has no support for internet radio (or i did not see it). I tried to install qmmp and it seems to be great player (I was user of old winamp some 20 years ago and qmmp brings back memories :) Libor > > And as a bonus you will be able to control the reproduction from multiple > > devices. > > not much needed right now, maybe handy next year. > > > MfG, > Lars Schimmer
Re: Plasma 5.17.5 available in experimental
Hello, everything was upgraded smoothly. Everything seems to work. Only problem is very small font in sddm login screen. (I did not reboot, just restarted sddm service, so it may resolve after reboot) Thank you very much for packages Libor Pino Toscano píše v Út 21. 01. 2020 v 06:37 +0100: > Hi, > > as it was mentioned already in other threads on this list, > Plasma 5.17.5 is available in experimental. > > Make sure you get plasma-desktop >= 4:5.17.5-2 and > plasma-workspace >= 4:5.17.5-2, as they solve a number of update > issues > from testing. Also make sure that you pull *all* the Plasma bits from > experimental, as I did not update all the requirements yet (including > the kde-plasma-desktop metapackage, which is what you ought to have > to > get Plasma BTW). The only known issue at the moment is with > kde-config-systemd, already tracked as bug #949318, and that will be > fixed only when uploading Plasma 5.17 to unstable. > > In case of any issues please do report them *here* (on this debian- > kde > mailing list) for now. > > No ETA on upload to unstable. > > Thanks,
Re: Kde experimental still not installable due to kwayland server in new queue
Hi, so I have just upgraded to plasma 5.19 and frameworks 5.74 (I had to remove kdevelop), everything is running ok so far. Thanks to all involved, Libor On Ne, 2020-10-18 at 19:04 +0200, Marco Valli wrote: > In data domenica 18 ottobre 2020 12:23:08 CEST, Eric Valette ha > scritto: > > Saw kwin-x11 entering unstanble but not installable > > due to missing libkwaylandserver5 held in NEW queu for 2 months > > now... > > > And now only plasma-desktop is missing... > A step at a time. > > regards >
Re: You can help: Test Plasma 5.20.4 and test applications 20.12
Hi, i upgraded to Plasma 5.20.4 when it appeared in experimental. So far so good. Today I also upgraded qt5, without problems (but I have not logged in again, yet) Thanks to all packagers Libor On So, 2020-12-12 at 19:37 +0100, Martin Steigerwald wrote: > Hi! > > If you are feeling adventurous and are using Sid, then you can help > by > testing Plasma 5.20.4 from experimental. I installed it using > > apt install -t experimental plasma-base > > "plasma-base" is a new package to keep the versions of all Plasma > packages in lock step. > > But beware currently Qt 5.15.2 is entering into Sid. It may need a > day > or two to complete. Be extra careful during that time. > > Also you can help test new application 20.12 packages as they enter > unstable. Use them and report any issues you find with them. > > Please do this only if you feel up to it and are willing to keep the > pieces in case something breaks. Of course you can always ask for > help > here, but it would be good if you are willing to do your best to > resolve > and diagnose issues on your own first and then if need be report with > as > much detail as possible. > > If unsure whether it is really a Debian bug or you like to learn > about > which package to report the bug for, feel free to ask here first. > > So far I am very happy with Plasma 5.20.4 and those KDE application > packages I upgraded. I thank Norbert, Aurélien, Sandro who is in the > process to upgrade KDEPIM packages to 20.08.3, Dmitry and everyone > else > who is involved with upgrading the packages or helps testing them. > > Thank you,
Re: Unable to access plasma desktop after nvidia drive upgrade on testing
Hi, i think, i was bitten by this today, after rebooting to upgraded KDE. I workarounded it by disabling compositor, using openbox session Libor On Út, 2021-10-19 at 11:27 +0200, Marc Bres Gil wrote: > Thanks a lot Sami, > > I thought it was nvidia driver problem as it was the "big" package on > the upgrade. But you are right, downgrading the libkdecorations2-5v5 > allowed me to access kde again! > After your indications I've found the bug 996726 which was exactly > what was happening to me. > > Thanks for your quick response! > > > Missatge de Sami Erjomaa del dia dt., 19 > d’oct. 2021 a les 11:17: > > On Tue, 19 Oct 2021 at 11:46, Marc Bres Gil > > wrote: > > > Good Morning, > > > > > > Yesterday I've did a apt upgrade which upgraded the nvidia-driver > > > to 470 on my debian testing system. > > > After the corresponding reboot, SDDM starts ok, but when I input > > > my credentials plasma desktop hangs on the splash screen. > > > > > > Now I've installed cinnamon DE (a lot uglier btw) which works, so > > > seems some problem between plasma and new nvidia-driver. > > > I've created a new user from scratch to check if there are some > > > problems with user profile customizations, but got the same > > > behavior, after entering the credentials on sddm, plasma hangs on > > > the splash screen. > > > > > > I've checked the xorg.0.log, and seen nothing there. > > > Anyone has the same problem? > > > Can you guide me on which logs I have to check to find the > > > problem? > > > > > > Thank you > > > > > > -- > > > Marc Bres Gil > > > m...@bres.cat > > > marc.b...@gmail.com > > > > Hi, > > > > Downgrade libkdecorations2-5v5 to version 5.21.5-2 > > > > -- > > Sami Erjomaa > > linktr.ee/erjomaa > >
Re: Illegal instruction when running in kvm?
Hi, seems to be account related problem. No problem on fresh newly installed VM. No problem on fresh account on old VM. Maybe something with compositor? Thanks, Libor
Illegal instruction when running in kvm?
Hello, i have Debian 11 desktop VM with KDE running on Debian 11 machine using KVM. I'm migrating from current Dell T1700SFF with i7 CPU to Dell R420 with xeon processor. I used dd to transfer disks from old machine to new and then copied it's vm.xml from libvirt. When i launch desktop on new server, i get this Executable: ksplashqml PID: 2146 Signal: Illegal instruction (4) Time: 2/11/22 10:12:49 AM CET and dmesg says [ 248.820494] traps: QSGRenderThread[2145] trap invalid opcode ip:7fd5842f6027 sp:7fd5858a0820 error:0 ksplash, plasmashell, systemsettings5 - all does not work, crashes with illegal instruction. But for example kwin, konsole, dolphin - all this is started in my KDE session. What can be the problem? I checked filesystem on cloned machine with btrfs scrub, tried to reinstall libc6 and all libqt5 packages, also run debsums to check all files - everything was OK. I also tried to upgrade libvirt (7.0 -> 8.0) and qemu (5.2 -> 6.2) on my new server. I use nomachine to connect to desktop. Also tried xrdp. Also connected via ssh and started systemsettings5, with the same error Any clues? Thanks, Libor
Re: Illegal instruction when running in kvm?
Hi, yeah, seems like that. I "fixed" it by deleting all KDE settings. I use this VM just for web browsing, so no big loss. Libor On Pá, 2022-02-11 at 22:24 +, Alex DEKKER wrote: > On 11/02/2022 09:22, Libor Klepáč wrote: > > I'm migrating from current Dell T1700SFF with i7 CPU to Dell R420 > > with > > xeon processor. > > > and dmesg says > > [ 248.820494] traps: QSGRenderThread[2145] trap invalid opcode > > ip:7fd5842f6027 sp:7fd5858a0820 error:0 > > > > I think this is much more likely to be a KVM issue than a KDE one, > but > what exactly, I cannot say. Something like, new CPU is missing some > instructions that old CPU had? > > alexd >
Re: Illegal instruction when running in kvm?
But it seems to be interesting, that some HW fingerprint is embeded in KDE config. Libor On Pá, 2022-02-11 at 22:24 +, Alex DEKKER wrote: > On 11/02/2022 09:22, Libor Klepáč wrote: > > I'm migrating from current Dell T1700SFF with i7 CPU to Dell R420 > > with > > xeon processor. > > > and dmesg says > > [ 248.820494] traps: QSGRenderThread[2145] trap invalid opcode > > ip:7fd5842f6027 sp:7fd5858a0820 error:0 > > > > I think this is much more likely to be a KVM issue than a KDE one, > but > what exactly, I cannot say. Something like, new CPU is missing some > instructions that old CPU had? > > alexd >
Re: Illegal instruction when running in kvm?
On Po, 2022-02-14 at 12:31 +, Alex DEKKER wrote: > On 14/02/2022 08:43, Libor Klepáč wrote: > > But it seems to be interesting, that some HW fingerprint is embeded > > in > > KDE config. > > > Well...it's going to be the Qt libraries that use whatever these > functions are, probably not KDE itself. But I never had this issue > when > using same KDE profile shared to different machines with NFS. So I > don't > really know what the cause is here. I used to have USB flash with debian & KDE used for diagnostics and data recovery and used it in around 70 computers (at least according to generated unique ethernet interface names) without any problems. (we called it "promiscuous flash drive" :) It was variety of different desktops, servers , amd cpu, intel cpu ... never had a problem > > alexd > Libor
Re: Wayland in current KDE
On Út, 2022-02-01 at 20:09 +0100, chris wrote: > On Monday, 31 January 2022 11:10:35 CET Marc Haber wrote: > > Hi, > > > > I tried Wayland recently. Looked ok, but was hardly usable. The > > Panels > > show, but don't accept any mouse clicks (neither left nor right). > > "Leave" in the desktop's right-click menu didn't work either, had > > to > > Ctrl-Alt-Backspace myself out of the session. > > > > Is this the expected beavior of a KDE Wayland session in current > > Debian > > unstable? If not, which package deserves the bug report? > > Here on old lenovo laptop with intel integrated gpu and external 4k > monitor . > The experience is, all in all, way better than what it was with X11. > Chris Hi, how did you deal with screen layout changes when disconnecting laptop from external monitor? I mean - on xwindows, when i connect my laptop to dock, my primary screen moves to external monitor, when i disconnect it moves back. With wayland, all panels and windows stayed on laptop screen, when I plugged laptop to dock. I wanted to try wayland, because my browsers (edge, chromium) sometimes does this https://www.youtube.com/watch?v=WRIkewXZga4 and i think it's xwindows related Libor > > > > > Greetings > > Marc > > > >
Re: Plasma 5.24 coming to unstable
Thanks for your work and upload. Updated without problems and as heavy shade/unshade window user, I immediately hit this: https://bugs.kde.org/show_bug.cgi?id=450777 It will be tough, I shade my windows without thinking about it ;) Libor On Ne, 2022-02-27 at 00:15 +0100, Patrick Franz wrote: > Hi all, > > we've just uploaded Plasma 5.24.2 to unstable. The first packages > should > be arriving in a couple of hours. > > As always, be careful when you upgrade and make sure that you upgrade > the entire Plasma stack at once to avoid mixing 5.23 and 5.24. > >
Re: Plasma 5.24 coming to unstable
Hi, seems to be fixed in plasma 5.24.3 With regards, Libor On St, 2022-03-02 at 13:47 +0100, Aurélien COUDERC wrote: > > > Dear Libor, > > Le 2 mars 2022 10:00:43 GMT+01:00, "Libor Klepáč" > a écrit : > > Thanks for your work and upload. > > > > Updated without problems and as heavy shade/unshade window user, I > > immediately hit this: > > > > https://bugs.kde.org/show_bug.cgi?id=450777 > > > > It will be tough, I shade my windows without thinking about it ;) > > I'm not using that feature but I can understand your frustration. :-) > > Feel free to comment on the upstream bug, to follow-up here and if a > patch gets merged upstream we can add it to the Debian package. > > We can even walk you through if you're interested in cherry picking > such a patch into the package yourself so it benefits everyone > (better on IRC than on a mailing list though). > > > Cheers, > -- > Aurélien >
Re: Plasma 5.24 coming to unstable
Just an observation to this. It was fixed for maximized windows, still did not work with normal windows. Today i switched from breeze decoration to materia and it works now Libor On St, 2022-03-02 at 13:47 +0100, Aurélien COUDERC wrote: > > > Dear Libor, > > Le 2 mars 2022 10:00:43 GMT+01:00, "Libor Klepáč" > a écrit : > > Thanks for your work and upload. > > > > Updated without problems and as heavy shade/unshade window user, I > > immediately hit this: > > > > https://bugs.kde.org/show_bug.cgi?id=450777 > > > > It will be tough, I shade my windows without thinking about it ;) > > I'm not using that feature but I can understand your frustration. :-) > > Feel free to comment on the upstream bug, to follow-up here and if a > patch gets merged upstream we can add it to the Debian package. > > We can even walk you through if you're interested in cherry picking > such a patch into the package yourself so it benefits everyone > (better on IRC than on a mailing list though). > > > Cheers, > -- > Aurélien >
Re: Many thanks for KDEPIM 22.08!
Hi, anyone using EWS with office365? Is it working? It stopped working for me several years ago and i switched to evolution. I would like to switch back to KDEPIM if it works again. I will try Thanks for the packages Libor On So, 2022-09-10 at 21:24 +0200, Martin Steigerwald wrote: > Hi! > > Many thanks for KDEPIM 22.08 packages. > > Still need to wait a bit here with dist-upgrade, but I bet it will be > soon enough! > > Ciao,
krdc acting strange/blank screen
Hi guys, anyone having problems with krdc lately? About a week or two? Maybe connected to qt5 upgrade on end of september? When i connect to some remote desktop, everything is ok, as always. But when i minimize window with krdc or switch to another desktop and then go back to krdc, viewport of remote connection is just blue screen. I have to close connection and open it again. When i open more connections it gets even more broken and i have to quit and start krdc, because it looses even tqhe list of my recent connections. I'm on debian unstable Any clues? Thanks, Libor
Re: krdc acting strange/blank screen
Hi, thanks for new version, I grabbed it from incoming, right when I read your email ;) Unfortunately it does not fix the problem for me. Commit you referred seems to be VNC related, i don't have any VNC connections to test, I use it for RDP. I tried to set fixed resolution for connection instead of "Current KRDC size" when connecting, but it did not help either With regards, Libor On Út, 2022-10-11 at 08:57 +0200, Aurélien COUDERC wrote: > Le lundi 10 octobre 2022, 12:51:46 CEST Libor Klepáč a écrit : > > Hi guys, > > anyone having problems with krdc lately? About a week or two? Maybe > > connected to qt5 upgrade on end of september? > > > > When i connect to some remote desktop, everything is ok, as always. > > But when i minimize window with krdc or switch to another desktop > > and > > then go back to krdc, viewport of remote connection is just blue > > screen. > > I have to close connection and open it again. > > When i open more connections it gets even more broken and i have to > > quit and start krdc, because it looses even tqhe list of my recent > > connections. > > There’s this upstream commit that could be a fix to what you’re > describing: > https://invent.kde.org/network/krdc/- > /commit/0760c9583c2e9657cfdc4ecad114ad5b7b310140 > > I’ve just uploaded 22.08.1 so it should reach unstable in the coming > hours. Feel free to test and report back. > > > Happy hacking ! > -- > Aurélien > >
Re: krdc acting strange/blank screen
On Út, 2022-10-11 at 10:41 +0200, Aurélien COUDERC wrote: > > > Le 11 octobre 2022 10:29:44 GMT+02:00, "Libor Klepáč" > a écrit : > > Hi, > > thanks for new version, I grabbed it from incoming, right when I > > read > > your email ;) > > Unfortunately it does not fix the problem for me. > > Commit you referred seems to be VNC related, i don't have any VNC > > connections to test, I use it for RDP. > > > > I tried to set fixed resolution for connection instead of "Current > > KRDC > > size" when connecting, but it did not help either > > OK, then the best would be to report it upstream describing your use > case and issue. Ok, I will try later, thanks Libor > > Cheers, > -- > Aurélien
Re: krdc acting strange/blank screen
Hi, somebody already reported it, i did not find this when writing my first email https://bugs.kde.org/show_bug.cgi?id=460089 I have provided some more info to the issue With regards, Libor On Út, 2022-10-11 at 10:41 +0200, Aurélien COUDERC wrote: Le 11 octobre 2022 10:29:44 GMT+02:00, "Libor Klepáč" mailto:libor.kle...@bcom.cz>> a écrit : Hi, thanks for new version, I grabbed it from incoming, right when I read your email ;) Unfortunately it does not fix the problem for me. Commit you referred seems to be VNC related, i don't have any VNC connections to test, I use it for RDP. I tried to set fixed resolution for connection instead of "Current KRDC size" when connecting, but it did not help either OK, then the best would be to report it upstream describing your use case and issue. Cheers, -- Aurélien
Re: krdc acting strange/blank screen
Hi, it seems it may be fixed with qt 5.15.7. https://bugs.kde.org/show_bug.cgi?id=460089 I tried to install this version of qt5 from experimental in chroot to test it, but i cannot run krdc with it, crashes and complains LD_LIBRARY_PATH=. krdc Cannot mix incompatible Qt library (5.15.6) with this library (5.15.7) Libor From: Aurélien COUDERC Sent: Tuesday, October 11, 2022 10:41 To: Libor Klepáč ; debian-kde@lists.debian.org Subject: Re: krdc acting strange/blank screen Le 11 octobre 2022 10:29:44 GMT+02:00, "Libor Klepáč" a écrit : >Hi, >thanks for new version, I grabbed it from incoming, right when I read >your email ;) >Unfortunately it does not fix the problem for me. >Commit you referred seems to be VNC related, i don't have any VNC >connections to test, I use it for RDP. > >I tried to set fixed resolution for connection instead of "Current KRDC >size" when connecting, but it did not help either OK, then the best would be to report it upstream describing your use case and issue. Cheers, -- Aurélien
Re: krdc acting strange/blank screen
Hi, just to let you know, it fixed itself somehow without libqt5 upgrade. I needed to reboot today and it works now without problems. Libor From: Aurélien COUDERC Sent: Tuesday, October 11, 2022 10:41 To: Libor Klepáč ; debian-kde@lists.debian.org Subject: Re: krdc acting strange/blank screen Le 11 octobre 2022 10:29:44 GMT+02:00, "Libor Klepáč" a écrit : >Hi, >thanks for new version, I grabbed it from incoming, right when I read >your email ;) >Unfortunately it does not fix the problem for me. >Commit you referred seems to be VNC related, i don't have any VNC >connections to test, I use it for RDP. > >I tried to set fixed resolution for connection instead of "Current KRDC >size" when connecting, but it did not help either OK, then the best would be to report it upstream describing your use case and issue. Cheers, -- Aurélien
Compositing not enabled in kwin-x11
Hello, i have just noticed, that i don't have composition enabled in my kwin x11 session. I don't remember, when this happened. I have new laptop for several months and i don't remember if composition worked on my old laptop. Both are with some intel intergrated gpu (sorry, don't know how to get details, my lspci says "Intel Corporation Raptor Lake-P [Iris Xe Graphics] (rev 04) "). Old laptop was running Debian/Sid, new laptop is Debian/Trixie . I have copied my home directory from old laptop to new. In kwinrc, i have this [Compositing] Backend=OpenGL GLColorCorrection=false GLCore=true GLPlatformInterface=egl GLPreferBufferSwap=a GLTextureFilter=0 HiddenPreviews=5 LatencyPolicy=Low OpenGLIsUnsafe=false UnredirectFullscreen=false WindowsBlockCompositing=false XRenderSmoothScale=false and qdbus org.kde.KWin /KWin supportInformation says KWin Support Information: The following information should be used when requesting support on e.g. https://forum.kde.org. It provides information about the currently running instance, which options are used, what OpenGL driver and which effects are running. Please post the information provided underneath this introductory text to a paste bin service like https://paste.kde.org instead of pasting into support threads. == Version === KWin version: 5.27.9 Qt Version: 5.15.10 Qt compile version: 5.15.10 XCB compile version: 1.15 Operation Mode: X11 only Build Options = KWIN_BUILD_DECORATIONS: yes KWIN_BUILD_TABBOX: yes KWIN_BUILD_ACTIVITIES: yes HAVE_X11_XCB: yes HAVE_EPOXY_GLX: yes X11 === Vendor: The X.Org Foundation Vendor Release: 12101009 Protocol Version/Revision: 11/0 SHAPE: yes; Version: 0x11 RANDR: yes; Version: 0x14 DAMAGE: yes; Version: 0x11 Composite: yes; Version: 0x4 RENDER: yes; Version: 0xb XFIXES: yes; Version: 0x50 SYNC: yes; Version: 0x31 GLX: yes; Version: 0x0 Decoration == Plugin: org.kde.kwin.aurorae Theme: __aurorae__svg__Materia-Dark Plugin recommends border size: No onAllDesktopsAvailable: true alphaChannelSupported: false closeOnDoubleClickOnMenu: false decorationButtonsLeft: 0, 2 decorationButtonsRight: 6, 3, 4, 5 borderSize: 2 gridUnit: 10 font: Linux Biolinum O,10,-1,5,50,0,0,0,0,0,Regular smallSpacing: 2 largeSpacing: 10 Output backend == Name: KWin::X11StandaloneBackend Cursor == themeName: Alkano-Aluminium themeSize: 24 Options === focusPolicy: 1 xwaylandCrashPolicy: xwaylandMaxCrashCount: 3 nextFocusPrefersMouse: false clickRaise: true autoRaise: false autoRaiseInterval: 750 delayFocusInterval: 300 shadeHover: false shadeHoverInterval: 250 separateScreenFocus: false activeMouseScreen: true placement: activationDesktopPolicy: 0 focusPolicyIsReasonable: true borderSnapZone: 10 windowSnapZone: 10 centerSnapZone: 0 snapOnlyWhenOverlapping: false rollOverDesktops: false focusStealingPreventionLevel: 1 operationTitlebarDblClick: 5009 operationMaxButtonLeftClick: 5000 operationMaxButtonMiddleClick: 5015 operationMaxButtonRightClick: 5014 commandActiveTitlebar1: 0 commandActiveTitlebar2: 28 commandActiveTitlebar3: 2 commandInactiveTitlebar1: 4 commandInactiveTitlebar2: 28 commandInactiveTitlebar3: 2 commandWindow1: 7 commandWindow2: 8 commandWindow3: 8 commandWindowWheel: 28 commandAll1: 10 commandAll2: 3 commandAll3: 14 keyCmdAllModKey: 16777250 condensedTitle: false electricBorderMaximize: true electricBorderTiling: true electricBorderCornerRatio: 0.25 borderlessMaximizedWindows: false killPingTimeout: 5000 hideUtilityWindowsForInactive: true compositingMode: 1 useCompositing: true hiddenPreviews: 1 glSmoothScale: 0 glStrictBinding: true glStrictBindingFollowsDriver: true glPreferBufferSwap: 97 glPlatformInterface: 2 windowsBlockCompositing: false latencyPolicy: renderTimeEstimator: allowTearing: true Screen Edges desktopSwitching: false desktopSwitchingMovingClients: false cursorPushBackDistance: 1x1 timeThreshold: 150 reActivateThreshold: 350 actionTopLeft: 0 actionTop: 0 actionTopRight: 0 actionRight: 0 actionBottomRight: 0 actionBottom: 0 actionBottomLeft: 0 actionLeft: 0 Screens === Active screen follows mouse: yes Number of Screens: 2 Screen 0: - Name: DP-1 Enabled: 1 Geometry: 0,0,3440x1440 Scale: 1 Refresh Rate: 59972 Adaptive Sync: incapable Screen 1: - Name: eDP-1 Enabled: 1 Geometry: 842,1440,1920x1200 Scale: 1 Refresh Rate: 60003 Adaptive Sync: incapable Compositing === Compositing is not active Is there anything to do to enable compositing? Thanks, Libor
Re: "RE:Compositing not enabled in kwin-x11"
| From: josep.feb...@wanadoo.es | Sent: Friday, December 29, 2023 0:58 | To: debian-kde@lists.debian.org ; Libor Klepáč | Subject: "RE:Compositing not enabled in kwin-x11" | | Have you tried to enable or disable compositing with the shortcut ALT Shift F12? | If it don't work at first try, try again. It used to work for me. Hi, i forgot about this shortcut, but it does nothing. Isn't my compositor setting somehow empty? There used to be some more options (see screenshot). I also noticed, that gtk apps (which i usually don't use) have big black border around them, which also seems to be related to composition not working | | Best regards, | Josep With regards, Libor
Re: "RE:Compositing not enabled in kwin-x11"
Hi, > From: Soren Stoutner > Sent: Friday, December 29, 2023 23:21 > To: debian-kde@lists.debian.org > Cc: Libor Klepáč > Subject: Re: "RE:Compositing not enabled in kwin-x11" > > Looking at it a little closer, what you probably need is contained in > `firmware-misc-nonfree`, which is pulled in by `firmware-linux`. I have this one installed. > > On Friday, December 29, 2023 3:18:31 PM MST Soren Stoutner wrote: > > I don’t have any more options than you show in your screenshot, but > > compositing works for me. > > > > Out of curiosity, do you have the `firmware-linux` package installed? On my > > AMD hardware I need to have the non-free `firmware-amd-graphics` installed. > > There isn’t a corollary package for Intel, but installing the non-free > `intel- > > microcode` might make a difference. intel-microcode is for cpu Problem is in my account settings somewhere. With fresh account, composition works. I don't know, how to debug what causes the problem. I don't want to get rid of my home directory, i have it for 15 or so years. Libor
Re: Compositing not enabled in kwin-x11
Hi, when i start kwin from CLI, i get this line in output kwin_scene_opengl: Creating the OpenGL rendering failed: "Invalid QOpenGLContext::globalShareContext()" I think, i have solved it. kwinrc under new user contained [Compositing] OpenGLIsUnsafe=false kwinrc under my user contained [Compositing] Backend=OpenGL GLColorCorrection=false GLCore=true GLPlatformInterface=egl GLPreferBufferSwap=a GLTextureFilter=0 HiddenPreviews=5 LatencyPolicy=Low OpenGLIsUnsafe=false UnredirectFullscreen=false XRenderSmoothScale=false I have deleted everything except the one option and compositing seems to work now Libor ____ From: Libor Klepáč Sent: Thursday, December 28, 2023 10:17 To: debian-kde@lists.debian.org Subject: Compositing not enabled in kwin-x11 Hello, i have just noticed, that i don't have composition enabled in my kwin x11 session. I don't remember, when this happened. I have new laptop for several months and i don't remember if composition worked on my old laptop. Both are with some intel intergrated gpu (sorry, don't know how to get details, my lspci says "Intel Corporation Raptor Lake-P [Iris Xe Graphics] (rev 04) "). Old laptop was running Debian/Sid, new laptop is Debian/Trixie . I have copied my home directory from old laptop to new. In kwinrc, i have this [Compositing] Backend=OpenGL GLColorCorrection=false GLCore=true GLPlatformInterface=egl GLPreferBufferSwap=a GLTextureFilter=0 HiddenPreviews=5 LatencyPolicy=Low OpenGLIsUnsafe=false UnredirectFullscreen=false WindowsBlockCompositing=false XRenderSmoothScale=false and qdbus org.kde.KWin /KWin supportInformation says KWin Support Information: The following information should be used when requesting support on e.g. https://forum.kde.org. It provides information about the currently running instance, which options are used, what OpenGL driver and which effects are running. Please post the information provided underneath this introductory text to a paste bin service like https://paste.kde.org instead of pasting into support threads. == Version === KWin version: 5.27.9 Qt Version: 5.15.10 Qt compile version: 5.15.10 XCB compile version: 1.15 Operation Mode: X11 only Build Options = KWIN_BUILD_DECORATIONS: yes KWIN_BUILD_TABBOX: yes KWIN_BUILD_ACTIVITIES: yes HAVE_X11_XCB: yes HAVE_EPOXY_GLX: yes X11 === Vendor: The X.Org Foundation Vendor Release: 12101009 Protocol Version/Revision: 11/0 SHAPE: yes; Version: 0x11 RANDR: yes; Version: 0x14 DAMAGE: yes; Version: 0x11 Composite: yes; Version: 0x4 RENDER: yes; Version: 0xb XFIXES: yes; Version: 0x50 SYNC: yes; Version: 0x31 GLX: yes; Version: 0x0 Decoration == Plugin: org.kde.kwin.aurorae Theme: __aurorae__svg__Materia-Dark Plugin recommends border size: No onAllDesktopsAvailable: true alphaChannelSupported: false closeOnDoubleClickOnMenu: false decorationButtonsLeft: 0, 2 decorationButtonsRight: 6, 3, 4, 5 borderSize: 2 gridUnit: 10 font: Linux Biolinum O,10,-1,5,50,0,0,0,0,0,Regular smallSpacing: 2 largeSpacing: 10 Output backend == Name: KWin::X11StandaloneBackend Cursor == themeName: Alkano-Aluminium themeSize: 24 Options === focusPolicy: 1 xwaylandCrashPolicy: xwaylandMaxCrashCount: 3 nextFocusPrefersMouse: false clickRaise: true autoRaise: false autoRaiseInterval: 750 delayFocusInterval: 300 shadeHover: false shadeHoverInterval: 250 separateScreenFocus: false activeMouseScreen: true placement: activationDesktopPolicy: 0 focusPolicyIsReasonable: true borderSnapZone: 10 windowSnapZone: 10 centerSnapZone: 0 snapOnlyWhenOverlapping: false rollOverDesktops: false focusStealingPreventionLevel: 1 operationTitlebarDblClick: 5009 operationMaxButtonLeftClick: 5000 operationMaxButtonMiddleClick: 5015 operationMaxButtonRightClick: 5014 commandActiveTitlebar1: 0 commandActiveTitlebar2: 28 commandActiveTitlebar3: 2 commandInactiveTitlebar1: 4 commandInactiveTitlebar2: 28 commandInactiveTitlebar3: 2 commandWindow1: 7 commandWindow2: 8 commandWindow3: 8 commandWindowWheel: 28 commandAll1: 10 commandAll2: 3 commandAll3: 14 keyCmdAllModKey: 16777250 condensedTitle: false electricBorderMaximize: true electricBorderTiling: true electricBorderCornerRatio: 0.25 borderlessMaximizedWindows: false killPingTimeout: 5000 hideUtilityWindowsForInactive: true compositingMode: 1 useCompositing: true hiddenPreviews: 1 glSmoothScale: 0 glStrictBinding: true glStrictBindingFollowsDriver: true glPreferBufferSwap: 97 glPlatformInterface: 2 windowsBlockCompositing: false latencyPolicy: renderTimeEstimator: allowTearing: true Screen Edges desktopSwitching: false desktopSwitchingMovingClients: false cursorPushBackDistance: 1x1 timeThreshold: 150 reActivateThreshold: 350 actionTopLeft: 0 actionTop: 0 actionTopRight: 0 actionRight: 0 actionBottomRight: 0 actionBottom: 0 actionBottomLeft: 0 actionLeft: 0 Screens === Active screen follows mo