date:20170523

[Bug 1693101] Re: gnome-shell crashed with signal 5 in _XIOError()

2017-05-23 Thread Apport retracing service

*** This bug is a duplicate of bug 1556601 ***
https://bugs.launchpad.net/bugs/1556601

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1556601, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1693101/+attachment/4882313/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1693101/+attachment/4882315/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1693101/+attachment/4882319/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1693101/+attachment/4882320/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1693101/+attachment/4882321/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1693101/+attachment/4882322/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1693101/+attachment/4882323/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1556601
   gnome-shell crashed with signal 5 in _XIOError()

** Tags removed: need-amd64-retrace

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1693101

Title:
  gnome-shell crashed with signal 5 in _XIOError()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1693101/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1690299] Re: Cannot remove detached devices from container

2017-05-23 Thread Michal Kovarik

Both proposals are useful.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1690299

Title:
  Cannot remove detached devices from container

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1690299/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1690957] secchi (amd64) - tests ran: 6, failed: 0

2017-05-23 Thread Brad Figg

tests ran:   6, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-53.56~16.04.1-generic/secchi__4.8.0-53.56~16.04.1__2017-05-24_05-07-00/results-index.html

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1690957

Title:
  linux-hwe: 4.8.0-53.56~16.04.1 -proposed tracker

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1690957/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 379873] Re: CPU Frequency Scaling Monitor reports incorrect CPU speeds when overclocked

2017-05-23 Thread Chris Placzek

Just want to chime in here.  I have this problem as well.  I have had it
on several motherboards, several CPUs, and every version of Ubuntu and
Debian I have had.  I am currently on Lubuntu 16.04 with kernel 4.4.0-78
and this issue persists.

My CPU has a stock speed of 3166MHz on a 1333MHz bus.  If I set my bus
to 1600MHz, which runs the CPU at 3800MHz, everything reports CPU speed
correctly.  However, if I run my bus speed anywhere in between 1333MHz
and 1600MHz, the CPU speed is *not* correctly reported.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/379873

Title:
  CPU Frequency Scaling Monitor reports incorrect CPU speeds when
  overclocked

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/379873/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1690957] wright-kernel (arm64) - tests ran: 64, failed: 1

2017-05-23 Thread Brad Figg

tests ran:  64, failed: 1;
  
http://kernel.ubuntu.com/testing/4.8.0-53.56~16.04.1-generic/wright-kernel__4.8.0-53.56~16.04.1__2017-05-24_04-36-00/results-index.html

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1690957

Title:
  linux-hwe: 4.8.0-53.56~16.04.1 -proposed tracker

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1690957/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1693101] [NEW] gnome-shell crashed with signal 5 in _XIOError()

2017-05-23 Thread Per-Inge

Public bug reported:

Happened directly after boot. No usability issue.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.24.2-0ubuntu4
ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
Uname: Linux 4.10.0-20-generic x86_64
ApportVersion: 2.20.5-0ubuntu4
Architecture: amd64
CrashCounter: 1
CurrentDesktop: GNOME-Greeter:GNOME
Date: Wed May 24 00:38:27 2017
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:
 
InstallationDate: Installed on 2017-05-20 (3 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170519)
ProcCmdline: /usr/bin/gnome-shell
Signal: 5
SourcePackage: gnome-shell
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libmutter-0.so.0
 _XIOError () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 XSync () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
Title: gnome-shell crashed with signal 5 in _XIOError()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

** Affects: gnome-shell (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-crash artful need-amd64-retrace

** Information type changed from Private to Public

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1693101

Title:
  gnome-shell crashed with signal 5 in _XIOError()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1693101/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1283003] Re: Bluetooth headset/speakers listed but not selectable in Sound settings

2017-05-23 Thread Daniel van Vugt

** Description changed:

  [Impact]
  Bluetooth headset/speakers are listed but not selectable in Sound settings. 
