I'm afraid I have to reassign this back to the kernel. In comment 4 it
is shown that the Fn+Fx keys work, but the topmost keys (labelled "3" in
your image) all generate the same scan code 0x8D, so it's impossible to
assign these to a keycode. These scan codes need to be fixed in the
driver, or it c
christian, on 13.10 (this also works on earlier versions), please
install the "evtest" package and use "sudo evtest". This lets you choose
your input device and basically gives the same information, but is a tad
easier to use.
--
You received this bug notification because you are a member of Kern
Thanks. Your attached udev.txt confirms that the keymap matching worked:
P: /devices/platform/i8042/serio0/input/input4/event4
[...]
E: KEYBOARD_KEY_85=brightnessdown
E: KEYBOARD_KEY_86=brightnessup
[...]
and your evdev output on event10 confirms that the device *claims* to
support KEY_BRIGHTNESS
I can reproduce this. I added a "sleep 5" to a pm-utils sleep.5 script.
When I run systemd-shim in the foreground in my session, I get this
output after resuming:
14:39:18 O: GDBus-debug:Address: In g_dbus_address_get_for_bus_sync() for bus
type 'session'
14:39:18 O: GDBus-debug:Address: env var
Argh, now that I'm looking for what is using the session bus: Look at
the original attempt to flush the bus and spot the error:
https://github.com/desrt/systemd-shim/commit/136ed11430
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux i
I'll land this upstream and upload an SRU next Monday.
** Changed in: systemd-shim (Ubuntu)
Status: Triaged => In Progress
** Changed in: systemd-shim (Ubuntu)
Assignee: (unassigned) => Martin Pitt (pitti)
--
You received this bug notification because you are a member of
Gabriel, can you please create a new systemd-shim log just like in
comment 5?
--
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/1252121
Title:
missing resume signal because D-BUS connection
Thanks Gabriel. That confirms that the D-BUS mess is fixed, and it also
times out properly 10 seconds after the suspend call. Both logs now look
spotless. So I'm afraid I need to ask you to get a complete system D-BUS
log of the whole suspend process, to check what happens to the
PrepareForSleep si
d
** Changed in: systemd-shim (Ubuntu)
Status: In Progress => Incomplete
** Changed in: systemd-shim (Ubuntu)
Assignee: Martin Pitt (pitti) => (unassigned)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
g. Please test suspend on devices without the alx module
as well (for the record, Martin Pitt did that on his ThinkPad X201)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1173952/+subscriptions
--
Mailing list: https://launchpad.net/~
Naming the interfaces is the responsibility of the kernel driver. It
doesn't need to be called "wlanXXX", that's just a convention.
** Package changed: systemd (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: New => Invalid
--
You received this bug notification because yo
Christopher, that's probably something that the AppArmor devs
(John/Tylor) should look into. When I discussed this with John and
Tylor, they already seemed to know which area of AppArmor hits this.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscri
amak79, thanks for pointing out! I fixed that upstream in
http://cgit.freedesktop.org/systemd/systemd/commit/?id=c79af123de
--
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/665918
Title:
M
Thanks; reassigning to the kernel then, as the keyboard driver must
produce scan codes, otherwise we can't reassign their meaning. Of
course, while doing that it could also just produce correct key codes
:-)
** Package changed: systemd (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
The "PrepareForSleep false" signal is missing. Invalidating kernel task
to stop the kernel bug auto-responder from nagging (please ignore the
previous comment).
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ke
Can you please modify ("sudo gedit", for example) /usr/share/dbus-1
/system-services/org.freedesktop.systemd1.service to set the Exec= line
to
Exec=/bin/sh -c 'env G_DBUS_DEBUG=all annotate-output /usr/lib/x86_64
-linux-gnu/systemd-shim >> /tmp/systemd-shim.log 2>&1'
Then please do a suspend/resu
In bug 1184262, Catalin made an interesting observation that this
failure seems to only happen for her when using the lid to suspend, but
not when using the session menu or power button.
It would be interesting if you ever get a suspend failure with this:
sudo gdbus call -y -d org.freedesktop.l
Philipp, Gabriel: I'm sorry, I didn't consider that annotate-output
isn't installed by default. It's in the "devscripts" package. Please
install it with "sudo apt-get install --no-install-recommends
devscripts". (It's useful to add timestamps to the log output).
--
You received this bug notificat
Thanks Rafael, Gabriel, Philipp! Your logs agree in the fact that at the
time it tries to call, or called pm-suspend, the shim's D-BUS connection
goes away:
09:20:16 E: (process:3100): GLib-GIO-CRITICAL **:
g_dbus_connection_flush_sync: assertion 'G_IS_DBUS_CONNECTION
(connection)' failed
(and so
Hello Daniel,
Daniel Lombraña González [2013-11-21 7:33 -]:
> Looks like I come from bug #1184262, and I'm experiencing the same
> problem :-) pm-suspend works always, quickly and the network is
> available without problems, however if I suspend the laptop with the lid
> or Unity menu, networ
Please don't apply this udev rule as it is:
* It can be made *much* more efficient and avoid an extra shell with
SUBSYSTEM=="memory", ACTION=="add",
DEVPATH=="/devices/system/memory/memory*[0-9]", ATTR{online}="1"
(same for the other rule)
* In this generic way they don't look plaus
** Also affects: linux (Ubuntu Saucy)
Importance: Undecided
Status: Invalid
** Also affects: systemd (Ubuntu Saucy)
Importance: High
Status: Triaged
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
http
** Changed in: systemd (Ubuntu Saucy)
Status: Triaged => 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.net/bugs/1235162
Title:
Regression: Persistent net names via /etc/udev
Abhishek Gupta, did you really quote the right mails? Because those
mails are just proving my point, it makes no sense to have an
unconditional userspace rule which is just there to always enable new
memory. To the contrary, as this is always going to involve more memory
allocation (like it might s
Yes, I think Andy's udev rule from comment 14 is an acceptable distro-
level compromise for 13.10, until that gets solved more cleanly. I
didn't see a confirmation from you that this worked, is that the one
which got tested?
> If you absolutely do not want to include the udev rule we can send you
BTW, where does this rule need to live, in the hypervisor or in the
guests? In the latter case I guess we should ship it in udev, in the
former case they hypervisor package could just ship it? That would avoid
the extra rule for other installs.
--
You received this bug notification because you ar
Time is running out for saucy, so I'll upload the rule from comment 14
now, with some correction: I take it you actually mean "memory[0-9]*"
instead of "memory*[0-9]" (same for CPU). @Abhishek, I don't see how
these rules would cause any other kernel module to suddenly not load?
All they do is to c
** 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://bugs.launchpad.net/bugs/1233466
Title:
Hot-Add Memory failing for lack of udev rule
St
Public bug reported:
Happened several times now, with saucy current and an external Monitor
attached. It seems to work fine with the laptop undocked, i. e. only
internal monitor (but I didn't suspend this machine often enough to be
sure about this).
ProblemType: KernelOops
DistroRelease: Ubuntu 1
untu Saucy)
Importance: Medium
Assignee: Steve Conklin (sconklin)
Status: Invalid
** Changed in: pm-utils (Ubuntu Saucy)
Status: Incomplete => Fix Committed
** Changed in: pm-utils (Ubuntu Saucy)
Assignee: (unassigned) => Martin Pitt (pitti)
** Changed in: lin
*** This bug is a duplicate of bug 430894 ***
https://bugs.launchpad.net/bugs/430894
** This bug has been marked a duplicate of bug 430894
Using Marvell SAS HBA, /dev/disk/by-path is not populated correctly
--
You received this bug notification because you are a member of Kernel
Packages,
Can anyone confirm that you see these bits:
DRIVER=omapfb
VSYNC=
in "udevadm monitor --kernel -e" on that device? It would be really
strange if not, I just want to make double-sure about that before I
start working on a fix tomorrow morning.
--
You received this bug notification because you are
Taking over from Dmitrijs as per Steve's request, Dmitrijs got pulled
into installer bugs.
** Changed in: systemd (Ubuntu)
Assignee: Dmitrijs Ledkovs (xnox) => Martin Pitt (pitti)
--
You received this bug notification because you are a member of Kernel
Packages, which is subsc
> Which appears to be getting a FD to "kernel" event source, via socket
created by
https://android.googlesource.com/platform/hardware/libhardware_legacy/+/android-4.3_r3/uevent/uevent.c
> so if we filter those VSYNC events on the "udev" source, systemd-udev
& upstart & et al user space shouldn't b
> Note, ideally we would already filter them at the "kernel" netlink
source
That's possible because that android driver doesn't use libudev to get
these events, but sets up its own netlink socket. We really don't want
to see these events anywhere else.
--
You received this bug notification becau
This is systemd-udevd with the patch, built on the Ubuntu armhf porter
box. That's what I used for testing on the maguro.
** Attachment added: "patched systemd-udevd (ARM)"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1234743/+attachment/3880064/+files/systemd-udevd
--
You received
This patch adds netlink filter rules to ignore change events from omapfb
if they are long enough to be a VSYNC event. It is a rather gross hack,
I don't want to expect the VSYNC= at a specific place in the raw packet
as the order or length of the other properties might change. But I
verified that d
Steve wanted a 0-day SRU with this so that we can build new phone images
with that included. The way the patch is done is that it doesn't change
anything on !arm; this both avoids potentially breaking
i386/amd64/powerpc, and also avoids penalizing those platforms with the
unnecessary extra netlink
This is udevadm with the patch.
** Attachment added: "patched udevadm (ARM)"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1234743/+attachment/3880065/+files/udevadm
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ub
tag verification-done
Thanks Colin for the comprehensive testing!
--
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/1234743
Title:
omapfb module floods system with udev events on samsung g
Reopening saucy kernel task, as this is apparently still an open issue
there.
** Changed in: linux (Ubuntu)
Status: Fix Released => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.la
What happens exactly? Does the computer power back on, you just don't
see anything? Can you still ssh in after resume? In that case, please do
so and attach /var/log/kern.log and /var/log/pm-suspend.log.
** Project changed: apport => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: New
If I install and boot
https://launchpad.net/ubuntu/+source/linux/3.11.0-11.17 on a current
trusty system this bug goes away. So
https://launchpad.net/ubuntu/+source/linux/3.11.0-12.18 was the one that
caused the regression.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: Ne
** Tags added: rls-t-incoming
--
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/1244157
Title:
"Failed name lookup - disconnected path" in dhclient D-BUS access
Status in “apparmor” packag
More kernel logs aren't relevant here, and I already stated the exact
kernel version which introduced this regression.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Summary changed:
- "Failed name lookup - disconnected path" in dhclient D-BUS access
+ [3.11.0-12.18 regr
** Also affects: network-manager (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/1244157
Title:
[3.11.0-12.18 regression] "Failed name
>From discussion with Jamie: Changing /etc/apparmor.d/sbin.dhclient to
/usr/lib/NetworkManager/nm-dhcp-client.action
flags=(attach_disconnected) {
does the trick. Apparently this happens because the NM tests unshare the
file system namespace.
They do this because they mount tmpfses over /run/
Is there any way to temporarily add this attach_disconnected flag
without having to touch files in /etc? I wouldn't want to actually sed
-i there as these tests are supposed to be running on a desktop
installation too (that's why I go through all the fuss in the first
place).
--
You received this
rom an unshared file
system, it can be kept open.
** Changed in: network-manager (Ubuntu)
Status: New => In Progress
** Changed in: network-manager (Ubuntu)
Assignee: (unassigned) => Martin Pitt (pitti)
--
You received this bug notification because you are a member of Kernel
Packag
** Changed in: network-manager (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://bugs.launchpad.net/bugs/1244157
Title:
[3.11.0-12.18 regression] "Failed name l
** 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
** 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
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
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 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
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
** 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
** 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
** 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
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)
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
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,
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
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
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
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
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
> 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.
> 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
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
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,
*** This bug is a duplicate of bug 1431582 ***
https://bugs.launchpad.net/bugs/1431582
** This bug has been marked a duplicate of bug 1431582
there is no wi-fi after hybernate mode
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to li
Unsubscribing sponsors for now. Let's please not change this until we
have some clarity about the broadcom drivers.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to b43-fwcutter in Ubuntu.
https://bugs.launchpad.net/bugs/1490212
Title:
"
Subscribing kernel team. Is this driver really something which we should
offer to users via graphical means (and thus make it very easy)? It
seems we've had three drivers (b43 with fwcutter, bcmwl, and now the
relatively new bcma one). Which of these do we actually still support?
We can't expect t
The difference under systemd is indeed mostly that the pm-utils suspend
quirks are not being run any more, like /usr/lib/pm-
utils/sleep.d/60_wpa_supplicant . Does it help if you run
sudo wpa_cli suspend
then suspend, resume, and run
sudo wpa_cli resume
? If so, then we need to teach the w
Wrt. suspend there is no structural change between 15.04 and 15.10, in
both cases you were already using a direct kernel sleep without pm-utils
when you use the "K" menu.
This sounds like some kernel/driver bug which one of the pm-utils quirks
is working around. Can you please "cd /usr/lib/pm-util
Public bug reported:
On Xenial, linux' autopkgtests now consistently fail
(http://autopkgtest.ubuntu.com/packages/l/linux/xenial/i386/):
==
FAIL: test_easyprof (__main__.ApparmorTest)
Test aa-easyprof
--
** No longer affects: util-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/1498162
Title:
unable to make backup link of `./usr/sbin/uuidd' before installing new
version:
** Tags added: bot-stop-nagging
** 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/1510362
Title:
[xenial] autopkgtest r
Thanks. Can you verify that "sudo systemctl suspend" exhibits the same
problem? If not, then it's indeed not a matter of pm-utils and its
quirks.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
@Mathieu: Is enabling "AutoEnable" something we want to do and is
generally safe?
--
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/1510570
Title:
BLE pairing fail
Status in bluez package
> I think this may just need a no change rebuild for apparmor so that
python 3.5 bindings are built.
This was already done in wily;
python3-libapparmor_2.10-0ubuntu6_amd64.deb does contain
LibAppArmor/_LibAppArmor.cpython-35m-x86_64-linux-gnu.so .
--
You received this bug notification because yo
Ah, thanks Simon. As you currently seem to manage bluez
(https://code.launchpad.net/~bluetooth/bluez/bluez5-upgrade), can you do
this change too?
** Changed in: bluez (Ubuntu)
Assignee: (unassigned) => Simon Fels (morphis)
--
You received this bug notification because you are a member of Ke
> Could this failure be related to bug report #1509868
I'm afraid I don't know enough about the kernel and graphics drivers to
tell.
Thanks for eliminating the pm-utils suspend quirks as a possible cause.
If "sudo systemctl suspend" by itself works, then we need to find out
what the K menu does d
Thanks. Reassigning to the kernel then.
** Package changed: systemd (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 subscribed to linux in Ubuntu.
https://bugs.l
So obviously one of the quirks in /usr/lib/pm-utils/sleep.d works around
this kernel bug. We need to find out which. Can you please move the
files in that directory to some other place one by one and do a "sudo
pm-suspend" / resume cycle until it starts failing? That's the "magic"
hook then. Which
g
> this bitesize-bugfix (there) should enter "wily-updates"
It's 8 days now, so ready to be released; the SRU team should do that
soon (but they might avoid releasing updates on Fridays).
Martin
--
Martin Pitt| http://www.piware.de
Ubuntu Developer (www
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
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
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
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 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
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/
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
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
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
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
401 - 500 of 536 matches
Mail list logo
