[Touch-packages] [Bug 1845046] Re: Bluetooth headphones default to low quality headset mode and fail to switch to A2DP when selected

2020-01-26 Thread Doctor Rover
I confirm that upgrade with proposed enabled on Eoan fixed the bug for me.
I've tested it using two bluetooth audio devices: Sony WH-1000XM3 and 
Plantronics Marque M155.
Thanks to everyone involved!

-- 
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/1845046

Title:
  Bluetooth headphones default to low quality headset mode and fail to
  switch to A2DP when selected

Status in bluez package in Ubuntu:
  Fix Released
Status in bluez source package in Bionic:
  Fix Committed
Status in bluez source package in Eoan:
  Fix Committed
Status in bluez source package in Focal:
  Fix Released

Bug description:
  [Impact]

  Whenever I turn on my headphones they'll connect to my computer but
  I'm able to hear the input audio from my microphone and low quality
  output audio. I have to disconnect the headphones in the bluetooth
  devices and reconnect for it to fix the problem.

  [Test Case]

  0. Set up your Bluetooth headphones with Ubuntu.
  1. Turn off the headphones.
  2. Turn on the headphones.
  3. In Settings>Sound verify they have reconnected in A2DP mode (stereo, high 
quality, no microphone support).

  [Regression Potential]

  Low. Only the headset code path is affected and the fix has already
  been released for some time in BlueZ 5.51 onward.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1845046/+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 1845046] Re: Bluetooth headphones default to low quality headset mode and fail to switch to A2DP when selected

2020-01-26 Thread Doctor Rover
Also confirm that the problem is fixed for me on Focal with regular upgrades.
Tested with the same devices: Sony WH-1000XM3 and Plantronics Marque M155.

-- 
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/1845046

Title:
  Bluetooth headphones default to low quality headset mode and fail to
  switch to A2DP when selected

Status in bluez package in Ubuntu:
  Fix Released
Status in bluez source package in Bionic:
  Fix Committed
Status in bluez source package in Eoan:
  Fix Committed
Status in bluez source package in Focal:
  Fix Released

Bug description:
  [Impact]

  Whenever I turn on my headphones they'll connect to my computer but
  I'm able to hear the input audio from my microphone and low quality
  output audio. I have to disconnect the headphones in the bluetooth
  devices and reconnect for it to fix the problem.

  [Test Case]

  0. Set up your Bluetooth headphones with Ubuntu.
  1. Turn off the headphones.
  2. Turn on the headphones.
  3. In Settings>Sound verify they have reconnected in A2DP mode (stereo, high 
quality, no microphone support).

  [Regression Potential]

  Low. Only the headset code path is affected and the fix has already
  been released for some time in BlueZ 5.51 onward.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1845046/+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 1695618] Re: Qt5 apps don’t pick up the GTK+ style anymore

2018-03-20 Thread Doctor Rover
** Tags added: bionic

-- 
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/1695618

Title:
  Qt5 apps don’t pick up the GTK+ style anymore

Status in qtbase-opensource-src package in Ubuntu:
  Confirmed

Bug description:
  Since I upgraded to Qt 5.7.1, Qt5 apps stopped picking up the Ubuntu
  (GTK+, I presume) theme, and look very Windowsy. I have qt5-gtk-
  platformtheme installed, and I tried forcing it by setting
  QT_QPA_PLATFORMTHEME, but to no avail.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1695618/+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 1695618] Re: Qt5 apps don’t pick up the GTK+ style anymore

2018-03-20 Thread Doctor Rover
Installing qt5-style-plugins and export QT_QPA_PLATFORMTHEME=gtk2 works for me. 
Great! Thank you for the clue.
But I believe that this must be enabled by default and absence of this package 
in the default installation is actually the bug.

-- 
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/1695618

Title:
  Qt5 apps don’t pick up the GTK+ style anymore

Status in qtbase-opensource-src package in Ubuntu:
  Confirmed