Hence not Bluetooth audio is unusable.
  
  [Test Case]
  1. Pair a Bluetooth audio device with Ubuntu.
  2. Go to Sound settings and try to select the device.
  Expected: The Bluetooth audio device is selectable (is usable).
  
  [Regression Potential]
  Low. The SRU focuses on Bluetooth logic in pulseaudio, so that is the main 
area affected. A combination of related A2DP bugs in pulseaudio in xenial means 
it is difficult to get working at all without this patch. So highly unlikely 
Bluetooth audio support could get worse. Since pulseaudio itself is being 
modified there is always a regression potential in support for other audio 
devices, but several audio devices have been tested and all continue to work 
well with the patch.
  
  [Other notes]
- Related to bug 1438510 and bug 1582213. Possibly others too. The debdiff 
which fixes this is attached to bug 1438510.
+ Related to bug 1438510 and bug 1582213. Possibly others too. The debdiff 
which fixes this is attached to bug 1582213.
  
  Please note that Bluetooth and Bluetooth audio support in xenial is
  still not perfect. This SRU only aims to address a few of the most
  troublesome issues. Please consider the fact that this is an incremental
  improvement and some people are still likely to experience some bugs
  related to pulseaudio and Bluetooth, even after this SRU.
  
  The patch was authored by Luke Yelavich with help from Konrad
  Zapałowicz. And it has received further testing over the past two months
  by Konrad, Jim Hodapp and Daniel van Vugt. The debdiff proposed here
  only changes the changelog wording from Luke's original PPA.
  
  [Original Description]
  Hi,
  
  I found a bug in Ubuntu 14.04 !
  
  I tried to pair a bluetooth stereo headset (A2DP compatible). The
  pairing process goes well, but after that I can't select it on the audio
  preferences.
  
  When I select it, it only shows the last selected item options and don't do 
anything. (he should switch to the headset output).
  I must mention that it worked very well on Ubuntu 12.04.
  
  This bug can be in the bluetooth stack or in unity-control-center or
  maybe pulseaudio. I actually have no idea.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1283003

Title:
  Bluetooth headset/speakers listed but not selectable in Sound settings

To manage notifications about this bug go to:
https://bugs.launchpad.net/blueman/+bug/1283003/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 598351] Re: External/Internal Mic on Lenovo Ideapad U150 (Conexant CX20582- Pebble) does not work.

2017-05-23 Thread madbiologist

Official support for Ubuntu 11.10 "Oneiric Ocelot" has ended.  If this
bug is still occurring on Ubuntu 17.04 "Zesty Zapus" please run ubuntu-
bug to file a new bug report so that we can get a fresh set of log files
and system info.

** Tags added: lucid

** Changed in: alsa-driver (Ubuntu)
   Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/598351

Title:
  External/Internal Mic on Lenovo Ideapad U150 (Conexant CX20582-
  Pebble) does not work.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/598351/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1582213] Re: [xenial] Bluetooth device doesn't play any sound in A2DP mode unless set to HSP/HFP first

2017-05-23 Thread Daniel van Vugt

Attached debdiff for updating xenial to pulseaudio 1:8.0-0ubuntu3.3, in
order to address a few problems with Bluetooth audio (A2DP).

** Patch added: "xenial-a2dp-fixes-may2017.debdiff"

https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1582213/+attachment/4882311/+files/xenial-a2dp-fixes-may2017.debdiff

** Description changed:

[Impact]
Bluetooth device doesn't play any sound in A2DP mode unless set to HSP/HFP
first. A2DP is the high quality profile used for Bluetooth speakers and music
in general.

[Test Case]
1. Pair a Bluetooth audio device with Ubuntu.
2. Verify in Sound settings you have it set to A2DP mode.
3. Turn off and then on the Bluetooth device.
4. Verify the device has reconnected and if not, force it to in the Bluetooth
indicator menu.
5. Open Sound settings again, select the device and verify it's reappeared in
A2DP mode.
6. Click 'Test Sound'.
Expected: Sound can be heard from the Bluetooth device.

