[konsole] [Bug 279915] "exec daemon konsole" fails
https://bugs.kde.org/show_bug.cgi?id=279915 Askar Safin <safinas...@mail.ru> changed: What|Removed |Added Resolution|UNMAINTAINED|--- Status|RESOLVED|REOPENED --- Comment #14 from Askar Safin <safinas...@mail.ru> --- What happened? Why closed with RESOLVED UNMAINTAINED? -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 374229] New: "modified" icon (floppy) is not synchronized between different windows
https://bugs.kde.org/show_bug.cgi?id=374229 Bug ID: 374229 Summary: "modified" icon (floppy) is not synchronized between different windows Product: kate Version: 16.08 Platform: Debian testing OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: safinas...@mail.ru Target Milestone: --- steps to reproduce: $ : > /tmp/a $ kate /tmp/a type space into opened file. you will see "modified" icon (floppy). open new window. it will not have this icon. Also, I often see that one window has "modified" icon and another window has not in different situations. So, double check that this icon is always synchronized. version 16.08.2 on debian stretch -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 256561] Katepart scrolls per paragraph rather than what is set globally (e.g. 3 lines)
https://bugs.kde.org/show_bug.cgi?id=256561 Askar Safin <safinas...@mail.ru> changed: What|Removed |Added CC||safinas...@mail.ru --- Comment #26 from Askar Safin <safinas...@mail.ru> --- [Here is comment about ad-hoc fixing this bug for particular system, you can safely skip it] I just made very simple patch based on https://bugs.kde.org/show_bug.cgi?id=256561#c21 . Here is my patch: https://zerobin.net/?0847ca5b9dec86f7#VxKX5KW7TUFqSD/yRddFQ8xitE3N2mP3yT37IrvA2bM= . It is obviously wrong (it doesn't handle "Shift" and pixel-based scrolling) and bad (hard-coded numeric constants). The patch prepared by editing current "master", i. e. 9ef9669733138b46019882fc535d9fa5097a1d29, but I didn't test whether "master" with my patch really builds. I tested the patch by applying it to debian source package ktexteditor 5.28.0-2. And patch fixes the bug. Tested on debian stretch amd64. Of course, don't pick the patch to upstream, it is just for people who want to patch their local kate -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 414635] New: Very strange code at main.cpp
https://bugs.kde.org/show_bug.cgi?id=414635
Bug ID: 414635
Summary: Very strange code at main.cpp
Product: Spectacle
Version: 19.11.80
Platform: Debian stable
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: General
Assignee: m...@baloneygeek.com
Reporter: safinas...@mail.ru
CC: k...@david-redondo.de
Target Milestone: ---
I am attempting to understand how Spectacle works. So I read its code. I found
the following very strange code in Main.cpp in current master (
4370c5484972a02497bf4bb479f4cc1586b6924c ,
https://github.com/KDE/spectacle/blob/4370c5484972a02497bf4bb479f4cc1586b6924c/src/Main.cpp
):
} else if (lCmdLineParser.isSet(QStringLiteral("windowundercursor"))) {
lCaptureMode = Spectacle::CaptureMode::TransientWithParent;
} else if (lCmdLineParser.isSet(QStringLiteral("transientonly"))) {
lCaptureMode = Spectacle::CaptureMode::WindowUnderCursor;
This seems like a typo. It seems the following code should be:
} else if (lCmdLineParser.isSet(QStringLiteral("windowundercursor"))) {
lCaptureMode = Spectacle::CaptureMode::WindowUnderCursor;
} else if (lCmdLineParser.isSet(QStringLiteral("transientonly"))) {
lCaptureMode = Spectacle::CaptureMode::TransientWithParent;
Even if this is not typo, please add some comment, which will explain such
strange code. Or (better) rename something to help people, who read you code.
I am reading code of Spectacle, because I'm trying to capture video from screen
in my very unusual scenario, see https://bugs.kde.org/show_bug.cgi?id=412731 if
you are interested
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 412731] Please add API to get list of all window IDs on Wayland (so that I can iterate over them and make screenshots using org.kde.kwin.Screenshot)
https://bugs.kde.org/show_bug.cgi?id=412731 --- Comment #2 from Askar Safin --- (In reply to David Edmundson from comment #1) > Why? Surely you know which windows you want in advance. This is my task. In X11 this worked. In Wayland it doesn't work, so we have no feature parity. My computer often crashes for various reasons. So I want to record videos from each of opened windows. So that after crash I can restore state of this windows. Reasons for crashes are really diverse. Not only software crashes or power outages but also physical force. For example one day I was angry and I hit table where was my laptop, and then this laptop forcibly rebooted. > There won't be a way for programs to get screenshots without some user > interaction for security purposes. Currently such way exists even on Wayland. This command: dbus-send --dest=org.kde.KWin --print-reply /Screenshot org.kde.kwin.Screenshot.screenshotFullscreen create screenshot without user interaction. > We do have pipewire support. Does you have way to capture pipewire stream from particular window? (I want to get list of all windows and capture them all, even covered ones.) I have read https://flatpak.github.io/xdg-desktop-portal/portal-docs.html and it seems that I can capture video either from whole screen, either from some my own window. It seems capturing window of other app is not supported -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 412731] Please add API to get list of all window IDs on Wayland (so that I can iterate over them and make screenshots using org.kde.kwin.Screenshot)
https://bugs.kde.org/show_bug.cgi?id=412731 Askar Safin changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #4 from Askar Safin --- (In reply to David Edmundson from comment #3) > I am happy to help do what we need to address any valid use cases, if we can > solve them properly. Thanks a lot! > However, I still don't yet understand, how does this > help with a crash? I often have something like 50 various windows opened. When my computer crashes, of course, I am completely disappointed and frustrated. Because all information about state of my computer and all information about my work is lost. In some sense set of opened windows *is* to-do list. When I start to do something, I open relevant windows. Then this work may for some reason become postponed and some new urgent work may appear. Then I open new windows (without closing previous set of windows). This can happen a lot of times and then I may got 50+ windows, some of them are "new" (i. e. opened recently) and some "old" (i. e. I saw them very lot of time ago). I rarely reboot my computer and I often use hibernate. So, I want to record video from every window. If my computer crashes, I will watch all this videos (with a paper and pencil in my hands) and thus I will be able to open all this windows again restoring their state. You may ask: why you need to watch video, why not just see the last screenshot? Well, there is a lot of programs, such that their state cannot be restored by last screenshot. For example, browser window with tabs. I need to watch video in reverse order starting from last screenshot until all tabs will show up in video. Same for konsole windows. I need to watch entire video to see all commands and their output. Last screenshot will show me only few last commands. So I will watch all this videos in reverse order from last screenshot until all information from this particular video is restored. Okey, what I do currently? Currently I don't have such program. I use X11, and I simply record video from whole screen using "ffmpeg -f x11grab". When my computer crashes I watch this video (with a paper and pencil) from last frame until all windows will show up in video and all information from them is restored. I usually restart video capturing once a day and unminimize all windows to make sure all they are captured. So in case of crash I need to watch no more than last day. Watching such video usually takes whole day. What programs I use? Most of time I use 3 programs only: konsole, chromium and kate/kwrite. Usually I have lots of konsole windows opened, lots of chromium windows opened and a few kate/kwrite windows. Currently I have 8 konsoles and 11 chromiums (i. e. 19 windows). This is good situation, often windows count is more. You may ask: why not just use build-in capabilities in this programs for restoring state? Chromium can restore tabs, kate can restore unsaved files and for konsole we have .bash_history. Well, this is true, but unfortunately all this features are not complete. Let's begin from Chromium. Usually it restores form data correctly. But unfortunately sometimes this just fails. Also, Chromium doesn't restore form data for dynamically created form elements. If I remember correctly Chromium dev even said to me in bug tracker that Chromium will never restore form data in dynamically created elements. For example, go open https://paste.gg/ . Then click "Add file". Additional dynamically created will open. Type some text to it, then crash your browser and restore tabs. That text will be lost. Now let's speak about konsole. I use konsole windows as to-do list in some sense. Let me explain. For example, I created some file or directory using konsole. Say, I typed "mkdir /some-dir". Then I will not close this window while I need this dir. I. e. this window serves as reminder that this directory exists and that I should delete it when it becomes not needed. So I need to restore all konsole windows. To know what files and dirs I created to know that I should delete them. Of course, all this applies not only to files and dirs, but to other things, too. For example, I temporary moved some file from one place to another. Then this konsole window with "mv" command serves as reminder that this file should be moved back. Etc, etc. Okey, what about .bash_history? Well, first of all, in case of hard crash commands in opened windows are lost (because bash writes .bash_history at exit). But bash can be configured to write command to history immediately. So, let us assume we configured bash so. What next? Well, then .bash_history will contain all commands. From opened windows and from closed. But I need from opened only! Because they are in
[kwin] [Bug 412731] New: Please add API to get list of all window IDs on Wayland (so that I can iterate over them and make screenshots using org.kde.kwin.Screenshot)
https://bugs.kde.org/show_bug.cgi?id=412731 Bug ID: 412731 Summary: Please add API to get list of all window IDs on Wayland (so that I can iterate over them and make screenshots using org.kde.kwin.Screenshot) Product: kwin Version: 5.14.5 Platform: Debian unstable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: safinas...@mail.ru Target Milestone: --- My final task is this: I want to capture videos from all my opened videos. Every window should produce its own video. Even covered windows should produce video and ideally minimized ones, too. Currently I do this using small C++ program written using Xlib. Unfortunately the world is moving to Wayland, so I start to research how to do similar thing on Wayland. I discovered that Wayland (as opposed to X11) doesn't have standard way to get window images, so I should use some tricks, specific for particular Wayland server implementation. (Note here: yes, I know about xdg-desktop-portal, but as well as I know it doesn't give a way to take screenshot or a video from particular specified window, so xdg-desktop-portal is not for me.) So I started to research my Wayland server implementation, i. e. kwin_wayland. I discovered that kwin_wayland offers a way to take screenshot of a particular window: dbus-send --dest=org.kde.KWin /Screenshot org.kde.kwin.Screenshot.screenshotForWindow Unfortunately, I was unable to understand what is this . On X11 this is (it seems) usual X11 window id. But on Wayland?! And how to get list of such ids? So, I ask for adding some way to get list of all IDs suitable to pass to org.kde.kwin.Screenshot.screenshotForWindow . Preferably this should be another dbus interface. This will allow me to write program I need. This program will repeatedly call screenshotForWindow for all windows on the system, thus creating videos. Without such interface "screenshotForWindow" is completely useless and should be removed. Also screenshotForWindow doesn't take fd as opposed to other functions in org.kde.kwin.Screenshot . This is bad, too, please, fix this. SOFTWARE/OS VERSIONS Linux Debian sid (created Oct 2019) amd64. KDE Plasma. Wayland (available in About System) KDE Plasma Version: 5.14.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.11.3 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 412731] Please add API to get list of all window IDs on Wayland (so that I can iterate over them and make screenshots using org.kde.kwin.Screenshot)
https://bugs.kde.org/show_bug.cgi?id=412731 --- Comment #6 from Askar Safin --- >>This program is unfinished, so I currently don't use it >I think this says a lot Hi. Things changed. I rewrote my program from xlib to xcb and added some features. I used it successfully from 2020-05-09 to today (2020-09-12) and I will continue to use it. It records all opened windows simultaneously. I. e. not whole desktop, but each windows separately. I. e. the program does exactly what I want. I runs on top of KDE on X11. And it seems it is currently impossible to port it to kwin-wayland. For all this time my computer never crashed. Except for today. Today the computer crashed and I was able successfully restore state of my computer using captured video. So I write this success report -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 317964] Cursor won't move forward to the next instance when using ^, $, or ^$ and regex
https://bugs.kde.org/show_bug.cgi?id=317964 --- Comment #7 from Askar Safin --- The bug is not reproducible in kate in latest debian sid. (Kate 20.08.2) -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 363280] New: highlighting: c++: #if 1 #endif #if defined (A) aaa #elif defined (B) bbb #endif
https://bugs.kde.org/show_bug.cgi?id=363280 Bug ID: 363280 Summary: highlighting: c++: #if 1 #endif #if defined (A) aaa #elif defined (B) bbb #endif Product: kate Version: 3.14.2 Platform: Debian stable OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: part Assignee: kwrite-bugs-n...@kde.org Reporter: safinas...@mail.ru - Reproducible: Always Steps to Reproduce: Open some C++ file in Kate 3.14.2 or KDevelop 4.7.0. Type: #if 1 #endif #if defined (A) aaa #elif defined (B) bbb #endif Actual Results: "defined (B)" and "bbb" will be gray Expected Results: "defined (B)" should be green like "defined (A)" and "bb" should be black like "aaa" Debian GNU/Linux Jessie -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 366014] New: if i minimize current split view it remains to be active
https://bugs.kde.org/show_bug.cgi?id=366014 Bug ID: 366014 Summary: if i minimize current split view it remains to be active Product: kate Version: 3.14.2 Platform: Debian stable OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: safinas...@mail.ru - Reproducible: Always Steps to Reproduce: 1. Open two vertical split views in kate 2. Activate (say) right view 3. Resize right view to size 0. I. e. make it so small that it will disappear Actual Results: Right view will remain to be active. Yes, it has size 0 and it is completely invisible, but it is still active. If I type some characters, they will go to this active view. Of course, user will be very frustrated. He will think: "I type characters, why they don't appear?" They actually appear at invisible view. If I click at some files at "Documents" (i. e. at "Documents" panel), then that active view will open this file, completely invisible for me Expected Results: Right view should deactivate when I resize it to zero -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 366014] if i minimize current split view it remains to be active
https://bugs.kde.org/show_bug.cgi?id=366014 --- Comment #3 from Askar Safin <safinas...@mail.ru> --- Personally for me this is acceptable solution -- You are receiving this mail because: You are watching all bug changes.
