-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Thu, 2019-08-15 at 17:04 +0200, Yves-Alexis Perez wrote:
> On Sat, 2019-06-15 at 09:21 +0100, Amy Wrigley wrote:
> > While I am not the user who originally reported this, I can confirm
> > that this bug is still present in the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
control: reassign -1 thunar-archive-plugin
On Fri, 2019-08-23 at 18:01 -0400, Evan Rysdam wrote:
> When I have a folder named X and a .zip file containing a folder named
> X, if I right-click the .zip file and choose "Extract Here", the
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Control: severity -1 important
On Mon, 25 Jun 2018 16:16:49 +0200 Andreas Beckmann wrote:
> Source: xfce4-session
> Version: 4.13.0-1
> Severity: serious
> Justification: fails to build from source (but built successfully in the
past)
>
> Hi,
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Wed, 2019-08-21 at 09:55 +, Niels Thykier wrote:
> Could you check if
> https://release.debian.org/transitions/html/xfce4-panel.html matches
> your expectation for the packages affected by this transition?
I'm a bit surprised we have so few
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Wed, 2019-08-21 at 08:33 +, Niels Thykier wrote:
> Ack, please go ahead.
Thanks, I've started uploading stuff.
> Please let us know what will need binNMUs and when.
Sure, I'll let stuff settle a bit after uploading everything and I'll let
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Wed, 2019-08-21 at 15:43 +0200, Ronny Standtke wrote:
> > I have no idea why SESSION_MANAGER is already set when you start Xfce
> > the second time, but it looks like a bug in either gdm or gnome.
>
> As I said, the variable SESSION_MANAGER will
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Tue, 2019-08-20 at 20:39 +0200, Ronny Standtke wrote:
> When you log into GNOME (or Cinnamon or MATE) the environment variable
> SESSION_MANAGER will be set. If you then log out and try logging into
> Xfce it will fail. You will simply be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Mon, 2019-08-19 at 15:16 +0200, Pavel Reznicek wrote:
> > I'm not sure I understand the use case here, can you be a little bit more
> > specific?
>
> Sure, sorry for not writing that clearly from the beginning. The use
> case is when one often
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Wed, 2019-07-31 at 23:30 -0300, Alex Henry wrote:
> Hello, since a recent update Xfce is unable to open any items clicked on in
> the desktop or
> through the panel launchers (anything that checks tfor "preferred
> application", I imagine).
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Mon, 2019-08-05 at 16:43 +0200, Pavel Reznicek wrote:
> The panel "Output" settings does not allow easily to configure option where
> it would be placed on any connected external monitor (regardless of name of
> the monitor), while not shown on
On Sat, 2019-08-17 at 07:53 +0200, Helmut Grohne wrote:
> xfce4-power-manager fails to build from source for every architecture on
> the buildds. A typical failure is:
Hi Helmut, thanks for the report. It seems that xfpm requires libxfe4ui 4.13
although that's not in configure.ac.
Xfce 4.14
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
the Xfce team would like to upload the Xfce 4.14 release to unstable
(most packages pre-release have been uploaded to experimental).
Panel plugins might have a tight dependency to the
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
Hi,
the Xfce team would like to upload the Xfce 4.14 release to unstable
(most packages pre-release have been uploaded to experimental). One
library package, xfconf, has a transition
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sat, 2019-06-15 at 09:21 +0100, Amy Wrigley wrote:
> While I am not the user who originally reported this, I can confirm
> that this bug is still present in the current testing/unstable version
> of mousepad. I don't know what more I can say
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Wed, 2019-07-31 at 00:12 +0600, Vladimir Bezhenar wrote:
> By default file /etc/swanctl/swanctl.conf is world-readable
> (permissions 644). This file can contain passwords for EAP
> authentications, therefore it must not be world-readable, as
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Fri, 2019-08-09 at 12:12 +0200, Harald Dunkel wrote:
> Upstream provides a new strongswan version 5.8.0, including
> IPv6 support for charon-nm. See
>
> https://wiki.strongswan.org/issues/1143
>
> Would it be possible to include this
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sun, 2019-08-11 at 09:28 +0800, Jun Jiang wrote:
> I hope this is helpful.
Hi,
could it be that the crashes started occurring after a glib update?
Regards,
- --
Yves-Alexis
-BEGIN PGP SIGNATURE-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Tue, 2019-07-16 at 21:01 +0200, Simon Frei wrote:
> On 16/07/2019 20:28, Yves-Alexis Perez wrote:
> > xfce4-settings depends on libgarcon-1-0 because it's not yet ported to >
> > libgarcon-2: > >
> https://git.xfce.o
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
control: severity -1 wishlist
On Tue, 2019-07-16 at 11:17 +0200, Simon Frei wrote:
> I noticed that both libxfce4ui-1-0 and -2-0 are installed on my system and
> checking showed it's due to xfce4-settings depending on libgarcon-1-0. I
> assume it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
control: retitle -1 xfce4-notifyd fails to start with DBus activation (Unable
to init server)
On Sat, 2019-07-13 at 13:31 -0700, Bob Hauck wrote:
> Jul 13 13:29:28 robin xfce4-notifyd[2624]: Unable to init server: Could not
> connect: Connection
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
control: reopen -1
On Sun, 2019-07-14 at 00:44 +0200, Adam Borowski wrote:
> But, in this case, I am very excited that you have a replacement for
> something I find to be hopelessly buggy -- and the replacement seems
> near-perfect. Thus, if you
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
is there any update on this issue? I'm bitten by this one because my system is
mostly always in “degraded” state according to systemd. Consequence (as
outlined in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916122#18) is
that cgroup
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Thu, 2019-07-11 at 10:34 +0200, Adam Borowski wrote:
> So... is there any reason to not let xfce4-screensaver go to Bullseye?
> Any day that a human being suffers from light-locker is a bad day.
Hi Adam,
could you please refrain from such
On Thu, 2019-07-11 at 10:11 +0200, Adam Borowski wrote:
> Hi!
> You've just changed Depends from
> logind | consolekit
> to
> libpam-systemd | logind
>
> I assume that you missed the new Policy -- discussed and approved before
> Buster, released as a package a few days ago.
Yes. To be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Wed, 2018-05-23 at 15:49 +0200, Pavel Kreuzt wrote:
> Since last upgrade xfce4-notifyd dowsn't start anymore with XFCE session,
> nor it does when some program presses some notification. This also causes
> some odd behaviour with some other apps
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
control: forwarded -1 https://bugzilla.xfce.org/show_bug.cgi?id=15698
On Thu, 2019-06-27 at 10:45 +0200, Miguel A. Marcos wrote:
> Package: parole
> Version: 1.0.1-1
> Severity: normal
>
> Dear Maintainer,
>
> How to reproduce this bug:
>
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Wed, 2019-07-03 at 20:59 +0200, Laurent Bonnaud wrote:
> this manpage:
>
>/usr/share/man/man2/xfce4-popup-places.22.gz
>
> is in section 22, which is most certainly a mistake.
Indeed, thanks for the report. I've updated the manpage,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
control: forcemerge 805711 -1
On Mon, 2019-07-08 at 00:14 +0900, Kubo Hiroshi wrote:
> On Debian 10 Xfce desktop, when the Xserver switch its DPMS state to
> standby, susped, or off, the light-locker steals the control
> on the screen on vt7. But
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Mon, 2019-07-01 at 14:13 -0500, Michael Umland wrote:
> I do not think this particular bug is dependent on any one driver (Intel or
> otherwise) as previous posters have suggested. I have also experienced this
> bug on a fresh installation using
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Fri, 2019-06-28 at 17:06 +, nodiscc wrote:
> Original, working, no xorg.conf, glx alternative = /usr/lib/mesa-diverted:
>
> (II) LoadModule: "nouveau"
> (II) Loading /usr/lib/xorg/modules/drivers/nouveau_drv.so
>
> glx alternative =
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Control: forcemerge -1 868087
On Thu, 2019-06-27 at 12:02 -0400, Onyuksel, Cem wrote:
> I'd like to point out that this bug has a similar effect on nvidia graphics
> as well, as pointed out in the bug report
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
control: affects -1 xserver-xorg-core
On Sat, 2019-06-22 at 17:34 -0400, John Franklin wrote:
> I've been suffering from this bug in a clean Buster system, too. A
> solution noted in another bug tracker is to explicitly tell X.org to
> use the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Tue, 2019-06-18 at 21:20 +0200, Mattia Rizzolo wrote:
> That would indeed be a fine workaround for me, and reduce the load the
> security team is experience, since it's the team which is the most
> affect by this.
> (Incidentally, it also is the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sun, 2019-06-16 at 15:50 +0200, Ivo De Decker wrote:
> > We regularly get biten by this issue when contributors to security
> > uploads, most recently with the bind9 upload but as well others.
>
> Is it clear in what cases this issue happens?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Mon, 2019-06-03 at 12:59 -0700, Russ Allbery wrote:
> Ah, good call. I was also seeing other problems with the Intel driver in
> combination with light-locker where the monitor resolution would be set to
> some incorrect value after restore from
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Mon, 2019-06-03 at 21:55 +0200, Yves-Alexis Perez wrote:
> I noted Andreas raised the severity, but I hope someone has an idea how to fix
> that because I don't.
Also, since it was posted on -devel, I guess there's a bit of exposure: i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Fri, 2019-05-31 at 18:32 -0700, Russ Allbery wrote:
> This appears to be a bug in light-locker specifically, which is the
> default screen lock program with XFCE with lightdm. See, for instance:
>
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Fri, 2019-05-31 at 10:35 -0400, James Henried wrote:
> Please let me know if this is useful/ok or if I need to do anything
> else.
It looks OpenSSL related, but besides that I don't have much clue yet. It
might help to install dbgsym packages
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Thu, 2019-05-30 at 12:36 -0400, James Henried wrote:
> Reopening #919630.
>
> Have been running into trouble mounting an iPhone with ifuse. Noticed that
> usbmuxd segfaults on startup:
Hi, can you also provide the information asked in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
control: forcemerge 846278 -1
On Thu, 2019-05-23 at 16:17 -0700, Matt Weatherford wrote:
> When screen locks on Dell Optiplex 9020 w/latest BIOS, i cannot wake it with
> keypresses or mouse movements
> have to ctrl-alt-f1 to console, then monitor
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Thu, 8 Sep 2016 20:28:36 +0200 Julian Andres Klode wrote:
> Source: edk2
> Severity: wishlist
>
> Having an EFI shell on a real host is quite useful, it would be nice
> to have one packaged so bootloader(s/configuration tools) can install
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
control: forwarded -1 https://bugzilla.xfce.org/show_bug.cgi?id=15356
On Fri, 2019-05-03 at 19:43 +0200, pn...@telenet.be wrote:
> Hi Yves-Alexis,
> Thank you for your quick response.
> I've reported the issue at bugzilla.xfce.org (Bug #15356).
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Fri, 2019-05-03 at 18:06 +0200, pn...@telenet.be wrote:
> After creating some panel launcher buttons to maximize (toggle), minimize
> and
> close the active window (reason: handle maximized windows when the titlebar
> is
> not shown), maximizing
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Tue, 2019-04-16 at 09:15 -0400, robert.grizz...@quoininc.com wrote:
> >Configure the plugin's settings directly in
> > strongswan.conf in the charon-nm.plugins.pkcs11 section (or set them in
> > the libstrongswan section so they apply to both
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Thu, 2019-04-11 at 13:49 +0200, Christophe Devine wrote:
> The eap-sim and eap-sim-file plugins are missing from
> libcharon-extra-plugins. They are
> required to authenticate a client using 2G authentication vector obtained
> using for example
Package: src:wpa
Severity: grave
Tags: security
Justification: user security hole
Hi,
multiple vulnerabilities were discovered in wpa:
CVE-2019-9494 [cache attack against SAE]
CVE-2019-9495 [cache attack against EAP-pwd]
CVE-2019-9496 [SAE confirm missing state validation in hostapd/AP]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Tue, 2019-04-09 at 19:56 +0200, Paul Gevers wrote:
> Ack (for the restrictions, not the depends).
I'm a bit lost here so I refer to both of you. Can you provide a patch against
current git debian/master (which should be the same as unstable).
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sun, 2019-04-07 at 14:22 +0200, Christian Ehrhardt wrote:
> I have no Debian VM that supports autopkgtest, maybe you could upload
> that to experimental or the QA team could otherwise help to verify the
> suggestion.
> Or - if you want - you can
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sat, 2019-04-06 at 14:45 +0200, Yves-Alexis Perez wrote:
> On Fri, 2019-04-05 at 22:23 +0200, Paul Gevers wrote:
> > Your package has an autopkgtest, great.
>
> Hi,
>
> I have *no* idea where this autopkgtest comes from,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Fri, 2019-04-05 at 22:23 +0200, Paul Gevers wrote:
> Your package has an autopkgtest, great.
Hi,
I have *no* idea where this autopkgtest comes from, to be honest. There's no
reference to it in the packaging and I'm pretty sure I never did
Package: mokutil
Version: 0.2.0-1+b3
Severity: wishlist
Hi,
would it be possible at one point to update mokutil to latest version?
Our version doesn't support --set-verbosity option for shim (it can be
done manually but it'd be convenient to have it directly).
Regards,
--
Yves-Alexis
--
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
control: tag -1 pending
On Thu, 2019-03-14 at 12:38 +0100, Yves-Alexis Perez wrote:
> Hi everyone, we're aware of the situation and will try to fix it as soon as
> possible. It should be harmless when not running with Secure-Boot e
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Control: forcemerge 924545 924549 924553
On Thu, 2019-03-14 at 11:03 +0100, Vincent Lefevre wrote:
> Package: src:linux
> Version: 4.19.28-1
> Severity: important
>
> With this new kernel, I get the following error 487 times!
>
> PKCS#7
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Wed, 2019-03-06 at 19:04 +0100, Michael Biebl wrote:
> This is usually not a good idea, as apt will pick a package at random if
> none is installed yet. You should always list a real package or
> default-logind first.
I've already changed that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sat, 2019-03-02 at 08:15 +0100, Ansgar wrote:
> I think this problem (having $HOME world-readable by default) should
> really be fixed... In installations sharing $HOME between multiple
> users this means private data of all sorts (medical
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Thu, 2019-02-28 at 21:34 +0300, Andreas B. Mundt wrote:
> I already draft-implemented this, seems to be pretty simple (and
> indeed usefull):
>
>
>
Package: di-netboot-assistant
Version: 0.59
Severity: wishlist
Hi,
I'd like to setup some netboot images for serving over PXE, storing
stuff in /var/lib/tftp is not practical for me. I'd like to be able to
specify the target directory from the command line, but it's apparently
not possible for
protocol
+ * d/gbp.conf adjusted for buster branch
+ * d/control: drop Emanuele, Simon, Lionel and Stefan from uploaders
+ * d/control: update standards version to 4.2.1
+
+ -- Yves-Alexis Perez Thu, 07 Feb 2019 17:29:33 +0100
+
+gigolo (0.4.2-2) unstable; urgency=medium
+
+ * debian/patches
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Mon, 2019-02-25 at 13:13 +0100, Yves-Alexis Perez wrote:
> On Sat, 2019-02-23 at 16:44 +, Mark Hindley wrote:
> > On Sat, Feb 23, 2019 at 02:13:22PM +0100, Yves-Alexis Perez wrote:
> > > For the pam configuration, yes I didn
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sat, 2019-02-23 at 16:44 +, Mark Hindley wrote:
> On Sat, Feb 23, 2019 at 02:13:22PM +0100, Yves-Alexis Perez wrote:
> > For the pam configuration, yes I didn't change anything because I honestly
> > don't know enough a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Mon, 2019-02-25 at 11:53 +, Mark Hindley wrote:
> Yes, or even use the new default-logind virtual package (currently provided by
> libpam-systemd) as well:
>
> default-logind [linux-any] | logind [linux-any]
That won't fix the issue that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Fri, 2019-02-22 at 18:34 +0100, Ansgar wrote:
> On Fri, 2019-02-22 at 13:59 +, Mark Hindley wrote:
> > A further suggestion, now systemd 241-1 has been uploaded to unstable
> > with
> > libpam-systemd which provides logind (closing #915407),
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Thu, 2019-02-21 at 14:02 +0100, Dominik George wrote:
> That also does not replace light-locker. It only enables locking in default
> installations in the above scenarios.
We're running in circle. I already said no (not now, at least).
Regards,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Thu, 2019-02-21 at 14:32 +0100, Adam Borowski wrote:
> > Honestly I'd be just fine in just disabling all the screensavers and only
> > keep
> > blank screen.
>
> Do you mean dropping them all by default, or just after the powersave kicks
> in?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Thu, 2019-02-21 at 13:43 +0100, Dominik George wrote:
> > I'm not sure at all I want to actually replace lightdm/light-locker by
> > xfce4-
> > screensaver.
>
> Noone requested that.
>
> The attached patch uses xfce4-screensaver only if lightdm
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
[adding Jonathan to CC just in case]
On Sat, 2019-02-09 at 11:53 +0100, Adam Borowski wrote:
> Package: xfce4-screensaver
> Version: 0.1.3-2
> Severity: normal
>
> I left home for the weekend, just ssh-ed in and I see:
> PID USER PR NI
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Thu, 2019-02-14 at 18:51 +, Paul "LeoNerd" Evans wrote:
> Any update on this? It's been 2.5 years now.
No, sorry
>
> Anything I can do to assist debugging and eventually fixing it?
Honestly, it'd be best to directly report this upstream.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Tue, 2019-02-19 at 21:54 +0100, Dominik George wrote:
> Control: retitle -1 screen locking does not work without lightdm
> Control: severity -1 important
>
> > In xflock4, please support xfce4-screensaver, which is a mate-screensaver
> > fork
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Fri, 2019-02-15 at 18:37 +, Thorsten Glaser wrote:
> Perhaps, if it’s best to consider these LD_PRELOADable libraries
> that could benefit from the glibc suid bit case-by-case, this can
> be “preapproved”?
My own opinion on this is that no
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Fri, 2019-02-15 at 13:17 +, Thorsten Glaser wrote:
> > I think one reason I never really consider this chage is because my
> > security foo are not great enough to understand to throughly understand
> > all the possible implications such
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Tue, 2019-02-12 at 08:06 -0500, Dan Robinson wrote:
> I was able to actually log in so I didn't realize that was an exact
> duplicate.
Yes sorry, this is a bit of a mess (which doesn't help user reporting bugs
either). If you look at the end of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Tue, 2019-02-12 at 20:05 +, Mark Hindley wrote:
> As /etc/pam.d/lightdm-greeter doesn't source common-session (should it?), the
> extra line is required.
To be honest, I'm definitely not a PAM expert, so maybe it would be better to
do it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
control: forcemerge 846278 -1
On Mon, 2019-02-11 at 18:28 -0500, Dan Robinson wrote:
> Off a fresh install with no changes to the system, light-locker doesn't
> respond after locking the screen without manually switching VTs. Mouse or
> key
> input
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Wed, 2014-08-06 at 21:21 +0200, Moritz Molle wrote:
> As to when the plugin crashes in the panel: I add it to the panel and
> the icon (the menubutton) gets displayed. When I click it, the frame
> opens in which the menu should be displayed,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Fri, 2019-02-08 at 10:10 +1100, Dmitry Smirnov wrote:
> Thanks. Maximiliano diagnosed the problem in #907297:
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907297#35
>
> It is happening because of ".gtkrc-2.0" file as per
>
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Thu, 2019-01-31 at 12:49 +0100, Yves-Alexis Perez wrote:
> On Thu, 2019-01-31 at 11:20 +0100, Tomas Pospisek wrote:
> > Do you have a reference for a bug report in the bts for this? Or asked
> > slightly differently: are th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
control: severity -1 important
control: tag -1 unreproducible
On Wed, 2019-01-30 at 15:37 +1100, Dmitry Smirnov wrote:
> In Cinnamon xfce4-notes does not work any more: it starts without showing
> its
> window or tray icon and uses ~55% CPU
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Thu, 2019-01-31 at 11:20 +0100, Tomas Pospisek wrote:
> Do you have a reference for a bug report in the bts for this? Or asked
> slightly differently: are the X maintainers and/or upstream aware of this
> problem and are tracking it (again I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Tue, 2019-01-29 at 23:24 +0100, franz.da...@web.de wrote:
> I am using Debian GNU/Linux 9.7 with Kernel 4.9.0-8-amd64 #1 SMP Debian
> 4.9.130-2 (2018-10-27) x86_64 GNU/Linux and XFCE 4.12.3 desktop environment
> and lightdm 1.18.3-1 ,
Package: dump1090-mutability
Version: 1.15~20180310.4a16df3+dfsg-6
Severity: normal
Hi,
I just tried the Debian package for dump1090-mutability, and it seems
that the HTTP interface doesn't work.
When running with --net and looking at netstat output, I get:
Active Internet connections (servers
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Tue, 2019-01-29 at 09:30 +0100, Tomas Pospisek wrote:
> * I had very spurious problems with the lock screen (say once in three
> months) under Debian stretch
> * however under 'buster' the problem is 100% repeatable
> * I have tried with both
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Mon, 2019-01-28 at 14:07 +0100, Olivier Berger wrote:
> > I have local patches which enable a bit more debug and maybe fix that issue.
> > Out of curiosity, do you mount /proc with hidepid option?
> >
>
> Nope, AFAIU :
> $ mount | grep ^proc
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Mon, 2019-01-28 at 09:15 +0100, Olivier Berger wrote:
> Oh, and btw, this happened when I started light-locker --debug from the
> command-line, but actually, that seems to happen also when started
> from the command-line without --debug too...
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Fri, 2019-01-25 at 15:40 -0700, Jason Crain wrote:
> This issue was discussed a while ago in a Debian bug:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860796#56. smcv's
> comment in that bug includes some suggestions. To fix the file
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Tue, 2019-01-15 at 10:26 +0100, Yves-Alexis Perez wrote:
> I think it would make more sense to migrate the modules_disabled part to
> hardening-runtime and I would happily welcome co-maintainership on this if
> you're interested. Obvious
Source: nautilus
Version: 3.30.5-1
Severity: normal
Hi,
this is a “preemptive” bug about a future file conflict. Latest Thunar
upstream version (1.8.3) gained support for the
org.freedesktop.FileManager1 DBus name
(https://bugzilla.xfce.org/show_bug.cgi?id=12414).
This is a generic Freedesktop
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
control: tag -1 moreinfo unreproducible
On Thu, 2019-01-17 at 18:44 -0500, James Henried wrote:
> Have been running into trouble mounting an iPhone with ifuse. Noticed that
> usbmuxd segfaults on startup:
Hi, thanks for the report. When does this
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
[adding the ITP bug on CC]
On Mon, 2019-01-14 at 10:24 -0800, Matt Taggart wrote:
> Hi,
>
> I just found out about your hardening-runtime package, it's great!
>
> A while back I created a package with similar intent named lockdown.
>
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Mon, 2019-01-14 at 10:51 +0100, Nicolas Boulenguez wrote:
> There is probably a reason why these options are not activated by
> default on each installation by the appropriate package.
> I think that the long description should mention this
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sun, 2019-01-13 at 22:48 +, Colin Watson wrote:
> Hmm. I mean, it's possible that it wouldn't hurt, and I'm not sure
> whether I have a strong opinion on it, but for the record could you
> explain the positive benefits of reusing it?
It's a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Just a side note on this. The package currently supports sysctl (by dropping a
file in /etc/sysctl.d, which should be common enough) and Linux commandline
when using grub (by dropping a file in /etc/default/grub.d).
I was asked to open a discussion
Package: wnpp
Severity: wishlist
Owner: Yves-Alexis Perez
* Package name: hardening-runtime
Version : 1
Upstream Author : Yves-Alexis Perez https://salsa.debian.org/corsac/hardening-runtime
* License : GPL-2+
Programming Lang: configuration file
Description
Package: base-passwd
Version: 3.5.45
Severity: normal
Hi,
the range 64040-64044 is assigned to various grsec-related groups. The
groups are created by the linux-grsec-base package postinst, which was
used when src:linux-grsec was a thing. Unfortunately, there is no more
package since grsecurity
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
[Last time, please keep the bug address on CC, I am not a private support
channel]
On Wed, 2019-01-09 at 09:47 -0800, vassil wrote:
> Please go to menu "View" and try indicated shortcuts for "Zoom In", "Zoom
> Out", "Normal Size". Check for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Wed, 2019-01-09 at 01:17 -0800, vassil wrote:
> Expected: "Ctrl++" to "Zoom In"
> Observed: "Ctrl++" outputs "=" and does not "Zoom In"
> Fix: "View->Zoom In" shortcut should be labeled "Shift+Ctrl++"
[please keep the bug on CC]
I'm unsure how
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Fri, 12 Jan 2018 11:15:11 -0500 Cindy Sue Causey
wrote:
> Package: xfce4-clipman
> Version: 2:1.4.1-1
> Severity: important
>
> Dear Maintainer,
>
> Dear Maintainer,
>
> First and as always, #ThankYOU for the work you do!!
>
> Now for the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Mon, 2019-01-07 at 14:04 +, vassil wrote:
> Dear Maintainer,
>
> Thanks for your work on xfce4-terminal!
Thanks but when reporting a bug, could you please state what exactly you think
is a bug and how it should behave?
Regards,
- --
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sat, 2019-01-05 at 19:58 +0100, Andreas Henriksson wrote:
> Please also note the previous/above comment about G_SPAWN_SEARCH_PATH
> flag, which I think you will need as well (or AIUI g_spawn_sync will
> *not* search in PATH).
>
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Tue, 2019-01-08 at 12:14 +0200, Panagiotis Malakoudis wrote:
> I use ikev2 with certificates from let's encrypt, so they need to be
> verified from a root ca.
I understand the need, but be aware that that could easily mean that every
Let's
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Tue, 2019-01-08 at 11:17 +0200, Panagiotis Malakoudis wrote:
> Ιαν 08 10:28:32 ryzenpc charon-nm[6196]: 05[LIB] building CRED_CERTIFICATE -
> X509 failed, tried 6 builders
> Ιαν 08 10:28:32 ryzenpc charon-nm[6196]: 05[CFG] loading CA certificate
301 - 400 of 5906 matches
Mail list logo