Bug description:
  Since I upgraded to Qt 5.7.1, Qt5 apps stopped picking up the Ubuntu
  (GTK+, I presume) theme, and look very Windowsy. I have qt5-gtk-
  platformtheme installed, and I tried forcing it by setting
  QT_QPA_PLATFORMTHEME, but to no avail.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1695618/+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 1695618] Re: Include qt5-style-plugins into the default installation, otherwise Qt5 apps don’t pick up the GTK+ style

2018-03-21 Thread Doctor Rover
** Summary changed:

- Qt5 apps don’t pick up the GTK+ style anymore
+ Include qt5-style-plugins into the default installation, otherwise Qt5 apps 
don’t pick up the GTK+ style

** Description changed:

- Since I upgraded to Qt 5.7.1, Qt5 apps stopped picking up the Ubuntu
- (GTK+, I presume) theme, and look very Windowsy. I have qt5-gtk-
- platformtheme installed, and I tried forcing it by setting
- QT_QPA_PLATFORMTHEME, but to no avail.
+ In Artful and Bionic, Qt5 applications look alien because they don’t follow 
the GTK+ style.
+ For Qt5 applications to pick up the GTK+ style, qt5-style-plugins must be 
included into the default installation and “export QT_QPA_PLATFORMTHEME=gtk2” 
must be provided.
+ 
+ Original bug description:
+ Since I upgraded to Qt 5.7.1, Qt5 apps stopped picking up the Ubuntu (GTK+, I 
presume) theme, and look very Windowsy. I have qt5-gtk-platformtheme installed, 
and I tried forcing it by setting QT_QPA_PLATFORMTHEME, but to no avail.

-- 
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/1695618

Title:
  Include qt5-style-plugins into the default installation, otherwise Qt5
  apps don’t pick up the GTK+ style

Status in qtbase-opensource-src package in Ubuntu:
  Confirmed

Bug description:
  In Artful and Bionic, Qt5 applications look alien because they don’t follow 
the GTK+ style.
  For Qt5 applications to pick up the GTK+ style, qt5-style-plugins must be 
included into the default installation and “export QT_QPA_PLATFORMTHEME=gtk2” 
must be provided.

  Original bug description:
  Since I upgraded to Qt 5.7.1, Qt5 apps stopped picking up the Ubuntu (GTK+, I 
presume) theme, and look very Windowsy. I have qt5-gtk-platformtheme installed, 
and I tried forcing it by setting QT_QPA_PLATFORMTHEME, but to no avail.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1695618/+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 1695618] Re: Include qt5-style-plugins into the default installation, otherwise Qt5 apps don’t pick up the GTK+ style

2018-03-22 Thread Doctor Rover
Dmitry, thank you for your response and explanation.

-- 
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/1695618

Title:
  Include qt5-style-plugins into the default installation, otherwise Qt5
  apps don’t pick up the GTK+ style

Status in qtbase-opensource-src package in Ubuntu:
  Won't Fix

Bug description:
  In Artful and Bionic, Qt5 applications look alien because they don’t follow 
the GTK+ style.
  For Qt5 applications to pick up the GTK+ style, qt5-style-plugins must be 
included into the default installation and “export QT_QPA_PLATFORMTHEME=gtk2” 
must be provided.

  Original bug description:
  Since I upgraded to Qt 5.7.1, Qt5 apps stopped picking up the Ubuntu (GTK+, I 
presume) theme, and look very Windowsy. I have qt5-gtk-platformtheme installed, 
and I tried forcing it by setting QT_QPA_PLATFORMTHEME, but to no avail.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1695618/+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 1315434] Re: Mouse with no time remaining estimate showing in preference to battery being charged

2015-02-24 Thread Doctor Rover
Lee Dixon,
By the way, there is a special bug report about the 55% charge level:
Bug #1296872 - Charge level and the remaining time are estimated incorrectly 
for the battery in Logitech Wireless Mouse with Unifying receiver

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-power in Ubuntu.
https://bugs.launchpad.net/bugs/1315434

