I have this same problem. Take a look at your /boot/grub/grub.cfg.
Notice all of the "/root/boot/*" entries? update-grub (grub-mkconfig) is
picking up an incorrect path.
Workarounds:
1) As root, "cd /root; ln -s ../boot", update-grub/grub-install. Now the
incorrect path in grub.cfg exists and
Package: qmail-run
Version: 2.0.2+nmu1
Severity: important
Dear Maintainer,
ran "apt-get install qmail systemd-runit"
qmail-run was installed
/etc/qmail/qmail-[smtpd|verify|send]/supervise link points to a missing
directory.
/var/lib/supervise is missing.
-- System Information:
Debian Release
Package: fail2ban
Version: 0.9.6-2
Severity: important
Dear Maintainer,
fail2ban 0.9.6 does not work with systemd-journald. See:
https://github.com/fail2ban/fail2ban/issues/1657 (version 0.9.6)
Workaround: Install fail2ban experimental that uses 0.9.7
Steps to reproduce problem with 0.9.6:
log
unsubscribe
On Mon, Aug 15, 2016 at 4:52 PM, Mert Dirik wrote:
> On Fri, 10 Jun 2016 02:02:59 -0400 Michael Gilbert
> wrote:
> > > How about stack traces from a first message? Are they useless?
> >
> > Without debugging symbols, basically yes.
> >
> > > If you want full backtrace from gdb then
I am having the same problem. When I visit
http://www.classicalkusc.org/stream/listen.html and click the Play button
(triangle in the middle) to stream music, chromium crashes with aw, snap.
Version: 51.0.2704.79-1, crashes
Version: chromium_51.0.2704.63-1-deb8u1_i386.deb, works great.
I disable
Yes. I agree that #826782 is a duplicate of #826512.
This exactly fits: https://github.com/systemd/systemd/issues/3332
Please close.
On Wed, Jun 8, 2016 at 6:07 PM, Michael Biebl wrote:
> Am 09.06.2016 um 02:51 schrieb Erik:
> > Package: systemd
> > Version: 230-2
> > Severity: important
> >
>
does not
appear to affect your test.
On Fri, Apr 8, 2016 at 8:52 AM, Yves-Alexis Perez wrote:
> On jeu., 2016-04-07 at 00:58 -0700, Erik Haller wrote:
> > All I can say is that xfce4 was using monitorDVI-0 and then switched to
> > monitor0. I had to move my settings from moni
All I can say is that xfce4 was using monitorDVI-0 and then switched to
monitor0. I had to move my settings from monitorDVI-0 to monitor0.
On Wed, Apr 6, 2016 at 11:10 PM, Yves-Alexis Perez
wrote:
> On mer., 2016-04-06 at 21:33 -0700, Erik Haller wrote:
> > I compiled monitor.c an
e:
> On mer., 2016-04-06 at 13:13 +0200, Yves-Alexis Perez wrote:
> > On mer., 2016-04-06 at 04:04 -0700, Erik Haller wrote:
> > >
> > > I have never seen xrandr use monitor0|1. I am running lightdm.
> > That just means xfdesktop4 didn&
This bug is caused by xfce4. I removed the config files under ~/.config and
the desktop images appeared and the dimming went away. The dimming was
probably caused by a lack of a desktop image on the second monitor.
The missing desktop images was caused by a change in the
/home//.config/xfce4/xfcon
/var/log/apt/history.log packages upgraded:
Start-Date: 2016-03-14 16:03:02
Commandline: apt-get upgrade
Upgrade: xserver-xorg-input-all:i386 (7.7+13, 7.7+14), libmpx0:i386
(5.3.1-10, 5.3.1-11), xserver-xorg:i386 (7.7+13, 7.7+14), libgcc-5-dev:i386
- Does this error happen every time you start ReText? Or only for some
*Yes. Happens everytime. No special documents.*
special documents? (If the latter, can you attach one of them?)
- Did you configure ReText for custom language for spell checking?
*I did not configure any language setting
Applied patch. Same problem. journalctl shows:
retext[4481]: segfault at 0 ip b3d200c5 sp bfa99480 error 4 in
libxcb.so.1.1.0[b3d17000+24000]
On Tue, Oct 6, 2015 at 4:51 AM, Debian Bug Tracking System <
ow...@bugs.debian.org> wrote:
> This is an automatic notification regarding your Bug report
Creating a soft link via ln -s . pkg will not work with some packages; i.e.
godoc net. The godoc command has a problem with the new go 1.4 "range"
syntax. You can fix the go src file by replacing "for range ?" with "for _
:= range ?" in the net package. Use "godoc net |& less" to the line number
t
This is not a bug in the bash-completion package. Please cancel.
The problem is caused by the ksu command in the krb5-user package.
If you become root via "ksu -qe /bin/bash -a -l" and execute "bash
/usr/share/bash-completion/bash_completion", you will see the errors as
reported in this report.
None.
On Wed, Feb 11, 2015 at 11:19 AM, Sam Hartman wrote:
> Do you see any differences in /etc/krb5.conf or /etc/krb5kdc/kdc.conf in
> the successful vs unsuccessful situations?
>
Ben is correct. Installing krb5-{admin-server,kdc} in jessie will install
the database in /var/lib by default when no krb5-user package exists.
However, I was able to reproduce the problem of a database being installed
under /etc/krb5kdc three times in a row when the krb5-user package was
installed
What is telling kadmind to use the /etc/krb5kdc directory? configure
script? Because the /etc/krb5kdc/kdc.conf points -> /var/lib and it
runs just fine with the databases under /etc.
On 2/10/15 12:36 PM, Sam Hartman wrote:
The database (principal and principal.*) live under /var/lib.
The
What conf file is krb5_newrealm using? Message #40 shows it pointing to
/var/lib/
What is the long term goal here? Which files need to reside under
/etc/krb5kdc? Just the principle database, lock file? What about the
kadm5.acl and stash file? Are these variable enough to also reside under
Yes. The default realm is not EXAMPLE.COM.
The krb5_newrealm shows the problem. It's using /etc .
I have the .bash_history as root. I can give you the exact commands used
to installed kdc/krb5-admin-server. But if you run krb5_newrealm on your
server right now, it should reproduce /etc as the
No. I replaced the realm for the report.
On 2/10/15 9:38 AM, Sam Hartman wrote:
Is your realm actually called EXAMPLE.COM?
my guess is that somehow the realm in kdc.conf was incorrect and so that
stanza is not being used.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
w
default_principal_flags = +preauth
}
The /var/lib/krb5kdc directory is empty. The /etc/krb5kdc directory must be
compiled into kadmind as a default because I do not see a conf file that
tells kadmind where to look.
On Mon, Feb 9, 2015 at 10:21 PM, Russ Allbery wrote:
> Erik Haller wri
The database was created fresh with krb5_newrealm in an lxc container. No
Kerberos KDC existed previously. I did not configure the database location
differently. This was my first Kerberos installation.
On Mon, Feb 9, 2015 at 9:52 PM, Russ Allbery wrote:
> Erik Haller writes:
>
> >
e prompted for the database Master Password.
It is important that you NOT FORGET this password.
Enter KDC database master key:
Looks like krb5_newrealm is choosing a default location of /etc/krb5kdc instead
of /var ...
On Mon, Feb 9, 2015 at 9:52 PM, Russ Allbery wrote:
> Erik H
-- Forwarded message --
From: Erik Haller
Date: Mon, Feb 9, 2015 at 9:42 PM
Subject: Re: Bug#777579: krb5-admin-server: kadmind reports Insufficient
access to lock database
To: Russ Allbery
Yes. These files reside under /etc/krb5kdc:
principal
principal.kadm5
principal.kadm5
25 matches
Mail list logo
