-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Wed, 2020-05-06 at 10:43 -0400, Aaron M. Ucko wrote:
> Package: hardening-runtime
> Version: 2
> Severity: normal
>
> systemd services specifying PrivateUsers=yes (upower for a while, now
> also uuidd from uuid-runtime) have been failing with
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Wed, 2020-04-29 at 10:41 +0100, Simon McVittie wrote:
> Source: tumbler
> Version: 0.2.8-1
> Severity: normal
> User: pkg-gnome-maintain...@lists.alioth.debian.org
> Usertags: oldlibs gtk2
> Control: block 947713 by -1
>
> While preparing a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Fri, 2020-03-20 at 09:06 +0100, Yves-Alexis Perez wrote:
> On Thu, 2020-03-19 at 18:39 +0100, Andreas Henriksson wrote:
> > There doesn't seem to have been any movement since your comment on the
> > upstream bug report. The xfc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Thu, 2020-03-19 at 18:39 +0100, Andreas Henriksson wrote:
> There doesn't seem to have been any movement since your comment on the
> upstream bug report. The xfce4-notes-plugin is now the only remaining
> package in unstable that still depends on
Package: firefox
Version: 74.0-1
Severity: normal
Hey,
I'm a intensive user of containers in Firefox. I have like 15-20
containers using the Multi-Account-Containers extension, plus temporary
containers using the Temporary Containers extension.
With the Firefox 74 update has apparently appeared
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Mon, 2020-03-02 at 11:49 -0700, Sean Whitton wrote:
> > Hi Jonas, I got that issue earlier, and to be honest I kind of side with
> > Fabrice here, and I find it bit sad Buster was released with that kind of
> > behavior.
>
> It's definitely
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
control: severity -1 grave
On Thu, 12 Sep 2019 12:47:57 +0200 Jonas Smedegaard wrote:
>
> Sorry, which _Debian_ issues are left here which I missed?
>
> If you tried b) and it failed, then please provide more details what
> exactly you did and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Thu, 2020-02-13 at 13:11 +0100, Andreas Henriksson wrote:
> Control: severity -1 serious
>
> Hello XFCE Maintainers,
>
> I'm bumping the severity of this bug report because the libindicators
> package in RC buggy and likely not going to make it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sun, 2020-02-09 at 21:02 +0100, Helmut Grohne wrote:
> strongswan fails to build from source in unstable, because it misses a
> build dependency on libiptc-dev. The library was formerly pulled by
> "something" and no longer is. The build now
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Mon, 2020-02-10 at 11:21 +0100, B wrote:
> I'm sorry for the noise and your wasted time, but thanks for your help ;
> may be a warning about not re-using old xfce4 configuration files when
> upgrading would be of some help for others.
Well,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sun, 2020-02-09 at 19:01 +, B wrote:
> > Ok. Can you run it throught gdb and when it crashes, run bt full and
> > copy the output?
>
> I don't know how to do that, could you explain it?
Try to follow those instructions:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sun, 2020-02-09 at 16:57 +, B wrote:
> > I tried on my own Buster installation but I can't reproduce your
> > problem. I installed Orage and it worked just fine here (either the
> > plugin or running from command line).
>
> Ra ! :/
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
control: tag -1 moreinfo unreproducible
On Sun, 2020-02-09 at 12:12 +, Jiff wrote:
> Package: orage
> Version: 4.12.1-6
> Severity: important
>
> Hi Dear Maintainer,
>
>* What led up to the situation?
>
> Yesterday buster large update to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Wed, 2020-02-05 at 19:32 +0100, Till Kamppeter wrote:
> Probably the best is to try to print without using PostScript. When
> creating a print queue and selecting your printer's make, model, and
> driver manually, have a look at PCL 6/XL
On Wed, 2020-02-05 at 17:19 +, Brian Potkin wrote:
> > Not really sure, but I don't think so. I mean, I'm using the PPD file
> > from cups Debian packages, not anything from Brother.
>
> As root, what do you get for
>
> grep "*NickName" /etc/cups/ppd/
*NickName: "Brother HL-5250DN
On Wed, Feb 05, 2020 at 03:29:22PM +, Brian Potkin wrote:
> Your issue seems connected with
>
> https://github.com/OpenPrinting/cups-filters/issues/169
>
> and its associated bugs.
When looking at the warning message in the logs I stumbled on that bug,
but didn't really find it really
Package: cups-filters
Version: 1.27.0-2
Severity: important
Hi,
since “some” time (few weeks maybe, I guess the 1.27.0 upload), I can't
print on my Brother HL-5250DN network printer (which was working just
fine earlier).
The printer is laser monochrome, and I always was able to print color
and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sun, 2020-02-02 at 21:08 +0100, Yves-Alexis Perez wrote:
> > An empty
> > override_dh_installsystemd:
> >
> > is probably better suited in this case.
> >
> > Not sure if this fixes the issue you are seeing
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sun, 2020-02-02 at 21:03 +0100, Michael Biebl wrote:
> I had a very superficial look at debian/rules
>
> override_dh_installsystemd:
>dh_installsystemd -plightdm --no-start -r lightdm.service
>
> I suppose you don't want that.
To be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sat, 2020-02-01 at 03:21 +0100, Michael Biebl wrote:
> They should also add a
>
> [Install]
> Alias=display-manager.service
>
> section
>
> to their service file. Which will make sure that if you run
> "systemctl enable foo.service",
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sat, 2020-02-01 at 11:54 -0800, Vagrant Cascadian wrote:
> Control: tags 950437 -patch
> Control: block 950437 by 950444
>
> On 2020-02-01, Vagrant Cascadian wrote:
> > When built with the C locale, some files differ from when built with a
> >
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Wed, 2020-01-29 at 14:58 +0100, Wilco Baan Hofman wrote:
> The optional dependency for consolekit has been silently dropped and replaced
> with another systemd package (consolekit replaced by libpam-systemd?). Please
> keep ConsoleKit as
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Mon, 2020-01-27 at 10:54 +0100, Vincent Lefevre wrote:
> It was the kernel from Debian/unstable at the time I reported the
> bug, and it still occurred with linux-image-5.4.0-3-amd64 5.4.13-1.
>
> > It's likely related to the *Xorg* driver,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Mon, 2020-01-20 at 12:03 +0100, Vincent Lefevre wrote:
> > In case this might depend on the driver, I was using the nvidia
> > driver (and I still use it on this machine).
>
> My laptop uses the nouveau driver. So this is not related to the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Fri, 2020-01-24 at 19:23 -0500, annadane wrote:
> In thunar (debian stable), right clicking a file and entering something in
> "use a custom command" does not open the file. I was trying to open image
> files with feh -B black but I suspect this
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Tue, 2020-01-07 at 19:21 +0100, Enrico Weigelt, metux IT consult wrote:
> Therefore introduce a new setting and only execute programs if explicitly
> enabled.
Hi, thanks for the patch. Can you submit it directly upstream so it can be
discussed
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sun, 2020-01-05 at 19:19 +0100, Alf wrote:
> So, my guess is that this nasty bug is actually caused not caused by
> light-locker, but instead by xorg-server which either looses the mouse
> or fails to (re)start with correct configuration. With
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
control: tag -1 pending
On Fri, 2020-01-03 at 13:08 +0200, Graham Inggs wrote:
> The package build-depends on python3-all-dev, but does not build
> extensions/libraries for all supported python3 versions. This
> is seen on the transition tracker
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Fri, 2019-12-27 at 17:13 +0100, Klaumi Klingsporn wrote:
> Dear maintainers,
>
> Would be nice, if you applied the ubuntu patch to the
> debian-package as well.
>
> I built a personal debian package with this patch
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
control: severity -1 important
On Tue, 2019-12-24 at 16:16 +0100, Jérôme Bouat wrote:
> It seems a directory is missing :
> ---
> Could not enumerate user data directory /var/lib/lightdm/data: Error opening
> directory '/var/lib/lightdm/data': No
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sun, 2019-12-22 at 17:11 +0100, Enrico Zini wrote:
> I can confirm that with the kernel currently in buster-backports[1], the
> display comes back on correctly.
Thanks, that's good news.
>
> However, after the screen lock activates for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sat, 2019-12-07 at 20:11 +, Adam D. Barratt wrote:
> > Sorry, I replied to the wrong bug. I'll upload the isolated fix soon,
> > likely this weekend, thanks.
>
> Just to keep this up-to-date, the libimobiledevice upload made it to
> sid, but
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sat, 2019-12-14 at 21:34 +0300, dinar qurbanov wrote:
> > Do you still have the issue? Which kernel are you running? Are you on
> > stable
> > or testing/unstable?
>
> (this letter got to spam, so i answer a bit later). yes, still have.
> stable
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Wed, 2019-12-11 at 12:38 +0300, dinar qurbanov wrote:
> possible solutions/wokarounds:
> 1) https://bbs.archlinux.org/viewtopic.php?pid=1671675#p1671675
> 2)
> https://github.com/the-cavalry/light-locker/issues/108#issuecomment-502404552
> (i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sat, 2019-11-30 at 00:19 +0100, Sebastien Bacher wrote:
> Package: libplist
> Version: 2.0.1~git20190104.3f96731-1
>
> The package build-depends on python3-all-dev, but does not build for all
> supported python3 versions, it should rather b-d on
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sat, 2019-11-30 at 02:49 -0800, Brian Clinkenbeard wrote:
> Any updates regarding the Ubuntu patch?
Hi, I'm not sure what you mean by “the Ubuntu patch”?
Regards,
- --
Yves-Alexis
-BEGIN PGP SIGNATURE-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sun, 2019-09-22 at 11:04 +0200, Yves-Alexis Perez wrote:
> Obviously there might be people using python-plist and python-imobiledevice
> directly in python scripts and they'll have to migrate them to python3,
> which
> is not perfect,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Thu, 21 Nov 2019 22:20:03 -0600 tubus wrote:
> Package: thunar
> Version: 1.8.4-1
> Severity: important
>
> Dear Maintainer,
>
> I have set environment variable FREETYPE_PROPERTIES in /etc/environment
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Fri, 2019-11-08 at 21:55 +0100, Yves-Alexis Perez wrote:
> On Fri, 2019-11-08 at 20:53 +, Adam D. Barratt wrote:
> > Sorry for the delay in getting back to you.
>
> Yeah, this time it's me who's really sorry.
> > That so
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Thu, 2019-10-24 at 11:44 +0200, Emilio Pozuelo Monfort wrote:
> Just go ahead with the package rename / soname bump, no need to revert it and
> then do the transition in this case, given the rdeps are going to build fine
> so
> there will be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Fri, 2019-11-22 at 17:18 +0100, Andreas Henriksson wrote:
> I'm tired. Your package already build-depends on yelp-tools so I'm
> going to just assume that the gnome-doc-utils build-dependency is
> a leftover from before switching to yelp/itstool.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sun, 2019-11-17 at 11:00 +, Mike Gabriel wrote:
> If you plan to drop maintenance sooner or later anyway, then please
> state that asap (packages are in deferred-15 from today again), so
> that I can change the uploads and make these bugs
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Wed, 2019-11-13 at 20:58 +, Mike Gabriel wrote:
> One last question: For the themes you maintain, is it ok if I provide
> the "Provides: any-murrine-theme" patches (as MRs or pushed commits)
> and possibly even NMU them for those
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Tue, 2019-11-12 at 12:09 +0100, Mike Gabriel wrote:
>
> As I haven't had any reply nor statement nor veto nor anything from any
> of you on the above, here is what is going to happen, if noone interacts...
Hi Mike,
I'm unfortunately quite
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Fri, 2019-11-08 at 20:53 +, Adam D. Barratt wrote:
> Sorry for the delay in getting back to you.
Yeah, this time it's me who's really sorry.
>
> That sounds OK, but it looks like the fix still hasn't made it to sid,
> so I'm tagging this as
On Sun, 2019-10-27 at 11:06 +0100, Alf wrote:
> Hi Yves-Alexis,
>
> I tested in Buster with kernel linux-image-5.3.0-1-amd64 from unstable
> and "modesetting" DDX: it appears to be fixed.
> Hardware is Intel Iyv-Bridge CPU with HD4000 GPU.
> The workarounds like using "intel" driver or "xset s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
upstream (kernel) bug report indicates that the problem might lies with the
way the modesetting DDX driver uses atomic. The 5.3.7 kernel (available in
linux-image-5.3.0-1-amd64 5.3.7-1) has a workaround for this:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Tue, 2019-10-22 at 17:12 +0200, Yves-Alexis Perez wrote:
> Unfortunately, I can't just revert the patch so that means basically reverting
> the whole stuff to the previous snapshot (I'm not too sure how well gbp handle
> that), dro
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sun, 2019-10-20 at 21:33 +0200, Paul Gevers wrote:
> Sorry for taking so long, but I have the feeling that the binNMU isn't
> appropriate. I take the silence from the other team members to mean
> something similar.
To be honest, I'm a bit
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Tue, 2019-10-22 at 03:14 -0500, Diego Escalante Urrelo wrote:
> Forgot to add that when logging in into my GNOME session, if my iPhone
> is connected, I experience a long freeze too. I thought it was mtp or
> gvfs-gphoto2, but it's probably
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Mon, 2019-10-14 at 18:35 -0500, Diego Escalante Urrelo wrote:
> Anyway, thanks for your work on this. Let me know if I can help with
> anything else.
I'm still waiting for the binNMU or the package from NEW to be accepted,
unfortunately.
On Thu, 2019-10-10 at 09:31 +0200, Simon Ruderich wrote:
> Thanks for verifying. I've pushed c4814aa ("Fix false positive in
> libtool detection with quoted path", 2019-10-06) [1] with the
> fix.
>
> I've also released blhc 0.10 with the recent fixes. [2]
Thanks for the work. I'll wait for it to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Wed, 2019-09-25 at 10:36 +0200, Andries van Bergen wrote:
> Dear Maintainer,
>
> When more than one window is open, closing one window (by button) makes a
> zombie process of Bash.
> Closing the last window (by button), or any window by typing
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sun, 2019-10-06 at 07:08 -0400, Jeremy Bicha wrote:
> Control: severity -1 serious
>
> The Debian GNOME team would like to remove libunique from Debian.
> Therefore, I'm bumping the severity of this bug to serious.
>
> Please see the master bug
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sun, 2019-10-06 at 11:47 +0200, Simon Ruderich wrote:
> Now I'm somewhat confused. I think the issue in this case is not
> "libtool: relink:" because I get no errors for those lines when
> running blhc on the buildd log.
>
> Instead, I think the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sun, 2019-10-06 at 10:59 +0200, Simon Ruderich wrote:
> sounds sensible. Can I get the relevant parts of the original
> build log? Your updated regex won't match the line you pasted
> ('libtool: ' vs. '/libtool" --tag CC --mode=relink') and I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sat, 2019-10-05 at 15:45 +0200, Yves-Alexis Perez wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: binnmu
>
> nmu libimobiledevice_1.2.1~git20181030.92c5462-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
control: reassign -1 libimobiledevice
control: affects -1 ifuse
control: forcemerge 941703 -1
control: forwarded -1 https://github.com/libimobiledevice/libusbmuxd/issues/81
On Sun, 2019-10-06 at 19:26 +1300, Bart Joy wrote:
> When running ifuse
Package: blhc
Version: 0.09-2
Severity: normal
Hi,
blhc running on salsaci for strongSwan reports failure
(https://salsa.debian.org/debian/strongswan/-/jobs/350397/raw) at the
blhc step because of lines like these:
8890:CPPFLAGS missing (-D_FORTIFY_SOURCE=2): /bin/bash
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu
nmu libimobiledevice_1.2.1~git20181030.92c5462-1 . ANY . unstable . -m "rebuild
against newer libusbmuxd"
Hi,
I recently updated the idevices stack in Debian (libplist, libusbmuxd,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sat, 2019-10-05 at 14:50 +0200, Yves-Alexis Perez wrote:
> That beeing said, it would be helpful to know when the problem started
> appearing for you. libimobiledevice wasn't updated recently, but libusbmuxd
> was, and it seems that th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
control: reassign -1 libimobiledevice6
On Fri, 2019-10-04 at 14:30 -0500, Diego Escalante Urrelo wrote:
> Well I noticed the crash because upower uses idevice_new in
> up-device-idevice.c, I guess to monitor idevice's batteries.
> In my system
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Fri, 2019-10-04 at 03:18 -0500, Diego Escalante Urrelo wrote:
> While trying to play around with this, I rebuild libimobiledevice
> locally from the sources available in unstable and the crash went
> away.
> If I reinstall the .deb from the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
control: reassign -1 upower
On Thu, 2019-10-03 at 18:23 -0500, Diego Escalante Urrelo wrote:
> Whenever you connect an iPhone when upower is running, a crash in upower
> is triggered, apparently because libimobiledevice is doing something
> leading
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
control: retitle -1 RFP: idevicerestore
control: reassign-1 wnpp
On Thu, 2019-10-03 at 18:47 +, John Cooper wrote:
> When attempting to install and/or check the files installed by visiting for
> example (
>
-Alexis Perez Sun, 29 Sep 2019 17:14:37 +0200
+
libimobiledevice (1.2.1~git20181030.92c5462-1) unstable; urgency=medium
* New upstream snapshot
diff -Nru libimobiledevice-1.2.1~git20181030.92c5462/debian/gbp.conf
libimobiledevice-1.2.1~git20181030.92c5462/debian/gbp.conf
--- libimobiledevice
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sun, 2019-09-29 at 06:29 -0400, Jeremy Bicha wrote:
> On Sun, Sep 29, 2019 at 5:06 AM Yves-Alexis Perez wrote:
> > I don't have much time or interest anymore in maintaining those theme, so
> > I'm
> > unlikely to fixe tho
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sun, 2019-09-29 at 07:10 -0400, Jeremy Bicha wrote:
> Control: severity -1 serious
>
> I propose that we remove albatross-gtk-theme from Unstable & Bullseye.
> A GTK theme that doesn't work with GTK3 isn't very helpful any more.
>
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Fri, 2019-09-27 at 05:08 +, Yu Franklin wrote:
> Dear maintainer,
>
> Is there any update for this? At least we should be able to update the
> version in sid before backporting some of the patches to testing/stable?
Hey,
I don't have much
control: merge -1 941200
On Thu, 2019-09-26 at 12:02 +0200, Jonas Andradas wrote:
> The file /usr/bin/icat from the libusbmuxd-tools package conflicts with the
> binary file /usr/bin/icat also present in package sleuthkit.
>
> $ apt-file show libusbmuxd-tools | grep icat
> libusbmuxd-tools:
On Thu, 2019-09-26 at 11:51 +0100, Tim Marston wrote:
> Hi,
>
> On Wed, Sep 25, 2019 at 08:36:38PM +0200, Yves-Alexis Perez wrote:
> > Does it depend on the content of the folder? Is there a specific file in
> > that
> > folder which makes Thunar choke on it or some
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Wed, 2019-09-25 at 12:49 +0100, Tim Marston wrote:
> Setting XDG_TEMPLATES_DIR in ~/.config/user-dirs.dirs to point to a
> directory with a lot of stuff in it (other than $HOME, it seems) causes
> delays to Thunar startup that can very easily
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Mon, 2019-09-23 at 21:23 +0200, Damien Pous wrote:
> > You can vt-switch to VT7 to check for yourself, but I'd assume it *is*
> > locked
> > (please report otherwise).
> If I switch to VT7 once the ligthdm login screen has appeared, I get
> to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Mon, 2019-09-23 at 10:35 +0200, Damien wrote:
> When I suspend to ram (eg, by closing the lid), then wake up, I see the last
> state of my screen (desktop with open applications) for ~1sec before getting
> the lightdm password prompt.
> I don't
On Sat, 2019-09-21 at 10:02 +, Patrick Schleizer wrote:
> As for kernel settings (sysctl) and kernel parameters by KSPP... Our
> files in
>
> https://github.com/Whonix/security-misc/tree/master/etc/default/grub.d
>
> and https://github.com/Whonix/security-misc/tree/master/etc/sysctl.d
>
>
control: forwarded -1 https://bugzilla.xfce.org/show_bug.cgi?id=15974
On Thu, 2019-09-19 at 11:41 -0700, Nick Lewycky wrote:
> When focus follows mouse is enabled and automatically raising windows is
> enabled, windows are raised immediately when they get focus instead of
> waiting
> for the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Tue, 2019-09-17 at 14:13 +0200, Geert Stappers wrote:
> bugreport is now open for almost two years, in two days exactly two years.
>
> a patch is one year old.
>
>
> What will happen with this issue?
Hi,
sorry noone replied sooner (I seem to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Tue, 2019-09-17 at 13:29 -0300, Lisandro Damián Nicanor Pérez Meyer wrote:
> I'm terribly sorry if we are being pushy here, it is indeed with no
> bad faith and we definitely don't want to annoy anyone. And yes, we
> are targeting at removing qt4
not intended, but could
you please slow down a bit?
—
Yves-Alexis
> On 17 Sep 2019, at 18:05, Lisandro Damián Nicanor Pérez Meyer
> wrote:
>
> Hi!
>
>> On Tue, 17 Sep 2019 at 12:49, Yves-Alexis Perez wrote:
>>
>> Please don’t, I already told Moritz I’ll handle it w
Please don’t, I already told Moritz I’ll handle it when I have time.
—
Yves-Alexis
> On 17 Sep 2019, at 16:46, Lisandro Damián Nicanor Pérez Meyer
> wrote:
>
> Hi Yves-Alexis!
>
> lightdm is now one of the three packages holding qt4 in testing. Would
> it be possible for you to apply the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sun, 2019-09-15 at 23:26 +0200, Moritz Mühlenhoff wrote:
> > Attached is a patch which drops Qt4 support. It's only used by src:razorqt,
> > which is already RC-buggy anyway and which will be removed soon along with
> > Qt4.
>
> razorqt also got
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sun, 2019-09-15 at 12:48 +, Patrick Schleizer wrote:
> Package: hardening-runtime
> Severity: wishlist
> X-Debbugs-CC: whonix-de...@whonix.org
>
> We now have (at least) three very similar packages.
>
> *
On Fri, 6 Sep 2019 13:13:01 +0200 Elimar Riesebieter
wrote:
> * Michael Biebl [2019-09-05 21:36 +0200]:
>
> > Am 05.09.19 um 21:10 schrieb Elimar Riesebieter:
> > > * Michael Biebl [2019-09-05 20:41 +0200]:
> > >
> > >> Control: forcemerge -1 939468
> > >>
> > >> Am 05.09.19 um 19:48 schrieb
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Thu, 2019-09-05 at 07:28 +0100, Anton Ivanov wrote:
> It is not set to start off with and even if it was
> 95dbus_update-activation-env
>
> will unset it. Lines 8-10 in that are:
>
> unset XDG_SEAT
> unset XDG_SESSION_ID
> unset
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
control: tag -1 unreproducible moreinfo
On Wed, 2019-09-04 at 17:37 +0100, Anton Ivanov wrote:
> No
>
> These are the XDG environment variables:
>
> XDG_CONFIG_DIRS=/etc/xdg
> XDG_CURRENT_DESKTOP=XFCE
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Wed, 2019-09-04 at 12:47 +0100, Anton Ivanov wrote:
> I do not.
>
> It is mounted normally and light-locker worked fine before the upgrade
> to buster.
In your session, is XDG_SESSION_ID set (and to what)? Could you give us the
debug output?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Tue, 2019-09-03 at 20:24 +0200, Yves-Alexis Perez wrote:
> Yes, for some reason it looks like all translations are missing. We'll take a
> look.
I did a local rebuild and it worked fine, so it looks like the buildd somehow
did it wrong, b
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Wed, 2019-09-04 at 11:51 +0100, Anton Ivanov wrote:
> Fails to start with the following message:
>
> ERROR **: 11:46:17.929: session_id is not set, is /proc mounted with
> hidepid>0?
>
> Looks like this bug:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Tue, 2019-09-03 at 19:45 +0200, Mechtilde Stehmann wrote:
> I miss the translation in
> /usr/share/applications/xfce-workspaces-settings.desktop
>
> In German it should be
>
> I found this entry in the po file. but in the *.desktop file.
>
>
Package: ftp.debian.org
Severity: normal
Hi,
gtk2-engines-xfce, the GTK2 theme engine for Xfce, is now obsolete and
unmaintained upstream anyway. All dependencies on it should have been removed
from unstable, so the package can now be removed, it doesn't need to be
part of bulleye.
Thanks in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Thu, 2019-08-29 at 17:31 +0700, Theppitak Karoonboonyanan wrote:
> Package: xfwm4
> Version: 4.14.0-1
> Severity: serious
> Justification: Policy 3.5
>
> Dear Maintainer,
>
> xfwm4 fails to start:
>
> $ xfwm4
> xfwm4: error while loading
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Control: forwarded -1 https://bugzilla.xfce.org/show_bug.cgi?id=15897
On Wed, 2019-08-28 at 21:13 +0200, Martin wrote:
> Bug is filed upstream in the xfce bugtracker:
>
> https://bugzilla.xfce.org/show_bug.cgi?id=15897
Thanks,
- --
Yves-Alexis
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Wed, 2019-08-28 at 14:35 +0200, Jonas Smedegaard wrote:
> Quoting Yves-Alexis Perez (2019-08-28 13:33:57)
> > gtk2-engines-xfce is now deprecated and unmaintained upstream. With the
> > upload of Xfce 4.14, we intend to remove i
Source: debian-parl
Version: 1.9.18
Severity: important
Hi,
gtk2-engines-xfce is now deprecated and unmaintained upstream. With the
upload of Xfce 4.14, we intend to remove it from unstable when possible.
Could you update the dependencies in debian-parl to remove
Source: debian-design
Version: 3.0.13
Severity: important
Hi,
gtk2-engines-xfce is now deprecated and unmaintained upstream. With the
upload of Xfce 4.14, we intend to remove it from unstable when possible.
Could you update the dependencies in debian-design to remove it?
Thanks in advance,
--
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Control: reassign -1 xfwm4
Control: severity -1 wishlist
Control: retitle -1 add support for xrandr hotplug_mode_update property
Control: tag -1 upstream
On Tue, 2019-08-27 at 12:38 +, Martin wrote:
> Screen resolution did change automatically
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
If you report a bug, please keep its address in CC for all communications.
On Tue, 2019-08-27 at 21:07 -0400, Evan Rysdam wrote:
> I don't know. How can I check that information?
It should use the preferred applications for the associated file
Source: xfce4-sntray-plugin
Version: 0.4.11-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Hi,
xfce4-sntray-plugin doesn't seem to build from source anymore. We
noticed that as part of the xfconf transition (part of the Xfce 4.14
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sun, 2019-08-25 at 19:46 +, Niels Thykier wrote:
> jmw already scheduled the binNMUs already so everything but
> xfce4-sntray-plugin has been rebuilt successfully by now (some of the
> builds are still pending uploads though).
Thanks for the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Mon, 2014-01-27 at 19:35 +0100, Yves-Alexis Perez wrote:
> > Finally, I still view this as a minor issue since the DVDs play fine if I
> > enter their location as dvd://,
> >
> > even though the Insert Disc entry i
201 - 300 of 5906 matches
Mail list logo