Title:
  Mouse with no time remaining estimate showing in preference to battery
  being charged

Status in indicator-power package in Ubuntu:
  In Progress

Bug description:
  When my laptop battery is in a charging state, but is not fully
  charged, I expect it to be displayed in preference to my mouse, which
  has no time remaining estimate.

  The spec here:

  https://wiki.ubuntu.com/Power

  says:

  "If anything is discharging, the menu title should represent the
  component (not battery, but component) that is estimated to lose power
  first. For example, if your notebook battery is estimated to discharge
  in 1 hour 47 minutes, and your wireless mouse battery is estimated to
  discharge in 27 minutes, the menu title should represent the mouse. "

  but there doesn't seem to be any guideline to what happens when a
  battery is being charged.

  I suggest the time remaining to charge a battery should be displayed
  in preference to the power level in a wireless mouse.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: indicator-power 12.10.6+14.04.20140411-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri May  2 11:50:36 2014
  InstallationDate: Installed on 2013-11-26 (156 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: indicator-power
  UpgradeStatus: Upgraded to trusty on 2014-01-17 (104 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1315434/+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 1270579] Re: On laptops, screen brightness isn't memorized between sessions

2015-04-04 Thread Doctor Rover
Unfortunately, the fix doesn't work for me. After reboot, the screen brightness 
is always on the minimum level.
Maybe I did something wrong... Is there a need to do something after the 
installation of the package with the script or installation itself is supposed 
to be enough?
Ubuntu 14.10 64bit
Notebook: Asus N550JK
Graphics: Integrated Intel HD Graphics 4600 + NVIDIA GTX850M

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/1270579

Title:
  On laptops, screen brightness isn't memorized between sessions

Status in Dell Sputnik:
  New
Status in One Hundred Papercuts:
  Won't Fix
Status in The Linux Mint Distribution:
  Confirmed
Status in Upstart:
  Confirmed
Status in upstart package in Ubuntu:
  Won't Fix

Bug description:
  HOW TO REPRODUCE:
  1. Boot a laptop.
  2. Set a different screen brightness level.
  3. Reboot.

  RESULT:
  Backlight is not memorized.

  FIX:
    Install package from PPA
  sudo add-apt-repository ppa:nrbrtx/sysvinit-backlight
  sudo apt-get update
  sudo apt-get install sysvinit-backlight

  NOTE:
    If you have installed previous version, please remove it carefully manually
  sudo rm /etc/rc?.d/?25backlight /etc/init.d/brightness 
/etc/rc?.d/?25brightness

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: initscripts 2.88dsf-41ubuntu5
  ProcVersionSignature: Ubuntu 3.13.0-4.19-generic 3.13.0-rc8
  Uname: Linux 3.13.0-4-generic i686
  ApportVersion: 2.13.1-0ubuntu1
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Sun Jan 19 17:20:26 2014
  InstallationDate: Installed on 2013-10-20 (91 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1)
  SourcePackage: sysvinit
  UpgradeStatus: Upgraded to trusty on 2013-11-19 (61 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1270579/+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 1641720] Re: Selecting a day does not display all day event for that day

2016-11-26 Thread Doctor Rover
I confirm, the bug is still present for all-day events from google calendar.
bq M10 rc-proposed/r240

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-datetime in
Ubuntu.
https://bugs.launchpad.net/bugs/1641720

Title:
  Selecting a day does not display all day event for that day

Status in indicator-datetime package in Ubuntu:
  Fix Released

Bug description:
  bq M10 rc-proposed silo #2195

  When I select a day from the calendar, I can see events for that day
  but it does not work with all-day events.

  Please see short video with this and other bugs with this silo:
  https://youtu.be/3vg6AQZmsqE

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1641720/+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 1645021] [NEW] indicator-datetime shows all-day events from google calendar a day before the actual date of the event

