[bts-link] source package xfce4-battery-plugin

2020-05-21 Thread debian-bts-link 
#
# bts-link upstream status pull for source package xfce4-battery-plugin
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
# https://bts-link-team.pages.debian.net/bts-link/
#

user debian-bts-l...@lists.debian.org

# remote status report for #497202 (http://bugs.debian.org/497202)
# Bug title: xfce4-battery-plugin only supports ACPI and APM
#  * http://bugzilla.xfce.org/show_bug.cgi?id=3476
#  * remote status changed: NEW -> RESOLVED
#  * remote resolution changed: (?) -> WONTFIX
#  * upstream said bug is wontfix
tags 497202 + upstream wontfix
usertags 497202 - status-NEW
usertags 497202 + status-RESOLVED resolution-WONTFIX

# remote status report for #507499 (http://bugs.debian.org/507499)
# Bug title: xfce4-battery-plugin: "Charging" reported if the battery isn't 
charged
#  * http://bugzilla.xfce.org/show_bug.cgi?id=4673
#  * remote status changed: ASSIGNED -> RESOLVED
#  * remote resolution changed: (?) -> WONTFIX
#  * upstream said bug is wontfix
tags 507499 + upstream wontfix
usertags 507499 - status-ASSIGNED
usertags 507499 + status-RESOLVED resolution-WONTFIX

thanks

Processed: [bts-link] source package xfce4-battery-plugin

2020-05-21 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> #
> # bts-link upstream status pull for source package xfce4-battery-plugin
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #497202 (http://bugs.debian.org/497202)
> # Bug title: xfce4-battery-plugin only supports ACPI and APM
> #  * http://bugzilla.xfce.org/show_bug.cgi?id=3476
> #  * remote status changed: NEW -> RESOLVED
> #  * remote resolution changed: (?) -> WONTFIX
> #  * upstream said bug is wontfix
> tags 497202 + upstream wontfix
Bug #497202 [xfce4-battery-plugin] xfce4-battery-plugin only supports ACPI and 
APM
Added tag(s) upstream and wontfix.
> usertags 497202 - status-NEW
Usertags were: status-NEW.
Usertags are now: .
> usertags 497202 + status-RESOLVED resolution-WONTFIX
There were no usertags set.
Usertags are now: status-RESOLVED resolution-WONTFIX.
> # remote status report for #507499 (http://bugs.debian.org/507499)
> # Bug title: xfce4-battery-plugin: "Charging" reported if the battery isn't 
> charged
> #  * http://bugzilla.xfce.org/show_bug.cgi?id=4673
> #  * remote status changed: ASSIGNED -> RESOLVED
> #  * remote resolution changed: (?) -> WONTFIX
> #  * upstream said bug is wontfix
> tags 507499 + upstream wontfix
Bug #507499 [xfce4-battery-plugin] xfce4-battery-plugin: "Charging" reported if 
the battery isn't charged
Added tag(s) upstream and wontfix.
> usertags 507499 - status-ASSIGNED
Usertags were: status-ASSIGNED.
Usertags are now: .
> usertags 507499 + status-RESOLVED resolution-WONTFIX
There were no usertags set.
Usertags are now: status-RESOLVED resolution-WONTFIX.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
497202: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=497202
507499: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=507499
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#773743: xfce4-power-manager: Suspend fails (requests authentication in order to suspend)

2020-05-21 Thread Justin 
Package: xfce4-power-manager
Version: 1.6.6-1
Followup-For: Bug #773743

Hello,

  I run a thinkpad 495 laptop with tlp and this bug still exists. I believe the
bug has to do with the way the package adds rules to the systemd polkit. It
appears some rules and there subsequent config are missing. I also noticed that
with workarounds using the xfce4-power-manager settings the laptop would often
suspend before locking and when coming back it would briefly show the contents
of the unlocked system.

I have added what I did to fix the authentication errors below:

In order to get suspend issue corrected perform the following:

1) Create the '/etc/polkit-1/rules.d' directory

 $ sudo su
 # mkdir /etc/polkit-1/rules.d

2) Correct the permissions for the directory

 # chmod 755 /etc/polkit-1/rules.d

3) Create a new file called /etc/polkit-1/rules.d/85-suspend.rules

 # vi /etc/polkit-1/rules.d/85-suspend.rules

4) Add the following text to the new file called
'/etc/polkit-1/rules.d/85-suspend.rules'

