[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.
[plasmashell] [Bug 485870] Can't resize Application Launcher window under X11, works under Wayland
https://bugs.kde.org/show_bug.cgi?id=485870 Eugene San changed: What|Removed |Added CC||eugene...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 485870] Can't resize Application Launcher window under X11, works under Wayland
https://bugs.kde.org/show_bug.cgi?id=485870 Eugene San changed: What|Removed |Added Summary|Can't resize Application|Can't resize Application |Launcher windows under X11, |Launcher window under X11, |works under Wayland |works under Wayland -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 485870] New: Can't resize Application Launcher windows under X11, works under Wayland
https://bugs.kde.org/show_bug.cgi?id=485870 Bug ID: 485870 Summary: Can't resize Application Launcher windows under X11, works under Wayland Classification: Plasma Product: plasmashell Version: git-stable-Plasma/5.27 Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: plasma-b...@kde.org Reporter: eugene...@gmail.com CC: mikel5...@gmail.com, noaha...@gmail.com Target Milestone: 1.0 When opening Application Launcher window, mouse cursor changes to resize style but won't actually resize under X11. The same works as expected under Wayland session. Tested on: Ubuntu 23.10 - KDE 5.27.10, KF 5.112.0, QT 5.15.10 Also on Ubuntu 24.04 with also 5.27.11 Reproduction is simple. Install Kubuntu 23.10 or 24.04, Open Application Launcher by clicking the button in in the panel. Move cursor to the edge of the applet window, try to resize. On X11 the cursor just leaves the window border and does nothing. On Wayland the cursor "grabs" the window edge and resizes it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424485] GDbus-DBusMenu-Proxy does not work for GTK Wayland apps
https://bugs.kde.org/show_bug.cgi?id=424485 --- Comment #42 from Eugene San --- I know Plasma 6 is the main focus nowadays but the bug still affects Plasma 5 which is still shipped on Neon and upcoming Kubuntu 24.04 Plasma 5.27.11 and going to be an issue for a LOT of users and for a LONG time. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424485] GDbus-DBusMenu-Proxy does not work for GTK Wayland apps
https://bugs.kde.org/show_bug.cgi?id=424485 Eugene San changed: What|Removed |Added CC||eugene...@gmail.com -- 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.
[krdc] [Bug 483638] TAB key not functional inside rdp windows client
https://bugs.kde.org/show_bug.cgi?id=483638 eugene changed: What|Removed |Added CC||eug...@zvyagintsev.com --- Comment #2 from eugene --- Manjaro Linux, krdc 24.02 + freerdp2, tab key doesn't work in remote system window. -- 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
[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.
[kwin] [Bug 479201] New: Allow hiding of the titlebar for maximized windows
https://bugs.kde.org/show_bug.cgi?id=479201 Bug ID: 479201 Summary: Allow hiding of the titlebar for maximized windows Classification: Plasma Product: kwin Version: master Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: decorations Assignee: kwin-bugs-n...@kde.org Reporter: eugene...@gmail.com Target Milestone: --- Default plasma config consumes too much vertical space. It is not suitable for hardly suitable on small 16:9 displays. In previous versions there an option to hide titlebar for maximized windows but it no longer available. It is still possible to add below config option but doesn't work as expected. Instead it hides the titlebar permanently and does not restore the titlebar after un-maximizing. ``` [Windows] BorderlessMaximizedWindows=true ``` Please restore the option to configure titlebar behavior for maximized windows. Also, it would be nice to have window control buttons in the panel or at as first options in the window context menu. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 479200] New: Allow relocation of the tabs bar to other toolbars
https://bugs.kde.org/show_bug.cgi?id=479200 Bug ID: 479200 Summary: Allow relocation of the tabs bar to other toolbars Classification: Applications Product: konsole Version: master Platform: Neon OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: tabbar Assignee: konsole-de...@kde.org Reporter: eugene...@gmail.com Target Milestone: --- Konsole consumes too much vertical space with default 2 toolbars. It would be nice to be able to hide it and move to the main toolbar as a component. -- 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.
[systemsettings] [Bug 420280] Google authentication process gets stuck due to excessively old version of signon-ui library
https://bugs.kde.org/show_bug.cgi?id=420280 --- Comment #79 from Eugene --- (In reply to Bernie Innocenti from comment #73) > I tested signon-ui-0.17+15.10.20150810-1.20171022git4368bb7.fc40.x86_64 from > the Fedora COPR repo "hazel-bunny/ports". > > I confirm it fixes this particular bug: the authentication window renders > and you can type your login and password. > > I still couldn't log into my Google account because it has 2FA enabled and > the webengine doesn't seem to support USB security keys :-( > It seems KDE would be better off switching to gnome-online-accounts or other > actively developed framework. Tried it recently. Now it is stuck on reading the drive after login. :( -- 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.
[kwin] [Bug 15329] Save and remember positions of all windows
https://bugs.kde.org/show_bug.cgi?id=15329 --- Comment #83 from Eugene --- (In reply to Nate Graham from comment #82) > FWIW, as a workaround while this feature remains unimplemented, you should > be able to use Window Rules on Wayland to manually force windows to appear > where you want them. I would be very appreciate if you would show working window rules for Telegram window to always appear in upper right screen corner on Wayland. -- 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=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.
[kwin] [Bug 15329] Placement policy 'Remember'
https://bugs.kde.org/show_bug.cgi?id=15329 Eugene changed: What|Removed |Added Version|unspecified |5.26.5 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 15329] Placement policy 'Remember'
https://bugs.kde.org/show_bug.cgi?id=15329 Eugene changed: What|Removed |Added OS|Other |Linux Platform|Mandrake RPMs |unspecified -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 15329] Placement policy 'Remember'
https://bugs.kde.org/show_bug.cgi?id=15329 Eugene changed: What|Removed |Added CC||ken20...@ukr.net --- Comment #78 from Eugene --- 2023 is on the street, and it is impossible to switch between the windows of Wayland and XWayland. -- 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.
[digikam] [Bug 463502] New: Tags in captions sidebar are not sorted on image change when "Tags already asigned" option is enabled
https://bugs.kde.org/show_bug.cgi?id=463502 Bug ID: 463502 Summary: Tags in captions sidebar are not sorted on image change when "Tags already asigned" option is enabled Classification: Applications Product: digikam Version: 8.0.0 Platform: Compiled Sources OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Tags-Captions Assignee: digikam-bugs-n...@kde.org Reporter: eugene.a.v...@gmail.com Target Milestone: --- SUMMARY *** Tags in captions sidebar not sorted on image change when "Tags already asigned" option is enabled *** STEPS TO REPRODUCE 1. Open the right sidebar -> captions -> tags 2. Toggle the "Tags already asigned" option 3. Go to a next image OBSERVED RESULT Tags in the sidebar not sorted alphabetically EXPECTED RESULT Tags in the sidebar is sorted alphabetically when "Tags already asigned" option is on -- 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.
[kde] [Bug 462708] Automount NTFS HDD
https://bugs.kde.org/show_bug.cgi?id=462708 --- Comment #2 from Eugene --- Hello sir! if smb else comes with same trash/mount/fstab problem on arch-based distro, just forward him/her this link: https://wiki.archlinux.org/title/Trash_management#External_drives It works perfectly! Thank you for help anyway On 12/6/22 21:38, Nate Graham wrote: > https://bugs.kde.org/show_bug.cgi?id=462708 > > Nate Graham changed: > > What|Removed |Added > > Status|REPORTED|RESOLVED > CC||n...@kde.org > Resolution|--- |DOWNSTREAM > > --- Comment #1 from Nate Graham --- > This is an issue with the default PolKit rules and needs to be reported to > your > distro. > -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 462056] KDE can use only system SSD partition for trash, mounted NTFS one is not available in trash settings
https://bugs.kde.org/show_bug.cgi?id=462056 --- Comment #16 from Eugene --- I don't know sir )) Maybe smb else with similar problem. it's fine I understand you discuss stuff with many people at the same time. On 12/6/22 18:39, Nate Graham wrote: > https://bugs.kde.org/show_bug.cgi?id=462056 > > --- Comment #15 from Nate Graham --- > Oh sorry. Where did I get the idea you use Fedora? That's odd. > -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 462056] KDE can use only system SSD partition for trash, mounted NTFS one is not available in trash settings
https://bugs.kde.org/show_bug.cgi?id=462056 --- Comment #14 from Eugene --- I'm sorry I don't use Fedora, I use EndeavourOS On 12/6/22 17:44, Nate Graham wrote: > https://bugs.kde.org/show_bug.cgi?id=462056 > > --- Comment #13 from Nate Graham --- > Thanks. Because the password issue is a Fedora bug, can you file it at > https://bugzilla.redhat.com? And then please paste the link here as I'm > interested in having that fixed as well. :) > -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 462708] New: Automount NTFS HDD
https://bugs.kde.org/show_bug.cgi?id=462708 Bug ID: 462708 Summary: Automount NTFS HDD Classification: I don't know Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: eugene.bee...@yandex.ru Target Milestone: --- SUMMARY Automount NTFS HDD with KDE setting cause need for password after boot to mount the device STEPS TO REPRODUCE 1. Set automount in settings 2. Reboot OBSERVED RESULT Asks for password to mount the device EXPECTED RESULT Automount without password SOFTWARE/OS VERSIONS Linux/KDE Plasma: EndeavourOS (available in About System) KDE Plasma Version: 5.26.4 KDE Frameworks Version: 5.100.0 Qt Version: 5.15.7 ADDITIONAL INFORMATION Kernel 6.0.11-arch1-1 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 462056] KDE can use only system SSD partition for trash, mounted NTFS one is not available in trash settings
https://bugs.kde.org/show_bug.cgi?id=462056 --- Comment #12 from Eugene --- OK i will report that automount with KDE setting cause need for password after boot to mount the device. The widget problem is expected because it loads on login and after that i type password a mount the device (it just don't give me information about it because I mount it after widget loads) On 12/6/22 03:06, Nate Graham wrote: > https://bugs.kde.org/show_bug.cgi?id=462056 > > --- Comment #11 from Nate Graham --- > (In reply to Eugene from comment #10) >> The original bus is that automount with fstab using all the same >> parameters that "mount" command gives me in terminal makes trash >> workable only on root partition, if use automount through system >> parameters - I have to type password, the rest is just side effects of it > And that's not a bug, it's expected behavior since you need to use special > mount flags to make trash functionality work. The `mount` command doesn't know > what those are, so it's expected that you use the KDE automount system > instead. > > If using the KDE automount system is causing other bugs (e.g. having to enter > your password on boot or disk space widgets not working until plasmashell is > restarted) those are the bugs that need to be fixed. Can you file bug reports > for them, please? > -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 462056] KDE can use only system SSD partition for trash, mounted NTFS one is not available in trash settings
https://bugs.kde.org/show_bug.cgi?id=462056 --- Comment #10 from Eugene --- The original bus is that automount with fstab using all the same parameters that "mount" command gives me in terminal makes trash workable only on root partition, if use automount through system parameters - I have to type password, the rest is just side effects of it On 12/5/22 23:04, Nate Graham wrote: > https://bugs.kde.org/show_bug.cgi?id=462056 > > --- Comment #9 from Nate Graham --- >> i have to type password after boot to mount it > That's a bug in your distro's polkit rules. I can reproduce it. It should be > fixed there, rather than worked around. Can you file a bug report at > https://bugzilla.redhat.com/ and paste the link to it here? > >> always reset the disc usage widget because it loads before the mount happens > That's a different bug, similar to Bug 441556, but not quite the same thing. > Can you file a new bug report for it and paste the link to it here? > > > As a general matter, when you have a problem, you should file a bug on the > problem. If you seek a workaround, and the workaround has problems too, we're > just going to ask you what the original problem is that you were trying to > work > around. :) We want to fix the original bug that caused yu to seek a > workaround, > not bugs caused by the workaround. > -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 462056] KDE can use only system SSD partition for trash, mounted NTFS one is not available in trash settings
https://bugs.kde.org/show_bug.cgi?id=462056 --- Comment #8 from Eugene --- Yes sir! That's exactly what i do though, but the problem is that i have to type password after boot to mount it and always reset the disc usage widget because it loads before the mount happens. So the solution is not replacement for the fstab line. On 12/5/22 21:10, Nate Graham wrote: > https://bugs.kde.org/show_bug.cgi?id=462056 > > --- Comment #7 from Nate Graham --- > Then don't use fstab automount; if you want it to automount, use KDE's own > automounting system in System Settings > Removable Storage > Removable Devices > which should mount the disk with the correct options to make trash support > work. > -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 462619] New: Screen oss shortcut
https://bugs.kde.org/show_bug.cgi?id=462619 Bug ID: 462619 Summary: Screen oss shortcut Classification: I don't know Product: kde Version: unspecified Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: eugene.bee...@yandex.ru Target Milestone: --- SUMMARY If i'm in X11 session and use shortcut for screen off it turns off the screen only for approx 1-1,5 second and then screen turns back on again STEPS TO REPRODUCE 1. Log in to X11 session 2. Set up shortcut for screen off 3. Press the combination OBSERVED RESULT Screen off only for approximately 1 sec EXPECTED RESULT Screen off until i move mouse or press any key SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: EndeavourOS/5.26.4 (available in About System) KDE Plasma Version: KDE Frameworks Version: 5.100.0 Qt Version: 5.15.7 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 462056] KDE can use only system SSD partition for trash, mounted NTFS one is not available in trash settings
https://bugs.kde.org/show_bug.cgi?id=462056 --- Comment #6 from Eugene --- If I mount the partition manually at each boot - trash settings see it, if i use fstab automount with all the same aguments that terminal "mount" command gives me - the partition is not available in trash settings On 12/2/22 20:56, Nate Graham wrote: > https://bugs.kde.org/show_bug.cgi?id=462056 > > --- Comment #5 from Nate Graham --- > You said: >> If I remove this line from fstab and mount drive at boot - trash settings >> can see this partition and use it for moving deleted files accordingly. > I interpreted that to mean that it was working. Is that incorrect? > -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 462056] KDE can use only system SSD partition for trash, mounted NTFS one is not available in trash settings
https://bugs.kde.org/show_bug.cgi?id=462056 --- Comment #4 from Eugene --- Hello! The problem is there if i mount the drive even with all the same args manually as the default one. Basically with the line in fstab trash doesn't work for the partition On 12/1/22 23:50, Nate Graham wrote: > https://bugs.kde.org/show_bug.cgi?id=462056 > > Nate Graham changed: > > What|Removed |Added > > Status|NEEDSINFO |RESOLVED > Resolution|WAITINGFORINFO |NOT A BUG > > --- Comment #3 from Nate Graham --- > Indeed, the trash code is picky about which args a disk is mounted with to be > counted as a volume with its own trash, because the functionality needs some > special mount options to work properly. As you've discovered, some of those > parameters break this and falling back to the default settings makes it work. > So I would recommend doing that. > -- 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.
[frameworks-kio] [Bug 462056] KDE can use only system SSD partition for trash, mounted NTFS one is not available in trash settings
https://bugs.kde.org/show_bug.cgi?id=462056 --- Comment #2 from Eugene --- Hello! It"s been mounted with gdisks with parameters nosuid,nodev,nofail,x-gvfs-show, read/write works well in this case. If I remove this line from fstab and mount drive at boot - trash settings can see this partition and use it for moving deleted files accordingly. This situation I can see on EndeavourOS too. On 11/30/22 01:38, Nate Graham wrote: > https://bugs.kde.org/show_bug.cgi?id=462056 > > Nate Graham changed: > > What|Removed |Added > > CC||kdelibs-b...@kde.org, > ||n...@kde.org > Assignee|unassigned-b...@kde.org |fa...@kde.org > Version|unspecified |5.100.0 > Product|kde |frameworks-kio > Resolution|--- |WAITINGFORINFO > Status|REPORTED|NEEDSINFO >Component|general |Trash > > --- Comment #1 from Nate Graham --- > Is the NTFS disk mounted read/write, or read-only? > -- 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.
[kde] [Bug 462056] New: KDE can use only system SSD partition for trash, mounted NTFS one is not available in trash settings
https://bugs.kde.org/show_bug.cgi?id=462056 Bug ID: 462056 Summary: KDE can use only system SSD partition for trash, mounted NTFS one is not available in trash settings Classification: I don't know Product: kde Version: unspecified Platform: Manjaro OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: eugene.bee...@yandex.ru Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** KDE can use only system SSD partition for trash, mounted NTFS one is not available in trash settings STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT files are being moved to Trash on system SSD EXPECTED RESULT files to be moved to created Trash folder on HDD SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.26.3 KDE Frameworks Version: 5.100.0 Qt Version: 5.15.7 ADDITIONAL INFORMATION -- 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.
[kscreenlocker] [Bug 391442] Can't unlock the session from the first time while it has been locked in VM
https://bugs.kde.org/show_bug.cgi?id=391442 --- Comment #4 from Eugene --- Not actual at the moment. All is ok. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 461242] New: Wish: Use QMovie for animated images previews in StackedView
https://bugs.kde.org/show_bug.cgi?id=461242 Bug ID: 461242 Summary: Wish: Use QMovie for animated images previews in StackedView Classification: Applications Product: digikam Version: 8.0.0 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Preview-Engine Assignee: digikam-bugs-n...@kde.org Reporter: eugene.a.v...@gmail.com Target Milestone: --- Created attachment 153354 --> https://bugs.kde.org/attachment.cgi?id=153354=edit Example animations (gif, apng, webp, avif, jxl): 15px blinking square SUMMARY *** Currently qtav player is used for animated images playback, but it doesn't work well with short looped images (sometimes there is a сonsiderable delay between each loop) and it often freezes during playback. Previewing WebP animation results in a black screen (but it does work in MPV / Gwenview) and JXL animations not work at all. Would it be possible to add animated images playback via QMovie to the StackedView? *** KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 ffmpeg version: 5.0.1 ADDITIONAL INFORMATION There is a check for animated images in: core/app/views/stack/stackedview.cpp:341 void StackedView::setPreviewItem 363: DImg::isAnimatedImage(info.fileUrl().toLocalFile()) Thanks for amazing work on digikam. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 456306] Wayland-exclusive mouse cursor graphical artifacts
https://bugs.kde.org/show_bug.cgi?id=456306 --- Comment #13 from Eugene --- Hello. I can confirm, in KDE 5.26 mouse cursor is ok. Thank you. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 460786] Freeze for 3-4 seconds after assigning tag to an image
https://bugs.kde.org/show_bug.cgi?id=460786 --- Comment #5 from Eugene Vert --- Hello Maik Sent a dummy database to your email Turns out i had the "Show a count of items in Tree Views" enabled After disabling "Show a count of items in Tree Views" in "Settings->Views->Tree-Views" freeze no longer as noticeable, but is still present (~1.5 seconds) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 460786] Freeze for 3-4 seconds after assigning tag to an image
https://bugs.kde.org/show_bug.cgi?id=460786 --- Comment #3 from Eugene Vert --- Database type: SQLite Qt version: 5.15.6 After clicking "Apply" in Captions->Tags sidebar there is no debug messages until freeze occurs after ~1 second. After the freeze this message appears in logs: ``` digikam.general: Using 4 CPU core to run threads digikam.general: Using 4 CPU core to run threads digikam.general: Action Thread run 1 new jobs digikam.general: Action Thread run 1 new jobs digikam.general: One job is done digikam.general: One job is done digikam.general: Cancel Main Thread digikam.general: Cancel Main Thread ``` -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 460786] Freeze for 3-4 seconds after assigning tag to an image
https://bugs.kde.org/show_bug.cgi?id=460786 --- Comment #2 from Eugene Vert --- Created attachment 153072 --> https://bugs.kde.org/attachment.cgi?id=153072=edit Debug log -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 460786] New: Freeze for 3-4 seconds after assigning tag to an image
https://bugs.kde.org/show_bug.cgi?id=460786 Bug ID: 460786 Summary: Freeze for 3-4 seconds after assigning tag to an image Classification: Applications Product: digikam Version: 8.0.0 Platform: Compiled Sources OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Tags-Engine Assignee: digikam-bugs-n...@kde.org Reporter: eugene.a.v...@gmail.com Target Milestone: --- SUMMARY *** On assigning any tag to image, digikam freezes after ~1 second for 3-4 seconds. When image tags are changed, `TagsJob::run` is called, which recalculates counts for the tags in the database.(`CoreDB::getNumberOfImagesInTags` and `CoreDB::getNumberOfImagesInTagProperties`). With removed `getNumberOfImages*` from `TagsJob::run` no freezes are observed. *** STEPS TO REPRODUCE 1. Have a relatively large number (10 000) of tags in the database 2. Assign any tag to an image OBSERVED RESULT Digicam becomes unresponsive for 3-4 seconds EXPECTED RESULT No freezes -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 460510] Desktop settings drops to default after reboot or session switch
https://bugs.kde.org/show_bug.cgi?id=460510 --- Comment #4 from Eugene --- Got it. Thank you, sir! Wish you good luck! On 10/17/22 22:19, Nate Graham wrote: > https://bugs.kde.org/show_bug.cgi?id=460510 > > Nate Graham changed: > > What|Removed |Added > > Resolution|WAITINGFORINFO |DUPLICATE > Status|NEEDSINFO |RESOLVED > > --- Comment #3 from Nate Graham --- > Unfortunately this very annoying issue is impossible to truly fix with the > current broken-by-design system of mapping containments to screens. We are > rewriting it to work properly in Plasma 5.27. My apologies this happened, and > hopefully issues of this nature will finally be completely fixed for good in > Plasma 5.27. > > *** This bug has been marked as a duplicate of bug 450068 *** > -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 460510] Desktop settings drops to default after reboot or session switch
https://bugs.kde.org/show_bug.cgi?id=460510 --- Comment #2 from Eugene --- hello! 1) My hardware is ASUS Laptop with hybrid Intel HD4600/NV-GTX-850M graphics. 2) I'm using only one screen, only one desktop 3) Yes, wallpaper settings, all widgets disappear and all icons set to default size and positions. Nothing else was noticed On 10/16/22 06:13, Nate Graham wrote: > https://bugs.kde.org/show_bug.cgi?id=460510 > > Nate Graham changed: > > What|Removed |Added > > Resolution|--- |WAITINGFORINFO > Status|REPORTED|NEEDSINFO > CC||n...@kde.org > Severity|critical|normal > > --- Comment #1 from Nate Graham --- > Thanks for the bug report, but I'm afraid we're going to need more information > to debug it. Can you answer the following questions: > > 1. What is your hardware setup like? > 2. How many screens are you using? > 3. What exactly resets to the default? The wallpaper, widgets, and desktop > icon > positions? Or something else? > -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 460510] New: Desktop settings drops to default after reboot or session switch
https://bugs.kde.org/show_bug.cgi?id=460510 Bug ID: 460510 Summary: Desktop settings drops to default after reboot or session switch Classification: Plasma Product: plasmashell Version: 5.26.0 Platform: Manjaro OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: Desktop Containment Assignee: plasma-b...@kde.org Reporter: eugene.bee...@yandex.ru CC: notm...@gmail.com Target Milestone: 1.0 SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.26.0 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.6 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 456306] Wayland-exclusive mouse cursor graphical artifacts
https://bugs.kde.org/show_bug.cgi?id=456306 Eugene changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #8 from Eugene --- There is screenshot in duplicated report. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459679] distorted mouse pointer in Kubuntu 22.10 under wayland
https://bugs.kde.org/show_bug.cgi?id=459679 Eugene changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #10 from Eugene --- https://bugs.launchpad.net/ubuntu/+source/kwin/+bug/1990783 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459679] distorted mouse pointer in Kubuntu 22.10 under wayland
https://bugs.kde.org/show_bug.cgi?id=459679 --- Comment #9 from Eugene --- Created attachment 152567 --> https://bugs.kde.org/attachment.cgi?id=152567=edit syslog -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459679] distorted mouse pointer in Kubuntu 22.10 under wayland
https://bugs.kde.org/show_bug.cgi?id=459679 --- Comment #8 from Eugene --- Created attachment 152566 --> https://bugs.kde.org/attachment.cgi?id=152566=edit dmesg -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459679] distorted mouse pointer in Kubuntu 22.10 under wayland
https://bugs.kde.org/show_bug.cgi?id=459679 --- Comment #7 from Eugene --- $ glxinfo -B name of display: :1 display: :1 screen: 0 direct rendering: Yes Extended renderer info (GLX_MESA_query_renderer): Vendor: X.Org (0x1002) Device: AMD RV730 (DRM 2.50.0 / 5.19.0-15-generic, LLVM 15.0.1) (0x9490) Version: 22.2.0 Accelerated: yes Video memory: 1024MB Unified memory: no Preferred profile: core (0x1) Max core profile version: 3.3 Max compat profile version: 3.0 Max GLES1 profile version: 1.1 Max GLES[23] profile version: 3.0 Memory info (GL_ATI_meminfo): VBO free memory - total: 1023 MB, largest block: 1023 MB VBO free aux. memory - total: 1021 MB, largest block: 1021 MB Texture free memory - total: 1023 MB, largest block: 1023 MB Texture free aux. memory - total: 1021 MB, largest block: 1021 MB Renderbuffer free memory - total: 1023 MB, largest block: 1023 MB Renderbuffer free aux. memory - total: 1021 MB, largest block: 1021 MB Memory info (GL_NVX_gpu_memory_info): Dedicated video memory: 1024 MB Total available memory: 2045 MB Currently available dedicated video memory: 1023 MB OpenGL vendor string: X.Org OpenGL renderer string: AMD RV730 (DRM 2.50.0 / 5.19.0-15-generic, LLVM 15.0.1) OpenGL core profile version string: 3.3 (Core Profile) Mesa 22.2.0 OpenGL core profile shading language version string: 3.30 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL version string: 3.0 Mesa 22.2.0 OpenGL shading language version string: 1.30 OpenGL context flags: (none) OpenGL ES profile version string: OpenGL ES 3.0 Mesa 22.2.0 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459679] distorted mouse pointer in Kubuntu 22.10 under wayland
https://bugs.kde.org/show_bug.cgi?id=459679 --- Comment #6 from Eugene --- For any additional info, please, ask. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459679] distorted mouse pointer in Kubuntu 22.10 under wayland
https://bugs.kde.org/show_bug.cgi?id=459679 --- Comment #5 from Eugene --- Created attachment 152481 --> https://bugs.kde.org/attachment.cgi?id=152481=edit mouse pointer in Fedora 37 beta -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459679] distorted mouse pointer in Kubuntu 22.10 under wayland
https://bugs.kde.org/show_bug.cgi?id=459679 --- Comment #4 from Eugene --- I checked Fedora KDE 37 Beta. And the mouse pointer looks the same (screenshot attached). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459679] distorted mouse pointer in Kubuntu 22.10 under wayland
https://bugs.kde.org/show_bug.cgi?id=459679 Eugene changed: What|Removed |Added Version|unspecified |5.25.5 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459679] distorted mouse pointer in Kubuntu 22.10 under wayland
https://bugs.kde.org/show_bug.cgi?id=459679 --- Comment #3 from Eugene --- P.S. I am using distro drivers. There is No any additional vendor drivers installations. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459679] distorted mouse pointer in Kubuntu 22.10 under wayland
https://bugs.kde.org/show_bug.cgi?id=459679 --- Comment #2 from Eugene --- (In reply to Aleix Pol from comment #1) > It would be useful to get some details as to what could be special to your > system. > > Would you be able to see what's special about it? This is not something we > (I?) have seen before. > > Some ideas: > Can you reproduce this on 22.04? How about on another distro like Fedora? > Note that to test them you can generally just boot into their live images on > USB, no need to go all the way. > What graphics card and drivers are you using? > Do you get any outstanding error messages in > ~/.?local/share/sddm/wayland-session.log Hello, Aleix. How can I reproduce it if it happened only once I upgraded to 22.10 from 22.04? This is new to me also. I never experienced such before. And I am sorry, I forgot to specify my adapter: $ lspci | grep -i vga 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV730 XT [Radeon HD 4670] Log is empty: ~/.local/share/sddm$ ls -lh загалом 0 -rw--- 1 eugene eugene 0 вер 27 10:20 wayland-session.log -rw--- 1 eugene eugene 0 вер 25 02:52 xorg-session.log I will try Fedora ASAP. Thanks you for your answer. -- You are receiving this mail because: You are watching all bug changes.
[plasma-wayland-protocols] [Bug 459679] New: distorted mouse pointer in Kubuntu 22.10 under wayland
https://bugs.kde.org/show_bug.cgi?id=459679 Bug ID: 459679 Summary: distorted mouse pointer in Kubuntu 22.10 under wayland Classification: Plasma Product: plasma-wayland-protocols Version: unspecified Platform: Ubuntu OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: ken20...@ukr.net CC: aleix...@kde.org Target Milestone: --- Created attachment 152426 --> https://bugs.kde.org/attachment.cgi?id=152426=edit mouse pointer screenshot STEPS TO REPRODUCE 1. Upgrade to Kubuntu 22.10 dev OBSERVED RESULT Look at mouse pointer. It is distorted. See attached screenshot. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.19.0-15-generic KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 -- 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/abstractdeclarat
