[Touch-packages] [Bug 1413363] Re: bluetooth speaker and suspension issue
Reduced priority for Ubuntu Touch bugs. ** Changed in: bluez (Ubuntu) Importance: High => Medium -- 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/1413363 Title: bluetooth speaker and suspension issue Status in bluez package in Ubuntu: Incomplete Bug description: STEPS: 1. Open settings bluetooth 2. Turn on your blue tooth speaker 3. Pair the speaker 4. Open the music app 5. Play music 6. Pause the music 7. Let the phone suspend 8. After a while it goes into deep sleep and the speaker disconnects 9. Wake the phone press the play button EXPECTED: I expected the music to play out of the bluetooth speaker ACTUAL: A long pause, then a click then the music plays from the internal speaker. You can no longer get the music to play from the bluetooth speaker. Things I've tried: Reboot the phone re connect to the bt speaker music still plays from the loud speaker on the phone. Turned off the speaker, restarted it still plays through the Loud speaker on the phone WORK AROUND: Forget the connection. Re pair the device now press play now it works as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1413363/+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 1514166] Re: bluetoothd crashed with SIGSEGV in rawmemchr() from _IO_str_init_static_internal from _IO_vsscanf from __sscanf from get_supported_device [plugins/sixaxis.c]
** Summary changed: - bluetoothd crashed with SIGSEGV in rawmemchr() + bluetoothd crashed with SIGSEGV in rawmemchr() from _IO_str_init_static_internal from _IO_vsscanf from __sscanf from get_supported_device [plugins/sixaxis.c] -- 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/1514166 Title: bluetoothd crashed with SIGSEGV in rawmemchr() from _IO_str_init_static_internal from _IO_vsscanf from __sscanf from get_supported_device [plugins/sixaxis.c] Status in bluez package in Ubuntu: Confirmed Bug description: bluetoothd crashed with SIGSEGV in rawmemchr() https://errors.ubuntu.com/problem/f0eca11dfcb228bd89caa34e5f9b5529151c0c88 ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: bluez 5.35-0ubuntu2 ProcVersionSignature: Ubuntu 4.2.0-17.21-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 NonfreeKernelModules: openafs ApportVersion: 2.19.2-0ubuntu4 Architecture: amd64 Date: Sat Nov 7 17:15:18 2015 ExecutablePath: /usr/lib/bluetooth/bluetoothd InstallationDate: Installed on 2015-06-02 (158 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20349 ProcCmdline: /usr/lib/bluetooth/bluetoothd ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-17-generic.efi.signed root=/dev/mapper/btree-ubuntu ro rootflags=subvol=@ noprompt quiet splash vt.handoff=7 SegvAnalysis: Segfault happened at: 0x7fef0124a51f : movdqu (%rdi),%xmm0 PC (0x7fef0124a51f) ok source "(%rdi)" (0x) not located in a known VMA region (needed readable region)! destination "%xmm0" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: bluez StacktraceTop: rawmemchr () at ../sysdeps/x86_64/rawmemchr.S:37 _IO_str_init_static_internal (sf=sf@entry=0x7fffafd6df50, ptr=ptr@entry=0x0, size=size@entry=0, pstart=pstart@entry=0x0) at strops.c:44 _IO_vsscanf (string=0x0, format=0x7fef0062eacc "%hx:%hx:%hx", args=args@entry=0x7fffafd6e078) at iovsscanf.c:43 __sscanf (s=, format=) at sscanf.c:32 ?? () from /usr/lib/x86_64-linux-gnu/bluetooth/plugins/sixaxis.so Title: bluetoothd crashed with SIGSEGV in rawmemchr() UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: Upgraded to xenial on 2015-10-28 (11 days ago) UserGroups: dmi.bios.date: 07/22/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN40WW(V3.00) dmi.board.asset.tag: 31900058Std dmi.board.name: Lenovo Y50-70 Touch dmi.board.vendor: LENOVO dmi.board.version: 31900058Std dmi.chassis.asset.tag: 31900058Std dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 Touch dmi.modalias: dmi:bvnLENOVO:bvr9ECN40WW(V3.00):bd07/22/2015:svnLENOVO:pn20349:pvrLenovoY50-70Touch:rvnLENOVO:rnLenovoY50-70Touch:rvr31900058Std:cvnLENOVO:ct10:cvrLenovoY50-70Touch: dmi.product.name: 20349 dmi.product.version: Lenovo Y50-70 Touch dmi.sys.vendor: LENOVO hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: 28:B2:BD:0B:11:97 ACL MTU: 1021:5 SCO MTU: 96:5 UP RUNNING RX bytes:691 acl:0 sco:0 events:47 errors:0 TX bytes:2182 acl:0 sco:0 commands:47 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1514166/+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 1413363] Re: bluetooth speaker and suspension issue
** Tags added: bluez-touch -- 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/1413363 Title: bluetooth speaker and suspension issue Status in bluez package in Ubuntu: Incomplete Bug description: STEPS: 1. Open settings bluetooth 2. Turn on your blue tooth speaker 3. Pair the speaker 4. Open the music app 5. Play music 6. Pause the music 7. Let the phone suspend 8. After a while it goes into deep sleep and the speaker disconnects 9. Wake the phone press the play button EXPECTED: I expected the music to play out of the bluetooth speaker ACTUAL: A long pause, then a click then the music plays from the internal speaker. You can no longer get the music to play from the bluetooth speaker. Things I've tried: Reboot the phone re connect to the bt speaker music still plays from the loud speaker on the phone. Turned off the speaker, restarted it still plays through the Loud speaker on the phone WORK AROUND: Forget the connection. Re pair the device now press play now it works as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1413363/+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 1598173] Re: Please consider SRU of "xcb: Compress mouse motion and touch update events"
Aha, I forgot to check the other bug. No worries. Thanks a lot for all the work Dmitry, looking at that bug I see that it is much more complicated than this one. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1598173 Title: Please consider SRU of "xcb: Compress mouse motion and touch update events" Status in qtbase-opensource-src package in Ubuntu: Fix Released Status in qtbase-opensource-src source package in Xenial: Fix Committed Bug description: Mouse event compression stopped working in Qt 5, a regression from Qt 4: https://bugreports.qt.io/browse/QTBUG-40889 The bug was fixed in Qt 5.6 https://codereview.qt- project.org/#/c/126136/ where the fix has been thoroughly tested by now. Attached is a debdiff against 5.5.1+dfsg-16ubuntu7.2 which includes a backport of the 5.6 patch (only one trivial hunk failed, which was easily fixed). [Impact] The bug affects any program that relies on the event compression Qt normally performs. For example, VTK programs (ParaView, Tomviz, ...) do their rendering in response to mouse events during camera movements, and with event compression at the Qt level suddenly gone, camera movements become very slow, since the application is now flooded with mouse events and the rendering lags behind. The problem is not limited to these programs however; it can be observed by simply putting two regular, slightly slow-to-render, widgets into a QSplitter and moving the splitter handle. The result is a syrup-like experience as the widgets try to keep up with the onslaught of resize events due to the lack of mouse event compression. [Test Case] The attached test application can be used to check if event compression is functioning. It performs some artificial work on each mouse move and prints a message. Click and drag the mouse a little. After releasing the mouse, you'll notice that the printouts keeps coming for quite a while, as the program is catching up with the flood of events. With the attached patch (and with Qt 4), the problem is gone - the mouse event stream is compressed and the printouts are no longer lagging behind. [Regression Potential] There's a small risk that some applications have made workarounds for the faulty behavior, and that unwanted behavior is introduced if this bug is fixed. But chances are high that such workarounds will keep working, as the obvious workaround is to do timer based rendering instead of event based. The workarounds will then simply become unnecessary, but shouldn't cause problems. I'm asking for someone to nominate this bug for an SRU of 16.04 LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1598173/+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 1689437] Re: bluetoothd crashed with SIGSEGV in __rawmemchr_ia32 from _IO_str_init_static_internal from _IO_vsscanf from __sscanf from get_supported_device
*** This bug is a duplicate of bug 1514166 *** https://bugs.launchpad.net/bugs/1514166 ** This bug has been marked a duplicate of bug 1514166 bluetoothd crashed with SIGSEGV in rawmemchr() from _IO_str_init_static_internal from _IO_vsscanf from __sscanf from get_supported_device [plugins/sixaxis.c] -- 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/1689437 Title: bluetoothd crashed with SIGSEGV in __rawmemchr_ia32 from _IO_str_init_static_internal from _IO_vsscanf from __sscanf from get_supported_device Status in bluez package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.43-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/5fc18b3add1fab2dc0d0676d7680aa9f1324f9fa contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1689437/+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 1370911] Re: bluetooth headset (Motorola S10-HD) remains connected despite it appears disconnected
Reduced priority for Ubuntu Touch bugs. ** Changed in: bluez (Ubuntu) Importance: High => Medium -- 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/1370911 Title: bluetooth headset (Motorola S10-HD) remains connected despite it appears disconnected Status in bluez package in Ubuntu: New Bug description: bluetooth headset (Motorola S10-HD) remains connected despite it appears disconnected Steps to reproduce: 1. Pair the Motorola S10-HD with krillin 2. Now disconnect the headtset form bluetooth settings page. 3. Note that bt headset settings page shows that device is disconnected. 4. Now play some music track Observe that music is still playing through bt headset while it is disconnected. Build/Device Info: phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 1 device name: krillin channel: ubuntu-touch/ubuntu-rtm/14.09 last update: 2014-09-16 17:43:20 version version: 1 version ubuntu: 20140916 version device: 20140912-23825b8 version custom: 1410739265 Bluetooth Headset: Motorola S10-HD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1370911/+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 1555608] Re: Bluetooth "Connection timed out" during a longer call
Reduced priority for Ubuntu Touch bugs. ** Changed in: bluez (Ubuntu) Importance: High => Medium -- 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/1555608 Title: Bluetooth "Connection timed out" during a longer call Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Confirmed Bug description: Issue: Phone disconnected bluetooth connection during a longer call. I am on: current build number: 275 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2016-03-08 06:14:58 version version: 275 version ubuntu: 20160308 version device: 20160108-efc96d8 version custom: 20160111-926-36--vivid I was in a longer telephone call. All of a sudden the bluetooth connection got interrupted. At the time when the bluetooth connection got disconnected the following statement from bluetooth was logged: Mar 9 08:26:31 ubuntu-phablet bluetoothd[899]: Start: Connection timed out (110) + following logs (see attached) The call itself still was active just the phone disconnected from my car. Logs are attached. Matthias To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1555608/+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 1398193] Re: The bluetooth headset cannot control media playback
Reduced priority for Ubuntu Touch bugs. ** Changed in: bluez (Ubuntu) Importance: High => Medium -- 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/1398193 Title: The bluetooth headset cannot control media playback Status in Canonical System Image: Triaged Status in bluez package in Ubuntu: Triaged Status in media-hub package in Ubuntu: Invalid Status in media-hub package in Ubuntu RTM: Invalid Bug description: [Preconditions] 1.The DUT pair with bluetooth headset [Procedures] 1.Play a video using the mediaplayer-app 2.Play/pause video by bluetooth headset [Expect results] The bluetooth headset can play/pause video [Actual results] The bluetooth headset can not control the video playback. [Reproduce] Always Same for audio playback To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1398193/+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 1435040] Re: Ubuntu Phone does not connect to car-bluetooth
Reduced priority for Ubuntu Touch bugs. ** Changed in: bluez (Ubuntu) Importance: High => Medium -- 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/1435040 Title: Ubuntu Phone does not connect to car-bluetooth Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Incomplete Bug description: With my FORD Focus Car, pairing does not work. The bluetooth system in the car searches for devices and shows "Aquaris E4.5 Ubuntu Edition" and then prompts me to connect with a 4-digit pin code, but the Ubuntu phone doesn't react at all and after a while the car system says that it failed to connect. image: 20150310-3201c0a KRILIN01A-S15A_BQ_L100EN_2020_150312 OS Build 20 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1435040/+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 1387949] Re: power cycling Emerson EM229 headset caused phone to reboot
Reduced priority for Ubuntu Touch bugs. ** Changed in: bluez (Ubuntu) Importance: High => Medium -- 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/1387949 Title: power cycling Emerson EM229 headset caused phone to reboot Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Confirmed Bug description: While sanity testing krillin rtm image 139, I paired a bluetooth headset. I made a call with it, hung up, then turned the headset off. I noticed this caused the BT indicator icon to invert, which is a nice way to indicate whether something is connected. So, I turned the device back on, waited for the icon to invert, turned the device off, waited, and instead of inverting the icon... the phone rebooted. Not sure what exactly failed here, like which component, but it's definitely not good when a paired headset can cause the phone to spontaneously reboot. I don't see any relevant .crash files, and all I see in syslog from that time is this: Oct 30 23:42:27 ubuntu-phablet NetworkManager[1429]: Activation (/ril_1) failed for connection '/310410695117999/context1' Oct 30 23:42:27 ubuntu-phablet NetworkManager[1429]: (/ril_1): device state change: failed -> disconnected (reason 'none') [120 30 0] Oct 30 23:42:27 ubuntu-phablet NetworkManager[1429]: (/ril_1): deactivating device (reason 'none') [0] Oct 30 23:43:01 ubuntu-phablet kernel: [ 747.229681][Ker_PM][request_suspend_state]wakeup (3->0) at 747214006509 (2014-10-31 05:43:01.704759580 UTC) Oct 30 23:43:02 ubuntu-phablet kernel: [ 747.779813]mtk-tpd: TPD wake up Oct 30 23:43:02 ubuntu-phablet kernel: [ 747.816572]mtk-tpd: TPD wake up done Oct 30 23:43:02 ubuntu-phablet kernel: [ 747.816593] mag_context_obj ok--->hwm_obj->early_suspend=0 Oct 30 23:43:09 ubuntu-phablet dbus[769]: [system] Activating service name='org.freedesktop.systemd1' (using servicehelper) Oct 30 23:43:09 ubuntu-phablet dbus[769]: [system] Successfully activated service 'org.freedesktop.systemd1' Oct 30 23:43:09 ubuntu-phablet rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="771" x-info="http://www.rsyslog.com";] exiting on signal 15. Oct 30 23:43:42 ubuntu-phablet rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="785" x-info="http://www.rsyslog.com";] start Oct 30 23:43:42 ubuntu-phablet rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ] Oct 30 23:43:42 ubuntu-phablet rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ] Oct 30 23:43:42 ubuntu-phablet rsyslogd: rsyslogd's groupid changed to 103 Oct 30 23:43:42 ubuntu-phablet rsyslogd: rsyslogd's userid changed to 100 Oct 30 23:43:42 ubuntu-phablet kernel: [0.00]Booting Linux on physical CPU 0 Oct 30 23:43:42 ubuntu-phablet kernel: [0.00]Initializing cgroup subsys cpu Oct 30 23:43:42 ubuntu-phablet kernel: [0.00]Linux version 3.4.67 (root@android-barajas_1414177384) (gcc version 4.7 (GCC) ) #1 SMP PREEMPT Tue Oct 28 11:57:42 UTC 2014 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1387949/+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 1479438] Re: IN CAR: Battery levels not shared via bluetooth for in car experience
Reduced priority for Ubuntu Touch bugs. ** Changed in: bluez (Ubuntu) Importance: High => Medium -- 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/1479438 Title: IN CAR: Battery levels not shared via bluetooth for in car experience Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: In Progress Status in ofono package in Ubuntu: Confirmed Status in ofono package in Ubuntu RTM: Confirmed Bug description: STEPS: Requirements: DUT a car with bluetooth and phone connection kit (Skoda Superb 2013 in my instance) 1. Connect the DUT to the car 2. On the display panel the battery always shows full EXPECTED: I expect to see the actual level of the battery on the device ACTUAL: The display always shows the battery at 100% I assume the default if no info is available. VERSIONS: current build number: 71 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en last update: 2015-07-28 18:01:08 version version: 71 version ubuntu: 20150728 version device: 20150709-8965e37 version custom: 20150716-819-8-42 MODIFICATIONS: Installation of silo19 for in car bt fix To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1479438/+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 1527354] Re: [Jawbone ERA] HFP features not working with Bluez5 when phone initiates connection
Reduced priority for Ubuntu Touch bugs. ** Changed in: bluez (Ubuntu) Importance: High => Medium -- 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/1527354 Title: [Jawbone ERA] HFP features not working with Bluez5 when phone initiates connection Status in Canonical System Image: In Progress Status in bluez package in Ubuntu: In Progress Bug description: While debugging some re-factoring work on the ofono upower plugin, I noticed that I wasn't able to answer or terminate calls using my Jawbone ERA headset. I bought this headset last year, and although it's an older model, it's spec sheet states that it supports HSP 1.1, and HFP 1.5. I can pair the device with my krillin, and it properly auto connects ( note, this seems to work better than my iPhone ). In-call audio works for both incoming and outgoing calls, however I get no ringtone in the headset and as mentioned above, I can't answer or terminate the call. I've verified on my iPhone6, that the headset works. In addition to a ringtone in the earpiece, the headset also announces the incoming phone number. From looking at the ofono debug output, I'm never seeing a new HFP connection occur. I noticed as the upower plugin uses a foreach_atom (HFP) style call to update the battery indicators on all attached HFP devices. I've tested this extensively on krillin, running rc-proposed: phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 205 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2015-12-16 17:53:19 version version: 205 version ubuntu: 20151216 version device: 20151204-2254a36 version custom: 2015--36-46-vivid I've also tested on mako, rc-proposed ( #317 ). For reference here's the versions of bluez, ofono, and PulseAudio on the device: bluez 5.36-0ubuntu2~overlay1 ofono 1.17.bzr6908+15.04.20151203-0ubuntu1~awe3 pulseaudio1:6.0-0ubuntu9.11 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1527354/+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 1552410] Re: Cannot pair mako with 2014 Subaru Forester
Reduced priority for Ubuntu Touch bugs. ** Changed in: bluez (Ubuntu) Importance: High => Medium -- 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/1552410 Title: Cannot pair mako with 2014 Subaru Forester Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Confirmed Bug description: Since the bluez5 transition my mako has not been able to pair with the radio in my 2014 Subaru Forester. When the radio is put into pairing mode the phone sees the CAR_M_MEDIA device, but when I click "connect" the radio immediately shows "failed" and no PIN prompt is shown on the phone. Additionally, the entry in system-settings for the car stereo is left in a limbo state with the "forget" button inactive. The only way to remove the entry is to use bluetoothctl from the command line. Here's what the phone is currently running: current build number: 252 device name: mako channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2016-03-02 00:31:33 version version: 252 version ubuntu: 20160302 version device: 20160112 version custom: 20160201-5-vivid To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1552410/+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 1494225] Re: Call audio is not routed to headset with HFP
Reduced priority for Ubuntu Touch bugs. ** Changed in: bluez (Ubuntu) Importance: Critical => Medium ** Changed in: pulseaudio (Ubuntu) Importance: Critical => Medium -- 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/1494225 Title: Call audio is not routed to headset with HFP Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Confirmed Status in media-hub package in Ubuntu: Invalid Status in ofono package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: With bluez 5.33 on Nexus 4 and silo 43 installed: * pair and connect a headset over HFP * Establish an outgoing call or accept an incoming one * Once the call is established the call audio isn't routed through the handsfree device To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1494225/+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 1532980] Re: have to "forget" device sometimes
Reduced priority for Ubuntu Touch bugs. ** Changed in: bluez (Ubuntu) Importance: High => Medium -- 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/1532980 Title: have to "forget" device sometimes Status in Canonical System Image: Confirmed Status in Canonical Pocket Desktop: New Status in bluez package in Ubuntu: Confirmed Bug description: while testing pd, had trouble connecting a previously connected mouse. attempted the restart indicator-bluetooth trick, this didn't help. I could see the mouse in the list, but never would connect when selecting the "connect" button. in the end had to "forget device" then refresh list, then device would connect. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1532980/+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 1539158] Re: Unable to pair with in-car hands-free system after OTA-9 update
Reduced priority for Ubuntu Touch bugs. ** Changed in: bluez (Ubuntu) Importance: High => Medium -- 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/1539158 Title: Unable to pair with in-car hands-free system after OTA-9 update Status in Canonical System Image: Fix Released Status in bluez package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Fix Released Bug description: After OTA-9 I started having trouble with my bluetooth connection to the car hands-free system (no sound, and incoming calls no longer displayed the number), so I have reset both the car and the phone connections (eg. forgot the devices). Now I can't even pair the phone with the car's system. The car finds the phone, and then asks me to enter the code "" to pair the device, but after a few moments, it just says the connection failed and asks me to try again. Which fails again. It was working fine just before the update. Any logs I should post to help debug? PS - The car is a 2015 Honda Civic Tourer, if that matters. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1539158/+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 1565957] Re: Issue pairing with BTLE "Smart technology" mouse
Reduced priority for Ubuntu Touch bugs. ** Changed in: bluez (Ubuntu) Importance: High => Medium -- 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/1565957 Title: Issue pairing with BTLE "Smart technology" mouse Status in bluez package in Ubuntu: Confirmed Bug description: I have a Gearhead MBT9950 Testing with M10 running r75 I started bluetoothd with --experimental. I did not see the device in the UI I was able to pair it using bluetoothctl, (the only issue is the mouse movement is rather laggy, the velocity is weird and it overshoots) The UI still does not show the device connected. Device 84:EB:18:2B:47:28 Name: MBT9950 Alias: MBT9950 Appearance: 0x03c2 Icon: input-mouse Paired: no Trusted: no Blocked: no Connected: no LegacyPairing: no To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1565957/+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 1576951] Re: System hangs if apple magic mouse is connected via bluetooth
Reduced priority for Ubuntu Touch bugs. ** Changed in: bluez (Ubuntu) Importance: High => Medium -- 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/1576951 Title: System hangs if apple magic mouse is connected via bluetooth Status in Canonical System Image: Confirmed Status in frieza: New Status in turbo: New Status in bluez package in Ubuntu: Confirmed Bug description: If you connect apple magic mouse via bluetooth the system hangs completely. After 1 minute the system restarts. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1576951/+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 1396973] Re: Audio not switched when headset disabled via bluetooth on/off
** Tags added: bluez-touch -- 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/1396973 Title: Audio not switched when headset disabled via bluetooth on/off Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: New Bug description: Version: ubuntu-touch/ubuntu-rtm/14.09-proposed r169 krillin Steps to reproduce: * Pair krillin with BT Headset (Sony MDR-10RBT used in test) * Call the handset * Answer call * Check headset input/output * Disable Bluetooth on the krillin * Audio routed to phone speaker/mic * Re-enable Bluetooth Expected result: - Bluetooth re-connects to headset audio routed back to headset input/output Actual result: - Audio seems to be routed badly - no audio on call at all from krillin To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1396973/+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 1370911] Re: bluetooth headset (Motorola S10-HD) remains connected despite it appears disconnected
** Tags added: bluez-touch -- 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/1370911 Title: bluetooth headset (Motorola S10-HD) remains connected despite it appears disconnected Status in bluez package in Ubuntu: New Bug description: bluetooth headset (Motorola S10-HD) remains connected despite it appears disconnected Steps to reproduce: 1. Pair the Motorola S10-HD with krillin 2. Now disconnect the headtset form bluetooth settings page. 3. Note that bt headset settings page shows that device is disconnected. 4. Now play some music track Observe that music is still playing through bt headset while it is disconnected. Build/Device Info: phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 1 device name: krillin channel: ubuntu-touch/ubuntu-rtm/14.09 last update: 2014-09-16 17:43:20 version version: 1 version ubuntu: 20140916 version device: 20140912-23825b8 version custom: 1410739265 Bluetooth Headset: Motorola S10-HD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1370911/+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 1387949] Re: power cycling Emerson EM229 headset caused phone to reboot
** Tags added: bluez-touch -- 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/1387949 Title: power cycling Emerson EM229 headset caused phone to reboot Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Confirmed Bug description: While sanity testing krillin rtm image 139, I paired a bluetooth headset. I made a call with it, hung up, then turned the headset off. I noticed this caused the BT indicator icon to invert, which is a nice way to indicate whether something is connected. So, I turned the device back on, waited for the icon to invert, turned the device off, waited, and instead of inverting the icon... the phone rebooted. Not sure what exactly failed here, like which component, but it's definitely not good when a paired headset can cause the phone to spontaneously reboot. I don't see any relevant .crash files, and all I see in syslog from that time is this: Oct 30 23:42:27 ubuntu-phablet NetworkManager[1429]: Activation (/ril_1) failed for connection '/310410695117999/context1' Oct 30 23:42:27 ubuntu-phablet NetworkManager[1429]: (/ril_1): device state change: failed -> disconnected (reason 'none') [120 30 0] Oct 30 23:42:27 ubuntu-phablet NetworkManager[1429]: (/ril_1): deactivating device (reason 'none') [0] Oct 30 23:43:01 ubuntu-phablet kernel: [ 747.229681][Ker_PM][request_suspend_state]wakeup (3->0) at 747214006509 (2014-10-31 05:43:01.704759580 UTC) Oct 30 23:43:02 ubuntu-phablet kernel: [ 747.779813]mtk-tpd: TPD wake up Oct 30 23:43:02 ubuntu-phablet kernel: [ 747.816572]mtk-tpd: TPD wake up done Oct 30 23:43:02 ubuntu-phablet kernel: [ 747.816593] mag_context_obj ok--->hwm_obj->early_suspend=0 Oct 30 23:43:09 ubuntu-phablet dbus[769]: [system] Activating service name='org.freedesktop.systemd1' (using servicehelper) Oct 30 23:43:09 ubuntu-phablet dbus[769]: [system] Successfully activated service 'org.freedesktop.systemd1' Oct 30 23:43:09 ubuntu-phablet rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="771" x-info="http://www.rsyslog.com";] exiting on signal 15. Oct 30 23:43:42 ubuntu-phablet rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="785" x-info="http://www.rsyslog.com";] start Oct 30 23:43:42 ubuntu-phablet rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ] Oct 30 23:43:42 ubuntu-phablet rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ] Oct 30 23:43:42 ubuntu-phablet rsyslogd: rsyslogd's groupid changed to 103 Oct 30 23:43:42 ubuntu-phablet rsyslogd: rsyslogd's userid changed to 100 Oct 30 23:43:42 ubuntu-phablet kernel: [0.00]Booting Linux on physical CPU 0 Oct 30 23:43:42 ubuntu-phablet kernel: [0.00]Initializing cgroup subsys cpu Oct 30 23:43:42 ubuntu-phablet kernel: [0.00]Linux version 3.4.67 (root@android-barajas_1414177384) (gcc version 4.7 (GCC) ) #1 SMP PREEMPT Tue Oct 28 11:57:42 UTC 2014 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1387949/+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 1379485] Re: bluez only manages one modem with HSP (not dual as we have on krillin)
** Tags added: bluez-touch -- 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/1379485 Title: bluez only manages one modem with HSP (not dual as we have on krillin) Status in bluez package in Ubuntu: Confirmed Bug description: STEPS: 1. Have a device with 2 sim cards 2. Connect to a bluetooth car/headset (car is better it shows the network you are connected to) 3. Call sim number one (rings on phone but not bt device) 4. Call sim number two (rings on phone and bt device) EXPECTED: In both situations you expect the call to trigger the ringer on both of the sims numbers ACTUAL: For me only sim number 2 triggers the ringer on the device and the mobile. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1379485/+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 1398193] Re: The bluetooth headset cannot control media playback
** Tags added: bluez-touch -- 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/1398193 Title: The bluetooth headset cannot control media playback Status in Canonical System Image: Triaged Status in bluez package in Ubuntu: Triaged Status in media-hub package in Ubuntu: Invalid Status in media-hub package in Ubuntu RTM: Invalid Bug description: [Preconditions] 1.The DUT pair with bluetooth headset [Procedures] 1.Play a video using the mediaplayer-app 2.Play/pause video by bluetooth headset [Expect results] The bluetooth headset can play/pause video [Actual results] The bluetooth headset can not control the video playback. [Reproduce] Always Same for audio playback To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1398193/+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 1657553] Re: Laptop stick and touchpad problems after linux 4.4 update
** Attachment added: "71-pointingstick-5470.hwdb" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1657553/+attachment/4873861/+files/71-pointingstick-5470.hwdb -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1657553 Title: Laptop stick and touchpad problems after linux 4.4 update Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Confirmed Status in linux source package in Xenial: Incomplete Status in systemd source package in Xenial: Confirmed Bug description: Ever since the 4.4.0-53 kernel update the touchpad and trackpoint have behaved erratically on my Dell Precision 7510: * The trackpoint moves WAY too fast and there don't seem to be any parameters I can change in xinput to fix this. It is essentially unusable. * The touchpad starts with parameters set incorrectly. * Touchpad tap to click is now turned on again and is very sensitive. This I can change through xinput but the change is still odd. * The two finger scrolling is set incorrectly to be highly sensitive. This I can also change through xinput. * Two finger scrolling still activates often during normal use of the trackpad. To the extent that I had to turn off two finger scrolling to stop inadvertent scrolling. All of the above behavior is new going from 4.4.0-47 to -53. Previously this all worked perfectly on this machine. Seems to be symptoms noted by these other users on askubuntu here as well: http://askubuntu.com/questions/862527/laptop-stick-mouse- problems-after-linux-4-4-update-on-14-04 The touchpad symptoms I seem to be able to work around my changing xinput parameters, but the trackpoint I have not been able to fix at all (which is sad since that is my primary mouse device normally). Would appreciate any suggestions as to how to revert the old behavior. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-53-generic 4.4.0-53.74 ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jpeverill 2813 F pulseaudio /dev/snd/controlC0: jpeverill 2813 F pulseaudio Date: Wed Jan 18 10:21:55 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2014-07-17 (916 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 004: ID 1bcf:2b91 Sunplus Innovation Technology Inc. Bus 001 Device 003: ID 0a5c:5832 Broadcom Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Precision 7510 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic.efi.signed root=UUID=4a4cfeb0-ad39-4293-bcaf-000d6538b550 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-59-generic N/A linux-backports-modules-4.4.0-59-generic N/A linux-firmware1.157.6 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-05-01 (262 days ago) dmi.bios.date: 01/24/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.10 dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.10:bd01/24/2016:svnDellInc.:pnPrecision7510:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Precision 7510 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1657553/+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 1657553] Re: Laptop stick and touchpad problems after linux 4.4 update
Hi, please download the attach file, then $ sudo cp 71-pointingstick-5470.hwdb /etc/udev/hwdb.d/ $ sudo systemd-hwdb update $ sudo udevadm trigger And check if this issue is solved or not. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1657553 Title: Laptop stick and touchpad problems after linux 4.4 update Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Confirmed Status in linux source package in Xenial: Incomplete Status in systemd source package in Xenial: Confirmed Bug description: Ever since the 4.4.0-53 kernel update the touchpad and trackpoint have behaved erratically on my Dell Precision 7510: * The trackpoint moves WAY too fast and there don't seem to be any parameters I can change in xinput to fix this. It is essentially unusable. * The touchpad starts with parameters set incorrectly. * Touchpad tap to click is now turned on again and is very sensitive. This I can change through xinput but the change is still odd. * The two finger scrolling is set incorrectly to be highly sensitive. This I can also change through xinput. * Two finger scrolling still activates often during normal use of the trackpad. To the extent that I had to turn off two finger scrolling to stop inadvertent scrolling. All of the above behavior is new going from 4.4.0-47 to -53. Previously this all worked perfectly on this machine. Seems to be symptoms noted by these other users on askubuntu here as well: http://askubuntu.com/questions/862527/laptop-stick-mouse- problems-after-linux-4-4-update-on-14-04 The touchpad symptoms I seem to be able to work around my changing xinput parameters, but the trackpoint I have not been able to fix at all (which is sad since that is my primary mouse device normally). Would appreciate any suggestions as to how to revert the old behavior. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-53-generic 4.4.0-53.74 ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jpeverill 2813 F pulseaudio /dev/snd/controlC0: jpeverill 2813 F pulseaudio Date: Wed Jan 18 10:21:55 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2014-07-17 (916 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 004: ID 1bcf:2b91 Sunplus Innovation Technology Inc. Bus 001 Device 003: ID 0a5c:5832 Broadcom Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Precision 7510 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic.efi.signed root=UUID=4a4cfeb0-ad39-4293-bcaf-000d6538b550 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-59-generic N/A linux-backports-modules-4.4.0-59-generic N/A linux-firmware1.157.6 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-05-01 (262 days ago) dmi.bios.date: 01/24/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.10 dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.10:bd01/24/2016:svnDellInc.:pnPrecision7510:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Precision 7510 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1657553/+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 1509622] Re: Xorg crash
[Expired for xorg (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg (Ubuntu) Status: Incomplete => Expired -- 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/1509622 Title: Xorg crash Status in xorg package in Ubuntu: Expired Bug description: This is the full apport data from the crash reported as bug #1507461. It occurred whilst watching a full-screen Flash video in Google Chrome. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.19.1-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sat Oct 24 18:04:11 2015 DistUpgraded: Fresh install DistroCodename: wily DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21fa] MachineType: LENOVO CTO ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-16-generic root=/dev/mapper/peleg0-lv01 ro splash quiet nomdmonddf nomdmonisw vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/24/2012 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET33WW (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ET33WW(1.13):bd07/24/2012:svnLENOVO:pnCTO:pvrThinkPadX230:rvnLENOVO:rnCTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: CTO dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Sat Oct 24 17:58:31 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 728 vendor LGD xserver.version: 2:1.17.2-1ubuntu9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1509622/+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 1670724] Re: Cannot launch hp tools
[Expired for unity8 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: unity8 (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1670724 Title: Cannot launch hp tools Status in Canonical System Image: Incomplete Status in unity8 package in Ubuntu: Expired Bug description: hplip is a common set of tools to manage HP printers. The tools fail to start on unity8 and the indicator is not displayed in the top panel. The following message is displayed on the command line: - HP Linux Imaging and Printing System (ver. 3.16.11) Printer/Fax Setup Utility ver. 9.0 Copyright (c) 2001-15 HP Development Company, LP This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to distribute it under certain conditions. See COPYING file for more details. Loading module: 'libubuntu_application_api_desktop_mirclient.so.3.0.0' [QPA] QMirClientClientIntegration: connection to Mir server failed. Mir returned: "Failed to connect: not accepted by server" [2017-03-07 16:06:27.426662] MirConnectionAPI: Caught exception at client library boundary (in mir_connection_release): /build/mir-rgB9wX/mir-0.26.1+17.04.20170209.1/src/client/rpc/stream_socket_transport.cpp(168): Throw in function virtual void mir::client::rpc::StreamSocketTransport::send_message(const std::vector&, const std::vector&) Dynamic exception type: boost::exception_detail::clone_impl > std::exception::what: Failed to send message to server: Relais brisé (pipe) [boost::errinfo_errno_*] = 32, "Relais brisé (pipe)" - ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: unity8 8.15+17.04.20170221-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-9.11-generic 4.10.0 Uname: Linux 4.10.0-9-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 Date: Tue Mar 7 16:08:35 2017 InstallationDate: Installed on 2014-07-23 (958 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) SourcePackage: unity8 UpgradeStatus: Upgraded to zesty on 2016-11-15 (112 days ago) upstart.unity8-dash.log: [2017-03-07:15:15:07.070] "clickscope" : setActive: false To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1670724/+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 1689437] Re: bluetoothd crashed with SIGSEGV in __rawmemchr_ia32 from _IO_str_init_static_internal from _IO_vsscanf from __sscanf from get_supported_device
** Changed in: bluez (Ubuntu) Status: New => Confirmed -- 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/1689437 Title: bluetoothd crashed with SIGSEGV in __rawmemchr_ia32 from _IO_str_init_static_internal from _IO_vsscanf from __sscanf from get_supported_device Status in bluez package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.43-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/5fc18b3add1fab2dc0d0676d7680aa9f1324f9fa contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1689437/+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 1689435] Re: bluetoothd crashed with SIGSEGV in browse_cb from search_completed_cb from sdp_process from search_process_cb from g_main_dispatch
** Changed in: bluez (Ubuntu) Status: New => Confirmed -- 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/1689435 Title: bluetoothd crashed with SIGSEGV in browse_cb from search_completed_cb from sdp_process from search_process_cb from g_main_dispatch Status in bluez package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.43-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/257c18b3cbc69a5ebb4fc9e4efa0f5564822daf0 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1689435/+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 1689436] Re: bluetoothd crashed with SIGABRT due to heap corruption "double free or corruption (fasttop)"
** Changed in: bluez (Ubuntu) Status: New => Confirmed -- 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/1689436 Title: bluetoothd crashed with SIGABRT due to heap corruption "double free or corruption (fasttop)" Status in bluez package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.43-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/2522ea5604a622769e532f07ec9ecab43310bf23 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1689436/+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 1689440] Re: bluetoothd crashed with SIGSEGV in btd_device_get_service from policy_connect_sink from g_timeout_dispatch from g_main_dispatch from g_main_context_dispatch
** Changed in: bluez (Ubuntu) Status: New => Confirmed -- 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/1689440 Title: bluetoothd crashed with SIGSEGV in btd_device_get_service from policy_connect_sink from g_timeout_dispatch from g_main_dispatch from g_main_context_dispatch Status in bluez package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.43-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/685c44346c1666e27b097b86cba784459205e32d contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1689440/+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 1689445] Re: bluetoothd crashed with SIGSEGV in timeout_cb from timeout_callback from g_timeout_dispatch from g_main_dispatch from g_main_context_dispatch
** Changed in: bluez (Ubuntu) Status: New => Confirmed -- 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/1689445 Title: bluetoothd crashed with SIGSEGV in timeout_cb from timeout_callback from g_timeout_dispatch from g_main_dispatch from g_main_context_dispatch Status in bluez package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.43-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/b959171c4183443c43f641033bf8efcdee964438 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1689445/+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 1689443] Re: bluetoothd crashed with SIGSEGV in g_io_channel_unref from control_connect_cb from connect_cb from g_main_dispatch from g_main_context_dispatch
** Changed in: bluez (Ubuntu) Status: New => Confirmed -- 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/1689443 Title: bluetoothd crashed with SIGSEGV in g_io_channel_unref from control_connect_cb from connect_cb from g_main_dispatch from g_main_context_dispatch Status in bluez package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.43-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/60e9f362576651ff41d2c58e273c79aa15824ad8 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1689443/+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 1689442] Re: bluetoothd crashed with SIGSEGV in btd_service_connecting_complete from control_connect_cb from connect_cb from g_main_dispatch from g_main_context_dispatch
** Changed in: bluez (Ubuntu) Status: New => Confirmed -- 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/1689442 Title: bluetoothd crashed with SIGSEGV in btd_service_connecting_complete from control_connect_cb from connect_cb from g_main_dispatch from g_main_context_dispatch Status in bluez package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.43-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/fffbe12b82b8b2181e3dc736bea0a598f3b61042 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1689442/+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 1689463] Re: /usr/lib/bluetooth/bluetoothd:11:ba2str:update_bredr_services:browse_cb:search_completed_cb:sdp_process
** Changed in: bluez (Ubuntu) Importance: Undecided => High ** Changed in: bluez (Ubuntu) Status: New => Confirmed ** Summary changed: - /usr/lib/bluetooth/bluetoothd:11:ba2str:update_bredr_services:browse_cb:search_completed_cb:sdp_process + bluetoothd crashing with SIGSEGV in ba2str from update_bredr_services from browse_cb from search_completed_cb from sdp_process -- 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/1689463 Title: bluetoothd crashing with SIGSEGV in ba2str from update_bredr_services from browse_cb from search_completed_cb from sdp_process Status in bluez package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.43-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/34f2d57d9e4087da25c8712bf1ea880ced7a88b6 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1689463/+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 1689464] Re: /usr/lib/bluetooth/bluetoothd:11:g_io_channel_shutdown:avctp_channel_destroy:avctp_disconnected:avctp_set_state:session_cb
** Changed in: bluez (Ubuntu) Importance: Undecided => High ** Changed in: bluez (Ubuntu) Status: New => Confirmed ** Summary changed: - /usr/lib/bluetooth/bluetoothd:11:g_io_channel_shutdown:avctp_channel_destroy:avctp_disconnected:avctp_set_state:session_cb + bluetoothd crashing with SIGSEGV in g_io_channel_shutdown from avctp_channel_destroy from avctp_disconnected from avctp_set_state from session_cb -- 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/1689464 Title: bluetoothd crashing with SIGSEGV in g_io_channel_shutdown from avctp_channel_destroy from avctp_disconnected from avctp_set_state from session_cb Status in bluez package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.43-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/a562dd1c2698bbeadb296ebb39c238522aeb3600 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1689464/+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 1689465] Re: bluetoothd crashing with SIGABRT due to heap corruption - malloc(): smallbin double linked list corrupted
** Summary changed: - /usr/lib/bluetooth/bluetoothd:*** Error in `/usr/lib/bluetooth/bluetoothd': malloc(): smallbin double linked list corrupted: ADDR *** + bluetoothd crashing with SIGABRT due to heap corruption - malloc(): smallbin double linked list corrupted ** Changed in: bluez (Ubuntu) Importance: Undecided => High ** Changed in: bluez (Ubuntu) Status: New => Triaged ** Changed in: bluez (Ubuntu) Status: Triaged => Confirmed -- 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/1689465 Title: bluetoothd crashing with SIGABRT due to heap corruption - malloc(): smallbin double linked list corrupted Status in bluez package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.43-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/2cd62ac3fc6977ec03346b6dedcb8edee13c8014 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1689465/+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 1689448] Re: bluetoothd crashed with SIGSEGV in avdtp_stream_set_transport transport_cb accept_cb g_main_dispatch g_main_context_dispatch
** Changed in: bluez (Ubuntu) Status: New => Confirmed -- 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/1689448 Title: bluetoothd crashed with SIGSEGV in avdtp_stream_set_transport transport_cb accept_cb g_main_dispatch g_main_context_dispatch Status in bluez package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.43-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/74228037aee5c1e95c18d26533f63d5396d48e3e contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1689448/+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 1689451] Re: bluetoothd crashed with SIGSEGV in queue_remove_if from bt_att_unregister_disconnect from attio_cleanup from browse_request_cancel from device_remove
** Changed in: bluez (Ubuntu) Status: New => Confirmed -- 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/1689451 Title: bluetoothd crashed with SIGSEGV in queue_remove_if from bt_att_unregister_disconnect from attio_cleanup from browse_request_cancel from device_remove Status in bluez package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.41-0ubuntu3, the problem page at https://errors.ubuntu.com/problem/686eb99935548ae15300b85caf382f510d0c074f contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1689451/+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 1689452] Re: bluetoothd crashed with SIGSEGV in avdtp_sep_set_state from avdtp_abort_resp from avdtp_parse_resp from session_cb from g_main_dispatch
** Changed in: bluez (Ubuntu) Status: New => Confirmed -- 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/1689452 Title: bluetoothd crashed with SIGSEGV in avdtp_sep_set_state from avdtp_abort_resp from avdtp_parse_resp from session_cb from g_main_dispatch Status in bluez package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.43-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/108dd760fb9f1f5bb12e155ffad01ee758816f36 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1689452/+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 1689450] Re: bluetoothd crashed with SIGSEGV in strlen from _dbus_string_init_const from _dbus_check_is_valid_path from dbus_message_iter_append_basic from dev_property_get_adapt
** Changed in: bluez (Ubuntu) Status: New => Confirmed -- 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/1689450 Title: bluetoothd crashed with SIGSEGV in strlen from _dbus_string_init_const from _dbus_check_is_valid_path from dbus_message_iter_append_basic from dev_property_get_adapter Status in bluez package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.43-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/e95b08689734fed39c54cb1173dccd71279f1c1a contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1689450/+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 1689466] Re: bluetoothd crashing with SIGSEGV in encrypt_notify from g_io_unix_dispatch from g_main_dispatch from g_main_context_dispatch from g_main_context_iterate
** Summary changed: - /usr/lib/bluetooth/bluetoothd:11:encrypt_notify:g_io_unix_dispatch:g_main_dispatch:g_main_context_dispatch:g_main_context_iterate + bluetoothd crashing with SIGSEGV in encrypt_notify from g_io_unix_dispatch from g_main_dispatch from g_main_context_dispatch from g_main_context_iterate ** Changed in: bluez (Ubuntu) Importance: Undecided => Medium ** Changed in: bluez (Ubuntu) Status: New => Confirmed -- 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/1689466 Title: bluetoothd crashing with SIGSEGV in encrypt_notify from g_io_unix_dispatch from g_main_dispatch from g_main_context_dispatch from g_main_context_iterate Status in bluez package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.37-0ubuntu5, the problem page at https://errors.ubuntu.com/problem/51e27350205066877db9eee38a77d852664027f7 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1689466/+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 1689461] Re: /usr/lib/bluetooth/bluetoothd:11:g_io_channel_shutdown:attio_cleanup:browse_request_cancel:device_remove:btd_adapter_remove_device
** Changed in: bluez (Ubuntu) Importance: Undecided => Medium ** Changed in: bluez (Ubuntu) Status: New => Confirmed ** Summary changed: - /usr/lib/bluetooth/bluetoothd:11:g_io_channel_shutdown:attio_cleanup:browse_request_cancel:device_remove:btd_adapter_remove_device + bluetoothd crashed with SIGSEGV from g_io_channel_shutdown from attio_cleanup from browse_request_cancel from device_remove from btd_adapter_remove_device -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1689461 Title: bluetoothd crashed with SIGSEGV from g_io_channel_shutdown from attio_cleanup from browse_request_cancel from device_remove from btd_adapter_remove_device Status in bluez package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.37-0ubuntu5, the problem page at https://errors.ubuntu.com/problem/732cce930e4db100b0ec943638e1029f4655fbf9 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1689461/+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 1689460] Re: bluetoothd crashing with SIGSEGV in avdtp_unref from setup_free from setup_unref from transport_cb from accept_cb
** Summary changed: - /usr/lib/bluetooth/bluetoothd:11:avdtp_unref:setup_free:setup_unref:transport_cb:accept_cb + bluetoothd crashing with SIGSEGV in avdtp_unref from setup_free from setup_unref from transport_cb from accept_cb ** Changed in: bluez (Ubuntu) Importance: Undecided => High ** Changed in: bluez (Ubuntu) Status: New => Confirmed -- 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/1689460 Title: bluetoothd crashing with SIGSEGV in avdtp_unref from setup_free from setup_unref from transport_cb from accept_cb Status in bluez package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.43-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/b07fc39aa06a535581fad194d445c76f189364c1 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1689460/+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 1689456] Re: obexd crashed with SIGSEGV in main_arena from xfer_complete from transfer_complete from transfer_abort_response from handle_response
** Summary changed: - /usr/lib/bluetooth/obexd:11:main_arena:xfer_complete:transfer_complete:transfer_abort_response:handle_response + obexd crashed with SIGSEGV in main_arena from xfer_complete from transfer_complete from transfer_abort_response from handle_response ** Changed in: bluez (Ubuntu) Importance: Undecided => Medium ** Changed in: bluez (Ubuntu) Status: New => Confirmed -- 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/1689456 Title: obexd crashed with SIGSEGV in main_arena from xfer_complete from transfer_complete from transfer_abort_response from handle_response Status in bluez package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.37-0ubuntu5, the problem page at https://errors.ubuntu.com/problem/e5556f928fe0308e14b1e88856fa73749f61ce2a contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1689456/+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 1689457] Re: bluetoothd crashing with SIGSEGV in g_io_channel_shutdown from attio_cleanup from browse_request_cancel from device_remove from adapter_remove
** Summary changed: - /usr/lib/bluetooth/bluetoothd:11:g_io_channel_shutdown:attio_cleanup:browse_request_cancel:device_remove:adapter_remove + bluetoothd crashing with SIGSEGV in g_io_channel_shutdown from attio_cleanup from browse_request_cancel from device_remove from adapter_remove -- 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/1689457 Title: bluetoothd crashing with SIGSEGV in g_io_channel_shutdown from attio_cleanup from browse_request_cancel from device_remove from adapter_remove Status in bluez package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.43-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/e2c5f3e07125e7ba40af3a44a3b07adb73420030 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1689457/+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 1689459] Re: bluetoothd crashing with SIGSEGV in ext_confirm from server_cb from g_main_dispatch from g_main_context_dispatch from g_main_context_iterate
** Summary changed: - /usr/lib/bluetooth/bluetoothd:11:ext_confirm:server_cb:g_main_dispatch:g_main_context_dispatch:g_main_context_iterate + bluetoothd crashing with SIGSEGV in ext_confirm from server_cb from g_main_dispatch from g_main_context_dispatch from g_main_context_iterate ** Changed in: bluez (Ubuntu) Importance: Undecided => High ** Changed in: bluez (Ubuntu) Status: New => Confirmed -- 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/1689459 Title: bluetoothd crashing with SIGSEGV in ext_confirm from server_cb from g_main_dispatch from g_main_context_dispatch from g_main_context_iterate Status in bluez package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.43-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/79fb1a2bdca7699121c71f94778d0ac7688ef891 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1689459/+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 1689458] Re: bluetoothd crashing with SIGSEGV in device_svc_resolved from search_cb from browse_cb from connect_watch from g_main_dispatch
** Summary changed: - /usr/lib/bluetooth/bluetoothd:11:device_svc_resolved:search_cb:browse_cb:connect_watch:g_main_dispatch + bluetoothd crashing with SIGSEGV in device_svc_resolved from search_cb from browse_cb from connect_watch from g_main_dispatch ** Changed in: bluez (Ubuntu) Importance: Undecided => High ** Changed in: bluez (Ubuntu) Status: New => Confirmed -- 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/1689458 Title: bluetoothd crashing with SIGSEGV in device_svc_resolved from search_cb from browse_cb from connect_watch from g_main_dispatch Status in bluez package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.41-0ubuntu3, the problem page at https://errors.ubuntu.com/problem/3d579b15e5040bb946caffbf22f9ee8124529197 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1689458/+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 1689462] Re: /usr/lib/bluetooth/bluetoothd:11:release_stream:g_slist_foreach:connection_lost:disconnect_timeout:g_timeout_dispatch
** Changed in: bluez (Ubuntu) Importance: Undecided => High ** Changed in: bluez (Ubuntu) Status: New => Confirmed ** Summary changed: - /usr/lib/bluetooth/bluetoothd:11:release_stream:g_slist_foreach:connection_lost:disconnect_timeout:g_timeout_dispatch + bluetoothd crashing with SIGSEGV in release_stream from g_slist_foreach from connection_lost from disconnect_timeout from g_timeout_dispatch -- 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/1689462 Title: bluetoothd crashing with SIGSEGV in release_stream from g_slist_foreach from connection_lost from disconnect_timeout from g_timeout_dispatch Status in bluez package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.41-0ubuntu3, the problem page at https://errors.ubuntu.com/problem/d9aec0cc9617e42fcd64fe69270d8f758e39c453 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1689462/+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 1556324] Re: bluetoothd crashed with SIGSEGV in encrypt_notify from g_main_dispatch from g_main_context_dispatch from g_main_context_iterate from g_main_loop_run
This bug is the #1 crasher of bluetoothd right now... https://errors.ubuntu.com/?package=bluez&period=year ** Tags added: yakkety 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/1556324 Title: bluetoothd crashed with SIGSEGV in encrypt_notify from g_main_dispatch from g_main_context_dispatch from g_main_context_iterate from g_main_loop_run Status in bluez package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with version 5.36-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/20c758a42f23b514e8bc98469a414de3ed9b727f contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1556324/+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 1689438] Re: bluetoothd crashed with SIGABRT in free(): invalid pointer
** Changed in: bluez (Ubuntu) Status: New => Confirmed -- 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/1689438 Title: bluetoothd crashed with SIGABRT in free(): invalid pointer Status in bluez package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.43-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/9690f8797e673b0fa8359647ae193ab8d0a62d3e contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1689438/+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 1689455] Re: /usr/lib/bluetooth/obexd:11:_dbus_header_cache_check:_dbus_header_get_field_basic:dbus_message_get_sender:dbus_message_new_method_return:abort_complete
** Changed in: bluez (Ubuntu) Importance: Undecided => Medium ** Changed in: bluez (Ubuntu) Status: New => Confirmed ** Summary changed: - /usr/lib/bluetooth/obexd:11:_dbus_header_cache_check:_dbus_header_get_field_basic:dbus_message_get_sender:dbus_message_new_method_return:abort_complete + obexd crashed with SIGSEGV in _dbus_header_cache_check from _dbus_header_get_field_basic from dbus_message_get_sender from dbus_message_new_method_return from abort_complete -- 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/1689455 Title: obexd crashed with SIGSEGV in _dbus_header_cache_check from _dbus_header_get_field_basic from dbus_message_get_sender from dbus_message_new_method_return from abort_complete Status in bluez package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.37-0ubuntu5, the problem page at https://errors.ubuntu.com/problem/5d1def138d65e6306ef3c03b6ee79217e5ed7fe3 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1689455/+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 1514166] Re: bluetoothd crashed with SIGSEGV in rawmemchr()
** Changed in: bluez (Ubuntu) Importance: Medium => High ** Changed in: bluez (Ubuntu) Status: New => Confirmed ** Description changed: bluetoothd crashed with SIGSEGV in rawmemchr() + + https://errors.ubuntu.com/problem/f0eca11dfcb228bd89caa34e5f9b5529151c0c88 ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: bluez 5.35-0ubuntu2 ProcVersionSignature: Ubuntu 4.2.0-17.21-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 NonfreeKernelModules: openafs ApportVersion: 2.19.2-0ubuntu4 Architecture: amd64 Date: Sat Nov 7 17:15:18 2015 ExecutablePath: /usr/lib/bluetooth/bluetoothd InstallationDate: Installed on 2015-06-02 (158 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20349 ProcCmdline: /usr/lib/bluetooth/bluetoothd ProcEnviron: - LANG=en_US.UTF-8 - PATH=(custom, no user) + LANG=en_US.UTF-8 + PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-17-generic.efi.signed root=/dev/mapper/btree-ubuntu ro rootflags=subvol=@ noprompt quiet splash vt.handoff=7 SegvAnalysis: - Segfault happened at: 0x7fef0124a51f : movdqu (%rdi),%xmm0 - PC (0x7fef0124a51f) ok - source "(%rdi)" (0x) not located in a known VMA region (needed readable region)! - destination "%xmm0" ok + Segfault happened at: 0x7fef0124a51f : movdqu (%rdi),%xmm0 + PC (0x7fef0124a51f) ok + source "(%rdi)" (0x) not located in a known VMA region (needed readable region)! + destination "%xmm0" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: bluez StacktraceTop: - rawmemchr () at ../sysdeps/x86_64/rawmemchr.S:37 - _IO_str_init_static_internal (sf=sf@entry=0x7fffafd6df50, ptr=ptr@entry=0x0, size=size@entry=0, pstart=pstart@entry=0x0) at strops.c:44 - _IO_vsscanf (string=0x0, format=0x7fef0062eacc "%hx:%hx:%hx", args=args@entry=0x7fffafd6e078) at iovsscanf.c:43 - __sscanf (s=, format=) at sscanf.c:32 - ?? () from /usr/lib/x86_64-linux-gnu/bluetooth/plugins/sixaxis.so + rawmemchr () at ../sysdeps/x86_64/rawmemchr.S:37 + _IO_str_init_static_internal (sf=sf@entry=0x7fffafd6df50, ptr=ptr@entry=0x0, size=size@entry=0, pstart=pstart@entry=0x0) at strops.c:44 + _IO_vsscanf (string=0x0, format=0x7fef0062eacc "%hx:%hx:%hx", args=args@entry=0x7fffafd6e078) at iovsscanf.c:43 + __sscanf (s=, format=) at sscanf.c:32 + ?? () from /usr/lib/x86_64-linux-gnu/bluetooth/plugins/sixaxis.so Title: bluetoothd crashed with SIGSEGV in rawmemchr() UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: Upgraded to xenial on 2015-10-28 (11 days ago) UserGroups: - + dmi.bios.date: 07/22/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN40WW(V3.00) dmi.board.asset.tag: 31900058Std dmi.board.name: Lenovo Y50-70 Touch dmi.board.vendor: LENOVO dmi.board.version: 31900058Std dmi.chassis.asset.tag: 31900058Std dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 Touch dmi.modalias: dmi:bvnLENOVO:bvr9ECN40WW(V3.00):bd07/22/2015:svnLENOVO:pn20349:pvrLenovoY50-70Touch:rvnLENOVO:rnLenovoY50-70Touch:rvr31900058Std:cvnLENOVO:ct10:cvrLenovoY50-70Touch: dmi.product.name: 20349 dmi.product.version: Lenovo Y50-70 Touch dmi.sys.vendor: LENOVO hciconfig: - hci0:Type: BR/EDR Bus: USB - BD Address: 28:B2:BD:0B:11:97 ACL MTU: 1021:5 SCO MTU: 96:5 - UP RUNNING - RX bytes:691 acl:0 sco:0 events:47 errors:0 - TX bytes:2182 acl:0 sco:0 commands:47 errors:0 + hci0:Type: BR/EDR Bus: USB + BD Address: 28:B2:BD:0B:11:97 ACL MTU: 1021:5 SCO MTU: 96:5 + UP RUNNING + RX bytes:691 acl:0 sco:0 events:47 errors:0 + TX bytes:2182 acl:0 sco:0 commands:47 errors:0 ** Tags added: yakkety 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/1514166 Title: bluetoothd crashed with SIGSEGV in rawmemchr() Status in bluez package in Ubuntu: Confirmed Bug description: bluetoothd crashed with SIGSEGV in rawmemchr() https://errors.ubuntu.com/problem/f0eca11dfcb228bd89caa34e5f9b5529151c0c88 ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: bluez 5.35-0ubuntu2 ProcVersionSignature: Ubuntu 4.2.0-17.21-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 NonfreeKernelModules: openafs ApportVersion: 2.19.2-0ubuntu4 Architecture: amd64 Date: Sat Nov 7 17:15:18 2015 ExecutablePath: /usr/lib/bluetooth/bluetoothd InstallationDate: Installed on 2015-06-02 (158 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20349 ProcCmdline: /usr/lib/bluetooth/bluetoothd ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-1
[Touch-packages] [Bug 1689432] Re: bluetoothd crashed with SIGABRT due to memory corruption "corrupted double-linked list"
** Changed in: bluez (Ubuntu) Status: New => Confirmed -- 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/1689432 Title: bluetoothd crashed with SIGABRT due to memory corruption "corrupted double-linked list" Status in bluez package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.43-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/a0e2acef0b29137ce41d624db0f08893d7ee9636 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1689432/+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 1689433] Re: bluetoothd crashed with SIGSEGV in memcpy from bacpy from bt_cancel_discovery from browse_request_cancel from device_remove
** Changed in: bluez (Ubuntu) Status: New => Confirmed -- 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/1689433 Title: bluetoothd crashed with SIGSEGV in memcpy from bacpy from bt_cancel_discovery from browse_request_cancel from device_remove Status in bluez package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.43-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/28b7383d0b74f23dd092e097248686dd0be7300e contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1689433/+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 1689452] Re: /usr/lib/bluetooth/bluetoothd:11:avdtp_sep_set_state:avdtp_abort_resp:avdtp_parse_resp:session_cb:g_main_dispatch
** Changed in: bluez (Ubuntu) Importance: Undecided => High ** Summary changed: - /usr/lib/bluetooth/bluetoothd:11:avdtp_sep_set_state:avdtp_abort_resp:avdtp_parse_resp:session_cb:g_main_dispatch + bluetoothd crashed with SIGSEGV in avdtp_sep_set_state from avdtp_abort_resp from avdtp_parse_resp from session_cb from g_main_dispatch -- 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/1689452 Title: bluetoothd crashed with SIGSEGV in avdtp_sep_set_state from avdtp_abort_resp from avdtp_parse_resp from session_cb from g_main_dispatch Status in bluez package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.43-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/108dd760fb9f1f5bb12e155ffad01ee758816f36 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1689452/+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 1689449] Re: /usr/lib/bluetooth/obexd:ERROR:gobex/gobex-header.c:110:g_obex_header_encode: assertion failed (utf16_len + 3 == header->hlen): (133 == 129)
*** This bug is a duplicate of bug 1689441 *** https://bugs.launchpad.net/bugs/1689441 ** Changed in: bluez (Ubuntu) Importance: Undecided => Medium ** Summary changed: - /usr/lib/bluetooth/obexd:ERROR:gobex/gobex-header.c:110:g_obex_header_encode: assertion failed (utf16_len + 3 == header->hlen): (133 == 129) + obexd crashed with SIGABRT - ERROR:gobex/gobex-header.c:110:g_obex_header_encode: assertion failed (utf16_len + 3 == header->hlen): (133 == 129) ** This bug has been marked a duplicate of bug 1689441 obexd crashed with SIGABRT - ERROR:gobex/gobex-header.c:110:g_obex_header_encode: assertion failed (utf16_len + 3 == header->hlen): (77 == 75) -- 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/1689449 Title: obexd crashed with SIGABRT - ERROR:gobex/gobex- header.c:110:g_obex_header_encode: assertion failed (utf16_len + 3 == header->hlen): (133 == 129) Status in bluez package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.37-0ubuntu5, the problem page at https://errors.ubuntu.com/problem/060b3b179119e491500d8eecff12e0621be085ea contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1689449/+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 1689459] [NEW] /usr/lib/bluetooth/bluetoothd:11:ext_confirm:server_cb:g_main_dispatch:g_main_context_dispatch:g_main_context_iterate
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.43-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/79fb1a2bdca7699121c71f94778d0ac7688ef891 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: xenial 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/1689459 Title: /usr/lib/bluetooth/bluetoothd:11:ext_confirm:server_cb:g_main_dispatch:g_main_context_dispatch:g_main_context_iterate Status in bluez package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.43-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/79fb1a2bdca7699121c71f94778d0ac7688ef891 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1689459/+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 1689458] [NEW] /usr/lib/bluetooth/bluetoothd:11:device_svc_resolved:search_cb:browse_cb:connect_watch:g_main_dispatch
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.41-0ubuntu3, the problem page at https://errors.ubuntu.com/problem/3d579b15e5040bb946caffbf22f9ee8124529197 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: xenial 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/1689458 Title: /usr/lib/bluetooth/bluetoothd:11:device_svc_resolved:search_cb:browse_cb:connect_watch:g_main_dispatch Status in bluez package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.41-0ubuntu3, the problem page at https://errors.ubuntu.com/problem/3d579b15e5040bb946caffbf22f9ee8124529197 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1689458/+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 1689455] [NEW] /usr/lib/bluetooth/obexd:11:_dbus_header_cache_check:_dbus_header_get_field_basic:dbus_message_get_sender:dbus_message_new_method_return:abort_complete
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.37-0ubuntu5, the problem page at https://errors.ubuntu.com/problem/5d1def138d65e6306ef3c03b6ee79217e5ed7fe3 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: xenial -- 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/1689455 Title: /usr/lib/bluetooth/obexd:11:_dbus_header_cache_check:_dbus_header_get_field_basic:dbus_message_get_sender:dbus_message_new_method_return:abort_complete Status in bluez package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.37-0ubuntu5, the problem page at https://errors.ubuntu.com/problem/5d1def138d65e6306ef3c03b6ee79217e5ed7fe3 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1689455/+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 1689457] [NEW] /usr/lib/bluetooth/bluetoothd:11:g_io_channel_shutdown:attio_cleanup:browse_request_cancel:device_remove:adapter_remove
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.43-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/e2c5f3e07125e7ba40af3a44a3b07adb73420030 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: wily xenial 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/1689457 Title: /usr/lib/bluetooth/bluetoothd:11:g_io_channel_shutdown:attio_cleanup:browse_request_cancel:device_remove:adapter_remove Status in bluez package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.43-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/e2c5f3e07125e7ba40af3a44a3b07adb73420030 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1689457/+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 1689456] [NEW] /usr/lib/bluetooth/obexd:11:main_arena:xfer_complete:transfer_complete:transfer_abort_response:handle_response
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.37-0ubuntu5, the problem page at https://errors.ubuntu.com/problem/e5556f928fe0308e14b1e88856fa73749f61ce2a contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: xenial -- 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/1689456 Title: /usr/lib/bluetooth/obexd:11:main_arena:xfer_complete:transfer_complete:transfer_abort_response:handle_response Status in bluez package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.37-0ubuntu5, the problem page at https://errors.ubuntu.com/problem/e5556f928fe0308e14b1e88856fa73749f61ce2a contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1689456/+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 1689464] [NEW] /usr/lib/bluetooth/bluetoothd:11:g_io_channel_shutdown:avctp_channel_destroy:avctp_disconnected:avctp_set_state:session_cb
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.43-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/a562dd1c2698bbeadb296ebb39c238522aeb3600 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: wily xenial 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/1689464 Title: /usr/lib/bluetooth/bluetoothd:11:g_io_channel_shutdown:avctp_channel_destroy:avctp_disconnected:avctp_set_state:session_cb Status in bluez package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.43-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/a562dd1c2698bbeadb296ebb39c238522aeb3600 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1689464/+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 1689466] [NEW] /usr/lib/bluetooth/bluetoothd:11:encrypt_notify:g_io_unix_dispatch:g_main_dispatch:g_main_context_dispatch:g_main_context_iterate
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.37-0ubuntu5, the problem page at https://errors.ubuntu.com/problem/51e27350205066877db9eee38a77d852664027f7 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: wily xenial -- 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/1689466 Title: /usr/lib/bluetooth/bluetoothd:11:encrypt_notify:g_io_unix_dispatch:g_main_dispatch:g_main_context_dispatch:g_main_context_iterate Status in bluez package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.37-0ubuntu5, the problem page at https://errors.ubuntu.com/problem/51e27350205066877db9eee38a77d852664027f7 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1689466/+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 1689460] [NEW] /usr/lib/bluetooth/bluetoothd:11:avdtp_unref:setup_free:setup_unref:transport_cb:accept_cb
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.43-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/b07fc39aa06a535581fad194d445c76f189364c1 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: wily xenial yakkety 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/1689460 Title: /usr/lib/bluetooth/bluetoothd:11:avdtp_unref:setup_free:setup_unref:transport_cb:accept_cb Status in bluez package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.43-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/b07fc39aa06a535581fad194d445c76f189364c1 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1689460/+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 1689465] [NEW] /usr/lib/bluetooth/bluetoothd:*** Error in `/usr/lib/bluetooth/bluetoothd': malloc(): smallbin double linked list corrupted: ADDR ***
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.43-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/2cd62ac3fc6977ec03346b6dedcb8edee13c8014 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: wily xenial 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/1689465 Title: /usr/lib/bluetooth/bluetoothd:*** Error in `/usr/lib/bluetooth/bluetoothd': malloc(): smallbin double linked list corrupted: ADDR *** Status in bluez package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.43-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/2cd62ac3fc6977ec03346b6dedcb8edee13c8014 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1689465/+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 1689461] [NEW] /usr/lib/bluetooth/bluetoothd:11:g_io_channel_shutdown:attio_cleanup:browse_request_cancel:device_remove:btd_adapter_remove_device
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.37-0ubuntu5, the problem page at https://errors.ubuntu.com/problem/732cce930e4db100b0ec943638e1029f4655fbf9 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: xenial -- 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/1689461 Title: /usr/lib/bluetooth/bluetoothd:11:g_io_channel_shutdown:attio_cleanup:browse_request_cancel:device_remove:btd_adapter_remove_device Status in bluez package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.37-0ubuntu5, the problem page at https://errors.ubuntu.com/problem/732cce930e4db100b0ec943638e1029f4655fbf9 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1689461/+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 1689463] [NEW] /usr/lib/bluetooth/bluetoothd:11:ba2str:update_bredr_services:browse_cb:search_completed_cb:sdp_process
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.43-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/34f2d57d9e4087da25c8712bf1ea880ced7a88b6 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: yakkety 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/1689463 Title: /usr/lib/bluetooth/bluetoothd:11:ba2str:update_bredr_services:browse_cb:search_completed_cb:sdp_process Status in bluez package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.43-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/34f2d57d9e4087da25c8712bf1ea880ced7a88b6 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1689463/+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 1689462] [NEW] /usr/lib/bluetooth/bluetoothd:11:release_stream:g_slist_foreach:connection_lost:disconnect_timeout:g_timeout_dispatch
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.41-0ubuntu3, the problem page at https://errors.ubuntu.com/problem/d9aec0cc9617e42fcd64fe69270d8f758e39c453 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: xenial 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/1689462 Title: /usr/lib/bluetooth/bluetoothd:11:release_stream:g_slist_foreach:connection_lost:disconnect_timeout:g_timeout_dispatch Status in bluez package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.41-0ubuntu3, the problem page at https://errors.ubuntu.com/problem/d9aec0cc9617e42fcd64fe69270d8f758e39c453 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1689462/+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 1689447] Re: bluetoothd crashed with SIGSEGV in browse_request_cancel from device_remove from btd_adapter_remove_device from remove_device from process_message
** Summary changed: - /usr/lib/bluetooth/bluetoothd:11:browse_request_cancel:device_remove:btd_adapter_remove_device:remove_device:process_message + bluetoothd crashed with SIGSEGV in browse_request_cancel from device_remove from btd_adapter_remove_device from remove_device from process_message ** Changed in: bluez (Ubuntu) Importance: Undecided => Medium -- 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/1689447 Title: bluetoothd crashed with SIGSEGV in browse_request_cancel from device_remove from btd_adapter_remove_device from remove_device from process_message Status in bluez package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.41-0ubuntu3, the problem page at https://errors.ubuntu.com/problem/656d6f19e98b8adc45e8c6f3218c6dcea039315a contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1689447/+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 1689448] Re: /usr/lib/bluetooth/bluetoothd:11:avdtp_stream_set_transport:transport_cb:accept_cb:g_main_dispatch:g_main_context_dispatch
** Changed in: bluez (Ubuntu) Importance: Undecided => High ** Summary changed: - /usr/lib/bluetooth/bluetoothd:11:avdtp_stream_set_transport:transport_cb:accept_cb:g_main_dispatch:g_main_context_dispatch + bluetoothd crashed with SIGSEGV in avdtp_stream_set_transport transport_cb accept_cb g_main_dispatch g_main_context_dispatch -- 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/1689448 Title: bluetoothd crashed with SIGSEGV in avdtp_stream_set_transport transport_cb accept_cb g_main_dispatch g_main_context_dispatch Status in bluez package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.43-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/74228037aee5c1e95c18d26533f63d5396d48e3e contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1689448/+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 1689451] Re: bluetoothd crashed with SIGSEGV in queue_remove_if from bt_att_unregister_disconnect from attio_cleanup from browse_request_cancel from device_remove
** Summary changed: - /usr/lib/bluetooth/bluetoothd:11:queue_remove_if:bt_att_unregister_disconnect:attio_cleanup:browse_request_cancel:device_remove + bluetoothd crashed with SIGSEGV in queue_remove_if from bt_att_unregister_disconnect from attio_cleanup from browse_request_cancel from device_remove ** Changed in: bluez (Ubuntu) Importance: Undecided => High -- 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/1689451 Title: bluetoothd crashed with SIGSEGV in queue_remove_if from bt_att_unregister_disconnect from attio_cleanup from browse_request_cancel from device_remove Status in bluez package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.41-0ubuntu3, the problem page at https://errors.ubuntu.com/problem/686eb99935548ae15300b85caf382f510d0c074f contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1689451/+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 1689450] Re: /usr/lib/bluetooth/bluetoothd:11:strlen:_dbus_string_init_const:_dbus_check_is_valid_path:dbus_message_iter_append_basic:dev_property_get_adapter
** Changed in: bluez (Ubuntu) Importance: Undecided => High ** Summary changed: - /usr/lib/bluetooth/bluetoothd:11:strlen:_dbus_string_init_const:_dbus_check_is_valid_path:dbus_message_iter_append_basic:dev_property_get_adapter + bluetoothd crashed with SIGSEGV in strlen from _dbus_string_init_const from _dbus_check_is_valid_path from dbus_message_iter_append_basic from dev_property_get_adapter -- 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/1689450 Title: bluetoothd crashed with SIGSEGV in strlen from _dbus_string_init_const from _dbus_check_is_valid_path from dbus_message_iter_append_basic from dev_property_get_adapter Status in bluez package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.43-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/e95b08689734fed39c54cb1173dccd71279f1c1a contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1689450/+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 1689444] Re: /usr/bin/gatttool:11:g_source_remove:interactive:main
** Changed in: bluez (Ubuntu) Importance: Undecided => Medium ** Summary changed: - /usr/bin/gatttool:11:g_source_remove:interactive:main + gatttool crashed with SIGSEGV in g_source_remove from interactive from main -- 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/1689444 Title: gatttool crashed with SIGSEGV in g_source_remove from interactive from main Status in bluez package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.37-0ubuntu5, the problem page at https://errors.ubuntu.com/problem/edf93ae590df75746d783c408e6b879a4111444a contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1689444/+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 1689441] Re: obexd crashed with SIGABRT - ERROR:gobex/gobex-header.c:110:g_obex_header_encode: assertion failed (utf16_len + 3 == header->hlen): (77 == 75)
** Summary changed: - /usr/lib/bluetooth/obexd:ERROR:gobex/gobex-header.c:110:g_obex_header_encode: assertion failed (utf16_len + 3 == header->hlen): (77 == 75) + obexd crashed with SIGABRT - ERROR:gobex/gobex-header.c:110:g_obex_header_encode: assertion failed (utf16_len + 3 == header->hlen): (77 == 75) ** Changed in: bluez (Ubuntu) Importance: Undecided => Medium -- 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/1689441 Title: obexd crashed with SIGABRT - ERROR:gobex/gobex- header.c:110:g_obex_header_encode: assertion failed (utf16_len + 3 == header->hlen): (77 == 75) Status in bluez package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.37-0ubuntu5, the problem page at https://errors.ubuntu.com/problem/eba4dce1246a1f2b6202414791cee579566ae3dc contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1689441/+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 1689442] Re: bluetoothd crashed with SIGSEGV in btd_service_connecting_complete from control_connect_cb from connect_cb from g_main_dispatch from g_main_context_dispatch
** Summary changed: - /usr/lib/bluetooth/bluetoothd:11:btd_service_connecting_complete:control_connect_cb:connect_cb:g_main_dispatch:g_main_context_dispatch + bluetoothd crashed with SIGSEGV in btd_service_connecting_complete from control_connect_cb from connect_cb from g_main_dispatch from g_main_context_dispatch ** Changed in: bluez (Ubuntu) Importance: Undecided => High -- 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/1689442 Title: bluetoothd crashed with SIGSEGV in btd_service_connecting_complete from control_connect_cb from connect_cb from g_main_dispatch from g_main_context_dispatch Status in bluez package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.43-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/fffbe12b82b8b2181e3dc736bea0a598f3b61042 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1689442/+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 1689446] Re: bluetoothd crashed with SIGSEGV in malloc_consolidate from _int_malloc from _int_realloc from __GI___libc_realloc from dbus_realloc
** Summary changed: - /usr/lib/bluetooth/bluetoothd:11:malloc_consolidate:_int_malloc:_int_realloc:__GI___libc_realloc:dbus_realloc + bluetoothd crashed with SIGSEGV in malloc_consolidate from _int_malloc from _int_realloc from __GI___libc_realloc from dbus_realloc ** Changed in: bluez (Ubuntu) Importance: Undecided => Medium -- 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/1689446 Title: bluetoothd crashed with SIGSEGV in malloc_consolidate from _int_malloc from _int_realloc from __GI___libc_realloc from dbus_realloc Status in bluez package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.37-0ubuntu5, the problem page at https://errors.ubuntu.com/problem/7b313fd07b77a23c80ecbe44098ca4f1086407da contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1689446/+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 1689443] Re: bluetoothd crahed with SIGSEGV in g_io_channel_unref from control_connect_cb from connect_cb from g_main_dispatch from g_main_context_dispatch
** Summary changed: - /usr/lib/bluetooth/bluetoothd:11:g_io_channel_unref:control_connect_cb:connect_cb:g_main_dispatch:g_main_context_dispatch + bluetoothd crahed with SIGSEGV in g_io_channel_unref from control_connect_cb from connect_cb from g_main_dispatch from g_main_context_dispatch ** Summary changed: - bluetoothd crahed with SIGSEGV in g_io_channel_unref from control_connect_cb from connect_cb from g_main_dispatch from g_main_context_dispatch + bluetoothd crashed with SIGSEGV in g_io_channel_unref from control_connect_cb from connect_cb from g_main_dispatch from g_main_context_dispatch ** Changed in: bluez (Ubuntu) Importance: Undecided => High -- 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/1689443 Title: bluetoothd crashed with SIGSEGV in g_io_channel_unref from control_connect_cb from connect_cb from g_main_dispatch from g_main_context_dispatch Status in bluez package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.43-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/60e9f362576651ff41d2c58e273c79aa15824ad8 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1689443/+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 1689445] Re: bluetoothd crashed with SIGSEGV in timeout_cb from timeout_callback from g_timeout_dispatch from g_main_dispatch from g_main_context_dispatch
** Summary changed: - /usr/lib/bluetooth/bluetoothd:11:timeout_cb:timeout_callback:g_timeout_dispatch:g_main_dispatch:g_main_context_dispatch + bluetoothd crashed with SIGSEGV in timeout_cb from timeout_callback from g_timeout_dispatch from g_main_dispatch from g_main_context_dispatch ** Changed in: bluez (Ubuntu) Importance: Undecided => High -- 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/1689445 Title: bluetoothd crashed with SIGSEGV in timeout_cb from timeout_callback from g_timeout_dispatch from g_main_dispatch from g_main_context_dispatch Status in bluez package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.43-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/b959171c4183443c43f641033bf8efcdee964438 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1689445/+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 1689435] Re: bluetoothd crashed with SIGSEGV in browse_cb from search_completed_cb from sdp_process from search_process_cb from g_main_dispatch
** Summary changed: - /usr/lib/bluetooth/bluetoothd:11:browse_cb:search_completed_cb:sdp_process:search_process_cb:g_main_dispatch + bluetoothd crashed with SIGSEGV in browse_cb from search_completed_cb from sdp_process from search_process_cb from g_main_dispatch ** Changed in: bluez (Ubuntu) Importance: Undecided => High -- 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/1689435 Title: bluetoothd crashed with SIGSEGV in browse_cb from search_completed_cb from sdp_process from search_process_cb from g_main_dispatch Status in bluez package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.43-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/257c18b3cbc69a5ebb4fc9e4efa0f5564822daf0 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1689435/+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 1689436] Re: bluetoothd crashed with SIGABRT due to heap corruption "double free or corruption (fasttop)"
** Summary changed: - /usr/lib/bluetooth/bluetoothd:*** Error in `/usr/lib/bluetooth/bluetoothd': double free or corruption (fasttop): ADDR *** + bluetoothd crashed with SIGABRT due to heap corruption "double free or corruption (fasttop)" ** Changed in: bluez (Ubuntu) Importance: Undecided => High -- 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/1689436 Title: bluetoothd crashed with SIGABRT due to heap corruption "double free or corruption (fasttop)" Status in bluez package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.43-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/2522ea5604a622769e532f07ec9ecab43310bf23 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1689436/+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 1689433] Re: bluetoothd crashed with SIGSEGV in memcpy from bacpy from bt_cancel_discovery from browse_request_cancel from device_remove
** Summary changed: - /usr/lib/bluetooth/bluetoothd:11:memcpy:bacpy:bt_cancel_discovery:browse_request_cancel:device_remove + bluetoothd crashed with SIGSEGV in memcpy from bacpy from bt_cancel_discovery from browse_request_cancel from device_remove ** Changed in: bluez (Ubuntu) Importance: Undecided => High -- 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/1689433 Title: bluetoothd crashed with SIGSEGV in memcpy from bacpy from bt_cancel_discovery from browse_request_cancel from device_remove Status in bluez package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.43-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/28b7383d0b74f23dd092e097248686dd0be7300e contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1689433/+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 1689434] Re: bluetoothd crashed with SIGSEGV in g_io_channel_unix_get_fd from bt_io_get_type from bt_io_get from report_map_read_cb from read_blob_helper
Dropping severity to medium until such time as it is known to still occur in zesty (or yakkety). ** Summary changed: - /usr/lib/bluetooth/bluetoothd:11:g_io_channel_unix_get_fd:bt_io_get_type:bt_io_get:report_map_read_cb:read_blob_helper + bluetoothd crashed with SIGSEGV in g_io_channel_unix_get_fd from bt_io_get_type from bt_io_get from report_map_read_cb from read_blob_helper ** Changed in: bluez (Ubuntu) Importance: Undecided => High ** Changed in: bluez (Ubuntu) Importance: High => Medium -- 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/1689434 Title: bluetoothd crashed with SIGSEGV in g_io_channel_unix_get_fd from bt_io_get_type from bt_io_get from report_map_read_cb from read_blob_helper Status in bluez package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.37-0ubuntu5, the problem page at https://errors.ubuntu.com/problem/1d86a1a385ca39a20c12d294fc4a014f8bc60c16 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1689434/+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 1689440] Re: bluetoothd crashed with SIGSEGV in btd_device_get_service from policy_connect_sink from g_timeout_dispatch from g_main_dispatch from g_main_context_dispatch
** Summary changed: - /usr/lib/bluetooth/bluetoothd:11:btd_device_get_service:policy_connect_sink:g_timeout_dispatch:g_main_dispatch:g_main_context_dispatch + bluetoothd crashed with SIGSEGV in btd_device_get_service from policy_connect_sink from g_timeout_dispatch from g_main_dispatch from g_main_context_dispatch ** Changed in: bluez (Ubuntu) Importance: Undecided => High -- 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/1689440 Title: bluetoothd crashed with SIGSEGV in btd_device_get_service from policy_connect_sink from g_timeout_dispatch from g_main_dispatch from g_main_context_dispatch Status in bluez package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.43-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/685c44346c1666e27b097b86cba784459205e32d contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1689440/+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 1689437] Re: bluetoothd crashed with SIGSEGV in __rawmemchr_ia32 from _IO_str_init_static_internal from _IO_vsscanf from __sscanf from get_supported_device
** Summary changed: - /usr/lib/bluetooth/bluetoothd:11:__rawmemchr_ia32:_IO_str_init_static_internal:_IO_vsscanf:__sscanf:get_supported_device + bluetoothd crashed with SIGSEGV in __rawmemchr_ia32 from _IO_str_init_static_internal from _IO_vsscanf from __sscanf from get_supported_device ** Changed in: bluez (Ubuntu) Importance: Undecided => High -- 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/1689437 Title: bluetoothd crashed with SIGSEGV in __rawmemchr_ia32 from _IO_str_init_static_internal from _IO_vsscanf from __sscanf from get_supported_device Status in bluez package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.43-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/5fc18b3add1fab2dc0d0676d7680aa9f1324f9fa contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1689437/+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 1689438] Re: bluetoothd crashed with SIGABRT in free(): invalid pointer
** Summary changed: - /usr/lib/bluetooth/bluetoothd:*** Error in `/usr/lib/bluetooth/bluetoothd': free(): invalid pointer: ADDR *** + bluetoothd crashed with SIGABRT in free(): invalid pointer ** Changed in: bluez (Ubuntu) Importance: Undecided => High -- 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/1689438 Title: bluetoothd crashed with SIGABRT in free(): invalid pointer Status in bluez package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.43-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/9690f8797e673b0fa8359647ae193ab8d0a62d3e contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1689438/+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 1689439] Re: bluetoothd crashed with SIGSEGV in set_ct_player from player_remove from g_slist_foreach from g_slist_free_full from avrcp_get_media_player_list_rsp
** Summary changed: - /usr/lib/bluetooth/bluetoothd:11:set_ct_player:player_remove:g_slist_foreach:g_slist_free_full:avrcp_get_media_player_list_rsp + bluetoothd crashed with SIGSEGV in set_ct_player from player_remove from g_slist_foreach from g_slist_free_full from avrcp_get_media_player_list_rsp ** Changed in: bluez (Ubuntu) Importance: Undecided => Medium -- 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/1689439 Title: bluetoothd crashed with SIGSEGV in set_ct_player from player_remove from g_slist_foreach from g_slist_free_full from avrcp_get_media_player_list_rsp Status in bluez package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.37-0ubuntu5, the problem page at https://errors.ubuntu.com/problem/58231706469af54317bae2161b3fc6e0b066388d contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1689439/+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 1689432] Re: bluetoothd crashed with SIGABRT due to memory corruption "corrupted double-linked list"
** Summary changed: - /usr/lib/bluetooth/bluetoothd:*** Error in `/usr/lib/bluetooth/bluetoothd': corrupted double-linked list: ADDR *** + bluetoothd crashed with SIGABRT due to memory corruption "corrupted double-linked list" ** Changed in: bluez (Ubuntu) Importance: Undecided => High -- 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/1689432 Title: bluetoothd crashed with SIGABRT due to memory corruption "corrupted double-linked list" Status in bluez package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.43-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/a0e2acef0b29137ce41d624db0f08893d7ee9636 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1689432/+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 1689449] [NEW] /usr/lib/bluetooth/obexd:ERROR:gobex/gobex-header.c:110:g_obex_header_encode: assertion failed (utf16_len + 3 == header->hlen): (133 == 129)
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.37-0ubuntu5, the problem page at https://errors.ubuntu.com/problem/060b3b179119e491500d8eecff12e0621be085ea contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: xenial -- 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/1689449 Title: /usr/lib/bluetooth/obexd:ERROR:gobex/gobex- header.c:110:g_obex_header_encode: assertion failed (utf16_len + 3 == header->hlen): (133 == 129) Status in bluez package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.37-0ubuntu5, the problem page at https://errors.ubuntu.com/problem/060b3b179119e491500d8eecff12e0621be085ea contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1689449/+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 1689443] [NEW] /usr/lib/bluetooth/bluetoothd:11:g_io_channel_unref:control_connect_cb:connect_cb:g_main_dispatch:g_main_context_dispatch
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.43-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/60e9f362576651ff41d2c58e273c79aa15824ad8 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: wily xenial yakkety 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/1689443 Title: /usr/lib/bluetooth/bluetoothd:11:g_io_channel_unref:control_connect_cb:connect_cb:g_main_dispatch:g_main_context_dispatch Status in bluez package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.43-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/60e9f362576651ff41d2c58e273c79aa15824ad8 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1689443/+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 1689445] [NEW] /usr/lib/bluetooth/bluetoothd:11:timeout_cb:timeout_callback:g_timeout_dispatch:g_main_dispatch:g_main_context_dispatch
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.43-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/b959171c4183443c43f641033bf8efcdee964438 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: yakkety 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/1689445 Title: /usr/lib/bluetooth/bluetoothd:11:timeout_cb:timeout_callback:g_timeout_dispatch:g_main_dispatch:g_main_context_dispatch Status in bluez package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.43-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/b959171c4183443c43f641033bf8efcdee964438 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1689445/+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 1689444] [NEW] /usr/bin/gatttool:11:g_source_remove:interactive:main
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.37-0ubuntu5, the problem page at https://errors.ubuntu.com/problem/edf93ae590df75746d783c408e6b879a4111444a contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: wily xenial -- 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/1689444 Title: /usr/bin/gatttool:11:g_source_remove:interactive:main Status in bluez package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.37-0ubuntu5, the problem page at https://errors.ubuntu.com/problem/edf93ae590df75746d783c408e6b879a4111444a contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1689444/+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 1689447] [NEW] /usr/lib/bluetooth/bluetoothd:11:browse_request_cancel:device_remove:btd_adapter_remove_device:remove_device:process_message
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.41-0ubuntu3, the problem page at https://errors.ubuntu.com/problem/656d6f19e98b8adc45e8c6f3218c6dcea039315a contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: wily xenial yakkety -- 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/1689447 Title: /usr/lib/bluetooth/bluetoothd:11:browse_request_cancel:device_remove:btd_adapter_remove_device:remove_device:process_message Status in bluez package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.41-0ubuntu3, the problem page at https://errors.ubuntu.com/problem/656d6f19e98b8adc45e8c6f3218c6dcea039315a contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1689447/+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 1689448] [NEW] /usr/lib/bluetooth/bluetoothd:11:avdtp_stream_set_transport:transport_cb:accept_cb:g_main_dispatch:g_main_context_dispatch
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.43-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/74228037aee5c1e95c18d26533f63d5396d48e3e contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: wily xenial yakkety 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/1689448 Title: /usr/lib/bluetooth/bluetoothd:11:avdtp_stream_set_transport:transport_cb:accept_cb:g_main_dispatch:g_main_context_dispatch Status in bluez package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.43-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/74228037aee5c1e95c18d26533f63d5396d48e3e contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1689448/+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 1689446] [NEW] /usr/lib/bluetooth/bluetoothd:11:malloc_consolidate:_int_malloc:_int_realloc:__GI___libc_realloc:dbus_realloc
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.37-0ubuntu5, the problem page at https://errors.ubuntu.com/problem/7b313fd07b77a23c80ecbe44098ca4f1086407da contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: xenial -- 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/1689446 Title: /usr/lib/bluetooth/bluetoothd:11:malloc_consolidate:_int_malloc:_int_realloc:__GI___libc_realloc:dbus_realloc Status in bluez package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.37-0ubuntu5, the problem page at https://errors.ubuntu.com/problem/7b313fd07b77a23c80ecbe44098ca4f1086407da contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1689446/+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 1689451] [NEW] /usr/lib/bluetooth/bluetoothd:11:queue_remove_if:bt_att_unregister_disconnect:attio_cleanup:browse_request_cancel:device_remove
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.41-0ubuntu3, the problem page at https://errors.ubuntu.com/problem/686eb99935548ae15300b85caf382f510d0c074f contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: wily xenial yakkety 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/1689451 Title: /usr/lib/bluetooth/bluetoothd:11:queue_remove_if:bt_att_unregister_disconnect:attio_cleanup:browse_request_cancel:device_remove Status in bluez package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.41-0ubuntu3, the problem page at https://errors.ubuntu.com/problem/686eb99935548ae15300b85caf382f510d0c074f contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1689451/+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 1689450] [NEW] /usr/lib/bluetooth/bluetoothd:11:strlen:_dbus_string_init_const:_dbus_check_is_valid_path:dbus_message_iter_append_basic:dev_property_get_adapter
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.43-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/e95b08689734fed39c54cb1173dccd71279f1c1a contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: xenial yakkety 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/1689450 Title: /usr/lib/bluetooth/bluetoothd:11:strlen:_dbus_string_init_const:_dbus_check_is_valid_path:dbus_message_iter_append_basic:dev_property_get_adapter Status in bluez package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.43-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/e95b08689734fed39c54cb1173dccd71279f1c1a contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1689450/+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 1689452] [NEW] /usr/lib/bluetooth/bluetoothd:11:avdtp_sep_set_state:avdtp_abort_resp:avdtp_parse_resp:session_cb:g_main_dispatch
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.43-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/108dd760fb9f1f5bb12e155ffad01ee758816f36 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: wily xenial yakkety 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/1689452 Title: /usr/lib/bluetooth/bluetoothd:11:avdtp_sep_set_state:avdtp_abort_resp:avdtp_parse_resp:session_cb:g_main_dispatch Status in bluez package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.43-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/108dd760fb9f1f5bb12e155ffad01ee758816f36 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1689452/+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 1689432] [NEW] bluetoothd crashed with SIGABRT due to memory corruption "corrupted double-linked list"
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.43-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/a0e2acef0b29137ce41d624db0f08893d7ee9636 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. ** Affects: bluez (Ubuntu) Importance: High Status: New ** Tags: wily xenial yakkety 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/1689432 Title: bluetoothd crashed with SIGABRT due to memory corruption "corrupted double-linked list" Status in bluez package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.43-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/a0e2acef0b29137ce41d624db0f08893d7ee9636 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1689432/+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 1689434] [NEW] bluetoothd crashed with SIGSEGV in g_io_channel_unix_get_fd from bt_io_get_type from bt_io_get from report_map_read_cb from read_blob_helper
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.37-0ubuntu5, the problem page at https://errors.ubuntu.com/problem/1d86a1a385ca39a20c12d294fc4a014f8bc60c16 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. ** Affects: bluez (Ubuntu) Importance: High Status: New ** Tags: xenial -- 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/1689434 Title: bluetoothd crashed with SIGSEGV in g_io_channel_unix_get_fd from bt_io_get_type from bt_io_get from report_map_read_cb from read_blob_helper Status in bluez package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.37-0ubuntu5, the problem page at https://errors.ubuntu.com/problem/1d86a1a385ca39a20c12d294fc4a014f8bc60c16 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1689434/+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