[plasmashell] [Bug 372723] New: KDE restart
https://bugs.kde.org/show_bug.cgi?id=372723 Bug ID: 372723 Summary: KDE restart Product: plasmashell Version: 5.7.5 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: shadeinthe...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.7.5) Qt Version: 5.6.1 Frameworks Version: 5.27.0 Operating System: Linux 4.8.7-200.fc24.x86_64 x86_64 Distribution (Platform): Fedora RPMs -- Information about the crash: - What I was doing when the application crashed: Im try start megasync app on to the root, im see brakeble megasync icon in tray and not access to app. im try start megasync app in user rights but not see trayicon and app interface, but in "htop" i see app and 100% CPU loaded... im use Fedora 24 x64 KDE edition The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fb7baefa940 (LWP 1652))] Thread 8 (Thread 0x7fb6fb47b700 (LWP 6846)): #0 0x7fb7ca705da0 in timerSourcePrepareHelper(GTimerSource*, int*) () at /lib64/libQt5Core.so.5 #1 0x7fb7ca705e75 in timerSourcePrepare(_GSource*, int*) () at /lib64/libQt5Core.so.5 #2 0x7fb7c503ef59 in g_main_context_prepare () at /lib64/libglib-2.0.so.0 #3 0x7fb7c503f92b in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #4 0x7fb7c503fb1c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #5 0x7fb7ca70624b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #6 0x7fb7ca6b55ea in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #7 0x7fb7ca514343 in QThread::exec() () at /lib64/libQt5Core.so.5 #8 0x7fb7cd7f08f5 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5 #9 0x7fb7ca51899a in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #10 0x7fb7c8c5c5ca in start_thread () at /lib64/libpthread.so.0 #11 0x7fb7c990c0ed in clone () at /lib64/libc.so.6 Thread 7 (Thread 0x7fb704976700 (LWP 1926)): #0 0x7ffdd098ca8c in clock_gettime () #1 0x7fb7c991a6f6 in clock_gettime () at /lib64/libc.so.6 #2 0x7fb7ca5b4ab3 in qt_gettime() () at /lib64/libQt5Core.so.5 #3 0x7fb7ca704869 in QTimerInfoList::updateCurrentTime() () at /lib64/libQt5Core.so.5 #4 0x7fb7ca704c65 in QTimerInfoList::timerWait(timespec&) () at /lib64/libQt5Core.so.5 #5 0x7fb7ca705dac in timerSourcePrepareHelper(GTimerSource*, int*) () at /lib64/libQt5Core.so.5 #6 0x7fb7c503ef59 in g_main_context_prepare () at /lib64/libglib-2.0.so.0 #7 0x7fb7c503f92b in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #8 0x7fb7c503fb1c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #9 0x7fb7ca70624b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #10 0x7fb7ca6b55ea in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #11 0x7fb7ca514343 in QThread::exec() () at /lib64/libQt5Core.so.5 #12 0x7fb70654e2e7 in KCupsConnection::run() () at /lib64/libkcupslib.so #13 0x7fb7ca51899a in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #14 0x7fb7c8c5c5ca in start_thread () at /lib64/libpthread.so.0 #15 0x7fb7c990c0ed in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7fb79afba700 (LWP 1802)): #0 0x7fb7c8c61bd0 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fb7d000fbc4 in QTWTF::TCMalloc_PageHeap::scavengerThread() () at /lib64/libQt5Script.so.5 #2 0x7fb7d000fc09 in () at /lib64/libQt5Script.so.5 #3 0x7fb7c8c5c5ca in start_thread () at /lib64/libpthread.so.0 #4 0x7fb7c990c0ed in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7fb7a8e13700 (LWP 1798)): #0 0x7fb7c5083a24 in g_mutex_unlock () at /lib64/libglib-2.0.so.0 #1 0x7fb7c503f91e in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #2 0x7fb7c503fb1c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x7fb7ca70624b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #4 0x7fb7ca6b55ea in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7fb7ca514343 in QThread::exec() () at /lib64/libQt5Core.so.5 #6 0x7fb7cd7f08f5 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5 #7 0x7fb7ca51899a in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #8 0x7fb7c8c5c5ca in start_thread () at /lib64/libpthread.so.0 #9 0x7fb7c990c0ed in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7fb7aa7c2700 (LWP 1728)): #0 0x7fb7c990056d in poll () at /lib64/libc.so.6 #1 0x7fb7c503fa06 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #
[konsole] [Bug 488905] New: Feature request: OSC 12 support (Change text cursor color)
https://bugs.kde.org/show_bug.cgi?id=488905 Bug ID: 488905 Summary: Feature request: OSC 12 support (Change text cursor color) Classification: Applications Product: konsole Version: 24.05.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: emulation Assignee: konsole-de...@kde.org Reporter: sliva...@gmail.com Target Milestone: --- SUMMARY Konsole already supports OSC 10 and 11 (text fg/bg colors) but doesn't support OSC 110 and 111 (reset for fg/bg colors), and OSC 12 and 112 (text cursor color and reset). STEPS TO REPRODUCE 1. run the command: printf '\e]12;red\a' OBSERVED RESULT Cursor color doesn't change with any Appearence>Cursor settings, unlike in xterm or libvte-based terminals (gnome-terminal, xfce4-terminal, terminator). EXPECTED RESULT The cursor color changes the same way as in xterm and libvte. SOFTWARE/OS VERSIONS Linux/KDE Plasma: EndeavourOS KDE Plasma Version: 6.1.0 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.1 ADDITIONAL INFORMATION My use case is I want to change neovim cursor color depending on the mode. I don't care about OSC 110 and 111 support, but this seems adjacent enough to include it in this issue. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 488905] Feature request: OSC 12 support (Change text cursor color)
https://bugs.kde.org/show_bug.cgi?id=488905 --- Comment #1 from Maxim --- Created attachment 170762 --> https://bugs.kde.org/attachment.cgi?id=170762&action=edit xterm, xfce4-terminal, terminator and Konsole -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 488905] Feature request: OSC 12 support (Change text cursor color)
https://bugs.kde.org/show_bug.cgi?id=488905 --- Comment #2 from Maxim --- The closest thing I found to the documentation is the "XTerm Control Sequences" pdf file: https://invisible-island.net/xterm/ctlseqs/ctlseqs.pdf, pages 34-36. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 489230] New: Excessive amount of _NET_DESKTOP_GEOMETRY PropertyChange slow down the entire Xorg
https://bugs.kde.org/show_bug.cgi?id=489230 Bug ID: 489230 Summary: Excessive amount of _NET_DESKTOP_GEOMETRY PropertyChange slow down the entire Xorg Classification: Plasma Product: kwin Version: git-stable-Plasma/6.1 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: platform-x11-standalone Assignee: kwin-bugs-n...@kde.org Reporter: maxim.kartas...@jetbrains.com Target Milestone: --- Created attachment 171011 --> https://bugs.kde.org/attachment.cgi?id=171011&action=edit A C program that illustrates the bug SUMMARY Starting with Plasma 6.0.3, Java-based IntelliJ IDEs may slow down the entire X session making various elements feel sluggish or unresponsive. The issue has been traced down to the generation of a huge amount of PropertyChange events for the `_NET_DESKTOP_GEOMETRY` property (https://specifications.freedesktop.org/wm-spec/1.3/ar01s03.html) when starting to drag a file from any file manager (Gnome Files in my case). This can be seen on a simple X11 application found below. Note that the application itself is not enough to reproduce the sluggishness as it does not react to `_NET_DESKTOP_GEOMETRY` change in the same heavy-weight manner as intelliJ IDEs do. The bug was reported by multiple users here: https://youtrack.jetbrains.com/issue/JBR-6830 STEPS TO REPRODUCE 1. Log in to a Plasma X11 desktop 2. Download PyCharm Community Edition (or any other IntelliJ IDE) https://www.jetbrains.com/pycharm/download/?section=linux 3. Run PyCharm and create an empty project 4. Open any graphical file manager 5. Start dragging a file from that file manager over PyCharm's window 6. Note how the dragged file lags behind the mouse pointer; Xorg process is at 100% CPU at this point. 7. Exit PyCharm, wait a couple of seconds 8. Start dragging a file from a file manager again 9. Note how smooth dragging is now Alternatively, compile (`gcc -lX11 test.c`) and run the C program attached. Once executed, start dragging a file from a file manager and observe the amount of messages printed to stdout of that program. Since the actual desktop geometry (its width and height in pixels) is the same throughout the lifetime of the application, there should not be any such events at all. OBSERVED RESULT Sluggish drag and lots of `Property _NET_DESKTOP_GEOMETRY changed` messages. EXPECTED RESULT Smooth drag and one or no `Property _NET_DESKTOP_GEOMETRY changed` messages. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 40 (available in About System) KDE Plasma Version: 6.1.0 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.1 ADDITIONAL INFORMATION Also reproduces with 6.0.3 and on other Linux distros such as Arch. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483020] New: Artifacts when starting KDE (Wayland) after entering the password in SDDM
https://bugs.kde.org/show_bug.cgi?id=483020 Bug ID: 483020 Summary: Artifacts when starting KDE (Wayland) after entering the password in SDDM Classification: Plasma Product: kwin Version: 6.0.1 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: mxtyul...@gmail.com Target Milestone: --- STEPS TO REPRODUCE 1. Load system 2. Enter password in SDDM OBSERVED RESULT Artifacts in the form of white squares appear for a second. EXPECTED RESULT Normal loading to desktop, without artifacts SOFTWARE/OS VERSIONS Linux: Arch Linux (Linux LTS 6.6.21-1) KDE Plasma Version: KDE Plasma 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION мар 09 18:34:59 archlinux sddm-helper[574]: Starting Wayland user session: "/usr/share/sddm/scripts/wayland-session" "/usr/lib/plasma-dbus-run-session-if-needed /usr/bin/startplasma-wayland" мар 09 18:35:04 archlinux kwin_wayland[657]: No backend specified, automatically choosing drm мар 09 18:35:04 archlinux kwin_wayland[657]: kwin_wayland_drm: drmSetClientCap for Atomic Mode Setting failed. Using legacy mode on GPU "/dev/dri/card1" мар 09 18:35:05 archlinux kwin_wayland[657]: OpenGL vendor string: AMD мар 09 18:35:05 archlinux kwin_wayland[657]: OpenGL renderer string: AMD Radeon R2 Graphics (radeonsi, kabini, LLVM 17.0.6, DRM 3.54, 6.6.21-1-lts) мар 09 18:35:05 archlinux kwin_wayland[657]: OpenGL version string: 4.6 (Core Profile) Mesa 24.0.2-arch1.2 мар 09 18:35:05 archlinux kwin_wayland[657]: OpenGL shading language version string: 4.60 мар 09 18:35:05 archlinux kwin_wayland[657]: Driver: Unknown мар 09 18:35:05 archlinux kwin_wayland[657]: GPU class: Unknown мар 09 18:35:05 archlinux kwin_wayland[657]: OpenGL version: 4.6 мар 09 18:35:05 archlinux kwin_wayland[657]: GLSL version: 4.60 мар 09 18:35:05 archlinux kwin_wayland[657]: Mesa version: 24.0.2 мар 09 18:35:05 archlinux kwin_wayland[657]: Requires strict binding: no мар 09 18:35:05 archlinux kwin_wayland[657]: Virtual Machine: no мар 09 18:35:05 archlinux kwin_wayland[657]: Timer query support: yes -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 446654] Feature Request: mirror a panel on all monitors
https://bugs.kde.org/show_bug.cgi?id=446654 Maxim changed: What|Removed |Added CC||maxim.kukush...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483826] New: Feature Request: Option to never switch to icon-only
https://bugs.kde.org/show_bug.cgi?id=483826 Bug ID: 483826 Summary: Feature Request: Option to never switch to icon-only Classification: Plasma Product: plasmashell Version: 6.0.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Task Manager and Icons-Only Task Manager Assignee: plasma-b...@kde.org Reporter: maxim.kukush...@gmail.com CC: qydwhotm...@gmail.com Target Milestone: 1.0 SUMMARY Despite using `Task Manager` widget to show icons with window titles, it still defaults to icon-only view when many windows are opened. Could we please have a configurable threshold to switch between icon+titles and icon-only views or a setting to disable the icon-only view? STEPS TO REPRODUCE 1. Create a `Task Manager` widget 2. Open 10-15 windows OBSERVED RESULT Titles are hidden in the Task Manager and icon-only view is used EXPECTED RESULT Titles are shown no matter what, because it's a user preference. (I do actually prefer an icon with even one letter shown than icons only). Could we please have a configurable threshold to switch between icon+titles and icon-only views or a setting to disable the icon-only view? SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux (available in About System) KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 446192] New: Slide swithcing
https://bugs.kde.org/show_bug.cgi?id=446192 Bug ID: 446192 Summary: Slide swithcing Product: kdeconnect Version: unspecified Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: android-application Assignee: albertv...@gmail.com Reporter: mkradoz...@gmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Switching slides with volume keys on the locked screen (Does not work) 2. Switching slides with the volume keys with the screen on (Works) OBSERVED RESULT Nothing EXPECTED RESULT switch slides SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro (available in About System) KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Lock screen slide switch doesn't work on android 12, but worked on earlier versions -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 446192] Slide swithcing
https://bugs.kde.org/show_bug.cgi?id=446192 --- Comment #1 from Maxim --- On Android 7 does not working too. Maybe the problem is due to the distribution -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 454276] New: Some IPC syscalls is missing for x86 linux
https://bugs.kde.org/show_bug.cgi?id=454276 Bug ID: 454276 Summary: Some IPC syscalls is missing for x86 linux Product: valgrind Version: 3.19.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: jsew...@acm.org Reporter: mussitantesmor...@gmail.com Target Milestone: --- Created attachment 149138 --> https://bugs.kde.org/attachment.cgi?id=149138&action=edit Possible fix SUMMARY New separate IPC syscalls is missing in syscall_table for x86 linux: * semget * semctl * shmget * shmctl * shmat * shmdt * msgget * msgsnd * msgrcv * msgctl STEPS TO REPRODUCE 1. Try to call some of syscalls above on kernel i386 >5.1 with actual uapi headers OBSERVED RESULT Gets ENOSYS EXPECTED RESULT Syscalls should work =) SOFTWARE/OS VERSIONS i386 Linux with uclibc-ng libc ADDITIONAL INFORMATION This issue can be fixed by followed patch: -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 455839] New: Audio traffic does not work in Crete. I add music in animation mode, I try to launch, but there is no sound and the animation itself ceases to work because of this. There is
https://bugs.kde.org/show_bug.cgi?id=455839 Bug ID: 455839 Summary: Audio traffic does not work in Crete. I add music in animation mode, I try to launch, but there is no sound and the animation itself ceases to work because of this. There is no such problem in the PC version. Product: krita Version: unspecified Platform: Android OS: Android 10.x Status: REPORTED Severity: crash Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: mccloudjeffer...@gmail.com Target Milestone: --- Audio traffic does not work in Crete. I add music in animation mode, I try to launch, but there is no sound and the animation itself ceases to work because of this. There is no such problem in the PC version. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 445039] New: ksystemstats constantly (3-4 times a second) accessing disk but doing nothing.
https://bugs.kde.org/show_bug.cgi?id=445039 Bug ID: 445039 Summary: ksystemstats constantly (3-4 times a second) accessing disk but doing nothing. Product: plasma-systemmonitor Version: 5.22.5 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: ma...@damage.nl CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- SUMMARY ksystemstats continuously accessing my drive at ~1,7% but zero % writes or reads. Disk light flickers 3-4 times a second non stop. STEPS TO REPRODUCE 1. Just a clean install Kubuntu 21.10 2. 3. OBSERVED RESULT When Idle, disk light flickers 3-4 times every second, iostat -0 says only ksystemstats is doing this, and mostly actually the only thing actively accessing the disk. EXPECTED RESULT (observed after removing ksystemstats) Disk light flickers like once every 5-15 seconds when idle SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 21.10 KDE Plasma Version: 5.22.5 (came default with it) KDE Frameworks Version: 5.86.0 (came default with it) Qt Version: 5.15.2 ADDITIONAL INFORMATION Can not kill the process ksystemstats, so had to uninstall it. Then the problem is solved. After reinstalling it, the problem came back. For now i removed it, but looks like a crucial part for Kubuntu. Hardware: DeskMini X300 Series with cpu: AMD Ryzen 7 PRO 4750G with Radeon Graphics storage: Micron/Crucial Non-Volatile memory controller network: enp2s0 Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller disk: /dev/nvme0n1 Micron/Crucial Disk partition: /dev/nvme0n1p1 Partition /dev/nvme0n1p2 Partition memory: Main Memory, 32GB -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 398584] Proxy settings not effective
https://bugs.kde.org/show_bug.cgi?id=398584 Maxim changed: What|Removed |Added Status|RESOLVED|REPORTED Resolution|WORKSFORME |--- --- Comment #9 from Maxim --- (In reply to Justin Zobel from comment #6) > (In reply to Maxim from comment #5) > > On Manjaro KDE `Linux 5.8.18-1-MANJARO x86_64`. > > Firefox does not receive proxy settings by default. Chrome gets success. > > Did you add the settings to your .profile file? I didn't add anything for the proxy. The .profile file did not change. In the .bashrc file added only settings for git, phpbrew, and created a little alias to quickly run commands. -- You are receiving this mail because: You are watching all bug changes.
[kiofuse] [Bug 428141] New: kiofuse dont work with mtp
https://bugs.kde.org/show_bug.cgi?id=428141 Bug ID: 428141 Summary: kiofuse dont work with mtp Product: kiofuse Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: a.saout...@gmail.com Reporter: maxim3...@gmail.com Target Milestone: --- Created attachment 132661 --> https://bugs.kde.org/attachment.cgi?id=132661&action=edit Text file opened on mtp in not kde editor STEPS TO REPRODUCE 1. Connect phone with any text file on it 2. Open mtp folder 3. Open text file in any gtk editor (geany for example) OBSERVED RESULT kiofuse not used (result on screenshot) Operating System: KDE neon 5.20 KDE Plasma Version: 5.20.1 KDE Frameworks Version: 5.76.0 Qt Version: 5.15.0 Kernel Version: 5.4.0-52-generic OS Type: 64-bit Processors: 4 × Intel® Core™ i3-4030U CPU @ 1.90GHz Memory: 11.6 ГиБ of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 4400 kio-fuse/focal,now 0.0+p20.04+git20200602.2259-0 amd64 [установлен] installed kde neon user edition and changed repo to testing cat /etc/apt/sources.list.d/neon.list deb http://archive.neon.kde.org/testing focal main deb-src http://archive.neon.kde.org/testing focal main -- You are receiving this mail because: You are watching all bug changes.
[kiofuse] [Bug 428141] kiofuse dont work with mtp
https://bugs.kde.org/show_bug.cgi?id=428141 Maxim changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WORKSFORME |LATER --- Comment #2 from Maxim --- Sorry, please close this bug report. I did not read https://invent.kde.org/system/kio-fuse/-/issues/2 -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 358716] Occasional loss of GUI layout settings after system restart
https://bugs.kde.org/show_bug.cgi?id=358716 Maxim changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED --- Comment #7 from Maxim --- (In reply to Justin Zobel from comment #6) > Thanks for the report Maxim, how often is this happening, is there anything > that you do before that you can recall when this issue happens? Oh, I already forgot about this... :) Thanks for the answer, Justin! I've tested this on openSUSE 15.2 with: - Qt 5.12.7 - Plasma 5.18.5 - Frameworks 5.71.0 - Applications 20.04.2 - Akregator 5.14.2 It seems everything is fine, so I guess this was fixed a long time ago. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 472470] New: Audio
https://bugs.kde.org/show_bug.cgi?id=472470 Bug ID: 472470 Summary: Audio Classification: Applications Product: krita Version: unspecified Platform: Other OS: Android 10.x Status: REPORTED Severity: normal Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: mccloudjeffer...@gmail.com Target Milestone: --- Dear developers. Thank you so much for updating the audio track in Krita! Finally, the music is working! But there is a small problem. The audio does not start over when the animation is played. Even with a full return to the first frame, the music continues to play at the place where it stopped. It's not critical, but inconvenient. Thank you for your hard work! You are the best! 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.
[xdg-desktop-portal-kde] [Bug 431514] New: GTK_FILE_CHOOSER_ACTION_SELECT_FOLDER is not supported by GtkFileChooserNativePortal because portal is too old
https://bugs.kde.org/show_bug.cgi?id=431514 Bug ID: 431514 Summary: GTK_FILE_CHOOSER_ACTION_SELECT_FOLDER is not supported by GtkFileChooserNativePortal because portal is too old Product: xdg-desktop-portal-kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: jgrul...@redhat.com Reporter: maxim3...@gmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. open thunderbird with "GTK_USE_PORTAL=1 thunderbird" 2. Open any email with two or more attachments 3. Press save all attachments OBSERVED RESULT GTK file dialog appeared EXPECTED RESULT KDE file dialog appeared Operating System: KDE neon Testing Edition KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 Kernel Version: 5.4.0-60-generic OS Type: 64-bit installed packages xdg-desktop-portal 1.6.0-1 xdg-desktop-portal-gtk 1.6.0-1build1 xdg-desktop-portal-kde 5.20.5+p20.04+git20210112.0018-0 Thunderbird 68.10.0 -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 431514] GTK_FILE_CHOOSER_ACTION_SELECT_FOLDER is not supported by GtkFileChooserNativePortal because portal is too old
https://bugs.kde.org/show_bug.cgi?id=431514 --- Comment #1 from Maxim --- bug title - its error when I launch thunderbird from terminal -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 431514] GTK_FILE_CHOOSER_ACTION_SELECT_FOLDER is not supported by GtkFileChooserNativePortal because portal is too old
https://bugs.kde.org/show_bug.cgi?id=431514
--- Comment #3 from Maxim ---
(In reply to Nate Graham from comment #2)
> What do you mean by "because portal is too old?"
It is error which i see in terminal
maxim@oit3-notebook:~$ GTK_USE_PORTAL=1 thunderbird
WINDOW DECORATIONS RELOADED
console.log: WebExtensions: Loading packed extension from
/home/maxim/.thunderbird/bgtede5y.default-release/extensions/{a62ef8ec-5fdc-40c2-873c-223b8a6925cc}.xpi
console.log: WebExtensions: Loading packed extension from
/home/maxim/.thunderbird/bgtede5y.default-release/extensions/{e2fda1a4-762b-4020-b5ad-a41df1933103}.xpi
console.log: WebExtensions: Loading add-on preferences from
/home/maxim/.thunderbird/bgtede5y.default-release/extensions/{a62ef8ec-5fdc-40c2-873c-223b8a6925cc}.xpi
console.log: WebExtensions: Firing profile-after-change listeners for
{a62ef8ec-5fdc-40c2-873c-223b8a6925cc}
console.log: WebExtensions: Loading add-on preferences from
/home/maxim/.thunderbird/bgtede5y.default-release/extensions/{e2fda1a4-762b-4020-b5ad-a41df1933103}.xpi
console.log: WebExtensions: Firing profile-after-change listeners for
{e2fda1a4-762b-4020-b5ad-a41df1933103}
[calBackendLoader] Using Thunderbird's builtin libical backend
console.warn: Overlays.jsm: Could not resolve 1 references Array [{}]
1610520173361 addons.xpi WARNCan't get modified time of
/usr/lib/thunderbird/features/wetrans...@extensions.thunderbird.net
(thunderbird:8207): Gtk-WARNING **: 09:42:59.884:
GTK_FILE_CHOOSER_ACTION_SELECT_FOLDER is not supported by
GtkFileChooserNativePortal because portal is too old
--
You are receiving this mail because:
You are watching all bug changes.
[ksysguard] [Bug 423382] New: KSysGuard crashes sometimes when closed
https://bugs.kde.org/show_bug.cgi?id=423382 Bug ID: 423382 Summary: KSysGuard crashes sometimes when closed Product: ksysguard Version: 5.19.1 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: darkcac...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- Application: ksysguard (5.19.1) Qt Version: 5.14.2 Frameworks Version: 5.71.0 Operating System: Linux 5.3.0-59-generic x86_64 Windowing system: X11 Distribution: KDE neon User Edition 5.19 -- Information about the crash: Operating System: KDE neon 5.19 KDE Plasma Version: 5.19.1 KDE Frameworks Version: 5.71.0 Qt Version: 5.14.2 Kernel Version: 5.3.0-59-generic OS Type: 64-bit Processors: 8 × Intel® Core™ i7-6700HQ CPU @ 2.60GHz Memory: 11,4 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 530 The crash can be reproduced sometimes. -- Backtrace: Application: System Monitor (ksysguard), signal: Segmentation fault [KCrash Handler] #4 0x7f6d9a21d9e9 in QLabelPrivate::clearContents() (this=this@entry=0x5597d8b2b740) at widgets/qlabel.cpp:1308 #5 0x7f6d9a21e54a in QLabel::setText(QString const&) (this=0x5597d8b00dc0, text=...) at widgets/qlabel.cpp:293 #6 0x7f6d9d5ce170 in TopLevel::answerReceived(int, QList const&) (this=0x5597d8b335b0, id=, answerList=...) at ./gui/ksysguard.cpp:466 #7 0x7f6d9cd03b8a in KSGRD::SensorAgent::processAnswer(char const*, int) () at /usr/lib/x86_64-linux-gnu/libksgrd.so.9 #8 0x7f6d9cd0ae24 in () at /usr/lib/x86_64-linux-gnu/libksgrd.so.9 #9 0x7f6d98aa06d7 in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x7fff8ee12010, r=0x5597d8c26920, this=) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #10 0x7f6d98aa06d7 in doActivate(QObject*, int, void**) (sender=0x5597d8ba5dd0, signal_index=15, argv=0x7fff8ee12010) at kernel/qobject.cpp:3870 #11 0x7f6d98a9af92 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=sender@entry=0x5597d8ba5dd0, m=m@entry=0x7f6d98f317c0 , local_signal_index=local_signal_index@entry=6, argv=argv@entry=0x7fff8ee12010) at kernel/qobject.cpp:3930 #12 0x7f6d989d38da in QProcess::readyReadStandardOutput(QProcess::QPrivateSignal) (this=this@entry=0x5597d8ba5dd0, _t1=...) at .moc/moc_qprocess.cpp:367 #13 0x7f6d989da131 in QProcessPrivate::tryReadFromChannel(QProcessPrivate::Channel*) (this=0x5597d8b33340, channel=0x5597d8b33450) at io/qprocess.cpp:1073 #14 0x7f6d989da600 in QProcessPrivate::_q_canReadStandardOutput() (this=) at io/qprocess.cpp:1084 #15 0x7f6d989da600 in QProcess::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) (_o=, _c=, _id=, _a=0x7fff8ee121c0) at .moc/moc_qprocess.cpp:208 #16 0x7f6d98aa04b9 in doActivate(QObject*, int, void**) (sender=0x5597d8bf99a0, signal_index=3, argv=0x7fff8ee121c0) at kernel/qobject.cpp:3882 #17 0x7f6d98a9af92 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=sender@entry=0x5597d8bf99a0, m=m@entry=0x7f6d98f33ba0 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7fff8ee121c0) at kernel/qobject.cpp:3930 #18 0x7f6d98aa3cb8 in QSocketNotifier::activated(int, QSocketNotifier::QPrivateSignal) (this=this@entry=0x5597d8bf99a0, _t1=, _t2=...) at .moc/moc_qsocketnotifier.cpp:141 #19 0x7f6d98aa4072 in QSocketNotifier::event(QEvent*) (this=0x5597d8bf99a0, e=0x7fff8ee12490) at kernel/qsocketnotifier.cpp:266 #20 0x7f6d9a0ea9ac in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=this@entry=0x5597d8749700, receiver=receiver@entry=0x5597d8bf99a0, e=e@entry=0x7fff8ee12490) at kernel/qapplication.cpp:3685 #21 0x7f6d9a0f1bb0 in QApplication::notify(QObject*, QEvent*) (this=0x7fff8ee12780, receiver=0x5597d8bf99a0, e=0x7fff8ee12490) at kernel/qapplication.cpp:3431 #22 0x7f6d98a654a8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=0x5597d8bf99a0, event=0x7fff8ee12490) at kernel/qcoreapplication.cpp:1075 #23 0x7f6d98a6567e in QCoreApplication::sendEvent(QObject*, QEvent*) (receiver=, event=event@entry=0x7fff8ee12490) at kernel/qcoreapplication.cpp:1470 #24 0x7f6d98ac5378 in socketNotifierSourceDispatch(GSource*, GSourceFunc, gpointer) (source=0x5597d87547e0) at kernel/qeventdispatcher_glib.cpp:107 #25 0x7f6d8a349417 in g_main_context_dispatch () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #26 0x7f6d8a349650 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #27 0x7f6d8a3496dc in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #28 0x7f6d98ac47ac in QEventDispatcherGlib::processEvents(QFlags) (this=0x5597d8797100, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #29 0x7f6d98a63d2a in QEventLoop::exec(QFlags) (this=this@entry=0x7fff8ee126b0,
[gwenview] [Bug 423547] New: Cannot open kra file, saved with Krita 4.3.0
https://bugs.kde.org/show_bug.cgi?id=423547 Bug ID: 423547 Summary: Cannot open kra file, saved with Krita 4.3.0 Product: gwenview Version: 19.04.3 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: maxim.shero...@gmail.com Target Milestone: --- SUMMARY Gwenview cannot display content of kra file, that was saved with recent Krita version 4.3.0. STEPS TO REPRODUCE 1. Create a file with Krita 4.3.0 2. Try to open it with Gwenview OBSERVED RESULT Shows error: Loading ‘FileName.kra’ failed Loading meta information failed. EXPECTED RESULT File opens and shows content as regular image file SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Kubuntu 19.10 (available in About System) KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.4 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 423382] KSysGuard crashes sometimes when closed
https://bugs.kde.org/show_bug.cgi?id=423382 Maxim changed: What|Removed |Added Version|5.19.1 |5.19.3 -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 423382] KSysGuard crashes sometimes when closed
https://bugs.kde.org/show_bug.cgi?id=423382 Maxim changed: What|Removed |Added CC||darkcac...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 398584] Proxy settings not effective
https://bugs.kde.org/show_bug.cgi?id=398584 Maxim changed: What|Removed |Added CC||maximmand...@gmail.com --- Comment #5 from Maxim --- On Manjaro KDE `Linux 5.8.18-1-MANJARO x86_64`. Firefox does not receive proxy settings by default. Chrome gets success. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 430304] "Open With" for remote files missing in context menu
https://bugs.kde.org/show_bug.cgi?id=430304 Maxim changed: What|Removed |Added CC||maxim3...@gmail.com --- Comment #1 from Maxim --- I work with remote files in dolphin often and for me it is critical bug. https://bugs.kde.org/show_bug.cgi?id=430293 has workaround - you can create service menus, but this bug has no workaround. Why it is critical - for example I have html file. I need to have possibility open it in browser and edit it in Kate for example. Now - i cant do it. Krusader as interesting - not affects this bug. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 430293] "Open With" for folders missing in context menu
https://bugs.kde.org/show_bug.cgi?id=430293 Maxim changed: What|Removed |Added CC||maxim3...@gmail.com --- Comment #8 from Maxim --- (In reply to Nate Graham from comment #3) > I believe this was an intentional change, to reduce the humongous length of > the context menu. On my setup, the only item in the "Open With" menu was > Gwenview, which was redundant with the fileitemaction plugin. I guess you > have Konqueror in yours. > > I can understand that from your perspective this is a regression, but isn't > it a pretty niche use case to use Dolphin to open a location in Konqueror? > > We gotta keep the context menu's size reasonable somehow... :( A little question - https://bugs.kde.org/show_bug.cgi?id=430304 possibly is also intentional change or a real bug? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 398446] FUSE-mounted remote locations accessed with a KIO-using app are not visible in non-KDE open/save dialog
https://bugs.kde.org/show_bug.cgi?id=398446 Maxim changed: What|Removed |Added CC||maxim3...@gmail.com --- Comment #8 from Maxim --- (In reply to Kyle Tirak from comment #7) > It sounds like one unfortunate effect of this will be an inability for > browsers like Firefox to directly save downloads to the smb share. With firefox you can use gtk_use_portal option or use firefox from opensuse. In both cases - you got kde file dialogs/ -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 493195] Automatically clone panel when connecting a new display
https://bugs.kde.org/show_bug.cgi?id=493195 Maxim changed: What|Removed |Added CC||maxim.kukush...@gmail.com --- Comment #1 from Maxim --- I would add that this needs to be configurable in the panel settings - whether it's expected to be cloned or not Also, the algorithm can be "clone if the monitor doesn't have any panels" in case it's hard to backtrack the link between an already existing panel and its origin -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 446654] Feature Request: mirror a panel on all monitors
https://bugs.kde.org/show_bug.cgi?id=446654 --- Comment #43 from Maxim --- (In reply to Niccolò Venerandi from comment #42) > After some investigation, I believe that the technical implementation of > this is de-facto impossible; however, a very similar feature - the ability > to clone a panel from a monitor to another - was implemented, and thus I'm > closing this as wontfix. > > To elaborate, it's already quite complex to have two different panels who > should follow the same set of settings (a major rewrite would be needed for > that); but, on top of that, monitors can have different sizes and thus the > same panel should have to be mirrored with different looks on different > panels, potentially interfering with the settings. There would be a lot of > combinations possible, and I believe they would be prone to breakage. Could you please elaborate a bit more on the panel cloning? Last time I tried to do this I found it quite complicated. Basically there were no controls to clone a panel and the panels are not stored anywhere in a simple format on a filesystem, so that it could be somehow automated Given the amount of comments in this feature request and points that it's big UI experience downgrade when coming from other platforms, this feature needs to be implemented in one way or another. Even if a panel can be cloned with several clicks, it's still quite cumbersome to do, especially when we're talking about laptops which can be attached to all sorts of monitors and projectors in meeting rooms. Imagine doing this 3-4 times per day, for people who often need to present in different locations. I think when people talk about mirroring a panel, it doesn't mean mirror pixel-by-pixel. It's about the set of widgets and their settings which is hardest to do manually. That aspect doesn't depend on monitor's resolution. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 446654] Feature Request: mirror a panel on all monitors
https://bugs.kde.org/show_bug.cgi?id=446654 --- Comment #44 from Maxim --- btw, if there's already an option/code to clone an existing panel, why can't this Feature Request be implemented in form of automatically triggering that "clone" feature when a new monitor is added in case doesn't have any panel yet? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 446654] Feature Request: mirror a panel on all monitors
https://bugs.kde.org/show_bug.cgi?id=446654 --- Comment #47 from Maxim --- > This could be done, but I'm a bit worried about the consequences it might > have. What if the user has multiple panels? Should we always clone *all* > panels from one screen to another? Is that what the user really expects when > connecting to a new monitor? Not always, I think the original idea was to have a setting for a panel to indicate that it's expected to be mirrored. So the algorithm in the first iteration could be: - when a monitor is connected - for each panel - does it have the "mirror" flag set? (no by default) - if not, do nothing - does the new monitor already have panels? - if yes, do nothing - otherwise, clone the panel The last bit can be modified, depending on what information is available internally. The main idea is to prevent cloning panels endlessly on each connect of the same monitor. I don't know if it's possible to mark a panel as a clone of another one in its metadata (like an ID) to be checked more precisely. However, imho, it would already be a major improvement -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 489898] New: Bug/Enhancement: Use PAM failed login timeout or allow its configuration
https://bugs.kde.org/show_bug.cgi?id=489898 Bug ID: 489898 Summary: Bug/Enhancement: Use PAM failed login timeout or allow its configuration Classification: Plasma Product: kscreenlocker Version: 6.1.2 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: maxim.kukush...@gmail.com Target Milestone: --- SUMMARY Despite PAM configuration for not having a delay for failed logins (which is normal for local machines with no sensitive data), kscreenlocker still imposes a hardcoded ~3s timeout after entering incorrect password STEPS TO REPRODUCE 1. Configure PAM with `nodelay` setting (specifically for pam_unix.so and pam_faillock.so) 2. Make sure the settings have been applied by trying an incorrect login in TTY 1-6 3. Lock the screen in KDE 6.1 4. Enter incorrect password OBSERVED RESULT There's a ~3s delay before the user is allowed to retry EXPECTED RESULT The next attempt must be allowed immediately as per the PAM settings SOFTWARE/OS VERSIONS Linux/KDE (available in About System) KDE Plasma Version: 6.1.2 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.2 ADDITIONAL INFORMATION Having no delay between login attempts is user's choice that must be respected (not all machines contain sensitive data, some of them can be temporary virtual machines or some local devices that no one will ever bruteforce, or they are not critical even if compromised - it's admin's decision). PAM allow this setting, so should kscreenlocker. kscreenlocker must either respect PAM's settings or expose its own setting for the failed login timeout so that the administrator can configure it. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 408463] New: only ftp
https://bugs.kde.org/show_bug.cgi?id=408463 Bug ID: 408463 Summary: only ftp Product: krusader Version: unspecified Platform: Mint (Ubuntu based) OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: net-connection Assignee: krusader-bugs-n...@kde.org Reporter: maxsmart3...@mail.ru CC: krusader-bugs-n...@kde.org Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Tools -> Net Connection 2. I can choose only ftp protocol for connection, no sftp nor the other ones 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 406180] KWin 5.15.4+ hang regression on Nvidia Optimus
https://bugs.kde.org/show_bug.cgi?id=406180 --- Comment #70 from Maxim --- Will it fix in 5.16 version of KDE plasma? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 408578] New: Turn off touchpad
https://bugs.kde.org/show_bug.cgi?id=408578 Bug ID: 408578 Summary: Turn off touchpad Product: systemsettings Version: 5.16.0 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: darkcac...@gmail.com Target Milestone: --- Application: systemsettings5 (5.16.0) Qt Version: 5.12.3 Frameworks Version: 5.59.0 Operating System: Linux 4.18.0-21-generic x86_64 Distribution: KDE neon User Edition 5.16 -- Information about the crash: - What I was doing when the application crashed: Turned off touchpad in wayland session, then settings is crashed. -- Backtrace: Application: Параметры системы (systemsettings5), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fdc6492e680 (LWP 6322))] Thread 5 (Thread 0x7fdbfaf31700 (LWP 6863)): #0 0x7fdc5fea7bf9 in __GI___poll (fds=0x55fa1cf0bb00, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fdc58f084c9 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fdc58f08862 in g_main_loop_run () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fdc0025d026 in () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #4 0x7fdc58f2ff15 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fdc5b2c66db in start_thread (arg=0x7fdbfaf31700) at pthread_create.c:463 #6 0x7fdc5feb488f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7fdbfb732700 (LWP 6862)): #0 0x7fdc5fea7bf9 in __GI___poll (fds=0x55fa15d97a10, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fdc58f084c9 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fdc58f085dc in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fdc58f08621 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fdc58f2ff15 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fdc5b2c66db in start_thread (arg=0x7fdbfb732700) at pthread_create.c:463 #6 0x7fdc5feb488f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7fdc03fff700 (LWP 6859)): #0 0x7fdc5fea7bf9 in __GI___poll (fds=0x7fdbfc077100, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fdc58f084c9 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fdc58f085dc in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fdc607eadcb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fdc6078c03a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fdc605b34ca in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fdc5e369115 in () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7fdc605b4c72 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fdc5b2c66db in start_thread (arg=0x7fdc03fff700) at pthread_create.c:463 #9 0x7fdc5feb488f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7fdc4f801700 (LWP 6324)): #0 0x7fdc5fea30b4 in __GI___libc_read (fd=5, buf=0x7fdc4f800b20, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7fdc58f4d000 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fdc58f07fb7 in g_main_context_check () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fdc58f08470 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fdc58f085dc in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fdc607eadcb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fdc6078c03a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fdc605b34ca in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fdc60c59015 in () at /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #9 0x7fdc605b4c72 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7fdc5b2c66db in start_thread (arg=0x7fdc4f801700) at pthread_create.c:463 #11 0x7fdc5feb488f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7fdc6492e680 (LWP 6322)): [KCrash Handler] #6 0x7fdc5338aaa9 in () at /usr/lib/x86_64-linux-gnu/libwayland-client.so.0 #7 0x7fdc533868d3 in wl_proxy_destroy () at /usr/lib/x86_64-linux-gnu/libwayland-client.so.0 #8 0x7fdc51e75e57 in KWayland::Client::PlasmaWindow::release() () at /usr/lib/x86_64-linux-gnu/libKF5WaylandClient.so.5 #9 0x7fdc51e75e7a in KWayland::Client::PlasmaWindow::~PlasmaWindow() () at /usr/lib/x86_64-linux-gnu/libKF5WaylandClient.so.5 #10 0x7fdc51e75f99 in KWayland::Client::PlasmaWindow::~Plasma
[kio-extras] [Bug 404652] thumbnail.so do no close while after thumbnails are generated
https://bugs.kde.org/show_bug.cgi?id=404652 Maxim changed: What|Removed |Added CC||darkcac...@gmail.com --- Comment #2 from Maxim --- I can confirm itI have the same issue Because of these processes, Xorg begins to weigh more SOFTWARE/OS VERSIONS Operating System: KDE neon 5.16 KDE Plasma Version: 5.16.1 KDE Frameworks Version: 5.59.0 Qt Version: 5.12.3 Kernel Version: 4.18.0-21-generic OS Type: 64-bit Processors: 8 × Intel® Core™ i7-6700HQ CPU @ 2.60GHz Memory: 11,4 ГиБ -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 404652] thumbnail.so do no close while after thumbnails are generated
https://bugs.kde.org/show_bug.cgi?id=404652 Maxim changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #3 from Maxim --- It turned out that this is due to the fact that thumbnail.so cannot display a thumbnail for the djvu file. Decision: Install the djvulibre-bin package -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406180] KWin 5.15.4+ hang regression on Nvidia Optimus
https://bugs.kde.org/show_bug.cgi?id=406180 Maxim changed: What|Removed |Added Status|RESOLVED|REPORTED Ever confirmed|1 |0 Resolution|FIXED |--- --- Comment #90 from Maxim --- I still have this error. Operating System: KDE neon 5.16 KDE Plasma Version: 5.16.2 KDE Frameworks Version: 5.59.0 Qt Version: 5.12.3 Kernel Version: 4.18.0-24-generic OS Type: 64-bit Processors: 8 × Intel® Core™ i7-6700HQ CPU @ 2.60GHz Memory: 11,4 GiB of RAM nvidia: 430.26 -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 409586] New: Falkon crushed when add folder for bookmarks
https://bugs.kde.org/show_bug.cgi?id=409586 Bug ID: 409586 Summary: Falkon crushed when add folder for bookmarks Product: Falkon Version: 3.1.0 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: now...@gmail.com Reporter: darkcac...@gmail.com Target Milestone: --- Application: falkon (3.1.0) Qt Version: 5.12.3 Frameworks Version: 5.59.0 Operating System: Linux 4.18.0-25-generic x86_64 Distribution: KDE neon User Edition 5.16 -- Information about the crash: - What I was doing when the application crashed: Falkon crushed when added folder for bookmarks in root directory The crash can be reproduced every time. -- Backtrace: Application: Falkon (falkon), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f0f616e0b80 (LWP 13114))] Thread 21 (Thread 0x7f0ebc9ae700 (LWP 13192)): #0 0x7f0f562249f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x7f0ebc9ad948) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x7f0ebc9ad8f8, cond=0x7f0ebc9ad920) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x7f0ebc9ad920, mutex=0x7f0ebc9ad8f8) at pthread_cond_wait.c:655 #3 0x7f0f59bf7a49 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f0f59bf8478 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f0f59bf850f in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f0f59bb8fc8 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f0f59bbb7f6 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7f0f5934 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7f0f59bfa561 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7f0f5621e6db in start_thread (arg=0x7f0ebc9ae700) at pthread_create.c:463 #11 0x7f0f5f93388f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 20 (Thread 0x7f0ebd1af700 (LWP 13191)): #0 0x7f0f5f933bb7 in epoll_wait (epfd=71, events=0x7f0eb4002010, maxevents=32, timeout=3) at ../sysdeps/unix/sysv/linux/epoll_wait.c:30 #1 0x7f0f52aab2c5 in ?? () from /usr/lib/x86_64-linux-gnu/libevent-2.1.so.6 #2 0x7f0f52aa1114 in event_base_loop () from /usr/lib/x86_64-linux-gnu/libevent-2.1.so.6 #3 0x7f0f59bfddb4 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f0f59b982db in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f0f59bca311 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f0f59bfa561 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f0f5621e6db in start_thread (arg=0x7f0ebd1af700) at pthread_create.c:463 #8 0x7f0f5f93388f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 19 (Thread 0x7f0ebe5bb700 (LWP 13174)): #0 0x7f0f5f926bf9 in __GI___poll (fds=0x7f0eb8003ce0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f0f54aae4c9 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f0f54aae5dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f0f60269dcb in QEventDispatcherGlib::processEvents (this=0x7f0eb8000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #4 0x7f0f6020b03a in QEventLoop::exec (this=this@entry=0x7f0ebe5baa20, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #5 0x7f0f600324ca in QThread::exec (this=) at thread/qthread.cpp:531 #6 0x7f0f60033c72 in QThreadPrivate::start (arg=0x563900bf3230) at thread/qthread_unix.cpp:361 #7 0x7f0f5621e6db in start_thread (arg=0x7f0ebe5bb700) at pthread_create.c:463 #8 0x7f0f5f93388f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 18 (Thread 0x7f0ec7fff700 (LWP 13170)): #0 0x7f0f5f926bf9 in __GI___poll (fds=0x7f0ec0004a10, nfds=1, timeout=10495) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f0f54aae4c9 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f0f54aae5dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f0f60269daf in QEventDispatcherGlib::processEvents (this=0x7f0ecb20, flags=...) at kernel/qeventdispatcher_glib.cpp:422 #4 0x7f0f6020b03a in QEventLoop::exec (this=this@entry=0x7f0ec7ffea20, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #5 0x7f0f600324ca in QThread::exec (this=) at thread/qthread.cpp:531 #6 0x7f0f60033c72 in QThreadPrivate::start (arg=0x563900b2dd80) at thread/qthread_unix.cpp:361 #7 0x7f0f5621e6db in start_thread (arg=0x7f0ec7fff700) at pthread_create.c:463 #8 0x7f0f5f93388f in clone () at .
[Falkon] [Bug 409586] Falkon crushed when added folder for bookmarks
https://bugs.kde.org/show_bug.cgi?id=409586 Maxim changed: What|Removed |Added Summary|Falkon crushed when add |Falkon crushed when added |folder for bookmarks|folder for bookmarks -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 412773] New: kwin crash after sleep
https://bugs.kde.org/show_bug.cgi?id=412773 Bug ID: 412773 Summary: kwin crash after sleep Product: kwin Version: 5.16.5 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: darkcac...@gmail.com Target Milestone: --- Application: kwin_x11 (5.16.5) Qt Version: 5.13.1 Frameworks Version: 5.62.0 Operating System: Linux 5.0.0-31-generic x86_64 Distribution: KDE neon User Edition 5.16 -- Information about the crash: - What I was doing when the application crashed: 1. Sleep mode 2. Awakening 3. Kwin crash Operating System: KDE neon 5.16 KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.13.1 Kernel Version: 5.0.0-31-generic OS Type: 64-bit Processors: 8 × Intel® Core™ i7-6700HQ CPU @ 2.60GHz Video card: nvidia 960m Memory: 11,4 GiB of RAM -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f788e5edd00 (LWP 2096))] Thread 6 (Thread 0x7f786cd2a700 (LWP 6262)): #0 0x7f7886eb09f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x5644c561a324) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f7886eb09f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x5644c561a2d0, cond=0x5644c561a2f8) at pthread_cond_wait.c:502 #2 0x7f7886eb09f3 in __pthread_cond_wait (cond=0x5644c561a2f8, mutex=0x5644c561a2d0) at pthread_cond_wait.c:655 #3 0x7f788b263b0b in QWaitConditionPrivate::wait(QDeadlineTimer) (deadline=..., this=0x5644c561a2d0) at thread/qwaitcondition_unix.cpp:146 #4 0x7f788b263b0b in QWaitCondition::wait(QMutex*, QDeadlineTimer) (this=, mutex=0x5644c5646b40, deadline=...) at thread/qwaitcondition_unix.cpp:225 #5 0x7f788b263e19 in QWaitCondition::wait(QMutex*, unsigned long) (this=0x5644c5646b48, mutex=0x5644c5646b40, time=) at thread/qwaitcondition_unix.cpp:208 #6 0x7f788603aec8 in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7f788603b2fa in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #8 0x7f788b25cb72 in QThreadPrivate::start(void*) (arg=0x5644c5646ac0) at thread/qthread_unix.cpp:360 #9 0x7f7886eaa6db in start_thread (arg=0x7f786cd2a700) at pthread_create.c:463 #10 0x7f788df6088f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7f785b07e700 (LWP 2341)): #0 0x7f7886eb09f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x7f788a468fb8) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f7886eb09f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x7f788a468f68, cond=0x7f788a468f90) at pthread_cond_wait.c:502 #2 0x7f7886eb09f3 in __pthread_cond_wait (cond=0x7f788a468f90, mutex=0x7f788a468f68) at pthread_cond_wait.c:655 #3 0x7f788a173874 in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #4 0x7f788a1738b9 in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #5 0x7f7886eaa6db in start_thread (arg=0x7f785b07e700) at pthread_create.c:463 #6 0x7f788df6088f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7f7867fff700 (LWP 2192)): #0 0x7f788b471e98 in QMetaObject::activate(QObject*, int, int, void**) (sender=sender@entry=0x7f785c000b20, signalOffset=3, local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x0) at kernel/qobject.cpp:3667 #1 0x7f788b472dd7 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=sender@entry=0x7f785c000b20, m=m@entry=0x7f788b8f7300 , local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x0) at kernel/qobject.cpp:3660 #2 0x7f788b43dc23 in QAbstractEventDispatcher::awake() (this=this@entry=0x7f785c000b20) at .moc/moc_qabstracteventdispatcher.cpp:149 #3 0x7f788b49cc87 in QEventDispatcherUNIX::processEvents(QFlags) (this=0x7f785c000b20, flags=...) at kernel/qeventdispatcher_unix.cpp:465 #4 0x7f788b43feaa in QEventLoop::exec(QFlags) (this=this@entry=0x7f7867ffed00, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #5 0x7f788b25b3ca in QThread::exec() (this=) at thread/qthread.cpp:531 #6 0x7f78858b5cb5 in () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7f788b25cb72 in QThreadPrivate::start(void*) (arg=0x5644c5183890) at thread/qthread_unix.cpp:360 #8 0x7f7886eaa6db in start_thread (arg=0x7f7867fff700) at pthread_create.c:463 #9 0x7f788df6088f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7f786ebd1700 (LWP 2117)): #0 0x7f788df53cf6 in __GI_ppoll (fds=fds@entry=0x7f786800bc28, nfds=nfds@entry=1, timeout=, timeout@entry=0x0, sigmask=sigmask@entry=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39 #1 0x7f788b49b6e1 in ppoll (__ss=, __timeout=, __nfds=, __fds=) at /us
[kdenlive] [Bug 406963] New: Removing the first key results in an error and it is impossible to move the first key.
https://bugs.kde.org/show_bug.cgi?id=406963 Bug ID: 406963 Summary: Removing the first key results in an error and it is impossible to move the first key. Product: kdenlive Version: 19.04.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: darkcac...@gmail.com Target Milestone: --- Created attachment 119666 --> https://bugs.kde.org/attachment.cgi?id=119666&action=edit Information for developer STEPS TO REPRODUCE 1. Put the transformation effect on data 2. Double click on alone key OBSERVED RESULT Crashes with segmentation fault EXPECTED RESULT The key will disappear or just will stay SOFTWARE/OS VERSIONS Operating System: KDE neon 5.15 KDE Plasma Version: 5.15.4 KDE Frameworks Version: 5.57.0 Qt Version: 5.12.0 Kernel Version: 4.18.0-18-generic OS Type: 64-bit Processors: 8 × Intel® Core™ i7-6700HQ CPU @ 2.60GHz Memory: 11,4 ГиБ -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406180] KWin 5.15.4 hang regression on Nvidia Optimus
https://bugs.kde.org/show_bug.cgi?id=406180 Maxim changed: What|Removed |Added CC||darkcac...@gmail.com --- Comment #26 from Maxim --- I have the same issue on my laptop with nvidia 960m. Al+tab, resize window when moving to the top edge of the screen are freezing. SOFTWARE/OS VERSIONS Operating System: KDE neon 5.15 KDE Plasma Version: 5.15.4 KDE Frameworks Version: 5.57.0 Qt Version: 5.12.0 Kernel Version: 4.18.0-18-generic OS Type: 64-bit Processors: 8 × Intel® Core™ i7-6700HQ CPU @ 2.60GHz Memory: 11,4 ГиБ -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 413659] Option "Open folders during drag operations" has no effect on folders panel
https://bugs.kde.org/show_bug.cgi?id=413659 Maxim changed: What|Removed |Added CC||darkcac...@gmail.com --- Comment #1 from Maxim --- I can't repeat it. Operating System: KDE neon 5.17 KDE Plasma Version: 5.17.4 KDE Frameworks Version: 5.65.0 Qt Version: 5.13.2 Kernel Version: 5.0.0-37-generic OS Type: 64-bit Processors: 8 × Intel® Core™ i7-6700HQ CPU @ 2.60GHz Memory: 11,4 GiB of RAM -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 372723] KDE restart
https://bugs.kde.org/show_bug.cgi?id=372723 --- Comment #4 from Maxim --- Thanks for you. Fix and response. пт, 31 янв. 2020 г., 19:20 Nate Graham : > https://bugs.kde.org/show_bug.cgi?id=372723 > > Nate Graham changed: > >What|Removed |Added > > > Status|REPORTED|RESOLVED > CC||n...@kde.org > Resolution|--- |FIXED > > --- Comment #3 from Nate Graham --- > No response and no new duplicates; assuming it was fixed long ago. > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 417067] New: Dolphin permissions error
https://bugs.kde.org/show_bug.cgi?id=417067 Bug ID: 417067 Summary: Dolphin permissions error Product: dolphin Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: ma...@disroot.org CC: kfm-de...@kde.org Target Milestone: --- SUMMARY Dolphin permissions error STEPS TO REPRODUCE 1. Copy files 2. create files 3. chenge acl permission for directory OBSERVED RESULT When copying files, Dolphin does not accept the permissions of the destination directory. when installed on a Sticky Byt directory, the ACL mask crashes in --- an attempt to recover from the GUI is ineffective only from under the console. EXPECTED RESULT This leads to the inability to use data by other users of these directories, makes it impossible for users to determine access to their work to others and does not allow the project base to be formed automatically SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) ubuntu 16.04 KDE plasma version 5.8.9 KDE Frameworks Version: 5.36.0 Qt Version: 5.6.1 kubuntu 18.04 KDE plasma version 5.12.8 KDE Frameworks Version: 5.44.0 Qt Version: 5.9.5 AltLinux p9 KDE plasma version 5.19.x KDE ADDITIONAL INFORMATION In the case of AltLinux p9, only the error of changing permissions to the file from the target directory occurs -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 417067] Dolphin permissions error
https://bugs.kde.org/show_bug.cgi?id=417067 maxim changed: What|Removed |Added CC||ma...@disroot.org -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 417067] Dolphin permissions error
https://bugs.kde.org/show_bug.cgi?id=417067 maxim changed: What|Removed |Added CC|ma...@disroot.org | -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 188794] Embedded Konsole follows fish path through ssh
https://bugs.kde.org/show_bug.cgi?id=188794 Maxim changed: What|Removed |Added CC||maxim3...@gmail.com --- Comment #13 from Maxim --- The problem is still present. It seems to me that fixing it now should be easier, with kiofuse implemented. It can be opened not a remote directory, but mounted, for example /run/user/1000/kio-fuse-.../smb/.../ -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 419638] New: VLC player don't close after watching film (Kubuntu 20.04 beta)
https://bugs.kde.org/show_bug.cgi?id=419638 Bug ID: 419638 Summary: VLC player don't close after watching film (Kubuntu 20.04 beta) Product: ksysguard Version: 5.18.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: maxim.makov...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY VLC player stays in tray after closing VlC window with the film. Tray icon doesn't close after clicking and checking exit. New films cannot be opened in vlc after clicking on them. VLC only opens after searching vlc in KDE command center and clicking on "Run vlc" below it (opens another window with working vlc and second tray icon). STEPS TO REPRODUCE 1. open .mkv video file with vlc 2. close the vlc window 3. OBSERVED RESULT Tray icon hangs in tray. Couldn't open new video file with vlc. EXPECTED RESULT Program closes. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Kubuntu 20.04 beta with default vlc version. KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396975] New: Kwin crashed after closing the window
https://bugs.kde.org/show_bug.cgi?id=396975 Bug ID: 396975 Summary: Kwin crashed after closing the window Product: kwin Version: 5.13.3 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: ya.maxi...@yandex.ru Target Milestone: --- Application: kwin_x11 (5.13.3) Qt Version: 5.11.1 Frameworks Version: 5.48.0 Operating System: Linux 4.17.8-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: Closing the vivaldi-stable (chromium based browser) OS: Antergos (Arch linux based) kwin 5.13.3 -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f2c5c41c6c0 (LWP 984))] Thread 15 (Thread 0x7f2b77fff700 (LWP 4981)): #0 0x7f2c54e38ffc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f2ba09f3dc4 in () at /usr/lib/dri/radeonsi_dri.so #2 0x7f2ba09f3ab8 in () at /usr/lib/dri/radeonsi_dri.so #3 0x7f2c54e33075 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f2c5bde253f in clone () at /usr/lib/libc.so.6 Thread 14 (Thread 0x7f2c3a788700 (LWP 1422)): #0 0x7f2c54e38ffc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f2ba09f3dc4 in () at /usr/lib/dri/radeonsi_dri.so #2 0x7f2ba09f3ab8 in () at /usr/lib/dri/radeonsi_dri.so #3 0x7f2c54e33075 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f2c5bde253f in clone () at /usr/lib/libc.so.6 Thread 13 (Thread 0x7f2b8b7fe700 (LWP 1303)): #0 0x7f2c54e38ffc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f2ba09f3dc4 in () at /usr/lib/dri/radeonsi_dri.so #2 0x7f2ba09f3ab8 in () at /usr/lib/dri/radeonsi_dri.so #3 0x7f2c54e33075 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f2c5bde253f in clone () at /usr/lib/libc.so.6 Thread 12 (Thread 0x7f2b8bfff700 (LWP 1302)): #0 0x7f2c54e38ffc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f2ba09f3dc4 in () at /usr/lib/dri/radeonsi_dri.so #2 0x7f2ba09f3ab8 in () at /usr/lib/dri/radeonsi_dri.so #3 0x7f2c54e33075 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f2c5bde253f in clone () at /usr/lib/libc.so.6 Thread 11 (Thread 0x7f2b98fff700 (LWP 1301)): #0 0x7f2c54e38ffc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f2ba09f3dc4 in () at /usr/lib/dri/radeonsi_dri.so #2 0x7f2ba09f3ab8 in () at /usr/lib/dri/radeonsi_dri.so #3 0x7f2c54e33075 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f2c5bde253f in clone () at /usr/lib/libc.so.6 Thread 10 (Thread 0x7f2b99800700 (LWP 1300)): #0 0x7f2c54e38ffc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f2ba09f3dc4 in () at /usr/lib/dri/radeonsi_dri.so #2 0x7f2ba09f3ab8 in () at /usr/lib/dri/radeonsi_dri.so #3 0x7f2c54e33075 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f2c5bde253f in clone () at /usr/lib/libc.so.6 Thread 9 (Thread 0x7f2b9a001700 (LWP 1299)): #0 0x7f2c54e38ffc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f2ba09f3dc4 in () at /usr/lib/dri/radeonsi_dri.so #2 0x7f2ba09f3ab8 in () at /usr/lib/dri/radeonsi_dri.so #3 0x7f2c54e33075 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f2c5bde253f in clone () at /usr/lib/libc.so.6 Thread 8 (Thread 0x7f2b9a802700 (LWP 1298)): #0 0x7f2c54e38ffc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f2ba09f3dc4 in () at /usr/lib/dri/radeonsi_dri.so #2 0x7f2ba09f3ab8 in () at /usr/lib/dri/radeonsi_dri.so #3 0x7f2c54e33075 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f2c5bde253f in clone () at /usr/lib/libc.so.6 Thread 7 (Thread 0x7f2b9b144700 (LWP 1297)): #0 0x7f2c54e38ffc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f2ba09f3dc4 in () at /usr/lib/dri/radeonsi_dri.so #2 0x7f2ba09f3ab8 in () at /usr/lib/dri/radeonsi_dri.so #3 0x7f2c54e33075 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f2c5bde253f in clone () at /usr/lib/libc.so.6 Thread 6 (Thread 0x7f2ba9163700 (LWP 1249)): #0 0x7f2c5bdd7fa6 in ppoll () at /usr/lib/libc.so.6 #1 0x7f2c591d8f0b in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/libQt5Core.so.5 #2 0x7f2c591da3fb in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #3 0x7f2c5918894c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f2c58fd1a99 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #5 0x7f2c5387a9c9 in ()
[plasmashell] [Bug 391451] New: plasmashell always crashed after clicking on any items in kde global menu
https://bugs.kde.org/show_bug.cgi?id=391451 Bug ID: 391451 Summary: plasmashell always crashed after clicking on any items in kde global menu Product: plasmashell Version: 5.12.2 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: skovorodker.re...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.12.2) Qt Version: 5.10.1 Frameworks Version: 5.43.0 Operating System: Linux 4.15.6-1-ARCH x86_64 Distribution: "Arch Linux" -- Information about the crash: - What I was doing when the application crashed: 1. Go to "System Settings", "Application Style", "Widget Style", "Fine Tuning" tab and enable both "Text Beside Icons" items in "Toolbars" section; 2. Go to Plasma Desktop, right-click on it and add a panel with application menu; 3. Restart applications that doesn't use global menu settings yet; 4. Try to click on any items in created global menu; 5. Catch restart of plasmashell; 6. Go to section 4. The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f91ca730800 (LWP 17276))] Thread 8 (Thread 0x7f91004ec700 (LWP 17390)): #0 0x7f91be4bf7d1 in () at /usr/lib/libglib-2.0.so.0 #1 0x7f91be479ac8 in g_main_context_check () at /usr/lib/libglib-2.0.so.0 #2 0x7f91be479f96 in () at /usr/lib/libglib-2.0.so.0 #3 0x7f91be47a10e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #4 0x7f91c452d314 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f91c44cf3db in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7f91c42de7ae in QThread::exec() () at /usr/lib/libQt5Core.so.5 #7 0x7f9102e9f1ba in KCupsConnection::run() () at /usr/lib/libkcupslib.so #8 0x7f91c42e3b4d in () at /usr/lib/libQt5Core.so.5 #9 0x7f91c349808c in start_thread () at /usr/lib/libpthread.so.0 #10 0x7f91c3bebe7f in clone () at /usr/lib/libc.so.6 Thread 7 (Thread 0x7f911400f700 (LWP 17382)): #0 0x7f91be4c0b79 in g_mutex_lock () at /usr/lib/libglib-2.0.so.0 #1 0x7f91be479525 in g_main_context_prepare () at /usr/lib/libglib-2.0.so.0 #2 0x7f91be479f1e in () at /usr/lib/libglib-2.0.so.0 #3 0x7f91be47a10e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #4 0x7f91c452d314 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f91c44cf3db in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7f91c42de7ae in QThread::exec() () at /usr/lib/libQt5Core.so.5 #7 0x7f91c80b350b in () at /usr/lib/libQt5Quick.so.5 #8 0x7f91c42e3b4d in () at /usr/lib/libQt5Core.so.5 #9 0x7f91c349808c in start_thread () at /usr/lib/libpthread.so.0 #10 0x7f91c3bebe7f in clone () at /usr/lib/libc.so.6 Thread 6 (Thread 0x7f919700 (LWP 17372)): #0 0x7f91c349e3bd in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f91c9e10f77 in () at /usr/lib/libQt5Script.so.5 #2 0x7f91c9e10fb9 in () at /usr/lib/libQt5Script.so.5 #3 0x7f91c349808c in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f91c3bebe7f in clone () at /usr/lib/libc.so.6 Thread 5 (Thread 0x7f91aa363700 (LWP 17361)): #0 0x7f91be4c0b94 in g_mutex_unlock () at /usr/lib/libglib-2.0.so.0 #1 0x7f91be4797ca in g_main_context_query () at /usr/lib/libglib-2.0.so.0 #2 0x7f91be479f6c in () at /usr/lib/libglib-2.0.so.0 #3 0x7f91be47a10e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #4 0x7f91c452d314 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f91c44cf3db in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7f91c42de7ae in QThread::exec() () at /usr/lib/libQt5Core.so.5 #7 0x7f91c74f5379 in () at /usr/lib/libQt5Qml.so.5 #8 0x7f91c42e3b4d in () at /usr/lib/libQt5Core.so.5 #9 0x7f91c349808c in start_thread () at /usr/lib/libpthread.so.0 #10 0x7f91c3bebe7f in clone () at /usr/lib/libc.so.6 Thread 4 (Thread 0x7f91abdfa700 (LWP 17357)): #0 0x7f91be479350 in g_main_context_prepare () at /usr/lib/libglib-2.0.so.0 #1 0x7f91be479f1e in () at /usr/lib/libglib-2.0.so.0 #2 0x7f91be47a10e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f91c452d314 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f91c44cf3db in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f91c42de7ae in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f91c74f5379 in () at /usr/lib/libQt5Qml.so.5 #7 0x7f91c42e3b4d
[plasmashell] [Bug 391451] plasmashell crashed after clicking on any items in kde global menu
https://bugs.kde.org/show_bug.cgi?id=391451 Maxim changed: What|Removed |Added Summary|plasmashell always crashed |plasmashell crashed after |after clicking on any items |clicking on any items in |in kde global menu |kde global menu -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 391451] plasmashell crashed after clicking on any items in kde global menu
https://bugs.kde.org/show_bug.cgi?id=391451 --- Comment #1 from Maxim --- Addition: I wanted to capture a screencast of the bug, but this issue is disappeared when I re-created global menu (remove panel and add panel) and unreproducible anymore by myself. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 378003] All packages: qt incompletely upgraded (qtbase-abi-5-5-1
https://bugs.kde.org/show_bug.cgi?id=378003 Maxim changed: What|Removed |Added CC||maxim.minc...@yandex.ru -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 403204] New: Discovery chrash on startup when updates available
https://bugs.kde.org/show_bug.cgi?id=403204 Bug ID: 403204 Summary: Discovery chrash on startup when updates available Product: Discover Version: 5.14.5 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: maxvancef...@gmail.com Target Milestone: --- Application: plasma-discover (5.14.5) Qt Version: 5.11.2 Frameworks Version: 5.54.0 Operating System: Linux 4.15.0-43-generic x86_64 Distribution: KDE neon User Edition 5.14 -- Information about the crash: - What I was doing when the application crashed: I click in system tray icon, which show me that updates is available. The crash can be reproduced every time. -- Backtrace: Application: Discover (plasma-discover), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f0a3a1f0200 (LWP 9354))] Thread 12 (Thread 0x7f09ea840700 (LWP 9368)): #0 0x7f0a31e61ed9 in futex_reltimed_wait_cancelable (private=, reltime=0x7f09ea83fc30, expected=0, futex_word=0x562de99a5390) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 0x7f0a31e61ed9 in __pthread_cond_wait_common (abstime=0x7f09ea83fd00, mutex=0x562de99a5340, cond=0x562de99a5368) at pthread_cond_wait.c:533 #2 0x7f0a31e61ed9 in __pthread_cond_timedwait (cond=0x562de99a5368, mutex=0x562de99a5340, abstime=0x7f09ea83fd00) at pthread_cond_wait.c:667 #3 0x7f0a35e6b880 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f0a35e6228d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f0a35e6aadb in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f0a31e5b6db in start_thread (arg=0x7f09ea840700) at pthread_create.c:463 #7 0x7f0a3576288f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 11 (Thread 0x7f09eb041700 (LWP 9367)): #0 0x7f0a35755bf9 in __GI___poll (fds=0x7f09e00018a0, nfds=1, timeout=125829) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f0a2fcc0539 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f0a2fcc064c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f0a3609004b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f0a3603430a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f0a35e5fbba in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f0a35e6aadb in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f0a31e5b6db in start_thread (arg=0x7f09eb041700) at pthread_create.c:463 #8 0x7f0a3576288f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 10 (Thread 0x7f09f0ac3700 (LWP 9364)): #0 0x7f0a31e61ed9 in futex_reltimed_wait_cancelable (private=, reltime=0x7f09f0ac2c30, expected=0, futex_word=0x7f09ec0033b0) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 0x7f0a31e61ed9 in __pthread_cond_wait_common (abstime=0x7f09f0ac2d00, mutex=0x7f09ec003360, cond=0x7f09ec003388) at pthread_cond_wait.c:533 #2 0x7f0a31e61ed9 in __pthread_cond_timedwait (cond=0x7f09ec003388, mutex=0x7f09ec003360, abstime=0x7f09f0ac2d00) at pthread_cond_wait.c:667 #3 0x7f0a35e6b880 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f0a35e6228d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f0a35e6aadb in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f0a31e5b6db in start_thread (arg=0x7f09f0ac3700) at pthread_create.c:463 #7 0x7f0a3576288f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 9 (Thread 0x7f09f12c4700 (LWP 9363)): #0 0x7f0a2fcbd49a in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f0a2fcbf9d3 in g_main_context_prepare () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f0a2fcc046b in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f0a2fcc064c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f0a3609004b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f0a3603430a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f0a35e5fbba in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f0a35e6aadb in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f0a31e5b6db in start_thread (arg=0x7f09f12c4700) at pthread_create.c:463 #9 0x7f0a3576288f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 8 (Thread 0x7f0a022ec700 (LWP 9361)): #0 0x7f0a2fd06064 in g_mutex_unlock () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f0a2fcbfa8
[plasmashell] [Bug 375517] Submenu in context menu opening on another monitor
https://bugs.kde.org/show_bug.cgi?id=375517 Maxim changed: What|Removed |Added CC||ya.maxi...@yandex.ru -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 495705] New: Color picker for "Plain Color" Wallpaper option Shortens color model options to 1 letter
https://bugs.kde.org/show_bug.cgi?id=495705 Bug ID: 495705 Summary: Color picker for "Plain Color" Wallpaper option Shortens color model options to 1 letter Classification: Applications Product: systemsettings Version: 6.2.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_wallpaper Assignee: plasma-b...@kde.org Reporter: sliva...@gmail.com CC: me...@kde.org Target Milestone: --- Created attachment 175463 --> https://bugs.kde.org/attachment.cgi?id=175463&action=edit Color picker with color model menu opened SUMMARY Color picker shortens color model menu to the shortest possible state no matter how wide the window is which makes it hard to use. STEPS TO REPRODUCE 1. Go to System Settings > Wallpaper 2. Select Wallpaper type: Plain Color 3. Open the Color picker. OBSERVED RESULT Color model options (HEX, RGB, HSV, HSB) are shortened to H, R, H and H. EXPECTED RESULT Full color model names. SOFTWARE/OS VERSIONS Linux/KDE Plasma: EndeavourOS KDE Plasma Version: 6.2.2 KDE Frameworks Version: 6.7.0 Qt Version: 6.8.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 493195] Automatically clone panel when connecting a new display
https://bugs.kde.org/show_bug.cgi?id=493195 --- Comment #7 from Maxim --- (In reply to Nate Graham from comment #6) > Manually, though. I don't think we're going to be doing any automatic panel > cloning, as the behavior would be challenging to predict: > 1. What about monitors that, due to their own hardware issues, get detected > as "newly connected" every time? > 2. What about setups with more than one panel on the original monitor? > 3. What about setups where a single panel on the original monitor would not > fit or make sense on a newly connected monitor (e.g. very wide bottom panel > on monitor 1, and you connect a new portrait-orientation monitor 2? > > For these reasons, there are just too many edge cases, and panel cloning is > going to have to be a manual thing. Hi Nate, please see my comment in the original feature request: https://bugs.kde.org/show_bug.cgi?id=446654#c47 My suggestion is to always ask the user. I.e., let the user set whether to copy or not some panel to the new monitor. This can be an attribute of the panel and can be False by default. If the user intentionally sets the flag, they agree there can be side effects. In many cases it will just work, however in the those edge cases the users will expect this and maybe temporarily unset the flag. Also, if the copied panel is too wide, the user can super quickly delete it. This also solves the question how many panels to copy - specifically those that the user has requested to copy. As I mentioned there the algorithm can also check if the new monitor already has any panels. If there're no panels yet, it looks like the target case for copying the panels. If the monitor already has any panels - big change the user has already connected it before and already done some adjustments. (this behavior just needs to be indicated under some question mark next to the setting) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 497100] New: Feature Request: Automatically clone selected panels when connecting a new display
https://bugs.kde.org/show_bug.cgi?id=497100 Bug ID: 497100 Summary: Feature Request: Automatically clone selected panels when connecting a new display Classification: Plasma Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: maxim.kukush...@gmail.com CC: niccolo.venera...@gmail.com Target Milestone: 1.0 SUMMARY When using two (or more) monitors, it is convenient to have a panel on each monitor such that all panels are completely identical. Currently, it's either tedious process of creating a new panel from scratch and replicating all widgets and their settings, or (with the upcoming or just implemented change) still a manual step of selecting a panel and cloning it. It would be nice if cloning could be automated (see Additional Information for a more elaborated suggestion) SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kernel 6.12.1-arch1-1 KDE Plasma Version: 6.2.4 KDE Frameworks Version: 5.116.0 Qt Version: 6.8.1 ADDITIONAL INFORMATION This is a re-iteration of the previous feature request (https://bugs.kde.org/show_bug.cgi?id=493195) with a different suggested approach discussed in the comments there. Basically, the main concern when implementing automatic cloning was the decision making of which panels to clone and how to differentiate a new monitor and a previous monitor (in case monitors change their IDs. Also, there was a concern about different resolutions and aspect ratios in theory making the cloned panel look ugly. The suggestion in this feature request is: Always prefer user's choice and let the user decide. If the setup didn't work nicely - it was the user's elaborate choice anyway. Regarding the proposed algorithm: - Implement a panel attribute "Clone to new monitors" which is by default set to FALSE. This ensures backward compatibility with the current behavior and no unexpected side effects - If the user sets this flag intentionally - they assume responsibility of panels in theory not fitting well different resolutions - At this point a warning can be shown to indicate possible side effects When a monitor is connected: - Check if the connected monitor already has any panels - If yes -> do nothing. This monitor has been connected before, the panels have already been cloned, or the user already customized it - If no, check each panel to find those which have the above flag set - If the clone flag is set -> Copy the panel to the connected monitor This is a simple algorithm that: - Ensures backward compatibility - Doesn't affect existing setup and doesn't clone panels indefinitely - Addresses automatic provisioning of a new monitor with panels - Is flexible, cause it lets the user choose which panels to clone automatically (maybe someone prefers to clone only one panel to extra monitors, but have panels on the main one) The panel configuration page can also have a question mark next to the "Clone to new monitors" flag, to show a quick summary of the above algorithm to give the user an idea of how it works. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 493195] Automatically clone panel when connecting a new display
https://bugs.kde.org/show_bug.cgi?id=493195 --- Comment #9 from Maxim --- (In reply to Nate Graham from comment #8) > It's an interesting idea. Can you open a new feature requests for that > specific thing so it doesn't get lost? Thanks! I've just raised a new feature request: https://bugs.kde.org/show_bug.cgi?id=497100 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 497100] Feature Request: Automatically clone selected panels when connecting a new display
https://bugs.kde.org/show_bug.cgi?id=497100 --- Comment #7 from Maxim --- (In reply to Grant Gryczan from comment #5) > I see. But in that case, wouldn't it still be the same monitor with an > existing panel? Or does KDE forget the panel when you disconnect the > monitor? I've disconnected and reconnected monitors before, and panels have > never gotten lost. Yeah, that happens a lot at work and home. Perhaps it's a bug in KDE, or maybe the monitor indeed identifies itself differently sometimes and there's nothing that KDE can do about it. However, even beyond that - at work, many times you have to travel and connect to random monitors/projectors. Many offices nowadays have hot desks and you have to connect to random new monitor every day. There're lots of cases where new monitors is a norm. This feature request has been created not to completely replace the option of always keeping a clone of a panel (I'd be happy if that request was implemented too). However, the original request to keep a clone of a panel raised many technical questions that were hard to address (like what to do in case the monitors have significantly different resolution and the mirrored panel is too big on the other monitor). So I raised this option as an alternative - temporary or permanent (KDE has always been about flexibility and configurability, so in theory both options could be kept). Regarding the point of keeping the panels in sync and having to apply the changes manually to each of them in my original suggestion - yes, I agree that it can be a bit cumbersome and non-obvious at first. The advantages I see in this approach though are (especially if both mirroring and one-off cloning are implemented in future): - Many times on the permanent setups, one may actually want the panels to drift a bit in their configuration. I'm for one who keeps them slightly different sometimes (say, clock/calendar and tray on the primary monitor only) - The configuration of the existing panels is not frequently changed, so rarely adjusting it might not be a big deal. The biggest problem is the initial configuration that is addressed in my proposal - In case major configuration changes are required, with my proposal it can be quickly addressed by deleting the cloned panel and reconnecting the monitor, for the panel to be cloned again That being said, I'm not saying that the above points are applicable to everyone, and I do agree that people have different setups and use cases and some people may need to change the panel configuration daily (for whatever reasons - we're all different). I'm just saying that if such an approach can be implemented in a reasonable time, it would already be a huge relief comparing to the lack of any cloning options atm. That doesn't cancel the fact the actual mirroring of a panel would be really nice to have and I don't see this proposal to be a replacement of mirroring. Rather a quick workaround or (better) an available alternative to mirroring. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 346135] Kmail support for DarkThemes and HTML-Mails
https://bugs.kde.org/show_bug.cgi?id=346135 --- Comment #7 from Maxim Vasilyev --- Indeed. It doesn't work for anyone. It's a real issue, although not in KMail or KDE, but in those who can't slap a single in HTML letter. I suppose the best soluion would be to add a switch to 'force white background for HTML letters' or, like in Kate, an option to select theme for text box. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 412709] Libreoffice windows and virtual desktops
https://bugs.kde.org/show_bug.cgi?id=412709 Maxim Egorushkin changed: What|Removed |Added Version|5.17.0 |5.27.3 CC||maxim.yegorush...@gmail.com --- Comment #11 from Maxim Egorushkin --- KDE Neon still suffers from this bug. Any plans to fix it? Operating System: KDE neon 5.27 KDE Plasma Version: 5.27.3 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 Kernel Version: 5.19.0-1018-lowlatency (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 340982] No way to change just the date format but not its actual translated text
https://bugs.kde.org/show_bug.cgi?id=340982 --- Comment #229 from Maxim Egorushkin --- Thinking more about date format customisation, another option could be a file or a few in .config directory, e.g.: .config/date-format/default .config/date-format/file .config/date-format/clock .config/date-format/calendar Each file would contain a sole strftime format string, or gnu date format string, whatever works best. Which any applications can choose to honour, or ignore (to its users' dismay). Waiting on POSIX or C standard library can be an exercise in futility. Leading by example is contagious. Existing case study is https://editorconfig.org/ -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442337] CPU frequency widget shows wrong value
https://bugs.kde.org/show_bug.cgi?id=442337 Maxim Egorushkin changed: What|Removed |Added CC||maxim.yegorush...@gmail.com --- Comment #1 from Maxim Egorushkin --- Created attachment 158811 --> https://bugs.kde.org/attachment.cgi?id=158811&action=edit Correct GPU frequency, CPU core frequencies are stuck with the initial values that never change. Same issue in KDE neon 5.27. The widget shows correct real-time GPU frequency, but CPU core frequencies are stuck with the initial values that never change. Operating System: KDE neon 5.27 KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9 Kernel Version: 5.19.0-1023-lowlatency (64-bit) Graphics Platform: X11 Processors: 32 × AMD Ryzen 9 5950X 16-Core Processor Memory: 125.7 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 3090/PCIe/SSE2 Manufacturer: Gigabyte Technology Co., Ltd. Product Name: X570 AORUS MASTER -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 451873] Temperature page line chart wrong zero last value
https://bugs.kde.org/show_bug.cgi?id=451873 Maxim Egorushkin changed: What|Removed |Added Ever confirmed|0 |1 Resolution|INTENTIONAL |--- Assignee|ksysguard-b...@kde.org |maxim.yegorush...@gmail.com Status|RESOLVED|REOPENED --- Comment #2 from Maxim Egorushkin --- Created attachment 170434 --> https://bugs.kde.org/attachment.cgi?id=170434&action=edit System Monitor time series misaligned. This current line chart update logic results in time series being being misaligned in the System Monitor. See the attached screenshot of System Monitor where the CPU usage time series line chart is misaligned relative to corresponding temperature and fans time series charts. This is rather undesirable behaviour, I would not intend that onto my neighbour. The best practice is to have time series aligned by time, with the rightmost chart edge corresponding to the latest data points at all times. This is easily achieved by always displaying new/later data points as coming from the right edge of the chart, e.g. display chart points and lines from right to left starting with the latest data point. This way time series chart in System Monitor would stay correctly aligned on the right edge regardless of the length of available time-series history. Such logic I would happily intend onto my neighbour. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 451873] Temperature page line chart wrong zero last value
https://bugs.kde.org/show_bug.cgi?id=451873 Maxim Egorushkin changed: What|Removed |Added Version|5.24.3 |6.0.5 -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 451873] Temperature page line chart wrong zero last value
https://bugs.kde.org/show_bug.cgi?id=451873 --- Comment #3 from Maxim Egorushkin --- Created attachment 170437 --> https://bugs.kde.org/attachment.cgi?id=170437&action=edit System Monitor time series misaligned from the start. Here is another example of time-series charts being misaligned in System Monitor from the start because of different widths of Y-axis tick labels in different charts. That is extremely undesirable and must never happen. But it happens because the current line chart update logic doesn't follow the best practices. MSI Afterburner hardware monitor time-series charts is a good example of the best practices to follow. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 481565] New: The konsole closes unexpectedly
https://bugs.kde.org/show_bug.cgi?id=481565 Bug ID: 481565 Summary: The konsole closes unexpectedly Classification: Applications Product: konsole Version: 23.08.1 Platform: Kubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: mbaru...@gmail.com Target Milestone: --- Created attachment 165949 --> https://bugs.kde.org/attachment.cgi?id=165949&action=edit crash log SUMMARY *** The konsole closes unexpectedly *** STEPS TO REPRODUCE 1. Open the console in the morning 2. Come back the next morning 3. Console closed OBSERVED RESULT Console closed EXPECTED RESULT The console continues to work SOFTWARE/OS VERSIONS PRETTY_NAME="Ubuntu 23.10" NAME="Ubuntu" VERSION_ID="23.10" VERSION="23.10 (Mantic Minotaur)" VERSION_CODENAME=mantic ID=ubuntu ID_LIKE=debian HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; UBUNTU_CODENAME=mantic LOGO=ubuntu-logo 6.5.0-17-generic ADDITIONAL INFORMATION /var/log/syslog 2024-02-20T09:26:43.343691+03:00 max-note plasmashell[194427]: Unable to find file for pid 8340 expected at "kcrash-metadata/8340.ini" 2024-02-20T09:26:43.345512+03:00 max-note kwin_x11[2900]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 52456, resource id: 79691860, major code: 18 (ChangeProperty), minor code: 0 2024-02-20T09:26:43.360962+03:00 max-note plasmashell[8340]: QSocketNotifier: Invalid socket 12 and type 'Read', disabling... 2024-02-20T09:26:43.361171+03:00 max-note plasmashell[8340]: QSocketNotifier: Invalid socket 14 and type 'Read', disabling... 2024-02-20T09:26:43.361516+03:00 max-note kded5[2897]: Service ":1.135" unregistered 2024-02-20T09:26:44.369449+03:00 max-note plasmashell[8340]: Unable to start Dr. Konqi 2024-02-20T09:26:44.369555+03:00 max-note plasmashell[8340]: Re-raising signal for core dump handling. 2024-02-20T09:26:45.511232+03:00 max-note systemd[1]: Started whoopsie.service - crash report submission. 2024-02-20T09:26:45.520982+03:00 max-note whoopsie[561349]: [09:26:45] Using lock path: /var/lock/whoopsie/lock 2024-02-20T09:26:45.523224+03:00 max-note systemd[1]: whoopsie.service: Deactivated successfully. 2024-02-20T09:26:45.950199+03:00 max-note kded5[2897]: "/var/crash" 2024-02-20T09:26:45.950380+03:00 max-note kded5[2897]: running "/usr/share/kubuntu-notification-helper/whoopsie-upload-all" 2024-02-20T09:26:45.967753+03:00 max-note kded5[561360]: kdeinit5: preparing to launch '/usr/lib/x86_64-linux-gnu/libexec/kf5/klauncher' 2024-02-20T09:26:45.968625+03:00 max-note kded5[561360]: kdeinit5: Launched KLauncher, pid = 561361, result = 0 2024-02-20T09:26:46.090841+03:00 max-note kded5[561361]: Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) 2024-02-20T09:26:46.091475+03:00 max-note kded5[561360]: kdeinit5: opened connection to :0 2024-02-20T09:26:46.105380+03:00 max-note kded5[561360]: kdeinit5: Got EXEC_NEW '/usr/share/kubuntu-notification-helper/whoopsie-upload-all' from launcher. 2024-02-20T09:26:46.105501+03:00 max-note kded5[561360]: kdeinit5: preparing to launch '/usr/share/kubuntu-notification-helper/whoopsie-upload-all' 2024-02-20T09:26:46.107995+03:00 max-note kded5[2897]: "/var/crash/_usr_bin_konsole.1000.crash" 2024-02-20T09:26:46.108089+03:00 max-note kded5[2897]: "/var/crash" 2024-02-20T09:26:46.108153+03:00 max-note kded5[2897]: running "/usr/share/kubuntu-notification-helper/whoopsie-upload-all" 2024-02-20T09:26:46.108519+03:00 max-note kded5[561360]: kdeinit5: Got EXEC_NEW '/usr/share/kubuntu-notification-helper/whoopsie-upload-all' from launcher. 2024-02-20T09:26:46.108586+03:00 max-note kded5[561360]: kdeinit5: preparing to launch '/usr/share/kubuntu-notification-helper/whoopsie-upload-all' 2024-02-20T09:26:46.182781+03:00 max-note kded5[561375]: INFO: whoopsie-upload-all already running 2024-02-20T09:26:46.195577+03:00 max-note kded5[561374]: ERROR: whoopsie is not running 2024-02-20T09:26:46.197455+03:00 max-note kded5[561360]: kdeinit5: PID 561375 terminated. 2024-02-20T09:26:46.212771+03:00 max-note kded5[561360]: kdeinit5: PID 561374 terminated. 2024-02-20T09:26:48.894910+03:00 max-note kded5[2897]: "/var/crash/_usr_bin_konsole.1000.crash" 2024-02-20T09:26:57.343432+03:00 max-note kded5[2897]: message repeated 17 times: [ "/var/crash/_usr_bin_konsole.1000.crash"] 2024-02-20T09:26:57.466643+03:00 max-note systemd[1]: Started whoopsie.service - crash report submission. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 487154] New: Konsole won't start, crashes on launch every time.
https://bugs.kde.org/show_bug.cgi?id=487154 Bug ID: 487154 Summary: Konsole won't start, crashes on launch every time. Classification: Applications Product: konsole Version: 24.02.2 Platform: Neon OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: maxim.yegorush...@gmail.com Target Milestone: --- Application: konsole (24.02.2) Qt Version: 6.7.0 Frameworks Version: 6.1.0 Operating System: Linux 6.5.0-35-generic x86_64 Windowing System: X11 Distribution: KDE neon 6.0 DrKonqi: 6.0.4 [KCrashBackend] -- Information about the crash: Konsole won't start, crashes on launch every time. I tried launching from Plasma applications menu or Krunner, Konsole crashes on launch and won't start. Console window in Dolphin still works fine. The crash can be reproduced every time. -- Backtrace: Application: Konsole (konsole), signal: Aborted [KCrash Handler] #4 __pthread_kill_implementation (no_tid=0, signo=6, threadid=125572437551808) at ./nptl/pthread_kill.c:44 #5 __pthread_kill_internal (signo=6, threadid=125572437551808) at ./nptl/pthread_kill.c:78 #6 __GI___pthread_kill (threadid=125572437551808, signo=signo@entry=6) at ./nptl/pthread_kill.c:89 #7 0x723521c42476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #8 0x723521c287f3 in __GI_abort () at ./stdlib/abort.c:79 #9 0x723523d41eec in ?? () from /lib/x86_64-linux-gnu/libKF6XmlGui.so.6 #10 0x723523da42ea in ?? () from /lib/x86_64-linux-gnu/libKF6XmlGui.so.6 #11 0x723523db9732 in KXmlGuiWindow::createGUI(QString const&) () from /lib/x86_64-linux-gnu/libKF6XmlGui.so.6 #12 0x723523daf633 in KXmlGuiWindow::setupGUI(QSize const&, QFlags, QString const&) () from /lib/x86_64-linux-gnu/libKF6XmlGui.so.6 #13 0x723523daf781 in KXmlGuiWindow::setupGUI(QFlags, QString const&) () from /lib/x86_64-linux-gnu/libKF6XmlGui.so.6 #14 0x7235240c9a16 in Konsole::MainWindow::MainWindow() () from /lib/x86_64-linux-gnu/libkonsoleapp.so.24.02.2 #15 0x7235240bdae3 in Konsole::Application::newMainWindow() () from /lib/x86_64-linux-gnu/libkonsoleapp.so.24.02.2 #16 0x7235240c12c5 in Konsole::Application::processWindowArgs(bool&) () from /lib/x86_64-linux-gnu/libkonsoleapp.so.24.02.2 #17 0x7235240c15fa in Konsole::Application::newInstance() () from /lib/x86_64-linux-gnu/libkonsoleapp.so.24.02.2 #18 0x5cd3ebbf99cd in ?? () #19 0x723521c29d90 in __libc_start_call_main (main=main@entry=0x5cd3ebbf6e80, argc=argc@entry=1, argv=argv@entry=0x7fff2eca4168) at ../sysdeps/nptl/libc_start_call_main.h:58 #20 0x723521c29e40 in __libc_start_main_impl (main=0x5cd3ebbf6e80, argc=1, argv=0x7fff2eca4168, init=, fini=, rtld_fini=, stack_end=0x7fff2eca4158) at ../csu/libc-start.c:392 #21 0x5cd3ebbfa445 in ?? () [Inferior 1 (process 4142) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[muon] [Bug 418044] Muon crashes during uninstallation
https://bugs.kde.org/show_bug.cgi?id=418044 Maxim Egorushkin changed: What|Removed |Added CC||maxim.yegorush...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[muon] [Bug 418044] Muon crashes during uninstallation
https://bugs.kde.org/show_bug.cgi?id=418044 --- Comment #1 from Maxim Egorushkin --- Created attachment 148503 --> https://bugs.kde.org/attachment.cgi?id=148503&action=edit New crash information added by DrKonqi muon (5.8.0) using Qt 5.15.3 I experience the same crash when purging or uninstalling. -- Backtrace (Reduced): #4 0x7f0dde7c125f in QApt::Backend::package (this=this@entry=0x55ab1e47ba80, name=...) at /usr/include/apt-pkg/string_view.h:39 #5 0x7f0dde7c3f04 in QApt::Backend::search (this=0x55ab1e47ba80, searchString=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qstring.h:91 #6 0x55ab1cc11f52 in PackageProxyModel::search (this=0x55ab1e2032d0, searchText=...) at ./src/PackageModel/PackageProxyModel.cpp:71 #7 0x55ab1cc16ace in PackageWidget::startSearch (this=0x55ab1e167380) at ./src/PackageModel/PackageWidget.cpp:409 #8 PackageWidget::startSearch (this=0x55ab1e167380) at ./src/PackageModel/PackageWidget.cpp:406 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 441830] 12 TCP keepalive packets per minute is excessive, battery drain hazard.
https://bugs.kde.org/show_bug.cgi?id=441830 --- Comment #6 from Maxim Egorushkin --- Longer story about this bug report. My OnePlus 7T Pro McLaren would go 2 days without charge in my routine, with day 2 morning charge above 55% for the first 8 months, I was quite impressed. Then suddenly day 2 morning charge became ~38%. I examined phone battery stats and there was Android System being top battery consumer with 25%+, which I hadn't seen being above 10% before. I wasn't able to find the cause of Android System battery drain at the time and had to switch to charging the phone every night. A few weeks later I started Wireshark on my workstation for unrelated task and couldn't help but notice these 5-second keepalive TCP messages between KDE Connect on the workstation and the phone. The phone with its screen off replied to all these keepalive messages, which looked excessive and unnecessary. I uninstalled KDE Connect app from my phone, went on with my task, charged the phone overnight. Next day at charge time the remaining charge was above 60% and Android System battery usage went lower than 10%. I switched back to charging the phone once in 2 days. I had to make this workaround because it makes 2x difference for me in how often the phone needs to be charged. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 441830] 12 TCP keepalive packets per minute is excessive, battery drain hazard.
https://bugs.kde.org/show_bug.cgi?id=441830 --- Comment #7 from Maxim Egorushkin --- Battery power is a limited resource but 5-second keepalive frequency expends it at high rate without consideration. The user may know best how much battery power they would be willing to expend for the immediacy of disconnect detection, or how much disconnect detection delay they can tolerate. And that may depend on the intended usage in the near future, or the network, or connection type, or particular device, etc.. Making this setting user configurable from both the desktop app and the mobile app would be the ideal solution - a win-win for users and developers. -- You are receiving this mail because: You are watching all bug changes.
[Skanlite] [Bug 458719] New: Skanlite multiple selection scan fails with "Error during device I/O"
https://bugs.kde.org/show_bug.cgi?id=458719 Bug ID: 458719 Summary: Skanlite multiple selection scan fails with "Error during device I/O" Product: Skanlite Version: 22.08.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kare.s...@iki.fi Reporter: maxim.yegorush...@gmail.com Target Milestone: --- With save mode "Open the save dialog for the first image only" multiple selection scan fails to scan the next selection with "Error during device I/O" message. HP Color LaserJet Pro M283fdw scanner with hpaio:/ scanner connection. Connections escl:http:// and escl:https:// fail during preview scan with "Invalid argument" error while the scanner gets stuck with "Scanning to Computer" message until I tap "cancel" on it. The scanner seems to require a delay between subsequent scan requests to move the image sensor back up to the starting position at the top of the page. To work around the error, I scan one selection at a time and make a new selection while the image sensor is returning to the starting position. One way to fix this error would be for Skanlite to keep retrying its failed scan requests, e.g., retry every 0.5 second for 10 seconds and only then give up and fail. This numbers should probably be configurable. Even better "do more with less" option would be for Skanlite to scan the entire bounding rectangle of all selections in one scan request / one image sensor scanning pass, and extract the multiple selection scans from that one big scan in RAM. This saves both time and energy for the expense of higher RAM utilization. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 340982] No way to change just the date format but not its actual translated text
https://bugs.kde.org/show_bug.cgi?id=340982 Maxim Egorushkin changed: What|Removed |Added See Also|https://bugs.kde.org/show_b | |ug.cgi?id=316180| -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 316180] Provide a (very) short date format, like dd-mm, dd.mm
https://bugs.kde.org/show_bug.cgi?id=316180 Maxim Egorushkin changed: What|Removed |Added See Also|https://bugs.kde.org/show_b | |ug.cgi?id=340982| -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 451873] New: Temperature page line chart wrong zero last value
https://bugs.kde.org/show_bug.cgi?id=451873 Bug ID: 451873 Summary: Temperature page line chart wrong zero last value Product: plasma-systemmonitor Version: 5.24.3 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: maxim.yegorush...@gmail.com CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- Created attachment 147715 --> https://bugs.kde.org/attachment.cgi?id=147715&action=edit Temperature page line chart wrong zero last value screenshot SUMMARY Temperature page line chart displays last value of every temperature time series as 0°C, which isn't right. STEPS TO REPRODUCE 1. Open System Monitor. 2. Navigate to Temperature page. OBSERVED RESULT Temperature page default line chart all temperature time series drop to 0°C at the end. EXPECTED RESULT The line chart shows correct last measured temperature at the end, not 0°C. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE neon 5.24 KDE Plasma Version: 5.24.3 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION This bug didn't exist in the past, but I didn't notice KDE neon update which broke it. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 441830] 12 TCP keepalive packets per minute is excessive, battery drain hazard.
https://bugs.kde.org/show_bug.cgi?id=441830 --- Comment #3 from Maxim Egorushkin --- A workaround to configure TCP keepalive timeout for kdeconnectd until the application makes this timeout configurable: https://github.com/max0x7ba/kdeconnect-powersave-keepalive -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 441830] 12 TCP keepalive packets per minute is excessive, battery drain hazard.
https://bugs.kde.org/show_bug.cgi?id=441830 Maxim Egorushkin changed: What|Removed |Added CC||n...@kde.org --- Comment #5 from Maxim Egorushkin --- (In reply to valdikss from comment #4) > (In reply to Maxim Egorushkin from comment #3) > > A workaround to configure TCP keepalive timeout for kdeconnectd until the > > application makes this timeout configurable: > > https://github.com/max0x7ba/kdeconnect-powersave-keepalive > > Could you please make a test of cellphone battery consumption with 5 second > keep-alives vs longer keep-alives please? The developers must provide justification for these rather frequent TCP keepalive messages when communicating with battery-powered devices. Without justification I consider this hard-coded 5-second TCP keepalive timeout leftover debugging code that the developers forgot to remove. There is no value for this timeout which works for any and all use cases. This timeout must be user-configurable. > I was asked to justify the modification in > https://invent.kde.org/network/kdeconnect-kde/-/merge_requests/ > 447#note_388849, but always forgot to make a clean test. I cannot do that for you, I am sorry. IMO, it is rather the authors who must justify the rather short TCP keepalive timeout and prove that it doesn't result in increased battery drain. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 441830] New: 12 keepalives per minute is excessive, battery drain hazard.
https://bugs.kde.org/show_bug.cgi?id=441830 Bug ID: 441830 Summary: 12 keepalives per minute is excessive, battery drain hazard. Product: kdeconnect Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: plasmoid Assignee: albertv...@gmail.com Reporter: maxim.yegorush...@gmail.com Target Milestone: --- Created attachment 141200 --> https://bugs.kde.org/attachment.cgi?id=141200&action=edit TCP keepalive packets in wireshark SUMMARY I couldn't help but notice in Wireshark that my KDE Neon workstation and my phone exchange 12 TCP keepalive packets per minute. Such a rate doesn't seem reasonable at all and I am concerned that it drains my phone battery for no good reason. STEPS TO REPRODUCE 1. Pair KDE Connect on a workstation to a phone. 2. Start Wireshark on the workstation. OBSERVED RESULT 12 TCP keepalive packets per minute between the workstation and the phone. EXPECTED RESULT No TCP keepalive packets. Or configurable TCP keepalive interval, with an option to disable keepalive completely. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE neon 5.22 KDE Plasma Version: 5.22.4 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION https://github.com/KDE/kdeconnect-kde/blob/664da445ee1ad5b63727cd0453bb6ca8364f50ea/core/backends/lan/lanlinkprovider.cpp#L575 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 441830] 12 TCP keepalive packets per minute is excessive, battery drain hazard.
https://bugs.kde.org/show_bug.cgi?id=441830 Maxim Egorushkin changed: What|Removed |Added Summary|12 keepalives per minute is |12 TCP keepalive packets |excessive, battery drain|per minute is excessive, |hazard. |battery drain hazard. -- You are receiving this mail because: You are watching all bug changes.
[klipper] [Bug 335831] pasting works sporadicly
https://bugs.kde.org/show_bug.cgi?id=335831 --- Comment #5 from Maxim Egorushkin --- I haven't been using those apps for quite a while, so can no longer confirm. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 441830] 12 TCP keepalive packets per minute is excessive, battery drain hazard.
https://bugs.kde.org/show_bug.cgi?id=441830 --- Comment #10 from Maxim Egorushkin --- (In reply to Simon Redman from comment #9) > In particular, this claim is unsubstantiated from the evidence in this bug: Your response is little more than arrogant anti-scientific dismissals and denials, I am afraid. Which makes you a part of the problem, rather than solution, in my opinion. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 441830] 12 TCP keepalive packets per minute is excessive, battery drain hazard.
https://bugs.kde.org/show_bug.cgi?id=441830 --- Comment #11 from Maxim Egorushkin --- (In reply to Simon Redman from comment #8) > (In reply to Maxim Egorushkin from comment #5) > > The developers must provide justification for these rather frequent TCP > > keepalive messages when communicating with battery-powered devices. > > As in the PR vladikss linked: If the keepalive is set higher, it will > falsely tell users that the phone is connected when it is in fact not. The problem the desktop kdeconnect tries to solve with its uber-frequent TCP keep-alives is detecting whether the user mobile device is still connected or not. That's a genuine and common problem, and it has long been solved. The uber-frequent TCP keep-alives kdeconnect uses to solve this recurrent problem isn't the right solution or best practice, precisely because it drains mobile device battery. There are different solutions for this problem in different mobile OSs. kdeconnect authors should use those, instead of spamming those battery draining incessant TCP keep-alives. Numerous messenger apps solve this problem, none drains the battery as bad as kdeconnect does. > Please do the test as requested by vladikss. Without some evidence that a > change actually makes a difference, it's just a random number. I am not the author, maintainer or QA of kdeconnect. That's why vladikss' request to expend my time and effort to do tests or experiments for him sounds rather wild to me. I have taken the time to provide an accurate description of the problem, root cause analysis and a working solution. That's the best I can do for kdeconnect. Conceptually, I have shown you the light. Whether to follow the light or stay in the dark is up to kdeconnect authors and maintainers. I don't care if they prefer staying in the dark. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 448315] New: Touchpad System Settings don't apply upon reconnecting
https://bugs.kde.org/show_bug.cgi?id=448315 Bug ID: 448315 Summary: Touchpad System Settings don't apply upon reconnecting Product: systemsettings Version: 5.23.5 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_touchpad Assignee: plasma-b...@kde.org Reporter: maxim.yegorush...@gmail.com Target Milestone: --- Touchpad System Settings don't apply upon reconnecting Apple Magic Trackpad 2. I set "Tap-to-click" option in System Settings, Touchpad for device "Apple Magic Inc. Trackpad 2". When I reboot or reconnect the trackpad this option is set but has no effect, which is a bug. I have to disable "Tap-to-click", apply, enable it again and apply for it to come into effect. STEPS TO REPRODUCE Connect the trackpad, set "Tap-to-click" and apply. Observe that it has an effect. Reboot. Connect the trackpad. OBSERVED RESULT Observe that despite "Tap-to-click" option being set, it has no effect. EXPECTED RESULT "Tap-to-click" option comes into effect. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE neon 5.23 KDE Plasma Version: 5.23.5 KDE Frameworks Version: 5.89.0 Qt Version: 5.15.3 -- 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 Maxim Kuznetsov changed: What|Removed |Added CC||macku...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 395725] Blur effect applied to decoration shadows
https://bugs.kde.org/show_bug.cgi?id=395725 Maxim Kuznetsov changed: What|Removed |Added CC||macku...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 340982] No way to change just the date format but not its actual translated text
https://bugs.kde.org/show_bug.cgi?id=340982 --- Comment #200 from Maxim Egorushkin --- I did my +1 to this bug in 2016, and this issue appeared to be trivial at the time for me, a fellow (naive) C++ developer, and a big fan of KDE Plasma. It is a bit hard for me to fathom that such a seemingly trivial issue, not even a bug but oversight in my eyes, couldn't be fixed easily. The comments here suggest that the issue stems from a design oversight, in that KDE Plasma is incapable of using user defined time/date formats independently of a system-wide locale. Could there be an option to create another system-wide locale which forks an existing locale, but overrides date-time format (and other formats, if desired), and could be used by KDE Plasma? May be a locale that overrides date-time formats with ISO ones? I wanted to take a look into this issue but couldn't find easy guides how to check out KDE Plasma source, build it, and run it without destroying my existing KDE Neon desktop environment. That was in 2016, may be things changed for better since then. This is a rather annoying and unexpectedly difficult bug for the most configurable DE, IMO, which is KDE Plasma. It didn't prevent me from doing my tasks though, I can still sort by date asc/desc in Dolphin and that works as expected. The dates and times don't look ISO-well-formed, but Dolphin does sort by the timestamp correctly, and that's usable enough. Elsewhere, I use: * In `bash`: `alias ll="ls -al --time-style=long-iso --block-size=\'1"` * In `emacs`: `(custom-set-variables ... (dired-listing-switches "-al --time-style=long-iso --block-size='1") ... )` -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 340982] No way to change just the date format but not its actual translated text
https://bugs.kde.org/show_bug.cgi?id=340982 --- Comment #202 from Maxim Egorushkin --- (In reply to Kevin Kofler from comment #201) > Well, the thing is, Qt does not actually use the system-wide locales, i.e., > glibc/POSIX locales. What it does is map the glibc locale to a Unicode > locale and then use that with ICU and/or with bundled copies of Unicode > tables within Qt. So just inventing a glibc locale would not fix it, because > it would not map to anything in Qt. And the tables in Qt are hardcoded and > cannot be extended at runtime. > > IMHO, the whole QLocale system should be thrown away / ignored / blacklisted > (just like, e.g., QHttp) and KDE code ported to a resurrected KLocale (based > on the old kdelibs 3 code, not on QLocale) instead. I am not sure if begging open-source developers ever worked, because someone has to pay the work, unless the developer wants to make a name with changes for themselves, which could be a quite tall order here. Would you like to spec the changes, as well as time and money required to materialize those changes? Or anyone else still listening to this conversation? With that we can try crowdfunding the change and see what happens? -- You are receiving this mail because: You are watching all bug changes.
[kamoso] [Bug 421917] crashes on the 1st frame render.
https://bugs.kde.org/show_bug.cgi?id=421917 --- Comment #2 from Maxim Egorushkin --- (In reply to Christoph Feck from comment #1) > Crash is in the NVIDIA binary OpenGL drivers. If this is reproducible, > please report this issue directly to NVIDIA developers via > https://forums.developer.nvidia.com/t/if-you-have-a-problem-please-read-this- > first/27131 No other video application crashes in NVidia drivers, apart from kamoso. Given that, it is much more likely the bug is in kamoso, not NVidia drivers. But I know some developers refuse to investigate and fix their bugs when they see nvidia binary driver in the stack trace. -- You are receiving this mail because: You are watching all bug changes.
[kamoso] [Bug 421917] crashes on the 1st frame render.
https://bugs.kde.org/show_bug.cgi?id=421917 --- Comment #4 from Maxim Egorushkin --- (In reply to Christoph Feck from comment #3) > If we had the sources of the driver we could investigate. The backtrace > doesn't even have symbol information for the driver to check which function > was being called. Some more info: VideoMaterial::bindTexture calls glTexImage2D and this call crashes: #12 0x7fffc1e5c4ac in VideoMaterial::bindTexture(int, unsigned char const*) () from /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstqt5videosink.so (gdb) disassemble Dump of assembler code for function _ZN13VideoMaterial11bindTextureEiPKh: 0x7fffc1e5c460 <+0>: movsxd rsi,esi 0x7fffc1e5c463 <+3>: push r12 0x7fffc1e5c465 <+5>: push rbp 0x7fffc1e5c466 <+6>: push rbx 0x7fffc1e5c467 <+7>: learbx,[rdi+rsi*4] 0x7fffc1e5c46b <+11>:movrbp,rdi 0x7fffc1e5c46e <+14>:movedi,0xde1 0x7fffc1e5c473 <+19>:movr12,rdx 0x7fffc1e5c476 <+22>:movesi,DWORD PTR [rbx+0x2c] 0x7fffc1e5c479 <+25>:call 0x7fffc1e56b40 0x7fffc1e5c47e <+30>:movsxd rax,DWORD PTR [rbx+0x50] 0x7fffc1e5c482 <+34>:subrsp,0x8 0x7fffc1e5c486 <+38>:movecx,DWORD PTR [rbx+0x38] 0x7fffc1e5c489 <+41>:movedx,DWORD PTR [rbp+0x6c] 0x7fffc1e5c48c <+44>:xorr9d,r9d 0x7fffc1e5c48f <+47>:xoresi,esi 0x7fffc1e5c491 <+49>:movedi,0xde1 0x7fffc1e5c496 <+54>:addr12,rax 0x7fffc1e5c499 <+57>:push r12 0x7fffc1e5c49b <+59>:moveax,DWORD PTR [rbp+0x70] 0x7fffc1e5c49e <+62>:push rax 0x7fffc1e5c49f <+63>:moveax,DWORD PTR [rbp+0x68] 0x7fffc1e5c4a2 <+66>:push rax 0x7fffc1e5c4a3 <+67>:movr8d,DWORD PTR [rbx+0x44] 0x7fffc1e5c4a7 <+71>:call 0x7fffc1e56ad0 => 0x7fffc1e5c4ac <+76>:addrsp,0x20 0x7fffc1e5c4b0 <+80>:movedx,0x2601 0x7fffc1e5c4b5 <+85>:movesi,0x2800 0x7fffc1e5c4ba <+90>:movedi,0xde1 0x7fffc1e5c4bf <+95>:call 0x7fffc1e56340 0x7fffc1e5c4c4 <+100>: movedx,0x2601 0x7fffc1e5c4c9 <+105>: movesi,0x2801 0x7fffc1e5c4ce <+110>: movedi,0xde1 0x7fffc1e5c4d3 <+115>: call 0x7fffc1e56340 0x7fffc1e5c4d8 <+120>: movedx,0x812f 0x7fffc1e5c4dd <+125>: movesi,0x2802 0x7fffc1e5c4e2 <+130>: movedi,0xde1 0x7fffc1e5c4e7 <+135>: call 0x7fffc1e56340 0x7fffc1e5c4ec <+140>: poprbx 0x7fffc1e5c4ed <+141>: poprbp 0x7fffc1e5c4ee <+142>: popr12 0x7fffc1e5c4f0 <+144>: movedx,0x812f 0x7fffc1e5c4f5 <+149>: movesi,0x2803 0x7fffc1e5c4fa <+154>: movedi,0xde1 0x7fffc1e5c4ff <+159>: jmp0x7fffc1e56340 Registers in glTexImage2D just before the crash: Thread 15 "QSGRenderThread" hit Breakpoint 1, 0x70866700 in glTexImage2D () from /usr/lib/x86_64-linux-gnu/libGL.so.1 (gdb) info registers rax0x1907 6407 rbx0x7fff881b5da4 140735476882852 rcx0x7f 127 rdx0x8051 32849 rsi0x0 0 rdi0xde13553 rbp0x7fff881b5da0 0x7fff881b5da0 rsp0x7fff9f7fd678 0x7fff9f7fd678 r8 0x7f 127 r9 0x0 0 r100x1 1 r110x3f80 1065353216 r120x7fff98e56593 140735758558611 r130x7fff940266b0 140735676573360 r140x7fff9f7fd760 140735869343584 r150x7fff8816a140 140735476572480 rip0x70866700 0x70866700 eflags 0x206[ PF IF ] cs 0x33 51 ss 0x2b 43 ds 0x0 0 es 0x0 0 fs 0x0 0 gs 0x0 0 (gdb) x/4xa $rsp 0x7fff9f7fd678: 0x7fffc1e5c4ac <_ZN13VideoMaterial11bindTextureEiPKh+76> 0x1907 0x7fff9f7fd688: 0x1401 0x7fff98e56593 The first 6 args of glTexImage2D are in registers above, the other 3 args are in the stack. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 491399] Plasma panel disappears after unlocking screen
https://bugs.kde.org/show_bug.cgi?id=491399 --- Comment #28 from Maxim Egorushkin --- (In reply to Nate Graham from comment #26) > Thanks. This sounds quite a bit like Bug 467422, which was ultimately traced > to a faulty HDMI cable. Any chance you could try using a different cable to > rule that out? The bug I experience is triggered by having desktop notifications on when the screen is locked, perfectly reproducible, as I documented above. There is no evidence suggesting faulty hardware hypothesis. Should I open a new bug report? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 491399] Plasma panel disappears after unlocking screen
https://bugs.kde.org/show_bug.cgi?id=491399 Maxim Egorushkin changed: What|Removed |Added CC||maxim.yegorush...@gmail.com --- Comment #13 from Maxim Egorushkin --- I experience the same problem of the panel disappearing after the monitor goes off due to inactivity and then back on. I have one panel only, at the top. Some existing windows then resize to fill the gap at the top where the panel was. The desktop also seem to disappear - no icons, right click doesn't open a menu. Keyboard shortcuts for KRunner, system settings, switching windows and desktops still work. I have one DP monitor connected to the system. Operating System: KDE neon 6.0 KDE Plasma Version: 6.1.4 KDE Frameworks Version: 6.5.0 Qt Version: 6.7.2 Kernel Version: 6.8.0-40-lowlatency (64-bit) Graphics Platform: Wayland Processors: 32 × AMD Ryzen 9 5950X 16-Core Processor Memory: 125.7 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 4090/PCIe/SSE2 Manufacturer: Gigabyte Technology Co., Ltd. Product Name: X570 AORUS MASTER System Version: -CF -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 491399] Plasma panel disappears after unlocking screen
https://bugs.kde.org/show_bug.cgi?id=491399 --- Comment #14 from Maxim Egorushkin --- (In reply to Waqar Ahmed from comment #6) > I haven't found any concrete way to reproduce this so far Reproduction steps: 1. Enable notifications (turn off "do not disturb"). 2. Connect Bluetooth headphones. 3. Lock the screen and wait till the monitor turns off. 4. Turn off the Bluetooth headphones. 5. Unlock the screen. 6. Observe that the panel is gone. Sometimes, there is a volume OSD stuck in a random place on the screen, cannot be removed. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 491399] Plasma panel disappears after unlocking screen
https://bugs.kde.org/show_bug.cgi?id=491399 --- Comment #15 from Maxim Egorushkin --- (In reply to Maxim Egorushkin from comment #14) > (In reply to Waqar Ahmed from comment #6) > > I haven't found any concrete way to reproduce this so far > > Reproduction steps: > > 1. Enable notifications (turn off "do not disturb"). > 2. Connect Bluetooth headphones. > 3. Lock the screen and wait till the monitor turns off. > 4. Turn off the Bluetooth headphones. > 5. Unlock the screen. > 6. Observe that the panel is gone. Sometimes, there is a volume OSD stuck in > a random place on the screen, cannot be removed. Thinking more about the root cause of the issue, the audio device change OSD and volume OSD are displayed regardless of whether notifications are in "do not disturb" mode or not. There is no audio playing, and notification sounds are disabled in the "Colours & Theme -> System Sounds" on my system, when I turn the Bluetooth headphones off. The problem seems to occur only when notifications are not in "do not disturb" mode. Which suggests that notification pop-ups could be crashing the panel when the only monitor turns off. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 491399] Plasma panel disappears after unlocking screen
https://bugs.kde.org/show_bug.cgi?id=491399 --- Comment #20 from Maxim Egorushkin --- (In reply to Nate Graham from comment #16) > When this happens, is it just the panel that's gone? Or the wallpaper on > that panel's screen, too? For me, when that happens my desktop icons are gone, no desktop context menu. My black colour wallpaper might still be there, hard to tell. This happens in Wayland session, not X11. -- You are receiving this mail because: You are watching all bug changes.
