[Kernel-packages] [Bug 1410779] Re: Bluetooth adapter is not working in Ubuntu 14.04
Thanks Victor for your report. I am aware that you were trying: sudo rfkill unblock 3 [sudo] password for vestival: vestival@vestival01:~$ sudo rfkill list 0: tpacpi_wwan_sw: Wireless WAN Soft blocked: no Hard blocked: no 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no 3: hci0: Bluetooth Soft blocked: yes Hard blocked: no -- 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/1410779 Title: Bluetooth adapter is not working in Ubuntu 14.04 Status in bluez package in Ubuntu: New Bug description: Bluetooth is not working on Ubuntu 14.04 in a Lenovo t430s is not working ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: bluez 4.101-0ubuntu13 ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11 Uname: Linux 3.13.0-43-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 CurrentDesktop: Unity Date: Wed Jan 14 13:37:16 2015 InstallationDate: Installed on 2014-08-29 (137 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) InterestingModules: btusb bnep rfcomm bluetooth MachineType: LENOVO 23554M2 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-43-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/12/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G7ET96WW (2.56 ) dmi.board.asset.tag: Not Available dmi.board.name: 23554M2 dmi.board.vendor: LENOVO dmi.board.version: 0B98401 Pro dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG7ET96WW(2.56):bd09/12/2013:svnLENOVO:pn23554M2:pvrThinkPadT430s:rvnLENOVO:rn23554M2:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 23554M2 dmi.product.version: ThinkPad T430s dmi.sys.vendor: LENOVO hciconfig: mtime.conffile..etc.init.bluetooth.conf: 2015-01-02T13:44:45.063731 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1410779/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1393317] Re: Intel 7265 [8086:095b] Wireless disconnect automatically
I have Intel 7260ac, and since the last kernel update (3.13.0-44) connecton get lost every few minutes. So I stay on previous kernel (3.13.0-43) and the situation is better again -- 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/1393317 Title: Intel 7265 [8086:095b] Wireless disconnect automatically Status in HWE Next Project: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: Fix Released Status in linux source package in Trusty: Fix Released Status in linux-firmware source package in Trusty: Fix Released Status in linux source package in Utopic: Fix Released Status in linux-firmware source package in Utopic: Fix Released Bug description: SRU Justification: Impact: Intel's latest wireless adapter will disconnect automatically Fix: bump firmware API version to 9(the version 9 firmwares of 3160, 7260 and 7265 were already in trusty, but need an upgrade from 23.214.9.0 to the latest 25.222.9.0) Testcase: already tested with Intel 7265 [8086:095b] in OEM projects. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1393317/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1270676] Re: SD Card Reader broken on UX302LG
I can confirm it is also working for Asus BU401LA. Thanks for the fix! -- 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/1270676 Title: SD Card Reader broken on UX302LG Status in linux package in Ubuntu: Triaged Bug description: SD card reader (controller Alcor Micro AU6601) is dysfunctional in UX302LG laptop. USB readers work without problem. Nothing happens when pluggin SD/mSD/SDHC/mSDHC cards in the reader (might as well use a piece of wood). Nothing is listed in lsusb -v that could be the reader. Nohting is listed in lspci -k -vv -nnn. Nothing in acpi_listen. Nothing in kern.log etc. According to (select Windows 8 then Card Reader) : http://support.asus.com/download.aspx?SLanguage=enp=3s=597m=UX302LGos=hashedid=GEZaY8oaj8oSlQ3U Reader vendor is : Alcor Multi-Card Reader Driver http://www.pcidatabase.com/vendor_details.php?id=1672 There is only one device that is Unassigned class 1aea:6601 but searching this online only pops up my other bug reports (sigh) and vendor is unassigned on pcidatabase.com. But...Downloading the 14M Win driver for the reader, vendor id 1aea and device id 6601 is present at multiple instances : [DeviceList.NTamd64] ; For XP and later %AMPCIECR% = DriverInstall_6601, PCI\VEN_1aeaDEV_6601 Also there is mention of _Gen instance in the .inf, might point to a Generic alternative ? [DeviceList_Gen.NTamd64] ; For XP and later %AMPCIECR_GEN% = DriverInstall_Gen, PCI\VEN_105bDEV_0ef6 This does point to something totally different online 105b:0ef6 points to some Realtek HD Audio device... --- ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2013-12-31 (21 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20131231) Package: linux (not installed) Tags: trusty Uname: Linux 3.13.0-031300-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo --- ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=e6458b44-fdb9-4db5-8cac-40ee0bbf9cf6 InstallationDate: Installed on 2013-12-31 (21 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20131231) MachineType: ASUSTeK COMPUTER INC. UX302LG Package: linux (not installed) ProcFB: 0 simple ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-4-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash acpi_osi= nomodeset plymouth:debug vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-4.19-generic 3.13.0-rc8 RelatedPackageVersions: linux-restricted-modules-3.13.0-4-generic N/A linux-backports-modules-3.13.0-4-generic N/A linux-firmware1.121 Tags: trusty Uname: Linux 3.13.0-4-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 10/30/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX302LG.207 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX302LG dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX302LG.207:bd10/30/2013:svnASUSTeKCOMPUTERINC.:pnUX302LG:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX302LG:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX302LG dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1270676/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1410779] Re: Bluetooth adapter is not working in Ubuntu 14.04
Adding syslog with enhannced debugging information from bluetoothd. ** Attachment added: Syslog with -d passed to bluetoothd https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1410779/+attachment/4298384/+files/syslog -- 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/1410779 Title: Bluetooth adapter is not working in Ubuntu 14.04 Status in bluez package in Ubuntu: New Bug description: Bluetooth is not working on Ubuntu 14.04 in a Lenovo t430s is not working ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: bluez 4.101-0ubuntu13 ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11 Uname: Linux 3.13.0-43-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 CurrentDesktop: Unity Date: Wed Jan 14 13:37:16 2015 InstallationDate: Installed on 2014-08-29 (137 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) InterestingModules: btusb bnep rfcomm bluetooth MachineType: LENOVO 23554M2 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-43-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/12/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G7ET96WW (2.56 ) dmi.board.asset.tag: Not Available dmi.board.name: 23554M2 dmi.board.vendor: LENOVO dmi.board.version: 0B98401 Pro dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG7ET96WW(2.56):bd09/12/2013:svnLENOVO:pn23554M2:pvrThinkPadT430s:rvnLENOVO:rn23554M2:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 23554M2 dmi.product.version: ThinkPad T430s dmi.sys.vendor: LENOVO hciconfig: mtime.conffile..etc.init.bluetooth.conf: 2015-01-02T13:44:45.063731 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1410779/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1392820] Re: CVE-2014-7841
** Changed in: linux-lts-trusty (Ubuntu Precise) Status: Fix Committed = Fix Released ** Changed in: linux-lts-utopic (Ubuntu Trusty) Status: Fix Committed = Fix Released ** Changed in: linux (Ubuntu Trusty) Status: Fix Committed = Fix Released ** Changed in: linux (Ubuntu Utopic) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1392820 Title: CVE-2014-7841 Status in linux package in Ubuntu: Fix Committed Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-lts-backport-maverick package in Ubuntu: New Status in linux-lts-backport-natty package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Lucid: Fix Released Status in linux-armadaxp source package in Lucid: Invalid Status in linux-ec2 source package in Lucid: Fix Released Status in linux-fsl-imx51 source package in Lucid: Invalid Status in linux-lts-backport-maverick source package in Lucid: New Status in linux-lts-backport-natty source package in Lucid: New Status in linux-lts-quantal source package in Lucid: Invalid Status in linux-lts-raring source package in Lucid: Invalid Status in linux-lts-saucy source package in Lucid: Invalid Status in linux-lts-trusty source package in Lucid: Invalid Status in linux-lts-utopic source package in Lucid: Invalid Status in linux-mvl-dove source package in Lucid: Invalid Status in linux-ti-omap4 source package in Lucid: Invalid Status in linux source package in Precise: Fix Released Status in linux-armadaxp source package in Precise: Fix Released Status in linux-ec2 source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: New Status in linux-lts-backport-natty source package in Precise: New Status in linux-lts-quantal source package in Precise: Fix Committed Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Fix Committed Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Released Status in linux source package in Trusty: Fix Released Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Fix Released Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Utopic: Fix Released Status in linux-armadaxp source package in Utopic: Invalid Status in linux-ec2 source package in Utopic: Invalid Status in linux-fsl-imx51 source package in Utopic: Invalid Status in linux-lts-backport-maverick source package in Utopic: New Status in linux-lts-backport-natty source package in Utopic: New Status in linux-lts-quantal source package in Utopic: Invalid Status in linux-lts-raring source package in Utopic: Invalid Status in linux-lts-saucy source package in Utopic: Invalid Status in linux-lts-trusty source package in Utopic: Invalid Status in linux-lts-utopic source package in Utopic: Invalid Status in linux-mvl-dove source package in Utopic: Invalid Status in linux-ti-omap4 source package in Utopic: Invalid Status in linux source package in Vivid: Fix Committed Status in linux-armadaxp source package in Vivid: Invalid Status in linux-ec2 source package in Vivid: Invalid Status in linux-fsl-imx51 source package in Vivid: Invalid Status in linux-lts-backport-maverick source package in Vivid: New Status in linux-lts-backport-natty source package in Vivid: New Status in linux-lts-quantal source package in Vivid: Invalid Status in
[Kernel-packages] [Bug 1410363] Re: partition table updates require a reboot
** Changed in: linux (Ubuntu)
Assignee: (unassigned) = Stefan Bader (smb)
--
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/1410363
Title:
partition table updates require a reboot
Status in linux package in Ubuntu:
Confirmed
Bug description:
We're seeing a problem in automated testing of ceph and swift in that
partition tables always require a reboot:
2015-01-13 16:50:07 INFO mon-relation-changed Setting name!
2015-01-13 16:50:07 INFO mon-relation-changed partNum is 1
2015-01-13 16:50:07 INFO mon-relation-changed REALLY setting name!
2015-01-13 16:50:07 INFO mon-relation-changed Warning: The kernel is still
using the old partition table.
2015-01-13 16:50:07 INFO mon-relation-changed The new table will be used at
the next reboot.
2015-01-13 16:50:07 INFO mon-relation-changed The operation has completed
successfully.
2015-01-13 16:50:09 INFO mon-relation-changed Setting name!
2015-01-13 16:50:09 INFO mon-relation-changed partNum is 0
2015-01-13 16:50:09 INFO mon-relation-changed REALLY setting name!
2015-01-13 16:50:09 INFO mon-relation-changed Warning: The kernel is still
using the old partition table.
2015-01-13 16:50:09 INFO mon-relation-changed The new table will be used at
the next reboot.
2015-01-13 16:50:09 INFO mon-relation-changed The operation has completed
successfully.
2015-01-13 16:50:09 INFO mon-relation-changed mkfs.xfs: cannot open
/dev/vdb1: Device or resource busy
2015-01-13 16:50:09 INFO mon-relation-changed ceph-disk: Error: Command
'['/sbin/mkfs', '-t', 'xfs', '-f', '-i', 'size=2048', '--', '/dev/vdb1']'
returned non-zero exit status 1
2015-01-13 16:50:09 ERROR juju-log mon:1: Unable to initialize device:
/dev/vdb
2015-01-13 16:50:09 INFO mon-relation-changed Traceback (most recent call
last):
2015-01-13 16:50:09 INFO mon-relation-changed File
/var/lib/juju/agents/unit-ceph-0/charm/hooks/mon-relation-changed, line 381,
in module
2015-01-13 16:50:09 INFO mon-relation-changed hooks.execute(sys.argv)
2015-01-13 16:50:09 INFO mon-relation-changed File
/var/lib/juju/agents/unit-ceph-0/charm/hooks/charmhelpers/core/hookenv.py,
line 528, in execute
2015-01-13 16:50:09 INFO mon-relation-changed self._hooks[hook_name]()
2015-01-13 16:50:09 INFO mon-relation-changed File
/var/lib/juju/agents/unit-ceph-0/charm/hooks/mon-relation-changed, line 217,
in mon_relation
2015-01-13 16:50:09 INFO mon-relation-changed reformat_osd(),
config('ignore-device-errors'))
2015-01-13 16:50:09 INFO mon-relation-changed File
/var/lib/juju/agents/unit-ceph-0/charm/hooks/ceph.py, line 327, in osdize
2015-01-13 16:50:09 INFO mon-relation-changed osdize_dev(dev, osd_format,
osd_journal, reformat_osd, ignore_errors)
2015-01-13 16:50:09 INFO mon-relation-changed File
/var/lib/juju/agents/unit-ceph-0/charm/hooks/ceph.py, line 375, in osdize_dev
2015-01-13 16:50:09 INFO mon-relation-changed raise e
2015-01-13 16:50:09 INFO mon-relation-changed subprocess.CalledProcessError:
Command '['ceph-disk-prepare', '--fs-type', u'xfs', '--zap-disk', u'/dev/vdb']'
returned non-zero exit status 1
this is obviously blocking deployment and subsequent testing; previous
Ubuntu releases have been OK.
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: linux-image-generic (not installed)
ProcVersionSignature: User Name 3.18.0-8.9-generic 3.18.1
Uname: Linux 3.18.0-8-generic x86_64
AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code
2: ls: cannot access /dev/snd/: No such file or directory
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.15.1-0ubuntu2
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
CRDA: Error: [Errno 2] No such file or directory: 'iw'
Date: Tue Jan 13 16:51:36 2015
Ec2AMI: ami-006e
Ec2AMIManifest: FIXME
Ec2AvailabilityZone: nova
Ec2InstanceType: m1.small
Ec2Kernel: aki-0002
Ec2Ramdisk: ari-0002
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: OpenStack Foundation OpenStack Nova
PciMultimedia:
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.18.0-8-generic
root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0
RelatedPackageVersions:
linux-restricted-modules-3.18.0-8-generic N/A
linux-backports-modules-3.18.0-8-generic N/A
linux-firmwareN/A
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/01/2011
dmi.bios.vendor: Bochs
dmi.bios.version: Bochs
dmi.chassis.type: 1
dmi.chassis.vendor: Bochs
dmi.modalias:
