[Kernel-packages] [Bug 1283938] Re: [Samsung NP535U4X-S01TH] Ubuntu 14.04 blank screen after wakeup from sleep

2014-06-10 Thread piyush
how can i fix this bug???
everyone here is posting the problems beings facednone with the solution !!!
what should i do ???

** 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/1283938

Title:
  [Samsung NP535U4X-S01TH] Ubuntu 14.04 blank screen after wakeup from
  sleep

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  In 14.04 after wakeup from suspend, the notebook screen goes blank
  while the OS and the hardware is awake (I can also press Ctrl+F1 and
  Ctrl+Alt+Del to reboot the system).

  Changeing "quiet splash" to "nomodeset" in /etc/default/grub allows
  the wakeup, but the pc is really slow (can't be used).

  WORKAROUND: This problem is not happening with the AMD property
  drivers.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xserver-xorg-video-ati 1:7.3.0-1ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3
  Uname: Linux 3.13.0-11-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon Feb 24 12:58:07 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 4.3.6, 3.13.0-11-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7500G] [1002:990a] 
(prog-if 00 [VGA controller])
     Subsystem: Samsung Electronics Co Ltd Device [144d:c660]
   Advanced Micro Devices, Inc. [AMD/ATI] Thames [Radeon HD 7550M/7570M/7650M] 
[1002:6841] (rev ff) (prog-if ff)
  InstallationDate: Installed on 2014-02-22 (1 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140218)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 535U4C
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-11-generic 
root=UUID=9f8c7e92-a6ea-41fd-9489-a256c8b9f5d5 ro quiet splash vt.handoff=7
  SourcePackage: xserver-xorg-video-ati
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/03/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P06RAF.N93.130403.LEO
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP535U4X-S01TH
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SEC_SW_REVISION_1234567890ABCD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP06RAF.N93.130403.LEO:bd04/03/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn535U4C:pvrP06RAF:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP535U4X-S01TH:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
  dmi.product.name: 535U4C
  dmi.product.version: P06RAF
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  version.compiz: compiz 1:0.9.11+14.04.20140218-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0~rc1-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0~rc1-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Mon Feb 24 12:54:54 2014
  xserver.configfile: default
  xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.15.0-1ubuntu6
  xserver.video_driver: radeon

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1283938/+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 892544] Re: Unity slow after resume from suspend

