[digikam] [Bug 413905] Some icon / picture are not displayed in maps but picture have GPS data
https://bugs.kde.org/show_bug.cgi?id=413905 Maik Qualmann changed: What|Removed |Added Platform|Other |MS Windows -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 413905] Some icon / picture are not displayed in maps but picture have GPS data
https://bugs.kde.org/show_bug.cgi?id=413905 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #1 from Maik Qualmann --- Tested here with the Windows version. Icon and geographical position available. Perform a re-read of the metadata of the image (Menu-> Item-> Re-read Metadata from file). Has the image been added to the collection recently or a long time ago? How was it imported? Maik -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 413906] Crash when opening PSD file (PSDImageResourceSection::read)
https://bugs.kde.org/show_bug.cgi?id=413906 Ben XO changed: What|Removed |Added Attachment #123768|File which demonstrates |crash report description|crash | -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 413906] New: Crash when opening PSD file (PSDImageResourceSection::read)
https://bugs.kde.org/show_bug.cgi?id=413906 Bug ID: 413906 Summary: Crash when opening PSD file (PSDImageResourceSection::read) Product: krita Version: 4.2.7.1 Platform: macOS Disk Images OS: macOS Status: REPORTED Severity: crash Priority: NOR Component: File formats Assignee: krita-bugs-n...@kde.org Reporter: m...@ben-xo.com Target Milestone: --- Created attachment 123768 --> https://bugs.kde.org/attachment.cgi?id=123768=edit File which demonstrates crash SUMMARY When opening a PSD template file from Awesome Merch, Krita immediately crashes. Example file: * http://www.awesomemerchandise.com/assets/templates/Stickers/Custom%20Shaped%20Sticker%20Template%2010cm.psd * http://www.awesomemerchandise.com/assets/templates/Packaging/Sticker%20Pack%20Header.psd STEPS TO REPRODUCE 1. Open one of the template files from Awesome Merch (e.g. https://www.awesomemerchandise.com/Custom-Shaped-Vinyl-Stickers-10cm -> "DOWNLOAD TEMPLATE"). Links above. 2. that's it. OBSERVED RESULT Immediate crash. (Crash report attached.) EXPECTED RESULT A CMYK template file appears in Krita. SOFTWARE/OS VERSIONS macOS: 10.14.6 (18G1012) ADDITIONAL INFORMATION This is with a fresh download of Krita from https://krita.org/en/download/krita-desktop/ -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 413905] New: Some icon / picture are not displayed in maps but picture have GPS data
https://bugs.kde.org/show_bug.cgi?id=413905 Bug ID: 413905 Summary: Some icon / picture are not displayed in maps but picture have GPS data Product: digikam Version: 6.3.0 Platform: Other OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: Geolocation-Engine Assignee: digikam-bugs-n...@kde.org Reporter: 8025...@free.fr Target Milestone: --- Created attachment 123767 --> https://bugs.kde.org/attachment.cgi?id=123767=edit One of the picture I cannnot displayed in any maps SUMMARY A picture have GPS data but I cannot display the icon / picture in any maps available in DigiKam. You can find the picture attached in this message. STEPS TO REPRODUCE 1. Try to display the picture location in any maps available in DigiKam 2. 3. OBSERVED RESULT No picture / icon are displayed in any maps EXPECTED RESULT To be able to display the icon / picture location in the map Many thanks in advance for helping me to solve this bug. Best Regards 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.
[digikam] [Bug 413837] Reverse geolocation deletes previous tags from the picture
https://bugs.kde.org/show_bug.cgi?id=413837 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com --- Comment #9 from caulier.gil...@gmail.com --- Hi Maik, No. I just tested with AppImage 6.4.0, and i cannot reproduce the problem. Perhaps the database is corrupted ? The console trace will help to investiguate. Gilles -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 413837] Reverse geolocation deletes previous tags from the picture
https://bugs.kde.org/show_bug.cgi?id=413837 --- Comment #8 from Maik Qualmann --- The output of the console may be interesting from assigning the test tag to reverse geolocation. Gilles, can you reproduce a problem here? Maik -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 413869] Colour brush settings don't work when brush size is 1 pixel
https://bugs.kde.org/show_bug.cgi?id=413869 Ahab Greybeard changed: What|Removed |Added CC||ahab.greybe...@hotmail.co.u ||k Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #2 from Ahab Greybeard --- I can confirm this for the 4.3.0-prealpha (git 33bc57f) appimage. As noted by Tiar in the linked Reddit thread, "... Dmitry says it's because of Sharpness option." If you disable the Sharpness parameter then the colour adjustment (and other parameters) all work with their various control inputs. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 413896] crash application when trying to use uim anthy
https://bugs.kde.org/show_bug.cgi?id=413896 --- Comment #1 from Dominik Haumann --- Could you add debug symbols for kate, KTextEditor, Qt, and uim and reproduce again? Could you then also run kate with: valgrind kate And oaste the output here? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 413900] Untranslated placeholder "Search..." in Kirigami.SearchField on second run
https://bugs.kde.org/show_bug.cgi?id=413900 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 413902] Can't select the created date text in the properties dialog
https://bugs.kde.org/show_bug.cgi?id=413902 Nate Graham changed: What|Removed |Added Version Fixed In||5.65 Status|ASSIGNED|RESOLVED Resolution|--- |FIXED Latest Commit||https://commits.kde.org/kio ||/4a74cb139d8cdafe5a76252695 ||913441889ec157 --- Comment #2 from Nate Graham --- Git commit 4a74cb139d8cdafe5a76252695913441889ec157 by Nate Graham. Committed on 07/11/2019 at 05:37. Pushed by ngraham into branch 'master'. [KPropertiesDialog] Make creation date string mouse-selectable too FIXED-IN: 5.65 M +1-0src/widgets/kpropertiesdialog.cpp https://commits.kde.org/kio/4a74cb139d8cdafe5a76252695913441889ec157 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 263042] XFA Forms are not supported
https://bugs.kde.org/show_bug.cgi?id=263042 Oliver Sander changed: What|Removed |Added CC||oliver.san...@tu-dresden.de --- Comment #17 from Oliver Sander --- I wonder if it is feasible to aim for some form of partial support? A lot would be gained already if poppler were simply able to render the text on a page, without any fancyness or even interactivity. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 413904] New: Moving a file, renames the NEXT file to the moved file
https://bugs.kde.org/show_bug.cgi?id=413904 Bug ID: 413904 Summary: Moving a file, renames the NEXT file to the moved file Product: konqueror Version: 5.0.97 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: file list view Assignee: konq-b...@kde.org Reporter: cswans...@gmail.com Target Milestone: --- SUMMARY files 111.txt 222.txt STEPS TO REPRODUCE 1. If you drag 111.txt to a new place, 222.txt gets given the name 111.txt and it waits for you to hit return (to accept) or ESC (to stop it) - it's continually and easily reproduceable 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.
[Spectacle] [Bug 413361] Spectacle crashes every time when capturing a rectangular region
https://bugs.kde.org/show_bug.cgi?id=413361 --- 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.
[plasmashell] [Bug 412723] Switching virtual desktops sends wrong mouse signal
https://bugs.kde.org/show_bug.cgi?id=412723 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- 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.
[plasmashell] [Bug 413903] New: KWin crashes when closing the Google Chrome window
https://bugs.kde.org/show_bug.cgi?id=413903 Bug ID: 413903 Summary: KWin crashes when closing the Google Chrome window Product: plasmashell Version: 5.16.5 Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: davidshe...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.16.5) (Compiled from sources) Qt Version: 5.12.5 Frameworks Version: 5.60.0 Operating System: Linux 4.19.72-gentoo x86_64 Distribution (Platform): Gentoo Packages -- Information about the crash: - What I was doing when the application crashed: Closing the main Google Chrome window. I had expereinced this issue multiple times when closing the Chrome windows. My system is Gentoo 64 bit; my glibc version is 2.29-r2. The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f188782f880 (LWP 2057))] Thread 15 (Thread 0x7f1849938700 (LWP 80016)): #0 0x7f188ab400fc in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f188b622080 in () at /usr/lib64/libQt5Core.so.5 #2 0x7f188b621e9a in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib64/libQt5Core.so.5 #3 0x7f188d23668f in () at /usr/lib64/libQt5Quick.so.5 #4 0x7f188d2368e0 in () at /usr/lib64/libQt5Quick.so.5 #5 0x7f188b61b60e in () at /usr/lib64/libQt5Core.so.5 #6 0x7f188ab39458 in start_thread () at /lib64/libpthread.so.0 #7 0x7f188b2a96ef in clone () at /lib64/libc.so.6 Thread 14 (Thread 0x7f1848bea700 (LWP 38231)): #0 0x7f188ab400fc in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f188b622080 in () at /usr/lib64/libQt5Core.so.5 #2 0x7f188b621e9a in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib64/libQt5Core.so.5 #3 0x7f188d23668f in () at /usr/lib64/libQt5Quick.so.5 #4 0x7f188d2368e0 in () at /usr/lib64/libQt5Quick.so.5 #5 0x7f188b61b60e in () at /usr/lib64/libQt5Core.so.5 #6 0x7f188ab39458 in start_thread () at /lib64/libpthread.so.0 #7 0x7f188b2a96ef in clone () at /lib64/libc.so.6 Thread 13 (Thread 0x7f184a1ac700 (LWP 38170)): #0 0x7f188ab400fc in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f188b622080 in () at /usr/lib64/libQt5Core.so.5 #2 0x7f188b621e9a in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib64/libQt5Core.so.5 #3 0x7f188d23668f in () at /usr/lib64/libQt5Quick.so.5 #4 0x7f188d2368e0 in () at /usr/lib64/libQt5Quick.so.5 #5 0x7f188b61b60e in () at /usr/lib64/libQt5Core.so.5 #6 0x7f188ab39458 in start_thread () at /lib64/libpthread.so.0 #7 0x7f188b2a96ef in clone () at /lib64/libc.so.6 Thread 12 (Thread 0x7f184aaf2700 (LWP 9958)): #0 0x7f188ab400fc in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f188b622080 in () at /usr/lib64/libQt5Core.so.5 #2 0x7f188b621e9a in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib64/libQt5Core.so.5 #3 0x7f188d23668f in () at /usr/lib64/libQt5Quick.so.5 #4 0x7f188d2368e0 in () at /usr/lib64/libQt5Quick.so.5 #5 0x7f188b61b60e in () at /usr/lib64/libQt5Core.so.5 #6 0x7f188ab39458 in start_thread () at /lib64/libpthread.so.0 #7 0x7f188b2a96ef in clone () at /lib64/libc.so.6 Thread 11 (Thread 0x7f184bbff700 (LWP 3773)): #0 0x7f188ab400fc in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f188b622080 in () at /usr/lib64/libQt5Core.so.5 #2 0x7f188b621e9a in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib64/libQt5Core.so.5 #3 0x7f188d23668f in () at /usr/lib64/libQt5Quick.so.5 #4 0x7f188d2368e0 in () at /usr/lib64/libQt5Quick.so.5 #5 0x7f188b61b60e in () at /usr/lib64/libQt5Core.so.5 #6 0x7f188ab39458 in start_thread () at /lib64/libpthread.so.0 #7 0x7f188b2a96ef in clone () at /lib64/libc.so.6 Thread 10 (Thread 0x7f186700 (LWP 3772)): #0 0x7f188b29d633 in poll () at /lib64/libc.so.6 #1 0x7f188999d69e in () at /usr/lib64/libpulse.so.0 #2 0x7f188998f074 in pa_mainloop_poll () at /usr/lib64/libpulse.so.0 #3 0x7f188998f604 in pa_mainloop_iterate () at /usr/lib64/libpulse.so.0 #4 0x7f188998f6a0 in pa_mainloop_run () at /usr/lib64/libpulse.so.0 #5 0x7f188999da49 in () at /usr/lib64/libpulse.so.0 #6 0x7f1887abbd01 in () at /usr/lib64/pulseaudio/libpulsecommon-12.2.so #7 0x7f188ab39458 in start_thread () at /lib64/libpthread.so.0 #8 0x7f188b2a96ef in clone () at /lib64/libc.so.6 Thread 9 (Thread 0x7f184b3fe700 (LWP 3503)): #0 0x7f188ab3da05 in __pthread_mutex_unlock_usercnt
[dolphin] [Bug 413902] Can't select the created date text in the properties dialog
https://bugs.kde.org/show_bug.cgi?id=413902 Nate Graham changed: What|Removed |Added Ever confirmed|0 |1 Assignee|dolphin-bugs-n...@kde.org |n...@kde.org Status|REPORTED|ASSIGNED CC||n...@kde.org --- Comment #1 from Nate Graham --- Whoops! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 413864] Window > New View does not open new view
https://bugs.kde.org/show_bug.cgi?id=413864 --- Comment #4 from Ivy Wong --- Okay, I tried it on i3wm and it worked. I normally use the Ubuntu default (compiz, on Unity). -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 413902] Can't select the created date text in the properties dialog
https://bugs.kde.org/show_bug.cgi?id=413902 Michael Alexsander Silva Dias changed: What|Removed |Added CC||michaelalexsander@protonmai ||l.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 413902] New: Can't select the created date text in the properties dialog
https://bugs.kde.org/show_bug.cgi?id=413902 Bug ID: 413902 Summary: Can't select the created date text in the properties dialog Product: dolphin Version: 19.08.2 Platform: Manjaro OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: michaelalexsan...@protonmail.com CC: kfm-de...@kde.org Target Milestone: --- When checking the properties of a file, while all the other pieces of info can have their text selected, the "Created" date cannot. KDE Plasma Version: 5.17.2 KDE Frameworks Version: 5.63.0 Qt Version: 5.13.1 -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 413901] Ksysguard aborted when its Wayland connection broke
https://bugs.kde.org/show_bug.cgi?id=413901 Matt Fagnani changed: What|Removed |Added Summary|Konsole aborted when its|Ksysguard aborted when its |Wayland connection broke|Wayland connection broke Keywords||wayland -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 413901] New: Konsole aborted when its Wayland connection broke
https://bugs.kde.org/show_bug.cgi?id=413901 Bug ID: 413901 Summary: Konsole aborted when its Wayland connection broke Product: ksysguard Version: 5.16.5 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: matthew.fagn...@utoronto.ca Target Milestone: --- Application: ksysguard (5.16.5) Qt Version: 5.12.5 Frameworks Version: 5.61.0 Operating System: Linux 5.3.8-300.fc31.x86_64 x86_64 Distribution (Platform): Fedora RPMs -- Information about the crash: - What I was doing when the application crashed: I was running Plasma 5.16.5 on Wayland in Fedora 31. I updated the system with the updates-testing repo enabled using sudo dnf upgrade --refresh. The update was taking longer than usual, and the system was slowing down. I started ksysguard 5.16.5. ksysguard's title bar showed (Not Responding) and its colours were faded. I tried to click on the CPU column title to sort by it. After about a minute, ksysguard aborted with a message that the Wayland connection had broken in the journal and trace. ksysguard[3134]: The Wayland connection broke. Did the Wayland compositor die? No other programs showed such a message about the Wayland connection breaking in the journal. The update completed correctly after a few minutes. I saw a similar abort of konsole with the same "The Wayland connection broke" message three weeks ago https://bugs.kde.org/show_bug.cgi?id=413058 -- Backtrace: Application: System Monitor (ksysguard), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". 29return SYSCALL_CANCEL (poll, fds, nfds, timeout); [Current thread is 1 (Thread 0x7f33d8dd6840 (LWP 3134))] Thread 10 (Thread 0x7f339effd700 (LWP 3143)): #0 0x7f33d94c7a1f in __GI___poll (fds=0x7f33880029e0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f33cf40279e in g_main_context_poll (priority=, n_fds=1, fds=0x7f33880029e0, timeout=, context=0x7f3388000c30) at ../glib/gmain.c:4216 #2 g_main_context_iterate (context=context@entry=0x7f3388000c30, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../glib/gmain.c:3912 #3 0x7f33cf4028d3 in g_main_context_iteration (context=0x7f3388000c30, may_block=may_block@entry=1) at ../glib/gmain.c:3978 #4 0x7f33d7b5acd3 in QEventDispatcherGlib::processEvents (this=0x7f3388000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #5 0x7f33d7b04ceb in QEventLoop::exec (this=this@entry=0x7f339effcd30, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #6 0x7f33d795d395 in QThread::exec (this=this@entry=0x7f33d7f0c060 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #7 0x7f33d7e88f4a in QDBusConnectionManager::run (this=0x7f33d7f0c060 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:178 #8 0x7f33d795e4e6 in QThreadPrivate::start (arg=0x7f33d7f0c060 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:361 #9 0x7f33cfd2a4e2 in start_thread (arg=) at pthread_create.c:479 #10 0x7f33d94d2643 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 9 (Thread 0x7f339f7fe700 (LWP 3142)): #0 futex_wait_cancelable (private=0, expected=0, futex_word=0x555dd7d7ae18) at ../sysdeps/unix/sysv/linux/futex-internal.h:80 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x555dd7d7adc8, cond=0x555dd7d7adf0) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x555dd7d7adf0, mutex=0x555dd7d7adc8) at pthread_cond_wait.c:638 #3 0x7f33bd5d7e6b in cnd_wait (mtx=0x555dd7d7adc8, cond=0x555dd7d7adf0) at ../include/c11/threads_posix.h:155 #4 util_queue_thread_func (input=input@entry=0x555dd7d99170) at ../src/util/u_queue.c:272 #5 0x7f33bd5d7a7b in impl_thrd_routine (p=) at ../include/c11/threads_posix.h:87 #6 0x7f33cfd2a4e2 in start_thread (arg=) at pthread_create.c:479 #7 0x7f33d94d2643 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 8 (Thread 0x7f339700 (LWP 3141)): #0 futex_wait_cancelable (private=0, expected=0, futex_word=0x555dd797b8d0) at ../sysdeps/unix/sysv/linux/futex-internal.h:80 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x555dd797b880, cond=0x555dd797b8a8) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x555dd797b8a8, mutex=0x555dd797b880) at pthread_cond_wait.c:638 #3 0x7f33bd5d7e6b in cnd_wait (mtx=0x555dd797b880, cond=0x555dd797b8a8) at ../include/c11/threads_posix.h:155 #4 util_queue_thread_func (input=input@entry=0x555dd797d180) at ../src/util/u_queue.c:272 #5 0x7f33bd5d7a7b in impl_thrd_routine (p=) at ../include/c11/threads_posix.h:87 #6
[Discover] [Bug 412908] scrolling of app description page is slow/choppy on Wayland
https://bugs.kde.org/show_bug.cgi?id=412908 Aleix Pol changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED Latest Commit||https://commits.kde.org/dis ||cover/836b5595516c323ad75b2 ||7ecbec11f7fdbd857ca --- Comment #8 from Aleix Pol --- Git commit 836b5595516c323ad75b27ecbec11f7fdbd857ca by Aleix Pol. Committed on 07/11/2019 at 02:36. Pushed by apol into branch 'Plasma/5.17'. ui: improve busy indicator handling Simplifies the logic, makes sure it's not moving unless we are seeing it. M +7-51 discover/qml/ApplicationsListPage.qml https://commits.kde.org/discover/836b5595516c323ad75b27ecbec11f7fdbd857ca -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 385321] Screen locker 'unable to unlock, use loginctl instead' randomly when system is locked
https://bugs.kde.org/show_bug.cgi?id=385321 manuelcha...@gmail.com changed: What|Removed |Added CC||manuelcha...@gmail.com --- Comment #2 from manuelcha...@gmail.com --- This is happening to me randomly on Neon. Using latest KDE packages. I tried switching between OpenGL 2.0 and 3.0 compositors, both trigger it. I have to issue the command in another TTY to unlock. kscreenlocker_g[8579]: segfault at 7ffc56242fe8 ip 7f390f2f242d sp 7ffc56242ff0 error 6 in libc-2.27.so[7f390f297000+1e7000] -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 413795] when i zoom on canvas its slow and delays a ton my work. Quality of lines are also a ,ittl
https://bugs.kde.org/show_bug.cgi?id=413795 M changed: What|Removed |Added CC||manuel.snudl.zeidler@gmail. ||com --- Comment #2 from M --- Please also check if you have Canvas Graphics Acceleration activated at all under Settings > Configure Krita > Display and that Scaling Mode is set to High Quality Filtering. Also try switching between OpenGL and ANGLE for the Preferred Renderer, restart Krita and see if those settings stay enabled. -- You are receiving this mail because: You are watching all bug changes.
[knetattach] [Bug 413889] Can't connect to Nextcloud server
https://bugs.kde.org/show_bug.cgi?id=413889 techxga...@outlook.com changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #2 from techxga...@outlook.com --- Never mind. Figured out what went wrong -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 413900] Untranslated placeholder "Search..." in Kirigami.SearchField on second run
https://bugs.kde.org/show_bug.cgi?id=413900 --- Comment #2 from Alexander Potashev --- Yaroslav (CC'd) was able to reproduce after a few runs of the KCM. I'm not sure if two attempts running the KCM is always enough to reproduce, it might depend on the system or software configuration. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 413900] Untranslated placeholder "Search..." in Kirigami.SearchField on second run
https://bugs.kde.org/show_bug.cgi?id=413900 Alexander Potashev changed: What|Removed |Added CC||zawer...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 413900] Untranslated placeholder "Search..." in Kirigami.SearchField on second run
https://bugs.kde.org/show_bug.cgi?id=413900 --- Comment #1 from Alexander Potashev --- I guess that the search field is implemented with Kirigami.SearchField. The placeholder is translated into Russian in messages/frameworks/libkirigami2plugin_qt.po. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 413900] New: Untranslated placeholder "Search..." in Kirigami.SearchField on second run
https://bugs.kde.org/show_bug.cgi?id=413900 Bug ID: 413900 Summary: Untranslated placeholder "Search..." in Kirigami.SearchField on second run Product: kwin Version: 5.17.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: aspotas...@gmail.com Target Milestone: --- SUMMARY Untranslated placeholder "Search..." in Kirigami.SearchField on second run. STEPS TO REPRODUCE 1. Change Plasma system language to Russian 2. Start new Plasma session 3. Run "kcmshell5 kcm_kwin_effects" 4. Notice that the search field placeholder "Search..." is translated as "Поиск...". 5. Close the dialog. 6. Run "kcmshell5 kcm_kwin_effects" again. OBSERVED RESULT Search field placeholder "Search..." is not translated into Russian. EXPECTED RESULT Search field placeholder "Search..." should use Russian translation. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 5.17.2 (available in About System) KDE Plasma Version: 5.17.2 KDE Frameworks Version: 5.63.0 Qt Version: 5.14.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 411584] The Apply button is inactive in Night Color KCM
https://bugs.kde.org/show_bug.cgi?id=411584 Alexander Potashev changed: What|Removed |Added CC||aspotas...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 412078] Hovering on checkboxes or comboboxes changes their color to black
https://bugs.kde.org/show_bug.cgi?id=412078 Nate Graham changed: What|Removed |Added URL|https://gitlab.gnome.org/GN |https://gitlab.gnome.org/GN |OME/gtk/issues/2217 |OME/librsvg/issues/525 --- Comment #44 from Nate Graham --- Looks like the upstream issue is being fixed. See https://gitlab.gnome.org/GNOME/librsvg/issues/525 We'll investigate at which point we can bring this back! -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 386754] Search box cropped when Dolphin window is not wide enough
https://bugs.kde.org/show_bug.cgi?id=386754
--- Comment #3 from Ismael Asensio ---
Git commit 7949aee2d2528fb3adfc83d43799f1566e835466 by Ismael Asensio.
Committed on 07/11/2019 at 00:51.
Pushed by iasensio into branch 'master'.
Make the search box more compact
Summary:
Reduce the spacing between widgets and remove the content margins on the
extended search options to have a more compact and space-saving layout.
Currently, some widgets are not even aligned.
This will be even more important if we remove the toggle button for 'More
Options'.
Test Plan:
BEFORE: {F7681182}
AFTER: {F7681184}
Reviewers: elvisangelaccio, ngraham, #dolphin, #vdg
Reviewed By: elvisangelaccio, ngraham, #dolphin, #vdg
Subscribers: kfm-devel
Tags: #dolphin
Differential Revision: https://phabricator.kde.org/D25028
M +1-0src/global.h
M +1-0src/search/dolphinfacetswidget.cpp
M +4-0src/search/dolphinsearchbox.cpp
https://commits.kde.org/dolphin/7949aee2d2528fb3adfc83d43799f1566e835466
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 346680] Untranslatable strings in Comment column
https://bugs.kde.org/show_bug.cgi?id=346680 Alexander Potashev changed: What|Removed |Added CC||aspotas...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 413899] New: not working properly
https://bugs.kde.org/show_bug.cgi?id=413899 Bug ID: 413899 Summary: not working properly Product: Discover Version: 5.17.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: rickyj...@yahoo.com CC: aleix...@kde.org Target Milestone: --- SUMMARY Hey thanks for fixing my icons and environment. I have a problem with Discover not connecting to internet again but also I have a problem with discovering my touch screen on KDE. Archlinux finds my drivers but KDE isnt showing anything connected. just wondering. STEPS TO REPRODUCE 1. Open Discover 2. wait for featured to load 3. OBSERVED RESULT featured window on discover not connected to internet EXPECTED RESULT list of featured plugins SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: archlinux 5 (available in About System) KDE Plasma Version: 5 KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION if you email me i can send you pictures of what I am talking about. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 413898] New: Why has KDevelop Find{LLVM, Clang}.cmake instead of using their CMake modules?
https://bugs.kde.org/show_bug.cgi?id=413898
Bug ID: 413898
Summary: Why has KDevelop Find{LLVM,Clang}.cmake instead of
using their CMake modules?
Product: kdevelop
Version: git master
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: kdevelop-bugs-n...@kde.org
Reporter: aaronpuch...@alice-dsl.net
Target Milestone: ---
Upstream LLVM/Clang provide CMake modules that provide all libraries as targets
to link against, these are by default installed into
/cmake/{llvm,clang}/. They can also be used from a local LLVM/Clang
build by setting LLVM_DIR=/lib/cmake/llvm and
Clang_DIR=/lib/cmake/clang.
Why don't we use that instead of maintaining our own Find{LLVM,Clang}.cmake?
--
You are receiving this mail because:
You are watching all bug changes.
[Discover] [Bug 413897] New: button
https://bugs.kde.org/show_bug.cgi?id=413897 Bug ID: 413897 Summary: button Product: Discover Version: 5.12.8 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: nakei...@yandex.ru CC: aleix...@kde.org Target Milestone: --- Created attachment 123766 --> https://bugs.kde.org/attachment.cgi?id=123766=edit The mouse cursor on this button in the right corner SUMMARY Hello, in the discover application center, after installing any program, the start application button appears. It does not work, tried on different programs. SOFTWARE/OS VERSIONS OpenSUSE 15.1 Leap KDE Plasma Version: 5.12.8 KDE Frameworks Version: 5.55.0 Qt Version: 5.9.7 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 413829] Discover does not start with Qt 5.12
https://bugs.kde.org/show_bug.cgi?id=413829 --- Comment #4 from Aleix Pol --- Brilliant, thanks for investigating. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 413896] New: crash application when trying to use uim anthy
https://bugs.kde.org/show_bug.cgi?id=413896 Bug ID: 413896 Summary: crash application when trying to use uim anthy Product: kate Version: 19.08.2 Platform: Debian stable OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: kwrite Assignee: kwrite-bugs-n...@kde.org Reporter: codename...@hotmail.com Target Milestone: --- Application: kwrite (19.08.2) Qt Version: 5.12.5 Frameworks Version: 5.62.0 Operating System: Linux 5.3.0-1-amd64 x86_64 Distribution: Debian GNU/Linux bullseye/sid -- Information about the crash: - What I was doing when the application crashed: I use sway-wm and kwrite with wayland backend. I use debian unstable. When I activate uim, write some characters, and then press space multiple times to make it show up the candidate window, focus between the candidate window and kwrite flickers every frame until eventually (2~5 seconds later) it crashes. I reproduced this behavior also when using plasma's wayland session, and with weston too. I reproduced this behavior with konsole too. Not sure if it is a uim problem or a kde problem? Relevant environment variables: QT_IM_MODULE=uim QT_QPA_PLATFORMTHEME=qt5ct QT_QPA_PLATFORM=wayland The crash can be reproduced every time. -- Backtrace: Application: KWrite (kwrite), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f77a4784100 (LWP 16701))] Thread 3 (Thread 0x7f779affc700 (LWP 16705)): #0 futex_wait_cancelable (private=0, expected=0, futex_word=0x55c1d1a32ec8) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x55c1d1a32e78, cond=0x55c1d1a32ea0) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x55c1d1a32ea0, mutex=0x55c1d1a32e78) at pthread_cond_wait.c:655 #3 0x7f779b82330b in cnd_wait (mtx=0x55c1d1a32e78, cond=0x55c1d1a32ea0) at ../include/c11/threads_posix.h:155 #4 util_queue_thread_func (input=input@entry=0x55c1d1d4fe50) at ../src/util/u_queue.c:272 #5 0x7f779b822f27 in impl_thrd_routine (p=) at ../include/c11/threads_posix.h:87 #6 0x7f77a7a39fb7 in start_thread (arg=) at pthread_create.c:486 #7 0x7f77a91a52cf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7f77a2d4b700 (LWP 16702)): #0 0x7f77a919ad0f in __GI___poll (fds=0x7f779c005260, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f77a722909e in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f77a72291bf in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f77a971680b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f77a96bf71b in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f77a9500751 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f77a7fa94e6 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7f77a95018d2 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f77a7a39fb7 in start_thread (arg=) at pthread_create.c:486 #9 0x7f77a91a52cf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7f77a4784100 (LWP 16701)): [KCrash Handler] #5 0x7f77a96c097d in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f77a437f174 in QUimPlatformInputContext::updatePreedit() () from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforminputcontexts/libuimplatforminputcontextplugin.so #7 0x7f77a416e3f8 in ?? () from /usr/lib/x86_64-linux-gnu/libuim.so.8 #8 0x7f77a4144d0c in ?? () from /usr/lib/x86_64-linux-gnu/libuim-scm.so.0 #9 0x7f77a4144f79 in ?? () from /usr/lib/x86_64-linux-gnu/libuim-scm.so.0 #10 0x7f77a414fc36 in ?? () from /usr/lib/x86_64-linux-gnu/libuim-scm.so.0 #11 0x7f77a4144cdb in ?? () from /usr/lib/x86_64-linux-gnu/libuim-scm.so.0 #12 0x7f77a4144f79 in ?? () from /usr/lib/x86_64-linux-gnu/libuim-scm.so.0 #13 0x7f77a41450b1 in ?? () from /usr/lib/x86_64-linux-gnu/libuim-scm.so.0 #14 0x7f77a4145219 in ?? () from /usr/lib/x86_64-linux-gnu/libuim-scm.so.0 #15 0x7f77a4144cdb in ?? () from /usr/lib/x86_64-linux-gnu/libuim-scm.so.0 #16 0x7f77a4144f79 in ?? () from /usr/lib/x86_64-linux-gnu/libuim-scm.so.0 #17 0x7f77a41455a4 in ?? () from /usr/lib/x86_64-linux-gnu/libuim-scm.so.0 #18 0x7f77a436a2fd in GCROOTS_call_with_gc_ready_stack () from /usr/lib/x86_64-linux-gnu/libgcroots.so.0 #19 0x7f77a41548c3 in uim_scm_callf () from /usr/lib/x86_64-linux-gnu/libuim-scm.so.0 #20 0x7f77a416defd in ?? () from /usr/lib/x86_64-linux-gnu/libuim.so.8 #21 0x7f77a416dff0 in uim_press_key () from /usr/lib/x86_64-linux-gnu/libuim.so.8 #22
[konqueror] [Bug 413895] New: Renaming a file, then moving it, automatically renames the NEXT file as well
https://bugs.kde.org/show_bug.cgi?id=413895 Bug ID: 413895 Summary: Renaming a file, then moving it, automatically renames the NEXT file as well Product: konqueror Version: 5.0.97 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: file list view Assignee: konq-b...@kde.org Reporter: cswans...@gmail.com Target Milestone: --- SUMMARY you have 3 files 111.txt 222.txt 333.txt STEPS TO REPRODUCE 1. rename 111.txt to aaa.txt 2. move aaa.txt to a diff dir 3. 222.txt is renamed to aaa.txt - it doesnt SAVE it, but it starts the rename - ENTER renames it, escape fixes it - it's happened a dozen times to me, very disconcerting 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 email me at cswans...@gmail.com if you want more info - but it was very easy to reproduce -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 413893] Crash, when transparency mask is added to filter layer and manipulated
https://bugs.kde.org/show_bug.cgi?id=413893 Ahab Greybeard changed: What|Removed |Added Status|REPORTED|CONFIRMED CC||ahab.greybe...@hotmail.co.u ||k Ever confirmed|0 |1 --- Comment #1 from Ahab Greybeard --- I can confirm this crash for the conditions reported, using the 4.3.0 prealpha (git 2c21a4c) appimage. If I use a Gaussian Blur filter layer, I can't induce a crash, despite many and complicated attempts. With the Colour Adjustment filter layer, it happens on the second deletion of the added transparency mask. Krita Version: 4.3.0-prealpha (git 2c21a4c) Languages: en_GB, en Hidpi: true Qt Version (compiled): 5.12.5 Version (loaded): 5.12.5 OS Information Build ABI: x86_64-little_endian-lp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: linux Kernel Version: 4.19.0-6-amd64 Pretty Productname: Debian GNU/Linux 10 (buster) Product Type: debian Product Version: 10 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 413087] lockscreen broken when mediacontrols active
https://bugs.kde.org/show_bug.cgi?id=413087 --- Comment #7 from Jacques W --- (In reply to Jacques W from comment #6) > (In reply to sasori.nami from comment #5) > > PS: I've been working since 2019-10-19 with the line commented and can > > confirm that I didn't have the problem once in that time. > > I got the exact same problem. Best way to reproduce is just use > /usr/lib/kscreenlocker_greet --testing command to test. With the line > commented out screen locking works again :-) I use: Mellowplayer Linux 5.3.8-3 Plasma 5.17.2 KDE Frameworks 5.63.0 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 413087] lockscreen broken when mediacontrols active
https://bugs.kde.org/show_bug.cgi?id=413087 Jacques W changed: What|Removed |Added CC||nuclearjo...@gmail.com --- Comment #6 from Jacques W --- (In reply to sasori.nami from comment #5) > PS: I've been working since 2019-10-19 with the line commented and can > confirm that I didn't have the problem once in that time. I got the exact same problem. Best way to reproduce is just use /usr/lib/kscreenlocker_greet --testing command to test. With the line commented out screen locking works again :-) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 410387] Krita suddenly closes while using the palettize filter
https://bugs.kde.org/show_bug.cgi?id=410387 M changed: What|Removed |Added CC||manuel.snudl.zeidler@gmail. ||com --- Comment #21 from M --- Created attachment 123765 --> https://bugs.kde.org/attachment.cgi?id=123765=edit GDB backtrace So strangely enough, I can reliably produce a hang / crash when I choose the Pastel 5x2 or PixelArt 16 palettes in the filter with my build from master (git 33bc57f), but on the newest AppImage (also git 33bc57f) I only managed to provoke the same crash twice in about 10 restarted sessions. I'll attach my GDB backtace in any case. -- 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 #3 from DHCP Easyness --- I can confirm this is still a bug in Kubuntu 19.10 released last month. Can't run kpat games mod3 or spider unless a big hard drive for ~/.xsession-errors so disk won't full. SOFTWARE/OS VERSIONS Windows: N/A macOS: N/A Linux/KDE Plasma: Kubuntu 19.10 (available in About System) KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.4 ADDITIONAL INFORMATION You can reproduce this from a Kubuntu 19.10 Live CD -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 413894] New: File Layer stops automatic update after the first time.
https://bugs.kde.org/show_bug.cgi?id=413894 Bug ID: 413894 Summary: File Layer stops automatic update after the first time. Product: krita Version: 4.2.7-beta1 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: Layer Stack Assignee: krita-bugs-n...@kde.org Reporter: snopm...@yahoo.com Target Milestone: --- SUMMARY File Layer stops automatic update after the first time. STEPS TO REPRODUCE 1. Create a File Layer. 2. Edit the image linked to the File Layer then save. 3. The File Layer will update. 4. Try to repeat Step 2, the File Layer will no longer update from this point on. OBSERVED RESULT File Layer will automatically update once after the linked image has been edited then saved. EXPECTED RESULT File Layer updates every time the linked image is edited then saved. SOFTWARE/OS VERSIONS Windows: Windows 10 Home 64-Bit macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Krita Version: 4.2.7-beta1 (git a75d7b2) Qt Version (compiled): 5.12.5 Version (loaded): 5.12.5 OS Information Build ABI: x86_64-little_endian-llp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: winnt Kernel Version: 10.0.18362 Pretty Productname: Windows 10 (10.0) Product Type: windows Product Version: 10 OpenGL Info Vendor: "Google Inc." Renderer: "ANGLE (NVIDIA GeForce GTX 660 Direct3D11 vs_5_0 ps_5_0)" Version: "OpenGL ES 3.0 (ANGLE 2.1.0.57ea533f79a7)" Shading language: "OpenGL ES GLSL ES 3.00 (ANGLE 2.1.0.57ea533f79a7)" 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 3.0, options QFlags(), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples 0, swapBehavior QSurfaceFormat::DefaultSwapBehavior, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::NoProfile) Version: 3.0 Supports deprecated functions false is OpenGL ES: true QPA OpenGL Detection Info supportsDesktopGL: true supportsAngleD3D11: true isQtPreferAngle: false Hardware Information Memory: 23 Gb Cores: 8 Swap: Z:/Krita_Swap_File -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 263042] XFA Forms are not supported
https://bugs.kde.org/show_bug.cgi?id=263042 Luigi Toscano changed: What|Removed |Added CC||luigi.tosc...@tiscali.it --- Comment #16 from Luigi Toscano --- IMHO it's fine to close this here, as it was before, if it belongs to poppler. But let's not pretend that we can snap our fingers and all the "deprecated" forms and their users (often slow moving enteriprises and, more important for everyday life, hovernment institutions). We shouldn't act like the CUPS project, which is deprecating the old PPD format, condemning a lot of hardware (which is supposed to last for long time) to obsolescence. For sure it would take a lot of money to implement this format and its support is not probably going to happen, but that does not mean that it wouldn't be useful and that it must die just because it's old. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413890] Missing UI elements, widget icons, tooltips background, possibly more
https://bugs.kde.org/show_bug.cgi?id=413890 --- Comment #2 from Mark Smith --- I actually found out it's related to me using software mode in Plasma Renderer... Still, it's odd that some random parts of the UI aren't rendering at all. Not sure if this needs to be closed or if it's worth it to investigate still. Anyway, on my system software rendering is much more responsive than OpenGL and that's why I was using it. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 413837] Reverse geolocation deletes previous tags from the picture
https://bugs.kde.org/show_bug.cgi?id=413837 --- Comment #7 from MarcP --- No, I have sidecars disabled completely (both read and write). Maybe it's that particular build. Do you want me to test a specific version? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 413837] Reverse geolocation deletes previous tags from the picture
https://bugs.kde.org/show_bug.cgi?id=413837 --- Comment #6 from Maik Qualmann --- No, not to reproduce here, test tag remains. Do you use sidecars? If so, read and write mode? Maik -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 413893] New: Crash, when transparency mask is added to filter layer and manipulated
https://bugs.kde.org/show_bug.cgi?id=413893 Bug ID: 413893 Summary: Crash, when transparency mask is added to filter layer and manipulated Product: krita Version: 4.2.7.1 Platform: Mint (Ubuntu based) OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: Filter Layers Assignee: krita-bugs-n...@kde.org Reporter: m...@deltagram.eu Target Milestone: --- SUMMARY When a transparency mask is added to a filter layer and some simple manipulation (like deleting and adding the mask again or going back and forth in Undo History) is performed, Krita crashes. STEPS TO REPRODUCE 1. Open an image. (In my example it had a size of 5184x3888px. 2. Add a filter layer. (In my case I used up a simple Color Adjustment.) 3. Add a transparency mask to this filter layer. Now, a few different procedures lead to Krita crashing: 4. Go back a few steps in the Undo History. 5. Go forward again in the Undo History. 6. Delete the transparency mask. 7. Krita crashes. (Video: https://vimeo.com/371430316) Alternatively: 4. Go back a few steps in the Undo History. 5. Go forward again in the Undo History. 6. Go back again in the Undo History. 7. Go forward again in the Undo History. 8. Krita crashes. (Video: https://vimeo.com/371431930) Alternatively: 4. Delete the transparency mask. 5. Add the transparency mask. 6. Delete the transparency mask. 7. Add the transparency mask. 8. ... X. Krita crashes. (Video: https://vimeo.com/371431102) OBSERVED RESULT Crash. EXPECTED RESULT No crash. :) SOFTWARE/OS VERSIONS Linux: Linux Mint 19.1 (based on Ubuntu Bionic) ADDITIONAL INFORMATION CPU: Intel© Xeon© CPU E5-2670 0 @ 2.60GHz × 8 GPU: NVIDIA GeForce GTX 1070 OpenCL: activated -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 413870] Wrong git status determination
https://bugs.kde.org/show_bug.cgi?id=413870 Elvis Angelaccio changed: What|Removed |Added CC||elvis.angelac...@kde.org --- Comment #1 from Elvis Angelaccio --- Do you mind uploading the patch on phabricator? See https://community.kde.org/Infrastructure/Phabricator for instructions. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413892] New: Plasma crash under Wayland when I unplugged second monitor
https://bugs.kde.org/show_bug.cgi?id=413892 Bug ID: 413892 Summary: Plasma crash under Wayland when I unplugged second monitor Product: plasmashell Version: 5.17.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: crib...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.17.2) Qt Version: 5.13.2 Frameworks Version: 5.63.0 Operating System: Linux 5.3.8-zen1-1-zen x86_64 Distribution: Arch Linux -- Information about the crash: - What I was doing when the application crashed: Plasma crashed when I unplugged a HDMI projection (second monitor). Plugged the projector and all went well. When I unplugged it Plasma crashed. - Unusual behavior I noticed: Plasma crash. - Custom settings of the application: No custom settings. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fb00c37ac80 (LWP 11176))] Thread 12 (Thread 0x7fafe21e0700 (LWP 11545)): #0 0x7fb0104bbc45 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fb010fca610 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7fb010fca702 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7fb012c50e3d in () at /usr/lib/libQt5Quick.so.5 #4 0x7fb012c510ee in () at /usr/lib/libQt5Quick.so.5 #5 0x7fb010fc4530 in () at /usr/lib/libQt5Core.so.5 #6 0x7fb0104b54cf in start_thread () at /usr/lib/libpthread.so.0 #7 0x7fb010c4e2d3 in clone () at /usr/lib/libc.so.6 Thread 11 (Thread 0x7fafcb7fe700 (LWP 11462)): #0 0x7fb0104bbc45 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fb010fca610 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7fb010fca702 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7fb012c50e3d in () at /usr/lib/libQt5Quick.so.5 #4 0x7fb012c510ee in () at /usr/lib/libQt5Quick.so.5 #5 0x7fb010fc4530 in () at /usr/lib/libQt5Core.so.5 #6 0x7fb0104b54cf in start_thread () at /usr/lib/libpthread.so.0 #7 0x7fb010c4e2d3 in clone () at /usr/lib/libc.so.6 Thread 10 (Thread 0x7fafcbfff700 (LWP 11441)): #0 0x7fb00f2d94e4 in g_mutex_unlock () at /usr/lib/libglib-2.0.so.0 #1 0x7fb00f329088 in () at /usr/lib/libglib-2.0.so.0 #2 0x7fb00f329241 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7fb0111eab2c in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7fb01119183c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7fb010fc3305 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7fb010fc4530 in () at /usr/lib/libQt5Core.so.5 #7 0x7fb0104b54cf in start_thread () at /usr/lib/libpthread.so.0 #8 0x7fb010c4e2d3 in clone () at /usr/lib/libc.so.6 Thread 9 (Thread 0x7fafe19df700 (LWP 11422)): #0 0x7fb0104bbc45 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fb010fca610 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7fb010fca702 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7fb012c50e3d in () at /usr/lib/libQt5Quick.so.5 #4 0x7fb012c510ee in () at /usr/lib/libQt5Quick.so.5 #5 0x7fb010fc4530 in () at /usr/lib/libQt5Core.so.5 #6 0x7fb0104b54cf in start_thread () at /usr/lib/libpthread.so.0 #7 0x7fb010c4e2d3 in clone () at /usr/lib/libc.so.6 Thread 8 (Thread 0x7faff4c8d700 (LWP 11419)): #0 0x7fb00f326dbb in () at /usr/lib/libglib-2.0.so.0 #1 0x7fb00f3276cc in () at /usr/lib/libglib-2.0.so.0 #2 0x7fb00f32898b in g_main_context_prepare () at /usr/lib/libglib-2.0.so.0 #3 0x7fb00f329096 in () at /usr/lib/libglib-2.0.so.0 #4 0x7fb00f329241 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #5 0x7fb0111eab2c in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7fb01119183c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #7 0x7fb010fc3305 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #8 0x7fb010fc4530 in () at /usr/lib/libQt5Core.so.5 #9 0x7fb0104b54cf in start_thread () at /usr/lib/libpthread.so.0 #10 0x7fb010c4e2d3 in clone () at /usr/lib/libc.so.6 Thread 7 (Thread 0x7fafe34e7700 (LWP 11382)): #0 0x7fb00f32067f in g_source_ref () at /usr/lib/libglib-2.0.so.0 #1 0x7fb00f3276b2 in () at /usr/lib/libglib-2.0.so.0 #2 0x7fb00f32782f in g_main_context_check () at /usr/lib/libglib-2.0.so.0 #3
[amarok] [Bug 413861] attempting to install scripts does nothing
https://bugs.kde.org/show_bug.cgi?id=413861 Myriam Schweingruber changed: What|Removed |Added Status|REPORTED|RESOLVED Version|unspecified |kf5 Resolution|--- |LATER --- Comment #2 from Myriam Schweingruber --- scripting doesn't yet work in the kf5 port, so currently not a valid bug. FWIW: version 2.9.70 is pre-alpha and has not yet been officially released. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 413837] Reverse geolocation deletes previous tags from the picture
https://bugs.kde.org/show_bug.cgi?id=413837 --- Comment #5 from MarcP --- No, the low disk space was something temporary because some log files grew unexpectedly huge in my system. But when that happened, no tags could even be saved. I tried right now, from a fresh Digikam session, and I can reproduce it consistently. I recorded a screencap as an example. You can watch it here: https://imgur.com/a/75gpnSt In it, I selected a picture with GPS coordinates, I added a "test tag", then used the reverse geolocation tool. When I clicked apply, the tags used by the reverse geolocation tool replaced the old ones, including "test tag". -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 372340] Tagged face areas on portait (vertical) oriented images are mispositioned
https://bugs.kde.org/show_bug.cgi?id=372340 --- Comment #30 from Alexandre Belz --- Ok, thanks Maik. Do you think it can be managed in 7.0 ? -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 413118] Scrollbar mouse down/click on background zone not registered in Firefox
https://bugs.kde.org/show_bug.cgi?id=413118 Nate Graham changed: What|Removed |Added Summary|Scrollbar mouse down/click |Scrollbar mouse down/click |on background zone not |on background zone not |registered. |registered in Firefox Keywords||regression CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 263042] XFA Forms are not supported
https://bugs.kde.org/show_bug.cgi?id=263042 Nate Graham changed: What|Removed |Added Resolution|--- |UPSTREAM Status|CONFIRMED |RESOLVED --- Comment #15 from Nate Graham --- Sounds good to me. :) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 395618] Text glitching when moving file or folder on desktop w/ font rendering on subpixel hinting RGB and moderate
https://bugs.kde.org/show_bug.cgi?id=395618 Nate Graham changed: What|Removed |Added Resolution|WAITINGFORINFO |UPSTREAM Status|NEEDSINFO |RESOLVED --- Comment #17 from Nate Graham --- Yeah. Thanks for confirming! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 395618] Text glitching when moving file or folder on desktop w/ font rendering on subpixel hinting RGB and moderate
https://bugs.kde.org/show_bug.cgi?id=395618 --- Comment #16 from Patrick Silva --- what is "moderate" hinting? "Medium"? If so, I can't reproduce this issue on my system. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.17.2 KDE Frameworks Version: 5.63.0 Qt Version: 5.13.2 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 413891] Crash at startup
https://bugs.kde.org/show_bug.cgi?id=413891 --- Comment #1 from Hervé LEFEBVRE <066ce...@free.fr> --- Finally I've been able to start kdenlive after removing files : /home/aegir/.config/kdenliverc and /home/aegir/.config/kdenlive-appimagerc -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 413837] Reverse geolocation deletes previous tags from the picture
https://bugs.kde.org/show_bug.cgi?id=413837 --- Comment #4 from Maik Qualmann --- I can not reproduce the problem. Can it be related to your no longer existing disk space for the databases? Maik -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 413891] New: Crash at startup
https://bugs.kde.org/show_bug.cgi?id=413891 Bug ID: 413891 Summary: Crash at startup Product: kdenlive Version: 19.08.2 Platform: Neon Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: Installation Assignee: vpi...@kde.org Reporter: 066ce...@free.fr Target Milestone: --- Application: kdenlive (19.08.2) Qt Version: 5.13.1 Frameworks Version: 5.63.0 Operating System: Linux 5.0.0-32-generic x86_64 Distribution: KDE neon User Edition 5.17 -- Information about the crash: - What I was doing when the application crashed: 1) Start kdenlive, message "The default profile of Kdenlive is not set or invalid, press OK to set it to a correct value" 2) Click OK 3) Select any default profile (for example the first one 1024*576 16:9 PAL) 4) click OK --> crash Stdout : aegir@aegir-desktop:~/.local/share$ kdenlive org.kde.multimedia.kdenlive: WARNING: default profile not found: "/home/aegir/.local/share/kdenlive/profiles/customprofile1" . Returning random profile instead. org.kde.multimedia.kdenlive: WARNING: default profile not found: "/home/aegir/.local/share/kdenlive/profiles/customprofile1" . Returning random profile instead. org.kde.multimedia.kdenlive: WARNING: default profile not found: "/home/aegir/.local/share/kdenlive/profiles/customprofile1" . Returning random profile instead. KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = kdenlive path = /usr/bin pid = 26258 KCrash: Arguments: /usr/bin/kdenlive KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi from kdeinit sock_file=/run/user/1000/kdeinit5__0 [2]+ Arrêtékdenlive == Creating en empty ~/.local/share/kdenlive/profiles/customprofile1 allows to start kdenlive, but then it hangs when trying to open a file with following stdout : aegir@aegir-desktop:~/.local/share/kdenlive$ kdenlive org.kde.multimedia.kdenlive: WARNING: default profile not found: "/home/aegir/.local/share/kdenlive/profiles/customprofile1" . Returning random profile instead. org.kde.multimedia.kdenlive: WARNING: default profile not found: "/home/aegir/.local/share/kdenlive/profiles/customprofile1" . Returning random profile instead. org.kde.multimedia.kdenlive: WARNING: default profile not found: "/home/aegir/.local/share/kdenlive/profiles/customprofile1" . Returning random profile instead. KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = kdenlive path = /usr/bin pid = 26360 KCrash: Arguments: /usr/bin/kdenlive KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi from kdeinit sock_file=/run/user/1000/kdeinit5__0 [1]+ Arrêtékdenlive aegir@aegir-desktop:~/.local/share/kdenlive$ ps aux | grep live aegir24152 0.7 0.6 1286440 107360 ? Sl 21:45 0:04 /usr/lib/x86_64-linux-gnu/libexec/drkonqi -platform xcb -display :0 --appname kdenlive --apppath /usr/bin --signal 11 --pid 24136 --appversion 19.08.2 --programname Kdenlive --bugaddress sub...@bugs.kde.org --startupid 0 aegir26360 15.1 0.8 2230600 138680 pts/1 Tl 21:54 0:02 kdenlive aegir26376 0.6 0.2 621248 41860 ?Sl 21:54 0:00 /usr/lib/x86_64-linux-gnu/libexec/drkonqi -platform xcb -display :0 --appname kdenlive --apppath /usr/bin --signal 11 --pid 26360 --appversion 19.08.2 --programname Kdenlive --bugaddress sub...@bugs.kde.org --startupid 0 aegir26386 0.0 0.0 15660 1112 pts/1R+ 21:54 0:00 grep live aegir@aegir-desktop:~/.local/share/kdenlive$ ll total 24 4 drwxrwxr-x 6 aegir aegir 4096 nov. 6 21:53 . 4 drwxr-xr-x 89 aegir aegir 4096 nov. 6 21:41 .. 4 drwxrwxr-x 2 aegir aegir 4096 nov. 6 21:41 .backup 4 drwxrwxr-x 2 aegir aegir 4096 nov. 6 21:41 library 4 drwxrwxr-x 2 aegir aegir 4096 nov. 6 21:53 profiles 4 drwxrwxr-x 2 aegir aegir 4096 nov. 6 21:41 titles aegir@aegir-desktop:~/.local/share/kdenlive$ cd profiles aegir@aegir-desktop:~/.local/share/kdenlive/profiles$ touch customprofile1 aegir@aegir-desktop:~/.local/share/kdenlive/profiles$ kdenlive "motion_est" is blacklisted WARNING : Fails to parse "crop_detect" WARNING : Fails to parse "glsl.manager" WARNING : Fails to parse "movit.convert" WARNING : Fails to parse "movit.crop" WARNING : Fails to parse "movit.resample" WARNING : Fails to parse "movit.resize" "frei0r.3dflippo" is blacklisted "frei0r.bluescreen0r" is blacklisted "frei0r.bw0r" is blacklisted "frei0r.gamma" is blacklisted "frei0r.invert0r" is blacklisted "frei0r.rgbsplit0r" is blacklisted "frei0r.transparency" is blacklisted "frei0r.vertigo" is blacklisted "resample" is blacklisted "rgblut" is blacklisted "spot_remover" is blacklisted "text" is blacklisted "timer" is blacklisted "gtkrescale" is blacklisted WARNING : Fails to parse "telecide" WARNING
[drkonqi] [Bug 383863] Absence of DrKonqi icon in a tray after same crash reappeared
https://bugs.kde.org/show_bug.cgi?id=383863 --- Comment #10 from Patrick Silva --- I made plasma to crash following the steps from bug 409466 -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 413062] note can create only one unique sticky note
https://bugs.kde.org/show_bug.cgi?id=413062 --- Comment #10 from David Edmundson --- Wow, would I would never guessed that. We do use UUIDs in the note filename. Thanks for following up on that. -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 383863] Absence of DrKonqi icon in a tray after same crash reappeared
https://bugs.kde.org/show_bug.cgi?id=383863 --- Comment #9 from Harald Sitter --- Do you just send SEGV to plasmashell or how do you crash it? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 392015] Show "Unknown" faces in a more visible and preeminent place in the "People" list.
https://bugs.kde.org/show_bug.cgi?id=392015 Maik Qualmann changed: What|Removed |Added Resolution|--- |FIXED CC||metzping...@gmail.com Status|REPORTED|RESOLVED Version Fixed In||7.0.0 --- Comment #2 from Maik Qualmann --- In digiKam-7.0.0 these entries are now at the top of the list. I close the bug. Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 372340] Tagged face areas on portait (vertical) oriented images are mispositioned
https://bugs.kde.org/show_bug.cgi?id=372340 --- Comment #29 from Maik Qualmann --- Yes, it is known that digiKam mistreats the face rotation. I had already corrected it. However, since digiKam has been treating it like this since the very beginning, all longtime users are facing a problem. So we first have to write a converter that corrects all images. Maik -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 413690] missing icon in the preview of several task switchers
https://bugs.kde.org/show_bug.cgi?id=413690 Patrick Silva changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #2 from Patrick Silva --- (In reply to Nate Graham from comment #1) > Do you have Thunderbird, KMail, or any other email client installed? And > what is the default email client set to in System Settings > Applications > > Default Applications > Email Client? both thunderbird and kmail are installed here. "Use kmail as prefered email client" radio button is selected in System Settings > Applications > > Default Applications > Email Client. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 405980] The area of a "face rectangle" in the picture is different than the face thumbnail.
https://bugs.kde.org/show_bug.cgi?id=405980 Alexandre Belz changed: What|Removed |Added CC||alexandre.b...@live.fr --- Comment #7 from Alexandre Belz --- I still see the issue with latest weekly build 6.4.0 when I browse my picture, with people correctly detected by Picasa but then wrongly positionned by Digikam. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 372340] Tagged face areas on portait (vertical) oriented images are mispositioned
https://bugs.kde.org/show_bug.cgi?id=372340 --- Comment #28 from Alexandre Belz --- (I'm using latest weekly build 6.4) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 372340] Tagged face areas on portait (vertical) oriented images are mispositioned
https://bugs.kde.org/show_bug.cgi?id=372340 --- Comment #27 from Alexandre Belz --- I have the same issue ! People correctly detected by Picasa, but Wrongly displayed by Digikam (the square is not correctly located) especially on rotated pictures. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 263042] XFA Forms are not supported
https://bugs.kde.org/show_bug.cgi?id=263042 Munzir Taha changed: What|Removed |Added CC||munzirt...@gmail.com --- Comment #14 from Munzir Taha --- After Albert explanation, I don't see a reason this bug should be open here. Actually after knowing that 1. It's now deprecated officially 2. It's an 1600 pp of proprietary format I would go and close my bug at poppler too, https://gitlab.freedesktop.org/poppler/poppler/issues/364 It wasn't deprecated officially when I filed mine. Even if there is enough money and resources we shouldn't bring the dead to life again. Let it die with peace for free. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 413062] note can create only one unique sticky note
https://bugs.kde.org/show_bug.cgi?id=413062 jms changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |UPSTREAM -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 383863] Absence of DrKonqi icon in a tray after same crash reappeared
https://bugs.kde.org/show_bug.cgi?id=383863 --- Comment #8 from Patrick Silva --- I can't reproduce this behavior after systemsettings crash or gwenview crash for example. But drkonqi icon does not reappear in systray after plasma crash until relogin. Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.17.80 KDE Frameworks Version: 5.64.0 Qt Version: 5.13.1 -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 413062] note can create only one unique sticky note
https://bugs.kde.org/show_bug.cgi?id=413062 --- Comment #9 from jms --- ok so there was a bug but not from note. for info this bug came from amd ryzen and how it set uuid. see for info https://www.reddit.com/r/kde/comments/cff976/are_keyboard_shortcuts_broken_on_51631/euvol55/ all uuid created are the same. doing a bios update (or microcode) will solve the problem. Works for me -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 392015] Show "Unknown" faces in a more visible and preeminent place in the "People" list.
https://bugs.kde.org/show_bug.cgi?id=392015 Alexandre Belz changed: What|Removed |Added CC||alexandre.b...@live.fr --- Comment #1 from Alexandre Belz --- I agree, I'm starting using People-based window, and scrolling to "Unknown" is not THAT obvious. -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 413854] Dolphin crashes repeatedly right after login to SMB server
https://bugs.kde.org/show_bug.cgi?id=413854 --- Comment #3 from Elvis Angelaccio --- > #6 0x7f649bc188f0 in ?? () from /usr/lib64/libKF5KIOCore.so.5 > #7 0x7f649bc11e42 in ?? () from /usr/lib64/libKF5KIOCore.so.5 Symbols for kio are still missing (you only have symbols for kcoreaddons). -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 412864] Latte dock crashed when changing layout
https://bugs.kde.org/show_bug.cgi?id=412864 --- Comment #8 from Christoph Feck --- The original reporter closed this ticket with comment #1. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 412864] Latte dock crashed when changing layout
https://bugs.kde.org/show_bug.cgi?id=412864 --- Comment #7 from Michail Vourlakos --- crash reports must follow https://userbase.kde.org/LatteDock/HowToReportCrashes in order to produce meaningful crash reports. In my system the crash is NOT reproducable. The minimum that user must do is follow the above guide AND include a latte layout file that produces that crash in its system. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 412864] Latte dock crashed when changing layout
https://bugs.kde.org/show_bug.cgi?id=412864 --- Comment #6 from Michail Vourlakos --- (In reply to Christoph Feck from comment #5) > Apparently, it doesn't work for multiple other reporters, who keep adding > their reports to a closed ticket. Reopening and reassigning. what does not work? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413890] Missing UI elements, widget icons, tooltips background, possibly more
https://bugs.kde.org/show_bug.cgi?id=413890 --- Comment #1 from Mark Smith --- Created attachment 123764 --> https://bugs.kde.org/attachment.cgi?id=123764=edit Correct popups\tooltips -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 412864] Latte dock crashed when changing layout
https://bugs.kde.org/show_bug.cgi?id=412864 Christoph Feck changed: What|Removed |Added Version|unspecified |0.9.4 Product|kde |lattedock Status|RESOLVED|REPORTED Resolution|WORKSFORME |--- Assignee|unassigned-b...@kde.org |mvourla...@gmail.com Component|general |application --- Comment #5 from Christoph Feck --- Apparently, it doesn't work for multiple other reporters, who keep adding their reports to a closed ticket. Reopening and reassigning. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 413695] bug in review bar, custom tool, text comment color gets reverted
https://bugs.kde.org/show_bug.cgi?id=413695 --- Comment #6 from Simone Gaiarin --- The settings look correct. The fact that when the annotation is moved the color is set to the correct one suggests that it is something related to how the annotation is rendered. The new annotation toolbar is not going to fix this. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413890] New: Missing UI elements, widget icons, tooltips background, possibly more
https://bugs.kde.org/show_bug.cgi?id=413890 Bug ID: 413890 Summary: Missing UI elements, widget icons, tooltips background, possibly more Product: plasmashell Version: 5.17.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: anon...@openmailbox.org CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY Some elements are missing in Plasma. I don't know what caused this, but it happened to me twice. I fixed it by deleting the following folders, effectively removing all of my customizations .cache, .config, .kde, .local/share in my home folder. I'm not sure which deletion fixed it the first time. It doesn't happen if I create a new user, only for my user. It is related to some corrupted setting or cache. Theme does not affect it as it happens on default themes or downloaded themes. STEPS TO REPRODUCE No idea as it happened suddenly twice in a few days. OBSERVED RESULT Widget icons\previews are missing, and also tooltip backgrounds, possibly more. I know this happened to me also on KDE Neon, not just Manjaro. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro KDE (available in About System) KDE Plasma Version: 5.17.2 KDE Frameworks Version: 5.63.0 Qt Version: 5.13.1 ADDITIONAL INFORMATION Screenshot of missing widget icons: https://forum.manjaro.org/uploads/default/optimized/3X/5/f/5ff530e6e6e5cf50882bb1e8ba77a1894d169528_2_194x375.png Screenshot of missing tooltip background: https://forum.manjaro.org/uploads/default/optimized/3X/f/a/fa93be2c00927de06c83fca186fb20ab56f4ac5f_2_646x500.png Other missing ui elements Tooltips when overing over themes or desktop background, IE when hovering over default desktop backgrounds, it usually displays a tooltip with a background, now it displays the text floating with no background. Attached is how it should look. -- You are receiving this mail because: You are watching all bug changes.
[knetattach] [Bug 413889] Can't connect to Nextcloud server
https://bugs.kde.org/show_bug.cgi?id=413889 --- Comment #1 from techxga...@outlook.com --- Not sure if this is the case, but the URL that popped up on my notification is webdavs://u...@example.com:443/nextcloud/remote.php/dav/files/USER/ FYI, I decided to make the URL look like an example for privacy reasons. -- You are receiving this mail because: You are watching all bug changes.
[knetattach] [Bug 413889] Can't connect to Nextcloud server
https://bugs.kde.org/show_bug.cgi?id=413889 techxga...@outlook.com changed: What|Removed |Added Platform|Other |Ubuntu Packages -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwidgetsaddons] [Bug 413827] KActionMenu sticky/delayed wrong behavior
https://bugs.kde.org/show_bug.cgi?id=413827 Simone Gaiarin changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #2 from Simone Gaiarin --- Yes, setPopupMode seems the right solution (and deprecating setSticky and setDelayed). -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 384515] [ksysguardd]: Internal buffer too small to read '/proc/cpuinfo'
https://bugs.kde.org/show_bug.cgi?id=384515 lots0logs changed: What|Removed |Added CC||dus...@falgout.us -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 413819] highlight annotation not carried over to pdfjs
https://bugs.kde.org/show_bug.cgi?id=413819 --- Comment #8 from ghavami...@hotmail.com --- pls ignore 1st picture, (it's same as 4, I don't know how to remove it) so i took exactly the same steps as before... and got a completely different this, I couldn't reproduce the same error, but got an even worse one! opened and saved annotation in okular (see screenshot) opened same in firefox.. as before cant see the colour but can see the note on hovering (cursor missing on screenshot) (see screenshot) opened same doc in foxit and made new annotation and saved (see screenshot) opened this is firefox... now there nothing at all opened same in okular... now okular highlight is missing! (see screenshot) for what it's worth it opens the same in adobe, okular note missing.. so I've attached the pdf... I worry if I do this again in 24 hours I'll get yet another result, I woish I had sent you the pdf and screenshots from the original bug report now... -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 413885] At least for some versions ~/.cache/kioexec/krun/ was not cleaned up
https://bugs.kde.org/show_bug.cgi?id=413885 --- Comment #2 from Serhiy Zahoriya --- kio_http_cache_cleaner was mentioned on IRC too, maybe the problem is that it's not functioning properly -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 413819] highlight annotation not carried over to pdfjs
https://bugs.kde.org/show_bug.cgi?id=413819 --- Comment #6 from ghavami...@hotmail.com --- Created attachment 123762 --> https://bugs.kde.org/attachment.cgi?id=123762=edit 4 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 413819] highlight annotation not carried over to pdfjs
https://bugs.kde.org/show_bug.cgi?id=413819 --- Comment #7 from ghavami...@hotmail.com --- Created attachment 123763 --> https://bugs.kde.org/attachment.cgi?id=123763=edit pdf -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 413819] highlight annotation not carried over to pdfjs
https://bugs.kde.org/show_bug.cgi?id=413819 --- Comment #5 from ghavami...@hotmail.com --- Created attachment 123761 --> https://bugs.kde.org/attachment.cgi?id=123761=edit 3 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 413819] highlight annotation not carried over to pdfjs
https://bugs.kde.org/show_bug.cgi?id=413819 --- Comment #4 from ghavami...@hotmail.com --- Created attachment 123760 --> https://bugs.kde.org/attachment.cgi?id=123760=edit 2 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 413819] highlight annotation not carried over to pdfjs
https://bugs.kde.org/show_bug.cgi?id=413819 --- Comment #2 from ghavami...@hotmail.com --- Created attachment 123758 --> https://bugs.kde.org/attachment.cgi?id=123758=edit 1 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 413819] highlight annotation not carried over to pdfjs
https://bugs.kde.org/show_bug.cgi?id=413819 --- Comment #3 from ghavami...@hotmail.com --- Created attachment 123759 --> https://bugs.kde.org/attachment.cgi?id=123759=edit 1 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 413174] 5.17 lost the ability to detect when a monitor is unplugged during a session
https://bugs.kde.org/show_bug.cgi?id=413174 Francisco Cribari changed: What|Removed |Added CC||crib...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[knetattach] [Bug 413889] New: Can't connect to Nextcloud server
https://bugs.kde.org/show_bug.cgi?id=413889 Bug ID: 413889 Summary: Can't connect to Nextcloud server Product: knetattach Version: 5.17.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: techxga...@outlook.com Target Milestone: --- SUMMARY Tried following the steps here: https://docs.nextcloud.com/server/stable/user_manual/files/access_webdav.html?highlight=webdav#accessing-files-with-kde-and-dolphin-file-manager. Still can't connect to Nextcloud via WebDAV STEPS TO REPRODUCE See this link https://docs.nextcloud.com/server/stable/user_manual/files/access_webdav.html?highlight=webdav#accessing-files-with-kde-and-dolphin-file-manager. OBSERVED RESULT "Unable to connect" popup EXPECTED RESULT SOFTWARE/OS VERSIONS Operating System: Kubuntu 19.10 KDE Plasma Version: 5.17.2 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.4 Kernel Version: 5.3.0-19-generic OS Type: 64-bit Processors: 4 × Intel® Core™ i5-6500 CPU @ 3.20GHz Memory: 15.6 GiB of RAM ADDITIONAL INFORMATION Wish Online Accounts will setup Nextcloud WebDAV as soon as we login, which I mentioned on bug 413888 -- You are receiving this mail because: You are watching all bug changes.
[KAccounts] [Bug 413888] New: Connect to Nextcloud via WebDAV when you login via Online Accounts
https://bugs.kde.org/show_bug.cgi?id=413888 Bug ID: 413888 Summary: Connect to Nextcloud via WebDAV when you login via Online Accounts Product: KAccounts Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kde-telepathy-b...@kde.org Reporter: techxga...@outlook.com Target Milestone: --- SUMMARY KDE's Online Accounts doesn't connect to Nextcloud via WebDAV as soon as you login. SOFTWARE/OS VERSIONS Operating System: Kubuntu 19.10 KDE Plasma Version: 5.17.2 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.4 Kernel Version: 5.3.0-19-generic OS Type: 64-bit Processors: 4 × Intel® Core™ i5-6500 CPU @ 3.20GHz Memory: 15.6 GiB of RAM ADDITIONAL INFORMATION For some reason, I can't even connect to my Nextcloud server even if I set it up manually. -- You are receiving this mail because: You are watching all bug changes.
