> Note that after using this for 15 days now, I still occasionally (say 1 in
> 10 times?) get a flash of the unlocked screen content on resume, followed
> by the XScreenSaver password dialog. Unclear to me what is going on here
> other than "random scheduling races" but that's precisely what this
>
On Monday, 03.06.2019 at 00:19, Jamie Zawinski wrote:
> I'd like to include your code with the next xscreensaver release if that's ok
> with you -- is the latest version on GitHub what you'd like to go with?
Take the version I've just pushed -- I went hunting for the suspected
memory leak, confir
On Sunday, 19.05.2019 at 12:42, Jamie Zawinski wrote:
> Wow, this seems like a huge amount of code to do such a simple thing! Is
> that... normal? Is this really how insane the world has gotten?
Unfortunately, yes, this is the simplest I could do.
It's also why I abandoned all my previous attemp
Hi folks,
I got annoyed by this bug yet again, so decided to try and fix it and came
up with what I think is a minimal yet robust solution, certainly better
than the various hacks floating around on the Internet today:
https://github.com/mato/xscreensaver-systemd
The above repository contains a
Package: dhcpcd5
Version: 6.10.1-1
Severity: normal
Dear Maintainer,
Please consider updating the dhcpcd5 package to the latest upstream version
(6.11.5) in time for inclusion in stretch.
Thank you,
Martin
On Wednesday, 27.05.2015 at 10:05, Martin Lucina wrote:
> > Does "xl mem-set 0 4051" make the messages stop? If not what about using
> > 4050?
>
> I'm not sure if this is due to my rebooting the dom0 since I reported this
> issue, it now appears to be using a
On Sunday, 17.05.2015 at 15:19, Ian Campbell wrote:
> One last thing... If you are able to try it then it would be interesting
> to know if the 4.0.x kernel from sid exhibits this behaviour too.
I can try this at some point next week when I have time to go and
physically kick the box in case it do
On Sunday, 17.05.2015 at 15:14, Ian Campbell wrote:
> On Thu, 2015-05-07 at 21:02 +0200, Martin Lucina wrote:
> > Note that despite the memory setting above, the dom0 has not been allocated
> > exactly the amount asked for:
> >
> > # xl list 0
> > Name
Package: linux-image-3.16.0-4-amd64
Version: 3.16.7-ckt9-3~deb8u1
Severity: normal
Dear maintainer,
my Xen dom0 is printing thousands of these messages to its logs:
# journalctl -b |grep "xen:balloon: Cannot add additional memory (-17)" | wc -l
126892
# uptime
20:50:08 up 3 days, 8:28, 7 user
Package: xen-utils-4.4
Version: 4.4.1-6
Severity: normal
Dear Maintainer,
The xen-utils-4.4 package in jessie is missing the gdbsx binary. This is
useful to have when one wishes to debug Xen domains, and complicated to
obtain if one does not have it ready.
The same package on at least Ubuntu 14
i...@debian.org said:
> They are being uploaded to
> https://people.debian.org/~ijc/tmp/linux/3.16.7-ckt2-2~xen0/ right now.
> I've not booted them myself.
I have just tested these and netfront is working again for me so they're
good to go.
Thanks,
Martin
--
To UNSUBSCRIBE, email to debian-bu
i...@debian.org said:
> On Mon, 2014-12-29 at 12:56 +, Ian Campbell wrote:
>
> > > Should I reopen #767261 or file a new bug for this?
> >
> > A new bug would be best please.
>
> Actually, no need for this, I've applied the fixes locally and am just
> building them before pushing.
Note that
i...@debian.org said:
> On Mon, 2014-12-29 at 12:56 +, Ian Campbell wrote:
>
> > > Should I reopen #767261 or file a new bug for this?
> >
> > A new bug would be best please.
>
> Actually, no need for this, I've applied the fixes locally and am just
> building them before pushing.
Thanks. I
(Cc-ing debian-kernel, note I am not subscribed to this list, please Cc me
on replies)
Hi,
after updating linux-image-3.16.0-4-amd64 from 3.16.7-2 to the latest
3.16.7-ckt2-1 networking on my rumprun-xen [1] domUs stopped working.
Here is an excerpt of the failure during Mini-OS boot:
net TX rin
cjwat...@debian.org said:
> On Tue, Apr 08, 2014 at 07:20:57PM +0200, Martin Lucina wrote:
> > update-alternatives: unknown argument `--quiet'
> >
> > Usage: update-alternatives --install
> >update-alternatives --remove
> >update-alterna
Hi,
I did some inaverdent cut and paste when reporting this bug, here's the
full unmodified apt-get dist-upgrade output.
Martin
-
root@nodbug:~# apt-get dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade...
Package: openssh-client
Version: 1:6.0p1-4+deb7u1
Severity: important
Dear Maintainer,
* What led up to the situation?
apt-get update && apt-get dist-upgrade on a stable wheezy system
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was the outcome
Hi,
I've also been hit by this bug when upgrading an ia64 machine from squeeze.
Is this going to go in wheezy-proposed-updates? I don't see the package
there right now?
Martin
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Conta
Hi,
following up on this bug, I tried booting the generic
linux-image-3.2.0-4-itanium kernel and this does not boot on my zx6000
either, with the exact same symptoms as the -mckinley kernel.
This means that none of the kernels supplied with wheezy boot :-(
Martin
signature.asc
Description: Dig
Hi,
can we get this patch into a point release of wheezy?
I just upgraded a system running postfix-policyd-spf-python and ran into
the same problem. The patch in this bug fixes the problem for me, but it
would be nice if it could be pushed into the next point release of wheezy.
Thanks,
Martin
Hi,
I've just ran into this exact same problem after upgrading a zx6000 system
I run from squeeze.
The machine has two identical 1.4Ghz processors installed:
processor : 0
vendor : GenuineIntel
arch : IA-64
family : 31
model : 1
model name : Madison
revision : 5
archrev
Package: installation-reports
Severity: grave
Tags: d-i
Justification: renders package unusable
-- Package-specific info:
Boot method: usb stick, serial console
Image version:
http://d-i.debian.org/daily-images/armel/20130325-08:34/kirkwood/netboot/marvell/dreamplug/
Date: Mar 25 11:43:51 +010
Package: wnpp
Severity: normal
Given that my interest is primarily focused on the Crossroads I/O fork of
ZeroMQ (already packaged in Debian as libxs), I have a conflict of interest in
maintaining the zeromq package.
In the interim I will continue to package new stable (2.x) versions, but that
is
al3x...@gmail.com said:
> Hello,
>
> it seems like the libpgm package has been in the archive for some time now,
> is there any news on the zeromq side?
The package has been available for some days now, I am waiting on my
sponsor to actually upload it.
Cheers
-mato
--
To UNSUBSCRIBE, email
al3x...@gmail.com said:
> Hi,
>
> are there any blockers that prevent you from uploading zeromq 2.1.4 to
> unstable?
I'm waiting for openpgm to hit unstable at which point I can integrate with
that and get rid of the embedded OpenPGM in the libzmq package.
Cheers,
-mato
--
To UNSUBSCRIBE, e
Hello,
is there any progress on this? The upstream 2.1.6 release of zeromq now
supports --with-system-pgm, so I would like to get rid of the embedded
OpenPGM library ASAP.
Is there any way I can help?
Cheers,
-mato
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a
tfh...@debian.org said:
> Package: src:zeromq
> Severity: wishlist
>
> 2.1.3 of zeromq is out upstream. Any chance of this hitting unstable
> soon?
Yes, I expect to upload to experimental tomorrow or Friday and then to
unstable once we're happy with the package. There will be a soname change,
so
Hi,
I would like to proceed with this. Adrian, are you OK with going over the
workflow with me by email? I would prefer at this stage that you sponsor
the upload of 2.0.7 and maybe one more release, and can then look at
applying for DM/DD.
-mato
avbid...@fortytwo.ch said:
> Package: wnpp
> Sever
Hi,
I've just spent ~4 days debugging some software we're developing only to
discover we were being hit by this bug. It seems that the fix for this
didn't make it into sarge for amd64.
Would it be possible to make sure that the fix for this is included in
the next point release of sarge?
Thank
Hi,
I'm getting this as well, on a new install of Sarge on amd64.
Looking at the Blackdown and Sun Java download pages, AFAICT there is
(unsurprisingly) no 1.3.x version of the JRE for amd64, so I would
suggest that this code in the firefox launch script be disabled if
running on amd64.
The actu
30 matches
Mail list logo