[Regression Potential]
Low. The SRU focuses on Bluetooth logic in pulseaudio, so that is the main
area affected. A combination of related A2DP bugs in pulseaudio in xenial means
it is difficult to get working at all without this patch. So highly unlikely
Bluetooth audio support could get worse. Since pulseaudio itself is being
modified there is always a regression potential in support for other audio
devices, but several audio devices have been tested and all continue to work
well with the patch.

[Other notes]
- Related to bug 1283003 and bug 1438510. Possibly others too. The debdiff
which fixes this is attached to bug 1438510.
+ Related to bug 1283003 and bug 1438510. Possibly others too.

The patch was authored by Luke Yelavich with help from Konrad
Zapałowicz. And it has received further testing over the past two months
by Konrad, Jim Hodapp and Daniel van Vugt. The debdiff proposed here
only changes the changelog wording from Luke's original PPA.

[Original Description]
I have a Sennheiser MM 450-X headset.

In 15.10, connection & playback was straightforward.

In 16.04, the headset connects, and shows up as default playback device
on `pavucontrol`, but there is no sound.

A functional workaround is to, after having connected it, to go the
`Configuration` tab, and in the `Profile` dropdown, to choose `...
HSP/HFP`, which will make them play as expected (but in low quality),
then switch to `... A2DP Sink` (they will play in high quality).

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: pulseaudio-module-bluetooth 1:8.0-0ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl nvidia_uvm nvidia_drm
nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: myuser2936 F pulseaudio
/dev/snd/controlC2: myuser2936 F pulseaudio
/dev/snd/controlC0: myuser2936 F pulseaudio
Date: Mon May 16 14:18:58 2016
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-03-11 (66 days ago)
InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160224)
PulseList:
Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not
accessible: Permission denied
No PulseAudio daemon running, or not running as session daemon.
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/22/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F5
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: F2A88XN-WIFI
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd04/22/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A88XN-WIFI:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1582213

Title:
[xenial] Bluetooth device doesn't play any sound in A2DP mode unless
set to HSP/HFP first

To manage notifications about this bug go to:

[Bug 1438510] Re: [regression] Bluetooth audio no longer supports A2DP (stuck in HSP/HFP mode)

2017-05-23 Thread Daniel van Vugt

I have moved the debdiff into bug 1582213, which seems to be a more
sure-fire-definitely-fixed bug when compared to this more vague ongoing
issue.

** Patch removed: "xenial-a2dp-fixes-may2017.debdiff"

https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1438510/+attachment/4882273/+files/xenial-a2dp-fixes-may2017.debdiff

** Description changed:

[Impact]
Bluetooth audio seemingly refuses to support A2DP (stuck in HSP/HFP mode).
A2DP is the high quality profile used for Bluetooth speakers and music in
general.

[Test Case]
1. Pair a Bluetooth audio device with Ubuntu.
2. Go to Sound settings and check the device's current "Mode".
3. If the current Mode is not yet A2DP then try to set it to A2DP
Expected: The mode is either A2DP by default or can be set to it.

[Other notes]
- Related to bug 1283003 and bug 1582213. Possibly others too.
+ Related to bug 1283003 and bug 1582213. Possibly others too. The debdiff
which fixes this is attached to bug 1582213.

[Original 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.

--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1438510

Title:
[regression] Bluetooth audio no longer supports A2DP (stuck in HSP/HFP
mode)

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1438510/+subscriptions

--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1690299] Re: Cannot remove detached devices from container

2017-05-23 Thread Stéphane Graber

Okay, so I figured out what's going on here and while not ideal, it
actually makes sense.

unix-char and unix-block devices don't have an "optional" property,
therefore LXD will fail to start any container which lists such a device
without the host path existing.

