Your message dated Thu, 05 Nov 2020 22:01:39 +0100
with message-id <[email protected]>
and subject line Re: Bug#904136: lightdm-gtk-greeter: Ayatana indicators aren't 
shown shown in lightdm-gtk-greeter
has caused the Debian Bug report #904136,
regarding lightdm-gtk-greeter: Ayatana indicators aren't shown shown in 
lightdm-gtk-greeter
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 [email protected]
immediately.)


-- 
904136: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904136
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: lightdm-gtk-greeter
Version: 2.0.5-1
Severity: normal

Dear Maintainer,

I've tried to use ayatana-indicator-printers with lightdm-gtk-greeter but the 
indicator isn't shown in the greeter.
For this I've added /usr/lib/ayatana-indicators3/7/libayatana-printersmenu.so 
to the indicators list in /etc/lightdm/lightdm-gtk-greeter.conf.
The lightdm-gtk-greeter process then had libayatana-printersmenu.so in its 
memory map but the indicator icon itself didn't appear and there was no log 
output under /var/log/lightdm/ that would indicate an obvious issue.

I've also tried ayatana-indicator-application with 'nm-applet --indicator' but 
I had again the same issue.
Can it be that the Ayatana indicators generally don't work yet with 
lightdm-gtk-greeter or am I doing something wrong?

Best,

Michael Schaller


-- System Information:
Debian Release: testing
Architecture: amd64 (x86_64)
Foreign Architectures: i386

--- End Message ---
--- Begin Message ---
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Version: 2.0.8-2
On Thu, 2020-11-05 at 11:53 +0100, Michael Schaller wrote:
> We completely gave up on LightDM and migrated to GDM in the meanwhile
> and I sadly forgot that this bug was still open. Hence I didn't post
> an update to it that we are no longer interested in a fix. My bad.
> I'm furthermore sorry that I won't be able to test your fix after
> you've spend the effort to implement it. I hope someone else will find
> this fix useful and might even be able to test it.

No problem, I can understand the frustration.

I'm marking the bug as closed, feel free to reopen if needed.

Regards,
- -- 
Yves-Alexis
-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAl+kaDQACgkQ3rYcyPpX
RFvFJggAudOp1+slhHTmY/pfZcW3TPRFcHBZCaAMeXuk1fUGtt7S8/uJCECcm7uE
Qe/cEJNlDFvS1tqE4gHhs7visKhSf06TKtLZ0oyfrsQeFjjAzKdqY5MZ3Y1vD8M7
8zbdYnmw5eNl4wrV5r/GW1DYEzUgS5EI5vXwIm1qNTRfHh1ZHN+ELhH72wdqgDRh
E96uGb8kXgddP83glhRO5WQc6ago961rhRLNJPfoYsUS/7zRvEEL2tYcON/oX5eF
JNXeeNslDGyC1Um1+a3LtMrURvnvNSNKRC6eCmlzcBlmi4U0/g58QaZfVvExYILp
2YHDI7baSrYkX+4R0uu+d1WnZuBY5g==
=Ezw2
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to