[Touch-packages] [Bug 1922338] [NEW] Bluetooth not working after reboot after upgrade to 21.04
Public bug reported: 1) Description:Ubuntu Hirsute Hippo (development branch) Release:21.04 2) bluez: Installed: 5.56-0ubuntu3 Candidate: 5.56-0ubuntu3 Version table: *** 5.56-0ubuntu3 500 500 http://pl.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages 100 /var/lib/dpkg/status After every reboot bluetooth doesn't work. The GNOME bluetooth on/off switch can be changed but doesn't have any effect - no devices are shown. Output from systemctl after reboot: karol@toronto:~$ systemctl status bluetooth.service ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled) Active: active (running) since Fri 2021-04-02 11:26:31 CEST; 2min 6s ago Docs: man:bluetoothd(8) Main PID: 811 (bluetoothd) Status: "Running" Tasks: 1 (limit: 14115) Memory: 3.2M CGroup: /system.slice/bluetooth.service └─811 /usr/lib/bluetooth/bluetoothd Apr 02 11:26:24 toronto systemd[1]: Starting Bluetooth service... Apr 02 11:26:25 toronto bluetoothd[811]: Bluetooth daemon 5.56 Apr 02 11:26:31 toronto systemd[1]: Started Bluetooth service. Apr 02 11:26:31 toronto bluetoothd[811]: Starting SDP server Apr 02 11:26:32 toronto bluetoothd[811]: Bluetooth management interface 1.19 initialized Apr 02 11:26:37 toronto bluetoothd[811]: Failed to set mode: Blocked through rfkill (0x12) Apr 02 11:27:21 toronto bluetoothd[811]: Failed to set mode: Blocked through rfkill (0x12) Apr 02 11:27:48 toronto bluetoothd[811]: Endpoint registered: sender=:1.72 path=/MediaEndpoint/A2DPSink/sbc Apr 02 11:27:48 toronto bluetoothd[811]: Endpoint registered: sender=:1.72 path=/MediaEndpoint/A2DPSource/sbc Then after running `sudo systemctl restart bluetooth` everything seems to be fine: karol@toronto:~$ sudo systemctl restart bluetooth [sudo] password for karol: karol@toronto:~$ systemctl status bluetooth.service ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled) Active: active (running) since Fri 2021-04-02 11:30:13 CEST; 3s ago Docs: man:bluetoothd(8) Main PID: 3152 (bluetoothd) Status: "Running" Tasks: 1 (limit: 14115) Memory: 760.0K CGroup: /system.slice/bluetooth.service └─3152 /usr/lib/bluetooth/bluetoothd Apr 02 11:30:13 toronto systemd[1]: Starting Bluetooth service... Apr 02 11:30:13 toronto bluetoothd[3152]: Bluetooth daemon 5.56 Apr 02 11:30:13 toronto systemd[1]: Started Bluetooth service. Apr 02 11:30:13 toronto bluetoothd[3152]: Starting SDP server Apr 02 11:30:13 toronto bluetoothd[3152]: Bluetooth management interface 1.19 initialized Apr 02 11:30:15 toronto bluetoothd[3152]: Endpoint registered: sender=:1.72 path=/MediaEndpoint/A2DPSink/sbc Apr 02 11:30:15 toronto bluetoothd[3152]: Endpoint registered: sender=:1.72 path=/MediaEndpoint/A2DPSource/sbc karol@toronto:~$ ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Apr 2 11:31:48 2021 InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 80Q7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-13-generic root=UUID=9996d76c-d95e-4d4c-8902-0a583a091e93 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to hirsute on 2021-04-02 (0 days ago) dmi.bios.date: 12/16/2015 dmi.bios.release: 1.43 dmi.bios.vendor: LENOVO dmi.bios.version: D5CN43WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Paris 5A8 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 300-15ISK dmi.ec.firmware.release: 1.43 dmi.modalias: dmi:bvnLENOVO:bvrD5CN43WW:bd12/16/2015:br1.43:efr1.43:svnLENOVO:pn80Q7:pvrLenovoideapad300-15ISK:rvnLENOVO:rnParis5A8:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad300-15ISK: dmi.product.family: IDEAPAD dmi.product.name: 80Q7 dmi.product.sku: LENOVO_MT_80Q7_BU_idea_FM_Lenovo ideapad 300-15ISK dmi.product.version: Lenovo ideapad 300-15ISK dmi.sys.vendor: LENOVO hciconfig: hci0: Type: Primary Bus: USB BD Address: 08:D4:0C:C4:D1:2C ACL MTU: 1021:5 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:14133 acl:230 sco:0 events:330 errors:0 TX bytes:5930 acl:17 sco:0 commands:164 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute wayland-session ** Description changed: 1) Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 2) bluez: - Installed: 5.56-0ubuntu3 - Candidate: 5.56-0ubuntu3 - Version table: - *** 5.56-0ubuntu3 500 - 500 http://pl.archive.ubuntu
[Touch-packages] [Bug 1922340] Re: GNOME lock screen wallpaper turns black on main display
** Also affects: wayland (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1922340 Title: GNOME lock screen wallpaper turns black on main display Status in gnome-shell package in Ubuntu: New Status in wayland package in Ubuntu: New Bug description: 1) Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 2) gnome-shell: Installed: 3.38.4-1ubuntu1 Candidate: 3.38.4-1ubuntu1 Version table: *** 3.38.4-1ubuntu1 500 500 http://pl.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages 100 /var/lib/dpkg/status 3) This bug only appears on Gnome with Wayland. It does not affect Gnome on xorg. After the screen stays off and locked for some time the wallpaper on the main display turns black. It never happens on the secondary display. The issue is also reported, here on gitlab: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3206 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Apr 2 11:50:15 2021 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 3.38.4-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2021-04-02 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1922340/+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 1922338] Re: Bluetooth not working after reboot after upgrade to 21.04
Seems that the steps to fixing this issue are: 1) Turn on bluetooth in GNOME (has no effect) 2) Then: sudo systemctl restart bluetooth And then it works -- 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/1922338 Title: Bluetooth not working after reboot after upgrade to 21.04 Status in bluez package in Ubuntu: New Bug description: 1) Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 2) bluez: Installed: 5.56-0ubuntu3 Candidate: 5.56-0ubuntu3 Version table: *** 5.56-0ubuntu3 500 500 http://pl.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages 100 /var/lib/dpkg/status After every reboot bluetooth doesn't work. The GNOME bluetooth on/off switch can be changed but doesn't have any effect - no devices are shown. Output from systemctl after reboot: karol@toronto:~$ systemctl status bluetooth.service ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled) Active: active (running) since Fri 2021-04-02 11:26:31 CEST; 2min 6s ago Docs: man:bluetoothd(8) Main PID: 811 (bluetoothd) Status: "Running" Tasks: 1 (limit: 14115) Memory: 3.2M CGroup: /system.slice/bluetooth.service └─811 /usr/lib/bluetooth/bluetoothd Apr 02 11:26:24 toronto systemd[1]: Starting Bluetooth service... Apr 02 11:26:25 toronto bluetoothd[811]: Bluetooth daemon 5.56 Apr 02 11:26:31 toronto systemd[1]: Started Bluetooth service. Apr 02 11:26:31 toronto bluetoothd[811]: Starting SDP server Apr 02 11:26:32 toronto bluetoothd[811]: Bluetooth management interface 1.19 initialized Apr 02 11:26:37 toronto bluetoothd[811]: Failed to set mode: Blocked through rfkill (0x12) Apr 02 11:27:21 toronto bluetoothd[811]: Failed to set mode: Blocked through rfkill (0x12) Apr 02 11:27:48 toronto bluetoothd[811]: Endpoint registered: sender=:1.72 path=/MediaEndpoint/A2DPSink/sbc Apr 02 11:27:48 toronto bluetoothd[811]: Endpoint registered: sender=:1.72 path=/MediaEndpoint/A2DPSource/sbc Then after running `sudo systemctl restart bluetooth` everything seems to be fine: karol@toronto:~$ sudo systemctl restart bluetooth [sudo] password for karol: karol@toronto:~$ systemctl status bluetooth.service ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled) Active: active (running) since Fri 2021-04-02 11:30:13 CEST; 3s ago Docs: man:bluetoothd(8) Main PID: 3152 (bluetoothd) Status: "Running" Tasks: 1 (limit: 14115) Memory: 760.0K CGroup: /system.slice/bluetooth.service └─3152 /usr/lib/bluetooth/bluetoothd Apr 02 11:30:13 toronto systemd[1]: Starting Bluetooth service... Apr 02 11:30:13 toronto bluetoothd[3152]: Bluetooth daemon 5.56 Apr 02 11:30:13 toronto systemd[1]: Started Bluetooth service. Apr 02 11:30:13 toronto bluetoothd[3152]: Starting SDP server Apr 02 11:30:13 toronto bluetoothd[3152]: Bluetooth management interface 1.19 initialized Apr 02 11:30:15 toronto bluetoothd[3152]: Endpoint registered: sender=:1.72 path=/MediaEndpoint/A2DPSink/sbc Apr 02 11:30:15 toronto bluetoothd[3152]: Endpoint registered: sender=:1.72 path=/MediaEndpoint/A2DPSource/sbc karol@toronto:~$ ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Apr 2 11:31:48 2021 InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 80Q7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-13-generic root=UUID=9996d76c-d95e-4d4c-8902-0a583a091e93 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to hirsute on 2021-04-02 (0 days ago) dmi.bios.date: 12/16/2015 dmi.bios.release: 1.43 dmi.bios.vendor: LENOVO dmi.bios.version: D5CN43WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Paris 5A8 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 300-15ISK dmi.ec.firmware.release: 1.43 dmi.modalias: dmi:bvnLENOVO:bvrD5CN43WW:bd12/16/2015:br1.43:efr1.43:svnLENOVO:pn80Q7:pvrLenovoideapad300-15ISK:rvnLENOVO:rnParis5A8:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad300-15ISK: dmi.product.family: IDEAPAD dmi.product.name: 80Q7 dmi.product.sku: LENOVO_MT_80Q7_BU_idea_FM_Lenovo ideapad 300-15ISK dmi.product.version: Lenovo ideapad 300-15ISK dmi.sys.vendor: LENOVO hciconfig: h
[Touch-packages] [Bug 1922338] Re: Intel 3165 [PCI 8086:3166] [USB 8087:0a2a] Bluetooth not working after reboot after upgrade to 21.04
And after restarting bluetooth.service it unblocks bluetooth: karol@toronto:~$ rfkill ID TYPE DEVICE SOFT HARD 0 wlan ideapad_wlan unblocked unblocked 1 bluetooth ideapad_bluetooth unblocked unblocked 2 wlan phy0 unblocked unblocked 4 bluetooth hci0 unblocked unblocked -- 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/1922338 Title: Intel 3165 [PCI 8086:3166] [USB 8087:0a2a] Bluetooth not working after reboot after upgrade to 21.04 Status in bluez package in Ubuntu: Incomplete Bug description: 1) Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 2) bluez: Installed: 5.56-0ubuntu3 Candidate: 5.56-0ubuntu3 Version table: *** 5.56-0ubuntu3 500 500 http://pl.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages 100 /var/lib/dpkg/status After every reboot bluetooth doesn't work. The GNOME bluetooth on/off switch can be changed but doesn't have any effect - no devices are shown. Output from systemctl after reboot: karol@toronto:~$ systemctl status bluetooth.service ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled) Active: active (running) since Fri 2021-04-02 11:26:31 CEST; 2min 6s ago Docs: man:bluetoothd(8) Main PID: 811 (bluetoothd) Status: "Running" Tasks: 1 (limit: 14115) Memory: 3.2M CGroup: /system.slice/bluetooth.service └─811 /usr/lib/bluetooth/bluetoothd Apr 02 11:26:24 toronto systemd[1]: Starting Bluetooth service... Apr 02 11:26:25 toronto bluetoothd[811]: Bluetooth daemon 5.56 Apr 02 11:26:31 toronto systemd[1]: Started Bluetooth service. Apr 02 11:26:31 toronto bluetoothd[811]: Starting SDP server Apr 02 11:26:32 toronto bluetoothd[811]: Bluetooth management interface 1.19 initialized Apr 02 11:26:37 toronto bluetoothd[811]: Failed to set mode: Blocked through rfkill (0x12) Apr 02 11:27:21 toronto bluetoothd[811]: Failed to set mode: Blocked through rfkill (0x12) Apr 02 11:27:48 toronto bluetoothd[811]: Endpoint registered: sender=:1.72 path=/MediaEndpoint/A2DPSink/sbc Apr 02 11:27:48 toronto bluetoothd[811]: Endpoint registered: sender=:1.72 path=/MediaEndpoint/A2DPSource/sbc Then after running `sudo systemctl restart bluetooth` everything seems to be fine: karol@toronto:~$ sudo systemctl restart bluetooth [sudo] password for karol: karol@toronto:~$ systemctl status bluetooth.service ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled) Active: active (running) since Fri 2021-04-02 11:30:13 CEST; 3s ago Docs: man:bluetoothd(8) Main PID: 3152 (bluetoothd) Status: "Running" Tasks: 1 (limit: 14115) Memory: 760.0K CGroup: /system.slice/bluetooth.service └─3152 /usr/lib/bluetooth/bluetoothd Apr 02 11:30:13 toronto systemd[1]: Starting Bluetooth service... Apr 02 11:30:13 toronto bluetoothd[3152]: Bluetooth daemon 5.56 Apr 02 11:30:13 toronto systemd[1]: Started Bluetooth service. Apr 02 11:30:13 toronto bluetoothd[3152]: Starting SDP server Apr 02 11:30:13 toronto bluetoothd[3152]: Bluetooth management interface 1.19 initialized Apr 02 11:30:15 toronto bluetoothd[3152]: Endpoint registered: sender=:1.72 path=/MediaEndpoint/A2DPSink/sbc Apr 02 11:30:15 toronto bluetoothd[3152]: Endpoint registered: sender=:1.72 path=/MediaEndpoint/A2DPSource/sbc karol@toronto:~$ ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Apr 2 11:31:48 2021 InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 80Q7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-13-generic root=UUID=9996d76c-d95e-4d4c-8902-0a583a091e93 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to hirsute on 2021-04-02 (0 days ago) dmi.bios.date: 12/16/2015 dmi.bios.release: 1.43 dmi.bios.vendor: LENOVO dmi.bios.version: D5CN43WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Paris 5A8 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 300-15ISK dmi.ec.firmware.release: 1.43 dmi.modalias: dmi:bvnLENOVO:bvrD5CN43WW:bd12/16/2015:br1.43:efr1.43:svnLENOVO:pn80Q7:pvrLenovoideapad300-15ISK:rvnLENOVO:rnParis5A8:rvrNODPK:cvnLENOVO:
[Touch-packages] [Bug 1922338] Re: Intel 3165 [PCI 8086:3166] [USB 8087:0a2a] Bluetooth not working after reboot after upgrade to 21.04
The output is: karol@toronto:~$ rfkill ID TYPE DEVICE SOFT HARD 0 wlan ideapad_wlan unblocked unblocked 1 bluetooth ideapad_bluetooth blocked unblocked 2 wlan phy0 unblocked unblocked 4 bluetooth hci0blocked unblocked -- 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/1922338 Title: Intel 3165 [PCI 8086:3166] [USB 8087:0a2a] Bluetooth not working after reboot after upgrade to 21.04 Status in bluez package in Ubuntu: Incomplete Bug description: 1) Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 2) bluez: Installed: 5.56-0ubuntu3 Candidate: 5.56-0ubuntu3 Version table: *** 5.56-0ubuntu3 500 500 http://pl.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages 100 /var/lib/dpkg/status After every reboot bluetooth doesn't work. The GNOME bluetooth on/off switch can be changed but doesn't have any effect - no devices are shown. Output from systemctl after reboot: karol@toronto:~$ systemctl status bluetooth.service ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled) Active: active (running) since Fri 2021-04-02 11:26:31 CEST; 2min 6s ago Docs: man:bluetoothd(8) Main PID: 811 (bluetoothd) Status: "Running" Tasks: 1 (limit: 14115) Memory: 3.2M CGroup: /system.slice/bluetooth.service └─811 /usr/lib/bluetooth/bluetoothd Apr 02 11:26:24 toronto systemd[1]: Starting Bluetooth service... Apr 02 11:26:25 toronto bluetoothd[811]: Bluetooth daemon 5.56 Apr 02 11:26:31 toronto systemd[1]: Started Bluetooth service. Apr 02 11:26:31 toronto bluetoothd[811]: Starting SDP server Apr 02 11:26:32 toronto bluetoothd[811]: Bluetooth management interface 1.19 initialized Apr 02 11:26:37 toronto bluetoothd[811]: Failed to set mode: Blocked through rfkill (0x12) Apr 02 11:27:21 toronto bluetoothd[811]: Failed to set mode: Blocked through rfkill (0x12) Apr 02 11:27:48 toronto bluetoothd[811]: Endpoint registered: sender=:1.72 path=/MediaEndpoint/A2DPSink/sbc Apr 02 11:27:48 toronto bluetoothd[811]: Endpoint registered: sender=:1.72 path=/MediaEndpoint/A2DPSource/sbc Then after running `sudo systemctl restart bluetooth` everything seems to be fine: karol@toronto:~$ sudo systemctl restart bluetooth [sudo] password for karol: karol@toronto:~$ systemctl status bluetooth.service ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled) Active: active (running) since Fri 2021-04-02 11:30:13 CEST; 3s ago Docs: man:bluetoothd(8) Main PID: 3152 (bluetoothd) Status: "Running" Tasks: 1 (limit: 14115) Memory: 760.0K CGroup: /system.slice/bluetooth.service └─3152 /usr/lib/bluetooth/bluetoothd Apr 02 11:30:13 toronto systemd[1]: Starting Bluetooth service... Apr 02 11:30:13 toronto bluetoothd[3152]: Bluetooth daemon 5.56 Apr 02 11:30:13 toronto systemd[1]: Started Bluetooth service. Apr 02 11:30:13 toronto bluetoothd[3152]: Starting SDP server Apr 02 11:30:13 toronto bluetoothd[3152]: Bluetooth management interface 1.19 initialized Apr 02 11:30:15 toronto bluetoothd[3152]: Endpoint registered: sender=:1.72 path=/MediaEndpoint/A2DPSink/sbc Apr 02 11:30:15 toronto bluetoothd[3152]: Endpoint registered: sender=:1.72 path=/MediaEndpoint/A2DPSource/sbc karol@toronto:~$ ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Apr 2 11:31:48 2021 InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 80Q7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-13-generic root=UUID=9996d76c-d95e-4d4c-8902-0a583a091e93 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to hirsute on 2021-04-02 (0 days ago) dmi.bios.date: 12/16/2015 dmi.bios.release: 1.43 dmi.bios.vendor: LENOVO dmi.bios.version: D5CN43WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Paris 5A8 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 300-15ISK dmi.ec.firmware.release: 1.43 dmi.modalias: dmi:bvnLENOVO:bvrD5CN43WW:bd12/16/2015:br1.43:efr1.43:svnLENOVO:pn80Q7:pvrLenovoideapad300-15ISK:rvnLENOVO:rnParis5A8:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad300-15ISK: dmi.product.family: ID
[Touch-packages] [Bug 1912940] Re: Bluetooth (ideapad_bluetooth) disabled every time on startup
We've been discussing rfkill on the duplicate bug (#1922338). The rfkill output from just after boot was: ID TYPE DEVICE SOFT HARD 0 wlan ideapad_wlan unblocked unblocked 1 bluetooth ideapad_bluetooth blocked unblocked 2 wlan phy0 unblocked unblocked 4 bluetooth hci0 blocked unblocked And we've come to the conclusion that the GUI does not run rfkill unblock, however I've checked today and after flicking the GUI switch it does indeed unblock the device: ID TYPE DEVICE SOFT HARD 0 wlan ideapad_wlan unblocked unblocked 1 bluetooth ideapad_bluetooth unblocked unblocked 2 wlan phy0 unblocked unblocked 4 bluetooth hci0 unblocked unblocked It still doesn't work of course. I can also manually run rfkill unblock 1 (and 3), but that doesn't work either. Bluetooth starts working only after unblocking and then restarting bluetooth.service -- 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/1912940 Title: Bluetooth (ideapad_bluetooth) disabled every time on startup Status in bluez package in Ubuntu: Confirmed Status in gnome-settings-daemon package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Bug description: [Policy] AutoEnable=true not working ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3 Uname: Linux 5.10.0-051000-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Sun Jan 24 19:49:49 2021 InstallationDate: Installed on 2021-01-24 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 4: Dev 2, If 0, Class=Wireless, Driver=btusb, 12M |__ Port 4: Dev 2, If 1, Class=Wireless, Driver=btusb, 12M MachineType: LENOVO 81CG ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-051000-generic root=UUID=0281b4fb-589a-46ed-b8ee-896d3505e7bd ro SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/10/2019 dmi.bios.release: 1.39 dmi.bios.vendor: LENOVO dmi.bios.version: 6NCN39WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40688 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 32 dmi.chassis.vendor: LENOVO dmi.chassis.version: MIIX 520-12IKB dmi.ec.firmware.release: 1.39 dmi.modalias: dmi:bvnLENOVO:bvr6NCN39WW:bd10/10/2019:br1.39:efr1.39:svnLENOVO:pn81CG:pvrMIIX520-12IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40688WIN:cvnLENOVO:ct32:cvrMIIX520-12IKB: dmi.product.family: MIIX 520-12IKB dmi.product.name: 81CG dmi.product.sku: LENOVO_MT_81CG_BU_idea_FM_MIIX 520-12IKB dmi.product.version: MIIX 520-12IKB dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: 3C:6A:A7:BB:B7:63 ACL MTU: 1021:5 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:213889 acl:13940 sco:0 events:310 errors:0 TX bytes:40352 acl:45 sco:0 commands:249 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1912940/+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 1912940] Re: Bluetooth (ideapad_bluetooth) disabled every time on startup
I've tested a few versions: 1) Working fine: 5.8.0-48 (official repo) 5.9.16 5.10.0 5.10.14 5.10.27 (last build of 5.10) 2) The issue first appears on 5.11.0-051100. I haven't tested release candidates. -- 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/1912940 Title: Bluetooth (ideapad_bluetooth) disabled every time on startup Status in bluez package in Ubuntu: Confirmed Status in gnome-settings-daemon package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Bug description: [Policy] AutoEnable=true not working ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3 Uname: Linux 5.10.0-051000-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Sun Jan 24 19:49:49 2021 InstallationDate: Installed on 2021-01-24 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 4: Dev 2, If 0, Class=Wireless, Driver=btusb, 12M |__ Port 4: Dev 2, If 1, Class=Wireless, Driver=btusb, 12M MachineType: LENOVO 81CG ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-051000-generic root=UUID=0281b4fb-589a-46ed-b8ee-896d3505e7bd ro SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/10/2019 dmi.bios.release: 1.39 dmi.bios.vendor: LENOVO dmi.bios.version: 6NCN39WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40688 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 32 dmi.chassis.vendor: LENOVO dmi.chassis.version: MIIX 520-12IKB dmi.ec.firmware.release: 1.39 dmi.modalias: dmi:bvnLENOVO:bvr6NCN39WW:bd10/10/2019:br1.39:efr1.39:svnLENOVO:pn81CG:pvrMIIX520-12IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40688WIN:cvnLENOVO:ct32:cvrMIIX520-12IKB: dmi.product.family: MIIX 520-12IKB dmi.product.name: 81CG dmi.product.sku: LENOVO_MT_81CG_BU_idea_FM_MIIX 520-12IKB dmi.product.version: MIIX 520-12IKB dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: 3C:6A:A7:BB:B7:63 ACL MTU: 1021:5 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:213889 acl:13940 sco:0 events:310 errors:0 TX bytes:40352 acl:45 sco:0 commands:249 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1912940/+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 1707420] [NEW] Cannot install package when sudo apt-get upgrade: package libgtk2.0-bin 2.24.30-1ubuntu1 [modified: usr/sbin/update-icon-caches] failed to install/upgrade: trying
Public bug reported: Cannot install package when sudo apt-get upgrade Preparing to unpack .../libgtk2.0-bin_2.24.30-1ubuntu1.16.04.1_amd64.deb ... Unpacking libgtk2.0-bin (2.24.30-1ubuntu1.16.04.1) over (2.24.30-1ubuntu1) ... dpkg: error processing archive /var/cache/apt/archives/libgtk2.0-bin_2.24.30-1ubuntu1.16.04.1_amd64.deb (--unpack): trying to overwrite '/usr/sbin/update-icon-caches', which is also in package libgtk-3-bin 3.18.9-1ubuntu3.1 Errors were encountered while processing: /var/cache/apt/archives/libgtk2.0-bin_2.24.30-1ubuntu1.16.04.1_amd64.deb /var/cache/apt/archives/libgtk-3-bin_3.18.9-1ubuntu3.3_amd64.deb ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libgtk2.0-bin 2.24.30-1ubuntu1 [modified: usr/sbin/update-icon-caches] ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70 Uname: Linux 4.4.0-83-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Sat Jul 29 18:41:59 2017 DuplicateSignature: package:libgtk2.0-bin:2.24.30-1ubuntu1 [modified: usr/sbin/update-icon-caches] Unpacking libgtk2.0-bin (2.24.30-1ubuntu1.16.04.1) over (2.24.30-1ubuntu1) ... dpkg: error processing archive /var/cache/apt/archives/libgtk2.0-bin_2.24.30-1ubuntu1.16.04.1_amd64.deb (--unpack): trying to overwrite '/usr/sbin/update-icon-caches', which is also in package libgtk-3-bin 3.18.9-1ubuntu3.1 ErrorMessage: trying to overwrite '/usr/sbin/update-icon-caches', which is also in package libgtk-3-bin 3.18.9-1ubuntu3.1 InstallationDate: Installed on 2015-08-20 (708 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: gtk+2.0 Title: package libgtk2.0-bin 2.24.30-1ubuntu1 [modified: usr/sbin/update-icon-caches] failed to install/upgrade: trying to overwrite '/usr/sbin/update-icon-caches', which is also in package libgtk-3-bin 3.18.9-1ubuntu3.1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gtk+2.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package package-conflict xenial ** Attachment added: "log.txt" https://bugs.launchpad.net/bugs/1707420/+attachment/4923856/+files/log.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1707420 Title: Cannot install package when sudo apt-get upgrade: package libgtk2.0-bin 2.24.30-1ubuntu1 [modified: usr/sbin/update-icon-caches] failed to install/upgrade: trying to overwrite '/usr/sbin/update-icon- caches', which is also in package libgtk-3-bin 3.18.9-1ubuntu3.1 Status in gtk+2.0 package in Ubuntu: New Bug description: Cannot install package when sudo apt-get upgrade Preparing to unpack .../libgtk2.0-bin_2.24.30-1ubuntu1.16.04.1_amd64.deb ... Unpacking libgtk2.0-bin (2.24.30-1ubuntu1.16.04.1) over (2.24.30-1ubuntu1) ... dpkg: error processing archive /var/cache/apt/archives/libgtk2.0-bin_2.24.30-1ubuntu1.16.04.1_amd64.deb (--unpack): trying to overwrite '/usr/sbin/update-icon-caches', which is also in package libgtk-3-bin 3.18.9-1ubuntu3.1 Errors were encountered while processing: /var/cache/apt/archives/libgtk2.0-bin_2.24.30-1ubuntu1.16.04.1_amd64.deb /var/cache/apt/archives/libgtk-3-bin_3.18.9-1ubuntu3.3_amd64.deb ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libgtk2.0-bin 2.24.30-1ubuntu1 [modified: usr/sbin/update-icon-caches] ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70 Uname: Linux 4.4.0-83-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Sat Jul 29 18:41:59 2017 DuplicateSignature: package:libgtk2.0-bin:2.24.30-1ubuntu1 [modified: usr/sbin/update-icon-caches] Unpacking libgtk2.0-bin (2.24.30-1ubuntu1.16.04.1) over (2.24.30-1ubuntu1) ... dpkg: error processing archive /var/cache/apt/archives/libgtk2.0-bin_2.24.30-1ubuntu1.16.04.1_amd64.deb (--unpack): trying to overwrite '/usr/sbin/update-icon-caches', which is also in package libgtk-3-bin 3.18.9-1ubuntu3.1 ErrorMessage: trying to overwrite '/usr/sbin/update-icon-caches', which is also in package libgtk-3-bin 3.18.9-1ubuntu3.1 InstallationDate: Installed on 2015-08-20 (708 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: gtk+2.0 Title: package libgtk2.0-bin 2.24.30-1ubuntu1 [modified: usr/sbin/update-icon-caches] failed to install/upgrade: trying to overwrite '/usr/sbin/update-icon-caches', which is also in package libgtk-3-bin 3.18.9-1ubuntu3.1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1707420/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpa
[Touch-packages] [Bug 1707420] Re: Cannot install package when sudo apt-get upgrade: package libgtk2.0-bin 2.24.30-1ubuntu1 [modified: usr/sbin/update-icon-caches] failed to install/upgrade: trying to
Everything seems to be fine after running the following command: sudo dpkg -i --force-overwrite var/cache/apt/archives/libgtk2.0-bin_2.24.30-1ubuntu1.16.04.1_amd64.deb -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1707420 Title: Cannot install package when sudo apt-get upgrade: package libgtk2.0-bin 2.24.30-1ubuntu1 [modified: usr/sbin/update-icon-caches] failed to install/upgrade: trying to overwrite '/usr/sbin/update-icon- caches', which is also in package libgtk-3-bin 3.18.9-1ubuntu3.1 Status in gtk+2.0 package in Ubuntu: New Bug description: Cannot install package when sudo apt-get upgrade Preparing to unpack .../libgtk2.0-bin_2.24.30-1ubuntu1.16.04.1_amd64.deb ... Unpacking libgtk2.0-bin (2.24.30-1ubuntu1.16.04.1) over (2.24.30-1ubuntu1) ... dpkg: error processing archive /var/cache/apt/archives/libgtk2.0-bin_2.24.30-1ubuntu1.16.04.1_amd64.deb (--unpack): trying to overwrite '/usr/sbin/update-icon-caches', which is also in package libgtk-3-bin 3.18.9-1ubuntu3.1 Errors were encountered while processing: /var/cache/apt/archives/libgtk2.0-bin_2.24.30-1ubuntu1.16.04.1_amd64.deb /var/cache/apt/archives/libgtk-3-bin_3.18.9-1ubuntu3.3_amd64.deb ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libgtk2.0-bin 2.24.30-1ubuntu1 [modified: usr/sbin/update-icon-caches] ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70 Uname: Linux 4.4.0-83-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Sat Jul 29 18:41:59 2017 DuplicateSignature: package:libgtk2.0-bin:2.24.30-1ubuntu1 [modified: usr/sbin/update-icon-caches] Unpacking libgtk2.0-bin (2.24.30-1ubuntu1.16.04.1) over (2.24.30-1ubuntu1) ... dpkg: error processing archive /var/cache/apt/archives/libgtk2.0-bin_2.24.30-1ubuntu1.16.04.1_amd64.deb (--unpack): trying to overwrite '/usr/sbin/update-icon-caches', which is also in package libgtk-3-bin 3.18.9-1ubuntu3.1 ErrorMessage: trying to overwrite '/usr/sbin/update-icon-caches', which is also in package libgtk-3-bin 3.18.9-1ubuntu3.1 InstallationDate: Installed on 2015-08-20 (708 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: gtk+2.0 Title: package libgtk2.0-bin 2.24.30-1ubuntu1 [modified: usr/sbin/update-icon-caches] failed to install/upgrade: trying to overwrite '/usr/sbin/update-icon-caches', which is also in package libgtk-3-bin 3.18.9-1ubuntu3.1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1707420/+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 1573396] [NEW] package shared-mime-info 1.3-1 failed to install/upgrade: dependency problems - leaving triggers unprocessed
Public bug reported: 1)Description: Ubuntu 16.04 LTS Release: 16.04 (actually I was upgrading from 15.10 to 16.04 when it appeared) 2)shared-mime-info: Installed: 1.5-2 Candidate: 1.5-2 Version table: *** 1.5-2 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status 3) My computer should update without any problems 4) The problem occured ProblemType: Package DistroRelease: Ubuntu 16.04 Package: shared-mime-info 1.3-1 ProcVersionSignature: Ubuntu 4.2.0-36.41-generic 4.2.8-ckt8 Uname: Linux 4.2.0-36-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 Date: Fri Apr 22 07:05:38 2016 DuplicateSignature: package:shared-mime-info:1.3-1:dependency problems - leaving triggers unprocessed ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2016-02-07 (74 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: shared-mime-info Title: package shared-mime-info 1.3-1 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to xenial on 2016-04-22 (0 days ago) ** Affects: shared-mime-info (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 shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1573396 Title: package shared-mime-info 1.3-1 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in shared-mime-info package in Ubuntu: New Bug description: 1)Description:Ubuntu 16.04 LTS Release: 16.04 (actually I was upgrading from 15.10 to 16.04 when it appeared) 2)shared-mime-info: Installed: 1.5-2 Candidate: 1.5-2 Version table: *** 1.5-2 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status 3) My computer should update without any problems 4) The problem occured ProblemType: Package DistroRelease: Ubuntu 16.04 Package: shared-mime-info 1.3-1 ProcVersionSignature: Ubuntu 4.2.0-36.41-generic 4.2.8-ckt8 Uname: Linux 4.2.0-36-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 Date: Fri Apr 22 07:05:38 2016 DuplicateSignature: package:shared-mime-info:1.3-1:dependency problems - leaving triggers unprocessed ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2016-02-07 (74 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: shared-mime-info Title: package shared-mime-info 1.3-1 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to xenial on 2016-04-22 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1573396/+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 1424625] [NEW] Cannot send SMS message when there is no network.
Public bug reported: I am unable to send a SMS message when there is no network (no coverage). I think that the System should save the message and automatically send the SMS when the telephone will find the coverage. It's very frustrating because to send a SMS in poorly coveraged area I have to wait a few minutes and try sending the message. Device: MAKO, OS build number: 15, Ubuntu Image part: 20150129, Device Image part: 20150116 ** Affects: messaging-app (Ubuntu) Importance: Undecided Status: New ** Tags: coverage message sending sms -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1424625 Title: Cannot send SMS message when there is no network. Status in messaging-app package in Ubuntu: New Bug description: I am unable to send a SMS message when there is no network (no coverage). I think that the System should save the message and automatically send the SMS when the telephone will find the coverage. It's very frustrating because to send a SMS in poorly coveraged area I have to wait a few minutes and try sending the message. Device: MAKO, OS build number: 15, Ubuntu Image part: 20150129, Device Image part: 20150116 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1424625/+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 1081022] Re: logging.SysLogHandler doesn't close UNIX socket when connection failed
As mentioned by Joe Breu, this bug has significant impact on stability of OpenStack services on Precise and the patch is absent on this release. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1081022 Title: logging.SysLogHandler doesn't close UNIX socket when connection failed Status in “python2.7” package in Ubuntu: Fix Released Status in “python2.7” source package in Precise: Fix Released Bug description: Python logging SysLogHandler to log into SysLog doesn't close UNIX-socket when connection failed. This bug is solved on the Python Issue Tracker at http://bugs.python.org/issue15179 and affects python package with version 2.7.3-0ubuntu2 at Ubuntu 12.04 LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1081022/+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 91389] Re: Please add support for more than one VPN simultaneously
In about one month this bug will be 8 years old. It's quite impressive :) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/91389 Title: Please add support for more than one VPN simultaneously Status in NetworkManager: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 affects /ubuntu/network-manager I often need to use more than one VPN at the same time (each using a different address range though). It'd be nice if network-manager would support that situation. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQCVAwUBRfQLkQy0JeEGD2blAQItkgP/SWjDb/mIMltNpsr6CyY7tQ290sszSPQV FSmEir+njA+Eq52nnoqwowAImJeiF2g3VAcHLcfsoaBjcPhqN8o4iT5LoAEtKLeA +UE+qoY0zerSkn8tCgJa1U/Zaa80lROpU3pLSCKfbFPisnzybCxjGzkmwLyKRQT/ KcJBSkHDeZY= =PKgd -END PGP SIGNATURE- To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/91389/+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 1615305] [NEW] Output when changing comment is weird and badly documented
Public bug reported: Changing a key comment within a private key might not be something you do on a daily basis, but it is mostly a frustrating task, since the documentation is incomplete and wrong. In particular the man page says: -c Requests changing the comment in the private and public key files. This operation is only supported for RSA1 keys and keys stored in the newer OpenSSH format. The program will prompt for the file containing the private keys, for the passphrase if the key has one, and for the new comment. So, one gets the impression that this is not applicable to newer keys. However bug #811125 dealt with this, and there was a commit (see [1]) that added support for basically all key types. In the case of RSA keys one has to use the new key format though (-o), which can only be find out with trial and error and is not documented at all. Furthermore the output of an actual ssh-keygen run is also confusing: [kbabioch@antares .ssh]$ ssh-keygen -c -C "new comment" -f id_rsa -o Enter passphrase: Key now has comment '(null)' The comment in your key file has been changed. The output tells me that the key is now empty (null). However the comment is correctly set, so while this works as intended, it is confusing to the user. [1] https://github.com/openssh/openssh- portable/commit/4d90625b229cf6b3551d81550a9861897509a65f#diff- 8a50ef3f3b9ea11be3c3b2fc1c0555b3 ** Affects: openssh (Ubuntu) Importance: Undecided Status: New ** Tags: change comment documentation ssh -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1615305 Title: Output when changing comment is weird and badly documented Status in openssh package in Ubuntu: New Bug description: Changing a key comment within a private key might not be something you do on a daily basis, but it is mostly a frustrating task, since the documentation is incomplete and wrong. In particular the man page says: -c Requests changing the comment in the private and public key files. This operation is only supported for RSA1 keys and keys stored in the newer OpenSSH format. The program will prompt for the file containing the private keys, for the passphrase if the key has one, and for the new comment. So, one gets the impression that this is not applicable to newer keys. However bug #811125 dealt with this, and there was a commit (see [1]) that added support for basically all key types. In the case of RSA keys one has to use the new key format though (-o), which can only be find out with trial and error and is not documented at all. Furthermore the output of an actual ssh-keygen run is also confusing: [kbabioch@antares .ssh]$ ssh-keygen -c -C "new comment" -f id_rsa -o Enter passphrase: Key now has comment '(null)' The comment in your key file has been changed. The output tells me that the key is now empty (null). However the comment is correctly set, so while this works as intended, it is confusing to the user. [1] https://github.com/openssh/openssh- portable/commit/4d90625b229cf6b3551d81550a9861897509a65f#diff- 8a50ef3f3b9ea11be3c3b2fc1c0555b3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1615305/+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
