[Desktop-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 Desktop 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: [Desktop-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 Desktop 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-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 Desktop 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-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 Desktop 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-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 Desktop 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"
[Desktop-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 Desktop 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
[Desktop-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 Desktop 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="/run/d
[Desktop-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
[Desktop-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 Desktop 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"
[Desktop-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 Desktop 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 dmi.modalias:
[Desktop-packages] [Bug 1692825] [NEW] Error while Sending message. Welcome response error: Input/output error issue arrives in smtp configuration, I have tried smtpserver:25 SSL configuration but it
Public bug reported: I want to upgrade Evolution client from 3.18.5.2 to 3.20.4 on Ubuntu 16.04 Xenial. How can I do that. The launchpad has only 3.18.5.2. Appreciate your help, ... Dario ** Affects: evolution (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1692825 Title: Error while Sending message. Welcome response error: Input/output error issue arrives in smtp configuration, I have tried smtpserver:25 SSL configuration but it doesn't work. give me the solution on above issue. Status in evolution package in Ubuntu: New Bug description: I want to upgrade Evolution client from 3.18.5.2 to 3.20.4 on Ubuntu 16.04 Xenial. How can I do that. The launchpad has only 3.18.5.2. Appreciate your help, ... Dario To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1692825/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-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 Desktop 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-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 Desktop 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1309850] Re: Machine not able to boot into ubuntu by default. After using advance booting option and restart machine boots.
Hey, I am also having same machine with same configuration and having same issue with ubuntu 14.04. If anybody got the solution please let me know ASAP. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1309850 Title: Machine not able to boot into ubuntu by default. After using advance booting option and restart machine boots. Status in “fglrx-installer” package in Ubuntu: New Bug description: My machine in intel i5 dell inspiron n5010. Dual boot with Both windows 8.1 and ubuntu. I have problem with amd display ati driver after ubuntu version 13.10. It still persits in this version of ubuntu 14.04. Hoped my problem will be sorted in this version expected much from this version. Problem persists. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1309850/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1224438] [NEW] Menus on evince black with grey text.
Public bug reported: The evince application's menus do not follow the overall Lubuntu's default theme. Instead they are black in colour with the menu items in grey. This contrasts visibly with the rest of the system, and also because of grey on black, it is very difficult to use. Incative menu items are in light grey with active ones in darker grey. Inactive menu items are bolded as well. This makes the user think the inactive items are active. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: evince 3.9.90-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-7.13-generic 3.11.0 Uname: Linux 3.11.0-7-generic x86_64 ApportVersion: 2.12.1-0ubuntu3 Architecture: amd64 Date: Thu Sep 12 17:10:59 2013 EcryptfsInUse: Yes InstallationDate: Installed on 2013-09-11 (0 days ago) InstallationMedia: Lubuntu 13.10 Saucy Salamander - Alpha amd64 (20130902.1) MarkForUpload: True SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: evince (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1224438 Title: Menus on evince black with grey text. Status in “evince” package in Ubuntu: New Bug description: The evince application's menus do not follow the overall Lubuntu's default theme. Instead they are black in colour with the menu items in grey. This contrasts visibly with the rest of the system, and also because of grey on black, it is very difficult to use. Incative menu items are in light grey with active ones in darker grey. Inactive menu items are bolded as well. This makes the user think the inactive items are active. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: evince 3.9.90-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-7.13-generic 3.11.0 Uname: Linux 3.11.0-7-generic x86_64 ApportVersion: 2.12.1-0ubuntu3 Architecture: amd64 Date: Thu Sep 12 17:10:59 2013 EcryptfsInUse: Yes InstallationDate: Installed on 2013-09-11 (0 days ago) InstallationMedia: Lubuntu 13.10 Saucy Salamander - Alpha amd64 (20130902.1) MarkForUpload: True SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1224438/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
