[Touch-packages] [Bug 1707487] Re: Bluetooth speaker only plays as mono

2017-07-31 Thread David
I need to report a SIMILAR bug, which affects the same GUI for the
audio. Bear with me.

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

Title:
  Bluetooth speaker only plays as mono

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  When I connect my Sony SRS-X1 Bluetooth speaker to Ubuntu, it only
  plays back as "mono" and refuses to use "hi fidelity".

  I have Windows 10 installed on the same laptop and when I've used the
  Bluetooth speaker in Ubuntu, Windows will "forget" the speaker on its
  Bluetooth list. I have to hold in the "reset" button on the speaker
  itself and re-add the speaker to Windows 10. This ONLY HAPPENS if I
  try using this speaker in Ubuntu, which suggests that Ubuntu is
  forcing the speaker into "mono" mode and Windows then sees it as a
  different device?

  Please help.
  I will post all needed outputs as instructed.

  Cheers!
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   david  3626 F...m pulseaudio
   /dev/snd/controlC0:  david  3626 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-07-28 (367 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Package: pulseaudio 1:8.0-0ubuntu3.3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-87.110-generic 4.4.73
  Tags:  xenial
  Uname: Linux 4.4.0-87-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/16/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.21
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: VA50_HC_CR
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Insyde Corp.
  dmi.chassis.version: V2.21
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.21:bd12/16/2013:svnAcer:pnAspireV3-571:pvrV2.21:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnInsydeCorp.:ct10:cvrV2.21:
  dmi.product.name: Aspire V3-571
  dmi.product.version: V2.21
  dmi.sys.vendor: Acer
  modified.conffile..etc.xdg.autostart.pulseaudio.desktop: [modified]
  mtime.conffile..etc.xdg.autostart.pulseaudio.desktop: 
2016-07-29T10:08:04.428983

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1707487/+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 1707611] [NEW] Sound does not automatically play on new audio device

2017-07-31 Thread David
Public bug reported:

When connecting a HDMI cable or other audio device, the user must
manually click on the "sound volume" in the top-right and switch to the
newly connected device.

Example: you connect a HDMI cable to the television, but then you must
manually choose the HDMI sound option; it does not get selected
automatically.

Often times e.g. when the HDMI cable is disconnected, the user must then
manually click on the "speakers" or "line out" setting - EVEN IF IT'S
ALREADY SELECTED, it must be clicked on again for the sound to work
through the computer's speakers.

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

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

Title:
  Sound does not automatically play on new audio device

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  When connecting a HDMI cable or other audio device, the user must
  manually click on the "sound volume" in the top-right and switch to
  the newly connected device.

  Example: you connect a HDMI cable to the television, but then you must
  manually choose the HDMI sound option; it does not get selected
  automatically.

  Often times e.g. when the HDMI cable is disconnected, the user must
  then manually click on the "speakers" or "line out" setting - EVEN IF
  IT'S ALREADY SELECTED, it must be clicked on again for the sound to
  work through the computer's speakers.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1707611/+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 1707606] [NEW] [nautilus] no sidebar mouseover selection displayed

2017-07-31 Thread Sebastien Bacher
Public bug reported:

Using nautilus 3.24 in artful, if you dnd a file over one of the folders
in the sidebar with Adwaita you get a green selection displayed around
the target entry. When using Ambiance there is no such indication

** Affects: ubuntu-themes (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: gnome-17.10

** Tags added: gnome-17.10

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

Title:
  [nautilus] no sidebar mouseover selection displayed

Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  Using nautilus 3.24 in artful, if you dnd a file over one of the
  folders in the sidebar with Adwaita you get a green selection
  displayed around the target entry. When using Ambiance there is no
  such indication

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1707606/+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 1707487] Re: Bluetooth speaker only plays as mono

2017-07-31 Thread Daniel van Vugt
** Changed in: pulseaudio (Ubuntu)
   Status: Incomplete => New

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

