+1,11 @@
+strongswan (6.0.1-6) unstable; urgency=medium
+
+ * d/control: keep strongswan-charon and strongswan-starter as acceptable
+dependencies for strongswan
+(Closes: #1109510)
+
+ -- Yves-Alexis Perez Tue, 22 Jul 2025 18:24:43 +0200
+
strongswan (6.0.1-5) unstable; urgency=medium
ternate dependency for Trixie
> and do do an upload soon as time is running out.
I guess so…
- --
Yves-Alexis
-BEGIN PGP SIGNATURE-
iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmh/t4gACgkQ3rYcyPpX
RFuvSAgAtFc/s/rDb91CcOMPR8W55GAYlbJHYlab+w+B2y0KgFdvkicRsF0FrmAI
3gXIzxhQWMgx8gbydhuntRflJxp
orky if I remove the
> > alternate dependency at that point?
>
> For Forky you would have to do the transition dummy package and
> maintainer scripts conversion then.
Hey Jochen
as already said, that's not an option for us. There's no plan to retire
strongswan-charon (an
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Mon, 2025-07-21 at 18:42 +0200, Yves-Alexis Perez wrote:
> > If both should be in trixie I would say:
> >
> > Package: strongswan
> > Depends: charon-systemd | strongswan-charon, strongswan-swanctl
>
> Ah, good poi
configuration, and migrate on their own term.
>
> > So I'm not sure how to express that in apt relationships.
>
> If both should be in trixie I would say:
>
> Package: strongswan
> Depends: charon-systemd | strongswan-charon, strongswan-swanctl
Ah, goo
an metapackage. We recommend people to migrate to the new
daemon, and for new install that'll be the case. For old installations one
could actually wonder if we should actually migrate, but in any case we would
still want to actually upgrade the packages.
So I'm not sure how to
ebian/changelog 2025-07-19 18:32:45.0 +0200
@@ -1,3 +1,10 @@
+xfce4 (4.20.1) unstable; urgency=medium
+
+ * d/control: update standards version to 4.7.2
+ * d/control: recommends mate-polkit (Closes: #1090384)
+
+ -- Yves-Alexis Perez Sat, 19 Jul 2025 18:32:45 +0200
+
xfce4
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sun, 2025-07-20 at 12:25 +0200, Yves-Alexis Perez wrote:
> In any case, help would be appreciated on how to interpret apt output and
> how
> to make it accept the removal of strongswan-charon for upgrading the
> strongswan metapackage
7;m not too sure what happens here.
> > There's indeed a change in the metapackage dependencies for Bookworm and I
> > had
> > the impression everything was working.
> >
> > I noticed you used dist-upgrade and not full upgrade. Does that change
> > anything
#x27;s indeed a change in the metapackage dependencies for Bookworm and I had
the impression everything was working.
I noticed you used dist-upgrade and not full upgrade. Does that change
anything? I'll try to reproduce using the above command line but if y
ng another desktop installed
might not get a running agent (because of the OnlyShowIn part, especially
since packages with Provides: polkit-1-auth-agent include gnome-shell or
cinnamon) but I think I'm ok with that. Besides this bug I don't have the
feeling that a lot of people are actually
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Wed, 2025-07-16 at 16:17 +0100, Peter Blackman wrote:
> On 14/07/2025 20:34, Yves-Alexis Perez wrote:
> > Right now, this is a strong NACK for the NMU, because of the lack of
> > coordination, especially this late in the fre
you can use merge request on
Salsa, that would be easier for us than manually merging the changes after an
NMU.
Regards,
- --
Yves-Alexis
-BEGIN PGP SIGNATURE-
iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmh1W94ACgkQ3rYcyPpX
RFutBQgA0g1BHO4t978huCAi/dKGWQgO0uwZOw/7L9TqJ8mAhh+ymioRA+Lyz
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
control: forwarded -1 https://gitlab.xfce.org/xfce/xfwm4/-/issues/867
On Fri, 2025-06-20 at 21:38 +0200, Adam Chyła wrote:
> Hey Yves-Alexis,
>
> thank you for your response.
>
> On 20.06.2025 o 08:59, Yves-Alexis Perez wrote
which
should be used for the calculation). Maybe it's something similar for you (in
case you have a smaller display attached)?
Regards,
- --
Yves-Alexis
-BEGIN PGP SIGNATURE-
iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmhVBsYACgkQ3rYcyPpX
RFvvJggApHzFkGLOCMb1DbYgt
plit view
> click on left view, open parent
> create folder X
> in left view move Y to X
> click on right view
> crash
Hi,
thanks for the report, but I don't seem to be able to reproduce here using
your detailed steps
ion 'GDK_IS_PIXBUF (pixbuf)' failed
>
> (thunar:7316): GdkPixbuf-CRITICAL **: 14:58:52.249:
> gdk_pixbuf_get_pixels_with_length: assertion 'GDK_IS_PIXBUF (pixbuf)' failed
> Segmentation fault
Hi,
is that bug still reproducible for you on current (
sktop4.
>
> I suggest also looking at https://bugs.debian.org/948339 . Maybe
> that's unreproducible now. (I don't use Xfce myself.)
>
I'll ask the reporter then :)
Regards,
- --
Yves-Alexis
-BEGIN PGP SIGNATURE-
iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3
metic expression in line 52:
Indeed, that was caused by the fix for #1100179.
I've backported the upstream patch and will upload it asap.
Regards,
- --
Yves-Alexis
-BEGIN PGP SIGNATURE-
iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmfnscsACgkQ3rYcyPpX
RFufngf+PFKHDcabtUxvr9besYi2Zz13kISYI
e modern) strongswan-swanctl.
Could you please upgrade the dependencies in the test and/or the
package, so strongSwan can migrate?
Don't hesitate to ask/discuss this with me as I might be totally wrong
about the vpnc dependencies and/or autopkgtest.
Thanks in advance!
Regards.
--
Yves-Alex
y not sure of
what the problem really is, and there's no such thing as "xfce print dialog".
Maybe there's GTK+ print dialog but that's it.
Sorry,
- --
Yves-Alexis
-BEGIN PGP SIGNATURE-
iQEzBAEBCAAdFiEE8vi34Qgf
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Mon, 2025-03-03 at 08:46 +0100, Yves-Alexis Perez wrote:
> Hey Fiona, thanks for the report. I've forwarded the bug upstream because
> it'd
> be nice to not crash in this situation, but I'll check for adding the build-
&g
ng libgtk-layer-shell-dev to Build-Depends solves the issue, trivial
> patch attached.
Hey Fiona, thanks for the report. I've forwarded the bug upstream because it'd
be nice to not crash in this situation, but I'll check for adding the build-
dep in case there are no side ef
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Wed, 2025-02-26 at 12:47 +, Douglas Kosovic wrote:
> Hi Yves-Alexis,
>
> > Sorry for breaking your use case, I didn't really check the reverse
> > dependencies of the strongswan metapackage (to be honest that
>
won't happen though.
>
> Thanks for your kind response, and sorry again to have failed to properly
> read the NEWS.
No problem, hopefully your problems are now solved.
Regards,
- --
Yves-Alexis
-BEGIN PGP SIGNATURE-
iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAme+
On Tue, Feb 25, 2025 at 11:13:40AM +0100, Yves-Alexis Perez wrote:
> On Tue, Feb 25, 2025 at 10:03:37AM +, Luca Boccassi wrote:
> > On Tue, 25 Feb 2025 at 09:57, Yves-Alexis Perez wrote:
> > Would you be able to provide a patch that fixes them?
>
> Unfortunately no, but
On Tue, Feb 25, 2025 at 11:26:58AM +0100, Yves-Alexis Perez wrote:
> On Tue, Feb 25, 2025 at 11:13:40AM +0100, Yves-Alexis Perez wrote:
> > On Tue, Feb 25, 2025 at 10:03:37AM +, Luca Boccassi wrote:
> > > On Tue, 25 Feb 2025 at 09:57, Yves-Alexis Perez wrote:
> >
he charon daemon itself is in the strongswan-charon package, while the
strongswan-starter package provides the ipsec(8) command reading the
ipsec.conf to control the daemon through the stroke plugin. If you need
both, then depends on both.
Regards,
--
Yves-Alexis
On Tue, Feb 25, 2025 at 10:03:37AM +, Luca Boccassi wrote:
> On Tue, 25 Feb 2025 at 09:57, Yves-Alexis Perez wrote:
> >
> > Hi,
> >
> > it seems that the efitools NMU actually broke the package (at least for
> > my use case).
> >
> > efitools 1.
ersion,
> AFAIU. You might want to consider to include it for 6.0.0.
Hi, thanks for the heads up. I think we're not too far from a 6.0.1
release so I think I'll just wait for it to happen.
Regards,
--
Yves-Alexis Perez
ones.
Regards,
--
Yves-Alexis
l encouraged to
migrate from the ipsec.conf (and ipsec(8) and /usr/lib/charon) to the
swanct.conf way. Just pull the strongswan metapackage and you should be good
to start the transition to the configuration.
Regards,
- --
Yves-Alexis
-BEGIN PGP SIGNATURE-
ed the bug on a piupart run on salsa CI:
https://salsa.debian.org/debian/strongswan/-/jobs/7132445#L5105
I guess that could also happens in buildds or minimal containers.
Not sure about the correct solution but feel free to discuss it here :)
Regards,
--
Yves-Alexis
-- System Information:
Debian
I tried to contact Kees Cook on Mastodon about that
(https://mastodon.social/@corsac/111811338805308373 ) but it didn't go
anywhere.
Adding Kees to the CC: list as it might be a better way to reach him :)
Regards,
--
Yves-Alexis
uot;No hard-coded default proposals are passed from starter to the stroke
> plugin anymore (the IKE proposal used curve25519 since 5.5.2, which is
> an optional plugin)."
Hi Carl-Daniel, thanks for that, I somehow missed it (for a long time). I'm
marking as closed with that version
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Mon, 2025-02-17 at 16:07 -0700, Soren Stoutner wrote:
> Yves-Alexis,
>
> I have just taken over maintenance of the courier-authlib-ldap package. I
> apologize that nobody responded to your bug report in a timely manner.
Ahah, n
just the lightdm-gtk-greeter.
Ok. So it's more about something with the whole device stack. I have no clue
here so help from the systemd/loginctl/dbus folks will likely be needed.
Since it wasn't clear: I'm not adding lightdm user to the render group, that
should be done dynam
don't have permission access in the log,
and obviously it works just fine for everyone else.
I'm unsure if it's mali-related (I don't really see why) or more software
related.
Regards,
- --
Yves-Alexis
-BEGIN PGP SIGNATURE-
iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAm
oup::rw-
mask::rw-
other::---
Regards,
- --
Yves-Alexis
-BEGIN PGP SIGNATURE-
iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmewWb0ACgkQ3rYcyPpX
RFtCTggAsonZ7XFmUBjPgkfbi5MrW421CauHLj8PioFYSlQWGYVrSFcJSQ03Yz5d
mWyAUrK9gHFgOLyFLuUyITTBtb9osUjOOClFvO3cdircRPjCnUiNY3Tn+yfoM9sM
ZL7JG
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Mon, 2025-02-10 at 11:47 +, mag...@autistici.org wrote:
> Hi Yves-Alexis, hi Helmut!
>
> @Helmut: I'm writing to you too because Yves-Alexis raised
> the severity of the bug to serious and Yves-Alexis is asking
> below i
Hi,
this looks like a duplicate/consequence of #1094494 so I'm merging the bugs.
- --
Yves-Alexis
-BEGIN PGP SIGNATURE-
iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmemGnkACgkQ3rYcyPpX
RFs4zQgAk1ROmvqUggV2trr3F12AdnKUb9t8dftaBGuovoPZZL3hZgDzJombmkpW
MenilNpxVbLQINM1yXtTBykBY04Ca
how the tag system works, so patch welcome :)
Regards,
- --
Yves-Alexis
-BEGIN PGP SIGNATURE-
iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmejx4YACgkQ3rYcyPpX
RFtsGQgAlmoepf5PwTaOQyfDs5KyIiV03+5r4YXN8HqFiQfa2Ktal3nYDtiOtQD8
Z3kUuXeeO7Lo673pstkfEmtSm9pgxDJJrVNhPbQKS9jY/5MhwEk3R6YFh+Z
eed to look at versions and
> more when I have time.
Thanks for the information, and yes we'll need version information if you have
it so we can properly mark this as fixed.
Regards,
- --
Yves-Alexis
-BEGIN PGP SIGNATURE-
iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmegy/
s but where is the documentation?
Hi everyone,
sorry but this bug doesn't really make sense to me considering it's been
opened against 4.18.3-2 and various people commented afterwards with things
which look a bit different.
Ael, could you elaborate on this and confirm the version
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Fri, 2025-01-24 at 08:12 +0100, Petter Reinholdtsen wrote:
> Dear gtkpod Maintainers and Yves-Alexis Perez,
>
> Is there anything more I can do to help you get this Appstream fix into
> unstable? At the moment the AppStream met
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sat, 2025-01-18 at 13:14 +, mag...@autistici.org wrote:
> i Yves-Alexis, hi Debian Xfce Maintainers,
>
> On 2024-10-11 09:09, Debian Bug Tracking System wrote:
>
> > This is an automatic notification regarding your Bug re
ble polkit
> agent for XFCE, then the XFCE team will need to fork it and become the new
> upstream maintainers of the fork.
>
On this box I'm apparently indeed using policykit-1-gnome. I think we
might use mate-polkit without too much issues (although it brings
accountsservice as a new dependency).
Regards,
--
Yves-Alexis
pacity.
Yes sure, go ahead!
Regards,
- --
Yves-Alexis
-BEGIN PGP SIGNATURE-
iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmde/+IACgkQ3rYcyPpX
RFt3sQf/amEW3P97+QssKb4IXb94nHXgBmvtgmeJ+TMLoZuGNz7fBIDR/WlABjv0
sWgtrJnOd+jBHWnPBgFi6n0jU5WpLgM3YTK8IDUYr8IK1WI
t really doing much work on murrine-themes
anymore so feel free to provide a patch (afair the commands just moving files
around so there might be an easy way to do it rootless).
Regards,
- --
Yves-Alexis
-BEGIN PGP SIGNATURE-
iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmdXHj
x27;ll keep
it in mind.
I'll update the network manager dependencies though.
Regards,
- --
Yves-Alexis
-BEGIN PGP SIGNATURE-
iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmc0TrMACgkQ3rYcyPpX
RFvZHwf9F2DNvLE5mPH62V7K2rxlXuYnppD4dOUFg4zRGt1YoFmPKAV2NyM8KlXy
oqb/w
packages to in order to made "working" a features that is
> enabled as defaut.
>
> I suggest to disable it as default and add an explanation in the config file
> that the feature require AccountsSetting.
Yes, that looks sensible indeed.
Regards,
- --
cessary, it's not even a basic
feature. It's currently in the 'Suggests' field and I think it's just fine
that way. Adding it to Recommends would install and run it by default and I
don't think we want that at this point.
Regards,
- -
gged as "won't fix" for now.
Eh, thanks for the precision.
I guess work from both Debian maintainer and upstream.
Do you know if they are aware of the patch by the way?
- --
Yves-Alexis
-BEGIN PGP SIGNATURE-
iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rY
install accountsservice package? And then report back.
Regards,
- --
Yves-Alexis
-BEGIN PGP SIGNATURE-
iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmcamPYACgkQ3rYcyPpX
RFscqAgApCJ4qd305XI9AwDg1nB2I6BDWiswEAezHFB+7FfJEz7IKz+9of37eMdF
5UQHM+abpJIiwxIKzc7J3UrSr+q90Cu9DIZwDk9S526St2C5TU1+JZmR
t all.
Also I'm not sure I see the link with org.gnome.settings-
daemon.plugins.background but maybe some logs would help.
Regards,
- --
Yves-Alexis
-BEGIN PGP SIGNATURE-
iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmcZCVsACgkQ3rYcyPpX
RFv5SQgAh2TL/C/CJgEBLmiQWrCctm3ehb+ZNQE270
either nm-applet or nm-connection-editor, so we
use both features (although I guess nm-applet is the most used).
I'm not sure if there are graphical frontend for systemd-networkd but that
could be an alternative as well (never played with it though).
Regards,
- --
Yves-Alexis
-BEGIN PG
ngswan-starter package already finds a file I think we
should respect the permissions there, and I'm not really sure how often
people statoverride them, so I'm not sure I want the package to "fix"
the permissions in case they're different from 700.
Regards,
--
Yves-Alexis Perez
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Tue, 2024-09-17 at 17:52 -0400, NullRien wrote:
> Hello anything else I can do?
Yes, please:
- - provide the information requested earlier
- - use the bug email address and not just my own email address
Regards,
- --
Yves-Alexis
-BE
uite sure LightDM is used when
installing KDE Plasma desktop. Can you double check?
Also it'd help to use reportbug so we have all the information on your system
Regards,
- --
Yves-Alexis
-BEGIN PGP SIGNATURE-
iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmbj784ACgkQ3rYcyPpX
RFv
gt; the old machine.
When you have a stable situation can you please retry and report back?
>
> > So it's not the *login* (from a 'clean' lightdm with noone logged in)
> > but really the *change user* feature?
>
> Yes it is and this feature shows the us
g, /var/log/auth.log, /var/log/lightdm/*...) of the various
attempts?
Can you login with those different users on the console? On another DM like
gdm3?
I don't experience this here so there's likely an issue on your end but it's a
bit hard to identify it like this.
Regards,
-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Wed, 2024-09-04 at 11:44 +0200, nicolas wrote:
> On 04/09/2024 11:25:39, Yves-Alexis Perez wrote:
>
> I don’t have /var/log/syslog nor /var/log/auth.log my machine is rather
> young, I haven’t reinstalled everything).
> In /
d doesnt work here:
- - login with 'user1' from lightdm
- - logout from 'user1'
- - login with 'user2' from lightdm
- - logout from 'user2'
- - login with 'user1' from lightdm
- - *changing* from `user1` to `use
nything I can try to help you understand that?
Well if you notice any new, undesirable behavior, please share it here. And I
guess we'll see once the new version gains exposure if there are any side
effect reported.
Regards,
- --
Yv
en connected, sleeping
> when the screensaver is active, etc.
>
> Is there something else you want me to try?
I wasn't really worried about not fixing the problem, but more about having
side effects of losing the LID closure detection.
- --
On Mon, Jul 29, 2024 at 12:25:19PM +0200, Chris Hofstaedtler wrote:
> Hi,
>
> On Mon, Jul 29, 2024 at 12:07:38PM +0200, Yves-Alexis Perez wrote:
> > > Per the discussion on debian-devel, Debian will switch to wtmpdb for
> > > Y2038-safe wtmp recording. If your
o libpam-wtmpdb or libwtmpdb.
>
> https://lists.debian.org/debian-devel/2024/04/msg00406.html
>
Hi Chris,
xfce4-terminal uses libutempter[0] for utmp/wtmp management so I'd say
support should come from there. I've noticed #1072237 but I'm not sure
about the outcome.
[0] https://t
hink to disable the laptop screen when
the lid is closed.
It'd be best to fix the detection code there, but we can see what happens at
least.
Regards,
- --
Yves-Alexis
-BEGIN PGP SIGNATURE-
iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmamBWEACgkQ3rYcyPpX
RFu2cwf/Uscw4cS1kEX11
orts.
Yes, to be honest I'm unlikely to backport 1.32 to Bookworm, so I guess I'll
go with the move.
Thanks for the reply!
Regards,
- --
Yves-Alexis
-BEGIN PGP SIGNATURE-
iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmZ130cACgkQ3rYcyPpX
RFtlYwgAovVHigiLsFB1Yrq3gHj3SZ
m.service
Hey Helmut,
the lightdm.service file is installed via debian/lightdm.install. My first
impulse would be to just move that to /usr/lib/systemd/system. do you see any
issue with that?
Regards,
- --
Yves-Alexis
-BEGIN PGP SIGNATURE-
iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFs
configuration file.
I had to add (actually uncomment) a:
Listen localhost:631
line to cupsd.conf but I'd rather not do that and would prefer to stick
to unix socket (which are still marked as supported in the cupsd.conf
manpage).
Regards,
--
Yves-Alexis
-- System Information:
Debian Release: trixi
Package: compiz
Version: 2:0.8.18-5.2
Severity: grave
Tags: upstream
Justification: renders package unusable
Dear Maintainer,
* What led up to the situation?
After upgrading libxml2 to 2.12.7+dfsg-2, compiz failed to start.
* What exactly did you do (or not do) that was effective (or ineffect
ifferent 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+n8GawA4mvDAwah4ui8C4R27
Package: mousetweaks
Version: 3.32.0-4
Severity: important
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
sudo apt update
sudo apt install mousetweaks
mousetweaks
** (mousetweaks:5734): CRITICAL **: 08:56:17.1
specially for other shells (I think zsh still uses it
but not all I think) and not graphical sessions.
Regards,
- --
Yves-Alexis
-BEGIN PGP SIGNATURE-
iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmY7YGgACgkQ3rYcyPpX
RFvbsAf/dKuiRbySXE4iYEONIt3Exw4ZqeECQGovA/cCq7fSVpPN/qAtA
x27;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-
ttps://github.com/canonical/lightdm/issues/352
Regards,
- --
Yves-Alexis
-BEGIN PGP SIGNATURE-
iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmYcLKoACgkQ3rYcyPpX
RFvszggAuBC/jVutExKct2P2GNDoxIG8UHEkD0q0nZwzY3ojcVYF4Za4+g5i9HyJ
khWQgqXzwxA5aWvOn4
hine needs to be fixed, or just not enabled? I cant say for sure but it
looks like the easiest way for me.
Regards,
- --
Yves-Alexis
-BEGIN PGP SIGNATURE-
iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmYTpxEACgkQ3rYcyPpX
RFubwAf7BLanLdiDs0ERBersGiLzc0+SF2Fxid7d2k4hfANYpBNvGYuM4PHwP4Up
Pizj
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
RFu
am commits and issues and couldn't see anything there.
Regards,
- --
Yves-Alexis
-BEGIN PGP SIGNATURE-
iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmYPlZEACgkQ3rYcyPpX
RFtkIwf/QZUtuSvH9DPGorTFJ/RybRfdEYONU8kLD8dOFGTXiNRcQYmSCTU/fH5B
4h0VxRWFXlF8TfBN0LmvgM+Rqzx9bT+5ZR+h8SGXL4UvH/W1
e, not finding the libplist configuration.
Hi Doko,
ifuse doesn't seem to FTBFS in unstable or testing *yet*. We still have the
old plist there, plist-2.0 is in experimental.
I'm downgrading the severity then but we'll upload a similar patch when
possible.
Thanks for the help!
Rega
ething too.
>
Hi Leandro,
what's the status on this? As Michael noted below, compose V1 isn't maintained
upstream anymore and it'd be nice to switch to V2 in Debian. I know V2 is in
Go and might bring some challenges, but having some kind of status update
would be nice.
Regards,
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 th
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
R
-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 S
Output from gdb (first try with doomsday-dbgsym, doomsday-common-dbgsym,
libsdl2-2.0-0-dbgsym) can be found in attachment.
Tell me to install more debug packages.
ylb
doomsday_gdb_output.txt.7z
Description: application/7z-compressed
Sorry, your answer on Sun, 4 Feb 2024 12:31:35 + was marked 'spam'
by my provider,
so i didn't notice it until now.
Here are some informations about my environment :
System:
Host: jupiter Kernel: 6.6.13-amd64 arch: x86_64 bits: 64
Desktop: Xfce v: 4.18.1 Distro: Debian GNU/Linux trixie/
x27;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-Ale
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-
iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmXAne4AC
ed 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-
iQEzBAEBCAAdFiEE8vi34Qgfo83x35g
Package: doomsday
Version: 2.3.1+ds1-1+b2
Severity: grave
Justification: renders package unusable
Dear Maintainer,
* What led up to the situation?
loading wad file (doom /doom2/heretic/...)
* What exactly did you do (or not do) that was effective (or
ineffective)?
upgraded libsdl2-2.0-0 (2
o servers to test latency.
>
> * What outcome did you expect instead?
>
> successful run
Same thing happens here. As far as I can tell that makes the package pretty
unusable so I guess the severity could be raised.
Regards,
- --
Yves-Alexis
-BEGIN PGP SIGNATURE-
iQE
ad 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-
iQEzBAEBCAAdFiEE8vi34Qgf
about the map { $_ => 1 } structure and the
> test suite.
Unfortunately I'm not fluent at all in perl :)
- --
Yves-Alexis
-BEGIN PGP SIGNATURE-
iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmV6DU8ACgkQ3rYcyPpX
RFvYeAf+P9NRJc1n3Y4RQ9ZspdD+QeMnnCSLT/a8Ay3qzJSMeyu7HcDq
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Tue, 2023-12-12 at 17:18 -0500, Antoine Beaupré wrote:
> On 2018-05-21 16:01:59, Yves-Alexis Perez wrote:
> > subject mostly says it all, but it'd be nice if KGB could support
> > password-protected IRC channels for not
see a reply to my bug submission
from more than 12 years ago. But thanks, I guess?
Regards,
- --
Yves-Alexis
-BEGIN PGP SIGNATURE-
iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmVo4X8ACgkQ3rYcyPpX
RFsXMAf/WrUsLPQw958f9kNcn9D/1yXc/ekH3d+Hi9CpJxNKLWVuqIX1UD
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?
Re
-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.
Regard
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
gt; Sessions=
> IdleHint=yes
> IdleSinceHint=0
> IdleSinceHintMonotonic=0
And does LightDM starts correctly with the greeter?
- --
Yves-Alexis
-BEGIN PGP SIGNATURE-
iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmUbGlIACgkQ3rYcyPpX
RFsO8QgAtbR7v03OgNuubCD1/IK8s/quSCltCg9ctR2
1 - 100 of 6241 matches
Mail list logo
