** Description changed:
In the past weeks we experienced few systems coming up without started
dbus-daemon after reboots due to updates.
The first occurrence happens on January 21th 2021, since this time we
were experiencing 0 up to 2 machines with this issue on each reboot
cycle affe
This affects dbus, but the last change that could probably have caused
this was in systemd.
** Package changed: dbus (Ubuntu) => systemd (Ubuntu)
** Also affects: dbus (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
T
Public bug reported:
In the past weeks we experienced few systems coming up without started
dbus-daemon after reboots due to updates.
The first occurrence happens on January 21th 2021, since this time we
were experiencing 0 up to 2 machines with this issue on each reboot
cycle affecting all (appr
Hi Markus,
this was originally a Bug about SHA-1 signed repositories in local0
breaking the entire installation. The Error messages displayed,
where/are not really good, changing to the shell of the install system,
and having a look at /var/log/syslog there shows more.
This was in 2016 and mainly
Of course only if they're inheriting special repositories this way. But
the bugs referenced here IMHO are showing lot's of examples representing
different reasons and ways to do this. ;-)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subs
Hello again,
I don't really have an opinion if this should be solved by
- changing the priority of gnupg or gnupg2 (if that wasn't only another
unrelated side effect of the change described in Comment #7)
- adding a dependency to gnupg2 | gnupg to apt-setup-udeb if that would be
possible.
Hello,
Bug #1761030 indeed describes the same issues.
I've also a modified udeb in use, now. And it's working for me, but the
setup is almost the same.
d-i apt-setup/local0/source boolean false
d-i apt-setup/local0/key string
http://software.ubuntu.man-da.de/software/key.gpg
d-i apt-setup/local
On Monday, 9 April 2018 12:56:12 CEST Lars Kollstedt wrote:
[...]
> This patch should IMHO work, but I have no opportunity to test it without
> your help, since we're in udeb and testing preseed issues. ;-)
Hi again,
20 times looked at it and still overlooked one detail.
This must o
I'm also trying to assign a useful name to the key added this way.
This patch should IMHO work, but I have no opportunity to test it without your
help, since we're in udeb and testing preseed issues. ;-)
Kind regards,
Lars
--
Lars Kollstedt
Telefon: +49 6151 16-71027
E-Mail: l
In apt-setup-0.104ubuntu5/generators/60local there is an call
$chroot $ROOT apt-key add "/tmp/key$i.pub"
which would be the origin of this message.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gnupg in Ubuntu.
https://bug
Hi again,
switching to installation shell, and doing a
chroot /target
apt install gnupg2
exit
exit
allows me to complete the installation, when continuing with the
installation step preparing installation sources after this.
The /var/log/syslog from the installation system shows the following
m
Hi again,
on March 2nd we were already on 2.2.4-1ubuntu1 so there obviously was
something fixing this. Since the package already wasn't marked as
important this time.
On this time adding the keys still worked fine.
The last days it didn't on bionic.
Kind regards,
Lars
--
You received this b
Hi,
looks like this has happened when changing the source of gnupg to gnupg2
with 2.2.4-1ubuntu1.
The old source
svn://anonscm.debian.org/pkg-gnupg/gnupg/trunk/
contains the Package as important.
The new source
https://anonscm.debian.org/git/pkg-gnupg/gnupg2.git
contains the Package as optional
Didn't want to throw out apt-setup.
** Package changed: gnupg (Ubuntu) => apt-setup (Ubuntu)
** Also affects: gnupg (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gnupg i
apt-key complains about missing necessary gnupg or gnupg2 package.
** Package changed: apt-setup (Ubuntu) => gnupg (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gnupg in Ubuntu.
https://bugs.launchpad.net/bugs/1754
Hello together,
this seems to affect me, too. On Ubuntu 16.4 LTS.
Lots off Syslog lines with:
Feb 2 12:44:01 ws-kollstedt org.kde.KScreen[1925]: kscreen: Primary output
changed from KScreen::Output(Id: 638 , Name: "DVI-I-1" ) ( "DVI-I-1" ) to
KScreen::Output(Id: 638 , Name: "DVI-I-1" ) ( "DVI-
*** This bug is a duplicate of bug 1575572 ***
https://bugs.launchpad.net/bugs/1575572
Send to fast. :-( Tab, Enter wasn't a good idea, in the Bugtrackers
WebGUI. :-( ;-)
The differences between the versions and platforms are probably just
timing. But this happens deterministically on xenial,
*** This bug is a duplicate of bug 1575572 ***
https://bugs.launchpad.net/bugs/1575572
Hi Martin,
the fix for Bug #1575572 released yesterday turns the situation from bad
to worse from my experience. Since I saw this on i686 only before, I am
experiencing this also on amd64 since installing t
18 matches
Mail list logo
