[frameworks-baloo] [Bug 490981] baloosearch6: --directory switch results in no matches
https://bugs.kde.org/show_bug.cgi?id=490981 --- Comment #3 from Eugene Shalygin --- Although I use BTRFS, this behaviour can be observed without remounting the partition between indexing and queering. -- You are receiving this mail because: You are watching all bug changes.
[filelight] [Bug 492155] New: Filelight (potentially) removes wrong directories
https://bugs.kde.org/show_bug.cgi?id=492155 Bug ID: 492155 Summary: Filelight (potentially) removes wrong directories Classification: Applications Product: filelight Version: 24.08.0 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: eugene.shalygin+bugzilla@gmail.com CC: martin.sandsm...@kde.org Target Milestone: --- SUMMARY After removing a directory, the left directory list goes out of sync. Invoking the "Delete" action from the context menu shows the next path in the confirmation dialog. If user is not careful, they can remove what they don't indent to remove. STEPS TO REPRODUCE 1. Scan a directory. 2. Remove a directory using the right pane. 3. Invoke the context menu action "Delete" on one of the last entries in the left pane. OBSERVED RESULT Filelight shows the next entry in the confirmation dialog. EXPECTED RESULT Filelight asks to confirm removal of the selected entry. SOFTWARE/OS VERSIONS Operating System: Gentoo Linux 2.15 KDE Plasma Version: 6.1.4 KDE Frameworks Version: 6.5.0 Qt Version: 6.7.2 Kernel Version: 6.10.6-gentoo (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 491825] New: Notifications are drawn nested
https://bugs.kde.org/show_bug.cgi?id=491825 Bug ID: 491825 Summary: Notifications are drawn nested Classification: Plasma Product: plasmashell Version: 6.1.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Notifications Assignee: plasma-b...@kde.org Reporter: eugene.shalygin+bugzilla@gmail.com CC: k...@privat.broulik.de Target Milestone: 1.0 Created attachment 172705 --> https://bugs.kde.org/attachment.cgi?id=172705&action=edit screenshot SUMMARY I had a long running copy operation, and while it was active a notification from kdeconnect arrived. Upon clicking on the notifications tray icon I saw the notification from kdeconnect rendered inside the Dolphin one. SOFTWARE/OS VERSIONS Operating System: Gentoo Linux 2.15 KDE Plasma Version: 6.1.4 KDE Frameworks Version: 6.5.0 Qt Version: 6.7.2 Kernel Version: 6.10.5-gentoo (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 9 5900HX with Radeon Graphics -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 490981] New: baloosearch6: --directory switch results in no matches
https://bugs.kde.org/show_bug.cgi?id=490981 Bug ID: 490981 Summary: baloosearch6: --directory switch results in no matches Classification: Frameworks and Libraries Product: frameworks-baloo Version: 6.4.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: baloo-bugs-n...@kde.org Reporter: eugene.shalygin+bugzilla@gmail.com Target Milestone: --- baloosearch6 returns a list of files withing the home directory (BTW, incomplete). baloosearch6 -d returns nothing. STEPS TO REPRODUCE 1. baloosearch6 -d $HOME SOFTWARE/OS VERSIONS Operating System: Gentoo Linux 2.15 KDE Plasma Version: 6.1.3 KDE Frameworks Version: 6.4.0 Qt Version: 6.7.2 Kernel Version: 6.10.1-gentoo (64-bit) -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 490750] A file "$HOME/ --writable-path ConfigLocation)/mimeapps.list" is created when launching app via .desktop file
https://bugs.kde.org/show_bug.cgi?id=490750 Eugene Shalygin changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #2 from Eugene Shalygin --- (In reply to Nate Graham from comment #1) > Is there a problem though? I'm sure whoever wrote the code did not intend to create a subdirectory " --writable-path ConfigLocation)" in the home directory. So, this is probably a manifestation that something went wrong. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 490750] New: A file "$HOME/ --writable-path ConfigLocation)/mimeapps.list" is created when launching app via .desktop file
https://bugs.kde.org/show_bug.cgi?id=490750 Bug ID: 490750 Summary: A file "$HOME/ --writable-path ConfigLocation)/mimeapps.list" is created when launching app via .desktop file Classification: Plasma Product: krunner Version: 6.1.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: eugene.shalygin+bugzilla@gmail.com CC: alexander.loh...@gmx.de, natalie_clar...@yahoo.de Target Milestone: --- Signal .desktop file: [Desktop Entry] Name=Signal Exec=/opt/Signal/signal-desktop %U Terminal=false Type=Application Icon=signal-desktop StartupWMClass=Signal Comment=Private messaging from your desktop MimeType=x-scheme-handler/sgnl;x-scheme-handler/signalcaptcha; Categories=Network;InstantMessaging;Chat; When launching the app via this .desktop file, a file "$HOME/ --writable-path ConfigLocation)/mimeapps.list" is created: [Added Associations] x-scheme-handler/sgnl=signal-desktop.desktop; x-scheme-handler/signalcaptcha=signal-desktop.desktop; Operating System: Gentoo Linux 2.15 KDE Plasma Version: 6.1.3 KDE Frameworks Version: 6.4.0 Qt Version: 6.7.2 Kernel Version: 6.10.0-gentoo (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481933] Menus somtimes appear as normal windows when activated from anything other than the current active window
https://bugs.kde.org/show_bug.cgi?id=481933 --- Comment #23 from Eugene Shalygin --- It's not only a visual glitch, but if user is typing fast enough for popups to update, Qt crashes (QTBUG-126660). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481933] Menus somtimes appear as normal windows when activated from anything other than the current active window
https://bugs.kde.org/show_bug.cgi?id=481933 --- Comment #19 from Eugene Shalygin --- (In reply to Nate Graham from comment #15) > This appears to be an upstream Qt issue. It'll be fixed by > https://codereview.qt-project.org/c/qt/qtwayland/+/562273. Will updated this > ticket with the Qt version that ends up with the fix. I applied this patch to Qt 6.7.1 but QtC popups are still drawn as normal windows. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 488248] plasma-nm tray icon tooltip does not list VPN connection
https://bugs.kde.org/show_bug.cgi?id=488248 --- Comment #2 from Eugene Shalygin --- Yes, Plasma 5 showed all the connections -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 488248] New: plasma-nm tray icon tooltip does not list VPN connection
https://bugs.kde.org/show_bug.cgi?id=488248 Bug ID: 488248 Summary: plasma-nm tray icon tooltip does not list VPN connection Classification: Plasma Product: plasma-nm Version: git-stable-Plasma/6.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: applet Assignee: plasma-b...@kde.org Reporter: eugene.shalygin+bugzilla@gmail.com Target Milestone: --- SUMMARY The tooltip does not list active VPN connections STEPS TO REPRODUCE 1. Connect to a VPN 2. Hover the tray icon OBSERVED RESULT There is no mention of the connected VPN connection in the tooltip EXPECTED RESULT The VPN connection is listed in the tooltip text SOFTWARE/OS VERSIONS Operating System: Gentoo Linux 2.15 KDE Plasma Version: 6.0.90 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.1 Kernel Version: 6.9.3-gentoo (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436318] Save session doesn't work under Wayland
https://bugs.kde.org/show_bug.cgi?id=436318 --- Comment #104 from Eugene Shalygin --- Oh, I'm on Gentoo as well. Maybe it is our packaging that disables this feature? David, could you, please, point out the implementation location so I can try to figure out why it does not work? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436318] Save session doesn't work under Wayland
https://bugs.kde.org/show_bug.cgi?id=436318 --- Comment #102 from Eugene Shalygin --- It is set to "On last logout" here, but nothing gets launched on the next log in. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436318] Save session doesn't work under Wayland
https://bugs.kde.org/show_bug.cgi?id=436318 --- Comment #100 from Eugene Shalygin --- No signs of session restore as of 6.0.90 -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 487761] Tray icon does not show VPN status
https://bugs.kde.org/show_bug.cgi?id=487761 --- Comment #2 from Eugene Shalygin --- The icon popup does not list the VPN connection as well, so it's likely not a display issue -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 430514] Dolphin location bar ignores case sensitivity mode
https://bugs.kde.org/show_bug.cgi?id=430514 --- Comment #5 from Eugene Shalygin --- 6.0.90 does not substitute suggestions, but still lists them. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 487761] New: Tray icon does not show VPN status
https://bugs.kde.org/show_bug.cgi?id=487761 Bug ID: 487761 Summary: Tray icon does not show VPN status Classification: Plasma Product: plasma-nm Version: git-stable-Plasma/6.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: applet Assignee: plasma-b...@kde.org Reporter: eugene.shalygin+bugzilla@gmail.com Target Milestone: --- SUMMARY After updating to 6.0.1.90, the tray icon does not change upon connecting a Wireguard VPN SOFTWARE/OS VERSIONS Operating System: Gentoo Linux 2.15 KDE Plasma Version: 6.0.90 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.1 Kernel Version: 6.9.2-gentoo (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487731] New: Mouse click animation effect text is misaligned
https://bugs.kde.org/show_bug.cgi?id=487731 Bug ID: 487731 Summary: Mouse click animation effect text is misaligned Classification: Plasma Product: kwin Version: git-stable-Plasma/6.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-various Assignee: kwin-bugs-n...@kde.org Reporter: eugene.shalygin+bugzilla@gmail.com Target Milestone: --- SUMMARY The text is rendered with big displacement to the right and does not fir the tooltip window. STEPS TO REPRODUCE 1. Enable effect. 2. Enable "Show text" in the advanced settings 3. Click mouse OBSERVED RESULT The text left edge is in the middle of the popup window. EXPECTED RESULT The text is center-aligned inside the popup window. SOFTWARE/OS VERSIONS Operating System: Gentoo Linux 2.15 KDE Plasma Version: 6.0.90 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.1 Kernel Version: 6.9.2-gentoo (64-bit) Graphics Platform: Wayland Processors: 32 × AMD Ryzen 9 7950X 16-Core Processor Graphics Processor: AMD Radeon Graphics -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 487675] New: The desktop edit mode in Plasma 6.1 became less usable
https://bugs.kde.org/show_bug.cgi?id=487675 Bug ID: 487675 Summary: The desktop edit mode in Plasma 6.1 became less usable Classification: Plasma Product: plasmashell Version: git-stable-Plasma/6.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Edit Mode toolbar Assignee: plasma-b...@kde.org Reporter: eugene.shalygin+bugzilla@gmail.com Target Milestone: 1.0 The new edit mode in Plasma 6.1 makes it unpleasant to edit desktop and its widgets because they are scaled down and blurry, and I'd like to see their real size (I'm aware they can be resized in the normal mode). -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 487149] New: web inspector in falkon does not restor selected theme
https://bugs.kde.org/show_bug.cgi?id=487149 Bug ID: 487149 Summary: web inspector in falkon does not restor selected theme Classification: Applications Product: Falkon Version: 24.02.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: eugene.shalygin+bugzilla@gmail.com Target Milestone: --- Setting theme to "Dark" in the web inspector preferences does not persist between Falkon launches. Also, In KDE "System preference" ignores dark Plasma theme. STEPS TO REPRODUCE 1. Open Web Inspector 2. Select dark theme 3. Close Falkon 4. Launch Falkon 5. Open Web Inspector OBSERVED RESULT The theme is light EXPECTED RESULT The theme is dark SOFTWARE/OS VERSIONS Operating System: Gentoo Linux 2.15 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.0 Kernel Version: 6.9.0-gentoo (64-bit) Graphics Platform: Wayland Graphics Processor: AMD Radeon Graphics -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 486247] New: Systray popup closes right after opening upon first activation after unlocking the session
https://bugs.kde.org/show_bug.cgi?id=486247 Bug ID: 486247 Summary: Systray popup closes right after opening upon first activation after unlocking the session Classification: Plasma Product: plasmashell Version: 6.0.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: System Tray Assignee: plasma-b...@kde.org Reporter: eugene.shalygin+bugzilla@gmail.com CC: mate...@gmail.com Target Milestone: 1.0 SUMMARY After unlocking a session, clicking on any systray widgets displays popup window for a moment, which is then closes on itself. The only way I found to work that around is to show the hidden icons and activate any of them. After that visible icons behave normally. Operating System: Gentoo Linux 2.15 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Kernel Version: 6.8.7-gentoo (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 9 5900HX with Radeon Graphics Memory: 62.2 GiB of RAM Graphics Processor: AMD Radeon Graphics -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 485683] New: Popup windows are drawn detached and with title bars
https://bugs.kde.org/show_bug.cgi?id=485683 Bug ID: 485683 Summary: Popup windows are drawn detached and with title bars Classification: Plasma Product: kwin Version: 6.0.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: eugene.shalygin+bugzilla@gmail.com Target Milestone: --- SUMMARY Popup windows, like QCompleter popups (example: include path complete windows in QtCreator) are often rendered as full windows with title bars. Variable lookup popup windows in QtCreator are rendered empty and wrongly sized. STEPS TO REPRODUCE 1. Load a project in QtCreator 2. Try to complete an include path OBSERVED RESULT The list of completions is displayed in a basic window with title bar and at a detached location. EXPECTED RESULT The popup window is always displayed as popup and have its whole content rendered. SOFTWARE/OS VERSIONS Operating System: Gentoo Linux 2.15 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Kernel Version: 6.8.6-gentoo (64-bit) Graphics Platform: Wayland Graphics Processor: AMD Radeon Graphics ADDITIONAL INFORMATION The regression is present from at least 6.0.0. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483520] Window size is reset after screen sleep
https://bugs.kde.org/show_bug.cgi?id=483520 --- Comment #8 from Eugene Shalygin --- Well, to me it seems the original issue is now unreachable :) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483520] Window size is reset after screen sleep
https://bugs.kde.org/show_bug.cgi?id=483520
--- Comment #6 from Eugene Shalygin ---
I did set it manually in the past (Plasma 5), but now I don't find this
variable in any of the config files.
After updating one of the other system libraries, the window size seem to be
right after unlocking the screen, but plasmashell crashes every time instead:
Program terminated with signal SIGSEGV, Segmentation fault.
[KCrash Handler]
#4 0x7f9f9beac43e in void
QtPrivate::QPodArrayOps::emplace(long
long, KScreen::WaylandOutputDevice*&) () at
/usr/lib64/qt6/plugins/kf6/kscreen/KSC_KWayland.so
#5 0x7f9f9beaa626 in KScreen::WaylandConfig::addOutput(unsigned int,
unsigned int) () at /usr/lib64/qt6/plugins/kf6/kscreen/KSC_KWayland.so
#6 0x7f9f9beaa8cf in
KScreen::WaylandConfig::setupRegistry()::{lambda(void*, wl_registry*, unsigned
int, char const*, unsigned int)#1}::_FUN(void*, wl_registry*, unsigned int,
char const*, unsigned int) () at
/usr/lib64/qt6/plugins/kf6/kscreen/KSC_KWayland.so
#7 0x7f9fa7f0c2aa in ffi_call_unix64 () at /usr/lib64/libffi.so.8
#8 0x7f9fa7f0b6c1 in ffi_call_int () at /usr/lib64/libffi.so.8
#9 0x7f9fa7f0be1d in ffi_call () at /usr/lib64/libffi.so.8
#10 0x7f9faaa44c44 in wl_closure_invoke.constprop () at
/usr/lib64/libwayland-client.so.0
#11 0x7f9faaa44fac in dispatch_event.isra () at
/usr/lib64/libwayland-client.so.0
#12 0x7f9faaa49af6 in wl_display_dispatch_pending () at
/usr/lib64/libwayland-client.so.0
#13 0x7f9fa9f5e052 in QtWaylandClient::QWaylandDisplay::flushRequests() ()
at /usr/lib64/libQt6WaylandClient.so.6
#14 0x7f9fa827a68d in QObject::event(QEvent*) () at
/usr/lib64/libQt6Core.so.6
#15 0x7f9faa516bb9 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib64/libQt6Widgets.so.6
#16 0x7f9fa82f0408 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /usr/lib64/libQt6Core.so.6
#17 0x7f9fa83162ee in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () at /usr/lib64/libQt6Core.so.6
#18 0x7f9fa80c85b7 in postEventSourceDispatch(_GSource*, int (*)(void*),
void*) () at /usr/lib64/libQt6Core.so.6
#19 0x7f9fa6ca1c72 in g_main_dispatch () at /usr/lib64/libglib-2.0.so.0
#20 0x7f9fa6ca4e27 in g_main_context_iterate_unlocked.isra () at
/usr/lib64/libglib-2.0.so.0
#21 0x7f9fa6ca544c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#22 0x7f9fa80c1f10 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt6Core.so.6
#23 0x7f9fa831b00a in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt6Core.so.6
#24 0x7f9fa831b1c7 in QCoreApplication::exec() () at
/usr/lib64/libQt6Core.so.6
#25 0x561d91241154 in main ()
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 483520] Window size is reset after screen sleep
https://bugs.kde.org/show_bug.cgi?id=483520 --- Comment #4 from Eugene Shalygin --- The scale is set to 100% and QT_AUTO_SCREEN_SCALE_FACTOR=0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483520] Window size is reset after screen sleep
https://bugs.kde.org/show_bug.cgi?id=483520 --- Comment #2 from Eugene Shalygin --- 3440 × 1440 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 455431] "Spare Layouts" feature on Wayland
https://bugs.kde.org/show_bug.cgi?id=455431 Eugene Shalygin changed: What|Removed |Added CC||eugene.shalygin+bugzilla.kd ||e...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 482278] Screen remains dimmed after unlocking
https://bugs.kde.org/show_bug.cgi?id=482278 --- Comment #4 from Eugene Shalygin --- Still an issue here with 6.0.3 and a single HDMI screen as well, albeit it happens less often with 6.0.3 as compared to 6.0.1. The screen is set to 50% brightness, and finds itself dimmed to the min (10%) after waking up from sleep. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483520] Window size is reset after screen sleep
https://bugs.kde.org/show_bug.cgi?id=483520 Eugene Shalygin changed: What|Removed |Added Keywords||regression -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 397953] KIO::highlightInFileManager does not respect default file manager setting when launched via FileManager1 DBus activation
https://bugs.kde.org/show_bug.cgi?id=397953 Eugene Shalygin changed: What|Removed |Added CC||eugene.shalygin+bugzilla.kd ||e...@gmail.com --- Comment #18 from Eugene Shalygin --- Unless Dolphin is running (and there is no FileManager1 service on the session bus), KIO::highlightInFileManager() opens a new nautilus. inode/directory mime-type is set to Dolphin, while the xdg-open utility opens Dolphin. I'd be happy if setting the default file application overwrite /usr/share/dbus-1/services/org.freedesktop.FileManager1.service. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483520] New: Window size is reset after screen sleep
https://bugs.kde.org/show_bug.cgi?id=483520 Bug ID: 483520 Summary: Window size is reset after screen sleep Classification: Plasma Product: kwin Version: 6.0.2 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: eugene.shalygin+bugzilla@gmail.com Target Milestone: --- Putting the screen to sleep and waking it up again resets non-maximized, but larger than 1920x1080 windows to 1920x1080. STEPS TO REPRODUCE 1. Open any window, size it to be bigger than 1920x1080. 2. Wait for the screen to go into the sleep mode. 3. Wake up the screen. OBSERVED RESULT The window is moved to the top left corner of the screen and its size is set to 1920x1080. SOFTWARE/OS VERSIONS Operating System: Gentoo Linux 2.15 KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.8.0-gentoo (64-bit) Graphics Platform: Wayland Graphics Processor: AMD Radeon Graphics ADDITIONAL INFORMATION This is a regression from 5.27. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 482278] New: Screen remains dimmed after unlocking
https://bugs.kde.org/show_bug.cgi?id=482278 Bug ID: 482278 Summary: Screen remains dimmed after unlocking Classification: Plasma Product: Powerdevil Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: eugene.shalygin+bugzilla@gmail.com CC: m...@ratijas.tk, natalie_clar...@yahoo.de Target Milestone: --- SUMMARY When powerdevil-6.0 is built with screen brightness support (HAVE_DDCUTIL), the screen brightness decreases as per power management settings, but is not restored upon unlocking the session. The brightness level slider in the applet is not updated as well. Changing the value there brings the desired brightness level back. STEPS TO REPRODUCE 1. Wait until the screen gets locked and powered off 2. Wake up the screen. Notice normal brightness level in the screenlock. 3. Unlock the session. OBSERVED RESULT Screen goes dim. EXPECTED RESULT Screen brightness corresponds to the value as it is set in the brightness applet. SOFTWARE/OS VERSIONS Operating System: Gentoo Linux 2.14 KDE Plasma Version: 6.0.0 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.7.7-gentoo (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 9 5900HX with Radeon Graphics Graphics Processor: AMD Radeon Graphics -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 480526] New: KDevelop always crashes when loading session cache
https://bugs.kde.org/show_bug.cgi?id=480526 Bug ID: 480526 Summary: KDevelop always crashes when loading session cache Classification: Applications Product: kdevelop Version: git master Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: Language Support: CPP (Clang-based) Assignee: kdevelop-bugs-n...@kde.org Reporter: eugene.shalygin+bugzilla@gmail.com Target Milestone: --- SUMMARY KDevelop, built against LLVM 17.0.6, always crashes when loading existing session cache. STEPS TO REPRODUCE 1. Load a project, wait for it to be parsed. 2. Close KDevelop. 3. Re-open KDevelop with this session, without clearing duchain cache or reparsing project on opening enabled. OBSERVED RESULT Thread 75 "Queue(0x55d" received signal SIGSEGV, Segmentation fault. #0 0x75d986fa in ??? () at /usr/lib64/libc.so.6 #1 0x741552b3 in KDevelop::ItemRepository::convertMonsterBucket(int, int) [clone .isra.0] () at /usr/lib64/libKDevPlatformLanguage.so.514 #2 0x741560b0 in KDevelop::ItemRepository::index(KDevelop::(anonymous namespace)::PersistentSymbolTableRequestItem const&) [clone .isra.0] () at /usr/lib64/libKDevPlatformLanguage.so.514 #3 0x7415721a in KDevelop::PersistentSymbolTable::addDeclaration(KDevelop::IndexedQualifiedIdentifier const&, KDevelop::IndexedDeclaration const&) () at /usr/lib64/libKDevPlatformLanguage.so.514 #4 0x740f53b8 in KDevelop::Declaration::setInSymbolTable(bool) () at /usr/lib64/libKDevPlatformLanguage.so.514 #5 0x7fffae913059 in KDevelop::Declaration* (anonymous namespace)::Visitor::createDeclarationCommon<(CXCursorKind)201, KDevelop::Declaration>(CXCursor, KDevelop::Identifier const&) () at /usr/lib64/libKDevClangPrivate.so.514 #6 0x7fffae918402 in (anonymous namespace)::visitCursor(CXCursor, CXCursor, void*) () at /usr/lib64/libKDevClangPrivate.so.514 #7 0x7fff952de24c in clang::cxcursor::CursorVisitor::Visit(CXCursor, bool) [clone .localalias] () at /usr/lib/llvm/17/lib64/libclang.so.17 #8 0x7fff952d in clang::cxcursor::CursorVisitor::handleDeclForVisitation(clang::Decl const*) [clone .localalias] () at /usr/lib/llvm/17/lib64/libclang.so.17 #9 0x7fff952defb8 in clang::cxcursor::CursorVisitor::VisitDeclContext(clang::DeclContext*) [clone .localalias] () at /usr/lib/llvm/17/lib64/libclang.so.17 #10 0x7fff952ddf2e in clang::cxcursor::CursorVisitor::VisitChildren(CXCursor) [clone .localalias] () at /usr/lib/llvm/17/lib64/libclang.so.17 #11 0x7fff952de10a in clang_visitChildren () at /usr/lib/llvm/17/lib64/libclang.so.17 #12 0x7fffae9092a3 in Builder::visit(CXTranslationUnitImpl*, void*, QHash const&, bool) () at /usr/lib64/libKDevClangPrivate.so.514 #13 0x7fffae923516 in ClangHelpers::buildDUChain(void*, QMultiHash const&, ParseSession const&, QFlags, QHash&, QHash const&, KDevelop::IndexedString const&, ClangIndex*, std::function const&) () at /usr/lib64/libKDevClangPrivate.so.514 #14 0x7fffae922d22 in ClangHelpers::buildDUChain(void*, QMultiHash const&, ParseSession const&, QFlags, QHash&, QHash const&, KDevelop::IndexedString const&, ClangIndex*, std::function const&) () at /usr/lib64/libKDevClangPrivate.so.514 #15 0x7fffae922d22 in ClangHelpers::buildDUChain(void*, QMultiHash const&, ParseSession const&, QFlags, QHash&, QHash const&, KDevelop::IndexedString const&, ClangIndex*, std::function const&) () at /usr/lib64/libKDevClangPrivate.so.514 #16 0x7fffae922d22 in ClangHelpers::buildDUChain(void*, QMultiHash const&, ParseSession const&, QFlags, QHash&, QHash const&, KDevelop::IndexedString const&, ClangIndex*, std::function const&) () at /usr/lib64/libKDevClangPrivate.so.514 #17 0x7fffae922d22 in ClangHelpers::buildDUChain(void*, QMultiHash const&, ParseSession const&, QFlags, QHash&, QHash const&, KDevelop::IndexedString const&, ClangIndex*, std::function const&) () at /usr/lib64/libKDevClangPrivate.so.514 #18 0x7fffae922d22 in ClangHelpers::buildDUChain(void*, QMultiHash const&, ParseSession const&, QFlags, QHash&, QHash const&, KDevelop::IndexedString const&, ClangIndex*, std::function const&) () at /usr/lib64/libKDevClangPrivate.so.514 #19 0x7fffafe1020d in ClangParseJob::run(QSharedPointer, ThreadWeaver::Thread*) () at /usr/lib64/qt5/plugins/kdevplatform/514/kdevclangsupport.so #20 0x7283f027 in ThreadWeaver::IdDecorator::run(QSharedPointer, ThreadWeaver::Thread*) () at /usr/lib64/libKF5ThreadWeaver.so.5 #21 0x7283ec78 in ThreadWeaver::Executor::run(QSharedPointer const&, ThreadWeaver::Thread*) () at /usr/lib64/libKF5ThreadWeaver.so.5 #22 0x7283fb1f in ThreadWeaver::Job::execute(QSharedPointer const&, ThreadWeaver::Thread*) () at /usr/lib64/libKF5ThreadWeaver.so.5 #23 0x72844811 in ThreadWeaver::Thread::run() () at /usr/lib64/libKF5ThreadWeaver.so.5 #24 0x7fff
[Falkon] [Bug 479244] Falkon blocks log in to gitlab.com
https://bugs.kde.org/show_bug.cgi?id=479244 --- Comment #3 from Eugene Shalygin --- Thank you for the quick investigation! -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 479244] Falkon blocks log in to gitlab.com
https://bugs.kde.org/show_bug.cgi?id=479244 Eugene Shalygin changed: What|Removed |Added Platform|Other |Gentoo Packages -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 479244] New: Falkon blocks log in to gitlab.com
https://bugs.kde.org/show_bug.cgi?id=479244 Bug ID: 479244 Summary: Falkon blocks log in to gitlab.com Classification: Applications Product: Falkon Version: 24.01.85 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: now...@gmail.com Reporter: eugene.shalygin+bugzilla@gmail.com Target Milestone: --- SUMMARY When trying to log in into gitlab.com, the browser enters an infinite loop checking connection security. The console log contains: Error with Permissions-Policy header: Origin trial controlled feature not enabled: 'browsing-topics'. Error with Permissions-Policy header: Origin trial controlled feature not enabled: 'interest-cohort'. Error with Permissions-Policy header: Unrecognized feature: 'payment'. Error with Permissions-Policy header: Unrecognized feature: 'usb'. GET https://gitlab.com/users/sign_in 403 Error with Permissions-Policy header: Origin trial controlled feature not enabled: 'browsing-topics'. Error with Permissions-Policy header: Origin trial controlled feature not enabled: 'interest-cohort'. Error with Permissions-Policy header: Unrecognized feature: 'payment'. Error with Permissions-Policy header: Unrecognized feature: 'usb'. VM4 userscript:_falkon_webchannel:456 Uncaught DOMException: Blocked a frame with origin "https://challenges.cloudflare.com"; from accessing a cross-origin frame. at userscript:_falkon_webchannel:456:309 at userscript:_falkon_webchannel:456:1064 STEPS TO REPRODUCE 1. Navigate to gitlab.com 2. Attempt to sign in SOFTWARE/OS VERSIONS Application version 24.01.85 (435962a9a) QtWebEngine version 6.6.1 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 477827] Kdevelop crashes on valgrind launch
https://bugs.kde.org/show_bug.cgi?id=477827 --- Comment #1 from Eugene Shalygin --- Running valgrind manually with the save executable results in: ==190644== Memcheck, a memory error detector ==190644== Copyright (C) 2002-2022, and GNU GPL'd, by Julian Seward et al. ==190644== Using Valgrind-3.22.0 and LibVEX; rerun with -h for copyright info ==190644== Command: ./x ==190644== valgrind: Fatal error at startup: a function redirection valgrind: which is mandatory for this platform-tool combination valgrind: cannot be set up. Details of the redirection are: valgrind: valgrind: A must-be-redirected function valgrind: whose name matches the pattern: strlen valgrind: in an object with soname matching: ld-linux-x86-64.so.2 valgrind: was not found whilst processing valgrind: symbols from the object with soname: ld-linux-x86-64.so.2 valgrind: valgrind: Possible fixes: (1, short term): install glibc's debuginfo valgrind: package on this machine. (2, longer term): ask the packagers valgrind: for your Linux distribution to please in future ship a non- valgrind: stripped ld.so (or whatever the dynamic linker .so is called) valgrind: that exports the above-named function using the standard valgrind: calling conventions for this platform. The package you need valgrind: to install for fix (1) is called valgrind: valgrind:On Debian, Ubuntu: libc6-dbg valgrind:On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo valgrind: valgrind: Note that if you are debugging a 32 bit process on a valgrind: 64 bit system, you will need a corresponding 32 bit debuginfo valgrind: package (e.g. libc6-dbg:i386). valgrind: valgrind: Cannot continue -- exiting now. Sorry. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 477827] New: Kdevelop crashes on valgrind launch
https://bugs.kde.org/show_bug.cgi?id=477827 Bug ID: 477827 Summary: Kdevelop crashes on valgrind launch Classification: Applications Product: kdevelop Version: unspecified Platform: Gentoo Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: eugene.shalygin+bugzilla@gmail.com Target Milestone: --- Application: kdevelop (5.13.240180 (24.01.80)) Qt Version: 5.15.11 Frameworks Version: 5.112.0 Operating System: Linux 6.6.2-gentoo x86_64 Windowing System: Wayland Distribution: "Gentoo Linux" DrKonqi: 5.27.9 [KCrashBackend] -- Information about the crash: Launching the memcheck session make KDevelop crash The crash can be reproduced every time. -- Backtrace: Application: KDevelop (kdevelop), signal: Segmentation fault [KCrash Handler] #4 0x7f123d5fd410 in typeinfo for KJobTrackerInterface () at /usr/lib64/libKF5CoreAddons.so.5 #5 0x7f123c2c7b34 in () at /usr/lib64/libQt5Core.so.5 #6 0x7f123d5a0490 in KJob::finished(KJob*, KJob::QPrivateSignal) () at /usr/lib64/libKF5CoreAddons.so.5 #7 0x7f123d5a0e4f in KJob::~KJob() () at /usr/lib64/libKF5CoreAddons.so.5 #8 0x7f11d53ab67d in () at /usr/lib64/qt5/plugins/kdevplatform/513/kdevvalgrind.so #9 0x7f123c2bf5b2 in QObjectPrivate::deleteChildren() () at /usr/lib64/libQt5Core.so.5 #10 0x7f123c2c596b in QObject::~QObject() () at /usr/lib64/libQt5Core.so.5 #11 0x7f123dcef639 in KDevelop::ExecuteCompositeJob::~ExecuteCompositeJob() () at /usr/lib64/libKDevPlatformUtil.so.513 #12 0x7f123c2bf7a7 in QObject::event(QEvent*) () at /usr/lib64/libQt5Core.so.5 #13 0x7f123cf6345e in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #14 0x7f123c293e68 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5 #15 0x7f123c2974e3 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib64/libQt5Core.so.5 #16 0x7f123c2e6a73 in () at /usr/lib64/libQt5Core.so.5 #17 0x7f1238281e82 in () at /usr/lib64/libglib-2.0.so.0 #18 0x7f1238285087 in () at /usr/lib64/libglib-2.0.so.0 #19 0x7f12382856ac in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #20 0x7f123c2e6566 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #21 0x7f123c29288b in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #22 0x7f123c29aded in QCoreApplication::exec() () at /usr/lib64/libQt5Core.so.5 #23 0x56407d28c66f in () #24 0x7f123c5e0eea in () at /usr/lib64/libc.so.6 #25 0x7f123c5e0fa5 in __libc_start_main () at /usr/lib64/libc.so.6 #26 0x56407d28d241 in () [Inferior 1 (process 185899) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 476995] New: The Folders pane only show subdirs one level deep
https://bugs.kde.org/show_bug.cgi?id=476995 Bug ID: 476995 Summary: The Folders pane only show subdirs one level deep Classification: Applications Product: gwenview Version: 23.08.3 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: eugene.shalygin+bugzilla@gmail.com Target Milestone: --- The folders pane only show the root ones and one level deep. STEPS TO REPRODUCE 1. Open any image in a deep sub-directory. 2. Open the "Folders" pane. OBSERVED RESULT There is no synchronization between the currently displayed image and the "Folders" pane. Expanding folders there does not work. SOFTWARE/OS VERSIONS Operating System: Gentoo Linux 2.14 KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.112.0 Qt Version: 5.15.11 Kernel Version: 6.6.1-gentoo (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[ktouch] [Bug 473617] Cannot enter the name when i first launch the app
https://bugs.kde.org/show_bug.cgi?id=473617 --- Comment #8 from Eugene Shalygin --- (In reply to Eugene Shalygin from comment #7) > The name can be pasted from the mouse buffer (middle click). But then it is the same problem with lesson window: the app does not register any key press, so it is completely unusable. -- You are receiving this mail because: You are watching all bug changes.
[ktouch] [Bug 473617] Cannot enter the name when i first launch the app
https://bugs.kde.org/show_bug.cgi?id=473617 --- Comment #7 from Eugene Shalygin --- The name can be pasted from the mouse buffer (middle click). -- You are receiving this mail because: You are watching all bug changes.
[ktouch] [Bug 473617] Cannot enter the name when i first launch the app
https://bugs.kde.org/show_bug.cgi?id=473617 Eugene Shalygin changed: What|Removed |Added CC||eugene.shalygin+bugzilla.kd ||e...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 474746] Wayland: all Gnome apps fonts are rendered without anti-aliasing
https://bugs.kde.org/show_bug.cgi?id=474746 --- Comment #14 from Eugene Shalygin --- Opps, had to restart the xdg-desktop-portal service, not the kde one. -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 474746] Wayland: all Gnome apps fonts are rendered without anti-aliasing
https://bugs.kde.org/show_bug.cgi?id=474746 --- Comment #13 from Eugene Shalygin --- Also, Firefox can't display content when GTK_USE_PORTAL=1, page loading indicator spins infinitely. -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 474746] Wayland: all Gnome apps fonts are rendered without anti-aliasing
https://bugs.kde.org/show_bug.cgi?id=474746 Eugene Shalygin changed: What|Removed |Added CC||eugene.shalygin+bugzilla.kd ||e...@gmail.com --- Comment #12 from Eugene Shalygin --- The fix does not work for me with 5.27.8. My /usr/share/xdg-desktop-portal/kde-portals.conf: [preferred] default=kde;gtk; org.freedesktop.impl.portal.Settings=kde;gtk; Restarted the plasma-xdg-desktop-portal-kde service and yet all GTK apps render fonts without anti-aliasing, use wrong cursor theme, etc. The only workaround is to set GTK_USE_PORTAL=0. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 469079] Kdevelop clang parser fails with GCC 13.1
https://bugs.kde.org/show_bug.cgi?id=469079 --- Comment #14 from Eugene Shalygin --- > So there is no fatal error in a single-file project? Are the "unknown type > name" errors printed somewhere? > > /usr/include/stdlib.h:141:8: error: unknown type name '_Float32' I see errors in the terminal when run KDEV_CLANG_DISPLAY_DIAGS=1 CLEAR_DUCHAIN_DIR=1 kdevelop, and the IDE shows error when I open those glibc headers. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 469079] Kdevelop clang parser fails with GCC 13.1
https://bugs.kde.org/show_bug.cgi?id=469079 --- Comment #12 from Eugene Shalygin --- The issue has not went away with update to GCC 13.2, so I sat down to create an MWE only to discover that the problem is not directly controlled by the C++20 mode. There is the following block for each _Float type in the /usr/include/bits/floatn-common.h file: # if !__GNUC_PREREQ (7, 0) || (defined __cplusplus && !__GNUC_PREREQ (13, 0)) typedef float _Float16 __attribute__ ((__mode__ (__HF__))); # endif When the "Compiler for path" is set to "GCC" in the project options dialog, and GCC version is >= 13, the Clang parser then runs into "fatal error: too many errors emitted, stopping now [-ferror-limit=]". My guess is __GNUC__ is defined somewhere to the actual GCC version, which prevents glibc to define those typedefs itself. Maybe the C++20 mode changed the list of includes so that the error state is triggered quicker. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 469079] Kdevelop clang parser fails with GCC 13.1
https://bugs.kde.org/show_bug.cgi?id=469079 --- Comment #11 from Eugene Shalygin --- I'm building GCC 13.2, once it's ready I create an MWE, or maybe the update resolves the issue. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 469079] Kdevelop clang parser fails with GCC 13.1
https://bugs.kde.org/show_bug.cgi?id=469079 --- Comment #6 from Eugene Shalygin --- Although the same GCC page states "These types are not supported when compiling C++." I don't understand what's going on then. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 469079] Kdevelop clang parser fails with GCC 13.1
https://bugs.kde.org/show_bug.cgi?id=469079 --- Comment #5 from Eugene Shalygin --- (In reply to Igor Kushnir from comment #4) > The failing KDevelop's tests use a default standard and C++14, so the issue > isn't limited to C++20. Does the standard version make a difference in your > case? Yes, definitely. Everything works fine in the C++17 mode. > What do you typedef these types to? float, double, and __float128. > I agree that injecting type aliases would be safer than macros. Do you mean > this option > https://clang.llvm.org/docs/ClangCommandLineReference.html#cmdoption-clang- > include-file ? Yes, the force-include option. > Does the Clang version make a difference or only GCC's? If only GCC's, then > I think the header should be included `if (isCpp)`, similarly to > https://invent.kde.org/kdevelop/kdevelop/-/commit/ > 35ea746ddd49e872998152cc157152c2cb5b86ea . I haven't tried clang-15, but why would it work if the newer version still has no these types? https://gcc.gnu.org/onlinedocs/gcc/Floating-Types.html says they are a new addition in C. > The header file can be installed with KDevelop, but then the exact path to > the installed header would have to be found at run-time... Alternatively the > header file can be stored in resources and copied into a temporary file at > run-time (similarly to how the define files are stored in /tmp/kdevelop.*). I see no big difference from the user point of view, and I guess it is not a big deal to find out own installation prefix at run-time? -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 469079] Kdevelop clang parser fails with GCC 13.1
https://bugs.kde.org/show_bug.cgi?id=469079 --- Comment #3 from Eugene Shalygin --- (In reply to Igor Kushnir from comment #2) > What are the practical consequences/problems? What workaround do you employ > for this bug? Well, the IDE ceases to work as soon as you turn the C++20 mode on. As a workaround I provide those types as typedefs in the Language support/Defines page of the project settings dialog. > Does anyone know how to fix this issue properly? I'd supply a header file that defines those types basing on Clang version, which can be force included. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 469079] New: Kdevelop clang parser fails with GCC 13.1
https://bugs.kde.org/show_bug.cgi?id=469079 Bug ID: 469079 Summary: Kdevelop clang parser fails with GCC 13.1 Classification: Applications Product: kdevelop Version: git master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Language Support: CPP (Clang-based) Assignee: kdevelop-bugs-n...@kde.org Reporter: eugene.shalygin+bugzilla@gmail.com Target Milestone: --- Parsing fails with clang 16 and GCC 13 when GCC is selected as "Compiler for path". clang complains on these types being undefined: _Float32, _Float64, _Float128, _Float32x, _Float64x, _Float128x. This is with the C++20 mode set by CMake, haven't tried other standards. -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 468735] New: Kile: the Scanning project files dialog blocks the application
https://bugs.kde.org/show_bug.cgi?id=468735 Bug ID: 468735 Summary: Kile: the Scanning project files dialog blocks the application Classification: Applications Product: kile Version: master Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: user interface Assignee: michel.lud...@gmail.com Reporter: eugene.shalygin+bugzilla@gmail.com Target Milestone: --- SUMMARY The Scanning project files dialog blocks interaction with the application completely, and at certain conditions the dialog does not go away. STEPS TO REPRODUCE 1. Set Kile options to reopen last projects on start up. 2. Remove/rename one of the project files. 3. Launch Kile. OBSERVED RESULT The application asks what to do with the removed project, but interaction with that dialog is impossible because everything is blocked by the Scanning project files dialog. Even if you are quick enough to choose and option before the scanning progress dialog appears, the progress dialog stays open forever, blocking any UI interaction with the main Kile window. EXPECTED RESULT Errors when loading projects closes the progress dialog. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 407444] Background parser gets confused by gcc-generated precompiled headers
https://bugs.kde.org/show_bug.cgi?id=407444 --- Comment #4 from Eugene Shalygin --- Created attachment 158128 --> https://bugs.kde.org/attachment.cgi?id=158128&action=edit remove CMake-generated precompiled headers from Clang arguments While we are waiting for a proper fix, I'd like to share my workaround for GCC and CMake. It simply drops cmake-generated -include path/to/cmake_pch.h[xx] arguments from clang invocation command line. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 464987] Shell script declared as POSIX-compliant but is not
https://bugs.kde.org/show_bug.cgi?id=464987 --- Comment #6 from Eugene Shalygin --- (In reply to Igor Kushnir from comment #5) > Or would it somehow work worse for zsh users? No, it should not be a problem for zsh users. -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 464368] New: qproperty-type-mismatch fails to extract type when Q_PROPERTY( is followed by a whitespace
https://bugs.kde.org/show_bug.cgi?id=464368 Bug ID: 464368 Summary: qproperty-type-mismatch fails to extract type when Q_PROPERTY( is followed by a whitespace Classification: Developer tools Product: clazy Version: unspecified Platform: Other OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: eugene.shalygin+bugzilla@gmail.com CC: smart...@kde.org Target Milestone: --- If property is declared as Q_PROPERTY( Type name ... ), clazy derives property type as an empty string. But some code formatting styles require whitespace inside braces :( STEPS TO REPRODUCE 1. Insert a whitespace after the opening brace in any Q_PROPERTY declaration OBSERVED RESULT Clazy resolves the type of the property to empty string and qproperty-type-mismatch always reports errors. EXPECTED RESULT Clazy trims contents of the Q_PROPERTY() macro before parsing. Clazy from Qt Creator 9.0.1 -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 392637] Please do not resolve symbolic links when adding files to project
https://bugs.kde.org/show_bug.cgi?id=392637 Eugene Shalygin changed: What|Removed |Added Resolution|WORKSFORME |--- Status|RESOLVED|REPORTED -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 407064] Cannot toggle breakpoint by single click
https://bugs.kde.org/show_bug.cgi?id=407064 --- Comment #14 from Eugene Shalygin --- (In reply to Igor Kushnir from comment #13) > Fixed in https://invent.kde.org/frameworks/ktexteditor/-/merge_requests/445 > (KTextEditor 5.101). Have 5.101 installed, but left clicks still show the menu. At least I know I can press Control to set a breakpoint, thank you! -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 407064] Cannot toggle breakpoint by single click
https://bugs.kde.org/show_bug.cgi?id=407064 Eugene Shalygin changed: What|Removed |Added CC||eugene.shalygin+bugzilla.kd ||e...@gmail.com --- Comment #11 from Eugene Shalygin --- (In reply to Gabriele Menna from comment #9) > Right click on the icons border triggers the Kate popup menu, instead of the > abitual kdevelop menu allowing to set the default click behaviour And the left click toggles another menu, which provides an option to set the default mark type, but settings that makes no difference, the next left click toggles the same menu. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 399783] C++ code parsing is slower than compilation
https://bugs.kde.org/show_bug.cgi?id=399783 --- Comment #4 from Eugene Shalygin --- It is still a problem. CLang-based code model in Qt creator, for example, parses faster than it takes to compile the code. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 399783] C++ code parsing is slower than compilation
https://bugs.kde.org/show_bug.cgi?id=399783 Eugene Shalygin changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 436318] Save session doesn't work under Wayland
https://bugs.kde.org/show_bug.cgi?id=436318 Eugene Shalygin changed: What|Removed |Added CC||eugene.shalygin+bugzilla.kd ||e...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 461980] New: KDevelop code model ignores using declarations for types
https://bugs.kde.org/show_bug.cgi?id=461980
Bug ID: 461980
Summary: KDevelop code model ignores using declarations for
types
Classification: Applications
Product: kdevelop
Version: git master
Platform: Gentoo Packages
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Language Support: CPP (Clang-based)
Assignee: kdevelop-bugs-n...@kde.org
Reporter: eugene.shalygin+bugzilla@gmail.com
Target Milestone: ---
When a type is introduced via a using declaration, it is not fully recognized
by the code model: the name is rendered colorless, have no tooltip, but it
participates in code completion.
#include
using std::string;
int main()
{
string s; // "string" is colorless and has no tooltip
s. // code completion works here
}
Introducing types via type aliases (using string = std::string) works.
Version 5.10.230370 (23.03.70)
--
You are receiving this mail because:
You are watching all bug changes.
[kile] [Bug 392637] Please do not resolve symbolic links when adding files to project
https://bugs.kde.org/show_bug.cgi?id=392637 --- Comment #2 from Eugene Shalygin --- (In reply to Justin Zobel from comment #1) Yes, it is still theere. I have to manually edit the project file to add symbolic links. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 413618] When I assign a key combination to turn off a screen using powerdevil, it stays off only for one second and then turns on again automatically
https://bugs.kde.org/show_bug.cgi?id=413618 Eugene Shalygin changed: What|Removed |Added CC||eugene.shalygin+bugzilla.kd ||e...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 379532] UI stucks in debug view after an unsuccesfull launch attempt
https://bugs.kde.org/show_bug.cgi?id=379532 Eugene Shalygin changed: What|Removed |Added Ever confirmed|0 |1 Status|NEEDSINFO |REOPENED Resolution|WAITINGFORINFO |--- --- Comment #2 from Eugene Shalygin --- Still exists in 5.10.221170 (22.11.70) -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 452382] KScreen turns my monitor back on after "xset dpms force off"
https://bugs.kde.org/show_bug.cgi?id=452382 --- Comment #8 from Eugene Shalygin --- (In reply to Danilo Luvizotto from comment #7) > Thank you for your tip. How do I disable automatic input selection? Can't > find it. Sorry, I don't know. Watched video [1] and saw no obvious option. My screens are much more primitive, they provide a straightforward option "Input auto switch". https://www.youtube.com/watch?v=TjhH1o1Ygms -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 452382] KScreen turns my monitor back on after "xset dpms force off"
https://bugs.kde.org/show_bug.cgi?id=452382 --- Comment #6 from Eugene Shalygin --- I am on 5.18.1 as well and experienced the same problem. Disabling automatic input selection in my screen settings helped. You can check X log for the events screens produce. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 452382] KScreen turns my monitor back on after "xset dpms force off"
https://bugs.kde.org/show_bug.cgi?id=452382 --- Comment #4 from Eugene Shalygin --- https://gitlab.freedesktop.org/drm/amd/-/issues/662 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 452382] KScreen turns my monitor back on after "xset dpms force off"
https://bugs.kde.org/show_bug.cgi?id=452382 --- Comment #3 from Eugene Shalygin --- Same problem on Gentoo with: Operating System: Gentoo Linux 2.8 KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.4 Kernel Version: 5.18.0-gentoo (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 9 5900HX with Radeon Graphics Memory: 62.3 GiB of RAM Graphics Processor: AMD RENOIR -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 452382] KScreen turns my monitor back on after "xset dpms force off"
https://bugs.kde.org/show_bug.cgi?id=452382 Eugene Shalygin changed: What|Removed |Added CC||eugene.shalygin+bugzilla.kd ||e...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 439592] KDevelop always crashes when parsing the CMake project
https://bugs.kde.org/show_bug.cgi?id=439592 --- Comment #12 from Eugene Shalygin --- Got back to this after some time. Seems like KDevelop's CMake parser can't handle strings with 0 bytes inside. Specifically, creating the CMake console project from the template and appending contents of Tests/RunCMake/Syntax/NullTerminatedArgument.cmake file from the CMake project to the CMakeLists.txt make KDevelop crash on it either during project loading or upon opening the file. Valgrind says: ==800842== Invalid read of size 1 ==800842==at 0x624870A: QUtf8::convertToUnicode(char const*, int, QTextCodec::ConverterState*) (in /usr/lib64/libQt5Core.so.5.15.3) ==800842==by 0x6248D55: QUtf8Codec::convertToUnicode(char const*, int, QTextCodec::ConverterState*) const (in /usr/lib64/libQt5Core.so.5.15.3) ==800842==by 0x60D1963: QString::fromLocal8Bit_helper(char const*, int) (in /usr/lib64/libQt5Core.so.5.15.3) ==800842==by 0x3A15398F: fromLocal8Bit (qstring.h:710) ==800842==by 0x3A15398F: CMakeListsParser::readCMakeFunction(cmListFileLexer_s*, CMakeFunctionDesc&) (cmakelistsparser.cpp:180) ==800842==by 0x3A1540CE: CMakeListsParser::readCMakeFile(QString const&) (cmakelistsparser.cpp:126) ==800842==by 0x3A1DEE17: CMakeParseJob::run(QSharedPointer, ThreadWeaver::Thread*) (cmakeparsejob.cpp:84) ==800842==by 0x9C9E557: ThreadWeaver::IdDecorator::run(QSharedPointer, ThreadWeaver::Thread*) (in /usr/lib64/libKF5ThreadWeaver.so.5.92.0) ==800842==by 0x9C9E366: ThreadWeaver::Executor::run(QSharedPointer const&, ThreadWeaver::Thread*) (in /usr/lib64/libKF5ThreadWeaver.so.5.92.0) ==800842==by 0x9C9F232: ThreadWeaver::Job::execute(QSharedPointer const&, ThreadWeaver::Thread*) (in /usr/lib64/libKF5ThreadWeaver.so.5.92.0) ==800842==by 0x9CA5A36: ThreadWeaver::Thread::run() (in /usr/lib64/libKF5ThreadWeaver.so.5.92.0) ==800842==by 0x605891B: QThreadPrivate::start(void*) (in /usr/lib64/libQt5Core.so.5.15.3) ==800842==by 0x67F9019: start_thread (in /lib64/libc.so.6) ==800842== Address 0x508a1ff2 is 13 bytes after a block of size 5 alloc'd ==800842==at 0x48447E5: malloc (vg_replace_malloc.c:381) ==800842==by 0x680B2CA: strdup (in /lib64/libc.so.6) ==800842==by 0x3A15145B: cmListFileLexerSetToken (cmListFileLexer.in.l:290) ==800842==by 0x3A15260A: cmListFileLexer_yylex (cmListFileLexer.in.l:185) ==800842==by 0x3A152C7E: cmListFileLexer_Scan (cmListFileLexer.in.l:507) ==800842==by 0x3A1536EA: CMakeListsParser::readCMakeFunction(cmListFileLexer_s*, CMakeFunctionDesc&) (cmakelistsparser.cpp:158) ==800842==by 0x3A1540CE: CMakeListsParser::readCMakeFile(QString const&) (cmakelistsparser.cpp:126) ==800842==by 0x3A1DEE17: CMakeParseJob::run(QSharedPointer, ThreadWeaver::Thread*) (cmakeparsejob.cpp:84) ==800842==by 0x9C9E557: ThreadWeaver::IdDecorator::run(QSharedPointer, ThreadWeaver::Thread*) (in /usr/lib64/libKF5ThreadWeaver.so.5.92.0) ==800842==by 0x9C9E366: ThreadWeaver::Executor::run(QSharedPointer const&, ThreadWeaver::Thread*) (in /usr/lib64/libKF5ThreadWeaver.so.5.92.0) ==800842==by 0x9C9F232: ThreadWeaver::Job::execute(QSharedPointer const&, ThreadWeaver::Thread*) (in /usr/lib64/libKF5ThreadWeaver.so.5.92.0) ==800842==by 0x9CA5A36: ThreadWeaver::Thread::run() (in /usr/lib64/libKF5ThreadWeaver.so.5.92.0) Debug build crashes under GDB after clearing duchain cache with the following stacktrace: #0 0x75f36d1c in __pthread_kill_implementation () at /lib64/libc.so.6 #1 0x75eeb6a2 in raise () at /lib64/libc.so.6 #2 0x75ed6469 in abort () at /lib64/libc.so.6 #3 0x75f2b278 in __libc_message () at /lib64/libc.so.6 #4 0x75f407fa in () at /lib64/libc.so.6 #5 0x75f423e5 in _int_free () at /lib64/libc.so.6 #6 0x75f44edf in free () at /lib64/libc.so.6 #7 0x7645c2a7 in QHashData::free_helper(void (*)(QHashData::Node*)) () at /usr/lib64/libQt5Core.so.5 #8 0x7fffc0a50e0b in QHash::freeData(QHashData*) (this=this@entry=0x7fff7a7fb110, x=) at /usr/include/qt5/QtCore/qhash.h:619 #9 0x7fffc0a50aea in QHash::~QHash() (this=0x7fff7a7fb110, __in_chrg=) at /usr/include/qt5/QtCore/qhash.h:250 #10 QSet::~QSet() (this=0x7fff7a7fb110, __in_chrg=) at /usr/include/qt5/QtCore/qset.h:53 #11 KDevelop::AbstractContextBuilder, CMakeFunctionDesc>::~AbstractContextBuilder() (this=0x7fff7a7fb040, __in_chrg=) at /usr/src/debug/dev-util/kdevelop-/kdevelop-/kdevplatform/language/duchain/builders/abstractcontextbuilder.h:51 #12 ContextBuilder::~ContextBuilder() (this=0x7fff7a7fb040, __in_chrg=) at /usr/src/debug/dev-util/kdevelop-/kdevelop-/plugins/cmake/duchain/contextbuilder.h:15 #13 KDevelop::AbstractDeclarationBuilder, CMakeFunctionDesc, ContextBuilder>::~AbstractDeclarationBuilder() (this=0x7fff7a7fb040, __in_chrg=) at /usr/src/debug/dev-util/kdevelop-/kdevelop-/kdevplatform/language/duchain/builders/a
[kwin] [Bug 425864] Aurorae-based windecos vanishing with libglvnd
https://bugs.kde.org/show_bug.cgi?id=425864 --- Comment #11 from Eugene Shalygin --- Works on Gentoo after libglvnd upgrade to 1.4.0. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 443987] New: Kate ignores kate: word-wrap-column comment
https://bugs.kde.org/show_bug.cgi?id=443987 Bug ID: 443987 Summary: Kate ignores kate: word-wrap-column comment Product: kate Version: 21.08.2 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: part Assignee: kwrite-bugs-n...@kde.org Reporter: eugene.shalygin+bugzilla@gmail.com Target Milestone: --- SUMMARY This setting from the file is ignored STEPS TO REPRODUCE 0. Enable displaying the word wrap marker. 1. Add kate: word-wrap-column XX comment to the file 2. Reopen the file OBSERVED RESULT Marker position does not change EXPECTED RESULT The value in the comment always overrides the value in the editor settings. SOFTWARE/OS VERSIONS amd64 KDE Plasma Version: 5.23.0 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 442481] Embedded terminal can't retrieve session data due to using wrong qdbus executable name
https://bugs.kde.org/show_bug.cgi?id=442481 --- Comment #3 from Eugene Shalygin --- https://invent.kde.org/kdevelop/kdevelop/-/merge_requests/260 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 442481] Embedded terminal can't retrieve session data due to using wrong qdbus executable name
https://bugs.kde.org/show_bug.cgi?id=442481 Eugene Shalygin changed: What|Removed |Added Ever confirmed|0 |1 Status|NEEDSINFO |CONFIRMED Resolution|WORKSFORME |--- --- Comment #2 from Eugene Shalygin --- Thank you for looking into this! So, I've got Gentoo and zsh here. The kdevplatform_shell_environment.sh absolutely does not work in this environment. 1. My $ZDOTDIR is empty: it fails to detect zsh. Why not simply check $SHELL? E.g. _shell=$(basename "$SHELL"). I guess those who rename their shell executables know that they are doing. 2. This "$(which $_qdbus 2> /dev/null)" executes result of "which $_qdbus", so when it is negated, $_qdbus value is not changed when there is no qdbus-qt5 executable. A proper test is: if ! command -v $_qdbus &> /dev/null; then _qdbus=qdbus if ! command -v $_qdbus &> /dev/null; then echo "The utility qdbus (or qdbus-qt5) is not in your path, the shell integration will not work properly." fi fi -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 442481] New: Embedded terminal can't retrieve session data due to using wrong qdbus executable name
https://bugs.kde.org/show_bug.cgi?id=442481 Bug ID: 442481 Summary: Embedded terminal can't retrieve session data due to using wrong qdbus executable name Product: kdevelop Version: 5.6.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: UI: general Assignee: kdevelop-bugs-n...@kde.org Reporter: eugene.shalygin+bugzilla@gmail.com Target Milestone: --- SUMMARY It is just qdbus in Gentoo, while KDevelop attempts to call qdbus-qt5 STEPS TO REPRODUCE 1. Open the terminal tab OBSERVED RESULT getSessionDir:1: command not found: qdbus-qt5 executeInAppSync:6: command not found: qdbus-qt5 getSessionDir:1: command not found: qdbus-qt5 getSessionDir:1: command not found: qdbus-qt5 executeInAppSync:6: command not found: qdbus-qt5 getSessionName:1: command not found: qdbus-qt5 You are controlling the KDevelop session ''. Type help! for more information. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 442308] High CPU usage with network activity
https://bugs.kde.org/show_bug.cgi?id=442308 --- Comment #1 from Eugene Shalygin --- For the illustration purposes the network activity columns are enabled in the screenshot, but CPU usage stays the same with the columns set to "hidden". -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 414036] ksgrd_network_helper uses a lot of CPU on high network load
https://bugs.kde.org/show_bug.cgi?id=414036 --- Comment #28 from Eugene Shalygin --- (In reply to Nate Graham from comment #27) > Can you file a bug report for that? If that helps - #442308 -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 442308] New: High CPU usage with network activity
https://bugs.kde.org/show_bug.cgi?id=442308 Bug ID: 442308 Summary: High CPU usage with network activity Product: plasma-systemmonitor Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: eugene.shalygin+bugzilla@gmail.com CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- Created attachment 141477 --> https://bugs.kde.org/attachment.cgi?id=141477&action=edit illustration Basically a duplicate of #414036 with very same problem: any network activity maxes out CPU usage of the monitor app, so that it eats up the whole CPU core. STEPS TO REPRODUCE 1. Open system monitor 2. Got to the "Applications" tab 3. Initiate network activity OBSERVED RESULT The monitor app utilizes a full CPU core. SOFTWARE/OS VERSIONS Operating System: Gentoo KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 Kernel Version: 5.14.1-gentoo (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-4810MQ CPU @ 2.80GHz Memory: 31.3 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 4600 -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 414036] ksgrd_network_helper uses a lot of CPU on high network load
https://bugs.kde.org/show_bug.cgi?id=414036 --- Comment #26 from Eugene Shalygin --- (In reply to Nate Graham from comment #24) > In Plasma 5.22, the ksgrd_network_helper process is no longer used if you > use System Monitor instead of KSysGuard. So this bug should not be present > there. Nate, the System Monitor application itself uses CPU like crazy if there is network activity, even with network columns set to "Hidden". -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 385816] KDevelop has problems with multiple projects with same structure
https://bugs.kde.org/show_bug.cgi?id=385816 --- Comment #7 from Eugene Shalygin --- Thank you, it turned out I had one crashed KDevelop instance in the KDE bug handler. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 439592] KDevelop always crashes when parsing the CMake project
https://bugs.kde.org/show_bug.cgi?id=439592 --- Comment #11 from Eugene Shalygin --- Removing "0"s from that file allows KDevelop to finish project parsing without crashing. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 439592] KDevelop always crashes when parsing the CMake project
https://bugs.kde.org/show_bug.cgi?id=439592 --- Comment #10 from Eugene Shalygin --- Debug build crashes as well with the same backtrace as in the OP. 1. rm -fr ~/.cache/kdevduchain 2. open the cmake project and wait It crashes and at that moment the parsing progress shows "Tests/RunCMake/Syntax/NullTerminatedArgument.cmake" -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 385816] KDevelop has problems with multiple projects with same structure
https://bugs.kde.org/show_bug.cgi?id=385816 --- Comment #5 from Eugene Shalygin --- Also had two branches checked out in different dirs and both open in the same session. And KDevelop jumped to the source code in the second project from the first one when using "Jump to declaration" or "Jump to definition". Even after I unloaded the second project. And even after I then restarted KDevelop. And after I removed ~/.cache/kdevduchain (and restarted KDevelop once again). How is that possible? -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 385816] KDevelop has problems with multiple projects with same structure
https://bugs.kde.org/show_bug.cgi?id=385816 Eugene Shalygin changed: What|Removed |Added CC||eugene.shalygin+bugzilla.kd ||e...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 440531] New: Wrong data in tooltips for namespace aliases
https://bugs.kde.org/show_bug.cgi?id=440531 Bug ID: 440531 Summary: Wrong data in tooltips for namespace aliases Product: kdevelop Version: git master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Code completion Assignee: kdevelop-bugs-n...@kde.org Reporter: eugene.shalygin+bugzilla@gmail.com Target Milestone: --- SUMMARY for a declaration like "namespace a = b::c;" tooltips for 'a' show "namespace a = b", omitting further entries. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 439592] KDevelop always crashes when parsing the CMake project
https://bugs.kde.org/show_bug.cgi?id=439592 --- Comment #9 from Eugene Shalygin --- Yes, and sometimes when it asks for it after a crash too. Can't say either choice (to clean or not to clean) is more likely leads to a crash. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 439592] KDevelop always crashes when parsing the CMake project
https://bugs.kde.org/show_bug.cgi?id=439592 Eugene Shalygin changed: What|Removed |Added Status|RESOLVED|REOPENED Ever confirmed|0 |1 Resolution|WORKSFORME |--- --- Comment #7 from Eugene Shalygin --- Unfortunately, the problem is back. Please see the stacktrace below (I will try with debug build of kdevelop-python too). The kdevelop-python is recompiled after kdevelop updates. Application: KDevelop (kdevelop), signal: Segmentation fault [KCrash Handler] #4 0x7f197f39a41d in KDevelop::Declaration::ownIndex() const (this=0x7f1899c7e4a0) at /var/portage/tmp/portage/dev-util/kdevelop-/work/kdevelop-/kdevplatform/language/duchain/declaration.cpp:116 #5 0x7f18f9e833de in Python::DeclarationBuilder::assignToAttribute(Python::AttributeAst*, Python::DeclarationBuilder::SourceType const&) () at /usr/lib64/libkdevpythonduchain.so #6 0x7f18f9e83b7e in Python::DeclarationBuilder::visitAssignment(Python::AssignmentAst*) () at /usr/lib64/libkdevpythonduchain.so #7 0x7f18f9e80ab1 in non-virtual thunk to Python::DeclarationBuilder::visitNode(Python::Ast*) () at /usr/lib64/libkdevpythonduchain.so #8 0x7f1960053dbc in void Python::AstVisitor::visitNodeList(QList const&) () at /usr/lib64/libkdevpythonparser.so #9 0x7f18f9e80ab1 in non-virtual thunk to Python::DeclarationBuilder::visitNode(Python::Ast*) () at /usr/lib64/libkdevpythonduchain.so #10 0x7f1960054025 in Python::AstDefaultVisitor::visitTry(Python::TryAst*) () at /usr/lib64/libkdevpythonparser.so #11 0x7f18f9e80ab1 in non-virtual thunk to Python::DeclarationBuilder::visitNode(Python::Ast*) () at /usr/lib64/libkdevpythonduchain.so #12 0x7f1960054475 in Python::AstDefaultVisitor::visitCode(Python::CodeAst*) () at /usr/lib64/libkdevpythonparser.so #13 0x7f18f9e789c7 in Python::ContextBuilder::visitCode(Python::CodeAst*) () at /usr/lib64/libkdevpythonduchain.so #14 0x7f18f9e80ab1 in non-virtual thunk to Python::DeclarationBuilder::visitNode(Python::Ast*) () at /usr/lib64/libkdevpythonduchain.so #15 0x7f18f9e915bd in KDevelop::AbstractTypeBuilder::supportBuild(Python::Ast*, KDevelop::DUContext*) () at /usr/lib64/libkdevpythonduchain.so #16 0x7f18f9e7785c in KDevelop::AbstractContextBuilder::build(KDevelop::IndexedString const&, Python::Ast*, KDevelop::ReferencedTopDUContext const&) () at /usr/lib64/libkdevpythonduchain.so #17 0x7f18f9e743a3 in Python::ContextBuilder::build(KDevelop::IndexedString const&, Python::Ast*, KDevelop::ReferencedTopDUContext const&) () at /usr/lib64/libkdevpythonduchain.so #18 0x7f18f9e7c260 in Python::DeclarationBuilder::build(KDevelop::IndexedString const&, Python::Ast*, KDevelop::ReferencedTopDUContext const&) () at /usr/lib64/libkdevpythonduchain.so #19 0x7f18f9f3a103 in Python::ParseJob::run(QSharedPointer, ThreadWeaver::Thread*) () at /usr/lib64/qt5/plugins/kdevplatform/35/kdevpythonlanguagesupport.so #20 0x7f197cfbbf38 in ThreadWeaver::IdDecorator::run(QSharedPointer, ThreadWeaver::Thread*) () at /usr/lib64/libKF5ThreadWeaver.so.5 #21 0x7f197cfbc9a7 in ThreadWeaver::Executor::run(QSharedPointer const&, ThreadWeaver::Thread*) () at /usr/lib64/libKF5ThreadWeaver.so.5 #22 0x7f197cfbb6d3 in ThreadWeaver::Job::execute(QSharedPointer const&, ThreadWeaver::Thread*) () at /usr/lib64/libKF5ThreadWeaver.so.5 #23 0x7f197cfb9867 in ThreadWeaver::Thread::run() () at /usr/lib64/libKF5ThreadWeaver.so.5 #24 0x7f19808295f9 in QThreadPrivate::start(void*) () at /usr/lib64/libQt5Core.so.5 #25 0x7f197da0ccde in start_thread () at /lib64/libpthread.so.0 #26 0x7f19803dd69f in clone () at /lib64/libc.so.6 Thread 9 (Thread 0x7f180e7bc640 (LWP 3583379) "Queue(0x56368e2"): #1 0x7f19803ab933 in nanosleep () at /lib64/libc.so.6 #2 0x7f1980821d95 in QThread::usleep(unsigned long) () at /usr/lib64/libQt5Core.so.5 #3 0x7f197f3a4326 in KDevelop::DUChainLock::lockForWrite(unsigned int) (this=, timeout=0) at /var/portage/tmp/portage/dev-util/kdevelop-/work/kdevelop-/kdevplatform/language/duchain/duchainlock.cpp:170 #4 0x7f197f3a449c in KDevelop::DUChainWriteLocker::lock() (this=this@entry=0x7f180e7b9da0) at /var/portage/tmp/portage/dev-util/kdevelop-/work/kdevelop-/kdevplatform/language/duchain/duchainlock.cpp:277 #5 0x7f197f3a71b4 in KDevelop::DUChainWriteLocker::DUChainWriteLocker(KDevelop::DUChainLock*, unsigned int) (this=0x7f180e7b9da0, duChainLock=, timeout=0, this=, duChainLock=, timeout=) at /var/portage/tmp/portage/dev-util/kdevelop-/work/kdevelop-/kdevplatform/language/duchain/duchainlock.cpp:261 #6 0x7f18f9e84ae5 in Python::DeclarationBuilder::addArgumentTypeHints(Python::CallAst*, KDevelop::DUChainPointer) () at /usr/lib64/libkde
[kdevelop] [Bug 440430] New: KDevelop crashes launching debug session when launching arguments contain '\n'
https://bugs.kde.org/show_bug.cgi?id=440430 Bug ID: 440430 Summary: KDevelop crashes launching debug session when launching arguments contain '\n' Product: kdevelop Version: unspecified Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: eugene.shalygin+bugzilla@gmail.com Target Milestone: --- Application: kdevelop (5.6.40) (Compiled from sources) Qt Version: 5.15.2 Frameworks Version: 5.84.0 Operating System: Linux 5.13.5-gentoo x86_64 Windowing System: X11 Drkonqi Version: 5.22.4 Distribution: Gentoo/Linux -- Information about the crash: - What I was doing when the application crashed: Accidently copied debug arguments with line break symbol and launched debugging session. GDB replied with error: The exception is: Received a result with token not matching pending command. Pending: 23Received: 0 The MI response is: ^error,msg="Undefined command: \"_DIR\". Try \"help\"." and then KDEvelop crashed. The crash can be reproduced every time. -- Backtrace: Application: KDevelop (kdevelop), signal: Segmentation fault [KCrash Handler] #4 0x7fceefa0325b in void doActivate(QObject*, int, void**) () at /usr/lib64/libQt5Core.so.5 #5 0x7fceb4a999c1 in KDevMI::MIDebugger::exited(bool, QString const&) (this=this@entry=0x560217709da0, _t1=, _t1@entry=true, _t2=...) at /var/portage/tmp/portage/dev-util/kdevelop-/work/kdevelop-_build/plugins/debuggercommon/kdevdebuggercommon_autogen/EWIEGA46WW/moc_midebugger.cpp:288 #6 0x7fceb4aa0f17 in KDevMI::MIDebugger::processLine(QByteArray const&) (this=this@entry=0x560217709da0, line=...) at /var/portage/tmp/portage/dev-util/kdevelop-/work/kdevelop-/plugins/debuggercommon/midebugger.cpp:350 #7 0x7fceb4aa11bf in KDevMI::MIDebugger::readyReadStandardOutput() (this=0x560217709da0) at /var/portage/tmp/portage/dev-util/kdevelop-/work/kdevelop-/plugins/debuggercommon/midebugger.cpp:162 #8 0x7fceb4a9942a in QtPrivate::FunctorCall, QtPrivate::List<>, void, void (KDevMI::MIDebugger::*)()>::call(void (KDevMI::MIDebugger::*)(), KDevMI::MIDebugger*, void**) (arg=, o=, f=) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:152 #9 QtPrivate::FunctionPointer::call, void>(void (KDevMI::MIDebugger::*)(), KDevMI::MIDebugger*, void**) (arg=, o=, f=) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:185 #10 QtPrivate::QSlotObject, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) (which=, this_=, r=, a=, ret=) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:418 #11 0x7fceefa03733 in void doActivate(QObject*, int, void**) () at /usr/lib64/libQt5Core.so.5 #12 0x7fceef96062d in QProcess::readyReadStandardOutput(QProcess::QPrivateSignal) () at /usr/lib64/libQt5Core.so.5 #13 0x7fceef95a405 in QProcessPrivate::tryReadFromChannel(QProcessPrivate::Channel*) () at /usr/lib64/libQt5Core.so.5 #14 0x7fceef960cfd in QProcess::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) () at /usr/lib64/libQt5Core.so.5 #15 0x7fceefa03768 in void doActivate(QObject*, int, void**) () at /usr/lib64/libQt5Core.so.5 #16 0x7fceef9fe07d in QSocketNotifier::activated(QSocketDescriptor, QSocketNotifier::Type, QSocketNotifier::QPrivateSignal) () at /usr/lib64/libQt5Core.so.5 #17 0x7fceef93 in QSocketNotifier::event(QEvent*) () at /usr/lib64/libQt5Core.so.5 #18 0x7fcef065b4cf in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #19 0x7fceef9d1418 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5 #20 0x7fceefa1ab4c in socketNotifierSourceDispatch(_GSource*, int (*)(void*), void*) () at /usr/lib64/libQt5Core.so.5 #21 0x7fceec03c44b in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0 #22 0x7fceec096108 in g_main_context_iterate.constprop () at /usr/lib64/libglib-2.0.so.0 #23 0x7fceec0365df in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #24 0x7fceefa1c328 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #25 0x7fceef9c99a3 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #26 0x7fcef0856abd in QDialog::exec() () at /usr/lib64/libQt5Widgets.so.5 #27 0x7fceed4ac0f7 in KMessageBox::createKMessageBox(QDialog*, QDialogButtonBox*, QIcon const&, QString const&, QStringList const&, QString const&, bool*, QFlags, QString const&, QMessageBox::Icon) () at /usr/lib64/libKF5WidgetsAddons.so.5 #28 0x7fceed4ac52d in KMessageBox::createKMessageBox(QDialog*, QDialogButtonBox*, QMessageBox::Icon, QString const&, QStringList const&, QString const&, bool*, QFlags, QString const&) () at /usr/lib64/libKF5WidgetsAddons.so.5 #29 0x7fceed4af339 in KMessageBox::detailedSorryInternal(QDialog
[kdevelop] [Bug 439592] KDevelop always crashes when parsing the CMake project
https://bugs.kde.org/show_bug.cgi?id=439592 Eugene Shalygin changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #6 from Eugene Shalygin --- Can not reproduce it anymore, probably after updating clang to 12.0.1 and recompiling KDevelop. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 439592] KDevelop always crashes when parsing the CMake project
https://bugs.kde.org/show_bug.cgi?id=439592
--- Comment #3 from Eugene Shalygin ---
Debug build does not seem to crash. In console output I see the following:
kdevelop.plugins.definesandincludes: error while fetching defines for the
compiler: "clang" ("-xc", "-std=c++17", "-dM", "-E", "-") "error: invalid
argument '-std=c++17' not allowed with 'C'\n"
kdevelop.plugins.definesandincludes: error while fetching includes for the
compiler: "clang" "clang version 12.0.0\nTarget: x86_64-pc-linux-gnu\nThread
model: posix\nInstalledDir: /usr/lib/llvm/12/bin\nSelected GCC installation:
/usr/lib/gcc/x86_64-pc-linux-gnu/11.1.0\nCandidate multilib: .;@m64\nCandidate
multilib: 32;@m32\nSelected multilib: .;@m64\n (in-process)\n
\"/usr/lib/llvm/12/bin/clang-12\" -cc1 -triple x86_64-pc-linux-gnu -E
-disable-free -disable-llvm-verifier -discard-value-names -main-file-name -
-mrelocation-model static -mframe-pointer=all -fmath-errno -fno-rounding-math
-mconstructor-aliases -munwind-tables -target-cpu x86-64 -tune-cpu generic
-fno-split-dwarf-inlining -debugger-tuning=gdb -v -resource-dir
/usr/lib/llvm/12/bin/../../../../lib/clang/12.0.0 -internal-isystem
/usr/local/include -internal-isystem
/usr/lib/llvm/12/bin/../../../../lib/clang/12.0.0/include
-internal-externc-isystem /include -internal-externc-isystem /usr/include
-std=gnu++17 -fdebug-compilation-dir
/home/eugene/develop/alien/cmake/cbuild/debug -ferror-limit 19
-fgnuc-version=4.2.1 -o - -x c -\nerror: invalid argument '-std=gnu++17' not
allowed with 'C'\n"
--
You are receiving this mail because:
You are watching all bug changes.
[kdevelop] [Bug 439592] KDevelop always crashes when parsing the CMake project
https://bugs.kde.org/show_bug.cgi?id=439592 --- Comment #2 from Eugene Shalygin --- Unfortunately, under Valgrind C++ parsing does not work at all: KDevelop can not find any include file even those from C++ stdlib. I see many messages from Valgring with the following content: Thread 1: status = VgTs_Runnable syscall 56 (lwpid 2096983) ==2096983==at 0x6818299: syscall (in /lib64/libc-2.33.so) ==2096983==by 0x613B4D3: QProcessPrivate::start(QFlags) (in /usr/lib64/libQt5Core.so.5.15.2) ==2096983==by 0x26F4953E: .LTHUNK0.lto_priv.1 (in /usr/lib64/qt5/plugins/kdevplatform/35/kdevdefinesandincludesmanager.so) ==2096983==by 0x26F40BE0: .LTHUNK3.lto_priv.0 (in /usr/lib64/qt5/plugins/kdevplatform/35/kdevdefinesandincludesmanager.so) ==2096983==by 0x26F2CF29: DefinesAndIncludesManager::defines(KDevelop::ProjectBaseItem*, KDevelop::IDefinesAndIncludesManager::Type) const (in /usr/lib64/qt5/plugins/kdevplatform/35/kdevdefinesandincludesmanager.so) ==2096983==by 0x27C98CC8: ClangParseJob::ClangParseJob(KDevelop::IndexedString const&, KDevelop::ILanguageSupport*) (in /usr/lib64/qt5/plugins/kdevplatform/35/kdevclangsupport.so) ==2096983==by 0x27C99DB5: non-virtual thunk to ClangSupport::createParseJob(KDevelop::IndexedString const&) (in /usr/lib64/qt5/plugins/kdevplatform/35/kdevclangsupport.so) ==2096983==by 0x6981E22: KDevelop::BackgroundParser::parseDocuments() (in /usr/lib64/libKDevPlatformLanguage.so.5.6.40) ==2096983==by 0x61CDEE5: QObject::event(QEvent*) (in /usr/lib64/libQt5Core.so.5.15.2) ==2096983==by 0x518D4CE: QApplicationPrivate::notify_helper(QObject*, QEvent*) (in /usr/lib64/libQt5Widgets.so.5.15.2) ==2096983==by 0x61AA417: QCoreApplication::notifyInternal2(QObject*, QEvent*) (in /usr/lib64/libQt5Core.so.5.15.2) ==2096983==by 0x61AAEB1: QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) (in /usr/lib64/libQt5Core.so.5.15.2) ==2096983==by 0x61F10C2: postEventSourceDispatch(_GSource*, int (*)(void*), void*) (in /usr/lib64/libQt5Core.so.5.15.2) ==2096983==by 0x9B0244A: g_main_context_dispatch (in /usr/lib64/libglib-2.0.so.0.6800.3) ==2096983==by 0x9B5C107: g_main_context_iterate.constprop.0 (in /usr/lib64/libglib-2.0.so.0.6800.3) ==2096983==by 0x9AFC5DE: g_main_context_iteration (in /usr/lib64/libglib-2.0.so.0.6800.3) ==2096983==by 0x61F5327: QEventDispatcherGlib::processEvents(QFlags) (in /usr/lib64/libQt5Core.so.5.15.2) ==2096983==by 0x61A29A2: QEventLoop::exec(QFlags) (in /usr/lib64/libQt5Core.so.5.15.2) ==2096983==by 0x61ADD8F: QCoreApplication::exec() (in /usr/lib64/libQt5Core.so.5.15.2) ==2096983==by 0x1144F0: main (in /usr/bin/kdevelop) client stack range: [0x1FFEFE1000 0x1FFF000FFF] client SP: 0x1FFEFFDC98 valgrind stack range: [0x10029AE000 0x1002AADFFF] top usage: 19456 of 1048576 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 439592] New: KDevelop always crashes when parsing the CMake project
https://bugs.kde.org/show_bug.cgi?id=439592 Bug ID: 439592 Summary: KDevelop always crashes when parsing the CMake project Product: kdevelop Version: unspecified Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: eugene.shalygin+bugzilla@gmail.com Target Milestone: --- Application: kdevelop (5.6.40) (Compiled from sources) Qt Version: 5.15.2 Frameworks Version: 5.83.0 Operating System: Linux 5.13.0-gentoo x86_64 Windowing System: X11 Drkonqi Version: 5.22.1 Distribution: Gentoo/Linux -- Information about the crash: - What I was doing when the application crashed: 1. Clone and open the CMake project (master branch) 2. Wait for parser to crash 3. Requesting for a help tooltip at almost any place in Source/cmFindPackageCommand.cxx also leads to a crash, whether the parsing is finished or not yet. The crash can be reproduced every time. -- Backtrace: Application: KDevelop (kdevelop), signal: Aborted [KCrash Handler] #4 0x7fc50679820e in raise () at /lib64/libc.so.6 #5 0x7fc506782536 in abort () at /lib64/libc.so.6 #6 0x7fc5067d94b8 in __libc_message () at /lib64/libc.so.6 #7 0x7fc5067e0eba in () at /lib64/libc.so.6 #8 0x7fc5067e216b in _int_free () at /lib64/libc.so.6 #9 0x7fc5067e5e74 in free () at /lib64/libc.so.6 #10 0x7fc506e530b2 in QMetaType::destroy(int, void*) () at /usr/lib64/libQt5Core.so.5 #11 0x7fc506e61c7e in QMetaCallEvent::~QMetaCallEvent() () at /usr/lib64/libQt5Core.so.5 #12 0x7fc506e61cd9 in QMetaCallEvent::~QMetaCallEvent() () at /usr/lib64/libQt5Core.so.5 #13 0x7fc506e3febc in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib64/libQt5Core.so.5 #14 0x7fc506e860c3 in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () at /usr/lib64/libQt5Core.so.5 #15 0x7fc5034c144b in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0 #16 0x7fc50351b108 in g_main_context_iterate.constprop () at /usr/lib64/libglib-2.0.so.0 #17 0x7fc5034bb5df in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #18 0x7fc506e8a328 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #19 0x7fc506e379a3 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #20 0x7fc506e42d90 in QCoreApplication::exec() () at /usr/lib64/libQt5Core.so.5 #21 0x562c76a444f1 in main () [Inferior 1 (process 1817371) detached] Possible duplicates by query: bug 439386, bug 439305, bug 438235, bug 437773, bug 437110. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 421441] Calendar widget highlights yesterday instead of today
https://bugs.kde.org/show_bug.cgi?id=421441 --- Comment #6 from Eugene Shalygin --- On Gentoo with the patched qtcore everything seems to be working fine now. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 437004] New: Slow task list update upon desktop switch
https://bugs.kde.org/show_bug.cgi?id=437004 Bug ID: 437004 Summary: Slow task list update upon desktop switch Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Task Manager and Icons-Only Task Manager Assignee: h...@kde.org Reporter: eugene.shalygin+bugzilla@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 The longer the session is ran, the slower the tasks applet becomes updating itself after desktop switch. The update time grows with the number of open apps too. After a day or so, it takes ~3 seconds for it to update after switching to a desktop with 6 top windows. Restarting plasmashell does not help. Log off/log in makes switching quick again. STEPS TO REPRODUCE 1. Work for 20 or more hours in a Plasma session. 2. Enable option to show tasks only from the current desktop. 3. Open > 5 apps on the same desktop. 4. Switch to another desktop. 5. Switch back to the previous desktop. OBSERVED RESULT The task applet does not update for a few seconds. EXPECTED RESULT The applet updates immediately. Operating System: Gentoo KDE Plasma Version: 5.21.80 KDE Frameworks Version: 5.83.0 Qt Version: 5.15.2 Kernel Version: 5.12.2-gentoo (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-4810MQ CPU @ 2.80GHz Memory: 31.3 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 4600 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 436983] New: Okular crashes on exit
https://bugs.kde.org/show_bug.cgi?id=436983 Bug ID: 436983 Summary: Okular crashes on exit Product: okular Version: unspecified Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: eugene.shalygin+bugzilla@gmail.com Target Milestone: --- Application: okular (21.07.70) (Compiled from sources) Qt Version: 5.15.2 Frameworks Version: 5.83.0 Operating System: Linux 5.12.2-gentoo x86_64 Windowing System: X11 Drkonqi Version: 5.21.80 Distribution: "Gentoo Base System release 2.7" -- Information about the crash: - What I was doing when the application crashed: Closing the app with open PDF file. This happens with every PDF file. The crash can be reproduced every time. -- Backtrace: Application: Okular (okular), signal: Segmentation fault [KCrash Handler] #4 0x7efe4755b143 in __memmove_avx_unaligned_erms () from /lib64/libc.so.6 #5 0x7efe48d176c8 in QList::detach_helper(int) () from /usr/lib64/libKF5WidgetsAddons.so.5 #6 0x7efe48d4f1ef in QList::removeAll(QComboBox* const&) () from /usr/lib64/libKF5WidgetsAddons.so.5 #7 0x7efe48d4f398 in QtPrivate::QFunctorSlotObject, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) () from /usr/lib64/libKF5WidgetsAddons.so.5 #8 0x7efe47b11733 in void doActivate(QObject*, int, void**) () from /usr/lib64/libQt5Core.so.5 #9 0x7efe47b0badf in QObject::destroyed(QObject*) () from /usr/lib64/libQt5Core.so.5 #10 0x7efe4863f7ab in QWidget::~QWidget() () from /usr/lib64/libQt5Widgets.so.5 #11 0x7efe4870c2a9 in QComboBox::~QComboBox() () from /usr/lib64/libQt5Widgets.so.5 #12 0x7efe4864fd7f in QWidgetAction::~QWidgetAction() () from /usr/lib64/libQt5Widgets.so.5 #13 0x7efe48d47b29 in KSelectAction::~KSelectAction() () from /usr/lib64/libKF5WidgetsAddons.so.5 #14 0x7efe47b064ec in QObjectPrivate::deleteChildren() () from /usr/lib64/libQt5Core.so.5 #15 0x7efe4863f646 in QWidget::~QWidget() () from /usr/lib64/libQt5Widgets.so.5 #16 0x7efe3ad397d9 in PageView::~PageView() () from /usr/lib64/qt5/plugins/okularpart.so #17 0x7efe47b064ec in QObjectPrivate::deleteChildren() () from /usr/lib64/libQt5Core.so.5 #18 0x7efe4863f646 in QWidget::~QWidget() () from /usr/lib64/libQt5Widgets.so.5 #19 0x7efe4863f839 in QWidget::~QWidget() () from /usr/lib64/libQt5Widgets.so.5 #20 0x7efe47b064ec in QObjectPrivate::deleteChildren() () from /usr/lib64/libQt5Core.so.5 #21 0x7efe4863f646 in QWidget::~QWidget() () from /usr/lib64/libQt5Widgets.so.5 #22 0x7efe487bf4f9 in QSplitter::~QSplitter() () from /usr/lib64/libQt5Widgets.so.5 #23 0x7efe47b064ec in QObjectPrivate::deleteChildren() () from /usr/lib64/libQt5Core.so.5 #24 0x7efe4863f646 in QWidget::~QWidget() () from /usr/lib64/libQt5Widgets.so.5 #25 0x7efe3ad689c9 in Sidebar::~Sidebar() () from /usr/lib64/qt5/plugins/okularpart.so #26 0x7efe47b064ec in QObjectPrivate::deleteChildren() () from /usr/lib64/libQt5Core.so.5 #27 0x7efe4863f646 in QWidget::~QWidget() () from /usr/lib64/libQt5Widgets.so.5 #28 0x7efe487bf789 in QStackedWidget::~QStackedWidget() () from /usr/lib64/libQt5Widgets.so.5 #29 0x7efe47b064ec in QObjectPrivate::deleteChildren() () from /usr/lib64/libQt5Core.so.5 #30 0x7efe4863f646 in QWidget::~QWidget() () from /usr/lib64/libQt5Widgets.so.5 #31 0x7efe487e8479 in QTabWidget::~QTabWidget() () from /usr/lib64/libQt5Widgets.so.5 #32 0x5605bf728d67 in Shell::~Shell() () #33 0x5605bf729389 in Shell::~Shell() () #34 0x7efe47b02c67 in QObject::event(QEvent*) () from /usr/lib64/libQt5Core.so.5 #35 0x7efe48f35409 in KXmlGuiWindow::event(QEvent*) () from /usr/lib64/libKF5XmlGui.so.5 #36 0x7efe486164cf in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #37 0x7efe47adf418 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib64/libQt5Core.so.5 #38 0x7efe47adfeb2 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib64/libQt5Core.so.5 #39 0x7efe47b260c3 in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () from /usr/lib64/libQt5Core.so.5 #40 0x7efe4620266b in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #41 0x7efe46260f38 in g_main_context_iterate.constprop () from /usr/lib64/libglib-2.0.so.0 #42 0x7efe4620115f in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #43 0x7efe47b2a328 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #44 0x7efe47ad79a3 in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #45 0x7efe47ae2d90 in QCoreApplication::exec() () from /usr/lib64/libQt5Core.so.5 #46 0x5605bf71fa21 in main () [Inferior 1 (process
[frameworks-kwayland] [Bug 435069] Commit 250feee0cac866730ef305aec4c0670d92cba34d breaks kwayland compilation
https://bugs.kde.org/show_bug.cgi?id=435069 --- Comment #2 from Eugene Shalygin --- Thank you! Could you, please, update build script in kwayland to bump required plasma-wayland-protocols version? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwayland] [Bug 435069] New: Commit 250feee0cac866730ef305aec4c0670d92cba34d breaks kwayland compilation
https://bugs.kde.org/show_bug.cgi?id=435069 Bug ID: 435069 Summary: Commit 250feee0cac866730ef305aec4c0670d92cba34d breaks kwayland compilation Product: frameworks-kwayland Version: unspecified Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: mgraess...@kde.org Reporter: eugene.shalygin+bugzilla@gmail.com CC: kwin-bugs-n...@kde.org Target Milestone: --- SUMMARY Does not compile against wayland-protocols 1.2.0 and git master. Reverting the said commit makes it compile. 5.80.0 builds too. STEPS TO REPRODUCE 1. mkdir -p build & cd build & cmake .. 2. make OBSERVED RESULT src/client/plasmawindowmanagement.cpp:425:1: error: too many initializers for ‘org_kde_plasma_window_listener’ 425 | }; | ^ src/client/plasmawindowmanagement.cpp: In member function ‘void KWayland::Client::PlasmaWindow::requestEnterActivity(const QString&)’: src/client/plasmawindowmanagement.cpp:1185:5: error: ‘org_kde_plasma_window_request_enter_activity’ was not declared in this scope; did you mean ‘org_kde_plasma_window_request_resize’? 1185 | org_kde_plasma_window_request_enter_activity(d->window, id.toUtf8()); | ^~~~ | org_kde_plasma_window_request_resize src/client/plasmawindowmanagement.cpp: In member function ‘void KWayland::Client::PlasmaWindow::requestLeaveActivity(const QString&)’: src/client/plasmawindowmanagement.cpp:1190:5: error: ‘org_kde_plasma_window_request_leave_activity’ was not declared in this scope; did you mean ‘org_kde_plasma_window_request_resize’? 1190 | org_kde_plasma_window_request_leave_activity(d->window, id.toUtf8()); | ^~~~ | org_kde_plasma_window_request_resize -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 422815] Aborted launch leave UI unusable
https://bugs.kde.org/show_bug.cgi?id=422815 --- Comment #1 from Eugene Shalygin --- A simple way to reproduce is an attempt to launch a debug session with no executable specified. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 425864] Aurorae-based windecos vanishing with libglvnd
https://bugs.kde.org/show_bug.cgi?id=425864 Eugene Shalygin changed: What|Removed |Added CC||eugene.shalygin+bugzilla.kd ||e...@gmail.com --- Comment #10 from Eugene Shalygin --- Same problem with an old Intel Haswell: Extended renderer info (GLX_MESA_query_renderer): Vendor: Intel Open Source Technology Center (0x8086) Device: Mesa DRI Intel(R) HD Graphics 4600 (HSW GT2) (0x416) Version: 21.0.0 Accelerated: yes Video memory: 1536MB Unified memory: yes Preferred profile: core (0x1) Max core profile version: 4.5 Max compat profile version: 3.0 Max GLES1 profile version: 1.1 Max GLES[23] profile version: 3.1 OpenGL vendor string: Intel Open Source Technology Center OpenGL renderer string: Mesa DRI Intel(R) HD Graphics 4600 (HSW GT2) OpenGL core profile version string: 4.5 (Core Profile) Mesa 21.0.0-rc5 OpenGL core profile shading language version string: 4.50 -- You are receiving this mail because: You are watching all bug changes.