Title:
  Bluetooth speaker only plays as mono

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  When I connect my Sony SRS-X1 Bluetooth speaker to Ubuntu, it only
  plays back as "mono" and refuses to use "hi fidelity".

  I have Windows 10 installed on the same laptop and when I've used the
  Bluetooth speaker in Ubuntu, Windows will "forget" the speaker on its
  Bluetooth list. I have to hold in the "reset" button on the speaker
  itself and re-add the speaker to Windows 10. This ONLY HAPPENS if I
  try using this speaker in Ubuntu, which suggests that Ubuntu is
  forcing the speaker into "mono" mode and Windows then sees it as a
  different device?

  Please help.
  I will post all needed outputs as instructed.

  Cheers!
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   david  3626 F...m pulseaudio
   /dev/snd/controlC0:  david  3626 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-07-28 (367 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Package: pulseaudio 1:8.0-0ubuntu3.3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-87.110-generic 4.4.73
  Tags:  xenial
  Uname: Linux 4.4.0-87-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/16/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.21
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: VA50_HC_CR
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Insyde Corp.
  dmi.chassis.version: V2.21
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.21:bd12/16/2013:svnAcer:pnAspireV3-571:pvrV2.21:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnInsydeCorp.:ct10:cvrV2.21:
  dmi.product.name: Aspire V3-571
  dmi.product.version: V2.21
  dmi.sys.vendor: Acer
  modified.conffile..etc.xdg.autostart.pulseaudio.desktop: [modified]
  mtime.conffile..etc.xdg.autostart.pulseaudio.desktop: 
2016-07-29T10:08:04.428983

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1707487/+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 1442050] Re: (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown error -2

2017-07-31 Thread paz
still a problem here:
Ubuntu 17.04.1 32 bit 

 sudo service colord status
[sudo] password for paz: 
● colord.service - Manage, Install and Generate Color Profiles
   Loaded: loaded (/lib/systemd/system/colord.service; static; vendor preset: 
enabled)
   Active: active (running) since Mon 2017-07-31 07:48:17 IDT; 3h 0min ago
 Main PID: 939 (colord)
Tasks: 3 (limit: 4915)
   CGroup: /system.slice/colord.service
   └─939 /usr/lib/colord/colord

Jul 31 07:48:16 paz-it systemd[1]: Starting Manage, Install and Generate Color 
Profiles...
Jul 31 07:48:17 paz-it systemd[1]: Started Manage, Install and Generate Color 
Profiles.
Jul 31 07:48:17 paz-it colord[939]: failed to get session [pid 825]: No such 
device or address
Jul 31 07:49:06 paz-it colord[939]: failed to get session [pid 1721]: No such 
device or address

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

Title:
  (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown
  error -2

Status in colord package in Ubuntu:
  Confirmed

Bug description:
  Get that error logged into journalctl

  (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown
  error -2

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-6ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3
  Uname: Linux 3.19.0-12-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17-0ubuntu1
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Thu Apr  9 11:57:02 2015
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 002: ID 046d:c50e Logitech, Inc. Cordless Mouse Receiver
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-12-generic 
root=UUID=7b1f4a51-558f-468f-85e0-f815d2f791e1 ro
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3002
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5W DH Deluxe
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5W DH Deluxe
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTEK COMPUTER INC

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/colord/+bug/1442050/+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 1707487] Re: Bluetooth speaker only plays as mono

2017-07-31 Thread David
Now the Ubuntu updater is doing a "partial upgrade". I hope I don't
break anything?!!

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

Title:
  Bluetooth speaker only plays as mono

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  When I connect my Sony SRS-X1 Bluetooth speaker to Ubuntu, it only
  plays back as "mono" and refuses to use "hi fidelity".

  I have Windows 10 installed on the same laptop and when I've used the
  Bluetooth speaker in Ubuntu, Windows will "forget" the speaker on its
  Bluetooth list. I have to hold in the "reset" button on the speaker
  itself and re-add the speaker to Windows 10. This ONLY HAPPENS if I
  try using this speaker in Ubuntu, which suggests that Ubuntu is
  forcing the speaker into "mono" mode and Windows then sees it as a
  different device?

  Please help.
  I will post all needed outputs as instructed.

  Cheers!
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   david  3626 F...m pulseaudio
   /dev/snd/controlC0:  david  3626 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-07-28 (367 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Package: pulseaudio 1:8.0-0ubuntu3.3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-87.110-generic 4.4.73
  Tags:  xenial
  Uname: Linux 4.4.0-87-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/16/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.21
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: VA50_HC_CR
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Insyde Corp.
  dmi.chassis.version: V2.21
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.21:bd12/16/2013:svnAcer:pnAspireV3-571:pvrV2.21:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnInsydeCorp.:ct10:cvrV2.21:
  dmi.product.name: Aspire V3-571
  dmi.product.version: V2.21
  dmi.sys.vendor: Acer
  modified.conffile..etc.xdg.autostart.pulseaudio.desktop: [modified]
  mtime.conffile..etc.xdg.autostart.pulseaudio.desktop: 
2016-07-29T10:08:04.428983

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1707487/+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 1707487] PulseList.txt

2017-07-31 Thread David
apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1707487/+attachment/4924484/+files/PulseList.txt

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

Title:
  Bluetooth speaker only plays as mono

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  When I connect my Sony SRS-X1 Bluetooth speaker to Ubuntu, it only
  plays back as "mono" and refuses to use "hi fidelity".

  I have Windows 10 installed on the same laptop and when I've used the
  Bluetooth speaker in Ubuntu, Windows will "forget" the speaker on its
  Bluetooth list. I have to hold in the "reset" button on the speaker
  itself and re-add the speaker to Windows 10. This ONLY HAPPENS if I
  try using this speaker in Ubuntu, which suggests that Ubuntu is
  forcing the speaker into "mono" mode and Windows then sees it as a
  different device?

  Please help.
  I will post all needed outputs as instructed.

  Cheers!
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   david  3626 F...m pulseaudio
   /dev/snd/controlC0:  david  3626 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-07-28 (367 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Package: pulseaudio 1:8.0-0ubuntu3.3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-87.110-generic 4.4.73
  Tags:  xenial
  Uname: Linux 4.4.0-87-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/16/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.21
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: VA50_HC_CR
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Insyde Corp.
  dmi.chassis.version: V2.21
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.21:bd12/16/2013:svnAcer:pnAspireV3-571:pvrV2.21:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnInsydeCorp.:ct10:cvrV2.21:
  dmi.product.name: Aspire V3-571
  dmi.product.version: V2.21
  dmi.sys.vendor: Acer
  modified.conffile..etc.xdg.autostart.pulseaudio.desktop: [modified]
  mtime.conffile..etc.xdg.autostart.pulseaudio.desktop: 
2016-07-29T10:08:04.428983

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1707487/+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 1707487] Dependencies.txt

2017-07-31 Thread David
apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1707487/+attachment/4924480/+files/Dependencies.txt

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

Title:
  Bluetooth speaker only plays as mono

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  When I connect my Sony SRS-X1 Bluetooth speaker to Ubuntu, it only
  plays back as "mono" and refuses to use "hi fidelity".

  I have Windows 10 installed on the same laptop and when I've used the
  Bluetooth speaker in Ubuntu, Windows will "forget" the speaker on its
  Bluetooth list. I have to hold in the "reset" button on the speaker
  itself and re-add the speaker to Windows 10. This ONLY HAPPENS if I
  try using this speaker in Ubuntu, which suggests that Ubuntu is
  forcing the speaker into "mono" mode and Windows then sees it as a
  different device?

  Please help.
  I will post all needed outputs as instructed.

  Cheers!
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   david  3626 F...m pulseaudio
   /dev/snd/controlC0:  david  3626 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-07-28 (367 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Package: pulseaudio 1:8.0-0ubuntu3.3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-87.110-generic 4.4.73
  Tags:  xenial
  Uname: Linux 4.4.0-87-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/16/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.21
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: VA50_HC_CR
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Insyde Corp.
  dmi.chassis.version: V2.21
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.21:bd12/16/2013:svnAcer:pnAspireV3-571:pvrV2.21:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnInsydeCorp.:ct10:cvrV2.21:
  dmi.product.name: Aspire V3-571
  dmi.product.version: V2.21
  dmi.sys.vendor: Acer
  modified.conffile..etc.xdg.autostart.pulseaudio.desktop: [modified]
  mtime.conffile..etc.xdg.autostart.pulseaudio.desktop: 
2016-07-29T10:08:04.428983

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1707487/+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 1707487] JournalErrors.txt

2017-07-31 Thread David
apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1707487/+attachment/4924481/+files/JournalErrors.txt

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

Title:
  Bluetooth speaker only plays as mono

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  When I connect my Sony SRS-X1 Bluetooth speaker to Ubuntu, it only
  plays back as "mono" and refuses to use "hi fidelity".

  I have Windows 10 installed on the same laptop and when I've used the
  Bluetooth speaker in Ubuntu, Windows will "forget" the speaker on its
  Bluetooth list. I have to hold in the "reset" button on the speaker
  itself and re-add the speaker to Windows 10. This ONLY HAPPENS if I
  try using this speaker in Ubuntu, which suggests that Ubuntu is
  forcing the speaker into "mono" mode and Windows then sees it as a
  different device?

  Please help.
  I will post all needed outputs as instructed.

  Cheers!
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   david  3626 F...m pulseaudio
   /dev/snd/controlC0:  david  3626 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-07-28 (367 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Package: pulseaudio 1:8.0-0ubuntu3.3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-87.110-generic 4.4.73
  Tags:  xenial
  Uname: Linux 4.4.0-87-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/16/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.21
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: VA50_HC_CR
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Insyde Corp.
  dmi.chassis.version: V2.21
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.21:bd12/16/2013:svnAcer:pnAspireV3-571:pvrV2.21:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnInsydeCorp.:ct10:cvrV2.21:
  dmi.product.name: Aspire V3-571
  dmi.product.version: V2.21
  dmi.sys.vendor: Acer
  modified.conffile..etc.xdg.autostart.pulseaudio.desktop: [modified]
  mtime.conffile..etc.xdg.autostart.pulseaudio.desktop: 
2016-07-29T10:08:04.428983

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1707487/+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 1707487] ProcEnviron.txt

2017-07-31 Thread David
apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1707487/+attachment/4924483/+files/ProcEnviron.txt

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

Title:
  Bluetooth speaker only plays as mono

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  When I connect my Sony SRS-X1 Bluetooth speaker to Ubuntu, it only
  plays back as "mono" and refuses to use "hi fidelity".

  I have Windows 10 installed on the same laptop and when I've used the
  Bluetooth speaker in Ubuntu, Windows will "forget" the speaker on its
  Bluetooth list. I have to hold in the "reset" button on the speaker
  itself and re-add the speaker to Windows 10. This ONLY HAPPENS if I
  try using this speaker in Ubuntu, which suggests that Ubuntu is
  forcing the speaker into "mono" mode and Windows then sees it as a
  different device?

  Please help.
  I will post all needed outputs as instructed.

  Cheers!
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   david  3626 F...m pulseaudio
   /dev/snd/controlC0:  david  3626 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-07-28 (367 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Package: pulseaudio 1:8.0-0ubuntu3.3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-87.110-generic 4.4.73
  Tags:  xenial
  Uname: Linux 4.4.0-87-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/16/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.21
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: VA50_HC_CR
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Insyde Corp.
  dmi.chassis.version: V2.21
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.21:bd12/16/2013:svnAcer:pnAspireV3-571:pvrV2.21:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnInsydeCorp.:ct10:cvrV2.21:
  dmi.product.name: Aspire V3-571
  dmi.product.version: V2.21
  dmi.sys.vendor: Acer
  modified.conffile..etc.xdg.autostart.pulseaudio.desktop: [modified]
  mtime.conffile..etc.xdg.autostart.pulseaudio.desktop: 
2016-07-29T10:08:04.428983

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1707487/+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 1707487] ProcCpuinfoMinimal.txt

2017-07-31 Thread David
apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1707487/+attachment/4924482/+files/ProcCpuinfoMinimal.txt

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

Title:
  Bluetooth speaker only plays as mono

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  When I connect my Sony SRS-X1 Bluetooth speaker to Ubuntu, it only
  plays back as "mono" and refuses to use "hi fidelity".

  I have Windows 10 installed on the same laptop and when I've used the
  Bluetooth speaker in Ubuntu, Windows will "forget" the speaker on its
  Bluetooth list. I have to hold in the "reset" button on the speaker
  itself and re-add the speaker to Windows 10. This ONLY HAPPENS if I
  try using this speaker in Ubuntu, which suggests that Ubuntu is
  forcing the speaker into "mono" mode and Windows then sees it as a
  different device?

  Please help.
  I will post all needed outputs as instructed.

  Cheers!
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   david  3626 F...m pulseaudio
   /dev/snd/controlC0:  david  3626 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-07-28 (367 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Package: pulseaudio 1:8.0-0ubuntu3.3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-87.110-generic 4.4.73
  Tags:  xenial
  Uname: Linux 4.4.0-87-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/16/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.21
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: VA50_HC_CR
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Insyde Corp.
  dmi.chassis.version: V2.21
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.21:bd12/16/2013:svnAcer:pnAspireV3-571:pvrV2.21:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnInsydeCorp.:ct10:cvrV2.21:
  dmi.product.name: Aspire V3-571
  dmi.product.version: V2.21
  dmi.sys.vendor: Acer
  modified.conffile..etc.xdg.autostart.pulseaudio.desktop: [modified]
  mtime.conffile..etc.xdg.autostart.pulseaudio.desktop: 
2016-07-29T10:08:04.428983

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1707487/+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 1707487] CurrentDmesg.txt

2017-07-31 Thread David
apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1707487/+attachment/4924479/+files/CurrentDmesg.txt

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

Title:
  Bluetooth speaker only plays as mono

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  When I connect my Sony SRS-X1 Bluetooth speaker to Ubuntu, it only
  plays back as "mono" and refuses to use "hi fidelity".

  I have Windows 10 installed on the same laptop and when I've used the
  Bluetooth speaker in Ubuntu, Windows will "forget" the speaker on its
  Bluetooth list. I have to hold in the "reset" button on the speaker
  itself and re-add the speaker to Windows 10. This ONLY HAPPENS if I
  try using this speaker in Ubuntu, which suggests that Ubuntu is
  forcing the speaker into "mono" mode and Windows then sees it as a
  different device?

  Please help.
  I will post all needed outputs as instructed.

  Cheers!
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   david  3626 F...m pulseaudio
   /dev/snd/controlC0:  david  3626 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-07-28 (367 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Package: pulseaudio 1:8.0-0ubuntu3.3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-87.110-generic 4.4.73
  Tags:  xenial
  Uname: Linux 4.4.0-87-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/16/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.21
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: VA50_HC_CR
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Insyde Corp.
  dmi.chassis.version: V2.21
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.21:bd12/16/2013:svnAcer:pnAspireV3-571:pvrV2.21:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnInsydeCorp.:ct10:cvrV2.21:
  dmi.product.name: Aspire V3-571
  dmi.product.version: V2.21
  dmi.sys.vendor: Acer
  modified.conffile..etc.xdg.autostart.pulseaudio.desktop: [modified]
  mtime.conffile..etc.xdg.autostart.pulseaudio.desktop: 
2016-07-29T10:08:04.428983

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1707487/+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 1707487] Re: Bluetooth speaker only plays as mono

2017-07-31 Thread David
apport information

** Tags added: apport-collected xenial

** Description changed:

  When I connect my Sony SRS-X1 Bluetooth speaker to Ubuntu, it only plays
  back as "mono" and refuses to use "hi fidelity".
  
  I have Windows 10 installed on the same laptop and when I've used the
  Bluetooth speaker in Ubuntu, Windows will "forget" the speaker on its
  Bluetooth list. I have to hold in the "reset" button on the speaker
  itself and re-add the speaker to Windows 10. This ONLY HAPPENS if I try
  using this speaker in Ubuntu, which suggests that Ubuntu is forcing the
  speaker into "mono" mode and Windows then sees it as a different
  device?
  
  Please help.
  I will post all needed outputs as instructed.
  
  Cheers!
+ --- 
+ ApportVersion: 2.20.1-0ubuntu2.10
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/pcmC0D0c:   david  3626 F...m pulseaudio
+  /dev/snd/controlC0:  david  3626 F pulseaudio
+ CurrentDesktop: Unity
+ DistroRelease: Ubuntu 16.04
+ EcryptfsInUse: Yes
+ InstallationDate: Installed on 2016-07-28 (367 days ago)
+ InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
+ Package: pulseaudio 1:8.0-0ubuntu3.3
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 4.4.0-87.110-generic 4.4.73
+ Tags:  xenial
+ Uname: Linux 4.4.0-87-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 12/16/2013
+ dmi.bios.vendor: Insyde Corp.
+ dmi.bios.version: V2.21
+ dmi.board.asset.tag: Type2 - Board Asset Tag
+ dmi.board.name: VA50_HC_CR
+ dmi.board.vendor: Acer
+ dmi.board.version: Type2 - Board Version
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: Insyde Corp.
+ dmi.chassis.version: V2.21
+ dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.21:bd12/16/2013:svnAcer:pnAspireV3-571:pvrV2.21:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnInsydeCorp.:ct10:cvrV2.21:
+ dmi.product.name: Aspire V3-571
+ dmi.product.version: V2.21
+ dmi.sys.vendor: Acer
+ modified.conffile..etc.xdg.autostart.pulseaudio.desktop: [modified]
+ mtime.conffile..etc.xdg.autostart.pulseaudio.desktop: 
2016-07-29T10:08:04.428983

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1707487/+attachment/4924478/+files/AlsaInfo.txt

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

Title:
  Bluetooth speaker only plays as mono

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  When I connect my Sony SRS-X1 Bluetooth speaker to Ubuntu, it only
  plays back as "mono" and refuses to use "hi fidelity".

  I have Windows 10 installed on the same laptop and when I've used the
  Bluetooth speaker in Ubuntu, Windows will "forget" the speaker on its
  Bluetooth list. I have to hold in the "reset" button on the speaker
  itself and re-add the speaker to Windows 10. This ONLY HAPPENS if I
  try using this speaker in Ubuntu, which suggests that Ubuntu is
  forcing the speaker into "mono" mode and Windows then sees it as a
  different device?

  Please help.
  I will post all needed outputs as instructed.

  Cheers!
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   david  3626 F...m pulseaudio
   /dev/snd/controlC0:  david  3626 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-07-28 (367 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Package: pulseaudio 1:8.0-0ubuntu3.3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-87.110-generic 4.4.73
  Tags:  xenial
  Uname: Linux 4.4.0-87-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/16/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.21
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: VA50_HC_CR
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Insyde Corp.
  dmi.chassis.version: V2.21
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.21:bd12/16/2013:svnAcer:pnAspireV3-571:pvrV2.21:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnInsydeCorp.:ct10:cvrV2.21:
  dmi.product.name: Aspire V3-571
  dmi.product.version: V2.21
  dmi.sys.vendor: Acer
  modified.conffile..etc.xdg.autostart.pulseaudio.desktop: [modified]
  mtime.conffile..etc.xdg.autostart.pulseaudio.desktop: 
2016-07-29T10:08:04.428983

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : 

[Touch-packages] [Bug 1663528] Re: pulseaudio assert failure: pulseaudio: mixer.c:929: snd_mixer_elem_get_callback_private: Assertion `mixer' failed.

2017-07-31 Thread Daniel van Vugt
** Tags added: artful

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

Title:
  pulseaudio assert failure: pulseaudio: mixer.c:929:
  snd_mixer_elem_get_callback_private: Assertion `mixer' failed.

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/a8bcc8185d5b1da4614bcdcf99daf57011bf9250

  ---

  Sidenote: Imediatly got that crash after the apt-xapian-index one (
  lp:1663524 ); does not know if it can exist a possible relationship
  between them.

  Got an other crash, and that time 'sound' is fully lost (pulseaudio
  not reloaded). Wonder if lp:1662860 can be concerned.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: pulseaudio 1:10.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.9.0-16.17-generic 4.9.6
  Uname: Linux 4.9.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AssertionMessage: pulseaudio: mixer.c:929: 
snd_mixer_elem_get_callback_private: Assertion `mixer' failed.
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  oem4084 F pulseaudio
   /dev/snd/controlC0:  oem4084 F pulseaudio
  CurrentDesktop: GNOME
  Date: Fri Feb 10 09:55:45 2017
  ExecutablePath: /usr/bin/pulseaudio
  ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: pulseaudio
  StacktraceTop:
   __assert_fail_base (fmt=, 
assertion=assertion@entry=0x7f92818e7188 "mixer", 
file=file@entry=0x7f92818e7419 "mixer.c", line=line@entry=929, 
function=function@entry=0x7f92818e76a0 "snd_mixer_elem_get_callback_private") 
at assert.c:92
   __GI___assert_fail (assertion=0x7f92818e7188 "mixer", file=0x7f92818e7419 
"mixer.c", line=929, function=0x7f92818e76a0 
"snd_mixer_elem_get_callback_private") at assert.c:101
   snd_mixer_elem_get_callback_private () from 
/usr/lib/x86_64-linux-gnu/libasound.so.2
   ?? () from /usr/lib/pulse-10.0/modules/module-alsa-card.so
   ?? () from /usr/lib/pulse-10.0/modules/module-alsa-card.so
  Title: pulseaudio assert failure: pulseaudio: mixer.c:929: 
snd_mixer_elem_get_callback_private: Assertion `mixer' failed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom colord dip lpadmin nvidia-persistenced plugdev 
sambashare sudo users
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3002
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5W DH Deluxe
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5W DH Deluxe
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTEK COMPUTER INC

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1663528/+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 1707487] Re: Bluetooth speaker only plays as mono

2017-07-31 Thread David
Thanks. I tried it, got this:

Quote "You need to run 'sudo apt-get install python-apport' for apport-
collect to work."

I guess I need to run "sudo apt-get install python-apport" first?

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

Title:
  Bluetooth speaker only plays as mono

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  When I connect my Sony SRS-X1 Bluetooth speaker to Ubuntu, it only
  plays back as "mono" and refuses to use "hi fidelity".

  I have Windows 10 installed on the same laptop and when I've used the
  Bluetooth speaker in Ubuntu, Windows will "forget" the speaker on its
  Bluetooth list. I have to hold in the "reset" button on the speaker
  itself and re-add the speaker to Windows 10. This ONLY HAPPENS if I
  try using this speaker in Ubuntu, which suggests that Ubuntu is
  forcing the speaker into "mono" mode and Windows then sees it as a
  different device?

  Please help.
  I will post all needed outputs as instructed.

  Cheers!
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   david  3626 F...m pulseaudio
   /dev/snd/controlC0:  david  3626 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-07-28 (367 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Package: pulseaudio 1:8.0-0ubuntu3.3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-87.110-generic 4.4.73
  Tags:  xenial
  Uname: Linux 4.4.0-87-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/16/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.21
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: VA50_HC_CR
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Insyde Corp.
  dmi.chassis.version: V2.21
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.21:bd12/16/2013:svnAcer:pnAspireV3-571:pvrV2.21:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnInsydeCorp.:ct10:cvrV2.21:
  dmi.product.name: Aspire V3-571
  dmi.product.version: V2.21
  dmi.sys.vendor: Acer
  modified.conffile..etc.xdg.autostart.pulseaudio.desktop: [modified]
  mtime.conffile..etc.xdg.autostart.pulseaudio.desktop: 
2016-07-29T10:08:04.428983

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1707487/+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 1690054] Re: pulseaudio crashed with SIGABRT in pa_sink_input_attach() from pa_sink_attach_within_thread() from pa_sink_process_msg() from sink_process_msg() from asyncmsgq_read_

2017-07-31 Thread Daniel van Vugt
** Tags added: artful

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

Title:
  pulseaudio crashed with SIGABRT in pa_sink_input_attach() from
  pa_sink_attach_within_thread() from pa_sink_process_msg() from
  sink_process_msg() from asyncmsgq_read_work()

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
pulseaudio.  This problem was most recently seen with package version 
1:10.0-1ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/cba7a3bcc7f260f8aab11c71680f8742fbbb03b1 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1690054/+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 1703271] Re: pulseaudio crashed with SIGABRT in device_start_waiting_for_profiles() from pa_bluetooth_transport_set_state() from profile_new_connection() from profile_handler() f

2017-07-31 Thread Daniel van Vugt
See also bug 1703272

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

Title:
  pulseaudio crashed with SIGABRT in device_start_waiting_for_profiles()
  from pa_bluetooth_transport_set_state() from profile_new_connection()
  from profile_handler() from _dbus_object_tree_dispatch_and_unlock()

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
pulseaudio.  This problem was most recently seen with package version 
1:10.0-1ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/f2718ea2383be2a9cda88115eeb71652d9444a7d 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1703271/+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 1703272] Re: pulseaudio crashed with SIGABRT in device_start_waiting_for_profiles() from pa_bluetooth_transport_set_state() from pa_bluetooth_transport_put() from endpoint_set_co