2015-06-25 Thread Piyush
** Also affects: systemd (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/892544

Title:
  Unity slow after resume from suspend

Status in linux package in Ubuntu:
  Expired
Status in systemd package in Ubuntu:
  New

Bug description:
  After resuming from suspend unity feels like it is very slow.

  How to play:

  Go to Unity Dash, show all applications, move icons up and down with
  the scroll bar, suspend and resume, perform the same operation and
  notice that is very slow.

  This already happens with the (cd or usb) of installation.

  This bug only happens with free radeon driver with driver fglrx does
  not happen.

  This only happens in unity, this does not happen in either Gnome Shell
  or Unity 2D.

  I do not know if it's a bug in Unity or compiz, but "unity --reset"
  solves the problem until the next suspend / resume.

  I do not know if this bug may be related to #782810 or #803943, but I
  did not notice any increase in CPU consumption.

  This bug occurs on a clean install of 11.10 [64 bits]   with a ATI
  Radeon 5770 graphics card,  Asus P6T Deluxe V2 Motherboard, Micro
  Intel Core™ i7-950 y SSD OCZ Vertex2.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/892544/+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


Re: [Kernel-packages] [Bug 1072730] Re: CPU fan constantly at high speed on Asus K53SM laptop

2013-08-10 Thread Piyush Puranik
Christopher, I managed to fix the bug by switching from the nouveau driver
to the nvidia proprietary driver. Then installing Optimus later. Thanks
though.

Sent from my Android™
On 11-Aug-2013 2:21 AM, "Christopher M. Penalver" <
christopher.m.penal...@gmail.com> wrote:

> Piyush Puranik, as per http://www.service.asus.com/#!downloads/c1wax an
> update is available for your BIOS (214). If you update to this, does it
> change anything?
>
> If not, could you please both specify what happened, and provide the
> output of the following terminal command:
> sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
>
> Thank you for your understanding.
>
> ** Description changed:
>
>   I have Ubuntu 12.04.1 LTS installed on my Asus K53SM alongside Windows
>   7. Ubuntu has been installed on a seperate partition and I am using the
>   GRUB loader for booting.
>
>   The CPU fan on my laptop is constantly at a very high speed irrespective
>   of whether I'm running any CPU intensive applications or not. The CPU's
>   reported temperature is 42 degrees centigrade (room temp is 28 degrees).
>   The air being ejected out of the system is cold and not warm enough to
>   warrant a high fan speed.
>
>   I have installed bumblebee to ensure that my Nvidia card is not
>   constantly running and I ensured that it is fully updated to the latest
>   version. All the reported updates have also been installed on Ubuntu.
>
> + WORKAROUND: Switching to the Nvidia proprietary drivers seems to have
> + drastically reduced the fan throttling.
> +
>   ProblemType: Bug
>   DistroRelease: Ubuntu 12.04
>   Package: linux-image-3.2.0-32-generic-pae 3.2.0-32.51
>   ProcVersionSignature: Ubuntu 3.2.0-32.51-generic-pae 3.2.30
>   Uname: Linux 3.2.0-32-generic-pae i686
>   AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
>   ApportVersion: 2.0.1-0ubuntu14
>   Architecture: i386
>   ArecordDevices:
> -   List of CAPTURE Hardware Devices 
> -  card 0: PCH [HDA Intel PCH], device 0: ALC269VB Analog [ALC269VB Analog]
> -Subdevices: 1/1
> -Subdevice #0: subdevice #0
> +   List of CAPTURE Hardware Devices 
> +  card 0: PCH [HDA Intel PCH], device 0: ALC269VB Analog [ALC269VB Analog]
> +Subdevices: 1/1
> +Subdevice #0: subdevice #0
>   AudioDevicesInUse:
> -  USERPID ACCESS COMMAND
> -  /dev/snd/controlC0:  piyush 2031 F pulseaudio
> +  USERPID ACCESS COMMAND
> +  /dev/snd/controlC0:  piyush 2031 F pulseaudio
>   Card0.Amixer.info:
> -  Card hw:0 'PCH'/'HDA Intel PCH at 0xdf00 irq 50'
> -Mixer name : 'Intel CougarPoint HDMI'
> -Components : 'HDA:10ec0269,10431ac3,00100100
> HDA:80862805,80860101,0010'
> -Controls  : 24
> -Simple ctrls  : 11
> +  Card hw:0 'PCH'/'HDA Intel PCH at 0xdf00 irq 50'
> +Mixer name : 'Intel CougarPoint HDMI'
> +Components : 'HDA:10ec0269,10431ac3,00100100
> HDA:80862805,80860101,0010'
> +Controls  : 24
> +Simple ctrls  : 11
>   Date: Mon Oct 29 19:18:15 2012
>   HibernationDevice: RESUME=UUID=c1fe8aa2-eadb-4d88-9a2a-a77346a7085e
>   InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386
> (20120817.3)
>   MachineType: ASUSTeK Computer Inc. K53SM
>   ProcEnviron:
> -  LANGUAGE=en_IN:en
> -  TERM=xterm
> -  PATH=(custom, no user)
> -  LANG=en_IN
> -  SHELL=/bin/bash
> +  LANGUAGE=en_IN:en
> +  TERM=xterm
> +  PATH=(custom, no user)
> +  LANG=en_IN
> +  SHELL=/bin/bash
>   ProcFB: 0 inteldrmfb
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-32-generic-pae
> root=UUID=5e0353be-ffe5-4b71-8616-dbc6e0767248 ro quiet splash vt.handoff=7
>   RelatedPackageVersions:
> -  linux-restricted-modules-3.2.0-32-generic-pae N/A
> -  linux-backports-modules-3.2.0-32-generic-pae  N/A
> -  linux-firmware1.79.1
> +  linux-restricted-modules-3.2.0-32-generic-pae N/A
> +  linux-backports-modules-3.2.0-32-generic-pae  N/A
> +  linux-firmware1.79.1
>   SourcePackage: linux
>   StagingDrivers: rts5139 mei
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 03/06/2012
>   dmi.bios.vendor: American Megatrends Inc.
>   dmi.bios.version: K53SM.211
>   dmi.board.asset.tag: To be filled by O.E.M.
>   dmi.board.name: K53SM
>   dmi.board.vendor: ASUSTeK Computer Inc.
>   dmi.board.version: 1.0
>   dmi.chassis.asset.tag: No Asset Tag
>   dmi.chassis.type: 9
>   dmi.chassis.vendor: ASUSTeK Computer Inc.
>   dmi.chassis.version: 1.0
>   dmi.modalias:
> dmi:

[Kernel-packages] [Bug 1913859] Re: RT3290 Bluetooth not finding any device

2021-01-30 Thread Piyush Santosh Mhatre
** Also affects: bluez (Ubuntu)
   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/1913859

Title:
  RT3290 Bluetooth not finding any device

Status in Ubuntu:
  New
Status in bluez package in Ubuntu:
  New

Bug description:
  Ubuntu :- 20.04 
  Hello I have RT3290 bluetooth in built and it was not working so I installed 
its latest driver from github whose version is 3.9.6 . Now its working but its 
not discoverable to any other device and also not finding any other device.
  Outout of command :- service bluetooth status

  ● bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
pre>
   Active: active (running) since Sat 2021-01-30 09:49:10 IST; 1h 0min ago
     Docs: man:bluetoothd(8)
     Main PID: 1389 (bluetoothd)
   Status: "Running"
    Tasks: 1 (limit: 4514)
   Memory: 2.0M
   CGroup: /system.slice/bluetooth.service
   └─1389 /usr/lib/bluetooth/bluetoothd

  Jan 30 09:49:07 Piyush-X55C systemd[1]: Starting Bluetooth service...
  Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Bluetooth daemon 5.53
  Jan 30 09:49:10 Piyush-X55C systemd[1]: Started Bluetooth service.
  Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Starting SDP server
  Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Bluetooth management interface 
1.>
  Jan 30 10:49:34 Piyush-X55C bluetoothd[1389]: Endpoint registered: 
sender=:1.66>
  Jan 30 10:49:34 Piyush-X55C bluetoothd[1389]: Endpoint registered: 
sender=:1.66>
  lines 1-18/18 (END)

  Output of command :- sudo btmgmt info

  Index list with 1 item
  hci0:   Primary controller
  addr A4:17:31:1D:65:54 version 4 manufacturer 91 class 0x00
  supported settings: powered connectable fast-connectable discoverable 
bondable link-security ssp br/edr debug-keys
  current settings: powered bondable ssp br/edr
  name Piyush-X55C

  Output of command :- bluetoothctl

  Agent registered
  [bluetooth]# scan on
  [bluetooth]# discoverable on
  [bluetooth]# scan on
  Failed to start discovery: org.bluez.Error.InProgress
  [bluetooth]# discoverable on
  Changing discoverable on succeeded
  [bluetooth]#

  Output of command :- sudo btmgmt find

  Unable to start discovery. status 0x0c (Not Supported)

  Output of command :- lspci -knn | grep Net -A3; lsusb

  02:00.0 Network controller [0280]: Ralink corp. RT3290 Wireless 802.11n 1T/1R 
PCIe [1814:3290]
  Subsystem: Foxconn International, Inc. RT3290 Wireless 802.11n 1T/1R PCIe 
[105b:e055]
  Kernel driver in use: rt2800pci
  Kernel modules: rt2800pci
  Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 003: ID 1bcf:2883 Sunplus Innovation Technology Inc.
  Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  Output of command :-dmesg | grep -i bluetooth

   [   12.851854] Bluetooth: Core ver 2.22
  [   12.851883] Bluetooth: HCI device and connection manager initialized
  [   12.851888] Bluetooth: HCI socket layer initialized
  [   12.851889] Bluetooth: L2CAP socket layer initialized
  [   12.851893] Bluetooth: SCO socket layer initialized
  [   67.399550] audit: type=1400 audit(1611909043.091:58): 
apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=875 
comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 
requested_mask="create" denied_mask="create"
  [   67.727240] audit: type=1400 audit(1611909043.419:60): 
apparmor="DENIED" operation="connect" profile="snap.bluez.bluez" 
name="/run/dbus/system_bus_socket" pid=875 comm="bluetoothd" 
requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
  [   67.929889] audit: type=1400 audit(1611909043.619:62): 
apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=1043 
comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 
requested_mask="create" denied_mask="create"
  [   67.930261] audit: type=1400 audit(1611909043.623:63): 
apparmor="DENIED" operation="connect" profile="snap.bluez.bluez" 
name="/run/dbus/system_bus_socket" pid=1043 comm="bluetoothd" 
requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
  [   68.194380] audit: type=1400

[Kernel-packages] [Bug 1913859] Re: RT3290 Bluetooth not finding any device

2021-01-30 Thread Piyush Santosh Mhatre
** Tags removed: bot-comment
** Tags added: kernel-bug package-conflict

-- 
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/1913859

Title:
  RT3290 Bluetooth not finding any device

Status in Ubuntu:
  New
Status in bluez package in Ubuntu:
  New

Bug description:
  Ubuntu :- 20.04 
  Hello I have RT3290 bluetooth in built and it was not working so I installed 
its latest driver from github whose version is 3.9.6 . Now its working but its 
not discoverable to any other device and also not finding any other device.
  Outout of command :- service bluetooth status

  ● bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
pre>
   Active: active (running) since Sat 2021-01-30 09:49:10 IST; 1h 0min ago
     Docs: man:bluetoothd(8)
     Main PID: 1389 (bluetoothd)
   Status: "Running"
    Tasks: 1 (limit: 4514)
   Memory: 2.0M
   CGroup: /system.slice/bluetooth.service
   └─1389 /usr/lib/bluetooth/bluetoothd

  Jan 30 09:49:07 Piyush-X55C systemd[1]: Starting Bluetooth service...
  Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Bluetooth daemon 5.53
  Jan 30 09:49:10 Piyush-X55C systemd[1]: Started Bluetooth service.
  Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Starting SDP server
  Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Bluetooth management interface 
1.>
  Jan 30 10:49:34 Piyush-X55C bluetoothd[1389]: Endpoint registered: 
sender=:1.66>
  Jan 30 10:49:34 Piyush-X55C bluetoothd[1389]: Endpoint registered: 
sender=:1.66>
  lines 1-18/18 (END)

  Output of command :- sudo btmgmt info

  Index list with 1 item
  hci0:   Primary controller
  addr A4:17:31:1D:65:54 version 4 manufacturer 91 class 0x00
  supported settings: powered connectable fast-connectable discoverable 
bondable link-security ssp br/edr debug-keys
  current settings: powered bondable ssp br/edr
  name Piyush-X55C

  Output of command :- bluetoothctl

  Agent registered
  [bluetooth]# scan on
  [bluetooth]# discoverable on
  [bluetooth]# scan on
  Failed to start discovery: org.bluez.Error.InProgress
  [bluetooth]# discoverable on
  Changing discoverable on succeeded
  [bluetooth]#

  Output of command :- sudo btmgmt find

  Unable to start discovery. status 0x0c (Not Supported)

  Output of command :- lspci -knn | grep Net -A3; lsusb

  02:00.0 Network controller [0280]: Ralink corp. RT3290 Wireless 802.11n 1T/1R 
PCIe [1814:3290]
  Subsystem: Foxconn International, Inc. RT3290 Wireless 802.11n 1T/1R PCIe 
[105b:e055]
  Kernel driver in use: rt2800pci
  Kernel modules: rt2800pci
  Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 003: ID 1bcf:2883 Sunplus Innovation Technology Inc.
  Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  Output of command :-dmesg | grep -i bluetooth

   [   12.851854] Bluetooth: Core ver 2.22
  [   12.851883] Bluetooth: HCI device and connection manager initialized
  [   12.851888] Bluetooth: HCI socket layer initialized
  [   12.851889] Bluetooth: L2CAP socket layer initialized
  [   12.851893] Bluetooth: SCO socket layer initialized
  [   67.399550] audit: type=1400 audit(1611909043.091:58): 
apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=875 
comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 
requested_mask="create" denied_mask="create"
  [   67.727240] audit: type=1400 audit(1611909043.419:60): 
apparmor="DENIED" operation="connect" profile="snap.bluez.bluez" 
name="/run/dbus/system_bus_socket" pid=875 comm="bluetoothd" 
requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
  [   67.929889] audit: type=1400 audit(1611909043.619:62): 
apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=1043 
comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 
requested_mask="create" denied_mask="create"
  [   67.930261] audit: type=1400 audit(1611909043.623:63): 
apparmor="DENIED" operation="connect" profile="snap.bluez.bluez" 
name="/run/dbus/system_bus_socket" pid=1043 comm="bluetoothd" 
requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
  [   68.194380] audit: type=1400

[Kernel-packages] [Bug 1913859] Re: RT3290 Bluetooth not finding any device

2021-01-30 Thread Piyush Santosh Mhatre
Have you seen the output of bluetoothctl I have given?

-- 
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/1913859

Title:
  RT3290 Bluetooth not finding any device

Status in Ubuntu:
  New
Status in bluez package in Ubuntu:
  New

Bug description:
  Ubuntu :- 20.04 
  Hello I have RT3290 bluetooth in built and it was not working so I installed 
its latest driver from github whose version is 3.9.6 . Now its working but its 
not discoverable to any other device and also not finding any other device.
  Outout of command :- service bluetooth status

  ● bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
pre>
   Active: active (running) since Sat 2021-01-30 09:49:10 IST; 1h 0min ago
     Docs: man:bluetoothd(8)
     Main PID: 1389 (bluetoothd)
   Status: "Running"
    Tasks: 1 (limit: 4514)
   Memory: 2.0M
   CGroup: /system.slice/bluetooth.service
   └─1389 /usr/lib/bluetooth/bluetoothd

  Jan 30 09:49:07 Piyush-X55C systemd[1]: Starting Bluetooth service...
  Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Bluetooth daemon 5.53
  Jan 30 09:49:10 Piyush-X55C systemd[1]: Started Bluetooth service.
  Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Starting SDP server
  Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Bluetooth management interface 
1.>
  Jan 30 10:49:34 Piyush-X55C bluetoothd[1389]: Endpoint registered: 
sender=:1.66>
  Jan 30 10:49:34 Piyush-X55C bluetoothd[1389]: Endpoint registered: 
sender=:1.66>
  lines 1-18/18 (END)

  Output of command :- sudo btmgmt info

  Index list with 1 item
  hci0:   Primary controller
  addr A4:17:31:1D:65:54 version 4 manufacturer 91 class 0x00
  supported settings: powered connectable fast-connectable discoverable 
bondable link-security ssp br/edr debug-keys
  current settings: powered bondable ssp br/edr
  name Piyush-X55C

  Output of command :- bluetoothctl

  Agent registered
  [bluetooth]# scan on
  [bluetooth]# discoverable on
  [bluetooth]# scan on
  Failed to start discovery: org.bluez.Error.InProgress
  [bluetooth]# discoverable on
  Changing discoverable on succeeded
  [bluetooth]#

  Output of command :- sudo btmgmt find

  Unable to start discovery. status 0x0c (Not Supported)

  Output of command :- lspci -knn | grep Net -A3; lsusb

  02:00.0 Network controller [0280]: Ralink corp. RT3290 Wireless 802.11n 1T/1R 
PCIe [1814:3290]
  Subsystem: Foxconn International, Inc. RT3290 Wireless 802.11n 1T/1R PCIe 
[105b:e055]
  Kernel driver in use: rt2800pci
  Kernel modules: rt2800pci
  Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 003: ID 1bcf:2883 Sunplus Innovation Technology Inc.
  Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  Output of command :-dmesg | grep -i bluetooth

   [   12.851854] Bluetooth: Core ver 2.22
  [   12.851883] Bluetooth: HCI device and connection manager initialized
  [   12.851888] Bluetooth: HCI socket layer initialized
  [   12.851889] Bluetooth: L2CAP socket layer initialized
  [   12.851893] Bluetooth: SCO socket layer initialized
  [   67.399550] audit: type=1400 audit(1611909043.091:58): 
apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=875 
comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 
requested_mask="create" denied_mask="create"
  [   67.727240] audit: type=1400 audit(1611909043.419:60): 
apparmor="DENIED" operation="connect" profile="snap.bluez.bluez" 
name="/run/dbus/system_bus_socket" pid=875 comm="bluetoothd" 
requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
  [   67.929889] audit: type=1400 audit(1611909043.619:62): 
apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=1043 
comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 
requested_mask="create" denied_mask="create"
  [   67.930261] audit: type=1400 audit(1611909043.623:63): 
apparmor="DENIED" operation="connect" profile="snap.bluez.bluez" 
name="/run/dbus/system_bus_socket" pid=1043 comm="bluetoothd" 
requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
  [   68.194380] audit: type=1400 audit(1611909043.887:65): 
app

[Kernel-packages] [Bug 1913859] Re: RT3290 Bluetooth not finding any device

2021-01-31 Thread Piyush Santosh Mhatre
I ran the command apport-collect 1913859 and it gives me no additional
info collected. @Jeremy(wa113y3s)

-- 
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/1913859

Title:
  RT3290 Bluetooth not finding any device

Status in bluez package in Ubuntu:
  Invalid

Bug description:
  Ubuntu :- 20.04 
  Hello I have RT3290 bluetooth in built and it was not working so I installed 
its latest driver from github whose version is 3.9.6 . Now its working but its 
not discoverable to any other device and also not finding any other device.
  Outout of command :- service bluetooth status

  ● bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
pre>
   Active: active (running) since Sat 2021-01-30 09:49:10 IST; 1h 0min ago
     Docs: man:bluetoothd(8)
     Main PID: 1389 (bluetoothd)
   Status: "Running"
    Tasks: 1 (limit: 4514)
   Memory: 2.0M
   CGroup: /system.slice/bluetooth.service
   └─1389 /usr/lib/bluetooth/bluetoothd

  Jan 30 09:49:07 Piyush-X55C systemd[1]: Starting Bluetooth service...
  Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Bluetooth daemon 5.53
  Jan 30 09:49:10 Piyush-X55C systemd[1]: Started Bluetooth service.
  Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Starting SDP server
  Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Bluetooth management interface 
1.>
  Jan 30 10:49:34 Piyush-X55C bluetoothd[1389]: Endpoint registered: 
sender=:1.66>
  Jan 30 10:49:34 Piyush-X55C bluetoothd[1389]: Endpoint registered: 
sender=:1.66>
  lines 1-18/18 (END)

  Output of command :- sudo btmgmt info

  Index list with 1 item
  hci0:   Primary controller
  addr A4:17:31:1D:65:54 version 4 manufacturer 91 class 0x00
  supported settings: powered connectable fast-connectable discoverable 
bondable link-security ssp br/edr debug-keys
  current settings: powered bondable ssp br/edr
  name Piyush-X55C

  Output of command :- bluetoothctl

  Agent registered
  [bluetooth]# scan on
  [bluetooth]# discoverable on
  [bluetooth]# scan on
  Failed to start discovery: org.bluez.Error.InProgress
  [bluetooth]# discoverable on
  Changing discoverable on succeeded
  [bluetooth]#

  Output of command :- sudo btmgmt find

  Unable to start discovery. status 0x0c (Not Supported)

  Output of command :- lspci -knn | grep Net -A3; lsusb

  02:00.0 Network controller [0280]: Ralink corp. RT3290 Wireless 802.11n 1T/1R 
PCIe [1814:3290]
  Subsystem: Foxconn International, Inc. RT3290 Wireless 802.11n 1T/1R PCIe 
[105b:e055]
  Kernel driver in use: rt2800pci
  Kernel modules: rt2800pci
  Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 003: ID 1bcf:2883 Sunplus Innovation Technology Inc.
  Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  Output of command :-dmesg | grep -i bluetooth

   [   12.851854] Bluetooth: Core ver 2.22
  [   12.851883] Bluetooth: HCI device and connection manager initialized
  [   12.851888] Bluetooth: HCI socket layer initialized
  [   12.851889] Bluetooth: L2CAP socket layer initialized
  [   12.851893] Bluetooth: SCO socket layer initialized
  [   67.399550] audit: type=1400 audit(1611909043.091:58): 
apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=875 
comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 
requested_mask="create" denied_mask="create"
  [   67.727240] audit: type=1400 audit(1611909043.419:60): 
apparmor="DENIED" operation="connect" profile="snap.bluez.bluez" 
name="/run/dbus/system_bus_socket" pid=875 comm="bluetoothd" 
requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
  [   67.929889] audit: type=1400 audit(1611909043.619:62): 
apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=1043 
comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 
requested_mask="create" denied_mask="create"
  [   67.930261] audit: type=1400 audit(1611909043.623:63): 
apparmor="DENIED" operation="connect" profile="snap.bluez.bluez" 
name="/run/dbus/system_bus_socket" pid=1043 comm="bluetoothd" 
requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
  [   68.194380] audit: type=1400

[Kernel-packages] [Bug 1914007] [NEW] RT3290 Bluetooth not finding any device

2021-01-31 Thread Piyush Santosh Mhatre
Public bug reported:

Ubuntu :- 20.04
Hello I have RT3290 bluetooth in built and it was not working so I installed 
its latest driver from github whose version is 3.9.6 . Now its working but its 
not discoverable to any other device and also not finding any other device.
Outout of command :- service bluetooth status

● bluetooth.service - Bluetooth service
 Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor pre>
 Active: active (running) since Sat 2021-01-30 09:49:10 IST; 1h 0min ago
   Docs: man:bluetoothd(8)
   Main PID: 1389 (bluetoothd)
 Status: "Running"
  Tasks: 1 (limit: 4514)
 Memory: 2.0M
 CGroup: /system.slice/bluetooth.service
 └─1389 /usr/lib/bluetooth/bluetoothd

Jan 30 09:49:07 Piyush-X55C systemd[1]: Starting Bluetooth service...
Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Bluetooth daemon 5.53
Jan 30 09:49:10 Piyush-X55C systemd[1]: Started Bluetooth service.
Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Starting SDP server
Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Bluetooth management interface 1.>
Jan 30 10:49:34 Piyush-X55C bluetoothd[1389]: Endpoint registered: sender=:1.66>
Jan 30 10:49:34 Piyush-X55C bluetoothd[1389]: Endpoint registered: sender=:1.66>
lines 1-18/18 (END)

Output of command :- sudo btmgmt info

Index list with 1 item
hci0: Primary controller
addr A4:17:31:1D:65:54 version 4 manufacturer 91 class 0x00
supported settings: powered connectable fast-connectable discoverable 
bondable link-security ssp br/edr debug-keys
current settings: powered bondable ssp br/edr
name Piyush-X55C

Output of command :- bluetoothctl

Agent registered
[bluetooth]# scan on
[bluetooth]# discoverable on
[bluetooth]# scan on
Failed to start discovery: org.bluez.Error.InProgress
[bluetooth]# discoverable on
Changing discoverable on succeeded
[bluetooth]#

Output of command :- sudo btmgmt find

Unable to start discovery. status 0x0c (Not Supported)

Output of command :- lspci -knn | grep Net -A3; lsusb

02:00.0 Network controller [0280]: Ralink corp. RT3290 Wireless 802.11n 1T/1R 
PCIe [1814:3290]
Subsystem: Foxconn International, Inc. RT3290 Wireless 802.11n 1T/1R PCIe 
[105b:e055]
Kernel driver in use: rt2800pci
Kernel modules: rt2800pci
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 1bcf:2883 Sunplus Innovation Technology Inc.
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Output of command :-dmesg | grep -i bluetooth

 [ 12.851854] Bluetooth: Core ver 2.22
[ 12.851883] Bluetooth: HCI device and connection manager initialized
[ 12.851888] Bluetooth: HCI socket layer initialized
[ 12.851889] Bluetooth: L2CAP socket layer initialized
[ 12.851893] Bluetooth: SCO socket layer initialized
[ 67.399550] audit: type=1400 audit(1611909043.091:58): apparmor="DENIED" 
operation="create" profile="snap.bluez.bluez" pid=875 comm="bluetoothd" 
family="bluetooth" sock_type="raw" protocol=1 requested_mask="create" 
denied_mask="create"
[ 67.727240] audit: type=1400 audit(1611909043.419:60): apparmor="DENIED" 
operation="connect" profile="snap.bluez.bluez" 
name="/run/dbus/system_bus_socket" pid=875 comm="bluetoothd" 
requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
[ 67.929889] audit: type=1400 audit(1611909043.619:62): apparmor="DENIED" 
operation="create" profile="snap.bluez.bluez" pid=1043 comm="bluetoothd" 
family="bluetooth" sock_type="raw" protocol=1 requested_mask="create" 
denied_mask="create"
[ 67.930261] audit: type=1400 audit(1611909043.623:63): apparmor="DENIED" 
operation="connect" profile="snap.bluez.bluez" 
name="/run/dbus/system_bus_socket" pid=1043 comm="bluetoothd" 
requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
[ 68.194380] audit: type=1400 audit(1611909043.887:65): apparmor="DENIED" 
operation="create" profile="snap.bluez.bluez" pid=1102 comm="bluetoothd" 
family="bluetooth" sock_type="raw" protocol=1 requested_mask="create" 
denied_mask="create"
[ 68.194710] audit: type=1400 audit(1611909043.887:66): apparmor="DENIED" 
operation="connect" profile="snap.bluez.bluez" 
name="/run/dbus/system_bus_socket" pid=1102 comm=

[Kernel-packages] [Bug 1913859] Re: RT3290 Bluetooth not finding any device

2021-01-31 Thread Piyush Santosh Mhatre
Thankyou @Daniel I ran command given by you and It replied that the 
linux-generic-hwe-20.04 is already installed. Then I ran the last command that 
you have given and it says that I have two versions of blueman one is stable 
directs to launch pad web site and gives me this :-
[
Lost something?
This page does not exist, or you may not have permission to see it.

If you have been to this page before, it is possible it has been
removed.

Check that you are logged in with the correct account, or that you entered the 
address correctly, or search for it:
]
The other versions bug is submitted succesfully.

-- 
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/1913859

Title:
  RT3290 Bluetooth not finding any device

Status in bluez package in Ubuntu:
  Invalid

Bug description:
  Ubuntu :- 20.04 
  Hello I have RT3290 bluetooth in built and it was not working so I installed 
its latest driver from github whose version is 3.9.6 . Now its working but its 
not discoverable to any other device and also not finding any other device.
  Outout of command :- service bluetooth status

  ● bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
pre>
   Active: active (running) since Sat 2021-01-30 09:49:10 IST; 1h 0min ago
     Docs: man:bluetoothd(8)
     Main PID: 1389 (bluetoothd)
   Status: "Running"
    Tasks: 1 (limit: 4514)
   Memory: 2.0M
   CGroup: /system.slice/bluetooth.service
   └─1389 /usr/lib/bluetooth/bluetoothd

  Jan 30 09:49:07 Piyush-X55C systemd[1]: Starting Bluetooth service...
  Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Bluetooth daemon 5.53
  Jan 30 09:49:10 Piyush-X55C systemd[1]: Started Bluetooth service.
  Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Starting SDP server
  Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Bluetooth management interface 
1.>
  Jan 30 10:49:34 Piyush-X55C bluetoothd[1389]: Endpoint registered: 
sender=:1.66>
  Jan 30 10:49:34 Piyush-X55C bluetoothd[1389]: Endpoint registered: 
sender=:1.66>
  lines 1-18/18 (END)

  Output of command :- sudo btmgmt info

  Index list with 1 item
  hci0:   Primary controller
  addr A4:17:31:1D:65:54 version 4 manufacturer 91 class 0x00
  supported settings: powered connectable fast-connectable discoverable 
bondable link-security ssp br/edr debug-keys
  current settings: powered bondable ssp br/edr
  name Piyush-X55C

  Output of command :- bluetoothctl

  Agent registered
  [bluetooth]# scan on
  [bluetooth]# discoverable on
  [bluetooth]# scan on
  Failed to start discovery: org.bluez.Error.InProgress
  [bluetooth]# discoverable on
  Changing discoverable on succeeded
  [bluetooth]#

  Output of command :- sudo btmgmt find

  Unable to start discovery. status 0x0c (Not Supported)

  Output of command :- lspci -knn | grep Net -A3; lsusb

  02:00.0 Network controller [0280]: Ralink corp. RT3290 Wireless 802.11n 1T/1R 
PCIe [1814:3290]
  Subsystem: Foxconn International, Inc. RT3290 Wireless 802.11n 1T/1R PCIe 
[105b:e055]
  Kernel driver in use: rt2800pci
  Kernel modules: rt2800pci
  Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 003: ID 1bcf:2883 Sunplus Innovation Technology Inc.
  Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  Output of command :-dmesg | grep -i bluetooth

   [   12.851854] Bluetooth: Core ver 2.22
  [   12.851883] Bluetooth: HCI device and connection manager initialized
  [   12.851888] Bluetooth: HCI socket layer initialized
  [   12.851889] Bluetooth: L2CAP socket layer initialized
  [   12.851893] Bluetooth: SCO socket layer initialized
  [   67.399550] audit: type=1400 audit(1611909043.091:58): 
apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=875 
comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 
requested_mask="create" denied_mask="create"
  [   67.727240] audit: type=1400 audit(1611909043.419:60): 
apparmor="DENIED" operation="connect" profile="snap.bluez.bluez" 
name="/run/dbus/system_bus_socket" pid=875 comm="bluetoothd" 
requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
  [   67.929889] audit: type=1400 audit(1611909043.619:62): 
apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=1043 
comm=&quo

[Kernel-packages] [Bug 1913859] Re: RT3290 Bluetooth not finding any device

2021-02-01 Thread Piyush Santosh Mhatre
** This bug is no longer a duplicate of bug 1189721
   Ralink RT3290 doesn't have a bluetooth driver

** Changed in: bluez (Ubuntu)
   Status: Invalid => In Progress

** Changed in: bluez (Ubuntu)
 Assignee: (unassigned) => Piyush Santosh Mhatre (piyush-m)

-- 
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/1913859

Title:
  RT3290 Bluetooth not finding any device

Status in bluez package in Ubuntu:
  In Progress

Bug description:
  Ubuntu :- 20.04 
  Hello I have RT3290 bluetooth in built and it was not working so I installed 
its latest driver from github whose version is 3.9.6 . Now its working but its 
not discoverable to any other device and also not finding any other device.
  Outout of command :- service bluetooth status

  ● bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
pre>
   Active: active (running) since Sat 2021-01-30 09:49:10 IST; 1h 0min ago
     Docs: man:bluetoothd(8)
     Main PID: 1389 (bluetoothd)
   Status: "Running"
    Tasks: 1 (limit: 4514)
   Memory: 2.0M
   CGroup: /system.slice/bluetooth.service
   └─1389 /usr/lib/bluetooth/bluetoothd

  Jan 30 09:49:07 Piyush-X55C systemd[1]: Starting Bluetooth service...
  Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Bluetooth daemon 5.53
  Jan 30 09:49:10 Piyush-X55C systemd[1]: Started Bluetooth service.
  Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Starting SDP server
  Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Bluetooth management interface 
1.>
  Jan 30 10:49:34 Piyush-X55C bluetoothd[1389]: Endpoint registered: 
sender=:1.66>
  Jan 30 10:49:34 Piyush-X55C bluetoothd[1389]: Endpoint registered: 
sender=:1.66>
  lines 1-18/18 (END)

  Output of command :- sudo btmgmt info

  Index list with 1 item
  hci0:   Primary controller
  addr A4:17:31:1D:65:54 version 4 manufacturer 91 class 0x00
  supported settings: powered connectable fast-connectable discoverable 
bondable link-security ssp br/edr debug-keys
  current settings: powered bondable ssp br/edr
  name Piyush-X55C

  Output of command :- bluetoothctl

  Agent registered
  [bluetooth]# scan on
  [bluetooth]# discoverable on
  [bluetooth]# scan on
  Failed to start discovery: org.bluez.Error.InProgress
  [bluetooth]# discoverable on
  Changing discoverable on succeeded
  [bluetooth]#

  Output of command :- sudo btmgmt find

  Unable to start discovery. status 0x0c (Not Supported)

  Output of command :- lspci -knn | grep Net -A3; lsusb

  02:00.0 Network controller [0280]: Ralink corp. RT3290 Wireless 802.11n 1T/1R 
PCIe [1814:3290]
  Subsystem: Foxconn International, Inc. RT3290 Wireless 802.11n 1T/1R PCIe 
[105b:e055]
  Kernel driver in use: rt2800pci
  Kernel modules: rt2800pci
  Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 003: ID 1bcf:2883 Sunplus Innovation Technology Inc.
  Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  Output of command :-dmesg | grep -i bluetooth

   [   12.851854] Bluetooth: Core ver 2.22
  [   12.851883] Bluetooth: HCI device and connection manager initialized
  [   12.851888] Bluetooth: HCI socket layer initialized
  [   12.851889] Bluetooth: L2CAP socket layer initialized
  [   12.851893] Bluetooth: SCO socket layer initialized
  [   67.399550] audit: type=1400 audit(1611909043.091:58): 
apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=875 
comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 
requested_mask="create" denied_mask="create"
  [   67.727240] audit: type=1400 audit(1611909043.419:60): 
apparmor="DENIED" operation="connect" profile="snap.bluez.bluez" 
name="/run/dbus/system_bus_socket" pid=875 comm="bluetoothd" 
requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
  [   67.929889] audit: type=1400 audit(1611909043.619:62): 
apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=1043 
comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 
requested_mask="create" denied_mask="create"
  [   67.930261] audit: type=1400 audit(1611909043.623:63): 
apparmor="DENIED" operation="connect" profile="snap.bluez.bluez" 
name="/

[Kernel-packages] [Bug 1914007] Re: RT3290 Bluetooth not finding any device

2021-02-01 Thread Piyush Santosh Mhatre
** This bug is no longer a duplicate of bug 1189721
   Ralink RT3290 doesn't have a bluetooth driver

-- 
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/1914007

Title:
  RT3290 Bluetooth not finding any device

Status in bluez package in Ubuntu:
  New

Bug description:
  Ubuntu :- 20.04
  Hello I have RT3290 bluetooth in built and it was not working so I installed 
its latest driver from github whose version is 3.9.6 . Now its working but its 
not discoverable to any other device and also not finding any other device.
  Outout of command :- service bluetooth status

  ● bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
pre>
   Active: active (running) since Sat 2021-01-30 09:49:10 IST; 1h 0min ago
 Docs: man:bluetoothd(8)
 Main PID: 1389 (bluetoothd)
   Status: "Running"
Tasks: 1 (limit: 4514)
   Memory: 2.0M
   CGroup: /system.slice/bluetooth.service
   └─1389 /usr/lib/bluetooth/bluetoothd

  Jan 30 09:49:07 Piyush-X55C systemd[1]: Starting Bluetooth service...
  Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Bluetooth daemon 5.53
  Jan 30 09:49:10 Piyush-X55C systemd[1]: Started Bluetooth service.
  Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Starting SDP server
  Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Bluetooth management interface 
1.>
  Jan 30 10:49:34 Piyush-X55C bluetoothd[1389]: Endpoint registered: 
sender=:1.66>
  Jan 30 10:49:34 Piyush-X55C bluetoothd[1389]: Endpoint registered: 
sender=:1.66>
  lines 1-18/18 (END)

  Output of command :- sudo btmgmt info

  Index list with 1 item
  hci0: Primary controller
  addr A4:17:31:1D:65:54 version 4 manufacturer 91 class 0x00
  supported settings: powered connectable fast-connectable discoverable 
bondable link-security ssp br/edr debug-keys
  current settings: powered bondable ssp br/edr
  name Piyush-X55C

  Output of command :- bluetoothctl

  Agent registered
  [bluetooth]# scan on
  [bluetooth]# discoverable on
  [bluetooth]# scan on
  Failed to start discovery: org.bluez.Error.InProgress
  [bluetooth]# discoverable on
  Changing discoverable on succeeded
  [bluetooth]#

  Output of command :- sudo btmgmt find

  Unable to start discovery. status 0x0c (Not Supported)

  Output of command :- lspci -knn | grep Net -A3; lsusb

  02:00.0 Network controller [0280]: Ralink corp. RT3290 Wireless 802.11n 1T/1R 
PCIe [1814:3290]
  Subsystem: Foxconn International, Inc. RT3290 Wireless 802.11n 1T/1R PCIe 
[105b:e055]
  Kernel driver in use: rt2800pci
  Kernel modules: rt2800pci
  Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 003: ID 1bcf:2883 Sunplus Innovation Technology Inc.
  Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  Output of command :-dmesg | grep -i bluetooth

   [ 12.851854] Bluetooth: Core ver 2.22
  [ 12.851883] Bluetooth: HCI device and connection manager initialized
  [ 12.851888] Bluetooth: HCI socket layer initialized
  [ 12.851889] Bluetooth: L2CAP socket layer initialized
  [ 12.851893] Bluetooth: SCO socket layer initialized
  [ 67.399550] audit: type=1400 audit(1611909043.091:58): apparmor="DENIED" 
operation="create" profile="snap.bluez.bluez" pid=875 comm="bluetoothd" 
family="bluetooth" sock_type="raw" protocol=1 requested_mask="create" 
denied_mask="create"
  [ 67.727240] audit: type=1400 audit(1611909043.419:60): apparmor="DENIED" 
operation="connect" profile="snap.bluez.bluez" 
name="/run/dbus/system_bus_socket" pid=875 comm="bluetoothd" 
requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
  [ 67.929889] audit: type=1400 audit(1611909043.619:62): apparmor="DENIED" 
operation="create" profile="snap.bluez.bluez" pid=1043 comm="bluetoothd" 
family="bluetooth" sock_type="raw" protocol=1 requested_mask="create" 
denied_mask="create"
  [ 67.930261] audit: type=1400 audit(1611909043.623:63): apparmor="DENIED" 
operation="connect" profile="snap.bluez.bluez" 
name="/run/dbus/system_bus_socket" pid=1043 comm="bluetoothd" 
requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
  [ 68.194380] audit: type=1400 audit(1611909043.887:65): ap

[Kernel-packages] [Bug 1914007] Re: RT3290 Bluetooth not finding any device

2021-02-01 Thread Piyush Santosh Mhatre
Yeah I know that it might be a driver issue, but there no other option
for me and I have gone through the given bug by you and its quite old
and available for old kernal versions and I am a noob in these bugs and
all and have no knowlwdge about this. I tried there given solution but I
got errors in them and as I said (have no knowledge) don't know how to
fix it.BTW Thanks.

-- 
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/1914007

Title:
  RT3290 Bluetooth not finding any device

Status in bluez package in Ubuntu:
  New

Bug description:
  Ubuntu :- 20.04
  Hello I have RT3290 bluetooth in built and it was not working so I installed 
its latest driver from github whose version is 3.9.6 . Now its working but its 
not discoverable to any other device and also not finding any other device.
  Outout of command :- service bluetooth status

  ● bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
pre>
   Active: active (running) since Sat 2021-01-30 09:49:10 IST; 1h 0min ago
 Docs: man:bluetoothd(8)
 Main PID: 1389 (bluetoothd)
   Status: "Running"
Tasks: 1 (limit: 4514)
   Memory: 2.0M
   CGroup: /system.slice/bluetooth.service
   └─1389 /usr/lib/bluetooth/bluetoothd

  Jan 30 09:49:07 Piyush-X55C systemd[1]: Starting Bluetooth service...
  Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Bluetooth daemon 5.53
  Jan 30 09:49:10 Piyush-X55C systemd[1]: Started Bluetooth service.
  Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Starting SDP server
  Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Bluetooth management interface 
1.>
  Jan 30 10:49:34 Piyush-X55C bluetoothd[1389]: Endpoint registered: 
sender=:1.66>
  Jan 30 10:49:34 Piyush-X55C bluetoothd[1389]: Endpoint registered: 
sender=:1.66>
  lines 1-18/18 (END)

  Output of command :- sudo btmgmt info

  Index list with 1 item
  hci0: Primary controller
  addr A4:17:31:1D:65:54 version 4 manufacturer 91 class 0x00
  supported settings: powered connectable fast-connectable discoverable 
bondable link-security ssp br/edr debug-keys
  current settings: powered bondable ssp br/edr
  name Piyush-X55C

  Output of command :- bluetoothctl

  Agent registered
  [bluetooth]# scan on
  [bluetooth]# discoverable on
  [bluetooth]# scan on
  Failed to start discovery: org.bluez.Error.InProgress
  [bluetooth]# discoverable on
  Changing discoverable on succeeded
  [bluetooth]#

  Output of command :- sudo btmgmt find

  Unable to start discovery. status 0x0c (Not Supported)

  Output of command :- lspci -knn | grep Net -A3; lsusb

  02:00.0 Network controller [0280]: Ralink corp. RT3290 Wireless 802.11n 1T/1R 
PCIe [1814:3290]
  Subsystem: Foxconn International, Inc. RT3290 Wireless 802.11n 1T/1R PCIe 
[105b:e055]
  Kernel driver in use: rt2800pci
  Kernel modules: rt2800pci
  Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 003: ID 1bcf:2883 Sunplus Innovation Technology Inc.
  Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  Output of command :-dmesg | grep -i bluetooth

   [ 12.851854] Bluetooth: Core ver 2.22
  [ 12.851883] Bluetooth: HCI device and connection manager initialized
  [ 12.851888] Bluetooth: HCI socket layer initialized
  [ 12.851889] Bluetooth: L2CAP socket layer initialized
  [ 12.851893] Bluetooth: SCO socket layer initialized
  [ 67.399550] audit: type=1400 audit(1611909043.091:58): apparmor="DENIED" 
operation="create" profile="snap.bluez.bluez" pid=875 comm="bluetoothd" 
family="bluetooth" sock_type="raw" protocol=1 requested_mask="create" 
denied_mask="create"
  [ 67.727240] audit: type=1400 audit(1611909043.419:60): apparmor="DENIED" 
operation="connect" profile="snap.bluez.bluez" 
name="/run/dbus/system_bus_socket" pid=875 comm="bluetoothd" 
requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
  [ 67.929889] audit: type=1400 audit(1611909043.619:62): apparmor="DENIED" 
operation="create" profile="snap.bluez.bluez" pid=1043 comm="bluetoothd" 
family="bluetooth" sock_type="raw" protocol=1 requested_mask="create" 
denied_mask="create"
  [ 67.930261] audit: type=1400 audit(1611909043.623:63): apparmor="DENIED" 
ope

[Kernel-packages] [Bug 1914007] Re: RT3290 Bluetooth not finding any device

2021-02-01 Thread Piyush Santosh Mhatre
Please suggest me a solution for this @Daniel.

** This bug is no longer a duplicate of bug 1189721
   Ralink RT3290 doesn't have a bluetooth driver

-- 
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/1914007

Title:
  RT3290 Bluetooth not finding any device

Status in bluez package in Ubuntu:
  Invalid

Bug description:
  Ubuntu :- 20.04
  Hello I have RT3290 bluetooth in built and it was not working so I installed 
its latest driver from github whose version is 3.9.6 . Now its working but its 
not discoverable to any other device and also not finding any other device.
  Outout of command :- service bluetooth status

  ● bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
pre>
   Active: active (running) since Sat 2021-01-30 09:49:10 IST; 1h 0min ago
 Docs: man:bluetoothd(8)
 Main PID: 1389 (bluetoothd)
   Status: "Running"
Tasks: 1 (limit: 4514)
   Memory: 2.0M
   CGroup: /system.slice/bluetooth.service
   └─1389 /usr/lib/bluetooth/bluetoothd

  Jan 30 09:49:07 Piyush-X55C systemd[1]: Starting Bluetooth service...
  Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Bluetooth daemon 5.53
  Jan 30 09:49:10 Piyush-X55C systemd[1]: Started Bluetooth service.
  Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Starting SDP server
  Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Bluetooth management interface 
1.>
  Jan 30 10:49:34 Piyush-X55C bluetoothd[1389]: Endpoint registered: 
sender=:1.66>
  Jan 30 10:49:34 Piyush-X55C bluetoothd[1389]: Endpoint registered: 
sender=:1.66>
  lines 1-18/18 (END)

  Output of command :- sudo btmgmt info

  Index list with 1 item
  hci0: Primary controller
  addr A4:17:31:1D:65:54 version 4 manufacturer 91 class 0x00
  supported settings: powered connectable fast-connectable discoverable 
bondable link-security ssp br/edr debug-keys
  current settings: powered bondable ssp br/edr
  name Piyush-X55C

  Output of command :- bluetoothctl

  Agent registered
  [bluetooth]# scan on
  [bluetooth]# discoverable on
  [bluetooth]# scan on
  Failed to start discovery: org.bluez.Error.InProgress
  [bluetooth]# discoverable on
  Changing discoverable on succeeded
  [bluetooth]#

  Output of command :- sudo btmgmt find

  Unable to start discovery. status 0x0c (Not Supported)

  Output of command :- lspci -knn | grep Net -A3; lsusb

  02:00.0 Network controller [0280]: Ralink corp. RT3290 Wireless 802.11n 1T/1R 
PCIe [1814:3290]
  Subsystem: Foxconn International, Inc. RT3290 Wireless 802.11n 1T/1R PCIe 
[105b:e055]
  Kernel driver in use: rt2800pci
  Kernel modules: rt2800pci
  Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 003: ID 1bcf:2883 Sunplus Innovation Technology Inc.
  Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  Output of command :-dmesg | grep -i bluetooth

   [ 12.851854] Bluetooth: Core ver 2.22
  [ 12.851883] Bluetooth: HCI device and connection manager initialized
  [ 12.851888] Bluetooth: HCI socket layer initialized
  [ 12.851889] Bluetooth: L2CAP socket layer initialized
  [ 12.851893] Bluetooth: SCO socket layer initialized
  [ 67.399550] audit: type=1400 audit(1611909043.091:58): apparmor="DENIED" 
operation="create" profile="snap.bluez.bluez" pid=875 comm="bluetoothd" 
family="bluetooth" sock_type="raw" protocol=1 requested_mask="create" 
denied_mask="create"
  [ 67.727240] audit: type=1400 audit(1611909043.419:60): apparmor="DENIED" 
operation="connect" profile="snap.bluez.bluez" 
name="/run/dbus/system_bus_socket" pid=875 comm="bluetoothd" 
requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
  [ 67.929889] audit: type=1400 audit(1611909043.619:62): apparmor="DENIED" 
operation="create" profile="snap.bluez.bluez" pid=1043 comm="bluetoothd" 
family="bluetooth" sock_type="raw" protocol=1 requested_mask="create" 
denied_mask="create"
  [ 67.930261] audit: type=1400 audit(1611909043.623:63): apparmor="DENIED" 
operation="connect" profile="snap.bluez.bluez" 
name="/run/dbus/system_bus_socket" pid=1043 comm="bluetoothd" 
requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
  [ 68

[Kernel-packages] [Bug 1914007] Re: RT3290 Bluetooth not finding any device

2021-02-01 Thread Piyush Santosh Mhatre
And yeah in that given bug post there is a solution how to get working
RT3290 but my problem is different my adapter is working but the agent
Bluetoothctl is giving an error related to blueman so isn't it a
different problem? @Daniel

-- 
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/1914007

Title:
  RT3290 Bluetooth not finding any device

Status in bluez package in Ubuntu:
  Invalid

Bug description:
  Ubuntu :- 20.04
  Hello I have RT3290 bluetooth in built and it was not working so I installed 
its latest driver from github whose version is 3.9.6 . Now its working but its 
not discoverable to any other device and also not finding any other device.
  Outout of command :- service bluetooth status

  ● bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
pre>
   Active: active (running) since Sat 2021-01-30 09:49:10 IST; 1h 0min ago
 Docs: man:bluetoothd(8)
 Main PID: 1389 (bluetoothd)
   Status: "Running"
Tasks: 1 (limit: 4514)
   Memory: 2.0M
   CGroup: /system.slice/bluetooth.service
   └─1389 /usr/lib/bluetooth/bluetoothd

  Jan 30 09:49:07 Piyush-X55C systemd[1]: Starting Bluetooth service...
  Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Bluetooth daemon 5.53
  Jan 30 09:49:10 Piyush-X55C systemd[1]: Started Bluetooth service.
  Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Starting SDP server
  Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Bluetooth management interface 
1.>
  Jan 30 10:49:34 Piyush-X55C bluetoothd[1389]: Endpoint registered: 
sender=:1.66>
  Jan 30 10:49:34 Piyush-X55C bluetoothd[1389]: Endpoint registered: 
sender=:1.66>
  lines 1-18/18 (END)

  Output of command :- sudo btmgmt info

  Index list with 1 item
  hci0: Primary controller
  addr A4:17:31:1D:65:54 version 4 manufacturer 91 class 0x00
  supported settings: powered connectable fast-connectable discoverable 
bondable link-security ssp br/edr debug-keys
  current settings: powered bondable ssp br/edr
  name Piyush-X55C

  Output of command :- bluetoothctl

  Agent registered
  [bluetooth]# scan on
  [bluetooth]# discoverable on
  [bluetooth]# scan on
  Failed to start discovery: org.bluez.Error.InProgress
  [bluetooth]# discoverable on
  Changing discoverable on succeeded
  [bluetooth]#

  Output of command :- sudo btmgmt find

  Unable to start discovery. status 0x0c (Not Supported)

  Output of command :- lspci -knn | grep Net -A3; lsusb

  02:00.0 Network controller [0280]: Ralink corp. RT3290 Wireless 802.11n 1T/1R 
PCIe [1814:3290]
  Subsystem: Foxconn International, Inc. RT3290 Wireless 802.11n 1T/1R PCIe 
[105b:e055]
  Kernel driver in use: rt2800pci
  Kernel modules: rt2800pci
  Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 003: ID 1bcf:2883 Sunplus Innovation Technology Inc.
  Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  Output of command :-dmesg | grep -i bluetooth

   [ 12.851854] Bluetooth: Core ver 2.22
  [ 12.851883] Bluetooth: HCI device and connection manager initialized
  [ 12.851888] Bluetooth: HCI socket layer initialized
  [ 12.851889] Bluetooth: L2CAP socket layer initialized
  [ 12.851893] Bluetooth: SCO socket layer initialized
  [ 67.399550] audit: type=1400 audit(1611909043.091:58): apparmor="DENIED" 
operation="create" profile="snap.bluez.bluez" pid=875 comm="bluetoothd" 
family="bluetooth" sock_type="raw" protocol=1 requested_mask="create" 
denied_mask="create"
  [ 67.727240] audit: type=1400 audit(1611909043.419:60): apparmor="DENIED" 
operation="connect" profile="snap.bluez.bluez" 
name="/run/dbus/system_bus_socket" pid=875 comm="bluetoothd" 
requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
  [ 67.929889] audit: type=1400 audit(1611909043.619:62): apparmor="DENIED" 
operation="create" profile="snap.bluez.bluez" pid=1043 comm="bluetoothd" 
family="bluetooth" sock_type="raw" protocol=1 requested_mask="create" 
denied_mask="create"
  [ 67.930261] audit: type=1400 audit(1611909043.623:63): apparmor="DENIED" 
operation="connect" profile="snap.bluez.bluez" 
name="/run/dbus/system_bus_socket" pid=1043 comm="bluetoot

[Kernel-packages] [Bug 1914007] Re: RT3290 Bluetooth not finding any device

2021-02-01 Thread Piyush Santosh Mhatre
** Changed in: bluez (Ubuntu)
   Status: Invalid => 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/1914007

Title:
  RT3290 Bluetooth not finding any device

Status in bluez package in Ubuntu:
  New

Bug description:
  Ubuntu :- 20.04
  Hello I have RT3290 bluetooth in built and it was not working so I installed 
its latest driver from github whose version is 3.9.6 . Now its working but its 
not discoverable to any other device and also not finding any other device.
  Outout of command :- service bluetooth status

  ● bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
pre>
   Active: active (running) since Sat 2021-01-30 09:49:10 IST; 1h 0min ago
 Docs: man:bluetoothd(8)
 Main PID: 1389 (bluetoothd)
   Status: "Running"
Tasks: 1 (limit: 4514)
   Memory: 2.0M
   CGroup: /system.slice/bluetooth.service
   └─1389 /usr/lib/bluetooth/bluetoothd

  Jan 30 09:49:07 Piyush-X55C systemd[1]: Starting Bluetooth service...
  Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Bluetooth daemon 5.53
  Jan 30 09:49:10 Piyush-X55C systemd[1]: Started Bluetooth service.
  Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Starting SDP server
  Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Bluetooth management interface 
1.>
  Jan 30 10:49:34 Piyush-X55C bluetoothd[1389]: Endpoint registered: 
sender=:1.66>
  Jan 30 10:49:34 Piyush-X55C bluetoothd[1389]: Endpoint registered: 
sender=:1.66>
  lines 1-18/18 (END)

  Output of command :- sudo btmgmt info

  Index list with 1 item
  hci0: Primary controller
  addr A4:17:31:1D:65:54 version 4 manufacturer 91 class 0x00
  supported settings: powered connectable fast-connectable discoverable 
bondable link-security ssp br/edr debug-keys
  current settings: powered bondable ssp br/edr
  name Piyush-X55C

  Output of command :- bluetoothctl

  Agent registered
  [bluetooth]# scan on
  [bluetooth]# discoverable on
  [bluetooth]# scan on
  Failed to start discovery: org.bluez.Error.InProgress
  [bluetooth]# discoverable on
  Changing discoverable on succeeded
  [bluetooth]#

  Output of command :- sudo btmgmt find

  Unable to start discovery. status 0x0c (Not Supported)

  Output of command :- lspci -knn | grep Net -A3; lsusb

  02:00.0 Network controller [0280]: Ralink corp. RT3290 Wireless 802.11n 1T/1R 
PCIe [1814:3290]
  Subsystem: Foxconn International, Inc. RT3290 Wireless 802.11n 1T/1R PCIe 
[105b:e055]
  Kernel driver in use: rt2800pci
  Kernel modules: rt2800pci
  Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 003: ID 1bcf:2883 Sunplus Innovation Technology Inc.
  Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  Output of command :-dmesg | grep -i bluetooth

   [ 12.851854] Bluetooth: Core ver 2.22
  [ 12.851883] Bluetooth: HCI device and connection manager initialized
  [ 12.851888] Bluetooth: HCI socket layer initialized
  [ 12.851889] Bluetooth: L2CAP socket layer initialized
  [ 12.851893] Bluetooth: SCO socket layer initialized
  [ 67.399550] audit: type=1400 audit(1611909043.091:58): apparmor="DENIED" 
operation="create" profile="snap.bluez.bluez" pid=875 comm="bluetoothd" 
family="bluetooth" sock_type="raw" protocol=1 requested_mask="create" 
denied_mask="create"
  [ 67.727240] audit: type=1400 audit(1611909043.419:60): apparmor="DENIED" 
operation="connect" profile="snap.bluez.bluez" 
name="/run/dbus/system_bus_socket" pid=875 comm="bluetoothd" 
requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
  [ 67.929889] audit: type=1400 audit(1611909043.619:62): apparmor="DENIED" 
operation="create" profile="snap.bluez.bluez" pid=1043 comm="bluetoothd" 
family="bluetooth" sock_type="raw" protocol=1 requested_mask="create" 
denied_mask="create"
  [ 67.930261] audit: type=1400 audit(1611909043.623:63): apparmor="DENIED" 
operation="connect" profile="snap.bluez.bluez" 
name="/run/dbus/system_bus_socket" pid=1043 comm="bluetoothd" 
requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
  [ 68.194380] audit: type=1400 audit(1611909043.887:65): apparmor="DENIED" 
operatio

[Kernel-packages] [Bug 1913859] Re: RT3290 Bluetooth not finding any device

2021-02-01 Thread Piyush Santosh Mhatre
** This bug is no longer a duplicate of bug 1914007
   RT3290 Bluetooth not finding any device

-- 
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/1913859

Title:
  RT3290 Bluetooth not finding any device

Status in bluez package in Ubuntu:
  Invalid

Bug description:
  Ubuntu :- 20.04 
  Hello I have RT3290 bluetooth in built and it was not working so I installed 
its latest driver from github whose version is 3.9.6 . Now its working but its 
not discoverable to any other device and also not finding any other device.
  Outout of command :- service bluetooth status

  ● bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
pre>
   Active: active (running) since Sat 2021-01-30 09:49:10 IST; 1h 0min ago
     Docs: man:bluetoothd(8)
     Main PID: 1389 (bluetoothd)
   Status: "Running"
    Tasks: 1 (limit: 4514)
   Memory: 2.0M
   CGroup: /system.slice/bluetooth.service
   └─1389 /usr/lib/bluetooth/bluetoothd

  Jan 30 09:49:07 Piyush-X55C systemd[1]: Starting Bluetooth service...
  Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Bluetooth daemon 5.53
  Jan 30 09:49:10 Piyush-X55C systemd[1]: Started Bluetooth service.
  Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Starting SDP server
  Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Bluetooth management interface 
1.>
  Jan 30 10:49:34 Piyush-X55C bluetoothd[1389]: Endpoint registered: 
sender=:1.66>
  Jan 30 10:49:34 Piyush-X55C bluetoothd[1389]: Endpoint registered: 
sender=:1.66>
  lines 1-18/18 (END)

  Output of command :- sudo btmgmt info

  Index list with 1 item
  hci0:   Primary controller
  addr A4:17:31:1D:65:54 version 4 manufacturer 91 class 0x00
  supported settings: powered connectable fast-connectable discoverable 
bondable link-security ssp br/edr debug-keys
  current settings: powered bondable ssp br/edr
  name Piyush-X55C

  Output of command :- bluetoothctl

  Agent registered
  [bluetooth]# scan on
  [bluetooth]# discoverable on
  [bluetooth]# scan on
  Failed to start discovery: org.bluez.Error.InProgress
  [bluetooth]# discoverable on
  Changing discoverable on succeeded
  [bluetooth]#

  Output of command :- sudo btmgmt find

  Unable to start discovery. status 0x0c (Not Supported)

  Output of command :- lspci -knn | grep Net -A3; lsusb

  02:00.0 Network controller [0280]: Ralink corp. RT3290 Wireless 802.11n 1T/1R 
PCIe [1814:3290]
  Subsystem: Foxconn International, Inc. RT3290 Wireless 802.11n 1T/1R PCIe 
[105b:e055]
  Kernel driver in use: rt2800pci
  Kernel modules: rt2800pci
  Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 003: ID 1bcf:2883 Sunplus Innovation Technology Inc.
  Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  Output of command :-dmesg | grep -i bluetooth

   [   12.851854] Bluetooth: Core ver 2.22
  [   12.851883] Bluetooth: HCI device and connection manager initialized
  [   12.851888] Bluetooth: HCI socket layer initialized
  [   12.851889] Bluetooth: L2CAP socket layer initialized
  [   12.851893] Bluetooth: SCO socket layer initialized
  [   67.399550] audit: type=1400 audit(1611909043.091:58): 
apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=875 
comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 
requested_mask="create" denied_mask="create"
  [   67.727240] audit: type=1400 audit(1611909043.419:60): 
apparmor="DENIED" operation="connect" profile="snap.bluez.bluez" 
name="/run/dbus/system_bus_socket" pid=875 comm="bluetoothd" 
requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
  [   67.929889] audit: type=1400 audit(1611909043.619:62): 
apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=1043 
comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 
requested_mask="create" denied_mask="create"
  [   67.930261] audit: type=1400 audit(1611909043.623:63): 
apparmor="DENIED" operation="connect" profile="snap.bluez.bluez" 
name="/run/dbus/system_bus_socket" pid=1043 comm="bluetoothd" 
requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
  [   68.194380] audit: type=1400