Public bug reported:
After intel-graphics-compiler was updated to 1.0.8744-2, intel-opencl-
icd is no longer installable due to the following errors:
libigc1 : Breaks: intel-opencl-icd (< 21.32.20609-2~) but 21.32.20609-1 is to
be installed
libigdfcl1 : Breaks: intel-opencl-icd (<
I've been running this since it was first uploaded to the staging PPA
without any problems.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1943376
Title:
[FFe] KDE Frameworks 5.86.0 into Impish
Public bug reported:
The Impish build of Firefox 89 beta in the PPA seems to be built without
Wayland support. This of course causes it to work only in XWayland mode
when running in Wayland, but also breaks VAAPI in both environments due
to "DMABUF unavailable by default: Wayland support
Fixed in 0.140ubuntu2.
** Changed in: initramfs-tools (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926658
Title:
initramfs-tools 0.140ubuntu1 causes
Public bug reported:
After updating the initramfs-tools 0.140ubuntu1, the system no longer
boots. Instead, the busybox shell is started. The error says that
"/init" cannot be started due to error -13.
In investigated and figured out that the error occurs because the
I have also installed the packages from the staging PPA without any
issues.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1895187
Title:
[FFe] KDE Frameworks 5.740 into Groovy archive
To manage
Public bug reported:
It depends on lib32gcc1, which would also be compiled from gcc-10, but
no longer is as of 10-20200502-1ubuntu1. This causes anything
transitively dependent on lib32stdc++6 to be uninstallable, which makes
a great many things (at least anything dependent on libclang-X-dev) to
I have been running these on several systems since Rik initially put
them in the staging PPA and I haven't had any issues.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1869079
Title:
[FFe] KDE
It looks like the VAAPI version is gone from the snap store again. Is
there some reason why this hasn't been merged yet as mentioned in #96?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1424201
I've been running this on several computers for daily use ever since Rik
uploaded it and haven't had any issues.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1843866
Title:
[FFe] KDE Frameworks
It seems to be caused by the latest release, 7.3.1-2, and its change in
how icu is detected. Reverting both that change and the change in icu
to not ship icu-config and rebuilding makes the issue go away again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Public bug reported:
When PHP starts, I get:
PHP Warning: PHP Startup: Unable to load dynamic library 'intl.so'
(tried: /usr/lib/php/20180731/intl.so (/usr/lib/php/20180731/intl.so:
undefined symbol: spoofchecker_register_constants),
/usr/lib/php/20180731/intl.so.so
I have been using this since it was staged several days ago and haven't
had any problems. I believe that some combination of this and VLC 3.0.4
even fixed a previous issue I had been seeing where applications would
hang while playing notification sounds through Phonon.
--
You received this bug
Public bug reported:
After upgrading to uriparser 0.8.5, attempting to link an executable
with it using "-luriparser" fails with "/usr/bin/ld: cannot find
-luriparser". Downgrading back to 0.8.4 makes it work again. For an
example of a build that failed for this reason, see
I see the same issue on my Skylake desktop (sig=0x506e3). The microcode
updates at startup (microcode: microcode updated early to revision 0xc2,
date = 2017-11-16) but I still get "Intel Spectre v2 broken microcode
detected; disabling Speculation Control". I also tested it on Ivy
Bridge,
I have been running this since Rik packaged it and I haven't had any
problem either.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1754825
Title:
[FFe] KDE Frameworks 5.44.0 into the Bionic Archive
Public bug reported:
Version 1:11.1-1ubuntu3 added 0030-load-module-switch-on-connect.patch,
which changes line 38 of /etc/pulse/default.pa to read ".endif### Load
audio drivers statically". It appears that there are a couple of line
feeds missing here, and having the comment on the same line as
I've been running this since it was staged a few weeks ago and haven't
had any issues.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1716381
Title:
[FFe] KDE Frameworks 5.38.0 into the Artful
** Tags removed: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1675830
Title:
nvidia 304 graphics causes Login loop in Ubuntu Budgie
To manage notifications about this bug go to:
Confirmed; after the update to Maven 3.5, everything builds correctly
again. Thanks!
** Changed in: wagon2 (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
After I upgraded to libwagon2-java 2.12 on Artful, I get the following
error and stacktrace when trying to build any project in Maven
(installed using apt):
[WARNING] Error injecting:
org.apache.maven.wagon.providers.http.HttpWagon$__sisu1
java.lang.NoClassDefFoundError:
That works, thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1654453
Title:
LMTP delivery to Dovecot stops working in 3.1.4-1
To manage notifications about this bug go to:
Sure, but it appears to be FTBFS at the moment.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1654453
Title:
LMTP delivery to Dovecot stops working in 3.1.4-1
To manage notifications about this
Here is the master.cf file.
** Attachment added: "master.cf"
https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1654453/+attachment/4801261/+files/master.cf
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Here is the relevant section of term.log. It does say that it is
removing the symlink and updating the configuration.
** Attachment added: "term.log"
https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1654453/+attachment/4801260/+files/term.log
--
You received this bug notification
I just upgraded and still have exactly the same problem as before.
** Changed in: postfix (Ubuntu)
Status: Fix Committed => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1654453
No, there is no trailing whitespace on any of the lines related to lmtp
in either of my configuration files.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1654453
Title:
LMTP delivery to Dovecot
I don't have anything about dovecot-lmtp in master.cf. The only
uncommented line I have about lmtp in master.cf is "lmtp unix -
- n - - lmtp". In main.cf, I have
"mailbox_transport = lmtp:unix:/var/spool/postfix/private/dovecot-lmtp".
--
You received this bug
Public bug reported:
After installing Postfix 3.1.4, email delivery to Dovecot stops working.
In the Postfix log, I get:
Jan 5 19:50:45 michaelmarley postfix/smtpd[30558]: connect from
[]
Jan 5 19:50:45 michaelmarley postfix/smtpd[30558]: B3A2C1801FA:
client=[]
Jan 5 19:50:45 michaelmarley
michael@mamarley-desktop:~$ DISPLAY=:0 xdpyinfo | grep dimensions
dimensions:7680x2160 pixels (1060x301 millimeters)
michael@mamarley-desktop:~$ DISPLAY=:0 xdpyinfo | grep resolution
resolution:184x182 dots per inch
michael@mamarley-desktop:~$
I should also mention that this bug now
Public bug reported:
The first installation of the nginx-common on a system without nginx
installed works fine, but attempting to reinstall it (or upgrade from a
previous version of nginx-common) results in the post-install script
exiting with status 1. I attempted to debug this issue myself,
Public bug reported:
The title says it all.
** Affects: lirc (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1636355
Title:
In lirc 0.9.4,
Public bug reported:
Either the file needs to be moved to /usr/sbin/ or the
/lib/systemd/system/irexec.service needs to be updated to point to
/usr/bin/irexec instead.
** Affects: lirc (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you
Yes, what you did with lxc seems to be reproducing the same issue I am
seeing.
I am running Yakkety, but I actually did try backporting the package to
Xenial and saw the same issue there too.
The script that copies the /etc/resolv.conf (and other files) into the
chroot is
Public bug reported:
This occurs because /etc/resolv.conf gets copied to
/var/spool/postfix/resolv.conf before the network is up and therefore
before it contains any useful data. Therefore, every message fails to
be sent or received with a message such as "dsn=4.4.3, status=deferred
(Host or
I have been using these packages (minus PIM and Telepathy, neither of
which I use) since they were staged and haven't had any issues.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1625756
Title:
I too have been running several computers with these packages since they
were staged and also haven't had any problems.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1625392
Title:
[FFe] KDE
Thanks, with this version of plasma-integration Quassel and VLC do not
crash.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1620870
Title:
After updating to qtbase-opensource-src
I do have it installed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1620870
Title:
After updating to qtbase-opensource-src 5.6.1+dfsg-3ubuntu3~3, Quassel
crashes every time on start
To manage
That environment variable is empty. I did upgrade appmenu-qt5; the
installed version is 0.3.0+16.10.20160628.1-0ubuntu2~2.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1620870
Title:
After
VLC crashes every time you try to start it too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1620870
Title:
After updating to qtbase-opensource-src 5.6.1+dfsg-3ubuntu3~3, Quassel
crashes every
Specifically, the "libqt5widgets5" package seems to be at fault. If I
revert only this package to the previous version Quassel works properly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1620870
Public bug reported:
Reverting to the previous version fixes the problem. Here is the
stacktrace from the crash:
#0 0x in ?? ()
#1 0x73896c5e in copyActionToPlatformItem
(action=action@entry=0x55d65820,
item=item@entry=0x55e24380,
Public bug reported:
This causes postgrey to fail to start on installation:
Setting up postgrey (1.36-1) ...
Job for postgrey.service failed because the control process exited with error
code.
See "systemctl status postgrey.service" and "journalctl -xe" for details.
invoke-rc.d: initscript
Public bug reported:
There is a bug in the CMake configuration for Quassel 0.12.4 that causes
it to fail to enable SSL support during the build with compiled with
Qt5.6 and GCC5. The most recent build of Quassel is now compiled
against Qt5.6 and therefore triggers the bug. The bug is fixed in
I don't see any reason not to do that, but I am not really the decider
of such things. It looks like the only difference is that the Ubuntu
package puts the user in the Kubuntu IRC channel by default. I will ask
the people from #kubuntu-devel to comment.
--
You received this bug notification
Public bug reported:
In that config version, all of the CONFIG_CPU_FREQ_GOV_* drivers except
PERFORMANCE were switch from "y" to "m". Because of this, none of the
drivers other than PERFORMANCE are loaded and the CPU remains at full
speed all the time.
The results of this can be seen in the
For anyone encountering this bug, a workaround to allow the removal of
the broken package is to first stop your X display manager, then use
remove the packages manually on the command line, and finally reboot.
This will switch you back to Nouveau but at least give you a working
system from which
Public bug reported:
Quassel should be updated to 0.12.4 to fix several bugs, including a
core-crashing bug (fixed in
https://github.com/quassel/quassel/commit/adbd7f6efa14b107ed722daa0b7963dd1238a681).
I have prepared a package for Yakkety in
Public bug reported:
When CONFIG_GOLDFISH_BUS is set to "y", the goldfish_pdev_bus driver is
compiled into the kernel and claims the serial UART, breaking serial
communications with the following kernel message: "genirq: Flags
mismatch irq 4. (serial) vs. 0080 (goldfish_pdev_bus)"
Sorry, I don't use Wily anymore.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1559468
Title:
Missing single-quote in watchdog.service prevents service from working
correctly
To manage
I can confirm that thew newly-uploaded version in Xenial works properly,
thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1559468
Title:
Missing single-quote in watchdog.service prevents
** Patch added: "mysql57fix.debdiff"
https://bugs.launchpad.net/ubuntu/+source/amarok/+bug/1571215/+attachment/4638418/+files/mysql57fix.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: amarok (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1571215
Title:
Amarok uses mysql config option that is removed in 5.7
To manage
** Changed in: amarok (Ubuntu)
Status: New => Confirmed
** Changed in: amarok (Ubuntu)
Assignee: (unassigned) => Michael Marley (mamarley)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
Public bug reported:
The ExecStartPre command should have a single-quote at the end to close
the opening single-quote, but it does not. This patch fixes the
problem.
** Affects: watchdog (Ubuntu)
Importance: Undecided
Status: New
** Patch added: "singlequote.debdiff"
Public bug reported:
On my Thinkpad T530 laptop, if I install and enable the watchdog service
with the iTCO_wdt watchdog device, suspend stops working correctly. It
always works correctly the first time, but if I try 2 or 3 times, it
often locks up and fails to go into suspend on the second or
I know that the PPAs need new keys, but it is not obvious how to do
that. After extensive searching, I still cannot figure out how to do
that.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1558331
Hmm, it looks like the combination of the warnings and errors may be
especially confusing. I have several PPAs and the Google Chrome
repository on my system. The PPAs have the packages themselves signed
with SHA256, but the GPG key is only SHA1. These repositories should
work, but display an
Public bug reported:
The title pretty much says it all.
** Affects: apt (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1558331
Title:
After
Public bug reported:
If I install Postfix 3.0.3-1~build1 on a system that has never had
Postfix installed before, it fails to start with the following error:
"fatal: instance /etc/postfix, shlib_directory=/usr/lib/postfix
conflicts with instance /etc/postfix, daemon_directory=/usr/lib/postfix"
Public bug reported:
If I install Postfix 3.0.3-1~build1 on a system that has never had
Postfix installed before, it fails to start with the following error:
"fatal: instance /etc/postfix, shlib_directory=/usr/lib/postfix
conflicts with instance /etc/postfix, daemon_directory=/usr/lib/postfix"
Public bug reported:
I recently upgraded my Kubuntu x86_64 system with a HiDPI monitor (24"
4K) from Wily to Xenial. Before I did this, applications using all the
toolkits (GTK2, GTK3, Qt4, and Qt5) properly obeyed the DPI value
automatically detected from the monitor, causing them to
This was fixed in icedtea-web 1.6.1-3ubuntu1.
** Changed in: icedtea-web (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1538258
Title:
Installation of
Public bug reported:
When attempting to install icedtea-8-plugin on a Xenial x86_64 system, I
get the following error:
update-alternatives: error: alternative path //jre/lib/amd64/IcedTeaPlugin.so
doesn't exist
dpkg: error processing package icedtea-8-plugin:amd64 (--install):
subprocess
Public bug reported:
The /usr/share/sddm/scripts/Xsetup file is automatically and silently
overwritten when sddm is updated, removing any modifications the user
may have made to the file. This is a pain because it requires the file
to be re-edited after every update if the user needs to launch
Public bug reported:
phonon-backend-vlc depends on "vlc-plugin-pulse", but that is a
transitional dummy package and the functionality it provides is now in
the main "vlc" package. Therefore, depending on "vlc" only is adequate.
** Affects: phonon-backend-vlc (Ubuntu)
Importance: Undecided
When 16.04 gets Qt 5.5, this is about to get a lot worse. Qt 5.5
apparently (I tested https://launchpad.net/~ci-train-ppa-
service/+archive/ubuntu/landing-012) handles the monitor hotplugging
differently and it causes kdeinit5 to crash (dumping me back to sddm)
*every time* I move the mouse to
Sorry, I forgot to mention, I have a setup very similar to ~krose with
an Nvidia card and two Dell 4K monitors connected by DisplayPort.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1492778
Title:
Any chance of getting this one in too?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1494076
Title:
[Feature] Please backport mei support for Sunrise Point
To manage notifications about this bug
This was fixed in 4.2.0-11.13, thanks!
https://launchpad.net/ubuntu/+source/linux/4.2.0-11.13
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
It might also be a good idea to include
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/cpufreq/intel_pstate.c?id=ba88d4338f226766f510e207911dde8c1875e072
since that patch fixes enabling HWP for non-boot CPUs and Skylake uses
HWP.
--
You received this bug
Public bug reported:
Support for the Skylake H/S processors (0x5e) has been added to linux
4.3, but it would be nice if this could be backported to Wily as well.
The upstream patch is
Public bug reported:
Support for the Skylake H/S processors (0x5e) has been added to linux
4.3, but it would be nice if this could be backported to Wily as well.
The upstream patch is
This is a feature request, so logs are not applicable.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1494073
Title:
[Feature]
This is a feature request, so logs are not applicable.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1494074
Title:
[Feature]
Public bug reported:
Support for the Sunrise Point PCH has been added to the mei driver for
linux 4.3, but it would be nice if this could be backported to Wily as
well.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1494076
Title:
[Feature] Please backport mei support for Sunrise Point
To manage
Public bug reported:
As described in the upstream bug report
https://bugzilla.redhat.com/show_bug.cgi?id=1207730, network-manager can
cause a continuous IPv6 router solicitation loop. In my specific case,
a large number of computers running network-manager are on the network.
The resulting storm
While having a 4096-bit certificate is not necessary in order to be
secure, its only disadvantages are taking longer to generate (which I
don't think is much of an issue because it doesn't get regenerated very
often) and taking slightly longer for the handshake (which is
practically negligible on
OK, here is a patch for 2048-bit certificates. I also discovered that
OpenSSL generates the SHA256 hash automatically now, so there is no need
to specify that explicitly.
** Patch added: certificate.debdiff
Public bug reported:
After installation, quassel-core generates a 1024-bit certificate using
the SHA1 hash. Both of these are considered deprecated and somewhat
insecure. The attached patch updates the postinst script to generate a
4096-bit certificate using the SHA256 hash instead.
The SHA256
Hmm, it seems to not be doing it anymore. I guess an update sometime
between when I filed the bug and now fixed the problem. (I had
NetworkManager-wait-online disabled since I don't need its
functionality, so I wouldn't have noticed.) Sorry for the trouble.
** Changed in: systemd (Ubuntu)
219-4ubuntu7 fixes the problem. Thanks!
** Changed in: systemd (Ubuntu)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1434020
Title:
With systemd 219-4ubuntu6,
Public bug reported:
After updating to systemd 219-4ubuntu6, the ifup services for both
network cards in my system fail to start with /sbin/ifup: failed to
open lockfile /run/network/.ifstate.lock: No such file or directory.
My networks still come up because I am using network-manager, but
The problem seems to be that ifup@.service currently isn't sequenced to
run after systemd-tmpfiles-setup.service (both of those are configured
to run after local-fs.target). If I override ifup@.service and set
After=local-fs.target network-pre.target systemd-tmpfiles-
setup.service, it starts
Ah, OK, I hadn't read that. Makes sense, here is another debdiff that
only has the PostgreSQL and Restart=on-failure changes. Quassel doesn't
support MySQL, so I don't think adding mysql.service is necessary.
** Patch added: init.debdiff
Oops, I hadn't read that either. Sorry for the trouble.
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to quassel in Ubuntu.
https://bugs.launchpad.net/bugs/1432161
Title:
quasselcore.service systemd unit does not depend on PostgreSQL,
After further reading and experimentation, it seems that the ExecStart=
directive cannot be overridden because the contents of the override file
are appended to the contents of the main unit file. This results in two
ExecStart= directives being present, which is illegal and prevents
systemd from
Here is a new patch that fixes a couple more issues I found.
First, the systemd unit file did not have Restart=on-failure, which
differed from the behavior of the upstart script.
Second, neither the systemd unit file nor the upstart script had support
for the DAEMON_OPTS variable from
Public bug reported:
quasselcore's current systemd unit file does not have Wants or After
entries for PostgreSQL, so Quassel will usually/always be started before
PostgreSQL is running. If the core is configured to use PostgreSQL for
storage, this causes the core to fail to start.
I have
Public bug reported:
The enablement of NetworkManager-wait-online.service in network-manager
0.9.10.0-4ubuntu10 has made my Kubuntu Vivid x64 system take nearly
twice as long to boot to the login screen. I did some investigating and
determined that this is because sddm.service depends on
The directory is indeed missing. If I run the journalctl command, it
just says No journal files were found. (No, I haven't modified the
logging configuration.) Running the systemd-tmpfiles command does
create that directory. I have attached the output.
** Attachment added:
Interesting, I tried running the journalctl command again and now it
works. Here is the output.
** Attachment added: journalctl.log
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1431110/+attachment/4342526/+files/journalctl.log
--
You received this bug notification because you are
Yes, both of those things are true. I have attached the output of
journalctl -ab. This particular startup also triggered the network-
manager-related bug that I reported, and I had to manually run the
systemd-tmpfiles command you posted over there to actually get the
system to finish booting to
Sure, it says:
Requires=basic.target
Wants=system.slice
Before=multi-user.target shutdown.target graphical.target checkfs.service
local-fs.target
After=system.slice basic.target cryptdisks-early.service mdadm-raid.service
systemd-udevd.service mountdevsubfs.service systemd-journald.socket
OK, here it is:
michael@mamarley-laptop:~$ cat /etc/init.d/lvm2
#!/bin/sh
### BEGIN INIT INFO
# Provides: lvm2 lvm
# Required-Start:mountdevsubfs
# Required-Stop:
# Should-Start: udev mdadm-raid cryptdisks-early multipath-tools-boot
# Should-Stop: umountroot mdadm-raid
#
Yeah, for some reason my system has them in in *all* the rcX.d
directories. rc2-rc5 all have start scripts (S05lvm2) and the others
have kill scripts, except for rcS.d, which actually has nothing. I
guess I should delete all of them and add one in rcS.d? Should the one
in rcS.d be a start or
That seems to make everything work OK on bootup. Thanks!
I have no idea how those symlinks got there. I definitely didn't put
them there manually.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
After switching to systemd, the AppArmor service often fails to start on
boot. This seems to happen at least 50% of the times I turn on the
system. If I attempt to start the process again after the system is
otherwise finished booting, it works fine. I also have another
1 - 100 of 797 matches
Mail list logo
