[krusader] [Bug 413239] [kio_iso] Crash while using Browse ISO plugin
https://bugs.kde.org/show_bug.cgi?id=413239 Toni Asensi Esteve changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||toni.ase...@kdemail.net -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 420868] Random crashes, no error messages. Windows event report follows, suspect TIFF plugin
https://bugs.kde.org/show_bug.cgi?id=420868 --- Comment #5 from Josec --- I am downloading the RC and will install and test tomorrow. I was able to test and reproduce the issue - I have two very large TIFF scans, one is 1.6G and as soon as DigiKam saw the photo in a photo directory, it crashed. As soon as I moved it out of the photos directory, no more problems. BTW, if put it in an "ignored directory", it looks as if DigiKam scans all directories before it ignores it so it even crashed if it was in an ignored directory. I will report back tomorrow on what I find after I install the updated RC. Jose -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 420904] Icons are blurred when fractional scaling is enabled
https://bugs.kde.org/show_bug.cgi?id=420904 Toni Asensi Esteve changed: What|Removed |Added CC||toni.ase...@kdemail.net --- Comment #3 from Toni Asensi Esteve --- Thanks for writing. Does the same happen to you using, for example, Dolphin? -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 420804] Crash in Category::blacklistPluginsInVector() when starting Discover on system update notification
https://bugs.kde.org/show_bug.cgi?id=420804 --- Comment #2 from Kevin Weller --- (In reply to Nate Graham from comment #1) > Please upgrade to Kubuntu 20.04, which is an LTS release like 18.04 and > ships a much newer version of Discover that is less crashy. Thanks! > > *** This bug has been marked as a duplicate of bug 401435 *** After some googling, there doesn't appear to be ab upgrade path from Kubuntu 18.04 LTS to 20.04 LTS yet, not until this Summer at least? But I do have other tools beasides Discover for OS updates. -- You are receiving this mail because: You are watching all bug changes.
[krename] [Bug 420940] Krename Notifications do not disappear even after completion
https://bugs.kde.org/show_bug.cgi?id=420940 --- Comment #1 from Peter --- To add a bit more detail. 1) Open up Krename 2) edit in the interface adding suffix to files to rename 3) can see the potential changes made in the Krename window 4) press finish) Observed result A small window appears showing over all progress Notifications pop up in system tray (Plasma notification area by clock) Small window updates at the end saying finished, giving options to re open Krename, close etc and I close that window Files were successfully renamed. But! the notifications continue in the system tray/ notification see screen shot, I can not cancel them. Expected result should be as above but in addition the notification pop up should show completed and minimize/disapear -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 276683] Krusader includes various 3rd party code that is not updated
https://bugs.kde.org/show_bug.cgi?id=276683 Davide Gianforte changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #1 from Davide Gianforte --- Tar code is no more used. Libisofs does not provide relevant changes to the current code. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 396543] Bookmark context sub-menus opens near mouse
https://bugs.kde.org/show_bug.cgi?id=396543 Davide Gianforte changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|CONFIRMED |NEEDSINFO --- Comment #5 from Davide Gianforte --- Can you confirm on a system with a newer QT? With the same Krusader code, I can reproduce with QT 5.13.2 (the one shipped in Slackware) and not with 5.14.2 (built from source with the same configuration as 5.13.2). -- You are receiving this mail because: You are watching all bug changes.
[krename] [Bug 420940] New: Krename Notifications do not disappear even after completion
https://bugs.kde.org/show_bug.cgi?id=420940 Bug ID: 420940 Summary: Krename Notifications do not disappear even after completion Product: krename Version: 5.0.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: heire...@exherbo.org Reporter: e...@protonmail.ch Target Milestone: --- Created attachment 128108 --> https://bugs.kde.org/attachment.cgi?id=128108=edit list of neaver ending rename activities SUMMARY Plasma Notifications of renaming progress do not disappear. Not sure if this a bug in Plasma widget/notification area or Krename. I cannot seem to dismiss the progress bars for each successfully renamed file. I just have to log out and log back in again. I am not seeing this issue for other progress file actions like copying files. STEPS TO REPRODUCE 1. Select files to rename on a network share 2. Press Finish 3. Progress is displayed in notifications but do not disapear even after successful rename. 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.
[krusader] [Bug 399735] help does not work
https://bugs.kde.org/show_bug.cgi?id=399735 Davide Gianforte changed: What|Removed |Added CC||dav...@gengisdave.org Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from Davide Gianforte --- Is the problem still present? Did you tried to reinstall Krusader? -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 403573] Will not save directory for Syncronize Folders
https://bugs.kde.org/show_bug.cgi?id=403573 Davide Gianforte changed: What|Removed |Added CC||dav...@gengisdave.org Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #2 from Davide Gianforte --- Can you reproduce the problem? I can save sync profile (checked in krusaderrc) and restore it. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 412013] Wrong typeset of numbers in tab inscription
https://bugs.kde.org/show_bug.cgi?id=412013 Davide Gianforte changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO CC||dav...@gengisdave.org --- Comment #2 from Davide Gianforte --- As in comment #1, it seems to be a problem with the system, is the problem still present? -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 376983] Krusader filename capitalization and show directory size in Window in MB
https://bugs.kde.org/show_bug.cgi?id=376983 Davide Gianforte changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED CC||dav...@gengisdave.org --- Comment #2 from Davide Gianforte --- No response, closing -- You are receiving this mail because: You are watching all bug changes.
[kfile-plugins] [Bug 420939] New: Baloo purge not completing
https://bugs.kde.org/show_bug.cgi?id=420939 Bug ID: 420939 Summary: Baloo purge not completing Product: kfile-plugins Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: fa...@kde.org Reporter: shagooser...@gmail.com Target Milestone: --- Created attachment 128107 --> https://bugs.kde.org/attachment.cgi?id=128107=edit output of running baloo purge SUMMARY command: baloo purge hangs and does not complete, repeatedly STEPS TO REPRODUCE 1. baloo purge 2. 3. OBSERVED RESULT see attached output then terminal just hangs with no prompt EXPECTED RESULT That the baloo database is entirely empty SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 Baloo Version: 5.68.0 ADDITIONAL INFORMATION I have performed purge 5 times because after each purge baloo status each time came back with a database of thousands of entries. For the last 3 times it reported the same 3949 entries despite the fact it appeared to be doing something. The initial status before the first purge was over 9000 records. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 418798] Hide maximized window's title by using kwinscript
https://bugs.kde.org/show_bug.cgi?id=418798 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #4 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 381966] Bethesda Software Archive
https://bugs.kde.org/show_bug.cgi?id=381966 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #4 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 419577] Audio doesn't play on playback. When the timeline doctor is stretched, you can hear fragments of the audio
https://bugs.kde.org/show_bug.cgi?id=419577 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 420245] Bottom panel missing each time after reboot
https://bugs.kde.org/show_bug.cgi?id=420245 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 419548] Krita stuck in pan mode when using drawing tablet
https://bugs.kde.org/show_bug.cgi?id=419548 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 401677] Some phone models, ROMs or Apps don't report SMS History
https://bugs.kde.org/show_bug.cgi?id=401677 --- Comment #46 from zirkov...@gmail.com --- This is a core feature that I want for an app like this. Until this is fixed I don't think anyone with a galaxy S8 should use this app. They should find an alternative. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 416758] Encoding broken
https://bugs.kde.org/show_bug.cgi?id=416758 Oliver Kurz changed: What|Removed |Added CC||ok...@suse.de -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 420938] New: Discover crashes on start
https://bugs.kde.org/show_bug.cgi?id=420938 Bug ID: 420938 Summary: Discover crashes on start Product: Discover Version: 5.18.3 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: pans...@gmail.com CC: aleix...@kde.org Target Milestone: --- Application: plasma-discover (5.18.3) Qt Version: 5.12.4 Frameworks Version: 5.67.0 Operating System: Linux 5.3.0-42-generic x86_64 Windowing system: X11 Distribution: Ubuntu 19.10 -- Information about the crash: Discover crashed on start. Neither reinstall nor purge and install of Discover solved it. The crash can be reproduced every time. -- Backtrace: Application: Discover (plasma-discover), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fd9ccd483c0 (LWP 12565))] Thread 11 (Thread 0x7fd9a27fc700 (LWP 12580)): #0 futex_abstimed_wait_cancelable (private=, abstime=0x7fd9a27fbbd0, clockid=, expected=0, futex_word=0x556558918d70) at ../sysdeps/unix/sysv/linux/futex-internal.h:208 #1 __pthread_cond_wait_common (abstime=0x7fd9a27fbbd0, clockid=, mutex=0x556558918d20, cond=0x556558918d48) at pthread_cond_wait.c:520 #2 __pthread_cond_timedwait (cond=0x556558918d48, mutex=0x556558918d20, abstime=0x7fd9a27fbbd0) at pthread_cond_wait.c:656 #3 0x7fd9d107dd2c in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fd9d107de7b in QWaitCondition::wait(QMutex*, unsigned long) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fd9d107b421 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fd9d1077c92 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fd9d007c669 in start_thread (arg=) at pthread_create.c:479 #8 0x7fd9d0cfa323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 10 (Thread 0x7fd9a2ffd700 (LWP 12579)): #0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 #1 0x7fd9d107a081 in QSemaphore::acquire(int) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7fd9d126a875 in QMetaObject::activate(QObject*, int, int, void**) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7fd9d06eef00 in ?? () from /lib/x86_64-linux-gnu/libQt5Network.so.5 #4 0x7fd9d07a5874 in ?? () from /lib/x86_64-linux-gnu/libQt5Network.so.5 #5 0x7fd9d126a3f8 in QMetaObject::activate(QObject*, int, int, void**) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fd9d06e4985 in ?? () from /lib/x86_64-linux-gnu/libQt5Network.so.5 #7 0x7fd9d06e524b in ?? () from /lib/x86_64-linux-gnu/libQt5Network.so.5 #8 0x7fd9d126a3f8 in QMetaObject::activate(QObject*, int, int, void**) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7fd9d079e9d3 in ?? () from /lib/x86_64-linux-gnu/libQt5Network.so.5 #10 0x7fd9d0792b5e in ?? () from /lib/x86_64-linux-gnu/libQt5Network.so.5 #11 0x7fd9d0792fa6 in ?? () from /lib/x86_64-linux-gnu/libQt5Network.so.5 #12 0x7fd9d076cd13 in ?? () from /lib/x86_64-linux-gnu/libQt5Network.so.5 #13 0x7fd9d126a3f8 in QMetaObject::activate(QObject*, int, int, void**) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x7fd9d072f834 in ?? () from /lib/x86_64-linux-gnu/libQt5Network.so.5 #15 0x7fd9d072f8cf in ?? () from /lib/x86_64-linux-gnu/libQt5Network.so.5 #16 0x7fd9d0741db9 in ?? () from /lib/x86_64-linux-gnu/libQt5Network.so.5 #17 0x7fd9d21b3a86 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #18 0x7fd9d21bce00 in QApplication::notify(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #19 0x7fd9d123ea2a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #20 0x7fd9d1297295 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #21 0x7fd9cf7f98bd in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #22 0x7fd9cf7f9b40 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #23 0x7fd9cf7f9be3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #24 0x7fd9d1296635 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #25 0x7fd9d123d5cb in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #26 0x7fd9d1076a45 in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #27 0x7fd9d1077c92 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #28 0x7fd9d007c669 in start_thread (arg=) at pthread_create.c:479 #29 0x7fd9d0cfa323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 9 (Thread 0x7fd9a37fe700 (LWP 12577)): #0 __GI___libc_read (nbytes=16, buf=0x7fd9a37fdbd0, fd=28) at
[systemsettings] [Bug 420937] New: Desktop Effects / Show/Hide Video
https://bugs.kde.org/show_bug.cgi?id=420937 Bug ID: 420937 Summary: Desktop Effects / Show/Hide Video Product: systemsettings Version: 5.18.4 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: hdcomputerke...@gmail.com Target Milestone: --- Application: systemsettings5 (5.18.4) Qt Version: 5.12.8 Frameworks Version: 5.68.0 Operating System: Linux 5.4.0-26-generic x86_64 Windowing system: X11 Distribution: Ubuntu 20.04 LTS -- Information about the crash: clicked on Settings/ Workspace Behavior/Desktop Effects/ Most of time closes itself only when I go to see a Show/Hide Video (see what it looks like before changing, u know, love it) Other than that feature, woroks fine ya'll, love KDE - Unusual behavior I noticed: - Custom settings of the application: The crash can be reproduced every time. -- Backtrace: Application: System Settings (systemsettings5), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f8988fd6800 (LWP 28865))] Thread 10 (Thread 0x7f8961205700 (LWP 28877)): #0 0x7f898b1bb6f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f898b1bd185 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f898b1beaff in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f898b1bf152 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f898b1bf2e3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f898d485583 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f898d42c4db in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f898d264785 in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f898c5171a9 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #9 0x7f898d2659d2 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f898baa3609 in start_thread (arg=) at pthread_create.c:477 #11 0x7f898cef6103 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 9 (Thread 0x7f89635ef700 (LWP 28874)): #0 0x7fffbf3d6933 in clock_gettime () #1 0x7f898ceb4235 in __GI___clock_gettime (clock_id=1, tp=0x7f89635eeaf0) at ../sysdeps/unix/sysv/linux/clock_gettime.c:38 #2 0x7f898d484e45 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f898d4836dd in QTimerInfoList::updateCurrentTime() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f898d483cb9 in QTimerInfoList::timerWait(timespec&) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f898d4852d6 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f898b1be72f in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7f898b1bf0db in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #8 0x7f898b1bf2e3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #9 0x7f898d485583 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f898d42c4db in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7f898d264785 in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7f898c5171a9 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #13 0x7f898d2659d2 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x7f898baa3609 in start_thread (arg=) at pthread_create.c:477 #15 0x7f898cef6103 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 8 (Thread 0x7f897da5a700 (LWP 28873)): #0 0x7f898b18eae4 in g_ptr_array_set_size () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f898b1be62e in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f898b1bf0db in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f898b1bf2e3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f898d485583 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f898d42c4db in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f898d264785 in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f898c5171a9 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #8 0x7f898d2659d2 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f898baa3609 in start_thread (arg=) at pthread_create.c:477 #10 0x7f898cef6103 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 7 (Thread 0x7f897effd700 (LWP 28871)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x56373114192c) at ../sysdeps/nptl/futex-internal.h:183 #1
[dolphin] [Bug 417400] Feature to create new folder containing selected items
https://bugs.kde.org/show_bug.cgi?id=417400 José changed: What|Removed |Added CC||panchopap...@gmail.com --- Comment #1 from José --- This feature is really useful, especially when you are ordering several files in different folders, but there's not that sorting option (it can be an arbitrary criterion) I could use for a certain requirement -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 420936] New: The text box has remnant text in its original size when trying to resize it smaller than the minimum size after altering text.
https://bugs.kde.org/show_bug.cgi?id=420936 Bug ID: 420936 Summary: The text box has remnant text in its original size when trying to resize it smaller than the minimum size after altering text. Product: krita Version: 4.2.9 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: grave Priority: NOR Component: Tool/Text Assignee: krita-bugs-n...@kde.org Reporter: atomicboy...@gmail.com Target Milestone: --- SUMMARY There is a problem with the text tool and resizing. STEPS TO REPRODUCE 0. Create a canvas of dimensions 800 by 1280. 1. Create a text box using the SVG Text Tool. It doesn't matter if the selected region for the text box is entirely within the canvas or partially out of the canvas. 2. Write out some arbitrary text (the default latin text may be used) and set the size to be the minimum of 6. 3. Resize the text box to be considerably smaller, both in length and width, using the "Transform a layer or a selection" tool. You can do this by dragging the corners of the text after selecting the tool. 4. Alter the text again, using the tool in step 1, preferrably by adding more text (a single letter will do). 5. Attempt to resize again using that same tool in step 3. OBSERVED RESULT There is an arbitrary remnant of text in the original size that is past the text you just rewrote. EXPECTED RESULT It should just be the text you've already written that is visible and able to be resized. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION This is problematic for me, a manga creator, who wishes to fit small text into my pages. The default minimum size of 6 is way too large for me, so I always resize the text box using the tool mentioned in step 3. But that remnent that appears is really problematic if the text I am trying to place is on the left hand side of the canvas and the remnent is on the canvas, possibly obscuring stuff I don't want to be obscured. And I can't get rid of it. I just have to depend on it to be out of the canvas area. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 416145] Krunner doesn't immediately intercept keystrokes, leading the user to accidentally type text into whatever app is open
https://bugs.kde.org/show_bug.cgi?id=416145 ariasuni changed: What|Removed |Added CC||pe...@hack-libre.org --- Comment #11 from ariasuni --- Hi, I still have this issue in Plasma 5.18.4.1. I’m not sure I’m running a version with the improvements of David Edmundson, though. I think that this issue is important because it can give the impression that Plasma is slow or buggy. Regularly, *even when KRunner is already started*, the first letter I type after using the keyboard shortcut is entered in the wrong place (aka in my browser or my code editor), on a powerful laptop. It’s very annoying because I may not have noticed I typed a letter in the wrong place, thinking the letter was just «lost», because when invoking Krunner I’m already thinking of the next task and I don’t remember where my cursor/focus was. So starting KRunner ahead of time is not a working workaround for me, because my issue is the time an already opened Krunner take to capture input. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 420917] Looped bash script (unfinished command) holds plasma_session startup
https://bugs.kde.org/show_bug.cgi?id=420917 --- Comment #2 from Evgen --- (In reply to David Edmundson from comment #1) > Fixing that would break other use cases as we have to source env variables > from that into our running environment. Sure. now I understand that this folder is primarily for env variables which must be set before starting anything else in session. By the way, some locations are not easily discoverable for an inexperienced user ... Hope with Plasma 6 structure would be reconsidered. > > The scripts doing what you're describing are probably best suited for the > .local/share/autostart-scripts these are run async and even if broken won't > lock startup. Thank you! Just a small correction: it's .config/autostart-scripts -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 420791] "%"-symbol in bookmark address appears like "%25"
https://bugs.kde.org/show_bug.cgi?id=420791 Nate Graham changed: What|Removed |Added Version Fixed In||20.08.0 CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 420791] "%"-symbol in bookmark address appears like "%25"
https://bugs.kde.org/show_bug.cgi?id=420791 Kurt Hindenburg changed: What|Removed |Added Latest Commit||https://invent.kde.org/kde/ ||konsole/commit/d3519ae24c0d ||e218b3a2c0728fb4da519574044 ||a Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #6 from Kurt Hindenburg --- Git commit d3519ae24c0de218b3a2c0728fb4da519574044a by Kurt Hindenburg, on behalf of Yaroslav Sidlovsky. Committed on 03/05/2020 at 01:59. Pushed by hindenburg into branch 'master'. Use Qurl::fromPercentEncoding for bookmarks This will allow % in URLs; also sync test code with actual code. Previously the tests were using toUtf8(); however fromPercentEncoding seems better. Differential Revision: https://phabricator.kde.org/D29322 M +2-1src/SessionController.cpp M +4-4src/autotests/BookMarkTest.cpp https://invent.kde.org/kde/konsole/commit/d3519ae24c0de218b3a2c0728fb4da519574044a -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 420695] Dolphin crashes when closing terminal via "Close Session"
https://bugs.kde.org/show_bug.cgi?id=420695 arshad.husa...@gmail.com changed: What|Removed |Added Assignee|arshad.husa...@gmail.com|dolphin-bugs-n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 419625] System settings crashed when playing with Display configuration in QQuickWindow::MouseGrabbItem
https://bugs.kde.org/show_bug.cgi?id=419625 Nate Graham changed: What|Removed |Added Version Fixed In||5.19.0 CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 420769] Font rendering is different (not quite as sharp) in applications that use Kirigami
https://bugs.kde.org/show_bug.cgi?id=420769 Nate Graham changed: What|Removed |Added Summary|Font rendering super blurry |Font rendering is different |in applications that use|(not quite as sharp) in |Kirigami|applications that use ||Kirigami Status|NEEDSINFO |CONFIRMED Resolution|WAITINGFORINFO |--- Ever confirmed|0 |1 Severity|normal |minor --- Comment #3 from Nate Graham --- Ah, I see it now. I don't think I ever would have if you hadn't pointed it out though! Doesn't looks like Plasma is affected, so it's not all QML software that's affected. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 353983] Turning off compositing breaks Plasma panel rendering
https://bugs.kde.org/show_bug.cgi?id=353983 --- Comment #171 from Alex Barrero --- Finally!! Thanks for the fix! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 353983] Turning off compositing breaks Plasma panel rendering
https://bugs.kde.org/show_bug.cgi?id=353983 --- Comment #170 from Nate Graham --- That's great news! Once there's a fix, can you include a link to it in the URL field of this bug, and put the version of the driver that includes the fix in the Version fixed in field? Thanks! I'll keep this open since some people are saying that they experience this with Intel drivers too; perhaps they will require a driver fix as well. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected
https://bugs.kde.org/show_bug.cgi?id=356225 --- Comment #335 from Michael Butash --- I did do some upgrades to my system that helped fix general stability (removing i915 driver, moving to nvidia with modern xorg in arch), but still I run into weirdness with the displays resize/relocate/forget whenever they change, which is quite often with my laptop. Part of this seems related to the control-center settings, not sure where to even bark about it, as it loses its settings _every_ time my displays go to sleep. I set it back up in display with no less than some 10-15 clicks, sometimes unplug/plug the TB3, and get it back working. I eat lunch, come back, I have to reset everything again. My case, I have my laptop on the 15" local display, 4k/60hz. Never an issue with built-in, but same res/refresh as externals. Second and Third are two Samsung 48" 4k/60hz tv's, attached via a Thunderbolt dock. KDE has to figure these out each time from scratch oddly, and still always breaks windows sizing on a number of apps. This is the worst, as it makes them like 20px by 1080px for some unfathomable reason, rather even hard to find when juggled randomly. There are some odd issues with the TB3 dock too. It is a CalDigit USB-C Pro Dock from amazon, using 2x DP-to-HDMI2.0 cables that usually work great to my displays when they're awake. When they power down, or I shut them down, the dock seems to treat them both entirely different for what xrandr -Q reports during the time they power down, which is I think what is really killing KDE, but the fact it cannot even remember a default setting for each time, is what makes it worse. I get everything from the display settings in control-panel fighting me to move displays, to changing the resolution and refresh each time. First step is to remove and reconnect the TB3 cable each morning, or the displays pop up in reverse. Control panel shows them and left-to-right, but is just literally backward. Disconnecting the TB3 and back in resets the left/right, but resets my resolution and refresh again, even though xrandr -Q shows right now. Just really wonky, inconsistent behavior with kde display handling, and at this point it's like groundhog day, but less funny. All I want KDE to do after some 15 years is 1) remember my display config, and 2) put things apps/windows back where I had them from before. Hardware/drivers/etc complicate it, but KDE has had a notoriously bad handling of Multi-monitor settings over years since 4.x, this ticket alone ~5yr. -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 395461] multiple video support
https://bugs.kde.org/show_bug.cgi?id=395461 --- Comment #4 from J --- If this is fixed in KDEconnect (https://invent.kde.org/kde/kdeconnect-kde/merge_requests/153), is it possible to implement it in a similar way on the Desktop Plasmoid? -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 415241] Trouble opening an MTP device
https://bugs.kde.org/show_bug.cgi?id=415241 yourjunkher...@yahoo.com changed: What|Removed |Added CC||yourjunkher...@yahoo.com --- Comment #2 from yourjunkher...@yahoo.com --- I've seen this problem with a Samsung S7. Possible related: https://bugs.kde.org/show_bug.cgi?id=411489 -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 420926] No control over multiple or different playback sources
https://bugs.kde.org/show_bug.cgi?id=420926 --- Comment #2 from J --- Sorry, i searched a few times but couldn't find something similar. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 353983] Turning off compositing breaks Plasma panel rendering
https://bugs.kde.org/show_bug.cgi?id=353983 Erik Kurzinger changed: What|Removed |Added CC||ekurzin...@nvidia.com --- Comment #169 from Erik Kurzinger --- Took a look at this from the NVIDIA side and determined that it is a bug in our X driver. KWin / plasmashell aren't doing anything wrong. Should be able to get a fix out in an upcoming driver release. I'll include an entry in the change log mentioning the issue. -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 420933] kdesrc-build fails to update modules randomly (git stash failure)
https://bugs.kde.org/show_bug.cgi?id=420933 --- Comment #2 from Michael Pyne --- Git commit 5019317f41977d67f1932cacb68850bda83ec73b by Michael Pyne. Committed on 02/05/2020 at 23:21. Pushed by mpyne into branch 'master'. git: Capture basic git-status info before error-prone ops. There have long been bug reports around git-stash handling. I just had to enter another one, but it's hard to troubleshoot what git was seeing after the fetch and rebase has already happened, even if you try to rewind with reflog. For now this will just run a simple 'git-status' as a smoke check before the update, and optionally if a stash or error occur. My hope is this will permit more detail to be provided with subsequent bug reports. M +6-0modules/ksb/Updater/Git.pm https://invent.kde.org/kde/kdesrc-build/commit/5019317f41977d67f1932cacb68850bda83ec73b -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 420935] New: "Edit Shapes Tool" is called "Path Editing" in Keyboard Shortcuts
https://bugs.kde.org/show_bug.cgi?id=420935 Bug ID: 420935 Summary: "Edit Shapes Tool" is called "Path Editing" in Keyboard Shortcuts Product: krita Version: git master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Shortcuts and Canvas Input Settings Assignee: krita-bugs-n...@kde.org Reporter: tamtamy.tym...@gmail.com Target Milestone: --- SUMMARY The name of the tool doesn't match the name of the shortcut in Keyboard Shortcuts STEPS TO REPRODUCE 1. Hover your cursor over the Edit Shapes Tool. It says: "Edit Shapes Tool". 2. Go to Configure Krita -> Keyboard Shortcuts. Try to find Edit Shapes Tool. 3. Search for "Path Editing". Assign a shortcut to it. 4. Try the shortcut. OBSERVED RESULT "Path editing" shortcut switches to the Edit Shapes Tool. EXPECTED RESULT The shortcut is called "Edit Shapes Tool" because that's how the tool is called now. Note: afaik Select Shapes Tool was also called differently in the past but the shortcut name matches. SOFTWARE/OS VERSIONS Krita Version: 4.3.0-prealpha (git ea7c856) Languages: pl, pl_PL, pl Hidpi: true Qt Version (compiled): 5.11.1 Version (loaded): 5.11.1 OS Information Build ABI: x86_64-little_endian-lp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: linux Kernel Version: 5.3.7-050307-generic Pretty Productname: Linux Mint 19.3 Product Type: linuxmint Product Version: 19.3 Desktop: X-Cinnamon -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 420933] kdesrc-build fails to update modules randomly (git stash failure)
https://bugs.kde.org/show_bug.cgi?id=420933 Michael Pyne changed: What|Removed |Added CC||fa...@kde.org --- Comment #1 from Michael Pyne --- David, I'm not able to immediately resolve so entering a bug. I will update kdesrc-build to include 'git-status' output before update and stash operations to potentially improve on the error reporting available. I suspect something to do with long periods of changes between updates. For clarity in case you look yourself, the basic sequence kdesrc-build for updates to existing modules is: cd $srcdir git fetch --tags $remote DO_STASH = git diff-index --quiet HEAD != 0 if DO_STASH: git stash save --quiet git checkout $branch ; unconditionally done git rebase origin/$branch if DO_STASH: git stash pop -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 419305] Have transparent icons in systray
https://bugs.kde.org/show_bug.cgi?id=419305 --- Comment #26 from Dacha204 --- (In reply to Konrad Materka from comment #25) > Thank you detailed report! > > I have few more questions: > > * To open System Tray settings, right click on the arrow - will show a menu > with "Configure System Tray..." entry. This way you can access settings. > > * From that bug occurrence you sent screenshots, do you have errors like > this in logs? > file:///usr/share/plasma/plasmoids/org.kde.plasma.private.systemtray/ > contents/ui/items/StatusNotifierItem.qml: > My guess is that no, because tooltips are working, but it is worth to > confirm. * Sorry, my bad about system tray settings. Icons in settings dialog are actually rendered correctly: https://imgur.com/toPZdaN * About tooltips and icons, it seems that not all of them are rendered correctly: https://imgur.com/IHbYVKI In this GIF, I placed the second instance of the system tray side by side (the left one is new). On reboot, both of them are broken. * I do have errors in logs $ journalctl -b | grep org.kde.plasma.private.systemtray May 03 00:38:25 dacha204-linux plasmashell[2143]: file:///usr/share/plasma/plasmoids/org.kde.plasma.private.systemtray/contents/ui/items/StatusNotifierItem.qml: ReferenceError: Icon is not defined May 03 00:38:25 dacha204-linux plasmashell[2143]: file:///usr/share/plasma/plasmoids/org.kde.plasma.private.systemtray/contents/ui/items/StatusNotifierItem.qml:59: ReferenceError: Icon is not defined May 03 00:38:26 dacha204-linux plasmashell[2143]: file:///usr/share/plasma/plasmoids/org.kde.plasma.private.systemtray/contents/ui/items/StatusNotifierItem.qml:51: ReferenceError: Icon is not defined These 3 different lines are repeating * Something that I discovered in the meantime and can reproduce: The system tray icon for Blueman-manager (GTK+ app; bluetooth icon) reappears when I edit panel. Also, the tooltip icon is rendered correctly. As shown in this GIF: https://imgur.com/1yS7JqX Note: flickering is only visible in GIF. Recorded using Peek -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 420934] New: Tooltips of Touchpad applet in systray and some widgets added to plasma panel still have an icon on Neon unstable
https://bugs.kde.org/show_bug.cgi?id=420934 Bug ID: 420934 Summary: Tooltips of Touchpad applet in systray and some widgets added to plasma panel still have an icon on Neon unstable Product: plasmashell Version: master Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: bugsefor...@gmx.com Target Milestone: 1.0 Created attachment 128106 --> https://bugs.kde.org/attachment.cgi?id=128106=edit screen recording SUMMARY On master branch the icons of tooltips shown by systray icons and widgets placed on plasma panel were removed. However, the Touchpad applet in systray and the following widgets added to plasma panel are still showing an icon in their tooltips: show desktop minimize all windows trash touchpad quicklaunch quick share lock/logout activities STEPS TO REPRODUCE 1. enable the Touchpad applet in systray settings 2. add any of the widgets mentioned above to plasma panel 3. hover over the Touchpad applet in systray and the just added widget OBSERVED RESULT tooltip with an icon. Watch the attached screen recording please. EXPECTED RESULT tooltip without icon SOFTWARE/OS VERSIONS Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.18.80 KDE Frameworks Version: 5.70.0 Qt Version: 5.14.2 -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 420933] New: kdesrc-build fails to update modules randomly (git stash failure)
https://bugs.kde.org/show_bug.cgi?id=420933
Bug ID: 420933
Summary: kdesrc-build fails to update modules randomly (git
stash failure)
Product: kdesrc-build
Version: Git
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: mp...@kde.org
Reporter: mp...@kde.org
Target Milestone: ---
Created attachment 128105
--> https://bugs.kde.org/attachment.cgi?id=128105=edit
kdesrc-build logs from my failed kactivitymanagerd run
SUMMARY
dfaure reports that kdesrc-build can consider a module failed to update (even
though it successfully fetches updates from the git server and successfully
rebases the module to the updated 'master' branch). It complains about being
unable to restore stashed local changes. See
https://invent.kde.org/snippets/868. The pertinent error:
user@localhost:~/release-tools$ cd ../src && ./kdesrc-build --src-only
Updating kde-build-metadata (to branch master)
Local changes detected, stashing them away...
Module updated, reapplying your local changes.
*
* Unable to re-apply stashed changes to kde-build-metadata!
*
* These changes were saved using the name "kdesrc-build auto-stash at
2020-05-02-21:48"
* and should still be available using the name stash@{0}, the command run
* to re-apply was git stash pop --index. Resolve this before you run
* kdesrc-build to update this module again.
*
* If you do not desire to keep your local changes, then you can generally
run
* git reset --hard HEAD, or simply delete the source directory for
* kde-build-metadata. Developers be careful, doing either of these options
will remove
* any of your local work.
* Unable to download required metadata for build process
* Will attempt to press onward...
* Exception message: Runtime Error: Failed to re-apply stashed changes for
kde-build-metadata
STEPS TO REPRODUCE
1. Change to desired config directory
2. Run kdesrc-build --src-only
OBSERVED RESULT
Modules randomly fail to update complaining of re-application of stashed
changes. Different modules fail on subsequent builds.
[18:17] thanks
[18:17] it seems like ot happened randomly in various repos
[18:17] it
[18:17] git version 2.26.1, if it matters
[18:33] mpyne happened twice in a row upon "kdesrc-build frameworks",
but on different modules every time
[18:34] thanks
[18:34] mpyne: once kde-build-metadata, once kio and kdesrc-build
itself... pretty random
In my own testing from an old checkout, applying to master as of 2020-05-02, I
had one module fail for this reason, kactivitymanagerd. I believe this may be
related to a commit that removed a file, but I cannot understand what situation
kactivitymanagerd had been in before that would have led kdesrc-build to think
a local change had occurred. I was not able to reproduce random modules having
this failure.
EXPECTED RESULT
The source code modules cleanly update, since there were no local modifications
to worry about.
SOFTWARE/OS VERSIONS
kdesrc-build: v19.12-44-geaf569d
ADDITIONAL INFORMATION
There have been recent changes to git-stash handling to fix other "fake local
change detected" bugs.
--
You are receiving this mail because:
You are watching all bug changes.
[kdesrc-build] [Bug 420486] Bump Qt5 requirement to match other packages requirements
https://bugs.kde.org/show_bug.cgi?id=420486 Michael Pyne changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from Michael Pyne --- Thanks. This has been applied on git master. See https://invent.kde.org/kde/kdesrc-build/-/merge_requests/28 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 420932] New: TIFF images with display resolution stored in pels/cm is displayed as ppi in image/properties panel
https://bugs.kde.org/show_bug.cgi?id=420932 Bug ID: 420932 Summary: TIFF images with display resolution stored in pels/cm is displayed as ppi in image/properties panel Product: krita Version: git master Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: boxe...@gmail.com Target Milestone: --- Created attachment 128104 --> https://bugs.kde.org/attachment.cgi?id=128104=edit TIFF image with pixels/cm stored 1. run tiffinfo on attached image - resolution stored as 118 pixels / cm 2. Open attached image, and then open image / properties resolution is displayed as 118 pixels / inch -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 420784] Restore of Vaults fail
https://bugs.kde.org/show_bug.cgi?id=420784 --- Comment #5 from Nate Graham --- Ah of course, I forgot the activity integration. If you're right though, then IMO there's a real bug here. When a user restores their system, their vaults shouldn't disappear due to the implementation detail that the UUID of the activity they were assigned to on the old system is no longer valid on the new system. A vault becoming inaccessible after restoring from backup amounts to data loss. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 420889] Shift+scroll wheel behavior broke
https://bugs.kde.org/show_bug.cgi?id=420889 Nate Graham changed: What|Removed |Added Priority|NOR |VHI Keywords||regression Ever confirmed|0 |1 Status|REPORTED|CONFIRMED Summary|Shift+scroll wheel |Shift+scroll wheel behavior |behaviour changed |broke --- Comment #1 from Nate Graham --- Can confirm. I didn't even know this feature existed! -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 417463] icons of GTK2 apps are barely visible or invisible after I set global theme to Breeze Dark
https://bugs.kde.org/show_bug.cgi?id=417463 Nate Graham changed: What|Removed |Added CC||benjamin.p...@enioka.com -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 412331] Background colors in Gimp and Inkscape do not match kde color scheme in plasma 5.17beta
https://bugs.kde.org/show_bug.cgi?id=412331 Nate Graham changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED --- Comment #17 from Nate Graham --- Mush be a separate issue then. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 417463] icons of GTK2 apps are barely visible or invisible after I set global theme to Breeze Dark
https://bugs.kde.org/show_bug.cgi?id=417463 Nate Graham changed: What|Removed |Added Resolution|DUPLICATE |--- Ever confirmed|0 |1 Status|RESOLVED|REOPENED -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 420893] Icon for Anydesk
https://bugs.kde.org/show_bug.cgi?id=420893 Nate Graham changed: What|Removed |Added Summary|REQUEST [ICON FOR ANYDESK] |Icon for Anydesk CC||n...@kde.org Severity|normal |wishlist --- Comment #1 from Nate Graham --- Sure, go ahead. -- You are receiving this mail because: You are watching all bug changes.
[kshisen] [Bug 420915] Games displayed rotate around 5 or 6 layouts
https://bugs.kde.org/show_bug.cgi?id=420915 --- Comment #2 from Dave S. --- Only checked: Create solvable games only Board Difficulty: at center line Piece Removal Speed: at center line Board Size: 18x8 On 5/2/20 1:28 PM, Frederik Schwarzer wrote: > https://bugs.kde.org/show_bug.cgi?id=420915 > > --- Comment #1 from Frederik Schwarzer --- > Hi, > > Thank you for your report. > > I just tried it on my machine with the same version of KShisen and the first > 20 > games were different. > > Can you please tell us your settings found at: > Settings -> Configure Shisen-Sho... -> General > > Thanks > -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 420931] New: Crash in "Edit loan Wizard"
https://bugs.kde.org/show_bug.cgi?id=420931 Bug ID: 420931 Summary: Crash in "Edit loan Wizard" Product: kmymoney Version: git (master) Platform: Appimage OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: eu...@albiker.org Target Milestone: --- Created attachment 128103 --> https://bugs.kde.org/attachment.cgi?id=128103=edit Video of the crash SUMMARY When I "modify loan attributes" the "edit loan wizard" crash. This happens if I deleted the "schedules transaction" befor STEPS TO REPRODUCE 1. Create a loan ledger 2. Delete the scheduled transaction for the loan 3. edit the "load attributes" twice(!) OBSERVED RESULT Crash of kmymoney EXPECTED RESULT no crash SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Frameworks 5.68.0 Qt 5.12.8 (kompiliert gegen 5.12.8) Das xcb Fenstersystem ADDITIONAL INFORMATION kmymoney version "KMyMoney-5.0.8-332b888-x86_64.AppImage" Enclosed I have made a video :-) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 418039] DigiKam - importing from camera onto removable media
https://bugs.kde.org/show_bug.cgi?id=418039 --- Comment #5 from Mihaela --- I have in the meantime moved from Plasma to GNOME, and I haven't noticed any crashes. Kwin did crash a lot for me related to some Plasma animations (reported), unrelated to digiKam, so maybe this bug is related to Kwin. But there is one other difference that may be related: in Plasma KDE the remote media path inside digiKam was /media/username/longdevicename/Photos/ but the same location now on GNOME is /mnt/longdevicename/Photos/. When setting up the collection in GNOME I chose the removable media option, but digiKam still added it under Local, I guess it matters if the device is automounted? I haven't removed KDE yet so I can login back if you'd like me to run backtrace again. I installed kwin-dev package. Is it safe for me to do that? I don't want that to affect my collection in a bad way. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 420695] Dolphin crashes when closing terminal via "Close Session"
https://bugs.kde.org/show_bug.cgi?id=420695 Tobias Fella changed: What|Removed |Added CC||fe...@posteo.de Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #5 from Tobias Fella --- (In reply to arshad.husa...@gmail.com from comment #2) > I apologize but I can't seem to replicate this bug. I have the same KF5 > version and the same distro but my Qt5 version is 5.14.2. I have a hunch > that whatever it was that was causing this issue was fixed in Qt 5.14.2. I can reproduce it in 5.14.2, so it's not fixed. I'm currently looking into it. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 420917] Looped bash script (unfinished command) holds plasma_session startup
https://bugs.kde.org/show_bug.cgi?id=420917 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #1 from David Edmundson --- Fixing that would break other use cases as we have to source env variables from that into our running environment. The scripts doing what you're describing are probably best suited for the .local/share/autostart-scripts these are run async and even if broken won't lock startup. -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 420929] New: Bad working printing in dark theme
https://bugs.kde.org/show_bug.cgi?id=420929 Bug ID: 420929 Summary: Bad working printing in dark theme Product: cantor Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: cantor-b...@kde.org Reporter: warqu...@gmail.com Target Milestone: --- SUMMARY Using printing with black theme produce white paper with white text. -- You are receiving this mail because: You are watching all bug changes.
[okteta] [Bug 420930] New: Okteta crashes on exit
https://bugs.kde.org/show_bug.cgi?id=420930 Bug ID: 420930 Summary: Okteta crashes on exit Product: okteta Version: 0.26.3 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: kosse...@kde.org Reporter: k...@trummer.xyz Target Milestone: --- Created attachment 128102 --> https://bugs.kde.org/attachment.cgi?id=128102=edit backtrace SUMMARY Okteta crashes on exit when a file is loaded. STEPS TO REPRODUCE 1. launch Okteta 2. open any file in it 3. close Okteta OBSERVED RESULT clean exit EXPECTED RESULT crash ADDITIONAL INFORMATION Operating System: openSUSE Tumbleweed 20200429 KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.69.0 Qt Version: 5.14.1 Kernel Version: 5.6.6-1-default OS Type: 64-bit Processors: 8 × AMD Ryzen 5 PRO 3500U w/ Radeon Vega Mobile Gfx Memory: 13,5 GiB -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 420917] Looped bash script (unfinished command) holds plasma_session startup
https://bugs.kde.org/show_bug.cgi?id=420917 Evgen changed: What|Removed |Added Summary|Looped bash script blocks |Looped bash script |plasma_session startup |(unfinished command) holds ||plasma_session startup -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 419625] System settings crashed when playing with Display configuration in QQuickWindow::MouseGrabbItem
https://bugs.kde.org/show_bug.cgi?id=419625 David Edmundson changed: What|Removed |Added Status|CONFIRMED |RESOLVED Latest Commit||https://commits.kde.org/ksc ||reen/cfd95e6bff4bfeadf95a7a ||475693b30ddfe30431 Resolution|--- |FIXED --- Comment #9 from David Edmundson --- Git commit cfd95e6bff4bfeadf95a7a475693b30ddfe30431 by David Edmundson. Committed on 02/05/2020 at 21:52. Pushed by davidedmundson into branch 'master'. fix(kcm): avoid recursive OpacityMask which leads to teardown crash Summary: In the current code OpacityMask's source is the parent which contains itself, which doesn't make sense. Docs explicitly say this. [1] This leads to a crash in teardown. A quick reshuffle fixes it. [1] https://doc.qt.io/qt-5/qml-qtgraphicaleffects-opacitymask.html#source-prop Test Plan: Found reproducible steps (see bug) No longer crashes Reviewers: romangg Reviewed By: romangg Subscribers: romangg, plasma-devel Tags: #plasma Differential Revision: https://phabricator.kde.org/D29340 M +15 -11 kcm/package/contents/ui/Output.qml https://commits.kde.org/kscreen/cfd95e6bff4bfeadf95a7a475693b30ddfe30431 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 419305] Have transparent icons in systray
https://bugs.kde.org/show_bug.cgi?id=419305 --- Comment #25 from Konrad Materka --- Thank you detailed report! I have few more questions: * To open System Tray settings, right click on the arrow - will show a menu with "Configure System Tray..." entry. This way you can access settings. * From that bug occurrence you sent screenshots, do you have errors like this in logs? file:///usr/share/plasma/plasmoids/org.kde.plasma.private.systemtray/contents/ui/items/StatusNotifierItem.qml: My guess is that no, because tooltips are working, but it is worth to confirm. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385602] Add option to show volume level text in OSD
https://bugs.kde.org/show_bug.cgi?id=385602 Andres Betts changed: What|Removed |Added CC||anditosan1...@gmail.com --- Comment #5 from Andres Betts --- Looks-wise good. Maybe if people feel like having a progress bar and text, that would be good too. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 420928] New: SystemSettings don't expose page size
https://bugs.kde.org/show_bug.cgi?id=420928 Bug ID: 420928 Summary: SystemSettings don't expose page size Product: systemsettings Version: 5.16.5 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: kcm_formats Assignee: se...@kde.org Reporter: syfe...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY The format settings in SystemSettings should expose a setting to change the preferred page format. Currently people who have set all their formats to use metric find themselves with typesetting programs such as LibreOffice producing "letter" formatted documents instead of A4 that's standard around the world. Changing the format requires writing a value to /etc/papersize, but the discoverability of this option is quite low. The discoverability of this setting in SystemSettings will be much higher and thus it should be exposed here. The minimum two options should be "letter" and "A4". Setting the region to anything except USA and Canada should set this value to A4 as well. STEPS TO REPRODUCE 1. Open SystemSettings 2. Go to Regional Settings 3. Go to formats OBSERVED RESULT There is no option to change the paper size. EXPECTED RESULT There should be an option to change the paper size SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Kubuntu 19.10 (available in About System) KDE Plasma Version: 5.15.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.4 ADDITIONAL INFORMATION According to https://linux.die.net/man/5/papersize, valid values include a3, a4, a5, b5, letter, legal,executive, note and 11x17. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 420927] New: quick tile is very hard to trigger on multi monitor middle edge
https://bugs.kde.org/show_bug.cgi?id=420927 Bug ID: 420927 Summary: quick tile is very hard to trigger on multi monitor middle edge Product: kwin Version: 5.18.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: multihead Assignee: kwin-bugs-n...@kde.org Reporter: emil.vanh...@gmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. have a multi monitor setup 2. Drag a window to the edge between the two screens for quick tile OBSERVED RESULT You need to be very slow and very precise to be able to tile the window. EXPECTED RESULT It should be easy to quick tile a window. Maybe make the trigger come earlier on the edge in the middle? 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.
[plasma-browser-integration] [Bug 395461] multiple video support
https://bugs.kde.org/show_bug.cgi?id=395461 --- Comment #3 from Kai Uwe Broulik --- *** Bug 420926 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 420926] No control over multiple or different playback sources
https://bugs.kde.org/show_bug.cgi?id=420926 Kai Uwe Broulik changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Kai Uwe Broulik --- *** This bug has been marked as a duplicate of bug 395461 *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 420923] Nor auto-scroll either children album expansion is possible while drag and drop photos to the album tree
https://bugs.kde.org/show_bug.cgi?id=420923 --- Comment #2 from caulier.gil...@gmail.com --- I cannot reproduce this problem with 7.0.0 RC. Can you check with this installer : https://files.kde.org/digikam/ Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 420923] Nor auto-scroll either children album expansion is possible while drag and drop photos to the album tree
https://bugs.kde.org/show_bug.cgi?id=420923 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Maik Qualmann --- *** This bug has been marked as a duplicate of bug 417322 *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 417322] Unable to move album because tree view does not scroll
https://bugs.kde.org/show_bug.cgi?id=417322 Maik Qualmann changed: What|Removed |Added CC||jor...@gmail.com --- Comment #4 from Maik Qualmann --- *** Bug 420923 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 420926] New: No control over multiple or different playback sources
https://bugs.kde.org/show_bug.cgi?id=420926 Bug ID: 420926 Summary: No control over multiple or different playback sources Product: plasma-browser-integration Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: k...@privat.broulik.de Reporter: unfold1...@gmail.com Target Milestone: --- SUMMARY When having multiple playback streams like tabs or browser windows, it's not possible to switch between different sources, only the last playing source is picked up by the integration controls, this also goes to KdeConnect. STEPS TO REPRODUCE 1. Open a browser with several tabs or 2 browser instances with 2 youtube videos 2. Play both videos 3. Go to multimedia controls in integration OBSERVED RESULT Only the last media source playing is controlable EXPECTED RESULT It should be possible to switch media sources in the controls SOFTWARE/OS VERSIONS Linux/KDE Plasma: Gentoo Linux (available in About System) KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.60.0 Qt Version: 5.12.5 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 420925] New: Add kinetic scrolling on Trackpad use too
https://bugs.kde.org/show_bug.cgi?id=420925 Bug ID: 420925 Summary: Add kinetic scrolling on Trackpad use too Product: okular Version: 20.04.0 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: m...@elbmurf.de Target Milestone: --- Okular 20.04 has introduced fantastic kinetic scrolling with acceleration momentum on mouse drag, touch drag and page up/down keys. But trackpad scrolling is missing the kinetic momentum. If I switch from dragging the page to using the normal scroll gesture on my trackpad, the missing momentum feels like there is something wrong. Also see 413989 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 420924] New: After I apply "Always show all entries" setting in systray settings, the arrow to show hidden systray icons is still present until it is clicked
https://bugs.kde.org/show_bug.cgi?id=420924 Bug ID: 420924 Summary: After I apply "Always show all entries" setting in systray settings, the arrow to show hidden systray icons is still present until it is clicked Product: plasmashell Version: master Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: System Tray Assignee: plasma-b...@kde.org Reporter: bugsefor...@gmx.com Target Milestone: 1.0 Created attachment 128101 --> https://bugs.kde.org/attachment.cgi?id=128101=edit screen recording STEPS TO REPRODUCE 1. open system tray settings, check "Always show all entries" and apply the change OBSERVED RESULT Notice that the arrow to show hidden systray icons unexpectedly is still present. Click on it and it disappears as expected after the step above. Watch the attached screen recording please. EXPECTED RESULT the arrow to show hidden systray icons should immediately disappear from the systray after we apply "Always show all entries" setting. SOFTWARE/OS VERSIONS Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.18.80 KDE Frameworks Version: 5.70.0 Qt Version: 5.14.2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 371502] Task switcher (task manager) only allows to switch between two windows of application
https://bugs.kde.org/show_bug.cgi?id=371502 --- Comment #11 from Alan Aversa --- Here's an animation where the issues and functionality: https://i.stack.imgur.com/xTsGo.gif -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 420923] New: Nor auto-scroll either children album expansion is possible while drag and drop photos to the album tree
https://bugs.kde.org/show_bug.cgi?id=420923 Bug ID: 420923 Summary: Nor auto-scroll either children album expansion is possible while drag and drop photos to the album tree Product: digikam Version: 6.3.0 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: wishlist Priority: NOR Component: Usability-Drag Assignee: digikam-bugs-n...@kde.org Reporter: jor...@gmail.com Target Milestone: --- SUMMARY Album folder tree doesn't auto-scroll when dragging photos from icon-view STEPS TO REPRODUCE 1. Select at least one photo from icon view (either thumbnails, table or preview) 2. click and drag to album tree tab on left 3. trying to drop the photos on an album that is not visible prior to dragging,is not possible OBSERVED RESULT Drag and drop is limited to the current view only EXPECTED RESULT Album auto-scroll Expand children albums branch 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.
[ktimetracker] [Bug 416693] Moving a subtask to another higher-order task scrambles time data of all tasks
https://bugs.kde.org/show_bug.cgi?id=416693 --- Comment #4 from Andreas Kilgus --- (In reply to Andreas Kilgus from comment #3) > (In reply to Alexander Potashev from comment #2) > > "grep DTSTART ktimetracker.ics | sort" tells me, that the oldest regular > entries in my current ktimetracker.ics date back to May 2013. Though there > are some irregular entries, too: > > DTSTART:19800406T01 > DTSTART:19800928T03 > DTSTART:19810329T02 > DTSTART:19971026T03 Meanwhile I recognized that these do not belong to VTODO or VEVENT sections, so there's nothing wrong here probably. > I can try to anonymize my file and send it to you for testing. Unfortunately my email seems not to have reached you. Anyway, another observation: While ktimetracker is running, a lot of entries 'm_sessionStartTime= ""' appear in my system log. The time interval between the groups of these messages seems to correlate with the autosave interval. I cloned your git, extended the contents of the debug message and tried to compile the code to see if I can identify the tasks in ktimetracker that cause these messages. But I already failed at compilation stage. Even after a bunch of additions to the CMakeLists.txt I did not manage to get a working Makefile so I gave up eventually. If you can provide some explanation how the code is supposed to be compiled, I'll give it another try. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 405094] Symbols in name break search
https://bugs.kde.org/show_bug.cgi?id=405094 Ceaus changed: What|Removed |Added CC||k...@pohw.nl --- Comment #2 from Ceaus --- I'm facing the same problem. Files are not found whilst they are there. The logic of Igor Poboiko (comment #1) just complicated things: 1. If I search for files with very common letters in their name, such as 'a' or 'e', baloo just reports a handful, while I have hundreds in my home dir. At this point I have zero cue how to interpret the search results. I see some files, but I also see many not. How do I now interpret this list? I know the list is incorrect(because I know the file exists). But to what extend? Are there other files not in the search results? And if so, why? 2. If I search for single non-alphabet characters, such as filenames with a '-', '_' or ' ' baloo returns zero results. Which goes against the results of option (1). So now the question becomes even more difficult to answer: what is this list I am looking at? Apparently A-Z characters are first class citizens, whereas the other characters are estranged cousins. To me this sounds rather arbitrary. baloo should simply return them all. If there is a genuine concern for the list being too long, then why not raise a warning: "Hey, are you sure you want a list containing 137K filenames?" BTW: I'm on openSUSE Leap 15.1 Baloo = 5.55.0 -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 420922] New: mis-identifies strace -yy output as spam
https://bugs.kde.org/show_bug.cgi?id=420922 Bug ID: 420922 Summary: mis-identifies strace -yy output as spam Product: bugs.kde.org Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: sysad...@kde.org Reporter: k...@kdebugs.elan.rulez.org CC: she...@kde.org Target Milestone: --- I originally tried to submit https://bugs.kde.org/show_bug.cgi?id=420921 with the text at https://pastebin.com/p4TKSX3R. The original text couldn't be submitted because bugzilla thought it was spam. Removing the UNIX socket IDs output by strace -yy, which, if you squint at them right and tilt your head, might look like HTML, I was able to submit the bug report. Perhaps the spam detector can be tuned to allow strace -yy output to be posted? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 371502] Task switcher (task manager) only allows to switch between two windows of application
https://bugs.kde.org/show_bug.cgi?id=371502 Alan Aversa changed: What|Removed |Added Version|5.8.2 |5.18.4 Platform|Ubuntu Packages |Slackware Packages CC||ave...@email.arizona.edu --- Comment #10 from Alan Aversa --- I've had a very similar issue intermittently for awhile, even now with KDE 5.18.4. Hitting Alt+Tab only goes to next application. Holding the Alt down and hitting tab again does nothing; it doesn't cycle through. I have to use my arrow keys to select other apps while holding the Alt key down. Alt+Shift+Tab will go the previous application (sometimes). The same for Alt+` and Alt+~. Sometimes after rebooting this issue goes away. It's intermittent for me. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 420920] New: Tooltip and popup of battery applet show different battery levels
https://bugs.kde.org/show_bug.cgi?id=420920 Bug ID: 420920 Summary: Tooltip and popup of battery applet show different battery levels Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Battery Monitor Assignee: k...@privat.broulik.de Reporter: bugsefor...@gmx.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 128100 --> https://bugs.kde.org/attachment.cgi?id=128100=edit screen recording STEPS TO REPRODUCE 1. disconnect the ac adapter from your laptop 2. use your device during a few minutes/hours or just wait for the battery level to decrease 3. reconnect the ac adapter to your device and wait for your battery to be charged 4. observe the battery level hovering over the battery applet in systray. Also click on such applet and observe the percentage of "Charging". OBSERVED RESULT Tooltip and popup of battery applet show different battery levels. Watch the attached screen recording please. EXPECTED RESULT Tooltip and popup of battery applet should show the same battery level SOFTWARE/OS VERSIONS Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.18.80 KDE Frameworks Version: 5.70.0 Qt Version: 5.14.2 -- You are receiving this mail because: You are watching all bug changes.
[kwallet-pam] [Bug 420921] New: execute_kwallet() accidentally closes syslog socket, which results in failure to listen() on its own socket, breaking kwalletd
https://bugs.kde.org/show_bug.cgi?id=420921
Bug ID: 420921
Summary: execute_kwallet() accidentally closes syslog socket,
which results in failure to listen() on its own
socket, breaking kwalletd
Product: kwallet-pam
Version: unspecified
Platform: Debian unstable
OS: Linux
Status: REPORTED
Severity: major
Priority: NOR
Component: general
Assignee: plasma-b...@kde.org
Reporter: k...@kdebugs.elan.rulez.org
Target Milestone: ---
SUMMARY
execute_kwallet() closes many of its inherited file descriptors, which includes
the one used for syslog() previously (I assume by pam_syslog()). However,
somewhere there is still global state that remembers that FD number.
The function goes on to create envSocket of type SOCK_STREAM, then calls
syslog() to log a debug message, and eventually tries to listen on envSocket.
The problem is that envSocket ends up having the same FD as the one saved for
syslog in global state; so in the call to syslog(), libc(?) closes the FD and
reopens it for logging as SOCK_DGRAM. listen() won't work on a datagram socket,
so that the listen() call fails and kwalletd does not run.
Severity set to major because this makes pam_kwallet unusable. There are a
number of reports scattered in various forums about this, but I didn't find an
actual bug report.
strace:
socket(AF_UNIX, SOCK_STREAM, 0) = 3 // this is the 'envSocket =
socket(AF_UNIX, SOCK_STREAM, 0)' call
unlink("/run/user//kwallet5.socket") = -1 ENOENT (No such file or
directory)
getpid()=
sendto(3, "<87>[some date] lightdm[]: pam_kwallet5: final socket path:
/run/user//kwallet5.socket", 98, MSG_NOSIGNAL, NULL, 0) = -1 ENOTCONN
(Transport endpoint is not connected) // this is the syslog() call
close(3) = 0 // this is syslog() being smart about apparently
having lost its connection to /dev/log
socket(AF_UNIX, SOCK_DGRAM|SOCK_CLOEXEC, 0) = 3
connect(3, {sa_family=AF_UNIX, sun_path="/dev/log"}, 110) = 0
sendto(3, "<87>[some date] lightdm[]: pam_kwallet5: final socket path:
/run/user/1011/kwallet5.socket", 98, MSG_NOSIGNAL, NULL, 0) = 98// this
is where syslog() actually logs the message, but FD3 is already SOCK_DGRAM
bind(3, {sa_family=AF_UNIX, sun_path="/run/user//kwallet5.socket"}, 32) = 0
// we're back from syslog() and in execute_kwallet() but at this point, FD3
is already a SOCK_DGRAM
listen(3, 5) = -1 EOPNOTSUPP (Operation not supported)
// so listen() fails
STEPS TO REPRODUCE
Try to start kwalletd from pam.
OBSERVED RESULT
kwalletd doesn't start and instead logs "pam_kwallet5-kwalletd: Couldn't listen
in socket"
EXPECTED RESULT
kwalletd starts and listens on its Unix domain socket.
SOFTWARE/OS VERSIONS
Windows:
macOS:
Linux/KDE Plasma: all
(available in About System)
KDE Plasma Version: reproduced with 5.17.5, but the code on github seems to be
the same
KDE Frameworks Version:
Qt Version: irrelevant
ADDITIONAL INFORMATION
Calling closelog() explicitly might be a fix.
Also, how do you know there are no inherited FDs above 63 you need to close?
Maybe you know, but in that case a comment that points this out would be
helpful. Currently the loop boundary at the beginning of the function looks
like either magic or a guess.
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 385602] Add option to show volume level text in OSD
https://bugs.kde.org/show_bug.cgi?id=385602 José changed: What|Removed |Added CC||panchopap...@gmail.com --- Comment #4 from José --- It's also useful for (quickly) knowing if 150% volume is enabled -- You are receiving this mail because: You are watching all bug changes.
[kshisen] [Bug 420915] Games displayed rotate around 5 or 6 layouts
https://bugs.kde.org/show_bug.cgi?id=420915 --- Comment #1 from Frederik Schwarzer --- Hi, Thank you for your report. I just tried it on my machine with the same version of KShisen and the first 20 games were different. Can you please tell us your settings found at: Settings -> Configure Shisen-Sho... -> General Thanks -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 420919] New: Transormations makes my object disappear, then reverts the transformation
https://bugs.kde.org/show_bug.cgi?id=420919 Bug ID: 420919 Summary: Transormations makes my object disappear, then reverts the transformation Product: krita Version: 4.2.9 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: Tools/Transform Assignee: krita-bugs-n...@kde.org Reporter: s.freem...@sasktel.net Target Milestone: --- SUMMARY When I apply the warp transformation to an circle, the circle disappears when I hit apply. If I select another tool the warp is reverted and the circle reappears STEPS TO REPRODUCE 1. Draw a circle in a vector layer 2. Apply warp changes and then apply 3. select any other transformation process to make object appear again, but untransformed OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: 10 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.
[kdenlive] [Bug 420916] Scrollbars in timeline are missing
https://bugs.kde.org/show_bug.cgi?id=420916 --- Comment #1 from Ludwig --- It seems the scroll bars are there but are not distinctly visible in the darker themes. The scrollbars are in the same shade of color as the surroundings and make them difficult to see. Can the scroll bars be shown in the opposite color of the theme? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 419305] Have transparent icons in systray
https://bugs.kde.org/show_bug.cgi?id=419305 --- Comment #24 from Dalibor --- (In reply to Konrad Materka from comment #23) > This is really hard to reproduce... When it happens again, can you: > > * click with left/right button on the empty space where icon should be > rendered - does it have any effect? > * hover over empty/invisible icon - can you see a tooltip? Does it have icon > or title? > * open System Tray settings (if you don't know how: right click on the small > arrow, you should find a menu option for it) - are icons correctly rendered > there? > * Run "plasmoidviewer --applet org.kde.plasma.systemtray" - do you have > icons correctly rendered (it should work correctly) > * open "System Settings" -> "Startup and Shutdown" -> "Background Services" > and in section "Startup Service", then stop/pause and run again the "Status > Notifier Manager" - what happened? On stop, it should remove "invisible" > icons and on start it should recreate icons correctly. > > I have some ideas, but I need your inputs to verify. * Right/Left click works as aspected * Tooltip is shown and rendered as expected: https://imgur.com/uETqh5s * System Tray settings is also affected. Icons are not rendered, tooltips are working fine: https://imgur.com/t5rpCKR * "plasmoidviewer --applet org.kde.plasma.systemtray" view render icons correctly : https://imgur.com/rSXn1yM * Restarting "Status Notifier Manager" does not help. Icons are still transparent. Tried multiple time to restart, same result. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 420918] New: Switch workspaces with mousewheel broken
https://bugs.kde.org/show_bug.cgi?id=420918 Bug ID: 420918 Summary: Switch workspaces with mousewheel broken Product: plasmashell Version: 5.18.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Folder Assignee: h...@kde.org Reporter: crazy-ivano...@gmx.net CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY With several virtual workspaces configured and the mouse wheel vertical scroll configured to allow switching between workspaces, it does not work if "folder view" is selected. Switching does work in "Desktop" mode. Switching via middle click does work as well. The same issue is described on this forum post: https://forum.endeavouros.com/t/switching-workspaces-with-mouse-wheel-stopped-working/4112 Speculation by JanKusanagi in the #kde IRC chan is that this is due to the folderview widget kidnapping the mouse wheel. The behavior of switching desktops via mousewheel changed some versions ago earlier this year (running archlinux ~amd64). A downgrade to an older package plasma-desktop back from the days when it was (most likely) still working did not help though. STEPS TO REPRODUCE 1. Configure >1 workspace, apply changes 2. Configure workspaces, change layout to "folder view" and ensure that vertical scrolling as well as middle click is set to "change workspace", apply changes 3. move the mouse to the desktop area and use the wheel to scroll vertically, afterwards use middle click OBSERVED RESULT Nothing happens when scrolling vertically, middle click opens the workspace selector as expected EXPECTED RESULT Switching workspaces or at least an information that this is not possible via wheel in folder view, middle click opens the workspace selector as expected SOFTWARE/OS VERSIONS Windows: N/A macOS: N/A Linux/KDE Plasma: 5.6.9-arch1-1, 64-bit (available in About System) KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.69.0 Qt Version: 5.14.2 ADDITIONAL INFORMATION Same issue as described in this forum post: https://forum.endeavouros.com/t/switching-workspaces-with-mouse-wheel-stopped-working/4112 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 420917] Looped bash script blocks plasma_session startup
https://bugs.kde.org/show_bug.cgi?id=420917 Evgen changed: What|Removed |Added Summary|Looped bash scripts block |Looped bash script blocks |plasma_session startup |plasma_session startup -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 420917] New: Looped bash scripts block plasma_session startup
https://bugs.kde.org/show_bug.cgi?id=420917 Bug ID: 420917 Summary: Looped bash scripts block plasma_session startup Product: systemsettings Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_autostart Assignee: mon...@kde.org Reporter: alts...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- Looped bash scripts blocks plasma_session startup SUMMARY I have few looped bash scripts for maintenance tasks (resume paused printers, mute sound after headphones disconnect). So I placed one of them to ~/.config/plasma-workspace/env/ During next login session didn't start leaving me with a mouse cursor on a black background. STEPS TO REPRODUCE 1. On ~/.config/plasma-workspace/env/ create file test.sh with content while true; do : done 2. Log out from session 3. Try to login OBSERVED RESULT Black background with a mouse cursor. I switched to different tty and htop showed that process /bin/sh /usr/lib/x86_64-linux-gnu/libexec/plasma-sourceenv.sh /home/$USER/.config/plasma-workspace/env/test.sh loads 100% percent of 1 CPU After I killed it plasma_session and other services started to load. Solution for my problem was to push that script into the background (adding "&" after "done") done & EXPECTED RESULT Looped script doesn't block plasma_session startup SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 20.04 KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 420541] Critical notifications (and *only* critical notifications) should be more attention-getting
https://bugs.kde.org/show_bug.cgi?id=420541 --- Comment #10 from RaitaroH --- And... it appeared! Awesome. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 420916] Scrollbars in timeline are missing
https://bugs.kde.org/show_bug.cgi?id=420916 Ludwig changed: What|Removed |Added CC||ikbenlud...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 420916] New: Scrollbars in timeline are missing
https://bugs.kde.org/show_bug.cgi?id=420916 Bug ID: 420916 Summary: Scrollbars in timeline are missing Product: kdenlive Version: 20.04.0 Platform: Other OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: ikbenlud...@gmail.com Target Milestone: --- SUMMARY After in-place upgrade from 19.12.3 to 20.04 and opening a project the scrollbars on bottom and right of the timelime are missing. STEPS TO REPRODUCE 1. upgrade to 20.04 2. start up 3. scrolbars missing - slider and CTL -- /++ at the bottom works normal OBSERVED RESULT unable to scroll to timeline or track outside the window without re-sizing or closing tracks regardless color theme or Breeze Icon forced or not. EXPECTED RESULT scroll bars to scroll through the timeline and tracks SOFTWARE/OS VERSIONS Windows: WIN 10 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION check documentation I could not find any setting to get the scroll bars back or reset did not help. I am new to KDENLIVE, therefore it could be that I missed something. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 415762] Exiting the session in a Yakuake tab sometimes crash Yakuake
https://bugs.kde.org/show_bug.cgi?id=415762 Mustafa Muhammad changed: What|Removed |Added CC||mustafa10...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 419305] Have transparent icons in systray
https://bugs.kde.org/show_bug.cgi?id=419305 Konrad Materka changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 419305] Have transparent icons in systray
https://bugs.kde.org/show_bug.cgi?id=419305 --- Comment #23 from Konrad Materka --- This is really hard to reproduce... When it happens again, can you: * click with left/right button on the empty space where icon should be rendered - does it have any effect? * hover over empty/invisible icon - can you see a tooltip? Does it have icon or title? * open System Tray settings (if you don't know how: right click on the small arrow, you should find a menu option for it) - are icons correctly rendered there? * Run "plasmoidviewer --applet org.kde.plasma.systemtray" - do you have icons correctly rendered (it should work correctly) * open "System Settings" -> "Startup and Shutdown" -> "Background Services" and in section "Startup Service", then stop/pause and run again the "Status Notifier Manager" - what happened? On stop, it should remove "invisible" icons and on start it should recreate icons correctly. I have some ideas, but I need your inputs to verify. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 415762] Exiting the session in a Yakuake tab sometimes crash Yakuake
https://bugs.kde.org/show_bug.cgi?id=415762 --- Comment #11 from JanKusanagi --- (In reply to Ricardo J. Barberis from comment #10) > Happens to me too, seeminlgy randomly. > > I didn’t experience crashes yesterday nor today but I'm being careful not to > leave any text selected with the mouse (X selection) before closing the > session, which was my gut feeling. See https://bugs.kde.org/show_bug.cgi?id=415762#c4 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 417628] Exclude filter in find/replace files dialog doesn't seem to work
https://bugs.kde.org/show_bug.cgi?id=417628 Igor Kushnir changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED Version Fixed In||5.5.1 Latest Commit||https://invent.kde.org/kde/ ||kdevelop/commit/f56cdda54b7 ||f88b119f2c7cfb2f534b4fe7447 ||8f --- Comment #2 from Igor Kushnir --- Git commit f56cdda54b7f88b119f2c7cfb2f534b4fe74478f by Igor Kushnir. Committed on 02/05/2020 at 16:28. Pushed by igorkushnir into branch '5.5'. Work around QDir::match() behavior change in Qt 5.12.0 QDir::match() migrated to QRegularExpression in Qt 5.12.0. In the new implementation asterisk in a wildcard no longer matches path separators. This caused two bugs in KDevelop: 1. kdev_format_source rejects input files if the 'format_sources' file is not located in the same directory as the target file. 2. Exclude filter in Find/Replace in Files has no effect (unless the user specifies almost complete paths in the format supported by Bash Filename Expansion with the globstar shell option disabled). Note that Files (aka `include`) filter in Find/Replace in Files is unaffected by the behavior change because in its code a filename rather than a path is passed as the second argument to QDir::match(). WildcardHelpers can migrate to QRegularExpression::wildcardToRegularExpression() once we require Qt 5.12.1 or later. This function was added in Qt 5.12.0 and started anchoring wildcard pattern in Qt 5.12.1. Ideally support for globstar (**) in glob patterns should be added to QRegularExpression::wildcardToRegularExpression() and to QDir::match(). In that case WildcardHelpers could be eliminated and QDir::match() could be used again. If globstar support is not added to QRegularExpression::wildcardToRegularExpression(), WildcardHelpers can port away from QRegExp, for example, by replacing `starEscape` (see the definition of wildcardToRegularExpression()) with ".*" in the value returned by wildcardToRegularExpression() and passing DotMatchesEverythingOption to QRegularExpression constructor. When we port away from QRegExp, we can change the syntax of format_sources and possibly Exclude filter to match Bash globstar syntax or perhaps some other new Qt wildcard syntax. Alternatively, we can process user-provided wildcard patterns before and/or after passing them to wildcardToRegularExpression() so as to preserve our syntax. Related: bug 409222 FIXED-IN: 5.5.1 M +1-0kdevplatform/util/CMakeLists.txt M +3-1kdevplatform/util/kdevformatfile.cpp A +59 -0kdevplatform/util/wildcardhelpers.h [License: LGPL (v2+)] M +2-1plugins/grepview/grepdialog.cpp M +4-2plugins/grepview/grepfindthread.cpp https://invent.kde.org/kde/kdevelop/commit/f56cdda54b7f88b119f2c7cfb2f534b4fe74478f -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 409222] kdev_format_source returns "error: no commands applicable to" for any pattern
https://bugs.kde.org/show_bug.cgi?id=409222 Igor Kushnir changed: What|Removed |Added Version Fixed In||5.5.1 Latest Commit||https://invent.kde.org/kde/ ||kdevelop/commit/f56cdda54b7 ||f88b119f2c7cfb2f534b4fe7447 ||8f Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #4 from Igor Kushnir --- Git commit f56cdda54b7f88b119f2c7cfb2f534b4fe74478f by Igor Kushnir. Committed on 02/05/2020 at 16:28. Pushed by igorkushnir into branch '5.5'. Work around QDir::match() behavior change in Qt 5.12.0 QDir::match() migrated to QRegularExpression in Qt 5.12.0. In the new implementation asterisk in a wildcard no longer matches path separators. This caused two bugs in KDevelop: 1. kdev_format_source rejects input files if the 'format_sources' file is not located in the same directory as the target file. 2. Exclude filter in Find/Replace in Files has no effect (unless the user specifies almost complete paths in the format supported by Bash Filename Expansion with the globstar shell option disabled). Note that Files (aka `include`) filter in Find/Replace in Files is unaffected by the behavior change because in its code a filename rather than a path is passed as the second argument to QDir::match(). WildcardHelpers can migrate to QRegularExpression::wildcardToRegularExpression() once we require Qt 5.12.1 or later. This function was added in Qt 5.12.0 and started anchoring wildcard pattern in Qt 5.12.1. Ideally support for globstar (**) in glob patterns should be added to QRegularExpression::wildcardToRegularExpression() and to QDir::match(). In that case WildcardHelpers could be eliminated and QDir::match() could be used again. If globstar support is not added to QRegularExpression::wildcardToRegularExpression(), WildcardHelpers can port away from QRegExp, for example, by replacing `starEscape` (see the definition of wildcardToRegularExpression()) with ".*" in the value returned by wildcardToRegularExpression() and passing DotMatchesEverythingOption to QRegularExpression constructor. When we port away from QRegExp, we can change the syntax of format_sources and possibly Exclude filter to match Bash globstar syntax or perhaps some other new Qt wildcard syntax. Alternatively, we can process user-provided wildcard patterns before and/or after passing them to wildcardToRegularExpression() so as to preserve our syntax. Related: bug 417628 FIXED-IN: 5.5.1 M +1-0kdevplatform/util/CMakeLists.txt M +3-1kdevplatform/util/kdevformatfile.cpp A +59 -0kdevplatform/util/wildcardhelpers.h [License: LGPL (v2+)] M +2-1plugins/grepview/grepdialog.cpp M +4-2plugins/grepview/grepfindthread.cpp https://invent.kde.org/kde/kdevelop/commit/f56cdda54b7f88b119f2c7cfb2f534b4fe74478f -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 415762] Exiting the session in a Yakuake tab sometimes crash Yakuake
https://bugs.kde.org/show_bug.cgi?id=415762 --- Comment #10 from Ricardo J. Barberis --- Happens to me too, seeminlgy randomly. I didn’t experience crashes yesterday nor today but I'm being careful not to leave any text selected with the mouse (X selection) before closing the session, which was my gut feeling. My second difference between crashes/no crashes would be a secondary display connected, which I didn't have yesterday or today. My system: Operating System: Slackware 14.2+ (-current) KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.69.0 Qt Version: 5.13.2 Kernel Version: 5.4.35 OS Type: 64-bit Processors: 4 × Intel® Core™ i5-4200U CPU @ 1.60GHz Memory: 7,7 GiB -- You are receiving this mail because: You are watching all bug changes.
[lokalize] [Bug 416427] TM doesn't work due to: requested database does not belong to the calling thread
https://bugs.kde.org/show_bug.cgi?id=416427 Valter Mura changed: What|Removed |Added CC||valterm...@gmail.com --- Comment #1 from Valter Mura --- I have a similar problem: I have 3 TMs created some years ago but now they neither auto-update when I translate, nor update when I try to add translated files manually. Operating System: KDE neon Testing Edition KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.70.0 Qt Version: 5.14.2 Kernel Version: 5.3.0-51-generic OS Type: 64-bit -- You are receiving this mail because: You are watching all bug changes.
