[Plasma Vault] [Bug 410457] System Integration for cloud usage (mounting/unlocking)
https://bugs.kde.org/show_bug.cgi?id=410457 Ivan Čukić changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |INTENTIONAL --- Comment #4 from Ivan Čukić --- To repeat, if you want encryption just for the cloud sync, which is unlocked while you're logged in, Vault is not the solution. It is not Vault's use-case. Vault is *not* going to support use-cases which blur the best practices for its use-case. One of the interesting things I've been researching recently (which might end up as a new KDE project at one point) is git+gpg which provides a nice end-to-end encryption. The local files are not encrypted, but they are sent properly encrypted to a git server. This would be a good tool for your use-case. As mentioned before, the alternative is to set up the usual encrypted $HOME (or some other directory) and sync the encrypted data with your cloud provider. This would have the benefit of gpg+git with added protection against device theft if it is stolen while powered off. P.S. Bug status is meant for developers to classify bugs. While we all appreciate the discussion, there is no point in reopening a bug unless a developer reopens it because the discussion made them see the problem in a different light. -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 410457] System Integration for cloud usage (mounting/unlocking)
https://bugs.kde.org/show_bug.cgi?id=410457 Ivan Čukić changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |INTENTIONAL --- Comment #2 from Ivan Čukić --- There are already better tools for this use-case. You should encrypt user's home directory, or better, create an encrypted /home partition. The same goes for PAM - if you want encryption that integrates with login, Vault is not the solution. Integration with KWallet is out of the question as it would render Vaults useless. Anyone who has access to a computer with the user logged in would have access to all Vaults as getting the password from KWallet is as simple as invoking a single command in shell. There is no point in keeping something encrypted if the encryption key is easily accessible. Vaults are meant and designed to be small encrypted containers _under_ your regular security (be it a simple login or an encrypted drive etc.) that are in the locked state for as much as they can be. That is the reason closing a vault can be easily done and easily automated (activit switching, kde connect commands) while requiring an explicit action to open them. As for cloud storage, the encrypted data can be synced without the vault being open. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 308267] Home view, net total of preferred accounts doesn't include stocks
https://bugs.kde.org/show_bug.cgi?id=308267 Ivan changed: What|Removed |Added Status|RESOLVED|REOPENED Ever confirmed|0 |1 Resolution|WORKSFORME |--- CC||ivanperezdoming...@gmail.co ||m --- Comment #4 from Ivan --- I can add information to this bug, and I'd like to reopen. In KMM 5.1.1 AppImage on Linux (Ubuntu 18.04 64 bit), the preferred account section shows three columns: Account, Current Balance, and To Minimum Balance/Maximum Credit. The column Current Balance does not take brokerage/stock accounts into account when calculating the total. So, it shows the account balance correctly for each individual account, but then the total is not the sum of that column. I have tried this with two accounts only, a checking account and an investing account with shares. The sum matches the checking account and the investing account is ignored. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 424138] Report with tags does not show split transactions with tags.
https://bugs.kde.org/show_bug.cgi?id=424138 --- Comment #5 from Ivan --- In case it's useful, I'm seeing this bug on Ubuntu 18.04 with the stable AppImage. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 424138] Report with tags does not show split transactions with tags.
https://bugs.kde.org/show_bug.cgi?id=424138 Ivan changed: What|Removed |Added CC||ivanperezdoming...@gmail.co ||m --- Comment #4 from Ivan --- I can confirm that this bug is present in KMM 5.1.1 (build ba2c445) which, as of the time of this writing, I think is the last stable version. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 431549] Multi X-pointer second keyboard input does not work even when invoked
https://bugs.kde.org/show_bug.cgi?id=431549 --- Comment #2 from Ivan Tham --- So multi-pointer will never be supported in Qt? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 431549] Multi X-pointer second keyboard input does not work even when invoked
https://bugs.kde.org/show_bug.cgi?id=431549 Ivan Tham changed: What|Removed |Added CC||pickf...@riseup.net -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 431549] New: Multi X-pointer second keyboard input does not work even when invoked
https://bugs.kde.org/show_bug.cgi?id=431549 Bug ID: 431549 Summary: Multi X-pointer second keyboard input does not work even when invoked Product: plasmashell Version: 5.20.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: k...@davidedmundson.co.uk Reporter: pickf...@riseup.net CC: mikel5...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 SUMMARY Second keyboard for second pointer (or input master) does not work even though the second keyboard is used to open kickoff (and the same thing happened to krunner), even when the second keyboard is used to start kickoff but only the first keyboard (in first input master) is able to type something. STEPS TO REPRODUCE 1. xinput create-master 2. xinput reattach (all the second mouse and keyboard) https://wiki.archlinux.org/index.php/Multi-pointer_X#xinput_utility 3. super (I binded it to alt-f1) from the second input master/keyboard 4. Type something from the second input master/keyboard OBSERVED RESULT Only the keyboard from first input master is able to type something, the second input master is not able to type anything, even if the second pointer is updated to use the first input master. The same thing is observed for krunner. EXPECTED RESULT Second keyboard from second input master should be able to search kickoff instead of the first keyboard from first input master since it is the one that initiated it, also the first keyboard should also be able to input if the if the first pointer clicked on kickoff search bar. Right now second keyboard can't even enter anything even if the second pointer clicked on the search bar. The same thing is expected from krunner. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Linux mi 5.10.6-zen1-1-zen #1 ZEN SMP PREEMPT Sat, 09 Jan 2021 18:22:39 + x86_64 GNU/Linux (available in About System) Operating System: Arch Linux KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 Kernel Version: 5.10.6-zen1-1-zen OS Type: 64-bit Processors: 6 × AMD Ryzen 5 4500U with Radeon Graphics Memory: 15.1 GiB of RAM Graphics Processor: AMD RENOIR ADDITIONAL INFORMATION This happens to krunner as well. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422682] "Show in Activities" item is missing in window menu
https://bugs.kde.org/show_bug.cgi?id=422682 --- Comment #11 from Ivan Čukić --- Hm, I don't like that it is ok with a clean user. Means that some setting in kwin can hide this. If you figure out what was the problem or how to reproduce, please report. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422682] "Show in Activities" item is missing in window menu
https://bugs.kde.org/show_bug.cgi?id=422682 --- Comment #6 from Ivan Čukić --- Is it possible that kwin on arch is compiled without development headers of kactivities? -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 430058] Several seconds of random lag in UI
https://bugs.kde.org/show_bug.cgi?id=430058 --- Comment #3 from Ivan Čukić --- Hi Steve, Those files are automatically handled by sqlite. WAL is a write-ahead-log - a technique sqlite uses to avoid updating the database for each sql insert/update command. It writes the updates to WAL and then merges a chunk of them at once. KAMD only tells sqlite to flush WAL every 400k instead of the default 4M. Now, sqlite is free to ignore this request - it flushes only if the flush can be fast enough. So, the WAL file can grow more than that. This code (in KAMD) hasn't really been changed in 5 years. Did freebsd get a new version of sqlite recently? Now, Inkscape and KAMD have nothing in common - if KAMD manages to slow down Inkscape, my guess is that the OS doesn't handle file writes as it should. Maybe Inkscape is also trying to write something to the hard drive. Can you watch whe process IO with iotop to see what KAMD and Inkscape do when you experience the slowdown. Also, can you track the RAM usage while this happens? -- You are receiving this mail because: You are watching all bug changes.
[i18n] [Bug 430881] Icon title consumes too much space (at least in Russian translation)
https://bugs.kde.org/show_bug.cgi?id=430881 Ivan Čukić changed: What|Removed |Added Component|general |ru CC||ivan.cu...@kde.org, ||kekc...@gmail.com Assignee|aa...@kde.org |aspotas...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[i18n] [Bug 430881] Icon title consumes too much space (at least in Russian translation)
https://bugs.kde.org/show_bug.cgi?id=430881 Ivan Čukić changed: What|Removed |Added Assignee|ivan.cu...@kde.org |aa...@kde.org Status|REPORTED|CONFIRMED Product|Plasma Vault|i18n Ever confirmed|0 |1 Component|general |general --- Comment #1 from Ivan Čukić --- Moving to i18n as this is (IMO) a translation problem. I'd say the translation is overly literal - almost as translating Plasma as "системный пользовательский интерфейс" everywhere instead of using the product name. The product name is Vault. It could be translated to Russian as сейф. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 428085] "Often Used/Recent file" list doesn't work as expected
https://bugs.kde.org/show_bug.cgi?id=428085 Ivan Čukić changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED --- Comment #9 from Ivan Čukić --- > not yet landed and its commit will be different. It has, and the commit that fixes the issue is the one linked (it was a merge, not a rebase, so the sha is preserved) Fix to be released in 5.77 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 428085] "Often Used/Recent file" list doesn't work as expected
https://bugs.kde.org/show_bug.cgi?id=428085 Ivan Čukić changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED Latest Commit||https://invent.kde.org/fram ||eworks/kactivities-stats/co ||mmit/6faad8ed5f76510de06707 ||836d6406e7177086a3 --- Comment #7 from Ivan Čukić --- Git commit 6faad8ed5f76510de06707836d6406e7177086a3 by Ivan Čukić. Committed on 19/11/2020 at 17:39. Pushed by ivan into branch 'ivan/event-filtering-for-files-and-directories'. Add event filtering for files and directories The df52b1a3 revision introduced Type::files and Type::directories special resource type values for queries, but it omitted to support the same special values in the ResultWatcher. M +10 -1src/resultwatcher.cpp https://invent.kde.org/frameworks/kactivities-stats/commit/6faad8ed5f76510de06707836d6406e7177086a3 -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 411900] Tracking activity
https://bugs.kde.org/show_bug.cgi?id=411900 --- Comment #2 from Ivan Čukić --- This is something that kinda existed in Plasma 4.x (for Plasma Active) when kactivitymanagerd followed a 'let's add everything into it' kind of an application. KAMD grew too much to be maintainable, so the scope is now more focussed. I agree that this would be a great thing to have in Plasma, but not as a part of KAMD. A separate time tracking application / plasma applet / system tray applet that integrates with activities* would be quite easy to implement. If anyone is game, I could mentor the project. At least the activities integration part. * Plasma Vault was also in a sense a part of KAMD in Plasma Active days, and now it is a separate applet that integrates with activities. And, IMO, much better than what we had back then. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 366454] Right Alt does not change ketboard language layout back to English, both Win keys do not change layout at all
https://bugs.kde.org/show_bug.cgi?id=366454 --- Comment #2 from Ivan --- (In reply to Justin Zobel from comment #1) > Thanks for the report Ivan. I've just tested this on systemsettings 5.20.2 > and I can't replicate the issue. I was able to toggle between layouts with > right alt. > > Can you please test and confirm if this issue is still occurring or if this > bug report can be marked as resolved. I'm setting status to "needsinfo" > pending your response, please change back to "reported" or "resolved" when > you respond, thanks. Thanks for testing. It's been a while since this bug disappeared, however long enough for me to forget about the report. I've tested key combinations on systemsettings 5.20.3 and everything was working too. Lets close this ticket and thank you again for your efforts. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 428468] icon-only task manager crash when move icons position on Wayland
https://bugs.kde.org/show_bug.cgi?id=428468 --- Comment #2 from Ivan --- This is not possible (or maybe i'm not able) just because plasma crashes immediately and the user is logged out -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 428468] New: icon-only task manager crash when move icons position on Wayland
https://bugs.kde.org/show_bug.cgi?id=428468 Bug ID: 428468 Summary: icon-only task manager crash when move icons position on Wayland Product: plasmashell Version: 5.20.2 Platform: Neon Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: Task Manager and Icons-Only Task Manager Assignee: h...@kde.org Reporter: gulpega...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY In the icon-only task manager, when I try to change a position of a pinned icon (dragging it by mouse), plasma crashes. It happens only in Wayland. STEPS TO REPRODUCE 1. Drag an icon on the icon-only task manager to change its position OBSERVED RESULT Plasma crashes and a new login is required EXPECTED RESULT Icon change its position in the task manager SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE neon 5.20 (available in About System) KDE Plasma Version: 5.20.2 KDE Frameworks Version: 5.75.0 Qt Version: 5.15.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 428447] icon-only task manager application launch animation missing on Wayland
https://bugs.kde.org/show_bug.cgi?id=428447 Ivan changed: What|Removed |Added CC||gulpega...@gmail.com --- Comment #4 from Ivan --- I confirm the issue reported by Pawel. No animation on the task manager icons and no bouncing/blinking mouse pointer. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 406379] Magnet Links not recognised correctly
https://bugs.kde.org/show_bug.cgi?id=406379 Ivan Tham changed: What|Removed |Added CC||pickf...@riseup.net -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 409070] Ktorrent not handling magnet links
https://bugs.kde.org/show_bug.cgi?id=409070 Ivan Tham changed: What|Removed |Added CC||pickf...@riseup.net --- Comment #6 from Ivan Tham --- The issue is the magnet link is prepended with the original url. Related issue, https://bugs.kde.org/show_bug.cgi?id=406379 and https://bugs.kde.org/show_bug.cgi?id=392321 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 428092] New: Ugly color title background in system tray when Breeze Dark is selected
https://bugs.kde.org/show_bug.cgi?id=428092 Bug ID: 428092 Summary: Ugly color title background in system tray when Breeze Dark is selected Product: Breeze Version: 5.20.1 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: QStyle Assignee: unassigned-b...@kde.org Reporter: gulpega...@gmail.com Target Milestone: --- Created attachment 132627 --> https://bugs.kde.org/attachment.cgi?id=132627&action=edit Clipboard widget SUMMARY Ugly color title background in system tray when Breeze Dark is selected STEPS TO REPRODUCE 1. Select "Breeze Dark" in Plasma Stlyle. 2. Left click on every widget in system tray (es. clipboard, audio volume). OBSERVED RESULT The widget title and his background color are too similar. EXPECTED RESULT Better color contrast SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon 5.20 (available in About System) KDE Plasma Version: 5.20.1 KDE Frameworks Version: 5.75.0 Qt Version: 5.15.0 -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 427650] kactivitymanagerd crashes with segmentation fault
https://bugs.kde.org/show_bug.cgi?id=427650 Ivan Čukić changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #5 from Ivan Čukić --- @Albert Great, thanks for testing! -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 427650] kactivitymanagerd crashes with segmentation fault
https://bugs.kde.org/show_bug.cgi?id=427650 --- Comment #4 from Ivan Čukić --- Git commit 590778d6f105e11f4521d5bed65ac0e30b086132 by Ivan Čukić. Committed on 15/10/2020 at 06:49. Pushed by ivan into branch 'Plasma/5.20'. Fix a dangling reference to the list of database files M +2-1src/service/plugins/sqlite/Database.cpp https://invent.kde.org/plasma/kactivitymanagerd/commit/590778d6f105e11f4521d5bed65ac0e30b086132 -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 427650] kactivitymanagerd crashes with segmentation fault
https://bugs.kde.org/show_bug.cgi?id=427650 --- Comment #3 from Ivan Čukić --- Git commit 847c1dbed6b422211285fb19d7fd07d8112349ff by Ivan Čukić. Committed on 15/10/2020 at 06:45. Pushed by ivan into branch 'master'. Fix a dangling reference to the list of database files M +2-1src/service/plugins/sqlite/Database.cpp https://invent.kde.org/plasma/kactivitymanagerd/commit/847c1dbed6b422211285fb19d7fd07d8112349ff -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 427650] kactivitymanagerd crashes with segmentation fault
https://bugs.kde.org/show_bug.cgi?id=427650 --- Comment #1 from Ivan Čukić --- Git commit 4e48431b0b4d9b8d73002d55ffb01d2a864f1b91 by Ivan Čukić. Committed on 14/10/2020 at 08:43. Pushed by ivan into branch 'ivan/fix-dangling-reference-crash-in-db-error-handling'. Fix a dangling reference to the list of database files M +2-1src/service/plugins/sqlite/Database.cpp https://invent.kde.org/plasma/kactivitymanagerd/commit/4e48431b0b4d9b8d73002d55ffb01d2a864f1b91 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 420590] System Settings Crashin
https://bugs.kde.org/show_bug.cgi?id=420590 --- Comment #3 from Ivan --- When I click for second time in any section. Recent log: KDE Version: 5.19.5 Qt Version: 5.15.1 Frameworks Version: 5.75.0 Operating System: Linux 5.8.11-1-MANJARO x86_64 Windowing system: X11 Distribution: Manjaro Linux Application: Configurações do sistema (systemsettings5), signal: Segmentation fault [KCrash Handler] #4 0x in ?? () #5 0x7f61af46b137 in ?? () from /usr/lib/libQt5Quick.so.5 #6 0x7f61af46b179 in ?? () from /usr/lib/libQt5Quick.so.5 #7 0x7f61af5ea103 in ?? () from /usr/lib/libQt5Quick.so.5 #8 0x7f61ab210c9a in ?? () from /usr/lib/libQt5XcbQpa.so.5 #9 0x7f61ab212f24 in ?? () from /usr/lib/libQt5XcbQpa.so.5 #10 0x7f61ab214661 in ?? () from /usr/lib/libQt5XcbQpa.so.5 #11 0x7f61af47d60d in QQuickItemPrivate::setEffectiveVisibleRecur(bool) () from /usr/lib/libQt5Quick.so.5 #12 0x7f61af47d6f5 in QQuickItemPrivate::setVisible(bool) () from /usr/lib/libQt5Quick.so.5 #13 0x7f61a00697d1 in ?? () from /usr/lib/qt/qml/org/kde/kirigami.2/libkirigamiplugin.so #14 0x7f61a006add8 in ?? () from /usr/lib/qt/qml/org/kde/kirigami.2/libkirigamiplugin.so #15 0x7f61af478185 in QQuickItemPrivate::itemChange(QQuickItem::ItemChange, QQuickItem::ItemChangeData const&) () from /usr/lib/libQt5Quick.so.5 #16 0x7f61af47f044 in QQuickItemPrivate::removeChild(QQuickItem*) () from /usr/lib/libQt5Quick.so.5 #17 0x7f61af480ef3 in QQuickItem::setParentItem(QQuickItem*) () from /usr/lib/libQt5Quick.so.5 #18 0x7f61af481497 in QQuickItem::~QQuickItem() () from /usr/lib/libQt5Quick.so.5 #19 0x7f618d704037 in ?? () from /usr/lib/qt/qml/QtQuick/Templates.2/libqtquicktemplates2plugin.so #20 0x7f61af7a47b9 in KDeclarative::QmlObject::~QmlObject() () from /usr/lib/libKF5Declarative.so.5 #21 0x7f61af7a504a in KDeclarative::QmlObjectSharedEngine::~QmlObjectSharedEngine() () from /usr/lib/libKF5Declarative.so.5 #22 0x7f61b15b261c in KQuickAddons::ConfigModule::~ConfigModule() () from /usr/lib/libKF5QuickAddons.so.5 #23 0x7f6170e663b3 in ?? () from /usr/lib/qt/plugins/kcms/kcm_lookandfeel.so #24 0x7f61b16b2263 in ?? () from /usr/lib/libKF5KCMUtils.so.5 #25 0x7f61b16b2289 in ?? () from /usr/lib/libKF5KCMUtils.so.5 #26 0x7f61b16b86f4 in KCModuleProxy::deleteClient() () from /usr/lib/libKF5KCMUtils.so.5 #27 0x7f61b16b8869 in KCModuleProxy::~KCModuleProxy() () from /usr/lib/libKF5KCMUtils.so.5 #28 0x7f61b16b892a in KCModuleProxy::~KCModuleProxy() () from /usr/lib/libKF5KCMUtils.so.5 #29 0x7f61b004b36e in QObjectPrivate::deleteChildren() () from /usr/lib/libQt5Core.so.5 #30 0x7f61b0bab04e in QWidget::~QWidget() () from /usr/lib/libQt5Widgets.so.5 #31 0x7f61b0bab3ca in QWidget::~QWidget() () from /usr/lib/libQt5Widgets.so.5 #32 0x7f61b004b36e in QObjectPrivate::deleteChildren() () from /usr/lib/libQt5Core.so.5 #33 0x7f61b0bab04e in QWidget::~QWidget() () from /usr/lib/libQt5Widgets.so.5 #34 0x7f61b0d0882a in QScrollArea::~QScrollArea() () from /usr/lib/libQt5Widgets.so.5 #35 0x7f61b1400118 in KPageWidgetItem::~KPageWidgetItem() () from /usr/lib/libKF5WidgetsAddons.so.5 #36 0x7f61b1400216 in ?? () from /usr/lib/libKF5WidgetsAddons.so.5 #37 0x7f61b1401574 in KPageWidgetModel::removePage(KPageWidgetItem*) () from /usr/lib/libKF5WidgetsAddons.so.5 #38 0x7f61b16f19f6 in ModuleView::closeModules() () from /usr/lib/libsystemsettingsview.so.3 #39 0x7f61a319f29c in ?? () from /usr/lib/qt/plugins/systemsettings_sidebar_mode.so #40 0x7f61a319d82e in ?? () from /usr/lib/qt/plugins/systemsettings_sidebar_mode.so #41 0x7f61a319dd53 in ?? () from /usr/lib/qt/plugins/systemsettings_sidebar_mode.so #42 0x7f61af08c50e in ?? () from /usr/lib/libQt5Qml.so.5 #43 0x7f61aef7203f in ?? () from /usr/lib/libQt5Qml.so.5 #44 0x7f61aef73eda in QV4::QObjectMethod::callInternal(QV4::Value const*, QV4::Value const*, int) const () from /usr/lib/libQt5Qml.so.5 #45 0x7f61aef8fad7 in ?? () from /usr/lib/libQt5Qml.so.5 #46 0x7f61aef9262f in ?? () from /usr/lib/libQt5Qml.so.5 #47 0x7f61aef2ccce in QV4::Function::call(QV4::Value const*, QV4::Value const*, int, QV4::ExecutionContext const*) () from /usr/lib/libQt5Qml.so.5 #48 0x7f61af0a98d6 in QQmlJavaScriptExpression::evaluate(QV4::CallData*, bool*) () from /usr/lib/libQt5Qml.so.5 #49 0x7f61af05b5cd in QQmlBoundSignalExpression::evaluate(void**) () from /usr/lib/libQt5Qml.so.5 #50 0x7f61af05bab1 in ?? () from /usr/lib/libQt5Qml.so.5 #51 0x7f61af08bfad in QQmlNotifier::emitNotify(QQmlNotifierEndpoint*, void**) () from /usr/lib/libQt5Qml.so.5 #52 0x7f61b0057bb5 in ?? () from /usr/lib/libQt5Core.so.5 #53 0x7f61aa420712 in QQuickAbstractButtonPrivate::handleRelease(QPointF const&) () from /usr/lib/libQt5QuickTemplates2.so.5 #54 0x7f61aa43dff1 in QQuickControl::mouseReleaseEvent(QMouseEvent*) () from /usr/lib/libQt5QuickTemplates2.
[ksysguard] [Bug 426053] ksysguard - delete tab option unavailable
https://bugs.kde.org/show_bug.cgi?id=426053 --- Comment #4 from Ivan Tsulimov --- (In reply to Christoph Feck from comment #3) > Only those tabs can be closed that you added manually using "New Tab". Why i'm not allowed to remove tab, that i have imported by myself few seconds ago? What if i don't need this tab anymore, or i have added it by mistake? -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 426963] kactivitymanagerd continuously crashing
https://bugs.kde.org/show_bug.cgi?id=426963 --- Comment #6 from Ivan Čukić --- Thanks. Seems that database disk corruption can be exposed randomly during work. KAMD performs some tests on startup and restores the last database known to work. But it does not cover these errors. Will see how to handle these. -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 426963] kactivitymanagerd continuously crashing
https://bugs.kde.org/show_bug.cgi?id=426963 --- Comment #3 from Ivan Čukić --- Can you start kactivitymanagerd from shell and post the output here? -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 426053] ksysguard - delete tab option unavailable
https://bugs.kde.org/show_bug.cgi?id=426053 --- Comment #2 from Ivan Tsulimov --- (In reply to David Redondo from comment #1) > To make sure, you don't have the "close tab" option in the file menu? yep -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 426053] ksysguard - delete tab option unavailable
https://bugs.kde.org/show_bug.cgi?id=426053 Ivan Tsulimov changed: What|Removed |Added Summary|delete tab option |ksysguard - delete tab |unavailable |option unavailable -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 426053] New: delete tab option unavailable
https://bugs.kde.org/show_bug.cgi?id=426053 Bug ID: 426053 Summary: delete tab option unavailable Product: ksysguard Version: 5.18.4 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: ksysguard Assignee: ksysguard-b...@kde.org Reporter: osth...@yandex.ru CC: plasma-b...@kde.org Target Milestone: --- SUMMARY delete tab option unavailable STEPS TO REPRODUCE 1. open ksysguard 2. add some new tab via file->dowload new tabs 3. try to remove added tab OBSERVED RESULT no way to do it EXPECTED RESULT see option like "delete tab" in menu "File" or anywhere SOFTWARE/OS VERSIONS Kubuntu 20.04.1 KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 374575] "Shortcut for switching to this activity" has no effect when set from the Activities KCM
https://bugs.kde.org/show_bug.cgi?id=374575 --- Comment #23 from Ivan Čukić --- I proposed removing this some time ago as the shortcut can be set from Shortcuts KCM, but I was told it will be fixed. That hasn't happened, so I'm in favor of removing this part of the configuration. Expect the patch soon. -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 419499] Switch activity shortcut order
https://bugs.kde.org/show_bug.cgi?id=419499 --- Comment #9 from Ivan Čukić --- After switching from A to B activity, you are in activity B, and the order in the switcher when you open it again is the same as before you switched to B? -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 419499] Switch activity shortcut order
https://bugs.kde.org/show_bug.cgi?id=419499 --- Comment #7 from Ivan Čukić --- I've added an attachment that shows the default behaviour. What happens in your case? -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 419499] Switch activity shortcut order
https://bugs.kde.org/show_bug.cgi?id=419499 --- Comment #6 from Ivan Čukić --- Created attachment 130311 --> https://bugs.kde.org/attachment.cgi?id=130311&action=edit Default behaviour -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 419499] Switch activity shortcut order
https://bugs.kde.org/show_bug.cgi?id=419499 --- Comment #3 from Ivan Čukić --- @Adam By default, Meta+Shift+Tab switches to the least recently used activity (activity at the oposite end). -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 424063] If password has been made visible, it should be hidden again the moment the user clicks the "OK" button
https://bugs.kde.org/show_bug.cgi?id=424063 --- Comment #10 from Ivan Čukić --- @Nate Characters can't (shouldn't) be encrypted one by one. @lestofante Something like that could be doable with some encryption schemes. -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 424063] If password has been made visible, it should be hidden again the moment the user clicks the "OK" button
https://bugs.kde.org/show_bug.cgi?id=424063 --- Comment #7 from Ivan Čukić --- It will hide *and* clear the field. This is to follow the new screen locker policy (or did I dream it Nate?). Password reveal button is useful, though it kills the point of having a long passphrase :) The main issue I have with it (apart from the over-the-shoulder ones like this bug was) is that in order to have the reveal button, the string needs to sit in memory unencrypted. If password fields were simpler (no reveal, no left-right arrow keys, no random character deletion/change), each char could be encrypted as soon as it is entered without decrypting the old ones. -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 424063] If password has been made visible, it should be hidden again the moment the user clicks the "OK" button
https://bugs.kde.org/show_bug.cgi?id=424063 --- Comment #4 from Ivan Čukić --- The reveal button is one of the worst things that ever happened to password entry fields... Thanks for reporting this! -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 424063] If password has been made visible, it should be hidden again the moment the user clicks the "OK" button
https://bugs.kde.org/show_bug.cgi?id=424063 Ivan Čukić changed: What|Removed |Added Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/plasma-vault/commit/c493 |ma/plasma-vault/commit/5e6a |2f99056ff348e354e95fcbdd1af |53ba55fd60ace3adbd4ca57f90a |28f25c5ef |5cd44992f --- Comment #3 from Ivan Čukić --- Git commit 5e6a53ba55fd60ace3adbd4ca57f90a5cd44992f by Ivan Čukić. Committed on 12/07/2020 at 15:45. Pushed by ivan into branch 'Plasma/5.19'. Reset password field when the user clicks Ok - Clear the password on unsuccessful vault open - If the user clicked to show the password, it gets hidden as soon as Ok is clicked M +2-0kded/ui/mountdialog.cpp https://invent.kde.org/plasma/plasma-vault/commit/5e6a53ba55fd60ace3adbd4ca57f90a5cd44992f -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 424063] If password has been made visible, it should be hidden again the moment the user clicks the "OK" button
https://bugs.kde.org/show_bug.cgi?id=424063 Ivan Čukić changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/plas ||ma/plasma-vault/commit/c493 ||2f99056ff348e354e95fcbdd1af ||28f25c5ef Status|CONFIRMED |RESOLVED --- Comment #2 from Ivan Čukić --- Git commit c4932f99056ff348e354e95fcbdd1af28f25c5ef by Ivan Čukić. Committed on 12/07/2020 at 15:42. Pushed by ivan into branch 'master'. Reset password field when the user clicks Ok - Clear the password on unsuccessful vault open - If the user clicked to show the password, it gets hidden as soon as Ok is clicked M +2-0kded/ui/mountdialog.cpp https://invent.kde.org/plasma/plasma-vault/commit/c4932f99056ff348e354e95fcbdd1af28f25c5ef -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 423994] Accounts from a template are not being created
https://bugs.kde.org/show_bug.cgi?id=423994 --- Comment #2 from Ivan --- (In reply to Jack from comment #1) > Templates don't create accounts, they create categories. The terminology > can easily be confusing, because internally, categories are a special type > of account. I don't believe there are any cases where initial setup creates > any accounts for you, other than the setup wizard asking if you want to set > up an initial checking account. Yes, thank you for the answer. The terminology is confusing. I just thought that this is something similar to GnuCash. I think, we can close the bug now :) -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 423994] New: Accounts from a template are not being created
https://bugs.kde.org/show_bug.cgi?id=423994 Bug ID: 423994 Summary: Accounts from a template are not being created Product: kmymoney Version: git (master) Platform: MS Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: ivan.zinkev...@gmail.com Target Milestone: --- SUMMARY I'm trying to create a default set of accounts, but I don't see any when I created a new file. STEPS TO REPRODUCE 1. Start "New file" wizard 2. Select currency "USD" 3. Select "Base - detail" 4. Open "Accounts" tab 5. There are no accounts from the template. OBSERVED RESULT EXPECTED RESULT Accounts from the template are added. SOFTWARE/OS VERSIONS Windows: 10 (available in About System) KDE Plasma Version: The windows windowing system KDE Frameworks Version: 5.71.0 Qt Version: 5.15.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 422836] Vaults don't open, even though dolphin launches there
https://bugs.kde.org/show_bug.cgi?id=422836 Ivan Čukić changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |UPSTREAM --- Comment #2 from Ivan Čukić --- Hi, you should open a bug report on cryfs [1] as it is issue in it. There is a possibility that the underlying file system was corrupted so the cryfs key can not be opened, but cryfs maintainers will know the cause and the potential fix better than I. [1] https://github.com/cryfs/cryfs/issues -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422779] Alt+Tab left pane shows huge virtual keyboard underneath open windows
https://bugs.kde.org/show_bug.cgi?id=422779 Ivan Čukić changed: What|Removed |Added Assignee|ivan.cu...@kde.org |k...@davidedmundson.co.uk Component|Activity Switcher |general -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 422429] Guides are always drag while editing
https://bugs.kde.org/show_bug.cgi?id=422429 --- Comment #7 from Ivan Batalin --- Hi, Dmitry! Yes this problem a take in place. Thank you for hinting to code snippets for the review. As at last 15yeas I was using Linux at home and work, I'll try to build Krita in chroot sandbox by the official documentation: https://docs.krita.org/en/untranslatable_pages/building_krita.html -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422682] "Show in Activities" item is missing in window menu
https://bugs.kde.org/show_bug.cgi?id=422682 --- Comment #1 from Ivan Čukić --- I'd say this is a problem with Arch packages as that feature has not been removed - I use it on a daily basis. Also, there is a nicer way to move windows accross activities now - you can drag and drop tasks from the task bar onto the activitty switcher https://pointieststick.files.wordpress.com/2020/05/screenshot_20200512_155226.png -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 422429] Guides are always drag while editing
https://bugs.kde.org/show_bug.cgi?id=422429 Ivan Batalin changed: What|Removed |Added CC||direc...@oas.su --- Comment #5 from Ivan Batalin --- My vision of this problem, and several methods of solving for the best user experience, locking guides or switching to gimp/photoshops method are not correct by the Krita main ideology and design. The issue appears when you working with all tools without left mouse button (stylus pressure or a finger touch event) pressed. In this case guide selects immediately and prevents to drawing at this place, even snap to this guide. The most awful UX example is drawing with Polyline, Polygon, or Bezier Curve tool. There are three possible solutions to workaround this issue: The first - we are may limit tools, that can select the guides for the moving purposes, for example Select shapes, Edit Shapes, Move and Zoom tools (such as Inkscape does). The second - will be adding a small delay (for example 300ms) after activating guide in case of mouse hover event, but this solution are not perfect at all, and dissolves other user experience. The third possible solution - to disable selecting guides when tool are in active state (in the process of drawing, or selecting next point) without left button pressed. This solution was solved issue, but not in the cases when you must start drawing with snapping to the guide. This method can be combined with the second solution for the best effort. I may try to implement any of above solutions and contribute this patch to the upstream, if it will be needed by the developer community. Best regards, Ivan Batalin. -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 386200] Import Vault
https://bugs.kde.org/show_bug.cgi?id=386200 --- Comment #25 from Ivan Čukić --- Seems like the field validation does not happen always after the browse button. Will have to see what that is about. The slash should really be of no importance. It is removed so that people don't accidentally create /some/path and /some/path/ vaults. Thanks for the report! -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 386200] Import Vault
https://bugs.kde.org/show_bug.cgi?id=386200 --- Comment #22 from Ivan Čukić --- Sadly, no debugging output is present. Can you try one stupid thing - add a trailing slash manually to both paths? -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 386200] Import Vault
https://bugs.kde.org/show_bug.cgi?id=386200 --- Comment #19 from Ivan Čukić --- Hi Sylvain, Which version of cryfs dod you install? Did you select an existing, empty directory for the mount point? (seems like the error message does not appear always, need to investigate why) If the UI fails, you can 'import' by manally editing the config. 1. kquitapp5 kded5 2. killall kded5 3. cp ~/.config/plasmavaultrc ~/.config/plasmavaultrc.backup 4. open .config/plasmavaultrc in an editor of your choice 5. In the section [EncryptedDevices] add the device as /location/to/encrypted/data=true 6. Create a new section called [/location/to/encrypted/data] and add these fields in it: mountPoint=/path/to/an/empty/directory/where/you/want/the/vault/mounted backend=cryfs name=Name of the Vault 7. Save the file and "killall kded5" again just for good measure 8. Start kded5: kded5 &>/dev/null& 9. Check whether the things you added are still present in ~/.config/plasmavaultrc 10. Check whether you can mount the vault -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 399375] Default Window Actions Modifier Key is ALT and it breaks Krita's ALT modifier
https://bugs.kde.org/show_bug.cgi?id=399375 --- Comment #52 from Ivan Čukić --- @David @Nate Thanks! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 399375] Default Window Actions Modifier Key is ALT and it breaks Krita's ALT modifier
https://bugs.kde.org/show_bug.cgi?id=399375 Ivan Čukić changed: What|Removed |Added CC||ivan.cu...@kde.org --- Comment #49 from Ivan Čukić --- Changes like these should be accompanied by a notification to the user first time they try to use the old modifier to move the window. I thought something was broken in kwin these past few days until I saw Nate's blog post. I usually just glance over the list, but fortunately I had a thorough read this time. Also, did this change go through code review as I can't find it? -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 414956] cryfs vault unresponsive for a long time after mount
https://bugs.kde.org/show_bug.cgi?id=414956 --- Comment #8 from Ivan Čukić --- @Ken You should try from the terminal - when dolphin/krusader get blocked, test whether you can open some file in vim or another console editor. If that works, then you might be experiencing an issue that *is* somewhere in KDE (I assume krusader uses the same underlying libraries as dolpgin, though I might be mistaken) -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 414956] cryfs vault unresponsive for a long time after mount
https://bugs.kde.org/show_bug.cgi?id=414956 --- Comment #6 from Ivan Čukić --- @Zvi Yes, please :) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 349004] UI for activity switching provides poor feedback
https://bugs.kde.org/show_bug.cgi?id=349004 --- Comment #6 from Ivan Čukić --- Just as a note, there's a seemingly unrelated, but related new feature for 'the user knows what activity they've switched to' - the activity switcher applet (the one that opens the activity switcher) can be configured to show the icon and the name of the current activity instead of only showing dull generic icon. -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 414956] cryfs vault unresponsive for a long time after mount
https://bugs.kde.org/show_bug.cgi?id=414956 --- Comment #4 from Ivan Čukić --- @Ken You can open a separate bug report on Dolphin. Dolphin is not to blame for "Filesystem is not responding" reported by Zvi. There have been reports here of cryfs being blocked even in terminal. So, nothing to do with Dolphin. -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 414956] cryfs vault unresponsive for a long time after mount
https://bugs.kde.org/show_bug.cgi?id=414956 Ivan Čukić changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |UPSTREAM --- Comment #2 from Ivan Čukić --- Hi all, This is something that needs to be reported upstream. It would be great if you have the time to do so and provide the cryfs authors with feedback / more information they might need. -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 398323] Add gocryptfs support
https://bugs.kde.org/show_bug.cgi?id=398323 Ivan Čukić changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED Latest Commit||https://commits.kde.org/pla ||sma-vault/853b0be5a4ac9f6a0 ||2b1848d832871e7b16fec22 --- Comment #2 from Ivan Čukić --- Git commit 853b0be5a4ac9f6a02b1848d832871e7b16fec22 by Ivan Čukić, on behalf of Martino Pilia. Committed on 12/05/2020 at 16:38. Pushed by ivan into branch 'master'. Add gocryptfs support Summary: Implement basic support for gocryptfs backend. Reviewers: ivan, #plasma Reviewed By: ivan, #plasma Subscribers: ngraham, plasma-devel Tags: #plasma Differential Revision: https://phabricator.kde.org/D29595 M +1-0kded/CMakeLists.txt M +3-1kded/engine/backend_p.cpp A +212 -0kded/engine/backends/gocryptfs/gocryptfsbackend.cpp [License: GPL (v2/3)] A +54 -0kded/engine/backends/gocryptfs/gocryptfsbackend.h [License: GPL (v2/3)] M +6-6kded/engine/fusebackend_p.cpp M +4-0kded/ui/vaultconfigurationdialog.cpp M +31 -0kded/ui/vaultcreationwizard.cpp M +16 -0kded/ui/vaultimportingwizard.cpp M +3-2kded/ui/vaultwizardbase.h https://commits.kde.org/plasma-vault/853b0be5a4ac9f6a02b1848d832871e7b16fec22 -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 420784] Restore of Vaults fail
https://bugs.kde.org/show_bug.cgi?id=420784 --- Comment #12 from Ivan Čukić --- It also does it on startup - just async as it needs to wait for the activities list to be loaded from kamd. -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 420784] Restore of Vaults fail
https://bugs.kde.org/show_bug.cgi?id=420784 Ivan Čukić changed: What|Removed |Added Status|NEEDSINFO |RESOLVED --- Comment #10 from Ivan Čukić --- @Nate Nothing else to do here I think. Marking as resolved. @Justin No problem, glad to be of help! -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 420784] Restore of Vaults fail
https://bugs.kde.org/show_bug.cgi?id=420784 --- Comment #7 from Ivan Čukić --- Git commit 2befe1ffd7d75be3603e38270c5db2847083f292 by Ivan Čukić. Committed on 04/05/2020 at 14:39. Pushed by ivan into branch 'master'. Unassign activity from vault on activity deletion Summary: CCBUG: 420784 Reviewers: ngraham, davidedmundson, mart Reviewed By: mart Subscribers: plasma-devel Tags: #plasma Differential Revision: https://phabricator.kde.org/D29379 M +60 -14 kded/service.cpp M +2-0kded/service.h https://commits.kde.org/plasma-vault/2befe1ffd7d75be3603e38270c5db2847083f292 -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 420784] Restore of Vaults fail
https://bugs.kde.org/show_bug.cgi?id=420784 --- Comment #6 from Ivan Čukić --- Incomplete backup restoration is not something I can cover in the general case. But, I have been planning to handle missing activities more gracefully. The usual mantra for encryption is that data loss is preferred to a data leak, but I guess that the 'leak' in this case is not a real problem - if an attacker has system access, they can access the rc file and see the list of all existing vaults regardless of what is shown in the applet. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 420890] Widget was looping. See video
https://bugs.kde.org/show_bug.cgi?id=420890 Ivan Čukić changed: What|Removed |Added Assignee|ivan.cu...@kde.org |notm...@gmail.com Component|general |Desktop Containment Product|frameworks-kactivities |plasmashell Target Milestone|--- |1.0 Version|unspecified |5.14.5 -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 420784] Restore of Vaults fail
https://bugs.kde.org/show_bug.cgi?id=420784 --- Comment #4 from Ivan Čukić --- If I'm not mistaken (some parts are missing in you response, so I'm making an educated guess :) ), you haven't restored activity configuration and your vault is assigned to an activity with an id of "5e847ac8-3735-4647-ad07-ac753d5" which no longer exists. Try to do this - open konsole and: killall kded5 cd ~/.config mv plasmavaultrc plasmavaultrc.backup grep -v 5e847ac8-3735-4647 plasmavaultrc.backup > plasmavaultrc kded5 & -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 420784] Restore of Vaults fail
https://bugs.kde.org/show_bug.cgi?id=420784 Ivan Čukić changed: What|Removed |Added Status|CONFIRMED |NEEDSINFO Resolution|--- |NOT A BUG --- Comment #2 from Ivan Čukić --- > I debugged this with Justin and we think we migrated all the old files into > the This is not all that helpful :) 1. Can you try creating a new vault (with the same backend as the last one) and checking that it works at all? 2. What does the following command return? qdbus --literal org.kde.kded5 /modules/plasmavault availableDevices 3. Open the vaultrc file and check whether the newly created vault is there 4. Is the old vault present in the config? 5. Check that the encrypted directory location (path in the square brackets) and the path specified in mountPoint exist 6a. What is the value of activities field for that vault? 6b. If the field is not empty, what does this command return: kactivities-cli --list-activities 7. Can you mount the old vault manually using encfs/cryfs from command line? I'm marking this as needsinfo - I don't expect it to be a vault issue per se, but let's triage this and make it working anyhow. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 420590] System Settings Crashin
https://bugs.kde.org/show_bug.cgi?id=420590 --- Comment #1 from Ivan --- Created attachment 128058 --> https://bugs.kde.org/attachment.cgi?id=128058&action=edit New crash information added by DrKonqi systemsettings5 (5.18.4) using Qt 5.14.2 After clicking on any other section the application closes. -- Backtrace (Reduced): #6 0x in () #7 0x7f4114a68fa7 in () at /usr/lib/libQt5Quick.so.5 #8 0x7f4114a69019 in () at /usr/lib/libQt5Quick.so.5 #9 0x7f4114c2fa93 in () at /usr/lib/libQt5Quick.so.5 #10 0x7f41105bf47a in () at /usr/lib/libQt5XcbQpa.so.5 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 420590] System Settings Crashin
https://bugs.kde.org/show_bug.cgi?id=420590 Ivan changed: What|Removed |Added CC||ivanvalentimsan...@gmail.co ||m -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 420424] [enhancement] Provide feedback when unable to mount CryFS vault
https://bugs.kde.org/show_bug.cgi?id=420424 Ivan Čukić changed: What|Removed |Added Resolution|--- |UPSTREAM Status|REOPENED|RESOLVED --- Comment #3 from Ivan Čukić --- Thanks for the reply. I understand what you are saying and I agree that the end user does not care where the bug is. But Vault can not detect errors that cryfs does not tell it about. Vault reports all errors it gets from cryfs. Cryfs reports errors via return error codes. If cryfs does not report something as an error, Vault is not going to be able to show it to the user. In this case, cryfs crashes and reports an error through debugging output instead through the error codes as it should. And that *IS* an upstream issue. Grepping the output text is not something that could be used as an error detection mechanism reliably because the debugging output is not stable between backend versions and might depend on the active system language. While Vault can catch (and report to the user) many errors, it can not detect everything. It can only rely on the backend command to tell it what is wrong. Problems like this one would require to be handled on a case by case basis. If this was an issue that still existed in the current cryfs version, I would add some sort of a temporary hack to detect and report this problem to the user until the issue in cryfs was fixed. If you find a similar error with the latest version of cryfs, reopen this issue. P.S. While I really appreciate the discussion, it is not generally useful to reopen bug reports just because you disagree with a decision. The bug report status serves the developers to organize their work. If developers set the status to Fixed/Upstream, that means they consider the report to be a bug in an upstream product. If you change the status, that does not change the decision of the developer. It should go the other way round - you explain why you think an issue should be fixed, and the developer will then change the bug report status. -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 386200] Import Vault
https://bugs.kde.org/show_bug.cgi?id=386200 --- Comment #17 from Ivan Čukić --- Great to hear that! -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 386200] Import Vault
https://bugs.kde.org/show_bug.cgi?id=386200 --- Comment #15 from Ivan Čukić --- You can test how well the current implementation of importing works, and then we could think of a way to expose it to the user without it being overly accessible for the reasons mentioned before. -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 420424] [enhancement] Provide feedback when unable to mount CryFS vault
https://bugs.kde.org/show_bug.cgi?id=420424 Ivan Čukić changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |UPSTREAM --- Comment #1 from Ivan Čukić --- In general, if cryfs crashed, than it is an upstream issue. I'd advise you to update to cryfs 0.10 as this issue has been resolved. If it happens again after the update, please reopen. -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 420380] Folder with files disappear
https://bugs.kde.org/show_bug.cgi?id=420380 Ivan Čukić changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Ivan Čukić --- Should be fixed for the next release Plasma 5.18.5 or 5.19 when they get out. Please reopen if it persists after update. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 420236] Opening the menu from second application menu panel crashes Plasma
https://bugs.kde.org/show_bug.cgi?id=420236 --- Comment #1 from Ivan Ivanov --- I have updated to Kubuntu 20.04 Beta and this problem is no longer present, I do manage to have multiple application menu panels. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 420236] New: Opening the menu from second application menu panel crashes Plasma
https://bugs.kde.org/show_bug.cgi?id=420236 Bug ID: 420236 Summary: Opening the menu from second application menu panel crashes Plasma Product: plasmashell Version: 5.18.3 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: ivan.iva...@suricactus.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.18.3) Qt Version: 5.12.4 Frameworks Version: 5.67.0 Operating System: Linux 5.3.0-46-generic x86_64 Windowing system: X11 Distribution: Ubuntu 19.10 -- Information about the crash: 1) create a new menu by right click on a planel -> add panel -> application menu panel 2) place he panel on another edge 3) the menu shows correctly, but trying to open any of the items cases Plasma to crash I need that so I can have my menus on my multiscren setup. Currently running 19.10 with backports. If you need any additional details, I will try to provide them. The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f41b62161c0 (LWP 2120))] Thread 16 (Thread 0x7f4165d44700 (LWP 19869)): #0 0x7f41b8ff72c6 in futex_wait_cancelable (private=, expected=0, futex_word=0x55e554c28534) at ../sysdeps/unix/sysv/linux/futex-internal.h:80 #1 0x7f41b8ff72c6 in __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55e554c284e0, cond=0x55e554c28508) at pthread_cond_wait.c:508 #2 0x7f41b8ff72c6 in __pthread_cond_wait (cond=0x55e554c28508, mutex=0x55e554c284e0) at pthread_cond_wait.c:638 #3 0x7f41b9b57dbf in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f41b9b57eb1 in QWaitCondition::wait(QMutex*, unsigned long) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f41bb7f37b9 in () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7f41bb7f3a1a in () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7f41b9b51c92 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f41b8ff0669 in start_thread (arg=) at pthread_create.c:479 #9 0x7f41b97d4323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 15 (Thread 0x7f416663a700 (LWP 15228)): #0 0x7f41b8ff72c6 in futex_wait_cancelable (private=, expected=0, futex_word=0x55e554ef7990) at ../sysdeps/unix/sysv/linux/futex-internal.h:80 #1 0x7f41b8ff72c6 in __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55e554ef7940, cond=0x55e554ef7968) at pthread_cond_wait.c:508 #2 0x7f41b8ff72c6 in __pthread_cond_wait (cond=0x55e554ef7968, mutex=0x55e554ef7940) at pthread_cond_wait.c:638 #3 0x7f41b9b57dbf in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f41b9b57eb1 in QWaitCondition::wait(QMutex*, unsigned long) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f41bb7f37b9 in () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7f41bb7f3a1a in () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7f41b9b51c92 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f41b8ff0669 in start_thread (arg=) at pthread_create.c:479 #9 0x7f41b97d4323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 14 (Thread 0x7f4166f00700 (LWP 6245)): #0 0x7f41b8ff72c6 in futex_wait_cancelable (private=, expected=0, futex_word=0x55ee10f0) at ../sysdeps/unix/sysv/linux/futex-internal.h:80 #1 0x7f41b8ff72c6 in __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55ee10a0, cond=0x55ee10c8) at pthread_cond_wait.c:508 #2 0x7f41b8ff72c6 in __pthread_cond_wait (cond=0x55ee10c8, mutex=0x55ee10a0) at pthread_cond_wait.c:638 #3 0x7f41b9b57dbf in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f41b9b57eb1 in QWaitCondition::wait(QMutex*, unsigned long) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f41bb7f37b9 in () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7f41bb7f3a1a in () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7f41b9b51c92 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f41b8ff0669 in start_thread (arg=) at pthread_create.c:479 #9 0x7f41b97d4323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 13 (Thread 0x7f4167701700 (LWP 6238)): #0 0x7f41b8ff72c6 in futex_wait_cancelable (private=, expected=0, futex_word=0x55e5557db660) at ../sysdeps/unix/sysv/linux/futex-internal.h:80 #1 0x7f41b8ff72c6 in __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55e5557db610, cond=0x55e5557db638) at pthread_cond_wait.c:508 #2 0x7f41b8ff72c6 in __pthread_cond_wait (con
[Plasma Vault] [Bug 418262] Plasma Vault crashes kded5 when unable to mount a Vault
https://bugs.kde.org/show_bug.cgi?id=418262 Ivan Čukić changed: What|Removed |Added Latest Commit|https://commits.kde.org/pla |https://commits.kde.org/pla |sma-vault/f6a924b37880b7340 |sma-vault/5920e79ebc695b4ce |e796846a6e5474413ca6533 |2937cbdac435e30389db96a --- Comment #4 from Ivan Čukić --- Git commit 5920e79ebc695b4ce2937cbdac435e30389db96a by Ivan Čukić. Committed on 17/04/2020 at 13:42. Pushed by ivan into branch 'Plasma/5.18'. Make sure we have saved network state before accessing it M +1-1kded/service.cpp https://commits.kde.org/plasma-vault/5920e79ebc695b4ce2937cbdac435e30389db96a -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 419822] Vault crashed after canceling password prompt
https://bugs.kde.org/show_bug.cgi?id=419822 Ivan Čukić changed: What|Removed |Added Resolution|DUPLICATE |FIXED --- Comment #17 from Ivan Čukić --- Done -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 419822] Vault crashed after canceling password prompt
https://bugs.kde.org/show_bug.cgi?id=419822 --- Comment #13 from Ivan Čukić --- I have to say that you're amazing! :) Can you check the commit f6a924b37880b7340e796846a6e5474413ca6533 and one before that one. I think that might be the fix that resolved this crash. -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 419822] Vault crashed after canceling password prompt
https://bugs.kde.org/show_bug.cgi?id=419822 --- Comment #10 from Ivan Čukić --- Hm, the output log seems to hint at another place than the crash log. Fun. Can you compile the master version of plasma-vault and check again? -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 419822] Vault crashed after canceling password prompt
https://bugs.kde.org/show_bug.cgi?id=419822 --- Comment #7 from Ivan Čukić --- Thanks! I think debugging symbols for Qt are not needed at this point. Can you also start kded5 manually from terminal and post the output right before the crash? -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 419822] Vault crashed after canceling password prompt
https://bugs.kde.org/show_bug.cgi?id=419822 --- Comment #5 from Ivan Čukić --- Can you install packages with debugging symbols? (plasma-vault in particular) -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 419822] Vault crashed after canceling password prompt
https://bugs.kde.org/show_bug.cgi?id=419822 --- Comment #3 from Ivan Čukić --- Can you provide the versions of Qt, Plasma, cryfs, encfs? -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 399680] Graphical glitch/corruption in certain menus when transparency effect is enabled
https://bugs.kde.org/show_bug.cgi?id=399680 Ivan D Vasin changed: What|Removed |Added CC||i...@nisavid.io -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 397851] Disabled entries in context menu are unreadable when blur and transparency effects are active
https://bugs.kde.org/show_bug.cgi?id=397851 Ivan D Vasin changed: What|Removed |Added CC||i...@nisavid.io -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 420046] Emoji Picker is not accurate in the selection
https://bugs.kde.org/show_bug.cgi?id=420046 --- Comment #6 from Ivan Nieto --- (In reply to Nate Graham from comment #5) > The 5.18 LTS Plasma release gets bugfixes throughout its lifetime, but not > new features. Also some bugfixes are sufficiently complicated that they > can't be easily or safely applied to 5.18. This may be one of them, > unfortunately. > > The way you would upgrade (even just temporarily) to the git master version > of Plasma depends on your distro. For Kubuntu, you would add the Kubuntu > unstable CI PPA: https://launchpad.net/~kubuntu-ci/+archive/ubuntu/unstable > > Note that there is a bit of risk involved in this, and while it's > reversible, there's a chance that it could break your system while running. > > For more information, you would want to ask in a Kubuntu-specific > venue/forum/etc. > > Hope that helps! It helps a lot. Thanks again. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 420046] Emoji Picker is not accurate in the selection
https://bugs.kde.org/show_bug.cgi?id=420046 --- Comment #4 from Ivan Nieto --- (In reply to Nate Graham from comment #3) > Cannot reproduce with git master version. Looking through the code changes, > it seems as if this has already been fixed in Plasma 5.19. Thanks for taking your time checking. I'm kinda new and I don't know exactly how this works... I just meant to ask, the fix is gonna be out for 5.18 in a given moment? Since it's the LTS release? Or its obligatory to upgrade to 5.19? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 420046] Emoji Picker is not accurate in the selection
https://bugs.kde.org/show_bug.cgi?id=420046 Ivan Nieto changed: What|Removed |Added Attachment #127522|0 |1 is obsolete|| --- Comment #2 from Ivan Nieto --- Created attachment 127523 --> https://bugs.kde.org/attachment.cgi?id=127523&action=edit Pointing at that sad face actually selects angry horn face. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 420046] Emoji Picker is not accurate in the selection
https://bugs.kde.org/show_bug.cgi?id=420046 --- Comment #1 from Ivan Nieto --- Created attachment 127522 --> https://bugs.kde.org/attachment.cgi?id=127522&action=edit Selecting emojis with the mouse/touchpad cursor. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 420046] New: Emoji Picker is not accurate in the selection
https://bugs.kde.org/show_bug.cgi?id=420046 Bug ID: 420046 Summary: Emoji Picker is not accurate in the selection Product: plasmashell Version: 5.18.4 Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Emoji picker Assignee: plasma-b...@kde.org Reporter: inie...@gmail.com Target Milestone: 1.0 Created attachment 127521 --> https://bugs.kde.org/attachment.cgi?id=127521&action=edit Selecting emojis with the keyboard SUMMARY With the screen scalling setted at 125% the Emoji Picker is not accurate when you point at an emoji with the arrow pointer of the mouse or the arrows in the keyboard. STEPS TO REPRODUCE 1. Go to System Preferences > Display and monitor > Display Configuration 2. Set Global Scale at 125% 3. Launch the Emoji Picker OBSERVED RESULT Trying to select an emoji results in confusing highlight, when you point with the cursor to one emoji you actually are highlighting another one. EXPECTED RESULT The emoji pointed with the cursor is the one you are highlighting to select. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Kubuntu 20.04 (available in About System) KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.5 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 419883] The ordering of the activities in the activity switcher is inconsistent with the activity pager
https://bugs.kde.org/show_bug.cgi?id=419883 --- Comment #5 from Ivan Čukić --- It ended up (for some historical reason) in the Plasma component. Global Shortcuts -> Plasma -> Switch to Next Activity -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 419883] The ordering of the activities in the activity switcher is inconsistent with the activity pager
https://bugs.kde.org/show_bug.cgi?id=419883 Ivan Čukić changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #1 from Ivan Čukić --- The activity switcher sorts activities in the most recently used order. Like the window switcher (alt+tab) which it is designed after. If you want to have keyboard shortcuts follow the pager ordering, you can undefine the 'walk through' shortcuts and define 'switch to next/previous activity'. -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 419499] Switch activity shortcut order
https://bugs.kde.org/show_bug.cgi?id=419499
--- Comment #1 from Ivan Čukić ---
Meta+Tab and Meta+Shift+Tab are a part of the default activities shortcuts
("Walk through activities" and "Walk through activities (Reverse)") and they
switch activities in most-recently-used order by default. If you keep the Meta
key pressed, you'll get the activity switcher on the left side of the screen
similar to the default task switcher you get when you switch tasks with
Alt+Tab.
Now, I'm curious what exactly you set up. Which shortcuts exactly did you
change?
--
You are receiving this mail because:
You are watching all bug changes.
[Plasma Vault] [Bug 412779] Test for and try to fix a lack of FUSE availability
https://bugs.kde.org/show_bug.cgi?id=412779 Ivan Čukić changed: What|Removed |Added Status|ASSIGNED|RESOLVED Latest Commit||https://commits.kde.org/pla ||sma-vault/1e2988d7d3ca68f9f ||f00e576c634aff4fe5b8b32 Resolution|--- |FIXED --- Comment #3 from Ivan Čukić --- Git commit 1e2988d7d3ca68f9ff00e576c634aff4fe5b8b32 by Ivan Čukić. Committed on 17/03/2020 at 14:35. Pushed by ivan into branch 'master'. Show command output on unknown failure Summary: If the error is unknown (all errors in encfs), show the 'details...' button which shows the command line output to the user when activated. Reviewers: #plasma, davidedmundson, ngraham, mart Subscribers: plasma-devel Tags: #plasma Differential Revision: https://phabricator.kde.org/D28099 M +2-0.gitignore M +2-1kded/engine/backends/cryfs/cryfsbackend.cpp M +13 -1kded/engine/commandresult.cpp M +9-4kded/engine/commandresult.h M +2-1kded/engine/fusebackend_p.cpp M +35 -4kded/ui/mountdialog.cpp M +5-0kded/ui/mountdialog.h https://commits.kde.org/plasma-vault/1e2988d7d3ca68f9ff00e576c634aff4fe5b8b32 -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 401264] Vault not unmounted when logging out
https://bugs.kde.org/show_bug.cgi?id=401264 Ivan Čukić changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DOWNSTREAM -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 388349] Activity partially unusable
https://bugs.kde.org/show_bug.cgi?id=388349 Ivan Čukić changed: What|Removed |Added Target Milestone|--- |1.0 Product|kactivitymanagerd |plasmashell Assignee|ivan.cu...@kde.org |notm...@gmail.com Component|general |Desktop Containment -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 412964] Activities are not properly supported in Wayland
https://bugs.kde.org/show_bug.cgi?id=412964 Ivan Čukić changed: What|Removed |Added Assignee|ivan.cu...@kde.org |k...@davidedmundson.co.uk Component|Activity Switcher |general --- Comment #1 from Ivan Čukić --- I don't have access to a wayland system. I'm assigning this to the plasma team. The support is missing in kwin/plasma. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kactivities-stats] [Bug 414327] plasmashell segfaults
https://bugs.kde.org/show_bug.cgi?id=414327 --- Comment #2 from Ivan Čukić --- Do you have the console output for this? Seems like an issue with sqlite - might be a corrupted filesystem or something similar. -- You are receiving this mail because: You are watching all bug changes.
