[lattedock] [Bug 406235] Dodge all windows causes dock to hide on empty desktop
https://bugs.kde.org/show_bug.cgi?id=406235 --- Comment #3 from Michail Vourlakos --- It does not occur in my system, 1. Are you using latest master? 2. How did you install Latte? 3. What is your env output? 4. Are you in multi screen environment? -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 406235] Dodge all windows causes dock to hide on empty desktop
https://bugs.kde.org/show_bug.cgi?id=406235 --- Comment #2 from Tyler Brown --- This issue does not occur with the Dodge Active Windows. It also does not occur with the Dodge Maxmized setting. It only occurs under Dodge All Windows. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 406227] Picture without any tag are not listed with button "No Tags"
https://bugs.kde.org/show_bug.cgi?id=406227 --- Comment #7 from Daniel Ouin --- Created attachment 119253 --> https://bugs.kde.org/attachment.cgi?id=119253&action=edit 2nd part of psr zip file... -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 406227] Picture without any tag are not listed with button "No Tags"
https://bugs.kde.org/show_bug.cgi?id=406227 --- Comment #6 from Daniel Ouin --- Created attachment 119252 --> https://bugs.kde.org/attachment.cgi?id=119252&action=edit clearing filters and trash... Thank you Maik for the proposition. I cleared all filters. I checked the trash, but no picture was there. Coming back to Tag tab afterwards, I can see that it is the same. I attach 1 zip file generated by PSR, converted into 2 pdf files in order to fit size limitation. I hope this will help you... -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 405691] Screen flickering in newest 4.2.0 when running through primusrun
https://bugs.kde.org/show_bug.cgi?id=405691 --- Comment #4 from Boudewijn Rempt --- Thanks for testing. I'm beginning to suspect that this is Yet Another Qt 5.12. Bug... I've got a laptop with both nvidia and intel gpu myself, but I haven't got anything setup to use the nvidia gpu... I'll probably have to do that :-( -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 401996] clicking contact web url => uncomplete url is selected
https://bugs.kde.org/show_bug.cgi?id=401996 Laurent Montel changed: What|Removed |Added Latest Commit||https://commits.kde.org/kco ||readdons/7e96b4cee76ba7de73 ||b2e69bfe79c25f8afa5ea9 Version Fixed In||5.57.0 Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #6 from Laurent Montel --- Git commit 7e96b4cee76ba7de73b2e69bfe79c25f8afa5ea9 by Laurent Montel. Committed on 05/04/2019 at 06:12. Pushed by mlaurent into branch 'master'. Fix Bug 401996 - clicking contact web url => uncomplete url is selected (Fixed in kcoreaddons) FIXED-IN: 5.57.0 M +8-0autotests/kstringhandlertest.cpp M +1-1src/lib/text/kstringhandler.cpp https://commits.kde.org/kcoreaddons/7e96b4cee76ba7de73b2e69bfe79c25f8afa5ea9 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 398410] KMyMoney crashes when trying to save entries back to DB Backend
https://bugs.kde.org/show_bug.cgi?id=398410
--- Comment #40 from Thomas Baumgart ---
No, no update. This is something out of the scope of KMyMoney. It works for at
least two more installations (and I bet there are more).
I expect an upstream problem (maybe even only on your installation). Looking at
the first frames of the BT we see
#0 0x7fffef3dbfa0 in __GI___pthread_mutex_lock (mutex=0x20) at
../nptl/pthread_mutex_lock.c:65
#1 0x7fff604622da in () at /usr/lib/x86_64-linux-gnu/libmysqlclient.so.20
and the code to that seems straight forward:
int
__pthread_mutex_lock (pthread_mutex_t *mutex)
{
unsigned int type = PTHREAD_MUTEX_TYPE_ELISION (mutex);
with the assignment of type being the statement on line 65. A pointer of value
0x20 seems a bit odd and is causing the trouble. This pointer is not provided
by KMyMoney, so nothing we can do about.
Did you ever updated any of Qt, libmysql? Sorry, but this is out of reach for
me.
Do we have anyone else running on Kubuntu 18.04.1 with SQL backend?
--
You are receiving this mail because:
You are watching all bug changes.
[kaddressbook] [Bug 401996] clicking contact web url => uncomplete url is selected
https://bugs.kde.org/show_bug.cgi?id=401996 --- Comment #5 from Laurent Montel --- it's a bug in kcoreaddons. I will investigate it -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 406224] 'No space left on device' on startup
https://bugs.kde.org/show_bug.cgi?id=406224 --- Comment #2 from Maik Qualmann --- Scientific Linux Release 6.8 would have to use an old kernel 2.6.x. Do you use the digiKam AppImage? Maik -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 406121] Do not disturb mode icon
https://bugs.kde.org/show_bug.cgi?id=406121
Björn Feber changed:
What|Removed |Added
Latest Commit||https://commits.kde.org/bre
||eze-icons/47af5254b0396d982
||92605a2e0b415e5b222ea04
Resolution|--- |FIXED
Status|CONFIRMED |RESOLVED
--- Comment #2 from Björn Feber ---
Git commit 47af5254b0396d98292605a2e0b415e5b222ea04 by Björn Feber.
Committed on 05/04/2019 at 05:40.
Pushed by bfeber into branch 'master'.
Add "notifications" and "notifications-disabled" icons
Summary:
Needed for the upcoming do not disturb mode and overhauled notifcations.
{F6753477}
{F6753478}
Test Plan: Search for "notifications" in Cuttlefish.
Reviewers: #plasma, #vdg, ngraham, ndavis
Reviewed By: #vdg, ngraham, ndavis
Subscribers: bruns, ndavis, abetts, ngraham, #vdg, kde-frameworks-devel,
#plasma
Tags: #frameworks
Differential Revision: https://phabricator.kde.org/D20226
A +15 -0icons-dark/actions/16/notifications-disabled.svg
A +11 -0icons-dark/actions/16/notifications.svg
A +15 -0icons/actions/16/notifications-disabled.svg
A +11 -0icons/actions/16/notifications.svg
https://commits.kde.org/breeze-icons/47af5254b0396d98292605a2e0b415e5b222ea04
--
You are receiving this mail because:
You are watching all bug changes.
[kmail2] [Bug 406208] "#" in a title news then only a part of the title is transmitted in subject of a mail
https://bugs.kde.org/show_bug.cgi?id=406208 --- Comment #11 from Laurent Montel --- (In reply to Philippe ROUBACH from comment #10) > it looks like https://bugs.kde.org/show_bug.cgi?id=401996 nope we don't use kmail for this one. It's kaddressbook-webengine which doesn't parse correctly. FF has the same problem has it doesn't show ')' as part of url... -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 406241] New: Crash when applying split alpha to layers
https://bugs.kde.org/show_bug.cgi?id=406241 Bug ID: 406241 Summary: Crash when applying split alpha to layers Product: krita Version: 4.1.7 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: Layers/Vector Assignee: krita-bugs-n...@kde.org Reporter: acc4commissi...@gmail.com Target Milestone: --- git 0cf7c06 SUMMARY (To any layers) Split alpha -> Alpha into mask -> Crash SOFTWARE/OS VERSIONS Windows: Windows 7 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION - Error occurred on Friday, April 5, 2019 at 14:01:12. krita.exe caused an Access Violation at location DEP violation at location . AddrPC Params 0D5E2B80 38CE76F0 07FEC76BF428 0D6B6BC0 0DC59A70 0D6B6BC0 libkritaui.dll!0xf428 KisDisplayColorConverter::Private::setCurrentNode+0x128 07FEC76BF7CD 0001 libkritaui.dll!0xf7cd KisDisplayColorConverter::Private::slotCanvasResourceChanged+0xcd 07FECA0F74CA 08E5C4C0 061C 07FECA4A1198 Qt5Core.dll!0x2274ca QMetaObject::activate+0x7fa 07FEC759C5B5 002256F0 1776 43F91CE0 libkritaflake.dll!0x10c5b5 KoCanvasResourceProvider::canvasResourceChanged+0x35 07FECA0F75DD 1C1A50E0 6FD0728C 0020 Qt5Core.dll!0x2275dd QMetaObject::activate+0x90d 07FEC759CE35 1776 000E libkritaflake.dll!0x10ce35 KoResourceManager::resourceChanged+0x35 07FEC7495099 07FECA4A13E0 1776 000E libkritaflake.dll!0x5099 KoResourceManager::setResource+0x3a9 07FEC774736B 1DB7A9C0 002259D0 libkritaui.dll!0x9736b KisCanvasResourceProvider::slotNodeActivated+0x13b 07FEC7A28D32 1C0C0AD0 07FEF6F788A2 38CEFBA0 libkritaui.dll!0x378d32 KisCanvasResourceProvider::qt_static_metacall+0x412 07FECA0F74CA 08E5C370 08E5C370 00225AB8 Qt5Core.dll!0x2274ca QMetaObject::activate+0x7fa 07FEC7A2CB07 00225A18 21DBE820 libkritaui.dll!0x37cb07 KisNodeManager::sigNodeActivated+0x27 07FEC77A8966 21DBE820 0012 07FEC7A3AAE0 libkritaui.dll!0xf8966 KisNodeManager::slotSomethingActivatedNodeImpl+0x146 07FEC77A8B69 39277D50 357F5F60 libkritaui.dll!0xf8b69 KisNodeManager::slotNonUiActivatedNode+0x69 07FEC7A2C56C 0001 0080 00225C60 libkritaui.dll!0x37c56c KisNodeManager::qt_static_metacall+0x3ec 07FECA0F74CA 21DBE820 07FECA0F408C 00225D50 Qt5Core.dll!0x2274ca QMetaObject::activate+0x7fa 07FEC7A3B38A 00226038 357F5F60 libkritaui.dll!0x38b38a KisDummiesFacadeBase::sigActivateNode+0x2a 07FEC7717194 0001 44AAAE80 44AAAE80 libkritaui.dll!0x67194 KisDummiesFacadeBase::slotNodeActivationRequested+0x74 07FEC7A3ADA0 00225DD0 0002 3FE3 libkritaui.dll!0x38ada0 KisDummiesFacadeBase::qt_static_metacall+0x2c0 07FECA0F74CA 0DA1BCD0 0001 39277D50 Qt5Core.dll!0x2274ca QMetaObject::activate+0x7fa 07FEC95C3917 21FECB90 21FECBA0 0008 libkritaimage.dll!0x243917 KisImage::qt_static_metacall+0x347 07FECA0F74CA 16338948 07FECA0F408C 357F5F60 Qt5Core.dll!0x2274ca QMetaObject::activate+0x7fa 07FEC95C01EA 00226170 07FEC94B8049 39277D01 libkritaimage.dll!0x2401ea KisImageSignalRouter::sigNodeAddedAsync+0x2a 07FEC94B976C 07FEC9F79650 00226108 libkritaimage.dll!0x13976c KisImageSignalRouter::emitNodeHasBeenAdded+0x4c 07FEC95067EF 0256F118 00226248 00226360 libkritaimage.dll!0x1867ef KisNode::add+0x2df 07FEC9507A34 0009 37EB95D8 00226268 libkritaimage.dll!0x187a34 KisNodeFacade::addNode+0x44 07FEC93D95B0 07FEFD7F5DC8 00226270 libkritaimage.dll!0x595b0 KisImageLayerAddCommand::redo+0x90 07FEF6BF3340 01D4EBB8071E1E87 07FECA26A300 00050005000407E3 libkritacommand.dll!0x3340 KUndo2Command::redoMergedCommands+0x1c0 07FEF6BF41C2 0060 393BF0E0 00226430 libkritacommand.dll!0x41c2 KUndo2QStack::push+0x32 07FEC954BBB4 37EB9428 07FEFFBF10C8 0040 libkritaimage.dll!0x1cbbb4 KisLegacyUndoAdapter::addCommand+0x24 07FEC77A0BBB 00226508 07FECA26A300 libkritaui.dll!0xf0bbb KisNodeCommandsAdapter::addNode+0x11b 07FEC7795CC
[kmail2] [Bug 406167] Show all messages in mbox
https://bugs.kde.org/show_bug.cgi?id=406167 Laurent Montel changed: What|Removed |Added CC||mon...@kde.org --- Comment #1 from Laurent Montel --- I don't know how to displaying them... open several viewer ? -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 406240] Hour for TODO won't change on KDE NEON
https://bugs.kde.org/show_bug.cgi?id=406240 --- Comment #1 from felipeari...@gmail.com --- I forgot to say that I synced the calendar with Google, in case it's related. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 406240] Hour for TODO won't change on KDE NEON
https://bugs.kde.org/show_bug.cgi?id=406240 felipeari...@gmail.com changed: What|Removed |Added Platform|Other |Neon Packages -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 406028] Folder right-click menu is missing items in the folder panel
https://bugs.kde.org/show_bug.cgi?id=406028 --- Comment #4 from Nate Graham --- (In reply to Abijith from comment #2) > (In reply to Nate Graham from comment #1) > > Yep, looks like it. Probably not a hard patch to write, either. Wanna try > > your hand at it? I can help! > > I am looking for assistance on fixing bugs, can you help me? I am very much > interested in fixing but I have little trouble understanding stuff. I would > like help. First get your development environment set up: https://community.kde.org/Get_Involved/development Then compile Dolphin. After that, check out the code that implements the context menus. The easiest way to find it is to grep through the codebase for English string that appears in the context menu. (In reply to Marcus Sundman from comment #3) > When you find the relevant places in the code, please don't copy'n'paste the > code that adds those menu entries, but have both places call the same piece > of code. For example, you can have a function adding those menu entries, and > then call the same function from both popup-menu-creation places. (That way, > if someone adds more menu entries then those will automatically go to both > menus.) +1, at least for the menu items that are relevant to both the Places panel and the Folder panel. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 406204] Shift and Snap in Assistant Tools do not work
https://bugs.kde.org/show_bug.cgi?id=406204 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #8 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.
[korganizer] [Bug 406240] New: Hour for TODO won't change on KDE NEON
https://bugs.kde.org/show_bug.cgi?id=406240 Bug ID: 406240 Summary: Hour for TODO won't change on KDE NEON Product: korganizer Version: 5.10.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: incidence editors Assignee: kdepim-b...@kde.org Reporter: felipeari...@gmail.com Target Milestone: --- SUMMARY I wanted to use KOrganizer so I installed it on my KDE NEON, unfortunately I can't properly set an start or end hour for my TODO. STEPS TO REPRODUCE 1. Open KOrganizer 2. Create a TODO 3. Try to set an start or end hour for the TODO 4. Save it and open it again. You'll find it at 12:00AM OBSERVED RESULT It never assign an hour for the TODO task. It's always at 12:00AM. EXPECTED RESULT It should assign the hour specified by the user SOFTWARE/OS VERSIONS OS: KDE NEON 5.15 KDE Plasma Version: 5.15.3 KDE Frameworks Version: 5.56.0 Qt Version: 5.12.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 406235] Dodge all windows causes dock to hide on empty desktop
https://bugs.kde.org/show_bug.cgi?id=406235 --- Comment #1 from Michail Vourlakos --- Dodge Active works OK in that regard in your system? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 405691] Screen flickering in newest 4.2.0 when running through primusrun
https://bugs.kde.org/show_bug.cgi?id=405691 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #3 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.
[plasmashell] [Bug 404342] HP Mini 210-2204er + OpenSUSE Leap-15.0 + slideshow = plasmashell CRASH
https://bugs.kde.org/show_bug.cgi?id=404342 --- Comment #3 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 404147] old display / no pressure / crashes
https://bugs.kde.org/show_bug.cgi?id=404147 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.
[kdevelop] [Bug 405097] Unhandled exception in KDevPlatformLanguage.dll during background parsing crashes program
https://bugs.kde.org/show_bug.cgi?id=405097 Bug Janitor Service changed: What|Removed |Added Resolution|FIXED |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #7 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.
[frameworks-kfilemetadata] [Bug 399650] Video duration in Dolphin details mode not working (m2ts & mkv)
https://bugs.kde.org/show_bug.cgi?id=399650 Nate Graham changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #18 from Nate Graham --- We believe this may have been resolved, so please do re-open it if you find that it has not been after upgrading to Frameworks 5.57. Thamks! -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 373178] Blurry scaling on HiDPI
https://bugs.kde.org/show_bug.cgi?id=373178 --- Comment #44 from Nate Graham --- Digikam has a different codebase and will need a different patch. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 405691] Screen flickering in newest 4.2.0 when running through primusrun
https://bugs.kde.org/show_bug.cgi?id=405691 --- Comment #2 from M --- Yes, unfortunately it still is (git f3858d1), with optirun as well as primusrun. The flickers only become apparent once a document is opened or created, and only when there is any movement on screen. No issues with 4.1.8. Another way of avoiding it is starting an X session on the Nvidia GPU directly. In the terminal I see these lines repeated only with primusrun or optirun: qt.glx: qglx_findConfig: Failed to finding matching FBConfig (8 8 8 8) qt.glx: qglx_findConfig: Failed to finding matching FBConfig (1 8 8 8) qt.glx: qglx_findConfig: Failed to finding matching FBConfig (1 1 8 8) qt.glx: qglx_findConfig: Failed to finding matching FBConfig (1 1 1 8) -- You are receiving this mail because: You are watching all bug changes.
[Oxygen] [Bug 406239] New: Better contrast for selected text
https://bugs.kde.org/show_bug.cgi?id=406239 Bug ID: 406239 Summary: Better contrast for selected text Product: Oxygen Version: unspecified Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: kos...@koshka.ddns.net Target Milestone: --- I would like to see better contrast for selected items in Plasma. To start with, I mean selected folders in Dolphin in the sidebar or in the main frame. In Breeze theme you are using a white font on a light-blue background so selected text is actually worse visible than a usual one. I believe you have checked some guides and they said that the contrast is fine. I also didn't find any complaints from other users on the matter (though they complain on pale fonts). I also might be advised to use high contrast theme... But I'm not blind and actually like Breeze theme in each aspect except its accent color, especially when it is used for text selection. It's true that the theme is highly customizable in Plasma through the special GUI, but there are 2 problems: 1) background color also affects progressbar color so after changing the former, the latter becomes invisible when selected (selected row in qbittorrent, for example) 2)There is no GUI for GTK theme so it is needed to change appropriate lines in a huge file for GTK-theme. Changing background color for GTK application is extremely important because most of the problems with selection color I got from Thunderbird and Firefox where I want to see the text better if I selected it. Now I'm using #2d82ac as a background color for selections. It would be nice to have a variant of Breeze with a deeper accent color which would affect GTK apps too. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 398410] KMyMoney crashes when trying to save entries back to DB Backend
https://bugs.kde.org/show_bug.cgi?id=398410 --- Comment #39 from Eleazar --- Any update on this issue? I tried the same process as before using the latest code in branch 5.0 (04/04/2019 @ 21:43 MDT Build version 5.0.3-a4a39821b) #0 0x7fffef3dbfa0 in __GI___pthread_mutex_lock (mutex=0x20) at ../nptl/pthread_mutex_lock.c:65 #1 0x7fff604622da in () at /usr/lib/x86_64-linux-gnu/libmysqlclient.so.20 #2 0x7fff60439b41 in () at /usr/lib/x86_64-linux-gnu/libmysqlclient.so.20 #3 0x7fff6040db2b in mysql_real_connect () at /usr/lib/x86_64-linux-gnu/libmysqlclient.so.20 #4 0x7fff609f61b9 in () at /usr/lib/x86_64-linux-gnu/qt5/plugins/sqldrivers/libqsqlmysql.so #5 0x7fffa6168f50 in QSqlDatabase::open() () at /usr/lib/x86_64-linux-gnu/libQt5Sql.so.5 #6 0x7fffa63c5dff in MyMoneyStorageSql::open(QUrl const&, int, bool) (this=0x55de4b70, url=..., openMode=3, clear=false) at /home/eagleboy/kmymoney/kmymoney/plugins/sql/mymoneystoragesql.cpp:114 #7 0x7fffa63c1748 in SQLStorage::save(QUrl const&) (this=0x56262cc0, url=...) at /home/eagleboy/kmymoney/kmymoney/plugins/sql/sqlstorage.cpp:198 #8 0x5560d2b3 in KMyMoneyApp::slotFileSave() (this=0x55d68790) at /home/eagleboy/kmymoney/kmymoney/kmymoney.cpp:3411 #9 0x5562a21d in QtPrivate::FunctorCall, QtPrivate::List<>, void, bool (KMyMoneyApp::*)()>::call(bool (KMyMoneyApp::*)(), KMyMoneyApp*, void**) (f=(bool (KMyMoneyApp::*)(KMyMoneyApp * const)) 0x5560d198 , o=0x55d68790, arg=0x7fffcdc0) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:136 #10 0x55629f9d in QtPrivate::FunctionPointer::call, void>(bool (KMyMoneyApp::*)(), KMyMoneyApp*, void**) (f=(bool (KMyMoneyApp::*)(KMyMoneyApp * const)) 0x5560d198 , o=0x55d68790, arg=0x7fffcdc0) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:169 #11 0x556295b8 in QtPrivate::QSlotObject, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) (which=1, this_=0x55edef30, r=0x55d68790, a=0x7fffcdc0, ret=0x0) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobject_impl.h:120 #12 0x70c7b77f in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x72bf8122 in QAction::triggered(bool) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #14 0x72bfa80c in QAction::activate(QAction::ActionEvent) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #15 0x72cf112b in () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #16 0x72cf138d in QAbstractButton::mouseReleaseEvent(QMouseEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #17 0x72dd001a in QToolButton::mouseReleaseEvent(QMouseEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #18 0x72c3d048 in QWidget::event(QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #19 0x72dd00b4 in QToolButton::event(QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #20 0x72bfe83c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #21 0x72c0665f in QApplication::notify(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #22 0x70c4c9e8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #23 0x72c05632 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #24 0x72c5816b in () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #25 0x72c5a7da in () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #26 0x72bfe83c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #27 0x72c06104 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #28 0x70c4c9e8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #29 0x72442583 in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #30 0x72444055 in QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #31 0x7241b2eb in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #32 0x7fffd96b91c0 in () at /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 ---Type to continue, or q to quit--- #33 0x7fffe65ed387 in g_main_context_dispatch () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #34 0x7fffe65ed5c0 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #35 0x7fffe65ed64c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #36 0x70ca599f in QEven
[Falkon] [Bug 393480] SSL Error: Server's certificate does not match the URL
https://bugs.kde.org/show_bug.cgi?id=393480 Nick changed: What|Removed |Added CC||futurepi...@gmx.us -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 406238] Transparency can't be rolled back.
https://bugs.kde.org/show_bug.cgi?id=406238 leftcrane changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #1 from leftcrane --- Error. I thought the minimum was opaque - it's actually most transparent. Not intuitive, but works fine. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 406238] New: Transparency can't be rolled back.
https://bugs.kde.org/show_bug.cgi?id=406238 Bug ID: 406238 Summary: Transparency can't be rolled back. Product: Breeze Version: 5.15.3 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: QStyle Assignee: unassigned-b...@kde.org Reporter: leftcr...@tutanota.com Target Milestone: --- Operating System: Kubuntu 18.10 KDE Plasma Version: 5.15.3 KDE Frameworks Version: 5.54.0 Qt Version: 5.11.1 Kernel Version: 4.18.0-17-generic OS Type: 64-bit After you enable transparency in the Breeze config, you can no longer disable it. 1. Enable trasparency in the widget theme, using slider. 2. Observe transparent menus. 3. Disable transparency, using slider. 4. Transparency remains. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 403376] [Wayland] Cannot resize correctly a gtk CSD window by dragging its borders
https://bugs.kde.org/show_bug.cgi?id=403376
David Edmundson changed:
What|Removed |Added
CC||k...@davidedmundson.co.uk
--- Comment #4 from David Edmundson ---
I remember this from a report a while ago.
When dragging, kwin has protection that it only sends one resize event at a
time, then blocks till the app re-renders before sending the next so that it
can track the correct pending topleft position. It made sense on X and
wl_surface.
We sometimes send a configure event twice with the same size. Qt responds, GTK
does not which is legitimate behaviour, then we deadlock till the timeout.
We don't need this request behaviour since we added proper configure ack
handling.
If I do:
bool ShellClient::isWaitingForMoveResizeSync() const {
return false;
}
everything still great and is faster too.
--
You are receiving this mail because:
You are watching all bug changes.
[gwenview] [Bug 373178] Blurry scaling on HiDPI
https://bugs.kde.org/show_bug.cgi?id=373178 --- Comment #43 from younker...@gmail.com --- Happy to see there is a fix for viewer in 19.04, will try to get sometime to test these patches on my gentoobox first. Btw, will the same patch applied to gigikam? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 406237] PDFs get an added margin when printing
https://bugs.kde.org/show_bug.cgi?id=406237 Matthew Trescott changed: What|Removed |Added Resolution|DUPLICATE |--- Ever confirmed|0 |1 Status|RESOLVED|REOPENED --- Comment #2 from Matthew Trescott --- I do not have "Force rasterization" enabled. I don't even know where the scaling settings are. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 406237] PDFs get an added margin when printing
https://bugs.kde.org/show_bug.cgi?id=406237 Michael Weghorn changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED CC||m.wegh...@posteo.de --- Comment #1 from Michael Weghorn --- This sounds like bug 348172, therefore I'm closing this as a duplicate. https://phabricator.kde.org/D7962 added the possibility to select whether or not the document should be scaled to take into account hardware printer margins if the "Force rasterization" option is set in the printer dialog. Please reopen if margins are still added when no scaling has explicitly been selected there. (By the way, https://phabricator.kde.org/D18179 is supposed to make the same options available without having the "Force rasterization" checkbox enabled as well.) *** This bug has been marked as a duplicate of bug 348172 *** -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 348172] Scaling options missing in print dialog
https://bugs.kde.org/show_bug.cgi?id=348172 Michael Weghorn changed: What|Removed |Added CC||matthewtresc...@gmail.com --- Comment #26 from Michael Weghorn --- *** Bug 406237 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 406237] New: PDFs get an added margin when printing
https://bugs.kde.org/show_bug.cgi?id=406237 Bug ID: 406237 Summary: PDFs get an added margin when printing Product: okular Version: 1.6.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: printing Assignee: okular-de...@kde.org Reporter: matthewtresc...@gmail.com Target Milestone: --- Created attachment 119251 --> https://bugs.kde.org/attachment.cgi?id=119251&action=edit Screenshot exhibiting the issue SUMMARY Even when there is nothing extra in the margins of the PDF, Print Preview and the final printed document gets extra margins added. The problem doesn't show up with PostScript files (produced by pdftops). STEPS TO REPRODUCE 1. Open a PDF 2. Go to File > Print Preview 3. Resize the Print Preview window to line up with the document in the main viewer and scroll to the top of the Print Preview window. OBSERVED RESULT An extra margin is added and the original document is shrunken. (see attachment) EXPECTED RESULT The document is printed on paper exactly as it is displayed on the screen, with no margins other than those already in the PDF. SOFTWARE/OS VERSIONS Windows: N/A macOS: N/A Linux/KDE Plasma: Arch Linux (last updated no more than a week ago) (available in About System) KDE Plasma Version: 5.15.3 KDE Frameworks Version: 5.56.0 Qt Version: 5.12.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 406028] Folder right-click menu is missing items in the folder panel
https://bugs.kde.org/show_bug.cgi?id=406028 --- Comment #3 from Marcus Sundman --- (In reply to Abijith from comment #2) > (In reply to Nate Graham from comment #1) > > Yep, looks like it. Probably not a hard patch to write, either. Wanna try > > your hand at it? I can help! > > I am looking for assistance on fixing bugs, can you help me? I am very much > interested in fixing but I have little trouble understanding stuff. I would > like help. When you find the relevant places in the code, please don't copy'n'paste the code that adds those menu entries, but have both places call the same piece of code. For example, you can have a function adding those menu entries, and then call the same function from both popup-menu-creation places. (That way, if someone adds more menu entries then those will automatically go to both menus.) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 406236] kde systemsettings5 crash
https://bugs.kde.org/show_bug.cgi?id=406236 --- Comment #2 from Christoph Feck --- Fix is in KF5 5.53. *** This bug has been marked as a duplicate of bug 397894 *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kcmutils] [Bug 397894] Launch Feedback KCM crashes in KQuickAddons::ConfigModule::needsSave()
https://bugs.kde.org/show_bug.cgi?id=397894 Christoph Feck changed: What|Removed |Added CC||pic...@gmail.com --- Comment #22 from Christoph Feck --- *** Bug 406236 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 403950] Crash on close, after visiting the settings for Launch Feedback
https://bugs.kde.org/show_bug.cgi?id=403950 David Edmundson changed: What|Removed |Added CC||pic...@gmail.com --- Comment #4 from David Edmundson --- *** Bug 406236 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 406236] kde systemsettings5 crash
https://bugs.kde.org/show_bug.cgi?id=406236 David Edmundson changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE CC||k...@davidedmundson.co.uk --- Comment #1 from David Edmundson --- Not 100% sure this is the same thing, please reopen if you have an issue with Plasma >= 5.15 *** This bug has been marked as a duplicate of bug 403950 *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 406236] New: kde systemsettings5 crash
https://bugs.kde.org/show_bug.cgi?id=406236 Bug ID: 406236 Summary: kde systemsettings5 crash Product: systemsettings Version: 5.13.5 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: pic...@gmail.com Target Milestone: --- Application: systemsettings5 (5.13.5) Qt Version: 5.11.1 Frameworks Version: 5.50.0 Operating System: Linux 4.18.0-18-generic x86_64 Distribution: Ubuntu 18.10 -- Information about the crash: - What I was doing when the application crashed: in personalisation > applications, i clicked on one or the other of: file associations or locations. systemsettings immediately crashed. -- Backtrace: Application: System Settings (systemsettings5), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f9f0c7c9840 (LWP 12542))] Thread 6 (Thread 0x7f9ee9f00700 (LWP 12652)): #0 0x7f9f12bb1172 in __libc_disable_asynccancel () at ../sysdeps/unix/sysv/linux/x86_64/cancellation.S:85 #1 0x7f9f12b91f79 in __GI___libc_read (fd=28, buf=0x7f9ee9effc90, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:26 #2 0x7f9f0fd0b180 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f9f0fcc591f in g_main_context_check () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f9f0fcc5df0 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f9f0fcc61d2 in g_main_loop_run () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7f9eeb4b67b6 in () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #7 0x7f9f0fcee135 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #8 0x7f9f1103b164 in start_thread (arg=) at pthread_create.c:486 #9 0x7f9f12ba2def in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7f9eedf1f700 (LWP 12651)): #0 0x7f9f0fcc2d9e in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f9f0fcc52b3 in g_main_context_prepare () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f9f0fcc5d7b in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f9f0fcc5f6c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f9f0fcc5fb1 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f9f0fcee135 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7f9f1103b164 in start_thread (arg=) at pthread_create.c:486 #7 0x7f9f12ba2def in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7f9ef49d2700 (LWP 12570)): #0 0x7f9f12b91f64 in __GI___libc_read (fd=13, buf=0x7f9ef49d1b20, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:26 #1 0x7f9f0fd0b180 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f9f0fcc591f in g_main_context_check () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f9f0fcc5df0 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f9f0fcc5f6c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f9f130b915b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f9f1306616b in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f9f12eb50b6 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f9f121761f5 in () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #9 0x7f9f12ebec87 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f9f1103b164 in start_thread (arg=) at pthread_create.c:486 #11 0x7f9f12ba2def in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7f9f0298e700 (LWP 12545)): #0 0x7f9f110412eb in futex_wait_cancelable (private=, expected=0, futex_word=0x5597fa2e14c8) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f9f110412eb in __pthread_cond_wait_common (abstime=0x0, mutex=0x5597fa2e1478, cond=0x5597fa2e14a0) at pthread_cond_wait.c:502 #2 0x7f9f110412eb in __pthread_cond_wait (cond=0x5597fa2e14a0, mutex=0x5597fa2e1478) at pthread_cond_wait.c:655 #3 0x7f9f03075ebb in () at /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #4 0x7f9f03075c27 in () at /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #5 0x7f9f1103b164 in start_thread (arg=) at pthread_create.c:486 #6 0x7f9f12ba2def in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7f9f094a6700 (LWP 12544)): #0 0x7f9f12b966d9 in __GI___poll (fds=0x7f9efc013a40, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f9f0fcc5e46 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f9f0fcc5f6c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f9f130b915b in QEventDispatcherGlib::processEvents(QFlags)
[lattedock] [Bug 406235] New: Dodge all windows causes dock to hide on empty desktop
https://bugs.kde.org/show_bug.cgi?id=406235 Bug ID: 406235 Summary: Dodge all windows causes dock to hide on empty desktop Product: lattedock Version: git (master) Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: ty...@condoulo.com Target Milestone: --- Created attachment 119250 --> https://bugs.kde.org/attachment.cgi?id=119250&action=edit Video showing the dock dodging the desktop SUMMARY STEPS TO REPRODUCE 1. Enable dodge all windows 2. Click anywhere on the desktop 3. OBSERVED RESULT Dock hides as if it is treating the plasmashell desktop as a window EXPECTED RESULT Dock should not hide as there is no proper window to dodge. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Kubuntu 18.10; Kernel 4.18.0-16-generic; (available in About System) KDE Plasma Version: 5.15.3 KDE Frameworks Version: 5.54.0 Qt Version: 5.11.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 406207] KDE tries to hibernate when there is no swap file/partition.
https://bugs.kde.org/show_bug.cgi?id=406207 --- Comment #5 from David Edmundson --- system settings-> power management -> look at the suspend session checkbox -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 406234] New: The cursor icon appears early. (filter > gradient map)
https://bugs.kde.org/show_bug.cgi?id=406234 Bug ID: 406234 Summary: The cursor icon appears early. (filter > gradient map) Product: krita Version: 4.1.7 Platform: macOS Disk Images OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: icnikera...@gmail.com Target Milestone: --- Created attachment 119249 --> https://bugs.kde.org/attachment.cgi?id=119249&action=edit cursor bug SUMMARY The cursor icon appears early. (filter > gradient map) STEPS TO REPRODUCE watch attachment SOFTWARE/OS VERSIONS Macbook Pro 15" 2016 - macOs Mojave Radeon Pro 455 2 GB Intel HD Graphics 530 1536 MB -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 406207] KDE tries to hibernate when there is no swap file/partition.
https://bugs.kde.org/show_bug.cgi?id=406207 deemon changed: What|Removed |Added CC||pr...@ww.ee -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 406207] KDE tries to hibernate when there is no swap file/partition.
https://bugs.kde.org/show_bug.cgi?id=406207 --- Comment #4 from deemon --- Basically there is NO indication at all that I could enable hibernation. There is 0 settings to enable it (in the GUI at least). However it did what I described in the initial bugreport and adding nohibernate to grub config line fixed it for me. I do not know any other way to "check my powermanagement settings" or whatever and you have to be way more specific than that if you actually want me to do this. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 406207] KDE tries to hibernate when there is no swap file/partition.
https://bugs.kde.org/show_bug.cgi?id=406207 deemon changed: What|Removed |Added Ever confirmed|0 |1 Status|RESOLVED|REOPENED Resolution|NOT A BUG |--- --- Comment #3 from deemon --- And why you think I didn't, before even bothering to report it? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 406233] New: Hard to catch with the cursor (color adjustment curve)
https://bugs.kde.org/show_bug.cgi?id=406233 Bug ID: 406233 Summary: Hard to catch with the cursor (color adjustment curve) Product: krita Version: 4.1.7 Platform: macOS Disk Images OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: icnikera...@gmail.com Target Milestone: --- Created attachment 119248 --> https://bugs.kde.org/attachment.cgi?id=119248&action=edit Hard to catch with the cursor STEPS TO REPRODUCE filter -> ajust -> color adjustment curve try the drag curve point also there is a visual glitch when drag along edge. SYSTEM Macbook Pro 15" 2016 - macOs Mojave Radeon Pro 455 2 GB Intel HD Graphics 530 1536 MB -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 401377] Export to (Onedrive, Dropbox ...) crashes digikam (Segmentation Fault)
https://bugs.kde.org/show_bug.cgi?id=401377 --- Comment #64 from caulier.gil...@gmail.com --- - I notice a slight different version between you (Maegia: 1.1.0j) and me (Fedora 1.1.1b). Probably not a problem ? ==> No idea. Mageia7 beta2 is not yet finalized, but i'm sure that last openssl is used for possible security issue. - Why do you compile with openssl10 and not openssl11? ==> Because it's the last stable provided in standard in Centos6.10. It's a LTS support. There are 2 reasons also why 1.0 is used instead 1.1 : the binary compatibilty at run time, and the plenty of problems when packaging. I tried to use 1.1, but this need to package or revisite a large collection of libraries. This introduce also a double linking stage which mix 1.0 and 1.1 version. This create a mess in AppImage. - export OPENSSL_CONF=/etc/pki/openssl10.cnf : why not if this don't have a side effect. I will test here... Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 406208] "#" in a title news then only a part of the title is transmitted in subject of a mail
https://bugs.kde.org/show_bug.cgi?id=406208 --- Comment #10 from Philippe ROUBACH --- it looks like https://bugs.kde.org/show_bug.cgi?id=401996 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 406232] New: ASAN log of direct memory leaks for 4.2 prealpha
https://bugs.kde.org/show_bug.cgi?id=406232 Bug ID: 406232 Summary: ASAN log of direct memory leaks for 4.2 prealpha Product: krita Version: git master Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: griffinval...@gmail.com Target Milestone: --- Created attachment 119247 --> https://bugs.kde.org/attachment.cgi?id=119247&action=edit Krita ASAN output of only direct leaks. SUMMARY These are all the 'Direct Memory Leaks' from the Adress Sanitizer build. Some of these are known(Our LCMS plugin), but the SVG and Docker related ones might need a second look. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 401377] Export to (Onedrive, Dropbox ...) crashes digikam (Segmentation Fault)
https://bugs.kde.org/show_bug.cgi?id=401377 --- Comment #63 from Nicofo --- Humm, I have compared your openssl.cnf with mines: it is totally similar to the one coming from compat-openssl10-1.0.2o-3 package (which differs from the one from openssl-libs-1.1.1b-3 package, used as default on Fedora). So I understand why it works on your machine. But I don't know why this is different with Fedora (why different config files?). - I notice a slight different version between you (Maegia: 1.1.0j) and me (Fedora 1.1.1b). Probably not a problem ? - Why do you compile with openssl10 and not openssl11? - To make appimage work with Fedora, maybe you could add in your appimage exe something like: if [ -f /etc/pki/openssl10.cnf ] then export OPENSSL_CONF=/etc/pki/openssl10.cnf \ (but I could understand you don't want to add plenty of distro specific codes. But I don't know how else trying to solve this issue...) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 124788] Allow to turn off AdvancedSlideshow delay [patch]
https://bugs.kde.org/show_bug.cgi?id=124788 --- Comment #4 from Maik Qualmann --- - bool offAutoDelay is not initialized - not implemented in OpenGL mode - after the left click the control widget stays permanently on Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 401377] Export to (Onedrive, Dropbox ...) crashes digikam (Segmentation Fault)
https://bugs.kde.org/show_bug.cgi?id=401377 --- Comment #62 from Nicofo --- Humm, I have compared your openssl.cnf with mines: it is totally similar to the one coming from compat-openssl10-1.0.2o-3 package (which differs from the one from openssl-libs-1.1.1b-3 package, used as default on Fedora). So I understand why it works on your machine. But I don't know why this is different with Fedora (why different config files?). - I notice a slight different version between you (Maegia: 1.1.0j) and me (Fedora 1.1.1b). Probably not a problem ? - Why do you compile with openssl10 and not openssl11? - TO make appimage work with Fedora, maybe you could add in your appimage exe if -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 124788] Allow to turn off AdvancedSlideshow delay [patch]
https://bugs.kde.org/show_bug.cgi?id=124788 Maik Qualmann changed: What|Removed |Added Attachment #119244|0 |1 is obsolete|| --- Comment #3 from Maik Qualmann --- Created attachment 119246 --> https://bugs.kde.org/attachment.cgi?id=119246&action=edit AutoDelay2.patch Patch adapted to current git/master. Maik -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kcmutils] [Bug 398820] sizeHint not properly passed on for KCMs with a QML UI, causing the window to be too short when opened standalone
https://bugs.kde.org/show_bug.cgi?id=398820 --- Comment #13 from Patrick Silva --- This bug persists. Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.15.80 KDE Frameworks Version: 5.57.0 Qt Version: 5.12.0 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 387454] MTP doesn't work in KDE with Linux 4.14
https://bugs.kde.org/show_bug.cgi?id=387454 Ben Bullard changed: What|Removed |Added CC|benbullar...@cox.net| -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 406231] New: Wifi is very slow to connect when opening session
https://bugs.kde.org/show_bug.cgi?id=406231 Bug ID: 406231 Summary: Wifi is very slow to connect when opening session Product: plasma-nm Version: master Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: jgrul...@redhat.com Reporter: edouard.duli...@gmail.com Target Milestone: --- Description of problem: Wifi is very slow to connect when I open a session. after a good 10 seconds the system says "wrong password" then immediately connects to the wifi. Right after opening the session, if I disable wifi and enable it again, it connects to the wifi rapidly and flawlessly. How reproducible: everytime Steps to Reproduce: 1. open session 2. wait for wifi to connect (10 sec) Actual results: error message then connects flawlessly Expected results: connects to wifi within 3 sec Additional info: Wifi card: 02:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78) rfkill list 0: hci0: Bluetooth Soft blocked: yes Hard blocked: no 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no nmcli con NAME UUID TYPE DEVICE AKED adbfb94b-0c7b-4078-9253-715f12988ede wifi wlp2s0 journal: janv. 26 08:56:39 localhost.localdomain NetworkManager[940]: [1548489399.2501] audit: op="statistics" arg="refresh-rate-ms" pid=1413 uid=1000 result="success" janv. 26 08:56:38 localhost.localdomain audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' janv. 26 08:56:32 localhost.localdomain chronyd[843]: Selected source 192.168.1.1 janv. 26 08:56:28 localhost.localdomain NetworkManager[940]: [1548489388.4548] audit: op="statistics" arg="refresh-rate-ms" pid=1413 uid=1000 result="success" janv. 26 08:56:28 localhost.localdomain nm-dispatcher[4358]: req:6 'connectivity-change': start running ordered scripts... janv. 26 08:56:28 localhost.localdomain nm-dispatcher[4358]: req:6 'connectivity-change': new request (3 scripts) janv. 26 08:56:28 localhost.localdomain NetworkManager[940]: [1548489388.1945] manager: NetworkManager state is now CONNECTED_GLOBAL janv. 26 08:56:28 localhost.localdomain audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' janv. 26 08:56:28 localhost.localdomain chronyd[843]: Source 37.187.18.4 online janv. 26 08:56:28 localhost.localdomain chronyd[843]: Source 188.165.207.160 online janv. 26 08:56:28 localhost.localdomain chronyd[843]: Source 212.51.181.242 online janv. 26 08:56:28 localhost.localdomain chronyd[843]: Source 92.243.6.5 online janv. 26 08:56:27 localhost.localdomain systemd[1]: iscsi.service: Unit cannot be reloaded because it is inactive. janv. 26 08:56:27 localhost.localdomain nm-dispatcher[4358]: req:5 'up' [wlp2s0]: start running ordered scripts... janv. 26 08:56:27 localhost.localdomain nm-dispatcher[4358]: req:5 'up' [wlp2s0]: new request (3 scripts) janv. 26 08:56:27 localhost.localdomain NetworkManager[940]: [1548489387.9733] device (wlp2s0): Activation: successful, device activated. janv. 26 08:56:27 localhost.localdomain NetworkManager[940]: [1548489387.9699] policy: set 'AKED' (wlp2s0) as default for IPv4 routing and DNS janv. 26 08:56:27 localhost.localdomain NetworkManager[940]: [1548489387.9696] manager: NetworkManager state is now CONNECTED_SITE janv. 26 08:56:27 localhost.localdomain dhclient[4507]: bound to 192.168.1.41 -- renewal in 32850 seconds. janv. 26 08:56:27 localhost.localdomain NetworkManager[940]: [1548489387.9603] manager: NetworkManager state is now CONNECTED_LOCAL janv. 26 08:56:27 localhost.localdomain NetworkManager[940]: [1548489387.9600] device (wlp2s0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed') janv. 26 08:56:27 localhost.localdomain NetworkManager[940]: [1548489387.9597] device (wlp2s0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed') janv. 26 08:56:27 localhost.localdomain NetworkManager[940]: [1548489387.9586] device (wlp2s0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed') janv. 26 08:56:27 localhost.localdomain avahi-daemon[804]: Registering new address record for 192.168.1.41 on wlp2s0.IPv4. janv. 26 08:56:27 localhost.localdomain avahi-daemon[804]: New relevant interface wlp2s0.IPv4 for mDNS. janv. 26 08:56:27 localhost.localdomain avahi-daemon[804]: Joining mDNS multicast group on interface wlp2s0.IPv4 with address 192.168.1.41. janv. 26 08:56:27 localhost.localdomain NetworkManager[940]: [1548489387.9563] dhcp4 (wlp2s0): state change
[digikam] [Bug 124788] Allow to turn off AdvancedSlideshow delay [patch]
https://bugs.kde.org/show_bug.cgi?id=124788 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com Summary|Allow to turn off |Allow to turn off |AdvancedSlideshow delay |AdvancedSlideshow delay ||[patch] -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 406230] New: Subfolders of "local folders" (inbox, outbox, drafts, templates) are no longer localized
https://bugs.kde.org/show_bug.cgi?id=406230 Bug ID: 406230 Summary: Subfolders of "local folders" (inbox, outbox, drafts, templates) are no longer localized Product: kmail2 Version: 5.10.3 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: folders Assignee: kdepim-b...@kde.org Reporter: gsten...@gmx.net Target Milestone: --- After restarting kmail and akonadi from scratch (after deleting all akonadi data and kmail settings), the subfolders of "Local folders" are no longer translated. STEPS TO REPRODUCE remove .config/akonadi/* remove .local/share/akonadi/* remove kmail settings Alternatively, you can create a new user and start kmail. OBSERVED RESULT Even though using German locale, the subfolders of "local folders" have English names. EXPECTED RESULT The names should be localized. That has been the case until recently. SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSuse Tumbleweed KDE Plasma Version: 5.15.3 KDE Frameworks Version: 5.56.0 Qt Version: 5.12.2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 405587] KDE became monochrome after update
https://bugs.kde.org/show_bug.cgi?id=405587 --- Comment #13 from Martin Flöser --- KWin doesn't provide the greyscale effect. You either installed it manually or your distribution. -- You are receiving this mail because: You are watching all bug changes.
[kio-gdrive] [Bug 387995] Dolphin KIO gdrive unknown error
https://bugs.kde.org/show_bug.cgi?id=387995 Tapio Metsälä changed: What|Removed |Added Platform|Archlinux Packages |Kubuntu Packages CC||tapio.mets...@elisanet.fi --- Comment #5 from Tapio Metsälä --- This bug has appeared in Kubuntu 18.10. I got kio-grive occasionally working, but only momentarily. Attached 'journalctl -b | grep kdeinit5' log. huhti 04 20:06:27 tapio-VG069AA-UUW-m9751sc dbus-daemon[2249]: [session uid=1000 pid=2249] Activating service name='org.kde.ActivityManager' requested by ':1.6' (uid=1000 pid=2322 comm="kded5 [kdeinit5] " label="unconfined") huhti 04 20:06:30 tapio-VG069AA-UUW-m9751sc dbus-daemon[2249]: [session uid=1000 pid=2249] Activating service name='org.kde.KScreen' requested by ':1.6' (uid=1000 pid=2322 comm="kded5 [kdeinit5] " label="unconfined") huhti 04 20:06:52 tapio-VG069AA-UUW-m9751sc dbus-daemon[2249]: [session uid=1000 pid=2249] Activating via systemd: service name='org.bluez.obex' unit='dbus-org.bluez.obex.service' requested by ':1.6' (uid=1000 pid=2322 comm="kded5 [kdeinit5] " label="unconfined") huhti 04 20:08:09 tapio-VG069AA-UUW-m9751sc dbus-daemon[2249]: [session uid=1000 pid=2249] Activating service name='com.google.code.AccountsSSO.SingleSignOn' requested by ':1.64' (uid=1000 pid=2953 comm="gdrive.so [kdeinit5] gdrive local:/run/user/1000/k" label="unconfined") huhti 04 20:09:28 tapio-VG069AA-UUW-m9751sc dbus-daemon[2249]: [session uid=1000 pid=2249] Activating service name='com.google.code.AccountsSSO.SingleSignOn' requested by ':1.64' (uid=1000 pid=2953 comm="gdrive.so [kdeinit5] gdrive local:/run/user/1000/k" label="unconfined") huhti 04 20:09:47 tapio-VG069AA-UUW-m9751sc dbus-daemon[1131]: [system] Activating service name='org.debian.AptXapianIndex' requested by ':1.54' (uid=1000 pid=2322 comm="kded5 [kdeinit5] " label="unconfined") (using servicehelper) huhti 04 20:09:47 tapio-VG069AA-UUW-m9751sc dbus-daemon[1131]: [system] Rejected send message, 1 matched rules; type="method_return", sender=":1.128" (uid=0 pid=3054 comm="/usr/bin/python3 /usr/share/apt-xapian-index/updat" label="unconfined") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.54" (uid=1000 pid=2322 comm="kded5 [kdeinit5] " label="unconfined") huhti 04 20:10:57 tapio-VG069AA-UUW-m9751sc dbus-daemon[2249]: [session uid=1000 pid=2249] Activating service name='org.kubuntu.DriverManager' requested by ':1.6' (uid=1000 pid=2322 comm="kded5 [kdeinit5] " label="unconfined") huhti 04 21:58:15 tapio-VG069AA-UUW-m9751sc dbus-daemon[2249]: [session uid=1000 pid=2249] Activating service name='com.google.code.AccountsSSO.SingleSignOn' requested by ':1.169' (uid=1000 pid=6092 comm="gdrive.so [kdeinit5] gdrive local:/run/user/1000/k" label="unconfined") -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 382390] plasma-shell crash when search for app in installed app list
https://bugs.kde.org/show_bug.cgi?id=382390 Elmas changed: What|Removed |Added Platform|Archlinux Packages |Neon Packages CC||bilal.el...@outlook.com Version|5.10.3 |5.15.3 --- Comment #3 from Elmas --- Application: Plasma (plasmashell), signal: Segmentation fault -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 406227] Picture without any tag are not listed with button "No Tags"
https://bugs.kde.org/show_bug.cgi?id=406227 --- Comment #5 from Maik Qualmann --- Can you please clear the filter on the status bar with press the trash icon and try again. Maik -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kfilemetadata] [Bug 405210] baloofile_extractor crash
https://bugs.kde.org/show_bug.cgi?id=405210 Alexander Stippich changed: What|Removed |Added CC||a.stipp...@gmx.net --- Comment #2 from Alexander Stippich --- Can you retest with KF 5.56? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kfilemetadata] [Bug 404565] baloo_file_extractor crashes in Exiv2::DataValue::toLong() in kfilemetadata_exiv2extractor on specific image file
https://bugs.kde.org/show_bug.cgi?id=404565 --- Comment #8 from Alexander Stippich --- KDE Frameworks 5.56 contains a change that may also fix your crash. Can you retest? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kfilemetadata] [Bug 399650] Video duration in Dolphin details mode not working (m2ts & mkv)
https://bugs.kde.org/show_bug.cgi?id=399650 Alexander Stippich changed: What|Removed |Added Component|general |general Product|BalooWidgets|frameworks-kfilemetadata Version|18.08.0 |5.54.0 Assignee|baloo-bugs-n...@kde.org |pinak.ah...@gmail.com --- Comment #17 from Alexander Stippich --- KFileMetaData was not able to extract the properties from .ts and .ogv. I cannot exactly reproduce the issue with .mkv though, but there were some recent fixes to mimetype detection, which may have been the issue. Please report back once you have KDE Frameworks 5.57 (to be released April 13th) or higher. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 406219] [WACOM] pen buttons swapped
https://bugs.kde.org/show_bug.cgi?id=406219 --- Comment #3 from Piotr --- Let me make a guess: Krita/Qt picks up some kind of physical, low level button id instead od one mapped by the driver. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 406227] Picture without any tag are not listed with button "No Tags"
https://bugs.kde.org/show_bug.cgi?id=406227 --- Comment #4 from Daniel Ouin --- This not tagged file is a GIF file, not a JPEG file. Sorry for this mistake. But it does not change any thing in this bug -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 406219] [WACOM] pen buttons swapped
https://bugs.kde.org/show_bug.cgi?id=406219 --- Comment #2 from Piotr --- I don't know how to get more from it, it seems pretty basic. I just observed output like this one (this was with lower button pressed): ... Stylus move X=63.09 Y=145.23 B=2 P=25.8% (DRAW) Stylus move X=63.17 Y=145.23 B=2 P=13.6% (DRAW) Stylus release X=63.17 Y=145.23 B=0 P=0.0% Mouse release I just observed B value (bitfield?), how it corresponds with pressed buttons on stylus, and to regular mouse. What I got is that in this build: B=1 regular draw, mouse left B=2 draw with lower stylus button pressed, mouse right B=4 draw with upper stylus button pressed, mouse middle This is independent from what I set in tablet preference utility, even if I set for eg. lower button to 'disabled' it still reacts as right button and reports B=2. I noticed it first, when I wanted to move the canvas, and instead pop-up palette appeared... -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 406227] Picture without any tag are not listed with button "No Tags"
https://bugs.kde.org/show_bug.cgi?id=406227 --- Comment #3 from Daniel Ouin --- In fact, I have RAW files and JPEG files in my folders. I do not want Digikam to categorize RAW files. That's why I set this MIME type filter. I attached above an example of a JPEG picture that do not have any tag. I am expecting to see this picture in "Tag" tab when "No tags" button is activated. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 406227] Picture without any tag are not listed with button "No Tags"
https://bugs.kde.org/show_bug.cgi?id=406227 --- Comment #2 from Daniel Ouin --- Created attachment 119245 --> https://bugs.kde.org/attachment.cgi?id=119245&action=edit JPEG Picture without any tag -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 393480] SSL Error: Server's certificate does not match the URL
https://bugs.kde.org/show_bug.cgi?id=393480 jltrinchard changed: What|Removed |Added CC||jimmy.trinch...@gmail.com --- Comment #5 from jltrinchard --- I had the same problem while visiting reputable sites, and I couldn't reproduce the problem on Chromium and Firefox. Nevertheless, I found out that my DNSBL on pfBlockerNG was causing the issue. By launching Falkon from the terminal, I would get the following: [7645:7663:0404/123334.261921:ERROR:cert_verify_proc_nss.cc(944)] CERT_PKIXVerifyCert for www.google-analytics.com failed err=-8102 [7645:7661:0404/123434.553688:ERROR:cert_verify_proc_nss.cc(944)] CERT_PKIXVerifyCert for www.googletagservices.com failed err=-8102 [7645:7663:0404/123436.621166:ERROR:cert_verify_proc_nss.cc(944)] CERT_PKIXVerifyCert for www.googletagmanager.com failed err=-8102 [7645:7662:0404/123523.083457:ERROR:nss_ocsp.cc(614)] No URLRequestContext for NSS HTTP handler. host: ocsp.digicert.com [7645:7662:0404/123523.083538:ERROR:nss_ocsp.cc(614)] No URLRequestContext for NSS HTTP handler. host: crl4.digicert.com [7645:7663:0404/123525.908547:ERROR:cert_verify_proc_nss.cc(944)] CERT_PKIXVerifyCert for collector.githubapp.com failed err=-8102 That would be from visiting https://www.reddit.com/r/kde/comments/azva4r/falkon_ssl_certificate_error/ and other places. The certificates shown in KDE's SSL Preferences and the Kleopatra/GnuPG logs looked fine. I also don't have any NTP-related issues. After checking the DNSBL logs, I realized that pfBlockerNG's DNS blacklist was causing the issue. It redirects unwanted traffic to a private IP address which has a web server hosting a basic page and its own certificate. Firefox and Chromium silently ignore the SSL error, and I didn't add any certificate exception for the DNSBL address. On the other hand, Falkon brings up the SSL certificate error window. After adding an exception whenever a unique domain name becomes blacklisted, the exceptions become cleared after restarting Falkon. :( So, presumably if a user is running pfBlockerNG, a similar DNSBL service, or blocks domains using some hosts file, then they'll probably encounter OP's problem. I hope that was helpful. I left the status as 'REPORTED' instead of 'CONFIRMED' because my explanation probably doesn't cover all scenarios that lead to OP's issue. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 405587] KDE became monochrome after update
https://bugs.kde.org/show_bug.cgi?id=405587 --- Comment #12 from Tom Kijas --- Yeah, because it would be totally strange if by update something goes wrong ;) Noone has access to my PC. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 124788] Allow to turn off AdvancedSlideshow delay
https://bugs.kde.org/show_bug.cgi?id=124788 Sambhav Dusad changed: What|Removed |Added CC||sambhavdusa...@gmail.com --- Comment #2 from Sambhav Dusad --- Created attachment 119244 --> https://bugs.kde.org/attachment.cgi?id=119244&action=edit Solves the #124788 entry. This patch gives the user option to switch off the Auto Delay option in Advanced Slideshow. The user has to check the Off Auto Delay checkbox. After Checking this, the effects will be turned off and user can traverse the slideshow using the mouse|pagedown|cursor|space. Sambhav -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 406200] Limit Scope Types
https://bugs.kde.org/show_bug.cgi?id=406200 --- Comment #2 from John --- Hello Jasem Thank you. Best regards, John Sent from my iPad > On Apr 4, 2019, at 6:17 AM, Jasem Mutlaq wrote: > > https://bugs.kde.org/show_bug.cgi?id=406200 > > Jasem Mutlaq changed: > > What|Removed |Added > > Latest Commit||https://commits.kde.org/kst > ||ars/7bf777cf4bf66c72e8942d5 > ||c463874fcb9b438c7 > Status|REPORTED|RESOLVED > Resolution|--- |FIXED > > --- Comment #1 from Jasem Mutlaq --- > Git commit 7bf777cf4bf66c72e8942d5c463874fcb9b438c7 by Jasem Mutlaq. > Committed on 04/04/2019 at 10:16. > Pushed by mutlaqja into branch 'master'. > > Add RC telescope type > > M +12 -10 kstars/auxiliary/ksuserdb.cpp > M +7-1kstars/oal/equipmentwriter.ui > > https://commits.kde.org/kstars/7bf777cf4bf66c72e8942d5c463874fcb9b438c7 > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 404843] s390x: backtrace sometimes ends prematurely
https://bugs.kde.org/show_bug.cgi?id=404843 --- Comment #7 from Julian Seward --- Thanks for the testing and review. > + For s390, the unwound registers are: R11(FP) R14(LR) R15(SP) F0 F2 F4 … > This doesn't match the current implementation, right? That's correct. The comment is out of date. I'll fix it. > In fact it seems that F0-F7 are unwound, although F0, F2, and F4 are > probably sufficient (I hope). I at first implemented only F0, F2 and F4, but then I thought it would be worth checking for "summarisation failures" (failures to represent the unwind info in V's internal structures) when reading all the unwind data for libc/libpthread/whatever when starting a hello-world program. From that it was obvious that the compiler really does use all of F0-F7 at least once. So I decided to do them all. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 406229] baloo-file-extractor crashes
https://bugs.kde.org/show_bug.cgi?id=406229 --- Comment #1 from Nicolas Fella --- I was able to pinpoint the crash to a file: https://cgit.kde.org/digikam.git/tree/core/tests/metadataengine/data/20160821035715.jpg -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected
https://bugs.kde.org/show_bug.cgi?id=356225 --- Comment #323 from Dan Duris --- (In reply to Martin Ueding from comment #319) > (In reply to Dan Duris from comment #312) > > I have made a little Python script that performs these changes. This seems > to work, it at least did so for me twice. One has to restart plasmashell > manually afterwords. You can run it with `--dry` to see what it will change. > > https://gist.github.com/martin-ueding/45c7ae78a091db3accfcffaf65588d9f Hi, I had to partially modify it as my xrandr output does not have "primary" screen set. So, I just modified it to "DP1 connected 1920" and it worked! Thanks for that. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 406225] digikam exits when trying to assign tags to large selection (using sidebar)
https://bugs.kde.org/show_bug.cgi?id=406225 --- Comment #3 from caulier.gil...@gmail.com --- Another point : you can disable opengl access to QtWenEngine at run time to turn off a env. variable, before to run you native system digiKam 6.0.0: export QT_XCB_FORCE_SOFTWARE_OPENGL=1 Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 406219] [WACOM] pen buttons swapped
https://bugs.kde.org/show_bug.cgi?id=406219 wolthera changed: What|Removed |Added CC||griffinval...@gmail.com --- Comment #1 from wolthera --- This might be related to our recent attempts at fixing the tablet support with qt 5.12. Can you attach some of the debug from the tablet tester? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 406229] New: baloo-file-extractor crashes
https://bugs.kde.org/show_bug.cgi?id=406229 Bug ID: 406229 Summary: baloo-file-extractor crashes Product: frameworks-baloo Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Baloo File Daemon Assignee: baloo-bugs-n...@kde.org Reporter: nicolas.fe...@gmx.de Target Milestone: --- Created attachment 119243 --> https://bugs.kde.org/attachment.cgi?id=119243&action=edit Backtrace SOFTWARE/OS VERSIONS KDE Plasma Version: 5.15.3 KDE Frameworks Version: 5.56 Qt Version: 5.12.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 406225] digikam exits when trying to assign tags to large selection (using sidebar)
https://bugs.kde.org/show_bug.cgi?id=406225 --- Comment #2 from caulier.gil...@gmail.com --- Also please try with the Qtwebkit version of digiKam 6.1.0 appimage bundle pre-release to see if problem is reproducible. https://files.kde.org/digikam/ Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 406223] CSV Import of "Remove" transactions reclassifies as "Add Shares"
https://bugs.kde.org/show_bug.cgi?id=406223 --- Comment #3 from mcdrae...@gmail.com --- Located the csvimporterrc file and confirmed that invalid transaction types that the user maps to the "Remove Shares" action are correctly being appended to the "ShrsoutParam" line. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 406225] digikam exits when trying to assign tags to large selection (using sidebar)
https://bugs.kde.org/show_bug.cgi?id=406225 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com --- Comment #1 from caulier.gil...@gmail.com --- The crash appear in nividia card driver. Did you use QtWebEngine or QtWebKit as web browser components from Qt5 with digiKam ? Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 404843] s390x: backtrace sometimes ends prematurely
https://bugs.kde.org/show_bug.cgi?id=404843
--- Comment #6 from Andreas Arnez ---
(In reply to Julian Seward from comment #5)
> Created attachment 119229 [details]
> Proposed fix
>
> For s390x, adds unwinding of f0..f7, so as to be able the handle the case
> where GPRs are saved in caller-saved fp registers.
Thanks! This certainly helps a lot. In my limited testing the unwinding seems
to have worked consistently with this patch. Note that I've only tried GCC
8.0.1. A few comments:
> [...]
> --- a/coregrind/m_debuginfo/debuginfo.c
> +++ b/coregrind/m_debuginfo/debuginfo.c
> @@ -3199,6 +3199,15 @@ Addr ML_(get_CFA) ( Addr ip, Addr sp, Addr fp,
> [...]
> uregs.sp = sp;
> uregs.fp = fp;
> + /* JRS FIXME 3 Apr 2019: surely we can do better for f0..f7 */
> + uregs.f0 = 0;
> + uregs.f1 = 0;
I think we can skip the FPR initialization here. IIUC, we'd only need it
if the CFA depended on an FPR. But this would be a very unusual compiler
decision, because an FPR can't be used for addressing. I'd say we can
rule that out.
> [...]
> @@ -3259,6 +3268,8 @@ void VG_(ppUnwindInfo) (Addr from, Addr to)
> For arm, the unwound registers are: R7 R11 R12 R13 R14 R15.
>
> For arm64, the unwound registers are: X29(FP) X30(LR) SP PC.
> +
> + For s390, the unwound registers are: R11(FP) R14(LR) R15(SP) F0 F2 F4 …
This doesn't match the current implementation, right? In fact it seems
that F0-F7 are unwound, although F0, F2, and F4 are probably sufficient (I
hope). Theoretically we could even avoid unwinding the FPRs at all; we
just need them for the initial frame. Since all of F0-F7 are volatile,
the caller can't really have saved anything there.
By the way, the PC doesn't need to be unwound either, since unwound frames
have PC == R14.
> [...]
> --- a/coregrind/m_debuginfo/storage.c
> +++ b/coregrind/m_debuginfo/storage.c
> @@ -138,7 +138,31 @@ void ML_(ppDiCfSI) ( const XArray* /* of CfiExpr */ e…
> [...]
> +VG_(printf)("oldF6");\
> + } else \
> + if (_how == CFIR_S390X_F7) {\
> +VG_(printf)("oldF7");\
> + } else{ \
Missing space.
> [...]
> --- a/coregrind/m_libcassert.c
> +++ b/coregrind/m_libcassert.c
> @@ -176,6 +176,15 @@
> [...]
> (srP)->misc.S390X.r_fp = fp; \
> (srP)->misc.S390X.r_lr = lr; \
> +/* ANDREAS 3 Apr 2019 FIXME r_f0..r_f7 */ \
> +(srP)->misc.S390X.r_f0 = 0;/*FIXME*/ \
> +(srP)->misc.S390X.r_f1 = 0;/*FIXME*/ \
Let me look into this, I'll provide a suitable inline assembly.
> [...]
> --- a/coregrind/m_machine.c
> +++ b/coregrind/m_machine.c
> @@ -118,6 +118,23 @@ void VG_(get_UnwindStartRegs) ( /*OUT*/UnwindStartReg…
> [...]
> regs->misc.S390X.r_lr
>= VG_(threads)[tid].arch.vex.guest_LR;
> + /* ANDREAS 3 Apr 2019 FIXME r_f0..r_f7: is this correct? */
> + regs->misc.S390X.r_f0
> + = VG_(threads)[tid].arch.vex.guest_v0.w64[0];
Looks correct to me. The FPRs overlap with the lower-addressed halves of
the respective vector registers.
> [...]
> --- a/coregrind/m_signals.c
> +++ b/coregrind/m_signals.c
> @@ -526,6 +526,15 @@ typedef struct SigQueue {
> (srP)->r_sp = (ULong)((uc)->uc_mcontext.regs.gprs[15]);\
> (srP)->misc.S390X.r_fp = (uc)->uc_mcontext.regs.gprs[11]; \
> (srP)->misc.S390X.r_lr = (uc)->uc_mcontext.regs.gprs[14]; \
> +/* ANDREAS 3 Apr 2019 FIXME r_f0..r_f7: is this correct? */ \
> +(srP)->misc.S390X.r_f0 = (uc)->uc_mcontext.fpregs.fprs[0]; \
Looks OK.
--
You are receiving this mail because:
You are watching all bug changes.
[kdenlive] [Bug 374171] Kdenlive crashed when closing and saving a project
https://bugs.kde.org/show_bug.cgi?id=374171 emohr changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #1 from emohr --- Please try with the actual Kdenlive_Nightly_Appimage https://binary-factory.kde.org/job/Kdenlive_Nightly_Appimage_Build/lastSuccessfulBuild/artifact/ -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 373813] Crash when inserting new track above the first one
https://bugs.kde.org/show_bug.cgi?id=373813 emohr changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #2 from emohr --- Please try with the actual Kdenlive_Nightly_Appimage https://binary-factory.kde.org/job/Kdenlive_Nightly_Appimage_Build/lastSuccessfulBuild/artifact/ -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 396559] "digikam.dbengine: Database is locked." when scanning for new items.
https://bugs.kde.org/show_bug.cgi?id=396559 Maik Qualmann changed: What|Removed |Added CC||ben.hu...@framestore.com --- Comment #3 from Maik Qualmann --- *** Bug 406228 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 406228] getting random unextpected 'Database is locked' events
https://bugs.kde.org/show_bug.cgi?id=406228 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Maik Qualmann --- *** This bug has been marked as a duplicate of bug 396559 *** -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 406220] Crash when deleting more than 5000 transactions at once
https://bugs.kde.org/show_bug.cgi?id=406220 Thomas Baumgart changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://commits.kde.org/kmy ||money/a4a39821bbea41228f6f7 ||ee49d1d97f6f006ea8e Status|REPORTED|RESOLVED Version Fixed In||5.0.4 --- Comment #1 from Thomas Baumgart --- Git commit a4a39821bbea41228f6f7ee49d1d97f6f006ea8e by Thomas Baumgart. Committed on 04/04/2019 at 18:00. Pushed by tbaumgart into branch '5.0'. Avoid crash when removing items from container FIXED-IN: 5.0.4 M +14 -10 kmymoney/views/kgloballedgerview_p.h https://commits.kde.org/kmymoney/a4a39821bbea41228f6f7ee49d1d97f6f006ea8e -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 406219] [WACOM] pen buttons swapped
https://bugs.kde.org/show_bug.cgi?id=406219 Piotr changed: What|Removed |Added Summary|[WACOM] pen buttons |[WACOM] pen buttons swapped |inverted| -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 406227] Picture without any tag are not listed with button "No Tags"
https://bugs.kde.org/show_bug.cgi?id=406227 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #1 from Maik Qualmann --- In the right sidebar a MIME type filter is active (no RAW files) which probably filters the display of items. The no tags search works here without problems. Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 406228] New: getting random unextpected 'Database is locked' events
https://bugs.kde.org/show_bug.cgi?id=406228 Bug ID: 406228 Summary: getting random unextpected 'Database is locked' events Product: digikam Version: 6.0.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Database Assignee: digikam-bugs-n...@kde.org Reporter: ben.hu...@framestore.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. this can happen at any time 2. 3. OBSERVED RESULT UI locks while in the shell the below goes on endless repeat, requiring force-quitting. Digikam::BdEngineBackendPrivate::checkRetrySQLiteLockError: Database is locked. Waited 6500 Digikam::BdEngineBackendPrivate::checkRetrySQLiteLockError: Database is locked. Waited 6750 Digikam::BdEngineBackendPrivate::checkRetrySQLiteLockError: Database is locked. Waited 7000 Digikam::BdEngineBackendPrivate::checkRetrySQLiteLockError: Database is locked. Waited 7250 Digikam::BdEngineBackendPrivate::checkRetrySQLiteLockError: Database is locked. Waited 7500 Digikam::BdEngineBackendPrivate::checkRetrySQLiteLockError: Database is locked. Waited 7750 Digikam::BdEngineBackendPrivate::checkRetrySQLiteLockError: Database is locked. Waited 8000 Digikam::BdEngineBackendPrivate::checkRetrySQLiteLockError: Database is locked. Waited 8250 Digikam::BdEngineBackendPrivate::checkRetrySQLiteLockError: Database is locked. Waited 8500 Digikam::BdEngineBackendPrivate::checkRetrySQLiteLockError: Database is locked. Waited 8750 Digikam::BdEngineBackendPrivate::checkRetrySQLiteLockError: Database is locked. Waited 9000 Digikam::BdEngineBackendPrivate::checkRetrySQLiteLockError: Database is locked. Waited 9250 Digikam::BdEngineBackendPrivate::checkRetrySQLiteLockError: Database is locked. Waited 9500 Digikam::BdEngineBackendPrivate::checkRetrySQLiteLockError: Database is locked. Waited 9750 Digikam::BdEngineBackendPrivate::checkRetrySQLiteLockError: Database is locked. Waited 1 Digikam::BdEngineBackendPrivate::checkRetrySQLiteLockError: Detected locked database file. There is an active transaction. Waited but giving up now. Digikam::BdEngineBackendPrivate::debugOutputFailedQuery: Failure executing query: "SELECT latitude, latitudeNumber, longitude, longitudeNumber, altitude, orientation, tilt, roll, accuracy, description FROM ImagePositions WHERE imageid=?;" Error messages: "Unable to fetch row" "database table is locked: ImagePositions" 6 1 Bound values: (QVariant(qlonglong, 128130)) EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: scientific linux release 6.8 (Carbon), Gnome 2.28.2 (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.
[digikam] [Bug 406224] 'No space left on device' on startup
https://bugs.kde.org/show_bug.cgi?id=406224 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #1 from Maik Qualmann --- This message comes from the QFilesystemWatcher. The number of monitorable folders may be limited depending on the operating system. Tests here on Linux were possible depending on the free kernel memory for the 50,000 folders. Under BSD, however, it is very limited according to Qt-DOC. Which kernel do you use exactly and how many folders does your image collection have? Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 406227] New: Picture without any tag are not listed with button "No Tags"
https://bugs.kde.org/show_bug.cgi?id=406227 Bug ID: 406227 Summary: Picture without any tag are not listed with button "No Tags" Product: digikam Version: 6.0.0 Platform: Other OS: MS Windows Status: REPORTED Severity: grave Priority: NOR Component: Tags-Engine Assignee: digikam-bugs-n...@kde.org Reporter: daniel.o...@wanadoo.fr Target Milestone: --- Created attachment 119242 --> https://bugs.kde.org/attachment.cgi?id=119242&action=edit Screen shot of "No tags" bug SUMMARY In "Tags" tab, no picture is listed when I select the radio button "No tags", whereas I have few non-tagged pictures. STEPS TO REPRODUCE 1. Launch Digikam 2. Click on tab "Tags" on the left 3. Click on radio button "No tags" OBSERVED RESULT No picture is listed. EXPECTED RESULT Picture not assigned to any tag (i.e. for example newly imported pictures) should appear in the list. SOFTWARE/OS VERSIONS Windows: WIN 10 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION This feature was working properly with the previous version. This feature is very helpful when importing new picture and for checking the result of categorization at any time. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 406223] CSV Import of "Remove" transactions reclassifies as "Add Shares"
https://bugs.kde.org/show_bug.cgi?id=406223 --- Comment #2 from mcdrae...@gmail.com --- Also a similar thing happens when I import an QFX through the OFX importer: where buy transactions get turned into sell transactions. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 406226] New: adding tags to a selection from a large list of no-tags images takes a very long time
https://bugs.kde.org/show_bug.cgi?id=406226 Bug ID: 406226 Summary: adding tags to a selection from a large list of no-tags images takes a very long time Product: digikam Version: 6.0.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Tags-Engine Assignee: digikam-bugs-n...@kde.org Reporter: ben.hu...@framestore.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. toggle 'no tags' in a library that contains lots of no-tags images 2. select a couple of images 3. apply a tag using the side bar tag window OBSERVED RESULT UI becomes non responsive for a solid minute while digikam seems to iterate through all the images that are still 'no tags' after the operation, complaining about missing thumbnails, etc, or whatever reaction each image provokes EXPECTED RESULT no such re-scanning of images that are still 'no-tag'. not sure if this is really what happens, but that's the only activity I can see during this time of unresponsiveness. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: scientific linux release 6.8 (Carbon), Gnome 2.28.2 (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.