2017-07-31 Thread Daniel van Vugt
See also bug 1703271

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

Title:
  pulseaudio crashed with SIGABRT in device_start_waiting_for_profiles()
  from pa_bluetooth_transport_set_state() from
  pa_bluetooth_transport_put() from endpoint_set_configuration() from
  endpoint_handler()

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
pulseaudio.  This problem was most recently seen with package version 
1:8.0-0ubuntu3.3, the problem page at 
https://errors.ubuntu.com/problem/80ef14dcf1628eef17ef830d6c65f4c9ee035457 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1703272/+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 1703272] Re: pulseaudio crashed with SIGABRT in device_start_waiting_for_profiles() from pa_bluetooth_transport_set_state() from pa_bluetooth_transport_put() from endpoint_set_co

2017-07-31 Thread Daniel van Vugt
Although it's hard to tell if "pulseaudio (1:10.0-2ubuntu1) artful"
fixed this because there are zero instances of this crash in artful. We
won't really know until the same fixes get backported to xenial. And
it's possibly still a bit too early for that.

** Changed in: pulseaudio (Ubuntu)
   Status: In Progress => Confirmed

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

Title:
  pulseaudio crashed with SIGABRT in device_start_waiting_for_profiles()
  from pa_bluetooth_transport_set_state() from
  pa_bluetooth_transport_put() from endpoint_set_configuration() from
  endpoint_handler()

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
pulseaudio.  This problem was most recently seen with package version 
1:8.0-0ubuntu3.3, the problem page at 
https://errors.ubuntu.com/problem/80ef14dcf1628eef17ef830d6c65f4c9ee035457 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1703272/+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 1703271] Re: pulseaudio crashed with SIGABRT in device_start_waiting_for_profiles() from pa_bluetooth_transport_set_state() from profile_new_connection() from profile_handler() f