2016-11-26 Thread Doctor Rover
Public bug reported:

bq M10 rc-proposed/r240

The date-time indicator shows all-day events from google calendar one day 
before the actual date of the event. For example, the event happening on Monday 
is shown on Sunday. It applies for both the calendar and the list of events in 
the indicator.
At the same, the Calendar App shows the all-day events correctly.

This behavior is related to the time zone. My time zone is UTC+3. When I
set the zone to UTC+0, the indicator shows the all-day events correctly.

This bug looks just like Bug #1261191, but for Unity 8.
It also seems to be somehow related to Bug #1641720 and Bug #1641726. But after 
marking them as fixed, this one is still present.

** Affects: canonical-devices-system-image
 Importance: Undecided
 Status: New

** Affects: indicator-datetime (Ubuntu)
 Importance: Undecided
 Status: New

** Also affects: canonical-devices-system-image
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-datetime in
Ubuntu.
https://bugs.launchpad.net/bugs/1645021

Title:
  indicator-datetime shows all-day events from google calendar a day
  before the actual date of the event

Status in Canonical System Image:
  New
Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  bq M10 rc-proposed/r240

  The date-time indicator shows all-day events from google calendar one day 
before the actual date of the event. For example, the event happening on Monday 
is shown on Sunday. It applies for both the calendar and the list of events in 
the indicator.
  At the same, the Calendar App shows the all-day events correctly.

  This behavior is related to the time zone. My time zone is UTC+3. When
  I set the zone to UTC+0, the indicator shows the all-day events
  correctly.

  This bug looks just like Bug #1261191, but for Unity 8.
  It also seems to be somehow related to Bug #1641720 and Bug #1641726. But 
after marking them as fixed, this one is still present.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1645021/+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 1645021] Re: indicator-datetime shows all-day events from google calendar a day before the actual date of the event

2016-11-27 Thread Doctor Rover
** Description changed:

  bq M10 rc-proposed/r240
  
  The date-time indicator shows all-day events from google calendar one day 
before the actual date of the event. For example, the event happening on Monday 
is shown on Sunday. It applies for both the calendar and the list of events in 
the indicator.
- At the same, the Calendar App shows the all-day events correctly.
+ At the same time, the Calendar App shows the all-day events correctly.
  
  This behavior is related to the time zone. My time zone is UTC+3. When I
  set the zone to UTC+0, the indicator shows the all-day events correctly.
  
  This bug looks just like Bug #1261191, but for Unity 8.
  It also seems to be somehow related to Bug #1641720 and Bug #1641726. But 
after marking them as fixed, this one is still present.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-datetime in
Ubuntu.
https://bugs.launchpad.net/bugs/1645021

Title:
  indicator-datetime shows all-day events from google calendar a day
  before the actual date of the event

Status in Canonical System Image:
  New
Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  bq M10 rc-proposed/r240

  The date-time indicator shows all-day events from google calendar one day 
before the actual date of the event. For example, the event happening on Monday 
is shown on Sunday. It applies for both the calendar and the list of events in 
the indicator.
  At the same time, the Calendar App shows the all-day events correctly.

  This behavior is related to the time zone. My time zone is UTC+3. When
  I set the zone to UTC+0, the indicator shows the all-day events
  correctly.

  This bug looks just like Bug #1261191, but for Unity 8.
  It also seems to be somehow related to Bug #1641720 and Bug #1641726. But 
after marking them as fixed, this one is still present.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1645021/+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 1438510] Re: [REGRESSION] bluetooth headset no longer supports a2dp in 16.04 xenial

2016-10-08 Thread Doctor Rover
** Summary changed:

- [REGRESSION] bluetooth headset no longer supports a2dp
+ [REGRESSION] bluetooth headset no longer supports a2dp in 16.04 xenial

