Re: lokalize 24.08.01?
Le 22 septembre 2024 19:59:41 GMT+02:00, Martin Steigerwald a écrit : >Luc Castermans - 22.09.24, 19:55:49 CEST: >> > I just uploaded it to unstable. I’ve split the documentation and data >> > files into their own packages so it will have to go through NEW for >> > review by the FTP masters and it should take some days. >> Thanks, merci > >Already accepted by ftpmasters. > >That was fast. Cool 🙂
Re: lokalize 24.08.01?
Le dimanche 22 septembre 2024, 09:22:36 CEST Luc Castermans a écrit : > Dear Dear Luc, > As manpage translator I use Lokalize. Cool, any chance you can convince upstream to ship manpages for more binaries ? :) We still have a whole lot of missing manpage lintian warnings for the KDE stack. > https://tracker.debian.org/pkg/lokalize > > Latter is in version 22.12.3 while upstream 24.08.01 is available. > > Can i do something my self to get it upraded? I just uploaded it to unstable. I’ve split the documentation and data files into their own packages so it will have to go through NEW for review by the FTP masters and it should take some days. In the meantime you can rebuild it locally by cloning the salsa repo if you have a build setup at hand. Or I've uploaded the amd64 packages there for convenience : https://people.debian.org/~coucouf/lokalize-24.08.1/ (Of course you should never install packages recommended by random people from the Internet if you want to keep your systems safe.) Happy hacking, -- Aurélien signature.asc Description: This is a digitally signed message part.
Re: Black folder icons in Dolphin
Le jeudi 19 septembre 2024, 00:20:39 CEST Luigi Toscano a écrit : > Rik Mills ha scritto: > > The reason is that the kf6-breeze-icon-theme which replaced the kf5 version > > has some changes which are not supported by the Qt5/KF5 kiconthemes library. > > You are also likely to see black folder icons in the file picker of any > > Qt5/KF5 app when you enlarge the icon view enough to see coloured folders. > > > > Some solutions might be: > > - downgrade to the KF5 breeze icon theme package and put that on hold with > > apt > > until Qt6/KF6 apps are ready. > > - as some have done, copy locally the old icon theme so that takes > > precedence. > > - persuade devs to revert the offending upstream change in the debian > > packaging, again until no longer required. > > > > Was this reported upstream? The icons are still supposed to work with KF5, so > this should probably be fixed upstream. > Even a comment in the offending commit > https://invent.kde.org/frameworks/breeze-icons/-/commit/931fc4520ceb9ef44f367979d233f2b5bdd4bbb7 > may help. Yes, done : https://invent.kde.org/frameworks/breeze-icons/-/commit/931fc4520ceb9ef44f367979d233f2b5bdd4bbb7#note_1037514
Re: Black folder icons in Dolphin
Le jeudi 19 septembre 2024, 00:03:54 CEST Rik Mills a écrit : > Yes it does work. > > See:https://git.launchpad.net/~kubuntu-packagers/kubuntu-packaging/+git/kf6-breeze-icons/commit/?h=kubuntu_oracular_staging&id=1520c1891847fbef4221793df607c5ff5b69934a > > This was confirmed by me in testing the modified package and by 2 of > more regular testers for Kubuntu. Indeed it does work, thanks. I included the revert as part of the KF 6.6 upload I just did. Happy hacking, -- Aurélien
Re: Black folder icons in Dolphin
Dear Rik, Le mercredi 18 septembre 2024, 20:15:54 CEST Rik Mills a écrit : […] > Some solutions might be: […] > - persuade devs to revert the offending upstream change in the debian > packaging, again until no longer required. Does that really work ? I was sure I had tried what you described in #1079542 and that it didn’t solve the issue. If it’s really supposed to work I can give it another try. Thanks ! -- Aurélien
Re: Other issues
Dear Shmerl, Le lundi 12 août 2024, 08:44:17 CEST Shmerl a écrit : > A few other issues I encountered: > > * Any time I need to reboot, it's delayed by systemd for 90 seconds while > it's waiting for some session to complete? > In the past I enabled systemd startup for KDE, not sure if it's related. > (I used this to enable it > https://blog.davidedmundson.co.uk/blog/plasma-and-the-systemd-startup/) > > * user level ssh-agent.service isn't kicking in, so I have to every time > start it manually with systemctl --user start to be able to use ssh-add. These 2 issues are fixed in plasma-workspace 4:6.1.4-5 that I just uploaded to experimental. We were missing a build-dependency on systemd and it looks like part of the session processes were started with systemd and others not which caused various issues. > * Firefox causes plasma-browser-integration to crash on startup, but > restarting it from the crash notification fixes it. > > * wl-copy completely doesn't work with Plasma 6. May be it's by design? I don’t know about these. Happy hacking, -- Aurélien
Re: KDE audio long broken.
Le vendredi 6 septembre 2024, 17:40:14 CEST Andy Wood a écrit : > On Friday, 6 September 2024 15:54:15 BST Andrey Rakhmatullin wrote: > > On Thu, Sep 05, 2024 at 10:45:16AM +0100, Andy Wood wrote: > > > Hi, > > > > > > Can anybody point me towards a solution to this long standing Debian KDE > > > problem, which started around the time of the t64 transition upheaval. > > > Up-to-date Debian testing system. > > > Audio works with the VLC media player (via Pipewire to ALSA). > > > The Audio Volume Plasma Widget says "No output or input devices found". > > > > I expect the outcome to be the same, but still. Can you install > > pavucontrol and see what it shows? > > pavucontrol says it cannot connect to pulseaudio. I am guessing this is > because wireplumber > pipewire is now in control; pulseaudio has been removed > and replaced with pipewire-pulse? Yes but that shouldn’t prevent pulseaudio-anything to work. Pipewire implements the pulseaudio interface natively. What does pactl info give you ? For instance I have : Server Name: PulseAudio (on PipeWire 1.2.3) -- Aurélien
Re: Some feedback on KDE6 install
Hi Éric, Le 19 août 2024 10:00:44 GMT+02:00, Eric Valette a écrit : >Hi, > >First a big thank to everyone involved. It was nearly smooth. Thanks. […] >I still have some minor annoyance (my taste): > > 1) The list of recent element is empty and generates errors on sqlite, I've not paid attention to that. If you (or others) want to diagnose this a bit further and try to find if it's an upstream or packaging problem that would be welcome. I've had other feedbacks that baloo was not started or not correctly running, maybe that's why ? […] > 3) The battery icon is not always displayed. I have to enter >the "hidden icons" menu to see it. Found no way to make it stick on menu bar. >SOme other icons that I had are still there. Dunno why specifically this one >disapperared. This looks like [1], fixed in Plasma 6.2. [1] https://bugs.kde.org/show_bug.cgi?id=486781 Happy hacking, -- Aurélien
Re: Smaller Plasma bugs in unstable
Le lundi 19 août 2024, 12:15:19 CEST Diederik de Haas a écrit : > On Mon Aug 19, 2024 at 11:54 AM CEST, Diederik de Haas wrote: > > Why report this to the KDE mailing list? > > > > Because yesterday I had what looks like a *partial* upgrade of KDE packages, > > and saw some 'funny' things* (which is ofc expected in Sid from time to > > time). > > ... > > > > *) I'm guessing that's what Aurélien's message is about ... > > Note that I do NOT have any KDE (related) packages installed from > Experimental, which (IIUC) is what Aurélien's message is about. Yes. And unstable should be again fully installable, and supporting both kf5 applications like Gear that we currently ship, and kf6 applications like Digikam. > My Dolphin icon is still black (instead of blue), but the (other) > 'funny' things I did see are now fixed. > So AFAICT the (whole) bunch of libkf6* packages that (also) got > installed with today's Sid upgrade appear to be fine. Yes, I saw that. Dolphin icon in Plasma and folder icons inside Gwenview (and probably other places) are black. Curriously enough, folder icons *inside* dolphin itself and in file browsing popups are fine. That’s the only issue I could find now that we’re running a dual kf5+kf6 stack and I don’t consider it a blocker. I’m betting on a small breakage of backwards compatibility in breeze-icons (which is supposed to be backwards compatible), or maybe just in our packaging ? If someone can analyse and find a fix I’m willing to upload it. But I won’t look into it myself, it’s both transitional and cosmetic issue and there are more important things to do. It’s fixed in Plasma 6 which is not 100% ready for unstable prime time yet. Happy hacking, -- Aurélien
Warning to Plasma 6 / experimental users
TDLR : *DON’T* upgrade to : - libkf5globalaccel* version 5.115.0-6 - libkf5plasma* and plasma-framework version 5.115.0-5 it will break. *WAIT FOR* : - libkf5globalaccel* version 5.115.0-7~exp1 - libkf5plasma* and plasma-framework version 5.115.0-6~exp1 Longer explanation: I uploaded a set of changes to some kf5 packages today to ensure coinstallability with their qt6 counterparts. That was needed because we start having packages relying on kf6 like Digikam and we want them to be installable without requiring experimental. The issue that I overlooked is that there were actually 2 sets of kf5 packages that need updates for coinstallability : - ones that stayed in kf6 for their Qt6 version => these were OK to upload - ones that moved to *Plasma* for the Qt6 version, which is the case for kglobalaccel and plasma-framework (now called libplasma) => these were *NOT OK* to upload now because Plasma 6 is not in unstable yet. So I have reverted the changes to kglobalaccel in version 5.115.0-6 and plasma-framework 5.115.0-5 in unstable to keep all packages installable in unstable. The unpleasant side effect is that if you install these versions in parallel to their Plasma 6 counterparts, it will break. So please ensure you upgrade directly to libkf5globalaccel* version 5.115.0-7exp1 and libkf5plasma* and plasma-framework version 5.115.0-6~exp1 if you don’t want dpkg to break on file conflicts. That’s why they call it experimental after all… Happy hacking, -- Aurélien
Re: Situation KDE Apps 24.0x
Hi, Le mercredi 14 août 2024, 12:38:02 CEST Sedat Dilek a écrit : > Hi Aurelien and Patrick, > > so people are very excited about having KDE Plasma version 6.1.3 and > reporting problems. > > I just wanted to ask what are the plans for KDE Apps (Gears) upgrade > to version 24.05.2 or newer? We still don’t give ETAs however many times you ask. :) The priority is to get kf6 into trixie which shouldn’t be far away, then Plasma 6 and probably Qt6.7 before Plasma. > Here I have a mixture: > > root@iniza:~/packages/KDE# LC_ALL=C wc -l KG-24-05-2.20240814 > KG-23-0x-x.20240814 KG-22-12-3.20240814 > 28 KG-24-05-2.20240814 > 17 KG-23-0x-x.20240814 > 134 KG-22-12-3.20240814 > 179 total Yes and that’s fine. KDE apps are release together but they are completely independent from each other (with some exceptions). We’ve already released Debian with mixed versions several times. Also some apps get released because they are part of the KDE Gear set, but don’t have a single line of code changed between versions. So having all KDE apps to the exact latest upstream version is more OCD than something we’re aiming for. […] > For kmail2 I guess it will be required to be adapted to new versions > of kdepim and akonadi stuff. > kmail can send emails - that's my use-case. The PIM stack is big and has a lot of inter-dependencies, plus some things to take care of for libraries ABI compatibility where upstream is not 100% clean so it’s a big piece. Also many of its packages will need to go through NEW because the libraries had a soname bump. > Maybe you can tell what problems you faced? There are many reasons and we don’t keep a formal list. If you (or anyone else !) is interested in helping, please go through some Debian packaging introduction, setup an environment where you can build packages, and join us on #debian-qt-kde on OFCT. We’re usually friendly and KDE Gear is a good starting point because they are leaf packages without inter-dependencies. > I know you are mostly two maintainers doing the hard work. Scarlett and Jesse have done most of the work for 24.05 apps so far, so let’s thank them ! Happy hacking, -- Aurélien
Re: Successful upgrade to Plasma 6.1.3
Le mardi 13 août 2024, 09:33:38 CEST Luc Castermans a écrit : > Dear > > Previously most Plasma packages were installed from Experimental. This > morning "apt upgrade" showed 247 packages to be upgraded. Now most > were Plasma, but now from Sid! > > Thanks for this enormous step and result!! [ Due to NVDIA I > need to stick to X11] Sorry but no. :) This is « just » KDE Frameworks 6 that I uploaded to unstable. Plasma is still in the works and not there yet. But that was a lot of work from Patrick and myself already, yes. Happy hacking, -- Aurélien
Re: Successful upgrade to Plasma 6.1.3
Le 12 août 2024 06:22:50 GMT+02:00, Shmerl a écrit : >Thanks for the fixes, I was able to install plasma 6.1.3 in testing >by enabling unstable and experimental temporarily and doing > >sudo apt install -t experimental plasma-desktop konsole dolphin sddm > >So far so good. Great. >Note that without updating sddm, I was greeted with black screen after boot >due to missing qt 6 based greeter, >so I had to dig into sddm logs to narrow it down. Anyone doing the above, >don't miss it. I yes I've had that too. I was wondering if/how to set versioned dependencies to ensure it doesn't happen but didn't come up with a good idea. Will try again. Hally hacking, -- Aurélien
Re: KDE/Frameworks/Plasma/Apps QT from experimental
Le dimanche 11 août 2024, 07:27:14 CEST Shmerl a écrit : > Looks like these couple of bugs handle breakage in plasma-desktoptheme > and kwin-data: > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1078140 > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1078436 Exact. I’ve just uploaded the fix for both (libplasma 6.1.3-4, kwin 4:6.1.3-4) so once they’re built on experimental you may want to give the plasma 6 install another try… Happy hacking, -- Aurélien
Re: Re: Re: Re: Re: KDE/Frameworks/Plasma/Apps QT from experimental
Le 6 août 2024 09:32:55 GMT+02:00, Shmerl a écrit : >On Tue, 06 Aug 2024 08:46:11 +0200 Aurélien COUDERC >wrote: > >*> If you could also share your dpkg logs we should be able to see what >happened.* > >I managed to track down some terminal output from dpkg that was stored >in /var/log/apt/term.log > >These errors happened: > >Unpacking kwin-data (4:6.1.3-3) over (4:5.27.11-2) ... >dpkg: error processing archive >/tmp/apt-dpkg-install-0sB9EX/53-kwin-data_4%3a6.1.3-3_all.deb >(--unpack): > trying to overwrite >'/usr/share/kwin/tabbox/thumbnail_grid/contents/ui/main.qml', which is >also in package kwin-addons:amd64 4:5.27.11-1 > > Unpacking plasma-desktoptheme (6.1.3-3) ... >dpkg: error processing archive >/tmp/apt-dpkg-install-0sB9EX/61-plasma-desktoptheme_6.1.3-3_amd64.deb >(--unpack): > trying to overwrite >'/usr/share/plasma/desktoptheme/breeze-dark/colors', which is also in >package plasma-framework 5.115.0-2 OK great that's the issue. If you feel like opening a bug against kwin with severity:serious you may do so. Otherwise I'll do it later. This needs to be fixed in the next upload. Cheers, -- Aurélien
Re: Re: Re: Re: KDE/Frameworks/Plasma/Apps QT from experimental
Le 6 août 2024 03:02:46 GMT+02:00, Shmerl a écrit : >On Mon, 05 Aug 2024 22:03:15 +0200 Aurélien COUDERC wrote: > >> If you don't mind sharing the summary of the apt command (it will show some >> of the packages you've chosen to install), alongside the output of apt >> policy I'd >> still be interested to check that nothing looks amiss. > >I didn't save that run unfortunately, but here is what I managed to >pull from apt log: >https://pastebin.com/raw/44XrZA2m > >apt policy in that scenario looks like this: >https://pastebin.com/raw/JUa0LYCc > >If you really need it, I can try re-running the experiment, but >breakage was a bit tangled No need thanks. It's already useful. The first install section says it's a dpkg error and not a dependency issue, which should never happen if we made our packages correctly. 🙂 If you could also share your dpkg logs we should be able to see what happened. The most common issue is a missing Breaks/Replaces relation between new and old packages, which is required for upgrades to go well when a file moves from one package to another. Thanks ! -- Aurélien
Re: Re: Re: KDE/Frameworks/Plasma/Apps QT from experimental
Le 5 août 2024 08:19:45 GMT+02:00, Shmerl a écrit : >Luc Castermans wrote on Mon, 05 Aug 2024 >05:24:37 + > >*> I am happy to confirm above, using Plasma 6 since few weeks, with most >packages from Experimental.* > >*>* >*> Luc* > >I tried doing > >sudo apt install -t experimental plasma-desktop > >from testing (with unstable and experimental enabled) but that resulted in >some breakage / conflicts that >looked too tangled to resolve, so I reverted that for now. If you don't mind sharing the summary of the apt command (it will show some of the packages you've chosen to install), alongside the output of apt policy I'd still be interested to check that nothing looks amiss. Thanks ! -- Aurélien
Re: Re: KDE/Frameworks/Plasma/Apps QT from experimental
Le 4 août 2024 19:28:04 GMT+02:00, Shmerl a écrit : >Sat, 03 Aug 2024 20:31:37 +0200Aurélien COUDERC wrote: > > >*>> we've both had the issue Patrick and I while having every single >KF6 and Plasma 6 packages installed.* > >So is it close to being pushed to unstable We don't give ETAs, the team is a handful of volunteers, some already quite overworked keeping up with this huge stack. I can give you the anticipated order for things to reach unstable which (until it changes) would be : kf6 > qt6.7 > plasma 6. > or there are still a bunch >of issues left to iron out? Besides the cosmetic wallpaper preview issue, I don't think we've seen anything really scary so far. Happy hacking, -- Aurélien
Re: KDE/Frameworks/Plasma/Apps + QT from experimental
Hi Nicholas, Le 4 août 2024 01:12:19 GMT+02:00, Nicholas D Steeves a écrit : >Hi Aurélien, > > >What I understood was that whoever updated the source package believed >that our new bin:plasma-integration logically provided >plasma5-integration (whether or not it had formal Provides). I found >this reasonable and didn't question it. Yes but no. The new binary is plasma5-integration. It was just an oversight. > >Of course :) So in this case I wonder if it would save time to somehow >search for all versioned-2-unversioned bin:packages, and then add >Recommends for the old Qt5/KF5/Plasma5 variant, See above we're not in that case here. I'm not convinced we would save time with such a thing but if you want to explore that and share feedback, feel free. > run autopkgtests That would be very useful if it did anything. But it requires someone (upstream, us) to write some tests that can run under autopkgtest. autopkgtest [1] runs against the installed system, not from the build tree so you need something that tests the result of apt install $package, not of cmake+make. KDE didn't have that, that I now, but they started building some end user tests using Selenium ~recently. If $someone wants to look at KDE packages with selenium tests and can make them run as autokpgtests, I'd be very interested in merging such changes ! [1] https://manpages.debian.org/bookworm/autopkgtest/autopkgtest.1.en.html Happy hacking, -- Aurélien
Re: KDE/Frameworks/Plasma/Apps + QT from experimental
Le 3 août 2024 20:22:50 GMT+02:00, Edward Shornock a écrit : > >Sedat Dilek kirjoitti 22.7.2024 klo 11.49 ap.: >> KDE/apps partly from experimental like konsole - akonadi/kmail etc. >> still works but from unstable. >> >> The upgrade was mostly done manually - some QT packages were required >> from unstable. > >I have done the upgrade to Plasma from experimental and everything appears to >be working quite well, other than System Settings → Wallpaper doesn't show any >images for the various wallpaper choices. I guess I'm probably missing a >package, but which one I haven't figured out yet. Good to hear. I don't think it's a missing package issue, we've both had the issue Patrick and I while having every single KF6 and Plasma 6 packages installed. So either it's some other package missing that's not from the KDE stack, some hidden missing build dependency, some version incompatibility with what we have in Debian, some other bug ? If someone has it working with our packages and/or can figure out what's missing, feedback would be highly appreciated. Happy hacking, -- Aurélien
Re: KDE/Frameworks/Plasma/Apps + QT from experimental
Hi, Le vendredi 2 août 2024, 05:22:39 CEST Nicholas D Steeves a écrit : > Shai Berger writes: > > > On Thu, 01 Aug 2024 17:17:17 +0200 > > Aurélien COUDERC wrote: > > > >> Le 1 août 2024 15:59:44 GMT+02:00, Alex Hermann > >> a écrit : > >> > > >> >Yes, thanks. plasma5-integration was the missing bit. > >> > > >> >Maybe some packages need a depend/recommend on this package. As of > >> >now, it stands completely on its own. > >> > > >> >$ apt-cache rdepends plasma5-integration > >> >plasma5-integration > >> >Reverse Depends: > >> > >> Yes, good idea, will do. > >> > > > > FWIW, in testing there's "plasma-integration" and it has rdepends: > > > > $ aptitude why plasma-integration > > i task-kde-desktop Depends kde-standard > > i A kde-standard Depends kde-plasma-desktop (>= 5:148) > > i A kde-plasma-desktop Depends plasma-desktop (>= 4:5.27.11) > > i A plasma-desktop Depends plasma-integration (>= 5.27.11~) > > Package: plasma-desktop > Version: 4:6.1.3-1 [experimental] > [snip] > Depends: [snip] plasma-integration (>= 6.1.0~) … which is fine, this package is the integration for Qt6 apps. plasma5-integration is required for Qt5 apps in addition. > The other end up transitively depending on it because of this. I'm > guessing that the nature of this issue is that one should never > 'dist-upgrade'/'full-upgrade' when mixing experimental; however, in this > case I'm guessing that this was needed in order to install a new > package. > > Aurélien, do you think upgrades could be smoother for users if > plasma-integration (and/or any other packages) had stronger breaks & > replaces, or will everything 'just work'? I don’t get what you mean by that. Yes, we must have a working upgrade path and we make what we can to make it happen. When someone finds an issue like here with missing plasma5-integration or previously with qml6-qtmql-workerscript we fix it. We generally install all packages from the stack when packaging to ensure that nothing breaks when upgrading. So we don’t catch the missing package issues immediately. Happy hacking, -- Aurélien
Re: KDE/Frameworks/Plasma/Apps + QT from experimental
Le 1 août 2024 15:59:44 GMT+02:00, Alex Hermann a écrit : >On donderdag 1 augustus 2024 14:51:57 CEST Luigi Toscano wrote: […] >> KFileDialog doesn't exist since Frameworks 5. Maybe you are missing a >> package? >> >> The special feature are provided (if I remember correctly) by some >> integration layer that uses the "hooks" provided by Qt to extend the >> behavior. If you use Plasma, that's done by plasma-integration. > >Yes, thanks. plasma5-integration was the missing bit. > >Maybe some packages need a depend/recommend on this package. As of now, >it stands completely on its own. > >$ apt-cache rdepends plasma5-integration >plasma5-integration >Reverse Depends: Yes, good idea, will do. -- Aurélien
Re: Bug#1076043: task-kde-desktop: synaptic not installed by default with task-kde-desktop
Hi ! Le 10 juillet 2024 11:09:30 GMT+02:00, Omega a écrit : > But for non-technical users whom never heard of it might be useful >of having it installed out of the box. With my KDE / Plasma comaintainer hat on, I tend to disagree with this statement. In my opinion if you're going to (ask someone to) do something with Synaptic that you cannot do with Discover, it's OK to have to install Synaptic in the process… which you can easily do from Discover. So I would mark this as wontfix unless other KDE/Plasma maintainers have a strong opinion in the other direction. Happy hacking, -- Aurélien
Re: Save session is not working after lastest upgrade
Hi, [copying debian-kde user list] Le 8 juin 2024 11:49:13 GMT+02:00, "Martin Šoltis" a écrit : >Hi, > >after latest upgrade, I don't know exactly when, but within the latest week, >my KDE Plasma stopped restoring session after logout. > >I don't know why but the only one item which is restored is Firefox. >Kmail, Konsole, Krusader are not restored. > >Is this some known bug ? Maybe you switched to the Wayland session ? In which case yes this is a known bug, with a first workaround only in the yet-to-be-released Plasma 6.1 version. See [1], [2] and [3] if you're interested in more context. [1] https://bugs.kde.org/show_bug.cgi?id=436318 [2] https://community.kde.org/Plasma/Wayland_Known_Significant_Issues [3] https://kde.org/announcements/plasma/6/6.0.90/ Cheers, -- Aurélien
Re: Qt upgrade
Le 23 mai 2024 10:09:29 GMT+02:00, Andrey Rakhmatullin a écrit : >On Thu, May 23, 2024 at 09:44:10AM +0200, Martin Steigerwald wrote: >> The new apt 2.9 and later makes it really obvious, so maybe warnings like >> this are no longer needed? >It was always obvious *shrug* Must depend on your kind of eyes :-), I do find the new feedback of packages to be removed *much* more obvious. And BTW it's in apt version 2.9.3 onwards if I remember correctly. Older versions didn't have that. Happy hacking, -- Aurélien
Re: Plasma 6 in Debian?
Le 26 avril 2024 10:05:19 GMT+02:00, Martin Steigerwald a écrit : > >Members of the Debian Qt/KDE team are working on packages and uploading to >experimental since quite a while already. Most of them KF6 related. Due to >new names most, if not all, of them need to go through NEW. Those appear >to get accepted by ftpmasters quite smoothly at the moment, but it still >needs additional time. Yes, and we're making good progress on kf6 thanks to the sustained effort of Patrick Franz in particular. 🙂 >Also AFAIR there an updated set of KF5 packages needs to go to unstable >first. I think it was due to some packages need to be provided as 5 and 6 >versions and some missing features in the older KF5 packages currently in >Debian preventing that, but I am not sure I got the exact explanation >right. The exact reason is that the previous kf5 versions were not all co-installable with their kf6 counterparts. We want to have kf5 and kf6 co-installable to avoid breaking everything so we need the lastest version of kf5 to go in first. >To summarize all of this in a short way: From what I have read it is to >early to predict when Plasma 6 will hit Debian unstable. Yes, that's it. It's coming and will be ready when it's ready. 🙂 Happy hacking, -- Aurélien
Re: Help in porting to wayland?
Le 23 mars 2024 12:51:18 GMT+01:00, "Aurélien COUDERC" a écrit : > >Le 23 mars 2024 04:25:07 GMT+01:00, Salvo Tomaselli a >écrit : >>Hello, Hi ! >>I maintain trabucco, which uses XGrabKey() to show up on the screen with a >>shortcut. >> >>Naturally, this doesn't work if a wayland session is in use. >> >>I could not find any guide on what should I replace it with. >> >>Any pointers on where to look to do that? No idea but I'm transferring to the packaging discussion list in case someone has one. Happy hacking ! -- Aurélien
Re: After upgrading to Debian Bookworm, Meta key activates Application Launcher
Dear Andrej, Le samedi 17 juin 2023, 03:45:41 CEST Andrej Kacian a écrit : > Hello, > > after I upgraded my system to Bookworm with newer KDE/Plasma, my Meta > (Windows) key started making the application launcher pop up. I had it > disabled before, although I do not remember how anymore. Now I can't > find a way to make it not do that again. In the settings for the > application launcher, the activation shortcut is unset. > > Any hints, please? Have a look at the official documentation [0]. Basically you can run : kwriteconfig5 --file ~/.config/kwinrc --group ModifierOnlyShortcuts --key Meta "" qdbus org.kde.KWin /KWin reconfigure to revert to the previous behaviour. > It's very annoying. I find it quite handy. :) [0] https://userbase.kde.org/Plasma/Tips#Windows/Meta_Key Happy hacking, -- Aurélien signature.asc Description: This is a digitally signed message part.
Re: Dragging icons at desktop
Hi. Le samedi 24 décembre 2022, 10:33:52 CEST Aurélien COUDERC a écrit : > > Le 24 décembre 2022 09:57:15 GMT+01:00, "luca.pedrielli" a > écrit : > >Il 24/12/22 02:15, Miguel A. Vallejo ha scritto: > >> El lun, 28 nov 2022 a las 23:34, Martin Steigerwald > >> () escribió: > >>> Miguel A. Vallejo - 28.11.22, 23:26:52 CET: > >>>> Recently I noticed when I drag an icon in the desktop (fully updated > >>>> Sid), the icon lags behind the mouse cursor instead of following the > >>>> mouse cursor under it as it always did. > >> After almost a month of usage I can't get used to this "feature", it > >> makes the desktop feel sluggish and unresponsive. > >> > >> But I still haven't found where to disable it, so should I open a > >> bug? Against what package? At Debian or KDE? > >> > >> Thanks in advance. > >> > >I can confirm this issue, but not on all my machines. > >For example in virtualbox with 3D disabled, drag is immediate, it lags when > >3D is enabled. > >So it seems gpu related. > >It's ok with my intel graphic card. > > Yes it would be interesting to get more info about the setups and > combinations where it does lag (X11/Wayland, GPU and graphics driver, desktop > compositing enabled/disabled). > > On my machine it's not noticeable at all and becomes slightly noticeable > inside a KVM VM but the lag in that case is still a small fraction of a > second and not something I would want to open a bug for. For the record this has been fixed in Qt5 version 5.15.8+dfsg-9 that already reached bookworm. Patrick identified the upstream commit and Dmitry backported it to our packages. Happy hacking, -- Aurélien
Re: Question about Plasma 5.27.5 and Frameworks 5.106
Le 20 mai 2023 09:11:56 GMT+02:00, Luc Castermans a écrit : >indeed. The command should have contained 104 instead of 103 Nope, Martin corrected me on that, the expression selects the packages that you *want* to upgrade so 5.103.0 / 5.27.2 are correct. Best, -- Aurélien
Re: Question about Plasma 5.27.5 and Frameworks 5.106
Le 19 mai 2023 15:52:24 GMT+02:00, Martin Steigerwald a écrit : >Hi, > >Aurélien COUDERC - 19.05.23, 14:41:44 CEST: >> Le 19 mai 2023 13:11:01 GMT+02:00, Luc Castermans > a écrit : >> >Dear >> > >> >I just upgraded the machine which was messed up earlier, fixed later, >> >using: >> > >> >aptitude install -t experimental '~i ~V5\.27\.2' >> >aptitude install -t experimental '~i ~V5\.103\.0' >> >> You probably meant 104 for the second command otherwise I don't see >> the point. > >The version you specify is the version you like to upgrade to >experimental. So 103 is about right. > >I will postpone upgrading to 5.104 a bit longer. So far all is fine and >Plasma 5.27.5 works nicely. Indeed, thanks.
Re: Question about Plasma 5.27.5 and Frameworks 5.106
You probably meant 104 for the second command otherwise I don't see the point. Le 19 mai 2023 13:11:01 GMT+02:00, Luc Castermans a écrit : >Dear > >I just upgraded the machine which was messed up earlier, fixed later, using: > >aptitude install -t experimental '~i ~V5\.27\.2' >aptitude install -t experimental '~i ~V5\.103\.0' > >Now it is running > >Operating System: Debian GNU/Linux 12 >KDE Plasma Version: 5.27.5 >KDE Frameworks Version: 5.104.0 >Qt Version: 5.15.8 >Kernel Version: 6.1.0-9-amd64 (64-bit) >Graphics Platform: X11 >Processors: 12 × AMD Ryzen 5 3600 6-Core Processor >Memory: 31.3 GiB of RAM >Graphics Processor: NVIDIA GeForce GT 1030/PCIe/SSE2 >Manufacturer: BIOSTAR Group >Product Name: A320MH > >Thank you very much team!! > >Luc > > >Op 19-05-2023 om 10:09 schreef Aurélien COUDERC: >> >> Le 19 mai 2023 09:00:37 GMT+02:00, Martin Steigerwald >> a écrit : >>> Hi Luc. >>> >>> Luc Castermans - 16.05.23, 07:11:33 CEST: >>>> On top and for the record. >>>> >>>> I installed all of KDE, plasma 5.25.5 etc. from Experimental >>>> yesterday. The upgrade went smooth, all worked well. >>> Installing as well. >>> >>> I don't know whether it helps if some users "vote" for its stability? >>> But I am willing to do so if after a few days of test there is no >>> regression compared to the current state. >> Yes, useful for us there so we get some feedback that we're not talking >> nonsense when saying the new version is an improvement. 🙂 >> >> But please don't contact the release team directly nor comment on the >> unblock bug report about bit, it would only add noise and make our case more >> difficult. >> >> Also if people here could find the time to try and mix some .2 and .5 >> packages and report back, that would be useful to confirm it doesn't break >> more than it fixes. >> In particular mixing core components like kwin, libkscreen, plasmas >> workspace/desktop would be interesting tests. >> >> We may get a signoff for some but not all packages. >> >> >> Thanks all for your tests, feedback and support ! >> >> -- >> Aurélien >> >-- >m.vr.gr. > >Luc Castermans >mailto:luc.casterm...@gmail.com
Re: Question about Plasma 5.27.5 and Frameworks 5.106
Le 19 mai 2023 09:39:52 GMT+02:00, Martin Steigerwald a écrit : >No need to copy me directly. Actually I prefer that you do not. Creates >extra work for me. > >Sedat Dilek - 19.05.23, 09:28:46 CEST: >> Did you install and test KDE/Frameworks version 5.104? > >No. > >I am not aware of any plans to get KDE Frameworks 5.104 or later into >Bookworm. No we have no plans for that. The ratio of important bug fixed vs. total number of packages to upgrade isn't worth it. If you identify specific bugs that affect you we may try and back port individual fixes. Happy hacking, -- Aurélien
Re: Question about Plasma 5.27.5 and Frameworks 5.106
Le 19 mai 2023 09:00:37 GMT+02:00, Martin Steigerwald a écrit : >Hi Luc. > >Luc Castermans - 16.05.23, 07:11:33 CEST: >> On top and for the record. >> >> I installed all of KDE, plasma 5.25.5 etc. from Experimental >> yesterday. The upgrade went smooth, all worked well. > >Installing as well. > >I don't know whether it helps if some users "vote" for its stability? >But I am willing to do so if after a few days of test there is no >regression compared to the current state. Yes, useful for us there so we get some feedback that we're not talking nonsense when saying the new version is an improvement. 🙂 But please don't contact the release team directly nor comment on the unblock bug report about bit, it would only add noise and make our case more difficult. Also if people here could find the time to try and mix some .2 and .5 packages and report back, that would be useful to confirm it doesn't break more than it fixes. In particular mixing core components like kwin, libkscreen, plasmas workspace/desktop would be interesting tests. We may get a signoff for some but not all packages. Thanks all for your tests, feedback and support ! -- Aurélien
Re: Kuser
Le 5 avril 2023 22:01:16 GMT+02:00, Soren Stoutner a écrit : >Sounds like a very Mac philosophy that I thought I got away from with Linux. >;) Yeah agreed, it's not in the spirit of KDE to drop features for the sake of it, and I'd think it was more for a question of resources and/or interest in diving into that topic. Best would be to check upstream bug reports and file one for the functionality that you're missing if it doesn't already exist. Happy hacking, -- Aurélien
Re: Bookworm: Dolphin no longer shows "RMB click > Open with > Other applications" dialog
Le 13 février 2023 23:53:03 GMT+01:00, local10 a écrit : >Feb 13, 2023, 22:12 by hrn...@onlinehome.de: > >> In general, the window is ok. >> But it's already quite big, with large icons and no customization options. >> > > >There are several issues with that window: > >1. Requires extra clicks, counterintuitive. If you open the new "Open with" >window and start typing you won't find the app you're looking for because the >window initially limits the apps only to "standard" apps and you have to click >the "Show other apps" button to see other apps. > >This is really not smart as the reason one would use the "Open with > Other >apps" window is because one's not satisfied with the initially presented apps >and wants to see other apps. This at least will be fixed in 5.27.1 : https://bugs.kde.org/show_bug.cgi?id=464521 Cheers, -- Aurélien
Re: Bookworm: Dolphin no longer shows "RMB click > Open with > Other applications" dialog
Le 13 février 2023 23:06:31 GMT+01:00, Helge Reimer a écrit : >Am Montag, 13. Februar 2023, 22:51:45 CET schrieb Aurélien COUDERC: > >> > Now yes. And that solved it. Thanks. >> > I always wonder how you should know about this. >> > It has always worked and suddenly an additional package is needed. Where >> > is >> > that written? >> >> You shouldn’t, that’s a packing bug. >> It’s fine to raise this kind of issue here, thanks for that ! and I will fix >> it in the next upload. > >Very nice info. Thanks for that. >That means xdg-desktop-portal-kde is not required and we are waiting for the >bug fix? No, it's still required but I will add it to the list of recommended packages so it gets installed automatically on upgrade. -- Aurélien
Re: Bookworm: Dolphin no longer shows "RMB click > Open with > Other applications" dialog
Le lundi 13 février 2023, 18:51:53 CET Helge Reimer a écrit : > Am Montag, 13. Februar 2023, 18:29:39 CET schrieb luca.pedrielli: > > is xdg-desktop-portal-kde installed? > > Now yes. And that solved it. Thanks. > I always wonder how you should know about this. > It has always worked and suddenly an additional package is needed. Where is > that written? You shouldn’t, that’s a packing bug. It’s fine to raise this kind of issue here, thanks for that ! and I will fix it in the next upload. To give some background, when working on KDE packaging we usually update whole package sets in one go. That’s 83 frameworks source packages, ~45 plasma, over 200 Gear, and several times that number in binary packages. When the packages build we then install the whole set to ensure they’re not broken. So on our packaging machines we usually have all the packages installed and don’t notice these kind of issues. Some packages declare these runtime dependencies as such in their cmake makefile but not all of them do, so your testing and feedback is appreciated so we can fix it for everyone else. Le lundi 13 février 2023, 21:17:16 CET Helge Reimer a écrit : > Am Montag, 13. Februar 2023, 20:58:08 CET schrieb local10: > > Not happy about the change though. KDE devs reworked the "Open with" > > dialog > > and not for the better, IMO. Now it has huge icons that occupy several > > pages, no organization, no way to reduce the icon size. The old dialog had > > everything neatly organized, even showed what section the target app > > belonged to (Development, Internet, Multimedia, etc). With the old dialog > > one could find the app even without knowing its exact name, just by > > browsing the related sections. Anyhow, it words. > > Unfortunately I have to agree. > I was almost shocked when I saw the window for the first time. I have to disagree with that. I never liked the old « open with » window which I found hard to navigate. Hard to make everyone happy I guess… Happy hacking ! -- Aurélien
Re: Coloured character borders in kterm
Le samedi 14 janvier 2023, 22:05:44 CET Miguel A. Vallejo a écrit : > Hello! > > After today's apt-upgrade I noticed all letters in kterm have a > coloured border as you can see in the attached image. > > But I also noticed 78 packages have been kept back, so my question is: > > Is this a new problem or only the symptom of an incomplete upgrade? > > Anyone else noticed this? I used to see the issue too, but it disappeared since last time I checked. Maybe the fix for #103 [0] or some other fontconfig update fixed it for me. Do you still see the issue with an up-to-date sid or testing ? [0] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=103 Happy hacking, -- Aurélien
Re: Bookworm upgrade to 5.26.90 resulted in a huge App Launcher icon size
Le 1 février 2023 07:40:47 GMT+01:00, local10 a écrit : >Hi, Hi, >The latest Bookworm upgrade to 5.26.90 [1] resulted in the Application >Launcher widget's icon becoming a huge, ridiculous size[2]. It's now about 10 >times larger than what it used to be before the upgrade and, respectively, >takes 10x times more space on the task bar. Strange, we've not seem that elsewhere (yet ?). Can you confirm that you have no more plasma packages installed with the old version ? (5.26.5) Also if you have time you may search the KDE bugtracker for issues raised against version 5.26.90 and report if you find something similar. Thanks, -- Aurélien
Re: Plasma 5.27 beta (5.26.90) coming to unstable
Le 25 janvier 2023 17:07:14 GMT+01:00, Martin Steigerwald a écrit : >Aurélien COUDERC - 25.01.23, 11:21:01 CET: >> >Could you check with the lxqt that they do the rebuild quickly enough >> >that we don't break more things ? >> Actually don't, there are more packages involved, I'm handling this >> with the release team to fix the situation. >> >> Thank for raising the issue. > >Thanks, Aurélien. > >I am not in a hurry. Basically I just installed lxqt to have some >desktop at hand in case Plasma would not start up for some reason. When is the last time this actually happens ?
Re: Plasma 5.27 beta (5.26.90) coming to unstable
Le 25 janvier 2023 09:27:38 GMT+01:00, "Aurélien COUDERC" a écrit : > > >Le 25 janvier 2023 08:23:53 GMT+01:00, Martin Steigerwald > a écrit : >>Diederik de Haas - 24.01.23, 14:53:29 CET: >>> On Tuesday, 24 January 2023 11:58:25 CET Martin Steigerwald wrote: >>> > Ah, held back due to libkf5screen7 still at 4:5.26.5-1 >>> >>> FWIW: kscreen version 4:5.26.90-1 (now) depends on libkf5screen8 >> >>That is key as I found out this morning before reading your mail :) >> >>lxqt packages were blocking the upgrade to libkf5screen8. >> >>Now explicitly installed libkf5screen8 which triggered the removal of >>some lxqt packages. So it seems there needs to be a binary rebuild of >>some lxqt packages. > >Hmmm, I wasn't aware of that dependency and it's not going to make out life… >That means we should be handling soname bumps for libkscreen as transitions, >which would have meant no Plasma 5.27 for bookworm… >Currently I was considering these as libs for Plasma use only. > >Could you check with the lxqt that they do the rebuild quickly enough that we >don't break more things ? Actually don't, there are more packages involved, I'm handling this with the release team to fix the situation. Thank for raising the issue. -- Aurélien
Re: Plasma 5.27 beta (5.26.90) coming to unstable
Le 25 janvier 2023 08:23:53 GMT+01:00, Martin Steigerwald a écrit : >Diederik de Haas - 24.01.23, 14:53:29 CET: >> On Tuesday, 24 January 2023 11:58:25 CET Martin Steigerwald wrote: >> > Ah, held back due to libkf5screen7 still at 4:5.26.5-1 >> >> FWIW: kscreen version 4:5.26.90-1 (now) depends on libkf5screen8 > >That is key as I found out this morning before reading your mail :) > >lxqt packages were blocking the upgrade to libkf5screen8. > >Now explicitly installed libkf5screen8 which triggered the removal of >some lxqt packages. So it seems there needs to be a binary rebuild of >some lxqt packages. Hmmm, I wasn't aware of that dependency and it's not going to make out life… That means we should be handling soname bumps for libkscreen as transitions, which would have meant no Plasma 5.27 for bookworm… Currently I was considering these as libs for Plasma use only. Could you check with the lxqt that they do the rebuild quickly enough that we don't break more things ? (If not I will, please tell me.) Thanks, -- Aurélien
Plasma 5.27 beta (5.26.90) coming to unstable
Dear all, I've just uploaded Plasma 5.27 beta to *unstable*. We usually keep beta versions in experimental but this one is our target for bookworm and I want to give it maximum exposure with the bookworm freeze starting already. I've been using it for a couple of days without major issue by YMMV of course, it's beta software still. Feel free to not update or hold Plasma packages if you don't want to use the beta. I'll upload the final 5.27.0 as soon as it's released, so on Feb 14. or close to that. If you're interested, have a look at our Bookworm plans at [0] for more context if you haven't already. Also if you have time, now would be a good time testing bullseye -> bookworm upgrades with the Plasma desktop installed and report anything broken (on spare machines / VMs obviously, NOT on systems you need to rely on). [0] https://wiki.debian.org/PkgQtKde/BookwormReleasePlans Happy hacking ! -- Aurélien
Re: Coloured character borders in kterm
Le 16 janvier 2023 01:59:12 GMT+01:00, "Miguel A. Vallejo" a écrit : >Until january 13th it rendered perfect. Crisp and clean but after an apt >upgrade the issue appeared. Would you mind posting the package changes on your system for this date ? Maybe something will give us inspiration. You would find that in the /var/log/apt/history.log file. Thanks, -- Aurélien
Re: Coloured character borders in kterm
Le 16 janvier 2023 01:33:47 GMT+01:00, piorunz a écrit : >On 16/01/2023 00:31, piorunz wrote: > >> Looks like inverted sub-pixel rendering to me. > >Scratch that. Even with inverted RGB, it should NOT have colors.. :| Like you >have. Shades of blue and brown. That's weird one! Indeed, you would see that kind of effects in a photo of the screen, where each pixel is physically rendered by multiple color sub-pixels. But not in a screenshot. -- Aurélien
Re: Dragging icons at desktop
OK indeed I can reproduce in an X11 session with desktop compositing on. It's awful. 🙂 I'll report the bug upstream. Thanks for the additional info and the video. Haply hacking & Christmas, -- Aurélien Le 24 décembre 2022 22:26:16 GMT+01:00, "Miguel A. Vallejo" a écrit : >Yes! This is becoming quite interesting! > >I made a small video showing the issue: > >https://www.dropbox.com/s/rm98raxb4i55v1d/issue.mp4?dl=1 > >Questions: > >> What happens if you try to suspend the compositor (SHIFT+Alt+F12)? > >Problem solved, a white icon background but it moves perfectly! > >> It would also be interesting to test under a Wayland session > >No issues at all under Wayland. Just perfect! > >So I guess I will use Wayland for now... The problem seems to be in >the compositor under X11. > >If you need more info about my setup, just tell me. > >Thank you all! >
Re: Dragging icons at desktop
Le 24 décembre 2022 14:08:27 GMT+01:00, "luca.pedrielli" a écrit : >Il 24/12/22 12:30, Miguel A. Vallejo ha scritto: >> Interesting... >> >> My system is running X on a Intel 530 HD Graphics card. >> >> When I drag an icon, and move the mouse pointer slowly, the icon >> follow the mouse pointer a few centimeters behind moving somewhat >> irregularly >> >> If I move the mouse at "medium" speed, the icon can be 15 or 20 >> centimeters behind the mouse cursor. >> >> If I move the mouse cursor fast, the icon does not move at all until I >> drop the icon, then it moves slowly from the old to the new position. >> >> Otherwise, moving windows is as fast as usual, they move in real time >> under the mouse pointer without any problem. >> >> It happens with any icon, even with icons inside Dolphin or Ark. >> >> I must admit I thought it was a new desktop effect. >> >> I also noticed plasmashell CPU usage is quite high (around 60 - 65 % >> CPU usage) while dragging icons. Xorg is also high CPU usage (35 - >> 40%) while dragging icons. In fact both plasmashell and Xorg CPU >> usages added are always very close to 100%. They do not use as much >> CPU moving windows (well under 10%). >> >> I didn't see any suspicious problems both in syslog or .xsession-errors >> >> Any ideas to find where the problem is? >> >> Thanks in advance >> >What happens if you try to suspend the compositor (SHIFT+Alt+F12)? Yes that would be useful. It would also be interesting to test under a Wayland session (you need to install plasma-workspace-wayland and select the Wayland session before logging in). Also trying for a newly created user could give us some info on whether the issue can be caused by some customisations you made to your environment. Thanks, -- Aurélien
Re: Dragging icons at desktop
Le 24 décembre 2022 09:57:15 GMT+01:00, "luca.pedrielli" a écrit : >Il 24/12/22 02:15, Miguel A. Vallejo ha scritto: >> El lun, 28 nov 2022 a las 23:34, Martin Steigerwald >> () escribió: >>> Miguel A. Vallejo - 28.11.22, 23:26:52 CET: Recently I noticed when I drag an icon in the desktop (fully updated Sid), the icon lags behind the mouse cursor instead of following the mouse cursor under it as it always did. >> After almost a month of usage I can't get used to this "feature", it >> makes the desktop feel sluggish and unresponsive. >> >> But I still haven't found where to disable it, so should I open a >> bug? Against what package? At Debian or KDE? >> >> Thanks in advance. >> >I can confirm this issue, but not on all my machines. >For example in virtualbox with 3D disabled, drag is immediate, it lags when 3D >is enabled. >So it seems gpu related. >It's ok with my intel graphic card. Yes it would be interesting to get more info about the setups and combinations where it does lag (X11/Wayland, GPU and graphics driver, desktop compositing enabled/disabled). On my machine it's not noticeable at all and becomes slightly noticeable inside a KVM VM but the lag in that case is still a small fraction of a second and not something I would want to open a bug for. Thanks, -- Aurélien
Re: Careful with dist-upgrade in unstable at the moment
Hi all, Le mercredi 21 décembre 2022, 21:37:45 CET Marc Haber a écrit : > On Wed, Dec 21, 2022 at 12:50:45PM +0100, Martin Steigerwald wrote: > > Marc Haber - 21.12.22, 12:00:39 CET: > > > > Stop using *dist-*upgrade by DEFAULT. > > > > > > *AMEN* to that. > > > > I usually do "dist-upgrade", but then look carefully what it is about to > > do. If I don't like that, I only to "upgrade". > > > > Of course one can argue it is safer to do it the other way around. > > P.S. dist-upgrade is as deprecated as it could be, it's not even in the > man page any more That can be correct or incorrect depending on which manpage you’re looking at. :) dist-upgrade is an argument for apt-get while full-upgrade is for apt. I’d like to recommend using « apt upgrade » which has a slightly different behaviour than apt-get : it will upgrade already installed packages but also install new packages where necessary (which apt-get upgrade won’t do). This will leave full-upgrade with less things to do and for me to review. The only remaining packages should have a note in their changelog about doing a split, replacing another package or adding a Breaks/Replace condition. I regularly check this when I see non obvious removals (and by obvious I really only mean libfooN+1 replacing libfooN). Happy hacking, -- Aurélien
Copy bug in Dolphin 22.12.0
Dear all, there’s an embarassing bug in Dolphin 22.12.0 that was raised following my upload to unstable. [0] [1] So if you’re running unstable and this is an issue for you, you may want to hold the previous version for now. I’m upgrading the Debian bug severity so this version doesn’t migrate to testing. [0] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025943 [1] https://bugs.kde.org/show_bug.cgi?id=462928 Happy hacking, -- Aurélien
Re: Unable to access SMB shares when credential are needed - kio-extras
Le 11 décembre 2022 10:07:54 GMT+01:00, "luca.pedrielli" a écrit : >kio-extras 4:22.12.0-2 solves. >Thanks. Good to know ! Thanks for the feedback. -- Aurélien
Re: Thank for your the ambitious plan for Bookworm
Le 23 novembre 2022 16:23:56 GMT+01:00, Diederik de Haas a écrit : >On Saturday, 12 November 2022 11:50:53 CET Martin Steigerwald wrote: >> Dear Debian/Kubuntu Qt/KDE team developers, >> >> thank you dearly for the ambitious plan you set out in: >> https://wiki.debian.org/PkgQtKde/BookwormReleasePlans > >That indeed looks quite good :-) >Please do inform the Release Team about it (even if it's not 100% final). Ah yes, I still havn't do that. What's best ? Filing a pre-approval bug ? >> In case you'd like some of us to test something from experimental at >> some time, just let us know. > >Indeed. Happy to help here! Thanks. - The thing that's the most lagging behind is Gear. The Gear packages are mostly independent from one another so help on any of them is welcome. - Also we have *loads* of bug reports, I pick some with every upload but I cannot scale to the number we have across Frameworks, Plasma and Gear. Help welcome on triaging, retesting, linking with upstream bugs (or filing them when reproducible and not yet in bugs.kde.org). - Give a try to the testing ISO, choose Plasma, report any bugs or ideas for improvements. - Create a Plasma Debiab theme à la kubuntu-settings to we can get back the Debian wallpaper by default. The old way to script that in desktop-base is too fragile and broken. - Review upstream packaging recommendations [0] and propose patches for achievable item, fix anything non directly KDE-related mentioned there in Debian. Best if you ping us on #debian-qt-kde when you work on any of this. [0] https://community.kde.org/Distributions/Packaging_Recommendations Hally hacking ! 🙂 -- Aurélien
Re: Plasma 5.26 coming to unstable - Thank you!
Dear all, Le 14 octobre 2022 23:10:40 GMT+02:00, Diederik de Haas a écrit : >On vrijdag 14 oktober 2022 20:36:44 CEST Aurélien COUDERC wrote: >> In any case I've uploaded plasma-workspace 4:5.26.0-2 with the fix and I've >> synchronised the theme conf file with the upstream one as you suggest. Thanks for your various feedback and bug reports that help make the KDE packages better. Now that the login screen bug seems to be fixed for everyone, I'd like to strongly recommend everyone who switched to the breeze SDDM theme due to the bug to switch back to debian-breeze. Debian-breeze is the default that our users will see and we need to get it as much exposure as possible before it reaches testing. Thank you again for your help in testing Plasma and your patience. Happy hacking, -- Aurélien
Re: Plasma 5.26 and multi-display support: Regression found
Le 15 octobre 2022 12:20:25 GMT+02:00, "Aurélien COUDERC" a écrit : >Dear Volker, > >Le samedi 15 octobre 2022, 10:47:53 CEST Christian Volker a écrit : >> Oh, i missed to say that I am still using X and not Wayland. > >[…] > >> After upgrading to 5.26 a view days ago, I noticed that my external monitors >> no longer show any content - they only show a black screen. Looks a lot like this bug : https://bugs.kde.org/show_bug.cgi?id=460341 Fixed in 5.26.1. If you shout loud enough I can backport it but I would as well wait for the 5.26.1 release if you can live with the bug. Cheers, -- Aurélien
Re: Plasma 5.26 and multi-display support: Regression found
Dear Volker, Le samedi 15 octobre 2022, 10:47:53 CEST Christian Volker a écrit : > Oh, i missed to say that I am still using X and not Wayland. […] > After upgrading to 5.26 a view days ago, I noticed that my external monitors > no longer show any content - they only show a black screen. I cannot reproduce this on a purely Intel laptop, neither with X11 nor Wayland. There are a lot of moving parts like you said including the KDE stack, Qt and also the graphics drivers. Out of curiosity did you try Wayland and it had some shortcomings for your use case or is it just that you stayed on X11 because it was always your setup ? At this point I’d recommend giving it a try, it’s becoming more and more stable and has features like per-screen UI zoom factor that I don’t think Plasma can do with X11. Can you also check journalctl if you can find anything funny or any kind of errors ? In any case (wayland working or not) I’d recommend raising the bug upstream as we’re with the latest versions of everything here. Happy hacking, -- Aurélien
Re: Plasma 5.26 coming to unstable - Thank you!
Le 14 octobre 2022 18:53:41 GMT+02:00, Diederik de Haas a écrit : >On Friday, 14 October 2022 14:49:01 CEST Aurélien COUDERC wrote: >> Alternatively you can add the following line : >> background=/usr/share/desktop-base/active-theme/login/background.svg >> >> at the end of this file : >> /usr/share/sddm/themes/debian-breeze/theme.conf >> >> until the package is fixed. > >Thanks. > >> > >the password chars were REALLY tiny. I could still login though. > >Should the following be added to that file for the tiny char issue? >fontSize=10 I dont know but fixing the wallpaper path also fixes the font size for me so I'd prefer not touching anything else if not required. >Diffing the theme.conf files also showed this item: >needsFullUserModel=false > >But I have no idea what that is for (and thus whether it's needed). AFAICR it's related to remote logins and not loading all user information by default to avoid performance problems on the login screen. In any case I've uploaded plasma-workspace 4:5.26.0-2 with the fix and I've synchronised the theme conf file with the upstream one as you suggest. Happy hacking, -- Aurélien
Re: Plasma 5.26 coming to unstable - Thank you!
Le mercredi 12 octobre 2022, 17:07:35 CEST Joe McEntire a écrit : > I noticed the very tiny lettering too, switched themes from debian breeze to > just breeze and swapped background to homewold and all is well. One issue I > do still have is in wayland my right click menu is not being positioned > correctly. It's way off to the right of where I click. Thinking that has > something to do with having 4 monitors with carrying resolutions. > > On October 12, 2022 11:02:18 AM EDT, Diederik de Haas > wrote: > >On Wednesday, 12 October 2022 11:07:05 CEST Sedat Dilek wrote: > >> No background wallpaper in SDDM (white background) - only visible is > >> the box where I can type my password. > > > >I did have a background wallpaper in SDDM, but the password chars were > >REALLY > >tiny. I could still login though. Thanks all for the comments. Indeed the bug is still present in the 5.26.0 packages. Alternatively you can add the following line : background=/usr/share/desktop-base/active-theme/login/background.svg at the end of this file : /usr/share/sddm/themes/debian-breeze/theme.conf until the package is fixed. Best, -- Aurélien
Re: Plasma 5.26 coming to unstable - Thank you!
Le 12 octobre 2022 11:07:05 GMT+02:00, Sedat Dilek a écrit : >After a reboot my only complaint is... > >No background wallpaper in SDDM (white background) - only visible is >the box where I can type my password. > >So, changing from Wayland to X11 or GNOME seems "unpossible". >( Might be solvable via KDE/systemsettings? ) Yes, thanks for the feedback. I noticed this a bit too late but it's already fixed in the 5.26.0 packages. Happy hacking ! -- Aurélien
Re: Plasma 5.26 coming to unstable - Thank you!
Plus I explained this explicitly in my email about 5.26 beta… 🙂 Le 12 octobre 2022 10:49:12 GMT+02:00, Sedat Dilek a écrit : >I love to answer my own questions: > ># zless /usr/share/doc/kwin-wayland/changelog.Debian.gz >... >kwin (4:5.25.90-1) experimental; urgency=medium > > [ Aurélien COUDERC ] > * New upstream release (5.25.90). > * Bump version of internal libraries libkwineffects and libkwinglutils > from 13 to 14. > ... > * Upstream merged Wayland backends into the main KWin library. <--- XXX: NOTE > >I guess this is... /usr/lib/x86_64-linux-gnu/libkwin.so.5.26.0 > >Quick check with llvm-objdump: > ># llvm-objdump-15 -D /usr/lib/x86_64-linux-gnu/libkwin.so.5.26.0 | >grep -i backend | grep -i wayland >matches: KWin7Wayland14WaylandBackend > >Obsolete (bumped version 13 -> 14) - remove: ># dpkg --purge libkwinxrenderutils13 > >-sed@- > >On Wed, Oct 12, 2022 at 10:33 AM Sedat Dilek wrote: >> >> [ Please CC me I am not subscribed to this ML ] >> >> Hi, >> >> Thanks for the quick packaging + upload to Debian/unstable AMD64. >> >> Looks like 4 packages missing: >> >> # git diff KDE/KP-5-25-5 KDE/KP-5-26-0 >> diff --git a/KDE/KP-5-25-5 b/KDE/KP-5-26-0 >> index 94f379d..86078b0 100644 >> --- a/KDE/KP-5-25-5 >> +++ b/KDE/KP-5-26-0 >> @@ -28,9 +28,6 @@ kwin-common >> kwin-data >> kwin-style-breeze >> kwin-wayland >> -kwin-wayland-backend-drm >> -kwin-wayland-backend-wayland >> -kwin-wayland-backend-x11 >> kwin-x11 >> kwrited >> layer-shell-qt >> @@ -51,9 +48,8 @@ libksysguardformatter1 >> libksysguardsensorfaces1 >> libksysguardsensors1 >> libksysguardsystemstats1 >> -libkwineffects13 >> -libkwinglutils13 >> -libkwinxrenderutils13 >> +libkwineffects14 >> +libkwinglutils14 >> libkworkspace5-5 >> liblayershellqtinterface5 >> libnotificationmanager1 >> >> Note: Yes, I use `git diff` for comparing files. >> >> Those packages were built out of kwin sources. >> >> But... kwin_5.26.0-1.dsc [1] says: >> >> Package-List: >> kwin-common deb kde optional arch=any >> kwin-data deb kde optional arch=all >> kwin-dev deb libdevel optional arch=any >> kwin-wayland deb kde optional arch=any >> kwin-x11 deb kde optional arch=any >> libkwineffects14 deb libs optional arch=any >> libkwinglutils14 deb libs optional arch=any >> >> So my question: What happened to these packages? >> >> -kwin-wayland-backend-drm >> -kwin-wayland-backend-wayland >> -kwin-wayland-backend-x11 >> -libkwinxrenderutils13 >> >> Now, obsolete? >> Moved from kwin to a different package? >> Included in kwin in a different manner? >> >> Thanks in advance for answering my questions? >> >> [1] >> https://incoming.debian.org/debian-buildd/pool/main/k/kwin/kwin_5.26.0-1.dsc >> >> Best regards, >> -Sedat- >> >> P.S.: Status/Availability of some packages >> >> # LC_ALL=C apt-cache policy kwin-wayland-backend-drm >> kwin-wayland-backend-wayland kwin-wayland-backend-x11 >> libkwinxrenderutils13 >> kwin-wayland-backend-drm: >> Installed: (none) >> Candidate: 4:5.25.5-1 >> Version table: >> 4:5.25.5-1 500 >>500 https://ftp.debian.org/debian testing/main amd64 Packages >>500 https://deb.debian.org/debian testing/main amd64 Packages >> 4:5.20.5-1 500 >>500 https://ftp.debian.org/debian stable/main amd64 Packages >>500 https://deb.debian.org/debian stable/main amd64 Packages >> kwin-wayland-backend-wayland: >> Installed: (none) >> Candidate: 4:5.25.5-1 >> Version table: >> 4:5.25.5-1 500 >>500 https://ftp.debian.org/debian testing/main amd64 Packages >>500 https://deb.debian.org/debian testing/main amd64 Packages >> 4:5.20.5-1 500 >>500 https://ftp.debian.org/debian stable/main amd64 Packages >>500 https://deb.debian.org/debian stable/main amd64 Packages >> kwin-wayland-backend-x11: >> Installed: (none) >> Candidate: 4:5.25.5-1 >> Version table: >> 4:5.25.5-1 500 >>500 https://ftp.debian.org/debian testing/main amd64 Packages >>500 https://deb.debian.org/debian testing/main amd64 Packages >> 4:5.20.5-1 500 >>500 https://ftp.debian.org/debian stable/main amd64 Packages >>500 https://deb.debian.org/debian stable/main amd64 Packages >> libkwinxrenderutils13: >> Installed: 4:5.25.5-1+b1 >> Candidate: 4:5.25.5-1+b1 >> Version table: >> *** 4:5.25.5-1+b1 100 >>100 /var/lib/dpkg/status >> 4:5.25.5-1 500 >>500 https://ftp.debian.org/debian testing/main amd64 Packages >>500 https://deb.debian.org/debian testing/main amd64 Packages >> >> -EOT- >
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
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
Plasma 5.26 beta available near you
Hi all, Plasma 5.26 beta (5.25.90) was uploaded to experimental and should be installable now or in the next couple of hours. The package set is mostly the same with just 2 notable changes : - soname bumps for libkwineffects14 and libkwinglutils14 - dropped internal libraries libkwinxrenderutils13 and kwin-wayland-backend-*, these can be safely removed after the upgrade. I still need to package kpipewire which I understand handles Pipewire integration with flatpacked apps, and rebuild plasma-workspace with it. The Plasma 5.26 release is expected to happen on Tuesday and I should be able to upload it to unstable shortly. Happy testing to the adventurous. 🙂 -- Aurélien
Re: Bug#1020417: plasma-vault: encfs security warning during Debian-Installer when KDE desktop selected
Le dimanche 2 octobre 2022, 16:59:13 CEST Aurélien COUDERC a écrit : > > Le 2 octobre 2022 15:20:45 GMT+02:00, Philip Hands a écrit : > >Hi, > > Dear Phil, > > >[Please CC me if you want me to see your replies] > > > >I'd imagine you all saw this bug go past, so I was wondering if the lack > >of reaction is due to it seeming to be Somebody Else's Problem. > > Not at all. > > I have 5.26 in the works with the fix for this bug and thought it could wait > until then but it's taking more time than I had anticipated. > > Sune committed the fix to Salsa on top of 5.25.5 today and I'll upload it > later today if no one beats me at it. Voilà, the fix is uploaded. (btw, we use pkg-kde-talk@alioth for packaging discussions, debian-kde@l.d.o is for users) Happy hacking, -- Aurélien
Re: Bug#1020417: plasma-vault: encfs security warning during Debian-Installer when KDE desktop selected
Le 2 octobre 2022 15:20:45 GMT+02:00, Philip Hands a écrit : >Hi, Dear Phil, >[Please CC me if you want me to see your replies] > >I'd imagine you all saw this bug go past, so I was wondering if the lack >of reaction is due to it seeming to be Somebody Else's Problem. Not at all. I have 5.26 in the works with the fix for this bug and thought it could wait until then but it's taking more time than I had anticipated. Sune committed the fix to Salsa on top of 5.25.5 today and I'll upload it later today if no one beats me at it. Happy hacking, -- Aurélien
Re: [plasmashell] [Bug 452888] 24-hour config setting does not propagate to items in the "Copy to clipboard" menu
Le mardi 27 septembre 2022, 00:08:47 CEST local10 a écrit : > Sep 26, 2022, 20:02 by li...@coucouf.fr: > > I'm currently working on packaging the incoming 5.26 release and I don't > > feel the severity of the bug deserves being patched urgently. > > > > If you really need it fixed now you can work on the patch and provide an > > MR on Salsa. If the change looks reasonable I'll upload it to Debian. > You're right, there's really no great urgency about this bug. Was really > inquiring about the backport because I assumed 5.26 may take some months. > So what are your plans for 5.26? I’m working on 5.26 beta and wantet do push it to experimental but I’m a bit short on time. 5.26.0 should be doable and should reach Debian close to the upstream release date (11/10). Happy hacking, -- Aurélien
Re: [plasmashell] [Bug 452888] 24-hour config setting does not propagate to items in the "Copy to clipboard" menu
Dear local10, Le 26 septembre 2022 19:12:51 GMT+02:00, local10 a écrit : >Sep 26, 2022, 16:37 by bugzilla_nore...@kde.org: > >>> --- Comment #14 from Nate Graham <>> n...@kde.org>> > --- >>> This bug is marked as fixed in 5.26; you're using 5.25.5. >>> >>> Unfortunately a backport was too to make it inth the final 5.25 release so >>> it >>> didn't get done. The Debian packagers will patch to manually patch it if >>> they >>> want this fix included. >>> >>> >> https://bugs.kde.org/show_bug.cgi?id=452888 >> > > >Any chance this bug can be backported to 5.25? I'm currently working on packaging the incoming 5.26 release and I don't feel the severity of the bug deserves being patched urgently. If you really need it fixed now you can work on the patch and provide an MR on Salsa. If the change looks reasonable I'll upload it to Debian. Happy hacking ! -- Aurélien
Re: KDE 5.97 frameworks
Le 21 août 2022 07:17:34 GMT+02:00, Luc Castermans a écrit : >Dear > >Thank you for making KDE 5.97 frameworks available. You're welcome. Even if every new version is not strictly required by Plasma/Gear I'm currently trying to follow upstream so each individual update requires less work. (And thanks to Patrick for the actual upload.) Also it should be easier to report bug upstream if we have the latest version in Debian with the latest fixes (and bugs 🙂). Happy hacking, -- Aurélien
Re: plasma 25.4
Le 10 août 2022 09:56:53 GMT+02:00, local10 a écrit : >Aug 10, 2022, 05:46 by li...@coucouf.fr: > >> Also your bug report is misleading to me. You describe it as a 3rd party >> applet whereas it’s definitely a Plasma applet shipped with the Plasma >> source code. For me 3rd party would be that you installed yourself from some >> other source. > >That wasn't me. It was the KDE dev who responded and described the System >Monitor widget as a 3rd party applet. I was surprised as well but was hoping >the applet dev would clarify the issue: see >https://bugs.kde.org/show_bug.cgi?id=457379 > Ah, right. Also it would help if you could get a screenshot of the "before" state. (Maybe on stable ?) Without having it for comparison it's a bit difficult to get an idea. The current state looks pretty reasonable. Cheers, -- Aurélien
Re: plasma 25.4
Hi local10, Le 10/08/2022 à 00:21, local10 a écrit : Aug 9, 2022, 14:19 by pior...@gmx.com: Yes, KDE 5.25.4 is up and running. Everything fine, so far! Can't really say the same. 25.4.3 had created some issues for me[1][2] that continued in 25.4.4, the devs say some are resolved in 25.4.5. So what are the plans for 25.4.5? Also, any plans for elisa 22.04.3 [3]? 1. https://bugs.kde.org/show_bug.cgi?id=457357 OK I’m backporting the fix to the Debian package. 2. https://bugs.kde.org/show_bug.cgi?id=457379 Not clear to me. As far as I understand, the status RESOLVED DOWNSTREAM means the devs thinks it’s not an issue in Plasma and are closing the bug, *NOT* that it has been fixed. Also your bug report is misleading to me. You describe it as a 3rd party applet whereas it’s definitely a Plasma applet shipped with the Plasma source code. For me 3rd party would be that you installed yourself from some other source. 3. https://bugs.kde.org/show_bug.cgi?id=457510 Yes it’s on my TODO list too. :) There were some failing unit tests that I’ve discussed with the upstream developer who already fixed some. I’ll disable the remaining failing ones for now. Happy hacking ! -- Aurélien
Re: plasma 25.4
Le 9 août 2022 16:19:52 GMT+02:00, piorunz a écrit : >On 08/08/2022 07:21, Luc Castermans wrote: >> Dear >> >> Just saw many Plasma 25.4 packages being installed. Thank you very much! >> >Yes, KDE 5.25.4 is up and running. Everything fine, so far! Thanks for the feedback. A bit less visible but we also had frameworks 5.96 a while back and 5.97 should follow around the time of its release if no particular problem arise. Happy hacking ! -- Aurélien
Re: Remaining KDE/Apps version 21.12.3
Dear Sedat,
thank you for your feedback.
We try to keep the packages as up to date as possible with the rest of
the Qt/KDE packaging team but that’s quite a big piece work. There are
more than 400 source packages including Qt and KDE packages, and several
more hundred binary packages built from those.
I have a plan to update apps to 22.04 like in « I’d like to find time to
do so », so no ETA.
It’s not a complex work but there are a lot of packages to do. So if
some people feel like scratching their own itch and getting started with
updating the Debian package for their KDE Gear of choice, feel free to
join us on #debian-qt-kde and step in. :-)
Happy hacking !
--
Aurélien
Le 21/06/2022 à 12:46, Sedat Dilek a écrit :
Hi,
I just upgraded to packages from Debian/experimental where possible...
1. Qt version 5.15.4
2. KDE/Frameworks version 5.94.0
3. KDE/Plasma version 5.25
4. KDE/Gears (formerly KDE/Apps) version 22.04.1 + 22.04.2
What are the plans for the remaining KDE/Apps version 21.12.3?
root# dpkg -l | grep 21.12.3 | awk '/^ii/ {print $1 " " $2 " " $3}' | column -t
ii ffmpegthumbs4:21.12.3-1.1
ii k3b 21.12.3-1
ii k3b-data21.12.3-1
ii k3b-i18n21.12.3-1
ii kaccounts-integration 4:21.12.3-1
ii kaccounts-providers 4:21.12.3-1
ii kamera 4:21.12.3-1
ii kde-telepathy-kaccounts 21.12.3-1
ii kde-telepathy-kpeople 21.12.3-1
ii kdeconnect 21.12.3-1
ii kdegraphics-thumbnailers4:21.12.3-1
ii kdepim 4:21.12.3+5.122
ii kdialog 4:21.12.3-1
ii keditbookmarks 21.12.3-1
ii kfind 4:21.12.3-1
ii kio-extras 4:21.12.3-1
ii kio-extras-data 4:21.12.3-1
ii kmag4:21.12.3-1
ii kmousetool 4:21.12.3-1
ii kmouth 4:21.12.3-1
ii konq-plugins4:21.12.3-1
ii konqueror 4:21.12.3-1
ii kontrast21.12.3-1
ii libk3b7:amd64 21.12.3-1
ii libk3b7-extracodecs:amd64 21.12.3-1
ii libkaccounts2:amd64 4:21.12.3-1
ii libkf5baloowidgets-bin 4:21.12.3-1
ii libkf5baloowidgets5:amd64 4:21.12.3-1
ii libkf5cddb5:amd64 4:21.12.3-1
ii libkf5kdcraw5:amd64 21.12.3-1
ii libkf5kexiv2-15.0.0:amd64 21.12.3-1
ii libkf5kipi-data 4:21.12.3-1
ii libkf5konq6:amd64 4:21.12.3-1
ii libkpmcore1121.12.3-1
ii libktpcommoninternals9abi1:amd6421.12.3-1
ii libktplogger9abi1:amd64 21.12.3-1
ii libqmobipocket2:amd64 4:21.12.3-1
ii partitionmanager21.12.3-1
ii qml-module-org-kde-kaccounts:amd64 4:21.12.3-1
ii signon-kwallet-extension:amd64 4:21.12.3-1
ii sweeper 4:21.12.3-1
For me this was sort of extra work to downgrade KDE/Apps down to
version 21.12.3.
Some background infos:
Before I had used & enabled Norbert Preining's 3rd party APT
repositories which offer newer versions of above listed packages.
I stopped using them as the maintainer no longer runs a Debian system
and as a consequence switched to official Debian repos.
Personally, I am interested in fresh modern KDE/Qt packages in the Debian world.
Thanks for providing uploads so quickly!
Regards,
-Sedat-
Re: plasma 5.25 / PIM 22.04
Hi Diederik,
Le 17/06/2022 à 01:52, Diederik de Haas a écrit :
On Thursday, 16 June 2022 07:40:07 CEST Aurélien COUDERC wrote:
Le 16 juin 2022 07:31:39 GMT+02:00, Luc Castermans
a écrit :
Yesterday I was able to install Plasma 5.25 from Experimental. All good
sofar.
good to know, thanks for the feedback.
There's an ongoing Qt 5 transition so I won't upload to unstable just now to
avoid it and the Plasma transition stepping onto each other's toes.
I seem to have run into an issue:
Ah, yes.
# aptitude install kdepim-addons libkpimitinerary5 -t experimental
The following NEW packages will be installed:
kdepim-addons libkpimitinerary-data{a} libkpimitinerary5{b}
libkpimpkpass5{a} libphonenumber8{a}
0 packages upgraded, 5 newly installed, 0 to remove and 176 not upgraded.
Need to get 2,690 kB of archives. After unpacking 13.9 MB will be used.
The following packages have unmet dependencies:
libkpimitinerary5 : Depends: qtdeclarative-abi-5-15-2 which is a virtual
package, provided by:
- libqt5qml5 (5.15.2+dfsg-10), but 5.15.4+dfsg-3
is installed
- libqt5qml5 (5.15.2+dfsg-6), but 5.15.4+dfsg-3
is installed
PIM 22.04.x in experimental was built before the Qt transition so it
still has the dependencies on Qt 5.15.2, so right now you kind of have
to fallback to PIM 21.12.x from unstable which has been rebuilt with the
new Qt.
@Patrick I don’t know what your plans are for PIM but would you mind
rebuilding the experimental version against Qt 5.15.4 ?
Thanks !
--
Aurélien
Re: plasma 5.25
Hi Luc, Le 16 juin 2022 07:31:39 GMT+02:00, Luc Castermans a écrit : >Yesterday I was able to install Plasma 5.25 from Experimental. All good >sofar. > >Big thank you for making this happen!! good to know, thanks for the feedback. There's an ongoing Qt 5 transition so I won't upload to unstable just now to avoid it and the Plasma transition stepping onto each other's toes. But it should happen in the coming week or so. Happy hacking ! -- Aurélien
Re: Thank you!
Also the thanks should extend to Rik Mills from Kubuntu who takes great care to catch up with us on IRC regularly and ensure as much as possible is maintained in a shared way between both Debian and Ubuntu ! Le 2 juin 2022 08:26:12 GMT+02:00, Martin Steigerwald a écrit : >Hi! > >A huge thanks to the Debian Qt/KDE maintainer team for the continued >work on Qt/KDE related packages. > >Thank you to Pino, Patrick, Aurélien and of course all the others for >tirelessly packaging newest versions of Qt, including Qt 6 which KDE >will switch to at some time, Plasma, KDE Frameworks, KDE Gear, KDEPIM >and all the other applications from KDE, including new ones like the >Korganizer alternative Kalendar. I bet in total that could easily be >about one thousand packages, maybe even more. It is a huge effort to pull >this off! > >While not all of this is available within unstable yet, at least not in >most recent versions, most of it is and the state of the art in unstable >regarding KDE related packages is very decent. > >Thank you for this continued effort to all of you, of course also to >those who I did not mention specifically including those long term team >members who advice newcomers to the team on packaging questions and >those who contributed a lot previously. > >I appreciate your effort! > >Best, >-- >Martin > >
Re: Plasma 5.25 beta in experimental (was: Thank you!)
Hi, thanks, appreciated. By the way, I’ve uploaded Plasma 5.25 beta to experimental. If you feel like testing pre-release software and reporting issues to the upstream project, feel free to give it a try. ;-) Happy hacking ! -- Aurélien Le 02/06/2022 à 08:26, Martin Steigerwald a écrit : Hi! A huge thanks to the Debian Qt/KDE maintainer team for the continued work on Qt/KDE related packages. Thank you to Pino, Patrick, Aurélien and of course all the others for tirelessly packaging newest versions of Qt, including Qt 6 which KDE will switch to at some time, Plasma, KDE Frameworks, KDE Gear, KDEPIM and all the other applications from KDE, including new ones like the Korganizer alternative Kalendar. I bet in total that could easily be about one thousand packages, maybe even more. It is a huge effort to pull this off! While not all of this is available within unstable yet, at least not in most recent versions, most of it is and the state of the art in unstable regarding KDE related packages is very decent. Thank you for this continued effort to all of you, of course also to those who I did not mention specifically including those long term team members who advice newcomers to the team on packaging questions and those who contributed a lot previously. I appreciate your effort! Best,
Re: Kind request to package kpart-webkit for modern Debian versions
[adding pkg-kde-talk@alioth-lists to the thread, where we discuss packaging topics] Le 9 mai 2022 20:10:19 GMT+02:00, ValdikSS a écrit : >Hello, mailing list. Hi ValdikSS, >Is there any chance to get kpart-webkit package into newer Debian versions? >https://packages.debian.org/stretch/kpart-webkit > >This package allows to use Webkit renderer in Konqueror browser. This renderer >is outdated and not compatible with all the websites, however it is much >faster and lower on RAM consumption than modern WebEngine used by default. >This would allow to browse the web using very low-end machines by current >standards, such as 32-bit PCs with 512 MB RAM. > >Debian is basically the only major Linux distribution which still supports >i386, and there's Webkit packaged for Surf and Qutebrowser packages, and it's >even present as a module for KDE Frameworks (libkf5webkit5), but it can't be >used in Konqueror due to missing kpart. > >Kindly asking to bring old kpart-webkit package from Stretch to newer >Bullseye, to extent the lifespan of older hardware. Surf and QuteBrowser still >could be used, but that browsers are aimed at keyboard controls, not a regular >interface such as Konqueror. The package was removed from Debian for a specific reason : it's dependency on Qt4 : https://tracker.debian.org/news/902784/removed-134-2-from-unstable/ Since it seems to have been ported to Qt5 / KF5 in the meantime I see no technical reason why it shouldn't be reintegrated into Debian. However this is still a relatively niche use case and the Qt/KDE Team in Debian is generally more interested in on-boarding more contributors than more packages. 😉 So if you want to see it back I'd advise you fork the repo and start getting the package up to date with upstream and Debian standards, so we can review and upload your work to the archive. Feel free to join #debian-qt-kde on IRC and ask for help/review. >P.S. libkf5webkit5 package description says it provides kpart component, which >is does not. Could it be the whole reason of missing webkit in Konqueror? The description is purely … hem … descriptive. I'll have a look at what's in the package and fix the description accordingly. Happy hacking ! -- Aurélien
Re: [SOLVED] Re: State of KDE in testing?
Le 23 avril 2022 22:15:05 GMT+02:00, local10 a écrit : > >So I have upgraded from Bullseye to Bookworm. The upgraded wasn't completely >smooth, there were some errors and some packages "dist-upgrade" failed to >upgrade. But running "safe-upgrade" and then "full-upgrade" afterwards has >upgraded them. That's the recommended / supported way to upgrade between major Debian releases, so nothing too surprising here. See Debian 11's release doc §4.4.4 and 4.4.5 for example : https://www.debian.org/releases/bullseye/amd64/release-notes/ch-upgrading.en.html#minimal-upgrade Welcome to bookworm. :-) Happy hacking, -- Aurélien
Re: State of KDE in testing?
Le 20 avril 2022 17:24:23 GMT+02:00, local10 a écrit : >Apr 20, 2022, 11:08 by li...@coucouf.fr: > >> One thing to be aware of is to be more careful when upgrading major versions >> of Plasma. We currently don't have a safe way to ensure that all Plasma >> packages transition form unstable (where we upload them) to testing at once. >> So be sure you know what you're doing when doing upgrades to ensure you >> don't end up with mixed versions of Plasma packages. >> > >That's what I was concerned about. I usually use "aptitude dist-upgrade" to >upgrade between releases, so will it catch a situation like that or will I >have to manually ensure that all KDE packages are of the same version? > >Also, what is the current state of KDE/X in testing, are all packages of the >same Plasma/KDE version? It's all fine and ready and fine as a daily driver on both AMD and Intel graphics for what I use. Even Wayland in Intel is mostly stable (like < 1 crash a week) in my experience and setup. Possible breakages would happen around when a new major version of Plasma gets released so the next would be mid-June with Plasma 5.25. Happy testing ! -- Aurélien
Re: State of KDE in testing?
Le 20 avril 2022 02:43:50 GMT+02:00, local10 a écrit : >Hi, Hi local10, >Am thinking about upgrading from Bullseye to Bookworm as there are some minor >bugs in Bullseye that annoy me and I hope they are resolved in Bullseye. >What's the current state of KDE in testing and testing in general? Any issues >I need to be aware of? I use KDE with X. Testing is in a generally usable state and many are using it as a daily driver. Obviously if you're running mission critical machines and cannot afford hicups you should be running stable. We try to follow upstream releases closely in testing with the latest upstream versions of Plasma and Gear (applications) currently available and the KDE frameworks libraries being slightly older. One thing to be aware of is to be more careful when upgrading major versions of Plasma. We currently don't have a safe way to ensure that all Plasma packages transition form unstable (where we upload them) to testing at once. So be sure you know what you're doing when doing upgrades to ensure you don't end up with mixed versions of Plasma packages. Or/and continue reading this list where transitions are announced and you get warned during transitions. Regarding the bugs we're following upstream closely, so as others have said we tend to have mostly upstream bugs. 🙂 It's a bit easier to report these to upstream than if you're using stable though, because upstream focus is really on the latest versions and not on our stable ones. Happy testing ! -- Aurélien
plasma-gamemode
Dear all, for those of you using Plasma for gaming you may want to give a look at the new plasma- gamemode package. It was just accepted by the FTP masters and is now available in unstable. [1] https://apachelog.wordpress.com/2022/03/04/plasma-gamemode/[1] [2] https://github.com/FeralInteractive/gamemode[2] You will need both plasma-gamemode and gamemode Debian packages for it to work. plasma-gamemode is still in very early stages but it seems to work for me so far. Happy gaming ! -- Aurélien [1] https://apachelog.wordpress.com/2022/03/04/plasma-gamemode/ [2] https://github.com/FeralInteractive/gamemode
Re: Plasma 5.24 coming to unstable
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: KDE Frameworks 5.90 coming to unstable
Le 12 février 2022 12:44:21 GMT+01:00, "Aurélien COUDERC" a écrit : > > >Le 12 février 2022 12:02:24 GMT+01:00, Sami Erjomaa a >écrit : >>> >>> >>> It appears to me that it is complete already. >>> >>> >>Frameworkintegration hasn't been built since it depends on knewstuff that's >>in the "NEW" queue. >I'll post some workarounds later today but I wouldn't recommend to upgrade >only parts of frameworks. No one tested this, neither upstream nor myself. So it turns out knewstuff cleared the NEW queue really quick thanks to FTP masters, so please just wait for everything to build in the coming hours and update once everything is available as 5.90. Happy testing ! -- Aurélien
Re: KDE Frameworks 5.90 coming to unstable
Le 12 février 2022 12:02:24 GMT+01:00, Sami Erjomaa a écrit : >> >> >> It appears to me that it is complete already. >> >> >Frameworkintegration hasn't been built since it depends on knewstuff that's >in the "NEW" queue. Yes, that's not what I wanted to do. I was planning to upload to experimental first but I finished a bit too late and mixed things up. I'll post some workarounds later today but I wouldn't recommend to upgrade only parts of frameworks. No one tested this, neither upstream nor myself. Sorry for the inconvenience. -- Aurélien
Re: Future of KDE packages in Debian
Dear all, please consider that events being commented here have already happened, had consequences and it’s not like you can go back in time. Debian like most human groups has rules on how to become and stay a member of the community. If you’re interested in them you can find pointers at : https://wiki.debian.org/DAManager The discussions on this have long passed usefulness and are more and more offtopic for a Debian mailing list for KDE users. Regarding the maintenance of the KDE stack in Debian, as I wrote earlier help is very much welcome ! You’re welcome to test and report here, welcome to file bugs, welcome to step in and help update or maintain your favorite desktop and apps ! If you’re interested in packaging software for Debian you can start at : https://mentors.debian.net/intro-maintainers/ and join the #debian-qt-kde IRC channel, subscribe to the pkg-kde-talk mailing list. You’re obviously also free to go some place else if you so prefer. We’re lucky that the Free and Open Source community is striving with many nice projects to use and contribute to. Also remember that there are people on the other side of your "apt update" who spend hours packaging complex software for the benefits of everyone, on their free time. Gratuitous criticism of what others choose to do or not do in a volunteer project is uncalled for, unwelcome and only going to make things worse. So please refrain from doing so and if you’re unhappy with something do come and fix it instead. :-) Happy hacking ! -- Aurélien Le dimanche 23 janvier 2022, 21:51:51 CET Rainer Dorsch a écrit : > Hi Luc, > > the DAMs decision is extremly frustrating for Debian KDE users and given the > short statement on debian-user > > https://lists.debian.org/debian-user/2022/01/msg00807.html > > it is at least not clear to me if they seriously searched for a solution > which would have served better all involved parties and the Debian (KDE) > users. This message even increases the doubt, that searching for such a > solution was a priority for them > > https://lists.debian.org/debian-project/2019/01/msg00186.html > > I used the ... which the DAMs created in Debian KDE as opportunity and > installed on a new desktop Manjaro stable instead of Debian to experiment > with it (I still have Debian bullseye desktops in use). As a Debian stable > user I considered manjaro more appropriate than Arch. > > Kmail 5.19.0/21.12.0 in manjaro stable was a pleasant surprise. Even though > it is newer than Kmail in Debian unstable, the manjaro stable upgrade to > 21.12.1 is downloaded while I am writting. I am curious to see how this > experiment goes in the next months in particular the updates. The good > thing for Open Source users is that we have choice if things go into the > wrong direction somewhere :-) > > Rainer > > On Sonntag, 23. Januar 2022 18:56:09 CET Luc Castermans wrote: > > yep. > > > > For me key is that we loose a very valuable contributor and great > > contribution!Reasons for this are unclear to me. Why this demotion, > > are > > those who decide on this stating and communicating their reasons, better > > is > > this a group decision? > > > > Luc > > > > Op zo 23 jan. 2022 13:59 schreef Dietz Proepper : > > > Am Freitag, 21. Januar 2022, 01:11:44 CET schrieb Johannes Zarl-Zierl: > > > > > I never had any issues with Norbert. > > > > > > > > Full ACK. > > > > > > +1. And also not with Marco, as far as I remember. Which comes with > > > little > > > relevance, as we did not have much contact before. > > > > > > > Let's always keep discussions civil and in good faith... > > > > > > Well, but jftr, let's not forget who started this thread and in which > > > way. > > > At > > > the very least, citing the source of ones comments is quite basic > > > IMNSHO. > > > > > > Kindest regards, > > > > > > Dietz
Re: Dolphin stopped displaying hidden folders in the Folders pane
Dear Gary, Le jeudi 20 janvier 2022, 19:29:35 CET Gary Dale a écrit : > I'm running Debian/Bookworm on an AMD64 machine. > > For a few weeks now, Dolphin hasn't been showing hidden folders in the > Folders pane. I've set the view to show hidden files and have been > seeing hidden folders in the Folders pane since Dolphin was first > introduced. When I right click on the folders pane itself I have a « show hidden files » checkbox that seems to have the behaviour you're looking for. Does that work for you ? Happy hacking, -- Aurélien
Re: Future of "his" packages in Debian
Le 20 janvier 2022 23:09:30 GMT+01:00, piorunz a écrit : >On 20/01/2022 18:17, Marco Valli wrote: >>> by Norbert Preining · 2022/01/14 >> >> Admittedly, this guy doesn't have much faith in the the Debian/Kde team. 😆 >> Regards >> >Who is this clown again? 😂 The Debian KDE team is a (small) handful of people maintaining both the Qt stack and the ~500 frameworks/plasma/apps packages on their free time. Lately Norbert was doing most of the later. More contributors are really welcome ! If you've always wanted to become a Debian contributor and are interested in the KDE stack, now is a perfect time. Join us on IRC, the handful is a friendly bunch of people. Best, -- Aurélien
Re: Kmail2 - Configure Special Window Setting: does not register (sid)
Le samedi 6 février 2021, 13:28:11 CET Sandro Knauß a écrit : > Hey Norbert, > > > Should we cherry-pick the relevant fix commit > > https://invent.kde.org/frameworks/kconfig/commit/b57c7ad9acf45928a6debefcd > > 43 2cc50432fefdb > > Yes we should cherry-pick this one. For the record, this has been uploaded as part of kconfig 5.78.0-4, thanks for the suggestion and thanks Norbert for the cherry-pick. Happy hacking ! -- Aurélien
Re: No Log In Notification
Hi ! Le vendredi 20 novembre 2020, 18:57:52 CET Brad Rogers a écrit : > On Fri, 20 Nov 2020 15:27:17 +0100 > "luca.pedrielli" wrote: > > >I can confirm. > >https://bugs.kde.org/show_bug.cgi?id=422948 I just came across this thread. The bug report says it’s fixed in Plasma 5.20.2 so it should be good in testing now that we have 5.20.5. Happy hacking ! -- Aurélien
Re: Plasma-discover (5.19.5-3) on testing closes unexpectedly( drkonqi)
Yeah, I tested with just the kirigami patch and it doesn’t fix it. I’ve committed the Discover patch to the salsa repo which really fixes it for me. If someone feels sure enough that it’s not going to interfere with the ongoing plasma transition to testing, feel free to upload. Happy hacking ! -- Aurélien Le vendredi 13 novembre 2020, 21:55:25 CET Rik Mills a écrit : > Plasma devs advised me that BOTH > > https://invent.kde.org/frameworks/kirigami/-/commit/6eaefba5001445fa7e198e4c > aa0bde738240d66f > > and > > https://invent.kde.org/plasma/discover/-/commit/c9438fc383630e452cd21dd7b495 > c925dcc82e28 > > were required to fix the crash. > > On testing myself, this did seem to be the case. > > On 13/11/2020 19:55, luca.pedrielli wrote: > > Fixed in Frameworks 5.75 or Plasma 5.20. > > > > Il 13/11/20 20:01, Rik Mills ha scritto: > >> Sounds like https://bugs.kde.org/show_bug.cgi?id=425670 > >> > >> On 13/11/2020 17:53, Héctor Sales Llamas wrote: > >>> After update testing (few minutes): > >>> > >>> I open Plasma-discover (5.19.5-3)--->Preferences--->closes > >>> unexpectedly( drkonqi) > >>> > >>> "Application: Discover (plasma-discover), signal: Segmentation fault > >>> > >>> [KCrash Handler] > >>> #4 0x7fb2643076df in QQmlData::createQQmlData(QObjectPrivate*) () > >>> from /lib/x86_64-linux-gnu/libQt5Qml.so.5 > >>> #5 0x7fb26423bcbd in > >>> QV4::QObjectWrapper::wrap_slowPath(QV4::ExecutionEngine*, QObject*) () > >>> from /lib/x86_64-linux-gnu/libQt5Qml.so.5 > >>> #6 0x7fb26423c10a in ?? () from > >>> /lib/x86_64-linux-gnu/libQt5Qml.so.5 > >>> #7 0x7fb26423d5b2 in > >>> QV4::QObjectWrapper::getQmlProperty(QV4::ExecutionEngine*, > >>> QQmlContextData*, QObject*, QV4::String*, > >>> QV4::QObjectWrapper::RevisionMode, bool*, QQmlPropertyData**) () from > >>> /lib/x86_64-linux-gnu/libQt5Qml.so.5 > >>> #8 0x7fb2643834e3 in QV4::QQmlTypeWrapper::virtualGet(QV4::Managed > >>> const*, QV4::PropertyKey, QV4::Value const*, bool*) () from > >>> /lib/x86_64-linux-gnu/libQt5Qml.so.5 > >>> #9 0x7fb2641d38ed in QV4::Lookup::getterFallback(QV4::Lookup*, > >>> QV4::ExecutionEngine*, QV4::Value const&) () from > >>> /lib/x86_64-linux-gnu/libQt5Qml.so.5 > >>> #10 0x7fb20c123825 in ?? () > >>> #11 0x in ?? () > >>> [Inferior 1 (process 3397) detached]" > >>> > >>> Best Regards
Re: dolphin 20.08.2 crashes upon right-click
Le samedi 31 octobre 2020, 12:38:57 CET Marco Möller a écrit : > Hello, Dear Marco, > Dolphin 20.08.2 ALWAYS crashes when trying to reach the context menu by > a right-click with the mouse somewhere inside Dolphin after my yesterday > update of my Debian/testing "bullseye". Thanks for reporting the issue. The answer is in the very clear, concise and understandable call stack. ;) Here: > Thread 1 (Thread 0x7f7275e01bc0 (LWP 3280)): > [KCrash Handler] […] > #5 0x7f7273475f23 in VersionControlObserver::actions(KFileItemList > const&) const () from /lib/x86_64-linux-gnu/libdolphinprivate.so.5 > #6 0x7f727346738c in > DolphinView::versionControlActions(KFileItemList const&) const () from […] > #12 0x7f72733fdbd4 in DolphinView::requestContextMenu(QPoint const&, > KFileItem const&, QUrl const&, QList const&) () from > /lib/x86_64-linux-gnu/libdolphinprivate.so.5 […] > KItemListController::mousePressEvent(QGraphicsSceneMouseEvent*, > QTransform const&) () from /lib/x86_64-linux-gnu/libdolphinprivate.so.5 Note the mousePressEvent -> requestContextMenu -> versionControlActions chain. The version control systems integration is part of dolphin-plugins and I can reproduce your issue with the versions currently in testing: dolphin 20.08.2 and dolphin-plugins 20.04.2. There seem to be a requirement to have exact same versions between the 2 that I haven’t seen explicitly in the make files. So to fix it immediately you can: - remove dolphin-plugins for now - grab dolphin-plugins/20.08.2 from unstable Or you can wait for dolphin-plugins/20.08.2 to migrate to testing which should happen in the next 24H. I’ll add a Breaks relation so users don’t run into this again. If you could file a bug in the Debian BTS to track the issue that would be appreciated. Happy hacking ! -- Aurélien
Kate with KUserFeedback support
Dear Team and Users, I’ve just uploaded Kate 20.08.2 to unstable, and now that we have KUserFeedback in Debian (thanks Scarlett and hefee !), I enabled its support in the build process for Kate. It’s off by default but if you’re interested in contributing usage metrics to the KDE project and participating in their surveys you now can ! To activate either, you need to go to the Setting->Configure Kate menu and then to the User Feedback section, and choose which level of metrics you may want to share and which frequency of surveys you’re interested in participating. Happy hacking ! -- Aurélien