2017-07-31 Thread Daniel van Vugt
Although it's hard to tell if "pulseaudio (1:10.0-2ubuntu1) artful"
fixed this because there are zero instances of this crash in artful. We
won't really know until that version gets backported to zesty. And it's
possibly still a bit too early for that.

** Changed in: pulseaudio (Ubuntu)
   Status: In Progress => Confirmed

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

Title:
  pulseaudio crashed with SIGABRT in device_start_waiting_for_profiles()
  from pa_bluetooth_transport_set_state() from profile_new_connection()
  from profile_handler() from _dbus_object_tree_dispatch_and_unlock()

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
pulseaudio.  This problem was most recently seen with package version 
1:10.0-1ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/f2718ea2383be2a9cda88115eeb71652d9444a7d 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1703271/+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 1707487] Re: Bluetooth speaker only plays as mono

2017-07-31 Thread Daniel van Vugt
Open a terminal window (Ctrl+Alt+T) and then run:

sudo apt install -y apport
apport-collect 1707487

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

Title:
  Bluetooth speaker only plays as mono

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  When I connect my Sony SRS-X1 Bluetooth speaker to Ubuntu, it only
  plays back as "mono" and refuses to use "hi fidelity".

  I have Windows 10 installed on the same laptop and when I've used the
  Bluetooth speaker in Ubuntu, Windows will "forget" the speaker on its
  Bluetooth list. I have to hold in the "reset" button on the speaker
  itself and re-add the speaker to Windows 10. This ONLY HAPPENS if I
  try using this speaker in Ubuntu, which suggests that Ubuntu is
  forcing the speaker into "mono" mode and Windows then sees it as a
  different device?

  Please help.
  I will post all needed outputs as instructed.

  Cheers!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1707487/+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 349469] Re: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable

