Devuan bug report logs - #494
lightdm: please add user lightdm to the audio group

Full log

🔗 View this message in rfc822 format

MIME-Version: 1.0
X-Mailer: MIME-tools 5.509 (Entity 5.509)
X-Loop: owner@bugs.devuan.org
From: "Devuan bug Tracking System" <owner@bugs.devuan.org>
To: dak@devuan.org
Subject: bug#494: marked as done (lightdm: please add user lightdm to the
 audio group)
Message-ID: <handler.494.D494.16922147443044.ackdone@bugs.devuan.org>
References: <1692214710.718001.923.nullmailer@dak.localnet.devuan.org>
 <159539281751.2978.13577532054125158303.reportbug@pegasus.lan.lan>
X-Devuan-PR-Message: closed 494
X-Devuan-PR-Package: lightdm
X-Devuan-PR-Source: lightdm
Reply-To: 494@bugs.devuan.org
Date: Wed, 16 Aug 2023 19:40:03 +0000
Content-Type: multipart/mixed; boundary="----------=_1692214803-3091-0"

[Message part 1 (text/plain, inline)]

Your message dated Wed, 16 Aug 2023 19:38:30 +0000
with message-id <1692214710.718001.923.nullmailer@dak.localnet.devuan.org>
and subject line #494: fixed in src:lightdm version 1.32.0-3devuan1
has caused the Devuan bug report #494,
regarding lightdm: please add user lightdm to the audio group
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.devuan.org
immediately.)


-- 
494: https://bugs.devuan.org/cgi/bugreport.cgi?bug=494
Devuan Bug Tracking System
Contact owner@bugs.devuan.org with problems

[Message part 2 (message/rfc822, inline)]

From: Gregory Nowak <greg@gregn.net>

To: Devuan Bug Tracking System <submit@bugs.devuan.org>

Subject: lightdm: please add user lightdm to the audio group

Date: Tue, 21 Jul 2020 21:40:17 -0700

Package: lightdm
Version: 1.26.0-4
Severity: normal
Tags: a11y

Dear Maintainer,

Please add the lightdm user to the audio group.
This is necessary so that the orca screen reader
can provide speech output at the 
lightdm-gtk-greeter login screen.
As far as I know, this is only needed when using the
orca screen reader at the login screen.
A possible side effect of adding lightdm
to the audio group may lead users who do not use
orca to question why lightdm is added to the audio
group on their systems. Perhaps this should be done only if
/etc/xdg/lightdm/lightdm.conf.d/80_orca-dm-wrapper.conf already exists?
I am assuming it doesn't exist on a system which wasn't
installed with accessibility, but I don't know that for sure.
Thank you.


-- System Information:
Distributor ID:	Debian
Description:	Devuan GNU/Linux 3 (beowulf)
Release:	3
Codename:	beowulf
Architecture: x86_64

Kernel: Linux 4.19.0-9-amd64 (SMP w/16 CPU cores)
Kernel taint flags: TAINT_CRAP
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages lightdm depends on:
ii  adduser                                3.118
ii  dbus                                   1.12.16-1+devuan2
ii  debconf [debconf-2.0]                  1.5.71
ii  libaudit1                              1:2.8.4-3
ii  libc6                                  2.28-10
ii  libgcrypt20                            1.8.4-5
ii  libglib2.0-0                           2.58.3-2+deb10u2
ii  libpam-elogind [logind]                241.4-2
ii  libpam0g                               1.3.1-5
ii  libxcb1                                1.13.1-2
ii  libxdmcp6                              1:1.1.2-3
ii  lightdm-gtk-greeter [lightdm-greeter]  2.0.6-1
ii  lsb-base                               10.2019051400

Versions of packages lightdm recommends:
ii  xserver-xorg  1:7.7+19

Versions of packages lightdm suggests:
ii  accountsservice  0.6.45-2
ii  upower           0.99.10-1
pn  xserver-xephyr   <none>

-- Configuration Files:
/etc/lightdm/lightdm.conf changed [not included]

