[Touch-packages] [Bug 1926084] Re: [hirsute] Bluetooth speakers reconnect randomly
Issue occurs in impish as well. -- 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/1926084 Title: [hirsute] Bluetooth speakers reconnect randomly Status in bluez package in Ubuntu: Confirmed Bug description: Bluetooth speakers reconnect randomly. The onlt workaround that seems to work is to remove speakers from paired devies, restart buetooth service and connect them once again. Once these stepss are performed connection become stable until reboot or hibernation. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: bluez 5.56-0ubuntu4 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Sun Apr 25 17:22:11 2021 InstallationDate: Installed on 2021-04-13 (12 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 174f:1800 Syntek Integrated RGB Camera Bus 001 Device 003: ID 8087:0029 Intel Corp. AX200 Bluetooth Bus 001 Device 002: ID 17ef:60a9 Lenovo Lenovo Essential Wireless Keyboard and Mouse Combo Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO F0FA0066UA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=9ef69356-31e9-488f-9a6b-99e10c0ed863 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to hirsute on 2021-04-18 (6 days ago) dmi.bios.date: 03/31/2021 dmi.bios.release: 1.32 dmi.bios.vendor: LENOVO dmi.bios.version: O4VKT32A dmi.board.asset.tag: INVALID dmi.board.name: 371F dmi.board.vendor: LENOVO dmi.board.version: SDK0J40688 WIN 3424143288435 dmi.chassis.type: 13 dmi.chassis.vendor: LENOVO dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrO4VKT32A:bd03/31/2021:br1.32:efr1.13:svnLENOVO:pnF0FA0066UA:pvrIdeaCentreAIO527IMB05:rvnLENOVO:rn371F:rvrSDK0J40688WIN3424143288435:cvnLENOVO:ct13:cvr0.1: dmi.product.family: IdeaCentre AIO 5 27IMB05 dmi.product.name: F0FA0066UA dmi.product.sku: LENOVO_MT_F0FA_BU_Lenovo_FM_IdeaCentre AIO 5 27IMB05 dmi.product.version: IdeaCentre AIO 5 27IMB05 dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: 44:AF:28:F7:A9:6C ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:2239397 acl:225 sco:0 events:318945 errors:0 TX bytes:207283666 acl:315238 sco:0 commands:3564 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1926084/+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 1926084] [NEW] Bluetooth speakers reconnect randomly
Public bug reported: Bluetooth speakers reconnect randomly. The onlt workaround that seems to work is to remove speakers from paired devies, restart buetooth service and connect them once again. Once these stepss are performed connection become stable until reboot or hibernation. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: bluez 5.56-0ubuntu4 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Sun Apr 25 17:22:11 2021 InstallationDate: Installed on 2021-04-13 (12 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 174f:1800 Syntek Integrated RGB Camera Bus 001 Device 003: ID 8087:0029 Intel Corp. AX200 Bluetooth Bus 001 Device 002: ID 17ef:60a9 Lenovo Lenovo Essential Wireless Keyboard and Mouse Combo Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO F0FA0066UA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=9ef69356-31e9-488f-9a6b-99e10c0ed863 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to hirsute on 2021-04-18 (6 days ago) dmi.bios.date: 03/31/2021 dmi.bios.release: 1.32 dmi.bios.vendor: LENOVO dmi.bios.version: O4VKT32A dmi.board.asset.tag: INVALID dmi.board.name: 371F dmi.board.vendor: LENOVO dmi.board.version: SDK0J40688 WIN 3424143288435 dmi.chassis.type: 13 dmi.chassis.vendor: LENOVO dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrO4VKT32A:bd03/31/2021:br1.32:efr1.13:svnLENOVO:pnF0FA0066UA:pvrIdeaCentreAIO527IMB05:rvnLENOVO:rn371F:rvrSDK0J40688WIN3424143288435:cvnLENOVO:ct13:cvr0.1: dmi.product.family: IdeaCentre AIO 5 27IMB05 dmi.product.name: F0FA0066UA dmi.product.sku: LENOVO_MT_F0FA_BU_Lenovo_FM_IdeaCentre AIO 5 27IMB05 dmi.product.version: IdeaCentre AIO 5 27IMB05 dmi.sys.vendor: LENOVO hciconfig: hci0: Type: Primary Bus: USB BD Address: 44:AF:28:F7:A9:6C ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:2239397 acl:225 sco:0 events:318945 errors:0 TX bytes:207283666 acl:315238 sco:0 commands:3564 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute -- 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/1926084 Title: Bluetooth speakers reconnect randomly Status in bluez package in Ubuntu: New Bug description: Bluetooth speakers reconnect randomly. The onlt workaround that seems to work is to remove speakers from paired devies, restart buetooth service and connect them once again. Once these stepss are performed connection become stable until reboot or hibernation. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: bluez 5.56-0ubuntu4 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Sun Apr 25 17:22:11 2021 InstallationDate: Installed on 2021-04-13 (12 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 174f:1800 Syntek Integrated RGB Camera Bus 001 Device 003: ID 8087:0029 Intel Corp. AX200 Bluetooth Bus 001 Device 002: ID 17ef:60a9 Lenovo Lenovo Essential Wireless Keyboard and Mouse Combo Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO F0FA0066UA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=9ef69356-31e9-488f-9a6b-99e10c0ed863 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to hirsute on 2021-04-18 (6 days ago) dmi.bios.date: 03/31/2021 dmi.bios.release: 1.32 dmi.bios.vendor: LENOVO dmi.bios.version: O4VKT32A dmi.board.asset.tag: INVALID dmi.board.name: 371F dmi.board.vendor: LENOVO dmi.board.version: SDK0J40688 WIN 3424143288435 dmi.chassis.type: 13 dmi.chassis.vendor: LENOVO dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrO4VKT32A:bd03/31/2021:br1.32:efr1.13:svnLENOVO:pnF0FA0066UA:pvrIdeaCentreAIO527IMB05:rvnLENOVO:rn371F:rvrSDK0J40688WIN3424143288435:cvnLENOVO:ct13:cvr0.1: dmi.product.family: IdeaCentre AIO 5 27IMB05 dmi.product.name: F0FA0066UA dmi.product.sku: LENOVO_MT_F0FA_BU_Lenovo_FM_IdeaCentre AIO 5 27IMB05 dmi.product.version: IdeaCentre AIO 5
[Touch-packages] [Bug 1681062] Re: Bluetooth doesn't work after update to 17.04
Some additional info: Bluetooth stop wokring after hibernation, but not always. Only way to get it work again is to completly power off computer and turn it on, reboot doesn't help. -- 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/1681062 Title: Bluetooth doesn't work after update to 17.04 Status in bluez package in Ubuntu: New Bug description: After update to 17.04 bluetooth stopped to work. some logs that could be useful: asudak@asudak-Inspiron-One-2330:~$ hciconfig hci0: Type: Primary Bus: USB BD Address: 80:56:F2:09:92:30 ACL MTU: 1022:8 SCO MTU: 183:5 DOWN RX bytes:580 acl:0 sco:0 events:31 errors:0 TX bytes:371 acl:0 sco:0 commands:38 errors:7 asudak@asudak-Inspiron-One-2330:~$ sudo hciconfig hci0 up Can't init device hci0: Connection timed out (110) ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu3 Architecture: amd64 Date: Sat Apr 8 13:04:36 2017 InstallationDate: Installed on 2013-12-27 (1197 days ago) InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release amd64 (20131017) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. Inspiron One 2330 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic root=UUID=13b39ae0-892a-4b5a-ab81-62dba9463c1a ro quiet splash radeon.dpm=1 radeon.runpm=0 vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to zesty on 2017-02-25 (41 days ago) dmi.bios.date: 05/13/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A13 dmi.board.name: 09JR1D dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 13 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 27147636_1 dmi.modalias: dmi:bvnDellInc.:bvrA13:bd05/13/2013:svnDellInc.:pnInspironOne2330:pvr00:rvnDellInc.:rn09JR1D:rvrA00:cvnDellInc.:ct13:cvr27147636_1: dmi.product.name: Inspiron One 2330 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: 80:56:F2:09:92:30 ACL MTU: 1022:8 SCO MTU: 183:5 DOWN RX bytes:580 acl:0 sco:0 events:31 errors:0 TX bytes:371 acl:0 sco:0 commands:40 errors:9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1681062/+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 1681062] [NEW] Bluetooth doesn't work after update to 17.04
Public bug reported: After update to 17.04 bluetooth stopped to work. some logs that could be useful: asudak@asudak-Inspiron-One-2330:~$ hciconfig hci0: Type: Primary Bus: USB BD Address: 80:56:F2:09:92:30 ACL MTU: 1022:8 SCO MTU: 183:5 DOWN RX bytes:580 acl:0 sco:0 events:31 errors:0 TX bytes:371 acl:0 sco:0 commands:38 errors:7 asudak@asudak-Inspiron-One-2330:~$ sudo hciconfig hci0 up Can't init device hci0: Connection timed out (110) ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu3 Architecture: amd64 Date: Sat Apr 8 13:04:36 2017 InstallationDate: Installed on 2013-12-27 (1197 days ago) InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release amd64 (20131017) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. Inspiron One 2330 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic root=UUID=13b39ae0-892a-4b5a-ab81-62dba9463c1a ro quiet splash radeon.dpm=1 radeon.runpm=0 vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to zesty on 2017-02-25 (41 days ago) dmi.bios.date: 05/13/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A13 dmi.board.name: 09JR1D dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 13 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 27147636_1 dmi.modalias: dmi:bvnDellInc.:bvrA13:bd05/13/2013:svnDellInc.:pnInspironOne2330:pvr00:rvnDellInc.:rn09JR1D:rvrA00:cvnDellInc.:ct13:cvr27147636_1: dmi.product.name: Inspiron One 2330 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. hciconfig: hci0: Type: Primary Bus: USB BD Address: 80:56:F2:09:92:30 ACL MTU: 1022:8 SCO MTU: 183:5 DOWN RX bytes:580 acl:0 sco:0 events:31 errors:0 TX bytes:371 acl:0 sco:0 commands:40 errors:9 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug zesty -- 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/1681062 Title: Bluetooth doesn't work after update to 17.04 Status in bluez package in Ubuntu: New Bug description: After update to 17.04 bluetooth stopped to work. some logs that could be useful: asudak@asudak-Inspiron-One-2330:~$ hciconfig hci0: Type: Primary Bus: USB BD Address: 80:56:F2:09:92:30 ACL MTU: 1022:8 SCO MTU: 183:5 DOWN RX bytes:580 acl:0 sco:0 events:31 errors:0 TX bytes:371 acl:0 sco:0 commands:38 errors:7 asudak@asudak-Inspiron-One-2330:~$ sudo hciconfig hci0 up Can't init device hci0: Connection timed out (110) ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu3 Architecture: amd64 Date: Sat Apr 8 13:04:36 2017 InstallationDate: Installed on 2013-12-27 (1197 days ago) InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release amd64 (20131017) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. Inspiron One 2330 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic root=UUID=13b39ae0-892a-4b5a-ab81-62dba9463c1a ro quiet splash radeon.dpm=1 radeon.runpm=0 vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to zesty on 2017-02-25 (41 days ago) dmi.bios.date: 05/13/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A13 dmi.board.name: 09JR1D dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 13 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 27147636_1 dmi.modalias: dmi:bvnDellInc.:bvrA13:bd05/13/2013:svnDellInc.:pnInspironOne2330:pvr00:rvnDellInc.:rn09JR1D:rvrA00:cvnDellInc.:ct13:cvr27147636_1: dmi.product.name: Inspiron One 2330 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: 80:56:F2:09:92:30 ACL MTU: 1022:8 SCO MTU: 183:5 DOWN RX bytes:580 acl:0 sco:0 events:31 errors:0 TX bytes:371 acl:0 sco:0 commands:40 errors:9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1681062/+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 1559805] Re: suspend not working with latest xenial and kernel 4.4.0
Confirming that new kernel fix this issue. Tested on 4.6-rc3 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1559805 Title: suspend not working with latest xenial and kernel 4.4.0 Status in xorg package in Ubuntu: Confirmed Bug description: suspend stops but never finishes and needs a reboot ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 Uname: Linux 4.4.0-15-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: KDE Date: Sun Mar 20 22:45:50 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2015-10-04 (168 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924) ProcEnviron: LANGUAGE= TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= SHELL=/bin/bash SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to xenial on 2016-03-17 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1559805/+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 1559805] Re: suspend not working with latest xenial and kernel 4.4.0
I have same bug. After closing lid system going to suspend but never woke up. here is suspend log Апр 16 21:08:50 LissAmour systemd-logind[648]: Lid closed. Апр 16 21:08:50 LissAmour systemd-logind[648]: Suspending... Апр 16 21:08:50 LissAmour NetworkManager[658]: [1460830130.2340] manager: sleep requested (sleeping: no enabled: yes) Апр 16 21:08:50 LissAmour NetworkManager[658]: [1460830130.2340] manager: sleeping... Апр 16 21:08:50 LissAmour NetworkManager[658]: [1460830130.2341] device (wlan0): state change: activated -> unmanaged (reason 'sleeping') [100 Апр 16 21:08:50 LissAmour /usr/lib/gdm3/gdm-x-session[1643]: gnome-session-binary[1653]: DEBUG(+): GsmSystemd: received logind signal: PrepareForSleep Апр 16 21:08:50 LissAmour /usr/lib/gdm3/gdm-x-session[1643]: gnome-session-binary[1653]: DEBUG(+): GsmSystemd: ignoring PrepareForSleep signal Апр 16 21:08:50 LissAmour gnome-session-binary[1653]: DEBUG(+): GsmSystemd: received logind signal: PrepareForSleep Апр 16 21:08:50 LissAmour gnome-session-binary[1653]: DEBUG(+): GsmSystemd: ignoring PrepareForSleep signal Апр 16 21:08:50 LissAmour NetworkManager[658]: [1460830130.2519] dhcp4 (wlan0): canceled DHCP transaction, DHCP client pid 1003 Апр 16 21:08:50 LissAmour avahi-daemon[1150]: Withdrawing address record for 192.168.0.104 on wlan0. Апр 16 21:08:50 LissAmour NetworkManager[658]: [1460830130.2520] dhcp4 (wlan0): state changed bound -> done Апр 16 21:08:50 LissAmour avahi-daemon[1150]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.0.104. Апр 16 21:08:50 LissAmour avahi-daemon[1150]: Interface wlan0.IPv4 no longer relevant for mDNS. Апр 16 21:08:50 LissAmour avahi-daemon[1150]: Withdrawing address record for fe80::9ead:97ff:fe36:bf45 on wlan0. Апр 16 21:08:50 LissAmour avahi-daemon[1150]: Leaving mDNS multicast group on interface wlan0.IPv6 with address fe80::9ead:97ff:fe36:bf45. Апр 16 21:08:50 LissAmour avahi-daemon[1150]: Interface wlan0.IPv6 no longer relevant for mDNS. Апр 16 21:08:50 LissAmour kernel: wlan0: deauthenticating from c0:4a:00:56:d8:56 by local choice (Reason: 3=DEAUTH_LEAVING) Апр 16 21:08:50 LissAmour NetworkManager[658]: [1460830130.2596] dns-mgr: Writing DNS information to /sbin/resolvconf Апр 16 21:08:50 LissAmour dnsmasq[1014]: setting upstream servers from DBus Апр 16 21:08:50 LissAmour wpa_supplicant[935]: wlan0: CTRL-EVENT-DISCONNECTED bssid=c0:4a:00:56:d8:56 reason=3 locally_generated=1 Апр 16 21:08:50 LissAmour whoopsie[653]: [21:08:50] Cannot reach: https://daisy.ubuntu.com Апр 16 21:08:50 LissAmour whoopsie[653]: [21:08:50] offline Апр 16 21:08:50 LissAmour NetworkManager[658]: [1460830130.2906] manager: NetworkManager state is now ASLEEP Апр 16 21:08:50 LissAmour whoopsie[653]: [21:08:50] Cannot reach: https://daisy.ubuntu.com Апр 16 21:08:50 LissAmour kernel: cfg80211: World regulatory domain updated: Апр 16 21:08:50 LissAmour kernel: cfg80211: DFS Master region: unset Апр 16 21:08:50 LissAmour kernel: cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time) Апр 16 21:08:50 LissAmour kernel: cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A) Апр 16 21:08:50 LissAmour kernel: cfg80211: (2457000 KHz - 2482000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A) Апр 16 21:08:50 LissAmour kernel: cfg80211: (2474000 KHz - 2494000 KHz @ 2 KHz), (N/A, 2000 mBm), (N/A) Апр 16 21:08:50 LissAmour kernel: cfg80211: (517 KHz - 525 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (N/A) Апр 16 21:08:50 LissAmour kernel: cfg80211: (525 KHz - 533 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (0 s) Апр 16 21:08:50 LissAmour kernel: cfg80211: (549 KHz - 573 KHz @ 16 KHz), (N/A, 2000 mBm), (0 s) Апр 16 21:08:50 LissAmour kernel: cfg80211: (5735000 KHz - 5835000 KHz @ 8 KHz), (N/A, 2000 mBm), (N/A) Апр 16 21:08:50 LissAmour kernel: cfg80211: (5724 KHz - 6372 KHz @ 216 KHz), (N/A, 0 mBm), (N/A) Апр 16 21:08:50 LissAmour kernel: cfg80211: Regulatory domain changed to country: UA Апр 16 21:08:50 LissAmour kernel: cfg80211: DFS Master region: ETSI Апр 16 21:08:50 LissAmour kernel: cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time) Апр 16 21:08:50 LissAmour kernel: cfg80211: (240 KHz - 2483500 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A) Апр 16 21:08:50 LissAmour kernel: cfg80211: (515 KHz - 535 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A) Апр 16 21:08:50 LissAmour kernel: cfg80211: (549 KHz - 567 KHz @ 8 KHz), (N/A, 2000 mBm), (0 s) Апр 16 21:08:50 LissAmour kernel: cfg80211: (5735000 KHz - 5835000 KHz @ 8 KHz), (N/A, 2000 mBm), (N/A) Апр 16 21:08:50 LissAmour kernel: cfg80211: (5700 KHz - 6600 KHz @ 216 KHz), (N/A, 4000 mBm), (N/A) Апр 16 21:08:50 LissAmour NetworkManager[658]: [1460830130.5255] device (44:D4:E0:B7:73:D4): state change: disconnected ->
[Touch-packages] [Bug 1543556] Re: Xorg crash while using netbeans
I'm unable to reproduce crash with latest updates, so I guess that issue was fixed. ** Changed in: xorg (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1543556 Title: Xorg crash while using netbeans Status in xorg package in Ubuntu: Fix Released Bug description: xorg randomly crashes while I using NetBeans 8.1. Crash reproducable with oracle and openjdk version 7 and 8. backtrace I got after another crash Program received signal SIGABRT, Aborted. 0x7f5412e73227 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:55 #0 0x7f5412e73227 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:55 #1 0x7f5412e74e8a in __GI_abort () at abort.c:89 #2 0x7f5412eb6bb3 in __libc_message (do_abort=do_abort@entry=1, fmt=fmt@entry=0x7f5412fcf128 "*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:175 #3 0x7f5412ebebc9 in malloc_printerr (ptr=, str=0x7f5412fcf1c8 "free(): corrupted unsorted chunks", action=1) at malloc.c:4965 #4 _int_free (av=, p=, have_lock=0) at malloc.c:3834 #5 0x7f5412ec27fc in __GI___libc_free (mem=) at malloc.c:2950 #6 0x55a20f705500 in present_event_notify () #7 0x7f540f11ec05 in present_flip_handler (event=, data=0x55a21054b7f0) at ../../../src/sna/sna_present.c:552 #8 0x7f540f08a2b0 in sna_mode_wakeup (sna=, sna@entry=0x7f5415041000) at ../../../src/sna/sna_display.c:9014 #9 0x7f540f08df80 in sna_wakeup_handler (arg=, result=1, read_mask=0x55a20fa244e0) at ../../../src/sna/sna_driver.c:733 #10 0x55a20f6286fa in WakeupHandler () #11 0x55a20f77e1df in WaitForSomething () #12 0x55a20f623811 in ?? () #13 0x55a20f627b9b in ?? () #14 0x7f5412e5ea00 in __libc_start_main (main=0x55a20f611f00, argc=14, argv=0x7fff2d756f58, init=, fini=, rtld_fini=, stack_end=0x7fff2d756f48) at libc-start.c:289 #15 0x55a20f611f39 in _start () ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0 Uname: Linux 4.4.0-2-generic x86_64 ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Feb 9 13:58:56 2016 InstallationDate: Installed on 2013-12-27 (773 days ago) InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release amd64 (20131017) SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to xenial on 2016-01-30 (9 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1543556/+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 1543556] [NEW] Xorg crash while using netbeans
Public bug reported: xorg randomly crashes while I using NetBeans 8.1. Crash reproducable with oracle and openjdk version 7 and 8. backtrace I got after another crash Program received signal SIGABRT, Aborted. 0x7f5412e73227 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:55 #0 0x7f5412e73227 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:55 #1 0x7f5412e74e8a in __GI_abort () at abort.c:89 #2 0x7f5412eb6bb3 in __libc_message (do_abort=do_abort@entry=1, fmt=fmt@entry=0x7f5412fcf128 "*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:175 #3 0x7f5412ebebc9 in malloc_printerr (ptr=, str=0x7f5412fcf1c8 "free(): corrupted unsorted chunks", action=1) at malloc.c:4965 #4 _int_free (av=, p=, have_lock=0) at malloc.c:3834 #5 0x7f5412ec27fc in __GI___libc_free (mem=) at malloc.c:2950 #6 0x55a20f705500 in present_event_notify () #7 0x7f540f11ec05 in present_flip_handler (event=, data=0x55a21054b7f0) at ../../../src/sna/sna_present.c:552 #8 0x7f540f08a2b0 in sna_mode_wakeup (sna=, sna@entry=0x7f5415041000) at ../../../src/sna/sna_display.c:9014 #9 0x7f540f08df80 in sna_wakeup_handler (arg=, result=1, read_mask=0x55a20fa244e0) at ../../../src/sna/sna_driver.c:733 #10 0x55a20f6286fa in WakeupHandler () #11 0x55a20f77e1df in WaitForSomething () #12 0x55a20f623811 in ?? () #13 0x55a20f627b9b in ?? () #14 0x7f5412e5ea00 in __libc_start_main (main=0x55a20f611f00, argc=14, argv=0x7fff2d756f58, init=, fini=, rtld_fini=, stack_end=0x7fff2d756f48) at libc-start.c:289 #15 0x55a20f611f39 in _start () ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0 Uname: Linux 4.4.0-2-generic x86_64 ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Feb 9 13:58:56 2016 InstallationDate: Installed on 2013-12-27 (773 days ago) InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release amd64 (20131017) SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to xenial on 2016-01-30 (9 days ago) ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug crash xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1543556 Title: Xorg crash while using netbeans Status in xorg package in Ubuntu: New Bug description: xorg randomly crashes while I using NetBeans 8.1. Crash reproducable with oracle and openjdk version 7 and 8. backtrace I got after another crash Program received signal SIGABRT, Aborted. 0x7f5412e73227 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:55 #0 0x7f5412e73227 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:55 #1 0x7f5412e74e8a in __GI_abort () at abort.c:89 #2 0x7f5412eb6bb3 in __libc_message (do_abort=do_abort@entry=1, fmt=fmt@entry=0x7f5412fcf128 "*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:175 #3 0x7f5412ebebc9 in malloc_printerr (ptr=, str=0x7f5412fcf1c8 "free(): corrupted unsorted chunks", action=1) at malloc.c:4965 #4 _int_free (av=, p=, have_lock=0) at malloc.c:3834 #5 0x7f5412ec27fc in __GI___libc_free (mem=) at malloc.c:2950 #6 0x55a20f705500 in present_event_notify () #7 0x7f540f11ec05 in present_flip_handler (event=, data=0x55a21054b7f0) at ../../../src/sna/sna_present.c:552 #8 0x7f540f08a2b0 in sna_mode_wakeup (sna=, sna@entry=0x7f5415041000) at ../../../src/sna/sna_display.c:9014 #9 0x7f540f08df80 in sna_wakeup_handler (arg=, result=1, read_mask=0x55a20fa244e0) at ../../../src/sna/sna_driver.c:733 #10 0x55a20f6286fa in WakeupHandler () #11 0x55a20f77e1df in WaitForSomething () #12 0x55a20f623811 in ?? () #13 0x55a20f627b9b in ?? () #14 0x7f5412e5ea00 in __libc_start_main (main=0x55a20f611f00, argc=14, argv=0x7fff2d756f58, init=, fini=, rtld_fini=, stack_end=0x7fff2d756f48) at libc-start.c:289 #15 0x55a20f611f39 in _start () ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0 Uname: Linux 4.4.0-2-generic x86_64 ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Feb 9 13:58:56 2016 InstallationDate: Installed on 2013-12-27 (773 days ago) InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release amd64 (20131017) SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to xenial on 2016-01-30 (9 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1543556/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages
[Touch-packages] [Bug 1542747] [NEW] Empathy stop working with accounts setup with GOA after last telepathy update
Public bug reported: I have google account setup with gnome online accounts. After updating telepathy-mission control from 1:5.16.3-1ubuntu4 to 1:5.16.3-1ubuntu5 empathy stopped recognizing this account. Another account (icq) that was setup directly in empathy works fine. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: telepathy-mission-control-5 1:5.16.3-1ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0 Uname: Linux 4.4.0-2-generic x86_64 ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Feb 7 02:22:11 2016 InstallationDate: Installed on 2013-12-27 (771 days ago) InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release amd64 (20131017) SourcePackage: telepathy-mission-control-5 UpgradeStatus: Upgraded to xenial on 2016-01-30 (7 days ago) ** Affects: telepathy-mission-control-5 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telepathy-mission- control-5 in Ubuntu. https://bugs.launchpad.net/bugs/1542747 Title: Empathy stop working with accounts setup with GOA after last telepathy update Status in telepathy-mission-control-5 package in Ubuntu: New Bug description: I have google account setup with gnome online accounts. After updating telepathy-mission control from 1:5.16.3-1ubuntu4 to 1:5.16.3-1ubuntu5 empathy stopped recognizing this account. Another account (icq) that was setup directly in empathy works fine. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: telepathy-mission-control-5 1:5.16.3-1ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0 Uname: Linux 4.4.0-2-generic x86_64 ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Feb 7 02:22:11 2016 InstallationDate: Installed on 2013-12-27 (771 days ago) InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release amd64 (20131017) SourcePackage: telepathy-mission-control-5 UpgradeStatus: Upgraded to xenial on 2016-01-30 (7 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telepathy-mission-control-5/+bug/1542747/+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
