[krita] [Bug 420032] Random crashes on Mac (with canvas acceleration off)
https://bugs.kde.org/show_bug.cgi?id=420032 --- Comment #31 from vanyossi --- if $.3.0 deps were compiled from 4.3 branch the Qt used is: Qt Version (compiled): 5.12.7 Version (loaded): 5.12.7 You can check on Help -> Show system information for bug reports. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 420340] Icon shown by information panel is not updated when certain entries of places panel are clicked
https://bugs.kde.org/show_bug.cgi?id=420340 Méven Car changed: What|Removed |Added Latest Commit||https://commits.kde.org/dol ||phin/dcd8c646a566eff1ff2c48 ||7fb2e7abe9a53a23cb Resolution|--- |FIXED Status|CONFIRMED |RESOLVED Version Fixed In||20.08 --- Comment #2 from Méven Car --- Git commit dcd8c646a566eff1ff2c487fb2e7abe9a53a23cb by Méven Car. Committed on 01/05/2020 at 05:51. Pushed by meven into branch 'master'. Information Panel: show early icons for folders Summary: Folders previews can be long to generate. This can be noticeable by the user. This diff displays folder icons after a 100ms timer. FIXED-IN: 20.08 Test Plan: rm -r ~/.cache/thumbnails/ In dolphin open trash Click on download (or any directory with a long to generate preview). Reviewers: #dolphin, ngraham Reviewed By: #dolphin, ngraham Subscribers: kfm-devel Tags: #dolphin Differential Revision: https://phabricator.kde.org/D29204 M +15 -12 src/panels/information/informationpanelcontent.cpp https://commits.kde.org/dolphin/dcd8c646a566eff1ff2c487fb2e7abe9a53a23cb -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 420593] A sum of multiple rows selected is incorrect for securities with fraction > 100
https://bugs.kde.org/show_bug.cgi?id=420593 Thomas Baumgart changed: What|Removed |Added Latest Commit|https://commits.kde.org/kmy |https://commits.kde.org/kmy |money/c37191ada147cf18f1c74 |money/7d860a6b0f17b7903bbe1 |dab70c02a425b67104a |4ce93f798a25067f150 Version Fixed In||5.0.9 --- Comment #6 from Thomas Baumgart --- Git commit 7d860a6b0f17b7903bbe14ce93f798a25067f150 by Thomas Baumgart. Committed on 01/05/2020 at 05:40. Pushed by tbaumgart into branch '5.0'. Display transactions sum using all decimal places For a sum of multiple rows selected in the global ledger view, use the automatically determined minimum required precision to avoid truncating the value FIXED-IN: 5.0.9 (cherry picked from commit c37191ada147cf18f1c74dab70c02a425b67104a) M +1-1kmymoney/views/kgloballedgerview.cpp https://commits.kde.org/kmymoney/7d860a6b0f17b7903bbe14ce93f798a25067f150 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 420584] QIF importer ignores new investments
https://bugs.kde.org/show_bug.cgi?id=420584 Thomas Baumgart changed: What|Removed |Added Latest Commit|https://commits.kde.org/kmy |https://commits.kde.org/kmy |money/6e19d946bbf8543c7b7b0 |money/101e5f665f1e9583887c9 |2ba8b59cc7603ff0891 |7126d5c9b7674935433 Version Fixed In||5.0.9 --- Comment #2 from Thomas Baumgart --- Git commit 101e5f665f1e9583887c97126d5c9b7674935433 by Thomas Baumgart. Committed on 01/05/2020 at 05:43. Pushed by tbaumgart into branch '5.0'. Start New Investment Wizard for new securities When importing investment transactions, don't ignore previously unknown securities and instead ask user to create them using a wizard. FIXED-IN: 5.0.9 (cherry picked from commit 6e19d946bbf8543c7b7b02ba8b59cc7603ff0891) M +6-10 kmymoney/converter/mymoneystatementreader.cpp https://commits.kde.org/kmymoney/101e5f665f1e9583887c97126d5c9b7674935433 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 420761] After upgrade from Fedora 31 to 32, one of my checking accounts shows a huge negative "Cleared" balance
https://bugs.kde.org/show_bug.cgi?id=420761 --- Comment #11 from Thomas Baumgart --- Had a quick glimpse at the log. Looks like the failing MyMoneyFile test is related to/dependent on the failing MyMoneyTransactionFilter tests. @Rex: as a side note, bcooksley added some magic to run the graphical chart tests on the KDE CI infra. I have no idea what he did in detail, though. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 420837] New: change application launcher to menuZ crashing
https://bugs.kde.org/show_bug.cgi?id=420837 Bug ID: 420837 Summary: change application launcher to menuZ crashing Product: plasmashell Version: 5.16.5 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: al...@hotmail.co.jp CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.16.5) Qt Version: 5.12.4 Frameworks Version: 5.62.0 Operating System: Linux 5.3.0-51-generic x86_64 Distribution: Ubuntu 19.10 -- Information about the crash: - What I was doing when the application crashed: change application launcher to menuZ crashing then not working at all then type: rm -rf .config/*kde* then change again to menuZ then crash again... The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f29b67c3880 (LWP 11296))] Thread 10 (Thread 0x7f2986813700 (LWP 11672)): #0 0x7f29b9bb32c6 in futex_wait_cancelable (private=, expected=0, futex_word=0x560bf4462f00) at ../sysdeps/unix/sysv/linux/futex-internal.h:80 #1 0x7f29b9bb32c6 in __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x560bf4462eb0, cond=0x560bf4462ed8) at pthread_cond_wait.c:508 #2 0x7f29b9bb32c6 in __pthread_cond_wait (cond=0x560bf4462ed8, mutex=0x560bf4462eb0) at pthread_cond_wait.c:638 #3 0x7f29ba06fdbf in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f29ba06feb1 in QWaitCondition::wait(QMutex*, unsigned long) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f29bbe867b9 in () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7f29bbe86a1a in () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7f29ba069c92 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f29b9bac669 in start_thread (arg=) at pthread_create.c:479 #9 0x7f29b9cee323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 9 (Thread 0x7f2987fff700 (LWP 11449)): #0 0x7f29b9bb32c6 in futex_wait_cancelable (private=, expected=0, futex_word=0x560bf0038294) at ../sysdeps/unix/sysv/linux/futex-internal.h:80 #1 0x7f29b9bb32c6 in __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x560bf0038240, cond=0x560bf0038268) at pthread_cond_wait.c:508 #2 0x7f29b9bb32c6 in __pthread_cond_wait (cond=0x560bf0038268, mutex=0x560bf0038240) at pthread_cond_wait.c:638 #3 0x7f29ba06fdbf in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f29ba06feb1 in QWaitCondition::wait(QMutex*, unsigned long) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f29bbe867b9 in () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7f29bbe86a1a in () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7f29ba069c92 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f29b9bac669 in start_thread (arg=) at pthread_create.c:479 #9 0x7f29b9cee323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 8 (Thread 0x7f2996007700 (LWP 11368)): #0 0x7f29ba06a193 in QMutex::unlock() () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #1 0x7f29ba288d69 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f29b8a074e1 in g_main_context_check () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f29b8a07a52 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f29b8a07be3 in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f29ba288653 in QEventDispatcherGlib::processEvents(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f29ba22f5cb in QEventLoop::exec(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f29ba068a45 in QThread::exec() () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f29ba069c92 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f29b9bac669 in start_thread (arg=) at pthread_create.c:479 #10 0x7f29b9cee323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 7 (Thread 0x7f2996808700 (LWP 11367)): #0 0x7f29b9cdd2ac in __GI___libc_read (nbytes=16, buf=0x7f2996807ad0, fd=24) at ../sysdeps/unix/sysv/linux/read.c:26 #1 0x7f29b9cdd2ac in __GI___libc_read (fd=24, buf=0x7f2996807ad0, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:24 #2 0x7f29b8a4f70f in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f29b8a075fe in g_main_context_check () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f29b8a07a52 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f29b8a07be3 in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7f29ba288653 in QEventDispatcherGlib::processEvents(QFlags) () at
[Discover] [Bug 420836] New: Discover crashes from update and application launcher
https://bugs.kde.org/show_bug.cgi?id=420836 Bug ID: 420836 Summary: Discover crashes from update and application launcher Product: Discover Version: 5.12.8 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: brianedwardgr...@yahoo.com CC: aleix...@kde.org Target Milestone: --- Application: plasma-discover (5.12.8) Qt Version: 5.9.5 Frameworks Version: 5.44.0 Operating System: Linux 5.3.0-51-generic x86_64 Distribution: Ubuntu 18.04.4 LTS -- Information about the crash: - What I was doing when the application crashed: first time clicked on update icon. Second time from restart application. Third through fifth time from application launcher (Discover). - Unusual behavior I noticed: before crashing Discover couldn't see the flatpack repository. The crash can be reproduced every time. -- Backtrace: Application: Discover (plasma-discover), signal: Illegal instruction Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f79f209e800 (LWP 4234))] Thread 11 (Thread 0x7f798700 (LWP 4251)): #0 0x7f79ed66ebf9 in __GI___poll (fds=0x7f7988016800, nfds=1, timeout=63621) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f79e7e5f5c9 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f79e7e5f6dc in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f79edfb78ab in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f79edf5c90a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f79edd7b23a in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f79edd8017d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f79e9f8e6db in start_thread (arg=0x7f798700) at pthread_create.c:463 #8 0x7f79ed67b88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 10 (Thread 0x7f799cb99700 (LWP 4249)): #0 0x7f79ed66a0b4 in __GI___libc_read (fd=42, buf=0x7f799cb98cd0, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7f79e7ea42b0 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f79e7e5f0b7 in g_main_context_check () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f79e7e5f570 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f79e7e5f962 in g_main_loop_run () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f799e9d8276 in () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #6 0x7f79e7e87175 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7f79e9f8e6db in start_thread (arg=0x7f799cb99700) at pthread_create.c:463 #8 0x7f79ed67b88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 9 (Thread 0x7f799d39a700 (LWP 4248)): #0 0x7f79ed66ebf9 in __GI___poll (fds=0x560d54974c90, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f79e7e5f5c9 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f79e7e5f6dc in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f79e7e5f721 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f79e7e87175 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f79e9f8e6db in start_thread (arg=0x7f799d39a700) at pthread_create.c:463 #6 0x7f79ed67b88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 8 (Thread 0x7f79b6577700 (LWP 4243)): #0 0x7f79e9f949f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x7f79a80141f0) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f79e9f949f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x7f79a80141a0, cond=0x7f79a80141c8) at pthread_cond_wait.c:502 #2 0x7f79e9f949f3 in __pthread_cond_wait (cond=0x7f79a80141c8, mutex=0x7f79a80141a0) at pthread_cond_wait.c:655 #3 0x7f79edd815ab in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f79edd79c1b in QSemaphore::acquire(int) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f79edf8d868 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f79eb5eedf2 in () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #7 0x7f79eb5efd4c in () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #8 0x7f79edf8d555 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f79eb5edeb2 in () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #10 0x7f79eb54f23f in () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #11 0x7f79eb5506cc in () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #12 0x7f79edf8d555 in
[lattedock] [Bug 420581] Right click doesn't work any more
https://bugs.kde.org/show_bug.cgi?id=420581 Nicolas Girard changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 420581] Right click doesn't work any more
https://bugs.kde.org/show_bug.cgi?id=420581 --- Comment #1 from Nicolas Girard --- Problem doesn't arise any longer after latest `apt upgrade`. Closing. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 411668] Different mouse pointer speed on wayland with the same settings
https://bugs.kde.org/show_bug.cgi?id=411668 --- Comment #4 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 419340] Docker Titlebars don't hide anymore
https://bugs.kde.org/show_bug.cgi?id=419340 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #5 from Bug Janitor Service --- Thanks for your comment! Automatically switching the status of this bug to REPORTED so that the KDE team knows that the bug is ready to get confirmed. In the future you may also do this yourself when providing needed information. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 420825] I eliminate color pixels and the saving I am forced to pick a pixel color
https://bugs.kde.org/show_bug.cgi?id=420825 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #14 from Bug Janitor Service --- Thanks for your comment! Automatically switching the status of this bug to REPORTED so that the KDE team knows that the bug is ready to get confirmed. In the future you may also do this yourself when providing needed information. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 419871] Configuring indentation rules for JSON results in crash
https://bugs.kde.org/show_bug.cgi?id=419871 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 419487] K3B crash when open a iso file by "right click mouse menu open" any iso file.
https://bugs.kde.org/show_bug.cgi?id=419487 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 420829] "Send to device via KDE Connect" does not work in Ubuntu when upgraded to 20.04 (Nautilus)
https://bugs.kde.org/show_bug.cgi?id=420829 Nate Graham changed: What|Removed |Added Assignee|n...@kde.org|albertv...@gmail.com Component|general |common Product|kdenetwork-filesharing |kdeconnect -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 420835] New: Plasmashell crashes on mouse hover over panel during drag & drop
https://bugs.kde.org/show_bug.cgi?id=420835 Bug ID: 420835 Summary: Plasmashell crashes on mouse hover over panel during drag & drop Product: plasmashell Version: 5.18.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: xnw...@yandex.com Target Milestone: 1.0 SUMMARY Plasmashell crashes whenever the mouse starts/stops hovering over the panel while dragging files. STEPS TO REPRODUCE 1. Log into a wayland session 2. Open Dolphin, drag a file from any directory with the left mouse button held down 3. Keep the mouse button held down, repeatedly hover over and leave the panel 4. A visual lag can be observed if plasmashell does not crash, keep hovering the file over the panel until plasma crashes OBSERVED RESULT Plasmashell crashes EXPECTED RESULT Plasmashell does not crash SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Tumbleweed 20200428 (available in About System) KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.69.0 Qt Version: 5.14.1 ADDITIONAL INFORMATION Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fc112c5e440 (LWP 2631))] Thread 13 (Thread 0x7fc0d6bfd700 (LWP 3011)): #0 0x7fc1143fc795 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fc114f801db in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /usr/lib64/libQt5Core.so.5 #2 0x7fc114f80299 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib64/libQt5Core.so.5 #3 0x7fc116c8d59f in QSGRenderThreadEventQueue::takeEvent (wait=true, this=0x55733af1ecb8) at /usr/src/debug/libqt5-qtdeclarative-5.14.1-1.3.x86_64/src/quick/scenegraph/qsgthreadedrenderloop.cpp:255 #4 QSGRenderThread::processEventsAndWaitForMore (this=this@entry=0x55733af1ec20) at /usr/src/debug/libqt5-qtdeclarative-5.14.1-1.3.x86_64/src/quick/scenegraph/qsgthreadedrenderloop.cpp:905 #5 0x7fc116c8d819 in QSGRenderThread::run (this=0x55733af1ec20) at /usr/src/debug/libqt5-qtdeclarative-5.14.1-1.3.x86_64/src/quick/scenegraph/qsgthreadedrenderloop.cpp:1000 #6 0x7fc114f7a698 in ?? () from /usr/lib64/libQt5Core.so.5 #7 0x7fc1143f5efa in start_thread () from /lib64/libpthread.so.0 #8 0x7fc114c083bf in clone () from /lib64/libc.so.6 Thread 12 (Thread 0x7fc0d7fff700 (LWP 2847)): #0 0x7fc1143fc795 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fc114f801db in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /usr/lib64/libQt5Core.so.5 #2 0x7fc114f80299 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib64/libQt5Core.so.5 #3 0x7fc116c8d59f in QSGRenderThreadEventQueue::takeEvent (wait=true, this=0x557337691578) at /usr/src/debug/libqt5-qtdeclarative-5.14.1-1.3.x86_64/src/quick/scenegraph/qsgthreadedrenderloop.cpp:255 #4 QSGRenderThread::processEventsAndWaitForMore (this=this@entry=0x5573376914e0) at /usr/src/debug/libqt5-qtdeclarative-5.14.1-1.3.x86_64/src/quick/scenegraph/qsgthreadedrenderloop.cpp:905 #5 0x7fc116c8d819 in QSGRenderThread::run (this=0x5573376914e0) at /usr/src/debug/libqt5-qtdeclarative-5.14.1-1.3.x86_64/src/quick/scenegraph/qsgthreadedrenderloop.cpp:1000 #6 0x7fc114f7a698 in ?? () from /usr/lib64/libQt5Core.so.5 #7 0x7fc1143f5efa in start_thread () from /lib64/libpthread.so.0 #8 0x7fc114c083bf in clone () from /lib64/libc.so.6 Thread 11 (Thread 0x7fc0dd48b700 (LWP 2844)): #0 0x7fc114f7ab8c in QMutex::lock() () from /usr/lib64/libQt5Core.so.5 #1 0x7fc1151a72d5 in ?? () from /usr/lib64/libQt5Core.so.5 #2 0x7fc113709449 in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #3 0x7fc113709982 in ?? () from /usr/lib64/libglib-2.0.so.0 #4 0x7fc113709aff in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #5 0x7fc1151a6c0b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #6 0x7fc11514eb9b in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #7 0x7fc114f795ce in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #8 0x7fc114f7a698 in ?? () from /usr/lib64/libQt5Core.so.5 #9 0x7fc1143f5efa in start_thread () from /lib64/libpthread.so.0 #10 0x7fc114c083bf in clone () from /lib64/libc.so.6 Thread 10 (Thread 0x7fc0ddca5700 (LWP 2840)): #0 0x7fc11370609d in ?? () from /usr/lib64/libglib-2.0.so.0 #1 0x7fc113707ab5 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7fc11370934f in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #3 0x7fc113709982 in ?? () from /usr/lib64/libglib-2.0.so.0 #4 0x7fc113709aff in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #5 0x7fc1151a6c0b in QEventDispatcherGlib::processEvents(QFlags) () from
[plasmashell] [Bug 420833] Plasma crashes when speakers and internal microphone are muted or unmuted
https://bugs.kde.org/show_bug.cgi?id=420833 Patrick Silva changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Patrick Silva --- *** This bug has been marked as a duplicate of bug 420801 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 420801] Muting audio device in the system tray applet crash plasma
https://bugs.kde.org/show_bug.cgi?id=420801 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com --- Comment #7 from Patrick Silva --- *** Bug 420833 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 420820] Konsole 20.04.0 crashes on start
https://bugs.kde.org/show_bug.cgi?id=420820 Kurt Hindenburg changed: What|Removed |Added CC||a.samir...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 420820] Konsole 20.04.0 crashes on start
https://bugs.kde.org/show_bug.cgi?id=420820 --- Comment #2 from Kurt Hindenburg --- Ahmad, could you look at this? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 419844] Dolphin crashes when trying to create a file from the right-click menu
https://bugs.kde.org/show_bug.cgi?id=419844 arshad.husa...@gmail.com changed: What|Removed |Added Assignee|arshad.husa...@gmail.com|dolphin-bugs-n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 415762] Exiting the session in a Yakuake tab sometimes crash Yakuake
https://bugs.kde.org/show_bug.cgi?id=415762 Lê Hoàng Phương changed: What|Removed |Added CC||herophuon...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 420786] Password request window should be application-modal
https://bugs.kde.org/show_bug.cgi?id=420786 --- Comment #2 from Nate Graham --- Anyway I've known people to get emotional about system-modal diaogs, but not really about app-modal ones. Discover only has one window and you can't really do anything else while it's waiting for your password anyway so I don't really see any way for a non-cranky person to legitimately complain about it. :) -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 420786] Password request window should be application-modal
https://bugs.kde.org/show_bug.cgi?id=420786 Nate Graham changed: What|Removed |Added CC||n...@kde.org Status|REPORTED|CONFIRMED Summary|[WHISHLIST] Password|Password request window |request window should be|should be application-modal |"modal" | Ever confirmed|0 |1 Keywords||usability --- Comment #1 from Nate Graham --- Makes sense to me. It's not like you can do anything else with Discover while it's open anyway. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 418662] Some system tray icons seem to choose the wrong color/become invisible
https://bugs.kde.org/show_bug.cgi?id=418662 --- Comment #11 from Patrick Silva --- Created attachment 128053 --> https://bugs.kde.org/attachment.cgi?id=128053=edit screen recording on Neon unstable it happens almost always when I open Gwenview while Media Player applet is not in use. I'm attaching a screen recording. Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.18.80 KDE Frameworks Version: 5.70.0 Qt Version: 5.14.2 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 420834] New: vex amd64->IR: unhandled instruction bytes: 0x62 0xF1 0x7D 0x8 0xEF 0xC0 0x62 0xF1 0xFD 0x28
https://bugs.kde.org/show_bug.cgi?id=420834 Bug ID: 420834 Summary: vex amd64->IR: unhandled instruction bytes: 0x62 0xF1 0x7D 0x8 0xEF 0xC0 0x62 0xF1 0xFD 0x28 Product: valgrind Version: 3.15 SVN Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: vex Assignee: jsew...@acm.org Reporter: aymaneltems...@hotmail.com Target Milestone: --- SUMMARY While running my application with valgrind, it crashes with SIGILL - Illegal instruction signal and the following errors. Running without valgrind does not cause any problems. I use CRoaring lib and it fails in roaring_bitmap_or_many function. vex amd64->IR: unhandled instruction bytes: 0x62 0xF1 0x7D 0x8 0xEF 0xC0 0x62 0xF1 0xFD 0x28 vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0 vex amd64->IR: VEX=0 VEX.L=0 VEX.n=0x0 ESC=NONE vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0 ==15525== valgrind: Unrecognised instruction at address 0x48e884d. ==15525==at 0x48E884D: _mm256_setzero_si256 (avxintrin.h:1237) ==15525==by 0x48E884D: avx2_harley_seal_popcount256 (bitset_util.h:288) ==15525==by 0x48F8661: bitset_container_compute_cardinality (bitset.c:154) ==15525==by 0x4909119: container_repair_after_lazy (containers.h:331) ==15525==by 0x4912D2A: roaring_bitmap_repair_after_lazy (roaring.c:2437) ==15525==by 0x490E1D5: roaring_bitmap_or_many (roaring.c:627) ==15525==by 0x4AE55E: ... ==15525== ==15525== Process terminating with default action of signal 4 (SIGILL): dumping core ==15525==at 0x4C635A9: raise (raise.c:46) ==15525==by 0x4F8AEB: ... ==15525==by 0x4C6372F: ??? (in /lib/x86_64-linux-gnu/libpthread-2.28.so) ==15525==by 0x48E884C: avx2_harley_seal_popcount256 (bitset_util.h:287) ==15525== ==15525== HEAP SUMMARY: ==15525== in use at exit: 168,225,692 bytes in 409 blocks ==15525== total heap usage: 18,662 allocs, 18,253 frees, 5,053,043,543 bytes allocated ==15525== ==15525== LEAK SUMMARY: ==15525==definitely lost: 0 bytes in 0 blocks ==15525==indirectly lost: 0 bytes in 0 blocks ==15525== possibly lost: 0 bytes in 0 blocks ==15525==still reachable: 168,225,692 bytes in 409 blocks ==15525== suppressed: 0 bytes in 0 blocks ==15525== Rerun with --leak-check=full to see details of leaked memory ==15525== ==15525== For lists of detected and suppressed errors, rerun with: -s ==15525== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) Illegal instruction Linux 4.15.0-1052-aws #54-Ubuntu SMP Tue Oct 1 15:43:26 UTC 2019 x86_64 GNU/Linux Using Valgrind-3.15.0-608cb11914-20190413 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 420833] New: Plasma crashes when speakers and internal microphone are muted or unmuted
https://bugs.kde.org/show_bug.cgi?id=420833 Bug ID: 420833 Summary: Plasma crashes when speakers and internal microphone are muted or unmuted Product: plasmashell Version: master Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: bugsefor...@gmx.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.18.80) Qt Version: 5.14.2 Frameworks Version: 5.70.0 Operating System: Linux 5.3.0-45-generic x86_64 Windowing system: X11 Distribution: KDE neon Unstable Edition -- Information about the crash: - What I was doing when the application crashed: click on sound icon in systray mute or unmute the speakers or the internal microphone (I'm using a laptop) by clicking on the respective icon. The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Content of s_kcrashErrorMessage: [Current thread is 1 (Thread 0x7fb385b96c80 (LWP 17928))] [KCrash Handler] #6 0x7fb38424a810 in Plasma::Svg::setColorGroup(Plasma::Theme::ColorGroup) () at /usr/lib/x86_64-linux-gnu/libKF5Plasma.so.5 #7 0x7fb37fbb6357 in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x7fff1bc7fc40, r=0x556df4a2ca20, this=) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #8 0x7fb37fbb6357 in doActivate(QObject*, int, void**) (sender=0x556df4a16840, signal_index=37, argv=0x7fff1bc7fc40) at kernel/qobject.cpp:3870 #9 0x7fb37fbb0c12 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=, m=m@entry=0x7fb35925c8a0 , local_signal_index=local_signal_index@entry=7, argv=argv@entry=0x0) at kernel/qobject.cpp:3930 #10 0x7fb3590420e3 in IconItem::colorGroupChanged() (this=) at ./obj-x86_64-linux-gnu/src/declarativeimports/core/corebindingsplugin_autogen/EWIEGA46WW/moc_iconitem.cpp:447 #11 0x7fb359036423 in IconItem::setColorGroup(Plasma::Theme::ColorGroup) (this=, group=) at ./src/declarativeimports/core/iconitem.cpp:415 #12 0x7fb359044080 in IconItem::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) (_o=, _c=, _id=, _a=) at ./obj-x86_64-linux-gnu/src/declarativeimports/core/corebindingsplugin_autogen/EWIEGA46WW/moc_iconitem.cpp:323 #13 0x7fb383507888 in QQmlPropertyData::writeProperty(QObject*, void*, QFlags) const (flags=..., value=, target=, this=) at ../../include/QtQml/5.14.2/QtQml/private/../../../../../src/qml/qml/qqmlpropertydata_p.h:286 #14 0x7fb383507888 in GenericBinding<2>::doStore(int, QQmlPropertyData const*, QFlags) const (flags=..., pd=, value=, this=) at qml/qqmlbinding.cpp:334 #15 0x7fb383507888 in GenericBinding<2>::write(QV4::Value const&, bool, QFlags) (this=0x556df4a171d0, result=..., isUndefined=, flags=...) at qml/qqmlbinding.cpp:302 #16 0x7fb38350844a in QQmlNonbindingBinding::doUpdate(QQmlJavaScriptExpression::DeleteWatcher const&, QFlags, QV4::Scope&) (this=0x556df4a171d0, watcher=..., flags=..., scope=...) at qml/qqmlbinding.cpp:250 #17 0x7fb383505032 in QQmlBinding::update(QFlags) (this=0x556df4a171d0, flags=...) at qml/qqmlbinding.cpp:186 #18 0x7fb3834de322 in QQmlNotifier::emitNotify(QQmlNotifierEndpoint*, void**) (endpoint=, a=a@entry=0x0) at qml/qqmlnotifier.cpp:104 #19 0x7fb38348c119 in QQmlData::signalEmitted(QAbstractDeclarativeData*, QObject*, int, void**) (object=0x556df4a11720, index=, a=0x0) at qml/qqmlengine.cpp:858 #20 0x7fb37fbb5f94 in doActivate(QObject*, int, void**) (sender=0x556df4a11720, signal_index=51, argv=argv@entry=0x0) at kernel/qobject.cpp:3762 #21 0x7fb37fbb0de9 in QMetaObject::activate(QObject*, int, int, void**) (sender=, signalOffset=, local_signal_index=, argv=argv@entry=0x0) at kernel/qobject.cpp:3943 #22 0x7fb383485fe5 in QQmlVMEMetaObject::activate(QObject*, int, void**) (this=, object=, index=, args=args@entry=0x0) at qml/qqmlvmemetaobject.cpp:1212 #23 0x7fb383486188 in QQmlVMEMetaObjectEndpoint::tryConnect() (this=0x556df4a2d740) at qml/qqmlvmemetaobject.cpp:155 #24 0x7fb3834de322 in QQmlNotifier::emitNotify(QQmlNotifierEndpoint*, void**) (endpoint=, a=a@entry=0x0) at qml/qqmlnotifier.cpp:104 #25 0x7fb38348c119 in QQmlData::signalEmitted(QAbstractDeclarativeData*, QObject*, int, void**) (object=0x556df4a13450, index=, a=0x0) at qml/qqmlengine.cpp:858 #26 0x7fb37fbb5f94 in doActivate(QObject*, int, void**) (sender=0x556df4a13450, signal_index=30, argv=0x0) at kernel/qobject.cpp:3762 #27 0x7fb37fbb0c12 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=sender@entry=0x556df4a13450, m=m@entry=0x7fb383fa5c40 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x0) at kernel/qobject.cpp:3930 #28 0x7fb383b734d0 in
[krita] [Bug 420032] Random crashes on Mac (with canvas acceleration off)
https://bugs.kde.org/show_bug.cgi?id=420032 --- Comment #30 from Yu-Hsuan Lai --- This particular bug doesn't seem to happen with 4.3.0. It might just be a placebo effect though. Does 4.3.0(2bae978) uses a different Qt version than 4.2.9? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 419844] Dolphin crashes when trying to create a file from the right-click menu
https://bugs.kde.org/show_bug.cgi?id=419844 arshad.husa...@gmail.com changed: What|Removed |Added CC||arshad.husa...@gmail.com Assignee|dolphin-bugs-n...@kde.org |arshad.husa...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 420832] New: PARROT OS AND MEGASYNC
https://bugs.kde.org/show_bug.cgi?id=420832 Bug ID: 420832 Summary: PARROT OS AND MEGASYNC Product: dolphin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: plugins: git Assignee: sebast...@sebastian-doerner.de Reporter: eneshuoffic...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Created attachment 128052 --> https://bugs.kde.org/attachment.cgi?id=128052=edit no description SUMMARY STEPS TO REPRODUCE 1. Downloaded Megasync for debian 9 using Parrot OS 5.5.5 2. chmod +x 3. dpkg -i pacakge_name gives error OBSERVED RESULT EXPECTED RESULT Have Megasync Installed on my harddrive -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409661] Brush properties widget (on the right) in Popup Palette becomes smaller and smaller
https://bugs.kde.org/show_bug.cgi?id=409661 Lynx3d changed: What|Removed |Added Latest Commit||https://invent.kde.org/kde/ ||krita/commit/93bdd1d6f56092 ||e2f229dc6202aa068f4526ddbc Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #7 from Lynx3d --- Git commit 93bdd1d6f56092e2f229dc6202aa068f4526ddbc by Mathias Wein. Committed on 01/05/2020 at 01:06. Pushed by mwein into branch 'master'. Fix Brush HUD width adjustment This time hopefully for real. There are two issues to bypass: 1) Layouts don't just instantly calculate new dimension as you modify them, it would be way too expensive, so Qt has a delayed pass for that in the event loop. So we need to wait until this has happened for the properties layout before resizing. 2) QScrollArea has a pretty broken sizeHint() implementation. It will just not give us a useful size that we could use. See also QTBUG-76256 and QTBUG-58447 The most sane solution I could come up with is to install the HUD widget as event filter for the content widget of the scroll area, and catch the LayoutRequest event. This event gets sent by the layout to the parent widget to indicate its new dimension are now available. This is what Q(Abstract)ScrollArea does internally anyway, so even fixing the sizeHint and waiting for the event to trigger again on the outer layout just costs another loop iteration and results in multiple screen updates. Since we need to adjust the width a few levels up, we need to calculate the margins our self, but the layout is not overly complex luckily. M +17 -1libs/ui/brushhud/kis_brush_hud.cpp M +1-0libs/ui/brushhud/kis_brush_hud.h https://invent.kde.org/kde/krita/commit/93bdd1d6f56092e2f229dc6202aa068f4526ddbc -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 305072] Animated GIF is some milliseconds too slow
https://bugs.kde.org/show_bug.cgi?id=305072 Toby Fox changed: What|Removed |Added CC||toby...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 420831] New: Dolphin can't copy folders to another directory
https://bugs.kde.org/show_bug.cgi?id=420831 Bug ID: 420831 Summary: Dolphin can't copy folders to another directory Product: dolphin Version: 20.04.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: techxga...@outlook.com CC: kfm-de...@kde.org Target Milestone: --- Created attachment 128051 --> https://bugs.kde.org/attachment.cgi?id=128051=edit Screenshot of ~/Music & ~/Downloads/iTunes/iTunes Media/Music SUMMARY There's a pop-up that says "An older item exists" when it doesn't exist at all. In fact it For example, I'm moving a folder in ~/Downloads/iTunes/Music to ~/Music, and that will pop-up. STEPS TO REPRODUCE 1. Copy a folder from dir1 2. Paste to dir2 OBSERVED RESULT Pop-up that says "An older item exists", and will ask me to rename the folder EXPECTED RESULT Folder should be able to copy like normal SOFTWARE/OS VERSIONS Operating System: KDE neon Testing Edition KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.70.0 Qt Version: 5.14.2 Kernel Version: 5.3.0-51-generic OS Type: 64-bit Processors: 4 × Intel® Core™ i5-6500 CPU @ 3.20GHz Memory: 15.6 GiB of RAM ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 420825] I eliminate color pixels and the saving I am forced to pick a pixel color
https://bugs.kde.org/show_bug.cgi?id=420825 --- Comment #13 from rfja...@yahoo.com --- Thank you for your time and assistance! I deeply appreciate it! I have had 3 heart attacks, 3 strokes, 2 open heart surgeries. At age 72 I know the Lord is not finished with me yet! I send you a recording of me a few years ago in the Local Mall. Thank you for all you help! https://www.dropbox.com/s/3alrbocqtsmskr0/Love%20was%20When%281%29.mp4?dl=0 On Thursday, April 30, 2020, 07:16:02 PM EDT, Tymond wrote: https://bugs.kde.org/show_bug.cgi?id=420825 --- Comment #12 from Tymond --- Created attachment 128049 --> https://bugs.kde.org/attachment.cgi?id=128049=edit Screenshot of the rose and random strokes behind it on a new layer The outline file contains the rose with transparency. See the screenshot; there are transparency checkers and if I add a new layer behind it and paint on it, it is visible. Not all white areas are transparent though; to get all of them transparent, you can use Filter -> Colors -> Color to Alpha. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 420830] New: Highlight / select the subfolder after unpacking
https://bugs.kde.org/show_bug.cgi?id=420830 Bug ID: 420830 Summary: Highlight / select the subfolder after unpacking Product: dolphin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: bakarichar...@outlook.hu CC: kfm-de...@kde.org Target Milestone: --- Unpacking a compressed archive is a very common daily operation. I often use the "extract archive, autodetect subfolder" function for that but after doing it I need to figure out and start typing the folder's name to find it. It would be a lovely feature if the file manager selected it automatically. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[kdenetwork-filesharing] [Bug 420829] New: "Send to device via KDE Connect" does not work in Ubuntu when upgraded to 20.04 (Nautilus)
https://bugs.kde.org/show_bug.cgi?id=420829 Bug ID: 420829 Summary: "Send to device via KDE Connect" does not work in Ubuntu when upgraded to 20.04 (Nautilus) Product: kdenetwork-filesharing Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: n...@kde.org Reporter: cyber...@gmx.us Target Milestone: --- After upgrading Ubuntu 19.10 to 20.04, the "Send to device via KDE Connect" is missing from File Manager. Removed and reinstalled KDEconnect. Same results. Ubuntu 20.04 LTS 64-bit GNOME Version 3.36.1 X11 -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 328922] Add separate history for each text field
https://bugs.kde.org/show_bug.cgi?id=328922 Toni Asensi Esteve changed: What|Removed |Added CC||toni.ase...@kdemail.net --- Comment #1 from Toni Asensi Esteve --- For the "File -> New directory" dialog, there's a proposal at https://phabricator.kde.org/D29316 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 420775] Bad error message when opening .epub files without .epub support
https://bugs.kde.org/show_bug.cgi?id=420775 --- Comment #2 from Volker Weißmann --- I opened a bug in the Arch Linux bug tracker: https://bugs.archlinux.org/task/66485 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 420825] I eliminate color pixels and the saving I am forced to pick a pixel color
https://bugs.kde.org/show_bug.cgi?id=420825 --- Comment #12 from Tymond --- Created attachment 128049 --> https://bugs.kde.org/attachment.cgi?id=128049=edit Screenshot of the rose and random strokes behind it on a new layer The outline file contains the rose with transparency. See the screenshot; there are transparency checkers and if I add a new layer behind it and paint on it, it is visible. Not all white areas are transparent though; to get all of them transparent, you can use Filter -> Colors -> Color to Alpha. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 420825] I eliminate color pixels and the saving I am forced to pick a pixel color
https://bugs.kde.org/show_bug.cgi?id=420825 --- Comment #6 from rfja...@yahoo.com --- Here are the files you asked for: On Thursday, April 30, 2020, 05:41:39 PM EDT, Tymond wrote: https://bugs.kde.org/show_bug.cgi?id=420825 --- Comment #5 from Tymond --- Can you please make a screenshot of your Krita window before saving (so I can see the image with transparency (removed background) inside Krita) and then another one when you are asked about PNG settings? (First you're asked for the name of the file, and then there are settings, I mean the dialog with settings). And you can share the result PNG image as well. (If you don't want to share your image, you can create a new one with some random strokes, what's important is just the transparency). -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 420825] I eliminate color pixels and the saving I am forced to pick a pixel color
https://bugs.kde.org/show_bug.cgi?id=420825 --- Comment #7 from rfja...@yahoo.com --- Created attachment 128044 --> https://bugs.kde.org/attachment.cgi?id=128044=edit Screen Shot withi Krita.png --- Comment #8 from rfja...@yahoo.com --- Created attachment 128045 --> https://bugs.kde.org/attachment.cgi?id=128045=edit Screen Shot removal backgroung.png --- Comment #9 from rfja...@yahoo.com --- Created attachment 128046 --> https://bugs.kde.org/attachment.cgi?id=128046=edit Screen Shot 2020-04-30 at 6.58.46 PM.png --- Comment #10 from rfja...@yahoo.com --- Created attachment 128047 --> https://bugs.kde.org/attachment.cgi?id=128047=edit Screen Shot 2020-04-30 at 6.59.25 PM.png --- Comment #11 from rfja...@yahoo.com --- Created attachment 128048 --> https://bugs.kde.org/attachment.cgi?id=128048=edit rose-outline-2018-10.png -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 419722] QMimeData::hasText() called on nullptr returned by QClipboard::mimeData().
https://bugs.kde.org/show_bug.cgi?id=419722 michael changed: What|Removed |Added Latest Commit|https://invent.kde.org/kde/ |https://invent.kde.org/kde/ |kdiff3/commit/48c0deaf53eb5 |kdiff3/commit/643edc26bcc8f |c8ab60deabfa59551c8bcca5612 |8e083a97e87c2686f62ffd01f31 --- Comment #2 from michael --- Git commit 643edc26bcc8f8e083a97e87c2686f62ffd01f31 by Michael Reeves, on behalf of Christoph Feck. Committed on 30/04/2020 at 22:44. Pushed by mreeves into branch '1.8'. Fix crash when clipboard is not available Summary: QClipboard::mimeData() can be nullptr according to documentation. FIXED-IN: 1.8.3 Reviewers: mreeves Reviewed By: mreeves Differential Revision: https://phabricator.kde.org/D29248 M +1-1src/pdiff.cpp https://invent.kde.org/kde/kdiff3/commit/643edc26bcc8f8e083a97e87c2686f62ffd01f31 -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 419722] QMimeData::hasText() called on nullptr returned by QClipboard::mimeData().
https://bugs.kde.org/show_bug.cgi?id=419722 michael changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED Version Fixed In||1.8.3 Latest Commit||https://invent.kde.org/kde/ ||kdiff3/commit/48c0deaf53eb5 ||c8ab60deabfa59551c8bcca5612 --- Comment #1 from michael --- Git commit 48c0deaf53eb5c8ab60deabfa59551c8bcca5612 by Michael Reeves, on behalf of Christoph Feck. Committed on 30/04/2020 at 22:38. Pushed by mreeves into branch 'master'. Fix crash when clipboard is not available Summary: QClipboard::mimeData() can be nullptr according to documentation. FIXED-IN: 1.8.3 Reviewers: mreeves Reviewed By: mreeves Differential Revision: https://phabricator.kde.org/D29248 M +1-1src/pdiff.cpp https://invent.kde.org/kde/kdiff3/commit/48c0deaf53eb5c8ab60deabfa59551c8bcca5612 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 420824] Zoom in over "Fit Width" in two page mode
https://bugs.kde.org/show_bug.cgi?id=420824 Albert Astals Cid changed: What|Removed |Added Ever confirmed|0 |1 CC||aa...@kde.org Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[kgeography] [Bug 420768] Incorrect name for county on Great Britain map
https://bugs.kde.org/show_bug.cgi?id=420768 Albert Astals Cid changed: What|Removed |Added Latest Commit||https://commits.kde.org/kge ||ography/9657dd8ea0e99a438e7 ||8e9d7e5e1c7a836c025db Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #3 from Albert Astals Cid --- Git commit 9657dd8ea0e99a438e78e9d7e5e1c7a836c025db by Albert Astals Cid. Committed on 30/04/2020 at 22:31. Pushed by aacid into branch 'master'. Make it clear the GB Counties map is Historic Counties M +2-2data/great-britain_counties.kgm https://commits.kde.org/kgeography/9657dd8ea0e99a438e78e9d7e5e1c7a836c025db -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 420775] Bad error message when opening .epub files without .epub support
https://bugs.kde.org/show_bug.cgi?id=420775 Albert Astals Cid changed: What|Removed |Added Resolution|--- |DOWNSTREAM Status|REPORTED|RESOLVED CC||aa...@kde.org --- Comment #1 from Albert Astals Cid --- That's a problem of your distribution. They are shipping a plugin without it's dependencies, they shouldn't do that. On a more abstract note, what you're asking is impossible, Okular doesn't know about it's plugins, there can be any number of plugins, shipped by third parties (calligra for exmaple does) so it can't telll you what you are missing to execute about a plugin it doesn't know about. -- You are receiving this mail because: You are watching all bug changes.
[kigo] [Bug 420814] kigo is not executing the go engine correctly
https://bugs.kde.org/show_bug.cgi?id=420814 Albert Astals Cid changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||aa...@kde.org, ||mon...@kde.org --- Comment #1 from Albert Astals Cid --- Yes, it was broken in f48c987eb6fcedac622f1d756774588c1829c635 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 418662] Some system tray icons seem to choose the wrong color/become invisible
https://bugs.kde.org/show_bug.cgi?id=418662 --- Comment #10 from Konrad Materka --- Patrick, are you still able to reproduce? Is it consistent or random? When it happens, are all SNI icons affected or only Media Player? Can you provide some steps and screenshots? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385828] Applications are restored before StatusNotifierWatcher is started
https://bugs.kde.org/show_bug.cgi?id=385828 --- Comment #57 from Konrad Materka --- I know that Brian is using VPN (Bug 420635), Aleksey - are you as well? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385828] Applications are restored before StatusNotifierWatcher is started
https://bugs.kde.org/show_bug.cgi?id=385828 --- Comment #56 from Konrad Materka --- Quick question: are you using VPN? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 420635] Apps that autostart do not appear in the system tray, including DiscoverNotifier
https://bugs.kde.org/show_bug.cgi?id=420635 --- Comment #14 from Konrad Materka --- > Maybe something is happening when SDDM launches Plasma? It may be that KDE is started in a different way, but I'm not an expert in this area. I was not able to reproduce this issue, I'm using exactly the same distribution. KDE Neon is popular among KDE developers, someone else would notice already, so it seems that this problem is very rare. We have another similar Bug 385828, so it is not that rare that you are the only one affected :) In that context, I would like to ask you for more help, but firstly I need to explain few technical aspects so that we will get as useful data as possible. System tray contains two type of items: * Plasmoids - these are not real applications, but embedded widgets, for example: Bluetooth, Network, Volume etc. You can recognize them by two things: in setting of System Tray they have disabled option and usually on click they show some panel, instead of menu. * SNI (Status Notifier Item) icons - all external applications like Skype, Dropbox, Discord, Telegram etc. It looks that the problem is with SNI icons - plasmoids are working fine. There is also a special case for SNI icons: legacy tray icons used by some old old application like KeePass2, Pidgin, xchat and all Windows application run with wine. The xembedsniproxy is used to translate legacy icons to SNI protocol. SNI icons are register in DBus service named "org.kde.StatusNotifierWatcher" - that's why I asked you to run "qdbus org.kde.StatusNotifierWatcher /StatusNotifierWatcher RegisteredStatusNotifierItems" - to list all icons IDs registered in that DBus service. The listIcons.sh scripts uses these IDs and just prints more information. In the situation you have, when icons are missing entirely but corresponding applications are running in the background, DBus service should not have them as well. This is the most important information to confirm first: is DBus service running and if it has or not icons registered. In your second comment, after running listIcons.sh, you received this error: "org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.". This is especially worrying and strange... You then posted this: "The error message is from NetworkManager. I accidentally had it disabled when". Can you give more details how did you disable NetworkManager? Can you reproduce the same situation again? Disabling Network Manager should not affect DBus, did you do anything else? Maybe it is related to your VPN configuration? I found this: https://www.privateinternetaccess.com/forum/discussion/33328/no-tray-icon-after-update-to-v80-on-ubuntu-17-10 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 420825] I eliminate color pixels and the saving I am forced to pick a pixel color
https://bugs.kde.org/show_bug.cgi?id=420825 --- Comment #5 from Tymond --- Can you please make a screenshot of your Krita window before saving (so I can see the image with transparency (removed background) inside Krita) and then another one when you are asked about PNG settings? (First you're asked for the name of the file, and then there are settings, I mean the dialog with settings). And you can share the result PNG image as well. (If you don't want to share your image, you can create a new one with some random strokes, what's important is just the transparency). -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 420825] I eliminate color pixels and the saving I am forced to pick a pixel color
https://bugs.kde.org/show_bug.cgi?id=420825 --- Comment #4 from rfja...@yahoo.com --- Thank you for getting back to me. When I open the file I see black. No. checkers . or white if I am able to change the color but it requires a color for transparency saving. I tried PNG an JPG On Thursday, April 30, 2020, 05:31:10 PM EDT, Tymond wrote: https://bugs.kde.org/show_bug.cgi?id=420825 --- Comment #3 from Tymond --- A lot of image viewers don't really show transparency and just fill it with white or black instead. If you open the file (the png file that you saved) in Krita, do you see transparency checkers or black? (Also remember: it's always good to save as .kra as well, it will save your layers and everything else as it is in Krita). Also btw: in general, it's easier to use krita-artists.org forum first to get help - it's more user-friendly and user-oriented than this website. This website is more like for development. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 419909] Shortcut descriptions are not Readable
https://bugs.kde.org/show_bug.cgi?id=419909 --- Comment #6 from Lonnie --- Wow; it looks fantastic! -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 420828] New: Discover Crashes on Launch
https://bugs.kde.org/show_bug.cgi?id=420828 Bug ID: 420828 Summary: Discover Crashes on Launch Product: Discover Version: 5.18.4 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: aer0...@gmail.com CC: aleix...@kde.org Target Milestone: --- Application: plasma-discover (5.18.4) Qt Version: 5.14.2 Frameworks Version: 5.69.0 Operating System: Linux 5.3.0-51-generic x86_64 Windowing system: X11 Distribution: KDE neon User Edition 5.18 -- Information about the crash: - What I was doing when the application crashed: I tried to open Discover from the app menu to install software. I had run an update in Discover earlier, it was fine. Just a minute ago, System Settings also crashed on launch, so maybe something larger is happening. I have not yet tried a restart. The crash can be reproduced every time. -- Backtrace: Application: Discover (plasma-discover), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fb57b99c980 (LWP 23695))] Thread 9 (Thread 0x7fb53b45a700 (LWP 23706)): #0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 #1 0x7fb577279e04 in QSemaphore::acquire(int) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7fb5774a231e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7fb5753ba70b in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #4 0x7fb575462b6d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #5 0x7fb5774a2139 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fb5753b0879 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #7 0x7fb5753b1125 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #8 0x7fb5774a2139 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7fb57545b10f in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #10 0x7fb5754502bb in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #11 0x7fb5754508fd in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #12 0x7fb57542c841 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #13 0x7fb5774a2139 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x7fb5753f70c3 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #15 0x7fb5753f716c in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #16 0x7fb57540a781 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #17 0x7fb578c489ac in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #18 0x7fb578c4fbb0 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #19 0x7fb577467128 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #20 0x7fb5774c6ff8 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #21 0x7fb570e54417 in g_main_context_dispatch () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #22 0x7fb570e54650 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #23 0x7fb570e546dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #24 0x7fb5774c642c in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #25 0x7fb5774659aa in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #26 0x7fb5772763d7 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #27 0x7fb5772778ac in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #28 0x7fb5730b26db in start_thread (arg=0x7fb53b45a700) at pthread_create.c:463 #29 0x7fb576b6c88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 8 (Thread 0x7fb540872700 (LWP 23705)): #0 __GI___pthread_getspecific (key=5) at pthread_getspecific.c:30 #1 0x7fb570e7c660 in g_thread_self () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fb570e546cd in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fb5774c644b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fb5774659aa in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fb5772763d7 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fb5772778ac in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fb5730b26db in start_thread (arg=0x7fb540872700) at pthread_create.c:463 #8 0x7fb576b6c88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 7 (Thread 0x7fb522d43700 (LWP 23703)): #0 0x7fb576b5b0b4 in __GI___libc_read (fd=17, buf=0x7fb522d42b50,
[krita] [Bug 420825] I eliminate color pixels and the saving I am forced to pick a pixel color
https://bugs.kde.org/show_bug.cgi?id=420825 --- Comment #3 from Tymond --- A lot of image viewers don't really show transparency and just fill it with white or black instead. If you open the file (the png file that you saved) in Krita, do you see transparency checkers or black? (Also remember: it's always good to save as .kra as well, it will save your layers and everything else as it is in Krita). Also btw: in general, it's easier to use krita-artists.org forum first to get help - it's more user-friendly and user-oriented than this website. This website is more like for development. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 420827] New: Cannot revert screen resolution to currently selected in KCM
https://bugs.kde.org/show_bug.cgi?id=420827 Bug ID: 420827 Summary: Cannot revert screen resolution to currently selected in KCM Product: systemsettings Version: 5.17.5 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_kscreen Assignee: kscreen-bugs-n...@kde.org Reporter: aspotas...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY Cannot revert screen resolution to currently selected in KCM if resolution was changed by another app while Screen KCM was open. STEPS TO REPRODUCE 1. Open kcm_kscreen. Notice current screen resolution (1920x1080 in my case.) 2. Use another app to change screen resolution, e.g. run StarCraft 2 in Wine that would request a different resolution (1280x720.) 3. Click Apply in the KCM. OBSERVED RESULT It won't work because Apply button in KCM is still grayed out. EXPECTED RESULT Either Apply should work to revert screen resolution back to 1920x1080, or there should be another way to do it (besides Apply). SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 5.17.5 (available in About System) KDE Plasma Version: 5.17.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.13.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 420826] New: System Settings Crashed on Launch
https://bugs.kde.org/show_bug.cgi?id=420826 Bug ID: 420826 Summary: System Settings Crashed on Launch Product: systemsettings Version: 5.18.4 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: aer0...@gmail.com Target Milestone: --- Application: systemsettings5 (5.18.4) Qt Version: 5.14.2 Frameworks Version: 5.69.0 Operating System: Linux 5.3.0-51-generic x86_64 Windowing system: X11 Distribution: KDE neon User Edition 5.18 -- Information about the crash: - What I was doing when the application crashed: I attempted to launch System Settings from the app menu. I had run it earlier and it ran fine. I tried to launch it a couple more times, and it didn't work. I have not yet tried a restart. The crash can be reproduced every time. -- Backtrace: Application: System Settings (systemsettings5), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7efd19f79840 (LWP 23135))] Thread 5 (Thread 0x7efce86bf700 (LWP 23140)): #0 0x7efd0e9b1642 in g_mutex_unlock () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7efd0e96afd9 in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7efd0e96b570 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7efd0e96b6dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7efd15d1d44b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7efd15cbc9aa in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7efd15acd3d7 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7efd13611fc5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #8 0x7efd15ace8ac in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7efd10deb6db in start_thread (arg=0x7efce86bf700) at pthread_create.c:463 #10 0x7efd153c388f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7efcf18f9700 (LWP 23139)): #0 0x7efd15acee9f in QMutex::unlock() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #1 0x7efd15d1dac7 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7efd0e96afe1 in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7efd0e96b570 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7efd0e96b6dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7efd15d1d44b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7efd15cbc9aa in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7efd15acd3d7 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7efd13611fc5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #9 0x7efd15ace8ac in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7efd10deb6db in start_thread (arg=0x7efcf18f9700) at pthread_create.c:463 #11 0x7efd153c388f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7efcfbfff700 (LWP 23138)): #0 __lll_unlock_wake () at ../sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:371 #1 0x7efd10def7df in __pthread_mutex_unlock_usercnt (decr=1, mutex=0x7efd1078b8a0) at pthread_mutex_unlock.c:54 #2 __GI___pthread_mutex_unlock (mutex=0x7efd1078b8a0) at pthread_mutex_unlock.c:345 #3 0x7efd10507b79 in ?? () from /usr/lib/x86_64-linux-gnu/libGL.so.1 #4 0x7efd1050b888 in ?? () from /usr/lib/x86_64-linux-gnu/libGL.so.1 #5 0x7efd0d46cfe1 in ?? () from /usr/lib/x86_64-linux-gnu/tls/libnvidia-tls.so.340.108 #6 0x7efd0e9b02b0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7efd0e96b0b7 in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #8 0x7efd0e96b570 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #9 0x7efd0e96b6dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #10 0x7efd15d1d44b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7efd15cbc9aa in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7efd15acd3d7 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7efd161a9555 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #14 0x7efd15ace8ac in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x7efd10deb6db in start_thread (arg=0x7efcfbfff700) at pthread_create.c:463 #16 0x7efd153c388f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7efd03fb0700
[plasmashell] [Bug 385880] Global Menu: does not work under wayland and causes a black screen when trying to enter its setting
https://bugs.kde.org/show_bug.cgi?id=385880 --- Comment #24 from Denis Shklyaev --- Created attachment 128041 --> https://bugs.kde.org/attachment.cgi?id=128041=edit Global Menu working on Plasma 5.18.80 under Wayland -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 419813] Okular on Windows cannot open WSL 2 files
https://bugs.kde.org/show_bug.cgi?id=419813 --- Comment #1 from w...@williamjbowman.com --- I found a workaround that suggests this may have something to do with the WSL 2 path. If we remount WSL 2 as a drive explicitly, we can open files using Okular. 1. Navigate to `\\wsl$` in Explorer. 2. Right click on the `` folder and click "Map network drive...". 3. Mount the folder as a new drive, such as `Z:`. 4. Open the same PDF from `Z:path\to\file.pdf` instead of from `\\wsl$\\path\to\file.pdf`. It will open correctly. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 420825] I eliminate color pixels and the saving I am forced to pick a pixel color
https://bugs.kde.org/show_bug.cgi?id=420825 --- Comment #2 from rfja...@yahoo.com --- I tried to follow your suggestions however now it is saving not as a transparence but now it is storing the png with a black background fill! On Thursday, April 30, 2020, 04:48:47 PM EDT, Tymond wrote: https://bugs.kde.org/show_bug.cgi?id=420825 Tymond changed: What |Removed |Added CC| |tamtamy.tym...@gmail.com Status|REPORTED |NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from Tymond --- What format do you save to? PNG has this function, while JPEG doesn't because you cannot save transparency in JPEG file, even in Photoshop, because JPEG doesn't support transparency. Make sure that while saving to PNG, the checkbox "Store alpha channel (transparency)" is *checked*, otherwise it won't save the transparency. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 420770] okular-20.04.0: very sluggish scrolling behavior
https://bugs.kde.org/show_bug.cgi?id=420770 Till Schäfer changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #2 from Till Schäfer --- this is fixed for me by the following commit Git commit 08d368c13b0fa7368be9720b8de1b7a67188b8e9 by Nate Graham, on behalf of Kezi Olio. Committed on 29/04/2020 at 22:15. Pushed by ngraham into branch 'release/20.04'. Fix scroll speed with free-spinning mouse wheels FIXED-IN: 1.10.1 This just removes the smooth mouse wheel scrolling, fixing that problem. M +4-10 ui/pageview.cpp https://invent.kde.org/kde/okular/commit/08d368c13b0fa7368be9720b8de1b7a67188b8e9 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 378694] applications menu covered by panel
https://bugs.kde.org/show_bug.cgi?id=378694 --- Comment #18 from magib...@hotmail.com --- What causes this issue? If you run plasmashell under Xwayland (QT_QPA_PLATFORM=xcb) the behaviour is the same as in X11. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 420761] After upgrade from Fedora 31 to 32, one of my checking accounts shows a huge negative "Cleared" balance
https://bugs.kde.org/show_bug.cgi?id=420761 --- Comment #10 from Rex Dieter --- (Temporary) link to full f32 build.log, https://kojipkgs.fedoraproject.org//work/tasks/7321/43947321/build.log -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 420761] After upgrade from Fedora 31 to 32, one of my checking accounts shows a huge negative "Cleared" balance
https://bugs.kde.org/show_bug.cgi?id=420761 --- Comment #9 from Rex Dieter --- running tests on f31: The following tests FAILED: 1 - appstreamtest (Failed) 38 - qsqlcipher-test (Failed) 1 is a false positive Start 1: appstreamtest 1/42 Test #1: appstreamtest .***Failed0.06 sec CMake Error at /usr/share/ECM/kde-modules/appstreamtest.cmake:32 (message): File '/usr/share/metainfo/org.kde.kmymoney.appdata.xml' does not exist. Assumes kmymoney appstream file is already installed, instead of testing the one in the build directory 38/42 Test #38: qsqlcipher-test ...***Failed0.02 sec * Start testing of qsqlciphertest * Config: Using QtTest library 5.13.2, Qt 5.13.2 (x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 9.3.1 20200317 (Red Hat 9.3.1-1)) FAIL! : qsqlciphertest::initTestCase() 'drivers.contains(sqlDriverName)' returned FALSE. () Loc: [/var/tmp/kdecache-rdieter/BUILDROOT/kmymoney-5.0.8/kmymoney/plugins/sqlcipher/tests/qsqlcipher-test.cpp(42)] PASS : qsqlciphertest::cleanupTestCase() Totals: 1 passed, 1 failed, 0 skipped, 0 blacklisted, 1ms * Finished testing of qsqlciphertest * Similar assumption, assuming sql driver in builddir is usable? On f32, The following tests FAILED: 1 - appstreamtest (Failed) 9 - mymoneyfile-test (Failed) 23 - mymoneytransactionfilter-test (Failed) 31 - reports-chart-test (Failed) 33 - reports-pivottable-test (Failed) 38 - qsqlcipher-test (Failed) 9/42 Test #9: mymoneyfile-test ..***Failed0.12 sec * Start testing of MyMoneyFileTest * Config: Using QtTest library 5.14.2, Qt 5.14.2 (x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 10.0.1 20200328 (Red Hat 10.0.1-0.11)) ... FAIL! : MyMoneyFileTest::testCountTransactionsWithSpecificReconciliationState_transactionWithUnwantedReconcileState() Compared values are not the same Actual (m->countTransactionsWithSpecificReconciliationState(accountId, eMyMoney::TransactionFilter::State::NotReconciled)): 1 Expected (0) : 0 Loc: [/builddir/build/BUILD/kmymoney-5.0.8/kmymoney/mymoney/tests/mymoneyfile-test.cpp(2345)] ... FAIL! : MyMoneyFileTest::testClearedBalance() Compared values are not the same Loc: [/builddir/build/BUILD/kmymoney-5.0.8/kmymoney/mymoney/tests/mymoneyfile-test.cpp(2543)] 23/42 Test #23: mymoneytransactionfilter-test .***Failed0.10 sec * Start testing of MyMoneyTransactionFilterTest * Config: Using QtTest library 5.14.2, Qt 5.14.2 (x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 10.0.1 20200328 (Red Hat 10.0.1-0.11)) ... FAIL! : MyMoneyTransactionFilterTest::testMatchTransactionState() Compared values are not the same Actual (filter.matchingSplits(transaction).size()): 4 Expected (1): 1 Loc: [/builddir/build/BUILD/kmymoney-5.0.8/kmymoney/mymoney/tests/mymoneytransactionfilter-test.cpp(454)] ... FAIL! : MyMoneyTransactionFilterTest::testMatchTransactionTypeAllTypes() '!filter.match(transaction)' returned FALSE. () Loc: [/builddir/build/BUILD/kmymoney-5.0.8/kmymoney/mymoney/tests/mymoneytransactionfilter-test.cpp(575)] FAIL! : MyMoneyTransactionFilterTest::testMatchTransactionTypeDeposits() Compared values are not the same Actual (filter.matchingSplits(transaction2).size()): 1 Expected (0) : 0 Loc: [/builddir/build/BUILD/kmymoney-5.0.8/kmymoney/mymoney/tests/mymoneytransactionfilter-test.cpp(623)] FAIL! : MyMoneyTransactionFilterTest::testMatchTransactionTypePayments() Compared values are not the same Actual (filter.matchingSplits(transaction).size()): 2 Expected (0): 0 Loc: [/builddir/build/BUILD/kmymoney-5.0.8/kmymoney/mymoney/tests/mymoneytransactionfilter-test.cpp(663)] FAIL! : MyMoneyTransactionFilterTest::testMatchTransactionTypeTransfers() Compared values are not the same Actual (filter.matchingSplits(transaction).size()): 3 Expected (0): 0 Loc: [/builddir/build/BUILD/kmymoney-5.0.8/kmymoney/mymoney/tests/mymoneytransactionfilter-test.cpp(724)] 31/42 Test #31: reports-chart-test ***Failed 10.09 sec * Start testing of ChartTest * Config: Using QtTest library 5.14.2, Qt 5.14.2 (x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 10.0.1 20200328 (Red Hat 10.0.1-0.11)) PASS : ChartTest::initTestCase() libEGL warning: MESA-LOADER: failed to open swrast (search paths /usr/lib64/dri) (probably harmless, buildsystem cannot use gui) 33/42 Test #33: reports-pivottable-test ...***Failed0.15 sec * Start testing of
[plasmashell] [Bug 385880] Global Menu: does not work under wayland and causes a black screen when trying to enter its setting
https://bugs.kde.org/show_bug.cgi?id=385880 Denis Shklyaev changed: What|Removed |Added CC||denisshkly...@yandex.ru --- Comment #23 from Denis Shklyaev --- Global menu still doesn't work on stable Plasma 5.18, but works on unstable Plasma 5.18.80 under Wayland (latest neon Unstable). Some menu items may work incorrect, global menu may not appear when first launch of some application (you should launch application, then collapse its window and maximize window again). But it works. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 420818] Received attachments show as "Unnamed"
https://bugs.kde.org/show_bug.cgi?id=420818 Laurent Montel changed: What|Removed |Added CC||mon...@kde.org --- Comment #1 from Laurent Montel --- I need a testcase. Could you provide a testcase in private if you want. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 420825] I eliminate color pixels and the saving I am forced to pick a pixel color
https://bugs.kde.org/show_bug.cgi?id=420825 Tymond changed: What|Removed |Added CC||tamtamy.tym...@gmail.com Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from Tymond --- What format do you save to? PNG has this function, while JPEG doesn't because you cannot save transparency in JPEG file, even in Photoshop, because JPEG doesn't support transparency. Make sure that while saving to PNG, the checkbox "Store alpha channel (transparency)" is *checked*, otherwise it won't save the transparency. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 420825] New: I eliminate color pixels and the saving I am forced to pick a pixel color
https://bugs.kde.org/show_bug.cgi?id=420825 Bug ID: 420825 Summary: I eliminate color pixels and the saving I am forced to pick a pixel color Product: krita Version: 4.2.8 Platform: macOS Disk Images OS: macOS Status: REPORTED Severity: critical Priority: NOR Component: Tools/Selection Assignee: krita-bugs-n...@kde.org Reporter: rfja...@yahoo.com Target Milestone: --- SUMMARY. I want to eliminate background colors including white around an object. This I am able to accomplish however when I save the file I am required to choose a color to fill the pixels. This is what I don not want to do. I wish to "see through the areas I eliminated! STEPS TO REPRODUCE 1. High lite and area and delete it 2. 3. OBSERVED RESULT When I do that it has no background fill this is what I expected however when saving the file I am required to select a color. This is what I do not want to do! EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: macOS Catalina ver 10.15.4 Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION The required results were a function in Photoshop! I would have thought it was in your program! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 395861] Contiguous Selection Tool is too slow
https://bugs.kde.org/show_bug.cgi?id=395861 --- Comment #21 from Dmitry Kazakov --- Hi, Tyson! Thank you for your explanation. With your test image I seem to be able to reproduce the problem now. I'll check in details tomorrow :) PS: Btw, your new splash screen is really nice! :) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 395861] Contiguous Selection Tool is too slow
https://bugs.kde.org/show_bug.cgi?id=395861 Dmitry Kazakov changed: What|Removed |Added Severity|wishlist|normal -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 420801] Muting audio device in the system tray applet crash plasma
https://bugs.kde.org/show_bug.cgi?id=420801 Konrad Materka changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED Version Fixed In||5.70 Latest Commit||https://commits.kde.org/pla ||sma-framework/4b0d4c4bdaed6 ||5f52d7f2110c53ce984ef459b5a --- Comment #6 from Konrad Materka --- Git commit 4b0d4c4bdaed65f52d7f2110c53ce984ef459b5a by Konrad Materka. Committed on 30/04/2020 at 20:27. Pushed by kmaterka into branch 'master'. [PlasmaCore.IconItem] Regression: fix crash on source change Summary: When SvgSource is changed, old one is deleted. Connections are not automatically disconnected. This change disconnects connections and fixes regression introduced in D28470. FIXED-IN: 5.70 Test Plan: STEPS TO REPRODUCE 1. click on mute button for a device 2. click on the desktop to collapse the applet OBSERVED RESULT crash in step 1 and in the rare case it doesn't crash it crash in step 2 EXPECTED RESULT don't crash Reviewers: #plasma, #frameworks, ngraham, davidedmundson Reviewed By: ngraham Subscribers: kde-frameworks-devel Tags: #frameworks Differential Revision: https://phabricator.kde.org/D29314 M +4-1src/declarativeimports/core/iconitem.cpp https://commits.kde.org/plasma-framework/4b0d4c4bdaed65f52d7f2110c53ce984ef459b5a -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 419238] [autosave] Brush stroke freeze during autosave process
https://bugs.kde.org/show_bug.cgi?id=419238 --- Comment #3 from Dmitry Kazakov --- Git commit 40879777f07ef300d922943902b4878dc3fa974a by Dmitry Kazakov. Committed on 30/04/2020 at 20:24. Pushed by dkazakov into branch 'krita/4.3'. Don't load entire file to RAM when computing MD5 hash sum M +3-2libs/pigment/resources/KoMD5Generator.cpp https://invent.kde.org/kde/krita/commit/40879777f07ef300d922943902b4878dc3fa974a -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 419238] [autosave] Brush stroke freeze during autosave process
https://bugs.kde.org/show_bug.cgi?id=419238 Dmitry Kazakov changed: What|Removed |Added Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/kde/ ||krita/commit/eda07ac6a3191d ||c98381662bcbb23bd7f746f1fe Resolution|--- |FIXED --- Comment #1 from Dmitry Kazakov --- Git commit f460064ef598bdf7f439ea8c273cea264275a0b1 by Dmitry Kazakov. Committed on 30/04/2020 at 20:21. Pushed by dkazakov into branch 'master'. Don't load entire file to RAM when computing MD5 hash sum M +3-2libs/resources/KoMD5Generator.cpp https://invent.kde.org/kde/krita/commit/f460064ef598bdf7f439ea8c273cea264275a0b1 --- Comment #2 from Dmitry Kazakov --- Git commit eda07ac6a3191dc98381662bcbb23bd7f746f1fe by Dmitry Kazakov. Committed on 30/04/2020 at 20:23. Pushed by dkazakov into branch 'master'. Don't generate MD5 hash for files bigger than 10MB This hash is used only for logging, so there is no reason for spending time on it. We should probably consider total removing of this hash, since its calculation for a 7MiB file takes about 10ms. M +1-1libs/ui/KisDocument.cpp https://invent.kde.org/kde/krita/commit/eda07ac6a3191dc98381662bcbb23bd7f746f1fe -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 419238] [autosave] Brush stroke freeze during autosave process
https://bugs.kde.org/show_bug.cgi?id=419238 --- Comment #1 from Dmitry Kazakov --- Git commit f460064ef598bdf7f439ea8c273cea264275a0b1 by Dmitry Kazakov. Committed on 30/04/2020 at 20:21. Pushed by dkazakov into branch 'master'. Don't load entire file to RAM when computing MD5 hash sum M +3-2libs/resources/KoMD5Generator.cpp https://invent.kde.org/kde/krita/commit/f460064ef598bdf7f439ea8c273cea264275a0b1 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 420824] New: Zoom in over "Fit Width" in two page mode
https://bugs.kde.org/show_bug.cgi?id=420824 Bug ID: 420824 Summary: Zoom in over "Fit Width" in two page mode Product: okular Version: 1.9.80 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: filippovolp...@gmail.com Target Milestone: --- SUMMARY When two page mode is selected and zoom with ctrl+mousewheel I can only go from the minimum percentage (ie 12%) to "Fit Width" and can't go further. If one page mode is selected this is not a problem and works normally. I verified the problem with at least .pdf and .djvu files. The only way there's to achieve more zoom that is to manually go to the zoom dropdown menu and select a a value higher than what "Fit width" currently corresponds to given the window size and then it works as expected until you zoom out of the two pages, then the problem reappear. STEPS TO REPRODUCE 1. Open a pdf file with more than 2 pages 2. Set view mode as "facing pages" 3. Zoom in from the minimum percentage OBSERVED RESULT The zoom locks at "Fit Width" level and won't go further. EXPECTED RESULT Being able to zoom in to from 12% to 400% with only a ctrl+mousewheel action as it works in view mode "single page". SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.6.7 (available in About System) KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.69.0 Qt Version: 5.14.2 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 420819] error while opening database digikam will try to automatically reconnect to the database
https://bugs.kde.org/show_bug.cgi?id=420819 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from Maik Qualmann --- I can't do much with the bug report ... Let's start: 1. Why is digiKam running when Manjaro is started? Did you activate any session management? 2. What type of database are you using? SQLite or MySQL? 3. Please start digiKam in the console and post the log. If the database is on a drive that has not yet been mounted, the error message would be normal. Make sure that the database is available when digiKam is started. Deactivate session management so that not all programs are restarted. Maik -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 420006] system settings crash
https://bugs.kde.org/show_bug.cgi?id=420006 g...@maltimore.info changed: What|Removed |Added CC||g...@maltimore.info -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 420823] Clips of title templates lose specified duration on timeline after project reopen
https://bugs.kde.org/show_bug.cgi?id=420823 Aaron O'Neill changed: What|Removed |Added CC||seth...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 420823] New: Clips of title templates lose specified duration on timeline after project reopen
https://bugs.kde.org/show_bug.cgi?id=420823 Bug ID: 420823 Summary: Clips of title templates lose specified duration on timeline after project reopen Product: kdenlive Version: 20.04.0 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Effects & Transitions Assignee: vpi...@kde.org Reporter: seth...@gmail.com Target Milestone: --- SUMMARY I create a title template using %s. I can then instantiate title clips from the template and arrange them on the timeline. After saving and reopening of the project, any clip based on a template has a duration of the default 5 seconds. STEPS TO REPRODUCE 1. Create user title template 2. Create a title based on the template 3. Drag title from bin onto timeline 4. Drag clip duration to required length (so far so good) 5. Save and close project 6. Reopen project OBSERVED RESULT All title clips based on a template now has default 5s duration, losing the durations set on the timeline before quitting. Fade-in, fade-outs retained. EXPECTED RESULT All clips including those based on a template title retain their set durations on the timeline. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro 64-bit, Gnome 3.36.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 420612] Krita: Segmentation fault when closing
https://bugs.kde.org/show_bug.cgi?id=420612 --- Comment #7 from Lynx3d --- For me it is krita built from source with all dependencies from Ubuntu packages. Since using system-wide Qt seems the only practical way to have the Breeze style engine, I don't really know any alternative to test besides Ubuntu packages and compiles that should be equivalent to those. However I just went through all the Python plugins, and the "Comics Project Managment Tools" seems to cause the crash for me, after disabling this plugin I can use the Breeze style without crashes. -- You are receiving this mail because: You are watching all bug changes.
[Skanlite] [Bug 420812] skanlite wont install as the architecture version isn't available
https://bugs.kde.org/show_bug.cgi?id=420812 Kåre Särs changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DOWNSTREAM --- Comment #1 from Kåre Särs --- Hi, Unfortunately this is a snapcraft issue, that I cannot fix. The error message says that the available snap package only is compatible with PC and not armhf, so just not compatible with Raspberry PI. I would imagine that the debian based Raspbian distribution contains the skanlite application in the repository, so a simple sudo apt install skanlite should be enough... -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 420822] New: Start tab or new tab ignore start settings
https://bugs.kde.org/show_bug.cgi?id=420822 Bug ID: 420822 Summary: Start tab or new tab ignore start settings Product: konqueror Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: konq-b...@kde.org Reporter: eseb...@gmail.com Target Milestone: --- SUMMARY After upgrading to 20.04.0, start tab/window always opens $HOME and new tabs (new tab button or Ctrl+T) always show konq:blank. STEPS TO REPRODUCE 1. Open Configure/General 2. Change "When Konqueror Starts" 3. Restart konqueror or open a new tab OBSERVED RESULT It always opens "konq:blank" EXPECTED RESULT Show what is in "When Konqueror Starts" or "Home page" options SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Frameworks 5.69.0 Qt 5.14.1 (built against 5.14.1) The xcb windowing system -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 415762] Exiting the session in a Yakuake tab sometimes crash Yakuake
https://bugs.kde.org/show_bug.cgi?id=415762 Karl Ove Hufthammer changed: What|Removed |Added CC||k...@huftis.org -- You are receiving this mail because: You are watching all bug changes.
[juk] [Bug 420718] juk segfaut on every startup
https://bugs.kde.org/show_bug.cgi?id=420718
--- Comment #3 from Markus ---
QStringList allColHeaders;
allColHeaders.reserve(numColumnsToReserve + standardColHeaders.size());
std::fill_n(allColHeaders.begin(), numColumnsToReserve, i18n("JuK"));
Introduced here:
https://cgit.kde.org/juk.git/commit/playlist.cpp?id=a800c1b3ffeb1672cf889e707baf2b181d7fc8f1
https://phabricator.kde.org/R344:a800c1b3ffeb1672cf889e707baf2b181d7fc8f1
--
You are receiving this mail because:
You are watching all bug changes.
[okular] [Bug 415985] Okular is not printing to HP1120C printer with driver HP DeskJet 1120C Foomatic/pcl3
https://bugs.kde.org/show_bug.cgi?id=415985 bruce.samha...@samhaber.ca changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED --- Comment #35 from bruce.samha...@samhaber.ca --- I never tried that. Yes it does print with "Force rasterisation" option set in the print dialog's "PDF options" section. Is there a way to make this option set by default? Thank you, Bruce. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 420820] Konsole 20.04.0 crashes on start
https://bugs.kde.org/show_bug.cgi?id=420820 --- Comment #1 from Michael Marley --- It looks like the crash is probably related to https://github.com/KDE/konsole/commit/6db7f8d2593ccb0238b2b547ed6eaf7da6a26c4c. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 420821] Rendered video stalls while playing on Android
https://bugs.kde.org/show_bug.cgi?id=420821 Sven Klomp changed: What|Removed |Added CC||m...@klomp.eu --- Comment #1 from Sven Klomp --- Created attachment 128039 --> https://bugs.kde.org/attachment.cgi?id=128039=edit Rendered video stalls after 20 seconds on Android device (should rotate 180degree) -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 420681] Dolphin does not show up Windows 10 machines in Network
https://bugs.kde.org/show_bug.cgi?id=420681 Harald Sitter changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #4 from Harald Sitter --- This report needs debug output `QT_LOGGING_RULES="kio_smb=true" KDE_FORK_SLAVES=1 dolphin --new-window smb://` -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 417011] krita Win 10 not recognizing pressure sensitivity
https://bugs.kde.org/show_bug.cgi?id=417011 anuranjan...@gmail.com changed: What|Removed |Added Resolution|NOT A BUG |--- Ever confirmed|0 |1 Status|RESOLVED|REOPENED CC||anuranjan...@gmail.com --- Comment #2 from anuranjan...@gmail.com --- (In reply to Boudewijn Rempt from comment #1) > I'm sorry, but this is a problem with your setup and not a bug in Krita. On > millions of Windows 10 systems, people use Krita and pressure works for them. > > What exactly is up, I cannot tell since you give no information about your > system and tablet whatsoever. Please check the faq: > https://docs.krita.org/en/KritaFAQ.html#tablets and the manual page on > problems with tablets: > https://docs.krita.org/en/user_manual/drawing_tablets.html#drivers-and- > pressure-sensitivity I'm facing the same issue. Device: Microsoft Surface Book 2. OS: Windows 10 1. I have enabled "Use Pen Pressure" but it doesn't register pressure. 2. Upgraded Krita from 4.2.8 to 4.2.9 but no luck. 3. Tried both "WinTab" and "Windows 8+ Pointer Input" in "Tablet Settings". Nothing seems to work. Pen pressure is working correctly in OneNote Application so it isn't a hardware issue. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 395861] Contiguous Selection Tool is too slow
https://bugs.kde.org/show_bug.cgi?id=395861 --- Comment #20 from Tyson Tan --- Hi Dmitry, Thank you for the second patched version. It was not until 3 AM today was I able to download the file from Yandex. I think it could be network slowdown in Europe during busy hours with all those pandemic induced bandwidth usage. I use Linux, but I maintain a second drive just for test purpose and flashing firmwares. Maybe you can give me appimage links from now on to save me a reboot and the eyesores looking at Windows Cleartype. :D Now the patched version (DK2). It both worked and did not work for me: For small pictures, it was definitely working. It selects an area in a blink. Fastest speed I ever saw. For large pictures it was a very different story. Use the the 4.3 splash for example, and select a small color patch: https://tysontan.com/temp/free_software/kiki/electrichearts_20200221A_kiki_b.png It was really, really slow. Much slower than the DK1 build. It doesn't matter where I clicked or how large a color patch is, it'd just slowdown to the same amount. Krita felt like it was taking the whole image into consideration when calculating the effective area. Meanwhile the Fill tool can still fill an area in an instant. This picture has no gradient color, all hard-edged, there is no way it needed to look at the whole picture for a small patch of waterlily. But if I crop the large splash under 1000x1000, then when I select the same area as above, it'd be selected in an instant. Enabling Antialiasing in DK1 build was able to speed up 100 to 200 ms. But in DK2 when the image was large, enable or disable it does make much difference, because it was just to slow to begin with. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 420821] New: Rendered video stalls while playing on Android
https://bugs.kde.org/show_bug.cgi?id=420821 Bug ID: 420821 Summary: Rendered video stalls while playing on Android Product: kdenlive Version: 20.04.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: m...@klomp.eu Target Milestone: --- Created attachment 128038 --> https://bugs.kde.org/attachment.cgi?id=128038=edit Project file causing the problem SUMMARY Rendered MP4 video from a project with profile "1920x1080 30.00Hz (Frame Rate 29.9975fps)" stalls after 20 seconds playing on an Android phone. The sound continues to play. STEPS TO REPRODUCE 1. Set Profile to Frame size: 1920 x 1080 (1920:1080), Frame rate: 29,9975 fps, Pixel Aspect Ratio: 1, Colour Space: ITU-R 601, Interlaced: no 2. Render video into MP4 3. Play video on Android device OBSERVED RESULT Video stalls after 20 seconds playing. The audio continues to play. Setting the project profile to exactly 30.00fps works without any problems on that device. Video plays normally under Linux using VLC or mplayer. EXPECTED RESULT Videos plays normally SOFTWARE/OS VERSIONS libx264 3:0.159.r2999.296494a-1 Android 9 on Motorola moto G7 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 420820] Konsole 20.04.0 crashes on start
https://bugs.kde.org/show_bug.cgi?id=420820 Michael Marley changed: What|Removed |Added CC||mich...@michaelmarley.com -- You are receiving this mail because: You are watching all bug changes.
[telepathy] [Bug 420549] Telepathy-kde 20.04 causes long delay to plasma login completion
https://bugs.kde.org/show_bug.cgi?id=420549 MikeC changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #8 from MikeC --- This issue is resolved in the updated package: telepathy-kde-integration-module 20.04.0-2 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 171295] Allow shortcuts for input devices other than the keyboard (mouse, lirc, bluetooth, joystick, etc)
https://bugs.kde.org/show_bug.cgi?id=171295 --- Comment #27 from Nate Graham --- Yep, I use `xbindkeys` too, it would just be nice to have this doable from the UI. :) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 420561] Icons in panel missing after upgrade
https://bugs.kde.org/show_bug.cgi?id=420561 --- Comment #6 from myndstr...@protonmail.ch --- > Display and windows too bright and "glowy" with large, bad-looking shadows > (white background) and glowing (on dark background) of windows I just tried it with my old graphics card instead of CPU-only and it's not too bright and "glowy" when using the graphics card. Strangely the graphics performance seems to be at least as bad as with CPU-only when using the nouveau driver and does have glitches where it shows green space across the screen which is why I removed it again. However, when using it I could change the HDMI Black Level from Low back to Normal. It could also be a bug in Debian but I only had this after upgrading from Debian9 to 10. Just wanted to add this to the bug report in case it's relevant to finding out what's causing it. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 420820] New: Konsole 20.04.0 crashes on start
https://bugs.kde.org/show_bug.cgi?id=420820 Bug ID: 420820 Summary: Konsole 20.04.0 crashes on start Product: konsole Version: 20.04.0 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: mich...@michaelmarley.com Target Milestone: --- Application: konsole (20.04.0) Qt Version: 5.12.8 Frameworks Version: 5.69.0 Operating System: Linux 5.7.0-050700rc3-lowlatency x86_64 Windowing system: X11 Distribution: Ubuntu Groovy Gorilla (development branch) -- Information about the crash: Konsole 20.04.0 crashes every time I try to start it. I tried deleting the configuration file but that had no effect. Reverting back to 19.12.x stops the crashing. I'm using the packages from https://launchpad.net/~kubuntu-ppa/+archive/ubuntu/staging-frameworks. The crash can be reproduced every time. -- Backtrace: Application: Konsole (konsole), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fb80b116800 (LWP 8316))] Thread 3 (Thread 0x7fb809a3a700 (LWP 8318)): #0 0x7fb81056bfec in read () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7fb80d31989f in read (__nbytes=16, __buf=0x7fb809a39b60, __fd=) at /usr/include/x86_64-linux-gnu/bits/unistd.h:44 #2 g_wakeup_acknowledge (wakeup=0x7fb804001bc0) at ../../../glib/gwakeup.c:210 #3 0x7fb80d2d0cfe in g_main_context_check (context=context@entry=0x7fb7fc000c30, max_priority=2147483647, fds=fds@entry=0x7fb7fc0029e0, n_fds=n_fds@entry=1) at ../../../glib/gmain.c:3825 #4 0x7fb80d2d1152 in g_main_context_iterate (context=context@entry=0x7fb7fc000c30, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../../../glib/gmain.c:4044 #5 0x7fb80d2d12e3 in g_main_context_iteration (context=0x7fb7fc000c30, may_block=may_block@entry=1) at ../../../glib/gmain.c:4108 #6 0x7fb80ed6f583 in QEventDispatcherGlib::processEvents (this=0x7fb7fc000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #7 0x7fb80ed164db in QEventLoop::exec (this=this@entry=0x7fb809a39d70, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #8 0x7fb80eb4e785 in QThread::exec (this=this@entry=0x7fb80e2e9d80 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #9 0x7fb80e266efa in QDBusConnectionManager::run (this=0x7fb80e2e9d80 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:178 #10 0x7fb80eb4f9d2 in QThreadPrivate::start (arg=0x7fb80e2e9d80 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:361 #11 0x7fb80db35609 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #12 0x7fb81057d103 in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 2 (Thread 0x7fb80a250700 (LWP 8317)): #0 0x7fb81057096f in poll () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7fb80db69c1a in poll (__timeout=-1, __nfds=1, __fds=0x7fb80a24fca8) at /usr/include/x86_64-linux-gnu/bits/poll2.h:46 #2 _xcb_conn_wait (c=c@entry=0x562f6dfbe600, cond=cond@entry=0x562f6dfbe640, vector=vector@entry=0x0, count=count@entry=0x0) at ../../src/xcb_conn.c:480 #3 0x7fb80db6b90a in xcb_wait_for_event (c=c@entry=0x562f6dfbe600) at ../../src/xcb_in.c:697 #4 0x7fb80aa74298 in QXcbEventQueue::run (this=0x562f6dfb6c60) at qxcbeventqueue.cpp:228 #5 0x7fb80eb4f9d2 in QThreadPrivate::start (arg=0x562f6dfb6c60) at thread/qthread_unix.cpp:361 #6 0x7fb80db35609 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #7 0x7fb81057d103 in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 1 (Thread 0x7fb80b116800 (LWP 8316)): [KCrash Handler] #5 0x7fb80f72b9e6 in QAction::shortcut() const () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #6 0x7fb81034f40e in BookmarkMenu::BookmarkMenu (this=0x562f6e00af30, mgr=, owner=, parentMenu=, collection=0x7fb804007800) at ./src/BookmarkMenu.cpp:63 #7 0x7fb81034e267 in Konsole::BookmarkHandler::BookmarkHandler (this=0x562f6e022a10, collection=, menu=, toplevel=, parent=) at ./src/BookmarkHandler.cpp:68 #8 0x7fb8106761da in Konsole::MainWindow::setupActions (this=this@entry=0x562f6e01aad0) at ./src/MainWindow.cpp:340 #9 0x7fb810677f4b in Konsole::MainWindow::MainWindow (this=0x562f6e01aad0, __in_chrg=, __vtt_parm=) at ./src/MainWindow.cpp:94 #10 0x7fb81066f270 in Konsole::Application::newMainWindow (this=this@entry=0x7ffe456e4a40) at ./src/Application.cpp:168 #11 0x7fb81066f565 in Konsole::Application::processWindowArgs (this=this@entry=0x7ffe456e4a40, createdNewMainWindow=@0x7ffe456e48d7: true) at ./src/Application.cpp:416 #12 0x7fb810670772 in
[dolphin] [Bug 420810] Dolphin (20.03.90) crashes when terminal is closed with 'exit' command
https://bugs.kde.org/show_bug.cgi?id=420810 Colin J Thomson changed: What|Removed |Added Status|REPORTED|RESOLVED CC||colin.thom...@g6avk.co.uk Resolution|--- |DUPLICATE --- Comment #1 from Colin J Thomson --- Similar behaviour as bug #420695 *** This bug has been marked as a duplicate of bug 420695 *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 420695] Dolphin crashes when closing terminal via "Close Session"
https://bugs.kde.org/show_bug.cgi?id=420695 Colin J Thomson changed: What|Removed |Added CC||elizab...@sem-artist.com --- Comment #1 from Colin J Thomson --- *** Bug 420810 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 420695] Dolphin crashes when closing terminal via "Close Session"
https://bugs.kde.org/show_bug.cgi?id=420695 Colin J Thomson changed: What|Removed |Added CC||colin.thom...@g6avk.co.uk -- You are receiving this mail because: You are watching all bug changes.
