Processed: Bug#753484 marked as pending in lightdm-gtk-greeter

2024-04-29 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 pending
Bug #753484 [lightdm-gtk-greeter] lightdm-gtk-greeter: Updated Norwegian Bokmål 
(nb) translation
Added tag(s) pending.

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



Processed: Bug#1069860 marked as pending in lightdm-gtk-greeter

2024-04-29 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 pending
Bug #1069860 [lightdm-gtk-greeter] lightdm-gtk-greeter: should not recommend 
the transitional package policykit-1
Added tag(s) pending.

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



Processed: [bts-link] source package lightdm

2024-04-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> #
> # bts-link upstream status pull for source package lightdm
> # 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 #1029557 (http://bugs.debian.org/1029557)
> # Bug title: debian-edu-config: Session exits on first login on 
> roaming-workstation fails
> #  * https://github.com/canonical/lightdm/issues/322
> #  * remote status changed: open -> closed
> #  * closed upstream
> tags 1029557 + fixed-upstream
Bug #1029557 [lightdm] debian-edu-config: Session exits on first login on 
roaming-workstation fails
Bug #1052389 [lightdm] First login with libpam-mklocaluser always fails
Added tag(s) fixed-upstream.
Added tag(s) fixed-upstream.
> usertags 1029557 - status-open
Usertags were: status-open.
There are now no usertags set.
> usertags 1029557 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> # remote status report for #1052389 (http://bugs.debian.org/1052389)
> # Bug title: First login with libpam-mklocaluser always fails
> #  * https://github.com/canonical/lightdm/issues/322
> #  * remote status changed: open -> closed
> #  * closed upstream
> tags 1052389 + fixed-upstream
Bug #1052389 [lightdm] First login with libpam-mklocaluser always fails
Bug #1029557 [lightdm] debian-edu-config: Session exits on first login on 
roaming-workstation fails
Ignoring request to alter tags of bug #1052389 to the same tags previously set
Ignoring request to alter tags of bug #1029557 to the same tags previously set
> usertags 1052389 - status-open
Usertags were: status-open.
There are now no usertags set.
> usertags 1052389 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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



Bug#785237: marked as done (lightdm-gtk-greeter: Please remove leading spaces from user name)

2024-04-21 Thread Debian Bug Tracking System
Your message dated Sun, 21 Apr 2024 11:05:45 +
with message-id 
and subject line Bug#785237: fixed in lightdm-gtk-greeter 2.0.9-1
has caused the Debian Bug report #785237,
regarding lightdm-gtk-greeter: Please remove leading spaces from user name
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 ow...@bugs.debian.org
immediately.)


-- 
785237: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785237
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lightdm-gtk-greeter
Version: 2.0.0-3
Severity: wishlist

Dear Maintainer,

I work at a laptop computer that I usually suspend instead of shutting down.
After opening the lid, I usually tap the space key to restart the computer.
Sometimes, a spurious space character makes it into the field for the user name
as first character. Naturally, user name and password don't match in this case.
However, as my password is quite long, I usually tend to assume I have mistyped
the password, thus losing time and nerves by repeatedly retyping the password
before thinking of the stray space character in front of the user name. :-)

Wouldn't it be possible to remove leading spaces from the input in the user
name field before matching user and password? Are leading spaces in user names
even allowed? If so, unconditionally removing them could cause issues for
people
with such user names. These might be prevented, however, if the test was for a
match of (password and username) OR (password and username without leading
spaces), rather than just (password and username).

Best regards,

Andreas



-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 3.16.0-4-686-pae (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages lightdm-gtk-greeter depends on:
ii  libc6   2.19-18
ii  libcairo2   1.14.0-2.1
ii  libgdk-pixbuf2.0-0  2.31.1-2+b1
ii  libglib2.0-02.44.0-3
ii  libgtk-3-0  3.14.5-1
ii  liblightdm-gobject-1-0  1.14.0-1
ii  libx11-62:1.6.3-1

Versions of packages lightdm-gtk-greeter recommends:
ii  desktop-base   8.0.2
ii  gnome-icon-theme-symbolic  3.12.0-1
pn  gnome-themes-standard  
ii  policykit-10.105-8

lightdm-gtk-greeter suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: lightdm-gtk-greeter
Source-Version: 2.0.9-1
Done: Yves-Alexis Perez 

We believe that the bug you reported is fixed in the latest version of
lightdm-gtk-greeter, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 785...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Yves-Alexis Perez  (supplier of updated lightdm-gtk-greeter 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 21 Apr 2024 12:42:26 +0200
Source: lightdm-gtk-greeter
Architecture: source
Version: 2.0.9-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Xfce Maintainers 
Changed-By: Yves-Alexis Perez 
Closes: 785237
Changes:
 lightdm-gtk-greeter (2.0.9-1) unstable; urgency=medium
 .
   * d/watch updated to fix signature download
   * New upstream version 2.0.9
 - trim whitespace in username (Closes: #785237)
   * d/control: replace pkg-config b-dep by pkgconf
Checksums-Sha1:
 a8fa95f4e5286bf000ac2de414fdb7f25ad09275 2062 lightdm-gtk-greeter_2.0.9-1.dsc
 90cf2a1fbe0e7035c7481566d03fed65f396eb78 602540 
lightdm-gtk-greeter_2.0.9.orig.tar.gz
 8191a6af5d95d365a6a04db9be50c7ac0ab973fe 488 
lightdm-gtk-greeter_2.0.9.orig.tar.gz.asc
 b99a87dca113f4acbd0b625049203c932462653b 6612 
lightdm-gtk-greeter_2.0.9-1.debian.tar.xz
 f253b2f5df869638f0871a3b7279f83dcf44edf3 16395 
lightdm-gtk-greeter_2.0.9-1_amd64.buildinfo
Checksums-Sha256:
 5c288d3602a8ff11c738521ffdd54b02f354c4f7438ed3882048a552bf899f89 2062 
lightdm-gtk-greeter_2.0.9-1.dsc
 c8fdf198aa9a3f9d0dad0b48dfe23c2277b79107e8fcfc62965290f1081f645d 602540 
lightdm-gtk-greeter_2.0.9.orig.tar.gz

Processed: Re: lightdm-gtk-greeter: Please remove leading spaces from user name

2024-04-20 Thread Debian Bug Tracking System
Processing control commands:

> tags -1 + fixed-upstream
Bug #785237 [lightdm-gtk-greeter] lightdm-gtk-greeter: Please remove leading 
spaces from user name
Added tag(s) fixed-upstream.

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



Bug#1067561: marked as done (FTBFS: Error: symbol `open64' is already defined)

2024-04-19 Thread Debian Bug Tracking System
Your message dated Fri, 19 Apr 2024 14:35:05 +
with message-id 
and subject line Bug#1067561: fixed in lightdm 1.32.0-5
has caused the Debian Bug report #1067561,
regarding FTBFS: Error: symbol `open64' is already defined
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 ow...@bugs.debian.org
immediately.)


-- 
1067561: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067561
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: lightdm
Version: 1.32.0-4
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=lightdm=armel=1.32.0-4%2Bb3=1711185127=0

/bin/bash ../../libtool  --tag=CC   --mode=link gcc -Wall
-Wstrict-prototypes  -Wnested-externs
-Werror=missing-prototypes  -Werror=implicit-function-
declaration  -Werror=pointer-arith
-Werror=init-self  -Werror=format-security
-Werror=format=2  -Werror=missing-include-dirs
-I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabi/glib-2.0/include
-I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabi/glib-2.0/include
-I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabi/glib-2.0/include -pthread
-I/usr/include/libmount -I/usr/include/blkid  -I/usr/include/gio-unix-2.0
-I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabi/glib-2.0/include -pthread
-I/usr/include/libmount -I/usr/include/blkid  -g -O2 -Werror=implicit-function-
declaration -ffile-prefix-map=/<>=. -fstack-protector-strong
-fstack-clash-protection -Wformat -Werror=format-security -O0  -Wl,-z,relro
-Wl,-z,now -Wl,-O1 -o Xvnc Xvnc-Xvnc.o Xvnc-x-authority.o Xvnc-x-common.o Xvnc-
x-server.o Xvnc-status.o -lgobject-2.0 -lglib-2.0  -lglib-2.0  -lgio-2.0
-lgobject-2.0 -lglib-2.0  -lgio-2.0 -lgobject-2.0 -lglib-2.0
/tmp/ccCHYR2t.s: Assembler messages:
/tmp/ccCHYR2t.s:2779: Error: symbol `open64' is already defined
/tmp/ccCHYR2t.s:3181: Error: symbol `creat64' is already defined
/tmp/ccCHYR2t.s:3508: Error: symbol `__stat64_time64' is already defined


-- System Information:
Debian Release: trixie/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 
'unstable'), (500, 'testing'), (101, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.7.9-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: lightdm
Source-Version: 1.32.0-5
Done: Yves-Alexis Perez 

We believe that the bug you reported is fixed in the latest version of
lightdm, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1067...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Yves-Alexis Perez  (supplier of updated lightdm package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 19 Apr 2024 15:34:32 +0200
Source: lightdm
Architecture: source
Version: 1.32.0-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Xfce Maintainers 
Changed-By: Yves-Alexis Perez 
Closes: 1067561
Changes:
 lightdm (1.32.0-5) unstable; urgency=medium
 .
   * d/patch: add upstream patch for 64b time_t build failure (Closes: #1067561)
   * d/control: replace pkg-config build-dep by pkgconf
   * d/gir1.2-lightdm-1.install: move typelib to multi-arch dir
   * Upload to unstable
Checksums-Sha1:
 8dcd27ce65dde196c89b62eba48f4ddec656a462 2493 lightdm_1.32.0-5.dsc
 c033f272898779060ebaf6deb616ba74cd239e41 39744 lightdm_1.32.0-5.debian.tar.xz
 0635df7ab89a139794fcf1e63d667b77391706c4 20924 lightdm_1.32.0-5_amd64.buildinfo
Checksums-Sha256:
 ee37960474840f5fa4e31838fb4eaf9ca4154ccbfc5922119af65658f2ea481f 2493 
lightdm_1.32.0-5.dsc
 453248d03826e6af8fcedcfd2039d48927a961cd46d8d9ea6c2c32a3ac1e5a72 39744 
lightdm_1.32.0-5.debian.tar.xz
 110c2ad1de1f97f26c14dc21f614026a707d101d6b70c944d4f30b4a6ecb5f61 20924 
lightdm_1.32.0-5_amd64.buildinfo
Files:
 f8b5cad61493d84b8fe998cc54124f53 2493 x11 optional lightdm_1.32.0

Processed: tagging 1046274, fixed 1062998 in 4.19.0-1.1~exp1, tagging 1062998, tagging 1062072 ...

2024-04-18 Thread Debian Bug Tracking System
libosmo-netif] libosmo-netif: NMU diff for 64-bit time_t 
transition
Marked as fixed in versions libosmo-netif/1.2.0-2.1~exp1.
> tags 1062558 + experimental
Bug #1062558 [src:libosmo-netif] libosmo-netif: NMU diff for 64-bit time_t 
transition
Added tag(s) experimental.
> tags 1064170 + experimental
Bug #1064170 {Done: Steve Langasek } [src:mediastreamer2] 
mediastreamer2: NMU diff for 64-bit time_t transition
Added tag(s) experimental.
> found 1064170 1:5.2.0+dfsg-3
Bug #1064170 {Done: Steve Langasek } [src:mediastreamer2] 
mediastreamer2: NMU diff for 64-bit time_t transition
Marked as found in versions mediastreamer2/1:5.2.0+dfsg-3.
> found 1064170 1:5.2.98+dfsg-7
Bug #1064170 {Done: Steve Langasek } [src:mediastreamer2] 
mediastreamer2: NMU diff for 64-bit time_t transition
Marked as found in versions mediastreamer2/1:5.2.98+dfsg-7 and reopened.
> found 1067117 10.8.2-1
Bug #1067117 [src:budgie-desktop] budgie-desktop: Fails to build with mutter >= 
45
Marked as found in versions budgie-desktop/10.8.2-1.
> found 1064282 24.02.0-1
Bug #1064282 [src:poppler] poppler: NMU diff for 64-bit time_t transition
Marked as found in versions poppler/24.02.0-1.
> tags 1063135 + experimental
Bug #1063135 [src:libselinux] libselinux: NMU diff for 64-bit time_t transition
Added tag(s) experimental.
> tags 1063040 + experimental
Bug #1063040 [src:uw-imap] uw-imap: NMU diff for 64-bit time_t transition
Added tag(s) experimental.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1046274: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1046274
1061864: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061864
1062007: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062007
1062022: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062022
1062072: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062072
1062249: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062249
1062285: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062285
1062320: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062320
1062340: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062340
1062444: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062444
1062558: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062558
1062834: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062834
1062998: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062998
1063040: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063040
1063135: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063135
1064141: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064141
1064170: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064170
1064282: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064282
1067117: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067117
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#1056555: marked as done (thunar: segfault when ejecting drive)

2024-04-12 Thread Debian Bug Tracking System
Your message dated Fri, 12 Apr 2024 14:50:31 +0200
with message-id 
and subject line Re: Bug#1056555: thunar: segfault when ejecting drive
has caused the Debian Bug report #1056555,
regarding thunar: segfault when ejecting drive
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 ow...@bugs.debian.org
immediately.)


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

Package: thunar
Version: 4.18.4-1
Severity: normal

Hi,
when ejecting a drive, thunar crashes (both with context menu 'eject', 
and the

eject button)

[18950.426861] Thunar[3027]: segfault at 0 ip 5615a96c98cc sp
7ffd2dbd7320 error 4 in thunar[5615a964+92000] likely on CPU 7 
(core 3,

socket 0)
[18950.426895] Code: f3 48 83 ec 38 64 48 8b 04 25 28 00 00 00 48 89 44 
24 28
31 c0 48 c7 44 24 20 00 00 00 00 48 85 f6 0f 84 77 02 00 00 48 8b 06 
<48> 39 10

0f 84 f1 01 00 00 4c 8b bf 28 01 00 00 4c 39 fe 0f 84 cb


Most of the time this happens when I eject it for the first time in that
session, when I try it a second time it works just fine.


-- System Information:
Debian Release: 12.2
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 
'stable')

Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.1.0-13-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8), 
LANGUAGE=es_AR:es

Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages thunar depends on:
ii desktop-file-utils 0.26-1
ii exo-utils 4.18.0-1
ii libatk1.0-0 2.46.0-5
ii libc6 2.36-9+deb12u3
ii libcairo2 1.16.0-7
ii libexo-2-0 4.18.0-1
ii libgdk-pixbuf-2.0-0 2.42.10+dfsg-1+b1
ii libglib2.0-0 2.74.6-2
ii libgtk-3-0 3.24.38-2~deb12u1
ii libgudev-1.0-0 237-2
ii libice6 2:1.0.10-1
ii libnotify4 0.8.1-1
ii libpango-1.0-0 1.50.12+ds-1
ii libsm6 2:1.2.3-1
ii libthunarx-3-0 4.18.4-1
ii libxfce4ui-2-0 4.18.2-2
ii libxfce4util7 4.18.1-2
ii libxfconf-0-3 4.18.0-2
ii shared-mime-info 2.2-1
ii thunar-data 4.18.4-1

Versions of packages thunar recommends:
ii dbus-user-session [default-dbus-session-bus] 1.14.10-1~deb12u1
ii dbus-x11 [dbus-session-bus] 1.14.10-1~deb12u1
ii gvfs 1.50.3-1
ii libxfce4panel-2.0-4 4.18.2-1
ii policykit-1-gnome [polkit-1-auth-agent] 0.105-8
ii thunar-volman 4.18.0-1
ii tumbler 4.18.0-1
ii udisks2 2.9.4-4
ii xdg-user-dirs 0.18-1

Versions of packages thunar suggests:
ii gvfs-backends 1.50.3-1
ii thunar-archive-plugin 0.5.0-1
ii thunar-media-tags-plugin 0.3.0-2+b1

-- no debconf information
--- End Message ---
--- Begin Message ---
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Wed, 2024-04-10 at 08:37 -0300, k02 wrote:
> Hi,
> 
> Since this bug was very annoying/frequent, a few weeks ago I decided to 
> format my machine entirely (I've been using debian on this machine for 
> over 4 years without reinstall and using very old config files).
> This bug and other annoyances are gone now,  so if something happens I 
> prefer to open a new bug.

Hi, thanks for the feedback, I'm closing the bug then.

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

iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmYZLhcACgkQ3rYcyPpX
RFt+Awf/eYQ9fvg+58FKf5pZxZ+Tm3T/CgF4rAwNNRYUiVI/CU8ZWOEprgC0JVoj
sygQQ7BO/ljAQlcLSKEncgsAz1EyyIKeb0PXwFnbDmNLw31En97Wh3itIe48V2lm
akbnOQI7XXUZzGCX7xRwphQ56B+767X8ab4Vi0ayIrlbdxVUe1qUTgk/uJ2svmPE
xtYG4cR9MD79cbEUEDxcmN0kEsj8MiKGjwe7/kRtfSzfvODyXNBEgxQrogbHFMpd
J6HD9oIQ6flokTXL7vLJUBdeWiZe1AAjV4SUaCeHEl2ahF0ds1lwwsJTF3nio3MN
DoZObJe8EB2pJM24UA3HswY+qRgN5w==
=teHV
-END PGP SIGNATURE End Message ---


Bug#1068018: marked as done (xfce4-power-manager: Brightness control keys no longer work)

2024-04-07 Thread Debian Bug Tracking System
Your message dated Sun, 7 Apr 2024 15:05:03 +0100
with message-id 
and subject line Keys now working again
has caused the Debian Bug report #1068018,
regarding xfce4-power-manager: Brightness control keys no longer work
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 ow...@bugs.debian.org
immediately.)


-- 
1068018: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068018
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xfce4-power-manager
Version: 4.18.3-2
Severity: normal

After a upgrade this morning which did not include this package, the
brightness keys on this Clevo laptop no longer work.

I tried to install the version from experimental 
xfce4-power-manager_4.19.1-1_amd64.deb
but there were too many problematic dependencies to sort out for a quick
test.

After the upgrade the only way I could control the screen brightness was
using an echo as root to 
/sys/class/backlight/intel_backlight/brightness



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

Kernel: Linux 6.6.15-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages xfce4-power-manager depends on:
ii  libc6 2.37-15
ii  libcairo-gobject2 1.18.0-1+b1
ii  libcairo2 1.18.0-1+b1
ii  libglib2.0-0  2.78.4-1
ii  libgtk-3-03.24.41-1
ii  libnotify40.8.3-1
ii  libpango-1.0-01.52.0+ds-1
ii  libpangocairo-1.0-0   1.52.0+ds-1
ii  libupower-glib3   1.90.2-8
ii  libx11-6  2:1.8.7-1
ii  libxext6  2:1.3.4-1+b1
ii  libxfce4ui-2-04.18.4-1
ii  libxfce4util7 4.18.1-2
ii  libxfconf-0-3 4.18.1-1+b1
ii  libxrandr22:1.5.4-1
ii  upower1.90.2-8
ii  xfce4-power-manager-data  4.18.3-2

Versions of packages xfce4-power-manager recommends:
ii  libpam-systemd [logind]  255.4-1
ii  xfce4-power-manager-plugins  4.18.3-2

xfce4-power-manager suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
It seems that the setting to control the Brightness had been turned off.
There are still problems with the power manager since the last update to
version 4.18.3-2, but at least the bightness keys are now back.

ael--- End Message ---


Processed: bug 1067561 is forwarded to https://github.com/canonical/lightdm/issues/352

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

> forwarded 1067561 https://github.com/canonical/lightdm/issues/352
Bug #1067561 {Done: Mike Gabriel } [src:lightdm] FTBFS: 
Error: symbol `open64' is already defined
Set Bug forwarded-to-address to 
'https://github.com/canonical/lightdm/issues/352'.
> thanks
Stopping processing here.

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



Bug#1067561: marked as done (FTBFS: Error: symbol `open64' is already defined)

2024-04-04 Thread Debian Bug Tracking System
Your message dated Thu, 04 Apr 2024 23:04:55 +
with message-id 
and subject line Bug#1067561: fixed in lightdm 1.32.0-5~exp1
has caused the Debian Bug report #1067561,
regarding FTBFS: Error: symbol `open64' is already defined
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 ow...@bugs.debian.org
immediately.)


-- 
1067561: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067561
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: lightdm
Version: 1.32.0-4
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=lightdm=armel=1.32.0-4%2Bb3=1711185127=0

/bin/bash ../../libtool  --tag=CC   --mode=link gcc -Wall
-Wstrict-prototypes  -Wnested-externs
-Werror=missing-prototypes  -Werror=implicit-function-
declaration  -Werror=pointer-arith
-Werror=init-self  -Werror=format-security
-Werror=format=2  -Werror=missing-include-dirs
-I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabi/glib-2.0/include
-I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabi/glib-2.0/include
-I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabi/glib-2.0/include -pthread
-I/usr/include/libmount -I/usr/include/blkid  -I/usr/include/gio-unix-2.0
-I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabi/glib-2.0/include -pthread
-I/usr/include/libmount -I/usr/include/blkid  -g -O2 -Werror=implicit-function-
declaration -ffile-prefix-map=/<>=. -fstack-protector-strong
-fstack-clash-protection -Wformat -Werror=format-security -O0  -Wl,-z,relro
-Wl,-z,now -Wl,-O1 -o Xvnc Xvnc-Xvnc.o Xvnc-x-authority.o Xvnc-x-common.o Xvnc-
x-server.o Xvnc-status.o -lgobject-2.0 -lglib-2.0  -lglib-2.0  -lgio-2.0
-lgobject-2.0 -lglib-2.0  -lgio-2.0 -lgobject-2.0 -lglib-2.0
/tmp/ccCHYR2t.s: Assembler messages:
/tmp/ccCHYR2t.s:2779: Error: symbol `open64' is already defined
/tmp/ccCHYR2t.s:3181: Error: symbol `creat64' is already defined
/tmp/ccCHYR2t.s:3508: Error: symbol `__stat64_time64' is already defined


