[plasmashell] [Bug 435220] Cannot paste text copied from firefox outside firefox in wayland session
https://bugs.kde.org/show_bug.cgi?id=435220 --- Comment #1 from Kiril Vladimiroff --- I can also reproduce this... occasionally. It's frustrating when it happens (dragging also doesn't work), but it's pretty hard to make a reproducible case. It _starts_ to happen sometimes, at some point. Restarting klipper and/or plasmashell doesn't seem to help. Logout->login fixes it for a while. What info should be gathered, when it starts to happen, in order for this to get tracked down? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 426429] Bad font rendering in sound settings comboboxs
https://bugs.kde.org/show_bug.cgi?id=426429 --- Comment #8 from Kiril Vladimiroff --- Not sure if that's the case. I'm not using fractional scaling and can not reproduce Bug 435456. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 426429] Bad font rendering in sound settings comboboxs
https://bugs.kde.org/show_bug.cgi?id=426429 Kiril Vladimiroff changed: What|Removed |Added Ever confirmed|0 |1 Status|RESOLVED|REOPENED Resolution|UPSTREAM|--- -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 426429] Bad font rendering in sound settings comboboxs
https://bugs.kde.org/show_bug.cgi?id=426429 Kiril Vladimiroff changed: What|Removed |Added CC||ki...@vladimiroff.org --- Comment #6 from Kiril Vladimiroff --- Created attachment 137923 --> https://bugs.kde.org/attachment.cgi?id=137923=edit Bad font rendering with Qt 5.15.2 @Christopher Feck, could you provide a link to the upstream fix? I can still reproduce this pretty much only in sound settings (as far as I can tell). Running Fedora Rawhide: KDE Plasma Version: 5.21.4 KDE Frameworks Version: 5.81.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[klipper] [Bug 424649] [Wayland] Impossible to paste copied text after the source app to be closed even if the text is in Klipper
https://bugs.kde.org/show_bug.cgi?id=424649 Kiril Vladimiroff changed: What|Removed |Added CC||ki...@vladimiroff.org -- You are receiving this mail because: You are watching all bug changes.
[klipper] [Bug 433165] Klipper still doesn't work properly on Wayland
https://bugs.kde.org/show_bug.cgi?id=433165 Kiril Vladimiroff changed: What|Removed |Added CC||ki...@vladimiroff.org -- You are receiving this mail because: You are watching all bug changes.
[klipper] [Bug 435220] Cannot paste text copied from firefox outside firefox in wayland session
https://bugs.kde.org/show_bug.cgi?id=435220 Kiril Vladimiroff changed: What|Removed |Added CC||ki...@vladimiroff.org -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 332512] Plasma Popups aren't resizable, and if you force-resize them, they forget their size after the computer or plasmashell is restarted
https://bugs.kde.org/show_bug.cgi?id=332512 Kiril Vladimiroff changed: What|Removed |Added CC||ki...@vladimiroff.org -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 392470] konsole: Ctrl-/ key sequence only sends / to running program (wayland)
https://bugs.kde.org/show_bug.cgi?id=392470 Kiril Vladimiroff changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED --- Comment #5 from Kiril Vladimiroff --- As somebody who suffered from this, I can confirm that the issue seems to be fixed now. Konsole 20.08.1 KDE Frameworks 5.75.0 Qt 5.15.1 (built against 5.15.1) KWin 5.20.2 running on wayland -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 413387] Unable to unlock after wake up
https://bugs.kde.org/show_bug.cgi?id=413387 Kiril Vladimiroff changed: What|Removed |Added CC||ki...@vladimiroff.org -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 415249] Tab goes unresponsive if copying in tmux copy mode
https://bugs.kde.org/show_bug.cgi?id=415249 Kiril Vladimiroff changed: What|Removed |Added CC||ki...@vladimiroff.org -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 403609] Znc password issue
https://bugs.kde.org/show_bug.cgi?id=403609 Kiril Vladimiroff changed: What|Removed |Added CC||ki...@vladimiroff.org --- Comment #1 from Kiril Vladimiroff --- Several clients started suffering from that due to not sending `:` before the password. See https://github.com/znc/znc/issues/1531 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 409517] [Wayland] KMail freezes
https://bugs.kde.org/show_bug.cgi?id=409517 Kiril Vladimiroff changed: What|Removed |Added CC||ki...@vladimiroff.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396437] Crash when unplug HDMI cable while session is locked
https://bugs.kde.org/show_bug.cgi?id=396437 Kiril Vladimiroff changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |WORKSFORME --- Comment #2 from Kiril Vladimiroff --- Decided to try reproducing this again now with plasma 5.16 and I can't anymore on the very same machine this has been reported. Plasma 5.16.2 KDE Frameworks 5.59.0 Qt: 5.13.0 Kernel 5.1.15 No idea if it has been fixed (un)intentionally at some point or I've changed some subtle setting which stopped causing this. In any case since I'm no longer able to provide help with debugging it's better to close it. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 409444] New: Connecting to WireGuard server fails with missing plugin
https://bugs.kde.org/show_bug.cgi?id=409444 Bug ID: 409444 Summary: Connecting to WireGuard server fails with missing plugin Product: plasma-nm Version: 5.16.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: applet Assignee: jgrul...@redhat.com Reporter: ki...@vladimiroff.org Target Milestone: --- SUMMARY This looks like a regression from plasma 5.15.x. I have added wireguard connection (via the configuration applet) which used to work just fine then. After 5.16.0 I'm able to connect to it only via `nmcli` (e.g. `nmcli c up `). Simply choosing it from the applet fails with "Missing VPN plugin" notification. Funny side-effect after connecting via `nmcli` is that I see the wireguard connection listed twice under "Active connections" and disconnecting from there works. STEPS TO REPRODUCE 1. Add wireguard connection 2. Try to connect to it using the "Connect" button in the applet from tray area (for instance) OBSERVED RESULT Connection is NOT getting activated and "Missing VPN plugin" notification is shown instead. EXPECTED RESULT WireGuard connection to become active. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 5.16.2 KDE Frameworks Version: 5.59.0 Qt Version: 5.13.0 Kernel version: 5.1.15 OS Type: 64-bit NetworkManager: 1.18.0 ADDITIONAL INFORMATION To confirm that the issue is not miss-configured NetworkManager and WireGuard: 1. Execute "nmcli c up " to confirm that networkmanager-wireguard is installed and working 2. Observe the connection listed twice under "Active connection" 3. Confirm that disconnecting works Looking at journalctl logs of NetworkManager I see no messages whatsoever when trying to connect via the applet. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408648] New: Tabs are dislocated until first change on vertical panel
https://bugs.kde.org/show_bug.cgi?id=408648 Bug ID: 408648 Summary: Tabs are dislocated until first change on vertical panel Product: plasmashell Version: 5.16.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: k...@davidedmundson.co.uk Reporter: ki...@vladimiroff.org CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 120839 --> https://bugs.kde.org/attachment.cgi?id=120839=edit Video recording of the bug SUMMARY When kickoff is on vertical panel tabs are dislocated and the first one is not quite visible. Once a tab is changed they're getting located properly everything is fine for the lifetime of plasmashell (i.e. ideally until logout). STEPS TO REPRODUCE 1. Add panel and pace it on left/right screen edge in order to make it vertical. 2. Add "Application Launcher" (kickoff) on it. 3. Open the application launcher 4. Change tabs 5. Close the launcher and open it again. OBSERVED RESULT Tabs are dislocated until first change. See the attached file (also available on: https://giant.gfycat.com/RepulsiveImmaterialJay.webm). SOFTWARE/OS VERSIONS KDE Plasma Version: 5.16.0 KDE Frameworks Version: 5.29.0 Qt Version: 5.12.3 Kernel Version: 5.1.9 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 397823] Shell is smaller than needed on two monitor
https://bugs.kde.org/show_bug.cgi?id=397823 --- Comment #8 from Kiril Vladimiroff --- > Please reopen if still an issue on Qt 5.12 Thanks, the bug is no longer reproducible. Not sure if it's because of Qt: Operating System: Arch Linux KDE Plasma Version: 5.14.5 Qt Version: 5.12.0 KDE Frameworks Version: 5.54.0 Kernel Version: 4.20.1-arch1-1-ARCH OS Type: 64-bit Should I close it or leave it as WAITINGFORINFO? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 397823] Shell is smaller than needed on two monitor
https://bugs.kde.org/show_bug.cgi?id=397823 --- Comment #6 from Kiril Vladimiroff --- This bug is still reproducible on my machine after updating plasma and frameworks. Operating System: Arch Linux KDE Plasma Version: 5.14.1 Qt Version: 5.11.2 KDE Frameworks Version: 5.51.0 Kernel Version: 4.18.14-arch1-1-ARCH OS Type: 64-bit -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 356359] Can't open documents with non-ascii filenames
https://bugs.kde.org/show_bug.cgi?id=356359 Kiril Vladimiroff changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #19 from Kiril Vladimiroff --- It's been three years since this bug was reported. Just tried to reproduce it on the same machine and it seems to be fixed now. Closing it with WORKSFORME, because I'm not sure when exactly this got fixed (whether intentionally or not). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 397823] Shell is smaller than needed on two monitor
https://bugs.kde.org/show_bug.cgi?id=397823 --- Comment #4 from Kiril Vladimiroff --- Created attachment 114573 --> https://bugs.kde.org/attachment.cgi?id=114573=edit Plasma log of running a session with two monitors Qt is 5.11.1 KDE Frameworks is 5.49.0 Both latest from archlinux "stable" (i.e. non-testing) repos. Restarting the session (or the whole computer for that matter) doesn't solve it. The issue is always reproducable. `plasma_log` file after that command is empty. I've just executed given command. Didn't do anything apart from waiting the session getting initialized and waiting a few seconds. Tried to add `2>&1` at the end of the command in order to record at least the stdout. There's plenty of things in there, see it attached. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 397823] New: Shell is smaller than needed on two monitor
https://bugs.kde.org/show_bug.cgi?id=397823 Bug ID: 397823 Summary: Shell is smaller than needed on two monitor Product: plasmashell Version: 5.13.4 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: generic-wayland Assignee: plasma-b...@kde.org Reporter: ki...@vladimiroff.org Target Milestone: 1.0 Created attachment 114570 --> https://bugs.kde.org/attachment.cgi?id=114570=edit screenshot of systemsettings going outside the shell I have two monitors with the same resolution. Even under wayland this worked until latest point release of 5.13 (at least in archlinux packages). This works in X11 plasma session. Another funny complication is the fact that XWayland windows can't receive mouse clicks when moved "outside" the desktop. Native wayland applications don't seem to be affected from this. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396437] New: Crash when unplug HDMI cable while session is locked
https://bugs.kde.org/show_bug.cgi?id=396437 Bug ID: 396437 Summary: Crash when unplug HDMI cable while session is locked Product: plasmashell Version: 5.13.3 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: generic-wayland Assignee: plasma-b...@kde.org Reporter: ki...@vladimiroff.org Target Milestone: 1.0 Steps to reproduce: 1. Start a Plasma wayland session with plugged second monitor via HDMI (it doesn't matter which one is done first). 2. Lock your screen. 3. Unplug the HDMI cable. 4. Observe how the whole session crashes immediately and get send back to login screen (SDDM in my case). Happens every time on my machine. Feel free to ping me what information I could provide. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 395850] Plasma applet deletion doesn't clean up global shortcuts
https://bugs.kde.org/show_bug.cgi?id=395850 --- Comment #4 from Kiril Vladimiroff --- Created attachment 113602 --> https://bugs.kde.org/attachment.cgi?id=113602=edit ~/.config/plasma-org.kde.plasma.desktop-appletsrc -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 395850] Plasma applet deletion doesn't clean up global shortcuts
https://bugs.kde.org/show_bug.cgi?id=395850 --- Comment #3 from Kiril Vladimiroff --- Created attachment 113601 --> https://bugs.kde.org/attachment.cgi?id=113601=edit ~/.config/kglobalshortcutsrc -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 395850] New: Adding and removing panels leave artifacts
https://bugs.kde.org/show_bug.cgi?id=395850 Bug ID: 395850 Summary: Adding and removing panels leave artifacts Product: plasmashell Version: 5.13.1 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: ki...@vladimiroff.org Target Milestone: 1.0 Created attachment 113553 --> https://bugs.kde.org/attachment.cgi?id=113553=edit SystemSettings screenshot of the "Audio Volume" hotkeys While trying different panel configuration, I've realized that removed panels leave artifacts. For instance, volume hotkeys in my case stopped working. Didn't think much about it and decided to re-define the hotkey. Please take a look at the attachment. It looks like every removed panel left its own increase/decrease volume hotkey. Not even sure now which is the correct one. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 376031] Panel completely disappears and is unretrievable
https://bugs.kde.org/show_bug.cgi?id=376031 Kiril Vladimiroff changed: What|Removed |Added CC||ki...@vladimiroff.org --- Comment #3 from Kiril Vladimiroff --- Bug is still reproducable in 5.13.1 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 392470] konsole: Ctrl-/ key sequence only sends / to running program (wayland)
https://bugs.kde.org/show_bug.cgi?id=392470 --- Comment #3 from Kiril Vladimiroff --- An easy way to reproduce this: In konsole execute `emacs -Q -nw` and hit `C-/`. You will see a / appearing on the last line of the buffer. Run `emacs -Q` (this will NOT run emacs in a terminal and open a GUI window instead) and hit `C-/`. You should see how the buffer goes empty and a text "Undo!" at minibuffer (status line at the bottom of the window). This is the desired behavior. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 392470] konsole: Ctrl-/ key sequence only sends / to running program (wayland)
https://bugs.kde.org/show_bug.cgi?id=392470 Kiril Vladimiroff changed: What|Removed |Added CC||ki...@vladimiroff.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 388009] New: Crash on copy file to mounted USB stick
https://bugs.kde.org/show_bug.cgi?id=388009 Bug ID: 388009 Summary: Crash on copy file to mounted USB stick Product: plasmashell Version: 5.11.4 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: ki...@vladimiroff.org CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.11.4) Qt Version: 5.10.0 Frameworks Version: 5.41.0 Operating System: Linux 4.14.5-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: I've plugged in a USB stick. Formatted it, using parted and mounted it via Device Notifier, without unplugging the stick. Then I've opened the folder where it was mounted via Dolphin and pasted a file. Plasma has crashed upon showing the transferring notification. It restarted itself afterwards, the transferring notification has shown and the operation finished successfully. - Plasma: 5.11 using official up-to date Arch linux packages. The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f0bbafce800 (LWP 8940))] Thread 18 (Thread 0x7f0a9f7fe700 (LWP 19082)): #0 0x7f0bb3d5738d in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f0bb4b9e00c in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f0af381d42f in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7f0af3822479 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7f0af381c924 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7f0af381fc83 in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7f0bb4b9cb2d in () at /usr/lib/libQt5Core.so.5 #7 0x7f0bb3d5108a in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f0bb44a442f in clone () at /usr/lib/libc.so.6 Thread 17 (Thread 0x7f0a9700 (LWP 19081)): #0 0x7f0bb3d5738d in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f0bb4b9e00c in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f0af381d42f in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7f0af3822479 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7f0af381c924 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7f0af381fc83 in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7f0bb4b9cb2d in () at /usr/lib/libQt5Core.so.5 #7 0x7f0bb3d5108a in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f0bb44a442f in clone () at /usr/lib/libc.so.6 Thread 16 (Thread 0x7f0ab0b80700 (LWP 19080)): #0 0x7f0bb3d5738d in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f0bb4b9e00c in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f0af381d42f in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7f0af3822479 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7f0af381c924 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7f0af38224d2 in () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7f0af381c924 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #7 0x7f0af38224d2 in () at /usr/lib/libKF5ThreadWeaver.so.5 #8 0x7f0af381c924 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #9 0x7f0af38224d2 in () at /usr/lib/libKF5ThreadWeaver.so.5 #10 0x7f0af381c924 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #11 0x7f0af38224d2 in () at /usr/lib/libKF5ThreadWeaver.so.5 #12 0x7f0af381c924 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #13 0x7f0af381fc83 in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #14 0x7f0bb4b9cb2d in () at /usr/lib/libQt5Core.so.5 #15 0x7f0bb3d5108a in start_thread () at /usr/lib/libpthread.so.0 #16 0x7f0bb44a442f in clone () at /usr/lib/libc.so.6 Thread 15 (Thread 0x7f0ab1381700 (LWP 19079)): #0 0x7f0bb3d5738d in pthread_cond_wait@@GLIBC_2.3.2 () at
[systemsettings] [Bug 381207] Allow the use of a solid color as the background instead of a wallpaper
https://bugs.kde.org/show_bug.cgi?id=381207 Kiril Vladimiroff <ki...@vladimiroff.org> changed: What|Removed |Added CC||ki...@vladimiroff.org -- You are receiving this mail because: You are watching all bug changes.
[telepathy] [Bug 371661] Incomplete Google Hangouts support in telepathy ?
https://bugs.kde.org/show_bug.cgi?id=371661 Kiril Vladimiroff <ki...@vladimiroff.org> changed: What|Removed |Added CC||ki...@vladimiroff.org -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 350364] error while inputing password with capital letters in kscreenlocker with kdeconnect
https://bugs.kde.org/show_bug.cgi?id=350364 Kiril Vladimiroff <ki...@vladimiroff.org> changed: What|Removed |Added CC||ki...@vladimiroff.org --- Comment #3 from Kiril Vladimiroff <ki...@vladimiroff.org> --- My password contains capital letters and it works smoothly when typing it from kdeconnect 1.0.3. -- You are receiving this mail because: You are watching all bug changes.
[kwalletmanager] [Bug 368314] kwalletmanager: "Export as XML..." produces empty file
https://bugs.kde.org/show_bug.cgi?id=368314 Kiril Vladimiroff <ki...@vladimiroff.org> changed: What|Removed |Added CC||ki...@vladimiroff.org -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 303848] BQM LensCorrection tool : doesn't work when 'use metadata' option is turned on
https://bugs.kde.org/show_bug.cgi?id=303848 Kiril Vladimiroff <ki...@vladimiroff.org> changed: What|Removed |Added CC||ki...@vladimiroff.org --- Comment #18 from Kiril Vladimiroff <ki...@vladimiroff.org> --- I have the same issue with digiKam 5.0.0. The lens auto-correction can't determine the subject distance (camera and lens are detected correctly) and instead of assuming default value like the image editor (i.e. 0.0) it fails completely. Is there a way to work-around this? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 351897] Plasma Shell freezes/hangs on file operations
https://bugs.kde.org/show_bug.cgi?id=351897 Kiril Vladimiroff <ki...@vladimiroff.org> changed: What|Removed |Added CC||ki...@vladimiroff.org -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 361008] "Require password after locking" setting is not respected in plasma 5.6
https://bugs.kde.org/show_bug.cgi?id=361008 --- Comment #5 from Kiril Vladimiroff <ki...@vladimiroff.org> --- Uhm... this is happening under X11 session. Could this still be related? -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 361008] "Require password after locking" setting is not respected in plasma 5.6
https://bugs.kde.org/show_bug.cgi?id=361008 Kiril Vladimiroff <ki...@vladimiroff.org> changed: What|Removed |Added CC||ki...@vladimiroff.org --- Comment #3 from Kiril Vladimiroff <ki...@vladimiroff.org> --- I suffer the same issue on Plasma 5.6 using Qt 5.6.0 (Arch's official packages). At first I though it might be a purely configuration issue in System Settings. However even after deleting my `~/.config/kscreenlockerrc` file and tweaking settings I got the same contents there. --> cat ~/.config/kscreenlockerrc [Daemon] LockGrace=15 Timeout=1 [Greeter] Theme=org.kde.breeze.desktop It requires password immediately after locking. I'm sure it's the Lock screen's settings performing the locking, because suspending session settings inside "Power Management" -> "Energe Saving" are set to way more than a minute. Also, I can confirm that this was working smoothly on the same machine with Plasma 5.5.x. @Martin, I would love to help by providing more information about my setup here and everything else that might help debugging this. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kcmutils] [Bug 349631] There is no possibility to configure my touchscreen
https://bugs.kde.org/show_bug.cgi?id=349631 Kiril Vladimiroff <ki...@vladimiroff.org> changed: What|Removed |Added CC||ki...@vladimiroff.org -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 359567] Compositor suspend when specific application is started
https://bugs.kde.org/show_bug.cgi?id=359567 --- Comment #16 from Kiril Vladimiroff <ki...@vladimiroff.org> --- Okay, I will be able to try this tomorrow and report if the issue is fixed. > But if it's this https://aur.archlinux.org/packages/spotify/ , I could just > test it myself (the CEF thingy is somehow statically linked? I don't see > relevant deps) Yes, this is the package that I'm using. If it's packaging issue, I will contact the package owner with a fix. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 359567] Compositor suspend when specific application is started
https://bugs.kde.org/show_bug.cgi?id=359567 --- Comment #14 from Kiril Vladimiroff <ki...@vladimiroff.org> --- > a) Does that "Football Manager 2016" client never sport (pun intended) > a WM_CLASS hint, or did you set it empty manually (because it also > adds WM_CLASS late)? It doesn't detect it. Even now when I try to create a new rule for it, I get these lines via the "Detect window properties" button: wmclass= wmclasscomplete=false wmclassmatch=1 > b) The pretty much means CEF is setting WM_CLASS after the map > request, what's rather an icccm violation > > Strictly spoken though, it must be set as long as the window is > withdrawn, maybe they keep it that state until it gets actually mapped > (while that's not helpful ;-) > > => We might have to sync after mapping the window and before applying > the rules? Can you try a patch (for kwin) - doesn't make sense to > relax things here if the client sets WM_CLASS some seconds later. I'm currently running a KWin from an offical Arch Linux package, but I could try applying a patch and compiling kwin, as long as I can apply it on top of the 5.5.4 tag. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 359567] Compositor suspend when specific application is started
https://bugs.kde.org/show_bug.cgi?id=359567 Kiril Vladimiroff <ki...@vladimiroff.org> changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #12 from Kiril Vladimiroff <ki...@vladimiroff.org> --- Thomas, you're right. I'm manually blocking the compositor and then complaining why it blocked. http://i.lvme.me/sgl679d.jpg -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 359567] Compositor suspend when specific application is started
https://bugs.kde.org/show_bug.cgi?id=359567 --- Comment #10 from Kiril Vladimiroff <ki...@vladimiroff.org> --- Created attachment 97297 --> https://bugs.kde.org/attachment.cgi?id=97297=edit ~/.config/kwinrulesrc No, but I use rules for sending particular windows to exact desktops and Spotify is one of them. What I've tried is to force-fully disable blocking composition for Spotify. (i.e. blockcompositing=false and blockcompositingrule=2), but it doesn't seem to change anything. I assume it doesn't help, because this option applies too late, since compositor is getting suspended before the actual appearance of the window and compositor is already suspended. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 359567] Compositor suspend when specific application is started
https://bugs.kde.org/show_bug.cgi?id=359567 --- Comment #8 from Kiril Vladimiroff <ki...@vladimiroff.org> --- 5.19.0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 359567] Compositor suspend when specific application is started
https://bugs.kde.org/show_bug.cgi?id=359567 --- Comment #6 from Kiril Vladimiroff <ki...@vladimiroff.org> --- Created attachment 97296 --> https://bugs.kde.org/attachment.cgi?id=97296=edit xprop output when clicking the Steam's login window -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 359567] Compositor suspend when specific application is started
https://bugs.kde.org/show_bug.cgi?id=359567 --- Comment #5 from Kiril Vladimiroff <ki...@vladimiroff.org> --- I knew that Spotify is using Chromium now, but I've ruled out Chromium to be responsible for this, because suspend doesn't happen when I start Chromium, Chrome or some Chrome app (like SlackDeck for example). However, I've just learned that Spotify is NOT a Chromium app, but uses Chromium Embedded Framework[1]. According to what I've been able to find the Steam client for Linux is also using CEF. Starting Steam involves updating (if not already up-to-date), logging in (if not already), before showing the actual client. The first two windows cause exactly the same issue: 1. Start Steam for the first time since weeks (i.e. it's not up-to-date) 2. Starts updating, showing a small window it a progress bar. 3. Composite goes to suspend. 4. I resume it with a shortcut. 5. Update is complete and login window is being showed. 6. Composite goes to suspend. 7. I resume it with a shortcut. 8. Successful login leads to opening the actual client window, *without* suspending the compositor. Once updated, if I simply start it (i.e. already logged in and up-to-date) it goes directly to step 8 and everything is fine. However if I log out, stop the client and try starting it again (i.e. still up-to-date, so steps 2, 3, 4 are omitted), the compositor gets suspended because of the login window. I will attach the output from xprop when clicking on the Steam's login window. Could it be that something in CEF is causing this? [1] https://en.wikipedia.org/wiki/Chromium_Embedded_Framework -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 359567] Compositor suspend when specific application is started
https://bugs.kde.org/show_bug.cgi?id=359567 --- Comment #4 from Kiril Vladimiroff <ki...@vladimiroff.org> --- Created attachment 97295 --> https://bugs.kde.org/attachment.cgi?id=97295=edit xprop output when clicking the spotify window Sure. However this is the output *after* the compositor is already suspended, because it happens before the actual appearance of Spotify's window. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 359567] Compositor suspend when specific application is started
https://bugs.kde.org/show_bug.cgi?id=359567 --- Comment #2 from Kiril Vladimiroff <ki...@vladimiroff.org> --- Forgot the mention that I can always reproduce this regardless of the "OpenGL interface" (i.e. EGL or GLX). The attached log is with EGL, though. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 359567] Compositor suspend when specific application is started
https://bugs.kde.org/show_bug.cgi?id=359567 --- Comment #1 from Kiril Vladimiroff <ki...@vladimiroff.org> --- Created attachment 97294 --> https://bugs.kde.org/attachment.cgi?id=97294=edit KWin output when Spotify is being started and stopped -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 359567] New: Compositor suspend when specific application is started
https://bugs.kde.org/show_bug.cgi?id=359567 Bug ID: 359567 Summary: Compositor suspend when specific application is started Product: kwin Version: 5.5.4 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: ki...@vladimiroff.org I'm going to use Spotify as an example here, because it's the only application I can *always* reproduce this with. It sometimes happens with LibreOffice applications, but haven't figured the pattern, yet. Reproducible: Always Steps to Reproduce: 1. Make sure compositor is enabled and working. 2. Start Spotify. Actual Results: Right after starting Spotify compositor is getting suspended. When I stop the application compositor resumes by itself. However, I'm able to resume it with my "Suspend compositing" shortcut and it works. Expected Results: Compositor shouldn't suspend when specific applications are being started, when the option "Suspend compositor for full screen windows" is disabled or the application is not on full screen. I've annotated the attached log of `kwin_x11 --replace` with when Spotify was started and stopped using lines starting with `###`. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 356359] Can't open documents with non-ascii filenames
https://bugs.kde.org/show_bug.cgi?id=356359 --- Comment #10 from Kiril Vladimiroff <ki...@vladimiroff.org> --- Not sure it's only due to the changed value of LANGUAGE. These settings should only modify LANGUAGE and LC_* env vars, as far as I get it, but I may be wrong. However, I'm 100% positive that that manipulating Regional settings can cause this bug, i.e. Okular is able to open document with non-ascii filenames, depending on specific regional formats settings. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 356359] Can't open documents with non-ascii filenames
https://bugs.kde.org/show_bug.cgi?id=356359 --- Comment #6 from Kiril Vladimiroff <ki...@vladimiroff.org> --- Dolphin: 15.08.3 KDE Frameworks: 5.16 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 356359] Can't open documents with non-ascii filenames
https://bugs.kde.org/show_bug.cgi?id=356359 --- Comment #4 from Kiril Vladimiroff <ki...@vladimiroff.org> --- While writing the bug report I didn't think there's a difference in how I "open" documents. After I found out that this assumption is wrong, I've described that in comment #2: > After trying to get this one confirmed by other users in #kde, several folks > there helped finding out that this issue occurs only when okular is invoked > by other application like Dolphin, Firefox (when pdf is downloaded), KMail > (when pdf file is received as an attachment), xdg-open, etc. If I use > kde-open the issue is the same, but the encoding seems to be different > (still not utf8, though), because the error is "Could not open > /home/kiril/desktop/???.pdf". Notice the question marks, instead of ... > those other funny symbols. > > However, if I simply execute "okular име.pdf" the file simply opens and > everything's fine. So, it looks like this issue is not in Okular in > particular, but it's the only place where I suffer from it. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 356359] New: Can't open documents with non-ascii filenames
https://bugs.kde.org/show_bug.cgi?id=356359 Bug ID: 356359 Summary: Can't open documents with non-ascii filenames Product: okular Version: 0.23.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: ki...@vladimiroff.org When I try to open a document named "име.pdf" I get the following error: "Could not open /home/kiril/име.pdf" (see the attached screenshot). When I rename the file using only ascii symbols, everything's fine. Even though my locales are strictly en_US.UTF8, it seems like Okular doesn't respect that. Output from the command "locale": LANG=en_US.UTF-8 LC_CTYPE="en_US.UTF-8" LC_NUMERIC="en_US.UTF-8" LC_TIME="en_US.UTF-8" LC_COLLATE="en_US.UTF-8" LC_MONETARY="en_US.UTF-8" LC_MESSAGES="en_US.UTF-8" LC_PAPER="en_US.UTF-8" LC_NAME="en_US.UTF-8" LC_ADDRESS="en_US.UTF-8" LC_TELEPHONE="en_US.UTF-8" LC_MEASUREMENT="en_US.UTF-8" LC_IDENTIFICATION="en_US.UTF-8" LC_ALL=en_US.UTF-8 P.S.: I'm assuming this is an issue in Okular, because everything else in cyrillic works just fine in other KDE applications (Plasma, Dolphin, Gwenview, etc.). Reproducible: Always Steps to Reproduce: 1. Open a regular .pdf document with ascii-only symbols in its name with Okular 2. Rename it by using cyrillic symbols, like "тест.pdf" for example 3. Try to open it again with Okular Actual Results: You get an error similar to "Could not open /home/.../.../ÑеÑÑ.pdf" Expected Results: Document should simply be opened, regardless of the non-ascii symbols in its name. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 356359] Can't open documents with non-ascii filenames
https://bugs.kde.org/show_bug.cgi?id=356359 --- Comment #1 from Kiril Vladimiroff <ki...@vladimiroff.org> --- Created attachment 95922 --> https://bugs.kde.org/attachment.cgi?id=95922=edit Could not open /home/kiril/име.pdf -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 356359] Can't open documents with non-ascii filenames
https://bugs.kde.org/show_bug.cgi?id=356359 --- Comment #2 from Kiril Vladimiroff <ki...@vladimiroff.org> --- After trying to get this one confirmed by other users in #kde, several folks there helped finding out that this issue occurs only when okular is invoked by other application like Dolphin, Firefox (when pdf is downloaded), KMail (when pdf file is received as an attachment), xdg-open, etc. If I use kde-open the issue is the same, but the encoding seems to be different (still not utf8, though), because the error is "Could not open /home/kiril/desktop/???.pdf". Notice the question marks, instead of ... those other funny symbols. However, if I simply execute "okular име.pdf" the file simply opens and everything's fine. So, it looks like this issue is not in Okular in particular, but it's the only place where I suffer from it. -- You are receiving this mail because: You are watching all bug changes.
