apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1628968/+attachment/4751089/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1628968/+attachment/4751083/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1628968/+attachment/4751090/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1628968/+attachment/4751084/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1628968/+attachment/4751086/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
Not much else to say. The system fails to complete booting, it gets
stuck somewhere before network comes up; with errors in syslog about
missing symbols for some modules (see
http://paste.ubuntu.com/23251408/). Boots fine in 4.4.0-21:
Sep 28 12:49:55 fujin kernel: [
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1628968/+attachment/4751082/+files/CRDA.txt
--
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/1628968
*** This bug is a duplicate of bug 1624096 ***
https://bugs.launchpad.net/bugs/1624096
** This bug has been marked a duplicate of bug 1624096
yakkety: backport (or rebase to) fix eliminating a double-close in shim
--
You received this bug notification because you are a member of Kernel
This is bug 1624096.
--
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/1627875
Title:
Yakkety server Beta install fails in a virtual client with UEFI bios
Status in Ubuntu Manual Tests:
Verification-successful for shim-signed on precise --- all that is
required is there: the update-secureboot-policy script does what it
should and is run as expected.
However, it looks like MokManager.efi (which isn't something coming from
shim-signed) isn't installed on the system under
efivar for trusty ended up not being needed.
** Changed in: efivar (Ubuntu Trusty)
Status: Fix Committed => Fix Released
--
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/1574727
Given that the solution presented here on the same kind of system was to
set:
nomodeset acpi_osi=
It sounds a lot more like an issue in the kernel. Disabling Secure Boot
should not impact the system if it reaches the point of the boot splash
(the purple screen with the Ubuntu logo in the center,
Verification done for XENIAL: grub2-signed, dkms, shim-signed all found
to be working as expected. Test cases pass. As previously discussed, the
grub2-signed update is not especially useful in itself and does need to
drop the calls to mokutil, but will need a further SRU to remove calling
Verification-done for TRUSTY: efivar, mokutil, dkms, shim-signed all
found to be working at expected. Test cases pass.
** Tags added: verification-done-trusty
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
Verification-done for WILY: mokutil, dkms, shim-signed all found to be
working as expected. Test cases pass.
--
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/1574727
Title:
[SRU] Enforce
** Description changed:
[Rationale]
Secure Boot is good. We want to be able to validate that as much as possible
of the boot process happens with signed binaries; from our shim (the part that
is loaded by the EFI firmware itself), down to grub2, the kernel, and even
loaded modules.
precise:
- verified efivar & sbsigntool
- verified mokutil
Verification passes for these SRUs.
** Tags added: verification-done-precise
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
** Changed in: shim-signed (Ubuntu Wily)
Status: New => In Progress
** Changed in: shim-signed (Ubuntu Trusty)
Status: New => In Progress
** Changed in: shim-signed (Ubuntu Precise)
Status: New => In Progress
--
You received this bug notification because you are a member
** Also affects: efibootmgr (Ubuntu)
Importance: Undecided
Status: New
** Changed in: efibootmgr (Ubuntu)
Status: New => Fix Released
** Changed in: efibootmgr (Ubuntu Xenial)
Status: New => Fix Released
** Changed in: efibootmgr (Ubuntu Wily)
Status: New => Fix
** Changed in: shim-signed (Ubuntu)
Importance: Undecided => High
** Changed in: shim-signed (Ubuntu)
Status: New => Fix Released
** Changed in: shim-signed (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)
--
You received this bug notification be
** Also affects: shim-signed (Ubuntu)
Importance: Undecided
Status: New
--
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/1574727
Title:
[SRU] Enforce using signed kernels and
t; Fix Released
** Changed in: grub2-signed (Ubuntu Xenial)
Status: New => In Progress
** Changed in: grub2-signed (Ubuntu Xenial)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)
** Changed in: grub2-signed (Ubuntu Xenial)
Importance: Undecided => Medium
** Ch
dium
** Changed in: grub2 (Ubuntu Xenial)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)
** Changed in: grub2 (Ubuntu Xenial)
Status: New => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in
Triaged
** Changed in: grub-installer (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)
--
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/1507505
Title:
NVME p
** Also affects: efivar (Ubuntu)
Importance: Undecided
Status: New
** Also affects: grub2 (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: dkms (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: shim (Ubuntu Precise)
That should have read, any version of mokutil below 0.3.0-0ubuntu3~ will
not work correctly with lts kernels on the LTS releases.
--
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/1574727
This also needs a mokutil update, as the version in >=14.04 will not
work correctly with *-lts* kernels.
** Also affects: mokutil (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms
Public bug reported:
[Rationale]
Secure Boot is good. We want to be able to validate that as much as possible of
the boot process happens with signed binaries; from our shim (the part that is
loaded by the EFI firmware itself), down to grub2, the kernel, and even loaded
modules.
[Impact]
All
There isn't much here to indicate anything is wrong with
NetworkManager's handling of the wireless interface. This looks rather
like a kernel issue, or at least the driver being confused by the device
renaming done by udev rules/systemd.
Nis 12 20:07:35 instantcrush-XPS-13-9350 kernel:
AFAICT systemtap works well in xenial with the latest version:
systemtap (2.9-2ubuntu2) xenial; urgency=medium
* d/p/0001-Fix-PR9497-by-updating-the-runtime-to-handle-linux-4.patch:
Fix stap compilation after kernel 4.4 commit 7523e4dc50. (LP: #1557673)
** Changed in: systemtap (Ubuntu
riaged
** Changed in: grub2 (Ubuntu)
Status: New => Triaged
** Changed in: dkms (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (mathieu-tl)
** Changed in: grub2 (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (mathieu-tl)
--
You received this bug notificat
Reassigning to grub2, which seems more appropriate at a quick glance.
I'll look to reproduce this tomorrow.
** Package changed: linux (Ubuntu) => grub2 (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Adam,
Generally this looks pretty good; but let's focus on just the modaliases
issues for this bug. Can you file separate bug reports for the other
problems?
As for software-properties, I suspect there are probably no issues
there; everything can be fixed by modifying just b43-fwcutter (by the
** Changed in: bcmwl (Ubuntu)
Status: New => In Progress
** Changed in: bcmwl (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (mathieu-tl)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bcmwl in Ubuntu.
Could you please share the partition layout for that system? Which
partitioning method you picked or if you specified some manual
partitioning. Also, please include how many disks are included, of what
size. I will try to reproduce this bug in a virtual machine for further
debugging.
** Changed
One of the aspects of this is to ship opal-prd tools in the archive; for
that, we need uapi/asm/opal-prd.h (but it will also require the opal-prd
device to exist to be of any use) to be available on each of the
releases on which the opal-prd tools need to be shipped -- see bug
1467542.
--
You
Public bug reported:
multipath-tools 0.5.0 has changed the default path selector algorithm
from round-robin to service-time.
In the interest of properly handling the transition, I'd like for
multipath-modules to ship *both* dm-round-robin and dm-service-time, so
that we don't need to coordinate
For grub2 we're still waiting to see the result of running '/usr/sbin
/grub-probe --device /dev/sda1 --target=fs_uuid' under strace, so
setting the status to Incomplete..
** Changed in: grub2 (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member
Reassigning to the linux package; the kernel team would more likely know
if there is a fix available for this.
** Package changed: ubuntu = linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Reassigning to linux; this seems most likely to be a filesystem/ibmvfc
driver issue.
** Package changed: 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/1446064
Reassigning to Linux. NM is not responsible for negotiating duplex;
performance issues caused by this would probably warrant looking into
what the driver does.
** Package changed: network-manager (Ubuntu) = linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Given that this is reportedly fixed by updating a driver, it's not a bug
in NetworkManager (so I'm removing the task, we don't need to track it
there).
Also, as a further data point, I wonder how running a low-latency might
affect things like wifi performance. I think it's not impossible that it
I meant ubuntu-reviewers, above.
** Tags removed: patch
--
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/1409102
Title:
WiFi is slower on Ubuntu than Windows.
Status in The Linux
Also, since the attached files aren't patches but rather deb packages,
I'll go ahead and undo the patch tag and flags.
Could you try and communicate with Bogdan Koval (bodyakov), and see if
you guys could come up with a proper patch in diff format for the
changes required? Then attach it here
** Also affects: linux (Ubuntu Utopic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Vivid)
Importance: Critical
Assignee: Mathieu Trudel-Lapierre (mathieu-tl)
Status: Triaged
** Changed in: linux (Ubuntu Utopic)
Status: New = Triaged
Trudel-Lapierre (mathieu-tl) = (unassigned)
--
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/1162781
Title:
bluez package out of date, 5.23 is available in debian sid/jessie
Status
don't know
what was the difference.
** Changed in: bluez (Ubuntu)
Assignee: Mathieu Trudel-Lapierre (mathieu-tl) = (unassigned)
** Changed in: bluez (Ubuntu)
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which
I see it was fixed in utopic for d-i already; are we good on vivid too?
--
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/1386490
Title:
HP ProLiant m400 nic doesn't work after trusty
I can't exactly test that IPv6 is fine in general with this, but it
doesn't appear to have regressed on Trusty.
--
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/994931
Title:
Altering
, simple patch that someone looking to start
working on Ubuntu development could easily put together in the package
and submit for review and sponsored upload. I tagged this bitesize.
** Tags added: bitesize
** Changed in: bluez (Ubuntu)
Assignee: Mathieu Trudel-Lapierre (mathieu-tl) = (unassigned
*** This bug is a duplicate of bug 1419874 ***
https://bugs.launchpad.net/bugs/1419874
marking as a duplicate of bug 1419874
** This bug has been marked a duplicate of bug 1419874
krillin bluetooth discoverability enabled on boot
--
You received this bug notification because you are a
Esokrates, could you try to boot your system after adding
'plymouth:debug' to the kernel command line in grub; and attaching
/var/log/plymouth-debug.log; first making sure it doesn't include your
passphrase for the disk encryption? If that doesn't trigger the bug, you
may need to edit
** Changed in: plymouth (Ubuntu)
Status: Incomplete = Triaged
** 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.
In that case we'll need the logs from ubuntu-system-settings; on re-
connection there should be a message, something like Host down or
Connection refused. Perhaps there is something extra we need to do in
this particular case for the headset to be happy with re-connecting.
--
You received this
We're reportedly already bulding the other ibmv* modules as builtin, so
I'm opening a task for linux so the Kernel Team can weigh in making this
one builtin as well, or if it would be preferable to just keep it in
initrd.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
This change is now in vivid as well:
grub2 (2.02~beta2-21) unstable; urgency=medium
.
[ Mathieu Trudel-Lapierre ]
* Fix overlap check in check_blocklists for load_env (backported patch
from upstream commit 1f6af2a9; LP: #1311247).
.
[ Steve McIntyre ]
* Add support for running
Could you also try to re-pair the speaker by pressing a button after the
system is resumed?
** Package changed: bluez-utils (Ubuntu) = bluez (Ubuntu)
** Changed in: bluez (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Kernel
Packages,
It looks like any moving of a file which comes from the read-only
underlying filesystem. It doesn't behave the same when one deletes a
file instead of moving.
It seems like it's probably a bug in overlayfs, so I'm adding a task for
linux so the kernel team can take a look.
** Also affects: linux
ApportVersion: 2.15.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ubuntu 2119 F pulseaudio
CasperVersion: 1.347
DistroRelease: Ubuntu 15.04
InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity
apport information
** Attachment added: AlsaInfo.txt
https://bugs.launchpad.net/bugs/1408495/+attachment/4300046/+files/AlsaInfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: CurrentDmesg.txt
https://bugs.launchpad.net/bugs/1408495/+attachment/4300050/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: CRDA.txt
https://bugs.launchpad.net/bugs/1408495/+attachment/4300048/+files/CRDA.txt
--
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/1408495
apport information
** Attachment added: Dependencies.txt
https://bugs.launchpad.net/bugs/1408495/+attachment/4300051/+files/Dependencies.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: Casper.txt
https://bugs.launchpad.net/bugs/1408495/+attachment/4300049/+files/Casper.txt
--
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/1408495
apport information
** Attachment added: ProcCpuinfo.txt
https://bugs.launchpad.net/bugs/1408495/+attachment/4300055/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: BootDmesg.txt
https://bugs.launchpad.net/bugs/1408495/+attachment/4300047/+files/BootDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: Lspci.txt
https://bugs.launchpad.net/bugs/1408495/+attachment/4300052/+files/Lspci.txt
--
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/1408495
apport information
** Attachment added: UbiquityDebug.txt
https://bugs.launchpad.net/bugs/1408495/+attachment/4300058/+files/UbiquityDebug.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: UbiquityDm.txt
https://bugs.launchpad.net/bugs/1408495/+attachment/4300059/+files/UbiquityDm.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: UdevDb.txt
https://bugs.launchpad.net/bugs/1408495/+attachment/4300062/+files/UdevDb.txt
--
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/1408495
apport information
** Attachment added: ProcInterrupts.txt
https://bugs.launchpad.net/bugs/1408495/+attachment/4300056/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: UbiquitySyslog.txt
https://bugs.launchpad.net/bugs/1408495/+attachment/4300061/+files/UbiquitySyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: UpstartUbiquity.txt
https://bugs.launchpad.net/bugs/1408495/+attachment/4300064/+files/UpstartUbiquity.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: UbiquityPartman.txt
https://bugs.launchpad.net/bugs/1408495/+attachment/4300060/+files/UbiquityPartman.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: UdevLog.txt
https://bugs.launchpad.net/bugs/1408495/+attachment/4300063/+files/UdevLog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: ProcModules.txt
https://bugs.launchpad.net/bugs/1408495/+attachment/4300057/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: WifiSyslog.txt
https://bugs.launchpad.net/bugs/1408495/+attachment/4300065/+files/WifiSyslog.txt
** Changed in: linux (Ubuntu Vivid)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Kernel
*** This bug is a duplicate of bug 1410480 ***
https://bugs.launchpad.net/bugs/1410480
This seems like a duplicate of bug 1410480.
** This bug has been marked a duplicate of bug 1410480
overlayfs v1: renaming existing file uses chardev whiteout (should be
symlink)
--
You received this
** Also affects: canonical-devices-system-image
Importance: Undecided
Status: New
--
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/1400827
Title:
BlueZ crashing when connecting
(Ubuntu RTM)
Importance: Undecided = High
** Changed in: bluez (Ubuntu RTM)
Assignee: (unassigned) = Mathieu Trudel-Lapierre (mathieu-tl)
** Changed in: bluez (Ubuntu)
Assignee: (unassigned) = Mathieu Trudel-Lapierre (mathieu-tl)
--
You received this bug notification because you
This still looks like a bug that should have been fixed by bluez
4.101-0ubuntu21; could you please confirm that this is indeed the
version of bluez that was installed, and running, on the system when you
got the crash?
I'm saying fixed, because it's been tested on some hardware,
specifically for
There were mentions of it happening after a resume from hibernate. Teo,
could you please confirm whether or not you've used hibernate again and
if it has triggered the bug? You mention later that it happens randomly,
but I just want to make it very certain that it can't be reliably
triggered by
-system-settings (Ubuntu)
Assignee: (unassigned) = Mathieu Trudel-Lapierre (mathieu-tl)
--
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/1369964
Title:
Cannot disconnect BQ Vivaldi
I uploaded the fixes for both gnome-bluetooth and bluez to trusty;
pending review by the SRU team.
** Description changed:
+ [Impact]
+
+ * Fixes issues connecting bluetooth devices using SSP (Simple Secure
+ Pairing); which does include many newer bluetooth devices, especially
+ keyboards.
+
Oh, I was really expecting this would have worked from the start; with
the changes that were made recently to allow it to pair.
Please, could you provide /home/phablet/.cache/upstart/application-
legacy-ubuntu-system-settings-.log ? As I recall, this particular device
doesn't do HSP; so we need
The fix for this has landed in RTM: ubuntu-system-settings
(0.3+14.10.20140909~rtm-0ubuntu1).
It is now available in the proposed RTM image; so I'll mark this as Fix
Released.
** Changed in: bluez (Ubuntu)
Status: New = Fix Released
--
You received this bug notification because you are
I think we can mark this as Fix Released by now; fixes for this have
been landed in ubuntu-touch and ubuntu-rtm images for a while and we've
tested it, it does appear to work properly.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez
Hmm, this didn't include the information I expected. Here's a different
command to use, again with the speaker in range:
hcitool inq
You should get a list of all the devices in range and their class, etc.;
the class information is what I need.
In the meantime, I'll dig in the code and make sure
** Changed in: bluez (Ubuntu)
Status: Fix Committed = Fix Released
--
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/1273629
Title:
HSP fails on Ubuntu Touch [Bluetooth headset does
:
hcitool info bluetooth address
** Changed in: bluez (Ubuntu)
Status: New = Incomplete
** Changed in: bluez (Ubuntu)
Assignee: (unassigned) = Mathieu Trudel-Lapierre (mathieu-tl)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
: Undecided = Medium
** Changed in: gnome-bluetooth (Ubuntu Trusty)
Importance: Undecided = High
** Changed in: gnome-bluetooth (Ubuntu Trusty)
Assignee: (unassigned) = Mathieu Trudel-Lapierre (mathieu-tl)
** Changed in: bluez (Ubuntu Trusty)
Assignee: (unassigned) = Mathieu Trudel
)
Assignee: (unassigned) = Mathieu Trudel-Lapierre (mathieu-tl)
** Summary changed:
- Can't pair any Bluetooth audio device with Ubuntu Touch
+ [bluetooth] Can't pair PIN-requiring audio devices with Ubuntu Touch
--
You received this bug notification because you are a member of Kernel
Packages
Closing as Invalid since the issue is reportedly solve, but we don't
know why/how the other mouse does not work.
Sorry for the delay in responding.
** Changed in: bluez (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Kernel
Packages,
Thanks, closing as Invalid.
** Changed in: bluez (Ubuntu)
Status: New = Invalid
--
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/1212287
Title:
bluetooth will not reconnect after
The fact that this is fixed just by enabling module-bluetooth-discover,
I think we should definitely investigate whether this is something
broken by blueman... reassigning.
** Also affects: blueman (Ubuntu)
Importance: Undecided
Status: New
** Changed in: blueman (Ubuntu)
*** This bug is a duplicate of bug 1285948 ***
https://bugs.launchpad.net/bugs/1285948
** This bug has been marked a duplicate of bug 1285948
Can't send files over bluetooth
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in
*** This bug is a duplicate of bug 1285948 ***
https://bugs.launchpad.net/bugs/1285948
** This bug has been marked a duplicate of bug 1285948
Can't send files over bluetooth
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in
*** This bug is a duplicate of bug 1285948 ***
https://bugs.launchpad.net/bugs/1285948
** This bug has been marked a duplicate of bug 1285948
Can't send files over bluetooth
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in
*** This bug is a duplicate of bug 1285948 ***
https://bugs.launchpad.net/bugs/1285948
** This bug has been marked a duplicate of bug 1285948
Can't send files over bluetooth
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in
*** This bug is a duplicate of bug 1285948 ***
https://bugs.launchpad.net/bugs/1285948
** This bug has been marked a duplicate of bug 1285948
Can't send files over bluetooth
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in
101 - 200 of 236 matches
Mail list logo