0

I run a process in a background (i.e. nobody attached) GNU screen session on a fresh Kubuntu machine (in a qemu vm). It starts very early during boot, runs for many minutes, and creates all kinds of output. Potentially that can be everything. At least it includes ansi escape sequences for colouring.

Later on, when I'm logged in to kde, start konsole and attach to it via 'screen -x', I get endless flickering. You can see some piece of output, but you can see how it builds the screen from top left to bottom right, character by character, then it instantly jumps back and repeats, and repeats, and repeats. Many times a second, so quite fast. Always with the same piece of output. It completely ignores any user input. In its 'status bar' I see 'Copy mode aborted' all the time.

In its current process state at that time, it should just show a prompt for user input and should not generate any new output at all.

Do you have an idea why it has that behavior here instead of just showing me the last output lines and the prompt I've mentioned?

ginger
  • 3
  • 4
  • Long running processes should be started as services, not inside screen. But there are some poorly written software such as Minecraft servers which make this difficult or impossible. You should check the configuration of your service, if possible. – Michael Hampton Aug 30 '19 at 19:19
  • @MichaelHampton But it is not a service; it is just a background process which starts early and runs for lets say an hour. I'm interested in the reason for that screen behavior, but I'm not going to change the entire architecture for that. As I mentioned, there is also some user interaction needed. – ginger Aug 30 '19 at 21:53

0 Answers0