2017-07-31 Thread Colin Watson
** Attachment removed: "926BF9B9908245F6.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/349469/+attachment/4924027/+files/926BF9B9908245F6.jpg

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

Title:
  debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by
  another process: Resource temporarily unavailable

Status in Aptdaemon:
  Confirmed
Status in Debconf:
  New
Status in aptdaemon package in Ubuntu:
  Incomplete
Status in debconf package in Ubuntu:
  Triaged

Bug description:
  Upgrading packages that use debconf sometimes fail with the following
  error:

  debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by
  another process: Resource temporarily unavailable

To manage notifications about this bug go to:
https://bugs.launchpad.net/aptdaemon/+bug/349469/+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 1707487] Re: Bluetooth speaker only plays as mono

2017-07-31 Thread David
Who do I run "apport-collect 1707487"?

Please tell me how to do this.

Many thanks.

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

Title:
  Bluetooth speaker only plays as mono

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  When I connect my Sony SRS-X1 Bluetooth speaker to Ubuntu, it only
  plays back as "mono" and refuses to use "hi fidelity".

  I have Windows 10 installed on the same laptop and when I've used the
  Bluetooth speaker in Ubuntu, Windows will "forget" the speaker on its
  Bluetooth list. I have to hold in the "reset" button on the speaker
  itself and re-add the speaker to Windows 10. This ONLY HAPPENS if I
  try using this speaker in Ubuntu, which suggests that Ubuntu is
  forcing the speaker into "mono" mode and Windows then sees it as a
  different device?

  Please help.
  I will post all needed outputs as instructed.

  Cheers!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1707487/+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 1585886] Re: WiFi indicator icon disappears in Ubuntu 16.04

