[Akonadi] [Bug 415991] New: mail archive job crash
https://bugs.kde.org/show_bug.cgi?id=415991 Bug ID: 415991 Summary: mail archive job crash Product: Akonadi Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: Archive Mail Agent Assignee: kdepim-b...@kde.org Reporter: philippe.roub...@free.fr Target Milestone: --- Application: akonadi_archivemail_agent (5.13.0 (19.12.0)) Qt Version: 5.14.0 Frameworks Version: 5.65.0 Operating System: Linux 4.12.14-lp151.28.36-default x86_64 Distribution: "openSUSE Leap 15.1" -- Information about the crash: - What I was doing when the application crashed: i have just defined a mail archive job. i get a notification : unexpected termination of akonadi_archivmail_agent -- Backtrace: Application: akonadi_archivemail_agent (akonadi_archivemail_agent), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fe3904e3540 (LWP 2551))] Thread 6 (Thread 0x7fe351197700 (LWP 2656)): #0 0x7fe38cb8319b in poll () from /lib64/libc.so.6 #1 0x7fe3833bd1a9 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7fe3833bd2bc in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7fe38d6fda3b in QEventDispatcherGlib::processEvents (this=0x7fe33c000b10, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7fe38d69d03a in QEventLoop::exec (this=this@entry=0x7fe351196bb0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #5 0x7fe38d4ae467 in QThread::exec (this=) at thread/qthread.cpp:536 #6 0x7fe38d4af93c in QThreadPrivate::start (arg=0x56396bb79880) at thread/qthread_unix.cpp:342 #7 0x7fe385263569 in start_thread () from /lib64/libpthread.so.0 #8 0x7fe38cb8d9ef in clone () from /lib64/libc.so.6 Thread 5 (Thread 0x7fe351998700 (LWP 2578)): #0 QMutex::lock (this=this@entry=0x56396bb6adc0) at thread/qmutex.cpp:231 #1 0x7fe38d6fd93c in QMutexLocker::QMutexLocker (m=0x56396bb6adc0, this=) at ../../include/QtCore/../../src/corelib/thread/qmutex.h:233 #2 QThreadData::canWaitLocked (this=0x56396bb6ad90) at ../../include/QtCore/5.14.0/QtCore/private/../../../../../src/corelib/thread/qthread_p.h:272 #3 postEventSourcePrepare (s=0x7fe348004780, timeout=0x7fe3519979e4) at kernel/qeventdispatcher_glib.cpp:260 #4 0x7fe3833bc709 in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0 #5 0x7fe3833bd0db in ?? () from /usr/lib64/libglib-2.0.so.0 #6 0x7fe3833bd2bc in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #7 0x7fe38d6fda3b in QEventDispatcherGlib::processEvents (this=0x7fe348000b10, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #8 0x7fe38d69d03a in QEventLoop::exec (this=this@entry=0x7fe351997bb0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #9 0x7fe38d4ae467 in QThread::exec (this=) at thread/qthread.cpp:536 #10 0x7fe38d4af93c in QThreadPrivate::start (arg=0x56396bb5cda0) at thread/qthread_unix.cpp:342 #11 0x7fe385263569 in start_thread () from /lib64/libpthread.so.0 #12 0x7fe38cb8d9ef in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7fe352199700 (LWP 2574)): #0 0x7fe38cb8319b in poll () from /lib64/libc.so.6 #1 0x7fe3833bd1a9 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7fe3833bd2bc in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7fe38d6fda3b in QEventDispatcherGlib::processEvents (this=0x7fe344000b10, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7fe38d69d03a in QEventLoop::exec (this=this@entry=0x7fe352198b80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #5 0x7fe38d4ae467 in QThread::exec (this=this@entry=0x7fe38ddefda0 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread.cpp:536 #6 0x7fe38db78115 in QDBusConnectionManager::run (this=0x7fe38ddefda0 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:179 #7 0x7fe38d4af93c in QThreadPrivate::start (arg=0x7fe38ddefda0 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:342 #8 0x7fe385263569 in start_thread () from /lib64/libpthread.so.0 #9 0x7fe38cb8d9ef in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7fe354412700 (LWP 2571)): #0 0x7fe3852698ad in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fe3550b89ab in ?? () from /usr/lib64/dri/i965_dri.so #2 0x7fe3550b86b7 in ?? () from /usr/lib64/dri/i965_dri.so #3 0x7fe385263569 in start_thread () from /lib64/libpthread.so.0 #4 0x7fe38cb8d9ef in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7fe35c8ce700 (LWP 2564)): #0 0x7fe38cb8319b in poll () from /lib64/libc.so.6 #1 0x7fe3810e0307 in ?? () from /usr/lib64/libxcb.so.1 #2 0x7fe3810e1f3a in xcb_w
[kdevelop] [Bug 415913] KDevelop code formatter generates incorrect formatting with kdev_format_source
https://bugs.kde.org/show_bug.cgi?id=415913 Kevin Funk changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #2 from Kevin Funk --- I can close it. Thanks for the feedback! -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 415962] kontact crash when restarting after a problem to view mail contents
https://bugs.kde.org/show_bug.cgi?id=415962 Philippe ROUBACH changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #7 from Philippe ROUBACH --- i recreate all about kmail things. something was wrong in a personnal folder. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 414028] digikam spamming journal with details of almost everything it does...
https://bugs.kde.org/show_bug.cgi?id=414028 caulier.gil...@gmail.com changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/kde/ ||digikam/commit/e613bc900c58 ||144256e6d24e463217dabe76e49 ||5 --- Comment #15 from caulier.gil...@gmail.com --- Git commit e613bc900c58144256e6d24e463217dabe76e495 by Gilles Caulier. Committed on 08/01/2020 at 08:22. Pushed by cgilles into branch 'master'. This is a mess: some qWarning(), qInfo(), qCritical() messages are not wrapped in litteral debug spaces as expected and are printed as "unknown". To disable these messages, the right keyword is "default" (it's logic of course!) Now AppImage do not export the huge warning strings from Qt core in log files. ouf... Related: bug 415882, bug 414016 M +1-1project/bundles/appimage/data/AppRun https://invent.kde.org/kde/digikam/commit/e613bc900c58144256e6d24e463217dabe76e495 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 414016] Log file /var/log/syslog grows in size very fast
https://bugs.kde.org/show_bug.cgi?id=414016 caulier.gil...@gmail.com changed: What|Removed |Added Latest Commit||https://invent.kde.org/kde/ ||digikam/commit/e613bc900c58 ||144256e6d24e463217dabe76e49 ||5 Resolution|DUPLICATE |FIXED --- Comment #18 from caulier.gil...@gmail.com --- Git commit e613bc900c58144256e6d24e463217dabe76e495 by Gilles Caulier. Committed on 08/01/2020 at 08:22. Pushed by cgilles into branch 'master'. This is a mess: some qWarning(), qInfo(), qCritical() messages are not wrapped in litteral debug spaces as expected and are printed as "unknown". To disable these messages, the right keyword is "default" (it's logic of course!) Now AppImage do not export the huge warning strings from Qt core in log files. ouf... Related: bug 415882, bug 414028 M +1-1project/bundles/appimage/data/AppRun https://invent.kde.org/kde/digikam/commit/e613bc900c58144256e6d24e463217dabe76e495 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 415882] DigiKam 6.4 crashes on processing a large number of new HEIC/HEIF files
https://bugs.kde.org/show_bug.cgi?id=415882 caulier.gil...@gmail.com changed: What|Removed |Added Latest Commit||https://invent.kde.org/kde/ ||digikam/commit/e613bc900c58 ||144256e6d24e463217dabe76e49 ||5 Resolution|DUPLICATE |FIXED --- Comment #7 from caulier.gil...@gmail.com --- Git commit e613bc900c58144256e6d24e463217dabe76e495 by Gilles Caulier. Committed on 08/01/2020 at 08:22. Pushed by cgilles into branch 'master'. This is a mess: some qWarning(), qInfo(), qCritical() messages are not wrapped in litteral debug spaces as expected and are printed as "unknown". To disable these messages, the right keyword is "default" (it's logic of course!) Now AppImage do not export the huge warning strings from Qt core in log files. ouf... Related: bug 414028, bug 414016 M +1-1project/bundles/appimage/data/AppRun https://invent.kde.org/kde/digikam/commit/e613bc900c58144256e6d24e463217dabe76e495 -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 415992] New: Duplicate Composition Association when rename it's variable in the tree View
https://bugs.kde.org/show_bug.cgi?id=415992 Bug ID: 415992 Summary: Duplicate Composition Association when rename it's variable in the tree View Product: umbrello Version: 2.30.0 (KDE Applications 19.12.0) Platform: Other OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: umbrello-de...@kde.org Reporter: sahra...@gmail.com Target Milestone: --- SUMMARY when I try to rename a variable in the Tree View that auto generated by the Composition tool, it create another Association link. STEPS TO REPRODUCE 1. Create two class C1 and C2 and drag them into the class diagram 2. Choose Composition tool from toolbar 3. Drag it from C1 to C2, a new variable will be appear with the default name 4. go to the Tree view and find that variable and rename it. OBSERVED RESULT another association will be create [therefore there is two association] and rename both of them. can be checked in the class Properties/Associations EXPECTED RESULT just rename the existing association variable. SOFTWARE/OS VERSIONS Windows: Win 10 64bit / 1903 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION I Suggest the default variable name that is generated in the composition association be the target class name that starts with "_". Excuse me for my bad English thanks a lot. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 415958] Changing language in Kstars
https://bugs.kde.org/show_bug.cgi?id=415958 --- Comment #2 from bansugor...@gmail.com --- I downloaded it from here. https://edu.kde.org/kstars/ Only US English can be selected in Switch Application Language ... -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 415993] New: Plasma crashed after trying to change the login screen
https://bugs.kde.org/show_bug.cgi?id=415993 Bug ID: 415993 Summary: Plasma crashed after trying to change the login screen Product: systemsettings Version: 5.17.4 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: m4a...@163.com Target Milestone: --- Application: systemsettings5 (5.17.4) Qt Version: 5.14.0 Frameworks Version: 5.65.0 Operating System: Linux 5.4.6-2-MANJARO x86_64 Distribution: Manjaro Linux -- Information about the crash: - What I was doing when the application crashed: I double click my mouse on the "Maldives" and "maya" and then it crashed The crash can be reproduced every time. -- Backtrace: Application: System Settings (systemsettings5), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f4807245840 (LWP 8853))] Thread 8 (Thread 0x7f47ee5ed700 (LWP 8862)): #0 0x7f480992362f in g_source_ref () at /usr/lib/libglib-2.0.so.0 #1 0x7f480992a662 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f480992b93b in g_main_context_prepare () at /usr/lib/libglib-2.0.so.0 #3 0x7f480992c046 in () at /usr/lib/libglib-2.0.so.0 #4 0x7f480992c1f1 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #5 0x7f480bf12cdc in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7f480beb939c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #7 0x7f480bcdee62 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #8 0x7f480afa4249 in () at /usr/lib/libQt5Qml.so.5 #9 0x7f480bcdffd6 in () at /usr/lib/libQt5Core.so.5 #10 0x7f480a5454cf in start_thread () at /usr/lib/libpthread.so.0 #11 0x7f480b9642d3 in clone () at /usr/lib/libc.so.6 Thread 7 (Thread 0x7f47eedee700 (LWP 8861)): #0 0x7f480b95542c in read () at /usr/lib/libc.so.6 #1 0x7f48098dc9f0 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f480992a9e1 in g_main_context_check () at /usr/lib/libglib-2.0.so.0 #3 0x7f480992c0c8 in () at /usr/lib/libglib-2.0.so.0 #4 0x7f480992d0c3 in g_main_loop_run () at /usr/lib/libglib-2.0.so.0 #5 0x7f4804868bc8 in () at /usr/lib/libgio-2.0.so.0 #6 0x7f4809908bb1 in () at /usr/lib/libglib-2.0.so.0 #7 0x7f480a5454cf in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f480b9642d3 in clone () at /usr/lib/libc.so.6 Thread 6 (Thread 0x7f47ef5ef700 (LWP 8860)): #0 0x7f480b95542c in read () at /usr/lib/libc.so.6 #1 0x7f48098dc9f0 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f480992a9e1 in g_main_context_check () at /usr/lib/libglib-2.0.so.0 #3 0x7f480992c0c8 in () at /usr/lib/libglib-2.0.so.0 #4 0x7f480992c1f1 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #5 0x7f480992c242 in () at /usr/lib/libglib-2.0.so.0 #6 0x7f4809908bb1 in () at /usr/lib/libglib-2.0.so.0 #7 0x7f480a5454cf in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f480b9642d3 in clone () at /usr/lib/libc.so.6 Thread 5 (Thread 0x7f47f6d1f700 (LWP 8857)): #0 0x7f480b9599ef in poll () at /usr/lib/libc.so.6 #1 0x7f480992c120 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f480992c1f1 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f480bf12cdc in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f480beb939c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f480bcdee62 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f480afa4249 in () at /usr/lib/libQt5Qml.so.5 #7 0x7f480bcdffd6 in () at /usr/lib/libQt5Core.so.5 #8 0x7f480a5454cf in start_thread () at /usr/lib/libpthread.so.0 #9 0x7f480b9642d3 in clone () at /usr/lib/libc.so.6 Thread 4 (Thread 0x7f47f7fff700 (LWP 8856)): #0 0x7f48098dc4e4 in g_mutex_unlock () at /usr/lib/libglib-2.0.so.0 #1 0x7f480992bf08 in g_main_context_acquire () at /usr/lib/libglib-2.0.so.0 #2 0x7f480992bfc7 in () at /usr/lib/libglib-2.0.so.0 #3 0x7f480992c1f1 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #4 0x7f480bf12cdc in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f480beb939c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7f480bcdee62 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #7 0x7f480afa4249 in () at /usr/lib/libQt5Qml.so.5 #8 0x7f480bcdffd6 in () at /usr/lib/libQt5Core.so.5 #9 0x7f480a5454cf in start_thread () at /usr/lib/libpthread.so.0 #10 0x7f480b9642d3 in clone () at /usr/lib/libc.so.6 Thread 3 (Thread 0x7f47ffa93700 (LWP 8855)): #0 0x7f48098dc479 in g_mutex_lock () at /usr/lib/libglib-2.0.so.0 #1 0x7f480992c1db in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #2 0x00
[krita] [Bug 415896] Stroke selection doesn't work for some selection tools
https://bugs.kde.org/show_bug.cgi?id=415896 --- Comment #8 from Boudewijn Rempt --- Yes -- vector shapes cannot be drawn with the raster brushes. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 333843] Brush freezes after lifting stylus pen away from tablet while cursor is on canvas
https://bugs.kde.org/show_bug.cgi?id=333843 --- Comment #31 from Boudewijn Rempt --- Aaaa: "a 32 bits operating system" -- which one? If it's not Linux, you do not have "the same issue". Which version of Krita are you using? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 415977] Feature request: Having to select both the frame and the layer to edit a frame
https://bugs.kde.org/show_bug.cgi?id=415977 Boudewijn Rempt changed: What|Removed |Added Severity|minor |wishlist CC||b...@valdyas.org -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 415891] Project file loads perfectly fine in seconds in 4.1.7, never finishes loading in 4.2.8
https://bugs.kde.org/show_bug.cgi?id=415891 --- Comment #21 from Boudewijn Rempt --- The debug output should be the same, and the backtrace is fairly clear. It's just that I cannot reproduce it :-( -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 398680] Wayland session is unusable (black screen) when monitor is reconnected to hdmi port after energy saving timeout
https://bugs.kde.org/show_bug.cgi?id=398680 Roman Gilg changed: What|Removed |Added Status|REPORTED|RESOLVED Latest Commit||https://commits.kde.org/kwi ||n/2632e4182c658178af82be175 ||575b094002468af Resolution|--- |FIXED --- Comment #4 from Roman Gilg --- Git commit 2632e4182c658178af82be175575b094002468af by Roman Gilg. Committed on 08/01/2020 at 09:12. Pushed by romangilg into branch 'master'. [platforms/drm] Allow running without outputs Summary: Set outputs enablement also when none outputs are present. This patch is similar to earlier attempt at D17985. Related: bug 402827, bug 389551, bug 413758 Test Plan: Starting without outputs, manual disconnects and DPMS changes. There is still an issue when an output gets disconnected while the DPMS is off. But it's an improvement already. Reviewers: #kwin, davidedmundson Reviewed By: #kwin, davidedmundson Subscribers: kwin Tags: #kwin Maniphest Tasks: T10016 Differential Revision: https://phabricator.kde.org/D26511 M +2-6plugins/platforms/drm/drm_backend.cpp https://commits.kde.org/kwin/2632e4182c658178af82be175575b094002468af -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 389551] kwin_wayland crash when monitor is switched off (or input is changed)
https://bugs.kde.org/show_bug.cgi?id=389551 Roman Gilg changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED Latest Commit||https://commits.kde.org/kwi ||n/2632e4182c658178af82be175 ||575b094002468af --- Comment #13 from Roman Gilg --- Git commit 2632e4182c658178af82be175575b094002468af by Roman Gilg. Committed on 08/01/2020 at 09:12. Pushed by romangilg into branch 'master'. [platforms/drm] Allow running without outputs Summary: Set outputs enablement also when none outputs are present. This patch is similar to earlier attempt at D17985. Related: bug 402827, bug 398680, bug 413758 Test Plan: Starting without outputs, manual disconnects and DPMS changes. There is still an issue when an output gets disconnected while the DPMS is off. But it's an improvement already. Reviewers: #kwin, davidedmundson Reviewed By: #kwin, davidedmundson Subscribers: kwin Tags: #kwin Maniphest Tasks: T10016 Differential Revision: https://phabricator.kde.org/D26511 M +2-6plugins/platforms/drm/drm_backend.cpp https://commits.kde.org/kwin/2632e4182c658178af82be175575b094002468af -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 413758] KWin_wayland crashes when an external display is unplugged
https://bugs.kde.org/show_bug.cgi?id=413758 Roman Gilg changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://commits.kde.org/kwi ||n/2632e4182c658178af82be175 ||575b094002468af Status|REPORTED|RESOLVED --- Comment #6 from Roman Gilg --- Git commit 2632e4182c658178af82be175575b094002468af by Roman Gilg. Committed on 08/01/2020 at 09:12. Pushed by romangilg into branch 'master'. [platforms/drm] Allow running without outputs Summary: Set outputs enablement also when none outputs are present. This patch is similar to earlier attempt at D17985. Related: bug 402827, bug 389551, bug 398680 Test Plan: Starting without outputs, manual disconnects and DPMS changes. There is still an issue when an output gets disconnected while the DPMS is off. But it's an improvement already. Reviewers: #kwin, davidedmundson Reviewed By: #kwin, davidedmundson Subscribers: kwin Tags: #kwin Maniphest Tasks: T10016 Differential Revision: https://phabricator.kde.org/D26511 M +2-6plugins/platforms/drm/drm_backend.cpp https://commits.kde.org/kwin/2632e4182c658178af82be175575b094002468af -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 402827] kwin_wayland segfault on monitor wakeup
https://bugs.kde.org/show_bug.cgi?id=402827 Roman Gilg changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED Latest Commit||https://commits.kde.org/kwi ||n/2632e4182c658178af82be175 ||575b094002468af --- Comment #23 from Roman Gilg --- Git commit 2632e4182c658178af82be175575b094002468af by Roman Gilg. Committed on 08/01/2020 at 09:12. Pushed by romangilg into branch 'master'. [platforms/drm] Allow running without outputs Summary: Set outputs enablement also when none outputs are present. This patch is similar to earlier attempt at D17985. Related: bug 389551, bug 398680, bug 413758 Test Plan: Starting without outputs, manual disconnects and DPMS changes. There is still an issue when an output gets disconnected while the DPMS is off. But it's an improvement already. Reviewers: #kwin, davidedmundson Reviewed By: #kwin, davidedmundson Subscribers: kwin Tags: #kwin Maniphest Tasks: T10016 Differential Revision: https://phabricator.kde.org/D26511 M +2-6plugins/platforms/drm/drm_backend.cpp https://commits.kde.org/kwin/2632e4182c658178af82be175575b094002468af -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 415989] Dosnt Open/Delete class Diagram element
https://bugs.kde.org/show_bug.cgi?id=415989 Ralf Habacker changed: What|Removed |Added CC||ralf.habac...@freenet.de --- Comment #1 from Ralf Habacker --- Comment on attachment 124964 --> https://bugs.kde.org/attachment.cgi?id=124964 _ClassDiagram_UI is a class diagram in the SahraCore/UI folder. it doesn't open or delete. The appended xmi file is somehow corrupted. It contains one class diagram named 'class diagram': which is referenced later in the section for the tree view ... a few line below there is also the class diagram you are missing: but there is no related tag in the file. I suggest to open the xmi file in an editor, remove the mentioned line, save the file, load it with umbrello and recreate the diagram _ClassDiagram_UI. If you can give some information how to reproduce this issue, it would be possible to fix this isssue inside the umbrello source code. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 404990] Sign in with Google temporarily disabled for this app
https://bugs.kde.org/show_bug.cgi?id=404990 luancarvalho changed: What|Removed |Added CC||luancarvalhomartins@gmail.c ||om -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 414818] Krita crashes when loading files containing colorize mask
https://bugs.kde.org/show_bug.cgi?id=414818 Boudewijn Rempt changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/kde/ ||krita/commit/478a8be4ef0c9d ||5ad073e37696e71737f7eb4282 Status|ASSIGNED|RESOLVED --- Comment #7 from Boudewijn Rempt --- Git commit 478a8be4ef0c9d5ad073e37696e71737f7eb4282 by Boudewijn Rempt. Committed on 08/01/2020 at 09:52. Pushed by rempt into branch 'master'. Fix endless recursion in KisAssignProfileProcessingVisitor::visitColorizeMask M +0-1libs/image/processing/kis_assign_profile_processing_visitor.cpp https://invent.kde.org/kde/krita/commit/478a8be4ef0c9d5ad073e37696e71737f7eb4282 -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 415990] the application assumes the class element is a folder type
https://bugs.kde.org/show_bug.cgi?id=415990 Ralf Habacker changed: What|Removed |Added Resolution|--- |FIXED Version Fixed In||2.30.80 (KDE Applications ||19.03.80) Status|REPORTED|RESOLVED Latest Commit||https://invent.kde.org/kde/ ||umbrello/commit/759b1cc5baa ||11007fd8ad2ea632dd49bf8b16d ||27 --- Comment #1 from Ralf Habacker --- Git commit 759b1cc5baa11007fd8ad2ea632dd49bf8b16d27 by Ralf Habacker. Committed on 08/01/2020 at 09:50. Pushed by habacker into branch 'master'. Fix 'the application assumes the class element is a folder type' FIXED-IN:2.30.80 (KDE Applications 19.03.80) M +16 -4umbrello/umllistview.cpp https://invent.kde.org/kde/umbrello/commit/759b1cc5baa11007fd8ad2ea632dd49bf8b16d27 -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 415951] Support .NRW as .RAW for thumbnails
https://bugs.kde.org/show_bug.cgi?id=415951 Kai Uwe Broulik changed: What|Removed |Added Resolution|--- |DOWNSTREAM Status|REPORTED|RESOLVED --- Comment #6 from Kai Uwe Broulik --- Alright, thanks, closing this then as it's not an issue on our side. -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 415990] the application assumes the class element is a folder type
https://bugs.kde.org/show_bug.cgi?id=415990 Ralf Habacker changed: What|Removed |Added CC||ralf.habac...@freenet.de --- Comment #2 from Ralf Habacker --- Thanks for reporting. The issue will be fixed in the next minor release 2.31, which will be available in April 2020. -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 415974] KDE Plasma does not work
https://bugs.kde.org/show_bug.cgi?id=415974 Kai Uwe Broulik changed: What|Removed |Added Status|REPORTED|NEEDSINFO CC||k...@privat.broulik.de Resolution|--- |BACKTRACE --- Comment #1 from Kai Uwe Broulik --- Please install debug symbols for Solid and submit a new backtrace. -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 415992] Duplicate Composition Association when rename it's variable in the tree View
https://bugs.kde.org/show_bug.cgi?id=415992 Ralf Habacker changed: What|Removed |Added CC||ralf.habac...@freenet.de Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #1 from Ralf Habacker --- Thanks reportin -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 415625] Crash in transform tool
https://bugs.kde.org/show_bug.cgi?id=415625 Boudewijn Rempt changed: What|Removed |Added Latest Commit||https://invent.kde.org/kde/ ||krita/commit/69bc2897bf9fb6 ||b88ef4bb2754f877057c0a3ea7 Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #2 from Boudewijn Rempt --- Git commit 69bc2897bf9fb6b88ef4bb2754f877057c0a3ea7 by Boudewijn Rempt. Committed on 08/01/2020 at 10:05. Pushed by rempt into branch 'master'. Convert Q_ASSERT to KIS_SAFE_ASSERT This doesn't properly fix bug 415625, but the assert here in addJob shouldn't be fatal. M +3-3libs/image/kis_stroke.cpp https://invent.kde.org/kde/krita/commit/69bc2897bf9fb6b88ef4bb2754f877057c0a3ea7 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 415994] New: Crashed when I tried to delete "Start application menu" applet
https://bugs.kde.org/show_bug.cgi?id=415994 Bug ID: 415994 Summary: Crashed when I tried to delete "Start application menu" applet Product: plasmashell Version: 5.17.4 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: ogldel...@mail.ru CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.17.4) Qt Version: 5.12.5 Frameworks Version: 5.64.0 Operating System: Linux 5.4.7-200.fc31.x86_64 x86_64 Distribution: Fedora 31 (KDE Plasma) -- Information about the crash: - What I was doing when the application crashed: Add lots of applets (~30-40 pcs) to workspace and starts to delete them. When I tried to delete one. Plasma crashed and restarted succesfuly. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f93034bec80 (LWP 992))] Thread 37 (Thread 0x7f92867fc700 (LWP 2477)): #0 0x7f930673e07a in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f928f658e3a in base::ConditionVariable::TimedWait(base::TimeDelta const&) () from /lib64/libQt5WebEngineCore.so.5 #2 0x7f928f6597f7 in base::WaitableEvent::TimedWaitUntil(base::TimeTicks const&) () from /lib64/libQt5WebEngineCore.so.5 #3 0x7f928f6598f1 in base::WaitableEvent::TimedWait(base::TimeDelta const&) () from /lib64/libQt5WebEngineCore.so.5 #4 0x7f928f61a022 in base::internal::SchedulerWorker::Delegate::WaitForWork(base::WaitableEvent*) () from /lib64/libQt5WebEngineCore.so.5 #5 0x7f928f61ce48 in base::internal::SchedulerWorker::RunWorker() () from /lib64/libQt5WebEngineCore.so.5 #6 0x7f928f61d0f4 in base::internal::SchedulerWorker::RunPooledWorker() () from /lib64/libQt5WebEngineCore.so.5 #7 0x7f928f65bd6f in base::(anonymous namespace)::ThreadFunc(void*) () from /lib64/libQt5WebEngineCore.so.5 #8 0x7f93067374e2 in start_thread () from /lib64/libpthread.so.0 #9 0x7f9306ef2693 in clone () from /lib64/libc.so.6 Thread 36 (Thread 0x7f9269688700 (LWP 2102)): #0 0x7f930673dd45 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f9307279003 in QWaitConditionPrivate::wait (deadline=..., this=0x55c23cdb5600) at thread/qwaitcondition_unix.cpp:146 #2 QWaitCondition::wait (this=, mutex=0x7f92f003a940, deadline=...) at thread/qwaitcondition_unix.cpp:225 #3 0x7f9307279091 in QWaitCondition::wait (this=this@entry=0x7f92f003a948, mutex=mutex@entry=0x7f92f003a940, time=time@entry=18446744073709551615) at ../../include/QtCore/../../src/corelib/kernel/qdeadlinetimer.h:68 #4 0x7f9308eb51b9 in QSGRenderThreadEventQueue::takeEvent (wait=true, this=0x7f92f003a938) at scenegraph/qsgthreadedrenderloop.cpp:245 #5 QSGRenderThread::processEventsAndWaitForMore (this=this@entry=0x7f92f003a8c0) at scenegraph/qsgthreadedrenderloop.cpp:710 #6 0x7f9308eb545d in QSGRenderThread::run (this=0x7f92f003a8c0) at scenegraph/qsgthreadedrenderloop.cpp:739 #7 0x7f93072734f6 in QThreadPrivate::start (arg=0x7f92f003a8c0) at thread/qthread_unix.cpp:361 #8 0x7f93067374e2 in start_thread () from /lib64/libpthread.so.0 #9 0x7f9306ef2693 in clone () from /lib64/libc.so.6 Thread 35 (Thread 0x7f9269e89700 (LWP 2101)): #0 0x7f930673dd45 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f9307279003 in QWaitConditionPrivate::wait (deadline=..., this=0x55c244b34eb0) at thread/qwaitcondition_unix.cpp:146 #2 QWaitCondition::wait (this=, mutex=0x7f92f0020600, deadline=...) at thread/qwaitcondition_unix.cpp:225 #3 0x7f9307279091 in QWaitCondition::wait (this=this@entry=0x7f92f0020608, mutex=mutex@entry=0x7f92f0020600, time=time@entry=18446744073709551615) at ../../include/QtCore/../../src/corelib/kernel/qdeadlinetimer.h:68 #4 0x7f9308eb51b9 in QSGRenderThreadEventQueue::takeEvent (wait=true, this=0x7f92f00205f8) at scenegraph/qsgthreadedrenderloop.cpp:245 #5 QSGRenderThread::processEventsAndWaitForMore (this=this@entry=0x7f92f0020580) at scenegraph/qsgthreadedrenderloop.cpp:710 #6 0x7f9308eb545d in QSGRenderThread::run (this=0x7f92f0020580) at scenegraph/qsgthreadedrenderloop.cpp:739 #7 0x7f93072734f6 in QThreadPrivate::start (arg=0x7f92f0020580) at thread/qthread_unix.cpp:361 #8 0x7f93067374e2 in start_thread () from /lib64/libpthread.so.0 #9 0x7f9306ef2693 in clone () from /lib64/libc.so.6 Thread 34 (Thread 0x7f926a68a700 (LWP 2100)): #0 0x7f930673dd45 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f9307279003 in QWaitConditionPrivate::wait (deadline=..., this=0x55c244c32fc0) at thread/qwaitcondition_unix.cpp:146 #2 QWaitCondition::wait (this=, mutex=0x55c243042690,
[krita] [Bug 414818] Krita crashes when loading files containing colorize mask
https://bugs.kde.org/show_bug.cgi?id=414818 --- Comment #8 from Regis --- Cool! Thanks a lot :) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 402940] no thumbnails with windows client using network share
https://bugs.kde.org/show_bug.cgi?id=402940 kidor...@gmail.com changed: What|Removed |Added Version|6.0.0 |6.4.0 CC||kidor...@gmail.com --- Comment #2 from kidor...@gmail.com --- I think this is related... I switched from local to network share and after a rescan the People face thumbnails were zoomed out and some were rotated 90 deg. See also this disccussion: http://digikam.1695700.n4.nabble.com/digiKam-users-People-thumbnail-not-zoomed-to-face-td4709112.html thanks, Neil -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 415406] Krita crashes opening .kra file
https://bugs.kde.org/show_bug.cgi?id=415406 Ahab Greybeard changed: What|Removed |Added CC||ahab.greybe...@hotmail.co.u ||k --- Comment #4 from Ahab Greybeard --- For the crashing .kra file provided by Josie and for another crashing animation provided by alyrah, here: https://forum.kde.org/viewtopic.php?f=139&t=163686, I can 'repair' them by opening in 4.2.7.1, turning onion skins off and then saving, after which they open ok in 4.2.8. If I then turn on onion skins in 4.2.8 and save, the resulting .kra file will crash krita 4.2.8. Another way to 'repair' them is to delete the Annotations folder in the .kra file as mentioned in https://bugs.kde.org/show_bug.cgi?id=414818 by Mikhail (though I realise that this could never be recommended). Krita Plus and the latest 4.3.0 prealpha do not crash with the original crashing files on Linux and Windows. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 414564] Update of bank account data aborted
https://bugs.kde.org/show_bug.cgi?id=414564 --- Comment #14 from Stefan Hohrein --- (In reply to Thomas Baumgart from comment #12) > Do you see a 'Settings/Configure AqBanking...' menu entry in this version? > If not, then the required AqBanking version is not packaged with the version > you downloaded. Yes I can see and open this menue and I can enter a new user till: "Die Systemkennung und Kontenliste werden angefordert". Then I get the following sequence: 11:47:13 Server-Zertifikat abrufen 11:47:13 Verbindung vorbereiten 11:47:13 Mit Server verbinden... 11:47:13 Verwende GnuTLS Default Ciphers. 11:47:13 TLS: SSL-Ciphers ausgehandelt: TLS1.2:ECDHE-RSA-AES-256-GCM:AEAD 11:47:13 Verbunden. 11:47:13 Verbindung beendet. 11:47:13 Got certificate 11:47:13 Retrieving generic bank info (SCA) 11:47:13 HBCI-Aufträge werden ausgeführt 11:47:13 AqHBCI gestartet 11:47:13 Encoding queue 11:47:13 Sending message 11:47:13 Verwende GnuTLS Default Ciphers. 11:47:13 TLS: SSL-Ciphers ausgehandelt: TLS1.2:ECDHE-RSA-AES-256-GCM:AEAD 11:47:13 Message sent 11:47:13 Queue sent 11:47:13 Waiting for response 11:47:13 Error receiving response (404) 11:47:13 AqHBCI abgeschlossen. 11:47:13 Die Aktion wurde durch den Benutzer abgebrochen. 11:47:13 Vorgang abgeschlossen, Sie können das Fenster nun schließen. My entered data: Benutzername: Stefan Hohrein Benutzerkennung: 7...9(= VR-NetKey) Kundennummer:7...9(= VR-NetKey) I don't understand, why to enter a new bankaccount generally, because all other data where extracted out of the backup. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 415995] New: Cannot assign circumflex as shortcut
https://bugs.kde.org/show_bug.cgi?id=415995 Bug ID: 415995 Summary: Cannot assign circumflex as shortcut Product: systemsettings Version: 5.17.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_keys Assignee: k...@michael-jansen.biz Reporter: den...@episode-iv.de Target Milestone: --- SUMMARY I installed yakuake and tried to set CTRL+circumflex as its global shortcut. When using the default German keyboard layout, it results in a weird, nonprintable character being set as the shortcut (I'll attach a screenshot) and the shortcut subsequently doesn't work. If I switch the keyboard layout to the nodeadkeys variant, it works as expected but I lose the ability to type accented characters. SOFTWARE/OS VERSIONS Gentoo Linux Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.17.4 KDE Frameworks Version: 5.64.0 Qt Version: 5.13.2 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 415995] Cannot assign circumflex as shortcut
https://bugs.kde.org/show_bug.cgi?id=415995 --- Comment #1 from Dennis Lichtenthäler --- Created attachment 124966 --> https://bugs.kde.org/attachment.cgi?id=124966&action=edit resulting shortcut after typing CTRL+circumflex -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 415996] New: Krita crashes when exiting
https://bugs.kde.org/show_bug.cgi?id=415996 Bug ID: 415996 Summary: Krita crashes when exiting Product: krita Version: 4.2.8 Platform: Neon Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: kristopher.i...@gmail.com Target Milestone: --- Created attachment 124967 --> https://bugs.kde.org/attachment.cgi?id=124967&action=edit Backtrace of crash SUMMARY STEPS TO REPRODUCE 1. Open Krita 2. Resize a Photo 3. Save 4. Close Photo 5. Close Krita OBSERVED RESULT File is saved correctly but as closing Krita crashes and the system crash handler appears. EXPECTED RESULT Krita should just close without crashing. SOFTWARE/OS VERSIONS Operating System: KDE neon 5.17 KDE Plasma Version: 5.17.4 KDE Frameworks Version: 5.65.0 Qt Version: 5.13.2 Kernel Version: 4.15.0-74-generic OS Type: 64-bit ADDITIONAL INFORMATION Global menu is being used, kde-hello theme is being used, applet-window-buttons is being used. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 373232] Horizontal lines with fractional HiDPI scaling
https://bugs.kde.org/show_bug.cgi?id=373232 Giusy Digital changed: What|Removed |Added CC||kurmi...@libero.it --- Comment #166 from Giusy Digital --- Definitely not resolved. The following commit (https://cgit.kde.org/konsole.git/commit/?id=54820e0ff2745add8b8353f538ad67d66b657d49) is causing weird font showing inside konsole. Commenting `QCoreApplication::setAttribute(Qt::AA_EnableHighDpiScaling, true);` in `src/main.cpp` or setting it to `false` or launching the application with `QT_AUTO_SCREEN_SCALE_FACTOR=0` fixes the issue. See also here: https://bbs.archlinux.org/viewtopic.php?pid=1881713 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 410867] Krita crashes on exit when saving tags in Qt's pcre code
https://bugs.kde.org/show_bug.cgi?id=410867 Boudewijn Rempt changed: What|Removed |Added CC||kristopher.i...@gmail.com --- Comment #12 from Boudewijn Rempt --- *** Bug 415996 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 415996] Krita crashes when exiting
https://bugs.kde.org/show_bug.cgi?id=415996 Boudewijn Rempt changed: What|Removed |Added CC||b...@valdyas.org Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Boudewijn Rempt --- This is a bug in Qt 5.13. Please try whether the stable nightly build works for you: https://binary-factory.kde.org/job/Krita_Stable_Appimage_Build/ -- that has a workaround. *** This bug has been marked as a duplicate of bug 410867 *** -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 415992] Duplicate Composition Association when rename it's variable in the tree View
https://bugs.kde.org/show_bug.cgi?id=415992 --- Comment #2 from Ralf Habacker --- (In reply to Ralf Habacker from comment #1) > Thanks reportin sed s,Thanks reportin,thanks for reporting,g' -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 414407] Can't load database (plugin)
https://bugs.kde.org/show_bug.cgi?id=414407 --- Comment #13 from Pedro de Carvalho Gomes --- Hi, I need more information that what I have to be able to know what's going on. But I suspect that you are not using Mysql. Rather you have MariaDB, which hasn't deprecated the embedded server. By the way, this is a quick alternative for Lapineige to try to get it working. Replace all Mysql packages with MariaDB alternatives: apt-get install libmariadbclient-dev libmariadbd-dev mariadb-client mariadb-common -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 415896] Stroke selection doesn't work for some selection tools
https://bugs.kde.org/show_bug.cgi?id=415896 --- Comment #9 from acc4commissi...@gmail.com --- 1 After updated to git 0875026(which says this patch has been applied to it) Stroke Selection works on vector layers. Just wanted to report, and hope it's not a bug or an accident. 2 Apparently the original issue has been solved before this patch, because it already worked when I updated to git 04d1174. Again, hope it's not a bug or an accident. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 415997] Kontact had crashed when I returned to machine
https://bugs.kde.org/show_bug.cgi?id=415997 --- Comment #1 from Andreas Hencke --- Created attachment 124968 --> https://bugs.kde.org/attachment.cgi?id=124968&action=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 415997] New: Kontact had crashed when I returned to machine
https://bugs.kde.org/show_bug.cgi?id=415997 Bug ID: 415997 Summary: Kontact had crashed when I returned to machine Product: kontact Version: 5.11.3 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: andreas.hen...@mailbox.org Target Milestone: --- Application: kontact (5.11.3) Qt Version: 5.12.4 Frameworks Version: 5.65.0 Operating System: Linux 5.3.0-26-generic x86_64 Distribution: Ubuntu 19.10 -- Information about the crash: - What I was doing when the application crashed: I made a coffee when I returned to the computer and Kontact crashed - Unusual behavior I noticed: For a few days (before the kernel update) it takes a few seconds (2-3 seconds) when I click on an email in the message list until the message text appears. -- Backtrace (Reduced): #6 0x in () #7 0x7f1087bb88ea in () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7f1087bb89fa in () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7f1087bb8a29 in () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7f108a02f779 in () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 Possible duplicates by query: bug 415991, bug 415973, bug 415962, bug 415960, bug 415956. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 415998] New: Crash when clicking an empty layer with liquify tool
https://bugs.kde.org/show_bug.cgi?id=415998 Bug ID: 415998 Summary: Crash when clicking an empty layer with liquify tool Product: krita Version: nightly build (please specify the git hash!) Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: Tools/Transform Assignee: krita-bugs-n...@kde.org Reporter: acc4commissi...@gmail.com Target Milestone: --- SUMMARY git 0875026 The title says it all. STEPS TO REPRODUCE 1. Select a transform tool > liquify 2. Select any empty layer, and click the canvas. 3. Crash SOFTWARE/OS VERSIONS Windows: Win7 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Error occurred on Wednesday, January 8, 2020 at 20:29:21. krita.exe caused an Access Violation at location 07FECB4974AE in module libkritaimage.dll Reading from location . AddrPC Params 07FECB4974AE 4110FA70 4110F7E8 07FEE2C31575 libkritaimage.dll!0x1d74ae KisLiquifyTransformWorker::run+0x7e 07FEC491B827 4110FB70 4110FCB8 25CA69F0 kritatooltransform.dll!0x3b827 KisTransformUtils::transformDevice+0x307 07FEC4922A04 2BEC3710 07FEFF0713D2 0003 kritatooltransform.dll!0x42a04 TransformStrokeStrategy::transformAndMergeDevice+0x74 07FEC4924224 0001 07887F90 2BEC3680 kritatooltransform.dll!0x44224 TransformStrokeStrategy::doStrokeCallback+0x16b4 07FECB5A1904 0010 25CA6EB0 50A77400 libkritaimage.dll!0x2e1904 KisUpdateJobItem::run+0x94 07FECECD8620 07887F90 50A77400 Qt5Core.dll!0x28620 QThreadPool::tryStart+0x520 07FECECD163F Qt5Core.dll!0x2163f QThread::qt_metacall+0x69f 76FC556D kernel32.dll!0x1556d BaseThreadInitThunk+0xd 7712372D ntdll.dll!0x5372d RtlUserThreadStart+0x1d 00014000-000140F84000 krita.exe 770D-7726F000 ntdll.dll 6.1.7601.24540 07FEEDDA-07FEEDDB4000 aswhook.dll 19.8.4793.0 76FB-770CF000 kernel32.dll 6.1.7601.24540 07FEFCC7-07FEFCCD7000 KERNELBASE.dll6.1.7601.24540 07FEF4BE-07FEF4C28000 libkritaglobal.dll 07FEFAFD-07FEFAFDE000 libkritaversion.dll 6144-6145A000 libgcc_s_seh-1.dll 07FEFF07-07FEFF10F000 msvcrt.dll7.0.7601.17744 6494-64955000 libwinpthread-1.dll 1.0.0.0 6FC4-6FDA5000 libstdc++-6.dll 76EB-76FAA000 USER32.dll6.1.7601.24540 07FEFF11-07FEFF177000 GDI32.dll 6.1.7601.24540 07FEFF18-07FEFF18E000 LPK.dll 6.1.7601.24537 07FEFE82-07FEFE8EB000 USP10.dll 1.626.7601.24535 07FECECB-07FECF2DB000 Qt5Core.dll 5.12.5.0 07FEFF2C-07FEFF39B000 ADVAPI32.dll 6.1.7601.24540 07FEFEDA-07FEFEDBF000 sechost.dll 6.1.7601.18869 07FEFF19-07FEFF2BC000 RPCRT4.dll6.1.7601.24540 07FEF535-07FEF5368000 MPR.dll 6.1.7600.16385 07FEFAAC-07FEFAAD6000 NETAPI32.dll 6.1.7601.17887 07FEFA90-07FEFA90C000 netutils.dll 6.1.7601.17514 07FEFC6C-07FEFC6E3000 srvcli.dll6.1.7601.17514 07FEFA8C-07FEFA8D5000 wkscli.dll6.1.7601.17514 07FEFCFF-07FEFD1EF000 ole32.dll 6.1.7601.24537 07FEFD79-07FEFE51B000 SHELL32.dll 6.1.7601.24468 07FEFEDC-07FEFEE31000 SHLWAPI.dll 6.1.7601.17514 07FEFCCE-07FEFCCFF000 USERENV.dll 6.1.7601.24535 07FEFCC2-07FEFCC2F000 profapi.dll 6.1.7600.16385 07FEFBC9-07FEFBC9C000 VERSION.dll 6.1.7600.16385 07FEFABF-07FEFAC2B000 WINMM.dll 6.1.7600.16385 07FEFD74-07FEFD78D000 WS2_32.dll6.1.7601.23451 07FEFCFE-07FEFCFE8000 NSI.dll 6.1.7601.23889 07FEE439-07FEE43E6000 libKF5I18n.dll 07FEFA27-07FEFA28E000 libintl.DLL 0.18.0.0 07FEF4BC-07FEF4BD2000 iconv.dll 07FECDE3-07FECE44B000 Qt5Gui.dll5.12.5.0 07FECD8C-07FECDE2D000 Qt5Widgets.dll5.12.5.0 07FEFBCA-07FEFBCB8000 dwmapi.dll6.1.7601.18917 07FEFB5B-07FEFB606000 UxTheme.dll 6.1.7600.16385 07FEE316-07FEE319B000 Qt5Xml.dll5.12.5.0 07FECB2C-07FECB80F000 libkritaimage.dll 07FEF4BA-07FEF4BBF000 libkritacommand.dll 07FEE2B6-07FEE2C94000 libkritawidgetutils.dll 07FEE30C-07FEE3153000 libkritaodf.dll 07FEF06D-07FEF06F3000 libkritaplugin.dll 07FEE2B
[yakuake] [Bug 412392] Open new tab/split in same directory
https://bugs.kde.org/show_bug.cgi?id=412392 lava changed: What|Removed |Added CC||shgr11...@yandex.ru --- Comment #1 from lava --- I second that. Very annoying to cd every single time. Like cd'ing to home directory is easy just type 'cd' so it shouldn't be a default behavior. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 415998] Crash when clicking an empty layer with liquify tool
https://bugs.kde.org/show_bug.cgi?id=415998 Boudewijn Rempt changed: What|Removed |Added Ever confirmed|0 |1 CC||b...@valdyas.org Status|REPORTED|CONFIRMED --- Comment #1 from Boudewijn Rempt --- KisLiquifyTransformWorker::run(KisSharedPtr) () at /home/boud/dev/krita/libs/image/kis_liquify_transform_worker.cpp:441 441 Private::MapIndexesOp indexesOp(m_d.data()); (gdb) bt #0 0x7560e648 in KisLiquifyTransformWorker::run(KisSharedPtr) (this=0x0, device=...) at /home/boud/dev/krita/libs/image/kis_liquify_transform_worker.cpp:441 #1 0x7fffb9879485 in KisTransformUtils::transformDevice(ToolTransformArgs const&, KisSharedPtr, KisProcessingVisitor::ProgressHelper*) (config=..., device=..., helper=) at /usr/include/c++/8/bits/atomic_base.h:295 #2 0x7fffb9883998 in TransformStrokeStrategy::transformAndMergeDevice(ToolTransformArgs const&, KisSharedPtr, KisSharedPtr, KisProcessingVisitor::ProgressHelper*) (this= 0x613a3ad0, helper=0x7fff877fdb30, dst=..., src=..., config=...) at /usr/include/c++/8/bits/atomic_base.h:295 #3 0x7fffb9883998 in TransformStrokeStrategy::doStrokeCallback(KisStrokeJobData*) (this=0x613a3ad0, data=) at /home/boud/dev/krita/plugins/tools/tool_transform2/strokes/transform_stroke_strategy.cpp:264 #4 0x756da3dc in non-virtual thunk to KisUpdateJobItem::run() () at /home/boud/dev/i-krita/lib/x86_64-linux-gnu/libkritaimage.so.19 #5 0x73230472 in QThreadPoolThread::run() (this=0x61c5c5d0) at thread/qthreadpool.cpp:99 #6 0x7322cb52 in QThreadPrivate::start(void*) (arg=0x61c5c5d0) at thread/qthread_unix.cpp:360 #7 0x7fffec4326db in start_thread (arg=0x7fff877fe700) at pthread_create.c:463 #8 0x7291188f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 415896] Stroke selection doesn't work for some selection tools
https://bugs.kde.org/show_bug.cgi?id=415896 --- Comment #10 from acc4commissi...@gmail.com --- (In reply to acc4commissions from comment #9) > 1 After updated to git 0875026(which says this patch has been applied to it) > Stroke Selection works on vector layers. Just wanted to report, and hope > it's not a bug or an accident. > > 2 Apparently the original issue has been solved before this patch, because > it already worked when I updated to git 04d1174. Again, hope it's not a bug > or an accident. I take back what I said about the vector layer. It seems to work like it's supposed to. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 415996] Krita crashes when exiting
https://bugs.kde.org/show_bug.cgi?id=415996 --- Comment #2 from Kristopher Ives --- Thanks. Is there a way to get the latest Krita as a PPA? I would really like to keep using the package manager version instead of AppImage. The PPA I found was: https://launchpad.net/~kritalime/+archive/ubuntu/ppa But it seems to only be 4.2.8? Thank you again for the help. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 415999] New: Progress bar goes backwards when tagging faces (from (100% to 0%)
https://bugs.kde.org/show_bug.cgi?id=415999 Bug ID: 415999 Summary: Progress bar goes backwards when tagging faces (from (100% to 0%) Product: digikam Version: 7.0.0 Platform: Appimage OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Faces-Maintenance Assignee: digikam-bugs-n...@kde.org Reporter: iwannaber...@gmail.com Target Milestone: --- SUMMARY This is just a minor cosmetic issue, but I thought of reporting it anyway. In the People panel, if you go to the Unknown section and select several faces and tag them with a name, the progress bar on the bottom will start at 100% and end at 0%. Everything still works just fine, it's just that the progress bar goes backwards. STEPS TO REPRODUCE 1. Select several faces from the Unknown category in People. 2. Tag them with a name. 3. Observe progress bar. OBSERVED RESULT Goes from 100 to 0. EXPECTED RESULT Goes from 0 to 100. SOFTWARE/OS VERSIONS digikam-7.0.0-beta2-20200105T130918-x86-64.appimage in Ubuntu 18.04LTS with Unity. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 415999] Progress bar goes backwards when tagging faces (from (100% to 0%)
https://bugs.kde.org/show_bug.cgi?id=415999 MarcP changed: What|Removed |Added CC||iwannaber...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 415992] Duplicate Composition Association when rename it's variable in the tree View
https://bugs.kde.org/show_bug.cgi?id=415992 Ralf Habacker changed: What|Removed |Added Attachment #124969|0 |1 is obsolete|| --- Comment #4 from Ralf Habacker --- Created attachment 124970 --> https://bugs.kde.org/attachment.cgi?id=124970&action=edit Screenshot showing what is broken (update) -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 415992] Duplicate Composition Association when rename it's variable in the tree View
https://bugs.kde.org/show_bug.cgi?id=415992 --- Comment #3 from Ralf Habacker --- Created attachment 124969 --> https://bugs.kde.org/attachment.cgi?id=124969&action=edit Screenshot showing what is broken I have attached a screenshot that contains use cases for the visual representation of compositions (and related aggregations). Did I forget anything ? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 415996] Krita crashes when exiting
https://bugs.kde.org/show_bug.cgi?id=415996 --- Comment #3 from Boudewijn Rempt --- No, we don't have nightly builds in a ppa. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 415782] face recognition "favors" people with few images
https://bugs.kde.org/show_bug.cgi?id=415782 MarcP changed: What|Removed |Added CC||iwannaber...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 379516] hide loop devices created by snapd
https://bugs.kde.org/show_bug.cgi?id=379516 --- Comment #16 from Méven Car --- Well apparently your are running an a version of solid that does not include https://phabricator.kde.org/D9895, somehow. On Kubuntu 19.10, this command only outputs my main nvme drive with solid-hardware5 (package libkf5solid-bin 5.62.0-0ubuntu1) On kde-neon VM I have, with solid-hardware I have a similar output as you do, but not the bug (the loop devices in the places panel). But with solid-hardware5 (compiled locally), I have what I expect (only main harddrive) like with kubuntu. I wonder if there is a packaging issue for solid in kde-neon. I am puzzled. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 332372] Edit and save (PDF) Document Information
https://bugs.kde.org/show_bug.cgi?id=332372 Māris Nartišs changed: What|Removed |Added CC||maris@gmail.com --- Comment #2 from Māris Nartišs --- This wish should be merged with Bug 377460. Note, there is also a problem with XMP tags being not displayed anywhere. It is tracked as Bug 385015. -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 412327] Plugin library 'kde_grantlee_plugin' not found
https://bugs.kde.org/show_bug.cgi?id=412327 Harald Sitter changed: What|Removed |Added CC||skna...@kde.org --- Comment #13 from Harald Sitter --- Sandro, what's your thinking on this? In debian the only relationship chain is kaddressbook -> depends libkf5grantleetheme5 -> recommends libkf5grantleetheme-plugins and as a result a user could uninstall the plugins when that seems entirely disadvantageous. -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 415967] Please publish the extension to addons.opera.com
https://bugs.kde.org/show_bug.cgi?id=415967 Kai Uwe Broulik changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Kai Uwe Broulik --- I literally did in December and it just got published now. :) I still can't find it listed on the Opera store, though... However, thanks to their amazingly tedious review process, they missed the deadline for Plasma 5.17.5 and because for whatever reason the extension ID is different (despite having been signed with the same key!) I'll have to whitelist the extension for Plasma 5.18. -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 415950] 100% CPU usage of plasmashell
https://bugs.kde.org/show_bug.cgi?id=415950 --- Comment #1 from Kai Uwe Broulik --- Download status is updated only every second. I believe it's the typical busy indicator (the spinning icon in your tray) causing excess CPU issue on some GPUs bug... -- You are receiving this mail because: You are watching all bug changes.
[klines] [Bug 129791] blocks and squares modes
https://bugs.kde.org/show_bug.cgi?id=129791 --- Comment #3 from Laurent Montel --- Git commit 182f73187c681d069cab33c260c820a8d0af8296 by Laurent Montel. Committed on 08/01/2020 at 12:36. Pushed by mlaurent into branch 'master'. Add endgame support. Patch from Kyryll A Mirnenko aka Mirya (2011) M +1-0klines.cpp M +6-0scene.cpp M +4-0scene.h https://commits.kde.org/klines/182f73187c681d069cab33c260c820a8d0af8296 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 415782] face recognition "favors" people with few images
https://bugs.kde.org/show_bug.cgi?id=415782 --- Comment #13 from MarcP --- I have also noticed that the precision of face recognition did not improve if a person had more pictures. Until that moment, I had tried the face recognition algorithm using a dataset of 85 famous people (http://vis-www.cs.umass.edu/lfw/), mostly portraits centered on their face, looking at the camera, with samples from 16 to 300 pictures each. In that case, tagging about 12 to 40 pictures of each person I achieved around a 80% of true positives (set at an accuracy of 70%). However, testing the algorithm in my personal database, including around 1500 different people, with some of them having thousands of faces, I had a very different experience. While the face detection works very well (it even detects babies!), recognition rates were below 1% of true positives, where results seem to be completely random. Maybe the number of people in the collection could be weighted in towards the recognition? Or try to predict which people are in a picture based on similar pictures of the same album or date? Or maybe an advanced option to consider a larger number of faces for each person? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 415782] face recognition "favors" people with few images
https://bugs.kde.org/show_bug.cgi?id=415782 --- Comment #14 from MarcP --- Or what about preventing recognizing faces for people with a very low sample? (e.g. fewer than 15 or 20 faces) -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 415990] the application assumes the class element is a folder type
https://bugs.kde.org/show_bug.cgi?id=415990 Christoph Feck changed: What|Removed |Added Version Fixed In|2.30.80 (KDE Applications |2.30.80 (KDE Applications |19.03.80) |20.03.80) -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 415967] Please publish the extension to addons.opera.com
https://bugs.kde.org/show_bug.cgi?id=415967 --- Comment #2 from Kyrylo Bohdanenko --- Thank you very much! On Wed, Jan 8, 2020, 13:38 Kai Uwe Broulik wrote: > https://bugs.kde.org/show_bug.cgi?id=415967 > > Kai Uwe Broulik changed: > >What|Removed |Added > > > Status|REPORTED|RESOLVED > Resolution|--- |FIXED > > --- Comment #1 from Kai Uwe Broulik --- > I literally did in December and it just got published now. :) I still can't > find it listed on the Opera store, though... > > However, thanks to their amazingly tedious review process, they missed the > deadline for Plasma 5.17.5 and because for whatever reason the extension > ID is > different (despite having been signed with the same key!) I'll have to > whitelist the extension for Plasma 5.18. > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 415999] Progress bar goes backwards when tagging faces (from (100% to 0%)
https://bugs.kde.org/show_bug.cgi?id=415999 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #1 from Maik Qualmann --- If you open the progress manager, you will see that there are 2 processes in quick succession. The first jumps to 100, then the second starts at 0. In the overall display it looks as if it is going backwards. Maik -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 416000] New: 2 Internal Error(Safe Assert) messages when opening kra file that has vector layer
https://bugs.kde.org/show_bug.cgi?id=416000 Bug ID: 416000 Summary: 2 Internal Error(Safe Assert) messages when opening kra file that has vector layer Product: krita Version: nightly build (please specify the git hash!) Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: acc4commissi...@gmail.com Target Milestone: --- Created attachment 124972 --> https://bugs.kde.org/attachment.cgi?id=124972&action=edit Capture SUMMARY git 0875026 STEPS TO REPRODUCE 1. Create a vector layer and save the document. 2. Open it again. 3. Error message. SOFTWARE/OS VERSIONS Windows: Win7 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 416000] 2 Internal Error(Safe Assert) messages when opening kra file that has vector layer
https://bugs.kde.org/show_bug.cgi?id=416000 Boudewijn Rempt changed: What|Removed |Added CC||b...@valdyas.org --- Comment #1 from Boudewijn Rempt --- Is this with the appimage? The appimages we build on the binary factory have the safe asserts disabled. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 416001] New: konsole displays fonts differently than the rest of applications
https://bugs.kde.org/show_bug.cgi?id=416001 Bug ID: 416001 Summary: konsole displays fonts differently than the rest of applications Product: konsole Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: font Assignee: konsole-de...@kde.org Reporter: andr...@rybczak.net Target Milestone: --- Created attachment 124973 --> https://bugs.kde.org/attachment.cgi?id=124973&action=edit Demonstration of different rendering of Dejavu Sans Mono 10pt in konsole SUMMARY After a system update (a bunch of plasma apps were upgraded from 5.17.4 to 5.17.5) konsole (and kwrite btw) renders fonts differently than the rest of applications (see attached screenshot for details). STEPS TO REPRODUCE 1. Check out DejaVu Sans Mono font in system settings and in konsole settings. OBSERVED RESULT Fonts are rendered differently in konsole/kwrite than the rest of apps. EXPECTED RESULT Fonts are rendered the same way in konsole/kwrite as the rest of apps. SOFTWARE/OS VERSIONS Linux: Arch Linux, kernel 5.4.8-arch1-1 KDE Plasma Version: 5.17.5 KDE Frameworks Version: 5.65.0 Qt Version: 5.14.0 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 416001] konsole displays fonts differently than the rest of applications
https://bugs.kde.org/show_bug.cgi?id=416001 Andrzej Rybczak changed: What|Removed |Added Platform|Other |Archlinux Packages -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 415999] Progress bar goes backwards when tagging faces (from (100% to 0%)
https://bugs.kde.org/show_bug.cgi?id=415999 --- Comment #2 from MarcP --- Aha. It could be what you say. What I usually see, is a bar for each tagged image, and the one on top being the one that appears to go backwards. Here is an example: https://imgur.com/a/OygbhZs -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 416002] New: 1 installation transactions failed There was a problem during the installation: mariadb-extra(x86-64) < 10.3.20-1.mga7 conflicts with mariadb-10.3.20-1.mga7.x86_64
https://bugs.kde.org/show_bug.cgi?id=416002 Bug ID: 416002 Summary: 1 installation transactions failed There was a problem during the installation: mariadb-extra(x86-64) < 10.3.20-1.mga7 conflicts with mariadb-10.3.20-1.mga7.x86_64 Product: Spectacle Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: oagwo...@yahoo.com CC: k...@david-redondo.de Target Milestone: --- Created attachment 124974 --> https://bugs.kde.org/attachment.cgi?id=124974&action=edit 1 installation transactions failed There was a problem during the installation: mariadb-extra(x86-64) < 10.3.20-1.mga7 conflicts with mariadb-10.3.20-1.mga7.x86_64 SUMMARY 1 installation transactions failed There was a problem during the installation: mariadb-extra(x86-64) < 10.3.20-1.mga7 conflicts with mariadb-10.3.20-1.mga7.x86_64 STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 416000] 2 Internal Error(Safe Assert) messages when opening kra file that has vector layer
https://bugs.kde.org/show_bug.cgi?id=416000 Boudewijn Rempt changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #2 from Boudewijn Rempt --- Okay, see the asserts, but only on the commandline, with the appimages we build, and not in 4.2.8 -- but it is present in the 4.2 branch. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 413578] if fractional display scaling is used, scrolling by dragging the scroll bar makes the icons flicker
https://bugs.kde.org/show_bug.cgi?id=413578 Ardith Metz changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #2 from Ardith Metz --- This issue seems fixed in the following setup (I think qt update to 5.14 and rebuild plasma against it was crucial): SOFTWARE/OS VERSIONS KDE Plasma Version: 5.17.5 KDE Frameworks Version: 5.65.0 Qt Version: 5.14.0 Dolphin: 19.12.0 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 416000] 2 Internal Error(Safe Assert) messages when opening kra file that has vector layer
https://bugs.kde.org/show_bug.cgi?id=416000 Boudewijn Rempt changed: What|Removed |Added Assignee|krita-bugs-n...@kde.org |b...@valdyas.org -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 414818] Krita crashes when loading files containing colorize mask
https://bugs.kde.org/show_bug.cgi?id=414818 Boudewijn Rempt changed: What|Removed |Added Latest Commit|https://invent.kde.org/kde/ |https://invent.kde.org/kde/ |krita/commit/478a8be4ef0c9d |krita/commit/fef559371da1cb |5ad073e37696e71737f7eb4282 |d9c20814938620823d89ed9830 --- Comment #9 from Boudewijn Rempt --- Git commit fef559371da1cbd9c20814938620823d89ed9830 by Boudewijn Rempt. Committed on 08/01/2020 at 13:34. Pushed by rempt into branch 'krita/4.2'. Fix endless recursion in KisAssignProfileProcessingVisitor::visitColorizeMask (cherry picked from commit 478a8be4ef0c9d5ad073e37696e71737f7eb4282) M +0-1libs/image/processing/kis_assign_profile_processing_visitor.cpp https://invent.kde.org/kde/krita/commit/fef559371da1cbd9c20814938620823d89ed9830 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 414890] Palette Docker does not show swatches 9 Version: 4.3.0-prealpha (git 818c841)
https://bugs.kde.org/show_bug.cgi?id=414890 Boudewijn Rempt changed: What|Removed |Added Latest Commit|https://invent.kde.org/kde/ |https://invent.kde.org/kde/ |krita/commit/ef55574a4af751 |krita/commit/1a76a971ae4677 |34a2a9be03fcd70e8b16aaf614 |ab984e3fd0111db26a442794f0 --- Comment #3 from Boudewijn Rempt --- Git commit 1a76a971ae4677ab984e3fd0111db26a442794f0 by Boudewijn Rempt, on behalf of Ivan Yossi. Committed on 08/01/2020 at 13:33. Pushed by rempt into branch 'krita/4.2'. Fix PaletteDocker not showing palettes Reverts 97c03e0f3314dae5520deb901dda73d1cf8df201 "-1" is a QMap key to signal "root group" Changed Q_ASSERT to KIS_ASSERT_RECOVER_RETURN_VALUE to try and avoid crashing if Qt is compiled in debug mode. M +2-2libs/widgets/KisPaletteModel.cpp https://invent.kde.org/kde/krita/commit/1a76a971ae4677ab984e3fd0111db26a442794f0 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 415810] Recovered autosaves are by default saved in incorrect location
https://bugs.kde.org/show_bug.cgi?id=415810 Boudewijn Rempt changed: What|Removed |Added Latest Commit|https://invent.kde.org/kde/ |https://invent.kde.org/kde/ |krita/commit/b4c44d395a7deb |krita/commit/a03c16cc9b8777 |d33c4bc1d9de52dcd556980a9a |f8c6ebf7a6e62a02cdcccb6e3a --- Comment #2 from Boudewijn Rempt --- Git commit a03c16cc9b8777f8c6ebf7a6e62a02cdcccb6e3a by Boudewijn Rempt. Committed on 08/01/2020 at 13:33. Pushed by rempt into branch 'krita/4.2'. Set the default location for restored files to QStandardPaths::PicturesLocation M +10 -1libs/ui/KisMainWindow.cpp https://invent.kde.org/kde/krita/commit/a03c16cc9b8777f8c6ebf7a6e62a02cdcccb6e3a -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 415218] Case-sensitivity import issue
https://bugs.kde.org/show_bug.cgi?id=415218 Boudewijn Rempt changed: What|Removed |Added Latest Commit|https://invent.kde.org/kde/ |https://invent.kde.org/kde/ |krita/commit/08e7240a6e77b8 |krita/commit/3eac2fc789435d |db1622256420ee56af0bbf6b9f |d4de8b4b03b5e91cf3489381d4 --- Comment #2 from Boudewijn Rempt --- Git commit 3eac2fc789435dd4de8b4b03b5e91cf3489381d4 by Boudewijn Rempt, on behalf of Ivan Yossi. Committed on 08/01/2020 at 13:33. Pushed by rempt into branch 'krita/4.2'. macOS: Fix case sensitive include for macOS with case sensitive File Systems M +1-1libs/ui/osx.mm https://invent.kde.org/kde/krita/commit/3eac2fc789435dd4de8b4b03b5e91cf3489381d4 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 415625] Crash in transform tool
https://bugs.kde.org/show_bug.cgi?id=415625 Boudewijn Rempt changed: What|Removed |Added Latest Commit|https://invent.kde.org/kde/ |https://invent.kde.org/kde/ |krita/commit/69bc2897bf9fb6 |krita/commit/5e5ded75c9f107 |b88ef4bb2754f877057c0a3ea7 |ff5e1601f7d3137ce558503901 --- Comment #3 from Boudewijn Rempt --- Git commit 5e5ded75c9f107ff5e1601f7d3137ce558503901 by Boudewijn Rempt. Committed on 08/01/2020 at 13:34. Pushed by rempt into branch 'krita/4.2'. Convert Q_ASSERT to KIS_SAFE_ASSERT This doesn't properly fix bug 415625, but the assert here in addJob shouldn't be fatal. (cherry picked from commit 69bc2897bf9fb6b88ef4bb2754f877057c0a3ea7) M +3-3libs/image/kis_stroke.cpp https://invent.kde.org/kde/krita/commit/5e5ded75c9f107ff5e1601f7d3137ce558503901 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 415896] Stroke selection doesn't work for some selection tools
https://bugs.kde.org/show_bug.cgi?id=415896 Boudewijn Rempt changed: What|Removed |Added Latest Commit|https://invent.kde.org/kde/ |https://invent.kde.org/kde/ |krita/commit/94dc6c1a404119 |krita/commit/d921fa60a37cab |a26fc3ff9e27fab63e2e1256e5 |528855919ebf124426bb2c0dbf --- Comment #11 from Boudewijn Rempt --- Git commit d921fa60a37cab528855919ebf124426bb2c0dbf by Boudewijn Rempt. Committed on 08/01/2020 at 13:34. Pushed by rempt into branch 'krita/4.2'. Fix logic for enabling/disabling options in stroke selection dialog (cherry picked from commit 94dc6c1a404119a26fc3ff9e27fab63e2e1256e5) M +79 -91 libs/ui/dialogs/kis_dlg_stroke_selection_properties.cpp M +12 -8libs/ui/dialogs/kis_dlg_stroke_selection_properties.h M +190 -152 libs/ui/forms/wdgstrokeselectionproperties.ui M +2-0libs/ui/kis_selection_manager.cc https://invent.kde.org/kde/krita/commit/d921fa60a37cab528855919ebf124426bb2c0dbf -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 413548] Color Selector Tool 'Add to palette:' option crashes if selected palette has been deleted
https://bugs.kde.org/show_bug.cgi?id=413548 Boudewijn Rempt changed: What|Removed |Added Latest Commit|https://invent.kde.org/kde/ |https://invent.kde.org/kde/ |krita/commit/d25b10a4c25e5f |krita/commit/7d72be15bc3a6e |ed309ff97b532e9eaf880f9a85 |f7a5d17bf7ac15a2770c14dcbe --- Comment #5 from Boudewijn Rempt --- Git commit 7d72be15bc3a6ef7a5d17bf7ac15a2770c14dcbe by Boudewijn Rempt, on behalf of Saurabh Kumar. Committed on 08/01/2020 at 13:33. Pushed by rempt into branch 'krita/4.2'. Prevent crash on addition of color to deleted palette with colorpicker This commit makes the deletion and addition of palette in palette docker show in colorpicker's tool options' Add to palette comboBox. This also prevents a crash due to a dangling pointer due to palette pointing to deleted memory location. M +60 -4plugins/tools/basictools/kis_tool_colorpicker.cc M +14 -3plugins/tools/basictools/kis_tool_colorpicker.h https://invent.kde.org/kde/krita/commit/7d72be15bc3a6ef7a5d17bf7ac15a2770c14dcbe -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 416000] 2 Internal Error(Safe Assert) messages when opening kra file that has vector layer
https://bugs.kde.org/show_bug.cgi?id=416000 --- Comment #3 from Boudewijn Rempt --- Okay, this is caused by commit dde9dd4d0d0b4148cbfebcfb64f7a76a89c884ac (refs/bisect/bad) Author: Ivan Yossi Date: Sun Jan 5 19:48:05 2020 + Delay initialization of brush paintop widget state State requires an active view in the canvas to change widget status. BUG:415033 Which seems completely unrelated... -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 414672] Crash in uninitialized transform tool
https://bugs.kde.org/show_bug.cgi?id=414672 --- Comment #19 from Tymond --- Created attachment 124975 --> https://bugs.kde.org/attachment.cgi?id=124975&action=edit Backtrace trying to reproduce, identical to the one from bug 415625 I'm on 3f0ff1a86c + a few irrelevant commits. When I try to reproduce according to boud's steps: - (I first select Move Tool) - it doesn't assert after changing from Move Tool to Transform Tool - it does crash when changing from Transform Tool to Freehand Brush Tool... but the crash log seem to be identical with what I would get in bug 415625: So @boud if you cannot reproduce it now after fixing bug 415625, that might be a reason and this bug should be closed as well? Thread 31 "Thread (pooled)" received signal SIGABRT, Aborted. [Switching to Thread 0x7fff97fff700 (LWP 27201)] __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 50 ../sysdeps/unix/sysv/linux/raise.c: No such file or directory. (gdb) thread apply all bt Thread 31 (Thread 0x7fff97fff700 (LWP 27201)): #0 0x74262077 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 #1 0x74243535 in __GI_abort () at abort.c:79 #2 0x746318d7 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x74630d59 in qt_assert_x(char const*, char const*, char const*, int) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x75a15528 in KisStroke::addJob(KisStrokeJobData*) (this=, data=) at /home/tymon/devsec/krita/libs/image/kis_stroke.cpp:84 #5 0x75c828e2 in KisStrokesQueue::addJob(QWeakPointer, KisStrokeJobData*) (this=, id=..., data=0x7fffb80017c0) at /home/tymon/devsec/krita/libs/image/kis_strokes_queue.cpp:339 #6 0x75c8fbc0 in KisUpdateScheduler::addJob(QWeakPointer, KisStrokeJobData*) (this=0x739a4c80, id=..., data=) at /usr/include/c++/8/bits/atomic_base.h:295 #7 0x75cb8e2f in non-virtual thunk to KisImage::addJob(QWeakPointer, KisStrokeJobData*) () at /usr/include/c++/8/bits/atomic_base.h:295 #8 0x75b75bb2 in KisSavedMacroCommand::addCommands(QWeakPointer, bool) (this=0x70ba9df0, id=..., undo=) at /usr/include/c++/8/bits/atomic_base.h:295 #9 0x75b74802 in KisSavedMacroCommand::performCancel(QWeakPointer, bool) (this=, id=..., strokeUndo=) at /usr/include/c++/8/bits/atomic_base.h:295 #10 0x75c7de85 in KisStrokeStrategyUndoCommandBased::cancelStrokeCallback() (this=0x5bb90b60) at /usr/include/c++/8/bits/atomic_base.h:295 #11 0x7fffd495a2a5 in TransformStrokeStrategyoperator() (__closure=0x7fffb0004c18, __closure=0x7fffb0004c18) at /home/tymon/devsec/krita/plugins/tools/tool_transform2/strokes/transform_stroke_strategy.cpp:686 #12 0x7fffd495a2a5 in std::_Function_handler::_M_invoke(std::_Any_data const&) (__functor=...) at /usr/include/c++/8/bits/std_function.h:297 #13 0x75c7e05b in KisStrokeStrategyUndoCommandBased::doStrokeCallback(KisStrokeJobData*) (this=0x5bb90b60, data=0x7fffb0004bf0) at /home/tymon/devsec/krita/libs/image/kis_stroke_strategy_undo_command_based.cpp:131 #14 0x7fffd495e59c in TransformStrokeStrategy::doStrokeCallback(KisStrokeJobData*) (this=0x5bb90b50, data=0x7fffb0004bf0) at /home/tymon/devsec/krita/plugins/tools/tool_transform2/strokes/transform_stroke_strategy.cpp:350 #15 0x75e988cc in non-virtual thunk to KisUpdateJobItem::run() () at /usr/include/c++/8/bits/atomic_base.h:295 #16 0x7466af71 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #17 0x74672c87 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #18 0x7206e164 in start_thread (arg=) at pthread_create.c:486 #19 0x7433bdef in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 415651] Multi-brush tool: Copy Translate "Add" button should disable when I choose other type
https://bugs.kde.org/show_bug.cgi?id=415651 Boudewijn Rempt changed: What|Removed |Added Latest Commit|https://invent.kde.org/kde/ |https://invent.kde.org/kde/ |krita/commit/df825790541e52 |krita/commit/aefd5398b57590 |26e26a2e8e221ae28169dce2c4 |48e2f5db5397da874ac5c8d559 --- Comment #3 from Boudewijn Rempt --- Git commit aefd5398b5759048e2f5db5397da874ac5c8d559 by Boudewijn Rempt, on behalf of Saurabh Kumar. Committed on 08/01/2020 at 13:33. Pushed by rempt into branch 'krita/4.2'. Make Add subbrush off on changing multibrush tool's type from Copy Translate This commit makes the Add option of subbrush off when changing from Copy Translate type to any other type. The option is toggled off even for Copy Translate type of multibrush. Previously the Add option stayed on and drawing with other tools was not possible unless it was turned off. M +2-0plugins/tools/basictools/kis_tool_multihand.cpp https://invent.kde.org/kde/krita/commit/aefd5398b5759048e2f5db5397da874ac5c8d559 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 415033] Opacity, brush size and blending modes are disabled in "brushes and stuff toolbar" if you close all open documents and open a new one while the "move" tool is selected
https://bugs.kde.org/show_bug.cgi?id=415033 Boudewijn Rempt changed: What|Removed |Added Latest Commit|https://invent.kde.org/kde/ |https://invent.kde.org/kde/ |krita/commit/7ef60648faf92e |krita/commit/dde9dd4d0d0b41 |b7e7939351cfd6b75706b497b7 |48cbfebcfb64f7a76a89c884ac --- Comment #3 from Boudewijn Rempt --- Git commit dde9dd4d0d0b4148cbfebcfb64f7a76a89c884ac by Boudewijn Rempt, on behalf of Ivan Yossi. Committed on 08/01/2020 at 13:34. Pushed by rempt into branch 'krita/4.2'. Delay initialization of brush paintop widget state State requires an active view in the canvas to change widget status. M +7-7libs/ui/KisMainWindow.cpp https://invent.kde.org/kde/krita/commit/dde9dd4d0d0b4148cbfebcfb64f7a76a89c884ac -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 415935] Colorize Mask: Cursor disappears when there's no colorize mask layer
https://bugs.kde.org/show_bug.cgi?id=415935 Boudewijn Rempt changed: What|Removed |Added Latest Commit|https://invent.kde.org/kde/ |https://invent.kde.org/kde/ |krita/commit/f30b0574a3f162 |krita/commit/fc54c03ea10f5e |4546ad8fd431da6931a6b9edea |7a9ee9cdbf83ce482338e620c7 --- Comment #7 from Boudewijn Rempt --- Git commit fc54c03ea10f5e7a9ee9cdbf83ce482338e620c7 by Boudewijn Rempt. Committed on 08/01/2020 at 13:34. Pushed by rempt into branch 'krita/4.2'. Show the hand cursor if there is no colorize mask yet (cherry picked from commit f30b0574a3f1624546ad8fd431da6931a6b9edea) M +12 -3plugins/tools/tool_lazybrush/kis_tool_lazy_brush.cpp https://invent.kde.org/kde/krita/commit/fc54c03ea10f5e7a9ee9cdbf83ce482338e620c7 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 415794] Krita crashes when opening a file 3 times without krita already open
https://bugs.kde.org/show_bug.cgi?id=415794 Boudewijn Rempt changed: What|Removed |Added Latest Commit|https://invent.kde.org/kde/ |https://invent.kde.org/kde/ |krita/commit/4c715c4c9470b9 |krita/commit/8db82515ce132c |a454413cd9002ace514abc7ee1 |1190597aae1aa1f80f841dd5af --- Comment #4 from Boudewijn Rempt --- Git commit 8db82515ce132c1190597aae1aa1f80f841dd5af by Boudewijn Rempt. Committed on 08/01/2020 at 13:33. Pushed by rempt into branch 'krita/4.2'. Don't crash if remoteArguments is called when there isn't a mainwindow This isn't perfect: if you're fast enough you can still start a couple of Krita processes even if application process sharing is enabled. That can't be helped, though. M +22 -15 libs/ui/KisApplication.cpp M +1-0libs/ui/KisApplication.h https://invent.kde.org/kde/krita/commit/8db82515ce132c1190597aae1aa1f80f841dd5af -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 414672] Crash in uninitialized transform tool
https://bugs.kde.org/show_bug.cgi?id=414672 Boudewijn Rempt changed: What|Removed |Added Resolution|--- |FIXED Status|REOPENED|RESOLVED Latest Commit|https://invent.kde.org/kde/ |https://invent.kde.org/kde/ |krita/commit/2dc2ed5f5a6be2 |krita/commit/47423c9abab188 |b81aab5001de8389e3f3cbdcac |a53c4003a09ce6bdf0824baef9 --- Comment #20 from Boudewijn Rempt --- Git commit 47423c9abab188a53c4003a09ce6bdf0824baef9 by Boudewijn Rempt, on behalf of Dmitry Kazakov. Committed on 08/01/2020 at 14:13. Pushed by rempt into branch 'krita/4.2'. Fix a crash when cancelling Transform Tool action The crash happens only on systems that have asserts enabled, that is, don't have NDEBUG defined. Binding uninitialized '*m_savedTransformArgs' to a cont-reference generated valid c++ code (a reference initialized with nullptr), and given that finishStrokeImpl() didn't try to use/dereference this reference, the code worked fine and didn't crash on systems without asserts. But on systems with asserts enabled (non NDEBUG), boost::optional triggered a sanity check assert for dereferencing nullptr and crashed the application. The patch removes entire code for resetting m_savedTransformArgs in cancelStrokeCallback(). It was actually an artifact of some initial refactoring. Thanks Fredrik Hansson for pointing out the problem! https://invent.kde.org/kde/krita/merge_requests/197 (cherry picked from commit 2dc2ed5f5a6be2b81aab5001de8389e3f3cbdcac) M +1-8 plugins/tools/tool_transform2/strokes/transform_stroke_strategy.cpp https://invent.kde.org/kde/krita/commit/47423c9abab188a53c4003a09ce6bdf0824baef9 -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 413368] upgraded to 5.17.x, krunner alt-f2 shortcut stopped working
https://bugs.kde.org/show_bug.cgi?id=413368 Tomas Trnka changed: What|Removed |Added CC||tomastr...@gmx.com --- Comment #13 from Tomas Trnka --- I have just hit this after updating to 5.17.4 (Fedora 31), after not having used Plasma for at least a year. Manually running "krunnerglobalshortcuts" fixed it (if it helps, I can attach both versions of "kglobalshortcutsrc" before and after running the fix). -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 414672] Crash in uninitialized transform tool
https://bugs.kde.org/show_bug.cgi?id=414672 --- Comment #21 from Boudewijn Rempt --- Um... Now I can make the content of a layer -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 403750] cannot reorder columns in main window
https://bugs.kde.org/show_bug.cgi?id=403750 --- Comment #3 from Gandalf Lechner --- Many thanks for your continuing work on kbibtex in general and this bug/request in particular. It would be great to be able to reorder/resize columns to ones liking. As a non-coder, I have however problems to test this version. I suppose I somehow need to download some files and patch the code in order to check it, but am not familiar with doing this. I regularly do check out the master branch with an automated script, so once the edits end up there I can provide feedback. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 415625] Crash in transform tool
https://bugs.kde.org/show_bug.cgi?id=415625 Boudewijn Rempt changed: What|Removed |Added Ever confirmed|0 |1 Status|RESOLVED|REOPENED Resolution|FIXED |--- CC||b...@valdyas.org -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 414672] Crash in uninitialized transform tool
https://bugs.kde.org/show_bug.cgi?id=414672 --- Comment #22 from Boudewijn Rempt --- completely disappear by first painting, then clicking the transform tool, then the move tool: SAFE ASSERT (krita): "!m_strokeEnded || m_isCancelled" in file /home/boud/dev/krita/libs/image/kis_stroke.cpp, line 84 SAFE ASSERT (krita): "!m_strokeEnded || m_isCancelled" in file /home/boud/dev/krita/libs/image/kis_stroke.cpp, line 84 SAFE ASSERT (krita): "!m_strokeEnded || m_isCancelled" in file /home/boud/dev/krita/libs/image/kis_stroke.cpp, line 84 There's still something extremely fishy going on, and my commit making a safe assert on this line very probably is wrong. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407405] Pixel paint, Line Tool and Grid with 1px offset!
https://bugs.kde.org/show_bug.cgi?id=407405 Boudewijn Rempt changed: What|Removed |Added Latest Commit|https://invent.kde.org/kde/ |https://invent.kde.org/kde/ |krita/commit/b434751233e91d |krita/commit/9a972eea695263 |229617952bb73ca0744353bd10 |11cd95dd45335d2f1ba7d24fc3 --- Comment #5 from Boudewijn Rempt --- Git commit 9a972eea69526311cd95dd45335d2f1ba7d24fc3 by Boudewijn Rempt, on behalf of Ivan Yossi. Committed on 08/01/2020 at 14:18. Pushed by rempt into branch 'krita/4.2'. Fix 1px brush offset in line tool This adjust the diferent position of KisPaintInformation from a line to be inside a line between starting and ending points. This is particularly important as brushes that use 1px perfect pixels require the line to be perfect in order to avoid looking jagged. In 1px size with sharpen active we only use the start and end KisPaintInformation points. This patch also adjusts the outine on 1px brushes to adjust to the grid to better preview where the paint is going to be applyied (cherry picked from commit b434751233e91d229617952bb73ca0744353bd10) M +2-2libs/image/brushengine/kis_paintop.cc M +10 -2libs/image/kis_painter.cc M +4-1plugins/paintops/libpaintop/kis_brush_based_paintop_settings.cpp M +21 -2plugins/paintops/libpaintop/kis_current_outline_fetcher.cpp M +2-1plugins/paintops/libpaintop/kis_current_outline_fetcher.h M +72 -0plugins/tools/basictools/kis_tool_line_helper.cpp M +3-0plugins/tools/basictools/kis_tool_line_helper.h https://invent.kde.org/kde/krita/commit/9a972eea69526311cd95dd45335d2f1ba7d24fc3 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 406595] Layer filter's opener menu is too narrow on Layer dock.
https://bugs.kde.org/show_bug.cgi?id=406595 Boudewijn Rempt changed: What|Removed |Added Latest Commit|https://invent.kde.org/kde/ |https://invent.kde.org/kde/ |krita/commit/818c841b0b20fc |krita/commit/6ce046bd3aa297 |6d56e6365fcd57a620a6d98303 |6686a5e95264774e3c4f3a91d1 --- Comment #8 from Boudewijn Rempt --- Git commit 6ce046bd3aa2976686a5e95264774e3c4f3a91d1 by Boudewijn Rempt, on behalf of Kai Uwe Broulik. Committed on 08/01/2020 at 14:19. Pushed by rempt into branch 'krita/4.2'. [KisColorFilterCombo] Force ComboBox popup Only in this mode will Qt respect the contents of the ComboBox popup. This is what Fusion uses. Differential Revision: https://phabricator.kde.org/D25739 (cherry picked from commit 818c841b0b20fc6d56e6365fcd57a620a6d98303) M +23 -0libs/ui/widgets/kis_color_filter_combo.cpp https://invent.kde.org/kde/krita/commit/6ce046bd3aa2976686a5e95264774e3c4f3a91d1 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 414672] Crash in uninitialized transform tool
https://bugs.kde.org/show_bug.cgi?id=414672 --- Comment #23 from Tymond --- Note: there are also bug 402770 and bug 408057 that might be responsible for that. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 415621] epoll_ctl reports for uninitialized padding
https://bugs.kde.org/show_bug.cgi?id=415621 zbys...@in.waw.pl changed: What|Removed |Added CC||zbys...@in.waw.pl -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 416003] New: Scrollbar width in Breeze theme
https://bugs.kde.org/show_bug.cgi?id=416003 Bug ID: 416003 Summary: Scrollbar width in Breeze theme Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: igor.ljubun...@canonical.com Target Milestone: --- Plasma Breeze theme does not have any field in the Settings/UI to customize the width of scrollbars. On small-size, high-resolution screens, scrollbars can be too small to select, especially on non-maximized windows. This can also be considered an accessibility feature. STEPS TO REPRODUCE 1. Launch Plasma desktop. 2. Open Settings > Appearance. 3. No available setting to change scrollbar width. OBSERVED RESULT Scrollbars have a set size and cannot be customized without extensive changes to the underlying code. EXPECTED RESULT There should be a simple UI feature that allows the user to change the width of the scrollbars to match their resolution, usage patters and accessibility needs. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 416002] 1 installation transactions failed There was a problem during the installation: mariadb-extra(x86-64) < 10.3.20-1.mga7 conflicts with mariadb-10.3.20-1.mga7.x86_64
https://bugs.kde.org/show_bug.cgi?id=416002 Nate Graham changed: What|Removed |Added Resolution|--- |DOWNSTREAM CC||n...@kde.org Status|REPORTED|RESOLVED --- Comment #1 from Nate Graham --- This is an issue with your distro's packaging, not Spectacle itself. Please report it to your distro's packagers. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 415984] Kickoff uses dialogs/background.svgz instead of dialogs/kickoff.svgz
https://bugs.kde.org/show_bug.cgi?id=415984 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 414890] Palette Docker does not show swatches 9 Version: 4.3.0-prealpha (git 818c841)
https://bugs.kde.org/show_bug.cgi?id=414890 Boudewijn Rempt changed: What|Removed |Added Latest Commit|https://invent.kde.org/kde/ |https://invent.kde.org/kde/ |krita/commit/1a76a971ae4677 |krita/commit/41dc9a84380354 |ab984e3fd0111db26a442794f0 |00983243fbc19d0290f3d06004 --- Comment #4 from Boudewijn Rempt --- Git commit 41dc9a8438035400983243fbc19d0290f3d06004 by Boudewijn Rempt, on behalf of Ivan Yossi. Committed on 08/01/2020 at 15:32. Pushed by rempt into branch 'krita/4.2'. Fix PaletteDocker not showing palettes Reverts 97c03e0f3314dae5520deb901dda73d1cf8df201 "-1" is a QMap key to signal "root group" Changed Q_ASSERT to KIS_ASSERT_RECOVER_RETURN_VALUE to try and avoid crashing if Qt is compiled in debug mode. M +0-3libs/widgets/KisPaletteModel.cpp https://invent.kde.org/kde/krita/commit/41dc9a8438035400983243fbc19d0290f3d06004 -- You are receiving this mail because: You are watching all bug changes.