** Description changed:

  Just installed 15.04 fresh from the latest ISO (beta2).
  
  I'm bummed to see my bluetooth headset (Bose Soundlink overear) seems to
  have regressed in functionality.
  
  In 14.10, I was able to set the output profile either to a2dp or hsp/hfp
  (telephony duplex).
  
  In 15.04, it only works in telephony duplex mode.  I can't get high
  fidelity sound playback to work at all.
  
  This thread seems to be related, though the workaround within did not solve 
the problem for me:
  https://bbs.archlinux.org/viewtopic.php?id=194006
+ 
+ The bug is still present in 16.04 LTS.

-- 
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/1438510

Title:
  [REGRESSION] bluetooth headset no longer supports a2dp in 16.04 xenial

Status in PulseAudio:
  Unknown
Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed
Status in bluez source package in Vivid:
  Won't Fix
Status in pulseaudio source package in Vivid:
  Won't Fix

Bug description:
  Just installed 15.04 fresh from the latest ISO (beta2).

  I'm bummed to see my bluetooth headset (Bose Soundlink overear) seems
  to have regressed in functionality.

  In 14.10, I was able to set the output profile either to a2dp or
  hsp/hfp (telephony duplex).

  In 15.04, it only works in telephony duplex mode.  I can't get high
  fidelity sound playback to work at all.

  This thread seems to be related, though the workaround within did not solve 
the problem for me:
  https://bbs.archlinux.org/viewtopic.php?id=194006

  The bug is still present in 16.04 LTS.

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1438510/+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 1438510] Re: [REGRESSION] bluetooth headset no longer supports a2dp in 16.04 xenial

2016-10-25 Thread Doctor Rover
** Tags added: yakkety

** Description changed:

  Just installed 15.04 fresh from the latest ISO (beta2).
  
  I'm bummed to see my bluetooth headset (Bose Soundlink overear) seems to
  have regressed in functionality.
  
  In 14.10, I was able to set the output profile either to a2dp or hsp/hfp
  (telephony duplex).
  
  In 15.04, it only works in telephony duplex mode.  I can't get high
  fidelity sound playback to work at all.
  
  This thread seems to be related, though the workaround within did not solve 
the problem for me:
  https://bbs.archlinux.org/viewtopic.php?id=194006
  
- The bug is still present in 16.04 LTS.
+ The bug is still present in 16.04 LTS and 16.10.

** Summary changed:

- [REGRESSION] bluetooth headset no longer supports a2dp in 16.04 xenial
+ [REGRESSION] bluetooth headset no longer supports a2dp in 16.04 xenial and 
16.10 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/1438510

Title:
  [REGRESSION] bluetooth headset no longer supports a2dp in 16.04 xenial
  and 16.10 yakkety

Status in PulseAudio:
  Unknown
Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed
Status in bluez source package in Vivid:
  Won't Fix
Status in pulseaudio source package in Vivid:
  Won't Fix

Bug description:
  Just installed 15.04 fresh from the latest ISO (beta2).

  I'm bummed to see my bluetooth headset (Bose Soundlink overear) seems
  to have regressed in functionality.

  In 14.10, I was able to set the output profile either to a2dp or
  hsp/hfp (telephony duplex).

  In 15.04, it only works in telephony duplex mode.  I can't get high
  fidelity sound playback to work at all.

  This thread seems to be related, though the workaround within did not solve 
the problem for me:
  https://bbs.archlinux.org/viewtopic.php?id=194006

  The bug is still present in 16.04 LTS and 16.10.

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1438510/+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 1527053] Re: Tab names unreadable in GTK3 in Ubuntu

2016-09-19 Thread Doctor Rover
** Tags added: gtk3

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu.
https://bugs.launchpad.net/bugs/1527053

Title:
  Tab names unreadable in GTK3 in Ubuntu

Status in LibreOffice:
  Confirmed
