-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),
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Tue, 2024-05-07 at 01:28 +0200, Santiago Vila wrote:
> My plan for base-files is to stop overriding the PATH in /etc/profile.
Note that /etc/profile is a configuration file for bourne shells. While it's a
common path, it's not especially for
-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
-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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sun, 2024-04-07 at 10:39 +0200, Paul Gevers wrote:
> Your package has an autopkgtest, great. I recently added support for
> isolation-machine tests on ci.debian.net for amd64 and added your
> package to the list to use that. However, it fails.
-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
-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
>
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Control: severity -1 important
On Tue, 2024-03-26 at 12:25 +0100, Matthias Klose wrote:
> Package: src:ifuse
> Version: 1.1.4~git20181007.3b00243-1
> Severity: serious
> Tags: sid trixie ftbfs patch
>
> ifuse ftbfs from source, not finding the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Wed, 16 Aug 2023 20:39:25 -0300 Leandro Cunha
wrote:
> Hi,
>
> I've been talking to one of them these days and he's been busy lately.
> But he said next month he should work on it. I should see if I can
> help with something too.
>
Hi Leandro,
-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?
>
>
-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
-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-
-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
-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.
-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 PGP SIGNED MESSAGE-
Hash: SHA256
Control: severity -1 serious
On Sat, 26 Nov 2022 08:35:40 +0100 cuboid_06_wavers
wrote:
> Package: speedtest-cli
> Version: 2.1.3-2
> Severity: important
> X-Debbugs-Cc: doczipe...@debian.home
>
> Dear Maintainer,
>
> * What led up to the
-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
>
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Wed, 2023-12-13 at 09:06 -0500, Antoine Beaupré wrote:
> What I would love is some review of my perl-fu, just visually, without
> running anything. I made some comments on the MR that expand on that;
> I'm particularly wondering about the map {
-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 fo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Thu, 2023-11-30 at 17:06 +0100, Sebastiaan Couwenberg wrote:
> The attached script can be used to generate a dd-list from the URL to
> the transition tracker.
>
> Kind Regards,
>
>
Hi Bas, I have to admit I was surprised to see a reply to my
-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
-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,
- --
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
-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
>
-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
-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
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
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
-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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Tue, 2023-09-26 at 12:54 +0200, Helmut Grohne wrote:
> We want to change the value of systemdsystemunitdir in systemd.pc to
> point below /usr. strongswan's upstream build system consumes this
> variable while the packaging hard codes its current
-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
-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
-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
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 l
On Mon, Jul 24, 2023 at 02:37:50PM +0100, Simon McVittie wrote:
> On Mon, 24 Jul 2023 at 14:57:23 +0200, Yves-Alexis Perez wrote:
> > If libopenraw Debian package isn't maintained in practice, maybe it
> > makes sense to drop it completely. For tumbler we can just remove the
e it on your box it's quite ok to remove it.
Regards,
--
Yves-Alexis Perez
On Mon, Jul 24, 2023 at 12:02:15AM +0100, Simon McVittie wrote:
> Source: libopenraw
> Version: 0.1.2-0.2
> Severity: wishlist
> X-Debbugs-Cc: tumb...@packages.debian.org
> Control: affects -1 + tumbler-plugins-extra
>
> While investigating whether libopenraw's dependency on GTK 2 can be
>
in 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
o 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
-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
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
f 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
uff 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
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
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 l
-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)
-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
-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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Mon, 2023-06-26 at 19:00 -0300, Andreas Hasenack wrote:
> on a recent build of strongswan, lintian is reporting that many source
> files are not covered by the current d/copyright contents. I'm going
> to paste it below:
Hi Andres, indeed it
;
> 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
-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
-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
-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
-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"
-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
-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 ->
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Tue, 2023-04-18 at 07:58 +0200, Helmut Grohne wrote:
> libplist fails to cross build from source for arm32, because it gets the
> python library directory wrong and uses the build architecture one. It
> extracts it from sysconfigdata, so we need
log
@@ -1,3 +1,18 @@
+strongswan (5.9.8-5) unstable; urgency=medium
+
+ * No-change upload for source-only upload.
+
+ -- Yves-Alexis Perez Fri, 03 Mar 2023 18:56:58 +0100
+
+strongswan (5.9.8-4) unstable; urgency=medium
+
+ * d/patches: libtls-Fix-authentication-bypass-and-expired-pointer ad
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: strongs...@packages.debian.org
Control: affects -1 + src:strongswan
Hi release team,
I've updated the strongSwan package in sid few days ago to fix a
security issue (only
-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
-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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Tue, 2023-02-28 at 16:44 +1100, James Lownie wrote:
> I then modified /etc/apparmor.d/usr.lib.ipsec.charon as follows, after which
> IPSec was able to load the secrets file and authenticate incoming
> connections:
Hi James, thanks for the
-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
-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
-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
-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
-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
-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
-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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sun, 13 Nov 2022 16:09:26 +0100 Jan Mojzis wrote:
> Hello,
> in the postinst script, the "ss" command from the iproute2 package is used,
> which checks whether TCP port 80 is free or not.
> If not, nginx will not start during installation.
>
>
-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
-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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Wed, 2022-11-02 at 19:14 +0100, Paul Gevers wrote:
> https://sources.debian.org/src/strongswan/5.9.8-1/debian/tests/control/
>
> line 2 says that the *first* two tests Depends on strongswan-scepclient.
> That means that autopkgtests tries to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Wed, 2022-11-02 at 19:14 +0100, Paul Gevers wrote:
> Hi Yves-Alexis,
>
> On 02-11-2022 17:27, Yves-Alexis Perez wrote:
> > I'm not sure why the test is failing then and what I should have done
> > differently. Could you
Package: nginx-light
Version: 1.18.0-6.1+deb11u2
Severity: normal
Hi,
I finally updated a nginx buster LXC to bullseye (this report is done on
my laptop so don't pay attention to the System information below). By
doing so I had to install iproute2 on that container because nginx-light
depends on
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Wed, 2022-11-02 at 17:08 +0100, Helmut Grohne wrote:
> On Wed, Nov 02, 2022 at 02:24:44PM +0100, Yves-Alexis Perez wrote:
> > Hi Helmut, thanks for the bug and the patch. Besides the add of :native
> > (and
> > :any) in vario
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Mon, 2022-10-31 at 21:01 +0100, Paul Gevers wrote:
> With a recent upload of strongswan the autopkgtest of strongswan fails
> in testing when that autopkgtest is run with the binary packages of
> strongswan from unstable. It passes when run
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Fri, 2022-10-28 at 17:02 +0200, Helmut Grohne wrote:
> libimobiledevice cannot be cross built from source, because its
> python-related build dependencies are not installable. It requests the
> python stack for the host architecture, but it wants
-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
-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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Tue, 2022-06-21 at 17:48 +0200, Yves-Alexis Perez wrote:
> The test were done on a LENOVO Thinkpad X280 laptop with latest
> firmware. If you need more information, please ask!
Hi, is this issue still on someone's radar?
Regards,
- --
-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
-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
>
-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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Thu, 2022-09-22 at 11:44 +0200, Tobias Brunner wrote:
> That's because the settings app uses GTK 4, while `nm-connection-editor`
> still uses GTK 3. In order for the strongSwan plugin to work with GTK
> 4, it has to be built with
-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
>
-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
Source: shim
Version: 15.4-7
Severity: normal
Hi,
I was trying to follow
https://wiki.debian.org/SecureBoot#MOK_-_Machine_Owner_Key to be able
to sign my locally built kernels (especially for debugging purposes).
As I already have a signing setup using my OpenPGP smartcartd, and I
prefer not
-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
-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
> >
-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
-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
Package: gvfs-backends
Version: 1.50.0-1
Severity: important
Hi,
I'm currently experiencing a segfault in gvfs-dav when mounting a share
(using gio mount davs:///remote.php/dav/corsac on a Nextcloud
instance).
I only started experiencing the issue now but it's been a while since I
tried to
-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,
-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
-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
-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).
-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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Wed, 2022-03-30 at 08:00 +0200, Johnny A. Solbu wrote:
> Are you telling me that unless I shell out some money,
> _Debian_ is not going to even provide any hints on what needs to be done to
> fix what is supposed to be a simple «apt upgrade»?
Hi
-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:
1 - 100 of 5906 matches
Mail list logo