polkit.addRule(function(action, subject) {
if (action.id == "org.freedesktop.login1.suspend" &&
subject.isInGroup("users")) {
return polkit.Result.YES;
}
});

5) Correct the permissions on the file
'/etc/polkit-1/rules.d/85-suspend.rules'

 # chmod 644 /etc/polkit-1/rules.d/85-suspend.rules

6) Edit the file
'/usr/share/polkit-1/actions/org.freedesktop.login1.policy' and change the
"suspend" rules to yes

The process is similar to fix the backlight modification authentication errors.

1) Create the '/etc/polkit-1/rules.d' directory ("if it doesn't exist")

 $ sudo su
 # mkdir /etc/polkit-1/rules.d

2) Correct the permissions for the directory ("if created above, in step
1")

 # chmod 755 /etc/polkit-1/rules.d

3) Create a new file called /etc/polkit-1/rules.d/89-backlight.rules

 # vi /etc/polkit-1/rules.d/89-backlight.rules

4) Add the following text to the new file called
'/etc/polkit-1/rules.d/89-backlight.rules'

polkit.addRule(function(action, subject) {
if (action.id == "org.xfce.power.backlight-helper" &&
subject.isInGroup("users")) {
return polkit.Result.YES;
}
});

5) Correct the permissions on the file
'/etc/polkit-1/rules.d/89-backlight.rules'

 # chmod 644 /etc/polkit-1/rules.d/89-backlight.rules

6) Edit the file
'/usr/share/polkit-1/actions/org.freedesktop.login1.policy' and change the
"backlight" rules to yes


I documented the fix on the wiki here:


https://wiki.debian.org/Xfce-power-manager-troubleshooting

And added a link the  xfce debian wiki page.

Maybe we can get these fixes incorporated into the package?

