*** This bug is a duplicate of bug 1060404 ***
https://bugs.launchpad.net/bugs/1060404
** This bug has been marked a duplicate of bug 1060404
update-grub runs and fails in containers
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Please attach a screenshot with the crash, it should show a traceback or
other error. Thanks!
** Package changed: systemd-shim (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Kernel
dy
has a blacklist (tree/drivers/ata/libata-core.c, ATA_HORKAGE_NO_NCQ_TRIM).
[...]
-- Martin Pitt Wed, 20 Aug 2014 07:18:28 +0200
** Changed in: linux (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Kernel
Packa
** Tags removed: need-duplicate-check
--
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/1348120
Title:
package linux-image-3.13.0-30-generic 3.13.0-30.55 failed to
install/upgrade: run-pa
** Tags removed: need-duplicate-check
--
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/1340676
Title:
package linux-image-3.13.0-31-generic 3.13.0-31.55 failed to
install/upgrade: run-pa
** Tags removed: need-duplicate-check
--
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/1340679
Title:
package linux-image-3.13.0-26-generic 3.13.0-26.48 failed to
install/upgrade: run-pa
** Changed in: auto-package-testing
Status: In Progress => Triaged
--
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/1081500
Title:
Add autopkgtest for mutual rebuild-testing amongst
Uploading gcc already triggers (e)glibc, binutils, linux, and pretty
much every single other autopkgtest, so there's nothing to change here.
The mutual rebuilding has worked quite well, aside from the fact that
glibc's autopkgtest has never succeeded (so it's not taken into
account). Ironically the
Setting to incomplete for now. This either needs fixing in AppArmor
properly, or I at least need to get some hints how to change the current
rule to work with current AppArmor.
** Changed in: lxc (Ubuntu)
Status: Triaged => Incomplete
--
You received this bug notification because you are
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
Seems irda-utils has an invalid init.d script:
insserv: warning: script 'irda-setup' missing LSB tags and overrides
insserv: There is a loop between service watchdog and irda-setup if stopped
insserv: loop involving service irda-setup at depth 2
insserv: loop involving service watchdog at depth
udev doesn't change permissions on these devices, that's a kernel
default (devtmpfs). However, why is that bad? As far as I know, the
devices are writable for non-root users so that you can have usespace
daemons like haveged for additional entropy data (but not increase it --
that's a separate ioct
Yeah, indeed. https://en.wikipedia.org/wiki//dev/random also describes
this aspect in more detail (but of course it's not a reference to rely
on). Unfortunately the FHS
(http://www.pathname.com/fhs/pub/fhs-2.3.html#DEVDEVICEFILES) makes no
statement about this at all.
I added a manpages tasks for
We ship /lib/firmware/iwlwifi-6000-4.ucode in linux-firmware, which is
also what the module advertises:
$ modinfo iwlwifi|grep 6000
firmware: iwlwifi-6000g2b-6.ucode
firmware: iwlwifi-6000g2a-5.ucode
firmware: iwlwifi-6000-4.ucode
This is what udev's userspace helper is looking
Adding a linux task. It seems quite clear that in the short term we need
to re-enable the udev userspace helper, but this eventually needs to be
fixed in the kernel properly.
** Description changed:
Using current vivid, when using udev 217 wlan0 is missing, it's there
and working fine when do
n: systemd (Ubuntu)
Status: New => In Progress
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Martin Pitt (pitti)
--
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
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
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
** 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
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://
This really isn't util-linux' fault. If you remove the package of the
running kernel then from then on all module loading will fail as they
went away. I think it would be better to add some safety check into the
kernel's preinst to abort the removal of the currently running kernel. I
think in the p
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
htt
This ran now in https://jenkins.qa.ubuntu.com/job/trusty-adt-linux/110/.
The new ubuntu-regression-suite autopkgtest succeeded (see
https://jenkins.qa.ubuntu.com/job/trusty-adt-
linux/110/ARCH=amd64,label=adt/console), just the test was marked as
failed because of a Jenkins job configuration issue.
Any chance of applying this upstream at some point?
** Changed in: dkms (Ubuntu Raring)
Status: Triaged => Won't Fix
** Changed in: dkms (Ubuntu Quantal)
Status: Triaged => Won't Fix
** Changed in: dkms (Ubuntu Precise)
Status: Triaged => Won't Fix
--
You received this bug
Discussed with Andy on IRC. The rebuild test should become simplified
and also do the build as the actual test, otherwise after the build it
will reset the testbed again (i. e. starting new VM, upgrading to new
kernel in -proposed, reboot). We also want to set a build profile to
only build one flav
OK, Jenkins config fixed, https://jenkins.qa.ubuntu.com/job/trusty-adt-
linux/113/ succeeded now. But please double-check if this is right:
seccomp_bpf_tests.c: In function ���change_syscall���:
seccomp_bpf_tests.c:1086:7: error: ���struct user_regs_struct��� has no
member named ���orig_ax���
Does this actually need to be fixed on the kernel side in Trusty? I'm a
bit confused by the "fix released" status of linux in utopic, as far as
I know most issues can be fixed in udev's keymaps alone?
** Also affects: linux (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affec
I uploaded an SRU to the trusty review queue with the latest upstream
keymaps which include the fix for this bug. Note that accepting the SRU
is currently blocked on verifying the current SRU in trusty-proposed
(bug 1367883).
** Changed in: systemd (Ubuntu Trusty)
Status: New => In Progress
Public bug reported:
Current Ubuntu Touch images cause a kernel panic at boot:
$ sudo ubuntu-emulator create --channel=ubuntu-touch/devel-proposed
--arch=i386 devel-proposed
The current revision as of the time of reporting is 160. This did not
yet happen with earlier revisions. I re-tested with
** Description changed:
Current Ubuntu Touch images cause a kernel panic at boot:
$ sudo ubuntu-emulator create --channel=ubuntu-touch/devel-proposed
--arch=i386 devel-proposed
The current revision as of the time of reporting is 160. This did not
yet happen with earlier revisions.
** Also affects: goget-ubuntu-touch (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Description changed:
Current Ubuntu Touch images cause a kernel panic at boot:
$ sudo ubuntu-emulator create --channel=ubuntu-to
I get the same crash in tty_buffer_request_room+0x1d/0x128 when I do
"phablet-shell" and "sudo poweroff", also on previous images.
--
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/1349709
Ti
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 Kerne
*** This bug is a duplicate of bug 1339998 ***
https://bugs.launchpad.net/bugs/1339998
** This bug has been marked a duplicate of bug 1339998
[Dell Latitude 12 Rugged Extreme 7204] Microphone mute key does not work
--
You received this bug notification because you are a member of Kernel
P
can you please do "dmesg > /tmp/dmesg.txt" after such a resume and
attach /tmp/dmesg.txt here? Thanks!
** Package changed: udisks2 (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Kernel
P
i.product.version: ThinkPad X230
dmi.sys.vendor: LENOVO
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: John Johansen (jjohansen)
Status: Confirmed
** Affects: lxc (Ubuntu)
Importance: Undecided
Assignee: Martin Pitt (pitti)
Status: Triaged
** T
I tested this on trusty's 3.13.0-32, and the previous utopic 3.15.0-6,
same result. So it's not a regression apparently; although I tried
"mount options=(rw, slave) -> /" some weeks ago and it appeared to work,
but apparently I did something weird back then which made it work, but I
can't remember
Status: New
** Changed in: lxc (Ubuntu)
Status: New => Triaged
** Changed in: lxc (Ubuntu)
Assignee: (unassigned) => Martin Pitt (pitti)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.la
** Description changed:
When the file system is mounted as MS_SHARED by default (such as under
systemd, or when the admin configures it so), things like schroot or LXC
need to make their "guest" mounts private. This currently fails under
utopic:
$ sudo lxc-create -t busybox -n c1
$
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)
Sta
** 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/1336541
Title:
No TRIM via USB
Status in “linux” package in Ubuntu:
New
Bug descrip
** Package changed: udisks2 (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/1352821
Title:
0489:e078 - Qualcom Atheros - Ubuntu 14.04 bluetooth not working
Sta
Added kernel task for the lack of evdev events.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
+ Summary:
+ - The joystick evdev device for the pedals doesn't get proper permissions
(in udev/systemd)
+ - The pedal evdev device sometimes doe
Closing again. Polling drives does not apply to udisks2 as for a few
years now this is done by the kernel itself.
Can I kindly ask you to report a new bug for unrelated issues like SMART
updates? Thanks!
--
You received this bug notification because you are a member of Kernel
Packages, which is
Hmm, bluez looks fine at first sight. Reassigning this back, apparently
the bluetooth.target behaviour changed.
** Package changed: bluez (Ubuntu) => systemd (Ubuntu)
** Changed in: systemd (Ubuntu)
Status: Triaged => Confirmed
** Changed in: systemd (Ubuntu)
Assignee: Marti
** Changed in: bluez (Ubuntu)
Status: New => Triaged
** Changed in: bluez (Ubuntu)
Assignee: (unassigned) => Martin Pitt (pitti)
** Summary changed:
- Bluetooth is not activated
+ bluetooth.service not started automatically
--
You received this bug notification because you are
** 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
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
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
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
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. 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
:
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,
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
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
** 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
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
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
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
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
** 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:
** 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
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
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
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
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
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
@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
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
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
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
** 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
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;
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
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 &
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
[
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
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
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
** 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
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
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
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
> 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
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
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
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
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
** 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
** 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
*** 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
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
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
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
** 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
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
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
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
** 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
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:
101 - 200 of 536 matches
Mail list logo