-- debconf information excluded

[Message part 3 (message/rfc822, inline)]

From: dak@devuan.org

To: 494-done@bugs.devuan.org

Subject: #494: fixed in src:lightdm version 1.32.0-3devuan1

Date: Wed, 16 Aug 2023 19:38:30 +0000

Version: 1.32.0-3devuan1

Source package lightdm (1.32.0-3devuan1) added to Devuan suite unstable.

This closes bug report 494.

Thanks

DAK managing the Devuan archive

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Wed, 14 Aug 2023 14:13:56 -0400
Source: lightdm
Architecture: source
Version: 1.32.0-3devuan1
Distribution: unstable
Urgency: medium
Maintainer: B. Stack <bgstack15@gmail.com>
Changed-By: B. Stack <bgstack15@gmail.com>
Closes: 432 494 529
Changes:
 lightdm (1.32.0-3devuan1) unstable; urgency=medium
 .
   * Fork for Devuan
     * (Closes: #494, #432, #529)
Checksums-Sha1:
 a9bf2194778467aea1b05e3c3b52312aab9e1c71 2195 lightdm_1.32.0-3devuan1.dsc
 17e49cd5341b954127bed1dd21b44dfb08415531 828156 lightdm_1.32.0.orig.tar.gz
 b88b87f8af70e084a2d10830b6ced3d7f966cdda 38704 lightdm_1.32.0-3devuan1.debian.tar.xz
 d70afa517ed3d9a0d1bda8de2646c260de63f0cb 5508 lightdm_1.32.0-3devuan1_source.buildinfo
Checksums-Sha256:
 0edebb4d26e6c83c6b33edd9110eda2f670d3da95b80c10935c70060f4d4a257 2195 lightdm_1.32.0-3devuan1.dsc
 886caf111c0becb4d28f483222783fa749c20dd336d1f7b0a75ace82d636536d 828156 lightdm_1.32.0.orig.tar.gz
 8ffcc0ad3d0837120bcbd04f796b4a1d6da0ee852d2889b854ea80e819ea50f6 38704 lightdm_1.32.0-3devuan1.debian.tar.xz
 43ac67ef6f491a588baece08f17444586d81cd652ca623d4d5ac8ef40f418434 5508 lightdm_1.32.0-3devuan1_source.buildinfo
Files:
 f2fd82bce8283430d9b8bd75ad622561 2195 x11 optional lightdm_1.32.0-3devuan1.dsc
 75b6d4b475d77de4499540d0dc2441e5 828156 x11 optional lightdm_1.32.0.orig.tar.gz
 6586247b8eeb5caf8fc34abebfb86d90 38704 x11 optional lightdm_1.32.0-3devuan1.debian.tar.xz
 73dd4963f150eeba8deac74dbc644e52 5508 x11 optional lightdm_1.32.0-3devuan1_source.buildinfo

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCgAdFiEEcuPLdzMV36LkZHQ9lFMhJFQZIvsFAmTdH9wACgkQlFMhJFQZ
Ivv4jQf/d/xs4t1iMohlgJaVub6EKM5blYuiPqQX56YZ3CaL/aGuTGC5Vm+rmN4c
yLDJrZUyQyS7RAVhWrCJehV7rjSOcyybxElmjrpTgak7wt51j49Evn1zuWzNd32a
WR/xLv994X/o2l2zR5abaV/SXCnpQMk6k1ChNcGiViD1HFKmv3FE6/yf0kW48n2G
jYDE837HnFK+7llGUmEX8TnAcJ8zxTYLSdz4+hqdNIPBfYh10YNqe3o79MiYcUaL
/foWUJ8IrWOlAZV9YzV8fv/L1W8GV8q5uIdvwtCJEbtImMAWwy4OuiE2ra2XhKEc
jszGgD8dbAuxn69kEshvu6YudJgbFA==
=TqFD
-----END PGP SIGNATURE-----

Send a report that this bug log contains spam.