[kscreenlocker] [Bug 495954] Plasma login screen black with only mouse cursor visible after resuming from sleep
https://bugs.kde.org/show_bug.cgi?id=495954 --- Comment #3 from Roman --- I don't think it is duplicate of 483163, I can (and do) lock and unlock (win+L) any time without problem. Black screen happens only after wake up from sleep. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 495954] Plasma login screen black with only mouse cursor visible after resuming from sleep
https://bugs.kde.org/show_bug.cgi?id=495954 --- Comment #1 from Roman --- One more thing: switching to other TTY and back does not change anything, still only black screen with mouse cursor. I can only swtich to other TTY, and reboot the system from console. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 495954] New: Plasma login screen black with only mouse cursor visible after resuming from sleep
https://bugs.kde.org/show_bug.cgi?id=495954 Bug ID: 495954 Summary: Plasma login screen black with only mouse cursor visible after resuming from sleep Classification: Plasma Product: kscreenlocker Version: 6.2.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: ro...@cervenak.info Target Milestone: --- Created attachment 175639 --> https://bugs.kde.org/attachment.cgi?id=175639&action=edit System log from resuming system SUMMARY After updating KDE to 6.2.3 (and nvidia-open to 565.57.01-2), Plasma login screen black with only mouse cursor visible after resuming from sleep. STEPS TO REPRODUCE 1. Running plasma desktop session on X11 2. Sleep 3. Wake up computer OBSERVED RESULT Black screen with mouse cursor visible and movable. Moving cursor across the screen, it can change to "text input" cursor when hovering over (invisible) password box perhaps. EXPECTED RESULT Normal login screen after resuming from sleep. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.2.3 KDE Frameworks Version: 6.7.0 Qt Version: 6.8.0 Kernel Version: 6.11.6-arch1-1 (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-9700K CPU @ 3.60GHz Memory: 15.6 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 4070/PCIe/SSE2 ADDITIONAL INFORMATION - Only happens with X11. When suspending from wayland session, login screen works normally (but I can't use wayland day-to-day for other reasons). - Only happens when suspending from Plasma session. When I log out to SDDM, sleep there, resuming back to SDDM works ok. - Attaching journal from resuming system - there are some suspicious looking lines from plasmashell, like "QRhiGles2: Context is lost" or "Graphics device lost, cleaning up scenegraph and releasing RHI", but when I grep my log for these, they are present for months, and I was sleeping/resuming without issue until last update. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 494687] Touchscreen toggle shortcut does nothing
https://bugs.kde.org/show_bug.cgi?id=494687 --- Comment #2 from Roman Odaisky --- (In reply to Nicolas Fella from comment #1) > The Wacom Tablet section refers to graphics tablets only, it's not supposed > to affect touchscreens The Wacom driver is also used for touchscreens. Is there a different section that can be used to set up a toggle shortcut? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 494687] New: Touchscreen toggle shortcut does nothing
https://bugs.kde.org/show_bug.cgi?id=494687 Bug ID: 494687 Summary: Touchscreen toggle shortcut does nothing Classification: Applications Product: systemsettings Version: 6.1.5 Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_keyboard Assignee: plasma-b...@kde.org Reporter: to.roma.from.kde...@qwertty.com CC: butir...@gmail.com, duha.b...@gmail.com, natalie_clar...@yahoo.de Target Milestone: --- Go to Settings > Touchscreen > Touchscreen. Observe that it shows a device named “Wacom HID 488F Finger” and the Enable checkbox works. Go to Settings > Keyboard > Shortcuts. Observe that a section called “Wacom Tablet” exists, it contains a shortcut named “Enable/Disable the Touch Tool” and the shortcut set for it is the same as was set in KDE 5, at which time it worked. Press the shortcut, nothing happens. Try normal things such as changing the shortcut to something else, deleting the Wacom Tablet section etc., doesn’t help. Given that the Enable checkbox works fine, hopefully it’s not a complicated hardware problem but just a question of the shortcut triggering the correct action. -- You are receiving this mail because: You are watching all bug changes.
[ksystemstats] [Bug 493122] Thermal Monitor widget missing CPU Package temperature and GPU temperature
https://bugs.kde.org/show_bug.cgi?id=493122 --- Comment #3 from Roman --- Well, if I go to project git: https://invent.kde.org/olib/thermalmonitor and use New Issue, there is big red warning "Please note that all bug reports and feature requests should be filed on bugs.kde.org and should never be raised here. " -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 493722] 1px gap between taskbar and maximized window
https://bugs.kde.org/show_bug.cgi?id=493722 --- Comment #4 from Roman --- I am not using wayland at all. I don't even have nvidia KMS enabled (which is must for wayland afaik) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 493722] 1px gap between taskbar and maximized window
https://bugs.kde.org/show_bug.cgi?id=493722 --- Comment #2 from Roman --- , Single 27" monitor 2560x1440 resolution, 125% scaling, X11 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 493722] New: 1px gap between taskbar and maximized window
https://bugs.kde.org/show_bug.cgi?id=493722 Bug ID: 493722 Summary: 1px gap between taskbar and maximized window Classification: Plasma Product: plasmashell Version: git-stable-Plasma/6.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: ro...@cervenak.info CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Created attachment 174130 --> https://bugs.kde.org/attachment.cgi?id=174130&action=edit screenshot of gap between taskbar and maximized window SUMMARY For panel height 42, there is gap between task bar panel and maximized window, so that colors of wallpaper can be seen. STEPS TO REPRODUCE 1. With panel at the bottom (all default, floating), set height to 42 2. Set some colorful background on your desktop to better see the issue 3. Open some dark program, i.e. Konsole, and maximize it OBSERVED RESULT There is 1px gap between taskbar and maximized window, wallpaper colors visible EXPECTED RESULT Bottom of maximized window should snap to taskbar without gap SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.1.5 KDE Frameworks Version: 6.6.0 Qt Version: 6.7.2 Kernel Version: 6.10.10-arch1-1 (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-9700K CPU @ 3.60GHz Memory: 15.6 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 4070/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 493186] Broken fonts on Overview Applications table
https://bugs.kde.org/show_bug.cgi?id=493186 --- Comment #4 from Roman --- Update: Just enabled modeset to try under wayland, and yes, it looks the same (fonts broken in Applications section) under Wayland -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 493186] Broken fonts on Overview Applications table
https://bugs.kde.org/show_bug.cgi?id=493186 --- Comment #3 from Roman --- Can't tell for Wayland, I am only using X11 for now, since I don't have KMS enabled (when I tried to enable it, Wayland worked, but I get only black screen with cursor after waking from sleep). -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 493186] New: Broken fonts on Overview Applications table
https://bugs.kde.org/show_bug.cgi?id=493186 Bug ID: 493186 Summary: Broken fonts on Overview Applications table Classification: Applications Product: plasma-systemmonitor Version: git-stable-Plasma/6.1 Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: ro...@cervenak.info CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- Created attachment 173716 --> https://bugs.kde.org/attachment.cgi?id=173716&action=edit system monitor overview broken fonts in Applications part SUMMARY Texts in Applications table in Overview screen are low quality/pixelated STEPS TO REPRODUCE 1. Open System Monitor OBSERVED RESULT Texts in Applications table in Overview screen are low quality/pixelated. See screenshot. In other parts of Overview, and also in other pages (Applications, Processes...) they are normal. EXPECTED RESULT Texts should be clear as everywhere else in System Monitor. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.1.5 KDE Frameworks Version: 6.5.0 Qt Version: 6.7.2 Kernel Version: 6.10.9-arch1-2 (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-9700K CPU @ 3.60GHz Memory: 15.6 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 4070/PCIe/SSE2 ADDITIONAL INFORMATION System fonts are all default Noto. Display configuration Global scale is 125%, on 2560x1440 monitor. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 493122] Thermal Monitor widget missing CPU Package temperature and GPU temperature
https://bugs.kde.org/show_bug.cgi?id=493122 --- Comment #1 from Roman --- Created attachment 173657 --> https://bugs.kde.org/attachment.cgi?id=173657&action=edit output of nvidia-smi -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 493122] New: Thermal Monitor widget missing CPU Package temperature and GPU temperature
https://bugs.kde.org/show_bug.cgi?id=493122 Bug ID: 493122 Summary: Thermal Monitor widget missing CPU Package temperature and GPU temperature Classification: Plasma Product: plasmashell Version: git-stable-Plasma/6.1 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: System Tray Assignee: plasma-b...@kde.org Reporter: ro...@cervenak.info CC: mate...@gmail.com Target Milestone: 1.0 Created attachment 173656 --> https://bugs.kde.org/attachment.cgi?id=173656&action=edit screenshot of configuration window with sensors available SUMMARY Thermal Monitor widget is missing important sensors, which are visible to lm_sensors/nvidia-smi, such as CPU Package temperature, and any GPU sensors. STEPS TO REPRODUCE 1. Add Thermal Monitor widget to taskbar, open Configure Thermal Monitor 2. Click Add Sensor... to open list of available sensors OBSERVED RESULT There are some hw sensors, such as individual CPU cores temperatures (with core 1 missing), but no CPU Package temperature, and no GPU Temperature (or any other GPU related sensors) EXPECTED RESULT CPU Package temperature and GPU Core temperature should be available SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.1.5 KDE Frameworks Version: 6.5.0 Qt Version: 6.7.2 Kernel Version: 6.10.9-arch1-2 (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-9700K CPU @ 3.60GHz Memory: 15.6 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 4070/PCIe/SSE2 ADDITIONAL INFORMATION Output of nvidia-smi: +-+ | NVIDIA-SMI 560.35.03 Driver Version: 560.35.03 CUDA Version: 12.6 | |-++--+ | GPU Name Persistence-M | Bus-Id Disp.A | Volatile Uncorr. ECC | | Fan Temp Perf Pwr:Usage/Cap | Memory-Usage | GPU-Util Compute M. | | || MIG M. | |=++==| | 0 NVIDIA GeForce RTX 4070Off | :01:00.0 On | N/A | | 0% 41CP8 7W / 200W | 962MiB / 12282MiB | 1% Default | | || N/A | +-++--+ +-+ | Processes: | | GPU GI CIPID Type Process name GPU Memory | |ID ID Usage | |=| |0 N/A N/A 797 G /usr/lib/Xorg 381MiB | |0 N/A N/A 860 G /usr/bin/kwalletd6 3MiB | |0 N/A N/A 888 G /usr/lib/kglobalacceld 2MiB | |0 N/A N/A 946 G /usr/bin/ksmserver 3MiB | |0 N/A N/A 948 G /usr/bin/kded6 3MiB | |0 N/A N/A 949 G /usr/bin/kwin_x11 16MiB | |0 N/A N/A 967 G /usr/bin/plasmashell 38MiB | |0 N/A N/A 1003 G /usr/lib/kactivitymanagerd 2MiB | |0 N/A N/A 1007 G ...b/polkit-kde-authentication-agent-1 3MiB | |0 N/A N/A 1008 G /usr/lib/org_kde_powerdevil 2MiB | |0 N/A N/A 1009 G /usr/lib/xdg-desktop-portal-kde 3MiB | |0 N/A N/A 1181 G /usr/bin/kaccess 3MiB | |0 N/A N/A 1183 G /usr/lib/DiscoverNotifier 3MiB | |0 N/A N/A 1244 G /usr/bin/konsole 2MiB | |0 N/A N/A 1316 G /usr/lib/firefox/firefox 0MiB | |0 N/A N/A 10298 G /usr/lib/kf6/kioworker 2MiB | +-+ Output of sensors: gigabyte_wmi-virtual-0 Adapter: Virtual device temp1:+33.0°C temp2:+42.0°C temp3:+22.0°C temp4:+37.0°C temp5:+33.0°C temp6:+34.0°C nvme-pci-0200 Adapter: PCI adapter Compo
[kdevelop] [Bug 492880] New: kdevelop crash while modifying CMakeLists.txt
https://bugs.kde.org/show_bug.cgi?id=492880 Bug ID: 492880 Summary: kdevelop crash while modifying CMakeLists.txt Classification: Applications 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: me+kdebugs@kropotkin.rocks Target Milestone: --- Application: kdevelop (6.0.240800 (24.08.0)) (Compiled from sources) Qt Version: 6.7.2 Frameworks Version: 6.5.0 Operating System: Linux 6.10.9-gentoo-x86_64 x86_64 Windowing System: Wayland Distribution: "Gentoo Linux" DrKonqi: 6.1.4 [KCrashBackend] -- Information about the crash: While modyfing the CMakeLists.txt from inside kdevelop it crashed. Maybe because kdevelop was running cmake configuration while I changed it. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: KDevelop (kdevelop), signal: Segmentation fault [KCrash Handler] #4 0x7f4209548024 in KDevelop::ProjectBaseItem::project() const () at /usr/lib64/libKDevPlatformProject.so.60 #5 0x7f420955f9c7 in ??? () at /usr/lib64/libKDevPlatformProject.so.60 #6 0x7f42095600c1 in KDevelop::BuilderJob::addItems(KDevelop::BuilderJob::BuildType, QList const&) () at /usr/lib64/libKDevPlatformProject.so.60 #7 0x7f41d563ac23 in ??? () at /usr/lib64/qt6/plugins/kdevplatform/60/KDevProjectManagerView.so #8 0x7f41d563c47d in ??? () at /usr/lib64/qt6/plugins/kdevplatform/60/KDevProjectManagerView.so #9 0x7f42098dae15 in ??? () at /usr/lib64/libQt6Core.so.6 #10 0x7f420a0a1326 in QAction::triggered(bool) () at /usr/lib64/libQt6Gui.so.6 #11 0x7f420a0a3cf9 in QAction::activate(QAction::ActionEvent) () at /usr/lib64/libQt6Gui.so.6 #12 0x7f420a94dc94 in ??? () at /usr/lib64/libQt6Widgets.so.6 #13 0x7f420a9bbd69 in ??? () at /usr/lib64/libQt6Widgets.so.6 #14 0x7f420ab2c6df in QWidget::event(QEvent*) () at /usr/lib64/libQt6Widgets.so.6 #15 0x7f420ab1c755 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQt6Widgets.so.6 #16 0x7f420ab1d59d in QApplication::notify(QObject*, QEvent*) () at /usr/lib64/libQt6Widgets.so.6 #17 0x7f42098f2d28 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib64/libQt6Core.so.6 #18 0x7f420ab242ce in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool, bool) () at /usr/lib64/libQt6Widgets.so.6 #19 0x7f420ab2aa84 in ??? () at /usr/lib64/libQt6Widgets.so.6 #20 0x7f420ab2dde0 in ??? () at /usr/lib64/libQt6Widgets.so.6 #21 0x7f420ab1c755 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQt6Widgets.so.6 #22 0x7f42098f2d28 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib64/libQt6Core.so.6 #23 0x7f4209d717fb in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () at /usr/lib64/libQt6Gui.so.6 #24 0x7f4209dca31c in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () at /usr/lib64/libQt6Gui.so.6 #25 0x7f420a19adf4 in ??? () at /usr/lib64/libQt6Gui.so.6 #26 0x7f4206080f44 in ??? () at /usr/lib64/libglib-2.0.so.0 #27 0x7f4206084067 in ??? () at /usr/lib64/libglib-2.0.so.0 #28 0x7f4206084680 in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #29 0x7f42096c22c3 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt6Core.so.6 #30 0x7f420991c27a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt6Core.so.6 #31 0x7f420a9b9591 in ??? () at /usr/lib64/libQt6Widgets.so.6 #32 0x7f420a9b96e0 in QMenu::exec(QPoint const&, QAction*) () at /usr/lib64/libQt6Widgets.so.6 #33 0x7f41d5651951 in ??? () at /usr/lib64/qt6/plugins/kdevplatform/60/KDevProjectManagerView.so #34 0x7f42098dae15 in ??? () at /usr/lib64/libQt6Core.so.6 #35 0x7f420aa83279 in QWidget::customContextMenuRequested(QPoint const&) () at /usr/lib64/libQt6Widgets.so.6 #36 0x7f420ab2ca90 in QWidget::event(QEvent*) () at /usr/lib64/libQt6Widgets.so.6 #37 0x7f420a9f0c24 in QFrame::event(QEvent*) () at /usr/lib64/libQt6Widgets.so.6 #38 0x7f42098f2a74 in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () at /usr/lib64/libQt6Core.so.6 #39 0x7f420ab1c745 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQt6Widgets.so.6 #40 0x7f420ab1e324 in QApplication::notify(QObject*, QEvent*) () at /usr/lib64/libQt6Widgets.so.6 #41 0x7f42098f2d28 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib64/libQt6Core.so.6 #42 0x7f420ab2a2a4 in ??? () at /usr/lib64/libQt6Widgets.so.6 #43 0x7f420ab2dde0 in ??? () at /usr/lib64/libQt6Widgets.so.6 #44 0x7f420ab1c755 in QApplicationPrivate::notify_helper(QObject*, QEven
[plasmashell] [Bug 491171] New: Plasma crashes when saving attachment in thunderbird
https://bugs.kde.org/show_bug.cgi?id=491171 Bug ID: 491171 Summary: Plasma crashes when saving attachment in thunderbird Classification: Plasma Product: plasmashell Version: 5.27.5 Platform: Debian stable OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: pos...@zohomail.eu CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Application: plasmashell (5.27.5) Qt Version: 5.15.8 Frameworks Version: 5.103.0 Operating System: Linux 6.1.0-23-amd64 x86_64 Windowing System: Wayland Distribution: Debian GNU/Linux 12 (bookworm) DrKonqi: 5.27.5 [CoredumpBackend] -- Information about the crash: Tasks carried out in thunderbird: 1. Open email 2. Click on save attachment (PDF-file) 3. Edit file name in save-dialog The crash occured during editing the file name. The reporter is unsure if this crash is reproducible. -- Backtrace (Reduced): #5 0x7fe76c5b3628 in KCoreConfigSkeleton::load() () from /lib/x86_64-linux-gnu/libKF5ConfigCore.so.5 [...] #7 0x7fe76c58b8e7 in KConfigWatcher::configChanged(KConfigGroup const&, QList const&) () from /lib/x86_64-linux-gnu/libKF5ConfigCore.so.5 #8 0x7fe76c5c54b9 in KConfigWatcher::onConfigChangeNotification(QHash > const&) () from /lib/x86_64-linux-gnu/libKF5ConfigCore.so.5 #9 0x7fe76c58bc52 in KConfigWatcher::qt_metacall(QMetaObject::Call, int, void**) () from /lib/x86_64-linux-gnu/libKF5ConfigCore.so.5 [...] #11 0x7fe76a6dd730 in QObject::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 The reporter indicates this bug may be a duplicate of or related to bug 463276, bug 463428, bug 463694, bug 470956, bug 471042, bug 471389, bug 471550, bug 472475, bug 473796, bug 474136, bug 474600, bug 474622, bug 477396, bug 478438, bug 485355, bug 487897. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 491171] Plasma crashes when saving attachment in thunderbird
https://bugs.kde.org/show_bug.cgi?id=491171 --- Comment #1 from Roman --- Created attachment 172213 --> https://bugs.kde.org/attachment.cgi?id=172213&action=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 489489] Taskbar bug freezing whole plasmashell
https://bugs.kde.org/show_bug.cgi?id=489489 --- Comment #3 from Roman --- Yes, sure. Operating System: openSUSE Tumbleweed 20240629 KDE Plasma Version: 6.1.1 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.2 Kernel Version: 6.9.6-3.gd344d3a-default (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Xeon® CPU E3-1575M v5 @ 3.00GHz Memory: 62.7 GiB of RAM Graphics Processor: Quadro P3000/PCIe/SSE2 Manufacturer: Dell Inc. Product Name: Precision 7720 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 489489] Taskbar bug freezing whole plasmashell
https://bugs.kde.org/show_bug.cgi?id=489489 --- Comment #1 from Roman --- I add also my report to NVidia. https://forums.developer.nvidia.com/t/555-release-feedback-discussion/293652/165?u=phoenix91140 It only happens with what I posted. And I believe there is some maybe mixed issue where not implemented sync or something well with nvidia. As far as I understand it happens only on nvidia card. So probably to cooperate with nvidia and fix the bug. Wayland is totally new thing to me, so please guide me, if any extra info needed -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 489489] New: Taskbar bug freezing whole plasmashell
https://bugs.kde.org/show_bug.cgi?id=489489 Bug ID: 489489 Summary: Taskbar bug freezing whole plasmashell Classification: Plasma Product: plasmashell Version: master Platform: openSUSE OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: phoenix91...@gmail.com CC: niccolo.venera...@gmail.com Target Milestone: 1.0 *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY STEPS TO REPRODUCE 1. Switch taskbar to icons mode (where only icons shown, without program name). 2. Make sure that window preview enabled 3. Hovering mouse over tasks switch windows with alt+tab. Over some time (for me like average 30 minutes) whole plasmashell will freeze (type of bug similar to endless I/O wait, meaning no high cpu load, just stopped process with only option to fix run kill with flag -9, as without flag no effect.). Then it keeps killing plasma shell for approx 7-8 seconds and reloads plasmashell. After reload no more window previews show, only huge icon drawn and since that plasmashell no longer hangs until system rebooted and previews shown again. Also less critical bug is, that if to hover mouse so that preview appears and then switch to full screen window preview gets stuck until window don't exit full screen mode or minimized. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Latest (available in About System) KDE Plasma Version: 6.1.1 KDE Frameworks Version: Latest Qt Version: 6.7.2 ADDITIONAL INFORMATION Guess that matters, it's Wayland session (this definitely matters), but also new nvidia driver as well. That's the only bug remaining so far that is critical to fix I found that really causes a lot of inconvenience. If to disable previews of windows, no hangs happen and stalled image artifacts happening. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 486666] New: Incorrect zooming when pressing CTRL+MOUSE_WHEEL_DOWN for the first time after start
https://bugs.kde.org/show_bug.cgi?id=48 Bug ID: 48 Summary: Incorrect zooming when pressing CTRL+MOUSE_WHEEL_DOWN for the first time after start Classification: Applications Product: dolphin Version: 23.08.5 Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: dr64...@mail.ru CC: kfm-de...@kde.org Target Milestone: --- SUMMARY When you start Dolphin and press CTRL+MOUSE_WHEEL_DOWN for the first time, the zoom increases, not decreases. While continuing to hold CTRL, the same thing happens when you try to scroll the wheel up (zoom in). But if you release CTRL and try again, then everything works as it should. The bug repeats every time Dolphin is launched and the first time CTRL+MOUSE_WHEEL is used, it does not matter where to start, from scrolling up or down. STEPS TO REPRODUCE 1. Start Dolphin. 2. Press CTRL. 3. Try to scroll the mouse wheel up or down. OBSERVED RESULT There is only a zoom in, instead of a zoom out. (on the first attempt) EXPECTED RESULT Zoom in when scrolling the mouse wheel up and zoom out when scrolling the mouse wheel down. SOFTWARE/OS VERSIONS Operating System: Void KDE Plasma Version: 5.27.11 KDE Frameworks Version: 5.115.0 Qt Version: 5.15.11 ADDITIONAL INFORMATION The keyboard shortcuts CTRL+PLUS_KEY and CTRL+MINUS_KEY work as expected. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 485497] New: It is not possible to restore a file with a Cyrillic path when it was moved using QFile::moveToTrash
https://bugs.kde.org/show_bug.cgi?id=485497 Bug ID: 485497 Summary: It is not possible to restore a file with a Cyrillic path when it was moved using QFile::moveToTrash Classification: Applications Product: dolphin Version: 23.08.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: dr64...@mail.ru CC: kfm-de...@kde.org Target Milestone: --- SUMMARY If you move a file containing Cyrillic letters in the path using QFile::moveToTrash Dolphin cannot restore it from the trash. STEPS TO REPRODUCE 1. Select a file containing Cyrillic characters in its path; 2. Move a file to the trash using the standard Qt function QFile::moveToTrash; 3. Try to restore a file from the trash. OBSERVED RESULT An error message window appears: The directory /home/user/???/ does not exist anymore, so it is not possible to restore this item to its original location. You can either recreate that directory and use the restore operation again, or drag the item anywhere else to restore it. EXPECTED RESULT Restoring a file "Text File.txt" to "/home/user/Проекты/" where it was originally located. SOFTWARE/OS VERSIONS Operating System: Void KDE Plasma Version: 5.27.11 KDE Frameworks Version: 5.115.0 Qt Version: 5.15.11 ADDITIONAL INFORMATION The bug could not be reproduced in other file managers (nemo and pcmanfm-qt have been tested). -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 407841] Kdevelop crashes with a segmentation fault when parsing my project
https://bugs.kde.org/show_bug.cgi?id=407841 David Roman changed: What|Removed |Added CC||me+kdebugs@kropotkin.rocks --- Comment #5 from David Roman --- I'm using kdevelop 5.13.240201 and it crashes for me. Some months ago it crashed and I solved it by removing the cache and kdevelop project files and starting from zero. Then it crashed again. Today while I was building the project and changing some files it crashed and now every time I open the problematic project it crashes. It also seems to be related with clang, from gdb backtrace: #0 0x7fffbdec44d0 in clang_getFileContents () at /usr/lib/llvm/17/lib64/libclang.so.17 #1 0x7fffc79c7188 in ClangUtils::getRawContents (unit=unit@entry=0x7ffe9c009a40, range=...) at /var/tmp/portage/dev-util/kdevelop-24.02.1/work/kdevelop-24.02.1/plugins/clang/util/clangutils.cpp:345 #2 0x7fffc79b0e34 in (anonymous namespace)::fixitsForDiagnostic (diagnostic=diagnostic@entry=0x7ffec059e570, unit=unit@entry=0x7ffe9c009a40) at /var/tmp/portage/dev-util/kdevelop-24.02.1/work/kdevelop-24.02.1/plugins/clang/duchain/clangproblem.cpp:63 #3 0x7fffc79b175c in ClangProblem::ClangProblem (this=0x7ffec0a9e540, diagnostic=0x7ffec059e570, unit=0x7ffe9c009a40) at /var/tmp/portage/dev-util/kdevelop-24.02.1/work/kdevelop-24.02.1/plugins/clang/duchain/clangproblem.cpp:154 #4 0x7fffc79b1a15 in ClangProblem::ClangProblem (this=this@entry=0x7ffec0a9c7e0, diagnostic=diagnostic@entry=0x7ffec059eb60, unit=unit@entry=0x7ffe9c009a40) at /var/tmp/portage/dev-util/kdevelop-24.02.1/work/kdevelop-24.02.1/plugins/clang/duchain/clangproblem.cpp:164 #5 0x7fffc79c1422 in UnknownDeclarationProblem::UnknownDeclarationProblem (this=this@entry=0x7ffec0a9c7e0, diagnostic=diagnostic@entry=0x7ffec059eb60, unit=unit@entry=0x7ffe9c009a40) at /var/tmp/portage/dev-util/kdevelop-24.02.1/work/kdevelop-24.02.1/plugins/clang/duchain/unknowndeclarationproblem.cpp:535 #6 0x7fffc79a423d in ClangDiagnosticEvaluator::createProblem (diagnostic=diagnostic@entry=0x7ffec059eb60, unit=0x7ffe9c009a40) at /var/tmp/portage/dev-util/kdevelop-24.02.1/work/kdevelop-24.02.1/plugins/clang/duchain/clangdiagnosticevaluator.cpp:108 #7 0x7fffc79b9efc in ParseSession::getOrCreateProblem (this=this@entry=0x7fff53dffac8, indexInTU=indexInTU@entry=9, diagnostic=diagnostic@entry=0x7ffec059eb60) at /var/tmp/portage/dev-util/kdevelop-24.02.1/work/kdevelop-24.02.1/plugins/clang/duchain/parsesession.cpp:501 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482653] Keyboard layout widget/tray entry state change leads to focus application launcher with current window unfocus
https://bugs.kde.org/show_bug.cgi?id=482653 Roman changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Ever confirmed|0 |1 Status|NEEDSINFO |CONFIRMED --- Comment #8 from Roman --- New info[2]: Если добавить показ раскладки в СИСТЕМНЫЙ ЛОТОК на панели, баг не проявляется. Только если как отдельный виджет, тогда она проявляется. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482653] Keyboard layout widget/tray entry state change leads to focus application launcher with current window unfocus
https://bugs.kde.org/show_bug.cgi?id=482653 Roman changed: What|Removed |Added CC||vlasovroman...@yandex.ru --- Comment #7 from Roman --- New info: This problem will be solved if you remove the keyboard layout widget from the tray. That exist in both modes (X11/wayland) -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 406917] Sync of webdav calendar stuck forever
https://bugs.kde.org/show_bug.cgi?id=406917 --- Comment #18 from Roman Zimmermann --- Definitely not fixed. I’m still experiencing this regularly. My last attempts to make this work again lead to losing my entire calendar. :-/ -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 473602] On X11, various applications crash in QXcbBackingStoreImage::flushPixmap when screens change
https://bugs.kde.org/show_bug.cgi?id=473602 Roman Pletka changed: What|Removed |Added CC||ro...@pletka.ch -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 480491] New: Warn about QFutureWatcher::connect: connecting after calling setFuture().
https://bugs.kde.org/show_bug.cgi?id=480491 Bug ID: 480491 Summary: Warn about QFutureWatcher::connect: connecting after calling setFuture(). Classification: Developer tools Product: clazy Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: dism...@gmail.com CC: smart...@kde.org Target Milestone: --- Hi. Is there possible to catch with clazy this warning: QFutureWatcher::connect: connecting after calling setFuture() is likely to produce race? This is probably something new, since i never previously received such a warning. Here is URL to Qt's code. https://github.com/openwebos/qt/blob/92fde5feca3d792dfd775348ca59127204ab4ac0/src/corelib/concurrent/qfuturewatcher.cpp#L367 Here is an example of code that should trigger the warning. MyClass myObject; // Start the computation. QFuture future = QtConcurrent::run(...); QFutureWatcher watcher; watcher.setFuture(future); connect(&watcher, &QFutureWatcher::finished, &myObject, &MyClass::handleFinished); According to documentation, correct code should look like this: MyClass myObject; QFutureWatcher watcher; connect(&watcher, &QFutureWatcher::finished, &myObject, &MyClass::handleFinished); // Start the computation. QFuture future = QtConcurrent::run(...); watcher.setFuture(future); Clazy 1.11 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477738] [NVIDIA] kwin on Wayland black screen with cursor after most resume-from-RAM
https://bugs.kde.org/show_bug.cgi?id=477738 Roman Pletka changed: What|Removed |Added CC||ro...@pletka.ch -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478231] On system with nvidia dGPU, external monitor turns black with only cursor shown after suspend to ram
https://bugs.kde.org/show_bug.cgi?id=478231 Roman Pletka changed: What|Removed |Added CC||ro...@pletka.ch -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 475726] system settings crash on opening 'application style' when in gnome DE
https://bugs.kde.org/show_bug.cgi?id=475726 --- Comment #3 from Roman --- Created attachment 164361 --> https://bugs.kde.org/attachment.cgi?id=164361&action=edit New crash information added by DrKonqi systemsettings (5.27.10) using Qt 5.15.11 It craches in KDE Plasma right on clicking on "Application style" item in "Global Theme" section. -- Backtrace (Reduced): #7 0x7fb1746a00c2 in qt_assert(char const*, char const*, int) () at /usr/lib/libQt5Core.so.5 [...] #10 0x7fb1755e6f74 in QStyleFactory::create(QString const&) () at /usr/lib/libQt5Widgets.so.5 [...] #12 0x7fb1724a47f1 in QQmlObjectCreator::finalize(QQmlInstantiationInterrupt&) () at /usr/lib/libQt5Qml.so.5 #13 0x7fb172450617 in QQmlIncubatorPrivate::incubate(QQmlInstantiationInterrupt&) () at /usr/lib/libQt5Qml.so.5 #14 0x7fb172450fc6 in QQmlEnginePrivate::incubate(QQmlIncubator&, QQmlContextData*) () at /usr/lib/libQt5Qml.so.5 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 475726] system settings crash on opening 'application style' when in gnome DE
https://bugs.kde.org/show_bug.cgi?id=475726 Roman changed: What|Removed |Added CC||nightcity...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[lokalize] [Bug 474685] Ctrl+Alt+B in lokalize no longer works
https://bugs.kde.org/show_bug.cgi?id=474685 --- Comment #13 from Roman Paholík --- Yes, it indeed works! -- You are receiving this mail because: You are watching all bug changes.
[i18n] [Bug 452328] appstreamcli validate complains about ksame's appstream file (klickety)
https://bugs.kde.org/show_bug.cgi?id=452328 Roman Paholík changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[i18n] [Bug 452328] appstreamcli validate complains about ksame's appstream file (klickety)
https://bugs.kde.org/show_bug.cgi?id=452328 --- Comment #1 from Roman Paholík --- Sorry, I have not noticed this bug until now, I just fixed it in KDE SVN repo in both KDE5 and KF6 branches. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 476843] New: [Feature request] read GPS data from phone to computer
https://bugs.kde.org/show_bug.cgi?id=476843 Bug ID: 476843 Summary: [Feature request] read GPS data from phone to computer Classification: Applications Product: kdeconnect Version: unspecified Platform: Other OS: All Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: me+kdebugs@kropotkin.rocks CC: andrew.g.r.hol...@gmail.com Target Milestone: --- I think will be a nice feature if kdeconnect could read GPS position from the phone and send it to the computers. One of the potentials I thought is when the phone and the computer are connected through a VPN network and not on the same access point. In that case, the phone and the computer can be very far away. In that case if the phone is lost making it emit a strong noise may not be enough, that's when will be nice to get GPS position of the phone. Another possibility (and the one I am most interested) is to use kdeconnect as an "API" to easily get a GPS position using the phone instead of buying a dedicated GPS hardware for the computer. Although this last one may seem more like a hack. -- 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 Roman Pletka changed: What|Removed |Added CC||ro...@pletka.ch -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 461891] Media control keyboard shortcuts always work on lock screen even if display of media control buttons is disabled
https://bugs.kde.org/show_bug.cgi?id=461891 Roman Odaisky changed: What|Removed |Added Version|5.25.5 |5.27.8 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455429] kwin sometimes composes windows in the wrong order when using the Slide Back effect
https://bugs.kde.org/show_bug.cgi?id=455429 Roman Pletka changed: What|Removed |Added CC||ro...@pletka.ch -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 445917] CPU-Tctl and Tccd missing from filtered sensors
https://bugs.kde.org/show_bug.cgi?id=445917 Roman Lebedev changed: What|Removed |Added CC||lebedev...@gmail.com --- Comment #5 from Roman Lebedev --- Due to this "filtering", it is now simply impossible to monitor CPU temperature on the AMD FX series or processors. Can that filtering please be ripped out? -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 406917] Sync of webdav calendar stuck forever
https://bugs.kde.org/show_bug.cgi?id=406917 Roman Zimmermann changed: What|Removed |Added CC||toro...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 474347] Last update from KDE destroyed system performance and loop CPU & GPU load
https://bugs.kde.org/show_bug.cgi?id=474347 --- Comment #2 from Roman --- (In reply to Nate Graham from comment #1) > Can you reproduce the issue when Telegram is *not* running? Yes. Any windows a bit moving around or even opened Ksysguard alone and cpu load goes too high compared to older versions of KDE -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 474347] New: Last update from KDE destroyed system performance and loop CPU & GPU load
https://bugs.kde.org/show_bug.cgi?id=474347 Bug ID: 474347 Summary: Last update from KDE destroyed system performance and loop CPU & GPU load Classification: Plasma Product: kwin Version: 5.27.7 Platform: openSUSE OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: core Assignee: kwin-bugs-n...@kde.org Reporter: phoenix91...@gmail.com Target Milestone: --- Created attachment 161529 --> https://bugs.kde.org/attachment.cgi?id=161529&action=edit cpu load SUMMARY Lastest update (5.27.7) loads CPU for 33-44% all the time. Top processes that eat whole cpu are KWin_X11 (if Wayland, then Kwin_Wayland) and plasma_shell. Any window movement also increases CPU load dramatically. Seems like something messed up with patches applied to KWin on latest (5.27.7) update. Unfortunately rollback to 5.27.6 impossible (due to no packaged remaining in system and OpenSUSE repository). Seems like KWin keep doing something erroneous in the loop loading half of cpu almost. All the rest in whole system is fine, expect KWin. Please fix bug. STEPS TO REPRODUCE 1. Update KDE 5.27.7 2. Start opening lightweight apps, like Telegram, Ksysguard and even move windows around and get almost 100% cpu load by Kwin_X11 and plasmashell 3. OBSERVED RESULT KWin does something incorrect with rendering utilizing CPU in the loop and also wasting GPU time. EXPECTED RESULT Fast, flawless almost no load operation as before update. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.27.7 KDE Frameworks Version: 5.109.0 Qt Version: 5.15.10 OpenSUSE Tumbleweed x86_64. Intel® Xeon® CPU E3-1575M v5 @ 3.00GHz, Quadro P3000/PCIe/SSE2. ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 472801] New: realme C11 2021 When connected to a PC, the phone freezes or periodically reboots
https://bugs.kde.org/show_bug.cgi?id=472801 Bug ID: 472801 Summary: realme C11 2021 When connected to a PC, the phone freezes or periodically reboots Classification: Applications Product: kdeconnect Version: unspecified Platform: Android OS: Android 11.x Status: REPORTED Severity: normal Priority: NOR Component: android-application Assignee: albertv...@gmail.com Reporter: romantkachu...@gmail.com CC: andrew.g.r.hol...@gmail.com Target Milestone: --- When connected to a PC, the phone freezes or periodically reboots 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: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 470144] Yakuake: Wayland keep above other windows not functional
https://bugs.kde.org/show_bug.cgi?id=470144 Roman changed: What|Removed |Added CC||mlj...@outlook.com -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 468866] New: Kontact stürzt ab bzw. friert ein ( OpenSuse Tumbleweed )
https://bugs.kde.org/show_bug.cgi?id=468866 Bug ID: 468866 Summary: Kontact stürzt ab bzw. friert ein ( OpenSuse Tumbleweed ) Classification: Applications Product: kontact Version: unspecified Platform: openSUSE OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: r.kuber...@gmail.com Target Milestone: --- Application: kontact (5.22.3 (22.12.3)) Qt Version: 5.15.8 Frameworks Version: 5.105.0 Operating System: Linux 6.2.10-1-default x86_64 Windowing System: X11 Distribution: "openSUSE Tumbleweed" DrKonqi: 5.27.4 [KCrashBackend] -- Information about the crash: Kontact stürzt bei Verwendung der Einstellungen ab. Beim Wechsel von der Übersicht zum Posteingang und Kalender friert es öfters ein und reagiert nicht mehr. Google Adressbuch lässt sich nicht integrieren. The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [KCrash Handler] #4 std::__atomic_base::load(std::memory_order) const (__m=std::memory_order_relaxed, this=Python Exception : Cannot access memory at address 0x100 #5 QAtomicOps::loadRelaxed(std::atomic const&) (_q_value=Python Exception : Cannot access memory at address 0x100 #6 QBasicAtomicInteger::loadRelaxed() const (this=Python Exception : Cannot access memory at address 0x100 #7 QtPrivate::RefCount::isShared() const (this=Python Exception : Cannot access memory at address 0x100 #8 QList::append(QWidget* const&) (this=0x100, t=@0x7ffc58acd350: 0x5569598626d0) at ../../include/QtCore/../../src/corelib/tools/qlist.h:622 #9 0x7f7c6fddd67c in QWidget::insertAction(QAction*, QAction*) (this=this@entry=0x5569598626d0, before=before@entry=0x0, action=0x5569548e1090) at kernel/qwidget.cpp:3138 #10 0x7f7c705bb763 in KXMLGUI::ActionList::plug(QWidget*, int) const (index=, container=0x5569598626d0, this=) at /usr/src/debug/kxmlgui-5.105.0/src/kxmlguifactory_p.cpp:33 #11 KXMLGUI::ContainerNode::plugActionList(KXMLGUI::BuildState&, QTypedArrayData::iterator const&) (mergingIdxIt=..., state=..., this=) at /usr/src/debug/kxmlgui-5.105.0/src/kxmlguifactory_p.cpp:209 #12 KXMLGUI::ContainerNode::plugActionList(KXMLGUI::BuildState&) (this=0x556959990190, state=...) at /usr/src/debug/kxmlgui-5.105.0/src/kxmlguifactory_p.cpp:181 #13 0x7f7c705bb82b in KXMLGUI::ContainerNode::plugActionList(KXMLGUI::BuildState&) (this=0x5569544dafc0, state=...) at /usr/src/debug/kxmlgui-5.105.0/src/kxmlguifactory_p.cpp:185 #14 0x7f7c705bb82b in KXMLGUI::ContainerNode::plugActionList(KXMLGUI::BuildState&) (this=0x5569544e09c0, state=...) at /usr/src/debug/kxmlgui-5.105.0/src/kxmlguifactory_p.cpp:185 #15 0x7f7c705c1831 in KXMLGUIFactory::plugActionList(KXMLGUIClient*, QString const&, QList const&) (this=0x556954680570, client=0x55695445bba0, name=, actionList=...) at /usr/src/debug/kxmlgui-5.105.0/src/kxmlguifactory.cpp:564 #16 0x7f7bfc0b4e23 in PimCommon::PluginInterface::initializePluginActions(QString const&, KXMLGUIClient*) (this=, prefix=..., guiClient=0x55695445bba0) at /usr/src/debug/pimcommon-22.12.3/src/pimcommonakonadi/genericplugins/plugininterface.cpp:154 #17 0x7f7bfcbf4f7e in KMMainWidget::initializePluginActions() (this=) at /usr/src/debug/kmail-22.12.3/src/kmmainwidget.cpp:4190 #18 0x7f7bfd464aa5 in KMailPart::guiActivateEvent(KParts::GUIActivateEvent*) (this=0x55695445bb70, e=) at /usr/src/debug/kmail-22.12.3/src/kmail_part.cpp:113 #19 0x7f7c6f118d2b in QObject::event(QEvent*) (this=0x55695445bb70, e=0x7ffc58acd8b0) at kernel/qobject.cpp:1369 #20 0x7f7c6fda52ce in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=, receiver=0x55695445bb70, e=0x7ffc58acd8b0) at kernel/qapplication.cpp:3640 #21 0x7f7c6f0ecb28 in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=0x55695445bb70, event=0x7ffc58acd8b0) at kernel/qcoreapplication.cpp:1064 #22 0x7f7c6fb81da1 in KParts::MainWindow::createGUI(KParts::Part*) (this=0x55695438ea00, part=0x55695445bb70) at /usr/src/debug/kparts-5.105.0/src/mainwindow.cpp:104 #23 0x7f7c706468ca in Kontact::MainWindow::selectPlugin(KontactInterface::Plugin*) (this=0x55695438ea00, plugin=) at /usr/src/debug/kontact-22.12.3/src/mainwindow.cpp:680 #24 0x7f7c6f1253a3 in doActivate(QObject*, int, void**) (sender=0x556954396530, signal_index=7, argv=0x7ffc58acdaf0) at kernel/qobject.cpp:3935 #25 0x7f7c6f11dfff in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=, m=m@entry=0x7f7c706684e0 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffc58acdaf0) at kernel/qobject.cpp:3983 #26 0x7f7c7064154f in Kontact::SidePaneBase::pluginSelected(KontactInterface::Plugin*) (this=, _t1=) at /usr/src/debug/kontact-22.12.3/build/src/kontactprivate_autogen/EWIEGA46WW/moc_sidepaneb
[ghostwriter] [Bug 467602] Text disappears when maximizing window (ghostwriter version 2.1.6)
https://bugs.kde.org/show_bug.cgi?id=467602 --- Comment #2 from David Roman --- I forgot to add the window resolution in case it helps: It's is a LG Electronics Ultrawide 2560x1080 -- You are receiving this mail because: You are watching all bug changes.
[ghostwriter] [Bug 467602] Text disappears when maximizing window (ghostwriter version 2.1.6)
https://bugs.kde.org/show_bug.cgi?id=467602 --- Comment #1 from David Roman --- Created attachment 157436 --> https://bugs.kde.org/attachment.cgi?id=157436&action=edit Ghostwriter before window is maximied -- You are receiving this mail because: You are watching all bug changes.
[ghostwriter] [Bug 467602] New: Text disappears when maximizing window (ghostwriter version 2.1.6)
https://bugs.kde.org/show_bug.cgi?id=467602 Bug ID: 467602 Summary: Text disappears when maximizing window (ghostwriter version 2.1.6) Classification: Applications Product: ghostwriter Version: unspecified Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: megan.con...@kdemail.net Reporter: me+kdebugs@kropotkin.rocks Target Milestone: --- Created attachment 157435 --> https://bugs.kde.org/attachment.cgi?id=157435&action=edit Ghostwriter in maximized window. Input text has disappeared When ghostwriter starts in a "small" window I can see the whole input text. It also is well scaled, but when the window is maximized the text disappears. Sometimes it doesn't disappear but the format is not scaled properly (see attach pictures). STEPS TO REPRODUCE 1. Opena markdown document with some text in a non-maximized window 2. Maximize the window OBSERVED RESULT Text disappears EXPECTED RESULT Text appears in the correct format SOFTWARE/OS VERSIONS Linux/KDE Plasma: Linux 6.2.6 KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.27.2 Qt Version: 5.15.8 Ghostwriter: 2.1.6 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kasts] [Bug 460859] Display issues on Android
https://bugs.kde.org/show_bug.cgi?id=460859 Roman Šmakal changed: What|Removed |Added Attachment #153122|0 |1 is obsolete|| --- Comment #5 from Roman Šmakal --- Created attachment 154588 --> https://bugs.kde.org/attachment.cgi?id=154588&action=edit 1:1 mode 1:1 mode still looking wierd, but I'm not sure if it's not too time consuming to make the bug worth fixing. Btw. for example my device is not actually 1:1 screen, it's resolution is 1430 x 1438. Maybe this parameter could be enough to use portrait displaying even in 1:1 mode (that's what most android apps do on my device) -- You are receiving this mail because: You are watching all bug changes.
[kasts] [Bug 460859] Display issues on Android
https://bugs.kde.org/show_bug.cgi?id=460859 Roman Šmakal changed: What|Removed |Added Attachment #153123|0 |1 is obsolete|| --- Comment #4 from Roman Šmakal --- Created attachment 154587 --> https://bugs.kde.org/attachment.cgi?id=154587&action=edit Portrait mode Portrait mode seems to be fixed -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 155541] Fix GaduGadu registration
https://bugs.kde.org/show_bug.cgi?id=155541 Roman S. changed: What|Removed |Added Attachment #115149|0 |1 is obsolete|| --- Comment #31 from Roman S. --- Created attachment 154274 --> https://bugs.kde.org/attachment.cgi?id=154274&action=edit Screenshot showing current (03.12.2022) registration -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 155541] Fix GaduGadu registration
https://bugs.kde.org/show_bug.cgi?id=155541 Roman S. changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #30 from Roman S. --- (In reply to Justin Zobel from comment #29) > Thank you for reporting this issue in KDE software. As it has been a while > since this issue was reported (...) Almost 15 years... :( It does not crash anymore (Kopete 22.08.3), but it doesn't work either. It seems the protocol provider has disabled registration via the communicator (it doesn't display a verification code to type in), you have to go to their web site to get the amount now. So "Fix GaduGadu registration" should now turn into "Remove obsolete non-working GaduGadu registration". -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 461299] elisa: irrtating stutters when playing audio
https://bugs.kde.org/show_bug.cgi?id=461299 --- Comment #9 from Roman Lebedev --- (In reply to Roman Lebedev from comment #8) > (In reply to Roman Lebedev from comment #7) > > (In reply to Nate Graham from comment #6) > > > Sounds like a libvlc issue, perhaps. > > > > You know what, why don't we just switch to libvlc backend? > > Err. Of course, i meant libmpv. https://invent.kde.org/multimedia/elisa/-/merge_requests/400 Testing welcomed. -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 461299] elisa: irrtating stutters when playing audio
https://bugs.kde.org/show_bug.cgi?id=461299 --- Comment #8 from Roman Lebedev --- (In reply to Roman Lebedev from comment #7) > (In reply to Nate Graham from comment #6) > > Sounds like a libvlc issue, perhaps. > > You know what, why don't we just switch to libvlc backend? Err. Of course, i meant libmpv. -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 461299] elisa: irrtating stutters when playing audio
https://bugs.kde.org/show_bug.cgi?id=461299 --- Comment #7 from Roman Lebedev --- (In reply to Nate Graham from comment #6) > Sounds like a libvlc issue, perhaps. You know what, why don't we just switch to libvlc backend? -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 461299] elisa: irrtating stutters when playing audio
https://bugs.kde.org/show_bug.cgi?id=461299 --- Comment #4 from Roman Lebedev --- (In reply to Aurélien COUDERC from comment #3) > I’ve added the patch to the Debian package on top of 22.08.3 but it doesn’t > solve the issue. It makes it less frequent but I still have occasional sound > cuts on an otherwise idle modern machine. > > I’ve not looked at the code but if the stutter is due to the playback > directly waiting for the data to load from the disk, the correct solution is > not to make the buffer bigger, it’s only going to make it less frequent. > Also loading complete files in memory is not the solution either. I have a > couple of albums that are a single FLAC file of a couple hundres of MBs and > it seems overkill to load these entirely into memory. > > If the issue is really the playback buffer becoming empty, the real fix > would be to ensure the prefetch is done in the background so the playback > never ends up waiting for the data to be there. > > > Thanks for looking into this ! I have not analysed *all* the remaining issues i heard, but at least some of them were artifacts in the audio itself. Are you sure that is not the case for you? -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 375014] konqueror Ctrl+cklick opens new tab but changes to it even if open in background is active
https://bugs.kde.org/show_bug.cgi?id=375014 --- Comment #4 from Roman Fietze --- Still true. Konqueror 5.0.97, opeSUSE repos. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 461891] New: Unable to disable media control shortcuts on lock screen
https://bugs.kde.org/show_bug.cgi?id=461891 Bug ID: 461891 Summary: Unable to disable media control shortcuts on lock screen Classification: Plasma Product: kscreenlocker Version: 5.25.5 Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: to.roma.from.kde...@qwertty.com Target Milestone: --- 1. Listen to an audio recording in a MPRIS-capable app 2. Ensure that Settings > Screen Locking > Appearance > Show > Media Controls is not checked 3. Lock the screen 4. Press the Play button on the keyboard 5. Observe that the audio starts playing I’ve noticed that this applies even to voice messages in a chat app in a browser (if plasma-browser-integration is installed), so privacy concerns are much more severe than strangers potentially figuring out your favorite music styles. Suggested resolution: 1. If media controls are hidden in settings, also disable the keyboard shortcuts 2. Alternatively, only enable the Pause and Volume Up/Down/Mute shortcuts, but not Play 3. Optionally, provide fine-grained settings for the above. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 461731] Error mlt_repository_init: failed
https://bugs.kde.org/show_bug.cgi?id=461731 Roman changed: What|Removed |Added CC||pos...@zohomail.eu --- Comment #4 from Roman --- I have the same issue using Ubuntu 22.10 where kdenlive has been installed with snap. Trying to install it with flatpak and AppImage failed as well. With flatpak errors occurred during working with videos and the AppImage executable couldn't be executed because fuse seems to be not recommended any more on Ubuntu... -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 388842] Silently stops receiving mail (agent not ready)
https://bugs.kde.org/show_bug.cgi?id=388842 --- Comment #2 from Roman Odaisky --- I have a systemd timer doing akonadictl restart, that mitigates the issue. For science purposes I’ve disabled the timer and let’s see what happens. Also recently KMail and Akonadi have started other unacceptable behaviors. Could you please help me as to the best way of reporting these? 1. There’s trouble sending messages, in akonadiconsole the Mail Dispatcher Agent is stuck at “Sending: 〈subject〉 (0%)” and nothing is sent, I can’t see useful logs anywhere. A single akonadictl restart isn’t even forcing the message through, I have to do it a bunch of times, or perhaps wait for something to time out, I’m not sure what exact actions cause the message to finally get sent. This seems to happen for a GMail transport but not for a non-GMail SMTP account. 2. At times, usually after waking up from suspend, KMail silently switches to offline mode and refuses to receive mail until I notice the fact and switch it back online. I would like to disable offline mode entirely as it’s harmful and I can’t see any use for it yet I don’t seem to have such an option. 3. The [^] button at the bottom of main KMail window that used to expand a popup listing what synchronization operations are taking place doesn’t do anything except change to [v] and [^] again. Which of these might be manifestations of the same issue and which should be filed as new bugs? -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 461299] elisa: irrtating stutters when playing audio
https://bugs.kde.org/show_bug.cgi?id=461299 --- Comment #1 from Roman Lebedev --- Posted minimal fix at https://invent.kde.org/multimedia/elisa/-/merge_requests/397 I don't know if this fully solves the problem for me, but if it does not, the next step would be forcing the kernel to prefetch the whole file... -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 461300] elisa: It would be nice to have integrated EBU R 128 loudness normalization ability
https://bugs.kde.org/show_bug.cgi?id=461300 --- Comment #2 from Roman Lebedev --- (In reply to Nate Graham from comment #1) > What's the difference between this and ReplayGain? I'm not sure what the question is. To reword my initial comment, i'm not interested in any solution, be it ReplayGain or R128, that requires me to modify the files themselves. Those two are essentially the same underlying algorithm i suppose, with R128 being more recent/modern, an official standard, and perhaps more accurate. I do believe R128 is taking over. -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 461300] elisa: It would be nice to have integrated EBU R 128 loudness normalization ability
https://bugs.kde.org/show_bug.cgi?id=461300 Roman Lebedev changed: What|Removed |Added CC||lebedev...@gmail.com, ||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 461299] elisa: irrtating stutters when playing audio
https://bugs.kde.org/show_bug.cgi?id=461299 Roman Lebedev changed: What|Removed |Added CC||lebedev...@gmail.com, ||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 461300] New: elisa: It would be nice to have integrated EBU R 128 loudness normalization ability
https://bugs.kde.org/show_bug.cgi?id=461300 Bug ID: 461300 Summary: elisa: It would be nice to have integrated EBU R 128 loudness normalization ability Classification: Applications Product: Elisa Version: 22.08.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: lebedev...@gmail.com Target Milestone: --- While one could of course do that offline, it would of course modify the source files, which is not always desired, because it obviously changes the hash of the file... Is this conceptually reasonable to have? -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 461299] New: elisa: irrtating stutters when playing audio
https://bugs.kde.org/show_bug.cgi?id=461299 Bug ID: 461299 Summary: elisa: irrtating stutters when playing audio Classification: Applications Product: Elisa Version: 22.08.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: lebedev...@gmail.com Target Milestone: --- Sometimes, when playing local audio files, regardless of system's load level, the audio playback momentairly stops and then resumes, it takes maybe less than 1s. This is happening on fully performance tuned Pipewire setup, and pwtop does not show any issues on pipewire side. I highly suspect elisa is simply running out of the input to play, and stutters when fetching next chunk from disk. Does elisa already have some kind of precaching system? Would it be acceptable to simply fully prefetch the whole file before playing, or is the filesize a concern? Something smarter, like ensuring that N next seconds are always avaliable could be nice, too. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 461174] New: Custom tab name should be independent of SSH
https://bugs.kde.org/show_bug.cgi?id=461174 Bug ID: 461174 Summary: Custom tab name should be independent of SSH Classification: Applications Product: konsole Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: tabbar Assignee: konsole-de...@kde.org Reporter: to.roma.from.kde...@qwertty.com Target Milestone: --- 1. In a couple of tabs, SSH to various servers 2. Rename the tabs using tab context menus or Ctrl+Alt+S 3. Observe that the tabs have the custom names and navigation is easy 4. Have SSH processes disconnect for whatever reason, maybe intermittent network failures 5. Observe that the tabs no longer have the custom names 6. Observe that it’s hard to go to a specific tab to restart its SSH command because they all look the same When I specify a custom name without any % substitutions, it should apply to the tab regardless of whether SSH is running in it. Perhaps there should be a third field, auto-focused upon entry, in the Tab Properties dialog, that, if populated, should be used in preference to tab title format entries. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460821] Allow manual displaying of keyboard
https://bugs.kde.org/show_bug.cgi?id=460821 --- Comment #2 from Roman Šmakal --- No, so far i am not aware of any. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 460963] neon-keyring is broken or not fully installed
https://bugs.kde.org/show_bug.cgi?id=460963 --- Comment #1 from roman.tel...@mail.com --- Neon-keyring problem occured after upgading to LTS 22.04 ‘Jammy Jellyfish’. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 460963] New: neon-keyring is broken or not fully installed
https://bugs.kde.org/show_bug.cgi?id=460963 Bug ID: 460963 Summary: neon-keyring is broken or not fully installed Classification: I don't know Product: kde Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: grave Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: roman.tel...@mail.com Target Milestone: --- After upgrading from Focal to 22.04 cannot install any updates. See: "Package failed to install: Error while installing package: installed neon-keyring package post-installation script subprocess returned error exit status 1." "/dpkg-reconfigure: neon-keyring is broken or not fully installed." -- You are receiving this mail because: You are watching all bug changes.
[libkgapi] [Bug 439285] Bad request, Google replied "Contacts API is being deprecated"
https://bugs.kde.org/show_bug.cgi?id=439285 Roman Šmakal changed: What|Removed |Added CC||schmakeri...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 420068] kde connect as phone backup tool
https://bugs.kde.org/show_bug.cgi?id=420068 Roman Šmakal changed: What|Removed |Added CC||schmakeri...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kasts] [Bug 460859] Display issues on Android
https://bugs.kde.org/show_bug.cgi?id=460859 --- Comment #1 from Roman Šmakal --- Created attachment 153123 --> https://bugs.kde.org/attachment.cgi?id=153123&action=edit Portrait mode -- You are receiving this mail because: You are watching all bug changes.
[kasts] [Bug 460859] New: Display issues on Android
https://bugs.kde.org/show_bug.cgi?id=460859 Bug ID: 460859 Summary: Display issues on Android Classification: Applications Product: kasts Version: unspecified Platform: Android OS: Android 10.x Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: b...@mogwai.be Reporter: schmakeri...@gmail.com Target Milestone: --- Created attachment 153122 --> https://bugs.kde.org/attachment.cgi?id=153122&action=edit 1:1 mode There are issues with displaying on Android. First i thought it's problem with unusual aspect ratio of my phone (1:1), but even after switching to portrait mode, issue persists. Screenshots attached Unihertz Titan - Android 10 App source: F-droid -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460724] Do not rely on automatic display of keyboard
https://bugs.kde.org/show_bug.cgi?id=460724 --- Comment #4 from Roman Šmakal --- (In reply to Nate Graham from comment #3) > > At this moment i'm always able to get virtual keyboard somehow, but it's > > inconsistent and UX (at least for me) could be much better. > I agree. Let's focus on making that better. Can you file individual bug > reports for your three use cases described below? We'll tackle them > individually. Thanks! Done https://bugs.kde.org/show_bug.cgi?id=460821 https://bugs.kde.org/show_bug.cgi?id=460822 https://bugs.kde.org/show_bug.cgi?id=460823 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460823] New: Switch for automatic / manual keyboard displaying
https://bugs.kde.org/show_bug.cgi?id=460823 Bug ID: 460823 Summary: Switch for automatic / manual keyboard displaying Classification: Plasma Product: kwin Version: 5.26.0 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: virtual-keyboard Assignee: kwin-bugs-n...@kde.org Reporter: schmakeri...@gmail.com Target Milestone: --- I think keyboard widget should have switch for (not) autoshowing keyboard for touchscreen although i have to be able to open keyboard manually - maybe change funcionality from virtual keyboard on/off to show/hide keyboard or automatic/manual display? Use case - laptop with attached keyboard + touchscreen - when i touch field in any app, i get half of display covered with keyboard, that i actually don't need. Keyboard could be broken though, so there should remain a way to show it manually -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460822] New: Allow disabling automatic display of virtual keyboard on touchscreen devices
https://bugs.kde.org/show_bug.cgi?id=460822 Bug ID: 460822 Summary: Allow disabling automatic display of virtual keyboard on touchscreen devices Classification: Plasma Product: kwin Version: 5.26.0 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: virtual-keyboard Assignee: kwin-bugs-n...@kde.org Reporter: schmakeri...@gmail.com Target Milestone: --- In tablet mode (touchscreen device without keyboard) it would be good to have switch between automatic/manual showing of keyboard. Swipe gesture could work well for showing in manual mode. Use case - tablet with touchscreen only - while browsing i might accidentally press input field - this means virtual keyboard is being shown and this behavior can be annoying -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460821] New: Allow manual displaying of keyboard
https://bugs.kde.org/show_bug.cgi?id=460821 Bug ID: 460821 Summary: Allow manual displaying of keyboard Classification: Plasma Product: kwin Version: 5.26.0 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: virtual-keyboard Assignee: kwin-bugs-n...@kde.org Reporter: schmakeri...@gmail.com Target Milestone: --- If everything works as expected then keyboard shows when pressing input field. Problem is, when input field is selected and keyboard does not get shown or i . There is no way to bring it up for typing (neither swipe gesture or clicking on widget). Use case - touchscreen with (for some reason) problematic app - Firefox at this moment (https://bugs.kde.org/show_bug.cgi?id=460537) - i do not get keyboard automatically when input field is pressed and i do not have way to show the keyboard -- You are receiving this mail because: You are watching all bug changes.
[kasts] [Bug 460727] Sync between apps
https://bugs.kde.org/show_bug.cgi?id=460727 --- Comment #4 from Roman Šmakal --- Thanks for tips, managed to make online sync to work somehow (relogin on both devices fixed it). Thanks. If you are not interested in implementing the kdeconnect way, then i guess bug report can be closed -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460724] Do not rely on automatic display of keyboard
https://bugs.kde.org/show_bug.cgi?id=460724 --- Comment #2 from Roman Šmakal --- I am on 5.26 and if there is *manual* way to open it, i did not found it. Automatic works (except for mentioned Firefox time after time), but when you use widget to hide the keyboard, there is no way to open it back. Other case is if the automatic do NOT work, then widget allows me to manually show the keyboard as expected. At this moment i'm always able to get virtual keyboard somehow, but it's inconsistent and UX (at least for me) could be much better. For time saving i may try to clarify use cases: Use case 1 - attached keyboard + touchscreen - when i touch field in any app, i get half of display covered with keyboard, that i actually don't need (and if wanted, i could bring it up) Use case 2 - touchscreen - while browsing i might accidentally press input field - this means virtual keyboard is being shown and this behavior can be annoying Use case 3 - touchscreen with (for some reason) problematic app - Firefox at this moment - i do not get keyboard automatically when input field is pressed and i do not have way to show the keyboard -- You are receiving this mail because: You are watching all bug changes.
[kasts] [Bug 460727] Sync between apps
https://bugs.kde.org/show_bug.cgi?id=460727 --- Comment #2 from Roman Šmakal --- It seems it would, but it does not sync anything for me (may be issue only on my side, had no time to find out). I'd still preffer offline variant with kdeconnect though anyway. But i guess GPodder API makes my FR invalid, so feel free to close it :) -- You are receiving this mail because: You are watching all bug changes.
[kasts] [Bug 460727] New: Sync between apps
https://bugs.kde.org/show_bug.cgi?id=460727 Bug ID: 460727 Summary: Sync between apps Classification: Applications Product: kasts Version: unspecified Platform: Archlinux OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: b...@mogwai.be Reporter: schmakeri...@gmail.com Target Milestone: --- It would be great to sync subscriptions, queue and play positions between devices. Maybe using KDEconnect could be a way? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460724] New: Do not rely on automatic display of keyboard
https://bugs.kde.org/show_bug.cgi?id=460724 Bug ID: 460724 Summary: Do not rely on automatic display of keyboard Classification: Plasma Product: kwin Version: 5.26.0 Platform: Archlinux OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: virtual-keyboard Assignee: kwin-bugs-n...@kde.org Reporter: schmakeri...@gmail.com Target Milestone: --- SUMMARY So far (at least for 5.26) Plasma seems to rely on automatic displaying of virtual keyboard. From my point of view there should be more options for keyboard displaying (it would also make workaround for incorrect behavior like this: https://bugs.kde.org/show_bug.cgi?id=460537 ), at least for my detachable convertible use-case. ADDITIONAL INFORMATION >From my point of view there are use cases i would not want to show keyboard or display it on demand from applet and maybe using swipe gesture (Gnome-like behavior). REQUESTS SUMMARY Virtual keyboard KCM + Always show (can't find use case, but i guess someone might) + Auto show + Show on user request (with icon or swipe gesture) Virtual keyboard widget + Show keyboard + Hide keyboard + Disable keyboard + Enable auto-showing switch Plasma behavior KCM - Touchscreen + Add "Show virtual keyboard" -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 390705] Show virtual keyboard on touch devices
https://bugs.kde.org/show_bug.cgi?id=390705 --- Comment #2 from Roman Šmakal --- I'd say this bug is fixed with https://bugs.kde.org/show_bug.cgi?id=439911 -- You are receiving this mail because: You are watching all bug changes.
[kasts] [Bug 438864] Add streaming feature
https://bugs.kde.org/show_bug.cgi?id=438864 Roman Šmakal changed: What|Removed |Added CC||schmakeri...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 447936] X11: turning the monitor off/on, causes the panel to disappear
https://bugs.kde.org/show_bug.cgi?id=447936 Roman changed: What|Removed |Added CC||ro...@romanlenegrate.net -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 458096] Plasmashell restricted (variables) environment
https://bugs.kde.org/show_bug.cgi?id=458096 Roman changed: What|Removed |Added CC||avistor...@gmail.com --- Comment #10 from Roman --- Can confirm same thing happens on Manjaro(5.25.4). -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kquickcharts] [Bug 457248] System monitor pie chart scaling error with non-zero manual data range
https://bugs.kde.org/show_bug.cgi?id=457248 --- Comment #9 from Roman Lebedev --- https://invent.kde.org/frameworks/kquickcharts/-/merge_requests/46 I haven't touched multi-item source handling, i don't really understand how it's supposed to behave, and i think it might not be handled correctly. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kquickcharts] [Bug 457248] System monitor pie charts is broken
https://bugs.kde.org/show_bug.cgi?id=457248 Roman Lebedev changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #7 from Roman Lebedev --- (In reply to Arjen Hiemstra from comment #2) > (In reply to Roman Lebedev from comment #0) > > 1. The coordinate system is wrong. Somehow "Start from angle = -180*" > > results in starting from six-o-clock, which is -90* in reality: > > https://upload.wikimedia.org/wikipedia/commons/9/9a/Degree-Radian_Conversion. > > svg > > Starting angle is arbitrary and there's no standard. In the case of the > Quick Charts library, it follows what other chart libraries do: 0 is at the > top, so -180 degrees is at the bottom. > > > 2. There is some weird normalization bug. Even when the underlying data > > reaches the specified data range max, the pie chart is still far from being > > full. > > Please show a code sample where this happens. If you're using automatic > maximum, the data source may be providing a different maximum than what you > expect. I'm using pie chart in system monitor sensor, measuring cpu temperature. Uploaded screenshots, let me know if that is not sufficient.. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kquickcharts] [Bug 457248] System monitor pie charts is broken
https://bugs.kde.org/show_bug.cgi?id=457248 --- Comment #6 from Roman Lebedev --- Created attachment 150974 --> https://bugs.kde.org/attachment.cgi?id=150974&action=edit chart under load -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kquickcharts] [Bug 457248] System monitor pie charts is broken
https://bugs.kde.org/show_bug.cgi?id=457248 --- Comment #5 from Roman Lebedev --- Created attachment 150973 --> https://bugs.kde.org/attachment.cgi?id=150973&action=edit idle chart -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kquickcharts] [Bug 457248] System monitor pie charts is broken
https://bugs.kde.org/show_bug.cgi?id=457248 --- Comment #4 from Roman Lebedev --- Created attachment 150972 --> https://bugs.kde.org/attachment.cgi?id=150972&action=edit sensors on system monitor -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kquickcharts] [Bug 457248] System monitor pie charts is broken
https://bugs.kde.org/show_bug.cgi?id=457248 --- Comment #3 from Roman Lebedev --- Created attachment 150971 --> https://bugs.kde.org/attachment.cgi?id=150971&action=edit pie chart settings in system monitor -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kquickcharts] [Bug 457248] New: System monitor pie charts is broken
https://bugs.kde.org/show_bug.cgi?id=457248 Bug ID: 457248 Summary: System monitor pie charts is broken Product: frameworks-kquickcharts Version: 5.94.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ahiems...@heimr.nl Reporter: lebedev...@gmail.com CC: kdelibs-b...@kde.org Target Milestone: --- 1. The coordinate system is wrong. Somehow "Start from angle = -180*" results in starting from six-o-clock, which is -90* in reality: https://upload.wikimedia.org/wikipedia/commons/9/9a/Degree-Radian_Conversion.svg 2. There is some weird normalization bug. Even when the underlying data reaches the specified data range max, the pie chart is still far from being full. -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 446475] File Download Order functionality has vanished
https://bugs.kde.org/show_bug.cgi?id=446475 Roman Lebedev changed: What|Removed |Added Version|21.11.90|21.12.3 CC||lebedev...@gmail.com --- Comment #2 from Roman Lebedev --- Same. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456163] New: KWin error on resume from suspend after Lock screen error
https://bugs.kde.org/show_bug.cgi?id=456163 Bug ID: 456163 Summary: KWin error on resume from suspend after Lock screen error Product: plasmashell Version: 5.24.5 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: nightcity...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Application: plasmashell (5.24.5) Qt Version: 5.15.5 Frameworks Version: 5.95.0 Operating System: Linux 5.18.0-1-rt11-MANJARO x86_64 Windowing System: X11 Distribution: Manjaro Linux DrKonqi: 5.24.5 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: -- resume from suspend - immediately got black screen with "Lock screen is broken" error -- swiched to TTY (ctrl+al+F2) and unlocked session 2 -- returned back to TTY1 - Unusual behavior I noticed: -- system settings UI has orange circle marks for different menu items -- "QDBusConnection: error: could not send signal to service" appears even after reinstalling qt and plasma packages - Custom settings of the application: current theme: "breath-light" (same issue on "breeze" theme). Reinstalling plasma5-themes-breath and sddm-breath-theme did not help. The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Aborted [KCrash Handler] #4 0x7f509cc06117 in () at /usr/lib/libc.so.6 #5 0x7f509cc08920 in pthread_cond_wait () at /usr/lib/libc.so.6 #6 0x7f509d0ab7d4 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #7 0x7f509eafd950 in () at /usr/lib/libQt5Quick.so.5 #8 0x7f509eafe6c1 in () at /usr/lib/libQt5Quick.so.5 #9 0x7f509d637707 in QWindow::event(QEvent*) () at /usr/lib/libQt5Gui.so.5 #10 0x7f509dea2abc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #11 0x7f509d24cf38 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #12 0x7f509d62a4d4 in QGuiApplicationPrivate::processExposeEvent(QWindowSystemInterfacePrivate::ExposeEvent*) () at /usr/lib/libQt5Gui.so.5 #13 0x7f509d60c9c5 in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () at /usr/lib/libQt5Gui.so.5 #14 0x7f5097c81ce0 in () at /usr/lib/libQt5XcbQpa.so.5 #15 0x7f509b624c6b in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0 #16 0x7f509b67b001 in () at /usr/lib/libglib-2.0.so.0 #17 0x7f509b622392 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #18 0x7f509d29764c in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #19 0x7f509d2456ec in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #20 0x7f509d2501e9 in QCoreApplication::exec() () at /usr/lib/libQt5Core.so.5 #21 0x55def0df1dc2 in () #22 0x7f509cba6290 in () at /usr/lib/libc.so.6 #23 0x7f509cba634a in __libc_start_main () at /usr/lib/libc.so.6 #24 0x55def0df2195 in () [Inferior 1 (process 1227) detached] Possible duplicates by query: bug 456151, bug 456062, bug 455869, bug 455543, bug 455505. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 420895] Files view rooted at $HOME; cannot be used to browse alternative locations
https://bugs.kde.org/show_bug.cgi?id=420895 --- Comment #16 from Roman Lebedev --- I've posted https://invent.kde.org/multimedia/elisa/-/merge_requests/360 I don't know if there is some nicer solution that is planned, but at least this makes elisa usable for me :) -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 420895] Files view rooted at $HOME; cannot be used to browse alternative locations
https://bugs.kde.org/show_bug.cgi?id=420895 Roman Lebedev changed: What|Removed |Added Version|19.12.3 |21.08.3 CC||lebedev...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 453954] New: Open Collaboration Service (0).
https://bugs.kde.org/show_bug.cgi?id=453954 Bug ID: 453954 Summary: Open Collaboration Service (0). Product: systemsettings Version: 5.24.4 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: kcm_cursortheme Assignee: plasma-b...@kde.org Reporter: roman.samokhval...@yandex.ru Target Milestone: --- Created attachment 148933 --> https://bugs.kde.org/attachment.cgi?id=148933&action=edit screenshot of the error itself 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. open system settings 2. open the appearance tab 3. now any tab from the design of the working environment, including its 4. now click upload design OBSERVED RESULT Неизвестная ошибка Open Collaboration Service (0). EXPECTED RESULT The ability to install the design SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: kubuntu 22.04 (available in About System) KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION I switched to kubuntu of the manjaro kde plasma 5 distribution in the hope of feeling the full power of ubuntu with kde design, well, I can't do it so there is no way to do the design -- You are receiving this mail because: You are watching all bug changes.
