[krusader] [Bug 388266] New: Closing calculate occupied space window does not abort the calculation
https://bugs.kde.org/show_bug.cgi?id=388266 Bug ID: 388266 Summary: Closing calculate occupied space window does not abort the calculation Product: krusader Version: 2.6.0 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: general Assignee: m...@fork.pl Reporter: matthew.li...@gmail.com Target Milestone: --- According to the documentation pressing the "cancel" button on the "Calculate occupied space" window aborts the calculation, which is true, but I expect similar results by closing the window using ESC, or the window buttons. Currently doing so closes the window, but the calculations are continuing in the background. Since this job isn't published in the job manager I found no other way to cancel the calculation but closing the whole application. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 434287] New: Bug in search in files panel
https://bugs.kde.org/show_bug.cgi?id=434287 Bug ID: 434287 Summary: Bug in search in files panel Product: kate Version: unspecified Platform: unspecified OS: Other Status: REPORTED Severity: minor Priority: NOR Component: search Assignee: kwrite-bugs-n...@kde.org Reporter: matthew.li...@gmail.com Target Milestone: --- SUMMARY When double clicking on a search result in the "search in files" results panel, it always activates the first unsaved document instead of the one which have the search results. STEPS TO REPRODUCE 1. Have two (or more) unsaved documents, and select any other tab which is not created firstly. 2. Open the "Edit->Search in files" 3. Select "in Current File" 4. Populate the result list (tree) by filling the search field and clicking on the search button 5. Double click on a search result OBSERVED RESULT The first unsaved document get activated, and the caret jumps to the line where the result was found in the document. (Regardless if there is any mach on the first document) EXPECTED RESULT The document should activated which the search results belongs to, and the caret should jump to the proper line. SOFTWARE/OS VERSIONS I'm using version 21.03.70 (flatpak release: 20.12.2) on Ubuntu KDE Frameworks 5.78.0 Qt 5.15.2 ADDITIONAL INFORMATION I was not able to reproduce it on the Windows (10) store version of Kate (20.08.2) -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 418096] New: Clip markers are drawn out of clips in timeline if clip is cut
https://bugs.kde.org/show_bug.cgi?id=418096 Bug ID: 418096 Summary: Clip markers are drawn out of clips in timeline if clip is cut Product: kdenlive Version: 19.12.2 Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: matthew.li...@gmail.com Target Milestone: --- Clip markers are duplicated for each clip snippet, and drawn out of clips in timeline in case the clip is cut into multiple pieces. STEPS TO REPRODUCE 1. Open a new project 2. Load a video, and place it on the timeline 3. Create a couple of markers on the clip, the markers are drawn properly on the timeline as well. 4. Cut the clip on the time line, and move it away. OBSERVED RESULT The markers are visually duplicated (for each cut), and drawn on the timeline regardless if there is a clip for it or not. EXPECTED RESULT Only the markers which belongs to that part of the clip should be drawn. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Ubuntu 18.04.4 LTS KDE Plasma Version: 5.12.9 KDE Frameworks Version: 5.44.0 Qt Version: 5.9.5 ADDITIONAL INFORMATION It look like this is a regression from version 19.12.1 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 418497] New: Plugins are missing for kate editor in snap package
https://bugs.kde.org/show_bug.cgi?id=418497 Bug ID: 418497 Summary: Plugins are missing for kate editor in snap package Product: neon Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Snaps Assignee: neon-b...@kde.org Reporter: matthew.li...@gmail.com CC: neon-b...@kde.org Target Milestone: --- SUMMARY Kate installed from snap does not install the kate-plugins. I don't know whether is it intended or not, but I really miss some of the plugins. STEPS TO REPRODUCE 1. Install snap package of kate editor 2. Start kate 3. Go to settings->plugins OBSERVED RESULT Plugin list is empty EXPECTED RESULT Plugins should be available 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.
[neon] [Bug 418497] Plugins are missing for kate editor in snap package
https://bugs.kde.org/show_bug.cgi?id=418497 Pozsgay Máté changed: What|Removed |Added CC||matthew.li...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 418497] Plugins are missing for kate editor in snap package
https://bugs.kde.org/show_bug.cgi?id=418497 --- Comment #1 from Pozsgay Máté --- It looks like the candidate channel is affected. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 418497] Plugins are missing for kate editor in snap package
https://bugs.kde.org/show_bug.cgi?id=418497 Pozsgay Máté changed: What|Removed |Added Component|Snaps |general Product|neon|kate Version|unspecified |19.12.2 Assignee|neon-b...@kde.org |kwrite-bugs-n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 418497] Plugins are missing for kate editor in snap package
https://bugs.kde.org/show_bug.cgi?id=418497 Pozsgay Máté changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #2 from Pozsgay Máté --- Fixed in version 19.12.3 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 473725] New: Kate crash if large json is poened and LSP client is enabled
https://bugs.kde.org/show_bug.cgi?id=473725 Bug ID: 473725 Summary: Kate crash if large json is poened and LSP client is enabled Classification: Applications Product: kate Version: Git Platform: Ubuntu OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: matthew.li...@gmail.com Target Milestone: --- Created attachment 161157 --> https://bugs.kde.org/attachment.cgi?id=161157&action=edit Backtrace of crash SUMMARY As title says. Kate cannot handle large json files lately. STEPS TO REPRODUCE 1. Open Kate, enable LSP client 2. Open a large Json OBSERVED RESULT Crash after a couple of seconds EXPECTED RESULT Do not crash SOFTWARE/OS VERSIONS This bug is introduced not a long time ago. I usually compile kate for myself (latest master) and only getting this problem for about a month or so. Kate version: 23.11.70 Linux/KDE Plasma: Ubuntu 22.04 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION GDB Backtrace is attached. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 473725] Kate crash if large json is opened and LSP client is enabled
https://bugs.kde.org/show_bug.cgi?id=473725 Pozsgay Máté changed: What|Removed |Added Summary|Kate crash if large json is |Kate crash if large json is |poened and LSP client is|opened and LSP client is |enabled |enabled -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 473725] Kate crash if large json is opened and LSP client is enabled
https://bugs.kde.org/show_bug.cgi?id=473725 --- Comment #1 from Pozsgay Máté --- Kate version 23.07.70 does not suffer from this problem. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 473725] Kate crash if large json is opened and LSP client is enabled
https://bugs.kde.org/show_bug.cgi?id=473725
--- Comment #3 from Pozsgay Máté ---
I'm using the default one:
"json": {
"command": ["vscode-json-languageserver", "--stdio"],
"url":
"https://github.com/microsoft/vscode/tree/main/extensions/json-language-features/server";,
"highlightingModeRegex": "^JSON$"
},
Installed via snap:
vscode-json-languageserver 1.3.4 136latest/stable
alexmurray✪ -
--
You are receiving this mail because:
You are watching all bug changes.
[kate] [Bug 473725] Kate crash if large json is opened and LSP client is enabled
https://bugs.kde.org/show_bug.cgi?id=473725 --- Comment #4 from Pozsgay Máté --- Also I can confirm if the LSP server is not accessible kate doesn't crash. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 473725] Kate crash if large json is opened and LSP client is enabled
https://bugs.kde.org/show_bug.cgi?id=473725 --- Comment #6 from Pozsgay Máté --- (In reply to Waqar Ahmed from comment #5) > Ok, thanks. Will be fixed soon. Thanks for the quck response, and the support! -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 473837] New: Regression: LSPClient/symbol info no longer works
https://bugs.kde.org/show_bug.cgi?id=473837 Bug ID: 473837 Summary: Regression: LSPClient/symbol info no longer works Classification: Applications Product: kate Version: Git Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: matthew.li...@gmail.com Target Milestone: --- SUMMARY On branch master the Symbol Info of the LSPClient plug-in no longer works on Kate master. STEPS TO REPRODUCE 1. Open a document which have a proper LSP Server configured 2. Select menu entry LSP Client -> Symbol Info OBSERVED RESULT Virtually nothing happens EXPECTED RESULT Should open a hint window describing the details of the symbol found at the caret. SOFTWARE/OS VERSIONS Kate version: 23.11.70 Linux/KDE Plasma: Ubuntu 22.04 KDE Frameworks Version: 5.109.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION This is broken for a while, but for example it was working properly on version 23.07.70. Tested shell/Python/Groovy, all the same, it is probably a problem with the plugin/kate itself. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 473982] New: Regression: LSP/Java crash
https://bugs.kde.org/show_bug.cgi?id=473982 Bug ID: 473982 Summary: Regression: LSP/Java crash Classification: Applications Product: kate Version: Git Platform: Other OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: matthew.li...@gmail.com Target Milestone: --- Created attachment 161298 --> https://bugs.kde.org/attachment.cgi?id=161298&action=edit Trace of the crash SUMMARY Kate (master branch in git) crashes if LSP client is enabled and connected to a Java LSP server STEPS TO REPRODUCE 1. Install and configure a Java LSP server 2. Setup the Java LSP client in Kate 3. Open a Java document OBSERVED RESULT After a couple of seconds (while the LSP server starts up) Kate Crashes EXPECTED RESULT Do not crash SOFTWARE/OS VERSIONS Linux/KDE Plasma: Ubuntu 22.04 KDE Frameworks Version: 5.109.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION Used Java LSP server: https://github.com/georgewfraser/java-language-server.git Kate version 23.07.70 does not suffer from this problem. Printed on terminal: kate: /mnt/kde/src/kde/applications/kate/addons/lspclient/rapidjson/include/rapidjson/document.h:1630: rapidjson::GenericValue::ConstObject rapidjson::GenericValue::GetObject() const [with Encoding = rapidjson::UTF8<>; Allocator = rapidjson::MemoryPoolAllocator; rapidjson::GenericValue::ConstObject = rapidjson::GenericObject > >]: Assertion `IsObject()' failed. /home/pozsgai/bin/kate: line 4: 19040 Aborted (core dumped) ~/projects/kde/build/kde/applications/kate/bin/kate "$@" -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 448308] New: Crash if katefilebrowserplugin is enabled
https://bugs.kde.org/show_bug.cgi?id=448308 Bug ID: 448308 Summary: Crash if katefilebrowserplugin is enabled Product: kate Version: 21.12.1 Platform: Appimage OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: matthew.li...@gmail.com Target Milestone: --- SUMMARY As soon as the FileBrowser plugin enabled Kate crashes in the AppImage distribution: /tmp/.mount_kate-2mnvpnF/AppRun.wrapped: symbol lookup error: /tmp/.mount_kate-2mnvpnF/usr/plugins/ktexteditor/katefilebrowserplugin.so: undefined symbol: _ZN13KBookmarkMenuC1EP16KBookmarkManagerP14KBookmarkOwnerP5QMenu STEPS TO REPRODUCE 1. Download AppImage version, add execution permission, and start. 2. If the plugin is already enabled in your settings Kate crashes as soon as the session is loaded 3. If not enabled, then turn it on at Settings -> Configure Kate -> Plugins -> Filesystem Browser plugin. As soon as you enable it crashes OBSERVED RESULT Crash EXPECTED RESULT Do not crash :) SOFTWARE/OS VERSIONS Linux/KDE Plasma: Ubuntu 30.04.3 LTS OS / AppImage KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.68.0 / 5.89.0 Qt Version: 5.12.8 / 5.15.2 ADDITIONAL INFORMATION Maybe this is just a symptom of a more generic packaging problem, because the SQL extension also crashes: Cannot mix incompatible Qt library (5.12.8) with this library (5.15.2) -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 448390] New: Empty application menu entries after startup
https://bugs.kde.org/show_bug.cgi?id=448390 Bug ID: 448390 Summary: Empty application menu entries after startup Product: kate Version: 21.12.1 Platform: Appimage OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: matthew.li...@gmail.com Target Milestone: --- SUMMARY After Kate starteded up (tested only Appimage version) the (system-wide) application menu entries are disappeared. STEPS TO REPRODUCE 1. Download Appimage version (maybe other versions are affected too) of Kate 2. Add execute permission and start Kate 3. Open application menu OBSERVED RESULT Entries in application menu are disappeared. File associations are temporally lost (if you open a file asks which application you want to open the file with, and that list is empty too) Under Gnome all the icons are replaced with the fallback "no icon" EXPECTED RESULT None of this nonsense should happen. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Ubuntu 20.04.3 LTS (available in About System) KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 ADDITIONAL INFORMATION Issue exists under both Plasma and Gnome. Menu (as well as icons, file associations) can be restored by starting kmenuedit (no entries are shown) and click on save. This is quite frightening to observe. Since this causes major disturbances outside of the application, I marked this bug as critical. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 447511] application doesn't run. Lubuntu 20.04
https://bugs.kde.org/show_bug.cgi?id=447511 Pozsgay Máté changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED CC||matthew.li...@gmail.com --- Comment #1 from Pozsgay Máté --- *** This bug has been marked as a duplicate of bug 448308 *** -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 448308] Crash if katefilebrowserplugin is enabled
https://bugs.kde.org/show_bug.cgi?id=448308 Pozsgay Máté changed: What|Removed |Added CC||pho13...@bk.ru --- Comment #1 from Pozsgay Máté --- *** Bug 447511 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 448308] Crash if katefilebrowserplugin is enabled
https://bugs.kde.org/show_bug.cgi?id=448308 --- Comment #2 from Pozsgay Máté --- You can work around the startup crash by disabling the affected plugins by editing the session file ~/.local/share/kate/anonymous.katesession Set the following lines to false: katefilebrowserplugin=false katesqlplugin=false Repeat these steps for all of your sessions: ~/.local/share/kate/sessions/, and do not enable file browser and SQL plugins. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 448390] Empty application menu entries after startup
https://bugs.kde.org/show_bug.cgi?id=448390 --- Comment #1 from Pozsgay Máté --- Switching Kate sessions also triggers this issue -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 377955] yakuake does no longer accept input
https://bugs.kde.org/show_bug.cgi?id=377955 Pozsgay Máté changed: What|Removed |Added CC||matthew.li...@gmail.com --- Comment #2 from Pozsgay Máté --- I can confirm this, I have updated to Ubuntu 22.04 yesterday, and today I incounterd with this issue. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 377955] yakuake does no longer accept input
https://bugs.kde.org/show_bug.cgi?id=377955 --- Comment #3 from Pozsgay Máté --- (In reply to Alexander Mentyu from comment #1) > @Achim Herwig. Are shortcuts working? Like - 'Ctrl+Shift+T' - new tab, > 'Ctrl+Shift+Right' - change tab to right, 'Ctrl+Shift+Left' - change tab to > left, 'Ctrl+Shift+V' - paste clipboard, 'Ctrl+Shift+S' - save output. No, none of the keyboard related inputs are working. Mouse inputs are still accepted. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 448308] Crash if katefilebrowserplugin is enabled
https://bugs.kde.org/show_bug.cgi?id=448308 --- Comment #3 from Pozsgay Máté --- Updated to Ubuntu 22.04, the problem no longer reproducable. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 427163] Quick Open Session toolbar button does nothing
https://bugs.kde.org/show_bug.cgi?id=427163 Pozsgay Máté changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #4 from Pozsgay Máté --- This is fixed on 22.04.3. I actually tracking down a similar issue regarding the Sessions menu. I learned that KActionMenu have a PopupMode property, which by default set to DelayedPopup (https://doc.qt.io/qt-5/qtoolbutton.html#popupMode-prop), this is why all of the Action menu affected this problem where it is not set explicitly to InstantPopup. Knowing this it is trivial to fix all the session-related menus, by adding the following line to the KateSessionsAction::KateSessionsAction constructor (or whatever it is, I do not really know C++): setPopupMode(QToolButton::InstantPopup); I'm wondering how many other component are affected... -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 427163] Quick Open Session toolbar button does nothing
https://bugs.kde.org/show_bug.cgi?id=427163 Pozsgay Máté changed: What|Removed |Added Ever confirmed|1 |0 Resolution|FIXED |--- Status|RESOLVED|REPORTED --- Comment #5 from Pozsgay Máté --- Actually I was wrong, I mixed up with the Open Recent menu, this one is not fixed, but it is an easy fix, see my previous comment -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 448390] Empty application menu entries after startup
https://bugs.kde.org/show_bug.cgi?id=448390 --- Comment #15 from Pozsgay Máté --- I was able to trigger the issue just by starting up Kate. Changing a Kate session also triggers the issue, so I suppose when Kate starts up it loads a Kate session, therefore I would look somewhere the session loading mechanism. I actually attempted to build Kate from source several times in order to be able to play around with it, however I kind of stuck with some build errors. For example Ubuntu 20.04 ships an older version of Qt5, so I also had to build it as well, which built successfully, but kwindowmanager unable to build due missing Qt5X11Extras cmake files, which infact missing, it also looks like the Qt5X11Extras build produces no shared object files. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 448390] Empty application menu entries after startup
https://bugs.kde.org/show_bug.cgi?id=448390 --- Comment #16 from Pozsgay Máté --- Duplicating, deleting, saving (save/save as) sessions also triggers the issue. It looks like every operation which somehow affect the sessions (always) triggers the issue. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 448390] Empty application menu entries after startup
https://bugs.kde.org/show_bug.cgi?id=448390 --- Comment #17 from Pozsgay Máté --- One more addition: If session chooser is enabled upon startup the issue is already triggered by the time when the chooser dialog is shown. If I reset the menus by the workaround mentioned, then I select a session it loads up properly without re-triggering the issue. It might not the session loading which cause problem, rather the changes of/in sessions. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 448390] Empty application menu entries after startup
https://bugs.kde.org/show_bug.cgi?id=448390 Pozsgay Máté changed: What|Removed |Added Version|5.18.7 |5.18.8 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 448390] Empty application menu entries after startup
https://bugs.kde.org/show_bug.cgi?id=448390 --- Comment #20 from Pozsgay Máté --- I'm making some progress here. I checked the source code of the kmenuedit to figure out what fixes my menus, and I found the following line particularly interesting: KBuildSycocaProgressDialog::rebuildKSycoca(this); As I figured out KSyCoCa is a configuration cache for KDE, and indeed executing the kbuildsycoca5 command fixes the menus. I suspect there is some caching problem, maybe the AppImage semi-sandboxing mechanism prevents the KDE to detect some changes and rebuild/update the cache properly. My knowledge in KDE internals are very limited, but it looks like this is the good direction. It would be good to test out on a non-sandboxed version as well. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 448390] Empty application menu entries after startup
https://bugs.kde.org/show_bug.cgi?id=448390 Pozsgay Máté changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #21 from Pozsgay Máté --- I can no longer reproduce this problem from version kate-21.12.3-???-linux-centos_64-gcc.AppImage. Tested build id 449, but might fixed in earlier versions as well. Tested kate-22.04.0-485-linux-64-gcc.AppImage as well, bug neither reproducable here. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 450434] Kate crashes when right clicking on a toolbar button before a file was loaded
https://bugs.kde.org/show_bug.cgi?id=450434 Pozsgay Máté changed: What|Removed |Added CC||matthew.li...@gmail.com --- Comment #5 from Pozsgay Máté --- I can confirm this issue. I can trigger almost every time when I start a new kate session (or change it to another one) and rightclick on an empty space of the toolbar. Kate: 22.04.0, Appimage version on Ubuntu 20.04.04 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 450434] Kate crashes when right clicking on a toolbar button before a file was loaded
https://bugs.kde.org/show_bug.cgi?id=450434 --- Comment #6 from Pozsgay Máté --- You don't have to click on an empty space, it crashes on any part of the toolbar. Running kate on one CPU fixes/hides (/making it very unlikely to happen) the issue: taskset -a -c 1 ./kate-22.04.0-485-linux-64-gcc.AppImage It is not always repruducable, just do a few Session->New Session; Rigth click on toolbar cycle to trigger the issue with different delay between these actions. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 427163] Quick Open Session toolbar button does nothing
https://bugs.kde.org/show_bug.cgi?id=427163 Pozsgay Máté changed: What|Removed |Added CC||matthew.li...@gmail.com --- Comment #3 from Pozsgay Máté --- I can also confirm this, however, if you hold your click on the button the menu will eventually show up after a cuouple of seconds. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 427163] Quick Open Session toolbar button does nothing
https://bugs.kde.org/show_bug.cgi?id=427163 Pozsgay Máté changed: What|Removed |Added Version|20.08.1 |22.04.0 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 450434] Kate crashes when right clicking on a toolbar button before a file was loaded
https://bugs.kde.org/show_bug.cgi?id=450434 --- Comment #7 from Pozsgay Máté --- (In reply to Pozsgay Máté from comment #6) > Running kate on one CPU fixes/hides (/making it very unlikely to happen) the > issue: taskset -a -c 1 ./kate-22.04.0-485-linux-64-gcc.AppImage It is just less likely to crash, beeing very quick with the right click after the new session still results a pretty consitent crash. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 454699] New: Crash if spellcheck is enabled
https://bugs.kde.org/show_bug.cgi?id=454699 Bug ID: 454699 Summary: Crash if spellcheck is enabled Product: kate Version: 22.04.1 Platform: Appimage OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: matthew.li...@gmail.com Target Milestone: --- SUMMARY On latest release 22.04.1 Kate crashes if spellcheking is enabled. STEPS TO REPRODUCE 1. If spellcheck is enabled by default Kate crashes upon startup, otherwise start kate 2. Enable spell check: Tools -> Spelling -> Automatic Spell checking 3. Start typing some text, and it crashes almost immediately. OBSERVED RESULT Crash with the following message in terminal: /tmp/.mount_kate-2bmiHrf/AppRun.wrapped: symbol lookup error: /tmp/.mount_kate-2bmiHrf/usr/plugins/kf5/sonnet/sonnet_hunspell.so: undefined symbol: _ZN8Hunspell5spellERKSsPiPSs EXPECTED RESULT Should not crash SOFTWARE/OS VERSIONS Linux/KDE Plasma: Ubuntu 20.04.4 LTS and 22.04 LTS KDE Plasma Version: KDE Frameworks Version: 5.94.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION I have lunched kate with the following command: 'LANG=en LANGUAGE=en ./kate-22.04.1-519-linux-64-gcc.AppImage' It looks like it doesn't really matters what is your system language, it crashes regardless. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 455022] New: Last Used Views not working if invoked via menu
https://bugs.kde.org/show_bug.cgi?id=455022 Bug ID: 455022 Summary: Last Used Views not working if invoked via menu Product: kate Version: 22.04.1 Platform: Appimage OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: matthew.li...@gmail.com Target Milestone: --- SUMMARY Last Used Views not working if invoked via menu STEPS TO REPRODUCE 1. Open multiple document in Kate 2. Use the "Last Used Views" function via "View -> Last Used Views" menu 3. Select a document by clicking on it with mouse or keyboard OBSERVED RESULT The line is selected from the list using keyboard, or the cell is selected if mouse was used. Document not switched even if pressing enter/double mouse click The popup window can be dismissed by cancelling the request using ESC key. EXPECTED RESULT The active document should be changed either by pressing enter, or single/double mouse click SOFTWARE/OS VERSIONS Linux/KDE Plasma: Ubuntu 20.04.4 LTS KDE Plasma Version: KDE Frameworks Version: 5.94.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION The workaround is to use this functionality via keyboard shortcut. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 455023] New: Problem with "Last Used Views" mouse selection
https://bugs.kde.org/show_bug.cgi?id=455023 Bug ID: 455023 Summary: Problem with "Last Used Views" mouse selection Product: kate Version: 22.04.1 Platform: Appimage OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: matthew.li...@gmail.com Target Milestone: --- SUMMARY There is a strange/unexpected behavior of the "Last Used Views" function. Making a document selection by mouse doesn't trigger the active document switch upon the box is closed by releasing the CTRL key unless the whole line is selected. This is probably an easy fix. I'm not familiar with QT, but probably there is a flag for that table component to select the whole line using mouse selection. STEPS TO REPRODUCE 1. Open multiple document in Kate 2. Invoke "Last Used Views" function using keyboard shortcut 3. Select the document by clicking it with mouse OBSERVED RESULT Cell selected, document not switched EXPECTED RESULT Should change the active document at click, or at least upon the CTRL is released. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Ubuntu 22.04.4 LTS KDE Frameworks Version: 5.94.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Workaround: Making a whole line selection using the mouse (or cursor keys afterwards) triggers the document switch. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 489931] New: Kate crashes using search function is navigation bar
https://bugs.kde.org/show_bug.cgi?id=489931 Bug ID: 489931 Summary: Kate crashes using search function is navigation bar Classification: Applications Product: kate Version: Git Platform: Other OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: matthew.li...@gmail.com Target Milestone: --- Created attachment 171480 --> https://bugs.kde.org/attachment.cgi?id=171480&action=edit Trace of the crash SUMMARY As the title says. STEPS TO REPRODUCE 1. Open Kate. 2. Open a document. 3. Click on (or invoke with a shortcut) the navigation bar (Breadcrumbs) 4. Start typing in order to search OBSERVED RESULT After a few character (most of the times even at the first one) Kate crashes. EXPECTED RESULT Do not crash, show the filtered results instead of. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Ubuntu 22.04 latest + updated Kate version: 24.07.70 (latest master from Git) KDE Framework: 6.4.0 Qt Version: 6.6.3 ADDITIONAL INFORMATION Compiled by myself including Qt. Based on the stack trace looks like an infinite recursion: -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 436804] New: Proxy clips are not properly generated from stabilized vidoes
https://bugs.kde.org/show_bug.cgi?id=436804 Bug ID: 436804 Summary: Proxy clips are not properly generated from stabilized vidoes Product: kdenlive Version: 21.04.0 Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: matthew.li...@gmail.com Target Milestone: --- SUMMARY Multiple issues of proxy clips generated from stabilized clips. STEPS TO REPRODUCE 1. Import a clip 2. Stabilize the clip 3. Add the stabilized mlt to the clip bin (or let the kdenlive do it for you) 4. Generate a proxy clip from the stabilized clip OBSERVED RESULT The proxy clip is generated, however the quality is much worst than expected, blank strips are added to te top and bottom, and the length of the proxy clip is also incorrect (about the double of the original). EXPECTED RESULT The proxy clip shouldn't have the two black strips, this might improve the quality as well, the length of the proxy clip should be the same as the original. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Ubuntu 20.04.2 KDE Plasma Version: KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 436805] New: Add clip to project option is ignored in video stabilize window
https://bugs.kde.org/show_bug.cgi?id=436805 Bug ID: 436805 Summary: Add clip to project option is ignored in video stabilize window Product: kdenlive Version: 21.04.0 Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: matthew.li...@gmail.com Target Milestone: --- SUMMARY "Add clip to project" option is ignored in video stabilizer dialog. STEPS TO REPRODUCE 1. Import a clip 2. Open the stabilize video window 3. Uncheck the "Add clip to project" checkbox OBSERVED RESULT After the stabilization is completed the stabilized mlt is added to project bin EXPECTED RESULT The mlt shouldn't added to project if the corresponding checkbox is not checked. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Ubuntu 20.04.2 (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 436804] Proxy clips are not properly generated from stabilized vidoes
https://bugs.kde.org/show_bug.cgi?id=436804 --- Comment #1 from Pozsgay Máté --- Might be related to: https://invent.kde.org/multimedia/kdenlive/-/issues/1053 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 436804] Proxy clips are not properly generated from stabilized vidoes
https://bugs.kde.org/show_bug.cgi?id=436804 --- Comment #3 from Pozsgay Máté --- The issue is partially solved in nightly (21.07.70). The length of the proxy video is the same as the source, however the black strips are still added. This is probably two separate issue, but one of them looks like to got solved. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 436804] Proxy clips are not properly generated from stabilized vidoes
https://bugs.kde.org/show_bug.cgi?id=436804 --- Comment #5 from Pozsgay Máté --- Created attachment 138567 --> https://bugs.kde.org/attachment.cgi?id=138567&action=edit Proxy with black strips -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 436804] Proxy clips are not properly generated from stabilized vidoes
https://bugs.kde.org/show_bug.cgi?id=436804 --- Comment #6 from Pozsgay Máté --- Created attachment 138568 --> https://bugs.kde.org/attachment.cgi?id=138568&action=edit No proxy without black strips -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 436804] Proxy clips are not properly generated from stabilized vidoes
https://bugs.kde.org/show_bug.cgi?id=436804 Pozsgay Máté changed: What|Removed |Added Attachment #138567|0 |1 is obsolete|| --- Comment #7 from Pozsgay Máté --- Created attachment 138569 --> https://bugs.kde.org/attachment.cgi?id=138569&action=edit Proxy with black strips (the real one) Please ignore previous upload, accidentally uploaded the same image twice -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 436804] Proxy clips are not properly generated from stabilized vidoes
https://bugs.kde.org/show_bug.cgi?id=436804 --- Comment #8 from Pozsgay Máté --- The black strips are present on all videos I tried, but only if I generate proxy videos from stabilized MLT clips (on normal clips, proxy videos are fine). Even the thumbnail picture in the project bin shows the black strips. (See attachments) I tested on this one as well: https://samplelib.com/lib/download/mp4/sample-30s.mp4 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 436804] Proxy clips are not properly generated from stabilized vidoes
https://bugs.kde.org/show_bug.cgi?id=436804
--- Comment #10 from Pozsgay Máté ---
Good news!
I was able to narrow down the source of the problem. I found a thread in the
mltframework gitlab. (https://github.com/mltframework/shotcut/issues/416) They
had similar problems, so I started kdenlive with an unset LANG variable (was
set to hu_HU.UTF-8) and now the proxy clips are generated without the black
bars on stabilized videos as well!
There is probably some problem with the decimal point format ("." vs ",").
--
You are receiving this mail because:
You are watching all bug changes.
[kdenlive] [Bug 436804] Proxy clips are not properly generated from stabilized vidoes
https://bugs.kde.org/show_bug.cgi?id=436804 --- Comment #15 from Pozsgay Máté --- Just one more addition. I am able to reproduce the crash on Linux as well: 1. Open kdenlive with unset LANG 2. Generate the mlt file using vidstab 3. Close kdenlive and restart LANG set to "hu_HU.UTF-8" 4. Add the generated mlt file to the clip bin 5. Enable proxy clips 6. The proxy generation starts, and kdenlive almost instantly crashes. The same happens if I load the "hungarian" version of mlt to the "english" version of kdenlive, so it looks like the generated files are also locale-dependent. I can spot two difference between the files: - In the mlt file the value of LC_NUMERIC is "C" vs. "hu_HU.UTF-8" - In the trf file decimal point indeed different "." vs. "," Thank you! -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kded] [Bug 460228] New: Kded5 freeze at startup if proxy enabled
https://bugs.kde.org/show_bug.cgi?id=460228 Bug ID: 460228 Summary: Kded5 freeze at startup if proxy enabled Classification: Frameworks and Libraries Product: frameworks-kded Version: 5.92.0 Platform: Ubuntu OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: fa...@kde.org Reporter: matthew.li...@gmail.com CC: kdelibs-b...@kde.org Target Milestone: --- SUMMARY Suddenly I had many wierd problems (missing systray icons, freezes in systemsettings on specific modules, etc) with my KDE session. STEPS TO REPRODUCE 1. Enable night colors 2. Set up proxy (I'm using PAC) 3. (Re)Start kded5 OBSERVED RESULT kded5 freezes at the stage of starting the location services. As a consequence many features are broken (missing systray icons, systemsettings also freezes/times out due inability to get response via dbus) EXPECTED RESULT Should finish the startup sequence, and serve the requests. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Ubuntu 22.04 KDE Plasma Version: 5.24.6 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION I traced the problem to kded5. Kded5 freezes if proxy (PAC) is enabled at startup. It looks like it attempts to start the location service, where it freezes: $ kded5 --replace kcm_touchpad: Using X11 backend Installing the delayed initialization callback. org.kde.plasma.dataengine.geolocation: gpsd not found "location" It turned out enabling the night colors triggers the location services, which looks like unable to operate properly with proxy enabled. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 461056] New: Crash in external tools if JS is used
https://bugs.kde.org/show_bug.cgi?id=461056
Bug ID: 461056
Summary: Crash in external tools if JS is used
Classification: Applications
Product: kate
Version: Git
Platform: Ubuntu
OS: Linux
Status: REPORTED
Severity: crash
Priority: NOR
Component: application
Assignee: kwrite-bugs-n...@kde.org
Reporter: matthew.li...@gmail.com
Target Milestone: ---
SUMMARY
I try to add an external tool call using the external tools plugin which
requests an additional input parameter. My approach is to call a JavaScript
window.prompt() function with the %{JS:} token, and I realized calling a JS
function crashes Kate
STEPS TO REPRODUCE
1. Enable External tools
2. Create a new tool, for example:
Executable: bash
Arguments: -c echo "Input: '%{JS:editor.clipboardText()}"'
3. Run the new tool you created in step 2
OBSERVED RESULT
Crash
EXPECTED RESULT
Execute the tool as requested
SOFTWARE/OS VERSIONS
Kate version: 22.11.70
Linux/KDE Plasma: Ubuntu 22.04.1 LTS
KDE Plasma Version:
KDE Frameworks Version: 5.100.0
Qt Version: 5.15.3
ADDITIONAL INFORMATION
Backtrace:
Core was generated by
`/home/pozsgai/projects/kde/build/kde/applications/kate/bin/kate'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x7fd9f541d687 in KateExternalToolsPlugin::runnerForTool
(this=0x560c47290340, tool=..., view=0x0, executingSaveTrigger=false)
at
/home/matthew/projects/kde/src/kde/applications/kate/addons/externaltools/externaltoolsplugin.cpp:250
--Type for more, q to quit, c to continue without paging--
250 auto mw = view->mainWindow();
[Current thread is 1 (Thread 0x7fda1b8e29c0 (LWP 17908))]
(gdb) bt
#0 0x7fd9f541d687 in KateExternalToolsPlugin::runnerForTool
(this=0x560c47290340, tool=..., view=0x0, executingSaveTrigger=false)
at
/home/matthew/projects/kde/src/kde/applications/kate/addons/externaltools/externaltoolsplugin.cpp:250
#1 0x7fd9f541dc8c in KateExternalToolsPlugin::runTool
(this=0x560c47290340, tool=..., view=0x0, executingSaveTrigger=false)
at
/home/matthew/projects/kde/src/kde/applications/kate/addons/externaltools/externaltoolsplugin.cpp:297
#2 0x7fd9f54286ef in operator() (__closure=0x560c479334d0) at
/home/matthew/projects/kde/src/kde/applications/kate/addons/externaltools/kateexternaltoolsview.cpp:77
#3 0x7fd9f542aa62 in QtPrivate::FunctorCall,
QtPrivate::List<>, void, KateExternalToolsMenuAction::reload()::
>::call(struct {...} &, void **) (f=...,
arg=0x7ffe29a42a90) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:146
#4 0x7fd9f542a9cb in
QtPrivate::Functor,
0>::call, void>(struct {...} &, void *, void **) (f=...,
arg=0x7ffe29a42a90)
at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:256
#5 0x7fd9f542a970 in
QtPrivate::QFunctorSlotObject,
0, QtPrivate::List<>, void>::impl(int, QtPrivate::QSlotObjectBase *, QObject *,
void **, bool *) (
which=1, this_=0x560c479334c0, r=0x560c47933030, a=0x7ffe29a42a90, ret=0x0)
at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:443
#6 0x7fda21320793 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#7 0x7fda21f82be6 in QAction::triggered(bool) () from
/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#8 0x7fda21f858fc in QAction::activate(QAction::ActionEvent) () from
/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#9 0x7fda22110142 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#10 0x7fda22117d39 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#11 0x7fda21fcc4ee in QWidget::event(QEvent*) () from
/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#12 0x7fda21f89713 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#13 0x7fda21f91364 in QApplication::notify(QObject*, QEvent*) () from
/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#14 0x7fda212e8e3a in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib/x86_64-linux-gnu/libQt5Core.so.5
#15 0x7fda21f8fe47 in QApplicationPrivate::sendMouseEvent(QWidget*,
QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool, bool) ()
from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#16 0x7fda21fe6843 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#17 0x7fda21fe8fd5 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#18 0x7fda21f89713 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#19 0x7fda212e8e3a in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib/x86_64-linux-gnu/libQt5Core.so.5
#20 0x7fda21880307 in
QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*)
() from /lib/x86_64-linux-gnu/libQt5Gui.so.5
#21 0x7fda21855a2c in
QWindowSystemInterface::sendWindowSystemEvents(QFlags)
() from /lib/x86_64-linux-gnu/libQt5Gui.so.5
#22 0x7fda1af75d6e in ?? () from
[kate] [Bug 461818] New: Excessive use of inotify instances in kate
https://bugs.kde.org/show_bug.cgi?id=461818 Bug ID: 461818 Summary: Excessive use of inotify instances in kate Classification: Applications Product: kate Version: Git Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: matthew.li...@gmail.com Target Milestone: --- SUMMARY Kate spawns many inotify instances. STEPS TO REPRODUCE 1. Start Kate 2. Open some project OBSERVED RESULT Kate spawns 10-15 inotify instances EXPECTED RESULT Kate should limit the inotify instances as the default number of allowed inotify instances per user is 127. Using multiple kate instances can easily use up all the available instances causing numerous problems in other applications. SOFTWARE/OS VERSIONS Kate: 22.11.70 Linux/KDE Plasma: Ubuntu 22.04.1 LTS (available in About System) KDE Plasma Version: 5.24.6 KDE Frameworks Version: 5.100.0 Qt Version: 5.13.3 ADDITIONAL INFORMATION I used the following script to investigate the issue: https://github.com/fatso83/dotfiles/blob/master/utils/scripts/inotify-consumers Below there is an example of the output. As you can see PyCharm uses 3217 watches, but only a singe instance. This is not a problem, since the max_user_watches limit is quite large (65535). On the other hand Kate uses 10+ watch instance for the 30+ files. This is a problem, because the max_user_instances limit is only 128 by default. Running 3 kate instance uses up 30% of the available watch instances. INOTIFY INSTANCES WATCHES PER COUNT PROCESS PID USER COMMAND 3217 1 19116 pozsgai /snap/pycharm-professional/306/bin/fsnotifier 92 43188 pozsgai /lib/systemd/systemd --user 78 13707 pozsgai /usr/libexec/xdg-desktop-portal-gtk 77 13646 pozsgai /usr/libexec/xdg-desktop-portal-gnome 54 43731 pozsgai /usr/bin/kded5 3712 80717 pozsgai /home/pozsgai/projects/kde/build/kde/applications/kate/bin/kate 36 13227 pozsgai /usr/libexec/tracker-miner-fs-3 3013 19236 pozsgai /home/pozsgai/projects/kde/build/kde/applications/kate/bin/kate 2914 28352 pozsgai /home/pozsgai/projects/kde/build/kde/applications/kate/bin/kate 28 85511 pozsgai /opt/google/chrome/chrome --enable-crashpad -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 450434] Kate crashes when right clicking on a toolbar button before a file was loaded
https://bugs.kde.org/show_bug.cgi?id=450434 --- Comment #9 from Pozsgay Máté --- (In reply to Christoph Cullmann from comment #8) > Can really not reproduce, please test again with e.g. version 22.12.x Neither can I, it looks like it is fixed. I'm currently on version 23.03.70 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 397810] Crash with Composite and Transform
https://bugs.kde.org/show_bug.cgi?id=397810 Pozsgay Máté changed: What|Removed |Added CC||matthew.li...@gmail.com --- Comment #3 from Pozsgay Máté --- I think I have encountered this issue as well. It is pretty easy to reproduce. Just grab a clip, and a picture (I want to use it as a logo). Place the video in the timeline, and the image above. Apply the transform effect on the image. (You can leave the default settings) Start the project playback while both the videos are enabled, and it crashes. Proxy clips mitigate the issue, but just a slightly better. Switching to "Preview" track compositing greatly reduce the likelihood of the crash. I also noticed if I start the playback only the video enabled, then enable the logo track as well the playback goes on and the logo displayed as well. However seeking to another position while the playing back, or stop the playback, and restarting it is likely to cause crash again. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 397810] Crash with Composite and Transform
https://bugs.kde.org/show_bug.cgi?id=397810 --- Comment #4 from Pozsgay Máté --- Created attachment 116820 --> https://bugs.kde.org/attachment.cgi?id=116820&action=edit kdenlive console output -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 397810] Crash with Composite and Transform
https://bugs.kde.org/show_bug.cgi?id=397810 --- Comment #5 from Pozsgay Máté --- Created attachment 116821 --> https://bugs.kde.org/attachment.cgi?id=116821&action=edit gdb backtrace -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 397810] Crash with Composite and Transform
https://bugs.kde.org/show_bug.cgi?id=397810 --- Comment #6 from Pozsgay Máté --- A quick update. It just came into my mind I have enabled an experimental feature: multiple processing thread. From the symptoms it looks like to me it is some kind of race condition issue, so I set back the processing threads to the default 1, and since then no matter how desperately I'm bashing the timeline, start/stop playback, enable/disable tracks; it just works fine. So it seems it is really some kind of threading issue. BTW, I'm using version 18.08.2 from ppa:kdenlive/kdenlive-stable on Ubuntu Bionic with a kernel 4.18.20-041820-generic. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 388266] New: Closing calculate occupied space window does not abort the calculation
https://bugs.kde.org/show_bug.cgi?id=388266 Bug ID: 388266 Summary: Closing calculate occupied space window does not abort the calculation Product: krusader Version: 2.6.0 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: general Assignee: m...@fork.pl Reporter: matthew.li...@gmail.com Target Milestone: --- According to the documentation pressing the "cancel" button on the "Calculate occupied space" window aborts the calculation, which is true, but I expect similar results by closing the window using ESC, or the window buttons. Currently doing so closes the window, but the calculations are continuing in the background. Since this job isn't published in the job manager I found no other way to cancel the calculation but closing the whole application. -- You are receiving this mail because: You are watching all bug changes.
