Xfce Forum

jrv

Member

Registered: 2015-01-05

Posts: 13

[solved] terminal processes suspend if not on current workspace

Running Debian trixie/testing on my desktop
$ uname -r
6.6.15-amd64

xfce is version 4.18 (meta package version #)

I frequently switch to one xfce workspace, open a new bash terminal and rip a cd in it using the abcde ripper. abcde is a perl script that does most of the work using other binaries, primarily cdparanoia. I then switch to another xfce workspace and do other stuff there (browse the internet for cat videos, doom scroll facebook, etc.). In the past week or so the abcde processing on the other workspace will go on for a bit then "suspend/pause." If I switch over to the workspace the process "wakes up" and starts working again. If I leave abcde workspace the processing will sometimes stop until the workspace is made the current one again.

During a recent update at least one xfce setting got disrupted. The keyboard layout switched. Is there any kind of xfce setting that would "pause" processes that are not on the current workspace? Or any other thoughts on what might be going on or on information I might gather?

Last edited by jrv (2024-03-09 11:26:37)

Tamaranch

Member

Registered: 2020-12-31

Posts: 321

Re: [solved] terminal processes suspend if not on current workspace

It's a bug in vte >= 0.75.0, fixed in 0.75.92: https://gitlab.gnome.org/GNOME/vte/-/issues/2742

jrv

Member

Registered: 2015-01-05

Posts: 13

Re: [solved] terminal processes suspend if not on current workspace

It's a bug in vte >= 0.75.0, fixed in 0.75.92: https://gitlab.gnome.org/GNOME/vte/-/issues/2742

Thanks much. I wasn't sure which application was the problem (xfce, vte, X-Windows, something else). I made a wild guess that it might be a power-saving setting intended for laptops or something. Apparently wrong. I will wait for a new vte then.

jrv

Member

Registered: 2015-01-05

Posts: 13

Re: [solved] terminal processes suspend if not on current workspace

As a follow-on, a new version of the vte came down in debian testing a couple weeks ago, and the problem is now gone. Thanks again!