[KPipeWire] [Bug 492844] VP9 encoding is not GPU accelerated
https://bugs.kde.org/show_bug.cgi?id=492844 --- Comment #2 from Francis John Baldon --- After using libva-intel-driver for days, I'm not sure now if the bug is caused by Spectacle solely. As I've noticed, even chromium now doesn't do vp9 decoding, so this might be a driver issue. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 492844] New: VP9 encoding not working
https://bugs.kde.org/show_bug.cgi?id=492844 Bug ID: 492844 Summary: VP9 encoding not working Classification: Applications Product: Spectacle Version: 24.08.0 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: noaha...@gmail.com Reporter: fjbal...@tuta.io CC: k...@david-redondo.de Target Milestone: --- Created attachment 173459 --> https://bugs.kde.org/attachment.cgi?id=173459&action=edit output from vainfo SUMMARY Attached is an output from vainfo. I'm having high cpu usage when I do webm/vp9 screen recording on spectacle. The default format is webm/vp9 and when I switch to mp4/h.264, cpu usage drastically decreases. I'm also seeing activity on the Video row when I'm using mp4/h.264 but nothing on webm/vp9. I have this line on my vainfo output so I assume I can encode vp9 on my igpu: "VAProfileVP9Profile0: VAEntrypointEncSlice" STEPS TO REPRODUCE 1. Screen record using Spectacle (Wayland) 2. Use System Monitor or intel_gpu_top to monitor cpu and gpu usage 3. Spectacle does not offload its encoding to the gpu, instead it uses only the cpu OBSERVED RESULT Spectacle does not use the gpu when encoding the video EXPECTED RESULT Spectacle uses the gpu when encoding the video SOFTWARE/OS VERSIONS Windows: macOS: (available in the Info Center app, or by running `kinfo` in a terminal window) Linux/KDE Plasma: Fedora Linux 40 KDE Plasma Version: 6.1.4 KDE Frameworks Version: 6.5.0 Qt Version: 6.7.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 487225] Plasma Shell Crashes for no reason
https://bugs.kde.org/show_bug.cgi?id=487225 --- Comment #3 from Francis Greaves --- Thanks for the quick response, I have reported this to MESA here https://gitlab.freedesktop.org/mesa/mesa/-/issues/11191 Regards -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 487225] Plasma Shell Crashes for no reason
https://bugs.kde.org/show_bug.cgi?id=487225 --- Comment #1 from Francis Greaves --- Created attachment 169610 --> https://bugs.kde.org/attachment.cgi?id=169610&action=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 487225] New: Plasma Shell Crashes for no reason
https://bugs.kde.org/show_bug.cgi?id=487225 Bug ID: 487225 Summary: Plasma Shell Crashes for no reason Classification: Plasma Product: plasmashell Version: 5.27.11 Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: themet...@themetman.net CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Application: plasmashell (5.27.11) (Compiled from sources) Qt Version: 5.15.13 Frameworks Version: 5.115.0 Operating System: Linux 6.8.9-gentoo-x86_64 x86_64 Windowing System: X11 Distribution: "Gentoo Linux" DrKonqi: 5.27.11 [KCrashBackend] -- Information about the crash: Scrolling a web page in Brave. Nothing opened recently The reporter is unsure if this crash is reproducible. -- Backtrace (Reduced): #5 0x7f91859f49f0 in ??? () at /usr/lib64/dri/radeonsi_dri.so #6 0x7f91855ffd81 in ??? () at /usr/lib64/dri/radeonsi_dri.so #7 0x7f9185600678 in ??? () at /usr/lib64/dri/radeonsi_dri.so #8 0x7f91856057e2 in ??? () at /usr/lib64/dri/radeonsi_dri.so #9 0x7f9185493470 in ??? () at /usr/lib64/dri/radeonsi_dri.so The reporter indicates this bug may be a duplicate of or related to bug 486665. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 486945] New: System Settings Crashed and Task Bar Disappeared
https://bugs.kde.org/show_bug.cgi?id=486945 Bug ID: 486945 Summary: System Settings Crashed and Task Bar Disappeared Classification: Applications Product: systemsettings Version: 5.27.11 Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: themet...@themetman.net Target Milestone: --- Application: systemsettings (5.27.11) (Compiled from sources) Qt Version: 5.15.13 Frameworks Version: 5.115.0 Operating System: Linux 6.8.9-gentoo-x86_64 x86_64 Windowing System: X11 Distribution: "Gentoo Linux" DrKonqi: 5.27.11 [KCrashBackend] -- Information about the crash: Opened System Settings and This crashed and Task Bar Disappeared The reporter is unsure if this crash is reproducible. -- Backtrace: Application: System Settings (systemsettings), signal: Bus error [KCrash Handler] #4 0x7fb5df377087 in ?? () from /lib64/libc.so.6 #5 0x7fb5d31f4d40 in ?? () from /usr/lib64/dri/radeonsi_dri.so #6 0x7fb5d2dffd81 in ?? () from /usr/lib64/dri/radeonsi_dri.so #7 0x7fb5d2e00678 in ?? () from /usr/lib64/dri/radeonsi_dri.so #8 0x7fb5d2e057e2 in ?? () from /usr/lib64/dri/radeonsi_dri.so #9 0x7fb5d2c93470 in ?? () from /usr/lib64/dri/radeonsi_dri.so #10 0x7fb5d2c91ef2 in ?? () from /usr/lib64/dri/radeonsi_dri.so #11 0x7fb5d2c92524 in ?? () from /usr/lib64/dri/radeonsi_dri.so #12 0x7fb5d2da92d7 in ?? () from /usr/lib64/dri/radeonsi_dri.so #13 0x7fb5ddd5fbcf in QSGBatchRenderer::Renderer::unmap(QSGBatchRenderer::Buffer*, bool) () from /usr/lib64/libQt5Quick.so.5 #14 0x7fb5ddd61a03 in QSGBatchRenderer::Renderer::uploadBatch(QSGBatchRenderer::Batch*) () from /usr/lib64/libQt5Quick.so.5 #15 0x7fb5ddd73ba5 in QSGBatchRenderer::Renderer::render() () from /usr/lib64/libQt5Quick.so.5 #16 0x7fb5ddd5b0c9 in QSGRenderer::renderScene(QSGBindable const&) () from /usr/lib64/libQt5Quick.so.5 #17 0x7fb5ddd5b59b in QSGRenderer::renderScene(unsigned int) () from /usr/lib64/libQt5Quick.so.5 #18 0x7fb5dddc0d17 in QSGDefaultRenderContext::renderNextFrame(QSGRenderer*, unsigned int) () from /usr/lib64/libQt5Quick.so.5 #19 0x7fb5dde34c79 in QQuickWindowPrivate::renderSceneGraph(QSize const&, QSize const&) () from /usr/lib64/libQt5Quick.so.5 #20 0x7fb5ddec90ab in QQuickRenderControl::render() () from /usr/lib64/libQt5Quick.so.5 #21 0x7fb5de9bf311 in ?? () from /usr/lib64/libQt5QuickWidgets.so.5 #22 0x7fb5e07484d2 in QWidget::event(QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #23 0x7fb5e07031f6 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #24 0x7fb5dfa87308 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib64/libQt5Core.so.5 #25 0x7fb5e073fc3e in QWidgetPrivate::sendPendingMoveAndResizeEvents(bool, bool) () from /usr/lib64/libQt5Widgets.so.5 #26 0x7fb5e07448c7 in QWidgetPrivate::show_helper() () from /usr/lib64/libQt5Widgets.so.5 #27 0x7fb5e0747933 in QWidgetPrivate::setVisible(bool) () from /usr/lib64/libQt5Widgets.so.5 #28 0x7fb5e0744849 in QWidgetPrivate::showChildren(bool) () from /usr/lib64/libQt5Widgets.so.5 #29 0x7fb5e07448e3 in QWidgetPrivate::show_helper() () from /usr/lib64/libQt5Widgets.so.5 #30 0x7fb5e0747933 in QWidgetPrivate::setVisible(bool) () from /usr/lib64/libQt5Widgets.so.5 #31 0x7fb5e0744849 in QWidgetPrivate::showChildren(bool) () from /usr/lib64/libQt5Widgets.so.5 #32 0x7fb5e07448e3 in QWidgetPrivate::show_helper() () from /usr/lib64/libQt5Widgets.so.5 #33 0x7fb5e0744869 in QWidgetPrivate::showChildren(bool) () from /usr/lib64/libQt5Widgets.so.5 #34 0x7fb5e07448e3 in QWidgetPrivate::show_helper() () from /usr/lib64/libQt5Widgets.so.5 #35 0x7fb5e0747933 in QWidgetPrivate::setVisible(bool) () from /usr/lib64/libQt5Widgets.so.5 #36 0x7fb5e0744849 in QWidgetPrivate::showChildren(bool) () from /usr/lib64/libQt5Widgets.so.5 #37 0x7fb5e07448e3 in QWidgetPrivate::show_helper() () from /usr/lib64/libQt5Widgets.so.5 #38 0x7fb5e0744869 in QWidgetPrivate::showChildren(bool) () from /usr/lib64/libQt5Widgets.so.5 #39 0x7fb5e07448e3 in QWidgetPrivate::show_helper() () from /usr/lib64/libQt5Widgets.so.5 #40 0x7fb5e0744869 in QWidgetPrivate::showChildren(bool) () from /usr/lib64/libQt5Widgets.so.5 #41 0x7fb5e07448e3 in QWidgetPrivate::show_helper() () from /usr/lib64/libQt5Widgets.so.5 #42 0x7fb5e0747933 in QWidgetPrivate::setVisible(bool) () from /usr/lib64/libQt5Widgets.so.5 #43 0x7fb5e0744849 in QWidgetPrivate::showChildren(bool) () from /usr/lib64/libQt5Widgets.so.5 #44 0x7fb5e07448e3 in QWidgetPrivate::show_helper() () from /usr/lib64/libQt5Widgets.so.5 #45 0x7fb5e0744869 in QWidgetPrivate::showChildren(bool) () from /usr/lib64/libQt5Widgets.so.
[kdenlive] [Bug 484393] New: Please, check two screenshots I sent you hereby attached (second report).
https://bugs.kde.org/show_bug.cgi?id=484393 Bug ID: 484393 Summary: Please, check two screenshots I sent you hereby attached (second report). Classification: Applications Product: kdenlive Version: 24.02.0 Platform: Mint (Debian based) OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: francisasi...@gmail.com Target Milestone: --- Created attachment 167706 --> https://bugs.kde.org/attachment.cgi?id=167706&action=edit One of the paths leading to freezing the next opening window SUMMARY As shown in both screenshots (one in this report and the other in the previous report), the mouse pointer is located in the place of the final command before the next opening window in Kdenlive freezes. It forces me to reset my computer. Each of both screenshots shows a different path leading to the same outcome, which is that the next opening window freezes. I am not well-versed in software language, thus I am not able to offer more specific details. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 484392] New: Please, check two screenshots I sent you hereby attached.
https://bugs.kde.org/show_bug.cgi?id=484392 Bug ID: 484392 Summary: Please, check two screenshots I sent you hereby attached. Classification: Applications Product: kdenlive Version: 24.02.0 Platform: Mint (Debian based) OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: francisasi...@gmail.com Target Milestone: --- Created attachment 167705 --> https://bugs.kde.org/attachment.cgi?id=167705&action=edit One of the paths leading to freezing the next opening window SUMMARY As shown in both screenshots (one in this report and the other in the second report), the mouse pointer is located in the place of the final command before the next opening window in Kdenlive freezes. It forces me to reset my computer. Each of both screenshots shows a different path leading to the same outcome, which is that the next opening window freezes. I am not well-versed in software language, thus I am not able to offer more specific details. -- You are receiving this mail because: You are watching all bug changes.
[Craft] [Bug 480007] New: craft kcalc fails to build. CMake directory pointers are wrong. May be related
https://bugs.kde.org/show_bug.cgi?id=480007 Bug ID: 480007 Summary: craft kcalc fails to build. CMake directory pointers are wrong. May be related Classification: Developer tools Product: Craft Version: unspecified Platform: Compiled Sources OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: Core Assignee: vonr...@kde.org Reporter: rich...@gerspatial.com CC: kde-wind...@kde.org Target Milestone: --- Created attachment 165016 --> https://bugs.kde.org/attachment.cgi?id=165016&action=edit CMake output log 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 *** I installed a fresh version of craft on macOS 14.1.1 (Sonoma) using the recipe at https://community.kde.org/Get_Involved/development/Mac. I chose Qt6 and arm64 as options (I'm running on Apple Silicon - a MacBook Pro with Apple M1 Max processor). I have a standard install of Xcode 15.2, and added the command line tools following the above-mentioned recipe. The first test is to build kcalc. This fails as it does not build the executable. A possible connection is with the lines in CMakeOutput.log (attached): ignoring nonexistent directory "/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX14.2.sdk/usr/local/include" ignoring nonexistent directory "/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX14.2.sdk/Library/Frameworks" These do not point to the right place. The actual directory structure is (starting at SDKs) SDKs/MacOSX14.2.sdk/usr/include SDKs/MacOSX14.2.sdk/System/Library/Frameworks and in each case the MacOSX14.2.sdk is an alias to MacOSX.sdk STEPS TO REPRODUCE 1. Install craft on an Apple Silicon machine running macOS14.1.1 following https://community.kde.org/Get_Involved/development/Mac 2. using the default zsh shell, enter the craft environment with: source ~/CraftRoot/craft/craftenv.sh 3. enter craft kcalc OBSERVED RESULT failure to build EXPECTED RESULT built app, according to the recipe mentioned SOFTWARE/OS VERSIONS Windows: macOS: 14.1.1 (Sonoma) Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: 6 ADDITIONAL INFORMATION I seem to only be able to attach one file, so I've attached CMakeOutput.log. There is also CMakeError.log, which I will copy here: --- Compiling the C compiler identification source file "CMakeCCompilerId.c" failed. Compiler: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang Build flags: -fdiagnostics-color=always Id flags: The output was: 1 ld: library 'System' not found clang: ;1;31merror: [0m[1mlinker command failed with exit code 1 (use -v to see invocation)[0m Compiling the CXX compiler identification source file "CMakeCXXCompilerId.cpp" failed. Compiler: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang++ Build flags: Id flags: The output was: 1 ld: library 'c++' not found clang: error: linker command failed with exit code 1 (use -v to see invocation) --- Yet at the start of the attached CMakeOutput.log, these lines do not show an error. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 478664] Kstars/Ekos crashes every time I try to add an Optical Train
https://bugs.kde.org/show_bug.cgi?id=478664 --- Comment #3 from Richard Francis --- Update: I found an on-line suggestion to delete users.sqlite from ~/.local/share/kstars -- though being on macOS the sqlite file was in Library/Application Support/kstars . For good measure I deleted the backup too. This fixed it. On restarting I made sure to include the mount in the equipment list, and this time the default Primary and Secondary Optical Trains were, with the Primary one populated. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 478664] Kstars/Ekos crashes every time I try to add an Optical Train
https://bugs.kde.org/show_bug.cgi?id=478664 Richard Francis changed: What|Removed |Added CC||rich...@gerspatial.com -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 478664] Kstars/Ekos crashes every time I try to add an Optical Train
https://bugs.kde.org/show_bug.cgi?id=478664 --- Comment #2 from Richard Francis --- Some more info: 1. I am a new Kstars/Ekos user. This was the first time I tried it. My Optical Trains list is empty (no Primary or anything). 2. Today I added the other necessary stuff. I found how to link to the Paramount via TheSkyX and TCP, and I added my guide camera too. So I should have the full set. I got just the same crash when I tried to add an Optical Train. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 478664] Kstars/Ekos crashes every time I try to add an Optical Train
https://bugs.kde.org/show_bug.cgi?id=478664 --- Comment #1 from Richard Francis --- Oh yes, I forgot to mention -- this is an Apple Silicon (i.e. ARM) machine running Kstars under Apple's Rosetta emulation. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 478664] New: Kstars/Ekos crashes every time I try to add an Optical Train
https://bugs.kde.org/show_bug.cgi?id=478664 Bug ID: 478664 Summary: Kstars/Ekos crashes every time I try to add an Optical Train Classification: Applications Product: kstars Version: unspecified Platform: macOS (DMG) OS: macOS Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: rich...@gerspatial.com Target Milestone: --- Created attachment 164260 --> https://bugs.kde.org/attachment.cgi?id=164260&action=edit zip of 5 crash reports NOTE: this is version 3.6.8, which does not appear on the menu of builds. SUMMARY *** I cannot use Ekos (buttons are disabled) and I assume it's because I have no optical train defined. when I press the edit button next to the blank Optical Train menu, I find a window with greyed out (and blank) optical train elements. There's a plus button whose function is obvious, but every time I press it (and this is repeatable) the app disappears and a crash report is presented. I'm attaching a zip of 5 of these. In my equipment list I have a camera, focuser and rotator. The mount is represented by the Telescope Simulator since my Software Bisque mount is connected to ThSkyX and I haven't started trying to figure out how to connect it to Ekos. Maybe this has something to do with it? The overall result is that Ekos is unusable, unfortunately *** STEPS TO REPRODUCE 1. define a camera (mine is a Moravian C5A-100M), a focuser (FLI Atlas) and rotator (Optic Pyxis), a telescope simulator. 2. start Ekos and connect the equipment 3. enter a telescope OTA definition in the telescopes and lenses dialog. 4. go to the tab (don't know the name where there is the setup for autofocus. 5. press the edit button next to the blank optical train 6. press the + button OBSERVED RESULT App disappears and crash report appears EXPECTED RESULT I imagine one would be able to add an optical Train, but as I've never reached this point I don't know. SOFTWARE/OS VERSIONS macOS: 14.1.2 KDE Plasma Version: ? KDE Frameworks Version: ? Qt Version: ? Kstars version: 3.6.8 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kholidays] [Bug 473279] Public holidays for Tanzania
https://bugs.kde.org/show_bug.cgi?id=473279 Francis changed: What|Removed |Added CC||beluchukwunj...@gmail.com --- Comment #2 from Francis --- This is a little bit off topic. When I add my country's holiday, is there are visual way to actually see the changes? My question is how do I visually test local changes to Kholiday? The test passes but I want to see the holidays in the calendar widget before submitting a pr. PS Am a beginner in C/C++ -- You are receiving this mail because: You are watching all bug changes.
[kdev-python] [Bug 414531] kdevelop crashes while editing a python script
https://bugs.kde.org/show_bug.cgi?id=414531 Francis Herne changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REOPENED|RESOLVED --- Comment #8 from Francis Herne --- I haven't seen this again. To the original reporter (or anyone else): please reopen or file a new bug if you find a similar case that's reproducible. -- You are receiving this mail because: You are watching all bug changes.
[kdev-python] [Bug 385464] Assignment to global or nonlocal variables only affects the local scope.
https://bugs.kde.org/show_bug.cgi?id=385464 Francis Herne changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |CONFIRMED Ever confirmed|0 |1 --- Comment #4 from Francis Herne --- There have been no changes in this area so the issue will still exist. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 446926] Dolphin crashed after click on stop button of notification indicating the progress of compression to zip archive
https://bugs.kde.org/show_bug.cgi?id=446926 --- Comment #5 from Francis --- *** Bug 451204 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 451204] Compression to ZIP format via Dolphin can not be stopped via Plasma notification
https://bugs.kde.org/show_bug.cgi?id=451204 Francis changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #4 from Francis --- *** This bug has been marked as a duplicate of bug 446926 *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 451204] Compression to ZIP format via Dolphin can not be stopped via Plasma notification
https://bugs.kde.org/show_bug.cgi?id=451204 --- Comment #3 from Francis --- Oh, just remembered i read it on someone blog 🤦🏽♂. Then this should be closed. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 451204] Compression to ZIP format via Dolphin can not be stopped via Plasma notification
https://bugs.kde.org/show_bug.cgi?id=451204 Francis changed: What|Removed |Added CC||beluchukwunj...@gmail.com --- Comment #1 from Francis --- I can confirm this bug. But for me it crashes Dolphin Log from journalctl Mar 06 23:34:52 Steam dolphin[8763]: Icon theme "Numix-Circle-Light" not found. Mar 06 23:34:53 Steam dolphin[8763]: Icon theme "Numix-Circle-Light" not found. Mar 06 23:34:54 Steam dolphin[8763]: Icon theme "Numix-Circle-Light" not found. Mar 06 23:34:55 Steam dolphin[8763]: Icon theme "Numix-Circle-Light" not found. Mar 06 23:34:56 Steam dolphin[8763]: Icon theme "Numix-Circle-Light" not found. Mar 06 23:34:57 Steam dolphin[8763]: Icon theme "Numix-Circle-Light" not found. Mar 06 23:39:47 Steam systemd[983]: app-org.kde.dolphin-0dd7397a64074ead880525455576fa40.scope: Consumed 28.911s CPU time. Mar 06 23:45:42 Steam dolphin[27321]: Icon theme "Numix-Circle-Light" not found. Mar 06 23:45:50 Steam dolphin[27321]: Cannot initialize model with data QJsonObject(). missing: QJsonValue(string, "urls") Mar 06 23:46:01 Steam audit[27321]: ANOM_ABEND auid=1000 uid=1000 gid=1000 ses=2 pid=27321 comm="Kerfuffle::Job:" exe="/usr/bin/dolphin" sig=11 res=1 Mar 06 23:46:01 Steam kernel: audit: type=1701 audit(1646606761.138:246): auid=1000 uid=1000 gid=1000 ses=2 pid=27321 comm="Kerfuffle::Job:" exe="/usr/bin/dolphin" sig=11 res=1 Mar 06 23:46:01 Steam systemd-coredump[27437]: Process 27321 (dolphin) of user 1000 dumped core. Module libdolphinvcs.so.5 with build-id 0ae3f82377dd7bebda4b1e8cfeb2b05bc2226d06 Module libdolphinprivate.so.5 with build-id 5bb397f00e5da00ef96394f92a1fcea71c4af18b Module dolphin with build-id ab72b00f6c6d25b6503f6b52250bc0d36fe2c787 #19 0x5618f19721b1 n/a (dolphin + 0x4f1b1) #22 0x5618f197298e n/a (dolphin + 0x4f98e) Mar 06 23:46:01 Steam systemd[983]: app-org.kde.dolphin-f33aec828d414a3cb88155ede5181274.scope: Consumed 9.843s CPU time. Mar 06 23:46:04 Steam dolphin[27447]: Icon theme "Numix-Circle-Light" not found. Mar 06 23:46:17 Steam dolphin[27447]: Cannot initialize model with data QJsonObject(). missing: QJsonValue(string, "urls") Mar 06 23:46:44 Steam audit[27447]: ANOM_ABEND auid=1000 uid=1000 gid=1000 ses=2 pid=27447 comm="Kerfuffle::Job:" exe="/usr/bin/dolphin" sig=11 res=1 Mar 06 23:46:44 Steam kernel: audit: type=1701 audit(1646606804.533:255): auid=1000 uid=1000 gid=1000 ses=2 pid=27447 comm="Kerfuffle::Job:" exe="/usr/bin/dolphin" sig=11 res=1 Mar 06 23:46:45 Steam systemd-coredump[27582]: Process 27447 (dolphin) of user 1000 dumped core. Module libdolphinvcs.so.5 with build-id 0ae3f82377dd7bebda4b1e8cfeb2b05bc2226d06 Module libdolphinprivate.so.5 with build-id 5bb397f00e5da00ef96394f92a1fcea71c4af18b Module dolphin with build-id ab72b00f6c6d25b6503f6b52250bc0d36fe2c787 #19 0x55ebdecf81b1 n/a (dolphin + 0x4f1b1) #22 0x55ebdecf898e n/a (dolphin + 0x4f98e) Mar 06 23:46:45 Steam systemd[983]: app-org.kde.dolphin-9a6ef835b5a74ca3ab3d350540ccac14.scope: Consumed 15.523s CPU time. Additional details: SOFTWARE/OS VERSIONS Distro: Manjaro KDE Plasma Version: 5.24.2 KDE Frameworks Version: 5.91 Qt Version: 5.15.2 Dolphin Version: 21.12.2 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knewstuff] [Bug 451165] Error message when clicking "Get new icons..." in system settings
https://bugs.kde.org/show_bug.cgi?id=451165 Francis changed: What|Removed |Added CC||beluchukwunj...@gmail.com --- Comment #1 from Francis --- Can't confirm this behavior. Everything works great for me. SOFTWARE/OS VERSIONS Distro: Manjaro KDE Plasma Version: 5.24.2 KDE Frameworks Version: 5.91 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[kdev-python] [Bug 438206] Fails to build against Python 3.10
https://bugs.kde.org/show_bug.cgi?id=438206 --- Comment #11 from Francis Herne --- To address the development comments: It's great that you're interested in contributing to kdev-python. As you can see it's kind of needed at the moment. Consider dropping by #kdevelop on Libera IRC if you want to discuss it (ping FLHerne [me] or scummos [Sven]). Tools/tests: There are quite a lot of unit/end-to-end tests. Run `ninja test` (or `make test`) after building kdev-python, or for more detailed output run the test binaries individually (e.g. build/parser/tests/pyasttest , build/duchain/tests/pyduchaintest ). parser/generated.h converts from CPython's AST structures to kdev-python's. It's generated based on parser/python39.sdef by the script conversionGenerator.py. The script pythonpythonparser.py spits out the AST as an XML representation, using the Python `ast` module API. In recent years it's been used only as a tool for debugging and development. I believe it was once used in kdevelop before it called into the C API instead, and could be resurrected as such to implement Sven's suggestion. I'm not a big fan of this idea, I suspect performance would suffer considerably. -- You are receiving this mail because: You are watching all bug changes.
[kdev-python] [Bug 438206] Fails to build against Python 3.10
https://bugs.kde.org/show_bug.cgi?id=438206 --- Comment #10 from Francis Herne --- My own thinking is that it's probably easier to fork (or, so far as possible, vendor in the most recent version of) CPython's parser code. The amount of code involved is relatively small - see https://github.com/python/typed_ast/tree/master/ast3 which is another fork. (in the past I'd considered changing kdev-python to use that typed-ast library instead of linking against the CPython parser, but it's now deprecated with the features added to CPython upstream). Sadly I haven't yet had time to work on this, but I hope to in a few weeks. Right now I'm busy buying and moving onto a houseboat... -- You are receiving this mail because: You are watching all bug changes.
[kdev-python] [Bug 438206] Fails to build against Python 3.10
https://bugs.kde.org/show_bug.cgi?id=438206 Francis Herne changed: What|Removed |Added CC||pierre.bour...@free.fr --- Comment #6 from Francis Herne --- *** Bug 443167 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdev-python] [Bug 443167] python 3.10 (rc2) unsupported
https://bugs.kde.org/show_bug.cgi?id=443167 Francis Herne changed: What|Removed |Added Resolution|--- |DUPLICATE CC||m...@flherne.uk Status|REPORTED|RESOLVED --- Comment #3 from Francis Herne --- *** This bug has been marked as a duplicate of bug 438206 *** -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 411108] KDevelop crashes during background parsing in clang_parseTranslationUnit2FullArgv
https://bugs.kde.org/show_bug.cgi?id=411108 Francis Herne changed: What|Removed |Added Summary|KDevelop crashes due to |KDevelop crashes during |background parsing of |background parsing in |python project |clang_parseTranslationUnit2 ||FullArgv CC||m...@flherne.uk Component|general |Language Support: CPP ||(Clang-based) Status|REPORTED|RESOLVED Resolution|--- |UPSTREAM --- Comment #1 from Francis Herne --- >From the backtrace, this crash is actually in the Clang-based C++ parsing. The bug appears to be inside libclang rather than KDevelop as such. You were using llvm/libclang 8 which is old and lacks many bugfixes for this sort of issue; it's quite likely this has been fixed upstream in the meantime. Sorry for the slow triaging, KDevelop has quite a backlog of reports and few people handling them. :-( (renamed from "KDevelop crashes due to background parsing of python project") -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 408965] KDevelop Crashes No Action after kdev-python plugin installed
https://bugs.kde.org/show_bug.cgi?id=408965 Francis Herne changed: What|Removed |Added CC||m...@flherne.uk Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #3 from Francis Herne --- Sorry I didn't see this earlier [technically it should be filed under 'kdev-python' rather than 'kdevelop' but I know the bug filing system sucks for users]. This appears to be the same as a previously-reported bug that was fixed in 5.2.2. See the linked issue for more details. Thanks for the report! *** This bug has been marked as a duplicate of bug 389326 *** -- You are receiving this mail because: You are watching all bug changes.
[kdev-python] [Bug 389326] lambda function crashes background parser
https://bugs.kde.org/show_bug.cgi?id=389326 Francis Herne changed: What|Removed |Added CC||chris+kde...@halbersma.us --- Comment #3 from Francis Herne --- *** Bug 408965 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdev-python] [Bug 438206] Fails to build against Python 3.10
https://bugs.kde.org/show_bug.cgi?id=438206 Francis Herne changed: What|Removed |Added Assignee|m...@svenbrauch.de |m...@flherne.uk Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||m...@flherne.uk --- Comment #1 from Francis Herne --- Noted, we will need to add support for Python 3.10 by next release. As I mentioned previously, we tend to leave this until late in the Python release cycle because the API is prone to breaking changes even in late betas. This time Python upstream has made life particularly inconvenient for us (c.f.https://bugzilla.redhat.com/show_bug.cgi?id=1898116#c12) and we'll have to work around their deliberate obstruction. C'est la vie. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 442029] [Feature request] Add file exclude options for quick open
https://bugs.kde.org/show_bug.cgi?id=442029 Francis Herne changed: What|Removed |Added CC||m...@flherne.uk --- Comment #3 from Francis Herne --- Note: you can also quickly exclude a single file or directory from the Projects toolview: right-click -> "Exclude Item from Project". The filter dialog is better if you want to exclude many files matching some pattern. -- You are receiving this mail because: You are watching all bug changes.
[kdev-python] [Bug 442027] Variables inside f-strings are not highlighted and not recognised for renaming
https://bugs.kde.org/show_bug.cgi?id=442027 Francis Herne changed: What|Removed |Added Assignee|m...@svenbrauch.de |m...@flherne.uk CC||m...@flherne.uk --- Comment #2 from Francis Herne --- Thank you for the detailed report. This was a known missing feature - it existed briefly, but had to be disabled because at that time the parser returned very inaccurate character ranges for the elements within f-strings, which led to crashes when trying to look up the variables; see https://invent.kde.org/kdevelop/kdev-python/-/commit/275775c150a9c5eed5db8ad76fe45da7e273e8f1 I had considered the impact to be relatively small, since f-string expressions rarely have side-effects and the evaluated type is always `str`, but hadn't considered the auto-renaming case. In recent CPython versions, particularly 3.8+, the parser has been improved to return more range information (which should allow removing many ugly and unreliable workarounds in kdev-python) and the information is also more reliable. I'll investigate taking advantage of this to enable proper support of expressions in f-strings. P.S. -- kdev-python has been effectively in maintenance mode for a while, because neither Sven nor I have been able to work on it much. If you'd be interested in contributing to the project please drop by #kdevelop on irc.libera.chat and discuss it :-) My own first non-trivial KDE commit was to fix a missing Python feature that bugged me; in that case `foo, *bar = ...` unpacking. -- You are receiving this mail because: You are watching all bug changes.
[calligrawords] [Bug 441669] New: Calligra Words closes when trying to increase the number of rows in tables
https://bugs.kde.org/show_bug.cgi?id=441669 Bug ID: 441669 Summary: Calligra Words closes when trying to increase the number of rows in tables Product: calligrawords Version: 3.2.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: calligra-words-bugs-n...@kde.org Reporter: hamzafran...@criptext.com Target Milestone: --- Application: calligrawords (3.2.1) Qt Version: 5.15.2 Frameworks Version: 5.85.0 Operating System: Linux 5.10.60-1-lts x86_64 Windowing System: X11 Drkonqi Version: 5.22.4 Distribution: Arch Linux -- Information about the crash: I created a document in which I inserted a table that needed to be enlarged, doing this the Application simply closes. The crash can be reproduced every time. -- Backtrace: Application: Calligra Words (calligrawords), signal: Segmentation fault [KCrash Handler] #4 0x7f17bee625b6 in QtSharedPointer::ExternalRefCountData::getAndRef(QObject const*) () from /usr/lib/libQt5Core.so.5 #5 0x7f17be9e41db in ?? () from /usr/lib/libkotextlayout.so.17 #6 0x7f17be9e4e91 in ?? () from /usr/lib/libkotextlayout.so.17 #7 0x7f17be9e4241 in ?? () from /usr/lib/libkotextlayout.so.17 #8 0x7f17be9bef14 in KoTextLayoutArea::layout(FrameIterator*) () from /usr/lib/libkotextlayout.so.17 #9 0x7f17be9d7bef in KoTextLayoutRootArea::layoutRoot(FrameIterator*) () from /usr/lib/libkotextlayout.so.17 #10 0x7f17be9db1f5 in KoTextDocumentLayout::doLayout() () from /usr/lib/libkotextlayout.so.17 #11 0x7f17be9dba69 in KoTextDocumentLayout::layout() () from /usr/lib/libkotextlayout.so.17 #12 0x7f17bf0384ff in QObject::event(QEvent*) () from /usr/lib/libQt5Core.so.5 #13 0x7f17bf407d62 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #14 0x7f17bfac15ea in KoApplication::notify(QObject*, QEvent*) () from /usr/lib/libkomain.so.17 #15 0x7f17bf00b3aa in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 #16 0x7f17bf00e4a9 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/libQt5Core.so.5 #17 0x7f17bf0649a4 in ?? () from /usr/lib/libQt5Core.so.5 #18 0x7f17bc9cd10c in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #19 0x7f17bca20ba9 in ?? () from /usr/lib/libglib-2.0.so.0 #20 0x7f17bc9ca871 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #21 0x7f17bf063fd6 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #22 0x7f17bf009d1c in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #23 0x7f17bf012284 in QCoreApplication::exec() () from /usr/lib/libQt5Core.so.5 #24 0x7f17bfd36b81 in kdemain () from /usr/lib/libkdeinit5_calligrawords.so #25 0x7f17bfb8db25 in __libc_start_main () from /usr/lib/libc.so.6 #26 0x55ee666f205e in _start () [Inferior 1 (process 61636) detached] Possible duplicates by query: bug 426188, bug 420058, bug 398918, bug 393557, bug 390470. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 439841] New: Attempting to compile solid has been causing problems with udevdevice
https://bugs.kde.org/show_bug.cgi?id=439841 Bug ID: 439841 Summary: Attempting to compile solid has been causing problems with udevdevice Product: frameworks-solid Version: 5.84.0 Platform: PCLinuxOS OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: lu...@kde.org Reporter: ze...@aol.com CC: kdelibs-b...@kde.org Target Milestone: --- # kdesrc-build running: 'gmake' '-j' '4' # from directory: /opt/KDE5-SOURCE-BUILD/build/frameworks/solid Scanning dependencies of target KF5Solid_autogen Scanning dependencies of target KF5Solid_static_autogen [ 1%] [FLEX][SolidLexer] Building scanner with flex 2.6.1 [ 2%] [FLEX][SolidLexer] Building scanner with flex 2.6.1 [ 2%] [BISON][SolidParser] Building parser with bison 3.0.4 [ 2%] [BISON][SolidParser] Building parser with bison 3.0.4 [ 2%] Automatic MOC for target KF5Solid_static [ 2%] Automatic MOC for target KF5Solid [ 2%] Built target KF5Solid_autogen [ 2%] Built target KF5Solid_static_autogen Scanning dependencies of target KF5Solid Scanning dependencies of target KF5Solid_static [ 3%] Building CXX object src/solid/CMakeFiles/KF5Solid.dir/KF5Solid_autogen/mocs_compilation.cpp.o [ 3%] Building CXX object src/solid/CMakeFiles/KF5Solid.dir/devices/managerbase.cpp.o [ 4%] Building CXX object src/solid/CMakeFiles/KF5Solid.dir/devices/solidnamespace.cpp.o [ 5%] Building CXX object src/solid/CMakeFiles/KF5Solid_static.dir/KF5Solid_static_autogen/mocs_compilation.cpp.o [ 5%] Building CXX object src/solid/CMakeFiles/KF5Solid.dir/devices/predicateparse.cpp.o [ 6%] Building CXX object src/solid/CMakeFiles/KF5Solid.dir/devices/frontend/device.cpp.o [ 6%] Building CXX object src/solid/CMakeFiles/KF5Solid.dir/devices/frontend/devicemanager.cpp.o [ 7%] Building CXX object src/solid/CMakeFiles/KF5Solid.dir/devices/frontend/deviceinterface.cpp.o [ 7%] Building CXX object src/solid/CMakeFiles/KF5Solid_static.dir/devices/managerbase.cpp.o [ 7%] Building CXX object src/solid/CMakeFiles/KF5Solid.dir/devices/frontend/genericinterface.cpp.o [ 8%] Building CXX object src/solid/CMakeFiles/KF5Solid.dir/devices/frontend/processor.cpp.o [ 9%] Building CXX object src/solid/CMakeFiles/KF5Solid_static.dir/devices/solidnamespace.cpp.o [ 9%] Building CXX object src/solid/CMakeFiles/KF5Solid.dir/devices/frontend/block.cpp.o [ 9%] Building CXX object src/solid/CMakeFiles/KF5Solid.dir/devices/frontend/storagedrive.cpp.o [ 9%] Building CXX object src/solid/CMakeFiles/KF5Solid_static.dir/devices/predicateparse.cpp.o [ 10%] Building CXX object src/solid/CMakeFiles/KF5Solid.dir/devices/frontend/opticaldrive.cpp.o [ 10%] Building CXX object src/solid/CMakeFiles/KF5Solid.dir/devices/frontend/storagevolume.cpp.o [ 11%] Building CXX object src/solid/CMakeFiles/KF5Solid.dir/devices/frontend/opticaldisc.cpp.o [ 11%] Building CXX object src/solid/CMakeFiles/KF5Solid.dir/devices/frontend/storageaccess.cpp.o [ 11%] Building CXX object src/solid/CMakeFiles/KF5Solid_static.dir/devices/frontend/device.cpp.o [ 12%] Building CXX object src/solid/CMakeFiles/KF5Solid.dir/devices/frontend/camera.cpp.o [ 12%] Building CXX object src/solid/CMakeFiles/KF5Solid.dir/devices/frontend/portablemediaplayer.cpp.o [ 13%] Building CXX object src/solid/CMakeFiles/KF5Solid.dir/devices/frontend/networkshare.cpp.o [ 14%] Building CXX object src/solid/CMakeFiles/KF5Solid_static.dir/devices/frontend/devicemanager.cpp.o [ 14%] Building CXX object src/solid/CMakeFiles/KF5Solid.dir/devices/frontend/battery.cpp.o [ 15%] Building CXX object src/solid/CMakeFiles/KF5Solid.dir/devices/frontend/predicate.cpp.o [ 15%] Building CXX object src/solid/CMakeFiles/KF5Solid.dir/devices/ifaces/battery.cpp.o [ 15%] Building CXX object src/solid/CMakeFiles/KF5Solid.dir/devices/ifaces/block.cpp.o [ 15%] Building CXX object src/solid/CMakeFiles/KF5Solid_static.dir/devices/frontend/deviceinterface.cpp.o [ 16%] Building CXX object src/solid/CMakeFiles/KF5Solid.dir/devices/ifaces/camera.cpp.o [ 16%] Building CXX object src/solid/CMakeFiles/KF5Solid.dir/devices/ifaces/opticaldrive.cpp.o [ 17%] Building CXX object src/solid/CMakeFiles/KF5Solid.dir/devices/ifaces/device.cpp.o [ 17%] Building CXX object src/solid/CMakeFiles/KF5Solid.dir/devices/ifaces/deviceinterface.cpp.o [ 18%] Building CXX object src/solid/CMakeFiles/KF5Solid_static.dir/devices/frontend/genericinterface.cpp.o [ 19%] Building CXX object src/solid/CMakeFiles/KF5Solid.dir/devices/ifaces/devicemanager.cpp.o [ 19%] Building CXX object src/solid/CMakeFiles/KF5Solid.dir/devices/ifaces/genericinterface.cpp.o [ 20%] Building CXX object src/solid/CMakeFiles/KF5Solid.dir/devices/ifaces/networkshare.cpp.o [ 20%] Building CXX object src/solid/CMakeFiles/KF5Solid_static.dir/devices/frontend/processor.cpp.o [ 20%] Building CXX object src/solid/CMakeFiles/KF5Solid.dir/devices/ifaces/opt
[kdevelop] [Bug 434672] Kdevelop's syntax highlighter fails after code errors
https://bugs.kde.org/show_bug.cgi?id=434672 Francis Herne changed: What|Removed |Added CC||m...@flherne.uk --- Comment #4 from Francis Herne --- In fact, 5.80 is now out, so it's fixed by the *current* Frameworks release. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 433434] Code colorization broken
https://bugs.kde.org/show_bug.cgi?id=433434 Francis Herne changed: What|Removed |Added CC||piotr.mierzwin...@gmail.com --- Comment #3 from Francis Herne --- *** Bug 433974 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 433974] Sematic highlighting stops work after insert one or more lines in the middle of code
https://bugs.kde.org/show_bug.cgi?id=433974 Francis Herne changed: What|Removed |Added Status|REPORTED|RESOLVED CC||m...@flherne.uk Resolution|--- |DUPLICATE --- Comment #1 from Francis Herne --- This is a bug in KTextEditor 5.79, not in KDevelop directly. It will be fixed by the next KDE Frameworks release. https://invent.kde.org/frameworks/ktexteditor/-/commit/686da7797105a93035cfbc7edbf2a8e8f8adf0ec *** This bug has been marked as a duplicate of bug 433434 *** -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 433434] Code colorization broken
https://bugs.kde.org/show_bug.cgi?id=433434 Francis Herne changed: What|Removed |Added CC||m...@flherne.uk Status|REPORTED|RESOLVED Resolution|--- |UPSTREAM --- Comment #1 from Francis Herne --- This is caused by a bug in KTextEditor, introduced in 5.79.0 and fixed by the linked commit: https://invent.kde.org/frameworks/ktexteditor/-/commit/686da7797105a93035cfbc7edbf2a8e8f8adf0ec This should be fixed in KDE Frameworks 5.80 (or 5.79.1 if there is one). -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 432966] New: Cursor snaps to a grid after switching tabs
https://bugs.kde.org/show_bug.cgi?id=432966 Bug ID: 432966 Summary: Cursor snaps to a grid after switching tabs Product: krita Version: 4.4.1 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: major Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: navin.kurupache...@gmail.com Target Milestone: --- 12 second video showing this bug: https://gfycat.com/jovialsimilarkillifish STEPS TO REPRODUCE 1. Open 2 files. 2. Zoom in on 1st file 3. Switch to 2nd file and switch back OBSERVED RESULT The cursor snaps to a coarse grid instead of moving smoothly. This stops happening as soon as I zoom out/in. The bug reoccurs every time I switch tabs which makes it hard to work with multiple files. Note that it is not caused by just zooming in too far. You need multiple tabs to trigger it SOFTWARE/OS VERSIONS Windows 10 Krita 4.4.1 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 432304] crash parsing python project
https://bugs.kde.org/show_bug.cgi?id=432304 Francis Herne changed: What|Removed |Added Status|REPORTED|NEEDSINFO Component|general |Language Support: ||QML/JavaScript CC||m...@flherne.uk Resolution|--- |WAITINGFORINFO --- Comment #2 from Francis Herne --- Thanks for the report. >From the backtrace this is actually from the background parser trying to parse a QML or JavaScript file, or something KDevelop believes to be one. Did you have any of those open at the time, or otherwise in your project directory? Does the crash happen repeatably when opening the same project (perhaps within a few minutes rather than immediately)? -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 432110] New: Draggin icons/launchers from within dock no longer possible
https://bugs.kde.org/show_bug.cgi?id=432110 Bug ID: 432110 Summary: Draggin icons/launchers from within dock no longer possible Product: lattedock Version: git (master) Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: frankeba...@gmail.com Target Milestone: --- SUMMARY The feature to drag/rearrange launcher icons from within the dock is no longer working. Instead of showing the small hand which allows moving icons around and changing its order, a small red circle with cross line is shown and no matter where you point your cursor to the dock, the pinned launchers do not change location. This is in DOCK mode, have not tried PANEL mode. STEPS TO REPRODUCE 1. Update to current latte-dock-git version 2. Pin launchers to the dock or use one of your already pinned launchers 3. Try moving it around OBSERVED RESULT Cannot move launchers around in the dock, but it's still possible to move them out of the dock. EXPECTED RESULT Moving launchers from within the dock to conveniently rearrange the order of the icons. SOFTWARE/OS VERSIONS Windows: N/A macOS: N/A Linux/KDE Plasma: 5.20.5 (available in About System) KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.78 Qt Version: 5.15.2 ADDITIONAL INFORMATION This started around latte-dock-git r4804.bba3c292-1. With latte-dock-git r4743.c4565998-1 it was working. With latte-dock-git r4808.bba3c292-1 it is broken. Some users reported it stopped working as of latte-dock-git r4804.bba3c292-1. Woraround: Manually unpinning all launchers and re-pinning them one by one in the desired order. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 431391] KDevelop crashes on startup
https://bugs.kde.org/show_bug.cgi?id=431391 Francis Herne changed: What|Removed |Added CC||m...@flherne.uk --- Comment #13 from Francis Herne --- Note that the latter bug reporter (hefee on IRC) was using a version with the `type = clang_getCanonicalType(type);` commit, so it appears not to be a complete fix. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 431391] KDevelop crashes on startup
https://bugs.kde.org/show_bug.cgi?id=431391 Francis Herne changed: What|Removed |Added CC||skna...@kde.org --- Comment #12 from Francis Herne --- *** Bug 431887 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 431887] Crash while scanning through kde/pim/messagelib
https://bugs.kde.org/show_bug.cgi?id=431887 Francis Herne changed: What|Removed |Added Resolution|--- |DUPLICATE Status|CONFIRMED |RESOLVED CC||m...@flherne.uk --- Comment #2 from Francis Herne --- *** This bug has been marked as a duplicate of bug 431391 *** -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 431391] KDevelop crashes on startup
https://bugs.kde.org/show_bug.cgi?id=431391 Francis Herne changed: What|Removed |Added CC||gjditchfi...@acm.org --- Comment #11 from Francis Herne --- *** Bug 431796 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 431796] kdevelop segmentation fault loading a project
https://bugs.kde.org/show_bug.cgi?id=431796 Francis Herne changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |DUPLICATE CC||m...@flherne.uk --- Comment #6 from Francis Herne --- The version numbering is perhaps misleading. The version number of `master` is 5.6.40, and that's the version you're using. (this numbering is common to most KDE applications -- betas will be 5.6.80+, RCs 5.6.90+). Today's Neon package already includes Milian's attempted fix, which unfortunately doesn't seem to work for another reporter. The new feature triggering this bug is not in the 5.6 branch so there's no reason to backport any fixes to it. *** This bug has been marked as a duplicate of bug 431391 *** -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 428688] KDevelop does not handle gdb in version 10.x properly
https://bugs.kde.org/show_bug.cgi?id=428688 Francis Herne changed: What|Removed |Added CC||fred...@witherden.org --- Comment #2 from Francis Herne --- *** Bug 429419 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 429419] GDB version check fails for "GNU gdb (Gentoo 10.1 vanilla) 10.1 "
https://bugs.kde.org/show_bug.cgi?id=429419 Francis Herne changed: What|Removed |Added CC||m...@flherne.uk Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Francis Herne --- Thank you for the report. This is fixed in git, and will be in 5.6.1. *** This bug has been marked as a duplicate of bug 428688 *** -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 407841] Kdevelop crashes with a segmentation fault when parsing my project
https://bugs.kde.org/show_bug.cgi?id=407841 Francis Herne changed: What|Removed |Added CC||m...@flherne.uk --- Comment #4 from Francis Herne --- The last comment is probably https://bugs.kde.org/show_bug.cgi?id=426292, and unrelated to the original report. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 428688] KDevelop does not handle gdb in version 10.x properly
https://bugs.kde.org/show_bug.cgi?id=428688 Francis Herne changed: What|Removed |Added CC||m...@flherne.uk Resolution|--- |FIXED Latest Commit||8831937ffe4849258ed282cb0c7 ||20fe1cf2705d4 Status|REPORTED|RESOLVED Version Fixed In||5.6.1 --- Comment #1 from Francis Herne --- Thank you for the report. This was noticed already and fixed by Milian Wolff; the fix will be in 5.6.1 which should be released soon. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 406821] Dark UI color theme breaks default LightTheme
https://bugs.kde.org/show_bug.cgi?id=406821 --- Comment #15 from Francis Lamonde --- You have to upgrade to KDE Applications 20.04 or above. 19.12 will not fix it. If you upgrade to Kubuntu 20.10 the issue will be fixed as it uses KDE Apps 20.08. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 427246] SIGTRAP/SIGSEGV while running any version of KDevelop under GDB after a recent system update
https://bugs.kde.org/show_bug.cgi?id=427246 --- Comment #4 from Francis Herne --- Arch just backported the relevant fix in qt5-base 5.15.1-3. I've installed this and gdb works again. Thanks Igor for finding the relevant upstream bug. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 427246] SIGTRAP/SIGSEGV while running any version of KDevelop under GDB after a recent system update
https://bugs.kde.org/show_bug.cgi?id=427246 Francis Herne changed: What|Removed |Added Resolution|--- |UPSTREAM Status|REPORTED|RESOLVED CC||m...@flherne.uk --- Comment #2 from Francis Herne --- I have filed an Arch ticket: https://bugs.archlinux.org/task/68080 I don't think there's anything else we can do for now, so closing this. Will comment if the Arch maintainers respond. As I mentioned on the other bug, one workaround is to start KDevelop and then use `gdb --pid=`. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 427227] kdevelop parser crashes with SEGFAULT
https://bugs.kde.org/show_bug.cgi?id=427227 --- Comment #4 from Francis Herne --- Backtrace confirms what I said above. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 427227] kdevelop parser crashes with SEGFAULT
https://bugs.kde.org/show_bug.cgi?id=427227 --- Comment #2 from Francis Herne --- Sorry, I forgot to include "uninstall `kdevelop-python`" or "disable the Python plugin in Configure KDevelop -> Plugins" as other workarounds. Obviously in that case you lose the Python support. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 427227] kdevelop parser crashes with SEGFAULT
https://bugs.kde.org/show_bug.cgi?id=427227 Francis Herne changed: What|Removed |Added Status|REPORTED|RESOLVED CC||m...@flherne.uk Resolution|--- |DUPLICATE --- Comment #1 from Francis Herne --- Thank you for the report. This is almost certainly the linked bug -- basically, I broke kdev-python in 5.6.0 for all CPython versions < 3.9... Sorry about that. We hope to release 5.6.1 soon. In the meantime, please either use a previous release (e.g. the 5.5.2 AppImage [1]) or compile with this patch applied [2]. [1] https://download.kde.org/stable/kdevelop/5.5.2/bin/linux/KDevelop-5.5.2-x86_64.AppImage [2] https://invent.kde.org/kdevelop/kdev-python/-/commit/172dc5138acf94d54215d630c2173d7f24ec97df.diff You're correct that the gdb crash is completely unrelated. I see the same thing (also on Arch), have tried debugging it in various ways and asked a number of people. It isn't due to a recent change in KDevelop, the same crash happens with compiled older versions. You can work around it by starting KDevelop normally and then using gdb --pid. If you have the slightest idea why *that* happens, it would be very helpful! *** This bug has been marked as a duplicate of bug 426292 *** -- You are receiving this mail because: You are watching all bug changes.
[kdev-python] [Bug 426292] kdevelop-python crash while parsing projects
https://bugs.kde.org/show_bug.cgi?id=426292 Francis Herne changed: What|Removed |Added CC||soos.m...@gmail.com --- Comment #14 from Francis Herne --- *** Bug 427227 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 427050] The classes toolview does not work--no classes displayed
https://bugs.kde.org/show_bug.cgi?id=427050 Francis Herne changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |NOT A BUG --- Comment #7 from Francis Herne --- Thank you for the detailed explanation, now I see what's happened. Also, it's a documentation (or at least a don't-use-it-that-way) issue. :D When you create the new project 'ex', it creates a new directory `test/ex/` as the project root. Because `test/junk.cpp` is outside that directory, it isn't part of the project. The "Classes" view only shows classes from open projects (my last comment "there's no case where..." was wrong...), so doesn't show those from `junk.cpp`. If you want to import a project with existing files, you shouldn't use "New from Template". Instead use "Open/Import Project" and select the existing directory -- if the buildsystem isn't supported, there will be a 'Custom Build System' option where you can enter the relevant configure/build commands manually. Resolving as no immediate bug -- we might want to consider adding classes from open non-project files to the toolview, and/or making sure the manual is clear. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 427167] Can NOT config custom-compiler
https://bugs.kde.org/show_bug.cgi?id=427167 Francis Herne changed: What|Removed |Added CC||m...@flherne.uk --- Comment #1 from Francis Herne --- I cannot reproduce this with 5.6-git on Arch. On the other hand, I also can't find any commit in the intervening time that seems relevant. Can you please try with the 5.6.0 AppImage from https://www.kdevelop.org/download (or a locally-compiled build) and see if the current version works for you? This may be related to https://bugs.kde.org/show_bug.cgi?id=387224#c1 . -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 387224] selecting custom set compiler crashes
https://bugs.kde.org/show_bug.cgi?id=387224
Francis Herne changed:
What|Removed |Added
CC||m...@flherne.uk
--- Comment #3 from Francis Herne ---
I got a different crash while editing settings in the same window. May or may
not be connected.
Application: KDevelop (kdevelop), signal: Aborted
[KCrash Handler]
#4 0x7fb790af7615 in raise () at /usr/lib/libc.so.6
#5 0x7fb790ae0862 in abort () at /usr/lib/libc.so.6
#6 0x7fb7910529ac in () at /usr/lib/libQt5Core.so.5
#7 0x7fb791051d59 in qt_assert_x(char const*, char const*, char const*,
int) () at /usr/lib/libQt5Core.so.5
#8 0x7fb795103e91 in
KDevelop::ConfigDialog::checkForUnsavedChanges(KPageWidgetItem*,
KPageWidgetItem*) (this=0x7fffadc89140, current=0x55735bb34840, before=0x0) at
/home/flh/projects/kdevelop/kdevplatform/shell/configdialog.cpp:89
#9 0x7fb7951079f0 in QtPrivate::FunctorCall,
QtPrivate::List, void, int
(KDevelop::ConfigDialog::*)(KPageWidgetItem*, KPageWidgetItem*)>::call(int
(KDevelop::ConfigDialog::*)(KPageWidgetItem*, KPageWidgetItem*),
KDevelop::ConfigDialog*, void**) (f=(int
(KDevelop::ConfigDialog::*)(KDevelop::ConfigDialog * const, KPageWidgetItem *,
KPageWidgetItem *)) 0x7fb795103e36
, o=0x7fffadc89140, arg=0x7fffadc87900) at
/usr/include/qt/QtCore/qobjectdefs_impl.h:152
#10 0x7fb7951073c4 in QtPrivate::FunctionPointer::call,
void>(int (KDevelop::ConfigDialog::*)(KPageWidgetItem*, KPageWidgetItem*),
KDevelop::ConfigDialog*, void**) (f=(int
(KDevelop::ConfigDialog::*)(KDevelop::ConfigDialog * const, KPageWidgetItem *,
KPageWidgetItem *)) 0x7fb795103e36
, o=0x7fffadc89140, arg=0x7fffadc87900) at
/usr/include/qt/QtCore/qobjectdefs_impl.h:185
#11 0x7fb7951069e8 in QtPrivate::QSlotObject, void>::impl(int,
QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) (which=1,
this_=0x5573587af710, r=0x7fffadc89140, a=0x7fffadc87900, ret=0x0) at
/usr/include/qt/QtCore/qobjectdefs_impl.h:418
#12 0x7fb7912ad036 in () at /usr/lib/libQt5Core.so.5
#13 0x7fb79269cb1c in KPageDialog::currentPageChanged(KPageWidgetItem*,
KPageWidgetItem*) () at /usr/lib/libKF5WidgetsAddons.so.5
#14 0x7fb7912ad036 in () at /usr/lib/libQt5Core.so.5
#15 0x7fb79271725c in KPageWidget::currentPageChanged(KPageWidgetItem*,
KPageWidgetItem*) () at /usr/lib/libKF5WidgetsAddons.so.5
#16 0x7fb7912ad070 in () at /usr/lib/libQt5Core.so.5
#17 0x7fb792711528 in KPageView::currentPageChanged(QModelIndex const&,
QModelIndex const&) () at /usr/lib/libKF5WidgetsAddons.so.5
#18 0x7fb79271323e in () at /usr/lib/libKF5WidgetsAddons.so.5
#19 0x7fb7912ad070 in () at /usr/lib/libQt5Core.so.5
#20 0x7fb79121fa91 in QItemSelectionModel::selectionChanged(QItemSelection
const&, QItemSelection const&) () at /usr/lib/libQt5Core.so.5
#21 0x7fb7912288b1 in QItemSelectionModel::select(QItemSelection const&,
QFlags) () at /usr/lib/libQt5Core.so.5
#22 0x7fb7912231fe in QItemSelectionModel::select(QModelIndex const&,
QFlags) () at /usr/lib/libQt5Core.so.5
#23 0x7fb791223519 in QItemSelectionModel::setCurrentIndex(QModelIndex
const&, QFlags) () at
/usr/lib/libQt5Core.so.5
#24 0x7fb792711b1f in () at /usr/lib/libKF5WidgetsAddons.so.5
#25 0x7fb7927130cd in () at /usr/lib/libKF5WidgetsAddons.so.5
#26 0x7fb7912ad070 in () at /usr/lib/libQt5Core.so.5
#27 0x7fb79120f3e7 in
QAbstractItemModel::layoutChanged(QList const&,
QAbstractItemModel::LayoutChangeHint) () at /usr/lib/libQt5Core.so.5
#28 0x7fb792719bf4 in KPageWidgetModel::addSubPage(KPageWidgetItem*,
KPageWidgetItem*) () at /usr/lib/libKF5WidgetsAddons.so.5
#29 0x7fb792719cc1 in KPageWidgetModel::addSubPage(KPageWidgetItem*,
QWidget*, QString const&) () at /usr/lib/libKF5WidgetsAddons.so.5
#30 0x7fb7951045b5 in
KDevelop::ConfigDialog::appendSubConfigPage(KDevelop::ConfigPage*,
KDevelop::ConfigPage*) (this=0x7fffadc89140, parentPage=0x55735b27dc50,
page=0x55735848e5f0) at
/home/flh/projects/kdevelop/kdevplatform/shell/configdialog.cpp:163
#31 0x7fb79505405e in operator()(KDevelop::IPlugin*) const
(__closure=0x55735bb47820, plugin=0x557358d8fba0) at
/home/flh/projects/kdevelop/kdevplatform/shell/uicontroller.cpp:557
#32 0x7fb79505670e in QtPrivate::FunctorCall,
QtPrivate::List, void,
KDevelop::UiController::showSettingsDialog()::
>::call(struct {...} &, void **) (f=..., arg=0x7fffadc883c0) at
/usr/include/qt/QtCore/qobjectdefs_impl.h:146
#33 0x7fb795056658 in
QtPrivate::Functor,
1>::call, void>(struct {...} &, void *,
void **) (f=..., arg=0x7fffadc883c0) at
/usr/include/qt/QtCore/qobjectdefs_impl.h:256
#34 0x7fb7950565fd in
QtPrivate::QFunctorSlotObject,
1, QtPrivate::List, void>::impl(int,
QtPrivate::QSlotObjectBase *, QObject *, void **, bool *) (which=1,
this_=0x55735bb47810, r=0x7fffadc89140, a=0x7f
[kdevelop] [Bug 384791] Option for unbuffered output
https://bugs.kde.org/show_bug.cgi?id=384791 Francis Herne changed: What|Removed |Added CC||kle...@gmail.com --- Comment #6 from Francis Herne --- *** Bug 427128 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdev-python] [Bug 427128] should not buffer python script run or debug output
https://bugs.kde.org/show_bug.cgi?id=427128 Francis Herne changed: What|Removed |Added CC||m...@flherne.uk Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Francis Herne --- Yep, this is a bit annoying. You can use `sys.stdout.flush()`, but it shouldn't be necessary. *** This bug has been marked as a duplicate of bug 384791 *** -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 403484] many classes not resolved by C++ indexer
https://bugs.kde.org/show_bug.cgi?id=403484 Francis Herne changed: What|Removed |Added CC||m...@flherne.uk --- Comment #6 from Francis Herne --- Is this still an issue with current Clang versions? (I attempted to build the example project, but it doesn't seem to work with current SCons). -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 427050] The classes toolview does not work--no classes displayed
https://bugs.kde.org/show_bug.cgi?id=427050 --- Comment #4 from Francis Herne --- Thank you for the report. Given that it only seems to happen for you, it's presumably caused by some attribute of your project or setup and unlikely to be reproducible given the information available. If the project is publicly-available somewhere (or you can attach it here or send it to me) I could try with that. Documentation is probably not an issue -- there's no case where classes should be visible in the code browser and not the Classes view. P.S. -- meson support in KDevelop is quite recent, it might not have existed when you originally imported the project. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 427050] The classes toolview does not work--no classes displayed
https://bugs.kde.org/show_bug.cgi?id=427050 Francis Herne changed: What|Removed |Added CC||m...@flherne.uk Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from Francis Herne --- I can't reproduce this with 5.6-git on Arch, the Classes toolview is working fine. Do you have an example of a specific project this doesn't work with? (also, can you please set the 'Version' field?) -- You are receiving this mail because: You are watching all bug changes.
[kdev-python] [Bug 426866] Cannot use variable browser in debugger
https://bugs.kde.org/show_bug.cgi?id=426866 Francis Herne changed: What|Removed |Added CC||m...@flherne.uk --- Comment #2 from Francis Herne --- I feel like we should be able to make this work though... -- You are receiving this mail because: You are watching all bug changes.
[kdev-python] [Bug 426292] kdevelop-python crash while parsing projects
https://bugs.kde.org/show_bug.cgi?id=426292 Francis Herne changed: What|Removed |Added Latest Commit|https://invent.kde.org/kdev |https://invent.kde.org/kdev |elop/kdev-python/commit/44b |elop/kdev-python/commit/172 |8992325bbcbfa350b163bf0176a |dc5138acf94d54215d630c2173d |ad2c9d47da |7f24ec97df --- Comment #12 from Francis Herne --- Git commit 172dc5138acf94d54215d630c2173d7f24ec97df by Francis Herne. Committed on 20/09/2020 at 13:42. Pushed by flherne into branch '5.6'. Fix ExtSlice crash with Python <= 3.8 FIXED-IN: 5.6.1 The dimensions of an ExtSlice node are _slice nodes rather than _expr, so this would crash whenever encountering one. -- This was introduced in commit 05e95cac7 "Initial support for CPython 3.9". When I replaced `SliceAst` with `ExpressionAst` in the relevant line of python39.sdef, conversionGenerator.py *also* changed `_slice` to `_expr` here (because the type used is implicitly determined in a stupid way) and I failed to notice that difference in the newly-generated code. I couldn't see an easy way to fix the implicit type thing, so this commit just bypasses that mechanism and uses CODE instead. M +1-0duchain/tests/pyduchaintest.cpp M +1-1parser/generated.h M +2-1parser/python39.sdef https://invent.kde.org/kdevelop/kdev-python/commit/172dc5138acf94d54215d630c2173d7f24ec97df -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 426756] KDevelop unresponsive with `kdevelop `
https://bugs.kde.org/show_bug.cgi?id=426756 Francis Herne changed: What|Removed |Added Status|REPORTED|CONFIRMED CC||m...@flherne.uk Ever confirmed|0 |1 --- Comment #1 from Francis Herne --- Weird bug. Can reproduce with my local build. This definitely used to work. -- You are receiving this mail because: You are watching all bug changes.
[kdev-python] [Bug 426292] kdevelop-python crash while parsing projects
https://bugs.kde.org/show_bug.cgi?id=426292 Francis Herne changed: What|Removed |Added Version Fixed In||5.6.1 Latest Commit|https://invent.kde.org/kdev |https://invent.kde.org/kdev |elop/kdev-python/commit/7db |elop/kdev-python/commit/44b |8f71c9fd9c5c2ffc32638b91ba2 |8992325bbcbfa350b163bf0176a |2916b6f69d |ad2c9d47da --- Comment #9 from Francis Herne --- Git commit 44b8992325bbcbfa350b163bf0176aad2c9d47da by Francis Herne. Committed on 19/09/2020 at 23:46. Pushed by flherne into branch 'flh-slice-crash'. Fix ExtSlice crash with Python <= 3.8 FIXED-IN: 5.6.1 The dimensions of an ExtSlice node are _slice nodes rather than _expr, so this would crash whenever encountering one. -- This was introduced in commit 05e95cac7 "Initial support for CPython 3.9". When I replaced `ExtendedSliceAst` with `TupleAst` in python39.sdef in that commit, conversionGenerator.py *also* changed `_slice` to `_expr` here (because the type used is implicitly determined in a stupid way) and I failed to notice that difference in the newly-generated code. I couldn't see an easy way to fix the implicit type thing, so this commit just bypasses that mechanism and uses CODE instead. M +1-0duchain/tests/pyduchaintest.cpp M +1-1parser/generated.h M +2-1parser/python39.sdef https://invent.kde.org/kdevelop/kdev-python/commit/44b8992325bbcbfa350b163bf0176aad2c9d47da -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 426561] Crash on startup while parsing python code
https://bugs.kde.org/show_bug.cgi?id=426561 Francis Herne changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED CC||m...@flherne.uk --- Comment #4 from Francis Herne --- *** This bug has been marked as a duplicate of bug 426292 *** -- You are receiving this mail because: You are watching all bug changes.
[kdev-python] [Bug 426292] kdevelop-python crash while parsing projects
https://bugs.kde.org/show_bug.cgi?id=426292 Francis Herne changed: What|Removed |Added CC||kle...@gmail.com --- Comment #4 from Francis Herne --- *** Bug 426561 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 426462] KDE project provider isn't available
https://bugs.kde.org/show_bug.cgi?id=426462 --- Comment #5 from Francis Herne --- Yes, reasonably so -- project provider plugins are quite simple and don't need much knowledge of the rest of the codebase. You can find a similar example in the GitHub provider (plugins/ghprovider in the source code) and of course the previous KDE project provider removed in the commit I linked. There's a tutorial on how to build KDevelop using kdesrc-build here: https://community.kde.org/index.php?title=KDevelop/HowToCompile_v5 Alternatively, you can install the various build dependencies (even the git version should be fine with the dep versions in most distros) and compile/install as any other CMake project. Do note that QT_PLUGIN_PATH must be set before running KDevelop if you install to /usr/local or some other non-standard path. Since I see you're using Manjaro, this is the PKGBUILD I use to build locally; you'd need to change _repo at least: http://www.flherne.uk/files/PKGBUILD If any other questions, ask in the #kdevelop IRC channel and wait a while if you don't get an answer immediately -- several devs are in it but not watching IRC all the time. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 426462] KDE project provider isn't available
https://bugs.kde.org/show_bug.cgi?id=426462 Francis Herne changed: What|Removed |Added CC||m...@flherne.uk Resolution|INTENTIONAL |--- Status|NEEDSINFO |CONFIRMED Severity|normal |wishlist Summary|Cannot find KDE under |KDE project provider isn't |sources |available Ever confirmed|0 |1 --- Comment #3 from Francis Herne --- This was removed in https://invent.kde.org/kdevelop/kdevelop/commit/a36a50baf050850fa0e513ceae2e99be7749c27c > https://projects.kde.org/kde_projects.xml is removed in the next weeks as > part of the reorganization happening in the move to gitlab by KDE. > Wanted: someone writing a replacement using gitlab, which then would also be usable for other gitlab servers. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 425511] Kdevelop random crash
https://bugs.kde.org/show_bug.cgi?id=425511 Francis Herne changed: What|Removed |Added CC||m...@flherne.uk Resolution|WAITINGFORINFO |UNMAINTAINED Status|NEEDSINFO |RESOLVED --- Comment #5 from Francis Herne --- Seems very likely this was due to kdev-embedded, which isn't being worked on currently. (this might be my fault for suggesting you look at it, if you were the person asking on IRC) -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 425994] Crashes caused by DebugController::showStepInSource() when a user requests KDevelop exit just before a code breakpoint is hit
https://bugs.kde.org/show_bug.cgi?id=425994 Francis Herne changed: What|Removed |Added CC||willyant...@protonmail.com --- Comment #1 from Francis Herne --- *** Bug 426371 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 426371] KDevelop crashed upon exit (segmentation fault)
https://bugs.kde.org/show_bug.cgi?id=426371 Francis Herne changed: What|Removed |Added Resolution|--- |DUPLICATE CC||m...@flherne.uk Status|REPORTED|RESOLVED --- Comment #1 from Francis Herne --- I believe this is the same bug that Igor Kushnir found, and wrote a fix for which will hopefully be in 5.6.1: See patches at https://invent.kde.org/kdevelop/kdevelop/-/merge_requests/161 *** This bug has been marked as a duplicate of bug 425994 *** -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 426335] kdevelop symantic analysis opencl only partially working
https://bugs.kde.org/show_bug.cgi?id=426335 Francis Herne changed: What|Removed |Added Ever confirmed|0 |1 CC||m...@flherne.uk Component|Analyzer: Clang-Tidy|Language Support: CPP ||(Clang-based) Status|REPORTED|CONFIRMED --- Comment #2 from Francis Herne --- The same errors are reported when calling `clang -cl-std=CL1.2 file.cl`. Adding `-include /usr/lib/clang/10.0.1/include/opencl-c.h` to the command resolves them, and jpsollie reports that adding this same header to 'Custom Defines/Includes' makes KDevelop work. We should probably include this automatically when parsing CL files in KDevelop. -- You are receiving this mail because: You are watching all bug changes.
[kdev-python] [Bug 426292] kdevelop-python crash while parsing projects
https://bugs.kde.org/show_bug.cgi?id=426292 Francis Herne changed: What|Removed |Added Product|kdevelop|kdev-python Component|general |Language support -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 426292] kdevelop-python crash while parsing projects
https://bugs.kde.org/show_bug.cgi?id=426292 Francis Herne changed: What|Removed |Added Status|REPORTED|CONFIRMED CC||m...@flherne.uk Assignee|kdevelop-bugs-n...@kde.org |m...@flherne.uk Ever confirmed|0 |1 --- Comment #3 from Francis Herne --- I'm investigating this. It's almost certainly a result of my Python 3.9 changes, and occurs only with previous versions. I thought I'd tested this pretty thoroughly on 3.4 and 3.8, but clearly not enough... It's triggered by a slice appearing as part of a multi-dimensional subscript, e.g. > M[1:3, 3] -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 425841] SIGPIPE, then a crash when the first event loop starts at least 60 seconds after KDevelop launch
https://bugs.kde.org/show_bug.cgi?id=425841 Francis Herne changed: What|Removed |Added Resolution|--- |FIXED Version Fixed In||5.7.0 Latest Commit||https://invent.kde.org/kdev ||elop/kdevelop/commit/43db1a ||72dbbe91e231ab7349f202df6a5 ||fb4337c Status|REPORTED|RESOLVED --- Comment #1 from Francis Herne --- Git commit 43db1a72dbbe91e231ab7349f202df6a5fb4337c by Francis Herne, on behalf of Igor Kushnir. Committed on 02/09/2020 at 22:03. Pushed by flherne into branch 'master'. Don't crash during a slow (>= 60 seconds) startup A quick benchmark shows that the added QCoreApplication::processEvents() call takes the same time - 6 milliseconds - in Debug and Release builds. 6 milliseconds is not a noticeable startup slowdown, especially considering that the event loop does useful work: processes events, which would have to be handled eventually anyway. FIXED-IN: 5.7.0 M +6-0app/main.cpp https://invent.kde.org/kdevelop/kdevelop/commit/43db1a72dbbe91e231ab7349f202df6a5fb4337c -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 425990] Crash in KDevelop::TypeSystem::ensureFactoryLoaded
https://bugs.kde.org/show_bug.cgi?id=425990
--- Comment #1 from Francis Herne ---
Oops, I somehow managed to paste the first non-obviously-irrelevant thread of
the backtrace twice...
Meant to include
#1 0x7f65e34f2819 in () at /usr/lib/libxcb.so.1
#2 0x7f65e34f408f in () at /usr/lib/libxcb.so.1
#3 0x7f65e34f41a2 in xcb_wait_for_reply () at /usr/lib/libxcb.so.1
#4 0x7f65d3803d2e in () at /usr/lib/libQt5XcbQpa.so.5
#5 0x7f65d3803e5c in () at /usr/lib/libQt5XcbQpa.so.5
#6 0x7f65e4ecccea in QCursor::pos(QScreen const*) () at
/usr/lib/libQt5Gui.so.5
#7 0x7f65e56c21d8 in
QApplicationPrivate::sendSyntheticEnterLeave(QWidget*) () at
/usr/lib/libQt5Widgets.so.5
#8 0x7f65e56fc7ec in QWidgetPrivate::setVisible(bool) () at
/usr/lib/libQt5Widgets.so.5
#9 0x7f65e57dad11 in () at /usr/lib/libQt5Widgets.so.5
#10 0x7f65e57dbb93 in QDockWidget::setFloating(bool) () at
/usr/lib/libQt5Widgets.so.5
#11 0x7f65e57e9546 in () at /usr/lib/libQt5Widgets.so.5
#12 0x7f65e57e9770 in () at /usr/lib/libQt5Widgets.so.5
#13 0x7f65e58175dd in () at /usr/lib/libQt5Widgets.so.5
#14 0x7f65e5817a64 in () at /usr/lib/libQt5Widgets.so.5
#15 0x7f65e580e980 in QMainWindow::restoreState(QByteArray const&, int) ()
at /usr/lib/libQt5Widgets.so.5
#16 0x7f65e62cb64c in KMainWindow::applyMainWindowSettings(KConfigGroup
const&) () at /usr/lib/libKF5XmlGui.so.5
#17 0x7f65e62fc208 in KXmlGuiWindow::applyMainWindowSettings(KConfigGroup
const&) () at /usr/lib/libKF5XmlGui.so.5
#18 0x7f65e85d797c in
KDevelop::MainWindow::applyMainWindowSettings(KConfigGroup const&)
(this=0x5589140c67c0, config=...) at
/home/flh/projects/kdevelop/kdevplatform/shell/mainwindow.cpp:92
#19 0x7f65e62fc1c4 in KXmlGuiWindow::finalizeGUI(bool) () at
/usr/lib/libKF5XmlGui.so.5
#20 0x7f65e62efdaf in KXMLGUIFactory::addClient(KXMLGUIClient*) () at
/usr/lib/libKF5XmlGui.so.5
#21 0x7f65e85e13c7 in
KDevelop::MainWindowPrivate::addPlugin(KDevelop::IPlugin*)
(this=0x55891417f8d0, plugin=0x558918506950) at
/home/flh/projects/kdevelop/kdevplatform/shell/mainwindow_p.cpp:94
#22 0x7f65e85e07b0 in QtPrivate::FunctorCall,
QtPrivate::List, void, void
(KDevelop::MainWindowPrivate::*)(KDevelop::IPlugin*)>::call(void
(KDevelop::MainWindowPrivate::*)(KDevelop::IPlugin*),
KDevelop::MainWindowPrivate*, void**) (f=(void
(KDevelop::MainWindowPrivate::*)(KDevelop::MainWindowPrivate * const,
KDevelop::IPlugin *)) 0x7f65e85e11c0
, o=0x55891417f8d0,
arg=0x7fff685cf7d0) at /usr/include/qt/QtCore/qobjectdefs_impl.h:152
#23 0x7f65e85dfd72 in QtPrivate::FunctionPointer::call,
void>(void (KDevelop::MainWindowPrivate::*)(KDevelop::IPlugin*),
KDevelop::MainWindowPrivate*, void**) (f=(void
(KDevelop::MainWindowPrivate::*)(KDevelop::MainWindowPrivate * const,
KDevelop::IPlugin *)) 0x7f65e85e11c0
, o=0x55891417f8d0,
arg=0x7fff685cf7d0) at /usr/include/qt/QtCore/qobjectdefs_impl.h:185
#24 0x7f65e85deedc in QtPrivate::QSlotObject, void>::impl(int,
QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) (which=1,
this_=0x5589146214f0, r=0x55891417f8d0, a=0x7fff685cf7d0, ret=0x0) at
/usr/include/qt/QtCore/qobjectdefs_impl.h:418
#25 0x7f65e4876a06 in () at /usr/lib/libQt5Core.so.5
#26 0x7f65e716369e in
KDevelop::IPluginController::pluginLoaded(KDevelop::IPlugin*)
(this=0x55891426a1b0, _t1=0x558918506950) at
kdevplatform/interfaces/KDevPlatformInterfaces_autogen/EWIEGA46WW/moc_iplugincontroller.cpp:199
#27 0x7f65e85edb78 in
KDevelop::PluginController::loadPluginInternal(QString const&)
(this=0x55891426a1b0, pluginId=...) at
/home/flh/projects/kdevelop/kdevplatform/shell/plugincontroller.cpp:629
#28 0x7f65e85ee648 in operator()(KPluginMetaData const&) const
(__closure=0x7fff685cf9b0, info=...) at
/home/flh/projects/kdevelop/kdevplatform/shell/plugincontroller.cpp:727
#29 0x7f65e85f03fa in
KDevelop::PluginControllerPrivate::foreachEnabledPlugin >(struct {...},
const QString &, const QVariantMap &, const QString &) const
(this=0x5589142e8bb0, func=..., extension=..., constraints=..., pluginName=...)
at /home/flh/projects/kdevelop/kdevplatform/shell/plugincontroller.cpp:237
#30 0x7f65e85ee74f in
KDevelop::PluginController::allPluginsForExtension(QString const&,
QMap const&) (this=0x55891426a1b0, extension=...,
constraints=...) at
/home/flh/projects/kdevelop/kdevplatform/shell/plugincontroller.cpp:722
#31 0x7f65e8648e84 in
KDevelop::LanguageController::languagesForMimetype(QString const&)
(this=0x558914595b10, mimetype=...) at
/home/flh/projects/kdevelop/kdevplatform/shell/languagecontroller.cpp:337
#32 0x7f65e8648c67 in KDevelop::LanguageController::languagesForUrl(QUrl
const&) (this=0x558914595b10, url=...) at
/home/flh/projects/kdevelop/kdevplatform/shell/languagecontroller.cpp:319
#33 0x7f65e73ef9ce in
KDevelop::BackgroundParserPrivate::createParseJob(KDevelop::IndexedString
const&, DocumentParsePlan const&a
[kdevelop] [Bug 425990] New: Crash in KDevelop::TypeSystem::ensureFactoryLoaded
https://bugs.kde.org/show_bug.cgi?id=425990 Bug ID: 425990 Summary: Crash in KDevelop::TypeSystem::ensureFactoryLoaded Product: kdevelop Version: 5.5.80 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Language Support: CPP (Clang-based) Assignee: kdevelop-bugs-n...@kde.org Reporter: m...@flherne.uk Target Milestone: --- SUMMARY While searching in QuickOpen, shortly after loading a session containing the KDevelop source, KDevelop crashed with the backtrace below. I wasn't able to reproduce this by repeating a similar sequence of actions. SOFTWARE/OS VERSIONS KDevelop 5.6-git bd8a49a10a (5.5.80 plus a few patches since). Arch Linux KF 5.73.0 Qt 5.15.0 Application: KDevelop (kdevelop), signal: Aborted [KCrash Handler] #4 0x7f65e40c3615 in raise () at /usr/lib/libc.so.6 #5 0x7f65e40ac862 in abort () at /usr/lib/libc.so.6 #6 0x7f65e461d9ac in () at /usr/lib/libQt5Core.so.5 #7 0x7f65e461cd59 in qt_assert_x(char const*, char const*, char const*, int) () at /usr/lib/libQt5Core.so.5 #8 0x7f65e7524cc8 in KDevelop::TypeSystem::ensureFactoryLoaded(KDevelop::AbstractTypeData const&) const (this=0x7f65e85323e0 , data=...) at /home/flh/projects/kdevelop/kdevplatform/language/duchain/types/typeregister.cpp:65 #9 0x7f65e75249ef in KDevelop::TypeSystem::callDestructor(KDevelop::AbstractTypeData*) const (this=0x7f65e85323e0 , data=0x7f64e0408bc0) at /home/flh/projects/kdevelop/kdevplatform/language/duchain/types/typeregister.cpp:36 #10 0x7f65e752f371 in KDevelop::AbstractType::~AbstractType() (this=0x7f64e0408ba0, __in_chrg=) at /home/flh/projects/kdevelop/kdevplatform/language/duchain/types/abstracttype.cpp:67 #11 0x7f65e752fd5c in KDevelop::IntegralType::~IntegralType() (this=0x7f64e0408ba0, __in_chrg=) at /home/flh/projects/kdevelop/kdevplatform/language/duchain/types/integraltype.cpp:75 #12 0x7f65e752fd78 in KDevelop::IntegralType::~IntegralType() (this=0x7f64e0408ba0, __in_chrg=) at /home/flh/projects/kdevelop/kdevplatform/language/duchain/types/integraltype.cpp:77 #13 0x7f650ba5f51b in QExplicitlySharedDataPointer::~QExplicitlySharedDataPointer() (this=0x7f64f5ff8c90, __in_chrg=) at /usr/include/qt/QtCore/qshareddata.h:184 #14 0x7f650ba5ed64 in KDevelop::TypePtr::~TypePtr() (this=0x7f64f5ff8c90, __in_chrg=) at /home/flh/projects/kdevelop/kdevplatform/language/duchain/types/typepointer.h:39 #15 0x7f650baa4e95 in (anonymous namespace)::Visitor::setDeclType<(CXCursorKind)6>(KDevelop::Declaration*, KDevelop::AbstractType*) (this=0x7f64f5ff9d70, decl=0x7f64e03e6790, type=0x7f64e0408ba0) at /home/flh/projects/kdevelop/plugins/clang/duchain/builder.cpp:868 #16 0x7f650ba9b40c in (anonymous namespace)::Visitor::createDeclaration<(CXCursorKind)6, KDevelop::ClassMemberDeclaration>(CXCursor, KDevelop::Identifier const&, KDevelop::DUContext*) (this=0x7f64f5ff9d70, cursor=..., id=..., context=0x0) at /home/flh/projects/kdevelop/plugins/clang/duchain/builder.cpp:473 #17 0x7f650ba96159 in (anonymous namespace)::Visitor::buildDeclaration<(CXCursorKind)6, KDevelop::ClassMemberDeclaration, false>(CXCursor) (this=0x7f64f5ff9d70, cursor=...) at /home/flh/projects/kdevelop/plugins/clang/duchain/builder.cpp:1216 #18 0x7f650ba90177 in (anonymous namespace)::Visitor::dispatchCursor<(CXCursorKind)6>(CXCursor, CXCursor) (this=0x7f64f5ff9d70, cursor=..., parent=...) at /home/flh/projects/kdevelop/plugins/clang/duchain/builder.cpp:967 #19 0x7f650ba8dc6a in (anonymous namespace)::visitCursor(CXCursor, CXCursor, CXClientData) (cursor=..., parent=..., data=0x7f64f5ff9d70) at /home/flh/projects/kdevelop/plugins/clang/duchain/builder.cpp:1553 #20 0x7f6509705727 in () at /usr/lib/libclang.so.10 #21 0x7f65097060de in () at /usr/lib/libclang.so.10 #22 0x7f65097062da in () at /usr/lib/libclang.so.10 #23 0x7f650970520b in () at /usr/lib/libclang.so.10 #24 0x7f650970dddb in clang_visitChildren () at /usr/lib/libclang.so.10 #25 0x7f650baa2c33 in (anonymous namespace)::Visitor::buildDeclaration<(CXCursorKind)2, KDevelop::ClassDeclaration, true>(CXCursor) (this=0x7f64f5ff9d70, cursor=...) at /home/flh/projects/kdevelop/plugins/clang/duchain/builder.cpp:1213 #26 0x7f650ba9aa29 in (anonymous namespace)::Visitor::dispatchCursor<(CXCursorKind)2, (Decision)1, (Decision)0>(CXCursor, CXCursor) (this=0x7f64f5ff9d70, cursor=..., parent=...) at /home/flh/projects/kdevelop/plugins/clang/duchain/builder.cpp:967 #27 0x7f650ba95bb3 in (anonymous namespace)::Visitor::dispatchCursor<(CXCursorKind)2, (Decision)1, (Decision)2>(CXCursor, CXCursor) (this=0x7f64f5ff9d70, cursor=..., parent=...) at /home/flh/projects/kdevelop/plugins/clang/duchain/builder.cpp:942 #28 0x7f650ba8ff6f in (anonymous namespace)::Visitor::dispatchCursor<(CXCursorKind)2>(CXCursor, CXCursor) (this=0x7f64f5ff9d70, cursor=..
[kdevelop] [Bug 395856] Semantic highlighting uses hardcoded colors that cannot be changed
https://bugs.kde.org/show_bug.cgi?id=395856 --- Comment #24 from Francis Herne --- Patches are, as always, very welcome. No-one's paid to work on KDevelop -- it's all done in our free time, so I might as well thank *you* for not doing anything about it. I have looked at this (and the similarly-popular https://bugs.kde.org/show_bug.cgi?id=257378 ) a couple of times, but I keep getting sidetracked by issues that matter more to my own work (like making sure the Python backend keeps working with new versions of the language). When someone fixes it, it'll be fixed. If you can't wait for someone else to fix it, do it yourself -- fixing bugs that annoyed me was how I got into KDevelop development, and I suspect many others over the years. The nice thing about KDevelop being an IDE is that all our users are programmers... -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 395856] Semantic highlighting uses hardcoded colors that cannot be changed
https://bugs.kde.org/show_bug.cgi?id=395856 Francis Herne changed: What|Removed |Added CC||brainstr...@yandex.ru --- Comment #22 from Francis Herne --- *** Bug 276057 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 276057] make semantic colors configurable
https://bugs.kde.org/show_bug.cgi?id=276057 Francis Herne changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |DUPLICATE CC||m...@flherne.uk --- Comment #8 from Francis Herne --- Marking as duplicate of #395856 , which is newer but has more discussion. *** This bug has been marked as a duplicate of bug 395856 *** -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 396195] Should use shebang to decide which language the file is
https://bugs.kde.org/show_bug.cgi?id=396195 Francis Herne changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #5 from Francis Herne --- This has been fixed at some point. KDevelop and other KTextEditor-based applications now detect such files. -- You are receiving this mail because: You are watching all bug changes.
[kdev-python] [Bug 419290] Fails to build against Python 3.9
https://bugs.kde.org/show_bug.cgi?id=419290 Francis Herne changed: What|Removed |Added Latest Commit|https://invent.kde.org/kdev |https://invent.kde.org/kdev |elop/kdev-python/commit/05e |elop/kdev-python/commit/efa |95cac74b0bb3595a6d97da07a12 |bd9d4b4884f6e715650a0667570 |b907385be5 |09a9647865 --- Comment #4 from Francis Herne --- Git commit efabd9d4b4884f6e715650a066757009a9647865 by Francis Herne. Committed on 22/08/2020 at 10:43. Pushed by flherne into branch '5.5-python39'. Initial support for CPython 3.9 This reformats our AST to match that introduced upstream by https://bugs.python.org/issue34822 and adjusts the conversion from older Python versions' AST to match. ExtendedSliceAst is removed, in favour of a TupleAst containing SliceAsts and/or other expressions. IndexAst is removed, instead non-slice index expressions are direct children of SubscriptAst. SliceAst and EllipsisAst are now subclasses of ExpressionAst. In the latter case I don't understand how it wasn't broken before. --- The stdlib docfiles are not updated. There aren't many changes to builtins in 3.9, but we do need a system to re-generate these - perhaps based on Typeshed. In CPython 3.8 and 3.9 there are several changes to the parser that could be useful to us -- particularly end_lineno and end_col_offset. This patch doesn't attempt to take advantage of them. M +2-2CMakeLists.txt M +2-2duchain/declarationbuilder.cpp M +2-2duchain/expressionvisitor.cpp M +2-17 parser/ast.cpp M +3-24 parser/ast.h M +0-10 parser/astdefaultvisitor.cpp M +0-4parser/astdefaultvisitor.h M +0-2parser/astvisitor.cpp M +0-2parser/astvisitor.h M +2-0parser/conversionGenerator.py M +22 -5parser/generated.h R +4-3parser/python39.sdef [from: parser/python38.sdef - 096% similarity] https://invent.kde.org/kdevelop/kdev-python/commit/efabd9d4b4884f6e715650a066757009a9647865 -- You are receiving this mail because: You are watching all bug changes.
[kdev-python] [Bug 414531] kdevelop crashes while editing a python script
https://bugs.kde.org/show_bug.cgi?id=414531 Francis Herne changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|WORKSFORME |--- Ever confirmed|0 |1 --- Comment #3 from Francis Herne --- ...of course, I say that, and then get a suspiciously-similar ASAN failure: PASS : Python::PyCompletionTest::testCompletionAfterQuotes(nothing) = ==3197==ERROR: AddressSanitizer: heap-use-after-free on address 0x604000e888d0 at pc 0x7f8fc7b67e0b bp 0x7f8f7d3f4a00 sp 0x7f8f7d3f49f8 READ of size 8 at 0x604000e888d0 thread T51 (Queue(0x6040001) #0 0x7f8fc7b67e0a in KDevelop::Declaration::ownIndex() const /home/jenkins/workspace/Administration/Dependency Build KDevelop kf5-qt5 SUSEQt5.14/kdevelop/kdevplatform/language/duchain/declaration.cpp:116 #1 0x7f8fcc2d9cc2 in Python::DeclarationBuilder::assignToAttribute(Python::AttributeAst*, Python::DeclarationBuilder::SourceType const&) /home/jenkins/kdev-python/duchain/declarationbuilder.cpp:1218 #2 0x7f8fcc2dc5ed in Python::DeclarationBuilder::assignToUnknown(Python::ExpressionAst*, Python::DeclarationBuilder::SourceType const&) /home/jenkins/kdev-python/duchain/declarationbuilder.cpp:1324 #3 0x7f8fcc2dcbe2 in Python::DeclarationBuilder::visitAssignment(Python::AssignmentAst*) /home/jenkins/kdev-python/duchain/declarationbuilder.cpp:1341 #4 0x7f8fcbe7e365 in Python::AstVisitor::visitNode(Python::Ast*) /home/jenkins/kdev-python/parser/astvisitor.cpp:47 #5 0x7f8fcc2ec6bd in Python::DeclarationBuilder::visitNode(Python::Ast*) /home/jenkins/kdev-python/duchain/declarationbuilder.cpp:1868 #6 0x7f8fcbe7746c in void Python::AstVisitor::visitNodeList(QList const&) (/home/jenkins/install-prefix/lib64/libkdevpythonparser.so+0xc246c) #7 0x7f8fcbe72568 in Python::AstDefaultVisitor::visitExceptionHandler(Python::ExceptionHandlerAst*) /home/jenkins/kdev-python/parser/astdefaultvisitor.cpp:256 #8 0x7f8fcc2bf095 in Python::DeclarationBuilder::visitExceptionHandler(Python::ExceptionHandlerAst*) /home/jenkins/kdev-python/duchain/declarationbuilder.cpp:356 #9 0x7f8fcbe7fe4d in Python::AstVisitor::visitNode(Python::Ast*) /home/jenkins/kdev-python/parser/astvisitor.cpp:97 #10 0x7f8fcc2ec6bd in Python::DeclarationBuilder::visitNode(Python::Ast*) /home/jenkins/kdev-python/duchain/declarationbuilder.cpp:1868 #11 0x7f8fcbe78624 in void Python::AstVisitor::visitNodeList(QList const&) (/home/jenkins/install-prefix/lib64/libkdevpythonparser.so+0xc3624) #12 0x7f8fcbe71d9b in Python::AstDefaultVisitor::visitTry(Python::TryAst*) /home/jenkins/kdev-python/parser/astdefaultvisitor.cpp:202 #13 0x7f8fcbe7e833 in Python::AstVisitor::visitNode(Python::Ast*) /home/jenkins/kdev-python/parser/astvisitor.cpp:56 #14 0x7f8fcc2ec6bd in Python::DeclarationBuilder::visitNode(Python::Ast*) /home/jenkins/kdev-python/duchain/declarationbuilder.cpp:1868 #15 0x7f8fcbe7746c in void Python::AstVisitor::visitNodeList(QList const&) (/home/jenkins/install-prefix/lib64/libkdevpythonparser.so+0xc246c) #16 0x7f8fcbe70a44 in Python::AstDefaultVisitor::visitCode(Python::CodeAst*) /home/jenkins/kdev-python/parser/astdefaultvisitor.cpp:91 #17 0x7f8fcc2a5f59 in Python::ContextBuilder::visitCode(Python::CodeAst*) /home/jenkins/kdev-python/duchain/contextbuilder.cpp:320 #18 0x7f8fcc2becee in Python::DeclarationBuilder::visitCode(Python::CodeAst*) /home/jenkins/kdev-python/duchain/declarationbuilder.cpp:345 #19 0x7f8fcbe7e035 in Python::AstVisitor::visitNode(Python::Ast*) /home/jenkins/kdev-python/parser/astvisitor.cpp:41 #20 0x7f8fcc2ec6bd in Python::DeclarationBuilder::visitNode(Python::Ast*) /home/jenkins/kdev-python/duchain/declarationbuilder.cpp:1868 #21 0x7f8fcc2a30e6 in Python::ContextBuilder::startVisiting(Python::Ast*) /home/jenkins/kdev-python/duchain/contextbuilder.cpp:145 #22 0x7f8fcc2b2329 in KDevelop::AbstractContextBuilder::supportBuild(Python::Ast*, KDevelop::DUContext*) /home/jenkins/install-prefix/include/kdevplatform/language/duchain/builders/abstractcontextbuilder.h:127 #23 0x7f8fcc31bf76 in KDevelop::AbstractTypeBuilder::supportBuild(Python::Ast*, KDevelop::DUContext*) /home/jenkins/install-prefix/include/kdevplatform/language/duchain/builders/abstracttypebuilder.h:84 #24 0x7f8fcc2ae70f in KDevelop::AbstractContextBuilder::build(KDevelop::IndexedString const&, Python::Ast*, KDevelop::ReferencedTopDUContext const&) /home/jenkins/install-prefix/include/kdevplatform/language/duchain/builders/abstractcontextbuilder.h:106 #25 0x7f8fcc2a2485 in Python::ContextBuilder::build(KDevelop::IndexedString const&, Python::Ast*, KDevelop::ReferencedTopDUContext const&) /home/jenkins/kdev-python/duchain/contextbuilder.cpp
[kdevelop] [Bug 416007] Crash on startup
https://bugs.kde.org/show_bug.cgi?id=416007 Francis Herne changed: What|Removed |Added CC||m...@flherne.uk Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME --- Comment #2 from Francis Herne --- This report doesn't provide enough information to identify the problem. Good that it seems to have been fixed. For future reference: Often removing ~/.cache/kdevduchain/ resolves crash-on-start issues (there should be a dialog asking to do that when starting after a crash). Otherwise there may be a file in your project or its dependencies that triggers some parser bug. There's unlikely to be an AppImage with debug symbols, but KDevelop has quite conservative dependencies - you should always be able to compile KDevelop using the system library versions found the latest release of Ubuntu LTS or of most other distros. -- You are receiving this mail because: You are watching all bug changes.
[kdev-python] [Bug 411956] Fails to build against Python 3.8
https://bugs.kde.org/show_bug.cgi?id=411956 --- Comment #7 from Francis Herne --- Those files should not be byte-compiled. They are never intended to be executed; kdev-python parses them as-is to provide information about the relevant modules. Compiling or executing them in any other way will not do anything useful and may cause problems. -- You are receiving this mail because: You are watching all bug changes.
[kdev-python] [Bug 419290] Fails to build against Python 3.9
https://bugs.kde.org/show_bug.cgi?id=419290 Francis Herne changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/kdev ||elop/kdev-python/commit/05e ||95cac74b0bb3595a6d97da07a12 ||b907385be5 Status|CONFIRMED |RESOLVED --- Comment #3 from Francis Herne --- Git commit 05e95cac74b0bb3595a6d97da07a12b907385be5 by Francis Herne. Committed on 19/08/2020 at 20:36. Pushed by flherne into branch '5.6'. Initial support for CPython 3.9 This reformats our AST to match that introduced upstream by https://bugs.python.org/issue34822 and adjusts the conversion from older Python versions' AST to match. ExtendedSliceAst is removed, in favour of a TupleAst containing SliceAsts and/or other expressions. IndexAst is removed, instead non-slice index expressions are direct children of SubscriptAst. SliceAst and EllipsisAst are now subclasses of ExpressionAst. In the latter case I don't understand how it wasn't broken before. --- The stdlib docfiles are not updated. There aren't many changes to builtins in 3.9, but we do need a system to re-generate these - perhaps based on Typeshed. In CPython 3.8 and 3.9 there are several changes to the parser that could be useful to us -- particularly end_lineno and end_col_offset. This patch doesn't attempt to take advantage of them. M +2-2CMakeLists.txt M +2-2duchain/declarationbuilder.cpp M +2-2duchain/expressionvisitor.cpp M +2-17 parser/ast.cpp M +3-24 parser/ast.h M +0-10 parser/astdefaultvisitor.cpp M +0-4parser/astdefaultvisitor.h M +0-2parser/astvisitor.cpp M +0-2parser/astvisitor.h M +2-0parser/conversionGenerator.py M +22 -5parser/generated.h R +4-3parser/python39.sdef [from: parser/python38.sdef - 096% similarity] https://invent.kde.org/kdevelop/kdev-python/commit/05e95cac74b0bb3595a6d97da07a12b907385be5 -- You are receiving this mail because: You are watching all bug changes.
[kdev-python] [Bug 414531] kdevelop crashes while editing a python script
https://bugs.kde.org/show_bug.cgi?id=414531 Francis Herne changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #2 from Francis Herne --- Unfortunately I don't think this can be traced without some reproducible example. Clearly the relevant `Declaration*` is bogus, but it was just retrieved from the DUChain at this point -- the bug is in whichever code inserted it, and that can't be identified from the backtrace. Please feel free to reopen if this recurs. -- You are receiving this mail because: You are watching all bug changes.
[kdevplatform] [Bug 236435] Embedded cvs interface does not honour CVS_RSH environment variable
https://bugs.kde.org/show_bug.cgi?id=236435 Francis Herne changed: What|Removed |Added Resolution|--- |UNMAINTAINED CC||m...@flherne.uk Status|REPORTED|RESOLVED --- Comment #2 from Francis Herne --- The CVS plugin was removed in KDevelop 5.3 because it was unmaintained and didn't work in most cases. -- You are receiving this mail because: You are watching all bug changes.
[kdevplatform] [Bug 328097] cvs commits messages wrapped with single quote
https://bugs.kde.org/show_bug.cgi?id=328097 Francis Herne changed: What|Removed |Added Resolution|--- |UNMAINTAINED Status|REPORTED|RESOLVED CC||m...@flherne.uk --- Comment #7 from Francis Herne --- The CVS plugin was removed in KDevelop 5.3 because it was unmaintained and didn't work in most cases. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-qqc2-desktop-style] [Bug 424125] Toolbuttons are almost invisible when checked (or hovered).
https://bugs.kde.org/show_bug.cgi?id=424125
Francis Herne changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution|--- |WORKSFORME
--- Comment #1 from Francis Herne ---
So... I produced a minimal example (should have done that first!).
Then I found this minimal example doesn't actually reproduce the bug for me, it
looks exactly like a Widgets app...
Closing as presumed user error, even if I haven't figured out how yet.
import org.kde.kirigami 2.9 as Kg
Kg.ScrollablePage {
header: Kg.ActionToolBar {
actions: [
Kg.Action {
id: editGridAction
iconName: "document-edit"
text: "Edit"
checkable: true
},
Kg.Action {
id: showNumbersAction
iconName: 'view-grid'
text: "Show Numbers"
checkable: true
checked: true
}
]
}
}
--
You are receiving this mail because:
You are watching all bug changes.
[frameworks-qqc2-desktop-style] [Bug 424125] Toolbuttons are almost invisible when checked (or hovered).
https://bugs.kde.org/show_bug.cgi?id=424125 Francis Herne changed: What|Removed |Added Keywords||usability -- You are receiving this mail because: You are watching all bug changes.
[frameworks-qqc2-desktop-style] [Bug 424125] New: Toolbuttons are almost invisible when checked (or hovered).
https://bugs.kde.org/show_bug.cgi?id=424125 Bug ID: 424125 Summary: Toolbuttons are almost invisible when checked (or hovered). Product: frameworks-qqc2-desktop-style Version: 5.72.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: notm...@gmail.com Reporter: m...@flherne.uk CC: k...@davidedmundson.co.uk Target Milestone: --- Created attachment 130069 --> https://bugs.kde.org/attachment.cgi?id=130069&action=edit Comparison of Kirigami and Widgets checkable toolbuttons. SUMMARY When a checkable toolbutton is checked, the background is *very* slightly darker than normal (with both dark and light themes). With light themes the contrast is marginal and much less than Widgets apps. With dark themes there's effectively no contrast; it's virtually impossibe to see whether a button is checked. [In the screenshot, 'Edit' is unchecked and 'Show Numbers' is checked.] In Widgets, there's clear contrast for checked toolbuttons. May be related to https://bugs.kde.org/show_bug.cgi?id=384989 Hovered toolbuttons are also nearly invisible, unlike in Widgets where they have a border (or coloured background if checked); that may be the same as https://bugs.kde.org/show_bug.cgi?id=415805 STEPS TO REPRODUCE 1. Have a Kirigami app with checkable actions, or another QML app with checkable ToolButtons. 2. For worst results, use a dark theme. 3. Check a button. OBSERVED RESULT Button looks pretty much the same. EXPECTED RESULT Checked state looks different (e.g. like Widgets). SOFTWARE/OS VERSIONS KDE Frameworks Version: 5.72 Qt Version: 5.15.0 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 401677] Some phone models, ROMs or Apps don't report SMS History
https://bugs.kde.org/show_bug.cgi?id=401677 --- Comment #49 from Francis (Grizzly) Smit --- (In reply to Andy Holmes from comment #0) > SUMMARY > > GSConnect has started shipping its SMS application, which has resulted in a > number of users reporting devices that don't report SMS history. > > I've opened this bug to help collect a list of these phones, ROMs or SMS > apps which don't currently support SMS history. > > > STEPS TO REPRODUCE > 1. Send a kdeconnect.sms.request_conversations packet to the device > 2. Wait for a kdeconnect.sms.messages packet > > > OBSERVED RESULT > > Some phone models (especially Samsung) or SMS apps (especially Signal) > return an empty list of SMS messages. Some phones don't seem to respond at > all, possibly indicating a different bug that may have useful messages in > logcat. > > > **USERS DIRECTED FROM GSCONNECT** > > Please be a good neighbour to the KDE Connect team. Keep this report limited > to phone models, ROMs, SMS apps and share logs as attachments. > > Please do not post "me too" or "+1" comments and don't repeat duplicate > information. I get the same with my Pixel 4 XL worked until I updated GSConnect then no sms chat history, I'm using the standard google SMS app -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 401677] Some phone models, ROMs or Apps don't report SMS History
https://bugs.kde.org/show_bug.cgi?id=401677 Francis (Grizzly) Smit changed: What|Removed |Added CC||griz...@smit.id.au --- Comment #48 from Francis (Grizzly) Smit --- (In reply to Andy Holmes from comment #0) > SUMMARY > > GSConnect has started shipping its SMS application, which has resulted in a > number of users reporting devices that don't report SMS history. > > I've opened this bug to help collect a list of these phones, ROMs or SMS > apps which don't currently support SMS history. > > > STEPS TO REPRODUCE > 1. Send a kdeconnect.sms.request_conversations packet to the device > 2. Wait for a kdeconnect.sms.messages packet > > > OBSERVED RESULT > > Some phone models (especially Samsung) or SMS apps (especially Signal) > return an empty list of SMS messages. Some phones don't seem to respond at > all, possibly indicating a different bug that may have useful messages in > logcat. > > > **USERS DIRECTED FROM GSCONNECT** > > Please be a good neighbour to the KDE Connect team. Keep this report limited > to phone models, ROMs, SMS apps and share logs as attachments. > > Please do not post "me too" or "+1" comments and don't repeat duplicate > information. I get the same with my Pixel 4 XL worked until I updated GSConnect then no sms chat history, I'm using the standard google SMS app -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 420315] Leave actions do nothing (cannot log out or shutdown from plasma)
https://bugs.kde.org/show_bug.cgi?id=420315 Francis T changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED --- Comment #2 from Francis T --- I'm running my development version from ~/kde/..., using the install-sessions.sh script as described here: https://community.kde.org/Get_Involved/development dbus is 1.12.16-5. I'm not sure how recently it was pushed to manjaro repositories, unfortunately. -- You are receiving this mail because: You are watching all bug changes.
