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
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1926658
Title:
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
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
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
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
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1620870
Title:
After updating
I do have it installed.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1620870
Title:
After updating to qtbase-opensource-src 5.6.1+dfsg-3ubuntu3~3, Quassel
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
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
VLC crashes every time you try to start it too.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1620870
Title:
After updating to qtbase-opensource-src
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
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
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,
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
Touch seeded packages, which is subscribed to apt in Ubuntu.
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
Touch seeded packages, which is subscribed to apt in Ubuntu.
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
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
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
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1434020
Title:
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
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
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
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:
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
Touch seeded packages, which is subscribed to systemd in 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
Public bug reported:
After switching to systemd, network-manager often fails to start
properly. Instead of startup up as it should, it seems to get into a
tight loop, burning through about 25% of each thread of my CPU. This
only happens on one of my systems, the one that is equipped with an
This is still happening on Kubuntu 14.10. GTK3 applications like
Synaptic won't scroll unless they are focused.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1240957
Public bug reported:
After upgrading a Kubuntu Trusty x86_64 system to Utopic, VDPAU support
has stopped working in all applications that use libav. In mplayer2, it
prints Cannot find codec 'h264_vdpau' in libavcodec... and in VLC I
get [7f909958] vdpau_avcodec generic error: decoder
This seems to be due to an API change in libav. They dropped the old
API for using VDPAU decoding, which broke every application that uses
VDPAU through libav. https://libav.org/releases/libav-10.5.release
** Also affects: vlc (Ubuntu)
Importance: Undecided
Status: New
** Also
32 matches
Mail list logo
