[okular] [Bug 408270] Okular always prints in A4 on physical printers, even when Letter is the default
https://bugs.kde.org/show_bug.cgi?id=408270 Michael Weghorn changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #19 from Michael Weghorn --- (In reply to Matthew Trescott from comment #18) > Same problem happens with Kate. :/ ... in which case this isn't Okuklar's fault, but seems somewhat related to the Qt print dialog in general. What Qt version do you have? Can we close this bug as RESOLVED UPSTREAM (since Qt has it's own issue tracker at [1])? Feel free to continue commenting, though, even if the bug is closed. However, unless you have an old Qt version (which seems to be unlikely since you mention you're using Arch), I'm running out of ideas... [1] http://bugreports.qt.io/ -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 409640] New: Hide virtual keyboard SNI on mobile/touchscreen only device.
https://bugs.kde.org/show_bug.cgi?id=409640 Bug ID: 409640 Summary: Hide virtual keyboard SNI on mobile/touchscreen only device. Product: kwin Version: git master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: virtual-keyboard Assignee: kwin-bugs-n...@kde.org Reporter: bhus...@gmail.com Target Milestone: --- SUMMARY It kinda becomes problem when on touchscreen only device if by accident you disable virtual keyboard. It makes no sense to enable/disable virtual-keyboard on phone/tablet devices. you always want virtual keyboard Linux/KDE Plasma: git master -- You are receiving this mail because: You are watching all bug changes.
[Ruqola] [Bug 409247] Group list - Do not able scroll down on members list
https://bugs.kde.org/show_bug.cgi?id=409247 Laurent Montel changed: What|Removed |Added Latest Commit||https://commits.kde.org/ruq ||ola/d3e156b34aecd363c3111cc ||51ce42a35dc43fd26 Resolution|--- |FIXED Version Fixed In||1.0 Status|ASSIGNED|RESOLVED --- Comment #2 from Laurent Montel --- Git commit d3e156b34aecd363c3111cc51ce42a35dc43fd26 by Laurent Montel. Committed on 09/07/2019 at 05:53. Pushed by mlaurent into branch '1.0'. Fix Bug 409247 - Group list - Do not able scroll down on members list FIXED-IN: 1.0 M +0-1src/apps/qml/MainComponent.qml M +1-0src/apps/qml/SearchLabel.qml M +15 -15 src/ruqolacore/model/usersforroommodel.cpp https://commits.kde.org/ruqola/d3e156b34aecd363c3111cc51ce42a35dc43fd26 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 409349] Offer a window placement mode that remembers windows' prior positioning
https://bugs.kde.org/show_bug.cgi?id=409349 --- Comment #4 from Martin Flöser --- (In reply to Nate Graham from comment #3) > 1. Would it be possible for KWin to override the windows' own placement when > using this mode? Yes of course, otherwise it would be impossible to have tiling window managers. But: there are windows which have to position themselves and with the current protocols we cannot distinguish. If we would override, we would override all, which would break applications like Yakuake, KRunner, every Plasma window, etc. > > 2. If the window manager specs don't easily allow for this behavior, can the > specs be changed? Particularly for Wayland, which is still accumulating new > protocols on a semi-regular basis, I would hope that a spec that doesn't > allow for a desirable feature could be changed to facilitate it. For Wayland I can imagine that a protocol extension gets added. But if you go this route, go back to drawing mode. What we want to achieve is the same positioning of windows. What we don't want is to start with the implementation, what this feature request is. Whether it's a window placement mode or some other mechanism is an implementation detail. If you approach other window managers with the wrong story you will get opposition. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 409639] Kwin crash on suspend system
https://bugs.kde.org/show_bug.cgi?id=409639 Martin Flöser changed: What|Removed |Added Resolution|--- |BACKTRACE Status|REPORTED|NEEDSINFO --- Comment #1 from Martin Flöser --- Unfortunately the backtrace is lacking debug symbols. If you are able to reproduce please install debug packages and attach a new backtrace. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 408375] Loading .mlt file corrupts project profile
https://bugs.kde.org/show_bug.cgi?id=408375 Evert Vorster changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #4 from Evert Vorster --- This issue is now resolved. Thank you very much, JB! -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 363676] Each time a plasma5 session is started one or more drkonqi segfault
https://bugs.kde.org/show_bug.cgi?id=363676 Bruno Friedmann changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |UNMAINTAINED --- Comment #3 from Bruno Friedmann --- This is no more seen with drkonqi 5.16 Most of crashes seen at startup time are now akonadi or baloo/miloo related. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 396158] Vanishing point assistant rays should be hidden when assistants are hidden
https://bugs.kde.org/show_bug.cgi?id=396158 vanyossi changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/kde/ ||krita/commit/639e0d2dcd71ad ||4f524e88fa32df7939c3373e64 Status|ASSIGNED|RESOLVED --- Comment #5 from vanyossi --- Git commit 639e0d2dcd71ad4f524e88fa32df7939c3373e64 by Ivan Yossi. Committed on 09/07/2019 at 05:00. Pushed by ivany into branch 'master'. Hide Vanishing points preview lines when hiding assistants M +1-1plugins/assistants/Assistants/VanishingPointAssistant.cc https://invent.kde.org/kde/krita/commit/639e0d2dcd71ad4f524e88fa32df7939c3373e64 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 408553] Segmentation faults and invalid reads/writes in powerdevil when logging out of Plasma 5.15.5 on Wayland in Fedora 30
https://bugs.kde.org/show_bug.cgi?id=408553 Matt Fagnani changed: What|Removed |Added URL|https://bugzilla.redhat.com |https://bugzilla.redhat.com |/show_bug.cgi?id=1713467|/show_bug.cgi?id=1713467 ||https://bugzilla.redhat.com ||/show_bug.cgi?id=1727470 --- Comment #4 from Matt Fagnani --- The versions used in the crash I reported in comment 3 were glib2-0:2.60.4-1.fc30.x86_64 glibc-0:2.29-15.fc30.x86_64 kf5-kwayland-0:5.59.0-2.fc30.x86_64 kwayland-integration-0:5.15.5-1.fc30.x86_64 kwin-wayland-0:5.15.5-2.fc30.x86_64 libwayland-client-0:1.17.0-1.fc30.x86_64 powerdevil-0:5.15.5-1.fc30.x86_64 qt5-qtbase-0:5.12.4-1.fc30.x86_64 qt5-qtwayland-5.12.4-2.fc30.x86_64 coredumpctl has 27 entries for aborts of drkonqi due to powerdevil segmentation faults and of the restarted powerdevil each. The segmentation faults of powerdevil often occurred about the same time as blank screens occurred which I reported at https://bugzilla.redhat.com/show_bug.cgi?id=1727482 The black screen problem seems to have been the one reported at https://bugs.kde.org/show_bug.cgi?id=372789 A patch to fix this issue for kwayland-integration was written by David Edmundson for Plasma 5.16.3 https://cgit.kde.org/kwayland-integration.git/commit/?id=bfce3c6727cdc58a2b8ba33c933df05e21914876 https://bugs.kde.org/show_bug.cgi?id=372789#c46 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409060] Program glitches and crashes fast
https://bugs.kde.org/show_bug.cgi?id=409060 --- 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.
[kate] [Bug 375792] blue "created from another program" bar not removed from hidden views when reloading a document
https://bugs.kde.org/show_bug.cgi?id=375792 --- Comment #3 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.
[frameworks-ktexteditor] [Bug 385962] kate indention jumps to next level on specific letters when it shouldn advance to next level
https://bugs.kde.org/show_bug.cgi?id=385962 --- Comment #5 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 409019] Krita text box wont display pasted text correctly
https://bugs.kde.org/show_bug.cgi?id=409019 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #8 from Bug Janitor Service --- Thanks for your comment! Automatically switching the status of this bug to REPORTED so that the KDE team knows that the bug is ready to get confirmed. In the future you may also do this yourself when providing needed information. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 344679] Korganizer no alerts no reminders
https://bugs.kde.org/show_bug.cgi?id=344679 --- Comment #9 from Filipus Klutiero --- Rob, Shlomi, Luca, Jaak, does this persist with your current version, and if so, do you have the "Enable Reminders" korgac option enabled? This option is - very strangely - not visible in the configuration of KOrganizer itself. To enable it, you must right-click the daemon's system tray icon, then left-click "Enable Reminders". -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 344679] Korganizer no alerts no reminders
https://bugs.kde.org/show_bug.cgi?id=344679 Filipus Klutiero changed: What|Removed |Added CC||chea...@gmail.com --- Comment #8 from Filipus Klutiero --- (In reply to Andrzej from comment #4) > I get a following error when trying to start korgac in terminal: > > "\"CalendarsLastChecked\" - conversion of \"0,0,0,-1,-1,-1\" to QDateTime > failed" > > korgac seems to work(appears in system tray), but there are no notifications > or alarms for any events. > > korgac 5.5.3 > Kubuntu 17.10 brand new install Andrzej, if this persists, please open a different ticket titled something like "KOrganizer alarm daemon fails to start (conversion to QDateTime failed)" -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 408553] Segmentation faults and invalid reads/writes in powerdevil when logging out of Plasma 5.15.5 on Wayland in Fedora 30
https://bugs.kde.org/show_bug.cgi?id=408553
--- Comment #3 from Matt Fagnani ---
Created attachment 121409
--> https://bugs.kde.org/attachment.cgi?id=121409=edit
coredumpctl gdb output of segmentation fault in powerdevil when logging of
Plasma on Wayland
Thanks Christoph. I think that if the segmentation faults in powerdevil were
fixed then the aborts of drkonqi and the restarted powerdevil after the Wayland
compositor connection was broken wouldn't happen. I saw another segmentation
fault in powerdevil when I logged out of Plasma 5.15.5 on Wayland. sddm didn't
show up and the screen stayed blank which I've seen many times before when
logging out of Plasma on Wayland. I pressed sysrq+alt+e , sysrq+alt+i which
terminated then killed most of the userspace processes. sddm restarted after
that.
This segmentation fault occurred at about the same time that the screen went
blank. coredumpctl gdb showed that tc_victim->fd in _int_malloc at
malloc.c:3623 was an inaccessible address.
Core was generated by `/usr/libexec/org_kde_powerdevil'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x7f0d44dcadac in _int_malloc (av=av@entry=0x7f0d2c20,
bytes=bytes@entry=65)
at malloc.c:3622
3622 if (SINGLE_THREAD_P)
[Current thread is 1 (Thread 0x7f0d33b86700 (LWP 1559))]
(gdb) list
3617
3618 /* While bin not empty and tcache not full, copy
chunks. */
3619 while (tcache->counts[tc_idx] < mp_.tcache_count
3620 && (tc_victim = *fb) != NULL)
3621{
3622 if (SINGLE_THREAD_P)
3623*fb = tc_victim->fd;
3624 else
3625{
3626 REMOVE_FB (fb, pp, tc_victim);
(gdb) p tc_victim->fd
Cannot access memory at address 0xa1556b
(gdb) p tc_victim
$2 = (mchunkptr) 0xa1555b
A signal indicating a crash appeared after #13 in tcache_get at malloc.c:2952.
KCrash::defaultCrashHandler in #11 showed errors like "Cannot access memory at
address 0x7" which might indicate memory corruption. Qt string conversions
involving "org.kde.kglobalaccel" happened at #16-19. I've seen many aborts of
kglobalaccel5 when logging out of Plasma on Wayland and X as reported at
https://bugzilla.redhat.com/show_bug.cgi?id=1701485
I've attached the coredumpctl gdb output of the crash with the full backtrace
of all threads etc. I reported this crash in more detail at
https://bugzilla.redhat.com/show_bug.cgi?id=1727470 Should I create a new
report on bugs.kde.org since the trace is different?
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 409639] New: Kwin crash on suspend system
https://bugs.kde.org/show_bug.cgi?id=409639 Bug ID: 409639 Summary: Kwin crash on suspend system Product: kwin Version: 5.16.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: wiji...@intempmail.com Target Milestone: --- Application: kwin_x11 (5.16.2) Qt Version: 5.13.0 Frameworks Version: 5.59.0 Operating System: Linux 5.1.15-arch1-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: Waking up from suspension. Using Nvidia optimus GPU with nvidia driver. Compositor enabled. The crash can be reproduced sometimes. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fa3f524b880 (LWP 899))] Thread 7 (Thread 0x7fa3f2424700 (LWP 6201)): #0 0x7fa3fdb1b756 in ppoll () at /usr/lib/libc.so.6 #1 0x7fa3fc662913 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/libQt5Core.so.5 #2 0x7fa3fc663fa3 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #3 0x7fa3fc60d5ec in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7fa3fc4402f5 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #5 0x7fa3fc441520 in () at /usr/lib/libQt5Core.so.5 #6 0x7fa3fb3ba57f in start_thread () at /usr/lib/libpthread.so.0 #7 0x7fa3fdb260e3 in clone () at /usr/lib/libc.so.6 Thread 6 (Thread 0x7fa3e0996700 (LWP 1888)): #0 0x7fa3fb3c0415 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fa3fc4475a0 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7fa3fc447692 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7fa3faee57bd in () at /usr/lib/libQt5Quick.so.5 #4 0x7fa3faee5a6e in () at /usr/lib/libQt5Quick.so.5 #5 0x7fa3fc441520 in () at /usr/lib/libQt5Core.so.5 #6 0x7fa3fb3ba57f in start_thread () at /usr/lib/libpthread.so.0 #7 0x7fa3fdb260e3 in clone () at /usr/lib/libc.so.6 Thread 5 (Thread 0x7fa3e3fff700 (LWP 978)): #0 0x7fa3fb3c0415 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fa3fbec9edc in () at /usr/lib/libQt5Script.so.5 #2 0x7fa3fbec9ef9 in () at /usr/lib/libQt5Script.so.5 #3 0x7fa3fb3ba57f in start_thread () at /usr/lib/libpthread.so.0 #4 0x7fa3fdb260e3 in clone () at /usr/lib/libc.so.6 Thread 4 (Thread 0x7fa3f1973700 (LWP 975)): #0 0x7fa3fdb1b756 in ppoll () at /usr/lib/libc.so.6 #1 0x7fa3fc662913 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/libQt5Core.so.5 #2 0x7fa3fc663fa3 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #3 0x7fa3fc60d5ec in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7fa3fc4402f5 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #5 0x7fa3fab4a8f9 in () at /usr/lib/libQt5Qml.so.5 #6 0x7fa3fc441520 in () at /usr/lib/libQt5Core.so.5 #7 0x7fa3fb3ba57f in start_thread () at /usr/lib/libpthread.so.0 #8 0x7fa3fdb260e3 in clone () at /usr/lib/libc.so.6 Thread 3 (Thread 0x7fa3f3763700 (LWP 962)): #0 0x7fa3fdb1b756 in ppoll () at /usr/lib/libc.so.6 #1 0x7fa3fc662913 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/libQt5Core.so.5 #2 0x7fa3fc663fa3 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #3 0x7fa3fc60d5ec in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7fa3fc4402f5 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #5 0x7fa3fa57bb37 in () at /usr/lib/libQt5DBus.so.5 #6 0x7fa3fc441520 in () at /usr/lib/libQt5Core.so.5 #7 0x7fa3fb3ba57f in start_thread () at /usr/lib/libpthread.so.0 #8 0x7fa3fdb260e3 in clone () at /usr/lib/libc.so.6 Thread 2 (Thread 0x7fa3f45a6700 (LWP 954)): #0 0x7fa3fdb1b667 in poll () at /usr/lib/libc.so.6 #1 0x7fa3fc361630 in () at /usr/lib/libxcb.so.1 #2 0x7fa3fc3632db in xcb_wait_for_event () at /usr/lib/libxcb.so.1 #3 0x7fa3f48d7049 in () at /usr/lib/libQt5XcbQpa.so.5 #4 0x7fa3fc441520 in () at /usr/lib/libQt5Core.so.5 #5 0x7fa3fb3ba57f in start_thread () at /usr/lib/libpthread.so.0 #6 0x7fa3fdb260e3 in clone () at /usr/lib/libc.so.6 Thread 1 (Thread 0x7fa3f524b880 (LWP 899)): [KCrash Handler] #6 0x7fa3fc0ea259 in () at /usr/lib/libkwin4_effect_builtins.so.1 #7 0x7fa3fc0ea317 in () at /usr/lib/libkwin4_effect_builtins.so.1 #8 0x7fa3fc0ec222 in () at /usr/lib/libkwin4_effect_builtins.so.1 #9 0x7fa3fc0ecc50 in () at /usr/lib/libkwin4_effect_builtins.so.1 #10
[okular] [Bug 409638] New: Inline note with pen opens new notes while hovering
https://bugs.kde.org/show_bug.cgi?id=409638 Bug ID: 409638 Summary: Inline note with pen opens new notes while hovering Product: okular Version: 1.3.3 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: ffuhrma...@gmx.de Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Thinkpad Pen Pro used on Lenovo Thinkpad L390 Yoga. 2. Try to make an Inline-Note by using this Pen. 3. Hover for a few seconds with the pen over the screen (while having the review option "inline-note" selected). OBSERVED RESULT An extreme amount of new windows to make a new inline text note is opened (800+ in my case). While being with the pen in proximity to the screen, the responsiveness was really slow (probably because of the new notes popping up). This occurred only when using the Pen. While using the Trackpad or Finger on the Touchscreen the software reacted as expected. EXPECTED RESULT Just one new popup windows for the input of a text for the inline-note. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Ubuntu 18.04, gnome 3.28.2 (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.
[krita] [Bug 409637] New: Color Display is wrong?
https://bugs.kde.org/show_bug.cgi?id=409637 Bug ID: 409637 Summary: Color Display is wrong? Product: krita Version: 4.2.2 Platform: Other OS: Linux Status: REPORTED Severity: task Priority: NOR Component: Color Selectors Assignee: krita-bugs-n...@kde.org Reporter: lilyzhang...@yahoo.com Target Milestone: --- SUMMARY I use a dell computer with Window 7 and a wacom intuos tablet. When I try to color in work, for example if I use the color red, it shows blue on the screen instead. However, in the layer it shows red unlike the blue shown on screen. I've tried to play with some color settings to try to fix the issue, but none of them work. STEPS TO REPRODUCE 1. 2. 3. 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.
[krita] [Bug 409636] New: Can you add layer clip locking? In ps, you can hold down the ALT key to lock the lower color area, and in medibang, you can also have tabs.
https://bugs.kde.org/show_bug.cgi?id=409636 Bug ID: 409636 Summary: Can you add layer clip locking? In ps, you can hold down the ALT key to lock the lower color area, and in medibang, you can also have tabs. Product: krita Version: 4.2.1 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: wishlist Priority: NOR Component: Filter Layers Assignee: krita-bugs-n...@kde.org Reporter: 366995...@qq.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: win10 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.
[krita] [Bug 409635] New: 4.2.2 Can not open the software, open it and show no response, and then exit.
https://bugs.kde.org/show_bug.cgi?id=409635 Bug ID: 409635 Summary: 4.2.2 Can not open the software, open it and show no response, and then exit. Product: krita Version: 4.2.2 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: crash Priority: NOR Component: tablet support Assignee: krita-bugs-n...@kde.org Reporter: 366995...@qq.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: win10 64 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.
[konsole] [Bug 409563] Konsole does not send shift+tab (backtab) to terminal
https://bugs.kde.org/show_bug.cgi?id=409563 --- Comment #2 from Radon Rosborough --- Thanks, I can confirm that fixes the issue. It did not occur to me that there would be a place for customizing the behavior of the keyboard aside from Edit Current Profile > Keyboard. I now see that there are several different menu items for the settings; perhaps they could be unified to avoid confusion. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 409349] Offer a window placement mode that remembers windows' prior positioning
https://bugs.kde.org/show_bug.cgi?id=409349 --- Comment #3 from Nate Graham --- 1. Would it be possible for KWin to override the windows' own placement when using this mode? 2. If the window manager specs don't easily allow for this behavior, can the specs be changed? Particularly for Wayland, which is still accumulating new protocols on a semi-regular basis, I would hope that a spec that doesn't allow for a desirable feature could be changed to facilitate it. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-krunner] [Bug 381835] RunnerManager::queryFinished never emitted
https://bugs.kde.org/show_bug.cgi?id=381835 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- 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 #15 from sepulchrewra...@protonmail.com --- Created attachment 121408 --> https://bugs.kde.org/attachment.cgi?id=121408=edit logcat entry from Samsung S9 -- 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 sepulchrewra...@protonmail.com changed: What|Removed |Added CC||SepulchreWraith@protonmail. ||com --- Comment #14 from sepulchrewra...@protonmail.com --- Adding to this, with version 1.12.93 on Android, with a Samsung Galaxy S9, running the latest firmware, an error is still occurring when fetching conversations. Seems that the request to the phone isn't returning what the code is expecting, and is throwing a NullPointer exception in the onPacketReceived handler -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 401582] Rubber-band selecting one item from its metadata column and shift-clicking another item does not include the items between them in the selection
https://bugs.kde.org/show_bug.cgi?id=401582 --- Comment #11 from Nate Graham --- Yep. :) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 409629] Plasma shell freezes and/or stops rendering elements
https://bugs.kde.org/show_bug.cgi?id=409629 --- Comment #3 from S --- Hi, I tried switching to the official Intel driver for Xorg, but it is giving me the same trouble. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 409380] Formatting by KSyntaxHighlighting::SyntaxHighlighter of normal text seems to be dropped partially (Qt >=5.13.0/5.12.4)
https://bugs.kde.org/show_bug.cgi?id=409380 --- Comment #4 from 3ndymion <3ndym...@protonmail.com> --- I just realized... from looking at the screen close & at a different angle, I can see that the text preview actually is there. It is indeed nearly white text on a white background. I never realized that until just now. But I guess that's what you were saying in your explanation. My apologies, I had a bit of trouble understanding everything you wrote. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 408594] color saturation in blurred regions is higher than expected
https://bugs.kde.org/show_bug.cgi?id=408594 --- Comment #30 from Fredrik Höglund --- (In reply to Fabian Vogt from comment #27) > > So I'm going to solve this by blacklisting sRGB configs on LLVMPipe instead. > > That sounds like a bit too much, everything except cirrus with 16bpp seems to > work. Unfortunately we can't easily detect that the video device is a Cirrus device. The OpenGL driver can only tell us that it is llvmpipe; it doesn't know where the results of the rendering is going to be presented. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kinit] [Bug 409514] DE freezes randomly
https://bugs.kde.org/show_bug.cgi?id=409514 --- Comment #4 from Avamander --- Also reported on Freedesktop: https://bugs.freedesktop.org/show_bug.cgi?id=111091 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 408594] color saturation in blurred regions is higher than expected
https://bugs.kde.org/show_bug.cgi?id=408594 Fredrik Höglund changed: What|Removed |Added Latest Commit||https://commits.kde.org/kwi ||n/5191311d36fbbbe51a3c137f3 ||6148a662a099963 Resolution|--- |FIXED Status|CONFIRMED |RESOLVED Version Fixed In||5.16.3 --- Comment #29 from Fredrik Höglund --- Git commit 5191311d36fbbbe51a3c137f36148a662a099963 by Fredrik Höglund. Committed on 08/07/2019 at 22:43. Pushed by fredrik into branch 'Plasma/5.16'. [effects/blur] Disable sRGB when the framebuffer is linear Disable sRGB rendering when the color encoding of the default framebuffer is linear. FIXED-IN: 5.16.3 Differential Revision: https://phabricator.kde.org/D22153 Signed-off-by: Fredrik Höglund M +28 -5effects/blur/blur.cpp https://commits.kde.org/kwin/5191311d36fbbbe51a3c137f36148a662a099963 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409019] Krita text box wont display pasted text correctly
https://bugs.kde.org/show_bug.cgi?id=409019 --- Comment #7 from Dave --- Yes, 4.2.1 solved this. Thank you so much, Dave On Sun, Jun 23, 2019 at 3:17 AM Ahab Greybeard wrote: > https://bugs.kde.org/show_bug.cgi?id=409019 > > Ahab Greybeard changed: > >What|Removed |Added > > > Status|REPORTED|NEEDSINFO > Resolution|--- |WAITINGFORINFO > > --- Comment #4 from Ahab Greybeard --- > Waiting for the bug report author to confirm all is well with 4.2.1. > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409019] Krita text box wont display pasted text correctly
https://bugs.kde.org/show_bug.cgi?id=409019 --- Comment #6 from Dave --- I've never heard of your bug status procedure and have not received an email on it since your initial response. Can you post a link where I might be able to respond with the results? Your HowTo link looks more like protocol for someone receiving a bug inquiry? Mahalo, Dave On Sun, Jul 7, 2019 at 6:33 PM Bug Janitor Service wrote: > https://bugs.kde.org/show_bug.cgi?id=409019 > > --- Comment #5 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 reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 394029] Auto x/y-range keeps constant
https://bugs.kde.org/show_bug.cgi?id=394029 --- Comment #3 from Uwe Stöhr --- This issue remains in LP 2.7 RC5: When I explicitly change the x-range in a plot and keep the y-range on AUTO, I expect that the y-range will automatically be adjusted to the y-range in the given x-range. So in my example changing the x-range to 1..30 should automatically change the y-range to 1..30 as well since 1..100 is senseless because there is no y > 30 for the given x-range. -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 408536] display bug in curve fitting dialog
https://bugs.kde.org/show_bug.cgi?id=408536 Uwe Stöhr changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 408270] Okular always prints in A4 on physical printers, even when Letter is the default
https://bugs.kde.org/show_bug.cgi?id=408270 Matthew Trescott changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #18 from Matthew Trescott --- Same problem happens with Kate. :/ -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 408536] display bug in curve fitting dialog
https://bugs.kde.org/show_bug.cgi?id=408536 Uwe Stöhr changed: What|Removed |Added CC||uwesto...@web.de --- Comment #1 from Uwe Stöhr --- Created attachment 121405 --> https://bugs.kde.org/attachment.cgi?id=121405=edit screenshot of LP 2.7 RC5 The bug is now fixed in RC5, Many thanks! -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 358889] Scrollbar in left subwindow
https://bugs.kde.org/show_bug.cgi?id=358889 --- Comment #7 from Sascha Gaspar --- Sorry, I did not see the progress. But for some time this does not happen anymore. (I use an other desktop resolution but I don't think that's the cause. Now 4k instead of 2560x1600.) -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 358888] Multiple password dialogs
https://bugs.kde.org/show_bug.cgi?id=35 --- Comment #5 from Sascha Gaspar --- Sorry, I did not see the progress. But now, in Plasma 5.16.2 it is fixed. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 409634] Color theme name translations
https://bugs.kde.org/show_bug.cgi?id=409634 --- Comment #1 from Sascha Gaspar --- Created attachment 121404 --> https://bugs.kde.org/attachment.cgi?id=121404=edit Screenshot -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 409634] New: Color theme name translations
https://bugs.kde.org/show_bug.cgi?id=409634 Bug ID: 409634 Summary: Color theme name translations Product: systemsettings Version: 5.16.2 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_desktoptheme Assignee: plasma-b...@kde.org Reporter: sascha.gas...@gmx.de Target Milestone: --- SUMMARY In the German translation of the GUI I get an error message in the color theme settings dialog: "Das Farbschema "Breeze-Dunkel" ist nicht installiert. Es wird stattdessen das Standardschema installiert." This means "The color sceme "Breeze-Dark" is not installed." I think, this may be a problem with the translation. I think breeze-dark is installed. See also the attached screenshot. I think you know what I mean. STEPS TO REPRODUCE Not sure: 1. Use german UI. 2. Select theme "Breeze-Dark" 3. Go to color settings OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Linux/KDE Plasma: OpenSuSE Tumbleweed KDE Plasma Version: 5.16.2 KDE Frameworks Version: 5.59.0 Qt Version: 5.13.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 409596] Adding a lambda as a template argument in a specific project (of mine) causes a crash when trying to parse a file.
https://bugs.kde.org/show_bug.cgi?id=409596 --- Comment #3 from Matti --- Adding `std::cout << "Visiting cursor\n";` to the Visitor::dispatchCursor method shows that that part of code isn't even touched before the crash. -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 407854] Solver is slow and logs too much to ~/.xsession-errors
https://bugs.kde.org/show_bug.cgi?id=407854 --- Comment #2 from Albert Astals Cid --- *** Bug 409602 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 409602] Spider outputting large (GB) of data to ~/.xsession-errors file
https://bugs.kde.org/show_bug.cgi?id=409602 Albert Astals Cid changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED CC||aa...@kde.org --- Comment #1 from Albert Astals Cid --- *** This bug has been marked as a duplicate of bug 407854 *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409617] Krita goes unresponsive while editing text
https://bugs.kde.org/show_bug.cgi?id=409617 --- Comment #3 from Annabel --- (In reply to Annabel from comment #2) > I recreated the crash with steps like this: > 1. I started writing text > 2. Changed font to MV boli, size 7, center alignment > 3. click save > 4. Not responding After continuous trying, the problem seems to be the text I write - pressing shift enter. Using just enter does not result with program not responding -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 409589] Text containing newline not prefilled using "Search/replace"
https://bugs.kde.org/show_bug.cgi?id=409589 --- Comment #1 from Dominik Haumann --- Hm, I think this is by design. Two reasons: 1. When multiple lines are selected, the "selection only" option is automatically turned on. 2. Assume you select the entire document. You wouldn't want all the document content in one line edit. To me, this looks like a functions-as-designed. As workaround, I suggest to Ctrl+C before Ctrl+f, then you just need to Ctrl+v and you have what you want. ...I currently don't know whether newlines are converted into \n characters, though. Any other thoughts? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 409633] New: Tapping on drawerhandle does nothing on Plasma Mobile
https://bugs.kde.org/show_bug.cgi?id=409633 Bug ID: 409633 Summary: Tapping on drawerhandle does nothing on Plasma Mobile Product: frameworks-kirigami Version: Master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: notm...@gmail.com Reporter: nicolas.fe...@gmx.de Target Milestone: Not decided STEPS TO REPRODUCE 1. Open a Kirigami app (e.g. Itinerary or KDE Connect) on the Nexus 5X running Plasma Mobile 2. Tap the global or context drawer handle OBSERVED RESULT Nothing happens EXPECTED RESULT Drawer opens ADDITIONAL INFORMATION: Dragging the handle opens the drawer It works fine on the desktop, even when forced to mobile mode -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 401366] I get duplicate notifications for wifi connection to KDEConnect and phone calls.
https://bugs.kde.org/show_bug.cgi?id=401366 XimeX changed: What|Removed |Added CC||rupprecht.thomas+kde@gmail. ||com -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 408974] notifictaion spam from SMS messates on my phone
https://bugs.kde.org/show_bug.cgi?id=408974 XimeX changed: What|Removed |Added CC||rupprecht.thomas+kde@gmail. ||com --- Comment #5 from XimeX --- I could confirm this bug. I also got many duplicates of the same notification. I use Signal on Android as messaging app. This looks like the same bug: https://bugs.kde.org/show_bug.cgi?id=401366 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409617] Krita goes unresponsive while editing text
https://bugs.kde.org/show_bug.cgi?id=409617 --- Comment #2 from Annabel --- I recreated the crash with steps like this: 1. I started writing text 2. Changed font to MV boli, size 7, center alignment 3. click save 4. Not responding -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 409580] Cantor crashes upon python2 backend interruption after showing the Mayavi demo
https://bugs.kde.org/show_bug.cgi?id=409580 vialav changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED --- Comment #3 from vialav --- Thank you, yes, the behaviour has definitely improved under both Pythons 2/3. There is no crash either if I interrupt the backend prematurely, as it has been the reported case (see also below), or after auto-moving the data to the Variable Manager window has been finalized. There is a lag, indeed, between closing the VTK/Mayavi window and Cantor returning to its original readiness, which I had wrongly assumed as a hang on 'Calculating…'. If I had waited for longer, possibly, I wouldn't have hit the present bug :) Auto-reloading the Var Manager, also upon walking over the tabs, contributes to a lag, especially with such big data, see to this my comment in Bug 409520 #3 in the past. There may be a room for rethinking the Var Manager implementation, as a suggestion. Closing as resolved, and thank you for looking into this matter. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 409632] New: Konqueror does not shut down properly.
https://bugs.kde.org/show_bug.cgi?id=409632 Bug ID: 409632 Summary: Konqueror does not shut down properly. Product: konqueror Version: 5.0.97 Platform: Debian stable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: konq-b...@kde.org Reporter: ogla...@gmail.com Target Milestone: --- SUMMARY After shutting down Konqueror, either via quit or the "X", it will not restart. Actually, the process is running. I find it using ksysguard. If I kill the process, konqueror will restart as it should. STEPS TO REPRODUCE 1. Start Konqueror 2. Shut down Konqueror 3. Attempt to restart Konqueror 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.
[frameworks-ktexteditor] [Bug 314395] Automatic indentation of subsequent lines in kate is erratic
https://bugs.kde.org/show_bug.cgi?id=314395 Christoph Cullmann changed: What|Removed |Added Version Fixed In||5.61.0 Resolution|--- |FIXED Latest Commit||https://commits.kde.org/kte ||xteditor/01526bfcb7e811dbc7 ||87f2fdf2924f30d7f8324c Status|CONFIRMED |RESOLVED --- Comment #31 from Christoph Cullmann --- Git commit 01526bfcb7e811dbc787f2fdf2924f30d7f8324c by Christoph Cullmann, on behalf of Ahmad Samir. Committed on 08/07/2019 at 20:59. Pushed by cullmann into branch 'master'. Add an action to insert a non-indented newline Summary: Currently pressing Enter to insert a new line, KTextEditor will, in most cases, indent the new line with the same indentation as the previous line, which makes sense when writing code. But there is a viable use case where a user may want to insert a new line to separate blocks of code that have different context/functionality inside a function, in that case that line should be non-indented, having trailing spaces on an empty line isn't good, IMHO. The new action can be triggered with Ctrl+Enter. And the current default behaviour is preserved. FIXED-IN: 5.61.0 Test Plan: - Open a file with some C++ code, put the cursor at the end of an indented line, and press Enter to insert a new line - Note that the new line is indented - Repeat the first step, but press Ctrl+Enter; the newly inserted line has no indentation Reviewers: #ktexteditor, cullmann, dhaumann Reviewed By: #ktexteditor, cullmann Subscribers: bruns, mickaelbo, kde-frameworks-devel, kwrite-devel Tags: #kate, #frameworks Differential Revision: https://phabricator.kde.org/D22276 M +6-3src/document/katedocument.cpp M +3-1src/document/katedocument.h M +17 -0src/view/kateview.cpp M +8-0src/view/kateview.h https://commits.kde.org/ktexteditor/01526bfcb7e811dbc787f2fdf2924f30d7f8324c -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 409513] Dolphin crashes on copying
https://bugs.kde.org/show_bug.cgi?id=409513 --- Comment #2 from Avamander --- Created attachment 121403 --> https://bugs.kde.org/attachment.cgi?id=121403=edit Crash log #3 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 409620] Plasma 5.16.2 Blur Noise Level Issue
https://bugs.kde.org/show_bug.cgi?id=409620 --- Comment #5 from duncanyo...@gmail.com --- Created attachment 121402 --> https://bugs.kde.org/attachment.cgi?id=121402=edit Konsole Blur Level 15 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 409620] Plasma 5.16.2 Blur Noise Level Issue
https://bugs.kde.org/show_bug.cgi?id=409620 --- Comment #4 from duncanyo...@gmail.com --- Vlad, thank you for the quick reply. I think something needs to be changed, because over a dark background the noise stands out too much now. It looks fine with a light background. Before it looked great with light or dark behind the window. The noise looks quite a bit different from when the noise was implemented. Look at level 15/15 from when the noise was added. And now look at level 15. Maybe a small change to how the values are calculated when the background is dark to make the noise slightly darker? Seems like it is being lightened too much currently. I think since the sRGB change the noise levels need an adjustment. I really like the noise itself, I think it makes a big difference in the look and feel of Plasma. -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 409631] New: Associations are sometime not addable in class diagram
https://bugs.kde.org/show_bug.cgi?id=409631 Bug ID: 409631 Summary: Associations are sometime not addable in class diagram Product: umbrello Version: 2.28.2 (KDE Applications 19.04.2) Platform: Other OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: umbrello-de...@kde.org Reporter: ralf.habac...@freenet.de Target Milestone: --- One user reported today that after placing multiple classes in a class diagram, adding associations will sometimes no longer work without further hints or error messages. STEPS TO REPRODUCE not reproducable yet OBSERVED RESULT The requested association is not added to the diagram EXPECTED RESULT The requested association should be added to the diagram SOFTWARE/OS VERSIONS Windows: 7 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 409489] Can't change permissions and ownership of remote files/folders
https://bugs.kde.org/show_bug.cgi?id=409489 Rafael Linux User changed: What|Removed |Added CC||rafael.linux.u...@gmail.com --- Comment #2 from Rafael Linux User --- Thank you for the clarification, however, I have same doubt, how and who could confirm and solve or add this feature? Is a MUST when working remotely with servers. Thank you -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 409224] kmail with >=mariadb-10.4.6: not able to refresh email list: Unable to append status flags
https://bugs.kde.org/show_bug.cgi?id=409224 Filzmaier Josef changed: What|Removed |Added CC||j.filzma...@gmx.at -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 405572] font dpi not saved/loaded correctly
https://bugs.kde.org/show_bug.cgi?id=405572 --- Comment #7 from Adomas Jackevičius --- (In reply to Adomas Jackevičius from comment #6) Forgot that this started with 5.16, and not 5.15 as in this report. For sure we need a separate bug-report -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 405572] font dpi not saved/loaded correctly
https://bugs.kde.org/show_bug.cgi?id=405572 Adomas Jackevičius changed: What|Removed |Added CC||adomas@gmail.com --- Comment #6 from Adomas Jackevičius --- (In reply to Eugene Shalygin from comment #5) > Same problem here. Easy reproducible: > > 1. Enable "Force fonts DPI", set to any non-default value (use 128 here). > 2. click "Apply", close systemsettings. > 3. Open the fonts KCM again. > > Result: "Force fonts DPI" is enabled, the value is reset to 96. Not sure if your issue is same like in this bug-report. I have issue exactly like yours. I set "Force font DPI" to 144 to achieve 1.5 scaling. When I visit that KCM module again, it always shows 96, if I want to keep 144, I must set it to 144, otherwise any other action forces 96 to apply. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 409630] New: Pagerow needs some right padding
https://bugs.kde.org/show_bug.cgi?id=409630 Bug ID: 409630 Summary: Pagerow needs some right padding Product: frameworks-kirigami Version: Master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: notm...@gmail.com Reporter: nicolas.fe...@gmx.de Target Milestone: Not decided Created attachment 121401 --> https://bugs.kde.org/attachment.cgi?id=121401=edit Screenshot SUMMARY On mobile and with a page with a long title the pagerow text can easily reach the right edge. Some padding would make it look better -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 393517] Window Decorations menu entry does not load when using 2x scaling (HiDPI)
https://bugs.kde.org/show_bug.cgi?id=393517 Adomas Jackevičius changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Adomas Jackevičius --- No longer happens in 5.16.2 Not sure which to choose, so to close this I choose RESOLVED -> FIXED. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 408456] Double Entries in Shortcuts
https://bugs.kde.org/show_bug.cgi?id=408456 David Edmundson changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |NOT A BUG --- Comment #3 from David Edmundson --- >Wipe your kdeglobals config file ~/.config/kglobalshortcutsrc -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 409501] amd64->IR: unhandled instruction bytes
https://bugs.kde.org/show_bug.cgi?id=409501 --- Comment #6 from 4ctrl.alt@gmail.com --- That makes sense thanks. It looks like XOP was abandoned by AMD with Zen which probably makes it even less of a priority. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 409501] amd64->IR: unhandled instruction bytes
https://bugs.kde.org/show_bug.cgi?id=409501 Tom Hughes changed: What|Removed |Added CC||t...@compton.nu --- Comment #5 from Tom Hughes --- Because nobody has provided a patch to implement it? Perhaps you are under the belief that we have a full time team of programmers paid to read each new architecture and immediately implement all the new instructions? I'm afraid that is not how it works. The simple answer is that commonly used instructions are always going to be the first to get implemented when only limited resources are available, and instructions specific to a minority processor brand are less likely to get done because most people build code to target a broad range of processors so will never encounter such instructions. Of course if somebody offers a high quality patch to implement them then I'm sure it would be gratefully accepted. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 408493] Desktop briefly visible before lock screen appears
https://bugs.kde.org/show_bug.cgi?id=408493 Martin Flöser changed: What|Removed |Added Component|general |general CC||bhus...@gmail.com Product|kwin|kscreenlocker Version|5.15.5 |unspecified Assignee|kwin-bugs-n...@kde.org |plasma-b...@kde.org --- Comment #1 from Martin Flöser --- Most likely a graphics driver failure. The infrastructure ensures to lock prior to suspend. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409460] Canvas pan & zoom frame 'spacing' inconsistent
https://bugs.kde.org/show_bug.cgi?id=409460 --- Comment #9 from Aaron Lavarnway --- Created attachment 121400 --> https://bugs.kde.org/attachment.cgi?id=121400=edit New package slow motion Notice how the blue cross moves at an inconsistent speed, despite the cursor updating correctly. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409460] Canvas pan & zoom frame 'spacing' inconsistent
https://bugs.kde.org/show_bug.cgi?id=409460 --- Comment #8 from Aaron Lavarnway --- Hey Dmitry, this package seems to be noticeably smoother, though it's hard to tell. Taking more high speed footage, I've found that instead of getting 'stuck' every other frame, it's now only getting stuck every couple of frames. So It's still stuttery on my end, though smoother in general. Turning on QT's FPS debug causes the canvas to hang every second, giving a lower FPS of ~32 in the debug logs, though when I use Krita's built-in OpenGL FPS reporter, it shows a consistent 100+ FPS in the upper left corner. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408497] Can't run Htop on Wayland session
https://bugs.kde.org/show_bug.cgi?id=408497 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com --- Comment #3 from Patrick Silva --- I can confirm this problem on Arch Linux. Htop opens as expected on Wayland session if I set Gnome Termnial as default terminal emulator in system settings > applications > default applications. Operating System: Arch Linux KDE Plasma Version: 5.16.2 KDE Frameworks Version: 5.59.0 Qt Version: 5.13.0 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409460] Canvas pan & zoom frame 'spacing' inconsistent
https://bugs.kde.org/show_bug.cgi?id=409460 --- Comment #7 from Aaron Lavarnway --- Created attachment 121399 --> https://bugs.kde.org/attachment.cgi?id=121399=edit DebugView logs -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 409563] Konsole does not send shift+tab (backtab) to terminal
https://bugs.kde.org/show_bug.cgi?id=409563 Mariusz Glebocki changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=402161 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 402161] Backtab (Shift+Tab) is inhibited in Yakuake
https://bugs.kde.org/show_bug.cgi?id=402161 Mariusz Glebocki changed: What|Removed |Added CC||m...@arccos-1.net Status|REPORTED|RESOLVED See Also||https://bugs.kde.org/show_b ||ug.cgi?id=409563 Version Fixed In||19.08 Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 408456] Double Entries in Shortcuts
https://bugs.kde.org/show_bug.cgi?id=408456 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com Status|RESOLVED|REOPENED Ever confirmed|0 |1 Resolution|NOT A BUG |--- --- Comment #2 from Patrick Silva --- Plasma 5.16.2w has the same bug on Arch Linux. Deleting kdeglobals file did not help. Operating System: Arch Linux KDE Plasma Version: 5.16.2 KDE Frameworks Version: 5.59.0 Qt Version: 5.13.0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 409524] _KDE_NET_WM_BLUR_BEHIND_REGION=0 does not always cause window backgrounds to be blurred
https://bugs.kde.org/show_bug.cgi?id=409524 --- Comment #24 from Szczepan Hołyszewski --- In a perfect world I would animate the blur radius. We're not living in a perfect world. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 409563] Konsole does not send shift+tab (backtab) to terminal
https://bugs.kde.org/show_bug.cgi?id=409563 Mariusz Glebocki changed: What|Removed |Added CC||m...@arccos-1.net Resolution|--- |FIXED Version Fixed In||19.08 Status|REPORTED|RESOLVED --- Comment #1 from Mariusz Glebocki --- To make Shift+Tab work on 19.04, please remove Shift+Tab shortcut in Settings → Configure shortcuts (by default assigned to "Next View Container"). It is fixed on master. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 409501] amd64->IR: unhandled instruction bytes
https://bugs.kde.org/show_bug.cgi?id=409501 --- Comment #4 from 4ctrl.alt@gmail.com --- I'm confused why valgrind version 3.14 released in October of 2018 does not recognize an XOP instruction that AMD announced in May of 2008. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 409524] _KDE_NET_WM_BLUR_BEHIND_REGION=0 does not always cause window backgrounds to be blurred
https://bugs.kde.org/show_bug.cgi?id=409524 --- Comment #23 from Szczepan Hołyszewski --- In other words, admixture of unblurred background is acceptable during opacity animation when the animation is associated with showing/hiding the window. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 409524] _KDE_NET_WM_BLUR_BEHIND_REGION=0 does not always cause window backgrounds to be blurred
https://bugs.kde.org/show_bug.cgi?id=409524 --- Comment #22 from Szczepan Hołyszewski --- (In reply to Vlad Zagorodniy from comment #20) > How do you suggest to handle opacity animations? For example, an opacity > animation will be started if you open/close Kickoff. background * (1-t/duration) + preblended_blurred_background_and_content * t/duration -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 409524] _KDE_NET_WM_BLUR_BEHIND_REGION=0 does not always cause window backgrounds to be blurred
https://bugs.kde.org/show_bug.cgi?id=409524 --- Comment #21 from Szczepan Hołyszewski --- At the very least, please make blurred translucency JustWork™ for windows that that are normally opaque, but due to the settings of the translucency plugin become translucent while inactive or dragged / resized. I understand that _NET_WM_WINDOW_OPACITY is a hint *for* kwin to do the translucency, which also serves as a hint to perform background blur if that is enabled. However it seems that temporary translucency for inactive or moved windows does not work by setting the hint, and does not implement the "use translucency as a hint for blur" logic either. This I believe should be fixed, and I will be happy-ish to limit the settings to moderate translucency so that the admixture of unblurred background won't be visible. -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 409580] Cantor crashes upon python2 backend interruption after showing the Mayavi demo
https://bugs.kde.org/show_bug.cgi?id=409580 Nikita Sirgienko changed: What|Removed |Added Status|CONFIRMED |NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #2 from Nikita Sirgienko --- Wrong confirmation, mayavi crash python2 in my system by itself, even in interpteter. I have tested this code in python3, all works fine, (with disable image integration). Entry with `show` command have finished after closing mayavi plot windows as expected. There is possibility, that Cantor behaviour, which you have discribed, the result of wrong crash handling. I have improved the handling, so could you tests this code with python3 and python2? -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 408467] Can't mark and copy text from the description
https://bugs.kde.org/show_bug.cgi?id=408467 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 408468] [Wayland] Yakuake expands in a background of Kickoff-panel when it is located at the top of the screen
https://bugs.kde.org/show_bug.cgi?id=408468 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com --- Comment #2 from Patrick Silva --- It seems related/duplicate to/of bug 386114 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 409524] _KDE_NET_WM_BLUR_BEHIND_REGION=0 does not always cause window backgrounds to be blurred
https://bugs.kde.org/show_bug.cgi?id=409524 --- Comment #20 from Vlad Zagorodniy --- (In reply to Szczepan Hołyszewski from comment #19) > The client is far from invisible at alpha=0.25. How do you suggest to handle opacity animations? For example, an opacity animation will be started if you open/close Kickoff. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 409524] _KDE_NET_WM_BLUR_BEHIND_REGION=0 does not always cause window backgrounds to be blurred
https://bugs.kde.org/show_bug.cgi?id=409524 --- Comment #19 from Szczepan Hołyszewski --- (In reply to Vlad Zagorodniy from comment #18) > There's no point for showing blurred background if the client is invisible. > This is intentional and it's not gonna change. The client is far from invisible at alpha=0.25. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 409629] Plasma shell freezes and/or stops rendering elements
https://bugs.kde.org/show_bug.cgi?id=409629 --- Comment #2 from S --- Created attachment 121398 --> https://bugs.kde.org/attachment.cgi?id=121398=edit A popup notification (Firefox browser in background) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 409629] Plasma shell freezes and/or stops rendering elements
https://bugs.kde.org/show_bug.cgi?id=409629 --- Comment #1 from S --- Created attachment 121397 --> https://bugs.kde.org/attachment.cgi?id=121397=edit Opening the popup calendar widget -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 409629] New: Plasma shell freezes and/or stops rendering elements
https://bugs.kde.org/show_bug.cgi?id=409629 Bug ID: 409629 Summary: Plasma shell freezes and/or stops rendering elements Product: plasmashell Version: 5.16.2 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: sb56...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Hi, I started experiencing this major bug in one of the recent Plasma/KDE/KF5 updates for openSUSE Tumbleweed (within the past week). Very frequently (within an hour or less) I notice that the Plama panel clock stops updating, and the App Menu and Calendar popups stop rendering (just the outline), and notification popups show black with a copy of the panel underneath. When I restart `plasmashell` it fixes it for a while, but later starts glitching again. This is on a Thinkpad T530 laptop with integrated Intel graphics, running the X modesetting drivers (not xorg-intel driver). I tried switching the KWin compositor from X11 rendering to openGL, but it made no difference. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409460] Canvas pan & zoom frame 'spacing' inconsistent
https://bugs.kde.org/show_bug.cgi?id=409460 --- Comment #6 from Dmitry Kazakov --- If you still have a problem with the package, please try to generate the FPS log for me: 1) Download DebugView and start it: https://docs.microsoft.com/en-us/sysinternals/downloads/debugview 2) Start 'cmd.exe' 3) Type: set QT_DEBUG_FPS=1 4) Type the path to Krita executable: C:\Path_To_Krita_Package\bin\krita.exe 5) When Krita starts, start panning an pan continuosly for at least 15 seconds (you'll see three messages in DebugView reporting FPS, they appear every 5 seconds). Attach the result to the bug. It would be also interesting for me to see FPS log for the release 4.2.2 package. PS: On my system FPS is 140fps whatever the settings are, so I cannot see any difference. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 409524] _KDE_NET_WM_BLUR_BEHIND_REGION=0 does not always cause window backgrounds to be blurred
https://bugs.kde.org/show_bug.cgi?id=409524 --- Comment #18 from Vlad Zagorodniy --- (In reply to Szczepan Hołyszewski from comment #17) > Well, that's the problem right there. They shouldn't be. Background is > background is background. There's no point for showing blurred background if the client is invisible. This is intentional and it's not gonna change. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 409559] Systemsettings' minimum window size is too large: 1032x733
https://bugs.kde.org/show_bug.cgi?id=409559 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Patrick Silva --- *** This bug has been marked as a duplicate of bug 395476 *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 395476] The minimum window size of System Settings is too big for a 1366x768 screen
https://bugs.kde.org/show_bug.cgi?id=395476 Patrick Silva changed: What|Removed |Added CC||aspotas...@gmail.com --- Comment #10 from Patrick Silva --- *** Bug 409559 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[ktouch] [Bug 409628] BarChart for errors on the score screen is broken
https://bugs.kde.org/show_bug.cgi?id=409628 Sebastian Gottfried changed: What|Removed |Added Status|REPORTED|RESOLVED Latest Commit||https://commits.kde.org/kto ||uch/45abc5feef1e903582d19d5 ||d8fbe1fb5164454a3 Resolution|--- |FIXED Version Fixed In||19.08.0 --- Comment #1 from Sebastian Gottfried --- Git commit 45abc5feef1e903582d19d5d8fbe1fb5164454a3 by Sebastian Gottfried. Committed on 08/07/2019 at 18:57. Pushed by gottfried into branch 'master'. Score Screen: Fix Display of Error Chart Now the error chart fills its designated content area. FIXED-IN: 19.08.0 M +21 -23 src/qml/scorescreen/ScoreScreen.qml https://commits.kde.org/ktouch/45abc5feef1e903582d19d5d8fbe1fb5164454a3 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 409524] _KDE_NET_WM_BLUR_BEHIND_REGION=0 does not always cause window backgrounds to be blurred
https://bugs.kde.org/show_bug.cgi?id=409524 --- Comment #17 from Szczepan Hołyszewski --- (In reply to Vlad Zagorodniy from comment #16) > RE: Screenshots > > Opacity of the client and opacity of the blurred background are connected. Well, that's the problem right there. They shouldn't be. Background is background is background. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 409596] Adding a lambda as a template argument in a specific project (of mine) causes a crash when trying to parse a file.
https://bugs.kde.org/show_bug.cgi?id=409596 --- Comment #2 from Matti --- I have reduced the bug down to just a header and a main.cpp (which just imports the header). Directly pasting the header into main.cpp does not reproduce the bug. See the reduced-code repo to see exactly what code is triggering the crash. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 409524] _KDE_NET_WM_BLUR_BEHIND_REGION=0 does not always cause window backgrounds to be blurred
https://bugs.kde.org/show_bug.cgi?id=409524 --- Comment #16 from Vlad Zagorodniy --- RE: Screenshots Opacity of the client and opacity of the blurred background are connected. -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 409147] Albums appear duplicated if they have different artists
https://bugs.kde.org/show_bug.cgi?id=409147 Alexander Stippich changed: What|Removed |Added CC||a.stipp...@gmx.net --- Comment #7 from Alexander Stippich --- I think this is a result of https://phabricator.kde.org/D20531 Without this, albums of tracks without an album artist tag would not be added to the database. Elisa should probably use more metadata to correctly guess the album artist. The current behavior is also one I've seen with other players I think. Actually, how should Elisa actually know what the correct artist name is? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 409524] _KDE_NET_WM_BLUR_BEHIND_REGION=0 does not always cause window backgrounds to be blurred
https://bugs.kde.org/show_bug.cgi?id=409524 --- Comment #15 from Vlad Zagorodniy --- (In reply to Szczepan Hołyszewski from comment #11) > If I am dragging a supposedly "opaque" window, but I am seeing the > background behind it while I am dragging it, The client buffer should have alpha, though I guess we can address this issue. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 408493] Desktop briefly visible before lock screen appears
https://bugs.kde.org/show_bug.cgi?id=408493 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
