I'm trying ...
https://lore.kernel.org/netdev/2c0a1779713b5bdd443a8e8258c7d...@manjaro.org/
https://lore.kernel.org/netdev/e1s9rpa-0006jy7-1...@ws2.gedalya.net/
On 5/21/24 10:55 PM, Luca Boccassi wrote:
> This has always been enabled by default, even in stable.
What is the meaning of this line in the changelog for 6.9.0-1, and why does it
correlate with an actual change in behavior?
Quote:
* Enable output with colors on terminals
Package: iproute2
Version: 6.9.0-1
Severity: minor
Hello,
The newly enabled colored output is rather hard to read on dark backgrounds,
especially the deep blue color used for IPv6 addresses.
Setting COLORFGBG=";0" as the manpage suggests helps a lot.
Consider a scenario when this command is
On 5/21/24 2:41 AM, Salvatore Bonaccorso wrote:
> Can you please test if you have the same behaviour with recent
> upstream kernels? For instance test with 6.8.9-1 in unstable, or if
> you can build upstream stable version 6.8.10, 6.9.1.
6.8.9 - same behavior
6.9.1 from pristine upstream tar
forwarded 1026863 https://gitlab.com/libvirt/libvirt/-/merge_requests/218
tags 1026863 fixed-upstream
thanks
Package: libvirt-daemon
Version: 8.10.0-2
Hello,
Given the following stanza in a domain XML,
with bridge='eno1' instead of dev='eno1', libvirtd segfaults.
See attached backtrace, libvirtd invoked with -v for extra noise
Thanks,
Gedalya
2022-12-22 19:29:00.366+
Package: linux-image-5.10.0-8-amd64
Version: 5.10.46-4
Hi,
amd-pmc is needed on recent AMD Ryzen laptops in order to properly enter s2Idle.
Another module apparently relevant on recent Ryzen laptops is
CONFIG_AMD_SFH_HID, although this PCI device is not present on my laptop.
Thanks,
Gedalya
On 3/9/21 5:31 PM, maximilian attems wrote:
>
>> the display stopped updating as soon as amdgpu took over, and it never came
>> back.
>> The firmware is needed of course, and as a side note, it could be nice if
>> the kernel could fail more gracefully, somehow bringing the display back (it
>>
Package: firmware-amd-graphics
Version: 20210208-3
Hi,
I've received my new laptop with a Ryzen R7 5800U and the display stopped
updating as soon as amdgpu took over, and it never came back.
The firmware is needed of course, and as a side note, it could be nice if the
kernel could fail more
Just in case this requires explicit clarification:
iptables-restore < /etc/iptables.conf
# now I have a firewall
nft flush ruleset
# now I don't
iptables-restore < /etc/iptables.conf
# now I do
nft -f /etc/nftables.conf
# now I have whatever that is, read: nothing by default
This would have
On 3/5/21 6:55 PM, Matthew Vernon wrote:
> Hi,
>
>> I just got orphan-sysvinit-scripts pulled in on a few boxes where I
>> happen to have nftables installed but rules are still defined and
>> loaded by iptables, called by a locally-defined init script.
>
> I'm slightly confused by your report,
# Default-Stop: 0 1 6
Which has stop actions (which actually flush the ruleset) and loads *after*
network interfaces are already up.
Thanks,
Gedalya
On 1/29/21 5:00 AM, Santiago Ruano Rincón wrote:
> Could you try it please?
Hi,
Sorry for the delay. I had to find the time to recreate that situation.
Now it works quite nicely:
knot[27809]: error: [gedalya.com.] zone already configured, ignoring
knot[27809]: error: [gedalya.net.] zone
Package: ser2net
Version: 4.3.2-1
Severity: grave
When attempting to start ser2net I get the message:
/usr/sbin/ser2net: symbol lookup error: /usr/sbin/ser2net: undefined
symbol: gensio_alloc_mdns
This happens when I start it in any way, such as just invoking the
executable with no parameters,
Hello,
I find the following is enough:
--- unbound.init 2020-12-24 00:34:24.0 +
+++ /etc/init.d/unbound 2021-01-27 18:15:25.663526469 +
@@ -42,7 +42,7 @@
stop)
log_daemon_msg "Stopping $DESC" "$NAME"
- if start-stop-daemon --stop --quiet --oknodo
Hi Jan,
For some reason I didn't get your message via email, but saw it when looking at
the Debian bug.
I see a fix for this in 3.0.4 (89c9a233). When that's packaged I'll try to
confirm that this is fixed.
Thank you!
Sorry, forgot to include the backtrace. Attached.
(gdb) run
Starting program: /usr/sbin/knotd -c /etc/knot/knot.conf
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7ffad0ee8700 (LWP 17295)]
[New Thread
Package: knot
Version: 3.0.2-2
When zones are defined twice, in a catalog zone and in the config, after adding
the unsigned zone files (gedalya.net and/or gedalya.com below) and restarting
knot, knot seems to start generating keys for, and signing the same zone twice,
in parallel, and
Opened an issue with ungoogled-chromium to discuss this on their end.
https://github.com/ungoogled-software/ungoogled-chromium-debian/issues/184
Hello,
I wonder if some collaboration would be possible with the ungoogled-chromium
people, and linux mint (#975060)?
In the case of linux-mint, they seem to have given up in Debian being their
upstream for this package, and ungoogled-chromium seems to be held back,
adhering to Debian as
Package: src:linux
Version: 4.19.87-1
Dear Maintainer,
* What led up to the situation?
Not sure exactly. Normal operations.
I'll include some facts that I suspect might be relevant:
Most volumes are mounted with the "discard" option. The I/O operations in
question seem to have involved
See:
https://bugs.launchpad.net/ubuntu/+source/strongswan/+bug/1846283
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/net/ethernet/intel/ixgbe/ixgbe_main.c?h=v5.4-rc1=f39b683d35dfa93a58f1b400a8ec0ff81296b37c
(linked therein)
And:
On 9/9/19 3:14 AM, Sam Kuper wrote:
> On 29 Apr 2013, Richard James Salts wrote[0]:
>> [..] pcretest was a handy utility. It would be good if the program
>> could instead be included with the pcregrep package in pcre-utils
>> package or the like.
> On 31 Jul 2012, G
I got this behavior with "session":{"restore_on_startup":1} in
~/.config/chromium/{profile}/Preferences.
I only get this on my laptop, for some reason, not my desktop.
I can set that to 0 instead of 1 and everything is OK, except my saved tabs of
course which are not restored.
Also, I've
on here, but I'd be happy
to investigate further given some guidance.
Also, if someone could provide some tips for a workaround that would be nice,
since this is currently simply not working.
Thanks,
Gedalya
ipsec statusall:
Connections:
office-1: %any...office IKEv2, dpddelay=30s
office-1
sr/share//ibus-sunpinyin/setup/main.py", line 133, in read_config
self.__set_value(self.v)
File "/usr/share//ibus-sunpinyin/setup/main.py", line 158, in __set_value
self.widget.set_active(self.unwrap(v))
AttributeError: 'HScale' object has no attribute 'set_active'
Thanks,
Gedalya
n write
return self.config.set_value(section, key, type(self.default)(v))
File "/usr/lib/python3/dist-packages/gi/overrides/IBus.py", line 87, in
set_value
super(Config, self).set_value(section, name, value)
TypeError: argument value: Expected GLib.Variant, but got int
Thanks
On 2/13/19 12:54 AM, Sven Hartge wrote:
> Maybe adding the Release to the first sentence to convey that this is
> only a problem for Stretch and not Buster
Yea.
Well, since mpm_event is still the default in buster :-)
--->8---
By default, Apache 2.4 as provided by Debian uses mpm_event
On Mon, 11 Feb 2019 14:28:00 +0100 Sven Hartge wrote:
>
> Language of course needs a bit of refining from my German-English.
>
Nothing atrocious, really, but I was able to come up with something a bit more
concise.
--->8---
By default, Apache 2.4 as provided by Debian uses mpm_event
On 2/13/19 12:38 AM, Jan Wagner wrote:
> backports is not meant for fixing things. beside that it would require
> all rebuilding most of the additional apache modules not shiped by the
> apache2 source package.
So we're back to doing nothing at all?
I'm not at all advocating backports as a
On Sun, 10 Feb 2019 14:36:11 +0100 (CET) Stefan Fritsch
wrote:
> If we did a backport, rhe risk of introducing regressions would be quite high.
So how about backporting it to stretch-backports? Isn't that what the backports
section is for?
It would be then available to those who have
> This currently looks like this now (after I have uninstalled
> cgroupfs-mount):
>
> → findmnt -R /sys/fs/cgroup
> TARGET SOURCE FSTYPE OPTIONS
> /sys/fs/cgroup tmpfs tmpfs rw,nosuid,nodev,noexec,mode=755
> ├─/sys/fs/cgroup/unified cgroup2 cgroup2
>
On Wed, 30 Jan 2019 01:37:14 +0100 Axel Beckert wrote:
> > Moving udev into its own special cgroup didn't change anything: udev
> > is still running, same PID, and and the same goes for ntpd.
> > Everything else is killed.
>
> And here you gave me the right hint: cgroups!
>
OK, Lorenz
On Sun, 27 Jan 2019 03:20:46 +0100 Lorenz wrote:
>
> Non-Systemd users can workaround this by using the init script from systemd
> 239-7
>
> https://salsa.debian.org/systemd-team/systemd/blob/debian/239-7/debian/udev.init
>
> or by editing the current init script replacing the --background option
> It just happened again, triggered by wireshark-dkms
s/wireshark/wireguard/
Coincidentally, I'm also using wireguard on my router. But I haven't been able
to reproduce this simply by installing wireguard and setting up a few
interfaces. Wait for the end
Also, on my router, ntpd is moved
Package: vlan
Version: 2.0.3
Hello,
/etc/network/if-pre-up.d/vlan and /etc/network/if-post-down.d/vlan are now
installed without the 'x' bit set. This makes vlan interfaces in
/etc/network/interfaces useless.
Thanks,
Gedalya
.
Regards,
Gedalya
I've had seemingly the same issue. After several weeks of running a backported
apache2 2.4.37-1 the issues are gone.
Previously it was happening several times every day, with the outage lasting
sometimes 10 minutes or so.
This was very difficult to troubleshoot, as nothing is logged, and it
access and don't normally have
console access. All I can say is it has spanned several kernel versions and
been going on definitely since systemd 239-?.
Now I've attached a serial console cable so I'm more able to investigate. I
welcome your suggestions.
Thank you all,
Gedalya
On 11/11/18 1:07 AM, Brian Potkin wrote:
> Gedalya, if you are on unstable please upgrade to 3.18.10+dfsg0-2. If
> you are on testing, install libsane-hpaio from unstable. This is the
> only package you need for scanning; it will overwrite models.dat.
>
> How do you go on now?
Package: exim4-config
Version: 4.90-4
In line 356, update-exim4.conf turns empty variables into the string "empty".
As a result, we get things like this:
MAIN_RELAY_TO_DOMAINS=empty
which means that an email to gedalya@empty is allowed through, and that's
probably not the intende
ot;debian/rules clean" gets called
early in the build process. See my results attached.
Thanks for maintaining this! :-)
Gedalya
>From ecaa19166f840c3391c701aa720c13ce2d53f6e9 Mon Sep 17 00:00:00 2001
From: Gedalya <geda...@gedalya.net>
Date: Mon, 22 Jan 2018 07:33:56 +
On 12/01/2017 02:04 PM, Brian Potkin wrote:
Sorry; another typo. It's drv:///hpcups.drv/hp-envy_4500_series.ppd
OK, finally I get:
device `hpaio:/net/envy_4500_series?ip=192.168.9.238' is a
Hewlett-Packard envy_4500_series all-in-one
You are definitely not wasting my time. I'm unsure
On 12/01/2017 07:05 PM, Brian Potkin wrote:
> How does that sound?
In terms of gut-feeling / speculation, we have arrived at what was obvious to
me when opening this bug.
> (It does not look at the broadcasts when the print queue is operative).
The same lines get printed to syslog, so it does
On 12/01/2017 05:51 PM, Brian Potkin wrote:
> > With CUPS running, or with models.dat edited:
> >$ scanimage -L
> > device `hpaio:/net/officejet_pro_8710?ip=192.168.9.238=false' is a
> Hewlett-Packard officejet_pro_8710 all-in-one
And now, with cupsd running and Bonjour enabled:
device
On 12/01/2017 05:51 PM, Brian Potkin wrote:
>
> I would appreciate that you do one re-test. Depending on the outcome, I
> think we will see light at the end of the tunnel. :)
>
> You report:
>
> > When cupsd is running and the AIO is configured as a printer
> > in CUPS, this issue does not
On 11/30/2017 11:19 PM, Brian Potkin wrote:
lpadmin -p 4500 -v hp:/net/envy_4500_series?ip=192.168.9.238 -E -m
drv:///hpcups.drv/hp_envy_4500_series.ppd\
^
^
We both have access to the same manual. :)
You're right. But I'm just not following most of
On 11/30/2017 03:11 PM, Brian Potkin wrote:
> I wonder how you would go on with the queue
>
>
> lpadmin -p 4500 hp:/net/envy_4500_series?ip=192.168.9.238 -E -m
> drv:///hpcups.drv/hp_envy_4500_series.ppd\
lpadmin: Unknown argument "hp:/net/envy_4500_series?ip=192.168.9.238".
not sure where to
On 11/23/2017 09:08 PM, Brian Potkin wrote:
>>> This device-uri should also be given by hp-makeuri. Would you confirm
>>> this and check printing takes place.
>> This in fact works only with the original models.dat, with the hp_ prefix:
> That in itself should indicate something to you.
>
I get
On 11/23/2017 09:08 PM, Brian Potkin wrote:
>
>>> So where does scanimage get the uri from when cups is running? From the
>>> Bonjour broadcasts? What happens when you deactivate broadcasting on the
>>> printer?
>> I don't know how to do that.
> Go to http://192.168.9.238 with a browser. Look
On 11/23/2017 05:44 PM, Brian Potkin wrote:
> On Thu 23 Nov 2017 at 14:05:38 +0100, Gedalya wrote:
>
>> On 11/23/2017 01:37 PM, Brian Potkin wrote:
>>>> Note: In order to produce this, I need to stop cupsd. Somehow, at some
>>>> point sane started finding the
On 11/23/2017 01:37 PM, Brian Potkin wrote:
>
>> Note: In order to produce this, I need to stop cupsd. Somehow, at some
>> point sane started finding the scanner via CUPS, the printer being
>> configured there.
> I take this to mean you configured the printer with something like
> hp-setup and the
On 11/22/2017 01:46 PM, Brian Potkin wrote:
> I forgot to ask: is scanning successful if, instead of duplicating the
> section. you just delete the "hp_" from [hp_officejet_pro_8710]?
Yes, same effect.
On 11/21/2017 08:09 PM, Brian Potkin wrote:
>
> Hello Gedalya. Thank you for your report. I forwarded it upstream and
> now you will see there is a reply. Please would you respond to that
> message there as I am unable to speak for you.
I'll look into that. Thank you!
>
> Me
59706, and
renaming it to [officejet_pro_8710] as the log suggests. That works fine.
Regards,
Gedalya
This is affecting EAP with wpa_supplicant.
See https://bugs.debian.org/877904
id="UPC Wi-Free" auth_failures=2 duration=37 reason=AUTH_FAILED
Related bug reports:
https://bugs.debian.org/875423
https://bugs.debian.org/871987
https://bugs.debian.org/873302
Regards,
Gedalya
On 08/26/2017 07:08 PM, Kurt Roeckx wrote:
> On Sat, Aug 26, 2017 at 02:50:37PM +0800, Gedalya wrote:
>> On 08/26/2017 02:58 AM, Kurt Roeckx wrote:
>>
>>> openvpn doesn't seem to make use of the
>>> SSL_CTX_set_min_proto_version() function yet. I've attached a
On 08/26/2017 02:58 AM, Kurt Roeckx wrote:
> openvpn doesn't seem to make use of the
> SSL_CTX_set_min_proto_version() function yet. I've attached a
> patch that I didn't even try to compile that I think should do the
> right thing.
>
Thanks for this!
It now connects fine with the setting
I tried openssl 1.1.0f-5 and it is indeed better with e.g. s_client.
However, I've locally built openvpn (and pkcs11-helper) with openssl 1.1.0.
I'm not sure whether this is a bug with openvpn or an issue with this latest
patch to openssl, but I've tried both these settings:
tls-version-min 1.0
TLSv1.
I came across both types of issues just in the past 24 hours.
I can always downgrade, or just use a stretch (or older) system for this minor
task, but it seems this issue could be rethought.
I think hard-disabling at compile time is a little too soon.
Thanks,
Gedalya
On Fri, 20 Jan 2017 07:38:32 -0700 LaMont Jones wrote:
>
> Can you provide a named.conf that reproduces the issue?
>
I've tried commenting out everything locally modified, leaving basically a
default config.
It seems the only thing needed to reproduce this issue is to run bind in a
chroot.
On 01/07/2017 06:47 PM, Gedalya wrote:
> On the other hand, this did work well in all versions of systemd prior to
> 232-1
Misspoke: it came and went several times.
On 01/07/2017 06:43 PM, Michael Biebl wrote:
>> As stated in the last few messages in this bug report, the problem appears
>> exclusively when not using systemd as init.
>> At Yves-Alexis's request I confirmed the symptoms do not occur when booting
>> with systemd as init.
>>
>> This is the n'th
well, things did work when using systemd as init.
Thanks,
Gedalya
reassign 846661 systemd 232-1
thanks
On 01/07/2017 10:06 AM, Yves-Alexis Perez wrote:
> On Fri, 2017-01-06 at 22:09 -0500, Gedalya wrote:
>> I've confirmed the problem appeared with systemd 232-1.
>> Downgrading to systemd 231-10 fixes everything.
>>
>> This no doubt has to do with me refusing to us
On 12/07/2016 03:22 AM, Yves-Alexis Perez wrote:
> It's unlikely to be in light-locker/lightDM, try to check what's upgraded in
> the Xorg stack (xserver, driver etc.).
>
>
I've confirmed the problem appeared with systemd 232-1.
Downgrading to systemd 231-10 fixes everything.
This no doubt has
Package: ipset
Version: 6.30-2
Severity: minor
I'm getting a bash completion error on a new server I've just set up. This
actually doesn't happen on my desktop, though both are running up-to-date
stretch.
I'm attaching the output I get when running 'bash -lx' and then typing 'ipset
de[TAB]'
On 12/18/2016 08:14 AM, Andreas Metzler wrote:
> Fair enough. See GIT head:
> * Add macro IGNORE_SMTP_LINE_LENGTH_LIMIT to allow disabling the SMTP DATA
> physical line limit check for both for SMTP DATA ACL and remote_smtp*
> transports. Closes: #828801
>
> cu Andreas
Looks great!!
Thanks!
On 12/17/2016 11:48 AM, Andreas Metzler wrote:
> Control: tags -1 pending
>
> exim4 (4.88~RC6-2) UNRELEASED; urgency=medium
> .
>* Add macro MAX_PHYSICAL_LINE_LENGTH with a default value of 998 to allow
> overriding the SMTP physical line length limit both for SMTP DATA ACL and
>
Reverting lightdm back to 1.18.2-2 didn't help.
Also I wasn't able to unlock per #846278 using 'loginctl unlock-session {X}',
however my init is sysvinit, so maybe that's an issue.
Package: light-locker
Version: 1.7.0-3
Severity: important
After pulling a bunch of new packages from sid - xorg-server-core, mesa, and
dbus, light-locker stopped working.
When unlocking, after putting in my credentials the screen remains black.
Killing the process brings the desktop back.
Package: chromium
Version: 55.0.2883.75-1
Over here it crashes much less, but still crashes on web.whatsapp.com and
sometimes on certain facebook pages.
The attached debugger output is from web.whatsapp.com
-- System Information:
Debian Release: stretch/sid
APT prefers unstable-debug
APT
Package: chromium
Version: 54.0.2840.101-1
When opening e.g. [0], chromium crashes (Aw snap!).
When attempting to reproduce debugging info for this, I wanted to run chromium
in a clean profile. When running chromium for the first time without a profile,
it also crashed.
In the attached
On 11/21/2016 11:11 AM, Gedalya wrote:
> On 11/20/2016 02:57 AM, intrigeri wrote:
>> Resizing also works with GNOME (Stretch VM, sid libvirt host), so I'm
>> retitling this bug to make it more specific. Can you still reproduce
>> it with MATE and current spice-vdagent
On 11/20/2016 02:57 AM, intrigeri wrote:
> Resizing also works with GNOME (Stretch VM, sid libvirt host), so I'm
> retitling this bug to make it more specific. Can you still reproduce
> it with MATE and current spice-vdagent?
Yes. Reproducible with fully updated host and guest.
On 11/10/2016 05:26 AM, Bernhard Schmidt wrote:
> I have just uploaded 2.5.5~dfsg-3 with all patches bundled in Asterisk
> applied. Please take a look, should be available shortly.
Installed, works just fine.
OK, confirmed.
The patch (r5401) works, we're back with the previous behavior:
[Nov 9 20:43:33] ERROR[14871]: res_pjsip.c:2883 ast_sip_create_dialog_uac:
Could not create dialog to endpoint '' as URI '' is not valid
[Nov 9 20:43:33] ERROR[14871]: chan_pjsip.c:1947 request: Failed to
r5401 seems to be the fix:
https://trac.pjsip.org/repos/ticket/1946
However I'm having trouble adding a patch with this source package :-(
On 11/09/2016 06:26 PM, Gedalya wrote:
> asterisk: ../src/pjsip/sip_auth_client.c:507: pjsip_auth_clt_deinit:
> Assertion `sess && sess->endpt' failed.
> Aborted
>
> This is me calling myself via my outbound trunk and coming back in via my
> inbound trunk
P/*-",
"PJSIP/*@trunk-didlogic") in new stack
-- Called PJSIP/*@trunk-didlogic
-- Executing [*@from-external:1]
Goto("PJSIP/trunk-vitelity-in-0002", "internal,gedalya-all,1")
-- Goto (internal,gedalya-all,1)
-- Executing
On 11/06/2016 05:50 PM, Bernhard Schmidt wrote:
> Nothing productive on the upstream mailinglist (or rather disturbing,
> they say that ABI can change in backward incompatible way even in minor
> versions and you're always expected to recompile),
Yea, I followed the conversation there. Looks
On 11/03/2016 07:39 AM, Bernhard Schmidt wrote:
> Confirmed. If you start Asterisk in the foreground you actually get an
> assertion
>
> asterisk: ../src/pj/os_core_unix.c:1254: pj_mutex_lock: Assertion
> `mutex' failed.
> Aborted
>
> Haven't done any further debugging until now, since we can't
. No error shows up, nothing in dmesg either.
-- Executing [gedalya-all@internal:1]
Set("PJSIP/trunk-vitelity-in-", "CDR(peername)=trunk-vitelity-in") in
new stack
-- Executing [gedalya-all@internal:2]
MixMonitor("PJSIP/trunk-vitelity-in-"
I have two KVM servers where I'm doing GPU passthrough to a VM. Both are
running linux 4.6.4.
We're using an NVIDIA GPU which means I have to hide KVM (kvm=off, or
).
As a result, current_clocksource is tsc. ntpd shows a drift of ~0.
So in seems that the tsc values the VM is getting are
13231 [002] 387476.246883: kvmclock_update_fn
<-process_one_work
kworker/0:47-13195 [000] 387476.246884: kvmclock_update_fn
<-process_one_work
Yet, the guests still seem to be getting the unadjusted time.
Thanks,
Gedalya
Package: src:linux
Version: 4.7.5-1
Severity: normal
Dear Maintainer,
When booting the host with linux 3.16, it looks like kvm-clock provides guests
with time as adjusted by ntpd.
This looks like this (note the 'frequency' variable [0]):
host :
# ntpq -crv
associd=0 status=0415 leap_none,
fixed 833501 52.0.2743.116-2
found 833501 53.0.2785.92-2
thanks
now that we're back with gcc 6, same crashes occur with facebook, google maps
and other sites.
This got it working for me
--- rules.orig2016-09-06 15:44:51.692191414 -0400
+++ rules2016-09-06 15:47:29.097229998 -0400
@@
On Sun, 07 Aug 2016 21:36:57 +0100 "George B." wrote:
> Package: exim4-config
> Version: 4.87-3
> Followup-For: Bug #828801
>
> Hello,
>
> I have just hit this issue trying to submit a bug report using the
> reportbug package (which in turn connects to my Exim SMTP server to send
> the message).
>
Rebuilt locally against stretch (using pbuilder). Seems to work fine now.
Package: exim4-config
Version: 4.87-3
Ref: #797919
I've noticed the recent addition to acl_check_data in
conf.d/acl/40_exim4-config_check_data:
denymessage= maximum allowed line length is 998 octets, \
got $max_received_linelength
condition = ${if >
On my girlfriend's laptop, chromium 50.0.2661.94-1 was crashing on all websites
that were attempted with "aw snap" and the same message:
ERROR:zygote_host_impl_linux.cc(162)] Failed to adjust OOM score of renderer
with pid ... : Permission denied
It's running stretch amd64, fully up to date,
Now I've installed the Cinnamon desktop. When logging in I get a notification
that we're running in software rendering mode. qxl is loaded. Resizing works:
spice-vdagent[2858]: 0x56310d707dc0 connected to
/var/run/spice-vdagentd/spice-vdagent-sock
spice-vdagent[2858]: Selection window: 18874369
Package: spice-vdagent
Version: 0.15.0-1.3
Dear Maintainer,
Running Debian Stretch as a guest under KVM using virt-manager. The host is
also running Debian Stretch.
Using MATE with lightdm, in case that matters.
Resizing the VM viewer window doesn't cause spice-vdagent to adjust the
resolution
On 04/20/2016 08:13 PM, Gedalya wrote:
> Going to try this patch now.
Built with pbuilder against sid. /usr/lib/chromium/chromium is now ~2MB smaller.
New packages pulled in from sid: libavcodec57 libavformat57 libavutil55
libswresample2 - version 7:3.0.1-3
ldd does show it's actually using t
On Wed, 20 Apr 2016 09:31:34 +0200 Sebastian Ramacher wrote:
> On 2016-04-16 10:20:26, Michael Gilbert wrote:
> > control: tag -1 help, confirmed
> > control: severity -1 grave
> > x-debbugs-cc: pkg-multimedia-maintain...@lists.alioth.debian.org
> >
> > Jose A. Fernandez Gonzalez wrote:
> > >
Package: chromium
Version: 50.0.2661.75-1
Severity: normal
Dear Maintainer,
* What led up to the situation?
Upgraded chromium from 49.0.2623.108-1
* What exactly did you do (or not do) that was effective (or
ineffective)?
Opened up vimeo.com, or file:// {...}.m4v also does the trick
On Mon, 14 Mar 2016 01:56:06 +0100 Jonas Smedegaard wrote:
>
> If noone else cares, I will consider step up and take over maintaining
> this package (but I really would prefer not to do so: I have plenty of
> other packages to look after already).
>
> - Jonas
I see you're preparing a release in
Package: php5.6-fpm
Version: 5.6.17+dfsg-1
Severity: grave
Hi,
apt-get install php5.6-fpm results in:
The following packages have unmet dependencies:
php5.6-fpm : Depends: php5.6-json but it is not installable
Thanks!
1 - 100 of 242 matches
Mail list logo
