[kio-extras] [Bug 487265] KIO-Extras AFC URL error
https://bugs.kde.org/show_bug.cgi?id=487265 Vladimir changed: What|Removed |Added CC||dv...@yandex.ru -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 487265] KIO-Extras AFC URL error
https://bugs.kde.org/show_bug.cgi?id=487265 --- Comment #1 from Vladimir --- Created attachment 169641 --> https://bugs.kde.org/attachment.cgi?id=169641=edit Mounting -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 487265] New: KIO-Extras AFC URL error
https://bugs.kde.org/show_bug.cgi?id=487265 Bug ID: 487265 Summary: KIO-Extras AFC URL error Classification: Frameworks and Libraries Product: kio-extras Version: unspecified Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: AFC Assignee: plasma-b...@kde.org Reporter: dv...@yandex.ru CC: k...@privat.broulik.de Target Milestone: --- Created attachment 169640 --> https://bugs.kde.org/attachment.cgi?id=169640=edit The error SUMMARY An Error when mounting Iphone 5s file system STEPS TO REPRODUCE 1. Connect iPhone with an ' in the iPhone name (e.g. JT's iPhone) 2. Dolphin will report the device UUID does not exist. OBSERVED RESULT see attachment file EXPECTED RESULT File system of iPhone should appear. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 6.0.4 KDE Frameworks Version: 5.115.0 Qt Version: 5.15.13 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 486510] New: Kmail does not sand e-mails
https://bugs.kde.org/show_bug.cgi?id=486510 Bug ID: 486510 Summary: Kmail does not sand e-mails Classification: Applications Product: kontact Version: 6.0.2 Platform: Other OS: Linux Status: REPORTED Severity: major Priority: NOR Component: mail Assignee: kdepim-b...@kde.org Reporter: galantan2...@yandex.ru Target Milestone: --- Kmail does not sand e-mails STEPS TO REPRODUCE 1. Write new e-mail 2. Click sent. OBSERVED RESULT I got message "The mail dispatcher is offline, so mails cannot be sent. Do you want to make it online?" After click "set online" message goes to outbox. If i try send queued message i always got same error: "The mail dispatcher is offline, so mails cannot be sent. Do you want to make it online?" In akonadiconsile i see mail dispatcher in status offline. I tried to swith it online\restart\abort. Nothing happens. No errors. EXPECTED RESULT Message sent SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 40 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 486362] New: Discover crashes when opening
https://bugs.kde.org/show_bug.cgi?id=486362 Bug ID: 486362 Summary: Discover crashes when opening Classification: Applications Product: Discover Version: 5.27.5 Platform: Debian stable OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: v24909...@gmail.com CC: aleix...@kde.org Target Milestone: --- Application: plasma-discover (5.27.5) Qt Version: 5.15.8 Frameworks Version: 5.103.0 Operating System: Linux 6.1.0-20-amd64 x86_64 Windowing System: Wayland Distribution: Debian GNU/Linux 12 (bookworm) DrKonqi: 5.27.5 [KCrashBackend] -- Information about the crash: Hello! When I try to open "Discover" I get an application crash, the program quits unexpectedly, immediately after the initial loading has completed. This happens every time when I try to open it. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Центр программ Discover (plasma-discover), signal: Segmentation fault [KCrash Handler] #4 0x7f5b568e8a3d in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f5b58b143b2 in ResultsStream::resourcesFound(QVector const&) () from /usr/lib/x86_64-linux-gnu/plasma-discover/libDiscoverCommon.so #6 0x7f5b467434d0 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/discover/packagekit-backend.so #7 0x7f5b4673d588 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/discover/packagekit-backend.so #8 0x7f5b568dd6f0 in QObject::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f5b58362fae in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #10 0x7f5b568b16f8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7f5b568b4681 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7f5b5690a153 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7f5b5511e7a9 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #14 0x7f5b5511ea38 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #15 0x7f5b5511eacc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #16 0x7f5b56909836 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #17 0x7f5b568b017b in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #18 0x7f5b568b82d6 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #19 0x5652932f52a7 in ?? () #20 0x7f5b5644624a in __libc_start_call_main (main=main@entry=0x5652932f49b0, argc=argc@entry=1, argv=argv@entry=0x7ffc5f880a58) at ../sysdeps/nptl/libc_start_call_main.h:58 #21 0x7f5b56446305 in __libc_start_main_impl (main=0x5652932f49b0, argc=1, argv=0x7ffc5f880a58, init=, fini=, rtld_fini=, stack_end=0x7ffc5f880a48) at ../csu/libc-start.c:360 #22 0x5652932f5811 in ?? () [Inferior 1 (process 16052) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[plasma-integration] [Bug 484405] Application closes when deleting QSystemTrayIcon in Linux Plasma 6
https://bugs.kde.org/show_bug.cgi?id=484405 --- Comment #7 from Vladimir Golovnev --- I believe that the "platform theme" should be considered exactly as an extension of the Qt implementation. Therefore, it is completely unacceptable for it to make Qt's behavior so incorrect and unpredictable. The application should base its logic only on the Qt interface. And it is certainly not declared by its interface that the application can terminate when some dialog or system tray icon is closed. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 484729] Reply to HTML mail using same visual style hangs Kmail
https://bugs.kde.org/show_bug.cgi?id=484729 Vladimir changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #2 from Vladimir --- (In reply to shivarryn from comment #1) > Another victim of bug 482367 most probably. > Should be fixed in Qt 6.6.3. Can confirm it is fixed in Qt 6.6.3. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 484729] New: Reply to HTML mail using same visual style hangs Kmail
https://bugs.kde.org/show_bug.cgi?id=484729
Bug ID: 484729
Summary: Reply to HTML mail using same visual style hangs Kmail
Classification: Applications
Product: kmail2
Version: 6.0.1
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: composer
Assignee: kdepim-b...@kde.org
Reporter: vladi...@kanazir.com
Target Milestone: ---
SUMMARY
If the "Reply or forward using the same visual format as the original message
(plain text or HTML)" option is selected, the Kmail will hang while replying to
HTML mail. It will also raise the CPU load to 100%.
STEPS TO REPRODUCE
1. go to settings, composer and select the option, click Apply / OK
2. select HTML mail
3. press R or A
OBSERVED RESULT
CPU load jumps to 100%, the composer window is not opened, and Kmail stops
responding.
EXPECTED RESULT
Composer window to open.
SOFTWARE/OS VERSIONS
Operating System: Artix Linux x86_64
KDE Plasma Version: 6.0.2
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2
Kernel Version: 6.8.1-artix1-1 (64-bit)
Graphics Platform: Wayland
Processors: 24 × AMD Ryzen 9 5900X 12-Core Processor
Memory: 62,7 GiB of RAM
Graphics Processor: AMD Radeon RX 6700 XT
ADDITIONAL INFORMATION
The last strace entries:
openat(AT_FDCWD, "/usr/lib/aspell-0.60/en-wo_accents-only.rws", O_RDONLY) = 115
fstat(115, {st_mode=S_IFREG|0644, st_size=176080, ...}) = 0
read(115, "aspell default speller rowl 1.10"..., 4096) = 4096
newfstatat(AT_FDCWD, "/usr/lib/aspell-0.60/en-wo_accents-only.rws",
{st_mode=S_IFREG|0644, st_size=176080, ...}, 0) = 0
close(115) = 0
read(114, "", 4096) = 0
close(114) = 0
close(113) = 0
read(111, "", 4096) = 0
close(111) = 0
close(24) = 0
newfstatat(AT_FDCWD, "/home/canny/.aspell.en.pws", 0x7ffed824d640, 0) = -1
ENOENT (No such file or directory)
access("/home/canny/.aspell.en.pws", F_OK) = -1 ENOENT (No such file or
directory)
openat(AT_FDCWD, "/home/canny/.aspell.en.per", O_RDONLY) = -1 ENOENT (No such
file or directory)
newfstatat(AT_FDCWD, "/home/canny/.aspell.en.prepl", 0x7ffed824d640, 0) = -1
ENOENT (No such file or directory)
access("/home/canny/.aspell.en.prepl", F_OK) = -1 ENOENT (No such file or
directory)
openat(AT_FDCWD, "/home/canny/.aspell.en.rpl", O_RDONLY) = -1 ENOENT (No such
file or directory)
access("cid:image001.png@01DA81C0.33A3AEC0", F_OK) = -1 ENOENT (No such file or
directory)
newfstatat(AT_FDCWD, "/etc/localtime", {st_mode=S_IFREG|0644, st_size=1920,
...}, 0) = 0
newfstatat(AT_FDCWD, "/etc/localtime", {st_mode=S_IFREG|0644, st_size=1920,
...}, 0) = 0
openat(AT_FDCWD, "/usr/local/share/fonts/WindowsFonts/calibri.ttf", O_RDONLY) =
24
fcntl(24, F_SETFD, FD_CLOEXEC) = 0
fstat(24, {st_mode=S_IFREG|0644, st_size=1648120, ...}) = 0
mmap(NULL, 1648120, PROT_READ, MAP_PRIVATE, 24, 0) = 0x74bce7e6d000
close(24) = 0
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
brk(0x6435fc91b000) = 0x6435fc91b000
brk(0x6435fcd1b000) = 0x6435fcd1b000
brk(0x6435fd31b000) = 0x6435fd31b000
mmap(NULL, 16781312, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x74bc7ae0
mremap(0x74bc7ae0, 16781312, 33558528, MREMAP_MAYMOVE) = 0x74bc78c0
mremap(0x74bc78c0, 33558528, 67112960, MREMAP_MAYMOVE) = 0x74bb9fe0
mremap(0x74bb9fe0, 67112960, 134217728, MREMAP_MAYMOVE) = 0x74bb97e0
mremap(0x74bb97e0, 134217728, 268439552, MREMAP_MAYMOVE) = 0x74bb87c0
mremap(0x74bb87c0, 268439552, 536875008, MREMAP_MAYMOVE) = 0x74bb67a0
mremap(0x74bb67a0, 536875008, 1073741824, MREMAP_MAYMOVE) = 0x74bb27a0
mremap(0x74bb27a0, 1073741824, 2147487744, MREMAP_MAYMOVE) = 0x74baa780
mremap(0x74baa780, 2147487744, 4294967296, MREMAP_MAYMOVE) = 0x74b9a780
mremap(0x74b9a780, 4294967296, 8589934592, MREMAP_MAYMOVE) = 0x74b7a780
mremap(0x74b7a780, 8589934592, 17179873280, MREMAP_MAYMOVE) =
0x74b3a760
mremap(0x74b3a760, 17179873280, 34359742464, MREMAP_MAYMOVE) =
0x74aba740
mremap(0x74aba740, 34359742464, 68719480832, MREMAP_MAYMOVE) =
0x749ba720
+++ killed by SIGKILL +++
--
You are receiving this mail because:
You are watching all bug changes.
[plasma-integration] [Bug 484405] Application closes when deleting QSystemTrayIcon in Linux Plasma 6
https://bugs.kde.org/show_bug.cgi?id=484405 --- Comment #3 from Vladimir Golovnev --- I think I figured it out. Previously, `QCoreApplication::setQuitLockEnabled(false)` was implicitly set by `QGuiApplication::setQuitOnLastWindowClosed(false)`. I wonder if this was mentioned somewhere in the documentation? I didn't find it. Anyway, I don't think it's a good idea to use something like `QEventLoopLocker` at "platform theme" level. -- You are receiving this mail because: You are watching all bug changes.
[plasma-integration] [Bug 484405] Application closes when deleting QSystemTrayIcon in Linux Plasma 6
https://bugs.kde.org/show_bug.cgi?id=484405 --- Comment #2 from Vladimir Golovnev --- >Because of a behavior change in Qt6 the application needs to set >QCoreApplication::setQuitLockEnabled(false) Could you please specify in more detail what exactly has been changed in Qt? Is QEventLoopLocker intended to quit the application if there are open windows? -- You are receiving this mail because: You are watching all bug changes.
[plasma-integration] [Bug 484405] New: Application closes when deleting QSystemTrayIcon in Linux Plasma 6
https://bugs.kde.org/show_bug.cgi?id=484405 Bug ID: 484405 Summary: Application closes when deleting QSystemTrayIcon in Linux Plasma 6 Classification: Plasma Product: plasma-integration Version: unspecified Platform: unspecified OS: Other Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: glas...@yandex.ru Target Milestone: --- SUMMARY Application closes when deleting QSystemTrayIcon in Linux Plasma 6 STEPS TO REPRODUCE 1. Create and show QSystemTrayIcon instance 2. delete QSystemTrayIcon instance (e.g. when disabled in app settings) OBSERVED RESULT app closes itself EXPECTED RESULT app continue working w/o system tray icon SOFTWARE/OS VERSIONS KDE Plasma Version: 6.0.2 Qt Version: 6.6.2 ADDITIONAL INFORMATION App works as expected when run w/o KDEPlasmaPlatformTheme6.so loaded. Ref.: https://github.com/qbittorrent/qBittorrent/issues/20604 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 475255] Selecting a power profile through the battery & Brightness applet doesn't work correctly; works using `powerprofilesctl`
https://bugs.kde.org/show_bug.cgi?id=475255 --- Comment #12 from Vladimir Yerilov --- According to my observations the slider jumps back to the previous state (not only left), which was set during the start of Plasma. No matter what that state was. Profiles switching works, it's only slider acts weird until plasmashell is restarted. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 475255] Selecting a power profile through the battery & Brightness applet doesn't work correctly; works using `powerprofilesctl`
https://bugs.kde.org/show_bug.cgi?id=475255 --- Comment #7 from Vladimir Yerilov --- Can confirm. I used to have it on Intel i7 8550u laptop with Plasma 5 and hoped it would be eliminated in Plasma 6, but it's still present, and even on another machine with Ryzen 7840H. However it didn't manifest itself right after the fresh install of Manjaro which I am using on both machines, but a couple of weeks later I started to see it again. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 475255] Selecting a power profile through the battery & Brightness applet doesn't work correctly; works using `powerprofilesctl`
https://bugs.kde.org/show_bug.cgi?id=475255 Vladimir Yerilov changed: What|Removed |Added CC||openmind...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482693] ShowDesktopGrid shortcut is not working
https://bugs.kde.org/show_bug.cgi?id=482693
--- Comment #3 from Vladimir ---
I believe, in plasma 6 the command similar to ShowGridView is called "Overview"
("Toggle Overview" in shortcuts settings) and can be invoked with `dbus
org.kde.kglobalaccel /component/kwin invokeShortcut Overview`. But still don't
understand why ShowGridView is still present in the shortcuts list.
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 482693] ShowDesktopGrid shortcut is not working
https://bugs.kde.org/show_bug.cgi?id=482693 --- Comment #2 from Vladimir --- (In reply to Vlad Zahorodnii from comment #1) > There's no ShowDesktopGrid shortcut anymore. But it is in the list of supported commands, checked with `qdbus org.kde.kglobalaccel /component/kwin org.kde.kglobalaccel.Component.shortcutNames | grep ShowDesktopGrid`, and I also see in System Settings/Keyboard/Shortcuts/Kwin > You're probably looking for > "Grid View" If you mean "Toggle grid view" shortcut, it does work, but this command produces a different visual effect compared to "Show grid desktop". "Toggle grid view" shows all virtual desktops and their windows, while "Show grid desktop" shows only the current desktop, and the command itself works, I can trigger it by a screen edge gesture. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482693] New: ShowDesktopGrid shortcut is not working
https://bugs.kde.org/show_bug.cgi?id=482693 Bug ID: 482693 Summary: ShowDesktopGrid shortcut is not working Classification: Plasma Product: kwin Version: 6.0.1 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-desktop-grid Assignee: kwin-bugs-n...@kde.org Reporter: vpkopy...@gmail.com Target Milestone: --- SUMMARY *** I use `qdbus org.kde.kglobalaccel /component/kwin invokeShortcut ShowDesktopGrid` command in my touchegg configuration, it stopped working after upgrading to plasma 6.0.1. Manually invoking the command or using a keyboard shortcut (Meta + F8) also gives no effect. However I can can trigger the desktop grid with a screen edge gesture. I also can successfully invoke other commands with invokeShortcut, for example "Show Desktop" *** STEPS TO REPRODUCE 1. Invoke `qdbus org.kde.kglobalaccel /component/kwin invokeShortcut ShowDesktopGrid` in command line or press Meta+F8 OBSERVED RESULT Nothing happens EXPECTED RESULT Desktop grid is shown SOFTWARE/OS VERSIONS Linux: Arch linux (6.7.8-arch1-1) KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 -- You are receiving this mail because: You are watching all bug changes.
[kde-cli-tools] [Bug 429408] kde-open5 changes case of argument
https://bugs.kde.org/show_bug.cgi?id=429408 Vladimir Tennov changed: What|Removed |Added CC||tennov+...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kxmlgui] [Bug 424126] Standardized feature to display a hamburger menu in the tool bar when the menu bar is hidden, like Dolphin does
https://bugs.kde.org/show_bug.cgi?id=424126 Vladimir Yerilov changed: What|Removed |Added CC||openmind...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 460967] Dolphin no longer runs executables and is no longer showing menu bar
https://bugs.kde.org/show_bug.cgi?id=460967 Vladimir Yerilov changed: What|Removed |Added CC||openmind...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kxmlgui] [Bug 466107] Make it clear how you can re-enable the menu bar and the toolbar when both are hidden
https://bugs.kde.org/show_bug.cgi?id=466107 Vladimir Yerilov changed: What|Removed |Added CC||openmind...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 479094] kwin wayland randomly freezes completely when opening task switcher / alt tab
https://bugs.kde.org/show_bug.cgi?id=479094 Vladimir Solomatin changed: What|Removed |Added CC||proge...@yandex.ru -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 476154] KDE Connect crashed after disconnecting bluetooth device
https://bugs.kde.org/show_bug.cgi?id=476154 Vladimir Hodakov changed: What|Removed |Added CC||vladi...@hodakov.me -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 399885] Support indexing NTFS disks
https://bugs.kde.org/show_bug.cgi?id=399885 Vladimir Yerilov changed: What|Removed |Added CC||openmind...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 457746] Deleted audio file not removed from index as expected
https://bugs.kde.org/show_bug.cgi?id=457746 Vladimir Yerilov changed: What|Removed |Added CC||openmind...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 474333] Stopped retaining open tabs
https://bugs.kde.org/show_bug.cgi?id=474333 Vladimir Stepanoff changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #2 from Vladimir Stepanoff --- Mageia 9 update of 9/11/23 fixed the problem although the dolphin version didn''t change! -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 474333] New: Stopped retaining open tabs
https://bugs.kde.org/show_bug.cgi?id=474333 Bug ID: 474333 Summary: Stopped retaining open tabs Classification: Applications Product: dolphin Version: 23.04.1 Platform: Mageia RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: v5234...@protonmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY *** In Mageia 9 9 (x86_64), dolphin 23.04.1 does not retain Folder,tabs and window state from last time. *** STEPS TO REPRODUCE 1. dolphin->Settings->Startup->Show on startup=Folder,tabs and window state from last time. 2. exit dolphin 3. restart dolphin OBSERVED RESULT Open tabs have disappeared EXPECTED RESULT Open tabs as before restart SOFTWARE/OS VERSIONS Mageia 9 9 (x86_64) kernel version: 6.4.9-desktop-4.mga9 (64-bit) dolphin 23.04.1 KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.7 built against 5.15.7 ADDITIONAL INFORMATION xcb windowing system -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 473886] Irrelevant search results in KRunner when searching for Gnome apps
https://bugs.kde.org/show_bug.cgi?id=473886 Vladimir Yerilov changed: What|Removed |Added CC||openmind...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 473886] Irrelevant search results in KRunner when searching for Gnome apps
https://bugs.kde.org/show_bug.cgi?id=473886 --- Comment #1 from Vladimir Yerilov --- Created attachment 161258 --> https://bugs.kde.org/attachment.cgi?id=161258=edit Proper search result This result is correct but one need to use native keyboard layout in order to get to it. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 473886] New: Irrelevant search results in KRunner when searching for Gnome apps
https://bugs.kde.org/show_bug.cgi?id=473886 Bug ID: 473886 Summary: Irrelevant search results in KRunner when searching for Gnome apps Classification: Plasma Product: krunner Version: 5.27.7 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: openmind...@gmail.com CC: alexander.loh...@gmx.de, natalie_clar...@yahoo.de Target Milestone: --- Created attachment 161257 --> https://bugs.kde.org/attachment.cgi?id=161257=edit Incomplete search result SUMMARY Since around 5.27 KRunner and Kickoff do not provide relevant results when searching some Gnome's application by its binary name, like 'disks' -- meaning 'gnome-disks', or 'virt' -- meaning 'virt-manager', until you enter a full name of app's executable, e.g. 'gnome-disks', but even then search results won't show a proper icon of the application, just a gear next to the text like 'Run %executable_name%'. STEPS TO REPRODUCE 1. Switch language to something other than English (and probably even non-West-European) 2. Open Kickoff, start typing some Gnome app's exec name you might have installed 3. See 0 hits or completely not what you have expected OBSERVED RESULT Irrelevant search results EXPECTED RESULT Entries of apps with that typed string present in the filename of their binaries SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro Linux latest possible (Unstable) KDE Plasma Version: 5.57.7 KDE Frameworks Version: 5.109.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION This happens to systems where English is NOT the default language. When searching using person's native language (e.g. 'диски' meaning 'gnome-disks'), one sees expected search result with right app on top of the list. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 402857] Touchpad gestures should be configurable
https://bugs.kde.org/show_bug.cgi?id=402857 Vladimir Yerilov changed: What|Removed |Added CC||openmind...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 419690] Night color setting doesn't extend to external monitors
https://bugs.kde.org/show_bug.cgi?id=419690 Vladimir Yerilov changed: What|Removed |Added CC||openmind...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 419858] Night Colour and Redshift require manual activation and display wrong status
https://bugs.kde.org/show_bug.cgi?id=419858 Vladimir Yerilov changed: What|Removed |Added CC||openmind...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 471931] org.kde.plasma.battery widget does not work properly on task bar
https://bugs.kde.org/show_bug.cgi?id=471931 Vladimir Yerilov changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||openmind...@gmail.com --- Comment #1 from Vladimir Yerilov --- Can confirm the weird behavior when switching power profiles with widget, and restarting plasma-plasmashell.service works for me too. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 470286] New: Plasma fault start on Xnest
https://bugs.kde.org/show_bug.cgi?id=470286 Bug ID: 470286 Summary: Plasma fault start on Xnest Classification: Plasma Product: plasmashell Version: 5.27.4 Platform: Compiled Sources OS: FreeBSD Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: vladimir.chervin...@autonit.spb.ru CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Application: plasmashell (5.27.4) (Compiled from sources) Qt Version: 5.15.8 Frameworks Version: 5.105.0 Operating System: FreeBSD 13.2-RELEASE amd64 Windowing System: X11 Distribution (Platform): FreeBSD Ports DrKonqi: 5.27.4 [KCrashBackend] -- Information about the crash: I start Xnest: Xnest :5 & I create new empty directory /home/new_dir I have all permisions in directory /home/new_dir I run: env DISPLAY=:5 HOME=/home/new_dir startplasma-x11 & On first start plasma generated bug. The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault [KCrash Handler] #7 0x0025889b in ?? () #8 0x00083e261863 in ?? () from /usr/local/lib/qt5/libQt5Core.so.5 #9 0x00083e2672c3 in QTimer::timerEvent(QTimerEvent*) () from /usr/local/lib/qt5/libQt5Core.so.5 #10 0x00083e2564fc in QObject::event(QEvent*) () from /usr/local/lib/qt5/libQt5Core.so.5 #11 0x000839e9cfb9 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/local/lib/qt5/libQt5Widgets.so.5 #12 0x000839e9e395 in QApplication::notify(QObject*, QEvent*) () from /usr/local/lib/qt5/libQt5Widgets.so.5 #13 0x00083e22d53d in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/local/lib/qt5/libQt5Core.so.5 #14 0x00083e280eda in QTimerInfoList::activateTimers() () from /usr/local/lib/qt5/libQt5Core.so.5 #15 0x00083e2828ed in ?? () from /usr/local/lib/qt5/libQt5Core.so.5 #16 0x000853b9ec54 in g_main_context_dispatch () from /usr/local/lib/libglib-2.0.so.0 #17 0x000853b9ef8c in ?? () from /usr/local/lib/libglib-2.0.so.0 #18 0x000853b9f038 in g_main_context_iteration () from /usr/local/lib/libglib-2.0.so.0 #19 0x00083e281fb0 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/local/lib/qt5/libQt5Core.so.5 #20 0x00083e229e66 in QEventLoop::exec(QFlags) () from /usr/local/lib/qt5/libQt5Core.so.5 #21 0x00083e22dbde in QCoreApplication::exec() () from /usr/local/lib/qt5/libQt5Core.so.5 #22 0x002432f3 in ?? () #23 0x00239dc0 in ?? () #24 0x00239cc0 in ?? () #25 0x in ?? () [Inferior 1 (process 4958) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 376728] Global Menu does not reappear for windows on session restore because appmenu kded module isn't loaded yet by the time the app launches
https://bugs.kde.org/show_bug.cgi?id=376728 --- Comment #12 from Vladimir Yerilov --- (In reply to Nate Graham from comment #11) > Is this still an issue with the systemd boot process in recent Plasma > versions? Haven't seen this issue for quite a long time. I use systemdBoot=true setting in startkderc file. Maybe I'm just a lucky one, need more confirmations. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 469656] Dolphin cannot remember previously opened tabs
https://bugs.kde.org/show_bug.cgi?id=469656 Vladimir Yerilov changed: What|Removed |Added CC||openmind...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 468469] Disabling compositing doesn't affect the lock screen
https://bugs.kde.org/show_bug.cgi?id=468469 --- Comment #8 from Vladimir Potapov --- Oh! I see now. In my localized version of KDE, "compositing" is translated as "effects". I think this is a more correct name, the user is not required to know the algorithms of effects, but should be able to disable them in those scenarios where they are not needed. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 468469] Disabling compositing doesn't affect the lock screen
https://bugs.kde.org/show_bug.cgi?id=468469 --- Comment #6 from Vladimir Potapov --- You need to disable the smooth change of background brightness before the password entry line appears when you press any key on the locked screen. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 447184] plasmashell uses 100% of cpu for extended period when switching desktops, when a custom *.desktop file is pinned in Task Manager
https://bugs.kde.org/show_bug.cgi?id=447184 --- Comment #6 from Vladimir Dergachev --- On Fri, 14 Apr 2023, Nate Graham wrote: > https://bugs.kde.org/show_bug.cgi?id=447184 > > Nate Graham changed: > > What|Removed |Added > > Resolution|WAITINGFORINFO |FIXED > Status|NEEDSINFO |RESOLVED > > --- Comment #5 from Nate Graham --- > Yep, I don't experience the bug with that .desktop file pinned to my Task > Manager. So let's call it fixed! Agreed ! > > It's always possible to compile a new Plasma on an old distro, but the older > the distro, the harder it will be since Plasma frequently depends on > relatively > new versions of 3rd-party libraries. I'd file it under "possible but painful" > (or adventurous, depending on how you want to look at it!). > > Also JFYI you probably need to be testing your code for speed and correctness > with new tooling as well as old tooling, because you can't guarantee that all > of your users will be using software compiled with old tooling, unless you > distribute the software yourself in purely binary form. As long as the source > code is available, any random distro can compile it with any tooling and > package it up for consumption. No, no, this is a different situation - this is a numerical code and speed is critical, so one needs to control assembly output. So I want the C compiler to produce a binary where inner loops do exactly what I want. When you upgrade distros gcc and C libraries often have large changes. A lot of those changes are well-intentioned attempts to automatically secure programs against bugs or introduce speedups into poorly optimized programs, at the expense of numerical codes such as mine. So I compare runtime between different binaries and start digging into assembly to figure out what went wrong. This fine tuning is worthwhile because the code takes months to run. It is the results that are distributed to the users - they are portable and use MVL library (package RMVL if you use R). thank for looking into this ! Vladimir Dergachev > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 468469] I can't disable effects
https://bugs.kde.org/show_bug.cgi?id=468469 --- Comment #4 from Vladimir Potapov --- System settings-compositor Compositior: enable on startup This setting enable-disables effects for the entire system, except for the screenblock -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 468469] I can't disable effects
https://bugs.kde.org/show_bug.cgi?id=468469 --- Comment #2 from Vladimir Potapov --- For example, take remote work via krfb-krdc over a slow connection. In this case, a reduced palette of colors is used. If the effects are turned on, I see a lot of color spots running around the screen, not adding beauty, only taking up the channel and time. For the desktop, I can turn off the effects and everything works fast. But it doesn't work for the blocker. I observed a similar picture on atomic netbooks, the plasma speed there is quite enough to work, but the effects have to be turned off. Unfortunately, this is impossible for a blocker. Another braking element is logging in via sddm, but I solve this problem by switching to lightdm. Otherwise, KDE plasma with disabled effects is comparable in speed and resource consumption to LXQT. This allows it to be used on weak machines, in the remote use option, for the graphical interface of servers in a virtual environment. Disabling effects gives a lot of options for using KDE Plasma, I would like this shutdown to apply to all elements of the system. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 447184] plasmashell uses 100% of cpu for extended period when switching desktops, when a custom *.desktop file is pinned in Task Manager
https://bugs.kde.org/show_bug.cgi?id=447184 --- Comment #4 from Vladimir Dergachev --- Oh, I see - is there a straightforward way to install the latest version to test without upgrading the whole distribution ? Years ago I was happily compiling KDE and it was often possible to compile one component at a time. Once I even compiled it for Solaris - was a major improvement over CDE. For me the key thing is stability of tools like gcc and system libraries - upgrading the distribution changes versions and then I need to retest my code again for speed. That's why I stick to LTS versions of Ubuntu. Btw, if you have the newest version installed, maybe you could run a quick test ? All one needs to do is to create a KDE desktop file pointing to any executable, assign an icon to it and pin it in the task manager. The if switching desktops is seamless, chances are it is fixed in the newest version. I also attached my Light.desktop file in case it is useful. thank you Vladimir Dergachev On Thu, 13 Apr 2023, Nate Graham wrote: > https://bugs.kde.org/show_bug.cgi?id=447184 > > Nate Graham changed: > > What|Removed |Added > > Resolution|--- |WAITINGFORINFO > Status|REPORTED|NEEDSINFO > > --- Comment #3 from Nate Graham --- > Yes. I would strongly recommend upgrading; Plasma 5.18 has been out of support > for years. If you upgrade to Kubuntu 22.04, you'll at least get Plasma 5.24, > which is still out of support, but it's much newer and less buggy. And then > you > can upgrade to Kubuntu 23.04 once it's released this month and get Plasma > 5.27, > which is supported and will be supported through the end of the year at least. > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 468469] New: I can't disable effects
https://bugs.kde.org/show_bug.cgi?id=468469 Bug ID: 468469 Summary: I can't disable effects Classification: Plasma Product: kscreenlocker Version: git-stable-Plasma/5.27 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: ke...@mail.ru Target Milestone: --- For remote desktop, I turn off the effects in plasma. They are turned off throughout the system, but only the screen blocker continues to work with effects. This makes some operations very difficult. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 447184] plasmashell uses 100% of cpu for extended period when switching desktops, when a custom *.desktop file is pinned in Task Manager
https://bugs.kde.org/show_bug.cgi?id=447184 --- Comment #2 from Vladimir Dergachev --- Not sure - I am using Kubuntu 20.04, currently running plasma 5.18.8, Is it still the case that to try new plasmashell one needs to replace the whole KDE ? On Tue, 11 Apr 2023, Nate Graham wrote: > https://bugs.kde.org/show_bug.cgi?id=447184 > > Nate Graham changed: > > What|Removed |Added > > CC||n...@kde.org > > --- Comment #1 from Nate Graham --- > Sorry no one got back to you about this bug earlier. Are you able to reproduce > the issue with Plasma 5.27.4 or newer? > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 464253] Support NAT
https://bugs.kde.org/show_bug.cgi?id=464253 --- Comment #3 from Vladimir Panteleev --- (In reply to ©TriMoon™ from comment #2) > Broadcast packets don't use source addresses AFAIK... The mobile client (on Android at least) supports adding devices by IP, in which case it does not use broadcast packets. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 467609] hung from resume
https://bugs.kde.org/show_bug.cgi?id=467609 --- Comment #3 from Vladimir Potapov --- (In reply to Nate Graham from comment #1) > Does the issue reproduce when when not using screen locking? I.e. when you > go to System Settings > Workspace Behavior > Screen Locking and uncheck > "After waking from sleep"? Yes, the issue reproduce without Screen Locking. On resume I see only black screen. journalctl -b -1 ended: апр 05 15:16:00 keleg-nvidia systemd[1]: grub-common.service: Deactivated successfully. апр 05 15:16:00 keleg-nvidia systemd[1]: Finished Record successful boot for GRUB. апр 05 15:16:00 keleg-nvidia systemd[1]: Starting GRUB failed boot detection... апр 05 15:16:00 keleg-nvidia systemd[1]: grub-initrd-fallback.service: Deactivated successfully. апр 05 15:16:00 keleg-nvidia systemd[1]: Finished GRUB failed boot detection. апр 05 15:16:01 keleg-nvidia systemd[1]: nvidia-suspend.service: Deactivated successfully. апр 05 15:16:01 keleg-nvidia systemd[1]: Finished NVIDIA system suspend actions. апр 05 15:16:01 keleg-nvidia systemd[1]: Starting System Suspend... апр 05 15:16:01 keleg-nvidia systemd-sleep[1604]: Entering sleep state 'suspend'... апр 05 15:16:01 keleg-nvidia kernel: PM: suspend entry (deep) -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 467609] New: hung from resume
https://bugs.kde.org/show_bug.cgi?id=467609 Bug ID: 467609 Summary: hung from resume Classification: Plasma Product: kscreenlocker Version: git-stable-Plasma/5.27 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: ke...@mail.ru Target Milestone: --- 1) Set up new KDE Neon Plasma 5.27.3 2) ubuntu-drivers autoinstall (set up proprietary drivers for my NVIDIA GTX650) 3) reboot, enter to system 4) standby mode/resume 5) blank screen and keyboard hung, only hard reset... on free nouveau drivers system work correct. The bug present for 5.27.1, 5.27.2, 5.27.3 but not present for plasma 5.25.5 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 343690] Missing windows tabbing
https://bugs.kde.org/show_bug.cgi?id=343690 Vladimir Yerilov changed: What|Removed |Added CC||openmind...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 435544] Application focus issue
https://bugs.kde.org/show_bug.cgi?id=435544 --- Comment #12 from Vladimir Yerilov --- Created attachment 157036 --> https://bugs.kde.org/attachment.cgi?id=157036=edit Kwin rule (In reply to Kai Eckert from comment #11) > I can confirm that the bug still exists, it annoys me to the point that I > had to switch off the "keep open" option. Nothing worse than constantly > accidently writing stuff into the wrong window. > > Yakuake 22.12.3 > Plasma 5.27.2 To work it around, go to Window Management -> Window Rules, and a new rule for yakuake as shown on atached file. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 446624] Pressing Meta makes plasma icon appear in overview effect on X11
https://bugs.kde.org/show_bug.cgi?id=446624 --- Comment #23 from Vladimir Yerilov --- Yeah Nate you are right, I should have said that the menu appears not in main view but in the upper virtual desktops preview section. I guess it's not designed this way that's why I wrote that the bug is still present. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 446624] Pressing Meta makes plasma icon appear in overview effect on X11
https://bugs.kde.org/show_bug.cgi?id=446624 --- Comment #21 from Vladimir Yerilov --- (In reply to Chris Rizzitello from comment #20) > This appears to be fixed, Unable to reproduce on Arch with > Plasma 5.27.1 > KDE Frameworks: 5.103.0 > FOSS AMD Drivers > on Both X11 and Wayland Manjaro, 5.27.1, i915, X session: it's still here. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 466121] Folders panel menu translucency is broken
https://bugs.kde.org/show_bug.cgi?id=466121 --- Comment #3 from Vladimir Yerilov --- Couldn't reproduce it in Wayland session, it happens under X only. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 466121] Folders panel menu translucency is broken
https://bugs.kde.org/show_bug.cgi?id=466121 --- Comment #2 from Vladimir Yerilov --- Interesting enough, I also see infamous "corners" bug for menus in Dolphin, but that (and the menu translucency thing) affects only my Manjaro install, and does not affect Tumbleweed VM. Probably some old config-related thing? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 466121] Folders panel menu translucency is broken
https://bugs.kde.org/show_bug.cgi?id=466121 Vladimir Yerilov changed: What|Removed |Added Summary|Translucent menu in folders |Folders panel menu |panel is broken |translucency is broken -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 466121] Translucent menu in folders panel is broken
https://bugs.kde.org/show_bug.cgi?id=466121 --- Comment #1 from Vladimir Yerilov --- Created attachment 156525 --> https://bugs.kde.org/attachment.cgi?id=156525=edit What a "normal" menu looks like -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 466121] New: Translucent menu in folders panel is broken
https://bugs.kde.org/show_bug.cgi?id=466121 Bug ID: 466121 Summary: Translucent menu in folders panel is broken Classification: Applications Product: dolphin Version: 22.12.2 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: panels: folders Assignee: dolphin-bugs-n...@kde.org Reporter: openmind...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Created attachment 156524 --> https://bugs.kde.org/attachment.cgi?id=156524=edit Dolphin's broken menu SUMMARY *** Trancparency/blur of folders panel's context menu looks broken. *** STEPS TO REPRODUCE 1. Set transparency for menus in Breeze application style in Systemsettings 2. Open Dolphin 3. Right-click on any item is the left panel OBSERVED RESULT Menu looks weird EXPECTED RESULT Menu should look like any other menu SOFTWARE/OS VERSIONS Windows: n/a macOS: n/a Linux/KDE Plasma: KDE Plasma Version: 5.27.0 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION I observe this with both Breeze and Klassy widget styles. Lightly style is not affected (it's too much different though). Can't remember if this started to happen after Plasma 5.27 update, but I'd rather blame Frameworks 5.103.0 update. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465251] "Leave" menu item is not persistent when switching between X11 and Wayland sessions
https://bugs.kde.org/show_bug.cgi?id=465251 --- Comment #9 from Vladimir Yerilov --- >>Or just the "Leave…" menu item? Even more strange, not only it does not affect other options, once "Leave..." item has been added in both sessions, it starts to (dis)appear in both instantly as expected (as per user settings). So only the first encounter with this preference is flawed if switching to another session type as described above. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465251] "Leave" menu item is not persistent across sessions
https://bugs.kde.org/show_bug.cgi?id=465251 Vladimir Yerilov changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |NOT A BUG --- Comment #5 from Vladimir Yerilov --- So I checked it once again using openSUSE Tumbleweed VM, and was unable to reproduce the issue. However, it still kinda exists: 1. Boot Live media, it starts X session by default. 2. Add this menu item, log out. 3. Change session to Wayland on SDDM greeter screen, log in. 4. Observe no menu item, add it. 5. Now it's there in both X and Wayland sessions. To sum up, it seems like X and Wayland sessions have separate lists (sets) of desktop menu items and both need a manual intervention to display a new item. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465251] "Leave" menu item is not persistent across sessions
https://bugs.kde.org/show_bug.cgi?id=465251 Vladimir Yerilov changed: What|Removed |Added Summary|Log out menu item is not|"Leave" menu item is not |persistent across sessions |persistent across sessions -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 457672] Spotify notifications (coming from plasma-workspace, through XDG portal) plays error sound
https://bugs.kde.org/show_bug.cgi?id=457672 Vladimir Solomatin changed: What|Removed |Added CC||proge...@yandex.ru -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465251] Log out menu item is not persistent across sessions
https://bugs.kde.org/show_bug.cgi?id=465251 --- Comment #4 from Vladimir Yerilov --- (In reply to Nate Graham from comment #3) > > log out menu item > Did you mean the "Leave…" menu item? There is no "log out" menu item. Can > you attach a screenshot that shows the config window where you add it? > > When I add the "Leave…" menu item and reboot, it's still there. Yeah, sorry, I meant "Leave...", of course. I forgot what it used to be in English. For now I cannot test if it is fixed because the latest Neon Unstable build is flawed with startplasma-x11 failure on boot, so I can't get to the graphical interface at all. If that works on your side, I hope it's fixed then. I just need to make a stress on the fact that in order to check it one needs a LiveCD system, not a system installed before 5.26 was rolled out, because on my old Manjaro install this option works as expected, but any fresh ISO produced the result I reported here. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465251] Log out menu item is not persistent across sessions
https://bugs.kde.org/show_bug.cgi?id=465251 --- Comment #1 from Vladimir Yerilov --- One thing I forgeot to mention: I noticed this in Manjaro as well. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465251] New: Log out menu item is not persistent across sessions
https://bugs.kde.org/show_bug.cgi?id=465251 Bug ID: 465251 Summary: Log out menu item is not persistent across sessions Classification: Plasma Product: plasmashell Version: master Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Desktop Containment Assignee: plasma-b...@kde.org Reporter: openmind...@gmail.com CC: notm...@gmail.com Target Milestone: 1.0 SUMMARY *** Log out desktop context menu option is gone after closing session. *** STEPS TO REPRODUCE 1. Right-click on desktop, select menu item to configure Desktop settings 2. Go to mouse action pane, hit gear for editing context menu options, tick log out item to enable it 3. Log out / reboot using any method, log in again, press mouse right button when hovering cursor over desktop OBSERVED RESULT No log out menu item EXPECTED RESULT Once enabled, log out menu item should not disappear SOFTWARE/OS VERSIONS Linux/KDE Plasma: Any fresh installed / LiveCD since Plasma 5.26 (available in About System) KDE Plasma Version: 5.26 and up KDE Frameworks Version: 5.102 Qt Version: 5.15 ADDITIONAL INFORMATION I noticed it when I was playing with Wayland session on Kubuntu and Neon Unstable in late 2022, checked in January 2023 - the issue was still there. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 464253] New: Support NAT
https://bugs.kde.org/show_bug.cgi?id=464253 Bug ID: 464253 Summary: Support NAT Classification: Applications Product: kdeconnect Version: unspecified Platform: Compiled Sources OS: All Status: REPORTED Severity: minor Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: k...@thecybershadow.net CC: andrew.g.r.hol...@gmail.com Target Milestone: --- Consider the situation where two clients are on a network with hairpin NAT (e.g. they are on the same Wireguard network, with the gateway set up to enable IP forwarding). In this case, packets are NAT-ed by the gateway. When this is done, the source port is replaced by a randomly allocated port on the gateway. When kdeconnectd receives the initial packet, it disregards the packet's source port and always attempts to reply to port 1716. This causes the packet to not be routed by the gateway back to the original server, causing the devices to not see each other. Ideally, kdeconnectd should pay attention to the port number of received packets, and reply to this number. Hopefully, combined with adding devices by IP in the mobile client, that should allow kdeconnect to work on such network configurations. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 322762] Please allow gestures for multi touchpad's in KDE
https://bugs.kde.org/show_bug.cgi?id=322762 Vladimir Yerilov changed: What|Removed |Added Component|kcm_khotkeys|kcm_touchpad Assignee|k...@michael-jansen.biz |plasma-b...@kde.org --- Comment #1 from Vladimir Yerilov --- Yeah, a much anticipated feature, esp on Wayland where gestures are hardcoded and cannot be changed or disabled. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 322762] Please allow gestures for multi touchpad's in KDE
https://bugs.kde.org/show_bug.cgi?id=322762 Vladimir Yerilov changed: What|Removed |Added CC||openmind...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 422552] Auto-detect appropriate scale factor for the easy cases (e.g. 4k screen) on X11
https://bugs.kde.org/show_bug.cgi?id=422552 Vladimir Yerilov changed: What|Removed |Added CC||openmind...@gmail.com --- Comment #14 from Vladimir Yerilov --- Hi, I have a 15" laptop with 3200x2000 resolution and I would've been perfectly fine with auto-applied 2X scale, which I set manually and which is used to be set automatically in Gnome. Of course it makes elements of UI a bit bigger than I used to, but as a starting point that's okay, way better than no scaling at all. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 437471] Cannot unlock KDE lockscreen after undocking while laptop screen was off
https://bugs.kde.org/show_bug.cgi?id=437471 Vladimir Yerilov changed: What|Removed |Added CC||openmind...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433563] Password field input not displayed on primary screen
https://bugs.kde.org/show_bug.cgi?id=433563 Vladimir Yerilov changed: What|Removed |Added CC||openmind...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413645] Can't remember desktop widget positions after reboot
https://bugs.kde.org/show_bug.cgi?id=413645 --- Comment #60 from Vladimir Yerilov --- Hope it will make it possible to use widgets on my multi-monitor setup without them losing their position or even disappear as it used to happen in the past. Will see. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413645] Can't remember desktop widget positions after reboot
https://bugs.kde.org/show_bug.cgi?id=413645 Vladimir Yerilov changed: What|Removed |Added CC||openmind...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 418363] Legend's font in "Energy Consumption Statistics" graph is blurry
https://bugs.kde.org/show_bug.cgi?id=418363 --- Comment #5 from Vladimir Yerilov --- (In reply to Nate Graham from comment #4) > I can't reproduce this issue in the Plasma 5.26 beta, can you? Hi Nate thanks for coming by. Yes it looks like it's been fixed and looks less blurry now in Plasma 5.26 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 419867] Unable to use scrollwheel on desktop to change Virtual Desktop
https://bugs.kde.org/show_bug.cgi?id=419867
--- Comment #66 from Vladimir Yerilov ---
(In reply to André from comment #65)
> For anyone that needs a quick fix to this problem i suggest doing this:
> 1) Copy the folder org.kde.desktopcontainment from
> /usr/share/plasma/plasmoids/org.kde.desktopcontainment
> 2) Paste it inside $HOME/.local/share/plasma/plasmoids/
> 3) Open the file
> $HOME/.local/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/
> FolderView.qml
> 4) Look for this line: Folder.WheelInterceptor {
> 5) Change the property from enabled: root.isContainment &&
> !gridView.overflowing to enabled: true
> 6) Save the file
> 7) Restart Plasma and it should work ;-)
Waow thanks André it worked! What a relief!
--
You are receiving this mail because:
You are watching all bug changes.
[yakuake] [Bug 441067] Yakuake is no longer available in the task switcher list
https://bugs.kde.org/show_bug.cgi?id=441067 --- Comment #15 from Vladimir Yerilov --- I think by default Yakuake should be present in task switcher (Alt + Tab) - especially when it is pinned to be always on, but always skip task manager (applet). This makes sense in order to switch to it without pressing invoke key (F12) twice, which would first hide it, and then show it focused again, and given that often keyboards have multimedia keys assigned to Fn keys, making it accessible without extra hassle with Fn keys could be useful. At least this is what I ended up with using Kwin rules. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 422951] Type-ahead navigation in dolphin resets position mid-search when a file is selected
https://bugs.kde.org/show_bug.cgi?id=422951 --- Comment #8 from Vladimir Yerilov --- I noticed that 1-letter navigation is still possible. For instance, pressing "m" in /etc once results in jumping "modprobe.d", then pressing it the 2nd time moves the selection to "modules-load", and so on, then as directories starting with are over, the selection scrolls down to the first file starting with "m" like "machine-id", and continues to move down as user keeps pressing "m" button. This is, however, not even half as convenient as it was before this bug was introduced, and filter panel for now feels like a better way to quickly jump to a file of interest. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 457288] New: nvidia drivers crash
https://bugs.kde.org/show_bug.cgi?id=457288 Bug ID: 457288 Summary: nvidia drivers crash Product: systemsettings Version: 5.18.7 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: larionov.v...@gmail.com Target Milestone: --- Application: systemsettings5 (5.18.7) Qt Version: 5.12.8 Frameworks Version: 5.68.0 Operating System: Linux 5.15.0-41-generic x86_64 Windowing system: X11 Distribution: Ubuntu 20.04.4 LTS -- Information about the crash: - What I was doing when the application crashed: System crashes after installing nvidia drivers version 340.108. The crash can be reproduced every time. -- Backtrace: Application: System Settings (systemsettings5), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f2c40ed1080 (LWP 21875))] Thread 5 (Thread 0x7f2c2eaee700 (LWP 21881)): #0 0x7ffe085d7aed in clock_gettime () #1 0x7f2c47db00b5 in __GI___clock_gettime (clock_id=1, tp=0x7f2c2eaedab0) at ../sysdeps/unix/sysv/linux/clock_gettime.c:38 #2 0x7f2c48384d15 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f2c483835ad in QTimerInfoList::updateCurrentTime() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f2c48383b89 in QTimerInfoList::timerWait(timespec&) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f2c483851a6 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f2c45dfa8ef in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7f2c45dfb29b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #8 0x7f2c45dfb4a3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #9 0x7f2c48385453 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f2c4832c3ab in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7f2c48164785 in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7f2c474161a9 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #13 0x7f2c481659d2 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x7f2c469a1609 in start_thread (arg=) at pthread_create.c:477 #15 0x7f2c47df2133 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7f2c3d18f700 (LWP 21880)): #0 0x7f2c45df9262 in g_source_ref () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f2c45df9328 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f2c45dfacbf in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f2c45dfb312 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f2c45dfb4a3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f2c48385453 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f2c4832c3ab in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f2c48164785 in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f2c474161a9 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #9 0x7f2c481659d2 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f2c469a1609 in start_thread (arg=) at pthread_create.c:477 #11 0x7f2c47df2133 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7f2c3f0a1700 (LWP 21878)): #0 0x7ffe085d7aed in clock_gettime () #1 0x7f2c47db00b5 in __GI___clock_gettime (clock_id=1, tp=0x7f2c3f0a0aa0) at ../sysdeps/unix/sysv/linux/clock_gettime.c:38 #2 0x7f2c48384d15 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f2c483835ad in QTimerInfoList::updateCurrentTime() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f2c48383b89 in QTimerInfoList::timerWait(timespec&) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f2c483851a6 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f2c45dfa8ef in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7f2c45dfb29b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #8 0x7f2c45dfb4a3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #9 0x7f2c48385453 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f2c4832c3ab in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7f2c48164785 in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7f2c48607efa in ?? () from /lib/x86_64-linux-gnu/libQt5DBus.so.5 #13 0x7f2c481659d2 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x7f2c469a1609 in start_thread (arg=) at pthread_create.c:477 #15
[kwin] [Bug 430010] Desktop freeze after resume from Screen Energy Saving.
https://bugs.kde.org/show_bug.cgi?id=430010 --- Comment #2 from Vladimir --- (In reply to postix from comment #1) > Can you still reproduce it with some more recent Plasma version? With Plasma 5.24.6 I cannot while reproduce it, I observe now. With versions below current version I have the issue. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 455438] New: Fortinet VPN doesn't wait for DUO/2FA answer long enough
https://bugs.kde.org/show_bug.cgi?id=455438 Bug ID: 455438 Summary: Fortinet VPN doesn't wait for DUO/2FA answer long enough Product: plasma-nm Version: 5.23.0 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: editor Assignee: jgrul...@redhat.com Reporter: vladimiro...@gmail.com Target Milestone: --- SUMMARY When using Fortinet paired with DUO 2FA the Network Manager Openforticlient applet waits only 2-3 seconds before giving up, this means you miss the opportunity to approve the connection 99% of the time. This doesn't happen with the openfortivpn client used as a CLI app. STEPS TO REPRODUCE 1. Have your Fortinet VPN setup with DUO 2FA 2. Try to connect to your VPN 3. Wait 5 seconds, the connection attempt is dropped OBSERVED RESULT the connection attempt is dropped before you can approve in DUO EXPECTED RESULT the connection attempt is should wait the same time as the CLI version (30 seconds?) for the approval before giving up SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 21.10 KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 377162] Window shading not supported for Wayland windows
https://bugs.kde.org/show_bug.cgi?id=377162 Vladimir Yerilov changed: What|Removed |Added CC||openmind...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 448418] [wayland] - plasma 5.24 - primary display is not respected as it should
https://bugs.kde.org/show_bug.cgi?id=448418 --- Comment #5 from Vladimir Yerilov --- (In reply to Michail Vourlakos from comment #4) > Git commit b1d57051c227ce5f52bde52b8f8308273fa2127b by Michail Vourlakos. > Committed on 09/05/2022 at 17:35. > Pushed by mvourlakos into branch 'master'. > > wayland:support Plasma primaryscreen protocol > > --use ScreenPool as reference for primary screen. > The new code uses PrimaryOutputWatcher class from > Plasma Shell in order to keep track of primary > screen at all cases. > FIXED-IN:0.11.0 Works great on Plasma 5.24.5, thanks! Tried unplugging my external monitor and plugging it back, both times Latte moved to the correct screen automatically. The only drawback now is on Plasma side as it resets the wallpaper on the external monitor to the defaults but Latte is fine anyway. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 445893] KDE Plasma segfaults in Plasma::WindowTextureProvider::~WindowTextureProvider()
https://bugs.kde.org/show_bug.cgi?id=445893 Vladimir changed: What|Removed |Added CC||vladimir.mensha...@gmail.co ||m -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 445893] KDE Plasma segfaults in Plasma::WindowTextureProvider::~WindowTextureProvider()
https://bugs.kde.org/show_bug.cgi?id=445893 --- Comment #11 from Vladimir --- Created attachment 148398 --> https://bugs.kde.org/attachment.cgi?id=148398=edit New crash information added by DrKonqi plasmashell (5.24.4) using Qt 5.15.3 - What I was doing when the application crashed: - Clicked task bar, then plasmashell exited and restarted. I didn't do anything else -- Backtrace (Reduced): #4 0x7f062f64fe90 in QSGAreaAllocator::deallocateInNode(QPoint const&, QSGAreaAllocatorNode*) () at /usr/lib64/libQt5Quick.so.5 #5 0x7f062f64ff06 in QSGAreaAllocator::deallocate(QRect const&) () at /usr/lib64/libQt5Quick.so.5 #6 0x7f062f65642f in QSGOpenGLAtlasTexture::AtlasBase::remove(QSGOpenGLAtlasTexture::TextureBase*) () at /usr/lib64/libQt5Quick.so.5 #7 0x7f062f65657d in QSGOpenGLAtlasTexture::Texture::~Texture() () at /usr/lib64/libQt5Quick.so.5 #8 0x7f062f656599 in QSGOpenGLAtlasTexture::Texture::~Texture() () at /usr/lib64/libQt5Quick.so.5 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 452778] Dolphin can't copy a file into network folder with samba version 1.0
https://bugs.kde.org/show_bug.cgi?id=452778 --- Comment #2 from Vladimir --- Hi! I am accessing this Samba share from its smb:// URL I know that support mounting shares by SMB1 protocol was removed from linux kernel since 5.15 >Среда, 20 апреля 2022, 18:12 +03:00 от Nate Graham : > >https://bugs.kde.org/show_bug.cgi?id=452778 > >Nate Graham < n...@kde.org > changed: > > What |Removed |Added > > CC| |n...@kde.org > Status|REPORTED |NEEDSINFO > Resolution|--- |WAITINGFORINFO > >--- Comment #1 from Nate Graham < n...@kde.org > --- >Are you accessing the Samba share from its smb:// URL, or have you manually >mounted it? > >-- >You are receiving this mail because: >You reported the bug. С уважением, Владимир Приходько v...@inbox.ru -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 452778] New: Dolphin can't copy a file into network folder with samba version 1.0
https://bugs.kde.org/show_bug.cgi?id=452778 Bug ID: 452778 Summary: Dolphin can't copy a file into network folder with samba version 1.0 Product: dolphin Version: 21.12.3 Platform: Manjaro OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: v...@inbox.ru CC: kfm-de...@kde.org 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 *** I have a device with samba share (TV-box). Samba version is 1.0 and it is impossible to update it. When I use Dolphin to copy any file into his shared folder, I get an error "Insufficient free disk space..." But if I use the other file manager (thunar, nautilus) everything works just fine. STEPS TO REPRODUCE 1. Open Dolphin 2. Find device's share 3. Try to copy any file on local disk and paste it into founded share OBSERVED RESULT Error "Insufficient free disk space..." EXPECTED RESULT Successful paste SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 452776] New: krita flashing krita program windov when moving mouse cursor on window =(
https://bugs.kde.org/show_bug.cgi?id=452776 Bug ID: 452776 Summary: krita flashing krita program windov when moving mouse cursor on window =( Product: krita Version: 5.0.5 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: critical Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: vladimiryn...@gmail.com Target Milestone: --- Krita flashing betwen normal and dark program window screen. Itryed to cach video from this problem but on cached video dosnt showing this bug. All redy tryed many versions of krita.. =( 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.
[kwin] [Bug 451778] Blur/Kornerbug enabled even when a window is set to opaque
https://bugs.kde.org/show_bug.cgi?id=451778 Vladimir Yerilov changed: What|Removed |Added CC||openmind...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 436553] X-KDE-Protocols fails to work as expected in some cases
https://bugs.kde.org/show_bug.cgi?id=436553 Vladimir Yerilov changed: What|Removed |Added CC||openmind...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kiofuse] [Bug 75324] Integrate KIO Slaves into file system using FUSE gateway
https://bugs.kde.org/show_bug.cgi?id=75324 Vladimir Yerilov changed: What|Removed |Added CC|openmind...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 424416] Type-ahead selection depends on typing speed
https://bugs.kde.org/show_bug.cgi?id=424416 Vladimir Yerilov changed: What|Removed |Added CC||openmind...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 427069] [wayland] Krunner starts on the most left screen.
https://bugs.kde.org/show_bug.cgi?id=427069 vladimir changed: What|Removed |Added CC||vsafo...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdev-python] [Bug 438206] Fails to build against Python 3.10
https://bugs.kde.org/show_bug.cgi?id=438206 Vladimir Yerilov changed: What|Removed |Added CC||openmind...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443410] Please restore the Desktop Cube switching effect
https://bugs.kde.org/show_bug.cgi?id=443410 Vladimir Yerilov changed: What|Removed |Added CC|openmind...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450520] Ushading is not working in breeze theme with borders
https://bugs.kde.org/show_bug.cgi?id=450520 --- Comment #2 from Vladimir Yerilov --- >anything other than no border Can only confirm. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450520] Ushading is not working in breeze theme with borders
https://bugs.kde.org/show_bug.cgi?id=450520 Vladimir Yerilov changed: What|Removed |Added CC||openmind...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 370676] Greeter shows wallpaper, but no input widgets; cannot unlock screen
https://bugs.kde.org/show_bug.cgi?id=370676 Vladimir Tennov changed: What|Removed |Added CC||tennov+...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448943] Night color not enabled auto after log in
https://bugs.kde.org/show_bug.cgi?id=448943 Vladimir Yerilov changed: What|Removed |Added CC|openmind...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448943] Night color not enabled auto after log in
https://bugs.kde.org/show_bug.cgi?id=448943 Vladimir Yerilov changed: What|Removed |Added CC||openmind...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 449860] Systemsettings: clearing search term shows incorrect left column
https://bugs.kde.org/show_bug.cgi?id=449860 Vladimir Yerilov changed: What|Removed |Added CC|openmind...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 446288] Clearing search returns focus to subcategory page in compact view
https://bugs.kde.org/show_bug.cgi?id=446288 Vladimir Yerilov changed: What|Removed |Added CC||openmind...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