-- System Information:
Debian Release: trixie/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 
'unstable'), (500, 'testing'), (101, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.7.9-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: lightdm
Source-Version: 1.32.0-5~exp1
Done: Mike Gabriel 

We believe that the bug you reported is fixed in the latest version of
lightdm, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1067...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Mike Gabriel  (supplier of updated lightdm package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 05 Apr 2024 00:36:32 +0200
Source: lightdm
Architecture: source
Version: 1.32.0-5~exp1
Distribution: experimental
Urgency: medium
Maintainer: Debian Xfce Maintainers 
Changed-By: Mike Gabriel 
Closes: 1067561
Changes:
 lightdm (1.32.0-5~exp1) experimental; urgency=medium
 .
   * Non-maintainer upload to experimental.
 .
   * debian/patches:
 + Add 09_time64-t-fix-for-arm-32bit.patch. Fix FTBFS after time_64t
   transition on 32bit architectures. (Closes: #1067561).
Checksums-Sha1:
 cdcdee84f06f4cd0233f3f3d8263f4c3d7f989b1 2890 lightdm_1.32.0-5~exp1.dsc
 21f9ad8bb18687c7f5647f9e67836cd47aba07b7 39340 
lightdm_1.32.0-5~exp1.debian.tar.xz
 7ec6b106dde42a7d9cfa6520bbeb8c205cff8307 18809 
lightdm_1.32.0-5~exp1_source.buildinfo
Checksums-Sha256:
 b2b5eb2a2facdf1da7d3c8165ec5f96d5bcfe0739450284e92be49d89c51b7ac 2890 
lightdm_1.32.0-5~exp1.dsc
 1b6992dbb005cc707f3e751d18f13f8752b7ae9bbf2673365f54fe4fa4a2e7d8 39340 
lightdm_1.32.0-5~exp1.debian.tar.xz
 8b7ec8b38341592fa5bee4f0ad78cb4114e89f77a3d58338eaafcc4dc88d407e 18809 
lightdm_1.32.0-5~exp1_source.buildinfo
Files:
 173fe636ec07f3972a881674556a3a2a 2890 x11 op

Processed: Re: Bug#1068018: Acknowledgement (xfce4-power-manager: Brightness control keys no longer work)

2024-04-02 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> reassign 1068018 xfce4-power-manager-plugins
Bug #1068018 [xfce4-power-manager] xfce4-power-manager: Brightness control keys 
no longer work
Bug reassigned from package 'xfce4-power-manager' to 
'xfce4-power-manager-plugins'.
No longer marked as found in versions xfce4-power-manager/4.18.3-2.
Ignoring request to alter fixed versions of bug #1068018 to the same values 
previously set
>
End of message, stopping processing here.

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



Processed: block 1036884 with 1067272 1067494 1067829 1067561

2024-03-30 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> block 1036884 with 1067272 1067494 1067829 1067561
Bug #1036884 [release.debian.org] transition: time64_t
1036884 was blocked by: 1067193 1067171 1065787 1055530 1067190 1067509 1067189 
1067458 1067069 1062847 1067288 1067677 1055352 1065973 1065816 1067192 1066049 
1067676 1066794 1066328 1067170 1067508 1067175
1036884 was not blocking any bugs.
Added blocking bug(s) of 1036884: 1067272, 1067829, 1067494, and 1067561
> thanks
Stopping processing here.

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



Bug#1041048: marked as done (xfce4-weather-plugin: Met.no API is obsolete)

2024-03-16 Thread Debian Bug Tracking System
Your message dated Sat, 16 Mar 2024 23:43:26 +
with message-id 
and subject line Bug#1041048: fixed in xfce4-weather-plugin 0.11.2-1
has caused the Debian Bug report #1041048,
regarding xfce4-weather-plugin: Met.no API is obsolete
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 ow...@bugs.debian.org
immediately.)


-- 
1041048: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041048
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xfce4-weather-plugin
Version: 0.11.1-1
Severity: normal
Tags: upstream

Dear Maintainer,

Here what I read in the Details tab (French inside):
L’API Met.no sunrise indique que cette version du service Web
est obsolète et le greffon doit être adapté pour utiliser
une version plus récente, ou bien il cessera de fonctionner d’ici quelques
mois.
Veuillez signaler un bogue sur https://gitlab.xfce.org/panel-
plugins/xfce4-weather-plugin/
si personne ne l’a encore fait.

Translated from GT:
The Met.no sunrise API indicates that this version of the web service
is deprecated and the plugin needs to be adapted to use
a newer version, or else it will stop working within a few months.
Please report a bug at https://gitlab.xfce.org/panel-plugins/xfce4-weather-
plugin/
if no one has done it yet.

It seems that the plugin won’t work in a few months because the source’s API is
getting modified.

Yours,
n.


-- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 5.16.0-6-686-pae (SMP w/3 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_FR:fr:en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages xfce4-weather-plugin depends on:
ii  libc62.37-5
ii  libcairo21.16.0-7
ii  libgdk-pixbuf-2.0-0  2.42.10+dfsg-1+b1
ii  libglib2.0-0 2.74.6-2
ii  libgtk-3-0   3.24.37-2
ii  libpango-1.0-0   1.50.14+ds-1
ii  libsoup2.4-1 2.74.3-1
ii  libxfce4panel-2.0-4  4.18.4-1
ii  libxfce4ui-2-0   4.18.4-1
ii  libxfce4util74.18.1-2
ii  libxfconf-0-34.18.1-1
ii  libxml2  2.9.14+dfsg-1.3

xfce4-weather-plugin recommends no packages.

xfce4-weather-plugin suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: xfce4-weather-plugin
Source-Version: 0.11.2-1
Done: Unit 193 

We believe that the bug you reported is fixed in the latest version of
xfce4-weather-plugin, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1041...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Unit 193  (supplier of updated xfce4-weather-plugin package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA384

Format: 1.8
Date: Sat, 16 Mar 2024 18:55:01 -0400
Source: xfce4-weather-plugin
Architecture: source
Version: 0.11.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Xfce Maintainers 
Changed-By: Unit 193 
Closes: 1041048
Changes:
 xfce4-weather-plugin (0.11.2-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream version 0.11.2.
 - Migration to Sunrise API 3.0 (Closes: #1041048)
   * d/control: Add libjson-c-dev to Build-Depends.
Checksums-Sha1:
 114d4c330d2aa5ef4e74003cdf95cba2cb88b228 2277 xfce4-weather-plugin_0.11.2-1.dsc
 8f082eef2e53f1d9ccbc4341d4bfcbe4ad5c 3096214 
xfce4-weather-plugin_0.11.2.orig.tar.bz2
 b35426eb82b5a2da89bb4314db022d34e23f2f1c 5624 
xfce4-weather-plugin_0.11.2-1.debian.tar.xz
 f8ac5f28b008d5b222ce2af1a8a1ec22f54948c0 17280 
xfce4-weather-plugin_0.11.2-1_amd64.buildinfo
Checksums-Sha256:
 384edd961cf1087d893b044179207b075a8532f8d60543a4b833833ba513 2277 
xfce4-weather-plugin_0.11.2-1.dsc
 65d40aff7863550858a9f9d2b6054f27c69a3e7e712991785987f9a73bba876b 3096214 
xfce4-weather-plugin_0.11.2.orig.tar.bz2
 03b1d7a874154a44c9c4ef0851e78426391eb77fd5b2652934b68646adf1c456 5624 
xfce4-weather-plugin_0.11.2-1.debian.tar.xz
 743dd93cf63b2ca46670a6f5dd9412bdd15605723d679998a9136f023c5e0245 17280 
xfce4

Bug#1062998: marked as done (tumbler: NMU diff for 64-bit time_t transition)

2024-02-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Feb 2024 22:37:13 +
with message-id 
and subject line Bug#1062998: fixed in tumbler 4.18.1-1.1
has caused the Debian Bug report #1062998,
regarding tumbler: NMU diff for 64-bit time_t transition
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 ow...@bugs.debian.org
immediately.)


-- 
1062998: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062998
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tumbler
Version: 4.18.1-1
Severity: serious
Tags: patch pending sid trixie
Justification: library ABI skew on upgrade
User: debian-...@lists.debian.org
Usertags: time-t

NOTICE: these changes must not be uploaded to unstable yet!

Dear maintainer,

As part of the 64-bit time_t transition required to support 32-bit
architectures in 2038 and beyond
(https://wiki.debian.org/ReleaseGoals/64bit-time), we have identified
tumbler as a source package shipping runtime libraries whose ABI
either is affected by the change in size of time_t, or could not be
analyzed via abi-compliance-checker (and therefore to be on the safe
side we assume is affected).

To ensure that inconsistent combinations of libraries with their
reverse-dependencies are never installed together, it is necessary to
have a library transition, which is most easily done by renaming the
runtime library package.

Since turning on 64-bit time_t is being handled centrally through a change
to the default dpkg-buildflags (https://bugs.debian.org/1037136), it is
important that libraries affected by this ABI change all be uploaded close
together in time.  Therefore I have prepared a 0-day NMU for tumbler
which will initially be uploaded to experimental if possible, then to
unstable after packages have cleared binary NEW.

Please find the patch for this NMU attached.

If you have any concerns about this patch, please reach out ASAP.  Although
this package will be uploaded to experimental immediately, there will be a
period of several days before we begin uploads to unstable; so if information
becomes available that your package should not be included in the transition,
there is time for us to amend the planned uploads.



-- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.5.0-14-generic (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru tumbler-4.18.1/debian/changelog tumbler-4.18.1/debian/changelog
--- tumbler-4.18.1/debian/changelog 2023-06-13 06:37:06.0 +
+++ tumbler-4.18.1/debian/changelog 2024-02-04 11:07:13.0 +
@@ -1,3 +1,10 @@
+tumbler (4.18.1-1.1) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Steve Langasek   Sun, 04 Feb 2024 11:07:13 +
+
 tumbler (4.18.1-1) unstable; urgency=medium
 
   * Team upload.
diff -Nru tumbler-4.18.1/debian/control tumbler-4.18.1/debian/control
--- tumbler-4.18.1/debian/control   2023-06-13 06:35:49.0 +
+++ tumbler-4.18.1/debian/control   2024-02-04 11:07:12.0 +
@@ -56,7 +56,7 @@
 Package: tumbler-common
 Architecture: all
 Depends: ${misc:Depends}, ${shlibs:Depends}
-Suggests: libtumbler-1-0
+Suggests: libtumbler-1-0t64
 Multi-Arch: foreign
 Description: D-Bus thumbnailing service (common files)
  Tumbler is a D-Bus service for applications to request thumbnails for various
@@ -64,7 +64,10 @@
  .
  This package contains files common to the various binary packages.
 
-Package: libtumbler-1-0
+Package: libtumbler-1-0t64
+Provides: ${t64:Provides}
+Replaces: libtumbler-1-0
+Breaks: libtumbler-1-0 (<< ${source:Version})
 Section: libs
 Architecture: any
 Pre-depends: ${misc:Pre-Depends}
@@ -81,7 +84,7 @@
 Section: libdevel
 Architecture: any
 Depends: libglib2.0-dev,
- libtumbler-1-0 (= ${binary:Version}),
+ libtumbler-1-0t64 (= ${binary:Version}),
  ${misc:Depends},
  ${shlibs:Depends}
 Multi-Arch: same
diff -Nru tumbler-4.18.1/debian/libtumbler-1-0.install 
tumbler-4.18.1/debian/libtumbler-1-0.install
--- tumbler-4.18.1/debian/libtumbler-1-0.install2022-09-16 
08:49:58.0 +
+++ tumbler-4.18.1/debian/libtumbler-1-0.install1970-01-01 
00:00:00.0 +
@@ -1 +0,0 @@
-usr/lib/*/libtumbler-1.so.*
diff -Nru tumbler-4.18.1/debian/libtumbler-1-0.symbols 
tumbler-4.18.1/debian/libtumbler-1-0.symbols
--- tumbler-4.18.1/

Processed: Re: Bug#1063661: xfce4: "IBus Notification: Keymap changes do not work in Plasma Wayland" but this is not Plasma Wayland

2024-02-11 Thread Debian Bug Tracking System
Processing control commands:

> reassign -1 ibus
Bug #1063661 [xfce4] xfce4: "IBus Notification: Keymap changes do not work in 
Plasma Wayland" but this is not Plasma Wayland
Bug reassigned from package 'xfce4' to 'ibus'.
No longer marked as found in versions xfce4/4.18.
Ignoring request to alter fixed versions of bug #1063661 to the same values 
previously set

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



Processed: notfound 1059787 in 4.19.1-1

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

> notfound 1059787 4.19.1-1
Bug #1059787 {Done: Paul Gevers } [src:xfce4-power-manager] 
src:xfce4-power-manager: fails to migrate to testing for too long: uploader 
built arch:all binaries
Ignoring request to alter found versions of bug #1059787 to the same values 
previously set
> thanks
Stopping processing here.

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



Processed: block 1018113 with 1018114 1018115 1018119 1018120 1018124 1018111 1041626 1018133 1041625 1018136

2024-01-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> block 1018113 with 1018114 1018115 1018119 1018120 1018124 1018111 1041626 
> 1018133 1041625 1018136
Bug #1018113 [src:clutter-gtk] clutter-gtk: upstream project discontinued, 
should be removed
1018113 was not blocked by any bugs.
1018113 was blocking: 1018109 996690
Added blocking bug(s) of 1018113: 1018111, 1018136, 1018133, 1041625, 1018115, 
1018114, 1018120, 1041626, 1018124, and 1018119
> thanks
Stopping processing here.

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



Processed (with 1 error): xfce4-panel-profiles: python3-psutil does not get pulled in when installing xfce4-panel-profiles

2024-01-01 Thread Debian Bug Tracking System
Processing control commands:

> severity -1 grave
Bug #1056704 [xfce4-panel-profiles] xfce4-panel-profiles: python3-psutil does 
not get pulled in when installing xfce4-panel-profiles
Severity set to 'grave' from 'important'
> tags patch
Unknown command or malformed arguments to command.


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



Processed: src:xfce4-power-manager: fails to migrate to testing for too long: uploader built arch:all binaries

2024-01-01 Thread Debian Bug Tracking System
Processing control commands:

> close -1 4.18.3-1
Bug #1059787 [src:xfce4-power-manager] src:xfce4-power-manager: fails to 
migrate to testing for too long: uploader built arch:all binaries
Marked as fixed in versions xfce4-power-manager/4.18.3-1.
Bug #1059787 [src:xfce4-power-manager] src:xfce4-power-manager: fails to 
migrate to testing for too long: uploader built arch:all binaries
Marked Bug as done

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



Processed (with 5 errors): Re: Major Dependency Bug in xfce4-panel-profiles

2024-01-01 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 1056704 - wontfix + confirmed
Bug #1056704 [xfce4-panel-profiles] xfce4-panel-profiles: python3-psutil does 
not get pulled in when installing xfce4-panel-profiles
Removed tag(s) wontfix.
Bug #1056704 [xfce4-panel-profiles] xfce4-panel-profiles: python3-psutil does 
not get pulled in when installing xfce4-panel-profiles
Added tag(s) confirmed.
> Sorry copy paste error.
Unknown command or malformed arguments to command.
> On Mon, 2024-01-01 at 08:41 +, Phil Wyett wrote:
Unknown command or malformed arguments to command.
> > severity 1056704 + grave
Unknown command or malformed arguments to command.
> > tags 1056704 + wontfix
Unknown command or malformed arguments to command.
> > thanks
Unknown command or malformed arguments to command.
Too many unknown commands, stopping here.

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



Processed (with 1 error): Re: Major Dependency Bug in xfce4-panel-profiles

2024-01-01 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> severity 1056704 + grave
Unknown command or malformed arguments to command.
> tags 1056704 + wontfix
Bug #1056704 [xfce4-panel-profiles] xfce4-panel-profiles: python3-psutil does 
not get pulled in when installing xfce4-panel-profiles
Added tag(s) wontfix.
> thanks
Stopping processing here.

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



Bug#748558: marked as done (Paste on desktop doesn't work.)

2024-01-01 Thread Debian Bug Tracking System
Your message dated Mon, 01 Jan 2024 08:01:45 +
with message-id <194cf682f15a3d7e53a19539c52d077003babe09.ca...@kathenas.org>
and subject line Re; Paste on desktop doesn't work.
has caused the Debian Bug report #748558,
regarding Paste on desktop doesn't work.
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 ow...@bugs.debian.org
immediately.)


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

Package: xfce4
Version: 4.8.0.3
Severity: important

Copy-pasting a file on Desktop doesn't not work.

The paste button is grayed out. I suspend this happened after the latest 
upgrade.


Anymore information I can provide?
--- End Message ---
--- Begin Message ---
Now, 'wontfix' closing.

Regards

Phil

-- 
Playing the game for the games sake.

Web:

* Debian Wiki: https://wiki.debian.org/PhilWyett
* Website: https://kathenas.org
* Social Debian: https://pleroma.debian.social/kathenas/
* Social Instagram: https://www.instagram.com/kathenasorg/




signature.asc
Description: This is a digitally signed message part
--- End Message ---


Bug#878880: marked as done (xfce4-panel: Xfce goes into kiosk mode after editing "icons, positions of itens and etc." and reboot or logout. At the next login, the panel will be in kiosk mode,it withou

2024-01-01 Thread Debian Bug Tracking System
Your message dated Mon, 01 Jan 2024 08:02:45 +
with message-id <3c959cec4c175499851e32bb5b16081f4e8e4089.ca...@kathenas.org>
and subject line Re: xfce4-panel: Xfce goes into kiosk mode after editing 
has caused the Debian Bug report #878880,
regarding xfce4-panel: Xfce goes into kiosk mode after editing "icons, 
positions of itens and etc." and reboot or logout. At the next login, the panel 
will be in kiosk mode,it without the file config needed to it goes into mode. 
Popup are invoked infinitly showing that is kiosk mode active. Any solotion is 
deleting manualy the directory ~/.cache/sessions and relogin on the system. the 
fallow link can help: the forum that help me to fix it 
https://forum.xfce.org/viewtopic.php?id=8801 and the RedHat bug report with 
more about the some bug https://bugzilla.redhat.com/show_bug.cgi?id=975483
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 ow...@bugs.debian.org
immediately.)


-- 
878880: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878880
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xfce4-panel
Version: 4.12.1-2
Severity: important

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation? After any changes as add new panel, delete 
any icons e other things.
   * What exactly did you do (or not do) that was effective (or
 ineffective)? After made changes on the panel. I logout and login again, 
and goes into kiosk mode.  
   * What was the outcome of this action? Xfce painel goes into kiosk mode
   * What outcome did you expect instead? Xfce panel work normaly with the new 
positions, icons and itens added or removed. 

*** End of the template - remove these template lines ***


-- System Information:
Debian Release: 9.2
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 4.9.0-4-686 (SMP w/1 CPU core)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), 
LANGUAGE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages xfce4-panel depends on:
ii  exo-utils0.10.7-1
ii  libatk1.0-0  2.22.0-1
ii  libc62.24-11+deb9u1
ii  libcairo21.14.8-1
ii  libdbus-1-3  1.10.22-0+deb9u1
ii  libdbus-glib-1-2 0.108-2
ii  libexo-1-0   0.10.7-1
ii  libfontconfig1   2.11.0-6.7+b1
ii  libfreetype6 2.6.3-3.2
ii  libgarcon-1-00.4.0-2
ii  libgdk-pixbuf2.0-0   2.36.5-2+deb9u1
ii  libglib2.0-0 2.50.3-2
ii  libgtk2.0-0  2.24.31-2
ii  libice6  2:1.0.9-2
ii  libpango-1.0-0   1.40.5-1
ii  libpangocairo-1.0-0  1.40.5-1
ii  libpangoft2-1.0-01.40.5-1
ii  libsm6   2:1.2.2-1+b3
ii  libwnck222.30.7-5.1
ii  libx11-6 2:1.6.4-3
ii  libxext6 2:1.3.3-1+b2
ii  libxfce4ui-1-0   4.12.1-2
ii  libxfce4util74.12.1-3
ii  libxfconf-0-24.12.1-1

xfce4-panel recommends no packages.

xfce4-panel suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Now, 'wontfix' closing.

Regards

Phil


-- 
Playing the game for the games sake.

Web:

* Debian Wiki: https://wiki.debian.org/PhilWyett
* Website: https://kathenas.org
* Social Debian: https://pleroma.debian.social/kathenas/
* Social Instagram: https://www.instagram.com/kathenasorg/




signature.asc
Description: This is a digitally signed message part
--- End Message ---


Processed: xfce4-panel: Xfce goes into kiosk mode after editing

2023-12-31 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 878880 + wontfix
Bug #878880 [xfce4-panel] xfce4-panel: Xfce goes into kiosk mode after editing 
"icons, positions of itens and etc." and reboot or logout. At the next login, 
the panel will be in kiosk mode,it without the file config needed to it goes 
into mode. Popup are invoked infinitly showing that is kiosk mode active. Any 
solotion is deleting manualy the directory ~/.cache/sessions and relogin on the 
system. the fallow link can help: the forum that help me to fix it 
https://forum.xfce.org/viewtopic.php?id=8801 and the RedHat bug report with 
more about the some bug https://bugzilla.redhat.com/show_bug.cgi?id=975483
Added tag(s) wontfix.
> thanks
Stopping processing here.

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



Processed: Re: Paste on desktop doesn't work.

2023-12-31 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 748558 + wontfix
Bug #748558 [xfce4] Paste on desktop doesn't work.
Added tag(s) wontfix.
> thanks
Stopping processing here.

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



Bug#1050417: marked as done (lightdm-guest-session support (via Arctica Greeter) takes a long time to startup X11 guest sessions)

2023-11-29 Thread Debian Bug Tracking System
Your message dated Wed, 29 Nov 2023 08:50:42 +
with message-id 
and subject line Bug#1050417: fixed in lightdm 1.32.0-4
has caused the Debian Bug report #1050417,
regarding lightdm-guest-session support (via Arctica Greeter) takes a long time 
to startup X11 guest sessions
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 ow...@bugs.debian.org
immediately.)


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

Package: src:lightdm
Severity: normal
Version: 1.32.0-3
Tags: patch
Forwarded: https://github.com/canonical/lightdm/pull/319


For Debian Edu 12, I tested the various features of Arctica Greeter  
(arctica-greeter src:pkg in Debian). The Arctica Greeter provides a  
feature called guest session login. With this, users can log into a  
host using one-time sessions. The guest user accounts gets created on  
the fly on login and gets removed after the session. A password is not  
required for guest session login.


In Debian 12, the login into an X11 desktop (such as MATE or Xfce4)  
takes a long time to bring up the session. This delay is caused by a  
missing apparmor rule in light.


diff --git a/data/apparmor/lightdm-guest-session.in  
b/data/apparmor/lightdm-guest-session.in

index 3239c54b..f4938c7c 100644
--- a/data/apparmor/lightdm-guest-session.in
+++ b/data/apparmor/lightdm-guest-session.in
@@ -18,6 +18,7 @@
   /usr/bin/sogou-qimpanel-watchdog ix,
   /usr/bin/sogou-sys-notify ix,
   /tmp/sogou-qimpanel:* rwl,
+  /run/user/*/ICEauthority-l l,

   # Allow ibus
   unix (bind, listen) type=stream addr="@tmp/ibus/*",

Here comes the description of the proposed patch:

data/apparmor/lightdm-guest-session.in: Allow l operation on  
/run/user/*/ICEauthority-l.


 This resolves long login delays into X11 guest sessions when using
 Arctica Greeter (forked from Unity Greeter). While waiting for the
 desktop to appear, the screen stays black and a non-WM'ed dialog box
 appears on screen, saying: "Could not update ICEauthority file
 /run/user//ICEauthority".

 When testing with MATE desktop, apparmor denies esp. creating this link
 operation:
 operation="link" class="file" profile="/lightdm-guest-session"
 name="/run/user/997/ICEauthority-l" pid= comm="mate-session"
 requested_mask="l" denied_mask="l" fsuid= ouid=
 target="/run/user//ICEauthority-c"

 Similar in Xfce4:
 operation="link" class="file" profile="/lightdm-guest-session"
 name="/run/user/997/ICEauthority-l" pid= comm="iceauth"
 requested_mask="l" denied_mask="l" fsuid= ouid=
 target="/run/user//ICEauthority-c"


It would be awesome if this could get resolved in the near future in  
Debian unstable and Debian bookworm. I can provide some help with  
these uploads if wanted by the maintainers.


Thanks+Greets,
Mike

--

mike gabriel aka sunweaver (Debian Developer)
mobile: +49 (1520) 1976 148
landline: +49 (4351) 486 14 27

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22  0782 9AF4 6B30 2577 1B31
mail: sunwea...@debian.org, http://sunweavers.net

>From 206320128f9636b814af76230ad64ed3b5e36fb8 Mon Sep 17 00:00:00 2001
From: Mike Gabriel 
Date: Thu, 24 Aug 2023 11:19:02 +0200
Subject: [PATCH] data/apparmor/lightdm-guest-session.in: Allow l operation on
 /run/user/*/ICEauthority-l.

 This resolves long login delays into X11 guest sessions when using
 Arctica Greeter (forked from Unity Greeter). While waiting for the
 desktop to appear, the screen stays black and a non-WM'ed dialog box
 appears on screen, saying: "Could not update ICEauthority file
 /run/user//ICEauthority".

 When testing with MATE desktop, apparmor denies esp. creating this link
 operation:
 operation="link" class="file" profile="/lightdm-guest-session"
 name="/run/user/997/ICEauthority-l" pid= comm="mate-session"
 requested_mask="l" denied_mask="l" fsuid= ouid=
 target="/run/user//ICEauthority-c"

 Similar in Xfce4:
 operation="link" class="file" profile="/lightdm-guest-session"
 name="/run/user/997/ICEauthority-l" pid= comm="iceauth"
 requested_mask="l" denied_mask="l" fsuid= ouid=
 target="/run/user//ICEauthority-c"

Signed-off-by: Mike Gabriel 
---
 data/apparmor/lightdm-guest-session.in | 1 +
 1 file changed, 1 inser

Processed: #1006911 is fixed in version 4.18.8

2023-11-28 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> fixed 1006911 4.18.8-1
Bug #1006911 [thunar] thunar: Cannot use IPv6 addresses in remote URLs
Marked as fixed in versions thunar/4.18.8-1.
>
End of message, stopping processing here.

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



Processed: Re: thunar: Cannot use IPv6 addresses in remote URLs

2023-11-09 Thread Debian Bug Tracking System
Processing control commands:

> tags -1 fixed-upstream
Bug #1006911 [thunar] thunar: Cannot use IPv6 addresses in remote URLs
Added tag(s) fixed-upstream.

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



Bug#977946: marked as done (thunar-archive-plugin: Extraction option missing for tar.lz4 and tar.zstd)

2023-11-09 Thread Debian Bug Tracking System
Your message dated Thu, 09 Nov 2023 23:05:25 +
with message-id 
and subject line Bug#977946: fixed in thunar-archive-plugin 0.5.2-1
has caused the Debian Bug report #977946,
regarding thunar-archive-plugin: Extraction option missing for tar.lz4 and 
tar.zstd
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 ow...@bugs.debian.org
immediately.)


-- 
977946: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977946
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: thunar-archive-plugin
Version: 0.4.0-2
Severity: wishlist

Hello,
I just installed debian testing and I was wondering if there's a way extract
files such as zstd and lz4 within thunar.  I see that files like lzma, 7z, rar,
etc can be extracted with a simple right click + extract,  but not with these
files (zstd, lz4).
It would be appreciated to have files as these handled by this plugin.

Thanks you,
Happy holidays.



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

Kernel: Linux 5.9.0-4-amd64 (SMP w/8 CPU threads)
Locale: LANG=es_CO.UTF-8, LC_CTYPE=es_CO.UTF-8 (charmap=UTF-8), 
LANGUAGE=es_CO:es
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages thunar-archive-plugin depends on:
ii  libatk1.0-0  2.36.0-2
ii  libc62.31-5
ii  libcairo-gobject21.16.0-4
ii  libcairo21.16.0-4
ii  libexo-2-0   0.12.11-1
ii  libgdk-pixbuf2.0-0   2.40.2-2
ii  libglib2.0-0 2.66.3-2
ii  libgtk-3-0   3.24.24-1
ii  libpango-1.0-0   1.46.2-3
ii  libpangocairo-1.0-0  1.46.2-3
ii  libthunarx-3-0   1.8.15-1
ii  libxfce4util74.14.0-2
ii  thunar   1.8.15-1

Versions of packages thunar-archive-plugin recommends:
ii  xarchiver  1:0.5.4.16-1

thunar-archive-plugin suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: thunar-archive-plugin
Source-Version: 0.5.2-1
Done: Unit 193 

We believe that the bug you reported is fixed in the latest version of
thunar-archive-plugin, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 977...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Unit 193  (supplier of updated thunar-archive-plugin 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA384

Format: 1.8
Date: Thu, 09 Nov 2023 17:38:12 -0500
Source: thunar-archive-plugin
Architecture: source
Version: 0.5.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Xfce Maintainers 
Changed-By: Unit 193 
Closes: 977946
Changes:
 thunar-archive-plugin (0.5.2-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream version 0.5.2.
 - Add a few more compression mimetypes, sort the list. (Closes: #977946)
Checksums-Sha1:
 380269b29cfdb24a140d1f0cda5ad4be419da199 2137 thunar-archive-plugin_0.5.2-1.dsc
 6f62040996e3890361448912f76d05e75d0685c5 371599 
thunar-archive-plugin_0.5.2.orig.tar.bz2
 475e887c765920c684bf6dedbdfecab19db9778f 4780 
thunar-archive-plugin_0.5.2-1.debian.tar.xz
 0b631c15f0a3b7581f0b992c93fdc687ad75c074 15730 
thunar-archive-plugin_0.5.2-1_amd64.buildinfo
Checksums-Sha256:
 49f3ff80d700e0881778ac0276773371524231f1a336fce37f4023778ce63b88 2137 
thunar-archive-plugin_0.5.2-1.dsc
 6379f877bcfc0ea85db9f43723b6fb317893050c712bd03c2ae3232fb9d5ade3 371599 
thunar-archive-plugin_0.5.2.orig.tar.bz2
 de90885d8b9815d801059193274fd25fdc51854006c39e39d43b8fb3002f1f75 4780 
thunar-archive-plugin_0.5.2-1.debian.tar.xz
 0c948f332671edc86d217d2aec0b29e624ef55fa40d60c67d456ad7df546fa3d 15730 
thunar-archive-plugin_0.5.2-1_amd64.buildinfo
Files:
 04f656823cebf1abbeba88717e30760f 2137 xfce optional 
thunar-archive-plugin_0.5.2-1.dsc
 2d40af56cdf6ef6a696d2763cb1b6381 371599 xfce optional 
thunar-archive-plugin_0.5.2.orig.tar.bz2
 771f4e1e0a37e5cf0499401958d5437e 4780 xfce optional 
thunar-archive-plugin_0.5.2-1.debian.tar.xz
 fe1d57818d442cb6ad46f75b6686a816 15730 xfce optional 
thunar-archive-plugin_0.5.2-1_amd64.buildinfo

-BEGIN PGP SIGNATURE

Bug#962224: marked as done (lightdm does not source ~/.profile)

2023-10-18 Thread Debian Bug Tracking System
Your message dated Wed, 18 Oct 2023 20:25:59 +0200
with message-id <04e86466609a2bb476159d3f62b7390bab0c5fcb.ca...@debian.org>
and subject line Re: Bug#636108: Still a problem
has caused the Debian Bug report #636108,
regarding lightdm does not source ~/.profile
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 ow...@bugs.debian.org
immediately.)


-- 
636108: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=636108
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lightdm
Version: 1.26.0-4
Severity: normal
Tags: newcomer

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***

Having switched to lightdm from GDM3 (due to another bug in gdm3) I now find
~/.profile does
not run.

In order to debug this I created a clean user (new) called guest (pid=1001)
I modified ~/.profile and ~/.bash_profile to log their use (see attached log)

In summary the behaviour was:

gdm3 + cinnamon = Runs ~/.profile only
gdm3 + xfce = Runs ~/.profile only
gdm3 + gnome3 = Runs ~/.profile only

Switch to lioghtdm & reboot system

lightdm + cinnamon = Runs neither
lightdm + xfce = Runs neither
lightdm + gnome = Runs neither
lightdm + gnome(2nd version) = Runs neither

The doc @ https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/794315 points
to where this has been fixed in the past.




-- System Information:
Debian Release: 10.4
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-9-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages lightdm depends on:
ii  adduser3.118
ii  dbus   1.12.16-1
ii  debconf [debconf-2.0]  1.5.71
ii  libaudit1  1:2.8.4-3
ii  libc6  2.28-10
ii  libgcrypt201.8.4-5
ii  libglib2.0-0   2.58.3-2+deb10u2
ii  libpam-systemd [logind]241-7~deb10u4
ii  libpam0g   1.3.1-5
ii  libxcb11.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
ii  xserver-xephyr   2:1.20.4-1

-- debconf information:
* shared/default-x-display-manager: lightdm
  lightdm/daemon_name: /usr/sbin/lightdm
$ head -20 ~/.profile 
# ~/.profile: executed by the command interpreter for login shells.
# This file is not read by bash(1), if ~/.bash_profile or ~/.bash_login
# exists.
# see /usr/share/doc/bash/examples/startup-files for examples.
# the files are located in the bash-doc package.

# the default umask is set in /etc/profile; for setting the umask
# for ssh logins, install and configure the libpam-umask package.
#umask 022



ENV="/tmp/${USER}.env"
rm -f ${ENV}
echo ".profile run at $(date)" >  ${ENV}
pstree -glus $$>> ${ENV}
env>> ${ENV} 2>&1

LOGON_TIME=$(date) export LOGON_TIME

$ head -20 ~/.bash_profile 
# ~/.profile: executed by the command interpreter for login shells.
# This file is not read by bash(1), if ~/.bash_profile or ~/.bash_login
# exists.
# see /usr/share/doc/bash/examples/startup-files for examples.
# the files are located in the bash-doc package.

# the default umask is set in /etc/profile; for setting the umask
# for ssh logins, install and configure the libpam-umask package.
#umask 022



ENV="/tmp/${USER}-bash.env"
rm -f ${ENV}
echo ".profile run at $(date)" >  ${ENV}
pstree -glus $$>> ${ENV}
env>> ${ENV} 2>&1

LOGON_TIME=$(date) export LOGON_TIME

$ 


*** GDM3 + cinnamon 

$ ls -l /tmp/*.env
-rw-rw-rw- 1 graeme users  462 Jun  4 18:37 /tmp/graeme-bash.env
-rw-r--r-- 1 graeme users 1226 Jun  4 18:37 /tmp/graeme.env
-rw-r--r-- 1 

Bug#636108: marked as done (lightdm: does not source ~/.profile)

2023-10-18 Thread Debian Bug Tracking System
Your message dated Wed, 18 Oct 2023 20:25:59 +0200
with message-id <04e86466609a2bb476159d3f62b7390bab0c5fcb.ca...@debian.org>
and subject line Re: Bug#636108: Still a problem
has caused the Debian Bug report #636108,
regarding lightdm: does not source ~/.profile
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 ow...@bugs.debian.org
immediately.)


-- 
636108: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=636108
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lightdm
Version: 0.9.2-2
Severity: minor

Hello,

lightdm is not sourcing ~/.profile like other dm do (at least gdm2 and 
slim).

Thanks,
Andrei

-- System Information:
Debian Release: wheezy/sid
  APT prefers oldstable
  APT policy: (500, 'oldstable'), (500, 'unstable'), (500, 'testing'), (500, 
'stable'), (1, 'experimental')
Architecture: i386 (x86_64)

Kernel: Linux 3.0.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=ro_RO.UTF-8, LC_CTYPE=ro_RO.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages lightdm depends on:
ii  adduser   3.113  add and remove users and groups
ii  consolekit0.4.5-1framework for defining and trackin
ii  dbus  1.4.14-1   simple interprocess messaging syst
ii  debconf [debconf-2.0] 1.5.41 Debian configuration management sy
ii  libc6 2.13-11Embedded GNU C Library: Shared lib
ii  libglib2.0-0  2.28.6-1   The GLib library of C routines
ii  libpam0g  1.1.3-2Pluggable Authentication Modules l
ii  libxcb1   1.7-3  X C Binding
ii  libxdmcp6 1:1.1.0-3  X11 Display Manager Control Protoc
ii  lightdm-gtk-greeter   0.9.2-2simple display manager (GTK+ greet

Versions of packages lightdm recommends:
ii  xserver-xorg  1:7.6+7X.Org X server

lightdm suggests no packages.

-- debconf information:
  lightdm/daemon_name: /usr/sbin/lightdm
* shared/default-x-display-manager: lightdm


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

On Wed, 2023-10-18 at 12:41 -0500, Ed Siefker wrote:
> Can we revisit this issue?  Upstream lightdm sources .profile, I don't
> understand why Debian changes it.

Still no.
> 
> Even if .profile shouldn't be used for graphical shells, ~/.local/bin
> should clearly be in PATH out of the box.

That's actually not my area of responsibility though.

> If sourcing .profile is unacceptable, the contents of .profile should
> be moved somewhere they will get sourced.

Just move it to .xsessionrc as documented iin

> It's 12 years later, and this issue is still inconveniencing users.

The .xsessionrc path has already been documented 12 years ago.

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

iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmUwIzcACgkQ3rYcyPpX
RFtOqQgA2MdH0tqjlsLKmoJJGx7EU1zURyqaB9GMEuOSTgY4Bjk97gESnsi4UcuM
iKrEkM33vl15WV4UCWB4sReQ3wGOb45iVyn7reTgd81rcOBi/Ovfk16L+5NNpqMz
8WKq0b0yZUUtKq9GsVP7Ql+QoYK1dLVvtgAsdG8tV/R+Dq5R4C95AolCXZ3jn/4C
g0DgMM/79ybkxPsATOAbpHLaUh03T9rsdocK8/jBfXqUs6hnwQ5B4BIKthkhwNkE
MqhhcjB9Nt4y9HE+ild8u6B6VFFrvUjnMjASAqPT/RZN/LEeloQsr3fIw0Jr8vZG
GYa447uDBbE8Lge3zWQC7cbU8KUBlQ==
=raw9
-END PGP SIGNATURE End Message ---


Bug#672793: marked as done (lightdm does not source ~/.profile)

2023-10-18 Thread Debian Bug Tracking System
Your message dated Wed, 18 Oct 2023 20:25:59 +0200
with message-id <04e86466609a2bb476159d3f62b7390bab0c5fcb.ca...@debian.org>
and subject line Re: Bug#636108: Still a problem
has caused the Debian Bug report #636108,
regarding lightdm does not source ~/.profile
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 ow...@bugs.debian.org
immediately.)


-- 
636108: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=636108
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lightdm
Version: 1.0.11-1
Severity: normal

Dear Maintainer,

I just switched from KDM and to lightdm, and had to notice that ~/bin was
dropped from my PATH. The reason is that KDM sources ~/.profile on login, but
lightdm obviously does not.
This was also reported, and fixed, in Ubuntu:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/794315

Kind regards,
Ralf



-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages lightdm depends on:
ii  adduser3.113+nmu1
ii  consolekit 0.4.5-3
ii  dbus   1.5.12-1
ii  debconf [debconf-2.0]  1.5.42
ii  libc6  2.13-32
ii  libglib2.0-0   2.32.2-1
ii  libpam0g   1.1.3-7
ii  libxcb11.8.1-1
ii  libxdmcp6  1:1.1.1-1
ii  lightdm-gtk-greeter1.0.11-1

Versions of packages lightdm recommends:
ii  xserver-xorg  1:7.6+12

Versions of packages lightdm suggests:
pn  accountsservice  

-- debconf information:
  lightdm/daemon_name: /usr/sbin/lightdm
* shared/default-x-display-manager: lightdm


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

On Wed, 2023-10-18 at 12:41 -0500, Ed Siefker wrote:
> Can we revisit this issue?  Upstream lightdm sources .profile, I don't
> understand why Debian changes it.

Still no.
> 
> Even if .profile shouldn't be used for graphical shells, ~/.local/bin
> should clearly be in PATH out of the box.

That's actually not my area of responsibility though.

> If sourcing .profile is unacceptable, the contents of .profile should
> be moved somewhere they will get sourced.

Just move it to .xsessionrc as documented iin

> It's 12 years later, and this issue is still inconveniencing users.

The .xsessionrc path has already been documented 12 years ago.

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

iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmUwIzcACgkQ3rYcyPpX
RFtOqQgA2MdH0tqjlsLKmoJJGx7EU1zURyqaB9GMEuOSTgY4Bjk97gESnsi4UcuM
iKrEkM33vl15WV4UCWB4sReQ3wGOb45iVyn7reTgd81rcOBi/Ovfk16L+5NNpqMz
8WKq0b0yZUUtKq9GsVP7Ql+QoYK1dLVvtgAsdG8tV/R+Dq5R4C95AolCXZ3jn/4C
g0DgMM/79ybkxPsATOAbpHLaUh03T9rsdocK8/jBfXqUs6hnwQ5B4BIKthkhwNkE
MqhhcjB9Nt4y9HE+ild8u6B6VFFrvUjnMjASAqPT/RZN/LEeloQsr3fIw0Jr8vZG
GYa447uDBbE8Lge3zWQC7cbU8KUBlQ==
=raw9
-END PGP SIGNATURE End Message ---


Processed: reassign 1038285 to src:cryptsetup, fixed 1038285 in 2:2.6.1-5 ..., fixed 1050291 in 13.0.3-1 ...

2023-10-13 Thread Debian Bug Tracking System
nger marked as found in versions thunar/1.8.15-1.
> tags 1015458 - bookworm
Bug #1015458 [src:kproperty] kproperty: ftbfs with LTO (link time optimization) 
enabled
Removed tag(s) bookworm.
> tags 1015415 - bookworm
Bug #1015415 [src:gesftpserver] gesftpserver: ftbfs with LTO (link time 
optimization) enabled
Removed tag(s) bookworm.
> affects 1028397 + src:goldendict-webengine
Bug #1028397 {Done: Boyuan Yang } [goldendict-webengine] 
Please switch goldendict-webengine to Qt6
Added indication that 1028397 affects src:goldendict-webengine
> reassign 1028397 src:goldendict-ng
Bug #1028397 {Done: Boyuan Yang } [goldendict-webengine] 
Please switch goldendict-webengine to Qt6
Bug reassigned from package 'goldendict-webengine' to 'src:goldendict-ng'.
Ignoring request to alter found versions of bug #1028397 to the same values 
previously set
No longer marked as fixed in versions goldendict-ng/23.06.02-1.
> fixed 1028397 23.06.02-1
Bug #1028397 {Done: Boyuan Yang } [src:goldendict-ng] Please 
switch goldendict-webengine to Qt6
Marked as fixed in versions goldendict-ng/23.06.02-1.
> fixed 779179 1:0.7.1-1
Bug #779179 {Done: Akbarkhon Variskhanov } 
[xfce4-xkb-plugin] xfce4-xkb-plugin: Forgets 'Change layout option' setting 
after restart
Marked as fixed in versions xfce4-xkb-plugin/1:0.7.1-1.
> tags 1051383 + experimental
Bug #1051383 {Done: David Prévot } [phpcpd] Unsatisfiable 
dependencies with PHPUnit 10
Added tag(s) experimental.
> tags 1048245 + experimental
Bug #1048245 {Done: Mattia Rizzolo } [src:lib2geom] 
lib2geom: Fails to build source after successful build
Added tag(s) experimental.
> fixed 964931 4.2.0-1
Bug #964931 {Done: xiao sheng wen(肖盛文) } [src:imv] imv 
FTCBFS: hard codes the build architecture pkg-config
Marked as fixed in versions imv/4.2.0-1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1015415: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015415
1015458: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015458
1028397: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028397
1034541: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034541
1035461: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035461
1036470: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036470
1036899: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036899
1038285: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038285
1041471: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041471
1048245: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1048245
1050291: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050291
1051383: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051383
561240: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=561240
779179: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779179
832239: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832239
837708: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837708
864502: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864502
941953: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941953
964931: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964931
985347: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985347
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Processed: tagging 1041458, tagging 1007596, tagging 1007688, tagging 1007042, tagging 1015653 ...

2023-10-12 Thread Debian Bug Tracking System
ian Germann } [src:gnokii] xgnokii: 
can't read sms since memory_type IN/OU for nokia drivers is not supported.
Marked as fixed in versions gnokii/0.6.31+dfsg-4.
> tags 1007373 - bookworm
Bug #1007373 {Done: Bastian Germann } [src:coco-cpp] coco-cpp: 
please consider upgrading to 3.0 source format
Removed tag(s) bookworm.
> tags 1007341 - bookworm
Bug #1007341 {Done: Bastian Germann } [src:coco-java] 
coco-java: please consider upgrading to 3.0 source format
Removed tag(s) bookworm.
> tags 968808 - bookworm wontfix
Bug #968808 {Done: Boyuan Yang } [src:lightdm] lightdm: 
Please package new upstream release (1.30.0)
Removed tag(s) bookworm and wontfix.
> tags 1015524 - bookworm
Bug #1015524 {Done: Yangfl } [src:libsimpleini] 
libsimpleini: ftbfs with LTO (link time optimization) enabled
Removed tag(s) bookworm.
> tags 1007595 - bookworm
Bug #1007595 {Done: Michael Ablassmeier } 
[src:libaudio-scrobbler-perl] libaudio-scrobbler-perl: please consider 
upgrading to 3.0 source format
Removed tag(s) bookworm.
> tags 1007634 - bookworm
Bug #1007634 {Done: Michael Ablassmeier } 
[src:libmp4-info-perl] libmp4-info-perl: please consider upgrading to 3.0 
source format
Removed tag(s) bookworm.
> tags 1007635 - bookworm
Bug #1007635 {Done: gregor herrmann } 
[src:libemail-foldertype-perl] libemail-foldertype-perl: please consider 
upgrading to 3.0 source format
Removed tag(s) bookworm.
> tags 1007526 - bookworm
Bug #1007526 {Done: Michael Ablassmeier } 
[src:libnet-proxy-perl] libnet-proxy-perl: please consider upgrading to 3.0 
source format
Removed tag(s) bookworm.
> tags 955929 - bullseye
Bug #955929 {Done: Bastian Germann } [src:ogmrip] ogmrip: 
Depends on deprecated dbus-glib
Removed tag(s) bullseye.
> tags 936390 - bullseye
Bug #936390 {Done: Carlos Henrique Lima Melara } 
[src:dhcpig] dhcpig: Python2 removal in sid/bullseye
Removed tag(s) bullseye.
> tags 895089 - bookworm bullseye
Bug #895089 {Done: Scott Kitterman } [src:postfix] 
postfix: Please replace 'c_rehash' with 'openssl rehash'
Removed tag(s) bullseye and bookworm.
> tags 922947 - bullseye
Bug #922947 {Done: Jonathan McDowell } [retroarch-assets] 
retroarch-assets: please don’t use hinted Roboto fonts
Removed tag(s) bullseye.
> tags 895280 - buster bullseye
Bug #895280 {Done: Emmanuel Bourg } 
[src:maven-javadoc-plugin] libgoogle-gson-java ftbfs with OpenJDK 10 from 
experimental
Removed tag(s) buster and bullseye.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1007042: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007042
1007341: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007341
1007373: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007373
1007526: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007526
1007595: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007595
1007596: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007596
1007634: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007634
1007635: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007635
1007688: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007688
1015524: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015524
1015653: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015653
1041458: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041458
485987: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=485987
485988: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=485988
616186: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=616186
626027: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=626027
895089: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895089
895280: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895280
895826: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895826
922947: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922947
936390: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936390
940095: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940095
955929: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955929
965021: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965021
968808: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968808
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#1038611: marked as done (lightdm 1.32 fails to start X on nvidia binary driver)

2023-10-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Oct 2023 23:11:09 +0200
with message-id 
and subject line Re: Bug#1038611: Help with investigating a bug in the 
LightDM/logind/DDX stack
has caused the Debian Bug report #1038611,
regarding lightdm 1.32 fails to start X on nvidia binary driver
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 ow...@bugs.debian.org
immediately.)


-- 
1038611: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038611
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lightdm
Version: 1.32.0-2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

After upgrading lightdm to the latest upstream version (1.32.0-2) fails to
start X session leading only to console mode.

Downgrading to 1.26.0-8, from testing, fixes this bug.



-- System Information:
Debian Release: trixie/sid
 APT prefers unstable
 APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.3.8 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8),
LANGUAGE=pt_BR:p
t:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages lightdm depends on:
ii  adduser3.134
ii  dbus   1.14.8-1
ii  debconf [debconf-2.0]  1.5.82
ii  libaudit1  1:3.0.9-1
ii  libc6  2.36-9
ii  libgcrypt201.10.2-2
ii  libglib2.0-0   2.74.6-2
ii  libpam-systemd [logind]252.11-1
ii  libpam0g   1.5.2-6
ii  libxcb11.15-1
ii  libxdmcp6  1:1.1.2-3
ii  lightdm-gtk-greeter [lightdm-greeter]  2.0.8-3

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

Versions of packages lightdm suggests:
ii  accountsservice  22.08.8-6
ii  upower   0.99.20-2
ii  xserver-xephyr   2:21.1.7-3

-- debconf information:
* shared/default-x-display-manager: lightdm
 lightdm/daemon_name: /usr/sbin/lightdm
--- End Message ---
--- Begin Message ---
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Thu, 2023-10-05 at 22:55 -0300, Adilson dos Santos Dantas wrote:
> But this module was not loaded at boot time and I found an old nvidia.conf
> at /etc/modprobe.d. Probably it was from an old nvidia package and it
> prevented this module from loading..
> 
> I removed this file and finally nvidia_drm was loaded in the next boot. It
> worked with lightdm and with sddm. With sddm it stopped working for more
> than one year until I removed nvidia.conf from modprobe.d.
> 
> Then, for me, the root cause is a nvidia_drm module not loaded due to a file
> in modprobe.d . I don't know if there is something similar with the
> RasperryPi 4. 
> 
Ok, thanks for the investigation, that's good to know. So it looks like an
issue isolated to your box (and maybe Steev test box) and not a general one.

I'm closing the bug on those grounds, feel free to reopen if needed.

And hopefully the bug will serve as documentation in case other people
experience that.

Have a nice day.

Regards,
- -- 
Yves-Alexis

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmUgd+0ACgkQ3rYcyPpX
RFv9gggA2c+vR8Kpd3tUHPWmJI5YdhlXatkRHDydiLsNKQrLxxTdoCvKSdNTsAeW
r72EesXtzJkRD4Z5FanIETPW9SF/e6s9Rv7iFhbhI6R17FLLE7/lqtr9jA9W4lLB
u3iRSyHz5s0TpiKn98t696Fm4m2F0PA1Uqd6cGgEyBacQXNCHd8Z2zEWEEwPK6n6
evWs95HO0Lq8Y+qLae6fxJevhfXtnZNB25sL2xo3sqRi10lKI44VAtpAiq9zd5l8
zBp7h/bNpQXFKyndm5xKsxB1LjNppFTwhRkSwJMmipkJyEwabRh3vs7QeapkRFd5
JfevfeLD8CLLKSzFqshuyK6PZ0hasw==
=KCFo
-END PGP SIGNATURE End Message ---


Bug#1050734: marked as done (xfce4-terminal: Preference to disable F10 key not working)

2023-10-03 Thread Debian Bug Tracking System
Your message dated Tue, 03 Oct 2023 20:43:32 +
with message-id 
and subject line Bug#1050734: fixed in xfce4-terminal 1.1.0-2
has caused the Debian Bug report #1050734,
regarding xfce4-terminal: Preference to disable F10 key not working
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 ow...@bugs.debian.org
immediately.)


-- 
1050734: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050734
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xfce4-terminal
Version: 1.1.0-1
Severity: normal

Dear Maintainer,

Edit-> Preferences in xfce4-terminal includes a checkbox to disable use
of the F10 key by the terminal so it can be used by the running
program. This is not working, F10 is working as the terminal menu key.
I have cleared the box, closed the terminal, opened another one and
checked the box, no change.

In mc, F10 is the key to close the current file and also to close mc.
mc does have a backup in the form of a bottom F-key bar, which can be
clicked with a mouse, but having used mc for a couple of decades, this
action does not come normally for me, I normally operate mc with just
the keyboard.

This problem has happened in the last week or two, I've been using
xfce4-terminal with mc for years previously.


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

Kernel: Linux 6.4.0-3-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages xfce4-terminal depends on:
ii  exo-utils4.18.0-1
ii  libatk1.0-0  2.49.90-4
ii  libc62.37-7
ii  libcairo21.16.0-7
ii  libgdk-pixbuf-2.0-0  2.42.10+dfsg-1+b1
ii  libglib2.0-0 2.77.2-1
ii  libgtk-3-0   3.24.38-4
ii  libpango-1.0-0   1.51.0+ds-2
ii  libpcre2-8-0 10.42-3
ii  libutempter0 1.2.1-3
ii  libvte-2.91-00.73.93-1
ii  libx11-6 2:1.8.6-1
ii  libxfce4ui-2-0   4.18.4-1
ii  libxfce4util74.18.1-2
ii  libxfconf-0-34.18.1-1
ii  perl 5.36.0-8

Versions of packages xfce4-terminal recommends:
ii  dbus-user-session [default-dbus-session-bus]  1.14.8-2

xfce4-terminal suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: xfce4-terminal
Source-Version: 1.1.0-2
Done: Yves-Alexis Perez 

We believe that the bug you reported is fixed in the latest version of
xfce4-terminal, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1050...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Yves-Alexis Perez  (supplier of updated xfce4-terminal 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 03 Oct 2023 21:59:06 +0200
Source: xfce4-terminal
Architecture: source
Version: 1.1.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Xfce Maintainers 
Changed-By: Yves-Alexis Perez 
Closes: 1050734
Changes:
 xfce4-terminal (1.1.0-2) unstable; urgency=medium
 .
   [ Mateusz Łukasik ]
   * Add cherry pick from upstream for fix not working preference to disable
 F10 key. (Closes: #1050734)
Checksums-Sha1:
 0d04e10f2737038542b1954a3e821576e686fa51 1834 xfce4-terminal_1.1.0-2.dsc
 f12abf923cfbd4368a1bce33b9f57c217067bfd7 9660 
xfce4-terminal_1.1.0-2.debian.tar.xz
 464ba93bdedcb82c9e12e8bcf6d83f9d407822de 16641 
xfce4-terminal_1.1.0-2_amd64.buildinfo
Checksums-Sha256:
 d0a198238ce2af4153bf603e9b8a848f61fc1b0b8c9d082771a29ad27a8e 1834 
xfce4-terminal_1.1.0-2.dsc
 367757f74727f232e793151047bcd88fd7acbf365d9453e546a5ddd8629aa2b1 9660 
xfce4-terminal_1.1.0-2.debian.tar.xz
 40abbc53f80496105ca3ce62e74b5896214fbdf745e0e802587d69b123086d15 16641 
xfce4-terminal_1.1.0-2_amd64.buildinfo
Files:
 7e8957dba8d838fcf545a47046265b48 1834 xfce optional xfce4-terminal_1.1.0-2.dsc
 f3cd1283c21b970cd687f20ebc6fd5f8 9660 xfce optional 
xfce4-terminal_1.1.0-2.debian.tar.xz
 09e9b60283f87c6eb790a25a68741a2c 16641 xfce optional 
xf

Processed: your mail

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

> reassign 1029557 lightdm 1.32.0-3
Bug #1029557 [debian-edu-config] debian-edu-config: Session exits on first 
login on roaming-workstation fails
Bug reassigned from package 'debian-edu-config' to 'lightdm'.
No longer marked as found in versions debian-edu-config/2.11.56+deb11u4.
Ignoring request to alter fixed versions of bug #1029557 to the same values 
previously set
Bug #1029557 [lightdm] debian-edu-config: Session exits on first login on 
roaming-workstation fails
Marked as found in versions lightdm/1.32.0-3.
> forwarded 1029557 https://github.com/canonical/lightdm/issues/322
Bug #1029557 [lightdm] debian-edu-config: Session exits on first login on 
roaming-workstation fails
Set Bug forwarded-to-address to 
'https://github.com/canonical/lightdm/issues/322'.
> merge 1029557 1052389
Bug #1029557 [lightdm] debian-edu-config: Session exits on first login on 
roaming-workstation fails
Bug #1052389 [lightdm] First login with libpam-mklocaluser always fails
Merged 1029557 1052389
>
End of message, stopping processing here.

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



Processed: your mail

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

> forwarded 1052389 https://github.com/canonical/lightdm/issues/322
Bug #1052389 [lightdm] First login with libpam-mklocaluser always fails
Set Bug forwarded-to-address to 
'https://github.com/canonical/lightdm/issues/322'.
>
End of message, stopping processing here.

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



Bug#1049418: marked as done (xfce4-pulseaudio-plugin: Please loosen Recommends, and allow pipewire-pulse as an alternative to pulseaudio)

2023-09-14 Thread Debian Bug Tracking System
Your message dated Thu, 14 Sep 2023 20:47:39 +
with message-id 
and subject line Bug#1049418: fixed in xfce4-pulseaudio-plugin 0.4.7-2
has caused the Debian Bug report #1049418,
regarding xfce4-pulseaudio-plugin: Please loosen Recommends, and allow 
pipewire-pulse as an alternative to pulseaudio
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 ow...@bugs.debian.org
immediately.)


-- 
1049418: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1049418
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xfce4-pulseaudio-plugin
Version: 0.4.7-1
Severity: normal
User: de...@kali.org
Usertags: origin-kali

Dear Maintainer,

it would be nice if xfce4-pulseaudio-plugin would Recommend
'pulseaudio|pipewire-pulse' instead of simply 'pulseaudio'.

For background: in Kali Linux (a derivative based on Debian testing), we
switched from pulseaudio to pipewire in our flagship desktop XFCE, that
was back in May 2023 [1]. So far so good: sound works great, via the
compat daemon pipewire-pulse. I'm not claiming *everything* works 100%
(I just don't know), but it seems that it works well enough, based on
the feedback we had so far on our bug tracker.

XUbuntu (XFCE's flavor of Ubuntu) also switched to pipewire in version
23.04, back in Apr 2023 [2].

A minor issue, in Kali, is that we still have to install pulseaudio, due
to the fact that xfce4-pulseaudio-plugin depends on pulseaudio. So
pulseaudio must be installed, even though it's not running.

On the same line, we also can't install the metapackage pipewire-audio,
since it Conflicts with pulseaudio, hence breaks the xfce4 metapackage.

Changing the Recommends field of xfce4-pulseaudio-plugin to
'pulseaudio|pipewire-pulse' would solve those two issues, and more
generally it would make life easier for people who want to switch to
pipewire and remove pulseaudio.

Thanks for considering this change,

Arnaud

[1] https://www.kali.org/blog/kali-linux-2023-2-release/#xfce--pipewire
[2] https://xubuntu.org/news/xubuntu-23-04-released/
--- End Message ---
--- Begin Message ---
Source: xfce4-pulseaudio-plugin
Source-Version: 0.4.7-2
Done: Yves-Alexis Perez 

We believe that the bug you reported is fixed in the latest version of
xfce4-pulseaudio-plugin, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1049...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Yves-Alexis Perez  (supplier of updated 
xfce4-pulseaudio-plugin package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 13 Sep 2023 22:22:50 +0200
Source: xfce4-pulseaudio-plugin
Architecture: source
Version: 0.4.7-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Xfce Maintainers 
Changed-By: Yves-Alexis Perez 
Closes: 1049418
Changes:
 xfce4-pulseaudio-plugin (0.4.7-2) unstable; urgency=medium
 .
   * d/control: add pipewire-pulse as alternate recommends for pulseaudio
 (Closes: #1049418)
Checksums-Sha1:
 63f270727a50bad5dc727e2ea5c639c26dfa4cc3 2038 
xfce4-pulseaudio-plugin_0.4.7-2.dsc
 2ee8dbea6297385ed781f0c110cade736cd2f0fb 3648 
xfce4-pulseaudio-plugin_0.4.7-2.debian.tar.xz
 1cc8a86eb4550c23bdb946270d22ac8ce203e0fe 16648 
xfce4-pulseaudio-plugin_0.4.7-2_amd64.buildinfo
Checksums-Sha256:
 7842f75f93d6574914c13c634fb27a41d7389ebd3d20cf6d4505696c870ffbcf 2038 
xfce4-pulseaudio-plugin_0.4.7-2.dsc
 e7ab85cfa7a7c3532fce648b6ed28a432d6efaa8bb180efbe81d6edf2fc0caa9 3648 
xfce4-pulseaudio-plugin_0.4.7-2.debian.tar.xz
 6b3fcbd74ff90c11e6a3608f388608f85f346fb2d0f2abca7efd8094eec5ddab 16648 
xfce4-pulseaudio-plugin_0.4.7-2_amd64.buildinfo
Files:
 71a40bc241bc14bf0bce22dae05a1ab4 2038 xfce optional 
xfce4-pulseaudio-plugin_0.4.7-2.dsc
 ea423bfa1a0d6e5934d5badee4222eeb 3648 xfce optional 
xfce4-pulseaudio-plugin_0.4.7-2.debian.tar.xz
 5b6c2d8c3ea92d5c532ed42b67c72505 16648 xfce optional 
xfce4-pulseaudio-plugin_0.4.7-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmUDZd4ACgkQ3rYcyPpX
RFsT8QgAhIebB0lTVaJMxODlgwK7jqFAMMGw0YRFVeuZnwYd/CD7Il4SR/arZMOd
xHxPOUM2d5ggSLFJU1u+JC0nmEYAeCon4EGYirB3U1RUbgBTdY4IquM4IM+VUYJz
zyP6BBLWc4/E6p++kLVubEFxyiz6w1qwtx162CXW1fwrQB2xYicJmwzcHcN0Jmic

Processed: Re: Bug#1050802: xfce4-session: please provide an xfce-portals.conf for xdg-desktop-portal

2023-09-12 Thread Debian Bug Tracking System
Processing control commands:

> tags -1 + patch fixed-upstream
Bug #1050802 [src:xfce4-session] xfce4-session: please provide an 
xfce-portals.conf for xdg-desktop-portal
Added tag(s) patch and fixed-upstream.

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



Processed: Re: Bug#1050802: xfce4-session: please provide an xfce-portals.conf for xdg-desktop-portal

2023-09-11 Thread Debian Bug Tracking System
Processing control commands:

> tags -1 + upstream
Bug #1050802 [src:xfce4-session] xfce4-session: please provide an 
xfce-portals.conf for xdg-desktop-portal
Added tag(s) upstream.
> forwarded -1 https://gitlab.xfce.org/xfce/xfce4-session/-/issues/181
Bug #1050802 [src:xfce4-session] xfce4-session: please provide an 
xfce-portals.conf for xdg-desktop-portal
Set Bug forwarded-to-address to 
'https://gitlab.xfce.org/xfce/xfce4-session/-/issues/181'.

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



Bug#760652: marked as done (xfce4-session: startx + logind + README.Debian)

2023-09-01 Thread Debian Bug Tracking System
Your message dated Fri, 1 Sep 2023 19:55:23 +0100
with message-id <01092023195235.f2f5ac51a...@desktop.copernicus.org.uk>
and subject line xfce4-session: startx + logind + README.Debian
has caused the Debian Bug report #760652,
regarding xfce4-session: startx + logind + README.Debian
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 ow...@bugs.debian.org
immediately.)


-- 
760652: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760652
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
package: xfce4-session
Version: 4.10.1-8
Severity: wishlist



README.Debian has a nice section entitled "Running Xfce from the console",
which was written for Wheezy as a result of #658284:

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

This advice does not to be appear applicable under Jessie's default init system.
However, the changelog for xinit_1.3.3-1 has

  * 10-startx-Under-Linux-start-X-on-the-current-VT.patch,
11-startx-Pass-vtX-as-long-as-the-user-did-not-specify-.patch: By default
start the server on the current VT, this is necessary to avoid logind to
see the startx session as inactive (Closes: #743015)

Basically, startx just works and nothing should have to be done for the
session to be active.

I'd suggest replacing the present text with a short note on this behaviour
with logind. Or maybe nothing is needed at all?

Regards,

Brian.




-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 3.14-2-686-pae (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages xfce4-session depends on:
ii  libatk1.0-02.12.0-1
ii  libc6  2.19-10
ii  libcairo2  1.12.16-4
ii  libdbus-1-31.8.6-2
ii  libcairo2  1.12.16-4
ii  libdbus-1-31.8.6-2
ii  libcairo2  1.12.16-4
ii  libdbus-1-31.8.6-2
ii  libdbus-glib-1-2   0.102-1
ii  libfontconfig1 2.11.0-6.1
ii  libfreetype6   2.5.2-1.1
ii  libgdk-pixbuf2.0-0 2.30.8-1
ii  libglib2.0-0   2.40.0-5
ii  libgtk2.0-02.24.24-1
ii  libice62:1.0.9-1
ii  libpango-1.0-0 1.36.6-1
ii  libpangocairo-1.0-01.36.6-1
ii  libpangoft2-1.0-0  1.36.6-1
ii  libpolkit-gobject-1-0  0.105-6.1
ii  libsm6 2:1.2.2-1
ii  libwnck22  2.30.7-1
ii  libx11-6   2:1.6.2-3
ii  libxfce4ui-1-0 4.10.0-5
ii  libxfce4util6  4.10.1-2
ii  libxfconf-0-2  4.10.0-3
ii  multiarch-support  2.19-10
ii  xfce4-settings 4.10.1-2
ii  xfconf 4.10.0-3

Versions of packages xfce4-session recommends:
ii  dbus-x11   1.8.6-2
ii  libpam-systemd 208-8
ii  systemd-sysv   208-8
ii  upower 0.99.1-3
ii  x11-xserver-utils  7.7+3
ii  xfdesktop4 4.10.2-3
ii  xfwm4  4.10.1-2
ii  xscreensaver   5.26-1

Versions of packages xfce4-session suggests:
pn  fortunes-mod  
pn  sudo  

-- no debconf information
pn  sudo  
--- End Message ---
--- Begin Message ---
As I said:

> Or maybe nothing is needed at all?

After nine years this is probably the best solution.

Cheers,

Brian.--- End Message ---


Processed: Issue affects arctica-greeter-guest-session

2023-08-24 Thread Debian Bug Tracking System
Processing control commands:

> affects -1 arctica-greeter-guest-session
Bug #1050417 [src:lightdm] lightdm-guest-session support (via Arctica Greeter) 
takes a long time to startup X11 guest sessions
Added indication that 1050417 affects arctica-greeter-guest-session

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



Bug#955855: marked as done (xfburn: unnecessarily Build-Depends on deprecated dbus-glib)

2023-08-14 Thread Debian Bug Tracking System
Your message dated Tue, 15 Aug 2023 03:37:14 +
with message-id 
and subject line Bug#955855: fixed in xfburn 0.7.0-1
has caused the Debian Bug report #955855,
regarding xfburn: unnecessarily Build-Depends on deprecated dbus-glib
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 ow...@bugs.debian.org
immediately.)


-- 
955855: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955855
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xfburn
Version: 0.6.2-1
Severity: normal
User: pkg-utopia-maintain...@lists.alioth.debian.org
Usertags: dbus-glib-deprecation
Control: block 895291 by -1

dbus-glib is a deprecated D-Bus library with some significant design
flaws, and is essentially unmaintained. As announced in [0], I would
like to minimize its use, and eventually remove it from Debian.

This package Build-Depends on libdbus-glib-1-dev, but I couldn't find any
sign of it actually *using* dbus-glib - perhaps it used to use dbus-glib
but does not any more? If this analysis is correct, please remove the
Build-Depends on libdbus-glib-1-dev.

If this package has uses of dbus-glib that I have missed, please see
[0] for how to proceed.

Thanks,
smcv

[0] https://lists.debian.org/debian-devel/2020/03/msg00272.html
--- End Message ---
--- Begin Message ---
Source: xfburn
Source-Version: 0.7.0-1
Done: Unit 193 

We believe that the bug you reported is fixed in the latest version of
xfburn, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 955...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Unit 193  (supplier of updated xfburn package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA384

Format: 1.8
Date: Mon, 14 Aug 2023 22:59:00 -0400
Source: xfburn
Architecture: source
Version: 0.7.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Xfce Maintainers 
Changed-By: Unit 193 
Closes: 955855 1008999
Changes:
 xfburn (0.7.0-1) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Yves-Alexis Perez ]
   * d/control: drop b-dep on dbus-glib (Closes: #955855)
   * d/control: update Homepage (Closes: #1008999)
   * New upstream version 0.6.2
 .
   [ Debian Janitor ]
   * Bump debhelper from old 11 to 13.
   * Update standards version to 4.6.0, no changes needed.
   * Avoid explicitly specifying -Wl,--as-needed linker flag.
   * Remove constraints unnecessary since buster (oldstable)
 .
   [ Akbarkhon Variskhanov ]
   * Update upstream metadata
   * Bump watch version to 4
   * Install NEWS in debian/rules
   * Bump Standards-Version to 4.6.1
   * Fix lintian mismatched-override
   * Rules-Requires-Root: no
   * Delete debian/xfburn.1 & debian/xfburn.manpages
 .
   [ Unit 193 ]
   * New upstream version 0.7.0.
 - Drop patch applied upstream.
   * d/control: Drop unneeded B-D on autoconf, automake, and libtool.
   * d/rules: Opt-out of trimmed changelogs.
   * d/xfburn.docs: Follow rename, README → README.md.
   * Update Standards-Version to 4.6.2.
Checksums-Sha1:
 0f0ddf06368c694276ef2702b82b7e11f8ec0c71 2078 xfburn_0.7.0-1.dsc
 29dd0d946516cb53658f5dc8c5042904569db19f 923498 xfburn_0.7.0.orig.tar.bz2
 673c5fea774c0932c5ff7b55c7490fb328517885 4488 xfburn_0.7.0-1.debian.tar.xz
 78bf927a9b897a80b361356135b9cb2e20475d7e 16273 xfburn_0.7.0-1_amd64.buildinfo
Checksums-Sha256:
 92939578930b73bb5a31594a6c45168bbb11dd1c7a7b74543be777234a6762ac 2078 
xfburn_0.7.0-1.dsc
 ba960ea79a044b93e513f7c32bca1a599472d687ed0e0184bde8c84aeebb1f45 923498 
xfburn_0.7.0.orig.tar.bz2
 77a371e67a9eff41747721aec6202950cd957a69738f20f215c7a7994f5d36af 4488 
xfburn_0.7.0-1.debian.tar.xz
 c88204ca813ee9dfc6c7051722610e03f30f15d3ca2ae609cfe59a7abc26d863 16273 
xfburn_0.7.0-1_amd64.buildinfo
Files:
 4d84f0c364730e796f8f53df90225fa3 2078 xfce optional xfburn_0.7.0-1.dsc
 38d1e73e53c0fc4bb1bd286df1d91839 923498 xfce optional xfburn_0.7.0.orig.tar.bz2
 9d237788d26cedb18bbc243060fd8795 4488 xfce optional 
xfburn_0.7.0-1.debian.tar.xz
 6e3d6ab6f9cecf6119eadf9e05f32379 16273 xfce optional 
xfburn_0.7.0-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCQAdFiEEjbPlhoZdK0orGFpcUAHhsJqjdEsFAmTa7AQACgkQUAHhsJqj
dEvjZRAAzK6DugW909OFeq42rtXthpIoqIXG9mNkRjHGRNh7/sGbOkq1XXZT

Bug#1008999: marked as done (xfburn: Homepage moved)

2023-08-14 Thread Debian Bug Tracking System
Your message dated Tue, 15 Aug 2023 03:37:14 +
with message-id 
and subject line Bug#1008999: fixed in xfburn 0.7.0-1
has caused the Debian Bug report #1008999,
regarding xfburn: Homepage moved
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 ow...@bugs.debian.org
immediately.)


-- 
1008999: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008999
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xfburn
Severity: normal
Version: 0.6.2-1
X-Debbugs-CC: cor...@debian.org

Dear Debian xfburn package maintainer,

Currently the documented xfburn homepage information is defunct. The new
homepage is located at https://docs.xfce.org/apps/xfburn/start .

Such information change can be found at
https://gitlab.xfce.org/apps/xfburn/-/commit/400c9fdabe6310ef88896156fa3d25778291350e
. 

Thanks,
Boyuan Yang


signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Source: xfburn
Source-Version: 0.7.0-1
Done: Unit 193 

We believe that the bug you reported is fixed in the latest version of
xfburn, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1008...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Unit 193  (supplier of updated xfburn package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA384

Format: 1.8
Date: Mon, 14 Aug 2023 22:59:00 -0400
Source: xfburn
Architecture: source
Version: 0.7.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Xfce Maintainers 
Changed-By: Unit 193 
Closes: 955855 1008999
Changes:
 xfburn (0.7.0-1) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Yves-Alexis Perez ]
   * d/control: drop b-dep on dbus-glib (Closes: #955855)
   * d/control: update Homepage (Closes: #1008999)
   * New upstream version 0.6.2
 .
   [ Debian Janitor ]
   * Bump debhelper from old 11 to 13.
   * Update standards version to 4.6.0, no changes needed.
   * Avoid explicitly specifying -Wl,--as-needed linker flag.
   * Remove constraints unnecessary since buster (oldstable)
 .
   [ Akbarkhon Variskhanov ]
   * Update upstream metadata
   * Bump watch version to 4
   * Install NEWS in debian/rules
   * Bump Standards-Version to 4.6.1
   * Fix lintian mismatched-override
   * Rules-Requires-Root: no
   * Delete debian/xfburn.1 & debian/xfburn.manpages
 .
   [ Unit 193 ]
   * New upstream version 0.7.0.
 - Drop patch applied upstream.
   * d/control: Drop unneeded B-D on autoconf, automake, and libtool.
   * d/rules: Opt-out of trimmed changelogs.
   * d/xfburn.docs: Follow rename, README → README.md.
   * Update Standards-Version to 4.6.2.
Checksums-Sha1:
 0f0ddf06368c694276ef2702b82b7e11f8ec0c71 2078 xfburn_0.7.0-1.dsc
 29dd0d946516cb53658f5dc8c5042904569db19f 923498 xfburn_0.7.0.orig.tar.bz2
 673c5fea774c0932c5ff7b55c7490fb328517885 4488 xfburn_0.7.0-1.debian.tar.xz
 78bf927a9b897a80b361356135b9cb2e20475d7e 16273 xfburn_0.7.0-1_amd64.buildinfo
Checksums-Sha256:
 92939578930b73bb5a31594a6c45168bbb11dd1c7a7b74543be777234a6762ac 2078 
xfburn_0.7.0-1.dsc
 ba960ea79a044b93e513f7c32bca1a599472d687ed0e0184bde8c84aeebb1f45 923498 
xfburn_0.7.0.orig.tar.bz2
 77a371e67a9eff41747721aec6202950cd957a69738f20f215c7a7994f5d36af 4488 
xfburn_0.7.0-1.debian.tar.xz
 c88204ca813ee9dfc6c7051722610e03f30f15d3ca2ae609cfe59a7abc26d863 16273 
xfburn_0.7.0-1_amd64.buildinfo
Files:
 4d84f0c364730e796f8f53df90225fa3 2078 xfce optional xfburn_0.7.0-1.dsc
 38d1e73e53c0fc4bb1bd286df1d91839 923498 xfce optional xfburn_0.7.0.orig.tar.bz2
 9d237788d26cedb18bbc243060fd8795 4488 xfce optional 
xfburn_0.7.0-1.debian.tar.xz
 6e3d6ab6f9cecf6119eadf9e05f32379 16273 xfce optional 
xfburn_0.7.0-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCQAdFiEEjbPlhoZdK0orGFpcUAHhsJqjdEsFAmTa7AQACgkQUAHhsJqj
dEvjZRAAzK6DugW909OFeq42rtXthpIoqIXG9mNkRjHGRNh7/sGbOkq1XXZTEmwa
AO6ADHW4TLeU8BMAAimuXq7zpXULoZzLRdfZyA+OgBnIN2zDiaxkRY4Sc+gTorH/
yQoOj1L8Ar/YsmKqqeGqvaV0lWdI8q1vNCfMd3F55LMu8rOAGu26AtTrFiaND1XM
3I62s4gXG0I4hPzhuEL5oaKMQ645LLHWWdruJdAw91v0remdbVxsGxaEeMxwo0Kj
48Ra19H4cEU8So13EddggrCLqR25VE9OxBqp5WZ00UjfgH/ygcxYTIiEMYQ0YpwC
0RkSXsWbgJrXlAFxNvgztLXAYiBQihzN2zcSuCIQg98OjEX0Vxd6iU2KwefB

Bug#1008971: marked as done (xfburn: on page https://packages.debian.org/stretch/xfburn, link "Homepage" is dead)

2023-08-14 Thread Debian Bug Tracking System
Your message dated Tue, 15 Aug 2023 03:37:14 +
with message-id 
and subject line Bug#1008999: fixed in xfburn 0.7.0-1
has caused the Debian Bug report #1008999,
regarding xfburn: on page https://packages.debian.org/stretch/xfburn, link 
"Homepage" is dead
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 ow...@bugs.debian.org
immediately.)


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

Package: xfburn
Version: 0.6.2-1
Severity: minor

Dear Maintainer,

*** Reporter, please consider answering these questions, where 
appropriate ***


* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was the outcome of this action?
* What outcome did you expect instead?

*** End of the template - remove these template lines ***


-- System Information:
Debian Release: 11.3
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500,
'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.10.0-13-amd64 (SMP w/2 CPU threads)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not
set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages xfburn depends on:
ii libburn4 1.5.2-1
ii libc6 2.31-13+deb11u3
ii libexo-2-0 4.16.0-1
ii libgdk-pixbuf2.0-0 2.40.2-2
ii libglib2.0-0 2.66.8-1
ii libgstreamer-plugins-base1.0-0 1.18.4-2
ii libgstreamer1.0-0 1.18.4-2.1
ii libgtk-3-0 3.24.24-4+deb11u2
ii libgudev-1.0-0 234-1
ii libisofs6 1.5.2-1
ii libxfce4ui-2-0 4.16.0-1
ii libxfce4util7 4.16.0-1

xfburn recommends no packages.

xfburn suggests no packages.
--- End Message ---
--- Begin Message ---
Source: xfburn
Source-Version: 0.7.0-1
Done: Unit 193 

We believe that the bug you reported is fixed in the latest version of
xfburn, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1008...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Unit 193  (supplier of updated xfburn package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA384

Format: 1.8
Date: Mon, 14 Aug 2023 22:59:00 -0400
Source: xfburn
Architecture: source
Version: 0.7.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Xfce Maintainers 
Changed-By: Unit 193 
Closes: 955855 1008999
Changes:
 xfburn (0.7.0-1) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Yves-Alexis Perez ]
   * d/control: drop b-dep on dbus-glib (Closes: #955855)
   * d/control: update Homepage (Closes: #1008999)
   * New upstream version 0.6.2
 .
   [ Debian Janitor ]
   * Bump debhelper from old 11 to 13.
   * Update standards version to 4.6.0, no changes needed.
   * Avoid explicitly specifying -Wl,--as-needed linker flag.
   * Remove constraints unnecessary since buster (oldstable)
 .
   [ Akbarkhon Variskhanov ]
   * Update upstream metadata
   * Bump watch version to 4
   * Install NEWS in debian/rules
   * Bump Standards-Version to 4.6.1
   * Fix lintian mismatched-override
   * Rules-Requires-Root: no
   * Delete debian/xfburn.1 & debian/xfburn.manpages
 .
   [ Unit 193 ]
   * New upstream version 0.7.0.
 - Drop patch applied upstream.
   * d/control: Drop unneeded B-D on autoconf, automake, and libtool.
   * d/rules: Opt-out of trimmed changelogs.
   * d/xfburn.docs: Follow rename, README → README.md.
   * Update Standards-Version to 4.6.2.
Checksums-Sha1:
 0f0ddf06368c694276ef2702b82b7e11f8ec0c71 2078 xfburn_0.7.0-1.dsc
 29dd0d946516cb53658f5dc8c5042904569db19f 923498 xfburn_0.7.0.orig.tar.bz2
 673c5fea774c0932c5ff7b55c7490fb328517885 4488 xfburn_0.7.0-1.debian.tar.xz
 78bf927a9b897a80b361356135b9cb2e20475d7e 16273 xfburn_0.7.0-1_amd64.buildinfo
Checksums-Sha256:
 92939578930b73bb5a31594a6c45168bbb11dd1c7a7b74543be777234a6762ac 2078 
xfburn_0.7.0-1.dsc
 ba960ea79a044b93e513f7c32bca1a599472d687ed0e0184bde8c84aeebb1f45 923498 
xfburn_0.7.0.orig.tar.bz2
 77a371e67a9eff41747721aec6202950cd957a69738f20f215c7a7994f5d36af 4488 
xfburn_0.7.0-1.debian.tar.xz
 c88204ca813ee9dfc6c7051722610e03f30f15d3ca2ae609cfe59a7abc26d863 16273 
xfburn_0.7.0-1_amd64.b

Bug#1009342: marked as done (xfce4-panel-profiles: reproducible builds: demo tarballs include user, group and file mode of build user)

2023-08-14 Thread Debian Bug Tracking System
Your message dated Tue, 15 Aug 2023 01:49:35 +
with message-id 
and subject line Bug#1009342: fixed in xfce4-panel-profiles 1.0.14-1
has caused the Debian Bug report #1009342,
regarding xfce4-panel-profiles: reproducible builds: demo tarballs include 
user, group and file mode of build user
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 ow...@bugs.debian.org
immediately.)


-- 
1009342: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009342
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xfce4-panel-profiles
Severity: normal
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: umask username
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Several of the tarballs shipped in
/usr/share/xfce4-panel-profiles/layouts/ embed the username, userid,
groupname, groupid and umask of the build user:

  
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/diffoscope-results/xfce4-panel-profiles.html

  /usr/share/xfce4-panel-profiles/layouts/Cupertino.tar.bz2

  
-rw-r--r--···0·pbuilder1··()·pbuilder1··()·4925·2021-02-21·22:44:32.00·config.txt
  vs.
  
-rw-rw-r--···0·pbuilder2··()·pbuilder2··()·4925·2021-02-21·22:44:32.00·config.txt


The attached patch fixes this by passing arguments to tar in
Makefile.in.in to ensure consistent user, group, uid, gid and file
permissions in the generated tarballs.


I have not verified that these changes work correctly in the resulting
packages, only that it builds reproducibly; please be sure to verify
before uploading.


With this patch applied, xfce4-panel-profiles should become reproducible
on tests.reproducible-builds.org!


Thanks for maintaining xfce4-panel-profiles!


live well,
  vagrant
From 8cf9f8941c20e1527ac73829687c0ea5f2f4b608 Mon Sep 17 00:00:00 2001
From: Vagrant Cascadian 
Date: Tue, 12 Apr 2022 01:28:32 +
Subject: [PATCH 1/3] Makefile.in.in: Pass arguments to tar to make build
 reproducible regardless of user or umask.

https://reproducible-builds.org/docs/archives/

---
 Makefile.in.in | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/Makefile.in.in b/Makefile.in.in
index a34e177..180da38 100644
--- a/Makefile.in.in
+++ b/Makefile.in.in
@@ -31,6 +31,8 @@ pot:
 
 ifeq ($(shell tar --help|grep -o sort=),sort=)
   TAROPTS := --sort=name --format ustar
+  TAROPTS += --owner=0 --group=0 --numeric-owner
+  TAROPTS += --mode=u=wrX,og=
 endif
 layouts:
 	cd data/layouts/cupertino; tar $(TAROPTS) -cvjf "../Cupertino.tar.bz2" *
-- 
2.30.2



signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: xfce4-panel-profiles
Source-Version: 1.0.14-1
Done: Unit 193 

We believe that the bug you reported is fixed in the latest version of
xfce4-panel-profiles, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1009...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Unit 193  (supplier of updated xfce4-panel-profiles package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA384

Format: 1.8
Date: Mon, 14 Aug 2023 21:14:12 -0400
Source: xfce4-panel-profiles
Architecture: source
Version: 1.0.14-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Xfce Maintainers 
Changed-By: Unit 193 
Closes: 1009342 1009812
Changes:
 xfce4-panel-profiles (1.0.14-1) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Akbarkhon Variskhanov ]
   * Add upstream metadata and bump Standards-Version
 .
   [ Unit 193 ]
   * d/gbp.conf: Add for xfce-team standard layout.
   * New upstream version 1.0.14.
 - Makefile.in.in: Pass arguments to tar to make build reproducible
   regardless of user or umask. (Closes: #1009342)
 - Save and restore rc-files. (Closes: #1009812)
   * d/rules: Opt-out of trimmed changelogs, install NEWS as changelog.
   * d/control: Update 'homepage' field.
   * d/copyright: Update years.
   * Update Standards-Version to 4.6.2.
Checksums-Sha1:
 070761bf1acf803327dc3c78375f30da3f4f646b 2122 xfce4-panel-profiles_1.0.14-1.dsc
 606c293ded2edd8a06a596480b7a2ae4c5a7b0d6 101521 
xfce4-panel-profiles_1.0.14.orig.tar.bz2
 c342a4cce0e1fa887439a844a19a753a3645b96a 8556 
xfce4-panel-profile

Bug#1009812: marked as done (xfce4-panel-profiles: Missing functionality. Save/export not possible.)

2023-08-14 Thread Debian Bug Tracking System
Your message dated Tue, 15 Aug 2023 01:49:35 +
with message-id 
and subject line Bug#1009812: fixed in xfce4-panel-profiles 1.0.14-1
has caused the Debian Bug report #1009812,
regarding xfce4-panel-profiles: Missing functionality. Save/export not possible.
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 ow...@bugs.debian.org
immediately.)


-- 
1009812: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009812
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xfce4-panel-profiles
Version: 1.0.13-1
Severity: important
X-Debbugs-Cc: mark.bran...@posteo.de


-- System Information:
Debian Release: bookworm/sid
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 
'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.16.0-6-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages xfce4-panel-profiles depends on:
ii  gir1.2-glib-2.01.72.0-1+b1
ii  gir1.2-gtk-3.0 3.24.33-1
ii  gir1.2-libxfce4ui-2.0  4.16.1-1
ii  python33.10.4-1

xfce4-panel-profiles recommends no packages.

xfce4-panel-profiles suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: xfce4-panel-profiles
Source-Version: 1.0.14-1
Done: Unit 193 

We believe that the bug you reported is fixed in the latest version of
xfce4-panel-profiles, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1009...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Unit 193  (supplier of updated xfce4-panel-profiles package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA384

Format: 1.8
Date: Mon, 14 Aug 2023 21:14:12 -0400
Source: xfce4-panel-profiles
Architecture: source
Version: 1.0.14-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Xfce Maintainers 
Changed-By: Unit 193 
Closes: 1009342 1009812
Changes:
 xfce4-panel-profiles (1.0.14-1) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Akbarkhon Variskhanov ]
   * Add upstream metadata and bump Standards-Version
 .
   [ Unit 193 ]
   * d/gbp.conf: Add for xfce-team standard layout.
   * New upstream version 1.0.14.
 - Makefile.in.in: Pass arguments to tar to make build reproducible
   regardless of user or umask. (Closes: #1009342)
 - Save and restore rc-files. (Closes: #1009812)
   * d/rules: Opt-out of trimmed changelogs, install NEWS as changelog.
   * d/control: Update 'homepage' field.
   * d/copyright: Update years.
   * Update Standards-Version to 4.6.2.
Checksums-Sha1:
 070761bf1acf803327dc3c78375f30da3f4f646b 2122 xfce4-panel-profiles_1.0.14-1.dsc
 606c293ded2edd8a06a596480b7a2ae4c5a7b0d6 101521 
xfce4-panel-profiles_1.0.14.orig.tar.bz2
 c342a4cce0e1fa887439a844a19a753a3645b96a 8556 
xfce4-panel-profiles_1.0.14-1.debian.tar.xz
 8e6c4338f62640a99540601beafd9dd64b379604 7280 
xfce4-panel-profiles_1.0.14-1_amd64.buildinfo
Checksums-Sha256:
 9cd2a6ddcf1a0a1bcb63aba30dedaca0c12e5b0ac91d1adf09186c736ff94f05 2122 
xfce4-panel-profiles_1.0.14-1.dsc
 6d08354e8c44d4b0370150809c1ed601d09c8b488b68986477260609a78be3f9 101521 
xfce4-panel-profiles_1.0.14.orig.tar.bz2
 de4bf4f174e487a014ac28682a6a59afb63b5d1c9a249ed026cd5443777ff3b8 8556 
xfce4-panel-profiles_1.0.14-1.debian.tar.xz
 5971290f483c702651bbbe19eecedf472737e015d676bd6cd3a00f68cef1c752 7280 
xfce4-panel-profiles_1.0.14-1_amd64.buildinfo
Files:
 798942827213003b91e9539e63a0 2122 xfce optional 
xfce4-panel-profiles_1.0.14-1.dsc
 c1d6c291469fb251af853171607450a9 101521 xfce optional 
xfce4-panel-profiles_1.0.14.orig.tar.bz2
 35a7b6c0dca88379d312ab765a111b85 8556 xfce optional 
xfce4-panel-profiles_1.0.14-1.debian.tar.xz
 104f706124c2bc870322c627ff6f3803 7280 xfce optional 
xfce4-panel-profiles_1.0.14-1_amd64.buildinfo

-BEGIN PGP SIGNATURE

Bug#968808: marked as done (lightdm: Please package new upstream release (1.30.0))

2023-08-03 Thread Debian Bug Tracking System
Your message dated Thu, 03 Aug 2023 20:19:46 -0400
with message-id <05d1fda1034af2396dffae1022dc317b15f51743.ca...@debian.org>
and subject line Re: lightdm: Please package new upstream release (1.30.0)
has caused the Debian Bug report #968808,
regarding lightdm: Please package new upstream release (1.30.0)
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 ow...@bugs.debian.org
immediately.)


-- 
968808: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968808
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: lightdm
Version: 1.26.0-7
Tags: sid
X-Debbugs-CC: cor...@debian.org

Dear Debian lightdm maintainers,

It seems that Debian's lightdm is stuck in v1.26. According to lightdm
upstream at https://github.com/canonical/lightdm/releases , the new
v1.30.0 has been available since 2019. Please package the new release.

According to 
https://sources.debian.org/src/lightdm/1.26.0-7/debian/watch/ , the
debian/watch file explicitly embedded the 1.26 string in the version
string, which doesn't make much sense. Please fix this version watching
scheme as well. I believe it is not Debian's intention to only monitor
the 1.26.x series.

Thanks,
Boyuan Yang


signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Version: 1.32.0-3

On Mon, 14 Nov 2022 13:27:12 +0500 Akbarkhon Variskhanov
 wrote:
> Control: tags -1 wontfix
> 
> As it was discussed on Salsa[1], there's no point in releasing 1.30.0
> as it's EoL already. We'll most likely skip it and package 1.32.0
> instead. Also, see[2]
> 
> [1] https://salsa.debian.org/xfce-extras-team/lightdm/-/merge_requests/7
> [2] https://discourse.ubuntu.com/t/current-status-of-lightdm/29048/12?u=kbar

Closing as lightdm 1.32 is packaged.

Thanks,
Boyuan Yang


signature.asc
Description: This is a digitally signed message part
--- End Message ---


Processed: parole: depends on unmaintained clutter-1.0

2023-07-21 Thread Debian Bug Tracking System
Processing control commands:

> block 996690 by -1
Bug #996690 [src:clutter-1.0] clutter-1.0: upstream project discontinued, 
should be removed
Bug #1018109 [src:clutter-1.0] clutter-1.0: unmaintained upstream, should 
eventually be removed
996690 was blocked by: 1018121 1018132 1018123 1041623 1018126 1018137 1018119 
1018112 1018116 1018113 1018129 1018136 1018133 1018127 1018111 1018124 1018120 
1041624 1041620 1018115 1018128 1018135 1018130 1018114 1018138 1041625 1018125
996690 was blocking: 996691
Added blocking bug(s) of 996690: 1041626
1018109 was blocked by: 1018121 1018132 1018123 1041623 1018126 1018137 1018119 
1018112 1018116 1018113 1018129 1018136 1018133 1018127 1018111 1018124 1018120 
1041624 1041620 1018115 1018128 1018135 1018130 1018114 1018138 1041625 1018125
1018109 was blocking: 996691
Added blocking bug(s) of 1018109: 1041626

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



Bug#1021962: marked as done (xfce4-notes-plugin: Missing from sid, testing and stable since before bullseye was even released)

2023-07-20 Thread Debian Bug Tracking System
Your message dated Thu, 20 Jul 2023 17:25:47 +
with message-id 
and subject line Bug#1021962: fixed in xfce4-notes-plugin 1.10.0-1
has caused the Debian Bug report #1021962,
regarding xfce4-notes-plugin: Missing from sid, testing and stable since before 
bullseye was even released
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 ow...@bugs.debian.org
immediately.)


-- 
1021962: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021962
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xfce4-goodies
Version: 4.14.0
Severity: important
X-Debbugs-Cc: rakirc...@gmail.com

Dear Maintainer,

I justed wanted to add "Notes plugin (xfce4-notes-plugin)" to my latest Debian 
11.5 installation, but the "add new items" to the Panel did not include
the Notes plugin.  Therefore, I tried downloading (from the web) the 
"xfce4-notes-plugin_1.8.1-1_amd64.deb" package and install it that way, but 
could
not find it anywhere to download it.  Now, I am hoping for a reply from this 
bugreport to get this bug fixed, or at least I am expecting a URL that 
will allow me to download and install to get the Notes plugin working.  Thanks 
for any help.


-- System Information:
Debian Release: 11.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-18-amd64 (SMP w/8 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages xfce4-goodies depends on:
ii  mousepad 0.5.2-1
ii  notification-daemon  3.20.0-4
ii  ristretto0.10.0-1
ii  thunar-archive-plugin0.4.0-2
ii  thunar-media-tags-plugin 0.3.0-2
ii  xfburn   0.6.2-1
ii  xfce4-battery-plugin 1.1.3-1
ii  xfce4-clipman-plugin 2:1.6.1-1
ii  xfce4-cpufreq-plugin 1.2.4-1
ii  xfce4-cpugraph-plugin1.2.1-1
ii  xfce4-datetime-plugin0.8.1-1
ii  xfce4-dict   0.8.4-1
ii  xfce4-diskperf-plugin2.6.3-1
ii  xfce4-fsguard-plugin 1.1.2-1
ii  xfce4-genmon-plugin  4.1.1-1
ii  xfce4-mailwatch-plugin   1.3.0-1
ii  xfce4-netload-plugin 1.3.2-1
ii  xfce4-notifyd [notification-daemon]  0.6.2-1
ii  xfce4-places-plugin  1.8.1-1
ii  xfce4-screenshooter  1.9.8-1
ii  xfce4-sensors-plugin 1.3.0-3
ii  xfce4-smartbookmark-plugin   0.5.2-1
ii  xfce4-systemload-plugin  1.2.4-1
ii  xfce4-taskmanager1.4.0-1
ii  xfce4-terminal   0.8.10-1
ii  xfce4-timer-plugin   1.7.1-1
ii  xfce4-verve-plugin   2.0.1-1
ii  xfce4-wavelan-plugin 0.6.2-1
ii  xfce4-weather-plugin 0.11.0-1
ii  xfce4-whiskermenu-plugin 2.5.3-1
ii  xfce4-xkb-plugin 1:0.8.2-1

Versions of packages xfce4-goodies recommends:
ii  xfce4-power-manager  4.16.0-1

Versions of packages xfce4-goodies suggests:
pn  gigolo  
ii  parole  4.16.0-1
pn  xfce4-indicator-plugin  
pn  xfce4-mpc-plugin
pn  xfce4-notes-plugin  
pn  xfce4-radio-plugin  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: xfce4-notes-plugin
Source-Version: 1.10.0-1
Done: Yves-Alexis Perez 

We believe that the bug you reported is fixed in the latest version of
xfce4-notes-plugin, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1021...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Yves-Alexis Perez  (supplier of updated xfce4-notes-plugin 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 18 Jul 2023 21:19:11 +0200
Source: xfce4-notes-plugin
Architecture: source
Version: 1.10.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Xfce Mainta

Processed (with 1 error): Re: Bug#1037020: xfce4-panel: workspace switcher extremely wide after bookworm upgrade

2023-07-18 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 unreproducible morinfo
Unknown tag/s: morinfo.
Recognized are: patch wontfix moreinfo unreproducible help security upstream 
pending confirmed ipv6 lfs d-i l10n newcomer a11y ftbfs fixed-upstream fixed 
fixed-in-experimental sid experimental potato woody sarge sarge-ignore etch 
etch-ignore lenny lenny-ignore squeeze squeeze-ignore wheezy wheezy-ignore 
jessie jessie-ignore stretch stretch-ignore buster buster-ignore bullseye 
bullseye-ignore bookworm bookworm-ignore trixie trixie-ignore forky 
forky-ignore.

Bug #1037020 [xfce4-panel] xfce4-panel: workspace switcher extremely wide after 
bookworm upgrade
Added tag(s) unreproducible.

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



Processed: Re: Bug#1041353: xfce4: option to make week start on Monday not Sunday

2023-07-18 Thread Debian Bug Tracking System
Processing control commands:

> reassign -1 xfce4-panel
Bug #1041353 [xfce4] xfce4: option to make week start on Monday not Sunday
Bug reassigned from package 'xfce4' to 'xfce4-panel'.
Ignoring request to alter found versions of bug #1041353 to the same values 
previously set
Ignoring request to alter fixed versions of bug #1041353 to the same values 
previously set

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



Bug#999926: marked as done (xfce4-verve-plugin: depends on obsolete pcre3 library)

2023-07-16 Thread Debian Bug Tracking System
Your message dated Sun, 16 Jul 2023 12:51:14 +
with message-id 
and subject line Bug#26: fixed in xfce4-verve-plugin 2.0.3-1
has caused the Debian Bug report #26,
regarding xfce4-verve-plugin: depends on obsolete pcre3 library
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 ow...@bugs.debian.org
immediately.)


-- 
26: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=26
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xfce4-verve-plugin
Severity: important
User: matthew-pcre...@debian.org
Usertags: obsolete-pcre3

Dear maintainer,

Your package still depends on the old, obsolete PCRE3[0] libraries
(i.e. libpcre3-dev). This has been end of life for a while now, and
upstream do not intend to fix any further bugs in it. Accordingly, I
would like to remove the pcre3 libraries from Debian, preferably in
time for the release of Bookworm.

The newer PCRE2 library was first released in 2015, and has been in
Debian since stretch. Upstream's documentation for PCRE2 is available
here: https://pcre.org/current/doc/html/

Many large projects that use PCRE have made the switch now (e.g. git,
php); it does involve some work, but we are now at the stage where
PCRE3 should not be used, particularly if it might ever be exposed to
untrusted input.

This mass bug filing was discussed on debian-devel@ in
https://lists.debian.org/debian-devel/2021/11/msg00176.html

Regards,

Matthew [0] Historical reasons mean that old PCRE is packaged as
pcre3 in Debian 
--- End Message ---
--- Begin Message ---
Source: xfce4-verve-plugin
Source-Version: 2.0.3-1
Done: Yves-Alexis Perez 

We believe that the bug you reported is fixed in the latest version of
xfce4-verve-plugin, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 999...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Yves-Alexis Perez  (supplier of updated xfce4-verve-plugin 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 16 Jul 2023 14:02:45 +0200
Source: xfce4-verve-plugin
Architecture: source
Version: 2.0.3-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Xfce Maintainers 
Changed-By: Yves-Alexis Perez 
Closes: 26
Changes:
 xfce4-verve-plugin (2.0.3-1) unstable; urgency=medium
 .
   * d/control: build against libpcre2 (Closes: #26)
   * New upstream version 2.0.3
   * d/control: update standards version to 4.6.2
Checksums-Sha1:
 213c7068fb4b157c6f5fd6c8fa6f7ba7170d9f9d 1799 xfce4-verve-plugin_2.0.3-1.dsc
 6d1f94c903a173c68d37f25618a37cf624f6b7e2 383536 
xfce4-verve-plugin_2.0.3.orig.tar.bz2
 6f8327d0a16def8a9f61be6dc8496b81fbbde572 3380 
xfce4-verve-plugin_2.0.3-1.debian.tar.xz
 c054671e346ca21b9e90a1b9252e2fd0078cb431 15680 
xfce4-verve-plugin_2.0.3-1_amd64.buildinfo
Checksums-Sha256:
 dd0699a5ecde084a0992d91faa11f01e28261ee291cf4ccbe84a3809d966d21b 1799 
xfce4-verve-plugin_2.0.3-1.dsc
 e1bf121f1bf9cf2a199bf5c0f3aa802f503df9bea50724741e7a92fe6d9fe09e 383536 
xfce4-verve-plugin_2.0.3.orig.tar.bz2
 5f4449c2cc9078797f03688454284ce020e06e997959b6e30de05050fdd661ba 3380 
xfce4-verve-plugin_2.0.3-1.debian.tar.xz
 4a754bde6194a57df0b9d0c57bdecfe56675d1991bc2975a19ea7b85da9f5e36 15680 
xfce4-verve-plugin_2.0.3-1_amd64.buildinfo
Files:
 ed3d0a41596b0c63ee4eeff6f14eb122 1799 xfce optional 
xfce4-verve-plugin_2.0.3-1.dsc
 7dac12f16b09031c985fe71e4e599377 383536 xfce optional 
xfce4-verve-plugin_2.0.3.orig.tar.bz2
 ebd0598dc841aa0a9c940533563cf6f6 3380 xfce optional 
xfce4-verve-plugin_2.0.3-1.debian.tar.xz
 b65dadbe734057bc7bc5d316533a6d84 15680 xfce optional 
xfce4-verve-plugin_2.0.3-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmSz3r8ACgkQ3rYcyPpX
RFurxQf/YA+z2aLqXZPeU+LywYDlxX0tqyEKa/i05CY8xSS2GwZORu+xbLyElCH5
28kYDGk9BIkMMYlkkuhyMqihFUZWulpkZVnGlcW5tNbzQAWoIvjonQep7FFdTMFo
dXDCN6G1WblEe5Kx/fzf6QZo5BxiqXGge+54nrKXwHjkjk1I/f6nqBGr8qpIPEkE
NammGpERV430x2sIZxAgnFwZKETiwxc47x/fz6yoYK6f8tLyMQ7OvQ8faGrG3ImN
tk0DHLH/Sz34KvyZeJsbSRHGiMva1gAmlNmoqn0P/wOQd9+q2z/EacvMVBv+eDgZ
tikPuUNwwW3QE7UtrKSViUBLRutgYg==
=Vuga
-END PGP SIGNATURE End Message ---


Processed: bug 1041048 is forwarded to https://gitlab.xfce.org/panel-plugins/xfce4-weather-plugin/-/issues/66

2023-07-14 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> forwarded 1041048 
> https://gitlab.xfce.org/panel-plugins/xfce4-weather-plugin/-/issues/66
Bug #1041048 [xfce4-weather-plugin] xfce4-weather-plugin: Met.no API is obsolete
Set Bug forwarded-to-address to 
'https://gitlab.xfce.org/panel-plugins/xfce4-weather-plugin/-/issues/66'.
> thanks
Stopping processing here.

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



Processed: Re: Bug#1040912: lightdm-gtk-greeter: greeter always uses Gnome (Standard) as default Xsession

2023-07-12 Thread Debian Bug Tracking System
Processing control commands:

> reassign -1 arctica-greeter
Bug #1040912 [lightdm-gtk-greeter] lightdm-gtk-greeter: greeter always uses 
Gnome (Standard) as default Xsession
Bug reassigned from package 'lightdm-gtk-greeter' to 'arctica-greeter'.
No longer marked as found in versions lightdm-gtk-greeter/2.0.8-2.
Ignoring request to alter fixed versions of bug #1040912 to the same values 
previously set

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



Processed: Re: Bug#1040912: lightdm-gtk-greeter: greeter always uses Gnome (Standard) as default Xsession

2023-07-12 Thread Debian Bug Tracking System
Processing control commands:

> tags -1 moreinfo
Bug #1040912 [lightdm-gtk-greeter] lightdm-gtk-greeter: greeter always uses 
Gnome (Standard) as default Xsession
Added tag(s) moreinfo.

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



Bug#910273: marked as done (xfce4-settings: xfce4-keyboard-settings spits critical messages every millisecond, filing up .xsession-errors)

2023-07-12 Thread Debian Bug Tracking System
Your message dated Wed, 12 Jul 2023 12:09:04 +0200
with message-id 
and subject line Re: Bug#910273: severity of 910273 is important
has caused the Debian Bug report #910273,
regarding xfce4-settings: xfce4-keyboard-settings spits critical messages every 
millisecond, filing up .xsession-errors
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 ow...@bugs.debian.org
immediately.)


-- 
910273: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910273
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xfce4-settings
Version: 4.12.4-1
Severity: normal

Dear Maintainer,

On a recently installed testing system, it happened that the home
partition of the user got filled up very quickly, by a 267 G
.xsession-errors file.

Looking at the content, it seems that every millisecond, a dozen error
messages are spit by xfce4-keyboard-settings, looking like :

(xfce4-keyboard-settings:1593): libxfce4ui-CRITICAL **: 08:31:41.803: 
IA__xfce_dialog_show_error: assertion 'parent == NULL || GTK_IS_WINDOW 
(parent)' failed

(xfce4-keyboard-settings:1593): GLib-GObject-WARNING **: 08:31:41.803: invalid 
unclassed pointer in cast to 'GtkDialog'

(xfce4-keyboard-settings:1593): Gtk-CRITICAL **: 08:31:41.803: 
IA__gtk_dialog_run: assertion 'GTK_IS_DIALOG (dialog)' failed

I fear this is quite nasty, but didn't raise severity because it may
just be happening due to local peculiarities.

Thanks in advance.

Best regards,

-- 
Olivier BERGER 
http://www-public.telecom-sudparis.eu/~berger_o/ - OpenPGP-Id: 2048R/5819D7E8
Ingenieur Recherche - Dept INF
Institut Mines-Telecom, Telecom SudParis, Evry (France)
--- End Message ---
--- Begin Message ---
On Tue, Jul 11, 2023 at 04:21:16PM +0200, Olivier Berger wrote:
> Hi.
> 
> Ouch, I had lst track myself of this issue. Obviously it kinda solved
> itself in between (or I have a disk filling-up unnoticed ;-).
> 
> I guess we can probably close now (Oh, I don't remember how to close
> properly in the BTS when no longer applicable :-/).

I'm doing that now. I don't have the relevant version in case it exists
so I'm just closing.

Regards,
-- 
Yves-Alexis Perez--- End Message ---


Bug#919348: marked as done (xfce4-screensaver: Accidental upload to unstable while fixing bug #919151)

2023-07-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Jul 2023 11:21:00 +0200
with message-id 
and subject line Re: Bug#919348: many new releases since -- still "too buggy"?
has caused the Debian Bug report #919348,
regarding xfce4-screensaver: Accidental upload to unstable while fixing bug 
#919151
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 ow...@bugs.debian.org
immediately.)


-- 
919348: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919348
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xfce4-screensaver
Version: 0.1.3-1
Severity: important

While fixing #919151, I uploaded this package to unstable when
it was meant to go to experimental.

This package is still beta and security-wise, we don't consider
it quite ready yet to support in a stable release.

So we're filing an RC bug to prevent it from migrating to testing,
this can be closed once buster is frozen.

-- 
  ⢀⣴⠾⠻⢶⣦⠀  Jonathan Carter (highvoltage) 
  ⣾⠁⢠⠒⠀⣿⡁  Debian Developer - https://wiki.debian.org/highvoltage
  ⢿⡄⠘⠷⠚⠋   https://debian.org | https://jonathancarter.org
  ⠈⠳⣄  Be Bold. Be brave. Debian has got your back.
--- End Message ---
--- Begin Message ---
On Thu, Feb 04, 2021 at 07:59:33PM +0100, Yves-Alexis Perez wrote:
> On Thu, 2021-02-04 at 14:43 +0200, Adrian Bunk wrote:
> > Yves-Alexis, do you have any objections to closing this bug now?
> 
> Yes. I have xfce4-screensaver (4.16) running on a Debian sid install and it
> still happens every once in a while that the desktop of the locked box appears
> (for example at resume). I'm still not confident it should actually be used on
> a production install it's just not robust enough, but I don't have the time or
> motivation to investigate and fix it myself.

Now that we are at 4.18.2 and at the beginning of the Trixie release
cycle, and after a quick chat with Unit193, we decided to close this bug
and let xfce4-screensaver migrate to testing so it gets a little bit
more exposure.

It'd be really helpful if people could report all bugs they identify
(whether by using it or looking at the code), especially security-wise
(crashes leaving the desktop open, screen not blanking etc.)

We're not changing the default locker for Xfce for now.

Regards,
-- 
Yves-Alexis--- End Message ---


Bug#1036819: marked as done (xfce4-panel: Clock plugin is 1 second behind reality)

2023-07-04 Thread Debian Bug Tracking System
Your message dated Tue, 04 Jul 2023 21:31:03 +0200
with message-id <14f162d5844f84c86154c10f3fc110a8e91baa08.ca...@debian.org>
and subject line Re: Bug#1036819: xfce4-panel: Clock plugin is 1 second behind 
reality
has caused the Debian Bug report #1036819,
regarding xfce4-panel: Clock plugin is 1 second behind reality
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 ow...@bugs.debian.org
immediately.)


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

Package: xfce4-panel
Version: 4.18.2-1
Severity: normal

Dear Maintainer,

xfce4-panel's Clock plugin has a delay of 1 second.  A comparison with
"xclock -digital -update 1" confirms it.

   * What led up to the situation?
I simply set the Clock plugin to display seconds.  Xfce 4.16's DateTime 
plugin, as shipped with Bullseye, did not have this problem.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
Changing the plugin's settings did not fix the problem.
   * What was the outcome of this action?
The Clock plugin displays the time with a 1-second delay.
   * What outcome did you expect instead?
I expected the Clock plugin to display the time accurately without a delay.


-- System Information:
Debian Release: 12.0
  APT prefers testing-security
  APT policy: (500, 'testing-security'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-9-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE 
not set

Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages xfce4-panel depends on:
ii  exo-utils4.18.0-1
ii  libatk1.0-0  2.46.0-5
ii  libc62.36-9
ii  libcairo21.16.0-7
ii  libdbusmenu-gtk3-4   18.10.20180917~bzr492+repack1-3
ii  libexo-2-0   4.18.0-1
ii  libgarcon-1-04.18.0-1
ii  libgarcon-gtk3-1-0   4.18.0-1
ii  libgdk-pixbuf-2.0-0  2.42.10+dfsg-1+b1
ii  libglib2.0-0 2.74.6-2
ii  libgtk-3-0   3.24.37-2
ii  libpango-1.0-0   1.50.12+ds-1
ii  libpangocairo-1.0-0  1.50.12+ds-1
ii  libwnck-3-0  43.0-3
ii  libx11-6 2:1.8.4-2
ii  libxext6 2:1.3.4-1+b1
ii  libxfce4panel-2.0-4  4.18.2-1
ii  libxfce4ui-2-0   4.18.2-2
ii  libxfce4util74.18.1-2
ii  libxfconf-0-34.18.0-2

xfce4-panel recommends no packages.

xfce4-panel suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Fri, 2023-05-26 at 21:21 -0700, xoddf2 wrote:
> 
> xfce4-panel's Clock plugin has a delay of 1 second.  A comparison with
> "xclock -digital -update 1" confirms it.


Hi,

Up to one second difference on two displays with one second interval looks
totally normal to me: you don't know when the refresh is actually done in both
apps, it's likely not done in real time when the tick is executed. So if one
refresh at the start of the second and the other at the end, you likely have
at most one second difference.

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

iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmSkc3gACgkQ3rYcyPpX
RFtlkgf/TuHuW6QUrARZE6u/0/KYk1digAxU75JKs6s2sJ5Tnaec5vvbAUcOAUZf
etOSd+r6bapx26MStR1ZyysZou96HfwX9RAnaDR36eRf6Zn/gH2bgSC5LqOWYEx3
/vvNZrAWGBWOQnAf0qu6OsMSbM7+tNDyl/KrJIpiLChlQhfb0cVnTPmHqMkTHDkf
aB3ThPwkgMBtG0thdNfkwUwu1HV8T+8bU4YNo9ZZOLKTOTYyP46lZj7+3r/mfzEf
lh1dy8ucc0L2Yktn/sinzhjS6z429WyoHRITIGAjjTTTo+i/q2IMQ67CMVVtVUGt
vqtO526WS6GYXdCCyXZ6CL5VzBbKeQ==
=nCOF
-END PGP SIGNATURE End Message ---


Bug#1039559: marked as done (lightdm does not start Xorg)

2023-07-04 Thread Debian Bug Tracking System
Your message dated Tue, 4 Jul 2023 14:36:01 +0200
with message-id 
and subject line Re: Bug#1039559: lightdm does not start Xorg
has caused the Debian Bug report #1039559,
regarding lightdm does not start Xorg
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 ow...@bugs.debian.org
immediately.)


-- 
1039559: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039559
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lightdm
Version: 1.32.0-2
Severity: important
X-Debbugs-Cc: christophe.l...@cegetel.net

Dear Maintainer,

  After a debian update this morning, I'm facing an unexpected problem: lightdm 
does not start Xorg!
still the text console

Xorg seems to work well by iteslf (xinit, xterm, xeyes ...)
but lightdm does not launch it
and no greeter also

Suprisingly, there is no unusual error messages in lightdm.log
(note that there is no Xorg.0.log since Xorg is not launched)
Nothing remarkable in dmesg either

So, I'm lost. How to investigate this issue?

Best regards
Christophe


-- System Information:
Debian Release: trixie/sid
  APT prefers stable-security
  APT policy: (500, 'stable-security'), (500, 'proposed-updates'), (500, 
'oldstable-updates'), (500, 'oldoldstable-updates'), (500, 'oldoldstable'), 
(500, 'testing'), (500, 'stable'), (500, 'oldstable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.3.0-1-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages lightdm depends on:
ii  adduser3.134
ii  dbus   1.14.8-1
ii  debconf [debconf-2.0]  1.5.82
ii  libaudit1  1:3.0.9-1
ii  libc6  2.36-9
ii  libgcrypt201.10.2-2
ii  libglib2.0-0   2.74.6-2
ii  libpam-systemd [logind]252.11-1
ii  libpam0g   1.5.2-6
ii  libxcb11.15-1
ii  libxdmcp6  1:1.1.2-3
ii  lightdm-gtk-greeter [lightdm-greeter]  2.0.8-3

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

Versions of packages lightdm suggests:
ii  accountsservice  22.08.8-6
ii  upower   0.99.20-2
ii  xserver-xephyr   2:21.1.7-3

-- Configuration Files:
/etc/pam.d/lightdm changed:
auth  requisite pam_nologin.so
session  required pam_env.so readenv=1
session  required pam_env.so readenv=1 envfile=/etc/default/locale
@include common-auth
-auth  optional pam_gnome_keyring.so
@include common-account
session  [success=ok ignore=ignore module_unknown=ignore default=bad] 
pam_selinux.so close
session  requiredpam_limits.so
session  requiredpam_loginuid.so
@include common-session
session [success=ok ignore=ignore module_unknown=ignore default=bad] 
pam_selinux.so open
-session optionalpam_gnome_keyring.so auto_start
@include common-password
@include local-krb5


-- debconf information:
  lightdm/daemon_name: /usr/sbin/lightdm
* shared/default-x-display-manager: lightdm


-- lightdm.log
[+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log
[+0.00s] DEBUG: Starting Light Display Manager 1.32.0, UID=0 PID=4984
[+0.00s] DEBUG: Loading configuration dirs from 
/usr/share/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration from 
/usr/share/lightdm/lightdm.conf.d/01_debian.conf
[+0.00s] DEBUG: Loading configuration dirs from 
/usr/local/share/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration dirs from /etc/xdg/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration from 
/etc/lightdm/lightdm.conf.d/99-local.conf
[+0.00s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf
[+0.00s] DEBUG: Registered seat module local
[+0.00s] DEBUG: Registered seat module xremote
[+0.00s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager
[+0.00s] DEBUG: Using cross-namespace EXTERNAL authentication (this will 
deadlock if server is GDBus < 2.73.3)
[+0.00s] DEBUG: _g_io_module_get_default: Found default implementation local 
(GLocalVfs) for ‘gio-vfs’
[+0.00s] DEBUG: Monitoring logind for seats
[+0.00s] DEBUG: Acquired bus name org.freedesktop.DisplayManager
[+0.01s] DEBUG: Loading users from org.freedesktop.Accounts
[+0.01s] DEBUG: User /org/freedesktop/Accounts/User1000 added
[+0.01s] DEBUG: User /org/freedesktop/Accounts/User1001 added
[+0.02s] DEBUG: User /org/freedesk

Bug#1037996: marked as done (xfce4: xfce-Desktop will be crashed at start and than black Desktop)

2023-07-04 Thread Debian Bug Tracking System
Your message dated Tue, 4 Jul 2023 11:19:36 +0200
with message-id 
and subject line Re: Bug#1037996: xfce4: xfce-Desktop will be crashed at start 
and than black Desktop
has caused the Debian Bug report #1037996,
regarding xfce4: xfce-Desktop will be crashed at start and than black Desktop
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 ow...@bugs.debian.org
immediately.)


-- 
1037996: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037996
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xfce4
Version: 4.18
Severity: important
X-Debbugs-Cc: ch-hani...@t-online.de

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


-- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.3.7-1-siduction-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages xfce4 depends on:
ii  libxfce4ui-utils 4.18.4-1
ii  thunar   4.18.6-1
ii  xfce4-appfinder  4.18.0-1
ii  xfce4-panel  4.18.2-1
ii  xfce4-pulseaudio-plugin  0.4.5-1
ii  xfce4-session4.18.1-1
ii  xfce4-settings   4.18.2-1
ii  xfconf   4.18.1-1
ii  xfdesktop4   4.18.1-1
ii  xfwm44.18.0-1

Versions of packages xfce4 recommends:
pn  desktop-base  
ii  tango-icon-theme  0.8.90-11
pn  thunar-volman 
pn  xfce4-notifyd 
pn  xorg  

Versions of packages xfce4 suggests:
ii  xfce4-goodies4.18.0
pn  xfce4-power-manager  

-- no debconf information
--- End Message ---
--- Begin Message ---
On Thu, Jun 15, 2023 at 11:56:47AM +0200, Hanisch wrote:
> Package: xfce4
> Version: 4.18
> Severity: important
> X-Debbugs-Cc: ch-hani...@t-online.de
> 
> Dear Maintainer,
> 
> *** Reporter, please consider answering these questions, where appropriate ***
> 
>* What led up to the situation?
>* What exactly did you do (or not do) that was effective (or
>  ineffective)?
>* What was the outcome of this action?
>* What outcome did you expect instead?
> 
> *** End of the template - remove these template lines ***
> 
> 
> -- System Information:
> Debian Release: trixie/sid
>   APT prefers unstable
>   APT policy: (500, 'unstable')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 6.3.7-1-siduction-amd64 (SMP w/8 CPU threads; PREEMPT)

Hi,

could you please report the bug on the siduction tracking system? Or
please reproduce on plain, vanilla Debian before reopening this bug.

Regards,
-- 
Yves-Alexis Perez--- End Message ---


Bug#939970: marked as done (lightdm: Restart, Suspend, Hibernate, Shut Down all greyed out with elogind)

2023-07-03 Thread Debian Bug Tracking System
Your message dated Mon, 03 Jul 2023 21:58:49 +
with message-id 
and subject line Bug#932047: fixed in lightdm 1.32.0-3
has caused the Debian Bug report #932047,
regarding lightdm: Restart, Suspend, Hibernate, Shut Down all greyed out with 
elogind
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 ow...@bugs.debian.org
immediately.)


-- 
932047: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932047
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lightdm
Version: 1.26.0-5
Severity: important

I have a machine still using sysvinit, and systemd-shim has been
replaced by elogind for such machines. The dependencies have been
updated in lightdm 1.26.0-4. But after the upgrade (which did not
output any warning about a regression), Restart, Suspend, Hibernate,
Shut Down are now all greyed out.

-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 
'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.2.0-2-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=POSIX 
(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  adduser3.118
ii  dbus   1.12.16-1
ii  debconf [debconf-2.0]  1.5.73
ii  libaudit1  1:2.8.5-2
ii  libc6  2.29-1
ii  libgcrypt201.8.5-2
ii  libglib2.0-0   2.60.6-2
ii  libpam-elogind [logind]241.3-1+debian1
ii  libpam0g   1.3.1-5
ii  libxcb11.13.1-2
ii  libxdmcp6  1:1.1.2-3
ii  lightdm-gtk-greeter [lightdm-greeter]  2.0.6-1
ii  lsb-base   11.1.0

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

Versions of packages lightdm suggests:
pn  accountsservice  
ii  upower   0.99.11-1
ii  xserver-xephyr   2:1.20.4-1

-- Configuration Files:
/etc/lightdm/lightdm.conf changed:
[LightDM]
[Seat:*]
greeter-hide-users=false
[XDMCPServer]
[VNCServer]


-- debconf information:
  lightdm/daemon_name: /usr/sbin/lightdm
* shared/default-x-display-manager: lightdm
--- End Message ---
--- Begin Message ---
Source: lightdm
Source-Version: 1.32.0-3
Done: Yves-Alexis Perez 

We believe that the bug you reported is fixed in the latest version of
lightdm, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 932...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Yves-Alexis Perez  (supplier of updated lightdm package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 03 Jul 2023 22:48:54 +0200
Source: lightdm
Architecture: source
Version: 1.32.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Xfce Maintainers 
Changed-By: Yves-Alexis Perez 
Closes: 932047
Changes:
 lightdm (1.32.0-3) unstable; urgency=medium
 .
   * d/patches/05_debianize-pam-files: include common-session for greeter
 (Closes: #932047)
Checksums-Sha1:
 1dd84568ee68081f346fcbe9784ea7b1f5418c4a 2496 lightdm_1.32.0-3.dsc
 692a0c3efadac70ff3bddd78dae59cbc7820b085 38660 lightdm_1.32.0-3.debian.tar.xz
 4380a0e98cbadee0051645742f3bc1ec689e2fc3 19794 lightdm_1.32.0-3_amd64.buildinfo
Checksums-Sha256:
 126ed97d0d5e32ba3bea018e83c6a7a155e5a37a8b8bd493926589282b06f495 2496 
lightdm_1.32.0-3.dsc
 bc6f4121de92027a99bade218d6cb134bd70047a3efc3f00e3af70663f3a1b98 38660 
lightdm_1.32.0-3.debian.tar.xz
 1afa13acef4cf5f3d00f530a5da1515a08b3fe69090487b3a99b2fd0503c3650 19794 
lightdm_1.32.0-3_amd64.buildinfo
Files:
 36cfc3277790d2890107c5e0c241f47e 2496 x11 optional lightdm_1.32.0-3.dsc
 8cbcc12444ba4564f568f529f9cdd74b 38660 x11 optional 
lightdm_1.32.0-3.debian.tar.xz
 a65ff8ef8024fb1307acb9c4cca3d2ef 19794 x11 optional 
lightdm_1.32.0-3_amd64.buildinfo

-BEGIN PGP SIGNATURE

Bug#932047: marked as done (lightdm: greeter session support for elogind)

2023-07-03 Thread Debian Bug Tracking System
Your message dated Mon, 03 Jul 2023 21:58:49 +
with message-id 
and subject line Bug#932047: fixed in lightdm 1.32.0-3
has caused the Debian Bug report #932047,
regarding lightdm: greeter session support for elogind
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 ow...@bugs.debian.org
immediately.)


-- 
932047: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932047
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lightdm
Severity: normal
Tags: patch

Yves-Alexis,

Many thanks for updating lightdm's dependencies to use the new logind virtual
packages in closing #922160.

However, the necessary adjustments to the PAM configuration for lightdm-greeter
are still outstanding.

My testing indicates that in order for lightdm greeter's Suspend, Hibernate,
Restart and Shut Down buttons to be enabled, the greeter itself needs to
register a logind session.

For elogind based systems this could be implemented by adding

 session   optional pam_elogind.so

to /etc/pam.d/lightdm-greeter

Or, alternatively and perhaps better for the future, whichever logind
implementation is enabled through pam-auth could be used by sourcing the PAM
common-session.

Patches implementing both of these approaches are attached.

Many thanks,

Mark
1 file changed, 5 insertions(+)
debian/patches/05_debianize-pam-files.patch | 5 +

modified   debian/patches/05_debianize-pam-files.patch
@@ -60,6 +60,11 @@
  
  # Always let the greeter start without authentication
  auth  required pam_permit.so
+@@ -15,3 +16,4 @@
+ # Setup session
+ session   required pam_unix.so
+ session   optional pam_systemd.so
++session   optional pam_elogind.so
 --- a/data/pam/lightdm-autologin
 +++ b/data/pam/lightdm-autologin
 @@ -1,20 +1,37 @@

[back]
1 file changed, 7 insertions(+)
debian/patches/05_debianize-pam-files.patch | 7 +++

modified   debian/patches/05_debianize-pam-files.patch
@@ -60,6 +60,13 @@
  
  # Always let the greeter start without authentication
  auth  required pam_permit.so
+@@ -13,5 +14,4 @@
+ password  required pam_deny.so
+ 
+ # Setup session
+-session   required pam_unix.so
+-session   optional pam_systemd.so
++@include common-session
 --- a/data/pam/lightdm-autologin
 +++ b/data/pam/lightdm-autologin
 @@ -1,20 +1,37 @@

[back]
--- End Message ---
--- Begin Message ---
Source: lightdm
Source-Version: 1.32.0-3
Done: Yves-Alexis Perez 

We believe that the bug you reported is fixed in the latest version of
lightdm, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 932...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Yves-Alexis Perez  (supplier of updated lightdm package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 03 Jul 2023 22:48:54 +0200
Source: lightdm
Architecture: source
Version: 1.32.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Xfce Maintainers 
Changed-By: Yves-Alexis Perez 
Closes: 932047
Changes:
 lightdm (1.32.0-3) unstable; urgency=medium
 .
   * d/patches/05_debianize-pam-files: include common-session for greeter
 (Closes: #932047)
Checksums-Sha1:
 1dd84568ee68081f346fcbe9784ea7b1f5418c4a 2496 lightdm_1.32.0-3.dsc
 692a0c3efadac70ff3bddd78dae59cbc7820b085 38660 lightdm_1.32.0-3.debian.tar.xz
 4380a0e98cbadee0051645742f3bc1ec689e2fc3 19794 lightdm_1.32.0-3_amd64.buildinfo
Checksums-Sha256:
 126ed97d0d5e32ba3bea018e83c6a7a155e5a37a8b8bd493926589282b06f495 2496 
lightdm_1.32.0-3.dsc
 bc6f4121de92027a99bade218d6cb134bd70047a3efc3f00e3af70663f3a1b98 38660 
lightdm_1.32.0-3.debian.tar.xz
 1afa13acef4cf5f3d00f530a5da1515a08b3fe69090487b3a99b2fd0503c3650 19794 
lightdm_1.32.0-3_amd64.buildinfo
Files:
 36cfc3277790d2890107c5e0c241f47e 2496 x11 optional lightdm_1.32.0-3.dsc
 8cbcc12444ba4564f568f529f9cdd74b 38660 x11 optional 
lightdm_1.32.0-3.debian.tar.xz
 a65ff8ef8024fb1307acb9c4cca3d2ef 19794 x11 optional 
lightdm_1.32.0-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmSjPRcACgkQ3rYcyPpX
RFvuaggAknILOQNWco9bEbDhSfOO+7WY7qnz1GETa2fXi5ZkZTgphSFOH23IXNSq
LBLcjGIHsHHtfGuKtYgbqduEeUku3mu5mxsGEtl6aaOA3cdVWhECmcIZz+NvkigW
OhlGsMwTPg3IRK4t

Processed: found 1000003 in 2.1.2-1, tagging 1000003, found 999965 in 3.3.5+ds-10, tagging 999965 ...

2023-06-30 Thread Debian Bug Tracking System
port.cgi?bug=161
165: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=165
167: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=167
168: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=168
174: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=174
176: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=176
177: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=177
185: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=185
186: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=186
189: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=189
190: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=190
196: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=196
197: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=197
1000100: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000100
1000101: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000101
1000103: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000103
1000112: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000112
1000113: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000113
1000115: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000115
1000117: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000117
1000120: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000120
1000123: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000123
1000125: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000125
1000126: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000126
1000129: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000129
1000131: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000131
1000132: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000132
1000133: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000133
1000134: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000134
1035720: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035720
1036022: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036022
1036997: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036997
18: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=18
19: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=19
21: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=21
22: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=22
24: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=24
25: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=25
26: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=26
30: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=30
31: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=31
35: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=35
36: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=36
38: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=38
39: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=39
43: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=43
45: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=45
46: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=46
47: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=47
52: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=52
53: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=53
54: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=54
55: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=55
56: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=56
57: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=57
59: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=59
60: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=60
61: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=61
62: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=62
64: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=64
65: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=65
66: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=66
67: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=67
68: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=68
71: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=71
72: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=72
77: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=77
83: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=83
89: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=89
90: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=90
92: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=92
93: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=93
97: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=97
98: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=98
99: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=99
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#1039573: marked as done (cannot authenticate after lock: pam_unix(lightdm:auth): auth could not identify password)

2023-06-30 Thread Debian Bug Tracking System
Your message dated Fri, 30 Jun 2023 16:51:14 +0200
with message-id 
and subject line Re: Bug#1039573: cannot authenticate after lock: 
pam_unix(lightdm:auth): auth could not identify password
has caused the Debian Bug report #1039573,
regarding cannot authenticate after lock: pam_unix(lightdm:auth): auth could 
not identify password
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 ow...@bugs.debian.org
immediately.)


-- 
1039573: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039573
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lightdm
Version: 1.32.0-2
Severity: important

Hi there!

Thanks for your hard work with this package, it is really appreciated.

I just upgraded lightdm from 1.26.0-8 to 1.32.0-2 and now the greeter wont let 
me
login after a session lock (like a laptop suspend or CTRL+ALT+L on xfce4).

This can be found in the logs:

Jun 27 12:08:28 endurance lightdm[91911]: pam_unix(lightdm-greeter:session): 
session opened for user lightdm(uid=108) by (uid=0)
Jun 27 12:08:29 endurance lightdm[92079]: pam_unix(lightdm:auth): auth could 
not identify password for [arturo]
Jun 27 12:08:38 endurance lightdm[935]: Session pid=92114: Invalid string 
length 1869348864 from child
Jun 27 12:08:38 endurance lightdm[92114]: pam_nologin(lightdm:auth): unexpected 
response from failed conversation function
Jun 27 12:08:38 endurance lightdm[92114]: No user selected during authentication
Jun 27 12:08:38 endurance lightdm[92114]: pam_nologin(lightdm:auth): cannot 
determine user name

So I suspect there is a bug somewhere in the stack.

regards.


-- System Information:
Debian Release: trixie/sid
  APT prefers stable-security
  APT policy: (500, 'stable-security'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 6.3.0-1-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages lightdm depends on:
ii  adduser3.134
ii  dbus   1.14.8-1
ii  debconf [debconf-2.0]  1.5.82
ii  libaudit1  1:3.0.9-1
ii  libc6  2.36-9
ii  libgcrypt201.10.2-2
ii  libglib2.0-0   2.74.6-2
ii  libpam-systemd [logind]252.11-1
ii  libpam0g   1.5.2-6
ii  libxcb11.15-1
ii  libxdmcp6  1:1.1.2-3
ii  lightdm-gtk-greeter [lightdm-greeter]  2.0.8-3

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

Versions of packages lightdm suggests:
ii  accountsservice  22.08.8-6
ii  upower   0.99.20-2
pn  xserver-xephyr   

-- Configuration Files:
/etc/lightdm/lightdm.conf changed:
[LightDM]
[Seat:*]
greeter-hide-users=false
display-setup-script=sh -c "xrandr -s 1920x1080"
[XDMCPServer]
[VNCServer]


-- debconf information:
* shared/default-x-display-manager: lightdm
  lightdm/daemon_name: /usr/sbin/lightdm
--- End Message ---
--- Begin Message ---
On Wed, 28 Jun 2023 10:58:39 +0200 Arturo Borrero Gonzalez  
wrote:

Thanks for the follow up, I'll keep you updated in the next few days.


I have not experienced this problem again since the update.--- End Message ---


Processed: Marking PCRE3 use as RC for trixie

2023-06-29 Thread Debian Bug Tracking System
s://bugs.debian.org/cgi-bin/bugreport.cgi?bug=187
189: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=189
190: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=190
193: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=193
196: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=196
197: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=197
1000100: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000100
1000101: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000101
1000103: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000103
1000112: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000112
1000113: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000113
1000115: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000115
1000117: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000117
1000118: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000118
1000120: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000120
1000123: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000123
1000125: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000125
1000126: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000126
1000128: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000128
1000129: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000129
1000130: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000130
1000131: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000131
1000132: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000132
1000133: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000133
1000134: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000134
18: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=18
19: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=19
21: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=21
22: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=22
24: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=24
25: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=25
26: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=26
30: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=30
31: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=31
35: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=35
36: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=36
37: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=37
38: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=38
39: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=39
43: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=43
45: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=45
46: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=46
47: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=47
52: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=52
53: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=53
54: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=54
55: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=55
56: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=56
57: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=57
59: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=59
60: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=60
61: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=61
62: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=62
64: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=64
65: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=65
66: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=66
67: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=67
68: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=68
71: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=71
72: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=72
75: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=75
77: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=77
81: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=81
83: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=83
84: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=84
89: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=89
90: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999990
92: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=92
93: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=93
97: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=97
98: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=98
99: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=99
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Processed: Re: Bug#1038611: lightdm: Lightdm fails to start X after upgrade to 1.32.0

2023-06-23 Thread Debian Bug Tracking System
Processing control commands:

> severity -1 important
Bug #1038611 [lightdm] lightdm: Lightdm fails to start X after upgrade to 1.32.0
Severity set to 'important' from 'grave'
> retitle -1 lightdm 1.32 fails to start X on nvidia binary driver
Bug #1038611 [lightdm] lightdm: Lightdm fails to start X after upgrade to 1.32.0
Changed Bug title to 'lightdm 1.32 fails to start X on nvidia binary driver' 
from 'lightdm: Lightdm fails to start X after upgrade to 1.32.0'.

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



Processed: Re: Bug#1038701: lightdm logs "lightdm[1166]: gkr-pam: unable to locate daemon control file" error on boot

2023-06-20 Thread Debian Bug Tracking System
Processing control commands:

> forwarded -1 https://github.com/canonical/lightdm/issues/70
Bug #1038701 [lightdm] lightdm logs "lightdm[1166]: gkr-pam: unable to locate 
daemon control file" error on boot
Set Bug forwarded-to-address to 
'https://github.com/canonical/lightdm/issues/70'.

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



Bug#1037540: marked as done (Thunar (4.18.4-1) Segfaults If Using Tab Key While Using Split View)

2023-06-18 Thread Debian Bug Tracking System
Your message dated Sun, 18 Jun 2023 15:57:17 +0200
with message-id 
and subject line Re: Bug#1037540: Thunar (4.18.4-1) Segfaults If Using Tab Key 
While Using Split View
has caused the Debian Bug report #1037540,
regarding Thunar (4.18.4-1) Segfaults If Using Tab Key While Using Split View
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 ow...@bugs.debian.org
immediately.)


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

Package: thunar
Version: 4.18.4-1
Severity: grave

Hello, Thunar has been regularly crashing if using the current stable 
build with split view enabled.


To reproduce this issue, open a new Thunar instance, enable split view, 
and have one of the directories contain images, focus on the 
image-containing directory, and then press the Tab key multiple times 
until it crashes. Terminal output: https://pastebin.com/2mpdYyUb


This has been apparently fixed upstream with 4.18.5, but linking it here 
anyway for your information: 
https://gitlab.xfce.org/xfce/thunar/-/issues/1067


Thank you.
--- End Message ---
--- Begin Message ---
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Version: 4.18.6-1

On Tue, 2023-06-13 at 14:34 -0700, Fjords wrote:
> Package: thunar
> Version: 4.18.4-1
> Severity: grave
> 
> Hello, Thunar has been regularly crashing if using the current stable 
> build with split view enabled.
> 
> To reproduce this issue, open a new Thunar instance, enable split view, 
> and have one of the directories contain images, focus on the 
> image-containing directory, and then press the Tab key multiple times 
> until it crashes. Terminal output: https://pastebin.com/2mpdYyUb
> 
> This has been apparently fixed upstream with 4.18.5, but linking it here 
> anyway for your information: 
> https://gitlab.xfce.org/xfce/thunar/-/issues/1067
> 
I totally missed this, marking as fixed in the relevant version then.
- -- 
Yves-Alexis
-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmSPDT0ACgkQ3rYcyPpX
RFu+2ggAvyHmAuZSfbLZOMQYA5iqyDrGmrqmCccyJoCTgMdf38R2f1ViEZnr+wY9
siOFepUEWPUYp+Z+J3yhnyeLT1jq/1sXsSlmeBA0xqv+mJVYkBkj8l3rKwyEJwba
oD8X6PcUefGbtsrsLP8YS1lUshv/1QEIHPU3/NyFBBxH949UNRtfwrd9dLXKol+0
auA81giUaY2pf4zt892rnMDJOSmpREY21NIBDGUVEY/gZ+YQakSrsSeZjw0veijC
4x+gysC14/ed9Pk+Zyedx6LMWdzKweBPAycedcDRW2FIJoU1U/88Rhsur7Bv7/D3
OO2yc7ob5mzlSN5Hc9dIQSVulAVZnA==
=tyQt
-END PGP SIGNATURE End Message ---


Bug#1025583: marked as done (lightdm-gtk-greeter: recommends transitional policykit-1 package)

2023-06-18 Thread Debian Bug Tracking System
Your message dated Sun, 18 Jun 2023 10:11:57 +
with message-id 
and subject line Bug#1025583: fixed in lightdm-gtk-greeter 2.0.8-3
has caused the Debian Bug report #1025583,
regarding lightdm-gtk-greeter: recommends transitional policykit-1 package
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 ow...@bugs.debian.org
immediately.)


-- 
1025583: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025583
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lightdm-gtk-greeter
Version: 2.0.8-2
Severity: normal
User: pkg-utopia-maintain...@lists.alioth.debian.org
Usertags: policykit-1

This package has a Recommends on the transitional package policykit-1,
which has been separated into polkitd, pkexec and (deprecated)
polkitd-pkla packages.

If this package communicates with polkitd via D-Bus, please represent that
as a Depends, Recommends or Suggests on polkitd, whichever is appropriate
for the strength of the requirement.

If this package runs /usr/bin/pkexec, please represent that as a Depends,
Recommends or Suggests on pkexec, whichever is appropriate for the strength
of the requirement.

For packages that are expected to be backported to bullseye, it's OK to
use an alternative dependency: polkitd | policykit-1 and/or
pkexec | policykit-1.

This is part of a mass bug filing, see
<https://lists.debian.org/debian-devel/2022/10/msg00211.html>.

Thanks,
smcv
--- End Message ---
--- Begin Message ---
Source: lightdm-gtk-greeter
Source-Version: 2.0.8-3
Done: Yves-Alexis Perez 

We believe that the bug you reported is fixed in the latest version of
lightdm-gtk-greeter, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1025...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Yves-Alexis Perez  (supplier of updated lightdm-gtk-greeter 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 18 Jun 2023 11:28:23 +0200
Source: lightdm-gtk-greeter
Architecture: source
Version: 2.0.8-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Xfce Maintainers 
Changed-By: Yves-Alexis Perez 
Closes: 1025583
Changes:
 lightdm-gtk-greeter (2.0.8-3) unstable; urgency=medium
 .
   [ Unit 193 ]
   * d/copyright: Correct upstream name, lightdm → lightdm-gtk-greeter.
 .
   [ Debian Janitor ]
   * Bump debhelper from old 12 to 13.
   * Update renamed lintian tag names in lintian overrides.
   * Set upstream metadata fields: Contact.
   * Avoid explicitly specifying -Wl,--as-needed linker flag.
   * Set field Upstream-Contact in debian/copyright.
   * Remove obsolete field Contact from debian/upstream/metadata (already
 present in machine-readable debian/copyright).
   * Remove constraints unnecessary since buster
 .
   [ Akbarkhon Variskhanov ]
   * debian/control: Recommend polkitd or policykit-1 (Closes: #1025583)
   * debian/control: Update Homepage
   * Update upstream metadata
   * debian/copyright: Update Upstream-Contact & Source
 .
   [ Yves-Alexis Perez ]
   * d/watch updated for version 4
   * update lintian override context
   * d/control: update standards version to 4.6.2
Checksums-Sha1:
 8b6054b7bb3b551eb88839e997b3032a60adc517 2065 lightdm-gtk-greeter_2.0.8-3.dsc
 183fe5cf3e32e9f0ed9980817ab803f8a35b64ca 6548 
lightdm-gtk-greeter_2.0.8-3.debian.tar.xz
 b425e72e6eec0dc87bd6f0adb970a06e00941b4c 15639 
lightdm-gtk-greeter_2.0.8-3_amd64.buildinfo
Checksums-Sha256:
 77f2af4cc50530848dc4b9327f8ab4a7d300c40dac768f85866c8bf38e8678ad 2065 
lightdm-gtk-greeter_2.0.8-3.dsc
 9e234efeb1427a944d9947adf2554d731d3252d384a154eb4e7cf2157efedfe8 6548 
lightdm-gtk-greeter_2.0.8-3.debian.tar.xz
 fc5ffbfc4c555cfca7be37d786c1079856c3161ec154c1ea8a80fbc6460af6a8 15639 
lightdm-gtk-greeter_2.0.8-3_amd64.buildinfo
Files:
 ddfc6307379e9c8f12029123a7e5ec9f 2065 x11 optional 
lightdm-gtk-greeter_2.0.8-3.dsc
 20f1383740bc322246600e52b76e8181 6548 x11 optional 
lightdm-gtk-greeter_2.0.8-3.debian.tar.xz
 51ecadc08698871fc6c5a97456e7d85f 15639 x11 optional 
lightdm-gtk-greeter_2.0.8-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmSOzx0ACgkQ3rYcyPpX
RFuGHAf6ApZ8Ph5Vqg7rDFQEl3Y3MJ2M6ryMIUh+L0duvCKc4YbSOZ

Bug#995366: marked as done (xfce4-pulseaudio-plugin: repeatedly polls D-Bus names, should watch NameOwnerChanged instead)

2023-06-15 Thread Debian Bug Tracking System
Your message dated Thu, 15 Jun 2023 10:33:05 +
with message-id 
and subject line Bug#995366: fixed in xfce4-pulseaudio-plugin 0.4.7-1
has caused the Debian Bug report #995366,
regarding xfce4-pulseaudio-plugin: repeatedly polls D-Bus names, should watch 
NameOwnerChanged instead
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 ow...@bugs.debian.org
immediately.)


-- 
995366: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995366
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xfce4-pulseaudio-plugin
Version: 0.4.3-1
Severity: normal
Tags: upstream

While using debian-live-11.0.0-amd64-xfce.iso to try to reproduce an
unrelated issue, I noticed that the pulseaudio plugin for the panel
calls the ListNames() D-Bus method approximately once per second.
This causes the system to wake up unnecessarily, and is likely to be
a waste of electricity on an otherwise idle system. It also makes it
more difficult to debug the unrelated issue with dbus-monitor :-)

Looking at upstream source code, this seems to be because it calls
pulseaudio_mpris_tick_cb() once per second, which calls
pulseaudio_mpris_get_available_players(), which calls ListNames.

This shouldn't be necessary: D-Bus is designed to be completely idle (no
messages sent, no messages received, no wakeups) if nothing interesting
is happening, similar to other AF_UNIX-based protocols such as X11.

Workaround: remove the Pulseaudio plugin (the volume control) from the
panel while debugging D-Bus-related issues.

I tried to report this upstream, but so far I have been unable to set
up an account on XFCE's Gitlab (presumably the email confirmation has
been greylisted).

For protocols like MPRIS that use an equivalence class of names starting
with a prefix, the intended pattern since dbus-daemon 1.6.0 (stable
release in 2012) is this:

* Add a match rule for the NameOwnerChanged signal with
  arg0namespace="org.mpris.MediaPlayer2"
- in GDBus, this is something like:
g_dbus_connection_signal_subscribe (connection,
"org.freedesktop.DBus",
"org.freedesktop.DBus",
"NameOwnerChanged",
"/org/freedesktop/DBus",
"org.mpris.MediaPlayer2",

G_DBUS_SIGNAL_FLAGS_MATCH_ARG0_NAMESPACE,
name_owner_changed_cb, ...);

* When the signal is received, its arguments are the name, the old owner,
  and the new owner
- if the new owner is "", the name is disappearing from the bus:
  remove it from the list of MPRIS media players
- otherwise, the name is appearing on the bus: add it to the list of
  MPRIS media players

* After connecting to the signal, call ListNames *once* to populate the
  initial list of MPRIS media players

smcv
--- End Message ---
--- Begin Message ---
Source: xfce4-pulseaudio-plugin
Source-Version: 0.4.7-1
Done: Unit 193 

We believe that the bug you reported is fixed in the latest version of
xfce4-pulseaudio-plugin, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 995...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Unit 193  (supplier of updated xfce4-pulseaudio-plugin 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA384

Format: 1.8
Date: Thu, 15 Jun 2023 05:21:29 -0400
Source: xfce4-pulseaudio-plugin
Architecture: source
Version: 0.4.7-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Xfce Maintainers 
Changed-By: Unit 193 
Closes: 995366
Changes:
 xfce4-pulseaudio-plugin (0.4.7-1) unstable; urgency=medium
 .
   * New upstream version 0.4.7.
 - Subscribe NameOwnerChanged to watch MPRIS changes instead of timer.
   Closes: #995366
   * d/rules:
 - Use execute_after_auto_install instead of override_dh_auto_install.
   * d/docs, d/rules: Opt-out of trimmed changelogs, install NEWS as changelog.
   * Update Standards-Version to 4.6.2.
Checksums-Sha1:
 0902f937202d

Bug#1018717: marked as done (orage: Segmentation fault)

2023-06-15 Thread Debian Bug Tracking System
Your message dated Thu, 15 Jun 2023 06:49:45 +
with message-id 
and subject line Bug#1018717: fixed in orage 4.18.0-1
has caused the Debian Bug report #1018717,
regarding orage: Segmentation fault
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 ow...@bugs.debian.org
immediately.)


-- 
1018717: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018717
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: orage
Version: 4.16.0-1
Severity: grave
Justification: renders package unusable

Orage crashes at launch with segmentation fault.


-- System Information:
Debian Release: 11.4
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 
'stable'), (100, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.18.0-4-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages orage depends on:
ii  libc62.34-4
ii  libcairo21.16.0-6
ii  libgdk-pixbuf-2.0-0  2.42.9+dfsg-1
ii  libglib2.0-0 2.73.3-2
ii  libgtk-3-0   3.24.34-3
ii  libical3 3.0.9-2
ii  libnotify4   0.7.9-3
ii  libpango-1.0-0   1.50.9+ds-1
ii  libpangocairo-1.0-0  1.50.9+ds-1
ii  libx11-6 2:1.8.1-2
ii  libxfce4panel-2.0-4  4.16.2-1
ii  libxfce4ui-2-0   4.16.0-1
ii  libxfce4util74.16.0-1
ii  orage-data   4.16.0-1

Versions of packages orage recommends:
ii  dbus-user-session [default-dbus-session-bus]  1.12.20-2
ii  dbus-x11 [dbus-session-bus]   1.12.20-2

Versions of packages orage suggests:
pn  sox  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: orage
Source-Version: 4.18.0-1
Done: Unit 193 

We believe that the bug you reported is fixed in the latest version of
orage, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1018...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Unit 193  (supplier of updated orage package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA384

Format: 1.8
Date: Thu, 15 Jun 2023 02:31:16 -0400
Source: orage
Architecture: source
Version: 4.18.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Xfce Maintainers 
Changed-By: Unit 193 
Closes: 1018717
Changes:
 orage (4.18.0-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream version 4.18.0.
 - Added Wayland support. (Issue #2, Closes: #1018717)
 - Drop patch upstreamed.
   * d/control: Drop B-D on libdbus-glib-1-dev and libxfce4panel-2.0-dev.
   * d/orage.install: Panel plugin was removed, update accordingly.
   * Update Standards-Version to 4.6.2.
Checksums-Sha1:
 cc0150b014d82d6c48fbcd8533f9e9e95c1d2b32 2065 orage_4.18.0-1.dsc
 d346563413ec6a3aa45e93899279e226f0a3ecdf 1418645 orage_4.18.0.orig.tar.bz2
 5826c3b77886b15960babc76b9006040804b3717 14228 orage_4.18.0-1.debian.tar.xz
 6e70847a63885be4156a3629ba7c27f9ed584141 15759 orage_4.18.0-1_amd64.buildinfo
Checksums-Sha256:
 82d8be235ff7ba2f055cbb13793d9440b763bf371d238c1bd7577721e7101627 2065 
orage_4.18.0-1.dsc
 6313b49b26cfa39fc5e99468f3fbcfe0fa1c0f3f74273f03674f1a7d6141a3ec 1418645 
orage_4.18.0.orig.tar.bz2
 a71c45fb41419d1a5d49da1d7908de2e1a9dbf0e2c215a66ea0b4a2066c17ed3 14228 
orage_4.18.0-1.debian.tar.xz
 3fc8d05055be238dd828a1b2bdc84f1d841dd5fcf3b079b3d836681a9b3b03fb 15759 
orage_4.18.0-1_amd64.buildinfo
Files:
 38c3962cbee2eefa49387cbcba8c0268 2065 xfce optional orage_4.18.0-1.dsc
 c12765da61022c710bb0d5aab3c9c56f 1418645 xfce optional 
orage_4.18.0.orig.tar.bz2
 89567d48de612ca92991f34f37ecbedd 14228 xfce optional 
orage_4.18.0-1.debian.tar.xz
 1750744a8ce5d421fe6e2c41c47a87c4 15759 xfce optional 
orage_4.18.0-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCQAdFiEEjbPlhoZdK0orGFpcUAHhsJqjdEsFAmSKsZQACgkQUAHhsJqj
dEtLCRAAxBuJflX3nh5NJZJXpBWGT3AtPqHmKhIfbFycM/LLnosxarUcszy3/6YS
jHnyGV+CLQpA8tghwAlAbYNblVPEhve50cSm4kMrH7W4gSPlzhK6f1QBfwuiyV+U
EAQBUbei/uKVv7yQxHPMnGxW3ZwRS+mBtHPwV4KCF50muIwhvSSr75Xd5yuOl9Fc

Bug#840599: marked as done (xfce4-notifyd: Noisy help for xfce4-notifyd-config in Spanish)

2023-06-14 Thread Debian Bug Tracking System
Your message dated Wed, 14 Jun 2023 14:22:58 +0200
with message-id 

and subject line xfce4-notifyd: bug #840599 fixed in 0.4.4-1
has caused the Debian Bug report #840599,
regarding xfce4-notifyd: Noisy help for xfce4-notifyd-config in Spanish
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 ow...@bugs.debian.org
immediately.)


-- 
840599: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840599
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xfce4-notifyd
Version: 0.3.3-1
Severity: minor
Tags: l10n

Dear Maintainer,

'xfce4-notifyd-config --help' shows some additional useless lines when
the Spanish language is used:

$ xfce4-notifyd-config --help
Uso:
  xfce4-notifyd-config [OPCIÓN…] Project-Id-Version: Xfce Apps
Report-Msgid-Bugs-To: 
POT-Creation-Date: 2016-06-30 00:31+0200
PO-Revision-Date: 2016-08-15 16:41+
Last-Translator: Pablo Roberto “Jristz” Lezaeta Reyes 
Language-Team: Spanish (http://www.transifex.com/xfce/xfce-apps/language/es/)
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Language: es
Plural-Forms: nplurals=2; plural=(n != 1);


Opciones de ayuda:
  -h, --help Mostrar opciones de ayuda
  --help-all Muestra todas las opciones de ayuda
  --help-gtk Mostrar opciones GTK+

Opciones de la aplicación:
  -V, --version  Mostrar información de la versión
  -s, --socket-id=ID._DEL_SOCKET Socket del gestor de configuración
  --display=VISORVisor [display] X que usar


On the other hand the English output is OK.


Best Regards,
-- 
Manolo Díaz
--- End Message ---
--- Begin Message ---
I forgot to cc 840599-d...@bugs.debian.org long time ago. Sorry.

Kind regards.


-- 
Manolo Díaz--- End Message ---


Bug#1037405: marked as done (tumbler: build-depends on transitional package libgdk-pixbuf2.0-dev)

2023-06-13 Thread Debian Bug Tracking System
Your message dated Tue, 13 Jun 2023 07:12:01 +
with message-id 
and subject line Bug#1037405: fixed in tumbler 4.18.1-1
has caused the Debian Bug report #1037405,
regarding tumbler: build-depends on transitional package libgdk-pixbuf2.0-dev
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 ow...@bugs.debian.org
immediately.)


-- 
1037405: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037405
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tumbler
Version: 4.18.0-1
Severity: important
Tags: trixie sid
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: split-gdk-pixbuf

This package Build-Depends on libgdk-pixbuf2.0-dev.

In Debian 11, libgdk-pixbuf2.0-dev was split into two packages:

- libgdk-pixbuf-2.0-dev contains the supported gdk-pixbuf-2.0 library

- libgdk-pixbuf-xlib-2.0-dev contains the deprecated, unmaintained
  Xlib integration layer, gdk-pixbuf-xlib-2.0

If this package only requires functionality from gdk-pixbuf-2.0.pc
and , please update the build-dependency to
libgdk-pixbuf-2.0-dev.

If it also requires the Xlib integration gdk-pixbuf-xlib-2.0.pc and
 (unlikely), then you can also build-depend on
libgdk-pixbuf-xlib-2.0-dev until the package can be updated to remove
that requirement.

libgdk-pixbuf-2.0-dev was present in both Debian 11 and Debian 12, so
it is not necessary to have a "| libgdk-pixbuf2.0-dev" alternative
dependency, even for packages that are expected to be backported.

We should remove the libgdk-pixbuf2.0-dev transitional package during
the Debian 13 'trixie' cycle, so this bug is likely to become RC later.

Thanks,
smcv
--- End Message ---
--- Begin Message ---
Source: tumbler
Source-Version: 4.18.1-1
Done: Unit 193 

We believe that the bug you reported is fixed in the latest version of
tumbler, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1037...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Unit 193  (supplier of updated tumbler package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA384

Format: 1.8
Date: Tue, 13 Jun 2023 02:37:06 -0400
Source: tumbler
Architecture: source
Version: 4.18.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Xfce Maintainers 
Changed-By: Unit 193 
Closes: 1037405
Changes:
 tumbler (4.18.1-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream version 4.18.1.
   * d/control: Update B-D, libgdk-pixbuf2.0-dev → libgdk-pixbuf-2.0-dev.
 Closes: #1037405
   * Update Standards-Version to 4.6.2.
Checksums-Sha1:
 25bec7351c3c030f5ba4afa529b172d91bf3539b 2533 tumbler_4.18.1-1.dsc
 4aecfca62ab70244fd21214de0fad08fb27f1053 613283 tumbler_4.18.1.orig.tar.bz2
 f413fce771cdcf5ea330c7bfed0f45f035bd14ce 6500 tumbler_4.18.1-1.debian.tar.xz
 92ac1b58596c13bc4d9fa425cfbdd7d27e6d0101 24424 tumbler_4.18.1-1_amd64.buildinfo
Checksums-Sha256:
 016818cd56a4644df94d9dcdff35a60b22fca9ed08c7a9ecb3c122b1d9315062 2533 
tumbler_4.18.1-1.dsc
 ff61981a9c0af5fec768d4f1552bd63948a64b2f4db1c2e3d93c31c19dc563a0 613283 
tumbler_4.18.1.orig.tar.bz2
 3c6bf09b2e57a364cd437cc66c253728a02abf144b77724cad8537fd596e1c46 6500 
tumbler_4.18.1-1.debian.tar.xz
 9e5729c3447e8daffb8f6c11ab3f70c56195edfa285e931eac6215e14c3b6488 24424 
tumbler_4.18.1-1_amd64.buildinfo
Files:
 c6022eabe2a74856245ff9da6ab5a1f4 2533 xfce optional tumbler_4.18.1-1.dsc
 e66ff221ea5cd19c84ce80abca033f52 613283 xfce optional 
tumbler_4.18.1.orig.tar.bz2
 3f6eca9fd8265826074c8662f62132b5 6500 xfce optional 
tumbler_4.18.1-1.debian.tar.xz
 c9ed043a494f80aa32940cc67bcb9bb8 24424 xfce optional 
tumbler_4.18.1-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCQAdFiEEjbPlhoZdK0orGFpcUAHhsJqjdEsFAmSID9wACgkQUAHhsJqj
dEsaiA/9F78pYIBisb7QioHMt55lcWbbYfvUZEYoF3573oWtncnGuaS+n0ob3Hoc
bxMwm1mTc5rZ4fltVquxmQePkHfMd4G41imMJxfAIC/XazaA7elSC8bpZJuvDLck
XIGPAFHOCAl+IGQp74VxDyo9UrT0G6JRBpXb66IXTn1fgVK90Ek/H42hOESLJ1u1
PmALheZF8d9MNpcUE9Pd9pNngkvQ2Ph35qKSUBXaSESHdJ2PV04O2xwM3O9L3T0p
/qLf45/jDuWDfwd3HDuFkfmLif4geio6Djsx7SaAzhRJ5SZtNB/Wwlyq56RnCGzu
40rvwznd8CvcyD4dwGsoLG5xuBGZPJ6rw9OG5fqURhmkQRIB3jQUtiEj2EM5z8T/
x2qLRdf+EJe2lj9RH39dVccaVOYF9sBdd70pwqN04U5D4AWbONMjyCqi9qIu1LnI
VWQpXiM856k+iW0QvlmLnGJjbrpvf7cqsxf0k/

Processed: Re: packages with dependencies on transitional policykit-1 package

2023-06-11 Thread Debian Bug Tracking System
Processing control commands:

> severity -1 important
Bug #1025583 [lightdm-gtk-greeter] lightdm-gtk-greeter: recommends transitional 
policykit-1 package
Severity set to 'important' from 'normal'
> tags -1 + trixie sid
Bug #1025583 [lightdm-gtk-greeter] lightdm-gtk-greeter: recommends transitional 
policykit-1 package
Added tag(s) sid and trixie.

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



Processed: found 1021962 in 1.8.1-3, found 1035933 in 6.1.25-1, found 1034911 in 20221002-8 ..., tagging 1036033 ...

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

> found 1021962 1.8.1-3
Bug #1021962 [xfce4-notes-plugin] xfce4-notes-plugin: Missing from sid, testing 
and stable since before bullseye was even released
Marked as found in versions xfce4-notes-plugin/1.8.1-3.
> found 1035933 6.1.25-1
Bug #1035933 [src:linux] linux-image-6.1.0-8-amd64-unsigned: fails to build 
(llvm-strip not found, missing dependency?)
Marked as found in versions linux/6.1.25-1.
> found 1034911 20221002-8
Bug #1034911 {Done: Daniel Baumann } 
[progress-linux-container] bfh-container progress-linux-container: error when 
installing together
Marked as found in versions progress-linux-metapackages/20221002-8.
> found 1036777 20211009-19
Bug #1036777 {Done: Daniel Baumann } 
[bfh-container] bfh-container progress-linux-container: error when installing 
together
Marked as found in versions bfh-metapackages/20211009-19.
> tags 1036033 + moreinfo
Bug #1036033 [ddcci-dkms] upgrade-reports: bullseye -> bookworm kernel package 
upgrade fails when ddcci-dkms package installed
Added tag(s) moreinfo.
> reassign 1036621 regionset
Bug #1036621 [regioset] regioset: Missing documentation
Warning: Unknown package 'regioset'
Bug reassigned from package 'regioset' to 'regionset'.
No longer marked as found in versions regionset.
Ignoring request to alter fixed versions of bug #1036621 to the same values 
previously set
> reassign 1036734 wnpp
Bug #1036734 [astro] RFP: astro -- a gemini web browser
Warning: Unknown package 'astro'
Bug reassigned from package 'astro' to 'wnpp'.
Ignoring request to alter found versions of bug #1036734 to the same values 
previously set
Ignoring request to alter fixed versions of bug #1036734 to the same values 
previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1021962: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021962
1034911: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034911
1035933: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035933
1036033: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036033
1036621: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036621
1036734: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036734
1036777: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036777
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Processed: xfce4-notes-plugin not in sid nor testing since before April 2021

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

> severity 1021962 grave
Bug #1021962 [xfce4-notes-plugin] xfce4-notes-plugin: not available in 
"bullseye"
Severity set to 'grave' from 'wishlist'
> retitle 1021962 xfce4-notes-plugin: Missing from sid, testing and stable 
> since before bullseye was even released
Bug #1021962 [xfce4-notes-plugin] xfce4-notes-plugin: not available in 
"bullseye"
Changed Bug title to 'xfce4-notes-plugin: Missing from sid, testing and stable 
since before bullseye was even released' from 'xfce4-notes-plugin: not 
available in "bullseye"'.
> thanks
Stopping processing here.

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



Processed: Changed email address a long time ago (2nd try)

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

> submitter 784928 bugs@gmail.com
Bug #784928 [xserver-xorg-input-synaptics] xserver-xorg-input-synaptics: 
Elantech clickpad doesn't move without clicking
Changed Bug submitter to 'bugs@gmail.com' from 'José Luis González 
'.
> submitter 827956 bugs@gmail.com
Bug #827956 [grub-pc] grub: Doesn't apply default entry from /etc/default/grub
Changed Bug submitter to 'bugs@gmail.com' from 'José Luis González 
'.
> submitter 883385 bugs@gmail.com
Bug #883385 [abcde] abcde: retrieves CD-TEXT in latin and eyeD3 fails
Changed Bug submitter to 'bugs@gmail.com' from 'José Luis González 
'.
> submitter 711205 bugs@gmail.com
Bug #711205 [xserver-xorg-input-synaptics] xserver-xorg-input-synaptics: 
synclient doesn't recognize SoftButtonAreas
Changed Bug submitter to 'bugs@gmail.com' from 'José Luis González 
'.
> submitter 711601 bugs@gmail.com
Bug #711601 [xserver-xorg-input-synaptics] xserver-xorg-input-synaptics: Edge 
motion not working
Changed Bug submitter to 'bugs@gmail.com' from 'José Luis González 
'.
> submitter 826756 bugs@gmail.com
Bug #826756 [exo-utils] Mail reader menu entry in top level menu, not inside 
Internet
Changed Bug submitter to 'bugs@gmail.com' from 'José Luis González 
'.
> submitter 827958 bugs@gmail.com
Bug #827958 [grub-pc] grub: keyboard doesn't seem to work on menu
Changed Bug submitter to 'bugs@gmail.com' from 'José Luis González 
'.
> submitter 830579 bugs@gmail.com
Bug #830579 [xfce4] xfce4: screen locked with screensaver disabled and nothing 
to configure it
Changed Bug submitter to 'bugs@gmail.com' from 'José Luis González 
'.
> submitter 830664 bugs@gmail.com
Bug #830664 [xserver-xorg-video-intel] X.org: mouse pointer disappears on XFCE 
screen unlock
Changed Bug submitter to 'bugs@gmail.com' from 'José Luis González 
'.
> submitter 881261 bugs@gmail.com
Bug #881261 [xfburn] xfburn: TAO seems to be SAO
Changed Bug submitter to 'bugs@gmail.com' from 'José Luis González 
'.
> submitter 883683 bugs@gmail.com
Bug #883683 [emacs25] emacs25: ignores X resources
Changed Bug submitter to 'bugs@gmail.com' from 'José Luis González 
'.
> submitter 127060 bugs@gmail.com
Bug #127060 [x11-apps] xbase-clients: [xclipboard] sizes the 'Save' dialog box 
incorrectly
Changed Bug submitter to 'bugs@gmail.com' from 'José Luis González 
'.
> submitter 15 bugs@gmail.com
Bug #15 [icewm-lite] icewm-lite: Support for the windows menu
Changed Bug submitter to 'bugs@gmail.com' from 'José Luis González 
'.
> submitter 708388 bugs@gmail.com
Bug #708388 [xfce4-terminal] xfce4-terminal: Dynamic titling doesn't work
Changed Bug submitter to 'bugs@gmail.com' from 'José Luis González 
'.
> submitter 192827 bugs@gmail.com
Bug #192827 [xdiskusage] xdiskusage: Printing doesn't manage non-ASCII 
characters
Changed Bug submitter to 'bugs@gmail.com' from 'José Luis González 
'.
> submitter 881478 bugs@gmail.com
Bug #881478 [chromium] chromium: entering address or searching does not work in 
full screen
Changed Bug submitter to 'bugs@gmail.com' from 'José Luis González 
'.
> submitter 509805 bugs@gmail.com
Bug #509805 [sylpheed] sylpheed: checks all acounts with "check for new mail 
every n minutes"
Changed Bug submitter to 'bugs@gmail.com' from 'José Luis González 
'.
> submitter 883689 bugs@gmail.com
Bug #883689 [emacs25] emacsclient -a incorrectly applies -nw when an emacs 
frame didn't exist
Changed Bug submitter to 'bugs@gmail.com' from 'José Luis González 
'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
127060: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=127060
15: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=15
192827: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=192827
509805: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=509805
708388: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=708388
711205: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=711205
711601: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=711601
784928: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784928
826756: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=826756
827956: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=827956
827958: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=827958
830579: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830579
830664: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830664
881261: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881261
881478: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881478
883385: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883385
883683: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883683
883689: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883689
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Processed: Severity of #1016823 was important

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

> severity 1016823 important
Bug #1016823 [thunar] Thunar: add Lens Model to Image tab [patch attached]
Severity set to 'important' from 'wishlist'
> thanks
Stopping processing here.

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



Bug#1035452: marked as done (libmousepad-dev: missing Depends: libmousepad0 (= ${binary:Version}))

2023-05-05 Thread Debian Bug Tracking System
Your message dated Fri, 05 May 2023 11:48:53 +
with message-id 
and subject line Bug#1035452: fixed in mousepad 0.5.10-2
has caused the Debian Bug report #1035452,
regarding libmousepad-dev: missing Depends: libmousepad0 (= ${binary:Version})
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 ow...@bugs.debian.org
immediately.)


-- 
1035452: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035452
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libmousepad-dev
Version: 0.5.10-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package ships (or creates)
a broken symlink.

0m9.1s ERROR: FAIL: Broken symlinks:
  /usr/lib/x86_64-linux-gnu/libmousepad.so -> libmousepad.so.0.0.0 
(libmousepad-dev)


cheers,

Andreas
--- End Message ---
--- Begin Message ---
Source: mousepad
Source-Version: 0.5.10-2
Done: Yves-Alexis Perez 

We believe that the bug you reported is fixed in the latest version of
mousepad, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1035...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Yves-Alexis Perez  (supplier of updated mousepad package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 05 May 2023 13:22:50 +0200
Source: mousepad
Architecture: source
Version: 0.5.10-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Xfce Maintainers 
Changed-By: Yves-Alexis Perez 
Closes: 1035452
Changes:
 mousepad (0.5.10-2) unstable; urgency=medium
 .
   [ Debian Janitor ]
   * Apply multi-arch hints. + libmousepad-dev, libmousepad0: Add Multi-Arch:
 same.
 .
   [ Yves-Alexis Perez ]
   * d/control: libmousepad-dev: add missing dep on libmousepad0
 (Closes: #1035452)
Checksums-Sha1:
 bfa7acff0a75ad14973cdfba3d446f83c94286a8 1832 mousepad_0.5.10-2.dsc
 7c012481923472e9189ace17dda2a90f05bbaacb 8748 mousepad_0.5.10-2.debian.tar.xz
 91089c01bfe437a6f603d7b58801d4b56e579662 16515 
mousepad_0.5.10-2_amd64.buildinfo
Checksums-Sha256:
 a9769ca93daa124f55835c1ddc22745684af4827a552f4faa8bdc404ffad1819 1832 
mousepad_0.5.10-2.dsc
 e70319a511da937c9addd3e879b716c75db4310fd260f654ca0b62249a78540d 8748 
mousepad_0.5.10-2.debian.tar.xz
 8124ed8ea9af5dd04a0cb91f2702f84dd388268ef16a1548ea56430f58c7fc39 16515 
mousepad_0.5.10-2_amd64.buildinfo
Files:
 df2b473c54ea4c363d24ed9748e1aa08 1832 editors optional mousepad_0.5.10-2.dsc
 f3f28429b38d3d2a1f8ec26daec58880 8748 editors optional 
mousepad_0.5.10-2.debian.tar.xz
 8a8b2879baef82ca981c0f7684d481d7 16515 editors optional 
mousepad_0.5.10-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmRU6GAACgkQ3rYcyPpX
RFtc7QgAt89IzvX+rEPDxQX5uZ23bYFKwPDy+U3rB5gQlVbJJPvRwscfHT2pBJS+
n0s3exi6oaWDSFC4S3XKWkAoihJ03ppv/yH+AYLdEUJVPQg4IVDoV569nEJHmovy
rVMk4x8QgFEQzNbTFSWrs+/BRYdhwjkogSh4APgHo0FiuqEgCY5D/mAzKILTo4DZ
S210OlNDiEOsXcmx2a/XrI1f1w6SvdQOxZxmu22p+cnv48N40dBqiohvtBgYf0zA
bG9nBnPoAZ0VEOBtDAE1Gt2vU6xHdt94WCjYi8XcAejoN+8zOBkRvZQkRfxuboYH
GA1TYHArd/ELVZBFrXOh62MJ1y1waA==
=L8bv
-END PGP SIGNATURE End Message ---


Processed: gdm3/bullseye: logging in to Plasma and then Xfce fails

2023-04-30 Thread Debian Bug Tracking System
Processing control commands:

> found -1 gdm3/3.38.2.1-1
Bug #1035301 [gdm3,plasma-desktop,xfce4-session] gdm3/bullseye: logging in to 
Plasma and then Xfce fails
Marked as found in versions gdm3/3.38.2.1-1.
> fixed -1 gdm3/43.0-3
Bug #1035301 [gdm3,plasma-desktop,xfce4-session] gdm3/bullseye: logging in to 
Plasma and then Xfce fails
Marked as fixed in versions gdm3/43.0-3.
> found -1 plasma-desktop/4:5.20.5-4
Bug #1035301 [gdm3,plasma-desktop,xfce4-session] gdm3/bullseye: logging in to 
Plasma and then Xfce fails
Marked as found in versions plasma-desktop/4:5.20.5-4.
> fixed -1 plasma-desktop/4:5.27.2-1
Bug #1035301 [gdm3,plasma-desktop,xfce4-session] gdm3/bullseye: logging in to 
Plasma and then Xfce fails
Marked as fixed in versions plasma-desktop/4:5.27.2-1.
> found -1 xfce4-session/4.16.0-1
Bug #1035301 [gdm3,plasma-desktop,xfce4-session] gdm3/bullseye: logging in to 
Plasma and then Xfce fails
Marked as found in versions xfce4-session/4.16.0-1.
> fixed -1 xfce4-session/4.18.1-1
Bug #1035301 [gdm3,plasma-desktop,xfce4-session] gdm3/bullseye: logging in to 
Plasma and then Xfce fails
Marked as fixed in versions xfce4-session/4.18.1-1.

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



Processed: Re: Bug#1000793: bind9-dnsutils: dig command fails with "`fd > STDERR_FILENO' failed" when run from a XFCE4 desktop applet

2023-04-24 Thread Debian Bug Tracking System
Processing control commands:

> reassign -1 xfce4-genmon-plugin
Bug #1000793 [bind9-dnsutils] bind9-dnsutils: dig command fails with "`fd > 
STDERR_FILENO' failed" when run from a XFCE4 desktop applet
Bug reassigned from package 'bind9-dnsutils' to 'xfce4-genmon-plugin'.
No longer marked as found in versions bind9/1:9.16.22-1~deb11u1.
Ignoring request to alter fixed versions of bug #1000793 to the same values 
previously set
> tags -1 = upstream fixed-upstream patch
Bug #1000793 [xfce4-genmon-plugin] bind9-dnsutils: dig command fails with "`fd 
> STDERR_FILENO' failed" when run from a XFCE4 desktop applet
Added tag(s) upstream, fixed-upstream, and patch.
> affects -1 bind9-dnsutils
Bug #1000793 [xfce4-genmon-plugin] bind9-dnsutils: dig command fails with "`fd 
> STDERR_FILENO' failed" when run from a XFCE4 desktop applet
Added indication that 1000793 affects bind9-dnsutils
> forwarded -1 
> https://gitlab.xfce.org/panel-plugins/xfce4-genmon-plugin/-/issues/19
Bug #1000793 [xfce4-genmon-plugin] bind9-dnsutils: dig command fails with "`fd 
> STDERR_FILENO' failed" when run from a XFCE4 desktop applet
Set Bug forwarded-to-address to 
'https://gitlab.xfce.org/panel-plugins/xfce4-genmon-plugin/-/issues/19'.

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



Processed: reassign to xfce4-panel

2023-04-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> reassign 1031036 xfce4-panel
Bug #1031036 [sagemath] sagemath: sage starts from command line but not from 
desktop menu
Bug reassigned from package 'sagemath' to 'xfce4-panel'.
No longer marked as found in versions sagemath/9.5-6.
Ignoring request to alter fixed versions of bug #1031036 to the same values 
previously set
> retitle 1031036 xfce4-panel: Input/output error when trying to launch sagemath
Bug #1031036 [xfce4-panel] sagemath: sage starts from command line but not from 
desktop menu
Changed Bug title to 'xfce4-panel: Input/output error when trying to launch 
sagemath' from 'sagemath: sage starts from command line but not from desktop 
menu'.
> thanks
Stopping processing here.

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



Processed: closing 827838

2023-03-30 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> close 827838
Bug #827838 [light-locker] light-locker makes it prohibitely difficult to debug
Marked Bug as done
> thanks
Stopping processing here.

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



Processed: Re: Bug#1031968: libxfconf-0-dev fails to build with valac installed

2023-02-28 Thread Debian Bug Tracking System
Processing control commands:

> severity -1 important
Bug #1031968 {Done: Unit 193 } [libxfconf-0-dev] 
libxfconf-0-dev fails to build with valac installed
Ignoring request to change severity of Bug 1031968 to the same value.

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



Bug#1031967: marked as done (libxfce4util-dev fails to build with valac installed)

2023-02-26 Thread Debian Bug Tracking System
Your message dated Mon, 27 Feb 2023 06:19:13 +
with message-id 
and subject line Bug#1031967: fixed in libxfce4util 4.18.1-2
has caused the Debian Bug report #1031967,
regarding libxfce4util-dev fails to build with valac installed
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 ow...@bugs.debian.org
immediately.)


-- 
1031967: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031967
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libxfce4util-dev
Version: 4.18.1-1
Severity: serious
Tags: ftbfs patch
Justification: fails to build from source (but built successfully in the past)

Dear Maintainer,

to repeat the problem, please follow these steps:

$ sudo apt install valac
$ apt-get source libxfce4util-dev
$ cd libxfce4util-4.18.1/
$ dpkg-buildpackage -j`nproc`

Output:
===
...
   dh_missing
dh_missing: warning: usr/share/vala/vapi/libxfce4util-1.0.vapi exists in 
debian/tmp but is not installed to anywhere 
The following debhelper tools have reported what they installed (with 
files per package)
 * dh_install: gir1.2-libxfce4util-1.0 (1), libxfce4util-bin (1), 
libxfce4util-common (1), libxfce4util-dev (38), libxfce4util7 (2)
 * dh_installdocs: gir1.2-libxfce4util-1.0 (0), libxfce4util-bin (0), 
libxfce4util-common (0), libxfce4util-dev (1), libxfce4util7 (0)
 * dh_installman: gir1.2-libxfce4util-1.0 (0), libxfce4util-bin (1), 
libxfce4util-common (0), libxfce4util-dev (0), libxfce4util7 (0)
If the missing files are installed by another tool, please file a bug 
against it.
When filing the report, if the tool is not part of debhelper itself, 
please reference the
"Logging helpers and dh_missing" section from the "PROGRAMMING" guide 
for debhelper (10.6.3+).
  (in the debhelper package: /usr/share/doc/debhelper/PROGRAMMING.gz)
Be sure to test with dpkg-buildpackage -A/-B as the results may vary 
when only a subset is built
If the omission is intentional or no other helper can take care of this 
consider adding the
paths to debian/not-installed.
dh_missing: error: missing files, aborting
make: *** [debian/rules:22: binary] Error 255
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
===

To fix the issue I propose including valac to package build dependencies
and include vala api file to libxfce4util-dev.

This vala api file is useful when you wish to build some xfce plugins
from vala sources. One example is xfce4-notes-plugin which I was trying
to build and found that some vala api files are missing in Debian
distribution.

Possible fix follows.
===
diff -Naur libxfce4util-4.18.1-orig/debian/control 
libxfce4util-4.18.1/debian/control
--- libxfce4util-4.18.1-orig/debian/control 2023-01-12 10:28:40.0 +0300
+++ libxfce4util-4.18.1/debian/control  2023-02-26 04:31:58.179657805 +0300
@@ -9,6 +9,7 @@
intltool,
libgirepository1.0-dev,
libglib2.0-dev,
+   valac,
xfce4-dev-tools
 Rules-Requires-Root: no
 Standards-Version: 4.6.2
diff -Naur libxfce4util-4.18.1-orig/debian/libxfce4util-dev.install 
libxfce4util-4.18.1/debian/libxfce4util-dev.install
--- libxfce4util-4.18.1-orig/debian/libxfce4util-dev.install2022-12-05 
09:48:34.0 +0300
+++ libxfce4util-4.18.1/debian/libxfce4util-dev.install 2023-02-26 
04:27:37.163908152 +0300
@@ -3,3 +3,4 @@
 usr/lib/*/pkgconfig/*
 usr/share/gir-1.0/*
 usr/share/gtk-doc/html/libxfce4util/*
+usr/share/vala/vapi/*
===

-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-3-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), 
LANGUAGE=ru_RU:ru
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libxfce4util-dev depends on:
ii  gir1.2-libxfce4util-1.0  4.18.1-1
ii  libglib2.0-dev   2.74.5

Bug#1031968: marked as done (libxfconf-0-dev fails to build with valac installed)

2023-02-26 Thread Debian Bug Tracking System
Your message dated Mon, 27 Feb 2023 06:20:24 +
with message-id 
and subject line Bug#1031968: fixed in xfconf 4.18.0-2
has caused the Debian Bug report #1031968,
regarding libxfconf-0-dev fails to build with valac installed
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 ow...@bugs.debian.org
immediately.)


-- 
1031968: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031968
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libxfconf-0-dev
Version: 4.18.0-1
Severity: serious
Tags: ftbfs patch
Justification: fails to build from source (but built successfully in the past)

Dear Maintainer,

To reproduce the problem please follow these steps:

$ sudo apt install valac
$ apt-get source libxfconf-0-dev
$ cd xfconf-4.18.0
$ dpkg-buildpackage -j`nproc`

Output:

...
   dh_compress
   dh_fixperms
   dh_missing
dh_missing: warning: usr/share/vala/vapi/libxfconf-0.deps exists in debian/tmp 
but is not installed to anywhere
dh_missing: warning: usr/share/vala/vapi/libxfconf-0.vapi exists in debian/tmp 
but is not installed to anywhere
The following debhelper tools have reported what they installed (with 
files per package)
 * dh_install: gir1.2-xfconf-0 (1), libxfconf-0-3 (2), libxfconf-0-dev 
(5), xfconf (5)
 * dh_installdocs: gir1.2-xfconf-0 (0), libxfconf-0-3 (0), 
libxfconf-0-dev (1), xfconf (0)
 * dh_installman: gir1.2-xfconf-0 (0), libxfconf-0-3 (0), 
libxfconf-0-dev (0), xfconf (1)
If the missing files are installed by another tool, please file a bug 
against it.
When filing the report, if the tool is not part of debhelper itself, 
please reference the
"Logging helpers and dh_missing" section from the "PROGRAMMING" guide 
for debhelper (10.6.3+).
  (in the debhelper package: /usr/share/doc/debhelper/PROGRAMMING.gz)
Be sure to test with dpkg-buildpackage -A/-B as the results may vary 
when only a subset is built
If the omission is intentional or no other helper can take care of this 
consider adding the
paths to debian/not-installed.
dh_missing: error: missing files, aborting
make: *** [debian/rules:7: binary] Error 255
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2


To fix the issue I propose including valac to package build dependencies
and include vala api files to libxfconf-0-dev.

This vala api files are useful when you wish to build some xfce plugins
from vala sources. One example is xfce4-notes-plugin which I was trying
to build and found that some vala api files are missing in Debian
distribution.

Possible fix follows (check the patch).


-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-3-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), 
LANGUAGE=ru_RU:ru
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libxfconf-0-dev depends on:
ii  gir1.2-xfconf-0   4.18.0-1
ii  libglib2.0-dev2.74.5-1
ii  libxfconf-0-3 4.18.0-1
ii  pkg-config1.8.1-1
ii  pkgconf [pkg-config]  1.8.1-1

libxfconf-0-dev recommends no packages.

libxfconf-0-dev suggests no packages.

-- no debconf information
diff -Naur xfconf-4.18.0-orig/debian/control xfconf-4.18.0/debian/control
--- xfconf-4.18.0-orig/debian/control   2022-12-10 10:48:30.0 +0300
+++ xfconf-4.18.0/debian/control2023-02-26 05:03:43.079063926 +0300
@@ -9,6 +9,7 @@
intltool,
libgirepository1.0-dev,
libxfce4util-dev (>= 4.17.3),
+   valac,
xfce4-dev-tools (>= 4.16)
 Rules-Requires-Root: no
 Standards-Version: 4.6.1
diff -Naur xfconf-4.18.0-orig/debian/libxfconf-0-dev.install 
xfconf-4.18.0/debian/libxfconf-0-dev.install
--- xfconf-4.18.0-orig/debian/libxfconf-0-dev.install   2020-11-14 
13:01:16.0 +0300
+++ xfconf-4.18.0/debian/libxfconf-0-dev.install2023-02-26 
05:02:28.854000853 +0300
@@ -3,3 +3,4 @@
 usr/lib/*/pkgconfig
 usr/share/gir-1.0/*
 usr/share/gtk-doc
+usr/share/vala/vapi/*
--- End Message ---
--- Begin Message ---
Source: xfconf
Source-Version: 4.18.0-2
Done: Unit 193 

We believe that the

Bug#1031971: marked as done (libxfce4panel-2.0-dev fails to build with valac installed)

2023-02-26 Thread Debian Bug Tracking System
Your message dated Mon, 27 Feb 2023 05:34:03 +
with message-id 
and subject line Bug#1031971: fixed in xfce4-panel 4.18.2-1
has caused the Debian Bug report #1031971,
regarding libxfce4panel-2.0-dev fails to build with valac installed
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 ow...@bugs.debian.org
immediately.)


-- 
1031971: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031971
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libxfce4panel-2.0-dev
Version: 4.18.1-1
Severity: serious
Tags: ftbfs patch
Justification: fails to build from source (but built successfully in the past)

Dear Maintainer,

To reproduce the problem please follow these steps:

$ sudo apt install valac
$ apt-get source libxfce4panel-2.0-dev
$ cd xfce4-panel-4.18.1
$ sudo apt-get build-dep .
$ dpkg-buildpackage -j`nproc`

Output:

...
   dh_compress
   dh_fixperms
   debian/rules override_dh_missing
make[1]: Entering directory '/home/spinal/tmp/xfce4-panel-4.18.1'
dh_missing --fail-missing -X .la
dh_missing: warning: usr/share/vala/vapi/libxfce4panel-2.0.deps exists in 
debian/tmp but is not installed to anywhere
dh_missing: warning: usr/share/vala/vapi/libxfce4panel-2.0.vapi exists in 
debian/tmp but is not installed to anywhere
The following debhelper tools have reported what they installed (with 
files per package)
 * dh_install: gir1.2-libxfce4panel-2.0 (1), libxfce4panel-2.0-4 (3), 
libxfce4panel-2.0-dev (5), xfce4-panel (18)
 * dh_installdocs: gir1.2-libxfce4panel-2.0 (0), libxfce4panel-2.0-4 
(0), libxfce4panel-2.0-dev (0), xfce4-panel (1)
 * dh_installman: gir1.2-libxfce4panel-2.0 (0), libxfce4panel-2.0-4 
(0), libxfce4panel-2.0-dev (0), xfce4-panel (1)
If the missing files are installed by another tool, please file a bug 
against it.
When filing the report, if the tool is not part of debhelper itself, 
please reference the
"Logging helpers and dh_missing" section from the "PROGRAMMING" guide 
for debhelper (10.6.3+).
  (in the debhelper package: /usr/share/doc/debhelper/PROGRAMMING.gz)
Be sure to test with dpkg-buildpackage -A/-B as the results may vary 
when only a subset is built
If the omission is intentional or no other helper can take care of this 
consider adding the
paths to debian/not-installed.
dh_missing: error: missing files, aborting
make[1]: *** [debian/rules:16: override_dh_missing] Error 255
make[1]: Leaving directory '/home/spinal/tmp/xfce4-panel-4.18.1'
make: *** [debian/rules:7: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2



To fix the issue I propose including valac to package build dependencies
and include vala api files to libxfce4panel-2.0-dev.

These vala api files are useful when you wish to build some xfce plugins
from vala sources. One example is xfce4-notes-plugin which I was trying
to build and found that vala api files are missing in Debian distribution.

Please keep in mind that building libxfce4panel-2.0-dev will also fail if
you didn't install libxfce4util-1.0 with vala api files. It means that
Debian bug #1031967 should be resolved first to satisfy vala api deps of
this package.

For possible fix check the following patch.


-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-3-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), 
LANGUAGE=ru_RU:ru
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libxfce4panel-2.0-dev depends on:
ii  gir1.2-libxfce4panel-2.0  4.18.1-1
ii  libglib2.0-dev2.74.5-1
ii  libgtk-3-dev  3.24.36-4
ii  libxfce4panel-2.0-4   4.18.1-1
ii  libxfce4util-dev  4.18.1-1

libxfce4panel-2.0-dev recommends no packages.

libxfce4panel-2.0-dev suggests no packages.

-- no debconf information
diff -Naur xfce4-panel-4.18.1-orig/debian/control 
xfce4-panel-4.18.1/debian/control
--- xfce4-panel-4.18.1-orig/debian/control  2023-01-12 10:55:51.0 
+0300
+++ xfce4-panel-4.18.1/debian/control   2023-02-26 05:33:54.816823882 +0300
@@ -19,6 +19,7 @@
libxfce4ui-2-dev (>= 4.17.1),
 

Processed: Re: Bug#1031983: light-locker: Fails to login a user back to her previous session (session lost, new one started)

2023-02-26 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 moreinfo
Bug #1031983 [light-locker] light-locker: Fails to login a user back to her 
previous session (session lost, new one started)
Added tag(s) moreinfo.

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



Processed: FTBFS that cannot happen on buildds are not RC (but should still be fixed)

2023-02-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> severity 1031967 important
Bug #1031967 [libxfce4util-dev] libxfce4util-dev fails to build with valac 
installed
Severity set to 'important' from 'serious'
> severity 1031968 important
Bug #1031968 [libxfconf-0-dev] libxfconf-0-dev fails to build with valac 
installed
Severity set to 'important' from 'serious'
> severity 1031971 important
Bug #1031971 [libxfce4panel-2.0-dev] libxfce4panel-2.0-dev fails to build with 
valac installed
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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



Processed: FTBFS that cannot happen are not RC (but should still be fixed)

2023-02-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> severity 1031967 serious
Bug #1031967 [libxfce4util-dev] libxfce4util-dev fails to build with valac 
installed
Ignoring request to change severity of Bug 1031967 to the same value.
> severity 1031968 serious
Bug #1031968 [libxfconf-0-dev] libxfconf-0-dev fails to build with valac 
installed
Ignoring request to change severity of Bug 1031968 to the same value.
> severity 1031971 serious
Bug #1031971 [libxfce4panel-2.0-dev] libxfce4panel-2.0-dev fails to build with 
valac installed
Ignoring request to change severity of Bug 1031971 to the same value.
> thanks
Stopping processing here.

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



Bug#1028399: marked as done (xfdesktop4: apps menu not popping up when menu icons disabled)

2023-01-31 Thread Debian Bug Tracking System
Your message dated Tue, 31 Jan 2023 23:56:57 +0900
with message-id 

and subject line Re: Bug#1028399: xfdesktop4: apps menu not popping up when 
menu icons disabled
has caused the Debian Bug report #1028399,
regarding xfdesktop4: apps menu not popping up when menu icons disabled
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 ow...@bugs.debian.org
immediately.)


-- 
1028399: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028399
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xfdesktop4
Version: 4.18.0-1
Severity: normal

apps menu not popping up when menu icons disabled
seems to have been fixed upstream

https://gitlab.xfce.org/xfce/xfdesktop/-/commit/3731b70c53fd219bd7d24eafb8822789059a59f7

-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.1.0-1-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_CPU_OUT_OF_SPEC, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages xfdesktop4 depends on:
ii  exo-utils4.18.0-1
ii  libc62.36-8
ii  libcairo-gobject21.16.0-7
ii  libcairo21.16.0-7
ii  libexo-2-0   4.18.0-1
ii  libgarcon-1-04.18.0-1
ii  libgarcon-gtk3-1-0   4.18.0-1
ii  libgdk-pixbuf-2.0-0  2.42.10+dfsg-1
ii  libglib2.0-0 2.74.4-1
ii  libgtk-3-0   3.24.36-1
ii  libnotify4   0.8.1-1
ii  libpango-1.0-0   1.50.12+ds-1
ii  libthunarx-3-0   4.18.1-1
ii  libwnck-3-0  43.0-3
ii  libx11-6 2:1.8.3-3
ii  libxfce4ui-2-0   4.18.1-1
ii  libxfce4util74.18.0-1
ii  libxfconf-0-34.18.0-1
ii  xfdesktop4-data  4.18.0-1

Versions of packages xfdesktop4 recommends:
ii  dbus-user-session [default-dbus-session-bus]  1.14.4-1
ii  dbus-x11 [dbus-session-bus]   1.14.4-1
ii  librsvg2-common   2.54.5+dfsg-1
ii  tumbler   4.18.0-1
ii  xdg-user-dirs 0.18-1

xfdesktop4 suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 4.18.1-1

thanks, fixed

2023年1月18日(水) 16:44 Yves-Alexis Perez :
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> On Tue, 2023-01-10 at 23:15 +0900, SHITAMORI Akira wrote:
> > apps menu not popping up when menu icons disabled
> > seems to have been fixed upstream
> >
> > https://gitlab.xfce.org/xfce/xfdesktop/-/commit/3731b70c53fd219bd7d24eafb8822789059a59f7
>
> Thanks for the report, we'll fix that when upstream pushes a new release.
>
> Regards,
> - --
> Yves-Alexis
> -BEGIN PGP SIGNATURE-
>
> iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmPHo0oACgkQ3rYcyPpX
> RFvFRwf9GN7BK2wty21p5akr1xrbLFprrsGGewRhwChLxdJ29NYP1IG6T/VgdgmG
> hYm4T8cwz2Wugqm6FCAButOUAILsBfeK2UOZQrUxQrrYekNdzDaFOupGpfSgd7gd
> A0Ys3gkcO7nrz7CgF1HmHzlzy9GyoFfQc6BYOFoUiiUYMenSLEQbWjP7/NX5/0WZ
> 7Or5WfoashnEHMmWowiTY6B28m+ATQhCT/GZ/s201wT5dsAVKjfHrrBuZNwn+VDA
> YB3Mt5hd5ly30Z30PZOff3QfpnAs6yTEY9CRcNgSB4ggwnpSSRKyPmataumWh/g4
> 0wTaXB/Aihfd+matkpR2QMmUGu2PIA==
> =LVr6
> -END PGP SIGNATURE End Message ---


Bug#1028033: marked as done (xfce4 package incorrectly reporting version 4.16 instead of 4.18)

2023-01-19 Thread Debian Bug Tracking System
Your message dated Thu, 19 Jan 2023 17:35:24 +
with message-id 
and subject line Bug#1028033: fixed in xfce4 4.18
has caused the Debian Bug report #1028033,
regarding xfce4 package incorrectly reporting version 4.16 instead of 4.18
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 ow...@bugs.debian.org
immediately.)


-- 
1028033: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028033
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xfce4
Version: 4.16
Severity: normal
X-Debbugs-Cc: jason.lee.quinn+deb...@gmail.com

Dear Maintainer,

The xfce4 package still thinks xfce 4.16 is being used even
though it is now 4.18. 

I use Synaptic and it shows that the xfce4 package reports 4.16 as
both the "Installed" and "Latest Version". 

This system was installed through a daily installer after the
change to 4.18 so all vestiges of 4.16 should be gone.
I picked "XFCE" as my desktop during an expert net install. The
task-xfce-desktop package is reporting itself as version 3.70.

I'd guess it's just a minor packaging error where a versioning
number was forgotten to be changed.

Cheers,
Jason


-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 6.0.0-6-amd64 (SMP w/24 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages xfce4 depends on:
ii  libxfce4ui-utils 4.18.0-1
ii  thunar   4.18.0-1
ii  xfce4-appfinder  4.18.0-1
ii  xfce4-panel  4.18.0-1
ii  xfce4-pulseaudio-plugin  0.4.5-1
ii  xfce4-session4.18.0-1
ii  xfce4-settings   4.18.0-1
ii  xfconf   4.18.0-1
ii  xfdesktop4   4.18.0-1
ii  xfwm44.18.0-1

Versions of packages xfce4 recommends:
ii  desktop-base  12.0.2
ii  tango-icon-theme  0.8.90-11
ii  thunar-volman 4.18.0-1
ii  xfce4-notifyd 0.6.5-1
ii  xorg  1:7.7+23

Versions of packages xfce4 suggests:
ii  xfce4-goodies4.14.0
ii  xfce4-power-manager  4.18.0-1

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: xfce4
Source-Version: 4.18
Done: Yves-Alexis Perez 

We believe that the bug you reported is fixed in the latest version of
xfce4, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1028...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Yves-Alexis Perez  (supplier of updated xfce4 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 19 Jan 2023 18:16:42 +0100
Source: xfce4
Architecture: source
Version: 4.18
Distribution: unstable
Urgency: medium
Maintainer: Debian Xfce Maintainers 
Changed-By: Yves-Alexis Perez 
Closes: 1028033
Changes:
 xfce4 (4.18) unstable; urgency=medium
 .
   [ Debian Janitor ]
   * Remove constraints unnecessary since buster:
 + xfce4: Drop versioned constraint on desktop-base and tango-icon-theme in
   Recommends.
 .
   [ Akbarkhon Variskhanov ]
   * debian/control:
 - Bump Standards-Version to 4.6.2
 - Bump debhelper-compat to 13
 - Bump Depends for Xfce 4.18 (Closes: #1028033)
Checksums-Sha1:
 c212d1c741fb52de83a87c41a9193f81fd0fab40 1263 xfce4_4.18.dsc
 179cbdbe34de31a3828e2715d074c9ad1a277de2 7024 xfce4_4.18.tar.xz
 306cbd8c3146bd6c9d96e9e5115bddd174c9feae 5900 xfce4_4.18_amd64.buildinfo
Checksums-Sha256:
 00a87cca67f26c94b25278316aa7c219b09bbc3fb7e79f6892b4c0a070f63477 1263 
xfce4_4.18.dsc
 877cd85df4867d85bab7cf488044fef3b757840caba7ce317b4689c25394d33f 7024 
xfce4_4.18.tar.xz
 0d414b2b8aa6c0fe82fdcade251e1e2e390ee86e0f16d834539d3431190c3bae 5900 
xfce4_4.18_amd64.buildinfo
Files:
 8406ea686bc474899e733840a238f805 1263 metapackages optional xfce4_4.18.dsc
 3d1d4a38ffb7db3ecb1142aa97731cdd 7024 metapackages optional xfce4_4.18.tar.xz
 e3d18f435367463386454aa1ed292d08 5900 metapackages optional 
xfce4_4.18_amd64.build

Bug#1027097: marked as done (xfwm4: taskbar is visible, when using borderless fullscreen)

2023-01-18 Thread Debian Bug Tracking System
Your message dated Wed, 18 Jan 2023 22:38:25 +0100
with message-id <3f6721109237c2682b9faffc5fa6c96dd8af6262.ca...@debian.org>
and subject line Re: Bug#1027097: xfwm4: taskbar is visible, when using 
borderless fullscreen
has caused the Debian Bug report #1027097,
regarding xfwm4: taskbar is visible, when using borderless fullscreen
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 ow...@bugs.debian.org
immediately.)


-- 
1027097: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027097
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xfwm4
Version: 4.18.0-1
Severity: normal
X-Debbugs-Cc: betaversion...@gmail.com

Dear Maintainer,

after updating xfwm4 from 4.16.1-1 to 4.18.0-1 taskbar now is always visible,
when using borderless fullscreen, like when watching video fullscreen in MPV or
on youtube in browser, or playing games with borderless fullscreen. If game
uses exclusive fullscreen, taskbar is not visible.

I tried using Openbox instead of xfwm4 and with Openbox taskbar works as
expected: not visible in borderless fullsreen.

DE is LXQt.


-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.0.0-6-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), 
LANGUAGE=ru_RU:ru
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages xfwm4 depends on:
ii  libc6 2.36-5
ii  libcairo2 1.16.0-6
ii  libepoxy0 1.5.10-1
ii  libgdk-pixbuf-2.0-0   2.42.10+dfsg-1
ii  libglib2.0-0  2.74.1-2
ii  libgtk-3-03.24.34-5
ii  libpango-1.0-01.50.10+ds-1
ii  libpangocairo-1.0-0   1.50.10+ds-1
ii  libstartup-notification0  0.12-6+b1
ii  libwnck-3-0   43.0-2
ii  libx11-6  2:1.8.3-3
ii  libxcomposite11:0.4.5-1
ii  libxdamage1   1:1.1.5-2
ii  libxext6  2:1.3.4-1+b1
ii  libxfce4ui-2-04.18.0-1
ii  libxfce4util7 4.18.0-1
ii  libxfconf-0-3 4.18.0-1
ii  libxfixes31:6.0.0-2
ii  libxinerama1  2:1.1.4-3
ii  libxpresent1  1.0.0-2+b10
ii  libxrandr22:1.5.2-2+b1
ii  libxrender1   1:0.9.10-1.1
ii  libxres1  2:1.2.1-1

Versions of packages xfwm4 recommends:
ii  librsvg2-common  2.54.5+dfsg-1

Versions of packages xfwm4 suggests:
pn  xfce4  

-- no debconf information
--- End Message ---
--- Begin Message ---
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Wed, 2023-01-18 at 23:14 +0300, Beta Version wrote:
> Hi. This problem has already been solved by updating lxqt-panel to 1.2.1-1.
> So if you have lxqt-panel 1.2.1-1 installed, I guess you won't be able to
> reproduce this bug. Anyway, the problem is solved and this bugreport can be
> closed. Thank you for your time.

Well it would have been nice to specify you were using lxqt-panel then. I'm
not familiar with LXQt and since you were using xfwm4 anyway I assumed you
were using xfce4-panel as well.

Anyway, closing this.
- -- 
Yves-Alexis
-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmPIZtEACgkQ3rYcyPpX
RFsDxwgAqalYtsLCE7VWgz1OcksC3YoSxBjXe/HWaUngxDtiOQfZSp0VDPcaLhfI
jXyv73buFGBVTlG43MsZWBEcEr6AlLxUTW0ZhOiAbMCe45Mx6y9Zi1f/OH+a6NYL
Tlq/rWCbTCTb/W3807q6F9C/uyqSmV++z30sm2jjFWl2X0snK7SdLVEJeVXNqTk4
OEjN3tHnEfffpmfEWUWjUKCAv3RUnBP2PzzVuvWIFuQtuZ0rK9bxmtYwCZBo+LrK
3tFtIiiuxPuERiP15wFdoxbjVC54Iz8QzMaohxPmKwhEW/2achSHYy5vy5CLJRhB
rT7C+7jH3jokZyGWaF8WRDcI1hZntw==
=mhPW
-END PGP SIGNATURE End Message ---


Bug#1027900: marked as done (parole 4.16.0-2 does not start)

2023-01-18 Thread Debian Bug Tracking System
Your message dated Wed, 18 Jan 2023 20:56:34 +
with message-id 
and subject line Bug#1027900: fixed in parole 4.16.0-3
has caused the Debian Bug report #1027900,
regarding parole  4.16.0-2 does not start
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 ow...@bugs.debian.org
immediately.)


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

Package: parole
Version: 4.16.0-2
Severity: normal
X-Debbugs-Cc: serfyod...@yandex.ru

Dear Maintainer,

parole 4.16.0-2 when running in the terminal emulator outputs :
free(): invalid pointer
Emergency stop

parole 4.16.0-1 is up and running.


-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.0.0-6-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages parole depends on:
ii  gstreamer1.0-alsa [gstreamer1.0-audiosink]  1.20.4-1
ii  gstreamer1.0-libav  1.20.3-1+b1
ii  gstreamer1.0-plugins-bad [gstreamer1.0-audiosink]   1.20.4-1+b1
ii  gstreamer1.0-plugins-base   1.20.4-1
ii  gstreamer1.0-plugins-good [gstreamer1.0-audiosink]  1.20.3-1+b1
ii  gstreamer1.0-x  1.20.4-1
ii  libc6   2.36-7
ii  libcairo2   1.16.0-7
ii  libdbus-1-3 1.14.4-1
ii  libdbus-glib-1-20.112-3
ii  libgdk-pixbuf-2.0-0 2.42.10+dfsg-1
ii  libglib2.0-02.74.4-1
ii  libgstreamer-plugins-base1.0-0  1.20.4-1
ii  libgstreamer1.0-0   1.20.4-1
ii  libgtk-3-0  3.24.36-1
ii  libnotify4  0.8.1-1
ii  libtagc01.13-1
ii  libx11-62:1.8.3-3
ii  libxfce4ui-2-0  4.18.0-1
ii  libxfce4util7   4.18.0-1
ii  libxfconf-0-3   4.18.0-1

parole recommends no packages.

Versions of packages parole suggests:
ii  gstreamer1.0-plugins-bad   1.20.4-1+b1
ii  gstreamer1.0-plugins-ugly  1.20.3-1

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: parole
Source-Version: 4.16.0-3
Done: Yves-Alexis Perez 

We believe that the bug you reported is fixed in the latest version of
parole, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1027...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Yves-Alexis Perez  (supplier of updated parole package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 18 Jan 2023 20:30:33 +0100
Source: parole
Architecture: source
Version: 4.16.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Xfce Maintainers 
Changed-By: Yves-Alexis Perez 
Closes: 1027900
Changes:
 parole (4.16.0-3) unstable; urgency=medium
 .
   * d/p/0002-build-Bump-GLib-minimum-required-to-2.38 added (Closes: #1027900)
   * d/control: update standards version
Checksums-Sha1:
 64152ac1aa251170a613f2d0918bb41b734f8a24 1896 parole_4.16.0-3.dsc
 fac9cbf2516de04c765cc7e364e1ca874dcddb57 6992 parole_4.16.0-3.debian.tar.xz
 83537cee7dfc04d0315233f52081b7b182625436 18046 parole_4.16.0-3_amd64.buildinfo
Checksums-Sha256:
 7a823dd531e44885971b9df9bbc6d9e7ab18face25f5f62116deb04e263c2f8a 1896 
parole_4.16.0-3.dsc
 620911b2dad9b4d969ddf3aa401322d45712aff59575d7eb3429a81f65d4b2c4 6992 
parole_4.16.0-3.debian.tar.xz
 e0ab5fe63e94730d79eb7a3980ff45ade7308d5fc710189dc0d7c53ee94d3314 18046 
parole_4.16.0-3_amd64.buildinfo
Files:
 fd6d39256894d5cfe20976b6b21206f1 1896 xfce optional parole_4.16.0-3.dsc
 730af9c4cdf15179abbad89cc7134623 6992 xfce optional

Processed: bug 1026884 is forwarded to https://gitlab.xfce.org/xfce/xfwm4/-/issues/699

2023-01-18 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> forwarded 1026884 https://gitlab.xfce.org/xfce/xfwm4/-/issues/699
Bug #1026884 [xfwm4] xfwm4: Reserved space through _NET_WM_STRUT property 
ignored
Set Bug forwarded-to-address to 
'https://gitlab.xfce.org/xfce/xfwm4/-/issues/699'.
> thanks
Stopping processing here.

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



Processed: block 1026648 with 1027900

2023-01-18 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> block 1026648 with 1027900
Bug #1026648 {Done: Yves-Alexis Perez } [src:parole] parole: 
FTBFS: make[1]: *** [debian/rules:22: override_dh_missing] Error 25
1026648 was not blocked by any bugs.
1026648 was not blocking any bugs.
Added blocking bug(s) of 1026648: 1027900
> thanks
Stopping processing here.

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



Processed: notfixed 766024 in 22.08.3-1, fixed 766024 in 4:22.08.3-1, fixed 1021531 in 3.42.0-2, tagging 1022849 ...

2023-01-18 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> notfixed 766024 22.08.3-1
Bug #766024 {Done: matthias.geiger1...@tutanota.de} [marble] marble: South 
Sudan not marked on "Political Map"
There is no source info for the package 'marble' at version '22.08.3-1' with 
architecture ''
Unable to make a source version for version '22.08.3-1'
No longer marked as fixed in versions 22.08.3-1.
> fixed 766024 4:22.08.3-1
Bug #766024 {Done: matthias.geiger1...@tutanota.de} [marble] marble: South 
Sudan not marked on "Political Map"
Marked as fixed in versions marble/4:22.08.3-1.
> fixed 1021531 3.42.0-2
Bug #1021531 {Done: Claudius Heine } [evolution-ews] Contacts: 
retrieve user S/MIME certificates patch was not applied on stable
Marked as fixed in versions evolution-ews/3.42.0-2.
> tags 1022849 - sid
Bug #1022849 {Done: Yves-Alexis Perez } [src:lightdm] 
lightdm: Project migrated to new homepage
Removed tag(s) sid.
> notfixed 1021449 1.62.1+dsfg1-1
Bug #1021449 {Done: Fabian Gruenbichler } 
[cargo] cargo: Cargo is not able to build minidump-stackwalk
There is no source info for the package 'cargo' at version '1.62.1+dsfg1-1' 
with architecture ''
Unable to make a source version for version '1.62.1+dsfg1-1'
No longer marked as fixed in versions 1.62.1+dsfg1-1.
> thanks
Stopping processing here.

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



  1   2   3   4   5   6   7   8   >