LXD also validates the container configuration to be valid whenever a change to 
it is done.
When removing one of the device, the client tool gives LXD an updated container 
config which includes the remaining device. That device is invalid and so LXD 
fails the config validation and returns the error.

The way around the issue is to use "lxc config edit" to remove both
devices in one shot. That way the LXD configuration will be valid.


There are a couple of things we could do to make this easier:
 - Add an "optional" flag to unix-char and unix-block, allowing you to specify 
devices which may not yet exist. The container would then start fine and the 
config would be considered valid by the validator even if those devices are 
missing. When the device shows up again, a restart would be needed to have it 
show up in the container again.

 - Allow for multiple device names to be passed to "lxc config device
remove". This would let you remove both devices in one shot, resulting
in a valid configuration.


Let me know if either/both of those would be useful to you. Until then, use 
"lxc config edit" to remove both devices.

** Changed in: lxd (Ubuntu)
   Status: New => Triaged

** Changed in: lxd (Ubuntu)
   Importance: Undecided => Medium

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1690299

Title:
  Cannot remove detached devices from container

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1690299/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1667444] Re: Failed to start lxd container because it is already running a start operation

2017-05-23 Thread Stéphane Graber

** Changed in: lxd (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1667444

Title:
  Failed to start lxd container because it is already running a start
  operation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1667444/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1692985] Re: Juju openstack lvd returns always "Container is already running a start operation"

2017-05-23 Thread Stéphane Graber

Looks like Juju is attempting to start the container twice. But that's
not really the problem. The problem is that the container start itself
failed.

We'd need all the files from /var/log/lxd// to
investigate. That may be made somewhat difficult by the fact that Juju
appears to clean everything up on failure.


The usual culprit for this is some invalid configuration in the Juju (or 
conjure-up) generated profile. Things like missing kernel modules or missing 
devices, but without the actual error message for the container in question, 
it's hard to tell exactly what's the issue.

** Changed in: lxd (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1692985

Title:
  Juju openstack lvd returns always "Container is already running a
  start operation"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1692985/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1283003] Re: Bluetooth headset/speakers listed but not selectable in Sound settings

2017-05-23 Thread Daniel van Vugt

** Description changed:

  [Impact]
  Bluetooth headset/speakers are listed but not selectable in Sound settings. 
Hence not Bluetooth audio is unusable.
  
  [Test Case]
  1. Pair a Bluetooth audio device with Ubuntu.
  2. Go to Sound settings and try to select the device.
  Expected: The Bluetooth audio device is selectable (is usable).
  
  [Regression Potential]
  Low. The SRU focuses on Bluetooth logic in pulseaudio, so that is the main 
area affected. A combination of related A2DP bugs in pulseaudio in xenial means 
it is difficult to get working at all without this patch. So highly unlikely 
Bluetooth audio support could get worse. Since pulseaudio itself is being 
modified there is always a regression potential in support for other audio 
devices, but several audio devices have been tested and all continue to work 
well with the patch.
  
  [Other notes]
  Related to bug 1438510 and bug 1582213. Possibly others too. The debdiff 
which fixes this is attached to bug 1438510.
  
  Please note that Bluetooth and Bluetooth audio support in xenial is
  still not perfect. This SRU only aims to address a few of the most
  troublesome issues. Please consider the fact that this is an incremental
  improvement and some people are still likely to experience some bugs
  related to pulseaudio and Bluetooth, even after this SRU.
  
+ The patch was authored by Luke Yelavich with help from Konrad
+ Zapałowicz. And it has received further testing over the past two months
+ by Konrad, Jim Hodapp and Daniel van Vugt. The debdiff proposed here
+ only changes the changelog wording from Luke's original PPA.
+ 
  [Original Description]
  Hi,
  
  I found a bug in Ubuntu 14.04 !
  
  I tried to pair a bluetooth stereo headset (A2DP compatible). The
  pairing process goes well, but after that I can't select it on the audio
  preferences.
  
  When I select it, it only shows the last selected item options and don't do 
anything. (he should switch to the headset output).
  I must mention that it worked very well on Ubuntu 12.04.
  
  This bug can be in the bluetooth stack or in unity-control-center or
  maybe pulseaudio. I actually have no idea.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1283003

Title:
  Bluetooth headset/speakers listed but not selectable in Sound settings

To manage notifications about this bug go to:
https://bugs.launchpad.net/blueman/+bug/1283003/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1582213] Re: [xenial] Bluetooth device doesn't play any sound in A2DP mode unless set to HSP/HFP first

2017-05-23 Thread Daniel van Vugt

** Description changed:

[Impact]
Bluetooth device doesn't play any sound in A2DP mode unless set to HSP/HFP
first. A2DP is the high quality profile used for Bluetooth speakers and music
in general.

[Other notes]
Related to bug 1283003 and bug 1438510. Possibly others too. The debdiff
which fixes this is attached to bug 1438510.

Please note that Bluetooth and Bluetooth audio support in xenial is
still not perfect. This SRU only aims to address a few of the most
troublesome issues. Please consider the fact that this is an incremental
improvement and some people are still likely to experience some bugs
related to pulseaudio and Bluetooth, even after this SRU.
+
+ The patch was authored by Luke Yelavich with help from Konrad
+ Zapałowicz. And it has received further testing over the past two months
+ by Konrad, Jim Hodapp and Daniel van Vugt. The debdiff proposed here
+ only changes the changelog wording from Luke's original PPA.

[Original Description]
I have a Sennheiser MM 450-X headset.

In 15.10, connection & playback was straightforward.

In 16.04, the headset connects, and shows up as default playback device
on `pavucontrol`, but there is no sound.

--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1582213

Title:
[xenial] Bluetooth device doesn't play any sound in A2DP mode unless
set to HSP/HFP first

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1582213/+subscriptions

--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1438510] Re: [regression] Bluetooth audio no longer supports A2DP (stuck in HSP/HFP mode)

