[digikam] [Bug 411882] I don't get image stack or panorama
https://bugs.kde.org/show_bug.cgi?id=411882 Maik Qualmann changed: What|Removed |Added Status|REPORTED|RESOLVED Version Fixed In||6.4.0 Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 411882] I don't get image stack or panorama
https://bugs.kde.org/show_bug.cgi?id=411882 Maik Qualmann changed: What|Removed |Added Component|ImageEditor |Plugin-Generic-ExpoBlending -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 403269] Stacked image and Panorama tools cannot find required binaries
https://bugs.kde.org/show_bug.cgi?id=403269 Maik Qualmann changed: What|Removed |Added Status|REPORTED|RESOLVED Version Fixed In||6.4.0 Resolution|--- |FIXED --- Comment #27 from Maik Qualmann --- OK, I close the bug now. Without debug mode, all programs are now found. If necessary, reopen the bug. Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 411651] New tool to export photos to Canon Irista
https://bugs.kde.org/show_bug.cgi?id=411651 Maik Qualmann changed: What|Removed |Added Version Fixed In||6.4.0 Resolution|--- |INTENTIONAL Status|REPORTED|RESOLVED --- Comment #5 from Maik Qualmann --- Ok, I close the bug, we can not do anything. If a public API is available, reopen the bug. Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 411612] When using Tags Manager and then closing crashes digikam
https://bugs.kde.org/show_bug.cgi?id=411612 --- Comment #5 from Maik Qualmann --- A new developer version is available. Is the problem still to reproduce? https://files.kde.org/digikam/ Maik -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 411890] New: Add Breeze SDDM login screen blur and font color settings
https://bugs.kde.org/show_bug.cgi?id=411890 Bug ID: 411890 Summary: Add Breeze SDDM login screen blur and font color settings Product: Breeze Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: msdobre...@gmail.com Target Milestone: --- SUMMARY There were many complaints about the readability and the blur effect of the Breeze SDDM screen. I've run into this myself lately, when I've set an image with a simple sea shore. It becomes hideous and disgusting when the blur occurs. I've seen a lot of discussions on how to fix that and manual workarounds that were overridden at update time. EXPECTED RESULT Please add settings for the font colour and shadow thickness (if there is one), and, of course, blur configuration for blur amount, timeouts and add the possibility to disable it completely, all these settings accessible to the user in the KDE theme settings for the SDDM login screen. SOFTWARE/OS VERSIONS Windows: Are you kidding? macOS: nope Linux/KDE Plasma: Linux Sabayon 64-bit, kernel 5.2.0-sabayon KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.61.0 Qt Version: 5.12.4 ADDITIONAL INFORMATION I love KDE! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 411506] Kwin requires constant restart after weeks of uptime to refresh windows
https://bugs.kde.org/show_bug.cgi?id=411506 --- Comment #16 from Vlad Zahorodnii --- > Requires strict binding: no That line shows whether loose binding is supported by the driver. Use this command instead qdbus org.kde.KWin /KWin supportInformation | grep glStrictBinding If everything is okay, you should see glStrictBinding: true glStrictBindingFollowsDriver: true -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 411891] New: Digikam crashes on startup
https://bugs.kde.org/show_bug.cgi?id=411891 Bug ID: 411891 Summary: Digikam crashes on startup Product: digikam Version: 6.3.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: digikam-bugs-n...@kde.org Reporter: jens.ra...@gmail.com Target Milestone: --- Application: digikam (6.3.0) Qt Version: 5.13.1 Frameworks Version: 5.61.0 Operating System: Linux 5.2.14-zen2-1-zen x86_64 Distribution: "Arch Linux" -- Information about the crash: - What I was doing when the application crashed: Fresh reboot, started Digikam. It opened on a secondary screen and crashed as the splash screen was visible. The crash can be reproduced every time. -- Backtrace: Application: digiKam (digikam), signal: Aborted Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fdadb280800 (LWP 1540))] Thread 21 (Thread 0x7fdab849d700 (LWP 1583)): #0 0x7fdb617ded16 in do_futex_wait.constprop () at /usr/lib/libpthread.so.0 #1 0x7fdb617dee18 in __new_sem_wait_slow.constprop.0 () at /usr/lib/libpthread.so.0 #2 0x7fdaec73c45a in () at /usr/lib/libopenal.so.1 #3 0x7fdaec6ea63f in () at /usr/lib/libopenal.so.1 #4 0x7fdaec73bfa8 in () at /usr/lib/libopenal.so.1 #5 0x7fdb617d657f in start_thread () at /usr/lib/libpthread.so.0 #6 0x7fdb618ef0e3 in clone () at /usr/lib/libc.so.6 Thread 20 (Thread 0x7fdab869e700 (LWP 1582)): #0 0x7fdb5a05e0e3 in () at /usr/lib/libm.so.6 #1 0x7fdaec70860d in () at /usr/lib/libopenal.so.1 #2 0x7fdaec6ffb1d in () at /usr/lib/libopenal.so.1 #3 0x7fdaec7353c2 in () at /usr/lib/libopenal.so.1 #4 0x7fdaec73bfa8 in () at /usr/lib/libopenal.so.1 #5 0x7fdb617d657f in start_thread () at /usr/lib/libpthread.so.0 #6 0x7fdb618ef0e3 in clone () at /usr/lib/libc.so.6 Thread 19 (Thread 0x7fdaba7e2700 (LWP 1581)): #0 0x7fdb617d880b in __pthread_mutex_lock_full () at /usr/lib/libpthread.so.0 #1 0x7fdadc122dff in pa_mutex_lock () at /usr/lib/pulseaudio/libpulsecommon-12.99.so #2 0x7fdaec684c20 in () at /usr/lib/libpulse.so.0 #3 0x7fdaec692059 in pa_mainloop_poll () at /usr/lib/libpulse.so.0 #4 0x7fdaec69c301 in pa_mainloop_iterate () at /usr/lib/libpulse.so.0 #5 0x7fdaec69c3b1 in pa_mainloop_run () at /usr/lib/libpulse.so.0 #6 0x7fdaec68c61e in () at /usr/lib/libpulse.so.0 #7 0x7fdadc112d1c in () at /usr/lib/pulseaudio/libpulsecommon-12.99.so #8 0x7fdb617d657f in start_thread () at /usr/lib/libpthread.so.0 #9 0x7fdb618ef0e3 in clone () at /usr/lib/libc.so.6 Thread 18 (Thread 0x7fda7bfff700 (LWP 1576)): #0 0x7fdb618e4667 in poll () at /usr/lib/libc.so.6 #1 0x7fdaec684c14 in () at /usr/lib/libpulse.so.0 #2 0x7fdaec692059 in pa_mainloop_poll () at /usr/lib/libpulse.so.0 #3 0x7fdaec69c301 in pa_mainloop_iterate () at /usr/lib/libpulse.so.0 #4 0x7fdaec69c3b1 in pa_mainloop_run () at /usr/lib/libpulse.so.0 #5 0x7fdaec68c61e in () at /usr/lib/libpulse.so.0 #6 0x7fdadc112d1c in () at /usr/lib/pulseaudio/libpulsecommon-12.99.so #7 0x7fdb617d657f in start_thread () at /usr/lib/libpthread.so.0 #8 0x7fdb618ef0e3 in clone () at /usr/lib/libc.so.6 Thread 17 (Thread 0x7fdaa0ff9700 (LWP 1575)): #0 0x7fdb618fc5cb in __lll_lock_wait_private () at /usr/lib/libc.so.6 #1 0x7fdb6185e514 in buffered_vfprintf () at /usr/lib/libc.so.6 #2 0x7fdb6185b764 in __vfprintf_internal () at /usr/lib/libc.so.6 #3 0x7fdb618fe123 in __fprintf_chk () at /usr/lib/libc.so.6 #4 0x7fdade0a4daf in event_logv_ () at /usr/lib/libevent-2.1.so.7 #5 0x7fdade0a4f78 in event_warn () at /usr/lib/libevent-2.1.so.7 #6 0x7fdade0a6a12 in () at /usr/lib/libevent-2.1.so.7 #7 0x7fdade09c915 in event_base_loop () at /usr/lib/libevent-2.1.so.7 #8 0x7fdaf0530548 in () at /usr/lib/libQt5WebEngineCore.so.5 #9 0x7fdaf04b9967 in () at /usr/lib/libQt5WebEngineCore.so.5 #10 0x7fdaf04fa9cf in () at /usr/lib/libQt5WebEngineCore.so.5 #11 0x7fdaf052c5f5 in () at /usr/lib/libQt5WebEngineCore.so.5 #12 0x7fdb617d657f in start_thread () at /usr/lib/libpthread.so.0 #13 0x7fdb618ef0e3 in clone () at /usr/lib/libc.so.6 Thread 16 (Thread 0x7fdaa17fa700 (LWP 1574)): [KCrash Handler] #6 0x7fdb6182d755 in raise () at /usr/lib/libc.so.6 #7 0x7fdb61818851 in abort () at /usr/lib/libc.so.6 #8 0x7fdb6186fa38 in __libc_message () at /usr/lib/libc.so.6 #9 0x7fdb618ffa85 in __fortify_fail_abort () at /usr/lib/libc.so.6 #10 0x7fdb618ffa36 in () at /usr/lib/libc.so.6 #11 0x7fdaee9d8594 in () at /usr/lib/libQt5WebEngineCore.so.5 #12 0x7fdaee9d85f6 in () at /usr/lib/libQt5WebEngineCore.so.5 #13 0x7fdaee9d9de2 in () at /usr/lib/libQt5WebEngineCore.so.5 #14 0x7fdaee9da35
[konqueror] [Bug 411892] New: Konqueror navigator
https://bugs.kde.org/show_bug.cgi?id=411892 Bug ID: 411892 Summary: Konqueror navigator Product: konqueror Version: 5.0.97 Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: konq-b...@kde.org Reporter: hpgz...@yahoo.es Target Milestone: --- Application: konqueror (5.0.97) (Compiled from sources) Qt Version: 5.9.5 Frameworks Version: 5.44.0 Operating System: Linux 5.0.0-27-generic x86_64 Distribution: Ubuntu 18.04.3 LTS -- Information about the crash: - What I was doing when the application crashed: Konqueror does not allow opening it a second time after closing it -We must restart session The crash can be reproduced every time. -- Backtrace: Application: Konqueror (konqueror), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f5fbe359840 (LWP 1626))] Thread 21 (Thread 0x7f5f327fc700 (LWP 1704)): #0 0x7f5fbdb95187 in __GI___libc_write (fd=2, buf=0x7f5f327f8e00, nbytes=50) at ../sysdeps/unix/sysv/linux/write.c:27 #1 0x7f5fbdb101bd in _IO_new_file_write (f=0x7f5fbde71680 <_IO_2_1_stderr_>, data=0x7f5f327f8e00, n=50) at fileops.c:1203 #2 0x7f5fbdb10b2f in new_do_write (to_do=, data=0x7f5f327f8e00 "[warn] epoll_wait: Descriptor de archivo err\303\263neo\n", fp=0x7f5fbde71680 <_IO_2_1_stderr_>) at fileops.c:457 #3 _IO_new_file_xsputn (f=0x7f5fbde71680 <_IO_2_1_stderr_>, data=, n=50) at fileops.c:1277 #4 0x7f5fbdae3707 in buffered_vfprintf (s=s@entry=0x7f5fbde71680 <_IO_2_1_stderr_>, format=format@entry=0x7f5f869ce6a8 "[%s] %s\n", args=args@entry=0x7f5f327fb3c0) at vfprintf.c:2350 #5 0x7f5fbdae0726 in _IO_vfprintf_internal (s=s@entry=0x7f5fbde71680 <_IO_2_1_stderr_>, format=0x7f5f869ce6a8 "[%s] %s\n", ap=ap@entry=0x7f5f327fb3c0) at vfprintf.c:1301 #6 0x7f5fbdbb74c6 in ___fprintf_chk (fp=0x7f5fbde71680 <_IO_2_1_stderr_>, flag=1, format=) at fprintf_chk.c:35 #7 0x7f5f869b69ad in event_logv_ () from /usr/lib/x86_64-linux-gnu/libevent-2.1.so.6 #8 0x7f5f869b6b44 in event_warn () from /usr/lib/x86_64-linux-gnu/libevent-2.1.so.6 #9 0x7f5f869b846c in ?? () from /usr/lib/x86_64-linux-gnu/libevent-2.1.so.6 #10 0x7f5f869ae114 in event_base_loop () from /usr/lib/x86_64-linux-gnu/libevent-2.1.so.6 #11 0x7f5f88ac0b0d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #12 0x7f5f88abcda8 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #13 0x7f5f88ad977b in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #14 0x7f5f88af14d6 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #15 0x7f5f88aed5eb in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #16 0x7f5fb32ef6db in start_thread (arg=0x7f5f327fc700) at pthread_create.c:463 #17 0x7f5fbdba688f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 20 (Thread 0x7f5f32ffd700 (LWP 1703)): #0 0x7f5fb32f59f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x7f5f32ffca78) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x7f5f32ffca28, cond=0x7f5f32ffca50) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x7f5f32ffca50, mutex=0x7f5f32ffca28) at pthread_cond_wait.c:655 #3 0x7f5f88ae5999 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f5f88ae59c7 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f5f88ac04db in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f5f88abcda8 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f5f88ad977b in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7f5f88af14d6 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7f5f88aed5eb in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7f5fb32ef6db in start_thread (arg=0x7f5f32ffd700) at pthread_create.c:463 #11 0x7f5fbdba688f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 19 (Thread 0x7f5f337fe700 (LWP 1702)): #0 0x7f5fac1a75d6 in ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so #1 0x7f5fac1a8798 in ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so #2 0x7f5fac1a8ab9 in ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so #3 0x7f5fac1a933f in ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so #4 0x7f5facd4d108 in pa_mainloop_dispatch () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #5 0x7f5facd4d4de in pa_mainloop_iterate () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #6 0x7f5facd4d560 in pa_mainloop_run () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #7 0x000
[digikam] [Bug 411891] Digikam crashes on startup
https://bugs.kde.org/show_bug.cgi?id=411891 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #1 from Maik Qualmann --- It crashes in QWebEngine. Your digiKam version is compiled with QWebEngine support instead of QWebKit. We currently recommend QWebKit. For QWebEngine you need a working and stable support of OpenGL. I also use QWebEngine in my developer version. Which graphics card and drivers do you use? Maik -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 411875] Undo Image->trim to selection shifts selection by constant amount
https://bugs.kde.org/show_bug.cgi?id=411875 --- Comment #2 from jamesnoec...@gmail.com --- Created attachment 122643 --> https://bugs.kde.org/attachment.cgi?id=122643&action=edit initial selection -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 411875] Undo Image->trim to selection shifts selection by constant amount
https://bugs.kde.org/show_bug.cgi?id=411875 --- Comment #3 from jamesnoec...@gmail.com --- Created attachment 122644 --> https://bugs.kde.org/attachment.cgi?id=122644&action=edit step 2: trim to selection For a split second when selecting trim to selection, the selection appears offset from the resized image boundaries, before jumping into place. That offset appears to be exactly the offset that gets applied to the selection when you undo the operation. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 411875] Undo Image->trim to selection shifts selection by constant amount
https://bugs.kde.org/show_bug.cgi?id=411875 --- Comment #4 from jamesnoec...@gmail.com --- Created attachment 122645 --> https://bugs.kde.org/attachment.cgi?id=122645&action=edit step3: undo -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 411875] Undo Image->trim to selection shifts selection by constant amount
https://bugs.kde.org/show_bug.cgi?id=411875 --- Comment #5 from jamesnoec...@gmail.com --- Created attachment 122646 --> https://bugs.kde.org/attachment.cgi?id=122646&action=edit step 4: redo and undo again -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 411875] Undo Image->trim to selection shifts selection by constant amount
https://bugs.kde.org/show_bug.cgi?id=411875 --- Comment #6 from jamesnoec...@gmail.com --- looking at these images, I am almost certain that the offset applied is exactly the offset of the selection to the top left corner of the image. Some correction term getting applied twice somewhere. -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 411602] Missing menu item for choose a file for all unsolved whitespace conflicts in 1.8
https://bugs.kde.org/show_bug.cgi?id=411602 michael changed: What|Removed |Added Summary|Unable to choose a file for |Missing menu item for |all unsolved whitespace |choose a file for all |conflicts in 1.8|unsolved whitespace ||conflicts in 1.8 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 411884] In wayland BorderlessMaximizedWindows can cause window to not receive input
https://bugs.kde.org/show_bug.cgi?id=411884 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 411877] Touchscreen input locked to first screen
https://bugs.kde.org/show_bug.cgi?id=411877 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 411891] Digikam crashes on startup
https://bugs.kde.org/show_bug.cgi?id=411891 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com Component|general |Geolocation --- Comment #2 from caulier.gil...@gmail.com --- Note : the AppImage bundle is compiled with QtWebEngine. Can you reproduce this problem ? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 411875] Undo Image->trim to selection shifts selection by constant amount
https://bugs.kde.org/show_bug.cgi?id=411875 --- Comment #7 from jamesnoec...@gmail.com --- also happens in the Linux 4.2.6 appimage. In fact, I scribbled on the transparent layer and in addition to the selection being shifted down and right, the top layer got shifted up and left so that the scribble was cut off. But while the selection bug happens every time, the layer getting shifted is hard to reproduce. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 411875] Undo Image->trim to selection shifts selection by constant amount
https://bugs.kde.org/show_bug.cgi?id=411875 --- Comment #8 from jamesnoec...@gmail.com --- In all cases, however, there is a short interval after cropping/undoing when everything is shifted (the layers slide out of the image boundaries and the selection is out of bounds) before it corrects itself. I guess sometimes it doesn't correct itself. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 411860] Latte panel size doesn't recover after being auto-shrunk
https://bugs.kde.org/show_bug.cgi?id=411860 --- Comment #3 from Michail Vourlakos --- I tested your layout, after 2VDs for every VD I add the items size is decreased. When I remove one VD then it does not restore but if I remove two VDs it does. Is this your system behavior? -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 411860] Latte panel size doesn't recover after being auto-shrunk
https://bugs.kde.org/show_bug.cgi?id=411860 --- Comment #4 from David --- (In reply to Michail Vourlakos from comment #3) > I tested your layout, after 2VDs for every VD I add the items size is > decreased. > When I remove one VD then it does not restore but if I remove two VDs it > does. > > Is this your system behavior? Kind of. But if I change the configuration of the pager to have only one row (right-click -> Configure Desktops -> Number of rows: 1), then it doesn’t restore the size anymore, even after leaving only one virtual desktop. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 411890] Expose theme-specific user-visible settings in the KCM
https://bugs.kde.org/show_bug.cgi?id=411890 Nate Graham changed: What|Removed |Added Ever confirmed|0 |1 Assignee|plasma-b...@kde.org |k...@davidedmundson.co.uk CC||filipfila@gmail.com, ||n...@kde.org Summary|Add Breeze SDDM login |Expose theme-specific |screen blur and font color |user-visible settings in |settings|the KCM Status|REPORTED|CONFIRMED Component|general |kcm_sddm Product|Breeze |systemsettings --- Comment #1 from Nate Graham --- Your current user's color scheme and font preferences can be synced to the SDDM login screen in the upcoming Plasma 5.17, which should take care of part of this request. As for the blur, that's tricky. The first problem is that the SDDM KCM doesn't expose any theme-specific options, so there's no way for the default Breeze SDDM theme to offer a way to turn off the blur. Even if we could, that would offer the possibility of making the buttons and their text unreadable with the current design. You might ask, then, "well, why don't you just change the design, duh?" This is easier said then done! :) The current design is the result of a lot of refinement and discussion. In the Plasma 5.16 timeframe we had multiple discussions regarding alternative designs that would not require a blurred background. The problem is that we allow users to set arbitrary wallpapers here, so we need some way to make sure that the things on top of the wallpaper remain visible, no matter what it is. There are only a few options: 1. Blur and darken the wallpaper 2. Put outlines or shadows behind everything 2. Put everything inside/on top of a frame or window that's above the wallpaper #1 Is the status quo. #2 Is what we do this for Desktop icons, but we could not find a way to make this work serviceably for the lock screen's use case. The possibilities for the wallpaper were too broad for us to be comfortable implementing it. #3 is a complete redesign. Personally I was pushing for #3, but like so many things in life (and especially with a large and complex project that involves other people), sometimes you don't get exactly what you want and that's what happened here. So we stuck with #1 but reduced the darkness and blurriness of the blur. This reduced the number of complaints, but I had a feeling that some people would still not be satisfied. Given that there is no remaining interest or energy in touching the login screen for quite some time (the discussions were exhausting), the only path forward I see here is making the blur completely disable-able, which would require changes in both the theme and the SDDM KCM to display per-theme user-visible options. Moving there for now. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 411841] Partition Manager doesn't actually edit fstab
https://bugs.kde.org/show_bug.cgi?id=411841 Andrius Štikonas changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 411891] Digikam crashes on startup
https://bugs.kde.org/show_bug.cgi?id=411891 --- Comment #3 from Jens Ramke --- (In reply to Maik Qualmann from comment #1) > It crashes in QWebEngine. Your digiKam version is compiled with QWebEngine > support instead of QWebKit. We currently recommend QWebKit. For QWebEngine > you need a working and stable support of OpenGL. I also use QWebEngine in my > developer version. Which graphics card and drivers do you use? > > Maik GPU: NVIDIA GeForce RTX 2080 GPU driver: nvidia-dkms 435.21-4 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 411891] Digikam crashes on startup
https://bugs.kde.org/show_bug.cgi?id=411891 --- Comment #4 from Jens Ramke --- (In reply to caulier.gilles from comment #2) > Note : the AppImage bundle is compiled with QtWebEngine. Can you reproduce > this problem ? Cannot reproduce with AppImage bundle. It starts normally. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 331539] All messages disappear after deleting one
https://bugs.kde.org/show_bug.cgi?id=331539 Marc Mezzarobba changed: What|Removed |Added CC||marc+b...@mezzarobba.net -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 318049] Message list gets blank after deleting message
https://bugs.kde.org/show_bug.cgi?id=318049 Marc Mezzarobba changed: What|Removed |Added CC||marc+b...@mezzarobba.net -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 411891] Digikam crashes on startup
https://bugs.kde.org/show_bug.cgi?id=411891 --- Comment #5 from Maik Qualmann --- Gilles has mean that AppImage is compiled with QWebKit. Gilles, how was that with you again with NVidia. The Nouveau is clear that does not work with QWebEngine. How was that with the proprietary NVidia driver? Did you have problems there as well? Maik -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 411890] Expose theme-specific user-visible settings in the KCM
https://bugs.kde.org/show_bug.cgi?id=411890 Mihai Sorin Dobrescu changed: What|Removed |Added CC||msdobre...@gmail.com --- Comment #2 from Mihai Sorin Dobrescu --- Thank you for the thorough answer and for your time! A last word before moving to another login theme. I've read the discussions myself and I have come to the same conclusion. The large range of ideas and opinions have led me to the request, the settings made available would be solution because they would let people tune it according to the chosen image. I know it's possible. The only thing it keep me from implementing it is the lack of knowledge in QT, as you already know. Importing the theme is something I am sure will make more trouble. BTW, whose theme? There is no current user at the login time... But I'm sure I am missing something... -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 411891] Digikam crashes on startup
https://bugs.kde.org/show_bug.cgi?id=411891 --- Comment #6 from Maik Qualmann --- @Jens Did you install Marble? Is there a problem starting Marble when using OpenStreetMap? Maik -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 411788] Indicate limited connectivity in tooltip
https://bugs.kde.org/show_bug.cgi?id=411788 Jan Grulich changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://commits.kde.org/pla ||sma-nm/695846c500d89824df0e ||5059b749b960096e4a12 Status|REPORTED|RESOLVED --- Comment #1 from Jan Grulich --- Git commit 695846c500d89824df0e5059b749b960096e4a12 by Jan Grulich. Committed on 13/09/2019 at 18:36. Pushed by grulich into branch 'master'. Show connectivity status in tooltip Summary: BUG: 411788 Reviewers: broulik Reviewed By: broulik Subscribers: plasma-devel Tags: #plasma Differential Revision: https://phabricator.kde.org/D23852 M +15 -1libs/declarative/networkstatus.cpp https://commits.kde.org/plasma-nm/695846c500d89824df0e5059b749b960096e4a12 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 411875] Undo Image->trim to selection shifts selection by constant amount
https://bugs.kde.org/show_bug.cgi?id=411875 --- Comment #9 from Ahab Greybeard --- With the 4.2.6 appimage on Linux, I don't have that offeset after Undo. I do see the transient selection offset as Trim is being performed (especially now I'm replicating your image and using a small selection). The transient offset appears to be equal to the initial selection offset from the top left corner, as you noted. Even with a large selection, I don't see any transient shift in the image layer itself. I've tried it with Image Preview on/off and Graphics Acceleration on/off and that made no difference. Does that make any difference for you? My PC is not particularly powerful (2x Xeon E5450 @3GHz): Hardware Information GPU Acceleration: auto Memory: 16039 Mb Number of Cores: 8 Swap Location: /tmp OpenGL Info Vendor: "NVIDIA Corporation" Renderer: "GeForce GTX 750 Ti/PCIe/SSE2" Version: "4.6.0 NVIDIA 418.74" Shading language: "4.60 NVIDIA" Requested format: QSurfaceFormat(version 3.0, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::CompatibilityProfile) Current format:QSurfaceFormat(version 4.6, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::CompatibilityProfile) Version: 4.6 Supports deprecated functions true is OpenGL ES: false I can't think of anything else to try. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 411860] Latte panel size doesn't recover after being auto-shrunk
https://bugs.kde.org/show_bug.cgi?id=411860 Michail Vourlakos changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED Version Fixed In||0.9.3 Latest Commit||https://commits.kde.org/lat ||te-dock/182831a808497dda434 ||3f5cc23a13a4ac5a1a01b --- Comment #5 from Michail Vourlakos --- Git commit 182831a808497dda4343f5cc23a13a4ac5a1a01b by Michail Vourlakos. Committed on 13/09/2019 at 18:38. Pushed by mvourlakos into branch 'v0.9'. improvements for automatic icon size code path --this patch add two fixes concerning automatic icon size when contents exceed the view maximum length. --A) when the function is called then it also called one more time after 1sec to confirm that the icon size found is valid. In the past that approach was creating an endless loop that should not be triggered any more --B) the grow limit was made to be equal with the shrink limit trying to be more predictive from the user when the items will grow or shrink. In the future we must take care of this if the items grow or shrink endlessly FIXED-IN:0.9.3 M +27 -12 containment/package/contents/ui/main.qml https://commits.kde.org/latte-dock/182831a808497dda4343f5cc23a13a4ac5a1a01b -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 411860] Latte panel size doesn't recover after being auto-shrunk
https://bugs.kde.org/show_bug.cgi?id=411860 Michail Vourlakos changed: What|Removed |Added Latest Commit|https://commits.kde.org/lat |https://commits.kde.org/lat |te-dock/182831a808497dda434 |te-dock/b9d82fe0f1e7a390410 |3f5cc23a13a4ac5a1a01b |d04543c2bae489f11e42c --- Comment #6 from Michail Vourlakos --- Git commit b9d82fe0f1e7a390410d04543c2bae489f11e42c by Michail Vourlakos. Committed on 13/09/2019 at 18:43. Pushed by mvourlakos into branch 'master'. improvements for automatic icon size code path --this patch add two fixes concerning automatic icon size when contents exceed the view maximum length. --A) when the function is called then it also called one more time after 1sec to confirm that the icon size found is valid. In the past that approach was creating an endless loop that should not be triggered any more --B) the grow limit was made to be equal with the shrink limit trying to be more predictive from the user when the items will grow or shrink. In the future we must take care of this if the items grow or shrink endlessly FIXED-IN:0.9.3 M +27 -12 containment/package/contents/ui/main.qml https://commits.kde.org/latte-dock/b9d82fe0f1e7a390410d04543c2bae489f11e42c -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 411891] Digikam crashes on startup
https://bugs.kde.org/show_bug.cgi?id=411891 --- Comment #7 from caulier.gil...@gmail.com --- Same problem here using Mageia 7 and last main update. When i use QtWebEngine, it crash but not at startup, and end of digiKam session. It's reproducible with 2 computers using different Nvidia card but with proprietary driver. Gilles -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 411860] Latte panel size doesn't recover after being auto-shrunk
https://bugs.kde.org/show_bug.cgi?id=411860 --- Comment #7 from Michail Vourlakos --- (In reply to David from comment #4) > (In reply to Michail Vourlakos from comment #3) > > I tested your layout, after 2VDs for every VD I add the items size is > > decreased. > > When I remove one VD then it does not restore but if I remove two VDs it > > does. > > > > Is this your system behavior? > > Kind of. But if I change the configuration of the pager to have only one row > (right-click -> Configure Desktops -> Number of rows: 1), then it doesn’t > restore the size anymore, even after leaving only one virtual desktop. I tried to improve things, you can test them out from v0.9 branch or master or wait for 0.9.3 to be released -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 411877] Touchscreen input locked to first screen
https://bugs.kde.org/show_bug.cgi?id=411877 --- Comment #2 from lo...@kde.bt.alestan.publicvm.com --- (In reply to Vlad Zahorodnii from comment #1) > Are you on X11 or Wayland? Wayland. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 411891] Digikam crashes on startup
https://bugs.kde.org/show_bug.cgi?id=411891 --- Comment #8 from Jens Ramke --- (In reply to Maik Qualmann from comment #6) > Did you install Marble? Is there a problem starting Marble when using > OpenStreetMap? Marble works fine with all installed maps. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 411891] Digikam crashes on startup
https://bugs.kde.org/show_bug.cgi?id=411891 --- Comment #9 from Maik Qualmann --- @Jens Try it if you delete the folder "~/.local/share/digikam/QtWebEngine" beforehand. Maik -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 411860] Latte panel size doesn't recover after being auto-shrunk
https://bugs.kde.org/show_bug.cgi?id=411860 --- Comment #8 from David --- (In reply to Michail Vourlakos from comment #7) > (In reply to David from comment #4) > > (In reply to Michail Vourlakos from comment #3) > > > I tested your layout, after 2VDs for every VD I add the items size is > > > decreased. > > > When I remove one VD then it does not restore but if I remove two VDs it > > > does. > > > > > > Is this your system behavior? > > > > Kind of. But if I change the configuration of the pager to have only one row > > (right-click -> Configure Desktops -> Number of rows: 1), then it doesn’t > > restore the size anymore, even after leaving only one virtual desktop. > > I tried to improve things, you can test them out from v0.9 branch or master > or wait for 0.9.3 to be released Great, thank you! Will test it in the next release. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 411893] New: constantly 1-2% in multiple layouts mode
https://bugs.kde.org/show_bug.cgi?id=411893 Bug ID: 411893 Summary: constantly 1-2% in multiple layouts mode Product: lattedock Version: git (master) Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: mvourla...@gmail.com Target Milestone: --- SUMMARY in my multiple layouts system when I activate two different sub-layouts e.g. "Unity Dream" or "Plasma Original" I notice a constant 1%-2% cpu usage that must be tracked down and be identified -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 411894] New: Converting text to path after moving with move tool ignores transformations
https://bugs.kde.org/show_bug.cgi?id=411894 Bug ID: 411894 Summary: Converting text to path after moving with move tool ignores transformations Product: krita Version: 4.2.6 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Layers/Vector Assignee: krita-bugs-n...@kde.org Reporter: jamesnoec...@gmail.com Target Milestone: --- SUMMARY The "convert to path" button ignores transformations applied to the vector layer using the move tool. STEPS TO REPRODUCE 1. Create text 2. Using move tool, move the text in some way 3. Select edit shapes tool, and press convert to path OBSERVED RESULT Shape is where the text was before transforming the vector layer EXPECTED RESULT Shape should be in the same location as the text SOFTWARE/OS VERSIONS Linux: kubuntu -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 411895] New: Transform tool vanishes text and leads to unstable text behavior
https://bugs.kde.org/show_bug.cgi?id=411895 Bug ID: 411895 Summary: Transform tool vanishes text and leads to unstable text behavior Product: krita Version: 4.2.6 Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Layers/Vector Assignee: krita-bugs-n...@kde.org Reporter: jamesnoec...@gmail.com Target Milestone: --- SUMMARY Attempting to use the transform tool to scale, move or rotate text causes unstable behavior. Even selecting the transform tool momentarily and switching back to the select shapes tool is enough to cause text to stop rendering. STEPS TO REPRODUCE 1. Create text 2. Select transform tool 3. Pick perspective transform or warp modes 4. Deform the text in some way OBSERVED RESULT Text vanishes from canvas EXPECTED RESULT Text should be transformed properly, or it should be made clear that those tools cannot be applied to text. Another thing to try: 1. Create text 2. Using transform tool, apply a translation to the text 3. Convert text to path using the edit shapes tool OBSERVED RESULT Text vanishes EXPECTED RESULT Text should be converted to a path in place And another: 1. Create text 2. Select Transform tool 3. Select Select Shapes tool OBSERVED RESULT Text vanishes until you hide and unhide the vector layer SOFTWARE/OS VERSIONS Linux: kubuntu ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 411894] Converting text to path after moving with move tool ignores transformations
https://bugs.kde.org/show_bug.cgi?id=411894 jamesnoec...@gmail.com changed: What|Removed |Added Platform|Kubuntu Packages|Appimage -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 411891] Digikam crashes on startup
https://bugs.kde.org/show_bug.cgi?id=411891 --- Comment #10 from Jens Ramke --- (In reply to Maik Qualmann from comment #9) > Try it if you delete the folder "~/.local/share/digikam/QtWebEngine" > beforehand. Still crashes. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 411894] Converting text to path after moving with move tool ignores transformations
https://bugs.kde.org/show_bug.cgi?id=411894 --- Comment #1 from jamesnoec...@gmail.com --- Happens on Windows as well -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 411895] Transform tool vanishes text and leads to unstable text behavior
https://bugs.kde.org/show_bug.cgi?id=411895 --- Comment #1 from jamesnoec...@gmail.com --- Also observed on Windows -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 411864] Onlinebanking with aqbanking needs rework for psd2
https://bugs.kde.org/show_bug.cgi?id=411864 hiwatari.se...@gmail.com changed: What|Removed |Added CC||hiwatari.se...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 411896] New: Reort improvement
https://bugs.kde.org/show_bug.cgi?id=411896 Bug ID: 411896 Summary: Reort improvement Product: kmymoney Version: 5.0.5 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: reports Assignee: kmymoney-de...@kde.org Reporter: hans-pe...@petzoldt.biz Target Milestone: --- SUMMARY I'm using Kmymoney about several years and would compare the figures in a yearly chart. Do I have a chance to achieve this with the standard report setting or can i amend the report part to set up some charts ? Thanks for a hint. Rgards Peter -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 405847] SFTP transfer corrupts all files
https://bugs.kde.org/show_bug.cgi?id=405847 Florian changed: What|Removed |Added CC||kde-b...@pyoworks.com -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 411674] When repeat is on, playlist does not repeat after reaching the end if a track was removed from the playlist
https://bugs.kde.org/show_bug.cgi?id=411674 --- Comment #5 from Alexander Stippich --- The bug is in ManageAudioPlayer only setting the new source if it differs from the previous one. However, since I am not really familiar with that part of the code, I will leave this to Matthieu :) -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 411888] Elisa does not compile against Qt 5.14
https://bugs.kde.org/show_bug.cgi?id=411888 Alexander Stippich changed: What|Removed |Added CC||a.stipp...@gmx.net --- Comment #1 from Alexander Stippich --- I don't have Qt 5.14 currently installed, but I pushed a possible fix. Could you please retry? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 411875] Undo Image->trim to selection shifts selection by constant amount
https://bugs.kde.org/show_bug.cgi?id=411875 --- Comment #10 from jamesnoec...@gmail.com --- I'm starting with the 1024x1024 texture preset. Though that wasn't the only one that caused the bug, that's the one I'm on now, if it helps. I've done nothing aside from start the program and create a new canvas before crop and undo. Large selections are affected too, and shift out of bounds. Happens to me both in Linux and Windows, but on the Linux workstation, specs are: Ubuntu 18.04 Graphics: Quadro RTX 8000 Memory: 50GB Krita renderer: OpenGL Scaling mode: High quality filtering What you posted looks like a debug dump from krita but I'm unfamiliar with that feature, so hopefully that's good enough. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 411875] Undo Image->trim to selection shifts selection by constant amount
https://bugs.kde.org/show_bug.cgi?id=411875 --- Comment #11 from jamesnoec...@gmail.com --- Hardware Information GPU Acceleration: auto Memory: 48201 Mb Number of Cores: 40 Swap Location: /tmp OpenGL Info Vendor: "NVIDIA Corporation" Renderer: "Quadro RTX 8000/PCIe/SSE2" Version: "4.6.0 NVIDIA 435.12" Shading language: "4.60 NVIDIA" Requested format: QSurfaceFormat(version 3.0, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::CompatibilityProfile) Current format:QSurfaceFormat(version 4.6, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::CompatibilityProfile) Version: 4.6 Supports deprecated functions true is OpenGL ES: false QPA OpenGL Detection Info supportsDesktopGL: true supportsOpenGLES: true isQtPreferOpenGLES: false == log == Supported renderers: QFlags(0x2|0x4) Surface format preference list: * QSurfaceFormat(version 3.0, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::CompatibilityProfile) 2 * QSurfaceFormat(version 3.0, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::CompatibilityProfile) 4 Probing format... QSurfaceFormat::DefaultColorSpace 2 Found format: QSurfaceFormat(version 3.0, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::CompatibilityProfile) 2 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 398384] Recording activities doing in editor and applying them on text
https://bugs.kde.org/show_bug.cgi?id=398384 Piotr Mierzwinski changed: What|Removed |Added Version|5.55.0 |5.61.0 -- You are receiving this mail because: You are watching all bug changes.
[karbon] [Bug 313913] Calligraphy tol: line editing bug
https://bugs.kde.org/show_bug.cgi?id=313913 jamesnoec...@gmail.com changed: What|Removed |Added CC||jamesnoec...@gmail.com --- Comment #2 from jamesnoec...@gmail.com --- I can confirm this bug as of version 4.2.6. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 411897] New: improvement suggestion
https://bugs.kde.org/show_bug.cgi?id=411897 Bug ID: 411897 Summary: improvement suggestion Product: systemsettings Version: 5.16.5 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: kcm_mouse Assignee: unassigned-b...@kde.org Reporter: leonei...@gmail.com CC: unassigned-b...@kde.org Target Milestone: --- SUMMARY It would be great if in Screen edge configuration have an option to change volume with mouse wheel. To use something like this, we have to put one bar in some edge and put the volume widget in the edge. It works, but is not the best way. Thanks 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.
[systemsettings] [Bug 411898] New: Mouse wheel speed
https://bugs.kde.org/show_bug.cgi?id=411898 Bug ID: 411898 Summary: Mouse wheel speed Product: systemsettings Version: 5.16.5 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: leonei...@gmail.com Target Milestone: --- SUMMARY I see a lot of people asking for how to change mouse wheel speed. It would be great this feature in Plasma KDE. My suggestion is also having an option to while holding CTRL change the mouse wheel speed. THANKS 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 411899] New: Editing calligraphy strokes with edit paths tool causes entire stroke to fly away
https://bugs.kde.org/show_bug.cgi?id=411899 Bug ID: 411899 Summary: Editing calligraphy strokes with edit paths tool causes entire stroke to fly away Product: krita Version: 4.2.6 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Tools/Vector Assignee: krita-bugs-n...@kde.org Reporter: jamesnoec...@gmail.com Target Milestone: --- SUMMARY Editing strokes made with the calligraphy tool causes all the points to fly off the screen if you move up or left beyond the bounding box of the stroke. STEPS TO REPRODUCE 1. Make a calligraphy stroke 2. Drag any point on the stroke up or left with the edit paths tool 3. drag until you exit the bounding box of all the points on the stroke OBSERVED RESULT All the rest of the points fly wildly in the opposite direction to where you're dragging. EXPECTED RESULT Only the point you're editing should move. SOFTWARE/OS VERSIONS Both windows and Linux appimage NOTES: This was once reported and resolved (Bug 335659) in 2014 as a duplicate of Bug 313913 from 2013, despite that bug being for an unmaintained piece of software called Karbon. All i can gather from this is that Krita somehow was built on top of Karbon and that its bugs are inherited, but I have my doubts that the bug report is visible due to being in the wrong software category, so I'm making a new report in 2019 for Krita 4.2.6. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 411898] Mouse wheel speed
https://bugs.kde.org/show_bug.cgi?id=411898 David Edmundson changed: What|Removed |Added Status|REPORTED|NEEDSINFO CC||k...@davidedmundson.co.uk Resolution|--- |WAITINGFORINFO --- Comment #1 from David Edmundson --- Do you mean number of lines scrolled or adjust actual angleDelta? -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 359627] choose order in which krunner displays results of different kinds
https://bugs.kde.org/show_bug.cgi?id=359627 Nate Graham changed: What|Removed |Added Summary|choose order in which |choose order in which |krunner displays results of |krunner displays results of |different kinds or have it |different kinds |learn user preference | -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 411900] New: Tracking activity
https://bugs.kde.org/show_bug.cgi?id=411900 Bug ID: 411900 Summary: Tracking activity Product: systemsettings Version: 5.16.5 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: leonei...@gmail.com Target Milestone: --- SUMMARY I would like to suggest a simple but useful feature. An option to track activities time. Just a simple log where we can see time spent on each activity. When changing between activities, the timer logs it. And of course a report. Thanks 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.
[dolphin] [Bug 405114] [Wayland] Video preview plays in a separate window
https://bugs.kde.org/show_bug.cgi?id=405114 Patrick Silva changed: What|Removed |Added CC||elvis.angelac...@kde.org --- Comment #3 from Patrick Silva --- *** Bug 411889 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Phonon] [Bug 411889] Phonon::VideoWidget opens its own VLC window when using the VLC backend on Wayland
https://bugs.kde.org/show_bug.cgi?id=411889 Patrick Silva changed: What|Removed |Added Status|REPORTED|RESOLVED CC||bugsefor...@gmx.com Resolution|--- |DUPLICATE --- Comment #1 from Patrick Silva --- *** This bug has been marked as a duplicate of bug 405114 *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 410158] Severe lag in 4.3.0 pre-alpha Brush Editor when adjusting transfer curves
https://bugs.kde.org/show_bug.cgi?id=410158 --- Comment #10 from Tymond --- Git commit 542da22bbbdcdb68e015bdb3b47e3f46c83c6214 by Agata Cacko. Committed on 13/09/2019 at 23:23. Pushed by tymond into branch 'master'. Fix curve changing with sensors w/ Use Same Curve Before this commit, curve would change semi-randomly in some cases if you change from some specific sensors to some other specific sensors (having a complex curve and clicking randomly should show a bug though) when "Share curve across all settings" is selected. This commit fixes that behaviour. Related: bug 383909 M +3-3libs/global/kis_signal_compressor.h M +18 -1libs/ui/widgets/kis_curve_widget.cpp M +17 -0libs/ui/widgets/kis_curve_widget.h M +6-2libs/ui/widgets/kis_curve_widget_p.h M +4-0plugins/paintops/libpaintop/kis_auto_brush_widget.cpp M +27 -22 plugins/paintops/libpaintop/kis_curve_option.cpp M +6-2plugins/paintops/libpaintop/kis_curve_option.h M +35 -15 plugins/paintops/libpaintop/kis_curve_option_widget.cpp M +5-2plugins/paintops/libpaintop/kis_curve_option_widget.h https://invent.kde.org/kde/krita/commit/542da22bbbdcdb68e015bdb3b47e3f46c83c6214 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 383909] Checkbox «Share curve across all settings» doesn’t save the curve if it’s not changed
https://bugs.kde.org/show_bug.cgi?id=383909 Tymond changed: What|Removed |Added Resolution|--- |FIXED Latest Commit|https://invent.kde.org/kde/ |https://invent.kde.org/kde/ |krita/commit/b915ac470f148a |krita/commit/542da22bbbdcdb |3f4787b1689865a0c4d434ca72 |68e015bdb3b47e3f46c83c6214 Status|REOPENED|RESOLVED --- Comment #7 from Tymond --- Git commit 542da22bbbdcdb68e015bdb3b47e3f46c83c6214 by Agata Cacko. Committed on 13/09/2019 at 23:23. Pushed by tymond into branch 'master'. Fix curve changing with sensors w/ Use Same Curve Before this commit, curve would change semi-randomly in some cases if you change from some specific sensors to some other specific sensors (having a complex curve and clicking randomly should show a bug though) when "Share curve across all settings" is selected. This commit fixes that behaviour. Related: bug 410158 M +3-3libs/global/kis_signal_compressor.h M +18 -1libs/ui/widgets/kis_curve_widget.cpp M +17 -0libs/ui/widgets/kis_curve_widget.h M +6-2libs/ui/widgets/kis_curve_widget_p.h M +4-0plugins/paintops/libpaintop/kis_auto_brush_widget.cpp M +27 -22 plugins/paintops/libpaintop/kis_curve_option.cpp M +6-2plugins/paintops/libpaintop/kis_curve_option.h M +35 -15 plugins/paintops/libpaintop/kis_curve_option_widget.cpp M +5-2plugins/paintops/libpaintop/kis_curve_option_widget.h https://invent.kde.org/kde/krita/commit/542da22bbbdcdb68e015bdb3b47e3f46c83c6214 -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 411901] New: No text entry in text fields
https://bugs.kde.org/show_bug.cgi?id=411901 Bug ID: 411901 Summary: No text entry in text fields Product: Falkon Version: 3.1.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: now...@gmail.com Reporter: dtomba...@gmail.com Target Milestone: --- SUMMARY webpages do not set focus for text fields unless the window has lost focus and regains it. STEPS TO REPRODUCE 1. open falkon 2. go to google.com (or any webpage with text field) 3. try typing OBSERVED RESULT Text is not entered in field EXPECTED RESULT text should be entered as you type SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: openSuse (available in About System) KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.61.0 Qt Version: 5.13.1 ADDITIONAL INFORMATION I have tried both 3.0.1 and 3.1.0 and the behavior is the same. I have removed all of the folders i could find for falkon and reinstalled, same issue. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 411802] Local selection outline is rendered wrong in some cases
https://bugs.kde.org/show_bug.cgi?id=411802 vanyossi changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #3 from vanyossi --- Setting this as confirmed, tested in 4.2.6. Selection outlineis not moved to updated position. Once in this state, outline is locked and updates only after a new selection is made. Local selection and outline move appears to be broken in general. 1. Make selection as local selection 2. Hover selection to make move seelction cursor appear 3. click and drag to move selection. Selection outline will not update but selecting local selection layer shows seletion did move after drag action. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 411901] No text entry in text fields
https://bugs.kde.org/show_bug.cgi?id=411901 --- Comment #1 from Dirk Tombaugh --- (In reply to Dirk Tombaugh from comment #0) > SUMMARY > webpages do not set focus for text fields unless the window has lost focus > and regains it. > > STEPS TO REPRODUCE > 1. open falkon > 2. go to google.com (or any webpage with text field) > 3. try typing > > OBSERVED RESULT > Text is not entered in field > > EXPECTED RESULT > text should be entered as you type > > SOFTWARE/OS VERSIONS > Windows: > macOS: > Linux/KDE Plasma: openSuse > (available in About System) > KDE Plasma Version: 5.16.5 > KDE Frameworks Version: 5.61.0 > Qt Version: 5.13.1 > > ADDITIONAL INFORMATION > I have tried both 3.0.1 and 3.1.0 and the behavior is the same. I have > removed all of the folders i could find for falkon and reinstalled, same > issue. I'm getting the same thing with Konqueror. So I don't know what actual piece is causing the issues. -- You are receiving this mail because: You are watching all bug changes.
[karbon] [Bug 313913] Calligraphy tol: line editing bug
https://bugs.kde.org/show_bug.cgi?id=313913 --- Comment #3 from jamesnoec...@gmail.com --- of Krita, that is, given that Krita Bug 335659 was marked as a duplicate of this. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 411895] Transform tool vanishes text and leads to unstable text behavior
https://bugs.kde.org/show_bug.cgi?id=411895 --- Comment #2 from jamesnoec...@gmail.com --- it seems that the perspective or warp transformation causes any vector layer to vanish, not just text. The vanishing bug when switching tools also happens with vector layers in general. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 411902] New: Interface icons become very large and unusable
https://bugs.kde.org/show_bug.cgi?id=411902 Bug ID: 411902 Summary: Interface icons become very large and unusable Product: digikam Version: 6.3.0 Platform: macOS Disk Images OS: macOS Status: REPORTED Severity: major Priority: NOR Component: general Assignee: digikam-bugs-n...@kde.org Reporter: gski...@gmail.com Target Milestone: --- The interface icons become very large and only the upper left corner of the screen is visible after entering the Image Editor. It also happens occasionally with other clicks, but I can trigger it by going into image editor. STEPS TO REPRODUCE 1. Select an image 2. click the Image Editor button 3. OBSERVED RESULT The image editor opens, but is unusable because it is magnified and only the top left corner of the screen is visible. Also happens with Light Table. EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: 10.14.6 Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 411890] Expose theme-specific user-visible settings in the KCM
https://bugs.kde.org/show_bug.cgi?id=411890 --- Comment #3 from Nate Graham --- The feature in Plasma 5.17 allows a user with admin rights to sync their user settings to SDDM. It's not automatic, it's manual. In the future we hope to optionally make it automatic for the common case of a single-user system where the user has admin rights. -- You are receiving this mail because: You are watching all bug changes.
[tellico] [Bug 411903] New: Add loan info to Entry View
https://bugs.kde.org/show_bug.cgi?id=411903 Bug ID: 411903 Summary: Add loan info to Entry View Product: tellico Version: 3.2 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: ro...@periapsis.org Reporter: ro...@periapsis.org Target Milestone: --- When a book is marked as "loaned", there is no way to see who it was loaned to when looking at the book info. The only way to have this information to is by watching in the left "Loan" column and try all names. Would it be possible to add the possibility to access this information easily ? -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 411904] New: Deleted email remain / greyed out iCloud IMAP
https://bugs.kde.org/show_bug.cgi?id=411904 Bug ID: 411904 Summary: Deleted email remain / greyed out iCloud IMAP Product: kontact Version: 5.12.1 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: mail Assignee: kdepim-b...@kde.org Reporter: dan.jenkins...@gmail.com Target Milestone: --- SUMMARY I have 3 active email account 2 iCloud and one Gmail account. The Gmail account functions without issue. Both iCloud accounts send / receive with no issue and the deleted messages properly route to the assigned Trash folder for each account (not the local folder). Upon deleting a message the message moves to trash as expected, but leaves a greyed out message in the inbox. STEPS TO REPRODUCE 1. Delete email (also tried deleting message thread and move all messages to Trash same result). 2. Check Trash - it's there, back to inbox it's there too but greyed out. OBSERVED RESULT Duplicate email in the inbox when the mail is moved to trash. EXPECTED RESULT Email should be moved to trash without being left in the inbox. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Kernel 5.2.11-1-default (available in About System) KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.61.0 Qt Version: 5.13.1 ADDITIONAL INFORMATION I've removed all identities and re-added issue presisted. Deleted kMail all dependencies and re-installed / re-added the accounts- issue presists. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 411905] New: New version in Flathub
https://bugs.kde.org/show_bug.cgi?id=411905 Bug ID: 411905 Summary: New version in Flathub Product: kdenlive Version: 19.08.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Translation Assignee: vpi...@kde.org Reporter: agvozdez...@yandex.ru Target Milestone: --- I can't see new version (19.08.1) on Flathub -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 411906] New: Panel widgets and menus are too high when panel on auto-hide
https://bugs.kde.org/show_bug.cgi?id=411906 Bug ID: 411906 Summary: Panel widgets and menus are too high when panel on auto-hide Product: kwin Version: 5.16.5 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: 116ni...@gmail.com Target Milestone: --- SUMMARY Panel widgets and menus like the system tray popups and application menu draw too high on the screen when the panel is on auto-hide. STEPS TO REPRODUCE 1. put panel on autohide 2. reboot computer 3. OBSERVED RESULT see screenshots EXPECTED RESULT normal men ADDITIONAL INFORMATION The problem seems to go away after setting the panel to Always Visible and then back again to Auto Hide. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 411906] Panel widgets and menus are too high when panel on auto-hide
https://bugs.kde.org/show_bug.cgi?id=411906 --- Comment #1 from Nicholas Estrada <116ni...@gmail.com> --- Created attachment 122647 --> https://bugs.kde.org/attachment.cgi?id=122647&action=edit See the problem -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 411906] Panel widgets and menus are too high when panel on auto-hide
https://bugs.kde.org/show_bug.cgi?id=411906 --- Comment #2 from Nicholas Estrada <116ni...@gmail.com> --- Created attachment 122648 --> https://bugs.kde.org/attachment.cgi?id=122648&action=edit See the problem 2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 411906] Panel widgets and menus are too high when panel on auto-hide
https://bugs.kde.org/show_bug.cgi?id=411906 --- Comment #3 from Nicholas Estrada <116ni...@gmail.com> --- *normal menus -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 411805] Issue with texture pattern in brush engine
https://bugs.kde.org/show_bug.cgi?id=411805 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #12 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.
[krita] [Bug 411875] Undo Image->trim to selection shifts selection by constant amount
https://bugs.kde.org/show_bug.cgi?id=411875 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #12 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.
[krita] [Bug 410911] Dialog displays file name to first "." only
https://bugs.kde.org/show_bug.cgi?id=410911 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- 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.
[krita] [Bug 410947] multiply layer disfunction
https://bugs.kde.org/show_bug.cgi?id=410947 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- 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.
[kmymoney] [Bug 410910] Income Expenses report per year when switched to Investments & liability shows wrong credit card expenses
https://bugs.kde.org/show_bug.cgi?id=410910 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- 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 410930] [Enlightenment] Support XembedSNIProxy for other DE / WM
https://bugs.kde.org/show_bug.cgi?id=410930 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #5 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 411432] Every time I try adding and editing text, the whole program freezes and crashes.
https://bugs.kde.org/show_bug.cgi?id=411432 --- 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.
[krename] [Bug 402678] crash opening more than one folder
https://bugs.kde.org/show_bug.cgi?id=402678 --- 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.
[kdenlive] [Bug 410798] Audio and Video are out of sync
https://bugs.kde.org/show_bug.cgi?id=410798 --- Comment #1 from Colin Brash --- Wanted to add an update to my first bug report, I'm incorrect in saying that the audio and video sync are out, It's actually the audio and waveform that are out of sync. My apologies for this misinterpreted information, I feel like I may have wasted somebody's valuable time. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 411902] Interface icons become very large and unusable
https://bugs.kde.org/show_bug.cgi?id=411902 caulier.gil...@gmail.com changed: What|Removed |Added Component|general |Usability-Themes CC||caulier.gil...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 411902] Interface icons become very large and unusable
https://bugs.kde.org/show_bug.cgi?id=411902 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #1 from Maik Qualmann --- Can you take a screenshot or maybe even a screencast? At the moment I have no idea what the cause of the problem is. Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 411902] Interface icons become very large and unusable
https://bugs.kde.org/show_bug.cgi?id=411902 --- Comment #2 from caulier.gil...@gmail.com --- Also give us which icon theme you use from setup dialog, and which color theme is selected from main menu. Note that i just ported all DK 6.4.0 bundles to KF5 framework 5.61 which include breeze theme. Perhaps this update will fix your problem. This will be available in next PKG 6.4.0 pre-release. Compiling is under way and file will be ready to download in one hour at usual place : https://files.kde.org/digikam/ Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 411891] Digikam crashes on startup
https://bugs.kde.org/show_bug.cgi?id=411891 Maik Qualmann changed: What|Removed |Added CC||iwannaber...@gmail.com --- Comment #11 from Maik Qualmann --- *** Bug 406809 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 409906] Crash at Startup
https://bugs.kde.org/show_bug.cgi?id=409906 Maik Qualmann changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #4 from Maik Qualmann --- *** This bug has been marked as a duplicate of bug 411891 *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 406809] digikam-6.2.0-git-20190421T121202-qtwebengine-x86-64.appimage crashes on startup.
https://bugs.kde.org/show_bug.cgi?id=406809 Maik Qualmann changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #12 from Maik Qualmann --- *** This bug has been marked as a duplicate of bug 411891 *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 411891] Digikam crashes on startup
https://bugs.kde.org/show_bug.cgi?id=411891 Maik Qualmann changed: What|Removed |Added CC||pauli.h...@yahoo.com --- Comment #12 from Maik Qualmann --- *** Bug 409906 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 411902] Interface icons become very large and unusable
https://bugs.kde.org/show_bug.cgi?id=411902 --- Comment #3 from caulier.gil...@gmail.com --- Maik, just for info, the Qt version used to compule digiKam under MacOS is an old one, not the 5.12.5 LTS (Appimage) or 5.13.1 (MXE): https://invent.kde.org/kde/digikam/blob/master/project/bundles/macports/01-build-macports.sh#L251 It's possible to use a more recent version of Qt as Macports provide 5.12.x for ex, but this will reduce again the compatibility at run-time with older MacOS version. It's explained in Qt platform page that MacOS API are used in some parts and compatibility is not well supported with older version. It's a know problem, so i would to progress slowly with Qt version here. Gilles -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 411891] DigiKam crashes if compiled with QWebEngine
https://bugs.kde.org/show_bug.cgi?id=411891 Maik Qualmann changed: What|Removed |Added Summary|Digikam crashes on startup |DigiKam crashes if compiled ||with QWebEngine -- You are receiving this mail because: You are watching all bug changes.
