[kdenlive] [Bug 413886] kdenlive won't load beyond a specific percentage
https://bugs.kde.org/show_bug.cgi?id=413886 Davy Bartoloni changed: What|Removed |Added CC||bartol...@outlook.com --- Comment #4 from Davy Bartoloni --- project loading fails all times when i select OpenGLES backend on Windows 10 (without Intel card) but maybe this is not related to your report... -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 413900] Untranslated placeholder "Search..." in Kirigami.SearchField on second run
https://bugs.kde.org/show_bug.cgi?id=413900 --- Comment #7 from Méven Car --- The string "Search..." is correctly present in https://websvn.kde.org/*checkout*/trunk/l10n-kf5/fr/messages/kde-workspace/kcm_kwin_effects.po This hints towards an issue in kirigami/Qt qml translation propagation/loading. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413934] New: High CPU usage when switching wallpaper as slideshow
https://bugs.kde.org/show_bug.cgi?id=413934 Bug ID: 413934 Summary: High CPU usage when switching wallpaper as slideshow Product: plasmashell Version: 5.17.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Image Wallpaper Assignee: notm...@gmail.com Reporter: xwaang1...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY When I configure the desktop to use images from a folder located on an SSD ext4 drive as wallpaper using a time ordered slideshow which changes image every 10 seconds, I see the CPU usage going up to about 25% (from a base constant level of less than 2%) every time the image is changed (it seems that one of the 4 CPU cores goes to 100%). If I change the changing rate of images nothing changes (CPU usage continue to goes up every time the image is changed) STEPS TO REPRODUCE 1. Set the wallpaper as slideshow every 10 seconds 2. Monitor the CPU usage using sudo top or a plasmoid OBSERVED RESULT CPU usage continue to goes up every time the image is changed EXPECTED RESULT Changing a wallpaper image should not require high CPU usage on an i7-6700HQ with 16GB f ram and SSD drive. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Archlinux (available in About System) KDE Plasma Version: 5.17.2-1 KDE Frameworks Version: 5.63.0 Qt Version: 5.13.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 413932] Constant crashing!
https://bugs.kde.org/show_bug.cgi?id=413932 Boudewijn Rempt changed: What|Removed |Added CC||b...@valdyas.org Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #1 from Boudewijn Rempt --- Could you please attach the contents of help->system information for bug reports and the kritacrash.log file that you can find in %LOCALAPPDATA% -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 413935] New: Delay before start until mouse click
https://bugs.kde.org/show_bug.cgi?id=413935 Bug ID: 413935 Summary: Delay before start until mouse click Product: kde Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: zmo...@hotmail.com Target Milestone: --- SUMMARY This happens sometimes when: - I enter name of application in KRunner dialog and press Enter, - double-click on freshly appeared image file in Krusader window to open GWenView. After that icon of starting application near mouse is shown and only after 3-5 seconds window of application appears. If I close application window and try to start it again then this time it shows instantly. I can interrupt that 3-5 second delay before start: I must click mouse somewhere. This problem I first noticed in KUbuntu 19.04 (plasma 5.17.1). Now I have freshly (no settings migrated) installed KUbuntu 19.10 and mentioned problem remains. OBSERVED RESULT Delay before start. EXPECTED RESULT Instant start. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 5.17.2 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.04 -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 413936] New: Lid close action is executed at unexpected times.
https://bugs.kde.org/show_bug.cgi?id=413936 Bug ID: 413936 Summary: Lid close action is executed at unexpected times. Product: Powerdevil Version: 5.17.2 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: benidan...@yahoo.de Target Milestone: --- SUMMARY Action on lid close (e.g. suspend) is in some cases executed at unexpected times. I noticed 2 different scenarios, they are not the same but I think they are related. a. STEPS TO REPRODUCE 1. in energy options: set to do nothing on lid close and apply 2. close lid and open again (nothing happens, as expected) 3. set to suspend on lid close 4. when I click apply, the computer suspends immediately This should not happen, as the lid close action was set to do nothing while the lid was closed. b. STEPS TO REPRODUCE 1. set use only external display when it is connected in display settings, set to suspend on lid close, but not when external display is connected in energy settings 2. start computer with lid closed and external display connected 3. open and close lid 4. switch off external display (either waiting for the delay in energy options or using 'xset dpms force off') 5. computer suspends as soon as the display is switched off (this does not happen if I do not open and close the lid in step 2) Independent of whether the lid was opened or not, I would expect to always see the same behaviour. Preferrably to leave the computer running, as the display is still physically connected. Is it possible to limit the lid close action to only trigger when the lid was closed not more than a few seconds ago? SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro (available in About System) KDE Plasma Version: 5.17.2 KDE Frameworks Version: 5.63.0 Qt Version: 5.13.1 ADDITIONAL INFORMATION Hardware: Surface Pro 3 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413937] New: Plasma crashed by kquitapp5 after screen corruption
https://bugs.kde.org/show_bug.cgi?id=413937 Bug ID: 413937 Summary: Plasma crashed by kquitapp5 after screen corruption Product: plasmashell Version: 5.16.5 Platform: Gentoo Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: ch...@rpgfiction.net CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.16.5) Qt Version: 5.12.5 Frameworks Version: 5.60.0 Operating System: Linux 4.19.72-gentoo-richBOOK x86_64 Distribution: "Gentoo Base System release 2.6" -- Information about the crash: - What I was doing when the application crashed: I got a long vertical stuck stripe on my screen so I resorted to restarting Plasma by "kquitapp5 plasmashell". Instead of closing, it crashed and restarted. - Unusual behavior I noticed: I often get corruption in kontact/kmail, but this was the first time in Plasma itself. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f42e471dfc0 (LWP 4506))] Thread 26 (Thread 0x7f423a7fc700 (LWP 30032)): #0 0x7f42e961611c in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f42ea500a90 in () at /usr/lib64/libQt5Core.so.5 #2 0x7f42ea5008aa in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib64/libQt5Core.so.5 #3 0x7f42ec16e56f in () at /usr/lib64/libQt5Quick.so.5 #4 0x7f42ec16e7c0 in () at /usr/lib64/libQt5Quick.so.5 #5 0x7f42ea4fa04e in () at /usr/lib64/libQt5Core.so.5 #6 0x7f42e960f408 in start_thread () at /lib64/libpthread.so.0 #7 0x7f42ea18931f in clone () at /lib64/libc.so.6 Thread 25 (Thread 0x7f4239ffb700 (LWP 30031)): #0 0x7f42e961611c in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f42ea500a90 in () at /usr/lib64/libQt5Core.so.5 #2 0x7f42ea5008aa in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib64/libQt5Core.so.5 #3 0x7f42ec16e56f in () at /usr/lib64/libQt5Quick.so.5 #4 0x7f42ec16e7c0 in () at /usr/lib64/libQt5Quick.so.5 #5 0x7f42ea4fa04e in () at /usr/lib64/libQt5Core.so.5 #6 0x7f42e960f408 in start_thread () at /lib64/libpthread.so.0 #7 0x7f42ea18931f in clone () at /lib64/libc.so.6 Thread 24 (Thread 0x7f4251ffb700 (LWP 30029)): #0 0x7f42e961611c in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f42ea500a90 in () at /usr/lib64/libQt5Core.so.5 #2 0x7f42ea5008aa in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib64/libQt5Core.so.5 #3 0x7f42ec16e56f in () at /usr/lib64/libQt5Quick.so.5 #4 0x7f42ec16e7c0 in () at /usr/lib64/libQt5Quick.so.5 #5 0x7f42ea4fa04e in () at /usr/lib64/libQt5Core.so.5 #6 0x7f42e960f408 in start_thread () at /lib64/libpthread.so.0 #7 0x7f42ea18931f in clone () at /lib64/libc.so.6 Thread 23 (Thread 0x7f4250ff9700 (LWP 30028)): #0 0x7f42e961611c in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f42ea500a90 in () at /usr/lib64/libQt5Core.so.5 #2 0x7f42ea5008aa in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib64/libQt5Core.so.5 #3 0x7f42ec16e56f in () at /usr/lib64/libQt5Quick.so.5 #4 0x7f42ec16e7c0 in () at /usr/lib64/libQt5Quick.so.5 #5 0x7f42ea4fa04e in () at /usr/lib64/libQt5Core.so.5 #6 0x7f42e960f408 in start_thread () at /lib64/libpthread.so.0 #7 0x7f42ea18931f in clone () at /lib64/libc.so.6 Thread 22 (Thread 0x7f42517fa700 (LWP 30027)): #0 0x7f42e961611c in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f42ea500a90 in () at /usr/lib64/libQt5Core.so.5 #2 0x7f42ea5008aa in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib64/libQt5Core.so.5 #3 0x7f42ec16e56f in () at /usr/lib64/libQt5Quick.so.5 #4 0x7f42ec16e7c0 in () at /usr/lib64/libQt5Quick.so.5 #5 0x7f42ea4fa04e in () at /usr/lib64/libQt5Core.so.5 #6 0x7f42e960f408 in start_thread () at /lib64/libpthread.so.0 #7 0x7f42ea18931f in clone () at /lib64/libc.so.6 Thread 21 (Thread 0x7f42527fc700 (LWP 30026)): #0 0x7f42e961611c in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f42ea500a90 in () at /usr/lib64/libQt5Core.so.5 #2 0x7f42ea5008aa in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib64/libQt5Core.so.5 #3 0x7f42ec16e56f in () at /usr/lib64/libQt5Quick.so.5 #4 0x7f42ec16e7c0 in () at /usr/lib64/libQt5Quick.so.5 #5 0x7f42ea4fa04e in () at /usr/lib64/libQt5Core.so.5 #6 0x7f42e960f408 in start_thread () at /lib64/libpthread.so.0 #7 0x7f42ea18931f in clone () at /lib64/libc.so.6 Thread 20 (Thread 0x7f42537fe700 (LWP 30006)): #0 0x7f42e961611c in pthread_cond_
[drkonqi] [Bug 383863] Absence of DrKonqi icon in a tray after same crash reappeared
https://bugs.kde.org/show_bug.cgi?id=383863 --- Comment #15 from Harald Sitter --- Yes. When A crashed too much then A has the pertinent environment variable and when A starts another process B, that environment is transferred and so B too has the environment variable. IOW any process started by another will inherit the disabled drkonqi. It's obviously a bit silly but that's a bug in (I think) KRun, which likely should clear the kcrash variables before starting a new process. Either that or kickoff doesn't use KRun in which case that bug would be in plasma-workspace somewhere. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 413938] New: Metadata is not written to all pictures in a tag hierarchy
https://bugs.kde.org/show_bug.cgi?id=413938 Bug ID: 413938 Summary: Metadata is not written to all pictures in a tag hierarchy Product: digikam Version: 6.4.0 Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Tags-Keywords Assignee: digikam-bugs-n...@kde.org Reporter: iwannaber...@gmail.com Target Milestone: --- SUMMARY This bug is derived from this tread in the mailing list: http://digikam.1695700.n4.nabble.com/digiKam-users-Hierarchical-tags-how-are-they-stored-td4709630.html In short, when creating a Tag hierarchy using existing tags by drag an dropping tags in the tree view, the metadata change is not saved to all pictures contained in the hierarchy (implying you are saving metadata to pictures, of course). The particular situation can be a bit hard to explain, so please fasten your seatbelts and I'll do my best. As you know, a picture can be part of a tag hierarchy, but not necessarily contain all tags in that hierarchy. For instance: [x] Canada [ ] Ontario [x] Toronto The picture in this case has the tags Toronto and Canada, but not Ontario, although it's part of the hierarchy and it's located there in the tag tree, and can be browsed as part of Ontario (if "Include Tag Sub-Tree" option is checked, which is by default). Usually, doing changes to a lower level tag (closer to the root) will imply that all pictures in the hierarchy will be modified as well. e.g., If I rename the tag "Ontario" to something else (e.g. "ONT"), all pictures containing Toronto will be written to reflect those changes. In the XMP metadata browser, which contains many different tag systems, changes will be reflected this way (for simplicity sake, just lightroom): lr: hierarchicalSubject = Canada|Ontario|Toronto to lr: hierarchicalSubject = Canada|ONT|Toronto This is when things work normally, but there is one situation when this is not working properly, which is why I am reporting this bug. Imagine you have pictures tagged either one of the following ways: Case 1)Case 2) [X] Ontariobut also [] Ontario [x] Toronto [x] Toronto and you create a new root-level tag called "Canada". Next, you drag and drop "Ontario" over "Canada". All pictures in Case 1 will be written and updated correctly: from lr: hierarchicalSubject = Ontario|Toronto tolr: hierarchicalSubject = Canada|Ontario|Toronto But pictures in Case 2 will NOT be updated. Their metadata will remain intact. Although changes have been correctly applied in the database. Until you manually select any of these pictures and use "Item, Write metadata to file" option. Basically, if there is a "gap" in the hierarchy where a parent tag is not "checked", the metadata update will skip these files, which will not be updated unless they are updated manually. So this is a situation where the database and the metadata have become out of sync. A symptom of this behavior can also be found in the warning when a large number of files are going to be modified (since these kind of reorganizations also imply hundreds or thousands of pictures). The number of affected pictures by the warning will be fewer than the total number of pictures included in the hierarchy. But this behavior can be easily reproduced in using just two pictures. As I said, manually selecting the affected (non-updated) files and forcing writing meta-data to files updates them with the correct hierarchy once again. SOFTWARE/OS VERSIONS Linux: Digikam 6.4.0 (stable release) appimage in Ubuntu 18.04 LTS -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 413938] Metadata is not written to all pictures in a tag hierarchy
https://bugs.kde.org/show_bug.cgi?id=413938 MarcP changed: What|Removed |Added CC||iwannaber...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 413939] New: Memory leak on file managers
https://bugs.kde.org/show_bug.cgi?id=413939 Bug ID: 413939 Summary: Memory leak on file managers Product: dolphin Version: 19.08.2 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: goli...@goliash.net CC: kfm-de...@kde.org Target Milestone: --- Created attachment 123790 --> https://bugs.kde.org/attachment.cgi?id=123790&action=edit Heaptrack screenshots SUMMARY Dolphin's heap grows in time even if it runs on background and no actions are done. The same occurs on Krusader. The memory usage grows to gigabytes after several hours. STEPS TO REPRODUCE 1. Run Dolphin 2. Wait 3. Mark memory usage 4. Wait more 5. Notice the memory usage is higher 6. Repeat steps 3-5 OBSERVED RESULT Memory usage grows in time and it doesn't stop at any time EXPECTED RESULT Memory usage should remain stable if nothing is happening with application SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.0.0-32 (available in About System) KDE Plasma Version: 5.17.2 KDE Frameworks Version: 5.63.0 Qt Version: 5.13.1 ADDITIONAL INFORMATION This has been appearing for months now. The application (Dolphin/Krusader) gets laggy in time and it has to be restarted to be able to be used. I am running KDE Neon User Ed. with HWE. Process 23931 - dolphin Summary The process dolphin (with pid 23931) is using approximately 360.5 MB of memory. It is using 350.6 MB privately, and a further 74.7 MB that is, or could be, shared with other programs. Dividing up the shared memory between all the processes sharing that memory we get a reduced shared memory usage of 9.8 MB. Adding that to the private usage, we get the above mentioned total memory footprint of 360.5 MB. Library Usage The memory usage of a process is found by adding up the memory usage of each of its libraries, plus the process's own heap, stack and any other mappings, plus the stack of its 6 threads. Private more 348808 KB [heap] 1068 KB /usr/lib/x86_64-linux-gnu/libdolphinprivate.so.5.0.0 888 KB /usr/lib/x86_64-linux-gnu/dri/i965_dri.so 852 KB /usr/lib/x86_64-linux-gnu/libkdeinit5_dolphin.so 848 KB /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5.13.1 Shared more 13812 KB/dev/shm/#153 (deleted) 4980 KB /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5.13.1 4644 KB /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5.13.1 4168 KB /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.13.1 2392 KB /usr/lib/x86_64-linux-gnu/dri/i965_dri.so -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 413940] New: Crash in DBus handling after error in XML parsing
https://bugs.kde.org/show_bug.cgi?id=413940 Bug ID: 413940 Summary: Crash in DBus handling after error in XML parsing Product: kactivitymanagerd Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ivan.cu...@kde.org Reporter: k...@davidedmundson.co.uk CC: plasma-b...@kde.org Target Milestone: --- Crashed whilst generally getting on with life my side. Seemingly from doing something with a GTK app that caused it to read some invalid XML and shutdown. The fact that it crashes in DBus stuff is probably a misleading output Application: kactivitymanagerd (kactivitymanagerd), signal: Aborted Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7efee5188e80 (LWP 641))] Thread 5 (Thread 0x7efee25f3700 (LWP 648)): #0 0x7efee84e59ef in poll () from /usr/lib/libc.so.6 #1 0x7efee58bc170 in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7efee58bc241 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #3 0x7efee8d0e518 in QEventDispatcherGlib::processEvents (this=0x7efecc000b60, flags=...) at /home/david/projects/qt/src/qtbase/src/corelib/kernel/qeventdispatcher_glib.cpp:425 #4 0x7efee8c742e3 in QEventLoop::processEvents (this=0x7efee25f2d00, flags=...) at /home/david/projects/qt/src/qtbase/src/corelib/kernel/qeventloop.cpp:138 #5 0x7efee8c7461d in QEventLoop::exec (this=0x7efee25f2d00, flags=...) at /home/david/projects/qt/src/qtbase/src/corelib/kernel/qeventloop.cpp:225 #6 0x7efee8a08fd4 in QThread::exec (this=0x56319a1b6d50) at /home/david/projects/qt/src/qtbase/src/corelib/thread/qthread.cpp:536 #7 0x5631985b9f1e in runInQThread()::Thread::run() (this=0x56319a1b6d50) at /home/david/projects/kde5/src/kde/workspace/kactivitymanagerd/src/service/Application.cpp:84 #8 0x7efee8a0be91 in QThreadPrivate::start (arg=0x56319a1b6d50) at /home/david/projects/qt/src/qtbase/src/corelib/thread/qthread_unix.cpp:342 #9 0x7efee7e0f4cf in start_thread () from /usr/lib/libpthread.so.0 #10 0x7efee84f02d3 in clone () from /usr/lib/libc.so.6 Thread 4 (Thread 0x7efee2df4700 (LWP 647)): [KCrash Handler] #6 0x7efee842cf25 in raise () from /usr/lib/libc.so.6 #7 0x7efee8416897 in abort () from /usr/lib/libc.so.6 #8 0x7efee8a00dc8 in qt_message_fatal (context=..., message=...) at /home/david/projects/qt/src/qtbase/src/corelib/global/qlogging.cpp:1894 #9 0x7efee89fd406 in QMessageLogger::fatal (this=0x7efee2df33d0, msg=0x7efee8db3d70 "ASSERT failure in %s: \"%s\", file %s, line %d") at /home/david/projects/qt/src/qtbase/src/corelib/global/qlogging.cpp:893 #10 0x7efee89f3c13 in qt_assert_x (where=0x7efee8ec5d11 "QCoreApplication::sendEvent", what=0x7efed0003018 "Cannot send events to objects owned by a different thread. Current thread 0x0x56319a1b6d70. Receiver '' (of type 'KSMServer::Private') was created in thread 0x0x56319a15e110", file=0x7efee8ec58e0 "/home/david/projects/qt/src/qtbase/src/corelib/kernel/qcoreapplication.cpp", line=575) at /home/david/projects/qt/src/qtbase/src/corelib/global/qglobal.cpp:3350 #11 0x7efee8c76dea in QCoreApplicationPrivate::checkReceiverThread (receiver=0x56319a1b6750) at /home/david/projects/qt/src/qtbase/src/corelib/kernel/qcoreapplication.cpp:575 #12 0x7efee9cdd123 in QApplication::notify (this=0x7ffc76e4f658, receiver=0x56319a1b6750, e=0x7efee2df3890) at /home/david/projects/qt/src/qtbase/src/widgets/kernel/qapplication.cpp:2879 #13 0x7efee8c77bf7 in QCoreApplication::notifyInternal2 (receiver=0x56319a1b6750, event=0x7efee2df3890) at /home/david/projects/qt/src/qtbase/src/corelib/kernel/qcoreapplication.cpp:1092 #14 0x7efee8c78604 in QCoreApplication::sendEvent (receiver=0x56319a1b6750, event=0x7efee2df3890) at /home/david/projects/qt/src/qtbase/src/corelib/kernel/qcoreapplication.cpp:1487 #15 0x7efee8cc003c in QObjectPrivate::setParent_helper (this=0x56319a1b2b60, o=0x0) at /home/david/projects/qt/src/qtbase/src/corelib/kernel/qobject.cpp:2166 #16 0x7efee8cbe136 in QObject::~QObject (this=0x7efedc0058f0, __in_chrg=) at /home/david/projects/qt/src/qtbase/src/corelib/kernel/qobject.cpp:1118 #17 0x7efee90f6152 in QDBusServiceWatcher::~QDBusServiceWatcher (this=0x7efedc0058f0, __in_chrg=) at /home/david/projects/qt/src/qtbase/src/dbus/qdbusservicewatcher.cpp:258 #18 0x7efee90f616e in QDBusServiceWatcher::~QDBusServiceWatcher (this=0x7efedc0058f0, __in_chrg=) at /home/david/projects/qt/src/qtbase/src/dbus/qdbusservicewatcher.cpp:260 #19 0x5631985b525f in std::default_delete::operator() (this=0x56319a1b6760, __ptr=0x7efedc0058f0) at /usr/bin/../lib64/gcc/x86_64-pc-linux-gnu/9.2.0/../../../../include/c++/9.2.0/bits/unique_ptr.h:81 #20 0x5631985b50d0 in std::unique_ptr >::~unique_ptr (this=0x56319a1b6760) at /usr/bin/../lib64/gcc/
[digikam] [Bug 413938] Metadata is not written to all pictures in a tag hierarchy
https://bugs.kde.org/show_bug.cgi?id=413938 --- Comment #1 from MarcP --- Created attachment 123791 --> https://bugs.kde.org/attachment.cgi?id=123791&action=edit Screen capture showing the issue This is a screen capture showing the problem with just two files. Observe how the Case2.jpg picture did not had its metadata updated when "Ontario" was moved inside "Canada", unless picture Case1.jpg, which did. Manually selecting Case2.jpg and doing "Item, Write metadata to file" finally updated the metadata. This should have been done automatically in the previous step. -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 413920] can not login
https://bugs.kde.org/show_bug.cgi?id=413920 Harald Sitter changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO CC||sit...@kde.org --- Comment #1 from Harald Sitter --- If you use kwalletmanager to inspect the content of kwallet and search for drkonqi_bugzilla, do those values 100% match the expected data? If that is the case: you can double click the drkonqi_bugzilla entry and rename it to something like drkonqi_bugzilla.bak. The next time you have to login you'll be asked to actually enter the data from scratch. Does that fix it? Do you see a difference in the drkonqi_bugzilla and drkonqi_bugzilla.bak entry after that? There's not much (=anything I can think of) that can go wrong with this, other than incorrect credentials. -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 347986] Cannot log bugs with krunner via drkonqi
https://bugs.kde.org/show_bug.cgi?id=347986 Harald Sitter changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #5 from Harald Sitter --- Drkonqi will fairly reliably detect applied updates and refuse to report bug reports against software started prior to the update. Starting with Plasma 5.18. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 290787] KMail shown "Unknown" date when Date field exist
https://bugs.kde.org/show_bug.cgi?id=290787 kavol changed: What|Removed |Added Version|1.99.0 |5.11.3 CC||ka...@seznam.cz --- Comment #25 from kavol --- (In reply to bib from comment #24) > This is starting to become the "longest bug". 7 years and counting. > > It still happens with 5.10.3. I started hitting this too :-( kmail 5.11.3 unknown dates in emails look like this: Date: Thu, 07 Nov 2019 17:04:17, -0500 note that this is probably duplicate of bug 288943 but that one looks more dead than this, so commenting here ... also bug 319906 might be duplicate -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 413143] Equalizer/Bandpass effects missing translation
https://bugs.kde.org/show_bug.cgi?id=413143 Jott changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Jott --- seems to be fixed with todays update. -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 413920] can not login
https://bugs.kde.org/show_bug.cgi?id=413920 Martin Koller changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #2 from Martin Koller --- Yes, the data is correct. I even did explicitely a copy/paste from kwalletmanager into firefox to test if the data is correct. With firefox I could login, with drkonqi not. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 413938] Metadata is not written to all pictures in a tag hierarchy
https://bugs.kde.org/show_bug.cgi?id=413938 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #2 from Maik Qualmann --- Marc, how it handles digikam is the metadata standard and completely correct. How should a tag list indicate that the tag is part of the path but not marked? The only tag list that allows this is the proprietary format of ACDsee. DigiKam can handle this format, you could push it as default all the way up in the advanced metadata settings. But I think except digiKam and ACDSee itself, nobody will use this tag list. Maik -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 413920] can not login
https://bugs.kde.org/show_bug.cgi?id=413920 Harald Sitter changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #3 from Harald Sitter --- Did you rename the entry in kwalletmanager and do a new login via drkonqi though? -- You are receiving this mail because: You are watching all bug changes.
[kmix] [Bug 127692] Wish: Volume Maximum / Cap Levels
https://bugs.kde.org/show_bug.cgi?id=127692 Alexander Potashev changed: What|Removed |Added CC||aspotas...@gmail.com Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #3 from Alexander Potashev --- *** This bug has been marked as a duplicate of bug 404387 *** -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 404387] Allow to set a maximum volume less than 100%
https://bugs.kde.org/show_bug.cgi?id=404387 Alexander Potashev changed: What|Removed |Added CC||ash...@gmail.com --- Comment #3 from Alexander Potashev --- *** Bug 127692 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 385041] When "Raise maximum volume" is checked, I can't set a volume level beyond 100% using special keyboard keys
https://bugs.kde.org/show_bug.cgi?id=385041 Alexander Potashev changed: What|Removed |Added CC||ahmed@protonmail.com --- Comment #9 from Alexander Potashev --- *** Bug 413332 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 413332] Can't raise the volume more than 100% from Audio Volume Applet
https://bugs.kde.org/show_bug.cgi?id=413332 Alexander Potashev changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED CC||aspotas...@gmail.com --- Comment #4 from Alexander Potashev --- *** This bug has been marked as a duplicate of bug 385041 *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 394750] baloo_file fills RAM and disk for hours with no visible progress
https://bugs.kde.org/show_bug.cgi?id=394750 --- Comment #11 from Igor Poboiko --- (In reply to p from comment #10) > same issue here on a fresh install of opensuse 15.1. It kills my system > completely. Makes baloo unusable. Sad. Considering that the report was open > one and half years ago I assume we don't can hope for a fix. Sad. So, which files does it choke on? What does `balooctl status` / `balooctl monitor` report? -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 294502] KMail crashes when removing an attachement from a mail
https://bugs.kde.org/show_bug.cgi?id=294502 Stefano changed: What|Removed |Added CC||erist...@cryptolab.net -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 413920] can not login
https://bugs.kde.org/show_bug.cgi?id=413920 Martin Koller changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #4 from Martin Koller --- I did, yes, as you suggested. -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 413920] can not login
https://bugs.kde.org/show_bug.cgi?id=413920 Harald Sitter changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #5 from Harald Sitter --- Hm, perhaps the URI builder is actually broken. Try changing you password on bugzilla to something with only ascii characters and see if that makes login work. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 413938] Metadata is not written to all pictures in a tag hierarchy
https://bugs.kde.org/show_bug.cgi?id=413938 --- Comment #3 from Maik Qualmann --- Can you provide 2 test files that are already tagged with just one more step to reproduce the problem? Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 413938] Metadata is not written to all pictures in a tag hierarchy
https://bugs.kde.org/show_bug.cgi?id=413938 --- Comment #4 from Maik Qualmann --- Updating a "tag"move" is an interesting task, we update the tags that are directly affected. Otherwise, we will have to recrusively update all other tags. That could be a long task. Actually, we have the maintenance tool to do such things. Maik -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 413941] New: Crash when opening Kmail
https://bugs.kde.org/show_bug.cgi?id=413941 Bug ID: 413941 Summary: Crash when opening Kmail Product: kmail2 Version: 5.11.3 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: stu...@tase.co.uk Target Milestone: --- Application: kmail (5.11.3) 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: Kmail's message window was only showing black, so I quit kmail and started it again, only now it crashes immediately on startup before any windows are displayed. The crash can be reproduced sometimes. -- Backtrace: Application: KMail (kmail), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f7f1106c680 (LWP 559274))] Thread 20 (Thread 0x7f7ec8ff9700 (LWP 559318)): #0 0x7f7f1d71907a in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f7f171d882a in base::ConditionVariable::TimedWait(base::TimeDelta const&) () from /lib64/libQt5WebEngineCore.so.5 #2 0x7f7f171d91e7 in base::WaitableEvent::TimedWaitUntil(base::TimeTicks const&) () from /lib64/libQt5WebEngineCore.so.5 #3 0x7f7f171d92e1 in base::WaitableEvent::TimedWait(base::TimeDelta const&) () from /lib64/libQt5WebEngineCore.so.5 #4 0x7f7f17199a12 in base::internal::SchedulerWorker::Delegate::WaitForWork(base::WaitableEvent*) () from /lib64/libQt5WebEngineCore.so.5 #5 0x7f7f1719c525 in base::internal::SchedulerWorker::RunWorker() () from /lib64/libQt5WebEngineCore.so.5 #6 0x7f7f1719cae4 in base::internal::SchedulerWorker::RunPooledWorker() () from /lib64/libQt5WebEngineCore.so.5 #7 0x7f7f171db75f in base::(anonymous namespace)::ThreadFunc(void*) () from /lib64/libQt5WebEngineCore.so.5 #8 0x7f7f1d7124e2 in start_thread () from /lib64/libpthread.so.0 #9 0x7f7f1ff15643 in clone () from /lib64/libc.so.6 Thread 19 (Thread 0x7f7ec97fa700 (LWP 559304)): #0 0x7f7f1d718d45 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f7f171d875a in base::ConditionVariable::Wait() () from /lib64/libQt5WebEngineCore.so.5 #2 0x7f7f171d91f8 in base::WaitableEvent::TimedWaitUntil(base::TimeTicks const&) () from /lib64/libQt5WebEngineCore.so.5 #3 0x7f7f171d929f in base::WaitableEvent::Wait() () from /lib64/libQt5WebEngineCore.so.5 #4 0x7f7f17199a28 in base::internal::SchedulerWorker::Delegate::WaitForWork(base::WaitableEvent*) () from /lib64/libQt5WebEngineCore.so.5 #5 0x7f7f1719c838 in base::internal::SchedulerWorker::RunWorker() () from /lib64/libQt5WebEngineCore.so.5 #6 0x7f7f1719cb64 in base::internal::SchedulerWorker::RunDedicatedWorker() () from /lib64/libQt5WebEngineCore.so.5 #7 0x7f7f171db75f in base::(anonymous namespace)::ThreadFunc(void*) () from /lib64/libQt5WebEngineCore.so.5 #8 0x7f7f1d7124e2 in start_thread () from /lib64/libpthread.so.0 #9 0x7f7f1ff15643 in clone () from /lib64/libc.so.6 Thread 18 (Thread 0x7f7ec9ffb700 (LWP 559303)): #0 0x7f7f1ff0aa1f in poll () from /lib64/libc.so.6 #1 0x7f7f1220e196 in poll_func () from /lib64/libpulse.so.0 #2 0x7f7f121ff801 in pa_mainloop_poll () from /lib64/libpulse.so.0 #3 0x7f7f121ffe83 in pa_mainloop_iterate () from /lib64/libpulse.so.0 #4 0x7f7f121fff30 in pa_mainloop_run () from /lib64/libpulse.so.0 #5 0x7f7f1220e0dd in thread () from /lib64/libpulse.so.0 #6 0x7f7f1154eb9c in internal_thread_func () from /usr/lib64/pulseaudio/libpulsecommon-13.0.so #7 0x7f7f1d7124e2 in start_thread () from /lib64/libpthread.so.0 #8 0x7f7f1ff15643 in clone () from /lib64/libc.so.6 Thread 17 (Thread 0x7f7eca7fc700 (LWP 559302)): #0 0x7f7f1d71907a in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f7f171d882a in base::ConditionVariable::TimedWait(base::TimeDelta const&) () from /lib64/libQt5WebEngineCore.so.5 #2 0x7f7f171d91e7 in base::WaitableEvent::TimedWaitUntil(base::TimeTicks const&) () from /lib64/libQt5WebEngineCore.so.5 #3 0x7f7f17156188 in base::MessagePumpDefault::Run(base::MessagePump::Delegate*) () from /lib64/libQt5WebEngineCore.so.5 #4 0x7f7f1717820f in base::RunLoop::Run() () from /lib64/libQt5WebEngineCore.so.5 #5 0x7f7f171aa86e in base::Thread::ThreadMain() () from /lib64/libQt5WebEngineCore.so.5 #6 0x7f7f171db75f in base::(anonymous namespace)::ThreadFunc(void*) () from /lib64/libQt5WebEngineCore.so.5 #7 0x7f7f1d7124e2 in start_thread () from /lib64/libpthread.so.0 #8 0x7f7f1ff15643 in clone () from /lib64/libc.so.6 Thread 16 (Thread 0x7f7ecaffd700 (LWP 559301)): #0 0x7f7f1d718d45 in pthread_cond_wait@@
[drkonqi] [Bug 413920] can not login
https://bugs.kde.org/show_bug.cgi?id=413920 Martin Koller changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #6 from Martin Koller --- In fact my password already only contains ASCII chars. I'll play with it ... AHA ... you nailed it! My old password contained a + char. Changing this solved the issue. As you said, there's a bug -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 413920] can not login
https://bugs.kde.org/show_bug.cgi?id=413920 Harald Sitter changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #7 from Harald Sitter --- That makes sense. + is handled a bit weirdly by QUrl. I can confirm it not working. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413937] Plasma crashed by kquitapp5 after screen corruption
https://bugs.kde.org/show_bug.cgi?id=413937 David Edmundson changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from David Edmundson --- *** This bug has been marked as a duplicate of bug 411221 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 411221] Crash in Plasma::Applet::configChanged on Applet destruction
https://bugs.kde.org/show_bug.cgi?id=411221 David Edmundson changed: What|Removed |Added CC||ch...@rpgfiction.net --- Comment #6 from David Edmundson --- *** Bug 413937 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 413620] The font in annotations (e.g. pop-up notes, highlights) can not be increased.
https://bugs.kde.org/show_bug.cgi?id=413620 --- Comment #8 from Sodre --- I'm using i3wm and almost no other KDE application other than Okular on a 4K monitor. Every other UI is OK other than okular. I tried QT_SCALE_FACTOR=2 okular for example and everything becomes bigger and with some graphical artifactsI think it would be beneficial to that Font UI for "Typrewrite" be available for any annotation type. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 413938] Metadata is not written to all pictures in a tag hierarchy
https://bugs.kde.org/show_bug.cgi?id=413938 --- Comment #5 from MarcP --- Sure, no problem. I have attached two pictures. This is their current and only metadata: Case1.jpg Case2.jpg [X] Ontario [ ] Ontario [x] Toronto [x] Toronto Now create an empty tag called "Canada" at the root of your tag tree, and then drag and drop the tag "Ontario" on "Canada". Observe how metadata is updated in Case1.jpg, but not in Case2.jpg. Now, if you click on "Item, Write metadata to file", the metadata is updated. But this last step should have been done automatically. This issue deals with how digikam tries to propagate a change across a tag tree. Usually, the whole tree is saved in each individual picture (so each image contains a "template" of its parent tags). When changing a parent tag, this change is also saved in each individual picture. However, if some intermediate tag is not "checked", changes are not propagated to that branch. Btw, I am not complaining about how digikam handles metadata. I think it does a great job considering how different software uses different standards, and it tries to integrate all of them, which is perfect. I honestly wouldn't have a problem if a picture in a tag tree would be tagged with each one of its subtags, just like lightroom does. The only consequence would be a little bit of clutter because of the amount of tags under each miniature. But in any case, the current implementation is perfectly fine and gives some more flexibility while maintaining the compatibility with other picture managers. PS: Yes, generally recursively updating a tag tree is something that can affect hundreds or thousands of pictures, and take a long time, but the user is already being warned about it when more than 100 pictures are going to be modified. The user has also the option of using sidecars, which would greatly improve the speed. I think it should be their responsibility if they want to make these big changes in their library. Actually, the recursive update is already the default behavior, except in the very particular case described in this bug report. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 413938] Metadata is not written to all pictures in a tag hierarchy
https://bugs.kde.org/show_bug.cgi?id=413938 --- Comment #7 from MarcP --- Created attachment 123794 --> https://bugs.kde.org/attachment.cgi?id=123794&action=edit Case2.jpg -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 413938] Metadata is not written to all pictures in a tag hierarchy
https://bugs.kde.org/show_bug.cgi?id=413938 --- Comment #6 from MarcP --- Created attachment 123793 --> https://bugs.kde.org/attachment.cgi?id=123793&action=edit Case1.jpg -- 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 Filip Fila changed: What|Removed |Added CC||filipfila@gmail.com --- Comment #8 from Filip Fila --- I made that patch but I can't reproduce this. I'm also using Audacious from git. Tested with both squared and non squared album art. The lock screen shows up immediately and everything works. I don't get any binding loops either. Operating System: Manjaro Linux 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.
[drkonqi] [Bug 413920] can not login
https://bugs.kde.org/show_bug.cgi?id=413920 Harald Sitter changed: What|Removed |Added Latest Commit||https://commits.kde.org/drk ||onqi/4e29b8a75635a2084d1cda ||0f1c9e8721cb8137c8 Resolution|--- |FIXED Status|CONFIRMED |RESOLVED Version Fixed In||5.17.3 --- Comment #8 from Harald Sitter --- Git commit 4e29b8a75635a2084d1cda0f1c9e8721cb8137c8 by Harald Sitter. Committed on 08/11/2019 at 12:15. Pushed by sitter into branch 'Plasma/5.17'. force-encode passwords on login QUrlQuery doesn't encode + by default while bugzilla wants it to be. This prevented passwords that include a plus from working. Simply force-encode the password string to be fully encoded. I've confirmed this working with passwords entailing spaces, plus, and percent characters, all at the same time. FIXED-IN: 5.17.3 M +17 -0src/bugzillaintegration/libbugzilla/autotests/bugzillatest.cpp M +3-1src/bugzillaintegration/libbugzilla/bugzilla.cpp https://commits.kde.org/drkonqi/4e29b8a75635a2084d1cda0f1c9e8721cb8137c8 -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 413942] New: ksysguard crashed after forcefully closing a frozen Viber
https://bugs.kde.org/show_bug.cgi?id=413942 Bug ID: 413942 Summary: ksysguard crashed after forcefully closing a frozen Viber Product: ksysguard Version: 5.16.5 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: killerm...@yahoo.com Target Milestone: --- Application: ksysguard (5.16.5) Qt Version: 5.12.4 Frameworks Version: 5.62.0 Operating System: Linux 5.3.0-19-generic x86_64 Distribution: Ubuntu 19.10 -- Information about the crash: - What I was doing when the application crashed: I sent a TERM signal to "Viber", then a KILL signal a few seconds later (Viber window was frozen). Viber windows closed on KILL. Viber processes dissapeard from the ksysguard list. Afterwards I closed the ksysguard window (everything seemed normal) and the crash handler poped up. The crash does not seem to be reproducible. -- Backtrace: Application: System Monitor (ksysguard), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fb620789f00 (LWP 5004))] Thread 3 (Thread 0x7fb617fff700 (LWP 5006)): #0 0x7fb633f61c2f in __GI___poll (fds=0x7fb6100029e0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fb62a31ea3e in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fb62a31eb73 in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fb6325bb6c3 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fb63256263b in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fb63239ba75 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fb6328e9efa in () at /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7fb63239ccc2 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fb62ab7a669 in start_thread (arg=) at pthread_create.c:479 #9 0x7fb633f6e323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7fb61f8a3700 (LWP 5005)): #0 0x7fb633f61c2f in __GI___poll (fds=0x7fb61f8a25a8, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fb62abdd917 in () at /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7fb62abdf53a in xcb_wait_for_event () at /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7fb61fe01288 in () at /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7fb63239ccc2 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fb62ab7a669 in start_thread (arg=) at pthread_create.c:479 #6 0x7fb633f6e323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7fb620789f00 (LWP 5004)): [KCrash Handler] #6 0x7fb6331f9810 in () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #7 0x7fb6331fa384 in QLabel::setText(QString const&) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #8 0x7fb6340b4223 in () at /usr/lib/x86_64-linux-gnu/libkdeinit5_ksysguard.so #9 0x7fb633cde378 in KSGRD::SensorAgent::processAnswer(char const*, int) () at /usr/lib/x86_64-linux-gnu/libksgrd.so.7 #10 0x7fb633ce5802 in () at /usr/lib/x86_64-linux-gnu/libksgrd.so.7 #11 0x7fb63258f5c8 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7fb6324df4ce in QProcess::readyReadStandardOutput(QProcess::QPrivateSignal) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7fb6324e5bd9 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x7fb6324e5f42 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x7fb63258f468 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #16 0x7fb63259c135 in QSocketNotifier::activated(int, QSocketNotifier::QPrivateSignal) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #17 0x7fb63259c491 in QSocketNotifier::event(QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #18 0x7fb6330bea86 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #19 0x7fb6330c7e00 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #20 0x7fb632563a9a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #21 0x7fb6325bc305 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #22 0x7fb62a31e84d in g_main_context_dispatch () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #23 0x7fb62a31ead0 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #24 0x7fb62a31eb73 in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #25 0x7fb6325bb6a5 in QEventDispatcherGlib::processEvents(QFlags) () at
[digikam] [Bug 413938] Metadata is not written to all pictures in a tag hierarchy
https://bugs.kde.org/show_bug.cgi?id=413938 --- Comment #8 from Maik Qualmann --- Ok, with the sample files I can reproduce it. I even think that the fix is very simple. Maik -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 413922] Krita crashes upon choosing a fill layer's color
https://bugs.kde.org/show_bug.cgi?id=413922 Boudewijn Rempt changed: What|Removed |Added Platform|Other |macOS Disk Images CC||b...@valdyas.org --- Comment #3 from Boudewijn Rempt --- The reason is that on macOS, Apple's native color selector dialog is used, which is not modal, on other platforms the color selector dialog is modal, so you cannot do anything until pressing okay in the color selector dialog. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 413922] Krita crashes upon choosing a fill layer's color
https://bugs.kde.org/show_bug.cgi?id=413922 --- Comment #4 from Boudewijn Rempt --- The reason we use the native color selector is the following: commit e6f88a3a65332d21546231349e0c36323f0c289e Author: Boudewijn Rempt Date: Thu Apr 6 11:59:44 2017 +0200 BUG:378282 Use the native color selector on OSX On OSX, the only way to pick screen colors is to use the native color selector, applications cannot access other windows than their own. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 382374] Second Screen Desktop config lost after turning off and on both DP-Displays
https://bugs.kde.org/show_bug.cgi?id=382374 omarelhaj...@gmail.com changed: What|Removed |Added Version|5.16.5 |5.17.2 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 413764] Cell not correctly displaying content with Arabic numerals in text
https://bugs.kde.org/show_bug.cgi?id=413764 --- Comment #4 from Hamidreza Jafari --- No. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 413943] New: Clicking on settings from networks, crashes it
https://bugs.kde.org/show_bug.cgi?id=413943 Bug ID: 413943 Summary: Clicking on settings from networks, crashes it Product: kde Version: unspecified Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: edin...@live.com Target Milestone: --- Application: kcmshell5 (5.12.8) Qt Version: 5.9.5 Frameworks Version: 5.44.0 Operating System: Linux 4.15.0-66-generic x86_64 Distribution: Ubuntu 18.04.3 LTS -- Information about the crash: - What I was doing when the application crashed: - Unusual behavior I noticed: Simply clicking on it when, when it tries to start a crash window comes up. I'm connected to wifi and lan in the same time currently. The crash can be reproduced every time. -- Backtrace: Application: System Settings Module (kcmshell5), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fcfa93ee800 (LWP 12575))] Thread 4 (Thread 0x7fcf8387b700 (LWP 12579)): #0 0x7fcfa617b8bd in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #1 0x7fcfa0c26b28 in g_main_context_prepare () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fcfa0c274fb in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fcfa0c276dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fcfa617b99b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fcfa61209fa in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fcfa5f3f23a in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fcfa4a7d6f5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #8 0x7fcfa5f4417d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7fcfa2ce26db in start_thread (arg=0x7fcf8387b700) at pthread_create.c:463 #10 0x7fcfa8d3e88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7fcf8cd22700 (LWP 12577)): #0 0x7fcfa0c6d664 in g_mutex_unlock () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fcfa0c264b7 in g_main_context_acquire () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fcfa0c27485 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fcfa0c276dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fcfa617b99b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fcfa61209fa in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fcfa5f3f23a in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fcfa65f8d45 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #8 0x7fcfa5f4417d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7fcfa2ce26db in start_thread (arg=0x7fcf8cd22700) at pthread_create.c:463 #10 0x7fcfa8d3e88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7fcf95df2700 (LWP 12576)): #0 0x7fcfa8d31bf9 in __GI___poll (fds=0x7fcf95df1ca8, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fcfa3311747 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7fcfa331336a in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7fcf98b9f5e9 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7fcfa5f4417d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fcfa2ce26db in start_thread (arg=0x7fcf95df2700) at pthread_create.c:463 #6 0x7fcfa8d3e88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7fcfa93ee800 (LWP 12575)): [KCrash Handler] #6 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 #7 0x7fcfa8c5d801 in __GI_abort () at abort.c:79 #8 0x7fcfa5f2efb7 in QMessageLogger::fatal(char const*, ...) const () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7fcfa4f242a7 in QSGRenderLoop::handleContextCreationFailure(QQuickWindow*, bool) () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #10 0x7fcfa4f25275 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #11 0x7fcfa4f25e9a in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #12 0x7fcfa697a3d5 in QWindow::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #13 0x7fcfa4f9a6c5 in QQuickWindow::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #14 0x7fcfa712a83c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #15 0x7fcfa7132104 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #16 0x0
[neon] [Bug 413703] "User Feedback" kcm is broken on Neon unstable edition: "Error loading QML file"
https://bugs.kde.org/show_bug.cgi?id=413703 Harald Sitter changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #4 from Harald Sitter --- The kuserfeedback job is not actually generated by the job updater, as such it seems lack wiring to the meta jobs which would trigger daily builds and as a consequence of that it hasn't been built in over a month. Note upstream/downstream jobs listed at https://build.neon.kde.org/view/3%20unstable%20%E2%98%A3%20git%20master/job/bionic_unstable_neon-packaging_kuserfeedback/ vs. for example https://build.neon.kde.org/view/3%20unstable%20%E2%98%A3%20git%20master/job/bionic_unstable_kde_svgpart/ -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 413592] Text cut off at left and right edges of <50px wide vertical panel
https://bugs.kde.org/show_bug.cgi?id=413592
Nate Graham changed:
What|Removed |Added
Version Fixed In||5.17.3
Latest Commit||https://commits.kde.org/kde
||plasma-addons/8aba24da397cc
||9ae37d9d74f46661cbbd6b3c082
Resolution|--- |FIXED
Status|CONFIRMED |RESOLVED
--- Comment #7 from Nate Graham ---
Git commit 8aba24da397cc9ae37d9d74f46661cbbd6b3c082 by Nate Graham.
Committed on 08/11/2019 at 13:53.
Pushed by ngraham into branch 'Plasma/5.17'.
[applets/weather] Reduce label minimum width to accommodate narrow vertical
panels
Summary:
The temperature label's minimum width was set high enough to overflow in a
narrow
vertical panel. This patch reduces it, without regressing the layout elsewhere.
FIXED-IN: 5.17.3
Test Plan: {F7695929}
Reviewers: #vdg, #plasma, kossebau
Subscribers: plasma-devel
Tags: #plasma
Differential Revision: https://phabricator.kde.org/D25082
M +2-2applets/weather/package/contents/ui/IconAndTextItem.qml
https://commits.kde.org/kdeplasma-addons/8aba24da397cc9ae37d9d74f46661cbbd6b3c082
--
You are receiving this mail because:
You are watching all bug changes.
[neon] [Bug 413703] "User Feedback" kcm is broken on Neon unstable edition: "Error loading QML file"
https://bugs.kde.org/show_bug.cgi?id=413703 --- Comment #5 from Jonathan Riddell --- I'm pretty certain I would have made the jobs for kuserfeedback with the jenkins_jobs_update_nci.rb script but probably run locally for only that job NO_UPDATE=1 UPDATE_INCLUDE='_kuserfeedback' ./jenkins_jobs_update_nci.rb -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406180] KWin 5.15.4+ hang regression on Nvidia Optimus
https://bugs.kde.org/show_bug.cgi?id=406180 sir phobos changed: What|Removed |Added Version|5.15.4 |5.16.5 Platform|unspecified |Kubuntu Packages Status|REOPENED|CONFIRMED CC||xapkoh...@gmail.com --- Comment #117 from sir phobos --- KDE Plasma 5.16.5 tk: Qt 5.12.4 wm: kwin dm: SDDM Distro: Ubuntu 19.10 (Eoan Ermine) laptop + hdmi-connected second monitor same bug! but what i've noticed - if at the moment it hangs you move mouse to the second screen and back - program list immediately appears and everything unhangs -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 413703] "User Feedback" kcm is broken on Neon unstable edition: "Error loading QML file"
https://bugs.kde.org/show_bug.cgi?id=413703 --- Comment #6 from Harald Sitter --- Yeah the UPDATE_INCLUDE will not update the meta jobs and the way this works is that the metajobs have a comprehensive list of jobs they need to trigger. So, missing in this case. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knewstuff] [Bug 413439] QtQuick dialog: show loading status messages in the view with a spinner or progress indicator, not using PassiveNotifications
https://bugs.kde.org/show_bug.cgi?id=413439
Dan Leinir Turthra Jensen changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REPORTED|RESOLVED
Latest Commit||https://commits.kde.org/kne
||wstuff/f1f439cbef94a700847b
||d20c49d3436851542106
--- Comment #1 from Dan Leinir Turthra Jensen ---
Git commit f1f439cbef94a700847bd20c49d3436851542106 by Dan Leinir Turthra
Jensen.
Committed on 08/11/2019 at 14:32.
Pushed by leinir into branch 'master'.
Give some more pretty feedback in NewStuff::Page while the Engine is loading
Summary:
This adds an isLoading property to KNSQuick::Engine, and that is used
to show a busy indicator (with descriptive label) when engine is loading.
Test Plan:
Without this patch: Empty content panel while loading is happening
With this patch:
{F7744725}
Reviewers: #knewstuff, #frameworks, ngraham, #vdg
Reviewed By: ngraham, #vdg
Subscribers: kde-frameworks-devel
Tags: #frameworks
Differential Revision: https://phabricator.kde.org/D25173
M +11 -4src/qtquick/qml/DialogContent.qml
M +47 -4src/qtquick/qml/Page.qml
M +20 -1src/qtquick/quickengine.cpp
M +16 -0src/qtquick/quickengine.h
https://commits.kde.org/knewstuff/f1f439cbef94a700847bd20c49d3436851542106
--
You are receiving this mail because:
You are watching all bug changes.
[Akonadi] [Bug 404990] Sign in with Google temporarily disabled for this app
https://bugs.kde.org/show_bug.cgi?id=404990 Mike Pagano changed: What|Removed |Added CC||mpag...@gentoo.org -- 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 #9 from Filip Fila --- Just an idea but can those of you that can reproduce the bug restore the 'fillMode: Image.PreserveAspectFit' line and then change the sourceSize line to be: sourceSize: Qt.size(paintedWidth, paintedHeight) and then test with /usr/lib/kscreenlocker_greet --testing -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 413944] New: Digikam crashes while album browsing
https://bugs.kde.org/show_bug.cgi?id=413944 Bug ID: 413944 Summary: Digikam crashes while album browsing Product: digikam Version: 6.3.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: general Assignee: digikam-bugs-n...@kde.org Reporter: ilmondodi...@gmail.com Target Milestone: --- Created attachment 123795 --> https://bugs.kde.org/attachment.cgi?id=123795&action=edit Screen of digiakm SUMMARY I try to use it since 6 months and can't get it work, this is why i use gthumb but i would like use digikam. Two machines bot with KDE - neon latest and updated releases. My laptop and my workstation. What happens. I open digikam, switch to the album browsing windows to select files, i start browsing and after second or third folder selection a freeze and crash. simply unusable :( I waited also some update circles but nothing changed. also Uninstal andnew install on both machines does not work STEPS TO REPRODUCE 1. Start digikam 2. when loaded go on left side in Album/file tree 3. Start searching folders by clicking and it freezes and crashes after seconds OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Kde-Neon always up to date (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Application: digiKam (digikam), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f0273213c00 (LWP 7226))] Thread 10 (Thread 0x7f01b99fc700 (LWP 7247)): #0 0x7f026e5a59f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x5649030bc210) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x5649030bc1c0, cond=0x5649030bc1e8) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x5649030bc1e8, mutex=0x5649030bc1c0) at pthread_cond_wait.c:655 #3 0x7f026f209b0b in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f026f209e19 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f0272811164 in Digikam::ActionThreadBase::run() () from /usr/lib/x86_64-linux-gnu/libdigikamcore.so.6.3.0 #6 0x7f026f202b72 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f026e59f6db in start_thread (arg=0x7f01b99fc700) at pthread_create.c:463 #8 0x7f026e8d988f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 9 (Thread 0x7f01ba9fe700 (LWP 7243)): #0 0x7f026e5a59f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x7f01bb3a1c9c) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x7f01bb3a1c48, cond=0x7f01bb3a1c70) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x7f01bb3a1c70, mutex=0x7f01bb3a1c48) at pthread_cond_wait.c:655 #3 0x7f026ee7f86c in std::condition_variable::wait(std::unique_lock&) () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #4 0x7f026934ef37 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #5 0x7f026934d75f in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #6 0x7f026934d836 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #7 0x7f02693517f8 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #8 0x7f0269375d0a in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #9 0x7f026e59f6db in start_thread (arg=0x7f01ba9fe700) at pthread_create.c:463 #10 0x7f026e8d988f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 8 (Thread 0x7f01c15ff700 (LWP 7235)): #0 0x7f0262df2664 in g_mutex_unlock () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f0262dac47d in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f0262dac6dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f026f4459db in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f026f3e5eaa in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f026f2013ca in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f026f202b72 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f026e59f6db in start_thread (arg=0x7f01c15ff700) at pthread_create.c:463 #8 0x7f026e8d988f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 7 (Thread 0x7f0203887700 (LWP 7234)): #0 0x7f026e5a59f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x7f026b538dd0) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x564900630b60, cond=0x7f026b538da8) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x7f02
[okular] [Bug 413819] highlight annotation not carried over to pdfjs
https://bugs.kde.org/show_bug.cgi?id=413819 --- Comment #12 from ghavami...@hotmail.com --- Thank you. if I find similar incongruencies in the future I will post them anywhere in particular? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 413945] New: Accesos rápidos de teclado globales
https://bugs.kde.org/show_bug.cgi?id=413945 Bug ID: 413945 Summary: Accesos rápidos de teclado globales Product: systemsettings Version: 5.14.5 Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: leif...@hotmail.com Target Milestone: --- Application: systemsettings5 (5.14.5) (Compiled from sources) Qt Version: 5.11.3 Frameworks Version: 5.54.0 Operating System: Linux 4.19.0-6-amd64 x86_64 Distribution: Debian GNU/Linux 10 (buster) -- Information about the crash: - What I was doing when the application crashed: desde el menu "accesos rapidos" accedi a "gestion de actividades" y seleccione "cambiar a la actividad por omision" y no seleccione nada, solamente presioné el boton para ingresar una configuracion de teclas y se cerro - Custom settings of the application: ninguna configuracion The crash can be reproduced every time. -- Backtrace: Application: Preferencias del sistema (systemsettings5), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f6972f34cc0 (LWP 1875))] Thread 7 (Thread 0x7f69526a7700 (LWP 1883)): #0 0x7f69721ae819 in poll () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f696fd2e136 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f696fd2e25c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f69726cb7b3 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f69726791cb in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f69724c8e96 in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f69718b5c65 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7f69724d2a87 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f69709fffa3 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #9 0x7f69721b94cf in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 6 (Thread 0x7f6953fff700 (LWP 1882)): #0 0x7f696fd77e84 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f696fd2daa0 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f696fd2e0e0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f696fd2e25c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f69726cb7b3 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f69726791cb in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f69724c8e96 in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f69718b5c65 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #8 0x7f69724d2a87 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f69709fffa3 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #10 0x7f69721b94cf in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 5 (Thread 0x7f6963237700 (LWP 1880)): #0 0x7f6970a0600c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x7f696336ef3b in ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so #2 0x7f696336edb7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so #3 0x7f69709fffa3 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #4 0x7f69721b94cf in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 4 (Thread 0x7f6968937700 (LWP 1879)): #0 0x7f6970a0600c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x7f696336ef3b in ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so #2 0x7f696336edb7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so #3 0x7f69709fffa3 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #4 0x7f69721b94cf in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 3 (Thread 0x7f696a57f700 (LWP 1878)): #0 0x7f69721ae819 in poll () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f696fd2e136 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f696fd2e25c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f69726cb7b3 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f69726791cb in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f69724c8e96 in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f6972926545 in ?? () from /lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7f69724d2a87 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f69709fffa3 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #9
[Discover] [Bug 413872] RPMs that are downloaded manually from untrusted sources can't be installed due to "bad PGP signature"
https://bugs.kde.org/show_bug.cgi?id=413872 Rex Dieter changed: What|Removed |Added CC||rdie...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 399267] hovering cursor over file displays file info in status bar for only 1 second
https://bugs.kde.org/show_bug.cgi?id=399267 Méven Car changed: What|Removed |Added CC||meve...@gmail.com --- Comment #4 from Méven Car --- I don't agree with you Nate. The problem is in the current behavior : the status bar changes its text without user interaction. This is not a good user experience and not what users would expect. Having redundant information with the information panel does not hurt, on the contrary it makes finding those very commonly used information twice as easy to find, and is important for users not using details view or the information panel. My opinion is that we should not have a timer here, simply, returning to the "normal" status text when the user hovers away from the file as one would expect. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 413946] New: crashed when tried to update from notification
https://bugs.kde.org/show_bug.cgi?id=413946 Bug ID: 413946 Summary: crashed when tried to update from notification Product: Discover Version: 5.17.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: sharky.ti...@gmail.com CC: aleix...@kde.org Target Milestone: --- Application: plasma-discover (5.17.2) Qt Version: 5.13.2 Frameworks Version: 5.63.0 Operating System: Linux 5.3.8-arch1-1 x86_64 Distribution: "Arch Linux" -- Information about the crash: - What I was doing when the application crashed: clicked 'Update' when the notification pop-up appeared. that's all -- Backtrace: Application: Центр программ Discover (plasma-discover), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fc0772b5c80 (LWP 1419))] Thread 27 (Thread 0x7fbfe4ff9700 (LWP 1637)): #0 0x7fc07adf3c45 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fc07bfd9610 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7fc07bfd9702 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7fc07dbe7e3d in () at /usr/lib/libQt5Quick.so.5 #4 0x7fc07dbe80ee in () at /usr/lib/libQt5Quick.so.5 #5 0x7fc07bfd3530 in () at /usr/lib/libQt5Core.so.5 #6 0x7fc07aded4cf in start_thread () at /usr/lib/libpthread.so.0 #7 0x7fc07bc5d2d3 in clone () at /usr/lib/libc.so.6 Thread 26 (Thread 0x7fbfe57fa700 (LWP 1636)): #0 0x7fc07adf3c45 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fc06cb0c5ec in () at /usr/lib/dri/radeonsi_dri.so #2 0x7fc06cb0c1e8 in () at /usr/lib/dri/radeonsi_dri.so #3 0x7fc07aded4cf in start_thread () at /usr/lib/libpthread.so.0 #4 0x7fc07bc5d2d3 in clone () at /usr/lib/libc.so.6 Thread 25 (Thread 0x7fbfe67fc700 (LWP 1633)): #0 0x7fc07bc529ef in poll () at /usr/lib/libc.so.6 #1 0x7fc07a222170 in () at /usr/lib/libglib-2.0.so.0 #2 0x7fc07a41 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7fc07c1f9b2c in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7fc07c1a083c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7fc07bfd2305 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7fc07bfd3530 in () at /usr/lib/libQt5Core.so.5 #7 0x7fc07aded4cf in start_thread () at /usr/lib/libpthread.so.0 #8 0x7fc07bc5d2d3 in clone () at /usr/lib/libc.so.6 Thread 24 (Thread 0x7fbfe7fff700 (LWP 1611)): #0 0x7fc07bc4e42c in read () at /usr/lib/libc.so.6 #1 0x7fc07a1d29f0 in () at /usr/lib/libglib-2.0.so.0 #2 0x7fc07a220a31 in g_main_context_check () at /usr/lib/libglib-2.0.so.0 #3 0x7fc07a222118 in () at /usr/lib/libglib-2.0.so.0 #4 0x7fc07a41 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #5 0x7fc07c1f9b2c in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7fc07c1a083c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #7 0x7fc07bfd2305 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #8 0x7fc07bfd3530 in () at /usr/lib/libQt5Core.so.5 #9 0x7fc07aded4cf in start_thread () at /usr/lib/libpthread.so.0 #10 0x7fc07bc5d2d3 in clone () at /usr/lib/libc.so.6 Thread 23 (Thread 0x7fc03d7fa700 (LWP 1609)): #0 0x7fc07bc529ef in poll () at /usr/lib/libc.so.6 #1 0x7fc07a222170 in () at /usr/lib/libglib-2.0.so.0 #2 0x7fc07a41 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7fc07c1f9b2c in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7fc07c1a083c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7fc07bfd2305 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7fc07bfd3530 in () at /usr/lib/libQt5Core.so.5 #7 0x7fc07aded4cf in start_thread () at /usr/lib/libpthread.so.0 #8 0x7fc07bc5d2d3 in clone () at /usr/lib/libc.so.6 Thread 22 (Thread 0x7fc03dffb700 (LWP 1566)): #0 0x7fc07adf3c45 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fc06cb0c5ec in () at /usr/lib/dri/radeonsi_dri.so #2 0x7fc06cb0c1e8 in () at /usr/lib/dri/radeonsi_dri.so #3 0x7fc07aded4cf in start_thread () at /usr/lib/libpthread.so.0 #4 0x7fc07bc5d2d3 in clone () at /usr/lib/libc.so.6 Thread 21 (Thread 0x7fc03e7fc700 (LWP 1565)): #0 0x7fc07adf3c45 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fc06cb0c5ec in () at /usr/lib/dri/radeonsi_dri.so #2 0x7fc06cb0c1e8 in () at /usr/lib/dri/radeonsi_dri.so #3 0x7fc07aded4cf in start_thread () at /usr/lib/libpthread.so.
[neon] [Bug 411636] krfb misses pipewire plugin
https://bugs.kde.org/show_bug.cgi?id=411636 Martin Flöser changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED --- Comment #21 from Martin Flöser --- Screenshot of krdc to krfb on Wayland: https://share.kde.org/s/cAXwLerPZcmy92j Setting to fixed as packaging wise everything gets properly installed. Verified in my virtual machine. Unfortunately also in the VM pipewire did not autostart, but that's probably a topic for a different bug and maybe resolves itself once Neon updates to Ubuntu 20.04. -- 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 #13 from Tobias Deiminger --- (In reply to ghavamikia from comment #12) > Thank you. > if I find similar incongruencies in the future I will post them anywhere in > particular? PDF parsing and rendering issues can directly go to poppler: https://gitlab.freedesktop.org/poppler/poppler/issues But don't worry, reporting to Okular in first place is absolutely fine. Both projects have a close relation and people behind are partially the same. Anyway thanks for your reports :) -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 413810] QUESTION: scrollbar margin
https://bugs.kde.org/show_bug.cgi?id=413810 pierrescal...@gmail.com changed: What|Removed |Added Resolution|WAITINGFORINFO |NOT A BUG Status|NEEDSINFO |RESOLVED --- Comment #5 from pierrescal...@gmail.com --- Updating the PapirusDevelopmentTeam/arc-kde theme with the latest version available in github fixed this issue. Thanks for your fast response. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 413928] Can't import QIF file to savings account
https://bugs.kde.org/show_bug.cgi?id=413928 Jack changed: What|Removed |Added CC||ostroffjh@users.sourceforge ||.net --- Comment #1 from Jack --- This has already been fixed: https://cgit.kde.org/kmymoney.git/commit/?h=5.0&id=1ef147cdc5bab0a84bb30f3af1b8355c38fe433e on 2019-04-19 for 5.0.4. -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 412327] Plugin library 'kde_grantlee_plugin' not found
https://bugs.kde.org/show_bug.cgi?id=412327 Michal Kec (MiK) changed: What|Removed |Added Product|neon|kaddressbook Component|general |general Assignee|neon-b...@kde.org |kdepim-b...@kde.org Version|unspecified |5.12.3 --- Comment #5 from Michal Kec (MiK) --- (In reply to Jonathan Riddell from comment #4) > what application? The Kaddressbook application obviously, as I set the Product field right initially. Dunno, why cfeck messed it with Neon, thanks for pointing me out. It is kaddressbook 19.08.3-0xneon+18.04+bionic+build43 actually. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412905] bugged "reference images" layer
https://bugs.kde.org/show_bug.cgi?id=412905 Dmitry Kazakov changed: What|Removed |Added Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/kde/ ||krita/commit/7ebb75f1311a9f ||15b31d3af0c321d044f168b617 Resolution|--- |FIXED --- Comment #3 from Dmitry Kazakov --- Git commit 7ebb75f1311a9f15b31d3af0c321d044f168b617 by Dmitry Kazakov. Committed on 08/11/2019 at 15:52. Pushed by dkazakov into branch 'master'. Fix visibility of Reference Layer and Global Selection Mask in Timeline 1) Fake nodes should not be visible in the timeline 2) Global selection should be visible depending on the GUI option, therefore we should link TimelineNodeListKeeper to KisNodeDisplayModeAdapter, so it would get proper notifications. M +13 -0libs/ui/flake/kis_node_dummies_graph.cpp M +2-0libs/ui/flake/kis_node_dummies_graph.h M +1-1libs/ui/kis_model_index_converter.cpp M +2-2libs/ui/kis_node_manager.cpp M +4-2plugins/dockers/animation/timeline_docker.cpp M +15 -2plugins/dockers/animation/timeline_frames_index_converter.cpp M +3-0plugins/dockers/animation/timeline_frames_index_converter.h M +5-2plugins/dockers/animation/timeline_frames_model.cpp M +4-1plugins/dockers/animation/timeline_frames_model.h M +46 -8plugins/dockers/animation/timeline_node_list_keeper.cpp M +14 -1plugins/dockers/animation/timeline_node_list_keeper.h https://invent.kde.org/kde/krita/commit/7ebb75f1311a9f15b31d3af0c321d044f168b617 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 413900] Untranslated placeholder "Search..." in Kirigami.SearchField on second run
https://bugs.kde.org/show_bug.cgi?id=413900 Victor Ryzhykh changed: What|Removed |Added CC||victorr2...@yandex.ru --- Comment #8 from Victor Ryzhykh --- (In reply to Méven Car from comment #7) > The string "Search..." is correctly present in > https://websvn.kde.org/*checkout*/trunk/l10n-kf5/fr/messages/kde-workspace/ > kcm_kwin_effects.po > This hints towards an issue in kirigami/Qt qml translation > propagation/loading. This line is from the old plasma, and it is commented out #~ msgid "Search..." #~ msgstr "ChercherтАж" -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412905] bugged "reference images" layer
https://bugs.kde.org/show_bug.cgi?id=412905 Dmitry Kazakov changed: What|Removed |Added Latest Commit|https://invent.kde.org/kde/ |https://invent.kde.org/kde/ |krita/commit/7ebb75f1311a9f |krita/commit/02f9b56f281a55 |15b31d3af0c321d044f168b617 |fb0f014f4fe0e0559cc8b2be88 --- Comment #4 from Dmitry Kazakov --- Git commit 02f9b56f281a55fb0f014f4fe0e0559cc8b2be88 by Dmitry Kazakov. Committed on 08/11/2019 at 15:56. Pushed by dkazakov into branch 'krita/4.2'. Fix visibility of Reference Layer and Global Selection Mask in Timeline 1) Fake nodes should not be visible in the timeline 2) Global selection should be visible depending on the GUI option, therefore we should link TimelineNodeListKeeper to KisNodeDisplayModeAdapter, so it would get proper notifications. M +13 -0libs/ui/flake/kis_node_dummies_graph.cpp M +2-0libs/ui/flake/kis_node_dummies_graph.h M +1-1libs/ui/kis_model_index_converter.cpp M +2-2libs/ui/kis_node_manager.cpp M +4-2plugins/dockers/animation/timeline_docker.cpp M +15 -2plugins/dockers/animation/timeline_frames_index_converter.cpp M +3-0plugins/dockers/animation/timeline_frames_index_converter.h M +5-2plugins/dockers/animation/timeline_frames_model.cpp M +4-1plugins/dockers/animation/timeline_frames_model.h M +46 -8plugins/dockers/animation/timeline_node_list_keeper.cpp M +14 -1plugins/dockers/animation/timeline_node_list_keeper.h https://invent.kde.org/kde/krita/commit/02f9b56f281a55fb0f014f4fe0e0559cc8b2be88 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 413810] QUESTION: scrollbar margin
https://bugs.kde.org/show_bug.cgi?id=413810 Nate Graham changed: What|Removed |Added Resolution|NOT A BUG |DOWNSTREAM -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 413947] New: Windows Client stops working correctly when it receives a notification from the phone
https://bugs.kde.org/show_bug.cgi?id=413947 Bug ID: 413947 Summary: Windows Client stops working correctly when it receives a notification from the phone Product: kdeconnect Version: unspecified Platform: MS Windows OS: MS Windows Status: REPORTED Severity: crash Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: calff...@outlook.it Target Milestone: --- Created attachment 123796 --> https://bugs.kde.org/attachment.cgi?id=123796&action=edit Picture of the error SUMMARY Windows Client (installed from the nightly binary and I'm using the build 196) stops working correctly when it receives a notification from the phone. It's not able to connect anymore until I close the application and I reopen it. The error is "Failed to execute program org.kde.kdeconnect: no such file or directory" and it's on the PC Name field. I'm attaching a screenshot. STEPS TO REPRODUCE 1. Open KDE Connect on Windows (I assume the phone is already paired) 2. Enable the mirroring of notifications. 3. Receive a notification on the phone, it can be a message from a friend. OBSERVED RESULT The phone disappears from the Windows Client and it shows an error. EXPECTED RESULT It should show the notification and... work without crashing. SOFTWARE/OS VERSIONS Windows: 10 v.1903 (build SO 18362.418) KDE Connect Nightly build 196 (even the older ones crashed) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 413944] Digikam crashes while album browsing
https://bugs.kde.org/show_bug.cgi?id=413944 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com Component|general |Database --- Comment #1 from caulier.gil...@gmail.com --- It crash while listing the number of item in an album. the database interface query the core database and print a message on the console for debugging using QtMessageLogger. The crash is located in Qt, not in digiKam. This must never happen ! So i suspect a broken Qt package installed in you Neon stuff. To confirm, just take the official digiKam 6.4.0 AppImage bundle for linux, at start it as well. This will run digiKam from the bundle that we support instead the system version. AppImage do not install files on your system, all is loaded in memory. https://download.kde.org/stable/digikam/6.4.0/ If it not crash report this problem as UPSTREAM to the Neon team... Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 391075] Can’t bind Ctrl+Backspace
https://bugs.kde.org/show_bug.cgi?id=391075 --- Comment #17 from Ahmad Samir --- Using the latest .keytab from master should give the behaviour you describe; basically the two rules concerning Backspace mean: Backspace-Ctrl: will send ^? Backspace+Ctrl: will send ^H The first rule also works for Alt, i.e. pressing Backspace without Control will always send ^?. And the bug I was talking about happens if you edit a keybiding scheme, then apply, the changes don't seem to take effect in the current konsole window (I should open a bug report to track the issue, but I need to test again). -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knewstuff] [Bug 412942] Add-on Installer's title does not follow color scheme
https://bugs.kde.org/show_bug.cgi?id=412942 Nate Graham changed: What|Removed |Added Resolution|--- |DOWNSTREAM Status|REPORTED|RESOLVED --- Comment #1 from Nate Graham --- This is a bug in your widget theme. Please report it to the theme creator. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 413928] Can't import QIF file to savings account
https://bugs.kde.org/show_bug.cgi?id=413928 Thomas Baumgart changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED Latest Commit||https://cgit.kde.org/kmymon ||ey.git/commit/?h=5.0&id=1ef ||147cdc5bab0a84bb30f3af1b835 ||5c38fe433e Version Fixed In||5.0.4 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 413922] Krita crashes upon choosing a fill layer's color
https://bugs.kde.org/show_bug.cgi?id=413922 --- Comment #5 from Jan --- Why not embed just like in other implementations and add an "Advanced / Pick Color" button on MacOS that shows this dialog? Still, this crash is very vicious and has cost me lots of hours over the time (I use fill layers a lot). So somehow this should be shielded from happening. I could try to help, if someone would give me some pointers (I am new to the krita code base and have no experience in c/c++, but have coded a lot in the past). -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 411927] Crash during initial scan
https://bugs.kde.org/show_bug.cgi?id=411927 Maik Qualmann changed: What|Removed |Added CC||ilmondodi...@gmail.com --- Comment #11 from Maik Qualmann --- *** Bug 413944 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 413944] Digikam crashes while album browsing
https://bugs.kde.org/show_bug.cgi?id=413944 Maik Qualmann changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED CC||metzping...@gmail.com --- Comment #2 from Maik Qualmann --- *** This bug has been marked as a duplicate of bug 411927 *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 413948] New: System's Preferences close
https://bugs.kde.org/show_bug.cgi?id=413948 Bug ID: 413948 Summary: System's Preferences close Product: systemsettings Version: 5.17.2 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: leandrovallejospu...@gmail.com Target Milestone: --- Application: systemsettings5 (5.17.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: I just opened the System's Preferences, and then when I select any option from the main menu of the system settings, the window closes. The crash can be reproduced every time. -- Backtrace: Application: Preferencias del sistema (systemsettings5), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fc07de66800 (LWP 24167))] Thread 6 (Thread 0x7fc051d0f700 (LWP 24175)): #0 0x7fc0793a3bf9 in __GI___poll (fds=0x7fc0480020a0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fc0728175c9 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fc0728176dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fc079cf69db in QEventDispatcherGlib::processEvents (this=0x7fc048000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7fc079c96eaa in QEventLoop::exec (this=this@entry=0x7fc051d0ed80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #5 0x7fc079ab23ca in QThread::exec (this=) at thread/qthread.cpp:531 #6 0x7fc077855cb5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7fc079ab3b72 in QThreadPrivate::start (arg=0x55bfde3c15f0) at thread/qthread_unix.cpp:360 #8 0x7fc074bd66db in start_thread (arg=0x7fc051d0f700) at pthread_create.c:463 #9 0x7fc0793b088f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7fc05271e700 (LWP 24174)): #0 0x7fc0793a3bf9 in __GI___poll (fds=0x55bfde3ab500, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fc0728175c9 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fc072817962 in g_main_loop_run () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fc053adb0e6 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #4 0x7fc07283f195 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fc074bd66db in start_thread (arg=0x7fc05271e700) at pthread_create.c:463 #6 0x7fc0793b088f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7fc052f1f700 (LWP 24173)): #0 0x7fc0793a3bf9 in __GI___poll (fds=0x55bfde37f0b0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fc0728175c9 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fc0728176dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fc072817721 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fc07283f195 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fc074bd66db in start_thread (arg=0x7fc052f1f700) at pthread_create.c:463 #6 0x7fc0793b088f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7fc05e19f700 (LWP 24170)): #0 0x7fc07285d649 in g_mutex_lock () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fc0728175af in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fc0728176dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fc079cf69db in QEventDispatcherGlib::processEvents (this=0x7fc058000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7fc079c96eaa in QEventLoop::exec (this=this@entry=0x7fc05e19ed70, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #5 0x7fc079ab23ca in QThread::exec (this=) at thread/qthread.cpp:531 #6 0x7fc07a16d0e5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7fc079ab3b72 in QThreadPrivate::start (arg=0x7fc07a3e4d80) at thread/qthread_unix.cpp:360 #8 0x7fc074bd66db in start_thread (arg=0x7fc05e19f700) at pthread_create.c:463 #9 0x7fc0793b088f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7fc06a359700 (LWP 24169)): #0 0x7fc0793a3bf9 in __GI___poll (fds=0x7fc06a358ca8, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fc07479a747 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7fc07479c36a in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7fc06d13ef00 in QXcbEventQueue::run (this=0x55bfddd4a8e0) at qxcbeventqueue.cpp:228 #4 0x7fc079ab3b72 in QThreadPrivate::star
[plasmashell] [Bug 413069] Plasma takes 3 minutes to start with thousands of wallpapers
https://bugs.kde.org/show_bug.cgi?id=413069 sp changed: What|Removed |Added CC||sp...@gmx.com --- Comment #1 from sp --- I can also confim this. As soon as you switch it to static color instead of random wallpapers the login process is much quicker and the panel, widgets, etc appear quicker. There's also his link where people mention this problem : https://forum.kde.org/viewtopic.php?f=309&t=162793 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 413938] Metadata is not written to all pictures in a tag hierarchy
https://bugs.kde.org/show_bug.cgi?id=413938 Maik Qualmann changed: What|Removed |Added Version Fixed In||7.0.0 Latest Commit||https://invent.kde.org/kde/ ||digikam/commit/4736b12a1baa ||18a8435716f6334dc515f31c116 ||0 Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #9 from Maik Qualmann --- Git commit 4736b12a1baa18a8435716f6334dc515f31c1160 by Maik Qualmann. Committed on 08/11/2019 at 17:32. Pushed by mqualmann into branch 'master'. get all recursive tags from the moved tag FIXED-IN: 7.0.0 M +2-1NEWS M +1-1core/libs/album/manager/albummanager_talbum.cpp https://invent.kde.org/kde/digikam/commit/4736b12a1baa18a8435716f6334dc515f31c1160 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 413916] Compile Error with lqr on neon
https://bugs.kde.org/show_bug.cgi?id=413916 Maik Qualmann changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |UPSTREAM Version Fixed In||7.0.0 --- Comment #2 from Maik Qualmann --- If I look at the status of the packages (https://build.neon.kde.org/) then there is not a KDE program compiling correctly. Build server installation broken? I close the bug. Maik -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 413380] Compositor crash
https://bugs.kde.org/show_bug.cgi?id=413380 ALYANBAAWI MOHAMMAD changed: What|Removed |Added CC||orcstudi...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 413880] Cannot find Plasma widgets on start page
https://bugs.kde.org/show_bug.cgi?id=413880 Nate Graham changed: What|Removed |Added Latest Commit||https://commits.kde.org/dis ||cover/11d79794b58e0852e2da1 ||568bf2babee1d372396 Resolution|--- |FIXED Version Fixed In||5.18.0 Status|CONFIRMED |RESOLVED --- Comment #6 from Nate Graham --- Git commit 11d79794b58e0852e2da1568bf2babee1d372396 by Nate Graham. Committed on 08/11/2019 at 17:50. Pushed by ngraham into branch 'master'. Perform KNS searches from the Featured page again Summary: We previously disabled this in https://bugs.kde.org/show_bug.cgi?id=399503 to improve the relevancy of the search results. However since then, searching has been improved in various other ways. For example, exact title matches are now shown first, and apps are shown before KNS entries. Therefore, it seems reasonable to re-enable KNS searches from the Featured page. FIXED-IN: 5.18.0 Test Plan: Can now find "Fokus" from a search inittated while viewing the Featured page. Reviewers: apol, #discover_software_store Subscribers: aspotashev, plasma-devel Tags: #plasma Differential Revision: https://phabricator.kde.org/D25196 M +1-1libdiscover/backends/KNSBackend/KNSBackend.cpp https://commits.kde.org/discover/11d79794b58e0852e2da1568bf2babee1d372396 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 413949] New: Docker Disappeared - Small Color Selector
https://bugs.kde.org/show_bug.cgi?id=413949 Bug ID: 413949 Summary: Docker Disappeared - Small Color Selector Product: krita Version: 4.2.7.1 Platform: Other OS: MS Windows Status: REPORTED Severity: grave Priority: NOR Component: Dockers Assignee: krita-bugs-n...@kde.org Reporter: keyth2363...@gmail.com Target Milestone: --- Created attachment 123797 --> https://bugs.kde.org/attachment.cgi?id=123797&action=edit on the left the SCS is there and on the right it is Missing SUMMARY The Docker "Small Color Selector" disappears and nothing seems to be able to bring it back besides a Krita fresh and clean install. I even have workspaces that call on it and it still does not show up. I have been playing around with Krita's shortcuts trying to find the best combination for my work flow. I might have broke something through that? because at a given point the shortcut listing disappeared too on all options, I assume this bug is somehow connected to each other. STEPS TO REPRODUCE saddley I dont know how to trigger it. it just happens on this version of Krita 4.2.7 on every install. I took pictures to show it is actually real. OBSERVED RESULT Missing: http://pasteall.org/pic/show.php?id=8b06715f826e1a516f1329d888fa1853 Found: http://pasteall.org/pic/show.php?id=b0f1c73accbc17d194d9ee1faf1a84a0 EXPECTED RESULT well to find the "Small Color Selector" in the docker list and be able to open it. SOFTWARE/OS VERSIONS Windows: 10 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 413938] Metadata is not written to all pictures in a tag hierarchy
https://bugs.kde.org/show_bug.cgi?id=413938 --- Comment #10 from MarcP --- Wow, you are the best! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 413949] Docker Disappeared - Small Color Selector
https://bugs.kde.org/show_bug.cgi?id=413949 Tymond changed: What|Removed |Added Platform|Other |MS Windows Severity|grave |normal CC||tamtamy.tym...@gmail.com --- Comment #1 from Tymond --- Does it happen to you often, or only once? If happens often, can you please save all krita*rc files (kritarc, kritashortcutsrc, kritadisplayrc, everything what you find) from the location described here: https://docs.krita.org/en/KritaFAQ.html#where-are-the-configuration-files-stored -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 413949] Docker Disappeared - Small Color Selector
https://bugs.kde.org/show_bug.cgi?id=413949 Tymond changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #2 from Tymond --- Forgot to change the status; the question is in the previous comment. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 413406] Night color only working while settings window open
https://bugs.kde.org/show_bug.cgi?id=413406 Karl Ove Hufthammer changed: What|Removed |Added CC||k...@huftis.org Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #3 from Karl Ove Hufthammer --- I can confirm this bug. I don’t even have to close the system settings; the night colors disappear even when I just return to the main system settings window. System info: Operating System: openSUSE Tumbleweed 20191104 KDE Plasma Version: 5.17.2 KDE Frameworks Version: 5.63.0 Qt Version: 5.13.1 Kernel Version: 5.3.8-1-default OS Type: 64-bit Processors: 4 × Intel® Core™ i5-2500 CPU @ 3.30GHz Memory: 15,6 GiB -- 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 #10 from sasori.n...@gmail.com --- (In reply to Filip Fila from comment #9) > Just an idea but can those of you that can reproduce the bug restore the > 'fillMode: Image.PreserveAspectFit' line and then change the sourceSize line > to be: > > sourceSize: Qt.size(paintedWidth, paintedHeight) > > and then test with /usr/lib/kscreenlocker_greet --testing Hi Filip, thanks for looking into it. I've just tested your proposed fix and I'm glad to report that it works on my system. Tested with square and non-square (3:1 ratio) cover arts. No more core dumps, no more binding loops. Manjaro (Arch) on kernel 5.3.6-1 Plasma 5.16.5 Clementine 1.3.1-771 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 413950] New: Undo Expand Canva crashes Krita
https://bugs.kde.org/show_bug.cgi?id=413950 Bug ID: 413950 Summary: Undo Expand Canva crashes Krita Product: krita Version: 4.2.7.1 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: inscript...@tepee.me Target Milestone: --- Application: krita (4.2.7.1) Qt Version: 5.12.4 Frameworks Version: 5.62.0 Operating System: Linux 5.3.0-19-generic x86_64 Distribution: Ubuntu 19.10 -- Information about the crash: - In Krita, with lots of layers, I accidentally clicked on the left side , resulting in expanding the canvas. - I undo - Crash -- Backtrace: Application: Krita (krita), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f78ca65a800 (LWP 32326))] Thread 10 (Thread 0x7f78a7727700 (LWP 32349)): #0 0x7f78ccc7fc3d in g_mutex_lock () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f78ccc33a24 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f78ccc33b73 in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f78cf7e46c3 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f78cf78b63b in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f78cf5c4a75 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f78cf5c5cc2 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f78cd3fe669 in start_thread (arg=) at pthread_create.c:479 #8 0x7f78cf230323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 9 (Thread 0x7f78a7f28700 (LWP 32347)): #0 __GI___libc_read (nbytes=16, buf=0x7f78a7f27b50, fd=24) at ../sysdeps/unix/sysv/linux/read.c:26 #1 __GI___libc_read (fd=24, buf=0x7f78a7f27b50, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:24 #2 0x7f78ccc7b63f in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f78ccc3358e in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f78ccc339e2 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f78ccc33b73 in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7f78cf7e46c3 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f78cf78b63b in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f78cf5c4a75 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f78c25f08aa in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #10 0x7f78cf5c5cc2 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7f78cd3fe669 in start_thread (arg=) at pthread_create.c:479 #12 0x7f78cf230323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 8 (Thread 0x7f78ad286700 (LWP 32346)): #0 0x7f78ccc31b16 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f78ccc3338f in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f78ccc339e2 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f78ccc33b73 in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f78cf7e46c3 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f78cf78b63b in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f78cf5c4a75 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f78c231d319 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #8 0x7f78cf5c5cc2 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f78cd3fe669 in start_thread (arg=) at pthread_create.c:479 #10 0x7f78cf230323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 7 (Thread 0x7f78af7fe700 (LWP 32344)): #0 0x7f78cf1f3d45 in __GI___nanosleep (requested_time=0x7f78af7fddc0, remaining=0x7f78af7fddc0) at ../sysdeps/unix/sysv/linux/nanosleep.c:28 #1 0x7f78cf7e3fe5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f78d0a6049a in KisTileDataSwapper::run() () from /usr/lib/x86_64-linux-gnu/libkritaimage.so.18 #3 0x7f78cf5c5cc2 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f78cd3fe669 in start_thread (arg=) at pthread_create.c:479 #5 0x7f78cf230323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 6 (Thread 0x7f78a700 (LWP 32343)): #0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 #1 0x7f78cf5c80b1 in QSemaphore::acquire(int) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f78d0a3f1ca in KisTileDataPooler::waitForWork() ()
[neon] [Bug 413951] New: Installer doesn't install updates
https://bugs.kde.org/show_bug.cgi?id=413951 Bug ID: 413951 Summary: Installer doesn't install updates Product: neon Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Live/Install images Assignee: neon-b...@kde.org Reporter: manuelcha...@gmail.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- I used an image from some months ago. The installer allowed me to connect to my wifi and I'm almost sure I told it to update while installing. After the installation finished, I removed the usb drive (which froze the live installer - had to force reboot) and then it wouldn't show the login screen at boot. I had to go to another TTY and use nmcli to connect to wifi and realized when doing pkcon update that there were tons of packages to update. After I updated that, the system worked as normal. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 413952] New: Specific Color Selector: Absence of HSL color model
https://bugs.kde.org/show_bug.cgi?id=413952 Bug ID: 413952 Summary: Specific Color Selector: Absence of HSL color model Product: krita Version: 4.2.7.1 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: wishlist Priority: NOR Component: Color models Assignee: krita-bugs-n...@kde.org Reporter: keyth2363...@gmail.com Target Milestone: --- Created attachment 123798 --> https://bugs.kde.org/attachment.cgi?id=123798&action=edit Specific Color Selector absence of HSV color Model SUMMARY I just love the HSV color model and was deeply sadden when the color docker to use it was taken out even for how buggy it was. I would love if the HSV selector would come back perhaps as a "Specific Color Selector" color model, Since making a new docker seems a bit Perhaps have presets for the "Shade Selector" that would favor certain color selection models. each time I reset Krita for some reason I have the "Advanced Color Selector" as a triangle or a square and then adjust the "Shade Selector" to a HSV color model. I love to choose it as I like but the text display of the numbers is really uneven so it really hard to see which is the one I really want too choose because the text is not align. perhaps a preset could help a faster pic of Shades for users. Not to mention have the Advance Color Selector update live as you use the "Shade Selector" EXPECTED RESULT 1) "Specific Color Selector" Docker with HSV color Model on the 2) "Advance Color Selector: Shade Selector" with Color Model presets 3) "Advance Color Selector" with live update from using the "Shade Selector" -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 413953] New: Weird installer progress bar behavior
https://bugs.kde.org/show_bug.cgi?id=413953 Bug ID: 413953 Summary: Weird installer progress bar behavior Product: neon Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Live/Install images Assignee: neon-b...@kde.org Reporter: manuelcha...@gmail.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- Using an image from some months ago, I noticed the progress bar used on the installer is in the same row as the label that says what's happening. This causes the bar to change width depending on the label width, which is pretty weird. The progress bar should have a fixed width. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 413954] New: Needless precision in night colour coordinates
https://bugs.kde.org/show_bug.cgi?id=413954 Bug ID: 413954 Summary: Needless precision in night colour coordinates Product: systemsettings Version: 5.17.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_nightcolor Assignee: plasma-b...@kde.org Reporter: k...@huftis.org CC: kwin-bugs-n...@kde.org Target Milestone: --- SUMMARY When one uses the ‘Detect Location’ feature in the night colour settings, the latitude and longitude is returned with *four* decimal digits (e.g. 60.3984). This corresponds to a precision of ~10 meters! This is far too many digits (the sunset/sunrise times don’t change much if you move ten meters). It makes people think the last digits matter, when they don’t matter at all. The number of decimal digits returned and shown should be reduced to two (corresponding to ~1 km) or one. (Even for two decimal digits, the change in the sunset/sunrise time for a change in the last digit is only a few *seconds*.) STEPS TO REPRODUCE 1. Open the night colour system settings. 2. Set the operation mode to ‘Location’. 3. Press ‘Detect Location’. OBSERVED RESULT The latitude and longitude is updated and shown with four decimal digits. EXPECTED RESULT The latitude and longitude should be updated and shown with two decimal digits (or just one). SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20191104 KDE Plasma Version: 5.17.2 KDE Frameworks Version: 5.63.0 Qt Version: 5.13.1 Kernel Version: 5.3.8-1-default OS Type: 64-bit Processors: 4 × Intel® Core™ i5-2500 CPU @ 3.30GHz Memory: 15,6 GiB -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 413952] Specific Color Selector: Absence of HSL color model
https://bugs.kde.org/show_bug.cgi?id=413952 Tymond changed: What|Removed |Added CC||tamtamy.tym...@gmail.com Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Tymond --- *** This bug has been marked as a duplicate of bug 397413 *** -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 413955] New: Wrong numbers on grub countdown
https://bugs.kde.org/show_bug.cgi?id=413955 Bug ID: 413955 Summary: Wrong numbers on grub countdown Product: neon Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: neon-b...@kde.org Reporter: manuelcha...@gmail.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- I'm not sure if this is a neon issue. But my grub's countdown (9 .. 8 .. 7 ..6) uses the same number for 8 and 0. Basically the countdown looks like: 10 .. 9 .. 0 .. 7. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 397413] Specific color selector misses HSV/HSL color space
https://bugs.kde.org/show_bug.cgi?id=397413 Tymond changed: What|Removed |Added CC||keyth2363...@gmail.com --- Comment #8 from Tymond --- *** Bug 413952 has been marked as a duplicate of this bug. *** -- 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 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk --- Comment #11 from David Edmundson --- Opened the file, one thing jumps out. implicitHeight: controlsRow.height + controlsRow.y Regardless of whether this causes the bug, this needs fixing. An implicitHeight should never depend on a current height as that's a loop An implicit size should only propagate an implicit size upwards. -- You are receiving this mail because: You are watching all bug changes.