2017-07-31 Thread Dilip
Wifi icon on top panel disappears for me as well (16.04 + Unity). I have
to use settings > network to deal with the WiFi connections. Happens
mostly when I " suspend " and resume my PC.

I do not use an ethernet cable. So, unable to comment on that.


sudo service network-manager restart
nm-applet

These commands, when active on terminal brings back the icon. But, the
WiFi network listing are missing at times.

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

Title:
  WiFi indicator icon disappears in Ubuntu 16.04

Status in indicator-applet package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Dear all,

  Can someone confirm an occasionally missing WiFi indicator tray icon?

  Sometimes it happens that the icon is not displayed although the WiFi
  connection is working.

  Please see also the attached screenshot.

  Warmly,

  ~Robert

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-applet/+bug/1585886/+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 1587142] Re: Shutdown hangs in md kworker after "Reached target Shutdown."

2017-07-31 Thread Jim Nijkamp
Confirm on this bug with hardware:

HP Z230, Intel Raid bios, Ubuntu 16.04.2.

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

Title:
  Shutdown hangs in md kworker after "Reached target Shutdown."

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I'm booting a fully patched 16.04 from an Intel Rapid Storage
  Technology enterprise RAID1 volume (ThinkServer TS140 with two SATA
  ST1000NM0033-9ZM drives, ext4 root partition, no LVM, UEFI mode).

  If the RAID volume is recovering or resyncing for whatever reason, then `sudo 
systemctl reboot` and `sudo systemctl poweroff` work fine (I had to `sudo 
systemctl --now disable lvm2-lvmetad lvm2-lvmpolld lvm2-monitor` in order to 
consistently get that). However, once the recovery/resync is complete and 
clean, the reboot and poweroff commands above hang forever after "Reached 
target Shutdown.". Note that issuing `sudo swapoff -a` beforehand (suggested in 
the bug #1464917) does not help.
  [EDIT]Actually, the shutdown also hangs from time to time during a resync. 
