I released 0.16.8 upstream and uploaded it to Debian unstable, from
where it should autosync into Ubuntu devel soon.
** Changed in: python-dbusmock (Ubuntu)
Status: Triaged => Fix Committed
** Changed in: python-dbusmock
Status: Fix Committed => Fix Released
--
You received this b
@Scott:
https://git.launchpad.net/postfix/commit/?h=stable/v3.1&id=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 de
Blaisorblade [2017-03-15 15:03 -]:
> Another corner case seems to be binaries linked against musl libc, since
> they do not use NSS.
Note that this is generally broken and cannot be supported, regardless of the
DNS resolver. These binaries could also not resolve winbind host names, YP,
LDAP, A
Perry, I just revisited this:
- /etc/network/if-up.d/openssh-server hack introduces a race (you run
into connection errors after bringing up a new interface as sshd stops
listening briefly while being reloaded).
- I can't seem to be able to actually reproduce that issue: I can start
a VM with n
Public bug reported:
The /etc/network/if-up.d/openssh-server hack was introduced ten years ago [1]
as a response to bug
103436. At least from today's perspective this isn't justified:
I can't seem to be able to actually reproduce that issue: I can start a
VM with no network interfaces, remove t
I filed bug 1674330 about dropping the hack.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/103436
Title:
sshd not reconfigured by /etc/network
Status in openssh package
Hey Perry,
Perry E. Metzger [2017-03-20 13:11 -0400]:
> That bug report was a decade ago.
Yeah, I know :-)
> So far as I know, this is still an issue for your users, because sshd
> does not, on its own, change its network address when one changes
> networks. I would not remove this because if yo
; Medium
** Changed in: packagekit (Ubuntu Xenial)
Status: Confirmed => In Progress
** Changed in: packagekit (Ubuntu Xenial)
Assignee: (unassigned) => Martin Pitt (pitti)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Description changed:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
packagekit. This problem was most recently seen with package version
0.8.17-4ubuntu6~gcc5.4ubuntu1.1, the problem page at
https://errors.ubuntu.com/problem/8c37a6988b890cc46b415972ef1e2ca746
I ran the description's test case and confirm that the crash is now
fixed. Furthermore, other operations like "pkcon refresh", "pkcon get-
updates", "pkcon update", and "pkcon install bash-doc" all worked fine,
as before.
** Tags removed: verification-needed verification-needed-xenial
** Tags adde
I cherry-picked the patches into the Debian packaging branch, so that on
next upload zesty can be synced again.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1647485
Title:
Fixed upstream:
https://github.com/systemd/systemd/commit/e8d23f92b50a97bb3
** Changed in: systemd (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
ht
Note: We keep DNSSEC=allow-downgrade during development to collect
feedback, but switch it off for stable releases (we did so in yakkety
and should do so again in zesty). So if you have some trouble which is
DNSSEC related, it would be good to get a debug output of resolved while
it's failing to re
Yes, there, see "man resolved.conf". But I'd recommend a separate file
to avoid changing the package-provided conffile:
sudo mkdir -p /etc/systemd/resolved.conf.d
printf "[Resolve]\nDNSSEC=no\n" | sudo tee
/etc/systemd/resolved.conf.d/no-dnssec.conf
--
You received this bug notification because
** Summary changed:
- "Failed name lookup - disconnected path"
+ /usr/lib/dovecot/dovecot-lda: "Failed name lookup - disconnected path"
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpa
This is quite simple to reproduce:
$ pkcon get-updates
Getting updates [=]
Loading cache [=]
Querying [=]
Finished [===
I confirmed that this is fixed in zesty.
** Changed in: packagekit (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to packagekit in Ubuntu.
https://bugs.launchpad.net/bugs/1689820
Tit
https://salsa.debian.org/debian/umockdev/-/commit/87b476aee2 should
hopefully help. I uploaded 0.14.2 to Debian unstable now, it should
auto-sync into Groovy soon. Thanks Dan for tackling this!
** Changed in: umockdev (Ubuntu Groovy)
Status: In Progress => Fix Committed
--
You received t
No, this won't be backported. This is a classic bug fix for stable-
updates, I'll prepare uploads soon.
** Also affects: udev (Ubuntu)
Importance: Undecided
Status: New
** Also affects: udev (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: udisks (Ubuntu Pr
I uploaded a trusty update for this to the SRU review queue. Please test
the -proposed package once it is available to verify this. Thanks!
** Changed in: systemd (Ubuntu Trusty)
Status: Triaged => In Progress
** Changed in: systemd (Ubuntu Trusty)
Assignee: Martin Pitt (pi
I uploaded a trusty update for this to the SRU review queue. Please test
the -proposed package once it is available to verify this, as it's not
really practical to write down a test case which works independently of
this affected hardware. Thanks!
** Changed in: systemd (Ubuntu Trusty)
Stat
** Description changed:
As per JEDEC 4.5 spec for eMMC devices,
There is a new partitions as part of eMMC storage devices it self. (Further
details please refer eMMC spec)
*In Linux Kernel@ 3.10.33, mmc driver has created a new partitions with
"mmcblkXrpmb" if device expresses it suppo
** Changed in: systemd-shim (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd-shim in Ubuntu.
https://bugs.launchpad.net/bugs/1359439
Title:
[7.287663] systemd-logind[1057]:
** Changed in: ubuntu-drivers-common (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1386257
Title:
intel-microcode
Adding Mir task, mirscreencast shouldn't completely fail on an invalid
locale.
** Changed in: mir (Ubuntu)
Status: New => Triaged
** Changed in: autopkgtest (Ubuntu)
Importance: Undecided => Low
** Changed in: autopkgtest (Ubuntu)
Assignee: (unassigned) => Mart
Ah, this is our old friend https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=391964 again: It's a mis-feature that ssh (which
runs behind phablet-shell) is blindly transfering the host's locale to
the remote target even if the target doesn't support that locale.
We can work around that in adt-run
5):bd07/09/2013:svnLENOVO:pn2324CTO:pvrThinkPadX230:rvnLENOVO:rn2324CTO:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 2324CTO
dmi.product.version: ThinkPad X230
dmi.sys.vendor: LENOVO
** Affects: systemd (Ubuntu)
Importance: Critical
Assignee: Martin Pitt (pitti)
** Description changed:
Since yesterday, systemd does not boot properly any more. It takes very
long, ends up in an X failsafe session, and eventually you just get a
getty on VT1.
+ Downgrading libpam-systemd libsystemd0 systemd systemd-sysv to
+ https://launchpad.net/ubuntu/+source/syste
Notekeeping:
- installing self-built .debs: boot ok
- reinstalling ubuntu debs: boot fail
- Removing persistant journal (sudo rm -r /var/log/journal) with the ubuntu
binaries: boot ok
- rebooting a few times with re-enabling persistant journal: boot ok
- QEMU with enabling persistant journal and
I can reproduce this quite reliably with:
sudo rm -r /var/log/journal
sudo mkdir /var/log/journal
sudo apt-get install --reinstall systemd
I now managed to reproduce the hang in a VM as well, with these
commands.
--
You received this bug notification because you are a member of Ubuntu
Tou
For the record, the chroot is done here:
# Work around absolute symlinks
if [ -d "${rootmnt}" ] && [ -h "${rootmnt}${checktarget}" ]; then
case $(readlink "${rootmnt}${checktarget}") in /*)
checktarget="$(chroot ${rootmnt} readlink
${checkta
anged in: initramfs-tools (Ubuntu)
Status: Incomplete => In Progress
** Changed in: initramfs-tools (Ubuntu)
Assignee: (unassigned) => Martin Pitt (pitti)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to init
FTR, that happens if busybox-static is *not* installed; that's in
ubuntu-standard, which explains why most people have it.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/b
** Changed in: systemd (Ubuntu)
Status: New => Triaged
** Changed in: systemd (Ubuntu)
Importance: Undecided => Medium
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Martin Pitt (pitti)
--
You received this bug notification because you are a member of Ubu
I continued to bisect binaries (/lib/systemd/{systemd,systemd-logind
,systemd-journald,systemd-fsck,systemd-fsckd}.
I never got a hang with 219 + journald from 218, and I did get a hang
with 218 + journald from 219, which indicates that this is related to
journald. Didier confirmed the latter hang
** Changed in: autopkgtest (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1423359
Title:
taking screenshots with mirscreencast
This is an automated reproducer in the form of an autopkgtest. You can
call it like this:
adt-run --built-tree ./systemd-bootsmoke --- qemu /srv/vm/adt-
pid1.img
This reboots the VM up to 20 times, and check for stuck jobs or non-
running polkit on each iteration. You can also test with modifi
I'm running "git bisect start v219 v218 -- src/shared src/journal" on
upstream trunk now (some 220 commits to test), using the above
autopkgtest. I don't use git bisect run, as the autopkgtest sometimes
fails with exit code 16 (testbed setup); in those cases it should be re-
run to either succeed,
Bisect run finished. The culprit is
http://cgit.freedesktop.org/systemd/systemd/commit/?id=13790add4bf64
This reverts cleanly against master, and running 219 with journald with
that commit reverted runs stable.
--
You received this bug notification because you are a member of Ubuntu
Touch see
This is an improved git bisect script which is now robust against
transient testbed failures and "make" build failures. This is now
suitable for a fully automated "git bisect run ./systemd-bisect-run.sh",
and was able to identify the regression in < 2 h fully noninteractively.
This is now mostly o
autopkgtest committed: http://anonscm.debian.org/cgit/pkg-
systemd/systemd.git/commit/?h=experimental&id=75f84790871
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1423811
T
** Changed in: systemd (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1423811
Title:
219-1ubuntu1 regression: boot han
** Bug watch added: Debian Bug tracker #778970
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778970
** Also affects: systemd (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778970
Importance: Unknown
Status: Unknown
--
You received this bug notification because y
*** This bug is a duplicate of bug 777224 ***
https://bugs.launchpad.net/bugs/777224
** This bug has been marked a duplicate of bug 777224
package ureadahead 0.100.0-11 failed to install/upgrade: subprocess
installed post-installation script returned error exit status 1
--
You received t
** Summary changed:
- package ureadahead 0.100.0-11 failed to install/upgrade: subproces installed
post-installation script gaf een foutwaarde 1 terug
+ package ureadahead 0.100.0-11 failed to install/upgrade: subprocess installed
post-installation script returned error exit status 1
--
You re
We really shouldn't start ureadahead on package install/upgrades.
** Changed in: ureadahead (Ubuntu)
Status: Confirmed => Triaged
** Changed in: ureadahead (Ubuntu)
Assignee: (unassigned) => Martin Pitt (pitti)
** Changed in: ureadahead (Ubuntu)
Importance: Undecide
That patch looks okay for an utopic SRU. Thanks!
** Also affects: systemd (Ubuntu Utopic)
Importance: Undecided
Status: New
** Also affects: systemd-shim (Ubuntu Utopic)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu Utopic)
Status: New => Triaged
**
** Changed in: ureadahead (Ubuntu)
Status: Triaged => In Progress
** Changed in: ureadahead (Ubuntu)
Importance: Medium => High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ureadahead in Ubuntu.
https://bugs.laun
** Changed in: ureadahead (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ureadahead in Ubuntu.
https://bugs.launchpad.net/bugs/777224
Title:
package ureadahead 0.100.0-1
** Changed in: initramfs-tools (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1421117
Title:
fails to boot wit
/lib/systemd/systemd-bootchart --help shows the default value, which is
clearly wrong:
-i, --init=PATH Path to init executable [/lib/x86_64-linux-
gnu/systemd/systemd]
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to s
I fixed this upstream:
http://cgit.freedesktop.org/systemd/systemd/commit/?id=a804d84
** Changed in: systemd (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
** Also affects: systemd
Importance: Undecided
Status: New
** Changed in: systemd
Assignee: (unassigned) => Martin Pitt (pitti)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
ht
Hello Simon,
simon thunder [2015-02-25 5:47 -]:
> I'm a Linux beginner and I'd like to know how to install the patch. Can
> anybody tell me how? Thank you!
See comment #42 in this bug report. It's documented here:
https://wiki.ubuntu.com/Testing/EnableProposed
Thanks!
--
You received this
** Changed in: systemd (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1424992
Title:
files in /tmp not being cleared on boot
St
: (unassigned) => Martin Pitt (pitti)
** Changed in: systemd (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1424992
Title:
fi
** Summary changed:
- taking screenshots with mirscreencast fails if locale is not C.
+ taking screenshots with mirscreencast fails if env locale does not exist
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
h
MitraX [2015-02-25 7:57 -]:
> Is there any way to implement the patch in Ubuntu 14.10 Utopic Unicorn?
Yes, we can SRU it there, too.
> Or a new bug should be reported separately for this version?
Pretty please no, that only confuses matters for everyone involved.
Martin
--
You received t
Fixed in packaging git, and I wrote an autopkgtest to check /tmp and
/var/tmp cleanup.
** Changed in: systemd (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubu
Another blocker: bug 1425575
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1153671
Title:
Port to python3-launchpadlib
Status in apport package in Ubuntu:
In Progress
S
Another blocker: bug 1425609
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1153671
Title:
Port to python3-launchpadlib
Status in apport package in Ubuntu:
In Progress
S
Next blocker: bug 1425627
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1153671
Title:
Port to python3-launchpadlib
Status in apport package in Ubuntu:
In Progress
Stat
** Tags removed: verification-needed
** Tags added: verification-done-trusty
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1333140
Title:
Fix udev rules to consider mmc r
I'm getting a similar (perhaps/hopefully the same) hang if I do this:
systemctl mask --runtime systemd-journald systemd-logind; systemctl stop
systemd-journald systemd-logind
SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-journald
# restart 5 times
SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd
I don't get the hang with the reproducer in comment 11 on Fedora 21 with
systemd 219 and dbus 1.8.16 from rawhide.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1423811
Tit
Fixed in trunk: http://bazaar.launchpad.net/~apport-
hackers/apport/trunk/revision/2917
** Changed in: apport (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubun
** Changed in: apport (Ubuntu)
Status: In Progress => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1153671
Title:
Port to python3-launchpadlib
Status in a
"sudo service network-manager restart" helps, this recovers the 3G
connection within a few secs.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1418077
Title:
NM f
Normally it looks like this:
$ ip route
default via 10.51.99.33 dev rmnet_usb0 proto static metric 1024
10.51.99.33 dev rmnet_usb0 proto static scope link metric 1024
100.148.199.0/24 dev rmnet_usb0 proto kernel scope link src 10.51.99.34
But after this happens, "ip route" is completel
I see a similar effect on mako vivid-proposed. Sometimes after doing
nothing for a few hours I pick up the phone and find it having no data
connection at all, without any action from me. This could potentially be
because of short 3G network outages. I can confirm that switching from
3G to 2G in the
Fixed upstream in http://bazaar.launchpad.net/~apport-
hackers/apport/trunk/revision/2918, thanks Chad!
** Changed in: apport
Status: New => Fix Released
** Also affects: apport (Ubuntu)
Importance: Undecided
Status: New
** Changed in: apport (Ubuntu)
Status: New => Fix C
Please be more specific what yo umean by "crashes on login". Do you have
some Apport crash reports which you could upload? If nothing actually
crashed, but you just can't see anything on the screen, can you ssh into
the VM and retrieve dmesg, /var/log/Xorg.0.log?
** Package changed: util-linux (Ub
Thanks Scott! This works fine under Ubuntu, but I figure that's due to
having a different icon theme. With your fix it still works as before
under Unity, so I merged it.
** Changed in: apport (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a mem
Assignee: (unassigned) => Martin Pitt (pitti)
** Also affects: console-setup (Ubuntu)
Importance: Undecided
Status: New
** Changed in: console-setup (Ubuntu)
Status: New => In Progress
** Changed in: console-setup (Ubuntu)
Assignee: (unassigned) => Martin Pit
First test package available in
https://launchpad.net/~pitti/+archive/ubuntu/systemd
I added the current upstream units as a big patch, and then added separate
patches for our changes, so that it's easier to see what we changed; these also
become easier to upstream that way.
TODO:
- debian/nfs
pitti2 uploaded to PPA now. This fixes the umount hang, and drops the
manual modprobing. The modules get loaded automatically without that
too. Neither upstream nor the Fedora package do any extra modprobing.
** Changed in: console-setup (Ubuntu)
Milestone: None => ubuntu-15.03
--
You receiv
debdiff for review: http://people.canonical.com/~pitti/tmp/nfs-
utils.systemd.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1312976
Title:
Make NFS client/server
nfs-utils - 1:1.2.8-9ubuntu2pitti3 uploaded to PPA. This merely cleans
up the changelog a bit and adds a proper "Forwarded:" reference to an
upstreamable patch.
I now tested this on both a single machine as well as two separate VMs
(one server, one client), with some /mnt/* mounts as well as /home
** Changed in: nfs-utils (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1312976
Title:
Make NFS client/server work un
Public bug reported:
As per https://blueprints.launchpad.net/ubuntu/+spec/core-1411-systemd-
migration we aimed for switching the system (not session) init from
upstart to systemd this cycle. As this was by and large a 1.2 man show,
this took a little longer. One of the remaining blockers for swit
You are still running upstart. However, it'd be good to check this under
systemd as well. Under either init system, a tmpfs should be mounted on
/tmp/ if the disk is full.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to system
Under upstart, /etc/init/mounted-tmp.conf is supposed to do that tmpfs
mounting, but there's a chance that it's failing on trying to write to
/var or another directory. So we should test this under both.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded package
Thansk! Committed with changelog entry and a few pep8 fixes.
** Changed in: systemd (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpa
** No longer affects: console-setup (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1312976
Title:
Make NFS client/server work under systemd
Status in apparmor p
Thanks Didier! Some remarks:
+ * Add systemd-emergency-tmpfs to force tmp.mount (tmpfs) enablement if the
... "generator"?
Also, s/enablement/startup/? (We don't permanently enable the unit, that could
be misleading)
+avail=`df -BM -P /tmp/ | awk 'NR==2 { print substr($4, 0, length($4)-1)
}'`
** Also affects: console-setup (Ubuntu)
Importance: Undecided
Status: New
** Changed in: console-setup (Ubuntu)
Assignee: (unassigned) => Martin Pitt (pitti)
** Changed in: console-setup (Ubuntu)
Status: New => In Progress
--
You received this bug notification becau
https://launchpad.net/ubuntu/+source/ubuntu-touch-meta/1.217
** Changed in: ubuntu-touch-meta (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-touch-meta in
Ubuntu.
https://bu
I can't approve the FFE, but this looks good to me. I merged the port
into the upstream branch now. Please note that I rejected the vivid
upload as that didn't update the current "python3-pykde4" dependency.
python-pyqt5 doesn't seem to be sufficient, it doesn't provide
QApplication; and you wanted
Fran, the first patch looks promising. The second patch looks unrelated,
but cherry-picking it can't hurt anyway I guess. If you can test this,
please do (I just returned from holidays and have a giant backlog).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
This is the right fix (together with
https://launchpad.net/ubuntu/+source/systemd/219-4ubuntu8), thanks
Scott!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1432821
Title:
Thanks Scott for fixing this! However, this is awkward to have in
systemd: it meddles with ifupdown's and open-iscsi's internals and has
open-iscsi specific knowledge which really belongs into open-iscsi
itself. I. e. open-iscsi should ship the counterpart of debian/open-
iscsi.iscsi-network-interf
Can you please try with current vivid? There were some ifup@ fixes
recently.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1430675
Title:
fails to set up a bridged networ
You can build that using libsystemd-login-dev, they provide
compatibility shims for the obsolete libsystemd-logind0 (and similar)
libraries.
** Changed in: systemd (Ubuntu)
Status: New => Won't Fix
** Changed in: systemd (Ubuntu)
Status: Won't Fix => Invalid
--
You received this b
This patch is in vivid.
** Changed in: util-linux (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1393542
Title:
[SRU]
Sponsored the utopic fix with a better changelog. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1393542
Title:
[SRU] exfat not detected by blkid
Status in uti
*** This bug is a duplicate of bug 1431523 ***
https://bugs.launchpad.net/bugs/1431523
** This bug has been marked a duplicate of bug 1431523
zfs not automounting after upgrading from upstart to systemd
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
** Also affects: wpa (Ubuntu)
Importance: Undecided
Status: New
** Changed in: wpa (Ubuntu)
Status: New => Triaged
** Bug watch added: Debian Bug tracker #780552
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=780552
** Also affects: wpa (Debian) via
http://bugs.debian.or
I think this overcomplicates things a lot. I see three options here:
1) My impression is that we don't actually care about persistant
interface names on the phone. Therefore, phone image builds could just
create/ship an empty /etc/udev/rules.d/75-persistent-net-generator.rules
which will disable
> > create/ship an empty /etc/udev/rules.d/75-persistent-net-generator.rules
> This is doable to me.
OK, that might be the quickest/safest way for now?
> net.ifnames depends on systemd
No, that's udev only. It should work just fine under upstart too. As
that's the long-term goal, doing that on t
Giuseppe, you can run "env DEB_BUILD_OPTIONS=nocheck debuild ..." (or
sbuild, etc.) to disable running the tests. (The test works fine in a
clean schroot, not sure what's wrong in your environment)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, whi
701 - 800 of 4146 matches
Mail list logo
