Bug#989038: kactivitymanagerd: KDE settings "activities:current" drives all activities to show the last "current activity" I setted
Package: kactivitymanagerd Version: 5.20.5-1 Severity: important X-Debbugs-Cc: t...@webologix.com Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Not shure but I think it happend with Bullseye version. * What exactly did you do (or not do) that was effective (or ineffective)? I defined several activities. Defined differents links to each activity The choice "Show files associated with the current activity" does not exist in Locations Desktop systemsettings Instead, choosed "activities:current" as the "Custom location" for all activities. * What was the outcome of this action? All activities show the last "current activity" I setted (right clic on desktop > locations > custom locations > activities:current. For instance if I define a "custom location" for activity x, all activities show activity x links on their desktop. Now, if I define a "custom location" for activity y, all activities show activity y links on their desktop * What outcome did you expect instead? Each activity should show its own links on desktop. That works fine on Ubuntu 20.04 *** End of the template - remove these template lines *** -- System Information: Debian Release: 11.0 APT prefers testing-security APT policy: (500, 'testing-security'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-4-rt-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_WARN Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages kactivitymanagerd depends on: ii kio5.78.0-4 ii libc6 2.31-12 ii libkf5configcore5 5.78.0-4 ii libkf5coreaddons5 5.78.0-4 ii libkf5crash5 5.78.0-3 ii libkf5dbusaddons5 5.78.0-2 ii libkf5globalaccel-bin 5.78.0-3 ii libkf5globalaccel5 5.78.0-3 ii libkf5i18n55.78.0-2 ii libkf5kiocore5 5.78.0-4 ii libkf5service-bin 5.78.0-2 ii libkf5service5 5.78.0-2 ii libkf5windowsystem55.78.0-2 ii libkf5xmlgui5 5.78.0-2 ii libqt5core5a 5.15.2+dfsg-5 ii libqt5dbus55.15.2+dfsg-5 ii libqt5gui5 5.15.2+dfsg-5 ii libqt5sql5 5.15.2+dfsg-5 ii libqt5sql5-sqlite 5.15.2+dfsg-5 ii libqt5widgets5 5.15.2+dfsg-5 ii libqt5xml5 5.15.2+dfsg-5 ii libstdc++6 10.2.1-6 kactivitymanagerd recommends no packages. kactivitymanagerd suggests no packages. -- no debconf information
Processed: [bts-link] source package src:qtbase-opensource-src
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:qtbase-opensource-src > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #898021 (http://bugs.debian.org/898021) > # Bug title: linux-image-4.16.0-1-amd64: kernel 4.16 infinite wait after dm > login on ivy bridge and bay trail > # * https://bugreports.qt.io/browse/QTBUG-69555 > # * remote status changed: In-Progress -> Closed > # * remote resolution changed: (?) -> Done > # * closed upstream > tags 898021 + fixed-upstream Bug #898021 [src:qtbase-opensource-src] linux-image-4.16.0-1-amd64: kernel 4.16 infinite wait after dm login on ivy bridge and bay trail Bug #898092 [src:qtbase-opensource-src] sddm: takes extremely long time to start Bug #904125 [src:qtbase-opensource-src] systemd: system startup stops unless root logs in in text mode Added tag(s) fixed-upstream. Added tag(s) fixed-upstream. Added tag(s) fixed-upstream. > usertags 898021 - status-In-Progress Usertags were: status-In-Progress. There are now no usertags set. > usertags 898021 + status-Closed resolution-Done There were no usertags set. Usertags are now: status-Closed resolution-Done. > # remote status report for #898092 (http://bugs.debian.org/898092) > # Bug title: sddm: takes extremely long time to start > # * https://bugreports.qt.io/browse/QTBUG-69555 > # * remote status changed: In-Progress -> Closed > # * remote resolution changed: (?) -> Done > # * closed upstream > tags 898092 + fixed-upstream Bug #898092 [src:qtbase-opensource-src] sddm: takes extremely long time to start Bug #898021 [src:qtbase-opensource-src] linux-image-4.16.0-1-amd64: kernel 4.16 infinite wait after dm login on ivy bridge and bay trail Bug #904125 [src:qtbase-opensource-src] systemd: system startup stops unless root logs in in text mode Ignoring request to alter tags of bug #898092 to the same tags previously set Ignoring request to alter tags of bug #898021 to the same tags previously set Ignoring request to alter tags of bug #904125 to the same tags previously set > usertags 898092 - status-In-Progress Usertags were: status-In-Progress. There are now no usertags set. > usertags 898092 + status-Closed resolution-Done There were no usertags set. Usertags are now: status-Closed resolution-Done. > # remote status report for #904125 (http://bugs.debian.org/904125) > # Bug title: systemd: system startup stops unless root logs in in text mode > # * https://bugreports.qt.io/browse/QTBUG-69555 > # * remote status changed: In-Progress -> Closed > # * remote resolution changed: (?) -> Done > # * closed upstream > tags 904125 + fixed-upstream Bug #904125 [src:qtbase-opensource-src] systemd: system startup stops unless root logs in in text mode Bug #898021 [src:qtbase-opensource-src] linux-image-4.16.0-1-amd64: kernel 4.16 infinite wait after dm login on ivy bridge and bay trail Bug #898092 [src:qtbase-opensource-src] sddm: takes extremely long time to start Ignoring request to alter tags of bug #904125 to the same tags previously set Ignoring request to alter tags of bug #898021 to the same tags previously set Ignoring request to alter tags of bug #898092 to the same tags previously set > usertags 904125 - status-In-Progress Usertags were: status-In-Progress. There are now no usertags set. > usertags 904125 + status-Closed resolution-Done There were no usertags set. Usertags are now: status-Closed resolution-Done. > thanks Stopping processing here. Please contact me if you need assistance. -- 898021: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898021 898092: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898092 904125: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904125 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
[bts-link] source package src:qtbase-opensource-src
# # bts-link upstream status pull for source package src:qtbase-opensource-src # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # https://bts-link-team.pages.debian.net/bts-link/ # user debian-bts-l...@lists.debian.org # remote status report for #898021 (http://bugs.debian.org/898021) # Bug title: linux-image-4.16.0-1-amd64: kernel 4.16 infinite wait after dm login on ivy bridge and bay trail # * https://bugreports.qt.io/browse/QTBUG-69555 # * remote status changed: In-Progress -> Closed # * remote resolution changed: (?) -> Done # * closed upstream tags 898021 + fixed-upstream usertags 898021 - status-In-Progress usertags 898021 + status-Closed resolution-Done # remote status report for #898092 (http://bugs.debian.org/898092) # Bug title: sddm: takes extremely long time to start # * https://bugreports.qt.io/browse/QTBUG-69555 # * remote status changed: In-Progress -> Closed # * remote resolution changed: (?) -> Done # * closed upstream tags 898092 + fixed-upstream usertags 898092 - status-In-Progress usertags 898092 + status-Closed resolution-Done # remote status report for #904125 (http://bugs.debian.org/904125) # Bug title: systemd: system startup stops unless root logs in in text mode # * https://bugreports.qt.io/browse/QTBUG-69555 # * remote status changed: In-Progress -> Closed # * remote resolution changed: (?) -> Done # * closed upstream tags 904125 + fixed-upstream usertags 904125 - status-In-Progress usertags 904125 + status-Closed resolution-Done thanks
Re: Bug#987430: upgrade-reports: KDE Plasma without panels and without background after upgrade from Buster to Bullseye
Hi Malvin, > > > I have now upgraded three different machines from (fully updated) Buster > > > to Bullseye, and all three times KDE Plasma was not usable afterwards. And I have now tried the update myself, successfully: - install debian buster wit KDE desktop - log into plasma, play around - do as you suggested apt upgrade --without-new-pkgs && apt full-upgrade - reboot - log into plasma, this takes a bit of time in my VM, but at the end Plasma is running without visual glitches and errors. Are you sure you have rebooted after the update? And, the question is even more interesting now: > Do you know which set of packages you had installed? Which meta-package? Best Norbert -- PREINING Norbert https://www.preining.info Fujitsu Research + IFMGA Guide + TU Wien + TeX Live + Debian Dev GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13
