Re: [Bug 1666676] Re: Enable tracker by default for Unity too
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 little extra overhead above the gio/inotify delays. > > - Does it significantly affect battery life? > > Given Tracker is pretty conservative while on battery, that's a bold "no". It's hard to make these statements simultaneously be true. There's clearly a trade-off between correctness and efficiency here. Unless nautilus pokes tracker to wake up and do a shallow (no previews, etc.) index/force-refresh the searched-for directory unthrottled right away? Then that would be the equivalent of a "classic" search, except that the gained data would be available in the tracker DB for the next time. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/176 Title: Enable tracker by default for Unity too To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/176/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1666676] Re: Enable tracker by default for Unity too
> 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 subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/176 Title: Enable tracker by default for Unity too To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/176/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1666676] Re: Enable tracker by default for Unity too
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 perspective (e. g. both techies and non-tech people I know don't use full search, so interesting to read what other people use it for). -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/176 Title: Enable tracker by default for Unity too To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/176/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1666676] Re: Enable tracker by default for Unity too
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 don't index while on battery, it's going to be even less reliable. > "So I don't see how "enable tracker" can ever be a replacement for typeahead > search" Maybe I was not clear enough in my first post. (don't mean to be > rude, just clear) Tracker is needed for search in Nautilus. Period. That's the bit I'm totally not convinced of. Due to it's "background/async" nature, it's not reliable for searching, and it's also way too much overhead to replace a single-directory level search (i. e. what you usually do for typeahead search). Doing a fully recursive search is okay to be slow, as that's only being used seldomly, and if you do it you most probably want the results to be correct, not approximative. So my (very subjective) opinion is that any indexing tool is not an appropriate backend for searching. This isn't particularly tracker's fault, it's just the nature of what an indexer is. Also, note that I'm not speaking authoritatively for the Ubuntu desktop team, this is just my personal opinion. I would just not appreciate it to see getting an indexer imposed onto everyone for rare use cases (like content-based batch renaming) -- optimize for the common case instead. As I said, if you care about content preview etc., it's still fine to give users an opt-in into this. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/176 Title: Enable tracker by default for Unity too To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/176/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1666676] Re: Enable tracker by default for Unity too
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 fast as it's only one readdir(), and nautilus already did that as it's displaying at least the first portion of the directory and there is no need to stat() the individual files. It also needs to be instant and correct even when I just copied a large directory from somewhere else or am looking at a remote sftp/cifs directory, and work everywhere. * Tracker imposes a huge cost due to always indexing everything (even if you never search for it). It's good for tasks like "where did I put my files last week". However, it is necessarily only approximate, as it has some delay (which can be quite large if you are on battery, or just copied a large bunch of files), and not universal (non-XDG directories, remote file systems), etc. So I don't see how "enable tracker" can ever be a replacement for typeahead search, and TBH I still don't buy that we have to penalize each and every installation with the tracker overhead even though most people don't do full-hard disk searches all the time (and many don't do this at all). And if you do need a "search through my home dir", you *still* need to do an actual search due to the latency/approximative nature of indexing. It's not an acceptable answer to say "sorry, we don't show the file you just downloaded as we didn't get to indexing it yet". I see tracker as a nice opt-in (!) feature for people who often do full searches, so this might become a checkbox in the search box? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/176 Title: Enable tracker by default for Unity too To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/176/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1649453] Re: systemd starts postfix before resolver
@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 dependency -- that would be Requires= or Wants=). Also, not sure why you added network-online.target, but if you actually do want to wait for the network then you also need a corresponding Wants =network-online.target (see man systemd.special). ** No longer affects: systemd (Ubuntu) ** Tags added: resolved -- 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/1649453 Title: systemd starts postfix before resolver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1649453/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1636912] Re: systemd-networkd runs too late for cloud-init.service (net)
** 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. https://bugs.launchpad.net/bugs/1636912 Title: systemd-networkd runs too late for cloud-init.service (net) To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1636912/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1648068] [NEW] systemd-resolved.service hangs a long time on shutdown
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 ] || /sbin/resolvconf -d systemd-resolved ├─15480 run-parts --arg=-d --arg=systemd-resolved /etc/resolvconf/update.d ├─15483 run-parts /etc/resolvconf/update-libc.d ├─15497 /bin/sh /usr/lib/avahi/avahi-daemon-check-dns.sh └─15509 host -t soa local. So that resolvconf hook tries to do name resolution which does not work any more at that time. ** Affects: systemd (Ubuntu) Importance: Medium Status: Triaged ** Tags: resolved ** Tags added: resolved ** Summary changed: - systemd-resolved hangs a long time on shutdown + systemd-resolved.service hangs a long time on shutdown ** Changed in: systemd (Ubuntu) Status: New => Triaged ** Changed in: systemd (Ubuntu) Importance: Undecided => Medium -- 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/1648068 Title: systemd-resolved.service hangs a long time on shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1648068/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1647485] Re: NVMe symlinks broken by devices with spaces in model or serial strings
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 /git-cherry-pick. ** Also affects: systemd via https://github.com/systemd/systemd/issues/4833 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. https://bugs.launchpad.net/bugs/1647485 Title: NVMe symlinks broken by devices with spaces in model or serial strings To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1647485/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1636375] Re: systemd-resolved does not allow you to connect using subdomains using search domains which are in /etc/resolv.conf
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) Status: Triaged => Won't Fix -- 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/1636375 Title: systemd-resolved does not allow you to connect using subdomains using search domains which are in /etc/resolv.conf To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1636375/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1636912] Re: systemd-networkd runs too late for cloud-init.service (net)
> 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 => Triaged ** Changed in: resolvconf (Ubuntu Xenial) Status: New => Triaged ** Changed in: resolvconf (Ubuntu Yakkety) Status: New => Triaged -- 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/1636912 Title: systemd-networkd runs too late for cloud-init.service (net) To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1636912/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1642966] Re: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
> 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 a default install). It would of
course be nice to fix that (as I suggested in the upstream bug).
> And there is also another bug in systemd: The *.path file as it comes
with CUPS should always start CUPS (if it is not already running) if
there is the keepalive file, not only if the keepalive file is newly
created.
It does -- that's precisely what happens here: The path unit restarts
cups after the maintainer scripts stop it, and that's the core of this
bug. So if anything, you want it to be less aggressive, not more :-)
> cups-browsed.service contains "After=cups.service avahi-
daemon.service" in its [Unit] section. Is this enough to make cups-
browsed being shut down before the shutdown of CUPS is done?
Yes, it is, the Before/After get inversed on stopping units.
** Changed in: cups (Ubuntu)
Status: Invalid => Confirmed
--
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/1642966
Title:
package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new
pre-removal script returned error exit status 1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1642966/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1636375] Re: systemd-resolved does not allow you to connect using subdomains using search domains which are in /etc/resolv.conf
** 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 => Triaged ** Changed in: systemd (Ubuntu) Importance: Undecided => Medium -- 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/1636375 Title: systemd-resolved does not allow you to connect using subdomains using search domains which are in /etc/resolv.conf To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1636375/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1644330] Re: systemd-resolved assumes that /etc/hosts for one address family means it doesn't ask DNS for another
** 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 member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1644330 Title: systemd-resolved assumes that /etc/hosts for one address family means it doesn't ask DNS for another To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1644330/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1573322] Re: package systemd 229-4ubuntu4 failed to install/upgrade: triggers looping, abandoned
** 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 because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1573322 Title: several packages failed to install/upgrade: triggers looping, abandoned To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1573322/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1573323] Re: package systemd 229-4ubuntu4 [modified: usr/share/dbus-1/system-services/org.freedesktop.systemd1.service] failed to install/upgrade: triggers looping, abandoned
*** 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 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/1573323 Title: package systemd 229-4ubuntu4 [modified: usr/share/dbus-1/system- services/org.freedesktop.systemd1.service] failed to install/upgrade: triggers looping, abandoned To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1573323/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1624729] Re: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: triggers looping, abandoned
*** 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 looping, abandoned -- 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/1624729 Title: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: triggers looping, abandoned To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1624729/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1646768] Re: package systemd 232-6 failed to install/upgrade: gatilhos em "loop", abandonado
*** 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 systemd 232-6 failed to install/upgrade: gatilhos em "loop", abandonado ** This bug has been marked a duplicate of bug 1573322 package systemd 229-4ubuntu4 [modified: usr/share/dbus-1/system-services/org.freedesktop.systemd1.service] failed to install/upgrade: triggers looping, abandoned -- 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/1646768 Title: package systemd 232-6 failed to install/upgrade: gatilhos em "loop", abandonado To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1646768/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1645631] Re: Sending files fails because obex not loaded
** 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 this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1645631/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1636912] Re: systemd-networkd runs too late for cloud-init.service (net)
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 networking is not yet available when cloud-init.service runs. cloud-init service unit deps look like this: [Unit] Description=Initial cloud-init job (metadata service crawler) DefaultDependencies=no Wants=cloud-init-local.service Wants=local-fs.target Wants=sshd-keygen.service Wants=sshd.service After=cloud-init-local.service After=networking.service Requires=networking.service Before=basic.target Before=dbus.socket Before=network-online.target Before=sshd-keygen.service Before=sshd.service Before=systemd-user-sessions.service Conflicts=shutdown.target Here's networkd unit deps: [Unit] Description=Network Service Documentation=man:systemd-networkd.service(8) ConditionCapability=CAP_NET_ADMIN DefaultDependencies=no # dbus.service can be dropped once on kdbus, and systemd-udevd.service can be # dropped once tuntap is moved to netlink After=systemd-udevd.service dbus.service network-pre.target systemd-sysusers.service systemd-sysctl.service Before=network.target multi-user.target shutdown.target Conflicts=shutdown.target Wants=network.target # On kdbus systems we pull in the busname explicitly, because it # carries policy that allows the daemon to acquire its name. Wants=org.freedesktop.network1.busname After=org.freedesktop.network1.busname And a critical-chain output: root@snap-test7:~# systemd-analyze critical-chain systemd-networkd Failed to get ID: Unit name systemd-networkd is not valid. The time after the unit is active or started is printed after the "@" character. The time the unit takes to start is printed after the "+" character. root@snap-test7:~# systemd-analyze critical-chain systemd-networkd.service The time after the unit is active or started is printed after the "@" character. The time the unit takes to start is printed after the "+" character. systemd-networkd.service +440ms └─dbus.service @11.461s └─basic.target @11.403s └─sockets.target @11.401s └─dbus.socket @11.398s └─cloud-init.service @10.127s +1.266s └─networking.service @9.305s +799ms └─network-pre.target @9.295s └─cloud-init-local.service @3.822s +5.469s └─local-fs.target @3.813s └─run-cgmanager-fs.mount @12.687s └─local-fs-pre.target @1.393s └─systemd-tmpfiles-setup-dev.service @1.116s +195ms └─kmod-static-nodes.service @887ms +193ms └─system.slice @783ms └─-.slice @721ms cloud-init would need networkd to run at or before 'networking.service' so it can raise networking to then find and use network-based datasources. # grep systemd /usr/share/snappy/dpkg.list ii libnss-resolve:amd64 229-4ubuntu11 amd64nss module to resolve names via systemd-resolved ii libpam-systemd:amd64 229-4ubuntu11 amd64system and service manager - PAM module ii libsystemd0:amd64 229-4ubuntu11 amd64systemd utility library ii systemd 229-4ubuntu11 amd64system and service manager ii systemd-sysv 229-4ubuntu11 amd64system and service manager - SysV links # grep cloud-init /usr/share/snappy/dpkg.list ii cloud-init 0.7.8-201610260005-gf7a5756-0ubuntu1~trunk~ubuntu16.04.1 all Init scripts for cloud instances SRU INFORMATION FOR systemd === - Fix: For xenial it is sufficient to drop systemd-networkd's After=dbus.service (https://github.com/systemd/systemd/commit/5f004d1e32) and drop the useless org.freedesktop.network1.busname unit (which is always "condition failed" as there is no kdbus, but it moves systemd-network.service after sockets.target which is too late for cloud-init). + Fix: For xenial it is sufficient to drop systemd-networkd's After=dbus.service (https://github.com/systemd/systemd/commit/5f004d1e32) and (for xenial only) drop the useless org.freedesktop.network1.busname unit (which is always "condition failed" as there is no kdbus, but it moves systemd-network.service after sockets.target which is too late for cloud-init). Regression potential: Low. networkd is not widely being used outside of netplan/snappy in xenial. Running it before dbus.service is running has two
[Bug 1595023] Re: Need to determine if snap apps require terminal or not
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 us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Tags added: verification-needed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1595023 Title: Need to determine if snap apps require terminal or not To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1595023/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1616943] Re: Can't auth against U1 in g-s
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 us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Tags removed: verification-failed ** Tags added: verification-needed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1616943 Title: Can't auth against U1 in g-s To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1616943/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1603610] Re: Snaps have no screenshots
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 us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Tags added: verification-needed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1603610 Title: Snaps have no screenshots To manage notifications about this bug go to: https://bugs.launchpad.net/snapd-glib/+bug/1603610/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1644355] Re: udev netdev naming does not work with mellanox switches
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: systemd (Ubuntu Yakkety) Status: New => Triaged -- 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/1644355 Title: udev netdev naming does not work with mellanox switches To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1644355/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1629456] Re: Summary isn't shown for snaps
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 us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Tags added: verification-needed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1629456 Title: Summary isn't shown for snaps To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1629456/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1562344] Re: Not working hotkeys for brightness in HP ProBook 640 G2
** 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 brightness in HP ProBook 640 G2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1562344/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1616943] Re: Can't auth against U1 in g-s
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 Ubuntu. https://bugs.launchpad.net/bugs/1616943 Title: Can't auth against U1 in g-s To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1616943/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1642903] Re: introduce disk/by-id (model_serial) symlinks for NVMe drives
> [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) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Zesty) Importance: Wishlist Status: New ** Changed in: systemd (Ubuntu Zesty) Status: New => Fix Released ** Description changed: [Impact] NVMe drives can't be identified/accessed via /dev/disk/by-id/nvme-SERIAL symlinks. [Test Case] On a system with an NVMe drive, check the /dev/disk/by-id/ directory; with the patch, it will contain link(s) named by the drive serial - number. + number. This should be the *only* change in `ls -l /dev/disk/*/*`. + + On a system without NVMe, verify that `ls -l /dev/disk/*/*` is identical + (aside from dates, of course) before and after the upgrade to the + -proposed version. [Regression Potential] - None. + Errors in udev rules can lead to an unbootable or otherwise completely + broken system if they unintentionally break or clobber existing + /dev/disks/ symlinks. [Other Info] This patch is already included upstream and in zesty systemd. -- 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/1642903 Title: introduce disk/by-id (model_serial) symlinks for NVMe drives To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1642903/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1560162] Update Released
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 a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1560162 Title: Xenial: scaling is horribly out on xps13 install session To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1560162/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1637758] Re: lightdm greeter session not properly shut down at login
** 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1637758/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 765152] Re: spacenavd xserver permissions problem
** 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 go to: https://bugs.launchpad.net/ubuntu/+source/spacenavd/+bug/765152/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1631328] Re: ceph-osd stays blocked on Yakkety: "No block devices detected using current configuration"
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 https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Also affects: ceph (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Yakkety) Importance: Undecided Status: New ** No longer affects: systemd (Ubuntu) ** No longer affects: systemd (Ubuntu Yakkety) ** Changed in: ceph (Ubuntu Yakkety) Status: New => Fix Committed ** Tags added: verification-needed -- 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/1631328 Title: ceph-osd stays blocked on Yakkety: "No block devices detected using current configuration" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1631328/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1638153] Re: metacity crashed with signal 5 in XGetWindowAttributes()
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 https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: metacity (Ubuntu Yakkety) Status: New => Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1638153 Title: metacity crashed with signal 5 in XGetWindowAttributes() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1638153/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1640293] [NEW] Backport graphical-session{, -pre}.target to xenial
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 stay inert. The net effect is solely to ship
those two new unit files.
TEST CASE: Verify that these two new units exist in the -proposed
version:
/usr/lib/systemd/user/graphical-session-pre.target
/usr/lib/systemd/user/graphical-session.target
and that they are *not* running (systemctl --user status graphical-
session{,-pre}.target)
REGRESSION POTENTIAL: Practically zero.
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: Fix Released
** Affects: systemd (Ubuntu Xenial)
Importance: Undecided
Status: In Progress
** Also affects: systemd (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu)
Status: New => 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/1640293
Title:
Backport graphical-session{,-pre}.target to xenial
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1640293/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1638301] Re: systemctl start auto-completion shows error
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: systemctl start auto-completion shows error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1638301/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1639440] Re: [desktop] apps don't start, missing logs
** 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 bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1639440/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1638836] Re: resolv.conf for resolved stub server should have a comment how to see the actual servers
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 Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1638836 Title: resolv.conf for resolved stub server should have a comment how to see the actual servers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1638836/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1638836] [NEW] resolv.conf for resolved stub server should have a comment how to see the actual servers
Public bug reported: resolv.conf currently just has nameserver 127.0.0.53 with resolved (its local stub resolver). We should have an extra comment on top of that that says # systemd-resolved stub resolver; run "systemd-resolve --status" to see the actual name servers ** Affects: 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 => ubuntu-16.11 ** 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/1638836 Title: resolv.conf for resolved stub server should have a comment how to see the actual servers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1638836/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1636912] Re: systemd-networkd runs too late for cloud-init.service (net)
** 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 member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1636912 Title: systemd-networkd runs too late for cloud-init.service (net) To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1636912/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1636912] Re: systemd-networkd runs too late for cloud-init.service (net)
The "networkd after D-Bus" ordering was introduced in https://github.com/systemd/systemd/commit/1346b1f038 and later refined in https://github.com/systemd/systemd/commit/bcbca8291f . So with the latter, removing this ordering would break the "UseHostname: yes" flag (when you receive/set your host name from what DHCP gives you), i. e. it would silently not work. We don't use that feature in the distro itself, but it would be a shame to break it for everyone even when cloud-init is not involved at all. So this at least gives us a quick way out for 16.04 -- we can simply drop the "After=dbus.service" from systemd-networkd.service without much trouble, but for devel I'd at least discuss this with upstream. ** Also affects: cloud-init (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Xenial) Importance: 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: Martin Pitt (pitti) => (unassigned) -- 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/1636912 Title: systemd-networkd runs too late for cloud-init.service (net) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1636912/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1636912] Re: systemd-networkd runs too late for cloud-init.service (net)
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 After=systemd-networkd.service. I also suggest to replace the "Requires=networking.service" with "After=networking.service" as ifupdown is not mandatory any more. However, due to networkd's After=dbus.service this wouldn't work yet, as dbus.service runs in late boot -- I proposed/tried to change this, but it's not ready for that (bug 1629797, https://bugs.freedesktop.org/show_bug.cgi?id=98254). networkd can run without D-Bus in principle, but if that is not running yet but dbus.socket is we'll run into deadlocks again -- and if we start it before we need to teach it to connect to D-Bus once it becomes available. ** Bug watch added: freedesktop.org Bugzilla #98254 https://bugs.freedesktop.org/show_bug.cgi?id=98254 ** Changed in: systemd (Ubuntu) Status: New => Triaged ** Also affects: cloud-init (Ubuntu) Importance: Undecided Status: New ** Changed in: cloud-init (Ubuntu) Status: New => Triaged -- 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/1636912 Title: systemd-networkd runs too late for cloud-init.service (net) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1636912/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1635423] Re: Every 24h we see [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. in the syslog
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 affects: rsyslog (Ubuntu) Importance: Undecided Status: New ** Changed in: rsyslog (Ubuntu) Status: New => Triaged ** Changed in: rsyslog (Ubuntu) Importance: Undecided => Low -- 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/1635423 Title: Every 24h we see [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. in the syslog To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1635423/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1635270] Re: libsnapd-glib is not useful without snapd-login-service
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 Title: libsnapd-glib is not useful without snapd-login-service To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd-glib/+bug/1635270/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1631994] Update Released
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 encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1631994 Title: Update evolution to 3.22.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1631994/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1632428] Update Released
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 you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1632428 Title: SRU: Update gnome-settings-daemon to 3.22.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1632428/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1630853] Update Released
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 you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1630853 Title: [sharing]: gnome-settings-daemon crashed with SIGSEGV in gsd_sharing_manager_handle_service() To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1630853/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1635256] [NEW] [xenial] search domains in networkd do not get propagated to resolvconf
Public bug reported: Search domains specified in networkd do not get propagated to /etc/resolv.conf via resolved in xenial, as systemd-networkd-resolvconf- update.service only tells resolvconf about DNS servers. This is not an issue any more in yakkety and zesty as that uses resolved and that unit is gone. This was uncovered while working on adding nameserver support to netplan, in bug 1626617. To fully support netplan/networkd in xenial we should fix this. ** Affects: systemd (Ubuntu) Importance: Undecided Status: Invalid ** Affects: systemd (Ubuntu Xenial) Importance: 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 Progress ** Changed in: systemd (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: systemd (Ubuntu Xenial) 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/1635256 Title: [xenial] search domains in networkd do not get propagated to resolvconf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1635256/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1635171] Re: IPv6 Privacy Extensions do not work
** 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 about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1635171/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1633757] Re: Update file-roller to 3.22.1
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. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Also affects: file-roller (Ubuntu Zesty) Importance: High Status: In Progress ** Also affects: file-roller (Ubuntu Yakkety) Importance: Undecided Status: New ** Changed in: file-roller (Ubuntu Zesty) Status: In Progress => Fix Committed ** Changed in: file-roller (Ubuntu Yakkety) Status: New => Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/1633757 Title: Update file-roller to 3.22.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1633757/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1633274] Re: Systemd-networkd crashes with core dump
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: Unknown ** Changed in: systemd (Ubuntu) Status: Incomplete => Fix Committed ** Description changed: Systemd-networkd crashes with core dump, this happends in Yakkety and Xenial. The latest patch that was commited to Xenial-updates and Yakkety is the one that broke this. Everything works just fine with Xenial without latest update or Yakkety Beta 2. The log entries i see is: Oct 14 02:37:42 Router01 systemd-networkd[3402]: Assertion 't' failed at ../src/network/networkd-netdev-tunnel.c:210, function netdev_vti_fill_message_key(). Aborting. Oct 14 02:37:42 Router01 systemd[1]: systemd-networkd.service: Main process exited, code=dumped, status=6/ABRT Oct 14 02:37:42 Router01 systemd[1]: systemd-networkd.service: Unit entered failed state. Oct 14 02:37:42 Router01 systemd[1]: systemd-networkd.service: Failed with result 'core-dump'. Oct 14 02:37:42 Router01 systemd[1]: systemd-networkd.service: Service has no hold-off time, scheduling restart. Oct 14 02:37:42 Router01 systemd[1]: Stopped Network Service. Oct 14 02:37:42 Router01 systemd[1]: systemd-networkd.service: Start request repeated too quickly. Oct 14 02:37:42 Router01 systemd[1]: Failed to start Network Service. Oct 14 02:37:42 Router01 systemd[1]: Dependency failed for Wait for Network to be Configured. Oct 14 02:37:42 Router01 systemd[1]: systemd-networkd-wait-online.service: Job systemd-networkd-wait-online.service/start failed with result 'dependency'. Oct 14 02:37:42 Router01 systemd[1]: systemd-networkd.service: Unit entered failed state. Oct 14 02:37:42 Router01 systemd[1]: systemd-networkd.service: Failed with result 'start-limit-hit'. + + SRU TEST CASE: See https://github.com/systemd/systemd/issues/4371#issuecomment-253697041 + + Regression potential: Very low, this just fixes an obvious type cast in + networkd and touches no code that applies to other network interfaces. + The service manager (pid 1) and other tools are entirely unaffected. + + ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: systemd 231-9git1 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Fri Oct 14 02:39:05 2016 InstallationDate: Installed on 2016-10-13 (0 days ago) InstallationMedia: Ubuntu-Server 16.10 "Yakkety Yak" - Release amd64 (20161012.1) MachineType: Dell Inc. OptiPlex 755 ProcEnviron: - LANGUAGE=en_US:en - TERM=xterm - PATH=(custom, no user) - LANG=en_US.UTF-8 - SHELL=/bin/bash + LANGUAGE=en_US:en + TERM=xterm + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-22-generic root=/dev/mapper/hostname--vg-root ro SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/11/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A22 dmi.board.name: 0PU052 dmi.board.vendor: Dell Inc. dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA22:bd06/11/2012:svnDellInc.:pnOptiPlex755:pvr:rvnDellInc.:rn0PU052:rvr:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex 755 dmi.sys.vendor: Dell Inc. ** Also affects: systemd (Ubuntu Yakkety) Importance: Undecided Status: Fix Committed ** Also affects: systemd (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Zesty) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu Zesty) Status: New => Fix Committed ** Changed in: systemd (Ubuntu Yakkety) Status: Fix Committed => In Progress ** Changed in: systemd (Ubuntu Xenial) Status: New => In Progress -- 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/1633274 Title: Systemd-networkd crashes with core dump To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1633274/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1596378] Update Released
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 encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1596378 Title: Uses legacy /v2/snapd?q= instead of /v2/find?q= API - caused many messages in log To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1596378/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1573061] Update Released
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 encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1573061 Title: gnome-software wants to upgrade held packages To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1573061/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1574666] Update Released
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 encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1574666 Title: Slow to start when many updates available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1574666/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1626803] Update Released
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 encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1626803 Title: Search results show snaps not installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1626803/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1632964] Re: Regression: systemd does not send all queued DBus Signals when a unit gets inactive
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 Status: New ** Also affects: systemd (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Z-series) 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/1632964 Title: Regression: systemd does not send all queued DBus Signals when a unit gets inactive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1632964/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1616943] Re: Can't auth against U1 in g-s
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 testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: gnome-software (Ubuntu Yakkety) Status: In Progress => Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1616943 Title: Can't auth against U1 in g-s To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1616943/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1631994] Re: Update evolution to 3.22.1
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 https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Also affects: evolution (Ubuntu Yakkety) Importance: Low Status: In Progress ** Changed in: evolution (Ubuntu Yakkety) Status: In Progress => Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1631994 Title: Update evolution to 3.22.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1631994/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1631682] Re: epiphany crashed with signal 5 in _XEventsQueued()
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. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: webkit2gtk (Ubuntu Yakkety) Status: Triaged => Fix Committed ** Tags added: verification-needed ** No longer affects: epiphany-browser (Ubuntu Yakkety) ** No longer affects: epiphany-browser (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to epiphany-browser in Ubuntu. https://bugs.launchpad.net/bugs/1631682 Title: epiphany crashed with signal 5 in _XEventsQueued() To manage notifications about this bug go to: https://bugs.launchpad.net/epiphany-browser/+bug/1631682/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1632428] Re: SRU: Update gnome-settings-daemon to 3.22
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 this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Also affects: gnome-settings-daemon (Ubuntu Yakkety) Importance: Medium Status: In Progress ** Also affects: gnome-settings-daemon (Ubuntu Z-series) Importance: Undecided Status: New ** Changed in: gnome-settings-daemon (Ubuntu Yakkety) Status: In Progress => Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1632428 Title: SRU: Update gnome-settings-daemon to 3.22 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1632428/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1630853] Re: [sharing]: gnome-settings-daemon crashed with SIGSEGV in gsd_sharing_manager_handle_service()
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 this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Also affects: gnome-settings-daemon (Ubuntu Z-series) Importance: Undecided Status: New ** Also affects: gnome-settings-daemon (Ubuntu Yakkety) Importance: Medium Status: In Progress ** Changed in: gnome-settings-daemon (Ubuntu Yakkety) Status: In Progress => Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1630853 Title: [sharing]: gnome-settings-daemon crashed with SIGSEGV in gsd_sharing_manager_handle_service() To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1630853/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1632939] Re: xchat-gnome missing in Ubuntu 16.10
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 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830188 Importance: Unknown Status: Unknown ** Changed in: xchat-gnome (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to xchat-gnome in Ubuntu. https://bugs.launchpad.net/bugs/1632939 Title: xchat-gnome missing in Ubuntu 16.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xchat-gnome/+bug/1632939/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1631955] Re: Update e-d-s to 3.22.1
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. https://bugs.launchpad.net/bugs/1631955 Title: Update e-d-s to 3.22.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1631955/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1631980] Re: Steam not able to see network in yakkety
** 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 bug go to: https://bugs.launchpad.net/ubuntu/+source/steam/+bug/1631980/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1631955] Re: Update e-d-s to 3.22.1
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 this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Also affects: evolution-data-server (Ubuntu Yakkety) Importance: Medium Status: In Progress ** Changed in: evolution-data-server (Ubuntu Yakkety) Status: In Progress => Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1631955 Title: Update e-d-s to 3.22.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1631955/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1631241] Re: Name resolution stops working after resume from suspend
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 -- 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/1631241 Title: Name resolution stops working after resume from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1631241/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1623198] Re: Masking and then disabling dbus.service causes the system to freeze
** 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 disabling dbus.service causes the system to freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1623198/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1626466] Re: [Yakkety] suspend fail and reboot while resuming
** 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 while resuming To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1626466/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1623198] Re: Masking and then disabling dbus.service causes the system to freeze
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 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 disabling dbus.service causes the system to freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1623198/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1615230] Re: Policykit broken with latest systemd
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 subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1615230 Title: Policykit broken with latest systemd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1615230/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1627612] Re: systemctl restart xxx* does not restart inactive services
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 (Ubuntu) Status: New => Won't Fix -- 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/1627612 Title: systemctl restart xxx* does not restart inactive services To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1627612/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1630951] Re: systemd 219-7ubuntu6 ADT test failure with linux 3.19.0-70.78
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 it is :-) ** Also affects: systemd (Ubuntu Vivid) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu) Status: New => Fix Released ** Changed in: systemd (Ubuntu Vivid) Status: New => Won't Fix -- 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/1630951 Title: systemd 219-7ubuntu6 ADT test failure with linux 3.19.0-70.78 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1630951/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1626737] Re: [4.8.0-14/ppc64el regression] rmmod scsi_debug keeps causing kernel oops
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, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1626737 Title: [4.8.0-14/ppc64el regression] rmmod scsi_debug keeps causing kernel oops To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1626737/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1628778] Re: systemd-resolved: after network reconnection, DNSSEC unsigned zones treated as bogus, stop resolving
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 bug is relevant, of course, thanks for the report. There are still several known problems with DNSSEC, and thus the plan had been from the start to enable it during the development series and disable it shortly before the release (which has happened a few days ago). The point was to learn about bugs in practice. So 16.10 ships with disabled DNSSEC, which is no worse than the default "dns" nss plugin (i. e. libc itself). ** Bug watch added: github.com/systemd/systemd/issues #4175 https://github.com/systemd/systemd/issues/4175 ** Also affects: systemd via https://github.com/systemd/systemd/issues/4175 Importance: Unknown Status: Unknown ** Changed in: systemd (Ubuntu) Importance: Undecided => Medium -- 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/1628778 Title: systemd-resolved: after network reconnection, DNSSEC unsigned zones treated as bogus, stop resolving To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1628778/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1622379] Re: SRU: sin(0)/sin(0) crash the the calculator
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 testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: gnome-calculator (Ubuntu Xenial) Status: In Progress => Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-calculator in Ubuntu. https://bugs.launchpad.net/bugs/1622379 Title: SRU: sin(0)/sin(0) crash the the calculator To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-calculator/+bug/1622379/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1629797] Re: resolve service in nsswitch.conf adds 25 seconds to failed lookups before systemd-resolved is up
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) => 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/1629797 Title: resolve service in nsswitch.conf adds 25 seconds to failed lookups before systemd-resolved is up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1629797/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1630245] Re: after starting ubuntu 16.10 -- no keyboard, no mouse
** 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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1630245/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1618886] Re: unity-gtk-module.service is racy; session services don't stop if session terminates
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 a need to stop/restart in > the script since everything would be stopped by definition if you're > trying to start unity7 again. I like that idea in principle -- picking a session leader which automatically dies when X goes away would be a lot simpler indeed (and gnome-session does not do that). I picked gnome-session as the session leader because it traditionally has had that role, and it still has the API for logging out. Another point is that we want to make unity/compiz robust against crashes and provide auto-restart -- if it becomes the session leader, then the whole session will go down on any crash. So picking unity7.service in particular is a bad choice. Of course over time we want to get rid of gnome-session -- we don't need its service management any more, thus the only thing it provides is that D-Bus API for logout/user switching etc. This can/should be replaced with calls to stop units or calls to the DM, and then we should actually be able to completely drop that concept of a "session leader" (or rather, foo-session.target then *is* the leader, as we really intend). But we aren't there yet, so until then I think BindsTo=gnome-session.service is still conceptually correct IMHO. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1618886 Title: unity-gtk-module.service is racy; session services don't stop if session terminates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1618886/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1618886] Re: unity-gtk-module.service is racy; session services don't stop if session terminates
> 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 ExecStopPost is harmless). gnome-session is the session leader, so stopping it by definition means to end the current session. I now cleaned up the transaction handling to avoid having to wait for "deactivating" units after *-session.target ends (both at the top of the script to clean up lingering sessions and the end to cleanly exit without prematurely stopping X). -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1618886 Title: unity-gtk-module.service is racy; session services don't stop if session terminates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1618886/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1618886] Re: unity-gtk-module.service is racy; session services don't stop if session terminates
> 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 not work anyway. > gnome-session needs a fix to its ExecStopPost to not kill the one we just started. This is similar to waiting for "deactivating" units after *-session.target goes down. On the systemd sprint we just figured out a better scheme for this which solves that waiting, does not require this session ID tracking, and also gets rid of the manual starting of graphical-session-pre.target: Eventually we just want to declare in *-session.target that it comes After=graphical-session-pre.target and have this propagate to the dependencies (https://github.com/systemd/systemd/issues/3750). Until then we can just have a mini-generator do this for us. After we have the Requires/After =graphical-session-pre.target, then "systemctl stop graphical-session- pre.target" properly blocks until all "later" units are completely stopped. ** Bug watch added: github.com/systemd/systemd/issues #3750 https://github.com/systemd/systemd/issues/3750 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1618886 Title: unity-gtk-module.service is racy; session services don't stop if session terminates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1618886/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1628687] Re: Assertion failure when PID 1 receives a zero-length message over notify socket
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 catastrophe (you can DoS the machine as user in lots of other ways). ** Changed in: systemd (Ubuntu Xenial) Status: Fix Released => In Progress ** Changed in: systemd (Ubuntu Yakkety) Status: Fix Committed => In Progress -- 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/1628687 Title: Assertion failure when PID 1 receives a zero-length message over notify socket To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1628687/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1588230] Re: systemd-resolved uses domain limited DNS servers for all requests potentially a privacy issue
** Bug watch added: github.com/systemd/systemd/issues #3421 https://github.com/systemd/systemd/issues/3421 ** Also affects: systemd via https://github.com/systemd/systemd/issues/3421 Importance: Unknown Status: Unknown ** Changed in: systemd (Ubuntu) Milestone: None => ubuntu-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 domain limited DNS servers for all requests potentially a privacy issue To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1588230/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1628687] Re: Assertion failure when PID 1 receives a zero-length message over notify socket
** 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: Undecided => High ** Changed in: systemd (Ubuntu Yakkety) Importance: Undecided => High -- 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/1628687 Title: Assertion failure when PID 1 receives a zero-length message over notify socket To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1628687/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1627641] Re: Backport netplan to xenial
We need to backport a networkd fix: https://github.com/systemd/systemd/commit/6fc2549711 . This will clean up old addresses from interfaces when restarting networkd, so that changed netplan configuration will actually reflect reality. ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu) Status: New => Fix Released ** Changed in: systemd (Ubuntu Xenial) Importance: Undecided => High ** Changed in: systemd (Ubuntu Xenial) Status: New => In Progress ** Changed in: systemd (Ubuntu Xenial) 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/1627641 Title: Backport netplan to xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1627641/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1626737] Re: [4.8.0-14/ppc64el regression] rmmod scsi_debug keeps causing kernel oops
** 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 scsi_debug keeps causing kernel oops To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1626737/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1626651] Re: brightness keys are handled slower in Yakkety than Xenial
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) ** Changed in: policykit-1 (Ubuntu) Status: Incomplete => Triaged -- 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/1626651 Title: brightness keys are handled slower in Yakkety than Xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1626651/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1625100] Re: systemd test failure with linux 4.8.0-11.12: scsi_debug missing in ppc64el, systemd-tmpfiles crash
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 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 test failure with linux 4.8.0-11.12: scsi_debug missing in ppc64el, systemd-tmpfiles crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1625100/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1625100] Re: systemd test failure with linux 4.8.0-11.12: scsi_debug missing in ppc64el, systemd-tmpfiles crash
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: systemd test failure with linux 4.8.0-11.12: scsi_debug missing in ppc64el, systemd-tmpfiles crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1625100/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1626394] Re: 4.8 dropped CONFIG_ATA=y (breaks systemd's TEST-08-ISSUE-2730 upstream test)
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) Status: In Progress => Won't Fix ** Changed in: systemd (Ubuntu) Milestone: ubuntu-16.09 => None -- 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/1626394 Title: 4.8 dropped CONFIG_ATA=y (breaks systemd's TEST-08-ISSUE-2730 upstream test) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1626394/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1626394] [NEW] 4.8 update breaks systemd's TEST-08-ISSUE-2730 upstream test
Public bug reported: Since the kernel upgrade from 4.4 to 4.8 in yakkety, systemd's TEST-08-ISSUE-2730 upstream test now consistently fails with: + timeout --foreground 180 /usr/bin/qemu-system-x86_64 -smp 1 -net none -m 512M -nographic -kernel /boot/vmlinuz-4.8.0-14-generic -drive format=raw,cache=unsafe,file=/var/tmp/systemd-test.4jlHRw/rootdisk.img -append 'root=/dev/sda1 raid=noautodetect loglevel=2 init=/lib/systemd/systemd ro console=ttyS0 selinux=0 systemd.unified_cgroup_hierarchy=no ' warning: TCG doesn't support requested feature: CPUID.01H:ECX.vmx [bit 5] [1.491760] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) [1.492153] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.8.0-14-generic #15-Ubuntu [1.492153] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Ubuntu-1.8.2-1ubuntu1 04/01/2014 [1.492153] 0086 35700369 a8b59c24 97201dd45000 [1.492153] 97201e9afea0 a8987431 0010 97201e9afeb0 [1.492153] 97201e9afe48 35700369 97201e9afe58 97201e9afeb8 [1.492153] Call Trace: [1.492153] [] ? dump_stack+0x5c/0x78 [1.492153] [] ? panic+0xe4/0x226 [1.492153] [] ? mount_block_root+0x284/0x2c0 [1.492153] [] ? set_debug_rodata+0xc/0xc [1.492153] [] ? prepare_namespace+0x12b/0x180 [1.492153] [] ? kernel_init_freeable+0x1dd/0x1ed [1.492153] [] ? kernel_init+0xa/0x100 [1.492153] [] ? ret_from_fork+0x1f/0x40 [1.492153] [] ? rest_init+0x80/0x80 [1.492153] Kernel Offset: 0x2780 from 0x8100 (relocation range: 0x8000-0xbfff) [1.492153] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) qemu-system-x86_64: terminating on signal 15 from pid 8784 This only happens on amd64, i386 and ppc64el are fine. http://autopkgtest.ubuntu.com/packages/systemd/yakkety/amd64 I'll investigate more details, filing this for getting a reference for the britney hint. ** Affects: linux (Ubuntu) Importance: 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) Assignee: (unassigned) => Martin Pitt (pitti) ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: bot-stop-nagging ** Description changed: Since the kernel upgrade from 4.4 to 4.8 in yakkety, systemd's TEST-08-ISSUE-2730 upstream test now consistently fails with: + timeout --foreground 180 /usr/bin/qemu-system-x86_64 -smp 1 -net none -m 512M -nographic -kernel /boot/vmlinuz-4.8.0-14-generic -drive format=raw,cache=unsafe,file=/var/tmp/systemd-test.4jlHRw/rootdisk.img -append 'root=/dev/sda1 raid=noautodetect loglevel=2 init=/lib/systemd/systemd ro console=ttyS0 selinux=0 systemd.unified_cgroup_hierarchy=no ' warning: TCG doesn't support requested feature: CPUID.01H:ECX.vmx [bit 5] [1.491760] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) [1.492153] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.8.0-14-generic #15-Ubuntu [1.492153] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Ubuntu-1.8.2-1ubuntu1 04/01/2014 [1.492153] 0086 35700369 a8b59c24 97201dd45000 [1.492153] 97201e9afea0 a8987431 0010 97201e9afeb0 [1.492153] 97201e9afe48 35700369 97201e9afe58 97201e9afeb8 [1.492153] Call Trace: [1.492153] [] ? dump_stack+0x5c/0x78 [1.492153] [] ? panic+0xe4/0x226 [1.492153] [] ? mount_block_root+0x284/0x2c0 [1.492153] [] ? set_debug_rodata+0xc/0xc [1.492153] [] ? prepare_namespace+0x12b/0x180 [1.492153] [] ? kernel_init_freeable+0x1dd/0x1ed [1.492153] [] ? kernel_init+0xa/0x100 [1.492153] [] ? ret_from_fork+0x1f/0x40 [1.492153] [] ? rest_init+0x80/0x80 [1.492153] Kernel Offset: 0x2780 from 0x8100 (relocation range: 0x8000-0xbfff) [1.492153] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) qemu-system-x86_64: terminating on signal 15 from pid 8784 This only happens on amd64, i386 and ppc64el are fine. + http://autopkgtest.ubuntu.com/packages/systemd/yakkety/amd64 I'll investigate more details, filing this for getting a reference for the britney hint. ** Changed in: systemd (Ubuntu) Status: New => In Progress ** Changed in: systemd (Ubuntu) Milestone: None => ubuntu-16.09 -- 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/1626394 Title: 4.8 u
[Bug 1625584] [NEW] Removing libnss-* does not remove corresponding options
Public bug reported:
libnss-{resolve,mymachines,myhostname} automatically add/remove
themselves from /etc/nsswitch.conf on installation/removal.
But when (manually) adding NSS action specifiers, these do not get
removed along.
TEST CASE:
* Install libnss-machines. This will change the "hosts" line in
/etc/nsswitch.conf from e. g. "files dns" to "files dns mymachines".
* Edit the file to add an action specifier: "files dns mymachines
[!UNAVAIL=return]"
* Remove/purge libnss-machines.
* In current xenial (229-4ubuntu7)/yakkety (231-6) the hosts line ends up as
"files dns [!UNAVAIL=return]", i. e. the action specifier now applies to "dns"
but should have been removed.
* With the fixed version, the action specifier is completely gone.
* Re-test with installing libnss-resolve (which inserts itself before "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)
Status: In Progress
** Affects: systemd (Ubuntu Xenial)
Importance: Undecided
Status: Triaged
** Also affects: systemd (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu)
Importance: Undecided => Medium
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Martin Pitt (pitti)
** Changed in: systemd (Ubuntu)
Milestone: None => ubuntu-16.09
** Changed in: systemd (Ubuntu Xenial)
Status: New => Triaged
** Changed in: systemd (Ubuntu)
Status: New => In Progress
--
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/1625584
Title:
Removing libnss-* does not remove corresponding options
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1625584/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1615021] Re: Unable to network boot Ubuntu 16.04 installer normally on Briggs
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 and serial consoles are wrt. geometry, colors, special chars, etc. ** Changed in: debian-installer (Ubuntu Yakkety) Status: Triaged => Invalid ** Changed in: debian-installer (Ubuntu Xenial) Status: Triaged => Invalid -- 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/1615021 Title: Unable to network boot Ubuntu 16.04 installer normally on Briggs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1615021/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1547844] Re: systemd does not allow fsck to finish
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 #788050 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=788050 ** Also affects: systemd (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=788050 Importance: Unknown Status: Unknown ** Changed in: systemd (Ubuntu) Status: New => Fix Committed ** Also affects: systemd (Ubuntu Xenial) Importance: Undecided Status: New ** Summary changed: - systemd does not allow fsck to finish + systemd-fsckd does not allow fsck to finish -- 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/1547844 Title: systemd-fsckd does not allow fsck to finish To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1547844/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1624844] Re: Ubuntu 16.04 breaks boot with wrong zpool.cache
** 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1624844/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1625100] Re: systemd 231-6 ADT test failure with linux 4.8.0-11.12
** 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 4.8.0-11.12 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1625100/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1579278] Re: Keep powersave CPU frequency scaling governor for CPUs that support intel_pstate
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. https://bugs.launchpad.net/bugs/1579278 Title: Keep powersave CPU frequency scaling governor for CPUs that support intel_pstate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1579278/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1624967] Re: $TERM is not set for /etc/rc.local
$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 systemd.exec).
You can create your own unit with Standard{Output,Error}=tty and a
setterm call, of course.
** Changed in: systemd (Ubuntu)
Status: New => Invalid
--
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/1624967
Title:
$TERM is not set for /etc/rc.local
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1624967/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1620366] Re: FFe: Sync appstream 0.10.0-2 (main) from Debian unstable (main)
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) + FFe: Sync appstream 0.10.1-1 (main) from Debian unstable (main) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to appstream in Ubuntu. https://bugs.launchpad.net/bugs/1620366 Title: FFe: Sync appstream 0.10.1-1 (main) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1620366/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS
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 https://github.com/systemd/systemd/issues/3421 ** Also affects: systemd via https://github.com/systemd/systemd/issues/3421 Importance: Unknown Status: Unknown ** Changed in: systemd (Ubuntu) Status: New => Incomplete -- 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/1624317 Title: systemd-resolved breaks VPN with split-horizon DNS To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1624317/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1624406] [NEW] systemd-fsck test started to fail
Public bug reported:
http://autopkgtest.ubuntu.com/packages/s/systemd/yakkety/amd64 now often
fails with
==
FAIL: test_systemd_fsckd_with_failure (__main__.FsckdTest)
Ensure that a failing systemd-fsckd doesn't prevent system to boot
--
Traceback (most recent call last):
File
"/tmp/autopkgtest.WN0dWu/build.zlE/systemd-231/debian/tests/systemd-fsckd",
line 125, in test_systemd_fsckd_with_failure
self.assertTrue(self.was_running('plymouth-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 in: systemd (Ubuntu)
Status: New => In Progress
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Martin Pitt (pitti)
** Changed in: systemd (Ubuntu)
Importance: Undecided => High
** Changed in: systemd (Ubuntu)
Milestone: None => ubuntu-16.09
--
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/1624406
Title:
systemd-fsck test started to fail
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1624406/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1618886] Re: unity-gtk-module.service is racy; session services don't stop if session terminates
** 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. https://bugs.launchpad.net/bugs/1618886 Title: unity-gtk-module.service is racy; session services don't stop if session terminates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1618886/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
