Here's the ticket to gather topics for the Plasma sprint: https://invent.kde.org/plasma/plasma-workspace/-/issues/32
On Mon, Jan 24, 2022 at 5:26 PM Marco Martin <notm...@gmail.com> wrote: > > Jonathan > * beta is out, beta testing day is done > * please fix bugs > * is there any progress on answering the lts question? > [discussion recap: lts now means we can't do the "last plasma release" > for 2 years, which is a quite realistinc timeframe anyways, so > decision is: let's do an lts-lite that can last less than 2 years] > [Discussion will continue on ML] > > Arjen > * so I finally merged a set of patches that have been around for a > while so we don't set default focus for a number of things if that > would show a virtual keyboard > * I also did a few small patches during the bug day last thursday to > fix some "vhi regression" bugs > * other than that, there was some discussion on the ml about doing a > virtual sprint february or march, were there any more concrete plans > there? > [Discussion: needs doodle] > [apol: I guess it could also make sense to discuss which topics we > need to go through] > [nico: I'd suggest that we collect topics on the ML in advance] > [apol: maybe we can have an invent issue] > [invent issue it is] > [d_ed: one thing we need to do, potentially at a sprint, is tag things > as "this is an interesting idea we could do" vs "this has to happen by > 6.0"] > > Bhushan > * So I've been trying to debug the weird plasma mobile issue where > plasmashell fails to connect to kactivitymanagerd and then doesn't > show anything. > * Some people say it is happening after recent qtwayland update > * But weirdly enough disabling systemd boot also makes it work > * I'm continuing to debug it today > [d_ed will look into it as it seems systemd-related] > > Nate > * So I have been doing a lot of bug triaging for the Plasma 5.24 beta > and we're in a pretty good shape. > *We're down to only 6 issues in the "VHI regressions" list: > https://bugs.kde.org/buglist.cgi?bug_status=UNCONFIRMED&bug_status=CONFIRMED&bug_status=ASSIGNED&bug_status=REOPENED&keywords=regression%2C%20&keywords_type=allwords&known_name=VHI-priority%20Plasma%20regressions&list_id=1967106&priority=VHI&product=Bluedevil&product=Breeze&product=Discover&product=drkonqi&product=frameworks-kirigami&product=frameworks-plasma&product=frameworks-qqc2-desktop-style&product=kactivitymanagerd&product=kde-gtk-config&product=kdeplasma-addons&product=khelpcenter&product=kinfocenter&product=klipper&product=kmenuedit&product=krunner&product=KScreen&product=kscreenlocker&product=ksmserver&product=ksysguard&product=KSystemLog&product=kwin&product=Plasma%20SDK&product=Plasma%20Vault&product=Plasma%20Workspace%20Wallpapers&product=plasma-integration&product=plasma-nm&product=plasma-pa&product=plasma-simplemenu&product=plasmashell&product=policykit-kde-agent-1&product=Powerdevil&product=print-manager&product=printer-applet&product=pulseaudio-qt&product=systemsettings&product=Touchpad-KCM&product=user-manager&product=xdg-desktop-portal-kde&query_based_on=VHI-priority%20Plasma%20regressions&query_format=advanced > > [d_ed will take 448475] > [marco will take 370676] > > > Aleix: > * maybe most useful to comment is sddm. I'd encourage anyone who can > to test the develop branch > * we'd like to get a release out so we can work on simplifying some > parts of the codebase and given how important a component it is, it > would be useful > * I'm aware there's some important pending PRs, we're trying to go > through them but it's also a delicate beast in itself > * testing these MRs on the different use-cases we might have would > also make it easier for reviewers > * other than that, I've been working on Discover and video recording > on wayland, not much to comment on that though > > > Kai Uwe > Dolphin/KIO: > Tab bar now accepts drop only ontop of a tab (denied cursor on blank > space) > Fix for janky show/hide animation in KFilePlacesView, please > review: https://invent.kde.org/frameworks/kio/-/merge_requests/725 > "Details" tab from Baloo-widgets is now only shown when it > actually has some details (it doesn't fetch them for remote locations) > Did some investigation as to why KFilePlacesView drop on place is > broken (cf. last week's notes), > Qt ignore()s the event and subsequently runs into the fallback > of calling dropMimeData to add the place to the model > > https://code.qt.io/cgit/qt/qtbase.git/tree/src/widgets/itemviews/qlistview.cpp?h=5.15#n963 > No idea what the right fix would be here. Just not calling > into the superclass in this case also wreaks all sorts of havoc to the > view's internal state. And doing a check for that special case in > KFilePlacesModel doesn't work as dropMimeData doesn't get the QEvent, > just the QMimeData within. And adding a special mime type is also ugly > because the QMimeData in the QEvent we get is const … whatever I try > :-( > Plasma: > Fixed regression in Bluetooth applet breaking the big "Enable" > button when it's off > Other: > Noticed a breakage in SDDM in neon, identical to > https://bugs.kde.org/show_bug.cgi?id=441080 – no idea why and how > > > Nico > * Fixed task manager identification for some XWayland apps, e.g. Chrome > webapps > https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/1396 > * which requires extending the plasmawindowmanagement protocol, so > lots of accompaning MRs > * Besides that I ported some things to the new ecm_add_qml_module > * I made patches to show pairing notifications for bluetooth and KDE > Connect even when in Do not Disturb, because those require user > interaction > * https://invent.kde.org/plasma/bluedevil/-/merge_requests/71 > * https://invent.kde.org/network/kdeconnect-kde/-/merge_requests/445 > * Fixed opening mailto urls not working sometimes: > https://invent.kde.org/frameworks/kio/-/merge_requests/719 > * Unbroke system dialogs, e.g. for screensharing portal: > https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/1368 > > > Carl > * Worked on moving the KCMS footer actions to the header: > https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/1391 > * But I hit a roadblock in the plasma mobile setting shell and will > need help with fixing: > https://invent.kde.org/plasma-mobile/plasma-settings/-/merge_requests/103 > (there is something wrong with the QMLContext and the kcm can't access > applicationWindow() and the contextDrawer). My solution of merging the > two context unfortunately crash often > [ahiemstra: I saw your patch for ActionMenu (I think it was?) but I > haven't had time yet to properly look into the implications of > changing it like that] > * oh yeah this one: > https://invent.kde.org/frameworks/kirigami/-/merge_requests/476 > > Fabian > * I submitted some more fixes for 5.24, one of which has apparently > caused a slight regression as Nate Graham just commented on > https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/1392#note_384538 > * Other than that, there's this fun issue: > https://invent.kde.org/qt/qt/qtwayland/-/merge_requests/24#note_383915 > * tl;dr: With the qtwayland MR for "nvidia gbm compatibility", > libreoffice crashes when using GTK, due to locking issues > * That instantiates a QGuiApplication, loading all kinds of plugins > and causing a qdbus thread to appear > > Marco > # Kirigami > * fixed the new kirigami search field icon/animation on dark themes, > was actually a qqc2-desktop-style bug > # Plasma > * reviewing bunch of merge requests > * more work on the screen reordering patches, manage the case of > redundant outputs, last feedbacks and adjustments, merged \o/ > * kwin dbus api to ask which is the active screen, popup krunner on > that screen probably will have to go in a wayland protocol, so not > much concrete so far > * resumed work on keyboard navigation on panels, trying a slightly > different approach with hopefully cleaner code and less work to do in > individual plasmoids and more "just works" > * attended plasma beta day, with usual bug triaging
