[systemsettings] [Bug 422895] [Wayland] Systemsettings crash
https://bugs.kde.org/show_bug.cgi?id=422895 --- Comment #2 from Tony --- Created attachment 129656 --> https://bugs.kde.org/attachment.cgi?id=129656=edit terminal log for systemsettings5 Sadly i can't reproduced the crash anymore, may be it was related to some other issue i had over the past weekend, i end up deleting ~/.cache and those as well as this one don't happen anymore. The attatchement it may not be of any help now although I do find wierd this line keeps repeating in it : dri_create_context: requested glthread but driver is missing backgroundCallable V2 extension -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 419351] Feature: Save/restore invert-effect per window
https://bugs.kde.org/show_bug.cgi?id=419351 Kishore Gopalakrishnan changed: What|Removed |Added CC||kishor...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 308331] Close window (or other) shortcut to be effective from window switcher view
https://bugs.kde.org/show_bug.cgi?id=308331 --- Comment #9 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/115 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 422429] Guides are always drag while editing
https://bugs.kde.org/show_bug.cgi?id=422429 --- Comment #9 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 421742] Give Shadow to Tab Window Switcher
https://bugs.kde.org/show_bug.cgi?id=421742 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 423404] Bug - Inconsistent input
https://bugs.kde.org/show_bug.cgi?id=423404 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #4 from Bug Janitor Service --- Thanks for your comment! Automatically switching the status of this bug to REPORTED so that the KDE team knows that the bug is ready to get confirmed. In the future you may also do this yourself when providing needed information. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 423461] Add PAR (Pixel Aspect Ratio) view option for images with non-square pixel.
https://bugs.kde.org/show_bug.cgi?id=423461 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #6 from Bug Janitor Service --- Thanks for your comment! Automatically switching the status of this bug to REPORTED so that the KDE team knows that the bug is ready to get confirmed. In the future you may also do this yourself when providing needed information. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 422067] Program stops responding when importing Quicken data
https://bugs.kde.org/show_bug.cgi?id=422067 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #6 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 422096] Right-click often performs the first action in the context menu on high-DPI displays
https://bugs.kde.org/show_bug.cgi?id=422096 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 423472] New: add a feature that tasks can keep bouncing when tasks need a attention
https://bugs.kde.org/show_bug.cgi?id=423472 Bug ID: 423472 Summary: add a feature that tasks can keep bouncing when tasks need a attention Product: lattedock Version: 0.9.11 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: gbcbook...@gmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. tasks bouncing time too short 2. too easy to miss attention especially for important message(IM APP) 3. provide a way to config tasks bouncing time OBSERVED RESULT latte dock tasks bouncing only persist few seconds, it's easy to miss attention, EXPECTED RESULT please provide a option to change how long bouncing effect can be play SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: archlinux (available in About System) KDE Plasma Version: 5.19-1 KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION NONE -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 421048] Input from /dev/null rejected
https://bugs.kde.org/show_bug.cgi?id=421048 michael changed: What|Removed |Added CC||solot...@gmail.com --- Comment #3 from michael --- *** Bug 419950 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 419950] a lot of windows opening when empty files are present
https://bugs.kde.org/show_bug.cgi?id=419950 michael changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED Version Fixed In||1.8.3 --- Comment #1 from michael --- This issue has been addressed in 1.8.3. *** This bug has been marked as a duplicate of bug 421048 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423471] New: Plasma crash after running plasmashell --replace
https://bugs.kde.org/show_bug.cgi?id=423471 Bug ID: 423471 Summary: Plasma crash after running plasmashell --replace Product: plasmashell Version: master Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: jodr...@live.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.19.80) Qt Version: 5.15.0 Frameworks Version: 5.72.0 Operating System: Linux 5.7.2-1-default x86_64 Windowing system: X11 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: Installed some updates, ran plasmashell --replace from krunner. The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault [KCrash Handler] #4 0x7f6c0aea8ce0 in QQmlRefPointer::QQmlRefPointer(QQmlRefPointer const&) (other=..., this=0x7f6bfede5a60) at /usr/src/debug/libqt5-qtdeclarative-5.15.0-ku.1.1.x86_64/include/QtQml/5.15.0/QtQml/private/../../../../../src/qml/qml/ftw/qqmlrefcount_p.h:152 #5 0x7f6c0aea8ce0 in QQmlType::QQmlType(QQmlType const&) (this=0x7f6bfede5a60) at /usr/src/debug/libqt5-qtdeclarative-5.15.0-ku.1.1.x86_64/include/QtQml/5.15.0/QtQml/private/../../../../../src/qml/qml/qqmltype_p.h:79 #6 0x7f6c0af20de3 in QQmlPropertyCacheCreator::propertyCacheForObject(QmlIR::Object const*, QQmlBindingInstantiationContext const&, QQmlError*) const (this=this@entry=0x7f6bfede5de0, obj=obj@entry=0x7f6bf06de820, context=..., error=error@entry=0x7f6bfede5af8) at /usr/include/qt5/QtCore/qstring.h:1065 #7 0x7f6c0af24044 in QQmlPropertyCacheCreator::buildMetaObjectRecursively(int, QQmlBindingInstantiationContext const&, QQmlPropertyCacheCreator::VMEMetaObjectIsRequired) (this=this@entry=0x7f6bfede5de0, objectIndex=3, context=..., isVMERequired=isVMERequired@entry=QQmlPropertyCacheCreator::VMEMetaObjectIsRequired::Maybe) at /usr/src/debug/libqt5-qtdeclarative-5.15.0-ku.1.1.x86_64/include/QtQml/5.15.0/QtQml/private/../../../../../src/qml/qml/ftw/qqmlrefcount_p.h:138 #8 0x7f6c0af24454 in QQmlPropertyCacheCreator::buildMetaObjectRecursively(int, QQmlBindingInstantiationContext const&, QQmlPropertyCacheCreator::VMEMetaObjectIsRequired) (this=this@entry=0x7f6bfede5de0, objectIndex=objectIndex@entry=0, context=..., isVMERequired=isVMERequired@entry=QQmlPropertyCacheCreator::VMEMetaObjectIsRequired::Maybe) at /usr/include/c++/9/bits/atomic_base.h:326 #9 0x7f6c0af24d91 in QQmlPropertyCacheCreator::buildMetaObjects() (this=this@entry=0x7f6bfede5de0) at /usr/include/c++/9/bits/stl_iterator.h:806 #10 0x7f6c0af1f7aa in QQmlTypeCompiler::compile() (this=this@entry=0x7f6bfede5f40) at /usr/src/debug/libqt5-qtdeclarative-5.15.0-ku.1.1.x86_64/src/qml/qml/qqmltypecompiler.cpp:85 #11 0x7f6c0ae5abe7 in QQmlTypeData::compile(QQmlRefPointer const&, QV4::ResolvedTypeReferenceMap*, std::function const&) (this=this@entry=0x7f6bf06e0c40, typeNameCache=..., resolvedTypeCache=resolvedTypeCache@entry=0x7f6bfede6030, dependencyHasher=...) at /usr/src/debug/libqt5-qtdeclarative-5.15.0-ku.1.1.x86_64/src/qml/qml/qqmltypedata.cpp:776 #12 0x7f6c0ae61247 in QQmlTypeData::done() (this=) at /usr/include/c++/9/bits/std_function.h:87 #13 0x7f6c0ae4ac45 in QQmlDataBlob::tryDone() (this=0x7f6bf06e0c40) at /usr/src/debug/libqt5-qtdeclarative-5.15.0-ku.1.1.x86_64/include/QtQml/5.15.0/QtQml/private/../../../../../src/qml/qml/ftw/qqmlrefcount_p.h:116 #14 0x7f6c0ae4ac45 in QQmlDataBlob::tryDone() (this=0x7f6bf06e0c40) at /usr/src/debug/libqt5-qtdeclarative-5.15.0-ku.1.1.x86_64/src/qml/qml/qqmldatablob.cpp:509 #15 0x7f6c0aeb61c3 in QQmlTypeLoader::setData(QQmlDataBlob*, QQmlDataBlob::SourceCodeData const&) (this=this@entry=0x55c91827e7f8, blob=blob@entry=0x7f6bf06e0c40, d=...) at /usr/src/debug/libqt5-qtdeclarative-5.15.0-ku.1.1.x86_64/src/qml/qml/qqmltypeloader.cpp:457 #16 0x7f6c0aeb6524 in QQmlTypeLoader::setData(QQmlDataBlob*, QString const&) (this=this@entry=0x55c91827e7f8, blob=blob@entry=0x7f6bf06e0c40, fileName=...) at /usr/src/debug/libqt5-qtdeclarative-5.15.0-ku.1.1.x86_64/src/qml/qml/qqmltypeloader.cpp:437 #17 0x7f6c0aeb6b10 in QQmlTypeLoader::loadThread(QQmlDataBlob*) (this=this@entry=0x55c91827e7f8, blob=blob@entry=0x7f6bf06e0c40) at /usr/src/debug/libqt5-qtdeclarative-5.15.0-ku.1.1.x86_64/src/qml/qml/qqmltypeloader.cpp:299 #18 0x7f6c0aebcfcc in PlainLoader::loadThread(QQmlTypeLoader*, QQmlDataBlob*) const (this=0x7f6bfede6297, blob=0x7f6bf06e0c40, loader=0x55c91827e7f8) at /usr/src/debug/libqt5-qtdeclarative-5.15.0-ku.1.1.x86_64/src/qml/qml/qqmltypeloader.cpp:146 #19 0x7f6c0aebcfcc in QQmlTypeLoader::doLoad(PlainLoader const&, QQmlDataBlob*, QQmlTypeLoader::Mode) (this=this@entry=0x55c91827e7f8, loader=...,
[kdeconnect] [Bug 422981] Windows version breaks Discord/SteamVR and possibly more unidentified programs
https://bugs.kde.org/show_bug.cgi?id=422981 m.house...@gmail.com changed: What|Removed |Added CC||m.house...@gmail.com --- Comment #1 from m.house...@gmail.com --- Same issue here, though not quite as extreme (I don't use SteamVR). The issue only happens with discord for me, and it isn't instant. After about 5-10 minutes being in a voice call, discord will crash. Definitely caused by kdeconnect, because uninstalling it fixes the issue. I'm on archlinux 5.7.5, using kdeconnect 1.4.0. I'd be happy to provide any other information needed to help resolve this bug. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 423470] New: Crash when try to use Fill Tool
https://bugs.kde.org/show_bug.cgi?id=423470 Bug ID: 423470 Summary: Crash when try to use Fill Tool Product: krita Version: nightly build (please specify the git hash!) Platform: MS Windows OS: All Status: REPORTED Severity: normal Priority: NOR Component: Tools Assignee: krita-bugs-n...@kde.org Reporter: acc4commissi...@gmail.com Target Milestone: --- SUMMARY git e0b6c5a STEPS TO REPRODUCE 1. Select Fill Tool 2. Click the canvas 3. Crash It doesn't crash when the 'fast mode' in Tool Settings is checked SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Error occurred on Thursday, June 25, 2020 at 11:04:32. krita.exe caused an Access Violation at location 07FEE331B1C0 in module libkritaimage.dll Reading from location 0018. AddrPC Params 07FEE331B1C0 451A0D50 07FEFF1213D2 0002 libkritaimage.dll!0x1cb1c0 KisSelection::pixelSelection+0x0 07FEE32392A1 0001 05BCFB38 36252B40 libkritaimage.dll!0xe92a1 KisFillPainter::genericFillStart+0x31 07FEE3239621 05BCFC30 07FEE567D758 001A libkritaimage.dll!0xe9621 KisFillPainter::fillColor+0xe1 07FEE1C7BD7D 0006 0010 libkritaui.dll!0x2bbd7d FillProcessingVisitor::fillPaintDevice+0x2ad 07FEE1C7C654 550A89B0 550A89B0 3D59EFE0 libkritaui.dll!0x2bc654 FillProcessingVisitor::visitNodeWithPaintDevice+0x54 07FEE31BA003 libkritaimage.dll!0x6a003 KisProcessingCommand::redo+0x23 07FEE326E806 0001 5514EAA0 360DCC70 libkritaimage.dll!0x11e806 KisStrokeStrategyUndoCommandBased::doStrokeCallback+0x76 07FEE3444D74 0010 362521A0 4519CE80 libkritaimage.dll!0x2f4d74 KisUpdateJobItem::run+0x94 07FEE54A8610 5514EAA0 4519CE00 Qt5Core.dll!0x28610 QThreadPool::tryStart+0x520 07FEE54A162F Qt5Core.dll!0x2162f QThread::qt_metacall+0x69f 7778556D kernel32.dll!0x1556d BaseThreadInitThunk+0xd 778E372D ntdll.dll!0x5372d RtlUserThreadStart+0x1d 00014000-000140F72000 krita.exe 7789-77A2F000 ntdll.dll 6.1.7601.24545 07FEF343-07FEF3443000 aswhook.dll 20.4.5312.0 -7788F000 kernel32.dll 6.1.7601.24545 07FEFD41-07FEFD477000 KERNELBASE.dll6.1.7601.24545 07FEF6AE-07FEF6B2C000 libkritaglobal.dll 07FEFAE3-07FEFAE3E000 libkritaversion.dll 6144-6145A000 libgcc_s_seh-1.dll 07FEFF12-07FEFF1BF000 msvcrt.dll7.0.7601.17744 6494-64955000 libwinpthread-1.dll 1.0.0.0 6FC4-6FDA5000 libstdc++-6.dll 7767-7776A000 USER32.dll6.1.7601.24546 07FEFE21-07FEFE277000 GDI32.dll 6.1.7601.24540 07FEFD89-07FEFD89E000 LPK.dll 6.1.7601.24537 07FEFF1C-07FEFF28B000 USP10.dll 1.626.7601.24535 07FEE548-07FEE5AAD000 Qt5Core.dll 5.12.8.0 07FEFD8A-07FEFD97B000 ADVAPI32.dll 6.1.7601.24545 07FEFFB6-07FEFFB7F000 sechost.dll 6.1.7601.18869 07FEFDE4-07FEFDF6C000 RPCRT4.dll6.1.7601.24545 07FEF641-07FEF6428000 MPR.dll 6.1.7600.16385 07FEFB28-07FEFB296000 NETAPI32.dll 6.1.7601.17887 07FEFB22-07FEFB22C000 netutils.dll 6.1.7601.17514 07FEFCE7-07FEFCE93000 srvcli.dll6.1.7601.17514 07FEFB19-07FEFB1A5000 wkscli.dll6.1.7601.17514 07FEFE01-07FEFE20F000 ole32.dll 6.1.7601.24537 07FEFE28-07FEFF00B000 SHELL32.dll 6.1.7601.24468 07FEFD7A-07FEFD811000 SHLWAPI.dll 6.1.7601.17514 07FEFD5B-07FEFD5CF000 USERENV.dll 6.1.7601.24535 07FEFD3E-07FEFD3EF000 profapi.dll 6.1.7600.16385 07FEFC47-07FEFC47C000 VERSION.dll 6.1.7600.16385 07FEFB2C-07FEFB2FB000 WINMM.dll 6.1.7600.16385 07FEFD84-07FEFD88D000 WS2_32.dll6.1.7601.23451 07FEFF29-07FEFF298000 NSI.dll 6.1.7601.23889 07FEF6A8-07FEF6AD7000 libKF5I18n.dll 07FEFAA2-07FEFAA3E000 libintl.DLL 0.18.0.0 07FEFAA0-07FEFAA12000 iconv.dll 07FEE4E6-07FEE547D000 Qt5Gui.dll5.12.8.0 07FEE36C-07FEE3C2D000 Qt5Widgets.dll5.12.8.0 07FEFC45-07FEFC468000 dwmapi.dll6.1.7601.18917 07FEFBD7-07FEFBDC6000 UxTheme.dll 6.1.7600.16385
[krita] [Bug 418071] Moving layers that has any area made with select>fill is slow to move with move tool
https://bugs.kde.org/show_bug.cgi?id=418071 --- Comment #4 from acc4commissi...@gmail.com --- This still happens in 4.3.0, but not in the nightly stable builds. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 423469] New: suggest. kate can change and use background use image. on option.
https://bugs.kde.org/show_bug.cgi?id=423469 Bug ID: 423469 Summary: suggest. kate can change and use background use image. on option. Product: kate Version: 19.12.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: gyrlg...@protonmail.com Target Milestone: --- hi, sorry strange english. suggested. kate is no background. kate can change background for only 1 color. If kate is can use gradation color or wallpaper. that great and beautiful view for text editor option. if you think > why use wallpaper for text editor? or > i think it's difficult see text. but please stop negation, you can see. ATOM = text editor, but yes can many editing file. so that IDE. atom need install package for change background image. but can change. or you can see pycharm = python editor. yes python IDE. that have option for change wallcolor and wallpaper. you can see settings > appearance & Behavior > Appearance > UI Options > Background Image. you can change background use imade. and opacity. or you know focus editor? that have'nt many editting option. but you can change documents editor ui! so background image, image opacity, image blur for text edit frame. text color, text style, text line spacing.. that many option. it's a beautiful and can raise for motivation. yes, but i know this feeling > no! that idea it's difficult text edit!! so because i suggested option like. you can change use background image or plane color only. that is gently method. sorry i no commit patch. i don't know programing for C## and QT. i can only tell for this idea. i try build kate on kubuntu 18.04, 19.04, but all faild. i don't know why dosen't build kate. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 423468] New: System setting crashed
https://bugs.kde.org/show_bug.cgi?id=423468 Bug ID: 423468 Summary: System setting crashed Product: systemsettings Version: 5.18.5 Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: qyg...@163.com Target Milestone: --- Application: systemsettings5 (5.18.5) (Compiled from sources) Qt Version: 5.15.0 Frameworks Version: 5.70.0 Operating System: Linux 5.7.0-3-MANJARO x86_64 Windowing system: X11 Distribution: Manjaro Linux -- Information about the crash: When I tried to Click "application style" and select application style, the system settings crashed. I think this is probably because I used some themes that I downloaded from the KDE store. My plasma is 5.18.5. The crash can be reproduced every time. -- Backtrace: Application: 系统设置 (systemsettings5), signal: Aborted Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7efd8b653300 (LWP 2572))] Thread 14 (Thread 0x7efd48494700 (LWP 2588)): #0 0x7efd8dd1c4c2 in () at /usr/lib/libglib-2.0.so.0 #1 0x7efd8dd1eeab in g_main_context_prepare () at /usr/lib/libglib-2.0.so.0 #2 0x7efd8dd6de56 in () at /usr/lib/libglib-2.0.so.0 #3 0x7efd8dd1f221 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #4 0x7efd900a522c in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7efd9004b01c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7efd8fe66c32 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #7 0x7efd8f155789 in () at /usr/lib/libQt5Qml.so.5 #8 0x7efd8fe67e0f in () at /usr/lib/libQt5Core.so.5 #9 0x7efd8e77a422 in start_thread () at /usr/lib/libpthread.so.0 #10 0x7efd8faf5bf3 in clone () at /usr/lib/libc.so.6 Thread 13 (Thread 0x7efd535ef700 (LWP 2585)): #0 0x7efd8dd68030 in g_mutex_unlock () at /usr/lib/libglib-2.0.so.0 #1 0x7efd8dd6df2d in () at /usr/lib/libglib-2.0.so.0 #2 0x7efd8dd1f221 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7efd900a522c in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7efd9004b01c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7efd8fe66c32 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7efd8f155789 in () at /usr/lib/libQt5Qml.so.5 #7 0x7efd8fe67e0f in () at /usr/lib/libQt5Core.so.5 #8 0x7efd8e77a422 in start_thread () at /usr/lib/libpthread.so.0 #9 0x7efd8faf5bf3 in clone () at /usr/lib/libc.so.6 Thread 12 (Thread 0x7efd6d720700 (LWP 2584)): #0 0x7efd8fae6aec in read () at /usr/lib/libc.so.6 #1 0x7efd8dd1df2d in g_main_context_check () at /usr/lib/libglib-2.0.so.0 #2 0x7efd8dd6dedb in () at /usr/lib/libglib-2.0.so.0 #3 0x7efd8dd1f221 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #4 0x7efd900a522c in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7efd9004b01c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7efd8fe66c32 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #7 0x7efd8f155789 in () at /usr/lib/libQt5Qml.so.5 #8 0x7efd8fe67e0f in () at /usr/lib/libQt5Core.so.5 #9 0x7efd8e77a422 in start_thread () at /usr/lib/libpthread.so.0 #10 0x7efd8faf5bf3 in clone () at /usr/lib/libc.so.6 Thread 11 (Thread 0x7efd6e18f700 (LWP 2583)): #0 0x7efd8e781158 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7efd8fe6dce8 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7efd8fe6bfd4 in () at /usr/lib/libQt5Core.so.5 #3 0x7efd8fe67e0f in () at /usr/lib/libQt5Core.so.5 #4 0x7efd8e77a422 in start_thread () at /usr/lib/libpthread.so.0 #5 0x7efd8faf5bf3 in clone () at /usr/lib/libc.so.6 Thread 10 (Thread 0x7efd6e990700 (LWP 2582)): #0 0x7efd8e781158 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7efd8fe6dce8 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7efd8fe6bfd4 in () at /usr/lib/libQt5Core.so.5 #3 0x7efd8fe67e0f in () at /usr/lib/libQt5Core.so.5 #4 0x7efd8e77a422 in start_thread () at /usr/lib/libpthread.so.0 #5 0x7efd8faf5bf3 in clone () at /usr/lib/libc.so.6 Thread 9 (Thread 0x7efd6f191700 (LWP 2581)): #0 0x7efd8e781158 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7efd8fe6dce8 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7efd8fe6bfd4 in () at /usr/lib/libQt5Core.so.5 #3 0x7efd8fe67e0f in () at /usr/lib/libQt5Core.so.5 #4 0x7efd8e77a422 in start_thread () at /usr/lib/libpthread.so.0 #5 0x7efd8faf5bf3 in clone ()
[krita] [Bug 419140] Crash on exit with the new Resources branch
https://bugs.kde.org/show_bug.cgi?id=419140 --- Comment #5 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/graphics/krita/-/merge_requests/396 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 423467] New: dolphin is difficult grasp to many open tab.
https://bugs.kde.org/show_bug.cgi?id=423467 Bug ID: 423467 Summary: dolphin is difficult grasp to many open tab. Product: dolphin Version: 19.12.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: gyrlg...@protonmail.com CC: kfm-de...@kde.org Target Milestone: --- hi, sorry strange english. suggested. dolphin is difficult grasp to many open tab. because that open tab all wide 1 column. like libre office calc style. side to side. you can push <> change open tab. but..that is need action. so 1 push, you can change open neighbor tab. if you many open tab. example 20, yes it's many many open. but please try this. you may think that. hey, i tired to push <>. 1. all open but side full. tab view row change. exsample. exsample ABCDEFGH = open tab title. A|B|C|D|E|F|G|... A|B|C|D| = 1row E|F|G|H|...= 2row yes that probrem. dolphin have many height on tab list. but that is a clearlty view to all tab. 2. panel change. like kate text editor documents tree view. if you don't know that kate text editor documents tree view. kate > settings > Application > plugins > Document Tree View check on. that it. you can see all open document list on kate side bar on documents tab. exsample. exsample ABCDEFGH = open tab title. A| main folder or file view | B| main folder or file view | C| main folder or file view | D| main folder or file view | E| main folder or file view | F| main folder or file view | G| main folder or file view | ok that probrem. dolphin have many side width. but if you use sidebar infobar, or places. this can dock panel for other panel. sorry i no commit patch. i don't know programing for C## and QT. i can only tell for this idea. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 419140] Crash on exit with the new Resources branch
https://bugs.kde.org/show_bug.cgi?id=419140 L. E. Segovia changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #4 from L. E. Segovia --- I was playing today with Krita, and I managed to trace this to an use-after-free condition in the resource server. The only place that observes it is the palette docker. In Windows, the main window is destroyed before the resource server, bringing the docker down with her; see below for the stacktrace of PaletteDockerDock::~PaletteDockerDock. The dock doesn't remove itself from the observer, unlike every other widget that uses this functionality. Thus, when the server is destroyed, it attempts to dereference a long dead object. I wonder why this happens only with debuggable builds, though? #0 PaletteDockerDock::~PaletteDockerDock (this=0x2215dd60, __in_chrg=) at C:\krita-win\src\plugins\dockers\palettedocker\palettedocker_dock.cpp:148 #1 0x7ffad6bb592d in PaletteDockerDock::~PaletteDockerDock (this=0x2215dd60, __in_chrg=) at C:\krita-win\src\plugins\dockers\palettedocker\palettedocker_dock.cpp:150 #2 0x7ffb47996867 in QObjectPrivate::deleteChildren() () from C:\krita-win\i_deps\bin\Qt5Core.dll #3 0x7ffb47e312c3 in QWidget::~QWidget() () from C:\krita-win\i_deps\bin\Qt5Widgets.dll #4 0x7ffb42606fda in KMainWindow::~KMainWindow (this=0x1fb6b530, __in_chrg=) at C:\krita-win\src\libs\widgetutils\xmlgui\kmainwindow.cpp:349 #5 0x7ffb18519685 in KisMainWindow::~KisMainWindow (this=0x1fb6b530, __in_chrg=, __vtt_parm=) at C:\krita-win\src\libs\ui\KisMainWindow.cpp:582 #6 0x7ffb185196fd in KisMainWindow::~KisMainWindow (this=0x1fb6b530, __in_chrg=, __vtt_parm=) at C:\krita-win\src\libs\ui\KisMainWindow.cpp:610 #7 0x7ffb47999a1a in QObject::event(QEvent*) () from C:\krita-win\i_deps\bin\Qt5Core.dll #8 0x7ffb47e3612c in QWidget::event(QEvent*) () from C:\krita-win\i_deps\bin\Qt5Widgets.dll #9 0x7ffb47f251eb in QMainWindow::event(QEvent*) () from C:\krita-win\i_deps\bin\Qt5Widgets.dll #10 0x7ffb42608eec in KMainWindow::event (this=0x1fb6b530, ev=0x182f2960) at C:\krita-win\src\libs\widgetutils\xmlgui\kmainwindow.cpp:765 #11 0x7ffb47df7bdc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from C:\krita-win\i_deps\bin\Qt5Widgets.dll #12 0x7ffb47dfec23 in QApplication::notify(QObject*, QEvent*) () from C:\krita-win\i_deps\bin\Qt5Widgets.dll #13 0x7ffb184f1e46 in KisApplication::notify (this=, receiver=0x1fb6b530, event=0x182f2960) at C:\krita-win\src\libs\ui\KisApplication.cpp:688 #14 0x7ffb4796d0d8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from C:\krita-win\i_deps\bin\Qt5Core.dll #15 0x7ffb47973709 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from C:\krita-win\i_deps\bin\Qt5Core.dll #16 0x6a8fe90e in qwindows!qt_plugin_instance () from C:\krita-win\i_deps\plugins\platforms\qwindows.dll #17 0x7ffb479c814a in QEventDispatcherWin32Private::sendTimerEvent(int) () from C:\krita-win\i_deps\bin\Qt5Core.dll #18 0x7ffb9cc85c0d in USER32!CallWindowProcW () from C:\WINDOWS\System32\user32.dll #19 0x7ffb9cc85602 in USER32!DispatchMessageW () from C:\WINDOWS\System32\user32.dll #20 0x7ffb479c75eb in QEventDispatcherWin32::processEvents(QFlags) () from C:\krita-win\i_deps\bin\Qt5Core.dll #21 0x6a8fe8f5 in qwindows!qt_plugin_instance () from C:\krita-win\i_deps\plugins\platforms\qwindows.dll #22 0x7ffb4796b8ff in QEventLoop::exec(QFlags) () from C:\krita-win\i_deps\bin\Qt5Core.dll #23 0x7ffb47974b77 in QCoreApplication::exec() () from C:\krita-win\i_deps\bin\Qt5Core.dll #24 0x000140006e90 in main (argc=, argv=0x2946c70) at C:\krita-win\src\krita\main.cc:594 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 417354] Telegram's icon invisble when using software plasma renderer
https://bugs.kde.org/show_bug.cgi?id=417354 --- Comment #4 from Daniel Felipe --- (In reply to Daniel Felipe from comment #3) > can confirm it still happens even when it was supposedly fixed in Plasma > 5.19, it seems this change > https://github.com/KDE/plasma-desktop/commit/ > 7b0fa84045aff156ffc82e434ea6c58a5e15afe6 has had no effect on my machine after applying these changes to the QML files manually the issue is fixed, this issue can be closed now -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423466] New: Journal and filled with TypeErrors
https://bugs.kde.org/show_bug.cgi?id=423466 Bug ID: 423466 Summary: Journal and filled with TypeErrors Product: plasmashell Version: 5.19.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: dcostr...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY Noticed when I opened KSystemLog that it was getting an error on loop. Checked journal and it's filled with error message "file:///home/derek/.local/share/plasma/plasmoids/org.kde.networkMonitor/contents/ui/HistoryGraph.qml:41: TypeError: Cannot read property 'height' of null" STEPS TO REPRODUCE 1. view journal or open KSystemLog SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch KDE Plasma Version: 5.19.2 KDE Frameworks Version: 5.71.0 Qt Version: 5.15.0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 423325] Modifier-only Meta key shortcut for opening Kickoff breaks a lot
https://bugs.kde.org/show_bug.cgi?id=423325 Nate Graham changed: What|Removed |Added Ever confirmed|0 |1 Assignee|k...@davidedmundson.co.uk|kwin-bugs-n...@kde.org Product|plasmashell |kwin Status|RESOLVED|REOPENED Version|5.19.0 |5.19.2 Component|general |general Target Milestone|1.0 |--- Resolution|WORKSFORME |--- --- Comment #3 from Nate Graham --- I just helped a user troubleshoot this on Plasma 5.19.2. She was experiencing this issue her kwinrc file did not have a [ModifierOnlyShortcuts] entry. The Meta key shortcut did not work to launch Kickoff. It started working after I advised her to add the following to the file: [ModifierOnlyShortcuts] Meta=org.kde.plasmashell,/PlasmaShell,org.kde.PlasmaShell,activateLauncherMenu In options.cpp, this is the value that gets assigned to Meta by default if there is nothing set in the config file. Seems like that's not working, or the code that calls is isn't getting run somehow? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 423465] New: Wrong rendering when using "Destination Atop" blending mode
https://bugs.kde.org/show_bug.cgi?id=423465 Bug ID: 423465 Summary: Wrong rendering when using "Destination Atop" blending mode Product: krita Version: git master Platform: Compiled Sources OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: gin...@gmail.com Target Milestone: --- Created attachment 129655 --> https://bugs.kde.org/attachment.cgi?id=129655=edit test image The destination atop compositing op seems to mix the colors wrong with some artifacts in some cases. Attached is a test image file. STEPS TO REPRODUCE 1. Paint something in a transparent layer. 2. Paint something else a different color in another transparent layer on top of the previous, overlaping the two shapes. 3. Choose "Destination Atop" blending mode on the layer on top. OBSERVED RESULT Sample image: https://imgur.com/a/tcIngTC EXPECTED RESULT The artifacts shouldn't appear SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.70.0 Qt Version: 5.15.0 ADDITIONAL INFORMATION I looked at the code and think this could be fixed by modifying the file libs/pigment/compositeops/KoCompositeOpDestinationAtop.h Changing lines 61 and 62: channels_type srcMult= mul(src[channel], appliedAlpha); dst[channel] = lerp(srcMult,dst[channel],dstAlpha); by: dst[channel] = lerp(src[channel],dst[channel],dstAlpha); seems to solve the problem -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kdeclarative] [Bug 423080] Impossible to use tab as custom shortcut anymore
https://bugs.kde.org/show_bug.cgi?id=423080 calvin.f@gmail.com changed: What|Removed |Added CC||calvin.f@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423402] plasma-org.kde.plasma.desktop-appletsrc -wheel:Vertical org.kde.switchdesktop vs qt-5.15.0
https://bugs.kde.org/show_bug.cgi?id=423402 --- Comment #3 from Nate Graham --- If you'd like to investigate, check out https://invent.kde.org/plasma/plasma-workspace/-/blob/master/containmentactions/switchdesktop/desktop.cpp -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423402] plasma-org.kde.plasma.desktop-appletsrc -wheel:Vertical org.kde.switchdesktop vs qt-5.15.0
https://bugs.kde.org/show_bug.cgi?id=423402 --- Comment #2 from Henry Pfeil --- Not really a duplicate, but a request for info. Now it is not my problem. If it were, I'd be looking at Qt. Qt5-5.14 didn't bother me because KDE worked using Qt5-5.13.2, however now with the latest KDE upgrade, I can't even start KDE because it looks for Qt5.15 in libQt5Core. Previous KDE, I could launch it with Qt5-5.13.2, switch desktops using scrollwheel from the desktop, not the panel; then reboot with Qt5-5.15 no other changes, scrollwheel from desktop no worka dis. Only change was the Qt version. That suggests to me that the problem is not with KDE, not a bug, but a change in functionality of a Qt library. I wanted to know which KDE component the switchdesktop was in to find out the Qt libraries to which it links. Now that this is kicked over to a stalled bug, I'm relieved of that analysis. I'm a retired systems analyst, gotta go check my tee time. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 422116] Access to Power Management Settings causes crash
https://bugs.kde.org/show_bug.cgi?id=422116 David Edmundson changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED CC||k...@davidedmundson.co.uk --- Comment #1 from David Edmundson --- *** This bug has been marked as a duplicate of bug 422337 *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 422337] Crash in QQuickWindowPrivate::dirtyItem setting text colour
https://bugs.kde.org/show_bug.cgi?id=422337 David Edmundson changed: What|Removed |Added Summary|Second Display Monitor |Crash in ||QQuickWindowPrivate::dirtyI ||tem setting text colour CC||k...@davidedmundson.co.uk -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 422337] Crash in QQuickWindowPrivate::dirtyItem setting text colour
https://bugs.kde.org/show_bug.cgi?id=422337 David Edmundson changed: What|Removed |Added CC||Wolfgang.Thumser@T-Systems. ||com --- Comment #2 from David Edmundson --- *** Bug 417820 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 417820] systemsettings5 crashes when selecting compositor
https://bugs.kde.org/show_bug.cgi?id=417820 David Edmundson changed: What|Removed |Added Status|REPORTED|RESOLVED CC||k...@davidedmundson.co.uk Resolution|--- |DUPLICATE --- Comment #3 from David Edmundson --- *** This bug has been marked as a duplicate of bug 422337 *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 422337] Crash in QQuickWindowPrivate::dirtyItem setting text colour
https://bugs.kde.org/show_bug.cgi?id=422337 David Edmundson changed: What|Removed |Added CC||marc_fel...@yahoo.com --- Comment #1 from David Edmundson --- *** Bug 422116 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 418902] System Settings crashes when clicking on Startup and Shutdown to configure SDDM
https://bugs.kde.org/show_bug.cgi?id=418902 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk Product|systemsettings |frameworks-kirigami Target Milestone|--- |Not decided Assignee|plasma-b...@kde.org |notm...@gmail.com Component|general |general -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 391556] kcmshell5 craches
https://bugs.kde.org/show_bug.cgi?id=391556 David Edmundson changed: What|Removed |Added Resolution|--- |BACKTRACE CC||k...@davidedmundson.co.uk Status|REPORTED|RESOLVED --- Comment #1 from David Edmundson --- That trace unfortunately tells us nothing and this is quite old. Hopefully whatever issue there was has now been fixed -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 416005] Crash while adjusting monitor layout and refresh rate in kscreen
https://bugs.kde.org/show_bug.cgi?id=416005 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk --- Comment #6 from David Edmundson --- So from the trace const auto oldMode = output.ptr->currentMode(); is null, which seems plausible. If a screen is off or something it won't have a valid mode. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 423456] Unable to use external screen with KScreen in Wayland
https://bugs.kde.org/show_bug.cgi?id=423456 --- Comment #4 from Shawn Starr --- It should be noted this laptop has two GPUs: 1) Intel(R) HD Graphics 4600 (HSW GT2) 2) AMD Radeon HD 8950 (BONAIRE, DRM 3.37.0, 5.7.0-1.fc33.x86_64, LLVM 10.0.0) But I do not see the other GPU being detected at all. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 416005] Crash while adjusting monitor layout and refresh rate in kscreen
https://bugs.kde.org/show_bug.cgi?id=416005 David Edmundson changed: What|Removed |Added CC||todo.ciencia.y.electronica@ ||gmail.com --- Comment #5 from David Edmundson --- *** Bug 421805 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 421805] App crash. When changing from 40-60hz. monitor rate. (secondary screen) Kubuntu
https://bugs.kde.org/show_bug.cgi?id=421805 David Edmundson changed: What|Removed |Added Status|REPORTED|RESOLVED CC||k...@davidedmundson.co.uk Resolution|--- |DUPLICATE --- Comment #1 from David Edmundson --- *** This bug has been marked as a duplicate of bug 416005 *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 421261] system settings keeps crashing
https://bugs.kde.org/show_bug.cgi?id=421261 David Edmundson changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO CC||k...@davidedmundson.co.uk --- Comment #1 from David Edmundson --- Crash is in the opengl stack, but not in the usual place. Can you confirm your plasmashell still works correctly and normally? -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 423456] Unable to use external screen with KScreen in Wayland
https://bugs.kde.org/show_bug.cgi?id=423456 --- Comment #3 from Shawn Starr --- Created attachment 129654 --> https://bugs.kde.org/attachment.cgi?id=129654=edit dbus session starting Kwin Plasma Wayland dbus session starting Kwin Plasma Wayland -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 422895] [Wayland] Systemsettings crash
https://bugs.kde.org/show_bug.cgi?id=422895 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from David Edmundson --- We were killed by kwin for making a protocol violation. Can you run from a terminal and reproduce and paste the contents -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 422963] System Setting crash on selecting any icon after changing button style
https://bugs.kde.org/show_bug.cgi?id=422963 David Edmundson changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO CC||k...@davidedmundson.co.uk --- Comment #1 from David Edmundson --- Can I have your ~/.config/kdeglobals please -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 423459] On second chose in any options of left panel, systemsettings crash
https://bugs.kde.org/show_bug.cgi?id=423459 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk --- Comment #4 from David Edmundson --- Can the others in the duplicates confirm the steps listed by the author of this bug about nvidia-settings? The comment doesn't seem to match the backtrace, but the backtrace also doesn't seem to make sense. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 423459] On second chose in any options of left panel, systemsettings crash
https://bugs.kde.org/show_bug.cgi?id=423459 David Edmundson changed: What|Removed |Added CC||jakobmi...@gmail.com --- Comment #1 from David Edmundson --- *** Bug 422808 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 423459] On second chose in any options of left panel, systemsettings crash
https://bugs.kde.org/show_bug.cgi?id=423459 David Edmundson changed: What|Removed |Added CC||kleberbal...@outlook.com --- Comment #2 from David Edmundson --- *** Bug 422484 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 423459] On second chose in any options of left panel, systemsettings crash
https://bugs.kde.org/show_bug.cgi?id=423459 David Edmundson changed: What|Removed |Added CC||jtr...@gmail.com --- Comment #3 from David Edmundson --- *** Bug 418002 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 418002] KDE Neon system settings and plasmashell keep crashing after enabling/configuring Orca then playing vlc with mp3
https://bugs.kde.org/show_bug.cgi?id=418002 David Edmundson changed: What|Removed |Added Resolution|--- |DUPLICATE CC||k...@davidedmundson.co.uk Status|REPORTED|RESOLVED --- Comment #1 from David Edmundson --- *** This bug has been marked as a duplicate of bug 423459 *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 422808] systemsettings5 crashes on closing window
https://bugs.kde.org/show_bug.cgi?id=422808 David Edmundson changed: What|Removed |Added Resolution|--- |DUPLICATE CC||k...@davidedmundson.co.uk Status|REPORTED|RESOLVED --- Comment #1 from David Edmundson --- *** This bug has been marked as a duplicate of bug 423459 *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 422484] Crash na seleção dos tópicos em Configurações do Sistema, Comportamento do Espaço de Trabalho
https://bugs.kde.org/show_bug.cgi?id=422484 David Edmundson changed: What|Removed |Added Resolution|--- |DUPLICATE CC||k...@davidedmundson.co.uk Status|REPORTED|RESOLVED --- Comment #1 from David Edmundson --- *** This bug has been marked as a duplicate of bug 423459 *** -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 423414] Cropping destroys images
https://bugs.kde.org/show_bug.cgi?id=423414 --- Comment #8 from Oussema Bouaneni --- As far as I know, the code for cropping images is implemented in Gwenview itself, somewhere in here: https://invent.kde.org/graphics/gwenview/-/tree/master/lib/crop . Unfortunately, while I am somewhat familiar with C++, I've never used QT before so this code is complete gibberish to me. If you can understand it I encourage you to try and pinpoint the exact location of your problem. I'll report back in a while whether this bug is reproducible on a fresh install of OpenSUSE Tumbleweed. Hopefully someone more technically competent can help you to fix the issue. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 423456] Unable to use external screen with KScreen in Wayland
https://bugs.kde.org/show_bug.cgi?id=423456 Shawn Starr changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED Ever confirmed|0 |1 --- Comment #2 from Shawn Starr --- No, upgraded to 5.19.2 and still see issue: Display Configuration in systemsettings shows Laptop Screen, but no options for any other displays to select. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423464] New: pie chart representation of percentage is incorrect
https://bugs.kde.org/show_bug.cgi?id=423464 Bug ID: 423464 Summary: pie chart representation of percentage is incorrect Product: plasmashell Version: 5.19.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: System Monitor Assignee: notm...@gmail.com Reporter: s_chriscoll...@hotmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 129653 --> https://bugs.kde.org/attachment.cgi?id=129653=edit screenshot showing the bug SUMMARY CPU and memory monitor widgets set to pie chart (the default) are filling an incorrect amount of the circle. For example, in the attached screenshot, memory usage is 45.6%, but almost 70% of the circle is filled, making it appear that a majority of the system RAM is consumed. STEPS TO REPRODUCE 1. Add a CPU or memory monitor widget to the desktop. OBSERVED RESULT There is a significant discrepancy between actual usage percentage and the percentage of the pie chart that is filled. EXPECTED RESULT The pie chart should represent the percentage accurately. SOFTWARE/OS VERSIONS OS: KDE neon 5.19 User Edition KDE Plasma Version: 5.19.2 KDE Frameworks Version: 5.71.0 Qt Version: 5.14.2 -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 422555] Crash when tagging images in kphotoalbum
https://bugs.kde.org/show_bug.cgi?id=422555 Johannes Zarl-Zierl changed: What|Removed |Added Version Fixed In||5.7.0 --- Comment #14 from Johannes Zarl-Zierl --- I've marked the bug as fixed for now. If you experience any problems with 5.7.0 (once it has been released) or an up-to-date version from git then please reopen this bug (or open a new one)! Cheers, Johannes -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 422555] Crash when tagging images in kphotoalbum
https://bugs.kde.org/show_bug.cgi?id=422555 Johannes Zarl-Zierl changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/grap ||hics/kphotoalbum/commit/c6f ||b6c1214e6a5b65d34573096e6dd ||b5dcd2deb8 Status|REPORTED|RESOLVED --- Comment #13 from Johannes Zarl-Zierl --- Git commit c6fb6c1214e6a5b65d34573096e6ddb5dcd2deb8 by Johannes Zarl-Zierl. Committed on 24/06/2020 at 22:29. Pushed by johanneszarl into branch 'master'. Changelog M +2-0ChangeLog https://invent.kde.org/graphics/kphotoalbum/commit/c6fb6c1214e6a5b65d34573096e6ddb5dcd2deb8 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 423406] /usr/bin/akonadi_kalarm_resource --identifier akonadi_kalarm_resource_X put my cpu at 100%
https://bugs.kde.org/show_bug.cgi?id=423406 --- Comment #1 from David Jarvie --- Did a single akonadi_kalarm_resource process use 100% CPU? If so, the stack trace doesn't help to find out why, since it gives no indication of where in the KAlarmResource it is hogging the CPU. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 423043] kalarm doesn't show alarms until restarting kalarm
https://bugs.kde.org/show_bug.cgi?id=423043 David Jarvie changed: What|Removed |Added Version Fixed In||20.08 Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #3 from David Jarvie --- I'm glad it's working now. The problems you report (and particularly any involving akonadi_kalarm_resource processes) should, I hope, be fixed in KAlarm version 3.0 which will no longer by default use Akonadi. This is due for release in August in KDE release 20.08. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 423067] Additionally assign Meta+Up+Up to "maximize" and Meta+Down+Down to "minimize"
https://bugs.kde.org/show_bug.cgi?id=423067 --- Comment #11 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/kwin/-/merge_requests/81 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 423461] Add PAR (Pixel Aspect Ratio) view option for images with non-square pixel.
https://bugs.kde.org/show_bug.cgi?id=423461 coa...@hyperbola.info changed: What|Removed |Added URL|https://en.wikipedia.org/wi |https://gitlab.gnome.org/GN |ki/Pixel_aspect_ratio |OME/gimp/-/issues/5285 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 423463] Enhance to display order of transactions in ledgers
https://bugs.kde.org/show_bug.cgi?id=423463 Mark changed: What|Removed |Added CC||mwvdum...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 423463] New: Enhance to display order of transactions in ledgers
https://bugs.kde.org/show_bug.cgi?id=423463 Bug ID: 423463 Summary: Enhance to display order of transactions in ledgers Product: kmymoney Version: 5.0.8 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: mwvdum...@gmail.com Target Milestone: --- SUMMARY I can alter the sort order of the transactions in the ledger. I've used post date and entry orders in addition to check numbers. If I choose post date and check number, my check numbers are out of order and I have to hunt for them. If I choose entry and then check number, any new transactions I enter end of at the end of the ledger instead of inline where I'd want to see them. Is it possible to sort the transactions by posting date and override the check sort so that for non checks they are in posting date order, but checks are in check number order. I'm sure it is not a simple thing to do given the existing data organization. But if you sorted by check number first and 'merged' the other transactions in by posting date 'as best you can' I think I would find the ledger display very usable for me. I suspect there are a few gotchas in such am implementation but I hope you might sort them out and make it work. Hopefully, others would like to see this as well. STEPS TO REPRODUCE 1. right click on ledger heading to bring up sort order dialog. 2. figure out a way to enhance this dialog to display like I'm asking. 3. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Fedora Core 32 (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 423461] Add PAR (Pixel Aspect Ratio) view option for images with non-square pixel.
https://bugs.kde.org/show_bug.cgi?id=423461 coa...@hyperbola.info changed: What|Removed |Added Summary|Add PAR (Pixel Aspect |Add PAR (Pixel Aspect |Ratio) simulation for |Ratio) view option for |images with non-square |images with non-square |pixel. |pixel. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 420555] Sorting mode (natural/alphabetical) is not applied immediately
https://bugs.kde.org/show_bug.cgi?id=420555 --- Comment #2 from Szczepan Hołyszewski --- EDIT to add version: 20.04.2 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 420555] Sorting mode (natural/alphabetical) is not applied immediately
https://bugs.kde.org/show_bug.cgi?id=420555 Szczepan Hołyszewski changed: What|Removed |Added CC||rula...@wp.pl --- Comment #1 from Szczepan Hołyszewski --- For me, natural sorting does not work at all, no matter how many times I apply the dialog. This feature is completely broken. Please raise the priority. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 383010] Add support for AVX-512 instructions
https://bugs.kde.org/show_bug.cgi?id=383010 Alexandra Hajkova changed: What|Removed |Added Attachment #129528|0 |1 is obsolete|| --- Comment #44 from Alexandra Hajkova --- Created attachment 129652 --> https://bugs.kde.org/attachment.cgi?id=129652=edit patch -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 383010] Add support for AVX-512 instructions
https://bugs.kde.org/show_bug.cgi?id=383010 --- Comment #43 from Alexandra Hajkova --- My git repo: https://github.com/sasshka/valgrind/commit/2a9d9c2a5e6021cd1b928e03aabb9e493cde5cdd I tested the patch on Knights Landing. I had to rename gdbserver xml files for gdbserver tests to pass - they used to have avx with upper cases: 64bit-avx512-valgrind-s2.xml 64bit-avx512-valgrind-s1.xml 64bit-avx512.xml The patch doesn't seem to handle AVX512 subsets, the knights landing I used didn't have KADD instruction which was added for BW/DQ (according to https://en.wikipedia.org/wiki/AVX-512#New_instructions_by_sets) avx512.stdout.exp is missing in the patch with makes avx512 test to always fail. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 423412] Dolphin can't properly run script if there is space in the path
https://bugs.kde.org/show_bug.cgi?id=423412 --- Comment #3 from Nate Graham --- Nice. Looks like a sensible fix to me. BTW submitting directly is often the best way to have that discussion, so please submit it over here: https://invent.kde.org/frameworks/kio/-/merge_requests/ In your commit message, you can add `Bug: 423412` on its own line and it will automatically close this when merged. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 423003] krunner crashes as soon as I start typing
https://bugs.kde.org/show_bug.cgi?id=423003 Tony Dee changed: What|Removed |Added CC||tonytony+...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 423003] krunner crashes as soon as I start typing
https://bugs.kde.org/show_bug.cgi?id=423003 --- Comment #25 from Tony Dee --- Created attachment 129651 --> https://bugs.kde.org/attachment.cgi?id=129651=edit New crash information added by DrKonqi krunner (5.19.80) using Qt 5.14.2 - What I was doing when the application crashed: Started typing on the desktop. After the second letter is typed, there is a crash. Happens every time. Both on wayland and xorg. thanks. -- Backtrace (Reduced): #4 0x7f76f1934ddc in Plasma::QueryMatch::urls() const (this=this@entry=0x5599db09f018) at ./src/querymatch.cpp:264 #5 0x7f76f1925fd8 in Plasma::AbstractRunner::mimeDataForMatch(Plasma::QueryMatch const&) (this=, match=...) at ./src/abstractrunner.cpp:226 #6 0x7f76f1943563 in Plasma::RunnerManagerPrivate::loadInstalledRunner(KPluginMetaData const&) (this=this@entry=0x5599db823950, pluginMetaData=...) at ./src/runnermanager.cpp:399 #7 0x7f76f1944f9b in Plasma::RunnerManagerPrivate::loadRunners() (this=0x5599db823950) at ./src/runnermanager.cpp:270 #8 0x7f76f194162d in Plasma::RunnerManager::launchQuery(QString const&, QString const&) (this=0x5599db822ba0, untrimmedTerm=..., runnerName=...) at ./src/runnermanager.cpp:913 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 423462] New: Krita version 4.3.0, file size 3.4 GiB so far; (I just hit 100 layers, but there's still 4.5 GiB space LEFT, so the document can hold 7.9 GiB total). For some reason the prog
https://bugs.kde.org/show_bug.cgi?id=423462 Bug ID: 423462 Summary: Krita version 4.3.0, file size 3.4 GiB so far; (I just hit 100 layers, but there's still 4.5 GiB space LEFT, so the document can hold 7.9 GiB total). For some reason the program won't draw: the cursor just stays put and doesn't stroke. It is NOT my tablet Product: krita Version: unspecified Platform: MS Windows OS: Microsoft Windows Status: REPORTED Severity: critical Priority: NOR Component: Brush engines Assignee: krita-bugs-n...@kde.org Reporter: zucciniyagaonl...@live.com Target Milestone: --- Created attachment 129650 --> https://bugs.kde.org/attachment.cgi?id=129650=edit Krita Usage Log (copy-and-pasted) Krita Version: 4.3.0 Languages: en_US, en Hidpi: true Qt Version (compiled): 5.12.8 Version (loaded): 5.12.8 OS Information Build ABI: x86_64-little_endian-llp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: winnt Kernel Version: 10.0.18362 Pretty Productname: Windows 10 (10.0) Product Type: windows Product Version: 10 OpenGL Info Vendor: "Google Inc." Renderer: "ANGLE (Intel(R) HD Graphics 630 Direct3D11 vs_5_0 ps_5_0)" Version: "OpenGL ES 3.0 (ANGLE 2.1.0.57ea533f79a7)" Shading language: "OpenGL ES GLSL ES 3.00 (ANGLE 2.1.0.57ea533f79a7)" Requested format: QSurfaceFormat(version 3.0, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::CompatibilityProfile) Current format:QSurfaceFormat(version 3.0, options QFlags(), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples 0, swapBehavior QSurfaceFormat::DefaultSwapBehavior, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::NoProfile) Version: 3.0 Supports deprecated functions false is OpenGL ES: true QPA OpenGL Detection Info supportsDesktopGL: true supportsAngleD3D11: true isQtPreferAngle: false Hardware Information GPU Acceleration: auto Memory: 16256 Mb Number of Cores: 8 Swap Location: C:/Users/IT/AppData/Local/Temp Current Settings Current Swap Location: C:/Users/IT/AppData/Local/Temp Current Swap Location writable: true Undo Enabled: true Undo Stack Limit: 30 Use OpenGL: true Use OpenGL Texture Buffer: true Use AMD Vectorization Workaround: false Canvas State: OPENGL_SUCCESS Autosave Interval: 900 Use Backup Files: true Number of Backups Kept: 1 Backup File Suffix: ~ Backup Location: Same Folder as the File Backup Location writable: false Use Win8 Pointer Input: false Use RightMiddleTabletButton Workaround: false Levels of Detail Enabled: false Use Zip64: false Display Information Number of screens: 1 Screen: 0 Name: \\.\DISPLAY1 Depth: 32 Scale: 1 Resolution in pixels: 1920x1080 Manufacturer: Model: Refresh Rate: 60 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 353983] Turning off compositing breaks Plasma panel rendering
https://bugs.kde.org/show_bug.cgi?id=353983 --- Comment #176 from Steven Gilberd --- (In reply to Antonio Orefice from comment #175) > Are you still getting this? > Nvidia devs claim the problem was in their driver, that's a bit odd. This was fixed on my laptop about a year ago. So perhaps this was two independent driver bugs, and Intel just happened to fix theirs first? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 423461] Add PAR (Pixel Aspect Ratio) simulation for images with non-square pixel.
https://bugs.kde.org/show_bug.cgi?id=423461 coa...@hyperbola.info changed: What|Removed |Added Platform|unspecified |Compiled Sources Keywords||future_project, usability -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 404073] In "Save as" dialog file name is not completing when is present extension
https://bugs.kde.org/show_bug.cgi?id=404073 Piotr Mierzwinski changed: What|Removed |Added Version|5.69.0 |5.71.0 Keywords||usability --- Comment #4 from Piotr Mierzwinski --- (In reply to Méven Car from comment #3) > I see, just to rephrase, what you suggest would be to have completion > disregarding extension. > > And make the example more detailed: > > In your example, in folder you have > > MyScreenshot_1.png > > You have Screenshot_DATE_TIME.png in the text field with > Screenshot_DATE_TIME selected. > You type "My", field text is now My.png all text unselected with cursor > before .png . > > At this point you would like to have the completion popup with > "MyScreenshot_1.png" offered. > > So it's a feature request to have smarter completion when saving files. Yes. I met such completion in some applications in Windows, so I thought would be nice to have it here in my favorite DE. > >> Clicking on the desired file in the view would give the result you expect. > > Yes. So why we have completing at all? > Completion match works currently by comparing the beginning of file names. > Removing the extension works too (typing four times Suppr key for instance) > > But given our behavior of pre-selecting text excluding extension your > suggestion makes sense. Simple scenario. In spectacle I click in "Save as", get file save dialog, whereas file name is highlighted excluding extension I start typing, so name is removing and now even I enter begin of name as is present in other files in opened directory then nothing is completed. I need to remove extension to get completion. Having completed file name I can easy correct it and don't need neither to remove extension to get completion nor enter whole file name or even click. This is obvious that completion of file name makes life easy in managing files. > > We can click on file name on the list, ritght? > Of course. You can change it as feature request if this is possible here. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 423461] Add PAR (Pixel Aspect Ratio) simulation for images with non-square pixel.
https://bugs.kde.org/show_bug.cgi?id=423461 coa...@hyperbola.info changed: What|Removed |Added OS|Unspecified |All Alias||pixel_aspect_ratio -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 423461] Add PAR (Pixel Aspect Ratio) simulation for images with non-square pixel.
https://bugs.kde.org/show_bug.cgi?id=423461 coa...@hyperbola.info changed: What|Removed |Added URL||https://en.wikipedia.org/wi ||ki/Pixel_aspect_ratio -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 423461] Add PAR (Pixel Aspect Ratio) simulation for images with non-square pixel.
https://bugs.kde.org/show_bug.cgi?id=423461 --- Comment #5 from coa...@hyperbola.info --- Created attachment 129649 --> https://bugs.kde.org/attachment.cgi?id=129649=edit Other example Other PAR example found in: https://graphicdesign.stackexchange.com/questions/75815/what-is-pixel-aspect-ratio -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 423461] Add PAR (Pixel Aspect Ratio) simulation for images with non-square pixel.
https://bugs.kde.org/show_bug.cgi?id=423461 --- Comment #4 from coa...@hyperbola.info --- Created attachment 129648 --> https://bugs.kde.org/attachment.cgi?id=129648=edit PAR 2:1 Image with PAR 2:1 (from Wikimedia) -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 423397] fsck fails after shrinking ext4 fs
https://bugs.kde.org/show_bug.cgi?id=423397 --- Comment #4 from Andrius Štikonas --- (In reply to Laosom from comment #3) > Hi Andrius, > > No matter how I unmount the FS. I did it within Partition Manager and in > Dolphin too. > I did not try fsck manually afterwards, as the filesystem was mounted after > resize by Partition Manager. I assume it is successful if the FS is not > mounted. That is very strange. The filesystem should stay unmounted whether successful or not. KDE Partition Manager would not automount ext4. (It does automount some other filesystems like btrfs that can only be resized when mounted but not ext4.) Maybe something else is automounting fs on your system and interfered with resize2fs command? That might explain why there are fsck errors afterwards. I'm not sure what could be automounting. Partition Manager does try to disable KDE automounter. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 423461] Add PAR (Pixel Aspect Ratio) simulation for images with non-square pixel.
https://bugs.kde.org/show_bug.cgi?id=423461 --- Comment #3 from coa...@hyperbola.info --- Created attachment 129647 --> https://bugs.kde.org/attachment.cgi?id=129647=edit PAR 1:1 Image with PAR 1:1 (from Wikimedia) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 423359] After doing a brushstroke with the new watercolour-brushes in Krita 4.3.0, there always apear "Squares" while and afterwards
https://bugs.kde.org/show_bug.cgi?id=423359 --- Comment #14 from herman --- Sorry, Boudewijn, just got my message back from your server that it was too big. Hope, you got at least some screenshots. Maybe trying again tomorrow. Good night H. Am 24.06.2020 um 10:16 schrieb Boudewijn Rempt: > https://bugs.kde.org/show_bug.cgi?id=423359 > > --- Comment #10 from Boudewijn Rempt --- > Yes, really helpful, thanks! > > This certainly points at an issue with the canvas rendering, not the brush > engines. Since you're on Windows 10, could you experiment a bit more for us? > > * Go to settings->configure krita->display > > and > > * test with canvas acceleration disabled > * test with canvas acceleration enabled, in Angle mode > * test with canvas acceleration enabled, in OpenGL mode > > Could you also attach to this bug report (you'll have to open the bug's url > https://bugs.kde.org/show_bug.cgi?id=423359 and use the And an Attachment > link) > the contents of Help->System Information for Bug reports? > -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406302] window decorations colours on 30-bit colour depth (10-bit/channel) displays are wrong (garbled)
https://bugs.kde.org/show_bug.cgi?id=406302 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 423397] fsck fails after shrinking ext4 fs
https://bugs.kde.org/show_bug.cgi?id=423397 --- Comment #3 from Laosom --- Hi Andrius, No matter how I unmount the FS. I did it within Partition Manager and in Dolphin too. I did not try fsck manually afterwards, as the filesystem was mounted after resize by Partition Manager. I assume it is successful if the FS is not mounted. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 423359] After doing a brushstroke with the new watercolour-brushes in Krita 4.3.0, there always apear "Squares" while and afterwards
https://bugs.kde.org/show_bug.cgi?id=423359 --- Comment #11 from herman --- Hi, Boudewijn, experimented this evening a bit for you, not sure wether these were the right things to do, you asked for. F.E. didn`t know, what you meant with "Angle mode" Did you mean changing the angle of the brush-point(-top)? Putting in some screenshots and hope they give you a bit of a clue, what could be wrong. But, as i mentioned, i am not an IT-specialist. Therefore i pull my head for all you guys and ladies(!), who are constantly working around this program, to get Krita better and better. Okay, whishing you and your team a good time and say "Good night" from here. Herman -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 423461] Add PAR (Pixel Aspect Ratio) simulation for images with non-square pixel.
https://bugs.kde.org/show_bug.cgi?id=423461 --- Comment #2 from coa...@hyperbola.info --- I needs this feature (Pixel Aspect Ratio) for works with drawing images and 2d sprites; its requires for screen with non-square pixels. I can't view correctly images with non-square pixels (like old TV or handled devices with LCD screens). -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 423414] Cropping destroys images
https://bugs.kde.org/show_bug.cgi?id=423414 --- Comment #7 from roman --- Created attachment 129643 --> https://bugs.kde.org/attachment.cgi?id=129643=edit the destroyed image Thank you for your effort. The image of konqi was created with spectacle. But this happens with other jpegs as well. Here is the resulat after I cropped it. May be this helps some how? Do you know what is used for cropping/saving? Maybe imagemagic or so? I could check that on the command line. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 423461] Add PAR (Pixel Aspect Ratio) simulation for images with non-square pixel.
https://bugs.kde.org/show_bug.cgi?id=423461 Tymond changed: What|Removed |Added CC||tamtamy.tym...@gmail.com Version|unspecified |4.3.0 Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from Tymond --- Hi, I noticed you haven't added any explanation what you need not square pixel aspect ratio for. Could you please add it? Please read here: https://docs.krita.org/en/untranslatable_pages/new_features.html about how to write up a good feature request with all the necessary elements. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 423412] Dolphin can't properly run script if there is space in the path
https://bugs.kde.org/show_bug.cgi?id=423412 --- Comment #2 from Tobias Klausmann --- Created attachment 129642 --> https://bugs.kde.org/attachment.cgi?id=129642=edit possible fix While debugging i found this to involve several components (Dolphin, kio, kcoreaddons), yet the seemingly easiest solution seems to be in kios CommandLauncherJob. A diff to fix the described regression is attached (I know this is not the way to upstream patches, yet i wanted it to discuss first) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 423138] [kcm/kwinrules X11] Theme rules are not applied
https://bugs.kde.org/show_bug.cgi?id=423138 Ismael Asensio changed: What|Removed |Added Latest Commit||https://invent.kde.org/plas ||ma/kwin/commit/3bfc750a79f9 ||67a93612385def636dced1ed133 ||7 Status|ASSIGNED|RESOLVED Version Fixed In||5.19.3 Resolution|--- |FIXED --- Comment #3 from Ismael Asensio --- Git commit 3bfc750a79f967a93612385def636dced1ed1337 by Ismael Asensio. Committed on 24/06/2020 at 18:13. Pushed by iasensio into branch 'Plasma/5.19'. [kcm/kwinrules] Fix detection of wmclass property Property `wmclass` of a window rule works in a special way, as it can have two meanings depending on `wmclasscomplete` flag: - false: only matches `resourceClass` - true: matches `resourceName` and `resourceClass` This MR fixes two subtle bugs when detecting the properties of a window: In the first case, `resourceName` was being wrongly set instead, which prevented window matching for windows where those two values differ. Also, the `wmclass` field was always set to `resourceName` independently of `wmclasscomplete` property. FIXED-IN: 5.19.3 M +7-6kcmkwin/kwinrules/rulesmodel.cpp https://invent.kde.org/plasma/kwin/commit/3bfc750a79f967a93612385def636dced1ed1337 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 423461] New: Add PAR (Pixel Aspect Ratio) simulation for images with non-square pixel.
https://bugs.kde.org/show_bug.cgi?id=423461 Bug ID: 423461 Summary: Add PAR (Pixel Aspect Ratio) simulation for images with non-square pixel. Product: krita Version: unspecified Platform: unspecified OS: Unspecified Status: REPORTED Severity: wishlist Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: coa...@hyperbola.info Target Milestone: --- SUMMARY Add PAR (Pixel Aspect Ratio) simulation for images with non-square pixel. An option as "View -> Pixel Aspect Ratio" (Photoshop) STEPS TO REPRODUCE 1. this software works with square pixel only. OBSERVED RESULT I can't found any option like "View -> Pixel Aspect Ratio". EXPECTED RESULT Works with square pixel only. SOFTWARE/OS VERSIONS Windows: any macOS: any Linux/KDE Plasma: any (available in About System) KDE Plasma Version: any KDE Frameworks Version: any Qt Version: any ADDITIONAL INFORMATION https://en.wikipedia.org/wiki/Pixel_aspect_ratio https://graphicdesign.stackexchange.com/questions/75815/what-is-pixel-aspect-ratio -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 423432] Fit page icon is misleading
https://bugs.kde.org/show_bug.cgi?id=423432 --- Comment #3 from apache --- Yes. I reflected to late that there are different use-cases and other factors. In my opinion, the bottom line is that each function should have its own distinct icon, so that when I have them all on the panel they don't confuse me. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 419867] Bouncing when changing virtual desktop through touchpad or mouse wheel scroll (broken with Folder View, works with Desktop view)
https://bugs.kde.org/show_bug.cgi?id=419867 torokat...@gmail.com changed: What|Removed |Added CC||torokat...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 423456] Unable to use external screen with KScreen in Wayland
https://bugs.kde.org/show_bug.cgi?id=423456 David Edmundson changed: What|Removed |Added Status|REPORTED|RESOLVED CC||k...@davidedmundson.co.uk Resolution|--- |FIXED --- Comment #1 from David Edmundson --- I believe this is fixed in 5.19 -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 422413] Browser Identification doesn't work with WebEngine browser engine
https://bugs.kde.org/show_bug.cgi?id=422413 Markus changed: What|Removed |Added CC||m4rkus...@web.de -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423460] New: Weather Report Widget hangs and doesn't update
https://bugs.kde.org/show_bug.cgi?id=423460 Bug ID: 423460 Summary: Weather Report Widget hangs and doesn't update Product: plasmashell Version: 5.18.5 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: System Tray Assignee: plasma-b...@kde.org Reporter: rhuben...@gmail.com Target Milestone: 1.0 SUMMARY Weather Report Widget hangs. STEPS TO REPRODUCE 1. Install Weather Report widget in panel 2. Works first time but never updates 3. If I remove widget and re-install, the widget hangs when I am setting the location with NOAA. 4. It will un-hang, if I logout/login or kill plasmashell & restart OBSERVED RESULT Temperature never changes EXPECTED RESULT Temperature will update every 30 minutes SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.70.0 Qt Version: 5.15.0 Kernel Version: 5.4.44-1-MANJARO OS Type: 64-bit Processors: 4 × Intel® Core™ i3 CPU M 350 @ 2.27GHz Memory: 7.4 GiB of RAM ADDITIONAL INFORMATION I am not sure how to debug this or resolve it. Thank you. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 420009] Resource management issue in Windows, Fatal Error on run
https://bugs.kde.org/show_bug.cgi?id=420009 voronw...@gmail.com changed: What|Removed |Added Resolution|--- |FIXED Status|REOPENED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422572] Plasma crashes and logs out to sddm after a graphic error from amdgpu driver
https://bugs.kde.org/show_bug.cgi?id=422572 --- Comment #3 from Leyenda --- It notifies when an error already. :) -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 423414] Cropping destroys images
https://bugs.kde.org/show_bug.cgi?id=423414 Oussema Bouaneni changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #6 from Oussema Bouaneni --- That's weird. Still can't reproduce on both systems even if I reload. I'll try to make an OpenSUSE tumbleweed VM. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 423455] Selection Tools are only adding selections as if I'm holding the shift key by default
https://bugs.kde.org/show_bug.cgi?id=423455 acc4commissi...@gmail.com changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |NOT A BUG --- Comment #3 from acc4commissi...@gmail.com --- (In reply to Tymond from comment #1) > Works for me. Could you please check Tool Options if you don't have the Add > mode selected? There are three ways to add selections after all: shift, > selecting it in the Tool Options or clicking A, which can probably happen > accidentally sometimes. > > Also if you're using the magic wand tool, please check the Tool options as > well. I changed them recently, maybe that had an impact. It was the case. Sorry. XD I'll be more careful. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 423459] New: On second chose in any options of left panel, systemsettings crash
https://bugs.kde.org/show_bug.cgi?id=423459 Bug ID: 423459 Summary: On second chose in any options of left panel, systemsettings crash Product: systemsettings Version: 5.19.1 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: frno...@gmail.com Target Milestone: --- Application: systemsettings5 (5.19.1) Qt Version: 5.15.0 Frameworks Version: 5.71.0 Operating System: Linux 5.7.2-1-default x86_64 Windowing system: X11 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: using systemsettings if i remove ~/.nvidia-settings-rc and ~/.config/dconf/user than reboot, the problem desapear the problem back when i use the nvidia-settings if i open nvidia-settings (not change any options) reboot system the problem come back sorry my english The crash can be reproduced every time. -- Backtrace: Application: Configurações do sistema (systemsettings5), signal: Segmentation fault [KCrash Handler] #4 0x in ?? () #5 0x7f31a1fee3f7 in QQuickItemLayer::~QQuickItemLayer (this=0x5604255ad9b0, __in_chrg=) at /usr/src/debug/libqt5-qtdeclarative-5.15.0-1.1.x86_64/src/quick/items/qquickitem.cpp:8335 #6 0x7f31a1fee439 in QQuickItemLayer::~QQuickItemLayer (this=0x5604255ad9b0, __in_chrg=) at /usr/src/debug/libqt5-qtdeclarative-5.15.0-1.1.x86_64/src/quick/items/qquickitem.cpp:8333 #7 0x7f31a21653f3 in QAccessibleQuickItem::role (this=0x56042554b420) at /usr/src/debug/libqt5-qtdeclarative-5.15.0-1.1.x86_64/include/QtQuick/../../src/quick/items/qquickitem.h:468 #8 0x7f319de913da in AtSpiAdaptor::pathForInterface (this=this@entry=0x5604236e9570, interface=0x56042554b420) at atspiadaptor.cpp:1538 #9 0x7f319de93594 in AtSpiAdaptor::notifyStateChange (this=this@entry=0x5604236e9570, interface=, state=..., value=0) at atspiadaptor.cpp:873 #10 0x7f319de94c30 in AtSpiAdaptor::notify (this=0x5604236e9570, event=0x7ffdb2153e30) at ../../../include/QtCore/../../src/corelib/text/qstring.h:1062 #11 0x7f31a2000278 in QQuickItemPrivate::setEffectiveVisibleRecur (this=this@entry=0x5604255ada70, newEffectiveVisible=) at /usr/src/debug/libqt5-qtdeclarative-5.15.0-1.1.x86_64/src/quick/items/qquickitem.cpp:6051 #12 0x7f31a2000353 in QQuickItemPrivate::setVisible (this=0x5604255ada70, visible=) at /usr/src/debug/libqt5-qtdeclarative-5.15.0-1.1.x86_64/src/quick/items/qquickitem.cpp:5948 #13 0x7f318d9a9ed6 in ContentItem::forgetItem (this=0x560425beb4d0, item=) at /usr/src/debug/kirigami2-5.71.0-1.1.x86_64/src/columnview.cpp:564 #14 0x7f318d9a9fb8 in ContentItem::itemChange (this=0x560425beb4d0, change=QQuickItem::ItemChildRemovedChange, value=...) at /usr/src/debug/kirigami2-5.71.0-1.1.x86_64/src/columnview.cpp:643 #15 0x7f31a1ffaf55 in QQuickItemPrivate::itemChange (this=this@entry=0x560425beb570, change=change@entry=QQuickItem::ItemChildRemovedChange, data=...) at /usr/src/debug/libqt5-qtdeclarative-5.15.0-1.1.x86_64/src/quick/items/qquickitem.cpp:6271 #16 0x7f31a2001c0f in QQuickItemPrivate::removeChild (this=this@entry=0x560425beb570, child=, child@entry=0x5604255ad9b0) at /usr/src/debug/libqt5-qtdeclarative-5.15.0-1.1.x86_64/src/quick/items/qquickitem.h:185 #17 0x7f31a2003a3c in QQuickItem::setParentItem (this=this@entry=0x5604255ad9b0, parentItem=parentItem@entry=0x0) at /usr/src/debug/libqt5-qtdeclarative-5.15.0-1.1.x86_64/src/quick/items/qquickitem.cpp:2669 #18 0x7f31a2003fc6 in QQuickItem::~QQuickItem (this=0x5604255ad9b0, __in_chrg=) at /usr/src/debug/libqt5-qtdeclarative-5.15.0-1.1.x86_64/src/quick/items/qquickitem.cpp:2311 #19 0x7f318d650c25 in QQmlPrivate::QQmlElement::~QQmlElement (this=, this=) at /usr/include/qt5/QtQml/qqmlprivate.h:142 #20 QQmlPrivate::QQmlElement::~QQmlElement (this=, this=) at /usr/include/qt5/QtQml/qqmlprivate.h:144 #21 0x7f31a2320b68 in KDeclarative::QmlObjectPrivate::~QmlObjectPrivate (this=, this=) at /usr/src/debug/kdeclarative-5.71.0-1.1.x86_64/src/kdeclarative/qmlobject.cpp:71 #22 KDeclarative::QmlObject::~QmlObject (this=, this=) at /usr/src/debug/kdeclarative-5.71.0-1.1.x86_64/src/kdeclarative/qmlobject.cpp:199 #23 0x7f31a2320df9 in KDeclarative::QmlObjectSharedEngine::~QmlObjectSharedEngine (this=, this=) at /usr/src/debug/kdeclarative-5.71.0-1.1.x86_64/src/kdeclarative/qmlobjectsharedengine.cpp:76 #24 0x7f31a408e132 in KQuickAddons::ConfigModule::~ConfigModule (this=, this=) at /usr/src/debug/kdeclarative-5.71.0-1.1.x86_64/src/quickaddons/configmodule.cpp:117 #25 0x7f31770c5f49 in IconModule::~IconModule (this=, this=) at /usr/src/debug/plasma5-desktop-5.19.1-1.1.x86_64/kcms/icons/main.cpp:100 #26 0x7f31a4182f33 in std::default_delete::operator() (__ptr=, this=) at
[kdeconnect] [Bug 423458] New: Contacts with utf-8 characters in the name are not displayed correctly
https://bugs.kde.org/show_bug.cgi?id=423458 Bug ID: 423458 Summary: Contacts with utf-8 characters in the name are not displayed correctly Product: kdeconnect Version: unspecified Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: messaging-application Assignee: si...@ergotech.com Reporter: blazing...@gmail.com Target Milestone: --- SUMMARY The KDE SMS app does not display contact names (or import contact photos) of contacts that have emojis in their names. STEPS TO REPRODUCE 1. Edit a contact name to contain an emoji 2. Restart kdeconnect 3. Open SMS app and look at contact name OBSERVED RESULT Phone number is shown instead of contact name. Contact photo is not imported EXPECTED RESULT Contact should be imported properly SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 20.04 (available in About System) KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 ADDITIONAL INFORMATION The issue may be in the upstream `KF5PeopleVCard` library. I debugged the `personAt` function in `smshelper.cpp` and found that the name for the contact is deformed right after importing. -- You are receiving this mail because: You are watching all bug changes.