2017-05-23 Thread Daniel van Vugt

** Description changed:

  [Impact]
  Bluetooth audio seemingly refuses to support A2DP (stuck in HSP/HFP mode). 
A2DP is the high quality profile used for Bluetooth speakers and music in 
general.
  
  [Test Case]
  1. Pair a Bluetooth audio device with Ubuntu.
  2. Go to Sound settings and check the device's current "Mode".
  3. If the current Mode is not yet A2DP then try to set it to A2DP
  Expected: The mode is either A2DP by default or can be set to it.
  
  [Regression Potential]
  Low. The SRU focuses on Bluetooth logic in pulseaudio, so that is the main 
area affected. A combination of related A2DP bugs in pulseaudio in xenial means 
it is difficult to get working at all without this patch. So highly unlikely 
Bluetooth audio support could get worse. Since pulseaudio itself is being 
modified there is always a regression potential in support for other audio 
devices, but several audio devices have been tested and all continue to work 
well with the patch.
  
  [Other notes]
  Related to bug 1283003 and bug 1582213. Possibly others too.
  
  Please note that Bluetooth and Bluetooth audio support in xenial is
  still not perfect. This SRU only aims to address a few of the most
  troublesome issues. Please consider the fact that this is an incremental
  improvement and some people are still likely to experience some bugs
  related to pulseaudio and Bluetooth, even after this SRU.
  