But I've never seen it succeed once the resync is complete.[/EDIT]

  Then, if the server has been forcibly restarted with the power button,
  the Intel Matrix Storage Manager indicates a "Normal" status for the
  RAID1 volume, but Ubuntu then resyncs the volume anyway:

  [1.223649] md: bind
  [1.228426] md: bind
  [1.230030] md: bind
  [1.230738] md: bind
  [1.232985] usbcore: registered new interface driver usbhid
  [1.233494] usbhid: USB HID core driver
  [1.234022] md: raid1 personality registered for level 1
  [1.234876] md/raid1:md126: not clean -- starting background reconstruction
  [1.234956] input: CHESEN USB Keyboard as 
/devices/pci:00/:00:14.0/usb3/3-10/3-10:1.0/0003:0A81:0101.0001/input/input5
  [1.236273] md/raid1:md126: active with 2 out of 2 mirrors
  [1.236797] md126: detected capacity change from 0 to 1000202043392
  [1.246271] md: md126 switched to read-write mode.
  [1.246834] md: resync of RAID array md126
  [1.247325] md: minimum _guaranteed_  speed: 1000 KB/sec/disk.
  [1.247503]  md126: p1 p2 p3 p4
  [1.248269] md: using maximum available idle IO bandwidth (but not more 
than 20 KB/sec) for resync.
  [1.248774] md: using 128k window, over a total of 976759940k.

  Note that the pain of "resync upon every (re)boot" cannot even be a
  bit relieved thanks to bitmaps because mdadm does not support them for
  IMSM containers:

  $ sudo mdadm --grow --bitmap=internal /dev/md126
  mdadm: Cannot add bitmaps to sub-arrays yet

  I also get this in syslog during boot when the individual drives are
  detected, but this seems to be harmless:

  May 30 17:26:07 wssrv1 systemd-udevd[608]: Process '/sbin/mdadm --incremental 
