[kdevelop] [Bug 486746] Untitled documents disappear from the working set when the user starts or stops debugging
https://bugs.kde.org/show_bug.cgi?id=486746 Christoph Roick changed: What|Removed |Added Version Fixed In||5.15.240800 Resolution|--- |FIXED Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/kdev ||elop/kdevelop/-/commit/9cc5 ||682da37101b62eabd56437fd901 ||c554b202c --- Comment #5 from Christoph Roick --- Git commit 9cc5682da37101b62eabd56437fd901c554b202c by Christoph Roick. Committed on 30/05/2024 at 21:47. Pushed by croick into branch 'master'. Keep unsaved documents open when switching areas The document controller can find unsaved files by specifying the "untitled" document name as long as the controller exists. Show the document if it is found. FIXED-IN: 5.15.240800 M +8-0kdevplatform/shell/tests/test_workingsets.cpp M +8-2kdevplatform/shell/workingsets/workingset.cpp https://invent.kde.org/kdevelop/kdevelop/-/commit/9cc5682da37101b62eabd56437fd901c554b202c -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 486746] Untitled documents disappear from the working set when the user starts or stops debugging
https://bugs.kde.org/show_bug.cgi?id=486746 --- Comment #4 from Christoph Roick --- (In reply to Igor Kushnir from comment #2) > (In reply to Igor Kushnir from comment #1) > > This bug is sort of reverse of Bug 409858 fixed in the mentioned merge > > request. > A simple fix that does not reopen Bug 409858 might work: skip opening > nonexistent files only on KDevelop start, not when that function is called > during a switch to a different area. Hopefully those nonexistent documents > would be (re)opened correctly then. I did something similar: Check if the document controller might actually find something with the temporary untitled name. If it does, take that document, if not, skip it. At startup it will not find the document. When switching between areas, it actually does. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 486746] Untitled documents disappear from the working set when the user starts or stops debugging
https://bugs.kde.org/show_bug.cgi?id=486746 Christoph Roick changed: What|Removed |Added Status|REPORTED|CONFIRMED CC||chris...@gmx.de Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 403769] Only the default environment profle is being used
https://bugs.kde.org/show_bug.cgi?id=403769 Christoph Roick changed: What|Removed |Added Latest Commit||https://invent.kde.org/kdev ||elop/kdevelop/commit/679558 ||2dce86d3766e596e240bfe2e5ad ||a52d6c0 Resolution|--- |FIXED Version Fixed In||5.11.230400 Status|ASSIGNED|RESOLVED --- Comment #3 from Christoph Roick --- Git commit 6795582dce86d3766e596e240bfe2e5ada52d6c0 by Christoph Roick. Committed on 05/01/2023 at 13:21. Pushed by croick into branch 'master'. Apply Ninja environment settings The Ninja configuration page offers to select a build environment. This setting is now applied when creating a corresponding NinjaJob. FIXED-IN: 5.11.230400 M +2-0plugins/ninjabuilder/ninjabuilder.cpp https://invent.kde.org/kdevelop/kdevelop/commit/6795582dce86d3766e596e240bfe2e5ada52d6c0 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 422203] PDF viewer hijacks spacebar, even when not in focus
https://bugs.kde.org/show_bug.cgi?id=422203 Christoph Roick changed: What|Removed |Added Status|REOPENED|RESOLVED Version Fixed In||5.7.0 Latest Commit||https://invent.kde.org/kdev ||elop/kdevelop/commit/4fadf2 ||c99c8a8826f0ca82e25e0718d83 ||23c7ad8 Resolution|--- |FIXED --- Comment #4 from Christoph Roick --- Git commit 4fadf2c99c8a8826f0ca82e25e0718d8323c7ad8 by Christoph Roick. Committed on 07/10/2021 at 19:43. Pushed by croick into branch 'master'. Restrict KParts keyboard shortcuts to their own view Fix keyboard shortcuts being applied across multiple split views. Without limiting the shortcuts owned by the respective KPart (such as an Okular view), actions are called even if the Part is not currently active (like scrolling the Okular document when pressing space in another view). FIXED-IN: 5.7.0 M +14 -6kdevplatform/shell/partcontroller.cpp https://invent.kde.org/kdevelop/kdevelop/commit/4fadf2c99c8a8826f0ca82e25e0718d8323c7ad8 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 407869] Okular KParts plugin steals space key events from shell
https://bugs.kde.org/show_bug.cgi?id=407869 Christoph Roick changed: What|Removed |Added CC||chris...@gmx.de --- Comment #9 from Christoph Roick --- I marked this bug in the above Kate MR, although it's flagged as Okular bug. In my opinion the issue is either related to Kate or to KXMLGUI. The latter (or QMainWindow) seems to be responsible for handling shortcuts in the main menu bar. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 422203] PDF viewer hijacks spacebar, even when not in focus
https://bugs.kde.org/show_bug.cgi?id=422203 Christoph Roick changed: What|Removed |Added Status|RESOLVED|REOPENED CC||chris...@gmx.de Resolution|DUPLICATE |--- --- Comment #3 from Christoph Roick --- This bug is not actually a duplicate of bug 407869, since here there is some interaction between "regular" KParts views which can be fixed within KDevelop. The other bug is caused by something else. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 352902] Kate Editor Shortcuts unambiguous on Split View
https://bugs.kde.org/show_bug.cgi?id=352902 Christoph Roick changed: What|Removed |Added Latest Commit||https://invent.kde.org/fram ||eworks/ktexteditor/commit/e ||def8135d2544fb9ab6f63e16693 ||b589d0d5d246 Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #3 from Christoph Roick --- Git commit edef8135d2544fb9ab6f63e16693b589d0d5d246 by Christoph Roick. Committed on 25/05/2021 at 21:54. Pushed by cullmann into branch 'master'. Limit shortcut context to active view for Reuse Word Above/Below The current default calls the corresponding action for every split view which leads to an error message. Qt::WidgetWithChildrenShortcut limits the call to the current view, as in kateview.cpp. M +3-0src/completion/katewordcompletion.cpp https://invent.kde.org/frameworks/ktexteditor/commit/edef8135d2544fb9ab6f63e16693b589d0d5d246 -- You are receiving this mail because: You are watching all bug changes.
[kdevplatform] [Bug 409858] Working file sets on load create text document objects for no longer existing or not yet opened files (e.g. shown in Documents toolview)
https://bugs.kde.org/show_bug.cgi?id=409858 Christoph Roick changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/kdev ||elop/kdevelop/commit/d2b8dc ||325abc99b4931598258bf052d06 ||a2440d2 Status|REPORTED|RESOLVED --- Comment #1 from Christoph Roick --- Git commit d2b8dc325abc99b4931598258bf052d06a2440d2 by Christoph Roick. Committed on 23/05/2021 at 11:28. Pushed by croick into branch 'master'. Do not try to reopen non-existing local files M +17 -7kdevplatform/shell/tests/test_workingsets.cpp M +7-0kdevplatform/shell/tests/test_workingsets.h M +13 -4kdevplatform/shell/workingsets/workingset.cpp https://invent.kde.org/kdevelop/kdevelop/commit/d2b8dc325abc99b4931598258bf052d06a2440d2 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 337891] Synchronise editor windows between Code and Debug modes
https://bugs.kde.org/show_bug.cgi?id=337891 Christoph Roick changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/kdev ||elop/kdevelop/commit/745481 ||58dc6d43a7b202a7a34e1e48d9a ||3f21a8e --- Comment #9 from Christoph Roick --- Git commit 74548158dc6d43a7b202a7a34e1e48d9a3f21a8e by Christoph Roick. Committed on 23/05/2021 at 11:28. Pushed by croick into branch 'master'. Maintain working set state when switching between areas Save the working set state before switching areas (i.e. from code to debug). This allows restoring the order of the view tabs and the current cursor positions in the new area. M +4-1kdevplatform/shell/areadisplay.cpp M +2-2kdevplatform/shell/debugcontroller.cpp M +4-2kdevplatform/shell/tests/test_workingsets.cpp M +1-0kdevplatform/shell/uicontroller.cpp M +18 -15 kdevplatform/shell/workingsetcontroller.cpp M +5-2kdevplatform/shell/workingsetcontroller.h M +1-1kdevplatform/shell/workingsets/closedworkingsetswidget.cpp M +1-1kdevplatform/shell/workingsets/closedworkingsetswidget.h M +2-2kdevplatform/shell/workingsets/workingsetwidget.cpp M +1-1kdevplatform/shell/workingsets/workingsetwidget.h M +5-4kdevplatform/sublime/area.cpp M +3-3kdevplatform/sublime/area.h M +1-1plugins/patchreview/patchreview.cpp https://invent.kde.org/kdevelop/kdevelop/commit/74548158dc6d43a7b202a7a34e1e48d9a3f21a8e -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 375446] First stashed working set disappears
https://bugs.kde.org/show_bug.cgi?id=375446 Christoph Roick changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/kdev ||elop/kdevelop/commit/fb3f03 ||9696567f9ae0b46fe05c2e61fcb ||feb718b --- Comment #3 from Christoph Roick --- Git commit fb3f039696567f9ae0b46fe05c2e61fcbfeb718b by Christoph Roick. Committed on 23/05/2021 at 11:28. Pushed by croick into branch 'master'. Fix disappearing closed working set buttons Fix the current behavior that working set buttons of working sets that are active in another area (i.e. code, review, debug) are not part of the current closed working set collection. New working sets are persistent by default, except for newly created working sets for patch reviews. When switching from the patch review to the code area, keep the current working set open, if it is persistent (so if it is not the dynamically created one). M +6-5kdevplatform/shell/debugcontroller.cpp M +4-4kdevplatform/shell/tests/test_workingsets.cpp M +2-1kdevplatform/shell/workingsetcontroller.cpp M +3-7kdevplatform/shell/workingsets/closedworkingsetswidget.cpp M +2-7kdevplatform/shell/workingsets/workingset.cpp M +1-1kdevplatform/shell/workingsets/workingset.h M +10 -3kdevplatform/sublime/area.cpp M +5-2kdevplatform/sublime/area.h M +11 -5plugins/patchreview/patchreview.cpp https://invent.kde.org/kdevelop/kdevelop/commit/fb3f039696567f9ae0b46fe05c2e61fcbfeb718b -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 377639] Crash in "'CTest' is already being executed" dialog.
https://bugs.kde.org/show_bug.cgi?id=377639 Christoph Roick changed: What|Removed |Added Latest Commit||https://invent.kde.org/kdev ||elop/kdevelop/commit/a48287 ||f4289cbe56c5affdb8735603b79 ||3cf0f1c Version Fixed In||5.6.1 Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #10 from Christoph Roick --- Git commit a48287f4289cbe56c5affdb8735603b793cf0f1c by Christoph Roick. Committed on 23/10/2020 at 20:21. Pushed by croick into branch '5.6'. Do not block "Run All Tests" by dialog - always start a new test job without asking to kill running jobs * disable the combo box in the launch config interface By default, app jobs are compared by their executable name. If a new job name matches an old job, a dialog pops up to ask whether the old instance shall be killed. This blocks the "Run All Tests" function under some circumstances (for instance when "cmake" is used to invoke the test). The patch always makes a CTest-generated job run without asking the user. FIXED-IN: 5.6.1 M +1-0plugins/execute/executeplugin.cpp M +1-0plugins/execute/executeplugin.h M +9-5plugins/execute/nativeappconfig.cpp M +14 -12 plugins/execute/nativeappjob.cpp M +8-1plugins/execute/nativeappjob.h https://invent.kde.org/kdevelop/kdevelop/commit/a48287f4289cbe56c5affdb8735603b793cf0f1c -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 377639] Crash in "'CTest' is already being executed" dialog.
https://bugs.kde.org/show_bug.cgi?id=377639 --- Comment #7 from Christoph Roick --- How exactly do you reproduce the behavior? I created a session with the three projects you mention and selected "Run All Tests", but there is no dialog showing up about a cmake job. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 414246] New: Net Worth Report includes share value twice
https://bugs.kde.org/show_bug.cgi?id=414246
Bug ID: 414246
Summary: Net Worth Report includes share value twice
Product: kmymoney
Version: git (master)
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: reports
Assignee: kmymoney-de...@kde.org
Reporter: chris...@gmx.de
Target Milestone: ---
The fix for BUG 398982 where the opening balance in the forecast was corrected,
results in a regression in the reports.
In the reports the calculated account value already includes the share value
and therefore the fix multiplies the share value a second time.
I can obtain the desired behavior by applying this patch:
diff --git a/kmymoney/plugins/views/reports/core/pivottable.cpp
b/kmymoney/plugins/views/reports/core/pivottable.cpp
index c0d8517ed..c0f73a10f 100644
--- a/kmymoney/plugins/views/reports/core/pivottable.cpp
+++ b/kmymoney/plugins/views/reports/core/pivottable.cpp
@@ -697,7 +697,7 @@ void PivotTable::calculateOpeningBalances()
}
}
- if (account.isInvest()) {
+ if (account.isInvest() and m_config.isIncludingForecast()) {
// calculate value of shares
value *= account.deepCurrencyPrice(from.addDays(-1));
}
but I do not consider it a real fix, since to me it doesn't seem to be a
reliable distinction of cases nor did I try to understand how the account value
is obtained in the first place.
--
You are receiving this mail because:
You are watching all bug changes.
[kdevplatform] [Bug 410942] Frequent segfaults when mouse-overing C typedefs in KDevelop
https://bugs.kde.org/show_bug.cgi?id=410942 Christoph Roick changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED Latest Commit||https://invent.kde.org/kde/ ||kdevelop/commit/f81d8884bd2 ||7c9a48717000a50cdd9cc705068 ||5b Version Fixed In||5.4.3 -- You are receiving this mail because: You are watching all bug changes.
[kdevplatform] [Bug 410942] Frequent segfaults when mouse-overing C typedefs in KDevelop
https://bugs.kde.org/show_bug.cgi?id=410942 Christoph Roick changed: What|Removed |Added CC||chris...@gmx.de --- Comment #1 from Christoph Roick --- I think this might get fixed here: https://invent.kde.org/kde/kdevelop/merge_requests/59 Could you check if the crash happens, if you rename one of the "Foo"s? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 406874] Trying to access a mounted CIFS share fails
https://bugs.kde.org/show_bug.cgi?id=406874 Christoph Roick changed: What|Removed |Added CC||chris...@gmx.de -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 406805] Cannot access histograms within a directory structure in a ROOT file
https://bugs.kde.org/show_bug.cgi?id=406805 Christoph Roick changed: What|Removed |Added Latest Commit||https://commits.kde.org/lab ||plot/3a2c6ef46980d396759963 ||12ffc26c8c03d9081d Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #2 from Christoph Roick --- Git commit 3a2c6ef46980d39675996312ffc26c8c03d9081d by Christoph Roick. Committed on 12/05/2019 at 14:03. Pushed by croick into branch 'master'. Support ROOT directory structure - display histograms and trees in a directory structure - internally store key information by their unique file positions M +204 -107 src/backend/datasources/filters/ROOTFilter.cpp M +11 -3src/backend/datasources/filters/ROOTFilter.h M +77 -62 src/backend/datasources/filters/ROOTFilterPrivate.h M +75 -40 src/kdefrontend/datasources/ROOTOptionsWidget.cpp M +2-2src/kdefrontend/datasources/ROOTOptionsWidget.h https://commits.kde.org/labplot/3a2c6ef46980d39675996312ffc26c8c03d9081d -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 402617] Crash when cancelling "Find in files" during collection stage
https://bugs.kde.org/show_bug.cgi?id=402617 Christoph Roick changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 CC||chris...@gmx.de --- Comment #7 from Christoph Roick --- I could reproduce this by searching in the home folder with the current master of KDevelop. The check seems to be a proper fix. Would you provide a patch in phabricator which also includes a similar check in GrepOutputView::rowsRemoved()? -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 402026] Crash after clicking backward button in Documentation viewer or second click into url present in documentation page
https://bugs.kde.org/show_bug.cgi?id=402026 Christoph Roick changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED Latest Commit||https://commits.kde.org/kde ||velop/7419d27c604bb0e0e3219 ||46d8bddd84ba87f86ed --- Comment #5 from Christoph Roick --- Git commit 7419d27c604bb0e0e321946d8bddd84ba87f86ed by Christoph Roick. Committed on 21/12/2018 at 21:57. Pushed by croick into branch 'master'. Fix crash in documentation view A QWebEngineProfile must exist longer, than a QWebEnginePage using it. The page is now explicitly deleted before the profile. M +7-0kdevplatform/documentation/standarddocumentationview.cpp https://commits.kde.org/kdevelop/7419d27c604bb0e0e321946d8bddd84ba87f86ed -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kcrash] [Bug 395584] Signal handlers overwritten by QtWebEngine (Chromium code)
https://bugs.kde.org/show_bug.cgi?id=395584 Christoph Roick changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from Christoph Roick --- There seems to be a solution to the problem. Here is how it could work: https://phabricator.kde.org/D16004 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 393445] Navigation for Qt5 documentation works incorrectly
https://bugs.kde.org/show_bug.cgi?id=393445 Christoph Roick changed: What|Removed |Added CC||chris...@gmx.de Resolution|--- |FIXED Latest Commit||4e02a129bfbb310850965153bbe ||5adc4c6156ccb Status|UNCONFIRMED |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kcrash] [Bug 395584] New: Signal handlers overwritten by QtWebEngine (Chromium code)
https://bugs.kde.org/show_bug.cgi?id=395584 Bug ID: 395584 Summary: Signal handlers overwritten by QtWebEngine (Chromium code) Product: frameworks-kcrash Version: 5.47.0 Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: fa...@kde.org Reporter: chris...@gmx.de CC: kdelibs-b...@kde.org Target Milestone: --- Whenever QtWebEngine is used, the signal handler assignments made by KCrash are overwritten by some internal crash handler inside the Chromium part of QtWebEngine. It results in crashes with backtraces put to stdout, instead of DrKonqi popping up. This can be tested (supposing QtWebEngine is actually used) by reproducing BUG 394849 (using the PHP documentation in KDevelop and then closing the session). I'm not sure how to handle this, just wanted to bring it up, because it might reduce the number of bug reports with applications just quitting without notification. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 394849] When KDevelop is closing, the KDE complains about it
https://bugs.kde.org/show_bug.cgi?id=394849 Christoph Roick changed: What|Removed |Added CC||chris...@gmx.de, ||m...@milianw.de --- Comment #1 from Christoph Roick --- I can (probably, with QWebEngine) reproduce this, by closing KDevelop once the PHP documentation view was or is opened. @Milian: Might that still be related to https://phabricator.kde.org/R52:fae4e7ea2be0510362ecd2a202764bb2a28fd35d? -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 394856] Crash when clicking
https://bugs.kde.org/show_bug.cgi?id=394856 Christoph Roick changed: What|Removed |Added CC||chris...@gmx.de --- Comment #1 from Christoph Roick --- Do you remember if you had any toolviews opened? I was struggling with something similar recently. Where exactly did you click? -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 393637] Blinking cursor suggests focus on input field
https://bugs.kde.org/show_bug.cgi?id=393637 Christoph Roick changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||674a0e78f69fb49c5512ddf03fe ||32597dc7ca209 Status|UNCONFIRMED |RESOLVED --- Comment #7 from Christoph Roick --- Ah, thank you. I gave it a try and indeed, the current version seems to be fixed. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 393637] Blinking cursor suggests focus on input field
https://bugs.kde.org/show_bug.cgi?id=393637 --- Comment #5 from Christoph Roick --- I also use QtWebEngine 5.10.1 and experienced this on two independent Arch Linux systems. Apparently the address must be part of the selection list of already visited pages. Steps to reproduce: 1. open a new tab 2. type d u c k ... until the address is auto-completed to duckduckgo.com 3. press enter 4. now the cursor in the search field is blinking, but also the address is highlighted 5. type something; it replaces the address instead of appearing in the search field This does not seem to depend on the default start page (works with falkon:speeddial, as well as some actual url). -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 393637] Blinking cursor suggests focus on input field
https://bugs.kde.org/show_bug.cgi?id=393637 --- Comment #3 from Christoph Roick --- It actually always works, when a new tab is added. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 393637] Blinking cursor suggests focus on input field
https://bugs.kde.org/show_bug.cgi?id=393637 --- Comment #2 from Christoph Roick --- https://duckduckgo.com/ for instance. The URL has to be typed manually (not just following the link) and should not already be loaded. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 392825] Slow startup: "org.kde.plasmaquick: Applet "Clipboard" loaded after 170640 msec", Crash
https://bugs.kde.org/show_bug.cgi?id=392825 Christoph Roick changed: What|Removed |Added CC||chris...@gmx.de --- Comment #9 from Christoph Roick --- This is probably related to [1]. Wiping the ~/.local/share/klipper folder resolves this for me as well. For me the plasmashell freezes when using Mathematica which creates large chunks (>10MB) of clipboard content. [1] https://askubuntu.com/q/1024071 -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 393637] New: Blinking cursor suggests focus on input field
https://bugs.kde.org/show_bug.cgi?id=393637 Bug ID: 393637 Summary: Blinking cursor suggests focus on input field Product: Falkon Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: now...@gmail.com Reporter: chris...@gmx.de Target Milestone: --- When loading a website with input fields (such as a search engine) by entering the site's address in the address field, the input cursor jumps to the input field. In some cases (more often than not) the actual focus remains in the address field however. Input from the keyboard consequently ends up in the browser's address field instead of the input field of the website. This is disturbing, especially when the actual input field is for passwords (which then is visible in the address field). The cursor should only appear if the input element is actually focussed. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 391127] svn+ssh doesn't work with password auth
https://bugs.kde.org/show_bug.cgi?id=391127 --- Comment #9 from Christoph Roick --- @Kevin: I'm not fully convinced. One problem is, that SSH_ASKPASS is ignored if a terminal is set [1]. So one would have to trick ssh into believing that there is no terminal; which is explained in [1]. Interestingly ssh-askpass is not part of my system (probably due to relying on the environment variable). That's where the idea of making KDevelop itself some kind of default askpass program was coming from. Nevertheless, setting the environment variable to some default value would surely be a start. [1] https://unix.stackexchange.com/a/272524 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 391320] crash on copy multiple files
https://bugs.kde.org/show_bug.cgi?id=391320 Christoph Roick changed: What|Removed |Added CC||chris...@gmx.de --- Comment #6 from Christoph Roick --- I think that has been fixed already with commit f3229baa. And Kevin, you cherry-picked it for the 5.2 version. However, the latest AppImage seems to date from before the fix. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 391127] svn+ssh doesn't work with password auth
https://bugs.kde.org/show_bug.cgi?id=391127 --- Comment #7 from Christoph Roick --- Ok, but what should it be set to? KDevelop doesn't really know what kind of program could be used to query a password, no? Maybe a call to KDevelop itself with a new parameter could be used? Like: SSH_ASKPASS="kdevelop --query-pw" -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 391127] svn+ssh doesn't work with password auth
https://bugs.kde.org/show_bug.cgi?id=391127 --- Comment #4 from Christoph Roick --- You are right, when run from a terminal, the password seems to be always requested there inside (which is not specific for svn). I was referring to having SSH_ASKPASS=ksshaskpass set for the environment, when starting the usual way. The point is, that the SVN library never gives a response to KDevelop requesting a password, since it directly calls ssh. And ssh prompts for the password in the terminal if there is one or uses SSH_ASKPASS otherwise. I don't see how this could easily be fixed. Maybe consider setting the environment variable as a workaround. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 391127] svn+ssh doesn't work with password auth
https://bugs.kde.org/show_bug.cgi?id=391127 --- Comment #2 from Christoph Roick --- Using "SSH_ASKPASS=ksshaskpass" (https://wiki.archlinux.org/index.php/KDE_Wallet) or "SSH_ASKPASS=" (password will be asked in the terminal) I cannot confirm the issue. Some problems were fixed in commit 9fd4f6c25f6c712a76672e0b3acbefef7d4fd155, but they are not directly related to ssh authentication. What kind of error do you get? -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 389418] Option to not close open program does not work
https://bugs.kde.org/show_bug.cgi?id=389418 Christoph Roick changed: What|Removed |Added Latest Commit||d896e7489b743d8691e480378c8 ||6f2b1ee0524b0 CC||chris...@gmx.de Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #1 from Christoph Roick --- There is a fix for this in the current master branch, but it is not part of 5.2. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 384372] baloo_file_extractor always high CPU usage
https://bugs.kde.org/show_bug.cgi?id=384372 Christoph Roick changed: What|Removed |Added CC||chris...@gmx.de --- Comment #4 from Christoph Roick --- (In reply to Rainer Finke from comment #3) > I have the same issue. baloo_file_extractor consumes 100% on one of my CPU > cores. If I kill the service and restart, it consumes again 100%. But this > issue is new to me, maybe since Frameworks 5.40 or any other recent change. I can confirm. It startet doing that just recently. Arch Linux KDE Frameworks 5.40 Plasma 5.11.4 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 385995] Variables display not showing data pointed to by shared_ptr
https://bugs.kde.org/show_bug.cgi?id=385995 Christoph Roick changed: What|Removed |Added CC||chris...@gmx.de Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 --- Comment #1 from Christoph Roick --- I can confirm and in some cases this makes the debug mode only half-useful. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 371235] vi-mode: ":tabe anything" crashed KDevelop
https://bugs.kde.org/show_bug.cgi?id=371235 Christoph Roick changed: What|Removed |Added Latest Commit||http://commits.kde.org/kdev ||elop/d1666b51297597eae00f58 ||a6e43d9cf4fe0f7d3f Status|CONFIRMED |RESOLVED Resolution|--- |FIXED CC||chris...@gmx.de --- Comment #3 from Christoph Roick --- There was no implementation for opening a new file from the KTextEditor plugin, but the VI module expects a valid result. This specific issue in KDevelop should be fixed. Other problems in VI mode are addressed in a separate revision https://phabricator.kde.org/D8710 . -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 385895] Crash when scrolling through tabs
https://bugs.kde.org/show_bug.cgi?id=385895 Christoph Roick changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WORKSFORME --- Comment #1 from Christoph Roick --- I could not reproduce this again, so I'll close it. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 386388] kdevelop crash when opening a project containing javascript files
https://bugs.kde.org/show_bug.cgi?id=386388 Christoph Roick changed: What|Removed |Added CC||chris...@gmx.de --- Comment #2 from Christoph Roick --- I cannot confirm. Did you try clearing the cache? -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 385895] New: Crash when scrolling through tabs
https://bugs.kde.org/show_bug.cgi?id=385895 Bug ID: 385895 Summary: Crash when scrolling through tabs Product: kdevelop Version: 5.1.80 Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: chris...@gmx.de Target Milestone: --- Application: kdevelop (5.1.80) (Compiled from sources) Qt Version: 5.9.2 Frameworks Version: 5.39.0 Operating System: Linux 4.13.7-2-ck x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: Quickly scrolling through tabs of opened documents (20 or so opened at the same time) - Unusual behavior I noticed: Maybe it is related to a class which derives from a std::vector and does not have correct highlighting. Cannot be reproduced when running kdevelop with gdb, so looks like a race condition. The crash can be reproduced sometimes. -- Backtrace: Application: KDevelop (kdevelop), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7ff7e46c20c0 (LWP 3337))] Thread 14 (Thread 0x7ff74f7fe700 (LWP 3910)): #0 0x7ff7d89004ed in () at /usr/lib/libglib-2.0.so.0 #1 0x7ff7d890169b in g_main_context_prepare () at /usr/lib/libglib-2.0.so.0 #2 0x7ff7d8901df6 in () at /usr/lib/libglib-2.0.so.0 #3 0x7ff7d8901fae in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #4 0x7ff7e1d33cf4 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7ff7e1cd748b in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7ff7e1af027e in QThread::exec() () at /usr/lib/libQt5Core.so.5 #7 0x7ff7e1af4fcb in () at /usr/lib/libQt5Core.so.5 #8 0x7ff7daac908a in start_thread () at /usr/lib/libpthread.so.0 #9 0x7ff7e140124f in clone () at /usr/lib/libc.so.6 Thread 13 (Thread 0x7ff74700 (LWP 3859)): #0 0x7ff7d8929664 in g_mutex_unlock () at /usr/lib/libglib-2.0.so.0 #1 0x7ff7d8901761 in g_main_context_prepare () at /usr/lib/libglib-2.0.so.0 #2 0x7ff7d8901df6 in () at /usr/lib/libglib-2.0.so.0 #3 0x7ff7d8901fae in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #4 0x7ff7e1d33cf4 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7ff7e1cd748b in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7ff7e1af027e in QThread::exec() () at /usr/lib/libQt5Core.so.5 #7 0x7ff7705eec1a in () at /usr/lib/qt/qml/QtQuick/XmlListModel/libqmlxmllistmodelplugin.so #8 0x7ff7e1af4fcb in () at /usr/lib/libQt5Core.so.5 #9 0x7ff7daac908a in start_thread () at /usr/lib/libpthread.so.0 #10 0x7ff7e140124f in clone () at /usr/lib/libc.so.6 Thread 12 (Thread 0x7ff772ffd700 (LWP 3610)): #0 0x7ff7daacf38d in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7ff7e1af645c in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7ff7d5ee742f in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7ff7d5eec4d9 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7ff7d5ee6924 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7ff7d5eec532 in () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7ff7d5ee6924 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #7 0x7ff7d5eec532 in () at /usr/lib/libKF5ThreadWeaver.so.5 #8 0x7ff7d5ee6924 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #9 0x7ff7d5eec532 in () at /usr/lib/libKF5ThreadWeaver.so.5 #10 0x7ff7d5ee6924 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #11 0x7ff7d5eec532 in () at /usr/lib/libKF5ThreadWeaver.so.5 #12 0x7ff7d5ee6924 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #13 0x7ff7d5eec532 in () at /usr/lib/libKF5ThreadWeaver.so.5 #14 0x7ff7d5ee6924 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #15 0x7ff7d5eec532 in () at /usr/lib/libKF5ThreadWeaver.so.5 #16 0x7ff7d5ee6924 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #17 0x7ff7d5eec532 in () at /usr/lib/libKF5ThreadWeaver.so.5 #18 0x7ff7d5ee6924 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #19 0x7ff7d5ee9ce3 in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWea
[kate] [Bug 359682] spellcheck dialog does not appear in Kate/Kwrite on Fedora 23/24
https://bugs.kde.org/show_bug.cgi?id=359682 Christoph Roick changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED Latest Commit||https://commits.kde.org/kte ||xteditor/9a77f365de57b26aa0 ||4c8db6d587bdba93db8433 --- Comment #9 from Christoph Roick --- Git commit 9a77f365de57b26aa04c8db6d587bdba93db8433 by Christoph Roick. Committed on 05/10/2017 at 19:55. Pushed by croick into branch 'master'. Fix missing spell check bar Summary: - the spell check bar removes itself from the bottom view bar, now is added again when required Test Plan: - write a text with spelling errors - run the spell check, ignore errors - run the spell check again, with the bar widget correctly showing up now Reviewers: #ktexteditor, dhaumann Reviewed By: #ktexteditor, dhaumann Subscribers: dhaumann, #frameworks Tags: #kate, #frameworks Differential Revision: https://phabricator.kde.org/D8148 M +2-2src/spellcheck/spellcheckdialog.cpp https://commits.kde.org/ktexteditor/9a77f365de57b26aa04c8db6d587bdba93db8433 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 384977] Crash when switching any toolview position
https://bugs.kde.org/show_bug.cgi?id=384977 Christoph Roick changed: What|Removed |Added Resolution|--- |FIXED CC||chris...@gmx.de Latest Commit||16abb2d78ec0 Status|CONFIRMED |RESOLVED Version Fixed In||5.2 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 384828] Crash when hiding widget toobar
https://bugs.kde.org/show_bug.cgi?id=384828 Christoph Roick changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Version Fixed In||5.2 Latest Commit||16abb2d78ec0 Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 384828] Crash when hiding widget toobar
https://bugs.kde.org/show_bug.cgi?id=384828 --- Comment #2 from Christoph Roick --- Sorry, can be reproduced by using the context menu of the widget title, not the toolbar button. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 384828] Crash when hiding widget toobar
https://bugs.kde.org/show_bug.cgi?id=384828 Christoph Roick changed: What|Removed |Added CC||chris...@gmx.de --- Comment #1 from Christoph Roick --- Fixed in 5.2: https://phabricator.kde.org/D6261 -- You are receiving this mail because: You are watching all bug changes.
[kdevplatform] [Bug 384899] find/replace key persistence causes find/replace toolview "trolling"
https://bugs.kde.org/show_bug.cgi?id=384899 --- Comment #6 from Christoph Roick --- It should stay silent with the new patch: https://phabricator.kde.org/D7945 It still keeps the old search parameters accessible. -- You are receiving this mail because: You are watching all bug changes.
[kdevplatform] [Bug 384899] find/replace key persistence causes find/replace toolview "trolling"
https://bugs.kde.org/show_bug.cgi?id=384899 --- Comment #4 from Christoph Roick --- Actually I didn't think about different views, so I admit this can get annoying. What do you think about just storing the search parameters and letting the user decide when to click the "Refresh" button? -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 380125] crash when hitting "next change" in the patchreview plugin after making an (unsaved) edit
https://bugs.kde.org/show_bug.cgi?id=380125 --- Comment #5 from Christoph Roick --- It will only be fixed in 5.2.0. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 377639] Crash in "'CTest' is already being executed" dialog.
https://bugs.kde.org/show_bug.cgi?id=377639 --- Comment #4 from Christoph Roick --- (In reply to Christoph Roick from comment #3) > This should be fixed with commit > https://phabricator.kde.org/R33:3ed8698f1baca73e2d7cb4400c90e6950a8ad623 > already. Well, it's not, since jobs may mutually kill each other. I managed to fix the NativeAppJob, but now it randomly crashes somewhere else. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 377639] Crash in "'CTest' is already being executed" dialog.
https://bugs.kde.org/show_bug.cgi?id=377639 Christoph Roick changed: What|Removed |Added CC||chris...@gmx.de --- Comment #3 from Christoph Roick --- This should be fixed with commit https://phabricator.kde.org/R33:3ed8698f1baca73e2d7cb4400c90e6950a8ad623 already. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 381754] Drop-down list is not saved
https://bugs.kde.org/show_bug.cgi?id=381754 Christoph Roick changed: What|Removed |Added CC||chris...@gmx.de --- Comment #1 from Christoph Roick --- I included a fix in this pending revision: https://phabricator.kde.org/D6262 Until then, you may use the enter key to start the search. It will save the changed line before closing the dialog. -- You are receiving this mail because: You are watching all bug changes.