+ The SRU was authored by Luke Yelavich with help from Konrad Zapałowicz.
+ And it has received further testing over the past two months by Konrad,
+ Jim Hodapp and Daniel van Vugt. The debdiff proposed here only changes
+ the changelog wording from Luke's original PPA.
+ 
  [Original 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.

** Description changed:

  [Impact]
  Bluetooth audio seemingly refuses to support A2DP (stuck in HSP/HFP mode). 
A2DP is the high quality profile used for Bluetooth speakers and music in 
general.
  
  [Test Case]
  1. Pair a Bluetooth audio device with Ubuntu.
  2. Go to Sound settings and check the device's current "Mode".
  3. If the current Mode is not yet A2DP then try to set it to A2DP
  Expected: The mode is either A2DP by default or can be set to it.
  
  [Regression Potential]
  Low. The SRU focuses on Bluetooth logic in pulseaudio, so that is the main 
area affected. A combination of related A2DP bugs in pulseaudio in xenial means 
it is difficult to get working at all without this patch. So highly unlikely 
Bluetooth audio support could get worse. Since pulseaudio itself is being 
modified there is always a regression potential in support for other audio 
devices, but several audio devices have been tested and all continue to work 
well with the patch.
  
  [Other notes]
  Related to bug 1283003 and bug 1582213. Possibly others too.
  
  Please note that Bluetooth and Bluetooth audio support in xenial is
  still not perfect. This SRU only aims to address a few of the most
  troublesome issues. Please consider the fact that this is an incremental
  improvement and some people are still likely to experience some bugs
  related to pulseaudio and Bluetooth, even after this SRU.
  
- The SRU was authored by Luke Yelavich with help from Konrad Zapałowicz.
- And it has received further testing over the past two months by Konrad,
- Jim Hodapp and Daniel van Vugt. The debdiff proposed here only changes
- the changelog wording from Luke's original PPA.
+ The patch was authored by Luke Yelavich with help from Konrad
+ Zapałowicz. And it has received further testing over the past two months
+ by Konrad, Jim Hodapp and Daniel van Vugt. The debdiff proposed here
+ only changes the changelog wording from Luke's original PPA.
  
  [Original 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.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

[Bug 1693099] [NEW] Firefox address bar not working

2017-05-23 Thread Parag

Public bug reported:

Firefox does not search for site in the address bar in the default tab
after launch, not even the bookmarks or recent sites list on the local
computer. It however fucntions normally when the same search is typed
into another (newly opened)  tab's address bar . After this is done, the
address bar in the original (first) tab also works normally.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: firefox 53.0.2+build1-0ubuntu0.14.04.2
ProcVersionSignature: Ubuntu 3.13.0-119.166-generic 3.13.11-ckt39
Uname: Linux 3.13.0-119-generic x86_64
NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
AddonCompatCheckDisabled: False
ApportVersion: 2.14.1-0ubuntu3.24
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  parag  2298 F pulseaudio
 /dev/snd/controlC0:  parag  2298 F pulseaudio
BuildID: 20170509210304
CRDA: Error: [Errno 2] No such file or directory: 'iw'
Channel: Unavailable
CurrentDesktop: GNOME
Date: Wed May 24 10:24:47 2017
Extensions: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
 #auto eth0
 #iface eth0 inet dhcp
IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini 
or extensions.sqlite)
InstallationDate: Installed on 2015-09-27 (604 days ago)
InstallationMedia: Lubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
IpRoute:
 default via 192.168.1.41 dev eth0  proto static 
 192.168.1.0/24 dev eth0  proto kernel  scope link  src 192.168.1.18  metric 1
Locales: extensions.sqlite corrupt or missing
Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
PrefSources: prefs.js
Profiles: Profile0 (Default) - LastVersion=53.0.2/20170509210304 (In use)
RunningIncompatibleAddons: False
SourcePackage: firefox
Themes: extensions.sqlite corrupt or missing
UpgradeStatus: Upgraded to trusty on 2017-05-03 (20 days ago)
dmi.bios.date: 10/16/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: Q550LF.211
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: Q550LF
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrQ550LF.211:bd10/16/2013:svnASUSTeKCOMPUTERINC.:pnQ550LF:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnQ550LF:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: Q550LF
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


** Tags: amd64 apport-bug third-party-packages trusty

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1693099

Title:
  Firefox address bar not working

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1693099/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

1 2 3 4 5 6 7 8 >

1 - 100 of 708 matches

Mail list logo