[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=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=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)
at
/home/Mi
[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=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=...) at
/
[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.
[Discover] [Bug 485634] Bad contrasting icon of available updates on dark toolbar.
https://bugs.kde.org/show_bug.cgi?id=485634 --- Comment #8 from Igor Mironchik --- Guys, I see that this issue was fixed. Could you confirm it? -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 485634] Bad contrasting icon of available updates on dark toolbar.
https://bugs.kde.org/show_bug.cgi?id=485634 --- Comment #7 from Igor Mironchik --- Created attachment 168645 --> https://bugs.kde.org/attachment.cgi?id=168645=edit Fixed? -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 485634] Bad contrasting icon of available updates on dark toolbar.
https://bugs.kde.org/show_bug.cgi?id=485634 --- Comment #5 from Igor Mironchik --- And if it matters I'm on X11 session. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 485634] Bad contrasting icon of available updates on dark toolbar.
https://bugs.kde.org/show_bug.cgi?id=485634 --- Comment #4 from Igor Mironchik --- I got it. In Breeze Dark everything is fine, in Breeze the same - all is fine. But in Breeze Twilight ( tool bar and system menu are dark, but windows are white) I have this issue. Please check again. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 485634] Bad contrasting icon of available updates on dark toolbar.
https://bugs.kde.org/show_bug.cgi?id=485634 --- Comment #2 from Igor Mironchik --- Hm, I need to play a little on the next update, when I will see this icon. Don't close this issue till I check. What this icon looks for you? -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 485634] New: Bad contrasting icon of available updates on dark toolbar.
https://bugs.kde.org/show_bug.cgi?id=485634 Bug ID: 485634 Summary: Bad contrasting icon of available updates on dark toolbar. 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 168582 --> https://bugs.kde.org/attachment.cgi?id=168582=edit Icon for available updates SUMMARY Bad contrasting icon of available updates on dark toolbar. STEPS TO REPRODUCE 1. Wait for available updates with dark theme in Plasma 6 2. 3. OBSERVED RESULT Icon for available updates is very low seen, look at the attached screenshot. EXPECTED RESULT I'd like to see something more seen. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDE neon 6.0 (available in About System) KDE Plasma Version: 6.0.3 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 482983] Meson project with missing dependency re configures in infinite loop
https://bugs.kde.org/show_bug.cgi?id=482983 Igor Kushnir changed: What|Removed |Added Version Fixed In||5.14 Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/kdev ||elop/kdevelop/-/commit/3416 ||38803895bd9910f8d79a4942733 ||b21f75ff3 Resolution|--- |FIXED --- Comment #12 from Igor Kushnir --- Git commit 341638803895bd9910f8d79a4942733b21f75ff3 by Igor Kushnir, on behalf of Jairus Martin. Committed on 05/04/2024 at 10:54. Pushed by igorkushnir into branch 'master'. Only reparse project if meson-info contents change Currently there is a file watcher that reloads the project when the meson-info.json file changes. If the project fails to configure, kdevelop keeps attempting to reconfigure in a loop because the meson-info.json file keeps getting rewritten. This change makes it only reconfigure if the contents of the watched file are actually changed avoiding the loop. FIXED-IN: 5.14 M +25 -0plugins/meson/mesonmanager.cpp M +1-0plugins/meson/mesonmanager.h https://invent.kde.org/kdevelop/kdevelop/-/commit/341638803895bd9910f8d79a4942733b21f75ff3 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 482983] Meson project with missing dependency re configures in infinite loop
https://bugs.kde.org/show_bug.cgi?id=482983 --- Comment #11 from Igor Kushnir --- (In reply to frmdstryr from comment #10) > There may be an better/easier way to fix it since it seems like a race > condition because there is a watch on create and dirty it so the job appears > to be running twice in parallel. Sorry, haven't noticed the suggestion about a better fix before reviewing your merge request. I think the Meson configure job creates the file. The MESON_FAILED_CONFIGURATION branch in MesonBuilder::configure() is taken. But I don't know how to fix this properly. Detect the configure loop and break it somehow? Would that be better than the relatively simple and safe file hash sum approach in the merge request? -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 482983] Meson project with missing dependency re configures in infinite loop
https://bugs.kde.org/show_bug.cgi?id=482983
--- Comment #7 from Igor Kushnir ---
I cannot reproduce the infinite loop when I add a bogus dependency to the
simple meson project created from a KDevelop template
(Standard=>Terminal=>Meson C++):
```
+ bb=dependency('missingd', version:'>=5.0')
executable('kdev-meson-cpp-test-project',
'main.cpp',
include_directories : incdir
+ , dependencies : bb
```
The configuration job fails once and is not restarted:
```
Run-time dependency missingd found: NO (tried pkgconfig and cmake)
meson.build:15:3: ERROR: Dependency "missingd" not found, tried pkgconfig and
cmake
A full log can be found at
/path/to/kdev-meson-cpp-test-project/build/meson-logs/meson-log.txt
*** Failure: Exit code 1 ***
```
Is some additional configuration of the project or KDevelop needed?
--
You are receiving this mail because:
You are watching all bug changes.
[kdevelop] [Bug 482983] Meson project with missing dependency re configures in infinite loop
https://bugs.kde.org/show_bug.cgi?id=482983 --- Comment #5 from Igor Kushnir --- (In reply to frmdstryr from comment #4) > This issue is unrelated to KF6 from what I can tell. The file watcher > triggers when the meson file stats change even if no contents changed. Rebase on master and create a merge request at https://invent.kde.org/kdevelop/kdevelop/-/merge_requests please. Maybe expand the commit message to explain the bug and the fix better. Add the following after a blank line at the bottom of the commit message to comment and automatically close this bug when merged: BUG: 482983 FIXED-IN: 5.14 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 484536] Unable to login using Wayland after OS update.
https://bugs.kde.org/show_bug.cgi?id=484536 Igor changed: What|Removed |Added CC||igorpa...@tutanota.com -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 484441] Installing texlive LaTeX made font on login screen smaller
https://bugs.kde.org/show_bug.cgi?id=484441 Igor Mironchik changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #4 from Igor Mironchik --- Got it, it was fixed by clicking "Apply Plasma Settings" button on Login Screen settings page. Thanks. I will check it as NOT A BUG. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 484441] Installing texlive LaTeX made font on login screen smaller
https://bugs.kde.org/show_bug.cgi?id=484441 --- Comment #3 from Igor Mironchik --- Guys, I'm maybe wrong here, can't check as KDE neon 6.0 impossible to install under VirtualBox. Could you compare login screen with yours? Check password field width, I have ~3cm. But on lock screen I have ~4cm. Not sure already, when I installed the above packages something caught my eye... -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 484441] Installing texlive LaTeX made font on login screen smaller
https://bugs.kde.org/show_bug.cgi?id=484441 --- Comment #2 from Igor Mironchik --- Look at a lock screen, compare with login one. Even background color of password field. What is it? How can I fix it? -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 484441] Installing texlive LaTeX made font on login screen smaller
https://bugs.kde.org/show_bug.cgi?id=484441 --- Comment #1 from Igor Mironchik --- Created attachment 167729 --> https://bugs.kde.org/attachment.cgi?id=167729=edit Lock screen, seems fine? -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 484441] New: Installing texlive LaTeX made font on login screen smaller
https://bugs.kde.org/show_bug.cgi?id=484441 Bug ID: 484441 Summary: Installing texlive LaTeX made font on login screen smaller 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 167727 --> https://bugs.kde.org/attachment.cgi?id=167727=edit Login screen with changed fonts SUMMARY Installing following packages made login screen's font smaller, and a field for a password shorter. STEPS TO REPRODUCE 1. Install texlive-latex-base texlive-fonts-recommended texlive-fonts-extra texlive-latex-extra 2. Reboot 3. OBSERVED RESULT Field for a password became shorter and font's size smaller. It's a little ugly now, look at the attached screenshot. On lock screen field for a password at 1 cm longer, what is better, but something is wrong anyway. Uninstalling those packages doesn't solve the problem. EXPECTED RESULT I expect to see Plasma UI the same. How can I fix it? SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDE neon 6.0 (available in About System) KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 481189] No option to attach to the process
https://bugs.kde.org/show_bug.cgi?id=481189 Igor Kushnir changed: What|Removed |Added Resolution|--- |DOWNSTREAM Status|CONFIRMED |RESOLVED --- Comment #14 from Igor Kushnir --- This must be a packaging issue as I wrote earlier. Nothing to be done in KDevelop's code, other than porting to KF6 and making the packagers' task easier. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475077] Show non-linear virtual desktop arrangements again
https://bugs.kde.org/show_bug.cgi?id=475077 Igor changed: What|Removed |Added CC||igorpa...@tutanota.com -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 484126] New: Clipboard UI is broken
https://bugs.kde.org/show_bug.cgi?id=484126 Bug ID: 484126 Summary: Clipboard UI is broken 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: --- SUMMARY Clipboard UI in Plasma 6 is broken. Copied data is not shown in clipboard widget. This was broken with today's update 21 March, 2024. STEPS TO REPRODUCE 1. Copy any text wherever you want. 2. Open clipboard widget in Plasma 6 3. OBSERVED RESULT Clipboard widget is always seen in system tray, but there are no data shown in it. EXPECTED RESULT You know what should be :) SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDE neon 6.0 (available in About System) KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION I see this issue in X11 session, didn't check Wayland. -- You are receiving this mail because: You are watching all bug changes.
[Keysmith] [Bug 484098] Keysmith does not encrypt your data
https://bugs.kde.org/show_bug.cgi?id=484098 Igor changed: What|Removed |Added CC||igorpa...@tutanota.com -- You are receiving this mail because: You are watching all bug changes.
[Keysmith] [Bug 484098] New: Keysmith does not encrypt your data
https://bugs.kde.org/show_bug.cgi?id=484098 Bug ID: 484098 Summary: Keysmith does not encrypt your data Classification: Applications Product: Keysmith Version: 24.02.0 Platform: openSUSE OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: General Assignee: bhus...@gmail.com Reporter: igorpa...@tutanota.com Target Milestone: --- If a malicious person gains access to a person's computer. It will have full access to Keysmith data in "~/.config/org.kde.keysmith". This is because the data is not encrypted. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 484072] New: Screen Config on Big Linux
https://bugs.kde.org/show_bug.cgi?id=484072 Bug ID: 484072 Summary: Screen Config on Big Linux Classification: Applications Product: systemsettings Version: 5.27.11 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_kscreen Assignee: kscreen-bugs-n...@kde.org Reporter: igoribei...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Open screen configuration 2. Using 2 monitors configuration and apply 3. Restart pc 4. Go to screen settings, it wasn't saved my screen configuration 5. 144hz config was saved, mas the screen on the left side, no... 6. It was on Big Linux, last version -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 483765] Crash after Saving CMake Changes
https://bugs.kde.org/show_bug.cgi?id=483765 Igor Kushnir changed: What|Removed |Added CC||igor...@gmail.com See Also||https://bugs.kde.org/show_b ||ug.cgi?id=455533 -- 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 See Also||https://bugs.kde.org/show_b ||ug.cgi?id=483765 -- You are receiving this mail because: You are watching all bug changes.
[kup] [Bug 482015] Kup system tray icon and settings module missing on Plasma 6
https://bugs.kde.org/show_bug.cgi?id=482015 Igor changed: What|Removed |Added CC||igorpa...@tutanota.com -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 481938] Unable to leave session via Desktop menu on Plasma 6.0.0
https://bugs.kde.org/show_bug.cgi?id=481938 Igor changed: What|Removed |Added CC||igorpa...@tutanota.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482040] Plasma 6 with X11 after auto-locking screen and shading blinks and almost unresponsive
https://bugs.kde.org/show_bug.cgi?id=482040 Igor Mironchik changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #15 from Igor Mironchik --- 13 March, 2024 UTC+3 15:12 Fixed! -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 482983] Meson project with missing dependency re configures in infinite loop
https://bugs.kde.org/show_bug.cgi?id=482983 --- Comment #3 from Igor Kushnir --- (In reply to frmdstryr from comment #2) > I pushed a branch that stops the loop to github > https://github.com/KDE/kdevelop/compare/master...frmdstryr:kdevelop:meson-info-only-reparse-if-contents-changed > . I had problems pushing to invent. What problem? Did you fork the KDevelop repository? Tried pushing to an SSH URL, e.g. g...@invent.kde.org:frmdstryr/kdevelop.git ? If the bug is present only in the branch work/apol/kf6, target it in your merge request. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 482983] Meson project with missing dependency re configures in infinite loop
https://bugs.kde.org/show_bug.cgi?id=482983 Igor Kushnir changed: What|Removed |Added CC||igor...@gmail.com --- Comment #1 from Igor Kushnir --- A fix merge request at https://invent.kde.org/kdevelop/kdevelop/-/merge_requests is welcome. Note that few KDevelop developers use Meson, so the KDevMesonManager plugin is not actively maintained. But users occasionally contribute small fixes to Meson support. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 481189] No option to attach to the process
https://bugs.kde.org/show_bug.cgi?id=481189 --- Comment #11 from Igor Kushnir --- (In reply to popov895 from comment #10) > https://invent.kde.org/plasma/libksysguard/-/commit/ > 4b9d502baff782426ce12ff12fb72e3094f7af1f > > The UI for selecting a process to attach was completely removed from > libksysguard. Right, but it is removed in libksysguard v6. KDevelop still requires libksysguard v5. https://invent.kde.org/kdevelop/kdevelop/-/merge_requests/533 deals with the v6 API removal. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 362485] After refresh editor (F5) already set breakpoint(s) are disappearing
https://bugs.kde.org/show_bug.cgi?id=362485 Igor Kushnir changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/kdev ||elop/kdevelop/-/commit/a152 ||4591a3d0d02a493c3742d2c772e ||9f7b50654 Version Fixed In||5.14 --- Comment #6 from Igor Kushnir --- Git commit a1524591a3d0d02a493c3742d2c772e9f7b50654 by Igor Kushnir. Committed on 08/03/2024 at 10:22. Pushed by igorkushnir into branch 'master'. BreakpointModel: complete document reload support This commit addresses the following issue and removes the FIXME comment that describes it: if a modified document is reloaded, and the user clicks a button other than "Discard" in the message box that appears, the moving cursors should not be reverted to their saved locations. When a modified document is reloaded, the user makes a Cancel/Discard/Save choice after the aboutToReload() signal is emitted. Therefore, BreakpointModel::aboutToReload() must not make any changes to breakpoints or breakpoint marks that depend on this user choice. Remove moving cursors during a reload later - in BreakpointModel::aboutToInvalidateMovingInterfaceContent() instead of BreakpointModel::aboutToReload(). If the user cancels reloading a modified document, it does not emit the signal aboutToInvalidateMovingInterfaceContent(), its moving cursors are not invalidated and breakpoints remain intact. If the user reloads a modified document and opts to save it (and overwrite possible changes on disk), BreakpointModel::documentSaved() is invoked and saves the breakpoints' tracked line numbers before aboutToInvalidateMovingInterfaceContent() removes the moving cursors. If the user reloads a modified document and opts to discard editor changes or reloads an unmodified document, the executed BreakpointModel code is almost unchanged, because these cases were already perfectly supported. The only consequential difference is that aboutToReload() inhibits mark change instead of removing all breakpoint marks in the reloaded document. That's because the breakpoint marks must not be removed in case the user cancels reloading. Unfortunately, not removing breakpoint marks in aboutToReload() lets KTextEditor::DocumentPrivate::documentReload() store in a local variable all of the document's breakpoint marks. The saving and restoring of breakpoint marks by KTextEditor is useless work, because BreakpointModel has a different notion/algorithm where breakpoint marks should be placed after the document is reloaded. There is no API to prevent this useless KTextEditor work. So BreakpointModel resorts to working around possible mark conflicts by removing all breakpoint marks in the document before adding them at correct locations in case of the Discard user choice. In case of the Save user choice or when an unmodified document is reloaded, KTextEditor restores breakpoint marks at correct locations. BreakpointModel still restores breakpoint marks again afterwards, because KTextEditor may choose to skip restoring some of the marks. This double restoration is safe, because KTextEditor::Document's member function addMark(int line, uint markType) does not change anything if a mark of the type `markType` is already set on the line `line`. Connect to 3 KTextEditor::Document's signals - aboutToReload(), aboutToInvalidateMovingInterfaceContent() and reloaded() in BreakpointModel::textDocumentCreated(). The downside of connecting to every open document's signals is that both the connecting itself and the work in the slots when the document is reloaded is useless if there are no breakpoints at its URL (which should be the case for most documents). I have considered and rejected connecting to these 3 signals in BreakpointModel::setupMovingCursor(), which is called only for documents that contain breakpoints. The problem is that a moving cursor is not set up for a breakpoint at a line out of the document's range. But reloading may increase the number of lines in the document and thus allow BreakpointModel::reloaded() to enable document line tracking for newly-in-range breakpoints. In the future, BreakpointModel should acquire a way to efficiently access all breakpoints in a given document. This would substantially reduce overhead for documents without breakpoints and allow to move the existing aboutToDeleteMovingInterfaceContent() connection from setupMovingCursor() to textDocumentCreated(). A unit test cannot make the Cancel/Discard/Save user choice programmatically instead of showing the Close Document warning dialog. Add semiautomatic tests and skip them by def
[kde] [Bug 482040] Plasma 6 with X11 after auto-locking screen and shading blinks and almost unresponsive
https://bugs.kde.org/show_bug.cgi?id=482040 --- Comment #14 from Igor Mironchik --- 05 March, 2024 UTC+3 19:45 The rules change a little. After locking and turning off a screen, I'm with some difficulties able to login, the screen is not blinking, but there happens something difficult to describe. With some dance I can see a field for password, but after successful login I see that blinking of the screen. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 482040] Plasma 6 with X11 after auto-locking screen and shading blinks and almost unresponsive
https://bugs.kde.org/show_bug.cgi?id=482040 Igor Mironchik changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 482435] New: DND from Android/Dolphin to Krusader doesn't work
https://bugs.kde.org/show_bug.cgi?id=482435 Bug ID: 482435 Summary: DND from Android/Dolphin to Krusader doesn't work 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 166412 --> https://bugs.kde.org/attachment.cgi?id=166412=edit Recording of the problem SUMMARY DND from Android/Dolphin to Krusader doesn't work STEPS TO REPRODUCE 1. Open folder on Android phone in Dolphin 2. DND file from Android to Krusader 3. OBSERVED RESULT Couldn't read file occurs. EXPECTED RESULT File should be copied. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDE neon 6 (available in About System) KDE Plasma Version: 6.0.0 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 482040] Plasma 6 with X11 after auto-locking screen and shading blinks and almost unresponsive
https://bugs.kde.org/show_bug.cgi?id=482040 --- Comment #13 from Igor Mironchik --- (In reply to Igor Mironchik from comment #12) > Created attachment 166411 [details] > [blinking.mp4] This is a link to YouTube -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 482040] Plasma 6 with X11 after auto-locking screen and shading blinks and almost unresponsive
https://bugs.kde.org/show_bug.cgi?id=482040 --- Comment #12 from Igor Mironchik --- Created attachment 166411 --> https://bugs.kde.org/attachment.cgi?id=166411=edit [blinking.mp4] -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 482040] Plasma 6 with X11 after auto-locking screen and shading blinks and almost unresponsive
https://bugs.kde.org/show_bug.cgi?id=482040 --- Comment #11 from Igor Mironchik --- Created attachment 166410 --> https://bugs.kde.org/attachment.cgi?id=166410=edit [2.png] -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 482040] Plasma 6 with X11 after auto-locking screen and shading blinks and almost unresponsive
https://bugs.kde.org/show_bug.cgi?id=482040 --- Comment #10 from Igor Mironchik --- Created attachment 166409 --> https://bugs.kde.org/attachment.cgi?id=166409=edit [1.png] -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 482040] Plasma 6 with X11 after auto-locking screen and shading blinks and almost unresponsive
https://bugs.kde.org/show_bug.cgi?id=482040 --- Comment #9 from Igor Mironchik --- I want to add some details... The picture of the issue is changing a little if chekboxes on screen [2.png] is not checked - in this case after locking I see a black screen, pressing hardware power button shows lock screen in normal mode, I'm able to iterate there, but when entering password and unlocking I see the same blinking in unlocked session. Note that this happened on X11 session, NOT ON WAYLAND. Recording [blinking.mp4] was made both with [1.png] and [2.png] settings. I closed lid of laptop, waited some seconds, and opened the lid. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 482040] Plasma 6 with X11 after auto-locking screen and shading blinks and almost unresponsive
https://bugs.kde.org/show_bug.cgi?id=482040 --- Comment #7 from Igor Mironchik --- (In reply to Nate Graham from comment #6) > Does that mean you updated your system and it's still happening? Sorry, that I was not clear. Sure, exactly. I installed updates, turned on screen locking, locked my laptop, and the issue the same, and very aggressive, I ran to shutdown my laptop by long-press of hardware shutdown button. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 482040] Plasma 6 with X11 after auto-locking screen and shading blinks and almost unresponsive
https://bugs.kde.org/show_bug.cgi?id=482040 --- Comment #5 from Igor Mironchik --- 4 March, 2024, UTC+3 12:53 - The problem is still there... -- You are receiving this mail because: You are watching all bug changes.
