[digikam] [Bug 447767] Face detection on Sony ARW files does not detect the correct face area
https://bugs.kde.org/show_bug.cgi?id=447767 --- Comment #26 from Igor Skoric --- @Maik This precise issue is mostly resolved for me with the workaround. Maybe Digikam should give a one-time warning to raw format users if the preview image ratio does not match the raw image ratio? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 447767] Face detection on Sony ARW files does not detect the correct face area
https://bugs.kde.org/show_bug.cgi?id=447767 --- Comment #24 from Igor Skoric --- > @Igor, if you set the digiKam view to full with half RAW view, it would work > for you. @Maik I think we already established that it would work like that as a workaround. What it it that you would like me to test? Are we expecting a regression on that? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 447767] Face detection on Sony ARW files does not detect the correct face area
https://bugs.kde.org/show_bug.cgi?id=447767 --- Comment #22 from Igor Skoric --- @gilles.caulier I did some testing right now: * installed Digikam 8.4.0 from flatpak today * left all install options on default * downloaded the same test files i sent you * selected yolo v3 * did face discovery and recognition Unfortunately it is still the same as before. The JPEG works fine but the ARW has misplaced detection rectangles. Comparison: https://imgur.com/GFYJZGK -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 486949] Kdevelop freezes after git checkout feature-branch
https://bugs.kde.org/show_bug.cgi?id=486949 --- Comment #6 from Igor Kushnir --- (In reply to Igor Kushnir from comment #5) > Maybe a simpler fix exists, > but I don't see it yet, and I'm not even sure my guess about the source of > many `git status` jobs is correct. The essence of the convoluted function GitPlugin::parseGitStatusOutput() is 14 years old. Perhaps this function can be simplified and optimized so as to avoid calling getLsFiles() from it. Even GitPlugin::parseGitStatusOutput_old() seems more efficient (though it is likely less correct because practically untested for a long while). Merge requests are welcome. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 486949] Kdevelop freezes after git checkout feature-branch
https://bugs.kde.org/show_bug.cgi?id=486949 --- Comment #5 from Igor Kushnir --- The backtrace seems to be a recursion, but is not, because getLsFiles() does not connect the parseGitStatusOutput() slot to any signal. So it looks like a lot of `git status` jobs finish one after another, each job's result is handled in the previous job's nested event loop and thus blocks the previous job's progress. I suspect the jobs are triggered by many almost simultaneous ProjectModel::rowsInserted signals, to which the ProjectChangesModel::itemsAdded() slot is connected, which in turn calls ProjectChangesModel::changes(), and IBasicVersionControl::status() is called from there. This is not the first time that the slowness of many non-parallel git commands causes a UI freeze: https://invent.kde.org/kdevelop/kdevelop/-/merge_requests/299 . Replacing job->exec() in GitPlugin::getLsFiles() with running the process asynchronously could help, but the implementation of DVcsJob::jobIsReady() does not allow such an optimization, because it emits result right after emitting readyForParsing(). So such a fix would require some DVcsJob redesign and adjustments to all DVCS plugins. Maybe a simpler fix exists, but I don't see it yet, and I'm not even sure my guess about the source of many `git status` jobs is correct. -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 494111] New: Message encrypted by device not verified by its owner may be shown encrypted
https://bugs.kde.org/show_bug.cgi?id=494111 Bug ID: 494111 Summary: Message encrypted by device not verified by its owner may be shown encrypted Classification: Applications Product: NeoChat Version: 24.08.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: fe...@posteo.de Reporter: igor.mironc...@gmail.com CC: c...@carlschwan.eu Target Milestone: --- Created attachment 174411 --> https://bugs.kde.org/attachment.cgi?id=174411&action=edit How it looks in Element *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports Please remove this comment after reading and before submitting - thanks! *** SUMMARY In Element I have a room, and opponent reported there with "Encrypted by device not verified by its owner". In this case NeoChat shows message from him with "This message is encrypted and the sender has not shared the key with this device.", but restarting of NeoChat may show some of them, some of them keep encrypted. STEPS TO REPRODUCE 1. Make a room with person with "Encrypted by device not verified by its owner". I don't know how to do it on other side... Ask Carl Schwan how he did it. 2. Chat with opponent. 3. OBSERVED RESULT Messages from him may be shown as "This message is encrypted and the sender has not shared the key with this device." In Element messages are shown, but marked - look at the attached screenshot. EXPECTED RESULT I'd like to see a message. SOFTWARE/OS VERSIONS Windows: macOS: (available in the Info Center app, or by running `kinfo` in a terminal window) Linux/KDE Plasma: KDE neon 6.0 KDE Plasma Version: 6.1.5 KDE Frameworks Version: 6.6.0 Qt Version: 6.7.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 494101] New: Info of room appears when not intended
https://bugs.kde.org/show_bug.cgi?id=494101 Bug ID: 494101 Summary: Info of room appears when not intended Classification: Applications Product: NeoChat Version: 24.08.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: fe...@posteo.de Reporter: igor.mironc...@gmail.com CC: c...@carlschwan.eu Target Milestone: --- *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports Please remove this comment after reading and before submitting - thanks! *** SUMMARY Some transitions of views shows not intended room info sidebar on the right. STEPS TO REPRODUCE 1. Open any existing room with friend you already have 2. Close there Room Information sidebar (if opened) 3. Click Home button 4. Click Friends button 5. Select existing room with friend OBSERVED RESULT Room Information sidebar opens with room EXPECTED RESULT I'd like to see just room with messages, and Room Information sidebar to be folded. SOFTWARE/OS VERSIONS Windows: macOS: (available in the Info Center app, or by running `kinfo` in a terminal window) Linux/KDE Plasma: KDE neon 6.0 KDE Plasma Version: 5.1.5 KDE Frameworks Version: 6.6.0 Qt Version: 6.7.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 494094] Previous encrypted messages are not decrypted if they were written in other client before verifying NeoChat
https://bugs.kde.org/show_bug.cgi?id=494094 Igor Mironchik changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #3 from Igor Mironchik --- (In reply to Tobias Fella from comment #1) > Did you activate the "Never send encrypted messages to unverified sessions > from this session" checkbox in element? if you do that, it won't send > encryption keys to unverified sessions No, this option is turned off, look screenshot. -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 494094] Previous encrypted messages are not decrypted if they were written in other client before verifying NeoChat
https://bugs.kde.org/show_bug.cgi?id=494094 --- Comment #2 from Igor Mironchik --- Created attachment 174398 --> https://bugs.kde.org/attachment.cgi?id=174398&action=edit Room settings in Element -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 494095] New: Settings button produces new dialog instance on every click
https://bugs.kde.org/show_bug.cgi?id=494095 Bug ID: 494095 Summary: Settings button produces new dialog instance on every click Classification: Applications Product: NeoChat Version: 24.08.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: fe...@posteo.de Reporter: igor.mironc...@gmail.com CC: c...@carlschwan.eu Target Milestone: --- Created attachment 174396 --> https://bugs.kde.org/attachment.cgi?id=174396&action=edit Settings button. *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports Please remove this comment after reading and before submitting - thanks! *** SUMMARY Settings button produces new dialog instance on every click (see attached screenshot with button I'm talking about) STEPS TO REPRODUCE 1. Click on setting button 2. Click again and again 3. OBSERVED RESULT Every click creates new instance of settings dialog EXPECTED RESULT Settings dialog should be alone and next clicking on settings button should activate previous dialog window if it's already opened SOFTWARE/OS VERSIONS Windows: macOS: (available in the Info Center app, or by running `kinfo` in a terminal window) Linux/KDE Plasma: KDE neon 6.0 KDE Plasma Version: 6.1.5 KDE Frameworks Version: 6.6.0 Qt Version: 6.7.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 494094] New: Previous encrypted messages are not decrypted if they were written in other client before verifying NeoChat
https://bugs.kde.org/show_bug.cgi?id=494094 Bug ID: 494094 Summary: Previous encrypted messages are not decrypted if they were written in other client before verifying NeoChat Classification: Applications Product: NeoChat Version: 24.08.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: fe...@posteo.de Reporter: igor.mironc...@gmail.com CC: c...@carlschwan.eu Target Milestone: --- *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports Please remove this comment after reading and before submitting - thanks! *** SUMMARY Previous encrypted messages are not decrypted if they were written in other client before verifying NeoChat STEPS TO REPRODUCE 1. Create encrypted room with somebody in any Matrix client before any NeoChat verifications 2. Type there messages 3. Install NeoChat and verify your devices OBSERVED RESULT I see all my rooms, but messages in them are encrypted and I see a text on each message: "This message is encrypted and the sender has not shared the key with this device." But, to be honest, new messages are seen on all devices. EXPECTED RESULT Messages should be decrypted and seen in NeoChat when device is verified. SOFTWARE/OS VERSIONS Windows: macOS: (available in the Info Center app, or by running `kinfo` in a terminal window) Linux/KDE Plasma: KDE neon 6.0 KDE Plasma Version: 6.1.5 KDE Frameworks Version: 6.6.0 Qt Version: 6.7.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 482310] About this System page: "Graphics Processor" field should include the driver version
https://bugs.kde.org/show_bug.cgi?id=482310 Igor Murzich changed: What|Removed |Added CC||imurz...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 493906] Rename symbol sometimes crashes KDevelop
https://bugs.kde.org/show_bug.cgi?id=493906 Igor Kushnir changed: What|Removed |Added Status|REPORTED|RESOLVED CC||igor...@gmail.com Resolution|--- |DUPLICATE --- Comment #1 from Igor Kushnir --- *** This bug has been marked as a duplicate of bug 492221 *** -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 492221] crash in click to 'show use' (only in large project)
https://bugs.kde.org/show_bug.cgi?id=492221 Igor Kushnir changed: What|Removed |Added CC||ad...@leinir.dk --- Comment #14 from Igor Kushnir --- *** Bug 493906 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 493908] Setting FOLDER property on CMake executable breaks launch configuration detection
https://bugs.kde.org/show_bug.cgi?id=493908 Igor Kushnir changed: What|Removed |Added CC||igor...@gmail.com --- Comment #1 from Igor Kushnir --- I have never used the FOLDER property myself, but recently stumbled upon the commit that added a related feature: https://commits.kde.org/kdevelop/ddca5c1fdd169aee750489958a38fb1c8edcee5f . Either the intended behavior doesn't suit your workflow or there is a bug in the original implementation or a regression crept into the code at some point. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 486932] Crash when adding an #include statement during normal editing
https://bugs.kde.org/show_bug.cgi?id=486932 --- Comment #14 from Igor Kushnir --- (In reply to painless roaster from comment #13) > is this it? > > https://github.com/llvm/llvm-project/issues/105994 ? Probably not. I don't think this KDevelop crash can be reproduced via a regular compilation. The backtrace looks different. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 486932] Crash when adding an #include statement during normal editing
https://bugs.kde.org/show_bug.cgi?id=486932 Igor Kushnir changed: What|Removed |Added Summary|Background parser crash C++ |Crash when adding an |source |#include statement during ||normal editing -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 493533] crash when inserting #include ... during normal editing
https://bugs.kde.org/show_bug.cgi?id=493533 Igor Kushnir changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE CC||igor...@gmail.com --- Comment #2 from Igor Kushnir --- *** This bug has been marked as a duplicate of bug 486932 *** -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 486932] Background parser crash C++ source
https://bugs.kde.org/show_bug.cgi?id=486932 Igor Kushnir changed: What|Removed |Added CC||painless.roas...@gmail.com --- Comment #12 from Igor Kushnir --- *** Bug 493533 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 458510] QtHelp homepage lists duplicates for every entry
https://bugs.kde.org/show_bug.cgi?id=458510 Igor Kushnir changed: What|Removed |Added Assignee|kdevelop-bugs-n...@kde.org |igor...@gmail.com Status|CONFIRMED |ASSIGNED --- Comment #6 from Igor Kushnir --- (In reply to David Redondo from comment #4) > But doing that I encountered another bug, there was initially no content at > all. I had to toggle the checkbox in the settings so it would appear. Looks like this other bug has been fixed (probably by Milian during the Qt 6 porting). I just found how Qt Creator detects missing documentation files in a function named cleanUpDocumentation(), then unregisters the corresponding documentation namespaces. I'll try to do the same cleanup on KDevelop start and finally fix this bug. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 492628] Cannot paste file
https://bugs.kde.org/show_bug.cgi?id=492628 Igor Kushnir changed: What|Removed |Added Status|REPORTED|RESOLVED CC||igor...@gmail.com Resolution|--- |DUPLICATE --- Comment #1 from Igor Kushnir --- *** This bug has been marked as a duplicate of bug 435235 *** -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 435235] When pasting file using Projects tool view, "File Already Exists" window cannot be interacted with
https://bugs.kde.org/show_bug.cgi?id=435235 --- Comment #15 from Igor Kushnir --- *** Bug 492628 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 492221] crash in click to 'show use' (only in large project)
https://bugs.kde.org/show_bug.cgi?id=492221 Igor Kushnir changed: What|Removed |Added Latest Commit|https://invent.kde.org/kdev |https://invent.kde.org/kdev |elop/kdevelop/-/commit/32d3 |elop/kdevelop/-/commit/c7d5 |88680839d22c8d635dc8c63a7a8 |09b5846f24760c6af2dbb5fec8e |845901e96 |727c5a86a --- Comment #12 from Igor Kushnir --- Git commit c7d509b5846f24760c6af2dbb5fec8e727c5a86a by Igor Kushnir. Committed on 04/09/2024 at 17:52. Pushed by igorkushnir into branch 'release/24.08'. UsesWidget: don't try to insert items at invalid positions cb01708424c1b21077761c6259e50fec1fac071f intended to insert high-priority uses at the top, normal-priority in the middle, and low-priority ones (declaration/definition-only) at the bottom. But optionally passing widget->items().size() as the insertion position to NavigatableWidgetList::addItem() cannot achieve that. Furthermore, the number of items in `widget` can be greater than the number of items in the higher-level `m_widget`. In this case KDevelop eventually segfaults in QBoxLayout::itemAt() since Qt 6, or given a Qt build with assertions enabled, the "index out of range" assertion fails in QBoxLayout::insertWidget() => QBoxLayoutPrivate::validateIndex(). Remove the broken and crashing insertion at widget->items().size() and insert both normal- and low-priority uses at the bottom for now. FIXED-IN: 6.0.240801 (cherry picked from commit 32d388680839d22c8d635dc8c63a7a8845901e96) M +6-1kdevplatform/language/duchain/navigation/useswidget.cpp https://invent.kde.org/kdevelop/kdevelop/-/commit/c7d509b5846f24760c6af2dbb5fec8e727c5a86a -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 492221] crash in click to 'show use' (only in large project)
https://bugs.kde.org/show_bug.cgi?id=492221 Igor Kushnir changed: What|Removed |Added Latest Commit||https://invent.kde.org/kdev ||elop/kdevelop/-/commit/32d3 ||88680839d22c8d635dc8c63a7a8 ||845901e96 Status|ASSIGNED|RESOLVED Version Fixed In||6.0.240801 Resolution|--- |FIXED --- Comment #11 from Igor Kushnir --- Git commit 32d388680839d22c8d635dc8c63a7a8845901e96 by Igor Kushnir. Committed on 04/09/2024 at 15:23. Pushed by igorkushnir into branch 'master'. UsesWidget: don't try to insert items at invalid positions cb01708424c1b21077761c6259e50fec1fac071f intended to insert high-priority uses at the top, normal-priority in the middle, and low-priority ones (declaration/definition-only) at the bottom. But optionally passing widget->items().size() as the insertion position to NavigatableWidgetList::addItem() cannot achieve that. Furthermore, the number of items in `widget` can be greater than the number of items in the higher-level `m_widget`. In this case KDevelop eventually segfaults in QBoxLayout::itemAt() since Qt 6, or given a Qt build with assertions enabled, the "index out of range" assertion fails in QBoxLayout::insertWidget() => QBoxLayoutPrivate::validateIndex(). Remove the broken and crashing insertion at widget->items().size() and insert both normal- and low-priority uses at the bottom for now. FIXED-IN: 6.0.240801 M +6-1kdevplatform/language/duchain/navigation/useswidget.cpp https://invent.kde.org/kdevelop/kdevelop/-/commit/32d388680839d22c8d635dc8c63a7a8845901e96 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 492398] After upgrade from 5.7 to 6.0 kdevelop starts in nonfunc state and cannot open *.pro files anymore
https://bugs.kde.org/show_bug.cgi?id=492398 Igor Kushnir changed: What|Removed |Added Resolution|--- |DOWNSTREAM Status|REPORTED|RESOLVED CC||igor...@gmail.com --- Comment #3 from Igor Kushnir --- *Building* KDevQMakeManager requires kdevelop-pg-qt version 2.3 or later. Looks like https://gitlab.archlinux.org/archlinux/packaging/packages/kdevelop/-/commit/376b17582443bd7a55715dc1c261f649ad7c391f fixed the Arch packaging issue today. Install the optional astyle dependency of the kdevelop package if you want to use the kdevastyle formatting plugin. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 492221] crash in click to 'show use' (only in large project)
https://bugs.kde.org/show_bug.cgi?id=492221 --- Comment #7 from Igor Kushnir --- Looks like a dangling pointer or memory corruption. > I also tried a custom compile to rule out a build error. But it still > crashed. And version 24.05.2 is still without problems. > If further plasma/qt updates don't help, I'll have to find the commit that > caused the problem. Just created a tag https://invent.kde.org/kdevelop/kdevelop/-/tags/v5.15 at the last KF5 commit. If/when you decide to bisect, you can compile KDevelop at the tagged commit against KF5/Qt5 and see if the crash is present. And you can check whether the crash is present in this early working KF6 commit: https://commits.kde.org/kdevelop/256bf70b947d0508a08f8321b69a4b8f375dab13 . If the crash is present in one but absent from the other of the two commits, we can be almost certain the regression is caused by the upgrade to KF6/Qt6 itself rather than some other KDevelop code change. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 492221] crash in click to 'show use' (only in large project)
https://bugs.kde.org/show_bug.cgi?id=492221 --- Comment #4 from Igor Kushnir --- (In reply to painless roaster from comment #3) > If further plasma/qt updates don't help, I'll have to find the commit that > caused the problem. You can start by installing KDevelop and Qt debug symbols to obtain a more detailed backtrace, possibly with deeper call stack and values of function arguments. Should be easy with https://fedoraproject.org/wiki/Debuginfod -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 492221] crash in click to 'show use' (only in large project)
https://bugs.kde.org/show_bug.cgi?id=492221 Igor Kushnir changed: What|Removed |Added CC||igor...@gmail.com Status|REPORTED|NEEDSINFO Resolution|--- |WORKSFORME --- Comment #2 from Igor Kushnir --- Cannot reproduce and the KDevelop code at the end of the backtrace looks OK to me. Have you tried showing uses of a variable in another (small) project? Have you tried clearing the cache? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kcodecs] [Bug 491824] KEncodingProber misdetects short UTF-8 text as Shift_JIS or gb18030 with high confidence=0.99
https://bugs.kde.org/show_bug.cgi?id=491824 --- Comment #1 from Igor Kushnir --- OBSERVED RESULT Step 2: QDEBUG : KEncodingProberTest::testProbe() Text: "Этот" QDEBUG : KEncodingProberTest::testProbe() state: 2 confidence: 0.99 encoding: "Shift_JIS" XFAIL : KEncodingProberTest::testProbe() KEncodingProber misdetects short UTF-8 text as Shift_JIS or gb18030 Loc: [kcodecs/autotests/kencodingprobertest.cpp(54)] QDEBUG : KEncodingProberTest::testProbe() state: 2 confidence: 0.28 encoding: "gb18030" XFAIL : KEncodingProberTest::testProbe() KEncodingProber::reset() leaves behind earlier fed data, so this is detected as gb18030 now Loc: [kcodecs/autotests/kencodingprobertest.cpp(60)] QDEBUG : KEncodingProberTest::testProbe() state: 2 confidence: 0.44 encoding: "gb18030" XFAIL : KEncodingProberTest::testProbe() KEncodingProber::reset() leaves behind earlier fed data, so the confidence is lower now Loc: [kcodecs/autotests/kencodingprobertest.cpp(66)] Step 4: same as step 2, except that "Shift_JIS" is replaced by "gb18030" at the end of the second line of the posted output. EXPECTED RESULT A. KEncodingProber detects the encoding of the short UTF-8 text as UTF-8. Or as some other encoding but with a confidence much lower than 0.99. B. The documented and actual behavior of KEncodingProber::reset() match. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kcodecs] [Bug 491824] New: KEncodingProber misdetects short UTF-8 text as Shift_JIS or gb18030 with high confidence=0.99
https://bugs.kde.org/show_bug.cgi?id=491824 Bug ID: 491824 Summary: KEncodingProber misdetects short UTF-8 text as Shift_JIS or gb18030 with high confidence=0.99 Classification: Frameworks and Libraries Product: frameworks-kcodecs Version: 6.5.0 Platform: Compiled Sources OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: igor...@gmail.com Target Milestone: --- Created attachment 172704 --> https://bugs.kde.org/attachment.cgi?id=172704&action=edit Patch for kencodingprobertest.cpp that demonstrates the bug SUMMARY KEncodingProber detects UTF-8-encoded 4 Russian characters (8 bytes) as Shift_JIS with confidence=0.99. Appending the end-of-line character '\n' to these 8 bytes makes KEncodingProber detect this short text as gb18030 with the same high confidence of 0.99. This issue was discovered while testing KDevelop's single use of KEncodingProber: https://invent.kde.org/kdevelop/kdevelop/-/issues/71#note_1007105 Also KEncodingProber::reset() leaves behind earlier fed data. It is documented as "reset the prober's internal state and data." So either reset()'s behavior is wrong or the documentation misleading. STEPS TO REPRODUCE 1. Download the attached patch, apply it to kcodecs and build. 2. Run the following command from the build directory of kcodecs: QT_LOGGING_RULES='default.debug=true' ./bin/kencodingprobertest 3. Replace `#if 1` with `#if 0` in the code added by the patch and rebuild kcodecs. 4. Repeat step 2. 5. Read and compare the two test run outputs and the patch itself. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 491620] Kdevelop5 crashes when opening U-Boot source
https://bugs.kde.org/show_bug.cgi?id=491620 Igor Kushnir changed: What|Removed |Added CC||igor...@gmail.com --- Comment #1 from Igor Kushnir --- The crash is at this line https://invent.kde.org/kdevelop/kdevelop/-/blob/release/23.08/plugins/clang/clangparsejob.cpp#L184 : projectPaths.append(bsm->buildDirectory(project->projectItem())); Probably the buildSystemManager is null. What project manager do you use for this project? > Kdevelop5 crashes when opening U-Boot source tree subdirectory "net" Do you mean opening a project with this "net" subdirectory as the root directory? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 488164] In split view cursor jumps to unexpected position
https://bugs.kde.org/show_bug.cgi?id=488164 --- Comment #9 from Igor Kushnir --- (In reply to Waqar Ahmed from comment #8) > Can't reproduce with Kate. I think this is a Kdevelop issue Just reproduced again in Kate 24.05.2. Have you tried the steps to reproduce in the bug description, taking into account clarifications in the Comment 3 above? Note: after the step 4 the Find/Replace panel, which spans the width of both left and right split views, becomes hidden; at the step 5 click close to the right view's bottom, where the panel is going to reappear. -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 408890] Livepreview runs BibTeX instead of Biber
https://bugs.kde.org/show_bug.cgi?id=408890 --- Comment #7 from Igor --- (In reply to Andrew Nowa Ammerlaan from comment #6) > As a workaround: In ~/.config/kilerc ... Thanks for your comments. With this workaround, will bibtex be also auto-detected? If not, it has no advantage over my workaround - to replace "bibtex" by "biber" in the Build-BibTex setting. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 489638] Plasma crashed in QWindowPrivate::connectToScreen() when trying to open Klipper paste menu with keyboard shortcut Meta+V
https://bugs.kde.org/show_bug.cgi?id=489638 Igor changed: What|Removed |Added CC||igorpa...@tutanota.com -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 408890] Livepreview runs BibTeX instead of Biber
https://bugs.kde.org/show_bug.cgi?id=408890 Igor changed: What|Removed |Added CC||i...@sai.msu.ru --- Comment #3 from Igor --- Five years since the original bug report, and I just run across the same bug with kile 2.9.94. When using biblatex with the biber backend in my source latex file, pressing "latex" button still runs bibtex instead of biber, which results in the error message "[BibTex] Finished with the exit code 2". Inspecting logs shows that (quite naturally) bibtex did not find any citations. The difference with the bug report above is that in my case the Build->Biber setting includes "biber" in the command line (not /usr/bin/biber). For the bug report author this solved the problem. For me, it does not. The rough workaround is to change "bibtex" by "biber" in the command line of the Build->Bibtex setting. This is clearly not the best solution. -- You are receiving this mail because: You are watching all bug changes.
[KleverNotes] [Bug 489528] New: UI for making attachments
https://bugs.kde.org/show_bug.cgi?id=489528 Bug ID: 489528 Summary: UI for making attachments Classification: Applications Product: KleverNotes Version: 1.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Editor Assignee: schul9lo...@gmail.com Reporter: igor.mironc...@gmail.com Target Milestone: --- SUMMARY I'd like to have a UI to make attachment (any file, like *.pdf, *.txt) in note. This UI should copy selected file into note's directory, so I should be able to make a link in Markdown to it like [](file.pdf). Clicking this link in HTML preview should open the file with a default application. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDE neon 6.0 (available in About System) KDE Plasma Version: 6.1.1 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.0 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 375778] Jump to gtest failures
https://bugs.kde.org/show_bug.cgi?id=375778 Igor Kushnir changed: What|Removed |Added CC||igor...@gmail.com Latest Commit||https://commits.kde.org/kde ||velop/a4e56fbe5682fb5040245 ||38e03d809534b2191b8 Version Fixed In||5.15.240800 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 455533] Kdevelop crashes upon exit
https://bugs.kde.org/show_bug.cgi?id=455533 Igor Kushnir changed: What|Removed |Added CC||lassi.vaatamoi...@gmail.com --- Comment #21 from Igor Kushnir --- *** Bug 489290 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 489290] Kdevelop crashes after openining project configuration and closing main window.
https://bugs.kde.org/show_bug.cgi?id=489290 Igor Kushnir changed: What|Removed |Added CC||igor...@gmail.com Status|CONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #4 from Igor Kushnir --- *** This bug has been marked as a duplicate of bug 455533 *** -- You are receiving this mail because: You are watching all bug changes.
[kdevplatform] [Bug 482001] SEGFAULT in DeclarationId::declaration() after squashing many commits
https://bugs.kde.org/show_bug.cgi?id=482001 Igor Kushnir changed: What|Removed |Added Status|ASSIGNED|RESOLVED Version Fixed In||5.15.240800 Resolution|--- |FIXED Latest Commit||https://invent.kde.org/kdev ||elop/kdevelop/-/commit/0587 ||8f92e82424df23a4e6e3c6a2988 ||3fbbedf4b --- Comment #2 from Igor Kushnir --- Git commit 05878f92e82424df23a4e6e3c6a29883fbbedf4b by Igor Kushnir. Committed on 23/06/2024 at 09:02. Pushed by igorkushnir into branch 'master'. Remove useless [Indexed]QualifiedIdentifier conversions DeclarationId::declaration[s]() construct a QualifiedIdentifier from an IndexedQualifiedIdentifier and pass it to one of two functions. Each of the two functions takes a `const IndexedQualifiedIdentifier& id` parameter and assigns the `id` argument to a local variable before doing anything else. Eliminate the redundant explicit conversion from IndexedQualifiedIdentifier to QualifiedIdentifier and implicit conversion back. The only way this optimization can break something is if the local variable `QualifiedIdentifier id` keeps the IndexedQualifiedIdentifier valid somehow. But I do not think this is the case. For some reason, KDevelop segfaulted during the implicit conversion back from QualifiedIdentifier to IndexedQualifiedIdentifier in DeclarationId::declaration() as described in Bug 482001. Hopefully this optimization will eliminate the crash, or at least move elsewhere, facilitate understanding and fixing it. FIXED-IN: 5.15.240800 M +2-2kdevplatform/language/duchain/declarationid.cpp https://invent.kde.org/kdevelop/kdevelop/-/commit/05878f92e82424df23a4e6e3c6a29883fbbedf4b -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 488164] In split view cursor jumps to unexpected position
https://bugs.kde.org/show_bug.cgi?id=488164 --- Comment #6 from Igor Kushnir --- (In reply to Christoph Cullmann from comment #5) > Hmm, doesn't the view just resize because the replace panel is shown? Both cursor and view can jump halfway through a long document, so it's not merely a matter of several-line-long position change. This bug is very easy to reproduce. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 488445] Wrong total space of disk in system monitor
https://bugs.kde.org/show_bug.cgi?id=488445 --- Comment #1 from Igor Mironchik --- Created attachment 170459 --> https://bugs.kde.org/attachment.cgi?id=170459&action=edit Actual data -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 488445] New: Wrong total space of disk in system monitor
https://bugs.kde.org/show_bug.cgi?id=488445 Bug ID: 488445 Summary: Wrong total space of disk in system monitor Classification: I don't know Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: igor.mironc...@gmail.com Target Milestone: --- Created attachment 170458 --> https://bugs.kde.org/attachment.cgi?id=170458&action=edit Shown info *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY Wrong total space of disk in system monitor. See attached screenshots. STEPS TO REPRODUCE 1. Open System Monitor on HP Pro Book with NVME disk 2. 3. OBSERVED RESULT Total space is shown more 700 GB, whereas I have only 500 GB. EXPECTED RESULT I'd like to see actual information. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDE neon 6.0 (available in About System) KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 488164] In split view cursor jumps to unexpected position
https://bugs.kde.org/show_bug.cgi?id=488164 Igor Kushnir changed: What|Removed |Added Assignee|kdevelop-bugs-n...@kde.org |kwrite-bugs-n...@kde.org Component|UI: general |general Ever confirmed|0 |1 Version|5.14.240500 |6.2.0 Product|kdevelop|frameworks-ktexteditor Status|NEEDSINFO |CONFIRMED Resolution|WAITINGFORINFO |--- --- Comment #3 from Igor Kushnir --- Reproduced. The document can be at any scroll position. But have to click close to the bottom of the KTextEditor view - at a position that becomes obscured by the Find/Replace tool when the tool appears. The cursor always jumps and the view is scrolled to the very last line of the document. Exactly the same bug is present in Kate 24.05.0, so the bug is likely in KTextEditor. Reassigning. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 488164] In split view cursor jumps to unexpected position
https://bugs.kde.org/show_bug.cgi?id=488164 Igor Kushnir changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO CC||igor...@gmail.com --- Comment #1 from Igor Kushnir --- Cannot reproduce. Where do you click? -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 488165] Find/Replace in File "New Search" does not update Replacement Text in tool dock
https://bugs.kde.org/show_bug.cgi?id=488165 Igor Kushnir changed: What|Removed |Added CC||igor...@gmail.com Status|REPORTED|RESOLVED Resolution|--- |INTENTIONAL --- Comment #1 from Igor Kushnir --- The Replacement template is not the same as the Replacement text. You can specify both. %s in the Replacement template is replaced with the Replacement text. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 431289] KDevelop crashes when creating Project from existing sources.
https://bugs.kde.org/show_bug.cgi?id=431289
Igor Kushnir changed:
What|Removed |Added
Ever confirmed|0 |1
CC||igor...@gmail.com
Status|REPORTED|CONFIRMED
--- Comment #3 from Igor Kushnir ---
I can reliably reproduce a crash with the same backtrace in KDevelop master
(Qt5-based) by selecting Solution 1 - Open Project, then pressing Cancel in the
Open Project dialog that appears:
Application: KDevelop (kdevelop), signal: Segmentation fault
Thread 1 (Thread 0x7f9435f63000 (LWP 285943)):
[KCrash Handler]
#4 0x7f9456081c2b in std::__atomic_base::operator++
(this=0x6d002f00650072) at /usr/include/c++/14.1.1/bits/atomic_base.h:398
#5 0x7f94560803ab in QAtomicOps::ref (_q_value=) at
/usr/include/qt/QtCore/qatomic_cxx11.h:283
#6 0x7f945607f342 in QBasicAtomicInteger::ref (this=0x6d002f00650072)
at /usr/include/qt/QtCore/qbasicatomic.h:118
#7 0x7f94560da069 in
QExplicitlySharedDataPointer::QExplicitlySharedDataPointer
(this=0x70037ae0, o=...) at /usr/include/qt/QtCore/qshareddata.h:187
#8 0x7f94560eb91b in
KDevelop::DUChainPointer::DUChainPointer
(this=0x70037ae0) at
kdevelop/kdevplatform/language/duchain/navigation/../duchainpointer.h:88
#9 0x7f945620b85f in KDevelop::AbstractNavigationContext::topContext
(this=0x559cd0d341c0) at
kdevelop/kdevplatform/language/duchain/navigation/abstractnavigationcontext.cpp:61
#10 0x7f94562048ff in KDevelop::ProblemNavigationContext::executeAction
(this=0x559cd0d341c0, index=0) at
kdevelop/kdevplatform/language/duchain/navigation/problemnavigationcontext.cpp:247
#11 0x7f94562047f4 in KDevelop::ProblemNavigationContext::executeKeyAction
(this=0x559cd0d341c0, key=...) at
kdevelop/kdevplatform/language/duchain/navigation/problemnavigationcontext.cpp:231
#12 0x7f945620c2a6 in KDevelop::AbstractNavigationContext::execute
(this=0x559cd0d341c0, action=...) at
kdevelop/kdevplatform/language/duchain/navigation/abstractnavigationcontext.cpp:170
#13 0x7f945620d883 in KDevelop::AbstractNavigationContext::acceptLink
(this=0x559cd0d341c0, link=...) at
kdevelop/kdevplatform/language/duchain/navigation/abstractnavigationcontext.cpp:485
#14 0x7f9456209ae3 in
KDevelop::AbstractNavigationWidgetPrivate::anchorClicked (this=0x559cce73a2b0,
url=...) at
kdevelop/kdevplatform/language/duchain/navigation/abstractnavigationwidget.cpp:265
#15 0x7f9456208b0e in operator() (__closure=0x559cd0d2e3d0, url=...) at
kdevelop/kdevplatform/language/duchain/navigation/abstractnavigationwidget.cpp:101
#16 0x7f945620a8cd in QtPrivate::FunctorCall,
QtPrivate::List, void,
KDevelop::AbstractNavigationWidget::initBrowser(int)::
>::call(struct {...} &, void **) (f=..., arg=0x70037f80) at
/usr/include/qt/QtCore/qobjectdefs_impl.h:146
#17 0x7f945620a891 in
QtPrivate::Functor, 1>::call, void>(struct {...} &, void *,
void **) (f=..., arg=0x70037f80) at
/usr/include/qt/QtCore/qobjectdefs_impl.h:256
#18 0x7f945620a860 in
QtPrivate::QFunctorSlotObject, 1, QtPrivate::List, void>::impl(int,
QtPrivate::QSlotObjectBase *, QObject *, void **, bool *) (which=1,
this_=0x559cd0d2e3c0, r=0x559cd0d23200, a=0x70037f80, ret=0x0) at
/usr/include/qt/QtCore/qobjectdefs_impl.h:443
#19 0x7f94530df99e in ??? () at /usr/lib/libQt5Core.so.5
#20 0x7f945413190d in QTextBrowser::anchorClicked(QUrl const&) () at
/usr/lib/libQt5Widgets.so.5
#21 0x7f94541362d4 in ??? () at /usr/lib/libQt5Widgets.so.5
#22 0x7f94530df962 in ??? () at /usr/lib/libQt5Core.so.5
#23 0x7f945415564d in QWidgetTextControl::linkActivated(QString const&) ()
at /usr/lib/libQt5Widgets.so.5
#24 0x7f945415706d in ??? () at /usr/lib/libQt5Widgets.so.5
#25 0x7f945414dda8 in ??? () at /usr/lib/libQt5Widgets.so.5
#26 0x7f94541527aa in QWidgetTextControl::processEvent(QEvent*, QTransform
const&, QWidget*) () at /usr/lib/libQt5Widgets.so.5
#27 0x7f9454145919 in QWidgetTextControl::processEvent(QEvent*, QPointF
const&, QWidget*) () at /usr/lib/libQt5Widgets.so.5
#28 0x7f945412e314 in QTextEdit::mouseReleaseEvent(QMouseEvent*) () at
/usr/lib/libQt5Widgets.so.5
#29 0x7f9453f8f7c6 in QWidget::event(QEvent*) () at
/usr/lib/libQt5Widgets.so.5
#30 0x7f945403af88 in QFrame::event(QEvent*) () at
/usr/lib/libQt5Widgets.so.5
#31 0x7f94530aae02 in
QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () at
/usr/lib/libQt5Core.so.5
#32 0x7f9453f56321 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib/libQt5Widgets.so.5
#33 0x7f9453f5c0d1 in QApplication::notify(QObject*, QEvent*) () at
/usr/lib/libQt5Widgets.so.5
#34 0x7f94530ab968 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /usr/lib/libQt5Core.so.5
#35 0x7f9453f59df5 in QApplic
[kdevelop] [Bug 488069] Reproducible crash in libclang after ::Visitor::setTypeSize
https://bugs.kde.org/show_bug.cgi?id=488069 Igor Kushnir changed: What|Removed |Added CC||igor...@gmail.com --- Comment #3 from Igor Kushnir --- The posted backtrace is incomplete (only 10 last stack frames). The only backtrace containing Visitor::setTypeSize on my disk is the one discussed in https://invent.kde.org/kdevelop/kdevelop/-/merge_requests/210#note_156543 - this crash has been fixed before the merge request was merged. But maybe you hit another edge case. Or this could be a regression in Clang 18. The only reported bug containing Visitor::setTypeSize is Bug 451856. Could be related. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 488043] KDevelop crashed when loading a KDevGenericManager project
https://bugs.kde.org/show_bug.cgi?id=488043 --- Comment #4 from Igor Kushnir --- (In reply to Davide Beatrici from comment #3) > Just checked: no updates to the Clang packages and it was the first time I > opened the project after a fresh system reinstall (I didn't transfer > ~/.cache over). Then it's probably a bug in CodeModel or ItemRepository somewhere. The backtrace looks good and may be used to find and fix a bug. If only someone had the time for that... -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 488043] KDevelop crashed when loading a KDevGenericManager project
https://bugs.kde.org/show_bug.cgi?id=488043 Igor Kushnir changed: What|Removed |Added CC||igor...@gmail.com --- Comment #2 from Igor Kushnir --- (In reply to Davide Beatrici from comment #0) > The crash happened almost immediately. Upon restarting the program, I chose > to delete the cache and then I opened the project again, which was loaded > just fine. Did you update Clang just before the crash occurred? Perhaps the cache is incompatible between [major] libclang versions. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 486932] Background parser crash C++ source
https://bugs.kde.org/show_bug.cgi?id=486932
--- Comment #9 from Igor Kushnir ---
Got another crash while completing an include. This time the first thread
crashed and its backtrace matches the more common one in this and duplicate bug
reports:
#0 0x7f87588ac194 in ??? () at /usr/lib/libc.so.6
#1 0x7f8758858d70 in raise () at /usr/lib/libc.so.6
#2 0x7f875aaef88f in KCrash::defaultCrashHandler(int) () at
/usr/lib/libKF5Crash.so.5
#3 0x7f8758858e20 in () at /usr/lib/libc.so.6
#4 clang::ASTReader::ReadSLocEntry () at
/usr/src/debug/clang/clang-17.0.6.src/lib/Serialization/ASTReader.cpp:1497
#5 0x7f86d1623356 in clang::ASTReader::ReadSLocEntry () at
/usr/src/debug/clang/clang-17.0.6.src/lib/Serialization/ASTReader.cpp:1436
#6 clang::SourceManager::loadSLocEntry () at
/usr/src/debug/clang/clang-17.0.6.src/lib/Basic/SourceManager.cpp:435
#7 0x7f86d1251c31 in clang::SourceManager::getLoadedSLocEntry () at
/usr/src/debug/clang/clang-17.0.6.src/include/clang/Basic/SourceManager.h:1718
#8 clang::SourceManager::getLoadedSLocEntryByID () at
/usr/src/debug/clang/clang-17.0.6.src/include/clang/Basic/SourceManager.h:1822
#9 clang::SourceManager::getSLocEntryByID () at
/usr/src/debug/clang/clang-17.0.6.src/include/clang/Basic/SourceManager.h:1816
#10 clang::SourceManager::isOffsetInFileID () at
/usr/src/debug/clang/clang-17.0.6.src/include/clang/Basic/SourceManager.h:1866
#11 0x7f86d1623eec in clang::SourceManager::getFileIDLoaded () at
/usr/src/debug/clang/clang-17.0.6.src/lib/Basic/SourceManager.cpp:922
#12 clang::SourceManager::getFileIDLoaded () at
/usr/src/debug/clang/clang-17.0.6.src/lib/Basic/SourceManager.cpp:866
#13 clang::SourceManager::getFileIDSlow () at
/usr/src/debug/clang/clang-17.0.6.src/lib/Basic/SourceManager.cpp:779
#14 clang::SourceManager::getFileIDSlow () at
/usr/src/debug/clang/clang-17.0.6.src/lib/Basic/SourceManager.cpp:771
#15 0x7f86d1251e6b in clang::SourceManager::getFileID () at
/usr/src/debug/clang/clang-17.0.6.src/include/clang/Basic/SourceManager.h:1830
#16 clang::SourceManager::getFileID () at
/usr/src/debug/clang/clang-17.0.6.src/include/clang/Basic/SourceManager.h:1119
#17 clang::SourceManager::getDecomposedExpansionLoc () at
/usr/src/debug/clang/clang-17.0.6.src/include/clang/Basic/SourceManager.h:1259
#18 0x7f86d1625b94 in clang::SourceManager::getFileCharacteristic () at
/usr/src/debug/clang/clang-17.0.6.src/lib/Basic/SourceManager.cpp:1477
#19 0x7f86d12af2ac in clang::SourceManager::isInSystemHeader () at
/usr/src/debug/clang/clang-17.0.6.src/include/clang/Basic/SourceManager.h:1509
#20 clang_Location_isInSystemHeader () at
/usr/src/debug/clang/clang-17.0.6.src/tools/libclang/CXSourceLocation.cpp:209
#21 0x7f86d2e2a6e4 in (anonymous namespace)::declVisitor (cursor=...,
parent=..., d=0x7f86d11fded0) at
/home/Mint14_home/igor/Install/abs/kdevelop-git/src/kdevelop/plugins/clang/codecompletion/completionhelper.cpp:224
#22 0x7f86d126c65e in clang::cxcursor::CursorVisitor::Visit () at
/usr/src/debug/clang/clang-17.0.6.src/tools/libclang/CIndex.cpp:224
#23 0x7f86d126df56 in
clang::cxcursor::CursorVisitor::handleDeclForVisitation () at
/usr/src/debug/clang/clang-17.0.6.src/tools/libclang/CIndex.cpp:686
#24 0x7f86d126e208 in clang::cxcursor::CursorVisitor::VisitDeclContext ()
at /usr/src/debug/clang/clang-17.0.6.src/tools/libclang/CIndex.cpp:647
#25 0x7f86d126b9be in clang::cxcursor::CursorVisitor::VisitChildren () at
/usr/src/debug/clang/clang-17.0.6.src/tools/libclang/CIndex.cpp:547
#26 0x7f86d126eba0 in clang_visitChildren () at
/usr/src/debug/clang/clang-17.0.6.src/tools/libclang/CIndex.cpp:4842
#27 0x7f86d2e2e023 in CompletionHelper::computeCompletions
(position=, file=, session=..., this=) at
/home/Mint14_home/igor/Install/abs/kdevelop-git/src/kdevelop/plugins/clang/codecompletion/completionhelper.cpp:394
#28 ClangCodeCompletionContext::ClangCodeCompletionContext (this=, context=, sessionData=, url=, position=, text=, followingText=, this=, context=, sessionData=, url=, position=, text=,
followingText=) at
/home/Mint14_home/igor/Install/abs/kdevelop-git/src/kdevelop/plugins/clang/codecompletion/context.cpp:1072
#29 0x7f86d2e3b160 in
QSharedPointer::create
const&, QExplicitlySharedDataPointer const&, QUrl const&,
KTextEditor::Cursor const&, QString const&, QString const&> () at
/usr/include/qt/QtCore/qsharedpointer_impl.h:444
#30 (anonymous namespace)::createCompletionContext
(followingText="inc\n#include \n\nnamespace KDevelop\n{\nQDebug
operator<<(QDebug debug, const StatusBar::Message& s)\n{\n const
QDebugStateSaver saver(debug);\n debug.nospace() << '{' << s.text << \", \" <<
s.t"..., text=, position=, url=,
session=..., context=...) at
/home/Mint14_home/igor/Install/abs/kdevelop-git/src/kdevelop/plugins/clang/codecompletion/model.cpp:48
#31 (anonymous namespace)::ClangCodeCompletionWorker::run (this=0x562b9620f040)
a
[kdevelop] [Bug 487378] Crash when adding #include statement
https://bugs.kde.org/show_bug.cgi?id=487378 --- Comment #5 from Igor Kushnir --- Please reply under the original bug, not its duplicates. The reporters of duplicate bugs are automatically subscribed to the original bug. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 487674] Kdevelop crashes during input of lines like "using namespace ..." and "#include <..."
https://bugs.kde.org/show_bug.cgi?id=487674 Igor Kushnir changed: What|Removed |Added CC||igor...@gmail.com Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Igor Kushnir --- *** This bug has been marked as a duplicate of bug 486932 *** -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 486932] Background parser crash C++ source
https://bugs.kde.org/show_bug.cgi?id=486932 Igor Kushnir changed: What|Removed |Added CC||ad...@arkades.org --- Comment #8 from Igor Kushnir --- *** Bug 487674 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 486932] Background parser crash C++ source
https://bugs.kde.org/show_bug.cgi?id=486932 Igor Kushnir changed: What|Removed |Added See Also|https://bugs.kde.org/show_b | |ug.cgi?id=487378| -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 487378] Crash when adding #include statement
https://bugs.kde.org/show_bug.cgi?id=487378 Igor Kushnir changed: What|Removed |Added See Also|https://bugs.kde.org/show_b | |ug.cgi?id=486932| -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 486932] Background parser crash C++ source
https://bugs.kde.org/show_bug.cgi?id=486932 Igor Kushnir changed: What|Removed |Added CC||spalmr...@gmail.com --- Comment #7 from Igor Kushnir --- *** Bug 487378 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 487378] Crash when adding #include statement
https://bugs.kde.org/show_bug.cgi?id=487378 Igor Kushnir changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #2 from Igor Kushnir --- (In reply to Igor Kushnir from comment #1) > Steps to reproduce this crash are very similar to those of Bug 486932. The > backtrace is different. But both bugs affect Clang 17 and probably not > earlier Clang versions. Actually the backtrace matches the backtrace in the description of Bug 486932 plus debug symbols, but not the backtrace I posted in a comment there. So this *is* a duplicate. *** This bug has been marked as a duplicate of bug 486932 *** -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 486656] Selecting text in the navigation widget demolishes clipboard history
https://bugs.kde.org/show_bug.cgi?id=486656 Igor Kushnir changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/kdev ||elop/kdevelop/-/commit/134f ||d24d0ec5f983d9da65dfe27dcab ||1801c3f81 Version Fixed In||5.15.240800 Status|ASSIGNED|RESOLVED --- Comment #11 from Igor Kushnir --- Git commit 134fd24d0ec5f983d9da65dfe27dcab1801c3f81 by Igor Kushnir. Committed on 22/05/2024 at 10:01. Pushed by igorkushnir into branch 'master'. Revert "Add copy button in AbstractNavigationWidget" When text is selected in a navigation widget (e.g. editor tooltip, Code Browser tool view, Quick Open or Outline item details), KDevelop automatically copies the selection to clipboard. The copying occurs continuously while the user selects text, so clipboard history ends up containing not only the final selection, but also all intermediate selections - all but one character, all but two characters, ..., the first selected character. This behavior not only clutters clipboard history with useless entries, but can also quickly overwrite useful clipboard entries if the clipboard manager limits its history size. The auto-copy feature is unexpected and undocumented. It is also redundant on most GNU/Linux and *BSD systems, because primary selection works naturally and automatically in X11 and in most modern Wayland compositors: https://wayland.app/protocols/primary-selection-unstable-v1 If someone needs to copy text from a navigation widget on other operating systems, the feature can be reintroduced but in the widget's context menu, where it would be discoverable and would not clutter clipboard history. This reverts commit dadaf13191e50cc99c3420f274f5e857f3050f06. FIXED-IN: 5.15.240800 M +0-4 kdevplatform/language/duchain/navigation/abstractnavigationwidget.cpp https://invent.kde.org/kdevelop/kdevelop/-/commit/134fd24d0ec5f983d9da65dfe27dcab1801c3f81 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 486932] Background parser crash C++ source
https://bugs.kde.org/show_bug.cgi?id=486932 Igor Kushnir changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=487378 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 487378] Crash when adding #include statement
https://bugs.kde.org/show_bug.cgi?id=487378 Igor Kushnir changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=486932 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 487378] Crash when adding #include statement
https://bugs.kde.org/show_bug.cgi?id=487378 Igor Kushnir changed: What|Removed |Added CC||igor...@gmail.com --- Comment #1 from Igor Kushnir --- Steps to reproduce this crash are very similar to those of Bug 486932. The backtrace is different. But both bugs affect Clang 17 and probably not earlier Clang versions. I suggest trying to search for includes/headers, crashes and parts of the backtraces at https://github.com/llvm/llvm-project/ . It is likely that someone has already fixed the bug in the main LLVM branch. Then the fix can be backported to Clang 17 by distros. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 487381] There are no almost all icons.
https://bugs.kde.org/show_bug.cgi?id=487381 --- Comment #3 from Igor Mironchik --- On login screen the same problem... -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 487381] There are no almost all icons.
https://bugs.kde.org/show_bug.cgi?id=487381 Igor Mironchik changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #2 from Igor Mironchik --- No, this is the default Breeze Twilight theme with default icons. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 487381] New: There are no almost all icons.
https://bugs.kde.org/show_bug.cgi?id=487381 Bug ID: 487381 Summary: There are no almost all icons. Classification: I don't know Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: igor.mironc...@gmail.com Target Milestone: --- Created attachment 169710 --> https://bugs.kde.org/attachment.cgi?id=169710&action=edit The problem SUMMARY There are no almost all icons. STEPS TO REPRODUCE 1. Update to Plasma 6.0.4 2. 3. OBSERVED RESULT See screenshot. EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDE neon 6.0 (available in About System) KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 486932] Background parser crash C++ source
https://bugs.kde.org/show_bug.cgi?id=486932 --- Comment #6 from Igor Kushnir --- My previous comment missed preliminary coredumpctl steps: 0.1. coredumpctl list kdevelop --since 2024-05-19. 0.2. Locate the necessary entry in the printed table and show its details via `coredumpctl info 151255` (where 151255 is the PID of the entry). 0.3. Find the Storage line in the info output, e.g. "Storage: /var/lib/systemd/coredump/core.kdevelop.1000.df23a15637fe47fbae399826251ac233.151255.171613318900.zst (present)" and extract the .zst archive to obtain the actual debuggable core dump file. Oh, and after these steps KDevelop's Frame Stack tool view also shows the backtrace with debug symbols. libclang headers can be opened and examined from the IDE right away. To examine libclang source files as well: 8. Download clang sources. I got the clang repository already, so just `git fetch origin` and `git checkout llvmorg-17.0.6` to match my system clang package version. 9. In the GDB tool view: set substitute-path /usr/src/debug/clang/clang-17.0.6.src /path/to/llvm-project/clang 10. Activate the Frame Stack tool view and switch to another thread, then back, to open libclang source files by clicking their lines in the backtrace. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 486932] Background parser crash C++ source
https://bugs.kde.org/show_bug.cgi?id=486932
--- Comment #5 from Igor Kushnir ---
(In reply to Igor Kushnir from comment #4)
> The crash just happened once to me. But I cannot reproduce it. Here is a
> more detailed backtrace (still no libclang debug symbols):
Managed to obtain a complete backtrace for the single crash that happened on my
system. Here are the steps in case I or someone else needs them in the future
(they can also be used to examine past core dumps with freshly downloaded
KDevelop debug symbols).
1. Download debuginfod debug symbols for libclang:
$ debuginfod-find debuginfo /usr/lib/libclang.so.17
/home/igor/.cache/debuginfod_client/02120dc8526595aac7ab8bc78eca4efc936b09be/debuginfo
2. Trigger the "Run=>Examine Core File=>Examine Core File with GDB" action in
KDevelop, select /bin/kdevelop and the crash coredump in the dialog that
appears.
3. Activate KDevelop's GDB tool view. All commands in the following steps are
entered into the GDB command line edit inside this tool view.
4. At this point the command `thread apply 15 bt` still shows a backtrace
without libclang debug symbols. Read and follow the top answer here:
https://stackoverflow.com/questions/30281766/need-to-load-debugging-symbols-for-shared-library-in-gdb
5. (gdb) 48info sharedlibrary
>From To Syms Read Shared Object Library
...
0x7f4d26433020 0x7f4d277c3c54 Yes /usr/lib/libclang.so.17
...
6. (gdb) 49add-symbol-file
/home/igor/.cache/debuginfod_client/02120dc8526595aac7ab8bc78eca4efc936b09be/debuginfo
0x7f4d26433020
add symbol table from file
"/home/igor/.cache/debuginfod_client/02120dc8526595aac7ab8bc78eca4efc936b09be/debuginfo"
at
.text_addr = 0x7f4d26433020
(y or n) [answered Y; input not from terminal]
Reading symbols from
/home/igor/.cache/debuginfod_client/02120dc8526595aac7ab8bc78eca4efc936b09be/debuginfo...
7. (gdb) 50thread apply 15 bt
Thread 15 (Thread 0x7f4d393616c0 (LWP 151298)):
#0 0x7f4db111d9ed in poll () at /usr/lib/libc.so.6
#1 0x7f4db31c6bca in ??? () at /usr/lib/libKF5Crash.so.5
#2 0x7f4db31c782c in KCrash::defaultCrashHandler(int) () at
/usr/lib/libKF5Crash.so.5
#3 0x7f4db1058e20 in () at /usr/lib/libc.so.6
#4 memcpy () at /usr/include/bits/string_fortified.h:29
#5 llvm::support::endian::read () at
/usr/include/llvm/Support/Endian.h:66
#6 llvm::support::endian::readNext () at
/usr/include/llvm/Support/Endian.h:84
#7 llvm::support::endian::readNext () at /usr/include/llvm/Support/Endian.h:92
#8
llvm::OnDiskChainedHashTable::find_hashed
() at /usr/include/llvm/Support/OnDiskHashTable.h:360
#9 operator() () at
/usr/src/debug/clang/clang-17.0.6.src/lib/Serialization/ASTReader.cpp:2103
#10 clang::ASTReader::get () at
/usr/src/debug/clang/clang-17.0.6.src/lib/Serialization/ASTReader.cpp:8174
#11 0x7f4d2644f6f7 in clang::IdentifierTable::get () at
/usr/src/debug/clang/clang-17.0.6.src/include/clang/Basic/IdentifierTable.h:647
#12 0x7f4d26af5423 in clang::Preprocessor::getIdentifierInfo () at
/usr/src/debug/clang/clang-17.0.6.src/include/clang/Lex/Preprocessor.h:1516
#13 clang::Preprocessor::LookUpIdentifierInfo () at
/usr/src/debug/clang/clang-17.0.6.src/lib/Lex/Preprocessor.cpp:715
#14 0x7f4d275eb473 in getTokens(clang::ASTUnit*, clang::SourceRange,
llvm::SmallVectorImpl&) [clone .constprop.0] () at
/usr/src/debug/clang/clang-17.0.6.src/tools/libclang/CIndex.cpp:7248
#15 0x7f4d264618f0 in clang_tokenize () at
/usr/src/debug/clang/clang-17.0.6.src/tools/libclang/CIndex.cpp:7330
#16 0x7f4d39396df8 in (anonymous namespace)::isInsideComment
(position=, file=0x13, unit=0x7f4d113e1eb0) at
/home/Mint14_home/igor/Install/abs/kdevelop-git/src/kdevelop/plugins/clang/codecompletion/context.cpp:490
#17 ClangCodeCompletionContext::isValidPosition
(this=this@entry=0x7f4d20001fc0, unit=0x7f4d113e1eb0,
file=file@entry=0x7f4c719a0520) at
/home/Mint14_home/igor/Install/abs/kdevelop-git/src/kdevelop/plugins/clang/codecompletion/context.cpp:1081
#18 0x7f4d39397b16 in
ClangCodeCompletionContext::ClangCodeCompletionContext (this=0x7f4d20001fc0,
context=, sessionData=, url=,
position=, text=, followingText=,
this=, context=, sessionData=,
url=, position=, text=,
followingText=) at
/home/Mint14_home/igor/Install/abs/kdevelop-git/src/kdevelop/plugins/clang/codecompletion/context.cpp:1067
#19 0x7f4d393a5160 in
QSharedPointer::create
const&, QExplicitlySharedDataPointer const&, QUrl const&,
KTextEditor::Cursor const&, QString const&, QString const&> () at
/usr/include/qt/QtCore/qsharedpointer_impl.h:444
#20 (anonymous namespace)::createCompletionContext (followingText="i\n#include
\"ui_qthelpconfig.h\"\n#include \"ui_qthelpconfigeditdialog.h\"\n#include
\"qthelp_config_shared.h\"\n#include \"debug.h\"\n#include
\"qthelpplugin.h\"\n\nenum Column\n{\n NameColumn,\n PathColumn,\n "...,
text=, position=, url=,
session=..., context=...)
[kdevelop] [Bug 486967] Remember order of closed document tabs/views
https://bugs.kde.org/show_bug.cgi?id=486967 --- Comment #3 from Igor Kushnir --- (In reply to JATothrim from comment #2) > Thus, I keep only 6 or so documents > manually arranged, and when KDevelop decides to insert new tabs in between > those, it becomes annoying. Then maybe you should make use of working sets (the button in the top right corner, near the area switch button). First Stash those 6 documents in a working set. Then Add All to reopen them. At this point you'll have a current working set and an identical backup working set. After you open many unwanted documents, just Close All documents and Add All from the backup working set. You can also back up [Working File Sets] config entries from sessionrc and restore them manually. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 486689] File creation and saving File Dialog not coherent with current project context
https://bugs.kde.org/show_bug.cgi?id=486689 Igor Kushnir changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 CC||igor...@gmail.com --- Comment #1 from Igor Kushnir --- Kate does something similar to what you request: it uses the directory of the last active tab though (not the previous in the visible tab order). KDevelop ends up using the directory of some unspecified tab (possibly first in tab order). Here is why: 1. KTextEditor::DocumentPrivate::getSaveFileUrl() delegates the ordering to KTextEditor::Editor::instance()->application()->activeMainWindow()->views() [we will try to get the url of the last used view, we assume some properly ordered views() list is around]. 2. Kate returns KateMainWindow::views(), which delegates to KateViewManager::views() [@return all views sorted by their last use, most recently used first]. 3. KDevelop returns KTextEditorIntegration::MainWindow::views(), which delegates to Sublime::Area::views() [@return the list of all views in this area in no particular order]. KDevelop's Most-Recently-Used Document Switcher plugin (Ctrl+Tab) maintains the list of documents sorted by their last use. So KDevelop could do the same as Kate. Might be difficult to implement properly though, because the list is in the plugin, not KDevPlatform. Maybe your proposed tab ordering would be easier to implement. Note: I don't expect anyone to implement this feature any time soon, unless you scratch your own itch. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 486967] Remember order of closed document tabs/views
https://bugs.kde.org/show_bug.cgi?id=486967 Igor Kushnir changed: What|Removed |Added CC||igor...@gmail.com See Also||https://bugs.kde.org/show_b ||ug.cgi?id=400168 --- Comment #1 from Igor Kushnir --- Managing tab order is difficult and time-consuming. Do you manually arange tabs in your preferred order? My tabs usually end up in quite a mess of an order, because I tend to go on document-opening spree by Ctrl+clicking identifiers often. Then I have to close all files from time to time to prevent severe IDE slowdown. I generally use Quick Open or Ctrl+Tab rather than the tab bar to switch between documents faster. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 400168] Recheck tab repositioning for open files
https://bugs.kde.org/show_bug.cgi?id=400168 Igor Kushnir changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=486967 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 372209] Feature request: full path in tab names & auto locate current file in project view
https://bugs.kde.org/show_bug.cgi?id=372209 Igor Kushnir changed: What|Removed |Added CC||igor...@gmail.com --- Comment #7 from Igor Kushnir --- > Adding confusion that the open file is not automatically located in the > project view, > would be interesting the same behavior as the documents tool view. An auto-sync option exists for several years now and is on by default. The option can be accessed by mouse-clicking and holding the leftmost action on the Project tool view's toolbar. A short click on the leftmost action synchronizes to the currently active tab once (on demand), as before. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 411585] KDevelop always segfaults when indexing my project
https://bugs.kde.org/show_bug.cgi?id=411585 Igor Kushnir changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED CC||igor...@gmail.com --- Comment #2 from Igor Kushnir --- Backtrace removed => nothing to check anymore => closing. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 486949] Kdevelop freezes after git checkout feature-branch
https://bugs.kde.org/show_bug.cgi?id=486949 Igor Kushnir changed: What|Removed |Added CC||igor...@gmail.com --- Comment #1 from Igor Kushnir --- When this happens, run `gdb -batch -ex "bt" -ex "quit" -p 12345 > ~/path/to/frozen.bt`, where 12345 is the ID of the frozen KDevelop process. Wait a few seconds/minutes and run the command again (with a different output filename) to check if KDevelop is still stuck in the same place in code. Then attach the generated backtrace(s) to your bug report. Make sure to have KDevelop debug symbols installed (either build KDevelop manually with debug info and don't strip it or use debuginfod - https://wiki.archlinux.org/title/Debuginfod). -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 486061] Launch configuration arguments are not fully passed when executing (escaped)
https://bugs.kde.org/show_bug.cgi?id=486061 --- Comment #5 from Igor Kushnir --- Just tested: quoting works as well as escaping, so the issue is not too bad. Perhaps the UI should show an error message earlier - before the user attempts to actually run the program, because the problem is localized in the value of the Arguments line edit. The relevant code was implemented in 2009 by https://commits.kde.org/kdevelop/fd240820495a98ff30b61af3476e0e5bc6fcd606. The code currently resides in https://invent.kde.org/kdevelop/kdevelop/-/blob/c8417fc2baf2ecba70e7e2b474fa2d00b1970265/plugins/execute/executeplugin.cpp#L62. The job of splitting arguments is fully delegated to KShell::splitArgs(cmd, KShell::TildeExpand | KShell::AbortOnMeta, err). Its documentation: https://api.kde.org/frameworks/kcoreaddons/html/namespaceKShell.html#a2af8a3c7f2b485868a1169f4de07a050. The documentation for the AbortOnMeta flag suggests it is the culprit, and indeed removing the flag makes unquoted and unescaped square brackets work. I don't know whether removing this flag is going to break something else though. Needs a more detailed analysis and careful testing. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 486656] Selecting text in the navigation widget demolishes clipboard history
https://bugs.kde.org/show_bug.cgi?id=486656 --- Comment #10 from Igor Kushnir --- (In reply to Igor Kushnir from comment #8) > Should we rush the feature removal into the upcoming release > https://community.kde.org/Schedules/KDE_Gear_24.05_Schedule or do it in > master and release in August > https://community.kde.org/Schedules/KDE_Gear_24.08_Schedule ? Too late for the 24.05 release now. Created a merge request based on master. Please review. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 487255] Kdevelop memory usage exceeds
https://bugs.kde.org/show_bug.cgi?id=487255 Igor Kushnir changed: What|Removed |Added Status|REPORTED|RESOLVED CC||igor...@gmail.com Resolution|--- |DUPLICATE --- Comment #1 from Igor Kushnir --- *** This bug has been marked as a duplicate of bug 241032 *** -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 241032] Background parser uses up too much memory
https://bugs.kde.org/show_bug.cgi?id=241032 Igor Kushnir changed: What|Removed |Added CC||ad...@arkades.org --- Comment #9 from Igor Kushnir --- *** Bug 487255 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 486932] Background parser crash C++ source
https://bugs.kde.org/show_bug.cgi?id=486932 Igor Kushnir changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #4 from Igor Kushnir --- The crash just happened once to me. But I cannot reproduce it. Here is a more detailed backtrace (still no libclang debug symbols): [KCrash Handler] #4 0x7f4d271e2fdb in ??? () at /usr/lib/libclang.so.17 #5 0x7f4d2644f6f7 in ??? () at /usr/lib/libclang.so.17 #6 0x7f4d26af5423 in ??? () at /usr/lib/libclang.so.17 #7 0x7f4d275eb473 in ??? () at /usr/lib/libclang.so.17 #8 0x7f4d264618f0 in clang_tokenize () at /usr/lib/libclang.so.17 #9 0x7f4d39396df8 in (anonymous namespace)::isInsideComment (position=, file=0x13, unit=0x7f4d113e1eb0) at kdevelop/plugins/clang/codecompletion/context.cpp:490 #10 ClangCodeCompletionContext::isValidPosition (this=this@entry=0x7f4d20001fc0, unit=0x7f4d113e1eb0, file=file@entry=0x7f4c719a0520) at kdevelop/plugins/clang/codecompletion/context.cpp:1081 #11 0x7f4d39397b16 in ClangCodeCompletionContext::ClangCodeCompletionContext (this=0x7f4d20001fc0, context=, sessionData=, url=, position=, text=, followingText=, this=, context=, sessionData=, url=, position=, text=, followingText=) at kdevelop/plugins/clang/codecompletion/context.cpp:1067 #12 0x7f4d393a5160 in QSharedPointer::create const&, QExplicitlySharedDataPointer const&, QUrl const&, KTextEditor::Cursor const&, QString const&, QString const&> () at /usr/include/qt/QtCore/qsharedpointer_impl.h:444 #13 (anonymous namespace)::createCompletionContext (followingText=..., text=, position=, url=, session=..., context=...) at kdevelop/plugins/clang/codecompletion/model.cpp:48 #14 (anonymous namespace)::ClangCodeCompletionWorker::run (this=0x55817e19a390) at kdevelop/plugins/clang/codecompletion/model.cpp:115 #15 0x7f4db18c89a7 in ??? () at /usr/lib/libQt5Core.so.5 #16 0x7f4db18ca4df in QTimer::timeout(QTimer::QPrivateSignal) () at /usr/lib/libQt5Core.so.5 #17 0x7f4db18bb44e in QObject::event(QEvent*) () at /usr/lib/libQt5Core.so.5 #18 0x7f4db25578ff in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #19 0x7f4db1893a68 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #20 0x7f4db18e20db in QTimerInfoList::activateTimers() () at /usr/lib/libQt5Core.so.5 #21 0x7f4db18e26ca in ??? () at /usr/lib/libQt5Core.so.5 #22 0x7f4dad720199 in ??? () at /usr/lib/libglib-2.0.so.0 #23 0x7f4dad77f3bf in ??? () at /usr/lib/libglib-2.0.so.0 #24 0x7f4dad71f712 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #25 0x7f4db18e288c in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #26 0x7f4db1892774 in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #27 0x7f4db16ef666 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #28 0x7f4db16eb88a in ??? () at /usr/lib/libQt5Core.so.5 #29 0x7f4db10aa1cf in ??? () at /usr/lib/libc.so.6 #30 0x7f4db112b6ec in ??? () at /usr/lib/libc.so.6 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 486932] Background parser crash C++ source
https://bugs.kde.org/show_bug.cgi?id=486932 --- Comment #3 from Igor Kushnir --- (In reply to JATothrim from comment #2) > I think I'll rebuild just to re-produce the bt and try print the locals just > before descending into clang code. However, clang would be painful to build > in this mode.. last time I did it the install directory was +10GiB o__O Can't you just download Clang debug symbols from Arch's debuginfod? -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 486932] Background parser crash C++ source
https://bugs.kde.org/show_bug.cgi?id=486932 Igor Kushnir changed: What|Removed |Added CC||igor...@gmail.com --- Comment #1 from Igor Kushnir --- I don't find anything like this backtrace in my local collection. Could be a libclang 17 regression (I am still at v16). > I perhaps should prevent the stripping of the debug info out from my > production builds... :) Yes, please use `options=(!strip)` and `-DCMAKE_BUILD_TYPE=RelWithDebInfo`. Though I suspect the bug is in libclang, in which case libclang debug symbols will be needed. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 379669] KDevelop continues to hang on exit in itemrepository.h [Bucket::deleteItem]
https://bugs.kde.org/show_bug.cgi?id=379669
--- Comment #50 from Igor Kushnir ---
I rarely experience freeze on exit and even more rarely this particular freeze
(lately, once a year perhaps despite heavy KDevelop use). Yesterday I got the
currentIndex=0 freeze. Note the `followerIndex (index=0,` part in the following
call stack extract:
0x7fbfc51630dd in KDevelop::Bucket::followerIndex (index=0,
this=) at
/path/to/kdevelop/kdevplatform/serialization/itemrepository.h:1070
1070return *reinterpret_cast(m_data + (index -
2));
#0 0x7fbfc51630dd in KDevelop::Bucket::followerIndex (index=0,
this=) at
/path/to/kdevelop/kdevplatform/serialization/itemrepository.h:1070
#1 KDevelop::Bucket::deleteItem >
(repository=, hash=, index=44482,
this=0x7fbf0cbc5ad0) at
/path/to/kdevelop/kdevplatform/serialization/itemrepository.h:628
#2 KDevelop::Bucket::finalCleanup >
(repository=, this=) at
/path/to/kdevelop/kdevplatform/serialization/itemrepository.h:791
KDevelop occupied a CPU core by the infinite loop `while (currentIndex !=
index)` for half an hour, until I terminated the KDevelop process. I verified
this by comparing GDB call stacks generated with the half-hour interval: all
addresses and arguments are exactly the same, until the line
itemrepository.h:626 in one and itemrepository.h:628 in another call stack.
These two line numbers correspond to the source code lines `while (currentIndex
!= index) {` and `currentIndex = followerIndex(currentIndex);` (inside the
loop) respectively.
1.5 years ago I got this same freeze after a blackout and consequently a sudden
system shutdown in KDevelop::Bucket, that is, probably because of cache
corruption.
Yesterday I repeatedly removed and installed kdev-python, KDevelop parsing of a
.py file hanged and I was forced to restart KDevelop. The freeze in
KDevelop::Bucket occurred during the next exit of the same KDevelop session. So again
it is a consequence of either missing language plugin or a related cache
corruption.
I think that due to performance considerations cache corruption inevitably
leads to undefined behavior. If the undefined behavior often manifests in the
same freeze, then we can try to work it around. An acceptable workaround should
be able to at least sometimes solve the problem automatically, possibly by
clearing the cache automatically or *insisting* that the user agrees to clear
the cache. Obviously no workaround can be 100% reliable in the face of
undefined behavior.
--
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 #2 from Igor Kushnir --- (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. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 486656] Selecting text in the navigation widget demolishes clipboard history
https://bugs.kde.org/show_bug.cgi?id=486656 --- Comment #8 from Igor Kushnir --- So what's left to be done: 1. Revert https://commits.kde.org/kdevelop/dadaf13191e50cc99c3420f274f5e857f3050f06 2. Transfer our conclusions from here into the commit message and reference this bug as `BUG: 486656`. 3. Create a merge request. Should we rush the feature removal into the upcoming release https://community.kde.org/Schedules/KDE_Gear_24.05_Schedule or do it in master and release in August https://community.kde.org/Schedules/KDE_Gear_24.08_Schedule ? -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 486656] Selecting text in the navigation widget demolishes clipboard history
https://bugs.kde.org/show_bug.cgi?id=486656 --- Comment #6 from Igor Kushnir --- (In reply to Sven Brauch from comment #5) > Selection clipboard also works on Wayland, I tried it here. You are right, > that works even without this code for the navigation popup, I wasn't aware. I was pretty sure selection clipboard doesn't work in Wayland. But apparently it does for a while (see Bug 422426) and is even specified in a Wayland protocol (though unstable): https://wayland.app/protocols/primary-selection-unstable-v1. > I would much prefer removing the feature completely over adding a button. > The navigation widget is shown a lot, is already *very* cluttered, and > copying text from it isn't something that happens very often. > > If copying (beyond the selection clipboard) is needed, IMO it should go into > the context menu (which doesn't exist right now, but could be added). I agree that the feature belongs to the context menu and that the original feature can be removed for now to fix this bug. Tianshu Feng, what's your take on this plan? -- 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 #1 from Igor Kushnir --- This bug is sort of reverse of Bug 409858 fixed in the mentioned merge request. Documents with a non-Untitled URL that don't have corresponding files on disk disappear when starting/stopping debugging too: 1. A nonexistent file opened by double-clicking a row in Breakpoints tool view. 2. A file that was opened in KDevelop editor, then deleted from disk externally. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 486746] New: Untitled documents disappear from the working set when the user starts or stops debugging
https://bugs.kde.org/show_bug.cgi?id=486746 Bug ID: 486746 Summary: Untitled documents disappear from the working set when the user starts or stops debugging Classification: Applications Product: kdevelop Version: 5.14.240480 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: UI: general Assignee: kdevelop-bugs-n...@kde.org Reporter: igor...@gmail.com Target Milestone: --- SUMMARY Working area change from Code to Debug or vise versa (but not from Code to Review and back) hides and makes inaccessible all untitled (unsaved) documents. Text entered in these documents is lost to the user, without any confirmation/save prompt. The open document counter is not decremented - new untitled documents contain greater numbers in their URLs after the older untitled documents disappear, so it appears the documents exist, but are inaccessible in the UI. Sometimes the few documents that became inaccessible most recently can be recovered from the Documents tool view or from the Most-Recently-Used Document Switcher. STEPS TO REPRODUCE 1. Create one or more documents, (optionally) type text into them, but do not save them. 2. Start debugging. 3. (optionally) Repeat step 1. 4. Stop debugging. OBSERVED RESULT The untitled document tabs disappear and are absent from the Active Working Set. KDevelop prints warnings like these: kdevplatform.workingset: Unable to find file "file:///Untitled" kdevplatform.workingset: Unable to find file "file:///Untitled (1)" EXPECTED RESULT The untitled document tabs are preserved when debugging is started or stopped. ADDITIONAL INFORMATION I suspect that this bug was introduced by the merge request that introduced the printed warning: https://invent.kde.org/kdevelop/kdevelop/-/merge_requests/213 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 486656] Selecting text in the navigation widget demolishes clipboard history
https://bugs.kde.org/show_bug.cgi?id=486656 --- Comment #4 from Igor Kushnir --- Sven, maybe we should restore the initial implementation with a button at https://phabricator.kde.org/D7157?id=17766, which Kevin Funk had suggested but you rejected? -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 486656] Selecting text in the navigation widget demolishes clipboard history
https://bugs.kde.org/show_bug.cgi?id=486656 --- Comment #3 from Igor Kushnir --- (In reply to Sven Brauch from comment #2) > Maybe the issue here is rather that text is copied to the wrong clipboard? I > think the expected behaviour on unix-like systems would be copying the text > to the `QClipboard::Selection` clipboard, but instead this code uses > `QTextEdit::copy()` which apparently copies to `QClipboard::Clipboard`. Copying to the usual clipboard was probably intended by the author of the code under discussion. The selection clipboard is populated automatically (as in all other applications), even with that connection to QTextEdit::selectionChanged commented out (just tested). Kevin Funk commented on the first review of the feature - https://phabricator.kde.org/D5794: > Also note: Selecting the next, then pressing the middle mouse button already > does work. > This is not discoverable on other platforms than Linux though. We don't care much about and barely support non-GNU/Linux platforms nowadays. But selection clipboard may work only on X11, not Wayland (cannot verify because I don't use Wayland). If it turns out that selection *does* more or less work on Wayland, the feature (connection) could be removed or limited to Windows and macOS. Also just tested: with the connection commented out, Ctrl+C hides the navigation widget and copies text that is selected in the editor, not navigation widget. That is, if selection clipboard is unavailable, there is no way (that I can see) to copy text from the navigation widget. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 486656] Selecting text in the navigation widget demolishes clipboard history
https://bugs.kde.org/show_bug.cgi?id=486656 Igor Kushnir changed: What|Removed |Added Status|REPORTED|CONFIRMED CC||igor...@gmail.com Ever confirmed|0 |1 --- Comment #1 from Igor Kushnir --- I completely agree with your analysis. And you found the responsible code. A quick search turned up nothing else like this auto-copying feature in KDevelop code. Git blame reveals that it was introduced in https://phabricator.kde.org/D7157. I'll be happy to review a merge request at https://invent.kde.org/kdevelop/kdevelop/-/merge_requests that prevents clipboard history flooding and/or makes the feature more discoverable. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 386985] akonadi CalDav resource not synching with certain servers
https://bugs.kde.org/show_bug.cgi?id=386985 --- Comment #64 from Igor Murzich --- I confirm that bug, synching with carddav.yandex.ru carddav still doesn't work. Kontact 6.0.2 (24.02.0) akonadi 6.0.2 (24.02.2) -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 386985] akonadi CalDav resource not synching with certain servers
https://bugs.kde.org/show_bug.cgi?id=386985 Igor Murzich changed: What|Removed |Added CC||imurz...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 486541] New: Embedded null character and subsequent characters in a watched QString are not displayed while debugging
https://bugs.kde.org/show_bug.cgi?id=486541 Bug ID: 486541 Summary: Embedded null character and subsequent characters in a watched QString are not displayed while debugging Classification: Applications Product: kdevelop Version: 5.14.240480 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: CPP Debugger Assignee: kdevelop-bugs-n...@kde.org Reporter: igor...@gmail.com CC: niko.s...@gmail.com Target Milestone: --- STEPS TO REPRODUCE 1. Debug the following (Qt 5) code: ``` QString str = "abcdef"; // (1) str[3] = 0; // (2) ``` 2. Look at the value of `str` before and after the line (2) in Variables tool view and in the debugger tooltip for the variable `str`. 3. Run the GDB command `print str` in GDB tool view before and after the line (2). OBSERVED RESULT 2. The value of `str` is "abcdef" before the line (2) and "abc" after it - both in Variables tool view and in the debugger tooltip. 3. GDB tool view displays `$1 = "abcdef"` before the line (2) and `$2 = "abc\000ef"` after it. Incidentally, the same value is displayed while debugging with GDB in terminal outside of KDevelop but using KDevelop's pretty printers. EXPECTED RESULT The value of `str` is something like "abc\0ef" in Variables tool view, debugger tooltip and GDB tool view. "\000" in GDB tool view is indisputably better than truncating the string, but I think "\0" would be a clearer representation of the null character, at least to C++ developers. ADDITIONAL INFORMATION The bug is present as early as in MIDebugger::readyReadStandardOutput(), where the values of `reply` received from GDB are: 1 (before the line (2)): "35^done,name=\"var0\",numchild=\"0\",value=\"\\\"abcdef\\\"\",type=\"QString\",displayhint=\"string\",dynamic=\"1\",has_more=\"0\"" 2 (after the line (2)): "35^done,name=\"var3\",numchild=\"0\",value=\"\\\"abc\\\"\",type=\"QString\",displayhint=\"string\",dynamic=\"1\",has_more=\"0\"" 3 (GDB tool view after the line (2)): "~\"$1 = \\\"abc000ef\\\"\\n\"" For some reason, GDB returns only 3 characters "abc" for variable display, but the entire string "abc\000ef" as the reply to the manual GDB print command. After the truncated string value "abc" is read in MIDebugger::readyReadStandardOutput(), it eventually ends up in MIParser::parseStringLiteral() and then is displayed in the UI. The same issue affects QByteArray in almost identical fashion and with practically the same results (except for minor differences because of divergent pretty-printing formats of KDevelop's QStringPrinter and QByteArrayPrinter). -- You are receiving this mail because: You are watching all bug changes.
[libplasma] [Bug 486431] Templates for C++ Plasmoids look for KF6PlasmaConfig
https://bugs.kde.org/show_bug.cgi?id=486431 Igor Kushnir changed: What|Removed |Added Component|Language Support: CPP |libplasma |(Clang-based) | Assignee|kdevelop-bugs-n...@kde.org |plasma-b...@kde.org Version|git master |unspecified CC||m...@ratijas.tk, ||notm...@gmail.com Product|kdevelop|libplasma --- Comment #9 from Igor Kushnir --- (In reply to Matthias from comment #8) > I found, that the CMakeLists.txt in /plugin and /src had been adjusted by > Nicolas 5 months ago, the CMakeLists.txt in the upper directory, has not > seen such an adjustment. Could it be, that this is the cause? Sorry, I know almost nothing about plasmoids. Maybe someone else can answer that question and fix the issue. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 486061] Launch configuration arguments are not fully passed when executing (escaped)
https://bugs.kde.org/show_bug.cgi?id=486061 --- Comment #4 from Igor Kushnir --- launch_window.png shows the argument as capitalize, without square brackets. Is this a screenshot mistake? Is escaping the only working solution or does quoting the argument work too? (In reply to Gerald Senarclens de Grancy from comment #3) > A possible alternative to using the argument text input as a raw string > would be to add a proper help message telling the user which characters > require escaping. Feel free to implement the help message (as a tooltip perhaps) and create a merge request at https://invent.kde.org/kdevelop/kdevelop/-/merge_requests -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 486431] Templates for C++ Plasmoids look for KF6PlasmaConfig
https://bugs.kde.org/show_bug.cgi?id=486431 --- Comment #7 from Igor Kushnir --- Found newer templates in the Plasma/6.0 branch: https://invent.kde.org/plasma/libplasma/-/tree/Plasma/6.0/templates -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 486431] Templates for C++ Plasmoids look for KF6PlasmaConfig
https://bugs.kde.org/show_bug.cgi?id=486431 --- Comment #6 from Igor Kushnir --- Can you find the broken template files in /usr/share/kdevappwizard/templates/ and check which package provides them? On my Qt 5 system different templates are provided by various packages: kdevelop, plasma-framework5, kio5, kirigami2, kdeplasma-addons, etc. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 486431] Templates for C++ Plasmoids look for KF6PlasmaConfig
https://bugs.kde.org/show_bug.cgi?id=486431 Igor Kushnir changed: What|Removed |Added CC||igor...@gmail.com --- Comment #1 from Igor Kushnir --- Are these the templates in question? https://invent.kde.org/plasma/libplasma/-/tree/8953e77ec26b90da0e79e3cf3ecb727034768d58/templates They are part of the libplasma repository, not KDevelop, so perhaps change the Product field accordingly? You could even try to fix the templates yourself and create a libplasma merge request. -- You are receiving this mail because: You are watching all bug changes.
[kio-gdrive] [Bug 486384] New: kio-gdrive sends a bad request to the Google API
https://bugs.kde.org/show_bug.cgi?id=486384
Bug ID: 486384
Summary: kio-gdrive sends a bad request to the Google API
Classification: Frameworks and Libraries
Product: kio-gdrive
Version: 24.02.2
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: elvis.angelac...@kde.org
Reporter: igorrum...@gmail.com
Target Milestone: ---
SUMMARY
I am getting a "Bad request" notification when opening my GDrive
STEPS TO REPRODUCE
1. Open GDrive in Dolphin
2.
3.
OBSERVED RESULT
Bad request notification shown.
EXPECTED RESULT
Able to access my GDrive
SOFTWARE/OS VERSIONS
Windows:
macOS:
Linux/KDE Plasma: Tuxedo OS 3
(available in About System)
KDE Plasma Version: 6.0.4
KDE Frameworks Version: 6.1.0
Qt Version: 6.7.0
ADDITIONAL INFORMATION
I got this line in the logs:
kioworker[25407]: org.kde.kgapi: Bad request, Google replied ' "{\n
\"error\": {\n\"code\": 400,\n\"message\": \"Invalid field selection
etag,kind,nextLink,nextPageToken,selfLink,items(labels,exportLinks,lastViewedByMeDate,alternateLink,kind)\",\n
\"errors\": [\n {\n\"message\": \"Invalid field selection
etag,kind,nextLink,nextPageToken,selfLink,items(labels,exportLinks,lastViewedByMeDate,alternateLink,kind)\",\n
\"domain\": \"global\",\n\"reason\": \"invalidParameter\",\n
\"location\": \"fields\",\n\"locationType\": \"parameter\"\n
}\n]\n }\n}\n"
--
You are receiving this mail because:
You are watching all bug changes.
[kdevelop] [Bug 486061] Launch configuration arguments are not fully passed when executing (escaped)
https://bugs.kde.org/show_bug.cgi?id=486061 Igor Kushnir changed: What|Removed |Added CC||igor...@gmail.com --- Comment #2 from Igor Kushnir --- I think the user is responsible for quoting or escaping problematic arguments manually. If KDevelop quotes the string automatically, passing multiple arguments becomes impossible. If KDevelop escapes special characters automatically, quoted or already escaped arguments in existing user configurations would break. -- You are receiving this mail because: You are watching all bug changes.
