[plasmashell] [Bug 405920] Display is out-of-focus/flickering after waking up from sleep
https://bugs.kde.org/show_bug.cgi?id=405920 --- Comment #11 from techxga...@outlook.com --- So I tried creating a new user account (probably the first thing I should've tried), and that flickering doesn't happen. I'm now trying to isolate the problem by comparing the settings from one user to another -- You are receiving this mail because: You are watching all bug changes.
[kdepim] [Bug 406333] Markdown addon: support syntax highlighting
https://bugs.kde.org/show_bug.cgi?id=406333 --- Comment #24 from avlas --- (In reply to Laurent Montel from comment #23) > > Sorry, I think I didn't explain myself well. I was not talking here now > > about the conversion from markdown to html, but about highlighting the email > > body in the composer while writing (if/when the markdown button is > > activated). In that case, it would be great to see how markdown keywords > > written in plain text get automatically highlighted. This would help writing > > markdown emails, e.g. to better structure the email or more easily visualize > > markdown typos. > > Ah ok. I don't know if it's possible but indeed I can look at it. Great, thanks -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406639] Disabling Full Screen -> crash
https://bugs.kde.org/show_bug.cgi?id=406639 Martin Flöser changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |BACKTRACE --- Comment #1 from Martin Flöser --- Unfortunately the backtrace is lacking debug symbols. If you are able to reproduce please install debug symbols and attach a new backtrace. -- You are receiving this mail because: You are watching all bug changes.
[kdepim] [Bug 406333] Markdown addon: support syntax highlighting
https://bugs.kde.org/show_bug.cgi?id=406333 --- Comment #23 from Laurent Montel --- (In reply to avlas from comment #22) > (In reply to Laurent Montel from comment #21) > > (In reply to avlas from comment #20) > > > (In reply to Laurent Montel from comment #18) > > > > Created attachment 119461 [details] > > > > Screenshot > > > > > > I had some ideas for further enhancement after seeing your screenshot (as > > > well as this one http://25.io/mou/img/1...@2x.png): > > > > > > 1) It would be great if Kmail composer would use KSyntaxHighlighting > > > technology as well to ease writing emails in markdown format, so it gets > > > automatically enabled when the markdown button in the composer is > > > activated. > > > > KSyntaxHighlighting highlights only text, it can create a html code but not > > for converting > > markdown to html. > > Sorry, I think I didn't explain myself well. I was not talking here now > about the conversion from markdown to html, but about highlighting the email > body in the composer while writing (if/when the markdown button is > activated). In that case, it would be great to see how markdown keywords > written in plain text get automatically highlighted. This would help writing > markdown emails, e.g. to better structure the email or more easily visualize > markdown typos. Ah ok. I don't know if it's possible but indeed I can look at it. > > > > 2) It would be so great to have a live preview (as shown in the link > > > above; > > > please note that Kate has already something similar to this) instead of a > > > pop-up window. > > > > We can't do it as composer is a "QTextEdit" and we need a html viewer/editor > > for showing > > mardown result. QTextEdit is too limited for html. > > I see. That's a pity, such a feature would probably attract users, > especially KDE users using markdown-here in other email client applications > or in the browser. yep but in thunderbird they use a html editor directly... It's not possible in Qt. > > I know there is the option but never tried using an external editor for > writing emails. I assume this would not be an option for writing emails in > markdown either, right? Saying because perhaps one could use Kate for this... > > > > 3) It would be nice if there could be an option to remember the status of > > > the Markdown button in the composer. > > > > We can do it. I will look at it. > > Thank you! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406636] Security problem with Desktop Grid
https://bugs.kde.org/show_bug.cgi?id=406636 Martin Flöser changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #2 from Martin Flöser --- *** This bug has been marked as a duplicate of bug 234153 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 234153] Effects grabbing keyboard prevent screen locking
https://bugs.kde.org/show_bug.cgi?id=234153 Martin Flöser changed: What|Removed |Added CC||aleseco.f...@gmail.com --- Comment #16 from Martin Flöser --- *** Bug 406636 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 406469] Clicking on individual songs does nothing
https://bugs.kde.org/show_bug.cgi?id=406469 --- Comment #1 from Matthieu Gallien --- The single click like for the gird views allows to select the current item. That is to make it usable with touch screens. The highlight effect is also necessary to make the application usable by keyboard (useful for everybody but especially people not able to make a good use of a mouse). Without the effect for the current item inside a view, you cannot know what is the current track when navigating with keyboard. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 405333] Unexpected connections between fast, short, close brush strokes.
https://bugs.kde.org/show_bug.cgi?id=405333 --- Comment #7 from acc4commissi...@gmail.com --- (In reply to Boudewijn Rempt from comment #6) > Could you try changing the double-click distance in the wacom settings? See > https://docs.krita.org/en/user_manual/drawing_tablets.html#wacom-double- > click-sensitivity-straight-starts-of-lines It fixed the problem. Thanks. Apparently it wasn't a bug.. -- You are receiving this mail because: You are watching all bug changes.
[kdepim] [Bug 406333] Markdown addon: support syntax highlighting
https://bugs.kde.org/show_bug.cgi?id=406333 --- Comment #22 from avlas --- (In reply to Laurent Montel from comment #21) > (In reply to avlas from comment #20) > > (In reply to Laurent Montel from comment #18) > > > Created attachment 119461 [details] > > > Screenshot > > > > I had some ideas for further enhancement after seeing your screenshot (as > > well as this one http://25.io/mou/img/1...@2x.png): > > > > 1) It would be great if Kmail composer would use KSyntaxHighlighting > > technology as well to ease writing emails in markdown format, so it gets > > automatically enabled when the markdown button in the composer is activated. > > KSyntaxHighlighting highlights only text, it can create a html code but not > for converting > markdown to html. Sorry, I think I didn't explain myself well. I was not talking here now about the conversion from markdown to html, but about highlighting the email body in the composer while writing (if/when the markdown button is activated). In that case, it would be great to see how markdown keywords written in plain text get automatically highlighted. This would help writing markdown emails, e.g. to better structure the email or more easily visualize markdown typos. > > 2) It would be so great to have a live preview (as shown in the link above; > > please note that Kate has already something similar to this) instead of a > > pop-up window. > > We can't do it as composer is a "QTextEdit" and we need a html viewer/editor > for showing > mardown result. QTextEdit is too limited for html. I see. That's a pity, such a feature would probably attract users, especially KDE users using markdown-here in other email client applications or in the browser. I know there is the option but never tried using an external editor for writing emails. I assume this would not be an option for writing emails in markdown either, right? Saying because perhaps one could use Kate for this... > > 3) It would be nice if there could be an option to remember the status of > > the Markdown button in the composer. > > We can do it. I will look at it. Thank you! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 406648] New: Crash when creating a text
https://bugs.kde.org/show_bug.cgi?id=406648 Bug ID: 406648 Summary: Crash when creating a text Product: krita Version: nightly build (please specify the git hash!) Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: Tool/Text Assignee: krita-bugs-n...@kde.org Reporter: acc4commissi...@gmail.com Target Milestone: --- git 17f2c8d SUMMARY I opened one of my png images in krita and then krita crashed when I tried to create a text on it. (where it should create a vector layer automatically) It's not always reproducable. SOFTWARE/OS VERSIONS Windows: Window 7 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Error occurred on Thursday, April 18, 2019 at 01:50:46. krita.exe caused an Access Violation at location 07FECD0E6430 in module libkritaflake.dll Reading from location 0010. AddrPC Params 07FECD0E6430 46080340 07FEFDFB13D2 0002 libkritaflake.dll!0x46430 KoShapeController::pixelsPerInch+0x0 07FECD1975C3 000A 07FECC4CD1BA 37AFFE90 libkritaflake.dll!0xf75c3 KoSvgTextShapeFactory::createShape+0x283 07FEC64CE1A1 0022B3D0 07FECD0E5FB3 3FF0 krita_tool_svgtext.dll!0xe1a1 SvgTextTool::mouseReleaseEvent+0x401 07FECD0F0D30 C04A C048 libkritaflake.dll!0x50d30 KoToolProxy::mouseReleaseEvent+0x60 07FECD0F11E1 004A40B0 004C6A30 004A4168 libkritaflake.dll!0x511e1 KoToolProxy::mouseReleaseEvent+0x21 07FEC98D5883 3413BEE0 46085DD0 1C74E820 libkritaui.dll!0x15883 KisToolProxy::forwardEvent+0x193 07FEC9B2BD3E 77C53128 0001 365CB910 libkritaui.dll!0x26bd3e KisToolInvocationAction::end+0xae 07FEC9B37260 0001 0028 0022B5B0 libkritaui.dll!0x277260 KisShortcutMatcher::tryEndRunningShortcut+0x70 07FEC9B38D55 365CB910 0001 0F99DCA0 libkritaui.dll!0x278d55 KisShortcutMatcher::buttonReleased+0x215 07FEC9B25083 1C228EE0 07FECC1F0D90 0022B700 libkritaui.dll!0x265083 KisInputManager::eventFilterImpl+0x283 07FECC35AA70 0022FBB0 0001 365CB910 Qt5Core.dll!0x1faa70 QCoreApplication::applicationVersionChanged+0x1a0 07FECADB7BB5 1C22C4E0 0003 011800BB Qt5Widgets.dll!0x7bb5 QApplicationPrivate::notify_helper+0x75 07FECADBFC5A 07FECC18215F Qt5Widgets.dll!0xfc5a QApplication::notify+0x13aa 07FEC9B80E56 3FF0 C04E8000 libkritaui.dll!0x2c0e56 KisApplication::notify+0x16 07FECC35C0C8 3FF0 Qt5Core.dll!0x1fc0c8 QCoreApplication::sendSpontaneousEvent+0x1a8 07FECADBE058 000804E4 0215 Qt5Widgets.dll!0xe058 QApplicationPrivate::sendMouseEvent+0x208 07FECAE0AA5D 0252A140 07FECC35A971 Qt5Widgets.dll!0x5aa5d QDesktopWidget::qt_metacall+0x2a1d 07FECAE0D7E3 0022FBB0 024603B0 0001 Qt5Widgets.dll!0x5d7e3 QDesktopWidget::qt_metacall+0x57a3 07FECADB7BDC 0068 0068 002E02E8 Qt5Widgets.dll!0x7bdc QApplicationPrivate::notify_helper+0x9c 07FECADBEC63 34143EA0 07FECC18215F 088C0D10 Qt5Widgets.dll!0xec63 QApplication::notify+0x3b3 07FEC9B80E56 0001 07FECB89ACC4 libkritaui.dll!0x2c0e56 KisApplication::notify+0x16 07FECC35C0C8 0022C410 088BE4E8 1C73F0F0 Qt5Core.dll!0x1fc0c8 QCoreApplication::sendSpontaneousEvent+0x1a8 07FECB887198 07FECC361F53 0001 Qt5Gui.dll!0x37198 QGuiApplicationPrivate::processMouseEvent+0x858 07FECB8883D5 02460450 000C04CA Qt5Gui.dll!0x383d5 QGuiApplicationPrivate::processWindowSystemEvent+0x105 07FECB8603FC 77CA6AF8 000C04CA 0401 Qt5Gui.dll!0x103fc QWindowSystemInterface::sendWindowSystemEvents+0x44c 07FECC3B689A 0038 0022C618 Qt5Core.dll!0x25689a QEventDispatcherWin32Private::sendTimerEvent+0x60a 77A49BBD 0022C730 07FECC3B63C0 USER32.dll!0x19bbd UserCallWinProcCheckWow+0x1ad 77A498C2 0022C730 0022C730 07FECC3B63C0 USER32.dll!0x198c2 DispatchMessageWorker+0x3b5 07FECC3B5D4B 02460450 0024 02528B20 Qt5Core.dll!0x255d4b QEventDispatcherWin32::processEvents+0x5db 6A8FB515 0080 0014 20BA1350 qwindows.dll!0x7b515
[plasmashell] [Bug 406647] New: Alternative Navigation Trough Windows won't work past first instance
https://bugs.kde.org/show_bug.cgi?id=406647 Bug ID: 406647 Summary: Alternative Navigation Trough Windows won't work past first instance Product: plasmashell Version: master Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Task Manager Assignee: h...@kde.org Reporter: wolft...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY The alternative version of Navigation Trough Windows only allows one to go to the next window. None of the normal functions to continue through the windows, go back etc. are possible. So, it can only go back and forth between two windows when using the recent-window setting. STEPS TO REPRODUCE 1. Enable a keyboard shortcut on the Alternative tab of Navigation Trough Windows settings 2. Use the shortcut and hold down the modifier key 3. Press the action key again and/or try using the arrow keys OBSERVED RESULT After first switch, no more switching can happen EXPECTED RESULT Behavior just like the Main setting just with whatever different filters or visualization SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Neon user edition 5.15 (available in About System) KDE Plasma Version: 5.15.4 KDE Frameworks Version: 5.57.0 Qt Version: 5.12.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdepim] [Bug 406333] Markdown addon: support syntax highlighting
https://bugs.kde.org/show_bug.cgi?id=406333 --- Comment #21 from Laurent Montel --- (In reply to avlas from comment #20) > (In reply to Laurent Montel from comment #18) > > Created attachment 119461 [details] > > Screenshot > > I had some ideas for further enhancement after seeing your screenshot (as > well as this one http://25.io/mou/img/1...@2x.png): > > 1) It would be great if Kmail composer would use KSyntaxHighlighting > technology as well to ease writing emails in markdown format, so it gets > automatically enabled when the markdown button in the composer is activated. KSyntaxHighlighting highlights only text, it can create a html code but not for converting markdown to html. > 2) It would be so great to have a live preview (as shown in the link above; > please note that Kate has already something similar to this) instead of a > pop-up window. We can't do it as composer is a "QTextEdit" and we need a html viewer/editor for showing mardown result. QTextEdit is too limited for html. > > 3) It would be nice if there could be an option to remember the status of > the Markdown button in the composer. We can do it. I will look at it. > > Please let me know if these ideas make sense and if you would like me to > open new bug reports for them, especially points 2 and 3 above, which are > not about highlighting. > > I can easily foresee myself in the near future writing all my emails in > markdown format instead of plain text :) -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 405780] "Create New..." button can't appear in the toolbar
https://bugs.kde.org/show_bug.cgi?id=405780 mthw0 changed: What|Removed |Added CC||matejm98m...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwidgetsaddons] [Bug 378523] KFontRequester: Fonts are saved with face name preventing bold/italic from working
https://bugs.kde.org/show_bug.cgi?id=378523 Jonathan Vasquez changed: What|Removed |Added CC|j...@xyinn.org | -- You are receiving this mail because: You are watching all bug changes.
[kdepim] [Bug 406333] Markdown addon: support syntax highlighting
https://bugs.kde.org/show_bug.cgi?id=406333 --- Comment #20 from avlas --- (In reply to Laurent Montel from comment #18) > Created attachment 119461 [details] > Screenshot I had some ideas for further enhancement after seeing your screenshot (as well as this one http://25.io/mou/img/1...@2x.png): 1) It would be great if Kmail composer would use KSyntaxHighlighting technology as well to ease writing emails in markdown format, so it gets automatically enabled when the markdown button in the composer is activated. 2) It would be so great to have a live preview (as shown in the link above; please note that Kate has already something similar to this) instead of a pop-up window. 3) It would be nice if there could be an option to remember the status of the Markdown button in the composer. Please let me know if these ideas make sense and if you would like me to open new bug reports for them, especially points 2 and 3 above, which are not about highlighting. I can easily foresee myself in the near future writing all my emails in markdown format instead of plain text :) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 399585] Enabling Windows 8+ pointer input breaks middle button actions
https://bugs.kde.org/show_bug.cgi?id=399585 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- 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.
[krita] [Bug 405618] Ist nach 10h zeichnen beim zwischen speichern abgestürzt die ganzen 10 h arbeit wurden nicht gespeichert.
https://bugs.kde.org/show_bug.cgi?id=405618 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.
[amarok] [Bug 405603] Local Collection does't scan files with special characters or accents (latin)
https://bugs.kde.org/show_bug.cgi?id=405603 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #4 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.
[okular] [Bug 406646] New: Okular Can not really change page color
https://bugs.kde.org/show_bug.cgi?id=406646 Bug ID: 406646 Summary: Okular Can not really change page color Product: okular Version: 1.6.3 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: PDF backend Assignee: okular-de...@kde.org Reporter: widon1...@qq.com Target Milestone: --- Created attachment 119477 --> https://bugs.kde.org/attachment.cgi?id=119477=edit Can not really change page color SUMMARY I want to change the page color to light yellow to relieve eye fatigue, but I find out the page color do not really change. In attached file, I change the page color to green, but only left and right side change the color to green, the part has words do not change at all. This behavior make 'change page color' useless I think. If I choose 'reverse color' the whole backgroud change and the words color become white. so I think 'change page color' is practicable. STEPS TO REPRODUCE 1. Configure Okular->Accessibility->Change colors->Change page color 2. Choose a color you like OBSERVED RESULT The page color do not really change, important part of the page's color do not change. EXPECTED RESULT whole page color change to color I set SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 399585] Enabling Windows 8+ pointer input breaks middle button actions
https://bugs.kde.org/show_bug.cgi?id=399585 --- Comment #5 from Tyson Tan --- Hi Dmitry! Thank you for the patch and I've tested it on Windows 10 1809 with Cintiq Pro 13 and Intuos Pro 2 M. Both the drivers and Krita have their Windows Ink enabled. Sadly it didn't work as intended for me. 1) The good part is the mouse event seems to be recognized by Krita: # Tablet Tester Information BEGIN Pen tip brought near Mouse press X=73 Y=127 B=4 Mouse move X=74 Y=127 B=4 Mouse move X=75 Y=127 B=4 Mouse move X=75 Y=128 B=4 Mouse move X=75 Y=129 B=4 Mouse move X=74 Y=129 B=4 Mouse move X=74 Y=130 B=4 Mouse move X=74 Y=129 B=4 Mouse move X=75 Y=129 B=4 Mouse release Pen tip taken away Pen tip brought near Pen tip taken away # Tablet Tester Information END 2) But for some reason Krita wouldn't pan the canvas according to most of my attempts. 3) For the roughly 1/30 chance when the canvas managed to pan, I could not stop it by releasing the middle button. And then I was stuck under the panning state, none of the stylus's buttons worked. I had to use my mouse's middle button to snap out of it. 4) Although I have no idea how it works, is it possible that Krita expects the mouse cursor to stay still while pressing the middle button here? It was the only human random factor in this test, I think. -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 406587] Autodrop stops in freecell
https://bugs.kde.org/show_bug.cgi?id=406587 --- Comment #2 from Duncan Kinnear --- Created attachment 119476 --> https://bugs.kde.org/attachment.cgi?id=119476=edit SAved Freecell game with stuck autodrop This saved game is stuck with it's autodrop. I had to 'restart' autodrop by clicking on a card four times after this point. -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 406645] yaml diagnostics export
https://bugs.kde.org/show_bug.cgi?id=406645 --- Comment #1 from chg...@gmail.com --- See https://github.com/llvm-mirror/clang-tools-extra/blob/master/clang-tidy/ClangTidy.cpp#L593 -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 406645] New: yaml diagnostics export
https://bugs.kde.org/show_bug.cgi?id=406645 Bug ID: 406645 Summary: yaml diagnostics export Product: clazy Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: chg...@gmail.com CC: smart...@kde.org Target Milestone: --- It would be nice if clazy could export the fixes in the same format as clang-tidy: -export-fixes= - YAML file to store suggested fixes in. The stored fixes can be applied to the input source code with clang-apply-replacements. This "fixes" database is more a diagnostic databse, as it contains entry for diagnostic even if they don't have fixits. -- You are receiving this mail because: You are watching all bug changes.
[sweeper] [Bug 406644] Sweeper launch from Desktop
https://bugs.kde.org/show_bug.cgi?id=406644 Sete changed: What|Removed |Added CC||jolug...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[sweeper] [Bug 406644] New: Sweeper launch from Desktop
https://bugs.kde.org/show_bug.cgi?id=406644 Bug ID: 406644 Summary: Sweeper launch from Desktop Product: sweeper Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: jolug...@gmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Copy application icon/launcher from System Menu to Desktop 2. Launch application from the link in the Desktop 3. Clic on "Clean Up" button OBSERVED RESULT Nothing happens. It doesn't work. After that it doesn't respond to close application button. You need to kill the application. EXPECTED RESULT Cleaning and messages about the result. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Manjaro KDE (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.
[kmymoney] [Bug 401397] kmymoney changes group permissions
https://bugs.kde.org/show_bug.cgi?id=401397 --- Comment #2 from bu...@pobox.com --- well, when i went to attach a patch it said to use phabricator, so i submitted a patch here: https://phabricator.kde.org/D20646 hope that's useful -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 406642] KDE Global Shortcuts service crashes on each start up (seg fault)
https://bugs.kde.org/show_bug.cgi?id=406642 --- Comment #3 from Tim Richardson --- Created attachment 119475 --> https://bugs.kde.org/attachment.cgi?id=119475=edit settings file causing segfault this settings file now causes a segfault for kglobalaccel when session starts. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 406642] KDE Global Shortcuts service crashes on each start up (seg fault)
https://bugs.kde.org/show_bug.cgi?id=406642 --- Comment #2 from Tim Richardson --- Delete ~/.config/kglobalshortcutsrc and restarting stopped the crashing. I have attached the settings I did have, which were causing the problem (apparently) after the 5.57 release. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 401397] kmymoney changes group permissions
https://bugs.kde.org/show_bug.cgi?id=401397 bu...@pobox.com changed: What|Removed |Added CC||bu...@pobox.com --- Comment #1 from bu...@pobox.com --- same here it seems like the XMLStorage plugin sets the permissions to be QFileDevice::ReadUser | QFileDevice::WriteUser at https://cgit.kde.org/kmymoney.git/tree/kmymoney/plugins/xml/xmlstorage.cpp#n524 formerly, this was done: QFileInfo info(file); ... m_fmode = QFileDevice::ReadUser | QFileDevice::WriteUser; m_fmode |= info.permissions(); at https://cgit.kde.org/kmymoney.git/tree/kmymoney/views/kmymoneyview.cpp?h=v5.0.1#n746 i'll attach a patch, though i don't have the local build environment to check to see if it either compiles or does what it's supposed to -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 406642] KDE Global Shortcuts service crashes on each start up (seg fault)
https://bugs.kde.org/show_bug.cgi?id=406642 --- Comment #1 from Tim Richardson --- running kglobalaccel5 in a shell after login restores shortcuts. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 406642] KDE Global Shortcuts service crashes on each start up (seg fault)
https://bugs.kde.org/show_bug.cgi?id=406642 Tim Richardson changed: What|Removed |Added Assignee|notm...@gmail.com |kdelibs-b...@kde.org Component|libplasma |general Product|frameworks-plasma |frameworks-kglobalaccel -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 405591] Plasmoid's tool-tip information should be displayed on mouse hover
https://bugs.kde.org/show_bug.cgi?id=405591 --- Comment #11 from emili...@gmail.com --- (In reply to Michail Vourlakos from comment #10) > (In reply to emilianh from comment #8) > > Created attachment 119467 [details] > > Screenshot of dock with System Load Viewer not showing it's tooltip > > > > Thanks, that fixed the systray. > > > > Unfortunately, I noticed that System Load Viewer (this time in a dock) is > > affected too :(, and for this dock I can't turn off the "Show title tooltips > > when hovering" option. > > > > lock it from applet tooltip Ah rigth, sorry, rearrange was off and it was missing the config and lock buttons in the tooltip. All good now. Thanks again. -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 406587] Autodrop stops in freecell
https://bugs.kde.org/show_bug.cgi?id=406587 --- Comment #1 from Duncan Kinnear --- Created attachment 119474 --> https://bugs.kde.org/attachment.cgi?id=119474=edit Example where autodrop stops At this point if I double-click the nine of spades, the rest completes automatically without stopping. I had not used undo in this game. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 406578] More general Access Counts
https://bugs.kde.org/show_bug.cgi?id=406578
--- Comment #2 from Andrew ---
(In reply to Nick Nethercote from comment #1)
> Valgrind 3.15 just came out and it completely overhauled DHAT. The new
> version is much better.
>
> The output is now in a tree. The root node of the tree covers the entire
> program, and looks like this:
>
> > AP 1/1 (25 children) {
> > Total: 1,355,253,987 bytes (100%, 67,454.81/Minstr) in 5,943,417
> > blocks (100%, 295.82/Minstr), avg size 228.03 bytes, avg lifetime
> > 3,134,692,250.67 instrs (15.6% of program duration)
> > At t-gmax: 423,930,307 bytes (100%) in 1,575,682 blocks (100%), avg size
> > 269.05 bytes
> > At t-end: 258,002 bytes (100%) in 2,129 blocks (100%), avg size 121.18
> > bytes
> > Reads: 5,478,606,988 bytes (100%, 272,685.7/Minstr), 4.04/byte
> > Writes:2,040,294,800 bytes (100%, 101,551.22/Minstr), 1.51/byte
> > Allocated at {
> > #0: [root]
> > }
> > }
>
> I'm not sure I understand exactly what you're asking for, but:
> - "how many times was an allocator accessed" might be the "5,943,417 blocks"
> part
> - "What is the read count of any width at any offset across all of blocks"
> might be the "Reads: 5,478,606,988 bytes" part, though that's a byte
> count rather than a read count.
>
> Does that help?
Thanks! I glanced at the changelog for DHAT yesterday and noticed all the
overhauls. I will upgrade ahead of cannocial's repos at my earliest
convenience.
Perhaps I was being confusing by describing what I want in two different ways.
The "5,478,606,988 bytes" part is very close to what I want to know, though as
you point out it's a byte count rather than a read count. I am currently
designing a tool that puts wrappers around every read and write, so the access
count is more important to me than the number of bytes accessed.
I know the development team historically has been looking for feedback on what
people want to use DHAT for, so I figured I would open this feature request if
only for informational purposes.
--
You are receiving this mail because:
You are watching all bug changes.
[k3b] [Bug 406622] during burning iso does not show progress
https://bugs.kde.org/show_bug.cgi?id=406622 --- Comment #2 from Giuliano --- Created attachment 119473 --> https://bugs.kde.org/attachment.cgi?id=119473=edit 3 screenshots I made an additional trial (with a rw disc): this time the progress indicator blocked in between. Attached are the screenshots I could take. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 406643] New: A clumsy alignment on Document Information widget
https://bugs.kde.org/show_bug.cgi?id=406643 Bug ID: 406643 Summary: A clumsy alignment on Document Information widget Product: krita Version: nightly build (please specify the git hash!) Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: libreaj...@gmail.com Target Milestone: --- Created attachment 119472 --> https://bugs.kde.org/attachment.cgi?id=119472=edit the screenshot of the bug SUMMARY Document Information widget looks very well with English but It is a bit glitchy on other languages. STEPS TO REPRODUCE 1. Change UI language. 2. Open a document. 3. Choose File - Document Information - Author A screenshot has been shared. Krita Version: 4.2.0-pre-alpha (Via PPA) Languages: en Hidpi: true Qt Version (compiled): 5.9.5 Version (loaded): 5.9.5 OS Information Build ABI: x86_64-little_endian-lp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: linux Kernel Version: 4.15.0-48-lowlatency Pretty Productname: Ubuntu 18.04.2 LTS Product Type: ubuntu Product Version: 18.04 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 406578] More general Access Counts
https://bugs.kde.org/show_bug.cgi?id=406578
--- Comment #1 from Nick Nethercote ---
Valgrind 3.15 just came out and it completely overhauled DHAT. The new version
is much better.
The output is now in a tree. The root node of the tree covers the entire
program, and looks like this:
> AP 1/1 (25 children) {
> Total: 1,355,253,987 bytes (100%, 67,454.81/Minstr) in 5,943,417 blocks
> (100%, 295.82/Minstr), avg size 228.03 bytes, avg lifetime 3,134,692,250.67
> instrs (15.6% of program duration)
> At t-gmax: 423,930,307 bytes (100%) in 1,575,682 blocks (100%), avg size
> 269.05 bytes
> At t-end: 258,002 bytes (100%) in 2,129 blocks (100%), avg size 121.18
> bytes
> Reads: 5,478,606,988 bytes (100%, 272,685.7/Minstr), 4.04/byte
> Writes:2,040,294,800 bytes (100%, 101,551.22/Minstr), 1.51/byte
> Allocated at {
> #0: [root]
> }
> }
I'm not sure I understand exactly what you're asking for, but:
- "how many times was an allocator accessed" might be the "5,943,417 blocks"
part
- "What is the read count of any width at any offset across all of blocks"
might be the "Reads: 5,478,606,988 bytes" part, though that's a byte count
rather than a read count.
Does that help?
--
You are receiving this mail because:
You are watching all bug changes.
[kdelibs] [Bug 165044] Dolphin can't handle well files/folders with wrong encoding
https://bugs.kde.org/show_bug.cgi?id=165044 Nathan Shearer changed: What|Removed |Added CC||kde-20091112@nathanshearer. ||ca --- Comment #166 from Nathan Shearer --- I just extracted an archive which contained a file that I could not copy/edit/move/rename/delete with dolphin. The file was simple readme file inside a nested subdirectory called L'$'\351''ame.html' The error messages in dolphin were extremely vague and did not indicate in an way that KDE and QT are incapable by design of handling files with these encoding. They did not inform the user why the file was causing these problems or even hint that they needed to be renamed in a terminal because of a WONTFIX on this bug. The only reason I knew what to do is because I encountered this bug years ago when operations on these files actually worked. Any normal user will have absolutely no idea what to do, and higher level systems will not handle these failures gracefully when these directory structures can't be modified because of a simple filename. The file or folder L'$'\351''ame.html' does not exist. - This is _false_ it does exist! Could not delete file L'$'\351''ame.html'. - No reason provided whatsoever. The user will not know how to solve this problem. Could not remove folder "". - All other files deleted, but the nested file was ignored leaving the user confused. This is ridiculous. It might be a lot of work, but a solution to this problem would be to store these strings as a tuple, where there is a degraded and user-friendly version of the string and the original unmodified string. If no changes are made to the string, use the original unmodified string. If the user decides to change the string, then they are interacting with the degraded version and deciding to keep that new string. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 404860] Tablet pressure not working in hidpi
https://bugs.kde.org/show_bug.cgi?id=404860 --- Comment #7 from Davide Baldo --- Hi Dimitry, I just tested it and works like a charm! :) Thank you -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 406642] New: KDE Global Shortcuts service crashes on each start up (seg fault)
https://bugs.kde.org/show_bug.cgi?id=406642 Bug ID: 406642 Summary: KDE Global Shortcuts service crashes on each start up (seg fault) Product: frameworks-plasma Version: 5.57.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: libplasma Assignee: notm...@gmail.com Reporter: t...@growthpath.com.au Target Milestone: --- SUMMARY KDE Global Shortcuts service crashes on each start up (seg fault) Some keyboard shortcuts are not working (alt-space, alt-F2) and some are, not sure if this is related or not. STEPS TO REPRODUCE 1. Restart desktop session 2. 3. OBSERVED RESULT Error message in panel tray. EXPECTED RESULT SOFTWARE/OS VERSIONS KDE Neon ADDITIONAL INFORMATION Executable: kglobalaccel5 PID: 3031 Signal: Segmentation fault (11) Time: 18/04/2019 07:38:40 Application: KDE Global Shortcuts Service (kglobalaccel5), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f1120f27800 (LWP 3031))] Thread 3 (Thread 0x7f1108061700 (LWP 3047)): #0 0x7f111eefdbf9 in __GI___poll (fds=0x7f11000182b0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f111ba4c539 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f111ba4c64c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f111f84015b in QEventDispatcherGlib::processEvents (this=0x7f110b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #4 0x7f111f7e164a in QEventLoop::exec (this=this@entry=0x7f1108060d70, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #5 0x7f111f60941a in QThread::exec (this=this@entry=0x7f111e761d80 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread.cpp:531 #6 0x7f111e4ea015 in QDBusConnectionManager::run (this=0x7f111e761d80 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:178 #7 0x7f111f60abc2 in QThreadPrivate::start (arg=0x7f111e761d80 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:361 #8 0x7f111db306db in start_thread (arg=0x7f1108061700) at pthread_create.c:463 #9 0x7f111ef0a88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7f1114a99700 (LWP 3034)): #0 0x7f111eefdbf9 in __GI___poll (fds=0x7f1114a98cb8, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f111ad39747 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f111ad3b36a in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7f111601432a in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7f111f60abc2 in QThreadPrivate::start (arg=0x55eb9c4db1b0) at thread/qthread_unix.cpp:361 #5 0x7f111db306db in start_thread (arg=0x7f1114a99700) at pthread_create.c:463 #6 0x7f111ef0a88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7f1120f27800 (LWP 3031)): [KCrash Handler] #6 GlobalShortcut::isPresent (this=this@entry=0x34002e0031003a) at ./src/runtime/globalshortcut.cpp:106 #7 0x7f1120b41af0 in KdeDGlobalAccel::Component::cleanUp (this=0x55eb9c55b530) at ./src/runtime/component.cpp:166 #8 0x7f1120b4a99b in KdeDGlobalAccel::Component::qt_static_metacall (_o=_o@entry=0x55eb9c55b530, _c=_c@entry=QMetaObject::InvokeMetaMethod, _id=_id@entry=1, _a=_a@entry=0x7ffc59fca950) at ./obj-x86_64-linux-gnu/src/runtime/KF5GlobalAccelPrivate_autogen/EWIEGA46WW/moc_component.cpp:130 #9 0x7f1120b4ad85 in KdeDGlobalAccel::Component::qt_metacall (this=0x55eb9c55b530, _c=QMetaObject::InvokeMetaMethod, _id=1, _a=0x7ffc59fca950) at ./obj-x86_64-linux-gnu/src/runtime/KF5GlobalAccelPrivate_autogen/EWIEGA46WW/moc_component.cpp:205 #10 0x7f111e4f5128 in QDBusConnectionPrivate::deliverCall (this=this@entry=0x7f1185e0, object=object@entry=0x55eb9c55b530, msg=..., metaTypes=..., slotIdx=) at qdbusintegrator.cpp:991 #11 0x7f111e4f9f80 in QDBusConnectionPrivate::activateCall (this=this@entry=0x7f1185e0, object=0x55eb9c55b530, flags=240, msg=...) at qdbusintegrator.cpp:894 #12 0x7f111e4fa467 in QDBusConnectionPrivate::activateCall (msg=..., flags=, object=, this=0x7f1185e0) at qdbusintegrator.cpp:843 #13 QDBusConnectionPrivate::activateObject (this=0x7f1185e0, node=..., msg=..., pathStartPos=) at qdbusintegrator.cpp:1501 #14 0x7f111e4fcf1e in QDBusActivateObjectEvent::placeMetaCall (this=0x7f1100013350) at qdbusintegrator.cpp:1597 #15 0x7f111f813992 in QObject::event (this=0x55eb9c55b530, e=) at kernel/qobject.cpp:1249 #16 0x7f111f7e3328 in QCoreApplication::notifyInternal2 (receiver=0x55eb9c55b530, event=0x7f1100013350) at kernel/qcoreapplication.cpp:1061 #17 0x7f111f7e34fe in
[krita] [Bug 406641] When I use the transformer tool it turned the thing I was drawing invisible. (note) I am using windows 10 32 Bit.
https://bugs.kde.org/show_bug.cgi?id=406641 Boudewijn Rempt changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO CC||b...@valdyas.org Platform|Other |MS Windows --- Comment #1 from Boudewijn Rempt --- Hi Caleb, Unfortunately, your report does not give us enough information to figure out what might be up. Please add the following: * an exact sequence of actions needed to reproduce the issue * a screenshot of the actual issue * a report of whether using the latest nightly build still has the same issue for you (https://binary-factory.kde.org/job/Krita_Nightly_Windows_Build/) * if it is still reproducible, the information from Help/System Information for Bug Reports as an attachment or comment to this bug report. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 406641] New: When I use the transformer tool it turned the thing I was drawing invisible. (note) I am using windows 10 32 Bit.
https://bugs.kde.org/show_bug.cgi?id=406641 Bug ID: 406641 Summary: When I use the transformer tool it turned the thing I was drawing invisible. (note) I am using windows 10 32 Bit. Product: krita Version: 4.1.7 Platform: Other OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: Tools/Transform Assignee: krita-bugs-n...@kde.org Reporter: calebt...@gmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 391445] Bold fonts set in profile settings are not applied after restarting konsole
https://bugs.kde.org/show_bug.cgi?id=391445 Mariusz Glebocki changed: What|Removed |Added URL|http://www.gruz-profmaster. | |ru | CC||m...@arccos-1.net -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 406640] New: Graph not displaying correctly with coreboot
https://bugs.kde.org/show_bug.cgi?id=406640 Bug ID: 406640 Summary: Graph not displaying correctly with coreboot Product: kinfocenter Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Energy Information Assignee: k...@privat.broulik.de Reporter: pepk...@gmail.com Target Milestone: --- Created attachment 119471 --> https://bugs.kde.org/attachment.cgi?id=119471=edit one of tabs which is messed up SUMMARY After flashing coreboot my power usage and charge percentage charts are messed up. Maybe it's unrelated or maybe ACPI behaves differently on corebooted hardware. I don't really want to flash stock as I would have to take my laptop apart to tiny bits to revert from OEM firmware. This may be important, kinfocenter claims that I'm using power supply which is incorrect, battery applet claims that I'm using battery which is correct. Or am I misinterpreting stuff? STEPS TO REPRODUCE 1. Go to kinfocenter 2. Select "Energy information" 3. Graphs are not displayed correctly OBSERVED RESULT As in attachment SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.15.4 KDE Frameworks Version: 5.56.0 Qt Version: 5.12.2 Kernel Version: 5.0.7-zen1-1-zen OS Type: 64-bit Processors: 8 × Intel® Core™ i7-3720QM CPU @ 2.60GHz Memory: 15,5 GiB of RAM ADDITIONAL INFORMATION Corebooted T430 Full design capacity might be skewed as this battery pack is designed for 94Wh. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406639] New: Disabling Full Screen -> crash
https://bugs.kde.org/show_bug.cgi?id=406639 Bug ID: 406639 Summary: Disabling Full Screen -> crash Product: kwin Version: 5.13.5 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: saleebm...@aol.com Target Milestone: --- Application: kwin_x11 (5.13.5) Qt Version: 5.11.1 Frameworks Version: 5.50.0 Operating System: Linux 4.18.0-17-generic x86_64 Distribution: Ubuntu 18.10 -- Information about the crash: - What I was doing when the application crashed: I have VMware openning in full screen automatically. It was open, then I ran my VM in full screen, closes the VM successfully, then on the VMware workstation itself, I used their option to disable full screen. Then it crashed. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f3a15734840 (LWP 5242))] Thread 7 (Thread 0x7f3a0e653700 (LWP 20179)): #0 0x7f3a1fd1f7d6 in __GI_ppoll (fds=0x7f3a3568, nfds=1, timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39 #1 0x7f3a1e8c0141 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f3a1e8c15b9 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f3a1e87116b in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f3a1e6c00b6 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f3a1cd2b1f5 in () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #6 0x7f3a1e6c9c87 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f3a1d4fa164 in start_thread (arg=) at pthread_create.c:486 #8 0x7f3a1fd2bdef in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 6 (Thread 0x7f39efb3f700 (LWP 16881)): #0 0x7f3a1fd1f7d6 in __GI_ppoll (fds=0x7f39640383f8, nfds=1, timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39 #1 0x7f3a1e8c0141 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f3a1e8c15b9 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f3a1e87116b in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f3a1e6c00b6 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f3a1cd2b1f5 in () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #6 0x7f3a1e6c9c87 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f3a1d4fa164 in start_thread (arg=) at pthread_create.c:486 #8 0x7f3a1fd2bdef in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7f3a0d8b9700 (LWP 11984)): #0 0x7f3a1fd1f7d6 in __GI_ppoll (fds=0x7f3a04003298, nfds=1, timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39 #1 0x7f3a1e8c0141 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f3a1e8c15b9 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f3a1e87116b in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f3a1e6c00b6 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f3a1e6c9c87 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f3a1d4fa164 in start_thread (arg=) at pthread_create.c:486 #7 0x7f3a1fd2bdef in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7f39f5207700 (LWP 5293)): #0 0x7f3a1d5002eb in futex_wait_cancelable (private=, expected=0, futex_word=0x7f3a1e2ddfb8) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f3a1d5002eb in __pthread_cond_wait_common (abstime=0x0, mutex=0x7f3a1e2ddf68, cond=0x7f3a1e2ddf90) at pthread_cond_wait.c:502 #2 0x7f3a1d5002eb in __pthread_cond_wait (cond=0x7f3a1e2ddf90, mutex=0x7f3a1e2ddf68) at pthread_cond_wait.c:655 #3 0x7f3a1e1e6e2a in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #4 0x7f3a1e1e6e49 in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #5 0x7f3a1d4fa164 in start_thread (arg=) at pthread_create.c:486 #6 0x7f3a1fd2bdef in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7f39fc973700 (LWP 5287)): #0 0x7f3a1fd1f7d6 in __GI_ppoll (fds=0x7f39f8000d28, nfds=1, timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39 #1 0x7f3a1e8c0141 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f3a1e8c15b9 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3
[dolphin] [Bug 405780] "Create New..." button can't appear in the toolbar
https://bugs.kde.org/show_bug.cgi?id=405780
--- Comment #4 from Nate Graham ---
with git bisect, I found that this broke with
https://cgit.kde.org/dolphin.git/commit/?id=dec7016c0d52129340a5b47f6de4df8af5115e21
Specifically, this bit:
diff --git a/src/dolphinmainwindow.cpp b/src/dolphinmainwindow.cpp
index 3e3803d..a93405f 100644
--- a/src/dolphinmainwindow.cpp
+++ b/src/dolphinmainwindow.cpp
@@ -1066,6 +1066,7 @@ void DolphinMainWindow::setupActions()
{
// setup 'File' menu
m_newFileMenu = new DolphinNewFileMenu(actionCollection(), this);
+m_newFileMenu->setObjectName("newFileMenu");
QMenu* menu = m_newFileMenu->menu();
menu->setTitle(i18nc("@title:menu Create new folder, file, link, etc.",
"Create New"));
menu->setIcon(QIcon::fromTheme(QStringLiteral("document-new")));
--
You are receiving this mail because:
You are watching all bug changes.
[krita] [Bug 398122] Krita ignores pen pressure if is brought into focus with the same pen touch
https://bugs.kde.org/show_bug.cgi?id=398122 --- Comment #4 from Boudewijn Rempt --- Um, it's not _hard_. Just download the zip file, unpack to the desktop, start by double-clicking the krita lnk file and test. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 345836] Annotations in pdf documents should be automatically saved to a temporary file.
https://bugs.kde.org/show_bug.cgi?id=345836 Jim Garrison changed: What|Removed |Added CC||j...@garrison.cc -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 394267] Add auto save feature
https://bugs.kde.org/show_bug.cgi?id=394267 Jim Garrison changed: What|Removed |Added CC||j...@garrison.cc -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 398122] Krita ignores pen pressure if is brought into focus with the same pen touch
https://bugs.kde.org/show_bug.cgi?id=398122 --- Comment #3 from Antti Savolainen --- Sadly, that's not up to me. The bug was noticed by my girlfriend and I don't use a PC with windows. She's not up to trying experimental builds. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 406461] Can't update from V9 to V10
https://bugs.kde.org/show_bug.cgi?id=406461 --- Comment #6 from Maik Qualmann --- For me, the question is more, why your images were all gone now. It was possible to write-protect database by changing mount options through the update of Tumbleweed. But why should it have emptied the database? Presumably, it can no longer be determined. There is no backup in digiKam. With SQLite, only the 4 database files (*.db) need to be backed up. Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 383987] Flickr tool no longer authenticates to Flickr
https://bugs.kde.org/show_bug.cgi?id=383987 --- Comment #7 from Maik Qualmann --- I just tested the Flickr tool again. Add new access-> Browser opens-> enter credentials-> allow digiKam rights-> Flickr Tool is logged in. Uploading images works. Maik -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 405591] Plasmoid's tool-tip information should be displayed on mouse hover
https://bugs.kde.org/show_bug.cgi?id=405591 --- Comment #10 from Michail Vourlakos --- (In reply to emilianh from comment #8) > Created attachment 119467 [details] > Screenshot of dock with System Load Viewer not showing it's tooltip > > Thanks, that fixed the systray. > > Unfortunately, I noticed that System Load Viewer (this time in a dock) is > affected too :(, and for this dock I can't turn off the "Show title tooltips > when hovering" option. > lock it from applet tooltip -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 406638] New: Crash while running EKOS with simulated telescope and CCD
https://bugs.kde.org/show_bug.cgi?id=406638
Bug ID: 406638
Summary: Crash while running EKOS with simulated telescope and
CCD
Product: kstars
Version: 3.2.0
Platform: Kubuntu Packages
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: mutla...@ikarustech.com
Reporter: ella...@eskimo.com
Target Milestone: ---
Created attachment 119470
--> https://bugs.kde.org/attachment.cgi?id=119470=edit
GDB debug info
SUMMARY
I tried running a simulated observation using the version of kstars in the
mutlaqja/ppa, and it crashed, possibly while mousing around the UI.
STEPS TO REPRODUCE
Honestly it crashes 100% of the time I've attempted to do this, but at
different points each time.
1. Set up indi, including a simulated guide camera.
2. Start guiding in EKOS (or not).
3. Start an observation sequence (or not).
OBSERVED RESULT
Program terminated with signal SIGSEGV, Segmentation fault.
#0 bool FITSView::rescale(FITSZoom)::{lambda()#1}::operator()() const (__closure=0x4b21d10)
at ./kstars/fitsviewer/fitsview.cpp:603
603 ./kstars/fitsviewer/fitsview.cpp: No such file or directory.
EXPECTED RESULT
No sequence of 1's and 0's should result in a segmentation fault.
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Ubuntu 18.04.2 LTS on a Raspberry Pi 3
Kstars debian package: 6:3.2.0+201904141849~ubuntu18.04.1
ADDITIONAL INFORMATION
I have the core file if you'd like it.
(gdb) bt
#0 bool FITSView::rescale(FITSZoom)::{lambda()#1}::operator()() const (__closure=0x4b21d10)
at ./kstars/fitsviewer/fitsview.cpp:603
#1 QtConcurrent::StoredFunctorCall0(FITSZoom)::{lambda()#1}>::runFunctor() (this=0x4b21d00) at
/usr/include/arm-linux-gnueabihf/qt5/QtConcurrent/qtconcurrentstoredfunctioncall.h:70
#2 0x00633530 in QtConcurrent::RunFunctionTask::run (this=0x4b21d00)
at
/usr/include/arm-linux-gnueabihf/qt5/QtConcurrent/qtconcurrentrunbase.h:136
#3 0x756923c0 in ?? () from /usr/lib/arm-linux-gnueabihf/libQt5Core.so.5
#4 0x756943ce in ?? () from /usr/lib/arm-linux-gnueabihf/libQt5Core.so.5
#5 0x7526e614 in start_thread (arg=0x7b05109d) at pthread_create.c:463
#6 0x74e607fc in ?? () at ../sysdeps/unix/sysv/linux/arm/clone.S:73 from
/lib/arm-linux-gnueabihf/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
(gdb) info args
__closure = 0x4b21d10
(gdb) info locals
i = 1044
runningBuffer = 0x5a8fe308
scanLine =
buffer = 0x5a889008
this = 0x3c31390
bscale = 5.1254216397405914
j = 160
bzero = -1125.480092473646
buffer =
j =
this =
bscale =
bzero =
runningBuffer =
scanLine =
i =
--
You are receiving this mail because:
You are watching all bug changes.
[kphotoalbum] [Bug 406633] Cannot rate photos
https://bugs.kde.org/show_bug.cgi?id=406633 --- Comment #2 from james.hirsch...@quantitative-technologies.com --- kiconfinder rating gives: /usr/share/icons/breeze/emblems/16/rating.svg I had the impression that it was not giving a rating, even when I pressed keys 1-5, which I read about somewhere. But I did not confirm this for certain. On Wed, Apr 17, 2019 at 3:48 PM Johannes Zarl-Zierl < bugzilla_nore...@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=406633 > > Johannes Zarl-Zierl changed: > >What|Removed |Added > > > CC||johan...@zarl-zierl.at > > --- Comment #1 from Johannes Zarl-Zierl --- > We don't do anything fancy with the ratings widget, so my best guess is > that > the problem is a missing rating icon in your icon scheme. > > Can you verify if the icon "rating" is installed? An easy way to do this > is by > running the command "kiconfinder rating". The command should print > something > like "/usr/share/icons/breeze-dark/emblems/22/rating.svg" as result. > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 405780] "Create New..." button can't appear in the toolbar
https://bugs.kde.org/show_bug.cgi?id=405780 Nate Graham changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||n...@kde.org Summary|"Create New..." button |"Create New..." button |can't be configured |can't appear in the toolbar --- Comment #3 from Nate Graham --- We have a report that this worked in 17.12.3, so it seems to have regressed recently. I'll see if I can figure out how and why. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 406637] Duplicates "Search in" Doesn't Show Collection Name Upon First Selection
https://bugs.kde.org/show_bug.cgi?id=406637 Maik Qualmann changed: What|Removed |Added Resolution|--- |FIXED CC||metzping...@gmail.com Status|REPORTED|RESOLVED Version Fixed In||6.2.0 --- Comment #1 from Maik Qualmann --- This problem is already fixed in digiKam-6.1.0. You can download a developer version here: https://files.kde.org/digikam/ Maik -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 406635] After adding 'Create New' to the toolbar via the toolbar configuration window, it doesn't actually appear on the toolbar
https://bugs.kde.org/show_bug.cgi?id=406635 Rog131 changed: What|Removed |Added Resolution|--- |DUPLICATE Status|CONFIRMED |RESOLVED CC||samrog...@hotmail.com --- Comment #4 from Rog131 --- *** This bug has been marked as a duplicate of bug 405780 *** -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 406633] Cannot rate photos
https://bugs.kde.org/show_bug.cgi?id=406633 Johannes Zarl-Zierl changed: What|Removed |Added CC||johan...@zarl-zierl.at --- Comment #1 from Johannes Zarl-Zierl --- We don't do anything fancy with the ratings widget, so my best guess is that the problem is a missing rating icon in your icon scheme. Can you verify if the icon "rating" is installed? An easy way to do this is by running the command "kiconfinder rating". The command should print something like "/usr/share/icons/breeze-dark/emblems/22/rating.svg" as result. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 405780] "Create New..." button can't be configured
https://bugs.kde.org/show_bug.cgi?id=405780 Rog131 changed: What|Removed |Added CC||bugs.kde@thebeach.plus. ||com --- Comment #2 from Rog131 --- *** Bug 406635 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406636] Security problem with Desktop Grid
https://bugs.kde.org/show_bug.cgi?id=406636 --- Comment #1 from Christoph Feck --- Bug 234153? -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 405591] Plasmoid's tool-tip information should be displayed on mouse hover
https://bugs.kde.org/show_bug.cgi?id=405591 --- Comment #9 from emili...@gmail.com --- Created attachment 119468 --> https://bugs.kde.org/attachment.cgi?id=119468=edit Image showing the original systray issue For completeness' sake I've also attached an image showing the initial Systray issue. (Show tooltips = OFF mode is now fixed) Thanks. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 405591] Plasmoid's tool-tip information should be displayed on mouse hover
https://bugs.kde.org/show_bug.cgi?id=405591 --- Comment #8 from emili...@gmail.com --- Created attachment 119467 --> https://bugs.kde.org/attachment.cgi?id=119467=edit Screenshot of dock with System Load Viewer not showing it's tooltip Thanks, that fixed the systray. Unfortunately, I noticed that System Load Viewer (this time in a dock) is affected too :(, and for this dock I can't turn off the "Show title tooltips when hovering" option. I've attached an image showing it when hovered by the mouse and also the configuration mode, hope it helps. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 368849] [WACOM] Krita does not react to Wacom Penabled tabletPC stylus's Top Barrel Button/2nd Switch mouse event on canvas
https://bugs.kde.org/show_bug.cgi?id=368849 --- Comment #13 from riceart --- I can confirm that this workaround works. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 406637] New: Duplicates "Search in" Doesn't Show Collection Name Upon First Selection
https://bugs.kde.org/show_bug.cgi?id=406637 Bug ID: 406637 Summary: Duplicates "Search in" Doesn't Show Collection Name Upon First Selection Product: digikam Version: 6.0.0 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: minor Priority: NOR Component: Searches Assignee: digikam-bugs-n...@kde.org Reporter: hardy.pub...@gmail.com Target Milestone: --- SUMMARY In Duplicates > Search in: > Albums dropdown box, I select a Collection. After selection, nothing is shown in the dropdown box. After toggling "Whole albums collection" checkbox the Collection name is now shown. OBSERVED RESULT No Collection name is shown EXPECTED RESULT Collection name to be shown upon first selection. SOFTWARE/OS VERSIONS Windows: 10 64bit -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 400154] Intuos 4 tablet wheel input for brush size results in "Ambiguous shortcut detected" dialog
https://bugs.kde.org/show_bug.cgi?id=400154 Dmitry Kazakov changed: What|Removed |Added CC||dimul...@gmail.com Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #5 from Dmitry Kazakov --- Hi, Michael! I guess this bug should also be fixed now after my commit I did just now: https://phabricator.kde.org/R37:fb089519cdae2c7cd0a1544c7fbdc6336b89c93f Please check nightly builds tomorrow evening, if you can still reproduce the bug or not :) https://binary-factory.kde.org/job/Krita_Nightly_Windows_Build/ If you still can reproduce the bug, please reopen the bug, so we could see it :) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 381452] Zooming using the Intuos 4 wheel not smooth while hovering pen over tablet
https://bugs.kde.org/show_bug.cgi?id=381452 Dmitry Kazakov changed: What|Removed |Added Latest Commit||https://commits.kde.org/kri ||ta/fb089519cdae2c7cd0a1544c ||7fbdc6336b89c93f Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #7 from Dmitry Kazakov --- Git commit fb089519cdae2c7cd0a1544c7fbdc6336b89c93f by Dmitry Kazakov. Committed on 17/04/2019 at 19:29. Pushed by dkazakov into branch 'master'. Fix hiccups when using wheel on the Wacom's tablets The tablet generates ctrl-down+wheel+ctrl-up group of events, so we shouldn't reset the accumulated wheen delta on every key and tablet move event. M +20 -1libs/ui/input/kis_input_manager.cpp https://commits.kde.org/krita/fb089519cdae2c7cd0a1544c7fbdc6336b89c93f -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406636] New: Security problem with Desktop Grid
https://bugs.kde.org/show_bug.cgi?id=406636 Bug ID: 406636 Summary: Security problem with Desktop Grid Product: kwin Version: 5.15.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: aleseco.f...@gmail.com Target Milestone: --- SUMMARY Security problem with Desktop Grid (ctrl +f8), no password required after wake-up STEPS TO REPRODUCE 1. Be sure your computer will lock or suspend automatically after n seconds and will ask your password at wake-up 2. Open Desktop Grid (ctrl+f8 by default) 3. Wait at least n+1 seconds (or close laptop lid) 4. Wake up your computer OBSERVED RESULT No password is required after wake up and desktop grid is still active. EXPECTED RESULT Lockscreen at least SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: linux 5.0.7.arch1-1 (available in About System) KDE Plasma Version: 5.15.4 KDE Frameworks Version: 5.56.1 Qt Version: 5.12.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 405591] Plasmoid's tool-tip information should be displayed on mouse hover
https://bugs.kde.org/show_bug.cgi?id=405591 Michail Vourlakos changed: What|Removed |Added Latest Commit||https://commits.kde.org/lat ||te-dock/f33b61d6cf8dad2b5ed ||a5137387073e7f0e02059 Resolution|NOT A BUG |FIXED --- Comment #7 from Michail Vourlakos --- Git commit f33b61d6cf8dad2b5eda5137387073e7f0e02059 by Michail Vourlakos. Committed on 17/04/2019 at 19:01. Pushed by mvourlakos into branch 'master'. simplify original applet behavior enablement --restores tooltips for systray when the Latte tooltips are not enabled M +1-2containment/package/contents/ui/applet/AppletItem.qml https://commits.kde.org/latte-dock/f33b61d6cf8dad2b5eda5137387073e7f0e02059 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 398959] Chromebook pen works but does not draw (draws in "Tablet Tester"!)
https://bugs.kde.org/show_bug.cgi?id=398959 wolthera changed: What|Removed |Added Severity|normal |wishlist CC||griffinval...@gmail.com --- Comment #10 from wolthera --- Setting this to wishlist until we have access to a testing device. :) -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 405591] Plasmoid's tool-tip information should be displayed on mouse hover
https://bugs.kde.org/show_bug.cgi?id=405591 --- Comment #6 from Michail Vourlakos --- (In reply to emilianh from comment #5) > (In reply to emilianh from comment #4) > > I noticed here the same issue happens with the System Tray, and AFAIKS > > there's no way to lock it, or to otherways get the correct behaviour. > > > > Gentoo Linux > > Qt: 5.12.2 > > KDE Frameworks: 5.56.0 > > KDE Plasma: 5.15.4 > > latte-dock latest from git (currently 9ce7ba35bb) > > > > Thanks. > > Forgot to add: > For the affected panel "Zoom on hover" is set to 0 and I've tried "Show > title tooltips" both on and off. > > Thanks Show me a screenshot of your systray please -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 369305] [HUION] Color picking alternate invocation gets stuck when un-focusing the Krita window
https://bugs.kde.org/show_bug.cgi?id=369305 Dmitry Kazakov changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||dimul...@gmail.com --- Comment #2 from Dmitry Kazakov --- Hah, I still can reproduce the problem... even after my recent tablet support refactoring. Let's fix it soon :) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 406426] kglobalaccel5 crashes often
https://bugs.kde.org/show_bug.cgi?id=406426 --- Comment #14 from Oded Arbel --- I would really love to testing the fix for this in Kubuntu CI unstable (which was last built April 12th). Anyone can kick the build job? I think its this one - http://kci.pangea.pub/job/disco_unstable_kglobalaccel , right? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 374336] Enable resettting tablet mapping in Krita after disabling or enabling a secondary display
https://bugs.kde.org/show_bug.cgi?id=374336 Dmitry Kazakov changed: What|Removed |Added Status|CONFIRMED |RESOLVED CC||dimul...@gmail.com Resolution|--- |FIXED --- Comment #6 from Dmitry Kazakov --- Hi, Neviril! I have just added automatic display resolution update in the Krita 4.2 PreAlpha. There is a special dialog in Preferences->Tablet->Wintab->Advanced that can let you configure tablet mapping without restarting Krita! Please test the nightly builds from here! :) https://binary-factory.kde.org/job/Krita_Nightly_Windows_Build/ If you still have a problem in the nightly builds, please reopen the bug the bug so we could see it :) -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 354248] Freehand annotation confuses tablet and touch events
https://bugs.kde.org/show_bug.cgi?id=354248 --- Comment #3 from Oliver Sander --- The patch you link to has been in Okular for a number of years. IIRC its state is 'discarded' because it was moved to phabricator for the final review. As for the trouble with freehand drawing: I have a half-finished patch that allows to disable mouse/touchscreen/stylus drawing separately, but I don't currently have time to finish it. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 387807] First brush stamp is 100% opaque if some pop-up is open
https://bugs.kde.org/show_bug.cgi?id=387807 Dmitry Kazakov changed: What|Removed |Added CC||dimul...@gmail.com Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #4 from Dmitry Kazakov --- Hi, radian! This bug has been fixed as part of huge tablet support refactoing we've just had in master. Please check the nightly builds :) https://binary-factory.kde.org/job/Krita_Nightly_Windows_Build/ If you see the problem still persist in the nightlies, please reopen the bug so we could see it in our queries :) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 395811] When painting on a CMYK image, the popup color picker's current color drifts
https://bugs.kde.org/show_bug.cgi?id=395811 Dmitry Kazakov changed: What|Removed |Added Status|CONFIRMED |NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #4 from Dmitry Kazakov --- Hi, def4ltkr4cked! Could you please check the latest nightly builds? I guess I have fixed this bug as part of HDR Project... https://binary-factory.kde.org/job/Krita_Nightly_Windows_Build/ -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 396034] After switching tools, quickly displaying PopUpPalette using Tablet buttons freezes tools.
https://bugs.kde.org/show_bug.cgi?id=396034 vanyossi changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #10 from vanyossi --- I no longer get this bug after 91963c577fad5adb226809fac4c00aeafb846128 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 395811] When painting on a CMYK image, the popup color picker's current color drifts
https://bugs.kde.org/show_bug.cgi?id=395811 Dmitry Kazakov changed: What|Removed |Added CC||dimul...@gmail.com Component|tablet support |Color Selectors --- Comment #3 from Dmitry Kazakov --- It is surely not a tablet bug. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 406617] Use .editorconfig and .kateconfig at the same time
https://bugs.kde.org/show_bug.cgi?id=406617 Nate Graham changed: What|Removed |Added CC||n...@kde.org, ||tcanabr...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 406624] dolphin titlebar garbled with baloosearch json query
https://bugs.kde.org/show_bug.cgi?id=406624 Nate Graham changed: What|Removed |Added CC||n...@kde.org Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from Nate Graham --- Hmm, I don't see this with Dolphin from 18.12.3 or git master, with either KDE Frameworks 5.56 or git master. Can you attach a screenshot please? -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 406627] UBUNTU 18.04 - Kate - would be nice to have more control in parameter for printouts
https://bugs.kde.org/show_bug.cgi?id=406627 Nate Graham changed: What|Removed |Added Resolution|--- |WAITINGFORINFO CC||n...@kde.org Status|REPORTED|NEEDSINFO --- Comment #1 from Nate Graham --- I'm afraid there's no information in this bug report. Please see https://community.kde.org/Get_Involved/Bug_Reporting -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 406632] Feature request for Discover
https://bugs.kde.org/show_bug.cgi?id=406632 Nate Graham changed: What|Removed |Added CC||n...@kde.org Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from Nate Graham --- What do yo mean by "interferes"? What are the symptoms of this interference? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 397143] Tablet resolution dialog cannot be forced to appear
https://bugs.kde.org/show_bug.cgi?id=397143 Dmitry Kazakov changed: What|Removed |Added Status|CONFIRMED |RESOLVED CC||dimul...@gmail.com Resolution|--- |FIXED --- Comment #1 from Dmitry Kazakov --- This dialog is now moved to the Preferences dialog, so let's close this bug :) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 406630] "Properties" window says "Device usage" while you are seeing the usage of a partition
https://bugs.kde.org/show_bug.cgi?id=406630 Nate Graham changed: What|Removed |Added Version|18.12.3 |unspecified Keywords||usability Ever confirmed|0 |1 Assignee|dolphin-bugs-n...@kde.org |fa...@kde.org CC||kdelibs-b...@kde.org, ||n...@kde.org Component|general |Properties dialog Status|REPORTED|CONFIRMED Product|dolphin |frameworks-kio --- Comment #1 from Nate Graham --- This dialog comes from KIO; moving there. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 401322] Unable to click the canvas rotation button in the pop-up palette when in Hidpi mode.
https://bugs.kde.org/show_bug.cgi?id=401322 Dmitry Kazakov changed: What|Removed |Added Status|REPORTED|RESOLVED CC||dimul...@gmail.com Resolution|--- |FIXED --- Comment #5 from Dmitry Kazakov --- Hi, Tyler! Could you please check if the bug still persists in the nightly builds: https://binary-factory.kde.org/job/Krita_Nightly_Appimage_Build/ I have fixed the HiDPI handling on Linux, so now it should work fine now. If the bug is still present, please reopen the bug, so we could see it :) -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 406635] After adding 'Create New' to the toolbar via the toolbar configuration window, it doesn't actually appear on the toolbar
https://bugs.kde.org/show_bug.cgi?id=406635 Nate Graham changed: What|Removed |Added Keywords||junior-jobs, usability -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 406635] After adding 'Create New' to the toolbar via the toolbar configuration window, it doesn't actually appear on the toolbar
https://bugs.kde.org/show_bug.cgi?id=406635 Nate Graham changed: What|Removed |Added Summary|[Dolphin] Unable to add|After adding 'Create New' |'Create New' to toolbar |to the toolbar via the ||toolbar configuration ||window, it doesn't actually ||appear on the toolbar -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 406629] Konsole needs either less tear-off sensativity or the ability to disable tear-off tabs
https://bugs.kde.org/show_bug.cgi?id=406629 Nate Graham changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED CC||n...@kde.org --- Comment #1 from Nate Graham --- I agree. Happily this has already been fixed in the upcoming 19.04 release (or possibly 19.04, can't recall which). -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 406635] [Dolphin] Unable to add 'Create New' to toolbar
https://bugs.kde.org/show_bug.cgi?id=406635 Nate Graham changed: What|Removed |Added Status|REPORTED|CONFIRMED CC||n...@kde.org Ever confirmed|0 |1 --- Comment #3 from Nate Graham --- Can reproduce. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 403465] Allow force-killing Discover even when there are pending tasks
https://bugs.kde.org/show_bug.cgi?id=403465 Nate Graham changed: What|Removed |Added Version Fixed In||5.16.0 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 406635] [Dolphin] Unable to add 'Create New' to toolbar
https://bugs.kde.org/show_bug.cgi?id=406635 mthw0 changed: What|Removed |Added CC||matejm98m...@gmail.com --- Comment #2 from mthw0 --- I also have this problem. SOFTWARE/OS VERSIONS Operating System: Arch Linux Dolphin Version: 19.03.90 KDE Plasma Version: 5.15.4 KDE Frameworks Version: 5.57.0 Qt Version: 5.13.0-beta1 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 403465] Allow force-killing Discover even when there are pending tasks
https://bugs.kde.org/show_bug.cgi?id=403465 Aleix Pol changed: What|Removed |Added Latest Commit||https://commits.kde.org/dis ||cover/3aadd3aa4c02bfa427050 ||e8933d32e063cecabff Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #3 from Aleix Pol --- Git commit 3aadd3aa4c02bfa427050e8933d32e063cecabff by Aleix Pol. Committed on 17/04/2019 at 18:09. Pushed by apol into branch 'master'. Allow to close Discover when there's ongoing jobs M +1-1discover/qml/DiscoverWindow.qml https://commits.kde.org/discover/3aadd3aa4c02bfa427050e8933d32e063cecabff -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 396034] After switching tools, quickly displaying PopUpPalette using Tablet buttons freezes tools.
https://bugs.kde.org/show_bug.cgi?id=396034 Dmitry Kazakov changed: What|Removed |Added CC||dimul...@gmail.com --- Comment #9 from Dmitry Kazakov --- It might be the same Enter/Leave problem that we just fixed on Windows and Linux... -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406593] Usability issue: destructive titlebar actions
https://bugs.kde.org/show_bug.cgi?id=406593 Nate Graham changed: What|Removed |Added CC||n...@kde.org Resolution|NOT A BUG |INTENTIONAL --- Comment #5 from Nate Graham --- (In reply to plane.wander from comment #4) > So it's ok if I submit a patch to add the same functionality back to the > present windows effect, because the reasons to remove it in the first place > aren't considered valid any more? I mean it has to be one or the other: > Either it's bad to have this sort of destructive actions to close windows or > it's fine as long as they are disabled by default. FWIW, I would support this, for just the reasoning you give. Makes sense to me, can't have it both ways. -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 406316] krdc distorts screen, when connecting with medium quality, and saturated GB ethernet in high quality
https://bugs.kde.org/show_bug.cgi?id=406316 Hans-Peter Jansen changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #3 from Hans-Peter Jansen --- Okay, tigervnc-1.9.0 was the culprit. After applying git master, all is well. For the record, the fixed package: https://build.opensuse.org/package/show/home:frispete:RemoteDesktop/tigervnc Sorry for the churn. Will report a few lesa impacting issues soon (that definitely origin from krdc ;-)) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 405747] Samsung Notebook 9 Pro/Pen S Pen (By Wacom) Eraser Button Not Working When Pressed In Proximity
https://bugs.kde.org/show_bug.cgi?id=405747 Dmitry Kazakov changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #12 from Dmitry Kazakov --- Marking as waitingforinfo -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 405747] Samsung Notebook 9 Pro/Pen S Pen (By Wacom) Eraser Button Not Working When Pressed In Proximity
https://bugs.kde.org/show_bug.cgi?id=405747 Dmitry Kazakov changed: What|Removed |Added Status|RESOLVED|REPORTED Resolution|FIXED |--- --- Comment #11 from Dmitry Kazakov --- Hi, Aster! Could you please test if this package fixes the problem for you? I have added a fix. https://yadi.sk/d/db3yUdmPLm8wAg -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 403682] Closing sliding of top left menu after startup of Discover in mobile width
https://bugs.kde.org/show_bug.cgi?id=403682 Aleix Pol changed: What|Removed |Added Latest Commit||https://commits.kde.org/dis ||cover/246ea726318282417bcdb ||7d6526521cd5a667c3d Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #3 from Aleix Pol --- Git commit 246ea726318282417bcdb7d6526521cd5a667c3d by Aleix Pol. Committed on 17/04/2019 at 18:01. Pushed by apol into branch 'master'. Improve startup sequence Don't the main window start in the default size and then arrange it into the saved geometry. Pass the width and height so the object is constructed with the correct sizes. This should solve some visual glitches at startup. M +6-0discover/DiscoverObject.cpp M +3-0discover/DiscoverObject.h M +2-0discover/qml/DiscoverWindow.qml https://commits.kde.org/discover/246ea726318282417bcdb7d6526521cd5a667c3d -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 368849] [WACOM] Krita does not react to Wacom Penabled tabletPC stylus's Top Barrel Button/2nd Switch mouse event on canvas
https://bugs.kde.org/show_bug.cgi?id=368849 Dmitry Kazakov changed: What|Removed |Added Resolution|--- |WAITINGFORINFO CC||dimul...@gmail.com Status|CONFIRMED |NEEDSINFO --- Comment #12 from Dmitry Kazakov --- Hi, all! Could you please test this package and check if the workaround fixes the problems you had? The patch affects both modes, Wintab and WinInk. https://yadi.sk/d/db3yUdmPLm8wAg 1) Unpack the package 2) Add to %LOCALAPPDATA%\kritarc: 'rightMiddleTabletButtonWorkaround=true' 3) Run Krita, if needed, activate WinInk or Wintab and restart 4) Test the problem -- You are receiving this mail because: You are watching all bug changes.
