[Touch-packages] [Bug 1943154] [NEW] My resolution has changed to 800x600 , it was in higher than 1000 I dont know the exact no
Public bug reported: My resolution has suddenly changed from a higher resolution from to low resolution to 800x600 and it is now showing only one resolution option ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Sep 9 20:32:10 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:2042] ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic root=UUID=78d7ef17-370f-42ec-839a-ad90938c65fb ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/24/2012 dmi.bios.vendor: Intel Corp. dmi.bios.version: HOH6110H.86A.0010.2012.0424.1632 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH61HO dmi.board.vendor: Intel Corporation dmi.board.version: AAG62445-102 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrHOH6110H.86A.0010.2012.0424.1632:bd04/24/2012:svn:pn:pvr:sku:rvnIntelCorporation:rnDH61HO:rvrAAG62445-102:cvn:ct3:cvr: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1943154 Title: My resolution has changed to 800x600 , it was in higher than 1000 I dont know the exact no Status in xorg package in Ubuntu: New Bug description: My resolution has suddenly changed from a higher resolution from to low resolution to 800x600 and it is now showing only one resolution option ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Sep 9 20:32:10 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:2042] ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic root=UUID=78d7ef17-370f-42ec-839a-ad90938c65fb ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/24/2012 dmi.bios.vendor: Intel Corp. dmi.bios.version: HOH6110H.86A.0010.2012.0424.1632 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH61HO dmi.board.vendor: Intel Corporation dmi.board.version: AAG62445-102 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrHOH6110H.86A.0010.2012.0424.1632:bd04/24/2012:svn:pn:pvr:sku:rvnIntelCorporation:rnDH61HO:rvrAAG62445-102:cvn:ct3:cvr: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau:
Re: [Touch-packages] [Bug 1915870] Re: gnome-shell/gnome-session-check-accelerated-gl-helper crashed with SIGSEGV in cso_destroy_context() [r300_dri.so]
I tried this but didn't work for me. But it could be because I didn't use the right patch.diff file. My patch.diff starts at: "--- a/src/gallium/drivers/i915/i915_screen.c" and ends at "switch (param)" from the patch link provided. After that, I just tried building " libgl1-mesa-dri" with: sudo apt-build install libgl1-mesa-dri This took a long time to complete, but doesn't fix the issue. I guess I will wait for the patch to be pushed into Ubuntu updates eventually. Any idea when that would be? Note: I can do "startx" from command line. However, the graphics login doesn't appear at startup because of segfault in gnome-session-check-accelerated-gl-helper. Thanks,Santosh -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1915870 Title: gnome-shell/gnome-session-check-accelerated-gl-helper crashed with SIGSEGV in cso_destroy_context() [r300_dri.so] Status in Mesa: Unknown Status in mesa package in Ubuntu: Triaged Status in mesa package in Fedora: Confirmed Bug description: Graphical user interface is not coming up upon start. Only SSH is possible. lsb_release -rd: Description: Ubuntu 20.10 Release: 20.10 dmesg: [ 11.985343] gnome-session-c[1013]: segfault at 0 ip sp 7fff7679ca48 error 14 in gnome-session-check-accelerated-gl-helper[56020e238000+2000] [ 11.985352] Code: Unable to access opcode bytes at RIP 0xffd6. [ 14.216117] gnome-shell[1094]: segfault at 0 ip sp 7ffeddff9f88 error 14 [ 14.216122] Code: Unable to access opcode bytes at RIP 0xffd6. [ 15.316292] gnome-shell[1109]: segfault at 0 ip sp 7ffc70716198 error 14 [ 15.316297] Code: Unable to access opcode bytes at RIP 0xffd6. apt-cache policy: gnome-session: Installed: (none) Candidate: 3.38.0-1ubuntu1 Version table: 3.38.0-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu groovy/main i386 Packages gnome-session-bin: Installed: 3.38.0-1ubuntu1 Candidate: 3.38.0-1ubuntu1 Version table: *** 3.38.0-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status gnome-session-common: Installed: 3.38.0-1ubuntu1 Candidate: 3.38.0-1ubuntu1 Version table: *** 3.38.0-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu groovy/main i386 Packages 100 /var/lib/dpkg/status /var/crash: see attachment To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1915870/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1915870] Re: gnome-session-check-accelerated-gl-helper crashed with SIGSEGV in cso_destroy_context() [r300_dri.so]
Sure. Thanks a lot. Looks like this has worked for Mark. So I will give this a try as well... Regards,Santosh -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1915870 Title: gnome-session-check-accelerated-gl-helper crashed with SIGSEGV in cso_destroy_context() [r300_dri.so] Status in Mesa: Unknown Status in mesa package in Ubuntu: Triaged Status in mesa package in Fedora: Unknown Bug description: Graphical user interface is not coming up upon start. Only SSH is possible. lsb_release -rd: Description: Ubuntu 20.10 Release: 20.10 dmesg: [ 11.985343] gnome-session-c[1013]: segfault at 0 ip sp 7fff7679ca48 error 14 in gnome-session-check-accelerated-gl-helper[56020e238000+2000] [ 11.985352] Code: Unable to access opcode bytes at RIP 0xffd6. [ 14.216117] gnome-shell[1094]: segfault at 0 ip sp 7ffeddff9f88 error 14 [ 14.216122] Code: Unable to access opcode bytes at RIP 0xffd6. [ 15.316292] gnome-shell[1109]: segfault at 0 ip sp 7ffc70716198 error 14 [ 15.316297] Code: Unable to access opcode bytes at RIP 0xffd6. apt-cache policy: gnome-session: Installed: (none) Candidate: 3.38.0-1ubuntu1 Version table: 3.38.0-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu groovy/main i386 Packages gnome-session-bin: Installed: 3.38.0-1ubuntu1 Candidate: 3.38.0-1ubuntu1 Version table: *** 3.38.0-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status gnome-session-common: Installed: 3.38.0-1ubuntu1 Candidate: 3.38.0-1ubuntu1 Version table: *** 3.38.0-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu groovy/main i386 Packages 100 /var/lib/dpkg/status /var/crash: see attachment To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1915870/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1915870] Re: gnome session not starting (segfault with r300_dri.so)
Hi Mark,Where do I find the "patch.diff"? Thanks,Santosh- Sent from a web-browser based mail client! On Wednesday, February 24, 2021, 02:30:55 AM GMT+5:30, Mark Muth <1915...@bugs.launchpad.net> wrote: Now I can confirm, applying the patch mentioned above brings my PC back to normal. Short summary for everyone else who might read this bug report: Download and save patch as patch.diff and run: sudo apt-build install --patch patch.diff libgl1-mesa-dri -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1915870 Title: gnome session not starting (segfault with r300_dri.so) Status in Mesa: Unknown Status in mesa package in Ubuntu: Confirmed Status in mesa package in Fedora: Unknown Bug description: Graphical user interface is not coming up upon start. Only SSH is possible. lsb_release -rd: Description: Ubuntu 20.10 Release: 20.10 dmesg: [ 11.985343] gnome-session-c[1013]: segfault at 0 ip sp 7fff7679ca48 error 14 in gnome-session-check-accelerated-gl-helper[56020e238000+2000] [ 11.985352] Code: Unable to access opcode bytes at RIP 0xffd6. [ 14.216117] gnome-shell[1094]: segfault at 0 ip sp 7ffeddff9f88 error 14 [ 14.216122] Code: Unable to access opcode bytes at RIP 0xffd6. [ 15.316292] gnome-shell[1109]: segfault at 0 ip sp 7ffc70716198 error 14 [ 15.316297] Code: Unable to access opcode bytes at RIP 0xffd6. apt-cache policy: gnome-session: Installed: (none) Candidate: 3.38.0-1ubuntu1 Version table: 3.38.0-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu groovy/main i386 Packages gnome-session-bin: Installed: 3.38.0-1ubuntu1 Candidate: 3.38.0-1ubuntu1 Version table: *** 3.38.0-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status gnome-session-common: Installed: 3.38.0-1ubuntu1 Candidate: 3.38.0-1ubuntu1 Version table: *** 3.38.0-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu groovy/main i386 Packages 100 /var/lib/dpkg/status /var/crash: see attachment To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1915870/+subscriptions -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1915870 Title: gnome-session-check-accelerated-gl-helper crashed with SIGSEGV in cso_destroy_context() [r300_dri.so] Status in Mesa: Unknown Status in mesa package in Ubuntu: Triaged Status in mesa package in Fedora: Unknown Bug description: Graphical user interface is not coming up upon start. Only SSH is possible. lsb_release -rd: Description: Ubuntu 20.10 Release: 20.10 dmesg: [ 11.985343] gnome-session-c[1013]: segfault at 0 ip sp 7fff7679ca48 error 14 in gnome-session-check-accelerated-gl-helper[56020e238000+2000] [ 11.985352] Code: Unable to access opcode bytes at RIP 0xffd6. [ 14.216117] gnome-shell[1094]: segfault at 0 ip sp 7ffeddff9f88 error 14 [ 14.216122] Code: Unable to access opcode bytes at RIP 0xffd6. [ 15.316292] gnome-shell[1109]: segfault at 0 ip sp 7ffc70716198 error 14 [ 15.316297] Code: Unable to access opcode bytes at RIP 0xffd6. apt-cache policy: gnome-session: Installed: (none) Candidate: 3.38.0-1ubuntu1 Version table: 3.38.0-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu groovy/main i386 Packages gnome-session-bin: Installed: 3.38.0-1ubuntu1 Candidate: 3.38.0-1ubuntu1 Version table: *** 3.38.0-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status gnome-session-common: Installed: 3.38.0-1ubuntu1 Candidate: 3.38.0-1ubuntu1 Version table: *** 3.38.0-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu groovy/main i386 Packages 100 /var/lib/dpkg/status /var/crash: see attachment To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1915870/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://he
[Touch-packages] [Bug 1913859] Re: RT3290 Bluetooth not finding any device
** 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 Ubuntu Touch seeded 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 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"
[Touch-packages] [Bug 1914007] Re: RT3290 Bluetooth not finding any device
** Changed in: bluez (Ubuntu) Status: Invalid => New -- You received this bug notification because you are a member of Ubuntu Touch seeded 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" 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
[Touch-packages] [Bug 1914007] Re: RT3290 Bluetooth not finding any device
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 Ubuntu Touch seeded 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.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"
[Touch-packages] [Bug 1914007] Re: RT3290 Bluetooth not finding any device
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 Ubuntu Touch seeded 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.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"
[Touch-packages] [Bug 1914007] Re: RT3290 Bluetooth not finding any device
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 Ubuntu Touch seeded 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" operation="create"
[Touch-packages] [Bug 1913859] Re: RT3290 Bluetooth not finding any device
** 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 Ubuntu Touch seeded 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="/
[Touch-packages] [Bug 1914007] Re: RT3290 Bluetooth not finding any device
** 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 Ubuntu Touch seeded 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" 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"
[Touch-packages] [Bug 1913859] Re: RT3290 Bluetooth not finding any device
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 Ubuntu Touch seeded 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"
[Touch-packages] [Bug 1914007] [NEW] RT3290 Bluetooth not finding any device
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="bluetoothd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0 [ 81.668783] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 81.668785] Bluetooth: BNEP filters: protocol multicast [ 81.668791] Bluetooth: BNEP socket layer initialized [ 1965.556683] Bluetooth: RTBT_Tb: vendor=0x1814, device=0x3298 [ 1965.556685] Bluetooth: RTBT_Tb: vendor=0x0, device=0x0 [ 1965.556687] Bluetooth: DynamicAlloc pci_device_id table at
[Touch-packages] [Bug 1913859] Re: RT3290 Bluetooth not finding any device
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 Ubuntu Touch seeded 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 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"
[Touch-packages] [Bug 1913859] Re: RT3290 Bluetooth not finding any device
Have you seen the output of bluetoothctl I have given? -- You received this bug notification because you are a member of Ubuntu Touch seeded 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): 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"
[Touch-packages] [Bug 1913859] Re: RT3290 Bluetooth not finding any device
** Tags removed: bot-comment ** Tags added: kernel-bug package-conflict -- You received this bug notification because you are a member of Ubuntu Touch seeded 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): 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"
[Touch-packages] [Bug 1913859] Re: RT3290 Bluetooth not finding any device
** Also affects: bluez (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded 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): 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"
[Touch-packages] [Bug 1731487] [NEW] I donot know what is this type of bug
Public bug reported: I don't know what is type of bug because I am new in ubuntu ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-38-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 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 Date: Fri Nov 10 19:59:28 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Biostar Microtech Int'l Corp 2nd Generation Core Processor Family Integrated Graphics Controller [1565:110f] InstallationDate: Installed on 2017-11-08 (2 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: BIOSTAR Group H61MLV2 ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-38-generic root=UUID=2d3d5b4b-63f6-4738-a551-65464531a017 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/19/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: None dmi.board.name: H61MLV2 dmi.board.vendor: BIOSTAR Group dmi.board.version: 6.0 dmi.chassis.asset.tag: None dmi.chassis.type: 3 dmi.chassis.vendor: BIOSTAR Group dmi.chassis.version: 6.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/19/2012:svnBIOSTARGroup:pnH61MLV2:pvr6.0:rvnBIOSTARGroup:rnH61MLV2:rvr6.0:cvnBIOSTARGroup:ct3:cvr6.0: dmi.product.name: H61MLV2 dmi.product.version: 6.0 dmi.sys.vendor: BIOSTAR Group version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Sat Nov 11 01:10:30 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.3-1ubuntu1~16.04.4 xserver.video_driver: modeset ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1731487 Title: I donot know what is this type of bug Status in xorg package in Ubuntu: New Bug description: I don't know what is type of bug because I am new in ubuntu ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-38-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 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 Date: Fri Nov 10 19:59:28 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Biostar Microtech Int'l Corp 2nd Generation Core Processor Family Integrated Graphics Controller [1565:110f] InstallationDate: Installed on 2017-11-08 (2 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: BIOSTAR Group H61MLV2 ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-38-generic root=UUID=2d3d5b4b-63f6-4738-a551-65464531a017 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/19/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: None dmi.board.name: H61MLV2 dmi.board.vendor: BIOSTAR Group dmi.board.version: 6.0 dmi.chassis.asset.tag: None dmi.chassis.type: 3 dmi.chassis.vendor: BIOSTAR Group dmi.chassis.version: 6.0
[Touch-packages] [Bug 1679659] [NEW] Move the code to show download page to different place
Public bug reported: Right now legacy webview shows download page when webbrowser-app is selected as source in contentpicker. The code to show download page lies inside filepicker implementation. With UbuntuWebView behaviour should be same, To support that, code to show download page Should exists at different place in webbrowser-app code. ** Affects: webbrowser-app (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1679659 Title: Move the code to show download page to different place Status in webbrowser-app package in Ubuntu: New Bug description: Right now legacy webview shows download page when webbrowser-app is selected as source in contentpicker. The code to show download page lies inside filepicker implementation. With UbuntuWebView behaviour should be same, To support that, code to show download page Should exists at different place in webbrowser-app code. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1679659/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1675501] [NEW] webbrowser-app editing menu have no text in "paste" button
Public bug reported: Paste text is missing in editing menu. see the attached picture I found this while testing webbrowser-app with https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/2611/+packages ** Affects: webbrowser-app (Ubuntu) Importance: Undecided Status: New ** Attachment added: "screenshot" https://bugs.launchpad.net/bugs/1675501/+attachment/4843528/+files/Screenshot%20from%202017-03-23%2022-38-32.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1675501 Title: webbrowser-app editing menu have no text in "paste" button Status in webbrowser-app package in Ubuntu: New Bug description: Paste text is missing in editing menu. see the attached picture I found this while testing webbrowser-app with https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/2611/+packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1675501/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1590561] Re: webbrowser-app crashes on startup on fresh zesty Unity8: No suitable EGL configs found
@Olivier, yes I rechecked and found /dev/dri already added there, which I missed somehow. So I confirm two apparmor access to be added. /dev/dri/ r, /sys/devices/pci[0-9]*/**/config r, -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1590561 Title: webbrowser-app crashes on startup on fresh zesty Unity8: No suitable EGL configs found Status in Canonical System Image: Confirmed Status in Oxide: Invalid Status in apparmor package in Ubuntu: In Progress Status in unity8 package in Ubuntu: Confirmed Status in webbrowser-app package in Ubuntu: In Progress Bug description: When trying to start webbrowser-app a unresponsive window appears and after a few moments it crashes. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: webbrowser-app 0.23+16.04.20160413-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Wed Jun 8 22:56:35 2016 InstallationDate: Installed on 2016-04-28 (41 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: webbrowser-app UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1590561/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1590561] Re: webbrowser-app crashes on startup on fresh zesty Unity8: No suitable EGL configs found
@Daniel /dev/dri/* is not the cause of any issue here, and I guess access is already provided. AFAIR adding /dev/dri/* doesn't fix the issue on unity8. The question is whether "/sys/devices/pci[0-9]*/**/config r," is being provided by unity8 to all apps or not, if not then adding that in each app will be only option -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1590561 Title: webbrowser-app crashes on startup on fresh zesty Unity8: No suitable EGL configs found Status in Canonical System Image: Confirmed Status in Oxide: Invalid Status in apparmor package in Ubuntu: New Status in unity8 package in Ubuntu: Confirmed Status in webbrowser-app package in Ubuntu: Confirmed Bug description: When trying to start webbrowser-app a unresponsive window appears and after a few moments it crashes. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: webbrowser-app 0.23+16.04.20160413-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Wed Jun 8 22:56:35 2016 InstallationDate: Installed on 2016-04-28 (41 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: webbrowser-app UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1590561/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1590561] Re: webbrowser-app crashes on startup on fresh zesty Unity8: No suitable EGL configs found
The issue is happening with egl context creation and I could see the bug(error logs) with QOpenGLContext ctx; ctx.create(). So I am also unsure if [1] practically works. Is there any way to validates that. [1] In theory Unity8 should be automatically assigning these rights to all GUI apps automatically. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1590561 Title: webbrowser-app crashes on startup on fresh zesty Unity8: No suitable EGL configs found Status in Canonical System Image: Confirmed Status in Oxide: Confirmed Status in webbrowser-app package in Ubuntu: Confirmed Bug description: When trying to start webbrowser-app a unresponsive window appears and after a few moments it crashes. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: webbrowser-app 0.23+16.04.20160413-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Wed Jun 8 22:56:35 2016 InstallationDate: Installed on 2016-04-28 (41 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: webbrowser-app UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1590561/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1590561] Re: webbrowser-app crashes on startup on fresh zesty Unity8: No suitable EGL configs found
summarising the apparmor fixes for issue.
Issue 1: WebBrowser-app crash on zesty/unity8/[intel, readon]
Fix: Adding apparmor access to
"/sys/devices/pci[0-9]*/**/config r,"
Issue 2: WebBrowser-app crash on xenail/unity7/nvidia
Fix: Adding apparmor access to
For the ibus denial you need:
#include
For nvidia, you need:
#include
@{PROC}/driver/nvidia/params r,
/dev/nvidia* rw,
unix (send, receive) type=dgram peer=(addr="@nvidia[0-9a-f]*"),
I plan to raise bug to add these in webbrowser-app profile,
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1590561
Title:
webbrowser-app crashes on startup on fresh zesty Unity8: No suitable
EGL configs found
Status in Canonical System Image:
Confirmed
Status in Oxide:
Confirmed
Status in webbrowser-app package in Ubuntu:
Confirmed
Bug description:
When trying to start webbrowser-app a unresponsive window appears and
after a few moments it crashes.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: webbrowser-app 0.23+16.04.20160413-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Jun 8 22:56:35 2016
InstallationDate: Installed on 2016-04-28 (41 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
SourcePackage: webbrowser-app
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1590561/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1590561] Re: webbrowser-app crashes on startup on fresh zesty Unity8: No suitable EGL configs found
@ ilija Thanks for syslog, I checked log, there is apparmor denail for /dev/nvidiactl Feb 20 16:28:07 Silver kernel: [ 117.797833] audit: type=1400 audit(1487604487.352:57): apparmor="DENIED" operation="open" profile="webbrowser-app" name="/dev/nvidiactl" pid=3124 comm="webbrowser-app" requested_mask="wr" denied_mask="wr" fsuid=1000 ouid=0 since I could not reproduce issue in my pc, I tried in reverse way, denying apparmor acess to /dev/nvidiactl and I could see exact same crash. So To validate that I need your help. Add path in profile: $ sudo vim /etc/apparmor.d/user.bin.webbrowser-app add /dev/nvidiactl --> [/dev/nvidiactl rw,] Reload the profile $sudo apparmor_parser -r /etc/apparmor.d/usr.bin.webbrowser-app $webbrowser-app // should works. I am still wondering why crash is not happening in any other machine(including mine) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1590561 Title: webbrowser-app crashes on startup on fresh zesty Unity8: No suitable EGL configs found Status in Canonical System Image: Confirmed Status in Oxide: Confirmed Status in webbrowser-app package in Ubuntu: Confirmed Bug description: When trying to start webbrowser-app a unresponsive window appears and after a few moments it crashes. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: webbrowser-app 0.23+16.04.20160413-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Wed Jun 8 22:56:35 2016 InstallationDate: Installed on 2016-04-28 (41 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: webbrowser-app UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1590561/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1590561] Re: webbrowser-app crashes on startup on fresh zesty Unity8: No suitable EGL configs found
@ Ilija Then this also seems to issue with apparmor access, So could you give me full /var/log/syslog. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1590561 Title: webbrowser-app crashes on startup on fresh zesty Unity8: No suitable EGL configs found Status in Canonical System Image: Confirmed Status in Oxide: Confirmed Status in webbrowser-app package in Ubuntu: Confirmed Bug description: When trying to start webbrowser-app a unresponsive window appears and after a few moments it crashes. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: webbrowser-app 0.23+16.04.20160413-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Wed Jun 8 22:56:35 2016 InstallationDate: Installed on 2016-04-28 (41 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: webbrowser-app UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1590561/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1590561] Re: webbrowser-app crashes on startup on fresh zesty Unity8: No suitable EGL configs found
@Ilija Could your try running after disabling apparmor profile for webbrpwser-app sudo apparmor_parser -R /etc/apparmor.d/usr.bin.webbrowser-app and let me know the result -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1590561 Title: webbrowser-app crashes on startup on fresh zesty Unity8: No suitable EGL configs found Status in Canonical System Image: Confirmed Status in Oxide: Confirmed Status in webbrowser-app package in Ubuntu: Invalid Bug description: When trying to start webbrowser-app a unresponsive window appears and after a few moments it crashes. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: webbrowser-app 0.23+16.04.20160413-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Wed Jun 8 22:56:35 2016 InstallationDate: Installed on 2016-04-28 (41 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: webbrowser-app UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1590561/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1590561] Re: webbrowser-app crashes on startup on fresh zesty Unity8: No suitable EGL configs found
@ Ilija I tried on unity7/16.04/nvidia with nouveau driver and didn't see any crash as such. But webbrowser-app crash on 17.04/unity7 which is related to https://bugs.launchpad.net/bugs/1649262, Here nvidia drivers is not getting loaded by mesa. Well, unity8/17.04 is apparmor issue but this(16.04/unity7) seems to be related to drivers, May I know which nvidia driver you are using? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1590561 Title: webbrowser-app crashes on startup on fresh zesty Unity8: No suitable EGL configs found Status in Canonical System Image: Confirmed Status in Oxide: Confirmed Status in webbrowser-app package in Ubuntu: Invalid Bug description: When trying to start webbrowser-app a unresponsive window appears and after a few moments it crashes. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: webbrowser-app 0.23+16.04.20160413-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Wed Jun 8 22:56:35 2016 InstallationDate: Installed on 2016-04-28 (41 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: webbrowser-app UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1590561/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1590561] Re: webbrowser-app crashes on startup on fresh zesty Unity8: No suitable EGL configs found
Crash is triggred When webbrowwser-app tries to create OpenGLContext. and it happens with creation of qml window. this context is shared with oxide so oxide shows error while using context. I could get same egl error log[1] by triggering this call: QOpenGLContext ctx; ctx.create() So In theory it should trigger crash for all Qt5 app (if window is created and they have apparmor profile). I couldn't find any app in current desktop to test it. [1] QEGLPlatformContext: Failed to create context: 3009 QEGLPlatformContext: Failed to create context: 3009 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1590561 Title: webbrowser-app crashes on startup on fresh zesty Unity8: No suitable EGL configs found Status in Canonical System Image: Confirmed Status in Oxide: Confirmed Status in webbrowser-app package in Ubuntu: Invalid Bug description: When trying to start webbrowser-app a unresponsive window appears and after a few moments it crashes. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: webbrowser-app 0.23+16.04.20160413-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Wed Jun 8 22:56:35 2016 InstallationDate: Installed on 2016-04-28 (41 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: webbrowser-app UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1590561/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1590561] Re: webbrowser-app crashes on startup on fresh zesty Unity8: No suitable EGL configs found
Environment: zesty/unity8/radeongpu I can see the EGL crash in my radeon gpu from command line $ webbrowser-app --desktop_file_hint=/usr/share/applications/webbrowser-app.desktop The Crash doesn't happen if I unload the webbrowser apparmor profile. Looking further on apparmor denial I see few number of message with apparmor=DENIED. I tried overriding that in webbrowser-app profile to find out actual missing privilege. and adding these in webbrowser-app profile fixes the issue: /sys/devices/pci[0-9]*/**/config r, This also solves webbrowser spinning problem when launched from scopes -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1590561 Title: webbrowser-app crashes on startup on fresh zesty Unity8: No suitable EGL configs found Status in Canonical System Image: Confirmed Status in Oxide: Confirmed Status in webbrowser-app package in Ubuntu: Invalid Bug description: When trying to start webbrowser-app a unresponsive window appears and after a few moments it crashes. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: webbrowser-app 0.23+16.04.20160413-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Wed Jun 8 22:56:35 2016 InstallationDate: Installed on 2016-04-28 (41 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: webbrowser-app UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1590561/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1590561] Re: webbrowser-app crashes on startup on fresh zesty Unity8: No suitable EGL configs found
Just to clarify actually I didn't see any crash in my test(unity8/zesty/radeon gpu), App gets launched but keeps spinning, same result as Pat mentioned above. After disabling apparmor service webbrowser-app works fine. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1590561 Title: webbrowser-app crashes on startup on fresh zesty Unity8: No suitable EGL configs found Status in Canonical System Image: Confirmed Status in Oxide: Confirmed Status in webbrowser-app package in Ubuntu: Invalid Bug description: When trying to start webbrowser-app a unresponsive window appears and after a few moments it crashes. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: webbrowser-app 0.23+16.04.20160413-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Wed Jun 8 22:56:35 2016 InstallationDate: Installed on 2016-04-28 (41 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: webbrowser-app UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1590561/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1590561] Re: webbrowser-app crashes on startup on fresh zesty Unity8: No suitable EGL configs found
unity8/zesty: In case browser startup screen and spins. it works and load page after disabling apparmor service -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1590561 Title: webbrowser-app crashes on startup on fresh zesty Unity8: No suitable EGL configs found Status in Canonical System Image: Confirmed Status in Oxide: Confirmed Status in webbrowser-app package in Ubuntu: Invalid Bug description: When trying to start webbrowser-app a unresponsive window appears and after a few moments it crashes. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: webbrowser-app 0.23+16.04.20160413-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Wed Jun 8 22:56:35 2016 InstallationDate: Installed on 2016-04-28 (41 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: webbrowser-app UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1590561/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1599771] Re: Webview appears to think it's in focus when typing in the addressbar
The real cause here is we rely on focusOut(In)Event to check for activeFocus item. but the any check of ActiveFocus (hasActiveFocus or window->activeFocusItem) inside focusout/in event give incorrect result. when another item is focused(location bar), window->activeFocusItem() return null not the new activeFocus Item. While check for activeFocus item is consistent Once we get ItemChanged event. http://doc.qt.io/qt-5/qquickitem.html#itemChange So When quickItem activeFocus changes we get ItemChange event and after any check window->activeFocusItem() correctly return the newly focus QuickItem. In short, we should do webview focus update based on ItemChange event. see previous comments also for more on activeFocus behaviour inside focusout/in event. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1599771 Title: Webview appears to think it's in focus when typing in the addressbar Status in Oxide: Confirmed Status in webbrowser-app package in Ubuntu: Invalid Bug description: See the screenshot - when keyboard focus is on the addressbar, the webview thinks it is still in focus (indicated by the presence of the caret in the search field). Not sure if this is Oxide or webbrowser-app To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1599771/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1647353] [NEW] PCI/internal sound card not detected
Public bug reported: the sound card is not detected. the output option in sound settings is showing dummy output. i am using ubuntu 14.04 lts i expected sound while playing a movie but there is no sound. in the sound settings only the output is displaying only dummy out put.(i connected my inspiron 3250 desktop to tv via hdmi, even when external speakers are connected system is not reading them.) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-75.83~14.04.1-generic 3.19.8-ckt22 Uname: Linux 3.19.0-75-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Mon Dec 5 18:28:50 2016 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-osp1-20150720-0 InstallationDate: Installed on 2016-10-18 (48 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20150720-04:06 PackageArchitecture: all ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/17/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 3.2.4 dmi.board.name: 0DNMV1 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr3.2.4:bd06/17/2016:svnDellInc.:pnInspiron3250:pvrX00:rvnDellInc.:rn0DNMV1:rvrA01:cvnDellInc.:ct3:cvrNotSpecified: dmi.product.name: Inspiron 3250 dmi.product.version: X00 dmi.sys.vendor: Dell Inc. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1647353 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: New Bug description: the sound card is not detected. the output option in sound settings is showing dummy output. i am using ubuntu 14.04 lts i expected sound while playing a movie but there is no sound. in the sound settings only the output is displaying only dummy out put.(i connected my inspiron 3250 desktop to tv via hdmi, even when external speakers are connected system is not reading them.) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-75.83~14.04.1-generic 3.19.8-ckt22 Uname: Linux 3.19.0-75-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Mon Dec 5 18:28:50 2016 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-osp1-20150720-0 InstallationDate: Installed on 2016-10-18 (48 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20150720-04:06 PackageArchitecture: all ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/17/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 3.2.4 dmi.board.name: 0DNMV1 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr3.2.4:bd06/17/2016:svnDellInc.:pnInspiron3250:pvrX00:rvnDellInc.:rn0DNMV1:rvrA01:cvnDellInc.:ct3:cvrNotSpecified: dmi.product.name: Inspiron 3250 dmi.product.version: X00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1647353/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1584965] Re: [browser] scrolling uneven and queues up
Some part of bug may be related https://bugs.launchpad.net/oxide/+bug/1643428 (May be) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1584965 Title: [browser] scrolling uneven and queues up Status in Canonical System Image: Confirmed Status in Oxide: Confirmed Status in webbrowser-app package in Ubuntu: Confirmed Bug description: I've noticed this on a bunch of websites, mainly on Arale but also on krillin, both running latest rc-proposed with and without oxide 1.15 The scenario is I'm on page A, navigate to page B, press back button, then try to scroll page A (flicking up). The page doesn't move for a short time then scrolls super fast almost to the bottom. Seems like the scroll events are getting queued up and then all applied at once. This site reproduces it pretty easy for me: 1) goto boston.craigslist.org 2) type "kayak" in the search field 3) you'll get a page full of results 4) click on one of the results 5) wait till page fully loads, flick quickly a few times, first flicks ignored. then press back button 6) wait till page fully loads and then start scrolling (flicking up, multiple times), first flicks ignored/queued then scrolling happens fast Expected results: the page should start scrolling immediately and keep up with action of finger Actual results: the page is not responsive for a few seconds then scrolls super fast toward the bottom To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1584965/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1584965] Re: [browser] scrolling uneven and queues up
Bill confirmed that scrolling is quite improved with latest oxide1.17 and the same issue is not observable. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1584965 Title: [browser] scrolling uneven and queues up Status in Canonical System Image: Confirmed Status in Oxide: Confirmed Status in webbrowser-app package in Ubuntu: Confirmed Bug description: I've noticed this on a bunch of websites, mainly on Arale but also on krillin, both running latest rc-proposed with and without oxide 1.15 The scenario is I'm on page A, navigate to page B, press back button, then try to scroll page A (flicking up). The page doesn't move for a short time then scrolls super fast almost to the bottom. Seems like the scroll events are getting queued up and then all applied at once. This site reproduces it pretty easy for me: 1) goto boston.craigslist.org 2) type "kayak" in the search field 3) you'll get a page full of results 4) click on one of the results 5) wait till page fully loads, flick quickly a few times, first flicks ignored. then press back button 6) wait till page fully loads and then start scrolling (flicking up, multiple times), first flicks ignored/queued then scrolling happens fast Expected results: the page should start scrolling immediately and keep up with action of finger Actual results: the page is not responsive for a few seconds then scrolls super fast toward the bottom To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1584965/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1610929] Re: Implement Screen::GetShellMode()
** Merge proposal linked: https://code.launchpad.net/~santoshbit2007/oxide/+git/oxide/+merge/306388 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1610929 Title: Implement Screen::GetShellMode() Status in Mir: New Status in Oxide: Triaged Status in unity8 package in Ubuntu: New Bug description: This is currently just a stub that returns NonWindowed on mobile devices and Windowed everywhere else. It needs to be more intelligent than that (eg, Windowed on a tablet device) and needs to be dynamic, but I don't think there's a way for us to do that yet. Basically, we need to know whether the shell is in windowed or staged mode. The display's form factor isn't particularly relevant. This is needed to complete bug 1545088 and others. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1610929/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1599771] Re: Webview appears to think it's in focus when typing in the addressbar
FIxed with https://code.launchpad.net/~santoshbit2007/oxide/+git/oxide/+merge/301475 ** Merge proposal linked: https://code.launchpad.net/~santoshbit2007/oxide/+git/oxide/+merge/301475 ** Changed in: oxide Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1599771 Title: Webview appears to think it's in focus when typing in the addressbar Status in Oxide: Fix Committed Status in webbrowser-app package in Ubuntu: Invalid Bug description: See the screenshot - when keyboard focus is on the addressbar, the webview thinks it is still in focus (indicated by the presence of the caret in the search field). Not sure if this is Oxide or webbrowser-app To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1599771/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1584965] Re: [browser] scrolling uneven and queues up
I tried to reproduce the same bug on Arale but to me it looks somewhat ok. I am using lastest oxide. There has been some changes in upstream chromium which might resolved this issue(https://crbug.com/574343#c40). I can see similar janked scrolling when I use --disable-features=SchedulerExpensiveTaskBlocking Which was default in chromium sometime before. I feel bug should not occur in latest oxide. Could you confirm that this bug is happening with latest trunk oxide also -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1584965 Title: [browser] scrolling uneven and queues up Status in Canonical System Image: Confirmed Status in Oxide: Confirmed Status in webbrowser-app package in Ubuntu: Confirmed Bug description: I've noticed this on a bunch of websites, mainly on Arale but also on krillin, both running latest rc-proposed with and without oxide 1.15 The scenario is I'm on page A, navigate to page B, press back button, then try to scroll page A (flicking up). The page doesn't move for a short time then scrolls super fast almost to the bottom. Seems like the scroll events are getting queued up and then all applied at once. This site reproduces it pretty easy for me: 1) goto boston.craigslist.org 2) type "kayak" in the search field 3) you'll get a page full of results 4) click on one of the results 5) wait till page fully loads, flick quickly a few times, first flicks ignored. then press back button 6) wait till page fully loads and then start scrolling (flicking up, multiple times), first flicks ignored/queued then scrolling happens fast Expected results: the page should start scrolling immediately and keep up with action of finger Actual results: the page is not responsive for a few seconds then scrolls super fast toward the bottom To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1584965/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1584965] Re: [browser] scrolling uneven and queues up
Initial investigation: There seems to be a blocking of task by blink scheduler because of prioritization of other task. So this may be result of side effect of blink scheduler policy. Need to check more before any conclusion. I get this log on console thrown by blink scheduler while scrolling on slashdot.org qml: [JS] (https://slashdot.org/:0) Blink deferred a task in order to make scrolling smoother. Your timer and network tasks should take less than 50ms to run to avoid this. Please see https://developers.google.com/web/tools/chrome-devtools/profile /evaluate-performance/rail and https://crbug.com/574343#c40 for more information. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1584965 Title: [browser] scrolling uneven and queues up Status in Canonical System Image: Confirmed Status in Oxide: Confirmed Status in webbrowser-app package in Ubuntu: Confirmed Bug description: I've noticed this on a bunch of websites, mainly on Arale but also on krillin, both running latest rc-proposed with and without oxide 1.15 The scenario is I'm on page A, navigate to page B, press back button, then try to scroll page A (flicking up). The page doesn't move for a short time then scrolls super fast almost to the bottom. Seems like the scroll events are getting queued up and then all applied at once. This site reproduces it pretty easy for me: 1) goto boston.craigslist.org 2) type "kayak" in the search field 3) you'll get a page full of results 4) click on one of the results 5) wait till page fully loads, flick quickly a few times, first flicks ignored. then press back button 6) wait till page fully loads and then start scrolling (flicking up, multiple times), first flicks ignored/queued then scrolling happens fast Expected results: the page should start scrolling immediately and keep up with action of finger Actual results: the page is not responsive for a few seconds then scrolls super fast toward the bottom To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1584965/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1610929] Re: Implement Screen::GetShellMode()
I have a small doubt, Does Gettings automatically dynamically track connection of mouse and keyboard to tell about window mode OR its just the track the static(and user changable) setting menu in unity8. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1610929 Title: Implement Screen::GetShellMode() Status in Mir: New Status in Oxide: Triaged Status in unity8 package in Ubuntu: New Bug description: This is currently just a stub that returns NonWindowed on mobile devices and Windowed everywhere else. It needs to be more intelligent than that (eg, Windowed on a tablet device) and needs to be dynamic, but I don't think there's a way for us to do that yet. Basically, we need to know whether the shell is in windowed or staged mode. The display's form factor isn't particularly relevant. This is needed to complete bug 1545088 and others. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1610929/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1615455] [NEW] package libglib2.0-0:amd64 2.48.1-1~ubuntu16.04.1 failed to install/upgrade: dependency problems - leaving triggers unprocessed
Public bug reported: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu sant-64@sant64-desktop:~$ lsb_release -rd Description:Ubuntu 16.04.1 LTS Release:16.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center apt-cache policy libglib2.0-0:amd64 libglib2.0-0: Installed: 2.48.1-1~ubuntu16.04.1 Candidate: 2.48.1-1~ubuntu16.04.1 Version table: *** 2.48.1-1~ubuntu16.04.1 500 500 http://in.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 2.48.0-1ubuntu4 500 500 http://in.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 3) What you expected to happen Installation/upgradation 4) What happened instead Error as desibed above ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libglib2.0-0:amd64 2.48.1-1~ubuntu16.04.1 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Sun Aug 21 20:19:49 2016 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2015-09-19 (337 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: glib2.0 Title: package libglib2.0-0:amd64 2.48.1-1~ubuntu16.04.1 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to xenial on 2016-08-21 (0 days ago) ** Affects: glib2.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1615455 Title: package libglib2.0-0:amd64 2.48.1-1~ubuntu16.04.1 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in glib2.0 package in Ubuntu: New Bug description: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu sant-64@sant64-desktop:~$ lsb_release -rd Description: Ubuntu 16.04.1 LTS Release: 16.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center apt-cache policy libglib2.0-0:amd64 libglib2.0-0: Installed: 2.48.1-1~ubuntu16.04.1 Candidate: 2.48.1-1~ubuntu16.04.1 Version table: *** 2.48.1-1~ubuntu16.04.1 500 500 http://in.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 2.48.0-1ubuntu4 500 500 http://in.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 3) What you expected to happen Installation/upgradation 4) What happened instead Error as desibed above ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libglib2.0-0:amd64 2.48.1-1~ubuntu16.04.1 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Sun Aug 21 20:19:49 2016 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2015-09-19 (337 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: glib2.0 Title: package libglib2.0-0:amd64 2.48.1-1~ubuntu16.04.1 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to xenial on 2016-08-21 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1615455/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1612659] Re: QScreen::nativeOrientation is wrong on the M10
Issue happening on oxide : https://bugs.launchpad.net/oxide/+bug/1601887 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtubuntu in Ubuntu. https://bugs.launchpad.net/bugs/1612659 Title: QScreen::nativeOrientation is wrong on the M10 Status in qtubuntu package in Ubuntu: New Bug description: This is a follow up bug to issues spotted in Oxide, where we rely on QScreen orientation properties to adjust the camera rotation. We noticed that apps on the M10 always receive a nativeOrientation reply of "portrait" whereas it should be landscape. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtubuntu/+bug/1612659/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1599771] Re: Webview appears to think it's in focus when typing in the addressbar
Ready for review: ttps://code.launchpad.net/~santoshbit2007/oxide/+git/oxide/+merge/301475 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1599771 Title: Webview appears to think it's in focus when typing in the addressbar Status in Oxide: In Progress Status in webbrowser-app package in Ubuntu: Invalid Bug description: See the screenshot - when keyboard focus is on the addressbar, the webview thinks it is still in focus (indicated by the presence of the caret in the search field). Not sure if this is Oxide or webbrowser-app To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1599771/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1599771] Re: Webview appears to think it's in focus when typing in the addressbar
QQuickWindow::activeFocusItem() is fine , I was just doubtful with it being null. I am going to patch it with using same -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1599771 Title: Webview appears to think it's in focus when typing in the addressbar Status in Oxide: Triaged Status in webbrowser-app package in Ubuntu: Invalid Bug description: See the screenshot - when keyboard focus is on the addressbar, the webview thinks it is still in focus (indicated by the presence of the caret in the search field). Not sure if this is Oxide or webbrowser-app To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1599771/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1599771] Re: Webview appears to think it's in focus when typing in the addressbar
QQuickWindow::activeFocusItem will still be tricky. There seems to be fundamental issue with focus events sent. FocusEvent are only sent to Item when its activeFocus = true; So when we focus is removed from item it won't immediately set activeFocus=false(since item won't get focus event then). What is does is, first send focusOutEvent to item, then set activeFocus = false; And when webview is clicked we forcefully need to set activeFocus=true(item_->forceActiveFocus in handleMousePress). then item is eligible to receive focusInEvent. In short activeFocus is updated after focusOutEvent and before focusInEvent. In this way In focusOutEvent both activeFocus and QQuickWindow::activeFocusItem both are not upated, QQuickWindow::activeFocusItem is specifically nullptr -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1599771 Title: Webview appears to think it's in focus when typing in the addressbar Status in Oxide: Triaged Status in webbrowser-app package in Ubuntu: Invalid Bug description: See the screenshot - when keyboard focus is on the addressbar, the webview thinks it is still in focus (indicated by the presence of the caret in the search field). Not sure if this is Oxide or webbrowser-app To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1599771/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1599771] Re: Webview appears to think it's in focus when typing in the addressbar
it seems focusOutEvent comes too early to QQuickItem. by that time activefocus is not updated, so it still holds earlier value. Once activeFocus of QQuickItem is changed we get ItemChanged(http://doc.qt.io/qt-5/qquickitem.html#ItemChange-enum). I tested it OxideQQuickWebView::itemChange has correct value of activeFocus. Inside: itemChangeItemChange : 6 Value : 0 // 6 represent QQuickItem::ItemActiveFocusHasChanged ActiveFocusItem : 0 So I was wondering if we should move focus handling inside OxideQQuickWebView::itemChange OR tweak HasFocus() -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1599771 Title: Webview appears to think it's in focus when typing in the addressbar Status in Oxide: Confirmed Status in webbrowser-app package in Ubuntu: Invalid Bug description: See the screenshot - when keyboard focus is on the addressbar, the webview thinks it is still in focus (indicated by the presence of the caret in the search field). Not sure if this is Oxide or webbrowser-app To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1599771/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1599771] Re: Webview appears to think it's in focus when typing in the addressbar
Olivier Surprising it is, I was checking from oxide side, and QQuickWeview activeFocus is set to true. So I was doubting issue in webbrowser-app -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1599771 Title: Webview appears to think it's in focus when typing in the addressbar Status in Oxide: New Status in webbrowser-app package in Ubuntu: New Bug description: See the screenshot - when keyboard focus is on the addressbar, the webview thinks it is still in focus (indicated by the presence of the caret in the search field). Not sure if this is Oxide or webbrowser-app To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1599771/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1573620] Re: can't deselect text after selecting on nytimes.com
** Changed in: webapps-sprint Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1573620 Title: can't deselect text after selecting on nytimes.com Status in Canonical System Image: Fix Committed Status in Oxide: Invalid Status in webapps-sprint: Fix Committed Status in webbrowser-app package in Ubuntu: Fix Released Bug description: This occurs on nytimes.com, most other sites works but guessing others will not work as well. Steps to reproduce: - go to nytimes.com and click on a news article - long press and drag the handles to select some text - tap on another area of the page to deselect the selected text Expected results: - selected text should become unselected Actual results: - text remains selected Note, this works correctly in Chrome for iOS To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1573620/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1575604] Re: Fast repeated scrolling with a finger changes direction of the scrolling
I had difficulty in producing this bug on my Meizu Mx4 with latest oxide code. I tried with twitter and theverge.com. Could you specify exact steps to produce this bug so I can try -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1575604 Title: Fast repeated scrolling with a finger changes direction of the scrolling Status in Oxide: Triaged Status in webbrowser-app package in Ubuntu: Confirmed Bug description: When scrolling on a page with repeated gestures with the finger on the screen, it often changes the direction of the scrolling and scrolls super fast. So if I am far down on a page and scrolls a few times with the finger, it suddenly start to scroll upwards super fast to the top. It seems like it happens if it lags while scrolling and it misses part of the gesture. Experienced on an M10 with OTA-10.1 To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1575604/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1579101] Re: no keyboard shortcuts in webapp containers
I have added shortcut handling for back/forward and reload. I generally thinks, webcontainer should not have all shortcut handling that webbrowser-app have Any recommendations will be welcomed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1579101 Title: no keyboard shortcuts in webapp containers Status in Canonical System Image: Confirmed Status in webapps-sprint: Triaged Status in webbrowser-app package in Ubuntu: Confirmed Bug description: having a keyboard attached to the phone/tablet i can use things like Ctrl-R or Alt+Left/Right to navigate in the webbrowser app ... none of these shortcuts work in webapp-containers though (while scrolling via cursor keys and PgUp and PgDn works) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1579101/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1579101] Re: no keyboard shortcuts in webapp containers
ready for review : https://code.launchpad.net/~santoshbit2007/webbrowser-app/webcontainer_shortcut_fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1579101 Title: no keyboard shortcuts in webapp containers Status in Canonical System Image: Confirmed Status in webapps-sprint: Triaged Status in webbrowser-app package in Ubuntu: Confirmed Bug description: having a keyboard attached to the phone/tablet i can use things like Ctrl-R or Alt+Left/Right to navigate in the webbrowser app ... none of these shortcuts work in webapp-containers though (while scrolling via cursor keys and PgUp and PgDn works) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1579101/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1448145] Re: [Ubuntu Phone] The first characters are always in uppercase in webapps
It is possible to fix this if : -- when word suggestion is disabled keyboard should send only single event with commit_string to be committed. this means preedit is diabled and we are inserting char directly. As of now current behaviour is it sends two event for every character pressed, once containing preedit_char and another containing commit_char. having same value. There is not point in these two event. --- somehow oxide has knowledge of keyboard setting, like if word suggestion is disabled, In this case oxide can stop composing preedittext and directly commit the string. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1448145 Title: [Ubuntu Phone] The first characters are always in uppercase in webapps Status in Canonical System Image: In Progress Status in Oxide: In Progress Status in ubuntu-keyboard: Confirmed Status in Ubuntu UX: Invalid Status in webapps-sprint: In Progress Status in ubuntu-keyboard package in Ubuntu: Confirmed Bug description: Hi! In the BQ Ubuntu Edition, when I write anything in any webapp (it works fine in native apps), the first 2 letters are auto uppercase. It should be uppercase just the first letter. Steps: 1. Open Twitter webapp 2. Write a tweet 3. Press "hello" > BUG: You'll see HEllo. It should be Hello. Thanks in advance! To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1448145/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1573620] Re: can't deselect text after selecting on nytimes.com
https://code.launchpad.net/~santoshbit2007/webbrowser-app/webbrowser- app/+merge/296521 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1573620 Title: can't deselect text after selecting on nytimes.com Status in Canonical System Image: In Progress Status in Oxide: Invalid Status in webapps-sprint: In Progress Status in webbrowser-app package in Ubuntu: Confirmed Bug description: This occurs on nytimes.com, most other sites works but guessing others will not work as well. Steps to reproduce: - go to nytimes.com and click on a news article - long press and drag the handles to select some text - tap on another area of the page to deselect the selected text Expected results: - selected text should become unselected Actual results: - text remains selected Note, this works correctly in Chrome for iOS To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1573620/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1573620] Re: can't deselect text after selecting on nytimes.com
Yes, I am doing that today now On Thu, Jun 2, 2016 at 2:30 PM, Olivier Tilloy <olivier.til...@canonical.com > wrote: > I have verified that with a custom UA string override for > mobile.nytimes.com, the issue goes away. > I used an iphone UA string: > >Mozilla/5.0 (iPhone; CPU iPhone OS 5_0 like Mac OS X) > AppleWebKit/534.46 (KHTML, like Gecko) Version/5.1 Mobile/9A334 > Safari/7534.48.3 > > But I’m guessing that an android one would do just fine, too. > > Santosh, would you mind adding such an override to the browser? The > relevant file is https://bazaar.launchpad.net/~phablet-team/webbrowser- > app/trunk/view/head:/src/Ubuntu/Web/ua-overrides-mobile.js. > > ** Changed in: oxide >Status: In Progress => Invalid > > ** Also affects: webbrowser-app (Ubuntu) >Importance: Undecided >Status: New > > ** Changed in: webbrowser-app (Ubuntu) >Status: New => Confirmed > > ** Changed in: webbrowser-app (Ubuntu) > Assignee: (unassigned) => Santosh (santoshbit2007) > > ** Changed in: webbrowser-app (Ubuntu) >Importance: Undecided => Medium > > -- > You received this bug notification because you are a bug assignee. > https://bugs.launchpad.net/bugs/1573620 > > Title: > can't deselect text after selecting on nytimes.com > > Status in Canonical System Image: > In Progress > Status in Oxide: > Invalid > Status in webapps-sprint: > In Progress > Status in webbrowser-app package in Ubuntu: > Confirmed > > Bug description: > This occurs on nytimes.com, most other sites works but guessing others > will not work as well. > > Steps to reproduce: > - go to nytimes.com and click on a news article > - long press and drag the handles to select some text > - tap on another area of the page to deselect the selected text > > Expected results: > - selected text should become unselected > > Actual results: > - text remains selected > > Note, this works correctly in Chrome for iOS > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/canonical-devices-system-image/+bug/1573620/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1573620 Title: can't deselect text after selecting on nytimes.com Status in Canonical System Image: In Progress Status in Oxide: Invalid Status in webapps-sprint: In Progress Status in webbrowser-app package in Ubuntu: Confirmed Bug description: This occurs on nytimes.com, most other sites works but guessing others will not work as well. Steps to reproduce: - go to nytimes.com and click on a news article - long press and drag the handles to select some text - tap on another area of the page to deselect the selected text Expected results: - selected text should become unselected Actual results: - text remains selected Note, this works correctly in Chrome for iOS To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1573620/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1573620] Re: can't deselect text after selecting on nytimes.com
I am doing it today, -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1573620 Title: can't deselect text after selecting on nytimes.com Status in Canonical System Image: In Progress Status in Oxide: Invalid Status in webapps-sprint: In Progress Status in webbrowser-app package in Ubuntu: Confirmed Bug description: This occurs on nytimes.com, most other sites works but guessing others will not work as well. Steps to reproduce: - go to nytimes.com and click on a news article - long press and drag the handles to select some text - tap on another area of the page to deselect the selected text Expected results: - selected text should become unselected Actual results: - text remains selected Note, this works correctly in Chrome for iOS To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1573620/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1448145] Re: [Ubuntu Phone] The first characters are always in uppercase in webapps
Cause of bug : The issue happens when preedit_string == commit_string, In this case, on commit string we dont't receive updateSelectionBounds from blink(since bounds is not changed and same as in preedit mode). Calculation of cursor position happens on updateSelectionBounds, So In this case after commit it doesn't happen and the current cursor position is left as last calculated cursor position. this bug can happpen even when word suggestion is enabled and preedit == commit string. I couldn't find direct elegant solution of this so trying to tweak some cases and check for side effect.May be forcing updateSelectionBounds after commit will work -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1448145 Title: [Ubuntu Phone] The first characters are always in uppercase in webapps Status in Canonical System Image: Confirmed Status in Oxide: Confirmed Status in ubuntu-keyboard: Confirmed Status in Ubuntu UX: Invalid Status in webapps-sprint: New Status in ubuntu-keyboard package in Ubuntu: Confirmed Bug description: Hi! In the BQ Ubuntu Edition, when I write anything in any webapp (it works fine in native apps), the first 2 letters are auto uppercase. It should be uppercase just the first letter. Steps: 1. Open Twitter webapp 2. Write a tweet 3. Press "hello" > BUG: You'll see HEllo. It should be Hello. Thanks in advance! To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1448145/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1352718] Re: Unknown memory utilization in Ubuntu14.04 Trusty
** Package changed: ubuntu = procps (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to procps in Ubuntu.
https://bugs.launchpad.net/bugs/1352718
Title:
Unknown memory utilization in Ubuntu14.04 Trusty
Status in “procps” package in Ubuntu:
New
Bug description:
I'm running Ubuntu Trusty 14.04 on a new machine with 8GB of RAM, and
it seems to be locking up periodically and nothing is in syslog file.
I've installed Nagios and have been watching the graphs, and it looks
like memory is going high from 7% to 72% in just a span of 10 mins.
Only node process are running on server. In top I found all process
are running very normal memory consumption. Even after stopping node
process. Memory remains with same utilization.
free agrees, claiming I'm using more than 5.7G of memory:
free -h
total used free sharedbuffers cached
Mem: 7.8G 6.5G 1.3G 2.2M 233M 612M
-/+ buffers/cache: 5.7G 2.1G
Swap: 2.0G 0B 2.0G
However, I'm having trouble determining what exactly is eating all of that
memory. Running top or htop doesn't seem to single anything out, and ps_mem.py
(https://raw.github.com/pixelb/ps_mem/master/ps_mem.py) claims that I'm using
much less than the system thinks...
...
Private + Shared = RAM used Program
184.0 KiB + 29.5 KiB = 213.5 KiB atd
176.0 KiB + 48.5 KiB = 224.5 KiB acpid
164.0 KiB + 99.5 KiB = 263.5 KiB anvil
272.0 KiB + 52.0 KiB = 324.0 KiB upstart-file-bridge
288.0 KiB + 76.0 KiB = 364.0 KiB cron
312.0 KiB + 60.0 KiB = 372.0 KiB irqbalance
208.0 KiB + 188.0 KiB = 396.0 KiB sh (2)
328.0 KiB + 87.5 KiB = 415.5 KiB upstart-udev-bridge
312.0 KiB + 104.5 KiB = 416.5 KiB log
424.0 KiB + 53.5 KiB = 477.5 KiB upstart-socket-bridge
304.0 KiB + 213.5 KiB = 517.5 KiB pickup
336.0 KiB + 213.5 KiB = 549.5 KiB qmgr
396.0 KiB + 165.5 KiB = 561.5 KiB dovecot
360.0 KiB + 205.5 KiB = 565.5 KiB master
528.0 KiB + 52.5 KiB = 580.5 KiB nrpe
608.0 KiB + 148.5 KiB = 756.5 KiB systemd-logind
764.0 KiB + 61.5 KiB = 825.5 KiB dbus-daemon
772.0 KiB + 107.0 KiB = 879.0 KiB top
808.0 KiB + 87.5 KiB = 895.5 KiB systemd-udevd
940.0 KiB + 147.5 KiB = 1.1 MiB ntpd
956.0 KiB + 285.0 KiB = 1.2 MiB getty (6)
1.1 MiB + 134.0 KiB = 1.2 MiB config
1.6 MiB + 121.5 KiB = 1.7 MiB init
2.5 MiB + 22.0 KiB = 2.6 MiB dhclient
2.8 MiB + 476.5 KiB = 3.3 MiB vmtoolsd
4.2 MiB + 452.5 KiB = 4.6 MiB whoopsie
5.1 MiB + 96.5 KiB = 5.2 MiB rsyslogd
3.6 MiB + 2.3 MiB = 5.9 MiB sshd (4)
6.7 MiB + 1.0 MiB = 7.7 MiB bash (3)
8.3 MiB + 277.5 KiB = 8.6 MiB redis-server (3)
13.0 MiB + 26.5 KiB = 13.0 MiB docker
342.0 MiB + 6.9 MiB = 348.9 MiB nodejs (8)
-
414.3 MiB
=
This other formula for totaling the memory roughly agrees:
# ps -e -orss=,args= | sort -b -k1,1n | awk '{total = total +
$1}END{print total}'
503612
If the processes only total 500 MiB, where's the rest of the memory
going?
Slabtop doesn't look like I have a huge cache or anything...
Active / Total Objects (% used): 672886 / 681837 (98.7%)
Active / Total Slabs (% used) : 15441 / 15441 (100.0%)
Active / Total Caches (% used) : 70 / 101 (69.3%)
Active / Total Size (% used) : 179811.23K / 184282.05K (97.6%)
Minimum / Average / Maximum Object : 0.01K / 0.27K / 8.00K
OBJS ACTIVE USE OBJ SIZE SLABS OBJ/SLAB CACHE SIZE NAME
171318 171318 100%0.19K 4079 42 32632K dentry
127257 127257 100%0.10K 3263 39 13052K buffer_head
75669 75669 100%0.96K 2293 33 73376K ext4_inode_cache
35328 34959 98%0.06K552 64 2208K kmalloc-64
33354 33354 100%0.04K327 102 1308K ext4_extent_status
25560 25560 100%0.11K710 36 2840K sysfs_dir_cache
18944 18944 100%0.01K 37 512 148K kmalloc-8
18848 18848 100%0.50K589 32 9424K kmalloc-512
17680 17680 100%0.05K208 85 832K shared_policy_node
17248 17248 100%0.12K539 32 2156K au_dinfo
15390 9116 59%0.55K270 57 8640K radix_tree_node
15372 15372 100%0.09K366 42 1464K kmalloc-96
13398 13398 100%0.75K319 42 10208K au_icntnr
11424 11424 100%0.57K204 56 6528K
