fix cherry-picked into Debian, will be synced into utopic ASAP.
** Changed in: systemd-shim (Ubuntu)
Status: Confirmed = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd-shim in Ubuntu.
Note that these fixes need to get into the Ubuntu RTM distro as well.
cgmanager 0.30-1ubuntu1 is already there (https://launchpad.net/ubuntu-
rtm/+source/cgmanager), but upstart is currently at version
1.13.1-0ubuntu3 vs. 1.13.2-0ubuntu1 in utopic.
James, please get the necessary changes landed
** Package changed: linux (Ubuntu) = rsyslog (Ubuntu)
** Changed in: rsyslog (Ubuntu)
Status: Incomplete = New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
https://bugs.launchpad.net/bugs/1366829
I know that the patch for this is not finalized (ongoing discussion with
upstream regarding the proper way to implement it), but I'm going to
sign off on this FFe on the grounds that this is a discrete new dbus
interface that will not impact the rest of the existing code.
(BTW, please avoid
cgmanager also approved as part of this.
** Changed in: cgmanager (Ubuntu)
Status: New = Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd-shim in Ubuntu.
https://bugs.launchpad.net/bugs/1355966
Title:
Yes, closing.
** Changed in: upstart (Ubuntu RTM)
Status: Triaged = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd-shim in Ubuntu.
https://bugs.launchpad.net/bugs/1357252
Title:
upstart can
The verification of the Stable Release Update for gccgo-4.9 has
completed successfully and the package has now been released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
The verification of the Stable Release Update for gccgo-4.9 has
completed successfully and the package has now been released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
The verification of the Stable Release Update for gccgo-4.9 has
completed successfully and the package has now been released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
Public bug reported:
The ubuntu-html5-container package has a dependency on dpkg-dev. But
the only references anywhere to dpkg-dev in the ubuntu-html5-theme
source are in
./tests/autopilot/ubuntu_html5_ui_toolkit/tests/__init__.py, installed
in the ubuntu-html5-ui-toolkit-autopilot package.
The
@ Robert
hm, digging a bit more, lightdm semms the real package to be blamed:
oem@u64:~$ grep kwallet /etc/pam.d/*
/etc/pam.d/lightdm:auth optional pam_kwallet.so
/etc/pam.d/lightdm:session optional pam_kwallet.so auto_start
/etc/pam.d/lightdm-greeter:auth optional pam_kwallet.so
insserv: warning: script 'S99autotest' missing LSB tags and overrides
insserv: warning: script 'autotest' missing LSB tags and overrides
This is not a bug in dbus. The dbus package is merely calling update-
rc.d, which calls into insserv, which expects to be able to order the
init scripts on
Public bug reported:
Something has regressed to cause my laptop to not resume from suspend.
But in addition, this has exposed a bug in apportcheckresume, which is
reporting the resume failure twice in a row.
$ ls -l /var/crash/susres.2014-09-22_15\:00\:53.7*.crash
-rw-r- 1 root whoopsie
** Changed in: system-image (Ubuntu)
Assignee: (unassigned) = James Hunt (jamesodhunt)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to system-image in Ubuntu.
https://bugs.launchpad.net/bugs/1372937
Title:
no ssh host
This probably needs to be moved to a different package than system-
image, which is the package for the atomic updating tools; but I'm not
sure if we know what package this will be on, as I'm not sure the
package to handle the system-image boot-time setup exists yet. (Will be
based on
The verification of the Stable Release Update for xorg-lts-transitional
has completed successfully and the package has now been released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that
Dann, what upstart services fail to be shut down? The last messages
shown in your log are from /etc/init.d/sendsigs and /etc/init.d/reboot,
which on an upstart system are only ever called via /etc/init/rc.conf,
systemd notwithstanding.
** Changed in: systemd (Ubuntu)
Status: New =
to verify that the udev events are what
we expect.
It might also be helpful to locally divert /sbin/reboot with a wrapper
that records the args, and the details about the calling process, for
later analysis.
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) = Steve Langasek (vorlon)
--
You
Public bug reported:
Currently, the top crasher reported on arm for the phones is in url-
dispatcher:
https://errors.ubuntu.com/problem/e17057d970fd4d64e71eb28c6f18b8a6468df471
This is a recoverable error, reported by url-dispatcher's explicit
recoverable problem handling.
The problem is, a
Any further detail I can add here to move this along?
Well, if you expect any movement you will certainly need to provide more
detail, because this is working as expected here.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
On Fri, Aug 01, 2014 at 02:13:18PM -, Dimitri John Ledkov wrote:
At the moment we'd want to support for people to install systemd-sysv,
and easily revert back to upstart.
Ideally, systemd-sysv would not conflict with upstart, instead it would
dpkg divert /sbin/init to /sbin/init.upstart
Note, in particular, that 'thread apply all bt' also returns results in
this environment. So whatever thread support gdb gets from
libthread_db, it doesn't appear to be required for analysis of foreign-
architecture crashes.
--
You received this bug notification because you are a member of
In spite of the warnings about libthread_db, I can't see that this is
actually causing any problems. Retracing here gives me:
vorlon@virgil:/tmp$ schroot -c precise
(precise)vorlon@virgil:/tmp$ sudo apt-get install apport-retrace
[...]
(precise)vorlon@virgil:/tmp$ sudo add-apt-repository
Yes, per IRC, this is more or less the expected behavior of both systemd
(logind) and upstart (poweroff). It's only the emergent behavior
combined with a buggy kernel/hardware button behavior that's surprising.
As noted on IRC, there are three possible solutions:
1) get the kernel fixed to not
** Changed in: autopilot (Ubuntu)
Status: Confirmed = Fix Released
** Changed in: autopilot-qt (Ubuntu)
Status: Confirmed = Fix Released
** Changed in: mir (Ubuntu)
Status: Confirmed = Fix Released
** Changed in: window-mocker (Ubuntu)
Status: Confirmed = Fix
This error message indicates that you have a non-default filesystem on
/mnt that's in a problematic state. The base-files package provides the
/mnt directory on the filesystem, so dpkg assumes it should be able to
unpack that directory if necessary. I think you will need to unmount
/mnt on your
This was probably an upgrade issue at the time. It is certainly not
reproducible now. Was logind being correctly restarted on package
upgrade?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Hello Manoj, or anyone else affected,
Accepted systemd into trusty-proposed. The package will build now and be
available at http://launchpad.net/ubuntu/+source/systemd/204-5ubuntu20.4
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Public bug reported:
Currently, the way whoopsie-upload-all works is that, whenever a new
.crash file is seen, /etc/init/apport-noui.conf triggers to run
whoopsie-upload-all from a single-threaded job that iterates through all
as-yet-unprocessed .crash files, process them via apport, marks them
This is a bug in the /etc/pam.d/login configuration, which has:
sessionoptional pam_motd.so motd=/run/motd.dynamic noupdate
sessionoptional pam_motd.so
This tells login to display the dynamic motd /without updating it/, and
then to call pam_motd again for the static motd... and
Seb, can I ask that you (or someone on desktop) look at this, please?
The whoopsie tests clearly need to be made autopkgtests, so that they're
run at the right moment for catching glib2.0 regressions, but as that
didn't happen, it's rather urgent now to figure out the cause of this
problem.
**
This bug has been marked wontfix, citing a design request. But the
design request only indicates background color and the icon asset to
use, it does not describe the disposition of the icon box, which is part
of what James is commenting on. Can someone from design confirm that
this is actually
Setting up libpam-systemd:amd64 (208-8ubuntu5) ...
Use of uninitialized value $reply in scalar chomp at
/usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 66.
Not a pam bug, either; something's wrong with the debconf environment
here. I suspect update-manager / aptdaemon. Michael, is
Public bug reported:
The phased update implementation in ./systemimage/helpers.py does:
def phased_percentage(*, reset=False):
global _pp_cache
if _pp_cache is None:
with open(UNIQUE_MACHINE_ID_FILE, 'rb') as fp:
data = fp.read()
now =
This bug is important to fix before phone images go to factory, since it
impacts our ability to do phased over-the-air updates.
** Changed in: system-image (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
Martin, this appears to be a regression introduced by the hook added for
bug #1336462. Could you check if you think the proposed patch is
suitable?
** Changed in: apport (Ubuntu)
Status: Fix Committed = Triaged
** Changed in: apport (Ubuntu)
Assignee: Canonical Taco Screen Team
/etc/resolvconf/interface-order is only supposed to determine the order
in which interfaces are preferred as sources of DNS configuration, it
should certainly not cause the DNS servers for an interface to be
ignored completely. Please attach your full /etc/network/interfaces, as
well as the
Confirmed. The issue here is that as an NFS mount not mounted under
/usr or /var, mountall implicitly treats this as 'nobootwait'. It's
debatable whether this should be done, but the other issue is that
filesystems being marked 'nobootwait' doesn't just prevent them from
blocking the boot, it
Ok. So the crucial thing shown here is that in addition to the br
interfaces, you have NetworkManager. NetworkManager sets 'nameserver
127.0.1.1', which by design will redirect DNS requests to a local
dnsmasq proxy, with dnsmasq itself picking up the configured nameservers
instead; and when set,
Public bug reported:
Every time I look at the flight mode status on my phone, it takes me an
extra second to understand the current state. Flight mode is on, and
shows a green check box, when the network is disabled; and flight mode
is off, showing a black and white X, when the network is
Your upgrade log shows:
Paramétrage de initscripts (2.88dsf-41ubuntu18) ...
Installation de la nouvelle version du fichier de configuration
/etc/init.d/ondemand ...
insserv: warning: script 'K01vpnagentd_init' missing LSB tags and overrides
insserv: warning: script 'cron' missing LSB tags and
The root cause of this failure is:
Log started: 2014-10-26 13:07:30
(Reading database ... ^M(Reading database ... 5%^M(Reading database ...
10%^M(Reading database ... 15%^M(Reading database ... 20%^M(Reading database
... 25%^M(Reading database ... 30%^M(Reading database ... 35%^M(Reading
*** This bug is a duplicate of bug 1385817 ***
https://bugs.launchpad.net/bugs/1385817
This is a duplicate of bug #1385817. Please see that bug for
recommendations on how to correct this local problem.
In your case, the affected scripts are:
insserv: warning: script 'vpnclient_init'
The errors in the log are:
Use of uninitialized value $reply in scalar chomp at
/usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 66.
Use of uninitialized value $reply in concatenation (.) or string at
/usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 67.
Use of uninitialized value
** Changed in: system-image (Ubuntu)
Status: New = Triaged
** Changed in: system-image (Ubuntu)
Assignee: (unassigned) = James Hunt (jamesodhunt)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to system-image in
** Changed in: system-image (Ubuntu)
Importance: Undecided = High
** Changed in: system-image (Ubuntu)
Status: New = Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to system-image in Ubuntu.
This requires changes to the indicator-sound package, which is present
not only on touch images but also on the desktop. This should therefore
go through the FFe process, and be reviewed to ensure there's no risk to
the desktop.
--
You received this bug notification because you are a member of
slangasek rsalveti: so the idea here is that the
sink-input-by-media-role:$foo are only present if we're on touch?
rsalveti slangasek: they can be part of the desktop, but the dbus module that
export that interface to the indicator is only available on touch
rsalveti the stream can have
I upgraded from 14.04 to 14.10.
Do you mention this because this is a new problem that didn't exist in
previous releases?
Since /var/log/wtmp's structure doesn't include timestamps, all times in
this file must be written in UTC. Is your system clock set in local
time instead of in UTC?
*** This bug is a security vulnerability ***
Public security bug reported:
With the latest updates, unity is failing to apply the lock screen
policy on my desktop. I have my desktop configured to lock the screen
after 5 minutes of inactivity. I came back to my laptop in the morning
after a
*** This bug is a duplicate of bug 1377847 ***
https://bugs.launchpad.net/bugs/1377847
** This bug has been marked a duplicate of bug 1377847
unity screen saver no longer blanks nor locks automatically
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
This is a regression in the util-linux package in 14.10. When built
with the current debhelper, /etc/init.d/hwclock.sh is installed
alongside /etc/init/hwclock.conf, and is not masked out by the system;
and this init script has broken handling of the $UTC setting entirely.
This is courtesy of an
** Package changed: mountall (Ubuntu) = mdadm (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mountall in Ubuntu.
https://bugs.launchpad.net/bugs/1378850
Title:
EXT4-fs (md0): bad geometry: block count
Status in
I have seen this problem here as well. As the code in update-notifier
hasn't changed, I think this is probably a bug in unity, refusing to
display the window.
** Package changed: update-notifier (Ubuntu) = unity (Ubuntu)
** Changed in: unity (Ubuntu)
Status: New = Confirmed
--
You
** Changed in: sysvinit (Ubuntu)
Assignee: (unassigned) = Martin Pitt (pitti)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sysvinit in Ubuntu.
https://bugs.launchpad.net/bugs/1389891
Title:
error during upgrade:
As this is a regression in an SRU, assigning to the developer who
uploaded that version. Timo, can you please look at this?
** Tags added: regression-update
** Changed in: resolvconf (Ubuntu)
Assignee: (unassigned) = Timo Jyrinki (timo-jyrinki)
--
You received this bug notification
Nothing in the definition of /etc/os-release requires that this field be
updated for point releases. It is Ubuntu policy to not update the
machine-readable field in this file (and in /etc/lsb-release), because
software *should not* treat point releases differently than they treat
the original
packages removed from trusty-proposed; resetting bug state.
** Changed in: cups (Ubuntu Trusty)
Status: Fix Committed = Triaged
** Changed in: system-config-printer (Ubuntu Trusty)
Status: Fix Committed = Triaged
** Changed in: cups-filters (Ubuntu Trusty)
Status: Fix
** Changed in: sysvinit (Ubuntu)
Assignee: (unassigned) = Martin Pitt (pitti)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sysvinit in Ubuntu.
https://bugs.launchpad.net/bugs/1399772
Title:
/dev/shm is not writable
This config file belongs to ssh, not to pam.
** Changed in: pam (Ubuntu)
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1377924
Title:
The error in your log is:
Setting up libpam0g:amd64 (1.1.8-1ubuntu2) ...
Can't load '/opt/perl/lib/x86_64-linux-gnu-thread-multi/auto/List/Util/Util.so'
for module List::Util:
/opt/perl/lib/x86_64-linux-gnu-thread-multi/auto/List/Util/Util.so: undefined
symbol: Perl_gv_init at
*** This bug is a duplicate of bug 1358438 ***
https://bugs.launchpad.net/bugs/1358438
** This bug has been marked a duplicate of bug 1358438
package libpam-modules 1.1.8-1ubuntu2 failed to install/upgrade:
ErrorMessage: pre-dependency problem - not installing libpam-modules:i386
--
You
*** This bug is a duplicate of bug 1358438 ***
https://bugs.launchpad.net/bugs/1358438
** This bug has been marked a duplicate of bug 1358438
package libpam-modules 1.1.8-1ubuntu2 failed to install/upgrade:
ErrorMessage: pre-dependency problem - not installing libpam-modules:i386
--
You
The upgrade issue described was for saucy, and there's no reason to
think it will still be present for trusty-utopic upgrades. If the bug
does reappear, we should solve it differently, not by dropping rightful
package dependencies (which util-linux - initscripts has).
--
You received this bug
Has been discussed on IRC with Stéphane and Oliver. Stéphane and I
believe the checking should be done at livefs build time by pre-
populating the list of system users with a deterministic order.
This is a lot more reliable than having to fix things up in a boot hook
(since in the event of
** Also affects: thumbnailer (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to thumbnailer in Ubuntu.
https://bugs.launchpad.net/bugs/1363314
Title:
App fails to launch on
Why is libqt5multimedia5-plugins still using gst0.10? This seems
important to fix ASAP.
I've sponsored an upload of thumbnailer to revert the gst1.0 linkage,
but it's failed to build; so continuing to work on this.
--
You received this bug notification because you are a member of Ubuntu
Touch
This bug has been worked around by dropping gstreamer linkage from
thumbnailer, but the fact that libqt5multimedia5-plugins is linked
against gst0.10 (and pulling it onto the phone, and into main, ...)
should be considered a high-priority bug.
** Also affects: qtmultimedia-opensource-src (Ubuntu)
this is a C++-specific change; no verification is required for gccgo-4.9
in trusty.
** Changed in: gccgo-4.9 (Ubuntu Trusty)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gcc-4.8 in Ubuntu.
Moving this back to in progress. Matthias, this seems to be a major
issue for go on ppc64el in 14.04. Are you planning to SRU this fix in?
Do you know the timeline when this might happen?
Thanks!
** Changed in: gccgo-4.9 (Ubuntu Trusty)
Importance: Medium = High
** Changed in: gccgo-4.9
12.04.5 has not been released yet. It is not due for release until
August 7.
Updating of base-files is a standard part of the point release process,
so no bug report needed (and unlikely to be noticed by the folks doing
the point release); closing.
** Changed in: base-files (Ubuntu)
Sorry you're having difficulties, but this is not a bug in Ubuntu; by
removing tar you've corrupted your install. You may want to consult one
of the available user forums for help in recovering your system.
** Changed in: base-files (Ubuntu)
Status: New = Invalid
--
You received this
it is an intentional change in the package build tools.
** Changed in: resolvconf (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf in Ubuntu.
Not sure if this is by design, but run-parts didn't care and I thought
this emulated the behavior of that package- at least that's what your
documentation says.
It's not by design. But I also don't think it's a bug in pam_motd, but in
run-parts itself. pam_motd invokes run-parts with
And what makes you think that the bug is in a piece of software that's
had a stable interface for the past decade and longer, and is used by
every Debian service up to and including wheezy, rather than a bug in
your invocation?
Blocking itp
On Fri, Jul 25, 2014 at 10:35:41PM -, Matt Bruzek wrote:
I believe the gccgo 4.9.1 compiler fix is a good thing. After
rebuilding Juju with gccgo-4.9_4.9.1-1ubuntu3_ppc64el.deb I was unable
to get the juju ssh problem I had seen previously.
For purposes of this SRU bug, please verify the
acpi-support is not involved in management of brightness keys.
Reassigning to udev.
** Package changed: acpi-support (Ubuntu) = systemd (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
The title of this bug is 'MRE', but it's not obvious to me how this is
covered by the existing micro-release exceptions. tracker is a core
dependency of GNOME, but its versioning doesn't appear to correspond to
GNOME upstream versioning. Can someone please explain here how tracker
1.0.6 fits the
Hello Tim, or anyone else affected,
Accepted tracker into utopic-proposed. The package will build now and be
available at http://launchpad.net/ubuntu/+source/tracker/1.0.6-0ubuntu1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
The /etc/network/if-up.d/mountnfs script has not been part of Ubuntu
since Ubuntu 9.04. How do you have this script on your system at all?
** Changed in: sysvinit (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
** This bug is no longer a duplicate of bug 1372193
package libpam-systemd:amd64 208-8ubuntu4 failed to install/upgrade:
subprocess installed post-installation script returned error exit status 128 in
pam-auth-update
--
You received this bug notification because you are a member of Ubuntu
** Also affects: llvm-toolchain-snapshot (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libdrm in Ubuntu.
https://bugs.launchpad.net/bugs/1400626
Title:
Please backport
Instead of uploading a new llvm-toolchain-3.5 package to trusty-
proposed, let's reuse the llvm-toolchain-snapshot source package which
already builds all of the relevant binaries in trusty.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Changed in: llvm-toolchain-snapshot (Ubuntu Trusty)
Status: New = Fix Committed
** Changed in: llvm-toolchain-snapshot (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libdrm in
** Changed in: xorg (Ubuntu)
Importance: High = Low
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1132736
Title:
Xorg fails to start after installing the hardware
** Also affects: xorg (Ubuntu)
Importance: Undecided
Status: New
** Changed in: xorg (Ubuntu)
Importance: Undecided = High
** Changed in: xorg (Ubuntu)
Assignee: (unassigned) = Maarten Lankhorst (mlankhorst)
** Changed in: xorg (Ubuntu)
Status: New = Triaged
--
You
Public bug reported:
After upgrading a snappy system from 211 to 219, I'm seeing the
following errors at boot:
[ 88.772405] systemd-journald[704]: Failed to join audit multicast group:
Operation not permitted
[ 88.777304] systemd[1]: Started User Manager for UID 1000.
[ 88.778311]
after a reinstall and upgrade to version 221, I'm not seeing this
problem now.
--
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/142
Title:
systemd-journal: Failed to
The second part of the patch proposed to upstart's wait-for-state job is
reasonable, but has nothing to do with the behavior shown here. And the
first part of the patch is wrong. It's not appropriate to change the
default wait-for-state behavior that other packages are relying on.
This is a regression introduced in the last whoopsie upload in vivid.
Prior to this, the upstart job included deliberate handling in
/etc/init/whoopsie.conf to ensure that if whoopsie were disabled in the
config, the job would be stopped without triggering upstart's respawn
behavior. Assigning
Please show the /etc/fstab from the affected system, and indicate which
mounts are not being mounted before the event is emitted.
** Changed in: mountall (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
Public bug reported:
After upgrading yesterday to the latest cups package, my root partition
is filling up at the rate of more than a gigabyte per day, as a result
of /var/log/cups/error.log being filled with useless messages.
Examples:
D [12/Feb/2015:06:58:49 -0800] [Client 60] POST / HTTP/1.1
package removed from trusty-proposed.
** Changed in: libsignon-glib (Ubuntu Trusty)
Status: Fix Committed = Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libsignon-glib in Ubuntu.
The masking of mountall when booting with systemd is deliberate;
mountall is a component of upstart's boot system and should not be used
with systemd.
So if there are any problems with mounting filesystems at boot when
booting with systemd, that's a systemd bug. Reassigning.
** Package changed:
On Mon, Mar 16, 2015 at 01:59:16PM -, Michael Terry wrote:
Is there no way to mark a package in main as 'not supported?' I
remember that we have some way to mark a universe package as supported.
Can we do the inverse?
This, in effect, is what the archive reorg spec was about.
Phone-specific functionality. FFe approved.
** Changed in: webbrowser-app (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
Please attach the log /var/lib/insserv/run-20150306T1805.log from this
system.
** Changed in: sysvinit (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sysvinit in Ubuntu.
I've seen this as well on my desktop. For me it was not a regression
vs. upstart (there are bug reports about nfs mounts similarly not being
mounted at boot under upstart in Ubuntu 14.10 and later), which is why I
did not consider this a blocker for switching by default.
Looking at the systemd
Public bug reported:
After some recent update in vivid, connecting to my employer's VPN with
network-manager-openvpn has resulted in broken name resolution.
Previously, the VPN-provided nameserver setting would be pushed into the
config of the dnsmasq run by NM. Now, it is being pushed instead
Jamie, now that systemd is becoming the default in vivid, I think this
is critical to fix, as dmesg is quite spammy at present (and of course
the log entries are being lost if the writes are denied). Can this fix
be expedited?
--
You received this bug notification because you are a member of
1 - 100 of 2444 matches
Mail list logo
