Bug#863389: Fwd: Bug#863389: linux-image-4.9.0-0.bpo.3-amd64: After update to linux-image-4.9.0.0-0.bpo.3, no route to host via IPV4

Hi Ben, Thanks for the reply. You're absolutely right about the ordering of the iface statements. I modified my interfaces file such that the bonding parameters followed "iface bond0 inet static" and now it loads the bonding module and adds a default gateway for IPV4. The configuration below

Bug#863389: Missing default Route

It appears that the "no route to host" issue was caused by a missing default route. "route add default gw 192.168.1.1 dev bond0" fixed the issue. The question is why my routing table was missing such a default route. My /etc/network/interfaces file specifically references the gateway, as

Bug#852799: mcelog: Mismatch of structure `mce`

On Mon, 6 Feb 2017 15:09:08 +0500 Andrey Rahmatullin wrote: > On Mon, Feb 06, 2017 at 10:50:18AM +0100, Paul Menzel wrote: > > Will you package v148, and will it get into Debian 9 (Stretch)? > No, stretch is frozen for issues below important severity. > > -- > WBR, wRAR The

Bug#878827: Auto-login no longer works as of 3.26.0-1 [Regression]

Package: gdm3 Version: 3.26.1-3 Severity: normal Dear Maintainer, * What led up to the situation? I noticed that auto-login stopped working in GDM after the package was updated from 3.25.90.1-2 to 3.26.0-1. I did not make any configuration changes between versions. * What exactly did you

Bug#871619: zfs-dkms: Please package ZFS 0.7.0

For those too inpatient to wait for an official Debian build, I managed to compile kmod packages from the ZoL source. See here for details: https://github.com/zfsonlinux/zfs/issues/6606 On Wed, Aug 9, 2017 at 8:42 PM, Jason Cohen wrote: > Package: zfs-dkms > Version:

Bug#874182: Regression breaks hourly, daily, weekly, and monthly snapshots

Package: zfs-auto-snapshot Version: 1.2.2-1 Severity: Important Dear Maintainer, The update to zfs-auto-snapshot 1.2.2-1 has caused a regression preventing hourly, daily, weekly, and monthly auto snapshots from running. Frequent snapshots still work. Reverting the scripts to those used by the

Bug#879900: apparmor-profiles-extra: Totem segfaults when apparmor profile is enforced

Hi, I would be happy to help. I have several machines running Stretch with a variety of hardware and uses (desktop/server, Intel/NVIDIA GPUs etc.). Are there specific apparmor profiles you wish to test? As for the totem profile on Stretch, simply adding #include to

Bug#879900: apparmor-profiles-extra: Totem segfaults when apparmor profile is enforced

Woops. The second line should read: "As for the totem profile on Stretch, simply adding #include to /etc/apparmor.d/local/usr.bin.totem and reloading the profile did not fix the issue:"

Bug#879900: apparmor-profiles-extra: Totem segfaults when apparmor profile is enforced

Package: apparmor-profiles-extra Version: 1.15 Severity: important Dear Maintainer, Totem suffers a segmentation fault upon startup when its respective apparmor profile is set to enforce mode. It starts fine when the apparmor profile is set to complain mode. I have not modified the

Bug#879900: Acknowledgement (apparmor-profiles-extra: Totem segfaults when apparmor profile is enforced)

I failed to mention earlier but I saw the same behavior on my Buster system running version 1.14 and 1.15.. I am also seeing the same behavior on my Stretch install: jason@jason-desktop:/etc/apparmor.d$ /usr/bin/totem (totem:14579): GLib-CRITICAL **: g_strsplit: assertion 'string != NULL'

Bug#879900: apparmor-profiles-extra: Totem segfaults when apparmor profile is enforced

Accidentally replied rather than replying all. On Fri, Oct 27, 2017 at 10:30 AM, Jason Wittlin-Cohen < jwittlinco...@gmail.com> wrote: > Thanks for the quick reply! > > Adding #include to /etc/apparmor.d/local/usr.bin.totem > fixed the issue. I am now able to open Totem a

Bug#1019544: Additional Information

As there were several changes in 5.10.140 to the kernel I/O code which could be the cause of my issue, I downloaded the vanilla source code for the 5.10.139 kernel and built it using my Debian kernel config from /boot. I installed the resulting kernel and kernel headers and DKMS built the required

Bug#1019545: closed by Michael Tokarev (Re: Bug#1019545: samba: Permission/ownership issue in /var/lib/samba results in repeated panic or segfault after upgrading from Buster to Bull

2015 through September 13, 2022 -rw-r--r-- 1 root sambashare 104 Jan 17 2015 backups On Thu, Sep 15, 2022 at 10:16 AM Jason Wittlin-Cohen < jwittlinco...@gmail.com> wrote: > > > On Thu, Sep 15, 2022 at 9:58 AM Jason Wittlin-Cohen < > jwittlinco...@gmail.com> wrot

Bug#1019545: closed by Michael Tokarev (Re: Bug#1019545: samba: Permission/ownership issue in /var/lib/samba results in repeated panic or segfault after upgrading from Buster to Bull

-- Forwarded message -- > From: Michael Tokarev > To: Jason Cohen , 1019545-d...@bugs.debian.org > Cc: > Bcc: > Date: Thu, 15 Sep 2022 13:17:28 +0300 > Subject: Re: Bug#1019545: samba: Permission/ownership issue in > /var/lib/samba results in repeated panic or segfault after

Bug#1019545: closed by Michael Tokarev (Re: Bug#1019545: samba: Permission/ownership issue in /var/lib/samba results in repeated panic or segfault after upgrading from Buster to Bull

On Thu, Sep 15, 2022 at 9:58 AM Jason Wittlin-Cohen wrote: > -- Forwarded message -- > >> From: Michael Tokarev >> To: Jason Cohen , 1019545-d...@bugs.debian.org >> Cc: >> Bcc: >> Date: Thu, 15 Sep 2022 13:17:28 +0300 >> Subject: Re