[Falkon] [Bug 433181] Add Gemini support
https://bugs.kde.org/show_bug.cgi?id=433181 Anna changed: What|Removed |Added CC||cyber+...@sysrq.in Version|3.1.0 |23.08.5 --- Comment #3 from Anna --- Such plugins already exist: https://gitlab.com/tobiasrautenkranz/kio-gemini https://gitlab.com/tobiasrautenkranz/geminipart But Falkon doesn't support KPart framework and so unable to render proper Gemtext. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 485049] New: Latte Dock crashes randomly
https://bugs.kde.org/show_bug.cgi?id=485049 Bug ID: 485049 Summary: Latte Dock crashes randomly Classification: Plasma Product: lattedock Version: 0.10.8 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: potsa...@gmail.com Target Milestone: --- Application: latte-dock (0.10.8) Qt Version: 5.15.12 Frameworks Version: 5.115.0 Operating System: Linux 6.7.10-200.fc39.x86_64 x86_64 Windowing System: Wayland Distribution: "Fedora Linux 39 (KDE Plasma)" DrKonqi: 5.27.11 [KCrashBackend] -- Information about the crash: Latt Dock sometimes crashes randomly and prevents me from using my device The crash can be reproduced sometimes. -- Backtrace: Application: Latte Dock (latte-dock), signal: Segmentation fault [KCrash Handler] #4 0x7f42c90e6cb7 in QObjectPrivate::ConnectionData::resizeSignalVector(unsigned int) () from /lib64/libQt5Core.so.5 #5 0x7f42c90dc86f in QObjectPrivate::addConnection(int, QObjectPrivate::Connection*) () from /lib64/libQt5Core.so.5 #6 0x7f42c90e2559 in QObjectPrivate::connectImpl(QObject const*, int, QObject const*, void**, QtPrivate::QSlotObjectBase*, Qt::ConnectionType, int const*, QMetaObject const*) () from /lib64/libQt5Core.so.5 #7 0x7f42c90e29e0 in QObject::connectImpl(QObject const*, void**, QObject const*, void**, QtPrivate::QSlotObjectBase*, Qt::ConnectionType, int const*, QMetaObject const*) () from /lib64/libQt5Core.so.5 #8 0x7f42c9416a06 in KNSCore::Engine::loadProviders() () from /lib64/libKF5NewStuffCore.so.5 #9 0x7f42c9417e55 in KNSCore::Engine::init(QString const&) () from /lib64/libKF5NewStuffCore.so.5 #10 0x7f429698c09c in Engine::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) () from /usr/lib64/qt5/qml/org/kde/newstuff/libnewstuffqmlplugin.so #11 0x7f42cad1b562 in GenericBinding<10>::write(QV4::Value const&, bool, QFlags) () from /lib64/libQt5Qml.so.5 #12 0x7f42cad1be9d in QQmlNonbindingBinding::doUpdate(QQmlJavaScriptExpression::DeleteWatcher const&, QFlags, QV4::Scope&) () from /lib64/libQt5Qml.so.5 #13 0x7f42cad19615 in QQmlBinding::update(QFlags) () from /lib64/libQt5Qml.so.5 #14 0x7f42cad272a4 in QQmlObjectCreator::finalize(QQmlInstantiationInterrupt&) () from /lib64/libQt5Qml.so.5 #15 0x7f42cacb2be7 in QQmlComponentPrivate::complete(QQmlEnginePrivate*, QQmlComponentPrivate::ConstructionState*) () from /lib64/libQt5Qml.so.5 #16 0x7f42cacb4be9 in QQmlComponentPrivate::completeCreate() () from /lib64/libQt5Qml.so.5 #17 0x7f42cacb4d9a in QQmlComponent::create(QQmlContext*) () from /lib64/libQt5Qml.so.5 #18 0x7f42cb9aad8c in KNS3::QtQuickDialogWrapper::QtQuickDialogWrapper(QString const&, QObject*) () from /lib64/libKF5NewStuff.so.5 #19 0x7f42883a8355 in WidgetExplorer::downloadWidgets() () from /usr/lib64/qt5/qml/org/kde/plasma/private/shell/libplasmashellprivateplugin.so #20 0x7f42c90e9151 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #21 0x7f42c9fa7d44 in QAction::triggered(bool) () from /lib64/libQt5Widgets.so.5 #22 0x7f42c9faab9b in QAction::activate(QAction::ActionEvent) () from /lib64/libQt5Widgets.so.5 #23 0x7f42c9fab9b2 in QAction::qt_metacall(QMetaObject::Call, int, void**) () from /lib64/libQt5Widgets.so.5 #24 0x7f42883aea7e in WidgetAction::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/qt5/qml/org/kde/plasma/private/shell/libplasmashellprivateplugin.so #25 0x7f42cacf536a in QQmlObjectOrGadget::metacall(QMetaObject::Call, int, void**) const () from /lib64/libQt5Qml.so.5 #26 0x7f42cabc6840 in CallPrecise(QQmlObjectOrGadget const&, QQmlPropertyData const&, QV4::ExecutionEngine*, QV4::CallData*, QMetaObject::Call) () from /lib64/libQt5Qml.so.5 #27 0x7f42cabc9ad2 in QV4::QObjectMethod::callInternal(QV4::Value const*, QV4::Value const*, int) const () from /lib64/libQt5Qml.so.5 #28 0x7f42cabe760c in QV4::Moth::VME::interpret(QV4::CppStackFrame*, QV4::ExecutionEngine*, char const*) () from /lib64/libQt5Qml.so.5 #29 0x7f42cabeae2f in QV4::Moth::VME::exec(QV4::CppStackFrame*, QV4::ExecutionEngine*) () from /lib64/libQt5Qml.so.5 #30 0x7f42cab7ad02 in QV4::Function::call(QV4::Value const*, QV4::Value const*, int, QV4::ExecutionContext const*) () from /lib64/libQt5Qml.so.5 #31 0x7f42cad11040 in QQmlJavaScriptExpression::evaluate(QV4::CallData*, bool*) () from /lib64/libQt5Qml.so.5 #32 0x7f42cacbf5e1 in QQmlBoundSignalExpression::evaluate(void**) () from /lib64/libQt5Qml.so.5 #33 0x7f42cacc0860 in QQmlBoundSignal_callback(QQmlNotifierEndpoint*, void**) () from /lib64/libQt5Qml.so.5 #34 0x7f42cacf4e17 in QQmlNotifier::emitNotify(QQmlNotifierEndpoint*, void**) () from /lib64/libQt5Qml.so.5 #35 0x7f42c90e8e20 in void
[krita] [Bug 401800] Even so I enabled pen pressure, pen pressure is not working
https://bugs.kde.org/show_bug.cgi?id=401800 Anna Khin changed: What|Removed |Added CC||annaml...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 480544] New: Add password store backend for zx2c4's pass
https://bugs.kde.org/show_bug.cgi?id=480544 Bug ID: 480544 Summary: Add password store backend for zx2c4's pass Classification: Applications Product: Falkon Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: extensions Assignee: now...@gmail.com Reporter: cyber+...@sysrq.in Target Milestone: --- This is a feature request to support the "Unix-way" password store backend: https://www.passwordstore.org/ See also: * Plasma applet: https://invent.kde.org/plasma/plasma-pass * Extension for Firefox & Chrome: https://github.com/browserpass/browserpass-extension -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 477400] New: [Android] Blank settings page
https://bugs.kde.org/show_bug.cgi?id=477400 Bug ID: 477400 Summary: [Android] Blank settings page Classification: Applications Product: NeoChat Version: 23.08.3 Platform: Android OS: Android 13.x Status: REPORTED Severity: major Priority: NOR Component: General Assignee: fe...@posteo.de Reporter: cyber+...@sysrq.in CC: c...@carlschwan.eu Target Milestone: --- When I tap a settings button or start verification, a blank page opens. Both 23.08.2 and 23.11.70 nightly are affected. I can provide logcats if you provide instructions. -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 477047] Make QtLocation support optional
https://bugs.kde.org/show_bug.cgi?id=477047 Anna changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 477047] Make QtLocation support optional
https://bugs.kde.org/show_bug.cgi?id=477047 Anna changed: What|Removed |Added URL||https://bugs.gentoo.org/895 ||516 Platform|Other |Gentoo Packages -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 477047] Make QtLocation support optional
https://bugs.kde.org/show_bug.cgi?id=477047 Anna changed: What|Removed |Added See Also||https://bugreports.qt.io/br ||owse/QTBUG-116652 -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 477047] New: Make QtLocation support optional
https://bugs.kde.org/show_bug.cgi?id=477047 Bug ID: 477047 Summary: Make QtLocation support optional Classification: Applications Product: NeoChat Version: 23.08.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: fe...@posteo.de Reporter: cyber+...@sysrq.in CC: c...@carlschwan.eu Target Milestone: --- QtLocation 5.15.11 fails to build on Clang 16+ systems. See: https://bugreports.qt.io/browse/QTBUG-116652 https://bugs.gentoo.org/895516 -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 358663] Feature Request: Enable interface to Nextcloud News
https://bugs.kde.org/show_bug.cgi?id=358663 Anna changed: What|Removed |Added CC||anmeldun...@malte-gerth.de --- Comment #8 from Anna --- *** Bug 330472 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 330472] ownCloud News App support
https://bugs.kde.org/show_bug.cgi?id=330472 Anna changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |DUPLICATE CC||cyber+...@sysrq.in --- Comment #11 from Anna --- *** This bug has been marked as a duplicate of bug 358663 *** -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 358663] Feature Request: Enable interface to Nextcloud News
https://bugs.kde.org/show_bug.cgi?id=358663 Anna changed: What|Removed |Added CC||akse...@akselmo.dev --- Comment #7 from Anna --- *** Bug 457794 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 457794] Nextcloud News support
https://bugs.kde.org/show_bug.cgi?id=457794 Anna changed: What|Removed |Added Resolution|--- |DUPLICATE CC||cyber+...@sysrq.in Status|REPORTED|RESOLVED --- Comment #1 from Anna --- *** This bug has been marked as a duplicate of bug 358663 *** -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 358663] Feature Request: Enable interface to Nextcloud News
https://bugs.kde.org/show_bug.cgi?id=358663 Anna changed: What|Removed |Added Summary|Feature : Enable interface |Feature Request: Enable |to Nextcloud News |interface to Nextcloud News -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 358663] Feature : Enable interface to Nextcloud News
https://bugs.kde.org/show_bug.cgi?id=358663 Anna changed: What|Removed |Added Ever confirmed|0 |1 CC||cyber+...@sysrq.in Status|REPORTED|CONFIRMED Summary|New Feature: Enable |Feature : Enable interface |interface to Owncloud News |to Nextcloud News --- Comment #6 from Anna --- I'd like to have Nextcloud News support in Akregator. -- an RSS Guard user -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 476085] New: Filter out boosts and/or replies from home feed
https://bugs.kde.org/show_bug.cgi?id=476085 Bug ID: 476085 Summary: Filter out boosts and/or replies from home feed Classification: Applications Product: Tokodon Version: 23.08.2 Platform: Android OS: Android 13.x Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: cyber+...@sysrq.in CC: c...@carlschwan.eu, j...@redstrate.com Target Milestone: --- I miss a feature to hide replies from home feed, present in web ui or Tusky. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 449163] Plasma panel visually freezes after some time under Wayland
https://bugs.kde.org/show_bug.cgi?id=449163 Anna changed: What|Removed |Added CC||a...@witches.live --- Comment #53 from Anna --- While this issue has gotten more infrequent over the last monthish with regular bleeding edge updates, it still persists. Weirdly today it was acting strange before that, I would try to open dolphin by clicking a small icon next to my kde menu but it would minimize my running game of Final Fantasy XIV instead (hypothetically, and/or ACT as well) and while the panel is responsive, it has weird behavior sometimes and doesn't work as expected. Posting my system stats in case it helps, seems like this is happening to nvidia users overall (wayland problems in nvidia? whoda thunk?) Operating System: Gentoo Linux 2.13 KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.106.0 Qt Version: 5.15.9 Kernel Version: 6.3.6-gentoo (64-bit) Graphics Platform: Wayland Processors: 32 × AMD Ryzen 9 7950X 16-Core Processor Memory: 30.5 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 3080 Ti/PCIe/SSE2 Manufacturer: ASRock Product Name: X670E Steel Legend -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 407524] No way to provide keyboard focus to the global drawer
https://bugs.kde.org/show_bug.cgi?id=407524 Anna changed: What|Removed |Added CC||cyber+...@sysrq.in -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 470421] Avatar image doesn't load with QT_QUICK_BACKEND=software
https://bugs.kde.org/show_bug.cgi?id=470421 --- Comment #4 from Anna --- > Do you have a reason to use the software renderer? Yes, I connect to remote desktop over RDP. Hardware acceleration is not available, so OpenGL rendering is very slow. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 470421] Avatar image doesn't load with QT_QUICK_BACKEND=software
https://bugs.kde.org/show_bug.cgi?id=470421 --- Comment #2 from Anna --- Created attachment 159326 --> https://bugs.kde.org/attachment.cgi?id=159326=edit Screenshot -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 470421] Avatar image doesn't load with QT_QUICK_BACKEND=software
https://bugs.kde.org/show_bug.cgi?id=470421 Anna changed: What|Removed |Added Attachment #159325|0 |1 is obsolete|| -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 470421] Avatar image doesn't load with QT_QUICK_BACKEND=software
https://bugs.kde.org/show_bug.cgi?id=470421 --- Comment #1 from Anna --- Created attachment 159325 --> https://bugs.kde.org/attachment.cgi?id=159325=edit Screenshot -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 470421] New: Avatar image doesn't load with QT_QUICK_BACKEND=software
https://bugs.kde.org/show_bug.cgi?id=470421 Bug ID: 470421 Summary: Avatar image doesn't load with QT_QUICK_BACKEND=software Classification: Frameworks and Libraries Product: frameworks-kirigami Version: 5.106.0 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: cyber+...@sysrq.in CC: notm...@gmail.com Target Milestone: Not decided STEPS TO REPRODUCE Run: $ QT_QUICK_BACKEND=software neochat OBSERVED RESULT No avatar images. SOFTWARE/OS VERSIONS KDE Frameworks Version: 5.106.0 Qt Version: 5.15.9 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469016] Plasma panel visually (but not functionally) freezing with Wayland+Nvidia
https://bugs.kde.org/show_bug.cgi?id=469016 Anna changed: What|Removed |Added CC||a...@witches.live --- Comment #15 from Anna --- Confirming that this also happens to me on nvidia/wayland and while playing games is sometimes involved it's not always clear what causes it honestly -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 469505] New: Chromium applications in Wayland get increasingly slow and unresponsive and ultimately stop working
https://bugs.kde.org/show_bug.cgi?id=469505 Bug ID: 469505 Summary: Chromium applications in Wayland get increasingly slow and unresponsive and ultimately stop working Classification: I don't know Product: kde Version: unspecified Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: a...@witches.live Target Milestone: --- SUMMARY Applications that use a chromium backend such as discord and steam will be workable for a period of time, but after an indeterminate amount of time (sometimes an hour or two, sometimes far less, it seems to be more on how much you interact with it than time though it's kind of both) the application will become sluggish and unresponsive, and eventually will not change pages/views for whatever that means in the application, such as discord not changing servers/channels, steam not loading or getting stuck on various pages, a chromium-based idle game I play called Increlution will eventually stop loading some modals that e.g. show your progress on the last few runs. The current/stable version of Steam is nigh-unusable, though the linux beta update works a bit better for longer before freezing. Note that when the UI becomes responsive, the application doesn't seem to be wholly frozen. It feels like a cousin to a memory leak, like further and further delay is added to UI interactions and at some point it causes the UI to take an untenably long time to respond to input or stop it entirely, it's not clear. This only happens on Wayland it does not happen on X11. STEPS TO REPRODUCE 1. Run a wayland session 2. Launch Discord, steam, or some other chromium application 3. The longer you use it or the more you try to do, the worse it gets OBSERVED RESULT Chromium-based application becomes sluggish and unresponsive, and eventually needs to be restarted to work EXPECTED RESULT Chromium-based applications should continue to work responsively and well with extended use SOFTWARE/OS VERSIONS Linux/KDE Plasma: Gentoo Linux 2.13 linux-6.3.1-gentoo KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9 ADDITIONAL INFORMATION CPU: 32 × AMD Ryzen 9 7950X 16-Core Processor Memory: 32 GB DDR5 GPU: NVIDIA GeForce RTX 3080 Ti/PCIe/SSE2 Motherboard: ASRock X670E Steel Legend -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 469082] Freecell game modes automatically put unsafe cards on the foundation
https://bugs.kde.org/show_bug.cgi?id=469082 --- Comment #1 from Anna --- Minor correction: * it is necessary to have the 6, 5, and 4 of hearts available to stack other cards on. We end up manually putting the 3 on the foundation, but this particular deal doesn't necessitate holding the 2 of clubs at any point, especially since its at the bottom of a stack. -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 469082] Freecell game modes automatically put unsafe cards on the foundation
https://bugs.kde.org/show_bug.cgi?id=469082 Anna changed: What|Removed |Added Summary|Freecell game modes |Freecell game modes |automatically puts unsafe |automatically put unsafe |cards on the foundation |cards on the foundation -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 469082] Freecell game modes automatically puts unsafe cards on the foundation
https://bugs.kde.org/show_bug.cgi?id=469082 Anna changed: What|Removed |Added Summary|Solitare automatically puts |Freecell game modes |unsafe cards on the |automatically puts unsafe |foundation |cards on the foundation -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 469082] Solitare automatically puts unsafe cards on the foundation
https://bugs.kde.org/show_bug.cgi?id=469082 Anna changed: What|Removed |Added CC||a...@witches.live -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 469082] New: Solitare automatically puts unsafe cards on the foundation
https://bugs.kde.org/show_bug.cgi?id=469082 Bug ID: 469082 Summary: Solitare automatically puts unsafe cards on the foundation Classification: Applications Product: kpat Version: 23.04.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: co...@kde.org Reporter: a...@witches.live CC: kde-games-b...@kde.org Target Milestone: --- Created attachment 158499 --> https://bugs.kde.org/attachment.cgi?id=158499=edit Screenshot of the game state with manual undo to help any poor soul who feels compelled to follow the demonstration but can't load up kpatience to do it In all Freecell game modes, cards will automatically be put on the foundation if they are eligible, necessitating an undo action in some cases in order to be able to solve the game. Automatically putting cards on the foundations should only be done if there aren't any cards on the field that could be placed on top of that card that could not be placed on the foundation if it was uncovered. OBSERVED RESULT An excellent example of this is I recently did Forecell variant game 26184086, which immediately at the start of the game places the ace of hearts through the six of hearts onto the foundation. I was unable to win this game until I hit undo immediately at the game start and only allowed ace and 2 initially, as later in the game it is necessary to have the 5, 4, and 3 of hearts available to stack other cards on. I have attached an image of the game state after undoing to the safe level of only putting the 2 of hearts on the foundation (though you might want to play along if you want to follow this). You might observe that rather immediately, the six of hearts is useful for freeing the cell holding the 5 of spades, the five of hearts can be put on the six of spades, the four of hearts can be put on the 5 of spades, then the cell with the 3 of spades can be placed on that 4 to free a cell. Then the 8 of clubs can go on the 9 of hearts and the 7 of diamonds can be released. 3 of hearts can be (manually!) put on the foundation, 9 of clubs can go on 10 of hearts, and the final free cell can be freed by putting the six of diamonds on the 7 of clubs. This ultimately ends up leading to the solution to this game; I was unable to find one that works by placing all the way through the 6 of hearts at the beginning. EXPECTED RESULT In the aforementioned example, I shouldn't have had to undo any move, only the ace and 2 of hearts should have moved automatically. The 3 of hearts would not be eligible for automatically moving to the foundation until both the ace of clubs and spades are uncovered, as now both black 2 cards are eligible to be moved to the foundation so there's no possible situation the three of hearts might be necessary to solve the game. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Gentoo Linux 2.13 (Kernel 6.3.0) KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9 ADDITIONAL INFORMATION gentoo ebuild version of kpatience -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 456154] New: Krita crashes when pasting from Windows 11 Photo app
https://bugs.kde.org/show_bug.cgi?id=456154 Bug ID: 456154 Summary: Krita crashes when pasting from Windows 11 Photo app Product: krita Version: 5.0.6 Platform: Compiled Sources OS: All Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: deanna.green...@gmail.com Target Milestone: --- Krita now crashes when trying to paste from Windows 11 native Photos app. I have been able to do this in Krita for many years without any problem, until now. SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Open Krita 2. Copy photo from Windows 11 Photo App (either manually or ctrl+c) 3. Paste photo into Krita (either manually or ctrl+v) OBSERVED RESULT Krita crashes. Log says "closed session" EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: 11 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.
[NeoChat] [Bug 455825] [TRACKER] Consistency with Konversation
https://bugs.kde.org/show_bug.cgi?id=455825 --- Comment #3 from Anna --- When I type "/join" with a room I already joined, NeoChat doesn't navigate me to this room. -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 455825] [TRACKER] Consistency with Konversation
https://bugs.kde.org/show_bug.cgi?id=455825 --- Comment #2 from Anna --- Pressing Escape doesn't focus the input field. -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 455825] New: [TRACKER] Consistency with Konversation
https://bugs.kde.org/show_bug.cgi?id=455825 Bug ID: 455825 Summary: [TRACKER] Consistency with Konversation Product: NeoChat Version: unspecified Platform: unspecified OS: All Status: REPORTED Severity: wishlist Priority: NOR Component: General Assignee: fe...@posteo.de Reporter: cyber+...@sysrq.in CC: c...@carlschwan.eu Target Milestone: --- A noticeable part of new NeoChat users are people that have been using Konversation before. We have to make sure NeoChat's UX (like keybindings and /commands) are intuitive to Konversation users. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 452568] New: Proxy settings KCM should also set corresponding keys in GSettings schemas
https://bugs.kde.org/show_bug.cgi?id=452568 Bug ID: 452568 Summary: Proxy settings KCM should also set corresponding keys in GSettings schemas Product: systemsettings Version: 5.24.4 Platform: unspecified OS: All Status: REPORTED Severity: wishlist Priority: NOR Component: kcm_proxy Assignee: konq-b...@kde.org Reporter: cyber+...@sysrq.in CC: plasma-b...@kde.org Target Milestone: --- Some apps use the following GConf schemas: org.gnome.system.proxy org.gnome.system.proxy.ftp org.gnome.system.proxy.http org.gnome.system.proxy.https org.gnome.system.proxy.socks -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 449024] Unable to fetch google calendar events
https://bugs.kde.org/show_bug.cgi?id=449024 Anna Ochab-Marcinek changed: What|Removed |Added Version|5.19.1 |5.18.1 Platform|openSUSE RPMs |Kubuntu Packages --- Comment #20 from Anna Ochab-Marcinek --- The bug is still present after system upgrade: Now Kubuntu 21.10, KOrganizer version 5.18.1 (21.08.1) -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 449024] Unable to fetch google calendar events
https://bugs.kde.org/show_bug.cgi?id=449024 Anna Ochab-Marcinek changed: What|Removed |Added Platform|Archlinux Packages |Kubuntu Packages CC||oc...@ichf.edu.pl Version|5.19.1 |5.16.3 --- Comment #4 from Anna Ochab-Marcinek --- same here. Kubuntu 21.04, KOrganizer Version 5.16.3 (20.12.3) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 446757] Appimage update does not work, underlying mechanism is either not present or not executable.
https://bugs.kde.org/show_bug.cgi?id=446757 --- Comment #10 from Anna Medonosova --- Hi, amyspark, > One mo, shouldn't these be > https://binary-factory.kde.org/job/Krita_Stable_Appimage_Build/ > lastSuccessfulBuild/artifact/Krita-Plus-x86_64.appimage.zsync and > https://binary-factory.kde.org/job/Krita_Nightly_Appimage_Build/ > lastSuccessfulBuild/artifact/Krita-Next-x86_64.appimage.zsync? I think the naming gets a little confusing, as there is a mismatch between branding/update channel and binary factory job names. For clarity, I have summarized it in the following table. > +-+-+---+ > | Channel | binary factory job | >zsync url > | > +-+--+---+ > | Next| Krita_Nightly_Appimage_Build | > https://binary-factory.kde.org/job/Krita_Nightly_Appimage_Build/lastSuccessfulBuild/artifact/Krita-Next-x86_64.appimage.zsync > | > | Plus| Krita_Stable_Appimage_Build | > https://binary-factory.kde.org/job/Krita_Stable_Appimage_Build/lastSuccessfulBuild/artifact/Krita-Plus-x86_64.appimage.zsync > | > | Beta| Krita_Release_Appimage_Build | the > https://download.kde.org/unstable/krita/updates/Krita-Beta-x86_64.appimage.zsync > | > | Stable | Krita_Release_Appimage_Build | > https://download.kde.org/stable/krita/updates/Krita-Stable-x86_64.appimage.zsync > | > +-+--+---+ -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 446757] Appimage update does not work, underlying mechanism is either not present or not executable.
https://bugs.kde.org/show_bug.cgi?id=446757 Anna Medonosova changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 446757] Appimage update does not work, underlying mechanism is either not present or not executable.
https://bugs.kde.org/show_bug.cgi?id=446757 Anna Medonosova changed: What|Removed |Added Status|ASSIGNED|CONFIRMED CC||anna.medonosova@protonmail. ||com --- Comment #2 from Anna Medonosova --- Hi, Wolthera, I can reproduce the issue in the betas, Plus and 5.0.0 stable version. I have filed a MR that should fix embedding of the AppImageUpdate tool. There is also a second issue that breaks the update process: the zsync files are missing on the download server. The update mechanism expects the zsync files to be available as https://download.kde.org/unstable/krita/updates/Krita-Beta-x86_64.appimage.zsync for stable version and https://download.kde.org/stable/krita/updates/Krita-Stable-x86_64.appimage.zsync for betas. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 445179] Krita crashes when opening a file with 16-bit int depth
https://bugs.kde.org/show_bug.cgi?id=445179 --- Comment #6 from Anna Medonosova --- Created attachment 144002 --> https://bugs.kde.org/attachment.cgi?id=144002=edit system information for bug reports (android) I'm attaching the system information. The device is a Samsung Galaxy Tab S6, if that's relevant. Thanks for looking into it :) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 445179] Krita crashes when opening a file with 16-bit int depth
https://bugs.kde.org/show_bug.cgi?id=445179 Anna Medonosova changed: What|Removed |Added Keywords||regression -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 445179] Krita crashes when opening a file with 16-bit int depth
https://bugs.kde.org/show_bug.cgi?id=445179 --- Comment #1 from Anna Medonosova --- Created attachment 143352 --> https://bugs.kde.org/attachment.cgi?id=143352=edit test file -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 445179] New: Krita crashes when opening a file with 16-bit int depth
https://bugs.kde.org/show_bug.cgi?id=445179 Bug ID: 445179 Summary: Krita crashes when opening a file with 16-bit int depth Product: krita Version: git master (please specify the git hash!) Platform: Android OS: Android 11.x Status: REPORTED Severity: normal Priority: NOR Component: * Unknown Assignee: krita-bugs-n...@kde.org Reporter: anna.medonos...@protonmail.com Target Milestone: --- Created attachment 143351 --> https://bugs.kde.org/attachment.cgi?id=143351=edit backtrace of the crash SUMMARY When I try to open a file with 16-bit int depth color profile, Krita crashes upon loading the file. 8-bit documents are opened correctly. I'm attaching a test file triggering the crash and a backtrace. STEPS TO REPRODUCE 1. Open a file with 16-bit depth profile OBSERVED RESULT Krita crashes. EXPECTED RESULT The file is opened. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 445127] New: Saving files opened from a file manager silently fails
https://bugs.kde.org/show_bug.cgi?id=445127 Bug ID: 445127 Summary: Saving files opened from a file manager silently fails Product: krita Version: git master (please specify the git hash!) Platform: Android OS: Android 11.x Status: REPORTED Severity: major Priority: NOR Component: File formats Assignee: krita-bugs-n...@kde.org Reporter: anna.medonos...@protonmail.com Target Milestone: --- Created attachment 143314 --> https://bugs.kde.org/attachment.cgi?id=143314=edit usage log SUMMARY On Android (Samsung Galaxy Tab S6), when I open a .kra file from within a file manager, make changes and want to save later, the file is not saved and there is no error shown. Also, there is no 'saving document' progress bar down in the status bar (the progress bar shows up for the same file opened from within Krita). The log does not even show a save operation. 'Save as' works normally. Saving documents opened from within Krita works correctly. STEPS TO REPRODUCE 1. open a .kra file from a file manager 2. make a change 3. click the save button OBSERVED RESULT The change is not saved. There is no corresponding save operation in the log file. EXPECTED RESULT Ideally, the file is saved. If that is not possible, there should be an error message shown to the user. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 438324] Specific PSD file causes color selector and canvas glitches
https://bugs.kde.org/show_bug.cgi?id=438324 Anna Medonosova changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED --- Comment #7 from Anna Medonosova --- (In reply to wolthera from comment #6) > anna, is this still happening with the latest appimage? Amyspark added some > important patches to LCMS. (though, you might need to use the nightly, I > don't recall if they cherry-picked it to 5.0...) Hi, Wolthera, I tried reproducing the issue on git 6a5e83d (AppImage and local builds for Linux and Android). The visual glitches are gone. I'm marking the bug as resolved. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 440782] the color selector freeze all the time, it is useless, i have to work with the color codes
https://bugs.kde.org/show_bug.cgi?id=440782 --- Comment #4 from anna --- Thank you! On Fri, 13 Aug 2021, 06:36 Bug Janitor Service, wrote: > https://bugs.kde.org/show_bug.cgi?id=440782 > > 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 reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 440782] the color selector freeze all the time, it is useless, i have to work with the color codes
https://bugs.kde.org/show_bug.cgi?id=440782 --- Comment #2 from anna --- I don't find the crash log, and I have the last, the newest release but I also experienced this problem before the update. Tiar ezt írta (időpont: 2021. aug. 9., H, 15:23): > https://bugs.kde.org/show_bug.cgi?id=440782 > > Tiar changed: > >What|Removed |Added > > >Severity|major |crash > CC||tamtamy.tym...@gmail.com > Status|REPORTED|NEEDSINFO > Resolution|--- |WAITINGFORINFO > > --- Comment #1 from Tiar --- > Please attach Help -> Show Krita log for bug reports. I hope there will be > a > crash log there. Also are you using 4.4.7, the newest release? > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 440782] the color selector freeze all the time, it is useless, i have to work with the color codes
https://bugs.kde.org/show_bug.cgi?id=440782 anna changed: What|Removed |Added Summary|the color selector freeze |the color selector freeze |all the time, it is |all the time, it is |useless, i have to wrok |useless, i have to work |with the color codes|with the color codes -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 440782] New: the color selector freeze all the time, it is useless, i have to wrok with the color codes
https://bugs.kde.org/show_bug.cgi?id=440782 Bug ID: 440782 Summary: the color selector freeze all the time, it is useless, i have to wrok with the color codes Product: krita Version: 4.4.7 Platform: Other OS: Microsoft Windows Status: REPORTED Severity: major Priority: NOR Component: Color Selectors Assignee: krita-bugs-n...@kde.org Reporter: csanyi.pa...@gmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. click on the color selector tool 2. the app freeze 3. the app close itself 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.
[kdenlive] [Bug 440436] Kdenlive crash (SIGABRT) on creating a project
https://bugs.kde.org/show_bug.cgi?id=440436 Anna changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #1 from Anna --- I had this problem because qtcore was build with `CONFIG+=debug` on my machine so it had extra asserts that crashed Kdenlive. Solved. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 440436] New: Kdenlive crash (SIGABRT) on creating a project
https://bugs.kde.org/show_bug.cgi?id=440436 Bug ID: 440436 Summary: Kdenlive crash (SIGABRT) on creating a project Product: kdenlive Version: 21.04.3 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: cyber+...@sysrq.in Target Milestone: --- Application: kdenlive (21.04.3) (Compiled from sources) Qt Version: 5.15.3 (KDE Qt5 Patch Collection) Frameworks Version: 5.84.0 Operating System: Linux 5.12.0-pf4 x86_64 Windowing System: X11 Drkonqi Version: 5.22.4 Distribution: "Gentoo Base System release 2.7" -- Information about the crash: I tried to create a project with default options. The crash can be reproduced every time. Removing ~/.config/kdenlive*, ~/.cache/kdenlive and ~/.local/share/kdenlive didn't help. -- Backtrace: Application: Kdenlive (kdenlive), signal: Aborted [KCrash Handler] #4 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:49 #5 0x7f3882402536 in __GI_abort () at abort.c:79 #6 0x7f388277496e in () at /usr/lib/gcc/x86_64-pc-linux-gnu/11.1.0/libstdc++.so.6 #7 0x7f38827a2daa in () at /usr/lib/gcc/x86_64-pc-linux-gnu/11.1.0/libstdc++.so.6 #8 0x7f38827a2e15 in () at /usr/lib/gcc/x86_64-pc-linux-gnu/11.1.0/libstdc++.so.6 #9 0x7f38827a3b43 in () at /usr/lib/gcc/x86_64-pc-linux-gnu/11.1.0/libstdc++.so.6 #10 0x7f3882bcafd2 in QAbstractItemModel::beginRemoveRows(QModelIndex const&, int, int) (this=0x555d2441c3b0, parent=..., first=3, last=3) at ../../../qtcore-5.15./src/corelib/itemmodels/qabstractitemmodel.cpp:2815 #11 0x555d205daac3 in operator() (__closure=) at ../kdenlive-21.04.3/src/timeline2/model/timelinemodel.cpp:3627 #12 std::__invoke_impl&> (__f=) at /usr/lib/gcc/x86_64-pc-linux-gnu/11.1.0/include/g++-v11/bits/invoke.h:61 #13 std::__invoke_r&> (__fn=) at /usr/lib/gcc/x86_64-pc-linux-gnu/11.1.0/include/g++-v11/bits/invoke.h:142 #14 std::_Function_handler >::_M_invoke(const std::_Any_data &) (__functor=...) at /usr/lib/gcc/x86_64-pc-linux-gnu/11.1.0/include/g++-v11/bits/std_function.h:291 #15 0x555d205dadec in std::function::operator()() const (this=0x7ffc7392eb20) at /usr/lib/gcc/x86_64-pc-linux-gnu/11.1.0/include/g++-v11/bits/std_function.h:556 #16 TimelineModel::~TimelineModel() (this=this@entry=0x555d2441c3b0, __in_chrg=) at ../kdenlive-21.04.3/src/timeline2/model/timelinemodel.cpp:168 #17 0x555d205b1d85 in TimelineItemModel::~TimelineItemModel() (this=0x555d2441c3b0, __in_chrg=) at ../kdenlive-21.04.3/src/timeline2/model/timelineitemmodel.cpp:80 #18 TimelineItemModel::~TimelineItemModel() (this=0x555d2441c3b0, __in_chrg=) at ../kdenlive-21.04.3/src/timeline2/model/timelineitemmodel.cpp:80 #19 std::_Sp_counted_ptr::_M_dispose() (this=) at /usr/lib/gcc/x86_64-pc-linux-gnu/11.1.0/include/g++-v11/bits/shared_ptr_base.h:348 #20 0x555d2056ad02 in std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>::_M_release() (this=0x555d25964590) at /usr/lib/gcc/x86_64-pc-linux-gnu/11.1.0/include/g++-v11/bits/shared_ptr_base.h:168 #21 std::__shared_count<(__gnu_cxx::_Lock_policy)2>::~__shared_count() (this=, __in_chrg=) at /usr/lib/gcc/x86_64-pc-linux-gnu/11.1.0/include/g++-v11/bits/shared_ptr_base.h:702 #22 std::__shared_ptr::~__shared_ptr() (this=, __in_chrg=) at /usr/lib/gcc/x86_64-pc-linux-gnu/11.1.0/include/g++-v11/bits/shared_ptr_base.h:1149 #23 std::__shared_ptr::reset() (this=0x555d2159a308) at /usr/lib/gcc/x86_64-pc-linux-gnu/11.1.0/include/g++-v11/bits/shared_ptr_base.h:1267 #24 ProjectManager::closeCurrentDocument(bool, bool) (this=this@entry=0x555d2159a2f0, saveChanges=saveChanges@entry=true, quit=quit@entry=false) at ../kdenlive-21.04.3/src/project/projectmanager.cpp:295 #25 0x555d2056ee5c in ProjectManager::newFile(QString, bool) (this=0x555d2159a2f0, profileName=..., showProjectSettings=) at ../kdenlive-21.04.3/src/project/projectmanager.cpp:181 #26 0x555d2056f94d in ProjectManager::newFile(bool) (this=0x555d2159a2f0, showProjectSettings=) at ../kdenlive-21.04.3/src/project/projectmanager.cpp:140 #27 0x7f3882c48e98 in doActivate(QObject*, int, void**) (sender=0x555d21573910, signal_index=4, argv=0x7ffc7392ee60) at ../../../qtcore-5.15./src/corelib/kernel/qobject.cpp:3898 #28 0x7f3882c42787 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=sender@entry=0x555d21573910, m=m@entry=0x7f388430dd60 , local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x7ffc7392ee60) at ../../../qtcore-5.15./src/corelib/kernel/qobject.cpp:3946 #29 0x7f3883d9f7ea in QAction::triggered(bool) (this=this@entry=0x555d21573910, _t1=) at .moc/moc_qaction.cpp:379 #30 0x7f3883da25a8 in QAction::activate(QAction::ActionEvent) (this=0x555d21573910, event=) at ../../../qtwidgets-5.15./src/widgets/kernel/qaction.cpp:1161 #31 0x7f3883e9ed82 in
[krita] [Bug 438549] Mirror tool handle is not displayed on canvas
https://bugs.kde.org/show_bug.cgi?id=438549 --- Comment #8 from Anna Medonosova --- Created attachment 140408 --> https://bugs.kde.org/attachment.cgi?id=140408=edit screenshot with handles missing -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 438549] Mirror tool handle is not displayed on canvas
https://bugs.kde.org/show_bug.cgi?id=438549 Anna Medonosova changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |CONFIRMED --- Comment #7 from Anna Medonosova --- (In reply to Dmitry Kazakov from comment #5) > Hi, Anna! > > Could you please make a screenshot of the problem? I cannot understand what > is wrong with the handles on your side. I've just retested on Linux and the > handles are painted correctly here :( Hi! yesterday I have retested on git efe590e (nightly appimage on linux, local build for Android). In this version, the handles were displayed correctly on both platforms. In the previous versions, the circle with the arrow was missing, only the dashed lines were present. (I will attach a screenshot.) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 440211] Crash when selecting some presets in brush editor
https://bugs.kde.org/show_bug.cgi?id=440211 Anna Medonosova changed: What|Removed |Added Attachment #140290|system |system information for bug description||reports -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 440211] Crash when selecting some presets in brush editor
https://bugs.kde.org/show_bug.cgi?id=440211 --- Comment #1 from Anna Medonosova --- Created attachment 140290 --> https://bugs.kde.org/attachment.cgi?id=140290=edit system -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 440211] New: Crash when selecting some presets in brush editor
https://bugs.kde.org/show_bug.cgi?id=440211 Bug ID: 440211 Summary: Crash when selecting some presets in brush editor Product: krita Version: git master (please specify the git hash!) Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Brush engines Assignee: krita-bugs-n...@kde.org Reporter: anna.medonos...@protonmail.com Target Milestone: --- Created attachment 140289 --> https://bugs.kde.org/attachment.cgi?id=140289=edit backtrace of the crash SUMMARY When some presets are either selected in the brush editor, or they are first selected in other widgets and then the brush editor is opened, Krita crashes. I have reproduced the crash with the "f) Bristles" group of presets, "b) Basic-6 Details" and presets from the "Charcoal KA" and "Digital Atelier" bundles. STEPS TO REPRODUCE A. 1. select the "f) Bristles-1 Details" preset 2. open the brush editor 3. crash B. 1. open the brush editor 2. select the "f) Bristles-1 Details" preset in the list on the left 3. crash OBSERVED RESULT Krita crashes. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 438549] Mirror tool handle is not displayed on canvas
https://bugs.kde.org/show_bug.cgi?id=438549 Anna Medonosova changed: What|Removed |Added Status|NEEDSINFO |CONFIRMED Resolution|WAITINGFORINFO |--- --- Comment #4 from Anna Medonosova --- (In reply to Dmitry Kazakov from comment #2) > Hi, Anna! > > Could you please check if the bug is still actual? I tested the current > master and it seems like the bug is not here anymore Hi, Dmitry, I can confirm the issue is still there in git b66a85a, both locally built and in the appimage from the Binary Factory. I have tested turning off canvas acceleration in the settings. When acceleration is turned off, the mirror tool handles are displayed correctly. However, with acceleration on, the handles do not appear. I have updated nvidia drivers to 460.91.03 in the meantime (I had 460.80 previously), but that didn't help. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 438549] Mirror tool handle is not displayed on canvas
https://bugs.kde.org/show_bug.cgi?id=438549 Anna Medonosova changed: What|Removed |Added Keywords||regression -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 438549] New: Mirror tool handle is not displayed on canvas
https://bugs.kde.org/show_bug.cgi?id=438549 Bug ID: 438549 Summary: Mirror tool handle is not displayed on canvas Product: krita Version: nightly build (please specify the git hash!) Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: * Unknown Assignee: krita-bugs-n...@kde.org Reporter: anna.medonos...@protonmail.com Target Milestone: --- Created attachment 139285 --> https://bugs.kde.org/attachment.cgi?id=139285=edit system information for bug reports SUMMARY When I turn on either the horizontal or vertical mirror tool, a dashed line appears on the canvas and brush strokes are mirrored. However, the handle is missing and so the line cannot be moved. The "Lock line" checkbox is unchecked. If you check and uncheck the checkbox, the handle does not appear. STEPS TO REPRODUCE 1. Turn on horizontal or vertical mirror (buttons in the toolbar OBSERVED RESULT The handle is missing. EXPECTED RESULT The handle should be displayed on canvas, unless "Lock line" checkbox is checked. ADDITIONAL INFORMATION Version: 5.0.0-prealpha (git 4f029a8) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 438324] Specific PSD file causes color selector and canvas glitches
https://bugs.kde.org/show_bug.cgi?id=438324 --- Comment #4 from Anna Medonosova --- Created attachment 139168 --> https://bugs.kde.org/attachment.cgi?id=139168=edit system information for bug reports (android) On Android, I can't reproduce the glitches on canvas with 5.0.0-prealpha (git 884a064) I have built today. The triangle in the Advanced color selector is invisible. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 438324] Specific PSD file causes color selector and canvas glitches
https://bugs.kde.org/show_bug.cgi?id=438324 --- Comment #3 from Anna Medonosova --- Created attachment 139166 --> https://bugs.kde.org/attachment.cgi?id=139166=edit system information for bug reports (appimage) I have retested with AppImage 5.0.0-prealpha (git 607fca8). I can still reproduce the issue. I'm attaching system information for bug reports to this bug. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 438324] Specific PSD file causes color selector and canvas glitches
https://bugs.kde.org/show_bug.cgi?id=438324 --- Comment #1 from Anna Medonosova --- Created attachment 139139 --> https://bugs.kde.org/attachment.cgi?id=139139=edit selector glitches -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 438324] New: Specific PSD file causes color selector and canvas glitches
https://bugs.kde.org/show_bug.cgi?id=438324 Bug ID: 438324 Summary: Specific PSD file causes color selector and canvas glitches Product: krita Version: git master (please specify the git hash!) Platform: Appimage OS: All Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: anna.medonos...@protonmail.com Target Milestone: --- Created attachment 139138 --> https://bugs.kde.org/attachment.cgi?id=139138=edit test file SUMMARY When a specific PSD file is open, color selectors (advanced, specific and internal on Linux, on Android also the one in popu palette) and canvas (on Android) become unusable due to various visual glitches. The image also does not work when saved as or exported. On Android I have also seen some kind of storage error. A way to recover the image is to copy the layers to a different document. I suspect it may have something to do with the document color space, but I'm not sure about that. I have observed the issue in latest nightly appimage and on Android git master build. In the 4.4.3 appimage, the glitches are not present. STEPS TO REPRODUCE 1. Open testimage.psd (attached to this report) OBSERVED RESULT The color selectors disappear, are displaced or display other glitches. The canvas shows only portions of the document. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 437663] New: Long press does not work in floating dockers
https://bugs.kde.org/show_bug.cgi?id=437663 Bug ID: 437663 Summary: Long press does not work in floating dockers Product: krita Version: git master (please specify the git hash!) Platform: Android OS: Android 11.x Status: REPORTED Severity: normal Priority: NOR Component: Dockers Assignee: krita-bugs-n...@kde.org Reporter: anna.medonos...@protonmail.com Target Milestone: --- SUMMARY When a docker is floating, long press (used instead of right click on Android) is not registered. A tap (left click) is registered instead. When the dockers are docked into the side toolbars, it works correctly. I have tested this issue in the Advanced Color Selector and Layers dockers, with the SPen. STEPS TO REPRODUCE A) 1. Undock the Advanced Color Selector 2. Long-press on the color selector to change background color => background color is unchanged B) 1. Undock the Layers docker 2. Long-press on a layer name => nothing happens (a context menu should appear -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 418855] Layer content is invisible after applying transform on a system under load
https://bugs.kde.org/show_bug.cgi?id=418855 Anna Medonosova changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |CONFIRMED Ever confirmed|0 |1 --- Comment #4 from Anna Medonosova --- Hi, Dmitry, with your appimage I couldn't reproduce the issue anymore (while it shows up quite consistently on the 4.4.3 appimage). -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 437365] New: Numbered value scale in artistic color selector does not show numbers
https://bugs.kde.org/show_bug.cgi?id=437365 Bug ID: 437365 Summary: Numbered value scale in artistic color selector does not show numbers Product: krita Version: git master (please specify the git hash!) Platform: Android OS: Android 11.x Status: REPORTED Severity: normal Priority: NOR Component: Color Selectors Assignee: krita-bugs-n...@kde.org Reporter: anna.medonos...@protonmail.com Target Milestone: --- SUMMARY When numbered value scale is turned on in the Artistic color selector, a grayscale strip with numbers is shown on the lefy of the selector. On Android, the strip is shown correctly, but the numbers are missing. STEPS TO REPRODUCE 1. Turn on numbered value scale in the selector settings OBSERVED RESULT The gray strip is shown on the left side of the docker, however, the numbers are missing. EXPECTED RESULT The gray strip should have numbers on top. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 436858] New: Long press on the brush preset chooser closes the popup
https://bugs.kde.org/show_bug.cgi?id=436858 Bug ID: 436858 Summary: Long press on the brush preset chooser closes the popup Product: krita Version: git master (please specify the git hash!) Platform: Android OS: Android 11.x Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: anna.medonos...@protonmail.com Target Milestone: --- SUMMARY When I long-press a brush preset in the left half of the preset chooser (the one on the toolbar), a context menu is shown. However, when I do the same on the right half, the popup is closed instead. The preset chooser docker works correctly. STEPS TO REPRODUCE 1. Open the brush preset chooser popup from the toolbar 2. Long-press a brush preset in the right half of the chooser OBSERVED RESULT The popup is closed EXPECTED RESULT The context menu is displayed. ADDITIONAL INFORMATION I tested it on git 87c46be, Samsung Galaxy Tab S6. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 429366] Poor keyboard navigation
https://bugs.kde.org/show_bug.cgi?id=429366 Anna changed: What|Removed |Added CC||cyber+...@sysrq.in --- Comment #4 from Anna --- Keyboard navigation is also poor in "Sensors" tab of plasmoid's settings. Moreover, it's unusable with a graphics tablet. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 432904] App crashes if Layers is selected from 3 bar menu Top right of screen
https://bugs.kde.org/show_bug.cgi?id=432904 Anna Medonosova changed: What|Removed |Added CC||anna.medonosova@protonmail. ||com --- Comment #2 from Anna Medonosova --- Created attachment 135761 --> https://bugs.kde.org/attachment.cgi?id=135761=edit backtrace of the crash I can reproduce the crash on current stable branch and master. I'm attaching a backtrace. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 432488] New: Brush presets from user-imported bundles cannot be reloaded
https://bugs.kde.org/show_bug.cgi?id=432488 Bug ID: 432488 Summary: Brush presets from user-imported bundles cannot be reloaded Product: krita Version: 4.4.2 Platform: Android OS: Android 10.x Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: anna.medonos...@protonmail.com Target Milestone: --- SUMMARY Brush presets from user-imported bundles cannot be reloaded: clicking the "Reload preset" button does nothing. Presets from the default bundles from Krita installation reload correctly. STEPS TO REPRODUCE 1. Select a preset 2. Make changes to the preset (e.g. change size or opacity) 3. Click the "Reload preset" button (in the toolbar, in brush editor or in the popup palette) OBSERVED RESULT The preset is not reloaded. EXPECTED RESULT The preset is reloaded to original state. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 432362] New: Crash when creating a new document
https://bugs.kde.org/show_bug.cgi?id=432362 Bug ID: 432362 Summary: Crash when creating a new document Product: krita Version: git master Platform: Android OS: Android 10.x Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: anna.medonos...@protonmail.com Target Milestone: --- SUMMARY Krita crashes when creating a new document (custom or from a template). Opening an existing document does not trigger the crash. STEPS TO REPRODUCE 1. Open the new document dialog, either from the menu or from the welcome page 2. Click "Create" OBSERVED RESULT Krita crashes. EXPECTED RESULT A new document is created and opened. ADDITIONAL INFORMATION Backtrace: ** Crash dump: ** Build fingerprint: 'samsung/gts6lwifieea/gts6lwifi:10/QP1A.190711.020/T860XXS3BUA1:user/release-keys' #00 0x00133138 /data/app/org.krita-6PDxR551NA-ziWeg3df6Mw==/lib/arm64/libQt5Core.so (operator==(QString const&, QString const&)) #01 0x001dd740 /data/app/org.krita-6PDxR551NA-ziWeg3df6Mw==/lib/arm64/libQt5Core.so (QUrl::fileName(QFlags) const+76) #02 0x00f3f758 /data/app/org.krita-6PDxR551NA-ziWeg3df6Mw==/lib/arm64/libkritaui.so (KisDocument::caption() const+76) (BuildId: 2faaa8be17f6618bc319e2f99f7135ac11729158) KisDocument::caption() const /home/user/persistent/src/libs/ui/KisDocument.cpp:1760:30 #03 0x00f669e8 /data/app/org.krita-6PDxR551NA-ziWeg3df6Mw==/lib/arm64/libkritaui.so (KisMainWindow::updateCaption()+408) (BuildId: 2faaa8be17f6618bc319e2f99f7135ac11729158) KisMainWindow::updateCaption() /home/user/persistent/src/libs/ui/KisMainWindow.cpp:961:32 #04 0x00f67ae0 /data/app/org.krita-6PDxR551NA-ziWeg3df6Mw==/lib/arm64/libkritaui.so (KisMainWindow::setActiveView(KisView*)+92) (BuildId: 2faaa8be17f6618bc319e2f99f7135ac11729158) KisMainWindow::setActiveView(KisView*) /home/user/persistent/src/libs/ui/KisMainWindow.cpp:1549:5 #05 0x00f6a810 /data/app/org.krita-6PDxR551NA-ziWeg3df6Mw==/lib/arm64/libkritaui.so (KisMainWindow::setActiveSubWindow(QWidget*)+208) (BuildId: 2faaa8be17f6618bc319e2f99f7135ac11729158) KisMainWindow::setActiveSubWindow(QWidget*) /home/user/persistent/src/libs/ui/KisMainWindow.cpp:2473:13 #06 0x00f5f198 /data/app/org.krita-6PDxR551NA-ziWeg3df6Mw==/lib/arm64/libkritaui.so (KisMainWindow::subWindowActivated()+260) (BuildId: 2faaa8be17f6618bc319e2f99f7135ac11729158) KisMainWindow::subWindowActivated() /home/user/persistent/src/libs/ui/KisMainWindow.cpp:2220:5 #07 0x00f76370 /data/app/org.krita-6PDxR551NA-ziWeg3df6Mw==/lib/arm64/libkritaui.so (BuildId: 2faaa8be17f6618bc319e2f99f7135ac11729158) KisMainWindow::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) /home/user/persistent/src/libs/ui/KisMainWindow.cpp:0:9 #08 0x002b5194 /data/app/org.krita-6PDxR551NA-ziWeg3df6Mw==/lib/arm64/libQt5Core.so (QMetaObject::activate(QObject*, int, int, void**)+2584) #09 0x002c69c0 /data/app/org.krita-6PDxR551NA-ziWeg3df6Mw==/lib/arm64/libQt5Widgets.so Crash dump is completed -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 431611] Transform tool sticks to stylus when attempting to resize
https://bugs.kde.org/show_bug.cgi?id=431611 Anna Medonosova changed: What|Removed |Added CC||anna.medonosova@protonmail. ||com --- Comment #1 from Anna Medonosova --- I can confirm this behavior on my Galaxy Tab S6. It might be related, that when dragging either the handles or a point outside/inside the transformed area, the action (move, scale, shear, ...) Krita performs is not always what I would expect, based on experience from the desktop version (e.g. it shears instead of scaling when dragging the handle). Also, the cursor does not change to reflect the current action. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 430314] New: Triangle shape of the Advanced color selector is not clickable
https://bugs.kde.org/show_bug.cgi?id=430314 Bug ID: 430314 Summary: Triangle shape of the Advanced color selector is not clickable Product: krita Version: 4.4.2-beta1 Platform: Android OS: Android 10.x Status: REPORTED Severity: normal Priority: NOR Component: Color Selectors Assignee: krita-bugs-n...@kde.org Reporter: anna.medonos...@protonmail.com Target Milestone: --- SUMMARY When the Advanced color selector is set to the triangle type, the triangle does not respond to neither touch nor the S Pen. The color blip is not moved to the selected point on the shape and foreground color is unchanged. The ring and the shade selector both work. When the foreground color is changed (from the working parts of the selector, from the color picker, or from other selectors), the blip updates correctly. Other shape types work correctly. STEPS TO REPRODUCE 1. Set the advanced color selector shape to triangle 2. Click the triangle to change foreground color OBSERVED RESULT The blip does not update, foreground color does not change. EXPECTED RESULT The blip moves to the selected position and foreground color is changed. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 429691] New: Adding a symbol from the Vector Library is very sensitive to timing
https://bugs.kde.org/show_bug.cgi?id=429691 Bug ID: 429691 Summary: Adding a symbol from the Vector Library is very sensitive to timing Product: krita Version: 4.4.1 Platform: Android OS: Android 10.x Status: REPORTED Severity: normal Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: anna.medonos...@protonmail.com Target Milestone: --- Created attachment 133669 --> https://bugs.kde.org/attachment.cgi?id=133669=edit screen recording of the issue SUMMARY In the desktop version of Krita, symbols from the Vector Library dockers can be drag onto the canvas. On Android, I can technically double-tap and drag the symbol (though it takes some trial and error). However, I have to be very quick, otherwise the dragged symbol disappears before I reach the canvas and the symbol is not added. STEPS TO REPRODUCE 1. Create a document 2. Enable the Vector Library docker 3. Drag a symbol from the docker onto the canvas OBSERVED RESULT The symbol disappears while dragging and is not added to the canvas. EXPECTED RESULT The symbol remains under cursor until it is dropped onto the canvas. Or a different way to add the symbol (e.g. a button in the docker) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 426832] Nighly AppImages do not contain update information
https://bugs.kde.org/show_bug.cgi?id=426832 Anna Medonosova changed: What|Removed |Added Latest Commit||https://invent.kde.org/grap ||hics/krita/commit/2d04911bd ||ffd581874004a6faade317a6ed8 ||f51f Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #3 from Anna Medonosova --- Git commit 2d04911bdffd581874004a6faade317a6ed8f51f by Anna Medonosova. Committed on 16/11/2020 at 11:34. Pushed by amedonosova into branch 'master'. Fix embedding of update information into AppImage M +1-1packaging/linux/appimage/build-image.sh https://invent.kde.org/graphics/krita/commit/2d04911bdffd581874004a6faade317a6ed8f51f -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 429056] New: Resaving with different mime type does not work on Android
https://bugs.kde.org/show_bug.cgi?id=429056 Bug ID: 429056 Summary: Resaving with different mime type does not work on Android Product: krita Version: 4.4.0 Platform: Android OS: Android 10.x Status: REPORTED Severity: normal Priority: NOR Component: File formats Assignee: krita-bugs-n...@kde.org Reporter: anna.medonos...@protonmail.com Target Milestone: --- SUMMARY When trying to save a file, which was opened as JPG, to the native KRA format, JPG file is saved instead of KRA. The native file dialog on Android does not allow me to select a mime type; the suffix of the file name I entered is not considered. STEPS TO REPRODUCE 1. Open a JPG file 2. Make a change 3. File -> Save As, rename the file to ‘testfile.kra’ OBSERVED RESULT On disk, there is a file called testfile.kra.jpg, which is a JPG, not KRA. EXPECTED RESULT I would expect either being able to select a mime type in the file dialog or that the saving process selecting a mime type for the file according to the suffix I input. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 427402] New: Paste as reference image crashes Krita
https://bugs.kde.org/show_bug.cgi?id=427402 Bug ID: 427402 Summary: Paste as reference image crashes Krita Product: krita Version: 4.4.0-beta2 Platform: Android OS: Android 10.x Status: REPORTED Severity: normal Priority: NOR Component: Tools/Reference Images Assignee: krita-bugs-n...@kde.org Reporter: anna.medonos...@protonmail.com Target Milestone: --- Created attachment 132179 --> https://bugs.kde.org/attachment.cgi?id=132179=edit backtrace of the crash SUMMARY 'Paste as reference image' button in the tool options of the reference image tool causes Krita to crash. STEPS TO REPRODUCE 1. Open a document 2. Select the reference image tool 3. Click the 'Paste as reference image' button in the tool options OBSERVED RESULT A crash. EXPECTED RESULT I would expect it to either work, or not crash and display an error message. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 427043] New: Usage log and system information cannot be saved to a file
https://bugs.kde.org/show_bug.cgi?id=427043 Bug ID: 427043 Summary: Usage log and system information cannot be saved to a file Product: krita Version: nightly build (please specify the git hash!) Platform: Android OS: Android 10.x Status: REPORTED Severity: normal Priority: NOR Component: File formats Assignee: krita-bugs-n...@kde.org Reporter: anna.medonos...@protonmail.com Target Milestone: --- SUMMARY In 5.0.0 39f51c6, usage log and system information for bug reports cannot be saved. STEPS TO REPRODUCE 1. Open Help -> Show system information for bug reports, or Show Krita Log for bug reports 2. Click 'Save to file' 3. Select a directory to save to OBSERVED RESULT The operation fails silently. There is a file in the target directory with size of 0B. EXPECTED RESULT The log file is saved. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 427042] New: Save Incremental Version/Backup does not work
https://bugs.kde.org/show_bug.cgi?id=427042 Bug ID: 427042 Summary: Save Incremental Version/Backup does not work Product: krita Version: nightly build (please specify the git hash!) Platform: Android OS: Android 10.x Status: REPORTED Severity: normal Priority: NOR Component: File formats Assignee: krita-bugs-n...@kde.org Reporter: anna.medonos...@protonmail.com Target Milestone: --- SUMMARY In 5.0.0 39f51c6, if you try to save with 'Save Incremental Version' or 'Save Incremental Backup', the operation does not save and produces an error. It fails both for local storage and Google Drive. A normal document produces a different error than an autosave file open on startup after a crash. STEPS TO REPRODUCE 1. Open a document 2. Make some changes 3. Save with 'File' -> 'Save Incremental Version' or 'Save Incremental Backup' OBSERVED RESULT The document is not saved. Saving a normal document says: "Cannot open file for writing. An unspecified error occured.". Saving an autosave produces either a popup with "Couldn't save incremental version. Alternative names exhausted, try manually saving with a higher number." (for incremental version), or an error in the status bar: "Error during saving: / cannot be written to. Please save under a different name." (incremental backup). EXPECTED RESULT The document is saved. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 425011] ext_qt for Android does not build
https://bugs.kde.org/show_bug.cgi?id=425011 Anna Medonosova changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #2 from Anna Medonosova --- ext_qt from master builds correctly now, thanks to Sharaf Zaman. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 426914] New: Crash when dragging global selection mask onto another layer
https://bugs.kde.org/show_bug.cgi?id=426914 Bug ID: 426914 Summary: Crash when dragging global selection mask onto another layer Product: krita Version: 4.4.0-beta1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Tools/Selection Assignee: krita-bugs-n...@kde.org Reporter: anna.medonos...@protonmail.com Target Milestone: --- Created attachment 131890 --> https://bugs.kde.org/attachment.cgi?id=131890=edit backtrace of the crash SUMMARY When the global selection mask is dragged onto another layer in the Layers docker, Krita crashes. In 4.3, the same action converted the global selection into a local selection for the target layer. STEPS TO REPRODUCE 1. Check "Show global selection mask" in the Select menu. 2. Make a selection. 3. In the Layers docker, drag the global selection mask onto another layer. OBSERVED RESULT Segfault. EXPECTED RESULT The global selection is converted into local selection mask. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 426832] Nighly AppImages do not contain update information
https://bugs.kde.org/show_bug.cgi?id=426832 --- Comment #2 from Anna Medonosova --- (In reply to wolthera from comment #1) > is this for the plus or Krita next? Because boud mentioned only master has > that information? Next. Last time I did an update was around 19th August, it worked correctly. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 426832] New: Nighly AppImages do not contain update information
https://bugs.kde.org/show_bug.cgi?id=426832 Bug ID: 426832 Summary: Nighly AppImages do not contain update information Product: krita Version: nightly build (please specify the git hash!) Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: anna.medonos...@protonmail.com Target Milestone: --- SUMMARY AppImage updating does not work, because the AppImage does not contain update information. (The check fails silently, and the updater dialog does not appear. The unsuccessful check is logged in krita.log. That is by design.) STEPS TO REPRODUCE 1. Download a nightly appimage 2. in the console, run ./ --appimage-updateinformation OBSERVED RESULT Empty string. EXPECTED RESULT The AppImage contains the right update information. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 426386] New: Fill pattern of vector shapes is not affected by transform
https://bugs.kde.org/show_bug.cgi?id=426386 Bug ID: 426386 Summary: Fill pattern of vector shapes is not affected by transform Product: krita Version: nightly build (please specify the git hash!) Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Tools/Vector Assignee: krita-bugs-n...@kde.org Reporter: anna.medonos...@protonmail.com Target Milestone: --- SUMMARY In the AppImage for 4.4.0-alpha (git c00326b), the 'Tool Options' docker shows controls for transforming pattern fill. However, vector shapes are not affected by these parameters. STEPS TO REPRODUCE 1. Create a document. Create a vector layer. 2. Select the rectangle tool (or any other shape tool) 3. In the 'Tool Options', set Fill to 'Pattern' and tweak 'Pattern Transform' parameters 4. Create a shape on the canvas OBSERVED RESULT The fill of the shape is not affected by the transform parameters. EXPECTED RESULT Either the transform parameters affect the vector shape, or the 'Pattern Transform' section is hidden for vector layers. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 425344] Pop up palette not showing brushes on android
https://bugs.kde.org/show_bug.cgi?id=425344 Anna Medonosova changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||anna.medonosova@protonmail. ||com --- Comment #1 from Anna Medonosova --- I can reproduce this on my tablet. I have also tried changing the number of palette presets, it does not help. When the configuration is reset, default presets appear on the palette. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 425011] New: ext_qt for Android does not build
https://bugs.kde.org/show_bug.cgi?id=425011 Bug ID: 425011 Summary: ext_qt for Android does not build Product: krita Version: nightly build (please specify the git hash!) Platform: Android OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: anna.medonos...@protonmail.com Target Milestone: --- Created attachment 130634 --> https://bugs.kde.org/attachment.cgi?id=130634=edit build error SUMMARY When trying to build ext_qt for Android (both git master and 4.3 branch; locally and in docker with the kdeorg/ci-android image), configure fails with "ERROR: Unknown command line option '-with'.", probably due to https://invent.kde.org/graphics/krita/-/commit/3845a10d659aa48603bfb19b737f714177e0f14e. When "-with qtmultimedia" is replaced with "-skip qtmultimedia", the error is gone. STEPS TO REPRODUCE 1. Build dependencies for Android OBSERVED RESULT ext_qt does not build EXPECTED RESULT ext_qt builds without error -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 424514] Guaranteed crash when opening 2 G'MIC-qt
https://bugs.kde.org/show_bug.cgi?id=424514 Anna Medonosova changed: What|Removed |Added CC||anna.medonosova@protonmail. ||com --- Comment #3 from Anna Medonosova --- Created attachment 130349 --> https://bugs.kde.org/attachment.cgi?id=130349=edit backtrace of the crash, when first gmic window is closed (3-1); Linux, git master -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 424347] Android: Flickering square appears where you are currently drawing
https://bugs.kde.org/show_bug.cgi?id=424347 Anna Medonosova changed: What|Removed |Added Keywords||triaged Status|REPORTED|NEEDSINFO CC||anna.medonosova@protonmail. ||com Resolution|--- |WAITINGFORINFO --- Comment #1 from Anna Medonosova --- This might be a matter of fine tuning the configuration to your hardware. Can you reproduce the flickering with different display settings? To change display settings, go to "Settings" -> "Configure Krita" -> "Display". You can try 1, unchecking the "Use texture buffer" option 2, selecting a different "Scaling Mode" 3, turning off "Canvas Graphics Acceleration" For more details about the settings, you can refer to the manual at https://docs.krita.org/en/reference_manual/preferences/display_settings.html -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 424366] New: Kopete crashes on connect to XMPP
https://bugs.kde.org/show_bug.cgi?id=424366 Bug ID: 424366 Summary: Kopete crashes on connect to XMPP Product: kopete Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kopete-bugs-n...@kde.org Reporter: kde-b...@annaclemens.io Target Milestone: --- Application: kopete (1.13.0) Qt Version: 5.14.2 Frameworks Version: 5.70.0 Operating System: Linux 5.7.8-200.fc32.x86_64 x86_64 Windowing system: X11 Distribution: "Fedora release 32 (Thirty Two)" -- Information about the crash: - What I was doing when the application crashed: I added my XMPP account to Kopete and connected to it. Upon connection, Kopete crashes after I see my contacts populate. It could be due to being part of groupchats that might be autojoined upon connect, hence the possible duplicate, but I'm not certain. - Custom settings of the application: Using an XMPP account (server is Prosody with MUCs enabled) The crash can be reproduced every time. -- Backtrace: Application: Kopete (kopete), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fbb58c4e980 (LWP 7733))] Thread 10 (Thread 0x7fbb2e109700 (LWP 7749)): #0 0x7fbb5d9ff57c in read () from /lib64/libc.so.6 #1 0x7fbb5c15253f in g_wakeup_acknowledge () from /lib64/libglib-2.0.so.0 #2 0x7fbb5c10860e in g_main_context_check () from /lib64/libglib-2.0.so.0 #3 0x7fbb5c108a75 in g_main_context_iterate.constprop () from /lib64/libglib-2.0.so.0 #4 0x7fbb5c108c03 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #5 0x7fbb5df6db8b in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #6 0x7fbb5df2091b in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #7 0x7fbb5dd8c427 in QThread::exec() () from /lib64/libQt5Core.so.5 #8 0x7fbb2ecf06ea in XMPP::NetTrackerThread::run() () from /usr/lib64/qt5/plugins/kopete_jabber.so #9 0x7fbb5dd8d690 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #10 0x7fbb5ca53432 in start_thread () from /lib64/libpthread.so.0 #11 0x7fbb5da0e9d3 in clone () from /lib64/libc.so.6 Thread 9 (Thread 0x7fbb2e90a700 (LWP 7748)): #0 0x7fbb5da03b6f in poll () from /lib64/libc.so.6 #1 0x7fbb5c108ace in g_main_context_iterate.constprop () from /lib64/libglib-2.0.so.0 #2 0x7fbb5c108c03 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #3 0x7fbb5df6db8b in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #4 0x7fbb5df2091b in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #5 0x7fbb2ea972ef in QCA::SyncThread::run() () from /lib64/libqca-qt5.so.2 #6 0x7fbb5dd8d690 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #7 0x7fbb5ca53432 in start_thread () from /lib64/libpthread.so.0 #8 0x7fbb5da0e9d3 in clone () from /lib64/libc.so.6 Thread 8 (Thread 0x7fbb2700 (LWP 7740)): #0 0x7fbb5ca59e92 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fbb3ae3d26b in util_queue_thread_func () from /usr/lib64/dri/iris_dri.so #2 0x7fbb3ae3cd3b in impl_thrd_routine () from /usr/lib64/dri/iris_dri.so #3 0x7fbb5ca53432 in start_thread () from /lib64/libpthread.so.0 #4 0x7fbb5da0e9d3 in clone () from /lib64/libc.so.6 Thread 7 (Thread 0x7fbb34ae6700 (LWP 7739)): #0 0x7fbb5ca59e92 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fbb3ae3d26b in util_queue_thread_func () from /usr/lib64/dri/iris_dri.so #2 0x7fbb3ae3cd3b in impl_thrd_routine () from /usr/lib64/dri/iris_dri.so #3 0x7fbb5ca53432 in start_thread () from /lib64/libpthread.so.0 #4 0x7fbb5da0e9d3 in clone () from /lib64/libc.so.6 Thread 6 (Thread 0x7fbb352e7700 (LWP 7738)): #0 0x7fbb5ca59e92 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fbb3ae3d26b in util_queue_thread_func () from /usr/lib64/dri/iris_dri.so #2 0x7fbb3ae3cd3b in impl_thrd_routine () from /usr/lib64/dri/iris_dri.so #3 0x7fbb5ca53432 in start_thread () from /lib64/libpthread.so.0 #4 0x7fbb5da0e9d3 in clone () from /lib64/libc.so.6 Thread 5 (Thread 0x7fbb35ae8700 (LWP 7737)): #0 0x7fbb5ca59e92 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fbb3ae3d26b in util_queue_thread_func () from /usr/lib64/dri/iris_dri.so #2 0x7fbb3ae3cd3b in impl_thrd_routine () from /usr/lib64/dri/iris_dri.so #3 0x7fbb5ca53432 in start_thread () from /lib64/libpthread.so.0 #4 0x7fbb5da0e9d3 in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7fbb499db700 (LWP 7736)): #0 0x7fbb5da03b6f in poll () from /lib64/libc.so.6 #1 0x7fbb5c108ace in g_main_context_iterate.constprop () from
[krita] [Bug 423752] Crash can be induced with 4.3.0 onwards after copying a vector layer to another open image
https://bugs.kde.org/show_bug.cgi?id=423752 Anna Medonosova changed: What|Removed |Added Attachment #130072|back|backtrace of the crash description|| -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 423752] Crash can be induced with 4.3.0 onwards after copying a vector layer to another open image
https://bugs.kde.org/show_bug.cgi?id=423752 --- Comment #2 from Anna Medonosova --- Created attachment 130072 --> https://bugs.kde.org/attachment.cgi?id=130072=edit back -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 423752] Crash can be induced with 4.3.0 onwards after copying a vector layer to another open image
https://bugs.kde.org/show_bug.cgi?id=423752 Anna Medonosova changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||anna.medonosova@protonmail. ||com --- Comment #1 from Anna Medonosova --- I can reproduce this issue in krita-5.0.0-prealpha-dd8d748-x86_64.appimage -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 423752] Crash can be induced with 4.3.0 onwards after copying a vector layer to another open image
https://bugs.kde.org/show_bug.cgi?id=423752 Anna Medonosova changed: What|Removed |Added Keywords||triaged -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 423959] The ppi of an image affects the pixel size of vector objects copied into it and creates artifacts with layer copying.
https://bugs.kde.org/show_bug.cgi?id=423959 Anna Medonosova changed: What|Removed |Added Status|REPORTED|CONFIRMED CC||anna.medonosova@protonmail. ||com Ever confirmed|0 |1 --- Comment #1 from Anna Medonosova --- I can confirm both issues in 4.3.0 appimage and in locally compiled git master. Krita Version: 4.3.0 Languages: C Hidpi: true Qt Version (compiled): 5.12.8 Version (loaded): 5.12.8 OS Information Build ABI: x86_64-little_endian-lp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: linux Kernel Version: 5.4.0-40-generic Pretty Productname: Ubuntu 20.04 LTS Product Type: ubuntu Product Version: 20.04 Desktop: KDE OpenGL Info Vendor: "Intel" Renderer: "Mesa Intel(R) HD Graphics 620 (KBL GT2)" Version: "4.6 (Compatibility Profile) Mesa 20.0.8" Shading language: "4.60" Requested format: QSurfaceFormat(version 3.0, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::CompatibilityProfile) Current format:QSurfaceFormat(version 4.6, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::CompatibilityProfile) Version: 4.6 Supports deprecated functions true is OpenGL ES: false QPA OpenGL Detection Info supportsDesktopGL: true supportsOpenGLES: true isQtPreferOpenGLES: false Hardware Information GPU Acceleration: auto Memory: 7849 Mb Number of Cores: 4 Swap Location: /tmp/user/1000 Current Settings Current Swap Location: /tmp/user/1000 Current Swap Location writable: true Undo Enabled: true Undo Stack Limit: 30 Use OpenGL: true Use OpenGL Texture Buffer: true Use AMD Vectorization Workaround: false Canvas State: OPENGL_SUCCESS Autosave Interval: 900 Use Backup Files: true Number of Backups Kept: 1 Backup File Suffix: ~ Backup Location: Same Folder as the File Backup Location writable: false Use Win8 Pointer Input: false Use RightMiddleTabletButton Workaround: false Levels of Detail Enabled: false Use Zip64: false Display Information Number of screens: 2 Screen: 0 Name: HDMI-2 Depth: 24 Scale: 1 Resolution in pixels: 1920x1080 Manufacturer: NEC Corporation Model: EA224WMi- Refresh Rate: 60 Screen: 1 Name: eDP-1 Depth: 24 Scale: 1 Resolution in pixels: 1920x1080 Manufacturer: Chimei Innolux Corporation Model: Refresh Rate: 60 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 423959] The ppi of an image affects the pixel size of vector objects copied into it and creates artifacts with layer copying.
https://bugs.kde.org/show_bug.cgi?id=423959 Anna Medonosova changed: What|Removed |Added Keywords||triaged -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 422843] Unable to save a document with selection
https://bugs.kde.org/show_bug.cgi?id=422843 --- Comment #5 from Anna Medonosova --- Update: raster selection seems to be unaffected, however, I can't save a vector selection. It might be related to bug https://bugs.kde.org/show_bug.cgi?id=422312 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 422843] Unable to save a document with selection
https://bugs.kde.org/show_bug.cgi?id=422843 Anna Medonosova changed: What|Removed |Added Summary|"Save As" does not work |Unable to save a document |from documents opened from |with selection |GDrive | -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 422843] "Save As" does not work from documents opened from GDrive
https://bugs.kde.org/show_bug.cgi?id=422843 --- Comment #3 from Anna Medonosova --- Created attachment 129394 --> https://bugs.kde.org/attachment.cgi?id=129394=edit file producing the error -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 422843] "Save As" does not work from documents opened from GDrive
https://bugs.kde.org/show_bug.cgi?id=422843 --- Comment #2 from Anna Medonosova --- I have done other tests and I think I have identified this issue wrongly. The problem seems unrelated to file storage, it rather is an issue with saving a file with selections. Scenario A 1. Create a document 2. Make a selection with any of the selection tools 3. Save the document Scenario B 1. Create a document 2. Add local selection mask to a layer 3. Save the document Scenario C 1. Open the document attached to this bug 2. Save the document All those scenarios produce the error on my device. The path I save to is /storage/emulated/0/Pictures. In scenario C, I can save the file after I delete the local selection mask attached to layer "local selection". I'm sorry for the confusion. -- You are receiving this mail because: You are watching all bug changes.
