[Kernel-packages] [Bug 1625805] Re: arm64: history daemon dereferences a rogue pointer
Per the discussion above, this could be anywhere (qtmir, untiy8) not necessarily in unity8 per se. It does seem that this is specific to "unity8 on dragonboard" though. We know that... - mir-kiosk examples works on dragonboard - unity8 works on arm64 m10 ** Summary changed: - arm64: history daemon dereferences a rogue pointer + dragonboard: history daemon dereferences a rogue pointer -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1625805 Title: dragonboard: history daemon dereferences a rogue pointer Status in Snappy: New Status in linux package in Ubuntu: Invalid Status in unity8 package in Ubuntu: New Bug description: we are running the unity8 session snap on amd64 without any problems. to setup and reproduce the problem follow the "on Dragonboard" section of https://docs.google.com/document/d/1o-jKITqUxRsujmN3OwRj3wRnn6dgblKuvrhKjeN8-Wc You can also find the panic signature at line 3276 of the attached syslog. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1625805/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1625805] Re: arm64: history daemon dereferences a rogue pointer
** Also affects: unity8 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1625805 Title: dragonboard: history daemon dereferences a rogue pointer Status in Snappy: New Status in linux package in Ubuntu: Invalid Status in unity8 package in Ubuntu: New Bug description: we are running the unity8 session snap on amd64 without any problems. to setup and reproduce the problem follow the "on Dragonboard" section of https://docs.google.com/document/d/1o-jKITqUxRsujmN3OwRj3wRnn6dgblKuvrhKjeN8-Wc You can also find the panic signature at line 3276 of the attached syslog. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1625805/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1625805] Re: arm64 kernel panic for l2 mmu with unity8 session snap (& deb as well)
** Summary changed: - arm64 kernel panic for l2 mmu with unity8 session snap + arm64 kernel panic for l2 mmu with unity8 session snap (& deb as well) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1625805 Title: arm64 kernel panic for l2 mmu with unity8 session snap (& deb as well) Status in Snappy: New Status in linux package in Ubuntu: Confirmed Bug description: we are running the unity8 session snap on amd64 without any problems. to setup and reproduce the problem follow the "on Dragonboard" section of https://docs.google.com/document/d/1o-jKITqUxRsujmN3OwRj3wRnn6dgblKuvrhKjeN8-Wc You can also find the panic signature at line 3276 of the attached syslog. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1625805/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1625805] Re: arm64 kernel panic for l2 mmu with unity8 session snap
is there any update to this bug? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1625805 Title: arm64 kernel panic for l2 mmu with unity8 session snap Status in Snappy: New Status in linux package in Ubuntu: Confirmed Bug description: we are running the unity8 session snap on amd64 without any problems. to setup and reproduce the problem follow the "on Dragonboard" section of https://docs.google.com/document/d/1o-jKITqUxRsujmN3OwRj3wRnn6dgblKuvrhKjeN8-Wc You can also find the panic signature at line 3276 of the attached syslog. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1625805/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1625805] Re: arm64 kernel panic for l2 mmu with unity8 session snap
@ppisati - didi you need anything else? ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1625805 Title: arm64 kernel panic for l2 mmu with unity8 session snap Status in Snappy: New Status in linux package in Ubuntu: Confirmed Bug description: we are running the unity8 session snap on amd64 without any problems. to setup and reproduce the problem follow the "on Dragonboard" section of https://docs.google.com/document/d/1o-jKITqUxRsujmN3OwRj3wRnn6dgblKuvrhKjeN8-Wc You can also find the panic signature at line 3276 of the attached syslog. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1625805/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1625805] Re: arm64 kernel panic for l2 mmu with unity8 session snap
@ppisati - if you have a classic deb based filesystem that is Xenial based, add the ppa:ci-train-ppa-service/stable-phone-overlay (update/upgrade), then you can simply apt-get install unity8-desktop-session-mir. Once that is installed, you can toggle between unity8 & unity7 by clicking the ubuntu-logo icon just in the top-right corner of the password entry box on the greeter/lock-screen to your session. here's a doc for any other questions. https://docs.google.com/document/d/1Io3pQvzyBQIpZi2n_hfseNsVOo4LH-BjtNhmdWNijEc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1625805 Title: arm64 kernel panic for l2 mmu with unity8 session snap Status in Snappy: New Status in linux package in Ubuntu: Incomplete Bug description: we are running the unity8 session snap on amd64 without any problems. to setup and reproduce the problem follow the "on Dragonboard" section of https://docs.google.com/document/d/1o-jKITqUxRsujmN3OwRj3wRnn6dgblKuvrhKjeN8-Wc You can also find the panic signature at line 3276 of the attached syslog. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1625805/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1625805] Re: arm64 kernel panic for l2 mmu with unity8 session snap
@ppisati sorry about that, must've had too many tabs open. Corrected the link and shared the doc with you as well. ** Description changed: we are running the unity8 session snap on amd64 without any problems. - to setup and reproduce the problem follow the "on Dragonboard" section of https://docs.google.com/document/d/1Io3pQvzyBQIpZi2n_hfseNsVOo4LH-BjtNhmdWNijEc + to setup and reproduce the problem follow the "on Dragonboard" section of + https://docs.google.com/document/d/1o-jKITqUxRsujmN3OwRj3wRnn6dgblKuvrhKjeN8-Wc You can also find the panic signature at line 3276 of the attached syslog. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1625805 Title: arm64 kernel panic for l2 mmu with unity8 session snap Status in Snappy: New Status in linux package in Ubuntu: Incomplete Bug description: we are running the unity8 session snap on amd64 without any problems. to setup and reproduce the problem follow the "on Dragonboard" section of https://docs.google.com/document/d/1o-jKITqUxRsujmN3OwRj3wRnn6dgblKuvrhKjeN8-Wc You can also find the panic signature at line 3276 of the attached syslog. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1625805/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1625805] Re: arm64 kernel panic for l2 mmu with unity8 session snap
so to be clear, this on ubuntu-core dragonboard image from the beta images -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1625805 Title: arm64 kernel panic for l2 mmu with unity8 session snap Status in Snappy: New Status in linux package in Ubuntu: Incomplete Bug description: we are running the unity8 session snap on amd64 without any problems. to setup and reproduce the problem follow the "on Dragonboard" section of https://docs.google.com/document/d/1Io3pQvzyBQIpZi2n_hfseNsVOo4LH-BjtNhmdWNijEc You can also find the panic signature at line 3276 of the attached syslog. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1625805/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1625805] Re: arm64 kernel panic for l2 mmu with unity8 session snap
@ogra actually we do! we all lucked out, recently (like within the last month) someone somewhere turned on gallium/freedreno drivers for our mesa builds. So i've got the full stack, i've already run the mir- server/client snap on it with no problems (really need to blog that) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1625805 Title: arm64 kernel panic for l2 mmu with unity8 session snap Status in Snappy: New Status in linux package in Ubuntu: Incomplete Bug description: we are running the unity8 session snap on amd64 without any problems. to setup and reproduce the problem follow the "on Dragonboard" section of https://docs.google.com/document/d/1Io3pQvzyBQIpZi2n_hfseNsVOo4LH-BjtNhmdWNijEc You can also find the panic signature at line 3276 of the attached syslog. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1625805/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1625805] Re: arm64 kernel panic for l2 mmu with unity8 session snap
** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1625805 Title: arm64 kernel panic for l2 mmu with unity8 session snap Status in Snappy: New Status in linux package in Ubuntu: New Bug description: we are running the unity8 session snap on amd64 without any problems. to setup and reproduce the problem follow the "on Dragonboard" section of https://docs.google.com/document/d/1Io3pQvzyBQIpZi2n_hfseNsVOo4LH-BjtNhmdWNijEc You can also find the panic signature at line 3276 of the attached syslog. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1625805/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1580768] [NEW] bluetooth keyboard flashes in ubuntu-system-settings
Public bug reported: on latest rc-proposed for frieza seeing the following 1. connect bt mouse, no problem 2. turn on bt keyboard (logitech k480) 3. click sync 4. u-s-s spinner goes expect: to see keyboard icon in list and availble to click on actual: keyboard icon flashes for just a moment, then disappears, very consistent once in this state ** Affects: bluez (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1580768 Title: bluetooth keyboard flashes in ubuntu-system-settings Status in bluez package in Ubuntu: New Bug description: on latest rc-proposed for frieza seeing the following 1. connect bt mouse, no problem 2. turn on bt keyboard (logitech k480) 3. click sync 4. u-s-s spinner goes expect: to see keyboard icon in list and availble to click on actual: keyboard icon flashes for just a moment, then disappears, very consistent once in this state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1580768/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1552371] Re: Unexpected display on
** Changed in: canonical-devices-system-image Assignee: Michał Sawicz (saviq) => Stephen M. Webb (bregma) ** Also affects: mir (Ubuntu) Importance: Undecided Status: New ** Also affects: mir Importance: Undecided Status: New ** Changed in: mir Milestone: None => 0.23.0 ** Changed in: mir Assignee: (unassigned) => Andreas Pokorny (andreas-pokorny) ** Changed in: mir (Ubuntu) Assignee: (unassigned) => Andreas Pokorny (andreas-pokorny) ** Changed in: canonical-devices-system-image Milestone: 11 => 12 ** Changed in: unity-system-compositor (Ubuntu) Assignee: (unassigned) => Alexandros Frantzis (afrantzis) ** Changed in: unity-system-compositor Assignee: (unassigned) => Alexandros Frantzis (afrantzis) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1552371 Title: Unexpected display on Status in Canonical System Image: Confirmed Status in Mir: New Status in Unity System Compositor: New Status in bluez package in Ubuntu: Confirmed Status in mir package in Ubuntu: New Status in unity-system-compositor package in Ubuntu: Confirmed Bug description: NOTE: kgunn suggests this bug be about 1) not 2) here 1) I have been noticing my phone and tablet occasionally turning on without interaction. Several times with my phone in my pocket I found it in the emergency call UI I also see the tablet display turn on while lying idle on the desk. Freiza & Arale 2) I have reproduced one case such that turning on a BT device (headset) causes the phone to light up and display the volume slider. Similarly turning on the BT keyboard while the tablet screen is off caused the display to turn on.These may be as intended. I suspect other BT events can similarly resume the device and/or turn on the display if it happens to be awake due to the 5 min polling timer. The proximity sensor is also not honored when this happens, if its covered the screen still comes on. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1552371/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1552371] Re: Unexpected display on
** Description changed: NOTE: kgunn suggests this bug be about 1) not 2) here 1) I have been noticing my phone and tablet occasionally turning on without interaction. Several times with my phone in my pocket I found it in the emergency call UI - I also see the tablet display turn on while lying idle on the desk. + I also see the tablet display turn on while lying idle on the desk. Freiza & Arale 2) I have reproduced one case such that turning on a BT device (headset) causes the phone to light up and display the volume slider. Similarly turning on the BT keyboard while the tablet screen is off caused the display to turn on.These may be as intended. I suspect other BT events can similarly resume the device and/or turn on the display if it happens to be awake due to the 5 min polling timer. The proximity sensor is also not honored when this happens, if its covered the screen still comes on. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1552371 Title: Unexpected display on Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: New Status in unity-system-compositor package in Ubuntu: New Bug description: NOTE: kgunn suggests this bug be about 1) not 2) here 1) I have been noticing my phone and tablet occasionally turning on without interaction. Several times with my phone in my pocket I found it in the emergency call UI I also see the tablet display turn on while lying idle on the desk. Freiza & Arale 2) I have reproduced one case such that turning on a BT device (headset) causes the phone to light up and display the volume slider. Similarly turning on the BT keyboard while the tablet screen is off caused the display to turn on.These may be as intended. I suspect other BT events can similarly resume the device and/or turn on the display if it happens to be awake due to the 5 min polling timer. The proximity sensor is also not honored when this happens, if its covered the screen still comes on. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1552371/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1552371] Re: Unexpected display on
>Fix 1: I think the policy for screen management is simple, > never turn the display on if proximity is detected, it should > not be specific to SMS or calls. So you are saying we should have the proximity sensor on all the time ? I disagree, first that's a power drain. Second, people will complain about the screen blanking off just interacting with the device. The right answer is to get the policy correct in the first place and filter the events properly into those that you want to turn on the display and those you don't. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1552371 Title: Unexpected display on Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: New Status in unity-system-compositor package in Ubuntu: New Bug description: NOTE: kgunn suggests this bug be about 1) not 2) here 1) I have been noticing my phone and tablet occasionally turning on without interaction. Several times with my phone in my pocket I found it in the emergency call UI I also see the tablet display turn on while lying idle on the desk. 2) I have reproduced one case such that turning on a BT device (headset) causes the phone to light up and display the volume slider. Similarly turning on the BT keyboard while the tablet screen is off caused the display to turn on.These may be as intended. I suspect other BT events can similarly resume the device and/or turn on the display if it happens to be awake due to the 5 min polling timer. The proximity sensor is also not honored when this happens, if its covered the screen still comes on. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1552371/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1552371] Re: Unexpected display on
@pat - also does the screen dim/blank at after expected expiry in the case of #1) ? and second, same question in the case of #2) ? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1552371 Title: Unexpected display on Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: New Status in unity-system-compositor package in Ubuntu: New Bug description: NOTE: kgunn suggests this bug be about 1) not 2) here 1) I have been noticing my phone and tablet occasionally turning on without interaction. Several times with my phone in my pocket I found it in the emergency call UI I also see the tablet display turn on while lying idle on the desk. 2) I have reproduced one case such that turning on a BT device (headset) causes the phone to light up and display the volume slider. Similarly turning on the BT keyboard while the tablet screen is off caused the display to turn on.These may be as intended. I suspect other BT events can similarly resume the device and/or turn on the display if it happens to be awake due to the 5 min polling timer. The proximity sensor is also not honored when this happens, if its covered the screen still comes on. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1552371/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1552371] Re: Bluetooth connection turns on the device
It seems like there is 1 bug and then 1 potential bug/feature depending based on the original description 1) actual bug - display turning on by itself (btw, i know this happens with Flo/N7 as well) 2) feature - bt devices are input, and we do want the screen to wake up on keypress or mouse move. I would propose we keep this bug to be about #1) If we feel something else needs to happen with #2) please spawn another bug - i worry a little with the suggestion to use the proximity sensor, eats battery and creates yet another complicated wrinkle in the display blanking policy. Also, we've kicked off a powerd rewrite to help consolidate policy - i would propose if we do want to address #2) let's do it as part of the powerd rewrite. ** Description changed: + NOTE: kgunn suggests this bug be about 1) not 2) here + + 1) I have been noticing my phone and tablet occasionally turning on without interaction. Several times with my phone in my pocket I found it in the emergency call UI I also see the tablet display turn on while lying idle on the desk. - I have reproduced one case such that turning on a BT device (headset) - causes the phone to light up and display the volume slider. Similarly - turning on the BT keyboard while the tablet screen is off caused the - display to turn on.These may be as intended. + 2) + I have reproduced one case such that turning on a BT device (headset) causes the phone to light up and display the volume slider. Similarly turning on the BT keyboard while the tablet screen is off caused the display to turn on.These may be as intended. I suspect other BT events can similarly resume the device and/or turn on the display if it happens to be awake due to the 5 min polling timer. The proximity sensor is also not honored when this happens, if its covered the screen still comes on. ** Summary changed: - Bluetooth connection turns on the device + Unexpected display on -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1552371 Title: Unexpected display on Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: New Status in unity-system-compositor package in Ubuntu: New Bug description: NOTE: kgunn suggests this bug be about 1) not 2) here 1) I have been noticing my phone and tablet occasionally turning on without interaction. Several times with my phone in my pocket I found it in the emergency call UI I also see the tablet display turn on while lying idle on the desk. 2) I have reproduced one case such that turning on a BT device (headset) causes the phone to light up and display the volume slider. Similarly turning on the BT keyboard while the tablet screen is off caused the display to turn on.These may be as intended. I suspect other BT events can similarly resume the device and/or turn on the display if it happens to be awake due to the 5 min polling timer. The proximity sensor is also not honored when this happens, if its covered the screen still comes on. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1552371/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1550050] Re: repeating phantom key when bt disconnects
** Changed in: canonical-pocket-desktop Importance: Undecided => Critical ** Changed in: canonical-pocket-desktop Assignee: (unassigned) => kevin gunn (kgunn72) ** Changed in: mir Importance: Undecided => Critical ** Changed in: mir (Ubuntu) Importance: Undecided => Critical -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1550050 Title: repeating phantom key when bt disconnects Status in Canonical System Image: Confirmed Status in Canonical Pocket Desktop: New Status in Mir: In Progress Status in bluez package in Ubuntu: Confirmed Status in mir package in Ubuntu: In Progress Bug description: Every now and then when having bt mouse/keyboard connected - you will see when selecting a text box there is a repeating character (there is no specific character, but always repeats) It seems to be related somehow to bt devices disconnecting the only cure is a reboot This was reproduced by turning off the keyboard while holding down a key. We suspect the key up event is never delivered. This mimics the case where the BT connection drops off momentarily or perhaps an event is missed over the BT connection. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1550050/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1550050] [NEW] repeating phantom key when bt disconnects
Public bug reported: using mako, every no and then when having bt mouse/keyboard connected - you will see when selecting a text box there is a repeating character (there is no specific character, but always repeats) it seems to be related somehow to bt devices disconnecting the only cure is a reboot ** Affects: canonical-devices-system-image Importance: Undecided Assignee: John McAleely (john.mcaleely) Status: New ** Affects: canonical-pocket-desktop Importance: Undecided Status: New ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Also affects: canonical-devices-system-image Importance: Undecided Status: New ** Also affects: bluez (Ubuntu) Importance: Undecided Status: New ** Changed in: canonical-devices-system-image Assignee: (unassigned) => John McAleely (john.mcaleely) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1550050 Title: repeating phantom key when bt disconnects Status in Canonical System Image: New Status in Canonical Pocket Desktop: New Status in bluez package in Ubuntu: New Bug description: using mako, every no and then when having bt mouse/keyboard connected - you will see when selecting a text box there is a repeating character (there is no specific character, but always repeats) it seems to be related somehow to bt devices disconnecting the only cure is a reboot To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1550050/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1481136] Re: Bluetooth mouse fails to reconnect after suspend + resume
I'm not sure if this needs a new bug or if i am correct in adding this information. But I made a quick video to show exactly the problem i'm seeing https://www.youtube.com/watch?v=Mkql0gSq1RQ hope that helps. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1481136 Title: Bluetooth mouse fails to reconnect after suspend + resume Status in Canonical System Image: Confirmed Status in Canonical Pocket Desktop: In Progress Status in bluez package in Ubuntu: In Progress Bug description: I can connect the bluetooth mouse (Logitech M557) using the GUI and the device works properly. However, after suspend and resume the mouse fails to reconnect. It does "attempt" to reconnect, in that I see the padlock flashes momentarily onto the bluetooth icon on the toolbar applet. Similarly, if the Bluetooth Settings dialog is open the devices flashes momentarily bold as if connected. Both effects happen whenever the mouse is used (movement or mouse click) but the device does not connect. I have a workaround, which is to remove the device and pair it using the command line as follows: sudo bluez-test-device remove 00:1F:20:EF:B1:00 sudo bluez-simple-agent hci0 00:1F:20:EF:B1:00 remove sudo bluez-simple-agent hci0 00:1F:20:EF:B1:00 sudo bluez-test-device trusted 00:1F:20:EF:B1:00 yes sudo bluez-test-input connect 00:1F:20:EF:B1:00 Once paired manually in this manner the devices appears in the Bluetooth Settings as normal an successfully reconnects when resuming. I'm submitted a new bug as this is similar but not the same as other bugs reported. In particular the workarounds presented in other bugs do not work for me and the workaround I'm using was not suggested in other cases. Thanks. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: bluez 4.101-0ubuntu25 ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Aug 4 09:53:18 2015 InstallationDate: Installed on 2014-01-23 (557 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: TOSHIBA KIRA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-25-generic.efi.signed root=UUID=a0fdb0ee-bbeb-4872-8e79-1a785c304e91 ro libata.force=noncq vesafb.invalid=1 splash quiet nopat vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/15/2013 dmi.bios.vendor: TOSHIBA dmi.bios.version: Version 1.30 dmi.board.asset.tag: 00 dmi.board.name: KIRA dmi.board.vendor: TOSHIBA dmi.board.version: Version A0 dmi.chassis.asset.tag: 00 dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: Version 1.0 dmi.modalias: dmi:bvnTOSHIBA:bvrVersion1.30:bd02/15/2013:svnTOSHIBA:pnKIRA:pvrPSU7FA-00T00K:rvnTOSHIBA:rnKIRA:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0: dmi.product.name: KIRA dmi.product.version: PSU7FA-00T00K dmi.sys.vendor: TOSHIBA hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: B4:B6:76:C4:A2:88 ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN RX bytes:587136 acl:36542 sco:0 events:271 errors:0 TX bytes:2913 acl:109 sco:0 commands:81 errors:0 mtime.conffile..etc.bluetooth.main.conf: 2015-08-01T14:24:23.630880 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1481136/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1544254] [NEW] connected bt mouse/kybd get disconnected/not in "connect when active" list
Public bug reported: So I've been running ubuntu-pd on Nexus4 over a few days and began noticing this. 1. connect bt mouse and keyboard 2. connect to external monitor 3. use device for extended period of time sometimes the devices will appear to disconnect, as well as be forgotten. I can't tell if this is in conjunction with the screen blanking or not I've even run into the kybd being forgotten, while the mouse was remembered. here's my devices info [bluetooth]# paired-devices Device 34:88:5D:24:05:61 Logitech Keyboard K480 Device F0:65:DD:AA:04:8B HP Bluetooth Mouse X4000b [bluetooth]# info 34:88:5D:24:05:61 Device 34:88:5D:24:05:61 Name: Logitech Keyboard K480 Alias: Logitech Keyboard K480 Class: 0x002540 Icon: input-keyboard Paired: yes Trusted: yes Blocked: no Connected: yes LegacyPairing: yes UUID: Service Discovery Serve.. (1000--1000-8000-00805f9b34fb) UUID: Human Interface Device... (1124--1000-8000-00805f9b34fb) UUID: PnP Information (1200--1000-8000-00805f9b34fb) Modalias: usb:v046DpB330d2800 [bluetooth]# info F0:65:DD:AA:04:8B Device F0:65:DD:AA:04:8B Name: HP Bluetooth Mouse X4000b Alias: HP Bluetooth Mouse X4000b Class: 0x002580 Icon: input-mouse Paired: yes Trusted: yes Blocked: no Connected: yes LegacyPairing: no UUID: Service Discovery Serve.. (1000--1000-8000-00805f9b34fb) UUID: Human Interface Device... (1124--1000-8000-00805f9b34fb) UUID: PnP Information (1200--1000-8000-00805f9b34fb) Modalias: usb:v03F0p024Cd0103 [bluetooth]# ** Affects: canonical-devices-system-image Importance: Undecided Status: New ** Affects: canonical-pocket-desktop Importance: Undecided Status: New ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Also affects: bluez (Ubuntu) Importance: Undecided Status: New ** Also affects: canonical-devices-system-image Importance: Undecided Status: New ** Description changed: - So I've been running ubuntu-pd over a few days and began noticing this. + So I've been running ubuntu-pd on Nexus4 over a few days and began + noticing this. 1. connect bt mouse and keyboard 2. connect to external monitor 3. use device for extended period of time - sometimes the devices will appear to disconnect as well as be forgotten. + sometimes the devices will appear to disconnect, as well as be forgotten. I can't tell if this is in conjunction with the screen blanking or not I've even run into the kybd being forgotten, while the mouse was - remembered + remembered. here's my devices info [bluetooth]# paired-devices Device 34:88:5D:24:05:61 Logitech Keyboard K480 Device F0:65:DD:AA:04:8B HP Bluetooth Mouse X4000b [bluetooth]# info 34:88:5D:24:05:61 Device 34:88:5D:24:05:61 - Name: Logitech Keyboard K480 - Alias: Logitech Keyboard K480 - Class: 0x002540 - Icon: input-keyboard - Paired: yes - Trusted: yes - Blocked: no - Connected: yes - LegacyPairing: yes - UUID: Service Discovery Serve.. (1000--1000-8000-00805f9b34fb) - UUID: Human Interface Device... (1124--1000-8000-00805f9b34fb) - UUID: PnP Information (1200--1000-8000-00805f9b34fb) - Modalias: usb:v046DpB330d2800 + Name: Logitech Keyboard K480 + Alias: Logitech Keyboard K480 + Class: 0x002540 + Icon: input-keyboard + Paired: yes + Trusted: yes + Blocked: no + Connected: yes + LegacyPairing: yes + UUID: Service Discovery Serve.. (1000--1000-8000-00805f9b34fb) + UUID: Human Interface Device... (1124--1000-8000-00805f9b34fb) + UUID: PnP Information (1200--1000-8000-00805f9b34fb) + Modalias: usb:v046DpB330d2800 [bluetooth]# info F0:65:DD:AA:04:8B Device F0:65:DD:AA:04:8B - Name: HP Bluetooth Mouse X4000b - Alias: HP Bluetooth Mouse X4000b - Class: 0x002580 - Icon: input-mouse - Paired: yes - Trusted: yes - Blocked: no - Connected: yes - LegacyPairing: no - UUID: Service Discovery Serve.. (1000--1000-8000-00805f9b34fb) - UUID: Human Interface Device... (1124--1000-8000-00805f9b34fb) - UUID: PnP Information (1200--1000-8000-00805f9b34fb) - Modalias: usb:v03F0p024Cd0103 + Name: HP Bluetooth Mouse X4000b + Alias: HP Bluetooth Mouse X4000b + Class: 0x002580 + Icon: input-mouse + Paired: yes + Trusted: yes + Blocked: no + Connected: yes + LegacyPairing: no + UUID: Service Discovery Serve.. (1000--1000-8000-00805f9b34fb) + UUID: Human Interface Device... (1124--1000-8000-00805f9b34fb) + UUID: PnP Information (1200--1000-8000-00805f9b34fb) + Modalias: usb:v03F0p024Cd0103 [bluetooth]# -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchp
[Kernel-packages] [Bug 1540731] Re: SocketMessenger::update_session_creds() fails to get client PID, causing "[ FAILED ] PromptSessionClientAPI.client_pid_is_associated_with_session"
so currently holding up promotion of mir - so, just noting here (mainly for
alan) we're disabling this test on mir 0.19.1 rel, if this bug gets fixed, we
should reinstate test if we do a 0.19.2
aiui, we've left it active on devel - so might be fixed by time we do mir0.20
and this will be moot
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1540731
Title:
SocketMessenger::update_session_creds() fails to get client PID,
causing "[ FAILED ]
PromptSessionClientAPI.client_pid_is_associated_with_session"
Status in GLibC:
New
Status in Mir:
Confirmed
Status in linux package in Ubuntu:
In Progress
Bug description:
Since updating to the 4.4.0-2 kernel recvmsg() fails SCM_CREDENTIALS
request with EOPNOTSUPP.
This manifests as a test failure in Mir:
[ RUN ] PromptSessionClientAPI.client_pid_is_associated_with_session
unknown file: Failure
Test case:
#include
#include
#include
#include
#include
#include
#include
int main()
{
enum { server, client, size };
int socket_fd[size];
int const opt = 1;
assert(socketpair(AF_LOCAL, SOCK_STREAM, 0, socket_fd) == 0);
char const msg[] = "A random message";
send(socket_fd[client], msg, sizeof msg, MSG_DONTWAIT | MSG_NOSIGNAL);
assert(setsockopt(socket_fd[server], SOL_SOCKET, SO_PASSCRED,
&opt, sizeof(opt)) != -1);
union {
struct cmsghdr cmh;
char control[CMSG_SPACE(sizeof(ucred))];
} control_un;
control_un.cmh.cmsg_len = CMSG_LEN(sizeof(ucred));
control_un.cmh.cmsg_level = SOL_SOCKET;
control_un.cmh.cmsg_type = SCM_CREDENTIALS;
msghdr msgh;
msgh.msg_name = NULL;
msgh.msg_namelen = 0;
msgh.msg_iov = NULL;
msgh.msg_iovlen = 0;
msgh.msg_control = control_un.control;
msgh.msg_controllen = sizeof(control_un.control);
errno = 0;
if (recvmsg(socket_fd[server], &msgh, MSG_PEEK) == -1)
{
printf("Error: %s\n", strerror(errno));
exit(EXIT_FAILURE);
}
else
{
printf("Success!\n");
exit(EXIT_SUCCESS);
}
}
To manage notifications about this bug go to:
https://bugs.launchpad.net/glibc/+bug/1540731/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1540731] Re: SocketMessenger::update_session_creds() fails to get client PID, causing "[ FAILED ] PromptSessionClientAPI.client_pid_is_associated_with_session"
this is effecting mir-snap work as well
** Changed in: linux (Ubuntu)
Importance: High => Critical
** Changed in: mir
Status: Confirmed => Opinion
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1540731
Title:
SocketMessenger::update_session_creds() fails to get client PID,
causing "[ FAILED ]
PromptSessionClientAPI.client_pid_is_associated_with_session"
Status in GLibC:
New
Status in Mir:
Opinion
Status in linux package in Ubuntu:
Confirmed
Bug description:
Since updating to the 4.4.0-2 kernel recvmsg() fails SCM_CREDENTIALS
request with EOPNOTSUPP.
This manifests as a test failure in Mir:
[ RUN ] PromptSessionClientAPI.client_pid_is_associated_with_session
unknown file: Failure
Test case:
#include
#include
#include
#include
#include
#include
#include
int main()
{
enum { server, client, size };
int socket_fd[size];
int const opt = 1;
assert(socketpair(AF_LOCAL, SOCK_STREAM, 0, socket_fd) == 0);
char const msg[] = "A random message";
send(socket_fd[client], msg, sizeof msg, MSG_DONTWAIT | MSG_NOSIGNAL);
assert(setsockopt(socket_fd[server], SOL_SOCKET, SO_PASSCRED,
&opt, sizeof(opt)) != -1);
union {
struct cmsghdr cmh;
char control[CMSG_SPACE(sizeof(ucred))];
} control_un;
control_un.cmh.cmsg_len = CMSG_LEN(sizeof(ucred));
control_un.cmh.cmsg_level = SOL_SOCKET;
control_un.cmh.cmsg_type = SCM_CREDENTIALS;
msghdr msgh;
msgh.msg_name = NULL;
msgh.msg_namelen = 0;
msgh.msg_iov = NULL;
msgh.msg_iovlen = 0;
msgh.msg_control = control_un.control;
msgh.msg_controllen = sizeof(control_un.control);
errno = 0;
if (recvmsg(socket_fd[server], &msgh, MSG_PEEK) == -1)
{
printf("Error: %s\n", strerror(errno));
exit(EXIT_FAILURE);
}
else
{
printf("Success!\n");
exit(EXIT_SUCCESS);
}
}
To manage notifications about this bug go to:
https://bugs.launchpad.net/glibc/+bug/1540731/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1481136] Re: Bluetooth mouse fails to reconnect after suspend + resume
I'm seeing this with an HP bt mouse and a logitech keyboard. I'd say 30% of the time. I was testing N7 convergence pretty heavily yesterday. I was having to hit "forget device" then reconnect. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1481136 Title: Bluetooth mouse fails to reconnect after suspend + resume Status in Canonical System Image: Confirmed Status in canonical-pocket-desktop: In Progress Status in bluez package in Ubuntu: In Progress Bug description: I can connect the bluetooth mouse (Logitech M557) using the GUI and the device works properly. However, after suspend and resume the mouse fails to reconnect. It does "attempt" to reconnect, in that I see the padlock flashes momentarily onto the bluetooth icon on the toolbar applet. Similarly, if the Bluetooth Settings dialog is open the devices flashes momentarily bold as if connected. Both effects happen whenever the mouse is used (movement or mouse click) but the device does not connect. I have a workaround, which is to remove the device and pair it using the command line as follows: sudo bluez-test-device remove 00:1F:20:EF:B1:00 sudo bluez-simple-agent hci0 00:1F:20:EF:B1:00 remove sudo bluez-simple-agent hci0 00:1F:20:EF:B1:00 sudo bluez-test-device trusted 00:1F:20:EF:B1:00 yes sudo bluez-test-input connect 00:1F:20:EF:B1:00 Once paired manually in this manner the devices appears in the Bluetooth Settings as normal an successfully reconnects when resuming. I'm submitted a new bug as this is similar but not the same as other bugs reported. In particular the workarounds presented in other bugs do not work for me and the workaround I'm using was not suggested in other cases. Thanks. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: bluez 4.101-0ubuntu25 ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Aug 4 09:53:18 2015 InstallationDate: Installed on 2014-01-23 (557 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: TOSHIBA KIRA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-25-generic.efi.signed root=UUID=a0fdb0ee-bbeb-4872-8e79-1a785c304e91 ro libata.force=noncq vesafb.invalid=1 splash quiet nopat vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/15/2013 dmi.bios.vendor: TOSHIBA dmi.bios.version: Version 1.30 dmi.board.asset.tag: 00 dmi.board.name: KIRA dmi.board.vendor: TOSHIBA dmi.board.version: Version A0 dmi.chassis.asset.tag: 00 dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: Version 1.0 dmi.modalias: dmi:bvnTOSHIBA:bvrVersion1.30:bd02/15/2013:svnTOSHIBA:pnKIRA:pvrPSU7FA-00T00K:rvnTOSHIBA:rnKIRA:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0: dmi.product.name: KIRA dmi.product.version: PSU7FA-00T00K dmi.sys.vendor: TOSHIBA hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: B4:B6:76:C4:A2:88 ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN RX bytes:587136 acl:36542 sco:0 events:271 errors:0 TX bytes:2913 acl:109 sco:0 commands:81 errors:0 mtime.conffile..etc.bluetooth.main.conf: 2015-08-01T14:24:23.630880 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1481136/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1532989] [NEW] bluetooth device list not populating after fresh flash
Public bug reported: Every time i flash, needing to connect my bt mouse/keyboard, i open u-s-s and go to the bt icon, select it and tap on "connect a device"...little orange spinner spins...but list never populates. I have to log on to the device shell and restart indicator-bluetooth at which point the list will populate. I _think_ this is only occurring after a fresh flash, but i am not sure. ** Affects: canonical-devices-system-image Importance: High Status: New ** Affects: canonical-pocket-desktop Importance: High Status: New ** Affects: bluez (Ubuntu) Importance: High Status: New ** Affects: indicator-bluetooth (Ubuntu) Importance: High Status: New ** Also affects: canonical-devices-system-image Importance: Undecided Status: New ** Also affects: canonical-pocket-desktop Importance: Undecided Status: New ** Also affects: indicator-bluetooth (Ubuntu) Importance: Undecided Status: New ** Changed in: canonical-devices-system-image Milestone: None => ww04-2016 ** Changed in: canonical-devices-system-image Importance: Undecided => High ** Changed in: canonical-pocket-desktop Importance: Undecided => High ** Changed in: bluez (Ubuntu) Importance: Undecided => High ** Changed in: indicator-bluetooth (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1532989 Title: bluetooth device list not populating after fresh flash Status in Canonical System Image: New Status in canonical-pocket-desktop: New Status in bluez package in Ubuntu: New Status in indicator-bluetooth package in Ubuntu: New Bug description: Every time i flash, needing to connect my bt mouse/keyboard, i open u-s-s and go to the bt icon, select it and tap on "connect a device"...little orange spinner spins...but list never populates. I have to log on to the device shell and restart indicator-bluetooth at which point the list will populate. I _think_ this is only occurring after a fresh flash, but i am not sure. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1532989/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1532980] [NEW] have to "forget" device sometimes
Public bug reported: 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. ** Affects: canonical-devices-system-image Importance: High Status: New ** Affects: canonical-pocket-desktop Importance: High Status: New ** Affects: bluez (Ubuntu) Importance: High Status: New ** Also affects: bluez (Ubuntu) Importance: Undecided Status: New ** Also affects: canonical-devices-system-image Importance: Undecided Status: New ** Changed in: canonical-devices-system-image Milestone: None => ww04-2016 ** Changed in: bluez (Ubuntu) Importance: Undecided => High ** Changed in: canonical-pocket-desktop Importance: Undecided => Medium ** Changed in: canonical-devices-system-image Importance: Undecided => Medium ** Changed in: canonical-devices-system-image Importance: Medium => High ** Changed in: canonical-pocket-desktop Importance: Medium => High -- You received this bug notification because you are a member of Kernel 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: New Status in canonical-pocket-desktop: New Status in bluez package in Ubuntu: New 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/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1481136] Re: Bluetooth mouse fails to reconnect after suspend + resume
** Changed in: canonical-pocket-desktop Importance: Medium => High ** Changed in: bluez (Ubuntu) Importance: Medium => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1481136 Title: Bluetooth mouse fails to reconnect after suspend + resume Status in canonical-pocket-desktop: In Progress Status in bluez package in Ubuntu: In Progress Bug description: I can connect the bluetooth mouse (Logitech M557) using the GUI and the device works properly. However, after suspend and resume the mouse fails to reconnect. It does "attempt" to reconnect, in that I see the padlock flashes momentarily onto the bluetooth icon on the toolbar applet. Similarly, if the Bluetooth Settings dialog is open the devices flashes momentarily bold as if connected. Both effects happen whenever the mouse is used (movement or mouse click) but the device does not connect. I have a workaround, which is to remove the device and pair it using the command line as follows: sudo bluez-test-device remove 00:1F:20:EF:B1:00 sudo bluez-simple-agent hci0 00:1F:20:EF:B1:00 remove sudo bluez-simple-agent hci0 00:1F:20:EF:B1:00 sudo bluez-test-device trusted 00:1F:20:EF:B1:00 yes sudo bluez-test-input connect 00:1F:20:EF:B1:00 Once paired manually in this manner the devices appears in the Bluetooth Settings as normal an successfully reconnects when resuming. I'm submitted a new bug as this is similar but not the same as other bugs reported. In particular the workarounds presented in other bugs do not work for me and the workaround I'm using was not suggested in other cases. Thanks. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: bluez 4.101-0ubuntu25 ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Aug 4 09:53:18 2015 InstallationDate: Installed on 2014-01-23 (557 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: TOSHIBA KIRA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-25-generic.efi.signed root=UUID=a0fdb0ee-bbeb-4872-8e79-1a785c304e91 ro libata.force=noncq vesafb.invalid=1 splash quiet nopat vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/15/2013 dmi.bios.vendor: TOSHIBA dmi.bios.version: Version 1.30 dmi.board.asset.tag: 00 dmi.board.name: KIRA dmi.board.vendor: TOSHIBA dmi.board.version: Version A0 dmi.chassis.asset.tag: 00 dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: Version 1.0 dmi.modalias: dmi:bvnTOSHIBA:bvrVersion1.30:bd02/15/2013:svnTOSHIBA:pnKIRA:pvrPSU7FA-00T00K:rvnTOSHIBA:rnKIRA:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0: dmi.product.name: KIRA dmi.product.version: PSU7FA-00T00K dmi.sys.vendor: TOSHIBA hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: B4:B6:76:C4:A2:88 ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN RX bytes:587136 acl:36542 sco:0 events:271 errors:0 TX bytes:2913 acl:109 sco:0 commands:81 errors:0 mtime.conffile..etc.bluetooth.main.conf: 2015-08-01T14:24:23.630880 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-pocket-desktop/+bug/1481136/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1513450] Re: ActivityIndicators cause very high cpu usage for unity8/mir even when visible: false
spawned bug 1518418 for the governor topic ** No longer affects: linux-flo (Ubuntu) ** No longer affects: linux-mako (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-flo in Ubuntu. https://bugs.launchpad.net/bugs/1513450 Title: ActivityIndicators cause very high cpu usage for unity8/mir even when visible: false Status in Canonical System Image: Fix Released Status in canonical-pocket-desktop: Fix Released Status in Mir: Invalid Status in Online Accounts setup for Ubuntu Touch: Fix Released Status in ubuntu-system-settings package in Ubuntu: Fix Released Status in ubuntu-ui-toolkit package in Ubuntu: Fix Released Bug description: running in window mode, open u-s-s, run top unity8 running at ~40% cpu on N7 cpu freq ~1GHz no monitor attached note: testing with silo 18 of mir containing lp:~albaguirre/mir/fix-1499039 (equivalent for 0.17) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1513450/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1513450] Re: ActivityIndicators cause very high cpu usage for unity8/mir even when visible: false
** Changed in: canonical-devices-system-image Status: In Progress => Fix Released ** Changed in: ubuntu-system-settings-online-accounts Status: New => Fix Released ** Changed in: canonical-pocket-desktop Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-flo in Ubuntu. https://bugs.launchpad.net/bugs/1513450 Title: ActivityIndicators cause very high cpu usage for unity8/mir even when visible: false Status in Canonical System Image: Fix Released Status in canonical-pocket-desktop: Fix Released Status in Mir: Invalid Status in Online Accounts setup for Ubuntu Touch: Fix Released Status in ubuntu-system-settings package in Ubuntu: Fix Released Status in ubuntu-ui-toolkit package in Ubuntu: Fix Released Bug description: running in window mode, open u-s-s, run top unity8 running at ~40% cpu on N7 cpu freq ~1GHz no monitor attached note: testing with silo 18 of mir containing lp:~albaguirre/mir/fix-1499039 (equivalent for 0.17) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1513450/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1518418] [NEW] devices need governor tuning for best performance
Public bug reported: spawned from bug 1513450 as well as some investigation by tvoss devices need to be tuned to utililze the interactive governor; available method employed by android/apple is to switch to interactive when the device is picked up (sensor) or screen is unblanked this actually applies to all devices, but i could only find/link our reference device projects. ** Affects: canonical-devices-system-image Importance: High Status: New ** Affects: linux-flo (Ubuntu) Importance: Undecided Status: New ** Affects: linux-mako (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-flo (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-mako (Ubuntu) Importance: Undecided Status: New ** Description changed: - spawned from bug 1513450 + spawned from bug 1513450 as well as some investigation by tvoss devices need to be tuned to utililze the interactive governor; available method employed by android/apple is to switch to interactive when the device is picked up (sensor) or screen is unblanked + + this actually applies to all devices, but i could only find/link our + reference device projects. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-flo in Ubuntu. https://bugs.launchpad.net/bugs/1518418 Title: devices need governor tuning for best performance Status in Canonical System Image: New Status in linux-flo package in Ubuntu: New Status in linux-mako package in Ubuntu: New Bug description: spawned from bug 1513450 as well as some investigation by tvoss devices need to be tuned to utililze the interactive governor; available method employed by android/apple is to switch to interactive when the device is picked up (sensor) or screen is unblanked this actually applies to all devices, but i could only find/link our reference device projects. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1518418/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1513450] Re: ActivityIndicators cause very high cpu usage for unity8/mir even when visible: false
adding projects linux-mako & linux-flo, is it possible to change to the interactive governor by default (instead of OnDemand) also, not just for mako/flo but this is a question that should be asked/answered for all devices (arale, krillin,... as well) ** No longer affects: qtmir ** No longer affects: unity8 (Ubuntu) ** Changed in: mir Status: In Progress => Invalid ** Also affects: linux-mako (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-flo (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-flo (Ubuntu) Importance: Undecided => Critical ** Changed in: linux-mako (Ubuntu) Importance: Undecided => Critical -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-mako in Ubuntu. https://bugs.launchpad.net/bugs/1513450 Title: ActivityIndicators cause very high cpu usage for unity8/mir even when visible: false Status in Canonical System Image: In Progress Status in canonical-pocket-desktop: New Status in Mir: Invalid Status in Online Accounts setup for Ubuntu Touch: New Status in Ubuntu UI Toolkit: New Status in linux-flo package in Ubuntu: New Status in linux-mako package in Ubuntu: New Status in ubuntu-system-settings package in Ubuntu: In Progress Bug description: running in window mode, open u-s-s, run top unity8 running at ~40% cpu on N7 cpu freq ~1GHz no monitor attached note: testing with silo 18 of mir containing lp:~albaguirre/mir/fix-1499039 (equivalent for 0.17) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1513450/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1481136] Re: Bluetooth mouse fails to reconnect after suspend + resume
it's better, but i still see failure about 25% of the time ** Changed in: canonical-pocket-desktop Importance: High => Medium ** Changed in: bluez (Ubuntu) Importance: High => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1481136 Title: Bluetooth mouse fails to reconnect after suspend + resume Status in canonical-pocket-desktop: In Progress Status in bluez package in Ubuntu: In Progress Bug description: I can connect the bluetooth mouse (Logitech M557) using the GUI and the device works properly. However, after suspend and resume the mouse fails to reconnect. It does "attempt" to reconnect, in that I see the padlock flashes momentarily onto the bluetooth icon on the toolbar applet. Similarly, if the Bluetooth Settings dialog is open the devices flashes momentarily bold as if connected. Both effects happen whenever the mouse is used (movement or mouse click) but the device does not connect. I have a workaround, which is to remove the device and pair it using the command line as follows: sudo bluez-test-device remove 00:1F:20:EF:B1:00 sudo bluez-simple-agent hci0 00:1F:20:EF:B1:00 remove sudo bluez-simple-agent hci0 00:1F:20:EF:B1:00 sudo bluez-test-device trusted 00:1F:20:EF:B1:00 yes sudo bluez-test-input connect 00:1F:20:EF:B1:00 Once paired manually in this manner the devices appears in the Bluetooth Settings as normal an successfully reconnects when resuming. I'm submitted a new bug as this is similar but not the same as other bugs reported. In particular the workarounds presented in other bugs do not work for me and the workaround I'm using was not suggested in other cases. Thanks. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: bluez 4.101-0ubuntu25 ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Aug 4 09:53:18 2015 InstallationDate: Installed on 2014-01-23 (557 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: TOSHIBA KIRA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-25-generic.efi.signed root=UUID=a0fdb0ee-bbeb-4872-8e79-1a785c304e91 ro libata.force=noncq vesafb.invalid=1 splash quiet nopat vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/15/2013 dmi.bios.vendor: TOSHIBA dmi.bios.version: Version 1.30 dmi.board.asset.tag: 00 dmi.board.name: KIRA dmi.board.vendor: TOSHIBA dmi.board.version: Version A0 dmi.chassis.asset.tag: 00 dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: Version 1.0 dmi.modalias: dmi:bvnTOSHIBA:bvrVersion1.30:bd02/15/2013:svnTOSHIBA:pnKIRA:pvrPSU7FA-00T00K:rvnTOSHIBA:rnKIRA:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0: dmi.product.name: KIRA dmi.product.version: PSU7FA-00T00K dmi.sys.vendor: TOSHIBA hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: B4:B6:76:C4:A2:88 ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN RX bytes:587136 acl:36542 sco:0 events:271 errors:0 TX bytes:2913 acl:109 sco:0 commands:81 errors:0 mtime.conffile..etc.bluetooth.main.conf: 2015-08-01T14:24:23.630880 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-pocket-desktop/+bug/1481136/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1481136] Re: Bluetooth mouse fails to reconnect after suspend + resume
** Changed in: canonical-pocket-desktop Importance: Undecided => High ** Changed in: canonical-pocket-desktop Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1481136 Title: Bluetooth mouse fails to reconnect after suspend + resume Status in canonical-pocket-desktop: In Progress Status in bluez package in Ubuntu: In Progress Bug description: I can connect the bluetooth mouse (Logitech M557) using the GUI and the device works properly. However, after suspend and resume the mouse fails to reconnect. It does "attempt" to reconnect, in that I see the padlock flashes momentarily onto the bluetooth icon on the toolbar applet. Similarly, if the Bluetooth Settings dialog is open the devices flashes momentarily bold as if connected. Both effects happen whenever the mouse is used (movement or mouse click) but the device does not connect. I have a workaround, which is to remove the device and pair it using the command line as follows: sudo bluez-test-device remove 00:1F:20:EF:B1:00 sudo bluez-simple-agent hci0 00:1F:20:EF:B1:00 remove sudo bluez-simple-agent hci0 00:1F:20:EF:B1:00 sudo bluez-test-device trusted 00:1F:20:EF:B1:00 yes sudo bluez-test-input connect 00:1F:20:EF:B1:00 Once paired manually in this manner the devices appears in the Bluetooth Settings as normal an successfully reconnects when resuming. I'm submitted a new bug as this is similar but not the same as other bugs reported. In particular the workarounds presented in other bugs do not work for me and the workaround I'm using was not suggested in other cases. Thanks. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: bluez 4.101-0ubuntu25 ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Aug 4 09:53:18 2015 InstallationDate: Installed on 2014-01-23 (557 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: TOSHIBA KIRA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-25-generic.efi.signed root=UUID=a0fdb0ee-bbeb-4872-8e79-1a785c304e91 ro libata.force=noncq vesafb.invalid=1 splash quiet nopat vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/15/2013 dmi.bios.vendor: TOSHIBA dmi.bios.version: Version 1.30 dmi.board.asset.tag: 00 dmi.board.name: KIRA dmi.board.vendor: TOSHIBA dmi.board.version: Version A0 dmi.chassis.asset.tag: 00 dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: Version 1.0 dmi.modalias: dmi:bvnTOSHIBA:bvrVersion1.30:bd02/15/2013:svnTOSHIBA:pnKIRA:pvrPSU7FA-00T00K:rvnTOSHIBA:rnKIRA:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0: dmi.product.name: KIRA dmi.product.version: PSU7FA-00T00K dmi.sys.vendor: TOSHIBA hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: B4:B6:76:C4:A2:88 ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN RX bytes:587136 acl:36542 sco:0 events:271 errors:0 TX bytes:2913 acl:109 sco:0 commands:81 errors:0 mtime.conffile..etc.bluetooth.main.conf: 2015-08-01T14:24:23.630880 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-pocket-desktop/+bug/1481136/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1481136] Re: Bluetooth mouse fails to reconnect after suspend + resume
** Also affects: qtmir Importance: Undecided Status: New ** No longer affects: qtmir (Ubuntu) ** No longer affects: qtmir ** Also affects: canonical-pocket-desktop Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1481136 Title: Bluetooth mouse fails to reconnect after suspend + resume Status in canonical-pocket-desktop: New Status in bluez package in Ubuntu: Confirmed Bug description: I can connect the bluetooth mouse (Logitech M557) using the GUI and the device works properly. However, after suspend and resume the mouse fails to reconnect. It does "attempt" to reconnect, in that I see the padlock flashes momentarily onto the bluetooth icon on the toolbar applet. Similarly, if the Bluetooth Settings dialog is open the devices flashes momentarily bold as if connected. Both effects happen whenever the mouse is used (movement or mouse click) but the device does not connect. I have a workaround, which is to remove the device and pair it using the command line as follows: sudo bluez-test-device remove 00:1F:20:EF:B1:00 sudo bluez-simple-agent hci0 00:1F:20:EF:B1:00 remove sudo bluez-simple-agent hci0 00:1F:20:EF:B1:00 sudo bluez-test-device trusted 00:1F:20:EF:B1:00 yes sudo bluez-test-input connect 00:1F:20:EF:B1:00 Once paired manually in this manner the devices appears in the Bluetooth Settings as normal an successfully reconnects when resuming. I'm submitted a new bug as this is similar but not the same as other bugs reported. In particular the workarounds presented in other bugs do not work for me and the workaround I'm using was not suggested in other cases. Thanks. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: bluez 4.101-0ubuntu25 ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Aug 4 09:53:18 2015 InstallationDate: Installed on 2014-01-23 (557 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: TOSHIBA KIRA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-25-generic.efi.signed root=UUID=a0fdb0ee-bbeb-4872-8e79-1a785c304e91 ro libata.force=noncq vesafb.invalid=1 splash quiet nopat vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/15/2013 dmi.bios.vendor: TOSHIBA dmi.bios.version: Version 1.30 dmi.board.asset.tag: 00 dmi.board.name: KIRA dmi.board.vendor: TOSHIBA dmi.board.version: Version A0 dmi.chassis.asset.tag: 00 dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: Version 1.0 dmi.modalias: dmi:bvnTOSHIBA:bvrVersion1.30:bd02/15/2013:svnTOSHIBA:pnKIRA:pvrPSU7FA-00T00K:rvnTOSHIBA:rnKIRA:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0: dmi.product.name: KIRA dmi.product.version: PSU7FA-00T00K dmi.sys.vendor: TOSHIBA hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: B4:B6:76:C4:A2:88 ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN RX bytes:587136 acl:36542 sco:0 events:271 errors:0 TX bytes:2913 acl:109 sco:0 commands:81 errors:0 mtime.conffile..etc.bluetooth.main.conf: 2015-08-01T14:24:23.630880 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-pocket-desktop/+bug/1481136/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1481136] Re: Bluetooth mouse fails to reconnect after suspend + resume
touching this bug as on our unity8 windowed mode i see this as 1. go to system settings 2. select connect device 3. select mouse detected 4. select connect (put user back to bt first view) expected: to be connected result: have to go back to the mouse bt page and hit "connect" again. this is really obvious, b/c the mouse presence is being used for converting into window mode ** Also affects: qtmir (Ubuntu) Importance: Undecided Status: New ** Changed in: qtmir (Ubuntu) Status: New => Opinion ** Tags added: pd -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1481136 Title: Bluetooth mouse fails to reconnect after suspend + resume Status in bluez package in Ubuntu: Confirmed Status in qtmir package in Ubuntu: Opinion Bug description: I can connect the bluetooth mouse (Logitech M557) using the GUI and the device works properly. However, after suspend and resume the mouse fails to reconnect. It does "attempt" to reconnect, in that I see the padlock flashes momentarily onto the bluetooth icon on the toolbar applet. Similarly, if the Bluetooth Settings dialog is open the devices flashes momentarily bold as if connected. Both effects happen whenever the mouse is used (movement or mouse click) but the device does not connect. I have a workaround, which is to remove the device and pair it using the command line as follows: sudo bluez-test-device remove 00:1F:20:EF:B1:00 sudo bluez-simple-agent hci0 00:1F:20:EF:B1:00 remove sudo bluez-simple-agent hci0 00:1F:20:EF:B1:00 sudo bluez-test-device trusted 00:1F:20:EF:B1:00 yes sudo bluez-test-input connect 00:1F:20:EF:B1:00 Once paired manually in this manner the devices appears in the Bluetooth Settings as normal an successfully reconnects when resuming. I'm submitted a new bug as this is similar but not the same as other bugs reported. In particular the workarounds presented in other bugs do not work for me and the workaround I'm using was not suggested in other cases. Thanks. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: bluez 4.101-0ubuntu25 ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Aug 4 09:53:18 2015 InstallationDate: Installed on 2014-01-23 (557 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: TOSHIBA KIRA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-25-generic.efi.signed root=UUID=a0fdb0ee-bbeb-4872-8e79-1a785c304e91 ro libata.force=noncq vesafb.invalid=1 splash quiet nopat vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/15/2013 dmi.bios.vendor: TOSHIBA dmi.bios.version: Version 1.30 dmi.board.asset.tag: 00 dmi.board.name: KIRA dmi.board.vendor: TOSHIBA dmi.board.version: Version A0 dmi.chassis.asset.tag: 00 dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: Version 1.0 dmi.modalias: dmi:bvnTOSHIBA:bvrVersion1.30:bd02/15/2013:svnTOSHIBA:pnKIRA:pvrPSU7FA-00T00K:rvnTOSHIBA:rnKIRA:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0: dmi.product.name: KIRA dmi.product.version: PSU7FA-00T00K dmi.sys.vendor: TOSHIBA hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: B4:B6:76:C4:A2:88 ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN RX bytes:587136 acl:36542 sco:0 events:271 errors:0 TX bytes:2913 acl:109 sco:0 commands:81 errors:0 mtime.conffile..etc.bluetooth.main.conf: 2015-08-01T14:24:23.630880 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1481136/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1400827] Re: BlueZ crashing when connecting input channel to a keyboard
dang it...that's 2015, not 22015so few months, not 20,000 years+few months -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1400827 Title: BlueZ crashing when connecting input channel to a keyboard Status in bluez package in Ubuntu: New Bug description: On the phone, pairing a keyboard makes BlueZ crash when connecting the input channel (either by calling org.bluez.Input.Connect() on D-Bus or by pressing some keys on the keyboard to make the keyboard open the channel. In order to pair a keyboard with an Ubuntu phone, you need to either apply this branch to ubuntu-system-settings [1] or do it manually with bluez-simple-agent and dbus-send/qdbus. [1] https://code.launchpad.net/~mzanetti/ubuntu-system-settings/bt-input To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1400827/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1400827] Re: BlueZ crashing when connecting input channel to a keyboard
in order to help set priority, we're hoping to have this functionality to support convergence demonstrations ~Feb 22015 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1400827 Title: BlueZ crashing when connecting input channel to a keyboard Status in bluez package in Ubuntu: New Bug description: On the phone, pairing a keyboard makes BlueZ crash when connecting the input channel (either by calling org.bluez.Input.Connect() on D-Bus or by pressing some keys on the keyboard to make the keyboard open the channel. In order to pair a keyboard with an Ubuntu phone, you need to either apply this branch to ubuntu-system-settings [1] or do it manually with bluez-simple-agent and dbus-send/qdbus. [1] https://code.launchpad.net/~mzanetti/ubuntu-system-settings/bt-input To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1400827/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1195811] Re: nouveau: Abnormally high FPS and tearing (no vsync) on native mir demo-clients. (root caused nv kernel)
** Changed in: linux (Ubuntu) Importance: Undecided => Critical -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1195811 Title: nouveau: Abnormally high FPS and tearing (no vsync) on native mir demo-clients. (root caused nv kernel) Status in Mir: Triaged Status in “linux” package in Ubuntu: In Progress Bug description: I installed Ubuntu 13.10 (yesterday) in order to test Xmir and Mir natively (examples-clients). Xmirg worked flawlessly. The only "problem" was the duplicate mouse cursor(s). But I noticed an abnormally high FPS in some clients demo when I tested Mir natively per these instructions http://unity.ubuntu.com/mir/using_mir_on_pc.html I recorded the test case using external camera. Apologies for the quality but you will see the values. http://www.youtube.com/watch?v=zil-lRNlaks I attached an apport.log just for more info if are needed. I'm not a technical guy and I filled this report prompted by @duflu in IRC #ubuntu-mir You can read the mini conversation here. http://irclogs.ubuntu.com/2013/06/28/%23ubuntu-mir.html This test had the same results either if X only was running in VT7 (Video) or Xmir. I hope I helped... in something. Regards NikTh To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1195811/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1195811] Re: nouveau: Abnormally high FPS and tearing (no vsync) on native mir demo-clients. (root caused nv kernel)
** Summary changed: - nouveau: Abnormally high FPS and tearing (no vsync) on natively mir testing demo-clients. + nouveau: Abnormally high FPS and tearing (no vsync) on native mir demo-clients. (root caused nv kernel) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1195811 Title: nouveau: Abnormally high FPS and tearing (no vsync) on native mir demo-clients. (root caused nv kernel) Status in Mir: Triaged Status in “linux” package in Ubuntu: In Progress Bug description: I installed Ubuntu 13.10 (yesterday) in order to test Xmir and Mir natively (examples-clients). Xmirg worked flawlessly. The only "problem" was the duplicate mouse cursor(s). But I noticed an abnormally high FPS in some clients demo when I tested Mir natively per these instructions http://unity.ubuntu.com/mir/using_mir_on_pc.html I recorded the test case using external camera. Apologies for the quality but you will see the values. http://www.youtube.com/watch?v=zil-lRNlaks I attached an apport.log just for more info if are needed. I'm not a technical guy and I filled this report prompted by @duflu in IRC #ubuntu-mir You can read the mini conversation here. http://irclogs.ubuntu.com/2013/06/28/%23ubuntu-mir.html This test had the same results either if X only was running in VT7 (Video) or Xmir. I hope I helped... in something. Regards NikTh To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1195811/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
