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
Public bug reported:
Standard usage of Ubuntu, sporadically end up with an unresponsive user
interface. Examination of syslog spews out some error about i915 intel
display driver.
I've noticed there are a couple of similar bugs around, most notably:
bug #1384342 and bug #64431, and possibly bug
Public bug reported:
Just finished reporting another bug #1475561
Had a quick google to see if I could find a way to kickstart the
graphics driver without a reboot, google's response was something like
'sudo service lightdm restart' should handle rebooting the driver.
That resulted in the virtua
Public bug reported:
Don't want to spam anyone, but this *should* be the other bug that
happened after bug #1475563...
ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: linux-image-3.16.0-43-generic 3.16.0-43.58
ProcVersionSignature: Ubuntu 3.16.0-43.58-generic 3.16.7-ckt13
Uname: Linux 3.16.
Public bug reported:
The same symptoms and problems as bug #1475561.
Don't know if there is anything in this debug stuff that isn't in that
bug. POsting in case there is.
ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: linux-image-3.16.0-43-generic 3.16.0-43.58
ProcVersionSignature: Ubunt
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: ubuntu-mate
--
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/1473295
Title:
Problem with
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: ubuntu-mate
--
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/1473540
Title:
Kernels above
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: ubuntu-mate
--
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/1469402
Title:
touchpad does
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: ubuntu-mate
--
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/1462221
Title:
Display Brigh
Yes BYD have been contacted. No reply :-(
--
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/1424293
Title:
BYD trackpad detected as PS/2 mouse
Status in linux package in Ubuntu:
Triaged
** 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
Raedwulf, I have a laptop with the BYD Trackpad and wanted to test your
patch. I applied your changes to the ubuntu-wily kernel source but
encountered the following error while rebuilding:
CC [M] drivers/input/mouse/byd.o
/home/martin/Kernel/ubuntu-wily/drivers/input/mouse/byd.c:159:5: error
In byd.h I think `#ifdef CONFIG_MOUSE_BYD` should be `#ifdef
CONFIG_MOUSE_PS2_BYD`.
--
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/1424293
Title:
BYD trackpad detected as PS/2 mouse
Sta
I've submitted a pull request to Raedwulf's 'byd' branch.
* https://github.com/raedwulf/linux/pull/1
I've successfully built the ubuntu-wily kernel with this driver added
and can confirm that multi touch and gestures are working. I've also
attached a diff for the ubuntu-wily kernel source.
*
Ugh, the comment above should say:
* git://kernel.ubuntu.com/ubuntu/ubuntu-wily.git
--
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/1424293
Title:
BYD trackpad detected as PS/2 mouse
A kernel for 15.10, including this patch, is available for testing here:
* https://launchpad.net/~flexiondotorg/+archive/ubuntu/kernel-stuff
--
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
The Stack Overflow comments suggest this is resolved -
http://stackoverflow.com/questions/30442719/getting-segmentation-fault-
when-using-rpi-gpio-setup-on-raspberry-pi-2
** Changed in: ubuntu-mate
Status: New => Invalid
--
You received this bug notification because you are a member of Ke
Just tested booting and installing my iBook G4 with Ubuntu MATE 15.10
daily. It booted from DVD using only 'live' and the install completed
successfully. Some PowerPC related bugs have been fixed this cycle:
* https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1471185
* https://bugs.la
Is this related?
* https://bugs.launchpad.net/ubuntu/+source/b43-fwcutter/+bug/1490212
--
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/1498074
Title:
Package is not being installed if
** 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
I'm now stuck*
--
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/1492764
Title:
[drm:intel_pipe_config_compare [i915]] *ERROR* mismatch in ips_enabled
(expected 1, found 0)
Status in lin
Another "me too" here. Decided since 15.10 was close to release that I'd
upgrade. I'm not stuck with X not starting at all, with "*ERROR*
mismatch in ips_enabled (expected 1, found 0)" just scrolling across the
logs. I'm not sure if it's the same as other reports, because I can't
start X _at all_,
@Christopher, thank you for the offer! As it turns out, I don't think
the root cause is the kernel. If I switch back to lightdm, I'm able to
successfully start X, so I think the messages I'm seeing are the same in
this bug, but they aren't the root cause of my particular problem (no
greeter, no X).
** 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
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1501993/+attachment/4481497/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
https://bugs.launchpa
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1501993/+attachment/4481498/+files/IwConfig.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
https://bugs.launchpad.net/bu
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1501993/+attachment/4481499/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
https://bugs.launch
apport information
** Attachment added: "AlsaInfo.txt"
https://bugs.launchpad.net/bugs/1501993/+attachment/4481495/+files/AlsaInfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
https://bugs.launchpad.net/bu
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1501993/+attachment/4481500/+files/Lspci.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1501
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1501993/+attachment/4481501/+files/Lsusb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1501
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1501993/+attachment/4481502/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
https://bugs.launchpad.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1501993/+attachment/4481503/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
https://bugs.launchpad.
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1501993/+attachment/4481512/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
https://bugs.launchpa
Public bug reported:
Hi there --
I'm seeing a kernel hang when I 'dock' my laptop into my docking station; this
happens with 4.2, specifically with:
linux-image-extra-4.2.0-11-generic
linux-image-extra-4.2.0-12-generic
Oct 1 21:38:33 mart6985-laptop kernel: [ 876.317186]
[drm:intel_dp_start_
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1501993/+attachment/4481504/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
https://bugs.laun
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1501993/+attachment/4481507/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
https://bugs.launchpad.net/bugs/15
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1501993/+attachment/4481505/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
https://bugs.launchpad.
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1501993/+attachment/4481496/+files/CRDA.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
https://bugs.launchpad.net/bugs/150199
apport information
** Attachment added: "UdevLog.txt"
https://bugs.launchpad.net/bugs/1501993/+attachment/4481508/+files/UdevLog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
https://bugs.launchpad.net/bugs
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1501993/+attachment/4481511/+files/CRDA.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
https://bugs.launchpad.net/bugs/150199
apport information
** Attachment added: "AlsaInfo.txt"
https://bugs.launchpad.net/bugs/1501993/+attachment/4481510/+files/AlsaInfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
https://bugs.launchpad.net/bu
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1501993/+attachment/4481506/+files/RfKill.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
https://bugs.launchpad.net/bugs/15
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1501993/+attachment/4481509/+files/WifiSyslog.txt
** Description changed:
Hi there --
I'm seeing a kernel hang when I 'dock' my laptop into my docking station;
this happens with 4.2, specifically
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1501993/+attachment/4481519/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
https://bugs.launchpad.
apport information
** Attachment added: "UdevLog.txt"
https://bugs.launchpad.net/bugs/1501993/+attachment/4481524/+files/UdevLog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
https://bugs.launchpad.net/bugs
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1501993/+attachment/4481513/+files/Dependencies.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
https://bugs.launchpa
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1501993/+attachment/4481514/+files/IwConfig.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
https://bugs.launchpad.net/bu
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1501993/+attachment/4481520/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
https://bugs.laun
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1501993/+attachment/4481516/+files/Lspci.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1501
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1501993/+attachment/4481515/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
https://bugs.launch
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1501993/+attachment/4481517/+files/Lsusb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1501
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1501993/+attachment/4481522/+files/RfKill.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
https://bugs.launchpad.net/bugs/15
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1501993/+attachment/4481518/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
https://bugs.launchpad.
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1501993/+attachment/4481523/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
https://bugs.launchpad.net/bugs/15
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1501993/+attachment/4481521/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
https://bugs.launchpad.
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1501993/+attachment/4481525/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
https://bugs.launchpad.ne
Hi Chris,
When using Google, A14 showed up as the latest, and I had tried that
before the bug report. D'oh! I've just upgraded to A15, and I'm still
seeing the problem. Here's the new dmidecode output:
Handle 0x, DMI type 0, 24 bytes
BIOS Information
Vendor: Dell Inc.
Version:
After the lines from the last comment ended, on bios A15, I had to hard
reboot. These lines were especially interesting to me:
Oct 3 10:08:17 mart6985-laptop kernel: [ 156.905626] ACPI Error: Index value
0x0083 overflows field width 0x7 (20150619/exfldio-341)
Oct 3 10:08:17 mart698
Tag added. Let me know if the ACPI error means I should keep testing
further older mainline kernels or not. 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/1501993
Title:
drivers/
Hello again!
I started by testing 4.3.0-040300rc3-generic. This seems to have fixed
the hang, but I still see log lines that seem problematic:
Oct 4 09:18:41 mart6985-laptop kernel: [ 56.385682] acpi PNP0401:00: Already
enumerated
Oct 4 09:18:41 mart6985-laptop kernel: [ 56.389467] acpi de
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,
or leave it open. Thanks!
- Martin
--
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/1501993
Title:
drivers/gpu/drm/i915/intel_display.c:12326
check_crtc_state+0x2c5/0x440 [i915]()
Status i
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
Still present in Ubuntu 15.10 daily image on October 16th 2015.
--
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/1359689
Title:
cryptsetup password prompt not shown
Status in xserver-xorg
Public bug reported:
I have HP ZBook 15 (1st generation, 2013) with ubuntu-MATE 64-bit;
latest updates installed. I am presently using an ethernet cable network
so I turn the wireless network off. After each new start or reboot of
the machine the wifi radio gets always on and I always have to swit
No matter in which way I disable it. Both ways of controlling wireless
work perfectly and consistently (contrary to some previous versions of
ubuntu, e.g. 14.04). The only problem is that the system does not
remember its previous wifi status (On or Off) and always starts with
wireless networks On.
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
1501 - 1600 of 2223 matches
Mail list logo