/dev/sdb --offroot' failed with exit code 1.
  May 30 17:26:07 wssrv1 systemd-udevd[608]: Process '/lib/udev/hdparm' failed 
with exit code 1.

  May 30 17:26:07 wssrv1 systemd-udevd[606]: Process '/sbin/mdadm --incremental 
/dev/sda --offroot' failed with exit code 1.
  May 30 17:26:07 wssrv1 systemd-udevd[606]: Process '/lib/udev/hdparm' failed 
with exit code 1.

  During a resync, `sudo sh -c 'echo idle >
  /sys/block/md126/md/sync_action'` actually stops it as expected, but
  it restarts immediately though nothing seems to have triggered it:

  May 30 18:17:02 wssrv1 kernel: [ 3106.826710] md: md126: resync interrupted.
  May 30 18:17:02 wssrv1 kernel: [ 3106.836320] md: checkpointing resync of 
md126.
  May 30 18:17:02 wssrv1 kernel: [ 3106.836623] md: resync of RAID array md126
  May 30 18:17:02 wssrv1 kernel: [ 3106.836625] md: minimum _guaranteed_  
speed: 1000 KB/sec/disk.
  May 30 18:17:02 wssrv1 kernel: [ 3106.836626] md: using maximum available 
idle IO bandwidth (but not more than 20 KB/sec) for resync.
  May 30 18:17:02 wssrv1 kernel: [ 3106.836627] md: using 128k window, over a 
total of 976759940k.
  May 30 18:17:02 wssrv1 kernel: [ 3106.836628] md: resuming resync of md126 
from checkpoint.
  May 30 18:17:02 wssrv1 mdadm[982]: RebuildStarted event detected on md device 
/dev/md/Volume0

  I attach screenshots of the hanging shutdown log after a `sudo sh -c 'echo 8 
> /proc/sys/kernel/printk'`. The second screenshot shows that the kernel has 
deadlocked in md_write_start(). Note that `sudo systemctl start debug-shell` is 
unusable on this machine at this point because Ctrl+Alt+F9 brings tty9 without 
any keyboard.
  [EDIT]But I can still switch back to tty1.[/EDIT]

  I have also tried with much lower values for vm.dirty_background_ratio
  and vm.dirty_ratio, but to no avail.

  Linux 4.6.0-040600-generic_4.6.0-040600.201605151930_amd64 from
  http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6-yakkety/ did not
  help either.

  More information below:

  $ lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

2017-07-31 Thread Andreas Lindhé
Is this bug confirmed resolved for any version of Ubuntu? What release
do I need to get my friends migrated to, in order for this to not be a
problem?

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

Title:
  Kernels not autoremoving, causing out of space error on LVM or
  Encrypted installation or on any installation, when /boot partition
  gets full

Status in unattended-upgrades:
  New
Status in unattended-upgrades package in Ubuntu:
  Fix Released

Bug description:
  Currently if one chooses to use LVM or encrypted install, a /boot
  partition is created of 236Mb

  Once kernel updates start being released this partition soon fills
  until people are left unable to upgrade.

  While you and I might know that we need to watch partition space, many
  of the people we have installing think that a windows disk is a disk
  and not a partition, education is probably the key - but in the
  meantime support venues keep needing to deal with the fact the
  partition is too small and/or old kernels are not purged as new ones
  install.

  For workaround and sytem repair, see
  https://help.ubuntu.com/community/RemoveOldKernels

To manage notifications about this bug go to:
https://bugs.launchpad.net/unattended-upgrades/+bug/1357093/+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


<    1   2