Bug#1071059: mousepad: segfaults at each launch !
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 control: severity -1 important control: tag - unreproducible moreinfo On Mon, 2024-05-13 at 18:28 +0200, Philippe Caillaud wrote: > Dear Maintainer, > > I use mousepad almost each day for small text editing ; since a few days > (maybe > 2 or 3), mousepad > stopped working : at each run, it crashes (segmentation fault) : > Hey Philippe, I can't reproduce here, mousepad seems to run just fine. Some ideas you might try: - - open a new file from the command line instead of just running mousepad - - try with a different user - - try with mousepad --preferences and try to tune the preferences Also try with gdb with debugging symbols installed maybe? Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmZCaMcACgkQ3rYcyPpX RFtBuwf9HO5l36+n8GawA4mvDAwah4ui8C4R27Ed7ly1e3GbMMp4a8RoZJlMoWUv 1S6VrbL4kaePF3PvLWeCY66oQ4WJxLGssa9+R1ciX59fjukUP64ToA3uy7pi5qg/ OUj79rmHLbzE8m+uFDd2JQe5xtvSDjTuXnXUdiUcb2dv4BFDoCh/CSpJ8ppFD5Nq 59W1R8fQ0+Ya3GoGy5lPcLypsC/hxoRPWPUdR83W51naNsKOTL/P7R6TJNl+kLFd BlgblvGtDlGxfwid721KvLaGuoniwBFbXHMTz9/TZ6u3DK0ZuKMGtSde4pfNfiyL fvmsm3wzzt1Qw6czO7jtWqQftS55Hg== =PTrV -END PGP SIGNATURE-
Re: Joining Xfce effort
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Mon, 2024-04-22 at 19:01 +0200, William Bonnet wrote: > Hi all, > > I am a long time Xfce user and experienced with packaging even if i am > not (yet) a DM. I would be very happy to join the xfce effort and help > with the various activities (packaging, bug fixing, documentation etc.). > > I am not sure of the best way to get in touch. Sending this email to the > list seems to make sense to me. Please don't hesitate to point me out > the right procedure to apply and prerequisite documentation to read. > > my salsa username is wbonnet It's Still 'empty' since i am only now > starting to apply to a few projects i'd like to contribute to. > Hi William, reaching out on the list is a good way, we can also be found on #debian-xfce on Libera chat. We don't really have a beginners guide, and the best would be to do stuff that you find fun/rewarding. On more *needed* stuff, something not always fun but really useful: check the Debian BTS to for old bugs and maybe check if they're still reproducible, check on upstream trackers to see if it's already reported etc. And maybe dig patches and submit them as PR on the various repositories. Regards. - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmYpLOcACgkQ3rYcyPpX RFujGQgAw5ziVAyE5nOE7PtFMDmTmSWYaMGgq6mugxWj31zaAUdLO9/c5wW7PkPq +rgFe4cB20BhfLwG4ddnfIAcJITx4x+EYbjnFRhI9+DJ7wzwbrB7c8OEX8/AVOxj ebzxgW642npje/5o4DmQOJIvE4EZbLPYie8Sic5QxVPc5oO+qkTYMgcypIlQnX6a z3BYclh/JM9F5Ymifyo/nn2lpTPGG0s9TvIV7pmTz+LW1vzVD2gNIUeqVfhw/Os8 nqHU98VoUGVnIl8+pMmfyqwnk9wgKNm8RF0UlChWKdFzmAv3FuCyZOKRK+g1ZCH5 lyfjWzMCmCzIOUVrg3Szwo0EgEZPPg== =NZNp -END PGP SIGNATURE-
Bug#1067561: FTBFS: Error: symbol `open64' is already defined
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Fri, 2024-04-19 at 00:01 +0100, Peter Green wrote: > Thanks, upstream has now accepted a patch that takes a slightly different > approach to fixing the issue. > > https://github.com/canonical/lightdm/issues/352 Yes I saw. That's why I think this should have been reported and talked directly with upstream, before the NMU, but eh... > > Could we get this uploaded to sid, so that the lightweight desktops > are installable on armel/armhf again? Yes I'll look into it. Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmYiRuIACgkQ3rYcyPpX RFsQkQgA1h8bIbWp0Sj6VqgcdG/dkwKEQ6Xrcuh6gpL7Gy2BiT2d1tY4HFN94bhG FJVz9E9QOqlZt2Mo7JQ6EBYyvcTspO0T09ZU/22VjA2NdP0eSRHTiyiFXq4hyoYf OBnPpKTxq0Wp9L7Tefta7uNPIBX+lsVlw9cdwv6PIEy6jlF3xjX+B8FoK/K/fIeY FuQh5qOw/k/nnPAM4pHxYGAfRw+BNBEnI3ADFCCWDvpQSgZ9uJ9UB3wnEo50aXub dsNsXAZx3UIX2CfDBs1jXsPc/B37csOr9sJIqDn1xJKaT/Q6Yk1A/LV8uTa38wGh MykmdfDqWLT0nK4atbVH5fxjkTNdDg== =Fysh -END PGP SIGNATURE-
Bug#1067561: FTBFS: Error: symbol `open64' is already defined
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Sat, 2024-04-13 at 16:11 +0100, Peter Green wrote: > > Hi, thanks for the patch. It looks a bit strong though, undefining stuff > > like > > that unconditionally. Do you have pointers to the Ubuntu bug or something? > > I've looked at upstream commits and issues and couldn't see anything > > there. > > My understanding of the issue. Hi Peter, thanks for the details. They really should be transmitted to the upstream maintainer so I took the liberty to copy/paste it to the upstream bug at https://github.com/canonical/lightdm/issues/352 Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmYcLKoACgkQ3rYcyPpX RFvszggAuBC/jVutExKct2P2GNDoxIG8UHEkD0q0nZwzY3ojcVYF4Za4+g5i9HyJ khWQgqXzwxA5aWvOn4/lxo0CUd3LyzvKf4c1bP5wEX6LO3WZmOOAwDMQSdGfF5/k jZ2tDP212sS7WRhc8cUqTagKww90WJ8O9MfhusOSzhjimArxeM5XkO2CTmKZI7/0 eU+VTahJxaqyOp8LNNVrqyJHgdkr1LdWL67crixf4sPrkIKfcibYleoaiG0pK/Oq hcm7iV956GEFTa0VIYhuskTjB2TopA85UsGNTLYMGWtS7+XZbLirpuE8ToUqVeQ2 lm5douVLT78wjf4ZBbUq58wn499Q4g== =AAyB -END PGP SIGNATURE-
Bug#1067561: FTBFS: Error: symbol `open64' is already defined
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Fri, 2024-04-05 at 11:25 +0500, Andrey Rakhmatullin wrote: > > Hi, thanks for the patch. It looks a bit strong though, undefining stuff > > like > > that unconditionally. Do you have pointers to the Ubuntu bug or something? > I haven't checked their bugs manually but the changelog entry doesn't > close any: > > lightdm (1.30.0-0ubuntu12) noble; urgency=medium > > * Undefine _FILE_OFFSET_BITS and _TIME_BITS when building preload gadget > to > allow interposition of open and open64 to work. > > -- Michael Hudson-Doyle Fri, 22 Mar 2024 > 15:08:46 +1300 Thanks, I've forwarded upstream, hoping to get their insight on this. Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmYPobQACgkQ3rYcyPpX RFuS/wf9GL2qVFHO2p9o7RusyuTFQYUxUQL/GsGCRXirSGPAV7p3n84NgZuLP7s0 exqt/MLArwQcKKejkKHWZE/BppUX72UUdCzIKM31PSZTsmfNvaZyomfO4NIYTzrM UBTCGdp/xA0nIjzHNjAyABLFsCunxVCodGIF3w2fnvcc6t0/RZKh8clsAUMgKKGx yfRhyuW+YyapuWAx1gXLOn1uL8C2K/MFnyGYilvv/8Fe10tt+HsOmRQygXKDOzHG NVHpcIL8beIR4yeLBzCu2/U255955I2RGTIcNP1mLkPfzGt9IiVbP9HdsXt/ZXTD OeePyswwLEdntKNJcjnn20MPpKPTHA== =s7QG -END PGP SIGNATURE-
Bug#1067561: FTBFS: Error: symbol `open64' is already defined
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Mon, 2024-04-01 at 00:37 +0500, Andrey Rakhmatullin wrote: > I assume the following patch from Ubuntu fixes this: > > --- a/tests/src/libsystem.c > +++ b/tests/src/libsystem.c > @@ -1,6 +1,9 @@ > #define _GNU_SOURCE > #define __USE_GNU > > +#undef _FILE_OFFSET_BITS > +#undef _TIME_BITS > + > #include > > #include Hi, thanks for the patch. It looks a bit strong though, undefining stuff like that unconditionally. Do you have pointers to the Ubuntu bug or something? I've looked at upstream commits and issues and couldn't see anything there. Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmYPlZEACgkQ3rYcyPpX RFtkIwf/QZUtuSvH9DPGorTFJ/RybRfdEYONU8kLD8dOFGTXiNRcQYmSCTU/fH5B 4h0VxRWFXlF8TfBN0LmvgM+Rqzx9bT+5ZR+h8SGXL4UvH/W1qPeKIEOYYCmTtFMo nI9TBJhc501maa4PolJXSJ/OYO4AAQPmKvo+kAq0X7eTCaZcN5q1AleRDY5dBmru lHoQXy+L7T2+5N+L8wo7I7rAjLbrTEKH6CkYjNNTZx23Tp/Q6bLRELUg0f4XUusb xfAjR53aav/jCXJ8pYKKYWp60N2uRGPQcw05npjM314YlZlDXPyGn3xHQuEmQfkZ jRYE5mAmrHbtOplP9P49XX4W6cjZBQ== =9cvf -END PGP SIGNATURE-
Re: Bug#1056704: Major Dependency Bug in xfce4-panel-profiles
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Mon, 2024-02-19 at 17:25 +, Faulk Johnny wrote: > Has anyone taken a look at this fix by Phil Wyett? It seems straightforward > enough, I just question what stops it from being merged... Hi Johnny, xfce4-panel-profiles is under the Xfce team umbrella but maintained by Leandro Ramos . I'm adding him to the CC: in case it helps. Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmXTqa0ACgkQ3rYcyPpX RFsx9AgAlHhM4dyNoDIGND70ZDMqrzAXcYNtRTQKjDfYo6/NYbxbd5kLKzeLk5cD IYBBpk0V37fsc+M9ujzLKZ1VuCAMkHpeN+RFbiAXENsIHsA1QdsFzjl24Lcn6PQk weczMxOr7tOv8u6a+7Q5rMxtgnswFQEOdl+IdpRBjYQ7E7e7BH5vw9RXfR3ircMC KKVZf2WhlPo7F7cCVF1FjxOkS9cR7+YLpjbGZ0bDTEgGCkXtvGWVjuckKgThOdvf WTHbRNrbz1i4E8nmsQ4LUKZdoWMakP+jy+HfSqIyRuvJ5LGwxbfcCjnRDQz8Wsm2 gGb0atvmx7Lb2nqN1LL8GU1M5RwBOw== =Hy7N -END PGP SIGNATURE-
Bug#1063661: xfce4: "IBus Notification: Keymap changes do not work in Plasma Wayland" but this is not Plasma Wayland
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Control: reassign -1 ibus On Sun, 2024-02-11 at 14:42 +, Simon McVittie wrote: > > Yes indeed, that's really weird. I'll try a live 12.5 cd at some point but > > if > > you have one handy can you run a dpkg -l |grep '^ibus' or something? > > No need for dpkg -l, > https://cdimage.debian.org/images/release/current-live/amd64/iso-hybrid/debian-live-12.5.0-amd64-xfce.iso.packages > says, among other things: > > ibus 1.5.27-5 > ibus-data 1.5.27-5 > ibus-gtk:amd641.5.27-5 > ibus-gtk3:amd64 1.5.27-5 > ibus-gtk4:amd64 1.5.27-5 > ibus-hangul 1.5.4-2 > ibus-m17n 1.4.19-1 A good, indeed. I'm reassigning to ibus because the message is at least misleading. Ibus maintainers: on Debian (Xfce) live images for 12.5 it seems that at startup ibus outputs an error message which shouldn't be there (no idea if it should work or not, but at least there's no Wayland or Plasma involved). > > At a guess, this is probably here because task-korean-desktop pulls in > ibus-hangul? But that has been the case since at least Debian 11... Maybe. > > > I don't really know why it would suddenly get installed but maybe some > > dependencies changed in 12.5. > > I don't remember noticing this when I helped to test XFCE live images > during the 12.0 release, but I also can't say for sure that 12.0 wasn't > affected. Ok. Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmXI+x8ACgkQ3rYcyPpX RFt6lgf+JTSF38jWL8y+Rd6qZVs9fIQ+dMQHGTFJwfN36oNNRxjJqlRIp31HOdkM nEPQa7iisCK4vMjmCJ9OHIuaLr/peCR0HuJm6rbxi8CWlJQ0z2GHjJjtBU6mdYPR E2BjmC/grMf6psIk6h4eoLqcuHQWTxHikaRXIiy4xBLZcSQaA2/KdIOHDnaqyhJ4 TY2P+qsHwoDKidfXI6QcKVkzd/T/A6OG2NuMYPsojb/LI/MUz/OTiIFQRi9N8Iq0 eHNJUPz29VxeegaQjUCIWjHXxH8Jyoc5tK1PjlfkoIgeeok6A6Ek9ywb1Flogp+E lr1AthvYLeFws21deXJ2EgiWJuI6kQ== =qQew -END PGP SIGNATURE-
Bug#1063661: xfce4: "IBus Notification: Keymap changes do not work in Plasma Wayland" but this is not Plasma Wayland
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Sat, 2024-02-10 at 17:22 +, Simon McVittie wrote: > Actual result > = > > I got this notification popping up (screenshot attached, transcribed here): > > IBus Notification > - > Keymap changes do not work in Plasma Wayland at present. Please use > systemsettings5 instead. > > It seems odd to get this message when I'm running a non-Plasma, X11 desktop. Yes indeed, that's really weird. I'll try a live 12.5 cd at some point but if you have one handy can you run a dpkg -l |grep '^ibus' or something? I don't really know why it would suddenly get installed but maybe some dependencies changed in 12.5. Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmXI1cEACgkQ3rYcyPpX RFukPAf+OKNnShjvh0I7idVmtNEZXKe5GEEgAGH//rxhbgKqR7g4kMmg29upevkS TGG/EjJb5Q/wDzeHUlYtJimhusNz5/HDVyGFDD44zogRkmbG9XwxrE4QlfT6EFV8 MxrglS1YXV1pGOwi6DpyTzuh6UUhbsO/9FnMFABL1NlvkkqqR6JD3bdnjq+kHTph n9viydvZjTwAQBHHF51DzauoeBwAHBRjObzp9lv5XUBx0Lcht9I3KxjzluA1V6MQ yzmQRVB+FE7xs5LVV414zsS7Q3ob2ysSCtZfPcC4K9tKx2tkWTXwhNaMKO9qNdb3 NF3YwNUfHGdOF5pWLBlIskODv096pw== =Gc5X -END PGP SIGNATURE-
Bug#1062783: libxfce4ui FTCBFS: fails running gtk-doc scanner
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Mon, 2024-02-05 at 20:38 +0100, Helmut Grohne wrote: > Is this line of reasoning convincing to you? Yes indeed, thanks for the explanation then. I'll import the diff to our repository. Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmXCi3YACgkQ3rYcyPpX RFt4dwf/bXtVCuA9JN+o5DvMscBqVph819yDX7yz3FJJHmDxGOEJpm8qexb/buP1 I0KDPA5AVrEtMpDkJUzRfggg9wIjG1vEo//pIhEPrSZZdTnBA59aQe/2tKnfItX8 7JRORtZQ8AG3wvHg5ZfUXDlSqXgQyGFjD7doNpVpgGvUXEHcGJH5jO07OXI6UgYK OgnGsMCPxhjYlOOhZHubfzVra59i2/8B0QZicNqsA0PtTFsw7hsLbXO/jGa+dRft tbET8DzwYCuO8sjAqEMQY6z6+k0uWp3JwjjVGhaaRtDYbg4xaiD3J8Z2C7Lj5s9h uiLFEE3RHiFcIGcHR1ehXpBOm6DlVA== =f4R0 -END PGP SIGNATURE-
Bug#1062783: libxfce4ui FTCBFS: fails running gtk-doc scanner
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Sat, 2024-02-03 at 10:34 +0100, Helmut Grohne wrote: > libxfce4ui fails to cross build from source, because it fails running > the gtk-doc scanner with an Exec format error. This is fairly usual. > Fortunately, it also splits out its documentation to an Arch:all > package. Hence, we can disable gtk-doc in arch-only builds and thus > side-step this problem making the cross build succeed. I'm attaching a > patch for your convenience. Hi Helmut, thanks for the report and the patch. The patch looks small, and I don't know a lot about cross-building, but would it be better to use something like: ifneq (,$(filter cross,$(DEB_BUILD_PROFILES)) inside override_dh_auto_configure to only add gtk-doc when not cross-building? Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmXBAXYACgkQ3rYcyPpX RFsBbwgA6yOREFfPDlNddwz6VZIYSF0IfxZ5/A5R5QB3xu+Nxx/ZYDl5XcSxALvQ 32BRjN1+cpubRj4R1h5yJ8RN3ac+ykz0PI7TmPw7zmYodJ0fYP/aCiONJZbIbuP5 4PAR9VLfI0EZ9Du7ArYuhN/bz//MXEO1ruHHl2nEigWzzPJinu3FUWIp42U5vI76 VfYSNz3mH1gFk0rshwMqsOx3Uokb5r1L+egGV7AwL79qJqXabMGolyMwjEzEWC23 +SmyY0NWaPwJBOSDTQ2Ren3lMeRE13FlowwQ0KzclDqEHNcZqlcBalC5d3iKzfLm ng5eQv8ht3WwkwW6vVDPyqc2VE0Wag== =h+YT -END PGP SIGNATURE-
Bug#1062998: tumbler: NMU diff for 64-bit time_t transition
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Mon, 2024-02-05 at 00:28 -0800, Steve Langasek wrote: > Well, to clarify, the patch I sent was against 4.18 in unstable; but it > applied cleanly to 4.19 in experimental (no new sonames in experimental vs > unstable), so it's been uploaded there. Ah ok. > > When the unstable uploads happen, they will be based on the version that's > current in unstable at the time. Perfect then. Thanks again! Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmXAne4ACgkQ3rYcyPpX RFs90QgA6yqQzb/h/MoSrQIPHxjPi+eU/LdgYfQlwvdXTeCWzoMmke8QHp0f2jQE 00j9LuD2TvnSPzcvBR0ZH7GYScJt+LQabIjmehCC8FmmgB+hrXwNEZussHNVl56i D+JFG5AHXohP2G+c+0LBB0u78Y+c10oweq8INh9/t2ZZO5jp366jiLTbKe1C6jq7 NRwioJa1tNIRlm3sebqJW59VdRdbybG0Q5WRZEYXg/+EmS34MZykZYyOhjpOBJ/E HzWyA48Itc0uj4juX8j/9nYu4mDPpFMUCQgNA4eY5V4b2HuNxN5j/T66YpsSw9nM XCImXWgkiGn+UMeFrqqSoX1EmatArQ== =Apdm -END PGP SIGNATURE-
Bug#1062998: tumbler: NMU diff for 64-bit time_t transition
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Sun, 2024-02-04 at 11:14 +, Steve Langasek wrote: > > 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. Hi Steve, thanks for the work on the time_t migration, and thanks for the diff. I'll import it to our repository, but one thing worth noting is that the diff is for the 4.19 in experimental, which will be part of Xfce 4.20 in the future. We don't intend to upload 4.19 to unstable at all, so tumbler will stay at 4.18 (4.18.1-1+b1 precisely) for now. We surely hope that 4.20 will be released before any freeze happens, but if you need a coordinated upload to unstable it'll need to happen on 4.18. I guess we can “backport” your changes to 4.18 and upload to unstable once the go is given? Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmXAm0sACgkQ3rYcyPpX RFtKcwgAtoccvc0XqV4QhpEJdoSvXE9v4hpAlDI2h0eA9fkwr0eWJFNullmSKHZZ iQeNSU3EVwcrG0vDJD6LadB2NQqyEYne4m/UmFqGvn3194aTBo2+0f+pIA0GV/2q wW6Vjj9ObMSJGIeSRGmaiyttofsqlLM/ElbosJf8pQvxmdwpKbAm9ocqAPc4tDGo Zp0gZnCNYsEGgjF3nG/t/PyFIwh5QBfyJhUD3/yw62vp8kFVX9/77UWWjUgpUpA5 QSGR4MQDPAiEK0JVhVlkedl+Bf8G7Qh+gLUTdAJSsMMD8BKuX+xcFASISHpEW0t4 iackjFr5lq9XZ+hZOVIGXDVCETZO9g== =+nIU -END PGP SIGNATURE-
Bug#1059787: src:xfce4-power-manager: fails to migrate to testing for too long: uploader built arch:all binaries
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Mon, 1 Jan 2024 11:31:38 +0100 Paul Gevers wrote: > Source: xfce4-power-manager > Version: 4.18.2-1 > Severity: serious > Control: close -1 4.18.3-1 > Tags: sid trixie > User: release.debian@packages.debian.org > Usertags: out-of-sync > > Dear maintainer(s), > > The Release Team considers packages that are out-of-sync between testing > and unstable for more than 30 days as having a Release Critical bug in > testing [1]. Your package src:xfce4-power-manager has been trying to > migrate for 31 days [2]. Hence, I am filing this bug. The version in > unstable has arch:all binaries built by the uploader. Unfortunately the > binNMU infrastructure doesn't support binNMU'ing arch:all (and DAK still > doesn't throw away uploaded binaries). Hence, a source-only upload is > required. Normally I do that (a no-change source-only NMU) for packages > in this state, but given the large amount of open bugs, I don't feel > comfortable taking that responsibility. > > If a package is out of sync between unstable and testing for a longer > period, this usually means that bugs in the package in testing cannot be > fixed via unstable. Additionally, blocked packages can have impact on > other packages, which makes preparing for the release more difficult. > Finally, it often exposes issues with the package and/or > its (reverse-)dependencies. We expect maintainers to fix issues that > hamper the migration of their package in a timely manner. > > This bug will trigger auto-removal when appropriate. As with all new > bugs, there will be at least 30 days before the package is auto-removed. > > I have immediately closed this bug with the version in unstable, so if > that version or a later version migrates, this bug will no longer affect > testing. I have also tagged this bug to only affect sid and trixie, so > it doesn't affect (old-)stable. > > If you believe your package is unable to migrate to testing due to > issues beyond your control, don't hesitate to contact the Release Team. > Hi Paul, thanks for the report, I didn't spot the error earlier. I mistakenly uploaded the _amd64.changes instead of the _sources.changes. I'm ready to upload a non-changes -2 rebuild, unfortunately it's apparently part of the ongoing perl transition (through libxml-parser-perl), so for now it won't build. Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmWeU8cACgkQ3rYcyPpX RFvcsgf+L7nOC9HmekQJxfTGLuIs6J/8TkO8c2sFZBhpDuTTEgJq6Fqvpx3+YdJ3 w0e5kBiXSM7Q1LzB4GG6GA8SHGhqqqkh84J1XXgQy6X1YoT+L9WlKG6PK4BigNK2 GsddQvbkOM8BvmuRnxkun7mlUKWR1vi65PtHfcHQu3NXswhNCiehkgIkwZ3FrDpt JLM1RzKmP1k4MnyX/cUFT/eKoJvpjkBP5Bmk9Xt9nDca9AQwnnLcXRlRiF2/rI3N i4xGDQUGgVd5QkSGlsWoAfDFkfnxKGMgsDIlwA3wtrjG0ZjKFOsFAKmwIwxpMAEW t/N6JloFRuIihK+amWmhI0N0IXin/A== =XMyS -END PGP SIGNATURE-
Bug#1050417: lightdm-guest-session support (via Arctica Greeter) takes a long time to startup X11 guest sessions
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Sun, 2023-11-19 at 10:07 +, Mike Gabriel wrote: > I just tested this once more: It needs to be > > /run/user/*/ICEauthority-l l, > > Without that line, guest login to a MATE desktop is slloo > (with error dialog about /run/user/*/ICEauthority, without "-l"). > > With that line, login is smooth, no error dialog anymore. Ok, that's confusing (unless there's a specific syntax weirdness?). I assume you tested with: /run/user/*/ICEauthority l, and it didn't work? Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmVbxBsACgkQ3rYcyPpX RFtyIQgA235A9IBEsi1H1NRl9VROuJSPFM8k4KTXrkbNMQ28pz+e24tnnfnbFXRa 55WnPtSzP96+420dKiUuYQgoL+BmZf4zQXT9o2YQDzdXVbFhtDpy+NW8B4rOQk0j EuaSwNcAXrE/QJsGMt0JfX9vIm+X8cHorYupHEy61kIAyzpRgU5K8fAUclV6vs2L RHbxja0HAXHCsoURKbVkEPJWo6LGX+fB7N1uJSGhFNfKJcYx1CDPJGgsGnuge7MV JrjyFFrCeHyCK/zqxQZUvBKH5roI+EEoo+eHuADhCJAwqc4L/+aHa90e+on1Z8il QEajGSWgyo3HGrymx2hCEHRVxolD9w== =omCC -END PGP SIGNATURE-
Bug#1050417: lightdm-guest-session support (via Arctica Greeter) takes a long time to startup X11 guest sessions
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Thu, 2023-08-24 at 10:25 +, Mike Gabriel wrote: > + /run/user/*/ICEauthority-l l, Hi Mike, are you sure about the `ICEauthority-l' filename (especially the -l part)? On my system it's just ICEauthority apparently. Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEyBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmVVIIoACgkQ3rYcyPpX RFvRNQf4nVUolt6huD76ZT4EcpvIDVyX4VJjZ3v5tMIxdnzWZMmSQpxsAQcgfljm zUzweJw0HczdKAbiP/0f9qDKWTEDUZ7IG7ORYz4S7V7ZCFz5IWt5x6V1styNWnlp wXFXTm7BG7tzM8efXIaW3OANyWg3ewBnLzeqW4hSjOccB14VHqioP++sHOXG9w0b ChWxCmR5jfd+wIPpluxvOVTcmMWZlirfTnc/nbUtUTa3LeBlBG+0butRQS+DrDjz ZYFVPpo0rT37WoX+Ll49kyXGDMg2J22yQS4obdS1D/7ltcVZYtcec/w9gf+5B89s 1pC8mvbWE4zYhA94YmqzYarjb9Pa =S4WQ -END PGP SIGNATURE-
Re: ANNOUNCE: xfce4-terminal 1.1.1 released
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Sun, 2023-10-15 at 18:51 -0700, Brian Tarricone wrote: > 1) We can put the new m4 macros in a .m4 file, prefix them with something > else so they don't conflict, and copy it into each project that uses them > and wants to do stable releases for now. Then those modules can run against > xfce4-dev-tools 4.18 again. > > 2) We can backport the new macros to the 4.18 branch of xfce4-dev-tools. > Since they're just additions, I don't think there's much risk of problems. - From my window both options would work but 2) might be more sustainable for upstream teams. Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmUtgBoACgkQ3rYcyPpX RFtooQgAo+5WVYSEgbcnXC2AhtqooXXHhVoOeqoYIjR3FXfJgIuaGGepUgyeqlU4 gZQqkX4waIwZMefZk6SN7RuyKZP/+3gi89JxsH70oV1D2PdtQ1D+pGjMzFryD+++ L1pRP7SPze+mUAngo5V19XJVr2JLC6jWNa9jR7eDMzHKNWoABolHDd1RrqD93ZfH VBWbCNH4aohDSM7vBfyAmIBmqpizc555LySmQAWkWMyTkE6vRVelQht4bemAnXSw 5mwtqi/3NtiWHWhO/JSziD51QTWbD4+DudUtGnwHx53oyuO+4H3l25sdMHmeqS9b TpES4mZtbA72Ji6UOKAbGhvCVeIeig== =5L5q -END PGP SIGNATURE-
Re: ANNOUNCE: xfce4-terminal 1.1.1 released
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Sun, 2023-10-15 at 21:08 +, Gaël Bonithon wrote: > > We have the same issue for xfce4-notifyd but then I assumed 0.9 was the > > development branch leading to a 0.10 release for Xfce 4.20. So we pushed > > it to > > experimental without too much fuss. > > Xfce4-notifyd 0.9.x are not dev versions as far as I know. Well that doesn't change the fact that we can't upload it to unstable now :) > > > Well, if you have it and it's sensible, yes sure. > > See the attached patch. Not all XDT_CHECK_OPTIONAL_FEATURE features are > reproduced, but it should be enough. And since it has a limited impact, it > should continue to apply until Xfce 4.20. Thanks, I'll try that and report back (also, no need to encrypt direct mail, since it's sent in cleartext to a mailing list anyway). Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmUsY4cACgkQ3rYcyPpX RFsCbgf8DZyS9lodlomYD9TmhfdHO+cEJ0t/kyza1kEiCfAvZY8EKyKPgbT1Uqch Sw5C9KM4Cx2wwIK7rH4FxaG+cdu1XzWy7kwRfWiy7Z5MtXGHKRK3SVgfTkh86pEE ht1RTid6An2QhaFTWEjhjH+FB/KKB+hERiVE7tAtoBHeR2Dv5GLI+48DcAnFkWQN n10uShfl6vMWdDQF3vJKvX6SEAGZY/+W+mZ1WoliqLfMUoZeMHUmQ6sA0QRHpuW5 tqOoSG2BAUY5gZ4qMq4o3+4viWOs3y4VjTnZktrOWxjP5b5O95loe1fsbd6WCcS0 LR+IVnv6GWxO6BfM823a2TEw8o2ang== =QZ8z -END PGP SIGNATURE-
Re: ANNOUNCE: xfce4-terminal 1.1.1 released
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Sun, 2023-10-15 at 15:39 +, Gaël Bonithon wrote: > Hi Yves-Alexis, > Hi Gael, > It's definitely not something I was expecting, but I have to admit I'm a > little embarrassed to revert this commit. As said on IRC, I saw that Brian > had also used xdt 4.19 for xfce4-notifyd 0.9.x without anyone complaining, > so I thought it was fine (after hesitating to use xdt 4.19 right away, it's > true). We have the same issue for xfce4-notifyd but then I assumed 0.9 was the development branch leading to a 0.10 release for Xfce 4.20. So we pushed it to experimental without too much fuss. For xfce4-terminal it looks (to me) like a stable point release so I was surprised. > > Note that this is only a build dependency, which is only bumped to be able > to use XDT_CHECK_OPTIONAL_FEATURE(). This doesn't pose a problem on Arch > Linux, for example, which doesn't package any of the development versions of > Xfce. Even though I know Arch isn't Debian :) I have no idea how packaging works on Arch, and specifically Xfce. But in Debian we basically run the autoreconf thing so we need xfce4-dev-tools at build time. And we can't build-dep on an experimental package in unstable (or testing), so that's why xfce4-terminal would have to go to experimental as well. > > Would it be possible to apply a minimal patch (which I can provide) on your > side to bring xdt down to a stable version? Well, if you have it and it's sensible, yes sure. Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmUsNSAACgkQ3rYcyPpX RFuXcAgA5XvQO1161PDYxbhO9EaTz1zeljUXDewNAFUtWudpo6bKR/NpdSN1Bnay 5rh4lZSzjVWizcQcSGjFNvkltdz21HBljbnpy91DJvfbZgTDaZcW+yv2kCsEF7lL UnQzMNRotpdxHPoyEgfMwpdWlSmBhNyVhfUh+MEJi5S+hGIwsWu+/daCKsyiH7yS HR4VCAIf7asJ1L0poeiN2s3Bk83txaJehsftELHLO91XxsVQa5x/Zr3j2I0B8xBJ RSwSG20SfAmw60+JREspMbe7C8M9mCqcCAixm4JbFE90JzI86XBy/oDZvVPMLWt6 bQkCbSnhFTOBtkxtCK/hblye6BsVZw== =Zsvh -END PGP SIGNATURE-
Re: ANNOUNCE: xfce4-terminal 1.1.1 released
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Sat, 2023-10-14 at 13:08 +0200, Gaël Bonithon wrote: > - build: Simplify and clarify X11/Wayland distinction Hi Gael, just so you know: it seems with that change to xfce4-terminal, it's no longer buildable with stable xfce4-dev-tools, and it will require x-d-t 4.19, so development release. For Debian, that means 1.1.1 and later will be restricted to experimental and thus have way less exposure. It'll be uploaded to unstable once 4.20 lands. I'm not sure if that's something you expected, and preferred to let you know in case it matters. Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmUr+koACgkQ3rYcyPpX RFsyIwgAyMDlped/UN6weAigyX9yw4k32sTPgg1DH8jE7A/KJx0iY8A/uFB2+2dm xonmXmHtjpguLKMX7l9+Ok/fuJIOU4MDUiUOFV6ozCphs37M3yCbxcdQInaWJsGU E2d6+F95pWbYKWSrr4sOe8HZBh6YenpEZ3IOD1dZRSKfyEcayBYB766KxQDTPg0e Nlpi6fMpZ5XTVtCJw4cqGhB/EveUCroYR6G1cQuLCwCSMRShPxYBhdnQbEJZjBXr L8c85/jPyAlEes6Bad/1DV1PFtD/lX6UDbYzlYMfEeI6SH1KQ5agXn1rA18qLjZq SmYkq56HsLgs9v9E9fd89XIML92dlA== =/A2J -END PGP SIGNATURE-
Bug#1038611: Help with investigating a bug in the LightDM/logind/DDX stack
On Thu, Oct 05, 2023 at 01:06:43AM +0200, Michael Biebl wrote: > have you checked if the graphics device is properly tagged by > > /lib/udev/rules.d/71-seat.rules > > udevadm info /sys/class/drm/card0 > → E: TAGS=:seat:master-of-seat:uaccess: > Hi Michael, thanks for the tip. I'm not the one experiencing the bug, I'm handling this as LightDM maintainer. So I'm adding back the bug and the two people who were experiencing it so they can test (especially Adilson). Regards, -- Yves-Alexis Perez
Bug#1038611: lightdm: Lightdm fails to start X after upgrade to 1.32.0
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Mon, 2023-10-02 at 16:09 -0300, Adilson dos Santos Dantas wrote: > Ok. Running the command "loginctl show-seat seat0" with lightdm 1.26.0-8 and > this option above: > Id=seat0 > CanTTY=yes > CanGraphical=no > Sessions= > IdleHint=yes > IdleSinceHint=0 > IdleSinceHintMonotonic=0 And does LightDM starts correctly with the greeter? - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmUbGlIACgkQ3rYcyPpX RFsO8QgAtbR7v03OgNuubCD1/IK8s/quSCltCg9ctR2vWLwK8sPIUkQjx6PFv7mV nrrS/OpCU5O2ihj/7qdARhHEulLDsYwg6eosOvRccjoxYtwSdSkNR5pBU9WqWQKR 2kZqunQfcsOlMPcDbULy1QMR636f2U+oA836tUulvjBj1KS9nVoIL1yBjHdC78jY ln1xv4x3nx+/KWbISeHfSVfNnxAXhnEH7jKyoLJ6MR6xwgon48GGpLuFqhgQpz4T UbZ12PA0t9zC/YJn2MxFP7Z3HJlXTW5NNhzrBbDmT6F2vciWNdghePq1FGY7yMWV xz7Us8AyE3flcZWNmHCesqr4L36O8w== =U+h1 -END PGP SIGNATURE-
Bug#1038611: Help with investigating a bug in the LightDM/logind/DDX stack
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi systemd/logind maintainers. I'm reaching out to you about a bug (#1038611) reported in LightDM which is likely somewhere else in the stack (maybe in logind or maybe in Xorg or the DDX). With the update to 1.32 some people experienced an issue where LightDM wouldn't start. At first it seemed linked to people using NVidia binary driver, but we also had one user on a RaspberryPi 4. Some investigation linked that to a option in lightdm.conf whose default value changed with 1.32. That option is `login-check-graphical` and seems to check if the seat (reported by logind) is marked as graphical or not. Adilson checked and indeed on their installation seat0 is not marked as graphical: > logind-check-graphical=true > loginctl show-seat seat0 > Id=seat0 > CanTTY=yes > CanGraphical=no > Sessions= > IdleHint=yes > IdleSinceHint=0 > IdleSinceHintMonotonic=0 I'm not sure why and I guess it's a bad interaction between logind and the graphical system or something, but I'm not too sure how to investigate more, so I'm adding you to the loop in case you can shine some light. At this point I don't think it's a bug in LightDM but since I'm not sure where the bug is, let's not reassign just yet. Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmUbEUcACgkQ3rYcyPpX RFuqdwgAkPorc8enxSgGWMBQI+kbX+RX76fQQSxgjN/UHdfkToHFcvZxjUi8uryv J/t6cCUrH9hrs1lcxZDLcoHy5wclbhJ0f2TroUOvtrN5Hstb8dJsr4+uPKGs1Xnz nxfCR3GBl52+6TgPRjqq8/f09L9tOcOmRAjOtpXsnvnAABNZXOx6QWs7gzZ/IVza P4kq+UQBT4ECicySD7cEH0y7zpcEJaLFt7Blf2SrBHo79qMb5lRfheFsJ45lunLs uJ/ATODBMgec9DFAGyzuUbKwbRnkKYSldVlLpgA9KNxzzagUlEDCkfoBXpFE01F2 60yyKJ3I9p0f8duCDKJpY4WneKsMGQ== =Di8i -END PGP SIGNATURE-
Bug#1038611: lightdm: Lightdm fails to start X after upgrade to 1.32.0
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Mon, 2023-10-02 at 15:33 +0200, Yves-Alexis Perez wrote: > At that point I don't think it's a problem in LightDM and I don't really > think it's a good idea to generalize the workaround (and divert from > upstream). Just to be sure, can you test with: - - LightDM 1.26 - - login-check-graphical=true Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmUbEHAACgkQ3rYcyPpX RFv38AgA5qxC4JCT1rzmu8ibemyV21C+VQIY+W+TIXw/IOBnWOmZskFeBY7VXdvY 4+simhXUdijgULROQKSHmhefO+AXSBbLXU8CPM0n89O3FIr1Fjyraff/bj+NEZUZ FoNeSBdYI8jQ0PK5BE9zXEWgseMrCDXy3w9YmoZcliIB/gvjr2cdoeKo/9V7+1lA jTvILl5MoaHRywdLVi7F3VAKGrhVJzUJU+CzNFFG7gFEhfQIWb9vlZ9gfO+Os7bC +jsK91J5+hg8tPWBUGnVNNv8JjQusMUy2XBw6m0SzuUl8UhuaCZ+wmYYklryd0Hq h7YKEzgKNsM3Bo3kQMIqS8snTCt6/w== =MFQU -END PGP SIGNATURE-
Bug#1038611: lightdm: Lightdm fails to start X after upgrade to 1.32.0
On Mon, Oct 02, 2023 at 09:47:38AM -0300, Adilson dos Santos Dantas wrote: > Here are the results of 'loginctl show-seat seat0' from both > 'login-check-grafical' options. > > logind-check-graphical=true > loginctl show-seat seat0 > Id=seat0 > CanTTY=yes > CanGraphical=no > Sessions= > IdleHint=yes > IdleSinceHint=0 > IdleSinceHintMonotonic=0 > > logind-check-graphical=false > loginctl show-seat seat0 > Id=seat0 > ActiveSession=c1 > CanTTY=yes > CanGraphical=no > Sessions=c1 > IdleHint=no > IdleSinceHint=0 > IdleSinceHintMonotonic=0 > Thanks, so that confirm the issue on your installation: the seat is marked as non graphical for some reason (likely related to the graphics drivers but honestly I'm not too sure). At that point I don't think it's a problem in LightDM and I don't really think it's a good idea to generalize the workaround (and divert from upstream). I'll ping the logind/systemd people with a summary, in case they have an idea here. Regards, -- Yves-Alexis Perez
Bug#1038611: lightdm: Lightdm fails to start X after upgrade to 1.32.0
On Sun, Oct 01, 2023 at 08:58:32PM -0300, Adilson dos Santos Dantas wrote: > Hi. > > Here are the logs with and without the "logind-check-graphical=false" > option. > > With this opinion, a new seat is added and no seat is added when this > option is commented. Thanks for the log. I'm unsure if there's no seat at all or if the seat is marked as "non graphical" in logind. In both cases and before logging in as an user, so when lightdm is started and a greeter is displayed (with =false) or you get the black screen (with =true), could you check the loginctl output (as root)? I'm not too sure where to look, but at least: - loginctl - loginctl list-seats - loginctl show-seat seat0 Regards, -- Yves-Alexis
Bug#1038611: lightdm: Lightdm fails to start X after upgrade to 1.32.0
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Tue, 2023-08-08 at 01:25 -0500, Steev Klimaszewski wrote: > I'm running into a very similar issue as the original submitter, > however, when I'm running into it, I am *not* using the nVidia binary > driver, but I am using a custom 5.15.44 kernel for a Raspberry Pi. > What I found after digging for quite a while, was that, yes, > downgrading to 1.26 would start Xorg, and upgrading to 1.32 would > cause it to not start Xorg. After diffing the contents between 1.26 > and 1.32, it seems that the option "logind-check-graphical" has > changed from the default of false, to a default of true. > > Simply adding in > > logind-check-graphical=false > > under the [LightDM] heading in /etc/lightdm/lightdm.conf shows it as > starting again. This happened for me on both Pi3 and Pi4, armhf and > arm64. I'm not entirely sure why this is the case, and the kernel > hasn't changed on these devices since 2022-07-03 when we last built > the kernel for them. Perhaps the original submitter could also see if > changing that option works for them with the nVidia binary driver? Hi Steev and Adilson, so it might be linked to https://github.com/canonical/lightdm/issues/263 Looking at a bug linked from above (https://github.com/canonical/lightdm/issues/165) it looks like the default was changed in order to fix a race condition or something. The documentation says: # logind-check-graphical = True to on start seats that are marked as graphical by logind Could you check the lightdm.log and check if you have messages about seats beeing added and whether it's graphical or not (you can add logs here). With both value for the logind-check-graphical option. It looks to me that there's an issue deeper in the stacks (in the NVIDIA stuff or in the RPi graphical stuff) and maybe the seats arent't marked as graphical or something. So it's ok to tune the option locally as a workaround, but I'm not sure about reverting it globally. Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmUZgJIACgkQ3rYcyPpX RFtkzAgAvSJE1yDFRCZrdI/1zGTW/SWH2KUXuxpYw8b+LrwcvkLBVwSzQhkxKkS4 rd8VUjRRXVcaPXTrPJxeKqObAAYN2iUhiFCKdYAYUxdvlIPWxOkQEf8CeLm/AG6f rCaHMmQNZY5SFkTCQ5AGUzH38IAp3a4Sdn3E+x1xVMsiYGn6h5I/z0eDcx5135mP omuBRUYZGnoTfsApetBOQCK7pMzUJX1QRxdaiMjLZCUEsKjwoJc/6ZaLSHB4goYQ AXAYcrc4jOhYfv6KFqbaxEBWxR/gbdG8+YBh2u8a44KEniJgXl+T4FEKfTA1poxc muyLJuBzqpHqGyfOvZS73TjWPVZcHw== =Lrpk -END PGP SIGNATURE-
Bug#1049418: xfce4-pulseaudio-plugin: Please loosen Recommends, and allow pipewire-pulse as an alternative to pulseaudio
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Fri, 2023-09-08 at 10:53 +0700, Arnaud Rebillout wrote: > Hope that it answers all your questions! Hi Arnaud, thanks for the very detailed information, that's much helpful. And it does make sense to use alternate dependencies indeed. But here there might be some differences. In your initial mail you say: > 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. I don't think that's completely true. Recommends: can (and are, on Debian at least) installed by default (when doing apt install or apt-get install) but you can totally remove it afterwards. So I guess the only relevant use case is when a user - - has pipewire-pulse installed - - has *not* pulseaudio installed - - runs apt install xfce4-pulseaudio-plugin (or xfce4-plugins) In that case, with the alternate recommends I'd assume it would consider the recommends already satisfied and won't try to install pulseaudio. I don't think that's really what Kali is concerned about, but rather the default installation. I'm not sure how Kali does it but afair on Debian the initial installation (using d-i but also I think when using debootstrap or other tools) doesn't install recommends by default (because it still uses tasksel). In any case, the recommends shouldn't hurt us so I'll add it at some point. Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmT6yY8ACgkQ3rYcyPpX RFunCAgArhnM9JAKh/I0yj/sbGjuMPVTd3nZzjp66ldqMLDi726oWIsgeQ6/8iQ+ h+kXpQPJ9z/4+X3J/in7uc1nTHSh0NpJBSbN72jgpLvvHyKJn+OxWGyuqpCgchhE Iq3go4yUE4+dWUQfqpLk5P1j4QmtYuHtMr6F5XxWzY29yFKIv8nxBPBnVanihsYj mbIRed3DlDiKPTn/ExBqAHbmCf2vJk078hqmtRwrqGhmDnuoyLxe/6GGdwQxey1z SmGhIbpoaFVCdp8yJmSKEwDkR5qOqWK7yf4RUbsAxcvvt6ZE0aUlfHCqVU1U0iUn 0zTrbPa/72fLOe4CQmKKaMoFXtewEA== =cy9F -END PGP SIGNATURE-
Bug#1049418: xfce4-pulseaudio-plugin: Please loosen Recommends, and allow pipewire-pulse as an alternative to pulseaudio
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Tue, 2023-08-15 at 20:09 +0700, Arnaud Rebillout wrote: > 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. Hi Arnaud, I have no idea what pipewire is, could you explain a bit here what it is? Is it a drop-in for pulseaudio or something? Because xfce4-pulseaudio-plugin is (by definition) really linked to pulseaudio. And if we have a drop-in replacement, does it really make sense to have every pulseaudio depending package to use alternate dependencies? Isn't there a way to centralize this change? Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmT6JLkACgkQ3rYcyPpX RFuLXggAsSGLse5tsY/463r+nLS6t5RVkIgIr3XLQHltMn5TINpXJIONAS38XXmT wqBAkj6oQcOJhj+5qjWtG8eH+eTtpPXhEb/l/1Sl2/7/Xi4QGtQ92ZiKF2lmKwfi uOZos/w9rPyotUb/2bXnFlXVlOoc2KCWfRRYHMwj5XwgnXsmm9WcKmUJw8LIH091 WC0tjIPmm4pT2DkrwZQ/vPgUNOt+2OCPooqmzfuJvucE37iW8tLA8EEJZjyKlduA PFIlT0czS30Y7C/kJrRzmcryqnyDKmPCtULR5LndiGx2hZojYrLfsiuXD/sbJkT+ VEdAF3NwYJ+lR2VCL83plPjiQ0HAig== =83EC -END PGP SIGNATURE-
Bug#1050802: xfce4-session: please provide an xfce-portals.conf for xdg-desktop-portal
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Tue, 2023-08-29 at 11:51 +0100, Simon McVittie wrote: > xdg-desktop-portal 1.17.x introduces a new way to select which portals will > be used for which desktop environments, modelled on mimeapps.list: Hi Simon, thanks for the report but I have no idea what a “portal” is. So feel free to provide a patch for that, I think it's unlikely we'll look at this soon. Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmT6I8MACgkQ3rYcyPpX RFuC+wf/YhTUai4ctNVzUJC7zPo9F2mgtmGLtOl3IFlD+YaTGtDztZuUIlFrNJL4 J9vIxLjYGtSsxpImkoHnj1lxnn0kX//Msj3cgmn8uyqRmoC0NIQr+Dz2bo8aD2C/ 0CsFeflqw20Q9Q2UEKdORppTtbmmosFCyfiyadhL94uSqYhFVC98HnVo7jc+qZoq 2DON8WKNgB4KGe+L4gNbEIV4t8SwhRXsjBx8FVSsE6xWrOjRwBL2MVf/krhxMryr eCxbC5/Zkb3+u3S5JPEyqhxctD1M3ulanTM42GUT1FUbL96c8YOLq9JwumpLYaBo QydscbTWY079TGnEH4oTWOI/MRF0Lw== =qTvF -END PGP SIGNATURE-
Bug#1039957: light-locker: Bug 1039957: light-locker: coredump from light-locker
On Mon, Jul 24, 2023 at 05:00:36PM +0200, Paul Gevers wrote: > Hi, > > On 24-07-2023 15:27, Yves-Alexis Perez wrote: > > so what you're saying is that you're a KDE user (not Xfce) > > Indeed. > > > but you're > > still using LightDM (not KDM), and light-locker is still started as part > > of your desktop session. > > I'm not aware that I ever did that actively. It seems that also nothing > obvious changed for me since I deinstalled light-locker. So everything > *looks* like before. Yeah I meant before removing it. > > > In any case, if you don't use it on your box it's quite ok to remove it. > > I tried to say in my previous message that I already did that. > Yes indeed, I was just saying that it was ok. -- Yves-Alexis Perez
Bug#1039957: light-locker: Bug 1039957: light-locker: coredump from light-locker
On Sun, Jul 23, 2023 at 09:22:41PM +0200, Paul Gevers wrote: > Package: light-locker > Version: 1.8.0-3 > Followup-For: Bug #1039957 > > Hi, > > I just found this coredump in my journal. Like the original reporter, > I'm a user of KDE (on trixie). I removed light-locker to see if I spotted any > change and I'm not seeing it yet. > Hi Paul, so what you're saying is that you're a KDE user (not Xfce) but you're still using LightDM (not KDM), and light-locker is still started as part of your desktop session. light-locker is autostarted using the XDG/Freedesktop.org specifications so you should be able to prevent it to startup if you have a KDE screen locker (not sure how to do that on KDE though). Right now light-locker autostart ignores GNOME and Unity desktop environment, maybe it'd make sense to ignore KDE as well. In any case, if you don't use it on your box it's quite ok to remove it. Regards, -- Yves-Alexis Perez
Bug#1037020: xfce4-panel: workspace switcher extremely wide after bookworm upgrade
control: tag -1 unreproducible morinfo On Thu, Jun 01, 2023 at 09:47:23PM +0200, Marc Lehmann wrote: > Package: xfce4-panel > Version: 4.18.2-1 > Severity: normal > > Dear Maintainer, > > after upgrading to xfce4-panel from bookworm, the workspace switcher has > become unusably large (wider than my screen). > > after realising this is not configurable, I dug a bit into the code and > found that plugin->ratio is set to 7.1, which explains why the switcher > displays extremely elongated miniature views - it apparently assumes my > display has an aspect ratio of 7.1, when it actually has a ratio of 1.78 > (standard full hd). > > I found that the ratio is calculated differently in bookworm's panel: > before, it was screen width / screen height (which is 1.777.. on > my system). Now it takes the workspace width divided by workspace > height. Since my workspace is 8x2 screens in size, this results in 15360 / > 2160, > or 7.1. > > So it seems to apply the full workspace aspect ratio as if it were a > single screen inside the workspace. > > I think either the ratio calculation is wrong, or some other code uses > this in the wrong way (workspace vs. single screen). Hi Marc, thank you for your report, but I'm not sure I understand and/or can reproduce it. Using a fairly standard Bookworm install with Xfce, the workspace switch seems just fine for me. I tried to configure the plugin to display using two rows, then added 16 workspaces (to get a 8x2 layout like you) but it seems to display just fine. Could you take a screenshot or something to help us investigate? Regards, -- Yves-Alexis Perez
Bug#1041353: xfce4: option to make week start on Monday not Sunday
control: reassign -1 xfce4-panel On Mon, Jul 17, 2023 at 09:13:37PM +, sr2f2c+b00m5anxhcd3k@cs.email wrote: > Package: xfce4 > Severity: wishlist > > Dear Maintainer, > > I am running my system with LC_ALL=C.UTF-8 locale. > > When clicking the clock on the taskbar, a calendar is displayed with the week > starting on Sunday. Reassigning to the xfce4-panel package which contains the clock plugin. > > I'd like the week to start on Monday instead, as ISO8601 defines it. > > Currently, the only way to change that is to install another locale on my > system, that has Monday as first day of week. I do not wish to have to > install another locale and run my system with LC_TIME just for the xfce4 > calendar to show week starting on Monday. That'd be the correct way to do that though. > > Please provide a new option to make the week start on Monday, independent of > any currently used locale. Since it's an upstream bug, could you please open directly a wishlist issue on their tracker? It's much more likely to be acted on that way. Regards, -- Yves-Alexis Perez
Bug#1040912: lightdm-gtk-greeter: greeter always uses Gnome (Standard) as default Xsession
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 control: reassign -1 arctica-greeter On Wed, 2023-07-12 at 20:49 +0200, Dieter Scheinkönig wrote: > find attached my .xsession-errors. > > My issue, regarding the login screen (See login-shot.png). I have to > change/select _always_ from "Gnome (Standard)" to "Default Xsession" in > order start my XFCE-session. > It changes always after login off from my session. In the past (Debian > 11), the selection, which session would be used stayed as selected before > login. > > Sorry, if I confused you. > Yes indeed, this is very confusing. Sorry I misunderstood from the start. And in the end, yes it looks like a bug in the greeter, so I'm reassigning there. Sorry for the lengthy process. Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmSu/nQACgkQ3rYcyPpX RFsWAQgA7dYT7OU7iqAheGHflI/l4awdYJ8zgavpEXEZmViX0kgDNsE0NX1cjfuf UkgvKxKfeCZDeocRMBYiH5Y+y0s5aOWDL03xiEkWraTWb8N0FIYhIU7d3UGBaDn3 xtcW4It6LWmvBoQaeiTTy6glbKBiehusLd9+jQV0pzidU4iWmjqLYX+h8s3RAY0p 0hWqPcITUgaN2aUWO6Lskc0kIxGijuxpk17rOYG6i6rMgD+b02xbtW+RdhLmy2Zi NYuYSKR/kgin0gIW8vzTG3UZ/QbJX/fl5ixrqi+41+r9uSb0g9MD1QUTcSGCVDHp OHWsR1lVG6kllmEzlTuHpEw4BX9CFw== =7rLP -END PGP SIGNATURE-
Bug#1040912: lightdm-gtk-greeter: greeter always uses Gnome (Standard) as default Xsession
On Wed, Jul 12, 2023 at 03:30:06PM +, Dieter Scheinkönig wrote: > Hi Yves-Alexis, > > I do not have a .xsession or .Xsession in my home directory. Ok > So, I’m using the default. I’m not in front of my computer right now, so I > would send it later from /etc/X11. Please especially send the .xsession-errors log (check for personal information first though). /etc/X11/Xsession sources various files from /etc/X11/Xsession.d and the session selection (if not selected in the greeter) should be done from /etc/X11/Xsession.d/50x11-common_determine-startup > > As mentioned, the difference between using the login between Debian 11 and 12 > is, before the selection of respective xsession (xfce, kde, gnome) did stay > after restart. Now it’s not the case anymore. Sorry but it's not at all clear what you mean here: are you using the *default* session, or are you choosing a session in the greeter and it's not actually selected? In the lightdm log you sent, you were using the default session. > > I’m happy to do the necessary configuration, however I do not know where to > search for. A “find” in /etc did not give me any result. > > In case it would be a bug, you would transfer to the artic maintainer? I don't think so, again it doesn't look like a but in the greeter. Regards, -- Yves-Alexis Perez
Bug#1040912: lightdm-gtk-greeter: greeter always uses Gnome (Standard) as default Xsession
On Wed, Jul 12, 2023 at 01:06:10PM +0200, Dieter Scheinkönig wrote: > Dear Yves-Alexis, > > thanks for the fast response. > > I'm talking about the lightdm logon screen (as on the screenshot of > https://de.wikipedia.org/wiki/LightDM#/media/Datei:Lightdm-screenshot.jpg) > Next to the users you have the possibility to select your session. This is > always defaulted to Gnome (Standard) since I upgraded to Debian 12. Hi, that screenshot is not lightdm-gtk-greeter > > I attached the last 150 lines from lightdm.log. > And the log confirm you're using arctica-greeter, so it's definitely unrelated to lightdm-gtk-greeter. But in any case, as I said before, you can select the session in the greeter but in the end it's handled by Lightdm itself. Looking at the log you provided, we can see: [+264.18s] DEBUG: Session pid=5587: Running command /etc/X11/Xsession default [+264.18s] DEBUG: Creating shared data directory /var/lib/lightdm/data/scheini72 [+264.18s] DEBUG: Session pid=5587: Logging to .xsession-errors So you're definitely using /etc/X11/Xsession with the 'default' parameter. You should be able to select a specific session if the desktop environment you use has it (for example Xfce). In any case, could you provide your .xsession-errors as well as your .xsession or .Xsession just in case? It looks to me like an configuration issue rather than a bug though. Regards, -- Yves-Alexis Perez
Bug#1040912: lightdm-gtk-greeter: greeter always uses Gnome (Standard) as default Xsession
Control: tags -1 moreinfo On Wed, Jul 12, 2023 at 12:05:01PM +0200, Dieter Scheinkönig wrote: > Package: lightdm-gtk-greeter > Version: 2.0.8-2+b1 > Severity: normal > X-Debbugs-Cc: die...@scheinkoenig.com > > Although update-alternatives --config x-session-manager is sset to start xfce. > the lightdm-greeter always set the defualt session to Gnome (Standard) > > Auswahl Pfad Priorität Status > > * 0/usr/bin/startxfce450automatischer Modus > 1/usr/bin/gnome-session 50manueller Modus > 2/usr/bin/i330manueller Modus > 3/usr/bin/lxsession 49manueller Modus > 4/usr/bin/openbox-session 40manueller Modus > 5/usr/bin/startlxqt 50manueller Modus > 6/usr/bin/startplasma-x11 40manueller Modus > 7/usr/bin/startxfce450manueller Modus > 8/usr/bin/xfce4-session 40manueller Modus > > I did not find any configuration, where I saw the this settings nor where I > was > able to change it. Hi Dieter, when you say "default session", do you mean in the top-right menu? If so, the LightDM (not the greeter) should run /etc/X11/Xsession, which in turn might run different stuff depending on your local configuration (check in ~/.xsession and ~/.Xsession). Could you provide logs from /var/log/lightdm and ~/.xsession-errors ? In any case, it's likely not a but in the greeter (whose role is minimal), but let's wait for more info before reassigning. Regards, -- Yves-Alexis Perez
Bug#910273: severity of 910273 is important
On Fri, Oct 05, 2018 at 04:14:41PM +0200, Olivier Berger wrote: > severity 910273 important > thanks > > I wasn't quite sure, but the impact is quite nasty, so raising severity > in the hope someone more knowledgable has hints on the likeliness it may > happen to anyone else in the next stable... Hey Olivier, it seems this one went under my radar for a *long time*. Did it get solved in the end? I never experienced this one myself. Regards, -- Yves-Alexis Perez
Bug#1039559: lightdm does not start Xorg
On Tue, Jul 04, 2023 at 09:39:56AM +0200, Christophe Lohr wrote: > Le 03/07/2023 à 21:54, Yves-Alexis Perez a écrit : > > On Wed, 2023-06-28 at 09:06 +0200, Christophe Lohr wrote: > How to know more about it? Honestly at that point I'm not sure. > I have outputs by strace and ltrace if needed. > I expected to see any errors, or attempts for execve( Xorg ...) or similar. > But there's nothing. Maybe share them so I can take a look just in case, but I'm not sure I can identify anything if you didn't > Are there any dependencies between lightdm and other components? (eg. dbus > plymouth etc.) There are but I don't think it should matter. Is xserver-xorg-video-nouveau package installed? If not, can you install it just to check if it does fix the problem (by not using fbdev)? Regards, -- Yves-Alexis Perez
Bug#1039559: lightdm does not start Xorg
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Wed, 2023-06-28 at 09:06 +0200, Christophe Lohr wrote: > X works well by itself. As a workaround, I'm now using gdm and Cinnamon (in > place of lightdm an Mate, which have my preferences ;) ) > (attached is the Xorg.0.log in this configuration) According to the log you're using the fbdev userland driver. Not sure why it doesn't work on LightDM though. - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmSjJ24ACgkQ3rYcyPpX RFsTFAgAkHUxrAgs4VWDbDOkm5NyCMLgPa29gRTuUaj2Qinkb5zxmWRgEFeb8Sj3 Xb05yRXy9BPWp6AOQMPTiqrkZsevJVr1uaIf1321FwHKNwOeg+Dt/KbxfZIItGHB KhZ2BtC+jPsGi1WmnzbgCaAT6Uh8zwm+ve4Se+ZeYRI/ojM6UkLIIMbXQPLXTNTp fJgsKPudlZO3UXh7KXeU7UTlsZ2klcjNl2bad3nQ5M6mFaNFGYJFVnVCvRhRNidk EHH36AzxUm1KHOkzUvWR1fLB0tGXOqpiUjpvitpIV5PpCfqdApfd/K/z3Zad0yQs +S5c8uda3B8IiBL+mqGcxBA2F4etkw== =xix8 -END PGP SIGNATURE-
Bug#1039573: cannot authenticate after lock: pam_unix(lightdm:auth): auth could not identify password
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Tue, 2023-06-27 at 12:22 +0200, Arturo Borrero Gonzalez wrote: > 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. Hi Arturo, it does look like there's something fishy from the "Invalid string length 1869348864" (which looks way too high). Is that reproducible everytime ? Is there something specific/peculiar about your installation? I assume you're using light-locker as your screen locker? Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmSbCukACgkQ3rYcyPpX RFvWuQf8C0PyAmDiSG3S0kgkVpfUO5amy5Q1Nn23KaSUALZsPyE4AAHvdw24K8RM C/FvwUNbbYw7PMoAfVeh7/Bc8cwYxitZ7/ZrCaD98eFTmadFijwWyMwi2OvxohJY cw30ztQhauyfYqp4DkHKMa/6dpRNyHLQjH/7hkqXK9Kg/CTcxJ41DBBepVQpxZTw Hkrw4+De14tWsh6JCRJ1ml8kNIe02YqCUamuAPUpjr8hMLjeNgdaw/FIaZWsqERk xxQTT7r8wS2GbWkb6vxSiMAhdGYLck2l1KtktrsDdPnyiCcIxd+Cxph0Dati0q+x SOZHZMatOJvjAGVOB2+VG+qqzu7ttQ== =e/LG -END PGP SIGNATURE-
Bug#1039559: lightdm does not start Xorg
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Tue, 2023-06-27 at 09:10 +0200, Christophe Lohr wrote: > 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? Hi Christophe, it looks a lot like #1038611. Could you check if it's not a duplicate, especially if you're using a binary proprietary driver like NVidia or AMD? Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmSbCTgACgkQ3rYcyPpX RFuwtggAyyj6ozywCru9way6JOrG4TKpM6nqe1nYFhNnoMXHXC3V9TI5p/nbLJYM xQ7QRjZh6BjSZ9iH+TknvIW3LBEBoJ5DEvUwvZHMNi+vq5S6gJ5+Ak3ceizuuSt2 llJ8G1W2Hlqfaxfa71OzH3Lp+VYkV2cx4CrsLJ7p37KDd9oadg/71Y2BmDsmkGtl RjM4akueN3O9/CtdQbcGO12PRab7P4DsRcs/FBs+0Gyd5skl5J+snJdcPB7tPAai ym5phuLFjPGQZdxWT6YrzPskpSLy2iaWvOF/RamCOSWb82F7+wH1N6CMHf33t9lM /auyadGWyu6KclG+lof4Kb4zqqQZ1A== =pPx/ -END PGP SIGNATURE-
Bug#1038611: lightdm: Lightdm fails to start X after upgrade to 1.32.0
control: severity -1 important control: retitle -1 lightdm 1.32 fails to start X on nvidia binary driver On Thu, Jun 22, 2023 at 01:10:41AM -0300, Adilson dos Santos Dantas wrote: > I tested with the nouveau driver and it worked. > > Maybe there is something between 1.26 and 1.32 that conflicts with nvidia > driver. Yes it's likely. > > And it is also similar to #996503 which affects sddm and it worked too with > nouveau. Ack. As I understand it, X doesn't even start at all so it's likely unrelated to LightDM or sddm actually. Could you try in a terminal to just start X (with the `X` command), with NVidia and with Nouveau drivers, and report back? > > I tried to fix this by removing some module options from > https://forums.developer.nvidia.com/t/display-manager-sddm-lightdm-not-starting-with-nvidia-driver/243992 > but it had no effect. > > Maybe forwarding this to nvidia-driver should get some hints about this Yes, feel free to do it and report back any progress. I'm lowering the bug severity as well so it does migrate. Regards, -- Yves-Alexis Perez
Bug#1038611: lightdm: Lightdm fails to start X after upgrade to 1.32.0
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Wed, 2023-06-21 at 09:40 -0300, Adilson dos Santos Dantas wrote: > These messages are when I stop lightdm. Ah ok. > > > > > > Also is there something peculiar about your hardware (Nvidia/AMD GPU for > > example?) or software (specific configuration or something). > > > I'm using Nvidia GPU: > > 01:00.0 VGA compatible controller: NVIDIA Corporation TU117 [GeForce GTX > 1650] (rev a1) > > And it is using its official drivers: > > dpkg -l xserver-xorg > Desired=Unknown/Install/Remove/Purge/Hold > | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig- > pend > |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) > ||/ Nome Versão Arquitectura Descrição > +++-==--- > = > ii xserver-xorg 1:7.7+23 amd64 X.Org X server > > dpkg -l xserver-xorg-video-nvidia > Desired=Unknown/Install/Remove/Purge/Hold > | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig- > pend > |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) > ||/ Nome Versão Arquitectura Descrição > +++-=--- > = > ii xserver-xorg-video-nvidia 530.41.03-1 amd64 NVIDIA binary Xorg > driver Yup, that's likely related. Honestly we (I) don't really support binary/proprietary drivers. It'd help if you could test with free drivers (nouveau or something maybe). Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmSTQAAACgkQ3rYcyPpX RFu7Ggf9FCsjsiXteQ+xDSolGEtK2a9eBlnCnI9MY3wY2OdOHJlNCpbEjamWVbw3 CwEn4//IWPgFmLcKBD1A9ySYein2tY3CDdNH5fii7ZZ/MNAlL1vuKAVuV30ayQtU V/4xxQXgJ+1JUCPzzKNGMdLs/yumAiLGAs3XzhjUmjVPQWMRWanCOf8dFavDyFG3 4sPS6niMeFUWqM17K0ja7VPVj2QbQQSe34jec93W+zcbnxbWZZuJY9nQ2PsQjRDd /FY0fBQtzopnZMBgRUdYNj09QGuI8kn6dZdD93+/MS2uP95ES7v1nG0bKARrGor7 pNaWlBMeMGI/+bL89SFEQdR52n/uFw== =tTX8 -END PGP SIGNATURE-
Bug#1038611: lightdm: Lightdm fails to start X after upgrade to 1.32.0
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Wed, 2023-06-21 at 01:59 +, solneman33 wrote: > I downgraded to xkb-data=2.35.1-1 lightdm=1.26.0-8 from testing repo and > reinstalled xserver-xorg and xinit. That resolved the issue for me on both > machines. > > I've never reported a bug before, my apologies if this is incorrect > procedure. Well, can you check by reinstalling lightdm 1.32 but making sure you have xserver-xorg? Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmSSnMIACgkQ3rYcyPpX RFs1Hwf9HgLiSwVwW4gMRS2ajXiUXmTRcgNe/jF5libmZllhhKXrMGlq2W/Whf7q 9oIjZ8BYq2x5M3y/VVCH9vYihxFRT6D9Fpg2yw9ojFmJDt0shJuYf2ErJ/2Ymbpy n5JO/1MXtEKbczhmu1ngc23Z9LzOxeuEiZwGJWZoFmhQDlkitD6uOWYByYA4LdA1 W+OsL7tVdE6rUMX9WPJ75mcIgp5+U8mC05Y/pH5+m40/55ZvD1mJotkt4ME6V6f7 fKggPqz8rVZukvXEiTp4oW5CGy/C4zqC5nWiPF8hY8rhZrwpEo9/VFBneEi5Ouze vzSQCUzeQvxMbA1VdXB4EL03t3rt2w== =Fg2s -END PGP SIGNATURE-
Bug#1038611: lightdm: Lightdm fails to start X after upgrade to 1.32.0
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Tue, 2023-06-20 at 20:37 -0300, Adilson dos Santos Dantas wrote: > I tried to use 1.32 again and it only > generates /var/log/lightdm/lightdm.log. It doesn't generate seat0- > greeter.log and x-0.lo. From the log attached below, one difference is that > 1.26 starts seat0 and 1.32 does not start it. I got an X session from 1.26 > and X does not even start from 1.32. In the log there's definitely a bad sign: [+69.14s] DEBUG: Got signal 15 from process 1 [+69.14s] DEBUG: Caught Terminated signal, shutting down [+69.14s] DEBUG: Stopping display manager [+69.14s] DEBUG: Display manager stopped [+69.14s] DEBUG: Stopping daemon [+69.14s] DEBUG: Exiting with return value 0 Can you check also the system logs (/var/log/syslog, /var/log/daemon.log, the journal, dmesg...) so we have more information? Also is there something peculiar about your hardware (Nvidia/AMD GPU for example?) or software (specific configuration or something). Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmSSmacACgkQ3rYcyPpX RFu3MQf9Hpnj5rWRK71USdZCS9Gx4vQZ+octjX/3TZWtlB8vb3eDbLAj4ZAEkZzZ YjyFBCOx2zSV7HbY2l7fgb9/q7njngHuFr/ux+Z8nxRsyWy4fkhdQKh/4mfOt7sy wDa7WH5y+z96f9ekBLtauWe7YBFocEiEFPsgQ6WApvLmNzMwl2oXFP/bTKBv6BWi NWe5//R4gdt2yDKHIlZrBWGQfItg4KzG6wUuBfkrz/53PicafeFxcrOcZILoYzJK PU6uWij2Imebdzq+02rgYWz0Qq7fqI3PxNNfiWq6fMMa+rWXM5cTEGs7XC//Vqe1 hHbM8JXrzsc2ZcMaYCQyJ0PaqnS18w== =4Egr -END PGP SIGNATURE-
Bug#1038701: lightdm logs "lightdm[1166]: gkr-pam: unable to locate daemon control file" error on boot
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 control: forwarded -1 https://github.com/canonical/lightdm/issues/70 On Tue, 2023-06-20 at 12:44 +0300, Yura wrote: > Dear Maintainer, > > I've noticed that on boot system logs the "lightdm[1166]: gkr-pam: unable to > locate daemon control file" error message from lightdm, which indicates that > there is some issue. > > Nevertheless, the booting process succeeds. > > The expectation is that such error shouldn't occur. Hey, this looks to be https://github.com/canonical/lightdm/issues/70 but there's not definite conclusion in that issue. It looks like gnome-keyring is launched for the lightdm user but lacks space to write some files. I don't think we really need gnome-keyring as part of the lightdm session anyway so I don't think it's really problematic, mostly cosmetic at that point. Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmSSGOMACgkQ3rYcyPpX RFu2mwgAtSXk2CbNNaPObACSEhVIbL3uZYFPMDyHucZQ2vXYYp/occiOlAaf1rNF efANrjxSFNngBuGrGvWyki5uGyw14GHKudSb4KJgg6qMbW4meCES4cvf/m6VP+p8 Is2Vbj6Dk4c3c0+JEZyWJD6Me9h6nMhu1g4RAyrxPo3K6kzbmcsWx2ZzAr3Yo686 NyrEy0jdBuea/C/eBh4q+fFNVB6BnXkwLBDYd0vHes/V3lfxAxG9Wv08L47B5elP ixr2pfX0Bx6h4thaloj8C88PR2sDNgGM95CJHktxKxX7By8tEp8yIKQg7x/NnR6D IoN3d/HUQFqbJYz+A8iiYKsgK9EsNw== =6fHb -END PGP SIGNATURE-
Bug#1038611: lightdm: Lightdm fails to start X after upgrade to 1.32.0
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Tue, 2023-06-20 at 12:45 +0200, Carlos Laviola wrote: > Package: lightdm > Followup-For: Bug #1038611 > > Can't reproduce, starts up just fine for me. > > Could you perhaps include the logs from `/var/log/lightdm/´? Hi Adilson, I'm running 1.32 just fine since it was uploaded to experimental so I can't reproduce either. Logs would help indeed, and if you can investigate a bit more on your side (the info about downgrading helps identifying lightdm but besides that...) Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmSSFncACgkQ3rYcyPpX RFuFvwgAlSLsGtGtw8gWLSKh9j53R90TnQFXO815eCtpu4v332YxbTEc8ZyqUPVF zndG+48/CWRtlhSi6PHlAorg3rMk7NgTSB29Oi1XD9Re3UX7z7Xvu/P92XbipzVg D0TqCHN34PkPqoImgoNoHVjdgzaJukgGcTMoTZqbU/EguAHudkDqnHdXKbps6JUA Pq1fXi2P6BP9nqDSpWjPmO4aA/o59Evb+D1q5MRHm43sZS3z9Vwj5zalLl2MiPG3 0EcBg/STIOV8Om+GBPYAsvQau4/3gWqyziVQw1/v4A8LYnH4BTLB+W6rVbHk/Fj6 PKbmA5VO3GjJfl4LABIPkpAwkB+gwg== =SArv -END PGP SIGNATURE-
Re: mousepad update
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Sun, 2023-05-21 at 17:25 +, Will wrote: > Any chance of updating debian bullseye's mousepad package to >= 0.5.5? > > It fixes the "When double clicked on file mousepad opens the file in > background if mousepad already opened" bug. > > https://gitlab.xfce.org/apps/mousepad/-/milestones/6#tab-issues > > Alternatively, backport the fix. I'm not fixated on the version number. > > Either way, thanks for maintaining the package in the first place. Hi, please reach the mailing list instead of private emails, it has better chance to reach someone available. To be honest at that point in the freeze we're unlikely to update mousepad, so I guess it'll have to wait. Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmRrnsYACgkQ3rYcyPpX RFtpXAgA0RRQx29/VNekW+BRH7okfbUNJwDnmhnMDYBSvehcJtP759Bcbn3QhXzH qdWugJlXtF2XCsqbtFxTrKfa9b8g9agFuoJ1GWzbRzrVg288MfgYE7wzslIi/1la tb4uxkwM7plDDMkIdGraxENHvPjowpymiQHVjQ+tDjnNe7dBv3ZYPv7r/tibE1Yg z2bg7a/I/0tfIoOBH4D+SY9X9LbywQ4Bi/xEroatDsXR9s7GPi6Y6jBGrzeEWfxe dBDGRtT6Ndj01luFexZm6TgE/DucKBqNJz+xl1Qv6Pk8UjoMKK3QchWtDVcewGKS lTV4CAJU8qdbNMX7xfvrrw/3gZg2kw== =BukE -END PGP SIGNATURE-
Bug#1035452: libmousepad-dev: missing Depends: libmousepad0 (= ${binary:Version})
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Wed, 2023-05-03 at 16:10 +0200, Andreas Beckmann wrote: > 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) Indeed, for some reason that depend is missing, we'll fix it for the next upload. Not sure about the severity though (especially at freeze time). Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmRT+kEACgkQ3rYcyPpX RFs/YAf9EdzJoXD2doBL26HIb1Lzfeli0uI3ZhvgdiwB+9mYuUzI2S+sYGM1v/X3 ZQ0BGkJhClQmnLdeNjRUbbRjNr6p3m4TCFb9o1oHXBVwvv7mTTK61ODgwjkMUqVw SGkWlxUQfwAsZxR3gnLAUw+pWkOXh1rm3fstZz2Q+FEkEJHDqnqJqilwOOwKDC3G Wx5Q40+ZOe2JDc8eCE3B2shpZtbOQL5eNkjIwlxQIoyeilrrJ6tl3WieKtQ2YeEZ bj3ldm2tl9QZpOLQLppR6zLx5VN8R+tJwDI69+T3UYkSsDF8jCc6BBLgpq5oOdvC Usx94Q39HLvxKvWjoWfI+StoVEGk6w== =o9iA -END PGP SIGNATURE-
Bug#1032250: xfdesktop4: Launcher icons start from ~/Desktop rather than ~
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Thu, 2023-03-02 at 10:49 +, Paul Evans wrote: > I have a bunch of launcher icons on the desktop to start terminals in > particular places, or other similar activities. They all used to begin > with $HOME as the working directory (shown by a shell prompt). After a > recent update they now all begin in ~/Desktop instead. This broke a > few launchers entirely, which did depend on paths to specific things. Hi Paul, thanks for the report. Considering the desktop launchers are stored in ~/Desktop, it does make sense though. If you require a specific working directory you can set it in the launcher properties. Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmQAnGwACgkQ3rYcyPpX RFufVQgAxTAO5xsptxIAoNCdWUoDsX5BrwTxqhNg0UDmO3DQ6ZaG4Pd1MQAOLR7b mWM5LbGNBzgPGSixsxaGW7fRFTYMlWz4bmNi+tZz6Z9XNc+JvdHLwfWBrJpw5+6U SCsVpKsO05/WxUq2KUL8XCdet9OismkGMA85dqSdMysyJTlXDtOniJtLqvck3rK4 0odcQx2vzEKNsQb2D91qAifP1snVuW6vR1GyqVA1mPaoR8lPKV+o5fQC8pZGjpsb JbA7mBWFM636RxTFKEOoEvsT/X6kSSTl42oJpgtifEzc6UB4SwNAaJWc+rsO56Vy OAWHw9LhxQubMW3RZn1KyFzjVVPGlg== =K0xH -END PGP SIGNATURE-
Bug#1031968: libxfconf-0-dev fails to build with valac installed
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 control: severity -1 important [please always keep the bug address on CC:] On Mon, 2023-02-27 at 04:17 +, spinal...@gmail.com wrote: > > The severety was set automatically by reportbug. Ok, but you're supposed to double-check that. I'm correcting this then. Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmP/AOsACgkQ3rYcyPpX RFscOwgAxIwy5n45QT8gsFZXcGzWyslZNR2cCfJeqvQB7hegbbF6ryx9DaFnxGQg BPL7918g5eRPcFtGYL+OubFWERJilKdH51p6c2Rcam3SjLKo+CvETvuZJUCWpCoI 0X+4J5pwy8l2xhxkmYPFGMMa/KLZ9U+lucO3eE/L26Qdy9E/7w2R/lPVCeknyQOH N10jLF/p16tkPEY9fqfedTYxzL/TTw++5USiU90lZHkZpHFZueVm+79y7kVZInl+ ttt301cCTbwqk43Cu2Gf8Pjr86yhNb1z2L1Mvrv7FSUTZbGhuCeg4tiXmrzt9KG1 QSlrdisoEp/FvECU24mqEUqSxXIgNQ== =XOPV -END PGP SIGNATURE-
Bug#1031983: light-locker: Fails to login a user back to her previous session (session lost, new one started)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Sun, 2023-02-26 at 16:28 +0100, Dimitri wrote: > Now, I guess the problem is not light-locker, but the function it calls... > Maybe you can give me an advice of which > package has an issue, and where to get more help ? Yup, it doesn't look like an issue in light-locker but rather in Xorg, not sure exactly which package though. Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmP7hfsACgkQ3rYcyPpX RFvVzQf+NBduQUGlA1yk94C6wwP98KsNOPY0tLgle+jOM4w89GCuJLB3wd8OFakS L3/r85QfssON9jng2xoS9FSDiIY1WTLktR7myj5xRPQJWKEhYB9hyahbSS0bScxk N49drGroxrNyW2oJmvlTHFmt88cwly1GCYKy3dgigVdxngfzJvO45HciVMB/4rFF m7BYk1YSYw3u1eh/ZYZk9RmvvITDZXXETd5gJW3XgsPv9j50QIoI1PH3gRvvj+5O PR+W5LnAKDoO3m8d2PkjC/VwLCcy22tNXvi5TSFmC9rP2hUEsNCz740aAKTSJjFg phf+KTYliMX30dU0hMWmHps2ThbDCQ== =QGhg -END PGP SIGNATURE-
Bug#1031983: light-locker: Fails to login a user back to her previous session (session lost, new one started)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 control: tag -1 moreinfo On Sun, 2023-02-26 at 11:43 +0100, Dimitri Chausson wrote: > I'll try to describe the issue as well as possible, even if I have no clue of > what happens. > After coming back to my workplace after a while, I see my screen locked. I am > prompted to type my password (the username is already filled). When the enter > key is > pressed down, a kind of "re-init" takes place I see the login screen again, > but > this time, I have to enter my username + password. I get logged in, but it is > a > new session.. None of the applications left open before is active. Hi, it looks like your session just crashed. Does this happen everytime or did it happen only once? Did you get information from the logs? Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmP7aF4ACgkQ3rYcyPpX RFs5NwgAwbC0dJHc+mq7f9U0IoAmLzJ5L4b3NZkGqbViDKb8M/qXlxMmjkbuKYKM 5wKUSTpipiZxoaC9DrMCipq912S5OY7S+ZcSshjDcUIuS2ejGRhfMKbyNABuRyhD mhkIig6NlkXv0VWmh1phy2gkfM8I/ItTp+xgmbJ4UlFTeY8O7XVkNwkAbx4+JWwH 9VMlAG0+XrwKyiLtuApDEqZbBjf8dvltfQ3H41cKxov9+SO6wdT4GtGz6IMGK5ZR o/i7ajQb/w9YrpipRtYbB8KMc1UJDUbdUS1bGBCyyu97OommkoWyho9tkBaWQ4sw slBWGR3yVtVrVykvRnlTcMrjCIJxcw== =j2jc -END PGP SIGNATURE-
Bug#1031968: libxfconf-0-dev fails to build with valac installed
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Sun, 2023-02-26 at 05:11 +0300, Arthur Demchenkov wrote: > 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` Hi, while I agree it'd be nice to fix that so all files can be successfully regenerated, I don't think I agree with the severity. As far as I can tell, the package built and still builds fine with a clean chroot? Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmP7HG4ACgkQ3rYcyPpX RFuWwQf/QmWPTQjD7r7AyTmhU6/p8ualRZKxOT/uW21mHQQ2wE/omxPwYqZ8nFZn 55uo7//u2ZKW2te5WX0FZDP1yTHtX5DtQABB7yiWbxVjlj7N2Mp1/NbGLgewGnj0 R330UOnC0vt7rB81AMT/QkP9Z9MxQnpCeF+KP1KIEUdPOebkC0oDyhUX8N0blRNU riCtzgYoe+o6jfz5LhMBEOGAOxakj3RxVLj/+niHhHini8PkhsoMLVKGS7lnx91E WJQnlcXbeinzP2P86HpV+3M91ZV65erB1tHD4dDtZnuyii5XtFvL58MSQqS6pmbb dsIQiVXtaTzQbpkPvMyXR4WMtn8SKg== =M4wl -END PGP SIGNATURE-
Bug#1027097: xfwm4: taskbar is visible, when using borderless fullscreen
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 control On Wed, 2023-01-18 at 08:42 +0100, Yves-Alexis Perez wrote: > On Tue, 2022-12-27 at 20:46 +0300, Beta Version wrote: > > 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. > > Hi, thanks for the report. Along with #1026884 it seems with have some > behavior changes regarding struts (reserved spaces). I'll try to ping > upstream > about that. Hi, so I just checked locally and I can't reproduce, at least when using mpv and using F it correctly cover the whole screen; same with Firefox and a youtube video. Could you elaborate a bit on what exactly you're doing? Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmPITkwACgkQ3rYcyPpX RFsKyQgAzzGtH1cUtQRmCdbQikVrH6oJ1po9X6VQ/Tlp/m/NWG8M/1e40ZlonOh1 pcnoE7NeBX3Rcy/h3xchvybxHPjJTux5WONkfHEx6Cd/8NpkxsJahZSTm5p0L25x nGzd0BZpG63xGOD9YUgWl/+4yQArOB6UWciCVfqqv3RclsTJQeRsNm6yevKIiSzh HPGS2Heah3+H1qnjAkB/IMc3Hmxu8HjOW1hbVeW15oZTTtHf7htzEUf13IDq9VsV FqPVcqp1Bd19hmFuD9yuAN826cztsDCv7cAbyGh8TqZRzq4jomZCz9jvist1fGAC JV5VfzS/+s+Rr2UYIz0+H41o9n2a+g== =7n/7 -END PGP SIGNATURE-
Bug#1028399: xfdesktop4: apps menu not popping up when menu icons disabled
-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-
Bug#1027097: xfwm4: taskbar is visible, when using borderless fullscreen
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Tue, 2022-12-27 at 20:46 +0300, Beta Version wrote: > 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. Hi, thanks for the report. Along with #1026884 it seems with have some behavior changes regarding struts (reserved spaces). I'll try to ping upstream about that. Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmPHouMACgkQ3rYcyPpX RFtK3Qf/VBR3rVHXqkaFguHx7wznYMWcsr2kzs+kzXAmSjSl6MPrH8+TipLfF5yO x/SGP11WoguYo0LnLy5qtChjWkqcq0rXlo+Qb7l2m9ZRodWL6Xa9TGwtarEyW6jP C/T3YRHkpYL3eqls/tGYBlQ9TZCxNI8IFNLyaJzwQZb3+6EXtdJP/OKRdOK6UeTP 3POlk14VJqQaYSqCYxil9wtAm0BYXZPRIpUwDHbCr8OkUoohm5n3LNTZ/Sd3beOX SE3HSMa6vb/MN+mN+VqE2EdpX7oVNWFz8R+hmSW2pfalQtoGn+t+yTGLMc7yD8Is 5JCA8HO0gh2C4SxpfXYxoTs0VG+QgQ== =Jpdc -END PGP SIGNATURE-
Bug#1027900: parole 4.16.0-2 does not start
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Wed, 2023-01-04 at 15:12 +0300, Сергей Фёдоров wrote: > 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. Yes indeed, so we have an issue with -1 which doesn't build, and -2 which doesn't run... We'll try to investigate when possible. Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmPHo6QACgkQ3rYcyPpX RFso8wf/a4WKNKwWJ0klpyxStGxtoGL2TVFU1JdB8I+iMsVdIjC+4DoZleLs55Tx fMas2p0AdP7YrO7xcpHrdBLU4fcqHdmAGe3p5nda6oFhew2JfBVal5CCaZR74n80 kxUg3SIMiA8TGBiOk68x7dO6ukyYmWlzlcBVGnnoDLJbhNv71ZSsQDQ7UEYAllCx 9ZoIej0Yvev7eYomcRQQUiwehosBY+D/efaeQYNnZhnTaLkacWl6rzNZUYaSLoX3 H0xPBh/L2h9aGNYVR6aOdxj3juYeICVlFi876rcPLftVidtmoUgbcdgFx13fQzTW AEYqe9m+qCFzE+ofdiViAa/ksRSKFQ== =jQTc -END PGP SIGNATURE-
Bug#1026884: xfwm4: Reserved space through _NET_WM_STRUT property ignored
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 control: tag -1 unreproducible moreinfo On Fri, 2022-12-23 at 13:38 +0100, Sébastien Dufromentel wrote: > Since the 4.18, it looks like Xfwm ignore such property: when I maximize some > windows, they take the whole screen size and thus cover those reserved spaces, > which is a bit problematic. The other WM I have on this computer, Compiz and > Sawfish, still reserve space perfectly. I rollbacked to 4.16 using the > bullseye > package, and it works again too, so it looks like something very specific to > this version of this particular WM. Hi Sébastien, could you add more details on your configuration and especially which applications use those reserved spaces? I didn't experience this issue here at least with a standard Xfce desktop (so with xfce4-panel). Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmOoo08ACgkQ3rYcyPpX RFuQnAf7BVZ7lvLWFxK+vh50BZFzT+ES4PGIjZ/cQ8M7YOeohPdU1Hgr6CgpUM7F md2zX6HUgSnikwZbE2DtMLXAVw3XKs6i3ilDMZq2yZ1fPLERbMYw5oAPMP5C8tcE aly8qZ8O2m8jApzBCt7gVlQLrVp7BGWcMNee29cGhQTYGAoUZvIAnKyXp5K3octb I0v/5jtG5vYiP8CrVuqsHaaA9mVpxchczOtHcKLaZX6TazeUqw9i/8kW8eqRc4Nb TgplcKRDGIM8rd8tTRiYv/Q1X/9QRtLDrhPktfhOkkZNt24Hs+9DQo5xNkaZ8NpT yBzgPThHF48wZcfDq6RvGYrF0pEEEA== =5ih2 -END PGP SIGNATURE-
Bug#1026648: parole: FTBFS: make[1]: *** [debian/rules:22: override_dh_missing] Error 25
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Tue, 2022-12-20 at 18:38 +0100, Lucas Nussbaum wrote: > During a rebuild of all packages in sid, your package failed to build > on amd64. > > > Relevant part (hopefully): > > make[1]: Entering directory '/<>' > > dh_missing --fail-missing -X .la > > dh_missing: warning: usr/parole/pixmaps/no-cover.png exists in debian/tmp > > but is not installed to anywhere > > dh_missing: warning: usr/parole/pixmaps/play.png exists in debian/tmp but > > is not installed to anywhere > > dh_missing: warning: usr/parole/pixmaps/replay.png exists in debian/tmp > > but is not installed to anywhere > > dh_missing: error: missing files, aborting > > The following debhelper tools have reported what they installed > > (with files per package) > > * dh_install: parole (5), parole-dev (1) > > * dh_installdocs: parole (0), parole-dev (0) > > * dh_installman: parole (1), parole-dev (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. > > make[1]: *** [debian/rules:22: override_dh_missing] Error 25 Hi Lucas, thanks for the report. It seems that the pixmaps aren't installed to the correct path, because pixmapsdir isn't defined to the correct place, in turn because DATADIRNAME isn't defined anymore. I'm unsure what changed in Debian since the initial upload in 2021, maybe some autoconf macros or something. It *seems* that DATADIRNAME might be obsolete (since a long time), it's not in /usr/share/aclocal/gettext.m4 but I can see a lot of embedded copies with https://codesearch.debian.net/search?q=DATADIRNAME (I looked at the gettext changelog but couldn't find a reference). It's likely an upstream issue but still I'm unsure where to point them. Apparently there's datadir/datarootdir but as I'm not an autoconf expert I'm not sure if it'd work in place. Any pointer appreciated here. Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmOjJl8ACgkQ3rYcyPpX RFv/XwgA4Ly4KInLEQ2j60tBvndrsJ7B4RIRyJH8Lb1nxwdP/XAWq93o3p/6bgTR SCdYYhret3y2M2jbZiJLY51/9EpOzKc2Ut8K2+mtm3sHpT+mMWLs3qbufOTE2MpL VMPtWg0dMHT9/eOjXbrcKCrNFhJLm/oxsIgdSXzsNL/5z70ARCo7MYi97bt22KjW uEFXrctxqDRdG6srwtj3cfYGufMAtYFWGwLcj+zvR730IZcjdscXrhbb4yHGKF/R p9hrzKS6l/smBfRJyf9h1lSxH8Pw1AKV+qBO4n5sX7GJ6rdDHpsc3kuZlivvpgSM UmL9nyEmuhOyrhdL1VgZr+9FfEE76w== =kpYg -END PGP SIGNATURE-
Re: Thank you for Xfce
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Sun, 2022-12-11 at 22:38 +0100, Lars Maria Norén wrote: > Windows is boring, KDE is not really my style (to many settings), Mac > OSX makes me feel stupid, Gnome might be ok but uses to much of the > screen just to look pretty. Xfce is the only DE I find fast, efficient, > easy (and intuitive) to use and configure, attractive, and simple to > work with*. With this email I just want to reach out and extend a big > thank you! to all of you who makes Xfce happen. > > Kind regards, > Lars (Lund, Skåne, Sweden) > https://www.openstreetmap.org/#map=12/55.7046/13.2124 > > * Besides the usual everyday stuff I do on a computer (email, web > browsing, word processing, looking at films, editing photos, etc.) I've > learnt to code a little in Python/tkinter and developed a small app that > I (and a few colleagues) have good use of at work. Hi, thanks for the feedback. Adding the Xfce debian mailing list to CC so other maintainers get your thanks. Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmOXeb8ACgkQ3rYcyPpX RFsRCwgA1P2ZEFxHV/f1o9pGCyc4admSTsT76auLwiUpr+U9+X7WrmzHkFTStd36 G7X67JZ46ZCYPMilKjOItRX+VjlNc3NI94wDZR4uW1MIx/vLYM2/ysKtln1+H6or qSx+H8lKJ/eO/tQWzDAXTwKtYE5PwfA6JdvR3IT0MiieEjS9xZsnyDB65dEJXbiC VDMG0nlJJ2Nrviopfb7Hx9JChTIbK39u5MHgwgvv4DOARm/V7njWEcsc2HmdLxdL zF2F/EyOm85+PjHbuGR0a0VwSsvk8YGtx6TifeY1Wwf+wg0NbUVa52mIenww8E8t r0RRd/zWYj4usGQ/grIMK5QRMRpKXQ== =hPco -END PGP SIGNATURE-
Bug#1021779: orage: eats events
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Control: reassign -1 libical3 Control: affects -1 orage On Fri, 14 Oct 2022 16:07:45 +0200 Slavko wrote: > Hi, > > On Fri, 14 Oct 2022 15:50:29 +0200 Slavko wrote: > > > upgrade libical3:amd64 3.0.14-1+b1 3.0.15-2 > > after i submit initial report, i tried to downgrade the libical3 to > previous version (from https://snapshot.debian.org/ ) and now all my > events are preserved, thus libical3 upgrade is related to it. > > To be sure, i start/stop orage multiple times, and events are still > here ;-) > > I am not able to decide if it is orage or libical3 problem (or both). > Hi Slavko, for some reason your reports never reached us so I've just seen this bug and your investigation. My feeling is that this is actually https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021698 so it might be interesting to check if it's fixed with 3.0.16-1. Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmNVD2wACgkQ3rYcyPpX RFvdswf/XUwqXMlktP06VWu04Gh+w1TuLkNx85qF3ZUxfozcHaqoEzma48lLCLxx bkdZTZ9SrT54hCYq+gbEux9AIfjam+2OUCf5X/9EedVZ77VNCX8qFZ7Qe3VCZt7W 1zrKwXmfvEU/llnzxdh7Sh9tZgo5ny3v9+q0D3Dkv/9dXPEIeQC9qZpt1tS06zuf LrLsejJMfQNAlX9s/8+d84hx0WbgqN66F67RwzSPe0mD4t0HBLTjOdRKMNQ97epL GgV9K9qKMoaURgpcOk5vjyHsyDXFENFmFguMi6VjyrYkL1zKjvcG/XIBnc6i8dlQ W4FZWjlWfYL6mI/7zWFDXXBR+InFjQ== =4Fom -END PGP SIGNATURE-
Bug#932047: lightdm: greeter session support for elogind
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Sun, 2022-10-16 at 11:49 +0100, Mark Hindley wrote: > > My suspicion is that since this appears to be working for other display > > managers, it's all fine. > > It seems that way to me as well. I'm not sure other display managers handle the greeters the same way (running under their own uid and stuff like that), so I'm unsure if we can really compare that. But if it seems that there is no breakage (and hopefully no bad side effects we don't see yet) I guess we'll be able to update the pam configuration to uses includes as well at some point. Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmNT2yYACgkQ3rYcyPpX RFtntAf+PrX+vI64PMhmD05GD1A07Y438fJRf5aMkYIPa8n5X1Yc53//SktpHaow lK07jJurXvyjxQRY3GviHP14ZQfqAgOhln7pDqqIkr+9QKxkNxAZKAJ4W6lKZrGo VAqas/Qxat+ImO694snxyYDUWnCNgZA7DL+3kxtaHsN9GbTbfDj1h2ghQRKUOA6K +yQWPq7owks1YzGgcLgLch0Mj7T9XI82J88tJ04iZXBsl3SMVe7/Xr2aSt2HmzRq sUNAlWlgGJ3RlK7DUPcue3SnSRYc8Y8xChEuAQC3HWS3SmVBCeqQPmOrke1ipk3I HCcdh98sBi44tSAW65/B+jBGTDyGlw== =Rw/9 -END PGP SIGNATURE-
Bug#932047: lightdm: greeter session support for elogind
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Tue, 2022-10-11 at 10:02 -0600, Sam Hartman wrote: > If including common-session will work, I think that's a good improvement > for everyone. > It is closer to best practice, and it means that as PAM profiles are > added over time, they will work for lightdm as well. Ok, but... > > Whether that works depends on the architecture of the greeter. > If the greeter has one process that does the initial authentication and > then forks off an entire different set of processes not descended from > the greeter that run the session, then including common-session might > not work so well. That's the case. > > I'm kind of confused though because it looks like 1.26.0-8's sources > already include common-session in data/pam/lightdm. Yes, because there are two PAM sessions: - - one for the greeter itself, running as the lightdm user - - one for the logged in user The user session already includes common-session but the greeter itself uses a more stripped PAM configuration since it's only used for the login screen. So I'm unsure if an “interactive user” PAM session is really a good idea here. Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmNFtc0ACgkQ3rYcyPpX RFu7BAgAoWJnJlzOocZHXVF1fZpYHPkHytKbvCWlm22qcSuEsdg+sBlKN+UtNK2n xnb1oY4qffVtCORVNicKlwP+3OuL8WsW9vwHpni3V3oLuMoG474dT3iP9YGc2nW8 tgeK1TNpUuYiNGGGwcoUI+NlJY8mqYmbOxNVrbGNz7M7fLnd4jDPNdzCfh00bxMQ W/MR5n/C+DlfXmoG+CQBudKRQpbNqXxl/POm2lphmf4do+oVfpFT7CPekwvzyp/H /eHEV/rkjPTRzDnlsuhKSsLWebK9+ye+gUJfUJLDc6Hrx3RVnr4ZULKrrtbMg5d+ JivFke0rBEELT4xJUhEQukxRUo12Rw== =+dab -END PGP SIGNATURE-
Bug#932047: lightdm: greeter session support for elogind
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Sun, 2022-10-09 at 13:22 +0100, Mark Hindley wrote: > > It might be nice to have them chime in. Also not sure how this thing is > > handled on other DM, any idea? > > A quick look shows most use '@include common-session'. AFAICS that is the > case for > > gdm3: /etc/pam.d/gdm-password > sddm: /etc/pam.d/sddm-greeter > xdm: /etc/pam.d/xdm > slim: /etc/pam.d/slim (although it doesn't use logind interfaces) > > AFAICS lxdm doesn't use logind at all. Thanks. I seem to recall that our pam configuration comes from gdm3 but maybe it evolved since them or maybe there's a discrepancy between the greeter and the user configurations. In any case, let's check what PAM people reply, but I think we might end up with the @include common-session part (I'm unsure if the *greeter* should have a common configuration but maybe it's ok). Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmNEItYACgkQ3rYcyPpX RFupawf+NinPdWdmpZUHKAnKYbyZQ73AkxYkWa7hbQO39tplye6OZrCQPjAhUnUS ODOfUhDJ8K+2lqV1Imhj4P7mQ568YuufZNDFtvsSugOQDHDylKgnI74E4pm8xpb2 lm1Pqfr6PeE3VrsiQkkiJfyqlyxwRLhjFnAXsLkSVWFsnegjwlgnAfcvpCDiIEta h7JOjzMsWvhaH4FYZoFHvalQ6vQooRJe6BSsZ5AFfp2UNy6XXmHVVlXVk7PYp5sV yRz/d0EZqjSWNCsnROL0AwWCtW0O3hKDHLo7VW3QFaJOC9m0abxsOIstW7ngxodu v182m8DY2wjlUIKlL5MquYhv0kCaxg== =1RY6 -END PGP SIGNATURE-
Bug#932047: lightdm: greeter session support for elogind
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Sun, 2022-10-09 at 10:03 +0100, Mark Hindley wrote: > Hi Yves-Alexis, > > With another user bumping into this issue, I am keen to have it resolved in > bookworm. > > I think adding > > session optional pam_elogind.so > > to /etc/pam.d/lighdm-greeter is the best and correct fix. > > I know you have been reluctant in the past, but would you consider it again. Hi Mark, for some reason it seems I never actually replied to this bug, sorry. I might have replied on different bugs, but I'm not really keen on modifying pam files, especially for specific / non-default stuff. Do you know what are the opinion of PAM people and systemd-logind people on that? It might be nice to have them chime in. Also not sure how this thing is handled on other DM, any idea? > > Alternatively, I am happy to offer an NMU? Please refrain for now. Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmNCtLAACgkQ3rYcyPpX RFuVzgf/ZUcNnSJTge42ZSCEvgRnwwjlCZw595S3MlZlSjQfRjPZfU2mitNvfs7u WZqXUEF1H+KoFeGF5IUEwoWYAK62KXz/9aTmO44kz6kTJKVy4JT8Lv/XWer7jkXN Ku1q62VcPxwilWYgiOyX4YVPfWgFrD7N/DJ+/04lpZHASqvPh+hrjR6wK4SIl1OH +WCoRTtgaRw/bRaXL0STpPFi2BhzBsXRyQTcNgbjFRrXLOU2u4fBAb3g60V0aGxP ZU0FdjYbwsTkI875rd2t0fN6uURU6AtrFE+L0vaAfpbxCWtdkG41RlotvfiNzJ6L F42WnwLeOsWT4uQ6/MeEWm8+JcLXKA== =YNpO -END PGP SIGNATURE-
Bug#1016004: lightdm: re-login possible without password after "dm-tool lock"
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Mon, 2022-07-25 at 08:23 +0200, HG wrote: > * start a terminal, type: "dm-tool lock" > (It is a frequent hint in the internet to have a graphical shortcut for > this commant in order to generate a "lock user session" functionality on the > Raspi.) Hi HG, it's a strong indication to not blindly trust everything on the Internet, unfortunately. dm-tool lock will request screen locking but it needs to have an actual locker installed and so far that means light-locker. If it's not installed then indeed nothing will be locked. So either don't use dm-tool lock, or install light-locker. Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmLj9dcACgkQ3rYcyPpX RFtxXAf/R0xCjDvncsy4sprwnkZgpP+VAgvCPh8UO0zqK6oqdQnqRQI2bhS5yJd4 z5Loc69Z6leRI9c8AmoM3ntZJ6g54+0XrM9nheoDwDbFYRy0yzh0a6HeUhk4vPVh cqDTMOoUu2DV/WS1FmOA4xg0GyFd+c/uGMmbSETOs0NST7ApaIB2e1TcAayfZ6/w Twu0Wi1x6EVu5GWOV/GV7u4iVjCXzaZYLEmFK3JpKdqztjJK3EyYoDOfLDIjNPfS H0w2R0KfKMea4yhCf7cwAx6fRslzFn9aGw74GWexkg55D6ax3v0DLsfY7ABsLU3D ortKYu86Y6Vf9XT4Q+APU/AmcLzusQ== =+EB7 -END PGP SIGNATURE-
Re: #992360 xfce4-notes-plugin in sid/bullseye
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Wed, 2022-06-22 at 19:11 -0400, Andres Salomon wrote: > Can we please get an upload of xfce4-notes-plugin 1.9.0 to unstable? I'm > happy to do a backport to bullseye once it migrates to bookworm. Hi Andres, could you poke upstream people so they can do a stable release then? Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmK0rA8ACgkQ3rYcyPpX RFuwLQf8CkEWubEKSkUKRXx7oMOdfPgLy8sl22kujOap0gTmH+ih2fkm+LQYzNe5 JdpNhHkB1RH9J7wgO/8P5JSmfLcP9ckAf5Rlh+dzPZOtt5H8CSWoFVAa3e4gBgg7 WhMZIWvQrBRyybDrW2MHDRkY7+JUirDB7NepXnVQOzqkZrATzKYE709r6hsMcIa5 681tYxDTl3NufZXAg0vPt5Ik5yZv04yluZU8ZJVDtbJdOM5cEid5nOan6JKVdwKn 0omr+47SKd5EilL5BLOYhDpezYTk6qlSJvbps2HjllUywLkoQrNw4fEEOfi6y9AR ObUDSlzbGQ4pKsttE84ZuWB0U9lxGA== =L3QK -END PGP SIGNATURE-
Bug#1013129: exo: CVE-2022-32278
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Fri, 2022-06-17 at 17:08 +0200, Moritz Mühlenhoff wrote: > The following vulnerability was published for exo. > > CVE-2022-32278[0]: > > XFCE 4.16 allows attackers to execute arbitrary code because xdg-open > > can execute a .desktop file on an attacker-controlled FTP server. > > https://gitlab.xfce.org/xfce/exo/-/commit/c71c04ff5882b2866a0d8506fb460d4ef796de9f > > If you fix the vulnerability please also make sure to include the > CVE (Common Vulnerabilities & Exposures) id in your changelog entry. > > For further information see: > > [0] https://security-tracker.debian.org/tracker/CVE-2022-32278 > https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32278 > > Please adjust the affected versions in the BTS as needed. Hi Moritz thanks for the heads-up, I'll take care of the upload to sid and stable-security. Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmKtu9kACgkQ3rYcyPpX RFsDjQf+NFhYi6pCz7G+2Ce9Byhpoi94b0CN8t2+4ILY2/NJq8wOv6IRgy4TrYz/ tvff1vCiK+OwnSymWnIiUNuslhqZxvJjTGuD1ZvgTd6UCxUhH1nEoE2mjR/LOnIL UePIkyJ3aWAZV1mr/Ez+f+YCZfuxuJKFIhjwX28p6qDvwK+F3oNUdlLJf670v8nz jROrgnIOZ2tVw6+Z3+Bd67VcW9zoHN87/hWIxxM7Hs6qrROGd27YauxTiXHdcDRQ 3fNicUiEB0E8FPhvJ5Dq+iXhHnqef7/WlKp15ci69dDv1RcBBfP1VsAh9OZn5tPE 6nGqseCIwTcPb6ACU1rIJuPoqkxv0w== =552N -END PGP SIGNATURE-
Bug#1011523: systemd-logind: lightdm ignores keyboard input for the first 3 seconds
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Wed, 2022-05-25 at 16:02 +0200, Michael Biebl wrote: > Am 25.05.2022 um 15:35 schrieb Vincent Lefevre: > > So, if I understand correctly, systemd now starts the user login > > management very early, possibly before the hardware is ready. If > > this is regarded as correct, does this mean that lightdm should > > have code to detect when a keyboard is ready? > > > > I have no idea what you mean here. > Anyway, no need to CC me personally and let the lightdm maintainers deal > with it. > Hi Michael, Vincent, I've quickly tried here and didn't have any issue, but if it's hardware- dependent it's likely the reason why neither Michael nor me have been able to reproduce (whether gdm3 or lightdm). I'm not sure it's actually linked to the display manager (rather than systemd itself, or maybe something in the X stack), but maybe it might help if you could test with another DM (gdm3 or another one) just in case? I don't think there's really code in the display manager to specifically handle keyboards, I'd assume it's in the X part, but I might be wrong. And it might be possible that the DM is starting “too soon” on your box, but delaying likely won't fix the keyboard delay itself, it's just that the UI will be available later (maybe it's better for consistency though). Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmKOeOYACgkQ3rYcyPpX RFt/JwgAtrFpDNeEbESmyfsz/kRUhLXFcbHb0IWzPC7m/0nsP/lZRBdbWUZiMSAd sowzOMZExA0rGtd1GJSjhxKLaELm9W1J8julh3zetskyZyPTR9gRB6bcNGYt00I7 0RsRXhSVdFF2g4cb3SyD4hdGGxzBeCtR4z2b1TyJRwVVt0RcqRUxPjquvCLeTnQa B1lJ8g/X0Gdi8iJ4Yysu41tFd6SehvRC3gSxZT2m/l6L4xF5FJfOwVfhIJyDis4G bnCJUEhK+5o66UrD3IKqmt3L+WnB0QrhaTb/ax8Qlq3OJlrMADzVnixFtHB6Vc0j CJia4JCG+0k1EUDrqXqxjUdXW3kUGQ== =Mc0a -END PGP SIGNATURE-
Bug#708388: [Pkg-xfce-devel] Bug#708388: xfce4-terminal: Dynamic titling doesn't work
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Wed, 2016-02-03 at 18:07 +0100, Torquil Macdonald Sørensen wrote: > My tabs initially show "Untitled", and stay as such until I use the su command > to become root. While being root, the tabs show > > root@hostname: /path/to/dir > > where /path/to/dir is correctly updated after each use of cd. But using exit > to > get back to my normal user, the tab title stays as the last state it had while > being root. So there seems to be a bug somewhere keeping the tab title to get > updated while being non-root. If updating works as root but not as non root, I'd say it's likely a difference in the shell configuration between the user and the root user, it might be worth checking. Note that I don't think the default bash setup (whether root or not) is configured to update the terminal title. Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmJ+mHMACgkQ3rYcyPpX RFvuZwf6A85HoKddxQmEhIJalJxhmQE9R61wbwWBNB+QZQVYjVe2jZOAAUeejjUD DsyJt0lxnnUZUWWJp+NKv87N4q3yuRTrdEF8Zhxhwj66Asvj81e/SYhVonnDMhVA QvJUPGSJ6PsX+fDmzZC5+MegGvMLHPEFyhqnWPXbuCY0WCI+4aY50rJLR1lU1urz 1PgQjgUCkVtO2mIvCdUX9z3KpSdRTEKxY7KDR21yAYKoZuhTKYShzlegpYQm2ii1 dNGZL/oBBFofAF2R6gfX8Jw/iiU/eiaO8ydDl1byNXGBno1wI14U8jjMLXsWlIkd pBrqJbCB1DQIRrsNtuXpyNDEtzTs8w== =/KYl -END PGP SIGNATURE-
Bug#689056: [Pkg-xfce-devel] Bug#689056: Shell output freeze during significant text output
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Fri, 2012-09-28 at 20:36 +0100, Omega Weapon wrote: > > When a terminal instance is used with no tabs (just the one shell) and > significant output is posted to the terminal, printing of the output > freezes - the command then no longer responds to Cntrl+C. Hi, in case you're still using xfce4-terminal with recent versions, does that still happen? Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmJ+l4QACgkQ3rYcyPpX RFsLCwf/UhVUOI2TAzH/VRUrBfTBqck8JGIBHf0BNAH/hSx8xaUvpRYyMEFNY4CO 8gJtL+QzPs3gCvpERBfpXoSjv01Kg/gaOdxKzjT9VfvCKUj+MmNxkjlYY3RDFgMb NH9r9wIClmtIhVsn9mqB6kmKb4u9NdnNQTQvpnLWAa9AErfPcrh/XRv0fOYU0xae b2iGZxIDSNSidl4W75lioSUBrY4gFaHZtmEHaU+r1tut6tmfv9v/FPuvHSjkrBqm NdC35KdYh2kYrqjS+JmidhoHr3s3K+fXCk9pP1FhnsSfZ0Ha3wIBQDiLftFUVO0Y s03Tm9veDgdoG513LFD6hU0dA6b4gA== =iiA/ -END PGP SIGNATURE-
Re: [Pkg-utopia-maintainers] Bug#992120: (No Subject)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Sat, 2022-04-09 at 16:11 +0200, Michael Biebl wrote: > I think that was a red herring. > After closer inspection I think the shown screenshot was from > gnome-control-center and *not* from nm-connection-editor. > > Sorry for the confusion. Ah, thanks for the clarification. I guess the bug can be reassigned back to network-manager-gnome and closed with the version number including 49f87caa3ab867de2569185c34c384d507ed5b62 (not sure which one it is)? Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmJTDtUACgkQ3rYcyPpX RFvQkQgAm5Dci//cWfeS3IYe94b/XPGiVe37EonTfHwKksLPwUnw5j7lc+iHLPC1 DfXLEJ5tpb1Ey8IN8Lf2b79N2a+q8t3IxdLo+d+6EpQkXa2rXExd/ff94c6WvEB2 2IzMs0CfcH6n1JY5TP48XSO89y3Lgsw4P6cOW3TSKKE9KTDO2wJ8+OW7WDQeJoAe +E6WjQradaMGzrXsowFh3LO83l/V0H08qn8M5pf5LyEyc7PIeuQH6HdltpwWdGkv be7ScqYexI5JgJimsZJ8gA7RS3scem6d+5JTKTyMl3qEDgIki31pvhKxt8SDzui2 vg+QdMsmatJZNEhor1KTnyCWvRqEkg== =664a -END PGP SIGNATURE-
Re: [Pkg-utopia-maintainers] Bug#992120: (No Subject)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Fri, 2022-04-08 at 19:26 +0200, Michael Biebl wrote: > Might be > > https://gitlab.gnome.org/GNOME/network-manager-applet/-/commit/49f87caa3ab867de2569185c34c384d507ed5b62 That's possible but it's interesting that it's correctly shown while in GNOME then. Regards. - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmJRW+4ACgkQ3rYcyPpX RFtwwwf8CO5SB3ZcEeTjhk08p24CfxVdcXXEttw0hLt7bns3E0TbbZx6t9vNlj4/ 0XH2qJDyarZTswhgmFk9Xu1E6rOIcmCraAsWo8blaxdW6/lszIBr/rb0bylX5hNx 9jMZ5zxzMWwjhGgOHxGuQ8HX0Iqkxm9Q4VpdcVcjtqDXonr29BtjOuNhgrELKH5x n/KJP9VzhF95PiSsUWsMK4vuVWrtCpDv5Nil2xp9L1wM0Coz9+6sFvNQ3B8pOS2f fbBCY/6eLwiUBtb9iWXCNWsoBfrhmqOe8W9R7Du15inm7ARVxVDAIJ6HnqiIfLxl WiBwWx0vPacH4zwaEh5LCIrtboUUkw== =OsaC -END PGP SIGNATURE-
Re: [Pkg-utopia-maintainers] Bug#992120: (No Subject)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Fri, 2022-04-08 at 17:57 +0200, Michael Biebl wrote: > > > Yes, I'm using network-manager (and have been for quite a while). The > > > problem first appeared when I started on a fresh installation of Debian > > > 11 (with Xfce4 as DE). On Debian 10 and older (and on Ubuntu 16/18, for > > > what it's worth), the checkbox was normally visible. > > > > > > > > However, since seeing your screenshot I quickly tested on a fresh VM > > > install but with Gnome desktop selected instead of Xfce. With Gnome, on > > > the Security tab, there is a checkbox (or slider widget) with which the > > > user can enable/disable the 802.1x. So this starts to seem more like an > > > Xfce4 bug (or a missing Gtk widget library package or similar). I'll > > > have to do some package list comparisons now. > > > > > > > > In any case, cheers for this. Hopefully now the bug report finds more > > > proper destination. > > > > Hi, > > > > Just installed Xfce (with tasksel) on the afore mentioned VM, and > > confirmed that on Xfce's NM GUI no checkbox can be found. IMO, the bug > > should be forwarded to Xfce maintainers. > > > > It's most likely a theme issue, but since I don't know xfce4, I'll > reassign the the xfce4 meta package for now. Hi all, thanks Michael for the reassign. I tried on my Bullseye install and I can confirm the checkbox is missing (it's present on my Sid install). But I don't think it's theme related, I've tried with few themes, including Adwaita, and the checkbox is missing on all the themes I've tried. I'm unsure what happens though. I don't think it's linked to missing dependencies (since on the test VM it works on GNOME but not on Xfce). I'll try to investigate but honestly don't hold your breath on this. Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmJQZdsACgkQ3rYcyPpX RFv69QgAyoKT2V8UaWE3CPTQMNClJjWAStU4apiqhGPBa5t4O+UkCb0+gUDwCzHd w4zSLzlO6rF9x5yCfGdx9+fkn1TqAhxDdkrHH7jAQlKk7TbHlmvHPV9wkUyKpq2b JAREeerSfmgQL02t3u5jBi+0QOHZFL/VdOCLonoa3Zf1fKkl7Zhi67346B1htsy6 U+mknaR9fBfr9vBxkr2g9XiPVL09x2ApqiujLrAhRr8Qwu8WAaJ+rS1549CfgSAx l91QPAQDCCEMLfSHrlIUpfCmzVOX/9689VjTUSFsVq0l8zQgpwnKhiGgX6pg1deY SU52boDLllPgnYO1QCC8FtxdltOzng== =+si7 -END PGP SIGNATURE-
Bug#784158: Missing pam_env.so user_readenv=1 in the pam file
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Thu, 2022-04-07 at 05:59 +0200, Christoph Anton Mitterer wrote: > You've set wontfix on #672793 some longer time ago, but AFAIU, this was > because of some user's request to have lightdm source .profile (which > is IMO indeed plain wrong). Indeed. > > Later on #784158 was forcemerged with these... (and thus also marked > wontfix). > > Why so? Because (I guess) the original #784158 message was about .profile as well. > > #784158 is a completely different request, namely to modify lightdm's > PAM config to allow users to have an env file parsed. That happened later in the bug log and I might have missed it indeed. > May I split these up again? You can, but to be honest I'm unsure (and relecutant) about changing PAM configuration. I'd like to avoid breaking stuff in the authentication path so having a review of how correct these changes are would be nice. The bug asks for adding: > auth required pam_env.so user_readenv=1 to /etc/pam.d/login. I don't think 'auth' is the correct place since pam.d(5) says: > auth > this module type provides two aspects of authenticating the user. > Firstly, it establishes that the user is who they claim to be, by > instructing the application to prompt the user for a password or > other means of identification. Secondly, the module can grant group > membership or other privileges through its credential granting > properties. > I guess it'd fit more in: > session > this module type is associated with doing things that need to be > done for the user before/after they can be given service. Such > things include the logging of information concerning the > opening/closing of some data exchange with a user, mounting > directories, etc. > And the file already contains: > # Load environment from /etc/environment and ~/.pam_environment > session required pam_env.so readenv=1 > session required pam_env.so readenv=1 envfile=/etc/default/locale So it'd be a matter of adding user_readenv=1. But to be honest, the PAM modifications for lightdm come from gdm3 package and I'm again reluctant to deviate from that, and GDM3 doesn't set user_readenv. Finally, the PAM configuration file has > @include common-session so I guess one could reconfigure pam to include user_readenv or something. Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmJOj10ACgkQ3rYcyPpX RFtSFQgA5tRHtzYoo0vCcKgGFkHux4/5di3/kOLS1IbZzNS3IW7//lYOTQz5svJZ VD3cllG7OvTxb7LgiQ9RjdsXURMYpxFPls4dj+B1a5t2Yy3Aj4THgGPSTTeExRx0 sMGncRkDMtfb13S+gA/Ojrj3zkk1TXFSWvGi3AJIqRjdnREsm/tR2DQyvflP3SG1 IOmSSWagWBxo7nG7JXf5gixfTdCMDVkPPJ5TTZuud04eOL1FHocjakjc6j5o/xMb SsWZbx24eWja4AnVkksgVByUY3y3j7HoxKoomtpTWtqMosN+625qAKC1Mq2MDNxb X/ITrn31x1JbOA6Qrx+xBV7TeOQf/A== =/m/P -END PGP SIGNATURE-
Bug#1008999: xfburn: Homepage moved
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Tue, 2022-04-05 at 13:57 -0400, Boyuan Yang wrote: > 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, I've updated the repository and it should be fixed in the next upload. Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmJMhFwACgkQ3rYcyPpX RFsdTQf/Yu1OTzL0w98DfDNncENz3A9VlNi2IwLYdz3Y53yjAoH86iBoVxeYGJI2 e/ucgiKFSGlgJgwENxj9f9v0wp8SQr6bxOw8ZiKjfWvGuB6n81BOes/hyLUmwQSG IOeJga2Sm9nvMZ/myL65vqYgNa0XW/asfd5cu7R3IeQy1zpg8r91II3miym29sJf 9nD21ehbDIH3pNVjFBP6WqxEL+Jrotamwpnlj8hfVUoxM+x8oIsriJMLaioWkE2a xtZlVdRXgV5E+RkR4HB9kzb/UAtnJeAQKU+V59tRIPQFwp/KrLaF02BNyblaQgfU 5jBPTOvzxhOm0N3Xq5oSoco8y4EQmg== =mqbF -END PGP SIGNATURE-
Re: New package: xfce4-panel-profiles
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Mon, 2022-03-14 at 22:07 +, Samuel Henrique wrote: > > I can review and sponsor Leandro's uploads and hopefully save the team > some work, if that's fine with you. > > Can you create the project on salsa under the team and give me and > Leandro permission to push? Hey, sorry for the delay. I forked the package to https://salsa.debian.org/xfce-team/goodies/xfce4-panel-profiles and added both of you to the team. Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmIzlYMACgkQ3rYcyPpX RFvDzQgA3critYHUW+eRN4JFc+O4PxqEdMRQyZVOVXJVk/Tw9AwKq4vSe7Ry7JZ9 lV7tlPHGeH3XR3CIklCWAQAp5KNl3spNMMhgi9OPm/7AfO9ly7QUX32hBe9mI2/u 5Sr3FTKgdvh/keEgkif6yWySUEqqU+YcNuTptuuHUZuwww9q4OTNUBnkHNzMJoP1 uJlg0INHC9jsgBB9+s2Xs2/gCzlCoQB9fXIVMN0wsvrPQLsuozE+cm0SaBTdoPFm DqcCzro8ZI60l+yVXoyQF9AGn2Jq+VLSBRYZnSttGao1DdmvVfJ+dnjvJN9FrumJ sjpcsGL/fw6qXJjuhsXgilbpe8xAzg== =eje9 -END PGP SIGNATURE-
Re: lightdm?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Wed, 2022-03-02 at 18:02 +0100, Sven Mueller wrote: > I noticed that lightdm seems pretty dead (last release upstream in May > 2019, last upstream release incorporated into Debian in May 2018 - > since then essentially only fixed build failures and integration into > Debian. Would it make sense to remove lightdm from Debian at this > point? Hi Sven, this question is more appopriate on the Debian-Xfce mailing list (added to CC:) but right now we don't have a replacement for it and while it's indeed not actively developed it's supposedly still maintained, so for now, no, we won't remove it. Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmIh8jcACgkQ3rYcyPpX RFv6BggAq8bPAvlLILM4Qnk4ftJ1zZHmwLXG5Dnv8WpAm6+qs830K6bM8GcIc76d 3pLVjdO2YvDk2zMdffeYj94cJtGRRwiWH1PVbeLD82beXmF6bhOP70TNxhiG78pI n6oTelSCNoPL1Yyc2F5u1/doQWRaHLr91OOAB0kUkkUKdMANiBG3OJ3z4Ib6KJT3 8iqt7+Jt/HDN4Cz5ydiIZIWeu+3qX8x+Epe7vrDUfuXLIBh5GXJIjpd6uWJy5MWm 9Ue4sk1/2Y6GczXlzWQtUdJ/c8/o1dam/QjVtRBhRDkBKIXPDNqdsU4nt1JUtv6Z SVewiEzVK+d+wojHdacghe6DJ0LFJQ== =+6zk -END PGP SIGNATURE-
Re: New package: xfce4-panel-profiles
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Wed, 2022-02-23 at 12:19 -0300, Leandro Ramos wrote: > I've been talking to Unit193 in the #debian-xfce IRC room, and I'd like to > maintain the package on the team. Could you help me in this process? Hi Leandro, sorry for the delay. Can you request to join the Xfce group on Salsa (https://salsa.debian.org/xfce-team). I'll also import the xfce4-panel- profiles to the goodies (https://salsa.debian.org/xfce-team/goodies) subgroup. We also need to review a bit the packaging. I assume your sponsor already did some work on that so it should merely be to check that it fits with the current packaging practice. Then when everything is ready we'll be able to upload. Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmIY/aQACgkQ3rYcyPpX RFvb+AgA6LhlLnywqOfraUXMvtjJ5F2m0oNAHIXe9MSVp+tNcYPmc9l0mbb9Ejm8 np/H0eSVL+FUK18MuDFoG6c1zznK0A3BpyMFkGq5GbpQoLh/A80StJqMsNr7Mjpy gb3My1Odgy5VP4VD+zfRCu6sJWFrDXfL+bubipEFrQOWse+FoYHfPH3LWav2J12M 3NNtDJDi45epTQb6eHyDlL3wunkFUYsOi+A78BEXY5AkK0YkNKO3uhA/6bc7V/Hh S5iPxpPsgLRRjoWZn/WGUIrEOlqF6JcPm0yv9v0Jnbr3Sr4UGlwwNVxmL6m4LPuj Kg+V9J9XdyazYI0MYSwzHaXDOf0tzg== =6ItF -END PGP SIGNATURE-
Re: New package: xfce4-panel-profiles
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Wed, 2022-02-16 at 12:47 -0300, Leandro Ramos wrote: > Hello. I'm working on xfce4-panel-profiles package. I have a sponsor helping > me (Samuel Henrique). > I'd like to know how I can get the package under the Debian XFCE team. Can > you help me? Hi Leandro, I'm not against taking the package under the debian-xfce umbrella, but right now we're a bit struggling with not enough people onboard to help on the all the packages we maintain (whether “core” packages, panel plugins, applications etc.). So adding a new package to that would require a strong commitment to help maintain it and other packages in the project. Would that be something you're interested in? You don't have to jump all the way in right for the start, we don't have a lot of ressources for onboarding but you can start small and then gain confidence? You can join the IRC channel #debian-xfce on OFTC as well. Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmIOJO0ACgkQ3rYcyPpX RFsYtwf/eT1xyguu1nKLGHfwotWqSgH1RwD3E6xtaerWtWIpDuxkAX3Lxww1v8wv vAnSct6ZhhhNEqLLNlKmNOvwwGcRj4a/XBo9eA6UXt2I7j+9ScYP2HZ3eNd3TLlm pWZ7rVsC2rVUFEhzuG8R8CDDQtIBmAOXA4UY0wWql/VksFLJIF89M7dFbdwvWC2Y CF15qCnBf0aInOgyNIF0KLsQqkNDxeG/VrG6nP/Hoh46xovC5a7KRGLyMTTqmsM5 kMXLK8Cvqc52xqspCiqJibnhT7cezEszRDK99NyziNwsqzNRQKnxp0MprqwrfEix h8V/3uYrBA+fhhTd5GDM02gLohruXQ== =U9FO -END PGP SIGNATURE-
Bug#1005160: gigolo: Segfaults when clicking on Edit->Preferences
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Tue, 2022-02-08 at 09:23 +0100, Heiko Lechner wrote: > Dear Maintainer, > > * What led up to the situation? > > Clicking on Edit->Preferences closes the program. > > When starting from CLI: > []:~$ LC_ALL=C gigolo -v > ** Message: 09:16:25.174: Gigolo 0.5.2 (GTK+ 3.24.31, GLib 2.70.3) > ** Message: 09:16:25.257: Loading configuration file failed (No such file or > directory). > > (gigolo:18456): Gtk-CRITICAL **: 09:16:25.283: gtk_widget_get_scale_factor: > assertion 'GTK_IS_WIDGET (widget)' failed > > [And when I click on Edit->Preferences] > > Speicherzugriffsfehler (think it is segfault in english) > > * What exactly did you do (or not do) that was effective (or > ineffective)? > > Found no effective workaround. Hi, I can't reproduce that behavior here, so it'd help to investigate a bit more on your side. Can you try to get a backtrace or run through strace? Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmIEzqcACgkQ3rYcyPpX RFu2SAgAnIEm9qxupZIB9j/VeNdArliTC7Oic0ojNpMmQFq+yMS+P78geFByf23i wMme5CGDW9UYzxawkzKtMw/dd1RvCUqwieZc6Z+By0710XdlSgVJVWgSrvXD55El yA+emqGOYlxRRmj2tJ2CoiqEmwo3ffFTDs9uoXt4KeELpWrqw9JXg9r/HFP6CU0P /Vj1riJrzU0gOmPUUC7QoOR/S6w24OsgXrIWjlqK499cbJPcGkyj82X0ElFo1nq3 QRzQicPDEnyhUtQgTytLjUzdNgBH8Rl2TMKgORgtPHBg4G0KsXdeYNSd8UpsjO7z yGGmPRFt0+1onlMiuhWcSPgMlKs9+A== =kmEH -END PGP SIGNATURE-
Re: Trivial typo in README.Debian
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Fri, 2022-02-04 at 15:36 +0500, Akbarkhon Variskhanov wrote: > The very first paragraph reads: > > In Terminal when you cycle through tabs, the default behaviour is to stop > > at > > theend and at the beginning. > > > > A single white space is needed in the middle of 'theend'. Thanks, fixed it for the next upload :) Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmH/oq4ACgkQ3rYcyPpX RFsgRggAmyYk5WJRv2JTCgpGogIASAhZZmO05youOWauRu2m/GdpDkAhQjGoS3U2 FdPHsVNHx7MwZNII05pbtZcE12YpgJhp4tnNH2+W/DRz3p69bg5Spt4701i8eqrH lIJb6HaquLJsOmEevkcXn9/DVKW1z51uo0ODiBfikNSInBShU8xv3ZEqq0ZwrgLI ndQjcmxAr/mbda56krtR88Dqn3ODBC0+DO680ergAwV66wqVnxsudB32mNn9VXpm YaCNyai1mUk7MPEHtcoexHCZgla0ZYwU6+bl54g3OZ9G1nD/JF7BiJYZwPav/pag YK/GS0U3KDSJjKK8oJHzPhbz9PFR7w== =yRSF -END PGP SIGNATURE-
Bug#1004060: systemd: breaks lightdm / lightdm-gtk-greeter
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Tue, 2022-01-25 at 11:25 +0100, Vincent Lefevre wrote: > Something that may be important: in my /etc/X11/xorg.conf file, I guess it is, yes. Could you try without that Xorg configuration, to be sure? I'm not really familiar with the NVIDIA driver configuration file (in my case I'm using the XRandr configuration using Xfce display profiles) so maybe there's indeed something fishy here. Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmHv0L4ACgkQ3rYcyPpX RFuElggA7o4EnCd71lQfS8F4f25SK/cRz2QlSJ2VvuKUHLHRxAmdlZsCaN6zZg18 N9nXt/3XeNjrFbVh0Ovax0wD1uCazMPDxpVUF6ZZ+azipg3QO+4nPdJFCKohuJ+u mbHT+qWRLt9paRQV73CV8DKa4Xhhh2pnd7Lj/8RIo1iGdGpMydMXSLL/5NUG6zCA rImub1t+XGIvMRgQBPvqNg8/kHnl8oiPndVBTwrACbZPppHoxEoLDDFCGrn+vmEC qg3PIo72i/sN6CsJ3m/76EUCrDtQu9oKSK4JUC9IYgaNTelSs/MMS1zb6NSZKWYU CLO8YaTu3IxoekTJ+qIcVlxeav2eFQ== =r9si -END PGP SIGNATURE-
Bug#1004091: Starts user services
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Mon, 2022-01-24 at 18:37 +0100, Yuri D'Elia wrote: > On Mon, Jan 24 2022, Yves-Alexis Perez wrote: > > I assume you're talking about systemd user services or something? I don't > > think there's any specific code in lightdm about starting manually > > pulseaudio, > > pipewire or anything, so I don't think there's a way to special cases some > > thing. > > Yes, the issue is that lightdm starts automatically all systemd's user > services (anything which is installed in the default.target in > /usr/lib/systemd/user/) probably because it is creating a full user > session? Is there anything else than “a full user session”. I don't think lightdm has any specific support for user session so it's likely started through other means. Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmHvxY4ACgkQ3rYcyPpX RFve3wgAvP1lGHhiZH3XRrOe6ZUjFI2K1UiMCSb491XApCTPOTGIEWq9RGlceiW7 HuCMfyElf1SP+/dx10IS+Jf5vlDOMNc/BWKaYDJf11mGNf9lGopCH53XyomA/cmj huE55P5ECbgNl/BQGOFBet+pL9ielO6K8LR0Tq8bPyeWsTgcATWy9FnVRKXLocF9 gxVA/k3VfZMPtuMM/M5Oy/tOcPYGUhbnhpJAnFHJyU175PdnSJPzAbbfAdfD5YUL Kac13baOIrIocfP+9Sfk4/H/eAJdvnDPVNtCG6Z57DGLzMDC+L0YgzQh/bU+WLof LRxhhXCaSezMH55XQQx88DbLlM+LVg== =MHVh -END PGP SIGNATURE-
Bug#1004060: systemd: breaks lightdm / lightdm-gtk-greeter
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Thu, 2022-01-20 at 13:59 +0100, Vincent Lefevre wrote: > Additional details: > > The resolution of the laptop screen is 3200×1800. > The resolution of the external monitor is 3840×2160. > A 3840×2160 virtual screen is used. > > I suspect that the greeter thinks that there is a second separate > screen (instead of a mirrored screen), and it puts the menu bar > and login dialog there, so that I cannot see them. The following > workaround would confirm that: set active-monitor=1 in the greeter > config file (/etc/lightdm/lightdm-gtk-greeter.conf). With this > setting, the issue on startup seems to have completely disappeared > (still no issues either with a one-monitor setup). Note: some users > say active-monitor=0, e.g. Hi Vincent, out of curiosity, did you try to move the mouse (and bring it “back” to the main screen) and see if the login dialog appears? My main setup also uses a dual screen (docked laptop with an external screen), and I didn't (yet) experienced the issue you describe, but both my screens have pretty similar resolutions (laptop is 1920×1080, external screen is 1920×1200). Also are both screens on and visible? Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmHu4rsACgkQ3rYcyPpX RFtF5AgAuC28bTr9VLnxTdrMqSDvC+w0SgdA3IzTSpvqYms13dCpWs+dcVGzUckU 01sEAllZZIsF0SJzRCkZtDqR7j1+LDyiWO//CaQBAibjF/pp/mlfYOovc7ZxA9kV G49y903snFbx8eWECYWbshYFSETEKxyuDtqs4eRfXiaQW10ore/xC5om+CHSqREg TM6GTU57smTo2J0xJ9UVIuZy2V2pYHrDm/c9o5r/z42n7PfRlfqgUZJtMhHO2Oju U6i0ylOPErbQygmoC55Oozz3zGf2ce/gxY5bBhiguSK1C1OFbmNhPpMvbXg5blmf 7J3SMBuEkLJR6kLywuB6UFhvf9aj8w== =a6/p -END PGP SIGNATURE-
Bug#1004091: Starts user services
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Thu, 2022-01-20 at 19:03 +0100, Yuri D'Elia wrote: > The user which is running lightdm starts all "user" services which are > enabled by default, which might include pipewire (and I guess > pulseaudio), gnupg.. synchthing. > > I find this behavior undersiderable. pipewire/pulseaudio could probably > by used by the theme to provide audio in the session, but most other > services only make sense for a real user. > > It seems like lightdm might befinit from a strictly defined list of > services instead of starting a full-fledged user session that results in > this behavior. Hi, I assume you're talking about systemd user services or something? I don't think there's any specific code in lightdm about starting manually pulseaudio, pipewire or anything, so I don't think there's a way to special cases some thing. Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmHu4MIACgkQ3rYcyPpX RFv+jwgA5kojYzryPAqDiNygOhWMIcP78tYHRSJQS+mYLWpAhRR5AvFc6+BZRde+ pR8PS+xqyEorp9OuPgm6QOoGDfVZygVQUEEYL+swilnZddaVv3OMDmbGYX+qO2i+ Qtlc8zg2nBdj251ndgJcWb7S2HIWf5Fr4JJjvJGM+kGmgAWfJn8ivBrwScBLcwyy 5IbXpiTuzrv88dpxfRTDRUFkY44Mcu9mV8B/n2y17JOaGhg8g1vnBTL/5yX8Kkz6 SQv4urcX1Y+D4xdZyLZmAldVMQ3+WmFr8VSJ/Qu2QKPo1hJGd9rX/wAsFeMdbWV6 PFfobXCrCl83dpNztf7cUwhTtqB9JQ== =PShR -END PGP SIGNATURE-
Bug#1000841: xfwm4: Maximized Chromium-based browser windows are too large.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 control: forward -1 https://gitlab.xfce.org/xfce/xfwm4/-/issues/603 On Mon, 2021-11-29 at 22:59 -0500, test wrote: > When I maximize Chromium-based browsers (e.g. Chromium, Brave), the relevant > window renders to an area larger than that of the screen. > > Relevant browser Github issue: https://github.com/brave/brave- > browser/issues/19038 > > It appears to only affect Xfce, and thus likely isn't a bug in the browsers > themselves. Hey, I can't reproduce here myself (with Chromium) but I can see on the above bug that there's been a fix in xfwm4 itself (https://gitlab.xfce.org/xfce/xfwm4/-/commit/488288f6e35d5d3dc077e87fe2ed83129692f62e) That should be part of the next xfwm4 release and we'll pick it by that time. Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmGl5kYACgkQ3rYcyPpX RFu2Ugf/fyd9iTDXToTVQjsaAKZlMTeXmFdiWYuWgbr77Dbs6outrRFdlwspM5EU K2FlOTEEnuhs/AGSjRON3BSreAT38SF52PV7JXjKBLuuPeZ9yWE1+/p/z6OFHvQT q6JGrlHJLvtThcBTg0QVp/G3VtnwK4CAqOuB3hVJycc7Yi04Sied/c8QlfYFFL5I +itRTb8jjojnAlRH8XkmcVqhu34Wzgiza5vJRc+FMcYafEsnugQkfEP4bFE+SNjY frmVHwSg2NMKeJp6hqY9M+4UWr4lPYoPElpIF9AbVoEb5r1NNu6vvJMsBkEcESFM d6dUcuWkbyNQ746rqVj8eYh6h0ES0w== =yp7Q -END PGP SIGNATURE-
Bug#993903: Acknowledgement (xfce4-session: After resuming from suspend, the synaptic touchpad was no longer working)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Sat, 2021-09-25 at 12:29 -0400, Wirawan Purwanto wrote: > So this should be filed as a bug with the XFCE4 settings daemon, I > think (xfce4-settings). The bugfix should be fairly easy, I suppose, > but it will require a hook that is invoked when the computer going to > sleep: when the touchpad is supposed to be disabled only temporarily, > it should be re-enabled upon resumption from sleep. Hi Wirawan, could you check with a recent xfce4-settings then? Stable has 4.16.2 now. Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmFy768ACgkQ3rYcyPpX RFuF5Qf9FVJpW6WYBEbFScLhpSjHybW8AIvOLBO7L+EAWyZDA44ZzIJIk7yueWwA oCg/MqXVIdK+7T/p5fWaPZdn/W33NtcehJ0Rikjwmwt3WZpuprjDHZx0WUSvQp4K MppLvkqNIrXCPMNj3S0LpLE0johLjVarc39CTt2mn6BwCJTw/wL/Titpb2R+7Cig iiSP6A2fp6j627JUfbsTyFP/9GEKxVY9f4vxEmJEuZm3TwSZdjqD3LNT1bvP+y9A h0kXNh2/lCvpXtcGE/gf3P2AsXJthcNrCZDs+dQKt88b7Xn9am5LEzTsnB0kqz10 BcUDD/kY51cE0lYp4V6K7m4FKXGRRQ== =d7MM -END PGP SIGNATURE-
Bug#995366: xfce4-pulseaudio-plugin: repeatedly polls D-Bus names, should watch NameOwnerChanged instead
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 control: forwarded -1 https://gitlab.xfce.org/panel-plugins/xfce4-pulseaudio-plugin/-/issues/65 On Thu, 2021-09-30 at 11:39 +0100, Simon McVittie wrote: > 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). Hi Simon, I've reported the bug upstream: https://gitlab.xfce.org/panel-plugins/xfce4-pulseaudio-plugin/-/issues/65 I'll let you know if something happens there. Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmFy70UACgkQ3rYcyPpX RFsbmggAiW5YoBQRNOSjzwqS7XH4ieBOloNNCLViYNAQ7fmT3wTjKUmmak0oVY+K B6pNlmKoYUMiBUJNWNKXxuGn/r+qMoVbRb0zLMpzlgfhDlRb49iWH+EFSNwXtb7K wD+Tb+39xrXVTyghOzcfrXdAMswRpvYaIznNmhgLmDXyixeE/5tMVBbVfQq2nLa3 Mztx0IfbRkASP760hEcs1wtN9SQ6e3kgtE4TcMY7ZiRJiI34qiUprUbNwRs247G+ jPT+VnwPHnqxs+tybRjkVnkL33mIlsOlknBsGsm7GJgj65Egj2tPqzxsHM/aJKO/ 3jWGXaAIeJkWlqG/gacv/OGlUwvf3w== =05jG -END PGP SIGNATURE-
Re: Disabling Upower support in xfce4-settings
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Control: severity -1 normal On Tue, 2021-08-17 at 22:05 +0200, truetec...@tutanota.com wrote: > Hello, > > When compiled with --enable-upower-glib, xfce4-power-manager doesn't seem to > re-enable laptop displays after suspending the system. And, for that reason, > this is disabled by default upstream... but it was explicitly re-enabled in > Debian for some reason. I reported this issue as a critical bug under > #991788 in xfce4-settings and was told that xfce4 maintainers in Debian > would have to decide whether or not to change this. However, it has been a > while and I want to bring attention to it further, especially as an update > without attention to this feature has already been pushed to unstable. > > Upstream bug report: > https://gitlab.xfce.org/xfce/xfce4-settings/-/issues/222 > Debian bug report: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991788 > Hi Elliot, thanks for the message, but it's usually best to directly send messages to the bug report, that way it's archived on the bug tracker (sorry we didn't reply earlier on it). That's definitely not a “critical” bug though (thus adjusting the severity). And unfortunately the “upstream” fix isn't really good because that actually means just not listening to the lid events, and that's a behavior which I think we do want. As far as I can tell it does work fine on other configurations, but maybe there's an issue with the proprietary NVidia driver (if you can try with nouveau or something like that, it'd be an interesting data point). Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmElQ6kACgkQ3rYcyPpX RFsP2Qf/aaipVYYhL8CdBZ3oL6xF72n3JNhCPOIvCggH+5BAKHG/xdgROsalKJLd l0mI8kHqqotc7SBWd6Rlndz26SvxTMgcIZ5rxrevkq05e8zzhystfCtqK8kIGs1+ LzHA+yS1kPrGqx170I4Dkw/EtdLovXOvJFQwGcGZDvqFq1IEAtvwg3m7OaN06xWj WTYnVPF2ByzC6g3t5VAUglKG8AwKS65fmAJzauv/iCF28QApYcUchQhDu4mLy/Rm TmdWjT/n0Fv2IZiB6HMbGzB8o0p86niUb4+RgKZ58RV1a89exRG6i7vuVt/BAPpF BohukQsr4iVsA5+GyWF0gnY3IZR9Pg== =1nfL -END PGP SIGNATURE-
Bug#990444: thunar: The command in thunar-custom-actions refers to / usr / lib / x86_64-linux-gnu / Thunar / ThunarBulkRename. Correct would be: thunar --bulk-rename
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 control: tag -1 unreproducible moreinfo On Tue, 2021-06-29 at 12:35 +0200, willy4711 wrote: > The command has no effect because there is nothing corresponding in the > directory. Hi Willy, I'm sorry but your bug report is really hard to read, and I'm not sure what you're referring to. In Thunar 4.16.8-1 is shipped /usr/share/applications/thunar-bulk- rename.desktop which contains: grep Exec /usr/share/applications/thunar-bulk-rename.desktop Exec=thunar --bulk-rename %F That file is in the thunar package. Feel free to provide more information if I missed something. Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmDbbhYACgkQ3rYcyPpX RFstZAgAuL7VCJJBr19LcXWqAz8zKvnRx3ZMircoK2Rb079/PVZglE2nKiA/h36q qr0M4BVNvzcfAVbpXVZb7iGc1qGamPrzUFnEmxIGvGNTf5/TAM1Y6hDQqQtPOoAs rmtxL9KE0CQomcGUzloPdek6MCGUl4nz65U7vzrWlYBCnr1/QUpk/IMwEPjtlMTM yJ07NSEBSah9gy0xpaj6GKNwO7zaicflI/hjmAM/CcFAiH7Ukl66FvoTnMiFZ1U5 +Ce0W9ijKffT+ggmCXqOPy9beg3/bxBhtkcygTqPgsoYsb75/vi+HUjpf2Jh2vrj G2xkEIjq7olQlCtT0/9c60pAjf5VZA== =dtax -END PGP SIGNATURE-
Bug#989833: thunar: Thunar does not auto-refresh when directory contents are changed
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Mon, 2021-06-14 at 08:13 -0500, sudoer wrote: > Seeing as there are no other bug reports for an issue this big, it makes > me think that only my system is affected. I can record my screen to show > the behavior of this bug, if needed. Hi, indeed, it looks that something is odd on your system. I assume you're testing on a regular, local filesystem and not on a remote filesystem? Thunar relies on gio/gvfs for all filesystems operations, so maybe there's something fishy here. You can try to quit all thunar instances (run thunar -q) then run Thunar from a terminal in case something is shown on the output. Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmDIqncACgkQ3rYcyPpX RFveYAgAp1s++rl82LTUGnPP+3xFnlNAB0RbvOOG1aPbCNWLwLm9m8UcF4p8kKnz sAdFTWbdm9S6KdipQKuY0QqV7upp4y6izSv717m/+ZPE6XqeGttSl/LZ57yiObM8 jRzg2+DVoVWngOS+RH+HSzI6W4GiJ35ZzlH6toyVW4dDcBDqV2c73pJIUMbzRgCV Xbxc3P9/8rzUEh7vO5FPrEnlK8GTS2v749bRWLCIsxfLuPcKUeTV8XW1alXCRRq8 B/qDxmKnpKlfGs0Nf1HGDBlv/CIHlbeWncOjWhDFUUNiQu69KdeymF5tIEO2tehw Y7PGWteBVqwyop8SLzEq3UhMdcYddQ== =g73v -END PGP SIGNATURE-
Bug#989548: light-locker: Username field has focus when unlocking
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 [please keep the bug number on CC so exchanges are public, this is a bug report and not a support channel :)] On Tue, 2021-06-08 at 08:43 +0100, Keith Edmunds wrote: > I've just locked the screen and the dialog box appears with no username > populated. > > Even if your hypothesis were correct, why is the focus on the username > field? If the username is populated, the focus should be on the password > field. Here the behavior is as you say: the username is populated (and actually selected), but the focus in on the password field (and as I understand it, it's the behavior you had as well before the Bullseye upgrade). > > I can record a video of the behaviour I see if you want. I don't think that's really necessary, I trust you on this, I just don't know what happens on your box (which doesn't on mine). You might want to take a look at logs in /var/log/lightdm (and maybe .xsession-errors as well). Did you maybe change something in the default lightdm configuration (like having the userlist displayed?). Is accountsservice installed on your box? Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmC/K2YACgkQ3rYcyPpX RFu2DAf/euW6Kyyn/noYc8KV5xZ+IVQ18xoqTuxvJF2/XY2T4N0N8r4DRccXmamP VSxHkyufIvHtD98OIvV5jz06MaTvRvIjp1HQ29EmfBu6HLHbgFG0sb8Dntdw6W5c g+OnN3ky2ILcyUVOxJtF1gJOL610lkwJwY5diYVJVe2OYWaIuv1ANsLoe3whYEaY xi/tBXJaDBffG+WiTFK3NOQhs6gvWJYJriHUbcN6f0ovY+W6OrCdrJ0CFrveu0hg 1BoI9k0p73KNIz+BqqPXP5KA3l4nXaBT50cmOslCpJUmBvqpG9NdzvKxRqdrfdEg l6P4KjvCE3E6Q/Gl6nfCzK5+6lBMYQ== =ysAi -END PGP SIGNATURE-
Bug#989548: light-locker: Username field has focus when unlocking
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 control: tag -1 unreproducible moreinfo On Mon, 2021-06-07 at 09:55 +0100, Keith Edmunds wrote: New installation of Bullseye with XFCE and light-locker. When the screen is locked, the username is not populated and it also has focus. Previous versions of light-locker would fill in the username and put the focus on the password field. If one is used to the previous behaviour and starts typing the password, it appears in clear text in the username field. The username field should be populated with the logged-in user as that is by far the most likely user to be unlocking the system. Hi Keith, this is exactly the behavior I have here. I'm running a sid box, but it has the same light-locker version (and I'm assuming you also use lightdm-gtk- greeter, which also has the same version in both). Are you sure you're not entering a key or something which would erase the field content (since it's focused)? Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmC/G18ACgkQ3rYcyPpX RFtEKgf/Wa7T62T0yhmpAv7d0AVNi+N8UuYOb9yPHc/yAW+CausLRjtu4THOJ3JZ Z/PEAe4t7AqnqHwWLp7313iq00BQv2sBwLCI5fEdlGWjqIgmblPY/MBxeCy9eFDY p0mK3TIp53z89E1G3Z5qmGqcmL9RAytG9GXGe3ArChumHVMB+W38PQ03Ni3Lp1L+ 3mDLDtoMxzZmxn2Ef+qRi4FqHmI5h7H46E9jz9+dFazuOl5TNd3sonz7FHORIXz8 aomJt+C3N3yPFpQD+fnS7BC8VDltPhAXPjg4mQ/2la0aoKNNRJIi0AUr0MW49OeR 700vq1WzbLzTaTqymfv1i6EJWP4zhg== =LbL7 -END PGP SIGNATURE-
Bug#988394: thunar: CVE-2021-32563
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Thu, 2021-05-13 at 20:58 +0200, Salvatore Bonaccorso wrote: > Thank you! Btw, I sitll would try to check if release team would > accept 4.16.8 itself. Note I'm as well not sure about if this will > need a DSA or can be fixed via point release, but given your double > hat on I will leave that decision to you :) Yeah I reached out to the release team, and will follow up with a bug at their request. For stable I'm unsure. I'm not sure it warrants a DSA indeed, but in any case stable has 1.8.4 and I'm unsure how hard it is to backport the fixes, I'll investigate. Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmCeQ5gACgkQ3rYcyPpX RFua1Qf7BItMSf215l3koGvolA6w/nRsdCSkPOoFQDf7VFsxdZyofJoVH+lYwU8/ N7FciTdOMkGfcGVPH0IrYEBPVPDgbgyMcVwgbroeaC4d3bHD33+k8LZS7WWDa+Ky XCk6dFrKaFRv/vHK/BrjuJq4J4MBfkjPoyyDB24o67qIQsDUUgw9inxkYqe1SmUw ml5GwYe9Moojtz5Ydvy0c1A+I6dWvgMeXCAQIkMQVTzDouPL5obf3iGD/coHczQO 6elhaw1wCTPl7zDhy1yrtjGX5w7m2fqtCOeEcuA+3/IViDDDcJYrK7H9fBcykkZ4 EDQ3Ts4RS1lsc7EbvljKGzAkKau8hA== =6pz1 -END PGP SIGNATURE-
Bug#988394: thunar: CVE-2021-32563
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Tue, 2021-05-11 at 21:45 +0200, Salvatore Bonaccorso wrote: > The following vulnerability was published for thunar. > > CVE-2021-32563[0]: > > An issue was discovered in Thunar before 4.16.7 and 4.17.x before > > 4.17.2. When called with a regular file as a command-line argument, it > > delegates to a different program (based on the file type) without user > > confirmation. This could be used to achieve code execution. > > > If you fix the vulnerability please also make sure to include the > CVE (Common Vulnerabilities & Exposures) id in your changelog entry. Hi Salvatore, thanks for the heads up. We have Thunar 4.16.3 in testing and 4.16.4 in sid. It'd be best to update everything to 4.16.8 but I'm unsure the release team will like that, so I'll also look at isolating the fix. Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmCdXGEACgkQ3rYcyPpX RFsjPAgA7FaKksal1xCLD/k/Y5I2Q4RkH3X/kxpObKguWPLAU+1Q/hzTbY9GTsla BpXhqp0JBo/s++5d5IMWtegF2M2DPmfe0yGV86sxFLJj4bKweIG62otjUuxr8dAI yJY9mLzypHR9ywcbOZsD1U2wzaSkJkOj7b+SXLQyowTuwda+LwPNAJNDbo8ishYh wUSodVcbxeZIeKF7dIn2tWpxQ69LRYYVaJm5u2ZZpGWfe0oJlYzFEha6XLc+CAsv SAWB+MwXTQ9INdImN8BlPUHdxK61AUD6UkxYN+hIPhwC2nIrG1d/IZDC8B7Gw/8m rFpkfO1jXgIV1wddJxdFl1YlL5ITWw== =W5K2 -END PGP SIGNATURE-
Bug#986267: xfce4-appfinder: Application Finder doesn't show up xfce4's "Add New Items" window
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Mon, 2021-05-10 at 00:21 -0400, Ron Murray wrote: > Never mind. I thought I'd point out a deficiency, but you seem to be more > interested in how I found it than the deficiency itself. Hi Ron, the point I was trying to make in my mail is that I'm unsure which deficiency you were pointing or if there is any. That's why I was asking some clarification and a way to reproduce the behaviour you're seeing. Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmCY+VQACgkQ3rYcyPpX RFsotAf/UecRm7sDygjtey3AjlwFSkYCCksRli1lDvYh2/oldK5AMBcIYtU/MHo5 hf+wJa6JqkBow8txGU0GmuyUDD8zoVK9TygYUkkK1t/Cibok0iNLqlmz0okK2Fjz UeaW9UxyPnqnEFbln2kHRaZGd5R7/Q4vNn246OSMyVPDk6ME8APzT+vjB1W0zlRW gQfhTdd5MTAHH8XeDpXIhUF8SukLr9tfq6aP2KzmMv4kdjtg2pzD8rOfeDtMaeYI KNWtWohevtDw07hDUJmdb1DLCugf5KC3/e6yc0iK2/Q3B9imdAzsXouMZFntq89u f7QptGhHzq9RpwntIuuGtDmnhBCnWg== =Gvob -END PGP SIGNATURE-
