[kde] [Bug 486972] New: Konsole crashes after unlocking screen
https://bugs.kde.org/show_bug.cgi?id=486972
Bug ID: 486972
Summary: Konsole crashes after unlocking screen
Classification: I don't know
Product: kde
Version: unspecified
Platform: Arch Linux
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: unassigned-b...@kde.org
Reporter: ernes...@yahoo.gr
Target Milestone: ---
Application: konsole (24.02.2)
Qt Version: 6.7.0
Frameworks Version: 6.1.0
Operating System: Linux 6.8.9-arch1-2 x86_64
Windowing System: Wayland
Distribution: "Arch Linux"
DrKonqi: 6.0.4 [CoredumpBackend]
-- Information about the crash:
The Konsole process crashed just after unlocking the screen.
The reporter is unsure if this crash is reproducible.
-- Backtrace:
Application: Konsole (konsole), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = }
Downloading separate debug info for /usr/bin/konsole...
[New LWP 4544]
[New LWP 4546]
[New LWP 4545]
[New LWP 4547]
[New LWP 4549]
[New LWP 4548]
[New LWP 12589]
Downloading separate debug info for /usr/lib/libkonsoleapp.so.24.02.2...
Downloading separate debug info for /usr/lib/libkonsoleprivate.so.24.02.2...
Downloading separate debug info for /usr/lib/libKF6DBusAddons.so.6...
Downloading separate debug info for /usr/lib/libKF6XmlGui.so.6...
Downloading separate debug info for /usr/lib/libKF6I18n.so.6...
Downloading separate debug info for /usr/lib/libKF6ConfigCore.so.6...
Downloading separate debug info for /usr/lib/libQt6Widgets.so.6...
Downloading separate debug info for /usr/lib/libKF6Crash.so.6...
Downloading separate debug info for /usr/lib/libQt6Gui.so.6...
Downloading separate debug info for /usr/lib/libKF6CoreAddons.so.6...
Downloading separate debug info for /usr/lib/libQt6Core.so.6...
Downloading separate debug info for /usr/lib/libc.so.6...
Downloading separate debug info for /usr/lib/libKF6NotifyConfig.so.6...
Downloading separate debug info for /usr/lib/libKF6GlobalAccel.so.6...
Downloading separate debug info for /usr/lib/libKF6KIOWidgets.so.6...
Downloading separate debug info for /usr/lib/libKF6WindowSystem.so.6...
Downloading separate debug info for /usr/lib/libKF6ConfigWidgets.so.6...
Downloading separate debug info for /usr/lib/libKF6ColorScheme.so.6...
Downloading separate debug info for /usr/lib/libKF6GuiAddons.so.6...
Downloading separate debug info for /usr/lib/libKF6ConfigGui.so.6...
Downloading separate debug info for /usr/lib/libKF6WidgetsAddons.so.6...
Downloading separate debug info for /usr/lib/libKF6NewStuffWidgets.so.6...
Downloading separate debug info for /usr/lib/libKF6TextWidgets.so.6...
Downloading separate debug info for /usr/lib/libKF6NewStuffCore.so.6...
Downloading separate debug info for /usr/lib/libKF6Pty.so.6...
Downloading separate debug info for /usr/lib/libicuuc.so.74...
Downloading separate debug info for /usr/lib/libQt6Core5Compat.so.6...
Downloading separate debug info for /usr/lib/libKF6IconWidgets.so.6...
Downloading separate debug info for /usr/lib/libKF6BookmarksWidgets.so.6...
Downloading separate debug info for /usr/lib/libQt6Multimedia.so.6...
Downloading separate debug info for /usr/lib/libQt6PrintSupport.so.6...
Downloading separate debug info for /usr/lib/libKF6KIOGui.so.6...
Downloading separate debug info for /usr/lib/libKF6KIOCore.so.6...
Downloading separate debug info for /usr/lib/libKF6Notifications.so.6...
Downloading separate debug info for /usr/lib/libKF6Service.so.6...
Downloading separate debug info for /usr/lib/libQt6Network.so.6...
Downloading separate debug info for /usr/lib/libKF6Bookmarks.so.6...
Downloading separate debug info for /usr/lib/libQt6Xml.so.6...
Downloading separate debug info for /usr/lib/libQt6DBus.so.6...
Downloading separate debug info for /usr/lib/libm.so.6...
Downloading separate debug info for /usr/lib/libKF6ItemViews.so.6...
Downloading separate debug info for /usr/lib/libKF6IconThemes.so.6...
Downloading separate debug info for /usr/lib/libX11.so.6...
Downloading separate debug info for /usr/lib/libEGL.so.1...
Downloading separate debug info for /usr/lib/libfontconfig.so.1...
Downloading separate debug info for /usr/lib/libglib-2.0.so.0...
Downloading separate debug info for /usr/lib/libxkbcommon.so.0...
Downloading separate debug info for /usr/lib/libGLX.so.0...
Downloading separate debug info for /usr/lib/libOpenGL.so.0...
Downloading separate debug info for /usr/lib/libpng16.so.16...
Downloading separate debug info for /usr/lib/libharfbuzz.so.0...
Downloading separate debug info for /usr/lib/libmd4c.so.0...
Downloading separate debug info for /usr/lib/libfreetype.so.6...
Downloading separate debug info for /usr/lib/libz.so.1...
Downloading separate debug info for /usr/lib/libudev.so.1...
Downloading separate debug info for /usr/lib/libicui18n.so.74...
Downloading separate debug info for
[kate] [Bug 454281] New: Adding custom shortcut deletes random lines in Shortcuts section in katerc
https://bugs.kde.org/show_bug.cgi?id=454281 Bug ID: 454281 Summary: Adding custom shortcut deletes random lines in Shortcuts section in katerc Product: kate Version: 22.04.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: psamar...@gmail.com Target Milestone: --- SUMMARY Note: It's a weird observation and I have not extensively tested, but judge for yourself :) Initially, my custom shortcut for `kate_mdi_toolview_kate_plugin_katesearch` was lost after a new user session, or reboot. I tried using the shortcuts manager profiles with no success, so I kept the Default Shortcuts profile, which included my custom shortcut. Today the shortcut was lost (again) and I saved a katerc backup. I created the *new* shortcut again (Ctrl+Shift+F) and compared kwinrc new and old. Old: ``` [Shortcut Schemes] Current Scheme=Default [Shortcuts] kate_mdi_toolview_kate_plugin_symbolviewer=Ctrl+Alt+M kate_mdi_toolview_kate_private_plugin_katefileselectorplugin=none kate_mdi_toolview_kate_private_plugin_katefiletreeplugin=none kate_mdi_toolview_kate_private_plugin_katekonsoleplugin=none kate_mdi_toolview_kate_private_plugin_katesnippetsplugin=none kate_mdi_toolview_kateproject=none kate_mdi_toolview_kateprojectgit=none kate_mdi_toolview_kateprojectinfo=none kate_mdi_toolview_ktexteditorpreviewplugin=none ``` New: ``` [Shortcut Schemes] Current Scheme=Default [Shortcuts] kate_mdi_toolview_kate_plugin_katesearch=Ctrl+Shift+F kate_mdi_toolview_kate_private_plugin_katesnippetsplugin=none kate_mdi_toolview_output=none ``` Of course, the shortcut works now. I have not logged out yet. I run to report ASAP :) Possibly related bugs: #453715 #438893 #428989 STEPS TO REPRODUCE 1. Save a copy of $XDG_CONFIG_HOME/katerc 2. Set a custom shortcut for "View Search & Replace" plugin 3. Compare the changed katerc file with the saved copy OBSERVED RESULT Lines irrelevant to the shortcut that were included in `[Shortcuts]` Section, are deleted. A line with the newly created shortcut is added. EXPECTED RESULT All lines that were included in `[Shortcuts]` Section, should be present (not deleted). A line with the newly created shortcut is added. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.4 Kernel Version: 5.17.7-arch1-2 (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i3 CPU 560 @ 3.33GHz Memory: 7.6 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics ADDITIONAL INFORMATION I will add more info later, after some more searching. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 446793] When I switch to Wayland, the Plasma crashed.
https://bugs.kde.org/show_bug.cgi?id=446793 Petros changed: What|Removed |Added CC||petross...@gmail.com --- Comment #1 from Petros --- > Graphic Card: Zotac GT220-1GD3HG Just a lucky guess: That's an old nvidia gpu. I am afraid the drivers that are supporting these cards are rather old and have many issues with wayland. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 439375] The font management kcm is missing from system settings in wayland session
https://bugs.kde.org/show_bug.cgi?id=439375 Petros changed: What|Removed |Added CC||psamar...@gmail.com --- Comment #3 from Petros --- I have just tried plasma wayland and it seems Fonts are present, visible and usable. I have installed sddm-wayland-git and enabled wayland on sddm (although I have not confirmed yet it really runs on it). I think Fonts were working, even before this, but my memory is not strong enough... Operating System: Arch Linux KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.2 Kernel Version: 5.14.7-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 8 × AMD Ryzen 5 3500U with Radeon Vega Mobile Gfx Memory: 6.7 GiB of RAM Graphics Processor: AMD Radeon™ Vega 8 Graphics -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 442974] New: KDevelop crash when I filtering a class though the Class Browser ToolView
https://bugs.kde.org/show_bug.cgi?id=442974 Bug ID: 442974 Summary: KDevelop crash when I filtering a class though the Class Browser ToolView Product: kdevelop Version: 5.6.2 Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: petross...@gmail.com Target Milestone: --- Application: kdevelop (5.6.2) (Compiled from sources) Qt Version: 5.15.2 Frameworks Version: 5.86.0 Operating System: Linux 5.13.7-gentoo x86_64 Windowing System: X11 Drkonqi Version: 5.22.5 Distribution: "Gentoo Base System release 2.7" -- Information about the crash: - What I was doing when the application crashed: KDevelop crashed when I filtered a class though the Class Browser ToolView. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: KDevelop (kdevelop), signal: Segmentation fault [KCrash Handler] #4 0x7f211fd5675d in ClassModelNodes::ClassNode::updateClassDeclarations() (this=this@entry=0x55a98ee6fb90) at /tmp/portage/dev-util/kdevelop-5.6.2/work/kdevelop-5.6.2/kdevplatform/language/classmodel/classmodelnode.cpp:163 #5 0x7f211fd57201 in ClassModelNodes::ClassNode::populateNode() (this=0x55a98ee6fb90) at /tmp/portage/dev-util/kdevelop-5.6.2/work/kdevelop-5.6.2/kdevplatform/language/classmodel/classmodelnode.cpp:139 #6 0x7f211fd575ed in ClassModelNodes::DynamicNode::performPopulateNode(bool) (this=0x55a98ee6fb90, a_forceRepopulate=) at /tmp/portage/dev-util/kdevelop-5.6.2/work/kdevelop-5.6.2/kdevplatform/language/classmodel/classmodelnode.cpp:555 #7 0x7f2121254542 in () at /usr/lib64/libQt5Core.so.5 #8 0x7f2122140b72 in QTreeView::expanded(QModelIndex const&) () at /usr/lib64/libQt5Widgets.so.5 #9 0x7f212214d016 in QTreeViewPrivate::expand(int, bool) () at /usr/lib64/libQt5Widgets.so.5 #10 0x7f212214d228 in QTreeView::expand(QModelIndex const&) () at /usr/lib64/libQt5Widgets.so.5 #11 0x7f20fc403965 in ClassTree::itemActivated(QModelIndex const&) (this=0x55a9838884d0, index=...) at /tmp/portage/dev-util/kdevelop-5.6.2/work/kdevelop-5.6.2/plugins/classbrowser/classtree.cpp:145 #12 0x7f2121254542 in () at /usr/lib64/libQt5Core.so.5 #13 0x7f21220d0765 in QAbstractItemView::activated(QModelIndex const&) () at /usr/lib64/libQt5Widgets.so.5 #14 0x7f21220d483b in QAbstractItemView::mouseReleaseEvent(QMouseEvent*) () at /usr/lib64/libQt5Widgets.so.5 #15 0x7f2121e9e6ac in QWidget::event(QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #16 0x7f2121f4ddee in QFrame::event(QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #17 0x7f212121fa8b in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5 #18 0x7f2121e5b8ce in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #19 0x7f2121e6318b in QApplication::notify(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #20 0x7f212121fcc3 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5 #21 0x7f2121e61fbd in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool, bool) () at /usr/lib64/libQt5Widgets.so.5 #22 0x7f2121eb7d7c in () at /usr/lib64/libQt5Widgets.so.5 #23 0x7f2121ebaf9c in () at /usr/lib64/libQt5Widgets.so.5 #24 0x7f2121e5b8e5 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #25 0x7f212121fcc3 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5 #26 0x7f2121731e80 in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () at /usr/lib64/libQt5Gui.so.5 #27 0x7f2121711e73 in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () at /usr/lib64/libQt5Gui.so.5 #28 0x7f210da2621a in () at /usr/lib64/libQt5XcbQpa.so.5 #29 0x7f211d8ca4f0 in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0 #30 0x7f211d8ca9c0 in () at /usr/lib64/libglib-2.0.so.0 #31 0x7f211d8caa6f in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #32 0x7f2121273bb4 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #33 0x7f212121e713 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #34 0x7f2121226acd in QCoreApplication::exec() () at /usr/lib64/libQt5Core.so.5 #35 0x55a98127484a in main(int, char**) (argc=, argv=) at /tmp/portage/dev-util/kdevelop-5.6.2/work/kdevelop-5.6.2/app/main.cpp:850 [Inferior 1 (process 6165) detached] Possible duplicates by query: bug 425618, bug 406931, bug 273355. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 438552] When switching desktops, applications can not be focused anymore and leave a ghost
https://bugs.kde.org/show_bug.cgi?id=438552 Petros changed: What|Removed |Added CC||psamar...@gmail.com --- Comment #12 from Petros --- Original report is with Intel video driver. Is it the same driver for the rest of the confirmed cases? Also, check if the modesetting module is used instead of intel. There is a similar report in Garuda forum. Archwiki has a similar troubleshooting https://wiki.archlinux.org/title/Intel_graphics#DRI3_issues , suggesting a drop to DRI2. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected
https://bugs.kde.org/show_bug.cgi?id=356225 Petros changed: What|Removed |Added CC||psamar...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 395476] The minimum window size of System Settings is too big for a 1366x768 screen
https://bugs.kde.org/show_bug.cgi?id=395476 Petros changed: What|Removed |Added CC||psamar...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 436635] New: nm-applet AGAIN "shows absurdedly high speeds on first update" for WiFi
https://bugs.kde.org/show_bug.cgi?id=436635 Bug ID: 436635 Summary: nm-applet AGAIN "shows absurdedly high speeds on first update" for WiFi Product: plasma-nm Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: applet Assignee: jgrul...@redhat.com Reporter: psamar...@gmail.com Target Milestone: --- SUMMARY Opening the Network applet’s speed graph AGAIN shows absurdly high speeds after initial applet show-up. It was supposed to have been fixed with https://invent.kde.org/plasma/plasma-nm/-/commit/30b4a718404a4a6c06fe903cba09ca702175a78c STEPS TO REPRODUCE 1. Click on network applet on plasma panel system tray 2. Click on active wifi network 3. OBSERVED RESULT An initial extreme spike of the graph at speeds over 10ths of MBs, while my line's max speed is 800kbps. After the instant spike, the graph shows expected values, but they are almost invisible at the lowest rate, having to keep the applet open for several seconds, for the graph to come sane. EXPECTED RESULT The network speed graph shows real/correct speed values, (even a small initial delay is prefered) SOFTWARE/OS VERSIONS Linux/KDE Plasma: Operating System: Arch Linux KDE Plasma Version: 5.21.5 KDE Frameworks Version: 5.81.0 Qt Version: 5.15.2 Kernel Version: 5.11.16-arch1-1 OS Type: 64-bit Graphics Platform: X11 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 436052] Malformed URL for bugs.kde.org at About "application" page, when using a non-English locale
https://bugs.kde.org/show_bug.cgi?id=436052 --- Comment #1 from Petros --- Ha, ha, ha!!! Reading again what I just wrote, I recognized the ~possible~ actual problem. > clipboard pastes https//bugs.kde.org which misses ":" from the protocol!!! -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 436052] New: Malformed URL for bugs.kde.org at About "application" page, when using a non-English locale
https://bugs.kde.org/show_bug.cgi?id=436052 Bug ID: 436052 Summary: Malformed URL for bugs.kde.org at About "application" page, when using a non-English locale Product: frameworks-kio Version: 5.81.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: general Assignee: kio-bugs-n...@kde.org Reporter: psamar...@gmail.com CC: kdelibs-b...@kde.org Target Milestone: --- SUMMARY **This happens in Greek locale. I started apps with LANG=en and the link is proper.** In any KDE application's About page, in Authors tab, there is an active link for kde.bugs.org. Clicking the link directs to a malformed URL address: https://www.https.com//bugs.kde.org STEPS TO REPRODUCE 1. Set your session LANG to el_GR.UTF-8 (or possibly other non-English locale) 2. Start any KDE application, i.e. Dolphin 3. Open menu Help => About Dolphin 4. Go to Authors tab 5. Click on the link to https//bugs.kde.org OBSERVED RESULT Default web browser (FF) opens page https://www.https.com//bugs.kde.org EXPECTED RESULT Default web browser opens page https://bugs.kde.org SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.21.4 KDE Frameworks Version: 5.81.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION I tested other links in similar window/tabs, but I haven't found any other to do the same. If I right-click on the link and select "Copy link location" clipboard pastes https//bugs.kde.org (to my surprise!!) -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 436048] New: Non English missing main menu translation showed as "No text"
https://bugs.kde.org/show_bug.cgi?id=436048 Bug ID: 436048 Summary: Non English missing main menu translation showed as "No text" Product: okular Version: 20.12.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: psamar...@gmail.com Target Milestone: --- Created attachment 137799 --> https://bugs.kde.org/attachment.cgi?id=137799=edit Screenshot of the menu showing the issue with wrong text SUMMARY I use kde/okular with a Greek user locale in Archlinux. After v.20.12 (I am not sure which "point" release, as I was waiting for a fix, sorry) 3 base menus' text (File, Tools, Help) were appearing with "Χωρίς κείμενο" (No text) as text, instead of maybe an English translation. As it is too basic translation that does not change normally, it must be some accidental "bug". STEPS TO REPRODUCE 1. Start a KDE session with Greek $LANG/$LC_MESSAGES=el_GR.UTF-8 2. Start okular 3. OBSERVED RESULT Menus that should be Αρχείο/File, Εργαλεία/Tools, Βοήθεια/Help have this text: "Χωρίς κείμενο" EXPECTED RESULT Menus that should be Αρχείο/File, Εργαλεία/Tools, Βοήθεια/Help have the proper relevant text. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.21.4 KDE Frameworks Version: 5.81.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION I use latte-dock with latte Window Appmenu for the menu system. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 414501] Cannot type accented characters (í, ã, etc) in any text fields in QML KCMs embedded in QWidgets view (works in the sidebar's text field)
https://bugs.kde.org/show_bug.cgi?id=414501 --- Comment #8 from Petros --- This has been fixed for me. Operating System: Arch Linux KDE Plasma Version: 5.21.3 KDE Frameworks Version: 5.80.0 Qt Version: 5.15.2 Kernel Version: 5.10.25-1-lts OS Type: 64-bit Graphics Platform: X11 Processors: 8 × AMD Ryzen 5 3500U with Radeon Vega Mobile Gfx Memory: 6.8 GiB of RAM Graphics Processor: AMD Radeon™ Vega 8 Graphics -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 425384] Yakuake jumps between displays since 20.08.0
https://bugs.kde.org/show_bug.cgi?id=425384 --- Comment #10 from Petros --- I want to add some info about my setup, which I think experiences the same bug. Laptop eDP connected primary 1920x1080+0+0 @60.01 same as preferred External HDMI-A-0 connected 1920x1080+1920+0 @60.00 preferred is 1680x1050 @59.95 On Primary Yakuake behaves as configured with single monitor, centered. On external it snaps/aligns at left monitor edge. While external is focused and yakuake open, I open settings and change screen alignment to left or right. After saving, yakuake uses the saved setting but assumes there is one monitor the size of X Screen (2 monitors side by side). Yakuake: yakuake 20.12.0(-1) Operating System: Arch Linux KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.77.0 Qt Version: 5.15.2 Kernel Version: 5.10.4-arch2-1 OS Type: 64-bit Processors: 8 × AMD Ryzen 5 3500U with Radeon Vega Mobile Gfx Memory: 6.8 GiB of RAM Graphics Processor: AMD Radeon™ Vega 8 Graphics -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 425384] Yakuake jumps between displays since 20.08.0
https://bugs.kde.org/show_bug.cgi?id=425384 --- Comment #9 from Petros --- Created attachment 134633 --> https://bugs.kde.org/attachment.cgi?id=134633=edit yakuake aligned left on the monitor at right -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 425384] Yakuake jumps between displays since 20.08.0
https://bugs.kde.org/show_bug.cgi?id=425384 Petros changed: What|Removed |Added CC||psamar...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 412477] meson support not working when meson is a symlink
https://bugs.kde.org/show_bug.cgi?id=412477 --- Comment #4 from Petros --- (In reply to Ihor Antonov from comment #3) > Yes. After reading meson quick start guide I learned that meson can be used > directly from its git repository: > https://mesonbuild.com/Quick-guide.html#installation-from-source > > So I cloned https://github.com/mesonbuild/meson into some directory and > pointed KDevelop at meson in that directory > > - > WORKAROUND: > 1. clone https://github.com/mesonbuild/meson > 2. in KDevelop when setting up meson project use meson.py that you obtain at > step #1 as meson binary Thank you. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 412477] meson support not working when meson is a symlink
https://bugs.kde.org/show_bug.cgi?id=412477 Petros changed: What|Removed |Added CC||petross...@gmail.com --- Comment #2 from Petros --- (In reply to Ihor Antonov from comment #1) > End of year 2020 > The problem still exists. > > Gentoo > > /usr/lib/python-exec/python-exec2 --backend ninja /home/.../project/build > /usr/lib/python-exec/python-exec2: python-exec2 is a wrapper, it must not be > run directly > *** Failure: Exit code 127 *** Same here, I am using KDevelop-5.6.1, meson-0.55.3 and I am getting the same error. Is there any temporary workaround? -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 422362] Request for a dark mode - option to set dark background/light font in article preview and in internal browser
https://bugs.kde.org/show_bug.cgi?id=422362 Petros changed: What|Removed |Added CC||psamar...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 365315] akregator can only show the feeds in a white background with black fonts.
https://bugs.kde.org/show_bug.cgi?id=365315 Petros changed: What|Removed |Added CC||psamar...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 403093] breeze dark => akregator background is full white
https://bugs.kde.org/show_bug.cgi?id=403093 Petros changed: What|Removed |Added CC||psamar...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 422808] systemsettings5 crashes on closing window
https://bugs.kde.org/show_bug.cgi?id=422808 Petros changed: What|Removed |Added CC||psamar...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 420570] Clang on MacOS can't find ~/Library/Application Support/kdevscratchpad/... because it contains whitespace
https://bugs.kde.org/show_bug.cgi?id=420570 Petros changed: What|Removed |Added Platform|Other |Homebrew (macOS) -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 420570] New: Clang on MacOS can't find ~/Library/Application Support/kdevscratchpad/... because it contains whitespace
https://bugs.kde.org/show_bug.cgi?id=420570 Bug ID: 420570 Summary: Clang on MacOS can't find ~/Library/Application Support/kdevscratchpad/... because it contains whitespace Product: kdevelop Version: git master Platform: Other OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: Plugin: Scratchpad Assignee: kdevelop-bugs-n...@kde.org Reporter: petross...@gmail.com Target Milestone: --- SUMMARY Clang can't compile code under this dir because it understands two separate directories. STEPS TO REPRODUCE 1. Open the scratchpad toolview 2. Write a small c/c++ example 3. Tap/click the cursor on the command to run the example and hit enter. OBSERVED RESULT Running /bin/sh -c g++ -std=c++11 -o /tmp/a.out /Users/petros/Library/Application Support/kdevscratchpad/scratches/typeid.cpp && /tmp/a.out... clang: error: no such file or directory: '/Users/petros/Library/Application' clang: error: no such file or directory: 'Support/kdevscratchpad/scratches/typeid.cpp' clang: error: no input files Process finished with exit code 1. EXPECTED RESULT Clang should be able to follow the path and find the file.cpp to compile it. SOFTWARE/OS VERSIONS macOS: Catalina Qt Version: qt: stable 5.14.1 (bottled) ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 416889] Latte Dock jumps up-down when attached at left or right edge of screen
https://bugs.kde.org/show_bug.cgi?id=416889 --- Comment #3 from Petros --- Refreshed repoDBs and updated to latte-dock 0.9.8.1-1 Confirmed fixed! Thanks! --- FWIW, AUR git did not help (as warned...). -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 416889] Latte Dock jumps up-down when attached at left or right edge of screen
https://bugs.kde.org/show_bug.cgi?id=416889 --- Comment #2 from Petros --- I still have the repo version. I may try AUR. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 416889] New: Latte Dock jumps up-down when attached at left or right edge of screen
https://bugs.kde.org/show_bug.cgi?id=416889 Bug ID: 416889 Summary: Latte Dock jumps up-down when attached at left or right edge of screen Product: lattedock Version: 0.9.8 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: psamar...@gmail.com Target Milestone: --- SUMMARY Using Unity layout on single monitor (laptop), the left side latte dock is jumping up and down continuously. When set to bottom screen edge, there is no issue. I cleaned latte cache (--cc) without improvement. As it happened right after it was updated, I downgraded to 0.9.7-1 which behaves properly (no issue). STEPS TO REPRODUCE 1. Start latte-dock 2. Set Unity layout, or place any panel or dock at the left or right side of screen 3. OBSERVED RESULT The panel/dock is jumping up and down continuously. EXPECTED RESULT The panel/dock is stable (not jumping up and down) SOFTWARE/OS VERSIONS Operating System: Arch Linux (Stable) KDE Plasma Version: 5.17.5 KDE Frameworks Version: 5.66.0 Qt Version: 5.14.0 Kernel Version: 4.19.99-1-lts OS Type: 64-bit Processors: 4 × Intel® Core™ i3 CPU M 380 @ 2.53GHz Memory: 7,5 GiB ADDITIONAL INFORMATION latte-dock 0.9.8-1 It is a new clean Archlinux installation, new/fresh user. I could not record video of this, or... more accurately, Latte was not included in my recorded video (giph, recordmydesktop, silentcast) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 414501] No accented characters in Desktop Effects filter
https://bugs.kde.org/show_bug.cgi?id=414501 --- Comment #2 from Petros --- (In reply to Vlad Zahorodnii from comment #1) > Created attachment 125280 [details] > run with `qmlscene test.qml` > > Can you run the attached "app" and check whether you're able to type in > accented Greek characters there? I did and I succeeded writing accented Greek chars as expected. My system has changed (to Arch) but the issue still exists. Also happened occasionally in the SystemSettings main filter textbox, but randomly, which is frustrating... Current KDE info: Operating System: Arch Linux KDE Plasma Version: 5.17.5 KDE Frameworks Version: 5.66.0 Qt Version: 5.14.0 Kernel Version: 4.19.96-1-lts OS Type: 64-bit Processors: 4 × Intel® Core™ i3 CPU M 380 @ 2.53GHz Memory: 7,5 GiB -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 412940] [qt 5.14] - dock background and rearrange button are not removed when settings panel closed
https://bugs.kde.org/show_bug.cgi?id=412940 --- Comment #21 from Petros --- I installed (again) latte-dock-git just to see this fixed! Fix confirmed! Thanks a lot Michalis. Happy new year!! -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 412940] [qt 5.14] - dock background and rearrange button are not removed when settings panel closed
https://bugs.kde.org/show_bug.cgi?id=412940 --- Comment #18 from Petros --- Created attachment 124786 --> https://bugs.kde.org/attachment.cgi?id=124786=edit Debug output from latte-dock --cc -r -d Same bug, since some days. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 412940] [qt 5.14] - dock background and rearrange button are not removed when settings panel closed
https://bugs.kde.org/show_bug.cgi?id=412940 Petros changed: What|Removed |Added CC||psamar...@gmail.com --- Comment #17 from Petros --- Created attachment 124785 --> https://bugs.kde.org/attachment.cgi?id=124785=edit My System info -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 415572] kdevelop-pg-qt build error on brew (MAC OS) struct hash< QT_PREPEND_NAMESPACE(Class) > 1 error generated
https://bugs.kde.org/show_bug.cgi?id=415572 --- Comment #1 from Petros --- I have to add that brew install kdevelop-pg-qt --HEAD completes and the compilation is successful. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 415572] kdevelop-pg-qt build error on brew (MAC OS) struct hash< QT_PREPEND_NAMESPACE(Class) > 1 error generated
https://bugs.kde.org/show_bug.cgi?id=415572 Petros changed: What|Removed |Added Platform|Other |Homebrew (macOS) Version|unspecified |5.4.5 OS|Linux |macOS -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 415572] New: kdevelop-pg-qt build error on brew (MAC OS) struct hash< QT_PREPEND_NAMESPACE(Class) > 1 error generated
https://bugs.kde.org/show_bug.cgi?id=415572 Bug ID: 415572 Summary: kdevelop-pg-qt build error on brew (MAC OS) struct hash< QT_PREPEND_NAMESPACE(Class) > 1 error generated Product: kdevelop Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: petross...@gmail.com Target Milestone: --- SUMMARY Trying to install kdevelop on Mac OS Catalina with brew fails, because kdevelop-pg-qt can't be built. STEPS TO REPRODUCE 1. brew install kdevelop OBSERVED RESULT The following link contains the build log. https://gist.github.com/Petross404/65e3026ddcd6d214b7ca7c2741f8402d SOFTWARE/OS VERSIONS macOS: Catalina KDE Frameworks Version: 5.65 Qt Version: 5.14 ADDITIONAL INFORMATION I am using this tap : https://github.com/KDE-mac/homebrew-kde -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 414501] New: No accented characters in Desktop Effects filter
https://bugs.kde.org/show_bug.cgi?id=414501 Bug ID: 414501 Summary: No accented characters in Desktop Effects filter Product: systemsettings Version: 5.17.3 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: psamar...@gmail.com Target Milestone: --- SUMMARY In System Settings => Desktop Behavior => Desktop Effects, when entering an accented Greek character, it is always showed/transformed(?) to the non-accented equivalent. For example: ό => ο, ά => α, Ό => Ο etc... STEPS TO REPRODUCE 1. Start System Settings => Desktop Behavior => Desktop Effects 2. Move focus to the Search Filter box/area 3. Enter any accented character pressing the key combination OBSERVED RESULT The equivalent non-accented character is produced in the filter area. EXPECTED RESULT The accented character is produced in the filter area. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro Testing (available in About System) KDE Plasma Version: 5.17.3 KDE Frameworks Version: 5.64.0 Qt Version: 5.13.2 ADDITIONAL INFORMATION I only tested with Greek Language characters. Filtering is applied properly, for the ... produced characters. I could not get to a target word that included an accented character. I tested more "filter" areas in System Settings and on kRunner and there was no such problem. IMHO at least for the Greek language, when using a search filter, a non-accented character "should" find the accented characters as well as the non-accented. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 414426] New: KDevelop crashed when I closed an qt *.ui in KUIViewerPart
https://bugs.kde.org/show_bug.cgi?id=414426 Bug ID: 414426 Summary: KDevelop crashed when I closed an qt *.ui in KUIViewerPart Product: kdevelop Version: 5.4.3 Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: petross...@gmail.com Target Milestone: --- Application: kdevelop (5.4.3) (Compiled from sources) Qt Version: 5.13.2 Frameworks Version: 5.63.0 Operating System: Linux 4.17.4-aufs x86_64 Distribution: "Gentoo Base System release 2.6" -- Information about the crash: - What I was doing when the application crashed: I opened an *.ui file and when I closed it, KDevelop crashed. It happened every time. I have to be carefull to not accidentally open an ui file in KDevelop but rather in QtDesigner. The crash can be reproduced every time. -- Backtrace: Application: KDevelop (kdevelop), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f551abc82c0 (LWP 10836))] Thread 26 (Thread 0x7f5476ffd700 (LWP 11087)): #0 0x7f552b408ad3 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f552e3cb35b in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib64/libQt5Core.so.5 #2 0x7f552e3d0501 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #3 0x7f552a8b9850 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #4 0x7f552a8b5390 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #5 0x7f552a8b58aa in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #6 0x7f552a8b53fd in () at /usr/lib64/libKF5ThreadWeaver.so.5 #7 0x7f552a8b58aa in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #8 0x7f552a8b53fd in () at /usr/lib64/libKF5ThreadWeaver.so.5 #9 0x7f552a8b58aa in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #10 0x7f552a8b53fd in () at /usr/lib64/libKF5ThreadWeaver.so.5 #11 0x7f552a8b58aa in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #12 0x7f552a8b53fd in () at /usr/lib64/libKF5ThreadWeaver.so.5 #13 0x7f552a8b58aa in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #14 0x7f552a8b53fd in () at /usr/lib64/libKF5ThreadWeaver.so.5 #15 0x7f552a8b58aa in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #16 0x7f552a8b53fd in () at /usr/lib64/libKF5ThreadWeaver.so.5 #17 0x7f552a8b58aa in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #18 0x7f552a8b53fd in () at /usr/lib64/libKF5ThreadWeaver.so.5 #19 0x7f552a8b58aa in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #20 0x7f552a8b53fd in () at /usr/lib64/libKF5ThreadWeaver.so.5 #21 0x7f552a8b58aa in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #22 0x7f552a8b53fd in () at /usr/lib64/libKF5ThreadWeaver.so.5 #23 0x7f552a8b58aa in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #24 0x7f552a8b53fd in () at /usr/lib64/libKF5ThreadWeaver.so.5 #25 0x7f552a8b58aa in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #26 0x7f552a8b5595 in ThreadWeaver::Thread::run() () at /usr/lib64/libKF5ThreadWeaver.so.5 #27 0x7f552e3d6ca0 in () at /usr/lib64/libQt5Core.so.5 #28 0x7f552b4014b7 in start_thread () at /lib64/libpthread.so.0 #29 0x7f552dd7266f in clone () at /lib64/libc.so.6 Thread 25 (Thread 0x7f54777fe700 (LWP 11086)): #0 0x7f552b408ad3 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f552e3cb35b in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib64/libQt5Core.so.5 #2 0x7f552e3d0501 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #3 0x7f552a8b9850 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #4 0x7f552a8b5390 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #5 0x7f552a8b58aa in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #6 0x7f552a8b53fd in () at /usr/lib64/libKF5ThreadWeaver.so.5 #7
[kdevelop] [Bug 414193] KDevelop crashes when it opens a project
https://bugs.kde.org/show_bug.cgi?id=414193 --- Comment #1 from Petros --- Re-emerging qtwebengine and kdevelop solved the problem. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 414194] New: Kontact crashes upon startup
https://bugs.kde.org/show_bug.cgi?id=414194 Bug ID: 414194 Summary: Kontact crashes upon startup Product: kontact Version: 5.12.2 Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: petross...@gmail.com Target Milestone: --- Application: kontact (5.12.2) (Compiled from sources) Qt Version: 5.13.2 Frameworks Version: 5.63.0 Operating System: Linux 4.17.4-aufs x86_64 Distribution: "Gentoo Base System release 2.6" -- Information about the crash: As soon as I open up kontact, it crashes for no reason. It happens every time. The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7faee3c73a00 (LWP 11163))] Thread 3 (Thread 0x7faedbf04700 (LWP 11214)): #0 0x7faef34cee69 in () at /usr/lib64/libglib-2.0.so.0 #1 0x7faef34d022b in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #2 0x7faef34d092b in () at /usr/lib64/libglib-2.0.so.0 #3 0x7faef34d0acf in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7faef53a982b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7faef53fc423 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7faef558c9e1 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #7 0x7faef4a24857 in () at /usr/lib64/libQt5DBus.so.5 #8 0x7faef558cca0 in () at /usr/lib64/libQt5Core.so.5 #9 0x7faef40864b7 in start_thread () at /lib64/libpthread.so.0 #10 0x7faef4f0f66f in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7faee3520700 (LWP 11193)): #0 0x7faef4f03053 in poll () at /lib64/libc.so.6 #1 0x7faef40c5cb2 in () at /usr/lib64/libxcb.so.1 #2 0x7faef40c69ca in xcb_wait_for_event () at /usr/lib64/libxcb.so.1 #3 0x7faee3645fb0 in () at /usr/lib64/libQt5XcbQpa.so.5 #4 0x7faef558cca0 in () at /usr/lib64/libQt5Core.so.5 #5 0x7faef40864b7 in start_thread () at /lib64/libpthread.so.0 #6 0x7faef4f0f66f in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7faee3c73a00 (LWP 11163)): [KCrash Handler] #6 0x7faef4e3eb84 in raise () at /lib64/libc.so.6 #7 0x7faef4e2656c in abort () at /lib64/libc.so.6 #8 0x7faef5330c65 in () at /usr/lib64/libQt5Core.so.5 #9 0x7faeeb5c60e9 in () at /usr/lib64/libQt5WebEngineCore.so.5 #10 0x7faeeb5c6bad in () at /usr/lib64/libQt5WebEngineCore.so.5 #11 0x7faeeb5c8c24 in () at /usr/lib64/libQt5WebEngineCore.so.5 #12 0x7faef48a9e43 in () at /usr/lib64/libQt5WebEngineWidgets.so.5 #13 0x7faef48a5653 in QWebEnginePage::QWebEnginePage(QObject*) () at /usr/lib64/libQt5WebEngineWidgets.so.5 #14 0x7faef6628ecd in Kontact::MainWindow::initAboutScreen() () at /usr/lib64/libkontactprivate.so.5 #15 0x7faef662f62a in Kontact::MainWindow::initWidgets() () at /usr/lib64/libkontactprivate.so.5 #16 0x7faef662f7ed in Kontact::MainWindow::initGUI() () at /usr/lib64/libkontactprivate.so.5 #17 0x7faef662fc34 in Kontact::MainWindow::MainWindow() () at /usr/lib64/libkontactprivate.so.5 #18 0x563c7b3b2bb2 in () #19 0x7faef65f2606 in KontactInterface::PimUniqueApplication::start(QStringList const&) () at /usr/lib64/libKF5KontactInterface.so.5 #20 0x563c7b3b1320 in () #21 0x7faef4e27eae in __libc_start_main () at /lib64/libc.so.6 #22 0x563c7b3b1d6a in () [Inferior 1 (process 11163) detached] Possible duplicates by query: bug 414147, bug 414137, bug 414102, bug 413978, bug 413943. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 414193] New: KDevelop crashes when it opens a project
https://bugs.kde.org/show_bug.cgi?id=414193 Bug ID: 414193 Summary: KDevelop crashes when it opens a project Product: kdevelop Version: 5.4.3 Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: petross...@gmail.com Target Milestone: --- Application: kdevelop (5.4.3) (Compiled from sources) Qt Version: 5.13.2 Frameworks Version: 5.63.0 Operating System: Linux 4.17.4-aufs x86_64 Distribution: "Gentoo Base System release 2.6" -- Information about the crash: - What I was doing when the application crashed: My system load is irrelevant. It crashes even my when pc is running nothing more than just a konsole. The crash can be reproduced every time. -- Backtrace: Application: KDevelop (kdevelop), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f2992116f00 (LWP 11588))] Thread 8 (Thread 0x7f2972b3d700 (LWP 14077)): #0 0x7f29a0f80fe1 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #1 0x7f29a0f829a3 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f29a0f82acf in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f29a484282b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f29a4895423 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f29a4a259e1 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f29a4a25ca0 in () at /usr/lib64/libQt5Core.so.5 #7 0x7f29a1a4c4b7 in start_thread () at /lib64/libpthread.so.0 #8 0x7f29a43c166f in clone () at /lib64/libc.so.6 Thread 7 (Thread 0x7f2973602700 (LWP 13882)): #0 0x7f29a1a53e08 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f29a4a1a28b in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib64/libQt5Core.so.5 #2 0x7f29a4a1f4c7 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #3 0x7f29a4a1fb8f in () at /usr/lib64/libQt5Core.so.5 #4 0x7f29a4a25ca0 in () at /usr/lib64/libQt5Core.so.5 #5 0x7f29a1a4c4b7 in start_thread () at /lib64/libpthread.so.0 #6 0x7f29a43c166f in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7f2980847700 (LWP 13701)): #0 0x7f29a43b5053 in poll () at /lib64/libc.so.6 #1 0x7f29a0f829f9 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f29a0f82acf in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f29a484282b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f29a4895423 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f29a4a259e1 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f29a4a25ca0 in () at /usr/lib64/libQt5Core.so.5 #7 0x7f29a1a4c4b7 in start_thread () at /lib64/libpthread.so.0 #8 0x7f29a43c166f in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7f2981048700 (LWP 13674)): #0 0x7f29a0f810c5 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #1 0x7f29a0f829a3 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f29a0f82acf in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f29a484282b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f29a4895423 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f29a4a259e1 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f29a4a25ca0 in () at /usr/lib64/libQt5Core.so.5 #7 0x7f29a1a4c4b7 in start_thread () at /lib64/libpthread.so.0 #8 0x7f29a43c166f in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7f2983fff700 (LWP 13338)): #0 0x7f29a0f2f2e4 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0 #1 0x7f29a0f795ee in g_main_context_query () at /usr/lib64/libglib-2.0.so.0 #2 0x7f29a0f82978 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7f29a0f82acf in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7f29a484282b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f29a4895423 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f29a4a259e1 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #7 0x7f29a3420f0c in () at /usr/lib64/libKDevPlatformLanguage.so.54 #8 0x7f29a4a25ca0 in () at /usr/lib64/libQt5Core.so.5 #9 0x7f29a1a4c4b7 in start_thread () at /lib64/libpthread.so.0 #10 0x7f29a43c166f in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7f298a1f7700 (LWP 11794)): #0 0x7ffd2c3eb929 in () #1 0x7ffd2c3ebaed in clock_gettime () #2 0x7f29a43d0697 in clock_gettime () at /lib64/libc.so.6 #3 0x7f29a48438a1 in () at /usr/lib64/libQt5Core.so.5 #4 0x7f29a4843d69 in QTimerInfoList::updateCurrentTime() () at
[kdevplatform] [Bug 410541] New: LLDB on windows can't start the executable
https://bugs.kde.org/show_bug.cgi?id=410541 Bug ID: 410541 Summary: LLDB on windows can't start the executable Product: kdevplatform Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: debugger Assignee: kdevelop-bugs-n...@kde.org Reporter: petross...@gmail.com CC: niko.s...@gmail.com Target Milestone: --- SUMMARY I am running KDevelop from the nightly builds on Windows 10. I needed to debug a small program of mine and I noticed that LLDB wants to start project_name, while on windows my executable is named as project_name.exe. STEPS TO REPRODUCE 1. Debug under windows 2. LLDB can't find your executable since it doesn't append the .exe 3. OBSERVED RESULT Doesn't debug since it can't find the required file (executable) EXPECTED RESULT Correctly search and find my executable under various platforms SOFTWARE/OS VERSIONS Windows: 10 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 377291] KDevelop doesn't allow me to modify a variable's value, when stepping though the code in Debug
https://bugs.kde.org/show_bug.cgi?id=377291 --- Comment #4 from Petros --- Any news in this? Is it a regression or just a missing, non-useful feature? -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 410269] New: Code completion doesn't work with designated initializers in C99
https://bugs.kde.org/show_bug.cgi?id=410269
Bug ID: 410269
Summary: Code completion doesn't work with designated
initializers in C99
Product: kdevelop
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Code completion
Assignee: kdevelop-bugs-n...@kde.org
Reporter: petross...@gmail.com
Target Milestone: ---
SUMMARY
I have this code:
typedef struct{
chara_c;
charb_c;
} chars;
chars c_array [] =
{
{.a_c = 'a', .b_c = 'b'}
};
Although the struct members are parsed after all, while I am typing them, I get
zero hints from the IDE.
OBSERVED RESULT
No code completion for designated initializers in C99.
EXPECTED RESULT
IDE should give a hint about what members struct Foo has.
C profile is set to C99 in parser settings.
--
You are receiving this mail because:
You are watching all bug changes.
[kdevelop] [Bug 410070] New: KDevelop should allow multi-line scripts or standardize a location for .sh files to be stored.
https://bugs.kde.org/show_bug.cgi?id=410070 Bug ID: 410070 Summary: KDevelop should allow multi-line scripts or standardize a location for .sh files to be stored. Product: kdevelop Version: unspecified Platform: Other OS: All Status: REPORTED Severity: wishlist Priority: NOR Component: UI: general Assignee: kdevelop-bugs-n...@kde.org Reporter: petross...@gmail.com Target Milestone: --- SUMMARY I want to create a custom script which will create the assembly output of my program. I noticed that while KDevelop has got me covered with it's variables (%u, %f...), it's kinda cramped in there if you want to write 2 or more bash commands. I am not talking about tenths of bash lines, but it would be nice to have some space for an if-fi or a kdialog. Either this, or the user will store a bash script (*.sh) in a standard directory so KDevelop can pick (or even edit) it up. Imho the second choice is more and flexible. A QComboBox would list all the scripts that are stored in directory "foo" and a small "Edit..." QPushButton, will open the script in KDevelop. PS. I know a script might not be the best solution for me to print assembly. I don't think we should debate whether a plugin should do a better job or if the user shouldn't want from the IDE custom things. IMO we should focus on whether a feature should be more flexible and mature for the user. The latter should use it in any way. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 407351] i18n ARGUMENT MISSING in task preview window
https://bugs.kde.org/show_bug.cgi?id=407351 --- Comment #3 from Petros --- Created attachment 119922 --> https://bugs.kde.org/attachment.cgi?id=119922=edit changed font -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 407351] i18n ARGUMENT MISSING in task preview window
https://bugs.kde.org/show_bug.cgi?id=407351 --- Comment #2 from Petros --- After more research (and guessing...) I find the issue might be related to fonts. I was using a custom font (Lato), downloaded and manually installed via System Settings - Fonts. Changing font to "Liberation Sans" (or other "known" font) changes the issue to something else, not sure it's fixed. Now the "broken" line shows "O..." (capital O with 3 dots, like truncation). I can assume it's the 1st letter of the same text string (On ). As I said I am not sure this is related/fixing, until new feedback/replication. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 407351] i18n ARGUMENT MISSING in task preview window
https://bugs.kde.org/show_bug.cgi?id=407351 --- Comment #1 from Petros --- Created attachment 119921 --> https://bugs.kde.org/attachment.cgi?id=119921=edit initial issue -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 407351] New: i18n ARGUMENT MISSING in task preview window
https://bugs.kde.org/show_bug.cgi?id=407351 Bug ID: 407351 Summary: i18n ARGUMENT MISSING in task preview window Product: lattedock Version: git (master) Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: psamar...@gmail.com Target Milestone: --- SUMMARY On Tasks thumbnails, the 2nd text line (normally shows "On DESKTOP_NAME") says: On %1(I18n ARGUMENT MISSING) I was using kvantum for widget style and Materia Dark theming. I changed to Breeze for widget style and Breeze Dark theming. With this change I realized the issue was absent on standard Plasma panel/tasks plasmoid. I had already tried another user account (dormant for testing), on which the issue existed for Latte tasks. Did not test this with Plasma default panel/tasks. What I did to investigate: Deleted ~/.cache folder from TTY and logged in Updated to latest packages and rebooted Rebuilt latte-dock-git and relogin Checked with another (rarely used for troubleshooting) user. Here, after some trouble with latte-dock initial crash, the issue was absent. I checked that themes were Breeze default. Changed the theme and some settings to my "normal" account prefs. Then the issue appeared as well. Reverting the theming at the previous settings did not make the issue go away... Checked at KDE bugs with the text "i18n_argument_missing" and nothing similar found. Created topic at Manjaro Forum for more feedback (https://forum.manjaro.org/t/i18n-argument-missing-in-task-preview-window/86613) STEPS TO REPRODUCE 1. Set Tasks to show thumbnails on hover 2. Hover over a running task OBSERVED RESULT 2nd text line shows: "On %1(I18n ARGUMENT MISSING)" EXPECTED RESULT 2nd text line shows: "On " SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro KDE Plasma Version: 5.15.4 KDE Frameworks Version: 5.57.0 Qt Version: 5.12.3 ADDITIONAL INFORMATION Kernel: 5.0.13-1-MANJARO x86_64 WM: kwin_x11 compiler: gcc v: 8.3.0 Theme: Materia, Breeze (tested on both) -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 403589] New: Consider using rust-analyzer which is a rust compiler front-end for IDEs
https://bugs.kde.org/show_bug.cgi?id=403589 Bug ID: 403589 Summary: Consider using rust-analyzer which is a rust compiler front-end for IDEs Product: kdevelop Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Language Support: Rust Assignee: kdevelop-bugs-n...@kde.org Reporter: petross...@gmail.com Target Milestone: --- I thought it would be nice to share this[1] project with KDevelop devs that work on rust support. Perphaps it could provide for rust what libclang does for c++. [1] https://github.com/rust-analyzer/rust-analyzer -- You are receiving this mail because: You are watching all bug changes.
[Craft] [Bug 403527] Trying to install LLVM with Craft gives : 'NoneType' object is not callable
https://bugs.kde.org/show_bug.cgi?id=403527 Petros changed: What|Removed |Added CC||petross...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Craft] [Bug 403527] New: Trying to install LLVM with Craft gives : 'NoneType' object is not callable
https://bugs.kde.org/show_bug.cgi?id=403527
Bug ID: 403527
Summary: Trying to install LLVM with Craft gives : 'NoneType'
object is not callable
Product: Craft
Version: master
Platform: Other
OS: MS Windows
Status: REPORTED
Severity: normal
Priority: NOR
Component: Core
Assignee: vonr...@kde.org
Reporter: petross...@gmail.com
CC: kde-wind...@kde.org
Target Milestone: ---
SUMMARY
I want to build KDE Software on my Windows machine and thus I installed Craft.
But when I try to install LLVM I get :
TypeError: 'NoneType' object is not callable
STEPS TO REPRODUCE
1. Open PowerShell as admin
2. Run the $CRAFTROOT/download/craftmaster/craftenv.ps1 script
3. craft llvm
4. Boom
OBSERVED RESULT
PS C:\CraftRoot\download> craft llvm
Craft : C:\CraftRoot\download
Version : master
ABI : windows-msvc2017_64-cl
Download directory : C:\CraftRoot\download\download
'NoneType' object is not callable
Traceback (most recent call last):
File "C:\CraftRoot\download\craft-master\bin\craft.py", line 250, in
success = main()
File "C:\CraftRoot\download\craft-master\bin\craft.py", line 238, in main
if not CraftCommands.run(package, action, tempArgs):
File "C:\CraftRoot\download\craft-master\bin\CraftCommands.py", line 240, in
run
depList = depPackage.getDependencies(depType=depType)
File
"C:\CraftRoot\download\craft-master\bin\Blueprints\CraftDependencyPackage.py",
line 105, in getDependencies
self.depenendencyType = depType
File
"C:\CraftRoot\download\craft-master\bin\Blueprints\CraftDependencyPackage.py",
line 45, in depenendencyType
self.__resolveDependencies()
File
"C:\CraftRoot\download\craft-master\bin\Blueprints\CraftDependencyPackage.py",
line 58, in __resolveDependencies
self.dependencies.extend(self.__readDependenciesForChildren([(x, None) for
x in self.children.values()]))
File
"C:\CraftRoot\download\craft-master\bin\Blueprints\CraftDependencyPackage.py",
line 74, in __readDependenciesForC
hildren
p.depenendencyType = self.depenendencyType
File
"C:\CraftRoot\download\craft-master\bin\Blueprints\CraftDependencyPackage.py",
line 45, in depenendencyType
self.__resolveDependencies()
File
"C:\CraftRoot\download\craft-master\bin\Blueprints\CraftDependencyPackage.py",
line 50, in __resolveDependencies
subinfo = self.subinfo
File
"C:\CraftRoot\download\craft-master\bin\Blueprints\CraftPackageObject.py", line
319, in subinfo
return self.instance.subinfo
File
"C:\CraftRoot\download\craft-master\bin\Blueprints\CraftPackageObject.py", line
307, in instance
pack = mod.Package()
File
"C:\CraftRoot\download\etc\blueprints\locations\craft-blueprints-kde\libs\llvm-meta\llvm\llvm.py",
line 30, in __
init__
CMakePackageBase.__init__(self)
File "C:\CraftRoot\download\craft-master\bin\Package\CMakePackageBase.py",
line 15, in __init__
PackageBase.__init__(self)
File "C:\CraftRoot\download\craft-master\bin\Package\PackageBase.py", line
32, in __init__
CraftBase.__init__(self)
File "C:\CraftRoot\download\craft-master\bin\CraftBase.py", line 38, in inner
return fun(*args, **kwargs)
File "C:\CraftRoot\download\craft-master\bin\CraftBase.py", line 58, in
__init__
self.subinfo = mod.subinfo(self)
File "C:\CraftRoot\download\craft-master\bin\info.py", line 65, in __init__
self.registerOptions()
File
"C:\CraftRoot\download\etc\blueprints\locations\craft-blueprints-kde\libs\llvm-meta\llvm\llvm.py",
line 8, in reg
isterOptions
self.options.dynamic.setDefault("buildType", "Release")
TypeError: 'NoneType' object is not callable
PS C:\CraftRoot\download>
EXPECTED RESULT
Install the LLVM package
SOFTWARE/OS VERSIONS
Windows: Windows 7 x64
Qt Version: None
ADDITIONAL INFORMATION
Craft and kde-blueprints are updated. Also, running the craftenv.ps1 script
gives this output:
Craft : C:\CraftRoot\download
Version : master
ABI : windows-msvc2017_64-cl
Download directory : C:\CraftRoot\download\download
PS C:\CraftRoot\download>
--
You are receiving this mail because:
You are watching all bug changes.
[kdevelop] [Bug 389060] Heaptrack analysis keeps firing /usr/bin/plasmoidviewer
https://bugs.kde.org/show_bug.cgi?id=389060 Petros changed: What|Removed |Added CC||petross...@gmail.com --- Comment #2 from Petros --- KDevelop 5.3 is already released an I am facing the same issue. Any news? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwayland] [Bug 396308] wayland: clearing clipboard history crashes plasma
https://bugs.kde.org/show_bug.cgi?id=396308 Petros Moisiadis changed: What|Removed |Added CC||ernes...@yahoo.gr --- Comment #3 from Petros Moisiadis --- I can reproduce this on Archlinux. Besides the kwin_wayland process, the org_kde_powerde process is crashing too, but that may be irrelevant. Backtraces from journal log follow: Sep 12 13:25:40 myhost systemd-coredump[2792]: Process 2438 (org_kde_powerde) of user 1000 dumped core. Stack trace of thread 2438: #0 0x7f4560de8d7f raise (libc.so.6) #1 0x7f45623b76cf _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5) #2 0x7f4560de8e00 __restore_rt (libc.so.6) #3 0x7f4561212380 _ZN9QHashData11free_helperEPFvPNS_4NodeEE (libQt5Core.so.5) #4 0x7f45608605c4 _ZN9KIdleTimeD2Ev (libKF5IdleTime.so.5) #5 0x7f456086061a _ZN9KIdleTimeD0Ev (libKF5IdleTime.so.5) #6 0x7f4560860292 n/a (libKF5IdleTime.so.5) #7 0x7f4560deb45c __run_exit_handlers (libc.so.6) #8 0x7f4560deb58e exit (libc.so.6) #9 0x7f4558fe310f _ZN15QtWaylandClient15QWaylandDisplay13exitWithErrorEv (libQt5WaylandClient.so.5) #10 0x7f4558fe316a _ZN15QtWaylandClient15QWaylandDisplay13flushRequestsEv (libQt5WaylandClient.so.5) #11 0x7f456139ff6c _ZN11QMetaObject8activateEP7QObjectiiPPv (libQt5Core.so.5) #12 0x7f45613abb7a _ZN15QSocketNotifier9activatedEiNS_14QPrivateSignalE (libQt5Core.so.5) #13 0x7f45613abed2 _ZN15QSocketNotifier5eventEP6QEvent (libQt5Core.so.5) #14 0x7f4561376129 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5) #15 0x7f45613ca12b n/a (libQt5Core.so.5) #16 0x7f455e8d63cf g_main_context_dispatch (libglib-2.0.so.0) #17 0x7f455e8d7f89 n/a (libglib-2.0.so.0) #18 0x7f455e8d7fce g_main_context_iteration (libglib-2.0.so.0) #19 0x7f45613c94b9 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.s> #20 0x7f455901d572 n/a (libQt5WaylandClient.so.5) #21 0x7f4561374dbc _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5) #22 0x7f456137d0b6 _ZN16QCoreApplication4execEv (libQt5Core.so.5) #23 0x55d6e36d00c6 n/a (org_kde_powerdevil) #24 0x7f4560dd5223 __libc_start_main (libc.so.6) #25 0x55d6e36d012e _start (org_kde_powerdevil) Stack trace of thread 2467: #0 0x7f4560ea1bb1 __poll (libc.so.6) #1 0x7f455e8d7ee0 n/a (libglib-2.0.so.0) #2 0x7f455e8d7fce g_main_context_iteration (libglib-2.0.so.0) #3 0x7f455e8d8022 n/a (libglib-2.0.so.0) #4 0x7f455e8a13eb n/a (libglib-2.0.so.0) #5 0x7f455fad7a9d start_thread (libpthread.so.0) #6 0x7f4560eaca43 __clone (libc.so.6) Stack trace of thread 2468: #0 0x7f4560ea1bb1 __poll (libc.so.6) #1 0x7f455e8d7ee0 n/a (libglib-2.0.so.0) #2 0x7f455e8d8f62 g_main_loop_run (libglib-2.0.s
[kdevelop] [Bug 378395] Kdevelop can't "lock" the open toolviews across restarts or when switching from "Debug" to "Code"
https://bugs.kde.org/show_bug.cgi?id=378395 Petros <petross...@gmail.com> changed: What|Removed |Added CC||petross...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 393913] New: KDevelop can't remember which toolviews the user opened.
https://bugs.kde.org/show_bug.cgi?id=393913 Bug ID: 393913 Summary: KDevelop can't remember which toolviews the user opened. Product: kdevelop Version: git master Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: UI: general Assignee: kdevelop-bugs-n...@kde.org Reporter: petross...@gmail.com Target Milestone: --- I want this : https://i.imgur.com/yb01VGw.png but after restart I get this : https://i.imgur.com/K4b04oW.png Any idea why? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 390361] New: Crash when clicking another shortcuts subsection in system settings
https://bugs.kde.org/show_bug.cgi?id=390361 Bug ID: 390361 Summary: Crash when clicking another shortcuts subsection in system settings Product: systemsettings Version: 5.12.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: ernes...@yahoo.gr Target Milestone: --- Application: systemsettings5 (5.12.0) Qt Version: 5.10.0 Frameworks Version: 5.42.0 Operating System: Linux 4.15.2-2-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: Clicking in each subsection one after the other in the shortcuts sections of system settings: Standard shortcuts, then Global shortcuts, then Web shortcuts, then Custom shortcuts. When I clicked on Custom shortcuts, having clicked previously on Web shortcuts, it crashed. I tried to find a pattern and it seems that it will crash each time you pass from web shortcuts first and then click on another category. -- Backtrace: Application: System Settings (systemsettings5), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f165058f800 (LWP 1059))] Thread 7 (Thread 0x7f160a7f2700 (LWP 1093)): #0 0x7f164bf9297b in poll () at /usr/lib/libc.so.6 #1 0x7f1645abeff3 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f1645abf3b2 in g_main_loop_run () at /usr/lib/libglib-2.0.so.0 #3 0x7f1609a6d6d8 in () at /usr/lib/libgio-2.0.so.0 #4 0x7f1645ae726a in () at /usr/lib/libglib-2.0.so.0 #5 0x7f164811208c in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f164bf9ce7f in clone () at /usr/lib/libc.so.6 Thread 6 (Thread 0x7f160881a700 (LWP 1092)): #0 0x7f164bf9297b in poll () at /usr/lib/libc.so.6 #1 0x7f1645abeff3 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f1645abf10e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f1645abf162 in () at /usr/lib/libglib-2.0.so.0 #4 0x7f1645ae726a in () at /usr/lib/libglib-2.0.so.0 #5 0x7f164811208c in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f164bf9ce7f in clone () at /usr/lib/libc.so.6 Thread 5 (Thread 0x7f1618ea6700 (LWP 1067)): #0 0x7f164bf8e3d8 in read () at /usr/lib/libc.so.6 #1 0x7f1645b047d1 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f1645abeac8 in g_main_context_check () at /usr/lib/libglib-2.0.so.0 #3 0x7f1645abef96 in () at /usr/lib/libglib-2.0.so.0 #4 0x7f1645abf10e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #5 0x7f164c8ddd24 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7f164c87fe9b in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #7 0x7f164c68f78e in QThread::exec() () at /usr/lib/libQt5Core.so.5 #8 0x7f164a1baa19 in () at /usr/lib/libQt5Qml.so.5 #9 0x7f164c694b2d in () at /usr/lib/libQt5Core.so.5 #10 0x7f164811208c in start_thread () at /usr/lib/libpthread.so.0 #11 0x7f164bf9ce7f in clone () at /usr/lib/libc.so.6 Thread 4 (Thread 0x7f1621b20700 (LWP 1065)): #0 0x7f164bf8e3d8 in read () at /usr/lib/libc.so.6 #1 0x7f1645b047d1 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f1645abeac8 in g_main_context_check () at /usr/lib/libglib-2.0.so.0 #3 0x7f1645abef96 in () at /usr/lib/libglib-2.0.so.0 #4 0x7f1645abf10e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #5 0x7f164c8ddd24 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7f164c87fe9b in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #7 0x7f164c68f78e in QThread::exec() () at /usr/lib/libQt5Core.so.5 #8 0x7f164a1baa19 in () at /usr/lib/libQt5Qml.so.5 #9 0x7f164c694b2d in () at /usr/lib/libQt5Core.so.5 #10 0x7f164811208c in start_thread () at /usr/lib/libpthread.so.0 #11 0x7f164bf9ce7f in clone () at /usr/lib/libc.so.6 Thread 3 (Thread 0x7f162999b700 (LWP 1064)): #0 0x7f164bf9297b in poll () at /usr/lib/libc.so.6 #1 0x7f1645abeff3 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f1645abf10e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f164c8ddd24 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f164c87fe9b in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f164c68f78e in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f164a1baa19 in () at /usr/lib/libQt5Qml.so.5 #7 0x7f164c694b2d in () at /usr/lib/libQt5Core.so.5 #8 0x7f164811208c in start_thread () at /usr/lib/libpthread.so.0 #9 0x7f164bf9ce7f in clone () at /usr/lib/libc.so.6 Thread 2 (Thread 0x7f1633e48700 (LWP 1062)): #0 0x7f1645abe9e9 in g_main_context_check () at
[kdevelop] [Bug 378395] Kdevelop can't "lock" the open toolviews across restarts or when switching from "Debug" to "Code"
https://bugs.kde.org/show_bug.cgi?id=378395 --- Comment #1 from Petros <petross...@gmail.com> --- Any news on this? KDevelop still can't remember and restore the last active toolviews, ie when I close and open another project or if KDevelop crashes and I reopen it. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 378237] KDevelop doesn't move the screen with the line indicator when stepping through the code in Debug
https://bugs.kde.org/show_bug.cgi?id=378237 --- Comment #3 from Petros <petross...@gmail.com> --- I can't reproduce it either. It's been a long time since I last tried to debug a project in KDevelop. Maybe they fixed it. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 378312] Can't change the "Page size" to custom in "Print Preview"
https://bugs.kde.org/show_bug.cgi?id=378312 --- Comment #2 from Petros <petross...@gmail.com> --- (In reply to Friedrich W. H. Kossebau from comment #1) > Please check and report this with Qt at https://bugreports.qt.io (could not > find a related bug report on a quick check). Thank you. https://bugreports.qt.io/browse/QTBUG-60041 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 378442] KDevelop crashed with virtual clang::Parser::~Parser(): Assertion `TemplateIds.empty() && "Still alive TemplateIdAnnotations around?"' failed
https://bugs.kde.org/show_bug.cgi?id=378442 Petros <petross...@gmail.com> changed: What|Removed |Added Status|RESOLVED|CLOSED --- Comment #10 from Petros <petross...@gmail.com> --- LLVM/Clang-4.0.0-r1 solved for me this issue. KDevelop no longer crashes if I remove the comment (//) infront of text. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 378509] [Wish] Language support: Assembly, based on gas or nasm
https://bugs.kde.org/show_bug.cgi?id=378509 Petros <petross...@gmail.com> changed: What|Removed |Added Severity|normal |wishlist -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 378509] New: [Wish] Language support: Assembly, based on gas or nasm
https://bugs.kde.org/show_bug.cgi?id=378509 Bug ID: 378509 Summary: [Wish] Language support: Assembly, based on gas or nasm Product: kdevelop Version: git master Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: petross...@gmail.com Target Milestone: --- Maybe assembly language support could be implemented. Gas is already there, if the language semantics (AT style) are to be supported we could also provide assembly language support. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 378442] KDevelop crashed with virtual clang::Parser::~Parser(): Assertion `TemplateIds.empty() && "Still alive TemplateIdAnnotations around?"' failed
https://bugs.kde.org/show_bug.cgi?id=378442 --- Comment #9 from Petros <petross...@gmail.com> --- I took one screenshot of a DDD backtrace of kdevelop. I can't save it to a text unfortunatelly. http://imgur.com/a/3RZVC -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 378442] KDevelop crashed with virtual clang::Parser::~Parser(): Assertion `TemplateIds.empty() && "Still alive TemplateIdAnnotations around?"' failed
https://bugs.kde.org/show_bug.cgi?id=378442 --- Comment #8 from Petros <petross...@gmail.com> --- I copied and pasted the text from a website, but when I tried to actually write text (without comments) in another source file (and project) I also got a crash. So it's not that I pasted some incompatible character or newline... Parser just doesn't like normal text. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 378442] KDevelop crashed with virtual clang::Parser::~Parser(): Assertion `TemplateIds.empty() && "Still alive TemplateIdAnnotations around?"' failed
https://bugs.kde.org/show_bug.cgi?id=378442
--- Comment #7 from Petros <petross...@gmail.com> ---
(In reply to Kevin Funk from comment #6)
> Please provide an exact way to reproduce this: e.g. file contents
> before/after.
>
> Reduce the test case as much as possible.
Before...
// Each new term in the Fibonacci sequence is generated by adding the previous
two terms.
//By starting with 1 and 2, the first 10 terms will be:
//1, 2, 3, 5, 8, 13, 21, 34, 55, 89, ...
//By considering the terms in the Fibonacci sequence whose values do not exceed
four million,
//find the sum of the even-valued terms
#include "headers/eul_2_facilities.h"
int main ( int argc, char** argv ) {
vector v{0, 1};
return ( 0 );
}
After that, just remove *any* comment, with Background Parser enabled.
--
You are receiving this mail because:
You are watching all bug changes.
[kdevelop] [Bug 378442] KDevelop crashed with virtual clang::Parser::~Parser(): Assertion `TemplateIds.empty() && "Still alive TemplateIdAnnotations around?"' failed
https://bugs.kde.org/show_bug.cgi?id=378442 --- Comment #5 from Petros <petross...@gmail.com> --- (In reply to Kevin Funk from comment #3) > @Petros: FYI: We don't recommend using a Clang/LLVM build which has > assertions enabled. Not sure what you mean. I build Kdevelop with GCC 6.3 and not Clang if that is what you are asking for. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 378442] KDevelop crashed with virtual clang::Parser::~Parser(): Assertion `TemplateIds.empty() && "Still alive TemplateIdAnnotations around?"' failed
https://bugs.kde.org/show_bug.cgi?id=378442 --- Comment #4 from Petros <petross...@gmail.com> --- KDevelop crashed once again when I enabled the Background Parser and removed the comment (//) from infront of text line. It seems clang parser has a certain problem with uncommented text. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 378442] KDevelop crashed with virtual clang::Parser::~Parser(): Assertion `TemplateIds.empty() && "Still alive TemplateIdAnnotations around?"' failed
https://bugs.kde.org/show_bug.cgi?id=378442 --- Comment #1 from Petros <petross...@gmail.com> --- Created attachment 104876 --> https://bugs.kde.org/attachment.cgi?id=104876=edit output of console [2] -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 378442] New: KDevelop crashed with virtual clang::Parser::~Parser(): Assertion `TemplateIds.empty() && "Still alive TemplateIdAnnotations around?"' failed
https://bugs.kde.org/show_bug.cgi?id=378442 Bug ID: 378442 Summary: KDevelop crashed with virtual clang::Parser::~Parser(): Assertion `TemplateIds.empty() && "Still alive TemplateIdAnnotations around?"' failed Product: kdevelop Version: git master Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: code completion Assignee: kdevelop-bugs-n...@kde.org Reporter: petross...@gmail.com Target Milestone: --- Created attachment 104875 --> https://bugs.kde.org/attachment.cgi?id=104875=edit kcrash [1] I pasted a chuck of text in kdevelop's editor and before managing to place "//" ahead, KDevelop had already crashed[1]. Next time I restarted KDevelop and parsed the project, editor asked me if I wanted to restore the changes made in the .cpp file, that lost due to crash. As soon as I clicked on restore the text reappeard for a second only for KDevelop to crash again.[2] As soon as I disabled the Background Parser I could open and append the "//" infront of the text and save my work. [1] https://paste.pound-python.org/show/L7ppJfhX342Ruxl5dD2D/ [2] https://paste.pound-python.org/show/vbhGbKw9slq7vao2MIdD/ -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 378397] New: KDevelop doesn't remember certain configuration options among IDE's restarts
https://bugs.kde.org/show_bug.cgi?id=378397 Bug ID: 378397 Summary: KDevelop doesn't remember certain configuration options among IDE's restarts Product: kdevelop Version: git master Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: session support Assignee: kdevelop-bugs-n...@kde.org Reporter: petross...@gmail.com Target Milestone: --- KDevelop doesn't remember the "Enable Look-ahead code-completion" among IDE's restarts. It can't remember it even for the same project, if this option isn't global. Another config option that the IDE doesn't remember, is the formating style under Source Formatter. Sometimes this is not happening just when IDE restarts, but even for a newly added source file. So I have to re-open Settings and select again: Language -> C++ Formatter -> Artistic Style and select the the style I want. One last thing, I stoped to use "Add Kate Modeline" ; kdevelop didn't remember those too. That is for now, I can't recall other options that I use and KDevelop ignores after restart. If anyone else wants to add something, feel free to. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 378395] New: Kdevelop can't "lock" the open toolviews across restarts or when switching from "Debug" to "Code"
https://bugs.kde.org/show_bug.cgi?id=378395 Bug ID: 378395 Summary: Kdevelop can't "lock" the open toolviews across restarts or when switching from "Debug" to "Code" Product: kdevelop Version: git master Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: session support Assignee: kdevelop-bugs-n...@kde.org Reporter: petross...@gmail.com Target Milestone: --- I work with git master version of KDevelop and I have trouble working with toolviews. I have open toolviews at both sides of the IDE (in the right side 3 of them opened with Ctrl), but when I close and reopen kdevelop, I always the left toolview closed (but it's button is grey - like pressed) and the right toolviews are replaced (always) by "Snipsets". Kind of the same thing happens when I return to "Code" from "Debug". I have my toolviews open when I am in code and when I return again the toolviews aren't replaced; rather they are closed but their buttons are "grayed". It's like Kdevelop knows that I had them opened, but for some reason it won't open them again. The same problem with toolviews disappearing when I return from "git commit" and closing the review window. Anyway, you got the point. Toolviews can't be "locked" or being remembered when KDevelop does *what* actually? There are diferrent cases with the same output. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 378367] New: Wrong url in "Open Project" dialog, leaves no choise to fix it but rather reopen the dialog once again
https://bugs.kde.org/show_bug.cgi?id=378367 Bug ID: 378367 Summary: Wrong url in "Open Project" dialog, leaves no choise to fix it but rather reopen the dialog once again Product: kdevelop Version: git master Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: UI: general Assignee: kdevelop-bugs-n...@kde.org Reporter: petross...@gmail.com Target Milestone: --- When I accindentally gave a wrong url in the field "Source" to clone from a remote git repo and clicked "Get" I couldn't get the url right or re-paste it correctly. Instead I could only click "Canclel" and re-open the "Fetch Project" etc... Perphaps a button "Back" could be provided so to get in the previous step to fix something. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 378312] New: Can't change the "Page size" to custom in "Print Preview"
https://bugs.kde.org/show_bug.cgi?id=378312 Bug ID: 378312 Summary: Can't change the "Page size" to custom in "Print Preview" Product: kdevelop Version: git master Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: all editors Assignee: kdevelop-bugs-n...@kde.org Reporter: petross...@gmail.com Target Milestone: --- I can't select "custom". KDevelop continues to keep enabled my previous selection (eg A4). So I can't change the size (mm) that corespond to the dimentions of the paper on which I will print my code. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 378267] New: Astyle doesn't support c++11 initialization `type var{x};`
https://bugs.kde.org/show_bug.cgi?id=378267
Bug ID: 378267
Summary: Astyle doesn't support c++11 initialization `type
var{x};`
Product: kdevelop
Version: git master
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: astyle
Assignee: kdevelop-bugs-n...@kde.org
Reporter: petross...@gmail.com
Target Milestone: ---
Astyle messes with c++11 {} initialization and thinks these are functions
brackets. As a consequence this happens:
Before
int minutes {0}, hours {0}
After reformating source
int minutes
{
0}, hours...
--
You are receiving this mail because:
You are watching all bug changes.
[kdevelop] [Bug 378237] KDevelop doesn't move the screen with the line indicator when stepping through the code in Debug
https://bugs.kde.org/show_bug.cgi?id=378237 --- Comment #1 from Petros <petross...@gmail.com> --- Also, if the indicator goes suddenly out of sight because let's say it jumped in a different function, KDevelop also could autoscroll there -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 378237] New: KDevelop doesn't move the screen with the line indicator when stepping through the code in Debug
https://bugs.kde.org/show_bug.cgi?id=378237 Bug ID: 378237 Summary: KDevelop doesn't move the screen with the line indicator when stepping through the code in Debug Product: kdevelop Version: git master Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: CPP Debugger Assignee: kdevelop-bugs-n...@kde.org Reporter: petross...@gmail.com CC: niko.s...@gmail.com Target Milestone: --- When I step through the code in Debug mode, the line indicator (which looks like an arrow an point at the next statement) sometimes jumps to another part of the source code/another function and goes out of sight. So I have to scroll here and there to actually see where the execution flow goes. Maybe the line indicator should have some kind of limit, or a margin of the screen that is allowed to exist. Eg if the indicator moves X numbers before the visible code's end, then the editor should auto scroll the code in order the indicator to be at Y lines above the middle of the shown code. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 377934] KDevelop's toolviews should be normal windows when undocked.
https://bugs.kde.org/show_bug.cgi?id=377934 --- Comment #5 from Petros <petross...@gmail.com> --- I am talkiing about something like this: http://lh5.ggpht.com/_feJtUp7IGuI/ShVuDHT__oI/AIw/jxd0y4dCYFA/image_thumb[1].png?imgmax=800 Ok, you get the point. While the code and some various toolviews are docked, a special toolview -eg Documentation, or something else you want to view with ease and at once, without scrolling and resizing- will be a second kdevelop window. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 377934] KDevelop's toolviews should be normal windows when undocked.
https://bugs.kde.org/show_bug.cgi?id=377934 --- Comment #4 from Petros <petross...@gmail.com> --- (In reply to Kevin Funk from comment #3) > @Petros: Which tool view? Maybe we should rather re-layout this particular > tool view so it fits to contents? Well it's not just one... I am thiniking of Valgrind outputs, Disassembly/Registers and of course Documentation. It would be nice if they could act as seperate windows if one wishes so. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 377934] KDevelop's toolviews should be normal windows when undocked.
https://bugs.kde.org/show_bug.cgi?id=377934 --- Comment #2 from Petros <petross...@gmail.com> --- (In reply to Ian Haber from comment #1) > I'm assuming they are qdockwidgets. as far as i know, qdockwidgets cant be > turned into qmainwindows. Can I do something for it? -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 377934] New: KDevelop's toolviews should be normal windows when undocked.
https://bugs.kde.org/show_bug.cgi?id=377934 Bug ID: 377934 Summary: KDevelop's toolviews should be normal windows when undocked. Product: kdevelop Version: git master Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: UI: general Assignee: kdevelop-bugs-n...@kde.org Reporter: petross...@gmail.com Target Milestone: --- When I want a toolview to be wide in order not to srcoll sideways, I usually undock it. But window manager doesn't treat it like a normal window - eg I may want to set it as "Keep above other" while I debug or run various analysis. So it there a way for a toolview to be undocked as another KDevelop's window on my desktop? -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 377899] New: KDevelop and automatic stepping through the code, with a timer to stop at each line.
https://bugs.kde.org/show_bug.cgi?id=377899 Bug ID: 377899 Summary: KDevelop and automatic stepping through the code, with a timer to stop at each line. Product: kdevelop Version: git master Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: CPP Debugger Assignee: kdevelop-bugs-n...@kde.org Reporter: petross...@gmail.com CC: niko.s...@gmail.com Target Milestone: --- KDevelop's debugging capabilities are steadily maturing. I think it is a nice idea to to also step through the code non-interactively, with an adjustable timer to halt at each line till the execution moves to the next one. If the programm needs user's input, then the debugger will halt as usual, waiting for the programm's input. This way the user or KDevelop can sit back and examine the execution flow in large programms, instead of clicking repeatedly. Another breakpoint in the code or/and a "stop on change" option, will halt the (automatic) execution, until further choise of the programmer. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 377291] New: KDevelop doesn't allow me to modify a variable's value, when stepping though the code in Debug
https://bugs.kde.org/show_bug.cgi?id=377291 Bug ID: 377291 Summary: KDevelop doesn't allow me to modify a variable's value, when stepping though the code in Debug Product: kdevelop Version: git master Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: CPP Debugger Assignee: kdevelop-bugs-n...@kde.org Reporter: petross...@gmail.com CC: niko.s...@gmail.com Target Milestone: --- As the title indicates, I can't modify the value of a variable when I debug my program. Double click on variable's name in "Variables" toolview does nothing and right click only gives these options: https://postimg.cc/image/cjsqial3j/ Also hovering the mouse above the variable in my code gives me this: https://postimg.org/image/6vz0wernn/ -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 377026] KDevelop should provide a menu for placing to the cursor some C++ features.
https://bugs.kde.org/show_bug.cgi?id=377026 --- Comment #8 from Petros <petross...@gmail.com> --- No worries ;) Anyway, these are just some ideas. They may lead to other ideas or they may not. Either way KDevelop is pretty competitive and I have trust in the developers that if they find something nice, they will implement it. Besides it's not bad afterall if a feature or idea is taken from another IDE. Have a nice day :) -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 377026] KDevelop should provide a menu for placing to the cursor some C++ features.
https://bugs.kde.org/show_bug.cgi?id=377026 --- Comment #5 from Petros <petross...@gmail.com> --- (In reply to Sven Brauch from comment #4) > But that is what the snippets plugin does, no? As far as I know I can't interactively give properties (eg name for the class, the functor or even if a default (de)constructor should appear in it). I hope you get the idea of full customisability that I am talking here. Sure, I as a developer will write the code; not a kdevelop template will. But it would be nice to just give the name of the class in a dialog, click if a default constructor is to be shown and voila. I can have a customized skeleton where I want it and start doing exactly this; write just the code. This might not be restricted to classes only; it's just that I can't imagine another c++ feature that can be created like this. Ok I have to admit that for c++ templates, a snippset with a small skeleton might cut it. Nothing here to interactively ask the user and append to the template. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 377026] KDevelop should provide a menu for placing to the cursor some C++ features.
https://bugs.kde.org/show_bug.cgi?id=377026 --- Comment #3 from Petros <petross...@gmail.com> --- And yes I did miss the snippset plugin. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 377026] KDevelop should provide a menu for placing to the cursor some C++ features.
https://bugs.kde.org/show_bug.cgi?id=377026 --- Comment #2 from Petros <petross...@gmail.com> --- (In reply to Sven Brauch from comment #1) > Maybe you just haven't used the snippets plugin yet? ;) First, I think you did unsterstand correctly. Indeed I can create a snippset for lambda, which can be triggered when Cnt+Space shows autocomplete and snippsets. But for a class, a functor or even a (C++) Template skeleton, I don't always wish to create new files with a (kdevelop) template, but rather write a simple, small class, or Template in place, in the file I am currently working. So, would you consider usefull a feature that does exactly the same thing without creating new files but placing inside an existing one? PS. Thank you for the clarification though. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 377027] KDevelop could feature a Designer UI
https://bugs.kde.org/show_bug.cgi?id=377027 --- Comment #2 from Petros <petross...@gmail.com> --- (In reply to Kevin Funk from comment #1) > You're aware there's a standalone Qt designer available you can use? Yes, yes I am. The way I see it, it's nice to not leave KDevelop and work with git. So it would nice to not leave KDevelop to edit, or design .ui files. Ok that is not as generic as git, it's qt specific but my personal opinion is that is would make KDevelop an ever more complete IDE. Of course the decision is yours (the devs) and I can't code in order to provide the solution. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 377027] New: [Wish] KDevelop could feature a Designer UI
https://bugs.kde.org/show_bug.cgi?id=377027 Bug ID: 377027 Summary: [Wish] KDevelop could feature a Designer UI Product: kdevelop Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: UI: general Assignee: kdevelop-bugs-n...@kde.org Reporter: petross...@gmail.com Target Milestone: --- It would be super cool to open .ui files with an integrated qtdesigner view. The same that did happen for kate's integration or okteta, could happen for qtdesigner too. So we could create and edit .ui files directly from KDevelop. The tools are already there, no need to reinvent the wheel. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 377026] New: [Wish] KDevelop should provide a menu for placing to the cursor some C++ features.
https://bugs.kde.org/show_bug.cgi?id=377026 Bug ID: 377026 Summary: [Wish] KDevelop should provide a menu for placing to the cursor some C++ features. Product: kdevelop Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: UI: general Assignee: kdevelop-bugs-n...@kde.org Reporter: petross...@gmail.com Target Milestone: --- I am explaining myself: When a programmer writes C++, it would be nice if certain menus and/or shortcuts enabled the programmer to place a skeleton for certain C++ features. Eg you use an STL algorithm and you press a shortcut and a lambda skeleton is created. Another: You create in place a class skeleton. You could also create a functor skeleton with the help of an interactive dialog that would take the class's name and the privates and publics variables as parameters. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 377025] New: [Wish] Kdevelop file creation from template should ask interactively for properties.
https://bugs.kde.org/show_bug.cgi?id=377025 Bug ID: 377025 Summary: [Wish] Kdevelop file creation from template should ask interactively for properties. Product: kdevelop Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: file create Assignee: kdevelop-bugs-n...@kde.org Reporter: petross...@gmail.com Target Milestone: --- I find Kdevelop very appealing and elegant in many ways. But it would really helpfull if when the user needed a ready, template-made class and it's header, KDevelop showed a dialog asking for class's name, or for functions protypes in the header and stuff like that. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 375555] New: Opening KDE apps gives multiples notifications about: "There are two actions(...) that want to use the same shortcut"
https://bugs.kde.org/show_bug.cgi?id=37 Bug ID: 37 Summary: Opening KDE apps gives multiples notifications about: "There are two actions(...) that want to use the same shortcut" Product: plasmashell Version: 5.8.5 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: petross...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 I a gentoo/linux user and since I updated kde-frameworks/ packages to 5.30 I constantly get multiple times these notifications each and every time I try to launch a KDE application. It pop's up a notification for every single menu and action there is in the application, before the actual window show up. https://s29.postimg.org/tf88plqif/Screenshot_20170125_183424.png "There are two actions (What's This?, What's this?) that want to use the same shortcut (Shift+F1). This is most probably a bug. Please report it in bugs.kde.org" If I check "Do not show this message again" for every action, next time I will launch the same app it will show up with a slight delay, but without any notification. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 369105] KDevelop-5.0.1 AppImage doesn't launch on Gentoo because of "libxcb-dri3.so.0: error: symbol lookup error"
https://bugs.kde.org/show_bug.cgi?id=369105 --- Comment #3 from Petros <petross...@gmail.com> --- Portage reemerged libxcb, mesa and last xorg-server with this specific order but the problem persists. equery b libGL.so * Searching for libGL.so.1 ... dev-util/apitrace-7.1 (/usr/lib64/apitrace/wrappers/libGL.so.1 -> glxtrace.so) media-libs/mesa-12.0.3 (/usr/lib32/libGL.so.1 -> libGL.so.1.2.0) media-libs/mesa-12.0.3 (/usr/lib64/libGL.so.1 -> libGL.so.1.2.0) media-libs/mesa-12.0.3 (/usr/lib64/libGL.so.1.2.0) file libGL.so.1 libGL.so.1: symbolic link to libGL.so.1.2.0 file libxcb-dri3.so.0 libxcb-dri3.so.0: symbolic link to libxcb-dri3.so.0.0.0 file libxcb-dri3.so.0.0.0 libxcb-dri3.so.0.0.0: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, stripped At first I though that there had to be some kind of inconsistency with the naming scheme of the symlinks. But every symlink exists and points where it should be. Below I provide the LD_DEBUG outputs relevanto dri3 from these two appimages (5.0.0-1 and 5.0.1) LD_DEBUG="files" ./kdevelop-latest.AppImage 2>&1 | tee | grep xcb-dri3 11109: file=libxcb-dri3.so.0 [0]; needed by /usr/lib64/libGL.so.1 [0] 11109: file=libxcb-dri3.so.0 [0]; generating link map 11109: calling init: /usr/lib64/libxcb-dri3.so.0 11132: file=libxcb-dri3.so.0 [0]; needed by /usr/lib64/libGL.so.1 [0] 11132: file=libxcb-dri3.so.0 [0]; generating link map 11132: calling init: /usr/lib64/libxcb-dri3.so.0 11135: file=libxcb-dri3.so.0 [0]; needed by /usr/lib64/libGL.so.1 [0] 11135: file=libxcb-dri3.so.0 [0]; generating link map 11135: calling init: /usr/lib64/libxcb-dri3.so.0 11109: calling fini: /usr/lib64/libxcb-dri3.so.0 [0] 11135: calling fini: /usr/lib64/libxcb-dri3.so.0 [0] 11132: calling fini: /usr/lib64/libxcb-dri3.so.0 [0] the whole output ( https://paste.pound-python.org/show/tvVFadlzvxdsYVOHwFv9/ ) LD_DEBUG="files" ./KDevelop-5.0.1-x86_64.AppImage 2>&1 | tee | grep xcb-dri 11225: file=libxcb-dri3.so.0 [0]; needed by /usr/lib64/libGL.so.1 [0] 11225: file=libxcb-dri3.so.0 [0]; generating link map 11225: /usr/lib64/libxcb-dri3.so.0: error: symbol lookup error: undefined symbol: xcb_send_request_with_fds (fatal) kdevelop: symbol lookup error: /usr/lib64/libxcb-dri3.so.0: undefined symbol: xcb_send_request_with_fds And system-installed kdevelop: LD_DEBUG="files" /usr/bin/kdevelop 12432: file=libxcb-dri3.so.0 [0]; needed by /usr/lib64/libGL.so.1 [0] 12432:EBUG=file=libxcb-dri3.so.0 [0]; generating link map 12432:EBUG=calling init: /usr/lib64/libxcb-dri3.so.0 12440: file=libxcb-dri3.so.0 [0]; needed by /usr/lib64/libEGL.so.1 [0] 12440: file=libxcb-dri3.so.0 [0]; generating link map 12440: calling init: /usr/lib64/libxcb-dri3.so.0 ^C The same command, with the same (in some way) executables, and the same (?) libraries provided. Why there is this inconsistency in the behavior? PS I even tried to recompile libxcb, mesa and xorg without -ggdb, but of course this wasn't an issue. PS1. I tried to create the output of LD_DEBUG="all" for the 5.0.0-1 version, but soon enough the log size was over 170MB. No way this thing can be uploaded with my internet connection. If it is necessary though, let me know. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 369105] KDevelop-5.0.1 AppImage doesn't launch on Gentoo because of "libxcb-dri3.so.0: error: symbol lookup error"
https://bugs.kde.org/show_bug.cgi?id=369105 --- Comment #1 from Petros <petross...@gmail.com> --- https://paste.pound-python.org/show/qWSBxLxUpD7ixgSIMIy6/ Here there is the output of LD_DEBUG="symbols" ./KDevelop-5.0.1-x86_64.AppImage -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 369105] New: KDevelop-5.0.1 AppImage doesn't launch on Gentoo because of "libxcb-dri3.so.0: error: symbol lookup error"
https://bugs.kde.org/show_bug.cgi?id=369105 Bug ID: 369105 Summary: KDevelop-5.0.1 AppImage doesn't launch on Gentoo because of "libxcb-dri3.so.0: error: symbol lookup error" Product: kdevelop Version: unspecified Platform: Appimage URL: https://paste.pound-python.org/raw/cB5s2QyMNTupcf548KP 5/ OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: petross...@gmail.com I use Gentoo/Linux and I have installed KDevelop-5.0.1 with a custom ebuild an works like a charm. Although I wanted to download and test an AppImage with the same version from here: http://files.svenbrauch.de/kdevelop-linux/ For some reason *this* KDevelop executable (appimage) can't launch and rants about " /usr/lib64/libxcb-dri3.so.0: error: symbol lookup error: undefined symbol: xcb_send_request_with_fds ". I am providing one URL with the output of command: LD_DEBUG=”libs” && ./KDevelop-5.0.1-x86_64.AppImage and onother of the command: LD_DEBUG=”files” && ./KDevelop-5.0.1-x86_64.AppImage which is : https://paste.pound-python.org/show/I3u5A2gfeoDAm8VaNnah/ Let me tell you that I tried the same appimage with Arch and worked right away. Also I haven't had any problem with AppImage version 5.0.0-1. Just this 5.0.1 version. So what is missing? Should I provide more debug-info about the system-installed KDevelop? Reproducible: Always Steps to Reproduce: 1. download from http://files.svenbrauch.de/kdevelop-linux/KDevelop-5.0.1-x86_64.AppImage 2. make the appimage executable and run it 3. crash Actual Results: kdevelop: symbol lookup error: /usr/lib64/libxcb-dri3.so.0: undefined symbol: xcb_send_request_with_fds Expected Results: Launch the application I am using software compiled with -ggdb and splitdebug for proper bug reporting. Don't think it matters to the problem though. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 364650] Crash when searching for '_' with non-native keyboard layout
https://bugs.kde.org/show_bug.cgi?id=364650 --- Comment #6 from Petros Moisiadis <ernes...@yahoo.gr> --- Well, it' not only the "shift" key press that causes the problem. Most "control" keys are crashing the editor (CTRL, CAPS LOCK, ALT, etc.). Note that I am talking about a crash that occurs only when having set the editor in vi input mode, and pressing the mentioned keys in the search box (opened with '/' shortcut). -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 364650] Crash when searching for '_' with non-native keyboard layout
https://bugs.kde.org/show_bug.cgi?id=364650 Petros Moisiadis <ernes...@yahoo.gr> changed: What|Removed |Added CC||ernes...@yahoo.gr --- Comment #5 from Petros Moisiadis <ernes...@yahoo.gr> --- (In reply to Buovjaga from comment #4) > (In reply to Sven Brauch from comment #2) > > Also happens in current kate, I'm moving the bug. Just switch to vi input > > mode, press / _ -> crash. > > No crash for me. > > Arch Linux 64-bit > Kate 16.04.2 > KDE Frameworks 5.23.0 > Qt 5.7 > xcb wm Have you tried with 16.04.3-1 ? In my case, it crashes all the time if I press "shift" to change the character to be inserted with each key press. So, If I try to search with a keyword containing the '_' character, I would try to press 'shift' + '-' keys, and the crash would occur when pressing 'shift'. At first, it seems that the problem occurs with the '_' character, but this is only because the combination "shift" + '-' can be typed fast enough to think so. However, it just needs to press "shift" to crash it. E.g., trying to insert a capital letter (with shift), also crashes the editor. Copy and pasting strings that contain '_' with mouse works ok, so it's the shift key press event that triggers the problem. -- You are receiving this mail because: You are watching all bug changes.
