Control: reassign -1 ckb-next
Control: forcemerge 977506 -1
Control: severity 977506 grave
Hi,
since there is now
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977506
I think it makes sense to merge the two bug reports.
If Stewart, the maintainer of ckb-next, thinks this is an issue in
Control: forwarded -1 https://github.com/systemd/systemd/issues/17922
OpenPGP_signature
Description: OpenPGP digital signature
Quack,
On 2020-12-10 07:39, Michael Biebl wrote:
It might be, that ckb-next is affected by this, especially when it
deals with handling/creating (input) devices.
I'm inclined to reassign this to ckb-next. WDYT?
Indeed it seems the change described in this article would affect
ckb-next.
Am 08.12.20 um 16:07 schrieb Michael Biebl:
Am 08.12.20 um 06:14 schrieb Marc Dequènes (duck):
I was wondering what make my system so peculiar and stumbled onto this
bug report:
https://github.com/ckb-next/ckb-next/issues/671
I haven't tried the ckb-next git version yet but it seems
Am 08.12.20 um 06:14 schrieb Marc Dequènes (duck):
I was wondering what make my system so peculiar and stumbled onto this
bug report:
https://github.com/ckb-next/ckb-next/issues/671
I haven't tried the ckb-next git version yet but it seems strange that
simply presenting a device's features
Quack,
I was wondering what make my system so peculiar and stumbled onto this
bug report:
https://github.com/ckb-next/ckb-next/issues/671
I haven't tried the ckb-next git version yet but it seems strange that
simply presenting a device's features differently would break things. If
there
Am Sonntag, den 06.12.2020, 16:04 +0100 schrieb Michael Biebl:
> Control: severity -1 important
> Control: tags -1 unreproducible
>
> I tested other Wayland clients
To be specific: weston, sway and GNOME.
I used gdm3 as display manager to start those Wayland sessions and did
not run into any
Control: severity -1 important
Control: tags -1 unreproducible
I tested other Wayland clients (on real hardware and in a VM), most
notably GNOME Shell, and could not reproduce the problem. We didn't have
other users confirming this issue either. I'm thus tentatively
downgrading the severity
Quack,
On 2020-12-05 05:00, Michael Biebl wrote:
hidepid is known to cause problems and no longer a supported
configuration:
https://www.debian.org/releases/stable/amd64/release-notes/ch-information.de.html#hidepid-unsupported
Thanks for pointing this out, I did not know it was officially
Am 04.12.2020 um 11:56 schrieb Marc Dequènes (duck):
On 2020-12-04 17:04, Michael Biebl wrote:
Is policykit-1 installed and working?
I dug a little bit more on this front and I am affected by this:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860040
which then made the polkit agent
On 2020-12-04 17:04, Michael Biebl wrote:
Is policykit-1 installed and working?
I dug a little bit more on this front and I am affected by this:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860040
which then made the polkit agent quit on start.
I have not tested yet if removing
On 2020-12-04 17:04, Michael Biebl wrote:
Control: tags -1 + moreinfo
Am 04.12.20 um 07:00 schrieb Marc Dequènes (duck):
After upgrade from 246.6-5 to 247.1-3 I experienced impossibility to
use my keyboard after login on graphical session.
I'm using Lightdm + Sway and could input with my
Control: tags -1 + moreinfo
Am 04.12.20 um 07:00 schrieb Marc Dequènes (duck):
After upgrade from 246.6-5 to 247.1-3 I experienced impossibility to use
my keyboard after login on graphical session.
I'm using Lightdm + Sway and could input with my usual keyboard for
encrypted disk
Package: systemd
Version: 247.1-3
Severity: critical
Justification: breaks graphical session input
Control: affects -1 sway
Quack,
After upgrade from 246.6-5 to 247.1-3 I experienced impossibility to use
my keyboard after login on graphical session.
I'm using Lightdm + Sway and could input
14 matches
Mail list logo
