Fixed in packaging git.
** 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.
https://bugs.launchpad.net/bugs/1357782
Title:
udev(7) is
The systemd side of this is fixed in utopic, closing. The kernel (and
main) side keeps open.
** Changed in: systemd (Ubuntu)
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd
This is fixed in utopic.
** Changed in: systemd (Ubuntu)
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1247676
Title:
*** This bug is a duplicate of bug 1301846 ***
https://bugs.launchpad.net/bugs/1301846
** This bug has been marked a duplicate of bug 1301846
loginctl crashed with SIGABRT
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
FTR, I tested today's rtm-proposed image (r30, mako), and the menu icons
are still overlapping and don't look any different from when I reported
the bug.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gallery-app in Ubuntu.
Public bug reported:
While fixing autopkgtest for tight umasks
(http://bugs.debian.org/761049) I noticed that LXC fails under tight
umasks, too:
$ sudo -i
# umask 077
# lxc-start-ephemeral --keep-data -o adt-utopic
[... boots ... ]
adt-utopic-9x0b7tw_ login: ubuntu
Password:
Welcome to Ubuntu
** Description changed:
While fixing autopkgtest for tight umasks
(http://bugs.debian.org/761049) I noticed that LXC fails under tight
umasks, too:
$ sudo -i
# umask 077
# lxc-start-ephemeral --keep-data -o adt-utopic
[... boots ... ]
adt-utopic-9x0b7tw_ login: ubuntu
-
BTW, I have added a workaround to autopkgtest, so this isn't a blocker
for me.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1367730
Title:
container root directory has
** Changed in: policykit-desktop-privileges (Ubuntu)
Status: Confirmed = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to policykit-desktop-
privileges in Ubuntu.
https://bugs.launchpad.net/bugs/1356326
Public bug reported:
Recent phablet-shell (r307) gives a lot of error messages:
$ ~/ubuntu/phablet-tools/phablet-shell
/home/martin/ubuntu/phablet-tools/phablet-shell: 72: [: /bin/bash:: unexpected
operator
/bin/bash: /root/.bash_profile: Permission denied
/home/martin/.ssh/known_hosts
Ah indeed. But this has worked by sheer accident, not by design. udev
rules aren't supposed for this, and if they write any files it should be
into /dev/ or /run. They can race in both ways: before the file system
becomes available, or they run too late when the display manager is
already starting
Oh, and finally: Depending on what you do in these conf files, it might
be even easier, better, and completely race free to move these to
xorg.conf.d snippets (see man xorg.conf.d) with the MatchDevice*
clauses.
--
You received this bug notification because you are a member of Ubuntu
Touch
Utopic fix committed to packaging git: http://anonscm.debian.org/cgit
/pkg-systemd/systemd.git/commit/?id=37f4673cf
** Changed in: systemd (Ubuntu)
Status: In Progress = Fix Committed
** Also affects: systemd (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in:
I suppose you at least want this for 14.04 LTS. Do you still need this
for 12.04 LTS too, or is 14.04 sufficient?
** Package changed: udev (Ubuntu) = systemd (Ubuntu)
** Changed in: systemd (Ubuntu)
Status: New = In Progress
--
You received this bug notification because you are a member
Utopic fix committed to git, thanks! I keep this open for trusty, but as
it's neither a data loss nor critical bug and just a cosmetical corner
case I keep it as low importance.
You say since 3.13.0-16.36 which is trusty -- i. e. precise's kernel
still has it as a module? So it seems to me that
@Luis: That version
(http://launchpadlibrarian.net/182673897/systemd_204-5ubuntu20.4_204-5ubuntu20.5.diff.gz)
does not change anything related to this bug at all, so this sounds like
a race condition and pure coincidence. However, you posted this to both
here and bug 1309025 and both are already
@Luis: That version
(http://launchpadlibrarian.net/182673897/systemd_204-5ubuntu20.4_204-5ubuntu20.5.diff.gz)
does not change anything related to this bug at all, so this sounds like
a race condition and pure coincidence. However, you posted this to both
here and bug 1302264 and both are already
I'm still not fully convinced about the SRUs -- this might have a
potential to break existing setups if they run custom kernels? It's ok
to add the expectancy to build in vesafb for a new release (utopic), but
not for existing stables?
Or is it impossible to build vesafb as a module now?
--
You
Ah right, that's the backported trusty kernels I figure (12.04.4 or
later).
** Changed in: udev (Ubuntu Precise)
Status: Incomplete = Triaged
** Changed in: udev (Ubuntu Precise)
Importance: Undecided = Low
--
You received this bug notification because you are a member of Ubuntu
Trusty had vesafb build in the kernel from the very first release, so
I believe the assumption is safe here.
Well no, one could still run a self-built kernel.
So I think for an SRU it would be safer to not drop the script, but
instead do some 2/dev/null to quiesce the error.
--
You received
do some 2/dev/null to quiesce the error.
or if that's not possible (because it's the kernel who spits out errors,
but that's unlikely), it could also do if modinfo vesafb /dev/null
21; then modprobe -q vesafb; fi
--
You received this bug notification because you are a member of Ubuntu
Touch
Right, protecting this with || true sounds perfectly fine and safe for
an SRU.
--
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/1367241
Title:
Incorrect
I sponsored these with changing the changelog to
* udev-fallback-graphics.conf: Avoid failure if vesafb module is compiled
in. (LP: #1367241).
as removed the script isn't true with those.
** Changed in: systemd (Ubuntu Trusty)
Status: Triaged = In Progress
** Changed in: udev
Thanks Brian for spotting this! Closing bug then.
** Changed in: systemd (Ubuntu)
Status: New = Invalid
** Summary changed:
- package libpam-systemd 204-5ubuntu20.5 failed to install/upgrade: subprocess
new pre-removal script returned error exit status 102
+ package libpam-systemd
** Changed in: unity
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1351306
Title:
Cannot uninstall upstart and install
** Summary changed:
- systemd boot hangs - sysv:networking - ifup - tinc
+ tinc needs systemd integration
** No longer affects: systemd (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Public bug reported:
Installing systemd-sysv replaces upstart's reboot, poweroff and
friends. systemd's binaries currently don't know how to talk to upstart
to forward the request to upstart. This breaks a transition to systemd
as default init which doesn't just change the boot= kernel parameter
** Changed in: systemd (Ubuntu)
Status: Triaged = In Progress
** Changed in: systemd (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 systemd in Ubuntu.
https
Not pretty, but working: http://anonscm.debian.org/cgit/pkg-
systemd/systemd.git/commit/?h=ubuntuid=587c487a33e711b
** Changed in: systemd (Ubuntu)
Status: In Progress = Fix Committed
** Changed in: systemd (Ubuntu)
Milestone: None = ubuntu-14.10
--
You received this bug
Sorry, wrong package. You need to install udev, not systemd.
--
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/1359933
Title:
[Hyper-V] hyperv_fb kernel module is not
Fix committed to Debian and Ubuntu systemd packaging branches. I'll do
an utopic upload now.
** Changed in: systemd (Ubuntu Utopic)
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
I have no idea what that file is, but reading it seems quite save. So
just add
/var/cache/samba/*.tdb r,
where the other samba related permissions are.
** Also affects: samba (Ubuntu)
Importance: Undecided
Status: New
** Changed in: cups (Ubuntu)
Status: New = Triaged
** No
The bits about gendache.tdb are covered by bug 1371097. I don't know
what the denied_mask=send signal=term bits are about, I suggest asking
the apparmor developers (jdstrand and tyhicks).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Theodotos Andreou [2014-09-19 11:11 -]:
Restarted the computer and I still get:
That might not be enough. Can you please try
sudo /etc/init.d/apparmor teardown
sudo /etc/init.d/apparmor start
after the profile update (well, you already made that)? That should
rebuild the binary
Ben, I uploaded both of them. The previous systemd version is still in
trusty-proposed, so accepting that will still take a few days. The
precise one can be reviewed/accepted by the SRU team right now.
** Also affects: udev (Ubuntu)
Importance: Undecided
Status: New
** No longer
** Changed in: ubuntu-ui-toolkit (Ubuntu)
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1346650
Title:
ubuntu-minimal depends on upstart and ifupdown, so supposedly you
removed that. This is really not a supported configuration.
As for upstart: Debian has a new essential package init which depends
on systemd-sysv | upstart | sysvinit. We could decide to adopt that.
Moving to init-system-helpers
First of all, for the removal of upstart, one must install package
systemd-sysv.
Right, that will switch the default init to systemd. If you want to
experiment with that, you can do either that or boot with
init=/bin/systemd (you don't need both).
This is indeed not officially supported yet as
Clint Byrum [2014-09-23 7:15 -]:
Doesn't ifupdown still bring up lo?
Systemd (or perhaps something else too), does that as well. You can
install systemd-sysv, purge ifupdown and upstart, and lo will be up.
--
You received this bug notification because you are a member of Ubuntu
Touch
I don't have such a device, so I'm afraid I either need someone with
such a device to debug this, or get ssh access to an affected machine.
As a first step, please install valgrind, and run this:
sudo killall upowerd; sudo valgrind --leak-check=full --
/usr/lib/upower/upowerd -v 21 | tee
Many thanks for the fast fix! Much appreciated to unbreak the emulator.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1349444
Title:
[emulator] unity8 fails to start
This doesn't yet seem to be in image 157, and image 160 crashes at boot
due to bug 1349709.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1349444
Title:
[emulator] unity8
I confirm that upgrading image 157 to current utopic fixes that problem.
I still happens after rebooting again (forcefully).
In general, unity and the launcher are still very unstable. E. g. after
launching calculator there is no way to get out of it again -- the
launcher (swipe from left edge)
Fixed in trunk r2821, thanks Brian.
** 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 Ubuntu.
https://bugs.launchpad.net/bugs/1329520
Title:
Fixed in trunk r2825.
** Changed in: apport (Ubuntu)
Status: New = Fix Committed
--
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/1349579
Title:
whoopsie-upload-all
I believe this has been sufficiently tested now. We are out of
traincon-0 for the touch images too, so let's unleash this.
** Changed in: systemd (Ubuntu)
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
Fixed upstream now:
http://cgit.freedesktop.org/systemd/systemd/commit/?id=1f6d36f
Thanks Wang!
** Package changed: linux (Ubuntu) = systemd (Ubuntu)
** Changed in: systemd (Ubuntu)
Status: Triaged = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Public bug reported:
The current autopilot rule does that:
# Creates autopilot group specific access to /dev/uinput
KERNEL==uinput, SUBSYSTEM==misc, SYMLINK=autopilot-uinput,
GROUP=autopilot, MODE=0660
But on our Ubuntu Touch images, at least on mako, we have other rules
which also change the
** Changed in: apport (Ubuntu)
Assignee: Martin Pitt (pitti) = (unassigned)
--
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/359810
Title:
apport-collect won't submit
** Changed in: apport (Ubuntu)
Assignee: Martin Pitt (pitti) = (unassigned)
--
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/957177
Title:
support multiple crashdbs
** Changed in: ufw (Ubuntu)
Status: Triaged = In Progress
** Changed in: ufw (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 ufw in Ubuntu.
https
This debdiff does both: It consistently installs sysvinit/upstart
scripts on Debian and Ubuntu, and also adds a simple systemd service
file which is equivalent to the upstart job. Tested under both upstart
and systemd (I didn't test the sysvinit script).
** Patch added: debdiff
Created upstream pull request: https://github.com/lxc/lxc/pull/285
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1325468
Title:
[systemd] container startup fails with
Fixed in Debian experimental branch: http://anonscm.debian.org/gitweb/?p
=pkg-systemd/systemd.git;a=commitdiff;h=ca2a7946
** Changed in: systemd (Ubuntu)
Status: Confirmed = Fix Committed
** Summary changed:
- systemd does not honor Ubuntu default mountpoints (as listed in
This is fixed in the proposed 2.88dsf-53.2ubuntu1 merge.
** Changed in: sysvinit (Ubuntu)
Status: Confirmed = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sysvinit in Ubuntu.
We don't use startpar in Ubuntu and don't plan to. It also does not get
along with upstart Tasks. It's probably not worth trying to fix it in
Ubuntu; we disabled its usage in sysvinit.
startpar got split out into its own package in Debian/utopic-proposed,
and will disappear from sysvinit as soon
This landed in trunk now.
** Changed in: autopilot (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 autopilot in Ubuntu.
https://bugs.launchpad.net/bugs/1350263
Title:
Patches sent to upstream ML: https://lists.linuxcontainers.org/pipermail
/lxc-devel/2014-July/009889.html
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1312532
Title:
in: rsyslog (Ubuntu)
Assignee: Dimitri John Ledkov (xnox) = Martin Pitt (pitti)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
https://bugs.launchpad.net/bugs/1331891
Title:
[systemd] /etc/logrotate.d
So it seems the originally reported problem was fixed. There's a
multitude of insufficiently described and hard to understand other
problems here. If you have particular issues under systemd, can you
please report one bug for each issue with a precise description, and
include the output of
Removing systemd-boot tag. Upgrades from trusty necessarily use upstart,
so the hang that you saw wasn't a systemd boot problem.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Can you please install evtest, run sudo evtest, then press the
brightness keys and copypaste the entire output? Please annotate it so
that I can see which line of output belongs to which particular key.
After that, please give me the output of
grep -r . /sys/class/dmi/id/
Thanks!
** Changed
*** This bug is a duplicate of bug 1350947 ***
https://bugs.launchpad.net/bugs/1350947
Unfortunately that previous commit isn't sufficient yet; I'm not sure
how it worked for me when I tested it, but bug 1350947 is in the way.
I'm making this a dupe and add an LXC task, that's easier.
**
*** This bug is a duplicate of bug 1350947 ***
https://bugs.launchpad.net/bugs/1350947
** This bug is no longer a duplicate of bug 1325468
[systemd] container startup fails with AppArmor
** This bug has been marked a duplicate of bug 1350947
apparmor: no working rule to allow making a
** Also affects: krb5 (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: gcc-4.8 (Ubuntu Trusty)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gcc-4.8
** Changed in: gobject-introspection (Ubuntu)
Status: Triaged = Fix Committed
** Changed in: gjs (Ubuntu)
Status: Triaged = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gobject-introspection in
SRUs uploaded as well. Unsubscribing sponsors, please re-subscribe when
there's anything further to sponsor (like typelib rebuilds). Thanks!
** Changed in: gjs (Ubuntu Trusty)
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch
Oh, and please add SRU information to the description (test case etc.)
** Changed in: gobject-introspection (Ubuntu Trusty)
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
** Changed in: ubuntu-touch-meta (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-touch-meta in
Ubuntu.
https://bugs.launchpad.net/bugs/1346766
Title:
Chinese in
I have an unprivileged container setup in my test VM now, and they
continue to work with 208. However, LXC under systemd currently requires
some work (bug 1312532 and bug 1350947), so this should land first so
that system-level containers work under systemd. Then I'll look into the
cgroups issue.
This bug was fixed in the package harfbuzz - 0.9.33-1
Sponsored for أحمد المحمودي (Ahmed El-Mahmoudy) (aelmahmoudy)
---
harfbuzz (0.9.33-1) unstable; urgency=medium
* New upstream release.
* Upload to unstable.
* Added unbreak_abi.diff patch to Re-add hb_version_check to
filesystem doesn't have requested /bin/systemd
and then a kernel panic.
** Affects: initramfs-tools (Ubuntu)
Importance: Undecided
Assignee: Martin Pitt (pitti)
Status: In Progress
** Changed in: initramfs-tools (Ubuntu)
Assignee: (unassigned) = Martin Pitt (pitti)
** Changed
** Tags added: systemd-boot
--
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/1351295
Title:
Boot fails if /sbin/init is an absolute symlink
Status in
This is coming from init line284:
case $(readlink ${rootmnt}${checktarget}) in /*)
That's the readlink that isn't found (not the chrooted one in the next
line). I added a few debugging steps, and type readlink says readlink
is readlink. I cannot reproduce this in break=bottom,
Moreover, this obviously works in Debian, but between Ubuntu's and
Debian's initramfs initd there is no obvious difference for readlink.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
** Changed in: plymouth (Ubuntu)
Status: New = Fix Committed
** Changed in: plymouth (Ubuntu)
Assignee: (unassigned) = Martin Pitt (pitti)
** Also affects: avahi (Ubuntu)
Importance: Undecided
Status: New
** Changed in: avahi (Ubuntu)
Status: New = In Progress
** Description changed:
upstart is currently quite deeply wired into our dependencies. Even in a
minimally bootstrapped chroot needs it, although this doesn't do any
booting at all:
# dpkg -P upstart
dpkg: dependency problems prevent removal of upstart:
- initscripts depends on
sysvinit's dependency updates are contained in my pending merge in
http://people.canonical.com/~pitti/tmp/sysvinit-merge/
** Changed in: sysvinit (Ubuntu)
Status: Confirmed = In Progress
** Changed in: sysvinit (Ubuntu)
Assignee: (unassigned) = Martin Pitt (pitti)
--
You received
** Description changed:
upstart is currently quite deeply wired into our dependencies. Even in a
minimally bootstrapped chroot needs it, although this doesn't do any
booting at all:
# dpkg -P upstart
dpkg: dependency problems prevent removal of upstart:
initscripts depends on
)
Importance: Undecided
Assignee: Martin Pitt (pitti)
Status: Fix Committed
** Affects: upstart (Ubuntu)
Importance: Undecided
Status: New
** Also affects: plymouth (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because
** Changed in: upstart (Ubuntu)
Importance: Undecided = Low
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sysvinit in Ubuntu.
https://bugs.launchpad.net/bugs/1351306
Title:
Cannot uninstall upstart and install
Thanks for that! This has to wait until we acutally land 214, or we find
a way to provide both APIs.
** 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
208 is in utopic now, so this can be closed.
** Changed in: systemd (Ubuntu)
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
The debug output does appear in /var/log/syslog after sudo udevadm
control --log-priority=debug at least in Ubuntu 14.04 LTS and 14.10, so
this apparently got fixed.
** Changed in: systemd (Ubuntu)
Status: New = Fix Released
--
You received this bug notification because you are a member
http://anonscm.debian.org/gitweb/?p=pkg-
systemd/systemd.git;a=commitdiff;h=44bbbcf93da59db1e60d3049348e605122fffb7a
** 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
There are no events at all in your log. So either Asus WMI hotkeys
isn't the right device for the brightness keys, can you try AT
Translated Set 2 keyboard? Or (more likely in this case), the kernel
driver needs to be fixed to actually generate key events for the
brightness keys; that's the case
Thanks. Reassigning to kernel then.
** Summary changed:
- [keymap] Brightness keys Fn+F5 and Fn+F6 don't work for Asus UX32LN
+ Asus UX32LN: Brightness keys Fn+F5 and Fn+F6 don't generate evdev event
** Package changed: systemd (Ubuntu) = linux (Ubuntu)
** Changed in: linux (Ubuntu)
** Also affects: friendly-recovery (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sysvinit in Ubuntu.
https://bugs.launchpad.net/bugs/1351306
Title:
Cannot uninstall
** Changed in: friendly-recovery (Ubuntu)
Status: New = Fix Committed
** Changed in: friendly-recovery (Ubuntu)
Assignee: (unassigned) = Martin Pitt (pitti)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
Can you please attach your /etc/network/interfaces? At the time when it
hangs, can you switch VTs and log in there already? Or ssh in? If you
get access to the machine in that state, can you please get the output
of sudo systemctl status and attach it here? Thanks!
** Changed in: systemd (Ubuntu)
Not a bug in systemd itself; (unity|gnome)-control-center need to start
depending on libnss-myhostname, like in Debian.
** Package changed: systemd (Debian) = gnome-control-center (Debian)
** Package changed: systemd (Ubuntu) = unity-control-center (Ubuntu)
--
You received this bug
Actually, in the MIR bug there is still some dispute, so reassigning
back to systemd for now.
** Package changed: unity-control-center (Ubuntu) = systemd (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in
Most of this was fixed in 204-9, i. e. in current Utopic. /dev/dvd etc.
work now, just /dev/cdrom is still broken, I'll fix that.
** Changed in: systemd (Ubuntu)
Status: New = In Progress
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) = Martin Pitt (pitti)
--
You received
http://anonscm.debian.org/gitweb/?p=pkg-
systemd/systemd.git;a=commitdiff;h=d5686ac2
Tested with scsi_debug and in KVM now.
** Changed in: systemd (Ubuntu)
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
What does not working mean? Your game doesn't have permissions to
access the pedals? Or they don't send the correct events, etc? (The
latter would be a kernel bug, not udev rules).
In a situation when they are not working, can you please find the
correct /dev/input/eventNN device for the pedals
Indeed, lots of USB port resets in
https://launchpadlibrarian.net/176813239/CurrentDmesg.txt. I suppose the
port that the hub is connected to is simply unable to provide enough
power for all devices on the hub, or there is a bad USB cable or other
hardware problem. Please try the USB device on a
I cannot reproduce this. On current Utopic (Ubuntu 14.10):
$ ls -l /dev/success
ls: cannot access /dev/success: No such file or directory
$ echo 'KERNEL==zero, SYMLINK+=success' | sudo tee
/lib/udev/rules.d/graphics-xorg.conf.rules
$ sudo udevadm trigger --verbose
Reproducible with scsi_debug:
sudo modprobe scsi_debug removable=1 ptype=5
Gives:
P: /devices/pseudo_0/adapter0/host10/target10:0:0/10:0:0:0/block/sr0
N: sr0
E: DEVLINKS=/dev/cdrom /dev/disk/by-id/scsi-3533055f0
/dev/disk/by-id/wwn-0x533055f0 /dev/disk/by-path/scsi-0:0:0:0
E:
It appears these numbers are pulled from ID_PATH, and I can't figure
out where this variable comes from.
From what used to be /lib/udev/path_id, which is now built into libudev-
private for performance reasons. You can do that part manually with:
sudo udevadm test-builtin path_id /sys/block/sr0
** Changed in: systemd (Ubuntu)
Status: Triaged = Invalid
** Changed in: systemd (Ubuntu Trusty)
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
1 - 100 of 4015 matches
Mail list logo
