Carlos Garnacho [2017-03-01 10:59 -]:
> > - Is it acceptable to have approximate search results if the indexing isn't
> > (yet) up to date?
>
> If tracker-miner-fs is not paused/throttled down, it will pick up
> changes in monitored folders just as fast as any other app, there is
> very
> To summarize, I see 2 performance questions:
I'd add:
- Is it acceptable to have approximate search results if the indexing isn't
(yet) up to date?
- Does it significantly affect battery life?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
Hello Carlos,
Carlos [2017-02-28 13:58 -]:
> Just wanted to mention I disagree with your statements and that I have
> the opposite experience and feedback from users (we agree we disagree,
> which is fine of course :)).
Yep :-) (I'm not making the call anyway). Thanks for sharing your
Carlos [2017-02-28 12:08 -]:
> "Tracker imposes a huge cost due to always indexing everything"
> As long as is low priority and the kernel scheduler works fine it shouldn't
> be an issue.
This isn't true. This will use a lot more CPU and disk cycles, thus decreasing
battery life. Or, if you
So all of this tells me that tracker isn't a replacement for typeahead
search. They have two entirely different use cases:
* Typeahead search only affects the currently displayed directory (or
should anyway -- you search through what you see, not through the
entirety of the file system). It is
@Scott:
https://git.launchpad.net/postfix/commit/?h=stable/v3.1=1a190cf17cc02
looks rather complicated and also creates an unmanaged config file. Why
not just always add those After= to the .service? If resolved is not
enabled, then After=systemd-resolved is a no-op (it's only ordering, not
a
** Also affects: resolvconf (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847440
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
Public bug reported:
On shutdown or "systemctl stop systemd-resolved" you get a long hang:
● systemd-resolved.service - Network Name Resolution
CGroup: /system.slice/systemd-resolved.service
└─control
├─15479 /bin/sh -c [ ! -e /run/resolvconf/enable-updates ] ||
This is still being discussed upstream, so let's get to an agreement
there first, land it in upstream master, and then backport the change.
Note that there is not much point with debdiffs, it's easier to cherry-
pick the fix directly into the packaging branches with gbp pq and debian
I'm afraid this is by design and wontfix, see
https://github.com/systemd/systemd/issues/4821#issuecomment-264995354
for details. This isn't something which we reasonably can/should change
downstream, so I suggest to direct discussions to the upstream bug.
Thanks!
** Changed in: systemd (Ubuntu)
> Before=networking.service
> +Before=systemd-networkd.service
FTR, this should be generalized to Before=network-pre.target. This is
also applicable to Debian.
** Also affects: resolvconf (Ubuntu)
Importance: Undecided
Status: New
** Changed in: resolvconf (Ubuntu)
Status: New
> In CUPS everything is OK and as intended.
No -- as above, the maintainer scripts need to stop cups.{socket,path}
first before stopping cups.service. Also, as it seems you can entirely
drop that .path unit as it's fairly useless -- we don't start cups on
demand, but it always starts on boot (in
** Bug watch added: github.com/systemd/systemd/issues #4821
https://github.com/systemd/systemd/issues/4821
** Also affects: systemd via
https://github.com/systemd/systemd/issues/4821
Importance: Unknown
Status: Unknown
** Changed in: systemd (Ubuntu)
Status: Confirmed =>
** Bug watch added: github.com/systemd/systemd/issues #4801
https://github.com/systemd/systemd/issues/4801
** Also affects: systemd via
https://github.com/systemd/systemd/issues/4801
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a
** Also affects: dpkg (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- package systemd 229-4ubuntu4 failed to install/upgrade: triggers looping,
abandoned
+ several packages failed to install/upgrade: triggers looping, abandoned
--
You received this bug notification
*** This bug is a duplicate of bug 1573322 ***
https://bugs.launchpad.net/bugs/1573322
This is a duplicate of bug 1624729, but for some reason Launchpad keeps
timing out in trying to mark it as such, so I'm closing this.
** Changed in: systemd (Ubuntu)
Status: New => Invalid
--
You
*** This bug is a duplicate of bug 1573322 ***
https://bugs.launchpad.net/bugs/1573322
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** This bug has been marked a duplicate of bug 1573322
package systemd 229-4ubuntu4 failed to install/upgrade: triggers
*** This bug is a duplicate of bug 1573322 ***
https://bugs.launchpad.net/bugs/1573322
** This bug has been marked a duplicate of bug 1646767
package systemd 232-6 failed to install/upgrade: gatilhos em "loop",
abandonado
** This bug is no longer a duplicate of bug 1646767
package
** No longer affects: systemd (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1645631
Title:
Sending files fails because obex not loaded
To manage notifications about
I suppose you want this for yakkety too, so backported:
https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h
=ubuntu-yakkety=648c659e9
** Description changed:
Ubuntu Core 16 images using cloud-init fail to function when the
DataSource is over the network (Like OpenStack) as
Hello Robert, or anyone else affected,
Accepted gnome-software into xenial-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/gnome-
software/3.20.1+git20161013.0.d77d6cf-0ubuntu2~xenial1 in a few hours,
and then in the -proposed repository.
Please help
Hello Will, or anyone else affected,
Accepted gnome-software into xenial-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/gnome-
software/3.20.1+git20161013.0.d77d6cf-0ubuntu2~xenial1 in a few hours,
and then in the -proposed repository.
Please help
Hello Robert, or anyone else affected,
Accepted gnome-software into xenial-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/gnome-
software/3.20.1+git20161013.0.d77d6cf-0ubuntu2~xenial1 in a few hours,
and then in the -proposed repository.
Please help
Can you please add a test case? I. e. how does the naming currently
look, and how is it supposed to look with the patch?
** Also affects: systemd (Ubuntu Yakkety)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu)
Status: New => Fix Released
** Changed in:
Hello Kyle, or anyone else affected,
Accepted gnome-software into xenial-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/gnome-
software/3.20.1+git20161013.0.d77d6cf-0ubuntu2~xenial1 in a few hours,
and then in the -proposed repository.
Please help
** Also affects: systemd (Ubuntu Trusty)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1562344
Title:
Not working hotkeys for
snapd-glib accepted into xenial. Please upload the corresponding gnome-
software SRU.
** Changed in: snapd-glib (Ubuntu Xenial)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-software in
> [Regression Potential]
> None.
This is a vast underestimate -- touching udev rules can lead to an
unbootable system in the worst case :-) I'll adjust the description.
** Also affects: systemd (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Xenial)
The verification of the Stable Release Update for ubiquity 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 encounter
** No longer affects: systemd (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1637758
Title:
lightdm greeter session not properly shut down at login
To manage
** No longer affects: systemd (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/765152
Title:
spacenavd xserver permissions problem
To manage notifications about this bug
Hello Ryan, or anyone else affected,
Accepted ceph into yakkety-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/ceph/10.2.3-0ubuntu2.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello KyL416, or anyone else affected,
Accepted metacity into yakkety-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/metacity/1:3.20.3-1ubuntu2.1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Public bug reported:
Ted Gould and Dimitri Ledkov requested that the graphical-
session{,-pre}.target user units introduced in yakkety should be
backported to xenial, so that snapd units can use them.
At the moment they will *not* be used by default by any desktop session
in xenial, so they will
This got fixed in version 232, now in zesty.
** Changed in: systemd (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1638301
Title:
** No longer affects: systemd (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1639440
Title:
[desktop] apps don't start, missing logs
To manage notifications about this
Turns out that resolvconf always filters out comments, so the only way
to get a comment in there is via /etc/resolvconf/resolv.conf.d/head. So
moving package.
** Package changed: systemd (Ubuntu) => resolvconf (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
s: systemd (Ubuntu)
Importance: Low
Assignee: Martin Pitt (pitti)
Status: In Progress
** Changed in: systemd (Ubuntu)
Status: New => In Progress
** Changed in: systemd (Ubuntu)
Importance: Undecided => Low
** Changed in: systemd (Ubuntu)
Milestone: None
** Bug watch added: github.com/systemd/systemd/issues #4504
https://github.com/systemd/systemd/issues/4504
** Also affects: systemd via
https://github.com/systemd/systemd/issues/4504
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a
: Undecided
Status: New
** Changed in: systemd (Ubuntu)
Importance: High => Medium
** Changed in: systemd (Ubuntu Xenial)
Importance: Undecided => High
** Changed in: systemd (Ubuntu Xenial)
Status: New => Triaged
** Changed in: cloud-init (Ubuntu)
Assignee: Marti
cloud-init already has *very* strong dependencies:
Requires=networking.service
Before=basic.target
(which is sorting the early boot fairly strictly). But I guess in the
same vein, if cloud-init wants to run in between networkd and
basic.target, it needs to grow an
Mostly a duplicate of bug 1484027. rsyslog ships
/usr/lib/tmpfiles.d/00rsyslog.conf which overrides the default var.conf.
This is just an informational message.
** Changed in: systemd (Ubuntu)
Status: New => Triaged
** Changed in: systemd (Ubuntu)
Importance: Undecided => Low
** Also
Please upload to zesty first.
** Also affects: snapd-glib (Ubuntu Yakkety)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to snapd-glib in Ubuntu.
https://bugs.launchpad.net/bugs/1635270
The verification of the Stable Release Update for evolution 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 gnome-settings-daemon
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
The verification of the Stable Release Update for gnome-settings-daemon
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
: Medium
Assignee: Martin Pitt (pitti)
Status: In Progress
** Also affects: systemd (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu)
Status: New => Invalid
** Changed in: systemd (Ubuntu Xenial)
Status: New => In Pr
** Package changed: systemd (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1635171
Title:
IPv6 Privacy Extensions do not work
To manage notifications
Hello Jeremy, or anyone else affected,
Accepted file-roller into yakkety-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/file-
roller/3.22.1-0ubuntu1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package.
Thanks for forwarding this upstream! I cherry-picked the patch.
** Bug watch added: github.com/systemd/systemd/issues #4371
https://github.com/systemd/systemd/issues/4371
** Also affects: systemd via
https://github.com/systemd/systemd/issues/4371
Importance: Unknown
Status:
The verification of the Stable Release Update for gnome-software 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 gnome-software 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 gnome-software 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 gnome-software 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
So I suppose this got broken as a subtle side effect from
https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h
=ubuntu-xenial=5c429176 (bug 1529079). Do you have a reproducer for
this that we can use to verify the fix?
** Also affects: systemd (Ubuntu Xenial)
Importance: Undecided
Hello Will, or anyone else affected,
Accepted gnome-software into yakkety-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/gnome-
software/3.20.1+git20161013.0.d77d6cf-0ubuntu1 in a few hours, and then
in the -proposed repository.
Please help us by
Hello Jeremy, or anyone else affected,
Accepted evolution into yakkety-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/evolution/3.22.1-0ubuntu1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Cristian, or anyone else affected,
Accepted webkit2gtk into yakkety-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/webkit2gtk/2.14.1-0ubuntu1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package.
Hello Jeremy, or anyone else affected,
Accepted gnome-settings-daemon into yakkety-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/gnome-settings-daemon/3.22.1-0ubuntu1 in a few hours, and then in the
-proposed repository.
Please help us by testing
Hello shankao, or anyone else affected,
Accepted gnome-settings-daemon into yakkety-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/gnome-settings-daemon/3.22.1-0ubuntu1 in a few hours, and then in the
-proposed repository.
Please help us by testing
xchat-gnome has been removed from Debian and Ubuntu as it's unmaintained
and superseded by hexchat.
** Bug watch added: Debian Bug tracker #830188
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830188
** Also affects: xchat-gnome (Debian) via
FWIW, if you feel confident about this, please drop the block-proposed
tag. We still need to do at least one more full image rebuild anyway.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evolution-data-server in Ubuntu.
** No longer affects: systemd (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1631980
Title:
Steam not able to see network in yakkety
To manage notifications about this
Hello Jeremy, or anyone else affected,
Accepted evolution-data-server into yakkety-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/evolution-data-server/3.22.1-0ubuntu1 in a few hours, and then in the
-proposed repository.
Please help us by testing
OK. This could be because NM does not feed it with correct DNS data, or
dnsmasq itself gets confused after resuming. Assigning to NetworkManager
for now.
** Package changed: systemd (Ubuntu) => network-manager (Ubuntu)
** Changed in: network-manager (Ubuntu)
Status: Incomplete => New
--
** Changed in: dbus (Ubuntu)
Status: New => Won't Fix
** No longer affects: systemd (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1623198
Title:
Masking and then
** Package changed: systemd (Ubuntu) => linux (Ubuntu)
** Tags added: kernel-4.8
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1626466
Title:
[Yakkety] suspend fail and reboot
Right, you can't sensibly stop dbus on a running desktop. This will kill
all sessions, kill lightdm, etc. and toss you back to consoles
(Ctrl+Alt+FN actually still works).
** Package changed: systemd (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Won't Fix
--
You received this
This was fixed in
https://launchpad.net/ubuntu/+source/policykit-1/0.105-16
** Changed in: policykit-1 (Ubuntu)
Status: Confirmed => Fix Released
** No longer affects: systemd (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
Right. As the manpage states, inactive units are not considered: "Units
which are not active and are not in a failed state usually are not
loaded, and will not be matched by any pattern."
This isn't a behaviour that we can or want to change downstream, so
closing. Thanks!
** Changed in: systemd
As discussed on IRC, let's ignore this. The test is by and large fine,
there's just something wrong with either configuring lightdm, or
apparmor profiles or what not. It works in later releases, we don't do
vivid SRUs any more, and there's nothing actually broken in the package,
so britney hinting
I didn't find a simpler reproducer on the CLI, and the systemd test now
does not call rmmod any more, so there's no handle on this any more.
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
Bug 1588230 and bug 1624071 are fixed now. I'm fairly sure I understand
bug 1624317 (and it would be fixed in yakkety now), and bug 1449001 is
not actually a malfunction but just some disagreement about a builtin
fallback if no DNS servers are configured (and thus fairly irrelevant
really).
This
Hello Cledersonbc, or anyone else affected,
Accepted gnome-calculator into xenial-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/gnome-
calculator/1:3.18.3-0ubuntu1.16.04.1 in a few hours, and then in the
-proposed repository.
Please help us by
Early in z-series we should look into starting D-Bus ealier, to fix this
in a more generic fashion.
** Package changed: systemd (Ubuntu) => dbus (Ubuntu)
** Changed in: dbus (Ubuntu)
Milestone: None => ubuntu-16.11
** Changed in: dbus (Ubuntu)
Assignee: (unassigned) => Ma
** Package changed: systemd (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1630245
Title:
after starting ubuntu 16.10 -- no keyboard, no mouse
To
Iain Lane [2016-10-01 19:26 -]:
> Hmm. Maybe this is saying that we should bind ubuntu-session.target to
> something else - like unity7? You can't log in again with an active
> unity7, so in theory (if stop is propagated down to graphical-session
> and graphical-session-pre) there wouldn't be
> If you ever end up stopping gnome-keyring from within a new session
then its ExecStopPost kills the upstart session of this new one that we
are starting up, *not* the previous one that it was started up under.
I assume you meant to say "gnome-session.service" here, not keyring (as
its
> To fix that, something like comment #3 is needed. Such as looping over
all 'active' units that are PartOf graphical-session.target and stopping
them all.
I think we would only need to "systemctl stop graphical-session.target"
for this, otherwise a unit forgets the PartOf= and that loop would
That initial fix just changed a DoS through assert() into a DoS through
fd exhaustion. This is being handled in
https://github.com/systemd/systemd/pull/4242 .
Please let's handle this upstream first and not put out another USN in
haste -- after all, this is just a local DoS, so far from being a
ntu-16.10
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Martin Pitt (pitti)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1588230
Title:
systemd-resolved uses
** Bug watch added: github.com/systemd/systemd/issues #4234
https://github.com/systemd/systemd/issues/4234
** Also affects: systemd via
https://github.com/systemd/systemd/issues/4234
Importance: Unknown
Status: Unknown
** Changed in: systemd (Ubuntu Xenial)
Importance:
nassigned) => Martin Pitt (pitti)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1627641
Title:
Backport netplan to xenial
To manage notifications about this bug
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1626737
Title:
[4.8.0-14/ppc64el regression] rmmod
Changing tasks as this is somewhere between unity-settings-daemon and
polkit.
** Package changed: linux (Ubuntu) => unity-settings-daemon (Ubuntu)
** Changed in: unity-settings-daemon (Ubuntu)
Status: Incomplete => Triaged
** Package changed: systemd (Ubuntu) => policykit-1 (Ubuntu)
**
http://autopkgtest.ubuntu.com/packages/s/systemd/yakkety/ppc64el passed
a few times again, and that tmpfiles crash never reproduced.
** Changed in: systemd (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: systemd (Ubuntu)
Status: Fix Released => Invalid
--
You received
This was fixed in -14, scsi_debug is back.
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1625100
Title:
Talked to Andy on IRC, and dropping these drivers was not intended. I
agree we should keep the most common ones built in, especially for cloud
instances; there it would really be beneficial to drop initrds
completely (see bug 1592684), as they are just bloat there.
** Changed in: systemd (Ubuntu)
: Undecided
Status: Confirmed
** Affects: systemd (Ubuntu)
Importance: Undecided
Assignee: Martin Pitt (pitti)
Status: In Progress
** Tags: bot-stop-nagging
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu
dns")
and modifying to "files resolve [!UNAVAIL=return] dns [foo=bar]", then purge
libnss-resolve again -- this should again remove the [!UNAVAIL=return] but
*NOT* "dns [foo=bar]".
** Affects: systemd (Ubuntu)
Importance: Medium
Assignee: Martin Pitt (pitti)
Thanks for the followup. Closing the debian-installer part now. The work
on the Debian side wrt. multiplexing the installer UI to mutiple
consoles sounds interesting, but I don't think we should houd our breath
for it -- I think this is going to be tricky given how different the
capabilities of VT
I believe this is fixed by https://anonscm.debian.org/cgit/pkg-
systemd/systemd.git/commit/?id=be10d22 . We should also SRU this fix.
** Summary changed:
- systemd does not allow fsck to finish on ubuntu 15.10
+ systemd does not allow fsck to finish
** Bug watch added: Debian Bug tracker
** Package changed: systemd (Ubuntu) => zfs-linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1624844
Title:
Ubuntu 16.04 breaks boot with wrong zpool.cache
To manage
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1625100
Title:
systemd 231-6 ADT test failure with linux
Thanks Doug! Ack, I'll change it to use "powersave" again then.
** Changed in: systemd (Ubuntu)
Status: Fix Released => In Progress
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
$TERM only gets set for units which have Standard{Output,Error}=tty. By
default services only have a stdout/err pipe to the journal, and rc-
local.service uses journal+console which is still a pipe. So it would be
actively wrong to set $TERM there as it is not actually a terminal. (See
man
Only two rdepends (appstream-generator and limba) which are already
prepared in your PPA and just syncs. Low-risk IMHO, so please go ahead.
** Changed in: appstream (Ubuntu)
Status: New => Triaged
** Summary changed:
- FFe: Sync appstream 0.10.0-2 (main) from Debian unstable (main)
+
This matches https://github.com/systemd/systemd/issues/3421 very closely
(I've worked on this a bit, but it got stalled, sorry). I think that is
the exact symptom you are seeing, can you confirm?
** Bug watch added: github.com/systemd/systemd/issues #3421
outh-start'))
AssertionError: False is not true
Same assertion failure on some other systemd-fsckd tests.
** Affects: systemd (Ubuntu)
Importance: High
Assignee: Martin Pitt (pitti)
Status: In Progress
** Tags: autopkgtest yakkety
** Tags added: autopkgtest yakkety
** Changed i
** Changed in: gnome-session (Ubuntu)
Status: In Progress => Won't Fix
** Changed in: gnome-session (Ubuntu)
Status: Won't Fix => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-session in Ubuntu.
1 - 100 of 7748 matches
Mail list logo
