Hi Andreas,
On Tue, Oct 06, 2015 at 10:36:36AM +0200, Andreas Beckmann wrote:
> On 2015-09-30 18:41, Andreas Beckmann wrote:
> > I'll try to remember to add back the support in the next backport. It's
> > a trivial change :-)
>
> This was re-enabled in 340.93-3~bpo8+1 which I just uploaded.
Than
Dear Maintainers,
please note that
* nvidia-kernel-*: [i386] Drop support for building amd64 kernel modules.
from 340.76-5 also hits 340.76-5~bpo8+1 from jessie-backports, which
might be considered a regression. In my case, I was running 340.76-2
(manually "backported" to jessie from unstable,
Hi,
isn't that a bug in e2fsck anyway? There is accept_time_fudge which
defaults to true and should take care of this situation. Even when it
wouldn't default to true, my e2fsck.conf already had its alias
buggy_init_scripts set to 1. Nevertheless, I'm briefly seeing an fsck
running now on every bo
Re,
On Mon, Oct 20, 2014 at 08:29:33PM +0200, Andreas Beckmann wrote:
> On 2014-10-20 20:11, Beck, Andre wrote:
> > Given that metamode, the result is an offset nVidia Logo (which you would
> > have seen hadn't you disabled it ;) - and the login window on the wrong
> > p
Hi,
exact same issue here on a HP Elitebook 8540p with NVS 5100M. Seems the
version of the blob which lurks in this package is seriously borked.
Martin, you may actually *have* a working gdm3 login, you just don't
see it. It's been the same here with kdm, the login window of which
is displayed on
Package: resolvconf
Version: 1.75
Followup-For: Bug #749405
On Sun, Jun 01, 2014 at 10:59:00AM +0100, Edward Allcutt wrote:
>
> Dear Maintainer,
>
> I generally concur with Andre, with one exception.
>
> I believe the WantedBy line should reference networking.service as that
> will be pulled in
Hi,
I was affected by the same bug and found that resolvconf.service, while
loaded, was actually never run by systemd (jessie). Now I know nothing
about systemd and the bizarre maze of targets and services it comprises,
but it appeared to me that network.target might not be the ideal target
to use
Hi Bernhard,
On Sat, Jul 13, 2013 at 09:44:47PM +0200, Bernhard Schmidt wrote:
> Am 09.07.2013 00:07, schrieb Bernhard Schmidt:
>
> Hello Andre,
>
>> please backport Commit 5985de2ace378ff8179ab9229470bd321728d061 (Bugfix
>> in walkSnmpTable(): maxrepetitions is only applicable in SNMPv2 or v3) an
Hi Andreas,
On Wed, Jan 23, 2013 at 01:22:59AM +0100, Andreas Beckmann wrote:
> On 2013-01-22 19:19, Andre Beck wrote:
> > for reasons I don't grok entirely, 304.64-4 doesn't fix the build issue
> > for me, though I'm building against linux-3.7.y stable (which in turn
> > is built using kernel-pac
9 matches
Mail list logo
