[valgrind] [Bug 400793] pthread_rwlock_timedwrlock false positive
https://bugs.kde.org/show_bug.cgi?id=400793 Paul Floyd changed: What|Removed |Added Resolution|--- |FIXED Status|REOPENED|RESOLVED --- Comment #5 from Paul Floyd --- That's how Helgrind works. The original problem (missing intercepts) was fixed. If you think that Helgrind shouldn't report timeouts, please open a separate bugzilla item. -- You are receiving this mail because: You are watching all bug changes.
[Spam] [Bug 467088] MOT Leamington Spa
https://bugs.kde.org/show_bug.cgi?id=467088 Paul Worrall changed: What|Removed |Added Assignee|forum-ad...@kde.org |n...@kde.org Product|forum.kde.org |Spam Component|general |Spam CC||p.r.worr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[KClock] [Bug 467093] New: Cannot add locations for clocks in KClock...
https://bugs.kde.org/show_bug.cgi?id=467093 Bug ID: 467093 Summary: Cannot add locations for clocks in KClock... Classification: Applications Product: KClock Version: unspecified Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: espi...@gmail.com Reporter: ben2t...@yahoo.com CC: hanyo...@protonmail.com Target Milestone: --- SUMMARY *** Unable to add specific clock. *** STEPS TO REPRODUCE 1. Select `+ Add` 2. Try to set a clock for New Zealand, Aukland. Try to search for `kidderminster` (UK town). 3. No results appear - unable to add clock for New Zealand. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 466046] Multiple Monitors with matching names cannot be told apart under Display Configuration applet.
https://bugs.kde.org/show_bug.cgi?id=466046 David Redondo changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 467090] Maps Window with Google Maps only empty
https://bugs.kde.org/show_bug.cgi?id=467090 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com --- Comment #4 from caulier.gil...@gmail.com --- yes QtWebkit is cross compiled with MXE. QtWebEngine do not yet support cross compilation (it's also true for ARM platform, even if Apple Silicon start to be supported with Qt6). I hope this situation will be better in the future... -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 467094] New: Typeset using LaTeX option need to be disabled and enabled again every time
https://bugs.kde.org/show_bug.cgi?id=467094 Bug ID: 467094 Summary: Typeset using LaTeX option need to be disabled and enabled again every time Classification: Applications Product: cantor Version: 22.12.3 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: maxima-backend Assignee: cantor-b...@kde.org Reporter: stefano.cro...@alice.it Target Milestone: --- I'm using the Maxima backend and I have LaTeX typesetting enabled in Cantor settings. In the Worksheet/Settings menu, the "Typeset using LaTeX" option is enabled. However, when I evaluate an entry, the result is not typeset using LaTeX. If I disable the "Typeset using LaTeX" option in the menu, then enable it again, LaTeX typesetting starts working and keeps going (for that worksheet) until I exit Cantor. I'm not sure whether this issue is specific to the Maxima backend or not, since of all backends I have, only Maxima seems to support the "Typeset using LaTeX" options (the other backends are: Qalculate, KAlgebra and Lua) -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 467095] New: Kate crash when undoing
https://bugs.kde.org/show_bug.cgi?id=467095 Bug ID: 467095 Summary: Kate crash when undoing Classification: Applications Product: kate Version: 22.12.3 Platform: Archlinux OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: 1sk8p...@anonaddy.me Target Milestone: --- Application: kate (22.12.3) Qt Version: 5.15.8 Frameworks Version: 5.103.0 Operating System: Linux 6.2.1-arch1-1 x86_64 Windowing System: Wayland Distribution: Arch Linux DrKonqi: 5.27.2 [KCrashBackend] -- Information about the crash: I had accidentally deleted all the text in a tab and decided to do CTRL+Z to undo but it just crashed the application. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Kate (kate), signal: Segmentation fault [KCrash Handler] #4 0x7fe8c553d329 in ?? () from /usr/lib/libKF5TextEditor.so.5 #5 0x7fe8c5546e3e in KateUndoManager::undo() () from /usr/lib/libKF5TextEditor.so.5 #6 0x7fe8c60bec20 in ?? () from /usr/lib/libQt5Core.so.5 #7 0x7fe8c6d6bec7 in QAction::triggered(bool) () from /usr/lib/libQt5Widgets.so.5 #8 0x7fe8c6d718c7 in QAction::activate(QAction::ActionEvent) () from /usr/lib/libQt5Widgets.so.5 #9 0x7fe8c6d7198e in QAction::event(QEvent*) () from /usr/lib/libQt5Widgets.so.5 #10 0x7fe8c6d78b5c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #11 0x7fe8c608df48 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 #12 0x7fe8c6573fad in QShortcutMap::dispatchEvent(QKeyEvent*) () from /usr/lib/libQt5Gui.so.5 #13 0x7fe8c656a817 in QShortcutMap::tryShortcut(QKeyEvent*) () from /usr/lib/libQt5Gui.so.5 #14 0x7fe8c652a038 in QWindowSystemInterface::handleShortcutEvent(QWindow*, unsigned long, int, QFlags, unsigned int, unsigned int, unsigned int, QString const&, bool, unsigned short) () from /usr/lib/libQt5Gui.so.5 #15 0x7fe8c653f972 in QGuiApplicationPrivate::processKeyEvent(QWindowSystemInterfacePrivate::KeyEvent*) () from /usr/lib/libQt5Gui.so.5 #16 0x7fe8c6528885 in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () from /usr/lib/libQt5Gui.so.5 #17 0x7fe8c0f5eb05 in ?? () from /usr/lib/libQt5WaylandClient.so.5 #18 0x7fe8c3b1682b in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #19 0x7fe8c3b6dcc9 in ?? () from /usr/lib/libglib-2.0.so.0 #20 0x7fe8c3b150e2 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #21 0x7fe8c60d8c6c in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #22 0x7fe8c60866ec in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #23 0x7fe8c6091219 in QCoreApplication::exec() () from /usr/lib/libQt5Core.so.5 #24 0x55abaa8945d5 in ?? () #25 0x7fe8c583c790 in ?? () from /usr/lib/libc.so.6 #26 0x7fe8c583c84a in __libc_start_main () from /usr/lib/libc.so.6 #27 0x55abaa896af5 in ?? () [Inferior 1 (process 16584) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 467090] Maps Window with Google Maps only empty
https://bugs.kde.org/show_bug.cgi?id=467090 --- Comment #5 from caulier.gil...@gmail.com --- my MXE environment have been fully recompiled on 15 November 2022. Gilles -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465536] Desktop icons disappear on wake up from sleep
https://bugs.kde.org/show_bug.cgi?id=465536 --- Comment #20 from Valerio Galdo --- Hi, i don't think it's the same bug, because i can't see any files on folderview also with a new installation of kde neon. My icons doesn't disapperar after a wakeup from sleep. And if i change from folderview to desktopview and come back to folderview, then all works. Il gio 9 mar 2023, 08:44 Pawel ha scritto: > https://bugs.kde.org/show_bug.cgi?id=465536 > > Pawel changed: > >What|Removed |Added > > >See Also|| > https://bugs.kde.org/show_b >||ug.cgi?id=467092 > > -- > You are receiving this mail because: > You are on the CC list for the bug. -- You are receiving this mail because: You are watching all bug changes.
[karbon] [Bug 426801] Karbon crashed after tried to "select all" the items
https://bugs.kde.org/show_bug.cgi?id=426801 f...@fellr.net changed: What|Removed |Added CC||f...@fellr.net -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 467096] New: VPN connections set to ask for a password do not offer to enter a password anymore
https://bugs.kde.org/show_bug.cgi?id=467096 Bug ID: 467096 Summary: VPN connections set to ask for a password do not offer to enter a password anymore Classification: Plasma Product: plasma-nm Version: 5.27.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: applet Assignee: plasma-b...@kde.org Reporter: trav...@redhat.com Target Milestone: --- SUMMARY Requesting activation of a VPN connection that requires a password to be entered manually each time you connect fails to offer a password entry dialog. In the logs: ``` Mar 09 10:05:54 phoenix plasmashell[1748]: QDBusObjectPath: invalid path "" ... Mar 09 10:03:00 phoenix systemsettings[8651]: QDBusObjectPath: invalid path "" ``` STEPS TO REPRODUCE 1. Setup a VPN connection that require manually entering a password each time you try to connect 2. Click to activate the connection in the applet or the settings panel OBSERVED RESULT No dialog show up to enter password EXPECTED RESULT A dialog to enter the password SOFTWARE/OS VERSIONS Operating System: Fedora Linux 37 KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.1.14-200.fc37.x86_64 (64-bit) Graphics Platform: Wayland ADDITIONAL INFORMATION Looks like a regression from 5.27.2 has this used to work a couple of days ago (I use that functionality almost daily). -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 466217] System monitor crashed when opening the Processes page
https://bugs.kde.org/show_bug.cgi?id=466217 Sergey changed: What|Removed |Added CC||rion...@gmail.com --- Comment #1 from Sergey --- I just had a crash with very similar trace in kwin_x11 and before that plasmashell also crashed on QGuiApplication::topLevelWindows() -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 467097] New: Welcome: select multiple files from "Recent Documents and Projects"
https://bugs.kde.org/show_bug.cgi?id=467097 Bug ID: 467097 Summary: Welcome: select multiple files from "Recent Documents and Projects" Classification: Applications Product: kate Version: 22.12.3 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: fisc...@unix-ag.uni-kl.de Target Milestone: --- When starting Kate, a special page to welcome the user is shown and a list of recent documents is presented. Currently, only a single recently opened file can selected to be opened, but it would be nice to select several files at once to be opened. Related, the list is vertically quite narrow, showing only the last 8 files without scrolling. On a large desktop screen however, there is much empty (unused) space around the welcome widgets. The layout should make better use of the available space on large screens. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 467087] Unable to start Valgrind due to error (MMAP)
https://bugs.kde.org/show_bug.cgi?id=467087 Paul Floyd changed: What|Removed |Added CC||pjfl...@wanadoo.fr --- Comment #1 from Paul Floyd --- That's not a lot to go on. Can you give more details of the application that you are testing? The patch has been applied. Your application is trying to use more memory than the threshold. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 467096] VPN connections set to ask for a password do not offer to enter a password anymore
https://bugs.kde.org/show_bug.cgi?id=467096 Timothée Ravier changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |MOVED --- Comment #1 from Timothée Ravier --- Looks like the plasma-kded service crashed and restarting it did the trick: ``` systemctl --user restart plasma-kded.service ``` Sorry for the noise. Will file another bug for the crash. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 467098] New: Allow user to mount LUKS drives without sudo permission
https://bugs.kde.org/show_bug.cgi?id=467098 Bug ID: 467098 Summary: Allow user to mount LUKS drives without sudo permission Classification: I don't know Product: kde Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: amanita+kdeb...@mailbox.org Target Milestone: --- SUMMARY KDE allows storing LUKS passwords in Kwallet. Its the users wallet with the users password. But when trying to mount a LUKS drive, you need sudo permissions, which makes no sense. STEPS TO REPRODUCE 1. Attach a USB LUKS drive 2. Enter the password, let it store in KWallet 3. unmount the LUKS drive, mount again OBSERVED RESULT You need to press "Enter" to confirm the password, and you need the sudo password. EXPECTED RESULT Password prompt opens where you have to only press enter. This should be removed and used only when the password is wrong. Also you need the sudo password to mount the drive. SOFTWARE/OS VERSIONS Operating System: Fedora Linux 37 (Kinoite, OSTree) KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.1.14-200.fc37.x86_64 (64-bit) PROPOSED SOLUTION add something like that: bash echo "$USER ALL=(ALL) NOPASSWD: /usr/bin/mount" | sudo tee -a /etc/sudoers.d/mount ADDITION This is not a duplicate of https://bugs.kde.org/show_bug.cgi?id=395300 This may be a solution for https://bugs.kde.org/show_bug.cgi?id=466731 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 467098] Allow user to mount LUKS drives without sudo permission
https://bugs.kde.org/show_bug.cgi?id=467098 --- Comment #1 from Henning --- Comment: Linux Mint seems to have that rule, LUKS drives mount fully automatic -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 467038] kde-baseapps package was removed from system after an update
https://bugs.kde.org/show_bug.cgi?id=467038 Carlos De Maine changed: What|Removed |Added CC||carlosdema...@gmail.com --- Comment #6 from Carlos De Maine --- Hi.. Updated packages are coming through the build system. Unfortunately you tried to upgrade while the packages that depend on libjpeg-turbo were rebuilding to satisfy the new dependencies. Please never accept the removal of any packages and wait for the corrected/rebuilt packages to come down the line. Cheers -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 467099] New: rendering crash missing ID3
https://bugs.kde.org/show_bug.cgi?id=467099 Bug ID: 467099 Summary: rendering crash missing ID3 Classification: Applications Product: kdenlive Version: 22.12.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: robert.gro...@gmx.de Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Render Video to any format (tried a few) 2. works until 536 3. rendering crashes OBSERVED RESULT crash error report: Discarding ID3 tags because more suitable tags were found EXPECTED RESULT rending SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Ubuntu 22.04.2 LTS (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Also crashes if I like to play my project in Kdenlive. Also crashes if I like to start a new project and like to add files to my project folder. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 467099] rendering crash missing ID3
https://bugs.kde.org/show_bug.cgi?id=467099 --- Comment #1 from Robert --- Created attachment 157139 --> https://bugs.kde.org/attachment.cgi?id=157139&action=edit screen copy rendering -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 467100] New: Primary Screen should be indexed 0
https://bugs.kde.org/show_bug.cgi?id=467100 Bug ID: 467100 Summary: Primary Screen should be indexed 0 Classification: Plasma Product: kwin Version: 5.26.2 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: multi-screen Assignee: kwin-bugs-n...@kde.org Reporter: ad...@arkades.org Target Milestone: --- SUMMARY Window rules that want to keep specific windows on primary screen are impossible to define on changing-display setups (eg notebook with multiple screens at the office, but single screen outdoors) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 467100] Primary Display should be indexed 0
https://bugs.kde.org/show_bug.cgi?id=467100 Dominik Kummer changed: What|Removed |Added Summary|Primary Screen should be|Primary Display should be |indexed 0 |indexed 0 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 459174] okular crashes after signature checking
https://bugs.kde.org/show_bug.cgi?id=459174 Syiad changed: What|Removed |Added Resolution|FIXED |--- Status|NEEDSINFO |REPORTED --- Comment #7 from Syiad --- I suppose this has been marked as FIXED by mistake. I didn't see any info on how this has been resolved. --> Changed back to REPORTED. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 467100] Primary Display should be indexed 0
https://bugs.kde.org/show_bug.cgi?id=467100 --- Comment #1 from Dominik Kummer --- PS: especially if additional displays are positioned lefthand from primary display. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 459174] okular crashes after signature checking
https://bugs.kde.org/show_bug.cgi?id=459174 Oliver Sander changed: What|Removed |Added CC||oliver.san...@tu-dresden.de --- Comment #8 from Oliver Sander --- Without having tried this myself: There has been a great number of bug reports similar to this one, and they have all been solved by updating to newer versions. Please try to get the latest flatpack version of Okular or build it from source and report back if the bug is still there. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 467099] rendering crash missing ID3
https://bugs.kde.org/show_bug.cgi?id=467099 --- Comment #2 from Robert --- Created attachment 157140 --> https://bugs.kde.org/attachment.cgi?id=157140&action=edit Playing crashes -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 467101] New: Corrupted KCrash files appear in home directory
https://bugs.kde.org/show_bug.cgi?id=467101 Bug ID: 467101 Summary: Corrupted KCrash files appear in home directory Classification: I don't know Product: kde Version: unspecified Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: ha51w...@anonaddy.me Target Milestone: --- SUMMARY Some time after updating to 5.27, a lot of files with corrupted filenames appeared. Some of them only have corrupted symbols in them but most look like this: [KCrash] exe=*corrupted characters* appname=*corrupted characters* apppath=*corrupted characters* signal=11 pid=4365 When going into the DrKonqi intensive care application to look at crashed processes, there are a lot of baloo_file_extractor entries. The time where it crashed corresponds to the time where the corrupted file was created. STEPS TO REPRODUCE I'm not really sure. It happened after updating to 5.27, just like in this reddit post: https://lr.mint.lgbt/r/kde/comments/116ss8x/files_with_strange_names_generated_in_home_after/?sort=new The issue of the poster is exactly the same as mine. OBSERVED RESULT A lot of files with corrupted names in /home/ EXPECTED RESULT No corrupted files in /home/ (baloo not crashing would also be great) SOFTWARE/OS VERSIONS Linux/KDE Plasma: 6.2.2-arch1-1 KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 KCrash version: kcrash-5.103.0-1 Baloo version: baloo-5.103.0-1 ADDITIONAL INFORMATION In the comment of the previously mentioned post someone mentioned that not doing an offline update might be the cause but at least for me, this issue is still present even after multiple restarts and daily use. There are the same kcrash files with corrupted entries in "~/.cache/kcrash-metadata/", however in this case they have non corrupted filenames (like 10020.ini). I'm not sure what exactly is causing this. In case it helps here is a backtrace of the latest time /usr/lib/baloo_file_extractor crashed: #0 __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:76 #1 0x7f1473a72ba1 in __printf_buffer (buf=buf@entry=0x7ffd2da5dd40, format=format@entry=0x7f1474cec176 "%s ", ap=ap@entry=0x7ffd2da5de40, mode_flags=mode_flags@entry=2) at /usr/src/debug/glibc/glibc/stdio-common/vfprintf-process-arg.c:423 #2 0x7f1473a7311a in __vfprintf_internal (s=0x7f1473bf24c0 <_IO_2_1_stderr_>, format=0x7f1474cec176 "%s ", ap=ap@entry=0x7ffd2da5de40, mode_flags=2) at vfprintf-internal.c:1474 #3 0x7f1473b2f1d3 in ___fprintf_chk (fp=, flag=, format=) at fprintf_chk.c:33 #4 0x7f1474ceb31a in fprintf (__fmt=0x7f1474cec176 "%s ", __stream=) at /usr/include/bits/stdio2.h:79 #5 KCrash::defaultCrashHandler (sig=11) at /usr/src/debug/kcrash/kcrash-5.103.0/src/kcrash.cpp:575 #6 #7 0x7f1474e9e325 in wl_map_insert_at (map=map@entry=0x564715cfd8f0, flags=flags@entry=1, i=23, data=) at ../wayland-1.21.0/src/wayland-util.c:276 #8 0x7f1474e9e483 in proxy_destroy (proxy=proxy@entry=0x564715d59110) at ../wayland-1.21.0/src/wayland-client.c:510 #9 0x7f1474ea0020 in wl_proxy_destroy_caller_locks (proxy=0x564715d59110) at ../wayland-1.21.0/src/wayland-client.c:530 #10 wl_proxy_marshal_array_flags (proxy=proxy@entry=0x564715d59110, opcode=opcode@entry=0, interface=interface@entry=0x0, version=version@entry=1, flags=flags@entry=1, args=args@entry=0x7ffd2da5ec20) at ../wayland-1.21.0/src/wayland-client.c:868 #11 0x7f1474ea0afa in wl_proxy_marshal_flags (proxy=0x564715d59110, opcode=0, interface=0x0, version=1, flags=1) at ../wayland-1.21.0/src/wayland-client.c:791 #12 0x7f146e50d603 in org_kde_kwin_idle_timeout_release (org_kde_kwin_idle_timeout=0x564715d59110) at /usr/src/debug/kidletime/build/src/plugins/wayland/wayland-idle-client-protocol.h:208 #13 QtWayland::ext_idle_notification_v1::destroy (this=0x564715d46f10) at /usr/src/debug/kidletime/build/src/plugins/wayland/qwayland-ext-idle-notify-v1.cpp:134 #14 IdleTimeoutExt::~IdleTimeoutExt (this=, this=) at /usr/src/debug/kidletime/kidletime-5.103.0/src/plugins/wayland/poller.cpp:77 #15 IdleTimeoutExt::~IdleTimeoutExt (this=, this=) at /usr/src/debug/kidletime/kidletime-5.103.0/src/plugins/wayland/poller.cpp:78 #16 0x7f146e50d38b in QtSharedPointer::ExternalRefCountData::destroy (this=0x564715d59250) at /usr/include/qt/QtCore/qsharedpointer_impl.h:149 #17 QSharedPointer::deref (dd=0x564715d59250) at /usr/include/qt/QtCore/qsharedpointer_impl.h:458 #18 QSharedPointer::deref (dd=0x564715d59250) at /usr/include/qt/QtCore/qsharedpointer_impl.h:454 #19 QSharedPointer::deref (this=) at /usr/include/qt/QtCore/qsharedpointer_impl.h:453 #20 QSharedPointer::~QSharedPointer (this=, this=) at /usr/include/qt/QtCore/qsharedpointer_impl.h:310 #21 QHashNode >::~QHashNode (this=, this=) at /usr/include/qt/QtCore/qhash.h:147
[plasmashell] [Bug 422111] Battery applet not showing up in tray.
https://bugs.kde.org/show_bug.cgi?id=422111 Vitor M. Pereira changed: What|Removed |Added CC||vmper...@fc.up.pt -- You are receiving this mail because: You are watching all bug changes.
[Spam] [Bug 467088] MOT Leamington Spa
https://bugs.kde.org/show_bug.cgi?id=467088 Ben Cooksley changed: What|Removed |Added URL|https://www.tyrefitauto.co. | |uk/ | -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 447029] Konsole no longer (or) incorrectly use GTK theme
https://bugs.kde.org/show_bug.cgi?id=447029 --- Comment #4 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/frameworks/kconfigwidgets/-/merge_requests/187 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467102] New: Plasmashell crashes/hangs every time when editing toolbar
https://bugs.kde.org/show_bug.cgi?id=467102 Bug ID: 467102 Summary: Plasmashell crashes/hangs every time when editing toolbar Classification: Plasma Product: plasmashell Version: 5.24.4 Platform: openSUSE OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: Edit Mode toolbar Assignee: plasma-b...@kde.org Reporter: obe...@web.de Target Milestone: 1.0 Created attachment 157141 --> https://bugs.kde.org/attachment.cgi?id=157141&action=edit Crash with debug-symbols SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Start current opensuse-stable-distro, intel+nvidia geforce hardware, nouveau, wayland, plasma 2. login with ssdm as user 3. Edit toolbar -> plasmashell hangs or crashes instantly, always OBSERVED RESULT plasmashell hangs or crashes instantly, always EXPECTED RESULT No crash, Toolbar can be edited. This only happens on Wayland, not on X11 SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kernel 5.14.21-150400.24.46-default #1 SMP PREEMPT_DYNAMIC Thu Feb 9 08:38:18 UTC 2023 (2d95137) x86_64 x86_64 x86_64 GNU/Linux KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION This only happens on Wayland, not on X11 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467102] Plasmashell crashes/hangs every time when editing toolbar (only Wayland affected)
https://bugs.kde.org/show_bug.cgi?id=467102 Daniel changed: What|Removed |Added Summary|Plasmashell crashes/hangs |Plasmashell crashes/hangs |every time when editing |every time when editing |toolbar |toolbar (only Wayland ||affected) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 452660] Random Plasma crashes caused by `reuseItems: true` in DelegateModel
https://bugs.kde.org/show_bug.cgi?id=452660 --- Comment #8 from Fushan Wen --- Git commit af51f8e0529f8db0b5612a15830adba53cfa900b by Fushan Wen. Committed on 09/03/2023 at 10:28. Pushed by fusionfuture into branch 'master'. applets/taskmanager: remove workaround for QTBUG-102811 It's no longer reproducible with 3ba196eddc8c37bc56a799a8189c18a4da550a4c because the loader will unload the model when the current tooltip type changes. M +3-10 applets/taskmanager/package/contents/ui/ToolTipDelegate.qml https://invent.kde.org/plasma/plasma-desktop/commit/af51f8e0529f8db0b5612a15830adba53cfa900b -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 467101] Corrupted KCrash files appear in home directory
https://bugs.kde.org/show_bug.cgi?id=467101 Bug Janitor Service changed: What|Removed |Added Severity|normal |crash -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467102] Plasmashell crashes/hangs every time when editing toolbar (only Wayland affected)
https://bugs.kde.org/show_bug.cgi?id=467102 Bug Janitor Service changed: What|Removed |Added Resolution|--- |DOWNSTREAM Status|REPORTED|RESOLVED --- Comment #1 from Bug Janitor Service --- Thank you for the bug report! However Plasma 5.24.4 is no longer eligible for support or maintenance from KDE; supported versions are 5.27, and 5.27 or newer. Please upgrade to a supported version as soon as your distribution makes it available to you. Plasma is a fast-moving project, and bugs in one version are often fixed in the next one. If you need support for Plasma 5.24.4, please contact your distribution, who bears the responsibility of providing support for older releases that are no longer supported by KDE. If you can reproduce the issue after upgrading to a supported version, feel free to re-open this bug report. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 464044] Could not find plugin kcm_kdeconnect
https://bugs.kde.org/show_bug.cgi?id=464044 Albert Vaca changed: What|Removed |Added Resolution|--- |FIXED CC||albertv...@gmail.com Status|REPORTED|RESOLVED --- Comment #2 from Albert Vaca --- Sorry for the delay folks, this has been fixed in the last nightly build: https://binary-factory.kde.org/view/MacOS/job/kdeconnect-kde_Nightly_macos/ -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 464231] KDE Connect for Mac OS no longer works after updating to latest version
https://bugs.kde.org/show_bug.cgi?id=464231 Albert Vaca changed: What|Removed |Added Status|CONFIRMED |RESOLVED CC||albertv...@gmail.com Resolution|--- |FIXED --- Comment #9 from Albert Vaca --- Sorry for the delay folks, this has been fixed in the last nightly build: https://binary-factory.kde.org/view/MacOS/job/kdeconnect-kde_Nightly_macos/ -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464996] Resurrection of bug 422111 with upower 0.99.14 or later
https://bugs.kde.org/show_bug.cgi?id=464996 Méven Car changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 CC||meve...@gmail.com --- Comment #8 from Méven Car --- I reproduce the issue on 5.27.2 with kernel 5.19 and upower 0.99.20 (kubuntu) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466020] With multimonitor set-up (hidpi laptop + 2 displays with different sizes and resolutions via usb-c dock) one screen always has an invisible containment with a black backgrou
https://bugs.kde.org/show_bug.cgi?id=466020 --- Comment #6 from Marco Martin --- Another explanation is everything being "correct" and the desktop window being there, but it has been failed to be moved with the plasma protocol? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466020] With multimonitor set-up (hidpi laptop + 2 displays with different sizes and resolutions via usb-c dock) one screen always has an invisible containment with a black backgrou
https://bugs.kde.org/show_bug.cgi?id=466020 --- Comment #7 from Marco Martin --- if you add a panel in the screen that usually stays darl, then restarting is the panel visible even if not the desktop? -- You are receiving this mail because: You are watching all bug changes.
[filelight] [Bug 467103] New: filelight crashes repeatedly after /home has no space to crash
https://bugs.kde.org/show_bug.cgi?id=467103
Bug ID: 467103
Summary: filelight crashes repeatedly after /home has no space
to crash
Classification: Applications
Product: filelight
Version: 22.12.3
Platform: Archlinux
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: unassigned-b...@kde.org
Reporter: unknowndev...@pm.me
CC: martin.sandsm...@kde.org
Target Milestone: ---
Application: filelight (22.12.3)
Qt Version: 5.15.8
Frameworks Version: 5.103.0
Operating System: Linux 6.2.2-zen1-1-zen x86_64
Windowing System: X11
Distribution: "Arch Linux"
DrKonqi: 5.27.2 [KCrashBackend]
-- Information about the crash:
Filling up /home for some unforeseen reason caused filelight to crash, and then
it kept crashing.
The crash can be reproduced every time.
-- Backtrace:
Application: Filelight (filelight), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = 0x0}
[KCrash Handler]
#6
QV4::CompiledData::TypeReferenceMap::collectFromObject
(obj=0x7f9aadec201c, this=0x7f9a9c203eb8) at
/usr/include/qt/QtCore/qendian.h:290
#7 QQmlTypeData::tryLoadFromDiskCache (this=0x7f9a9c203e10) at
/usr/src/debug/qt5-declarative/qtdeclarative/src/qml/qml/qqmltypedata.cpp:162
#8 0x7f9abe221bc5 in QQmlTypeData::dataReceived (this=0x7f9a9c203e10,
data=...) at
/usr/src/debug/qt5-declarative/qtdeclarative/src/qml/qml/qqmltypedata.cpp:574
#9 0x7f9abe2647db in QQmlTypeLoader::setData
(this=this@entry=0x557221f422b8, blob=blob@entry=0x7f9a9c203e10, d=...) at
/usr/src/debug/qt5-declarative/qtdeclarative/src/qml/qml/qqmltypeloader.cpp:447
#10 0x7f9abe2652ea in QQmlTypeLoader::setData
(this=this@entry=0x557221f422b8, blob=blob@entry=0x7f9a9c203e10, fileName=...)
at
/usr/src/debug/qt5-declarative/qtdeclarative/src/qml/qml/qqmltypeloader.cpp:437
#11 0x7f9abe266dd1 in QQmlTypeLoader::loadThread (this=0x557221f422b8,
blob=0x7f9a9c203e10) at
/usr/src/debug/qt5-declarative/qtdeclarative/src/qml/qml/qqmltypeloader.cpp:299
#12 0x7f9abe267296 in PlainLoader::loadThread (blob=0x7f9a9c203e10,
loader=0x557221f422b8, this=) at
/usr/src/debug/qt5-declarative/qtdeclarative/src/qml/qml/qqmltypeloader.cpp:146
#13 QQmlTypeLoader::doLoad (loader=...,
mode=QQmlTypeLoader::PreferSynchronous, blob=0x7f9a9c203e10,
this=0x557221f422b8) at
/usr/src/debug/qt5-declarative/qtdeclarative/src/qml/qml/qqmltypeloader.cpp:205
#14 QQmlTypeLoader::load (this=this@entry=0x557221f422b8,
blob=blob@entry=0x7f9a9c203e10,
mode=mode@entry=QQmlTypeLoader::PreferSynchronous) at
/usr/src/debug/qt5-declarative/qtdeclarative/src/qml/qml/qqmltypeloader.cpp:237
#15 0x7f9abe26765a in QQmlTypeLoader::getType (this=0x557221f422b8,
unNormalizedUrl=..., mode=QQmlTypeLoader::PreferSynchronous) at
/usr/src/debug/qt5-declarative/qtdeclarative/src/qml/qml/qqmltypeloader.cpp:825
#16 0x7f9abe21ff1e in QQmlTypeData::resolveTypes
(this=this@entry=0x557221d45780) at
/usr/src/debug/qt5-declarative/qtdeclarative/src/qml/qml/qqmltypedata.cpp:867
#17 0x7f9abe220f78 in QQmlTypeData::allDependenciesDone (this=) at
/usr/src/debug/qt5-declarative/qtdeclarative/src/qml/qml/qqmltypedata.cpp:737
#18 0x7f9abe264a72 in QQmlTypeLoader::setData
(this=this@entry=0x557221f422b8, blob=blob@entry=0x557221d45780, d=...) at
/usr/src/debug/qt5-declarative/qtdeclarative/src/qml/qml/qqmltypeloader.cpp:450
#19 0x7f9abe2652ea in QQmlTypeLoader::setData
(this=this@entry=0x557221f422b8, blob=blob@entry=0x557221d45780, fileName=...)
at
/usr/src/debug/qt5-declarative/qtdeclarative/src/qml/qml/qqmltypeloader.cpp:437
#20 0x7f9abe266dd1 in QQmlTypeLoader::loadThread (this=0x557221f422b8,
blob=0x557221d45780) at
/usr/src/debug/qt5-declarative/qtdeclarative/src/qml/qml/qqmltypeloader.cpp:299
#21 0x7f9abe22b512 in QQmlTypeLoaderThread::loadThread (this=, b=0x557221d45780) at
/usr/src/debug/qt5-declarative/qtdeclarative/src/qml/qml/qqmltypeloaderthread.cpp:162
#22 0x7f9abe2c570d in QQmlThreadPrivate::threadEvent (this=0x557221c251c0)
at
/usr/src/debug/qt5-declarative/qtdeclarative/src/qml/qml/ftw/qqmlthread.cpp:198
#23 QQmlThreadPrivate::event (this=0x557221c251c0, e=0x557221f20ce0) at
/usr/src/debug/qt5-declarative/qtdeclarative/src/qml/qml/ftw/qqmlthread.cpp:142
#24 0x7f9abed78b5c in QApplicationPrivate::notify_helper (this=, receiver=0x557221c251c0, e=0x557221f20ce0) at
kernel/qapplication.cpp:3640
#25 0x7f9abd48df48 in QCoreApplication::notifyInternal2
(receiver=0x557221c251c0, event=0x557221f20ce0) at
kernel/qcoreapplication.cpp:1064
#26 0x7f9abd48dfb3 in QCoreApplication::sendEvent (receiver=, event=) at kernel/qcoreapplication.cpp:1462
#27 0x7f9abd48ea53 in QCoreApplicationPrivate::sendPostedEvents
(receiver=0x0, event_type=0, data=0x557221f4b860) at
kernel/qcoreapplication.cpp:1821
#28 0x7f9abd4d4
[KScreen] [Bug 466516] Since Plasma 5.27, Plasma no longer remembers which display is "primary"
https://bugs.kde.org/show_bug.cgi?id=466516 Vorpal changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #4 from Vorpal --- Hm, the issue of the screen not being detected automatically appears to have fixed itself. Such is the life of rolling release distros, oh well. However, now "extend to right" and "extend to left" appears to have swapped meaning. Now it indicates which side the laptop monitor goes of the main screen! I don't know if it is useful any more, but here is the output you asked for: $ kscreen-doctor -o # Laptop only Output: 540 DP-0.2 disabled disconnected priority 0 Unknown Modes: Geometry: 0,0 0x0 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown Output: 563 DP-0 disabled disconnected priority 0 DisplayPort Modes: Geometry: 0,0 0x0 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown Output: 564 DP-1 disabled disconnected priority 0 DisplayPort Modes: Geometry: 0,0 0x0 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown Output: 565 DP-2 disabled disconnected priority 0 DisplayPort Modes: Geometry: 0,0 0x0 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown Output: 566 HDMI-0 disabled disconnected priority 0 HDMI Modes: Geometry: 0,0 0x0 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown Output: 567 DP-3 disabled disconnected priority 0 DisplayPort Modes: Geometry: 0,0 0x0 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown Output: 601 eDP-1-1 enabled connected priority 1 Panel Modes: 541:2560x1440@60 547:1600x1200@60 549:1280x1024@60 555:1024x768@60 557:800x600@60 561:640x480@60 608:3840x2160@60! 609:3840x2160@60 610:3840x2160@60 611:3200x1800@60 612:3200x1800@60 613:2880x1620@60 614:2880x1620@60 615:2560x1600@60 616:2560x1600@60 617:2560x1440@60 618:2560x1440@60 619:2560x1440@60 620:2048x1536@60 621:1920x1440@60 622:1856x1392@60 623:1792x1344@60 624:2048x1152@60 625:2048x1152@60 626:2048x1152@60 627:2048x1152@60 628:1920x1200@60 629:1920x1200@60 630:1920x1080@60* 631:1920x1080@60 632:1920x1080@60 633:1920x1080@60 634:1680x1050@60 635:1680x1050@60 636:1400x1050@60 637:1600x900@60 638:1600x900@60 639:1600x900@60 640:1600x900@60 641:1400x900@60 642:1400x900@60 643:1280x960@60 644:1440x810@60 645:1440x810@60 646:1368x768@60 647:1368x768@60 648:1280x800@60 649:1280x800@60 650:1280x800@60 651:1280x800@60 652:1280x720@60 653:1280x720@60 654:1280x720@60 655:1280x720@60 656:1024x768@60 657:960x720@60 658:928x696@60 659:896x672@60 660:1024x576@60 661:1024x576@60 662:1024x576@60 663:1024x576@60 664:960x600@60 665:960x600@60 666:960x540@60 667:960x540@60 668:960x540@60 669:960x540@60 670:800x600@60 671:800x600@56 672:840x525@60 673:840x525@60 674:864x486@60 675:864x486@60 676:700x525@60 677:800x450@60 678:800x450@60 679:640x512@60 680:700x450@60 681:700x450@60 682:640x480@60 683:720x405@60 684:720x405@59 685:684x384@60 686:684x384@60 687:640x400@60 688:640x400@60 689:640x360@60 690:640x360@60 691:640x360@60 692:640x360@59 693:512x384@60 694:512x288@60 695:512x288@60 696:480x270@60 697:480x270@60 698:400x300@60 699:400x300@56 700:432x243@60 701:432x243@60 702:320x240@60 703:360x202@60 704:360x202@59 705:320x180@60 706:320x180@59 Geometry: 0,0 1920x1080 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown Output: 602 DP-1-1 disabled disconnected priority 0 DisplayPort Modes: Geometry: 0,0 0x0 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown Output: 603 HDMI-1-1 disabled disconnected priority 0 HDMI Modes: Geometry: 0,0 0x0 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown Output: 604 DP-1-2 disabled disconnected priority 0 DisplayPort Modes: Geometry: 0,0 0x0 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown Output: 605 HDMI-1-2 disabled disconnected priority 0 HDMI Modes: Geometry: 0,0 0x0 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown Output: 606 DP-1-3 disabled disconnected priority 0 DisplayPort Modes: Geometry: 0,0 0x0 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown $ kscreen-doctor -o # External monitor plugged in (DP into dock connected via thunderbolt) Output: 540 DP-0.2 enabled connected priority 1 DisplayPort Modes: 541:2560x1440@60*! 542:2048x1080@60 543:2048x1080@24 544:1920x1080@60 545:1920x1080@60 546:1920x1080@50 547:1600x1200@60 548:1280x1024@75 549:1280x1024@60 550:1280x720@60 551:1280x720@60 552:1280x720@50 553:1152x864@75 554:1024x768@75 555:1024x768@60 556:800x600@75 557:800x600@60 558:720x576@50 559:720x480@60 560:640x480@75 561:640x480@60 562:640x480@60 Geometry: 1920,0 2560x1440 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown Output: 563 DP-0 disabled disconnected priority 0 DisplayPort Modes: Geometry: 0,0 0x0 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRang
[plasmashell] [Bug 466020] With multimonitor set-up (hidpi laptop + 2 displays with different sizes and resolutions via usb-c dock) one screen always has an invisible containment with a black backgrou
https://bugs.kde.org/show_bug.cgi?id=466020 --- Comment #8 from Marco Martin --- looking at he output you pasted, the 3 monitors are: the 3rd one DP-9 at 0,0 the 2nd one DP-8 at the right the 1st eDP-2 at the bottom of DP-9 screen priorities are eDP-2,DP-9,DP-8 What of the 3 screens gets black? or is it random? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 422306] Dolphin and KDE file dialogs open very slowly
https://bugs.kde.org/show_bug.cgi?id=422306 --- Comment #18 from Méven Car --- (In reply to bugreporter11 from comment #17) > (In reply to Henrik Gebauer from comment #16) > > I have the same issue (file open dialog took 9-10 seconds to show up). After > > reading this bug report and the comments I finally tried deleting ` > > ~/.local/share/user-places.xbel` and that resolved the problem for me. > > > > The original file had over 21,000 lines, the newly generated has only 198 > > lines. > > The original file was over and over full with entries from kdeconnect (i > > have only one paired device but there were hundreds of entries) and hundreds > > entries about docker layers. > > > > I guess this bug is related to > > * #466416 KDE Connect keeps adding devices to Dolphin over and over and over > > and over and over > > * #451876 Dolphin slow start takes almost 5-6 seconds > > * #398908 Dolphin uses up huge amounts of memory over time > > I'm the OP. Thanks for your comment. That helps. I have had this issue for > years and it is not resolved. Maybe those other bug reports will help. I > also think you are right about a large ~/.local/share/user-places.xbel being > part of the problem. Mine is currently 14617 lines. It has thousands of > kdeconnect entries in it. > > I do not want to delete the entire file because I have well organized > Dolphin bookmarks that I invested a lot of time in creating. You should be able to remove the unnecessary kdeconnect entries. Could anyone share their lenghthy ~/.local/share/user-places.xbel ? Only the kdeconnect entries part would be sufficient. That would help diagnose what goes wrong with kdeconnect adding all those entries. I don't reproduce it myself.k -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 465531] Dolphin Crashes Out of the Blue
https://bugs.kde.org/show_bug.cgi?id=465531 Méven Car changed: What|Removed |Added Status|NEEDSINFO |CONFIRMED Resolution|WAITINGFORINFO |--- Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 467089] Krita program works first day and it does not appear (icon) and does not work on the next day.
https://bugs.kde.org/show_bug.cgi?id=467089 Nicolas Fella changed: What|Removed |Added CC||nicolas.fe...@gmx.de Assignee|unassigned-b...@kde.org |krita-bugs-n...@kde.org Product|kde |krita Component|general |General -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466095] Plasma crashes in DesktopView::screenToFollow() on screen wake up when KScreen service is active
https://bugs.kde.org/show_bug.cgi?id=466095 --- Comment #10 from Marco Martin --- this says that a view for a desktop has been deleted, but not removed from m_desktopViewForScreen in theory, the only entry point where a desktopview gets deleted is in ShellCorona::removeDesktop (also in ShellCorona::setScreenForContainment but in theory this should ever be called only from the reorder UI) in ShellCorona::removeDesktop from 5.27.1 the view is removed m_desktopViewForScreen by searching all the values, so we are sure it's actually removed. Unless, the same view was inserted in the map multiple times, mapped in two or more screen numbers. this seems *very* improbable, but perhaps worth investigating -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 467038] kde-baseapps package was removed from system after an update
https://bugs.kde.org/show_bug.cgi?id=467038 --- Comment #7 from Moltke --- (In reply to Carlos De Maine from comment #6) > Hi.. Updated packages are coming through the build system. Unfortunately > you tried to upgrade while the packages that depend on libjpeg-turbo were > rebuilding to satisfy the new dependencies. Please never accept the removal > of any packages and wait for the corrected/rebuilt packages to come down the > line. Cheers I never accepted anything, it just happened. Is this fixable? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 467104] New: Change Case Error in Turkish
https://bugs.kde.org/show_bug.cgi?id=467104 Bug ID: 467104 Summary: Change Case Error in Turkish Classification: Frameworks and Libraries Product: frameworks-ktexteditor Version: 5.103.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: emir_s...@icloud.com Target Milestone: --- In Turkish, the capital form of the letter i is İ (with a dot on top). Also, there is another dotless ı, which is capitalised as I. This causes errors while changing case. For instance, the small case version of the word YILDIZ should be "yıldız", not "yildiz". As additional info, converting an all caps word into small caps leaves some artifacts, for instance small-casing "VAMPİR", gives the output "vampi̇r" (there is an additional here-invisible character between i and r. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 467081] importing transactions prior to account opening date cannot be edited
https://bugs.kde.org/show_bug.cgi?id=467081 --- Comment #1 from Thomas Baumgart --- Or we could simply adjust the opening date in that case. But what about a possible opening balance transaction? Maybe a warning about it is better. -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 464698] Sometimes the scrollbar doesn't move when clicking and dragging it
https://bugs.kde.org/show_bug.cgi?id=464698 Jan Rathmann changed: What|Removed |Added CC||jan.rathm...@gmx.de Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #6 from Jan Rathmann --- I'm also seeing this behavious, sometimes the scrollbar works, sometimes it doesn't. If it doesn't work, it usually helps to temporarily switch to another room and then switch back to the original one. Wondered if this might be Wayland specific but I see that the original report is from X11.. -- You are receiving this mail because: You are watching all bug changes.
[Alligator] [Bug 467105] New: Cannot scroll to refresh on empty list page
https://bugs.kde.org/show_bug.cgi?id=467105 Bug ID: 467105 Summary: Cannot scroll to refresh on empty list page Classification: Applications Product: Alligator Version: unspecified Platform: Android OS: Android 13.x Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: fe...@posteo.de Reporter: jackhill3...@gmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Mark all posts as read 2. Go into the Unread tab 3. Attempt to scroll down OBSERVED RESULT Cannot scroll EXPECTED RESULT Should be able to scroll to refresh SOFTWARE/OS VERSIONS Android 13 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467069] Intermittent Crashing Desktop Black Screen and Refresh of whole screen when i roll over mouse
https://bugs.kde.org/show_bug.cgi?id=467069 --- Comment #1 from Tho --- Created attachment 157142 --> https://bugs.kde.org/attachment.cgi?id=157142&action=edit Shows Fatal Error Crashed again grabbed log instantly -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 443009] Replying email breaks text encoding
https://bugs.kde.org/show_bug.cgi?id=443009 Laurent Montel changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/pim/ ||messagelib/commit/29a5a05e2 ||078b75f0a994e29e92707e3ec81 ||e2d1 --- Comment #2 from Laurent Montel --- Git commit 29a5a05e2078b75f0a994e29e92707e3ec81e2d1 by Laurent Montel, on behalf of Fabian Vogt. Committed on 09/03/2023 at 07:27. Pushed by fvogt into branch 'master'. Fix fallback path in MessageFactoryNG::applyCharset In the case that the codec of the original message could not encode the reply, it was still set as charset but the body encoded with the fallback codec. This resulted in replies having messed up encoding. It can be triggered by replying to multipart mails which define the charset in parts only or if the reply template ends up with other special characters. Related: bug 447297, bug 298349 M +64 -0messagecomposer/autotests/messagefactoryngtest.cpp M +3-0messagecomposer/autotests/messagefactoryngtest.h M +5-4messagecomposer/src/helper/messagefactoryng.cpp https://invent.kde.org/pim/messagelib/commit/29a5a05e2078b75f0a994e29e92707e3ec81e2d1 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 447297] UTF-8 characters decoded incorrectly on reply
https://bugs.kde.org/show_bug.cgi?id=447297 Laurent Montel changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/pim/ ||messagelib/commit/29a5a05e2 ||078b75f0a994e29e92707e3ec81 ||e2d1 --- Comment #2 from Laurent Montel --- Git commit 29a5a05e2078b75f0a994e29e92707e3ec81e2d1 by Laurent Montel, on behalf of Fabian Vogt. Committed on 09/03/2023 at 07:27. Pushed by fvogt into branch 'master'. Fix fallback path in MessageFactoryNG::applyCharset In the case that the codec of the original message could not encode the reply, it was still set as charset but the body encoded with the fallback codec. This resulted in replies having messed up encoding. It can be triggered by replying to multipart mails which define the charset in parts only or if the reply template ends up with other special characters. Related: bug 443009, bug 298349 M +64 -0messagecomposer/autotests/messagefactoryngtest.cpp M +3-0messagecomposer/autotests/messagefactoryngtest.h M +5-4messagecomposer/src/helper/messagefactoryng.cpp https://invent.kde.org/pim/messagelib/commit/29a5a05e2078b75f0a994e29e92707e3ec81e2d1 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 298349] kmail2 composer (still) fails to display non-ascii characters in quoted text on reply with some mails (only with nested multipart mime parts?)
https://bugs.kde.org/show_bug.cgi?id=298349 Laurent Montel changed: What|Removed |Added Latest Commit||https://invent.kde.org/pim/ ||messagelib/commit/29a5a05e2 ||078b75f0a994e29e92707e3ec81 ||e2d1 Status|ASSIGNED|RESOLVED Resolution|--- |FIXED --- Comment #19 from Laurent Montel --- Git commit 29a5a05e2078b75f0a994e29e92707e3ec81e2d1 by Laurent Montel, on behalf of Fabian Vogt. Committed on 09/03/2023 at 07:27. Pushed by fvogt into branch 'master'. Fix fallback path in MessageFactoryNG::applyCharset In the case that the codec of the original message could not encode the reply, it was still set as charset but the body encoded with the fallback codec. This resulted in replies having messed up encoding. It can be triggered by replying to multipart mails which define the charset in parts only or if the reply template ends up with other special characters. Related: bug 447297, bug 443009 M +64 -0messagecomposer/autotests/messagefactoryngtest.cpp M +3-0messagecomposer/autotests/messagefactoryngtest.h M +5-4messagecomposer/src/helper/messagefactoryng.cpp https://invent.kde.org/pim/messagelib/commit/29a5a05e2078b75f0a994e29e92707e3ec81e2d1 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466238] Exiting full screen video playback with on a multi-monitor setup causes a freeze
https://bugs.kde.org/show_bug.cgi?id=466238 --- Comment #22 from Rune --- (In reply to Zamundaaa from comment #21) > good, that narrows it down a lot. To narrow it down further, could you > remove that again and test with > > KWIN_DRM_PREFER_COLOR_DEPTH=24 > and > > KWIN_DRM_USE_MODIFIERS=0 > (one at a time only) instead? Neither one of those helped. -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 467106] New: URL preview expand button shows the wrong tooltip if button is pressed before tooltip shows
https://bugs.kde.org/show_bug.cgi?id=467106 Bug ID: 467106 Summary: URL preview expand button shows the wrong tooltip if button is pressed before tooltip shows Classification: Applications Product: NeoChat Version: unspecified Platform: Compiled Sources OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: General Assignee: fe...@posteo.de Reporter: jackhill3...@gmail.com CC: c...@carlschwan.eu Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Send a msg with a URL 2. Click the expand button 3. Wait for the tooltip to show OBSERVED RESULT "Expand Preview" EXPECTED RESULT "Shrink Preview" SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20230307 KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.2.1-1-default (64-bit) Graphics Platform: X11 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 467107] New: Applet does not update on network change.
https://bugs.kde.org/show_bug.cgi?id=467107 Bug ID: 467107 Summary: Applet does not update on network change. Classification: Plasma Product: plasma-nm Version: 5.27.2 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: applet Assignee: plasma-b...@kde.org Reporter: serrapmcc...@gmail.com Target Milestone: --- SUMMARY *** The connection details in the widget do not update when the connection is modified. Updates only seem to be triggered via Disconnect/reconnect. And are often incomplete. *** STEPS TO REPRODUCE 1. Change IP address in setting or via cli 2. Check applet for changes, vs nmci. 3. Applet doesnt change unless you toggle the connection (this will force a one-time update, that is often incomplete) OBSERVED RESULT No updates to widget details when connection changes are made. EXPECTED RESULT Widget details updates. SOFTWARE/OS VERSIONS Operating System: EndeavourOS KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.2.2-zen1-1-zen (64-bit) Graphics Platform: Wayland Processors: 20 × 12th Gen Intel® Core™ i7-12700K Memory: 30.7 GiB of RAM Graphics Processor: AMD Radeon RX 5700 XT Manufacturer: ASUS ADDITIONAL INFORMATION The DNS field in details is also broken -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 467108] New: pextrb instruction is not recognized
https://bugs.kde.org/show_bug.cgi?id=467108 Bug ID: 467108 Summary: pextrb instruction is not recognized Classification: Developer tools Product: valgrind Version: 3.19.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: vex Assignee: jsew...@acm.org Reporter: olek...@gmail.com Target Milestone: --- See similar bug #366237 Just replace pextrw with pextrb in #366237 attachment. $ cat test_pextrw.nas-nasm.lst 1 [bits 64] 2 [default rel] 3 4 [section .text align=16] 5 6 [global test_pextrw] 7 test_pextrw: 8 0F1007movups xmm0, [rdi] 9 0003 660F3A14C003 pextrb rax, xmm0, 3 10 0009 C3ret 11 $ cat test_pextrw.nas-yasm.lst 1 %line 1+1 test_pextrw.nas 2 [bits 64] 3 [default rel] 4 5 [section .text align=16] 6 7 [global test_pextrw] 8 test_pextrw: 9 0F1007 movups xmm0, [rdi] 10 0003 66480F3A14C003 pextrb rax, xmm0, 3 11 000A C3 ret Valgrind error: ==523428== Memcheck, a memory error detector ==523428== Copyright (C) 2002-2022, and GNU GPL'd, by Julian Seward et al. ==523428== Using Valgrind-3.19.0 and LibVEX; rerun with -h for copyright info ==523428== Command: ./test_pextrw_yasm.exe ==523428== Parent PID: 521086 ==523428== vex amd64->IR: unhandled instruction bytes: 0x66 0x48 0xF 0x3A 0x14 0xC0 0x3 0xC3 0x0 0xF3 vex amd64->IR: REX=1 REX.W=1 REX.R=0 REX.X=0 REX.B=0 vex amd64->IR: VEX=0 VEX.L=0 VEX.n=0x0 ESC=0F3A vex amd64->IR: PFX.66=1 PFX.F2=0 PFX.F3=0 ==523428== valgrind: Unrecognised instruction at address 0x109213. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 467109] New: Preview settings for RAW image files are ignored
https://bugs.kde.org/show_bug.cgi?id=467109 Bug ID: 467109 Summary: Preview settings for RAW image files are ignored Classification: Applications Product: dolphin Version: 22.12.3 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: sephiroth...@hotmail.it CC: kfm-de...@kde.org Target Milestone: --- SUMMARY I have a Lumix camera which produces RAW image files in the RW2 format, and I store them on an NFS share on a NAS. I have set Dolphin not to create previews of RAW files and to avoid previews of remote files larger than 15 MB. Despite this, Dolphin proceeds to create previews of RAW files shot with my camera. The only way to avoid this is to uncheck the "images (GIF, PNG, BMP...)" item in the list. There seems then to be two issues at play: one is that RW2 is grouped together with images, rather than wit RAW image files; the other is that the limit for file size is ignored. STEPS TO REPRODUCE 1. Uncheck the "RAW Photo Camera Files" item in the "previews" section of Dolphin's settings 2. Open a folder which contains RW2 files OBSERVED RESULT The preview for the files is generated anyway. EXPECTED RESULT The preview for the files is not generated. SOFTWARE/OS VERSIONS Linux: KDE neon KDE Plasma Version: 5.27.1 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 467108] pextrb instruction is not recognized
https://bugs.kde.org/show_bug.cgi?id=467108 Vasiliy Olekhov changed: What|Removed |Added Version|3.19.0 |3.21 GIT Platform|Other |Compiled Sources -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 467108] pextrb instruction is not recognized
https://bugs.kde.org/show_bug.cgi?id=467108 --- Comment #1 from Vasiliy Olekhov --- Confirmed bug at Valgrind-3.21.0.GIT 660F3A14C003 - nasm opcode version is OK 66480F3A14C003 - yasm opcode is detected as illegal instruction -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 374890] kscreenlocker_greet freezes with multiscreen setup and blocks unlocking
https://bugs.kde.org/show_bug.cgi?id=374890 --- Comment #39 from Vitaliy Filippov --- Created attachment 157143 --> https://bugs.kde.org/attachment.cgi?id=157143&action=edit Stack traces of hung kscreenlocker_greet Ok, finally I got another hang with 5.27.2. Attaching stack traces of all threads... -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 466329] The main window display doesn't update.
https://bugs.kde.org/show_bug.cgi?id=466329 Halla Rempt changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #5 from Halla Rempt --- Thanks! I've downloaded the file. I know what's up: it looks like you copied the canvas and then pasted it as a reference image over the canvas, so it looks like the image but cannot be painted on. Try to select the reference image tool: you'll see the reference tool handles appear. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467110] New: wayland: Submenu closing causes disabling of current selected menu item
https://bugs.kde.org/show_bug.cgi?id=467110 Bug ID: 467110 Summary: wayland: Submenu closing causes disabling of current selected menu item Classification: Plasma Product: plasmashell Version: 5.27.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: slartibar...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 At first, i thought that a click on a menu item wasn't registered properly, but the cause is something completely different: Open chromium or thunderbird right click on the window-titlebar to display the context menu Target the last entry 'close' with the mouse, but move/traverse slowly through the available items from top to bottom. The important part is, that the submenu 'more actions' opens. (don't select anything from here) Move the mouse further on to the 'close' entry and hold it (don't move any further, don't click) The desired effect is, that the end of the mouse motion is earlier than the closing of the 'more actions' submenu The last entry 'close' is seen to be highlighted, but when the submenu closes, the highlighting of the 'close' entry disappears as well. You need to move the mouse a bit to re-highlight again. The thing is, this happens also when operated quickly giving you the impression that clicking on the close entry is not registered. That's annoying at best :-) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 463115] [Android] Krita loses detection of mouse events on canvas after S-PEN is in range, and it won't come back
https://bugs.kde.org/show_bug.cgi?id=463115 --- Comment #26 from Tyson Tan --- Thanks Sharaf! I've tested the new APK, and I can confirm that the bugs has been fixed. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466238] Exiting full screen video playback with on a multi-monitor setup causes a freeze
https://bugs.kde.org/show_bug.cgi?id=466238 --- Comment #23 from Zamundaaa --- Okay, so the problem could be in either KWin or the driver. Can you remove all the environment variables again, enable drm logging and record the dmesg output while reproducing the bug again? For details on how to do that, see https://invent.kde.org/plasma/kwin/-/wikis/Debugging-DRM-issues -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 422306] Dolphin and KDE file dialogs open very slowly
https://bugs.kde.org/show_bug.cgi?id=422306 --- Comment #19 from Henrik Gebauer --- > Could anyone share their lenghthy ~/.local/share/user-places.xbel ? > Only the kdeconnect entries part would be sufficient. This is the entry. (I replaced some content by "x" because I'm not sure if it should be considered sensitive information) There are 1449 copies of the following entry in my file. They are all identical except for the part. The is often repeating only with a different number after the /. SM-G525F http://freedesktop.org";> http://www.kde.org";> 16402x/2 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 461046] Totally can't use in iOS 16.0.3
https://bugs.kde.org/show_bug.cgi?id=461046 --- Comment #25 from Bruce --- (In reply to Apollo Zhu from comment #24) > Okay, looks like there's a very rare scenario (which I don't know how to > reproduce) that the iOS client will send out an identity package with a > wrong tcp port than the one currently used. 0.3.1 (3) includes the fix, and > hopefully it should now work for you... bad news, I've tried switch to another wifi router, but still has the same problem. still cannot discover soduto on my macOS, even I configure my macOS's IP directly. but can discover my android kde-connect(each other). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466238] Exiting full screen video playback with on a multi-monitor setup causes a freeze
https://bugs.kde.org/show_bug.cgi?id=466238 --- Comment #24 from Rune --- Created attachment 157144 --> https://bugs.kde.org/attachment.cgi?id=157144&action=edit DRM log -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 466310] Thrash sort by deletion time doesn't work
https://bugs.kde.org/show_bug.cgi?id=466310 amarnath changed: What|Removed |Added CC||amarnathgo...@gmail.com --- Comment #2 from amarnath --- Hello, I see that in the screen shot you attached, time stamps under "deletion time" are sorted in most recent to least recent order. Can you point where it is not sorted by Deletion time correctly? Also, while looking for this bug I found that, dolphin sorts folders first and then files. Could you please assure me that this is not the point of confusion. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 467111] New: When I take a screenshot it captures a previous state of the screen and there is no way to update the captured screen.
https://bugs.kde.org/show_bug.cgi?id=467111 Bug ID: 467111 Summary: When I take a screenshot it captures a previous state of the screen and there is no way to update the captured screen. Classification: Applications Product: Spectacle Version: 22.12.3 Platform: Archlinux OS: Linux Status: REPORTED Severity: major Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: eriksoleper...@gmail.com CC: k...@david-redondo.de Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Open spectacle 2. Take screenshot OBSERVED RESULT Makes a screenshot of a previous state of the screen and it is always the same one. EXPECTED RESULT A screenshot of the current screen SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux x86_64 (available in About System) KDE Plasma Version: Plasma 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kup] [Bug 453919] Backup folder not created for external disk plans
https://bugs.kde.org/show_bug.cgi?id=453919 --- Comment #12 from Christian Hartmann --- (In reply to Simon Persson from comment #10) > Has anybody tried deleting the folder after a backup was saved there? > Does kup go back to not doing anything again? (It should still work, and > does still work when I tested) i tried this... 1. i moved (actualy just renamed) the used beforehand directory (on my external disk). 2. checked kup config via system settings - all unchanged 3. tried to create backup via system tray symbol (with a so configured but currently no existing directory) 4. nothing happened / quite exit 5. renamed the renamed folder to its original name 6. tried to create backup via system tray symbol (with the so configured and now existing again directory) 7. backup is created ... if it is helpful i can supply screenshots all of that -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466969] Virtual Keyboard button doesn't make the virtual keyboard appear on SDDM (Wayland)
https://bugs.kde.org/show_bug.cgi?id=466969 Aleix Pol changed: What|Removed |Added Latest Commit||https://invent.kde.org/plas ||ma/kwin/commit/d34cf36bfaad ||d39fcc6893379a0d8d8326031ee ||a Status|ASSIGNED|RESOLVED Resolution|--- |FIXED --- Comment #8 from Aleix Pol --- Git commit d34cf36bfaadd39fcc6893379a0d8d8326031eea by Aleix Pol Gonzalez, on behalf of Aleix Pol. Committed on 09/03/2023 at 14:18. Pushed by apol into branch 'master'. inputmethod: Show the input method even if it was dismissed Reset the current context in case we receive a show() event from the client, meaning that they really want to see that virtual keyboard. M +2-0src/inputmethod.cpp https://invent.kde.org/plasma/kwin/commit/d34cf36bfaadd39fcc6893379a0d8d8326031eea -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 466516] Since Plasma 5.27, Plasma no longer remembers which display is "primary"
https://bugs.kde.org/show_bug.cgi?id=466516 Nate Graham changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #5 from Nate Graham --- Since the original issue appears to be fixed now (could be a migration issue that doesn't happen anymore now that the migration is done) then could you please submit a new bug report for this new issue? Thanks a lot! -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 467112] New: all my notes disappeared no raeson
https://bugs.kde.org/show_bug.cgi?id=467112 Bug ID: 467112 Summary: all my notes disappeared no raeson Classification: Plasma Product: kdeplasma-addons Version: git-stable-Plasma/5.27 Platform: openSUSE OS: Linux Status: REPORTED Severity: major Priority: NOR Component: notes Assignee: plasma-b...@kde.org Reporter: mig...@rozsas.eng.br Target Milestone: --- SUMMARY *** Even on 5.27.2 my notes disappeared from desktop on login. Last night, when I logoff, they were there. Today, after login, no notes anymore. I had a dozen or so. *** STEPS TO REPRODUCE 1. Use knotes 2. Do nothing 3. Buum ! There is no notes anymore Sorry, this is a well know bug with KDE/Plasma/Knotes. For no reason they disappear without notice. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20230302 KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.2.1-1-default (64-bit) Graphics Platform: X11 Processors: 12 × AMD Ryzen 5 7600X 6-Core Processor Memory: 30.5 GiB of RAM Graphics Processor: AMD Radeon RX 6600 Manufacturer: ASUS -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 459858] Task switcher preview cannot be closed
https://bugs.kde.org/show_bug.cgi?id=459858 rosswzy...@outlook.com changed: What|Removed |Added Version|5.25.5 |5.27.2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467113] New: Icons only task manager crash when closing one of the grouped tasks
https://bugs.kde.org/show_bug.cgi?id=467113 Bug ID: 467113 Summary: Icons only task manager crash when closing one of the grouped tasks Classification: Plasma Product: plasmashell Version: 5.27.2 Platform: Archlinux OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: Task Manager and Icons-Only Task Manager Assignee: plasma-b...@kde.org Reporter: cakiroglu.m...@gmail.com Target Milestone: 1.0 Steps to Reproduce: 1. Open multiple instances of an application 2. Unfocus all of the windows (by maximizing another window) 3. Mouse hover on the grouped application so a mini-display of all instances appear 4. Without focusing on another window, press the close button on the top of one of the mini-displays. 5. Application closes but Task manager also crashes I am unable to replicate this reliably. Occasionally, following the steps may not result in a crash but it started happening fairly frequently. The bug seems to occur when I perform the steps after rebooting my system, and it may or may not continue to occur after the crash has already happened once. STACK TRACE PID: 861 (plasmashell) UID: 1000 GID: 1000 Signal: 11 (SEGV) Timestamp: Thu 2023-03-09 17:46:28 +03 (25s ago) Command Line: /usr/bin/plasmashell --no-respawn Executable: /usr/bin/plasmashell Control Group: /user.slice/user-1000.slice/user@1000.service/session.slice/plasma-plasmashell.service Unit: user@1000.service User Unit: plasma-plasmashell.service Slice: user-1000.slice Owner UID: 1000 Boot ID: 94298e8648e64c439f205eb57f17d88a Machine ID: 5ef343778877497694490d6a9d2f87a9 Hostname: Storage: /var/lib/systemd/coredump/core.plasmashell.1000.94298e8648e64c439f205eb57f17d88a.861.167837318800.zst (present) Size on Disk: 20.7M Message: Process 861 (plasmashell) of user 1000 dumped core. Stack trace of thread 861: #0 0x7f0b88ca08ec n/a (libc.so.6 + 0x878ec) #1 0x7f0b88c51ea8 raise (libc.so.6 + 0x38ea8) #2 0x7f0b8b4787ef _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5 + 0x77ef) #3 0x7f0b88c51f50 n/a (libc.so.6 + 0x38f50) #4 0x7f0b88ca08ec n/a (libc.so.6 + 0x878ec) #5 0x7f0b88c51ea8 raise (libc.so.6 + 0x38ea8) #6 0x7f0b88c51f50 n/a (libc.so.6 + 0x38f50) #7 0x7f0b88c9b764 n/a (libc.so.6 + 0x82764) #8 0x7f0b88c9df90 pthread_cond_wait (libc.so.6 + 0x84f90) #9 0x7f0b892eb7c4 _ZN14QWaitCondition4waitEP6QMutex14QDeadlineTimer (libQt5Core.so.5 + 0xeb7c4) #10 0x7f0b8b0024d0 n/a (libQt5Quick.so.5 + 0x2024d0) #11 0x7f0b8b052739 _ZN12QQuickWindow5eventEP6QEvent (libQt5Quick.so.5 + 0x252739) #12 0x7f0b68592caa n/a (libcorebindingsplugin.so + 0x30caa) #13 0x7f0b8a178b5c _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x178b5c) #14 0x7f0b8948df48 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x28df48) #15 0x7f0b89933488 _ZN15QPlatformWindow11windowEventEP6QEvent (libQt5Gui.so.5 + 0x133488) #16 0x7f0b8a17d041 _ZN12QApplication6notifyEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x17d041) #17 0x7f0b8948df48 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x28df48) #18 0x7f0b894d84b3 _ZN14QTimerInfoList14activateTimersEv (libQt5Core.so.5 + 0x2d84b3) #19 0x7f0b894d8af2 n/a (libQt5Core.so.5 + 0x2d8af2) #20 0x7f0b880f182b g_main_context_dispatch (libglib-2.0.so.0 + 0x5582b) #21 0x7f0b88148cc9 n/a (libglib-2.0.so.0 + 0xaccc9) #22 0x7f0b880f00e2 g_main_context_iteration (libglib-2.0.so.0 + 0x540e2) #23 0x7f0b894d8c6c _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2d8c6c) #24 0x7f0b894866ec _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2866ec) #25 0x7f0b89491219 _ZN16QCoreApplication4execEv (libQt5Core.so.5 + 0x291219) #26 0x562a7f4fc168 n/a (plasmashell + 0x24168) #27 0x7f0b88c3c790 n/a (libc.so.6 + 0x23790) #28 0x7f0b88c3c84a __libc_start_main (libc.so.6 + 0x2384a) #29 0x562a7f4fc515 n/a (plasmashell + 0x24515) Stack trace of thread 892: #0 0x7f0b88c9b766 n/a (libc.so.6 + 0x82766) #1 0x7f0b88c9df90 pthread_cond_wait (libc.so.6 + 0x84f90)
[kdenlive] [Bug 467114] New: kdenlive crashes on File->Save As after some successful saves
https://bugs.kde.org/show_bug.cgi?id=467114 Bug ID: 467114 Summary: kdenlive crashes on File->Save As after some successful saves Classification: Applications Product: kdenlive Version: git-master Platform: macOS (DMG) URL: http://@4iron OS: macOS Status: REPORTED Severity: critical Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: j...@sydney.dialix.com.au Target Milestone: --- Created attachment 157145 --> https://bugs.kde.org/attachment.cgi?id=157145&action=edit error details from kdenlive crash on Save As SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** Sorry, that link says it is not relevant to Mac computers. STEPS TO REPRODUCE 1. Start a new project, basing details on first clip imported, accepting suggested transcode. 16x9 ratio, variable framerate transcoded to 30 fps. 2. Add another video clip, accepting suggested transcode. 3. Do File->Save As and successfully save a .kdenlive file. 4. Drag the first clip to the timeline. 5. Replace the audio of that clip with an improved version made with Audacity. 6. Insert an image as a background video track below the main image, so the main image can be transformed and moved partly off the screen without leaving a slice of black. 7. Add a 3x4 image in a video track above the main track, transform it to move it to the left margin. This leaves the speaker on the right-hand side of the screen, and the slide she is talking about covering most of the screen. 8. Stretch the image to cover the duration of the talk about the image in the main track. 9. Transform the main track to move it left and right as the speaker moves a bit, to keep her on the right-hand side of the screen and not obscured by the slide she is talking about. 10. Do File->Save As to a modified filename in the same folder as the video clips. Successful save. 11. Repeat steps 7 to 10 several times, copying the transform effect from an old image to the new image each time. Save As works properly. 12. Do File->Save As and the program crashes, displaying a lot of details that it says will be sent to Apple. I'll attach a file of those. OBSERVED RESULT When the program crashes, the file I was trying to save is not written. When I relaunch the program and load the last-saved .kdenlive file, it offers to recover unsaved changes. For some images, the program reports an error dialog when I import the image, and the detail is that the image is too small to make a proxy file. (Setting was for 700 px.) Version 22 of kdenlive just said it was unable to make a proxy file from that image. I changed the default settings and the settings for the project so that it did not try to make proxies for any images, and after a crash this change was remembered. EXPECTED RESULT File->Save As would work properly as has been the case for several videos I have made with earlier versions on my Mac SOFTWARE/OS VERSIONS macOS: Ventura 13.2.1 ADDITIONAL INFORMATION kdenlive version is the nightly build from https://binary-factory.kde.org/job/Kdenlive_Nightly_macos/ Number 1410 of 2023-03-09. I moved to this version because the normal stable release, 22.12.1, was crashing the same way. I have attached the debug information that I could find, and have uploaded the .kdenlive files that I was able to save to a folder in Google Drive, along with a rendering of the video, so you can see what the transform effects do. Here's the link: https://drive.google.com/drive/folders/1ibi-iRBUtBnS_wRr7Ro1SzHF27p6QVWR?usp=sharing There is a bug report that seems similar at https://bugs.kde.org/show_bug.cgi?id=466561 In that one, 4ironm...@gmail.com changed the save location, which I did not do. I hope someone can suggest some work-around for me, and the developers, so generous with their time, can work out what is going wrong and fix it :-) (Thanks, developers, for a wonderful program!) -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 467114] kdenlive crashes on File->Save As after some successful saves
https://bugs.kde.org/show_bug.cgi?id=467114 Jim Henderson changed: What|Removed |Added CC||j...@sydney.dialix.com.au -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467113] Icons only task manager crash when closing one of the grouped tasks
https://bugs.kde.org/show_bug.cgi?id=467113 cakiroglu.m...@gmail.com changed: What|Removed |Added CC||cakiroglu.m...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 467114] kdenlive crashes on File->Save As after some successful saves
https://bugs.kde.org/show_bug.cgi?id=467114 Jim Henderson changed: What|Removed |Added URL|http://@4iron |http:// -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467113] Icons only task manager crash when closing one of the grouped tasks
https://bugs.kde.org/show_bug.cgi?id=467113 cakiroglu.m...@gmail.com changed: What|Removed |Added CC|cakiroglu.m...@gmail.com| -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467113] Icons only task manager crash when closing one of the grouped tasks
https://bugs.kde.org/show_bug.cgi?id=467113 cakiroglu.m...@gmail.com changed: What|Removed |Added Version|5.27.2 |master -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467115] New: Plasma Panels and Desktop management show reversed order of sreens on 2 monitor setup
https://bugs.kde.org/show_bug.cgi?id=467115 Bug ID: 467115 Summary: Plasma Panels and Desktop management show reversed order of sreens on 2 monitor setup Classification: Plasma Product: plasmashell Version: 5.27.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Multi-screen support Assignee: plasma-b...@kde.org Reporter: a.nolt...@almano.de CC: aleix...@kde.org, notm...@gmail.com Target Milestone: 1.0 Created attachment 157146 --> https://bugs.kde.org/attachment.cgi?id=157146&action=edit Plasma panel and Desktop management.jpg SUMMARY Under X11 the current release of Plasma 5 shows the connected monitors and screens in reversed order. Physically the monitors connected in the following order to the graphic card (Nvidia 2080 TI): at the first port (reported by the nvidia driver) left monitor at the second port right monitor This order ensures that the screens appear on the sddm logon screen in the right order, so the mouse point moves from left to right and backwards correct between the screens - left screen has its right border at the left border of the right screen. Though the same after login. Monitor and Display settings in systems settings show also the correct order using Identification functionality. Only the management window for managing Panels and Desktop shows the screens and therefore the connected monitor in reversed order. STEPS TO REPRODUCE 1. open system settings - Display setting 2. right click on one of the screens and select Edit panel 3. click on manage screen button at the management menu appearing on the top OBSERVED RESULT The new window showing the connected monitors and screens in reversed order compared to display settings EXPECTED RESULT The new window showing the connected monitors and screens show the same order as the display setting in plasma system setting SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.2.2-arch1-1 (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 3700X 8-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7C37 System Version: 1.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466969] Virtual Keyboard button doesn't make the virtual keyboard appear on SDDM (Wayland)
https://bugs.kde.org/show_bug.cgi?id=466969 Aleix Pol changed: What|Removed |Added Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/kwin/commit/d34cf36bfaad |ma/kwin/commit/8fefef61849c |d39fcc6893379a0d8d8326031ee |58ca74e50cf09a6fcc15639cf08 |a |7 --- Comment #9 from Aleix Pol --- Git commit 8fefef61849c58ca74e50cf09a6fcc15639cf087 by Aleix Pol Gonzalez, on behalf of Aleix Pol. Committed on 09/03/2023 at 14:36. Pushed by apol into branch 'Plasma/5.27'. inputmethod: Show the input method even if it was dismissed Reset the current context in case we receive a show() event from the client, meaning that they really want to see that virtual keyboard. (cherry picked from commit d34cf36bfaadd39fcc6893379a0d8d8326031eea) M +2-0src/inputmethod.cpp https://invent.kde.org/plasma/kwin/commit/8fefef61849c58ca74e50cf09a6fcc15639cf087 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 467114] kdenlive crashes on File->Save As after some successful saves
https://bugs.kde.org/show_bug.cgi?id=467114 Bug Janitor Service changed: What|Removed |Added Severity|critical|crash -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 333785] WISH: Would like to have better sticky notes
https://bugs.kde.org/show_bug.cgi?id=333785 Alexander Nolting changed: What|Removed |Added Resolution|--- |UNMAINTAINED Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 465690] When using wayland, Popup dialogs show up in the middle, or middle/bottom of the desktop
https://bugs.kde.org/show_bug.cgi?id=465690 --- Comment #16 from Troy Dawson --- Just letting you know that I've gotten the latest QT5 stack built. I am now rebuilding the KDE stack on top of it. Should have it done by the end of the week. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 333785] WISH: Would like to have better sticky notes
https://bugs.kde.org/show_bug.cgi?id=333785 --- Comment #3 from Alexander Nolting --- closed bug due to to feedback from development. Checking current Okular seem the handle annotation and sticky notes, notes and other note items better, whereas the overall performance and responsiveness of Okular when adding notes could be much better. In its current form it takes about 1-2 seconds after left clicking a PDf for placing a note or annotation to the selected text or picture. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 433142] Improvement for installer component needed
https://bugs.kde.org/show_bug.cgi?id=433142 Alexander Nolting changed: What|Removed |Added Resolution|--- |UNMAINTAINED Status|REPORTED|RESOLVED --- Comment #1 from Alexander Nolting --- closed bug due to to feedback from development. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 431563] While closing digikam ist crashed
https://bugs.kde.org/show_bug.cgi?id=431563 Kaj Haulrich changed: What|Removed |Added CC||kajhaulr...@gmail.com Platform|Debian stable |Kubuntu Component|Searches-Engine |general Version|7.1.0 |8.0.0 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 333785] WISH: Would like to have better sticky notes
https://bugs.kde.org/show_bug.cgi?id=333785 Luigi Toscano changed: What|Removed |Added CC||luigi.tosc...@tiscali.it Resolution|UNMAINTAINED|LATER -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 467116] New: Digikam chrashed on exit. Even the appimage not only the deb version.
https://bugs.kde.org/show_bug.cgi?id=467116 Bug ID: 467116 Summary: Digikam chrashed on exit. Even the appimage not only the deb version. Classification: Applications Product: digikam Version: 8.0.0 Platform: Kubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: digikam-bugs-n...@kde.org Reporter: kajhaulr...@gmail.com Target Milestone: --- Created attachment 157147 --> https://bugs.kde.org/attachment.cgi?id=157147&action=edit Crash when quitting digikam SUMMARY Digikam crashes on quitting NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. quit 2. quit 3. quit OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 455394] Vertically-arranged monitors' alignment is off by one pixel
https://bugs.kde.org/show_bug.cgi?id=455394 --- Comment #13 from Thiago Macieira --- I've just seen this again in 5.27.2 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 455394] Vertically-arranged monitors' alignment is off by one pixel
https://bugs.kde.org/show_bug.cgi?id=455394 Thiago Macieira changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #14 from Thiago Macieira --- As kscreen set them: Screen 0: minimum 320 x 200, current 7679 x 2400, maximum 16384 x 16384 eDP-1 connected primary 3840x2400+0+0 (normal left inverted right x axis y axis) 288mm x 180mm 3840x2400 59.99*+ 48.00 DP-3-2 connected 3840x2160+3839+0 (normal left inverted right x axis y axis) 597mm x 336mm 3840x2160 29.98* After xrandr --output DP-3-2 --right-of eDP-1: Screen 0: minimum 320 x 200, current 7680 x 2400, maximum 16384 x 16384 eDP-1 connected primary 3840x2400+0+0 (normal left inverted right x axis y axis) 288mm x 180mm 3840x2400 59.99*+ 48.00 DP-3-2 connected 3840x2160+3840+0 (normal left inverted right x axis y axis) 597mm x 336mm 3840x2160 29.98* -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361623] Notifications is shown in the middle of the screen
https://bugs.kde.org/show_bug.cgi?id=361623 Raman Gupta changed: What|Removed |Added CC||rocketra...@gmail.com --- Comment #10 from Raman Gupta --- I have this highly annoying issue also. Operating System: Fedora Linux 37 KDE Plasma Version: 5.27.0 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.1.12-200.fc37.x86_64 (64-bit) Graphics Platform: X11 Triple-monitor setup, High DPI. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 467117] New: Connections between apps with suspended audio and "Plasma PA" do not disconnect after closing the widget from tray.
https://bugs.kde.org/show_bug.cgi?id=467117 Bug ID: 467117 Summary: Connections between apps with suspended audio and "Plasma PA" do not disconnect after closing the widget from tray. Classification: Plasma Product: plasma-pa Version: 5.27.2 Platform: Archlinux OS: All Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: andrej.h...@gmail.com CC: isma...@gmail.com, m...@ratijas.tk, now...@gmail.com Target Milestone: --- Created attachment 157148 --> https://bugs.kde.org/attachment.cgi?id=157148&action=edit Video demonstration. When viewing "pw-top" or Carla, I can see new audio connections made each time when opening the "Plasma PA" widget (with the Applications tab open) from tray when an app like Firefox or Spotify are paused. The connections immediately disappear when an audio starts playing from the specific apps. This is when using PipeWire, I don't know how (or if) it behaves the same on PulseAudio. STEPS TO REPRODUCE 1. Open an app like Firefox, open a YouTube video and then pause it. 2. Or open Spotify, play something for a second and then pause it. 3. Open "pw-top" in terminal 4. Start opening and closing the Audio Volume (with the Applications shown, not the devices) widget located in the system tray. OBSERVED RESULT "Plasma PA" clients start appearing in pw-top, and only disappear when playing audio from the apps that had their audio paused. EXPECTED RESULT The "Plasma PA" clients should disappear regardless if the audio client has their audio suspended/paused or not. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.2.2 Graphics Platform: Wayland Processors: AMD Ryzen 9 4900HS Memory: 16GB of RAM Graphics Processor: Integrated: Vega 8 Manufacturer: ASUS (Zephyrus G15 GA502IV) -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 467117] Connections between apps with suspended audio and "Plasma PA" do not disconnect after closing the widget from tray.
https://bugs.kde.org/show_bug.cgi?id=467117 Andreas Sturmlechner changed: What|Removed |Added CC||ast...@gentoo.org -- You are receiving this mail because: You are watching all bug changes.
