[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1068020: marked as done (Background process seemingly paused)



Your message dated Sat, 10 Aug 2024 14:32:07 +0200 (CEST)
with message-id <20240810123207.2CCC0BE2DE0@eldamar.lan>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #1068020,
regarding Background process seemingly paused
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
1068020: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068020
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-amd64
Version: 6.6.15-2

Debian testing/trixie, kernel 6.6.15-2 (2024-02-04)
xfce

Case 1:

Start a command that runs for a long time, say `ffmpeg`. switch to other programs, i.e. web browser or other terminal windows, and keep using the computer. After a while, ffmpeg cpu usage drops to 0%, switch back to ffmpeg's terminal window, it will go back to running. 

Case 2: 

start ffmpeg, leave the computer untouched, then screensaver runs, then the display turns off. No suspend, no hibernate, no shutdown. after a while, wake up display, unlock session, ffmpeg is using 0% CPU. switch back to its terminal window, it resumes.


I am not sure which package is causing this. This happened long before 6.6.15 kernels.

--- End Message ---
--- Begin Message ---
Hi

This bug was filed for a very old kernel or the bug is old itself
without resolution.

If you can reproduce it with

- the current version in unstable/testing
- the latest kernel from backports

please reopen the bug, see https://www.debian.org/Bugs/server-control
for details.

Regards,
Salvatore

--- End Message ---

Reply to: