[plasmashell] [Bug 377192] New: Plasma shell crashed when I clicked on desktop menu button
https://bugs.kde.org/show_bug.cgi?id=377192 Bug ID: 377192 Summary: Plasma shell crashed when I clicked on desktop menu button Product: plasmashell Version: 5.9.2 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: kiv.ap...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.9.2) Qt Version: 5.8.0 Frameworks Version: 5.31.0 Operating System: Linux 4.9.11-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: I have clicked on desktop menu button (button, which opens menu with items "Show desktop", "Lock widgets", "Lock screen" etc). The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f57ecdc2800 (LWP 765))] Thread 17 (Thread 0x7f56eaffd700 (LWP 9168)): #0 0x7f57e5a3c10f in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f57e6b6c58b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f57306631d0 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7f57306679d8 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7f5730662263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7f5730667a32 in () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7f5730662263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #7 0x7f5730665249 in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #8 0x7f57e6b6b6d8 in () at /usr/lib/libQt5Core.so.5 #9 0x7f57e5a36454 in start_thread () at /usr/lib/libpthread.so.0 #10 0x7f57e64807df in clone () at /usr/lib/libc.so.6 Thread 16 (Thread 0x7f56eb7fe700 (LWP 9167)): #0 0x7f57e5a3c10f in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f57e6b6c58b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f57306631d0 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7f57306679d8 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7f5730662263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7f5730667a32 in () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7f5730662263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #7 0x7f5730667a32 in () at /usr/lib/libKF5ThreadWeaver.so.5 #8 0x7f5730662263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #9 0x7f5730667a32 in () at /usr/lib/libKF5ThreadWeaver.so.5 #10 0x7f5730662263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #11 0x7f5730665249 in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #12 0x7f57e6b6b6d8 in () at /usr/lib/libQt5Core.so.5 #13 0x7f57e5a36454 in start_thread () at /usr/lib/libpthread.so.0 #14 0x7f57e64807df in clone () at /usr/lib/libc.so.6 Thread 15 (Thread 0x7f56ebfff700 (LWP 9166)): #0 0x7f57e5a3c10f in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f57e6b6c58b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f57306631d0 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7f57306679d8 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7f5730662263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7f5730667a32 in () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7f5730662263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #7 0x7f5730667a32 in () at /usr/lib/libKF5ThreadWeaver.so.5 #8 0x7f5730662263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #9 0x7f5730667a32 in () at /usr/lib/libKF5ThreadWeaver.so.5 #10 0x7f5730662263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #11 0x7f5730667a32 in () at /usr/lib/libKF5ThreadWeaver.so.5 #12 0x0
[plasma-pa] [Bug 377193] New: Specify if audio devices are plugged in or not
https://bugs.kde.org/show_bug.cgi?id=377193 Bug ID: 377193 Summary: Specify if audio devices are plugged in or not Product: plasma-pa Version: 5.8.6 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: applet Assignee: now...@gmail.com Reporter: sud...@sudhirkhanger.com CC: plasma-b...@kde.org Target Milestone: --- pavucontrol shows if an audio device is connected or not. Plugged-in state would be very useful in the Audio Volume Settings. See the attached screenshot. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 377193] Specify if audio devices are plugged in or not
https://bugs.kde.org/show_bug.cgi?id=377193 --- Comment #1 from Sudhir Khanger --- Created attachment 104359 --> https://bugs.kde.org/attachment.cgi?id=104359&action=edit pavucontrol showing plugged-in status -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 377193] Specify if audio devices are plugged in or not
https://bugs.kde.org/show_bug.cgi?id=377193 --- Comment #2 from David Rosca --- https://phabricator.kde.org/D4836 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 362399] Import of payees details
https://bugs.kde.org/show_bug.cgi?id=362399 NSLW changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED Latest Commit||https://commits.kde.org/kmy ||money/8ee1d231f50824454e7ef ||0afdb8b47c5a918220b --- Comment #2 from NSLW --- Git commit 8ee1d231f50824454e7ef0afdb8b47c5a918220b by Łukasz Wojniłowicz. Committed on 04/03/2017 at 08:35. Pushed by wojnilowicz into branch 'master'. Fetch payee's data from addressbook Related: bug 288075, bug 353558 Differential Revision: https://phabricator.kde.org/D4786 M +60 -10 kmymoney/mymoney/mymoneycontact.cpp M +104 -1kmymoney/views/kpayeesview.cpp M +15 -0kmymoney/views/kpayeesview.h M +38 -35 kmymoney/views/kpayeesviewdecl.ui M +3-1kmymoney/wizards/newuserwizard/knewuserwizard.cpp https://commits.kde.org/kmymoney/8ee1d231f50824454e7ef0afdb8b47c5a918220b -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 282515] Hiding old securities
https://bugs.kde.org/show_bug.cgi?id=282515 NSLW changed: What|Removed |Added Latest Commit||https://commits.kde.org/kmy ||money/6471f04e80b95fb68fbe4 ||51c5ed6436ff0fb7541 Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #1 from NSLW --- Git commit 6471f04e80b95fb68fbe451c5ed6436ff0fb7541 by Łukasz Wojniłowicz. Committed on 04/03/2017 at 08:32. Pushed by wojnilowicz into branch 'master'. Show/Hide zero-balance investment account equities Related: bug 353002 Differential Revision: https://phabricator.kde.org/D4685 M +7-0kmymoney/dialogs/settings/ksettingsgeneraldecl.ui M +4-0kmymoney/kmymoney.kcfg M +8-1kmymoney/views/kinvestmentview.cpp https://commits.kde.org/kmymoney/6471f04e80b95fb68fbe451c5ed6436ff0fb7541 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 353002] Add ability to hide zero-balance equities on Investments page
https://bugs.kde.org/show_bug.cgi?id=353002 NSLW changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://commits.kde.org/kmy ||money/6471f04e80b95fb68fbe4 ||51c5ed6436ff0fb7541 Status|UNCONFIRMED |RESOLVED --- Comment #2 from NSLW --- Git commit 6471f04e80b95fb68fbe451c5ed6436ff0fb7541 by Łukasz Wojniłowicz. Committed on 04/03/2017 at 08:32. Pushed by wojnilowicz into branch 'master'. Show/Hide zero-balance investment account equities Related: bug 282515 Differential Revision: https://phabricator.kde.org/D4685 M +7-0kmymoney/dialogs/settings/ksettingsgeneraldecl.ui M +4-0kmymoney/kmymoney.kcfg M +8-1kmymoney/views/kinvestmentview.cpp https://commits.kde.org/kmymoney/6471f04e80b95fb68fbe451c5ed6436ff0fb7541 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 353558] Import of address details
https://bugs.kde.org/show_bug.cgi?id=353558 NSLW changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://commits.kde.org/kmy ||money/8ee1d231f50824454e7ef ||0afdb8b47c5a918220b Status|UNCONFIRMED |RESOLVED --- Comment #1 from NSLW --- Git commit 8ee1d231f50824454e7ef0afdb8b47c5a918220b by Łukasz Wojniłowicz. Committed on 04/03/2017 at 08:35. Pushed by wojnilowicz into branch 'master'. Fetch payee's data from addressbook Related: bug 288075, bug 362399 Differential Revision: https://phabricator.kde.org/D4786 M +60 -10 kmymoney/mymoney/mymoneycontact.cpp M +104 -1kmymoney/views/kpayeesview.cpp M +15 -0kmymoney/views/kpayeesview.h M +38 -35 kmymoney/views/kpayeesviewdecl.ui M +3-1kmymoney/wizards/newuserwizard/knewuserwizard.cpp https://commits.kde.org/kmymoney/8ee1d231f50824454e7ef0afdb8b47c5a918220b -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 288075] Tighter integration with Kontact
https://bugs.kde.org/show_bug.cgi?id=288075 NSLW changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED Latest Commit||https://commits.kde.org/kmy ||money/8ee1d231f50824454e7ef ||0afdb8b47c5a918220b --- Comment #1 from NSLW --- Git commit 8ee1d231f50824454e7ef0afdb8b47c5a918220b by Łukasz Wojniłowicz. Committed on 04/03/2017 at 08:35. Pushed by wojnilowicz into branch 'master'. Fetch payee's data from addressbook Related: bug 353558, bug 362399 Differential Revision: https://phabricator.kde.org/D4786 M +60 -10 kmymoney/mymoney/mymoneycontact.cpp M +104 -1kmymoney/views/kpayeesview.cpp M +15 -0kmymoney/views/kpayeesview.h M +38 -35 kmymoney/views/kpayeesviewdecl.ui M +3-1kmymoney/wizards/newuserwizard/knewuserwizard.cpp https://commits.kde.org/kmymoney/8ee1d231f50824454e7ef0afdb8b47c5a918220b -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 282515] Hiding old securities
https://bugs.kde.org/show_bug.cgi?id=282515 NSLW changed: What|Removed |Added Version Fixed In||5.0 CC||lukasz.wojnilow...@gmail.co ||m -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 353002] Add ability to hide zero-balance equities on Investments page
https://bugs.kde.org/show_bug.cgi?id=353002 NSLW changed: What|Removed |Added Version Fixed In||5.0 CC||lukasz.wojnilow...@gmail.co ||m -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 353558] Import of address details
https://bugs.kde.org/show_bug.cgi?id=353558 NSLW changed: What|Removed |Added Version Fixed In||5.0 CC||lukasz.wojnilow...@gmail.co ||m -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 362399] Import of payees details
https://bugs.kde.org/show_bug.cgi?id=362399 NSLW changed: What|Removed |Added CC||lukasz.wojnilow...@gmail.co ||m Version Fixed In||5.0 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 288075] Tighter integration with Kontact
https://bugs.kde.org/show_bug.cgi?id=288075 NSLW changed: What|Removed |Added CC||lukasz.wojnilow...@gmail.co ||m Version Fixed In||5.0 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kxmlgui] [Bug 375555] Opening KDE apps gives multiples notifications about: "There are two actions(...) that want to use the same shortcut"
https://bugs.kde.org/show_bug.cgi?id=37 --- Comment #19 from Lukas Tines --- There were bunch of pretty basic shortcuts, like CTR+C/V/X so I believe they worked. No idea how they got there. I change shortcuts very rarely and haven't done that in past few months. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 321987] add option for logarithmic axes to the various report graphs
https://bugs.kde.org/show_bug.cgi?id=321987 NSLW changed: What|Removed |Added Latest Commit||https://commits.kde.org/kmy ||money/5116e77bc3cd843d57902 ||8adfe5e98efcb8a56c9 Version Fixed In||5.0 CC||lukasz.wojnilow...@gmail.co ||m Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 321987] add option for logarithmic axes to the various report graphs
https://bugs.kde.org/show_bug.cgi?id=321987 --- Comment #1 from NSLW --- Git commit 5116e77bc3cd843d579028adfe5e98efcb8a56c9 by Łukasz Wojniłowicz. Committed on 04/03/2017 at 08:35. Pushed by wojnilowicz into branch 'master'. Add range tab to reports Range tab allows setting X and Y range of chart on one tab. Differential Revision: https://phabricator.kde.org/D4655 Signed-off-by: Łukasz Wojniłowicz M +2-1kmymoney/dialogs/CMakeLists.txt A +139 -0kmymoney/dialogs/daterangedlg.cpp [License: GPL (v2+)] A +99 -0kmymoney/dialogs/daterangedlg.h [License: GPL (v2+)] A +63 -0kmymoney/dialogs/daterangedlgdecl.ui M +2-1kmymoney/dialogs/kbalancechartdlg.cpp M +9-60 kmymoney/dialogs/kfindtransactiondlg.cpp M +2-35 kmymoney/dialogs/kfindtransactiondlg.h M +5-56 kmymoney/dialogs/kfindtransactiondlgdecl.ui M +106 -60 kmymoney/dialogs/kreportconfigurationfilterdlg.cpp M +4-1kmymoney/dialogs/kreportconfigurationfilterdlg.h M +41 -8kmymoney/mymoney/mymoneyreport.cpp M +83 -10 kmymoney/mymoney/mymoneyreport.h M +149 -77 kmymoney/reports/kreportchartview.cpp M +4-0kmymoney/reports/kreportchartview.h M +2-1kmymoney/views/kforecastview.cpp M +2-1kmymoney/views/khomeview.cpp M +44 -9kmymoney/views/kreportsview.cpp M +1-0kmymoney/views/kreportsview.h M +1-0kmymoney/widgets/CMakeLists.txt M +226 -266 kmymoney/widgets/kmymoneyreportconfigtab2decl.ui M +50 -36 kmymoney/widgets/kmymoneyreportconfigtabchartdecl.ui M +141 -0kmymoney/widgets/kmymoneyreportconfigtabimpl.cpp M +63 -2kmymoney/widgets/kmymoneyreportconfigtabimpl.h A +224 -0kmymoney/widgets/kmymoneyreportconfigtabrangedecl.ui https://commits.kde.org/kmymoney/5116e77bc3cd843d579028adfe5e98efcb8a56c9 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 377194] New: Crash after Arch-Linux update to plasma 5.9.3
https://bugs.kde.org/show_bug.cgi?id=377194 Bug ID: 377194 Summary: Crash after Arch-Linux update to plasma 5.9.3 Product: plasmashell Version: 5.9.3 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: kde_b...@thannernet.de CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.9.3) Qt Version: 5.8.0 Frameworks Version: 5.31.0 Operating System: Linux 4.9.11-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: Left click on Plasma Hamburger Menu (?) to unlock Applets (?) on a dual screen (different resolutions) desktop running Arch-Linux The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fd899baa800 (LWP 1012))] Thread 15 (Thread 0x7fd7abfff700 (LWP 1327)): #0 0x7fd8928644b8 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fd86efd0e44 in () at /usr/lib/libGLX_nvidia.so.0 #2 0x7fd86dbfc394 in () at /usr/lib/libnvidia-glcore.so.378.13 #3 0x7fd86efd012c in () at /usr/lib/libGLX_nvidia.so.0 #4 0x7fd89285e454 in start_thread () at /usr/lib/libpthread.so.0 #5 0x7fd8932a87df in clone () at /usr/lib/libc.so.6 Thread 14 (Thread 0x7fd7b0907700 (LWP 1326)): #0 0x7fd89286410f in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fd89399458b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7fd8976ed665 in () at /usr/lib/libQt5Quick.so.5 #3 0x7fd8976edf72 in () at /usr/lib/libQt5Quick.so.5 #4 0x7fd8939936d8 in () at /usr/lib/libQt5Core.so.5 #5 0x7fd89285e454 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7fd8932a87df in clone () at /usr/lib/libc.so.6 Thread 13 (Thread 0x7fd7b2c12700 (LWP 1312)): #0 0x7fd89329f48d in poll () at /usr/lib/libc.so.6 #1 0x7fd88e0b77a6 in () at /usr/lib/libglib-2.0.so.0 #2 0x7fd88e0b78bc in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7fd893bc306b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7fd893b6c89a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7fd89398ea73 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7fd7b54e40a7 in KCupsConnection::run() () at /usr/lib/libkcupslib.so #7 0x7fd8939936d8 in () at /usr/lib/libQt5Core.so.5 #8 0x7fd89285e454 in start_thread () at /usr/lib/libpthread.so.0 #9 0x7fd8932a87df in clone () at /usr/lib/libc.so.6 Thread 12 (Thread 0x7fd7cf7fe700 (LWP 1267)): #0 0x7fd8928644b8 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fd86efd0e44 in () at /usr/lib/libGLX_nvidia.so.0 #2 0x7fd86dbfc394 in () at /usr/lib/libnvidia-glcore.so.378.13 #3 0x7fd86efd012c in () at /usr/lib/libGLX_nvidia.so.0 #4 0x7fd89285e454 in start_thread () at /usr/lib/libpthread.so.0 #5 0x7fd8932a87df in clone () at /usr/lib/libc.so.6 Thread 11 (Thread 0x7fd7c700 (LWP 1266)): #0 0x7fd89286410f in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fd89399458b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7fd8976ed665 in () at /usr/lib/libQt5Quick.so.5 #3 0x7fd8976edf72 in () at /usr/lib/libQt5Quick.so.5 #4 0x7fd8939936d8 in () at /usr/lib/libQt5Core.so.5 #5 0x7fd89285e454 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7fd8932a87df in clone () at /usr/lib/libc.so.6 Thread 10 (Thread 0x7fd7d6d9e700 (LWP 1265)): #0 0x7fd8928644b8 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fd86efd0e44 in () at /usr/lib/libGLX_nvidia.so.0 #2 0x7fd86dbfc394 in () at /usr/lib/libnvidia-glcore.so.378.13 #3 0x7fd86efd012c in () at /usr/lib/libGLX_nvidia.so.0 #4 0x7fd89285e454 in start_thread () at /usr/lib/libpthread.so.0 #5 0x7fd8932a87df in clone () at /usr/lib/libc.so.6 Thread 9 (Thread 0x7fd7d759f700 (LWP 1264)): #0 0x7fd89286410f in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fd89399458b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7fd8976ed665 in () at /usr/lib/libQt5Quick.so.5 #3 0x7fd8976edf72 in () at /usr/lib/libQt5Quick.so.5 #4 0x7fd8939936d8 in () at /usr/lib/libQt5Core.so.5 #5 0x7fd89285e454 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7fd8932a87df in clone () at /usr/lib/libc.so.6 Thread 8 (Thread 0x7fd7dc9a9700 (LWP 1247)): #0 0x
[plasmashell] [Bug 341143] Wallpaper on every desktop is gone.
https://bugs.kde.org/show_bug.cgi?id=341143 --- Comment #239 from David H. --- Analogy time. Please bear with me, I promise that this is directly related to the bug report... Imagine you start a home business, and you set up a workshop in your garage to make or repair things. In that room you have a workbench, and on that bench you keep your various tools and working projects. Business is good, and you soon find yourself running out of space, so you set up a second bench near the first. And on it you have more tools, some of them being duplicates of those on the first bench, and others unique, so you can work on slightly different things. But you can also use the two benches in tandem when you have a really big project. Later on you add a third bench, and a fourth, and so on, to give you even more workspace. Now you also need an office to manage your business. That's in another room of your house. And in that room you have a desk with a computer, in/out-trays, pens and pencils, pads of paper, and other office supplies on it. As you become more successful you also put in a couple more tables, bookshelves, and cabinets and whatnot, each with its own collection of supplies, to help improve your productivity there too. In the rest of the house of course you also have a living area, with a TV, sofa, and various other facilities for relaxing, a kitchen/dining room for preparing food and eating it, a bedroom for sleeping, bathroom, whatever. Each room has its own purpose and its own unique set of accoutrements for fulfilling that purpose. And for the most part you keep each kind activity to its own space. You seldom, but not never, transfer what you're doing from one room to another. I hope you see where I'm going with this. Activities and Virtual Desktops, while being similar in many ways, are most definitely *not* the same thing. They categorize your work in different conceptual ways. Activities are like the various rooms, each focused *thematically* on a certain functional area. V.D.s are like the tables, benches, counters and other workspaces inside those rooms. They *spatially* organize the work you're doing and provide the actual tools with which to complete the various tasks within each area of activity. Now to apply this to the actual bug (and the proposed solutions and workarounds), I think most people are overlooking this foundational conceptual flaw that lies behind it -- the lack of recognition of the psychological separation between function space and work space, the differences in how we view them and react to them, and the differences in the work flows we set up within and between them. Activities and V.D.s perform complementary roles, not identical ones. Trying to replace or duplicate the one with the other is like saying four workshops with one bench each are basically the same thing as one workshop with four benches. They're not. Even if you put them right next to each other, cut doors between the rooms for easy access, and add pushcarts, conveyor belts, or whatever for the easy moving of projects between them, it's just never going to sit quite right in your mind or your behavior. You'd still be trying to fit a square peg into a round hole. Even worse, it could be seen as trying to put a workbench in your office, or an office desk in your workshop, or a toaster in your bathroom. Or say you do succeed in making the two experiences similar enough to not notice the difference. Then what was the point in changing it in the first place? Anyway, to my mind an ideal KDE set-up would provide the following: 1. The ability to set up one or more Activities, each of which can be centered around its own area of "business". 2. One or more Virtual Desktops inside each Activity, to provide the actual work areas in which to operate within that Activity's scope. 3. Full, individual, customizability of each Desktop inside each Activity, including... 3a. Setting the look and feel of each one so that it is clearly distinct from the others, the background being one of the most vital elements in creating that psychological, virtual "workspace". 3b. Individual customizability of the various widgets, toolbars and other features that populate each Desktop. 3c. The ability to set any single feature or tool as either unique to that Desktop or shared between all of them. Some features need to be always at hand, just as a workman might carry a toolbelt between workbenches with his most-used tools on it, while others can and should be confined to a certain workspace. 4. Multiple ways to quickly and easily navigate and move objects between Desktops, the ability to smoothly switch between Activities, and simple, but not necessarily as immediate, mechanisms for transferring and jumping to programs between Activities. Perhaps on occasion you really do need to put a toaster in the bathroom, but it will never be anywhere nearly as often as moving it from one kitchen counter to another. And really, th
[plasmashell] [Bug 377194] Crash after Arch-Linux update to plasma 5.9.3
https://bugs.kde.org/show_bug.cgi?id=377194 Antonio Rojas changed: What|Removed |Added CC||aro...@archlinux.org Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Antonio Rojas --- *** This bug has been marked as a duplicate of bug 375388 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 375388] Crash in QQuickItemPrivate::setEffectiveVisibleRecursive
https://bugs.kde.org/show_bug.cgi?id=375388 Antonio Rojas changed: What|Removed |Added CC||kde_b...@thannernet.de --- Comment #20 from Antonio Rojas --- *** Bug 377194 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 377192] Plasma shell crashed when I clicked on desktop menu button
https://bugs.kde.org/show_bug.cgi?id=377192 Antonio Rojas changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE CC||aro...@archlinux.org --- Comment #1 from Antonio Rojas --- *** This bug has been marked as a duplicate of bug 375388 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 375388] Crash in QQuickItemPrivate::setEffectiveVisibleRecursive
https://bugs.kde.org/show_bug.cgi?id=375388 Antonio Rojas changed: What|Removed |Added CC||kiv.ap...@gmail.com --- Comment #21 from Antonio Rojas --- *** Bug 377192 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 377190] Crash occures when clicking on the activity button on the desktop
https://bugs.kde.org/show_bug.cgi?id=377190 --- Comment #3 from David --- Activity button was maybe not the right name. I thought you could change activities with it, but I might be wrong. It's the button, which is always in a corner of the desktop. The bug report you marked this a duplicate of called it hamburger icon. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 377188] Cannot get smooth brush with OpenGL enabled
https://bugs.kde.org/show_bug.cgi?id=377188 Boudewijn Rempt changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE CC||b...@valdyas.org --- Comment #1 from Boudewijn Rempt --- *** This bug has been marked as a duplicate of bug 373676 *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 373676] Bent lines showing up on OSX.
https://bugs.kde.org/show_bug.cgi?id=373676 Boudewijn Rempt changed: What|Removed |Added CC||erich...@gmail.com --- Comment #3 from Boudewijn Rempt --- *** Bug 377188 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 377146] Brush color selection does not work on several brushes
https://bugs.kde.org/show_bug.cgi?id=377146 --- Comment #6 from b...@juno.com --- Hi, Dmitry, Thanks, but sadly, I barely understand a word of it. Is there a primer somewhere that can help me figure out what all the technical talk means? Thanks, Tedster On Sat, 04 Mar 2017 07:39:24 + Dmitry Kazakov writes: > https://bugs.kde.org/show_bug.cgi?id=377146 > > --- Comment #5 from Dmitry Kazakov --- > Hi, b-b1! > > You can find information about our brush engines in the official > manual: > > https://docs.krita.org/Category:Brush_Engines > > > > On 04.03.2017 05:02, bugzilla_nore...@kde.org wrote: > > https://bugs.kde.org/show_bug.cgi?id=377146 > > > > --- Comment #4 from b...@juno.com --- > > Oops, didn't mean to poke the bear. No, I just want to know how > to make > > them work, including how to use the ones I don't understand. Is > there > > another source of info that does not use technical terms to > answer > > technical problems? Like, could it tell me exactly what "painting > with > > surfaces", not colors, means? And how to access that, in terms of > "go to > > this spot and click this/choose that option"? > > I love what I have been able to get the program to do and don't > want to > > ditch the thing because I don't understand chunks of it. Much > better to > > learn how to work with those tools. > > Thanks > > > > > > > > On Fri, 03 Mar 2017 20:34:59 + Boudewijn Rempt > > writes: > >> https://bugs.kde.org/show_bug.cgi?id=377146 > >> > >> --- Comment #3 from Boudewijn Rempt --- > >> If this is too abstruse, don't use those brushes. Use other > brushes. > >> These > >> brushes are meant for people who need this feature; you don't > need > >> it, don't > >> use it! There are very likely more features in Krita that are > weird > >> or > >> incomprehensible unless you urgently need them. That doesn't > mean > >> the features > >> are buggy, though. > >> > >> -- > >> You are receiving this mail because: > >> You reported the bug. > > > > Warning: Don't Use Probiotics Before You See This > > Gundry MD > > > http://thirdpartyoffers.juno.com/TGL3141/58ba201053ca820102714st03vuc > > > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 377155] [Wayland] Caps Lock does not run on XWayland applications
https://bugs.kde.org/show_bug.cgi?id=377155 --- Comment #4 from tro...@free.fr --- I upgraded to XWayland 1.19.2 and the problem is still there. -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 377195] New: Cantor hangs at "Initializing session" when choosing R backend
https://bugs.kde.org/show_bug.cgi?id=377195 Bug ID: 377195 Summary: Cantor hangs at "Initializing session" when choosing R backend Product: cantor Version: 16.12 Platform: Other OS: Linux Status: UNCONFIRMED Severity: critical Priority: NOR Component: r-backend Assignee: fil...@kde.org Reporter: mich...@alzetta.org CC: alexanderrie...@gmail.com Target Milestone: --- It's the first time I try to use Cantor, my system is Gentoo, R version is 3.3.2 and cantor is 16.12.2. Bug description tells it all, actually. Any hints as to how I might debug this? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 377031] kwin crashed after unlock screen (2 local sessions)
https://bugs.kde.org/show_bug.cgi?id=377031 --- Comment #5 from Thomas Boerkel --- I tried to switch to Nouveau, but that is not working fast/stable enough on my hardware. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kxmlgui] [Bug 375555] Opening KDE apps gives multiples notifications about: "There are two actions(...) that want to use the same shortcut"
https://bugs.kde.org/show_bug.cgi?id=37 --- Comment #20 from Mav --- Created attachment 104361 --> https://bugs.kde.org/attachment.cgi?id=104361&action=edit Broken kdeglobals with duplicate shortcuts Using shortcuts "Reset to defaults" in the settings doesn't fix the errors produced by that config... -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kxmlgui] [Bug 375555] Opening KDE apps gives multiples notifications about: "There are two actions(...) that want to use the same shortcut"
https://bugs.kde.org/show_bug.cgi?id=37 --- Comment #21 from Mav --- Comment on attachment 104361 --> https://bugs.kde.org/attachment.cgi?id=104361 Broken kdeglobals with duplicate shortcuts At my end, I think the shortcuts were broken in a way long before the recent updates (I had some shortcuts throwing errors in Kate when used since many month), it seems that since 5.30 the errors just started being reported at app launch rather then when the shortcut is used. I'm skeptical I can reproduce breaking them, but may be we should check why resetting all shortcuts to defaults in the settings didn't fix the issue. I'm attaching my old/broken kdeglobals if you want to test with it. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 376494] Bin effect parameters do not reset properly
https://bugs.kde.org/show_bug.cgi?id=376494 Jean-Baptiste Mardelle changed: What|Removed |Added Latest Commit||https://commits.kde.org/kde ||nlive/d85742fcb1b62dcf1b0f4 ||e03532072615499fca8 Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #1 from Jean-Baptiste Mardelle --- Git commit d85742fcb1b62dcf1b0f4e03532072615499fca8 by Jean-Baptiste Mardelle. Committed on 04/03/2017 at 11:27. Pushed by mardelle into branch 'Applications/16.12'. Fix Bin Effect reset M +2-2src/bin/bin.cpp M +1-1src/bin/bin.h M +2-2src/bin/bincommands.cpp M +1-1src/bin/bincommands.h M +1-1src/effectstack/effectstackview2.cpp M +1-1src/effectstack/effectstackview2.h M +1-1src/mainwindow.cpp https://commits.kde.org/kdenlive/d85742fcb1b62dcf1b0f4e03532072615499fca8 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 341143] Wallpaper on every desktop is gone.
https://bugs.kde.org/show_bug.cgi?id=341143 --- Comment #240 from Bernd Paysan --- Am Samstag, 4. März 2017, 09:59:16 CET schrieb David H. : > I hope you see where I'm going with this. Activities and Virtual Desktops, > while being similar in many ways, are most definitely *not* the same thing. Actually, I think of virtual desktop as different "rooms" on my screen. This is, because a virtual desktop is spatially arranged, you go to the left, right, up or down from one desktop to the next. I usually have different activities on different desktops (not necessarily in the Plasma sense of "activity"), e.g. one desktop has shells and emacs, and is for programming, another desktop has Kontact and is for e-mail, the third desktop has Chromium, and is for browsing the web, the fourth has Digikam and is for processing photos. You get it. It's like the different rooms in your house's example. If I need more shells in the programming desktop (and yes, I need), I open more windows and more tabs per Konsole window. If I need more websites in the web-browsing desktop, I open more tabs. That is analogous to your benches: They are in the same room, they are visible and available at the same time. I liked KDE4's way to tie an activity to a virtual desktop, it made sense to also have different widgets in different virtual desktops (and especially different wallpapers to ease your orientation), and slide from one activity to the other just by pushing the mouse to the edge of the screen. I think the only thing that's now missing to fix this bug is to configure the desktop edge and desktop scrollwheel action to slide between different activities instead of different virtual desktops. Everything else is already in place: We have an activity pager which can replace the virtual desktop pager, when we switch between activities, it does slide (though not always in the right direction, as the activity pager looks 2D, but the activities are actually arranged only in one direction, horizontally). Your "thematically" vs. "spatially" is about the right way to think, but many of us separate thematically different things spatially. Like in your startup example: You have the garage for the workbenches (the "dirty" part of your startup), you have the working room with the computers, the living room for meetings (use the TV for presentations). You might also have a temporal relation, so in the evening, you change the way the rooms are used: The employees went home, and you can now use the TV in the living room as actual TV. Perhaps this is what the original "activity" designers imagined: Instead of quickly walking from one room to the other, you rearrange the room, and use it for something else. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 377196] Locking my screen loses X server
https://bugs.kde.org/show_bug.cgi?id=377196 Olivier Churlaud changed: What|Removed |Added Platform|Other |Archlinux Packages -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 377196] New: Locking my screen loses X server
https://bugs.kde.org/show_bug.cgi?id=377196 Bug ID: 377196 Summary: Locking my screen loses X server Product: plasmashell Version: 5.9.3 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: oliv...@churlaud.com CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 If I leave my computer locked for a long time, when I give my password to unlock, the plasma splashscreen (black screen with the spinner etc..) appears (but I'm already connected!) and I have to do CTRL+Alt+F2 (go to tty2) then CTRL+Alt+F1 (to come back to tty2, where my X Server is started) to make the splashscreen go. Then I cannot start X applications: $ kmail No protocol specified QXcbConnection: Could not connect to display :0 zsh: abort (core dumped) kmail At the end, I need to reboot to use my computer. -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 377134] Class method wrongly tagged as Qt signal if defined after class declaration with Q_SIGNALS as last section
https://bugs.kde.org/show_bug.cgi?id=377134 Sergio Martins changed: What|Removed |Added Latest Commit||https://commits.kde.org/cla ||zy/53c68bc6888f18409f8e803f ||b5b9c59f9b1d96c9 Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #2 from Sergio Martins --- Git commit 53c68bc6888f18409f8e803fb5b9c59f9b1d96c9 by Sergio Martins. Committed on 04/03/2017 at 12:32. Pushed by smartins into branch '1.1'. incorrect-emit: Fix two false positives When we're comparing a method's source location to check if it's affected by Q_SIGNAL we must use the first declaration of that method, and not other declarations which can also be a a definition, and live outside of the class Related: bug 377140 M +4-0src/AccessSpecifierManager.cpp M +2-4tests/incorrect-emit/config.json https://commits.kde.org/clazy/53c68bc6888f18409f8e803fb5b9c59f9b1d96c9 -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 377140] Signal methods no longer known as signals if signal method definition has been seen (e.g. with automoc)
https://bugs.kde.org/show_bug.cgi?id=377140 Sergio Martins changed: What|Removed |Added Status|CONFIRMED |RESOLVED Latest Commit||https://commits.kde.org/cla ||zy/53c68bc6888f18409f8e803f ||b5b9c59f9b1d96c9 Resolution|--- |FIXED --- Comment #2 from Sergio Martins --- Git commit 53c68bc6888f18409f8e803fb5b9c59f9b1d96c9 by Sergio Martins. Committed on 04/03/2017 at 12:32. Pushed by smartins into branch '1.1'. incorrect-emit: Fix two false positives When we're comparing a method's source location to check if it's affected by Q_SIGNAL we must use the first declaration of that method, and not other declarations which can also be a a definition, and live outside of the class Related: bug 377134 M +4-0src/AccessSpecifierManager.cpp M +2-4tests/incorrect-emit/config.json https://commits.kde.org/clazy/53c68bc6888f18409f8e803fb5b9c59f9b1d96c9 -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 377134] Class method wrongly tagged as Qt signal if defined after class declaration with Q_SIGNALS as last section
https://bugs.kde.org/show_bug.cgi?id=377134 --- Comment #3 from Sergio Martins --- please test! should work now -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 377197] New: Customize grouping behaviour
https://bugs.kde.org/show_bug.cgi?id=377197 Bug ID: 377197 Summary: Customize grouping behaviour Product: digikam Version: 5.5.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: AlbumsView-Group Assignee: digikam-de...@kde.org Reporter: freisi...@gmail.com Target Milestone: --- Created attachment 104362 --> https://bugs.kde.org/attachment.cgi?id=104362&action=edit Patch to customize grouping behaviour This extends the changes made in https://bugs.kde.org/show_bug.cgi?id=372027 As requested in the user mailing list, neither the old behaviour (disregard grouping) nor the behaviour introduces in the issue linked above (always operate on all group items) is ideal for all circumstances/users. This patch makes it customizable for operations where it makes sense/is possible. The behaviour is specifiable in the configuration in the "Miscellaneous" part. However this does not need to be specified manually by the user at all. By default these are set to "Ask", meaning a dialogue will pop up when an operation is run. There one can choose whether the operation should happen on all items in the group or not and a checkbox to remember the choice is provided. Also I found some dead/duplicate code related to icon and table view, which I centralized. In the end the whole patch got quite big. I can push it to a branch with the refactoring and grouping related code separated if you want. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 377198] New: Can't create a directory in the first level of a share in Dolphin (OK with other tool)
https://bugs.kde.org/show_bug.cgi?id=377198 Bug ID: 377198 Summary: Can't create a directory in the first level of a share in Dolphin (OK with other tool) Product: dolphin Version: 16.12.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: mathoj...@gmail.com Target Milestone: --- Hi, I noticed this problem for some months... I have an OpenMediaVault Server, on whitch I shared some Directories on the local Network. Those directories (an subdirectories) are set with chmod 770. Owner of every directories and files : Root Group of every directories and files : Users My user ID is of course in the users group. If I do a ls -l, all directories shared have this permissions : drwxrws---+ With Dolphin, when I want to enter one of thous shares, I'm prompted for my name, and password. I then enter the directory, and I can create a folder without problem. If I go back to the shares list, and enter another share, I'm not prompted for name and password anymore (that could be a problem too, but not mine for now). When I'm in this other share, I can't create a folder anymore. But I can do it in a subdirectory of this share... And If I use AndSMB on Android, I can create the folder I couldn't create in Dolphin. And in Dolphin, I could delete it without any problem. As it is working fine in AndSMB, I think it's a problem with Dolphin, or maybe kio an kio-extras. Thank you -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 377199] New: Cannot open multiple versions of Krita simultaneously
https://bugs.kde.org/show_bug.cgi?id=377199
Bug ID: 377199
Summary: Cannot open multiple versions of Krita simultaneously
Product: krita
Version: 3.1.2
Platform: Mac OS X Disk Images
OS: OS X
Status: UNCONFIRMED
Severity: minor
Priority: NOR
Component: general
Assignee: krita-bugs-n...@kde.org
Reporter: michi.schw...@gmail.com
Target Milestone: ---
I can't open multiple copies/versions of Krita at the same time, at least on OS
X 10.11.6. This makes testing for regressions and comparing the behaviour with
an older version very inconvenient.
Let's say I open Krita 3.1.2 and then double-click on Krita 3.1.1. The icon
briefly appears in the dock and then disappears again. Launching the binary
from the command line produces the following output:
$ /Applications/Krita\ 3.1.1.app/Contents/MacOS/krita
QCoreApplication::arguments: Please instantiate the QApplication object
first
krita.lib.pigment: Compiled for arch: 4
krita.lib.pigment: Features supported:
krita.lib.pigment: "SSE2" --- yes
krita.lib.pigment: "SSSE3"--- yes
krita.lib.pigment: "SSE4.1" --- yes
krita.lib.pigment: "AVX " --- no
krita.lib.pigment: "AVX2 "--- no
No "breeze" available.
Set style "fusion"
OpenGL Info
Vendor: ATI Technologies Inc.
Renderer: ATI Radeon HD 4850 OpenGL Engine
Version: 3.3 ATI-10.0.51
Shading language: 3.30
Requested format: QSurfaceFormat(version 3.2, options QFlags(),
depthBufferSize 24, redBufferSize -1, greenBufferSize -1, blueBufferSize -1,
alphaBufferSize -1, stencilBufferSize 8, samples -1, swapBehavior 2,
swapInterval 0, profile 1)
Current format:QSurfaceFormat(version 3.3, options QFlags(),
depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8,
alphaBufferSize -1, stencilBufferSize 8, samples -1, swapBehavior 2,
swapInterval 1, profile 1)
Version: 3 . 3
Supports deprecated functions false
krita has opengl true
Setting XDG_DATA_DIRS "/Applications/Krita 3.1.1.app/Contents/share"
Available translations QSet("en_US")
Available domain translations QSet("en_US")
Override language: ""
Comparing this to other applications on OS X/macOS, I would have assumed this
to just work. If there is some deeper, hard to fix problem preventing this
use-case from working, I would suggest that the second instance of Krita should
at least display a dialog explaining why this does now work.
--
You are receiving this mail because:
You are watching all bug changes.
[krita] [Bug 377199] Cannot open multiple versions of Krita simultaneously
https://bugs.kde.org/show_bug.cgi?id=377199 Michael Schwarz changed: What|Removed |Added CC||michi.schw...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 377199] Cannot open multiple versions of Krita simultaneously
https://bugs.kde.org/show_bug.cgi?id=377199 Michael Schwarz changed: What|Removed |Added CC|michi.schw...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 377191] Chroma key variance not working
https://bugs.kde.org/show_bug.cgi?id=377191 --- Comment #1 from Alexander van der Merwe --- After removing my debug outs, I'm now unable to get it working again. Seems like the parameter type change unfortunately isn't the solution. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 355872] svg icons in konqueror not displayed
https://bugs.kde.org/show_bug.cgi?id=355872 Roberto Castagnola changed: What|Removed |Added CC||roberto.castagn...@gmail.co ||m --- Comment #7 from Roberto Castagnola --- Same issue on Fedora 25 (konqueror version 4.14.25) and on Gentoo (konqueror version 5.0.97) With Right click -> Show Image, the icon is shown correctly. -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 376737] clazy-qstring-ref false positive with QVariant
https://bugs.kde.org/show_bug.cgi?id=376737 Sergio Martins changed: What|Removed |Added Latest Commit||https://commits.kde.org/cla ||zy/e6931ef2554c5b67e042bd5d ||1ed03a4bd7e4a19d Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #2 from Sergio Martins --- Git commit e6931ef2554c5b67e042bd5d1ed03a4bd7e4a19d by Sergio Martins. Committed on 04/03/2017 at 14:05. Pushed by smartins into branch '1.1'. qstring-ref: Don't warn when a QStringRef wouldn't compile For example when there's an implicit converstion to QVariant M +46 -3src/checks/level0/qstringref.cpp M +1-0src/checks/level0/qstringref.h M +1-2tests/qstring-ref/config.json https://commits.kde.org/clazy/e6931ef2554c5b67e042bd5d1ed03a4bd7e4a19d -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 374665] Logging out is nearly never possible
https://bugs.kde.org/show_bug.cgi?id=374665 --- Comment #9 from Kurt Seebauer --- still there in opensuse tumbleweed kde frameworks 5.31.0 wayland backtrace with debug symbols: Application: ksmserver-logout-greeter (ksmserver-logout-greeter), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f2c539b2e00 (LWP 11991))] Thread 7 (Thread 0x7f2c2db85700 (LWP 11997)): #0 0x7f2c49d6510f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f2c3721cf1b in ?? () from /usr/lib64/dri/radeonsi_dri.so #2 0x7f2c3721cd77 in ?? () from /usr/lib64/dri/radeonsi_dri.so #3 0x7f2c49d5f454 in start_thread () from /lib64/libpthread.so.0 #4 0x7f2c4f35937f in clone () from /lib64/libc.so.6 Thread 6 (Thread 0x7f2c2e386700 (LWP 11996)): #0 0x7f2c49d6510f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f2c3721cf1b in ?? () from /usr/lib64/dri/radeonsi_dri.so #2 0x7f2c3721cd77 in ?? () from /usr/lib64/dri/radeonsi_dri.so #3 0x7f2c49d5f454 in start_thread () from /lib64/libpthread.so.0 #4 0x7f2c4f35937f in clone () from /lib64/libc.so.6 Thread 5 (Thread 0x7f2c2eb87700 (LWP 11995)): #0 0x7f2c49d6510f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f2c3721cf1b in ?? () from /usr/lib64/dri/radeonsi_dri.so #2 0x7f2c3721cd77 in ?? () from /usr/lib64/dri/radeonsi_dri.so #3 0x7f2c49d5f454 in start_thread () from /lib64/libpthread.so.0 #4 0x7f2c4f35937f in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7f2c2f388700 (LWP 11994)): #0 0x7f2c49d6510f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f2c3721cf1b in ?? () from /usr/lib64/dri/radeonsi_dri.so #2 0x7f2c3721cd77 in ?? () from /usr/lib64/dri/radeonsi_dri.so #3 0x7f2c49d5f454 in start_thread () from /lib64/libpthread.so.0 #4 0x7f2c4f35937f in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7f2c2fdc3700 (LWP 11993)): #0 0x7f2c49d6510f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f2c3721cf1b in ?? () from /usr/lib64/dri/radeonsi_dri.so #2 0x7f2c3721cd77 in ?? () from /usr/lib64/dri/radeonsi_dri.so #3 0x7f2c49d5f454 in start_thread () from /lib64/libpthread.so.0 #4 0x7f2c4f35937f in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f2c3d167700 (LWP 11992)): #0 0x7f2c4f35066d in poll () from /lib64/libc.so.6 #1 0x7f2c48011896 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f2c480119ac in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f2c4fc7018b in QEventDispatcherGlib::processEvents (this=0x7f2c380008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f2c4fc19aea in QEventLoop::exec (this=this@entry=0x7f2c3d166c50, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #5 0x7f2c4fa47813 in QThread::exec (this=) at thread/qthread.cpp:507 #6 0x7f2c507c3385 in ?? () from /usr/lib64/libQt5DBus.so.5 #7 0x7f2c4fa4c4c8 in QThreadPrivate::start (arg=0x7f2c50a34d20) at thread/qthread_unix.cpp:368 #8 0x7f2c49d5f454 in start_thread () from /lib64/libpthread.so.0 #9 0x7f2c4f35937f in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f2c539b2e00 (LWP 11991)): [KCrash Handler] #6 0x7f2c4a7ea029 in wl_map_insert_at (map=, flags=flags@entry=0, i=, data=) at src/wayland-util.c:249 #7 0x7f2c4a7e61fe in proxy_destroy (proxy=0x107c740) at src/wayland-client.c:411 #8 wl_proxy_destroy (proxy=0x107c740) at src/wayland-client.c:442 #9 0x7f2c52d1b415 in wl_registry_destroy (wl_registry=) at /usr/include/wayland/wayland-client-protocol.h:1065 #10 KWayland::Client::WaylandPointer::release (this=0x106cc80, this=0x106cc80) at /usr/src/debug/kwayland-5.31.0/src/client/wayland_pointer_p.h:53 #11 KWayland::Client::Registry::release (this=this@entry=0x106cbe0) at /usr/src/debug/kwayland-5.31.0/src/client/registry.cpp:358 #12 0x7f2c52d1b43c in KWayland::Client::Registry::~Registry (this=0x106cbe0, __in_chrg=) at /usr/src/debug/kwayland-5.31.0/src/client/registry.cpp:353 #13 0x7f2c52d1b4d9 in KWayland::Client::Registry::~Registry (this=0x106cbe0, __in_chrg=) at /usr/src/debug/kwayland-5.31.0/src/client/registry.cpp:354 #14 0x7f2c4fc45f31 in QObjectPrivate::deleteChildren (this=this@entry=0x1070390) at kernel/qobject.cpp:1970 #15 0x7f2c4fc4f2bf in QObject::~QObject (this=, __in_chrg=) at kernel/qobject.cpp:1041 #16 0x7f2c2672f7e3 in WaylandIntegration::~WaylandIntegration (this=, __in_chrg=) at /usr/src/debug/kwayland-integration-5.9.3/src/windowsystem/waylandintegration.cpp:51 #17 WaylandIntegrationSingleton::~WaylandIntegrationSingleton (this=, __in_chrg=) at /usr/src/debug/kwayland-integration-5.9.3/src/windowsystem/waylandintegration.cpp:37 #18 (anonymous namespace)::Q_QGS_privateWaylandIntegrationSelf::Holder::~Holder (this=, __in_chrg=) at /usr/src/debug/kwayland-integration-5.9.3/src/window
[frameworks-kio] [Bug 377165] Looks like KIO wasn't tested when samba is installed but not started and fills logs with error messages
https://bugs.kde.org/show_bug.cgi?id=377165 --- Comment #1 from David Faure --- What happens on your system when you run the command `net usershare info` in a terminal? What is printed? If you could redirect it to a file and attach it here that would be even better ;) Thanks. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 377144] Make folder dialog maximizes to dolphin window
https://bugs.kde.org/show_bug.cgi?id=377144 --- Comment #3 from David Faure --- Cannot reproduce this either, not even the dialog remembering its size. The code is a QDialog created in KNewFileMenu::createDirectory, and there is nothing there about saving/restoring size, it's supposed to come with the default size every time. Can you still reproduce the issue now that you resized the dialog? If so, can you test if it also happens in the english locale? (start `LANG=en_US.UTF-8 dolphin` in a terminal) -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 187116] Holidays > 1 day show as multiple holidays.
https://bugs.kde.org/show_bug.cgi?id=187116 Sergio Martins changed: What|Removed |Added Assignee|smart...@kde.org|korganizer-de...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 321233] Import of ics files fails
https://bugs.kde.org/show_bug.cgi?id=321233 Sergio Martins changed: What|Removed |Added Assignee|smart...@kde.org|korganizer-de...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 209541] Akonadi iCal resource cannot be reloaded/refreshed
https://bugs.kde.org/show_bug.cgi?id=209541 Sergio Martins changed: What|Removed |Added Assignee|smart...@kde.org|kdepim-b...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 281213] Birthdays are automatically extracted from my kabc vcard contacts and shown in my calendar. The birthdays appear twice.
https://bugs.kde.org/show_bug.cgi?id=281213 Sergio Martins changed: What|Removed |Added Assignee|smart...@kde.org|kdepim-b...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 376365] KFileWidget does not support : in filenames
https://bugs.kde.org/show_bug.cgi?id=376365 --- Comment #4 from David Faure --- Thanks for fixing the bug, it can be closed now, right? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 377199] Cannot open multiple versions of Krita simultaneously
https://bugs.kde.org/show_bug.cgi?id=377199 Boudewijn Rempt changed: What|Removed |Added Resolution|--- |LATER Status|UNCONFIRMED |RESOLVED CC||b...@valdyas.org --- Comment #1 from Boudewijn Rempt --- That's not a bug, but a feature, requested by users. It means that newly opened documents go into the existing krita window, instead of in a new process/window. We might be adding a commandline flag to disable the single-application mode at some point, but that's not going to happen soon. -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 376128] SMB://server/dir Timeout on Server server in Dolphin
https://bugs.kde.org/show_bug.cgi?id=376128 David Faure changed: What|Removed |Added Component|general |default Product|frameworks-kio |kio-extras Assignee|fa...@kde.org |plasma-de...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 377134] Class method wrongly tagged as Qt signal if defined after class declaration with Q_SIGNALS as last section
https://bugs.kde.org/show_bug.cgi?id=377134 --- Comment #4 from Friedrich W. H. Kossebau --- Thanks for the quick fix, Sergio! Can confirm that this fixes both this bug and 377140 for what I have seen them with Okteta builds. ((Darn, and I could have taken some pride here, as I was pretty close to fix this myself then, as I was searching for a method like getCanonicalDecl, but gave up as the llvm lingo did not match my c++ one and then also was already mentally in bed :) )) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 376365] KFileWidget does not support : in filenames
https://bugs.kde.org/show_bug.cgi?id=376365 --- Comment #5 from Fabian Vogt --- (In reply to David Faure from comment #4) > Thanks for fixing the bug, it can be closed now, right? IMO not quite: > However, IMO the API needs to be changed to be less ambiguous. A QString as argument that accepts both URLs and filenames can't ever work as valid URLs are also valid filesystem paths. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 372597] /usr/bin/kaccess crashes when started in a Wayland Session
https://bugs.kde.org/show_bug.cgi?id=372597 Kurt Seebauer changed: What|Removed |Added CC||kurt_seeba...@yahoo.de --- Comment #17 from Kurt Seebauer --- New backtrace with debug symbols Distribution: opensuse tumbleweed (march 4th 2017) KDE frameworks: 5.31.0 Qt: 5.7.1 wayland Application: KDE Accessibility Tool (kaccess), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fcd89751540 (LWP 7352))] Thread 2 (Thread 0x7fcd76321700 (LWP 7353)): #0 0x7fcd890d56dd in read () from /lib64/libc.so.6 #1 0x7fcd7e9aeba0 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7fcd7e96a35e in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #3 0x7fcd7e96a834 in ?? () from /usr/lib64/libglib-2.0.so.0 #4 0x7fcd7e96a9ac in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #5 0x7fcd857a018b in QEventDispatcherGlib::processEvents (this=0x7fcd78c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #6 0x7fcd85749aea in QEventLoop::exec (this=this@entry=0x7fcd76320c50, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #7 0x7fcd85577813 in QThread::exec (this=) at thread/qthread.cpp:507 #8 0x7fcd8228b385 in ?? () from /usr/lib64/libQt5DBus.so.5 #9 0x7fcd8557c4c8 in QThreadPrivate::start (arg=0x7fcd824fcd20) at thread/qthread_unix.cpp:368 #10 0x7fcd80466454 in start_thread () from /lib64/libpthread.so.0 #11 0x7fcd890e237f in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7fcd89751540 (LWP 7352)): [KCrash Handler] #6 0x7fcd74f60029 in wl_map_insert_at (map=, flags=flags@entry=0, i=, data=) at src/wayland-util.c:249 #7 0x7fcd74f5c1fe in proxy_destroy (proxy=0xcb84b0) at src/wayland-client.c:411 #8 wl_proxy_destroy (proxy=0xcb84b0) at src/wayland-client.c:442 #9 0x7fcd742a0415 in wl_registry_destroy (wl_registry=) at /usr/include/wayland/wayland-client-protocol.h:1065 #10 KWayland::Client::WaylandPointer::release (this=0xcb4090, this=0xcb4090) at /usr/src/debug/kwayland-5.31.0/src/client/wayland_pointer_p.h:53 #11 KWayland::Client::Registry::release (this=this@entry=0xcb1420) at /usr/src/debug/kwayland-5.31.0/src/client/registry.cpp:358 #12 0x7fcd742a043c in KWayland::Client::Registry::~Registry (this=0xcb1420, __in_chrg=) at /usr/src/debug/kwayland-5.31.0/src/client/registry.cpp:353 #13 0x7fcd742a04d9 in KWayland::Client::Registry::~Registry (this=0xcb1420, __in_chrg=) at /usr/src/debug/kwayland-5.31.0/src/client/registry.cpp:354 #14 0x7fcd85775f31 in QObjectPrivate::deleteChildren (this=this@entry=0xcbe210) at kernel/qobject.cpp:1970 #15 0x7fcd8577f2bf in QObject::~QObject (this=, __in_chrg=) at kernel/qobject.cpp:1041 #16 0x7fcd6e1557e3 in WaylandIntegration::~WaylandIntegration (this=, __in_chrg=) at /usr/src/debug/kwayland-integration-5.9.3/src/windowsystem/waylandintegration.cpp:51 #17 WaylandIntegrationSingleton::~WaylandIntegrationSingleton (this=, __in_chrg=) at /usr/src/debug/kwayland-integration-5.9.3/src/windowsystem/waylandintegration.cpp:37 #18 (anonymous namespace)::Q_QGS_privateWaylandIntegrationSelf::Holder::~Holder (this=, __in_chrg=) at /usr/src/debug/kwayland-integration-5.9.3/src/windowsystem/waylandintegration.cpp:43 #19 0x7fcd8902fea0 in __run_exit_handlers () from /lib64/libc.so.6 #20 0x7fcd8902fefa in exit () from /lib64/libc.so.6 #21 0x7fcd89019298 in __libc_start_main () from /lib64/libc.so.6 #22 0x0040068a in _start () at ../sysdeps/x86_64/start.S:120 -- You are receiving this mail because: You are watching all bug changes.
[kgpg] [Bug 375029] decrypting files via GUI can delete files permanently
https://bugs.kde.org/show_bug.cgi?id=375029 Rettich changed: What|Removed |Added CC||sebastian.rad...@gmx.de --- Comment #1 from Rettich --- I have the same problem since the last update. In addition, "kgpg -s" does not work at all if the kgpg is already running. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 377200] New: KWrite crashed while invoking `search next'
https://bugs.kde.org/show_bug.cgi?id=377200 Bug ID: 377200 Summary: KWrite crashed while invoking `search next' Product: kate Version: unspecified Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: kwrite Assignee: kwrite-bugs-n...@kde.org Reporter: qinq_...@buaa.edu.cn Target Milestone: --- Application: kwrite (16.08.3) (Compiled from sources) Qt Version: 5.7.1 Frameworks Version: 5.31.0 Operating System: Linux 4.9.6-gentoo-r1 x86_64 Distribution: "NAME=Gentoo" -- Information about the crash: - What I was doing when the application crashed: Clicked `F3' to manually replace some terms when the term to be searched has all cleared. Then KWrite crashed. Seems that KWrite cannot use `F3' to search any pattern that does not appear in the file. - Custom settings of the application: Vi mode The crash can be reproduced every time. -- Backtrace: Application: KWrite (kwrite), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f7f7ec0f800 (LWP 16945))] Thread 3 (Thread 0x7f7f6c937700 (LWP 16946)): #0 0x7f7f7b5b85ed in poll () from /lib64/libc.so.6 #1 0x7f7f749a48f2 in ?? () from /usr/lib64/libxcb.so.1 #2 0x7f7f749a66df in xcb_wait_for_event () from /usr/lib64/libxcb.so.1 #3 0x7f7f6ee9d369 in ?? () from /usr/lib64/libQt5XcbQpa.so.5 #4 0x7f7f7bc7356c in ?? () from /usr/lib64/libQt5Core.so.5 #5 0x7f7f77ca84a4 in start_thread () from /lib64/libpthread.so.0 #6 0x7f7f7b5c166d in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f7f64715700 (LWP 16947)): #0 0x7f7f7bc6bea6 in QMutex::unlock() () from /usr/lib64/libQt5Core.so.5 #1 0x7f7f7be6001d in ?? () from /usr/lib64/libQt5Core.so.5 #2 0x7f7f7620b73d in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0 #3 0x7f7f7620c128 in ?? () from /usr/lib64/libglib-2.0.so.0 #4 0x7f7f7620c30c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #5 0x7f7f7be6013c in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #6 0x7f7f7be1401a in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #7 0x7f7f7bc6f044 in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #8 0x7f7f7ec98445 in ?? () from /usr/lib64/libQt5DBus.so.5 #9 0x7f7f7bc7356c in ?? () from /usr/lib64/libQt5Core.so.5 #10 0x7f7f77ca84a4 in start_thread () from /lib64/libpthread.so.0 #11 0x7f7f7b5c166d in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f7f7ec0f800 (LWP 16945)): [KCrash Handler] #6 0x7f7f7c20eb6c in QTextLine::width() const () from /usr/lib64/libQt5Gui.so.5 #7 0x7f7f7e7a74ea in ?? () from /usr/lib64/libKF5TextEditor.so.5 #8 0x7f7f7e7fbe20 in ?? () from /usr/lib64/libKF5TextEditor.so.5 #9 0x7f7f7e88095b in KateVi::ModeBase::goToPos(KateVi::Range const&) () from /usr/lib64/libKF5TextEditor.so.5 #10 0x7f7f7e8c85b5 in ?? () from /usr/lib64/libKF5TextEditor.so.5 #11 0x7f7f7e8d5740 in ?? () from /usr/lib64/libKF5TextEditor.so.5 #12 0x7f7f7be3af2f in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib64/libQt5Core.so.5 #13 0x7f7f7c652c02 in QAction::triggered(bool) () from /usr/lib64/libQt5Widgets.so.5 #14 0x7f7f7c65584d in QAction::activate(QAction::ActionEvent) () from /usr/lib64/libQt5Widgets.so.5 #15 0x7f7f7c656267 in QAction::event(QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #16 0x7f7f7c659e2c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #17 0x7f7f7c661350 in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #18 0x7f7f7be15340 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib64/libQt5Core.so.5 #19 0x7f7f7c174629 in QShortcutMap::dispatchEvent(QKeyEvent*) () from /usr/lib64/libQt5Gui.so.5 #20 0x7f7f7c174714 in QShortcutMap::tryShortcut(QKeyEvent*) () from /usr/lib64/libQt5Gui.so.5 #21 0x7f7f7c12f9ba in QWindowSystemInterface::handleShortcutEvent(QWindow*, unsigned long, int, QFlags, unsigned int, unsigned int, unsigned int, QString const&, bool, unsigned short) () from /usr/lib64/libQt5Gui.so.5 #22 0x7f7f7c1451bc in QGuiApplicationPrivate::processKeyEvent(QWindowSystemInterfacePrivate::KeyEvent*) () from /usr/lib64/libQt5Gui.so.5 #23 0x7f7f7c14a455 in QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) () from /usr/lib64/libQt5Gui.so.5 #24 0x7f7f7c12ae73 in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () from /usr/lib64/libQt5Gui.so.5 #25 0x7f7f6eecd0b0 in ?? () from /usr/lib64/libQt5XcbQpa.so.5 #26 0x7f7f7620bf7d in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #27 0x7f7f7620c260 in ?? () from /usr/lib64/libgl
[konqueror] [Bug 377201] New: Home Folder button not working in web browser mode
https://bugs.kde.org/show_bug.cgi?id=377201 Bug ID: 377201 Summary: Home Folder button not working in web browser mode Product: konqueror Version: 5.0.97 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: konq-b...@kde.org Reporter: roberto.castagn...@gmail.com Target Milestone: --- Created attachment 104363 --> https://bugs.kde.org/attachment.cgi?id=104363&action=edit Fix 'Home Folder' button action While in web browser mode, if I use 'Home Folder' button I get the error ERR_UNKNOWN_URL_SCHEME I got it solved with attached patch. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 377202] New: Empty DJVU page displayed in black
https://bugs.kde.org/show_bug.cgi?id=377202 Bug ID: 377202 Summary: Empty DJVU page displayed in black Product: okular Version: 0.25.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: DjVu backend Assignee: okular-de...@kde.org Reporter: trufano...@gmail.com Target Milestone: --- Created attachment 104364 --> https://bugs.kde.org/attachment.cgi?id=104364&action=edit sample doc If I open a djvu document in Okular its empty pages are displayed in black or even with some artifacts instead of solid white color. All other viewers display such documents correctly. The sample one page djvu is attached. This djvu is made with DJVU Small 0.4.4 from one solid white tiff page. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 377203] New: GUI corrupted under Gnome Wayland session
https://bugs.kde.org/show_bug.cgi?id=377203 Bug ID: 377203 Summary: GUI corrupted under Gnome Wayland session Product: gwenview Version: 16.12.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: yy...@gmx.com CC: myr...@kde.org Target Milestone: --- gwenview is unusable on Gnome 3.22.2 (Arch) because the problem shown on the screencast. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 377202] Empty DJVU page displayed in black
https://bugs.kde.org/show_bug.cgi?id=377202 truf changed: What|Removed |Added Platform|Other |Kubuntu Packages --- Comment #1 from truf --- Environment: Kubuntu 16.10 djvulibre 3.5.27.1-6 okular 4:16.04.3-0ubuntu1 -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 377203] GUI corrupted under Gnome Wayland session
https://bugs.kde.org/show_bug.cgi?id=377203 --- Comment #1 from Dr. Chapatin --- screencast link https://www.youtube.com/watch?v=wOFHw68B4Wc -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 377204] New: DOSBox 0.47 causes crash of kwin_x11
https://bugs.kde.org/show_bug.cgi?id=377204 Bug ID: 377204 Summary: DOSBox 0.47 causes crash of kwin_x11 Product: kwin Version: 5.9.3 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: koffeinfried...@gmail.com Target Milestone: --- Application: kwin_x11 (5.9.3) Qt Version: 5.8.0 Frameworks Version: 5.31.0 Operating System: Linux 4.9.11-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: Just playing good old games in DOSBox Version 0.74 - in Detail it was "World of Xeen" and I did a levelup, but I think this won't help you tracking this. -- Backtrace: Application: KWin (kwin_x11), signal: Aborted Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f559f557840 (LWP 780))] Thread 5 (Thread 0x7f557ce43700 (LWP 8646)): #0 0x7f559ef8a551 in ppoll () at /usr/lib/libc.so.6 #1 0x7f559c60f2f9 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/libQt5Core.so.5 #2 0x7f559c61096a in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #3 0x7f559c5bd89a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f559c3dfa73 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #5 0x7f559c3e46d8 in () at /usr/lib/libQt5Core.so.5 #6 0x7f55981d1454 in start_thread () at /usr/lib/libpthread.so.0 #7 0x7f559ef937df in clone () at /usr/lib/libc.so.6 Thread 4 (Thread 0x7f5574ec0700 (LWP 861)): #0 0x7f55981d710f in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f559b54e234 in () at /usr/lib/libQt5Script.so.5 #2 0x7f559b54e279 in () at /usr/lib/libQt5Script.so.5 #3 0x7f55981d1454 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f559ef937df in clone () at /usr/lib/libc.so.6 Thread 3 (Thread 0x7f557eccc700 (LWP 806)): #0 0x7f559ef8a551 in ppoll () at /usr/lib/libc.so.6 #1 0x7f559c60f2f9 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/libQt5Core.so.5 #2 0x7f559c61096a in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #3 0x7f559c5bd89a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f559c3dfa73 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #5 0x7f55960b1125 in () at /usr/lib/libQt5DBus.so.5 #6 0x7f559c3e46d8 in () at /usr/lib/libQt5Core.so.5 #7 0x7f55981d1454 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f559ef937df in clone () at /usr/lib/libc.so.6 Thread 2 (Thread 0x7f5584cda700 (LWP 794)): #0 0x7f559ef8a48d in poll () at /usr/lib/libc.so.6 #1 0x7f559e0a68e0 in () at /usr/lib/libxcb.so.1 #2 0x7f559e0a8679 in xcb_wait_for_event () at /usr/lib/libxcb.so.1 #3 0x7f558598a239 in () at /usr/lib/libQt5XcbQpa.so.5 #4 0x7f559c3e46d8 in () at /usr/lib/libQt5Core.so.5 #5 0x7f55981d1454 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f559ef937df in clone () at /usr/lib/libc.so.6 Thread 1 (Thread 0x7f559f557840 (LWP 780)): [KCrash Handler] #6 0x7f559eede04f in raise () at /usr/lib/libc.so.6 #7 0x7f559eedf47a in abort () at /usr/lib/libc.so.6 #8 0x7f559c3cae21 in () at /usr/lib/libQt5Core.so.5 #9 0x7f559c3ded04 in QThread::~QThread() () at /usr/lib/libQt5Core.so.5 #10 0x7f559c3dedf9 in QThread::~QThread() () at /usr/lib/libQt5Core.so.5 #11 0x7f559c5e9411 in QObjectPrivate::deleteChildren() () at /usr/lib/libQt5Core.so.5 #12 0x7f559c5f2d6f in QObject::~QObject() () at /usr/lib/libQt5Core.so.5 #13 0x7f557e2a8c49 in KWin::X11StandalonePlatform::~X11StandalonePlatform() () at /usr/lib/qt/plugins/org.kde.kwin.platforms/KWinX11Platform.so #14 0x7f559c5e9411 in QObjectPrivate::deleteChildren() () at /usr/lib/libQt5Core.so.5 #15 0x7f559c5f2d6f in QObject::~QObject() () at /usr/lib/libQt5Core.so.5 #16 0x7f559c5c0f56 in QCoreApplication::~QCoreApplication() () at /usr/lib/libQt5Core.so.5 #17 0x7f559d2a1dc1 in QApplication::~QApplication() () at /usr/lib/libQt5Widgets.so.5 #18 0x7f559f250834 in () at /usr/lib/libkdeinit5_kwin_x11.so #19 0x7f559f2523e0 in kdemain () at /usr/lib/libkdeinit5_kwin_x11.so #20 0x7f559eecb291 in __libc_start_main () at /usr/lib/libc.so.6 #21 0x0040069a in _start () Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 377205] New: Cannot open .jpg or .png images with gwenview
https://bugs.kde.org/show_bug.cgi?id=377205 Bug ID: 377205 Summary: Cannot open .jpg or .png images with gwenview Product: gwenview Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: thomas_o...@yahoo.se CC: myr...@kde.org Target Milestone: --- Application: gwenview (15.12.3) Qt Version: 5.5.1 Operating System: Linux 4.4.0-64-generic x86_64 Distribution: Ubuntu 16.04.2 LTS -- Information about the crash: - What I was doing when the application crashed: Browsing files with Dolphin filemanager. Every time I try to open a .jpg or .png, Gwenview crashes. Also there are no preview icons showed for thes imagetypes in Dolphin. System just upgraded to 16.04. The crash can be reproduced every time. -- Backtrace: Application: Gwenview (gwenview), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [KCrash Handler] #6 0x7fdf01d3e428 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:54 #7 0x7fdf01d4002a in __GI_abort () at abort.c:89 #8 0x7fdf01d807ea in __libc_message (do_abort=do_abort@entry=2, fmt=fmt@entry=0x7fdf01e992e0 "*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:175 #9 0x7fdf01d88e0a in malloc_printerr (ar_ptr=, ptr=, str=0x7fdf01e960b2 "free(): invalid pointer", action=3) at malloc.c:5004 #10 _int_free (av=, p=, have_lock=0) at malloc.c:3865 #11 0x7fdf01d8c98c in __GI___libc_free (mem=) at malloc.c:2966 #12 0x7fdf0651ad00 in __gnu_cxx::new_allocator::deallocate (this=0x7ffe8c703620, __p=) at /usr/include/c++/5/ext/new_allocator.h:110 #13 std::allocator_traits >::deallocate (__a=..., __n=, __p=) at /usr/include/c++/5/bits/alloc_traits.h:517 #14 std::__cxx11::basic_string, std::allocator >::_M_destroy (__size=, this=0x7ffe8c703620) at /usr/include/c++/5/bits/basic_string.h:185 #15 std::__cxx11::basic_string, std::allocator >::_M_dispose (this=0x7ffe8c703620) at /usr/include/c++/5/bits/basic_string.h:180 #16 std::__cxx11::basic_string, std::allocator >::~basic_string (this=0x7ffe8c703620, __in_chrg=) at /usr/include/c++/5/bits/basic_string.h:543 #17 Gwenview::ImageMetaInfoModel::setExiv2Image (this=, image=0x7fdedc003120) at /build/gwenview-iJ9mAT/gwenview-15.12.3/lib/imagemetainfomodel.cpp:368 #18 0x7fdf064e2b04 in Gwenview::Document::setExiv2Image (this=0x1b25270, image=...) at /build/gwenview-iJ9mAT/gwenview-15.12.3/lib/document/document.cpp:395 #19 0x7fdf064e1b71 in Gwenview::AbstractDocumentImpl::setDocumentExiv2Image (this=this@entry=0x1b22660, image=...) at /build/gwenview-iJ9mAT/gwenview-15.12.3/lib/document/abstractdocumentimpl.cpp:82 #20 0x7fdf064e8c8a in Gwenview::LoadingDocumentImpl::slotMetaInfoLoaded (this=0x1b22660) at /build/gwenview-iJ9mAT/gwenview-15.12.3/lib/document/loadingdocumentimpl.cpp:491 #21 0x7fdf02708d2a in QMetaObject::activate (sender=0x1ae78e8, signalOffset=, local_signal_index=, argv=) at kernel/qobject.cpp:3713 #22 0x7fdf024f10ee in QFutureWatcherBase::event (this=, event=0x7fdedc003020) at thread/qfuturewatcher.cpp:338 #23 0x7fdf0399d05c in QApplicationPrivate::notify_helper (this=this@entry=0x16284a0, receiver=receiver@entry=0x1ae78e8, e=e@entry=0x7fdedc003020) at kernel/qapplication.cpp:3716 #24 0x7fdf039a2516 in QApplication::notify (this=0x7ffe8c703e20, receiver=0x1ae78e8, e=0x7fdedc003020) at kernel/qapplication.cpp:3499 #25 0x7fdf026da38b in QCoreApplication::notifyInternal (this=0x7ffe8c703e20, receiver=0x1ae78e8, event=event@entry=0x7fdedc003020) at kernel/qcoreapplication.cpp:965 #26 0x7fdf026dc786 in QCoreApplication::sendEvent (event=0x7fdedc003020, receiver=) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:224 #27 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x161c550) at kernel/qcoreapplication.cpp:1593 #28 0x7fdf026dcc68 in QCoreApplication::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1451 #29 0x7fdf027303c3 in postEventSourceDispatch (s=0x1660180) at kernel/qeventdispatcher_glib.cpp:271 #30 0x7fdefcd9b197 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #31 0x7fdefcd9b3f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #32 0x7fdefcd9b49c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #33 0x7fdf027307cf in QEventDispatcherGlib::processEvents (this=0x16654b0, flags=...) at kernel/qeventdispatcher_glib.cpp:418 #34 0x7fdf026d7b4a in QEventLoop::exec (this=this@entry=0x7ffe8c703d10, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #35 0x7fdf026dfbec in QCoreApplication::exec () at k
[frameworks-kio] [Bug 377165] Looks like KIO wasn't tested when samba is installed but not started and fills logs with error messages
https://bugs.kde.org/show_bug.cgi?id=377165 Serhiy Zahoriya changed: What|Removed |Added Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED --- Comment #2 from Serhiy Zahoriya --- Yesterday I've deleted samba to get rid of these messages and after installing and disabling it again I can no longer reproduce this. Maybe it was due to some permissions issue on this /var/run/samba/ folder. It's an old system upgraded many times after all. Closing this for now, sorry for disturbing. Short version for anyone finding this by same errors: try reinstalling samba as a workaround. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 377144] Make folder dialog maximizes to dolphin window
https://bugs.kde.org/show_bug.cgi?id=377144 --- Comment #4 from Alex --- Created attachment 104365 --> https://bugs.kde.org/attachment.cgi?id=104365&action=edit Reproducing with enUS locale and closing -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 377171] Clicking outside of any presented windows should show desktop
https://bugs.kde.org/show_bug.cgi?id=377171 --- Comment #3 from Martin Gräßlin --- The behavior of software must be predictable. Something unexpected happening and assuming that users would learn quickly is terrible. Users don't want to learn by having unexpected behavior. If something happens they did not expect they call the software buggy and might move away from the software. Users want to be able to trust their system. Unexpected behavior destroys trust. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 377206] New: Sort templates and camera filter ins configuration
https://bugs.kde.org/show_bug.cgi?id=377206 Bug ID: 377206 Summary: Sort templates and camera filter ins configuration Product: digikam Version: 5.5.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: setup Assignee: digikam-de...@kde.org Reporter: freisi...@gmail.com Target Milestone: --- Created attachment 104366 --> https://bugs.kde.org/attachment.cgi?id=104366&action=edit sort lits in configuration As requested by Wolfgang, I am plucking the low-hanging fruit. This enables interactive sorting for templates and fixed sorting for camera input filter list. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 376365] KFileWidget does not support : in filenames
https://bugs.kde.org/show_bug.cgi?id=376365 --- Comment #6 from David Faure --- Oh, indeed, I hadn't seen that. I completely agree, the same API with a QString can't be for relative paths and for URLs, "a:b" is both. How about we add a KFileWidget::setSelectedUrl(const QUrl& url)? Then we can get rid of this ugly .toString() (QUrl -> QString -> QUrl). -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 377207] New: Kdenlive crashes upon attempt to add the "motion tracker" effect to a clip
https://bugs.kde.org/show_bug.cgi?id=377207
Bug ID: 377207
Summary: Kdenlive crashes upon attempt to add the "motion
tracker" effect to a clip
Product: kdenlive
Version: 16.12.2
Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
Severity: crash
Priority: NOR
Component: Effects & Transitions
Assignee: vpi...@kde.org
Reporter: krewe...@interia.pl
Target Milestone: ---
Attempted to add the "motion tracker" effect to a clip in a timeline, whilst 2
other clips already have this effect applied.
Irrespectively of whether the clip is "proxy" or not, application crashes upon
selectin blur value greater than 0 ("zero").
Disabling the effect with little eye icon, or removing the effect from the
affected clip, whilst leaving this effect applied on all other clips, does not
make Kdenlive to crash.
Defect repeatable, happens every time.
KDE DE, Kdenlive 16.12.2, Manjaro Linux stable branch (fully updated)
The crash can be reproduced every time.
===
-- Backtrace:
Application: Kdenlive (kdenlive), signal: Aborted
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fc68cc4b800 (LWP 6240))]
Thread 13 (Thread 0x7fc5e9cc4700 (LWP 6304)):
#0 0x7fc684b9848d in poll () at /usr/lib/libc.so.6
#1 0x7fc67c9c47a6 in () at /usr/lib/libglib-2.0.so.0
#2 0x7fc67c9c48bc in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3 0x7fc6857c006b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4 0x7fc68576989a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5 0x7fc68558ba73 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6 0x7fc6855906d8 in () at /usr/lib/libQt5Core.so.5
#7 0x7fc682bd3454 in start_thread () at /usr/lib/libpthread.so.0
#8 0x7fc684ba17df in clone () at /usr/lib/libc.so.6
Thread 12 (Thread 0x7fc628c47700 (LWP 6288)):
#0 0x7fc682bd910f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1 0x7fc6438ca6dd in () at /usr/lib/mlt/libmltsdl.so
#2 0x7fc682bd3454 in start_thread () at /usr/lib/libpthread.so.0
#3 0x7fc684ba17df in clone () at /usr/lib/libc.so.6
Thread 11 (Thread 0x7fc629848700 (LWP 6287)):
#0 0x7fc6748c45ba in pa_fdsem_before_poll () at
/usr/lib/pulseaudio/libpulsecommon-10.0.so
#1 0x7fc6748dc217 in () at /usr/lib/pulseaudio/libpulsecommon-10.0.so
#2 0x7fc67c74e99c in pa_mainloop_dispatch () at /usr/lib/libpulse.so.0
#3 0x7fc67c74ed9c in pa_mainloop_iterate () at /usr/lib/libpulse.so.0
#4 0x7fc642f83eed in () at /usr/lib/libSDL-1.2.so.0
#5 0x7fc642f57800 in () at /usr/lib/libSDL-1.2.so.0
#6 0x7fc642f5ffe8 in () at /usr/lib/libSDL-1.2.so.0
#7 0x7fc642fa18a9 in () at /usr/lib/libSDL-1.2.so.0
#8 0x7fc682bd3454 in start_thread () at /usr/lib/libpthread.so.0
#9 0x7fc684ba17df in clone () at /usr/lib/libc.so.6
Thread 10 (Thread 0x7fc62a049700 (LWP 6286)):
[KCrash Handler]
#6 0x7fc684aec04f in raise () at /usr/lib/libc.so.6
#7 0x7fc684aed47a in abort () at /usr/lib/libc.so.6
#8 0x7fc6851ec4ed in __gnu_cxx::__verbose_terminate_handler() () at
/build/gcc-multilib/src/gcc/libstdc++-v3/libsupc++/vterminate.cc:95
#9 0x7fc6851ea2a6 in __cxxabiv1::__terminate(void (*)())
(handler=) at
/build/gcc-multilib/src/gcc/libstdc++-v3/libsupc++/eh_terminate.cc:47
#10 0x7fc6851ea2f1 in std::terminate() () at
/build/gcc-multilib/src/gcc/libstdc++-v3/libsupc++/eh_terminate.cc:57
#11 0x7fc6851ea508 in __cxxabiv1::__cxa_throw(void*, std::type_info*, void
(*)(void*)) (obj=0x7fc6182afb10, tinfo=0x7fc64c9bf420 , dest=0x7fc64bf926d0 ) at
/build/gcc-multilib/src/gcc/libstdc++-v3/libsupc++/eh_throw.cc:87
#12 0x7fc64bf93702 in cv::error(cv::Exception const&) () at
/usr/lib/libopencv_core.so.3.2
#13 0x7fc64bf93883 in cv::error(int, cv::String const&, char const*, char
const*, int) () at /usr/lib/libopencv_core.so.3.2
#14 0x7fc64bebf7a4 in cv::Mat::Mat(cv::Mat const&, cv::Rect_ const&)
() at /usr/lib/libopencv_core.so.3.2
#15 0x7fc64e74c0f7 in () at /usr/lib/mlt/libmltopencv.so
#16 0x7fc68bd66197 in mlt_frame_get_image () at /usr/lib/libmlt.so.6
#17 0x7fc68bd66197 in mlt_frame_get_image () at /usr/lib/libmlt.so.6
#18 0x7fc643206772 in () at /usr/lib/mlt/libmltqt.so
#19 0x7fc68bd66197 in mlt_frame_get_image () at /usr/lib/libmlt.so.6
#20 0x7fc68bd7c1d9 in () at /usr/lib/libmlt.so.6
#21 0x7fc68bd66197 in mlt_frame_get_image () at /usr/lib/libmlt.so.6
#22 0x7fc68bd7986f in () at /usr/lib/libmlt.so.6
#23 0x0075774d in ()
#24 0x7fc6855906d8 in () at /usr/lib/libQt5Core.so.5
#25 0x7fc682bd3454 in start_thread () at /usr/lib/libpthread.so.0
#26 0x7fc684ba17df in clone () at /usr/lib/libc.so.6
Thread 9 (Thread 0x7fc62a84a700 (LWP 6285)):
#0 0x7fc682bd9
[frameworks-kio] [Bug 377165] Looks like KIO wasn't tested when samba is installed but not started and fills logs with error messages
https://bugs.kde.org/show_bug.cgi?id=377165 --- Comment #3 from Serhiy Zahoriya --- The log in question is `/tmp/fileEfcqvD`, where `EfcqvD` are some random characters, BTW. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 377144] Make folder dialog maximizes to dolphin window
https://bugs.kde.org/show_bug.cgi?id=377144 --- Comment #5 from David Faure --- Comment on attachment 104365 --> https://bugs.kde.org/attachment.cgi?id=104365 Reproducing with enUS locale and closing Do you maybe have a KWin rule for Dolphin, which would unexpected apply to all its windows? Right click on Dolphin titlebar, More Actions, Special Application Settings... Have you ever seen this dialog before? Does it contain anything enabled? Check also "Special Window Settings" on both the dolphin mainwindow and the "create new folder" dialog. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 377208] New: "Invert scroll direction" controls "Tap-and-drag lock" setting in Touchpad settings (on Wayland)
https://bugs.kde.org/show_bug.cgi?id=377208 Bug ID: 377208 Summary: "Invert scroll direction" controls "Tap-and-drag lock" setting in Touchpad settings (on Wayland) Product: systemsettings Version: 5.9.3 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: sascha.zengl...@yahoo.de Target Milestone: --- Created attachment 104367 --> https://bugs.kde.org/attachment.cgi?id=104367&action=edit Screenshots that describe the bug Title says it all. When trying to toggle natural scrolling the "Apply" button behaves strangely and the tap and drag lock setting is changed when you can click apply. I attached a few screenshots to show the behavior and visualize how to reproduce. First is the original state. Then I toggle the scroll direction and apply. Result is that scroll direction gets unchecked and drag lock gets checked. Next, when trying to toggle it again the "Apply" button stays grey. After unchecking it the same behavior as described above shows with turning off the setting. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 377209] New: QQuickWindow header include issue
https://bugs.kde.org/show_bug.cgi?id=377209 Bug ID: 377209 Summary: QQuickWindow header include issue Product: Breeze Version: 5.9.3 Platform: Compiled Sources OS: OS X Status: UNCONFIRMED Severity: normal Priority: NOR Component: QStyle Assignee: hugo.pereira.da.co...@gmail.com Reporter: rjvber...@gmail.com Target Milestone: --- Breeze version 5.9.3 has what seems flawed logic about including the QQuickWindow headerfile: it is included only when building for KDE4, but the corresponding type is used only when *not* building for KDE4. In addition the headerfile is only included when X11 is available. As a result, Breeze 5.9.3 fails to build for KF5 on Mac, yet this is supposed to be possible (and even somewhat supported) judging from the CMake files. I think the headerfile should simply be included unconditionally. Or, alternatively the build system could exclude all files that contain only windowmanager code on Mac and MS Windows (if that doesn't affect MDI windows). -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 377036] Kdevelop crashed when documentating template function
https://bugs.kde.org/show_bug.cgi?id=377036 --- Comment #1 from Robin Christ --- New minimal example: template typename T1> void foo(T1 bla); -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 377144] Make folder dialog maximizes to dolphin window
https://bugs.kde.org/show_bug.cgi?id=377144 --- Comment #6 from Alex --- Oh I forgot to add this, yes, I've set it recently. I've got size and position enabled for dolphin globally. -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 375240] The warnings don't show up in Qt Creator
https://bugs.kde.org/show_bug.cgi?id=375240 --- Comment #4 from Sergio Martins --- Can you printscreen QtCreator's dialog for your Kit settings and Compiler settings ? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 377204] DOSBox 0.47 causes crash of kwin_x11
https://bugs.kde.org/show_bug.cgi?id=377204 Martin Gräßlin changed: What|Removed |Added Resolution|--- |BACKTRACE Status|UNCONFIRMED |NEEDSINFO --- Comment #1 from Martin Gräßlin --- Unfortunately the backtrace is lacking debug symbols. If you are able to reproduce please install the debug packages provided by your distribution (please ask the distribution support channel on how to install them) and attach a new backtrace. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 374665] Logging out is nearly never possible
https://bugs.kde.org/show_bug.cgi?id=374665 --- Comment #10 from Martin Gräßlin --- Thanks for the backtrace. Should be easy to fix with that one. As explanation: a wayland version update started to trigger these crashes in several places. We just haven't found all yet. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 376365] KFileWidget does not support : in filenames
https://bugs.kde.org/show_bug.cgi?id=376365 --- Comment #7 from Fabian Vogt --- (In reply to David Faure from comment #6) > Oh, indeed, I hadn't seen that. I completely agree, the same API with a > QString can't be for relative paths and for URLs, "a:b" is both. > > How about we add a KFileWidget::setSelectedUrl(const QUrl& url)? > Then we can get rid of this ugly .toString() (QUrl -> QString -> QUrl). Sounds good to me! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 377210] New: Drag files from Dolphin to another programs causes plasma crash under Wayland
https://bugs.kde.org/show_bug.cgi?id=377210 Bug ID: 377210 Summary: Drag files from Dolphin to another programs causes plasma crash under Wayland Product: plasmashell Version: 5.9.3 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: yy...@gmx.com CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.9.3) Qt Version: 5.8.0 Frameworks Version: 5.31.0 Operating System: Linux 4.9.11-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: Plasma crashes under Wayland when I drag files from Dolphin to the follow programs... quod libet player totem player The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Illegal instruction Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fac04167800 (LWP 2215))] Thread 14 (Thread 0x7fab16492700 (LWP 3486)): #0 0x7fabfcde910f in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fabfdf1958b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7fab4bde61d0 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7fab4bdea9d8 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7fab4bde5263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7fab4bdeaa32 in () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7fab4bde5263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #7 0x7fab4bde8249 in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #8 0x7fabfdf186d8 in () at /usr/lib/libQt5Core.so.5 #9 0x7fabfcde3454 in start_thread () at /usr/lib/libpthread.so.0 #10 0x7fabfd82d7df in clone () at /usr/lib/libc.so.6 Thread 13 (Thread 0x7fab16c93700 (LWP 3485)): #0 0x7fabfcde910f in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fabfdf1958b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7fab4bde61d0 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7fab4bdea9d8 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7fab4bde5263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7fab4bdeaa32 in () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7fab4bde5263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #7 0x7fab4bde8249 in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #8 0x7fabfdf186d8 in () at /usr/lib/libQt5Core.so.5 #9 0x7fabfcde3454 in start_thread () at /usr/lib/libpthread.so.0 #10 0x7fabfd82d7df in clone () at /usr/lib/libc.so.6 Thread 12 (Thread 0x7fab38c29700 (LWP 3484)): #0 0x7fabfcde910f in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fabfdf1958b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7fab4bde61d0 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7fab4bdea9d8 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7fab4bde5263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7fab4bdeaa32 in () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7fab4bde5263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #7 0x7fab4bde8249 in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #8 0x7fabfdf186d8 in () at /usr/lib/libQt5Core.so.5 #9 0x7fabfcde3454 in start_thread () at /usr/lib/libpthread.so.0 #10 0x7fabfd82d7df in clone () at /usr/lib/libc.so.6 Thread 11 (Thread 0x7fab3948e700 (LWP 3483)): #0 0x7fabfcde910f in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fabfdf1958b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7fab4bde61d0 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7fab4bdea9d8 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7fab4bde5263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/
[neon] [Bug 368792] unmet dependencies for packages (libqt5core5a, libqt5scintilla2-12v5)
https://bugs.kde.org/show_bug.cgi?id=368792 bo...@web.de changed: What|Removed |Added CC||bo...@web.de -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 377208] "Invert scroll direction" controls "Tap-and-drag lock" setting in Touchpad settings (on Wayland)
https://bugs.kde.org/show_bug.cgi?id=377208
--- Comment #1 from Sascha Zenglein ---
I checked the touchpad kcm and found this in main.qml:
>Controls.CheckBox {
>id: naturalScroll
>text: i18n("Invert scroll direction")
>
>function load() {
>enabled = touchpad.supportsNaturalScroll && !scrollmethod.isNoScroll
>checked = enabled && touchpad.naturalScroll
>}
>
>onCheckedChanged: {
>if (enabled && !root.loading) {
>touchpad.tapDragLock = checked
>root.changeSignal()
>}
>}
>
>ToolTip {
>text: i18n("Touchscreen like scrolling.")
>}
>}
especially this line
> touchpad.tapDragLock = checked
looks suspicious.
--
You are receiving this mail because:
You are watching all bug changes.
[frameworks-kguiaddons] [Bug 365894] KMail(2) documentation not available
https://bugs.kde.org/show_bug.cgi?id=365894 andreas.sturmlech...@gmail.com changed: What|Removed |Added CC||andreas.sturmlechner@gmail. ||com -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 354661] "Rendering finished in" incorrect if job runs during 12am
https://bugs.kde.org/show_bug.cgi?id=354661 Jean-Baptiste Mardelle changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Jean-Baptiste Mardelle --- *** This bug has been marked as a duplicate of bug 372370 *** -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 372370] Kdenlive 16.04.2 reports render time as greater than 24 hours when midnight passes during rendering
https://bugs.kde.org/show_bug.cgi?id=372370 --- Comment #5 from Jean-Baptiste Mardelle --- *** Bug 354661 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 372370] Kdenlive 16.04.2 reports render time as greater than 24 hours when midnight passes during rendering
https://bugs.kde.org/show_bug.cgi?id=372370 Jean-Baptiste Mardelle changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Latest Commit||https://commits.kde.org/kde ||nlive/28816933a37a4799d8cad ||e1b04c80bdde417911a --- Comment #6 from Jean-Baptiste Mardelle --- Git commit 28816933a37a4799d8cade1b04c80bdde417911a by Jean-Baptiste Mardelle. Committed on 04/03/2017 at 17:24. Pushed by mardelle into branch 'Applications/16.12'. Fix render job duration when past midnight M +5-5src/dialogs/renderwidget.cpp M +1-1src/dialogs/renderwidget.h https://commits.kde.org/kdenlive/28816933a37a4799d8cade1b04c80bdde417911a -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 377211] New: [mac os x] unable to copy (clone) frame
https://bugs.kde.org/show_bug.cgi?id=377211 Bug ID: 377211 Summary: [mac os x] unable to copy (clone) frame Product: krita Version: 3.1.2 Platform: Other OS: OS X Status: UNCONFIRMED Severity: normal Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: gordie.lachance+...@gmail.com Target Milestone: --- Hi guys, I work with both mac & pc. Copying a frame works under windows (CTRL + drag frame); but I can't get it to work under mac os x. I did try with CTRL + drag, CMD + drag, ALT+drag, FN+drag... None works. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 376990] Okular randomly crashes when launched from Emacs
https://bugs.kde.org/show_bug.cgi?id=376990 --- Comment #3 from Tristan Miller --- Created attachment 104368 --> https://bugs.kde.org/attachment.cgi?id=104368&action=edit Another valgrind log, this time with more debugging symbols Attached is another log of running the following via emacs: /usr/bin/valgrind /usr/bin/okular --page 1 miller2017semeval.pdf >&/tmp/okular.log This time I had more debugging packages installed. I see the log contains a lot of null characters, following by what looks like some SQL statement. This looks very strange to me. Maybe valgrind itself crashed? -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 377212] New: Request: Allow encoding to Opus
https://bugs.kde.org/show_bug.cgi?id=377212 Bug ID: 377212 Summary: Request: Allow encoding to Opus Product: k3b Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: Plugins Assignee: k...@kde.org Reporter: ci3...@gmail.com CC: mich...@jabster.pl, tr...@kde.org Target Milestone: --- Since K3b offers a nice way to rip an audio CD, it would be cool, if it would allow to encode to Opus (https://opus-codec.org/) as well. Opus has serveral advantages. It is a free codec, has good support for different configurations, and offers one of the best compression rates for different kinds of audio sources. Encoding could be realized with libopus or FFmpeg (libavcodec, either wrapper to libopus as well or native). -- You are receiving this mail because: You are watching all bug changes.
[Skanlite] [Bug 299517] Skanlite should support scan to pdf.
https://bugs.kde.org/show_bug.cgi?id=299517 Michael changed: What|Removed |Added CC||prescience...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 377202] Empty DJVU page displayed in black
https://bugs.kde.org/show_bug.cgi?id=377202 truf changed: What|Removed |Added Version|0.25.0 |1.0.0 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 377202] Empty DJVU page displayed in black
https://bugs.kde.org/show_bug.cgi?id=377202 --- Comment #2 from truf --- Have also reproduced with djvulibre 3.5.27.1-7 okular 1.0.1 package 4:16.12.1-0ubuntu2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 377213] New: Keyboard shortcut for minimize all windows addon does not work under Wayland
https://bugs.kde.org/show_bug.cgi?id=377213 Bug ID: 377213 Summary: Keyboard shortcut for minimize all windows addon does not work under Wayland Product: plasmashell Version: 5.9.3 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: generic-wayland Assignee: plasma-b...@kde.org Reporter: yy...@gmx.com Target Milestone: 1.0 Add `minimize all windows` addon to your panel or your desktop, set a keyboard shorcut (I use meta+d). Nothing happens when I press the shortcut, it works under X11 session. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 374977] org.kde.plasma.minimizeall applet does not work under wayland
https://bugs.kde.org/show_bug.cgi?id=374977 Dr. Chapatin changed: What|Removed |Added CC||yy...@gmx.com --- Comment #1 from Dr. Chapatin --- Same here on Arch. Keyboard shortcut and click do no effect. -- You are receiving this mail because: You are watching all bug changes.
