[i18n] [Bug 477043] New: improve "unknown number" translation on KDE Connect
https://bugs.kde.org/show_bug.cgi?id=477043 Bug ID: 477043 Summary: improve "unknown number" translation on KDE Connect Classification: Translations Product: i18n Version: unspecified Platform: Other OS: All Status: REPORTED Severity: normal Priority: NOR Component: fr Assignee: kde-francoph...@kde.org Reporter: cypr...@devillez.eu Target Milestone: --- On KDE Connect "unknown number" calls are translated into "nombre inconnu" calls which is not a relevant to say that in french. "numéro inconnu" would be a better translation https://invent.kde.org/network/kdeconnect-kde/-/blob/master/po/fr/kdeconnect-plugins.po?ref_type=heads#L489 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 50443] selecting text difficult while more output is written to the console
https://bugs.kde.org/show_bug.cgi?id=50443 Cyp changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED CC||cyp...@gmail.com --- Comment #30 from Cyp --- Still happens with konsole 23.04.3. I did: 0. Adjust Scrollback says I have 1 lines scrollback. 1. while ((1)) ; do echo $RANDOM ; sleep .001 ; done 2. Scroll to top of buffer, so I can see when it starts overflowing. 3. When it overflows, scroll to the middle of the buffer. 4. Even though the numbers on the screen aren't moving, trying to select with click+drag or triple-click selects some random lines further down. The selected area flickers wildly all over the place (but only under the area that should have been selected), if slowly moving the mouse during a click+drag, even though the rest of the window is static. P.S. Not sure what just happened to being able to vote on bugs. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 410455] Unable to parse Linux kernel sources
https://bugs.kde.org/show_bug.cgi?id=410455 --- Comment #4 from Cyp --- Restarting kdevelop without killing often isn't possible, since when quitting, it often ends up with 100% CPU forever in the background until killed. Thanks, unchecking “Settings” (in the top menu bar) → “Configure KDevelop” → “Projects” → “Schedule all project files for parsing” seems to have helped. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 410455] Unable to parse Linux kernel sources
https://bugs.kde.org/show_bug.cgi?id=410455 Cyp changed: What|Removed |Added CC||cyp...@gmail.com --- Comment #1 from Cyp --- Same here with kdevelop-23.04.3, memory usage reached 49 GB before the OOM-killer kicked in. [1570147.196336] [ pid ] uid tgid total_vm rss pgtables_bytes swapents oom_score_adj name [1570147.197206] [ 14374] 1000 14374 12368969 4650241 8704 5140779 0 kdevelop [1570147.197303] oom-kill:constraint=CONSTRAINT_NONE,nodemask=(null),cpuset=/,mems_allowed=0,global_oom,task_memcg=/,task=kdevelop,pid=14374,uid=1000 [1570147.197352] Out of memory: Killed process 14374 (kdevelop) total-vm:49475876kB, anon-rss:18600964kB, file-rss:0kB, shmem-rss:0kB, UID:1000 pgtables:85000kB oom_score_adj:0 [1570154.066131] oom_reaper: reaped process 14374 (kdevelop), now anon-rss:0kB, file-rss:0kB, shmem-rss:0kB -- You are receiving this mail because: You are watching all bug changes.
[kasts] [Bug 465366] Flatpak do not start, module "org.kde.kirigami" version 2.20 is not installed
https://bugs.kde.org/show_bug.cgi?id=465366 Cyp changed: What|Removed |Added Status|NEEDSINFO |RESOLVED --- Comment #4 from Cyp --- Thank it's fix the problem. I removed all flatpak installed as user to reduce new problem (most of the time I only rely on Manjaro updater, Pamac, which do not seems to update they) -- You are receiving this mail because: You are watching all bug changes.
[kasts] [Bug 465366] Flatpak do not start, module "org.kde.kirigami" version 2.20 is not installed
https://bugs.kde.org/show_bug.cgi?id=465366 --- Comment #2 from Cyp --- Some info about my install below. I try to remove/reinstall Kasts without improvement. Maybe I should try to install a newer org.kde.Platform version (5.15-22.08 is available but not installed by flatpak update). ``` sh-5.1$ flatpak --version Flatpak 1.15.1 sh-5.1$ sudo flatpak update Looking for updates… Nothing to do. sh-5.1$ flatpak list Name Application ID Version Branch Installation calibre com.calibre_ebook.calibre 6.12.0stable system Mattermostcom.mattermost.Desktop 5.2.2 stable system Skype com.skype.Client 8.93.0.404stable system Sweet Home 3D com.sweethome3d.Sweethome3d 7.0.2 stable system Shortwave de.haeckerfelix.Shortwave 3.1.0 stable system Shortwave de.haeckerfelix.Shortwave 3.0.0 stable user Clementine Music Player org.clementine_player.Clementine1.4.0rc2 stable user Freedesktop Platform org.freedesktop.Platform 21.08.18 21.08 system Freedesktop Platform org.freedesktop.Platform 22.08.7 22.08 system Mesa org.freedesktop.Platform.GL.default 21.3.921.08 system Mesa org.freedesktop.Platform.GL.default 21.3.821.08 user Mesa org.freedesktop.Platform.GL.default 22.3.422.08 system Mesa (Extra) org.freedesktop.Platform.GL.default 22.3.4 22.08-extrasystem ffmpeg-full org.freedesktop.Platform.ffmpeg-full 20.08 user ffmpeg-full org.freedesktop.Platform.ffmpeg-full 21.08 user openh264 org.freedesktop.Platform.openh264 2.1.0 2.0 system openh264 org.freedesktop.Platform.openh264 2.1.0 2.0 user openh264 org.freedesktop.Platform.openh264 2.1.0 2.2.0 system openh264 org.freedesktop.Platform.openh264 2.1.0 2.3.0 system GNOME Application Platform version 42 org.gnome.Platform 42 system GNOME Application Platform version 43 org.gnome.Platform 43 system Podcasts org.gnome.Podcasts 0.5.1 stable system nuclear music player org.js.nuclear.Nuclear 95cfe0stable system Adwaita theme org.kde.KStyle.Adwaita 5.15-21.08 system KDE Application Platform org.kde.Platform 5.15-21.08 system KDE Application Platform org.kde.Platform 5.15-21.08 user Kasts org.kde.kasts 23.01 stable system Telegram Desktop org.telegram.desktop 3.7.3 stable user Telegram Desktop Webview Add-on org.telegram.desktop.webview 2.36.1stable user VLC org.videolan.VLC
[kasts] [Bug 465366] New: Flatpak do not start, module "org.kde.kirigami" version 2.20 is not installed
https://bugs.kde.org/show_bug.cgi?id=465366 Bug ID: 465366 Summary: Flatpak do not start, module "org.kde.kirigami" version 2.20 is not installed Classification: Applications Product: kasts Version: 23.01.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: b...@mogwai.be Reporter: cypr...@devillez.eu Target Milestone: --- Since last update Flatpak version of Kasts failed to start. STEPS TO REPRODUCE 1. Install Kasts with flatpak `flatpak install org.kde.kasts` 2. Launch Kasts with flatpak `flatpak run org.kde.kasts` OBSERVED RESULT Launch failed with the following error: ``` Database version 6 QQmlApplicationEngine failed to load component qrc:/main.qml:14:1: module "org.kde.kirigami" version 2.20 is not installed kasts: ../p11-kit/rpc-transport.c :723 : rpc_transport_buffer: l'assertion « sock->refs > 0 » a échoué. ``` EXPECTED RESULT Launch succeed. SOFTWARE/OS VERSIONS Manjaro KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.8 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 463800] konsole scrolling 3 tabs at a time, or up/down 1 line at a time
https://bugs.kde.org/show_bug.cgi?id=463800 --- Comment #4 from Cyp --- Yes, seems to happen with another mouse too (maybe even worse somehow). The mice I tested with are: • Logitech MX Anywhere 3 (originally) • Logitech MX Master (tested just now) Don't know if it could be something specific to Logitech mice…? Both happen to have some weird feature where the scroll wheel can be unlocked by pressing a button, making it spin freely without friction. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 463800] konsole scrolling 3 tabs at a time, or up/down 1 line at a time
https://bugs.kde.org/show_bug.cgi?id=463800 --- Comment #2 from Cyp --- Testing a bit more, it seems that it's sometimes possible to scroll 1 tab at a time, if physically moving the scroll wheel very very slowly. Somehow it seems to be able to tell how fast I'm physically moving the scroll wheel when I scroll a single tick. Didn't think that was even possible. If scrolling very slowly (but not very very slowly), then half-way through scrolling a single tick (before I'd expect the mouse to send the scroll event), it scrolls one tab left/right, and then another tab left/right once it's done scrolling. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 463800] New: konsole scrolling 3 tabs at a time, or up/down 1 line at a time
https://bugs.kde.org/show_bug.cgi?id=463800 Bug ID: 463800 Summary: konsole scrolling 3 tabs at a time, or up/down 1 line at a time Classification: Applications Product: konsole Version: 22.08.3 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: tabbar Assignee: konsole-de...@kde.org Reporter: cyp...@gmail.com Target Milestone: --- SUMMARY konsole scrolling gone weird. STEPS TO REPRODUCE 1. Scroll one step on the tab bar. 2. Scroll one step on the terminal. OBSERVED RESULT 1. It scrolls 3 tabs left/right. 2. It scrolls 1 line up/down. EXPECTED RESULT 1. It used to scroll 1 tab left/right. 2. It used to scroll 3 lines up/down. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.7 ADDITIONAL INFORMATION Shift+Left/Right still works normally, 1 tab at a time. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 463800] konsole scrolling 3 tabs at a time, or up/down 1 line at a time
https://bugs.kde.org/show_bug.cgi?id=463800 --- Comment #1 from Cyp --- Testing a bit more, 3 just seems to be the average. Often it's 3, but sometimes 2 or 4. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 460309] [Wayland] Menu, notifications, and search bar appear in the middle of the screen and have an icon on the taskbar
https://bugs.kde.org/show_bug.cgi?id=460309 --- Comment #3 from Cyp --- Created attachment 152748 --> https://bugs.kde.org/attachment.cgi?id=152748=edit menu misplaced -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 460309] [Wayland] Menu, notifications, and search bar appear in the middle of the screen and have an icon on the taskbar
https://bugs.kde.org/show_bug.cgi?id=460309 Cyp changed: What|Removed |Added Attachment #152746|search bar misplaced|notification misplaced description|| -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 460309] [Wayland] Menu, notifications, and search bar appear in the middle of the screen and have an icon on the taskbar
https://bugs.kde.org/show_bug.cgi?id=460309 --- Comment #2 from Cyp --- Created attachment 152747 --> https://bugs.kde.org/attachment.cgi?id=152747=edit search bar misplaced -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 460309] [Wayland] Menu, notifications, and search bar appear in the middle of the screen and have an icon on the taskbar
https://bugs.kde.org/show_bug.cgi?id=460309 --- Comment #1 from Cyp --- Created attachment 152746 --> https://bugs.kde.org/attachment.cgi?id=152746=edit search bar misplaced -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 460309] New: [Wayland] Menu, notifications, and search bar appear in the middle of the screen and have an icon on the taskbar
https://bugs.kde.org/show_bug.cgi?id=460309 Bug ID: 460309 Summary: [Wayland] Menu, notifications, and search bar appear in the middle of the screen and have an icon on the taskbar Classification: KDE Neon Product: neon Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Packages User Edition Assignee: neon-b...@kde.org Reporter: cypr...@devillez.eu CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- SUMMARY STEPS TO REPRODUCE Open menu, popup notification or open search bar in a Wayland sessions (single or multiscreen) OBSERVED RESULT Menu, notifications or search bar appear in the middle of the screen EXPECTED RESULT Menu appear near menu button, search bar appear top of screen, notification appear near notification area SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon 5.26 KDE Plasma Version: 5.26.0 (already broken in 5.25.5) KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 ADDITIONAL INFORMATION Work fine with X11 -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 423043] kalarm doesn't show alarms until restarting kalarm
https://bugs.kde.org/show_bug.cgi?id=423043
--- Comment #2 from Cyp ---
Thanks, I deleted lots and lots of kalarm entries marked as failed from
akonadiconsole.
They didn't reappear in akonadiconsole after starting kalarm, but
akonadi_kalarm_resource_{15,16,17} is now running, and
~/.local/share/kalarm/calendar.ics seems to get updated now.
Hope everything will work, now.
--
You are receiving this mail because:
You are watching all bug changes.
[kalarm] [Bug 423043] New: kalarm doesn't show alarms until restarting kalarm
https://bugs.kde.org/show_bug.cgi?id=423043 Bug ID: 423043 Summary: kalarm doesn't show alarms until restarting kalarm Product: kalarm Version: unspecified Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: general Assignee: djar...@kde.org Reporter: cyp...@gmail.com Target Milestone: --- SUMMARY kde-apps/kalarm-19.12.3 completely unusable, since most alarms don't appear unless restarting kalarm manually. STEPS TO REPRODUCE 1. Wait for an alarm to trigger. 2. See that it didn't. 3. Restart kalarm. 4. See the alarm pop up a week late. 5. Notice a mysterious "Show Calendars" button and click on it to see what it does. 6. See two calendars called "Active Alarms", one of which (~/.local/share/kalarm/calendar.ics) is forbidden to be disabled, and the other (~/.kde4/share/apps/kalarm/calendar.ics) can be disabled. 7. Disable the one that can be disabled, and see that most alarms are in it (since they disappear). 8. Reenable, and one of the alarms triggers. 9. Disable and reenable again and again, and the same alarm triggers again and again (despite having been closed multiple times). 10. Make a backup copy of the two calendar files. 11. Close kalarm. 12. Manually merge the calendars in a text editor. 13. Reopen kalarm, and see all the alarms have been split back into two files again. 14. Close kalarm. 15. Do 'killall -v -9 akonadi_kalarm_resource' to kill 12 processes. 16. Do 'killall -v -9 akonadi_kalarm_resource' to kill 12 more processes. 17. Do 'killall -v -9 akonadi_kalarm_resource' to kill 12 more processes. 18. Do 'killall -v -9 akonadi_kalarm_resource' and see they finally stopped coming back. 19. Merge the calendars in a text editor again. 20. Open kalarm. 21. See the alarms in two separate files again. 22. Delete the deletable calendar in kalarm 23. Close kalarm. 24 Try to kill any traces of it (although now there aren't any akonadi_kalarm_resource processes to kill). 25. See all alarms are still in ~/.local/share/kalarm/calendar.ics and that ~/.kde4/share/apps/kalarm/calendar.ics is still empty. 26. Reopen kalarm. 27. Wonder why kalarm still isn't showing the alarms in ~/.local/share/kalarm/calendar.ics that used to be in ~/.kde4/share/apps/kalarm/calendar.ics (just showing the few that were already there). 28. Create a new display alarm "test". 29. See that ~/.local/share/kalarm/calendar.ics doesn't get updated. 30. Close kalarm and try to kill any traces in case. 31. See that ~/.local/share/kalarm/calendar.ics still hasn't been updated. 32. Reopen kalarm, and see "test" pop up, despite it not being in ~/.local/share/kalarm/calendar.ics which is the only remaining calendar. 33. Right-click the calendar, choose Import. 34. Select the backup copy of ~/.kde4/share/apps/kalarm/calendar.ics. 35. Click "Open". Nothing happens. 36. Double-click the file to import. Nothing happens. 37. Repeat step 35. and 36. 10 times. 38. Run around in circles screaming in frustration, while pulling hair out. 39. Try typing the name of the backup file called "~\.kde4\share\apps\kalarm\calendar.ics", surrounded by double quotes. 40. Try opening it, which finally works, and it finally imports the alarms into the ~/.local/share/kalarm/calendar.ics calendar. 41. See that the ~/.local/share/kalarm/calendar.ics file hasn't been modified by importing the calendars (which were already in the file, anyway). 42. Report this bug. OBSERVED RESULT See above. EXPECTED RESULT For most steps, pretty much the exact opposite. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: kde-frameworks/plasma-5.67.0-r3 KDE Frameworks Version: 5.67.0 Qt Version: 5.14.1-r4 ADDITIONAL INFORMATION At least there aren't 12 akonadi_kalarm_resource processes thrashing the hard drive constantly forever, like previous versions used to. So despite being completely unusable, the current version is still a major improvement. Come to think of it, it's weird that by the time I got to step 42, it's down to 0 akonadi_kalarm_resource processes, even after restarting kalarm. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 417971] Kdevelop crashes during autocomplete
https://bugs.kde.org/show_bug.cgi?id=417971 --- Comment #4 from Cyp --- After building llvm with `cmake -DLLVM_ENABLE_ASSERTIONS=ON -DLLVM_ENABLE_PROJECTS=clang -G "Unix Makefiles" ../llvm`: kdevelop: /git/llvm-project/clang/tools/libclang/CXCursor.cpp:129: CXCursor clang::cxcursor::MakeCXCursor(const clang::Stmt*, const clang::Decl*, CXTranslationUnit, clang::SourceRange): Assertion `S && TU && "Invalid arguments!"' failed. gdb says S is null: #3 0x75fc8f72 in __GI___assert_fail (assertion=0x7fff92ad7da6 "S && \"Invalid arguments! (S)\"", file=0x7fff92ad7760 "/git/llvm-project/clang/tools/libclang/CXCursor.cpp", line=129, function=0x7fff92ad7d30 "CXCursor clang::cxcursor::MakeCXCursor(const clang::Stmt*, const clang::Decl*, CXTranslationUnit, clang::SourceRange)") at assert.c:101 #4 0x7fff8d56a73f in clang::cxcursor::MakeCXCursor(clang::Stmt const*, clang::Decl const*, CXTranslationUnitImpl*, clang::SourceRange) (S=0x0, Parent=0x0, TU=0x7fff74057c00, RegionOfInterest=...) at /git/llvm-project/clang/tools/libclang/CXCursor.cpp:129 #5 0x7fff8d4e874d in clang::cxcursor::CursorVisitor::EnqueueWorkList(llvm::SmallVector&, clang::Stmt const*) (this=0x7fff8caae310, WL=..., S=0x0) at /git/llvm-project/clang/tools/libclang/CIndex.cpp:2966 #6 0x7fff8d4e988c in clang::cxcursor::CursorVisitor::Visit(clang::Stmt const*) (this=0x7fff8caae310, S=0x0) at /git/llvm-project/clang/tools/libclang/CIndex.cpp:3194 #7 0x7fff8d4e955e in clang::cxcursor::CursorVisitor::RunVisitorWorkList(llvm::SmallVector&) (this=0x7fff8caae310, WL=...) at /git/llvm-project/clang/tools/libclang/CIndex.cpp:3152 #8 0x7fff8d4e989f in clang::cxcursor::CursorVisitor::Visit(clang::Stmt const*) (this=0x7fff8caae310, S=0x7fff74096938) at /git/llvm-project/clang/tools/libclang/CIndex.cpp:3195 #9 0x7fff8d4dde67 in clang::cxcursor::CursorVisitor::VisitChildren(CXCursor) (this=0x7fff8caae310, Cursor=...) at /git/llvm-project/clang/tools/libclang/CIndex.cpp:514 #10 0x7fff8d4ee64e in clang_visitChildren(CXCursor, CXCursorVisitor, CXClientData) (parent=..., visitor=0x7fffa8f11ba0 <(anonymous namespace)::visitCursor(CXCursor, CXCursor, CXClientData)>, client_data=0x7fff8cab08d0) at /git/llvm-project/clang/tools/libclang/CIndex.cpp:4389 #11 0x7fffa8f12676 in (anonymous namespace)::Visitor::buildCompoundStatement<(CXCursorKind)144> (cursor=..., this=0x7fff8cab08d0) at /usr/lib/gcc/x86_64-pc-linux-gnu/9.2.0/include/g++-v9/bits/move.h:99 #12 (anonymous namespace)::visitCursor(CXCursor, CXCursor, CXClientData) (cursor=..., parent=..., data=0x7fff8cab08d0) at /var/tmp/portage/dev-util/kdevelop-5.5.0/work/kdevelop-5.5.0/plugins/clang/duchain/builder.cpp:1587 #13 0x7fff8d4e8de9 in clang::cxcursor::CursorVisitor::RunVisitorWorkList(llvm::SmallVector&) (this=0x7fff8caaefb0, WL=...) at /git/llvm-project/clang/tools/libclang/CIndex.cpp:3052 #14 0x7fff8d4e989f in clang::cxcursor::CursorVisitor::Visit(clang::Stmt const*) (this=0x7fff8caaefb0, S=0x7fff74096ad8) at /git/llvm-project/clang/tools/libclang/CIndex.cpp:3195 #15 0x7fff8d4dde04 in clang::cxcursor::CursorVisitor::VisitChildren(CXCursor) (this=0x7fff8caaefb0, Cursor=...) at /git/llvm-project/clang/tools/libclang/CIndex.cpp:507 #16 0x7fff8d4ee64e in clang_visitChildren(CXCursor, CXCursorVisitor, CXClientData) (parent=..., visitor=0x7fffa8f11ba0 <(anonymous namespace)::visitCursor(CXCursor, CXCursor, CXClientData)>, client_data=0x7fff8cab08d0) at /git/llvm-project/clang/tools/libclang/CIndex.cpp:4389 #17 0x7fffa8f1627b in (anonymous namespace)::Visitor::buildCompoundStatement<(CXCursorKind)202> (cursor=..., this=0x7fff8cab08d0) at /usr/lib/gcc/x86_64-pc-linux-gnu/9.2.0/include/g++-v9/bits/move.h:99 #18 (anonymous namespace)::visitCursor(CXCursor, CXCursor, CXClientData) (cursor=..., parent=..., data=0x7fff8cab08d0) at /var/tmp/portage/dev-util/kdevelop-5.5.0/work/kdevelop-5.5.0/plugins/clang/duchain/builder.cpp:1585 #19 0x7fff8d4dcde8 in clang::cxcursor::CursorVisitor::Visit(CXCursor, bool) (this=0x7fff8caafa70, Cursor=..., CheckedRegionOfInterest=false) at /git/llvm-project/clang/tools/libclang/CIndex.cpp:213 #20 0x7fff8d4df799 in clang::cxcursor::CursorVisitor::VisitFunctionDecl(clang::FunctionDecl*) (this=0x7fff8caafa70, ND=0x7fff740962d8) at /git/llvm-project/clang/tools/libclang/CIndex.cpp:885 #21 0x7fff8d5207f4 in clang::declvisitor::Base::Visit(clang::Decl*) (this=0x7fff8caafa70, D=0x7fff740962d8) at /git/llvm-project/build/tools/clang/include/clang/AST/DeclNodes.inc:395 #22 0x7fff8d4ddd9a in clang::cxcursor::CursorVisitor::VisitChildren(CXCursor) (this=0x7fff8caafa70, Cursor=...) at /git/llvm-project/clang/tools/libclang/CIndex.cpp:502 #23 0x7fff8d4ee64e in clang_visitChildren(CXCursor, CXCursorVisitor, CXClientData) (parent=..., visitor=0x7fffa8f11ba0 <(a
[kdevelop] [Bug 417971] Kdevelop crashes during autocomplete
https://bugs.kde.org/show_bug.cgi?id=417971
Cyp changed:
What|Removed |Added
CC||cyp...@gmail.com
--- Comment #2 from Cyp ---
I got the same crash backtrace with the same kdevelop version.
The crash seems 100% reproducible if opening a file with the following reduced
testcase in kdevelop, or typing it manually:
void a(int b) { int c[b]; [&] { c
The crash may be related to using variable-length arrays from lambda functions.
--
You are receiving this mail because:
You are watching all bug changes.
[kdevelop] [Bug 414499] kdevelop-5.4.2 crash in KDevelop::AbstractDeclarationNavigationContext::declarationSizeInformation
https://bugs.kde.org/show_bug.cgi?id=414499 Cyp changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from Cyp --- Updated to 5.4.4, and seems to be working now. Was probably fixed by https://cgit.kde.org/kdevelop.git/commit/?id=f81d8884bd27c9a48717000a50cdd9cc7050685b -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 414499] New: kdevelop-5.4.2 crash in KDevelop::AbstractDeclarationNavigationContext::declarationSizeInformation
https://bugs.kde.org/show_bug.cgi?id=414499
Bug ID: 414499
Summary: kdevelop-5.4.2 crash in
KDevelop::AbstractDeclarationNavigationContext::declar
ationSizeInformation
Product: kdevelop
Version: 5.4.2
Platform: Gentoo Packages
OS: Linux
Status: REPORTED
Severity: crash
Priority: NOR
Component: Code completion
Assignee: kdevelop-bugs-n...@kde.org
Reporter: cyp...@gmail.com
Target Milestone: ---
Kdevelop-5.4.2 crashes when hovering over “SDL_SysWMmsg” in
/usr/include/SDL2/SDL_events.h.
(gdb) bt full
#0 0x752a7c8e in QMutexLocker::QMutexLocker(QBasicMutex*)
(m=0x7fffc5c3c020, this=) at
/usr/include/qt5/QtCore/qmutex.h:206
d = 0x7fffc5c3c010
lock = {val = 140736511328288}
item = {id = { = {},
m_index = 32767}, centralFreeItem = 1049121280, declarationsData = 3671106195}
index =
#1 0x752a7c8e in
KDevelop::PersistentSymbolTable::declarations(KDevelop::IndexedQualifiedIdentifier
const&) const (this=this@entry=0x75fd8b48
, id=...)
at
/var/tmp/portage/dev-util/kdevelop-5.4.2/work/kdevelop-5.4.2/kdevplatform/language/duchain/persistentsymboltable.cpp:374
d = 0x7fffc5c3c010
lock = {val = 140736511328288}
item = {id = { = {},
m_index = 32767}, centralFreeItem = 1049121280, declarationsData = 3671106195}
index =
#2 0x752a7ee3 in
KDevelop::PersistentSymbolTable::filteredDeclarations(KDevelop::IndexedQualifiedIdentifier
const&, Utils::StorableSet const&) const
(this=this@entry=0x75fd8b48 ,
id=..., visibility=...)
at
/var/tmp/portage/dev-util/kdevelop-5.4.2/work/kdevelop-5.4.2/kdevplatform/language/duchain/persistentsymboltable.cpp:326
d = 0x7fffc5c3c010
lock = {val = 140736511328289}
decls =
cachedImports = { = {}, m_setIndex = 32767}
it =
#3 0x752803c7 in
KDevelop::DeclarationId::declaration(KDevelop::TopDUContext const*, bool) const
(this=0x7fff88e962b2, top=top@entry=0x56f5ec50,
instantiateIfRequired=instantiateIfRequired@entry=true)
at
/var/tmp/portage/dev-util/kdevelop-5.4.2/work/kdevelop-5.4.2/kdevplatform/language/duchain/declarationid.cpp:164
filter =
{> =
{> = {m_data = 0x75fd8cd8
,
m_dataSize = 2, m_centralFreeItem = -1}, m_pos = 4286577264}, boundStack =
{,
Utils::VirtualSetNode >, 256>> = {a = -8390016, s = 32767,
ptr = 0x75fd8cd8
,
{array =
"\270\372\177\377\377\177\000\000У\tWUU\000\000У\tWUU\000\000\200\372\177\377\377\177\000\000\261^3\365\377\177\000\000\220\243\tWUU\000\000\262b\351\210\377\177\000\000\000\000\000\000\000\000\000\000\301\004(\365\377\177\000\000\226F\277\305\377\177\000\000P\354\365VUU\000\000!\300\303\305\001\000\000\000p\372\177\377\377\177\000\000\n\224\024\000\000\000\000\000R5V\320\377\177\000\000Ԗ\001\000\377\177\000\000\300\214\375\365\377\177\000\000
\316\330ZUU\000\000\002\000\000\000\377\377\377\377\000\000\000\000\377\177\000\000\000\001\000\000\000\000\000\000\270\372\177\377\377\177\000\000\000\000\000\000\001\000\000\000\224lCVUU\000\000У\tWUU\000\000\060\373\177\377\377"...,
q_for_alignment_1 = 140737479965368, q_for_alignment_2 =
6.9533553933159037e-310}}, }, m_rhs =
{ = {},
m_setIndex = 4131779782}, m_match = 32767, m_matchBound = 1518934160,
m_matchingTo = {m_index = 21845}, m_noFiltering = 32}
id = {m_index = 1348618, {dd = 0x7fffd0563552, cd = 0x7fffd0563552}}
ret = 0x0
#4 0x752ced6b in
KDevelop::IdentifiedType::declaration(KDevelop::TopDUContext const*) const
(this=, top=top@entry=0x56f5ec50)
at
/var/tmp/portage/dev-util/kdevelop-5.4.2/work/kdevelop-5.4.2/kdevplatform/language/duchain/types/identifiedtype.cpp:75
#5 0x752f3112 in
KDevelop::AbstractDeclarationNavigationContext::declarationSizeInformation(KDevelop::DUChainPointer
const&, KDevelop::TopDUContext const*)
(decl=..., topContext=0x56f5ec50) at
/var/tmp/portage/dev-util/kdevelop-5.4.2/work/kdevelop-5.4.2/kdevplatform/language/duchain/navigation/abstractdeclarationnavigationcontext.cpp:871
idType =
type = {> = {d =
0x5a891890}, }
memberDecl =
#6 0x752f316e in
KDevelop::AbstractDeclarationNavigationContext::declarationSizeInformation(KDevelop::DUChainPointer
const&, KDevelop::TopDUContext const*)
(decl=..., topContext=0x56f5ec50) at
/usr/lib/gcc/x86_64-pc-linux-gnu/8.3.0/include/g++-v8/bits/atomic_base.h:303
idType =
type = {> = {d =
0x5a891ba0}, }
memberDecl =
#7 0x752f316e in
KDevelop::AbstractDeclarationNavigationContext::declarationSizeInformation(KDevelop::DUChainPointer
const&, KDevelop::TopDUContext const*)
(decl=..., topContext=0x56f5ec50) at
/usr/lib/gcc/x86_64-pc-linux-gnu/8.3.0/include/g++-v8/bits/atomic_base.h:303
idType =
[kdevelop] [Bug 411549] Text silently erased after selecting text, navigating via tooltips and typing somewhere else
https://bugs.kde.org/show_bug.cgi?id=411549
--- Comment #1 from Cyp ---
Note that the original similar problem was that when changing "func();" to
"func(h);", that somehow made "void Class::func(bool var) {" elsewhere in the
file change to "void Class::(bool var) {". I'm not sure how to reproduce that
exact case though, since I don't see a way of directly navigating inside the
"()" of "func();" via a tooltip.
--
You are receiving this mail because:
You are watching all bug changes.
[kdevelop] [Bug 411549] New: Text silently erased after selecting text, navigating via tooltips and typing somewhere else
https://bugs.kde.org/show_bug.cgi?id=411549 Bug ID: 411549 Summary: Text silently erased after selecting text, navigating via tooltips and typing somewhere else Product: kdevelop Version: 5.3.2 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: All editors Assignee: kdevelop-bugs-n...@kde.org Reporter: cyp...@gmail.com Target Milestone: --- Independently reproduced on 5.4.2 and KF 5.61. Text silently erased after selecting text, navigating via tooltips and typing somewhere else. This can result in mysterious compilation errors later or even silently introduce bugs in edited code. STEPS TO REPRODUCE 1. Select any text. 2. Hover over a function name, and navigate via the tooltip to the function definition (in the same file). 3. Start typing (without moving the cursor) at the new location. OBSERVED RESULT 2½. Cursor is blinking at the navigated-to location, but the previously-selected text is still selected. 3½. Selected text is silently erased (even if not on the screen when typing). EXPECTED RESULT 2½. Cursor blinking in one location is inconsistent with text being selected. 3½. No text erased. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 5.57.0 KDE Frameworks Version: 5.57.0 Qt Version: 5.12.3 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 353370] RDRAND amd64->IR: unhandled instruction bytes: 0x48 0xF 0xC7 0xF0 0x72 0x4 0xFF 0xC9
https://bugs.kde.org/show_bug.cgi?id=353370 --- Comment #29 from Cyp --- It is now. And seems to work, thanks. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 353370] RDRAND amd64->IR: unhandled instruction bytes: 0x48 0xF 0xC7 0xF0 0x72 0x4 0xFF 0xC9
https://bugs.kde.org/show_bug.cgi?id=353370 Cyp changed: What|Removed |Added CC||cyp...@gmail.com --- Comment #23 from Cyp --- I'm seeing this with valgrind-3.15.0, even though the release notes say RdRand is now supported. The system is compiled with -march=native on an “Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz”. -- $ valgrind scribus ==26338== Memcheck, a memory error detector ==26338== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. ==26338== Using Valgrind-3.15.0 and LibVEX; rerun with -h for copyright info ==26338== Command: scribus ==26338== vex amd64->IR: unhandled instruction bytes: 0xF 0xC7 0xF0 0xB9 0x1 0x0 0x0 0x0 0x89 0x3 vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0 vex amd64->IR: VEX=0 VEX.L=0 VEX.n=0x0 ESC=0F vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0 ==26338== valgrind: Unrecognised instruction at address 0x8769603. ==26338==at 0x8769603: _rdrand32_step (immintrin.h:138) ==26338==by 0x8769603: qt_random_cpu (qrandom.cpp:114) ==26338==by 0x8769603: QRandomGenerator::SystemGenerator::generate(unsigned int*, unsigned int*) (qrandom.cpp:370) ==26338==by 0x87BC11A: fillRange (qrandom.h:143) ==26338==by 0x87BC11A: generate (qrandom.h:87) ==26338==by 0x87BC11A: qt_create_qhash_seed() (qhash.cpp:299) ==26338==by 0x87BC1D4: qt_initialize_qhash_seed (qhash.cpp:325) ==26338==by 0x87BC1D4: qt_initialize_qhash_seed() (qhash.cpp:322) ==26338==by 0x87BC7C9: QHashData::detach_helper(void (*)(QHashData::Node*, void*), void (*)(QHashData::Node*), int, int) (qhash.cpp:502) ==26338==by 0x87CFDB9: QHash::Node>::detach_helper() [clone .isra.191] (qhash.h:599) ==26338==by 0x87D5FFB: detach (qhash.h:275) ==26338==by 0x87D5FFB: find (qhash.h:901) ==26338==by 0x87D5FFB: take (qcache.h:154) ==26338==by 0x87D5FFB: prepareEngine_helper(QRegExpPrivate*) (qregexp.cpp:3853) … -- http://www.valgrind.org/docs/manual/dist.news.html Release 3.15.0 (12 April 2019) * amd64 (x86_64): the RDRAND and F16C insn set extensions are now supported. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 403059] shrinking size of tabs
https://bugs.kde.org/show_bug.cgi?id=403059 --- Comment #10 from Cyp --- Seems to help — now up to 24 tabs can squash to fit, like before. However, with 25 or more tabs, it makes the window wider than the screen (which is 1920 pixels wide), though. I note that it's possible to scroll in the tabs with Ctrl+(Shift+)Tab, but the order seems random. Shift+Left/Right still works normally. (In reply to tcanabrava from comment #9) > https://phabricator.kde.org/D21316 > > can you guys test and see if it helps? -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 403059] shrinking size of tabs
https://bugs.kde.org/show_bug.cgi?id=403059 --- Comment #6 from Cyp --- Having all tabs always on the screen at once with each at a fixed position can be more useful than having meaningful information, at least for some users. It's like having multiple desktops, where you know which you want to use at any time, even though it's just a grid of squares without meaningful information. If having 20 tabs in the same directory, it's hard to come up with any kind of meaningful information for them other than their order, anyway. Maybe it would be useful to have a way of adding separators between tabs, to make it easy to group tabs by category. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 403059] shrinking size of tabs
https://bugs.kde.org/show_bug.cgi?id=403059
Cyp changed:
What|Removed |Added
CC||cyp...@gmail.com
--- Comment #4 from Cyp ---
Tried calling setUsesScrollButtons(false), which made the scroll arrows
disappear, but made the window wider than the screen instead of making the tabs
narrower.
Suggestion from IRC is to use style sheets — a workaround is to create a file
containing this, and set it as a style sheet in Settings/Configure
Konsole/TabBar:
> QTabBar::tab {
> width: 100px;
> }
--
You are receiving this mail because:
You are watching all bug changes.
[konsole] [Bug 403130] Strange-looking horizontal stripe in konsole when find bar is open
https://bugs.kde.org/show_bug.cgi?id=403130 --- Comment #1 from Cyp --- Created attachment 117415 --> https://bugs.kde.org/attachment.cgi?id=117415=edit screenshot -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 403130] New: Strange-looking horizontal stripe in konsole when find bar is open
https://bugs.kde.org/show_bug.cgi?id=403130 Bug ID: 403130 Summary: Strange-looking horizontal stripe in konsole when find bar is open Product: konsole Version: 18.08.3 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: font Assignee: konsole-de...@kde.org Reporter: cyp...@gmail.com Target Milestone: --- SUMMARY Strange-looking horizontal stripe in konsole when find bar is open STEPS TO REPRODUCE 1. Put some text in konsole (probably most obvious with lots of '|') 2. Press Ctrl+Shift+F to open the find bar. 3. Switch to another window and optionally switch back (doesn't have to be covering the konsole window). OBSERVED RESULT A strange-looking horizontal stripe meeting at the bottom of the find bar. EXPECTED RESULT No strange-looking horizontal stripe meeting at the bottom of the find bar. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 5.14.3 KDE Frameworks Version: 5.52.0 Qt Version: 5.11.1 ADDITIONAL INFORMATION for (( x = 0; x < 1000; ++x)) ; do echo -n '||' ; done -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 392357] kalarm thrashes hard drive forever
https://bugs.kde.org/show_bug.cgi?id=392357 --- Comment #4 from Cyp --- Configuring kalarm to not start on startup doesn't help. Even uninstalling kalarm completely doesn't help! Seems kde-apps/kdepim-runtime spawns the akonadi_kalarm_resource processes even if kalarm is uninstalled. Not sure if uninstalling kdepim_runtime is a good idea, since it sounds like it's responsible for lots of stuff, and I don't know if it does anything important. -- You are receiving this mail because: You are watching all bug changes.
[kmplot] [Bug 400445] New: Checking/unchecking equation has no effect unless equation selected, in kmplot
https://bugs.kde.org/show_bug.cgi?id=400445 Bug ID: 400445 Summary: Checking/unchecking equation has no effect unless equation selected, in kmplot Product: kmplot Version: unspecified Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: cf...@kde.org Reporter: cyp...@gmail.com Target Milestone: --- SUMMARY Checking/unchecking an equation has no effect unless the equation is currently selected. STEPS TO REPRODUCE 1. Create two equations (cartesian plots). 2. Uncheck the equations. 3. Select the other equation. OBSERVED RESULT Only the plot of the selected equation is hidden when unchecking it. When selecting the other equation, it checks/unchecks itself, going back to the state it had when it was last selected. EXPECTED RESULT Something different. SOFTWARE VERSIONS kde-apps/kmplot-18.04.3 kde-frameworks/plasma-5.50.0 kde-frameworks/frameworkintegration-5.50.0 dev-qt/qtgui-5.11.1 ADDITIONAL INFORMATION 42 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 396876] New: Generated function definitions should exactly match declarations in headers
https://bugs.kde.org/show_bug.cgi?id=396876
Bug ID: 396876
Summary: Generated function definitions should exactly match
declarations in headers
Product: kdevelop
Version: 5.2.1
Platform: Other
OS: All
Status: UNCONFIRMED
Severity: wishlist
Priority: NOR
Component: Code completion
Assignee: kdevelop-bugs-n...@kde.org
Reporter: cyp...@gmail.com
Target Milestone: ---
If a header contains a declaration
myFunc(char const *str);
then autogenerating the definition in the source file creates
myFunc(const char *str)
{
}
. I think it would be better if the generated signature exactly matched the
header, even if "char const" and "const char" are equivalent.
Also, it would be nice if it were possible to set the { to appear on the same
line as the ).
--
You are receiving this mail because:
You are watching all bug changes.
[kate] [Bug 393633] New: kwrite javascript syntax highlighting incorrectly displays as regex
https://bugs.kde.org/show_bug.cgi?id=393633 Bug ID: 393633 Summary: kwrite javascript syntax highlighting incorrectly displays as regex Product: kate Version: 17.12.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: syntax Assignee: kwrite-bugs-n...@kde.org Reporter: cyp...@gmail.com Target Milestone: --- Created attachment 112304 --> https://bugs.kde.org/attachment.cgi?id=112304=edit screenshot of testcase Using javascript syntax highlighting and dividing an identifier ending in a non-ascii character by something, the / is interpreted as the start of a regex. Testcase, the / in δ/113 is interpreted as the start of a regex: let regex = /hello.*(world|universe)?/; let i = 22; let j = i/7; let δ = 355; let k = δ/113; let m = 42; let regex2 = /hello.*(world|universe)?/; let ouch = true; -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 393129] New: Red underline in kdevelop+kwrite on valid numerical constants (with invalid octal substrings)
https://bugs.kde.org/show_bug.cgi?id=393129 Bug ID: 393129 Summary: Red underline in kdevelop+kwrite on valid numerical constants (with invalid octal substrings) Product: kdevelop Version: 5.2.1 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: All editors Assignee: kdevelop-bugs-n...@kde.org Reporter: cyp...@gmail.com Target Milestone: --- If typing "-1.09" (without the quotes), the "09" appears red and underlined. Seems as if anything matching /[-+][0-9]+/ causes number parsing to stop at the end of the pattern. Red/underlined after the black dot: -0.09 -1.08 -1.09 +1.09 -1.012345678 Anything matching /[-+][0-9]+\.0[0-7]*[89]/ Red/underlined before the black dot: -09.0 +09.0 Entire number red, except dot is black if present: -08.08 -1e3 +1e3 -1e1f 1f (invalid) Not red/underlined, but dot is black: -1.90 +1.90 -1.01234567 -1.09e1 -3.١٤١٥٩e1 (invalid) Not red/underlined, and dot is yellowish orange-brown like the rest of the number: 1.09 - 1.09 -.09 09.0 08.08 1e3 1e1f 3.١٤١٥٩e1 (invalid) ٣.١٤١٥٩ (invalid) -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 392357] kalarm thrashes hard drive forever
https://bugs.kde.org/show_bug.cgi?id=392357
--- Comment #2 from Cyp <cyp...@gmail.com> ---
Looking at the source for anything obvious, I suspect
https://github.com/KDE/akonadi/blob/master/src/core/models/entityorderproxymodel.cpp#L110
should have something like this added:
const int rightPosition = list.indexOf(rightValue);
+if ((leftPosition < 0) != (rightPosition < 0)) {
+return (leftPosition < 0) < (rightPosition < 0);
+}
+
if (leftPosition < 0 || rightPosition < 0) {
Otherwise the sort comparison function is inconsistent if at least on item has
position < 0 and at least two items don't (possibly leading to A < B, B < C and
C < A).
Although I don't really think it's very likely to fix this particular issue
(unless the alarms are sorted by some key which is partially in a list), and
not sure how to test.
--
You are receiving this mail because:
You are watching all bug changes.
[kalarm] [Bug 392357] New: kalarm thrashes hard drive forever
https://bugs.kde.org/show_bug.cgi?id=392357 Bug ID: 392357 Summary: kalarm thrashes hard drive forever Product: kalarm Version: unspecified Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Akonadi Assignee: djar...@kde.org Reporter: cyp...@gmail.com Target Milestone: --- I have kde-apps/kalarm-17.08.3, but that version isn't listed in the version multiple choice box. I don't remember exactly when the problem started, but it might have been some versions ago. On logging in, kalarm thrashes the hard drive until stopping it by running `killall -v -9 akonadi_kalarm_resource` a few times until all threads are dead. While today I didn't see it, another time I saw it shuffling the alarms a few times per second until killing akonadi_kalarm_resource. It's possible that only alarms which were set for the same time as each other were being shuffled with each other. Also, when logging in, kalarm often pops up lots of old alarms that have previously been dismissed. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 391742] Crash on pressing Enter (kdevelop and kwrite)
https://bugs.kde.org/show_bug.cgi?id=391742 --- Comment #2 from Cyp <cyp...@gmail.com> --- (In reply to Cyp from comment #1) > Now started updating to frameworks 5.43.0, since it's available now in Gentoo. Still crashing after updating to frameworks 5.43.0 and pressing the clear cache button that appears when kdevelop crashes. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 391742] Crash on pressing Enter (kdevelop and kwrite)
https://bugs.kde.org/show_bug.cgi?id=391742 --- Comment #1 from Cyp <cyp...@gmail.com> --- Apparently also crashes if double-clicking on the autocomplete thing instead of pressing Enter. Now started updating to frameworks 5.43.0, since it's available now in Gentoo. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 391742] New: Crash on pressing Enter (kdevelop and kwrite)
https://bugs.kde.org/show_bug.cgi?id=391742 Bug ID: 391742 Summary: Crash on pressing Enter (kdevelop and kwrite) Product: kdevelop Version: 5.2.1 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: All editors Assignee: kdevelop-bugs-n...@kde.org Reporter: cyp...@gmail.com Target Milestone: --- After clicking to submit this with drkonqi, it said my login wasn't valid, even though it had just validated my login on an earlier screen. Submitting manually. Application: kdevelop (5.2.1) Qt Version: 5.7.1 Frameworks Version: 5.40.0 Operating System: Linux 4.14.13-gentoo x86_64 Distribution: "Gentoo Base System release 2.4.1" -- Information about the crash: - What I was doing when the application crashed: I pressed Enter in kdevelop, trying to accept an autocomplete suggestion. Have also had crashes in kwrite recently (since last updating) when pressing Enter, but not trying to accept any autocomplete suggestions. I'm guessing it's the same issue. If restarting kdevelop (or kwrite) and pressing Enter in the same place without editing too much, it sometimes crashes consistently. The crash can be reproduced sometimes. -- Backtrace: Application: KDevelop (kdevelop), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f152a655780 (LWP 12500))] Thread 17 (Thread 0x7f14bd7fa700 (LWP 12539)): #0 0x7f153bcbe8e3 in futex_reltimed_wait_cancelable (private=, reltime=0x7f14bd7f9ce0, expected=0, futex_word=0x55e131e82d64) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 __pthread_cond_wait_common (abstime=0x7f14bd7f9d90, mutex=0x55e131e82d10, cond=0x55e131e82d38) at pthread_cond_wait.c:533 #2 __pthread_cond_timedwait (cond=0x55e131e82d38, mutex=0x55e131e82d10, abstime=0x7f14bd7f9d90) at pthread_cond_wait.c:667 #3 0x7f15427bae78 in QWaitConditionPrivate::wait_relative (time=3, this=0x55e131e82d10) at thread/qwaitcondition_unix.cpp:133 #4 QWaitConditionPrivate::wait (time=3, this=0x55e131e82d10) at thread/qwaitcondition_unix.cpp:141 #5 QWaitCondition::wait (this=this@entry=0x55e131e823a0, mutex=mutex@entry=0x55e131e82ab0, time=3) at thread/qwaitcondition_unix.cpp:215 #6 0x7f15427b78dd in QThreadPoolThread::run (this=0x55e131e82390) at thread/qthreadpool.cpp:133 #7 0x7f15427ba83c in QThreadPrivate::start (arg=0x55e131e82390) at thread/qthread_unix.cpp:368 #8 0x7f153bcb7677 in start_thread (arg=0x7f14bd7fa700) at pthread_create.c:456 #9 0x7f1542056c2f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:97 Thread 16 (Thread 0x7f14beffd700 (LWP 12536)): #0 0x7f154204728d in read () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f1539d97bc0 in read (__nbytes=16, __buf=0x7f14beffcbf0, __fd=) at /usr/include/bits/unistd.h:44 #2 g_wakeup_acknowledge (wakeup=0x7f14b8002730) at /var/tmp/portage/dev-libs/glib-2.52.3/work/glib-2.52.3/glib/gwakeup.c:210 #3 0x7f1539d5328e in g_main_context_check (context=context@entry=0x7f14b4000990, max_priority=2147483647, fds=fds@entry=0x7f14b40013c0, n_fds=n_fds@entry=1) at /var/tmp/portage/dev-libs/glib-2.52.3/work/glib-2.52.3/glib/gmain.c:3750 #4 0x7f1539d53764 in g_main_context_iterate (context=context@entry=0x7f14b4000990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /var/tmp/portage/dev-libs/glib-2.52.3/work/glib-2.52.3/glib/gmain.c:3969 #5 0x7f1539d538dc in g_main_context_iteration (context=0x7f14b4000990, may_block=may_block@entry=1) at /var/tmp/portage/dev-libs/glib-2.52.3/work/glib-2.52.3/glib/gmain.c:4033 #6 0x7f154299e05b in QEventDispatcherGlib::processEvents (this=0x7f14b40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #7 0x7f154294f40a in QEventLoop::exec (this=this@entry=0x7f14beffce10, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #8 0x7f15427b6513 in QThread::exec (this=this@entry=0x55e131cf7d30) at thread/qthread.cpp:507 #9 0x7f14ce023825 in QQuickXmlQueryEngine::run (this=0x55e131cf7d30) at qqmlxmllistmodel.cpp:323 #10 0x7f15427ba83c in QThreadPrivate::start (arg=0x55e131cf7d30) at thread/qthread_unix.cpp:368 #11 0x7f153bcb7677 in start_thread (arg=0x7f14beffd700) at pthread_create.c:456 #12 0x7f1542056c2f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:97 Thread 15 (Thread 0x7f14b700 (LWP 12534)): #0 0x7f153bcbe4d6 in futex_wait_cancelable (private=, expected=0, futex_word=0x55e12db3bf84) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x55e12db3bf30, cond=0x55e12db3bf58) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x55e12db3bf58, mutex=0x55e12db3bf30) at pthread_cond_wait.c:655 #3 0x7f15427bae9a in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x55e