Status in libreoffice package in Ubuntu:
  Triaged
Status in ubuntu-themes package in Ubuntu:
  Invalid

Bug description:
  Steps to reproduce:
  1. On Ubuntu 15.4 or 15.10, install or build libreoffice 5.1
  2. Open a tabbed dialog box such Format->Paragraph

  Note the text is white on light gray, which is very hard to read. In
  Fedora or Debian, when you select a "dark" theme, the tabs are
  rendered as white text on a black background.  In Ubuntu other UI
  elements such as the toolbar and context menus are rendered the same
  as Debian's dark theme(white text on black).

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1527053/+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 1562513] Re: Toolbar has a dark background in GTK3 in Ubuntu

2016-09-19 Thread Doctor Rover
** Tags added: gtk3

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu.
https://bugs.launchpad.net/bugs/1562513

Title:
  Toolbar has a dark background in GTK3 in Ubuntu

Status in LibreOffice:
  Won't Fix
Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  When LO is launched with SAL_USE_VCLPLUGIN=gtk3, the toolbar panel has
  a dark background making icons of styles like Sifr or Breeze almost
  invisible.

  Ubuntu 15.10 x64
  LibreOffice 5.1.1.2 (1:5.1.1~rc2-0ubuntu1~wily0) installed from 
ppa:libreoffice/ppa

  See also Bug #1527053 on LibreOffice GTK3-related issues.

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1562513/+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 1610456] Re: Tablet must start in landscape orientation mode by default

2016-08-15 Thread Doctor Rover
** Also affects: canonical-devices-system-image
   Importance: Undecided
   Status: New

-- 
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/1610456

Title:
  Tablet must start in landscape orientation mode by default

Status in Canonical System Image:
  New
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Tablet always starts in portrait orientation mode unless I hold it
  absolutely vertically. The Log In screen appears in landscape mode
  which is correct, but then, when I log in, the device switches to
  portrait. So each time I use the device, I need to start from lifting
  it up to the vertical position. The default mode for tablets must be
  landscape.

  I use bq M10 tablet on rc-proposed channel with all daily updates
  installed. Current build is r160.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1610456/+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 can not control the media playback

2016-08-31 Thread Doctor Rover
There is at least one more important functionality of AVRCP missing in
Ubuntu Touch right now besides play/pause/stop/next/previous. It is
transmitting metadata information on the track (artist, track name,
album, etc.) to the connected bluetooth device. For example, many car
multimedia systems support this feature. It seems to be quite important
for drivers.

-- 
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 can not control the 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 1596330] Re: AVRCP not working

2016-08-31 Thread Doctor Rover
Possible duplicate of Bug #1398193 - The bluetooth headset can not
control the media playback

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus-cpp in Ubuntu.
https://bugs.launchpad.net/bugs/1596330

Title:
  AVRCP not working

Status in Client Developer Experience:
  New
Status in dbus-cpp package in Ubuntu:
  Confirmed
Status in media-hub package in Ubuntu:
  Confirmed

Bug description:
  AVRCP is still not working. I've digged a bit into it and it seems the
  reason is that mpris-proxy fails to introspect the MPRIS interface of
  media-hub. The reason for that seems to be that dbus-cpp does not
  correctly reply to GetAll property requests on D-Bus. I'm not entirely
  sure if it's an issue in libdbus-cpp, or wrong usage of it in media-
  hub.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-developer-experience/+bug/1596330/+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 can not control the media playback

2016-08-31 Thread Doctor Rover
@mpredotka, @mzanetti, thanks for the prompt responses!

> Once this is fixed, I think both, controls and metadata should start working.
Great! Looking forward to that :)
Do I get it right that this means no need for a separate bug ticket?

-- 
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 can not control the 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 1572528] Re: Side stage close/ collapse gesture hard to discover

