[neon] [Bug 415130] Lock and login screens: entering incorrect password or moving focus away breaks using return/enter key to submit password
https://bugs.kde.org/show_bug.cgi?id=415130 --- Comment #81 from WojtasJD --- (In reply to Bruno Santos from comment #80) > This is probably not related, but I'm having this issue on login with Plasma > 6 RC1 (sddm 0.20) in Neon Testing, anyone else testing it at the moment? > > After entering the password, Enter isn't recognized. I've just installed: - KDE neon Testing Edition with Plasma 6.0 RC1 (5.92.90) - default Wayland - KDE neon Unstable Edition with Plasma 6.1 dev (6.0.80) - default Wayland Full keyboard - middle doesn't work, right (NumPad) - is working. BTW: https://bugs.kde.org/show_bug.cgi?id=478875 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454639] amdgpu driver: Flickering in Wayland session after suspend without lock screen enabled
https://bugs.kde.org/show_bug.cgi?id=454639 WojtasJD changed: What|Removed |Added CC||wojta...@notowany.pl --- Comment #10 from WojtasJD --- I have similar issue with corrupted screen ( https://bugsfiles.kde.org/attachment.cgi?id=149347 ) in: - openSUSE 15.4, kernel 5.14.x and KDE Plasma 5.24.4 (installed on disk) - neon-user-20230420-0722.iso (kernel 5.19; KDE Plasma 5.27.4 ; with user "neon" logged out from X11 and logged in to Wayland live session) I have AMD Radeon HD 6570 (GPU name: TURKS, generation: Northern Islands) - with radeon driver; amdgpu does not support this card. In my case I don't need to suspend the machine, it is enough to switch from TTY1...6 (text login prompt) to TTY8 (Plasma) and screen is corrupted (with good mouse cursor). To 'repair' this I need to switch to TTY7 (SDDM) and back to TTY8 (Plasma). After repair, again switching to TTY1...6 (but not TTY7 (SDDM)) and back to TTY8 (Plasma) - screen is distorted (with good mouse cursor)... Same behavior with KDE neon (TTY numbers different). -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 464416] Disconnected panels cannot be reintegrated with the main application window
https://bugs.kde.org/show_bug.cgi?id=464416 --- Comment #2 from WojtasJD --- (In reply to Andrius Štikonas from comment #1) > Not a partition manager bug. That's Qt. Oops, I see, sorry. After further investigation - this issue occurs in Wayland session but not in X11 (in X11 docked and undocked windows have the same Float and Close controls). https://invent.kde.org/system/partitionmanager/-/issues/6 https://bugreports.qt.io/browse/QTBUG-87332 Thank you for your work! -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 464416] Disconnected panels cannot be reintegrated with the main application window
https://bugs.kde.org/show_bug.cgi?id=464416 WojtasJD changed: What|Removed |Added CC||wojta...@notowany.pl -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 464416] New: Disconnected panels cannot be reintegrated with the main application window
https://bugs.kde.org/show_bug.cgi?id=464416
Bug ID: 464416
Summary: Disconnected panels cannot be reintegrated with the
main application window
Classification: Applications
Product: partitionmanager
Version: 22.12.1
Platform: Archlinux
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: andr...@stikonas.eu
Reporter: wojta...@notowany.pl
Target Milestone: ---
Created attachment 155383
--> https://bugs.kde.org/attachment.cgi?id=155383=edit
partitionmanager with shown panels
SUMMARY
Cannot merge separated shown panels with the main application window and window
titles has "&" at the beginning ("", " Operations",
"", " Output")
STEPS TO REPRODUCE
1. Install and run KDE Partition Manager
2. Click resize icon on one or more shown panels (,
Operations, , Output)
OBSERVED RESULT
Panels are in separate windows with Minimize, Maximize and Close controls and
cannot be merged with the main KDE Partition Manager window.
Panels have window titles with a "&" at the beginning.
EXPECTED RESULT
Disconnected panels should have window controls to integrate with the main app
and window titles without special sign.
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch 6.1.6-arch1-1 (64-bit)
KDE Plasma Version: 5.26.5
KDE Frameworks Version: 5.102.0
Qt Version: 5.15.8
ADDITIONAL INFORMATION
Same problem:
https://www.reddit.com/r/kde/comments/xao3ou/in_kde_partition_manager_the_panels_are/
--
You are receiving this mail because:
You are watching all bug changes.
[partitionmanager] [Bug 464338] The existing volume label is not preserved after changing the file system from partition properties
https://bugs.kde.org/show_bug.cgi?id=464338 WojtasJD changed: What|Removed |Added CC||wojta...@notowany.pl -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 464338] New: The existing volume label is not preserved after changing the file system from partition properties
https://bugs.kde.org/show_bug.cgi?id=464338 Bug ID: 464338 Summary: The existing volume label is not preserved after changing the file system from partition properties Classification: Applications Product: partitionmanager Version: 22.12.1 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: andr...@stikonas.eu Reporter: wojta...@notowany.pl Target Milestone: --- SUMMARY The existing volume label is vanished after changing the file system from partition properties. STEPS TO REPRODUCE 1. Install and run KDE Partition Manager. 2. Create partition, choose file system (e.g. "ext2"), put a label (e.g. "test") and apply changes. 3. Go to partition properties, change the file system to e.g. "ext3" and apply changes. OBSERVED RESULT Existing label is not added to pending operations and created new file system has a blank label. EXPECTED RESULT Existing volume label should be preserved. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch 6.1.6-arch1-1 (64-bit) KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.101.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION - -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 464306] KDE Partition Manager crashes when trying format partition to f2fs
https://bugs.kde.org/show_bug.cgi?id=464306 WojtasJD changed: What|Removed |Added CC||wojta...@notowany.pl -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 464306] New: KDE Partition Manager crashes when trying format partition to f2fs
https://bugs.kde.org/show_bug.cgi?id=464306 Bug ID: 464306 Summary: KDE Partition Manager crashes when trying format partition to f2fs Classification: Applications Product: partitionmanager Version: 22.12.1 Platform: Archlinux OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: andr...@stikonas.eu Reporter: wojta...@notowany.pl Target Milestone: --- Created attachment 155301 --> https://bugs.kde.org/attachment.cgi?id=155301=edit (gdb) backtrace SUMMARY KDE Partition Manager crashes when trying format partition to f2fs STEPS TO REPRODUCE 1. Install partitionmanager and f2fs-tools packages 2. Launch KDE Partition Manager, select partition and in properties change file system to f2fs 3. Apply changes OBSERVED RESULT KDE Partition Manager crashes. (observed the same result on two different computers) EXPECTED RESULT KDE Partition Manager should create f2fs without terminating itself. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch 6.1.5-arch2-1 (64-bit) KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.101.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION f2fs-tools 1.15.0-2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 415130] Lock and login screens: entering incorrect password or moving focus away breaks using return/enter key to submit password
https://bugs.kde.org/show_bug.cgi?id=415130 --- Comment #28 from WojtasJD --- (In reply to Konrad Materka from comment #22) > Interesting. Maybe it is using different SDDM theme? Breeze (0.1) another example Feren OS 2020.01 (Plasma: 5.17.5 | Frameworks: 5.66.0 | Qt: 5.13.2) - this distro has LightDM instead of SDDM but also suffers from this bug after locking screen (you can wait... or manually with default combo + or from Konsole: "loginctl lock-session") (In reply to Nate Graham from comment #26) > If all of your machines are either Neon, or are otherwise running Qt 5.13.2, > then that makes sense, since we think this was a Qt 5.13.2 regression. Solus 4.1 with Plasma (Plasma: 5.17.5 | Frameworks: 5.66.0 | Qt: 5.13.2) - there is no bug here I can dig but what to look for? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 415130] Lock and login screens: entering incorrect password or moving focus away breaks using return/enter key to submit password
https://bugs.kde.org/show_bug.cgi?id=415130 WojtasJD changed: What|Removed |Added CC||wojta...@notowany.pl --- Comment #21 from WojtasJD --- KDE Neon User 5.17 (Plasma: 5.17.5 | Frameworks: 5.66.0 | Qt: 5.13.2) $ qmake -v QMake version 3.1 Using Qt version 5.13.2 in /usr/lib/x86_64-linux-gnu -> System is running -> Lock screen or Log out and then put your password and click with mouse left button in the password field -> left is NOT "working" but numeric/right is working. and now weird thing: Solus 4.1 with Plasma (Plasma: 5.17.5 | Frameworks: 5.66.0 | Qt: 5.13.2) I cannot reproduce this bug here... (but reported Qt version is the same as in Neon) $ sudo eopkg install qt5-base-devel $ qmake -v QMake version 3.1 Using Qt version 5.13.2 in /usr/lib64 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 407058] KDE Plasma5 can't change resolution in VM after last update
https://bugs.kde.org/show_bug.cgi?id=407058 WojtasJD changed: What|Removed |Added CC||wojta...@notowany.pl --- Comment #19 from WojtasJD --- Why this MAJOR bug is ignored? Host: Oracle VirtualBox 6.1.2 r135662 (Qt5.6.2) on Windows 7 X64 In VM settings as graphics controller is selected: VMSVGA (which is preferred for Linux guests): lspci -nnk | grep -i vga -A2 00:02.0 VGA compatible controller [0300]: VMware SVGA II Adapter [15ad:0405] Subsystem: VMware SVGA II Adapter [15ad:0405] Kernel driver in use: vmwgfx Kernel modules: vmwgfx Guest 1: openSUSE Tumbleweed 20200118 Plasma ver.: 5.17.5 KDE Frameworks: 5.66.0 Qt ver.: 5.13.1 Kernel: 5.4.10-1-default Arch: 64-bit Guest 2: Fedora 31 KDE Plasma Plasma ver.: 5.17.5 KDE Frameworks: 5.64.0 Qt ver.: 5.13.2 Kernel: 5.3.7-301.fc31.x86_64 Arch: 64-bit and another Plasma distros like KDE Neon 5.17 etc. Same issue - cannot change resolution from GUI (systemsettings5) or from terminal emulator with "xrandr" command. -- You are receiving this mail because: You are watching all bug changes.
[user-manager] [Bug 413377] Setting auto-login for a user does not change config files
https://bugs.kde.org/show_bug.cgi?id=413377 WojtasJD changed: What|Removed |Added CC||wojta...@notowany.pl --- Comment #1 from WojtasJD --- I can confirm this behavior on two machines with KDE neon 5.17.1 installed - in my case I cannot switch off auto-login for a user in "user-manager": 1. Issue this command from Konsole: $ kcmshell5 user_manager 2. Unset auto-login for a user 3. After entering password (ID: org.freedesktop.accounts.user-administration) Konsole throws this: QDBusArgument: read from a write-only object QDBusArgument: read from a write-only object QDBusArgument: read from a write-only object 4. After entering password (ID: org.kde.kcontrol.kcmsddm.save) Konsole throws this: Warning from helper: QFSFileEngine::open: No file name specified Warning from helper: Empty filename passed to function 5. Close and open "user-manager" - setting is not saved. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 412684] [Wayland] kwin_wayland[3904]: segfault at 10 ip 00007f35691b6c30 sp 00007ffcf514ce98 error 4 in libKF5WaylandServer.so.5.63.0[7f3569191000+60000]
https://bugs.kde.org/show_bug.cgi?id=412684 --- Comment #19 from WojtasJD --- KDE neon updated from 5.17 to 5.17.1 and logging to a Wayland session is working again - thanks. But there is another issue with killed keyboard & mouse after resuming from sleep, like this https://forums.opensuse.org/showthread.php/530065-KDE-Plasma-on-Wayland-no-mouse-and-keyboard-after-resume - but this is a case for another bug report... -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 412684] [Wayland] kwin_wayland[3904]: segfault at 10 ip 00007f35691b6c30 sp 00007ffcf514ce98 error 4 in libKF5WaylandServer.so.5.63.0[7f3569191000+60000]
https://bugs.kde.org/show_bug.cgi?id=412684 WojtasJD changed: What|Removed |Added CC||wojta...@notowany.pl -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 412684] [Wayland] kwin_wayland[3904]: segfault at 10 ip 00007f35691b6c30 sp 00007ffcf514ce98 error 4 in libKF5WaylandServer.so.5.63.0[7f3569191000+60000]
https://bugs.kde.org/show_bug.cgi?id=412684 --- Comment #11 from WojtasJD --- Before big update from KDE neon 5.16.5 to 5.17 logging to Wayland session worked fine but now freezes my computer (black screen, PC is not responsible), sometimes throws back to SDDM login screen and then "dmesg" is telling this: Oct 17 18:13:40 KDE kernel: [ 631.303567] show_signal_msg: 15 callbacks suppressed Oct 17 18:13:40 KDE kernel: [ 631.303570] kwin_wayland[5827]: segfault at 10 ip 7f5199bff110 sp 7fff9aa02618 error 4 in libKF5WaylandServer.so.5.63.0[7f5199b84000+fa000] Oct 17 18:13:40 KDE kernel: [ 631.303579] Code: 00 00 f3 c3 66 0f 1f 44 00 00 48 85 f6 74 0b 48 89 f7 e9 d3 94 fe ff 0f 1f 00 f3 c3 0f 1f 40 00 66 2e 0f 1f 84 00 00 00 00 00 <48> 8b 47 10 c3 90 66 2e 0f 1f 84 00 00 00 00 00 48 83 ec 08 e8 e7 -- KDE neon 5.17 -- Plasma: 5.17.0 Frameworks: 5.63.0 Qt: 5.13.1 Kernel: 5.0.0-29-generic Arch: 64-bit Card: Advanced Micro Devices [AMD/ATI] RV530 [Radeon X1600 XT/X1650 GTO] Display Server: X.Org 1.19.6 drivers: ati,radeon (unloaded: modesetting,fbdev,vesa) -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 412612] Enable autostart during startup - option is not saved
https://bugs.kde.org/show_bug.cgi?id=412612 --- Comment #9 from WojtasJD --- Created attachment 123041 --> https://bugs.kde.org/attachment.cgi?id=123041=edit Manjaro KDE neon 18.1.0 - Building "latte-dock" ver. 0.9.85 Manjaro KDE 18.1.0 - here autostart also works fine ;) [Plasma: 5.16.4; Frameworks: 5.61.0; Qt: 5.13.0] Build without problem, only some warnings about deprecated-declarations - file with build output attached. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 412612] Enable autostart during startup - option is not saved
https://bugs.kde.org/show_bug.cgi?id=412612 --- Comment #8 from WojtasJD --- Created attachment 123040 --> https://bugs.kde.org/attachment.cgi?id=123040=edit KDE neon 5.16.5 - Building "latte-dock" ver. 0.9.85 Of course I can check ;) TL;DR - autostart is working, now file org.kde.latte-dock.desktop is copied to ~/.config/autostart/ Thank you! (Latte is reporting itself ver. 0.9.85). "KDE neon 5.16.5" (two installations with Latte Dock build/configure problems): According to build instruction from https://github.com/KDE/latte-dock/blob/master/INSTALLATION.md I've installed dependencies: sudo apt install cmake extra-cmake-modules qtdeclarative5-dev libqt5x11extras5-dev libkf5iconthemes-dev libkf5plasma-dev libkf5windowsystem-dev libkf5declarative-dev libkf5xmlgui-dev libkf5activities-dev build-essential libxcb-util-dev libkf5wayland-dev git gettext libkf5archive-dev libkf5notifications-dev libxcb-util0-dev libsm-dev libkf5crash-dev libkf5newstuff-dev and: ---- wojtasjd@KDE:~$ git clone https://anongit.kde.org/latte-dock.git Cloning into 'latte-dock'... remote: Counting objects: 33586, done. remote: Compressing objects: 100% (12146/12146), done. remote: Total 33586 (delta 24994), reused 29019 (delta 21205) Receiving objects: 100% (33586/33586), 6.36 MiB | 4.30 MiB/s, done. Resolving deltas: 100% (24994/24994), done. wojtasjd@KDE:~$ cd latte-dock/ wojtasjd@KDE:~/latte-dock$ sh install.sh install.sh: 12: [: unexpected operator install.sh: 12: [: unexpected operator install.sh: 16: [: -a: unexpected operator install.sh: 22: [: -a: unexpected operator install.sh: 25: [: -a: unexpected operator install.sh: 29: [: unexpected operator install.sh: 32: [: unexpected operator -- The C compiler identification is GNU 7.4.0 -- The CXX compiler identification is GNU 7.4.0 -- Check for working C compiler: /usr/bin/cc -- Check for working C compiler: /usr/bin/cc -- works -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Detecting C compile features -- Detecting C compile features - done -- Check for working CXX compiler: /usr/bin/c++ -- Check for working CXX compiler: /usr/bin/c++ -- works -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- Detecting CXX compile features -- Detecting CXX compile features - done -- Could NOT find KF5SysGuard (missing: KF5SysGuard_DIR) -- Could NOT find KF5SysGuard: found neither KF5SysGuardConfig.cmake nor kf5sysguard-config.cmake CMake Error at /usr/share/cmake-3.10/Modules/FindPackageHandleStandardArgs.cmake:137 (message): Could NOT find KF5 (missing: SysGuard) Call Stack (most recent call first): /usr/share/cmake-3.10/Modules/FindPackageHandleStandardArgs.cmake:378 (_FPHSA_FAILURE_MESSAGE) /usr/share/ECM/find-modules/FindKF5.cmake:110 (find_package_handle_standard_args) CMakeLists.txt:22 (find_package) -- Configuring incomplete, errors occurred! See also "/home/wojtasjd/latte-dock/build/CMakeFiles/CMakeOutput.log". wojtasjd@KDE:~/latte-dock$ wojtasjd@KDE:~/latte-dock$ sh install.sh install.sh: 12: [: unexpected operator install.sh: 12: [: unexpected operator install.sh: 16: [: -a: unexpected operator mkdir: nie można utworzyć katalogu „build”: Plik istnieje wojtasjd@KDE:~/latte-dock$ wojtasjd@KDE:~/latte-dock$ which sh /bin/sh wojtasjd@KDE:~/latte-dock$ file /bin/sh /bin/sh: symbolic link to dash wojtasjd@KDE:~/latte-dock$ file /bin/dash /bin/dash: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/l, for GNU/Linux 3.2.0, BuildID[sha1]=a783260e3a5fe0afdae77417eea7fbf8d645219e, stripped wojtasjd@KDE:~/latte-dock$ ./install.sh -- Could NOT find KF5SysGuard (missing: KF5SysGuard_DIR) -- Could NOT find KF5SysGuard: found neither KF5SysGuardConfig.cmake nor kf5sysguard-config.cmake CMake Error at /usr/share/cmake-3.10/Modules/FindPackageHandleStandardArgs.cmake:137 (message): Could NOT find KF5 (missing: SysGuard) Call Stack (most recent call first): /usr/share/cmake-3.10/Modules/FindPackageHandleStandardArgs.cmake:378 (_FPHSA_FAILURE_MESSAGE) /usr/share/ECM/find-modules/FindKF5.cmake:110 (find_package_handle_standard_args) CMakeLists.txt:22 (find_package) -- Configuring incomplete, errors occurred! See also "/home/wojtasjd/latte-dock/build/CMakeFiles/CMakeOutput.log". wojtasjd@KDE:~/latte-dock$ So I propose updating build instruction to also add this dependencies: libkf5sysguard-dev , pkg-config Executing "sh install.sh" throw some errors but simply "./install.sh" works fine. Beside "pkg-config" there was some other "Could NOT find" messages - I've attached file with build output. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 412612] Enable autostart during startup - option is not saved
https://bugs.kde.org/show_bug.cgi?id=412612 --- Comment #3 from WojtasJD --- Thanks for reply. It's weird - I've installed another fresh KDE neon 5.16.5 + Latte 0.9.3 and here autostart option is working fine. I've installed also Kubuntu 19.04 (Plasma: 5.15.4, Frameworks: 5.56.0, Qt: 5.12.2) + Latte 0.8.8 and here autostart option is also working fine! But in other three installations [fresh KDE neon 5.16.5 + Latte 0.9.3 (virtual machine) ; another KDE neon 5.16.5 + Latte 0.9.3 (bare metal) ; Manjaro 18.1.0 + Latte 0.9.1 (virtual machine): - org.kde.latte-dock.desktop file doesn't appear in ~/.config/autostart/ if I click autostart option (+ Apply) - there is a file /usr/share/applications/org.kde.latte-dock.desktop (both "KDE neon" and "Manjaro KDE") - I did small experiment with steps as follows: 1. I've manually copied file /usr/share/applications/org.kde.latte-dock.desktop -> ~/.config/autostart/ 2. After launching Latte, in settings autostart option is marked 3. Rebooted system, Latte Dock is auto-starting 4. In settings I've unchecked autostart option (+ Apply) and then ~/.config/autostart/org.kde.latte-dock.desktop file was deleted (as expected) 5. Marked autostart option (+ Apply) and then in folder ~/.config/autostart/ file was NOT created Additional steps on this machines doesn't help: - latte-dock uninstall - delete file: ~/.config/lattedockrc - delete folder: ~/.config/latte - delete folder: ~/.cache/lattedock - latte-dock new install -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 412612] New: Enable autostart during startup - option is not saved
https://bugs.kde.org/show_bug.cgi?id=412612 Bug ID: 412612 Summary: Enable autostart during startup - option is not saved Product: lattedock Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: wojta...@notowany.pl Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Install KDE neon 5.16.5 or Manjaro KDE 18.1.0 2. Install latte-dock 0.9.2 or 0.9.3 (KDE neon) or 0.9.1 (Manjaro) 3. Run Latte Dock and go to Dock Settings -> Settings -> Preferences and mark under Behavior "Enable autostart during startup" -> Apply and OK OBSERVED RESULT Marking "Enable autostart during startup" option is not saved (if you go again to Settings... option is unmarked) and therefore during next session Latte is not launched. EXPECTED RESULT Save "Enable autostart during startup" option. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE neon 5.16.5 x64 | Manjaro KDE 18.1.0 x64 KDE Plasma Version: 5.16.5 | 5.16.4 KDE Frameworks Version: 5.62.0 | 5.61.0 Qt Version: 5.12.3 | 5.13.0 ADDITIONAL INFORMATION There is a folder: ~/.config/autostart Launching Latte from terminal emulator: latte-dock --cc doesn't help Another person with this behavior: https://forum.manjaro.org/t/new-to-kde-i-have-question/104312 -- You are receiving this mail because: You are watching all bug changes.
