Version: 5.0.0-4+deb10u1
I ran into this same issue on a buster system, with additional
buster-backports packages installed. After digging through it appears
that during a recent update the libvirt-daemon-system package was
uninstalled without me noticing. Reinstalling the package also
On 2020-08-05 09:56, Andreas Beckmann wrote:
On 8/5/20 5:30 PM, Joel Johnson wrote:
Thanks, I'll comment out the additional blacklist entries and test
with
that package installed. Those lines aren't harmful in any other way
that
I see, but just unexpected from your original response
On 2020-08-04 15:47, Andreas Beckmann wrote:
On 8/4/20 1:49 AM, Felix Dörre wrote:
I've got a slight clue, what could be wrong here:
The posted update-glx --display glx shows the following line:
[...]
but none libGLX_nvidia.so.0. From the maintainer-script however having
[...]
I hope this
On 2020-08-03 15:13, Andreas Beckmann wrote:
On 8/3/20 5:00 PM, Joel Johnson wrote:
On 2020-07-31 03:03, Andreas Beckmann wrote:
While this additional blacklisting sounds technically correct, I'm
curious why the driver gets loaded automatically in a bumblebee
setup.
$(update-glx --display
On 2020-07-31 03:03, Andreas Beckmann wrote:
On 7/30/20 6:41 PM, Joel Johnson wrote:
With more recent nvidia drivers and Debian packages of
nvidia-kernel-support, the nvidia-modeset and nvidia-drm modules are
attempted to be loaded. This causes the driver to always be loaded.
Locally I've added
Package: bumblebee
Version: 3.2.1-22
Severity: important
With more recent nvidia drivers and Debian packages of
nvidia-kernel-support, the nvidia-modeset and nvidia-drm modules are
attempted to be loaded. This causes the driver to always be loaded.
Locally I've added those two modules to the
c866cc5b105d5bdec3edec500512e7a2ca42e79a Mon Sep 17 00:00:00 2001
From: Joel Johnson
Date: Wed, 19 Feb 2020 18:25:55 -0700
Subject: [PATCH] Build PHY_MVEBU_A38X_COMPHY module
The Device Tree for ClearFog devices was updated to use comphy during
the 5.1 development cycle, merged in a4751093a26c. The new support
Package: src:linux
Version: 5.4.19-1
Severity: important
Recent armmp kernels fail to enable all available ethernet devices using
the mvneta driver. On a ClearFog Base, booting the 4.19 Buster kernels
works as expected, with eth0/eth1/eth2 all being present and available
for use.
However,
To be clean, I'm all for the systemd hardening. I'm just reporting a
case where the current configuration appears to have a gap. I'm in
agreement that the DAC_OVERRIDE may be too big of a hammer, but I wasn't
able to quickly identify another alternative without switching to the
Package: nsd
Version: 4.1.26-1
Severity: important
--- i/debian/nsd.service
+++ w/debian/nsd.service
@@ -8,7 +8,7 @@ Type=notify
Restart=always
ExecStart=/usr/sbin/nsd -d
ExecReload=+/bin/kill -HUP $MAINPID
-CapabilityBoundingSet=CAP_CHOWN CAP_IPC_LOCK CAP_NET_BIND_SERVICE
CAP_SETGID
Package: installation-reports
Boot method: microSD card
Image version:
http://ftp.debian.org/debian/dists/testing/main/installer-armhf/current/images/hd-media/hd-media.tar.gz
Date: 2019-02-22T20:57:53-07:00
Machine: ClearFog Base
Processor: Marvell ARMADA A388 ARM A9
Memory: 1GB
Partitions:
Package: zfs-dkms
Version: 0.7.9-3~bpo9+1
Severity: important
It appears that at least one dependency is missing for zfs-dkms. I
create a new squeeze installation using debootstrap, enabled
squeeze-backports, and performed manual installation of zfs-dkms. The
build failed, giving the
Package: coolkey
Version: 1.1.0-10
Severity: minor
As of version 1.1.0-10, coolkey stopped building the pk11install tool.
It is still referenced in README.Debian.gz and a manpage is still
installed, both of which should be removed.
Joel
Package: qtpass
Version: 1.1.6-1
Tags: security
Severity: important
It is noted in the changelog for version 1.2.1-1, but shouldn't the fix
be applied to the stretch package as well?
Per QtPass upstream (open disclosure), passwords generated from within
the application are insecure due to
=7198a6d4e74f684cb383b3e0f70dd2bae405e6e7
https://cgit.freedesktop.org/xorg/xserver/commit/?id=cfddd919cce4178baba07959e5e862d02e166522
https://cgit.freedesktop.org/xorg/xserver/commit/?id=3eb964e25243056dd998f52d3b00171b71c89189
Thanks,
Joel Johnson
Source: cryptsetup
Severity: minor
I tried to do a quick rebuild of the source package for a wheezy
backport locally, and all build-depends installed, however only during
the build execution did I receive the following message about automake
version requirements. Using automake 1.14.1 from
Package: r8168-dkms
Version: 8.037.00-1
I have a desktop machine to which I just added a second NIC. One
(correctly) uses the r8169 driver, while the new one (StarTech miniPCI-E
adapter) is an r8168 that doesn't work correctly with the r8169 driver.
I'll be filing the requests/bugs on the
More information on the davical mailing list, including the reference
to the section in the release notes where this is explicitly mentioned.
http://lists.davical.org/pipermail/davical-users/2013q1/004435.html
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a
For the reference of others, once I did the following, it is all
working correctly for me. It took a couple more hours to find the other
language references that get included in the update-davical-database
script since it didn't report any errors and gave the impression that
everything was
Package: davical
Version: 1.1.1-1
Severity: important
Tags: upstream
I'm running this machine with the pgdg postgres packages and am using pg 9.2.
When running the create-database.sh script, I get the errors listed below. The
first time through
I continued and it appeared to work until I tried
Package: rsync
Version: 3.0.9-3
Severity: normal
Tags: upstream
I've recently upgraded my backup host from squeeze to wheezy and am
being bit by an issue in rsync handling the replacement of directories
with symlinks.
I use rsync via rsnapshot to build backup snapshots over time using
Version: 3.0.7-2
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Package: cherokee
Version: 1.2.100-1
Severity: normal
The cherokee included logrotate file (/etc/logrotate.d/cherokee) uses the
'killall' command
to reload the worker process. There is no direct or inherited dependency on the
psmisc
package which contains the command, so when running on a
I believe that the delay and the fd0 read error are two separate issues
occurring together.
I have the same issue with the fd0 read error, however on this machine
it doesn't cause any additional delay, in fact I had to reboot four
times to get all parts of the message. I have other machines
In searching, it looks like bug 549905 may be the same issue, just
actual seeks occur on machines with floppies and the fd0 seek/read error
message is shown on those without, but still having controllers enabled.
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=549905
--
To UNSUBSCRIBE,
Package: krb5-kdc
Version: 1.8.1+dfsg-1
Severity: serious
I have a Sheevaplug (armv5tel) to which I am migrating Kerberos services.
I've imported an existing database and listing principals with kadmin
works, ticket issuing works, kpasswd works. However, when doing a ticket
renewal with `kinit
On Sun, 11 Apr 2010 22:42:16 -0700, Russ Allbery r...@debian.org wrote:
Joel Johnson mrj...@lixil.net writes:
I have a Sheevaplug (armv5tel) to which I am migrating Kerberos
services. I've imported an existing database and listing principals
with kadmin works, ticket issuing works, kpasswd
On Sun, 11 Apr 2010 23:48:51 -0600, Joel Johnson mrj...@lixil.net wrote:
Yeah, it's getting late - here's the actually useful bt output:
(gdb) continue
Continuing.
Program received signal SIGSEGV, Segmentation fault.
0x4023ebac in free () from /lib/libc.so.6
(gdb) bt
#0 0x4023ebac
On Fri, 27 Nov 2009 22:47:07 +0100, Jordi Mallach jo...@debian.org
wrote:
Hi Joel,
Have you seen this nano bug in the recent versions 2.0.x or even in the
soon to be stable 2.1.99pre2?
If not, I'll just close this bug, with apologies for not having
contacted
you in years. :/
Jordi
--
On Wed, 29 Jul 2009 15:27:19 +0200, Sandro Tosi sandro.t...@register.it
wrote:
Sandro Tosi wrote:
Package: dovecot-imapd
Version: 1:1.1.13-2~bpo50+1
Severity: important
Hi Timo,
I'd like to present to you the problem below we are facing with 1.1.13
version of Dovecot (the version available
dovecot currently defaults with: mbox_write_locks = dotlock fcntl
according to policy 11.6 though:
All Debian MUAs, MTAs, MDAs and other mailbox accessing programs (such
as
IMAP daemons) must lock the mailbox in an NFS-safe way. This means that
fcntl() locking must be combined with dot
Debian bug report
(http://bugs.debian.org/537379) regarding the headers used for address
matching. I'm fairly sure this fix amounts to the below patch, but would
like to confirm and get the patch included upstream first.
Thanks,
Joel Johnson
static const char * const _allowed_headers[] = {
/* Required
On Sat, 18 Jul 2009 03:03:16 +0930, Ron r...@debian.org wrote:
The other thing that broke in my previous sieve script when updating
from cmu to the dovecot sieve is this rule:
if envelope :detail To [virus, banned] {
fileinto virus;
stop;
}
I don't really understand why
The default for the debian package is to use syslog and not a separate
file. In this configuration, log rotations are done by the daily syslog
cron job.
However, the administrator can certainly configure logging to a file
instead, but if you consult the dovecot documentation/wiki on how to setup
Package: openldap2.3
Version: 2.4.7-4
The build-depends for the openldap2.3 source package call out libgnutls-dev,
but it appears to need a versioned depends. When trying to do an etch
backport of slapd 2.4.7, the compilation fails with unknown gnutls
references (etch version is 1.4.4 vs 2.2.1 in
On Wed, April 25, 2007 3:45 am, Modestas Vainius wrote:
Hello,
Would you like to hand over ktorrent maintainance to the Debian KDE extras
team? You could join the team and continue maintainance inside the team.
This
will guarantee faster releases to debian users and quick sponsorship of new
Giuseppe Bilotta wrote:
Latest upstream release is 2.1.2 ... any chances of the Debian package
being updated?
Shortly after the full release of Etch I'll release an updated package.
It is frozen along with the rest of Etch, and I haven't gotten around to
an experimental release.
--
To
onto the blank line above triggers this.
The error printed on VC1 after the crash is
(partially): gtk_text_view_start_selection_drag: assertion failed: text
view - selection_drag_handler == 0
Joel Johnson
I tried to reproduce the drag crash, but could not drag anything
anywhere: could you
is
(partially): gtk_text_view_start_selection_drag: assertion failed: text
view - selection_drag_handler == 0
Joel Johnson
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Continue
* on screen to select volume select any of them, click Go Back
* The selected volume is still deleted
Thanks,
Joel Johnson
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
I also have the same issue (reported at
http://lists.debian.org/debian-boot/2006/08/msg00230.html). Using a
hard-wired mouse is a *temporary* solution, but is not satisfactory for a
release.
Joel
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact
On Thu, June 8, 2006 11:45 am, freeze wrote:
Ktorrent crashes on start-up with the message
listed below.
SNIP
Is this on a new install or upgrade from 1.1? Does it still crash if you
move .kde/share/apps/ktorrent and .kde/share/config/ktorrent out of the
way?
On Saturday 27 May 2006 06:06, Martin Michlmayr wrote:
Can you please upload the new upstream release?
Will do within the week, when is the target date for the GCC 4.1 transition?
As an aside, thanks for your work building everything against 4.1 preemptively
as opposed to switching GCC in
Package: libsmbios
Version: 0.10.6-2
Severity: wishlist
Upstream version has significant changes, and is at version 0.11.3,
available at http://linux.dell.com/libsmbios/download/LATEST_STABLE/ (for
others interested, presumably the maintainer knows that).
Joel Johnson
Package: initscripts
Version: 2.86.ds1-6
Severity: minor
/etc/init.d/checkroot.sh -
The script checks where the swap is located to know how/if to enable it.
However, I have my swap located on an LVM volume, and the dm_mod isn't
loaded until later (libdevmapper1.02) so attempting to activate the
Package: ktorrent
Severity: important
I can't open file or change preferences because it locks itself.
Can you please provide more information about the problem:
Does the program appear to load properly - can you use the menus, get the file
open dialog, etc?
When you say it locks itself,
was unable to find anything. Originally I
thought it occured only on amd64, but I have also seen it on x86. Both
architectures I have used 2.6.8 and 2.6.11 (debian packaged versions).
Joel Johnson
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL
on /boot. I
found it interesting that (ext2, ext2) worked, while (ext3, ext3) did
not. I also tried combinations of reiser and ext2 to no avail.
Any ideas what could be the cause of the grub installation failures?
Thanks,
Joel Johnson
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED
Package: pathological
Version: 1.1.3-5
Severity: important
The latest patch introduced in the -5 package breaks navigating the main menu
with the mouse. When clicking on menu entries (instead of keyboard navigation,
which works as expected) the option is properly toggled, then the game is
Package: enigma
Version: 0.81.1-2
Severity: wishlist
New upstream release (much improved) of version 0.91.
-- System Information:
Debian Release: 3.1
APT prefers testing
APT policy: (500, 'testing'), (80, 'unstable'), (50, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.11-1-k7
50 matches
Mail list logo