Thanks,

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (900, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.6.0-1-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
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 /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages xfce4-power-manager depends on:
ii  libc6 2.30-8
ii  libcairo2 1.16.0-4
ii  libgdk-pixbuf2.0-02.40.0+dfsg-4
ii  libglib2.0-0  2.64.2-1
ii  libgtk-3-03.24.20-1
ii  libnotify40.7.9-1
ii  libpango-1.0-01.44.7-4
ii  libpangocairo-1.0-0   1.44.7-4
ii  libupower-glib3   0.99.11-1
ii  libx11-6  2:1.6.9-2+b1
ii  libxext6  2:1.3.3-1+b2
ii  libxfce4ui-2-04.14.1-1+b1
ii  libxfce4util7 4.14.0-1
ii  libxfconf-0-3 4.14.1-1
ii  libxrandr22:1.5.1-1
ii  upower0.99.11-1
ii  xfce4-power-manager-data  1.6.6-1

Versions of packages xfce4-power-manager recommends:
ii  libpam-systemd   245.5-2
ii  xfce4-power-manager-plugins  1.6.6-1

xfce4-power-manager suggests no packages.

-- no debconf information

Bug#961132: lightdm: with the nvidia driver, lightdm suspends the system when locking or logging out

2020-05-21 Thread Vincent Lefevre 
Hi,

On 2020-05-21 14:01:04 +0200, Yves-Alexis Perez wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
> 
> control: tag -1 unreproducible

Not sure the conditions to reproduce the bug, but to be sure, with
a laptop:

1. Set up a systemd-inhibit lock for handle-lid-switch.

2. Close the lid.

3. Lock the screen with light-locker or log out.

Just guessing, because the systemd log does not mention lid closing
at all for the reason of suspend.

Note that this was in my bug report against systemd:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961124

(merged with this bug).

> On Wed, 2020-05-20 at 19:35 +0200, Vincent Lefevre wrote:
> > 
> > Both locking and logging out trigger the lightdm login prompt,
> > so that I suppose that this is the same issue, and it was not
> > light-locker that was suspending the system, but lightdm.
> 
> Hi,
> 
> this is weird indeed, but I'm not going to investigate an nvidia
> binary issue. For what it's worth, I do have a system with an nvidia
> card and the binary driver, running lightdm, light-locker and Xfce,
> and I don't have that behavior at all (running Buster).

Well, Michael Biebl says that's light-locker / lightdm that suspends
the system:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961124#22

(note: I don't use XFCE, just lightdm + light-locker at that time).
There is no reason to do that under any condition, and the code that
does that needs to be removed.

Now, if there isn't any such code, I would tend to think that
Michael Biebl is wrong, because I also get a suspend issue
without lightdm / light-locker:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961146

and it seems to be related to systemd-inhibit lock vs which
login session is associated with the display, in particular
when switching from X to a VT:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961146#15

Since the use of lightdm does something similar, this could explain
the bug.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Re: Tab indents not working correctly

2020-05-21 Thread Yves-Alexis Perez 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Sun, 2020-05-17 at 16:45 +0200, Alejandro Colomar wrote:
> Hi,
> 
> I noticed this bug a few months ago in Manjaro, and couldn't find the 
> surce of the bug.  It happened both in Mousepad and Gedit (using XFCE).
> 
> I moved back to Debian testing (also XFCE) for that other reasons, and 
> didn't have that bug.  Until this week.
> 
> The length of an 8-character tab is not always 8.  Sometimes it's around 
> 8.5 (visually), causing wrong results.  Changing the length of the 
> indent (sometimes) fixes the problem, and sometimes it doesn't.
> 
> Using:
> Mousepad 0.4.2
> Debian Bullseye (11, testing)
> 
Hi, it's like caused by the recent pango update (see 
https://bugs.debian.org/956612)

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

iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAl7Gbj8ACgkQ3rYcyPpX
RFv/QQgAwK8KIOEGOaBQi+kNZXnFJ/cVLCXgp2wZKWytEyFKEFAxfpSVGiXDdPz9
p8Ps0jGuSOtk/BdSxUShEMb9b2tCqEUhToTp61UfTFVs/WOYo8UZ6sDpDCGiw4Ag
nEQO5QEq3suQ8akMHhTujNOQKcsJfBLhaI07ftmSEitmQSVEk6aEv6a8OjLJjaNM
lr2Haq0vFsScZ7i2kdHkA2aVhYrxTymLwTL2yfkN9U+7aBxWklzBH/5EcgTLW/nQ
738Hk8rq40zAI56wNGEV1OS84bQ592lg5Fvx0s7tWAuhJmDSwer66qOyFYpMJKs8
SbmgOWQ2ahVqLsjAZtFzOUE9QP3j8w==
=D+I9
-END PGP SIGNATURE-

Bug#961132: lightdm: with the nvidia driver, lightdm suspends the system when locking or logging out

2020-05-21 Thread Yves-Alexis Perez 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

control: tag -1 unreproducible

On Wed, 2020-05-20 at 19:35 +0200, Vincent Lefevre wrote:
> 
> Both locking and logging out trigger the lightdm login prompt,
> so that I suppose that this is the same issue, and it was not
> light-locker that was suspending the system, but lightdm.

Hi,

this is weird indeed, but I'm not going to investigate an nvidia binary issue.
For what it's worth, I do have a system with an nvidia card and the binary
driver, running lightdm, light-locker and Xfce, and I don't have that behavior
at all (running Buster).

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

iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAl7GbYAACgkQ3rYcyPpX
RFtKhwgAn7axFp/6uKnAgAMrpB7Z7IV33zp4l8KZXiR/AB6yc3WJbvzPNp+rmzVC
3jUfnKiG5iNSLmKu+AewnA9/jKV5MM60Fo+ZMm52DLocZ2lfUS5YghJ9BJM2ucgJ
CMagLBeMe9Q22W2q7g42CAmmmKfiDtkl6J+6xOKWDO1JZ2EkWE15TiavbPtEuZSs
pdKKauqZhAI/FjwfWSFhBN10rlReucN+MFFoYDWZ4X7j3MM1cKRR3LFGQOORrl+E
SDZ8BMz2LIbYthUSqYwNIW+8gCdIH1TjT8uqV9zZh0HTHQeeJjW8iRlpwC9MWWTr
Gd7NOmx90Ziuj53Xbpcyayk5AmEX0g==
=Sq/d
-END PGP SIGNATURE-

Processed: Re: Bug#961132: lightdm: with the nvidia driver, lightdm suspends the system when locking or logging out

2020-05-21 Thread Debian Bug Tracking System 
Processing control commands:

> tag -1 unreproducible
Bug #961132 [lightdm] lightdm: with the nvidia driver, lightdm suspends the 
system when locking or logging out
Bug #961124 [lightdm] lightdm: with the nvidia driver, lightdm suspends the 
system when locking or logging out
Added tag(s) unreproducible.
Added tag(s) unreproducible.

-- 
961124: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961124
961132: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961132
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems