[Touch-packages] [Bug 1673645] Re: A bunch of text goes missing sporadically.

2017-07-15 Thread NoBugs!
May or may not be the same as the icons disappearing bug that happens in 4.4. I 
updated again hoping that it would be fixed but it isn't!!
https://askubuntu.com/questions/582980/missing-letters-in-menus-and-folder-names/606583#comment1399040_606583

Seems it never happens on 4.2 so it is likely the Linux version issue.

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

Title:
  A bunch of text goes missing sporadically.

Status in xorg package in Ubuntu:
  New

Bug description:
  Almost every application is missing all or some characters rendering
  to screen. I see it in most consoles, dialogs, and the upper right
  hand calendar. Sometimes closing and reopening fixes it.

  This may be happening after close and reopen as I don't remember
  seeing this happen right after starting up the laptop.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 4.4.0-66.87~14.04.1-generic 4.4.44
  Uname: Linux 4.4.0-66-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Mar 16 18:47:57 2017
  DistUpgraded: 2014-04-19 04:44:12,758 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus: nvidia-340, 340.101, 4.4.0-64-generic, x86_64: installed
  EcryptfsInUse: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:054e]
 Subsystem: Dell GeForce GT 630M [1028:054e]
  InstallationDate: Installed on 2013-11-23 (1209 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: Dell Inc. XPS L521X
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-66-generic 
root=UUID=8e997c12-0ee0-422b-a7e4-a7cb0a74f38f ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to trusty on 2014-04-19 (1062 days ago)
  dmi.bios.date: 12/17/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0C5Y96
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A16
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd12/17/2013:svnDellInc.:pnXPSL521X:pvrA16:rvnDellInc.:rn0C5Y96:rvrA00:cvnDellInc.:ct8:cvrA16:
  dmi.product.name: XPS L521X
  dmi.product.version: A16
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.6
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.6
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.910-0ubuntu1.7
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Tue Mar 14 19:27:26 2017
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id4333 
   vendor AUO
  xserver.version: 2:1.15.1-0ubuntu2.7

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1673645/+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 1704616] Re: Display settings mess up when screens rearranged in xfce-display-settings

2017-07-15 Thread Patrick Dunford
A bit more testing shows completely random results each time the second
configuration is applied. For example this picture shows the problems
now occurring on the Sony screen rather than the Dell screen.

The biggest effect seen on the Sony screen in this instance included
mouse position offset where the mouse is registering in a different
place from where the pointer is.

As soon as I was able to restore the original configuration everything
works fine.

Attachment showing the messed up display. The computer had just been
restarted and there were no programs running, so the stuff displayed in
the top section of the screen was not from any running applications.

** Attachment added: "IMG_20170716_170942.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1704616/+attachment/4915453/+files/IMG_20170716_170942.jpg

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

Title:
  Display settings mess up when screens rearranged in xfce-display-
  settings

Status in xorg package in Ubuntu:
  New

Bug description:
  I have a Dell 1280x1024 19" screen and Sony 1366x768 32" screen. Due
  to the ports they are connected to on the video card they appear by
  default in xfce-display-settings in the reverse to their physical
  layout.

  On previous versions of Xubuntu there has not been any problem with
  rearranging the display order. On artful I can only get things to work
  properly if I leave the display order to the default.

  If I try to rearrange the display order on artful all sorts of weird
  things happen. The 19" screen only uses two thirds of its vertical
  height to display the picture, the rest is drawn as white. The taskbar
  disappears completely. The mouse has to be on the opposite screen to
  the one where you are working in order to be able to click on
  anything.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
  Uname: Linux 4.10.0-26-generic x86_64
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sun Jul 16 16:27:49 2017
  InstallationDate: Installed on 2017-07-16 (0 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170704)
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1704616/+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 1704616] Re: Display settings mess up when screens rearranged in xfce-display-settings

2017-07-15 Thread Patrick Dunford
And here is the configuration that doesn't work. If I apply this the
Dell screen will have a part of it that is duplicated from the Sony
screen, the taskbar and even the mouse position will be offset from this
duplicate part (will try to get a screenshot of it)

** Attachment added: "not ok.png"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1704616/+attachment/4915451/+files/not%20ok.png

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

Title:
  Display settings mess up when screens rearranged in xfce-display-
  settings

Status in xorg package in Ubuntu:
  New

Bug description:
  I have a Dell 1280x1024 19" screen and Sony 1366x768 32" screen. Due
  to the ports they are connected to on the video card they appear by
  default in xfce-display-settings in the reverse to their physical
  layout.

  On previous versions of Xubuntu there has not been any problem with
  rearranging the display order. On artful I can only get things to work
  properly if I leave the display order to the default.

  If I try to rearrange the display order on artful all sorts of weird
  things happen. The 19" screen only uses two thirds of its vertical
  height to display the picture, the rest is drawn as white. The taskbar
  disappears completely. The mouse has to be on the opposite screen to
  the one where you are working in order to be able to click on
  anything.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
  Uname: Linux 4.10.0-26-generic x86_64
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sun Jul 16 16:27:49 2017
  InstallationDate: Installed on 2017-07-16 (0 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170704)
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1704616/+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 1704616] Re: Display settings mess up when screens rearranged in xfce-display-settings

2017-07-15 Thread Patrick Dunford
Done some more playing and swapped the screens ports around on the card
to make it detect in the same order as I want them on the screen. It
basically doesn't cope with screens that have different resolutions
vertically. Attached picture of the supported positioning of the two
screens.

** Attachment added: "ok.png"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1704616/+attachment/4915450/+files/ok.png

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

Title:
  Display settings mess up when screens rearranged in xfce-display-
  settings

Status in xorg package in Ubuntu:
  New

Bug description:
  I have a Dell 1280x1024 19" screen and Sony 1366x768 32" screen. Due
  to the ports they are connected to on the video card they appear by
  default in xfce-display-settings in the reverse to their physical
  layout.

  On previous versions of Xubuntu there has not been any problem with
  rearranging the display order. On artful I can only get things to work
  properly if I leave the display order to the default.

  If I try to rearrange the display order on artful all sorts of weird
  things happen. The 19" screen only uses two thirds of its vertical
  height to display the picture, the rest is drawn as white. The taskbar
  disappears completely. The mouse has to be on the opposite screen to
  the one where you are working in order to be able to click on
  anything.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
  Uname: Linux 4.10.0-26-generic x86_64
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sun Jul 16 16:27:49 2017
  InstallationDate: Installed on 2017-07-16 (0 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170704)
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1704616/+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 1704616] [NEW] Display settings mess up when screens rearranged in xfce-display-settings

2017-07-15 Thread Patrick Dunford
Public bug reported:

I have a Dell 1280x1024 19" screen and Sony 1366x768 32" screen. Due to
the ports they are connected to on the video card they appear by default
in xfce-display-settings in the reverse to their physical layout.

On previous versions of Xubuntu there has not been any problem with
rearranging the display order. On artful I can only get things to work
properly if I leave the display order to the default.

If I try to rearrange the display order on artful all sorts of weird
things happen. The 19" screen only uses two thirds of its vertical
height to display the picture, the rest is drawn as white. The taskbar
disappears completely. The mouse has to be on the opposite screen to the
one where you are working in order to be able to click on anything.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
Uname: Linux 4.10.0-26-generic x86_64
ApportVersion: 2.20.5-0ubuntu5
Architecture: amd64
CurrentDesktop: XFCE
Date: Sun Jul 16 16:27:49 2017
InstallationDate: Installed on 2017-07-16 (0 days ago)
InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170704)
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug artful resolution

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

Title:
  Display settings mess up when screens rearranged in xfce-display-
  settings

Status in xorg package in Ubuntu:
  New

Bug description:
  I have a Dell 1280x1024 19" screen and Sony 1366x768 32" screen. Due
  to the ports they are connected to on the video card they appear by
  default in xfce-display-settings in the reverse to their physical
  layout.

  On previous versions of Xubuntu there has not been any problem with
  rearranging the display order. On artful I can only get things to work
  properly if I leave the display order to the default.

  If I try to rearrange the display order on artful all sorts of weird
  things happen. The 19" screen only uses two thirds of its vertical
  height to display the picture, the rest is drawn as white. The taskbar
  disappears completely. The mouse has to be on the opposite screen to
  the one where you are working in order to be able to click on
  anything.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
  Uname: Linux 4.10.0-26-generic x86_64
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sun Jul 16 16:27:49 2017
  InstallationDate: Installed on 2017-07-16 (0 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170704)
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1704616/+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 608069] Re: [Realtek ALC268] subwoofer does not work

2017-07-15 Thread Launchpad Bug Tracker
[Expired for pulseaudio (Ubuntu) because there has been no activity for
60 days.]

** Changed in: pulseaudio (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  [Realtek ALC268] subwoofer does not work

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  Binary package hint: pulseaudio

  hey there,

  on this acer aspire 7720 running ubuntu 10.04, the subwoofer does not work. 
Sound is there, but tinny.
  Support seems to be very generic.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: pulseaudio 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu14
  ProcVersionSignature: Ubuntu 2.6.32-23.37-generic 2.6.32.15+drm33.5
  Uname: Linux 2.6.32-23-generic i686
  NonfreeKernelModules: nvidia
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC268 Analog [ALC268 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC268 Analog [ALC268 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  richard3834 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0x9b30 irq 17'
 Mixer name : 'Realtek ALC268'
 Components : 'HDA:10ec0268,1025011e,0013 
HDA:14f12c06,1025011e,0010'
 Controls  : 11
 Simple ctrls  : 8
  Date: Wed Jul 21 15:14:59 2010
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SelectedCard: 0 Intel HDA-Intel - HDA Intel
  SourcePackage: pulseaudio
  Symptom: audio
  Title: [Realtek ALC268] PA test tone failed (alsa tone succeeded)
  dmi.bios.date: 01/05/2008
  dmi.bios.vendor: Acer
  dmi.bios.version: V1.27
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Poyang
  dmi.board.vendor: Acer
  dmi.board.version: V1.27
  dmi.chassis.type: 1
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.27
  dmi.modalias: 
dmi:bvnAcer:bvrV1.27:bd01/05/2008:svnAcer:pnAspire7720:pvrV1.27:rvnAcer:rnPoyang:rvrV1.27:cvnAcer:ct1:cvrV1.27:
  dmi.product.name: Aspire 7720
  dmi.product.version: V1.27
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/608069/+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 1597737] Re: Microphone resets to full volume after reboot

2017-07-15 Thread Launchpad Bug Tracker
[Expired for pulseaudio (Ubuntu) because there has been no activity for
60 days.]

** Changed in: pulseaudio (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Microphone resets to full volume after reboot

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  According to https://wiki.ubuntu.com/Sound:

  "when you plug in a microphone, input volume should be the same as
  when you last used a microphone, even if Ubuntu has restarted since
  then."

  Rebooting the phone resets the microphone to full volume.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1597737/+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 1665556] Re: Pulseaudio crashes on startup of rhythmbox

2017-07-15 Thread Launchpad Bug Tracker
[Expired for pulseaudio (Ubuntu) because there has been no activity for
60 days.]

** Changed in: pulseaudio (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Pulseaudio crashes on startup of rhythmbox

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  Starting up rhythmbox lets pulseaudio crash. The applet in the ubuntu
  status bar shows no audio possible, and hotkeys for audio level do
  also refuse to work.

  $ lsb_release -rd
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04
  $ apt-cache policy rhythmbox
  rhythmbox:
Installiert:   3.3-1ubuntu7
Installationskandidat: 3.3-1ubuntu7
Versionstabelle:
   *** 3.3-1ubuntu7 500
  500 http://de.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status
  $ apt-cache policy pulseaudio
  pulseaudio:
Installiert:   1:8.0-0ubuntu3.2
Installationskandidat: 1:8.0-0ubuntu3.2
Versionstabelle:
   *** 1:8.0-0ubuntu3.2 500
  500 http://de.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:8.0-0ubuntu3 500
  500 http://de.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.2
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: Unity
  Date: Fri Feb 17 07:48:08 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-22 (300 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/17/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.04
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W65_W67RZ
  dmi.board.vendor: TUXEDO
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: TUXEDO
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.04:bd12/17/2015:svnTUXEDO:pnW65_W67RZ:pvrNotApplicable:rvnTUXEDO:rnW65_W67RZ:rvrNotApplicable:cvnTUXEDO:ct10:cvrN/A:
  dmi.product.name: W65_W67RZ
  dmi.product.version: Not Applicable
  dmi.sys.vendor: TUXEDO
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.default.pa: 2016-05-27T07:24:27.474424

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

2017-07-15 Thread Launchpad Bug Tracker
[Expired for pulseaudio (Ubuntu) because there has been no activity for
60 days.]

** Changed in: pulseaudio (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  pulseaudio crashed

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  After updating to Ubuntu 16.04 there was no sound from my laptop. I checked 
with aplay -l and other such commands and found that my soundcard has been 
detected and the driver for the same is already installed. After this I tried 
to remove and re-install pulseaudio but to no avail. Hence I decided to report 
bug and on searching for bugs found that pulseaudio has crashed on my system. 
Also in sound settings there is no device listed in the play from devices list.
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04

  pulseaudio:
Installed: 1:8.0-0ubuntu3.2
Candidate: 1:8.0-0ubuntu3.2
Version table:
   *** 1:8.0-0ubuntu3.2 500
  500 http://in.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:8.0-0ubuntu3 500
  500 http://in.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.2
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  Uname: Linux 4.4.0-66-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D3', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: Unity
  Date: Fri Mar 10 21:12:34 2017
  InstallationDate: Installed on 2017-02-15 (23 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/20/2010
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 050VP6
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A10
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A10
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd10/20/2010:svnDellInc.:pnInspironN4010:pvrA10:rvnDellInc.:rn050VP6:rvrA10:cvnDellInc.:ct8:cvrA10:
  dmi.product.name: Inspiron N4010
  dmi.product.version: A10
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1671775/+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 1704608] [NEW] package libsamplerate0:i386 0.1.8-8 failed to install/upgrade: Paket libsamplerate0:i386 ist nicht bereit zur Konfiguration kann nicht konfiguriert werden (moment

2017-07-15 Thread Olaf Jensen
Public bug reported:

no info

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libsamplerate0:i386 0.1.8-8
ProcVersionSignature: Ubuntu 4.8.0-58.63~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-58-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.1-0ubuntu2.9
Architecture: amd64
Date: Fri Jul 14 15:12:16 2017
Dependencies:
 gcc-6-base 6.0.1-0ubuntu1
 libc6 2.23-0ubuntu9
 libgcc1 1:6.0.1-0ubuntu1
 multiarch-support 2.23-0ubuntu9
ErrorMessage: Paket libsamplerate0:i386 ist nicht bereit zur Konfiguration  
kann nicht konfiguriert werden (momentaner Status »half-installed«)
InstallationDate: Installed on 2017-05-25 (51 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
PackageArchitecture: i386
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: libsamplerate
Title: package libsamplerate0:i386 0.1.8-8 failed to install/upgrade: Paket 
libsamplerate0:i386 ist nicht bereit zur Konfiguration  kann nicht konfiguriert 
werden (momentaner Status »half-installed«)
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-package i386 xenial

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

Title:
  package libsamplerate0:i386 0.1.8-8 failed to install/upgrade: Paket
  libsamplerate0:i386 ist nicht bereit zur Konfiguration  kann nicht
  konfiguriert werden (momentaner Status »half-installed«)

Status in libsamplerate package in Ubuntu:
  New

Bug description:
  no info

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libsamplerate0:i386 0.1.8-8
  ProcVersionSignature: Ubuntu 4.8.0-58.63~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-58-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.9
  Architecture: amd64
  Date: Fri Jul 14 15:12:16 2017
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu9
   libgcc1 1:6.0.1-0ubuntu1
   multiarch-support 2.23-0ubuntu9
  ErrorMessage: Paket libsamplerate0:i386 ist nicht bereit zur Konfiguration  
kann nicht konfiguriert werden (momentaner Status »half-installed«)
  InstallationDate: Installed on 2017-05-25 (51 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: i386
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: libsamplerate
  Title: package libsamplerate0:i386 0.1.8-8 failed to install/upgrade: Paket 
libsamplerate0:i386 ist nicht bereit zur Konfiguration  kann nicht konfiguriert 
werden (momentaner Status »half-installed«)
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libsamplerate/+bug/1704608/+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 1704594] Re: Brother MFC 7820N printer is not working in Ubuntu 15.10

2017-07-15 Thread Paul White
Thank you for reporting this bug to Ubuntu. The 15.10 release reached EOL on 
July 28th, 2016.
See this document for currently supported Ubuntu releases: 
https://wiki.ubuntu.com/Releases 

Please upgrade to a supported version and advise if the problem is still
reproducible.


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

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

Title:
  Brother MFC 7820N printer is not working in Ubuntu 15.10

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  tera@tera-NV57H:~$ lsmod | grep usb
  usblp  20480  0
  usbhid 49152  0
  hid   118784  2 hid_generic,usbhid
  tera@tera-NV57H:~$ tail -f /var/log/syslog
  Jul 15 15:30:15 tera-NV57H systemd[1]: Started Hostname Service.
  Jul 15 15:30:20 tera-NV57H org.gnome.zeitgeist.SimpleIndexer[1217]: ** 
(zeitgeist-fts:1691): WARNING **: Unable to get info on 
application://nautilus-autostart.desktop
  Jul 15 15:30:20 tera-NV57H gnome-session[1286]: javaldx: Could not find a 
Java Runtime Environment!
  Jul 15 15:30:20 tera-NV57H gnome-session[1286]: Warning: failed to read path 
from javaldx
  Jul 15 15:30:27 tera-NV57H com.ubuntu.OneConf[1217]: 
WARNING:oneconf.hosts:Error in loading other_hosts file: [Errno 2] No such file 
or directory: 
'/home/tera/.cache/oneconf/ecc8c8b5f47f48d7848575bfc2692722/other_hosts'
  Jul 15 15:37:13 tera-NV57H kernel: [ 2310.456175] usb 2-1.1: USB disconnect, 
device number 3
  Jul 15 15:37:13 tera-NV57H kernel: [ 2310.456510] usblp0: removed
  Jul 15 15:37:13 tera-NV57H udev-configure-printer[6879]: remove 
/devices/pci:00/:00:1d.0/usb2/2-1/2-1.1
  Jul 15 15:37:13 tera-NV57H systemd[1]: printer.target: Unit not needed 
anymore. Stopping.
  Jul 15 15:37:13 tera-NV57H systemd[1]: Stopped target Printer.
  Jul 15 15:39:31 tera-NV57H kernel: [ 2448.849130] usb 2-1.1: new full-speed 
USB device number 5 using ehci-pci
  Jul 15 15:39:32 tera-NV57H kernel: [ 2448.945798] usb 2-1.1: New USB device 
found, idVendor=04f9, idProduct=0181
  Jul 15 15:39:32 tera-NV57H kernel: [ 2448.945809] usb 2-1.1: New USB device 
strings: Mfr=0, Product=0, SerialNumber=3
  Jul 15 15:39:32 tera-NV57H kernel: [ 2448.945824] usb 2-1.1: SerialNumber: 
000G5J363027
  Jul 15 15:39:32 tera-NV57H kernel: [ 2448.948742] usblp 2-1.1:1.0: usblp0: 
USB Bidirectional printer dev 5 if 0 alt 0 proto 2 vid 0x04F9 pid 0x0181
  Jul 15 15:39:32 tera-NV57H mtp-probe: checking bus 2, device 5: 
"/sys/devices/pci:00/:00:1d.0/usb2/2-1/2-1.1"
  Jul 15 15:39:33 tera-NV57H mtp-probe: bus: 2, device: 5 was not an MTP device
  Jul 15 15:39:33 tera-NV57H systemd[1]: Created slice 
system-udev\x2dconfigure\x2dprinter.slice.
  Jul 15 15:39:33 tera-NV57H systemd[1]: Starting Automatic USB/Bluetooth 
printer setup (-devices-pci:00-:00:1d.0-usb2-2\x2d1-2\x2d1.1)...
  Jul 15 15:39:33 tera-NV57H systemd[1]: Reached target Printer.
  Jul 15 15:39:33 tera-NV57H udev-configure-printer[6896]: add 
/devices/pci:00/:00:1d.0/usb2/2-1/2-1.1
  Jul 15 15:39:33 tera-NV57H udev-configure-printer[6896]: device devpath is 
/devices/pci:00/:00:1d.0/usb2/2-1/2-1.1
  Jul 15 15:39:33 tera-NV57H udev-configure-printer[6896]: MFG:Brother 
MDL:MFC-7820N SERN:- serial:000G5J363027
  Jul 15 15:39:38 tera-NV57H udev-configure-printer[6896]: IPP request 16395 
failed (1280)
  Jul 15 15:39:38 tera-NV57H systemd[1]: 
udev-configure-printer@-devices-pci:00-:00:1d.0-usb2-2\x2d1-2\x2d1.1.service:
 Control process exited, code=exited status=1
  Jul 15 15:39:38 tera-NV57H systemd[1]: Failed to start Automatic 
USB/Bluetooth printer setup 
(-devices-pci:00-:00:1d.0-usb2-2\x2d1-2\x2d1.1).
  Jul 15 15:39:38 tera-NV57H systemd[1]: 
udev-configure-printer@-devices-pci:00-:00:1d.0-usb2-2\x2d1-2\x2d1.1.service:
 Unit entered failed state.
  Jul 15 15:39:38 tera-NV57H systemd[1]: 
udev-configure-printer@-devices-pci:00-:00:1d.0-usb2-2\x2d1-2\x2d1.1.service:
 Failed with result 'exit-code'.
  ^C
  tera@tera-NV57H:~$ lsusb
  Bus 002 Device 004: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse
  Bus 002 Device 005: ID 04f9:0181 Brother Industries, Ltd MFC-7820N 
Port(FaxModem)
  Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 003: ID 1bcf:288a Sunplus Innovation Technology Inc. 
  Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  tera@tera-NV57H:~$ ls -l /dev/usb/lp* /dev/bus/usb/*/*
  crw-rw-r-- 1 root root 189,   0 Jul 15 14:58 /dev/bus/usb/001/001
  crw-rw-r-- 1 root root 189,   1 Jul 15 14:58 /dev/bus/usb/001/002
  crw-rw-r-- 1 root root 189,   2 Jul 15 14:58 /dev/bus/usb/001/003
  crw-rw-r-- 1 root root 189, 128 Jul 15 14:58 

[Touch-packages] [Bug 1704604] [NEW] package gconf2-common 3.2.6-3ubuntu6 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 10

2017-07-15 Thread Paulo Cruz
Public bug reported:

package gconf2-common 3.2.6-3ubuntu6 failed to install/upgrade: sub-
processo script post-installation instalado retornou estado de saída de
erro 10

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: gconf2-common 3.2.6-3ubuntu6
ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
Uname: Linux 4.10.0-26-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.4-0ubuntu4.4
Architecture: amd64
Date: Sat Jul 15 20:49:06 2017
ErrorMessage: sub-processo script post-installation instalado retornou estado 
de saída de erro 10
InstallationDate: Installed on 2016-07-23 (357 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4
SourcePackage: gconf
Title: package gconf2-common 3.2.6-3ubuntu6 failed to install/upgrade: 
sub-processo script post-installation instalado retornou estado de saída de 
erro 10
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package third-party-packages zesty

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

Title:
  package gconf2-common 3.2.6-3ubuntu6 failed to install/upgrade: sub-
  processo script post-installation instalado retornou estado de saída
  de erro 10

Status in gconf package in Ubuntu:
  New

Bug description:
  package gconf2-common 3.2.6-3ubuntu6 failed to install/upgrade: sub-
  processo script post-installation instalado retornou estado de saída
  de erro 10

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: gconf2-common 3.2.6-3ubuntu6
  ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
  Uname: Linux 4.10.0-26-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4.4
  Architecture: amd64
  Date: Sat Jul 15 20:49:06 2017
  ErrorMessage: sub-processo script post-installation instalado retornou estado 
de saída de erro 10
  InstallationDate: Installed on 2016-07-23 (357 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: gconf
  Title: package gconf2-common 3.2.6-3ubuntu6 failed to install/upgrade: 
sub-processo script post-installation instalado retornou estado de saída de 
erro 10
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1704604/+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 1704603] [NEW] Juniper/Pulse VPN (SSL VPN) not configurable

2017-07-15 Thread Moritz Naumann
Public bug reported:

While the OpenConnect CLI version available in Ubuntu 16.04.2 supports
connecting to (older but not current firmware versions of) Juniper/Pulse
VPN (SSL VPN) (using the --pulse option), the NM GUI does not allow for
configuring this type of VPN. You can choose to configure an OpenConnect
VPN, but it lacks the option to connect using the specific Juniper
Network Connect / Pulse Secure SSL VPN protocol.

Newer versions of network-manager-openconnect-gnome do, however, allow
for configuring this protocol and work with the openconnect '--protocol
pulse' option of the updated openconnect CLI.

Since Xenial is going to stay, and is the most likely target for
companies which make use of this VPN technology, please do consider to
support this protocol in Xenial by means of a SRU or backport.

The version of both openconnect and, moreover, the NM GUI, is most
likely not usable for any ompany running current VPN access servers
(with current software versions).

Thanks for your consideration.

** Affects: network-manager-openconnect (Ubuntu)
 Importance: Undecided
 Status: New

** Package changed: network-manager (Ubuntu) => network-manager-
openconnect (Ubuntu)

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

Title:
  Juniper/Pulse VPN (SSL VPN) not configurable

Status in network-manager-openconnect package in Ubuntu:
  New

Bug description:
  While the OpenConnect CLI version available in Ubuntu 16.04.2 supports
  connecting to (older but not current firmware versions of)
  Juniper/Pulse VPN (SSL VPN) (using the --pulse option), the NM GUI
  does not allow for configuring this type of VPN. You can choose to
  configure an OpenConnect VPN, but it lacks the option to connect using
  the specific Juniper Network Connect / Pulse Secure SSL VPN protocol.

  Newer versions of network-manager-openconnect-gnome do, however, allow
  for configuring this protocol and work with the openconnect '--
  protocol pulse' option of the updated openconnect CLI.

  Since Xenial is going to stay, and is the most likely target for
  companies which make use of this VPN technology, please do consider to
  support this protocol in Xenial by means of a SRU or backport.

  The version of both openconnect and, moreover, the NM GUI, is most
  likely not usable for any ompany running current VPN access servers
  (with current software versions).

  Thanks for your consideration.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-openconnect/+bug/1704603/+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 1704602] [NEW] nm-applet gui may segfault if bug #1704600 is triggered

2017-07-15 Thread Stefan Helmert
Public bug reported:

If network-manager stucks caused by bug #1704600, further attempts to
interact with the nm-applet gui lead to timeouts and often a
segmentation fault of nm-applet, causing the nm-applet to terminate non-
gracefully.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: network-manager 1.2.6-0ubuntu0.16.04.1
ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
Uname: Linux 4.4.0-83-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Jul 16 02:18:48 2017
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
 auto enp0s25
 iface enp0s25 inet manual
IpRoute:
 default via 10.149.15.253 dev wlp3s0  proto static  metric 600 
 10.149.0.0/20 dev wlp3s0  proto kernel  scope link  src 10.149.5.84  metric 
600 
 169.254.0.0/16 dev br-d5edc0a60a9c  scope link  metric 1000 
 172.17.0.0/16 dev docker0  proto kernel  scope link  src 172.17.0.1 linkdown 
 172.18.0.0/16 dev br-d5edc0a60a9c  proto kernel  scope link  src 172.18.0.1
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2017-04-14T17:29:21.619202
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  enabled

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug xenial

** Attachment added: "one variant of the error"
   
https://bugs.launchpad.net/bugs/1704602/+attachment/4915345/+files/nmappletSegFault.png

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

Title:
  nm-applet gui may segfault if bug #1704600 is triggered

Status in network-manager package in Ubuntu:
  New

Bug description:
  If network-manager stucks caused by bug #1704600, further attempts to
  interact with the nm-applet gui lead to timeouts and often a
  segmentation fault of nm-applet, causing the nm-applet to terminate
  non-gracefully.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.6-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
  Uname: Linux 4.4.0-83-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Jul 16 02:18:48 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
   auto enp0s25
   iface enp0s25 inet manual
  IpRoute:
   default via 10.149.15.253 dev wlp3s0  proto static  metric 600 
   10.149.0.0/20 dev wlp3s0  proto kernel  scope link  src 10.149.5.84  metric 
600 
   169.254.0.0/16 dev br-d5edc0a60a9c  scope link  metric 1000 
   172.17.0.0/16 dev docker0  proto kernel  scope link  src 172.17.0.1 linkdown 
   172.18.0.0/16 dev br-d5edc0a60a9c  proto kernel  scope link  src 172.18.0.1
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2017-04-14T17:29:21.619202
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1704602/+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 1702326] Re: New microrelease 1.4.7 for zesty

2017-07-15 Thread Bug Watch Updater
** Changed in: apt (Debian)
   Status: Confirmed => Fix Committed

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

Title:
  New microrelease 1.4.7 for zesty

Status in apt package in Ubuntu:
  Invalid
Status in apt source package in Zesty:
  Triaged
Status in apt package in Debian:
  Fix Committed

Bug description:
  [Impact]
  This is a new upstream micro release for the first point release of Debian 
stretch.

  apt (1.4.7) stretch; urgency=medium

[ Robert Luberda ]
* fix a "critical" typo in old changelog entry (Closes: 866358)
  => Remove a letter, and fixes some tool

[ David Kalnischkies ]
* use port from SRV record instead of initial port
  => Might have picked the wrong port

[ Julian Andres Klode ]
* Reset failure reason when connection was successful
  => Some failures were only treated as warnings, not errors

* debian/gbp.conf: Set debian-branch to 1.4.y
  => Building ...

* http: A response with Content-Length: 0 has no content

  => Downloading failed if server responded with Content-Length: 0, as
 APT was waiting for content to read.

   -- Julian Andres Klode   Tue, 04 Jul 2017 17:11:59
  +0200

  [Test case]
  We don't really have any yet, they require DNS servers and http servers, so 
it's not really easy to test.

  [Regression potential]
  We basically changed just the code used in the http method, and the changes 
are both very obvious and very small. I reproduced the http change with the tls 
support from 1.5, because launchpad was causing issues with that.

  With the failure reason reset, some errors might not be wrongly
  considered as transient connection errors and now cause scripts to
  fail. But that's how it should be, really.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1702326/+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 1667113] Re: System users appears in Ligthdm and user switcher (Accountsservice has no filter for shell types)

2017-07-15 Thread pierre
Thanks gcotnoir, it's a nice workaround while the bug gets looked into.

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

Title:
  System users appears in Ligthdm and user switcher (Accountsservice has
  no filter for shell types)

Status in accountsservice package in Ubuntu:
  Confirmed
Status in base-passwd package in Ubuntu:
  Invalid
Status in ceph package in Ubuntu:
  Confirmed
Status in ifmail package in Ubuntu:
  Confirmed
Status in libvirt package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  Confirmed
Status in netqmail package in Ubuntu:
  Confirmed
Status in sddm package in Ubuntu:
  Fix Released

Bug description:
  "Technical" user libvirt Qemu appears in the list of user in Ligthdm,
  among the real regular users. It probably shouldn't

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: libvirt-bin 2.5.0-3ubuntu2
  ProcVersionSignature: Ubuntu 4.9.0-15.16-generic 4.9.5
  Uname: Linux 4.9.0-15-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Wed Feb 22 22:09:24 2017
  InstallationDate: Installed on 2017-02-01 (21 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170201)
  KernLog:
   
  SourcePackage: libvirt
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1667113/+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 1704600] [NEW] network-manager stucks if 127.0.1.1:53 is in use

2017-07-15 Thread Stefan Helmert
Public bug reported:

If a process binds 127.0.1.1:53 and the network-manager ist started, it
tries to use this port (dnsmasq). It waits until the port is available.
That means no interaction with the network-manager is possible. So
unity-control-center stucks if "Network" is clicked or the nm-applet
does not respond if the user tries to change connection settings.

I think there should be a message that explains the problem: "network-
manager tries to set up dnsmasq on 127.0.1.1:53, but this port is
already in use. Retrying ..." and the associated GUI components should
stay responsive, but only the blocked options should be shown as blocked
by the problem.

You can verify the bug with the provieded script.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: network-manager 1.2.6-0ubuntu0.16.04.1
ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
Uname: Linux 4.4.0-83-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Jul 16 02:01:03 2017
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
 auto enp0s25
 iface enp0s25 inet manual
IpRoute:
 default via 10.149.15.253 dev wlp3s0  proto static  metric 600 
 10.149.0.0/20 dev wlp3s0  proto kernel  scope link  src 10.149.5.84  metric 
600 
 169.254.0.0/16 dev br-d5edc0a60a9c  scope link  metric 1000 
 172.17.0.0/16 dev docker0  proto kernel  scope link  src 172.17.0.1 linkdown 
 172.18.0.0/16 dev br-d5edc0a60a9c  proto kernel  scope link  src 172.18.0.1
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2017-04-14T17:29:21.619202
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  enabled

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug xenial

** Attachment added: "script triggers the problem"
   
https://bugs.launchpad.net/bugs/1704600/+attachment/4915321/+files/crash_networkmanager.bash

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

Title:
  network-manager stucks if 127.0.1.1:53 is in use

Status in network-manager package in Ubuntu:
  New

Bug description:
  If a process binds 127.0.1.1:53 and the network-manager ist started,
  it tries to use this port (dnsmasq). It waits until the port is
  available. That means no interaction with the network-manager is
  possible. So unity-control-center stucks if "Network" is clicked or
  the nm-applet does not respond if the user tries to change connection
  settings.

  I think there should be a message that explains the problem: "network-
  manager tries to set up dnsmasq on 127.0.1.1:53, but this port is
  already in use. Retrying ..." and the associated GUI components should
  stay responsive, but only the blocked options should be shown as
  blocked by the problem.

  You can verify the bug with the provieded script.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.6-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
  Uname: Linux 4.4.0-83-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Jul 16 02:01:03 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
   auto enp0s25
   iface enp0s25 inet manual
  IpRoute:
   default via 10.149.15.253 dev wlp3s0  proto static  metric 600 
   10.149.0.0/20 dev wlp3s0  proto kernel  scope link  src 10.149.5.84  metric 
600 
   169.254.0.0/16 dev br-d5edc0a60a9c  scope link  metric 1000 
   172.17.0.0/16 dev docker0  proto kernel  scope link  src 172.17.0.1 linkdown 
   172.18.0.0/16 dev br-d5edc0a60a9c  proto kernel  scope link  src 172.18.0.1
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2017-04-14T17:29:21.619202
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1704600/+subscriptions

-- 
Mailing list: 

[Touch-packages] [Bug 1704594] [NEW] Brother MFC 7820N printer is not working in Ubuntu 15.10

2017-07-15 Thread Tera Yoon
Public bug reported:

tera@tera-NV57H:~$ lsmod | grep usb
usblp  20480  0
usbhid 49152  0
hid   118784  2 hid_generic,usbhid
tera@tera-NV57H:~$ tail -f /var/log/syslog
Jul 15 15:30:15 tera-NV57H systemd[1]: Started Hostname Service.
Jul 15 15:30:20 tera-NV57H org.gnome.zeitgeist.SimpleIndexer[1217]: ** 
(zeitgeist-fts:1691): WARNING **: Unable to get info on 
application://nautilus-autostart.desktop
Jul 15 15:30:20 tera-NV57H gnome-session[1286]: javaldx: Could not find a Java 
Runtime Environment!
Jul 15 15:30:20 tera-NV57H gnome-session[1286]: Warning: failed to read path 
from javaldx
Jul 15 15:30:27 tera-NV57H com.ubuntu.OneConf[1217]: 
WARNING:oneconf.hosts:Error in loading other_hosts file: [Errno 2] No such file 
or directory: 
'/home/tera/.cache/oneconf/ecc8c8b5f47f48d7848575bfc2692722/other_hosts'
Jul 15 15:37:13 tera-NV57H kernel: [ 2310.456175] usb 2-1.1: USB disconnect, 
device number 3
Jul 15 15:37:13 tera-NV57H kernel: [ 2310.456510] usblp0: removed
Jul 15 15:37:13 tera-NV57H udev-configure-printer[6879]: remove 
/devices/pci:00/:00:1d.0/usb2/2-1/2-1.1
Jul 15 15:37:13 tera-NV57H systemd[1]: printer.target: Unit not needed anymore. 
Stopping.
Jul 15 15:37:13 tera-NV57H systemd[1]: Stopped target Printer.
Jul 15 15:39:31 tera-NV57H kernel: [ 2448.849130] usb 2-1.1: new full-speed USB 
device number 5 using ehci-pci
Jul 15 15:39:32 tera-NV57H kernel: [ 2448.945798] usb 2-1.1: New USB device 
found, idVendor=04f9, idProduct=0181
Jul 15 15:39:32 tera-NV57H kernel: [ 2448.945809] usb 2-1.1: New USB device 
strings: Mfr=0, Product=0, SerialNumber=3
Jul 15 15:39:32 tera-NV57H kernel: [ 2448.945824] usb 2-1.1: SerialNumber: 
000G5J363027
Jul 15 15:39:32 tera-NV57H kernel: [ 2448.948742] usblp 2-1.1:1.0: usblp0: USB 
Bidirectional printer dev 5 if 0 alt 0 proto 2 vid 0x04F9 pid 0x0181
Jul 15 15:39:32 tera-NV57H mtp-probe: checking bus 2, device 5: 
"/sys/devices/pci:00/:00:1d.0/usb2/2-1/2-1.1"
Jul 15 15:39:33 tera-NV57H mtp-probe: bus: 2, device: 5 was not an MTP device
Jul 15 15:39:33 tera-NV57H systemd[1]: Created slice 
system-udev\x2dconfigure\x2dprinter.slice.
Jul 15 15:39:33 tera-NV57H systemd[1]: Starting Automatic USB/Bluetooth printer 
setup (-devices-pci:00-:00:1d.0-usb2-2\x2d1-2\x2d1.1)...
Jul 15 15:39:33 tera-NV57H systemd[1]: Reached target Printer.
Jul 15 15:39:33 tera-NV57H udev-configure-printer[6896]: add 
/devices/pci:00/:00:1d.0/usb2/2-1/2-1.1
Jul 15 15:39:33 tera-NV57H udev-configure-printer[6896]: device devpath is 
/devices/pci:00/:00:1d.0/usb2/2-1/2-1.1
Jul 15 15:39:33 tera-NV57H udev-configure-printer[6896]: MFG:Brother 
MDL:MFC-7820N SERN:- serial:000G5J363027
Jul 15 15:39:38 tera-NV57H udev-configure-printer[6896]: IPP request 16395 
failed (1280)
Jul 15 15:39:38 tera-NV57H systemd[1]: 
udev-configure-printer@-devices-pci:00-:00:1d.0-usb2-2\x2d1-2\x2d1.1.service:
 Control process exited, code=exited status=1
Jul 15 15:39:38 tera-NV57H systemd[1]: Failed to start Automatic USB/Bluetooth 
printer setup (-devices-pci:00-:00:1d.0-usb2-2\x2d1-2\x2d1.1).
Jul 15 15:39:38 tera-NV57H systemd[1]: 
udev-configure-printer@-devices-pci:00-:00:1d.0-usb2-2\x2d1-2\x2d1.1.service:
 Unit entered failed state.
Jul 15 15:39:38 tera-NV57H systemd[1]: 
udev-configure-printer@-devices-pci:00-:00:1d.0-usb2-2\x2d1-2\x2d1.1.service:
 Failed with result 'exit-code'.
^C
tera@tera-NV57H:~$ lsusb
Bus 002 Device 004: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse
Bus 002 Device 005: ID 04f9:0181 Brother Industries, Ltd MFC-7820N 
Port(FaxModem)
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 1bcf:288a Sunplus Innovation Technology Inc. 
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
tera@tera-NV57H:~$ ls -l /dev/usb/lp* /dev/bus/usb/*/*
crw-rw-r-- 1 root root 189,   0 Jul 15 14:58 /dev/bus/usb/001/001
crw-rw-r-- 1 root root 189,   1 Jul 15 14:58 /dev/bus/usb/001/002
crw-rw-r-- 1 root root 189,   2 Jul 15 14:58 /dev/bus/usb/001/003
crw-rw-r-- 1 root root 189, 128 Jul 15 14:58 /dev/bus/usb/002/001
crw-rw-r-- 1 root root 189, 129 Jul 15 14:58 /dev/bus/usb/002/002
crw-rw-r-- 1 root root 189, 131 Jul 15 14:58 /dev/bus/usb/002/004
crw-rw-r-- 1 root lp   189, 132 Jul 15 15:39 /dev/bus/usb/002/005
crw-rw 1 root lp   180,   0 Jul 15 15:39 /dev/usb/lp0
tera@tera-NV57H:~$ sudo usb_printerid /dev/usb/lp0
[sudo] password for tera: 
GET_DEVICE_ID string:
MFG:Brother;CMD:PJL,PCL,PCLXL;MDL:MFC-7820N;CLS:PRINTER;
tera@tera-NV57H:~$ lpinfo -v
lpinfo: cups-deviced failed to execute.
tera@tera-NV57H:~$ cancel -a
tera@tera-NV57H:~$ lpadmin -p -0 usb-unidir-default=true
lpadmin: Unknown argument "usb-unidir-default=true".
tera@tera-NV57H:~$ sudo ubuntu-bug cups
[sudo] password for tera: 
tera@tera-NV57H:~$ 

[Touch-packages] [Bug 1282314] Re: Evince cannot open HTTP link in Google Chrome or chromium-browser

2017-07-15 Thread Tim Richardson
Still a problem in 17.04. I don't see how to turn comment #21 into a
fix.

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

Title:
  Evince cannot open HTTP link in Google Chrome or chromium-browser

Status in apparmor package in Ubuntu:
  Fix Released

Bug description:
  This is similar to bug #964510 but found on Ubuntu 13.10 Saucy which
  already has the patch for that bug, and with a different message:

  Feb 19 23:50:14 sammy kernel: [413602.643399] type=1400
  audit(1392853814.794:89): apparmor="DENIED" operation="file_mmap"
  parent=28174 profile="/usr/bin/evince//sanitized_helper"
  name="/usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.18" pid=28181 comm
  ="chrome-sandbox" requested_mask="m" denied_mask="m" fsuid=0 ouid=0

  Symptoms are the same, evince fails to launch chromium when it's
  selected as the default.

  Evince run from the command line outputs the following when you click
  a link:

  /usr/lib/chromium-browser/chrome-sandbox: error while loading
  shared libraries: libstdc++.so.6: failed to map segment from shared
  object: Permission denied

  Another user reported the same issue
  https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/964510/comments/15
  but received no response to date.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1282314/+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 1341890] Re: [X550LA, Realtek ALC3236, Mic, Internal] No sound at all

2017-07-15 Thread TimSC
I have a problem with my sound suddenly stopping working (I'm on Mint
18.2 based on xenial, asus x555l). The work around is to reboot.

Another work around without rebooting: disable pulseaudio, first by
turning off autorespawn https://askubuntu.com/questions/8425/how-to-
temporarily-disable-pulseaudio and then pulseaudio --kill

Then sudo alsa reload

alsactl init

aplay /usr/share/sounds/alsa/Front_Center.wav

This responsed (with no audio playback):

ALSA lib pcm_dmix.c:1029:(snd_pcm_dmix_open) unable to open slave
aplay: main:722: audio open error: No such file or directory

However, this works: aplay /usr/share/sounds/alsa/Front_Center.wav
--device=plughw:CARD=PCH,DEV=0

Then "pulseaudio --start" and my audio is back and working!

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

Title:
  [X550LA, Realtek ALC3236, Mic, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  I've been trying to fix this myself for a while now, and just a day or
  two ago, the speakers stopped working, too. Neither the internal nor
  external speakers I've been using with my laptop have been working,
  with two exceptions: the bongos noise when the login screen comes up,
  and the tones made during a system test. I have tried the commands
  "alsamixer" and "gstreamer-properties" in terminal and have had
  success with neither of them, and have also tried using the pulse
  audio volume controls to no avail. My assumption is that there is an
  issue with the drivers, as even the microphone produced a few sporadic
  noises ONLY when I was playing with the mic volume controls, but at no
  other point in no other program has it been so responsive.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2
  Uname: Linux 3.13.0-30-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jake   1815 F pulseaudio
   /dev/snd/controlC0:  jake   1815 F pulseaudio
   /dev/snd/pcmC0D3p:   jake   1815 F...m pulseaudio
  CurrentDesktop: Unity
  Date: Mon Jul 14 20:25:02 2014
  InstallationDate: Installed on 2014-05-23 (52 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jake   1815 F pulseaudio
   /dev/snd/controlC0:  jake   1815 F pulseaudio
   /dev/snd/pcmC0D3p:   jake   1815 F...m pulseaudio
  Symptom_Jack: Mic, Internal
  Symptom_Type: No sound at all
  Title: [X550LA, Realtek ALC3236, Mic, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/26/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X550LA.403
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X550LA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX550LA.403:bd11/26/2013:svnASUSTeKCOMPUTERINC.:pnX550LA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X550LA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1341890/+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 1173915] Re: initctl continuously takes 100% of CPU

2017-07-15 Thread Peter Connolly
@Arul: I'm still seeing it happen on 16.04. Upgrading to 17 isn't an option for 
some of us as we rely on third parties that don't support non-LTS releases 
(e.g., DSE Cassandra)
@Ketil: Couldn't agree more. Lower priority bugs are the red-headed stepchild 
on launchpad.

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

Title:
  initctl continuously takes 100% of CPU

Status in upstart :
  Confirmed
Status in upstart package in Ubuntu:
  Confirmed

Bug description:
  Many programs are fairly slow to start on my computer, despite it
  being relatively new (core i5). Suspecting a heavy CPU usage, I
  started gnome-system-monitor: all processes were displayed at 0% CPU,
  but the overall load was 1.33; 1.33; 1.34.

  Using the "top" command, however, revealed the real CPU use, with the
  "initctl" process taking 100%CPU, even 1 hour after startup.

  I upgraded to roaring ringtail before checking this but the symptoms
  were the same with quantal quetzal, so there is a fair chance the
  causes were identical.

  Regards

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: upstart 1.8-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
  Uname: Linux 3.8.0-19-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  CheckboxSubmission: 2deefc5fd2f1f0ae2fdd4bd781248a2a
  CheckboxSystem: daed2f3d6643b4a84b4520a2427f8c2b
  Date: Sun Apr 28 13:04:05 2013
  ExecutablePath: /sbin/initctl
  InstallationDate: Installed on 2012-12-15 (133 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MarkForUpload: True
  ProcEnviron:
   
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic 
root=UUID=fa624f8f-d9d0-4b09-af8b-88b106aaaf5b ro quiet splash vt.handoff=7
  SourcePackage: upstart
  UpgradeStatus: Upgraded to raring on 2013-04-28 (0 days ago)
  UpstartBugCategory: System

To manage notifications about this bug go to:
https://bugs.launchpad.net/upstart/+bug/1173915/+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 1250109] Re: Please use dpkg-triggers for update-grub when installing or removing kernel packages

2017-07-15 Thread Mathew Hodson
** Changed in: linux (Ubuntu)
Milestone: ubuntu-16.10 => None

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

Title:
  Please use dpkg-triggers for update-grub when installing or removing
  kernel packages

Status in grub2 package in Ubuntu:
  Triaged
Status in initramfs-tools package in Ubuntu:
  Triaged
Status in linux package in Ubuntu:
  Triaged
Status in grub2 package in Debian:
  Won't Fix

Bug description:
  Currently the kernel package runs update-grub every time one is
  installed or removed.  This results in it being run a dozen times
  during a dist-upgrade, and this is rather time consuming and annoying.
  Please use a dpkg trigger to cause update-grub to be run only once.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1250109/+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 1075424] Re: ping6 does not understand IPv6 addresses

2017-07-15 Thread Jaromir Obr
It's not a bug and man page ping6(8) mentions it:
---
-I interface
For IPv6, when doing ping to
a link-local scope address, link specification (by the '%'-nota‐
tion in destination, or by this option) is required.
---

However the error message "connect: Invalid argument" (with no help) is
very confusing and I believe many people need to google this issue.

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

Title:
  ping6 does not understand IPv6 addresses

Status in iputils package in Ubuntu:
  Invalid

Bug description:
  I cannot figure out what the problem is, but ping6 doesn't understand
  IPv6 addresses, except for the "local" IPs.

  $ ifconfig eth0
  eth0  Link encap:Ethernet  HWaddr 70:5a:b6:
inet addr:192.168.0.25  Bcast:192.168.0.63  Mask:255.255.255.192
inet6 addr: fe80::725a:b6ff:fef3:4d60/64 Scope:Link

  $ ping6 ::1 -c 1
  PING ::1(::1) 56 data bytes
  64 bytes from ::1: icmp_seq=1 ttl=64 time=0.074 ms

  $ ping6 fe80::725a:b6ff:fef3:4d60
  connect: Invalid argument

  strace:
  connect(3, {sa_family=AF_INET6, sin6_port=htons(1025), inet_pton(AF_INET6, 
"fe80::725a:b6ff:fef3:4d60", _addr), sin6_flowinfo=0, sin6_scope_id=0}, 
28) = -1 EINVAL (Invalid argument)
  dup(2)  = 4
  fcntl(4, F_GETFL)   = 0x8002 (flags O_RDWR|O_LARGEFILE)
  fstat(4, {st_mode=S_IFCHR|0600, st_rdev=makedev(136, 12), ...}) = 0
  mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x7ff83d761000
  lseek(4, 0, SEEK_CUR)   = -1 ESPIPE (Illegal seek)
  write(4, "connect: Invalid argument\n", 26connect: Invalid argument
  ) = 26
  close(4)

  I haven't been able to ping any IPv6 addresses for about a year.

  Tried on a fresh server install:
  $ ping6 -c 1 fe80::21d:9ff:feb6:1231
  connect: Invalid argument

  $ route -n46
  Kernel IP routing table
  Destination Gateway Genmask Flags Metric RefUse Iface
  0.0.0.0 192.168.0.2 0.0.0.0 UG10000 eth0
  10.0.3.00.0.0.0 255.255.255.0   U 0  00 lxcbr0
  169.254.0.0 0.0.0.0 255.255.0.0 U 1000   00 eth0
  192.168.0.0 0.0.0.0 255.255.255.192 U 0  00 eth0
  192.168.0.0 0.0.0.0 255.255.255.192 U 0  00 eth1
  Kernel IPv6 routing table
  DestinationNext Hop   Flag Met Ref Use If
  2001::/32  :: U256 0 0 
teredo
  fe80::/64  :: U256 0 0 
eth1
  fe80::/64  :: U256 0 0 
eth0
  fe80::/64  :: U256 0 0 
lxcbr0
  fe80::/64  :: U256 0 0 
teredo
  ::/0   :: U1029 0 0 
teredo
  ::/0   :: !n   -1  1  1206 lo
  ::1/128:: Un   0   133 lo
  2001:0:53aa:64c:2044:3165:a13e:bbf8/128 :: Un   0   1 
0 lo
  fe80::::/128   :: Un   0   1 0 lo
  fe80::725a:b6ff:fef3:4d60/128  :: Un   0   1 0 lo
  fe80::7ae4:ff:fe14:9eb5/128:: Un   0   1 0 lo
  fe80::f48c:52ff:fea5:50c2/128  :: Un   0   1 0 lo
  ff00::/8   :: U256 0 0 
eth1
  ff00::/8   :: U256 0 0 
eth0
  ff00::/8   :: U256 0 0 
lxcbr0
  ff00::/8   :: U256 0 0 
teredo
  ::/0   :: !n   -1  1  1206 lo

  Although, this doesn't appear to be a routing issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: iputils-ping 3:20101006-1ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-32.51-generic 3.2.30
  Uname: Linux 3.2.0-32-generic x86_64
  NonfreeKernelModules: fglrx wl
  ApportVersion: 2.0.1-0ubuntu14
  Architecture: amd64
  Date: Tue Nov  6 06:11:13 2012
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: iputils
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1593907] Re: ntpdate startup routine prevents ntp service from launching up on Ubuntu 16.04 server on system boot; manually starting ntp service works: [FIX in DESCRIPTION], just

2017-07-15 Thread Mathew Hodson
** Changed in: ntp (Ubuntu Trusty)
   Importance: Undecided => High

** Changed in: ntp (Ubuntu Xenial)
   Importance: Undecided => High

** Changed in: ntp (Ubuntu Yakkety)
   Importance: Undecided => High

** Changed in: ntp (Ubuntu Zesty)
   Importance: Undecided => High

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

Title:
  ntpdate startup routine prevents ntp service from launching up on
  Ubuntu 16.04 server on system boot; manually starting ntp service
  works: [FIX in DESCRIPTION], just need to apply it and release a new
  version

Status in ntp package in Ubuntu:
  Fix Released
Status in ntp source package in Trusty:
  Fix Committed
Status in ntp source package in Xenial:
  Fix Committed
Status in ntp source package in Yakkety:
  Fix Committed
Status in ntp source package in Zesty:
  Fix Committed

Bug description:
  [Impact]

   * Fixes several broken cases, those are:
   * Case 1 - ntp configured to drift time slowly, but time jumping
   - ntp is running and drifts time towards a target being way off
   - an interface comes up
   - stop ntpd
   - warp time via ntpdate-debian (static interfaces will even set -b)
   - (re-)start ntpd
   - if users relied on non-time warp they are now in trouble

   * Case 2 - ntp start/stop storms
   - ntpd comes up normally
   - the admin brings interfaces up/down rather often
   - ntp is restarted very very often due to this for no reason
   => reason for bugs like debian 823533

   * Case 3 - unintentional enablement of ntp
   - ntpd is installed but disabled (for whatever reason)
   - all is fine on any ifup/down
   - one installs ntpdate, maybe even without realizing due to a depends
   - now on the next ifup ntpd (or openntpd) will be started

   * Solution, drop the broken Delta

  [Test Case]

   * Testing Case 2/3 as it is the easiest, case 1 needs a more complex 
 setup to cause the time drift but otherwise works the same way.
 - install ntp and ntpdate
 - stop ntp
 - ifup/ifdown an interface multiple times; as simplification you can 
   also call /etc/network/if-up.d/ntpdate directly (not that this 
   spawns the change asnchronous and locks concurrency, so do that a 
   few times over the time of a minute or so)
 - the service of ntp should still be stopped and not report plenty of 
   restarts

  
  [Regression Potential] 

   * It improves a lot of cases (otherwise we wouldn't SRU), but there is 
 one regression potential I can see:

 - users that relied on starting NTP later on after other interfaces 
   got up due to that code in ntpdate which did that as a side effect. 
   But that is outweigh by Case2/3 for the majority of users. And even 
   Case1 only hits this potential regression on e.g. late network 
   intialization, but in that case please remind that the default 
   (systemd timedatectl) would handle that.

 - Since most users of ntp do not install ntpdate (which doesn't work 
   when ntp is active) we should be rather safe to assume that almost 
   no one should rely on that side effect.

 - Furthermore this is a Ubuntu Delta for very long, cause issues (see 
   the references on the git commit) but never made it into Debian - 
   in that sense another indicator it isn't an important delta to 
   have.

  [Other Info]
   
   * The original intention "what if net is available too late" fixed 
 correctly would not be part of ntpdate, but ntp and additionally 
 check if it is actually meant to be enabled - but I never seen/heard 
 of any of it since systemd is around - maybe new ordering mostly 
 avoids the original issue.


  ---

  
  I've installed ntp service on the clean ubuntu 16.04 server system. 
Configured it. Checked that it works, but, after reboot, it doesn't start 
automatically.
  When I check: 'systemctl is-enabled ntp', it shows enabled.
  If I manually start it 'systemctl start ntp' it starts just fine and woks 
correctly,
  but until I manually start it, 'systemctl status ntp' shows:

  Loaded: loaded (/etc/init.d/ntp; bad; vendor preset: enabled)
  Active: inactive (deadi)

  Installed 1.29ubuntu2 version of init-systems-helper, but it didn't
  fix the problem.

  Found a bugreport on ntpd package:

  https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1577596

  led to solution that involves a change to be made in file:

  /etc/network/if-up.d/ntpdate

  of ntpdate package

  After changing from:
  __CODE_START__

  invoke-rc.d --quiet $service stop >/dev/null 2>&1 || true

   # Avoid running more than one at a time
   flock -n /run/lock/ntpdate /usr/sbin/ntpdate-debian -s $OPTS 2>/dev/null 
|| :

  invoke-rc.d --quiet $service start >/dev/null 2>&1 || true

  

[Touch-packages] [Bug 1686803] Re: sudo returns exit code 0 if child is killed with SIGTERM

2017-07-15 Thread Mathew Hodson
** Changed in: sudo (Ubuntu Zesty)
   Importance: Undecided => Medium

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

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

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

Title:
  sudo returns exit code 0 if child is killed with SIGTERM

Status in sudo:
  Unknown
Status in sudo package in Ubuntu:
  Fix Released
Status in sudo source package in Xenial:
  Fix Committed
Status in sudo source package in Yakkety:
  Fix Committed
Status in sudo source package in Zesty:
  Fix Committed
Status in sudo source package in Artful:
  Fix Released

Bug description:
  [Impact]

   * sudo returns exit code 0 if child is killed with signals other than SIGINT
   * This can break scripts assuming successful execution of the command ran by
 sudo

  [Test Case]

   * Open two separate shells
 1. In shell 1. run:
   ubuntu@tough-calf:~$ sudo sleep 300; echo $?
 2. In shell 2. run:
   root@tough-calf:~# killall -TERM sleep
 3. In broken versions shell 1. shows this:
   ubuntu@tough-calf:~$ sudo sleep 300; echo $?
   0

 4. Install fixed version
 5. Execute steps 1. and 2.
 6. In fixed version shell 1. shows this:
   ubuntu@tough-calf:~$ sudo sleep 300; echo $?
   Terminated
   143

  [Regression Potential]

   *  sudo may exit with a different status than expected

  [Other Info]

  original bug description:

  Please backport upstream sudo changeset 10917:50b988d0c97f "The fix
  for Bug #722 contained a typo/thinko that resulted in the" to xenial,
  yakkety, and zesty versions of sudo.

  This will fix a regression documented by this upstream bug report:
  https://bugzilla.sudo.ws/show_bug.cgi?id=784

  sudo 1.8.15 changeset 10229:153f016db8f1 "When the command sudo is
  running is killed by a signal, sudo will" introduced a regression
  where the exit status is always 0 when a command is killed by a signal
  other than SIGINT. https://www.sudo.ws/repos/sudo/rev/153f016db8f1

  This will be fixed in sudo 1.8.20 with changeset 10917:50b988d0c97f
  "The fix for Bug #722 contained a typo/thinko that resulted in the".
  https://www.sudo.ws/repos/sudo/rev/50b988d0c97f

  trusty sudo is based off sudo 1.8.9 and is not affected. xenial sudo
  based off sudo 1.8.16, yaketty sudo based off sudo 1.8.16, and zesty
  sudo based off 1.8.19 need the fix.

To manage notifications about this bug go to:
https://bugs.launchpad.net/sudo/+bug/1686803/+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 1704585] Re: I'm getting error: SSL3_GET_RECORD:decryption failed or bad record mac

2017-07-15 Thread als
** Description changed:

- I have my own server (where I'm running Apache/2.4.27), and today I
- realized that from (Brave and Google Chrome - different computers) I'm
- getting from my websites this error;
+ Adter so many tries to solve this issue we were unable to find a
+ solution. So from that point we assumed that it can be a possible bug.
  
- This site can’t provide a secure connection
+ It was tested on Apache/2.4.27
  
- mywebsite.com sent an invalid response.
- ERR_SSL_PROTOCOL_ERROR
+ lsb_release -rd
  
- And the strange thing is that I'm getting this error every fifth click
- on my website.
+ Description:  Ubuntu 14.04.5 LTS
+ Release:  14.04
  
- From my conf file:
+ OpenSSL version 1.1.0f
  
- SSLEngine on
- SSLCertificateFile /etc/letsencrypt/live/mywebsite/cert.pem
- SSLCertificateKeyFile /etc/letsencrypt/live/mywebsite/privkey.pem
- Include /etc/letsencrypt/options-ssl-apache.conf
- SSLCertificateChainFile /etc/letsencrypt/live/mywebsite/chain.pem
- SSLCompression off
- 
- from options-ssl-apache.conf;
+ Our options-ssl-apache.conf;
  
  SSLProtocol all -SSLv2 -SSLv3
  SSLCipherSuite  EECDH+AESGCM:EDH+AESGCM:AES256+EECDH:AES256+EDH
  SSLHonorCipherOrder on
  SSLCompression  off
  
- I have checked log file from website but nothing, also nothing here;
- /var/log/apache2/error.log
+ We tried to manipulate and change CipherSuite but same error will appear
+ always.
  
- I'm trying to figure out what is causing this error, any ideas where can
- I find more info or even better, how to solve this problem?
- 
- EDIT:
  
  If I try openssl s_client -connect mywebsite.com:443, it will return:
  
  I'm using: OpenSSL 1.1.0f
  
  CONNECTED(0003)
  
  ...
  
  3073276480:error:1408F119:SSL routines:ssl3_get_record:decryption failed
  or bad record mac:../ssl/record/ssl3_record.c:469:
  
  apt-cache policy openssl
+ 
  openssl:
-   Installed: 1.1.0f-2~ubuntu14.04.1+deb.sury.org+4
-   Candidate: 1.1.0f-2~ubuntu14.04.1+deb.sury.org+4
-   Version table:
-  *** 1.1.0f-2~ubuntu14.04.1+deb.sury.org+4 0
- 500 http://ppa.launchpad.net/ondrej/apache2/ubuntu/ trusty/main i386 
Packages
- 100 /var/lib/dpkg/status
-  1.1.0f-2~ubuntu14.04.1+deb.sury.org+1 0
- 500 http://ppa.launchpad.net/ondrej/php/ubuntu/ trusty/main i386 
Packages
-  1.0.1f-1ubuntu2.22 0
- 500 http://si.archive.ubuntu.com/ubuntu/ trusty-updates/main i386 
Packages
- 500 http://security.ubuntu.com/ubuntu/ trusty-security/main i386 
Packages
-  1.0.1f-1ubuntu2 0
- 500 http://si.archive.ubuntu.com/ubuntu/ trusty/main i386 Packages
- 
- lsb_release -rd
- 
- Description:  Ubuntu 14.04.5 LTS
- Release:  14.04
+   Installed: 1.1.0f-2~ubuntu14.04.1+deb.sury.org+4
+   Candidate: 1.1.0f-2~ubuntu14.04.1+deb.sury.org+4
+   Version table:
+  *** 1.1.0f-2~ubuntu14.04.1+deb.sury.org+4 0
+ 500 http://ppa.launchpad.net/ondrej/apache2/ubuntu/ trusty/main i386 
Packages
+ 100 /var/lib/dpkg/status
+  1.1.0f-2~ubuntu14.04.1+deb.sury.org+1 0
+ 500 http://ppa.launchpad.net/ondrej/php/ubuntu/ trusty/main i386 
Packages
+  1.0.1f-1ubuntu2.22 0
+ 500 http://si.archive.ubuntu.com/ubuntu/ trusty-updates/main i386 
Packages
+ 500 http://security.ubuntu.com/ubuntu/ trusty-security/main i386 
Packages
+  1.0.1f-1ubuntu2 0
+ 500 http://si.archive.ubuntu.com/ubuntu/ trusty/main i386 Packages
  
  
- I have tried so many things but no solution yet, so I think this is a 
possible bug.
- 
- Full debate about this issue is here:
- https://serverfault.com/questions/859987/im-getting-error-ssl3-get-
- recorddecryption-failed-or-bad-record-mac
+ Full debate about this issue is here (also some other users suspected a bug): 
https://serverfault.com/questions/859987/im-getting-error-ssl3-get-recorddecryption-failed-or-bad-record-mac

** Description changed:

  Adter so many tries to solve this issue we were unable to find a
  solution. So from that point we assumed that it can be a possible bug.
  
  It was tested on Apache/2.4.27
  
  lsb_release -rd
  
  Description:  Ubuntu 14.04.5 LTS
  Release:  14.04
  
  OpenSSL version 1.1.0f
  
  Our options-ssl-apache.conf;
  
  SSLProtocol all -SSLv2 -SSLv3
  SSLCipherSuite  EECDH+AESGCM:EDH+AESGCM:AES256+EECDH:AES256+EDH
  SSLHonorCipherOrder on
  SSLCompression  off
  
  We tried to manipulate and change CipherSuite but same error will appear
  always.
  
- 
  If I try openssl s_client -connect mywebsite.com:443, it will return:
- 
- I'm using: OpenSSL 1.1.0f
  
  CONNECTED(0003)
  
  ...
  
  3073276480:error:1408F119:SSL routines:ssl3_get_record:decryption failed
  or bad record mac:../ssl/record/ssl3_record.c:469:
+ 
  
  apt-cache policy openssl
  
  openssl:
    Installed: 1.1.0f-2~ubuntu14.04.1+deb.sury.org+4
    Candidate: 1.1.0f-2~ubuntu14.04.1+deb.sury.org+4
    Version table:
   *** 1.1.0f-2~ubuntu14.04.1+deb.sury.org+4 0
  

[Touch-packages] [Bug 1704585] [NEW] I'm getting error: SSL3_GET_RECORD:decryption failed or bad record mac

2017-07-15 Thread als
Public bug reported:

I have my own server (where I'm running Apache/2.4.27), and today I
realized that from (Brave and Google Chrome - different computers) I'm
getting from my websites this error;

This site can’t provide a secure connection

mywebsite.com sent an invalid response.
ERR_SSL_PROTOCOL_ERROR

And the strange thing is that I'm getting this error every fifth click
on my website.

>From my conf file:

SSLEngine on
SSLCertificateFile /etc/letsencrypt/live/mywebsite/cert.pem
SSLCertificateKeyFile /etc/letsencrypt/live/mywebsite/privkey.pem
Include /etc/letsencrypt/options-ssl-apache.conf
SSLCertificateChainFile /etc/letsencrypt/live/mywebsite/chain.pem
SSLCompression off

from options-ssl-apache.conf;

SSLProtocol all -SSLv2 -SSLv3
SSLCipherSuite  EECDH+AESGCM:EDH+AESGCM:AES256+EECDH:AES256+EDH
SSLHonorCipherOrder on
SSLCompression  off

I have checked log file from website but nothing, also nothing here;
/var/log/apache2/error.log

I'm trying to figure out what is causing this error, any ideas where can
I find more info or even better, how to solve this problem?

EDIT:

If I try openssl s_client -connect mywebsite.com:443, it will return:

I'm using: OpenSSL 1.1.0f

CONNECTED(0003)

...

3073276480:error:1408F119:SSL routines:ssl3_get_record:decryption failed
or bad record mac:../ssl/record/ssl3_record.c:469:

apt-cache policy openssl
openssl:
  Installed: 1.1.0f-2~ubuntu14.04.1+deb.sury.org+4
  Candidate: 1.1.0f-2~ubuntu14.04.1+deb.sury.org+4
  Version table:
 *** 1.1.0f-2~ubuntu14.04.1+deb.sury.org+4 0
500 http://ppa.launchpad.net/ondrej/apache2/ubuntu/ trusty/main i386 
Packages
100 /var/lib/dpkg/status
 1.1.0f-2~ubuntu14.04.1+deb.sury.org+1 0
500 http://ppa.launchpad.net/ondrej/php/ubuntu/ trusty/main i386 
Packages
 1.0.1f-1ubuntu2.22 0
500 http://si.archive.ubuntu.com/ubuntu/ trusty-updates/main i386 
Packages
500 http://security.ubuntu.com/ubuntu/ trusty-security/main i386 
Packages
 1.0.1f-1ubuntu2 0
500 http://si.archive.ubuntu.com/ubuntu/ trusty/main i386 Packages

lsb_release -rd

Description:Ubuntu 14.04.5 LTS
Release:14.04


I have tried so many things but no solution yet, so I think this is a possible 
bug.

Full debate about this issue is here:
https://serverfault.com/questions/859987/im-getting-error-ssl3-get-
recorddecryption-failed-or-bad-record-mac

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


** Tags: openssl

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

Title:
   I'm getting error: SSL3_GET_RECORD:decryption failed or bad record
  mac

Status in openssl package in Ubuntu:
  New

Bug description:
  I have my own server (where I'm running Apache/2.4.27), and today I
  realized that from (Brave and Google Chrome - different computers) I'm
  getting from my websites this error;

  This site can’t provide a secure connection

  mywebsite.com sent an invalid response.
  ERR_SSL_PROTOCOL_ERROR

  And the strange thing is that I'm getting this error every fifth click
  on my website.

  From my conf file:

  SSLEngine on
  SSLCertificateFile /etc/letsencrypt/live/mywebsite/cert.pem
  SSLCertificateKeyFile /etc/letsencrypt/live/mywebsite/privkey.pem
  Include /etc/letsencrypt/options-ssl-apache.conf
  SSLCertificateChainFile /etc/letsencrypt/live/mywebsite/chain.pem
  SSLCompression off

  from options-ssl-apache.conf;

  SSLProtocol all -SSLv2 -SSLv3
  SSLCipherSuite  EECDH+AESGCM:EDH+AESGCM:AES256+EECDH:AES256+EDH
  SSLHonorCipherOrder on
  SSLCompression  off

  I have checked log file from website but nothing, also nothing here;
  /var/log/apache2/error.log

  I'm trying to figure out what is causing this error, any ideas where
  can I find more info or even better, how to solve this problem?

  EDIT:

  If I try openssl s_client -connect mywebsite.com:443, it will return:

  I'm using: OpenSSL 1.1.0f

  CONNECTED(0003)

  ...

  3073276480:error:1408F119:SSL routines:ssl3_get_record:decryption
  failed or bad record mac:../ssl/record/ssl3_record.c:469:

  apt-cache policy openssl
  openssl:
Installed: 1.1.0f-2~ubuntu14.04.1+deb.sury.org+4
Candidate: 1.1.0f-2~ubuntu14.04.1+deb.sury.org+4
Version table:
   *** 1.1.0f-2~ubuntu14.04.1+deb.sury.org+4 0
  500 http://ppa.launchpad.net/ondrej/apache2/ubuntu/ trusty/main i386 
Packages
  100 /var/lib/dpkg/status
   1.1.0f-2~ubuntu14.04.1+deb.sury.org+1 0
  500 http://ppa.launchpad.net/ondrej/php/ubuntu/ trusty/main i386 
Packages
   1.0.1f-1ubuntu2.22 0
  500 http://si.archive.ubuntu.com/ubuntu/ trusty-updates/main i386 
Packages
  500 http://security.ubuntu.com/ubuntu/ trusty-security/main i386 
Packages
   1.0.1f-1ubuntu2 0
  500 

[Touch-packages] [Bug 1689825] Re: gnome-keyring not unlocked on boot

2017-07-15 Thread Coeur Noir
I can also confirm that un-installing dbus-user-session solved the
issue.

Does flatpak always install it / or only some app's ?

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

Title:
  gnome-keyring not unlocked on boot

Status in D-Bus:
  New
Status in chromium-browser package in Ubuntu:
  Invalid
Status in flatpak package in Ubuntu:
  Confirmed
Status in gdm package in Ubuntu:
  Confirmed
Status in gnome-keyring package in Ubuntu:
  Confirmed
Status in libgnome-keyring package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  1) Release: 16.04.2
  2) gnome-keyring: 3.18.3-0ubuntu2
  3) Login. gnome-keyring unlocks "login" features including for google chrome
  4) gnome-keyring is not unlocked, chrome takes 2 minutes to open and with no 
secure password features(sync) functioning.

  For the past couple days, chrome on Ubuntu 16.04 takes a REALLY long
  time (maybe 2 minutes) to start. Once chrome is started, I am not able
  to sync and any secure password features are broken. I found out this
  is due to gnome-keyring not being unlocked at login. There's also no
  way to unlock the "login" portion of the keyring from the running
  daemon by default. I have to kill the gnome-keyring process and start
  without "--login" as a parameter. Then the "login" section shows up
  which I'm able to unlock. From there chrome starts up instantly but
  asks the following:

  Enter password to unlock your login keyring
  The login keyring did not get unlocked when you logged into your computer

  After that, all of it's sync and secure features are functional.

  Starting google-chrome-stable from a command line at boot without
  running the above workaround shows the following error messages:

  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  [4364:4393:0510/100407.740292:ERROR:token_service_table.cc(130)] Failed to 
decrypt token for service AccountId-108842767310111573264
  [4364:4445:0510/100407.740292:ERROR:gcm_store_impl.cc(929)] Failed to restore 
security token.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-keyring 3.18.3-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Wed May 10 09:43:37 2017
  SourcePackage: gnome-keyring
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/dbus/+bug/1689825/+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 1704578] [NEW] Ubuntu 16.04 - No sound from speakers. But headphone works fine.

2017-07-15 Thread nepupya
Public bug reported:

I use my computer with a dual boot. Win 10 and Ubuntu 16.04.2 LTS. After
an upgrade in windows or Ubuntu i can't get sound from speakers. But
headphone or an hdmi output works fine. It would really appreciate if
someone finds a solution for my problem.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
Uname: Linux 4.4.0-83-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.9
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  aypupen1753 F pulseaudio
CurrentDesktop: Unity
Date: Sat Jul 15 20:22:13 2017
InstallationDate: Installed on 2016-11-17 (240 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  aypupen1753 F pulseaudio
Symptom_Jack: Speaker, Internal
Symptom_Type: No sound at all
Title: [80TY, Realtek Generic, Speaker, Internal] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/13/2017
dmi.bios.vendor: LENOVO
dmi.bios.version: 0GCN22WW(V1.06)
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: Lenovo Yoga710-1
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo Yoga710-14ISK
dmi.modalias: 
dmi:bvnLENOVO:bvr0GCN22WW(V1.06):bd02/13/2017:svnLENOVO:pn80TY:pvrLenovoYoga710-14ISK:rvnLENOVO:rnLenovoYoga710-1:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYoga710-14ISK:
dmi.product.name: 80TY
dmi.product.version: Lenovo Yoga710-14ISK
dmi.sys.vendor: LENOVO

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug xenial

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

Title:
  Ubuntu 16.04 - No sound from speakers. But headphone works fine.

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I use my computer with a dual boot. Win 10 and Ubuntu 16.04.2 LTS.
  After an upgrade in windows or Ubuntu i can't get sound from speakers.
  But headphone or an hdmi output works fine. It would really appreciate
  if someone finds a solution for my problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
  Uname: Linux 4.4.0-83-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aypupen1753 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Jul 15 20:22:13 2017
  InstallationDate: Installed on 2016-11-17 (240 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aypupen1753 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [80TY, Realtek Generic, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/13/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 0GCN22WW(V1.06)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lenovo Yoga710-1
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga710-14ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvr0GCN22WW(V1.06):bd02/13/2017:svnLENOVO:pn80TY:pvrLenovoYoga710-14ISK:rvnLENOVO:rnLenovoYoga710-1:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYoga710-14ISK:
  dmi.product.name: 80TY
  dmi.product.version: Lenovo Yoga710-14ISK
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1704578/+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 1689825] Re: gnome-keyring not unlocked on boot

2017-07-15 Thread Antonios Hadjigeorgalis
I can now confirm that these instructions have worked for me.  Thank you
all.  I did change my password as suggested in comment #74 by
bytecommander.

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

Title:
  gnome-keyring not unlocked on boot

Status in D-Bus:
  New
Status in chromium-browser package in Ubuntu:
  Invalid
Status in flatpak package in Ubuntu:
  Confirmed
Status in gdm package in Ubuntu:
  Confirmed
Status in gnome-keyring package in Ubuntu:
  Confirmed
Status in libgnome-keyring package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  1) Release: 16.04.2
  2) gnome-keyring: 3.18.3-0ubuntu2
  3) Login. gnome-keyring unlocks "login" features including for google chrome
  4) gnome-keyring is not unlocked, chrome takes 2 minutes to open and with no 
secure password features(sync) functioning.

  For the past couple days, chrome on Ubuntu 16.04 takes a REALLY long
  time (maybe 2 minutes) to start. Once chrome is started, I am not able
  to sync and any secure password features are broken. I found out this
  is due to gnome-keyring not being unlocked at login. There's also no
  way to unlock the "login" portion of the keyring from the running
  daemon by default. I have to kill the gnome-keyring process and start
  without "--login" as a parameter. Then the "login" section shows up
  which I'm able to unlock. From there chrome starts up instantly but
  asks the following:

  Enter password to unlock your login keyring
  The login keyring did not get unlocked when you logged into your computer

  After that, all of it's sync and secure features are functional.

  Starting google-chrome-stable from a command line at boot without
  running the above workaround shows the following error messages:

  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  [4364:4393:0510/100407.740292:ERROR:token_service_table.cc(130)] Failed to 
decrypt token for service AccountId-108842767310111573264
  [4364:4445:0510/100407.740292:ERROR:gcm_store_impl.cc(929)] Failed to restore 
security token.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-keyring 3.18.3-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Wed May 10 09:43:37 2017
  SourcePackage: gnome-keyring
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/dbus/+bug/1689825/+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 1704572] Re: package libnl-route-3-200:amd64 3.2.27-1ubuntu0.16.04.1 failed to install/upgrade: package libnl-route-3-200:amd64 is not ready for configuration cannot configure (c

2017-07-15 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package libnl-route-3-200:amd64 3.2.27-1ubuntu0.16.04.1 failed to
  install/upgrade: package libnl-route-3-200:amd64 is not ready for
  configuration  cannot configure (current status 'half-installed')

Status in libnl3 package in Ubuntu:
  New

Bug description:
  System update failed because this package could not be removed.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libnl-route-3-200:amd64 3.2.27-1ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
  Uname: Linux 4.4.0-83-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.9
  Architecture: amd64
  Date: Sat Jul 15 18:24:00 2017
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu9
   libgcc1 1:6.0.1-0ubuntu1
   libnl-3-200 3.2.27-1ubuntu0.16.04.1
  DuplicateSignature:
   package:libnl-route-3-200:amd64:3.2.27-1ubuntu0.16.04.1
   Processing triggers for gconf2 (3.2.6-3ubuntu6) ...
   dpkg: error processing package libnl-route-3-200:amd64 (--configure):
package libnl-route-3-200:amd64 is not ready for configuration
  ErrorMessage: package libnl-route-3-200:amd64 is not ready for configuration  
cannot configure (current status 'half-installed')
  InstallationDate: Installed on 2016-10-20 (267 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: libnl3
  Title: package libnl-route-3-200:amd64 3.2.27-1ubuntu0.16.04.1 failed to 
install/upgrade: package libnl-route-3-200:amd64 is not ready for configuration 
 cannot configure (current status 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1704572/+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 1704572] [NEW] package libnl-route-3-200:amd64 3.2.27-1ubuntu0.16.04.1 failed to install/upgrade: package libnl-route-3-200:amd64 is not ready for configuration cannot configure

2017-07-15 Thread K.D.
Public bug reported:

System update failed because this package could not be removed.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libnl-route-3-200:amd64 3.2.27-1ubuntu0.16.04.1
ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
Uname: Linux 4.4.0-83-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.9
Architecture: amd64
Date: Sat Jul 15 18:24:00 2017
Dependencies:
 gcc-6-base 6.0.1-0ubuntu1
 libc6 2.23-0ubuntu9
 libgcc1 1:6.0.1-0ubuntu1
 libnl-3-200 3.2.27-1ubuntu0.16.04.1
DuplicateSignature:
 package:libnl-route-3-200:amd64:3.2.27-1ubuntu0.16.04.1
 Processing triggers for gconf2 (3.2.6-3ubuntu6) ...
 dpkg: error processing package libnl-route-3-200:amd64 (--configure):
  package libnl-route-3-200:amd64 is not ready for configuration
ErrorMessage: package libnl-route-3-200:amd64 is not ready for configuration  
cannot configure (current status 'half-installed')
InstallationDate: Installed on 2016-10-20 (267 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: libnl3
Title: package libnl-route-3-200:amd64 3.2.27-1ubuntu0.16.04.1 failed to 
install/upgrade: package libnl-route-3-200:amd64 is not ready for configuration 
 cannot configure (current status 'half-installed')
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package xenial

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

Title:
  package libnl-route-3-200:amd64 3.2.27-1ubuntu0.16.04.1 failed to
  install/upgrade: package libnl-route-3-200:amd64 is not ready for
  configuration  cannot configure (current status 'half-installed')

Status in libnl3 package in Ubuntu:
  New

Bug description:
  System update failed because this package could not be removed.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libnl-route-3-200:amd64 3.2.27-1ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
  Uname: Linux 4.4.0-83-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.9
  Architecture: amd64
  Date: Sat Jul 15 18:24:00 2017
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu9
   libgcc1 1:6.0.1-0ubuntu1
   libnl-3-200 3.2.27-1ubuntu0.16.04.1
  DuplicateSignature:
   package:libnl-route-3-200:amd64:3.2.27-1ubuntu0.16.04.1
   Processing triggers for gconf2 (3.2.6-3ubuntu6) ...
   dpkg: error processing package libnl-route-3-200:amd64 (--configure):
package libnl-route-3-200:amd64 is not ready for configuration
  ErrorMessage: package libnl-route-3-200:amd64 is not ready for configuration  
cannot configure (current status 'half-installed')
  InstallationDate: Installed on 2016-10-20 (267 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: libnl3
  Title: package libnl-route-3-200:amd64 3.2.27-1ubuntu0.16.04.1 failed to 
install/upgrade: package libnl-route-3-200:amd64 is not ready for configuration 
 cannot configure (current status 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1704572/+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 1704559] Re: often no wifi connections shown

2017-07-15 Thread Stefan Helmert
This may be a security problem, because also the currently running
connection is also not shown/named. It looks like wifi is inactive, but
the computer may be connected to an insecure, unencrypted or fishy
network without user knowledge.

** Summary changed:

- often now wifi connections shown
+ often no wifi connections shown

** Information type changed from Public to Public Security

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

Title:
  often no wifi connections shown

Status in network-manager package in Ubuntu:
  New

Bug description:
  On Ubuntu 16.04.2: The network-manager often does not show wifi
  networks. The connection may be runningen without problems at the same
  time.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.6-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
  Uname: Linux 4.4.0-83-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Jul 15 15:53:53 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
   auto enp0s25
   iface enp0s25 inet manual
  IpRoute:
   default via 172.22.99.1 dev wlp3s0  proto static  metric 600 
   169.254.0.0/16 dev docker0  scope link  metric 1000 linkdown 
   172.17.0.0/16 dev docker0  proto kernel  scope link  src 172.17.0.1 linkdown 
   172.18.0.0/16 dev br-d5edc0a60a9c  proto kernel  scope link  src 172.18.0.1 
   172.22.99.0/24 dev wlp3s0  proto kernel  scope link  src 172.22.99.149  
metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2017-04-14T17:29:21.619202
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1704559/+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 1704570] [NEW] [Inspiron 15-3555, Realtek ALC3234, Mic, Internal] Recording problem

2017-07-15 Thread bismi maria jose
Public bug reported:

people over the other side cant hear voice ..something is wrong with
input microphone

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
Uname: Linux 4.4.0-79-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.4
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC1D0p:   bismi  1759 F...m pulseaudio
 /dev/snd/controlC1:  bismi  1759 F pulseaudio
 /dev/snd/controlC0:  bismi  1759 F pulseaudio
CurrentDesktop: Unity
Date: Sat Jul 15 21:05:30 2017
InstallationDate: Installed on 2017-02-15 (149 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=en_IN:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_IN
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaRecordingTest: ALSA recording test through plughw:Generic failed
Symptom_Card: Built-in Audio - HD-Audio Generic
Symptom_Jack: Mic, Internal
Symptom_Type: None of the above
Title: [Inspiron 15-3555, Realtek ALC3234, Mic, Internal] Recording problem
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/28/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.0.1
dmi.board.name: Inspiron 15-3555
dmi.board.vendor: Dell Inc.
dmi.board.version: 1.0.1
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.1:bd01/28/2016:svnDellInc.:pnInspiron15-3555:pvrNotSpecified:rvnDellInc.:rnInspiron15-3555:rvr1.0.1:cvnDellInc.:ct8:cvrNotSpecified:
dmi.product.name: Inspiron 15-3555
dmi.product.version: Not Specified
dmi.sys.vendor: Dell Inc.

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug xenial

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

Title:
  [Inspiron 15-3555, Realtek ALC3234, Mic, Internal] Recording problem

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  people over the other side cant hear voice ..something is wrong with
  input microphone

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
  Uname: Linux 4.4.0-79-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   bismi  1759 F...m pulseaudio
   /dev/snd/controlC1:  bismi  1759 F pulseaudio
   /dev/snd/controlC0:  bismi  1759 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Jul 15 21:05:30 2017
  InstallationDate: Installed on 2017-02-15 (149 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:Generic failed
  Symptom_Card: Built-in Audio - HD-Audio Generic
  Symptom_Jack: Mic, Internal
  Symptom_Type: None of the above
  Title: [Inspiron 15-3555, Realtek ALC3234, Mic, Internal] Recording problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/28/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.1
  dmi.board.name: Inspiron 15-3555
  dmi.board.vendor: Dell Inc.
  dmi.board.version: 1.0.1
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.1:bd01/28/2016:svnDellInc.:pnInspiron15-3555:pvrNotSpecified:rvnDellInc.:rnInspiron15-3555:rvr1.0.1:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 15-3555
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1704570/+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 1563110] Re: No sound on Asus e200ha, intel sst with cx2072x codec

2017-07-15 Thread Venkat Bala
@Marek, I couldn't get sound working with kernel 4.12 on my laptop.

@Andrei, my sd card reader worked intermittently but since then I
haven't had any success. Switched back to windows for a while...but came
back to try out the latest kernel, but got no success with sound or SD
card reader.

any fixes available so far?

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

Title:
  No sound on Asus e200ha, intel sst with cx2072x codec

Status in ALSA driver:
  Unknown
Status in alsa-driver package in Ubuntu:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  I've recently bought an Asus e200ha.
  Sound in this laptop doesn't work.
  The sound card is an intel sst with codec conexant cx2072x

  aplay -l:
  aplay: device_list:268: no soundcard found...
  in the sound setting there is a "Dummy output"
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a
  InstallationDate: Installed on 2016-03-28 (0 days ago)
  InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105
  Lsusb:
   Bus 002 Device 002: ID 0781:5583 SanDisk Corp. 
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:3496 IMC Networks 
   Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. E200HA
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic 
root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-32-generic N/A
   linux-backports-modules-3.19.0-32-generic  N/A
   linux-firmware 1.127.16
  Tags:  rosa
  Uname: Linux 3.19.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/26/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E200HA.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: E200HA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: E200HA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/alsa-driver/+bug/1563110/+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 1702679] Re: binutils fails to build glibc-2.24 on aarch64-linux-gnu and arm-linux-gnueabihf

2017-07-15 Thread Bug Watch Updater
** Changed in: binutils
   Status: Confirmed => Fix Released

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

Title:
  binutils fails to build glibc-2.24 on aarch64-linux-gnu and arm-linux-
  gnueabihf

Status in binutils:
  Fix Released
Status in binutils package in Ubuntu:
  Confirmed
Status in glibc package in Ubuntu:
  New

Bug description:
  Trying to build glibc-2.24 on aarch64-linux-gnu and arm-linux-
  gnueabihf, the build fails when trying to run localedef in the check
  target, the just built localedef segfaulting. This glibc build ok when
  building with binutils from the 2.28 branch.

  glibc-2.24 needs upstream commit
  388b4f1a02f3a801965028bbfcd48d905638b797 backported to 2.24 to build.

  Program terminated with signal SIGSEGV, Segmentation fault.
  #0  0xd00c5d28 in _dl_start_user ()
 from 
/home/ubuntu/glibc/glibc-2.24/build-tree/arm64-libc/elf/ld-linux-aarch64.so.1
  (gdb) bt
  #0  0xd00c5d28 in _dl_start_user ()
 from 
/home/ubuntu/glibc/glibc-2.24/build-tree/arm64-libc/elf/ld-linux-aarch64.so.1
  #1  0xd00c5cc8 in _start ()
 from 
/home/ubuntu/glibc/glibc-2.24/build-tree/arm64-libc/elf/ld-linux-aarch64.so.1
  Backtrace stopped: previous frame identical to this frame (corrupt stack?)

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


Re: [Touch-packages] [Bug 1692981] Re: package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting con

2017-07-15 Thread Stephen Ewert
Done.

On Jul 15, 2017 5:41 AM, "Fernando Couto" <1692...@bugs.launchpad.net>
wrote:

> It seems that  sudo apt-get install –reinstall libc6-dbg: amd64
>
> is working for my computer too.
>
> Thank you very much to everybody!!
>
>
> 2017-07-15 0:28 GMT+02:00 vincenzo <1692...@bugs.launchpad.net>:
>
> > Thanks to everyone I solved the bug  in fact it was the package
> > that was not installed properly. I just had to reinstall the whole
> > thing
> >
> > If anyone may be interested
> >
> > Sudo apt-get install --reinstall libc6-dbg: amd64
> >
> >
> > Thank you again to everyone!!
> >
> > vincenzo
> >
> >
> >
> > 2017-07-14 11:25 GMT+02:00 carduner <1692...@bugs.launchpad.net>:
> >
> > > It works, after reinstall the packets (libc6-dbg:amd64 and openssl)
> > > Thanks Seth!
> > >
> > > Le 12/07/2017 à 20:52, Seth Arnold a écrit :
> > > > I'm curious how we can work around this bug. If you're affected
> please
> > > > report the results of:
> > > >
> > > > dpkg -l | awk '/^iH/ { print $2 }'
> > > >
> > > > This shows which specific packages are half-installed on your
> systems.
> > > >
> > > > With the list of packages this returns, please also report success or
> > > > failure of:
> > > >
> > > > sudo apt-get install --reinstall ALL PACKAGES FROM THE HALF-INSTALLED
> > > > LIST
> > > >
> > > > Thanks
> > > >
> > >
> > > --
> > > You received this bug notification because you are subscribed to a
> > > duplicate bug report (1701676).
> > > https://bugs.launchpad.net/bugs/1692981
> > >
> > > Title:
> > >   package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to
> install/upgrade:
> > >   package is in a very bad inconsistent state; you should  reinstall it
> > >   before attempting configuration
> > >
> > > Status in dpkg package in Ubuntu:
> > >   Confirmed
> > > Status in openssl package in Ubuntu:
> > >   Confirmed
> > >
> > > Bug description:
> > >   package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to
> install/upgrade:
> > >   package is in a very bad inconsistent state; you should  reinstall it
> > >   before attempting configuration
> > >
> > >   ProblemType: Package
> > >   DistroRelease: Ubuntu 17.04
> > >   Package: libssl-dev:amd64 1.0.2g-1ubuntu11.2
> > >   ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
> > >   Uname: Linux 4.10.0-21-generic x86_64
> > >   ApportVersion: 2.20.4-0ubuntu4.1
> > >   AptOrdering:
> > >libssl1.0.0:amd64: Install
> > >NULL: ConfigurePending
> > >   Architecture: amd64
> > >   Date: Tue May 23 21:47:55 2017
> > >   DuplicateSignature:
> > >package:libssl-dev:amd64:1.0.2g-1ubuntu11.2
> > >Setting up libssl1.0.0:amd64 (1.0.2g-1ubuntu11.2) ...
> > >dpkg: error processing package libssl-dev:amd64 (--configure):
> > > package is in a very bad inconsistent state; you should
> > >   ErrorMessage: package is in a very bad inconsistent state; you should
> > > reinstall it before attempting configuration
> > >   InstallationDate: Installed on 2017-05-15 (7 days ago)
> > >   InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64
> > (20170412)
> > >   RelatedPackageVersions:
> > >dpkg 1.18.10ubuntu2
> > >apt  1.4
> > >   SourcePackage: openssl
> > >   Title: package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to
> > > install/upgrade: package is in a very bad inconsistent state; you
> should
> > > reinstall it before attempting configuration
> > >   UpgradeStatus: No upgrade log present (probably fresh install)
> > >
> > > To manage notifications about this bug go to:
> > > https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/
> > 1692981/+subscriptions
> > >
> >
> > --
> > You received this bug notification because you are subscribed to a
> > duplicate bug report (1701880).
> > https://bugs.launchpad.net/bugs/1692981
> >
> > Title:
> >   package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade:
> >   package is in a very bad inconsistent state; you should  reinstall it
> >   before attempting configuration
> >
> > Status in dpkg package in Ubuntu:
> >   Confirmed
> > Status in openssl package in Ubuntu:
> >   Confirmed
> >
> > Bug description:
> >   package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade:
> >   package is in a very bad inconsistent state; you should  reinstall it
> >   before attempting configuration
> >
> >   ProblemType: Package
> >   DistroRelease: Ubuntu 17.04
> >   Package: libssl-dev:amd64 1.0.2g-1ubuntu11.2
> >   ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
> >   Uname: Linux 4.10.0-21-generic x86_64
> >   ApportVersion: 2.20.4-0ubuntu4.1
> >   AptOrdering:
> >libssl1.0.0:amd64: Install
> >NULL: ConfigurePending
> >   Architecture: amd64
> >   Date: Tue May 23 21:47:55 2017
> >   DuplicateSignature:
> >package:libssl-dev:amd64:1.0.2g-1ubuntu11.2
> >Setting up libssl1.0.0:amd64 (1.0.2g-1ubuntu11.2) ...
> >dpkg: error processing package libssl-dev:amd64 (--configure):
> > package is in a very bad inconsistent state; you should
> >   

[Touch-packages] [Bug 32016] Re: nm-applet shows no connections (cannot control Network Manager)

2017-07-15 Thread Stefan Helmert
Happens often also in Ubuntu 16.04.2, maybe in combination with standy.

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

Title:
  nm-applet shows no connections (cannot control Network Manager)

Status in network-manager package in Ubuntu:
  Fix Released

Bug description:
  From the 2/19/06 upgrade of the network-manager and nm-applet
  packages, nm-applet no longer shows any network connections. It only
  shows the "wired network disconnected" icon and left-clicking it shows
  the grayed out "Wired Network" option and nothing else. The wireless
  network still seems to be initialized by Network Manager, I just have
  no control over it via nm-applet. I have tried removing nm-applet and
  network-manager and reinstalling them, but the same thing happens.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/32016/+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 1704559] [NEW] often now wifi connections shown

2017-07-15 Thread Stefan Helmert
Public bug reported:

On Ubuntu 16.04.2: The network-manager often does not show wifi
networks. The connection may be runningen without problems at the same
time.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: network-manager 1.2.6-0ubuntu0.16.04.1
ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
Uname: Linux 4.4.0-83-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
CurrentDesktop: Unity
Date: Sat Jul 15 15:53:53 2017
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
 auto enp0s25
 iface enp0s25 inet manual
IpRoute:
 default via 172.22.99.1 dev wlp3s0  proto static  metric 600 
 169.254.0.0/16 dev docker0  scope link  metric 1000 linkdown 
 172.17.0.0/16 dev docker0  proto kernel  scope link  src 172.17.0.1 linkdown 
 172.18.0.0/16 dev br-d5edc0a60a9c  proto kernel  scope link  src 172.18.0.1 
 172.22.99.0/24 dev wlp3s0  proto kernel  scope link  src 172.22.99.149  metric 
600
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2017-04-14T17:29:21.619202
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  enabled

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug xenial

** Attachment added: "empty wifi list, but wifi working"
   
https://bugs.launchpad.net/bugs/1704559/+attachment/4915126/+files/NetworkmanagerEmptyWifi.png

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

Title:
  often now wifi connections shown

Status in network-manager package in Ubuntu:
  New

Bug description:
  On Ubuntu 16.04.2: The network-manager often does not show wifi
  networks. The connection may be runningen without problems at the same
  time.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.6-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
  Uname: Linux 4.4.0-83-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Jul 15 15:53:53 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
   auto enp0s25
   iface enp0s25 inet manual
  IpRoute:
   default via 172.22.99.1 dev wlp3s0  proto static  metric 600 
   169.254.0.0/16 dev docker0  scope link  metric 1000 linkdown 
   172.17.0.0/16 dev docker0  proto kernel  scope link  src 172.17.0.1 linkdown 
   172.18.0.0/16 dev br-d5edc0a60a9c  proto kernel  scope link  src 172.18.0.1 
   172.22.99.0/24 dev wlp3s0  proto kernel  scope link  src 172.22.99.149  
metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2017-04-14T17:29:21.619202
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1704559/+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 1510511] Re: machinectl pull-raw fails: No space left on device

2017-07-15 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: systemd (Ubuntu)
   Status: New => Confirmed

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

Title:
  machinectl pull-raw fails: No space left on device

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  $ machinectl pull-raw https://cloud-images.ubuntu.com/trusty/current
  /trusty-server-cloudimg-amd64-disk1.img

  fails to expand /var/lib/machines.raw or /var/lib/machines, and thus
  fails to complete:

  SHA256 checksum of 
https://cloud-images.ubuntu.com/trusty/current/trusty-server-cloudimg-amd64-disk1.img
 is valid.
  gpg: Signature made Wed 21 Oct 2015 16:06:28 BST using RSA key ID 7DB87C81
  gpg: Good signature from "UEC Image Automatic Signing Key 
" [unknown]
  gpg: WARNING: Using untrusted key!
  Signature verification succeeded.
  Unpacking QCOW2 file.
  Failed to convert qcow2 image: No space left on device
  Exiting.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1510511/+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 1483430] Re: /usr/bin/mate-panel:ERROR:/build/buildd/gtk+2.0-2.24.27/modules/other/gail/gail.c:622:gail_focus_notify_when_idle: code should not be reached

2017-07-15 Thread Vlad Orlov
*** This bug is a duplicate of bug 1359308 ***
https://bugs.launchpad.net/bugs/1359308

** Package changed: gail (Ubuntu) => gtk+2.0 (Ubuntu)

** This bug has been marked a duplicate of bug 1359308
   mate-panel crashed when using window list

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

Title:
  /usr/bin/mate-
  
panel:ERROR:/build/buildd/gtk+2.0-2.24.27/modules/other/gail/gail.c:622:gail_focus_notify_when_idle:
  code should not be reached

Status in gtk+2.0 package in Ubuntu:
  New
Status in mate-panel package in Ubuntu:
  Invalid

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding mate-panel.  This problem was most recently seen with
  version 1.8.1+dfsg1-3, the problem page at
  https://errors.ubuntu.com/problem/558945d278bfc3a06a03bc65607f51b8c4403af6
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1483430/+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 1483430] Re: /usr/bin/mate-panel:ERROR:/build/buildd/gtk+2.0-2.24.27/modules/other/gail/gail.c:622:gail_focus_notify_when_idle: code should not be reached

2017-07-15 Thread Launchpad Bug Tracker
*** This bug is a duplicate of bug 1359308 ***
https://bugs.launchpad.net/bugs/1359308

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: gtk+2.0 (Ubuntu)
   Status: New => Confirmed

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

Title:
  /usr/bin/mate-
  
panel:ERROR:/build/buildd/gtk+2.0-2.24.27/modules/other/gail/gail.c:622:gail_focus_notify_when_idle:
  code should not be reached

Status in gtk+2.0 package in Ubuntu:
  New
Status in mate-panel package in Ubuntu:
  Invalid

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding mate-panel.  This problem was most recently seen with
  version 1.8.1+dfsg1-3, the problem page at
  https://errors.ubuntu.com/problem/558945d278bfc3a06a03bc65607f51b8c4403af6
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1483430/+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 1598347] Re: /usr/bin/mate-panel:ERROR:/build/gtk+2.0-4ZhNBE/gtk+2.0-2.24.30/modules/other/gail/gail.c:622:gail_focus_notify_when_idle: code should not be reached

2017-07-15 Thread Vlad Orlov
*** This bug is a duplicate of bug 1359308 ***
https://bugs.launchpad.net/bugs/1359308

** Package changed: mate-panel (Ubuntu) => gtk+2.0 (Ubuntu)

** This bug has been marked a duplicate of bug 1359308
   mate-panel crashed when using window list

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

Title:
  /usr/bin/mate-
  
panel:ERROR:/build/gtk+2.0-4ZhNBE/gtk+2.0-2.24.30/modules/other/gail/gail.c:622:gail_focus_notify_when_idle:
  code should not be reached

Status in gtk+2.0 package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding mate-panel.  This problem was most recently seen with
  version 1.12.2-1, the problem page at
  https://errors.ubuntu.com/problem/4b6610a1d753c24afed0539ed6e21646fcbbdf6e
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1598347/+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 1483430] [NEW] /usr/bin/mate-panel:ERROR:/build/buildd/gtk+2.0-2.24.27/modules/other/gail/gail.c:622:gail_focus_notify_when_idle: code should not be reached

2017-07-15 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

The Ubuntu Error Tracker has been receiving reports about a problem
regarding mate-panel.  This problem was most recently seen with version
1.8.1+dfsg1-3, the problem page at
https://errors.ubuntu.com/problem/558945d278bfc3a06a03bc65607f51b8c4403af6
contains more details.

** Affects: gtk+2.0 (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: mate-panel (Ubuntu)
 Importance: Undecided
 Status: Invalid


** Tags: vivid
-- 
/usr/bin/mate-panel:ERROR:/build/buildd/gtk+2.0-2.24.27/modules/other/gail/gail.c:622:gail_focus_notify_when_idle:
 code should not be reached
https://bugs.launchpad.net/bugs/1483430
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to gtk+2.0 in Ubuntu.

-- 
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 1598347] [NEW] /usr/bin/mate-panel:ERROR:/build/gtk+2.0-4ZhNBE/gtk+2.0-2.24.30/modules/other/gail/gail.c:622:gail_focus_notify_when_idle: code should not be reached

2017-07-15 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

The Ubuntu Error Tracker has been receiving reports about a problem
regarding mate-panel.  This problem was most recently seen with version
1.12.2-1, the problem page at
https://errors.ubuntu.com/problem/4b6610a1d753c24afed0539ed6e21646fcbbdf6e
contains more details.

** Affects: gtk+2.0 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: xenial
-- 
/usr/bin/mate-panel:ERROR:/build/gtk+2.0-4ZhNBE/gtk+2.0-2.24.30/modules/other/gail/gail.c:622:gail_focus_notify_when_idle:
 code should not be reached
https://bugs.launchpad.net/bugs/1598347
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to gtk+2.0 in Ubuntu.

-- 
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 1188475] Re: ldap group doesn't work

2017-07-15 Thread sles
About comment 6- in my opinion this highly depends on your implementation and 
policy.
I work for not so large company, I'd say small - just about 4200 employers-, so 
our policy can be wrong - it says not show users their rights, i.e. intruder 
needs to try ;-)
>From another point of view- ldap connection credentials are supplied in 
>config, so application have to use them, not others.
Your point of view is right too- as I said this depends on your policy.
Thank you!

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

Title:
  ldap group doesn't work

Status in Cyrus-sasl2:
  Fix Released
Status in cyrus-sasl2 package in Ubuntu:
  Confirmed

Bug description:
  Hello!

  I wrote almost the same mail to sasl mail list, but , I guess, it is
  good to fix in 12.04...

  This bug exists in 2.1.26 , and in 2.1.25 which is in 12.04

  Problem is that after user is authentificated with ldap bind , ldap 
  connection for checking user in group ( lak_group_member function )
  is made with this user's bind, not bind parameters from config file.
  User can not ( and have not in our case- I don't know why , but this is 
  not real problem ) have access to ldap groups.
  And so, authentication is always fail.

  I added unbind and anonymous bind ( enough in our case):

  /var/local/files/sasl/cyrus-sasl-2.1.26/saslauthd# diff -ur lak.c.orig 
  lak.c
  --- lak.c.orig2013-06-07 09:15:20.098788278 +0400
  +++ lak.c2013-06-07 09:22:31.504774185 +0400
  @@ -1342,6 +1342,10 @@
   if (rc != LAK_OK)
   goto done;

  +lak_unbind (lak );
  +rc  = lak_bind(lak, "");
  +
  +
   rc = ldap_search_st(lak->ld, group_search_base, 
  lak->conf->group_scope, group_filter, (char **) group_attrs, 0, 
  &(lak->conf->timeout), );
   switch (rc) {
   case LDAP_SUCCESS:

  
  but, it is obvoius that rebind should be done with credintials from 
  config, but this is over my head :-(

  Could you, please, fix this bug correctly?

  Thank you!

To manage notifications about this bug go to:
https://bugs.launchpad.net/cyrus-sasl2/+bug/1188475/+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 1603815] Re: after updating to ubuntu 16.04 the network manager is unable to connect me to the wifi network. I can see the network, but once I introduce the password, it asks me

2017-07-15 Thread Uwe
I'm experiencing the same problem after I have changed my WiFi router.
Each of my device connect flawlessly except a laptop running Ubuntu
16.04. I was only able to connect to my network after disabling the
NetworkManager and configuring WiFi using wpa_supplicant.

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

Title:
  after updating to ubuntu 16.04 the network manager is unable to
  connect me to the wifi network. I can see the network, but once I
  introduce the password, it asks me for the password after a few
  seconds and never connects.

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  after updating to ubuntu 16.04 the network manager is unable to
  connect me to the wifi network. I can see the network, but once I
  introduce the password, it asks me for the password after a few
  seconds and never connects. I use different devices connected to the
  same wifi so it is not a problem of writting the wrong password.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.1.93-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Jul 17 16:58:17 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-07-16 (1 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IpRoute:
   default via 192.168.2.1 dev enp2s0  proto static  metric 100
   169.254.0.0/16 dev enp2s0  scope link  metric 1000
   192.168.2.0/24 dev enp2s0  proto kernel  scope link  src 192.168.2.242  
metric 100
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME UUID  TYPE 
TIMESTAMP   TIMESTAMP-REALAUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH
   Conexión cableada 1  9e376788-1744-46de-a314-eeb07aad8c13  802-3-ethernet   
1468789026  dom 17 jul 2016 16:57:06 CDT  yes  4294966297no 
   /org/freedesktop/NetworkManager/Settings/2  yes enp2s0  activated  
/org/freedesktop/NetworkManager/ActiveConnection/1
   BELL419 28bd64cc4-181f-449b-95a3-edc74cf2a9a6  802-11-wireless  
0   never yes  0 no 
   /org/freedesktop/NetworkManager/Settings/1  no  --  -- --
  nmcli-dev:
   DEVICETYPE  STATE DBUS-PATH  
CONNECTION   CON-UUID  CON-PATH
   enp2s0ethernet  connected /org/freedesktop/NetworkManager/Devices/1  
Conexión cableada 1  9e376788-1744-46de-a314-eeb07aad8c13  
/org/freedesktop/NetworkManager/ActiveConnection/1
   wlp3s0b1  wifi  disconnected  /org/freedesktop/NetworkManager/Devices/0  
--   ----
   loloopback  unmanaged /org/freedesktop/NetworkManager/Devices/2  
--   ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1603815/+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 1699676] Re: package click 0.4.45.1+16.10.20160916-0ubuntu1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

2017-07-15 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: click (Ubuntu)
   Status: New => Confirmed

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

Title:
  package click 0.4.45.1+16.10.20160916-0ubuntu1 failed to
  install/upgrade: subprocess new pre-removal script returned error exit
  status 1

Status in click package in Ubuntu:
  Confirmed

Bug description:
  auto

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: click 0.4.45.1+16.10.20160916-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15
  Uname: Linux 4.10.0-24-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  Date: Thu Jun 22 12:00:59 2017
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2017-03-28 (86 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: click
  Title: package click 0.4.45.1+16.10.20160916-0ubuntu1 failed to 
install/upgrade: subprocess new pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/click/+bug/1699676/+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 1701180] Re: package bsdutils 1:2.29-1ubuntu2 failed to install/upgrade: le paquet est dans un état vraiment incohérent; vous devriez le réinstaller avant de tenter de le config

2017-07-15 Thread Gaël Rousseau
Reinstalling bsdutils works in my case:

sudo apt install --reinstall bsdutils

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

Title:
  package bsdutils 1:2.29-1ubuntu2 failed to install/upgrade: le paquet
  est dans un état vraiment incohérent; vous devriez  le réinstaller
  avant de tenter de le configurer.

Status in dpkg package in Ubuntu:
  Confirmed
Status in util-linux package in Ubuntu:
  Confirmed

Bug description:
  unable to update

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: bsdutils 1:2.29-1ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15
  Uname: Linux 4.10.0-24-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  Date: Thu Jun 29 07:52:35 2017
  DpkgTerminalLog:
   dpkg: erreur de traitement du paquet bsdutils (--configure) :
le paquet est dans un état vraiment incohérent; vous devriez
le réinstaller avant de tenter de le configurer.
  ErrorMessage: le paquet est dans un état vraiment incohérent; vous devriez  
le réinstaller avant de tenter de le configurer.
  InstallationDate: Installed on 2016-06-27 (366 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: util-linux
  Title: package bsdutils 1:2.29-1ubuntu2 failed to install/upgrade: le paquet 
est dans un état vraiment incohérent; vous devriez  le réinstaller avant de 
tenter de le configurer.
  UpgradeStatus: Upgraded to zesty on 2017-06-10 (18 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1701180/+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 1701180] Re: package bsdutils 1:2.29-1ubuntu2 failed to install/upgrade: le paquet est dans un état vraiment incohérent; vous devriez le réinstaller avant de tenter de le config

2017-07-15 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: util-linux (Ubuntu)
   Status: New => Confirmed

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

Title:
  package bsdutils 1:2.29-1ubuntu2 failed to install/upgrade: le paquet
  est dans un état vraiment incohérent; vous devriez  le réinstaller
  avant de tenter de le configurer.

Status in dpkg package in Ubuntu:
  Confirmed
Status in util-linux package in Ubuntu:
  Confirmed

Bug description:
  unable to update

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: bsdutils 1:2.29-1ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15
  Uname: Linux 4.10.0-24-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  Date: Thu Jun 29 07:52:35 2017
  DpkgTerminalLog:
   dpkg: erreur de traitement du paquet bsdutils (--configure) :
le paquet est dans un état vraiment incohérent; vous devriez
le réinstaller avant de tenter de le configurer.
  ErrorMessage: le paquet est dans un état vraiment incohérent; vous devriez  
le réinstaller avant de tenter de le configurer.
  InstallationDate: Installed on 2016-06-27 (366 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: util-linux
  Title: package bsdutils 1:2.29-1ubuntu2 failed to install/upgrade: le paquet 
est dans un état vraiment incohérent; vous devriez  le réinstaller avant de 
tenter de le configurer.
  UpgradeStatus: Upgraded to zesty on 2017-06-10 (18 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1701180/+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 1701180] Re: package bsdutils 1:2.29-1ubuntu2 failed to install/upgrade: le paquet est dans un état vraiment incohérent; vous devriez le réinstaller avant de tenter de le config

2017-07-15 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: dpkg (Ubuntu)
   Status: New => Confirmed

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

Title:
  package bsdutils 1:2.29-1ubuntu2 failed to install/upgrade: le paquet
  est dans un état vraiment incohérent; vous devriez  le réinstaller
  avant de tenter de le configurer.

Status in dpkg package in Ubuntu:
  Confirmed
Status in util-linux package in Ubuntu:
  Confirmed

Bug description:
  unable to update

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: bsdutils 1:2.29-1ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15
  Uname: Linux 4.10.0-24-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  Date: Thu Jun 29 07:52:35 2017
  DpkgTerminalLog:
   dpkg: erreur de traitement du paquet bsdutils (--configure) :
le paquet est dans un état vraiment incohérent; vous devriez
le réinstaller avant de tenter de le configurer.
  ErrorMessage: le paquet est dans un état vraiment incohérent; vous devriez  
le réinstaller avant de tenter de le configurer.
  InstallationDate: Installed on 2016-06-27 (366 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: util-linux
  Title: package bsdutils 1:2.29-1ubuntu2 failed to install/upgrade: le paquet 
est dans un état vraiment incohérent; vous devriez  le réinstaller avant de 
tenter de le configurer.
  UpgradeStatus: Upgraded to zesty on 2017-06-10 (18 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1701180/+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 1704544] [NEW] Absturz bereits beim Hochfahren von LINUX, funktioniert erst beim 2. Hochfahren!

2017-07-15 Thread Hans Ludwigs
Public bug reported:

Beim Start des Betriebsprogramms bleibt das Programm (LINUX UBUNTU"
stehen, ohne es zu beeenden und das bei fast jedem Hochfahren! Es klappt
erst beim zweiten Versuch, Dann jedenfalls meistens!

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: lsb 4.1+Debian11ubuntu6.1
ProcVersionSignature: Ubuntu 3.13.0-123.172-generic 3.13.11-ckt39
Uname: Linux 3.13.0-123-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.14.1-0ubuntu3.23
Architecture: amd64
Date: Fri Jul 14 09:31:57 2017
ErrorMessage: Abhängigkeitsprobleme - verbleibt unkonfiguriert
InstallationDate: Installed on 2016-06-23 (386 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.17.5ubuntu5.7
 apt  1.0.1ubuntu2.17
SourcePackage: lsb
Title: package lsb 4.1+Debian11ubuntu6.1 failed to install/upgrade: 
Abhängigkeitsprobleme - verbleibt unkonfiguriert
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package trusty

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

Title:
  Absturz bereits beim Hochfahren von LINUX, funktioniert erst beim 2.
  Hochfahren!

Status in lsb package in Ubuntu:
  New

Bug description:
  Beim Start des Betriebsprogramms bleibt das Programm (LINUX UBUNTU"
  stehen, ohne es zu beeenden und das bei fast jedem Hochfahren! Es
  klappt erst beim zweiten Versuch, Dann jedenfalls meistens!

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: lsb 4.1+Debian11ubuntu6.1
  ProcVersionSignature: Ubuntu 3.13.0-123.172-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-123-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  Date: Fri Jul 14 09:31:57 2017
  ErrorMessage: Abhängigkeitsprobleme - verbleibt unkonfiguriert
  InstallationDate: Installed on 2016-06-23 (386 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.17
  SourcePackage: lsb
  Title: package lsb 4.1+Debian11ubuntu6.1 failed to install/upgrade: 
Abhängigkeitsprobleme - verbleibt unkonfiguriert
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lsb/+bug/1704544/+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 1704541] [NEW] package bsdutils 1:2.29-1ubuntu2 failed to install/upgrade: o pacote bsdutils não está pronto para configuração não pode configurar (status actual `half-installed

2017-07-15 Thread Álvaro Aragão Athayde
Public bug reported:

Poped up when using Mozilla Thunderbird on my gmail Account.

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: bsdutils 1:2.29-1ubuntu2
ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
Uname: Linux 4.10.0-26-generic i686
NonfreeKernelModules: wl
ApportVersion: 2.20.4-0ubuntu4.1
Architecture: i386
Date: Sat Jul 15 09:58:53 2017
DpkgTerminalLog:
 dpkg: erro ao processar o pacote bsdutils (--configure):
  o pacote bsdutils não está pronto para configuração
  não pode configurar (status actual `half-installed')
ErrorMessage: o pacote bsdutils não está pronto para configuração  não pode 
configurar (status actual `half-installed')
InstallationDate: Installed on 2017-01-04 (191 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release i386 (20161012.2)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4
SourcePackage: util-linux
Title: package bsdutils 1:2.29-1ubuntu2 failed to install/upgrade: o pacote 
bsdutils não está pronto para configuração  não pode configurar (status actual 
`half-installed')
UpgradeStatus: Upgraded to zesty on 2017-05-17 (58 days ago)

** Affects: util-linux (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package i386 zesty

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

Title:
  package bsdutils 1:2.29-1ubuntu2 failed to install/upgrade: o pacote
  bsdutils não está pronto para configuração  não pode configurar
  (status actual `half-installed')

Status in util-linux package in Ubuntu:
  New

Bug description:
  Poped up when using Mozilla Thunderbird on my gmail Account.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: bsdutils 1:2.29-1ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
  Uname: Linux 4.10.0-26-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: i386
  Date: Sat Jul 15 09:58:53 2017
  DpkgTerminalLog:
   dpkg: erro ao processar o pacote bsdutils (--configure):
o pacote bsdutils não está pronto para configuração
não pode configurar (status actual `half-installed')
  ErrorMessage: o pacote bsdutils não está pronto para configuração  não pode 
configurar (status actual `half-installed')
  InstallationDate: Installed on 2017-01-04 (191 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release i386 (20161012.2)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: util-linux
  Title: package bsdutils 1:2.29-1ubuntu2 failed to install/upgrade: o pacote 
bsdutils não está pronto para configuração  não pode configurar (status actual 
`half-installed')
  UpgradeStatus: Upgraded to zesty on 2017-05-17 (58 days ago)

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


Re: [Touch-packages] [Bug 1692981] Re: package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting con

2017-07-15 Thread Fernando Couto
It seems that  sudo apt-get install –reinstall libc6-dbg: amd64

is working for my computer too.

Thank you very much to everybody!!


2017-07-15 0:28 GMT+02:00 vincenzo <1692...@bugs.launchpad.net>:

> Thanks to everyone I solved the bug  in fact it was the package
> that was not installed properly. I just had to reinstall the whole
> thing
>
> If anyone may be interested
>
> Sudo apt-get install --reinstall libc6-dbg: amd64
>
>
> Thank you again to everyone!!
>
> vincenzo
>
>
>
> 2017-07-14 11:25 GMT+02:00 carduner <1692...@bugs.launchpad.net>:
>
> > It works, after reinstall the packets (libc6-dbg:amd64 and openssl)
> > Thanks Seth!
> >
> > Le 12/07/2017 à 20:52, Seth Arnold a écrit :
> > > I'm curious how we can work around this bug. If you're affected please
> > > report the results of:
> > >
> > > dpkg -l | awk '/^iH/ { print $2 }'
> > >
> > > This shows which specific packages are half-installed on your systems.
> > >
> > > With the list of packages this returns, please also report success or
> > > failure of:
> > >
> > > sudo apt-get install --reinstall ALL PACKAGES FROM THE HALF-INSTALLED
> > > LIST
> > >
> > > Thanks
> > >
> >
> > --
> > You received this bug notification because you are subscribed to a
> > duplicate bug report (1701676).
> > https://bugs.launchpad.net/bugs/1692981
> >
> > Title:
> >   package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade:
> >   package is in a very bad inconsistent state; you should  reinstall it
> >   before attempting configuration
> >
> > Status in dpkg package in Ubuntu:
> >   Confirmed
> > Status in openssl package in Ubuntu:
> >   Confirmed
> >
> > Bug description:
> >   package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade:
> >   package is in a very bad inconsistent state; you should  reinstall it
> >   before attempting configuration
> >
> >   ProblemType: Package
> >   DistroRelease: Ubuntu 17.04
> >   Package: libssl-dev:amd64 1.0.2g-1ubuntu11.2
> >   ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
> >   Uname: Linux 4.10.0-21-generic x86_64
> >   ApportVersion: 2.20.4-0ubuntu4.1
> >   AptOrdering:
> >libssl1.0.0:amd64: Install
> >NULL: ConfigurePending
> >   Architecture: amd64
> >   Date: Tue May 23 21:47:55 2017
> >   DuplicateSignature:
> >package:libssl-dev:amd64:1.0.2g-1ubuntu11.2
> >Setting up libssl1.0.0:amd64 (1.0.2g-1ubuntu11.2) ...
> >dpkg: error processing package libssl-dev:amd64 (--configure):
> > package is in a very bad inconsistent state; you should
> >   ErrorMessage: package is in a very bad inconsistent state; you should
> > reinstall it before attempting configuration
> >   InstallationDate: Installed on 2017-05-15 (7 days ago)
> >   InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64
> (20170412)
> >   RelatedPackageVersions:
> >dpkg 1.18.10ubuntu2
> >apt  1.4
> >   SourcePackage: openssl
> >   Title: package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to
> > install/upgrade: package is in a very bad inconsistent state; you should
> > reinstall it before attempting configuration
> >   UpgradeStatus: No upgrade log present (probably fresh install)
> >
> > To manage notifications about this bug go to:
> > https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/
> 1692981/+subscriptions
> >
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1701880).
> https://bugs.launchpad.net/bugs/1692981
>
> Title:
>   package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade:
>   package is in a very bad inconsistent state; you should  reinstall it
>   before attempting configuration
>
> Status in dpkg package in Ubuntu:
>   Confirmed
> Status in openssl package in Ubuntu:
>   Confirmed
>
> Bug description:
>   package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade:
>   package is in a very bad inconsistent state; you should  reinstall it
>   before attempting configuration
>
>   ProblemType: Package
>   DistroRelease: Ubuntu 17.04
>   Package: libssl-dev:amd64 1.0.2g-1ubuntu11.2
>   ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
>   Uname: Linux 4.10.0-21-generic x86_64
>   ApportVersion: 2.20.4-0ubuntu4.1
>   AptOrdering:
>libssl1.0.0:amd64: Install
>NULL: ConfigurePending
>   Architecture: amd64
>   Date: Tue May 23 21:47:55 2017
>   DuplicateSignature:
>package:libssl-dev:amd64:1.0.2g-1ubuntu11.2
>Setting up libssl1.0.0:amd64 (1.0.2g-1ubuntu11.2) ...
>dpkg: error processing package libssl-dev:amd64 (--configure):
> package is in a very bad inconsistent state; you should
>   ErrorMessage: package is in a very bad inconsistent state; you should
> reinstall it before attempting configuration
>   InstallationDate: Installed on 2017-05-15 (7 days ago)
>   InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
>   RelatedPackageVersions:
>dpkg 1.18.10ubuntu2
>apt  1.4
>   SourcePackage: openssl
>   Title: package 

[Touch-packages] [Bug 1689825] Re: gnome-keyring not unlocked on boot

2017-07-15 Thread Eric Alzheimer
I can also confirm that removing dbus-user-session fixes this issues,
and it was installed with flatpak. The steps in #67 got everything back
to normal. Thanks to Eberhard and 513G3 for the solution.

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

Title:
  gnome-keyring not unlocked on boot

Status in D-Bus:
  New
Status in chromium-browser package in Ubuntu:
  Invalid
Status in flatpak package in Ubuntu:
  Confirmed
Status in gdm package in Ubuntu:
  Confirmed
Status in gnome-keyring package in Ubuntu:
  Confirmed
Status in libgnome-keyring package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  1) Release: 16.04.2
  2) gnome-keyring: 3.18.3-0ubuntu2
  3) Login. gnome-keyring unlocks "login" features including for google chrome
  4) gnome-keyring is not unlocked, chrome takes 2 minutes to open and with no 
secure password features(sync) functioning.

  For the past couple days, chrome on Ubuntu 16.04 takes a REALLY long
  time (maybe 2 minutes) to start. Once chrome is started, I am not able
  to sync and any secure password features are broken. I found out this
  is due to gnome-keyring not being unlocked at login. There's also no
  way to unlock the "login" portion of the keyring from the running
  daemon by default. I have to kill the gnome-keyring process and start
  without "--login" as a parameter. Then the "login" section shows up
  which I'm able to unlock. From there chrome starts up instantly but
  asks the following:

  Enter password to unlock your login keyring
  The login keyring did not get unlocked when you logged into your computer

  After that, all of it's sync and secure features are functional.

  Starting google-chrome-stable from a command line at boot without
  running the above workaround shows the following error messages:

  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  [4364:4393:0510/100407.740292:ERROR:token_service_table.cc(130)] Failed to 
decrypt token for service AccountId-108842767310111573264
  [4364:4445:0510/100407.740292:ERROR:gcm_store_impl.cc(929)] Failed to restore 
security token.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-keyring 3.18.3-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Wed May 10 09:43:37 2017
  SourcePackage: gnome-keyring
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/dbus/+bug/1689825/+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 1704409] Re: Flickering screen on ubuntu 16.04.2 Lenovo B70

2017-07-15 Thread lotuspsychje
** Summary changed:

- Flickering screen on ubuntu 16.04 Lenovo B70
+ Flickering screen on ubuntu 16.04.2 Lenovo B70

** Description changed:

  Tested both unity & ubuntu-gnome on 16.04.2
- and both are flickering on a product: Haswell-ULT Integrated Graphics 
Controller
- and kernel: Linux fernand-Lenovo-B70-80 4.8.0-58-generic #63~16.04.1-Ubuntu 
SMP Mon Jun 26 18:08:51 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
+ and both are constantly flickering from login to desktop and on LIVEusb on a 
product: 
+ 
+ Haswell-ULT Integrated Graphics Controller and driver=i915
+ 
+ and kernel: Linux fernand-Lenovo-B70-80 4.8.0-58-generic
+ #63~16.04.1-Ubuntu SMP Mon Jun 26 18:08:51 UTC 2017 x86_64 x86_64 x86_64
+ GNU/Linux
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-58.63~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-58-generic x86_64
  .tmp.unity_support_test.0:
-  
+ 
  ApportVersion: 2.20.1-0ubuntu2.9
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Jul 14 17:18:12 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
-  Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
-Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:3987]
+  Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
+    Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:3987]
  InstallationDate: Installed on 2017-07-14 (0 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  Lsusb:
-  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
-  Bus 001 Device 004: ID 8087:07dc Intel Corp. 
-  Bus 001 Device 003: ID 0bda:579a Realtek Semiconductor Corp. 
-  Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
-  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 004: ID 8087:07dc Intel Corp.
+  Bus 001 Device 003: ID 0bda:579a Realtek Semiconductor Corp.
+  Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80MR
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-58-generic 
root=UUID=c471367f-a9a5-4e15-a987-f7b614634a1d ro quiet splash 
"acpi_osi=Windows 2013" vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: D1CN06WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lenovo B70-80
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo B70-80
  dmi.modalias: 
dmi:bvnLENOVO:bvrD1CN06WW:bd05/18/2015:svnLENOVO:pn80MR:pvrLenovoB70-80:rvnLENOVO:rnLenovoB70-80:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoB70-80:
  dmi.product.name: 80MR
  dmi.product.version: Lenovo B70-80
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Fri Jul 14 17:06:37 2017
  xserver.configfile: default
  xserver.errors:
-  
+ 
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
-  product id5921 
-  vendor CMN
+  product id5921
+  vendor CMN
  xserver.version: 2:1.18.4-1ubuntu6.1~16.04.1

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

Title:
  Flickering screen on ubuntu 16.04.2 Lenovo B70

Status in xorg package in Ubuntu:
  New

Bug description:
  Tested both unity & ubuntu-gnome on 16.04.2
  and both are constantly flickering from login to desktop and on LIVEusb on a 
product: 

  

[Touch-packages] [Bug 1259508] Re: padsp only works when pulseaudio server is local

2017-07-15 Thread Launchpad Bug Tracker
[Expired for pulseaudio (Ubuntu) because there has been no activity for
60 days.]

** Changed in: pulseaudio (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  padsp only works when pulseaudio server is local

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu 12.04.3 LTS
  Release:  12.04

  the following line in padsp makes that it works only if there is a
  local pulseaudio process running

  $ grep pgrep /usr/bin/padsp
  if `pgrep -f /usr/bin/pulseaudio 1>/dev/null` ; then

  This breaks for thinclient setups with a remote pulseaudio server.

  So if you want to check, you may rather want to check for the presence of the
  PULSE_SERVER and PULSE_COOKIE environment variables.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1259508/+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 1292560] Re: unity-settings-daemon crashed with SIGSEGV in malloc_consolidate()

2017-07-15 Thread Launchpad Bug Tracker
[Expired for pulseaudio (Ubuntu) because there has been no activity for
60 days.]

** Changed in: pulseaudio (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  unity-settings-daemon crashed with SIGSEGV in malloc_consolidate()

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  I booted the system and got this error.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: unity-settings-daemon 14.04.0+14.04.20140310-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6
  Uname: Linux 3.13.0-17-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Mar 14 11:03:04 2014
  ExecutablePath: /usr/lib/unity-settings-daemon/unity-settings-daemon
  ProcCmdline: /usr/lib/unity-settings-daemon/unity-settings-daemon
  ProcEnviron:
   PATH=(custom, user)
   LANGUAGE=en_US
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f0b5c9ae583 :   cmp
0x18(%rax),%rbx
   PC (0x7f0b5c9ae583) ok
   source "0x18(%rax)" (0x7f0b5ccee7e80018) not located in a known VMA region 
(needed readable region)!
   destination "%rbx" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: unity-settings-daemon
  StacktraceTop:
   malloc_consolidate (av=av@entry=0x7f0b5ccee760 ) at malloc.c:4157
   _int_malloc (av=av@entry=0x7f0b5ccee760 , 
bytes=bytes@entry=1056) at malloc.c:3423
   __libc_calloc (n=, elem_size=) at malloc.c:3219
   pa_xmalloc0 () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-4.0.so
   pa_hashmap_new () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-4.0.so
  Title: unity-settings-daemon crashed with SIGSEGV in malloc_consolidate()
  UpgradeStatus: Upgraded to trusty on 2013-12-06 (97 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1292560/+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 1300193] Re: [G31M-S2L, Realtek ALC883, Green Line Out, Rear] No sound at all

2017-07-15 Thread Launchpad Bug Tracker
[Expired for pulseaudio (Ubuntu) because there has been no activity for
60 days.]

** Changed in: pulseaudio (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  [G31M-S2L, Realtek ALC883, Green Line Out, Rear] No sound at all

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  I upgraded Ubuntu 13.04 to 13.10 & then installed Ubuntu Restricted
  Extras from Ubuntu software center & observed that there is no sound.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: pulseaudio 1:4.0-0ubuntu6
  ProcVersionSignature: Ubuntu 3.11.0-18.32-generic 3.11.10.4
  Uname: Linux 3.11.0-18-generic i686
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: i386
  Date: Mon Mar 31 17:40:44 2014
  InstallationDate: Installed on 2014-03-19 (11 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424)
  MarkForUpload: True
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful
  Symptom_Card: Built-in Audio - HDA Intel
  Symptom_Jack: Green Line Out, Rear
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: No sound at all
  Title: [G31M-S2L, Realtek ALC883, Green Line Out, Rear] No sound at all
  UpgradeStatus: Upgraded to saucy on 2014-03-31 (0 days ago)
  dmi.bios.date: 11/03/2008
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F8b DL
  dmi.board.name: G31M-S2L
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF8bDL:bd11/03/2008:svnGigabyteTechnologyCo.,Ltd.:pnG31M-S2L:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnG31M-S2L:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: G31M-S2L
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1300193/+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 1358434] Re: usb headset not available as microphone source

2017-07-15 Thread Launchpad Bug Tracker
[Expired for pulseaudio (Ubuntu) because there has been no activity for
60 days.]

** Changed in: pulseaudio (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  usb headset not available as microphone source

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  I have a usb Plantronics .Audio 478 headset that I use for conference
  calls.  Works perfect in trusty, but upon upgrade to utopic the
  microphone is not available as an input in the gnome sound preferences
  or pavucontrol.  There appears to be an entry in alsamixer, and a
  source in pactl list.

  Source #9
State: SUSPENDED
Name: 
alsa_output.usb-Plantronics_Plantronics_.Audio_478_USB-00-USB.analog-stereo.monitor
Description: Monitor of Plantronics .Audio 478 USB Analog Stereo
Driver: module-alsa-card.c
Sample Specification: s16le 2ch 44100Hz
Channel Map: front-left,front-right
Owner Module: 29
Mute: no
Volume: 0: 100% 1: 100%
0: 0.00 dB 1: 0.00 dB
balance 0.00
Base Volume: 100%
 0.00 dB
Monitor of Sink: 
alsa_output.usb-Plantronics_Plantronics_.Audio_478_USB-00-USB.analog-stereo
Latency: 0 usec, configured 0 usec
Flags: DECIBEL_VOLUME LATENCY 
Properties:
device.description = "Monitor of Plantronics .Audio 478 USB 
Analog Stereo"
device.class = "monitor"
alsa.card = "3"
alsa.card_name = "Plantronics .Audio 478 USB"
alsa.long_card_name = "Plantronics Plantronics .Audio 478 USB 
at usb-:00:14.0-5.3.4, full speed"
alsa.driver_name = "snd_usb_audio"
device.bus_path = "pci-:00:14.0-usb-0:5.3.4:1.0"
sysfs.path = 
"/devices/pci:00/:00:14.0/usb1/1-5/1-5.3/1-5.3.4/1-5.3.4:1.0/sound/card3"
udev.id = "usb-Plantronics_Plantronics_.Audio_478_USB-00-USB"
device.bus = "usb"
device.vendor.id = "047f"
device.vendor.name = "Plantronics, Inc."
device.product.id = "c011"
device.product.name = "Plantronics .Audio 478 USB"
device.serial = "Plantronics_Plantronics_.Audio_478_USB"
device.string = "3"
module-udev-detect.discovered = "1"
device.icon_name = "audio-card-usb"
Formats:
pcm

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: pulseaudio 1:4.0-0ubuntu18
  ProcVersionSignature: Ubuntu 3.16.0-9.14-generic 3.16.1
  Uname: Linux 3.16.0-9-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.14.5-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Aug 18 11:28:51 2014
  InstallationDate: Installed on 2014-02-24 (175 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140218)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to utopic on 2014-08-17 (0 days ago)
  dmi.bios.date: 10/18/2013
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP112.88Z.0138.B02.1310181745
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-2BD1B31983FE1663
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro11,3
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-2BD1B31983FE1663
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP112.88Z.0138.B02.1310181745:bd10/18/2013:svnAppleInc.:pnMacBookPro11,3:pvr1.0:rvnAppleInc.:rnMac-2BD1B31983FE1663:rvrMacBookPro11,3:cvnAppleInc.:ct10:cvrMac-2BD1B31983FE1663:
  dmi.product.name: MacBookPro11,3
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.default.pa: 2014-08-17T12:06:50.161248

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1358434/+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 1373131] Re: PulseAudio seems to have crashed.

2017-07-15 Thread Launchpad Bug Tracker
[Expired for pulseaudio (Ubuntu) because there has been no activity for
60 days.]

** Changed in: pulseaudio (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  PulseAudio seems to have crashed.

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  PulseAudio seems to have crashed.
  can't conect to hdmi,
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25.
  ApportVersion: 2.0.1-0ubuntu17.7
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: PCH [HDA Intel PCH], device 0: ALC269VC Analog [ALC269VC Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D3', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xc260 irq 45'
 Mixer name : 'Intel PantherPoint HDMI'
 Components : 'HDA:10ec0269,103c1854,00100202 
HDA:80862806,80860101,0010'
 Controls  : 25
 Simple ctrls  : 11
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-stella-anaheim-precise-amd64-20130326-1
  DistroRelease: Ubuntu 12.04
  InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 
20130326-08:07
  MarkForUpload: True
  Package: pulseaudio 1:1.1-0ubuntu15.4
  PackageArchitecture: amd64
  ProcEnviron:
   LANGUAGE=en_US:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.5.0-54.81~precise1-generic 3.5.7.33
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Tags:  precise running-unity
  Uname: Linux 3.5.0-54-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 05/13/2013
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.35
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 1854
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 64.28
  dmi.chassis.asset.tag: 5CG3262F2F
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.35:bd05/13/2013:svnHewlett-Packard:pnHP250G1NotebookPC:pvr088E1300591600010:rvnHewlett-Packard:rn1854:rvr64.28:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP 250 G1 Notebook PC
  dmi.product.version: 088E1300591600010
  dmi.sys.vendor: Hewlett-Packard
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25.
  ApportVersion: 2.0.1-0ubuntu17.7
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: PCH [HDA Intel PCH], device 0: ALC269VC Analog [ALC269VC Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D3', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xc260 irq 45'
 Mixer name : 'Intel PantherPoint HDMI'
 Components : 'HDA:10ec0269,103c1854,00100202 
HDA:80862806,80860101,0010'
 Controls  : 25
 Simple ctrls  : 11
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-stella-anaheim-precise-amd64-20130326-1
  DistroRelease: Ubuntu 12.04
  InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 
20130326-08:07
  MarkForUpload: True
  Package: pulseaudio 1:1.1-0ubuntu15.4
  PackageArchitecture: amd64
  ProcEnviron:
   LANGUAGE=en_US:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.5.0-54.81~precise1-generic 3.5.7.33
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Tags:  precise running-unity
  Uname: Linux 3.5.0-54-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 05/13/2013
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.35
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 1854
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 64.28
  dmi.chassis.asset.tag: 5CG3262F2F
  

[Touch-packages] [Bug 1370091] Re: With music playing, pressing the dialpad keys reduces the volume for an odd interval

2017-07-15 Thread Launchpad Bug Tracker
[Expired for pulseaudio (Ubuntu) because there has been no activity for
60 days.]

** Changed in: pulseaudio (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  With music playing, pressing the dialpad keys reduces the volume for
  an odd interval

Status in pulseaudio package in Ubuntu:
  Expired
Status in tone-generator package in Ubuntu:
  Expired

Bug description:
  1. play a track
  2. open dialer-app and press the keypad

  What happens:
  The sound music turns down for a few seconds and then gets back to normal 
automatically.

  While the above feels like a good idea, it need refinement. In its
  current condition it rather feels broken.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: media-hub 2.0.0+14.10.20140910.2-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: armhf
  Date: Tue Sep 16 19:45:21 2014
  InstallationDate: Installed on 2014-09-16 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140916-020205)
  SourcePackage: media-hub
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1370091/+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 1373392] Re: [mako] high cpu usage when playing audio via speaker

2017-07-15 Thread Launchpad Bug Tracker
[Expired for pulseaudio (Ubuntu) because there has been no activity for
60 days.]

** Changed in: pulseaudio (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  [mako] high cpu usage when playing audio via speaker

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  $ system-image-cli -i
  current build number: 253
  device name: mako
  channel: ubuntu-touch/devel-proposed
  alias: ubuntu-touch/utopic-proposed
  last update: 2014-09-24 00:51:54
  version version: 253
  version ubuntu: 20140923.1
  version device: 20140923.1
  version custom: mako-0.6

  I noticed that when playing audio via the speaker/headphones the CPU
  usage is higher than when playing via a paired bluetooth speaker.

  Speaker CPU usage:
  Format pulse media-hub
  m4a 30  20
  flac 30  15
  mp3 25  20

  Bluetooth Speaker CPU usage:
  Format pulse media-hub
  m4a 10  15
  flac 10  10 
  mp3 15  10

  It has been suggested that changing the buffer size may resolve this
  issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1373392/+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 1346022] Re: [530U3C/530U4C, Realtek ALC269VC, Speaker, Internal] No sound at all

2017-07-15 Thread Launchpad Bug Tracker
[Expired for pulseaudio (Ubuntu) because there has been no activity for
60 days.]

** Changed in: pulseaudio (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  [530U3C/530U4C, Realtek ALC269VC, Speaker, Internal] No sound at all

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  Open bug in launchpad.net
  https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1345977

  "0) Play music with Rhytmbox => OK!
  1) Crash gnome-shell
  2) Restore system automatic gnome-shell
  3) Not sound (chromium (youtube); rhytmbox, etc.)

  Not go rhytmbox, not play music."

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: pulseaudio 1:4.0-0ubuntu16
  Uname: Linux 3.16.0-031600rc6-generic x86_64
  ApportVersion: 2.14.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   2800 F pulseaudio
  CurrentDesktop: GNOME
  Date: Mon Jul 21 03:08:00 2014
  InstallationDate: Installed on 2014-04-27 (84 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1346022/+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 1393501] Re: "sudo ubuntu-bug" -> select "Sound/audio problem"

2017-07-15 Thread Launchpad Bug Tracker
[Expired for pulseaudio (Ubuntu) because there has been no activity for
60 days.]

** Changed in: pulseaudio (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  "sudo ubuntu-bug" -> select "Sound/audio problem"

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  Tried to use ubuntu-bug to generate a report regarding not detecting
  external microphone but it hang while displaying "Collecting problem
  information". (bar was animating but nothing happend after 20
  minutes.)

  Then I tried "sudo ubuntu-bug" too se if that made a difference and it
  crashed pulseaudio.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: pulseaudio 1:4.0-0ubuntu22
  ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
  Uname: Linux 3.16.0-23-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  mikaelb2403 F pulseaudio
   /dev/snd/controlC0:  mikaelb2403 F pulseaudio
  Date: Mon Nov 17 18:51:49 2014
  InstallationDate: Installed on 2014-10-20 (28 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  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
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/12/2014
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP112.88Z.0138.B07.1402121134
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-2BD1B31983FE1663
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro11,3
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-2BD1B31983FE1663
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP112.88Z.0138.B07.1402121134:bd02/12/2014:svnAppleInc.:pnMacBookPro11,3:pvr1.0:rvnAppleInc.:rnMac-2BD1B31983FE1663:rvrMacBookPro11,3:cvnAppleInc.:ct10:cvrMac-2BD1B31983FE1663:
  dmi.product.name: MacBookPro11,3
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1393501/+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 1396848] Re: pulseaudio use 100% CPU

2017-07-15 Thread Launchpad Bug Tracker
[Expired for pulseaudio (Ubuntu) because there has been no activity for
60 days.]

** Changed in: pulseaudio (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  pulseaudio use 100% CPU

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  Pulse audio was running at 100% CPU.

  #1  0x7f555f872882 in pa_semaphore_wait () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-4.0.so
  #2  0x7f555faabf97 in pa_asyncmsgq_send () from 
/usr/lib/libpulsecore-4.0.so
  #3  0x7f555fadc79f in ?? () from /usr/lib/libpulsecore-4.0.so
  #4  0x7f555fae4cc1 in pa_sink_suspend () from /usr/lib/libpulsecore-4.0.so
  #5  0x7f555fabbc1e in pa_card_suspend () from /usr/lib/libpulsecore-4.0.so
  #6  0x7f5559c092a8 in ?? () from 
/usr/lib/pulse-4.0/modules/module-udev-detect.so
  #7  0x7f5559c0a105 in ?? () from 
/usr/lib/pulse-4.0/modules/module-udev-detect.so
  #8  0x7f555f600b87 in pa_mainloop_dispatch () from 
/usr/lib/x86_64-linux-gnu/libpulse.so.0
  #9  0x7f555f600f8c in pa_mainloop_iterate () from 
/usr/lib/x86_64-linux-gnu/libpulse.so.0
  #10 0x7f555f601030 in pa_mainloop_run () from 
/usr/lib/x86_64-linux-gnu/libpulse.so.0
  #11 0x00407058 in main ()

  Is the stack trace where it was before I had to kill it.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: pulseaudio 1:4.0-0ubuntu22
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  mat7680 F pulseaudio
   /dev/snd/controlC0:  mat7680 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Nov 26 18:34:22 2014
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to utopic on 2014-10-24 (33 days ago)
  dmi.bios.date: 02/06/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GIET69WW (2.19 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20ALCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50512 STD
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGIET69WW(2.19):bd02/06/2014:svnLENOVO:pn20ALCTO1WW:pvrThinkPadX240:rvnLENOVO:rn20ALCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20ALCTO1WW
  dmi.product.version: ThinkPad X240
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.default.pa: 2014-06-17T20:21:21.095448

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1396848/+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 1404094] Re: Sound stops working

2017-07-15 Thread Launchpad Bug Tracker
[Expired for pulseaudio (Ubuntu) because there has been no activity for
60 days.]

** Changed in: pulseaudio (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Sound stops working

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  My fully working sound configuration occasionally stops working.  Symptoms 
are:
  - System Settings -> Sound only shows "dummy output" and no input devices
  - restarting pulseaudio has no effect
  - aplay -l as root shows sound cards
  - fuser -v /dev/snd/* shows nothing; /dev/dsp and /dev/seq do not exist
  - Rebooting solves the problem

  This did not occur on trusty but has occurred twice on utopic in the
  last month or two.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: pulseaudio 1:4.0-0ubuntu22
  Uname: Linux 3.17.1-031701-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D3', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/controlC29', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: Unity
  Date: Fri Dec 19 12:40:29 2014
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: HDA-Intel - HDA Intel PCH
  Symptom_Jack: Digital Out, HDMI
  Title: [CTO, Intel PantherPoint HDMI, Digital Out, HDMI] Pulseaudio fails 
to detect card
  UpgradeStatus: Upgraded to utopic on 2014-11-10 (38 days ago)
  dmi.bios.date: 07/24/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET33WW (1.13 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET33WW(1.13):bd07/24/2012:svnLENOVO:pnCTO:pvrThinkPadX230:rvnLENOVO:rnCTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: CTO
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1404094/+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 1704528] [NEW] package coreutils 8.25-2ubuntu3~16.04 failed to install/upgrade: package coreutils is not ready for configuration cannot configure (current status 'half-installed'

2017-07-15 Thread phillip dixon
Public bug reported:

ran - sudo apt-get -f install and this appears to have fixed issue.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: coreutils 8.25-2ubuntu3~16.04
ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
Uname: Linux 4.4.0-83-generic i686
ApportVersion: 2.20.1-0ubuntu2.9
Architecture: i386
Date: Sat Jul 15 15:07:23 2017
DpkgTerminalLog:
 dpkg: error processing package coreutils (--configure):
  package coreutils is not ready for configuration
  cannot configure (current status 'half-installed')
ErrorMessage: package coreutils is not ready for configuration  cannot 
configure (current status 'half-installed')
InstallationDate: Installed on 2017-03-19 (117 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: coreutils
Title: package coreutils 8.25-2ubuntu3~16.04 failed to install/upgrade: package 
coreutils is not ready for configuration  cannot configure (current status 
'half-installed')
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-package i386 xenial

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

Title:
  package coreutils 8.25-2ubuntu3~16.04 failed to install/upgrade:
  package coreutils is not ready for configuration  cannot configure
  (current status 'half-installed')

Status in coreutils package in Ubuntu:
  New

Bug description:
  ran - sudo apt-get -f install and this appears to have fixed issue.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: coreutils 8.25-2ubuntu3~16.04
  ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
  Uname: Linux 4.4.0-83-generic i686
  ApportVersion: 2.20.1-0ubuntu2.9
  Architecture: i386
  Date: Sat Jul 15 15:07:23 2017
  DpkgTerminalLog:
   dpkg: error processing package coreutils (--configure):
package coreutils is not ready for configuration
cannot configure (current status 'half-installed')
  ErrorMessage: package coreutils is not ready for configuration  cannot 
configure (current status 'half-installed')
  InstallationDate: Installed on 2017-03-19 (117 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: coreutils
  Title: package coreutils 8.25-2ubuntu3~16.04 failed to install/upgrade: 
package coreutils is not ready for configuration  cannot configure (current 
status 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1704528/+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 1308096] Re: unknown

2017-07-15 Thread Launchpad Bug Tracker
[Expired for pulseaudio (Ubuntu) because there has been no activity for
60 days.]

** Changed in: pulseaudio (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  unknown

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  showed up on boot

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: pulseaudio 1:1.1-0ubuntu15.4
  ProcVersionSignature: Ubuntu 3.5.0-48.72~precise1-generic 3.5.7.31
  Uname: Linux 3.5.0-48-generic x86_64
  NonfreeKernelModules: nvidia
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25.
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  Card0.Amixer.info:
   Card hw:0 'SB'/'HDA ATI SB at 0xfeaf irq 16'
 Mixer name : 'Realtek ALC887'
 Components : 'HDA:10ec0887,105b0e37,00100202'
 Controls  : 44
 Simple ctrls  : 20
  Card1.Amixer.info:
   Card hw:1 'AK5370'/'AKM AK5370 at usb-:00:12.1-3, full speed'
 Mixer name : 'USB Mixer'
 Components : 'USB0556:0001'
 Controls  : 2
 Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'Mic',0
 Capabilities: cvolume cvolume-joined cswitch cswitch-joined penum
 Capture channels: Mono
 Limits: Capture 0 - 78
 Mono: Capture 71 [91%] [13.00dB] [on]
  Card2.Amixer.info:
   Card hw:2 'NVidia'/'HDA NVidia at 0xfcf7c000 irq 19'
 Mixer name : 'Nvidia GPU 0b HDMI/DP'
 Components : 'HDA:10de000b,10de0101,00100200'
 Controls  : 24
 Simple ctrls  : 4
  Date: Tue Apr 15 07:42:56 2014
  InstallationMedia: Mythbuntu 12.04.2 "Precise Pangolin" - Release amd64 
(20130213)
  MarkForUpload: True
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/10/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 080016
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: A88GMV
  dmi.board.vendor: FOXCONN
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr080016:bd06/10/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnFOXCONN:rnA88GMV:rvr1.0:cvnToBeFilledByO.E.M.: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: To Be Filled By O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1308096/+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 1412611] Re: redefining "default" in ~/.asoundrc is impossible after pulseaudio is installed

2017-07-15 Thread Launchpad Bug Tracker
[Expired for pulseaudio (Ubuntu) because there has been no activity for
60 days.]

** Changed in: pulseaudio (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  redefining "default" in ~/.asoundrc is impossible after pulseaudio is
  installed

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  redefining "default" in ~/.asoundrc is ineffective after pulseaudio is
  installed.  upon removing /usr/share/alsa/pulse-alsa.conf it becomes
  possible again.  i'm sure we can discuss at length whether this is an
  implementation bug or a documentation bug, but either way, it should
  be far easier than many hours of wanton searching to arrive at this
  simple fact.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: pulseaudio 1:4.0-0ubuntu22
  ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2
  Uname: Linux 3.18.0-9-generic i686
  ApportVersion: 2.15.1-0ubuntu2
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mino   1850 F lxpanel
mino   1896 F pulseaudio
  CurrentDesktop: LXDE
  Date: Mon Jan 19 18:57:18 2015
  InstallationDate: Installed on 2015-01-16 (3 days ago)
  InstallationMedia: Lubuntu 15.04 "Vivid Vervet" - Alpha i386 (20150114)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/09/2008
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: K8M800-8237
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd01/09/2008:svn:pn:pvr:rvn:rnK8M800-8237:rvr:cvn:ct3:cvr:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1412611/+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 1293833] Re: There is sound when booting up the computer, but once i log in to ubuntu, there is no sound, and there is no sound device in the sound applet

2017-07-15 Thread Launchpad Bug Tracker
[Expired for pulseaudio (Ubuntu) because there has been no activity for
60 days.]

** Changed in: pulseaudio (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  There is sound when booting up the computer, but once i log in to
  ubuntu, there is no sound, and there is no sound device in the sound
  applet

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  when i open pulseaudio it says connection to pulseaudio failed

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: pulseaudio 1:4.0-0ubuntu6
  ProcVersionSignature: Ubuntu 3.11.0-18.32-generic 3.11.10.4
  Uname: Linux 3.11.0-18-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC29', 
'/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC0', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D8p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Date: Mon Mar 17 18:48:55 2014
  InstallationDate: Installed on 2014-03-01 (16 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MarkForUpload: True
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/23/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 79CN46WW(V3.05)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058Std
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G510
  dmi.modalias: 
dmi:bvnLENOVO:bvr79CN46WW(V3.05):bd12/23/2013:svnLENOVO:pn20238:pvrLenovoG510:rvnLENOVO:rnINVALID:rvr31900058Std:cvnLENOVO:ct10:cvrLenovoG510:
  dmi.product.name: 20238
  dmi.product.version: Lenovo G510
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1293833/+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 1404729] Re: When a bluetooth output device is paired no volume control thru indicator-sound

2017-07-15 Thread Launchpad Bug Tracker
[Expired for pulseaudio (Ubuntu) because there has been no activity for
60 days.]

** Changed in: pulseaudio (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  When a bluetooth output device is paired no volume control thru
  indicator-sound

Status in indicator-sound package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  Test Case:
  pair a bluetooth speaker
  play an audio file

  What happens:
  sound is output to the bluetooth speaker but no volume control is possible 
thru the sound indicator or sound settings volume label
  To get sound volume control one has to pick the bluetooth device in sound 
setting

  What should happen:
  once a speaker or headphones is paired sound settings should automatically 
set that as the output device to enable volume control

  : "The indicator and the volume
  slider — identical to its counterpart in System Settings — should both
  represent, and the slider should adjust, the volume of the active
  output role through the primary sound output."

  : "If you connect any
  audio output device that is not headphones, a headset, or a secondary
  display, the primary output should change to that device."

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: unity-control-center 15.04.0+15.04.20141217-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
  Uname: Linux 3.16.0-25-generic x86_64
  ApportVersion: 2.15.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Dec 21 16:08:20 2014
  InstallationDate: Installed on 2014-11-16 (35 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20141114)
  SourcePackage: unity-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_unity-control-center: deja-dup 32.0-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1404729/+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 1391470] Re: returning buzz on high quality resample

2017-07-15 Thread Launchpad Bug Tracker
[Expired for pulseaudio (Ubuntu) because there has been no activity for
60 days.]

** Changed in: pulseaudio (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  returning buzz on high quality resample

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  When I change to higher resampling it happens every few minutes
  repeating buzz

  resample-method = src-sinc-medium-quality
  default-sample-format = s24le
  default-sample-rate = 96000

  
  $ pacmd list-sinks | grep sample
sample spec: s24le 2ch 96000Hz
sample spec: s32le 2ch 96000Hz

  I have two sound cards, the symptom emerges on the external usb X-Fi
  soundcard.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: pulseaudio 1:4.0-0ubuntu22
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   mastier   24128 F...m pulseaudio
   /dev/snd/controlC1:  mastier   24128 F pulseaudio
   /dev/snd/controlC0:  mastier   24128 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Nov 11 11:56:16 2014
  InstallationDate: Installed on 2012-10-25 (747 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to utopic on 2014-11-01 (10 days ago)
  dmi.bios.date: 03/12/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GCET98WW (2.58 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 34352NG
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGCET98WW(2.58):bd03/12/2014:svnLENOVO:pn34352NG:pvrThinkPadX230Tablet:rvnLENOVO:rn34352NG:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 34352NG
  dmi.product.version: ThinkPad X230 Tablet
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.pulse.daemon.conf: [modified]
  mtime.conffile..etc.pulse.daemon.conf: 2014-11-11T11:31:45.523371

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1391470/+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 1388463] Re: package libpulse0 1:4.0-0ubuntu22 failed to install/upgrade: trying to overwrite shared '/etc/pulse/client.conf', which is different from other instances of package

2017-07-15 Thread Launchpad Bug Tracker
[Expired for pulseaudio (Ubuntu) because there has been no activity for
60 days.]

** Changed in: pulseaudio (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  package libpulse0 1:4.0-0ubuntu22 failed to install/upgrade: trying to
  overwrite shared '/etc/pulse/client.conf', which is different from
  other instances of package libpulse0:amd64

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  ...

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: libpulse0 1:4.0-0ubuntu22
  Uname: Linux 3.17.0-031700-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  claudiu2259 F pulseaudio
  Date: Sat Nov  1 23:13:24 2014
  DuplicateSignature: package:libpulse0:1:4.0-0ubuntu22:trying to overwrite 
shared '/etc/pulse/client.conf', which is different from other instances of 
package libpulse0:amd64
  ErrorMessage: trying to overwrite shared '/etc/pulse/client.conf', which is 
different from other instances of package libpulse0:amd64
  InstallationDate: Installed on 2014-11-01 (0 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Title: package libpulse0 1:4.0-0ubuntu22 failed to install/upgrade: trying to 
overwrite shared '/etc/pulse/client.conf', which is different from other 
instances of package libpulse0:amd64
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: V1.22
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Aspire V5-571G
  dmi.board.vendor: Acer
  dmi.board.version: V1.22
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.22
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrV1.22:bd03/15/2013:svnAcer:pnAspireV5-571G:pvrV1.22:rvnAcer:rnAspireV5-571G:rvrV1.22:cvnAcer:ct9:cvrV1.22:
  dmi.product.name: Aspire V5-571G
  dmi.product.version: V1.22
  dmi.sys.vendor: Acer

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