Hi,
I had the same problem, or at least it seems connected to what is reported here, I also reported
the error on the 'debian-backports' mailing-list (1).
It seems that the main problem is to be found in the 'kwin' version.
Would it be possible to have the packages updated also for kwin (or as
Good news,
updating to the latest kernel version from bookworm-backports seems to resolve the issue on my
Dell XPS: linux-image-amd64 (6.5.10-1~bpo12+1)
I confirm that the only version causing problems is the one indicated in the
initial email.
Enrico
Package: src:linux
Version: 6.5.3-1~bpo12+1
Severity: normal
X-Debbugs-Cc: debian-backpo...@lists.debian.org
After upgrading the latest kernel from backports the system does not shutdown
completely:
after starting shutdown (gui or terminal) the screen turns off but the power led (and other
keyb
Package: libcurl3-gnutls
Version: 7.74.0-1.2~bpo10+1
Severity: important
X-Debbugs-CC: debian-backpo...@lists.debian.org
After upgrading the Debian system from "backports" any git http operations
(clone/fetch ...) has stopped working, bringing libcurl3-gnutls to the previous
version (7.74.0-1.2
Package: libcurl3-gnutls
Version: 7.74.0-1.2~bpo10+1
Severity: important
|X-Debbugs-CC: |debian-backpo...@lists.debian.org
After upgrading the Debian system from "backports" any git http operations
(clone/fetch ...) has stopped working, bringing libcurl3-gnutls to the previous version
(7.74.0-1
Ok,
thanks.
Enrico
On Mon, 13 Apr 2020 17:36:26 +0200 Marcos Fouces
wrote:
> Hello Enrico
>
> In fact, you have to escape quotas in the argments you supply to the
> RUN_DAILY_OPTS variable.
>
> It should be posible to insert needed escape characters in debconf (i
> suppose that you configured
Thanks for investigating.
For the current version in my system (0.52-3+b10 in Debian Buster) the problem
seem fixed.
No error reported.
Thanks
Enrico
On Mon, 13 Apr 2020 18:09:39 +0200 Marcos Fouces
wrote:
> Hello
>
> I cannot test this o-o-stable kernel, but searching this particular
> chunk
Package: logcheck
Version: 1.3.20
Severity: wishlist
After updating system from stretch to buster the log lines relating to the
failed login are no longer detected as security.
Trying to start logcheck on a previous log file the result is correct, so it may
be that the problem is in formatting mes
Package: chkrootkit
Version: 0.49-4.1+deb7u2
Severity: normal
Upgrading to new kernel from backports repository chkrootkit report an error
detected from email report:
/etc/cron.daily/chkrootkit:
ERROR: chkrootkit output was not as expected.
The difference is:
---[ BEGIN: diff -u /var/log/chkroo
Package: chkrootkit
Version: 0.49-4.1+deb7u2
Severity: |important
Since the last upgrade of chkrootkit package from 0.49-41 to 0.49-4.1+deb7u2 I
found an error on the configuration file.
Configuration file seem to have been modified during last upgrade.
The error was reported by mail to localhost
10 matches
Mail list logo
