Package: sddm
Version: 0.18.0-1
Severity: important
Concurrent X-Sessions can be started on other VTs (without sddm, just
xinit) and you can switch between these without any problem.
When switching back to the sddm VT (number 7) sddm crashes and so the
session is lost.
This behaviour is 100%
Package: init
Version: 1.56+nmu1
Severity: minor
Tags: upstream
Dear Maintainer,
The man page of telinit/init says (for 'telinit N'):
Change the SysV runlevel. This is translated into an activation request for
runlevel2.target,
runlevel3.target, ... and is equivalent to systemctl isolate
Package: baloo-kf5
Version: 5.54.0-1
Severity: normal
Dear Maintainer,
baloo_file does not exit, this blocks the systemd --user session, and
therefore keeps a couple of prossess running after kde logout.
Put something like 'balooctl stop' at end end of /usr/bin/kdestartup to see
that systemd
Package: libpam-sss
Version: 1.16.3-3.1
Severity: normal
Dear Maintainer,
problem: changing SAMBA AD DC passwd using SSSD with AD providers
When user runs 'passwd' the old pw is prompted for and validated but
not prompt for a new pw is shows. SSSD log and source code indicate
that
Package: nfs-common
Version: 1:1.3.4-2.5+deb10u1
Severity: important
Tags: upstream
Dear Maintainers
There is a long standing bug (or wrong documentation) in rpc.gssd
Probably debian uses an outdated version (new upstream version).
I consider this bug as severe because it breaks backward compa-
Package: bash
Version: 5.2~rc2-2
Severity: normal
Tags: upstream
Dear Maintainer,
This new behaviour is documented in the upstream changelog
For example: "${/ && /&&}"
must now become: "${/ && /\&\&}"
To work as expected. Trivial, but breaks existing scripts. At least
debian should
Package: fwupd
Version: 1.8.4-2
Severity: minor
Dear Maintainer,
A few days ago we had press reports about updates from a specific os
vendor that made some linux machines unbootable. Although that the
vendor was probably well minded, this was problematic.
Today, at login I had a motd message
Package: digikam
Version: 4:7.9.0-1+b2
Severity: important
Dear Maintainer,
Thanks for building digikam for bookworm. As you shurely know this build
is quite important as recent appimage upstream builds crash on bookworm
(I believe that's a know problem).
The latest usable appimage for bookworm
Package: libpam-sss
Version: 2.8.2-4
Severity: normal
File: /lib/x86_64-linux-gnu/security/pam_sss.so
Dear Maintainer,
* What led up to the situation?
using kerberos, AD/DC, sssd and its pam module
* What exactly did you do (or not do) that was effective (or
ineffective)?
Package: src:linux
Version: 6.1.76-1
Severity: important
Tags: upstream
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
The driver fills the eventlog with millions !!! of messages, see below.
It otherwise works. The problem can be reproduced on
Package: linux-source-2.6.18
Version: 2.6.18-8
Severity: normal
Hi,
the kernel I use is built from debian source and 2.6.18-8 patches are
applied. The r8169 is on a dlink pci card in a SIS 671 system with a 2.4
GHz P4 CPU.
Symptom: Download speed is ok (25 MB/s) but Upload, e.g. the send speed
Package: kmail
Version: 4:3.5.5.dfsg.1-4
Severity: normal
kmails newest feature is to crash (without being touched) 1...2 minutes
after being launched. The behaviour is reproducable. Backtrace #1:
(no debugging symbols found)
Using host libthread_db library /lib/tls/libthread_db.so.1.
(no
12 matches
Mail list logo
