Forwarded upstream:
http://article.gmane.org/gmane.linux.bluez.kernel/65182
** Changed in: bluez (Ubuntu Wily)
Status: In Progress => Fix Committed
** Changed in: bluez (Ubuntu Wily)
Assignee: (unassigned) => Martin Pitt (pitti)
--
You received this bug notification because y
Wily fix uploaded (might end up as an SRU, though). I also sent the
patch upstream, will add a link once it hits the upstream ML archives.
** Changed in: bluez (Ubuntu Wily)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Kernel
Packages,
I'm expediting the usual 7 day maturing period; this is a rather grave
regression and apparently the new kernel didn't get around to add a
Breaks: to the previous LXC version. Thanks for verifying!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscri
The verification of the Stable Release Update for lxc 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 regr
> ConditionPathIsDirectory=/sys/class/bluetooth
Sounds perfect!
** Changed in: bluez (Ubuntu Wily)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/15067
> There is nothing we can do from bluez side.
Perhaps not from the daemon itself, but the packaging certainly needs to
be fixed. It could be that the .service file grows some Condition*= to
not start if we already know that it won't work; or the .postinst
shouldn't fail when the service fails (e.
Even if we would change our kernel package to always include bluetooth,
that still would make the package fail for custom/third-party kernels,
so I'd say this is neither required nor sufficient. Let's fix the bluez
packaging instead.
** Changed in: linux (Ubuntu Wily)
Status: New => Won't F
Trivially reproduces on e. g. the cloud images, but for completeness:
$ sudo systemctl status -l bluetooth.service
● bluetooth.service - Bluetooth service
Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor
preset: enabled)
Active: failed (Result: exit-code) since Tue 201
Asked on IRC, but didn't get a response:
- What are the changes to Add-support-for-forcing-modules-
installation.patch? That patch already existed, and the debdiff here
completely changes it. A lot of it just seems to be reformatting, but
the diff-of-diff makes it really hard to see what changed
Hello Andy, or anyone else affected,
Accepted lxc into trusty-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/lxc/1.0.7-0ubuntu0.9
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubun
I suppose the recent kernel patch
UBUNTU: SAUCE: (no-up) apparmor: fix mount not handling disconnected
paths
which got backported to trusty causes this regression. As the same code
is present in later releases, I guess that in v/w lxc has an updated
apparmor profile which allows the operation
To completely rule out that it's not the python3.4 regression in trusty-
proposed (bug 1500768) or the (really unrelated) udev fix in bug
1470399 I instead ran it with --apt-pocket=proposed --setup-commands
'apt-get update; apt-get -y install linux-generic' instead of the -U
/--apt-upgrade switch,
Thank you. This needs to be fixed in the kernel driver then, as without
a scan code there is nothing we can do in userspace.
** Package changed: systemd (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: Incomplete => New
** Summary changed:
- Brightness HotKeys not Detecte
This seems fixed in wily now with the latest kernel:
http://autopkgtest.ubuntu.com/packages/u/udisks2/wily/i386/ is happy
again \o/
** Also affects: linux via
http://bugzilla.kernel.org/show_bug.cgi?id=101011
Importance: Unknown
Status: Unknown
** Changed in: linux (Ubuntu Wily)
** Description changed:
dkms_packages.py crashed with AttributeError in __main__: 'module'
object has no attribute 'make_report_path'
+
+ This was introduced with/in bug 1492570. It is an API break as the old
+ API was insecure, so it was replaced with a new safe one. So we need to
+ adjust D
The verification of the Stable Release Update for dkms 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 reg
** Also affects: dkms (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: dkms (Ubuntu Vivid)
Importance: Undecided
Status: New
** Also affects: dkms (Ubuntu Trusty)
Importance: Undecided
Status: New
--
You received this bug notification because you
** No longer affects: upstart (Ubuntu)
** No longer affects: udev (Ubuntu)
** No longer affects: systemd (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1495116
Title:
booting
The upload auto-triggered new test runs of all DKMS packages against the
new DKMS:
-
http://people.canonical.com/~ubuntu-archive/proposed-migration/vivid/update_excuses.html#dkms
particularly http://autopkgtest.ubuntu.com/packages/t/tp-smapi/vivid/i386/
(as per SRU test case), first run f
Hello Andy, or anyone else affected,
Accepted dkms into vivid-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/dkms/2.2.0.3-2ubuntu3.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.u
Hello Andy, or anyone else affected,
Accepted dkms into precise-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/dkms/2.2.0.3-1ubuntu3.4 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki
Hello Andy, or anyone else affected,
Accepted dkms into trusty-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/dkms/2.2.0.3-1.1ubuntu5.14.04.3 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https
** Also affects: dkms (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: dkms (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: dkms (Ubuntu Wily)
Importance: High
Assignee: Andy Whitcroft (apw)
Status: In Progress
** Also affe
Thanks! Uploaded.
** Changed in: bcmwl (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bcmwl in Ubuntu.
https://bugs.launchpad.net/bugs/1491070
Title:
On removal the package should warn a re
Thank you! Makes sense. I removed the duplicate product ID at the end of
the patch. I'll upload this together with bug 1491070.
** Changed in: bcmwl (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
This doesn't need apport-collect, this is a bug in the header files
which is straightforward to reproduce.
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: linux (Ubuntu)
Status: Incomplete => Triaged
--
You received this bug notification because you are a me
amd64 kernel with i386 userspace does work in general. But this bug
contains no actual error message -- can you try booting with "debug" in
the kernel command line and drop "quiet splash", then wait for a failed
boot, and make a screenshot (with a camera)? There hopefully is some
indication what's
https://launchpadlibrarian.net/216237731/dkms_2.2.0.3-2ubuntu3_2.2.0.3-2ubuntu4.diff.gz
looks okay to me. A new dkms will now automatically trigger tests of all
our DKMS packages, so britney will complain at you if this introduces
any regressions. So +1 to the FFE.
** Project changed: dkms => dkms
This apparently was an error in the bluez package hook.
/usr/share/apport/package-hooks/source_bluez.py does not mention hcidump
any more in current wily, so I suppose the hook got fixed at some point.
** No longer affects: apport (Ubuntu)
** No longer affects: apport
** Changed in: bluez (Ubunt
The CurrentDmesg.txt attachment shows where the kernel hangs in
detecting the device.
** Package changed: udisks2 (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/
I now also successfully ran the test case above on my local laptop.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/1489
This is being automatically used by our autopkgtest infrastructure now:
Successful run with the -proposed trusty version:
http://autopkgtest.ubuntu.com/packages/b/bcmwl/trusty/amd64/
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-trusty/t
I uploaded the precise and trusty backports. They were straightforward,
dkms hardly changed since precise. I tested them locally with installing
the built deb into a precise/trusty container, and ran "adt-run bcmwl
--- lxc precise-dkms-backport".
** Description changed:
The kernel team has requ
right now, there is no test regression possible
either.
** Affects: dkms (Ubuntu)
Importance: Undecided
Status: Fix Released
** Affects: dkms (Ubuntu Precise)
Importance: Wishlist
Assignee: Martin Pitt (pitti)
Status: Triaged
** Affects: dkms (Ubuntu T
https://jenkins.qa.ubuntu.com/job/wily-adt-
udisks2/44/ARCH=i386,label=adt/ was the last one that succeeded, with
linux-image-4.0.0-4-generic 4.0.0-4.7. https://jenkins.qa.ubuntu.com/job
/wily-adt-udisks2/45/ARCH=i386,label=adt/ is the first one that failed,
with linux-image-4.1.0-1-generic 4.1.0-1
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1478623
Title:
Kernel oops - blk_update_request: I/O error when runnin
** Package changed: hal (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1467236
Title:
'Touchpad' incorrectly detected as PS/2 mouse in 'Toshiba Satellite
Z30
** Package changed: udev (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1384969
Title:
Writing large amounts of data to exFAT formatted micro sdcards with
Ub
Thanks for your patience! I believe this is sufficiently understood now.
I retitled the bug accordingly, this should indeed be fixed properly in
the driver then. In the meantime, putting that workaround into rc.local
or /lib/systemd/system-sleep/ (see man systemd-suspend.service) is fine.
** Summa
Hello Jan,
Jan Rathmann [2015-06-15 14:06 -]:
> - If I run the ethtool command before 'systemctl suspend', the bug
> hasn't appeared so far - and it does not seem to matter if I run ethtool
> with the 'wol g' (enable WOL) or with the 'wol d' flag!
That's indeed interesting -- After a clean b
Right, so this is (at most) the kernel's fault. I'm not sure whether
ejecting a CD is supposed to trigger an uevent, but maybe not in all
cases?
** Package changed: udev (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Importance: Undecided => Low
** Summary changed:
- udev rules are
Ah, thanks! That's a bit weird -- on powersave false wake-on-lan is
*enabled*. So it seems that with WOL disabled your computer doesn't stay
suspended, but with WOL enabled it does.
Cross-check:
sudo ethtool -s wlan0 wol g ; sudo systemctl suspend
-> that enables WOL on the usual magick packet
> F1,F2,F5,F6: no change, no output
OK, that makes it a kernel bug then, reassigning. The driver needs to
send evdev events for these keys.
> F3,F4,F7,F9 : no output, did produce output in previous Asus device
test.
Yes, that's expected. They are appearing on the WMI device, not the AT
keyboard
On that grounds I close the systemd/udev task, as this really needs to
be fixed in the hid-generic (or maybe other) kernel driver.
** Changed in: systemd (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subs
For example, we have
#define BTN_TRIGGER…0x120
I. e. the capability bit mask whether the device claims to have a BTN_TRIGGER
is the 0x120th bit in capabilities/key, or IOW, the 32th bit in
bit 256: 0C01
which is zero. Likewise there's no BTN_A, nor BTN_1. Interestingl
Adding a kernel task, as the /dev/input/js0 is created by the kernel
driver (usbhid) itself. udev does not create device nodes, it just adds
additional properties, runs extra programs on the device nodes, etc.
So cases a/ vs. b/ is interesting -- in both cases you get three HID
devices, just that
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1458631
Title:
udev: /dev/input/js0 is created but no joystick
Ah, great. So can you confirm that this works:
sudo pm-powersave false; sudo systemctl suspend; sudo pm-powersave
true
? If so, can you repeat the bisecting exercise with the hooks in
/usr/lib/pm-utils/power.d/ to find out which one is the important one
here?
Thanks!
--
You received this bug
Thanks Jan. Note that you can make this a little faster too -- you can
start with testing (i. e. starting with "suspend") all five hooks at the
same time, to confirm whether it's actually any of these five. If it
still doesn't help, then the problem is somewhere entirely different. If
it does help,
Thanks. So we need to find out which hook does the magic. For each value
of in the below list, can you please run
sudo /usr/lib/pm-utils/sleep.d/ suspend ; sudo systemctl
suspend; sudo /usr/lib/pm-utils/sleep.d/ resume
In descending order of likelyhood, I recommend the following list for
:
OK, then it might be one of the other hooks in /usr/lib/pm-utils/sleep.d
that pm-suspend runs. According to your dmesg it's unlikely that you
have the "alx" module loaded ("lsmod | grep alx" should be empty).
Can you please attach your /var/log/pm-suspend.log?
60_wpa_supplicant could be a likely
Thanks for confirming! Reassigning to the kernel then.
** Package changed: systemd (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1454253
Title:
external usb
Interesting, pm-suspend uses no quirks at all. Can you double-check that
running "sudo pm-suspend" is reliable while "sudo systemctl suspend" is
not? The two do exactly the same without quirks, i.e. writing "mem" into
/sys/power/state..
--
You received this bug notification because you are a memb
The main difference here is that under upstart we still run pm-suspend
with its quirks, while under systemd there are no quirks being run any
more. As suspend quirks have supposed to be obsolete for many years
and should be fixed properly in drivers/kernel, I add a linux task.
To find out which
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1437492
Title:
boot stalls on USB detection errors
Status in linux
That should be done by the kernel itself. In the meantime you can put a
script into /lib/systemd/system-sleep/, they work much like the old pm-
utils/sleep.d/ scripts. See "man systemd-sleep" for details.
** Package changed: systemd (Ubuntu) => linux (Ubuntu)
--
You received this bug notificatio
Hello Timo, or anyone else affected,
Accepted into utopic-proposed. The package will build now and be
available in a few hours 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 -prop
** Changed in: linux (Ubuntu)
Milestone: ubuntu-15.04 => ubuntu-15.05
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1438651
Title:
devel: consider shortening package name (only) to
** Changed in: pulseaudio (Ubuntu Vivid)
Milestone: ubuntu-15.04 => vivid-updates
** Changed in: bluez (Ubuntu Vivid)
Milestone: ubuntu-15.04 => vivid-updates
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https:
Setting systemd task to incomplete for now. Please let me know how we
want the cgroups set up for user sessions, and I'll change our patch
accordingly. Thanks!
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Kerne
ing the user session into all
controllers, and (2) might break existing container workloads which
actually expect the dropped controllers.
My gut feeling is that (2) is the better option.
Martin
--
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian De
Ah, indeed it seems btrfs is unhappy on your machine. Setting back to
New for now, as I don't know how to debug this kernel/fs bug from here
on, I'm afraid.
** Summary changed:
- ubuntu 15.04 hangs at purple scren even with nomodeset
+ btrfs-transaction hangs
** Package changed: linux-flo (Ubunt
Most of the upgraded packages in your list are totally unrelated to
keyboards. The only one which might even be remotely related is
libgnome-desktop. It's much more likely that this happened due to a
kernel upgrade -- could you try and boot with an earlier kernel in the
grub boot menu and see wheth
** Package changed: systemd (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1445488
Title:
audio hardware not recognized
Status in linux package in Ubuntu:
N
bluetooth.service failed on your system.
** Package changed: systemd (Ubuntu) => bluez (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1445408
Title:
USB-bluetooth-mouse not det
Does this also happen if you boot with upstart? (You can choose that
from the grub boot menu under "Advanced options").
Please also boot without "quiet splash $vt_handoff" -- does your
computer boot then? If so, it's a graphics/plymouth problem, if not this
should show where it's hanging.
/usr/sh
Thanks. So this keeps looping on
apr 09 01:41:57 hostname kernel: usb 1-3: new high-speed USB device number 2
using xhci_hcd
apr 09 01:41:57 hostname kernel: usb 1-3: device descriptor read/all, error -110
but doesn't say which kind of device that is as it can't talk to it.
Is this a regression
OK, so if that didn't help it looks like trouble with an internal USB
device. Could you add "debug" to the "linux" line in the grub boot menu,
boot with that, and then attach the output of "journalctl -ab" here?
Thanks!
--
You received this bug notification because you are a member of Kernel
Pack
The kernel log shows huge gaps in device detection, apparently the
hardware gets locked up during USB detection/enumeration?
[7.292422] input: HDA Intel HDMI HDMI/DP,pcm=7 as
/devices/pci:00/:00:03.0/sound/card0/input16
[ 10.918992] usb 1-3: device descriptor read/all, error -110
[
Ah-haa! For the first two workers I found these gems in the log:
Apr 01 13:58:57 alice systemd-udevd[458]: timeout '/bin/sh -c 'if [ -f
/usr/bin/systemctl ]; then /usr/bin/systemctl --no-block start
hplip-printer@003:006.service; else /usr/bin/nohup
/usr/bin/hp-config_usb_printer 003:006 ; fi &
Thanks. How long does the /lib/udev/accelerometer call take for you? (it
should be more or less instantaneous). It seems it takes a lot longer
when it runs during boot, so we need some better debugging there.
Could you re-enable /lib/udev/rules.d/61-accelerometer.rules and change
it to this:
SUBS
Can you please try this:
sudo mv /lib/udev/rules.d/61-accelerometer.rules{,.disabled}
and check if that changes anything? If so, can you please give me the
output of
sudo SYSTEMD_LOG_LEVEL=debug /lib/udev/accelerometer
/devices/platform/lis3lv02d/input/input23
? (It was input23 in your log;
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1420544
Title:
[SRU] Ubuntu instances on GCE should use NOOP scheduler
Updating status for vivid tentatively, until the kernel team can
comment.
** Changed in: systemd (Ubuntu)
Status: Incomplete => Won't Fix
** Changed in: linux (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Kernel
Packages, whic
** Tags removed: systemd-boot
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1430780
Title:
3.19.0-8-generic kernel got errors during installation
Status in linux package in Ubuntu:
C
http://git.kernel.org/cgit/docs/man-pages/man-
pages.git/commit/?id=6f67e3e
** Changed in: manpages (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
Nice, thanks Michael!
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1397652
Title:
/dev/random and /dev/urandom world
That's a kernel regression, I'm afraid. They all map to the same scan
code now, so userspace cannot tell them apart any more.
** Package changed: systemd (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
*** This bug is a duplicate of bug 1333140 ***
https://bugs.launchpad.net/bugs/1333140
Please note that it's very unlikely that the computer's BIOS has anyhing
to do with this. It's the linux kernel which exposes these RPMB devices,
and this issue is well understood. It's certainly not "incomp
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
Assigning to the kernel for now, as that looks like a block device
driver issue at first sight.
** Package changed: ubuntu => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Kernel
Packages, which is
@Ben Howard: I'll upload that to trusty as soon as the current SRU gets
verified and into trusty-updates.
** Changed in: systemd (Ubuntu Trusty)
Assignee: (unassigned) => Martin Pitt (pitti)
** Changed in: systemd (Ubuntu Trusty)
Importance: Undecided => Medium
--
You receiv
The updated udev rule is of course fine for an SRU. Marked for trusty
for now, please add more releases as desired. Keeping the linux task for
vivid onwards to change the default in the virtio kernel driver itself
(pending feedback from the kernel team).
** Package changed: ubuntu => linux (Ubuntu
http://cgit.freedesktop.org/systemd/systemd/commit/?id=4b9bb683
** Package changed: linux (Ubuntu) => systemd (Ubuntu)
** Changed in: systemd (Ubuntu)
Status: Incomplete => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribe
http://cgit.freedesktop.org/systemd/systemd/commit/?id=4b9bb683
** Package changed: linux (Ubuntu) => systemd (Ubuntu)
** Changed in: systemd (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
systemd 219 is planned in about two weeks which will contain this.
** Changed in: systemd (Ubuntu)
Importance: Undecided => Medium
** Changed in: systemd (Ubuntu)
Status: New => Fix Committed
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Martin Pitt (pitti)
Reopening the kernel task here. We've carried the "temporary" udev rule
workaround for three releases now; it seems we all agree that it's wrong
(unconditional "unbreak my kernel rule") and makes things even worse
under memory pressure. Is there any better solution in sight? Thanks!
** Changed in:
** No longer affects: linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1350947
Title:
apparmor: no working rule to allow making a mount private
Status in AppArmor Linux app
hallyn | stgraber: i was thinking lcx-start-ephemeral used the api more than it
does.
hallyn | stgraber: lcx-start-ephemeral needs to be updated the same way the api
did, for the new overlayfs options
--
You received this bug notification because you are a member of Kernel
Packages, which is su
It seems Serge knows what's going on, so tentatively closing the linux
task.
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bug
Initially I suspected that this is
https://github.com/lxc/lxc/commit/7fb1bef22a but we apparently already
have that commit.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1409425
Title:
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1409425
Title:
lxc-start-ephemeral stops working with kernel 3.18 - ov
Adding linux tasks. This overlayfs change might be due to its
upstreamization, or unintended, so please invalidate if appropriate.
Thanks!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/140
Public bug reported:
With the previous vivid kernel 3.16.0-28-generic,"lxc-start-ephemeral -o
containername" works fine. With the current 3.18.0-8-generic it fails
with "the container failed to start". This is reproducible in a clean
cloud VM:
$ sudo apt install lxc
$ sudo lxc-create -t busybox
I created an upstream patch and a pull request at
https://github.com/lxc/lxc/pull/393
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1350947
Title:
apparmor: no working rule to allow mak
I confirm that this works fine under systemd:
mount options=(rw, make-slave) -> **,
Thanks!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1350947
Title:
apparmor: no working rule to
http://anonscm.debian.org/cgit/pkg-
systemd/systemd.git/commit/?h=experimental&id=565eb7
** Changed in: systemd (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://
** Changed in: systemd (Ubuntu)
Importance: Medium => High
** Changed in: linux (Ubuntu)
Status: Confirmed => Triaged
** Changed in: linux (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Sebastien tested this, and it works:
SUBSYSTEM=="firmware", ACTION=="add", ATTR{loading}="-1"
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1398458
Title:
kernel fails to load iwlwif
Please create /etc/udev/rules.d/50-firmware.rules with
SUBSYSTEM=="firmware", ACTION=="add", RUN="/bin/false"
and see whether that improves things? To be honest I don't know exactly
what the kernel expects from the userspace helper, but it's worth a try.
--
You received this bug notification
301 - 400 of 535 matches
Mail list logo