2016-07-04 Thread Doctor Rover
@Michał Sawicz, thank you for the trick with 3 finger tap. It's convenient. But 
it's not obvious, so I didn't know that.
I believe this is a good idea to add a short info on 3-finger-tap gesture to 
the "black screen [tutorial] telling how to use 3 fingers to use the side 
stage".

-- 
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/1572528

Title:
  Side stage close/ collapse gesture hard to discover

Status in Ubuntu UX:
  New
Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  Once any app has been in the side stage there seems to be no way to close it 
anymore as long as the device is in landscape orientation. Moving all of the 
side staged apps back to the main stage or closing them will leave a black 
screen behind telling how to use 3 fingers to use the side stage.
  This is particularly inconvenient due to bug 1564348 and renders many apps 
difficult or impossible to use in landscape.

  This is on Frieza with OTA 10.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1572528/+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 1610456] [NEW] Tablet must start in landscape orientation mode by default

2016-08-05 Thread Doctor Rover
Public bug reported:

Tablet always starts in portrait orientation mode unless I hold it
absolutely vertically. The Log In screen appears in landscape mode which
is correct, but then, when I log in, the device switches to portrait. So
each time I use the device, I need to start from lifting it up to the
vertical position. The default mode for tablets must be landscape.

I use bq M10 tablet on rc-proposed channel with all daily updates
installed. Current build is r160.

** Affects: unity8 (Ubuntu)
 Importance: Undecided
 Status: New

-- 
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/1610456

Title:
  Tablet must start in landscape orientation mode by default

Status in unity8 package in Ubuntu:
  New

Bug description:
  Tablet always starts in portrait orientation mode unless I hold it
  absolutely vertically. The Log In screen appears in landscape mode
  which is correct, but then, when I log in, the device switches to
  portrait. So each time I use the device, I need to start from lifting
  it up to the vertical position. The default mode for tablets must be
  landscape.

  I use bq M10 tablet on rc-proposed channel with all daily updates
  installed. Current build is r160.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1610456/+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 1377008] Re: the application menu in windows tittle bar

2014-10-03 Thread Doctor Rover
*** This bug is a duplicate of bug 955193 ***
https://bugs.launchpad.net/bugs/955193

** This bug has been marked a duplicate of bug 955193
   Menu bar - add option for the global menu to make it always visible

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1377008

Title:
  the application menu in windows tittle bar

Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  Not possible to configure the application menu, the window menu on a
  regular basis instead of the name of the document. For example, a very
  easy to use the Gimp, video editor, players

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: unity 7.3.1+14.10.20140915-0ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-20.27-generic 3.16.3
  Uname: Linux 3.16.0-20-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  CasperVersion: 1.344
  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: Fri Oct  3 05:01:26 2014
  DistUpgraded: Fresh install
  DistroCodename: utopic
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7520G] [1002:9990] 
(prog-if 00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd Device [144d:c0da]
   Advanced Micro Devices, Inc. [AMD/ATI] Thames [Radeon HD 7500M/7600M Series] 
[1002:6840] (prog-if 00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd Radeon HD 7670M [144d:c0da]
  LiveMediaBuild: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141002)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 355V4C/356V4C/3445VC/3545VC
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: initrd=/casper/initrd.lz file=/cdrom/preseed/username.seed 
boot=casper  quiet splash -- BOOT_IMAGE=/casper/vmlinuz.efi
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/04/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P09AAN
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: NP355V5X-S01RU
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: BOARD REVISION 00
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP09AAN:bd07/04/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn355V4C/356V4C/3445VC/3545VC:pvrP09AAN.031.CP:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP355V5X-S01RU:rvrBOARDREVISION00:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 355V4C/356V4C/3445VC/3545VC
  dmi.product.version: P09AAN.031.CP
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.914-1~exp1ubuntu3
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2
  xserver.bootTime: Fri Oct  3 08:41:50 2014
  xserver.configfile: default
  xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.16.0-1ubuntu1
  xserver.video_driver: radeon

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1377008/+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